I had loop-AES 1.4e running fine with linux 2.4.8. I then upgraded my kernel to 2.4.16 to get ext3, and loop-AES stopped working. Upgrading to loop-AES 1.5b hasn't helped either. With 1.4e, everything builds OK, but running depmod -a gives depmod: *** Unresolved symbols in /lib/modules/2.4.16/block/loop.o and running "make tests" gives dd if=/dev/zero of=test-file1 bs=1024 count=10 10+0 records in 10+0 records out cp test-file1 test-file3 echo 12345678901234567890 | losetup -p 0 -e AES128 /dev/loop7 test-file1 ioctl: LOOP_SET_STATUS: Invalid argument presumably as a result of being unable to pull in a working loop.o module With 1.5b everything build OK, depmod is happy, but again running "make tests" gives the same error. The relevant bits out of /usr/src/linux/.config are CONFIG_MODULES=y CONFIG_MODVERSIONS=y CONFIG_KMOD=y # CONFIG_BLK_DEV_LOOP is not set Can someone help a baffled Windows C++ developer diagnose what he's doing wrong? Many TIA Mark - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
