[Solved] Successful Image Scan Installation for EPSON USB Scanner

Tom739 · Post by **Tom739** » Mon Dec 11, 2017 4:08 pm

In order to operate the EPSON PERFECTION 3170 PHOTO scanner under Linux Mint 18.3 Mate I have read plenty of internet posts and blogs and explored various strategies until I finally succeeded. In order to help others, who face similar problems, I'd like to share my experience in this post.

I am running:
- Lenovo Thinkpad T560
- Linux Mint 18.3 Mate
- 4.10.0-42-generic #46~16.04.1-Ubuntu SMP
- EPSON PERFECTION 3170 PHOTO with USB interface

Unfortunately, this scanner is not supported by SANE. Moreover, it requires a proprietary driver and the iscan software from Epson. Both are provided for i386 (32bit) Linux systems on the Epson website:

http://download.ebz.epson.net/dsc/searc ... archModule

Note, I did not find a more recent release of iscan (Image Scan) than 2.10 that really supports my scanner.

RPM Download

I downloaded the following RPM files:

iscan-plugin-gt-9400-1.0.0-1.c2.i386.rpm (the driver)
iscan-2.10.0-1.c2.i386.rpm (the iscan software)
Note, Epson does not seem to provide any source of the driver. As a result, the entire installation has to be based on i386 (32bit) systems. The compilation of the iscan software for i386 systems is not straightforward, which is the reason, why I finally dropped the idea to compile iscan.
Open the RPM Packages

Since rpm packages are not really supported by Linux Mint and since the contents of these packages had to be adjusted for Linux Mint 18.3 Mate, it was necessary to open these packages. I have done this and all further operations after login as root.
Code: Select all
```
# alien -g --scripts iscan-plugin-gt-9400-1.0.0-1.c2.i386.rpm
# alien -g --scripts iscan-2.10.0-1.c2.i386.rpm
```
Each command creates 2 directories, one holding the original contents (*.org) and one for the new contents with no special suffix.
Modification of both Packages

First of all it is necessary to edit the file creating the udev rules in the iscan software package. This modifiction is needed in order to allow non-root users to access the scanner per USB interface.
Code: Select all
```
# vim iscan-2.10.0/usr/lib/iscan/make-udev-rules
```
In this file I made the following changes:

a) Replaced 'SYSFS' by 'ATTRS'
b) Replaced 'usb_device' by 'usb'
c) Added 'ENV{DEVTYPE}=="usb_device", ' at the beginning of the TEMPLATE statement

I have added the resulting rules file at the end of this post for reference.

Second, both packages have to be re-configured to allow the installation as Debian packages under Linux Mint. In order to be accepted I have made the following changes:
Code: Select all
```
# cd <package directory>
# vim debian/control
```
I appended ', amd64' to the line with the 'Architecture' statement. The resulting line became:

Architecture: i386, amd64
Afterwards I created the Debian packages by running
Code: Select all
```
# debian/rules binary
# cd ..
# rm -rf <all created package directories>
```
in each package directory. As a result, new packages were created in the parent directory:

iscan-plugin-gt-9400_1.0.0-2_amd64.deb
iscan_2.10.0-2_amd64.deb
Installation of Missing i386 Packages per Synaptic

I have installed the following additional i386 packages in order to satisfy the necessary dependencies of both iscan packages:
- libc6-i386
- libpangox-1.0-0-:i386
- libpangoxft-1.0-0-:i386
- libusb-0.1-4:i386
- libjpeg62:i386
- libatk-bridge2.0-0:i386
- libatk-adaptor:i386
- libgusb2:i386
Installation of the iscan Debian Packages

I have installed the new Debian packages running:
Code: Select all
```
# dpkg -i iscan-plugin-gt-9400_1.0.0-2_amd64.deb
# dpkg -i iscan_2.10.0-2_amd64.deb
```
I have ignored all notes about irrelevant packages. I assume they are all given because dpkg considered those new packages to be amd64 packages rather than i386 packages. And since most of the corresponding 64bit packages were already installed on my system, it found 2 packages, one for amd64 and another for i386 and complained about assumed unnecessary packages. If anyone has an idea how to create clean i386 Debian packages on amd64 system that avoid these notes, please let me know.

First Run

I have connected the scanner per USB cable and turned it on. Afterwards I have run

Code: Select all

# iscan

