Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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.
Getting a LI w/blinking underscore on reboot and can't type.
SW 9.1 install. I'm a noob so pardon my ignorance.
I've already read through all similar posts and tried reconfiguring LILO in all possible combinations and still getting just the LI with a blinking underscore at bootup. Only option I have not done is installing LILO to floppy.
Using a stand-alone Slackware Linux installation... no other OS. Fresh hard drive, completely wiped.
hmm, this might be one of those flukey things that someone with more experience would know about. until then, what i would do is run the liloconfig utility again and this time set up lilo on a boot floppy. if that boots, that might help isolate the problem as being something to do with your hard disk, boot sector, etc. you have booted into this system before, right? i mean, your partitions are initialized or whatever to be able to boot?
I had to manually edit the lilo.conf file (after a quick lesson using vi). It seems thats running liloconfig was creating a problem in one line of the file.
boot = /dev/hda2
(my actual boot partition)
...needed to be changed to boot = /dev/hda
... even though I had specifically typed /dev/hda in liloconfig. It seems to me that liloconfig is picking-up the wrong path designation when it writes lilo.conf.
This problem/solution had been mentioned in other threads also. Thanks for the response synaptical!
Another noob problem solved... I'm off to find another!
Last edited by Snagglepuss; 12-27-2003 at 06:49 AM.
yeah that is totally weird, because the lilo.conf you posted looked okay. so you type "/dev/hda" in liloconfig, and it puts "dev/hda2" in the lilo.conf file? weird. maybe that's why i never use those configuration tools and like to learn how to do everything by hand. no mysteries.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.