[sane-devel] Updated info for Canon LiDE 500F

[Daniel Ellis]

Hi Stef, thanks for getting back to me.

Outputs of "lsusb -v" and "sane-find-scanner" are attached.

Thanks,
Dan


On 28 August 2013 05:33, Stef <stef.dev at free.fr> wrote:

>  On 24/08/2013 10:45, Daniel Ellis wrote:
>
>  I wasn't certain the info on the unsupported Canon CanoScan LiDE 500F
> was correct:
>
> http://www.sane-project.org/unsupported/canon-canoscan-lide-500f.html
>
>  On this page it says the chipset is GL841.  I have given up on this
> scanner, so I decided to take it apart to check the chip, and it turns out
> the chip is a GL120.
>
> Picture of the chip: http://postimg.org/image/y53f9ekpv/
>
>  I would be grateful if someone could update the webpage, and hopefully
> this info may help someone else have some better luck with this scanner!
>
>  Regards,
> Daniel Ellis.
>
>
>
>     Hello,
>
>     what does 'lsusb -v' reports for your device ?
>
> Regards,
>     Stef
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130828/f3f27fc2/attachment.html>
-------------- next part --------------

Bus 002 Device 004: ID 04a9:221f Canon, Inc. CanoScan LiDE 500F
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass          255 Vendor Specific Class
  bDeviceSubClass       255 Vendor Specific Subclass
  bDeviceProtocol       255 Vendor Specific Protocol
  bMaxPacketSize0        64
  idVendor           0x04a9 Canon, Inc.
  idProduct          0x221f CanoScan LiDE 500F
  bcdDevice            3.03
  iManufacturer           1 Canon
  iProduct                2 CanoScan
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           39
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0001  1x 1 bytes
        bInterval               8
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass          255 Vendor Specific Class
  bDeviceSubClass       255 Vendor Specific Subclass
  bDeviceProtocol       255 Vendor Specific Protocol
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0002
  (Bus Powered)
  Remote Wakeup Enabled

-------------- next part --------------

  # sane-find-scanner will now attempt to detect your scanner. If the
  # result is different from what you expected, first make sure your
  # scanner is powered up and properly connected to your computer.

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

found USB scanner (vendor=0x04a9 [Canon], product=0x221f [CanoScan], chip=GL842) at libusb:002:004
  # 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.