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.
i had slack 9.1 working and everything was fine. I set up VNC and SSH and was playing around with the stuff VNCing and SSHing from windows laptop. Then I went to the linux box and tried to start some apps. I wasn't able to run anything and it looked like it froze. So I tought a reboot would help. I went into root and did reboot command, but I didn't reboot but stopped at full screen of command prompts. Then I restarted manually and now when the pc boots up it doesn't go to LILO but displays half page of 99999. any ideas? what should I do? i don't have floppy drive in that box. thanks in advance
I've had this happen to me. As far as I can tell it means that your bios cannot find anything it can boot so it just spits out nines. As well as booting off cd2 you can boot cd1 and use it as a boot loader to boot the slack on your hard drive. Unfortunately I usually endup reformatting in this situation.
This has happened to me as well. I think it is a result with the partitions being formatted incorrectly, or the partition table not matching the partition format. I discovered that installing lilo to the MBR fixes the problem. You might also check your fstab.
i didn't have CD2, so I used install and send root=/dev/hda6 ro as a parameter to the kernel and from there I was able to rerun /sbin/lilo and write it to the MBR again. now everything works fine.
Originally posted by spec6635 use slackware disk number 2 and bootup your root installation and look at your /etc/lilo.conf file, if all is well then run /sbin/lilo then reboot
Fantastic!
I had to use this fix this morning and it worked! I downloaded the most recent release of the SLAX live cd and ran it on my Slack box and afterwards when I tried to boot from the hard drive, it just froze. I don't know if SLAX did something to cause this but it's good to know there is such a wealth of knowledge to consult to solve such problems.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.