<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - nouveau GF108 kernel crash in optimus mode when enabling external display output" href="https://bugs.freedesktop.org/show_bug.cgi?id=64774#c14">Comment # 14</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - nouveau GF108 kernel crash in optimus mode when enabling external display output" href="https://bugs.freedesktop.org/show_bug.cgi?id=64774">bug 64774</a> from <a class="email" href="mailto:pasik@iki.fi" title="Pasi Kärkkäinen <pasik@iki.fi>"> Pasi Kärkkäinen</a> <pre> Ok, after a lot of reboots and trying different kernels I realized the issue is not related to the warn_on patch I added. The difference is caused by the fact that if I boot with DVI monitor connected before powering on the system, or not. So what happens is: 1) I boot to Linux with DVI monitor connected to nouveau before powering on the system. This is how it looks then: $ grep . /sys/class/drm/card*-*/status /sys/class/drm/card0-LVDS-1/status:connected /sys/class/drm/card0-VGA-1/status:disconnected /sys/class/drm/card1-DP-1/status:disconnected /sys/class/drm/card1-DP-2/status:connected /sys/class/drm/card1-DP-3/status:disconnected /sys/class/drm/card1-LVDS-2/status:disconnected /sys/class/drm/card1-VGA-2/status:disconnected DP-2 is the external DVI monitor. So it's listed as "connected", but xrandr doesn't see it: $ xrandr Screen 0: minimum 320 x 200, current 1600 x 900, maximum 8192 x 8192 LVDS1 connected 1600x900+0+0 (normal left inverted right x axis y axis) 309mm x 174mm 1600x900 60.0*+ 40.0 1024x768 60.0 800x600 60.3 56.2 640x480 59.9 VGA1 disconnected (normal left inverted right x axis y axis) Nothing about the nouveau adapter in xrandr output.. 2) I boot to Linux with DVI monitor NOT connected to nouveau. I connect the DVI cable after the system has booted to Xorg. This is how it looks then: $ grep . /sys/class/drm/card*-*/status /sys/class/drm/card0-LVDS-1/status:connected /sys/class/drm/card0-VGA-1/status:disconnected /sys/class/drm/card1-DP-1/status:disconnected /sys/class/drm/card1-DP-2/status:connected /sys/class/drm/card1-DP-3/status:disconnected /sys/class/drm/card1-LVDS-2/status:disconnected /sys/class/drm/card1-VGA-2/status:disconnected So again DP-2 is shown as connected to the DVI monitor, which is true. $ xrandr Screen 0: minimum 320 x 200, current 1600 x 900, maximum 8192 x 8192 LVDS1 connected 1600x900+0+0 (normal left inverted right x axis y axis) 309mm x 174mm 1600x900 60.0*+ 40.0 1024x768 60.0 800x600 60.3 56.2 640x480 59.9 VGA1 disconnected (normal left inverted right x axis y axis) LVDS-2 disconnected (normal left inverted right x axis y axis) VGA-2 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DP-2 connected (normal left inverted right x axis y axis) 1920x1080 59.9 + 1600x1200 60.0 1680x1050 59.9 1280x1024 60.0 1440x900 59.9 1280x960 60.0 1280x800 59.9 1024x768 60.0 800x600 60.3 56.2 640x480 60.0 DP-3 disconnected (normal left inverted right x axis y axis) 1024x768 (0x8e) 65.0MHz h: width 1024 start 1048 end 1184 total 1344 skew 0 clock 48.4KHz v: height 768 start 771 end 777 total 806 clock 60.0Hz 800x600 (0x8f) 40.0MHz h: width 800 start 840 end 968 total 1056 skew 0 clock 37.9KHz v: height 600 start 601 end 605 total 628 clock 60.3Hz 800x600 (0x90) 36.0MHz h: width 800 start 824 end 896 total 1024 skew 0 clock 35.2KHz v: height 600 start 601 end 603 total 625 clock 56.2Hz And now xrandr can see the DVI monitor aswell. So when I plug-in the DVI cable on-the-fly to nouveau adapter, then the external display is actually detected, and can be enabled and used (with artifacts/corruption, but that is a separate bug ;) So 'xrandr' shows the same problem as I described earlier with the Mate desktop display-properties GUI application. When the laptop is booted with DVI cable plugged in from the start, the mate-display-properties GUI doesn't allow me to enable the DVI monitor - so the behaviour matches xrandr. I assume mate-display-properties internally uses xrandr. But this sounds like an another bug really..</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>