From: Oliver Neukum <oneukum@suse.com>
To: burcheri.massimo+linux-usb@gmail.com,
Alan Stern <stern@rowland.harvard.edu>
Cc: linux-usb <linux-usb@vger.kernel.org>
Subject: Re: JMicron JMS567 and UAS
Date: Mon, 16 Oct 2023 09:37:06 +0200 [thread overview]
Message-ID: <c3cd0de5-e8f3-4edb-bcaa-abf29ce5928b@suse.com> (raw)
In-Reply-To: <7f8396ae597a78969811011034a7e5f759a6564e.camel@gmail.com>
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
next prev parent reply other threads:[~2023-10-16 7:37 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
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 [this message]
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=c3cd0de5-e8f3-4edb-bcaa-abf29ce5928b@suse.com \
--to=oneukum@suse.com \
--cc=burcheri.massimo+linux-usb@gmail.com \
--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