JMTek USBDrive help

JMTek USBDrive help

Post by qwm.. » Sun, 27 Jan 2002 07:56:29



Hi,
   I'm trying to connect a 256MB JMTek USBDrive to my Linux 2.4.17.
However, so far to no avail. I've used the patch from usb-linux.org,
but I had to change the vendor ID and product ID to match the newer
device (or so I presume). I ended up with US_SC_SCSI, US_PR_BULK &
US_FL_START_STOP. When I connect the device it times out on every
command, and an attempt to view /proc/scsi/* causes segmentation
faults, some unsavoury log message and a hung scsi_mod.
   Following is a log of the device connection:

Jan 23 22:59:10 x kernel: hub.c: port 1 connection change
Jan 23 22:59:10 x kernel: hub.c: port 1, port status 101, change 1, 12
Mb/s
Jan 23 22:59:10 x kernel: hub.c: port 1, port status 103, change 10,
12 Mb/s
Jan 23 22:59:10 x kernel: hub.c: USB new device connect on bus 1/1/1,
assigned device number 6
Jan 23 22:59:10 x kernel: usb.c: kmalloc IF c03cfec0, numif 1
Jan 23 22:59:10 x kernel: usb.c: new device strings: Mfr=0, Product=0,
Serial Number=0
Jan 23 22:59:10 x kernel: usb-storage.c: act_altsetting is 0
Jan 23 22:59:10 x kernel: usb-storage.c: id_index calculated to be: 56
Jan 23 22:59:10 x kernel: usb-storage.c: Array length appears to be:
76
Jan 23 22:59:10 x kernel: usb-storage.c: Vendor: JMTek
Jan 23 22:59:10 x kernel: usb-storage.c: Product: USBDrive 256MB
Jan 23 22:59:10 x kernel: usb-storage.c: USB Mass Storage device
detected
Jan 23 22:59:10 x kernel: usb-storage.c: Endpoints: In: 0xc3cf7be0
Out: 0xc3cf7bf4 Int: 0xc3cf7c08 (Period 0)
Jan 23 22:59:10 x kernel: usb-storage.c: New GUID
0xb8651100000000000000000
Jan 23 22:59:10 x kernel: usb-storage.c: GetMaxLUN command result is
1, data is 0
Jan 23 22:59:10 x kernel: usb-storage.c: Transport: Bulk
Jan 23 22:59:10 x kernel: usb-storage.c: Protocol: Transparent SCSI
Jan 23 22:59:10 x kernel: usb-storage.c: *** thread sleeping.
Jan 23 22:59:10 x kernel: scsi0: SCSI emulation for USB Mass Storage
devices
Jan 23 22:59:10 x kernel: usb-storage: queuecommand() called
Jan 23 22:59:10 x kernel: usb-storage: *** thread awakened.
Jan 23 22:59:10 x kernel: usb-storage: Command INQUIRY (6 bytes)
Jan 23 22:59:10 x kernel: usb-storage: 12 00 00 00 ff 00 00 00 21 00
00 00
Jan 23 22:59:10 x kernel: usb-storage: Bulk command S 0x43425355 T 0x1
Trg 0 LUN 0 L 255 F 128 CL 6
Jan 23 22:59:10 x kernel: usb-storage: usb_stor_transfer_partial():
xfer 255 bytes
Jan 23 22:59:16 x kernel: usb-storage: command_abort() called
Jan 23 22:59:16 x kernel: usb-storage: usb_stor_bulk_msg() returned -2
xferred 0/255
Jan 23 22:59:16 x kernel: usb-storage: usb_stor_transfer_partial():
transfer aborted
Jan 23 22:59:16 x kernel: usb-storage: Bulk data transfer result 0x3
Jan 23 22:59:16 x kernel: usb-storage: -- transfer indicates command
was aborted
Jan 23 22:59:16 x kernel: usb-storage: Fixing INQUIRY data to show
SCSI rev 2
Jan 23 22:59:16 x kernel: usb-storage: scsi command aborted
Jan 23 22:59:16 x kernel: usb-storage: *** thread sleeping.
Jan 23 22:59:16 x kernel: usb-storage: queuecommand() called
Jan 23 22:59:16 x kernel: usb-storage: *** thread awakened.
Jan 23 22:59:16 x kernel: usb-storage: Command TEST_UNIT_READY (6
bytes)
Jan 23 22:59:16 x kernel: usb-storage: 00 00 00 00 00 00 00 00 21 00
00 00
Jan 23 22:59:16 x kernel: usb-storage: Bulk command S 0x42435355 T 0x1
Trg 0 LUN 0 L 0 F 0 CL 6
Jan 23 22:59:16 x kernel: usb-storage: Bulk command transfer result=0
Jan 23 22:59:16 x kernel: usb-storage: Attempting to get CSW...
Jan 23 22:59:26 x kernel: usb-storage: command_abort() called
Jan 23 22:59:26 x kernel: usb-storage: -- transport indicates command
was aborted
Jan 23 22:59:26 x kernel: usb-storage: scsi command aborted
Jan 23 22:59:26 x kernel: usb-storage: *** thread sleeping.
Jan 23 22:59:26 x kernel: usb-storage: device_reset() called
Jan 23 22:59:26 x kernel: usb-storage: Bulk reset requested
Jan 23 22:59:26 x kernel: usb-uhci.c: interrupt, status 3, frame# 765
Jan 23 22:59:26 x kernel: usb-storage: Bulk soft reset failed -75
Jan 23 22:59:26 x kernel: usb-storage: bus_reset() called

   Does anyone have a clue to the correct settings?

   Thanks.

 
 
 

JMTek USBDrive help

Post by Brian Ha » Wed, 30 Jan 2002 01:56:44


Hmmm. I wrote the patch you got from usb-linux.org. Can you dump the
usb info for your drive? I don't believe the vendor ID should have
changed. My USBDrive is the 32MB version.

This sounds like the bad behaviour I got from the earlier,
non-mass-storage compliant version, called the "Flash USBDrive"; the
new style is the "USBDrive (driverless)". The old model would report
that is was mass storage compliant, but it wasn't at the hardware
level, the functionality was in software.

Look at http://usbdrive.com/products.htm and tell me what "style"
yours is.



> Hi,
>    I'm trying to connect a 256MB JMTek USBDrive to my Linux 2.4.17.
> However, so far to no avail. I've used the patch from usb-linux.org,
> but I had to change the vendor ID and product ID to match the newer
> device (or so I presume). I ended up with US_SC_SCSI, US_PR_BULK &
> US_FL_START_STOP. When I connect the device it times out on every
> command, and an attempt to view /proc/scsi/* causes segmentation
> faults, some unsavoury log message and a hung scsi_mod.

>    Does anyone have a clue to the correct settings?

You can try setting different flags; look in storage/usb.c for a list.

--
http://www.bigfoot.com/~brihall
Linux Consultant

Experience is a good teacher but her fees are high...