linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: Greg KH <gregkh@linuxfoundation.org>, Lars Melin <larsm17@gmail.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	Oliver Neukum <oneukum@suse.com>,
	linux-usb@vger.kernel.org
Subject: Re: "SilverStone TS16" external SSD enclosing needs an UAS quirk
Date: Wed, 17 Jan 2024 08:59:29 +0100	[thread overview]
Message-ID: <2270283.o7ts2hSHzF@nimes> (raw)
In-Reply-To: <fc14c873-04ee-43cd-8328-b4e5b03e0230@gmail.com>

Lars Melin wrote:
> 0bda:9210 is a Realtek USB 3 to pcie chip used by umpteen
> enclosure manufacturers.

SilverStone TS16 is not the only one that makes problems. There's also
  - Sabrent NVMe M.2 enclosure (Model EC-SNVE) [1]
  - UnionSine Dual Protocol M2 NVMe to USB 3.1 [2]

> I have got one from Orico and it works ok under both linux and MSWin but 
> it can be a bit finicky if it doesn't get enough power, it may for 
> instance work well with an earlier (slower) type of NVME SSD but not 
> with a later faster type unless you provide external power to it (usb 
> hub + power adapter).

So, the Orico one has problems as well. Do these problems disappear when,
instead of changing the way it's connected to the computer, you add this
quirk?

> Slowing down all RTL9120 already in the market with this quirk is in my 
> humble opinion not a realistic solutio.

What else do you propose, for those of us who buy this hardware (€ 50,
it wasn't a cheap one), connect it directly to a computer (through the
vendor-provided cable, to an USB-C 3.2 Gen.2 connector, as in my case),
and then experience 1-2 crashes per day under Linux?

Bruno

[1] https://ubuntuforums.org/showthread.php?t=2466059
[2] https://forum.level1techs.com/t/nvme-to-usb-3-1-enclosure-buggy-in-linux-rtl9210b-chipset/199752




  reply	other threads:[~2024-01-17  8:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-15 23:35 "SilverStone TS16" external SSD enclosing needs an UAS quirk Bruno Haible
2024-01-16 14:13 ` Greg KH
2024-01-17  6:25   ` Lars Melin
2024-01-17  7:59     ` Bruno Haible [this message]
2024-01-17 14:11       ` [PATCH] uas: Disable UAS driver for Realtek RTL9210 M.2 NVME Adapters Bruno Haible
2024-01-17 14:53       ` "SilverStone TS16" external SSD enclosing needs an UAS quirk Alan Stern
2024-01-17 15:56         ` Bruno Haible
2024-01-17 18:39           ` Alan Stern
2024-01-17 16:41       ` Lars Melin

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=2270283.o7ts2hSHzF@nimes \
    --to=bruno@clisp.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=larsm17@gmail.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.com \
    --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;
as well as URLs for NNTP newsgroup(s).