2.6.17.13 initrd fiasco

[Collins Richey]

On 9/10/06, Net Llama! <netllama at linux-sxs.org> wrote:
> I built 2.6.17.13 today on a system that had been running 2.6.16.18 for
> the past 100+ days.  I used the same kernel config to build 2.6.17.13 as I
> had used for 2.6.16.18.  I built it with "make oldconfig && make all &&
> make modules_install && make install".  All attempts to boot the 2.6.17.13
> kernel kept failing with a kernel panic when attempting to mount the /
> filesystem complaining that "could not mount /dev/root".

>.  Guess what?!  It boots fine without the initrd.  I'm quite stumped on what
> is going on here.  I'm glad that it boots now, but i don't get how the initrd
> can be busticated like this when the kernel build process created it.
> Anyone?
>

A kernel build/ initrd build bug to take up with the maintainers of
your distro, ie file a bug.


-- 
Collins Richey
     If you fill your heart with regrets of yesterday and the worries
     of tomorrow, you have no today to be thankful for.