zorro wrote: > I build kernel-2.6.2 with the flowing Instructions > CONFIG_MODULES=y > BLK_DEV_LOOP=n > > I build > http://loop-aes.sourceforge.net/ciphers-latest.tar.bz2 > > ld -m elf_i386 -r loop_blowfish.o loop_blowfish.mod.o > -o loop_blowfish.ko > rm -f loop_blowfish.o loop_blowfish.mod.[co] .mod.[co] > mkdir -p /lib/modules/2.6.2/block > cp -p loop_twofish.ko loop_serpent.ko loop_blowfish.ko > /lib/modules/2.6.2/block > /sbin/depmod -a -F > /lib/modules/2.6.2/build/System.map 2.6.2 > sync > Currently running kernel is 2.6.2 > Modules were built for kernel 2.6.2 > Building modules, stage 2. > make[1]: Leaving directory `/usr/src/linux-2.6.2' > > for install > make > INSTALL_MOD_PATH=/lib/modules/2.6.2/kernel/drivers/block > > All is work :) > > root@zss:/home/hamer/sauv/crypto/ciphers-v2.0f#modprobe > loop_twofish > FATAL: Error inserting loop_twofish > (/lib/modules/2.6.2/block/loop_twofish.ko): Unknown > symbol in module, or unknown parameter (see dmesg) > > with dmesg : > loop_twofish: Unknown symbol loop_unregister_transfer > loop_twofish: Unknown symbol loop_register_transfer > loop_twofish: Unknown symbol loop_compute_md5_iv The INSTALL_MOD_PATH= specifies the _root_ of the destination, just like it does in the kernel Makefiles. You really installed files to /lib/modules/2.6.2/kernel/drivers/block/lib/modules/2.6.2/block/ To get rid of these incorrectly installed files, do this: rm -r /lib/modules/2.6.2/kernel/drivers/block/lib Since you already are running 2.6.2 kernel and want to compile and install modules for it, simplest way to do that is this: tar xvfj loop-AES-v2.0f.tar.bz2 cd loop-AES-v2.0f make cd .. tar xvfj ciphers-v2.0f.tar.bz2 cd ciphers-v2.0f make -- Jari Ruusu 1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9 DB 1D EB E3 24 0E A9 DD - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
