kernel-image kein lilo eintrag

[Tonami]

Huhu,
Habe folgendes Problem ich habe einen kernel erstellt mit initrd und ohne also mehrfach probiert.Der fehler ist das kein Eintrag in lilo.conf erfolgt wenn ich ihn selber erstelle bootet er nicht mehr.Habe mal die ausgabe gepostet:

t90:/usr/src# dpkg -i kernel-image-2.4.18-486_t90.0_i386.deb
Selecting previously deselected package kernel-image-2.4.18-486.
(Reading database ... 17702 files and directories currently installed.)
Unpacking kernel-image-2.4.18-486 (from kernel-image-2.4.18-486_t90.0_i386.deb) ...

You are attempting to install an initrd kernel image (version 2.4.18-486)
This will not work unless you have configured your boot loader to use
initrd. (An initrd image is a kernel image that expects to use an INITial
Ram Disk to mount a minimal root file system into RAM and use that for
booting).
As a reminder, in order to configure lilo, you need to
add an 'initrd=/initrd.img' to the image=/vmlinuz
stanza of your /etc/lilo.conf
I repeat, You need to configure your boot loader. If you have already done
so, and you wish to get rid of this message, please put
`do_initrd = Yes'
in /etc/kernel-img.conf. Note that this is optional, but if you do not,
you'll contitnue to see this message whenever you install a kernel
image using initrd.
Do you want to stop now? [Y/n]n
Setting up kernel-image-2.4.18-486 (t90.0) ...
/boot/initrd.img does not exist. Installing from scratch, eh?
Or maybe you don't want a symbolic link here. Hmm? Lets See.
/vmlinuz does not exist. Installing from scratch, eh?
Or maybe you don't want a symbolic link here. Hmm? Lets See.
A new kernel image has been installed, and usually that means
that some action has to be taken to make sure that the new
kernel image is used next time the machine boots. Usually,
this entails running a ``bootloader'' like SILO, loadlin, LILO,
ELILO, QUIK, VMELILO, ZIPL, or booting from a floppy. (Some
boot loader, like grub, for example, do not need to be run on
each new image install, so please ignore this if you are using
such a boot loader).

A new kernel image has been installed. at /boot/vmlinuz-2.4.18-486
(Size: 644kB)


Initial rootdisk image: /boot//initrd.img-2.4.18-486 (Size: )

Symbolic links, unless otherwise specified, can be found in /

LILO sets up your system to boot Linux directly from your hard
disk, without the need for booting from a boot floppy.


WARNING
If you are keeping another operating system or another version
of Linux on a separate disk partition, you should not have LILO
install a boot block now. Wait until you read the LILO documentation.
That is because installing a boot block now might make the other
system un-bootable. If you only want to run this version of Linux,
go ahead and install the boot block here. If it does not work, you
can still boot this system from a boot floppy.

You already have a LILO configuration in /etc/lilo.conf
Install a boot block using the existing /etc/lilo.conf? [Yes] yes
Testing lilo.conf ...
Testing successful.
Installing the partition boot sector...
Installation successful.

t90:/usr/src# lilo
Added 2.4.18-bf2.4
Added 2.4.18-1-386 *
t90:/usr/src#

[gms]

Ich kann mich jetzt täuschen, aber soweit ich mich erinnern kann, werden bei der Installation eines Kernel-Image nur die Symlinks vmlinuz und vmlinuz.old (oder so ähnlich) angepaßt. Die lilo.conf bleibt glaube ich unverändert.

[KBDCALLS]

Es gibt auch noch liloconfig bzw update-lilo welches Symlink auf liloconfig ist.