Gregor Diseth wrote:
> 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.
As Cory already explained, you installed your modules where the
distribution's modules already were. Some modules (cops, ltpc, and
ipx) didn't get replaced, so you had old modules mixed in with new
modules. Delete 'em and run depmod.
You've already overwritten your distribution modules, and won't be able
to go back to the distribution kernel until you reinstall the modules.
But if you or any of the other eug-luggers want to have both a distro
kernel and your own, here's how to give them different names.
Edit Makefile in the linux top level directory, and define
EXTRAVERSION as something unique. I use my name, kbob,
so my Makefile says,
EXTRAVERSION = -kbob
That means that all my modules are installed in
/lib/modules/2.2.16-kbob, and there's no conflict with the Mandrake
modules in /lib/modules/2.2.16-mdk.
The kernel is also installed to /boot/vmlinuz-2.2.16-kbob or something
similar. I edited lilo.conf to point to both kernels.
--
K<bob>
[EMAIL PROTECTED], http://www.jogger-egg.com/
