I am running Debian Sid, and recently ran a routine update. A slightly new
version of xorg was installed, 7.1.0-2. After a reboot, X would no longer
start. I had been using the nvidia proprietary driver (card is XFX nVidia
6600GT), and it would simply fail. I switched to the nv driver, and ran
startx. My monitor (15" LCD, KDS Rad-5p) went various streaked colors, and
reported "out of sync range. v:78.9/h:35.4". Switching back to a text vterm,
it was still streaked out and required a reboot to clear it.
I experimented with my xorg.conf settings a bit, and found no difference if I
or left those blank. I still got the same error from the monitor. (Those are
the values reported by the monitor, according to the log file.) I also
commented out all of the SubSections in the "Screen" section, and again no
However, if I switched to the vesa driver, X started normally, albeit in 2D and
with a refresh that is quite slow and barely usable.
I'm not sure what other info you'd need. I wasn't sure if I should file this
here or on the Debian BTS, but was advised to do so here by someone in #xorg on
freenode. Let me know if there is other info I could provide.
I may be having the same problem. Just upgraded Xorg under Gentoo to the modular
version (7.1.1). Running X -configure produces a configuration file that has the
proper sync rates, but trying to run with it gives only an "Out of range" error
from my monitor - despite its having been correctly recognized by X -configure.
Further, nearly identical values were previously working under Xorg - and the
monolithic XFree before it. But now they don't!
So far, I don't know if the sync is out of range, or maybe X is trying to go to
a resolution this monitor doesn't support.
Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Nv driver is still unable to autodetect via DDC or EDID even I'm using latest Fedora 8 Test 2 with xorg-x11-drv-nv-2.1.3-1.fc8. This does not work for more than a year.
This leads to unusable 'nv' driver on many motherboards with onboard graphics.
See bug #12002 for possible reason.
xf86-video-nv has been officially unmaintained for a bit now, and we are closing all -nv bugs. If your problem was not addressed, and -nv is still broken, please try xf86-video-nouveau. Thank you.