From: "David C. Partridge" <david.partridge@perdrix.co.uk>
To: "'Oliver Neukum'" <oneukum@suse.com>, <linux-usb@vger.kernel.org>
Subject: RE: Issues with LaCie USB3 drive and UAS
Date: Wed, 2 Dec 2020 11:12:29 -0000 [thread overview]
Message-ID: <000001d6c89c$086812e0$193838a0$@perdrix.co.uk> (raw)
In-Reply-To: <11ea70180f52b4965a451b3970891e0f547c777b.camel@suse.com>
A helpful person on the Ubuntu forums sent me a patched usb-storage.ko that was built using your patch file.
Here's what the system had to say when I tried it with the modified /etc/modprobe.d/blacklist-uas.conf w/r:
options usb-storage quirks=059f:105f:k
Dec 02 11:02:01 charon kernel: usb 2-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Dec 02 11:02:01 charon kernel: usb 2-1: New USB device found, idVendor=059f, idProduct=105f, bcdDevice= 0.01
Dec 02 11:02:01 charon kernel: usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
Dec 02 11:02:01 charon kernel: usb 2-1: Product: 2Big Quadra USB3
Dec 02 11:02:01 charon kernel: usb 2-1: Manufacturer: LaCie
Dec 02 11:02:01 charon kernel: usb 2-1: SerialNumber: 00000000250e9e711084
Dec 02 11:02:01 charon mtp-probe[2490]: checking bus 2, device 2: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
Dec 02 11:02:01 charon mtp-probe[2490]: bus: 2, device: 2 was not an MTP device
Dec 02 11:02:01 charon kernel: usb_storage: loading out-of-tree module taints kernel.
Dec 02 11:02:01 charon kernel: usb_storage: module verification failed: signature and/or required key missing - tainting kernel
Dec 02 11:02:01 charon kernel: usbcore: registered new interface driver usb-storage
Dec 02 11:02:01 charon kernel: scsi host5: uas
Dec 02 11:02:01 charon kernel: scsi 5:0:0:0: Direct-Access LaCie 2Big Quadra v3 051E PQ: 0 ANSI: 6
Dec 02 11:02:01 charon kernel: usbcore: registered new interface driver uas
Dec 02 11:02:01 charon kernel: sd 5:0:0:0: Attached scsi generic sg3 type 0
Dec 02 11:02:01 charon mtp-probe[2499]: checking bus 2, device 2: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
Dec 02 11:02:01 charon mtp-probe[2499]: bus: 2, device: 2 was not an MTP device
Dec 02 11:02:01 charon kernel: sd 5:0:0:0: [sdc] 7814025564 512-byte logical blocks: (4.00 TB/3.64 TiB)
Dec 02 11:02:01 charon kernel: sd 5:0:0:0: [sdc] Write Protect is off
Dec 02 11:02:01 charon kernel: sd 5:0:0:0: [sdc] Mode Sense: 43 00 00 00
Dec 02 11:02:01 charon kernel: sd 5:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Dec 02 11:02:17 charon kernel: usb 2-1: USB disconnect, device number 2
Dec 02 11:02:17 charon kernel: sd 5:0:0:0: [sdc] Optimal transfer size 33553920 bytes
Dec 02 11:02:18 charon kernel: sd 5:0:0:0: [sdc] Read Capacity(16) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Dec 02 11:02:18 charon kernel: sd 5:0:0:0: [sdc] Sense not available.
Dec 02 11:02:18 charon kernel: sd 5:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Dec 02 11:02:18 charon kernel: sd 5:0:0:0: [sdc] Sense not available.
Dec 02 11:02:18 charon kernel: sd 5:0:0:0: [sdc] 0 512-byte logical blocks: (0 B/0 B)
Regards
David
-----Original Message-----
From: Oliver Neukum [mailto:oneukum@suse.com]
Sent: 26 November 2020 10:22
To: David C. Partridge; linux-usb@vger.kernel.org
Subject: Re: Issues with LaCie USB3 drive and UAS
Am Donnerstag, den 26.11.2020, 09:33 +0000 schrieb David C. Partridge:
> I tried that but that wiped out the debian folder :(
Hi,
that is a pronblem as I do not use Debian, nor know a lot about it.
You can try "make clean" instead of "make mrproper" , as it is milder.
And yes, this is programmer humor.
HTH
Oliver
next prev parent reply other threads:[~2020-12-02 11:13 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-08 10:56 Issues with LaCie USB3 drive and UAS David C. Partridge
2020-11-09 9:29 ` Oliver Neukum
2020-11-09 9:51 ` David C. Partridge
2020-11-09 10:13 ` Oliver Neukum
2020-11-09 11:21 ` David C. Partridge
2020-11-09 15:21 ` David C. Partridge
2020-11-09 16:47 ` David C. Partridge
2020-11-11 11:43 ` Oliver Neukum
2020-11-11 15:50 ` David C. Partridge
2020-11-11 19:18 ` Oliver Neukum
2020-11-11 20:54 ` David C. Partridge
2020-11-23 14:59 ` Oliver Neukum
2020-11-25 12:25 ` David C. Partridge
2020-11-26 8:24 ` Oliver Neukum
2020-11-26 9:33 ` David C. Partridge
2020-11-26 10:22 ` Oliver Neukum
[not found] ` <0000 01d6c89c$086812e0$193838a0$@perdrix.co.uk>
2020-12-02 11:12 ` David C. Partridge [this message]
[not found] ` <612be9a9cd6ffdb9492781e174859c7b4e69 4a86.camel@suse.com>
2020-12-02 11:38 ` Oliver Neukum
2020-12-02 13:39 ` David C. Partridge
2020-12-03 2:11 ` David C. Partridge
2020-12-03 13:16 ` Oliver Neukum
2020-12-03 14:30 ` David C. Partridge
2020-12-07 10:53 ` David C. Partridge
2020-12-08 14:03 ` Oliver Neukum
2020-12-08 16:06 ` David C. Partridge
2020-12-08 16:27 ` Alan Stern
2020-12-08 16:47 ` David C. Partridge
2020-12-08 17:45 ` 'Alan Stern'
2020-12-08 20:00 ` David C. Partridge
2020-12-09 11:11 ` Oliver Neukum
2020-12-03 14:06 ` Oliver Neukum
2020-12-03 14:46 ` David C. Partridge
2020-12-03 16:16 ` 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='000001d6c89c$086812e0$193838a0$@perdrix.co.uk' \
--to=david.partridge@perdrix.co.uk \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.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).