Bug#354458: Kernel panic after upgrading initramfs-tools/klibc-utils/libklibc
On Sun, 26 Feb 2006, Manuel Bilderbeek wrote:
> maximilian attems wrote:
> >please don't drop the bug report out of cc.
>
> OK, the whole world gets to read stupid details on my system. :P
well bug reports are full of that. develepment can't touch all the
possible user interactions.. ;)
> >>Does this take (temporarily) extra disk space? I only have 8MB left on
> >>my /boot partition.
> >
> >your boot partition should already contain an /boot/initd.img-2.6.15-1-k7
> >so that will only replace it.
> >8 mb should be fine, consider enlarging your partition.
>
> Of course, but it's a long story. I'll promise to buy a new disk soon
> and move all files to it, OK? :P
well it should work with what you have at the moment..
> 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.
yaird hardcodes every step, so there you need to regenerate your image
after moving around. (sorry have no experience on that, primarily using
initramfs-tools).
> 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.
hmm exact error messages always help.
so please retest or i can't do much about that report.
regards
--
maks
Reply to: