Canon CanoScan 5000f
Mercury 03 A235-0604 FFNOW-2 T431616A (Dynamic RAM) Data sheet: http://www.tmtech.com.tw/products/pdf/T431616A.pdf#search=%22t431616a%22 GL660USB 0230MFCY001-48 164-07-200660
Despite the failing test for GL646+GL660 this scanner may use these chips. Therefore it may be possible to support it by the genesys backend in future.
There is now a project for that scanner.
USB 2.0, 2400x4800 dpi. With transparency adapter.
T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1 P: Vendor=04a9 ProdID=2212 Rev= 3.04 S: Manufacturer=Canon S: Product=CanoScan C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 10mA I: If#= 0 Alt= 0 #EPs= 3 Cls=00(>ifc ) Sub=00 Prot=00 Driver=usbscanner E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=16ms <device descriptor of 0x04a9/0x2212 at 001:002 (Canon CanoScan)> bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 255 bDeviceSubClass 255 bDeviceProtocol 255 bMaxPacketSize0 64 idVendor 0x04A9 idProduct 0x2212 bcdDevice 3.03 iManufacturer 2 (Canon) iProduct 3 (CanoScan) iSerialNumber 1 (1) bNumConfigurations 1 <configuration 0> bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 192 (Self-powered) MaxPower 10 mA <interface 0> <altsetting 0> bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 0 bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 () <endpoint 0> bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 2 (bulk) wMaxPacketSize 512 bInterval 0 ms bRefresh 0 bSynchAddress 0 <endpoint 1> bLength 7 bDescriptorType 5 bEndpointAddress 0x02 (out 0x02) bmAttributes 2 (bulk) wMaxPacketSize 512 bInterval 0 ms bRefresh 0 bSynchAddress 0 <endpoint 2> bLength 7 bDescriptorType 5 bEndpointAddress 0x83 (in 0x03) bmAttributes 3 (interrupt) wMaxPacketSize 1 bInterval 8 ms bRefresh 0 bSynchAddress 0 found USB scanner (vendor=0x04a9 [Canon], product=0x2212 [CanoScan]) at libusb:001:002 From another user: <trying to find out which USB chip is used> checking for GT-6801 ... this is not a GT-6801 (bcdUSB = 0x200) checking for GT-6816 ... this is not a GT-6816 (bDeviceClass = 255, bInterfaceClass = 0) checking for MA-1017 ... this is not a MA-1017 (bDeviceClass = 255, bInterfaceClass = 0) checking for MA-1015 ... this is not a MA-1015 (bcdUSB = 0x200) checking for MA-1509 ... this is not a MA-1509 (bcdUSB = 0x200) checking for LM983[1,2,3] ... this is not a LM983x (bDeviceClass = 255, bInterfaceClass = 0) checking for GL646 ... this is not a GL646 (bDeviceClass = 255, bInterfaceClass = 0) checking for GL660+GL646 ... this is not a GL660+GL646 (bEndpointAddress = 0x81, bmAttributes = 0x2, wMaxPacketSize = 0x200, bInterval = 0x0) <Couldn't determine the type of the USB chip>
If anything is wrong or missing on this page please file a bug report or use the the form for adding an unsupported device.
If you own an unsupported scanner, please send as much information as possible. Especially the output of sane-find-scanner -v -v and/or cat /proc/scsi/scsi (for SCSI scanners) or cat /proc/bus/usb/devices (for USB scanners) can help. If you dare to open the scanner, have a look at the text that's printed on the chips. That may help to identify the chipset. If you know that the scanner is similar to another one (e.g. supported by the same Windows driver), please also mention this fact.
Are you a manufacturer or vendor of scanners and one of your scanners is not supported by SANE yet? In this case please have a look at our information for manufacturers.