Creating support for the EPSON Perfection V370 scanner
Mageia does not support the popular EPSON Perfection V370 scanner - the reason is lacking upstream support in the Sane Project (http://www.sane-project.org/sane-mfgs.html#Z-EPSON).
This note documents how support for this scanner can be created by fetching and installing packages made available by EPSON at their download center.
Downloading packages from the EPSON Download Center
Go to the download center (http://download.ebz.epson.net/dsc/search/01/search/?OSC) and fetch the following package-files
(this is for a 64-bit machine, packages for 32-bit machines are also available). Store these files in a local repository, and dont forget doing urpmi.update for that repository.
Installing the packages
The iscan package fetched from the EPSON site replaces programs provided by the standard Mageia packages - therefore, you must first un-install the package sane-backends-iscan and, only then, install the new packages (to be done from a root-shell):
urpme sane-backends-iscan urpmi iscan urpmi iscan-data urpmi iscan-plugin-perfection-v370
Registering the V370 driver as a plugin for the iscan interpreter
Start by finding the usb "vendor-id" and "product-id" of your scanner:
- connect and power your scanner
- than do
In the list of devices you obtain, find the line that ends with something like "Seiko Epson Corp. The pair of colon-separated 4-digit hex numbers are the 2 usb ids <vendor-id>:<product-id>
Now, use the iscan-registry command to effectively register the new driver (again, as root)
iscan-registry interpreter usb --add 0x<vendor-id> 0x<product-id> /usr/lib64/iscan/libiscan-plugin-perfection-v370.so.0.0.0
(on a 32-bit machine, the directory will probably be /usr/lib/iscan - to be verified)
Finally, you need to reboot
Afterwords, you can verify that the scanner is correctly configured by doing
This procedure works both for Mageia-2 and Mageia-3 - however, it has only been tested on 64-bit machines. Once the installation is completed, the scanner works perfectly with both command-line iscan and the xsane GUI.
It is important to apply this installation procedure during the initial customisation process after system-install or, at least, before Linux has searched for a scanner device. Otherwise, the scanner will not correctly recognized - in that case, repeating the steps described above will not help. This approach being rather empirical, I do not know the reason why the only way to get things right again is a complete re-install.
Looking at bugzilla, the support of several EPSON scanners appears at present to be broken. It is not unlikely that this approach of replacing the standard Linux sane backend by the Epson iscan package plus a driver fetched from the Epson site could provide a workaround for some specific devices.