Re: loop-aes initrd failes to boot 2.6.x

[Martin Muellenberg <martinmue@xxxxxx>]

> > > build-initrd.sh script.
> >
> > diff build-initrd.sh.default build-initrd.sh.ownConfig
> >
> > < CRYPTROOT=/dev/hda2
> >
> > > CRYPTROOT=/dev/hda6
>
>               ^^^^^^^^^
> When devfs is mounted by kernel (CONFIG_DEVFS_FS=y and CONFIG_DEVFS_MOUNT=y
> in kernel config and USEDEVFS=1 in build-initrd.sh config), BOOTDEV=
The options above are in my kernel config set as you specified it.

> CRYPTROOT= and EXTERNALGPGDEV= (if needed) must be specified using long
> form genuine devfs name. /dev/hda6 is a compatibility name provided by
> devfsd. devfsd is not yet running when these names are used.
I changed build-initrd.sh as followed:
	#BOOTDEV=/dev/hda1
	BOOTDEV=/dev/ide/host0/bus0/target0/lun0/part1
	#CRYPTROOT=/dev/hda6
	CRYPTROOT=/dev/ide/host0/bus0/target0/lun0/part6

>> cat grub.conf
>> ---snip---
>> title=linux-2.6.3-ck2
>> root (hd0,0)
>> kernel /vmlinuz-2.6.3-ck2 init=/linuxrc rootfstype=minix
>> initrd /initrd-2.6.gz
>> ---snip---

>That looks ok. If it still fails, try with "root=/dev/ram0" or "root=0100"
>kernel parameter. Not specifying root= was a workaround for kernel bug in
>some older 2.4 kernels. Not sure if that bug is still there in 2.6 kernels.
I then rebooted and the same error as before. Even after trying with 
root=/dev/ram0 or root=0100 I get the error

hope that helps, thx
martin


-
Linux-crypto:  cryptography in and on the Linux system
Archive:       http://mail.nl.linux.org/linux-crypto/