Quote:> LI The first stage boot loader was able to load the second stage boot
> loader, but has failed to execute it. This can either be caused by a
> geometry mismatch or by moving /boot/boot.b without running the map
Well, I installed from my hard-drive. I went with linux slackware version 3.0 ELF,
and the kernel is 1.2.18.
I opted not to support my cd-rom for now (mitsumi 4x), just to see if I could get it to boot
So I created an emergency LILO boot disk and also a regular lilo boot disk.
Well, when I reboot with the regular lilo boot, it types on the screen:
then hangs there, not even making it to the bootup. Same happens with the Lilo installed
on the MBR of my first hard-disk, which is 340 meg dos disk. My second disk is partitioned
to be 500M,250M,750M, in that order. The 500m is the first partition and is linux.
250 and 750 are both dos partitions. I had troubles getting the install to recognize my
partitions. The only install disk that would recognize it was the one created with
ATAPI/IDF support through win3.1 linux boot utility. If I made a boot disk with rawrite
and idecd, color root image, it would not recognize my partitions. Said that it was an
unknown partition on the entire drive. So I installed with the one that recognized the
partitions. Now I have the LILO problem...and I don't know if it is related.
Also the emergency boot disk goes through and halts at a kernel panic as if the kernel were
compressed when it was expected to be expanded. I don't know about that one either as it is the
disk made from the linux setup. So I can only enter linux again by install disk.
I assume a geometry problem, but don't know how to get around it.
Any help please email me: