epson perfection 3590 cannot connect

English Hardware
#1

Ok,
I am a little frustrated, I hope someone can help. I have a perfectly good epson 3590 and I am tryin to get it running with on my 11.1 x64 installation. I have installed the iscan stuff (32bit) , i go through yast to configure the scanner, it seems to configure properly, but when I go into xsane, it does not see any scanner…

all i want is to be able to scan a couple of photo’s, nothing major, what do i have to do to get my scanner working?

thanks for your help!

#2

bump…

can anyone help…please

#3

This might be a permissions problem. What does

sane-find-scanner

report? (Try as user then root from console)

These HOWTOs may be useful:

YaST/Modules/Scanner - openSUSE

SDB:USB Scanner Configured with YaST Does Not Work - openSUSE

#4

hi, thanks

sane-find-scanner will now attempt to detect your scanner. If the

result is different from what you expected, first make sure your

scanner is powered up and properly connected to your computer.

No SCSI scanners found. If you expected something different, make sure that

you have loaded a kernel SCSI driver for your SCSI adapter.

found USB scanner (vendor=0x04b8 [EPSON], product=0x0122 [EPSON Scanner]) at libusb:002:004

Your USB scanner was (probably) detected. It may or may not be supported by

SANE. Try scanimage -L and read the backend’s manpage.

Not checking for parallel port scanners.

Most Scanners connected to the parallel port or other proprietary ports

can’t be detected by this program.

i will look at the links

#5

found USB scanner (vendor=0x04b8 [EPSON], product=0x0122 [EPSON Scanner]) at libusb:002:004

This looks hopeful.

Try this command (as user):

scanimage -L

If that works, you should be able to do a basic scan with something like

scanimage > /home/joe/test.pnm

The scanned image ‘test.pnm’ will be located in ‘/home/joe’ directory.

#6

doesn’t look good

No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).

#7

Did you run

scanimage -L

(Try as user first, then root).

#8

tried it both ways, same results

#9

Try typing following command

iscan

#10

i get a gui box up that says

could not send command to scanner. check the scanner’s status

thanks for hanging in …btw.

#11

No problem. Post output of

cat /etc/sane.d/epkowa.conf

There should be a line like this

usb 0x04b8 0x0122

pertaining to your scanner model.

#12 
# epkowa.conf -- sample configuration for the EPKOWA SANE backend
# Copyright (C) 2004  Olaf Meeuwissen
#
# See sane-epkowa(5), sane-scsi(5) and sane-usb(5) for details.

# SCSI scanners can be configured simply by listing the path to the
# device.  For example, if your system claims to have a /dev/scanner
# SCSI device, all you have to do is uncomment the following line:
#
#/dev/scanner
#
# In the interest of maintainability, most installations would have
# /dev/scanner sym-linked to the real SCSI scanner device node.
#
# An alternative way that works for many operating systems and is a
# little bit more generic, is to have the backend probe for your SCSI
# scanner with the following configuration command:
#
scsi EPSON

# On systems with libusb, the following line is sufficient to get the
# backend to recognise your USB scanners.  It presumes, however, that
# the scanner---more precisely, it's USB product ID---is known to the
# backend.
# For all USB scanners that are officially supported by this backend,
# this presumption is true.  A list of such scanners can be found in
# sane-epkowa(5).
#
usb

# For any USB scanner not known to the backend (yet), you may, at your
# own peril(!!), force the backend to recognise and use it via libusb.
# You can do so by the following configuration command:
# 
#   usb <USB vendor ID> <USB product ID>
#
# SEIKO EPSON's USB vendor ID is '0x04b8' (without quotes).  In order
# to find the USB product ID, use lsusb(1) or, on Linux systems, peek
# at the information in /proc/bus/usb/devices.
# A sample configuration for the Perfection 1650 (GT-8200), which has
# a product ID of 0x0110, would look as follows:
#
#usb 0x04b8 0x0110

# When not accessing your USB scanner via libusb, you may need to use
# one of the configuration commands below or commands that are almost
# the same.  These commands typically access the scanner via a kernel
# scanner module.
#
#usb /dev/usb/scanner0
#usb /dev/usbscanner0
#usb /dev/uscanner0
#
# Linux had a scanner module until version 2.6.2.  As of version 2.6.3
# libusb is your only option.  Linux' scanner module can be loaded via
# the modprobe(8) command like so:
#
#   modprobe scanner vendor=<USB vendor ID> product=<USB product ID>
#
# If the scanner module already knows the vendor and product IDs, you
# do not have to specify them.  If you want to have this done automa-
# tically every time you boot, you can add the above line, except for
# the modprobe command itself, to your /etc/modules file.

