linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Stern <stern@rowland.harvard.edu>
To: "Till Dörges" <doerges@pre-sense.de>
Cc: linux-usb@vger.kernel.org
Subject: Re: Ext. HDDs not working under Linux via USB 3.0 but under Windows
Date: Sun, 24 May 2020 10:34:31 -0400	[thread overview]
Message-ID: <20200524143431.GA3275@rowland.harvard.edu> (raw)
In-Reply-To: <816c9c46-6845-e09f-9c67-ecd2427eb9c4@pre-sense.de>

On Sun, May 24, 2020 at 09:46:06AM +0200, Till Dörges wrote:
> Am 23.05.20 um 22:33 schrieb Alan Stern:
> 
> >>>> I'm trying to get external HDDs from Sony to work under Linux with USB 3.0.
> >> [...]
> >>>>  - PSZ-HA2T: idVendor=054c, idProduct=087d
> >>>>  - PSZ-HA1T: idVendor=054c, idProduct=087d
> >>>>  - PSZ-HA50: idVendor=054c, idProduct=087d
> >>>>  - PSZ-HC1T: idVendor=054c, idProduct=0c4f
> [...]
> >> Because with setting the f flag (via options usb-storage quirks=054c:087d:f) the
> >> PSZ-HA*1*T starts behaving nicely.
> [...]
> >> The PSZ-HA*2*T, however, still doesn't work with that.
> [...]
> > That device seems to be behaving so badly, it's hard to tell what the 
> > underlying problem is.
> > 
> > I'd start by blacklisting the device for UAS, so forcing it to use 
> > usb-storage, which is a somewhat simpler protocol.  Next, you should 
> > collect a usbmon trace showing what happens when you plug in the 
> > PSZ-HA2T.  That will tell us what's going on, even if it doesn't suggest 
> > a way to work around the problems.
> > 
> > (The instructions for usbmon are in the kernel source file 
> > Documentation/usb/usbmon.rst.)
> 
> Thanks. Will give that a shot.
> 
> 
> Is there any way to differentiate between devices other than vendor and product ID?
> 
> Because the PSZ-HA1T (which seems to be working thanks to your help) and the PSZ-HA2T
> (which still refuses to work) have the *same* vendor and product ID.

There's also the bcdDevice value.  It is ignored for quirks specified by 
the "quirks=" module parameter, but it is used for quirks stored in the 
unusual_devs.h or unusual_uas.h files in the kernel source code.

Alan Stern

  reply	other threads:[~2020-05-24 14:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-23 14:57 Ext. HDDs not working under Linux via USB 3.0 but under Windows Till Dörges
2020-05-23 15:48 ` Alan Stern
2020-05-23 20:05   ` Till Dörges
2020-05-23 20:33     ` Alan Stern
2020-05-24  7:46       ` Till Dörges
2020-05-24 14:34         ` Alan Stern [this message]
2020-06-17 16:02       ` Till Dörges
2020-06-17 16:37         ` Alan Stern
2020-06-18  6:07           ` Till Dörges
2020-06-18  7:30             ` Till Dörges
2020-06-19 12:07               ` Till Dörges
2020-06-19 15:05                 ` Alan Stern
2020-06-19 18:01                   ` Till Dörges
2020-08-25 18:45                     ` Alan Stern
2020-08-26 11:51                       ` Till Dörges
2020-08-26 14:28                         ` Alan Stern
2020-08-26 14:32                         ` [PATCH] usb: storage: Add unusual_uas entry for Sony PSZ drives Alan Stern

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=20200524143431.GA3275@rowland.harvard.edu \
    --to=stern@rowland.harvard.edu \
    --cc=doerges@pre-sense.de \
    --cc=linux-usb@vger.kernel.org \
    /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).