https://bugzilla.novell.com/show_bug.cgi?id=840445
https://bugzilla.novell.com/show_bug.cgi?id=840445#c2
Johannes Meixner changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jsmeix@suse.com
--- Comment #2 from Johannes Meixner 2013-10-01 10:56:18 CEST ---
I got feedback via direct mail:
============================================================================
Dear Mr. Meixner,
thank you very much for your message and your comments.
Especially the hint with the USB port was helpful.
The scanner has a USB 1.1 interface. It was accidentally
connected to a USB 3.0 port. In principle, this should
not be an issue, as the 3.0 port should be compatible,
but it seems that there were timing problems.
I connected the scanner to a USB 2.0 port and thereby
found out that the problem with my scanner was actually
twofold - a problem with the USB port timing and
an issue with sane-find-scanner on 64 bit systems.
When the scanner is connected to an USB 3.0 port, there are
also problems with long response times of the scanimage program.
Running scanimage -L sometimes takes more than 20 seconds
to complete on the 64 bit system. With the USB 2.0 port it
finishes without delay, as it does on the 32 bit system.
So this part of the problem was obviously caused by
the USB 3.0 port.
However, the sane-find-scanner problem still exists.
Calling the sane-find-scanner version that came with
the OpenSUSE 12.3 release with the -v -v options with
root privileges lists the scanner as one USB device,
but it does not recognize it as a scanner. This only
happens on the 64 bit system, regardless of the USB port.
When reporting the issue on Alioth in February, the author
of sane-find-scanner has sent me an updated version.
This version did recognize the scanner, but it did not work
reliably. This was probably due to the USB port issue, which
I was not aware of at the time I tested the updated version.
Running yast with this updated version of sane-find-scanner
copied to /usr/bin works fine now with the scanner connected
to a USB 2.0 port. Xsane also works fine now on the 64 bit
system as it does on the 32 bit system.
============================================================================
Regarding USB 1.1 scannes at USB 2.0 versus 3.0 ports
I added a new section "USB Speed" to
http://en.opensuse.org/SDB:Configuring_Scanners
Regarding YaST scanner setup and
"sane-find-scanner" versus "scanimage -L":
One can set up any scanner model that is listed in
the list of scanner models in YaST regardlesss
whether or not the actual scanner device is autodetected
via "sane-find-scanner" and also even when the actual
scanner device is not connected to the computer, compare
http://en.opensuse.org/SDB:Configuring_Scanners#Scanner
----------------------------------------------------------------------------
Run the YaST scanner module and check the list of models therein.
You do not need to have a scanner connected to do this.
Click "Add" and pretend to set up an imaginary scanner.
Select the model and the driver from the list and click "Next"
..
Finally the selected driver for the model gets activated.
When no scanner is connected, all what happens is that the driver
tries to autodetect a scanner which will of course fail in this case.
----------------------------------------------------------------------------
One reason why one can set up a scanner regardless if connected or not
is that an admin should be able to set up a scanner on an end-user
computer (e.g. workstation or laptop) at any time regardless
if the scanner is connected or not.
When "the driver tries to autodetect a scanner" it is
what happens when "scanimage -L" is run.
The difference is that "sane-find-scanner" tries to autodetect
scanners without running various matching scanner drivers
while "scanimage -L" tries to autodetect scanners by running
all scanner drivers that are activated.
In the end it should have worked sufficiently well
if you had connected your HP 2200 C USB 1.1 scanner
right from the start at a USB 2.0 port at your computer.
Then you could have run the YaST scanner module and click "Add"
(regardless that the scanner was not autodetected at that time)
and select the scanner model manually from the list so that
YaST activates its matching scanner driver and afterwards
YaST runs "scanimage -L" which autodetects your scanner.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
