similar to: Network UPS Tools version 2.0.5 released

hello everyone, I've been testing the NUT solution as opposed to the undocumented LanSafe application to control my Eaton UPS. I am on a Slackware 13.37 system with a 2.6.37.6 kernel. NUT version is 2.4.3 . I installed the tarball by compiling it directly on my system (as a slackbuild package). The UPS is an Eaton Powerware 9155, but I don't know how to obtain the manufacturing date. The

Fellows, time has come for a new NUT release: I'm planning on 2.6.1 next week (max Friday 27), and I'm currently processing remaining patches. If you have some more on your side, please send in. cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer -

Hi All, I'm a system administrator of a large data center, and I've recently replaced the machine that acted as the nut master for our cluster/cloud. The machine that was interfacing with our Powerware 9135 450KVA 3 phase UPS, not to confused with Eaton's Powerware 9135, and was a Fedora Core 4 box running nut version 2.0.3-4 connected by a serial cable. We are using these versions

Hi All, I'm trying to communication with the HP r3000 XR UP using the latest stable build and I'm getting the following errors. Can anyone enlighten me with the errors below and what other course of action I can take. Thanks in advance. Paul. [root@WRRFtpServer etc]# /usr/local/ups/bin/upsdrvctl start Network UPS Tools - UPS driver controller 2.0.5 Network UPS Tools - BCMXCP UPS

* Charles Lepple <clepple at gmail.com> [2014-09-20 01:12]: > On Sep 19, 2014, at 5:18 PM, Stan Gammons <sg063015 at gmail.com> wrote: > > Looks like this patch fixed the problem. I see the status change now. > Good to hear. > I'm not familiar with the OpenBSD release process. Is that patch on track to be a part of the final 5.6 release? no, 5.6 is already cut.

Hello there. I use Online Xanto ups'es so I did some googling for their support in nut. Turns out that... - networkupstools.org talks about an 'optiups' driver in the development version (http://www.networkupstools.org/compat/dev.html - by the way, the web page says 'stable' in the title and headings just like the actual stable one) - Andreas Thienemann seems to have a

corrupted checksums happen all the time with the 6-port serial card, even when only using one port (and I don't give a shit about the other ports, if anybody has a one-port laying around...) so stop whining already. $OpenBSD$ --- drivers/bcmxcp_ser.c.orig Wed Aug 23 11:15:54 2006 +++ drivers/bcmxcp_ser.c Wed Aug 23 11:26:37 2006 @@ -168,8 +168,8 @@ int get_answer(unsigned char *data, unsi

Hi, So far I've gleaned heaps of useful info from the list and got mostly running with NUT. There was a thread by Paul Battaglia and Kjell Claesson about the R3000 which has helped me get so far, but now with the patched driver I still have this on startup: # /usr/local/ups/bin/upsdrvctl start Network UPS Tools - UPS driver controller 2.0.5 Network UPS Tools - BCMXCP UPS driver 0.11

On 1/23/07, Henning Brauer <hb-nut@bsws.de> wrote: > good new first: the megatec driverin 2.0.5 now works with the Online > Xanto S3000R here - well, for the very basics. > > the UPS has NO way ofidentifying itself. It also does not respond to > the power ratings query ("F"). I previously used a hacked up fentonups > driver. This means the driver cannot figure out

Hi, I have an HP R5500XR and a Compaq R3000XR that I would like to use with nut. I searched the compatibility lists and the mail list archives but couldn't find anything. They both have 9 pin serial ports. Can anyone give me any information about them, and if they are supported by nut? Thanks, Denny Fox

Hi developers, I would like to propose making a release soon from the current NUT trunk. There have been a lot of important changes since 2.0.5: new drivers added/refined (e.g. megatec_usb); the switch to Automake; the renaming of newhidups to usbhid-ups; automatic installation of hotplugging files; IPv6 support; improvements to the tripplite_usb driver; improvements to the gamatronic driver;

Good morning, i have an Xanto S1000 USV the Manufactor is ONLINE USV-Systeme AG. I tried all the buildin drivers, also the driver for the driver for the Generic UPS, nothing worked for this UPS so now my question has anyone else this UPS and functional driver? Thanks and Greets Dennis

On Sep 19, 2014, at 5:18 PM, Stan Gammons <sg063015 at gmail.com> wrote: > Looks like this patch fixed the problem. I see the status change now. Good to hear. I'm not familiar with the OpenBSD release process. Is that patch on track to be a part of the final 5.6 release? -- Charles Lepple clepple at gmail

* Henning Brauer <hb-nut at bsws.de> [2014-09-20 13:39]: > * Charles Lepple <clepple at gmail.com> [2014-09-20 01:12]: > > On Sep 19, 2014, at 5:18 PM, Stan Gammons <sg063015 at gmail.com> wrote: > > > Looks like this patch fixed the problem. I see the status change now. > > Good to hear. > > I'm not familiar with the OpenBSD release process. Is

On 09/19/14 07:23, Charles Lepple wrote: > On Sep 19, 2014, at 7:26 AM, Stan Gammons <sg063015 at gmail.com> wrote: > >> --enable-debug-log was in the original makefile. I added --enable-debug. At this point I guess trying to build from source or go back to OpenBSD 5.5 are the only options left. > Ah, my confusion was that --enable-debug-log was wrapped in ".ifdef

Hello... I have a PowerWare 9120 attached via USB to my Debian system. My ups.conf looks like this: [ups1] driver = bcmxcp_usb port = auto desc = "PowerWare 9120" When testing the driver with "upsdrvctl -u root start" I get: Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools - BCMXCP UPS driver 0.10 (2.0.4) Communications with UPS

Hi all, I just acquired a new UPS and have been trying to get it to work with NUT. It's an Eaton/Powerware 9120 700i with both USB and RS-232 interfaces. I first tried the USB interface (using bcmxcp_usb) and found that the UPS worked fine for a few minutes but then NUT lost communication and didn't get it back. In addition the UPS itself seemed to lock up at one point such that the

OK, I have removed the autoconf test for s6_addr32 (which is no longer used), and wrote a new test for IN6_IS_ADDR_V4MAPPED. The latter is probably portable, but since we're already in the business of testing, it does not hurt to do so. Arjen, I wonder about server/access.c, line 60-61: return (IN6_IS_ADDR_V4MAPPED(ip6) && ((((const u_int32_t *)ip6)[3] &

Hi! I am trying to get an Atlantis-Land 1501 UPS to work under OpenBSD. The UPS works OK under Linux + megatec_usb driver+nut_2.2.2. What I get under OpenBSD is: root at puffwall:~ # dmesg OpenBSD 4.3 (GENERIC) #698: Wed Mar 12 11:07:05 MDT 2008 deraadt at i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium III ("GenuineIntel" 686-class, 128KB L2

Hi! I am trying to get an Atlantis-Land 1501 UPS to work under OpenBSD. The UPS works OK under Linux + megatec_usb driver+nut_2.2.2. What I get under OpenBSD is: root at puffwall:~ # dmesg OpenBSD 4.3 (GENERIC) #698: Wed Mar 12 11:07:05 MDT 2008 deraadt at i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium III ("GenuineIntel" 686-class, 128KB L2