[SOLVED] Crashed my shiny new Slackware system into the 99 error wall.
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.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Did that allow you to boot up correctly?: I think so, but Kword & Kspread (maybe more) don't work.
can you save the output of the last time you ran lilo?
I have this:
bash-4.1# lilo -v -t -b /dev/sda8
LILO version 22.8 (test mode), Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2006 John Coffman
Released 19-Feb-2007 and compiled at 14:44:48 on Feb 16 2010
Warning: Ignoring entry 'boot'
Reading boot sector from /dev/sda8
Warning: Unable to determine video adapter in use in the present system.
Using BITMAP secondary loader
Mapping bitmap file /boot/slack.bmp
Warning: Video adapter does not support VESA BIOS extensions needed for
display of 256 colors. Boot loader will fall back to TEXT only operation.
Boot other: /dev/sda1, on /dev/sda, loader CHAIN
Added Windows_XP *
Boot image: /boot/vmlinuz-generic-smp-220.127.116.11-smp
Mapping RAM disk /boot/initrd.gz
Boot image: /boot/vmlinuz -> vmlinuz-huge-smp-18.104.22.168-smp
The boot sector and the map file have *NOT* been altered.
3 warnings were issued.
Have you tried lilo -M: No, I have not tried this yet, should I??
99 invalid second stage index sector (LILO)
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 mismatch between what LILO used (lilo -v3 to display) and what is actually being used by the BIOS (one of the lilo diagnostic disks, available in the source distribution, may be needed to diagnose this problem).
Read more in man lilo, it's a nice source of information.
Anyway, checking how /etc/lilo.conf looks (after your boot from dvd with root=/dev/sda8), and validating that output to be correct, lilo -M will install a new MBR. Also check that /boot/System.map is correct and actually points to an existing file or is a valid file itself.)
If in doubt, you can re-install the kernel from your dvd and rerun lilo again. That should fix your problem.