Nvidia driver does not work =(

[niteshadw]

I'm having some REAL problems with installing the Linux drivers from Nvidia.com. I have Linux Red Hat 8.0, Leadtek GeForce 3 Ti 500.

Before I found this site, I went to Nvidia.com, downloaded NVIDIA_kernel-1.0-3123.rh73up_2.4.18_10.i386.rpm and NVIDIA_GLX-1.0-3123.i386.rpm Then I followed the instructions. It said all went fine, however when I again turn on the computer, I get an error message:
INIT: Ia "x" respaqning too fast: disabled for 5 minutes

After 5 minutes, samething...so the Xserver won't load at all...well this was in Red Hat 7.3. In 8.0 it fixes itself - uses the backup files created during the insalltion of above rpm files. So its all back as it was = no nvidia drivers.

I tried following this thread http://www.nvnews.net/vbulletin/showthread.php?s=&threadid=2563


After compiling the source, I attempt to install, however I get an error saying that the kernel or glx has a newer version installed than the one I'm trying to install. So I try to uninstall using -e or -Uvh but it does not work...I don't remember the message.

Then I finally install the NVIDIA_kernel-1.0-3123.rh73up_2.4.18_10.i386.rpm and NVIDIA_GLX-1.0-3123.i386.rpm and tried to edit /etc/X11/XF86Config Maybe I should try /etc/X11/XF86Config-4 too...but when I made some changes with the GUI thing, it edited /etc/X11/XF86Config not -4 so I don't think it will make a difference.


Does anyone know how to fix this problem? I'm in school now so I don't know all the error messages but I'm trying to be as specific as I can. I have to kill some class time typing this too...
:D

[bwkaz]

Well, seeing as you're using RH 8, and because of that, you need to either use the .src.rpm or the .tar.gz files, you might want to try the .tar.gz files. They don't care if the package has been installed once already (which is the problem you were running into when you tried to install it the second time -- there was already an NVIDIA_kernel package in rpm's database, so it wouldn't let you install it twice -- and it apparently didn't know that you had a newer version), they'll just overwrite the files they need to overwrite. Normally this isn't such a good idea, but it might help in this case.

If you don't want to, you can instead do an rpm -qa | grep NVIDIA to get a list of packages that contain NVIDIA in their names. Then rpm -e <whatever it printed> should remove them all. You'll have to either remove the GLX package and then remove the kernel package, or remove them both at the same time. My guess is that this is why the rpm -e failed -- the GLX package is dependent on the kernel. Or, it might be that the RPM database doesn't use the full filename as the package name, but just a substring of it (usually). The rpm -qa | grep ... command should tell you the name that the RPM database uses for the package.

Installing a kernel built for RedHat 7.3 onto a RedHat 8.0 system is guaranteed to not work. You really don't have a choice but to go from source -- either .src.rpm or .tar.gz.

[niteshadw]

I think I got it to work...I see the nvidia logo and in the display manager, I see nvidia as the driver...however when I try to run the screen saver which I suppose requires GL, since its in (GL) next to the screen saver name. Its a little sluggish, infact it seems to be same before installing the drivers. I see there is an option in the display manager, next to the video card that says; "Enable Hardware 3D Acceleration", hoever I am unable to check it....

Any ideas what is wrong...I don't have a game under linux to see if there are any changes...but I would like to get the card to work as it was designed to work...thanks

[bwkaz]

You can't check "enable 3D" because the wonderful ( :rolleyes: ) GUI app that has that in it doesn't have a clue how to use 3D with the nVidia drivers.

If you've made all the appropriate changes to your X config file, then 3D should be working. You can always install TuxRacer and run it -- if you get more than 1-2 fps, you have 3D enabled.

[ernestus]

I expect this helps:
As nvidia driver docs say, some times the soft links don't point to the correct libraries and one gets mesa running instead. The driver docs also explain how to mend that.

E.