Quantcast

multiple, identical scanners?

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

multiple, identical scanners?

Jeremy Chacon
Hello,

I have been using sane to scan with an Epson v600 Perfection. scanimage works great with one or two scanners connected, I simply have to identify the address with scanimage -L and then use the entire device address when choosing the correct scanner.

However, we've now purchased two more identical scanners, and all of the sudden sane seems to have trouble. 

When I run scanimage -L, it usually complete, and gives four separate addresses. However, it takes very, very long (around 4-5 minutes), compared to the less than a minute for one or two scanners.

Additionally, sometimes not all the scanners have their model recognized, sometimes one is called "unknown epson ..."

The problems then persist with scanimage. If I scan with a device that was given a complete address with scanimage -L, it usually scans, but sometimes gives an I/O Error.  Even if it scans successfully, it often takes much longer than I would have expected. 

I'd appreciate any suggestions! 

Thanks,

Jeremy

--
___________________________________________________________________________

Jeremy M. Chacon, Ph.D.

Post-Doctoral Associate, Harcombe Lab
University of Minnesota
Ecology, Evolution and Behavior


--
sane-devel mailing list: [hidden email]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to [hidden email]
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: multiple, identical scanners?

Johannes Meixner

Hello,

On Nov 10 14:09 Jeremy Chacon wrote (excerpt):
> ... sometimes gives an I/O Error ...

In general "sometimes I/O Error" indicates that the root
cause is somehow hardware related where "hardware" means
the actual computer hardware plus the computer's built-in
firmware (i.e. BIOS or UEFI) and "hardware related" means
computer hardware plus firmware plus Linux kernel driver
plus low-level hardware related software (e.g. libusb).
You may have a look at "a stack consisting of various
layers must be functional in its entirety" in
https://en.opensuse.org/SDB:Configuring_Scanners#Basics

You did not tell how your scanners are connected to your
computer.

If your scanners are connected via USB:

There are currently issues with USB ports where the kernel
module "xhci" is used as kernel driver.
When "lsusb -t" shows "Driver=xhci_hcd" for the USB bus
and port where the USB scanner is connected (see "lsusb" where
the scanner is connected), then there could be issues depending
on the computer hardware and firmware.
In this case see
https://bugzilla.opensuse.org/show_bug.cgi?id=856794
in particular see
https://bugzilla.opensuse.org/show_bug.cgi?id=856794#c24
that reads (excerpt):
-----------------------------------------------------------------
My machine has 4 USB ports, two labeled with
the "super speed" USB logo (a.k.a. USB 3) and
two labeled with the normal USB logo (a.k.a. USB 2)
but for all 4 ports xhci is used and it fails on all 4 ports.
-----------------------------------------------------------------
and see
https://bugzilla.opensuse.org/show_bug.cgi?id=856794#c40

When your scanner is not connected at a USB port where the
kernel module xhci_hcd is used as kernel driver (e.g. when
your scanner is connected at a USB port where the kernel
module uhci_hcd or ehci_hcd is used as kernel driver),
then have a look at "Trouble-Shooting (Debugging)" in
https://en.opensuse.org/SDB:Configuring_Scanners

For example in your case to get USB debugging information
you could use comands (as root) like
-----------------------------------------------------------------
export SANE_DEBUG_SANEI_USB=128
scanimage -L
unset SANE_DEBUG_SANEI_USB
-----------------------------------------------------------------


Kind Regards
Johannes Meixner
--
SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard,
Graham Norton - HRB 21284 (AG Nuernberg)


--
sane-devel mailing list: [hidden email]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to [hidden email]
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: multiple, identical scanners?

Jeremy Chacon
Hi Johannes,

Thanks for your very thorough response!

It turned out you were correct, it was a USB issue. The scanners that always worked were connected to USB 2.0 ports, while the scanners that gave trouble were always connected to USB 3.0 ports (xhci_hcd when I did lsusb). 

Putting all the scanners on the older port type solved the problem.

Thanks very much!

Best,

Jeremy

On Wed, Nov 11, 2015 at 2:31 AM, Johannes Meixner <[hidden email]> wrote:

Hello,

On Nov 10 14:09 Jeremy Chacon wrote (excerpt):
... sometimes gives an I/O Error ...

In general "sometimes I/O Error" indicates that the root
cause is somehow hardware related where "hardware" means
the actual computer hardware plus the computer's built-in
firmware (i.e. BIOS or UEFI) and "hardware related" means
computer hardware plus firmware plus Linux kernel driver
plus low-level hardware related software (e.g. libusb).
You may have a look at "a stack consisting of various
layers must be functional in its entirety" in
https://en.opensuse.org/SDB:Configuring_Scanners#Basics

