[H-GEN] Usb Mass Storage

[Joe]

[ Humbug *General* list - semi-serious discussions about Humbug and     ]
[ Unix-related topics. Posts from non-subscribed addresses will vanish. ]

Hello,
 I purchased a Usb ram drive (with a built in mp3 player) today and ran
into a little trouble, I am looking for a few opinions on this from
smart people like yourselves :).

I played with it for awhile, nice little device. Decieded to try Linux
support (I just aquired a motherboard that can boot from usb, I'm
interested in trying Linux on a ram drive :).

Recieved these messages from the kernel driver:

usb-storage: act_altsettting is 0
usb-storage: id_index calculated to be: 89
usb-storage: Array length appears to be: 91
usb-storage: USB Mass Storage device detected
usb-storage: Endpoints: In: 0xc1e781c0 Out: 0xc1e781d4 Int: 0x00000000
(Period 0 )
usb_control/bulk_msg: timeout
usb-storage: New GUID 101100010004710765066451
usb-storage: GetMaxLUN command result is 1, data is 0
usb-storage: Transport: Bulk
usb-storage: Protocol: Transparent SCSI
usb-storage: *** thread sleeping.
usb-storage: queuecommand() called
usb-storage: *** thread awakened.
usb-storage: Command INQUIRY (6 bytes)
usb-storage: 12 00 00 00 ff 00 26 d7 63 09 25 c0
usb-storage: Bulk command S 0x43425355 T 0x1 Trg 0 LUN 0 L 255 F 128 CL
6
usb-storage: Bulk command transfer result=0
usb-storage: usb_stor_transfer_partial(): xfer 255 bytes
usb-storage: usb_stor_bulk_msg() returned 0 xferred 254/255
usb-storage: Bulk data transfer result 0x1
usb-storage: Attempting to get CSW...
usb-storage: Bulk status result = 0
usb-storage: Bulk status Sig 0x53425355 T 0x1 R 0 Stat 0x0
usb-storage: Fixing INQUIRY data to show SCSI rev 2
usb-storage: scsi cmd done, result=0x0
usb-storage: *** thread sleeping.
usb-storage: queuecommand() called
usb-storage: *** thread awakened.
usb-storage: Bad LUN (0/1)
usb-storage: *** thread sleeping.
usb-storage: queuecommand() called
usb-storage: *** thread awakened.
usb-storage: Bad target number (1/0)

continued like this till target no. 6 then:

usb.c: usb-storage driver claimed interface c1f3fd80.

At first I figured the errors were due to it having a slot for a flash
card that was empty, windows had detected this slot also.

Then I noticed the lcd on the unit which normally has Usb C on it was
blank, the mp3 part of it would no longer power on and after a reboot
into windows that the ram drive was patchy also.

Could a bad message from a driver do that much damage ? I am praying
they will replace it, as it wasn't cheap, but I don't really want it if
it's not useable with Linux.

Grateful for any input,
	Joe Skilton


--
* This is list (humbug) general handled by majordomo at lists.humbug.org.au .
* Postings to this list are only accepted from subscribed addresses of
* lists 'general' or 'general-post'.  See http://www.humbug.org.au/