Bug#354458: Kernel panic after upgrading initramfs-tools/klibc-utils/libklibc
- To: maximilian attems <email@example.com>
- Cc: firstname.lastname@example.org
- Subject: Bug#354458: Kernel panic after upgrading initramfs-tools/klibc-utils/libklibc
- From: Manuel Bilderbeek <email@example.com>
- Date: Fri, 03 Mar 2006 13:17:41 +0100
- Message-id: <440833E5.firstname.lastname@example.org>
- Reply-to: Manuel Bilderbeek <email@example.com>, firstname.lastname@example.org
- In-reply-to: <20060226182316.GA2918@nancy>
- References: <20060226144249.14785.61728.reportbug@goemon> <20060226154220.GS16411@baikonur.stro.at> <4401CD2D.email@example.com> <20060226163417.GA9824@nancy> <4401E69C.firstname.lastname@example.org> <20060226182316.GA2918@nancy>
maximilian attems wrote:
Anyway, if my kernel image is going to be replaced, while it came from
the linux-image package, does this mean that this kernel package should
be rebuilt with the new initramfs or something?
i don't understand that question.
linux-image generates in postinstall the initrd.img with a preconfigured
set of initramfs generators for 2.6 that's initramfs-tools and yaird.
with initramfs-tools you just need to copy your boot to your new partition
tell your boot loader to make it bootable and it should work.
Ah, I thought the initrd image also came from the linux-image package.
hmm exact error messages always help.
so please retest or i can't do much about that report.
Well, before I tested I did another dist-upgrade (just got back from
holidays), and this installed both a new kernel and a new
initramfs-tools, and now I can just boot the kernel nicely. So, as far
as I'm concerned the bug can be closed. I think regenerating the initrd.
img would have worked, though, but I can't check that now.
PS: MSX FOR EVER! (Questions? http://faq.msxnet.org/ )
PPS: Visit my homepage at http://manuel.msxnet.org/