Re: depmod: *** Unresolved symbols on install new kernel modules: Good News
On Sun, Feb 29, 2004 at 05:37:28PM -0800, Ross Boylan wrote:
> I just built a custom kernel and modules, and got a bunch of errors
> about unresolved symbols errors from depmod:
>
> # dpkg -i alsa-modules-2.4.24advncdfs_1.0.2c-2+rb.2_i386.deb i2c-2.4.24advncdfs_2.8.1-1+rb.2_i386.deb lm-sensors-2.4.24advncdfs_2.8.1-2+rb.2_i386.deb
> Selecting previously deselected package alsa-modules-2.4.24advncdfs.
> (Reading database ... 208972 files and directories currently installed.)
> Unpacking alsa-modules-2.4.24advncdfs (from alsa-modules-2.4.24advncdfs_1.0.2c-2+rb.2_i386.deb) ...
> Selecting previously deselected package i2c-2.4.24advncdfs.
> Unpacking i2c-2.4.24advncdfs (from i2c-2.4.24advncdfs_2.8.1-1+rb.2_i386.deb) ...
> Selecting previously deselected package lm-sensors-2.4.24advncdfs.
> Unpacking lm-sensors-2.4.24advncdfs (from lm-sensors-2.4.24advncdfs_2.8.1-2+rb.2_i386.deb) ...
> Setting up alsa-modules-2.4.24advncdfs (1.0.2c-2+rb.2) ...
> depmod: *** Unresolved symbols in /lib/modules/2.4.24advncdfs/kernel/arch/i386/kernel/apm.o
> depmod: *** Unresolved symbols in /lib/modules/2.4.24advncdfs/kernel/crypto/deflate.o
> depmod: *** Unresolved symbols in /lib/modules/2.4.24advncdfs/kernel/crypto/tcrypt.o
> depmod: *** Unresolved symbols in /lib/modules/2.4.24advncdfs/kernel/drivers/block/floppy.o
[etc]
This was caused by depmod -a 2.4.24advncdfs in the alsa postinst
script. The good news is that things were fine once I booted into the
new kernel. Why depmod complained in the old one remains a mystery.
When I did depmod with -e, the error symbols reported included lots of
devfs related ones. Possibly they were all from devfs, though that
wasn't obvious from the names. I enabled devfs in the new kernel; it
was absent in the old. Why that should cause trouble, given that
depmod was pointed at the new libs, I don't know. Although if it was
using the new modules and the old kernel, I guess that would do it.
I opened a bug on alsa-source about this, though it's probably more a
depmod issue. I don't have the number yet; subject is "alsa-source:
depmod -a reports freak out for new kernel".
Reply to: