>> +UNUSUAL_DEV( 0x0a16, 0x9989, 0x0100, 0x0100, >> + "IBM", >> + "IBM USB Memory Key", >> + US_SC_SCSI, US_PR_BULK, NULL, >> + US_FL_FIX_INQUIRY ), > >> bInterfaceClass 8 Mass Storage >> bInterfaceSubClass 6 SCSI >> bInterfaceProtocol 80 Bulk (Zip) > > Something does not quite compute. What does the entry do which > the generic code does not? I see the US_FL_FIX_INQUIRY only. > Can US_FL_FIX_INQUIRY cure timeouts? May it be better to fix > something in the generic code instead of ballooning the > unusual_devs.h?
I have no idea whatsoever, I'm not a kernel guru, but for me it seems that US_FL_FIX_INQUIRY does cure at least the timeout that happens with the memory stick. I rebooted back to unpatched kernel and this is what happens with the memory stick: --- SCSI subsystem driver Revision: 1.00 Initializing USB Mass Storage driver... usb.c: registered new driver usb-storage scsi0 : SCSI emulation for USB Mass Storage devices usb_control/bulk_msg: timeout usb.c: USB disconnect on device 3 hub.c: USB new device connect on bus1/2, assigned device number 7 usb-uhci.c: interrupt, status 3, frame# 1700 scsi: device set offline - not ready or command retry failed after bus reset: host 0 channel 0 id 0 lun 0 WARNING: USB Mass Storage data integrity not assured USB Mass Storage device found at 3 USB Mass Storage support registered. usb_control/bulk_msg: timeout --- When I try to mount that device with "mount /dev/sda1 /mnt/usbmemory", it either hangs or returns immediately with "/dev/sda1 is not a valid block device". What kind of extra information would help you to debug this? ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
