LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Loss of modules after 2.6 kernel upgrade (https://www.linuxquestions.org/questions/slackware-14/loss-of-modules-after-2-6-kernel-upgrade-129919/)

Sarno 12-29-2003 06:43 PM

Loss of modules after 2.6 kernel upgrade
 
Ok I've upgraded from 2.4 to 2.6 following this guide: durham.randomwire.com/kernel.php with the exception of copying over my old .config file.

The problem is after the upgrade, The number of modules that load on startup has gone from 29 to 5. Notably network drivers and sound are gone.
I'm very new to this and as far as I know magical gnomes made those modules load before. How can I get them to load again?

HappyTux 12-29-2003 07:22 PM

Re: Loss of modules after 2.6 kernel upgrade
 
Quote:

Originally posted by Sarno
Ok I've upgraded from 2.4 to 2.6 following this guide: durham.randomwire.com/kernel.php with the exception of copying over my old .config file.

The problem is after the upgrade, The number of modules that load on startup has gone from 29 to 5. Notably network drivers and sound are gone.
I'm very new to this and as far as I know magical gnomes made those modules load before. How can I get them to load again?

I see no mention of the new module-init-tools that are needed for the new kernel module format in that guide you may want to check on the proper way to install them in slackware.

Shade 12-29-2003 10:51 PM

If he's using slack 9.1, the modinit tools are already included as part of the distro.
It's 2.6.0 "ready".

Now, to Sarno --

Each kernel version you compile will have its own kernel modules. It's likely that you didn't compile everything you needed as modules, or compiled some of it into the kernel.
You see, the kernel has two ways of dealing with drivers... The first method is to compile them directly into the kernel. When you boot, they're in there.
The second way is that it can load them as kernel modules -- inserted or removed from the kernel on a per-need basis.
With the stock 2.4.22 kernel, most everything is done in the modular fashion, making it easy for the one kernel to work on many different systems.

Your old kernel modules are still there, just reserved in /usr/lib/modules/2.4.22 instead of /usr/lib/modules/2.6.0/
2.6.0 needs its own kernel modules, of course.

So, you need to figure out if you compiled in or built as modules all the drivers you needed for the 2.6.0 kernel.

:)

-Shade


All times are GMT -5. The time now is 03:02 PM.