search for: libusb_get_string

[please use reply-all to include the list, as the list does not override the Reply-To header.] On Jun 7, 2015, at 5:02 PM, Greg Hersch <hersch.greg at gmail.com> wrote: > Here is the driver debug log. If I just let it run, it pops up with > libusb_get_string_invalid argument over and over again, mixed in the > debug output. seems to be several issues reported in the log, but they > arent easily interpreted. Does the libusb_get_string error occur only every 30 seconds or so? > 1.164089 Path: UPS.ffff0015.[1].ffff00c5, Type: Feature, &gt...

Hello, Dist: Debian Testing Kernel: 2.6.38.3 Software: nut 2.6.0-1 I believe this is a chipset bug, are there any plans for a workaround? The messages have changed over the kernel versions for this problem, but the problem itself still exists: Apr 21 09:17:25 p34 usbhid-ups[3737]: libusb_get_string: error sending control message: Broken pipe Apr 21 09:44:20 p34 usbhid-ups[3737]: libusb_get_string: error sending control message: Broken pipe Error from 2009 (still a problem) http://lists.alioth.debian.org/pipermail/nut-upsuser/2009-October/005530.html This occurred on my last Intel motherboar...

...e the list, as the list does not override >>> the Reply-To header.] >>> >>> On Jun 7, 2015, at 5:02 PM, Greg Hersch <hersch.greg at gmail.com> wrote: >>> >>>> Here is the driver debug log. If I just let it run, it pops up with >>>> libusb_get_string_invalid argument over and over again, mixed in the >>>> debug output. seems to be several issues reported in the log, but they >>>> arent easily interpreted. >>> >>> >>> Does the libusb_get_string error occur only every 30 seconds or so? >>...

...t does not override >>>> the Reply-To header.] >>>> >>>> On Jun 7, 2015, at 5:02 PM, Greg Hersch <hersch.greg at gmail.com> wrote: >>>> >>>>> Here is the driver debug log. If I just let it run, it pops up with >>>>> libusb_get_string_invalid argument over and over again, mixed in the >>>>> debug output. seems to be several issues reported in the log, but they >>>>> arent easily interpreted. >>>> >>>> >>>> Does the libusb_get_string error occur only every 30 secon...

...d/recompiled CFLAGS=-G program. You will notice i made a change to the version definition of tripplite-hid.c just to make sure i am working with the updated version. On Tue, 9 Jun 2015, Charles Lepple wrote: > On Jun 9, 2015, at 4:55 PM, Greg Hersch wrote: > >> (gdb) bt >> #0 libusb_get_string (udev=0x43110, StringIdx=0, buf=0x40204 <buf> >> "", buflen=20) at libusb.c:496 >> #1 0x00015330 in HIDGetIndexString (udev=<optimized out>, >> Index=<optimized out>, buf=0x40204 <buf> "", buflen=<optimized out>) >> at libhi...

On Jun 9, 2015, at 4:55 PM, Greg Hersch wrote: > (gdb) bt > #0 libusb_get_string (udev=0x43110, StringIdx=0, buf=0x40204 <buf> > "", buflen=20) at libusb.c:496 > #1 0x00015330 in HIDGetIndexString (udev=<optimized out>, > Index=<optimized out>, buf=0x40204 <buf> "", buflen=<optimized out>) > at libhid.c:407 > #2...

...hange to the version definition of tripplite-hid.c just to make sure i am working with the updated version. >> >> On Tue, 9 Jun 2015, Charles Lepple wrote: >> >>> On Jun 9, 2015, at 4:55 PM, Greg Hersch wrote: >>> >>>> (gdb) bt >>>> #0 libusb_get_string (udev=0x43110, StringIdx=0, buf=0x40204 <buf> >>>> "", buflen=20) at libusb.c:496 >>>> #1 0x00015330 in HIDGetIndexString (udev=<optimized out>, >>>> Index=<optimized out>, buf=0x40204 <buf> "", buflen=<optimized ou...

...UPS is AVR900U System is archlinux - fully up to date, running on an ARM device. Linux <Systemnameomitted > 3.1.10-35-ARCH #1 PREEMPT Fri Jan 23 19:14:18 MST 2015 armv5tel GNU/Linux I can communicate with my UPS - no problems But in my system log i constantly get: "usbhid-ups[27732]: libusb_get_string: Invalid argument" command to launch: /usr/local/ups/sbin/upsdrvctl start -------------------------- ups.conf: [tripplite] driver = usbhid-ups port = auto vendorid = 09ae maxreport # This was added as per the manual, as a workaround for some bug. It didnt...

On Jun 12, 2015, at 10:33 AM, Greg Hersch <hersch.greg at gmail.com> wrote: > thanks - this has been fun. > > There is one other thing I have been having trouble with - and i've tried it on two archlinuxarm installs and gotten the same thing. i am not even sure if its important for me. but if i try to configure and make with neon support - it cant find the neon libraries.

.... You will notice i made a change to the version definition of tripplite-hid.c just to make sure i am working with the updated version. > > On Tue, 9 Jun 2015, Charles Lepple wrote: > >> On Jun 9, 2015, at 4:55 PM, Greg Hersch wrote: >> >>> (gdb) bt >>> #0 libusb_get_string (udev=0x43110, StringIdx=0, buf=0x40204 <buf> >>> "", buflen=20) at libusb.c:496 >>> #1 0x00015330 in HIDGetIndexString (udev=<optimized out>, >>> Index=<optimized out>, buf=0x40204 <buf> "", buflen=<optimized out>) >&...

