Have you upgraded the kernel; to 2.4.20-28.9 before running lilo?
Have you made the change above to lilo? If yes
did you run lilo -v -v?

hello

yes, i have upgrade kernel

ssh

up2date --nox -f kernel

lilo -v -v

reboot

______________
8.5.4. 8.5.5-R60
RH 9

OK!!! Great How-to... I went by the How-TO and everything went great. The new kernel was not being listed in lilo so as suggested I added the new values in /etc/lilo.conf and all is well. My question is, I have had this server over a year and with all the kernel upgrades in the past I noticed that I have a lot of old kernel stuff in my /boot partition, what files are safe to remove from my boot partition? Not just the .img files but these also or can these be safely removed?

module-info- for past kernel versions
System.map- for past kernel versions
config- for past kernel versions

Can these files be removed and leave the latest 2versions of the kernel on the server?

Thanks for the great HOw-To:D

denvercg yes I did it all but there is no /boot/message because of this when I write lilo -v -v I am taking an error Should I make all again?

My problem is /boot/message

there isnt message file because of this lilo -v -v command not finish its work

How can I add message file? or what should I do

lilo -v -v
LILO version 21.4-4, Copyright © 1992-1998 Werner Almesberger
'lba32' extensions Copyright © 1999,2000 John Coffman

Reading boot sector from /dev/hda
Merging with /boot/boot.b
Secondary loader: 11 sectors.
Mapping message file /boot/message
Fatal: open /boot/message: No such file or directory
Removed temporary file /boot/map~
root@server [/boot]#

Getting this when doing lilo -v -v

Reading boot sector from /dev/hda
Merging with /boot/boot.b
Secondary loader: 11 sectors.
Mapping message file /boot/message
Message: 46 sectors.
Boot image: /boot/vmlinuz-2.4.20-20.7
Setup length is 10 sectors.
Mapped 2097 sectors.
Mapping RAM disk /boot/initrd-2.4.20-20.7.img
RAM disk: 241 sectors.
Added linux
Boot image: /boot/vmlinuz-2.4.20-28.7
Setup length is 10 sectors.
Mapped 2097 sectors.
Mapping RAM disk /boot/initrd-2.4.20-28.7.img
RAM disk: 240 sectors.
Added 2.4.20-28.7
Fatal: No images have been defined.
Removed temporary file /boot/map~

What have I done wrong?

Thanks

Make sure you new kernel is listed in lilo.conf.. If not you will have to add the entry manually.

pico /etc/lilo.conf


This should be similar to what you have now...
prompt
timeout=50
default=linux
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
message=/boot/message
linear

image=/boot/vmlinuz-2.4.20-24.7
label=linux
root=/dev/hda3
read-only
initrd=/boot/initrd-2.4.20-24.7.img



Copy one of your entries and paste at the end. Change the entry to new kernel info and give it a new lable

image=/boot/vmlinuz-2.4.20-28.7
label=linux2
root=/dev/hda3
read-only
initrd=/boot/initrd-2.4.20-28.7.img

Change your default at the top to point to the new lable. This should fix ya up..

lilo -v -v
you should see the message at the bottom
Added new lable here *

Reboot and you are good to go..

ok after searching I understand that /boot/message file is for graphical interface and I know it doesnt matter its graphical or texture in the start for me I deleted the line from lilo.conf and lilo -v -v is worked then reboot brings to me new kernel.

I followed instructions by hostedzone with a lilo -v -v thrown in before the reboot and it worked perfectly - thanks ppl

Got it!

Thanks chism and everyone that contributed to this thread.

Scrumpy

Can you help a brother out.... as I am not sure right now...

root@srv3 [~]# up2date --nox -f kernel

Fetching package list for channel: redhat-linux-i386-9...
########################################

Fetching Obsoletes list for channel: redhat-linux-i386-9...
########################################

Testing package set / solving RPM inter-dependencies...
########################################
kernel-2.4.20-28.9.i686.rpm ########################## Done.
Preparing ########################################### [100%]

