Re: Loop-AES 1.6f and gpg encrypted root trouble

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

Peter Kirk wrote:
> On Dienstag, 7. Januar 2003 20:47 Jari Ruusu wrote:
> > Please post exact error messages. All of them.
> Here comes an extensive post =)
[snip]
> Encrypted file system, please supply correct password to continue
> 
> /dev/loop/0: No such file or directory
> Command "/lib/losetup -e AES128 /dev/loop/0
> /dev/ide/host0/bus0/target0/lun0/part10" returned error
> flushing ide devices: hda hdb hdc hdd hde
> System halted.

OK. So losetup is unable to open device /dev/loop/0 because it doesn't
exist.

> loop-AES version: loop-AES-v1.6i
> kernel version: 2.4.19-gentoo-r10 with devfs enabled, with mount at boot
> enabled
> 
> im totaly lost on whats going on =( please help

When kernel is configured with CONFIG_DEVFS_FS=y, drivers register their
devices at runtime so that devfs knows about them. And in loop driver case,
loop is supposed to register above /dev/loop/0 device. That device is not
registered there as above error message shows.

One reasonable explanation is that your kernel was compiled with
configuration that had CONFIG_DEVFS_FS=y, but externally compiled loop.o
module was compiled for kernel configuration that had CONFIG_DEVFS_FS=n.

What does this command output?

    nm /boot/loop-2.4.19-gentoo-r10.o | grep devfs

It should look something like this:

0000000c b devfs_handle
         U devfs_mk_dir
         U devfs_register_blkdev
         U devfs_register_series
         U devfs_unregister
         U devfs_unregister_blkdev

Your loop.o module is compiled for wrong kernel configuration
(CONFIG_DEVFS_FS=n) if it looks something like this:

0000000c b devfs_handle

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/