> You are running some other loop driver, not the loop-AES' > loop module. Above "dd: writing `/dev/loop7': Input/output error" is > a bug in mainline loop, and fixed in loop-AES two years ago. Hm, as far as I can see, the loop.o is the new one compiled from loop-AES: galgnet:~ # dir /lib/modules/2.4.18-64GB-SMP/block/ total 57 drwxr-xr-x 2 root root 72 Jun 23 17:19 . drwxr-xr-x 8 root root 512 Jun 23 17:19 .. -rw-r--r-- 1 root root 54178 Jun 23 17:50 loop.o Insmod tells me the following: galgnet:~ # insmod /lib/modules/2.4.18-64GB-SMP/block/loop.o /lib/modules/2.4.18-64GB-SMP/block/loop.o: init_module: Input/output error Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters > If you recompiled a new kernel, you also need to boot that new kernel. Yes, I booted from the new Kernel. In the tree there is: # CONFIG_BLK_DEV_LOOP is not set Should be correct or not? Thanks Frank - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
