Gateway EV910 "gwy232a" generates bad EDID

[M Pietila]

Binary package hint: xserver-xorg

Running the latest Hardy beta on a desktop with CRT monitor (model Gateway EV910, edid "name" gwy232a) with NVidia card. Used Restricted Driver Manager to install the nvidia driver and as far as I can tell it's being used.

Only 320x240 and 640x480 modes are being enabled at startup. I attempted to use xrandr to add new modes, but I get only "xrandr: Configure crtc0 failed" when I try to actually use any of the new modes (I used entries from my working Gutsy xorg.conf file as a base to create the modes).

I know I could probably just copy over the old xorg.conf file from Gutsy but I thought I should report a bug so maybe this can get fixed and help others (and me) in the future.

I don't know how to tell if this is a problem with the information reported by the monitor or with the nvidia driver (maybe it's not actually active, even though the Restricted Driver Manager says it is?) Reading the Xorg.0.log leads me to believe the nvidia driver really is active...

Attaching xorg.conf, Xorg.0.log, output of get-edid | parse-edid, output of ddcprobe, output of xrandr -q. Please let me know if any additional information would be helpful.

[M Pietila (pietila-meghan)]

Ignore the 1024x768 entry in the xrandr output; I added that myself, but it won't let me enable it, either through xrandr --output default --mode 1024x768@85, or through the Ubuntu Screen Resolution tool. The screen just flickers once, no new entries are added to the Xorg.0.log

[M Pietila (pietila-meghan)]

The output from running xresprobe leads me to believe this is not a bug with the nvidia driver? It seems to think it can support 1024x768 just fine on this monitor...

[Bryce Harrington (bryce)]

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).

[M Pietila (pietila-meghan)]

Great--glad to hear the information was useful. I went ahead and copied over my old xorg.conf file from Gutsy to use for now, and that gets me up and running with a decent resolution. I'm attaching the file in case someone else stumbles across this same bug and doesn't have a working xorg.conf file like I did (obviously, change its name to xorg.conf and put it in your /etc/X11 directory in place of the existing one if you choose to use this).

[warjowuch (lulkoek)]

I have got the exact problem on my EIZO F730, in combination with an ATI Radeon 9200SE.
It just does not detect correct resolutions. It can read EDID, but it seems to not use it.
It does use the vesa driver, but I can't imagine where to configure X to use the radeon-driver. It is all gone... (xorg.conf does not have a section for this anymore and the screens ' n graphics-utility is gone too)

[warjowuch (lulkoek)]

Oh, i was mistaken, it did use the OSS-ati driver, my compiz-effects were working correctly...

__________________________________________________
GRATIS: Movie-FLAT. Jetzt freischalten!
http://freemail.web.de/club/maxdome.htm/?mc=025557

[Bryce Harrington (bryce)]

I am forwarding the following bug from a Ubuntu reporter:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/211098

The user has a Gateway EV910 monitor (edid "name" gwy232a) which can be DDC probed properly but produces EDID that both read-edid and xorg fail to understand:

http://launchpadlibrarian.net/13079404/ddcprobe.txt
http://launchpadlibrarian.net/13079429/edid.txt
http://launchpadlibrarian.net/13079409/Xorg.0.log

From the read-edid output, it sounds like the monitor has some extended data in it?

 ...
 Call failed

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

Xorg's output follows:

(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):
(II) NVIDIA(0): NVIDIA GPU GeForce 6600 (NV43) at PCI:1:0:0 (GPU-0)
(--) NVIDIA(0): Memory: 262144 kBytes
(--) NVIDIA(0): VideoBIOS: 05.43.02.46.01
(II) NVIDIA(0): Detected AGP rate: 8X
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(--) NVIDIA(0): Connected display device(s) on GeForce 6600 at PCI:1:0:0:
(--) NVIDIA(0): CRT-0
(--) NVIDIA(0): CRT-0: 400.0 MHz maximum pixel clock
(II) NVIDIA(0): Assigned Display Device: CRT-0
(==) NVIDIA(0):
(==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
(==) NVIDIA(0): will be used as the requested mode.
(==) NVIDIA(0):
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0): "nvidia-auto-select"
(II) NVIDIA(0): Virtual screen size determined to be 640 x 480
(WW) NVIDIA(0): Unable to get display device CRT-0's EDID; cannot compute DPI
(WW) NVIDIA(0): from CRT-0's EDID.
(==) NVIDIA(0): DPI set to (75, 75); computed from built-in default

[Bryce Harrington (bryce)]

M Pietila, I've reported this bug upstream to Xorg as this bug: https://bugs.freedesktop.org/show_bug.cgi?id=15681

Could you please also subscribe yourself to that bug, so that if they have questions or need additional info, you can reply directly?

[M Pietila (pietila-meghan)]

Update - in Intrepid Ibex (beta), after applying the restricted NVidia driver through the built-in Ubuntu mechanism, my screen resolution is working beautifully - I didn't have to do any messing with the xorg file this time. Before using the restricted driver, however, it was still only allowing 800x600 resolution. Not surprising, since there doesn't seem to have been any activity on the upstream bug so I don't think anything has been added to the x server to handle this monitor yet.

[Bryce Harrington (bryce)]

Good to hear you've found a way to solve the problem - would you mind checking to see if it is still solved in Jaunty and if so, mark the status of this as Fixed?

Since it sounds like an -nvidia bug I'm reassigning to nvidia.

[Bryce Harrington (bryce)]

[This is an automated message]

In Jaunty (9.04), we have just updated to the latest
nvidia-graphics-drivers-180 package from nVidia, version 180.44.

This package provides fixes for a large number of bugs, and we need your
assistance in testing if it fixes the issue you reported.

To do this, please do the following:

 a. Update to the 180.44 version of -nvidia using your favorite update
     method

 b. Attempt to reproduce your bug

 c. If your bug still remains, please simply reply to this email
     indicating so.

 d. If your bug is now solved, you can help us by setting your bug
     report to Fix Released:
     * In launchpad, go to your bug report
     * Click on the downward pointing arrow under Status
     * Set the Status field to 'Fix Released'
     * Comment on the change, such as, 'Verified fixed in 180.44'
     * Click 'Save Changes'

 e. If the original problem is solved but there are now other problems,
     please close the original bug and open new ones for those issues.

Thank you!

For details on the changes in this version of -nvidia, please see:

   http://www.nvidia.com/object/linux_display_ia32_180.44.html

[Julien Cristau (jcristau)]

the log is using the nvidia driver. there's no evidence of a server bug here.

[Bryce Harrington (bryce)]

Resolved in ubuntu now in any case.

[Bryce Harrington (bryce)]

Based on your last comment, assuming the issue is resolved.

[Burton D. Barber (burtondbarber)]

Thanks a million M Pietela!!! I had the exact same problem that you did and your solution (using an old conf file) worked for me too.

[Gitlab-migration (gitlab-migration)]

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/365.