[nvidia-glx] EDID data is sometimes wrong and only a custom EDID will fix it

[Jonathan Lozinski]

The toshiba satellite 704 laptop suffers from the EDID issues many others have noted. The previous nvidia binary driver releases used IgnoreEDID set to true which did fix the issue.

The latest move the useEDID set to false. This does not however work on the 704, it results in bars of bleeding colours etc on the screen that look as though damage could well be being done to the dispay.

I have tried all the work arounds other than this and no success. to reproduce simply add the Option "useEDID" "false" to the device section of the x config.

Note, that I did succeed in rewriting a bin dump of the EDID data which is received when actually using the EDID data in the driver. details of this are in this bug report:

https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.20/+bug/91292

someone suggested I register a new bug regarding the EDID work-around failing even worse.

[Sitsofe Wheeler (sitsofe)]

Jonathan:
You might be able to get an EDID from the nv open source driver by using the information that appears in the Xorg.0.log when using the nv driver. Could you post the Xorg.0.log produced by the nv driver here?

[syncomm (syncomm)]

I have the same issue as Jonathan with a Toshiba Tecra 2100 (using GeForce4 420 GO and the nvidia driver). I get a perfect 1024x768 with the nv driver -- however the EDID info from the nvidia driver pegs my native screen resolution at 969x768 :( The workaround mentioned in Bug 91292 (hex editing the edid.bin) works for me. UseEdid set to false does not fix it -- nor does Option "ModeValidation" "NoDFPNativeResolutionCheck". I'll start it up with the nv driver and post the EDID info and the edid.bin from nvidia-settings.

[syncomm (syncomm)]

[attachments]

[Sitsofe Wheeler (sitsofe)]

(Might be related to this post http://www.nvnews.net/vbulletin/showthread.php?t=93218&page=2 )

[Bryce Harrington (bryce)]

This package has become obsolete so we're closing out the bug report as WONTFIX.
Thanks for reporting it though!