On Thu, 2023-09-21 at 10:23 -0400, Alan Stern wrote: > > > > coming from https://lore.kernel.org/all/20200818041324.GA3173@Susan/ > That email refers to vendor & product 357d:7788. But your device, as > shown in the earlier email message, is 152d:0567. So it's puzzling why > you referred back to this bug report, even though the devices do have > similar names (JMicron J566 and J567). Sorry for confusing. I wrote to Cyril Roelandt and he said that he noticed that old thread had a typo with JMS566 and he was actually using the same JMS567 at that time. Though productIds are still different: Old thread: [Tue Aug 18 05:14:19 2020] usb 2-2: New USB device found, idVendor=357d, idProduct=7788, bcdDevice= 1.14 [Tue Aug 18 05:14:19 2020] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 My Log: Aug 27 19:00:47 [kernel] usb 4-5: New USB device found, idVendor=152d, idProduct=0567, bcdDevice=52.03 Aug 27 19:00:47 [kernel] usb 4-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 > If you can, start by figuring out why your kernel isn't using the uas > driver for the JMS567. Is the driver itself blacklisted on your > computer? It's not blacklisted here afaik. This would be done in /etc/modprobe.d/*.conf and I have no entry about that device. So you mean if not blacklisted by kernel and not locally blacklisted, uas is just not supported by that firmware? I'm going to check if I can just try other firmwares that were reported to support uas. In the past I already got an enclosure supporting uas by just switching the firmware...that was: Nov 23 10:25:27 [kernel] usb 4-6: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd Nov 23 10:25:27 [kernel] usb 4-6: New USB device found, idVendor=174c, idProduct=55aa, bcdDevice= 1.00 Nov 23 10:25:27 [kernel] usb 4-6: New USB device strings: Mfr=2, Product=3, SerialNumber=1 Nov 23 10:25:27 [kernel] usb 4-6: Product: USB3-SATA-UASP1(modForGentoo) Nov 23 10:25:27 [kernel] usb 4-6: Manufacturer: StoreJet Transcend Best regards, Massimo
