similar to: using upscode2 driver with Powerware 5119 RM

----- Doorgestuurd bericht van dkbrig at gmail.com ----- Datum: Thu, 29 Jan 2009 11:16:06 -0600 Van: Danny <dkbrig at gmail.com> Onderwerp: upscode2.c Aan: adkorte-guest at alioth.debian.org Hi, I apologize if you are not the correct person, but I was wanting to submit a bug report for the upscode2.c driver but could not find a way to do that from the NUT website.

On 7/5/23 03:17AM, Jim Klimov wrote: > Ah, I thought you missed in my earlier reply the part about a bug with debug printouts in 2.8.0 (fixed on master since), > did not comment on that when you replied with quoting... So, for now options are to bump debugging to 3+ or to build > your own in one of many ways possible :\ I think I'm not following you - with debug 3 -->> it

Hi, Am 13.02.2012 um 18:58 schrieb Arnaud Quette: > 2012/2/6 thomas schorpp <thomas.schorpp at googlemail.com>: >> Hi, > > Hi Thomas, > >> I want the driver report the battery status from ABM charging controllers >> -patch attached- : > > For now, I've tracked your patch here: >

2012/2/6 thomas schorpp <thomas.schorpp at googlemail.com>: > Hi, Hi Thomas, > I want the driver report the battery status from ABM charging controllers > -patch attached- : thanks for your patch. since it introduces a new variable (battery.status.abm), I prefer to step back and think to something useful more widely. thus, I'm thinking about a generic

Ah, I thought you missed in my earlier reply the part about a bug with debug printouts in 2.8.0 (fixed on master since), did not comment on that when you replied with quoting... So, for now options are to bump debugging to 3+ or to build your own in one of many ways possible :\ On Wed, Jul 5, 2023, 06:23 Karl Schmidt <karl at lrak.net> wrote: > On 7/4/23 10:01PM, Jim Klimov wrote: >

>Da: hfinkel at anl.gov >Data: 02/12/2011 16.27 >A: "acrux_it at libero.it"<acrux_it at libero.it> >Cc: <llvmdev at cs.uiuc.edu> >Ogg: Re: [LLVMdev] LLVM-3.0 fails to build on linux ppc32 > >On Fri, 2011-12-02 at 09:15 -0600, Hal Finkel wrote: >> On Fri, 2011-12-02 at 06:58 -0600, Hal Finkel wrote: >> > Nico, >> > >> >

On Fri, 2011-12-02 at 20:18 +0100, acrux_it at libero.it wrote: > >Da: hfinkel at anl.gov > >Data: 02/12/2011 16.27 > >A: "acrux_it at libero.it"<acrux_it at libero.it> > >Cc: <llvmdev at cs.uiuc.edu> > >Ogg: Re: [LLVMdev] LLVM-3.0 fails to build on linux ppc32 > > > >On Fri, 2011-12-02 at 09:15 -0600, Hal Finkel wrote: > >>

Author: anish Repository: /hg/zfs-crypto/gate Revision: ca260b8c8934dc34091622676f0a58662e217e74 Log message: 6352071 MDB ::interrupts need not display non-ISR entries on x86 6354060 Add ::interrupts support for uppc(7d) based systems Files: create: usr/src/cmd/mdb/i86pc/modules/uppc/Makefile create: usr/src/cmd/mdb/i86pc/modules/uppc/amd64/Makefile create:

On Feb 19, 2014, at 12:50 PM, Ted Mittelstaedt wrote: > Worse, however, is if there's a power failure right near the end > of the 2-days-off cycle. That happened to me last week - it was a > short duration 15 second loss - and the upscode2 driver decided it needed to issue a forced shutdown. > > Very likely this was because upscode2 had decided the batteries > were

Author: anish Repository: /hg/zfs-crypto/gate Revision: dd242801250e0f77ff81a2cde19ac40dec0d88af Log message: 6427444 add ::softint support for x64 Files: update: usr/src/cmd/mdb/common/mdb/mdb_ks.h update: usr/src/cmd/mdb/common/modules/mdb_ks/mdb_ks.c update: usr/src/cmd/mdb/i86pc/modules/pcplusmp/apic.c update: usr/src/cmd/mdb/i86pc/modules/uppc/intr_common.c update:

