annoying modprobe errors
 

Hello everyone,

I've been running 2.6.0-test3 kernel on my slack 9 box for a while now and everything is okay except that when I boot up I keep getting modprobe errors like

modprobe : FATAL: <some_module> already loaded in kernel

or something to that effect. A ton of them just scroll past the screen for a second and then the machine proceeds to boot normally. I can't seem to find the script that's trying to load these modules. I've looked at modprobe.conf and modules.conf and found nothing. Any ideas on what's going on? Thanks in advance.

its possible that your kernel has drivers compiled into it and that you are also trying to load them as modules.

Is this a custom compiled kernel? Do you have the .config file that was used to create it?

Where do you get the errors? At the beginning of the boot process? Maybe your initial ramdisk has drivers in it that are compiled into the kernel or that you are trying to load as modules?

-K

Yes, I wanted to test out the new kernel so I downloaded the source and did the kernel compile thing. I still have the .config file. The errors come closer to the end of the boot up process. It's just before slackware does all the font-cache and ldconfig stuff. Thanks for the reply

Quite frankly, I can't remember WHAT Slack does at boot time. However, could you post some of the actual modprobe errors?

-K

That's another small problem. I can't copy and paste the error messages because they come up during the boot up. Besides doing a dmesg I haven't been able to find these errors logged anywhere.

DISREGARD THIS POST.

That's another small problem. I can't copy and paste the error messages because they come up during the boot up. I haven't been able to find these errors logged anywhere. Doing a dmesg doesn't show the errors generated during bootup either.