[sane-devel] Re: [Canoscan5000f-cvs] [Canoscan5000f] news.

[Henning Meier-Geinitz]

Hi,

On Thu, Jul 22, 2004 at 01:42:15PM +0200, Thibault North wrote:

Ok, that's the first log:
> <device descriptor of 0x03f0/0x0517 at 002:003>

That's not your scanner.

> <device descriptor of 0x04fc/0x0561 at 002:002>
> <trying to find out which USB chip is used>
>     checking for GT-6801 ...
>     this is not a GT-6801 (bDeviceProtocol = 0x0)
>     checking for GT-6816 ...
>     this is not a GT-6816 (bDeviceClass = 255, bInterfaceClass = 255)
>     checking for MA-1017 ...
>     this is not a MA-1017 (bDeviceClass = 255, bInterfaceClass = 255)
>     checking for MA-1015 ...
>     this is not a MA-1015 (bcdUSB = 0x110)
>     checking for MA-1509 ...
>     this is not a MA-1509 (bDeviceProtocol = 0x0)
>     checking for LM983[1,2,3] ...
>     this is not a LM983x (bDeviceSubClass = 0xff)
>     checking for GL646 ...
>     this is not a GL646 (bDeviceClass = 255, bInterfaceClass = 255)
>     checking for GL646_HP ...
>     this is not a GL646_HP (bDeviceProtocol = 0x0)
>     checking for GL660+GL646 ...
>     this is not a GL660+GL646 (bDeviceClass = 255, bInterfaceClass = 255)
>     checking for GL841 ...
>     this is not a GL841 (bcdUSB = 0x110)
>     checking for ICM532B ...
>   check 4, this is not a ICM532B (bDeviceProtocol = 0x0)
> <Couldn't determine the type of the USB chip>
> found USB scanner (vendor=0x04fc, product=0x0561) at libusb:002:002

That's also not your scanner. Maybe a webcam or similar device?

> <device descriptor of 0x0000/0x0000 at 002:001>
> <device descriptor of 0x0000/0x0000 at 001:001>

Your root hubs.

So your first log means that your scanner wasn't connected at the time
sane-find-scanner was run or at least the scanner didn't answer at all.

Second log:

> <device descriptor of 0x03f0/0x0517 at 002:003>

Not the scanner.

> <device descriptor of 0x04fc/0x0561 at 002:002>
> found USB scanner (vendor=0x04fc, product=0x0561) at libusb:002:002
 
Not the scanner.

> <device descriptor of 0x0000/0x0000 at 002:001>

Root hub.

> <device descriptor of 0x04a9/0x2212 at 001:002>

There it is.

> <trying to find out which USB chip is used>
[...]

>     checking for GL660+GL646 ...
>   Couldn't set configuration: could not set config 1: Operation not permitted
> <This USB chip looks like a GL660+GL646?>
> 
> found USB scanner (vendor=0x04a9, product=0x2212, chip=GL660+GL646?) at libusb:001:002

For some reason setting the configuration didn't work. Did you try
that as root? At least the USB device descriptor looks like a GL660
chip. But it couldn't be tested if sending commands works.

> <device descriptor of 0x0000/0x0000 at 001:001>

Hub.

Third log:

> <device descriptor of 0x04a9/0x2212 at 001:004>
[...]

> <trying to find out which USB chip is used>
>   checking for GL660+GL646 ...
> Couldn't set configuration: could not set config 1: Operation not permitted
> <This USB chip looks like a GL660+GL646?>
> 
> found USB scanner (vendor=0x04a9, product=0x2212, chip=GL660+GL646?) at libusb:001:004

Same as above. So at least it's consistent.

Bye,
  Henning