Bug#551728: closed by maximilian attems m...@stro.at (Re: Bug#551728: initramfs-tools: Fails to boot with encrypted root after upgrade)

2009-10-23 Thread Adam
maximilian attems wrote: On Wed, Oct 21, 2009 at 06:10:18AM +0200, Adam wrote: However the real and remaining problem is a initramfs for 2.6.30-2 that doesn't boot (wasn't stated properly in my previous email). The old initramfs for -2 (initrd.img-2.6.30-2-powerpc.bak) boots as well as

Bug#551728: closed by maximilian attems m...@stro.at (Re: Bug#551728: initramfs-tools: Fails to boot with encrypted root after upgrade)

2009-10-21 Thread maximilian attems
On Wed, Oct 21, 2009 at 06:10:18AM +0200, Adam wrote: However the real and remaining problem is a initramfs for 2.6.30-2 that doesn't boot (wasn't stated properly in my previous email). The old initramfs for -2 (initrd.img-2.6.30-2-powerpc.bak) boots as well as both -1 images. I guess a new

Bug#551728: closed by maximilian attems m...@stro.at (Re: Bug#551728: initramfs-tools: Fails to boot with encrypted root after upgrade)

2009-10-20 Thread Adam
It turned out, that /boot/initrd.img.old was pointing to 2.6.30-2 instead of -1 (embarrassing). So this problem is solved and unrelated. The -1 kernel now boots with the new image fine. So the remaining problem might be unrelated to cryptsetup. ok cool, thus closing.