Installing...
1:kernel ########################################### [100%]
Fatal: open /boot/message: No such file or directory
Error installing lilo.conf The message was:
test install of lilo failed
root@srv3 [~]# lilo -v -v
LILO version 21.4-4, Copyright © 1992-1998 Werner Almesberger
'lba32' extensions Copyright © 1999,2000 John Coffman

Reading boot sector from /dev/hda
Merging with /boot/boot.b
Secondary loader: 11 sectors.
Mapping message file /boot/message
Fatal: open /boot/message: No such file or directory
Removed temporary file /boot/map~

Try manually downloading the rpm here:

http://rhn.redhat.com/errata/RHSA-2003-417.html

Then install it with rpm -ivh. Then check /boot for the kernel, and the init file. Next, manually edit /etc/lilo.conf. Finally, run lilo -v -v, and reboot... It's the most reliable way, imho.

yeah doing an rpm -ivh gives me package installed.. if I rpm -e package is not installed...

anyways.. here is my current lilo.conf


and I get the same error on lilo -v -v

Got it.. but before running up2date --nox -f kernel you have to make a backup copy of your lilo.conf manually just in case..

Miso, I got the same "message" problem I deleted message line from lilo.conf and its working now...

message line is for graphical start up...

I am looking for someone to do this or teach me how. (cpanel)

Are you ensim or cpanel or plesk or plain RH?

there are a few threads with how tos.. but it really is not so bad... if you can find a time to meet on the irc of ev1 or the proz... I will go through it with you... it really isn't THAT big of a deal but you MUST make sure you cover your a$$ with simple backups, etc.

my cpanel saying

You are running an insecure kernel (2.4.20-24.9). You should upgrade to a newer version as soon as possible to avoid your system being compromised. https://rhn.redhat.com/errata/RHSA-2003-417.html

ok that is usual but interesting point begin in lilo


prompt
timeout=50
default=linux
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
message=/boot/message
linear
image=/boot/vmlinuz-2.4.20-18.7
label=linux
initrd=/boot/initrd-2.4.20-18.7.img
read-only
root=/dev/hda3

when i try to rpm

root@ns1 [~]# rpm -ivh kernel-2.4.20-28.7.i686.rpm
Preparing... ########################################### [100%]
package kernel-2.4.20-28.9 (which is newer than kernel-2.4.20-28.7) is already installed
package kernel-2.4.20-28.7 is already installed


so what i need to do?
please show me the path i need to walk

i have several rmp's in tmp? and different numbers...

need help.. just a touch

thanks for your time

I would first cp the current lilo.conf

then edit the lines the in the lilo.conf that say default and change it to reflect the latest kernel.

also edit the lines that show the old kernel and put in the current kernel.

cntrl X and save and then lilo -v -v

see what comes up.. whatever you do DO NOT REBOOT untill you get lilo -v -v to come without error....

in the worst case you put back the origninal lilo.

I change everything on the lilo.conf and when i type

/sbin/lilo

i get the following error

Added linux
Fatal: Kernel /boot/vmlinux-2.4.20-28.7 is too big

Can anyone help me here please.

I get the following error when trying to upgrade:

Preparing... ########################################### [100%]
1:kernel ########################################### [100%]
stdin: is not a tty
stdin: is not a tty
stdin: is not a tty
rpmdb: Item 208 on page 554 hashes incorrectly
rpmdb: Item 68 on page 742 hashes incorrectly
error: db4 error(-30979) from db->verify: DB_VERIFY_BAD: Database verification failed


Anyone know what this means?

how do i uninstall a wrong version of kernel?

isn't it like this:

rpm -e kernel-2.4.20-28.7.i686

when i tried to run the command, it said the package is not installed but when i tried installing this:

rpm -e kernel-2.4.20-28.7.i386

i got a lot of errors like this:

