[sane-devel] Scanner failure when connected via USB3
m. allan noah
kitno455 at gmail.com
Mon Sep 22 20:57:25 UTC 2014
Mike- when you get back to the machine, maybe you could make some
logs. If we could see a usb log of what scanimage does and what
vuescan does, we might be able to find a difference. The problem will
be figuring out how to both reduce the volume of data the the bare
minimum which reproduces the problem, and also doing exactly the same
thing in both cases. I might be as simple as a 'scanimage --help'
multiple times in a row, and starting/stopping vuescan multiple times.
I'm not sure how to tell the kernel to enable usb logging, but I bet
google will tell you :)
On Thu, Sep 11, 2014 at 5:19 AM, Mike Cloaked <mike.cloaked at gmail.com> wrote:
> For some time I have been having an issue with xsane hanging when connecting
> to a Canoscan LIDE 210 flatbed scanner with a laptop that only has USB3
> ports, when the same scanner works flawlessly when connected to a laptop
> which only has USB2 ports.
> I have seen similar issues reported for other scanners in the Ubuntu forums,
> though I am using arch linux.
> I came across a posting very recently that suggested that when a scanner is
> connected to a USB3 port that using the vuescan package the scanner works
> without any problem.
> So I decided to test this for a laptop running current up-to-date arch linux
> that only has USB3 ports. With xsane running in KDE the scanner hangs
> reliably every time. Restarting the system and scanning with the vuescan
> package gives reliable flawless operation without any other change to the
> system or connections.
> This would seem to indicate that there is some kind of bug in the sane
> packages. I have tried in the past to find out how to diagnose this issue
> but I don't know where to begin to get logs that might help in finding where
> the problem lies.
> I will be happy to provide diagnostics but I will be tied up until 1st
> October - but after that I can run tests and generate logs to upload if a
> developer can suggest what I need to do to get the diagnostic information.
> It would be very nice to get to a solution for this issue as there is almost
> exclusively USB2 scanner hardware, and increasingly people will be running
> machines that have USB3 capability with xhci rather than ehci modules in the
> mike c
> sane-devel mailing list: sane-devel at lists.alioth.debian.org
> Unsubscribe: Send mail with subject "unsubscribe your_password"
> to sane-devel-request at lists.alioth.debian.org
"well, I stand up next to a mountain- and I chop it down with the edge
of my hand"
More information about the sane-devel