On 2/20/2014 6:55 AM, Charles Lepple wrote: > On Feb 19, 2014, at 12:50 PM, Ted Mittelstaedt wrote: > >> Worse, however, is if there's a power failure right near the end of >> the 2-days-off cycle. That happened to me last week - it was a >> short duration 15 second loss - and the upscode2 driver decided it >> needed to issue a forced shutdown. >> >>

My UPS is an Exide NetUPS SE PRC1500i (1500 VA), also known as Powerware 5119, according to Karl Schmidt (http://lists.alioth.debian.org/pipermail/nut-upsuser/2005-July/000026.html) also Deltec PowerRite Pro II, and according to http://www.usedups.de/compaq_ups.html also Compaq R3000h. I am not sure if the information in http://www.bps.hu/powerware/model_en.html is to be interpreted as that it was

My UPS is an Exide NetUPS SE PRC1500i (1500 VA), also known as Powerware 5119, according to Karl Schmidt (http://lists.alioth.debian.org/pipermail/nut-upsuser/2005-July/000026.html) also Deltec PowerRite Pro II, and according to http://www.usedups.de/compaq_ups.html also Compaq R3000h. I am not sure if the information in http://www.bps.hu/powerware/model_en.html is to be interpreted as that it was

Hi All, I have what is probably a 12 year old (or older) Compaq R3000 UPS plugged into a FreeBSD 8 system running NUT version 2.6.5 This UPS contains a total of 16 batteries in 2 banks of 8, each battery is 6 volts and the bank produces 50 volts. The UPS monitors battery voltage and the battery charger in the UPS works like this. For about 2 days it will apply a charge/float/topping

Timo, thanks for writing and releasing Dovecot. I've recently discovered it and have been very impressed at the speed and balance between flexibility and simplicity. I had to make a packet-trace to be sure that encryption with OpenSSL was working correctly, since it all 'just worked' first time without complex configuration, which I don't think I've ever seen before ;-) LDAP

Ok - I'm wondering is this is a systemd config bit? systemctl restart nut-driver at malaysia.service Job for nut-driver at malaysia.service failed because the control process exited with error code. See "systemctl status nut-driver at malaysia.service" and "journalctl -xeu nut-driver at malaysia.service" for details. root at malaysia:~# systemctl status nut-driver at

Normally yes - enable and start the target and the particular services relevant to your setup. For the binary you have from packaging (if not rebuilt as suggested earlier), set debug_min=3 in ups.conf section for upscode2, to currently trade driver viability for some storage traffic with more logs :\ Sorry about that, Jim On Wed, Jul 5, 2023, 02:29 Karl Schmidt <karl at lrak.net> wrote:

On Fri, 2011-12-02 at 06:58 -0600, Hal Finkel wrote: > Nico, > > There is a third place that '#undef PPC' is needed (at the top of > PPCFixupKinds.h). Alternatively, you can run configure with -UPPC in > your CPPFLAGS. I'll try to get this fixed in trunk shortly. I just tested this, and I was wrong: passing -UPPC to configure in CPPFLAGS does not work for some reason.

On 7/4/23 10:01PM, Jim Klimov wrote: > Normally yes - enable and start the target and the particular services relevant to your setup. > > For the binary you have from packaging (if not rebuilt as suggested earlier), set debug_min=3 in ups.conf section for > upscode2, to currently trade driver viability for some storage traffic with more logs :\ > > Sorry about?that, > Jim

On Fri, 02 Dec 2011 13:23:07 -0600 Hal Finkel <hfinkel at anl.gov> wrote: _omissis__ > > > > ciao Hal, > > thanks a lot for your support. > > i'll try your last suggestion. > > > > Btw, adding -UPPC to my system cxx flags i.e.: > > export CXXFLAGS="$CXXFLAGS -UPPC" > > > > i got, instead, some tests error: > >