You did not tell how your scanners are connected to your
computer.

If your scanners are connected via USB:

There are currently issues with USB ports where the kernel
module "xhci" is used as kernel driver.
When "lsusb -t" shows "Driver=xhci_hcd" for the USB bus
and port where the USB scanner is connected (see "lsusb" where
the scanner is connected), then there could be issues depending
on the computer hardware and firmware.
In this case see
https://bugzilla.opensuse.org/show_bug.cgi?id=856794
in particular see
https://bugzilla.opensuse.org/show_bug.cgi?id=856794#c24
that reads (excerpt):
-----------------------------------------------------------------
My machine has 4 USB ports, two labeled with
the "super speed" USB logo (a.k.a. USB 3) and
two labeled with the normal USB logo (a.k.a. USB 2)
but for all 4 ports xhci is used and it fails on all 4 ports.
-----------------------------------------------------------------
and see
https://bugzilla.opensuse.org/show_bug.cgi?id=856794#c40

When your scanner is not connected at a USB port where the
kernel module xhci_hcd is used as kernel driver (e.g. when
your scanner is connected at a USB port where the kernel
module uhci_hcd or ehci_hcd is used as kernel driver),
then have a look at "Trouble-Shooting (Debugging)" in
https://en.opensuse.org/SDB:Configuring_Scanners

For example in your case to get USB debugging information
you could use comands (as root) like
-----------------------------------------------------------------
export SANE_DEBUG_SANEI_USB=128
scanimage -L
unset SANE_DEBUG_SANEI_USB
-----------------------------------------------------------------


Kind Regards
Johannes Meixner
--
SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard,
Graham Norton - HRB 21284 (AG Nuernberg)


--
sane-devel mailing list: [hidden email]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
            to [hidden email]



--
___________________________________________________________________________

Jeremy M. Chacon, Ph.D.

Post-Doctoral Associate, Harcombe Lab
University of Minnesota
Ecology, Evolution and Behavior


--
sane-devel mailing list: [hidden email]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to [hidden email]
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: multiple, identical scanners?

m. allan noah-3
You might find that a kernel and/or a sane-backends upgrade will help
that problem. There have been usb improvements in both of those places
in the past year.

allan

On Wed, Nov 11, 2015 at 4:49 PM, Jeremy Chacon <[hidden email]> wrote:

> Hi Johannes,
>
> Thanks for your very thorough response!
>
> It turned out you were correct, it was a USB issue. The scanners that always
> worked were connected to USB 2.0 ports, while the scanners that gave trouble
> were always connected to USB 3.0 ports (xhci_hcd when I did lsusb).
>
> Putting all the scanners on the older port type solved the problem.
>
> Thanks very much!
>
> Best,
>
> Jeremy
>
> On Wed, Nov 11, 2015 at 2:31 AM, Johannes Meixner <[hidden email]> wrote:
>>
>>
>> Hello,
>>
>> On Nov 10 14:09 Jeremy Chacon wrote (excerpt):
>>>
>>> ... sometimes gives an I/O Error ...
>>
>>
>> In general "sometimes I/O Error" indicates that the root
>> cause is somehow hardware related where "hardware" means
>> the actual computer hardware plus the computer's built-in
>> firmware (i.e. BIOS or UEFI) and "hardware related" means
>> computer hardware plus firmware plus Linux kernel driver
>> plus low-level hardware related software (e.g. libusb).
>> You may have a look at "a stack consisting of various
>> layers must be functional in its entirety" in
>> https://en.opensuse.org/SDB:Configuring_Scanners#Basics
>>
>> You did not tell how your scanners are connected to your
>> computer.
>>
>> If your scanners are connected via USB:
>>
>> There are currently issues with USB ports where the kernel
>> module "xhci" is used as kernel driver.
>> When "lsusb -t" shows "Driver=xhci_hcd" for the USB bus
>> and port where the USB scanner is connected (see "lsusb" where
>> the scanner is connected), then there could be issues depending
>> on the computer hardware and firmware.
>> In this case see
>> https://bugzilla.opensuse.org/show_bug.cgi?id=856794
>> in particular see
>> https://bugzilla.opensuse.org/show_bug.cgi?id=856794#c24
>> that reads (excerpt):
>> -----------------------------------------------------------------
>> My machine has 4 USB ports, two labeled with
>> the "super speed" USB logo (a.k.a. USB 3) and
>> two labeled with the normal USB logo (a.k.a. USB 2)
>> but for all 4 ports xhci is used and it fails on all 4 ports.
>> -----------------------------------------------------------------
>> and see
>> https://bugzilla.opensuse.org/show_bug.cgi?id=856794#c40
>>
>> When your scanner is not connected at a USB port where the
>> kernel module xhci_hcd is used as kernel driver (e.g. when
>> your scanner is connected at a USB port where the kernel
>> module uhci_hcd or ehci_hcd is used as kernel driver),
>> then have a look at "Trouble-Shooting (Debugging)" in
>> https://en.opensuse.org/SDB:Configuring_Scanners
>>
>> For example in your case to get USB debugging information
>> you could use comands (as root) like
>> -----------------------------------------------------------------
>> export SANE_DEBUG_SANEI_USB=128
>> scanimage -L
>> unset SANE_DEBUG_SANEI_USB
>> -----------------------------------------------------------------
>>
>>
>> Kind Regards
>> Johannes Meixner
>> --
>> SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard,
>> Graham Norton - HRB 21284 (AG Nuernberg)
>>
>>
>> --
>> sane-devel mailing list: [hidden email]
>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
>> Unsubscribe: Send mail with subject "unsubscribe your_password"
>>             to [hidden email]
>
>
>
>
> --
> ___________________________________________________________________________
>
> Jeremy M. Chacon, Ph.D.
>
> Post-Doctoral Associate, Harcombe Lab
> University of Minnesota
> Ecology, Evolution and Behavior
>
>
> --
> sane-devel mailing list: [hidden email]
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>              to [hidden email]



