similar to: nut 2.0.5-3+b1 reports low battery, previous versions do not

-> ups at p34 POWER ALERT on Sat Aug 25 07:40:01 EDT 2007 -> UPS belkin at localhost battery is low The last good version is 2.0.4, someone e-mailed me from this list before exactly why this happened it was about ignoring bad events from the usb-dev subsystem/kernel but I guess my question is this going to get fixed or should I stick with 2.0.4 as long as I can? Thanks. # ./usbhid-ups

Hello, http://lists.alioth.debian.org/pipermail/nut-upsuser/2007-September/003137.html http://lists.alioth.debian.org/pipermail/nut-upsuser/2007-July/003014.html http://permalink.gmane.org/gmane.comp.monitoring.nut.user/2552 I still have this problem: $ dpkg -l | grep -i nut ii nut 2.2.0-2 The core system I thought this bug was fixed :( syslog:Dec 10

Hello, Problem: When I migrated from a DG965WH -> DP55KG motherboard, there were quite a bit of issues, host still does not reboot without special flags, e.g. reboot=a, the NIC driver is broken with the in-kernel version (the one on e1000.sourceforge) fixes that and finally my UPS USB has driver stale problems, with two issues already relating to the HW/drivers themselves it would not be

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

When I disconnect my UPS from the wall, I have to wait 15-30 seconds before the USB drier 'polls' this information and tells me that the UPS is on battery power (via knutclient or syslog via nut): ups@p34 POWER ALERT on Fri Jan 26 12:49:29 EST 2007 With a serial connection, I would get the alerts IMMEDIATELY (0.5-1 seconds) after disconnecting the UPS. My new machine does not have a

Bus 003 Device 002: ID 050d:1100 Belkin Components # /lib/nut/usbhid-ups -a belkin Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.2.0-) No matching HID UPS found Hmm best to stick with 2.0.4. Justin.

Bus 003 Device 002: ID 050d:1100 Belkin Components # /lib/nut/usbhid-ups -a belkin Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.2.0-) No matching HID UPS found Hmm best to stick with 2.0.4. Justin.

Hi all. I would like to switch off my UPS once all upsmon clients have been disconnected from the upsd server, so that when power returns all the hosts connected to the ups will be powered up again. In the documentation it states that I should edit my shutdown scripts to add the command: /usr/local/ups/bin/upsdrvctl shutdown Unfortunately I don't know what file to add the command to.

Hello, I use the following in my ups.conf: # USB: [apc] driver = usbhid-ups port = auto desc = "APC 1500VA" pollfreq = 5 On my new motherboard (an Intel DP55KG), every once and awhile I get this: Broadcast Message from nut at box.com (somewhere) at 17:48 ... Communications with UPS apc at localhost lost Broadcast Message from nut at box.com

Dear List, This is just a programming problem which i cannot seem to figure out. I am trying to get a set of power from a test (say, kolmogorov smirnov) out of a distribution (say, G-K distribution) as follows. I am trying to reduce to pain of writing the whole set of data points (p# below) using "for" loop. However, I seem to have some problem in it as the output "M" does not

I looked through the faq, but couldn't find an answer to this. I'm trying to configure nut-2.0.4-26 on SuSE linux 10.2. In ups.conf, I have [myups] driver = belkinunv port = /dev/undefined desc = "Local UPS" I'm trying to find out what the port should be set to. lsusb shows: Bus 001 Device 005: ID 050d:0980 Belkin Components Device Descriptor: bLength

Dear Hyouko, Thank you very much ! Best regards, Bluefish -----????----- ???: hyouko at gmail.com [mailto:hyouko at gmail.com] ????: 2015?4?23? 7:25 ???: ??(bluefish_wei) ??: nut-upsdev at lists.alioth.debian.org ??: Re: [Nut-upsdev] How to upload new ups driver to NUT 2015-04-21 8:23 GMT+02:00 ??(bluefish_wei) <bluefish_wei at voltronicpower.com.cn>: > Can anyone tell me how to

Peter, Apparently, some Belkin UPSes still have problems with this. When we receive this report through the interrupt pipeline it is ignored (the special case in usbhid-ups.c) and even after that it looks like there are still some problems with it: http://lists.alioth.debian.org/pipermail/nut-upsuser/2007-July/003014.html Wouldn't it be an option to just to ignore this completely and

hi i have a belkin ups here some setting chmod 0600 /dev/hiddev0 chown nut:root /dev/hiddev0 linux:/home/sonia # /usr/lib/ups/driver/upsdrvctl start Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4) No matching USB/HID UPS found Driver failed to start (exit status=1) linux:/home/sonia # /usr/lib/ups/driver/upsdrvctl -u root start

I almost had nut_2.0.5-3_i386.deb (from http://packages.debian.org/unstable/admin/nut - installed via dpkg, not via repository) working: * problems with getting it to come up during boot * monitoring via knutclient was OK * shutdown on low battery worked adequately, if not quite as described) and newhidups suddenly stopped talking to my Belkin F6C550-AVR . It's only been in use for a

is there a way to override the productid (like -x productid=1234) when using newhidups? just thought i'd try it with the F6C1500-TW-RK over usb. i was able to get hidups to work using the below settings, but it provides limited information. my ups.conf entry: [belkin] driver = hidups port = /dev/usb/hiddev0 and the output of upsc: gateway:/etc/nut# upsc

In preparation for the klibc 2.0.5 release I wrote a basic test script which: 1. Builds for each architecture (with a cross-compiler where needed) 2. Runs several statically-linked programs (using qemu-user where needed): a. Many self-test programs b. "sh -c exit" c. "sh -c '.../bin/true; exit'" The results for the architectures I was able to test are:

Have had no issue until I ran apt-get dist-upgrade this morning: # /lib/nut/newhidups -u nut -DDDDDD auto Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5) debug level is '6' Checking device (0000/0000) (001/001) - VendorID: 0000 - ProductID: 0000 - Manufacturer: unknown - Product: unknown - Serial Number: unknown - Bus: 001 Trying to match device Device does not

Mr. Selinger, I'm CCing you directly since it appears (insofar as I can tell) that you are one of the delelopers for the newhidups driver. This is the third time I've submitted this (hence the CC this time). Hopefully mailman takes it. I've tweaked my SPF records, and I'm hoping that was the problem. My sincere apologies if this has gone through and I just haven't seen it