Go ahead and try the 2.4 kernel anyway.

These errors are usually caused by modules compiled for a different kernel
version than you are running.  On my firewall, I had gotten a 2.2.18pre21
source from the debian tree.  However, it wouldn't load the ip_masq [uerade]
modules.  It had unresolved symbols.  So I chucked that whole kernel source,
and recently downloaded a 2.2.18-1 source.  This one worked fine.

When you run 'make modules_install' your system will copy the compiled
kernel modules in to:
/lib/modules/<kernel-version>/

So you can have 2.2.14 installed
source: /usr/src/kernel-2.2.14  (or some such)
lib: /lib/modules/2.2.14/

And 2.4
src: /usr/src/linux-2.4
lib: /lib/modules/2.4

This will allow you to have multiple versioned kernels available to your
boot sequence.  The kernel will look in the appropriate versioned directory
for the proper modules.


For your current situation, ask yourself, do you need those modules?
ipx?  probably not, unless you know you want it
cops and ltpc?  I don't know what they are, but I've never used them.

If you don't need them, delete (or move) them from their location in the
/lib/modules/2.2.16 directory.  Then delete (or move)
/lib/modules/2.2.16/modules.dep.  Then run 'depmod' to create a new
modules.dep.  

Cory


-----Original Message-----
From: Gregor Diseth [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 19, 2001 2:54 PM
To: [EMAIL PROTECTED]
Subject: [EUG-LUG:384] Kernel compile question.


Slackware 7.1, 2.2.16.

For the first time, I'm ditching the training wheels of the canned
kernels, and I'm compiling my own, in order to customize it to my hardware
and to reduce bloat/memory requirements and to speed boot time.

When I boot from the newly compiled kernel, I get the following messages
during the boot:

depmod: *** Unresolved symbols in /lib/modules/2.2.16/cops.o
depmod: *** Unresolved symbols in /lib/modules/2.2.16/ltpc.o
depmod: *** Unresolved symbols in /lib/modules/2.2.16/ipx.o

Hints as to eliminating these errors will be gratefully accepted.  When I
solve this, I'm planning on doing the new 2.4 kernel.

Thanks.

   -Gregor

       <[EMAIL PROTECTED]> /* Oregon Public Networking - Eugene, OR */

Reply via email to