[sane-devel] CanoScan LiDE 25 found by sane-find-scanner but not scanimage

Warren Post warren at copaninvest.com
Fri Sep 1 22:40:42 UTC 2006

My Canon CanoScan LiDE 25 is found by sane-find-scanner but not by
scanimage (using sane-frontends-1.0.13-2mdk, xsane-0.97-2mdk, and
sane-backends-1.0.17-2.1.20060mdk on Mandriva 2006). So far I have done
the following:

1. Downloaded and installed a version of sane-backends (1.0.17) that
supports the LiDE 25 to replace my older 1.0.16.

2. Insured that the scanner is seen by the USB subsystem and reports
information consistent with man sane-plustek:

[warren at gerencia ~]$ lsusb
Bus 001 Device 002: ID 04a9:2220 Canon, Inc. 
Bus 001 Device 001: ID 0000:0000

3. Modified /etc/sane.d/plustek.conf per man sane-plustek.
Specifically, I added the line "[usb] 0x04a9 0x2220". I have tried both
"device auto" and not having a device line.

4. Insured that sane-find-scanner sees the LiDE 25 and reports
information consistent with man sane-plustek:

[warren at gerencia ~]$ sane-find-scanner [snip]
found USB scanner (vendor=0x04a9 [Canon], product=0x2220 [CanoScan],
chip=LM9832/3) at libusb:001:002

5. Run "scanimage -L" with debugging on, looking for clues. I can send
the entire lengthy output if desired, but what jumps out at me is:

[warren at gerencia ~]$ export SANE_DEBUG_PLUSTEK=24 
[warren at gerencia ~]$ export SANE_DEBUG_DLL=24 
[warren at gerencia ~]$ export SANE_DEBUG_SANEI_USB=24 
[warren at gerencia ~]$ scanimage -L 
[plustek] Checking for 0x04a9-0x2206
[plustek] Checking for 0x04a9-0x2207
[plustek] Checking for 0x04a9-0x2208
[plustek] Checking for 0x04a9-0x220d
[plustek] Checking for 0x04a9-0x220e
[plustek] Available and supported devices: 
[plustek] NONE.

Sane-plustek checks for other Canon (vendor ID 0x04a9) scanners, but not
for the one I am interested in (product ID 0x2200) and that is supported
by 1.0.17. Huh? I check to make sure that my version of sane-backends
really is 1.0.17 and not something earlier:

[warren at gerencia ~]$ rpm -q sane-backends

I have searched the sane mailing list archives, read the sane-plustek
homepage, and googled for clues on what might be wrong on my end to
cause a backend to not check for a supported scanner, but have
come up empty. Any ideas on what else I should be looking at to solve
this issue?

Warren Post
Santa Rosa de Copán, Honduras

More information about the sane-devel mailing list