how to auto modprobe on boot?

dialate · 06-10-2004, 01:04 AM

I (finally) got xserver to start after installing the nvidia drivers for my FX5900, but it requires x crashing to console, logging in as root, "modprobe nvidia", logging in as my regular account, and then "startx". Is there a way to stick the modprobe command in a config so that it boots smoothly into x?

I've tried chucking /sbin/modprobe nvidia in a few config files, but I guess thats too BSD-ish for Mandrake's liking, and usually just ends up associating nvidia with "/sbin/modprobe" or some such nonsense.

Pete M · 06-10-2004, 01:44 AM

dialate

Under Redhat you enter /sbin/modprobe nvidia into '/etc/rc.d/rc.local'

If this file exists in Mandrake I guess it will have the same effect

Pete

indeterminate · 06-10-2004, 03:30 AM

You can also use the /etc/modules.conf file. Just add a line like "alias /dev/nvidia* nvidia" and it should automatically load it during init. At least, that's how mine does it.

steffen_b · 06-10-2004, 06:38 AM

depends on which kernel you are running.

/etc/modules => 2.4
/etc/modprobe.preload => 2.6

Or an alias in /etc/modules.conf or an alias in /etc/modprobe.conf

As you like it. If you have Mdk 10, i think there is a tool from mandrake that syncs the entries from kernel 2.4 and 2.6, just don't remember the name, so /etc/modules should work out.

Steffen

dialate · 06-10-2004, 06:11 PM

no go.

These give errors like WARNING: /etc/modprobe line 8: ignoring bad line starting with '/sbin/modprobe nvidia'

I dug through my log files and found a couple of fishy errors.

In the logs it says something about not being able to find screens with a valid configuration.

Also:
nvidia: no version for "strict_module" found: kernel tainted
nvidia: module license 'NVIDIA' taints kernel

Hmm I installed the kernel sources from CD......and still odd that it will start with a modprobe.

steffen_b · 06-10-2004, 06:30 PM

You have to put it in /etc/modules and there only the module name ! no modprobe or sth else.

Then it should work.

Steffen

dialate · 06-10-2004, 07:11 PM

Yeah, that was an earlier part of the log, I did eventually figure out that it should be module name only after reading through the /etc/rc.d/rc.modules script.

No matter though, I reinstalled the driver and it worked.

Apparently renaming the install file breaks it. I just ran it with regular name, and everything works. The thing must be recursive or something.

Thanks for help! Now for some wolfenstein goodness