Difference between revisions of "USB Device Diagnostics in Linux"
(Created page with "To detect your USB device, in a terminal, you can try: lsusb lsusb -v The second, verbose, offering more detail. Another tool that provides extensive details for USB diag...") |
m |
||
| Line 16: | Line 16: | ||
A tool to show the device being recognized when inserted is | A tool to show the device being recognized when inserted is | ||
| − | udevadm | + | udevadm monitor --udev |
| + | |||
| + | The udevadm command cannot be run by itself. You must include a parameter to tell it what to do. | ||
=== input-utils package === | === input-utils package === | ||
| Line 23: | Line 25: | ||
* input-kbd - dump out the keyboard mapping of a particular event device, must specify the device number such as 'sudo input-kbd 3' | * input-kbd - dump out the keyboard mapping of a particular event device, must specify the device number such as 'sudo input-kbd 3' | ||
* input-events - observe input events for watching a specific input device, must specify the device number such as 'sudo input-events 3' | * input-events - observe input events for watching a specific input device, must specify the device number such as 'sudo input-events 3' | ||
| + | |||
| + | === udevadm === | ||
| + | udevadm can be used to monitor USB connections | ||
| + | |||
| + | udevadm -h | ||
| + | Usage: udevadm [--help] [--version] [--debug] COMMAND [COMMAND OPTIONS] | ||
| + | info query sysfs or the udev database | ||
| + | trigger request events from the kernel | ||
| + | settle wait for the event queue to finish | ||
| + | control control the udev daemon | ||
| + | monitor listen to kernel and udev events | ||
| + | hwdb maintain the hardware database index | ||
| + | test test an event run | ||
| + | test-builtin test a built-in command | ||
| + | |||
| + | To monitor USB connections here are some command usage examples: | ||
| + | udevadm monitor --subsystem-match=usb --property | ||
| + | udevadm monitor --subsystem-match=usb --property --udev | ||
| + | |||
| + | |||
Revision as of 19:08, 28 February 2019
To detect your USB device, in a terminal, you can try:
lsusb lsusb -v
The second, verbose, offering more detail.
Another tool that provides extensive details for USB diagnostics:
sudo lsinput
You may have to install it first, it is part of input-utils
sudo apt install input-utils
A tool to show the device being recognized when inserted is
udevadm monitor --udev
The udevadm command cannot be run by itself. You must include a parameter to tell it what to do.
input-utils package
input-utils: utilities for the input layer of the Linux kernel: This is a collection of utilities which are useful when working with the input layer of the Linux kernel (version 2.6 and later). Included are utilities to list the input devices known to the kernel, show the input events that are received by a device, and query or modify keyboard maps. Specifically the tools deal with /dev/input/event* input devices.
- lsinput - dumps out all the input devices and the associated details
- input-kbd - dump out the keyboard mapping of a particular event device, must specify the device number such as 'sudo input-kbd 3'
- input-events - observe input events for watching a specific input device, must specify the device number such as 'sudo input-events 3'
udevadm
udevadm can be used to monitor USB connections
udevadm -h Usage: udevadm [--help] [--version] [--debug] COMMAND [COMMAND OPTIONS] info query sysfs or the udev database trigger request events from the kernel settle wait for the event queue to finish control control the udev daemon monitor listen to kernel and udev events hwdb maintain the hardware database index test test an event run test-builtin test a built-in command
To monitor USB connections here are some command usage examples:
udevadm monitor --subsystem-match=usb --property udevadm monitor --subsystem-match=usb --property --udev
