http://bugzilla.opensuse.org/show_bug.cgi?id=939607 Bug ID: 939607 Summary: Kernel 4.1.2 + 2014 MacBook Air external vga monitor not detected Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-maintainers@forge.provo.novell.com Reporter: peter@rmk2.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Since updating to 4.1 (and more specifically, 4.1.2), my external monitor (LG Flatron 2000CE) that is attached to my 2014 MacBook Air via an Apple MiniDisplayPort->VGA adapter is not recognised at all anymore. This worked fine with 4.0.x kernels. However, xrandr seems to alternate between either not showing anything at all or a broken, arbitrary monitor VIRTUAL1, perhaps in an unsuccessful attempt to fix things: sh-4.3$ uname -r 4.1.2-1-desktop sh-4.3$ xrandr --query Screen 0: minimum 8 x 8, current 1440 x 900, maximum 32767 x 32767 eDP1 connected primary 1440x900+0+0 (normal left inverted right x axis y axis) 286mm x 179mm 1440x900 59.84*+ 1024x768 60.00 800x600 60.32 56.25 640x480 59.94 DP1 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) HDMI1 disconnected (normal left inverted right x axis y axis) HDMI2 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis) 848x480 (0xee) 33.750MHz h: width 848 start 864 end 976 total 1088 skew 0 clock 31.02KHz v: height 480 start 486 end 494 total 517 clock 60.00Hz 640x480 (0xef) 25.175MHz h: width 640 start 656 end 752 total 800 skew 0 clock 31.47KHz v: height 480 start 489 end 492 total 525 clock 59.94Hz The same problem (and setup) have been described by a handful of Arch users here at https://bbs.archlinux.org/viewtopic.php?id=199540 and an Arch bugreport has been filed at https://bugs.archlinux.org/task/45733 According to https://bugs.archlinux.org/task/45733#comment137505 this seems to be a bug that was recently introduced during changes to the Intel kernel drivers, and the poster identified commit 1d002fa720738bcd0bddb9178e9ea0773288e1dd as the one at fault. Let me know if you need to know anything else! -- You are receiving this mail because: You are on the CC list for the bug.