Compiling kernel on a RH9 (same thing happened on same box with 8) box with EZZI. This does not happen on my DN box.

kernel= 2.4.20-8

'uname -a' shows correct 2.4.20-8 kernel

wget the 2.4.24 src from kernel.org

'make dep clean all modules modules_install install;lilo;reboot'

Kernel compiles, no errors at all

ls -l /boot shows this

System.map -> System.map-2.4.24
vmlinuz -> vmlinuz-2.4.24

lilo.conf and grub both point to that as the default

reboot server

'uname -a' still shows 2.4.20-8 kernel

oh and ls -l /boot shows

System.map -> System.map-2.4.20-8
vmlinuz -> vmlinuz-2.4.24

after a reboot lol

A Friend have also a Ezzi-Server (Dell) and he have also Problems with Updating Kernel, the last Time his Server did not Start up and he needed the Ezzi-Support to fix it !

Do you use CPanel ? Maybe the following Kernel (incl. Grsecurity) is something for you: http://cplicensing.net/grsecurity.php

it seems to me the box is running lilo.

the command "lilo" must be run every time lilo.conf is updated. otherwise new configurations will not be loaded.

IF this is the case, do NOT set the new kernel as default in lilo.conf yet. edit lilo.conf now and change that setting back to the old kernel. run "lilo", then again run:

lilo -R 2.4.24

substitute 2.4.24 with wutever label u defined for the kernel in lilo.conf.

this will tell lilo to load the new kernel 2.4.24 only on the next reboot. so if anything happens and the new kernel fails to load, another simple reboot will boot the server back to the old working kernel. so u dont have to ask the techs@ dc to manually select the old kernel on startup.

if the new kernel boots up fine and runs good edit lilo.conf again and set it as default. then run the "lilo" command again to make the change effective.

hope this helps.

Thats what im saying tho - I have run lilo, and now i see the system.map is reverting back to old one for some reason. The vmlinuz symbolic link remains for the 2.4.24 but the system map one reverts back.

system.map rolls back to whichever kernel is used 2 boot the server. so its still the boot loader's problem.

according to ur steps, lilo was run rite after make install. i believe by default this only adds the new kernel entry to lilo and grub but does NOT make it the default one to boot up. did u edit the file after that? if u did u need 2 run lilo again.

and have u tried the command lilo -R kernel_label ?