Hi,
On 03-11-15 11:48, Oliver Neukum wrote:
It just doesn't work with uas.
Blacklist it.
Signed-off-by: Oliver Neukum <[email protected]>
---
drivers/usb/storage/unusual_uas.h | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/drivers/usb/storage/unusual_uas.h
b/drivers/usb/storage/unusual_uas.h
index c85ea53..8aefb36 100644
--- a/drivers/usb/storage/unusual_uas.h
+++ b/drivers/usb/storage/unusual_uas.h
@@ -134,6 +134,13 @@ UNUSUAL_DEV(0x152d, 0x0567, 0x0000, 0x9999,
USB_SC_DEVICE, USB_PR_DEVICE, NULL,
US_FL_NO_REPORT_OPCODES),
+/* Reported-by: Oliver Neukum <[email protected]> */
+UNUSUAL_DEV(0x174c, 0x55aa, 0x0000, 0x9999,
+ "ASUSTek",
+ "External Drive",
+ USB_SC_DEVICE, USB_PR_DEVICE, NULL,
+ US_FL_IGNORE_UAS),
+
/* Reported-by: Hans de Goede <[email protected]> */
UNUSUAL_DEV(0x2109, 0x0711, 0x0000, 0x9999,
"VIA",
Nack, unfortunately the usb-id you are blacklisting is not
just for that enclosure, it is for any enclosure using an
Asmedia ASM1051 / ASM1053 / ASM1153 chipset (yes there
re-using the same id not only for all enclosures but
also for 3 different chipsets).
There is some code to blacklist ASM1051 using enclosures
in drivers/usb/storage/uas-detect.h in the uas_use_uas_driver
function.
Can you see if there is anyway to make that code work
with the drive / enclosure in question, without disabling
uas on all Asmedia devices (where it generally sortof works).
It would also be good to know which of the 4 branches
for Asmedia devices in there we end up with this device.
Also have you tried less invasive options like:
US_FL_MAX_SECTORS_240 | US_FL_NO_ATA_1X | US_FL_NO_REPORT_OPCODES
?
Regards,
Hans
--
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
