From nobody Sat Apr 5 11:16:42 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4ZVCvp2kdrz5s2jJ for ; Sat, 05 Apr 2025 11:30:46 +0000 (UTC) (envelope-from rb@gid.co.uk) Received: from gid2.gid.co.uk (ns0.gid.co.uk [IPv6:2001:470:94de::240]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gid2.gid.co.uk", Issuer "gid2.gid.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4ZVCvm6hlvz3h6p; Sat, 05 Apr 2025 11:30:44 +0000 (UTC) (envelope-from rb@gid.co.uk) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=pass (policy=none) header.from=gid.co.uk; spf=pass (mx1.freebsd.org: domain of rb@gid.co.uk designates 2001:470:94de::240 as permitted sender) smtp.mailfrom=rb@gid.co.uk Received: from mx0.gid.co.uk (mx0.gid.co.uk [194.32.164.250]) by gid2.gid.co.uk (8.15.2/8.15.2) with ESMTP id 535BGwZN069968; Sat, 5 Apr 2025 12:16:58 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from smtpclient.apple (moriarty.gid.co.uk [194.32.164.17]) by mx0.gid.co.uk (8.14.2/8.14.2) with ESMTP id 535BGqSv084278; Sat, 5 Apr 2025 12:16:52 +0100 (BST) (envelope-from rb@gid.co.uk) From: Bob Bishop Message-Id: Content-Type: multipart/alternative; boundary="Apple-Mail=_CA2F09CE-9DBB-4D6D-A163-197601307056" List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51.11.1\)) Subject: Re: Samsung T7 external SSD support? Date: Sat, 5 Apr 2025 12:16:42 +0100 In-Reply-To: <556C4487-2E81-46E8-A9D6-3F8AE7896952@gmail.com> Cc: Tomoaki AOKI , Alexander Motin , =?utf-8?Q?S=C3=B8ren_Schmidt?= , "freebsd-current@freebsd.org" To: Steve Kargl References: <39bd6092-4bd9-4086-b202-08b83b425fb5@comcast.net> <35d2361d-80e8-489a-bd9d-6c5ada5736b8@FreeBSD.org> <591a0d84-a74a-4d8e-bd40-04475eb5b457@comcast.net> <20250405125636.b078c4cdd3638a677af16494@dec.sakura.ne.jp> <556C4487-2E81-46E8-A9D6-3F8AE7896952@gmail.com> X-Mailer: Apple Mail (2.3776.700.51.11.1) X-Spamd-Result: default: False [2.44 / 15.00]; SUSPICIOUS_RECIPS(1.50)[]; SUSPICIOUS_URL_IN_SUSPICIOUS_MESSAGE(1.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-0.85)[-0.846]; NEURAL_HAM_SHORT(-0.69)[-0.689]; NEURAL_HAM_MEDIUM(-0.63)[-0.628]; URIBL_RED(0.50)[dec.sakura.ne.jp:email]; MV_CASE(0.50)[]; HAS_ANON_DOMAIN(0.10)[]; BAD_REP_POLICIES(0.10)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FREEMAIL_CC(0.00)[dec.sakura.ne.jp,FreeBSD.org,gmail.com]; FROM_HAS_DN(0.00)[]; FREEMAIL_TO(0.00)[comcast.net]; GREYLIST(0.00)[pass,body]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; ARC_NA(0.00)[]; DMARC_POLICY_ALLOW(0.00)[gid.co.uk,none]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; R_SPF_ALLOW(0.00)[+mx:c]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; TO_DN_SOME(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@FreeBSD.org]; MID_RHS_MATCH_FROM(0.00)[]; R_DKIM_NA(0.00)[]; TAGGED_RCPT(0.00)[]; RCPT_COUNT_FIVE(0.00)[5] X-Rspamd-Queue-Id: 4ZVCvm6hlvz3h6p X-Spamd-Bar: ++ --Apple-Mail=_CA2F09CE-9DBB-4D6D-A163-197601307056 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi, > On 5 Apr 2025, at 09:40, S=C3=B8ren Schmidt = wrote: >=20 >=20 > S=C3=B8ren Schmidt > soren.schmidt@gmail.com >=20 >=20 >=20 >> On 5 Apr 2025, at 05.56, Tomoaki AOKI = wrote: >>=20 >> On Fri, 4 Apr 2025 19:44:49 -0700 >> Steve Kargl wrote: >>=20 >>> On 4/4/25 19:28, Alexander Motin wrote: >>>> On 04.04.2025 21:45, Steve Kargl wrote: >>>>> Anyone using a Samsung T7 external SSD with FreeBSD current? >>>>>=20 >>>>> If I plug the drive into a USB 2.0 port, I see >>>>>=20 >>>>> usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB mass storage=20= >>>>> device Samsung PSSD T7 Shield (0x04e8:0x61fb) >>>>> ugen0.2: at usbus0 >>>>> umass0 on uhub1 >>>>> umass0: on=20 >>>>> usbus0 >>>>> umass0: SCSI over Bulk-Only; quirks =3D 0x0100 >>>>> umass0:5:0: Attached to scbus5 >>>>> da0 at umass-sim0 bus 0 scbus5 target 0 lun 0 >>>>> da0: Fixed Direct Access SPC-4 SCSI = device >>>>> da0: Serial Number S6NPNS0Y201077Y >>>>> da0: 40.000MB/s transfers >>>>> da0: 1907729MB (3907029168 512 byte sectors) >>>>> da0: quirks=3D0x2 >>>>>=20 >>>>> However, the SSD is supposedly a USB 3.2 gen 2 device with a ~1000 = MBps >>>>> read/write speed. >>>>>=20 >>>>> When plugged into a USB 3.x port, I typically see >>>>>=20 >>>>> ugen0.2: at usbus0 >>>>>=20 >>>>> and the device is not listed with usbconfig. Repeatedly, = unplugging the >>>>> ssd and re-plugging it into the USB 3.x port, I eventually get the=20= >>>>> above dmesg output. Do I need a quirk for this SSD to get=20 >>>>> recognized? Also, >>>>> shouldn't it connect with faster transfer rate than 'da0: = 40.0MB/s'? >>>>=20 >>>> 40MB/s exactly means the device connected to USB2 controller or at = least=20 >>>> at USB2 speed. Considering that other times it does not connect at = all,=20 >>>> I wonder if some signal quality issue or something else prevents it = from=20 >>>> going proper USB3. IIRC USB3 uses completely different wires in = the=20 >>>> connector. Also USB2 and USB3 can be handled by different = controllers=20 >>>> with different drivers, so not detecting it still might be a = software=20 >>>> issue, but I can't say much about that area. >>>=20 >>> Thanks for confirming my suspension. >>>=20 >>> I've tried two different cables. I have few more I can test. >>> Unfortunately, I have to use a short USB 3.x extension cable >>> as the port is on the motherboard under a table. >=20 > Well, if you are using USB C you could try to turn the connector 180 = degrees around (it fits both ways apposed to the old connectors), = depending on driver quality and fase of the moon the USB3 side might not = be seen both ways =E2=80=A6 There are 8 distinct ways to plug in a USB C - USB C cable, and it=E2=80=99= s possible that they don=E2=80=99t all behave the same. I had such a = cable from Apple that failed in some orientations; once they had = recovered from their astonishment they replaced it. > S=C3=B8ren Schmidt > sos@deepcore.dk / sos@freebsd.org > "So much code to hack, so little time" >=20 >=20 -- Bob Bishop rb@gid.co.uk --Apple-Mail=_CA2F09CE-9DBB-4D6D-A163-197601307056 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hi,

