I just found out why!!!!

[Desire]

OK this may not seem like a big deal to anybody but it is for me.
A couple of weeks ago I loaded Slackware 8.0 and after the install all I got was "LI". couldn't figure out why or what that meant. Well I found out that it's because of LILO could not discern the location of the kernel and this indicates a disk geometry problem....hm!! I just found (read) this in a section of the Linux+ Certification Guide (by Osborne Press) Well I'll try to run another install this weekend but make a small change to see if it is what I suspect it might be.
Very :cool: !
I do know for a fact that there is absolutely nothing wrong with the drive it's a brand new Maxtor 20GB.

[Alex Cavnar, aka alc6379]

I was able to just boot from the Slackware CDROM, mount my / partition under mount, and do "chroot /mnt lilo". That solved my problem!

[bwkaz]

Originally posted by Alex Cavnar, aka alc6379:
<STRONG>I was able to just boot from the Slackware CDROM, mount my / partition under mount, and do "chroot /mnt lilo". That solved my problem!</STRONG>

:eek:

I'm surprised that worked. Supposedly LILO has problems running under a chroot environment (at least according to the LFS 3.0 book)...

Guess they fixed it or something.

[Alex Cavnar, aka alc6379]

It works any time I funk up my boot loader, come to think of it...

[Lorithar]

*grins*

Versions are important...
Older versions of lilo required you to chroot the *shell* in which you executed lilo to whack the loader, more recent lilo (certainly anything I've used in the last year) have *no* problems with the chroot shell/switch ...