Bug 141732 - sane hoses usb scanner
Summary: sane hoses usb scanner
Alias: None
Product: Fedora
Classification: Fedora
Component: sane-backends   
(Show other bugs)
Version: 3
Hardware: i686 Linux
Target Milestone: ---
Assignee: Tim Waugh
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2004-12-03 12:39 UTC by Sitsofe Wheeler
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-12-06 12:17:58 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Sitsofe Wheeler 2004-12-03 12:39:42 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040804 Galeon/1.3.17

Description of problem:
After some config file tweaking and firmware downloading I managed to get scanimage -l to detect an attached usb scanner. However doing scanimage by itself fails with some USB errrors reported by the kernel. scanimage -L no longer works.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Boot computer.
2. Log in as root over ssh.
3. Do scanimage -L . Note that:
device `snapscan:libusb:001:002' is a Acer FlatbedScanner22 flatbed scanner
is returned.
4. Do scanimage > /dev/null

Actual Results:  The following output is produced:
scanimage: open of device snapscan:libusb:001:002 failed: Error during device I/O

Expected Results:  Not sure. Never seen success.

Additional info:

The following is in dmesg:
usb 1-1: bulk timeout on ep1in
usb 1-1: usbfs: USBDEVFS_BULK failed ep 0x81 len 8 ret -110
usb 1-1: bulk timeout on ep2out
usb 1-1: usbfs: USBDEVFS_BULK failed ep 0x2 len 6 ret -110

scanimage -L no longer finds anything.

Unplugging and replugging the scanner moves it to a different address making scanimage -L work again, but repeating the steps results in the same problem.

Doing rmmod ohci_hcd; modprobe ohci_hcd makes whichever socket the USB scanner went wrong on disappear for good.

Comment 1 Sitsofe Wheeler 2004-12-03 12:40:49 UTC
Argh! Sorry for the long lines... This was done using the (Guided) bug entry
form on the beta bugzilla.

Comment 2 Tim Waugh 2004-12-03 12:49:20 UTC
There were some snapscan changes between SANE 1.0.14 and 1.0.15.  Please try
downloading and installing the sane-backends-1.0.15-7 package from here:


Does that still give the same problem?

Comment 3 Sitsofe Wheeler 2004-12-03 13:15:15 UTC
I might be a little while I am rebuilding the src.rpm against FC3 bits because I
don't want drag the system too far away from a "standard" install (I think it
wanted a newer pam and hotplug).

Comment 4 Sitsofe Wheeler 2004-12-03 13:49:10 UTC
And after all that the rebuilt RPM still wanted a newer pam and hotplug. Hpmph,
why didn't it warn me when I was installing the SRPM? Ah well, I shoved it on
using --nodeps.

Sigh. After upgrading /sbin/lsusb no longer detects the scanner at all. The
following is in dmesg:

ohci_hcd 0000:00:02.0: wakeup
hub 1-0:1.0: Cannot enable port 2.  Maybe the USB cable is bad?
hub 1-0:1.0: Cannot enable port 2.  Maybe the USB cable is bad?
usb 1-2: new full speed USB device using address 4
usb 1-2: device not accepting address 4, error -110
usb 1-2: new full speed USB device using address 5
usb 1-2: device not accepting address 5, error -110

Comment 5 Sitsofe Wheeler 2004-12-03 14:36:47 UTC
I figured I'd just double check whether I had the right firmware, you know, just
in case...

It turns out I had the wrong firmware. The scanner is an Acer/BenQ 4300U and is
reported as:
Bus 001 Device 017: ID 04a5:20b0 Acer Peripherals Inc. (now BenQ Corp.) S2W
in lsusb. According to http://snapscan.sourceforge.net/ this means I should need
the "u222v067.bin" firmware if you go via the "ID String" column. However, the
USB ID column for 0x04a5, 0x20b0 says you need the "u176v046.bin". The USB ID
column was the right one for me.

Clearly this is a user created problem. I think the only way I could salvage a
bit of dignity out of this bug is perhaps if I turn it into an enhancement
request for SANE to warn users about uploading the wrong firmware...

Comment 6 Tim Waugh 2004-12-06 12:17:58 UTC
Nice try. :-)

Comment 7 Sitsofe Wheeler 2004-12-06 12:42:21 UTC
Dang! I'll get you next time Waugh! : )

Note You need to log in before you can comment on or make changes to this bug.