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: Wed, 17 Jun 2020 12:37:34 -0400 [thread overview]
Message-ID: <20200617163734.GC11314@rowland.harvard.edu> (raw)
In-Reply-To: <5bd5e8be-f8a9-9456-cced-c2bc75455556@pre-sense.de>
On Wed, Jun 17, 2020 at 06:02:32PM +0200, Till Dörges wrote:
> Hi Alan,
>
> sorry for the delay. It took me a while to get back to this.
>
> 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
> >> [...]
> >>>> I've also tried several of the quirk settings
> >>>> (https://github.com/torvalds/linux/blob/ead751507de86d90fa250431e9990a8b881f713c/drivers/usb/storage/usb.c#L527).
>
> [...]
> >>> Try adding an entry to the unusual_uas.h file for the device, specifying
> >>> the USB_FL_NO_REPORT_OPCODES flag.
> >>
> >> I'm not sure I understand correctly. Do I have to compile the uas Kernel module
> >> myself if I want to test a flag?
> >>
> >> Because with setting the f flag (via options usb-storage quirks=054c:087d:f) the
> >> PSZ-HA*1*T starts behaving nicely.
> >>
> >> --- snip ---
> >> $ cat /sys/module/usb_storage/parameters/quirks
> >> 054c:087d:f,054c:0c4f:f
> >> --- snip ---
> >>
> >>
> >> The PSZ-HA*2*T, however, still doesn't work with that.
> Since the device stopped working under windows, I'm guessing that it's simply broken.
>
> I'll try to get my hands on a new sample.
>
>
> The PSZ-HA50 and the PSZ-HA1T work nicely when attached to USB 3.0 with this setting:
>
> --- snip ---
> $ cat /sys/module/usb_storage/parameters/quirks
> 054c:087d:u
> --- snip ---
>
> W/o this quirk they do not work.
>
>
> I'd be surprised if a non-broken PSZ-HA2T behaved any differently.
>
> So perhaps you might want to consider adding that quirk directly into the Kernel?
>
>
> FTR, the PSZ-HC1T just worked.
Okay. If you would like to write a patch for the quirk and submit it, you
can. Otherwise I'll write one for you.
Alan Stern
next prev parent reply other threads:[~2020-06-17 16:37 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
2020-06-17 16:02 ` Till Dörges
2020-06-17 16:37 ` Alan Stern [this message]
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=20200617163734.GC11314@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