On 06/30/17 12:30, Matthias Apitz wrote:
El día viernes, junio 30, 2017 a las 08:34:21a. m. +0200, Matthias Apitz 


Thanks for the hint. I disabled the three entries for uhci, ohci and ehci:

# USB support
options         USB_DEBUG               # enable debug msgs
# device                uhci            # UHCI PCI->USB interface
# device                ohci            # OHCI PCI->USB interface
# device                ehci            # EHCI PCI->USB interface (USB 2.0)
device          xhci                    # XHCI PCI->USB interface (USB 3.0)
device          usb                     # USB Bus (required)
device          ukbd                    # Keyboard
device          umass                   # Disks/Mass storage - Requires scbus 
and da

and maybe this will help already. I will let you know and update the PR
later the day.

The new kernel detects fine the uTrust Token on USB:

$ dmesg | egrep 'ugen|uhub|xhci|ehci'
xhci0: <Intel Panther Point USB 3.0 controller> mem 0xe0500000-0xe050ffff at 
device 20.0 on pci0
xhci0: 32 bytes context size, 64-bit DMA
xhci0: Port routing mask set to 0xffffffff
usbus0 on xhci0
ugen0.1: <0x8086 XHCI root HUB> at usbus0
uhub0: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
uhub0: 13 ports with 13 removable, self powered
ugen0.2: <SunplusIT Inc HD WebCam> at usbus0
ugen0.3: <vendor 0x0489 product 0xe056> at usbus0
ugen0.4: <Identiv uTrust 3512 SAM slot Token> at usbus0

OK, nice to know. We might want to delay the attachment of the ehci/ohci/uhci drivers after xhci by default if this is a widespread issue.


freebsd-usb@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

Reply via email to