linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Julian Sikorski <belegdol@gmail.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Oliver Neukum <oneukum@suse.com>,
	Nathan Stratton Treadway <vgerlists@nathanst.com>,
	USB list <linux-usb@vger.kernel.org>
Subject: Re: Lacie Rugged USB3-FW does not work with UAS
Date: Sun, 1 Aug 2021 09:36:17 +0200	[thread overview]
Message-ID: <7c0a8a94-b6ac-c09e-31db-11fbb7bcd365@gmail.com> (raw)
In-Reply-To: <830f09f8-7e16-425e-d5dc-2c5102ee4c7a@redhat.com>

Am 29.07.21 um 11:08 schrieb Hans de Goede:
> Hi,
> 
> On 7/28/21 7:29 PM, Julian Sikorski wrote:
>> Hi all,
>>
>> f quirk alone seems to be sufficient.
> 
> Thank you for testing, but I'm not sure using only the NO_REPORT_OPCODES
> quirk is wise here, the other similar La Cie drive also started out with
> just that quirk, only to have the NO_SAME quirk added later. See:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8010622c86ca5bb44bc98492f5968726fc7c7a21
> 
> Actually triggering a WRITE_SAME SCSI command is likely tricky, so
> it likely requires a special workload to ensure that that flag is
> not necessary.
> 
> As Oliver set with the quirk to disable UAS we at least have the
> drive working (albeit slower then it would work with UAS) so we
> can take our time to make sure that things work properly with
> the combination of the f+k flags (at least using both seems
> best to me) before re-enabling UAS.
> 
> Regards,
> 
> Hans
> 
Hi,

are there some tests which I could run in particular to test whether 
WRITE_SAME is working as intended? I use this drive for backups which 
means I don't connect it all that often.

Best regards,
Julian

>>
>> Best regards,
>> Julian
>>
>> Julian Sikorski <belegdol@gmail.com <mailto:belegdol@gmail.com>> schrieb am Mi., 28. Juli 2021, 01:14:
>>
>>      Hi Hans,
>>
>>      apologies for top-posting and HTML but I only can send emails from my mobile currently.
>>      With fk quirk the drive indeed appears to be working with uas: I can decrypt and mount a veracrypt volume from it. Thanks!
>>      The patch disabling uas has already made it to Linus' tree and is about to be added to stable:
>>      https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6abf2fe6b4bf6e5256b80c5817908151d2d33e9f <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6abf2fe6b4bf6e5256b80c5817908151d2d33e9f>
>>      As I have no working internet on any of my Linux machines and won't for the foreseeable future (thank you construction workers), would you mind taking care of amending the quirk accordingly? Thank you in advance.
>>
>>      Best regards,
>>      Julian
>>
>>
>>      Hans de Goede <hdegoede@redhat.com <mailto:hdegoede@redhat.com>> schrieb am Di., 27. Juli 2021, 23:19:
>>
>>          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
>>
> 

  reply	other threads:[~2021-08-01  7:36 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
     [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 [this message]
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=7c0a8a94-b6ac-c09e-31db-11fbb7bcd365@gmail.com \
    --to=belegdol@gmail.com \
    --cc=hdegoede@redhat.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).