2.6.17.13 initrd fiasco

[Bill Campbell]

On Sun, Sep 10, 2006, Net Llama! wrote:
>On Sun, 10 Sep 2006, Collins Richey wrote:
>> 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.
>
>I'm doubtful that's the problem, as I've built the same kernel version on 
>other systems without this problem.

Did you make a new initrd to match the new kernel?

It's been a while since I actually built a kernel, and that was
on Caldera OpenSomethingorother.  They had a mkinitrd script that
did this (which had a bug in that it didn't properly handle
whitespace in the modules directory -- which Caldera never fixed
even though I sent them a complete fixed SRPM :-).

Bill
--
INTERNET:   bill at Celestial.COM  Bill Campbell; Celestial Software LLC
URL: http://www.celestial.com/  PO Box 820; 6641 E. Mercer Way
FAX:            (206) 232-9186  Mercer Island, WA 98040-0820; (206) 236-1676

``We maintain that the very foundation of our way of life is what we call
free enterprise,'' said Cash McCall, ``but when one of our citizens
show enough free enterprise to pile up a little of that profit, we do
our best to make him feel that he ought to be ashamed of himself.''
		-- Cameron Hawley