[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#354458: Kernel panic after upgrading initramfs-tools/klibc-utils/libklibc



On Sun, 26 Feb 2006 19:23:16 +0100
maximilian attems <maks@sternwelten.at> wrote:

> On Sun, 26 Feb 2006, Manuel Bilderbeek 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.

No, you do not need to recompile your kernel.

The idea of using a so-called "initial ramdisk" (initrd) to extend the
kernel itself is exactly to avoid building a new kernel each time
hardware changes.

What you probably need, however, is to regenerate the initrd. No matter
the tool used to generate the initrd (initramfs-tools or yaird) this is
normally done with the following command:

dpkg-reconfigure kernel-image-<whatever your version>

Hope that helps :-)


> > As it's not recorded anywhere and I didnt' write it down, it's hard
> > to say exactly. But the last few lines were all about that it
> > coudln't mount the root fs and that I should pass a proper root=
> > parameter to the kernel.

One option is to add some boot parameter to the kernel (in GRUB or
LILO, that is) to redirect boot messages to a serial line, and then
attach a serial cable to some other machine capturing the info.

I haven't ever tried this myself, so can't help with the details,
though (but if someone will help point in the right direction I have a
completely different kernel bugreport waiting to be written ;-) ).


 - Jonas

(Package maintainer of yaird)

-- 
* Jonas Smedegaard - idealist og Internet-arkitekt
* Tlf.: +45 40843136  Website: http://dr.jones.dk/

 - Enden er nær: http://www.shibumi.org/eoti.htm

Attachment: pgp2IHfYrQgc5.pgp
Description: PGP signature


Reply to: