SlackwareThis Forum is for the discussion of Slackware Linux.
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.
I'm trying out Slack for the first time. The install seems to go ok - but when I reboot I just get an 'L' and then loads of '9's. I've tried installing lilo on the mbr and on the hard drive ( making the right partition bootable of course. ). I've also tried making a separate /boot partition and stuff like that. I've run out of ideas now.
I'm using an adaptec scsi pci card.. I'm pretty sure i'm choosing the right kernel because the rest of the install goes ok. The whole install is going on the scsi drive connected to this card.
Yeah sorry - i'm at work and in a bit of a rush - also the hardware is new (and at home)so i'm not entirely sure of the specs.
I'm not dual booting.
AOpen ATX motherboard .... mmm Ax3s or something like that.
sb128 pci ens1370 sound card.
Maxtor ide hard drive that is blank ( master on the first ide bus ).
Adaptec pci scsi card - with seagate hard drive connected to that.
I also don't have a floppy drive so can't make a boot floppy. (I was thinking of experimenting with /boot on the maxtor...)
thanks again.. if you need any more info just ask.
I had an error just like yours when I changed /etc/lilo.conf and forgot to run lilo. So what you might want to do is install everything and then get to prompt ( This was available on my install, so should be in yours) and run lilo. I think it will give and error ( it might help).
From the problem, it seems you will need to pass some extra parameters to lilo ( I just dont know which, I never installed linux on a notebook, its a notebook right??))
Try searching Google/linux for your hardware and see if anyone else had the same issue.