From 55959794d35f4374cddc1f8a76560215aa536197 Mon Sep 17 00:00:00 2001 From: Henning Geinitz Date: Sun, 18 Dec 2005 13:04:45 +0000 Subject: [PATCH] Added Lexmark X6170. --- unsupported/lexmark-x6170.html | 242 +++++++++++++++++++++++++++++++++ 1 file changed, 242 insertions(+) create mode 100644 unsupported/lexmark-x6170.html diff --git a/unsupported/lexmark-x6170.html b/unsupported/lexmark-x6170.html new file mode 100644 index 00000000..8da197a2 --- /dev/null +++ b/unsupported/lexmark-x6170.html @@ -0,0 +1,242 @@ + + + + + Scanner information + + + + + + + + + +

Scanners not supported by SANE

+

Manufacturer and model

+

+ Lexmark X6170 +

+

Bus type

+

+ USB +

+

Vendor ID

+

+ 0x043d +

+

Product ID

+

+ 0x0072 +

+

Chipset

+

+

+

Comments

+

+

+

Output of /proc/bus/usb/devices or sane-find-scanner -v -v or lsusb -vv

+ 
+<device descriptor of 0x043d/0x0072 at 002:002 (Lexmark Lexmark X6100 Series)> 
+bLength               18 
+bDescriptorType       1 
+bcdUSB                2.00 
+bDeviceClass          0 
+bDeviceSubClass       0 
+bDeviceProtocol       0 
+bMaxPacketSize0       64 
+idVendor              0x043D 
+idProduct             0x0072 
+bcdDevice             0.01 
+iManufacturer         1 (Lexmark) 
+iProduct              2 (Lexmark X6100 Series) 
+iSerialNumber         3 (15K005000498213) 
+bNumConfigurations    1 
+ <configuration 0> 
+ bLength              9 
+ bDescriptorType      2 
+ wTotalLength         94 
+ bNumInterfaces       3 
+ bConfigurationValue  1 
+ iConfiguration       0 () 
+ bmAttributes         192 (Self-powered) 
+ MaxPower             16 mA 
+  <interface 0> 
+   <altsetting 0> 
+   bLength            9 
+   bDescriptorType    4 
+   bInterfaceNumber   0 
+   bAlternateSetting  0 
+   bNumEndpoints      4 
+   bInterfaceClass    255 
+   bInterfaceSubClass 255 
+   bInterfaceProtocol 255 
+   iInterface         4 (Scan) 
+    <endpoint 0> 
+    bLength           7 
+    bDescriptorType   5 
+    bEndpointAddress  0x82 (in 0x02) 
+    bmAttributes      2 (bulk) 
+    wMaxPacketSize    64 
+    bInterval         0 ms 
+    bRefresh          0 
+    bSynchAddress     0 
+    <endpoint 1> 
+    bLength           7 
+    bDescriptorType   5 
+    bEndpointAddress  0x02 (out 0x02) 
+    bmAttributes      2 (bulk) 
+    wMaxPacketSize    64 
+    bInterval         0 ms 
+    bRefresh          0 
+    bSynchAddress     0 
+    <endpoint 2> 
+    bLength           7 
+    bDescriptorType   5 
+    bEndpointAddress  0x87 (in 0x07) 
+    bmAttributes      2 (bulk) 
+    wMaxPacketSize    64 
+    bInterval         0 ms 
+    bRefresh          0 
+    bSynchAddress     0 
+    <endpoint 3> 
+    bLength           7 
+    bDescriptorType   5 
+    bEndpointAddress  0x07 (out 0x07) 
+    bmAttributes      2 (bulk) 
+    wMaxPacketSize    64 
+    bInterval         0 ms 
+    bRefresh          0 
+    bSynchAddress     0 
+  <interface 1> 
+   <altsetting 0> 
+   bLength            9 
+   bDescriptorType    4 
+   bInterfaceNumber   1 
+   bAlternateSetting  0 
+   bNumEndpoints      2 
+   bInterfaceClass    7 
+   bInterfaceSubClass 1 
+   bInterfaceProtocol 2 
+   iInterface         5 (Print) 
+    <endpoint 0> 
+    bLength           7 
+    bDescriptorType   5 
+    bEndpointAddress  0x81 (in 0x01) 
+    bmAttributes      2 (bulk) 
+    wMaxPacketSize    64 
+    bInterval         0 ms 
+    bRefresh          0 
+    bSynchAddress     0 
+    <endpoint 1> 
+    bLength           7 
+    bDescriptorType   5 
+    bEndpointAddress  0x01 (out 0x01) 
+    bmAttributes      2 (bulk) 
+    wMaxPacketSize    64 
+    bInterval         0 ms 
+    bRefresh          0 
+    bSynchAddress     0 
+  <interface 2> 
+   <altsetting 0> 
+   bLength            9 
+   bDescriptorType    4 
+   bInterfaceNumber   2 
+   bAlternateSetting  0 
+   bNumEndpoints      1 
+   bInterfaceClass    3 
+   bInterfaceSubClass 0 
+   bInterfaceProtocol 0 
+   iInterface         0 () 
+    <endpoint 0> 
+    bLength           7 
+    bDescriptorType   5 
+    bEndpointAddress  0x83 (in 0x03) 
+    bmAttributes      3 (interrupt) 
+    wMaxPacketSize    8 
+    bInterval         100 ms 
+    bRefresh          0 
+    bSynchAddress     0 
+ 
+<trying to find out which USB chip is used> 
+    checking for GT-6801 ... 
+    this is not a GT-6801 (bDeviceClass = 0) 
+    checking for GT-6816 ... 
+    this is not a GT-6816 (bcdUSB = 0x200) 
+    checking for GT-8911 ... 
+    this is not a GT-8911 (check 2, bcdUSB = 0x200) 
+    checking for MA-1017 ... 
+    this is not a MA-1017 (bDeviceClass = 0, bInterfaceClass = 255) 
+    checking for MA-1015 ... 
+    this is not a MA-1015 (bDeviceClass = 0) 
+    checking for MA-1509 ... 
+    this is not a MA-1509 (bDeviceClass = 0) 
+    checking for LM983[1,2,3] ... 
+    this is not a LM983x (bcdUSB = 0x200) 
+    checking for GL646 ... 
+    this is not a GL646 (bDeviceClass = 0, bInterfaceClass = 255) 
+    checking for GL646_HP ... 
+    this is not a GL646_HP (bDeviceClass = 0, bInterfaceClass = 255) 
+    checking for GL660+GL646 ... 
+    this is not a GL660+GL646 (bDeviceClass = 0, bInterfaceClass = 255) 
+    checking for GL841 ... 
+    this is not a GL841 (bDeviceClass = 0, bInterfaceClass = 255) 
+    checking for ICM532B ... 
+    this is not a ICM532B (check 1, bDeviceClass = 0, bInterfaceClass = 255) 
+<Couldn't determine the type of the USB chip> 
+ 
+found USB scanner (vendor=0x043d [Lexmark], product=0x0072 [Lexmark X6100 Series]) at libusb:002:002 
+
+ +

Want to add or correct information?

+

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

+ +

Information for Manufacturers

+

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

+ +

Links

+ + +
+ +

+ SANE homepage
+ Contact +

+

+ $Date$ $Author$ +

+ + +