FC4 kernel upgrade

[phatPhrog]

How do I get an FC4 box to load and keep the latest kernel installed.

Here's what we have now. Why is vmlinuz.old -> /boot/vmlinuz-2.6.16-1.2069_FC4 actually the newest kernel installed and the current one is the original from a freshly reimaged box?

uname -r
2.6.16-rc6-060427a

rpm -q kernel kernel-smp
kernel-2.6.16-1.2069_FC4
kernel-2.6.16-1.2096_FC4
kernel-2.6.16-1.2108_FC4

ll /boot
total 9976
-rw-r--r-- 1 root root 512 Jul 18 2005 boot.0300
-rw-r--r-- 1 root root 512 Apr 13 17:42 boot.0800
-rw-r--r-- 1 root root 5824 Apr 13 22:56 boot.b
-rw-r--r-- 1 root root 612 Jun 15 2004 chain.b
-rw-r--r-- 1 root root 63029 Mar 28 12:43 config-2.6.16-1.2069_FC4
-rw-r--r-- 1 root root 63444 May 5 00:13 config-2.6.16-1.2108_FC4
-rw-r--r-- 1 root root 29824 Apr 27 04:33 config-2.6.16-rc6-060427a
drwxr-xr-x 2 root root 4096 May 17 13:52 grub
-rw-r--r-- 1 root root 1090927 Apr 13 17:55 initrd-2.6.16-1.2069_FC4.img
-rw-r--r-- 1 root root 1090846 May 17 12:23 initrd-2.6.16-1.2108_FC4.img
drwx------ 2 root root 28672 May 17 11:30 lost+found
-rw------- 1 root root 89600 May 17 11:30 map
-rw-r--r-- 1 root root 640 Jun 15 2004 os2_d.b
-rw-r--r-- 1 root root 786855 Mar 28 12:43 System.map-2.6.16-1.2069_FC4
-rw-r--r-- 1 root root 788364 May 5 00:13 System.map-2.6.16-1.2108_FC4
-rw-r--r-- 1 root root 873292 Apr 27 04:41 System.map-2.6.16-rc6-060427a
lrwxrwxrwx 1 root root 32 May 17 11:29 vmlinuz -> /boot/vmlinuz-2.6.16-rc6-060427a
-rw-r--r-- 1 root root 1598219 Mar 28 12:43 vmlinuz-2.6.16-1.2069_FC4
-rw-r--r-- 1 root root 1602889 May 5 00:13 vmlinuz-2.6.16-1.2108_FC4
-rw-r--r-- 1 root root 2005771 Apr 27 04:41 vmlinuz-2.6.16-rc6-060427a
lrwxrwxrwx 1 root root 31 May 17 11:29 vmlinuz.old -> /boot/vmlinuz-2.6.16-1.2069_FC4


cat /etc/grub.conf /etc/lilo.conf
serial --unit 0 --speed 57600
terminal serial console --timeout=5

default=0
timeout=10

title linux with serial console
root (hd0,0)
kernel /boot/vmlinuz ro root=/dev/sda3 console=ttyS0,57600 console=tty1

title linux
root (hd0,0)
kernel /boot/vmlinuz ro root=/dev/sda3 console=tty1 console=ttyS0,57600

title Red Hat Linux (2.4.20-8)
root (hd0,0)
kernel /boot/vmlinuz.old ro root=/dev/sda3

root=/dev/sda1
boot=/dev/sda

install=/boot/boot.b
vga=normal
timeout=10
prompt
lba32

read-only

default=lx

serial=0,57600n8
append="console=ttyS0,57600 console=tty0 panic=30"

image=/boot/vmlinuz
label=lxser
append="console=tty0 console=ttyS0,57600 panic=30"

image=/boot/vmlinuz
label=lx

image=/boot/vmlinuz.old
label=lxserold
append="console=tty0 console=ttyS0,57600 panic=30"
optional

image=/boot/vmlinuz.old
label=lxold
optional

#image=/boot/memtest86+.bin
# label=memtest+
# optional

[scott - another test server - )

[scott]

Is that on a 1and1 box? I see a suspicious kernel on there:

vmlinuz-2.6.16-rc6-060427a <- generally a sign of n00bish meddling.

When they do that it screws up the more modular kernel design of Redhat/Fedora, which generally means you need to get into /etc/modules.conf and define your critical hardware (network, SATA, etc) manually before you install the kernel, otherwise the initrd wont be generated correctly and the box will be rendered unbootable in that kernel.

[phatPhrog]

You hit it on the head. 1and1 default image. Only changes I made was run a yum update via the default /yum.repos.d before adding any ART channels. (i also commented out the 1n1 channels in yum.conf first - they always result in mirror problems)

Any yum update results in the info I posted. Any attempt to load the new kernel reverts to the vmlinuz-2.6.16-rc6-060427a

NOTE: This server is like the other one you were working with . /sda (SATA)

Don't suppose you would offer a remedy?


Also, and way off topic....they not only changed the OS, they have changed Plesk.

Just for one example:

The Technical Support link (which is supposed to redirect to SW-Soft support) on the Plesk 8 desktop redirects to "order dot one and one dot com" with someone elses 1and1 ID/affiliate link.

Worse yet....the back button has no effect (been killed). One has to close the window, close the browser (or clear your cache), login again, kill the last session before Plesk is restored.

Talk about a sales pitch! I'm all about advertising, but forcing current clients out of their secure layer into a unsecure sales page is a bit much.

Sorry, wrambling again..



BTW - this box does not have a /etc/modules.conf

[scott]

Oh yeah, theres a fix all right:

http://3es.atomicrocketturtle.com/tests ... staller.sh

It wipes the box out and puts CentOS4 on it. Back up your PSA key, run that, install PSA (through my archive or the sw-soft one) and your troubles will go away.