Re: "SilverStone TS16" external SSD enclosing needs an UAS quirk

From: Alan Stern <stern@rowland.harvard.edu>
To: Bruno Haible <bruno@clisp.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	Lars Melin <larsm17@gmail.com>, 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 09:53:17 -0500	[thread overview]
Message-ID: <21712025-0b46-4afb-9161-5d1f1afb502a@rowland.harvard.edu> (raw)
In-Reply-To: <2270283.o7ts2hSHzF@nimes>

On Wed, Jan 17, 2024 at 08:59:29AM +0100, Bruno Haible wrote:
> 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?

The proposal is that you keep on doing what you've been doing: Set the 
UAS quirk.  Then your system will work, and others who don't have the 
same problem will get to keep the advantage of quicker transfers with 
the uas driver.

Alan Stern