Jonas Larsson wrote: > I don't have "CONFIG_BLK_DEV_LOOP is N", I have "# CONFIG_BLK_DEV_LOOP is > not set" but I suppose that is ok. That's ok. > Anyway, I will try "make modules_install" after the kernel compilation: > > # find /lib/modules/ -name "loop.o" > /lib/modules/2.4.9-13/kernel/drivers/block/loop.o > /lib/modules/2.4.9-13custom/block/loop.o > > (2.4.9-13custom was created by "make" with loop-AES.) What does command "uname -r" output? If the output is "2.4.9-13", you have built loop.o module for kernel version "2.4.9-13custom" and you are still running kernel "2.4.9-13". Please install your newly compiled kernel and newly compiled modules, then you are running a kernel loop.o was compiled for. > # cd /usr/src/linux-2.4.9-13 > # make modules_install > [...] > > But the "loop.o" didn't got removed: > > # find /lib/modules/ -name "loop.o" > /lib/modules/2.4.9-13/kernel/drivers/block/loop.o > /lib/modules/2.4.9-13custom/block/loop.o Kernel's Makefile tried to remove /lib/modules/2.4.9-13custom/kernel/drivers/block/loop.o It was not there, so it was not removed. > The question is, do I dare to use it since the "6 out of 29 hunks FAILED" > with "make" and loop-AES seem to me a bit scary... but the "Test results ok" > above looks nice anyway... Those errors came from "patch --dry-run" and are harmless. Makefile is just trying to detect whether a patch applies or not. For more information type "man patch". Regards, Jari Ruusu <jari.ruusu@pp.inet.fi> - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
