search for: libusb1

...): https://github.com/networkupstools/nut/issues/300#issuecomment-263090233 > > The PPA switches NUT from libusb-0.1 to 1.0. > > https://launchpad.net/%7Eclepple/+archive/ubuntu/nut thanks. I added the repository, updated: Preparing to unpack .../libupsclient4_2.7.4-0ubuntu6~xenial~libusb1~gb0e1758_amd64.deb ... Unpacking libupsclient4:amd64 (2.7.4-0ubuntu6~xenial~libusb1~gb0e1758) over (2.7.2-4ubuntu1) ... Preparing to unpack .../nut-client_2.7.4-0ubuntu6~xenial~libusb1~gb0e1758_amd64.deb ... Unpacking nut-client (2.7.4-0ubuntu6~xenial~libusb1~gb0e1758) over (2.7.2-4ubuntu1) ......

...Errata and Bugfix Advisory 2013:0310 Upstream details at : https://rhn.redhat.com/errata/RHBA-2013-0310.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 1d57304c587c4aa3d5e39f322bc3d421a81c5621bdb771b05b0f06746950f880 libusb1-1.0.9-0.6.rc1.el6.i686.rpm c3345c9952eb5064f612c60a1fc5e438c8c1d10f5bbc90878847fd93cd8ba7e8 libusb1-devel-1.0.9-0.6.rc1.el6.i686.rpm 23fd81596031e8b1ad087bc4b359bfe50e0400cf4b1f8bedfa541050bf1b6ed9 libusb1-static-1.0.9-0.6.rc1.el6.i686.rpm x86_64: 1d57304c587c4aa3d5e39f322bc3d421a81c5621bdb771b0...

...1.127030 Got 0 HID objects... >> 1.127036 Quick update... >> >> Come to think of it, this might also depend on how OpenBSD provides libusb-0.1. What version of libusb-compat do you have? > > # pkg_info > ... > libusb-compat-0.1.5 libusb-0.1 compatibility layer for libusb1 > libusb1-1.0.9p8 library for USB device access from userspace > ... Nothing looks strange in libusb-compat, but there is a possibility that you are getting "Function not implemented" from some strange combinations of flags being passed to libusb1. Can you rebuild the libusb1...

...> 1.127036 Quick update... > > Come to think of it, this might also depend on how OpenBSD provides libusb-0.1. What version of libusb-compat do you have? # pkg_info libltdl-2.4.2p0 GNU libtool system independent dlopen wrapper libusb-compat-0.1.5 libusb-0.1 compatibility layer for libusb1 libusb1-1.0.9p8 library for USB device access from userspace nut-2.7.2p2 UPS monitoring program supporting many brands quirks-2.11 exceptions to pkg_add rules radeondrm-firmware-20131002p0 firmware binary images for radeondrm(4) driver > > However, checking the rest of t...

On Jun 16, 2017, at 6:12 AM, Manuel Wolfshant <wolfy at nobugconsulting.ro> wrote: > > running autogen.sh was triggered automatically. but even if I do it explicitly, I still get: > + autoreconf -i > configure.ac:887: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body

...mand': /builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/nutdrv_qx.c:542: undefined reference to `libusb_strerror' nutdrv_qx-nutdrv_qx.o:/builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/nutdrv_qx.c:568: more undefined references to `libusb_strerror' follow [...] libusb1.o: In function `nut_libusb_strerror': /builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/libusb1.c:484: undefined reference to `libusb_strerror' /builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/libusb1.c:469: undefined reference to `libusb_strerror' /builddir/bui...

...a composite USB device, CDC is on interface one, HID Power on Interface 2. According to the NUT source tree, an arduino HID subdriver came in a couple of years ago (e07bec1), so this should "just work" ;-) But it doesn't for me. I traced what I think the problem is to this section in libusb1.c diff --git a/drivers/libusb1.c b/drivers/libusb1.c index 17f4b8f74..f49cc78aa 100644 --- a/drivers/libusb1.c +++ b/drivers/libusb1.c @@ -420,7 +420,7 @@ static int nut_libusb_open(libusb_device_handle **udevp, upsdebugx(2, "Reading first configuration descriptor");...

...except the recent layers of cleanup). I guess I did not even realize that there is more than the regularly mentioned "interface number" to juggle here. So if you manage to reliably pinpoint which interface concept applies where, and add configurability to that with `addvar()` in `drivers/libusb1.c` (and `drivers/libusb0.c` if applicable/possible there) and `docs/man/nut_usb_addvars.txt` -- so this change applies consistently to all USB-aware drivers, and if it all works - that would be a welcome improvement :D Jim On Sun, Nov 5, 2023 at 11:29?PM Kelly Byrd <kbyrd at memcpy.com> wr...

...ast one interface. An interface may define zero or more endpoints. Reading about multiple configurations, they appear to be intended for things like a USB device operating in high-speed or low-speed mode, or a debug vs normal mode, or maybe high vs low power mode. Given this, hid_rep_index (which libusb1.h defines as "number of the interface we use in a composite USB device") is absolutely not the right thing to pass to libusb_get_config_descriptor(), because the number of configurations are not related to the index of the interface being used. Passing 0 would be better than the current c...

...objects... >>> 1.127036 Quick update... >>> >>> Come to think of it, this might also depend on how OpenBSD provides libusb-0.1. What version of libusb-compat do you have? >> # pkg_info >> ... >> libusb-compat-0.1.5 libusb-0.1 compatibility layer for libusb1 >> libusb1-1.0.9p8 library for USB device access from userspace >> ... > Nothing looks strange in libusb-compat, but there is a possibility that you are getting "Function not implemented" from some strange combinations of flags being passed to libusb1. > > Can you...

...ce may define zero or > more endpoints. > > Reading about multiple configurations, they appear to be intended for > things like a USB device operating in high-speed or low-speed mode, or a > debug vs normal mode, or maybe high vs low power mode. Given this, > hid_rep_index (which libusb1.h defines as "number of the interface we use > in a composite USB device") is absolutely not the right thing to pass to > libusb_get_config_descriptor(), because the number of configurations are > not related to the index of the interface being used. Passing 0 would be > bette...

...d/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/nutdrv_qx.c:542: > undefined reference to `libusb_strerror' > nutdrv_qx-nutdrv_qx.o:/builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/nutdrv_qx.c:568: > more undefined references to `libusb_strerror' follow > [...] > libusb1.o: In function `nut_libusb_strerror': > /builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/libusb1.c:484: > undefined reference to `libusb_strerror' > /builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/libusb1.c:469: > undefined reference to `libusb_strerro...

