Lexmark X1240
USB
0x043d
0x007d
Comment from a user: "The 1.0.18 lexmark driver can get it to scan, but the resulting image is colorful, stripy +static. Example.
<device descriptor of 0x043d/0x007d at 002:003>
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x043D
idProduct 0x007D
bcdDevice 1.00
iManufacturer 1 ((null))
iProduct 2 ((null))
iSerialNumber 7 ((null))
bNumConfigurations 1
<configuration 0>
bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 6 ((null))
bmAttributes 224 (Self-poweredRemote Wakeup)
MaxPower 0 mA
<interface 0>
<altsetting 0>
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255
bInterfaceSubClass 0
bInterfaceProtocol 255
iInterface 9 ((null))
<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 0x02 (out 0x02)
bmAttributes 2 (bulk)
wMaxPacketSize 8
bInterval 0 ms
bRefresh 0
bSynchAddress 0
<endpoint 2>
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 (in 0x03)
bmAttributes 3 (interrupt)
wMaxPacketSize 1
bInterval 250 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 (bNumEndpoints = 3)
checking for GT-8911 ...
this is not a GT-8911 (check 5, bNumEndpoints = 3)
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 (bEndpointAddress = 0x81, bmAttributes = 0x2, wMaxPacketSize = 0x40, bInterval = 0x0)
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)
checking for PV8630/LM9830 ...
this is not a PV8630/LM9830 (bcdUSB = 0x110)
checking for M011 ...
this is not a M011 (bDeviceClass = 0)
checking for RTS8822L-01H ...
this is not a RTS8822L-01H (bEndpointAddress = 0x81, bmAttributes = 0x2, wMaxPacketSize = 0x40, bInterval = 0x0)
checking for rts8858c ...
Unexpected result from register reading (0x1/0x0)
checking for SQ113 ...
this is not a SQ113 (bcdUSB = 0x110)
<Couldn't determine the type of the USB chip (result from sane-backends 1.0.18)>
found USB scanner (vendor=0x043d, product=0x007d) at libusb:002:003
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.