mattge
asked on
Module Problem
I just installed Slackware 3.2 using the kernel 2.0.29. After configuring the the kernel I built it using the following commands.
make mrproper
make config
make depend
make clean
make zImage
make modules
make modules_install
depmod -a
make zlilo
After rebooting I get the following errors.
***Unresolved symbols in module raid.o
ncpfs.o
appletalk.o
ipx.o
misc.o
dlci.o
linear.o
Why is the kernel trying to use these modules and how do I resolve the unresolved symbols???
make mrproper
make config
make depend
make clean
make zImage
make modules
make modules_install
depmod -a
make zlilo
After rebooting I get the following errors.
***Unresolved symbols in module raid.o
ncpfs.o
appletalk.o
ipx.o
misc.o
dlci.o
linear.o
Why is the kernel trying to use these modules and how do I resolve the unresolved symbols???
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I suspect that these modules were installed by Slackware itself.
You didn't compile all of them in your own kernel, but these files are still in your /lib/modules/2.0.29 hierarchy.
When Slackware boots up, it does a depmod -a . It finds some of the modules, but sees that they don't match your new kernel.
Remove all files from the /lib/modules/2.0.29 hierarchy and reinstall (Same procedure as you originally did, but replace the `make zImage' by `make zlilo').
(Note, to be on the safe side, make a copy of them and keep a rescue disk handy.)
Also, Check the /etc/rc.d/rc.modules file to make sure no unwanted modules are loaded.
You didn't compile all of them in your own kernel, but these files are still in your /lib/modules/2.0.29 hierarchy.
When Slackware boots up, it does a depmod -a . It finds some of the modules, but sees that they don't match your new kernel.
Remove all files from the /lib/modules/2.0.29 hierarchy and reinstall (Same procedure as you originally did, but replace the `make zImage' by `make zlilo').
(Note, to be on the safe side, make a copy of them and keep a rescue disk handy.)
Also, Check the /etc/rc.d/rc.modules file to make sure no unwanted modules are loaded.
ASKER
I do have it set to use modules if that is what you meant. I also have it set not to use the CONFIG_MODVERSIONS.
Matt G