Still problems with Epson Perfection 3490 Photo

I followed the instructions I found here (http:
//ubuntuforums.org/showthread.php?t=108256), which gave
a little bit more information about setting up udev.

I got some better activity and feedback, from this command :

SANE_DEBUG_SNAPSCAN=255 scanimage -L

However, it hangs at sane_snapscan_get_devices, with the
following
output from the process :

[snapscan] atomic_usb_cmd(0,0xbfea70ce,6,0x0,0x0 (0))
[snapscan] usb_cmd(0,0xbfea70ce,6,0x0,0x0 (0))
[snapscan] usb_cmd: cmdlen=6, datalen=0
[snapscan] usb_write: writing:  0x00 0x00 0x00 0x00 0x00
0x00
[snapscan] Written 6 bytes
[snapscan] usb_read: reading:  0xfb 0x00 0x00 0x00 0x00 0x00
0x00 0x00
[snapscan] Read 8 bytes
[snapscan] 2nd read 4 write 2
[snapscan] snapscani_init_device_structure()
[snapscan] sane_snapscan_get_devices (0xbfea8298, 0)

and after some time the process starts to take up 100% CPU.

What I want to know is if the snapscan backend on its own is
enough to
drive the scanner, or do I always need the iscan shared
libraries from
the Avasys website, and if yes, what is the best place to
install them ?

Thanks and regards,

Jurgen Defurne

-- 
sane-devel mailing list: sane-devellists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/sane-d
evel
Unsubscribe: Send mail with subject "unsubscribe
your_password"
             to sane-devel-requestlists.alioth.debian.org

jurgen.defurnepandora.be (Jurgen Defurne) writes:

> I followed the instructions I found here (http:
//ubuntuforums.org/showthread.php?t=108256), which gave
a little bit more information about setting up udev.
>
> I got some better activity and feedback, from this
command :
>
> SANE_DEBUG_SNAPSCAN=255 scanimage -L
>
> However, it hangs at sane_snapscan_get_devices, with
the following
> output from the process :
>
> [snapscan] atomic_usb_cmd(0,0xbfea70ce,6,0x0,0x0 (0))
> [snapscan] usb_cmd(0,0xbfea70ce,6,0x0,0x0 (0))
> [snapscan] usb_cmd: cmdlen=6, datalen=0
> [snapscan] usb_write: writing:  0x00 0x00 0x00 0x00
0x00 0x00
> [snapscan] Written 6 bytes
> [snapscan] usb_read: reading:  0xfb 0x00 0x00 0x00 0x00
0x00 0x00 0x00
> [snapscan] Read 8 bytes
> [snapscan] 2nd read 4 write 2
> [snapscan] snapscani_init_device_structure()
> [snapscan] sane_snapscan_get_devices (0xbfea8298, 0)
>
> and after some time the process starts to take up 100%
CPU.
>
> What I want to know is if the snapscan backend on its
own is enough to
> drive the scanner, or do I always need the iscan shared
libraries from
> the Avasys website, and if yes, what is the best place
to install them ?

You need a firmware file (esfw52.bin).

As for the iscan shared libraries (I assume you're talking
about
iscan-plugin-gt-f520-1.0.0-1.c2.i386.rpm) are only used by
the epkowa
backend.  The snapscan backend does not use them.  The
epkowa backend
is available in the iscan package/source.

Hope this helps,
-- 
Olaf Meeuwissen                          EPSON AVASYS
Corporation, SE1
FSF Associate Member #1962           sign up at http://member.fsf.org/
GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97  976A 16C7 F27D
6BE3 7D90
Penguin's lib!       -- I hack, therefore I am --           
   LPIC-2

-- 
sane-devel mailing list: sane-devellists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/sane-d
evel
Unsubscribe: Send mail with subject "unsubscribe
your_password"
             to sane-devel-requestlists.alioth.debian.org

On Thu, Nov 16, 2006 at 08:19:19AM +0900, Olaf Meeuwissen
wrote:
> jurgen.defurnepandora.be (Jurgen Defurne) writes:
> 
> > I followed the instructions I found here (http:
//ubuntuforums.org/showthread.php?t=108256), which gave
a little bit more information about setting up udev.
> >
> > I got some better activity and feedback, from this
command :
> >
> > SANE_DEBUG_SNAPSCAN=255 scanimage -L
> >
> > However, it hangs at sane_snapscan_get_devices,
with the following
> > output from the process :
> >
> > [snapscan] atomic_usb_cmd(0,0xbfea70ce,6,0x0,0x0
(0))
> > [snapscan] usb_cmd(0,0xbfea70ce,6,0x0,0x0 (0))
> > [snapscan] usb_cmd: cmdlen=6, datalen=0
> > [snapscan] usb_write: writing:  0x00 0x00 0x00
0x00 0x00 0x00
> > [snapscan] Written 6 bytes
> > [snapscan] usb_read: reading:  0xfb 0x00 0x00 0x00
0x00 0x00 0x00 0x00
> > [snapscan] Read 8 bytes
> > [snapscan] 2nd read 4 write 2
> > [snapscan] snapscani_init_device_structure()
> > [snapscan] sane_snapscan_get_devices (0xbfea8298,
0)
> >
> > and after some time the process starts to take up
100% CPU.
> >
> > What I want to know is if the snapscan backend on
its own is enough to
> > drive the scanner, or do I always need the iscan
shared libraries from
> > the Avasys website, and if yes, what is the best
place to install them ?
> 
> You need a firmware file (esfw52.bin).
> 
> As for the iscan shared libraries (I assume you're
talking about
> iscan-plugin-gt-f520-1.0.0-1.c2.i386.rpm) are only used
by the epkowa
> backend.  The snapscan backend does not use them.  The
epkowa backend
> is available in the iscan package/source.
> 
> Hope this helps,
> -- 
> Olaf Meeuwissen                          EPSON AVASYS
Corporation, SE1
> FSF Associate Member #1962           sign up at http://member.fsf.org/
> GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97  976A 16C7
F27D 6BE3 7D90
> Penguin's lib!       -- I hack, therefore I am --      
        LPIC-2

I already got the firmware, I added it to the snapscan.conf
file. I
suppose this is what makes the scanner tick, ie. the
software which
controls the device on-board.

When using this command :

 SANE_DEBUG_SNAPSCAN=255 SANE_DEBUG_SANEI_USB=255 scanimage
-L

I see that the system does not hang on the scanner
detection, but on
the USB detection.

Here are the last 20 lines of the output.

[sanei_debug] Setting debug level of sanei_usb to 255.
[sanei_usb] sanei_usb_init: Looking for kernel scanner
devices
[sanei_usb] sanei_usb_init: can't stat /dev/usb/: No such
file or
directory
[sanei_usb] sanei_usb_init: Looking for libusb devices
usb_os_init: Found USB VFS at /dev/bus/usb
usb_set_debug: Setting debugging level to 255 (on)
[sanei_usb] sanei_usb_init: found libusb device
(0x04b8/0x0122)
interface 0  at libusb:004:002
[sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like
a root hub
[sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like
a root hub
[sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like
a root hub
[sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like
a root hub
[sanei_usb] sanei_usb_init: found 1 devices
[sanei_usb] sanei_usb_find_devices: vendor=0x03f0,
product=0x0000
[sanei_usb] sanei_usb_find_devices: vendor=0x03f0,
product=0x2205
[sanei_usb] sanei_usb_find_devices: vendor=0x03f0,
product=0x2005
[sanei_usb] sanei_usb_find_devices: vendor=0x03f0,
product=0x2005
[sanei_usb] sanei_usb_find_devices: vendor=0x03f0,
product=0x0705
[sanei_usb] sanei_usb_find_devices: vendor=0x03f0,
product=0x0805

I have tried using gdb to attach to the process, which
works, but
since there is no symbolic information, I am unable to get
any output
which may help.

I suppose, since it hangs at the last line, that I have a
problem with
a product from vendor 0x3f0, product 0x0805. Is there
somewhere an
index where I can lookup these codes ?

Regards,

Jurgen

-- 
sane-devel mailing list: sane-devellists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/sane-d
evel
Unsubscribe: Send mail with subject "unsubscribe
your_password"
             to sane-devel-requestlists.alioth.debian.org

On Sun, 2006-11-19 at 07:25 +0100, Jurgen Defurne wrote:
> On Thu, Nov 16, 2006 at 08:19:19AM +0900, Olaf
Meeuwissen wrote:
> > jurgen.defurnepandora.be (Jurgen Defurne)
writes:
> > 
> > > I followed the instructions I found here (http:
//ubuntuforums.org/showthread.php?t=108256), which gave
a little bit more information about setting up udev.
> > >
> > > I got some better activity and feedback, from
this command :
> > >
> > > SANE_DEBUG_SNAPSCAN=255 scanimage -L
> > >
> > > However, it hangs at
sane_snapscan_get_devices, with the following
> > > output from the process :
> > >
> > > [snapscan]
atomic_usb_cmd(0,0xbfea70ce,6,0x0,0x0 (0))
> > > [snapscan] usb_cmd(0,0xbfea70ce,6,0x0,0x0
(0))
> > > [snapscan] usb_cmd: cmdlen=6, datalen=0
> > > [snapscan] usb_write: writing:  0x00 0x00
0x00 0x00 0x00 0x00
> > > [snapscan] Written 6 bytes
> > > [snapscan] usb_read: reading:  0xfb 0x00 0x00
0x00 0x00 0x00 0x00 0x00
> > > [snapscan] Read 8 bytes
> > > [snapscan] 2nd read 4 write 2
> > > [snapscan] snapscani_init_device_structure()
> > > [snapscan] sane_snapscan_get_devices
(0xbfea8298, 0)
> > >
> > > and after some time the process starts to
take up 100% CPU.
> > >
> > > What I want to know is if the snapscan
backend on its own is enough to
> > > drive the scanner, or do I always need the
iscan shared libraries from
> > > the Avasys website, and if yes, what is the
best place to install them ?
> > 
> > You need a firmware file (esfw52.bin).
> > 
> > As for the iscan shared libraries (I assume you're
talking about
> > iscan-plugin-gt-f520-1.0.0-1.c2.i386.rpm) are only
used by the epkowa
> > backend.  The snapscan backend does not use them. 
The epkowa backend
> > is available in the iscan package/source.
> > 
> > Hope this helps,
> > -- 
> > Olaf Meeuwissen                          EPSON
AVASYS Corporation, SE1
> > FSF Associate Member #1962           sign up at http://member.fsf.org/
> > GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97  976A
16C7 F27D 6BE3 7D90
> > Penguin's lib!       -- I hack, therefore I am -- 
             LPIC-2
> 
> I already got the firmware, I added it to the
snapscan.conf file. I
> suppose this is what makes the scanner tick, ie. the
software which
> controls the device on-board.
> 
> When using this command :
> 
>  SANE_DEBUG_SNAPSCAN=255 SANE_DEBUG_SANEI_USB=255
scanimage -L
> 
> I see that the system does not hang on the scanner
detection, but on
> the USB detection.
> 
> Here are the last 20 lines of the output.
> 
> [sanei_debug] Setting debug level of sanei_usb to 255.
> [sanei_usb] sanei_usb_init: Looking for kernel scanner
devices
> [sanei_usb] sanei_usb_init: can't stat /dev/usb/: No
such file or
> directory
> [sanei_usb] sanei_usb_init: Looking for libusb devices
> usb_os_init: Found USB VFS at /dev/bus/usb
> usb_set_debug: Setting debugging level to 255 (on)
> [sanei_usb] sanei_usb_init: found libusb device
(0x04b8/0x0122)
> interface 0  at libusb:004:002
> [sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks
like a root hub
> [sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks
like a root hub
> [sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks
like a root hub
> [sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks
like a root hub
> [sanei_usb] sanei_usb_init: found 1 devices
> [sanei_usb] sanei_usb_find_devices: vendor=0x03f0,
product=0x0000
> [sanei_usb] sanei_usb_find_devices: vendor=0x03f0,
product=0x2205
> [sanei_usb] sanei_usb_find_devices: vendor=0x03f0,
product=0x2005
> [sanei_usb] sanei_usb_find_devices: vendor=0x03f0,
product=0x2005
> [sanei_usb] sanei_usb_find_devices: vendor=0x03f0,
product=0x0705
> [sanei_usb] sanei_usb_find_devices: vendor=0x03f0,
product=0x0805
> 
> I have tried using gdb to attach to the process, which
works, but
> since there is no symbolic information, I am unable to
get any output
> which may help.
> 
> I suppose, since it hangs at the last line, that I have
a problem with
> a product from vendor 0x3f0, product 0x0805. Is there
somewhere an
> index where I can lookup these codes ?
> 
> Regards,
> 
> Jurgen
> 
One way is using the Sane search page

http://www.sane-
project.org/cgi-bin/driver.pl?manu=&model=&bus=any&a
mp;v=03f0&p=0805

Last line from the   hp_rts88xx   backend.

In /etc/sane.d/dll.conf you can disable the not used
backends by placing
a # before each backendname, maybe that will help.
-- 
--------
m.vr.gr.
Gerard Klaver


-- 
sane-devel mailing list: sane-devellists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/sane-d
evel
Unsubscribe: Send mail with subject "unsubscribe
your_password"
             to sane-devel-requestlists.alioth.debian.org

Hello, I'm new on Linux and in this list. My intention is to
help
sharing my experience making this target scanner to work on
Linux from
OpenSuSE 10.1 on x86-64 arch. Just in case, I wrote a small
"how to" on:
ht
tp://en.opensuse.org/Epson_Perfection_3490_Photo


Considering OpenSuSE already with Sane, the major steps are:

1. Check if usb hoplug recognized your usb scanner: Use
command line
"lsusb" to check.

2. Check if sane let snapscan be available: Uncomment
snapscan
in /etc/sane.d/dll.conf

3. Check if snapscan recognize the usb scanner: On OpenSuSE
use YaST
(Hardware/Scanner). Do not know how to do it on Ubuntu.

4. Check if snapscan.conf (on /etc/sane.d) pointing
correctly to the
target scanner firmware esfw52.bin.
 
obs: You can get the firmware esfw52.bin installing
iscan-firmware 1.18
rpm package (in this 1.18 version there are packages for
i386, i586 and
x86-64 arch).

That was all for me. scanimage command line works and so
xsane.

Regards
Marcio



-- 
sane-devel mailing list: sane-devellists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/sane-d
evel
Unsubscribe: Send mail with subject "unsubscribe
your_password"
             to sane-devel-requestlists.alioth.debian.org

On Sun, Nov 19, 2006 at 11:18:37AM +0100, Gerard Klaver
wrote:
> On Sun, 2006-11-19 at 07:25 +0100, Jurgen Defurne
wrote:
> > On Thu, Nov 16, 2006 at 08:19:19AM +0900, Olaf
Meeuwissen wrote:
> > > jurgen.defurnepandora.be (Jurgen Defurne)
writes:
> > > 
> > > > I followed the instructions I found here
(http:
//ubuntuforums.org/showthread.php?t=108256), which gave
a little bit more information about setting up udev.
> > > >
> > > > I got some better activity and feedback,
from this command :
> > > >
> > > > SANE_DEBUG_SNAPSCAN=255 scanimage -L
> > > >
> > > > However, it hangs at
sane_snapscan_get_devices, with the following
> > > > output from the process :
> > > >
> > > > [snapscan]
atomic_usb_cmd(0,0xbfea70ce,6,0x0,0x0 (0))
> > > > [snapscan]
usb_cmd(0,0xbfea70ce,6,0x0,0x0 (0))
> > > > [snapscan] usb_cmd: cmdlen=6, datalen=0
> > > > [snapscan] usb_write: writing:  0x00
0x00 0x00 0x00 0x00 0x00
> > > > [snapscan] Written 6 bytes
> > > > [snapscan] usb_read: reading:  0xfb 0x00
0x00 0x00 0x00 0x00 0x00 0x00
> > > > [snapscan] Read 8 bytes
> > > > [snapscan] 2nd read 4 write 2
> > > > [snapscan]
snapscani_init_device_structure()
> > > > [snapscan] sane_snapscan_get_devices
(0xbfea8298, 0)
> > > >
> > > > and after some time the process starts
to take up 100% CPU.
> > > >
> > > > What I want to know is if the snapscan
backend on its own is enough to
> > > > drive the scanner, or do I always need
the iscan shared libraries from
> > > > the Avasys website, and if yes, what is
the best place to install them ?
> > > 
> > > You need a firmware file (esfw52.bin).
> > > 
> > > As for the iscan shared libraries (I assume
you're talking about
> > > iscan-plugin-gt-f520-1.0.0-1.c2.i386.rpm) are
only used by the epkowa
> > > backend.  The snapscan backend does not use
them.  The epkowa backend
> > > is available in the iscan package/source.
> > > 
> > > Hope this helps,
> > > -- 
> > > Olaf Meeuwissen                         
EPSON AVASYS Corporation, SE1
> > > FSF Associate Member #1962           sign up
at http://member.fsf.org/
> > > GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 
976A 16C7 F27D 6BE3 7D90
> > > Penguin's lib!       -- I hack, therefore I
am --               LPIC-2
> > 
> > I already got the firmware, I added it to the
snapscan.conf file. I
> > suppose this is what makes the scanner tick, ie.
the software which
> > controls the device on-board.
> > 
> > When using this command :
> > 
> >  SANE_DEBUG_SNAPSCAN=255 SANE_DEBUG_SANEI_USB=255
scanimage -L
> > 
> > I see that the system does not hang on the scanner
detection, but on
> > the USB detection.
> > 
> > Here are the last 20 lines of the output.
> > 
> > [sanei_debug] Setting debug level of sanei_usb to
255.
> > [sanei_usb] sanei_usb_init: Looking for kernel
scanner devices
> > [sanei_usb] sanei_usb_init: can't stat /dev/usb/:
No such file or
> > directory
> > [sanei_usb] sanei_usb_init: Looking for libusb
devices
> > usb_os_init: Found USB VFS at /dev/bus/usb
> > usb_set_debug: Setting debugging level to 255 (on)
> > [sanei_usb] sanei_usb_init: found libusb device
(0x04b8/0x0122)
> > interface 0  at libusb:004:002
> > [sanei_usb] sanei_usb_init: device 0x0000/0x0000
looks like a root hub
> > [sanei_usb] sanei_usb_init: device 0x0000/0x0000
looks like a root hub
> > [sanei_usb] sanei_usb_init: device 0x0000/0x0000
looks like a root hub
> > [sanei_usb] sanei_usb_init: device 0x0000/0x0000
looks like a root hub
> > [sanei_usb] sanei_usb_init: found 1 devices
> > [sanei_usb] sanei_usb_find_devices: vendor=0x03f0,
product=0x0000
> > [sanei_usb] sanei_usb_find_devices: vendor=0x03f0,
product=0x2205
> > [sanei_usb] sanei_usb_find_devices: vendor=0x03f0,
product=0x2005
> > [sanei_usb] sanei_usb_find_devices: vendor=0x03f0,
product=0x2005
> > [sanei_usb] sanei_usb_find_devices: vendor=0x03f0,
product=0x0705
> > [sanei_usb] sanei_usb_find_devices: vendor=0x03f0,
product=0x0805
> > 
> > I have tried using gdb to attach to the process,
which works, but
> > since there is no symbolic information, I am
unable to get any output
> > which may help.
> > 
> > I suppose, since it hangs at the last line, that I
have a problem with
> > a product from vendor 0x3f0, product 0x0805. Is
there somewhere an
> > index where I can lookup these codes ?
> > 
> > Regards,
> > 
> > Jurgen
> > 
> One way is using the Sane search page
> 
> http://www.sane-
project.org/cgi-bin/driver.pl?manu=&model=&bus=any&a
mp;v=03f0&p=0805
> 
> Last line from the   hp_rts88xx   backend.
> 
> In /etc/sane.d/dll.conf you can disable the not used
backends by placing
> a # before each backendname, maybe that will help.
> -- 
> --------
> m.vr.gr.
> Gerard Klaver
> 

I already did that. The only backend that is enabled is the
snapscan.

Jurgen

-- 
sane-devel mailing list: sane-devellists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/sane-d
evel
Unsubscribe: Send mail with subject "unsubscribe
your_password"
             to sane-devel-requestlists.alioth.debian.org

On Sun, Nov 19, 2006 at 04:54:12PM -0200, Marcio Braga
wrote:
> Hello, I'm new on Linux and in this list. My intention
is to help
> sharing my experience making this target scanner to
work on Linux from
> OpenSuSE 10.1 on x86-64 arch. Just in case, I wrote a
small "how to" on:
> ht
tp://en.opensuse.org/Epson_Perfection_3490_Photo
> 
> 
> Considering OpenSuSE already with Sane, the major steps
are:
> 
> 1. Check if usb hoplug recognized your usb scanner: Use
command line
> "lsusb" to check.

Check :

Bus 004 Device 002: ID 04b8:0122 Seiko Epson Corp.
Bus 004 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000

> 
> 2. Check if sane let snapscan be available: Uncomment
snapscan
> in /etc/sane.d/dll.conf

Check : Only snapscan is enabled in dll.conf
> 
> 3. Check if snapscan recognize the usb scanner: On
OpenSuSE use YaST
> (Hardware/Scanner). Do not know how to do it on Ubuntu.

Check : firmware /usr/share/iscan/esfw52.bin

and /usr/share/iscan/esfw52.bin does exist.
> 
> 4. Check if snapscan.conf (on /etc/sane.d) pointing
correctly to the
> target scanner firmware esfw52.bin.
>  
> obs: You can get the firmware esfw52.bin installing
iscan-firmware 1.18
> rpm package (in this 1.18 version there are packages
for i386, i586 and
> x86-64 arch).

I got already several from these packages, and a few months
ago I
compared them. It seems that this firmware is very stable.

> 
> That was all for me. scanimage command line works and
so xsane.
> 
> Regards
> Marcio
> 
> 
> 
> -- 
> sane-devel mailing list: sane-devellists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-d
evel
> Unsubscribe: Send mail with subject "unsubscribe
your_password"
>              to sane-devel-requestlists.alioth.debian.org

As a last resort, I tried it as an ordinary user instead of
root. Wouldn't you know that this works ?

So, using the scanner as root blocks on listing devices, but
as an
ordinary user (member of group scanner) this works.

Alright,

everybody thanks for the help.

Regards,

Jurgen

-- 
sane-devel mailing list: sane-devellists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/sane-d
evel
Unsubscribe: Send mail with subject "unsubscribe
your_password"
             to sane-devel-requestlists.alioth.debian.org