Comment 7 for bug 211098

Revision history for this message
Bryce Harrington (bryce) wrote : Re: [hardy] Screen resolution only 640x480

Thanks for filing this as a separate bug from bug 194760 - you're right that this will be cleaner. I'm keeping that bug around mostly to centralize all the info about debugging these edid fail issues.

Anyway, your ddcprobe output looks fine, but something is really weird with the read-edid stuff:

....
 Call failed

The EDID data should not be trusted as the VBE call failed
EDID claims 32 more blocks left

*********** Something special has happened!
Please contact the author, John Fremlin
E-mail: one of <email address hidden>,<email address hidden>,<email address hidden>
Please include full output from this program (especially that to stderr)

...
The EDID data should not be trusted as the VBE call failed
EDID claims 32 more blocks left
EDID blocks left is wrong.
Your EDID is probably invalid.
....

Also, this error shows up in the Xorg.0.log:

(WW) NVIDIA(GPU-0): The EDID read for display device CRT-0 is invalid: the
(WW) NVIDIA(GPU-0): checksum for EDID version 1 is invalid.
(--) NVIDIA(GPU-0):
(--) NVIDIA(GPU-0): Raw EDID bytes:
(--) NVIDIA(GPU-0):
(--) NVIDIA(GPU-0): 00 ff ff ff ff ff ff 00 ff ff 2c 23 b6 b0 01 00
(--) NVIDIA(GPU-0): 2a 0b 01 03 1c 24 1b aa e9 68 45 a3 53 47 9a 24
(--) NVIDIA(GPU-0): 10 48 4c ff ff 80 61 59 45 59 31 59 61 40 31 4f
(--) NVIDIA(GPU-0): 3b ca 81 99 a9 4f 1a 4f 40 30 62 b0 32 40 40 c0
(--) NVIDIA(GPU-0): 10 00 5e 06 11 00 00 1e 00 00 00 fd 00 32 a0 1e
(--) NVIDIA(GPU-0): 5f 14 00 0a 20 20 20 20 20 20 00 00 00 fc 00 47
(--) NVIDIA(GPU-0): 61 74 65 77 61 79 20 45 56 39 31 30 00 00 00 fc
(--) NVIDIA(GPU-0): 00 0a 20 20 20 20 20 20 20 20 20 20 20 20 00 5b
(--) NVIDIA(GPU-0):

Xorg loses its mind about your monitor at this point, and decides to go arch-conservative:

(II) NVIDIA(0): Virtual screen size determined to be 640 x 480

So yeah, as a workaround you'll need to specify your hsync and vrefresh rates in xorg.conf, and specify your resolutions and such.

I think this will require a quirk be put in for your monitor. Looks like you've provided all the necessary info for doing this. Stay tuned; hopefully we'll have the fix in by Intrepid (*maybe* sooner).