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 setup my laptop with FC2 running kernel 2.6.5 with hostap-drivers, ipw2110 drivers, and smartlink modem drivers as Modules.
I upgraded the kernel to 2.6.7 by compiling the 2.6.7 kernel source.
When I boot into the new kernel, it does not load the hostap, ipw2100, or modem modules that I installed in the previous kernel. They are in /lib/modules/"previous kernel". Modprobe will not work. It can't see the modules.
You have two options. First one will work for sure - compile the modules again, for the new kernel. Second - copy the modules to new kernel directories and try to modprobe them. WIth luck (and kernel compiled with support or module versions) it may work.
Originally posted by Mara You have two options. First one will work for sure - compile the modules again, for the new kernel. Second - copy the modules to new kernel directories and try to modprobe them. WIth luck (and kernel compiled with support or module versions) it may work.
Mara,
I used the first option that you gave because I didn't want to miss any modules (I couldn't remember them all).
I only had three modules that were built external to the kernel.....WHAT IF I HAD LOTS????
I went from 2.6.5 to 2.6.7. Is there anything that I could have done before compiling to transfer all the external modules to the new kernel /lib/modules automatically?
Another thing is it better to install all kernel modules to ONE directory below /lib/modules/<kernel version>/ e.g /lib/modules/<kernel version>/new_stuff to make the transfer easier?
The bast thing I can recommend is to always keep source version of the modules in a safe place. Usually you need external modules only for special hardware (nvidia driver, modems, such things), so the number isn't very high. If you're unlucky and you have a huge collection of them, you need to do everything yourself - I'm not aware of any mechanism that would make the transitions easier.
There's no mechanism to transfer them between versions, either.
You can install the modules in the directories you like, but if they have non-strandard location, you may have problems loading them (I've not tried such a config, just guessing).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.