Hello Alan, Thanks for your reply. The errors I got was during a dd read of the complete device. If I put the stick in another brand hub or directly on the back of the PC (ASUS P5B motherboard), the entire stick is read without problems, but if I put it in a SYBA SD-U2HUB-4 hub, I get the errors in the previous post. Is there anything I can do to get it to work on these SYBA hubs? I've got about 150 of them :-) I tried limiting max_sectors to 36, but this did not result in much better results.
Best regards, Marco > -----Original Message----- > From: Alan Stern [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 02, 2007 6:19 PM > To: Marco Polet > Cc: '[email protected]' > Subject: Re: Unusual dev addition for memory stick? > > > On Wed, 2 May 2007, Marco Polet wrote: > > > Hello all, > > > > This is the output of the devices file of our (1 Gb) memory stick: > > > > T: Bus=01 Lev=02 Prnt=02 Port=03 Cnt=01 Dev#= 5 Spd=480 MxCh= 0 > > D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 > > P: Vendor=058f ProdID=6387 Rev= 1.43 > > S: Manufacturer=Generic > > S: Product=Mass Storage > > S: SerialNumber=5C19D733 > > C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA > > I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 > Driver=usb-storage > > E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms > > E: Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms > > > > I included the /var/log/messages file, but if attachments don't come > > through, this is a snippet: > > usb1001 usb-storage: Bulk status result = 0 > > usb1001 usb-storage: Bulk Status S 0x53425355 T 0x17 R > 122880 Stat 0x1 > > usb1001 usb-storage: -- transport indicates command failure > > usb1001 usb-storage: -- unexpectedly short transfer > > usb1001 usb-storage: Issuing auto-REQUEST_SENSE > > usb1001 usb-storage: Bulk Command S 0x43425355 T 0x18 L 18 > F 128 Trg 0 LUN 0 > > CL 6 > > usb1001 usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes > > usb1001 usb-storage: Status code 0; transferred 31/31 > > usb1001 usb-storage: -- transfer complete > > > > > > I found (through other posts on the list), there might be a > problem with > > residual bytes. I checked the messages file, and found this > might be the > > case (R 122880 above). To try to enable this ignore flag, I > added the > > following to my 2.6.19-gentoo-r5 kernel unusual_devs.h: > > > > UNUSUAL_DEV( 0x058f, 0x6387, 0x0000, 0x9999, > > "Generic", > > "Mass Storage", > > US_SC_DEVICE, US_PR_DEVICE, NULL, > > US_FL_IGNORE_RESIDUE | US_FL_SINGLE_LUN), > > > > > > After rebuilding the kernel, and restarting, there's no > difference in the > > messages output. Can anyone confirm I'm adding the correct > UNUSUAL_DEV > > statements? > > You are not. > > In fact, you don't need an unusual_devs entry at all. There > doesn't seem > to be anything especially wrong with the device. But your > USB connection > isn't working very well; large data transfers get hardware errors. > > This could be caused by poor USB cables, like the cables inside the > computer case connecting the port to the motherboard. Try > using different > USB ports. Also try testing your device on other computers, and try > testing other high-speed USB devices on your computer. > > Alan Stern > ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
