Subject: RE: Unresolved (module) symbols at boot time
From: Edward Lewis (lewis@tislabs.com)
Date: Fri Feb 16 2001 - 11:40:00 MST
Thanks - I think this solved my problems. I did a clean rebuild of the
kernel but made sure /lib/modules was empty before the make
modules_install. After that the complaints went away.
The reason for the "I think" is that I removed some modules that I didn't
really need in the rebuild. I did keep the IPv6 and it seems to be working
fine.
At 6:32 AM -0500 2/15/01, Isak Lyberth wrote:
>
>
>When you make the modules and install them they are copied to
>/lib/modules/kernelnumber.
>The 'make modules_install' doesent delete the old modules and thats why
>there are some unresolved modules.
>Because old modules are there.
>Here is what i did:
>First make the kernel
>make modules
>move the /lib/modules/kernelnumber folder to somewhere safe
>make modules_install
>copy 'System.map' from the source folder to /bin/System.map-kernelnumber
>point the link '/bin/System.map to the new System.make-kernelnumber file
>
>
>Do not remove the modules for the original kernel (in CS 1.2.1 thats
>kernel 2.2.15) as it seems that it uses those for some bootup process
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis NAI Labs
Phone: +1 443-259-2352 Email: lewis@tislabs.com
Dilbert is an optimist.
Opinions expressed are property of my evil twin, not my employer.
This archive was generated by hypermail 2a24 : Fri Feb 16 2001 - 11:45:29 MST