On Sun 25 Apr 2021 at 21:32:27 +0200, Rhialto wrote: > $ egrep 'uhub|usb|xhci' /var/run/dmesg.boot > xhci0 at pci0 dev 20 function 0: Intel 300 Series USB 3.1 xHCI (rev. 0x10) > xhci0: 64-bit DMA > xhci0: interrupting at msi1 vec 0 > xhci0: xHCI version 1.10 > usb0 at xhci0: USB revision 3.1 > usb1 at xhci0: USB revision 2.0 > uhub0 at usb0: NetBSD (0x0000) xHCI root hub (0x0000), class 9/0, rev 3.00/1.00, addr 0 > uhub0: 6 ports with 6 removable, self powered > uhub1 at usb1: NetBSD (0x0000) xHCI root hub (0x0000), class 9/0, rev 2.00/1.00, addr 0 > uhub1: 16 ports with 16 removable, self powered > uhidev0 at uhub1 port 7 configuration 1 interface 0 > uhidev1 at uhub1 port 7 configuration 1 interface 1 > uhidev2 at uhub1 port 8 configuration 1 interface 0 So those usb sticks were USB-2, attaching to uhub1. Today I tried a USB-3 device, attaching to uhub0 (a real external spinning disk). I plugged it in 3 times in succession and it went ok every time. It is not only an umass but also a ses device. My "BIOS setup" has something about "XHCI handoff", supposingly something for compatibility with some OSes. I turned it on on the general principle that anything "for compatibility" would apply to non-Windows OSes. For the USB-2 case, could it help to keep it disabled instead? Is it even clear what the option might do? A quick googling didn't reveal anything interesting. -Olaf. -- ___ Q: "What's an anagram of Banach-Tarski?" -- Olaf "Rhialto" Seibert \X/ A: "Banach-Tarski Banach-Tarski." -- rhialto at falu dot nl
Attachment:
signature.asc
Description: PGP signature