# Although not tested with this backend, parallel port scanners should
# be usable.  You can configure them as shown below, but I do not know
# much about the details.  Information is welcome.
#
#pio 0x278
#pio 0x378
#pio 0x3BC
#13

Hmmm…I see this:

For any USB scanner not known to the backend (yet), you may, at your

own peril(!!), force the backend to recognise and use it via libusb.

You can do so by the following configuration command:

usb <USB vendor ID> <USB product ID>

SEIKO EPSON’s USB vendor ID is ‘0x04b8’ (without quotes). In order

to find the USB product ID, use lsusb(1) or, on Linux systems, peek

at the information in /proc/bus/usb/devices.

A sample configuration for the Perfection 1650 (GT-8200), which has

a product ID of 0x0110, would look as follows:

#usb 0x04b8 0x0110

Try adding

usb 0x04b8 0x0122

You will need to edit this file as root. Some prefer to do this with a console editor like pico or nano (for user friendliness), otherwise you can do

kdesu kwrite /etc/sane.d/epkowa.conf (KDE)

gnomesu gedit (for Gnome)

Then plug scanner in again and test.

#14

BTW, did you go here to get scanner linux driver?

Linux Driver [AVASYS CORPORATION]

#15

ok, i added the line, unplugged and plugged back in the scanner. I then did a scanimage -L and got the same result as before

#16

also, i installed this

m -i iscan-plugin-gt-f520-1.0.0-1.c2.i386.rpm 
	package iscan-plugin-gt-f520-1.0.0-1.c2.i386 is already installed

did not help

#17

What iscan packages do you currently have installed? Mine for reference…

linux:/home/dean # rpm -qa |grep iscan
iscan-proprietary-drivers-2.10.0.1-10.1
iscan-2.10.0.1-21.1
iscan-firmware-2.8.0.1-48.1

All available from Non-OSS repo.

I’m hoping this isn’t a compatibility issue. (Its not listed in openSUSE HCL).

#18

TonyLaptop:/home/tonyg/Desktop # rpm -qa |grep iscan
iscan-2.10.0.1-59.8
iscan-firmware-2.8.0.1-1.4
iscan-plugin-gt-f520-1.0.0-1.c2
iscan-proprietary-drivers-2.10.0.1-1.3

#19

With the device plugged in, type

lsusb

Do you see any useful output?

For reference, I get this with my Epson CX5500:

Bus 001 Device 002: ID 04b8:083f Seiko Epson Corp. Stylus DX4450

The relevant udev file is /etc/udev/rules.d/55-iscan.rules

where your model and mine are listed:

SYSFS{idVendor}==“04b8”, SYSFS{idProduct}==“0122”, MODE=“0664”, GROUP=“lp”, ENV{libsane_matched}=“yes”

SYSFS{idVendor}==“04b8”, SYSFS{idProduct}==“083f”, MODE=“0664”, GROUP=“lp”, ENV{libsane_matched}=“yes”

I can’t imagine what the issue is. I’m nearly out of ideas…

#20

Now, I just found this scanner how to which mentions some potential problems with some Epson all-in-one devices. I’m not sure how relevant this is for openSUSE 11.1, but it states

Epson all-in-one devices show up at the USB as one USB device with different interfaces (use “sane-find-scanner -v -v”) like:

* "interface 0" is the scanner unit (USB scanner)
* "interface 1" is the printer unit (USB printer)
* an optional "interface 2" is a cardreader unit (USB mass storage)

As a result:

This leads to a conflict when SANE tries to access the scanner unit and the result is a “EBUSY” error (i.e. “Resource busy”) which let the scanner access fail. For example when running the command “scanimage -L” there are messages in /var/log/messages like:

usbfs: interface 1 claimed by usblp while ‘scanimage’ sets config #1
usbfs: interface 2 claimed by usb-storage while ‘scanimage’ sets config #1

I wonder if this could be the problem. Although this is supposed to have been fixed, the howto claims the ‘usblp’ and ‘usb-storage’ sometimes modules need unloading before the scanner will work. You could try this before invoking ‘scaimage -L’ command.