edgy - nvidia-glx install causes x to fail

Bug #63625 reported by Lee.Tambiah
4
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.17 (Ubuntu)
Invalid
Undecided
Unassigned
xorg (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: nvidia-glx

On using the edgy-beta release I found installing the nvidia-glx and then issuing the command "sudo nvidia-glx-config enable" on restarting X from a reboot for example the x-server fails, and hence no desktop is displayed.

Graphic card is Nvidia Geforce 6800 LE

Lee.Tambiah (flossgeek)
description: updated
Lee.Tambiah (flossgeek)
description: updated
Revision history for this message
Lee.Tambiah (flossgeek) wrote :

I am answering my own question it appears that edgy does not require the command:

Code:

sudo nvidia-glx-config enable

Simply install the nvidia-glx library also make sure nvidia-kernel-common is installed. After installation simply change the xorg.conf file device section and change it to nvidia.

Restart xserver

Code:

ctrl + delete + backspace

Thats it although I had the driver working I was stuck at 75Hz which also occurred in Dapper, a fault of the newer Nvidia Drivers I believe. To get round this issue I simply added _60 to the Screen Section. For Example:

I am displaying my resolution at 1280 x 1024 so i change the modes for that line.

Code:

Modes "1280x1024_60"

Add the _60 to every depth, and restart xserver.

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

do you have linux-restricted-modules-generic installed?

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

sorry, I misread your description..

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

I confirm this bug in nvidia-glx 1.0.8776+2.6.17.6-1 provided in Edgy final release.

When using 'Add/Remove Applications' to install 'NVidia binary X.Org driver', the description suggests "to enable the driver, run sudo nvidia-glx-config enable".

---8<---
# sudo nvidia-glx-config enable
Error: unable to load nvidia kernel driver! Be sure to have installed
the nvidia driver for your running kernel.
--->8---

Note that both 'linux-restricted-modules-common' and 'linux-restricted-modules-generic' are installed.

After manually switching the driver from 'nv' to 'nvidia' in /etc/X11/xorg.conf and restarting X, my BenQ FP731 LCD shows "Out of range" and nothing comes up. What the video driver fails to display is the LCD's native 1280x1024. In Dapper I was able to do CTRL+Alt+KP_+/- and switch to other resolutions as a temporary workaround.

I have 2 solutions to this problem, both involving modification of xorg.conf:

1. Force a specific refresh rate for the problematic resolution at given color depth ("1280x1024_75").

---8<---
Section "Screen"
        Identifier "Default Screen"
        Device "NVIDIA Corporation NV43 [GeForce 6200]"
        Monitor "BenQ FP731"
        DefaultDepth 24
SubSection "Display"
                Depth 24
                Modes "1280x1024_75" "1024x768" "800x600" "640x480"
        EndSubSection
EndSection
--->8---

2. Disable nVIDIA's handling of frequency ranges.

"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."
<http://download.nvidia.com/XFree86/Linux-x86_64/1.0-8756/README/appendix-d.html>

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

Revision history for this message
Rouben (rouben) wrote :

Thanks for your comments. This does not appear to be a bug report as such. We appreciate the difficulties you are facing, but it would make more sense to raise your question at http://launchpad.net/support.

Changed in xorg:
status: Unconfirmed → Rejected
Changed in linux-restricted-modules-2.6.17:
status: Unconfirmed → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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