Hi,
I have updated the kernel to 2.4.21-27.0.2 on Centos 3.4 (was 3.3 when
I did the kernel update) and have modified grub.conf to use the single
CPU kernel:
# 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/cciss/c0d0p6
# initrd /initrd-version.img
#boot=/dev/cciss/c0d0
default=1
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
title CentOS (2.4.21-27.0.2.EL)
root (hd0,0)
kernel /vmlinuz-2.4.21-27.0.2.EL ro root=LABEL=/
initrd /initrd-2.4.21-27.0.2.EL.img
title CentOS (2.4.21-27.0.2.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.4.21-27.0.2.ELsmp ro root=LABEL=/
initrd /initrd-2.4.21-27.0.2.ELsmp.img
title CentOS (2.4.21-27.0.1.EL)
.......
I then created a new symbolic link for Sytem.map in /boot to point to
System.map-2.4.21-27.0.2.EL.
When I reboot the 2.4.21-27.0.1.ELsmp is used and System.map has been
changed to point to the smp kernel.
Is there a step I'm missing out?
BTW, the upgrade from 3.3 to 3.4 using yum seems to have worked - I'm
running Oracle on the server.
Thanks,
Wayne
Wayne Bastow wrote:> Hi, > > I have updated the kernel to 2.4.21-27.0.2 on Centos 3.4 (was 3.3 > when I did the kernel update) and have modified grub.conf to use the > single CPU kernel: > > # 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/cciss/c0d0p6 # initrd /initrd-version.img > #boot=/dev/cciss/c0d0 > default=1 > timeout=10 > splashimage=(hd0,0)/grub/splash.xpm.gz > title CentOS (2.4.21-27.0.2.EL) > root (hd0,0) > kernel /vmlinuz-2.4.21-27.0.2.EL ro root=LABEL=/ > initrd /initrd-2.4.21-27.0.2.EL.img title CentOS > (2.4.21-27.0.2.ELsmp) root (hd0,0) > kernel /vmlinuz-2.4.21-27.0.2.ELsmp ro root=LABEL=/ > initrd /initrd-2.4.21-27.0.2.ELsmp.img title CentOS > (2.4.21-27.0.1.EL) ....... > > I then created a new symbolic link for Sytem.map in /boot to point to > System.map-2.4.21-27.0.2.EL. > > When I reboot the 2.4.21-27.0.1.ELsmp is used and System.map has been > changed to point to the smp kernel. > > Is there a step I'm missing out? > > BTW, the upgrade from 3.3 to 3.4 using yum seems to have worked - I'm > running Oracle on the server. > > Thanks, > Wayne > _______________________________________________ > CentOS mailing list > CentOS at caosity.org > http://lists.caosity.org/mailman/listinfo/centosPerhaps you need: default=1 You only pasted one entry from your grub.conf. Do you have more entries? Mike
On 25/01/2005 5:40 p.m., Wayne Bastow wrote:> Hi, > > I have updated the kernel to 2.4.21-27.0.2 on Centos 3.4 (was 3.3 when > I did the kernel update) and have modified grub.conf to use the single > CPU kernel: > > # 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/cciss/c0d0p6 > # initrd /initrd-version.img > #boot=/dev/cciss/c0d0 > default=1You just need to change this to default=0, to have the first listed image be the default. -Simon
1. Why the SMP and NON-SMP kernel ? Just one or the other is needed, not both. SMP = multi-processor or hyperthreading only ( though may be fine with non SMP .. I haven't examined the .config or the sources ). 2. Why the manual Sytem.map to System.map-2.4.21-27.0.2.EL symlink, also note the spelling. -- Beau Henderson http://www.iminteractive.net On Tue, 25 Jan 2005 15:40:05 +1100, Wayne Bastow <ayu.njoman at gmail.com> wrote:> Hi, > > I have updated the kernel to 2.4.21-27.0.2 on Centos 3.4 (was 3.3 when > I did the kernel update) and have modified grub.conf to use the single > CPU kernel: > > # 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/cciss/c0d0p6 > # initrd /initrd-version.img > #boot=/dev/cciss/c0d0 > default=1 > timeout=10 > splashimage=(hd0,0)/grub/splash.xpm.gz > title CentOS (2.4.21-27.0.2.EL) > root (hd0,0) > kernel /vmlinuz-2.4.21-27.0.2.EL ro root=LABEL=/ > initrd /initrd-2.4.21-27.0.2.EL.img > title CentOS (2.4.21-27.0.2.ELsmp) > root (hd0,0) > kernel /vmlinuz-2.4.21-27.0.2.ELsmp ro root=LABEL=/ > initrd /initrd-2.4.21-27.0.2.ELsmp.img > title CentOS (2.4.21-27.0.1.EL) > ....... > > I then created a new symbolic link for Sytem.map in /boot to point to > System.map-2.4.21-27.0.2.EL. > > When I reboot the 2.4.21-27.0.1.ELsmp is used and System.map has been > changed to point to the smp kernel. > > Is there a step I'm missing out? > > BTW, the upgrade from 3.3 to 3.4 using yum seems to have worked - I'm > running Oracle on the server. > > Thanks, > Wayne > _______________________________________________ > CentOS mailing list > CentOS at caosity.org > http://lists.caosity.org/mailman/listinfo/centos >
Wayne Bastow wrote:> Hi, > > I have updated the kernel to 2.4.21-27.0.2 on Centos 3.4 (was 3.3 when > I did the kernel update) and have modified grub.conf to use the single > CPU kernel:<snip>> # grub.conf generated by anaconda<snip>> default=1default=0 as it starts counting at 0, thank a programmer for this... <snip>> ....... > > I then created a new symbolic link for Sytem.map in /boot to point to > System.map-2.4.21-27.0.2.EL.Shouldn't really be necessary. .dn
btw.. 1 = 2nd in the list.. 0 = 1st. -- Beau Henderson http://www.iminteractive.net On Tue, 25 Jan 2005 15:40:05 +1100, Wayne Bastow <ayu.njoman at gmail.com> wrote:> Hi, > > I have updated the kernel to 2.4.21-27.0.2 on Centos 3.4 (was 3.3 when > I did the kernel update) and have modified grub.conf to use the single > CPU kernel: > > # 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/cciss/c0d0p6 > # initrd /initrd-version.img > #boot=/dev/cciss/c0d0 > default=1 > timeout=10 > splashimage=(hd0,0)/grub/splash.xpm.gz > title CentOS (2.4.21-27.0.2.EL) > root (hd0,0) > kernel /vmlinuz-2.4.21-27.0.2.EL ro root=LABEL=/ > initrd /initrd-2.4.21-27.0.2.EL.img > title CentOS (2.4.21-27.0.2.ELsmp) > root (hd0,0) > kernel /vmlinuz-2.4.21-27.0.2.ELsmp ro root=LABEL=/ > initrd /initrd-2.4.21-27.0.2.ELsmp.img > title CentOS (2.4.21-27.0.1.EL) > ....... > > I then created a new symbolic link for Sytem.map in /boot to point to > System.map-2.4.21-27.0.2.EL. > > When I reboot the 2.4.21-27.0.1.ELsmp is used and System.map has been > changed to point to the smp kernel. > > Is there a step I'm missing out? > > BTW, the upgrade from 3.3 to 3.4 using yum seems to have worked - I'm > running Oracle on the server. > > Thanks, > Wayne > _______________________________________________ > CentOS mailing list > CentOS at caosity.org > http://lists.caosity.org/mailman/listinfo/centos >
Just another note regarding SMP kernel. I've never had an issue, and am currently running dual XEON 2.4's. Well, I've had issue with kernel upgrades and the megaraid2 driver, but that seems to be a result of Dell's dkms enabled driver setup, rather than the kernel itself. Ben