On Thu, Sep 04, 2025 at 02:52:20PM +0100, Crystal Kolipe wrote:
> On Thu, Sep 04, 2025 at 01:46:39PM +0200, Fox Steward wrote:
> > Hi there,
> >
> > the following hardware is not recognized by OpenBSD 7.7,
> > using a Lenovo Thinkpad Carbon X1 6th Gen, neither on usb-c or usb-a port.
> >
> > - external enclosure for M.2 NVMe SSD: Delock USB 3.2 Gen 2 (42600),
> > Chipset: JMicron JMS583 [1]
> > - with Crucial P3 Plus 2TB PCIe 4.0 NVMe M.2 SSD
> >
> > Device works fine with none OpenBSD devices (e.g. LineageOS Smartphone).
> >
> > Could someone explain why this is the case?
>
> What exactly do you mean by 'not recognised'?
By that I mean there is no message in /var/log/messages whatsoever about a
newly connected
or recognised device when I connect the enclosure via usb-c or usb-a.
As for the usb-c case, I tested it with both Thunderbolt being activated and
deactivated in BIOS.
>
> Is the USB enclosure not detected at all, or does it just not present an sd
> device, for example connecting as ugen instead?
>
> The output of usbdevs -vv would be helpful if it's recognised at all.
---
$ usbdevs -vv
Controller /dev/usb0:
addr 01: 8086:0000 Intel, xHCI root hub
super speed, self powered, config 1, rev 1.00
driver: uhub0
port 01: 0000.02a0 power Rx.detect
port 02: 0000.0503 connect enabled recovery
port 03: 0000.02a0 power Rx.detect
port 04: 0000.02a0 power Rx.detect
port 05: 0000.02a0 power Rx.detect
port 06: 0000.02a0 power Rx.detect
port 07: 0000.02a0 power Rx.detect
port 08: 0000.02a0 power Rx.detect
port 09: 0000.02a0 power Rx.detect
port 10: 0000.02a0 power Rx.detect
port 11: 0000.02a0 power Rx.detect
port 12: 0000.02a0 power Rx.detect
port 13: 0000.02a0 power Rx.detect
port 14: 0000.02a0 power Rx.detect
port 15: 0000.0203 connect enabled power U0
port 16: 0000.02a0 power Rx.detect
addr 02: 2109:2811 VIA Labs, Inc., USB2.0 Hub
high speed, self powered, config 1, rev 90.40
driver: uhub1
port 01: 0000.0100 power
port 02: 0000.0303 connect enabled power
port 03: 0000.0100 power
port 04: 0000.0103 connect enabled power
addr 03: 04d9:0169 Holtek, USB Keyboard
low speed, power 100 mA, config 1, rev 2.09
driver: uhidev0
driver: uhidev1
addr 04: 046d:c52f Logitech, USB Receiver
full speed, power 98 mA, config 1, rev 30.00
driver: uhidev2
driver: uhidev3
addr 05: 0bda:0328 Generic, USB3.0-CRW
super speed, power 200 mA, config 1, rev 29.08, iSerial
28203008282014000
driver: umass0
---
>
> > Is there another eclosure that is known to work with this M.2 SSD?
>
> Various enclosures work, anything that presents as a regular usb mass storage
> device would be expected to work.
>
> If you want a JMicron chipset based device, I can confirm that the Icy Box
> IB-1807MT-C31 works with OpenBSD, (and has a write-protect switch which may be
> useful depending on your application).
>
> The Sabrent EC-SNVE also works, (but lacks a write-protect switch). This uses
> a Realtek chipset.
>
Thank you for that information. I don't have a hard requirement on a JMicron
chipset.
Well, I don't know enough details to know what is better or worse. The delock
enclosure seemed like a quality piece of hardware.
I would love to understand more about the inner workings, components and
communication
flow for this use case. In particular, why it would be failing, which
driver/firmware
might be missing and if there is a chance it would be supported in the future.
In general I would like to better understand the world of drivers/firmware in
the context of OpenBSD.
Essentially, what decides if a hardware is supported by OpenBSD or not, and how
will I be able to
tell in the future before buying some hardware. Obviously, I should have done a
better job of research beforehand.
