[Bug 100267] New: Ghost eDP-1 monitor on skylake with kernel >= 4.8

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sat Mar 18 06:56:18 UTC 2017


https://bugs.freedesktop.org/show_bug.cgi?id=100267

            Bug ID: 100267
           Summary: Ghost eDP-1 monitor on skylake with kernel >= 4.8
           Product: DRI
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: alkisg at gmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 130300
  --> https://bugs.freedesktop.org/attachment.cgi?id=130300&action=edit
Xorg.0.log and output of xrandr, cpuinfo and dmesg for all those kernels

After upgrading my Ubuntu 16.04.1 (kernel 4.4) to 16.04.2 (kernel 4.8), I got a
"fake" monitor called eDP-1, which now "extends" my real VGA monitor called
DP-1.
So when I boot into the desktop I only see a wallpaper, as the menus are shown
in the "primary" ghost monitor. Running `xrandr --output eDP-1 --off` works
around the problem.

I also tried with kernel 4.11, and I have a fake monitor there too, but now
it's called DP-1 instead of eDP-1, and my real VGA is now called DP-2.

This is on a i3-6100 CPU.

To sum up:
Kernel 4.4: HDMI-1, HDMI-2, DP-1 (real)
Kernel 4.8: eDP-1 (fake), HDMI-1, HDMI-2, DP-1 (real)
Kernel 4.11: DP-1 (fake), HDMI-1, HDMI-2, DP-2 (real)

I'm attaching a .zip file that contains subdirectories with Xorg.0.log and the
output of xrandr, cpuinfo and dmesg for all those kernels.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20170318/400ceb52/attachment.html>


More information about the intel-gfx-bugs mailing list