The Debian source for kernel 2.4.27 unpacks into /usr/src/kernel-source-2.4.27 (that's what's available debian-source-wise I think), but the running kernel (precompiled, from the debian install cd) is (from uname -r) 2.4.27-2-386 ie for i386 architecture. So when I built loop.o, it got put in /lib/modules/2.4.27/block This didn't seem to be a problem, however. I did rmmod loop.o rm -f /lib/modules/2.4.27-2-386/kernel/drivers/block/loop.o cp /lib/modules/2.4.27/block/loop.o /lib/modules/2.4.27-2-386/kernel/drivers/block modprobe loop and the new loop.o driver seems to be working. BUT this same procedure didn't work for the new modules I built from loop-aes-ciphers v3.0b - modprobe says it can't find them. Naively changing the name of the source code directory to match 2.4.26-2-386 doesn't work ( I didn't think it would). How to I fix this? ____________________________________________________ Yahoo! Sports Rekindle the Rivalries. Sign up for Fantasy Football http://football.fantasysports.yahoo.com - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
