a bit more information:

The foxboard is working at 4.73v loaded, so it could be that KINGSTON 
is very sensitive, than i got foxboard alone with 5.09v and it took a 
while to return the same error. SCSI disk error : .... return code = 
70000.  Error 0x7 is Internal Error.

Things get worst with kernel 2.6.15 for the LX832, it refuses to get 
a valid address and disconnect and tells me to "check cable"..

I have 2 classic foxboard and 2 LX832, all the same error.

Anyone got a DataTraveler model working with foxboard?
I would apprciate any information.

Regards,
Alexander



--- In [email protected], "xfingerfox32" <[EMAIL PROTECTED]> wrote:
>
> Hello,
> 
> I have read that many of you can mount a memory stick, but i am 
> unable to do so in kernel 2.4 and 2.6, default fimage or not.
> 
> I am using 2 KINGSTON memory stick, 2 GB and 512 MB, and both fails.
> when i mount it "mount -t vfat /dev/sda1 /mnt1" i get the message:
> 
> usb-host.c: USB controller running.
> hub.c: new USB device ETRAX 100LX-1, assigned address 2
> scsi0 : SCSI emulation for USB Mass Storage devices
>   Vendor: Kingston  Model: DataTraveler 2.0  Rev: PMAP
>   Type:   Direct-Access                      ANSI SCSI revision: 02
> Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
> SCSI device sda: 4030464 512-byte hdwr sectors (2064 MB)
> sda: Write Protect is off
> Partition check:
>  sda: sda1 sda2 sda3 sda4
> WARNING: USB Mass Storage data integrity not assured
> USB Mass Storage device found at 2
> usb-host.c: Got epid attn for bulk endpoint, epid 0
> usb-host.c: Stall for epid 0
> usb-host.c: Completing bulk urb with status -32.
>  I/O error: dev 08:01, sector 0
> FAT: unable to read boot sector
> 
> I have tried FAT and FAT32, all failed and my linux box reads and 
> writes fine, also my XP box.
> 
> Perhaps KINGSTON works only on USB 2.0? i dont have any other maker 
> to try.
> 
> Have anyone get it working?
> 
> If someone can mount it, or have an idea of what i am doing wrong, 
> please point it out.
> 
> Regards
> 
> Alexander
>


Reply via email to