Ubuntu
linux-restricted-modules-2.6.20 package

nvidia-glx should add [Option "UseEDID" "False"] to [Section "Device"] in xorg.conf

Bug #105957 reported by Obi Bok
2
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.20 (Ubuntu)
Won't Fix
Wishlist
Unassigned

Bug Description

Binary package hint: nvidia-glx

After enabling the nVIDIA binary driver and restarting the system (or just restarting X), X successfully starts but fails to set the correct refresh/frequency resulting in a blank screen and "out of range" display message.

Recently tested in Feisty daily 20070411. This problem has been present since Dapper release. Also see bug #94671 (linux-restricted-modules-2.6.20).

Fix:
Add to xorg.conf in Section "Device" => Option "UseEDID" "False" <=

Example:
--8<--
Section "Device"
        Identifier "NVIDIA Corporation NV43 [GeForce 6200]"
        Driver "nvidia"
        BusID "PCI:1:0:0"
        Option "UseEDID" "False"
EndSection
-->8--

As per nVIDIA documentation [http://http.download.nvidia.com/XFree86/Linux-x86/1.0-8774/README/appendix-d.html]
--8<--
Option "UseEDID" "boolean"

    By default, the NVIDIA X driver makes use of a display device's EDID, when available, during construction of its mode pool. The EDID is used as a source for possible modes, for valid frequency ranges, and for collecting data on the physical dimensions of the display device for computing the DPI (see Appendix Y, Dots Per Inch). However, if you wish to disable the driver's use of the EDID, you can set this option to False:

        Option "UseEDID" "FALSE"

    Note that, rather than globally disable all uses of the EDID, you can individually disable each particular use of the EDID; e.g.,

        Option "UseEDIDFreqs" "FALSE"
        Option "UseEDIDDpi" "FALSE"
        Option "ModeValidation" "NoEdidModes"

    Default: True (use EDID).
-->8--

This option should be set by default when enabling the nVIDIA binary driver.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

I'm not sure setting that is wise, since it mostly depends on the monitor you use.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

..setting it by default, that is.

Revision history for this message
Obi Bok (obibok) wrote :

Would setting this option by default cause more harm than good? I tested all HorizSync and VertRefresh and created custom ModeLines but nothing worked. Disabling UseEDID was the only solution. I know others experienced exactly the same problem.

Revision history for this message
Johan Kiviniemi (ion) wrote :

I strongly disagree with disabling EDID by default, unless it's proven most monitors report broken EDID values.

Revision history for this message
Obi Bok (obibok) wrote :

How about creating an alternate package with xorg.conf including this option? Or a solution where xorg.conf would get modified in a similar fashion to 'nvidia-glx-config enable' (perhaps 'nvidia-glx-config fixfreq')?

Keep in mind that once users affected by this issue switch from 'nv' to 'nvidia' driver, they loose their GUI. A console message informing about the alternate configuration would be very helpful. Otherwise users are left stranded and resort to using another working system to search the Internet for a fix.

Revision history for this message
Martin Pitt (pitti) wrote :

I generally don't like to do changes which fix things for one set of people and break it for others. Apparently there is no 'correct' setting to that option which works for everybody, so the driver itself should figure it out dynamically.

Revision history for this message
Obi Bok (obibok) wrote :

Understandable. In this case it'd be good to have the default setting as it is right now, with EDID enabled, but also an alternate solution with this option disabled. Maybe like I suggested earlier, a modification to the xorg.conf file via a command or at least a clear message what to edit somewhere in tty. Thanks for your thoughts on this.

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

This sounds similar to Bug #94671 ...

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

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

Daniel T Chen (crimsun)
Changed in linux-restricted-modules-2.6.20:
importance: Undecided → Wishlist
Revision history for this message
Bryce Harrington (bryce) wrote : linux-restricted-modules-2.6.20 is obsolete

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

Changed in linux-restricted-modules-2.6.20:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.