* JMicron JMS567 and UAS
@ 2023-09-19 13:34 Massimo Burcheri
2023-09-19 15:13 ` Alan Stern
0 siblings, 1 reply; 11+ messages in thread
From: Massimo Burcheri @ 2023-09-19 13:34 UTC (permalink / raw)
To: linux-usb
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.
Why? The hardware should support UAS and does so on Windows. Before 5.4 it was
working with UAS on Linux as well.
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?
Best regards,
Massimo
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: JMicron JMS567 and UAS
2023-09-19 13:34 JMicron JMS567 and UAS Massimo Burcheri
@ 2023-09-19 15:13 ` Alan Stern
2023-09-21 12:22 ` Massimo Burcheri
0 siblings, 1 reply; 11+ messages in thread
From: Alan Stern @ 2023-09-19 15:13 UTC (permalink / raw)
To: burcheri.massimo+linux-usb; +Cc: linux-usb
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
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: JMicron JMS567 and UAS
2023-09-19 15:13 ` Alan Stern
@ 2023-09-21 12:22 ` Massimo Burcheri
2023-09-21 14:23 ` Alan Stern
0 siblings, 1 reply; 11+ messages in thread
From: Massimo Burcheri @ 2023-09-21 12:22 UTC (permalink / raw)
To: Alan Stern; +Cc: linux-usb
On Tue, 2023-09-19 at 11:13 -0400, Alan Stern wrote:
> > 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
I got the idea from my original thread.
I did not test it on old kernel.
> 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.
From the report the idProduct is different from my product, might be a different
bridge.
So from what I understand it is blacklisted currently because of issues.
Is there a way I can bypass the blacklisting, like forcing to use uas similar to
the workaround by forcing usb-storage? I would like to know if there are still
issues in uas mode with this bridge.
The (chinese?) product is sold with UAS support. I know this is no warranty. The
JMicron bridge itself should support UASP:
https://pcper.com/wp-content/uploads/2014/12/0813-jms567.pdf
I found someone that fixed it by flashing an older firmware:
https://forum.openmediavault.org/index.php?user-post-list/36559-sanjager/
(Version 20.06.00.01, before 138.01.00.01)
It seems a similar device Icybox 4HDD enclosure is also using the JMS567:
https://answers.launchpad.net/ubuntu/+source/linux/+question/688498
This all sounds like UAS is not entirely missing but somehow faulty in this
bridge.
I'm going to test with a Windows machine soon, if UAS is working stable there.
But that won't help me on Linux, just for saying the enclosure hardware is UAS
capable.
How can I help exploring / debugging this?
Best regards,
Massimo
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: JMicron JMS567 and UAS
2023-09-21 12:22 ` Massimo Burcheri
@ 2023-09-21 14:23 ` Alan Stern
2023-09-22 13:23 ` Massimo Burcheri
0 siblings, 1 reply; 11+ messages in thread
From: Alan Stern @ 2023-09-21 14:23 UTC (permalink / raw)
To: Massimo Burcheri; +Cc: linux-usb
On Thu, Sep 21, 2023 at 02:22:13PM +0200, Massimo Burcheri wrote:
> On Tue, 2023-09-19 at 11:13 -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).
> > > 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
>
> I got the idea from my original thread.
> I did not test it on old kernel.
In fact, I don't see anything in the current kernel that would prevent
your device from working with uas. The entry in unusual_uas.h merely
has the BROKEN_FUA and NO_REPORT_OPCODES flags set, neither of which
should have a bad effect.
Am I missing something?
> > 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.
>
> From the report the idProduct is different from my product, might be a different
> bridge.
Indeed.
> So from what I understand it is blacklisted currently because of issues.
>
> Is there a way I can bypass the blacklisting, like forcing to use uas similar to
> the workaround by forcing usb-storage? I would like to know if there are still
> issues in uas mode with this bridge.
>
> The (chinese?) product is sold with UAS support. I know this is no warranty. The
> JMicron bridge itself should support UASP:
> https://pcper.com/wp-content/uploads/2014/12/0813-jms567.pdf
>
> I found someone that fixed it by flashing an older firmware:
> https://forum.openmediavault.org/index.php?user-post-list/36559-sanjager/
> (Version 20.06.00.01, before 138.01.00.01)
>
> It seems a similar device Icybox 4HDD enclosure is also using the JMS567:
> https://answers.launchpad.net/ubuntu/+source/linux/+question/688498
>
> This all sounds like UAS is not entirely missing but somehow faulty in this
> bridge.
>
> I'm going to test with a Windows machine soon, if UAS is working stable there.
> But that won't help me on Linux, just for saying the enclosure hardware is UAS
> capable.
>
> How can I help exploring / debugging this?
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?
Alan Stern
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: JMicron JMS567 and UAS
2023-09-21 14:23 ` Alan Stern
@ 2023-09-22 13:23 ` Massimo Burcheri
2023-09-22 13:59 ` Alan Stern
2023-10-16 7:37 ` Oliver Neukum
0 siblings, 2 replies; 11+ messages in thread
From: Massimo Burcheri @ 2023-09-22 13:23 UTC (permalink / raw)
To: Alan Stern; +Cc: linux-usb
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
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: JMicron JMS567 and UAS
2023-09-22 13:23 ` Massimo Burcheri
@ 2023-09-22 13:59 ` Alan Stern
2023-09-23 8:01 ` Massimo Burcheri
2023-10-16 7:37 ` Oliver Neukum
1 sibling, 1 reply; 11+ messages in thread
From: Alan Stern @ 2023-09-22 13:59 UTC (permalink / raw)
To: burcheri.massimo+linux-usb; +Cc: linux-usb
On Fri, Sep 22, 2023 at 03:23:29PM +0200, Massimo Burcheri wrote:
> 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
Okay. Let's forget about the 357d:7788 device and focus on your
152d:0567 device. That will help reduce the confusion.
> > 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
Maybe the problem isn't blacklisting at all; maybe your JMS567 device's
firmware just doesn't support UAS.
I don't think you have posted the "lsusb -v" output for this device.
What does it say?
Alan Stern
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: JMicron JMS567 and UAS
2023-09-22 13:59 ` Alan Stern
@ 2023-09-23 8:01 ` Massimo Burcheri
2023-09-23 15:02 ` Alan Stern
0 siblings, 1 reply; 11+ messages in thread
From: Massimo Burcheri @ 2023-09-23 8:01 UTC (permalink / raw)
To: Alan Stern; +Cc: linux-usb
On Fri, 2023-09-22 at 09:59 -0400, Alan Stern wrote:
> Maybe the problem isn't blacklisting at all; maybe your JMS567 device's
> firmware just doesn't support UAS.
>
> I don't think you have posted the "lsusb -v" output for this device.
> What does it say?
Bus 004 Device 012: ID 152d:0567 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 3.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 9
idVendor 0x152d JMicron Technology Corp. / JMicron USA Technology Corp.
idProduct 0x0567 JMS567 SATA 6Gb/s bridge
bcdDevice 52.03
iManufacturer 1 JMicron
iProduct 2 External USB 3.0
iSerial 3 20170220000C3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x002c
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 8mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 15
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 15
Binary Object Store Descriptor:
bLength 5
bDescriptorType 15
wTotalLength 0x0016
bNumDeviceCaps 2
USB 2.0 Extension Device Capability:
bLength 7
bDescriptorType 16
bDevCapabilityType 2
bmAttributes 0x00000f0e
BESL Link Power Management (LPM) Supported
BESL value 3840 us
SuperSpeed USB Device Capability:
bLength 10
bDescriptorType 16
bDevCapabilityType 3
bmAttributes 0x00
wSpeedsSupported 0x000e
Device can operate at Full Speed (12Mbps)
Device can operate at High Speed (480Mbps)
Device can operate at SuperSpeed (5Gbps)
bFunctionalitySupport 1
Lowest fully-functional device speed is Full Speed (12Mbps)
bU1DevExitLat 10 micro seconds
bU2DevExitLat 32 micro seconds
Device Status: 0x000d
Self Powered
U1 Enabled
U2 Enabled
Best regards,
Massimo
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: JMicron JMS567 and UAS
2023-09-23 8:01 ` Massimo Burcheri
@ 2023-09-23 15:02 ` Alan Stern
0 siblings, 0 replies; 11+ messages in thread
From: Alan Stern @ 2023-09-23 15:02 UTC (permalink / raw)
To: burcheri.massimo+linux-usb; +Cc: linux-usb
On Sat, Sep 23, 2023 at 10:01:32AM +0200, Massimo Burcheri wrote:
> On Fri, 2023-09-22 at 09:59 -0400, Alan Stern wrote:
> > Maybe the problem isn't blacklisting at all; maybe your JMS567 device's
> > firmware just doesn't support UAS.
> >
> > I don't think you have posted the "lsusb -v" output for this device.
> > What does it say?
>
> Bus 004 Device 012: ID 152d:0567 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge
> Device Descriptor:
> bLength 18
> bDescriptorType 1
> bcdUSB 3.00
> bDeviceClass 0
> bDeviceSubClass 0
> bDeviceProtocol 0
> bMaxPacketSize0 9
> idVendor 0x152d JMicron Technology Corp. / JMicron USA Technology Corp.
> idProduct 0x0567 JMS567 SATA 6Gb/s bridge
> bcdDevice 52.03
> iManufacturer 1 JMicron
> iProduct 2 External USB 3.0
> iSerial 3 20170220000C3
> bNumConfigurations 1
> Configuration Descriptor:
> bLength 9
> bDescriptorType 2
> wTotalLength 0x002c
> bNumInterfaces 1
> bConfigurationValue 1
> iConfiguration 0
> bmAttributes 0xc0
> Self Powered
> MaxPower 8mA
> Interface Descriptor:
> bLength 9
> bDescriptorType 4
> bInterfaceNumber 0
> bAlternateSetting 0
> bNumEndpoints 2
> bInterfaceClass 8 Mass Storage
> bInterfaceSubClass 6 SCSI
> bInterfaceProtocol 80 Bulk-Only
This is the Bulk-Only Transport interface (usb-storage).
> iInterface 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x81 EP 1 IN
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0400 1x 1024 bytes
> bInterval 0
> bMaxBurst 15
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x02 EP 2 OUT
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0400 1x 1024 bytes
> bInterval 0
> bMaxBurst 15
And there's no UAS interface. If one existed, this is where it would
show up.
> Binary Object Store Descriptor:
> bLength 5
> bDescriptorType 15
> wTotalLength 0x0016
> bNumDeviceCaps 2
> USB 2.0 Extension Device Capability:
> bLength 7
> bDescriptorType 16
> bDevCapabilityType 2
> bmAttributes 0x00000f0e
> BESL Link Power Management (LPM) Supported
> BESL value 3840 us
> SuperSpeed USB Device Capability:
> bLength 10
> bDescriptorType 16
> bDevCapabilityType 3
> bmAttributes 0x00
> wSpeedsSupported 0x000e
> Device can operate at Full Speed (12Mbps)
> Device can operate at High Speed (480Mbps)
> Device can operate at SuperSpeed (5Gbps)
> bFunctionalitySupport 1
> Lowest fully-functional device speed is Full Speed (12Mbps)
> bU1DevExitLat 10 micro seconds
> bU2DevExitLat 32 micro seconds
> Device Status: 0x000d
> Self Powered
> U1 Enabled
> U2 Enabled
So that's very clear; the device's firmware does not support UAS. You
might be able to fix it with a firmware update.
Alan Stern
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: JMicron JMS567 and UAS
2023-09-22 13:23 ` Massimo Burcheri
2023-09-22 13:59 ` Alan Stern
@ 2023-10-16 7:37 ` Oliver Neukum
2023-10-16 19:05 ` Alan Stern
1 sibling, 1 reply; 11+ messages in thread
From: Oliver Neukum @ 2023-10-16 7:37 UTC (permalink / raw)
To: burcheri.massimo+linux-usb, Alan Stern; +Cc: linux-usb
On 22.09.23 15:23, Massimo Burcheri wrote:
> 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
Hi,
sorry, this seems to have fallen through the cracks.
I think we have some sort of confusion here. Could you first
of all give us "lsusb -v" for your device?
Regards
Oliver
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: JMicron JMS567 and UAS
2023-10-16 7:37 ` Oliver Neukum
@ 2023-10-16 19:05 ` Alan Stern
2024-04-02 9:47 ` Massimo Burcheri
0 siblings, 1 reply; 11+ messages in thread
From: Alan Stern @ 2023-10-16 19:05 UTC (permalink / raw)
To: Oliver Neukum; +Cc: burcheri.massimo+linux-usb, linux-usb
On Mon, Oct 16, 2023 at 09:37:06AM +0200, Oliver Neukum wrote:
>
>
> On 22.09.23 15:23, Massimo Burcheri wrote:
> > 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
>
> Hi,
>
> sorry, this seems to have fallen through the cracks.
> I think we have some sort of confusion here. Could you first
> of all give us "lsusb -v" for your device?
Massimo did provide the "lsusb -v" listing here:
https://lore.kernel.org/linux-usb/1352baa835ecd1a6b7f49e0d08f440858a99189d.camel@gmail.com/
It showed that his device's current firmware does not support UAS. So
it won't work at very high speed without a firmware upgrade.
Alan Stern
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: JMicron JMS567 and UAS
2023-10-16 19:05 ` Alan Stern
@ 2024-04-02 9:47 ` Massimo Burcheri
0 siblings, 0 replies; 11+ messages in thread
From: Massimo Burcheri @ 2024-04-02 9:47 UTC (permalink / raw)
To: Alan Stern, Oliver Neukum; +Cc: linux-usb
On Mon, 2023-10-16 at 15:05 -0400, Alan Stern wrote:
> It showed that his device's current firmware does not support UAS. So
> it won't work at very high speed without a firmware upgrade.
I hate installing firmware from inofficial sources...
Too bad, I tried some firmware from
https://www.station-drivers.com/index.php/en/component/remository/Drivers/Jmicron/JMS567-Sata-USB-3.0-Controller/Jmicron-JMS-567-Firmware-Version-20.06.00.01/lang,en-gb/
First, the flashing looked good and said, the device needs a restart.
After a device restart, the device isn't shown in the hardware list anymore,
broken forever?
I did not find any official firmware from Orico or JMicron.
Best regards,
Massimo
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2024-04-02 9:47 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-09-19 13:34 JMicron JMS567 and UAS Massimo Burcheri
2023-09-19 15:13 ` Alan Stern
2023-09-21 12:22 ` Massimo Burcheri
2023-09-21 14:23 ` Alan Stern
2023-09-22 13:23 ` Massimo Burcheri
2023-09-22 13:59 ` Alan Stern
2023-09-23 8:01 ` Massimo Burcheri
2023-09-23 15:02 ` Alan Stern
2023-10-16 7:37 ` Oliver Neukum
2023-10-16 19:05 ` Alan Stern
2024-04-02 9:47 ` Massimo Burcheri
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox