Re: [gentoo-dev] module dependency issues with new kernel

[Pete Gavin]

On Wed, Feb 07, 2001 at 04:34:11AM +0100, Achim Gottinger wrote:
> Dave Bresson wrote:
>
> > So i decided to switch to the new 2.4.0.11-rc3 kernel, not only because of
> > the few improvements, but also i just prefer to make my own, slimmed down,
> > more optimized kernel for my machine.  Anyway, i merged the linux source
> > of the kernel in question from portage, and all was fine.  I then did a
> > 'make menuconfig', then a 'make bzImage', 'make modules', and 'make
> > modules_install'.  Now i know i didn't include or exclude anything i
> > shouldn't have (i've rolled my own kernel plenty of times), however when
> > booting with my new kernel i get "Error configuring module dependencies."
> > As such, the modules don't work (most importantly my ethernet driver).  I
> > know the drivers compiled and installed in the right spot, since i can
> > manually do an 'insmod' for my net driver, and then restart the inet
> > script.  So there must be some sort of configuration issue going on i
> > don't know about.  Here a sample of some of the boot errors from
> > /var/log/boot:
> >
> > Calculating kernel module dependencies...
> > depmod: *** Unresolved symbols in
> > /lib/modules/2.4.1-pre8/kernel/drivers/char/pc
> > mcia/serial_cb.o
> > depmod: *** Unresolved symbols in
> > /lib/modules/2.4.1-pre8/kernel/drivers/char/pc
> > mcia/serial_cs.o
> > depmod: *** Unresolved symbols in
> > /lib/modules/2.4.1-pre8/kernel/drivers/isdn/av
> > mb1/avm_cs.o
> > depmod: *** Unresolved symbols in
> > /lib/modules/2.4.1-pre8/kernel/drivers/md/line
> > ar.o
> > depmod: *** Unresolved symbols in
> > /lib/modules/2.4.1-pre8/kernel/drivers/md/raid
> > 0.o
> >
> > [...]
> >
> > Auto-generating 2.4.0-ac11 modules.conf...
> > modprobe: Can't open dependencies file /lib/modules/2.4.0-ac11/modules.dep
> > (No such file or directory)
> >
> > And that about ends the errors.  Well, right after that it tries to insert
> > the net driver, but fails.  You get the drift.  Anyway, it looks like from
> > the errors that it's still trying to load the modules my old kernel used,
> > but from my new kernel's mod directory (where they don't exist, since i
> > didn't need them for my new kernel).  However, i still have the same net
> > module for both kernels, and even that didn't work.  Something is
> > definitely wrong.  Somewhere along the line i must've forgotten something
> > neccessary to configure the correct module dependencies and such.  Could
> > this have anything to do with the discussed 'depmod -a' call from one of
> > the other threads on the list?  Since Pete just put that in, i doubt the
> > ebuild script i used did this (the one i had was from this morning).
> > Anyway, does anyone know what might have gone wrong here?
> >
> > thanks,
>
> Hmm thats what I said to pete before the depmod he added to the kernel-ebuild
> does not work.
>
> Do you have /lib/modules/2.4.0-ac11/modules.dep?
>
> If so take a look into it.
>
> There muste be some wrong path's tha point to /lib/modules/2.4.1-pre8
>
> change them to .../2.4.0-ac11 and rerun
>
> depmod -a
>
> then things should worke fine again.
>
> achim~
>

No, the problem is probably that /boot wasn't mounted before you
merged the new package. This is exactly what happened to me when I
merged it w/o having /boot mounted. Just mv /boot/boot/bzImage
somewhere safe, then mount boot, then mv bzImage /boot/boot. Then
reboot.


Pete