....of kernel-2.4.20-28.7 conflicts with file from package kernel-2.4.20-28.7
file /lib/modules/2.4.20-28.7/kernel/net/ipv6/netfilter/ip6t_mark.o from install of kernel-2.4.20-28.7 conflicts with file from package kernel-2.4.20-28.7
file /lib/modules/2.4.20-28.7/kernel/net/ipv6/netfilter/ip6t_multiport.o from install of kernel-2.4.20-28.7 conflicts with file from package kernel-2.4.20-28.7
file /lib/modules/2.4.20-28.7/kernel/net/ipv6/netfilter/ip6t_owner.o from install of kernel-2.4.20-28.7 conflicts with file from package kernel-2.4.20-28.7
file /lib/modules/2.4.20-28.7/kernel/net/ipv6/netfilter/ip6t_rt.o from install of kernel-2.4.20-28.7 conflicts with file from package kernel-2.4.20-28.7
file /lib/modules/2.4.20-28.7/kernel/net/ipv6/netfilter/ip6table_filter.o from install of kernel-2.4.20-28.7 conflicts with file from package kernel-2.4.20-28.7
file /lib/modules/2.4.20-28.7/kernel/net/ipv6/netfilter/ip6table_mangle.o from install of kernel-2.4.20-28.7 conflicts with file from package kernel-2.4.20-28.7
file /lib/modules/2.4.20-28.7/kernel/net/ipx/ipx.o from install of kernel-2.4.20-28.7 conflicts with file from package kernel-2.4.20-28.7
file /lib/modules/2.4.20-28.7/kernel/net/irda/ircomm/ircomm-tty.o from install of kernel-2.4.20-28.7 conflicts with file from package kernel-2.4.20-28.7
file /lib/modules/2.4.20-28.7/kernel/net/irda/ircomm/ircomm.o from install of kernel-2.4.20-28.7 conflicts with file from package kernel-2.4.20-28.7
file /lib/modules/2.4.20-28.7/kernel/net/irda/irda.o from install of kernel-2.4.20-28.7 conflicts with file from package kernel-2.4.20-28.7
file /lib/modules/2.4.20-28.7/kernel/net/irda/irlan.o from install of kernel-2.4.20-28.7 conflicts with file from package kernel-2.4.20-28.7
file /lib/modules/2.4.20-28.7/kernel/net/irda/irlan/irlan.o from install of kernel-2.4.20-28.7 conflicts with file from package kernel-2.4.20-28.7
file /lib/modules/2.4.20-28.7/kernel/net/irda/irnet/irnet.o from install of kernel-2.4.20-28.7 conflicts with file from package kernel-2.4.20-28.7
file /lib/modules/2.4.20-28.7/kernel/net/netrom/netrom.o from install of kernel-2.4.20-28.7 conflicts with file from package kernel-2.4.20-28.7
file /lib/modules/2.4.20-28.7/kernel/net/rose/rose.o from install of kernel-2.4.20-28.7 conflicts with file from package kernel-2.4.20-28.7
file /lib/modules/2.4.20-28.7/kernel/net/sched/cls_fw.o from install of kernel-2.4.20-28.7 conflicts with file from package kernel-2.4.20-28.7
file /lib/modules/2.4.20-28.7/kernel/net/sched/cls_route.o from install of kernel-2.4.20-28.7 conflicts with file from package kernel-2.4.20-28.7
file /lib/modules/2.4.20-28.7/kernel/net/sched/cls_rsvp.o from install of kernel-2.4.20-28.7 conflicts with file from package kernel-2.4.20-28.7
file /lib/modules/2.4.20-28.7/kernel/net/sched/cls_rsvp6.o from install of kernel-2.4.20-28.7 conflicts with file from package kernel-2.4.20-28.7
file /lib/modules/2.4.20-28.7/kernel/net/sched/cls_tcindex.o from install of kernel-2.4.20-28.7 conflicts with file from package kernel-2.4.20-28.7
file /lib/modules/2.4.20-28.7/kernel/net/sched/cls_u32.o from install of kernel-2.4.20-28.7 conflicts with file from package kernel-2.4.20-28.7
file /lib/modules/2.4.20-28.7/kernel/net/sched/sch_cbq.o from install of kernel-2.4.20-28.7 conflicts with file from package kernel-2.4.20-28.7
file /lib/modules/2.4.20-28.7/kernel/net/sched/sch_csz.o from install of kernel-2.4.20-28.7 conflicts with file from package kernel-2.4.20-28.7
file /lib/modules/2.4.20-28.7/kernel/net/sched/sch_dsmark.o from install of kernel-2.4.20-28.7 conflicts with file from package kernel-2.4.20-28.7
file /lib/modules/2.4.20-28.7/kernel/net/sched/sch_gred.o from install of kernel-2.4.20-28.7 conflicts with file from package kernel-2.4.20-28.7
file /lib/modules/2.4.20-28.7/kernel/net/sched/sch_htb.o from install of kernel-2.4.20-28.7 conflicts with file from package kernel-2.4.20-28.7
file /lib/modules/2.4.20-28.7/kernel/net/sched/sch_ingress.o from install of kernel-2.4.20-28.7 conflicts with file from package kernel-2.4.20-28.7
file /lib/modules/2.4.20-28.7/kernel/net/sched/sch_prio.o from install of kernel-2.4.20-28.7 conflicts with file from package kernel-2.4.20-28.7
file /lib/modules/2.4.20-28.7/kernel/net/sched/sch_red.o from install of kernel-2.4.20-28.7 conflicts with file from package kernel-2.4.20-28.7
file /lib/modules/2.4.20-28.7/kernel/net/sched/sch_sfq.o from install of kernel-2.4.20-28.7 conflicts with file from package kernel-2.4.20-28.7
file /lib/modules/2.4.20-28.7/kernel/net/sched/sch_tbf.o from install of kernel-2.4.20-28.7 conflicts with file from package kernel-2.4.20-28.7
file /lib/modules/2.4.20-28.7/kernel/net/sched/sch_teql.o from install of kernel-2.4.20-28.7 conflicts with file from package kernel-2.4.20-28.7
file /lib/modules/2.4.20-28.7/kernel/net/sunrpc/sunrpc.o from install of kernel-2.4.20-28.7 conflicts with file from package kernel-2.4.20-28.7
file /lib/modules/2.4.20-28.7/kernel/net/tux/tux.o from install of kernel-2.4.20-28.7 conflicts with file from package kernel-2.4.20-28.7
file /lib/modules/2.4.20-28.7/kernel/net/wanrouter/wanrouter.o from install of kernel-2.4.20-28.7 conflicts with file from package kernel-2.4.20-28.7

