On Thu, 7 Feb 2008, Fabio Venturi wrote: > > > Redirecting stderr and stdout of 'lsusb -v' I get the following details. > > > Note: the device restart if it get probed with 'lsusb -v' > > > > > > > > > Bus 001 Device 011: ID 10d6:2200 Actions Semiconductor Co., Ltd > > > Device Descriptor: > > > bLength 18 > > > bDescriptorType 1 > > > bcdUSB 2.00 > > > bDeviceClass 255 Vendor Specific Class > > > bDeviceSubClass 0 > > > bDeviceProtocol 0 > > > bMaxPacketSize0 64 > > > idVendor 0x10d6 Actions Semiconductor Co., Ltd > > > idProduct 0x2200 > > > > Notice how this is different from what appears when you left the device > > plugged in at boot time, earlier? > > > If it's already plugged at boot time it's registered as: > > Bus 001 Device 002: ID 10d6:1101 Actions Semiconductor Co., Ltd > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 2.00 > bDeviceClass 0 (Defined at Interface level) > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 64 > idVendor 0x10d6 Actions Semiconductor Co., Ltd > idProduct 0x1101
> Why 10d6:1101 instead of 10d6:2200 ???? Apparently the BIOS has done something that caused the device to change the way it behaves. Also changed is the error message about the invalid bInterval 200. > The behavior is also different: > If the flash disk is already plugged at boot there is a kind of > constant sync between pc and the drive (with consequent load of > usb-storage debug messages, the animated icon on device display confirm this) > Most important thing: there is a /dev/sdb file to mount That's what's supposed to happen. The constant "sync" is caused by hald as it monitors the device. > Else the icon stand still, there's no usb-storage debug output and there's no > device in /dev to mount So it doesn't work... > > > I guess something went wrong. > > > > Probably lsusb triggers that same firmware bug. > > With the device already plugged lsusb doesn't trigger the bug Because then the device behaves differently. > > Now that the device gets initialized correctly, does it actually work > > as it should? > > If plugged after boot it appears to be stuck. Can you post the usb-storage debugging log? It should indicate how things are getting "stuck". > The right ID seems to be 10d6:1101 but it's recognized > only if the device is plugged since boot time. I don't know what makes the device behave in this peculiar way. Alan Stern - To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
