nvidia 4191 drivers/nv_check.sh error

niknah · 12-31-2002, 12:09 PM

you might have an old version of nv_check.sh, where did u get this file from? a newer version I looked at doesn't even have this message.
anyways you can always edit the nv_check.sh and comment out the "exit" line below that message.

artaois · 12-31-2002, 04:13 PM

ok, I thought that I was going to feel really dumb after getting a newer version of nv_check.sh - but now I don't feel dumb, just more frustrated

I got the newest version I could find listed in the nvidia forums, it finds the GLX no problem, but the rest of the output is now different:

Quote:

First lets make sure you don't have the old modules still present
by mistake...
Checking /usr/X11R6/lib/modules/extensions/libglx.a...
Checking /usr/X11R6/lib/modules/extensions/libGLcore.a...
You don't appear to have any conflicting older drivers. Now lets check
if the new driver files are in place...
Checking /usr/X11R6/lib/modules/drivers/nvidia_drv.o...
Checking /usr/X11R6/lib/modules/extensions/libglx.so...
Checking /usr/lib/libGL.so...
libGLcore.so.1 => /usr/lib/libGLcore.so.1 (0x4005c000)
Checking /usr/lib/libGLcore.so.1...
All the files seem to exist. Now I'm going to see if your kernel
module is loaded correctly...
the NVdriver kernel module does not seem to be loaded. The 3D
drivers will not work without it...please compile it for your
kernel, set it up to insert the module on boot, then run
this script again.
Remember if you are having trouble compiling the module,
try adding -D_LOOSE_KERNEL_NAMES to the Makefile.

UT2003 is working fine here, so I don't understand the error message very well.

and as far as compiling the module: remember - I installed the drivers from the source rpms...

niknah · 12-31-2002, 09:52 PM

try...

/sbin/modprobe NVdriver

...and see if any error messages come up

artaois · 01-01-2003, 04:12 AM

$ /sbin/modprobe NVdriver
modprobe: Can't locate module NVdriver

:-/

(your patience with me is pretty amazing, you know

)

niknah · 01-01-2003, 11:18 AM

it looks like you don't have the nvidia kernel module, what nvidia rpms have you installed?
there should be one like NVIDIA-kernel-xxxx
anyways type...

rpm -q -l NVIDIA-kernel

...to see if you've got it.

artaois · 01-01-2003, 12:00 PM

hehe - check this one out:

Quote:

$ rpm -q -l NVIDIA-kernel
package NVIDIA-kernel is not installed

$ rpm -qa | grep NVIDIA
NVIDIA_GLX-1.0-4191
NVIDIA_kernel-1.0-4191

you do realize that i'm about ready to give up?

I mean, it's WORKING, except for the minor glitches, but i'm asking myself if it's time to try another distro........

niknah · 01-01-2003, 09:18 PM

use...

rpm -q -l NVIDIA_kernel

like with underscore instead of minus.
and type /sbin/modprobe xxx where xxx is the file that's installed in /lib/modules/......

...so you can start your X windows and it works? then i'm going the wrong direction!
other than nv_check.sh, what doesn't work that you're trying to fix??

Aussie · 01-01-2003, 09:59 PM

Nvidia changed the name of the kernel module from NVdriver to nvidia in the latest release. You can download a working nv_check here.

artaois · 01-02-2003, 04:39 AM

great - that nv_check works great - tells me everything is installed correctly - that still leaves me with the following problems:

when i login via shell (no graphic login anymore) startx won't work - i have to kdm from root, THEN i can get x up and running

I got the latest kernel from RHN but nvidia won't work at all with it (no screens.... so x won't start) - so i'm forced to continue with 2.4.18-18.8.0 even though 2.4.19 IS installed

*sigh*

Aussie · 01-02-2003, 05:08 AM

Ok, just download the nvidia kernel file in .tar.gz format and build it against your new kernel, you'll need the kernel matching headers/source for your new kernel installed first. To get to a graphical login try putting the command to start kdm in /etc/rc.r/rc.local

artaois · 01-02-2003, 05:35 AM

ummm - there is no /etc/rc.r/ directory..........

Aussie · 01-02-2003, 05:45 AM

Sorry, that should read rc.d, not rc.r.

artaois · 01-02-2003, 06:17 AM

ok - i did that - no change

when i get the login prompt in the shell, if i don't login within 10 seconds or so, i get a "bluescreen" with the message that the xserver couldn't start, and it asks me if i want to go into the configure program... the configure program just brings me into the place where i choose a soundcard - and on the bluescreen the "buttons" that should say "yes" or "no" have some strange ascii characters instead of yes or no.....

artaois · 01-02-2003, 06:42 AM

ok - i got x working in the new kernel - but:

1. still get shell login
2. as root i can no longer start kdm (that's a new problem)
3. when i type gdm i get the message that gdm is already running (old problem)
4. logging in as user lets me startx - but i'm stuck in kde (i prefer gnome in RH, because kde screwed up when i upgraded to 3.03)

Aussie · 01-02-2003, 06:45 AM

I always boot to text login and do "startx", I've found that it makes things easier when you have X problems.
You might want to have a loot at the following page, it has some info on RH8 and booting into X, http://www.redhat.com/docs/manuals/l...t-xconfig.html