can anyone help me on this?

previously rebooted the system with the .i686 kernel and it never booted again. The reason: "kernel panicking"

I then reviewed my last year's SUCCESSFUL kernel upgrade and found out that I used the i386 package. Now I want to re-do the upgrade using the "i386" package but it shows that it's having conflict with the same kernel and I can't uninstall it!

ok. i was able to uninstall the i686 version of kernel 2.4.20-28.7 and installed kernel 2.4.20-28.7.i386.

this is what happened:

root@srv1 [/]# rpm -ivh kernel-2.4.20-28.7.i386.rpm
Preparing... ########################################### [100%]
1:kernel ########################################### [100%]
stdin: is not a tty
stdin: is not a tty
stdin: is not a tty

i can't remember if i saw this in my last year's upgrade. Is this normal?

this is how my lilo.conf looks like:

prompt
timeout=50
default=linuxnew
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
message=/boot/message
linear

image=/boot/vmlinuz-2.4.20-18.7
label=linux
root=/dev/hda3
read-only
initrd=/boot/initrd-2.4.20-18.7.img

image=/boot/vmlinuz-2.4.20-28.7
label=linuxnew
root=/dev/hda3
read-only
initrd=/boot/initrd-2.4.20-28.7.img

ran lilo -v -v and this is the result:

root@srv1 [/]# lilo -v -v
LILO version 21.4-4, Copyright © 1992-1998 Werner Almesberger
'lba32' extensions Copyright © 1999,2000 John Coffman

