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.
13.1 was running ok for a few days but would then not boot up. Reinstalled and got lots of 99's when trying to boot. Ran RIPLinux (but this not a tool that I know well) and saw strange numbers, ie > 100% for a test of the cylinders, I think. So question is - how to test everything? Hardware for the moment since Slack not running.
99s sounds like a boot loader fault to me. If the disk is bad, it tells you, or it just sits there for a long time and says nothing, or makes evil sounding clacking noises.
Slackware in general uses lilo. I use grub, but I'd look there - /etc/lilo.conf and then run lilo. Man lilo - I've forgotten all about it.
Yes you could be right but for the moment nothing works so how do I start testing the most basic things, hard-disk for example and memory and so on and so which tool to use?
For memory you can use Memtest86+, for the harddisk I would recommend the Hitachi Drive Fitness Test, despite its name it will test harddisks from all manufacturers.
Both tests have to be burned as an image to CD.
So I tried the simplest way (because nothing to lose on hd) and reinstalled Slack. And this time it worked. So my next question - of a slightly different nature - if it LOOKS like it works, Slack 13.1 I mean, how can I check the installation?
I don't think re-installing was necessary. Rather, according to TFM, what an error code 99 means is:
Quote:
Errors 99 and 9A usually mean the map file (-m or map=) is not readable, likely because LILO was not re-run after some system change, or there is a geometry mis-match between what LILO used (lilo -v3 to display) and what is actually being used by the BIOS...
I don't think re-installing was necessary. Rather, according to TFM, what an error code 99 means is:
Quote:
Errors 99 and 9A usually mean the map file (-m or map=) is not readable, likely because LILO was not re-run after some system change, or there is a geometry mis-match between what LILO used (lilo -v3 to display) and what is actually being used by the BIOS...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.