In my case, I think Steam installer may have added some nvidia stuff to
my system, which doesn't have a nvidia hardware.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2084046
Titl
** Also affects: linux-hwe-6.8 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-hwe-6.8 (Ubuntu)
Status: New => Fix Committed
** No longer affects: linux-hwe-6.8 (Ubuntu Noble)
** Changed in: linux-hwe-6.8 (Ubuntu)
Milestone: None => jammy-updates
--
You rec
** Tags added: verification-done-noble-linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2084046
Title:
[i915] Phantom "Unknown" display detected on Intel Meteor Lake
Status in Linux
Sorry for taking forever, it also works on noble for me. Thank you all
very much!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2084046
Title:
[i915] Phantom "Unknown" display detected
Fix released to Plucky (kernel 6.12)
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2084046
Title:
[i915] Phan
Using the module via the proposed repository fixed this issue for me on
a Thinkpad X1 with intel graphics card.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2084046
Title:
[i915] Phant
** Also affects: linux-hwe-6.11 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-hwe-6.11 (Ubuntu Noble)
Status: New => Fix Committed
** No longer affects: linux-hwe-6.11 (Ubuntu Oracular)
** Changed in: linux-hwe-6.11 (Ubuntu)
Status: New => Fix Committed
** Changed in: linux
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2084046
Title:
[i915] Phantom "Unknown" display detected on Intel Meteor Lake
** Changed in: linux (Ubuntu)
Milestone: None => ubuntu-25.04
** Changed in: linux (Ubuntu Noble)
Milestone: None => noble-updates
** Changed in: linux (Ubuntu Oracular)
Milestone: None => oracular-updates
--
You received this bug notification because you are a member of Kernel
Pack
I can see the fix coming to Plucky in 6.12.0-10.10 now.
** Also affects: linux via
https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12160
Importance: Unknown
Status: Unknown
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug noti
Thanks for verifying Oracular Till!
** Tags added: verification-done-oracular-linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2084046
Title:
[i915] Phantom "Unknown" display detect
@mruffell, thank you very much!
I have installed the kernel 6.11.0-17-generic on my Oracular system now
and the ghost screen has gone away. All perfect now for me. Now I should
be able to do projections on conferences in Mirror mode without
problems.
$ uname -rv
6.11.0-17-generic #17-Ubuntu SMP P
Hi everyone,
I have excellent news. The Kernel Team respun this current SRU cycle to include
more patches, and
commit ad604f0a4c040dcb8faf44dc72db25e457c28076
Author: Thomas Zimmermann
Date: Tue Sep 24 10:41:03 2024 +0200
Subject: firmware/sysfb: Disable sysfb for firmware buffers with unknown p
It looks like this is causing at least some instances of bug 2095456.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2084046
Title:
[i915] Phantom "Unknown" display detected on Intel Met
Hi Justus,
Thanks for testing. We now know the fix, which is great news.
We just need to get it out to everyone now.
I see the Kernel Team has just tagged 6.8.0-52-generic, but
"firmware/sysfb: Disable sysfb for firmware buffers with unknown parent"
isn't in there. It looks like it might be a pa
Hi Matthew,
I tested your noble-kernel and it does indeed fix the issue, thank you
very much!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2084046
Title:
[i915] Phantom "Unknown" disp
Let's not close it prematurely. There is no fix released for Plucky yet.
** Changed in: linux (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
Hi Justus,
The test kernel finished building. I built a 6.8 kernel for Noble and a 6.11
kernel for Oracular. It uses the same patches that the Kernel Team has applied
to their git tree.
Please note this package is NOT SUPPORTED by Canonical, and is for TESTING
PURPOSES ONLY. ONLY Install in a ded
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu Noble)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu Oracular)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of
Hi Justus,
Thanks for bisecting! It really helps. Looking at what you found:
ubuntu-noble 648dd7aa1f69e1ea8eb6fdb8515e86945df2e424
commit b49420d6a1aeb399e5b107fc6eb8584d0860fbd7
Author: Alex Deucher
Date: Wed Aug 21 15:11:35 2024 -0400
Subject: video/aperture: optionally match the device in s
Hey,
since I've also encountered the bug, I've bisected the range and found
the offending commit to be 648dd7aa1f69 in noble.
I don't have any knowledge about the kernel, this was even the first
time I compiled a kernel, so I don't really know what's going on, except
that the problem has to be in
This issue could be reproduced at 6.8.0-50-generic and 6.8.0-51-generic,
I could not reproduce it at 6.8.0-49-generic kernel.
I used ThinkPad X1 Carbon Gen 12, it's also Meteor Lake.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux i
Hey y'all,
same here, a recent upgrade appears to have introduced the extra display
and with it some trouble with attaching external displays...
```
$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Meteor Lake-P [Intel Arc
Graphics] (rev 08)
$ grep 'model name' /proc/cpui
Hi, I'm also experiencing this issue. My current workaround is adding
the following udev rule to delete `/dev/dri/card0`:
```
TEST=="/sys/devices/platform/simple-framebuffer.0/drm/card0", RUN+="/bin/rm
/dev/dri/card0"
```
this deletes the extra device automatically and makes the extra display
The diff is too large to find anything obvious, but hopefully someone
can just bisect between the Ubuntu-6.8.0-49.49..Ubuntu-6.8.0-50.51 tags
(if indeed that is the range).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
h
Issue still present in 6.8.0-51 kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2084046
Title:
[i915] Phantom "Unknown" display detected on Intel Meteor Lake
Status in linux pack
Per comment #18, bug 2091576 also mentions this is a regression in
6.8.0-50-generic. So it might be easy to identify.
** Tags added: noble
** Tags added: regression-update
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2084046
Title:
[i915] Phantom "Unknown" display detected on Intel Meteor Lake
Status in linux package in Ubuntu:
Confirmed
Status in linu
Paolo, any idea what commit has regressed noble?
Nothing stands out looking at drivers/drm/i915
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2084046
Title:
[i915] Phantom "Unknown" di
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Noble)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/208
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Oracular)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Oracular)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/
This bug impacts my laptop 100% of the time. Booting into the previous
kernel (6.8.0-49-generic) is my current workaround.
See my bug report at https://bugs.launchpad.net/ubuntu/+bug/2091576 for
more info.
--
You received this bug notification because you are a member of Kernel
Packages, which i
I have added the above-mentioned part to the kernel command line (file
/etc/default/grub), done "sudo update-grub", and rebooted.
After that, the ghost screen is still there (I only had used the
temporary workaround before booting).
I have run
sudo dmesg > dmesg-boot-log-20241031.txt
to obtain
Till, can you boot with "drm.debug=0xe log_buf_len=4M ignore_loglevel"
appended to your boot cmdline, and attach the full boot log?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2084046
T
Just disabling the ghost display in the System Settings was not helpful
for me, as with this the "Mirror" mode for the actual display and the
projector does not work. Probably this is another bug ...
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
> the interesting bit is that my i915 GPU is marked as card1, and not
card0 (e.g. simpledrm was loaded earlier, attached as card0 but later
unloaded?)
Yes, that's what happens.
As soon as i195 registers fb0, simpledrm is unloaded:
[ 280.175042] i915 :00:02.0: [drm] fb0: i915drmfb frame buffer
The temporary workaround suggested in the initial description in the bug
report for NVidia, bug 2060268
-
[ Temporary Workaround ]
1. sudo rm /dev/dri/card0
2. Log in again.
-
also works here. I did not try the permanent workaround presented there,
but most probably it will also work.
E
A simple workaround for most people is to just disable the Unknown
display in Settings > Displays.
** Summary changed:
- [i915] Phantom "Unknown" display detected
+ [i915] Phantom "Unknown" display detected on Intel Meteor Lake
--
You received this bug notification because you are a member of K
I have the same problem.
I bought a ThinkPad T14 gen 5 in May this year. Worked perfectly with
Noble, but now, after the evil Oracular Oriole has eaten the nice cute
Numbats, I got the ghost screen as described in this bug report. This is
very disturbing, starting from the mouse pointer not stoppi
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2084046
I'm not sure #7 is the same issue because it seems to jump to
conclusions and describes a black TTY problem which I don't have.
As for testing the idea in comment #6, my kernel log shows simpledrm
creating /dev/fb0 around 1.4s, and i915 creating /dev/fb1 around 8.9s.
Both /dev/fb[01] still exist a
Daniel, did you have any chance to test it on your Meteor Lake? Can you
reproduce it?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2084046
Title:
[i915] Phantom "Unknown" display detec
Might be related to:
https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11158
** Bug watch added: gitlab.freedesktop.org/drm/i915/kernel/-/issues #11158
https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11158
--
You received this bug notification because you are a member of Kernel
> Like bug 2060268, this doesn't seem a kernel bug, more like a user
space issue.
I think it's the kernel DRM driver (i915) that's meant to evict
simpledrm. Either explicitly or implicitly. Or maybe simpledrm monitors
for new fbdev devices and removes itself when another one appears (as
alluded to
It's only happening on Meteor Lake for me. And I only have one Meteor
Lake machine to try.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2084046
Title:
[i915] Phantom "Unknown" display
** Attachment added: "Full dmesg log attached"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2084046/+attachment/5828504/+files/dmesg.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
I've an i915 Intel laptop running Oracular, but i can't reproduce the
issue:
```
[0.321780] ACPI: bus type drm_connector registered
[0.330979] [drm] Initialized simpledrm 1.0.0 for simple-framebuffer.0 on
minor 0
[0.333513] simple-framebuffer simple-framebuffer.0: [drm] fb0:
simpledr
Like bug 2060268, this doesn't seem a kernel bug, more like a user space
issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2084046
Title:
[i915] Phantom "Unknown" display detected
S
49 matches
Mail list logo