--
"well, I stand up next to a mountain- and I chop it down with the edge
of my hand"

--
sane-devel mailing list: [hidden email]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to [hidden email]
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: multiple, identical scanners?

Jeremy Chacon
Thanks, Allan, I'll try that too. Of course, this computer is isolated from the internet (groan), making upgrades difficult, but not impossible!

On Wed, Nov 11, 2015 at 4:17 PM, m. allan noah <[hidden email]> wrote:
You might find that a kernel and/or a sane-backends upgrade will help
that problem. There have been usb improvements in both of those places
in the past year.

allan

On Wed, Nov 11, 2015 at 4:49 PM, Jeremy Chacon <[hidden email]> wrote:
> Hi Johannes,
>
> Thanks for your very thorough response!
>
> It turned out you were correct, it was a USB issue. The scanners that always
> worked were connected to USB 2.0 ports, while the scanners that gave trouble
> were always connected to USB 3.0 ports (xhci_hcd when I did lsusb).
>
> Putting all the scanners on the older port type solved the problem.
>
> Thanks very much!
>
> Best,
>
> Jeremy
>
> On Wed, Nov 11, 2015 at 2:31 AM, Johannes Meixner <[hidden email]> wrote:
>>
>>
>> Hello,
>>
>> On Nov 10 14:09 Jeremy Chacon wrote (excerpt):
>>>
>>> ... sometimes gives an I/O Error ...
>>
>>
>> In general "sometimes I/O Error" indicates that the root
>> cause is somehow hardware related where "hardware" means
>> the actual computer hardware plus the computer's built-in
>> firmware (i.e. BIOS or UEFI) and "hardware related" means
>> computer hardware plus firmware plus Linux kernel driver
>> plus low-level hardware related software (e.g. libusb).
>> You may have a look at "a stack consisting of various
>> layers must be functional in its entirety" in
>> https://en.opensuse.org/SDB:Configuring_Scanners#Basics
>>
>> You did not tell how your scanners are connected to your
>> computer.
>>
>> If your scanners are connected via USB:
>>
>> There are currently issues with USB ports where the kernel
>> module "xhci" is used as kernel driver.
>> When "lsusb -t" shows "Driver=xhci_hcd" for the USB bus
>> and port where the USB scanner is connected (see "lsusb" where
>> the scanner is connected), then there could be issues depending
>> on the computer hardware and firmware.
>> In this case see
>> https://bugzilla.opensuse.org/show_bug.cgi?id=856794
>> in particular see
>> https://bugzilla.opensuse.org/show_bug.cgi?id=856794#c24
>> that reads (excerpt):
>> -----------------------------------------------------------------
>> My machine has 4 USB ports, two labeled with
>> the "super speed" USB logo (a.k.a. USB 3) and
>> two labeled with the normal USB logo (a.k.a. USB 2)
>> but for all 4 ports xhci is used and it fails on all 4 ports.
>> -----------------------------------------------------------------
>> and see
>> https://bugzilla.opensuse.org/show_bug.cgi?id=856794#c40
>>
>> When your scanner is not connected at a USB port where the
>> kernel module xhci_hcd is used as kernel driver (e.g. when
>> your scanner is connected at a USB port where the kernel
>> module uhci_hcd or ehci_hcd is used as kernel driver),
>> then have a look at "Trouble-Shooting (Debugging)" in
>> https://en.opensuse.org/SDB:Configuring_Scanners
>>
>> For example in your case to get USB debugging information
>> you could use comands (as root) like
>> -----------------------------------------------------------------
>> export SANE_DEBUG_SANEI_USB=128
>> scanimage -L
>> unset SANE_DEBUG_SANEI_USB
>> -----------------------------------------------------------------
>>
>>
>> Kind Regards
>> Johannes Meixner
>> --
>> SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard,
>> Graham Norton - HRB 21284 (AG Nuernberg)
>>
>>
>> --
>> sane-devel mailing list: [hidden email]
>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
>> Unsubscribe: Send mail with subject "unsubscribe your_password"
>>             to [hidden email]
>
>
>
>
> --
> ___________________________________________________________________________
>
> Jeremy M. Chacon, Ph.D.
>
> Post-Doctoral Associate, Harcombe Lab
> University of Minnesota
> Ecology, Evolution and Behavior
>
>
> --
> sane-devel mailing list: [hidden email]
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>              to [hidden email]



