On Fri, Feb 08, 2008 at 10:24:35AM -0500, Alan Stern wrote: > On Fri, 8 Feb 2008, Fabio Venturi wrote: > > > > Can you post the usb-storage debugging log? It should indicate how > > > things are getting "stuck". > > > This is the relevant part of dmesg (I think). > > I cut it because it's very long, if you need more details let me know. > > You posted the debugging log for when the device works!
Because there is no usb-storage debug output otherwise :( This is the only output I get pluging the device after boot: [EMAIL PROTECTED]:~$ dmesg hub 1-0:1.0: state 7 ports 6 chg 0000 evt 0010 ehci_hcd 0000:00:03.3: GetStatus port 4 status 001803 POWER sig=j CSC CONNECT hub 1-0:1.0: port 4, status 0501, change 0001, 480 Mb/s hub 1-0:1.0: debounce: port 4: total 100ms stable 100ms status 0x501 ehci_hcd 0000:00:03.3: port 4 high speed ehci_hcd 0000:00:03.3: GetStatus port 4 status 001005 POWER sig=se0 PE CONNECT usb 1-4: new high speed USB device using ehci_hcd and address 4 ehci_hcd 0000:00:03.3: port 4 high speed ehci_hcd 0000:00:03.3: GetStatus port 4 status 001005 POWER sig=se0 PE CONNECT usb 1-4: USB quirks for this device: 1 usb 1-4: config 1 interface 0 altsetting 0 endpoint 0x83 has an invalid bInterval 200, changing to 11 usb 1-4: default language 0x0409 usb 1-4: new device strings: Mfr=1, Product=2, SerialNumber=3 usb 1-4: Product: Actions Mtp Device 000001 usb 1-4: Manufacturer: Actions Semiconductor Co., Ltd. usb 1-4: SerialNumber: C621C804E79ACB41A8825E5C3BD13556 usb 1-4: uevent usb 1-4: usb_probe_device usb 1-4: configuration #1 chosen from 1 choice usb 1-4: adding 1-4:1.0 (config #1, interface 0) usb 1-4:1.0: uevent usb 1-4:1.0: uevent drivers/usb/core/inode.c: creating file '004' usbcore: registered new interface driver libusual [EMAIL PROTECTED]:~$ Nothing more. I guess that's not a good news, right? Regards, Fabio - 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
