similar to: bcmxcp: stop whining (and log spamming)

* 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.

I noted some correspondence from several years back about supporting this device with bcmxcp, and the problems therein. Since I have one of these UPS units, still going strong, and the Eaton LanSafe stuff has finally caused me enough grief to abandon it, I figured I'd take a look at this. The issue is not that bad - the bcmxcp driver query of the topology block (2 bytes!) is returning

* 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

Network UPS Tools version 2.0.5 has been released. http://www.networkupstools.org/ Direct access: - Download: http://www.networkupstools.org/source/2.0/nut-2.0.5.tar.gz - News: http://www.networkupstools.org/source/2.0/new-2.0.5.txt - ChangeLog: http://www.networkupstools.org/source/2.0/ChangeLog

Network UPS Tools version 2.0.5 has been released. http://www.networkupstools.org/ Direct access: - Download: http://www.networkupstools.org/source/2.0/nut-2.0.5.tar.gz - News: http://www.networkupstools.org/source/2.0/new-2.0.5.txt - ChangeLog: http://www.networkupstools.org/source/2.0/ChangeLog

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 -

at least for an HP R3000XR with the 6-cereal card, the first CPU is said 6-port card, not the inverter. so get the firmware version from the last CPU, not the first. I wonder wether it makes more sense to store them all, aka ups.firmware.cpu0 etc. $OpenBSD$ --- drivers/bcmxcp.c.orig Wed Aug 23 11:16:01 2006 +++ drivers/bcmxcp.c Wed Aug 23 11:21:26 2006 @@ -742,10 +742,7 @@ void

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

On Sep 23, 2014, at 3:55 AM, Henning Brauer <hb-nut at bsws.de> wrote: > We have upd(4) attaching to these devices now. Either nut needs a > driver getting status from upd (trivial, will show up in the > hw.sensors sysctl tree) or we need some way for nut still being able > to talk to the ups directly, without upd and nut interfering with each > other. While a upd(4) driver

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

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

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;

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

Hi, Got this mail. It looks like he has a ups with revision before K, and need another startup. The 'PW_SET_REQ_ONLY_MODE' is not implemented, so to make it work we have to follow the protocol and send a 'PW_ID_BLOCK_REQ'. This in comsetup of bcmxcp_ser.c Also the standard id block ends with 'Statistics Map', so we have to Skip after reading the length of the 'Size

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

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 all! The following files emits warnings when compiled with gcc 4.0: al175.c bcmxcp_ser.c belkinunv.c cyberpower.c everups.c powercom.c solis.c All warnings seem to be of this variety: everups.c:38: warning: pointer targets in passing argument 2 of 'ser_get_char' differ in signedness I suggest that those who fiddles with those drivers fixes the warnings and verifies that it works

Is anyone besides me using gcc 4.*.*? I noticed that NUT generates an enormous amount of warning noise with that compiler, mostly due to implicit casts between signed/unsigned pointer types. Any volunteers to de-noise the code a bit? The easy way is to insert typecasts; the better way is to actually take care about signedness. -- Peter gcc -I../include -O -Wall -Wsign-compare -c -o everups.o