kernel 2.4.24 compile error

german · 01-29-2004, 03:07 PM

Howdy gurus,

so I'm compiling along happily, everything's going fine, I make modules_install and after a while it barfs this back at me:

Code:

mkdir -p pcmcia; \
find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{} pcmcia
if [ -r System.map ]; then /sbin/depmod -ae -F System.map  2.4.24; fi
depmod: *** Unresolved symbols in /lib/modules/2.4.24/kernel/crypto/autoload.o
depmod:         crypto_alg_lookup
depmod: *** Unresolved symbols in /lib/modules/2.4.24/kernel/crypto/proc.o
depmod:         crypto_alg_sem
depmod:         crypto_alg_list
depmod: *** Unresolved symbols in /lib/modules/2.4.24/kernel/drivers/media/radio/miropcm20.o
depmod:         aci_version_R93350c87
depmod:         aci_rw_cmd_Rcc7c4cd8
depmod:         aci_port_R0d82adb6
make: *** [_modinst_post] Error 1

Looks like a .config problem, but I did not enable PCMCIA or the crypto libs... WTF? Has anyone solved this before?

TIA

B.

jpbarto · 01-29-2004, 03:35 PM

did you run 'make dep' before continuing with the rest of the build?

german · 01-29-2004, 03:52 PM

yeah... of course... I have compiled several kernels before on various (x86) hardware, but never seen this before... ah well I'll post the answer when I get through it...

Thanks for the response

B.

Half_Elf · 01-29-2004, 09:03 PM

is this a slackware kernel?
Slackware kernel are always busy, you might consider to get a fresh one from kernel.org

h/w · 01-29-2004, 09:09 PM

did u make mrproper before u started? did u have an existing 2.4.24?

german · 01-30-2004, 01:09 AM

Thanks for the responses...

I'm compiling a kernel downloaded as the latest stable 2.4 release from ftp.kernel.org around Jan. 27, and I did have a 2.4.24 before, which had the same problem (I deleted /lib/modules/2.4.24 before I did a make mrproper this time, as well as the /boot/[bzImage|System.map]). This is a p2 with basically nothing but a semi-old but reliable IDE HDD, 64MB RAM and a RealTek 8139 compatible card in it, on an oldish ASUS mobo with nothing integrated. It's running RedHat 7.3 right now but as a public LAMP it's not really secure enough to rely on, and I would much rather trust it than totally cut off its external access.

Thanks again, ideas welcome

B.

german · 01-30-2004, 06:31 PM

Uh.... I got it, though unfortunately I'm not certain exactly what I did to make it work. First I enabled sound support without actually building any modules, and did the same with amateur radio support. Then I opened up the .config file and set
CONFIG_SOUND_OSS=m
after which it compiled and installed fine, and is now happily ticking away.

Hope this helps someone

B.