Hi,
On 10/05/2014 11:14 AM, Jan Kiszka wrote:
> On 2014-10-05 11:08, Hans de Goede wrote:
>> Hi,
>>
>> On 10/04/2014 08:35 PM, Jan Kiszka wrote:
>>> Hi,
>>>
>>> my Delock external USB drive stopped working after updating from a
>>> UAS-disabled distro kernel to latest 3.17-rc7 with UAS on. That UAS was
>>> key became clear to me only after looking at storage_probe(): the device
>>> is ignored by usb-storage if it is UAS-capable. However, nothing causes
>>> uas.ko to be loaded when the drive is plugged here. How is this supposed
>>> to work in the normal case?
>>
>> Is the uas.ko module installed, and was depmod run after installing it ?
>
> Definitely. Just retried after another depmod -a, and only modprobe uas
> made it work.
>
>>
>> uas.c has the following:
>>
>> { USB_INTERFACE_INFO(USB_CLASS_MASS_STORAGE, USB_SC_SCSI, USB_PR_BULK) },
>> { USB_INTERFACE_INFO(USB_CLASS_MASS_STORAGE, USB_SC_SCSI, USB_PR_UAS) },
>>
>> Which should make it load automatically on your device.
>
> Should this match with what lsusb -v reports for the device?
Yes, and it does, for both alt settings of your device:
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 98
Where 98 == USB_PR_UAS, seems you have an quite old lsusb if it does not
know that though. Could it be the rest of your userspace is old too, and is
not smart enough to load all matching drivers, instead only loading the first matching
driver (which happens to be usb-storage) ?
Regards,
Hans
--
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
