Upgrading the kernel

**MosX** · 09-22-2004

I can upgrade the kernel (2.4.24 to 2.6.8.1) just fine, but I have a problem with modules. Do I have to edit all the rc files to insert the right modules in and stop the now unnecessary modules from inserting?

**sarumont** · 09-23-2004

You just have to edit your /etc/modules.autoload.d/kernel-2.6 to stop it from autoloading modules that you don't want it to load, or to load modules automatically. This file is read at boot, by the way.

**MosX** · 09-23-2004

Thank you for your reply, but it appears that I have no file of that name in my filesystem. I don't even have the /etc/modules.autoload.d/ folder. Do I have to create it? I probably should make it clear that it's a fresh install of Slackware 10.

**sarumont** · 09-23-2004

Do you have a /etc/modules.autoload?

Slack is really throwing me some curveballs tonight.

**MosX** · 09-23-2004

I think I do. I'm gonna check in about two minutes. Does that file deal with stopping modules from inserting too though? For instance, in some of the rc files in the /etc/rc.d/ directory, modules from the 2.4.22 module folder are added. It seems like the only way to make sure everything is running smoothly is to edit out all the modprobe statements in ALL the rc files.

**U-Turn** · 09-23-2004

No /etc/modules.autoload in Slack.

**will1127** · 10-21-2004

this is a little old but i use to use slackware 10 you want to go to /etc/rc.d/rc.modules and maybe even rc.local slackware uses bsd stile bootscripts thats y its like that

**Lenard Spencer** · 11-14-2004

The folder you're looking for in Slack is actually /etc/rc.d, if this helps.

Thread Tools

Display

Upgrading the kernel

Posting Permissions