Click to See Complete Forum and Search --> : Kernel module problems


kyutums
11-13-2001, 02:59 AM
After tinkering with the kernel via "make xconfig", I get the ff. error message upon loading the new kernel. But still, my new kernel works. Aside from the ff. messages, everything seems okay. Should I be worried about anything here?

Thanks! :)

depmod: *** Unresolved symbols in /lib/modules/2.2.14-5.0/net/cops.o
depmod: *** Unresolved symbols in /lib/modules/2.2.14-5.0/net/ltpc.o
depmod: *** Unresolved symbols in /lib/modules/2.2.14-5.0/block/raid5.o
depmod: *** Unresolved symbols in /lib/modules/2.2.14-5.0/ipv4/ip_masq_autofw.o
depmod: *** Unresolved symbols in /lib/modules/2.2.14-5.0/ipv4/ip_masq_cuseeme.o
depmod: *** Unresolved symbols in /lib/modules/2.2.14-5.0/ipv4/ip_masq_ftp.o
depmod: *** Unresolved symbols in /lib/modules/2.2.14-5.0/ipv4/ip_masq_irc.o
depmod: *** Unresolved symbols in /lib/modules/2.2.14-5.0/ipv4/ip_masq_mfw.o
depmod: *** Unresolved symbols in /lib/modules/2.2.14-5.0/ipv4/ip_masq_portfw.o
depmod: *** Unresolved symbols in /lib/modules/2.2.14-5.0/ipv4/ip_masq_quake.o
depmod: *** Unresolved symbols in /lib/modules/2.2.14-5.0/ipv4/ip_masq_raudio.o
depmod: *** Unresolved symbols in /lib/modules/2.2.14-5.0/ipv4/ip_masq_user.o
depmod: *** Unresolved symbols in /lib/modules/2.2.14-5.0/ipv4/ip_masq_vdolive.o
depmod: *** Unresolved symbols in /lib/modules/2.2.14-5.0/ipv4/ip_vs_lc.o
depmod: *** Unresolved symbols in /lib/modules/2.2.14-5.0/ipv4/ip_vs_rr.o
depmod: *** Unresolved symbols in /lib/modules/2.2.14-5.0/ipv4/ip_vs_wlc.o
depmod: *** Unresolved symbols in /lib/modules/2.2.14-5.0/ipv4/ip_vs_wrr.o
depmod: *** Unresolved symbols in /lib/modules/2.2.14-5.0/misc/appletalk.o
depmod: *** Unresolved symbols in /lib/modules/2.2.14-5.0/misc/emu10k1.o
depmod: *** Unresolved symbols in /lib/modules/2.2.14-5.0/misc/ipx.o

twen
11-13-2001, 11:38 AM
what did you do exactly after make xconfig?
did you do
make modules
and
make modules_install
if so did you get any error messages?

kyutums
11-13-2001, 12:57 PM
Yup.

I put all the commands in one line "make dep; make clean; make bzlilo; make modules; make modules_install; halt ;". The kernel compiles a long time on my system (a Pentium 133 with 16MB RAM) so I just put the commands in one line and ordered it to shutdown after compiling. I sense a "That's the wrong way!" sermon coming soon. :)

[ 13 November 2001: Message edited by: kyutums ]

twen
11-14-2001, 07:58 AM
I've never used zlilo because I've heard that it dosen't always work
what I do is; after make modules_install
cp System.map /boot/System.map-xxx
cp arch/i386/boot/bzImage /boot/vmlinuz-xxx
then you edit lilo.conf found in /etc/ to include the new kernel image whilst keeping the original in case things don't work.
after editing lilo.conf run /sbin/lilo to install the new lilo file in the mbr
another thing to consider is 1) did you do a make mrproper before xconfig
2)it may be a wrong option picked at the xconfig stage -make any sense?? :confused:
can't express myself today!