Xerox WorkCentre M15i
Device reports itself just as a printer. As such it works perfectly well with the PCL6 driver of CUPS.
usbview output: WorkCentre M15 Series Manufacturer: Xerox Serial Number: 6249-04040654587 Speed: 12Mb/s (full) USB Version: 1.10 Device Class: 00(>ifc ) Device Subclass: 00 Device Protocol: 00 Maximum Default Endpoint Size: 8 Number of Configurations: 1 Vendor Id: 0924 Product Id: ffef Revision Number: 1.00 Config Number: 1 Number of Interfaces: 1 Attributes: c0 MaxPower Needed: 0mA Interface Number: 0 Name: usblp Alternate Number: 0 Class: 07(print) Sub Class: 1 Protocol: 2 Number of Endpoints: 2 Endpoint Address: 02 Direction: out Attribute: 2 Type: Bulk Max Packet Size: 64 Interval: 0ms Endpoint Address: 83 Direction: in Attribute: 2 Type: Bulk Max Packet Size: 64 Interval: 0ms sane-find-scanner -v -v, output: <device descriptor of 0x0924/0xffef at 002:002 (Xerox WorkCentre M15 Series)> bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0924 idProduct 0xFFEF bcdDevice 1.00 iManufacturer 1 (Xerox) iProduct 2 (WorkCentre M15 Series) iSerialNumber 3 (6249-04040654587) bNumConfigurations 1 <configuration 0> bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 192 (Self-powered) MaxPower 0 mA <interface 0> <altsetting 0> bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 7 bInterfaceSubClass 1 bInterfaceProtocol 2 iInterface 0 () <endpoint 0> bLength 7 bDescriptorType 5 bEndpointAddress 0x02 (out 0x02) bmAttributes 2 (bulk) wMaxPacketSize 64 bInterval 0 ms bRefresh 0 bSynchAddress 0 <endpoint 1> bLength 7 bDescriptorType 5 bEndpointAddress 0x83 (in 0x03) bmAttributes 2 (bulk) wMaxPacketSize 64 bInterval 0 ms bRefresh 0 bSynchAddress 0
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.