Discussion:
Behringer Uphoria UMC204 usb audio capture only pops and clicks
Andrew Reyes
2014-04-13 23:47:07 UTC
Permalink
I have a usb Behringer Uphoria UMC204 and it seems to work fine at 44.1khz
full duplex but anything higher than that I get consistent pops and
clicks. I notice it's on the capure side of things as when I have it in
playback only it's quiet. I have to say I'm testing this using JACK so this
is how I noticed it on the capture only side of things. I'm not sure
exactly whats needed to debug this issue. Any help would be appreciated.
Thanks in advance.
Andrew Reyes
2014-04-12 21:45:13 UTC
Permalink
I have a usb Behringer Uphoria UMC204 and it seems to work fine at 44.1khz
full duplex but anything higher than that I get consistent pops and
clicks. I notice it's on the capure side of things as when I have it in
playback only it's quiet. I have to say I'm testing this using JACK so this
is how I noticed it on the capture only side of things. I'm not sure
exactly whats needed to debug this issue. Any help would be appreciated.
Thanks in advance.
Andrew Reyes
2014-04-16 01:44:31 UTC
Permalink
I have a usb Behringer Uphoria UMC204 and it seems to work fine at 44.1khz
full duplex but anything higher than that I get consistent pops and
clicks. I notice it's on the capure side of things as when I have it in
playback only it's quiet. I have to say I'm testing this using JACK so this
is how I noticed it on the capture only side of things. I'm not sure
exactly whats needed to debug this issue. Any help would be appreciated.
Thanks in advance.
Daniel Mack
2014-04-16 08:40:30 UTC
Permalink
Post by Andrew Reyes
I have a usb Behringer Uphoria UMC204 and it seems to work fine at 44.1khz
full duplex but anything higher than that I get consistent pops and
clicks. I notice it's on the capure side of things as when I have it in
playback only it's quiet. I have to say I'm testing this using JACK so this
is how I noticed it on the capture only side of things. I'm not sure
exactly whats needed to debug this issue. Any help would be appreciated.
Could you send the output of 'lsusb -v', please?


Thanks,
Daniel
Andrew Reyes
2014-04-16 13:09:30 UTC
Permalink
Post by Daniel Mack
Could you send the output of 'lsusb -v', please?
Here is a pastebin link to the output:

-http://pastebin.com/nRULYjZh
Andrew Reyes
2014-04-18 04:30:37 UTC
Permalink
Does the output help?
Andrew Reyes
2014-04-21 03:12:43 UTC
Permalink
Should I be posting somewhere else. If so can someone let me know where?
Daniel Mack
2014-04-21 13:25:47 UTC
Permalink
Post by Andrew Reyes
Should I be posting somewhere else. If so can someone let me know where?
Please don't start a new thread every time you post but reply to an
existing thread. Given the traffic on this list, the conversation is not
easy to follow otherwise.

Regarding your issue - the descriptors look sane AFAICS. Please have a
look at /proc/asound/card/xxx/stream* (where xxx is the index of your
USB soundcard), and report the actual streaming frequency when playing
at rates higher than 44.1khz.

You can also monitor the values automatically, like so:

(while sleep 0.123; do grep 'Momentary freq' /proc/asound/xxx/stream0;
done) | uniq


Also, how to you play the audio? Try with aplay, and try to tweak the
values in the --buffer-size parameters.