It took a busy CPU several seconds until the scanner awoke with some noise and the iscan window opened. I presume that in this time the software checked the USB bus for all supported scanners and created the udev rules file

/etc/udev/rules.d/60_iscan.rules

I have added the contents of this file below for reference:

Code: Select all

# This file is part of the "Image Scan! for Linux" binary package (or
# generated automatically as part of its installation).  Any changes
# will be overwritten with each upgrade of the package.

ACTION!="add", GOTO="iscan_rules_end"
SUBSYSTEM!="usb", GOTO="iscan_rules_end"

ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0101", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0103", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0104", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0106", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0107", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0109", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="010a", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="010b", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="010c", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="010e", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="010f", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0110", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0112", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0116", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0118", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0119", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="011b", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="011c", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="011d", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="011e", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0121", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0122", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0126", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0128", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0129", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="012a", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="012b", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="012c", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="012d", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="012e", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="012f", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0801", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0802", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0805", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0806", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0807", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="080d", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="080e", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="080f", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0810", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0811", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0813", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0814", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0815", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0817", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0818", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0819", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="081a", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="081c", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="081d", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="081f", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0820", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0827", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0828", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0829", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="082a", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="082b", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="082e", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="082f", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0830", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0833", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0835", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0836", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0837", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0838", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0839", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="083a", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="083c", MODE="0666"
ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="083f", MODE="0666"

LABEL="iscan_rules_end"

With this file it was also possible to run iscan as normal user, afterwards.

Debugging of the 60_iscan.rules

In this connection it may be interesting to learn how to debug the iscan rules file for correct syntax. In order to do so, I have restarted the udev daemon "systemd-udevd" and set its internal log level to "debug" per:
Code: Select all
```
# udevadm control -R --log-priority=6
```
Afterwards I monitored "/var/log/syslog" while un-plugging and plugging the USB cable to the scanner. The resulting notes in the syslog file helped a lot to correct the rules file.

I hope I did not forget any important detail. Feel free to add your comments on or improvements of this procedure.

Regards
Tom

bugeyedalien · Post by **bugeyedalien** » Tue Oct 20, 2020 7:44 pm

First I have to thank you a lot for this guide ! It helped me a lot to get the scanner going !
I went the long route first installing on 32bit in a VMware Player VM, however I had to convert the rpms to deb and change the rules template as described.
Then I made the plunge and tried it on my x64 Cinnamon 18.3 install ! I GOT IT TO WORK ! I have to say I use Vuescan for scanner software as Iscan was cumbersome and unstable for me. But BOY was I happy to hear the scanner wizz into action ! This has been an ongoing saga for me as long as I've had the scanner and as long as I've used Linux for most stuff. I had the scanner working in a XP VM earlier, but now I really WANTED it to work in *tux too !

I might add on this post if I remember some more clues from my own installing.

One thing I can write right away, I had to do was change the architecture from "i386, amd64" to "i386 amd64" so I had to remove the " , " I actually put "any" on the plugin and it seemed to compile. Not tried it yet. I had to install a number of the required packages too, some I already had. And when I was going to install the deb it wanted a 64bit version of libjpeg62. Anybody out there who try, remember to install the packages before compiling the deb. (I think).

A few tips to fellow people: to save in vim use ":" and type "w" :q to quit,
and "i" to insert while editing, esc key to get out of insert.

AND in the end ! Vuescan DID not work ! -> However ! <-
Then I tried the 32bit Vuescan..

AND IT WORKED !!
(people make sure you get it working before splashing out money for vuescan !)

Next on my travels I might go to 19.3 land !
Hope to succeed ! Would be nice to do that before april next year or whenever 18.3 times out !

Regards and greets
Dag !

absque fenestris · Post by **absque fenestris** » Tue Oct 20, 2020 10:33 pm

Tom739 wrote: ⤴Mon Dec 11, 2017 4:08 pm In order to operate the EPSON PERFECTION 3170 PHOTO scanner under Linux Mint 18.3 Mate I have read plenty of internet posts and blogs and explored various strategies until I finally succeeded. In order to help others, who face similar problems, I'd like to share my experience in this post.

I am running:
- Lenovo Thinkpad T560
- Linux Mint 18.3 Mate
- 4.10.0-42-generic #46~16.04.1-Ubuntu SMP
- EPSON PERFECTION 3170 PHOTO with USB interface