On 5 Apr 2025, at 09:40, S=C3=B8ren Schmidt = <soren.schmidt@gmail.com> wrote:


S=C3=B8ren = Schmidt
soren.schmidt@gmail.com



On 5 Apr 2025, at 05.56, Tomoaki = AOKI <junchoon@dec.sakura.ne.jp> wrote:

On Fri, 4 Apr 2025 = 19:44:49 -0700
Steve Kargl <kargls@comcast.net> = wrote:

On 4/4/25 19:28, Alexander Motin = wrote:
On 04.04.2025 21:45, Steve Kargl = wrote:
Anyone using a Samsung T7 external = SSD with FreeBSD current?

If I plug the drive into a USB 2.0 = port, I see

usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB = mass storage
device Samsung PSSD T7 Shield = (0x04e8:0x61fb)
ugen0.2: <Samsung PSSD T7 Shield> at = usbus0
umass0 on uhub1
umass0: <Samsung PSSD T7 Shield, class = 0/0, rev 2.10/1.00, addr 47> on
usbus0
umass0:  SCSI over = Bulk-Only; quirks =3D 0x0100
umass0:5:0: Attached to scbus5
da0 at = umass-sim0 bus 0 scbus5 target 0 lun 0
da0: <Samsung PSSD T7 = Shield 0> Fixed Direct Access SPC-4 SCSI device
da0: Serial Number = S6NPNS0Y201077Y
da0: 40.000MB/s transfers
da0: 1907729MB = (3907029168 512 byte sectors)
da0: = quirks=3D0x2<NO_6_BYTE>

However, the SSD is supposedly a = USB 3.2 gen 2 device with a ~1000 MBps
read/write speed.

When = plugged into a USB 3.x port, I typically see

ugen0.2: <vendor = 0x0507 product 0x0204> at usbus0

and the device is not listed = with usbconfig.  Repeatedly, unplugging the
ssd and re-plugging = it into the USB 3.x port, I eventually get the
above dmesg = output.  Do I need a quirk for this SSD to get =
recognized?  Also,
shouldn't it connect with faster transfer = rate than 'da0: 40.0MB/s'?

40MB/s exactly means the = device connected to USB2 controller or at least
at USB2 speed.  = Considering that other times it does not connect at all,
I wonder if = some signal quality issue or something else prevents it from
going = proper USB3.  IIRC USB3 uses completely different wires in the =
connector.  Also USB2 and USB3 can be handled by different = controllers
with different drivers, so not detecting it still might = be a software
issue, but I can't say much about that = area.

Thanks for confirming my = suspension.

I've tried two different cables.  I have few = more I can test.
Unfortunately, I have to use a short USB 3.x = extension cable
as the port is on the motherboard under a = table.

Well, if you = are using USB C you could try to turn the connector 180 degrees around = (it fits both ways apposed to the old connectors), depending on driver = quality and fase of the moon the USB3 side might not be seen both ways = =E2=80=A6

There are 8 = distinct ways to plug in a USB C - USB C cable, and it=E2=80=99s = possible that they don=E2=80=99t all behave the same. I had such a cable = from Apple that failed in some orientations; once they had recovered = from their astonishment they replaced it.

S=C3=B8ren Schmidt
sos@deepcore.dk / sos@freebsd.org
"So much code = to hack, so little time"
= --Apple-Mail=_CA2F09CE-9DBB-4D6D-A163-197601307056--