Created attachment 30749 [details] xorg.0.log Card: Intel GM45 uname -a: Linux tamarin 2.6.31-1-amd64 #1 SMP Sat Oct 24 17:50:31 UTC 2009 x86_64 GNU/Linux (but I get the same bug with 2.6.30) X.Org X Server 1.6.5 Module intel: vendor="X.Org Foundation" compiled for 1.6.4, module version = 2.9.0 libdrm:2.4.14-1 mesa: OpenGL version string: 2.1 Mesa 7.6 distribution: debian (testing + unstable kernel) machine: fujitsu siemens amilo 3655 Problem description: The machine is a laptop with an internal screen (lvds), and a dvi output. When I plug a dvi monitor, it does not get used. xrandr sees the monitor, detects its resolutions, and accepts to swith it it on and off or change its resolution. Still, it won't send any signal to the monitor, which goes to sleep. Meanwhile, the resolution I choose for the dvi screen gets used as a virtual resolution for the lvds screen, even if I put the dvi screen "above" or "right-of" the lvds screen. For instance, if i have 1280x800 on the lvds screen and 1900x1200 on the dvi screen, i get a blank dvi monitor, and the 1280x800 first pixels of a 1900x1200 screen on the internal monitor. This happens whether or not i enable kernel mode setting. The same setting with a VGA screen works without problem.
Created attachment 30750 [details] xrandr --verbose output (with dvi monitor attached)
The dvi monitor is also not usable as a text console (whereas a vga monitor gets used as a text console).
Created attachment 30905 [details] dmesg output, booting on the dvi screen If I plug the dvi screen at boot time, the dvi screen gets used by the kernel until the framebuffer appears. Then it switches to the lvds screen.
Does this still happen with recent kernels? It looks like the kernel is detecting your DVI output and setting a mode on it at least... If recent kernels still have the issue, can you capture a register dump using intel_reg_dumper from the intel-gpu-tools package?
Timeout. If this is still a problem, please re-open.
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.