Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs/man/nut_usb_addvars.txt: make a NOTE of LibUSB specific debugging #2625

Merged
merged 1 commit into from
Sep 11, 2024
Merged

docs/man/nut_usb_addvars.txt: make a NOTE of LibUSB specific debugging #2625

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions docs/man/nut_usb_addvars.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -124,3 +124,19 @@ number.
As a rule of thumb for `usb_hid_desc_index` discovery, you can see larger
`wDescriptorLength` values (roughly 600+ bytes) in reports of `lsusb` or
similar tools.

[NOTE]
======
Run-time troubleshooting of USB-capable NUT drivers can involve not only
raising the common NUT debug verbosity (e.g. using the `DEBUG_MIN` setting
in linkman:ups.conf[5] or protocol commands to change the `driver.debug`
value), but may also benefit from LibUSB specific debugging.

For the latter, currently you would have to export the environment variable
`LIBUSB_DEBUG` before starting a NUT driver (may be set and "exported" via
linkman:nut.conf[5]), to a numeric value such as `4` ("All messages are
emitted"). For more details, including the currently supported values, see:

* https://libusb.sourceforge.io/api-1.0/
* https://libusb.sourceforge.io/api-1.0/group__libusb__lib.html
======
Loading