--
"well, I stand up next to a mountain- and I chop it down with the edge
of my hand"



--
___________________________________________________________________________

Jeremy M. Chacon, Ph.D.

Post-Doctoral Associate, Harcombe Lab
University of Minnesota
Ecology, Evolution and Behavior


--
sane-devel mailing list: [hidden email]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to [hidden email]
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: multiple, identical scanners?

Olaf Meeuwissen-4

Jeremy Chacon writes:

> Thanks, Allan, I'll try that too. Of course, this computer is isolated from
> the internet (groan), making upgrades difficult, but not impossible!

Seeing that you are using Perfection V600s I am pretty sure you are
using the epkowa backend.  If so, upgrading sane-backends will not help
at all.  You should upgrade to the latest iscan version, 2.30.1, which
contains USB 3 fixes.  I am not sure they will address your problem,
though.

You can download the lastest collection of packages (iscan, iscan-data
and a non-free interpreter plugin for your model) from

  http://download.ebz.epson.net/dsc/search/01/search/?OSC=LX

> On Wed, Nov 11, 2015 at 4:17 PM, m. allan noah <[hidden email]> wrote:
>
>> You might find that a kernel and/or a sane-backends upgrade will help
>> that problem. There have been usb improvements in both of those places
>> in the past year.

Hope this helps,
--
Olaf Meeuwissen, LPIC-2            FSF Associate Member since 2004-01-27
Support Free Software               Support the Free Software Foundation
https://my.fsf.org/donate                        https://my.fsf.org/join
 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9


--
sane-devel mailing list: [hidden email]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to [hidden email]
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: multiple, identical scanners?

Jeremy Chacon
Ah, thanks Olaf, I am indeed using epkowa.  I will update the iscan version.

Much appreciated,

Jeremy

On Fri, Nov 13, 2015 at 3:32 AM, Olaf Meeuwissen <[hidden email]> wrote:

Jeremy Chacon writes:

> Thanks, Allan, I'll try that too. Of course, this computer is isolated from
> the internet (groan), making upgrades difficult, but not impossible!

Seeing that you are using Perfection V600s I am pretty sure you are
using the epkowa backend.  If so, upgrading sane-backends will not help
at all.  You should upgrade to the latest iscan version, 2.30.1, which
contains USB 3 fixes.  I am not sure they will address your problem,
though.

You can download the lastest collection of packages (iscan, iscan-data
and a non-free interpreter plugin for your model) from

  http://download.ebz.epson.net/dsc/search/01/search/?OSC=LX

> On Wed, Nov 11, 2015 at 4:17 PM, m. allan noah <[hidden email]> wrote:
>
>> You might find that a kernel and/or a sane-backends upgrade will help
>> that problem. There have been usb improvements in both of those places
>> in the past year.

Hope this helps,
--
Olaf Meeuwissen, LPIC-2            FSF Associate Member since 2004-01-27
Support Free Software               Support the Free Software Foundation
https://my.fsf.org/donate                        https://my.fsf.org/join
 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9




--
___________________________________________________________________________

Jeremy M. Chacon, Ph.D.

Post-Doctoral Associate, Harcombe Lab
University of Minnesota
Ecology, Evolution and Behavior


--
sane-devel mailing list: [hidden email]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to [hidden email]
Loading...