SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
Distribution: Redhat v8.0 (soon to be Fedora? or maybe I will just go back to Slackware)
Posts: 857
Rep:
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?
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
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.
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.