2.6.17.13 initrd fiasco

[Net Llama!]

On Sun, 10 Sep 2006, Bill Campbell wrote:
> 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?

'make all' does that automatically as part of the kernel build.

>
> 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 :-).

THat was an old 2.2.x kernel issue.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Lonni J Friedman                        netllama at linux-sxs.org
LlamaLand				http://netllama.linux-sxs.org