On Wed, 27 Feb 2002, Stan Kaufman wrote:
> Faheem Mitha wrote:
>
> > On 27 Feb 2002, Bill Moseley wrote:
> >
> > > So, I'd like to avoid the kernel panic this time with the
> > > kernel-image-2.4.17-k7 package. What steps do I need to take to make sure
> > > I will end up with a bootable image? Someone mentioned that moving to the
> > > more modular 2.4 kernel might have been the problem - something about not
> > > setting up initrd?
>
> I just installed 2.4.17 on a new woody box, which involved an upgrade from the
> 2.2.14 potato system my floppy install disks created. The kernel-image package
> provided clear notice during installation that the bootloader needs to be
> altered
> in order to find the new image, since it's handled differently from the 2.2.x
> kernels. Since I use lilo, it was a simple matter of adding a couple of lines
> to
> the right entry in /etc/lilo.conf:
Hmm. I use grub and I didn't have to do anything different to setup the
2.4 kernels. I believe that kernel-package has now some support for grub,
but I don't know the details. I just did update-grub and modify the
entries as necessary. Grub seems to be an easier method than lilo in this
situation, as it is in others.
Here is what the entry on one of my machines looks (created by
update-grub; I just modified the root from (hd0,0) and the root from
/dev/hda1.)
title Debian GNU/Linux, kernel 2.4.17
root (hd0,5)
kernel /boot/vmlinuz-2.4.17 root=/dev/hda6 ro
savedefault
title Debian GNU/Linux, kernel 2.4.17 (recovery mode)
root (hd0,5)
kernel /boot/vmlinuz-2.4.17 root=/dev/hda6 ro single
savedefault
Faheem.
