Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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 just updated my kernel from 2.4.20-31.9 to 2.6.14.4 for rh9. i am running into problems loading all modules. when i run lsmod, it'll list a few modules that did run from boot. I need the module nls_cp437.ko (and some other modules) to load on boot so i can mount vfat partitions. I can load the module manually with insmod but was wondering why doesn't the module load on boot. I checked modules.dep and found the module listed so im feeling kinda stuck now. when i reboot back into 2.4.20-31.0, everything seems to work fine, all modules loaded.
after i compiled and booted into 2.6.14.4, alot of modules failed to load (ie 8139cp.ko driver for my network card), because modprobe somehow did not work correctly. I had to compile the driver into the kernel to get around this problem. maybe this has something to do with why not all the modules load during boot??
depmod -V returns "module-init-tools 3.2" so i think my modprobe is up-to-date? ?
i didnt use rpm cause i couldnt find one, i did run /sbin/depmod -A after the install. Yes, the new kernel upgrade did provide new modules, all the modules in 2.6 end in .ko where as 2.4 ended in .o i believe. The problem is that some modules (ie the usb modules) do load yet other modules (ones required by vfat) failed to load on boot. From my understanding, modules do not load unless they are required. During boot, some modules failed to load, and i am not sure why that is because i can manually load them with insmod (module). On the same note, how do i access the log that shows which modules loaded correctly. I checked the boot.log and dmesg, both logs dont show the same information shown during the boot when the kernel tries to load the modules.
I don't know of such a log file to see what modules loaded. In SuSE, there is a file called /etc/sysconfig/kernel which can be edited to add modules to load on boot. You may have a similar file in rh9.
SuSE also has a file called /etc/init.d/boot.local in which the user can add modules to load on boot. The syntax is a bit different in the two files, but the end result is the same. You may have a file similar to that as well.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.