[NTLUG:Discuss] Weird problem switching to new kernel.

Wayne Dahl w.dahl4 at verizon.net
Tue Sep 16 13:19:51 CDT 2003


This is kind of strange, but I'm trying to switch to a newer kernel and
am getting nowhere.  I don't recall having this trouble before. 

I'm currently running 2.3.20-18.8 and have 2.4.20-19.8 on the machine,
am trying to get it running and the 18.8 kernel is the one the machine
keeps using.  I'm using Lilo and my lilo.conf is given below...

prompt
timeout="50"
boot="/dev/hda2"
map=/boot/map
install=/boot/boot.b
message=/boot/message
linear
default=linux

image="/boot/vmlinuz-2.4.20-19.8"
        label="linux"
        read-only
        initrd="/boot/initrd-2.4.20-19.8.img"
        append="hdd=ide-scsi root=LABEL=/"

other=/dev/hda1
        optional
        label=DOS

image="/boot/vmlinuz-2.4.20-18.8"
        label="2.4.18-24.8.0"
        read-only
        initrd="/boot/initrd-2.4.20-18.8.img"
        append="hdd=ide-scsi root=LABEL=/"

Just to be on the safe side, I checked the grub.conf and this is what I
find there...

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this
file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd0,1)
#          kernel /vmlinuz-version ro root=/dev/hda5
#          initrd /initrd-version.img
#boot=/dev/hda2
default=7
timeout=10
splashimage=(hd0,1)/grub/splash.xpm.gz
title Red Hat Linux (2.4.20-19.8)
        root (hd0,1)
        kernel /vmlinuz-2.4.20-19.8 ro root=LABEL=/ hdd=ide-scsi
        initrd /initrd-2.4.20-19.8.img
title Red Hat Linux (2.4.20-18.8)
        root (hd0,1)
        kernel /vmlinuz-2.4.20-18.8 ro root=LABEL=/ hdd=ide-scsi
        initrd /initrd-2.4.20-18.8.img
title Red Hat Linux (2.4.20-13.8)
        root (hd0,1)
        kernel /vmlinuz-2.4.20-13.8 ro root=LABEL=/ hdd=ide-scsi
                kernel /vmlinuz-2.4.20-13.8 ro root=LABEL=/ hdd=ide-scsi
        initrd /initrd-2.4.20-13.8.img
title Red Hat Linux (2.4.18-27.8.0)
        root (hd0,1)
        kernel /vmlinuz-2.4.18-27.8.0 ro root=LABEL=/ hdd=ide-scsi
        initrd /initrd-2.4.18-27.8.0.img
title Red Hat Linux (2.4.18-26.8.0)
        root (hd0,1)
        kernel /vmlinuz-2.4.18-26.8.0 ro root=LABEL=/ hdd=ide-scsi
        initrd /initrd-2.4.18-26.8.0.img
title Red Hat Linux (2.4.18-24.8.0)
        root (hd0,1)
        kernel /vmlinuz-2.4.18-24.8.0 ro root=LABEL=/ hdd=ide-scsi
        initrd /initrd-2.4.18-24.8.0.img
title Red Hat Linux (2.4.18-19.8.0)
        root (hd0,1)
        kernel /vmlinuz-2.4.18-19.8.0 ro root=LABEL=/ hdd=ide-scsi
        initrd /initrd-2.4.18-19.8.0.img
title Red Hat Linux (2.4.18-14)
        root (hd0,1)
        kernel /vmlinuz-2.4.18-14 ro root=LABEL=/ hdd=ide-scsi
        initrd /initrd-2.4.18-14.img
title DOS
        rootnoverify (hd0,0)
        chainloader +1

Now, I know I'm not using grub because none of this stuff comes up on
the initial boot screen...just the stuff from the lilo.conf file.  What
is going on here and why won't the machine boot into the new kernel?  I
AM selecting Linux from the menu which shows in the lilo.conf file to be
the newer kernel.  Is this something I've overlooked?  I've done this
before (modified the lilo.conf file to boot to a newer kernel) and never
has this problem before.

Thanks,

Wayne






More information about the Discuss mailing list