#73 AcerScan 620UT not working

[Anonymous]

Hello,
when I connect the AcerScan 620UT scanner, it's
identified by sane-find-scanner:

found USB scanner (vendor=0x04a5, product=0x2060) at
libusb:004:013
# Your USB scanner was (probably) detected. It may or
may not be supported by
# SANE. Try scanimage -L and read the backend's manpage.

However, scanimage -L (with SANE_DEBUG_SNAPSCAN set to
255) does not find the scanner:

$ scanimage -L
[sanei_debug] Setting debug level of snapscan to 255.
[snapscan] sane_snapscan_init
[snapscan] sane_snapscan_init: Snapscan backend version
1.4.37
[snapscan] add_usb_device(libusb:004:013)
[snapscan] add_usb_device: Detected (kind of) an USB device
[snapscan] snapscani_usb_open(libusb:004:013)
[snapscan] add_usb_device: error opening device
libusb:004:013: Invalid argument
[snapscan] add_usb_device(libusb:004:013)
[snapscan] add_usb_device: Detected (kind of) an USB device
[snapscan] snapscani_usb_open(libusb:004:013)
[snapscan] add_usb_device: error opening device
libusb:004:013: Invalid argument
[snapscan] sane_snapscan_get_devices (0xbfffea88, 0)

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).
[snapscan] sane_snapscan_exit

I'm running kernel 2.6.6 using libusb. Also, I get this
message in dmesg:

usb 4-1: new full speed USB device using address 14
usb 4-1: control timeout on ep0in
usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann dev
14 rqt 128 rq 6 len 100 ret -110
usb 4-1: control timeout on ep0in

These lines appear every time I run sane-find-scanner:
usb 4-1: control timeout on ep0in
usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann dev
14 rqt 128 rq 6 len 100 ret -110
usb 4-1: control timeout on ep0in
usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann dev
14 rqt 128 rq 6 len 100 ret -110

Also, what is interesting is that the ProductID
reported on my system differs from the
/etc/sane.d/snapscan.conf file. As sane-find-scanner
said, it's 0x2060, not 0x2040 as in the config file.
Thus I tried to add the following line to
snapscan.conf, but without results:

usb 0x04a5 0x2060

Please help!

I can be contacted at <joh-pub at deworks dot net>

[Oliver Schwartz]

Logged In: YES
user_id=89371

Hi,

> I'm running kernel 2.6.6 using libusb. Also, I get this
> message in dmesg:

there are some known problems with the combination of
libusb, kernel 2.6 and the snapscan backend. Unfortunately I
haven't been able to reproduce them here, my 620UT has
been working fine with libusb for ~2 years.

> Also, what is interesting is that the ProductID
> reported on my system differs from the
> /etc/sane.d/snapscan.conf file. As sane-find-scanner
> said, it's 0x2060, not 0x2040 as in the config file.
> Thus I tried to add the following line to
> snapscan.conf, but without results:

I've given up on sorting out Acer's model numbering. My
620UT reports itself with ID 0x2040, other people reported
there 640U using ID 0x2060. Since there seems to be no
difference between those scanners the ID is not important, it
just has to appear anywhere in snapscan.conf.

I've made some changes to the snapscan backend that should
resolve most issues with libusb and kernel 2.6 - at least some
people have reported that their problems disappeared.
Therefore I suggest that you try the latest version of the
snapscan backend from SANE CVS (you can get a daily
snapshot from http://www.sane-project.org/snapshots/ ).

However, if your scanner is never detected by
sane-find-scanner (even after a reboot and power-cycling the
scanner) there is probably something else wrong with your
USB setup. Maybe some other USB device blocks the bus.
Sometimes the hotplug agent gets in the way, too, you may
try to disable it.