similar to: monitor software does not find Belkin UPS

I have changed over to CentOS5 on some of our computers. I had been using Mandriva 2006 and the nut software worked using: driver = newhidups port = auto Using the same version of nut with the same config files on CentOS5, I get the following error output from 'upsdrvctl': Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4) No

I have changed over to CentOS5 on some of our computers. I had been using Mandriva 2006 and the nut software worked using: driver = newhidups port = auto Using the same version of nut with the same config files on CentOS5, I get the following error output from 'upsdrvctl': Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4) No

Well, I've spent a couple hours on this, unable to figure it out. I removed the libusb-compat-devel package using zypper. And I've downloaded, built, and installed libusb from sourceforge. But trying to configure nut now I get "USB drivers requested, but libusb not found", no matter what I put for --with-usb-libs. Continuing to flog away at it... Rob Groner Software

So far, the systemd service unit is working perfectly. Halleluia! For reference, here are the libs associated with the usbhid-ups driver: rtd at linux-fnda:/etc/init.d> ldd /usr/local/ups/bin/usbhid-ups linux-vdso.so.1 (0x00007fffecd25000) libusb-0.1.so.4 => /usr/lib64/libusb-0.1.so.4 (0x00007ff3b841b000) libpthread.so.0 => /lib64/libpthread.so.0

[Andrew: please subscribe to the nut-upsuser list: http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser Also, please gzip any attached logs.] > Hello, > > I downloaded NUT ver 2.6.2 and tried it on my Linux development > board. when I configure and it notified me that "USB drivers > requested, but libusb not found." > Then I download libusb

I have been trying to get Nut working on a system with Fedora 8 i86_64 installed and an APC Smart-UPS USB. The 2.2.0 rpm does not seem to like the USB on this UPS. I have tried compiling the 2.2.2 version, from source, but am getting warnings. I have tried building it on my i386 system (f8 as well) and I get no warnings also the 2.2.0 works fine on that one with a TrippLite Omni 900 LCD via

OK Eric, Den Tuesday 22 May 2007 08.56.08 skrev Eric S. Raymond: > Kjell Claesson <kjell.claesson at epost.tidanet.se>: > > Or install the udev rules and replug the ups. > > Did that. Manual startup of the driver now works without -u root, > indicating (I think) that the udev rools are doing their job. This >

On Sep 15, 2015, at 9:31 PM, Charles Lepple <clepple at gmail.com> wrote: > >> Trying to track down the source of the problem, I checked Yast to make sure I had at least 0.1.8 version for libusb. I saw this (attached photo). Is it then actually using ?compat instead of the ?real? libusb? And is that a problem? > > You're right, both the -compat and real libusb

Tim, Thanks for the help! No, I didn't already know that... I swear, the more time I spend at this, the less I seem to be understanding. I know that it had to be finding the libusb-compat I had just installed, because configure hadn't worked before that, and now it did. But finding useful version information seems to be almost impossible. Rob Groner Software Engineer Level II RTD

Hi, I've recently acquired a couple of Belkin F6H375-USB UPS units that use the Cypress Semiconductor interface (0665:5161), and they are not working with my etch servers. The usbhid driver sees them and takes possession but the nut software does not see anything. After exploration of the driver, running: % /lib/nut/usbhid-ups -DDDDDD -a belkin -x vendor=".*" -x

Thanks again Tim. I installed openSUSE from scratch, without installing libusb anything. I tried configure, and it failed because it couldn't find libusb. I used ldconfig to see what the system could see. It found 3 entries with "libusb" in them. I then built and installed the last update of libusb-0.1 (not libusb-compat or libusb-1.0). I tried configure, and it ran without

Rob - Just stepping in from the sidelines . . . with a few tidbits. Nut uses pkgconfig to find and identify stuff as part of it's build . . . So, depending on where your libusb install went, if it wasn't in the default "PKG_CONFIG_PATH" setting, it won't be found. Much like other shell variables, you can adjust that setting to find anything you like . . . IE

Hello I am trying to install Oblivion on Fedora 16 64-bit but am having problems with the install sheild crashing. I have read that this is because of the 64 bit wine so I am trying to build an older version of wine from source. However I am having problems with this aswell. I suspect that this is because of the 64-bit OS aswell. the reason I say this is that it appears 'make' is still

I recently bought a Belkin F6H375 UPS. It connects to the computer via USB. Searching the Internet led me to believe that the megatec_usb driver in nut supports this UPS, however I've been unable to get it to work. I have this in ups.conf: [belkinusb] driver = megatec_usb port = auto desc = "Belkin USB" Here's what happens when I try to use it: ~ #

For fun, if you want to see where the system thinks it is linking a library from, you can use "ldconfig -p" and it will give you a path to all known libraries that it can find. If you have one loaded, and it can't find it (odd directory, etc.) you can always amend "LD_LIBRARY_PATH" the same way as PKG_CONFIG_PATH I mentioned earlier . . . . PKG . . . is for the build

Ok, I tried this from scratch on a fresh 2.7.2 directory. I followed the web instructions, specifically: + I generated the new subdriver for my UPS (rtd-hid.*) based on PATH info. + I put them in the drivers subdir + I added the include line (#include rtd-hid.h) in usbhid-ups.c (specifically in the #ifndef SHUT_MODE section) + I added &rtd_subdriver, to the subdriver_list in usbhid-ups.c

Sorry for the bad formatting of the previous message...I tried to use plus signs as bullet points, and that caused a problem somehow. Ok...I discovered that if I do the autoreconf after the first failed make (and the autoreconf still gives that error message), and then do make again...it builds. Conclusions: 1) Autoreconf *must* be run, and not ./configure? I had thought that putting in my *.c

I have checked in a cleaned-up version of patch #302111 (Belkin support) into CVS. See cvs diff -uN -r before_PSE_2 -r after_PSE_2 to check the difference. Here is the CHANGES entry: Tue Sep 13 20:50:14 UTC 2005 / Peter Selinger <selinger@users.sourceforge.net> - newhidups: added Belkin support. Also added some new variables and instant commands (some of these were already used by

Hello, all, I had been using NUT's Ubuntu package (64 bit) with no problems until upgrading to Ubuntu 11.04. Now, I get the following message when I try usbhid-ups: $ sudo /lib/nut/usbhid-ups -a mybelkin Network UPS Tools - Generic HID driver 0.35 (2.6.0) USB communication driver 0.31 Can't claim USB device [050d:1100]: could not detach kernel driver from interface 0: Operation not

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: ########## - -