On Wed, 24 Oct 2012, Matthias Schniedermeyer wrote: > Hi > > > I have a 3TB WD HDD in an USB3 enclosure that fails to show up if i > connect the USB3-cable first and then switch on the enclosure. > (Example-Log see below) > > If i either: > - Wait a little before connecting the USB3-cable > - Disconnect/Reconnect the USB3-cable > - rmmod xhci; modprobe xhci > The HDD shows up and works normally. > > Question is, is there something that i can do that doesn't involve > 'rmmod'ing the xhci-driver or doing something physical? > Is there a way to force a "rescan"? > For e.g. is there something that i can do to a sysfs-file to force a > "rescan" of the USB-port? > Or can i prolong the timeout, which appears to be 5 seconds. The 5-second limit is part of the USB-2 specification (sections 9.2.6.1 and 9.2.6.4). > Kernel in this case is a vanilla 3.6.2. > xhci should be Intel but could also be from ASMedia (Z77-Chipset > mainboard with 2 additional ASMedia chips soldered on) > If more information is needed, i will happily provide it. > > > First i connected the USB3-cable and then powered up the device: > Oct 23 20:25:02 leeloo kernel: [852502.177231] usb 2-3: new SuperSpeed USB device number 2 using xhci_hcd > Oct 23 20:25:12 leeloo kernel: [852512.178456] usb 2-3: New USB device found, idVendor=174c, idProduct=5106 > Oct 23 20:25:12 leeloo kernel: [852512.178460] usb 2-3: New USB device strings: Mfr=2, Product=3, SerialNumber=1 > Oct 23 20:25:12 leeloo kernel: [852512.178462] usb 2-3: Product: AS2105 > Oct 23 20:25:12 leeloo kernel: [852512.178465] usb 2-3: Manufacturer: ASMedia > Oct 23 20:25:17 leeloo kernel: [852517.173409] usb 2-3: can't set config #1, error -110 According to this, it should work if you do: echo 1 >/sys/bus/usb/devices/2-3/bConfigurationValue Note that the "2-3" part may change from time to time. Always use the values the showed up in the log when the device was turned on. Alan Stern -- 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
