On Tue, Sep 19, 2023 at 03:34:21PM +0200, Massimo Burcheri wrote: > Hi, > > coming from https://lore.kernel.org/all/20200818041324.GA3173@Susan/ > > as I understand UAS was working for JMicron JMS567 in the past, then was > disabled in the kernel, now using usb-storage. How did you get that idea? After looking through the email archives, I found this bug report from 2015: https://bugzilla.redhat.com/show_bug.cgi?id=1260207 > Why? The hardware should support UAS and does so on Windows. Before 5.4 it was > working with UAS on Linux as well. That bug report indicates that the device wasn't working properly with a 4.1.4 kernel. Of course, it's possible that the problem had more to do with the drive inside the enclosure than the enclosure itself. > I purchased a 5-bay USB enclosure "ORICO DS500U3" but UAS is not working: > 4-5 152d:0567 00 1IF [USB 3.00, 5000 Mbps, 8mA] (JMicron > External USB 3.0 20170331000C3) > > |__ Port 5: Dev 8, If 0, Class=Mass Storage, Driver=usb-storage, 5000M > > Aug 28 18:47:09 [kernel] usb 4-5: new SuperSpeed USB device number 8 using xhci_hcd > Aug 28 18:47:09 [kernel] usb 4-5: New USB device found, idVendor=152d, idProduct=0567, bcdDevice=52.03 > Aug 28 18:47:09 [kernel] usb 4-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 > Aug 28 18:47:09 [kernel] usb 4-5: Product: External USB 3.0 > Aug 28 18:47:09 [kernel] usb 4-5: Manufacturer: JMicron > Aug 28 18:47:09 [kernel] usb 4-5: SerialNumber: 20170220000C3 > Aug 28 18:47:09 [kernel] usb-storage 4-5:1.0: USB Mass Storage device detected > Aug 28 18:47:09 [kernel] usb-storage 4-5:1.0: Quirks match for vid 152d pid 0567: 5000000 > Aug 28 18:47:09 [kernel] scsi host8: usb-storage 4-5:1.0 > Aug 28 18:47:09 [mtp-probe] checking bus 4, device 8: "/sys/devices/pci0000:00/0000:00:14.0/usb4/4-5" > Aug 28 18:47:09 [mtp-probe] bus: 4, device: 8 was not an MTP device > > With a mdraid raid0 and 5x1TB discs I get only about 72MiB/s to the raid0 which > is really slow. UAS could do more. > > Is there any chance UAS could get fixed for that device in the future? At least > is seems to have worked someday with older kernels? How do you know this? Alan Stern
