similar to: Improving messages related to USB permissions

I've added a pull request with changes to drivers/libusb and drivers/usbhid-ups mainly. They are to resolve issues I encountered when setting up a Tripp Lite SMART1500LCDT, but I think they're generally useful to the community. Here is the pull request comment I sent: https://github.com/networkupstools/nut/pull/122 Had trouble getting nut to work for my new Tripp Lite SMART1500LCDT. So

Earlier this year, I added a patch to my local NUT tree to additionally print the value of usb_strerror() if usb_clear_halt() failed. (Ignore the commented-out goto.) Since these messages are at the LOG_ERR level, should we add usb_strerror() to all of the calls in nut_usb.c? diff --git a/drivers/nut_usb.c b/drivers/nut_usb.c index 494a1fa..4ca2691 100644 --- a/drivers/nut_usb.c +++

Hello, I'm currently try to get newhidups running with the newhidups driver from nut 2.0.2. After some USB issues (usb_claim_interface() works only as root so far) newhidups is recognizing the device. Though it doesn't detect any state changes, meaning when I run the battery test mode it's not recognized. I wanted to try the CVS version but it seems anonymous CVS is broken. The

Hi Stephen, It's been a little busy at home, so I haven't had a chance to go over the pull request in depth, but I didn't want you to think it hadn't been considered. On Apr 19, 2014, at 1:23 AM, Stephen J. Butler wrote: > I've added a pull request with changes to drivers/libusb and drivers/usbhid-ups mainly. They are to resolve issues I encountered when setting up a

hi NUT 2.4.3 on new server can not see serial number, but old nut on different hardware can? I have 2 USB-hid ups from APC, 1500 and 3000 RM, i use the serial number to identify them. However my new UPS monitor server can not see the serial number? It works on Linux dkserver 2.6.22.18-vs2.2.0.6 #1 SMP Sat Feb 16 20:54:32 CET 2008 i686 GNU/Linux debian package 2.2.2-6.5 it does not work on

Hi, I have a customer who just bought an APC Back-UPS XS 1300 LCD and I thought I'd try the latest NUT with it (on an old-ish FreeBSD 6.x system). It sees the UPS but I can't actually query it for data, in the usbhid-ups debug output I see.. 30.840512 HIDGetEvents: failed to buffer report: Result too large 30.840600 Got -34 HID objects... 30.840681 Quick update...

I've been running the Debian packaged 2.4.3 for a while, working find. When 2.6.0-1 just pushed through to debian, things have stopped working :( I checked what had been the usual suspects in past problems, namely permissions problems in /dev/bus/usb, but all seems in order: $ lsusb ... Bus 009 Device 002: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS $ ls -l /dev/bus/usb/009/002

Compiling against http://www.networkupstools.org/source/2.7/nut-2.7.4.tar.gz. I also have libusb-0.1-4 installed but no joy. On Mon, Mar 23, 2020 at 2:45 AM Jim Klimov <jimklimov at cos.ru> wrote: > On March 23, 2020 12:50:11 AM UTC, Tyler Montney <montneytyler at gmail.com> > wrote: > >Came across this in the process of troubleshooting: > > >

Dear Sirs, First of all I would like to thank you for support PCM product in your project. Kindly please be informed that POWERCOM launch new USB-controller with productID 0X04. Updated USB-controller compatible with previous version which supported by your usbhid-ups driver. There is added some command and changed idProduct. Vendor ID stay the same 0X0d9f without changes. Detailed information

Came across this in the process of troubleshooting: https://alioth-lists.debian.net/pipermail/nut-upsuser/2011-November/007249.html My whole reason for compiling from source is to add SSL support (as it doesn't seem available through the package manager). Apt list shows these installed: libusb-1.0-0-dev/stable,now 2:1.0.22-2 armhf [installed] libusb-1.0-0/stable,now 2:1.0.22-2 armhf

Hi, I have an MGE Ellipse 1000 connected to a FreeBSD 7.1 system and it works well except that if I yank the cable it doesn't detect a problem.. It seems to quite merrily read the old data (upsc reports the same values). There is nothing logged by NUT to indicate comms is lost (usbhid-ups is still running). In the attached log I yanked the able at the 28 second mark and plugged it back

On 9/28/06, Ingo Schaefer <ingo@ingo-schaefer.de> wrote: > Hallo, > > I installed nut 2.0.4 on a Solaris 8 and tried two things: > > First I wanted the ups to connect via usb, but I could not compile the > usb drivers. Make usb told me: no target named usb found Do you have libusb installed? (I was not aware that there was a port of libusb for versions of Solaris before

Hi Manuel 2017-06-07 14:40 GMT+02:00 Charles Lepple <clepple at gmail.com>: > 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 > (latest stable ) version of nut was packaged by me. The problem appears on > any of the USB ports ( well, I tried the 2 in

On Wed, Dec 3, 2008 at 4:05 PM, Arjen de Korte <nut+devel at de-korte.org> wrote: > Citeren Charles Lepple <clepple at gmail.com>: > >> Note that this is the same VID/PID as on this example on the Lakeview >> Research home page: >> >> http://www.lvr.com/usb_on_a_budget.htm >> >> We can include the name "Lakeview Research" in the

I just upgraded the FreeBSD buildbot machine from 6.4 to 8.0, and I ran across some interesting differences. The libusb API that we use (0.1) is available in /usr/include/usb.h and /usr/lib/libusb.* as before, but it seems to be the compatibility layer from libusb 1.0. However, it doesn't include the libusb-config binary. This is from the 'ports' Makefile for NUT: ########## - -

Greetings people; The section of drakeconf that pclos uses has two problems. First is several screens full of complaints about deprecated syntax in "/etc/udev/rules.d/70-nut-usbups.rules" at each reboot. So I pulled the current 2.5 svn trunk, then found I was missing quite a few build tools needed here that aren't used when building a kernel, currently running a 32 bit

Hi there... nut 2.4.3 kicks an error at me when I try to talk to my UPS. machine is linux 2.4.21-32.ELsmp with libusb-0.1.8-3 package update. # /usr/local/ups/bin/upsdrvctl start Network UPS Tools - UPS driver controller 2.4.3 Network UPS Tools - Generic HID driver 0.34 (2.4.3) USB communication driver 0.31 Using subdriver: APC HID 0.95 libusb_get_interrupt: error submitting URB: Invalid

Dear Sirs, We appreciate your support and cooperation. Can you please kindly add our new USB-controller with productID 0X04 to NUT compatible list. Updated USB-controller compatible with previous version which is supported by your usbhid-ups driver. Detailed information regarding new POWERCOM communication protocol you could download via link

Citeren Charles Lepple <clepple at gmail.com>: >> Another thing, loosely related to this, is how we are going to deal with the >> 'generic' VID:PID combinations in some of the USB drivers, for example the >> megatec_usb and (new) blazer_usb drivers. At present, in the megatec_usb >> driver we have several VID:PID combinations for USB-to-serial converters

Hi, Has anyone had success with the Dynamix 650VA, that uses the USB cable? I can't get megatec_usb to recognize it, I have tried both stable and development versions. Regards Glen Ogilvie