I can confirm this issue, with a graphics chip detected by lspci as: 00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express Integrated Graphics Controller (rev 10)
With no monitor connected, X fails to start, and GDM goes into an infinite loop trying to get it up and running. (I'm running GDM on a headless server to accept XDCMP connections.) With the "i915.modeset=0" kernel parameter, the dmesg line disappears, but the symptom of X failing to start and GDM looping persists. The problem seems to be that the Intel driver reports no valid screenmodes available when there's no connected monitor. I initially thought this was due to the failure to fetch DDC information - but it's not. If I connect my old monitor via a BNC cable - which can't carry DDC information - then X starts correctly, and picks a fallback mode. Attached are Xorg logs for both cases. What needs to happen to solve this, I think, is for the Xorg intel driver to enable the VGA output as a fallback if it can't detect any connected monitors. As a workaround, if I allow X -configure to create a dummy Xorg.conf, then change the driver from intel to vesa, the problem goes away. I'd rather have the correct driver selected for those occasions when I do need to connect a monitor, however. ** Patch added: "Xorg log for the case when no cable is attached" http://launchpadlibrarian.net/39183716/Xorg.NoCable.log -- Headless GDM on G33 causes huge dmesg output https://bugs.launchpad.net/bugs/492062 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
