On Friday 18 January 2013 16:36:29 kishon wrote: > > Bus 001 Device 004: ID 152d:2509 JMicron Technology Corp. / JMicron > > USA Technology Corp. JMS539 SuperSpeed SATA II 3.0G Bridge > > Device Descriptor: > > You are connecting to the wrong port. > > Try connecting to bus2 which seems to have usb3. > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub. > . > . > bcdUSB 3.00 No. Look closer. > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 2.00 > bDeviceClass 9 Hub > bDeviceSubClass 0 Unused > bDeviceProtocol 1 Single TT > bMaxPacketSize0 64 > idVendor 0x1d6b Linux Foundation > idProduct 0x0002 2.0 root hub > bcdDevice 3.06 > iManufacturer 3 Linux 3.8.0-rc2 xhci_hcd > iProduct 2 xHCI Host Controller > iSerial 1 0000:05:00.0 > bNumConfigurations 1 This is the virtual root hub of the XHCI controller, to which the device is connected. This is exactly what is supposed to happen if you connect a non-SS device to an XHCI. The question is, what goes wrong, if indeed the device is SS. In this particular case a usbmon trace is likely not as useful as usually. Could you compile a kernel with DEBUG for USB and XHCI enabled? Regards Oliver -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
