Problem with my Canon Lide 25 scanner and Sane/XSane

hansdezwart · 08-19-2007, 11:57 AM

Yesterday I bought a Canon Lide 25 scanner. I had first checked the Sane supported devices database and saw that the support was "good" using the plustek backend.

I have connected the scanner to my laptop and everything seems to be okay.

The output of

Code:

sane-find-scanner

(run as a normal user) is

Code:

found USB scanner (vendor=0x04a9 [Canon], product=0x2220 [CanoScan], chip=LM9832/3) at libusb:001:003

When I run

Code:

scanimage -T

I hear the scanner working and I get the following output

Code:

scanimage: scanning image of size 202x150 pixels at 24 bits/pixel
scanimage: acquiring RGB frame, 8 bits/sample
scanimage: reading one scanline, 606 bytes...   PASS
scanimage: reading one byte...          PASS
scanimage: stepped read, 2 bytes...     PASS
scanimage: stepped read, 4 bytes...     PASS
scanimage: stepped read, 8 bytes...     PASS
scanimage: stepped read, 16 bytes...    PASS
scanimage: stepped read, 32 bytes...    PASS
scanimage: stepped read, 64 bytes...    PASS
scanimage: stepped read, 128 bytes...   PASS
scanimage: stepped read, 256 bytes...   PASS
scanimage: stepped read, 512 bytes...   PASS
scanimage: stepped read, 1024 bytes...  PASS
scanimage: stepped read, 1023 bytes...  PASS
scanimage: stepped read, 511 bytes...   PASS
scanimage: stepped read, 255 bytes...   PASS
scanimage: stepped read, 127 bytes...   PASS
scanimage: stepped read, 63 bytes...    PASS
scanimage: stepped read, 31 bytes...    PASS
scanimage: stepped read, 15 bytes...    PASS
scanimage: stepped read, 7 bytes...     PASS
scanimage: stepped read, 3 bytes...     PASS

Then when I run Xsane (or Kooka) for that matter everything still looks fine. The device is found, the correct backend is used. But when I try to do a preview or an actual scan nothing happens: the scanner stays silent!

Xsane/Kooka apparently seem to think they are doing fine as they show a completely black preview and ask me if I want to save that.

I rune sane version 1.0.18 on a standard Ubuntu Feisty installation with a 2.6.20-16-generic kernel and Gnome 2.18.1.

I hope anybody can help me solve my problem! Thanks in advance!

Hans de Zwart

hansdezwart · 08-22-2007, 06:10 AM

The plustek backend maintainer, Gerhard Jaeger, has given me the following answer to my problem:

======================================
I can't help you - sorry. This is a known problem with the Debian based
(also Ubuntu) Kernels, since they have activated CONFIG_USB_SUSPEND.
This feature is good to save power esp. on a laptop, but is known to
cause trouble with more or less all USB scanners.

One possible fix is to recompile your kernel without that option.
Probably it'll help to start the button daemon, which scans the
scanner buttons and will not allow the device to go to sleep.
Another fix is to upgrade the kernel to a more recent one (>= 2.6.22),
where there is some kind of blacklisting implemented to switch off
the suspend stuff for certain devices.

See also this report:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=419197
Esp. message #36
http://bugs.debian.org/cgi-bin/bugre...?bug=419197#36

Another report...
https://bugs.launchpad.net/debian/+s....20/+bug/85488

Guess in the reports you'll find some more hints and workarounds.
======================================

That just makes it a little easier to solve!