Daniel
Andrew Reyes
2014-04-21 14:10:27 UTC
Permalink
How do I reply to an existing thread? I'm not clear on that. Sorry about
that. I was under the impression I had to reply by using the same subject
description.
Post by Daniel Mack
Post by Andrew Reyes
Should I be posting somewhere else. If so can someone let me know where?
Please don't start a new thread every time you post but reply to an
existing thread. Given the traffic on this list, the conversation is not
easy to follow otherwise.
Regarding your issue - the descriptors look sane AFAICS. Please have a
look at /proc/asound/card/xxx/stream* (where xxx is the index of your
USB soundcard), and report the actual streaming frequency when playing
at rates higher than 44.1khz.
(while sleep 0.123; do grep 'Momentary freq' /proc/asound/xxx/stream0;
done) | uniq
Also, how to you play the audio? Try with aplay, and try to tweak the
values in the --buffer-size parameters.
Daniel
Andrew Reyes
2014-04-21 14:17:09 UTC
Permalink
And this is the pastebin link for the stream info set at 48khz:
http://pastebin.com/ysw6j5uA
Post by Andrew Reyes
How do I reply to an existing thread? I'm not clear on that. Sorry about
that. I was under the impression I had to reply by using the same subject
description.
Post by Daniel Mack
Post by Andrew Reyes
Should I be posting somewhere else. If so can someone let me know where?
Please don't start a new thread every time you post but reply to an
existing thread. Given the traffic on this list, the conversation is not
easy to follow otherwise.
Regarding your issue - the descriptors look sane AFAICS. Please have a
look at /proc/asound/card/xxx/stream* (where xxx is the index of your
USB soundcard), and report the actual streaming frequency when playing
at rates higher than 44.1khz.
(while sleep 0.123; do grep 'Momentary freq' /proc/asound/xxx/stream0;
done) | uniq
Also, how to you play the audio? Try with aplay, and try to tweak the
values in the --buffer-size parameters.
Daniel
Daniel Mack
2014-04-21 16:11:11 UTC
Permalink
(please do not top-post)
Post by Andrew Reyes
http://pastebin.com/ysw6j5uA
Ok, so the actual frequency is close enough to the nominal one. Please
also do the tests wit aplay to see whether your issue can be recovered
by chosing larger buffer sizes. Do you see any messages in dmesg when
these 'clicks and pop' occur?

Also, please try this one:

(while sleep 0.123; do grep 'Momentary freq' /proc/asound/xxx/stream0;
done) | uniq

Thanks,
Daniel
Andrew Reyes
2014-04-21 16:51:08 UTC
Permalink
The while shell command shows consistent 96k when set at 96khz and dmesg
shows nothing where it pops and clicks. How do I use aplay to adjust
buffer-size?
Post by Daniel Mack
(please do not top-post)
Post by Andrew Reyes
http://pastebin.com/ysw6j5uA
Ok, so the actual frequency is close enough to the nominal one. Please
also do the tests wit aplay to see whether your issue can be recovered
by chosing larger buffer sizes. Do you see any messages in dmesg when
these 'clicks and pop' occur?
(while sleep 0.123; do grep 'Momentary freq' /proc/asound/xxx/stream0;
done) | uniq
Thanks,
Daniel
Daniel Mack
2014-04-21 17:49:03 UTC
Permalink
(Please, do not top-post but quote properly!)
Post by Andrew Reyes
The while shell command shows consistent 96k when set at 96khz and dmesg
shows nothing where it pops and clicks. How do I use aplay to adjust
buffer-size?
aplay -Dhw:xxx --buffer-size 2048 file.wav

(again, xxx is the index or short name of your audio card).

Which application do you normally use to play audio?


Daniel
Andrew Reyes
2014-04-21 18:33:23 UTC
Permalink
Post by Daniel Mack
aplay -Dhw:xxx --buffer-size 2048 file.wav
(again, xxx is the index or short name of your audio card).
Which application do you normally use to play audio?
I'm using JACK right now for recording and gigging live and pulseaudio for
Youtube and movies.
Here is the pastebin link for the aplay command:
http://pastebin.com/3nquKW12
Post by Daniel Mack
(Please, do not top-post but quote properly!)
Post by Andrew Reyes
The while shell command shows consistent 96k when set at 96khz and dmesg
shows nothing where it pops and clicks. How do I use aplay to adjust
buffer-size?
aplay -Dhw:xxx --buffer-size 2048 file.wav
(again, xxx is the index or short name of your audio card).
Which application do you normally use to play audio?
Daniel
Daniel Mack
2014-04-21 18:37:15 UTC
Permalink
Post by Andrew Reyes
Post by Daniel Mack
aplay -Dhw:xxx --buffer-size 2048 file.wav
(again, xxx is the index or short name of your audio card).
Which application do you normally use to play audio?
I'm using JACK right now for recording and gigging live and pulseaudio for
Youtube and movies.
Bot should of course work, but as they're built on top of ALSA, it's
best to debug directly on the lower level. IOW: with aplay.
Post by Andrew Reyes
http://pastebin.com/3nquKW12
Playing WAVE 'Open The Eyes Of My Heart.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
aplay: set_params:1233: Sample format non available
- S32_LE
Ok, in this case, please use "plughw" instead of "hw".


