OK, from this build I get the following: # /usr/local/ups/bin/usbhid-ups -a ups -DDDD Network UPS Tools - Generic HID driver 0.53 (v2.7.4-603-gb14c3b42.7.4.1) USB communication driver 0.37 0.000000 [D1] debug level is '4' 0.001299 [D1] upsdrv_initups... 0.001450 [D2] nut_libusb_open: checking device 1 of 1. 0.033333 [D2] nut_libusb_open: - VendorID: 09ae. 0.033345 [D2] nut_libusb_open: - ProductID: 3016. 0.033350 [D2] nut_libusb_open: - Manufacturer: Tripp Lite. 0.033353 [D2] nut_libusb_open: - Product: TRIPP LITE UPS. 0.033357 [D2] nut_libusb_open: - Serial Number: unknown. 0.033361 [D2] nut_libusb_open: - Bus: 001. 0.033365 [D2] nut_libusb_open: - Device release number: 0002. 0.033368 [D2] nut_libusb_open: trying to match device... 0.033386 [D2] nut_libusb_open: device matches. 0.033399 [D3] nut_usb_claim_interface: libusb_kernel_driver_active() returned 1 (driver active). 0.033404 [D3] nut_usb_claim_interface: successfully set kernel driver auto-detach flag. 0.033412 [D3] nut_usb_claim_interface: failed to claim USB device (Other error). 0.033417 [D3] nut_usb_claim_interface: failed to detach kernel driver from USB device (Other error). 0.033422 [D3] nut_usb_claim_interface: failed to claim USB device (Other error). 0.033430 [D3] nut_usb_claim_interface: failed to detach kernel driver from USB device (Other error). 0.033434 [D3] nut_usb_claim_interface: failed to claim USB device (Other error). 0.033438 [D3] nut_usb_claim_interface: failed to detach kernel driver from USB device (Other error). 0.033443 [D3] nut_usb_claim_interface: failed to claim USB device (Other error). 0.033448 Can't claim USB device 09ae:3016 (Other error). 0.033456 [D1] upsdrv_cleanup...
On Mon, Aug 20, 2018 at 4:33 AM, Charles Lepple <[email protected]> wrote: > On Aug 19, 2018, at 3:03 PM, Valentin Merkulov <[email protected]> wrote: >> >> Here is what I get: >> >> # usbconfig -u 1 -a 3 dump_curr_config_desc >> ugen1.3: <Tripp Lite TRIPP LITE UPS> at usbus1, cfg=0 md=HOST spd=LOW >> (1.5Mbps) pwr=ON (100mA) >> > [...] > > Hmm, that may be an issue on the NUT side, then. (You might see issues if you > run those commands repeatedly, though.) > > We are working on another branch that uses the newer libusb-1.0 APIs. I > haven't had to modify a ports tree package in a while, but it should be > possible to substitute one of our snapshots from that branch. You can grab a > tarball from here: > > http://buildbot.networkupstools.org/~buildbot/docker-debian-jessie/snapshot/libusb-compat-1.0/rb14c3b4fe2540a6b4181918fb89678b68733a814-887/nut-v2.7.4-603-gb14c3b42.7.4.1.tar.gz > > and use that instead of the official NUT 2.7.4 tarball. > > SHA256(nut-v2.7.4-603-gb14c3b42.7.4.1.tar.gz)= > 4d67212669d777961f5a0c9215f1853004997cf225abeba3360453439390c6bd > > Some history of that branch (and other related branches) here: > https://github.com/networkupstools/nut/issues/300 _______________________________________________ Nut-upsuser mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
