What i'm seeing is that with the current builds, the USB3 chipset seems not properly recognized and is referenced by its memory block(?) instead. Result is that the UAS driver that i'm trying to use, to optimize the speed to my external drives, isn't working. (well that is my interpretation of analyzing dmesg)
Anybody any tips on what i could do to fix this? I don't really have a clue where to start to be honest.
[ 1.254451] xhci-hcd f10f8000.usb3: xHCI Host Controller
[ 1.270661] xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus number 2
[ 1.278236] xhci-hcd f10f8000.usb3: hcc params 0x0a000990 hci version 0x100 quirks 0x00010010
[ 1.286822] xhci-hcd f10f8000.usb3: irq 44, io mem 0xf10f8000
[ 1.300646] xhci-hcd f10f8000.usb3: xHCI Host Controller
[ 1.305983] xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus number 3
[ 1.911008] usb 3-1: USB controller f10f8000.usb3 does not support streams, which are required by the UAS driver.
[ 1.916164] usb 3-1: Please try an other USB controller if you wish to use UAS.
well, my point is. Doesn't it support it because it doesn't recognize the chip properly and uses somekind of generic method, or is it really just only that?
kmod-usb3 is no longer required for the WRT AC Series, as USB3 support is built into the kernel.
Also, I may be wrong, but OHCI, nor UHCI, is needed since both are USB1.1 controllers (EHCI is a USB2 controller). There's a chance you're working with ancient equipment, but most would be hard pressed to find a device or peripheral that's still using USB1 or 1.1