On Sun, 5 Apr 2015, Steve Bangert wrote: > > To do this, you need to set the usb-storage "quirks" module parameter > > to "174c:55aa:u". The 'u' quirk means to ignore the possibility of > > using UAS. > > > Here's dmesg using the kernel command line you provided: > > I can provide the full dmesg output/text if you wish in a follow up > email. Here's what the log looks like after all the useless chatter from xhci_hcd has been removed: > [ 65.322218] Bluetooth: RFCOMM socket layer initialized > [ 65.322282] Bluetooth: RFCOMM ver 1.11 > [ 123.405123] usb 2-2: new SuperSpeed USB device number 2 using xhci_hcd > [ 123.416030] usb 2-2: New USB device found, idVendor=174c, idProduct=55aa > [ 123.416038] usb 2-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1 > [ 123.416043] usb 2-2: Product: USB3-SATA-UASP1 > [ 123.416048] usb 2-2: Manufacturer: Plugable > [ 123.416052] usb 2-2: SerialNumber: 123456789014 > [ 123.455330] usbcore: registered new interface driver usb-storage As you can see, there's no line saying "UAS is blacklisted for this device, using usb-storage instead", so apparently you didn't set up the quirks parameter properly. What exactly did you do? > usbmon trace with uas disabled at the kernel command line: The same as before. You might as well not post this if the behavior hasn't changed. 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
