[sane-devel] Scanner failure when connected via USB3

m. allan noah kitno455 at gmail.com
Tue Oct 28 13:21:36 UTC 2014

I was able to somewhat parse the logs using a bit of perl. I am
suprised about the difference in file size. Where you making the scans
with the same parameters in both cases?


On Tue, Oct 28, 2014 at 5:04 AM, Mike Cloaked <mike.cloaked at gmail.com> wrote:
> 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
> --
> sane-devel mailing list: sane-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
> 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 mailing list