Comment # 4 on bug 955079 from Roger Whittaker

I have the same problem as described here, with the same scanner.

The hardware is an Intel NUC - if I disable xhci in the EFI BIOS, I see:

 # lsusb -t
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/8p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
        |__ Port 1: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
            |__ Port 1: Dev 5, If 0, Class=Mass Storage, Driver=usb-storage,
480M
            |__ Port 3: Dev 8, If 0, Class=Vendor Specific Class, Driver=, 12M
            |__ Port 4: Dev 7, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 2: Dev 4, If 0, Class=Mass Storage, Driver=uas, 480M
        |__ Port 4: Dev 6, If 1, Class=Human Interface Device, Driver=usbhid,
1.5M
        |__ Port 4: Dev 6, If 0, Class=Human Interface Device, Driver=usbhid,
1.5M

# lsusb
Bus 001 Device 006: ID 1a81:1004 Holtek Semiconductor, Inc. 
Bus 001 Device 004: ID 0bc2:ab26 Seagate RSS LLC 
Bus 001 Device 007: ID 2109:2812 VIA Labs, Inc. VL812 Hub
Bus 001 Device 008: ID 06bd:2061 AGFA-Gevaert NV SnapScan 1212U (?)
Bus 001 Device 005: ID 0cf2:6230 ENE Technology, Inc. SD Card Reader (UB623X)
Bus 001 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub
Bus 001 Device 002: ID 8087:8000 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

But the behaviour is the same as when xhci is enabled (and as described above).

Is this something that could one day be fixed with changes in the Linux USB
drivers, or is it ultimately just a hardware incompatibility?

And is there any mileage in trying to change the behaviour with setpci commands
as I've seen suggested elsewhere?