From: Eddie Chapman <eddie@ehuk.net>
To: Olivier Kaloudoff <olivier.kaloudoff@gmail.com>
Cc: linux-usb@vger.kernel.org, stern@rowland.harvard.edu,
gregkh@linuxfoundation.org, oneukum@suse.com,
usb-storage@lists.one-eyed-alien.net
Subject: Re: [PATCH] usb: uas: ignore UAS for ASMT135x bridges (174c:55aa)
Date: Mon, 16 Nov 2026 21:04:29 +0000 [thread overview]
Message-ID: <e2ded4e1-a7f3-47d4-a3be-d7c6eed3e436@ehuk.net> (raw)
In-Reply-To: <20261114174932.53895-1-olivier.kaloudoff@gmail.com>
On 14/11/2026 17:49, Olivier Kaloudoff wrote:
> Hi Eddie,
>
> On 13/11/2026 19:32, Eddie Chapman wrote:
>> May I trouble you to say the product/model of the Orico device you have
>> which reports "ASMT135x" as the iProduct?
>>
>> Also, is it still running whatever firmware it came with or has that
>> been upgraded?
>
> It's an ORICO C10 — sold as "ORICO C10 SSD Externe" (4 TB, "800 MB/s"
> USB enclosure). Stock firmware; it has never been updated, there is no
> vendor updater for it that I'm aware of.
>
> Identification details for the record: idVendor/idProduct 174c:55aa,
> iManufacturer "ASMT", iProduct "ASMT135x", bcdDevice 1.00.
>
> Note the model is now discontinued — mine went back under a
> defect-based refund (reallocated/pending sectors on the SSD itself),
> which is how the UAS breakage was noticed in the first place.
>
> Hope that helps,
> Olivier
Thanks Olivier. In my own experience just purchasing and using many
Asmedia USB to SATA products over the years, they usually ship with
quite old, buggy firmware, and the manufacturer rarely provides a
firmware update. But there are various unofficial sources of newer
firmware out there if you look. It goes without saying you have to
decide for yourself if the obvious risk is worth taking. Generally these
are either leaked, or are "extracted" from devices with newer firmware
by users and shared. Sometimes one or two "good" manufacturers supply
firmware updates for their products and the firmware enthusiast
community subsequently finds that these apply fine to other equivalent
product with the same chip.
There is an internal Asmedia firmware tool widely available online. If a
manufacturer does provide a firmware update it will usually come
packaged with that tool. It only runs on Windows (not sure about Mac,
definitely not Linux). There are community efforts I've seen trying to
develop alternative firmare tools.
Anyway, speaking purely from my own experience, I've always updated the
firmware on my devices and there is no doubt in my mind that the newer
firmware versions I've applied to my devices have resolved serious bugs
in the older versions they were shipped with.
Bringing this a little bit back on topic for issues seen in the Linux
kernel with Asmedia USB to SATA devices, I'd be willing to wager that a
lot (if not most) of the time, if there is a firmware update out there
for a chip, there's an excellent chance it will resolve the issue. But
it is a mine field for users who are forced to take risks, and it is a
very problematic situation for Linux to deal with to say the least.
Eddie
next prev parent reply other threads:[~2026-11-16 21:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-14 17:49 [PATCH] usb: uas: ignore UAS for ASMT135x bridges (174c:55aa) Olivier Kaloudoff
2026-11-16 21:04 ` Eddie Chapman [this message]
2026-11-17 8:34 ` Oliver Neukum
2026-11-17 14:41 ` Eddie Chapman
2026-11-18 9:18 ` Oliver Neukum
-- strict thread matches above, loose matches on Subject: below --
2026-10-13 22:19 Olivier Kaloudoff
2026-10-13 22:23 ` sashiko-bot
2026-10-14 5:00 ` Greg KH
2026-11-13 18:32 ` Eddie Chapman
2026-10-11 16:42 Olivier Kaloudoff
2026-10-11 16:47 ` sashiko-bot
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=e2ded4e1-a7f3-47d4-a3be-d7c6eed3e436@ehuk.net \
--to=eddie@ehuk.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=olivier.kaloudoff@gmail.com \
--cc=oneukum@suse.com \
--cc=stern@rowland.harvard.edu \
--cc=usb-storage@lists.one-eyed-alien.net \
/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