Hi Stefan and s.keeling

Am 15.03.2008 03:41, Stefan Patric schrieb:
> On Sat, 15 Mar 2008 00:30:08 +0100, Arun Dev wrote:
>
>> Am 15.03.2008 00:15, Arun Dev schrieb:
>>>
>>> I just installed a basic etch 4.0r3 and got it updated.
>>>
>>> Then got the kernel 2.4.19 and compiled it the old-way: [...]
>>> Web-search says either problem of switching to udev or broken Grub. It
>>> can't be the former, because that transition was already done in etch.
>>> Then I "repaired" Grub menu.lst /dev/hda2 should be /dev/sda2 and in
>>> fstab too hda should be sda.
>>>
>>> Still the problem persists, booting stops "Waiting for root device"..
>> Forgot to mention that, in Grub I'm using the initrd which was there,
>> /boot/initrd.img-2.6.18-6-486, in case if this is relevant.
>
> It sure is! And that's the problem probably. Your initrd.img has to
> match the kernel you're booting. Boot into the old kernel, then use
> mkinitrd to make a new initrd for the new kernel. Edit grub.conf to
> reflect the changes. Keep the old kernel and initrd and make a boot
> listing in case you have more problems booting the new kernel.

It could be the problem. When I'm back in the office, I'll try again.
What is the trick of making an initrd for a different (later) kernel
than the one is running? I mean making initrd for 2.6.19 inside a
running 2.6.18-6?

> Also post your grub.conf so we can check for any errors.

Thanks! These are the two options as of yesterday:

title Debian GNU/Linux, kernel 2.6.18-6-486
root (hd0,1)
kernel /boot/vmlinuz-2.6.18-6-486 root=/dev/hda2 ro
initrd /boot/initrd.img-2.6.18-6-486
savedefault

title Debian GNU/Linux, kernel 2.6.19-486
root (hd0,1)
kernel /boot/vmlinuz-2.6.19-486 root=/dev/hda2 ro
initrd /boot/initrd.img-2.6.18-6-486
savedefault

CU
Arun