Daniel
Andrew Reyes
2014-04-21 18:44:16 UTC
Permalink
Post by Daniel Mack
Ok, in this case, please use "plughw" instead of "hw".
Ok that worked. It plays fine at 44100 but when I try to set
`--period-size=48000` it still defaults to 44100.
Post by Daniel Mack
Post by Andrew Reyes
Post by Daniel Mack
aplay -Dhw:xxx --buffer-size 2048 file.wav
(again, xxx is the index or short name of your audio card).
Which application do you normally use to play audio?
I'm using JACK right now for recording and gigging live and pulseaudio
for
Post by Andrew Reyes
Youtube and movies.
Bot should of course work, but as they're built on top of ALSA, it's
best to debug directly on the lower level. IOW: with aplay.
Post by Andrew Reyes
http://pastebin.com/3nquKW12
Playing WAVE 'Open The Eyes Of My Heart.wav' : Signed 16 bit Little
Endian, Rate 44100 Hz, Stereo
Post by Andrew Reyes
aplay: set_params:1233: Sample format non available
- S32_LE
Ok, in this case, please use "plughw" instead of "hw".
Daniel
Andrew Reyes
2014-04-21 18:49:15 UTC
Permalink
Post by Andrew Reyes
Post by Daniel Mack
Ok, in this case, please use "plughw" instead of "hw".
Ok that worked. It plays fine at 44100 but when I try to set
`--period-size=48000` it still defaults to 44100.

I'm sorry I meant to `--rate=48000`.
Post by Andrew Reyes
Post by Daniel Mack
Ok, in this case, please use "plughw" instead of "hw".
Ok that worked. It plays fine at 44100 but when I try to set
`--period-size=48000` it still defaults to 44100.
Post by Daniel Mack
Post by Andrew Reyes
Post by Daniel Mack
aplay -Dhw:xxx --buffer-size 2048 file.wav
(again, xxx is the index or short name of your audio card).
Which application do you normally use to play audio?
I'm using JACK right now for recording and gigging live and pulseaudio
for
Post by Andrew Reyes
Youtube and movies.
Bot should of course work, but as they're built on top of ALSA, it's
best to debug directly on the lower level. IOW: with aplay.
Post by Andrew Reyes
http://pastebin.com/3nquKW12
Playing WAVE 'Open The Eyes Of My Heart.wav' : Signed 16 bit Little
Endian, Rate 44100 Hz, Stereo
Post by Andrew Reyes
aplay: set_params:1233: Sample format non available
- S32_LE
Ok, in this case, please use "plughw" instead of "hw".
Daniel
Daniel Mack
2014-04-21 18:54:25 UTC
Permalink
Post by Andrew Reyes
Post by Andrew Reyes
Post by Daniel Mack
Ok, in this case, please use "plughw" instead of "hw".
Ok that worked. It plays fine at 44100 but when I try to set
`--period-size=48000` it still defaults to 44100.
I'm sorry I meant to `--rate=48000`.
Generate some sine wav files in various rates with something like
audacity and play them. FWIW, a 192k file can be found here:

http://zonque.org/sine-192khz.wav (~22 MB)


