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 have compiled the kernel 2.6.24.3 and installed it. When I boot to the new kernel it looks like it's still using the modules from the old kernel (2.6.21.5) I look in /etc/rc.d and I don't see the new kernel modules only the old ones. I installed this kernel because I'm trying to install Intel Pro wireless 3945 driver and to do that I needed a newer kernel with mac80211. What do I need to do to make the new modules work.
Did you 'make modules' and 'make modules_install' after the 'make'? I like to edit the Makefile and change the 'EXTRAVERSION=' to a descriptive value yet unique. That way you will not have a problem identifying.
Did you 'make modules' and 'make modules_install' after the 'make'? I like to edit the Makefile and change the 'EXTRAVERSION=' to a descriptive value yet unique. That way you will not have a problem identifying.
BTW, 'softmac' should be in '/lib/modules/2.6.21.5-smp/kernel/net/ieee80211/softmac/' as part of the 2.6.21.5-smp stock kernel.
Oh ok cool thanks. I will see if I can get that to work using the ipw3945 driver with my Intel Pro Wireless 3945 ABG in my laptop.
If that doesn't work I will try to compile the 2.6.24.3 kernel again.
From that how to I followed I didn't use a Slackware kernel config file so maybe I hosed something up.
Oh ok cool thanks. I will see if I can get that to work using the ipw3945 driver with my Intel Pro Wireless 3945 ABG in my laptop.
If that doesn't work I will try to compile the 2.6.24.3 kernel again.
From that how to I followed I didn't use a Slackware kernel config file so maybe I hosed something up.
I have compiled and installed the kernel 2.6.24.4 after using a config file for Slackware. It already has the mac80211 and iwl3945 driver but still can't get wireless to work but I guess that is for another post maybe in in the wireless threads.
Did you make a /etc/rc.d/rc.modules-$(uname -r) file? If your modules are not automatically loaded you should specify them in that file. If the file does not exist it will check /etc/rc.d/rc.modules. Of course if you have /etc/rc.d/rc.modules.local it will run that first regardless of you kernel.
Did you make a /etc/rc.d/rc.modules-$(uname -r) file? If your modules are not automatically loaded you should specify them in that file. If the file does not exist it will check /etc/rc.d/rc.modules. Of course if you have /etc/rc.d/rc.modules.local it will run that first regardless of you kernel.
No I didn't make that file. I will have to take a look at that.
Should I just make a /etc/rc.d/rc.modules.local
How do I go about specifying my modules in /etc/rc.d/rc.modules-$(uname -r) ?
No I didn't make that file. I will have to take a look at that.
Should I just make a /etc/rc.d/rc.modules.local
How do I go about specifying my modules in /etc/rc.d/rc.modules-$(uname -r) ?
Don't make a rc.modules.local file unless you want that to be run for every kernel regardless of its version.
You just load the modules you need in the rc.modules-$(uname -r) file. Take a look at one of them and I am sure you will see what you need to put in there. I suggest just copying one of the current files and then modifying it (take out/comment out the modules you don't need and uncomment/add the modules you do need).
If you want your new file to be the default rc.modules file in case one is not found for a kernel's version ( $(uname -r) ) then symlink rc.modules to your new file.
Don't make a rc.modules.local file unless you want that to be run for every kernel regardless of its version.
You just load the modules you need in the rc.modules-$(uname -r) file. Take a look at one of them and I am sure you will see what you need to put in there. I suggest just copying one of the current files and then modifying it (take out/comment out the modules you don't need and uncomment/add the modules you do need).
If you want your new file to be the default rc.modules file in case one is not found for a kernel's version ( $(uname -r) ) then symlink rc.modules to your new file.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.