Hi Magnus,
When I played with the Sandisk, I had similar problems. I
think that the timing limits in the IDE driver should be
changed. I tweaked them out pretty far and that seemed to
do the trick. I haven't played with this for about a year,
so I can't give you more detail than that.
HTH,
John Lombardo
>
> Hello everyone.
>
> I'm currently evaluating the possibilities and
> disadvatages of using linux in an
> embedded pump controller. We are using the elan
> SC4x0 chip, and I have tried
> both AMD's evaluation board (yes, I know, that
> specific board have been discussed
> here for quite a while;) and the JumpTec DimmPC.
>
> The problem with appropriate flash memory drivers
> for Linux that seem to have been bothering some people
> here was initially the main problem for me. Until
> I tried the DimmPC (and also the sandisk
> flash ChipSet). The DimmPC uses a sandisc 16 mb
> flash disk with the FCS system, allowing the hardware
> to completely emulate an IDE interface. This way,
> you get rid of not only the flash driver problems
> in Linux but also the whole boot process is
> simplified. (initial ramdisk etc goes down the drain)
>
> But when mounting the disk in Linux, I get the following:
>
> hda: hda1
> hda: drive_cmd: status=0x51 { DriveReady
> SeekComplete Error }
> hda: drive_cmd: error=0x04 { DriveStatusError }
> hda: hda1
>
> but the drive is mounted alright and everything
> seems to work
>
> when I unmount the drive and mount it again I only get
>
> hda: hda1
> hda: hda1
> hda: hda1
>
> My questions are:
>
> * why the error stuff above? what does it mean?
> * why is [hda: hda1] written to console. Normally
> when you mount a IDE drive I don't
> get any messages. I believe that the sandisk chip
> completely emulates an IDE driver.
>
> best regards
>
> magnus oerstroem
>
>
>
> _______________________________
> Magnus Öhrström, Flygt MST
> please email to [EMAIL PROTECTED]
>
