It works!? I changed adaptor boards (PC Engines) and this one
works better...
Some observations:
1. First time the device partition table is accessed, errors are
reported
2. fdisk detects 1 more cylinder than the original device is formatted
with
3. Assigining too many blocks in the parition table kills the device
4. Not all IDE adaptor cards work the same way
5. IDE cables can act as fuses :-O
===========
>From the "Not Sure Why Department"...
===========
Using a Sandisk CF device, I partitioned it with fdisk and got
the errors mentioned below. The format and loading worked great, I
rebooted and it worked - but still generated error messages!
It seems the error with the flash card has something to do with the
first
time the drive partition table is accessed. When booting (my
understanding
of what the Kernel boot sequence is (RH 6.1, 2.2.12-20 Kernel):
1. the BIOS detects the card, runs LILO from hda
2. the boot image is loaded from the flash card
3. the Kernel finds the drive table (?)
4. the Kernel probes the device (prints C/H/S...)
5. the Kernel does a partition table check, generating the following:
...
Partition check:
hda: hda1 hda2 hda3 < hda5 >
hdb: hdb1
hdc: hdc1
hdb: hdb1
hdb: drive cmd: status=0x51 {DriveReady SeekComplete Error}
hdb: drive cmd: error=0x04 { DriveStatus Error }
hdb: hdb1
VFS: mounted root (ext2 filesystem)...
After this, fdisk on the device produces no errors. Copy/check/etc...no
problems (with Sandisk).
==========
I *had* a 15MB Sandisk card which I partitioned with fdisk. I took the
defaults, where the last cylinder is one more than the number of
cylinders
shown when the device arrived from the factory (DOS formatted).
After that when I boot with this card (CF is slave device - hdb; boot
from hda), I get massive read errors and sector not found errors and
a kernel panic...
DOS fdisk can't even read the device, but the BIOS still identifies
it...
Hmmm...can I plug this in "hot", after the system boots ?
Square Coasters anyone ?
==========
On yet another attempt, I plugged a Disk-On-Module in to a ribbon cable.
It was meant to be plugged into the motherboard, but Hey, I figured, why
not
use a ribbon cable ?...well, since the ribbon cable is female, I got a
header
and plugged it in then plugged in the Disk-On-Module device. *POOF**
smoke
and everything...really cool, the IDE center conductors burnt off the
insulation and then just stopped working. The Disk-On-Module still
works.
Ooops, ribbon cables get "flipped" by the connectors or something..What
was I thinking ?!
=========
Anyhow, I just hope the CF interface works with every card...maybe I
just
got lucky and the next card won't work :-( The DOC (M-Systems) and
Disk-On-Module (PQI) flash devices seem to work OK with no errors
generated.
Thank,
Ralph
more...
Jerry Van Baren wrote:
>
> I'm running RedHat 6.1 on my laptop and the CF cards just work. The
> cards show up as /dev/hde however, not /dev/hdb. Plug in your card and
> watch the messages in /var/log/messages (I think, possibly also to the
> console) to see what your computer is doing with the card. It should
> have two beeps, showing that the card was recognized. It should also
> print out the card's manufacture -- this shows that linux is
> recognizing and reading the card, at least the low level ID info. This
> is recognizing the CF hardware, not the partitioning and formatting.
>
Yep, that part works fine...
> I'm running CF cards (one 8Mbyte and one 64Mbyte) that plug into my
> digital camera and were formatted by the camera to be a DOS file
> system. I never tried to format the CF myself.
>
I think this is where the problem is...maybe fdisk needs updating
for CF devices ??
> I'm a little confused with your description: first you say you have
> errors fdisking the CF and then you say that you fdisk OK but have
> problems formatting it. If you are getting errors running fdisk, all
> bets are off on the format process.
>
Thats what I thought, but it still seems to work...not sure why...
I just get those pesky error messages.
> gvb
>
> At 09:27 AM 3/7/00 -0600, you wrote:
> >Hello,
> >I just got an IDE adaptor for compact flash cards with a few different
> >compact flash cards (Sandisk 32MB and PQI 32MB).
> >
> >Is there a special driver needed to make these work with Linux 2.2.12 ?
> >
> >When I try to fdisk the device:
> >fdisk /dev/hdb
> >
> >I get the error message
> >hdb: drive cmd: status=0x51 {DriveReady SeekComplete Error}
> >hdb: drive cmd: error=0x04 { DriveStatus Error }
> >
> >It seems like these are slower than the IDE driver expects or
> >something like that maybe...
> >
> >I can Fdisk the device, then when I format it as ext2, the partition
> >table gets trashed. My BIOS settings are set to AUTO detect and
> >the drive information is read when I reboot. However, If I change
> >these settings and play with the LBA / BLOCK mode / CHS stuff - setting
> >these to the values detected by the BIOS, *sometimes* it just hangs
> >the system.
> >
> >Any clues on what to do next ?
> >
> >Thanks in advance,
--
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>.
