Comment 3 for bug 640807

Revision history for this message
Erick Brunzell (lbsolost) wrote : Re: Forces low refresh rate on CRT monitor

I'm also effected by this bug, but with quite different symptoms. I also know this is quite long so I'll try to break things up very well.

First of all the hardware involved is Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02) with a Hanns-G 22" LCD. That same hardware has worked properly with all versions of Ubuntu from Hardy up through Maverick Beta. The default will normally be 1680x1050@61Hz.

I've been monitoring the daily builds more closely than usual following changes to the new ubiquity and beginning about September 16th the Live CD would result in the monitor spitting the error message "Input signal out of range". Oddly I have a fully updated Maverick installed that began with the toolchain upload May 22nd and I've not been able to reproduce this bug on it.

However I do have two additional Mavericks on this machine leftover from Beta upgrade and iso-testing, so over the weekend I booted into the one installed for iso-testing, fully updated it, and was presented with the "out-of-range" error on reboot. That's a good thing as it's much easier to fiddle with an installed OS than a Live CD or USB.

I have tried a number of things:

1) Creating a known good xorg.conf w/a default resolution of 1440x900@60Hz.

2) Editing "/etc/gdm/Init/Default" and/or "/etc/gdm/PreSession/Default" to default to 1440x900@60Hz.

Note: both 1 & 2 are options I've used for some time due to poor vision.

3) Suspecting it may be KMS related I tried two different mainline kernels - 2.6.35-02063504 & 2.6.35-02063506.

None of the above worked, but the installed "non-working" Maverick will boot if I choose Recovery Mode from the grub menu and then choose FailsafeX, however I've tried the Live CD with many options including "nomodeset" and "i915.modeset=1" which both result in the "out-of-range" error, and also "i915.modeset=1" which drops me to a TTY, and if I try startx I just get the error "Fatal server error: no screens found".

I should also mention that this i945 works OK with my old 17" CRT, and an old machine w/VIA P4M800 graphics still works OK with the 22" LCD.

Finally this AM MacUntu from the forums pointed me to this bug and sure as heck if I uncheck "turn_on_external_monitors_at_startup" in gconf booting works normally and defaults to my custom resolution of 1440x900@60Hz either upon reboot or if I restart gdm.

Oddly the working Maverick that began with the toolchain upload has "turn_on_external_monitors_at_startup" checked in gconf and it's working OK. Odd, eh?

I think I'll leave the working Maverick alone rather than try to break it, but I am going to try and get a TTY in the current daily live i386 and see if editing gconf will allow it to boot w/startx.

I'll be glad to do any testing requested or to attach any requested info, but I'm beyond clueless so please be as complete as possible in your requests.

I'd expect iso-testing for the RC to begin very soon and I'd think we need to at least address this in the release notes.