...les Lepple wrote: > [please use reply-all to include the list, as the list does not override the Reply-To header.] > > On Jun 7, 2015, at 5:02 PM, Greg Hersch <hersch.greg at gmail.com> wrote: > >> Here is the driver debug log. If I just let it run, it pops up with >> libusb_get_string_invalid argument over and over again, mixed in the >> debug output. seems to be several issues reported in the log, but they >> arent easily interpreted. > > Does the libusb_get_string error occur only every 30 seconds or so? Yes - thats correct. perhaps more like every 15 sec....

...nition of tripplite-hid.c just to make sure i am working with the updated version. >>> >>> On Tue, 9 Jun 2015, Charles Lepple wrote: >>> >>>> On Jun 9, 2015, at 4:55 PM, Greg Hersch wrote: >>>> >>>>> (gdb) bt >>>>> #0 libusb_get_string (udev=0x43110, StringIdx=0, buf=0x40204 <buf> >>>>> "", buflen=20) at libusb.c:496 >>>>> #1 0x00015330 in HIDGetIndexString (udev=<optimized out>, >>>>> Index=<optimized out>, buf=0x40204 <buf> "", buflen=<...

...se use reply-all to include the list, as the list does not override >> the Reply-To header.] >> >> On Jun 7, 2015, at 5:02 PM, Greg Hersch <hersch.greg at gmail.com> wrote: >> >>> Here is the driver debug log. If I just let it run, it pops up with >>> libusb_get_string_invalid argument over and over again, mixed in the >>> debug output. seems to be several issues reported in the log, but they >>> arent easily interpreted. >> >> >> Does the libusb_get_string error occur only every 30 seconds or so? > > > Yes - thats cor...

Hello, I have an openups2 ups. It works very well with nut, except two things: 1) It keeps sending a 'libusb_get_string: invalid argument' message to the log; 2) It does not report any command. Following http://nut-upsdev.alioth.debian.narkive.com/bmJyFFkO/libusb-get-string-invalid-argument, I was able to fix the error message using the attached patch. I do not know how ot fix the second point, but it is no...

...ignore the hid-generic errors; NUT detaches that kernel driver and bypasses it with libusb. That said, it means the HID descriptor has some syntax issues. > If I manually run 'upsdrvctl start? I get this : > > USB communication driver 0.32 > Using subdriver: openUPS HID 0.4 > libusb_get_string: Invalid argument > libusb_get_string: Invalid argument The driver should only call libusb_get_string() for informational purposes, so it should only affect ups.mfr and ups.model in upsc. > > And if I run upsd with high level of debug, after working OK for a while, I see these ?broken p...

...ver.version.data: openUPS HID 0.4 driver.version.internal: 0.41 input.current: 0.000 input.voltage: 12.08 output.current: 0.000 output.voltage: 12.04 ups.mfr: Mini-Box.Com ups.model: OPEN-UPS2 ups.productid: d005 ups.serial: LI-ION ups.status: OL ups.vendorid: 04d8 Note that there is still a 'libusb_get_string: Invalid argument' message into the log, but only when starting or resuming the system. > I don't think that the firmware supported commands when this sub-driver was written. It is certainly something we can check for, using the "explore" mode mentioned in the driver man page...

...sudo upsdrvctl -D start: Network UPS Tools - UPS driver controller 2.7.2 0.000000 Starting UPS: ups Network UPS Tools - Generic HID driver 0.38 (2.7.2) USB communication driver 0.32 Using subdriver: CyberPower HID 0.3 Syslog after server loses sight of UPS: Oct 6 17:29:01 kvm usbhid-ups[3529]: libusb_get_string: error sending control message: Broken pipe Oct 6 17:30:53 kvm upsd[3533]: Data for UPS [ups] is stale - check driver Oct 6 17:30:57 kvm upsmon[3548]: Poll UPS [ups at localhost] failed - Data stale Oct 6 17:30:57 kvm upsmon[3548]: Communications with UPS ups at localhost lost Oct 6 17:30:57 kv...

I?m a new user of NUT and the OpenUPS - in the past I?ve used APC hardware and apcupsd on Centos 6. I?ve built NUT 2.7.2 from source but used the OpenUPS HID driver v0.4 that?s in github. I?m using firmware version 1.5 on the openups which is the latest published version; I?ve also tried 1.7 which Mini-box sent to me but reverted to the published version. Their support seems a bit slow! I?ve got

...o look at the product string (for Belkin devices only) to determine whether it's a UPS. > - about your comment in newhidups.h (specifically "there is not file > libusb.h"): > > +/* there is not file libusb.h, so we have to declare this "by hand": > */+int libusb_get_string(int StringIdx, char *string); > > => if you mean the nut file that should go with libusb.c, then it's > hid-usb.h > (the reason is linked to the old libHID, and it's various backends...) > => if you mean the header from the libusb project, then it's named usb.h &g...

On Jul 21, 2017, at 3:21 PM, Alphonse <alphsteiner at gmail.com> wrote: > > Hello, > I have an openups2 ups. It works very well with nut, except two things: > 1) It keeps sending a 'libusb_get_string: invalid argument' message to the log; > 2) It does not report any command. > > Following http://nut-upsdev.alioth.debian.narkive.com/bmJyFFkO/libusb-get-string-invalid-argument, I was able to fix the error message using the attached patch. Thanks for the patch. For reference, what d...