Reading boot sector from /dev/hda
Merging with /boot/boot.b
Secondary loader: 11 sectors.
Mapping message file /boot/message
Message: 46 sectors.
Boot image: /boot/vmlinuz-2.4.20-18.7
Setup length is 10 sectors.
Mapped 2098 sectors.
Mapping RAM disk /boot/initrd-2.4.20-18.7.img
RAM disk: 248 sectors.
Added linux
Boot image: /boot/vmlinuz-2.4.20-28.7
Setup length is 10 sectors.
Mapped 2110 sectors.
Mapping RAM disk /boot/initrd-2.4.20-28.7.img
RAM disk: 237 sectors.
Added linuxnew *
/boot/boot.0300 exists - no backup copy made.
Map file size: 29696 bytes.
Writing boot sector.

Am I good to go? I would very much appreciate any advice before I reboot the machine. Thanks

why'd you uninstall i686 and use i386? i686 is a more appropriate kernel for EV1 boxes.

yes i know it's supposed to be better but when i rebooted using the i686 kernel, the server never came up. Reason: Kernel panicked.

After EV1 rebooted the server for me, I uninstalled the i686 kernel and replaced it with the i386 version. Did the same procedure and rebooted... kernel was upgraded!!!!! Finally!

You have a typo in your lilo.conf

locate /boot/vmlinux-2.4.20-28.7

and change to

/boot/vmlinuz-2.4.20-28.7

which one should I choose ???


prompt
timeout=50
default=linux
boot=/dev/sda
map=/boot/map
install=/boot/boot.b
message=/boot/message
linear

image=/boot/vmlinuz-2.4.20-30.7.legacysmp
label=2.4.20-30.7.legacysmp
root=/dev/sda3
read-only
initrd=/boot/initrd-2.4.20-30.7.legacysmp.img
image=/boot/vmlinuz-2.4.20-30.7.legacy
label=2.4.20-30.7.legacy
root=/dev/sda3
read-only
initrd=/boot/initrd-2.4.20-30.7.legacy.img
image=/boot/vmlinuz-2.4.20-28.7smp
label=2.4.20-28.7smp
root=/dev/sda3
read-only
initrd=/boot/initrd-2.4.20-28.7smp.img
image=/boot/vmlinuz-2.4.20-28.7
label=2.4.20-28.7
root=/dev/sda3
read-only
initrd=/boot/initrd-2.4.20-28.7.img
image=/boot/vmlinuz-2.4.20-27.7smp
label=2.4.20-27.7smp
root=/dev/sda3
read-only
initrd=/boot/initrd-2.4.20-27.7smp.img

image=/boot/vmlinuz-2.4.20-27.7
label=2.4.20-27.7
root=/dev/sda3
read-only
initrd=/boot/initrd-2.4.20-27.7.img

image=/boot/vmlinuz-2.4.20-24.7smp
label=2.4.20-24.7smp
root=/dev/sda3
read-only
initrd=/boot/initrd-2.4.20-24.7smp.img
image=/boot/vmlinuz-2.4.20-24.7
label=2.4.20-24.7
root=/dev/sda3
read-only
initrd=/boot/initrd-2.4.20-24.7.img

image=/boot/vmlinuz-2.4.20-20.7smp
label=2.4.20-20.7smp
root=/dev/sda3
read-only
initrd=/boot/initrd-2.4.20-20.7smp.img

image=/boot/vmlinuz-2.4.20-20.7
label=2.4.20-20.7
root=/dev/sda3
read-only
initrd=/boot/initrd-2.4.20-20.7.img
image=/boot/vmlinuz-2.4.20-19.7smp
label=2.4.20-19.7smp
initrd=/boot/initrd-2.4.20-19.7smp.img
read-only
root=/dev/sda3

image=/boot/vmlinuz-2.4.20-19.7
label=2.4.20-19.7
initrd=/boot/initrd-2.4.20-19.7.img
read-only
root=/dev/sda3
image=/boot/vmlinuz-2.4.20-18.7smp
label=2.4.20-18.7smp
initrd=/boot/initrd-2.4.20-18.7smp.img
read-only
root=/dev/sda3

image=/boot/vmlinuz-2.4.18-27.7.x
label=linux-up.bak
initrd=/boot/initrd-2.4.18-27.7.x.img
read-only
root=/dev/sda3

