Medion MD 6228
Tevion MD 6228
Medion MD 5345
Tevion MD 5345
Medion MD 6471
Primax Slim-Line 1200
USB
0x0461
0x0377
GL646
The following chips are used (MD 6228): M11B416256A (memory) L6219DS (motor driver) 610800009609 (1st line), 0252FG79A (2nd line) (unknown chip)
Looks like these are all the same scanners. The medion.de webpage has Windows XP drivers for 5345, 6228 and 6471 in one package.
Maybe the same as Primax Slim-Line 1200, at least it looks very similar. Also it has a Primax ID. The Windows driver contains a reference to this scanner.
sane-find-scanner thinks it's a GL646 chipset.
If this is the GL646 chip, maybe the Genesys backend can be used, when it's finished?
MD 6228 and MD 5345 T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0461 ProdID=0377 Rev= 0.00 S: Manufacturer=Primax S: Product=USB Scanner C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 48mA I: If#= 0 Alt= 0 #EPs= 3 Cls=10(unk. ) Sub=01 Prot=00 Driver=(none) E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl= 0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl= 0ms E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl= 8ms MD 6228 <device descriptor of 0x0461/0x0377 at 003:002 (Primax USB Scanner)> bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0461 idProduct 0x0377 bcdDevice 0.00 iManufacturer 2 (Primax) iProduct 3 (USB Scanner) iSerialNumber 0 () bNumConfigurations 1 <configuration 0> bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 224 (Self-poweredRemote Wakeup) MaxPower 48 mA <interface 0> <altsetting 0> bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 16 bInterfaceSubClass 1 bInterfaceProtocol 0 iInterface 0 () <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 64 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 <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 (bDeviceClass = 0, bInterfaceClass = 16) checking for MA-1017 ... this is not a MA-1017 (bDeviceClass = 0, bInterfaceClass = 16) 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 (bDeviceClass = 0, bInterfaceClass = 16) checking for GL646 ... <This USB chip looks like a GL646> found USB scanner (vendor=0x0461 [Primax], product=0x0377 [USB Scanner], chip=GL646) at libusb:003:002
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.
$Date$ $Author$