And now a reply without a smart*** comment.

Look at the value for "default =linux249-1", now look at the line
"label=vmlinuz249".  Shouldn't that be "label=linux249-1"?   I think the
two must match.  Try changing one or the other and rerun lilo and
restart and se what happens.   Also, I think you want "image =
/boot/linux249082501"  to match the actual path to the new kernel.   If
the image is actually called "linux_2.4.9-082501" then that is how you
must call it from lilo or it might actually be called
"vmlinuz-2.4.9-082501" only your compiler knows the truth.

Hope this helps
Brian Kelsay

----- Original Message -----
From: "James Edgar Twilley" <grimjack@blitz-it.net>
To: <kclug@kclug.org>
Sent: Saturday, August 25, 2001 12:14 PM
Subject: Lilo and 2.4.9 problems

> Hello all,
>   I just downloaded and built a 2.4.9 kernel, it all went entirely too
well.
> The problem comes when I  try and run lilo after moving the bzIImage
file to
> the boot dir and then modify lilo.conf and then run lilo.  It says...
> Added linux
> Added vmlinuz249  (this is my new kernel)  <<<<<<<<<<This is telling
> Added dos
> Fatal: No images have been defined.   <<<<<<This is the error, because
it can't find the kernel.
>   When I reboot my new info does not show up and it boots back into
the
> production RH 7.0 kernel.
> my lilo.conf file is a s follows:
> boot=/dev/hda
> map=/boot/map
> install=/boot/boot.b
> prompt
> timeout=50
> message=/boot/message
> default=linux249-1   <<<<<<<<<<HERE
>
> image = /boot/vmlinuz-2.2.16-22
> label=linux
> read-only
> root=/dev/hda2
>
> image = /boot/linux249082501     <<<<<<<<HERE
> label=vmlinuz249           <<<<<<<<HERE
> read-only
> root=/dev/hda2
>
> other = /dev/hda1
> label=dos