Daniel
Andrew Reyes
2014-04-21 18:56:57 UTC
Permalink
Post by Daniel Mack
Generate some sine wav files in various rates with something like
http://zonque.org/sine-192khz.wav (~22 MB)
Ok I will try that now. I should let you know that I just tried the
arecord command for that same device at 48000 and it pops and clicks just
as in JACK.
Post by Daniel Mack
Post by Andrew Reyes
Post by Andrew Reyes
Post by Daniel Mack
Ok, in this case, please use "plughw" instead of "hw".
Ok that worked. It plays fine at 44100 but when I try to set
`--period-size=48000` it still defaults to 44100.
I'm sorry I meant to `--rate=48000`.
Generate some sine wav files in various rates with something like
http://zonque.org/sine-192khz.wav (~22 MB)
Daniel
Andrew Reyes
2014-04-21 20:33:44 UTC
Permalink
Ok I did playback on a 48khz song and no pops and clicks. So it's just on
the capture side only. What could cause that on the capture side of things?
Post by Andrew Reyes
Post by Daniel Mack
Generate some sine wav files in various rates with something like
http://zonque.org/sine-192khz.wav (~22 MB)
Ok I will try that now. I should let you know that I just tried the
arecord command for that same device at 48000 and it pops and clicks just
as in JACK.
Post by Daniel Mack
Post by Andrew Reyes
Post by Andrew Reyes
Post by Daniel Mack
Ok, in this case, please use "plughw" instead of "hw".
Ok that worked. It plays fine at 44100 but when I try to set
`--period-size=48000` it still defaults to 44100.
I'm sorry I meant to `--rate=48000`.
Generate some sine wav files in various rates with something like
http://zonque.org/sine-192khz.wav (~22 MB)
Daniel
Andrew Reyes
2014-04-23 14:40:07 UTC
Permalink
Is there something else I could do to get to the problem?
Post by Andrew Reyes
Ok I did playback on a 48khz song and no pops and clicks. So it's just on
the capture side only. What could cause that on the capture side of things?
Post by Andrew Reyes
Post by Daniel Mack
Generate some sine wav files in various rates with something like
http://zonque.org/sine-192khz.wav (~22 MB)
Ok I will try that now. I should let you know that I just tried the
arecord command for that same device at 48000 and it pops and clicks just
as in JACK.
Post by Daniel Mack
Post by Andrew Reyes
Post by Andrew Reyes
Post by Daniel Mack
Ok, in this case, please use "plughw" instead of "hw".
Ok that worked. It plays fine at 44100 but when I try to set
`--period-size=48000` it still defaults to 44100.
I'm sorry I meant to `--rate=48000`.
Generate some sine wav files in various rates with something like
http://zonque.org/sine-192khz.wav (~22 MB)
Daniel
Daniel Mack
2014-04-23 14:59:35 UTC
Permalink
Post by Andrew Reyes
Is there something else I could do to get to the problem?
I can just give you a few more ideas to debug this, but that includes more action from your side.

* First of all, try the same device on a different computer, and/or a different USB port, especially if you're using an XHCI (USB3) port.

* Try the device on Mac OS X, without installing a driver and see if you have the same problem here.

* Use usbmon and analyze the data stream when a pop occurs. Compare that with settings that don't produce pops. There's good documentation on usbmon in Documentation/usb/ in the Linux kernel.


Best regards,
Daniel
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Andrew Reyes
2014-04-23 15:40:11 UTC
Permalink
Post by Daniel Mack
I can just give you a few more ideas to debug this, but that includes
more action from your side.
Post by Daniel Mack
* First of all, try the same device on a different computer, and/or a
different USB port, especially if you're using an XHCI (USB3) port.
Post by Daniel Mack
* Try the device on Mac OS X, without installing a driver and see if you
have the same problem here.
Post by Daniel Mack
* Use usbmon and analyze the data stream when a pop occurs. Compare that
with settings that don't produce pops. There's good documentation on usbmon
in Documentation/usb/ in the Linux kernel.

