LinuxQuestions.org - [SOLVED] Epson L350 scanner won't start

- Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)

- - Epson L350 scanner won't start (https://www.linuxquestions.org/questions/linux-hardware-18/epson-l350-scanner-won%27t-start-4175626253/)

Epson L350 scanner won't start

After a new install, I can't get the scanner working on my Epson L350. 2 days ago, it was working.

Following the instructions, I first ran sudo apt-get install lsb
I installed the driver (this one has the date 26.02.2018 so I chose it):

Quote:

epson-printer-utility_1.0.2-1lsb3.2_amd64.deb

In /etc/sane.d/ I have 3 .conf files concerning Epson scanners:

epkowa.conf epson.conf and epson2.conf

lsusb shows this:

Quote:

pedro@pedro-school2:~$ lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 0c45:64e0 Microdia
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 014: ID 1f75:0621 Innostor Technology Corporation
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 0cf3:3004 Atheros Communications, Inc. AR3012 Bluetooth 4.0
Bus 004 Device 006: ID 04b8:08a1 Seiko Epson Corp.
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
pedro@pedro-school2:~$

This is the Epson L350: Bus 004 Device 006: ID 04b8:08a1 Seiko Epson Corp.

I set the values in all of the above .conf files to:

usb 04b8:08a1

If I run xsane, it takes a very long time, then I get: 'failed to open, device busy' or something. (See screenshot)

Any tips please?

This was working 2 days ago before a reinstall. I only changed this because the ssd drive I put in 6 months ago went bad, I lost my database. I'm sure if I put it back, the scanner would work.

The scanner driver package for the L350 comes from here
http://download.ebz.epson.net/dsc/se...search/?OSC=LX
*Search for the L350 model, and download iscan-bundle-1.0.4.x64.deb.tar.gz. Follow the instructions here...
https://exain.wordpress.com/tag/l210/

Make sure that the epkowa driver is uncommented in /etc/sane.d/dll.conf, although the installer should have taken care of this for you. The epson epson2 drivers should remain commented (you don't want conflicts).

Can you detect your scanner?

Code:

scanimage -L

Is the user a member of the 'lp' group?

Code:

groups

No, scanimage -L finds nothing, but sane-find-scanner finds it!!

I am the only user, and I can print! Wouldn't that be lp group??

This is the /etc/sane.d/dll.d/iscan.dpkg.new

Quote:

# iscan -- enables the SANE backend(s) required
# Any changes to this file will be lost when upgrading iscan.

epkowa

But I think epkowa is only for my Epson DS-510, a batch scanner, which I can use with imagescan.

I am a member of lpadmin, would that be enough? The thing is, before I changed my hd, all this worked without a hitch.

Quote:

pedro@pedro-school:~$ groups
pedro adm cdrom sudo dip plugdev lpadmin sambashare
pedro@pedro-school:~$

The L350 model is also supported by the epkowa driver as far as I understand. The CUPS usb backend relies on ACL permissions so no group required, but SANE udev rules assign ‘lp’ group for USB-connected scanners.

If ‘sane-find-scanner’ finds the scanner when run as user then not a permissions issue. It might be interesting to note what is reported by the kernel when it is first plugged in to a USB port

Code:

dmesg|tail

Note that some scanner hardware devices have problems with USB 3.0 host controllers. It doesn’t affect printer operation in the same way.

How do I add myself to group lp??

Just plugged the usb cable in:

Quote:

pedro@pedro-school2:~$ dmesg | tail
[ 83.809629] usb 7-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 83.809635] usb 7-2: Product: EPSON L350 Series
[ 83.809641] usb 7-2: Manufacturer: EPSON
[ 83.809645] usb 7-2: SerialNumber: 5138474B3235303187
[ 84.116430] usblp 7-2:1.1: usblp0: USB Bidirectional printer dev 3 if 1 alt 0 proto 2 vid 0x04B8 pid 0x08A1
[ 90.275194] usblp0: removed
[ 90.721973] usblp 7-2:1.1: usblp0: USB Bidirectional printer dev 3 if 1 alt 0 proto 2 vid 0x04B8 pid 0x08A1
[ 90.722660] usblp0: removed
[ 91.228148] audit: type=1400 audit(1522013280.545:32): apparmor="DENIED" operation="exec" profile="/usr/share/hplip/systray.py" name="/bin/ping" pid=2550 comm="hp-upgrade" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0
[ 120.910071] usblp 7-2:1.1: usblp0: USB Bidirectional printer dev 3 if 1 alt 0 proto 2 vid 0x04B8 pid 0x08A1
pedro@pedro-school2:~$

I just commented out epson.conf and epson2.conf, just left epkowa.conf usb uncommented on the line where it says usb.

xsane takes a very long time, then sends the message, well, see the screenshot.

Which argument is invalid??

Epson Printers have a waste ink counter. When it gets to 100%, they stop working, although there is nothing wrong. There is a Vietnamese guy who sells reset keys for $7.50. You can download his program for Linux wicreset.

On his page, http://www.2manuals.com/forum/index....y-under-linux/ was this useful info: add current user to lp

Quote:

sudo usermod -a -G lp $(id -n -u)

Quote:

pedro@pedro-school2:~$ sudo usermod -a -G lp $(id -n -u)
[sudo] password for pedro:
pedro@pedro-school2:~$ id pedro
uid=1000(pedro) gid=1000(pedro) groups=1000(pedro),4(adm),7(lp),24(cdrom),27(sudo),30(dip),46(plugdev),113(lpadmin),128(sambashare)
pedro@pedro-school2:~$ xsane

I ran wicreset. The first time it could not find the printer, told me to switch it off, then on again, then click continue. The second time, it worked. I ran a nozzle check and checked the waste ink counter.

After this, xsane starts quickly with no problem!!!

How or why is for the Gods to say, I'm just glad it works!!

As a side note, on my new laptop the same procedure does not work! I just get: no devices available.

Good to read of your progress with adding the user to the 'lp' group. With respect to your new laptop, again run demsg to see what is reported. Some scanners don't play well with USB 3.0 (XHCI) ports.