[sane-devel] Still problems with Epson Perfection 3490 Photo

[Jurgen Defurne]

On Thu, Nov 16, 2006 at 08:19:19AM +0900, Olaf Meeuwissen wrote:
> jurgen.defurne at pandora.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