CanoScan LiDE 120 not recognized

Hi guys,

following issue:

I plugin my CanoScan LiDE 120, it gets recognized according to dmesg:

[   64.536498] usb 3-3: new high-speed USB device number 10 using xhci_hcd
[   64.661014] usb 3-3: New USB device found, idVendor=04a9, idProduct=190e, bcdDevice= 7.04
[   64.661029] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   64.661034] usb 3-3: Product: CanoScan
[   64.661039] usb 3-3: Manufacturer: Canon

Also by lsusb:

Bus 003 Device 010: ID 04a9:190e Canon, Inc. CanoScan LiDE 120

Also by sane-find-scanner:


$ sudo 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.
  # Also you need support for SCSI Generic (sg) in your operating system.
  # If using Linux, try "modprobe sg".

found possible USB scanner (vendor=0x06cb, product=0x00bd) at libusb:003:004
found possible USB scanner (vendor=0x04a9 [Canon], product=0x190e [CanoScan], chip=GL848+) at libusb:003:002
  # Your USB scanner was (probably) detected. It may or may not be supported by
  # SANE. Try scanimage -L and read the backend's manpage.

But scanimage -L doesn’t see it:

$ sudo scanimage -L
[sudo] Passwort fĂĽr photon: 

No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).

Graphical scanning tools like simple-scan, fail to recognize it as well. What could I do to further diagnose the issue?

Thanks in advance for any hints!

edit: I thought, the scanner used to work earlier, but possibly it was on my other machine (desktop PC running Arch). It still works there, so for now I don’t need the scanner any more. But it would be great if I could use it on my Manjaro laptop as well! :slight_smile:

ArchWiki - SANE - Troubleshooting - Communication via xHCI not working

Some older scanner models do not work when connected via an USB3 port. If you experience this issue, try setting the SANE_USB_WORKAROUND=1 environment variable before starting your frontend

If that does not work, try one of the following workarounds:

  • Use an USB2 port instead of an USB3 port, if available.
  • Disable xHCI via BIOS/EFI. eHCI will consequently be used and communication with the scanner will work. On the downside, USB3 speed can not be reached on any port.
  • On (some) intel chipsets the setpci command can be used to route specific usb ports to either the xHCI or the eHCI controller. See force-a-single-usb-3-0-port-to-work-as-usb-2-0 (scroll down to where it says “setpci”) for further information. With this it is possible to toggle single USB ports with a simple shell script.
  • Connect the scanner over the network instead if it is supported.
1 Like

Unfortunately, setting the variable had no effect and the laptop has no USB2 ports, also I’d like to not permanently go down to USB2 speed because I’m using the scanner like once a year… I’ll have a look into the setpci command, thanks for the hints!

You can disable USB 3 when you need to use the scanner, then enable it again afterwards.

1 Like

Is this possible without reboot, such that I can include it into a script launching simple-scan? If not, I think, I’ll just live with my laptop being unable to connect to my scanner, because I use it very rarely and always can use my desktop PC instead. I just thought, it would be nice to find a fix, but I’m not dependent on it.

A USB 3 connector has 9 pins, whereas a USB 2 connector only has 4 pins, so a USB 3 port should use USB 2 if only 4 pins are connected

It might be possible to get scanner working by using a USB 2 cable or un-powered hub, but a powered hub with a USB 2 controller is more likely to work

Or use a network connection to the desktop system