Re: AW: Problem executing make test with loop-AES

[Jari Ruusu <jari.ruusu@pp.inet.fi>]

Frenchstylistics@gmx.li wrote:
> 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

That looks correct.

> 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

And your kernel logs recorded this message, viewable with "dmesg" command

    "Unable to get major number 7 for loop device"

Which means that your kernel has loop built-in.

> > 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?

Above "# CONFIG_BLK_DEV_LOOP is not set" is correct, but you are not running
that kernel. Please post output of "uname -a" command.

If you run "cat /proc/devices" command, you will see loop device registered,
but "lsmod" command does not show loop module.

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/