I have a MacBook with the following card: $ lspci 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) 00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03) Sometimes xrandr shows: # xrandr Screen 0: minimum 320 x 200, current 1280 x 800, maximum 2048 x 1200 VGA disconnected (normal left inverted right x axis y axis) LVDS connected 1280x800+0+0 (normal left inverted right x axis y axis) 286mm x 179mm 1280x800 59.9*+ 60.0 58.9 1024x768 60.0 800x600 60.3 56.2 640x480 59.9 and after a reboot I have: # xrandr Screen 0: minimum 320 x 200, current 1280 x 864, maximum 2048 x 1200 VGA disconnected (normal left inverted right x axis y axis) LVDS connected 1280x800+0+0 (normal left inverted right x axis y axis) 286mm x 179mm 1280x800 59.9*+ 60.0 58.9 1024x768 60.0 800x600 60.3 56.2 640x480 59.9 TMDS-1 connected 1152x864+0+0 (normal left inverted right x axis y axis) 434mm x 270mm 1680x1050 59.9 + 60.0 1400x1050 60.0 1280x1024 75.0 60.0 60.0 1440x900 60.0 1280x960 60.0 60.0 1152x864 75.0* 75.0 1024x768 75.1 75.0 70.1 60.0 832x624 74.6 800x600 72.2 75.0 60.3 56.2 640x480 75.0 72.8 75.0 60.0 59.9 720x400 70.1 The difference in Xorg.0.log as analyzed by sndirsch in https://bugzilla.novell.com/show_bug.cgi?id=425252 is: --- bug-425252_Xorg.0.log.without-output +++ bug-425252_Xorg.0.log.with-output [...] -(II) intel(0): No SDVO device found on SDVOB -(II) intel(0): I2C device "SDVOCTRL_E for SDVOB:SDVO Controller B" removed. -(II) intel(0): I2C bus "SDVOCTRL_E for SDVOB" removed. -(II) intel(0): EDID vendor "APP", prod id 40031 +(II) intel(0): I2C bus "SDVOB DDC Bus" initialized. +(II) intel(0): Output TMDS-1 has no monitor section +(II) intel(0): SDVOB: device VID/DID: 04:AA.03, clock range 25.0MHz - 165.0MHz +(II) intel(0): SDVOB: 1 input channel +(II) intel(0): SDVOB: TMDS0 output reported +(II) intel(0): Current clock rate multiplier: 1 +(II) intel(0): EDID vendor "APP", prod id 40031 +(II) intel(0): I2C device "SDVOB DDC Bus:ddc2" registered at address 0xA0. +(II) intel(0): I2C device "SDVOB DDC Bus:ddc2" removed. +(II) intel(0): I2C device "CRTDDC_A:ddc2" registered at address 0xA0. +(II) intel(0): EDID vendor "GSM", prod id 22121 [...] +(II) intel(0): Output TMDS-1 connected [...] +(II) intel(0): Output TMDS-1 using initial mode 1152x864 [...] -(II) intel(0): Pipe A is off -(II) intel(0): Display plane A is now disabled and connected to pipe A. +(II) intel(0): Pipe A is on +(II) intel(0): Display plane A is now enabled and connected to pipe A. [...] +(II) intel(0): Output TMDS-1 is connected to pipe A This is openSUSE factory: # rpm -q xorg-x11-server kernel-default xorg-x11-server-7.3-163 kernel-default-2.6.27-rc5.git2.5
The external DVI monitor is always connected, right?
yes the screen is connected the whole time.
I just found out that I do not have to reboot. Instead /etc/init.d/xdm restart is enough. (i.e restarting the X-Server)
Ok this happens every then and then but I have no idea. How to reliable repdroduce this. But it certainly is not damaged hardware as it has not happened with Mac OS X ever. (In reply to comment #1) > The external DVI monitor is always connected, right? Is there no way to hotplug the monitor? Replugging does in fact not help. As far as I remember this was working before. I thought TMDS-1 xrandr entry was displayed regardless of the connection state ...?
is there any progress on this issue? I still have the same problem. By now my packages are newer: fm@macbook:~> rpm -q xorg-x11-server kernel-default xorg-x11-server-7.4-8.4 kernel-default-2.6.27.1-2.1 $ rpm -q --changelog xorg-x11-server * Sa Okt 11 2008 sndirsch suse.de - xorg-server 1.5.2 and $ rpm -q --changelog xorg-x11-driver-video * Do Okt 09 2008 sndirsch suse.de - xf86-video-intel 2.4.97.0_2.5-branch_ffcbbb0 * Intel-2008-Q3-RC3 release Stefan please add if this packages have anything more important. @intel please tell me what to try to get this working. It is really annoying to have to logout to get a beamer working... Sadly suspending does not bring the display to live either...
updating the version
Since Kent asked me about the severity/priority.
This bug is still present today. $ rpm -q xorg-x11-server kernel-default xorg-x11-driver-video xorg-x11-server-7.4-11.1 kernel-default-2.6.27.4-2.1 xorg-x11-driver-video-7.4-15.2 The intel driver is: - xf86-video-intel 2.5.0 * Enable Option "Legacy3D" for 965 as well, and clarify both the docs and code. with - xf86-video-intel-memleak.diff * fixes memory leak (bnc #432595, comment #22) - removed xf86-video-intel-memleak.diff, which resulted in a Xserver crash (bnc #439642) - xf86-video-intel-G33-1mb.diff * fix 1MB issue on Intel Onboard Graphics G33 (bnc #391261) - xf86-video-intel-commit-7ddea04.diff * revert commit 7ddea04, which broke Xserver start at least on Intel G4X/i386 (bnc #439865) - xf86-video-intel-commit-4dd0068.diff * revert commit 4dd0068, which broke Xserver start at least on Intel G4X/i386 (bnc #439865)
Lowering severity.
Created attachment 20607 [details] [review] detect sdvo device
I did a patch in Comment #10 to detect sdvo device, which works fine in my sdvo machine, please try it. Thanks Ma Ling
Stefan, please try this patch. thanks
ping for response...
adding stefan to CC: again ;) Stefan are you able to repdroduce this issue? Could you build packages in the buildservice with this patch applied? Right now it works for me ~95% therefore it will take a little to verify the problem is gone. ;) # rpm -q xorg-x11-server kernel-default xorg-x11-driver-video xorg-x11-server-7.4-17.1 kernel-default-2.6.27.7-8.1 xorg-x11-driver-video-7.4-19.2
Stefan is currently on vacation. For me the patch looks too intrusive to apply unconditionally for RC2 without testing, but I'll verify whether Stefan built test packages in our build service.
I'll track it with bug# 18136 then... *** This bug has been marked as a duplicate of bug 18136 ***
Just to make it clear, my external monitor is detected in 98% of the cases, it just missing sometimes. This has gotten way better since reporting the bug, but is still happened on the day I wrote comment #6 .
(In reply to comment #15) > Stefan is currently on vacation. For me the patch looks too intrusive to > apply unconditionally for RC2 without testing, I fully agree here. > but I'll verify whether Stefan built test packages in our build service. No, I didn't. Probably I removed myself from Cc, before the patch has been provided by Intel.
(In reply to comment #16) > I'll track it with bug# 18136 then... > > > *** This bug has been marked as a duplicate of bug 18136 *** For some reason this bug has been closed (no response by reporter). Thus reopening this one. The issue still exists.
Ling, any plans to include patch from comment #10 in a newer release?
Ling's patch looks not right to me, and we have already checked SDVO_DETECT bit before init SDVO. We need ModeDebug option on Xorg log when DVI failed.
lower serverity based on comment# 17.
(In reply to comment #19) > (In reply to comment #16) > > I'll track it with bug# 18136 then... > > > > > > *** This bug has been marked as a duplicate of bug 18136 *** > > For some reason this bug has been closed (no response by reporter). Thus > reopening this one. The issue still exists. I'm clearing NEEDINFO, as I assume Stephan means the issue still exists with the patch applied.
Hi Felix Because our driver has been modified much, could you kindly please update your driver from master tree, then upload log file with modedebug optoin on? Thanks for your help Ma Ling
I am not using the relevant notebook with openSUSE anymore. With Fedora 11 (xorg-x11-drv-intel-2.7.0-7.fc11.i586) the outputs do not get lost. But I sadly I have big modesetting problems, see https://bugzilla.redhat.com/show_bug.cgi?id=505536 and https://bugzilla.redhat.com/show_bug.cgi?id=494390. You may close this bug as I am currently not able to reproduce it anymore. Sorry.
mark as resolved for now.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.