Re: GRUB won't boot Suse 8.2 (fresh install)
From: Michael Forster (admin_at_muckworld.com)
Date: 08/03/03
- Next message: Michael Forster: "Re: GRUB won't boot Suse 8.2 (fresh install)"
- Previous message: Matt H: "Re: what distro for my router?"
- In reply to: NoSpam: "Re: GRUB won't boot Suse 8.2 (fresh install)"
- Next in thread: Michael Forster: "Re: GRUB won't boot Suse 8.2 (fresh install)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 3 Aug 2003 09:11:55 +0100
"NoSpam" <nobody@nowhere.com> wrote in message
news:qdhoiv89l5jhomhfmbs44sack7vhlh8ult@4ax.com...
> On Sat, 02 Aug 2003 19:59:22 +0100, Ian Northeast
> <ian@house-from-hell.demon.co.uk> wrote:
>
> >In a case like this it can sometimes help to replace grub with LILO
> >temporarily. LILO is more verbose with BIOS error messages. This is how
> >I diagnosed the one I mentioned. See
> >http://sdb.suse.de/en/sdb/html/fhassel_grub_lilo.html, although as this
> >refers explicitly to 8.1 it may not be totally correct.
> >
> >Regards, Ian
>
> I actually tried LILO and it wasn't real descriptive either. When it
> tried to boot, it printed out the number "99" a whole lot of times,
> then locked up.
>
99 is not a lilo boot message,It is a Bios code error
So it is likely to be a BIOS error not a Lilo Error
AS you can see below 99 is not a known code - what Version of bios is your
machine - check up what code 99 is?
Mike.
If the BIOS signals an error when LILO is trying to load a boot image, the
respective error code is displayed. The following BIOS error codes are
known:
0x00
"Internal error". This code is generated by the sector read routine of the
LILO boot loader whenever an internal inconsistency is detected. This might
be caused by corrupt files. Reinstall IPCop or recreate the boot media.
0x01
"Illegal command". This shouldn't happen, but if it does, it may indicated
an attempt to access a disk which is not supported by the BIOS.
0x02
"Address mark not found". This usually indicates a media problem. Try
again several times.
0x03
"Write-protected disk". This sould only occur on write operations.
0x04
"Sector not found". This typically indicates bad disk parameters in the
IPCop PC's BIOS. If you are booting from a large IDE disk, you should check
whether the IPCop PC's can handle the disk.
0x06
"Change line active". This sould be a transient error. Try booting a
second time.
0x07
"Invalid initialization". The BIOS failed to properly initialize the disk
controller. You should control the BIOS setup parameters. A warm boot might
help, too.
0x08
"DMA overrun". This shouln't happen. Try booting again.
0x0C
"Invalid media". This shouldn't happen and might be caused by a media
error. Try booting again.
0x10
"CRC error". A media error has been detected. Try booting several times,
and if all else fails, replace the media.
0x11
"ECC correction successful". A read error occurred by was corrected. LILO
does not recognize this condition and aborts the load process anyway. A
second load attempt should succeed.
0x20
"Controller error". This shouldn't happen.
0x40
"Seek failure". This might be a media problem. Try booting again.
0x80
"Disk timeout". The disk or the drive isn't ready. Either the media is bad
or the disk isn't spinning. If you're booting from a floppy, you might not
have closed the drive door. Otherwise, trying to boot again might help.
0xBB
"BIOS error". This shouldn't happen. Try booting again.
- Next message: Michael Forster: "Re: GRUB won't boot Suse 8.2 (fresh install)"
- Previous message: Matt H: "Re: what distro for my router?"
- In reply to: NoSpam: "Re: GRUB won't boot Suse 8.2 (fresh install)"
- Next in thread: Michael Forster: "Re: GRUB won't boot Suse 8.2 (fresh install)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
