Yeah I'm not sure why, but it appears in /boot that the only kernel that has an *.img file associated with it is that bigmem kernel. I thought I had up2date set to allow for kernel updates, but if I had up2date set to skip kernel updates, would that make sense that all the other kernels don't have img files associated with them? Sorry if I'm completely n00bish here, but I don't mess around with kernel stuff at all (obviously). Interestingly enough I have another box right here will an old drive from the remote box I want to fix, and on that box (the one in front of me) I can load the 2.4.20 kernel at boot up time from the graphical lilo menu. At 12:26 PM 10/20/2003 -0400, you wrote: >On Mon, 2003-10-20 at 15:17, Steve Bopple wrote: >> When I do that and run sbin/lilo I get the following error after the >> console echos back that all of the images have been added: >> >> "fatal: no images have been defined" > >It appears that most of your kernel listings are missing a ramdisk >entry. Something like what your last kernel contains: > >initrd=/boot/initrd-2.4.18-3bigmem.img > >Make sure a ramdisk exists in /boot for the kernel you wish to boot, >then add the appropriate line to your lilo.conf for that kernel and >re-run lilo. > >-- >Jason Dixon, RHCE >DixonGroup Consulting >http://www.dixongroup.net > > >-- >redhat-list mailing list >unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe >https://www.redhat.com/mailman/listinfo/redhat-list > > -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
