similar to: Configuring a server without an UPS attached

I'm sure I'm missing something, but I can't seem to get NUT working on FreeBSD. bryce at tahiti[/usr/local/etc/nut]>cat ups.conf [belkin] driver = usbhid-ups port = auto vendorid = 050d #productid = 0751 bryce at tahiti[/usr/local/etc/nut]>s /usr/local/libexec/nut/usbhid-ups -DDDDD -a belkin Network UPS Tools - Generic HID driver 0.34 (2.4.1) USB communication driver 0.31

Here are my permissions and user info. Let me know if there is anything else I should check pi at nutpi:~ $ ls -alt /etc/nut total 56 drwxr-xr-x 87 root root 4096 Jan 26 15:22 .. drwxr-xr-x 2 root nut 4096 Jan 26 13:53 . -rw-r----- 1 root nut 4719 Jan 26 13:15 upssched.conf -rw-r----- 1 root nut 15347 Jan 26 11:25 upsmon.conf -rw-r----- 1 root nut 1543 Jan 26 10:02 nut.conf -rw-r-----

Here is the output root at nutpi:/etc/nut# ps -elf | grep -E '[n]ut|ups[dms]' 4 S avahi 246 1 0 80 0 - 1472 poll_s Jan26 ? 00:00:31 avahi-daemon: running [nutpi.local] 1 S nut 451 1 0 80 0 - 678 poll_s Jan26 ? 00:03:41 /lib/nut/upscode2 -a deltec-PRA1500 1 S nut 454 1 0 80 0 - 1173 poll_s Jan26 ? 00:00:28 /lib/nut/upsd 1

Does anyone have a howto or documentation on how to add new drivers to the pxeboot initrd/kernel? It appears that although some newer dells (t300) have Broadcom NetXtreme IIs in them, 4.6 won't recognize them for some reason (possibly because they're dual port?) -Drew -------------- next part -------------- An HTML attachment was scrubbed... URL:

Compiling a simple automaton created by GNU bison with -O1 or -O2 resulted in the following machine code: 1300 /*-----------------------------. 1301 | yyreduce -- Do a reduction. | 1302 `-----------------------------*/ 1303 yyreduce: 1304 /* yyn is the number of a rule to reduce with. */ 1305 yylen = yyr2[yyn]; 0x0000000000400c14 <rpcalc_parse+628>: mov

The nut ups daemons seem to be communicating with the UPS but upscmd gives me no joy. Running commands do nothing and produce no output. Using the web interface returns an authentication failure and that is the only clue I have. I believe I have everything setup correctly but it's not working. Can someone review this and give me clues as to what I should research next?

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

Greetings all; Back to a thread I started back in May of 2008 I think. I never did get this belkin and nut to talking, so I thought I'd make another run at it. Trying to run the driver as the user gene, I'm getting this: --------------------------- [root at coyote ups]# su gene -c "/sbin/belkin -D -a myups" Network UPS Tools - Belkin Smart protocol driver 0.21 (2.2.2) debug

Hi I'm sending this to you as it appears that you are the person who looks after and/or supervises the code for NUT's Belkin drivers. I'm using the address you use for the Nut-upsdev mailing list ( selinger at mathstat.dal.ca ). Anyway... I have a Belkin Universal UPS and, having just upgraded my Fedora Core system from 4 to 5 and had to go back through the system RC files

Hi Arjen My apologies fro drifting off topic in the other mailing list...:-) On the bottom of the Belkin UPS unit - is the model number: F6C120auUNV The "au" is for Australia I think. "man belkinunv" states that F6C120-UNV is supported - and I assumed that the "au" would not prevent this. I plugged in the USB to gather the information you requested. My intention

Dean K. Gibson wrote: > > My Belkin UPS 1000 failed about a month ago; all of a sudden it > reported a battery failure. Since the Belkin logs showed this as in > instant transition from 99% to 22%, I assume a circuit board failure, > not a battery failure. Similarly, one Belkin UPS 500 circuit board > failed after I used my 100W amateur radio transmitter (not connected to

Hi On 10/02/2014 02:39 PM, Charles Lepple wrote:> On Oct 1, 2014, at 9:03 PM, paul.chavent at fnac.net wrote: > >>> It should run as user "nut" in Debian. You may want to reinstall the nut-server package, and check the post-inst error messages to make sure that the "nut" user is created, and that it is in the "nut" group as well. >> >> The

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

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

Hi. I have an improvement suggestion. Say that a careless user starts editing upsmon.conf before having read the complete documentation (not that I know of any such users of course) and starts by adding "RUN_AS_USER = nutmon" and then creates this user. Later he discovers that the rpm package already has created a "nut" user and therefore deletes the nutmon user but forgets to

Hi, I bought a Belkin Active Battery Backup UPS (http://www.belkin.com/uk/activebattery/) yesterday with a USB port and hoped it would work with nut. The device will show up in /proc/bus/usb/devices as a Cypress Semiconductor USB to Serial. It creates /dev/hiddev0 (and this disappears when the UPS is unplugged). I've tried using belkin, belkinunv, usbhid-ups and megatec_usb. I've tried

Hi Charles; I hope this finds you well. Here is dmesg output: gene at coyote:~$ dmesg |grep Belkin [ 3.315667] usb 2-3: Product: Belkin UPS [ 3.315669] usb 2-3: Manufacturer: Belkin [ 4.084258] generic-usb 0003:050D:0751.0009: hiddev0,hidraw4: USB HID v1.11 Device [Belkin Belkin UPS] on usb-0000:00:02.0-3/input I have configured it to use this generic-usb, and probably made it less

Hi, I've been fighting with trying to get a Belkin Universal model F6C800-UNV to work with NUT. The error I am getting is as follows: ---------------------------------------------- * Starting UPS drivers ... Network UPS Tools - UPS driver controller 2.0.0 Network UPS Tools - Belkin 'Universal UPS' driver 0.06 (2.0.0) tcgetattr(/dev/ups): Inappropriate ioctl for device Driver failed

On Sun, Mar 1, 2015 at 2:23 PM, Gene Heskett <gheskett at wdtv.com> wrote: > Hi Charles; I hope this finds you well. Hi Gene, > Here is dmesg output: > gene at coyote:~$ dmesg |grep Belkin > [ 3.315667] usb 2-3: Product: Belkin UPS > [ 3.315669] usb 2-3: Manufacturer: Belkin > [ 4.084258] generic-usb 0003:050D:0751.0009: hiddev0,hidraw4: USB HID v1.11 Device

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.