Right. It didn't occur to me, since I'm pretty sure it isn't a bug I'm looking at, but it was a truly instructive exercise. It is attached, gzipped.
So, this is what I'm seeing:
(II) NVIDIA(0): Validating Mode "1920x1080":
(II) NVIDIA(0): 1920 x 1080 @ 60 Hz
(II) NVIDIA(0): For use as DFP backend.
(II) NVIDIA(0): Mode Source: EDID
(II) NVIDIA(0): Pixel Clock : 148.35 MHz
(II) NVIDIA(0): HRes, HSyncStart : 1920, 2008
(II) NVIDIA(0): HSyncEnd, HTotal : 2052, 2200
(II) NVIDIA(0): VRes, VSyncStart : 1080, 1084
(II) NVIDIA(0): VSyncEnd, VTotal : 1089, 1125
(II) NVIDIA(0): H/V Polarity : +/+
(WW) NVIDIA(0): Mode is rejected: HorizSync (67.4 kHz) out of range
(WW) NVIDIA(0): (15.000-46.000 kHz).
This looks like a mode I might like to use... But then it says it is rejected
I don't understand what's going on here, though. EDID, in the screen, says that this mode exists, and then NVIDIA decides it is invalid because it computes the horizsync is out of range. I'm pretty sure the the horizsync range is correct, so I guess the trick is to set some parameters to get it in range. That means a more elaborate ModeLine, I guess...
Anything that can help do this...?