From nobody Sat Apr 05 02:44:49 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 4ZV0F72vGZz5sqlT for ; Sat, 05 Apr 2025 02:44:59 +0000 (UTC) (envelope-from kargls@comcast.net) Received: from resqmta-c2p-570216.sys.comcast.net (resqmta-c2p-570216.sys.comcast.net [IPv6:2001:558:fd00:56::6]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4ZV0F654Jnz3DWv for ; Sat, 05 Apr 2025 02:44:58 +0000 (UTC) (envelope-from kargls@comcast.net) Authentication-Results: mx1.freebsd.org; none Received: from resomta-c2p-555954.sys.comcast.net ([96.102.18.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 256/256 bits) (Client did not present a certificate) by resqmta-c2p-570216.sys.comcast.net with ESMTPS id 0tAZuTI3tW5O50tWduSSBT; Sat, 05 Apr 2025 02:44:51 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1743821091; bh=klvJwwLKr0pYj4RtR8A1my4giIm4z3oZ8zon4Gn7yYU=; h=Received:Received:Message-ID:Date:MIME-Version:Subject:To:From: Content-Type:Xfinity-Spam-Result; b=H7cxuYqBC1F59JH8MX4uUD3yyddbOvg3WSq/gzPk58Rczzwn+XM8J3ADneY+ft+Jw FuSC0zr3etW9/+k0PnsEyAWVis00Q33zCFLJ5tysQODKoMEvkkP05fBT+3b8LIhfmN hAqjMF2R/5uiNxrr/a0D9x+X/A644ZV4iEySBaIlUKAJb1Yn9D3EZFoIIDIIcpztGr Ih3NH8i5EaHarLXQmuqq4icnmX9mZpAL9XWthfELywS6FzDaFgb6CRjF73kri5yIAK jhM7aVjWBLzmKniS2itUuItDHpY/9tVz+LS2FwAA3KBNdxcyIg4hnyg/ZKlFRbvUqv bOqQqo6iz7FhA== Received: from [10.0.0.30] ([73.83.213.54]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 256/256 bits) (Client did not present a certificate) by resomta-c2p-555954.sys.comcast.net with ESMTPSA id 0tWbugbUVWkiv0tWcum2Z4; Sat, 05 Apr 2025 02:44:51 +0000 Message-ID: <591a0d84-a74a-4d8e-bd40-04475eb5b457@comcast.net> Date: Fri, 4 Apr 2025 19:44:49 -0700 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 User-Agent: Mozilla Thunderbird Subject: Re: Samsung T7 external SSD support? To: Alexander Motin , freebsd-current@freebsd.org References: <39bd6092-4bd9-4086-b202-08b83b425fb5@comcast.net> <35d2361d-80e8-489a-bd9d-6c5ada5736b8@FreeBSD.org> Content-Language: en-US From: Steve Kargl In-Reply-To: <35d2361d-80e8-489a-bd9d-6c5ada5736b8@FreeBSD.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4xfCGk0JUW90nhRESr9lc57Jry8/597OObkk7EPDq++Fx4+lCxALUrz3ObDO/rt8tjVhLFS47zotSQsX/HMOFNBqnkaSJupIw2WJYDB36e3gvSZM4AY1tT VNcP8AktS4wDX/E4TZJns3SYbhgmfuL1vJW6mBWGCDR615ZltSGR6Z//cAo8N6kr4KZyugXJxLSiRaatVF1X1Z8oaUrmetvNAzyxG3bUtGAH+eiU7LLV3/Kz X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7922, ipnet:2001:558::/29, country:US] X-Rspamd-Queue-Id: 4ZV0F654Jnz3DWv X-Spamd-Bar: ---- 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: at usbus0 >> umass0 on uhub1 >> umass0: on >> usbus0 >> umass0:  SCSI over Bulk-Only; quirks = 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=0x2 >> >> 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: 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. -- steve