2.6.20-16-generic cannot modprobe nvidia-glx

[gestoned]

Binary package hint: nvidia-glx

This may or may not be related to bug 106434, https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.20/+bug/106434

GPL driver is working nicely. My Nvidia is GeForce MX 4000. This model is supported by the 1.0-96xx driver,
at least according to http://us.download.nvidia.com/XFree86/Linux-x86/1.0-9755/README/appendix-a.html

The closed-source NVidia driver worked perfectly in Mandriva
2006 on this hardware.

I used adept manager to install nvidia-glx which resulted in a download of a new
kernel, 2.6.20-16-generic. I rebooted into the new kernel, then I set
xorg.conf Section "Device" - Driver "nvidia"

and I typed modprobe nvidia. The result was this line:
FATAL: Error running install command for nvidia

Then I tried nvidia-glx-legacy and it works but only at 800x600 at 60Hz. So I
believe I do need nvidia-glx.

I also Googled and looked at
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.20/+bug/106434
but that bug pertains to 2.6.20-15, while I have 2.6.20-16.

[Sitsofe Wheeler (sitsofe)]

Punting from linux-restricted-modules-2.6.22 -> linux-restricted-modules-2.6.20

gestoned:
Thank you for your bug report. This is actually more of a support request than a bug report and you may get a better/faster response using one of the methods described on http://www.ubuntu.com/support/communitysupport . However unravelling what you have done will now take several steps....

Generally speaking by far and away the easiest way of enabling the NVIDIA binary driver in Feisty is by using restricted-manager . The steps are outlined on https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia . However as you are now using the legacy drivers, trying to switch back to nvidia-glx is going to make you run into Bug #106217 .

Can you switch back to the nv driver and then do
sudo apt-get remove nvidia-glx-legacy
You will then have to manually remove the file /lib/linux-restricted-modules/.nvidia_legacy_installed if it exists. Can you then use restricted manager to enable the driver for your card. After rebooting and seeing the original issue can you add the output
sudo sh -x /sbin/lrm-video nvidia
dmesg | tail
dpkg -l linux-restricted-modules-\*| grep ii
dpkg -l nvidia-\* | grep ii
uname -a
to this bug report please?

[Sitsofe Wheeler (sitsofe)]

Oh and can you also indicate whether you've ever attempted to install the NVIDIA binary drivers from a non-Ubuntu repository and which guides you have followed to try and enable the binary drivers in the past?

[gestoned (prudek)]

I did sudo apt-get remove nvidia-glx-legacy
Then I installed restricted manager and I used it to enable NVIDIA propr driver.
I rebooted. I got empty screen so I shut down kdm via /etc/init.d/kdm stop.
Then I tried to "startx" and I got "API mismatch: NVIDIA kernel module version 1.0.7184, and X module version is 1.0.9631", so I looked into /lib/linux-restricted-modules and I found ".nvidia_new_installed" file. I removed that file and tried startx again. X Window started with correct acceleration!

Then I logged into my user account and while the display was 1920x1440 the refresh rate was very poor. Kubuntu configuration revealed I run at 56 Hz and the only other option was 50 Hz. After some experimentation I found that after switching to 50 Hz the monitor appears flicker-free. Somehow, although KDE KControl says that it runs at 50Hz it actually runs at 75 Hz.

Thank you for your help. I still believe that this is an error because a novice would hardly be able to resolve this.

[Sitsofe Wheeler (sitsofe)]

The "bad" refresh rate issue is also mentioned on https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia#troubleshooting and covered by Bug #92599 . The stale file already has bug of its own - Bug #106217 ...

[gestoned (prudek)]

Then you can close this bug report as resolved. Thanks again for your assistance.

[Sitsofe Wheeler (sitsofe)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #106217 and is being marked as such. Please feel free to report any other bugs you may find.