[sane-devel] Scanner failure when connected via USB3

Mike Cloaked mike.cloaked at gmail.com
Sun Oct 26 16:28:21 UTC 2014


On Tue, Sep 23, 2014 at 11:57 PM, Olaf Meeuwissen <olaf.meeuwissen at avasys.jp
> wrote:

>
> m. allan noah writes:
>
> > 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 :)
>
>   $ sudo modprobe usbmon
>   $ sudo wireshark
>
> and selecting the right USB bus to capture traffic on.  The `usbmon#`
> numbers match the bus numbers that `lsusb` outputs.
>
> Hope that helps,
>
>
Sorry about the delay - things got a bit hectic this month - the coming
week looks a little easier so I will set up to test the scanner for usb
logs during the coming week, and once I have captured some logging
information I will post back.

-- 
mike c
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20141026/aa2c6788/attachment.html>


More information about the sane-devel mailing list