search for: nut_libusb_open

Displaying 19 results from an estimated 19 matches for "nut_libusb_open".

2018 Aug 20
2
TrippLite SMX1500LCDT FreeBSD 11.2 trouble
...seen before with the port build): # /usr/local/ups/bin/usbhid-ups -a ups -DDDD -u root 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.002560 [D1] upsdrv_initups... 0.002748 [D2] nut_libusb_open: checking device 1 of 6. 0.002813 [D2] nut_libusb_open: - VendorID: 0000. 0.002819 [D2] nut_libusb_open: - ProductID: 0000. 0.002823 [D2] nut_libusb_open: - Manufacturer: Intel. 0.002826 [D2] nut_libusb_open: - Product: EHCI root HUB. 0.002829 [D2] nut_libusb_open...
2018 Aug 20
2
TrippLite SMX1500LCDT FreeBSD 11.2 trouble
Attached are config.log and usbhid-ups output with -u root (gzipped). Now driver output looks a lot like the one from port build. On Mon, Aug 20, 2018 at 1:42 PM, Charles Lepple <clepple at gmail.com> wrote: > On Aug 20, 2018, at 1:03 AM, Valentin Merkulov <schnobel at ickis.net> wrote: >> >> 0.033412 [D3] nut_usb_claim_interface: failed to claim USB >>
2023 Jun 29
0
NUT, Linux and libusb
...`root` and seeing most of the regular run-time info, in the initial device search it fails to find basic matching info points - the device vendor, product and sernum strings: ```` 0.289953 [D2] Device does not match - skipping 0.289960 [D2] Checking device 8 of 9 (0463/FFFF) 0.311147 [D1] nut_libusb_open get iManufacturer failed, retrying... 0.332348 [D1] nut_libusb_open get iManufacturer failed, retrying... 0.353600 [D1] nut_libusb_open get iManufacturer failed, retrying... 0.374780 [D1] nut_libusb_open get iProduct failed, retrying... 0.395962 [D1] nut_libusb_open get iProduct failed,...
2023 Jun 29
0
NUT, Linux and libusb
...`root` and seeing most of the regular run-time info, in the initial device search it fails to find basic matching info points - the device vendor, product and sernum strings: ```` 0.289953 [D2] Device does not match - skipping 0.289960 [D2] Checking device 8 of 9 (0463/FFFF) 0.311147 [D1] nut_libusb_open get iManufacturer failed, retrying... 0.332348 [D1] nut_libusb_open get iManufacturer failed, retrying... 0.353600 [D1] nut_libusb_open get iManufacturer failed, retrying... 0.374780 [D1] nut_libusb_open get iProduct failed, retrying... 0.395962 [D1] nut_libusb_open get iProduct failed,...
2018 Aug 20
2
TrippLite SMX1500LCDT FreeBSD 11.2 trouble
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_libus...
2018 Aug 19
2
TrippLite SMX1500LCDT FreeBSD 11.2 trouble
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) Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0022 bNumInterfaces = 0x0001 bConfigurationValue = 0x0001 iConfiguration = 0x0000 <no string> bmAttributes =
2023 Mar 24
1
Question on EATON UPS
...; > 0.039057 [D2] Checking device 4 of 10 (214B/7250) > > 0.039099 [D1] Failed to open device (214B/7250), skipping: > Access denied (insufficient permissions) > > 0.039109 [D2] Checking device 5 of 10 (0463/FFFF) > > 0.956144 [D1] nut_libusb_open get iManufacturer failed, > retrying... > > 0.956518 [D1] nut_libusb_open get iManufacturer failed, > retrying... > > 0.956836 [D1] nut_libusb_open get iManufacturer failed, > retrying... > > 0.957291 [D1] nut_libusb_open get iProduct fail...
2023 Mar 27
0
Question on EATON UPS
...rrors while launching the driver: 0.039057 [D2] Checking device 4 of 10 (214B/7250) 0.039099 [D1] Failed to open device (214B/7250), skipping: Access denied (insufficient permissions) 0.039109 [D2] Checking device 5 of 10 (0463/FFFF) 0.956144 [D1] nut_libusb_open get iManufacturer failed, retrying... 0.956518 [D1] nut_libusb_open get iManufacturer failed, retrying... 0.956836 [D1] nut_libusb_open get iManufacturer failed, retrying... 0.957291 [D1] nut_libusb_open get iProduct failed, retrying... 0.957708 [D1]...
2023 Mar 25
1
Question on EATON UPS
...[D2] Checking device 4 of 10 (214B/7250) >> >> 0.039099 [D1] Failed to open device (214B/7250), skipping: >> Access denied (insufficient permissions) >> >> 0.039109 [D2] Checking device 5 of 10 (0463/FFFF) >> >> 0.956144 [D1] nut_libusb_open get iManufacturer failed, >> retrying... >> >> 0.956518 [D1] nut_libusb_open get iManufacturer failed, >> retrying... >> >> 0.956836 [D1] nut_libusb_open get iManufacturer failed, >> retrying... >> >> 0.957291 [D...
2023 Mar 23
1
Question on EATON UPS
The "unknown" fields mean the driver did not get that piece of information from libusb. In case of Manufacturer/Product which are unknown in the later post, but known in the first, I suppose you had another driver running, or the kernel still owned it (udev misbehavior, not handing it off after reconnections, etc.) and so exclusive access was not given to the new (currently reporting)
2023 Nov 05
1
Passing hid_rep_index to libusb_get_config_descriptor is wrong?
...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"); ret = libusb_get_config_descriptor(device, - (uint8_t)usb_subdriver.hid_rep_index, + 0, //(uint8_t)usb_subdriver.hid_rep_index...
2023 Nov 05
1
Passing hid_rep_index to libusb_get_config_descriptor is wrong?
...ot; ;-) 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"); > ret = libusb_get_config_descriptor(device, > - (uint8_t)usb_subdriver.hid_rep_index, > + 0, //(uint8_...
2023 Nov 05
1
Passing hid_rep_index to libusb_get_config_descriptor is wrong?
...or 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"); >> ret = libusb_get_config_descriptor(device, >> - (uint8_t)usb_subdriver.hid_rep_index, >> +...
2017 Jun 18
3
Unable to use nut-2.7.4 with Eaton 5E1500I USB
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
2023 Nov 05
1
Passing hid_rep_index to libusb_get_config_descriptor is wrong?
...> 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"); >>> ret = libusb_get_config_descriptor(device, >>> - (uint8_t)usb_subdriver.hid_rep_index, &...
2017 Jun 19
0
Unable to use nut-2.7.4 with Eaton 5E1500I USB
...erence 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/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/libusb1.c:479: undefined reference to `libusb_strerror' libusb1.o: In function `nut_libusb_open': /builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/libusb1.c:181: undefined reference to `libusb_strerror' /builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/libusb1.c:282: undefined reference to `libusb_strerror' libusb1.o:/builddir/build/BUILD/nut-v2.7.4-418-gb...
2017 Jun 19
2
Unable to use nut-2.7.4 with Eaton 5E1500I USB
...r' > /builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/libusb1.c:469: > undefined reference to `libusb_strerror' > /builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/libusb1.c:479: > undefined reference to `libusb_strerror' > libusb1.o: In function `nut_libusb_open': > /builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/libusb1.c:181: > undefined reference to `libusb_strerror' > /builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/libusb1.c:282: > undefined reference to `libusb_strerror' > libusb1.o:/builddir/buil...
2017 Jun 16
0
Unable to use nut-2.7.4 with Eaton 5E1500I USB
...rs/libusb1.c:484: undefined reference to `libusb_strerror' /builddir/build/BUILD/nut-libusb-1.0/drivers/libusb1.c:469: undefined reference to `libusb_strerror' /builddir/build/BUILD/nut-libusb-1.0/drivers/libusb1.c:479: undefined reference to `libusb_strerror' libusb1.o: In function `nut_libusb_open': /builddir/build/BUILD/nut-libusb-1.0/drivers/libusb1.c:181: undefined reference to `libusb_strerror' /builddir/build/BUILD/nut-libusb-1.0/drivers/libusb1.c:282: undefined reference to `libusb_strerror' libusb1.o:/builddir/build/BUILD/nut-libusb-1.0/drivers/libusb1.c:289: more undef...
2017 Jun 15
2
Unable to use nut-2.7.4 with Eaton 5E1500I USB
Hi Manuel, 2017-06-14 15:16 GMT+02:00 Manuel Wolfshant <wolfy at nobugconsulting.ro>: > Hello > > > > On 06/14/2017 03:32 PM, Arnaud Quette wrote: > > > > On Jun 7, 2017, at 5:47 AM, Manuel Wolfshant <wolfy at nobugconsulting.ro> > wrote: > >> > >>> > If that matters, the OS is a fully updated CentOS 6.9 and this >>>