You are correct. Early firmware versions of the Sandisk (sundisk) did not
respond with the "drive door" status command(s). Firmware versions vdd1.02
and the like correctly report something to the effect "command not
supported". We went round and round with Sandisk on this one earlier this
year but got nowhere. A fantastic engineer with IBM's Microdrive division
recognized the problem right away (we had the same problem with Microdrive).
The good news is that it can be patched. We fixed kernel 2.0.18 just fine.
For the most part the drive will continue to work unpatched despite the
error messages but there are certain commands that will not work. Lilo is
one of them.
If my memory serves me correct, take a look at the latest kernel source and
compare the ide.c file of the kernel you are using. Ed here at our office
is the one who patched our image. He comes in later and I will ask him to
post a suggestion. He also monitors this list.
John Markham
EnFlex Corp.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Clemens Kuhnle
Sent: Monday, November 20, 2000 6:13 AM
To: Linux Embedded Mailing List
Subject: Flash Disk Error
Hello
I read the previous messages about Flash Disks, but i did not get a hint
to my problem:
I'm using different kinds of Flash Disks.
For example Sundisk and OEM Sundisk.
When booting with OEM Sundisk the kernel prints the following messages:
hda: SunDisk SDTB-128, 15MB w/1kB Cache, CHS=490/2/32
Partition check:
hda: hda1
VFS: Disk change detected on device ide0(3,1)
hda: hda1
hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hda: drive_cmd: error=0x04 { DriveStatusError }
The error messages don't not occur with the original SunDisk Flash
Disk.
Can sb tell me what this error messages mean?
The system is running on both Flash Disks quit good wuithot any problems
but what is the difference?
I sent the same question to SunDisk and got the following answer:
We have seen this problem before. There is a problem with the Linux IDE
driver. I believe the failing card is reporting itself as a Removable
Drive.
Linux then gives the card a command such as "close the Door" or "Open
the
Door", and the card rejects the command, returning status=0x51. 0x51
means
Ready, Seek Complete and Error (not a Seek Complete Error). error=0x04
means
the command was aborted, because the command was an unsupported command
to
the card.
Can i patch the problem, or are the error messages not really errors?
Many Thanks
Clemens
--
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>.
--
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>.
