Fatal "modprobe" error with nvidia drivers in Gentoo

Penguin of Wonder · 01-07-2006, 12:59 PM

After compiling my own kernel and installing a fresh version Gentoo linux, i've downloaded Xorg and installed ok. Now i'm trying to install the nvidia drivers for my Nvidia 6200 8x AGP graphics card. I'm following this guide provided by Gentoo to do it. After I use "emerge" to download and install the drivers, it says to use "modprobe" to do something with the kernel and the drivers, what "modprobe" does, im not real sure. My problem is after performing modprobe I get the following error message:

Code:

FATAL: Error inserting nvidia (/lib/modules/2.6.14-gentoo-r5/video/nvidia.ko): Unknown symbol in module, or unknown parameter (see dmesg)

That bit of information dosen't really mean much to me, but i'm afraid it means I haven't compiled my own kernel with the right parameters to let Linux instert the module in for me. The beginning of that guide discusses the proper parameters that have to be compiled in the kernel for this work. Dmesg goes on to say:

Code:

nvidia: module license 'NVIDIA' taints kernel.
nvidia: Unknown symbol register_ioctl32_conversion
nvidia: Unknown symbol unregister_ioctl32_conversion

This is very frustrating because i've been trying to get my new computer up and going for about a week now with Linux and i've already made a sacrafice to get this far. Does anyone know what my problem is? I'd be more than gratefull if someone had some advice. Thank you in advance.

Centinul · 01-07-2006, 02:18 PM

I run Gentoo Linux on my desktop and I've run into the same problem before. You are in luck the solution should be relatively easy. Like the Gentoo instructions say, every time you compile your own kernel you have to make sure you re-emerge nvidia-kernel to ensure that the nvidia drivers work correctly. The last time I ran into this problem, I DID NOT compile my kernel correctly. If I remember correctly for some reason I didn't create the right symlink to my kernel that I compiled. Once I compiled it correctly and ran "emerge nvidia-kernel" again everything was fine and I went on my way.

Also make sure that you put "nvidia" in "/etc/modules.autoload.d/kernel-2.6" file that way it will autoload when you boot up your machine. Good luck.

::EDITED FOR CLARITY::

Napalm Llama · 01-07-2006, 02:31 PM

"modprobe" is the command that inserts modules into the kernel, so it can use the goodness within. In your case, "modprobe nvidia" simply loads the nvidia driver, ready for use.

You shouldn't have to copy the nvidia module anywhere, but like Centinul said, if

Code:

ls -l /usr/src/linux

doesn't point to the exact kernel you configured, or worse still if it doesn't exist, you need to

Code:

cd /usr/src
ls -l
rm linux
ln -s your_kernel_directory_here linux

and then re-emerge nvidia-driver.

FYI, the same applies to any other modules you've got installed with Portage - I "emerge nvidia-kernel alsa-driver" every time I reconfigure my kernel!

Penguin of Wonder · 01-07-2006, 03:11 PM

Alright, thanks for the replys guys (and gals, maybe). I'm off to learn how to recompile my kernel and reload my modules. Thanks!

Penguin of Wonder · 01-07-2006, 11:12 PM

I reconfigured my Kernel, and that didn't help. Assuming I did that right, is there any other reason that it might not work?

Napalm Llama · 01-08-2006, 07:14 AM

You reconfigured the kernel... but did you re-emerge nvidia-kernel?

If not, do this:

Code:

emerge nvidia-kernel  # Rebuilds nvidia module for your new kernel
modprobe -r nvidia  # Removes old nvidia module from your kernel (if it's there)
modprobe nvidia  # Inserts new nvidia module into the kernel

This is assuming that you're running the kernel that's at /usr/src/linux. If you've reconfigured it, you need to reboot into the new version before running that code.

If it still doesn't work, post your /usr/src/linux/.config file here - we'll take a look and see if there's anything that needs changing.

Also, it would help to know what model of graphics card we're dealing with here

Penguin of Wonder · 01-10-2006, 03:29 PM

I've since reinstalle Ubuntu because of my frustration with Gentoo. Ubuntu is VERY easy to use, and not that Gentoo was really that hard, but I needed my computer back lol. I can't go forever without this thing. Your post though, along with what i've learned since trying unsucessfuly to install Gentoo twice (yes I used the guide both times) makes me want to try again. Perhaps this weekend I will look into that. One or maybe two questions though about the Gentoo install:

If your not really sure what to enable and not enable in your custom kernel gentoo lets you create, is it best to just use 'genkernel'?

If I don't know what to disable in my new Kernel, because I don't need it, so I just don't get rid of it, am I really helping anything?

Thanks for the reply though!

Napalm Llama · 01-11-2006, 08:05 AM

Hmm, I would advise trying genkernel first to see if that produces something that'll work. I tried it first (because I was scared of making my own kernel!) but whatever it was that it spat out, it wasn't bootable. So I bit the bullet and hand-configured my own kernel - and now I've never looked back!

I'm a fan of monolithic kernels - if you lsmod on my box, you'll see "nvidia" and some alsa stuff, but nothing else. I have actually been known to physically recoil from the reams of output lsmod gives on some other distros...

For most things in-kernel, enabling unnecessary options won't hurt. Don't quote me on that (there might be things I can't think of at the moment) but in general, and especially in the Drivers section, I would say it's quite a good rule of thumb. (But don't forget lspci)

I'm assuming you're using the make menuconfig method - if so, press H over the option you're not sure about (or move the cursor right to select the Help button) - some things don't have help text attached, but most things do and I still rely quite heavily on the descriptions provided.

If the option is marked "Experimental", the obvious thing would be not to enable it unless you know you need it.

Finally, you won't always get your kernel right first time. Pay attention to what it says during startup (so disable any bootsplash you might have) and have a look through dmesg if it boots far enough for you to type that in.

If you're still stuck, LinuxQuestions is always open - as are the excellent Gentoo Forums! Don't give up - Gentoo is the best distro of the best OS I've ever used, and I don't intend to switch any time soon.

RemusX2 · 01-11-2006, 09:42 AM

I've hard a the same problem (maybe similar) before... I was having troubles because I had the symlink in /usr/src pointing to a different kernel then the one I was actually running. This may be irrelivent to your problem, but keep it in mind.

Penguin of Wonder · 01-11-2006, 10:59 AM

Well, Napalm Llama, even if your answers don't work (I don't know, I haven't tried them yet) you are atleast very inspirational! This weekend when I have some spare time I beleive I'm going to try to reinstall Gentoo Linux on my desktop. I think i'll compile my own kernel though, the last time I did it, it worked and it booted, I just couldn't get the nvidia module to load in it. But this time i'll be more carefull about how I do it.

Penguin of Wonder · 01-11-2006, 11:00 AM

Quote:

Originally Posted by RemusX2

keep it in mind.

Will do. Thank you.

Napalm Llama · 01-11-2006, 04:16 PM

Well, I do try

Good luck with your Gentooage!