From: Hans de Goede <hdegoede@redhat.com>
To: Julian Sikorski <belegdol@gmail.com>,
Oliver Neukum <oneukum@suse.com>,
Nathan Stratton Treadway <vgerlists@nathanst.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: Lacie Rugged USB3-FW does not work with UAS
Date: Tue, 27 Jul 2021 23:19:33 +0200 [thread overview]
Message-ID: <c4d769e6-b906-f5f4-255b-7faf27f8702f@redhat.com> (raw)
In-Reply-To: <56cebf15-cf9d-475f-b388-b2be723697f6@gmail.com>
Hi,
On 7/19/21 6:10 PM, Julian Sikorski wrote:
> W dniu 19.07.2021 o 14:47, Oliver Neukum pisze:
>>
>>> Hi all,
>>>
>>> apologies for necro-ing this thread. I have just tried this drive with
>>> my new laptop (Asus ZenBook UM425IA) and the same quirk was needed to
>>> get the drive to work:
>>> options usb-storage quirks=059f:1061:u
>>>
>>> Should we still try to get uas working with this drive or should I
>>> send a patch hardcoding a quirk? I am on 5.13.2-300.fc34.x86_64 kernel
>>> now. Thanks for the feedback in advance.
>>>
>>
>> Hi,
>>
>>
>> sometimes we must give up. This thing is too elusive. Please send a
>> patch with a quirk.
>>
>> Regards
>>
>> Oliver
>>
>>
>
> Hi,
>
> thanks for confirming. Patch is attached, it appears to be working correctly when applied against 5.13.3. Please let me know if changes are required.
I seem to have missed the earlier part of this thread somehow.
Looking at the USB-ids, your model seems mightily close to this existing quirk:
UNUSUAL_DEV(0x059f, 0x105f, 0x0000, 0x9999,
"LaCie",
"2Big Quadra USB3",
USB_SC_DEVICE, USB_PR_DEVICE, NULL,
US_FL_NO_REPORT_OPCODES | US_FL_NO_SAME),
Before we go with the suggested patch, can you give the uas driver one last
try with:
options usb-storage quirks=059f:1061:fk
? The fk translates like this:
f -> US_FL_NO_REPORT_OPCODES
k -> US_FL_NO_SAME
Regards,
Hans
next prev parent reply other threads:[~2021-07-27 21:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 13:31 Lacie Rugged USB3-FW does not work with UAS Julian Sikorski
2019-08-23 13:39 ` Oliver Neukum
2019-08-23 13:43 ` Julian Sikorski
2019-08-23 14:21 ` Julian Sikorski
2019-08-23 21:23 ` Oliver Neukum
2019-08-24 7:08 ` Julian Sikorski
2019-08-29 18:33 ` Julian Sikorski
2019-09-02 11:42 ` Oliver Neukum
2019-09-02 20:10 ` Julian Sikorski
2019-09-04 15:58 ` Nathan Stratton Treadway
2019-09-04 17:10 ` Julian Sikorski
2019-09-09 12:45 ` Oliver Neukum
2019-09-09 16:18 ` Julian Sikorski
2021-07-17 8:28 ` Julian Sikorski
2021-07-19 12:47 ` Oliver Neukum
2021-07-19 16:10 ` Julian Sikorski
2021-07-20 7:43 ` Greg KH
2021-07-20 9:35 ` Oliver Neukum
2021-07-27 21:19 ` Hans de Goede [this message]
[not found] ` <CA+xVL_QEgzb1tu-tzqYPxJF-G_a8czCp=uyZ1JJ9+5xmCcNp2Q@mail.gmail.com>
[not found] ` <CA+xVL_QrJ9f8-BwVRq1oG_yo2Cd=yQH9=TCm5g=MUO9MmdvRVA@mail.gmail.com>
2021-07-29 8:43 ` Oliver Neukum
2021-07-29 9:08 ` Hans de Goede
2021-08-01 7:36 ` Julian Sikorski
2021-08-01 8:46 ` Hans de Goede
[not found] ` <a645c513-794f-5171-d383-7b40fbb1ba18@gmail.com>
2021-08-01 7:47 ` Julian Sikorski
2021-09-12 20:13 ` Julian Sikorski
2021-09-13 7:38 ` Hans de Goede
[not found] ` <1f6c3026-143a-2004-24da-1da56e6305be@suse.com>
2021-09-13 11:50 ` Hans de Goede
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=c4d769e6-b906-f5f4-255b-7faf27f8702f@redhat.com \
--to=hdegoede@redhat.com \
--cc=belegdol@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=vgerlists@nathanst.com \
/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).