image=/boot/vmlinuz-2.4.20-19.7
label=linux-up.bak1
root=/dev/sda3
read-only
initrd=/boot/initrd-2.4.20-19.7.img
image=/boot/vmlinuz-2.4.20-19.7smp
label=linux.bak
root=/dev/sda3
read-only
initrd=/boot/initrd-2.4.20-19.7smp.img

image=/boot/vmlinuz-2.4.20-20.7
label=linux-up.bak12
root=/dev/sda3
read-only
initrd=/boot/initrd-2.4.20-20.7.img

image=/boot/vmlinuz-2.4.20-20.7smp
label=linux.bak1
root=/dev/sda3
read-only
initrd=/boot/initrd-2.4.20-20.7smp.img
image=/boot/vmlinuz-2.4.20-24.7
label=linux-up.bak123
root=/dev/sda3
read-only
initrd=/boot/initrd-2.4.20-24.7.img

image=/boot/vmlinuz-2.4.20-24.7smp
label=linux.bak12
root=/dev/sda3
read-only
initrd=/boot/initrd-2.4.20-24.7smp.img
image=/boot/vmlinuz-2.4.20-27.7
label=linux-up
root=/dev/sda3
read-only
initrd=/boot/initrd-2.4.20-27.7.img

image=/boot/vmlinuz-2.4.20-27.7smp
label=linux
root=/dev/sda3
read-only
initrd=/boot/initrd-2.4.20-27.7smp.img

lilo -v -v


I get his fatal error?

Reading boot sector from /dev/sda
Merging with /boot/boot.b
Secondary loader: 11 sectors.
Mapping message file /boot/message
Message: 46 sectors.
Boot image: /boot/vmlinuz-2.4.20-30.7.legacysmp
Setup length is 10 sectors.
Mapped 2263 sectors.
Mapping RAM disk /boot/initrd-2.4.20-30.7.legacysmp.img
RAM disk: 467 sectors.
Added linuxnew *
Boot image: /boot/vmlinuz-2.4.20-30.7.legacy
Setup length is 10 sectors.
Mapped 2106 sectors.
Mapping RAM disk /boot/initrd-2.4.20-30.7.legacy.img
RAM disk: 462 sectors.
Fatal: Label "2.4.20-30.7.legacy" is too long
Removed temporary file /boot/map~

LILO version 21.4-4, Copyright © 1992-1998 Werner Almesberger
'lba32' extensions Copyright © 1999,2000 John Coffman

