Greetings-

I'm not a total newbie, but I'm having a problem and I can't seem to find any reason for at all and would like some help finding a resoution...

I recently got the download edition ( from linux forum)- it seemd to install correctly, but when I tried to reboot, I got as far as the POST and ram check, then it froze at what looks like a prompt that looks like :

LI_

I'm stumped- this happened on three different machines (two desktops and a laptop), and happened with those disks, and also another disk I downloaded myself. I've tried every variation I can think of: the kernal I am using should be right ( the default plain vanilla bare-ide), and I've tried different permutations of LILO and partitioning to no avail.

thanks in advance-

G

The problem is definitely a lilo issue. That is what the display means, the first two letters of LILO. The second stage of the loader is not completing. I am not sure what you mean by "download edition" if the reference is to Slack.

I would think you probably need to post your lilo.conf and little something about your machine config, so somebody can review it.

I have experienced the same issue as you have here. I first touched Slackware 8.1 at Uni, where it was used as a tutorial/lab for a networking subject. I believe EVERYONE in the computer lab (pretty much the same hardware in each machine) experienced this error.

The only fix that we found was to use the boot disk that was created during the installation process. It actually got past LILO; the boot drive/partition was specified to carry on with the boot process.

However only being a temporary fix, it is a fix. I can only assume it is dependant on hardware. I'm not too sure what exact specs the PCs had, but I believe they housed Pentium II CPUs. A full installation at home on a P3 Compaq machine hasn't caused me any issues -yet-.

I'm interested to know what exactly is causing the issue to occur. Could be something simple, or something complex. It's just something I have not seen the answer to...

I don't know what other things cause this, but from my experience, I have had this happen when I install Linux on a hard drive that isn't set to master on the IDE controller. I have also seen LILILILILILILILILILILILILILILILILILILILILILILILILILILILILILILILILILILILILILILILILILILILILILILILILILI LILILILILILILILILILILILILILILILILILILILI

go accross the screen and it never gets beyond that. Anyway, just an idea for you.