On Tue Nov 17 1998 at 12:38, [EMAIL PROTECTED] wrote: > > > >The only thing I see from lilo boot procedure is: "LI" and that's > > > >all. I can boot with bootdisk from fd0 and fsck shows that > > > >everything is ok. I've checked the disk geometry and manufacturer > > > >date, BIOS autodetect and lilo report at boot time (when I boot from > > > >fd0) are the same. I've changed the boot lilo record from /dev/hda > > > >to /dev/hda2 (my root partition), but the result was the same. I've > > > >even forse disk in lilo record, but no results. I've tried with > > > >smaller kernel(350kB) - the same > Is the linux partition set to active? If it's not, you'll get the LI > problem. I think that you'll find that this makes no difference to linux (although it does for other operating systems). The problems is caused by the boot loader (lilo) not finding the kernel image. Well, _it_ finds it, but the BIOS can't. It's the 1024 cylinder problem. The kernel is either on an extended partition (it should always be in a primary), and/or is on a partition but of reach of the BIOS. It might help to set the BIOS to LBA (linear) mode. But the solution is more likely to be to boot from a floppy/ramdisk (ie, rescue disk), mount the root partition, check the sanity of /mnt/etc/lilo.conf and /mnt/etc/fstab, re-establish the boot section by running "lilo -r /mnt", and if there are no complaints then rebooting at this point (fingers crossed). If there are complaints or the reboot still hangs with "LI", the kernel image will need to be moved into a new partition that is wholely within the first 1024 cylinders of a hard drive. See the LILO HOWTO and the docs in /usr/doc/lilo* for more details. Cheers Tony
