Arrrrg, I have been watching GooeyGirl do all the hard work as I have been working similar(same) issue, but luckily for only a few days.
My first thought, pleassseeeeeee don’t give up.
But I certainly understand addiction to USB3 sticks.
So here are my follow-on results for my issue, which certainly looks like GooeyGirls but slightly different.
My Brother is an MFC-L2700DW.
it is a brscan4 machine.
My computer is all USB3 ports.
I blocked xhci in bios, Initial testing looks good.
I can (finally) manually scan (flatbed mode), I have not yet tried MFC originated scans but will soon.
Here is some info
sudo brsaneconfig4 -d
[sudo] password for root:
-----------------------------
cat /etc/fstab
UUID=d16b7198-33ab-4315-9807-b4362c6c2bee / ext4 noatime,acl,user_xattr 1 1
UUID=2a5f7005-18b8-4c44-826a-fcd77523ef0a swap swap defaults 0 0
UUID=EACA-EE55 /boot/efi vfat umask=0002,utf8=true 0 0
UUID=470939b8-9894-47ed-b351-2e8b06a12702 /home ext4 defaults 1 2
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
tmpfs /var/tmp tmpfs defaults,noatime,mode=1777 0 0
/dev/mapper/cr_backupSRV7 /backupSRV7 ext4 acl,user_xattr,nofail 0 2
/dev/mapper/cr_loop1 /home/carl/srvc2 ext4 noauto,rw,acl,user_xattr,nofail 1 1
-----------------------------
sane-find-scanner
# sane-find-scanner will now attempt to detect your scanner. If the
# result is different from what you expected, first make sure your
# scanner is powered up and properly connected to your computer.
# No SCSI scanners found. If you expected something different, make sure that
# you have loaded a kernel SCSI driver for your SCSI adapter.
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
found USB scanner (vendor=0x04f9 [Brother], product=0x0331 [MFC-L2700DW]) at libusb:001:003
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
found USB scanner (vendor=0x0cd2, product=0xffff) at libusb:002:006
found USB scanner (vendor=0x04b8 [EPSON], product=0x0142 [EPSON Perfection V33/V330]) at libusb:002:005
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
# Your USB scanner was (probably) detected. It may or may not be supported by
# SANE. Try scanimage -L and read the backend's manpage.
# Not checking for parallel port scanners.
# Most Scanners connected to the parallel port or other proprietary ports
# can't be detected by this program.
-----------------------------
ls -R -all /proc/bus/usb
ls: cannot access '/proc/bus/usb': No such file or directory
-----------------------------
cat /proc/bus/usb/devices
cat: /proc/bus/usb/devices: No such file or directory
-----------------------------
scanimage -L
device `brother4:bus4;dev1' is a Brother MFC-L2700DW USB scanner
device `epkowa:interpreter:002:005' is a Epson Perfection V330 Photo flatbed scanner
-----------------------------
-----------------------------
/etc/opt/brother/scanner/brscan4//brsanenetdevice4.cfg:
-----------------------------
/etc/opt/brother/scanner/brscan4//Brsane4.ini:
-----------------------------
/etc/opt/brother/scanner/brscan4//models4/ext_7.ini:
-----------------------------
/etc/opt/brother/scanner/brscan4//models4/ext_1.ini:
-----------------------------
/etc/opt/brother/scanner/brscan4//models4/ext_6.ini:
-----------------------------
/etc/opt/brother/scanner/brscan4//models4/ext_5.ini:
-----------------------------
/etc/opt/brother/scanner/brscan4//models4/ext_2.ini:
-----------------------------
/etc/opt/brother/scanner/brscan4//models4/ext_17.ini:
-----------------------------
/etc/opt/brother/scanner/brscan4//models4/ext_4.ini:
-----------------------------
/etc/opt/brother/scanner/brscan4//models4/ext_8.ini:
-----------------------------
/etc/opt/brother/scanner/brscan4//models4/ext_15.ini:
-----------------------------
/etc/opt/brother/scanner/brscan4//models4/ext_3.ini:
-----------------------------
/etc/opt/brother/scanner/brscan4//models4/ext_9.ini:
-----------------------------
/etc/opt/brother/scanner/brscan4//models4/ext_13.ini:
-----------------------------
/etc/opt/brother/scanner/brscan4//models4/ext_11.ini:
-----------------------------
/etc/opt/brother/scanner/brscan4//models4/ext_18.ini:
-----------------------------
/etc/opt/brother/scanner/brscan4//models4/ext_19.ini:
-----------------------------
/etc/opt/brother/scanner/brscan4//models4/ext_12.ini:
-----------------------------
/etc/opt/brother/scanner/brscan4//models4/ext_14.ini:
-----------------------------
/etc/opt/brother/scanner/brscan4//models4/ext_10.ini:
-----------------------------
/etc/opt/brother/scanner/brscan4//models4/ext_16.ini:
-----------------------------
/etc/opt/brother/scanner/brscan4//models4/ext_20.ini:
-----------------------------
-----------------------------
ping
Not sure what else I could post that would be informative or helpful to others.
Here is a remove/re-insert
dmesg --follow
1319.914420] usb 1-1.1: USB disconnect, device number 3
1319.914502] usblp0: removed
1322.593704] usb 1-1.1: new high-speed USB device number 4 using ehci-pci
1322.688255] usb 1-1.1: New USB device found, idVendor=04f9, idProduct=0331
1322.688257] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
1322.688258] usb 1-1.1: Product: MFC-L2700DW
1322.688259] usb 1-1.1: Manufacturer: Brother
1322.688259] usb 1-1.1: SerialNumber: U63887G7N370957
1322.689399] usblp 1-1.1:1.0: usblp0: USB Bidirectional printer dev 4 if 0 alt 0 proto 2 vid 0x04F9 pid 0x0331
Aside from potential success, today I learned about dmesg --follow. Thanks!
Before blocking xhci, my thought plan was to try accessing scanner via network (IP address) connection,
since certain things just did not look right with USB. I will try that one I go back to xhci enabled.
The MFC-L2700DW is new to me, not sure if is to be considered ‘older’ hardware.
but add brscan4 to the list of drivers that appear to be allergic to xhci.