Ok cool. I'll get right on that. I did try the first suggestion on four
different computers and different ports and it's the same issue but just to
be thorough I'll check again.
Post by Daniel Mack
Post by Andrew Reyes
Is there something else I could do to get to the problem?
I can just give you a few more ideas to debug this, but that includes more
action from your side.
* First of all, try the same device on a different computer, and/or a
different USB port, especially if you're using an XHCI (USB3) port.
* Try the device on Mac OS X, without installing a driver and see if you
have the same problem here.
* Use usbmon and analyze the data stream when a pop occurs. Compare that
with settings that don't produce pops. There's good documentation on usbmon
in Documentation/usb/ in the Linux kernel.
Best regards,
Daniel
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Andrew Reyes
2014-04-23 16:18:29 UTC
Permalink
Ok I got the two different logs and I don't what I'm looking for lol. It's
just raw data. My last option is to try using it on Windows or Mac just to
make sure it's not the interface.
Post by Daniel Mack
Post by Daniel Mack
I can just give you a few more ideas to debug this, but that includes
more action from your side.
Post by Daniel Mack
* First of all, try the same device on a different computer, and/or a
different USB port, especially if you're using an XHCI (USB3) port.
Post by Daniel Mack
* Try the device on Mac OS X, without installing a driver and see if you
have the same problem here.
Post by Daniel Mack
* Use usbmon and analyze the data stream when a pop occurs. Compare that
with settings that don't produce pops. There's good documentation on usbmon
in Documentation/usb/ in the Linux kernel.
Ok cool. I'll get right on that. I did try the first suggestion on four
different computers and different ports and it's the same issue but just to
be thorough I'll check again.
Post by Daniel Mack
Post by Andrew Reyes
Is there something else I could do to get to the problem?
I can just give you a few more ideas to debug this, but that includes
more action from your side.
* First of all, try the same device on a different computer, and/or a
different USB port, especially if you're using an XHCI (USB3) port.
* Try the device on Mac OS X, without installing a driver and see if you
have the same problem here.
* Use usbmon and analyze the data stream when a pop occurs. Compare that
with settings that don't produce pops. There's good documentation on usbmon
in Documentation/usb/ in the Linux kernel.
Best regards,
Daniel
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Andrew Reyes
2014-04-24 14:14:58 UTC
Permalink
Daniel I got my hands on Windows 7 PC and installed the drivers from the
website and it does the samething. So now I'm leaning toward a defective
soundcard. I'm sending it back for a new one.
Post by Andrew Reyes
Ok I got the two different logs and I don't what I'm looking for lol.
It's just raw data. My last option is to try using it on Windows or Mac
just to make sure it's not the interface.
Post by Daniel Mack
Post by Daniel Mack
I can just give you a few more ideas to debug this, but that includes
more action from your side.
Post by Daniel Mack
* First of all, try the same device on a different computer, and/or a
different USB port, especially if you're using an XHCI (USB3) port.
Post by Daniel Mack
* Try the device on Mac OS X, without installing a driver and see if
you have the same problem here.
Post by Daniel Mack
* Use usbmon and analyze the data stream when a pop occurs. Compare
that with settings that don't produce pops. There's good documentation on
usbmon in Documentation/usb/ in the Linux kernel.
Ok cool. I'll get right on that. I did try the first suggestion on four
different computers and different ports and it's the same issue but just to
be thorough I'll check again.
Post by Daniel Mack
Post by Andrew Reyes
Is there something else I could do to get to the problem?
I can just give you a few more ideas to debug this, but that includes
more action from your side.
* First of all, try the same device on a different computer, and/or a
different USB port, especially if you're using an XHCI (USB3) port.
* Try the device on Mac OS X, without installing a driver and see if you
have the same problem here.
* Use usbmon and analyze the data stream when a pop occurs. Compare that
with settings that don't produce pops. There's good documentation on usbmon
in Documentation/usb/ in the Linux kernel.
Best regards,
Daniel
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Andrew Reyes
2014-04-29 17:53:36 UTC
Permalink
Daniel it turns out with a brand new UMC204 it still does it on my linux
box. I'm at a loss.
Post by Andrew Reyes
Daniel I got my hands on Windows 7 PC and installed the drivers from the
website and it does the samething. So now I'm leaning toward a defective
soundcard. I'm sending it back for a new one.
Post by Andrew Reyes
Ok I got the two different logs and I don't what I'm looking for lol.
It's just raw data. My last option is to try using it on Windows or Mac
just to make sure it's not the interface.
Post by Daniel Mack
Post by Daniel Mack
I can just give you a few more ideas to debug this, but that includes
more action from your side.
Post by Daniel Mack
* First of all, try the same device on a different computer, and/or a
different USB port, especially if you're using an XHCI (USB3) port.
Post by Daniel Mack
* Try the device on Mac OS X, without installing a driver and see if
you have the same problem here.
Post by Daniel Mack
* Use usbmon and analyze the data stream when a pop occurs. Compare
that with settings that don't produce pops. There's good documentation on
usbmon in Documentation/usb/ in the Linux kernel.
Ok cool. I'll get right on that. I did try the first suggestion on four
different computers and different ports and it's the same issue but just to
be thorough I'll check again.
Post by Daniel Mack
Post by Andrew Reyes
Is there something else I could do to get to the problem?
I can just give you a few more ideas to debug this, but that includes
more action from your side.
* First of all, try the same device on a different computer, and/or a
different USB port, especially if you're using an XHCI (USB3) port.
* Try the device on Mac OS X, without installing a driver and see if
you have the same problem here.
* Use usbmon and analyze the data stream when a pop occurs. Compare
that with settings that don't produce pops. There's good documentation on
usbmon in Documentation/usb/ in the Linux kernel.
Best regards,
Daniel
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Daniel Mack
2014-04-29 17:58:56 UTC
Permalink
(please, do not top post!)
Post by Andrew Reyes
Daniel it turns out with a brand new UMC204 it still does it on my linux
box. I'm at a loss.
Try that one on Windows as well. Uf it doesn't work there either, send tge hardqare back and get a different model. If the hardware has such severe bugs, there nothing the Linux driver can do to fix it up.


