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
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
severity 551728 important
stop
On Tue, Oct 20, 2009 at 09:47:38AM +0200, Adam Schmalhofer wrote:
Package: initramfs-tools
Version: 0.93.4
Severity: critical
Justification: breaks the whole system
no that would be true if it would break a huge number of boxes.
After upgrading to
With linux-image-2.6.30-1-powerpc [...] complaining that
dm_mod couldn't be loaded.
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
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.
5 matches
Mail list logo
