Quote:
Originally Posted by yougene;
Another related question though. How do I manage modules if I want to compile multiple kernels? Having to compile and reinstall all the modules after every time you try out a new kernel can't be the most practical way out there.
|
I know this is an old thread but I though I would post an answer to this question in case other people stumble upon it.
Basically, if you are booting to multiple versions of the same kernel version you need to make sure you enable the suffix option in the config. It is under 'General Setup'->'Local Version'. This is used in the config for the smp kernel of Slackware 12. What happens is the your modules will install to /lib/modules/'kernel version'suffix, so for the 2.6.21.5-smp config in Slackware 12 '-smp' is what is under 'Local Version' and the modules are installed to /lib/modules/2.6.21.5-smp. If you are only using actually different kernel versions you don't need to worry about this.
Another thing that is important to keep in mind is that you might want to enable module versioning. This will help 3rd party modules to work across different kernel builds. Even still you might have to resort to some manual tricks to get some of them to play nicely (eg. nvidia).
Finally, you can also modify the EXTRAVERSION var in the kernel Makefile, so instead of using '5' you could use '5a' so the kernel would compile to 2.6.21.5a for instance.
Oh, and don't worry too much if you start getting errors at boot time because the system is trying to load modules that are now built in to the kernel. You can modify /etc/rc.d/rc.modules if you want to change this.