Unfortunately, this scanner is not supported by SANE. Moreover, it requires a proprietary driver and the iscan software from Epson. Both are provided for i386 (32bit) Linux systems on the Epson website:

http://download.ebz.epson.net/dsc/searc ... archModule

...

Hi Tom and Dag

Have you tried this version of Epson Imagescan?

imagescan-bundle-linuxmint-20-3.63.0.x64.deb

https://support.epson.net/linux/old_dri ... linuxmint/

bugeyedalien · Post by **bugeyedalien** » Wed Oct 21, 2020 1:56 am

Hmmm have not noticed that one ! But does it support "Perfection 3170" ??? I was sure that 3.x didnt support it !
Will take a closer look !

Greets Dag !

absque fenestris · Post by **absque fenestris** » Wed Oct 21, 2020 2:24 am

bugeyedalien wrote: ⤴Wed Oct 21, 2020 1:56 am Hmmm have not noticed that one ! But does it support "Perfection 3170" ??? I was sure that 3.x didnt support it !
Will take a closer look !

Greets Dag !

The Epson Perfection 3170 is now around 12 years old. Everything Epson offers directly for Linux is from 2011.

Maybe it works, maybe it doesn't. You just have to try it out yourself.
Anyway, I saved this .deb package for the archive - you never know when an Epson scanner comes across ...

bugeyedalien · Post by **bugeyedalien** » Wed Oct 21, 2020 3:05 am

Well I'll be dog gone, I've not tried your package yet ! But I got the other solution to work on 19.3 too !!! This ROCKS ! My scanner has been virtually unused for the past 5-6 years since I moved to Linux, and now I can use it again !

Code: Select all

sudo apt install libc6-i386 libpangox-1.0-0 libpangox-1.0-0:i386 libpangoxft-1.0-0:i386 libusb-0.1-4:i386 libjpeg62:i386 libatk-bridge2.0-0:i386 libatk-adaptor:i386 libgusb2:i386 libjpeg62 libsm6:i386 libgtk2.0-0

Thats a couple of packages extra to Toms.

(vuescan x32bit install dependency if you are on x64 libSM6 )
(sudo apt install libsm6:i386 already added above).

Vuescan:
https://www.hamrick.com/alternate-versions.html

(Remember to run iscan on first run.)

EDIT: Got it to work on 20.04 Kubuntu too !
Anyone want my packages, ping me ! There are no file attachment here.

On a new installed Mint 20 I needed some extrapackages:

Code: Select all

sudo apt install libc6-i386 libpangox-1.0-0 libpangox-1.0-0:i386 libpangoxft-1.0-0:i386 libusb-0.1-4:i386 libjpeg62:i386 libatk-bridge2.0-0:i386 libatk-adaptor:i386 libgusb2:i386 libjpeg62 libsm6:i386 libgtk2.0-0 libgtk2.0-0:i386 libusb-0.1-4 libieee1284-3:i386 libsane:i386 libsane

