[sane-devel] Scanner failure when connected via USB3

Mike Cloaked mike.cloaked at gmail.com
Tue Oct 28 09:04:37 UTC 2014


On Tue, Oct 28, 2014 at 12:02 AM, Olaf Meeuwissen <olaf.meeuwissen at avasys.jp
> wrote:

>
> The idea is that you start/stop capturing USB traffic with wireshark
> rather than cat whatever is left in the /sys/kernel/debug/usb/usbmon/
> files.  Wireshark will read off that and presents you with an easier to
> digest view of what went on.
>
> If you don't have a GUI on the machine with the scanner, you can use
> tshark instead to save to file and view it elsewhere.  Read the manual
> page for instructions.
>
> > Are these two log files a help in getting some diagnostics?
>
> Not unless you're a USB kernel buff, which I'm not ;-)
>
> Hope this helps,
> --
> Olaf Meeuwissen, LPIC-2           FLOSS Engineer -- AVASYS CORPORATION
>

OK I will have a look at using wireshark to try to capture something more
compact and more useful. Probably be a couple of days before I get a block
of time to do it, and then I'll post back.

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


More information about the sane-devel mailing list