Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I just installed Redhat ES 5 U5 and I did an update to this load before handing it off to the Oracle DBA'. This made the kernel version of 2.6.9-55.0.9.ELsmp, . The issue here is that IBM sdd driver does not support this kernel version, it wants 2.6.9-55.0.2.ELsmp or older. When I originally installed from CD the kernel version is 2.6.9-55.ELsmp. How can I boot to the original kernel version??
These servers are fresh, so there is no issue with Oracle at this point..
You should first find the old kernel in the /boot partition or directory.
Just edit /boot/grub/grub.conf. Add another booting alternative at the beginning by copying the original booting instruction (from the title line to the one just before another title line, remember all lines with # are disavled and need not copied. You then amend it by in the "kernel statement substitute the existing kernek with old kernel name. You need to change the initrd file as well as the two go hand in hand. Save the file. On a reboot you should see the old kernel as another bootable choice.
If you have a problem post here the output of "ls /boot" and "ls /boot/grub/grub.conf".
[root@hqoradev08 grub]# more /boot/grub/grub.conf
# 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,0)
# kernel /vmlinuz-version ro root=/dev/sda3
# initrd /initrd-version.img
#boot=/dev/sda
default=1
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Red Hat Enterprise Linux ES (2.6.9-55.0.9.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-55.0.9.EL ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.9-55.0.9.EL.img
title Red Hat Enterprise Linux ES (2.6.9-55.0.9.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-55.0.9.ELsmp ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.9-55.0.9.ELsmp.img
title Red Hat Enterprise Linux ES (2.6.9-55.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-55.ELsmp ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.9-55.ELsmp.img
title Red Hat Enterprise Linux ES-up (2.6.9-55.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-55.EL ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.9-55.EL.img
You have to boot up the old installation CD, check for the old kernel if it is there copy it into your hda1 /boot partition.
Your grub.conf with these added lines (in red) will boot it
Code:
default=1
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Red Hat Enterprise Linux ES (2.6.9-55.0.2.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-55.0.2.EL ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.9-55.0.2.EL.img
title Red Hat Enterprise Linux ES (2.6.9-55.0.9.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-55.0.9.EL ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.9-55.0.9.EL.img
title Red Hat Enterprise Linux ES (2.6.9-55.0.9.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-55.0.9.ELsmp ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.9-55.0.9.ELsmp.img
The 0.2 version is just the version that IBMsdd supports and older kernel.. So, with just the install CD I get to the kernel I pasted above.. So, if I just edit my grub.conf with this, will this work??
title Red Hat Enterprise Linux ES (2.6.9-55.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-55.ELsmp ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.9-55.ELsmp.img
title Red Hat Enterprise Linux ES (2.6.9-55.0.9.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-55.0.9.EL ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.9-55.0.9.EL.img
title Red Hat Enterprise Linux ES (2.6.9-55.0.9.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-55.0.9.ELsmp ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.9-55.0.9.ELsmp.img
If this is the case then you current grub.conf already got it as the 3rd choice (in red text). Upgrading normally keeps the old kernels. There is no reason to remove it and in many cases newer kernel may fail to kick start all the hardware, as in your case.
Code:
default=1
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Red Hat Enterprise Linux ES (2.6.9-55.0.9.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-55.0.9.EL ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.9-55.0.9.EL.img
title Red Hat Enterprise Linux ES (2.6.9-55.0.9.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-55.0.9.ELsmp ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.9-55.0.9.ELsmp.img
title Red Hat Enterprise Linux ES (2.6.9-55.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-55.ELsmp ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.9-55.ELsmp.img
title Red Hat Enterprise Linux ES-up (2.6.9-55.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-55.EL ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.9-55.EL.img
Yes, you are correct that the entry is already in grub.conf. So technically I can just make my default 3, although I am a little confused. The default is currently set to 1 , but when I do a uname -r it comes up with the #2 entry or is the first line 0?
[root@hqoradev08 grub]# uname -r
2.6.9-55.0.9.ELsmp
[root@hqoradev08 grub]# cat /boot/grub/grub.conf
# 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,0)
# kernel /vmlinuz-version ro root=/dev/sda3
# initrd /initrd-version.img
#boot=/dev/sda
default=1
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Red Hat Enterprise Linux ES (2.6.9-55.0.9.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-55.0.9.EL ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.9-55.0.9.EL.img
title Red Hat Enterprise Linux ES (2.6.9-55.0.9.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-55.0.9.ELsmp ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.9-55.0.9.ELsmp.img
title Red Hat Enterprise Linux ES (2.6.9-55.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-55.ELsmp ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.9-55.ELsmp.img
title Red Hat Enterprise Linux ES-up (2.6.9-55.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-55.EL ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.9-55.EL.img
Check /lib/modules/ and see if you have a modules directory corresponding with the kernel you want to use. If you haven't uninstalled the previous kernel package, you probably have it. A kernel package supplies the /boot/vmlinuz-<version> and /boot/initrd-<version> files as well as the kernel modules compiled for that kernel. Simply copying a kernel and initrd file into the /boot directory will not work if you need any of the modules.
I you can boot to the grub menu item that refers to the 2.6.9-55.0.2.EL version kernel, all is probably well. You could simply edit the menu.lst file making this one your default if you want.
Thanks alot guys for you responses.. I have verifled the kernel modules exist, and I have made my default in grub.conf to 2. I am rebooting, i will let you guys know the result!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.