SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Ok. Just helped my younger brother install Slackware and now he has a problem. I have done like 20 Slack installs and never had an issue. I even installed here to a new partition so I could walk him through step by step over the phone.
What happens is, we get through the entire install, using 'expert' during lilo, everything appears fine. Reboot when prompted, and wind up with a black screen with a capital L inthe upper left corner with a blinking cursor. Nothing happens after this.
We performed a reinstall. Same thing. Then I had him boot from the Slackware Live cd, mount the slack parition, chroot over to it, and do /sbin/lilo to try reinstalling lilo. It appeared to work (no errors), but then after reboot we get the same black screen the the L. No lilo menu, nothing.
L <error> ... The first stage boot loader has been loaded and started,
but it can't load the second stage boot loader. The two-digit error
codes indicate the type of problem. (See also section "Disk error
codes".) This condition usually indicates a media failure or a geometry
mismatch (e.g. bad disk parameters, see section "Disk geometry").
from the Lilo readme. what kinda HDD does he have?
I don't understand your question. Where is the lilo readme? And by HDD you mean?
His device is a Maxtor IDE, and it's HDA. Same 160gb as I have matter of fact.
All I can think of, is the install media is corrupt somehow or another. He has a completely vanilla Hewlitt Packard with an Intel 815 chipset, integrated graphices, etc. I owned one some time ago and had no problems installing any linux distro. Problem is, he is 700 miles away and now has no access to Windows or Linux so obviosly, no internet access to download any kind of helpful utilities OR an new Slackware cd set.
Originally posted by Scruff I don't understand your question. Where is the lilo readme? And by HDD you mean?
His device is a Maxtor IDE, and it's HDA. Same 160gb as I have matter of fact.
HDD stands for Hard Disc Drive and you already answered the question
Anyway, the error message is that there's nothing beyond that L and that is what I wanted to tell you. I'm hardly being an expert on this field that's why I only posted that part of the readme which is accessable at /usr/doc/lilo-<insert his versionnumber here>/README
You can BTW boot your system with mount root=/dev/hdxy (change the numbers according to your setup) at the boot prompt of the installation disk.
How old is his BIOS. Does he maybe have this issue because the linux partition lies beyond the 1024 cylinders? Maybe a BIOS upgrade helps.
160GB on an older board seems to be the trouble here but I'm afraid, I can't help any further.
Oh and have you tried installing Lilo in the superblock of the linux partition rather than the MBR? then of course the Linux partition has to be the active partition and in Lilo you can tell the PC to boot Windows (9x or ME it appears)
I am almost positive his BIOS is ok with the 160gb drive. He's been using it for awhile, though it could be under some Windows software emulation this, rather than the BIOS. What we ultimately decided, is for me to mail him a copy of the Slack cd's I purchased from Slackware so we can at least rule out corrupt cd's. He fooled around with some retarded md5 check util in Windows that never really accomplised anything, so...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.