depmod: *** Unresolved symbols on install new kernel modules
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
depmod: *** Unresolved symbols in /lib/modules/2.4.24advncdfs/kernel/drivers/block/loop.o
depmod: *** Unresolved symbols in /lib/modules/2.4.24advncdfs/kernel/drivers/cdrom/cdrom.o
depmod: *** Unresolved symbols in /lib/modules/2.4.24advncdfs/kernel/drivers/char/agp/agpgart.o
depmod: *** Unresolved symbols in /lib/modules/2.4.24advncdfs/kernel/drivers/char/drm/mga.o
[and many more]
This happened immediately after I installed the new kernel. I'm
tempted to think this is just because depmod is running against the
current (2.4.21) kernel, but I don't recall seeing such warnings in
the past.
Here is some possibly related information and puzzles:
Kernel and modules built with debianized sources, debianized
kernel-patches, and make-kpkg.
I've been getting errors about apm.o (only) with my current kernel:
Feb 29 07:30:01 wheat insmod:
/lib/modules/2.4.21advncdfs/kernel/arch/i386/kernel/apm.o:
init_module: No such device
I do have the file
/lib/modules/2.4.21advncdfs/kernel/arch/i386/kernel/apm.o on my
system.
The build of the kernel seemed to have an unusual number of missing
files type messages. For example,
acsi.c:74:25: asm/atarihw.h: No such file or directory
acsi.c:75:27: asm/atariints.h: No such file or directory
acsi.c:76:28: asm/atari_acsi.h: No such file or directory
acsi.c:77:29: asm/atari_stdma.h: No such file or directory
acsi.c:78:29: asm/atari_stram.h: No such file or directory
fetchop.c:59:25: asm/machvec.h: No such file or directory
fetchop.c:60:24: asm/sn/sgi.h: No such file or directory
fetchop.c:61:26: asm/sn/addrs.h: No such file or directory
fetchop.c:62:25: asm/sn/arch.h: No such file or directory
fetchop.c:63:28: asm/sn/fetchop.h: No such file or directory
fetchop.c:64:29: asm/sn/sn_cpuid.h: No such file or directory
i2c-ite.h:36:31: asm/it8172/it8172.h: No such file or directory
rtc.c:27:25: asm/machdep.h: No such file or directory
rtc.c:29:22: asm/time.h: No such file or directory
via-pmu.c:36:22: asm/prom.h: No such file or directory
via-pmu.c:37:25: asm/machdep.h: No such file or directory
via-pmu.c:41:26: asm/sections.h: No such file or directory
via-pmu.c:44:30: asm/pmac_feature.h: No such file or directory
via-pmu.c:47:26: asm/sections.h: No such file or directory
via-pmu.c:48:26: asm/cputable.h: No such file or directory
via-pmu.c:49:22: asm/time.h: No such file or directory
tc.c:19:27: asm/addrspace.h: No such file or directory
tc.c:21:30: asm/dec/machtype.h: No such file or directory
Makefile:168: kernel/i2c-core.d: No such file or directory
Makefile:168: kernel/i2c-dev.d: No such file or directory
Makefile:168: kernel/i2c-algo-bit.d: No such file or directory
Makefile:168: kernel/i2c-algo-biths.d: No such file or directory
Makefile:168: kernel/i2c-philips-par.d: No such file or directory
Makefile:168: kernel/i2c-elv.d: No such file or directory
Makefile:168: kernel/i2c-velleman.d: No such file or directory
Makefile:168: kernel/i2c-algo-pcf.d: No such file or directory
Makefile:168: kernel/i2c-proc.d: No such file or directory
Makefile:168: kernel/i2c-pport.d: No such file or directory
make[3]: Entering directory `/usr/local/src/kernel/modules/lm-sensors'
Makefile:246: kernel/busses/i2c-nforce2.d: No such file or directory
Makefile:246: kernel/busses/i2c-ipmb.d: No such file or directory
Makefile:246: kernel/busses/i2c-ipmi.d: No such file or directory
Makefile:246: kernel/busses/i2c-ali1535.d: No such file or directory
The latter ones about i2c and lm-sensors seem particularly problematic
(I built both as modules, disabling i2c in the kernel).
Can anybody tell me whether any of this indicates a significant
problem, and if so, what I can do about it?
Thanks.
Reply to: