On 20 Nov 2015, edward wandasiewicz wrote: > If I try to plug in various USB 3.0 umass(4) devices into a USB 3.0 or > USB 3.1 Type C port, nothing gets registered via dmesg, even if I add > > option USB_DEBUG > option UMASS_DEBUG > option XHCI_DEBUG > > and compile a kernel. No dmesg output upon attachment of USB 3.0 > devices.
For what it's worth, also on 5.8 stable I also don't see anything twitch (dmesg, usbdevs, etc.) if I plug in a USB3 drive. > The USB 3.0 devices can only get recognised if I attach them via a USB > 2.0 cable, and plug this cable into the USB 3.0 or USB 3.1 Type C > port. Ha, an interesting discovery! If I put a cheap USB extension cable (http://www.amazon.co.uk/gp/product/B000BI804Y) inline then suddenly dmesg /does/ notice the drive, Dec 16 15:00:47 saffron /bsd: umass0 at uhub0 Dec 16 15:00:47 saffron /bsd: port 4 configuration 1 interface 0 "Seagate Expansion" rev 2.10/7.06 addr 2 Dec 16 15:00:47 saffron /bsd: umass0: using SCSI over Bulk-Only Dec 16 15:00:47 saffron /bsd: scsibus4 at umass0: 2 targets, initiator 0 Dec 16 15:03:55 saffron /bsd: sd1 at scsibus4 targ 1 lun 0: <Seagate, Expansion, 0706> SCSI4 0/direct fixed though not in any useful way, e.g., # fdisk sd1 fdisk: sd1: Device not configured > $ pcidump -v 0:20:0 > > 0:20:0: Intel 9 Series xHCI > 0x0000: Vendor ID: 8086 Product ID: 9cb1 I too have this. -- Mark
