When configuring a Canon Lide20 scanner through Yast, the scanner is
detected as:

"USB scanner (vendor=0x04a9 [Canon], product=0x2213 [CanoScan],
chip=GL841) at libusb:001:003"

yet when I associate it with the Canoscan Lide20 scanner, the plustek
driver is associated, but the 'Associated Scanner' remains blank.

Any ideas?

JC

Tardis:~ # sane-find-scanner

  # No SCSI scanners found. If you expected something different, make
sure that
  # you have loaded a SCSI driver for your SCSI adapter.

found USB scanner (vendor=0x04a9 [Canon], product=0x2213 [CanoScan],
chip=GL841)
  # 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.

Tardis:~ # scanimage -L

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).


-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20050824/4c4f1d53/attachment.htm
From jsm...@suse.de  Wed Aug 24 09:23:29 2005
From: jsm...@suse.de (Johannes Meixner)
Date: Wed Aug 24 09:23:38 2005
Subject: [sane-devel] Canoscan Lide 20, suse 9.3
In-Reply-To: <1124864792.7125.14.camel@Tardis.considine.local>
References: <1124864792.7125.14.camel@Tardis.considine.local>
Message-ID: <pine.lnx.4.58.0508241117380.4...@wotan.suse.de>


Hello,

On Aug 24 14:26 John Charles Considine wrote (shortened):
> When configuring a Canon Lide20 scanner through Yast, the scanner is
> detected as:
> 
> "USB scanner (vendor=0x04a9 [Canon], product=0x2213 [CanoScan],
> chip=GL841) at libusb:001:003"
> 
> yet when I associate it with the Canoscan Lide20 scanner, the plustek
> driver is associated, but the 'Associated Scanner' remains blank.

Was the "plustek" line really activated in /etc/sane.d/dll.conf?

> Tardis:~ # sane-find-scanner
...
> found USB scanner (vendor=0x04a9 [Canon], product=0x2213 [CanoScan],
> chip=GL841)

Strange, here the "at libusb:001:003" is missing.
Is it listed in the output of the "/sbin/lsusb" command?

> Tardis:~ # scanimage -L
> 
> No scanners were identified...

Which sane package version do you use?
The sane package from the Suse Linux 9.3 CDs or something else?

See
http://portal.suse.com/sdb/en/2004/10/jsmeix_scanner-setup-92.html
"Trouble-Shooting (Debugging)"
how to provide debugging information.

Kind Regards
Johannes Meixner
-- 
SUSE LINUX Products GmbH, Maxfeldstrasse 5      Mail: jsm...@suse.de
90409 Nuernberg, Germany                    WWW: http://www.suse.de/

Reply via email to