Reading boot sector from /dev/sda
Merging with /boot/boot.b
Secondary loader: 11 sectors.
Mapping message file /boot/message
Message: 46 sectors.
Boot image: /boot/vmlinuz-2.4.20-30.7.legacysmp
Setup length is 10 sectors.
Mapped 2263 sectors.
Mapping RAM disk /boot/initrd-2.4.20-30.7.legacysmp.img
RAM disk: 467 sectors.
Added linux-up
Boot image: /boot/vmlinuz-2.4.20-30.7.legacy
Setup length is 10 sectors.
Mapped 2106 sectors.
Mapping RAM disk /boot/initrd-2.4.20-30.7.legacy.img
RAM disk: 462 sectors.
Added linuxnew *
Boot image: /boot/vmlinuz-2.4.20-28.7smp
Setup length is 10 sectors.
Mapped 2257 sectors.
Mapping RAM disk /boot/initrd-2.4.20-28.7smp.img
RAM disk: 476 sectors.
Added 2.4.20-28.7smp
Boot image: /boot/vmlinuz-2.4.20-28.7
Setup length is 10 sectors.
Mapped 2097 sectors.
Mapping RAM disk /boot/initrd-2.4.20-28.7.img
RAM disk: 459 sectors.
Added 2.4.20-28.7
Boot image: /boot/vmlinuz-2.4.20-27.7smp
Setup length is 10 sectors.
Mapped 2259 sectors.
Mapping RAM disk /boot/initrd-2.4.20-27.7smp.img
RAM disk: 476 sectors.
Added 2.4.20-27.7smp
Boot image: /boot/vmlinuz-2.4.20-27.7
Setup length is 10 sectors.
Mapped 2097 sectors.
Mapping RAM disk /boot/initrd-2.4.20-27.7.img
RAM disk: 459 sectors.
Added 2.4.20-27.7
Boot image: /boot/vmlinuz-2.4.20-24.7smp
Setup length is 10 sectors.
Mapped 2259 sectors.
Mapping RAM disk /boot/initrd-2.4.20-24.7smp.img
RAM disk: 468 sectors.
Added 2.4.20-24.7smp
Boot image: /boot/vmlinuz-2.4.20-24.7
Setup length is 10 sectors.
Mapped 2097 sectors.
Mapping RAM disk /boot/initrd-2.4.20-24.7.img
RAM disk: 457 sectors.
Added 2.4.20-24.7
Boot image: /boot/vmlinuz-2.4.20-20.7smp
Setup length is 10 sectors.
Mapped 2259 sectors.
Mapping RAM disk /boot/initrd-2.4.20-20.7smp.img
RAM disk: 465 sectors.
Added 2.4.20-20.7smp
Boot image: /boot/vmlinuz-2.4.20-20.7
Setup length is 10 sectors.
Mapped 2097 sectors.
Mapping RAM disk /boot/initrd-2.4.20-20.7.img
RAM disk: 456 sectors.
Added 2.4.20-20.7
Boot image: /boot/vmlinuz-2.4.20-19.7smp
Setup length is 10 sectors.
Mapped 2258 sectors.
Mapping RAM disk /boot/initrd-2.4.20-19.7smp.img
RAM disk: 465 sectors.
Added 2.4.20-19.7smp
Boot image: /boot/vmlinuz-2.4.20-19.7
Setup length is 10 sectors.
Mapped 2099 sectors.
Mapping RAM disk /boot/initrd-2.4.20-19.7.img
RAM disk: 457 sectors.
Added 2.4.20-19.7
Boot image: /boot/vmlinuz-2.4.20-18.7smp
Setup length is 10 sectors.
Mapped 2258 sectors.
Mapping RAM disk /boot/initrd-2.4.20-18.7smp.img
RAM disk: 467 sectors.
Added 2.4.20-18.7smp
Boot image: /boot/vmlinuz-2.4.18-27.7.x
Setup length is 10 sectors.
Mapped 2083 sectors.
Mapping RAM disk /boot/initrd-2.4.18-27.7.x.img
RAM disk: 459 sectors.
Added linux-up.bak
Boot image: /boot/vmlinuz-2.4.20-19.7
Setup length is 10 sectors.
Mapped 2099 sectors.
Mapping RAM disk /boot/initrd-2.4.20-19.7.img
RAM disk: 457 sectors.
Added linux-up.bak1
Boot image: /boot/vmlinuz-2.4.20-19.7smp
Setup length is 10 sectors.
Mapped 2258 sectors.
Mapping RAM disk /boot/initrd-2.4.20-19.7smp.img
RAM disk: 465 sectors.
Added linux.bak
Boot image: /boot/vmlinuz-2.4.20-20.7
Setup length is 10 sectors.
Mapped 2097 sectors.
Mapping RAM disk /boot/initrd-2.4.20-20.7.img
RAM disk: 456 sectors.
Added linux-up.bak12
Boot image: /boot/vmlinuz-2.4.20-20.7smp
Setup length is 10 sectors.
Mapped 2259 sectors.
Mapping RAM disk /boot/initrd-2.4.20-20.7smp.img
RAM disk: 465 sectors.
Added linux.bak1
Boot image: /boot/vmlinuz-2.4.20-24.7
Setup length is 10 sectors.
Mapped 2097 sectors.
Mapping RAM disk /boot/initrd-2.4.20-24.7.img
RAM disk: 457 sectors.
Added linux-up.bak123
Boot image: /boot/vmlinuz-2.4.20-24.7smp
Setup length is 10 sectors.
Mapped 2259 sectors.
Mapping RAM disk /boot/initrd-2.4.20-24.7smp.img
RAM disk: 468 sectors.
Fatal: Only 19 image names can be defined


then I get this error? I'm getting close I think