On Sat, Jan 26, 2002 at 01:46:07AM +0200, Jari Ruusu wrote: > nosaj wrote: > > I'm trying to build loop-AES-v1.5b. I patch, compile and install > > util-linux-2.11n without error. I make and install loop-AES without error. > > Then when I run `make tests': > > ... > > ... > > echo 12345678901234567890 | losetup -p 0 -e AES128 /dev/loop7 test-file1 > > ioctl: LOOP_SET_STATUS: Invalid argument > > make: *** [tests] Error 1 > > > > When I try `insmod loop': > > Using /lib/modules/2.4.17/block/loop.o > > /lib/modules/2.4.17/block/loop.o: init_module: Input/output error > > Hint: insmod errors can be caused by incorrect module parameters, > > including invalid IO or IRQ parameters > > > > I am running kernel 2.4.17 <CONFIG_DEV_LOOP is not set> on an i686. I > > built it using gcc2.95.3 and glibc2.2.5. > > > > If anyone has had the same problem, or can give me some advice about what > > is causing this, I would be very grateful. > > Can you check if "insmod loop" causes "Unable to get major number 7 for > loop" message in dmesg? Can you double check that CONFIG_BLK_DEV_LOOP=n in > your _running_ kernel? "cat /proc/devices" output is useful. > > Regards, > Jari Ruusu <jari.ruusu@pp.inet.fi> > Apologies, Jari... cat /proc/devices shows that loop is running. I swear I compiled that option out of my kernel! Anyway, I re-rebuilt the kernel and this time it works a charm. Many thanks for your time and help, Nosaj. - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
