WooHoo! I know everyone has been working on this, so I pinged a friend on
it and here's his response. This may help:
- M.S.
---------------------- Forwarded by Micah J
Snodgrass/CONTRACT/CedarRapids/Collins/Rockwell on 08/23/2001 01:39 PM
---------------------------
To: [EMAIL PROTECTED]
cc:
Subject: Re: SanDisk boot problems
Micah,
Well, I don't know off of the top of my head what that would be, but I
know each letter of the word LILO means something. There is a _very_ nice
doc. about it in:
/usr/doc/lilo-v-whatever-you-have/README
if you installed the Docs. At least on Slackware systems...
Here is an interesting clip from that file:
When LILO loads itself, it displays the word "LILO". Each letter is printed
before or after performing some specific action. If LILO fails at some
point, the letters printed so far can be used to identify the problem. This
is described in more detail in the technical overview.
Note that some hex digits may be inserted after the first "L" if a
transient disk problem occurs. Unless LILO stops at that point, generating
an endless stream of error codes, such hex digits do not indicate a severe
problem.
(<nothing>) No part of LILO has been loaded. LILO either isn't installed
or the partition on which its boot sector is located isn't active.
L <error> ... The first stage boot loader has been loaded and started,
but it can't load the second stage boot loader. The two-digit error
codes indicate the type of problem. (See also section "Disk error
codes".) This condition usually indicates a media failure or a geometry
mismatch (e.g. bad disk parameters, see section "Disk geometry").
LI The first stage boot loader was able to load the second stage boot
loader, but has failed to execute it. This can either be caused by a
geometry mismatch or by moving /boot/boot.b without running the map
installer.
..."geometry mismatch" huh... Cylinder number issue? That file is worth a
read.
Hope that helps!
-Steve
Any idease Geoff, Steve?
---------------------- Forwarded by Micah J
Pete <[EMAIL PROTECTED]>@waste.org on 08/22/2001 09:01:53 AM
Sent by: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Sandisk boot problems
I've been trying (and failing) to get linux booting
off of a 16 meg san disk card. (It's recognized by the
bios as a SunDisk.)
I'm using lilo, and if I tell it to use lba32, when
booting, I see a L followed by 02 02 02...
If I turn off lba32 all I get is an L.
I fdisked and formatted the card with an ext2
filesystem.
Any ideas what this is indicative of?
My lilo.conf:
boot=/dev/hdc
root=/dev/hdc
install=/mnt/boot/boot.b
vga=normal
image=/mnt/boot/vmLinuz
label=linux
root=/dev/hdc1
read-only
This sandisk came out of a Siemens PC, and it had
linux on it at one time, it was sold as a 'net'
workstation, so I know that the card was able to boot
it at one time.
--
To unsubscribe from this list, send a message to [EMAIL PROTECTED]
with the command "unsubscribe linux-embedded" in the message body.
For more information, see <http://waste.org/mail/linux-embedded>.
