[sane-devel] Problem getting Epson V370 Photo working under OpenSuSE

Johannes Meixner jsmeix at suse.de
Thu Mar 10 10:46:26 UTC 2016


On Mar 10 08:17 Graham Freeman wrote (excerpt):
> I used YaST/scanner to configure the scanner.
> It presents two items in its list:
> epkowa     Epson (unknown model) at epkowa:usb:003:004
> EPSON Perfection V37/V370 USB scanner
> (vendor=0x04b8 [EPSON], product=0x014a [EPSON Perfecttion V37/V370])
> at libusb:003:004
> If I attempt to edit the second to configure it,
> I get a popup message
> "Possibly Problematic Driver The epkowa driver may cause
>  problems on 64-bit x86_64 architecture"

When you click [Continue] on that popup you get
a subsequent popup message that reads:

The third-party Image Scan driver software
from Epson/Avasys is required.
The Image Scan driver software is made and
provided by Epson (formerly Avasys)
(formerly Avasys http://avasys.jp/eng/linux_driver/)
where RPM packages for 32-bit (i386) and 64-bit (x86_64) architecture
can be downloaded (if you accept the Epson/Avasys license agreements).
The Image Scan driver contains proprietary binary-only software.
For some models it is only available for 32-bit (i386) architecture
which does not work when you have a 64-bit system installation.
Some scanners are also supported by another (free-software) driver.
When your scanner model requires a DFSG non-free (proprietary) module,
you have to download and install two packages from Epson/Avasys:
The 'iscan' package for the base software and an additional
model dependant 'iscan-plugin' package with the proprietary module.

That message is shown a bit unfortunate as an "Error" popup
because you cannot successfully continue the scanner setup here
which means there is some kind of "Error" at that point.

The text is a bit old (from May 08 2012) and perhaps somewhat
outdated but I cannot continuously verify if all the details
are still 100% correct.

But the most important thing seems to be still correct:

You can get the driver software from Epson via

In general regarding third-party drivers see
"Third-Party Scanner Drivers" at


Since a longer time I do no longer have time to actively
maintain and update the YaST scanner module.
Therefore (as long as nobody else cares about it)
it stays in its current form (frankly: it bitrots).
My last real adaption dated May 08 2012
(cf. "rpm -q --changelog yast2-scanner") because of

Kind Regards
Johannes Meixner
SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard,
Graham Norton - HRB 21284 (AG Nuernberg)

More information about the sane-devel mailing list