From: Massimo Burcheri <massimo@burcheri.de>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-usb <linux-usb@vger.kernel.org>
Subject: Re: JMicron JMS567 and UAS
Date: Thu, 21 Sep 2023 14:22:13 +0200 [thread overview]
Message-ID: <072417fd7806d86e930bccb882460dbbfaa5ca52.camel@gmail.com> (raw)
In-Reply-To: <a5b48a53-9dff-4a84-9a58-1c08f0e0781b@rowland.harvard.edu>
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
next prev parent reply other threads:[~2023-09-21 18:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=072417fd7806d86e930bccb882460dbbfaa5ca52.camel@gmail.com \
--to=massimo@burcheri.de \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox