plustek@linuxhacker.org

On Wednesday 08 September 2004 10:12, Felix Holzke wrote:
> Am Mi, den 08.09.2004 schrieb Gerhard Jaeger um 8:49:
> > > It is detected by sane-find-scanner but not by scanimage -L. Below
> > > there is my configuration and debug output.
> >
> > I guess the configuration is wrong, try the following:
> >
> > [usb]
> > device auto
> >
> > remove all the other stuff...
>
> I did that before but now again with all other stuff removed (see
> below). No success. I noticed that with the lide 20 canon removed the
> usb 2.0 capability from the lide 20 after some time, at least they
> removed that description from packing (I use one of the early usb2
> capable ones). Since you write something about chipset changes in other
> plustek models within the same product series, can I somehow check the
> chipset etc. to recognize if my scanner is the model your driver expects
> it to be?

The LiDE20 has never had USB2.0 capabilities, as they have always used the
LM9833 chip, which does only support USB1.1. It surely works on 2.0 ports, but
only @ 12Mib/s...

>
> sane-find-scanner offers:
> vendor=0x04a9 [Canon], product=0x220d [CanoScan], chip=LM9832/3
> and your man page says:
> CanoScan LIDE20    LM9833  600x1200dpi 48bit 512Kb 0x220D
>
> Can I provide some additional information which could help you solve the
> problem?

Yes, the auto does not find your scanner, and so I'm sure, that there are some
problems with the libusb stuff....

What is the output of sane-find-scanner -v -v (as root-user)?
What is the output of scanimage -L (as root-user)?
What is the output of sane-config --libs?
Please try:
export SANE DEBUG SANEI USB=255 ; export SANE DEBUG PLUSTEK=20; scanimage -L

Ciao,
  Gerhard