okay, i figured it out....don't laugh to hard.-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Shane,
Look in your /boot directory for System.map- and see if the new kernel build is listed along with the old one. You should also see coresponding module-info-, vmlinux- and vmlinuz- as well. If you do then go back to the grub.conf file and copy the original entry all lines and paste them back in below the original and change the version numbers on the second set to reflect the new kernel version - here is my gruf.conf for reference
# 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/hda
default=0
timeout=10
splashimage=(hd0,1)/grub/splash.xpm.gz
title Red Hat Linux (2.4.20-18.1.caps)
root (hd0,1)
kernel /vmlinuz-2.4.20-18.1.caps ro root=LABEL=/
initrd /initrd-2.4.20-18.1.caps.img
title Red Hat Linux (2.4.20-4.ll.acpi)
root (hd0,1)
kernel /vmlinuz-2.4.20-4.ll.acpi ro root=LABEL=/
initrd /initrd-2.4.20-4.ll.acpi.img
title Red Hat Linux (2.4.20-8)
root (hd0,1)
kernel /vmlinuz-2.4.20-8 ro root=LABEL=/
initrd /initrd-2.4.20-8.img
- --
Hope this helps you out.
:)
Ron
On Thursday 06 November 2003 10:33, shane c branch wrote:
i just attempted to upgrade the kernel with an rpm package (2.4.20-19). normally, i download and build my own, but this rpm build has some 'corporate' additions for our company linux image.
i ran #rpm -ivh <filename>
it reported back the hash count indicating a proper install.
next, i restarted the machine but only the old kernel appeared in the grub boot options. i checked /etc/grub.conf, and it only has one entry, for the kernel from the original installation.
how do i get this upgrade to install? --
regards,
shane
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE/qohY2eFUc2a4qSoRAhNZAKCLO6lE71ZiihpzVRl+ar8KlCwntACfZGx1 LGynwUtnQl2C9andyJ/kY5g= =zp+V -----END PGP SIGNATURE-----
the problem was that the package provided was not really the kernel. it was named like a kernel rpm would be, but this was apparently denoting a module that was built on the 2.4.20-18.9 kernel they used for the machine image. i downloaded the 2.4.20.something from redhat, and it upgraded successfully using
#rpm -ivh <filename>
these IT guys are sneaky.
--
regards,
shane
-- Shrike-list mailing list Shrike-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/shrike-list