Remember to run iscan first after all the installed packages is done,
switch on the scanner (it can be connected just need to switch on) - > run iscan -> then upgrade to vuescan (demo first i suggest, but I'm very satisfied with it.)

Greets Dag !

Tom739 · Post by **Tom739** » Thu Dec 10, 2020 3:06 pm

Hi a.f. and Dag,

Sorry for my late reply. In fact, I was not very active, since I had started that thread in 2017 and had marked it "solved". I am happy, that even 3 years later it helped somebody to operate an Epson Perfection 3170 Photo scanner. Mine is also still operating, although it lost a few pixels

.

Have you tried this version of Epson Imagescan?
imagescan-bundle-linuxmint-20-3.63.0.x64.deb

Although, I do not recall the exact names of all the different Epson SW packages that I had tried in vain before I decided to adapt the old iscan_2.10.0-2 package for Mint Mate 18.3, I remember that I checked on many different SW packages. So, it is likely that the one mentioned above was already included ... and failed the test.

It is interesting to see, that the old iscan_2.10.0-2 even works with some additional tweaks under Mint 20. As a matter of fact, I am currently planning to upgrade my old Mint Mate 18.3 system to Mint 20. After having read a note about dropped 386 support in Mint 20, I actually had thought that this upgrade would terminate my scanners lifetime. However, now it seems that with some additional 386 packages it can still be used. Great

. Thanks for appending the necessary steps to this thread, Dag.

Greetings to Switzerland and Norway
Tom

Seeheim · Post by **Seeheim** » Sun Dec 27, 2020 2:42 pm

I just tried to get an old Epson Perfection 2480 Photo scanner working on Linux Mint 19.3 with the instructions given by Tom739 and the modifications by bugeyedalien - but sadly without luck.

After adding the necessary dependencies I seem to have managed to build the deb-files and could install them. But the iscan-software would not start. Although it created the iscan.rules-file in the background I get the following warning in the Terminal:

Code: Select all

Gtk-WARNING **: 18:41:11.334: Im Modulpfad »adwaita« konnte keine Themen-Engine gefunden werden

[Unable to locate theme engine in module_path: "adwaita"]
and subsequently a small pop-up window reading:
"Es konnte kein Befehl an den Scanner gesendet werden. Bitte überprüfen Sie den Scanner Status."
[Unable to send any command to the scanner. Please check the scanner status.]

The presence of the scanner seems to be recognized by the system:

Code: Select all

~$ lsusb
Bus 003 Device 003: ID 04b8:0121 Seiko Epson Corp. GT-F500/GT-F550 [Perfection 2480/2580 PHOTO]

Code: Select all

~$ sane-find-scanner
found USB scanner (vendor=0x04b8 [EPSON], product=0x0121 [EPSON Scanner]) at libusb:003:003

Only scanimage -L doesn't find it.
Thanks for giving me something to try but I seem to be out of luck. *sigh*
Yes, I know it is old, but it is still perfectly working on a Windows machine so I would love to see it working on a current Linux too...

Tom739 · Post by **Tom739** » Sun Dec 27, 2020 6:03 pm

@ Seehelm

I just tried to get an old Epson Perfection 2480 Photo scanner working on Linux Mint 19.3 with the instructions given by Tom739 and the modifications by bugeyedalien - but sadly without luck.

Are you using the same rpm drivers that I used and have you verified, that these are the right drivers for your scanner model?

Gtk-WARNING **: 18:41:11.334: Im Modulpfad »adwaita« konnte keine Themen-Engine gefunden werden

I think, this is not necessarily a killing point. E.g. when I run iscan under LM Mate 19.3, I get the following GTK warnings:

Code: Select all

(iscan:8494): Gtk-WARNING **: 22:47:13.304: Unable to locate theme engine in module_path: "pixmap",
(iscan:8494): Gtk-WARNING **: 22:47:13.304: Unable to locate theme engine in module_path: "murrine",

Still the main window is displayed.

When you start iscan in a terminal window, is it immediately terminated after those gtk warnings or is the process running without displaying a window?

Nevertheless, you could try to find and install a package "gtk2-engines-adwaita:i386" in order to satisfy the missing dependency. If there is no such package available, you may want to configure your environment for a different theme. E.g. I am using the theme "Mint-X-Red".

Good luck
Tom

Seeheim · Post by **Seeheim** » Mon Dec 28, 2020 4:43 am

Dear Tom,

thank you for your ideas.

For building the deb-files I used the drivers for my scanner model (iscan-plugin-gt-f500-1.0.0-1.c2.i386.rpm) from the Epson website. The version of the iscan software is the same.

Your tip regarding the missing module theme was right on: Changing a theme setting from Mint-Y to Mint-X sucessfully eliminated the warning in the Terminal. Nevertheless the gui of the iscan software will not show. In the system monitor I can see an iscan-process that is started. It sits there for a while and after a couple of seconds the aforementioned message is shown in a seperate window ("Es konnte kein Befehl an den Scanner gesendet werden. Bitte überprüfen Sie den Scanner-Status." / Unable to send any command to the scanner. Please check the scanner status.)

I sometimes get the feeling that I already tried to many ways to get this scanner going and somehow managed to misconfigure my system in such a way that it might be better to start from scratch...

Tom739 · Post by **Tom739** » Tue Dec 29, 2020 3:49 am

I sometimes get the feeling that I already tried to many ways to get this scanner going and somehow managed to misconfigure my system in such a way that it might be better to start from scratch...

Welcome to the club

Nevertheless the gui of the iscan software will not show. In the system monitor I can see an iscan-process that is started. It sits there for a while and after a couple of seconds the aforementioned message is shown in a seperate window ("Es konnte kein Befehl an den Scanner gesendet werden. Bitte überprüfen Sie den Scanner-Status." / Unable to send any command to the scanner. Please check the scanner status.)

Have you tried to debug your USB configuration per

Code: Select all

# udevadm control -R --log-priority=6

and by monitoring "/var/log/syslog" (see list item 7 in my initial post)? Did you find any errors reported in this file?

USB seems to be largely controlled by the kernel. Did you check iscan with a different kernel? Are you using a recommended kernel or a special one? In this connection the following two links may be helpful (I have to admit that I have never used usbmon myself, though):

Seeheim · Post by **Seeheim** » Tue Dec 29, 2020 2:12 pm

I'm running Kernel 5.4.0-58-lowlatency - nothing too special, I guess?

What I can see in the syslog when plugging in the scanner is:

Code: Select all

kernel: [ 1903.062336] usb 3-2: new high-speed USB device number 2 using xhci_hcd
kernel: [ 1903.194219] usb 3-2: New USB device found, idVendor=04b8, idProduct=0121, bcdDevice= 1.10
kernel: [ 1903.194221] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
kernel: [ 1903.194222] usb 3-2: Product: EPSON Scanner
kernel: [ 1903.194223] usb 3-2: Manufacturer: EPSON
upowerd[1698]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:07.1/0000:0a:00.3/usb3/3-2

The last line looks suspicious, but until now I did not find any useful hint what that really means and what could be the cause for that output.

Debugging USB sounds like fun. Or maybe not.

I managed to collect some debug data but simply have no idea what to do with it. This is way over my head:

Code: Select all

ffff9c0e1111ec00 1699798691 S Co:3:011:0 s 00 09 0001 0000 0000 0
ffff9c0e1111ec00 1699798721 C Co:3:011:0 0 0
ffff9c0e1111ec00 1699831055 S Bo:3:011:2 -115 6 = 12000000 3300
ffff9c0e1111ec00 1729831887 C Bo:3:011:2 -2 0
ffff9c0df0c70f00 1729831927 S Co:3:011:0 s 02 01 0000 0002 0000 0
ffff9c0df0c70f00 1729831955 C Co:3:011:0 0 0
ffff9c0df0c70f00 1729832125 S Co:3:011:0 s 02 01 0000 0081 0000 0
ffff9c0df0c70f00 1729832160 C Co:3:011:0 0 0
ffff9c0df0c70f00 1729832246 S Co:3:011:0 s 02 01 0000 0002 0000 0
ffff9c0df0c70f00 1729832278 C Co:3:011:0 0 0
ffff9c0df0c715c0 1729859808 S Bo:3:011:2 -115 6 = 12000000 2400
ffff9c0df0c715c0 1759860288 C Bo:3:011:2 -2 0
ffff9c0df0c715c0 1759860329 S Co:3:011:0 s 02 01 0000 0002 0000 0
ffff9c0df0c715c0 1759860356 C Co:3:011:0 0 0
ffff9c0e112a4480 1762376695 S Bo:3:011:2 -115 2 = 1b40
ffff9c0e112a4480 1792377136 C Bo:3:011:2 -2 0
ffff9c0e112a4480 1792377169 S Co:3:011:0 s 02 01 0000 0002 0000 0
ffff9c0e112a4480 1792377188 C Co:3:011:0 0 0
ffff9c0e112a4480 1792377286 S Bo:3:011:2 -115 2 = 1b66
ffff9c0e112a4480 1822377707 C Bo:3:011:2 -2 0
ffff9c0e112a4480 1822377747 S Co:3:011:0 s 02 01 0000 0002 0000 0
ffff9c0e112a4480 1822377771 C Co:3:011:0 0 0
ffff9c0ebd366cc0 1830446869 C Ii:3:001:1 0:2048 1 = 04
ffff9c0ebd366cc0 1830446882 S Ii:3:001:1 -115:2048 4 <
ffff9c0e208c5e00 1830446893 S Ci:3:001:0 s a3 00 0000 0002 0004 4 <
ffff9c0e208c5e00 1830446902 C Ci:3:001:0 0 4 = 00010100
ffff9c0e208c5e00 1830446907 S Co:3:001:0 s 23 01 0010 0002 0000 0
ffff9c0e208c5e00 1830446912 C Co:3:001:0 0 0
ffff9c0ebd366cc0 1830449643 C Ii:3:001:1 0:2048 1 = 04

The scanner was plugged in on bus 3, device 11 (3:011). At one point I unplugged the USB cable and reconnected it shortly after. It was not found again after that...

Tom739 · Post by **Tom739** » Tue Dec 29, 2020 6:31 pm

I do not find a fundamental difference comparing your syslog messages with mine (see below).

Code: Select all

Dec 29 23:11:07 Desktop2 kernel: [ 2329.103691] usb 2-1.5: new high-speed USB device number 5 using ehci-pci
Dec 29 23:11:07 Desktop2 kernel: [ 2329.214562] usb 2-1.5: New USB device found, idVendor=04b8, idProduct=0116
Dec 29 23:11:07 Desktop2 kernel: [ 2329.214565] usb 2-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Dec 29 23:11:07 Desktop2 kernel: [ 2329.214567] usb 2-1.5: Product: EPSON Scanner
Dec 29 23:11:07 Desktop2 kernel: [ 2329.214569] usb 2-1.5: Manufacturer: EPSON
Dec 29 23:11:07 Desktop2 mtp-probe: checking bus 2, device 5: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5"
Dec 29 23:11:07 Desktop2 mtp-probe: bus: 2, device: 5 was not an MTP device
Dec 29 23:11:07 Desktop2 upowerd[2077]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5

Since iscan is starting up on my system, I don't think the last line is related to your problem.

I'm running Kernel 5.4.0-58-lowlatency - nothing too special, I guess?

I am running 4.15.0-128-generic and have never tried a low latency kernel. However, I have tried 5.4.0-58-generic on my laptop, because I have experienced a 6s boot delay with 4.15.0-128-generic that I did not have with older kernels. I have learned that 4.15.0-128 became subject to quite a number of changes compared to previous kernels. The same applies to 5.4.0-58-generic.

So, you may want to check with an older generic kernel (pre 5.4.0-58 or pre 4.15.0-128) just to take no chances. Having an additional older fallback kernel installed on a system is not a bad idea, anyway.

A final thought, have you installed the required i386 usb library packages on your system? E.g. I have installed

Code: Select all

libgusb2:i386
libusb-0.1-4:i386
libusb-1.0-0:i386

Good luck and a Happy New Year
Tom

Seeheim · Post by **Seeheim** » Thu Dec 31, 2020 8:04 am

Indeed I was missing libgusb2:i386. But installing that and reassembling the driver files did not change the situation unfortunately.

I have a relatively new system based on a Ryzen 2600x CPU with B450 chipset and had some trouble to get a reliably working computer with kernels before 4.18. That's why I am not really keen on going back to 4.15.
Once Mint 20.1 is released I will probably start from scratch anyway.

Thanks for your help and may you have a good time in 2021!

Tom739 · Post by **Tom739** » Thu Jan 07, 2021 5:45 pm

@Seeheim

Just an idea. Have you seen the recent post of xenopeek about printers and scanners (https://linuxmint-user-guide.readthedoc ... nters.html)?
Maybe, the problem of your scanner is also related to the ippusbxd package?

Regards
Tom

Seeheim · Post by **Seeheim** » Sun Jan 10, 2021 6:42 am

Hi Tom,

no, I had not seen this topic before and maybe it will proove useful in the future.
I am still on Mint 19.3, so ippusbxd is probably not to blame, as it is my understanding that it was first introduced with Mint 20.
But I will soon transition to Mint 20.1 and see what will be my options there.

Thanks!
Seeheim

frug · Post by **frug** » Mon Jan 18, 2021 12:16 am

Ed Hamrick of VueScan informs me that the Epson V600 requires the ISCAN plugins; that espsonscan plugins will not work.
I have removed the epsonscan plugins and installed

the Iscan plugins, but my Mint Linux still will not recognize the V600. Should I re-install Linux Mint 2.x?

Tom739 · Post by **Tom739** » Mon Jan 18, 2021 2:28 pm

Epson V600 with VueScan-worked under LM 19

I am sorry, this thread is dedicated to the Epson Perfection 3170 Photo. Maybe, I should have added this to its title. This thread does not deal with other Epson scanners. However, there seem to be other threads addressing V600 topics in this forum. Please have a look.

Besides, I do not see any reason, why it should be necessary to re-install a Linux OS only because some scanner software is not working. Linux is not Windows

.

Regards
Tom

Linux Mint Forums