Daniel
Post by Andrew Reyes
Post by Andrew Reyes
Daniel I got my hands on Windows 7 PC and installed the drivers from
the
Post by Andrew Reyes
website and it does the samething. So now I'm leaning toward a
defective
Post by Andrew Reyes
soundcard. I'm sending it back for a new one.
On Wed, Apr 23, 2014 at 11:18 AM, Andrew Reyes
Post by Andrew Reyes
Ok I got the two different logs and I don't what I'm looking for
lol.
Post by Andrew Reyes
Post by Andrew Reyes
It's just raw data. My last option is to try using it on Windows or
Mac
Post by Andrew Reyes
Post by Andrew Reyes
just to make sure it's not the interface.
On Wed, Apr 23, 2014 at 10:40 AM, Andrew Reyes
Post by Daniel Mack
Post by Daniel Mack
I can just give you a few more ideas to debug this, but that
includes
Post by Andrew Reyes
Post by Andrew Reyes
Post by Daniel Mack
more action from your side.
Post by Daniel Mack
* First of all, try the same device on a different computer,
and/or a
Post by Andrew Reyes
Post by Andrew Reyes
Post by Daniel Mack
different USB port, especially if you're using an XHCI (USB3) port.
Post by Daniel Mack
* Try the device on Mac OS X, without installing a driver and see
if
Post by Andrew Reyes
Post by Andrew Reyes
Post by Daniel Mack
you have the same problem here.
Post by Daniel Mack
* Use usbmon and analyze the data stream when a pop occurs.
Compare
Post by Andrew Reyes
Post by Andrew Reyes
Post by Daniel Mack
that with settings that don't produce pops. There's good
documentation on
Post by Andrew Reyes
Post by Andrew Reyes
Post by Daniel Mack
usbmon in Documentation/usb/ in the Linux kernel.
Ok cool. I'll get right on that. I did try the first suggestion on
four
Post by Andrew Reyes
Post by Andrew Reyes
Post by Daniel Mack
different computers and different ports and it's the same issue but
just to
Post by Andrew Reyes
Post by Andrew Reyes
Post by Daniel Mack
be thorough I'll check again.
Post by Daniel Mack
On April 23, 2014 4:40:07 PM CEST, Andrew Reyes
Post by Andrew Reyes
Is there something else I could do to get to the problem?
I can just give you a few more ideas to debug this, but that
includes
Post by Andrew Reyes
Post by Andrew Reyes
Post by Daniel Mack
Post by Daniel Mack
more action from your side.
* First of all, try the same device on a different computer,
and/or a
Post by Andrew Reyes
Post by Andrew Reyes
Post by Daniel Mack
Post by Daniel Mack
different USB port, especially if you're using an XHCI (USB3)
port.
Post by Andrew Reyes
Post by Andrew Reyes
Post by Daniel Mack
Post by Daniel Mack
* Try the device on Mac OS X, without installing a driver and see
if
Post by Andrew Reyes
Post by Andrew Reyes
Post by Daniel Mack
Post by Daniel Mack
you have the same problem here.
* Use usbmon and analyze the data stream when a pop occurs.
Compare
Post by Andrew Reyes
Post by Andrew Reyes
Post by Daniel Mack
Post by Daniel Mack
that with settings that don't produce pops. There's good
documentation on
Post by Andrew Reyes
Post by Andrew Reyes
Post by Daniel Mack
Post by Daniel Mack
usbmon in Documentation/usb/ in the Linux kernel.
Best regards,
Daniel
--
Sent from my Android phone with K-9 Mail. Please excuse my
brevity.
--
Sent from my phone. Please excuse my brevity and typos.
Loading...