...or your issue): >>> https://github.com/networkupstools/nut/tree/libusb-1.0 >>> <https://github.com/networkupstools/nut/tree/libusb-1.0> >> > > argh, no improvement, but still with libusb 0.1. > do you have libusb 1.0 -devel package installed? With that libusb1.0 > nut branch, if both 1.0 and 0.1 are available, 1.0 will take precedence. I just tried using libusb-1.0 instead of 0.1 (the only change I did was to replace libusb 0.1-devel with libusb 1.0-devel in the buildroot ) but it did not fly. I'll try to see what was missing and fix: libtool:...

This is new install on Ubuntu 16.04, using packages from Synaptic, *Network UPS Tools upsd 2.7.2 I am getting these messages in the terminal: Broadcast message from nut at amethi (somewhere) (Fri Dec 2 12:33:03 2016): UPS CyberUPS1 at localhost is unavailable I am still unclear on where to set when nut shutdowns system. I see nut-client and nut server are automatically starting from SystemD.

...Device [CPS UPS VALUE] on usb-0000:00:14.0-5.2/input0 2023-01-28T09:07:15+1100 nut-driver at ups[1289]: Network UPS Tools - Generic HID driver 0.47 (2.8.0) 2023-01-28T09:07:15+1100 nut-driver at ups[1289]: USB communication driver (libusb 1.0) 0.43 2023-01-28T09:07:15+1100 nut-driver at ups[1289]: libusb1: Could not open any HID devices: insufficient permissions on everything 2023-01-28T09:07:15+1100 nut-driver at ups[1289]: No matching HID UPS found 2023-01-28T09:07:15+1100 nut-driver at ups[1259]: Driver failed to start (exit status=1) 2023-01-28T09:07:20+1100 nut-driver at ups[1580]: Network UPS...

...23 [D3] HID descriptor length (method 2) > 549 > 9.250028 [D2] HID descriptor length 549 > > 9.250515 [D2] Unable to get Report descriptor: Broken pipe > > argh, no improvement, but still with libusb 0.1. do you have libusb 1.0 -devel package installed? With that libusb1.0 nut branch, if both 1.0 and 0.1 are available, 1.0 will take precedence. > > Comments on the new tree: > a) there seem to be some missing files in the tree: > - some bits for augeas, devs and udev: > configure.ac:1526: required file `scripts/augeas/nutupsconf.aug.in' n...

On Sep 18, 2014, at 10:09 PM, Stan Gammons <sg063015 at gmail.com> wrote: > > On 09/17/14 22:31, Charles Lepple wrote: >> Can you rebuild the libusb1 pkg as a port, with the DEBUG flag turned on? > > > Is --enable-debug the way one turns it on? I modified the Makefile as shown below, then did a make and make install. I am not sure how to tell OpenBSD to use that ".ifdef DEBUG" section. I think FreeBSD would let you set a D...

...00, Mark LaPierre wrote: > On 12/14/14 07:29, ken wrote: > > uname -r; rpm -q libusb > > CentOS 6.6 says: > [mlapier at mushroom ~]$ uname -r; rpm -q libusb > 2.6.32-504.1.3.el6.i686 > libusb-0.1.12-23.el6.i686 CentOS 5 has: libusb-0.1.12 CentOS 6 has: libusb-0.1.12 libusb1-1.0.9 CentOS 7 has: libusb-0.1.4 libusbx-1.0.15 -- rgds Stephen

On Sep 11, 2014, at 11:04 PM, Stan Gammons <sg063015 at gmail.com> wrote: > I see a libusb_get_interrupt message in the log. Could that be the problem? Yes, it seems related. 1.126896 upsdrv_initinfo... 1.126906 upsdrv_updateinfo... 1.127023 libusb_get_interrupt: Function not implemented 1.127030 Got 0 HID objects... 1.127036 Quick update... Come to think of it, this

...1 01 22 e1 01 > > 0.962201 [D3] HID descriptor length (method 2) 481 > > 0.962309 [D2] HID descriptor length 481 > > 0.962697 [D2] Unable to get Report descriptor: Resource > temporarily unavailable > > ? > > 0.963687 [D2] libusb1: No appropriate HID device found > > 0.963784 libusb1: Could not open any HID devices: insufficient > permissions on everything > > 0.963810 No matching HID UPS found > > > > > > Thanks for your help. > > Laurent > > > > >...