similar to: USB/UPS connectivity issue on Intel DP55KG Motherboard

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

Hi gang, I have the APC BR1500LCD [1] and would like to know if NUT can handle it. The compatibility list [2] does not show it but I thought that perhaps it would fit in as some other unit. Does anyone else have this unit? [1] http://www.apc.com/resource/include/techspec_index.cfm?base_sku=BR1500LCD [2] http://www.networkupstools.org/compat/stable.html -- /jm

Hi all, I've not been able to find the answer to my timer problem in the faq or the archives. (or google) Basically, I can't get timers to fire. They fire ignoring the timer value, as if the timer was set to 0. I'm using the OpenFiler distribution, patched to the latest and greatest. upsmon 2.2.2 When I pull the power plug, I see the text "Im In Battery" instantly, instead

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

Package: nut Version: 2.0.5-3+b1 Running: Debian Testing Arch: x86_64 BUG: (the battery is relatively new (6mos) and there have been no recent power outages) Jul 28 04:29:44 p34 upsmon[2402]: UPS belkin at localhost battery is low Jul 28 05:13:15 p34 upsmon[2402]: UPS belkin at localhost battery is low Jul 28 05:14:05 p34 upsmon[2402]: UPS belkin at localhost battery is low FIX: (go back to

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

Which among these three motherboard is the best supported in Linux (Centos/Ubuntu) ? Intel? Desktop Board DH55HC [ http://ark.intel.com/Product.aspx?id=42409 ] Intel? Desktop Board DP55WG [ http://ark.intel.com/Product.aspx?id=40078 ] Intel? Desktop Board DP55KG [ http://www.intel.com/products/desktop/motherboards/DP55KG/DP55KG-overview.htm] Also which will be a good processor , for using

Hello, is there a way to query from the cmdline if the UPS data is stale? "upsc" outputs a lot of information, but not if the data is stale. Example output from a "stale" UPS on the server: (nut version: nut-2.7.2-3.el7) # upsc apcsmart battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 50 battery.mfr.date: 2014/09/01 battery.runtime: 1320

I see this in syslog: Aug 12 03:57:22 orion upsd[18274]: Data for UPS [a102-apc-10] is stale - check driver (one for each UPS). Then I see a bunch of messages like this: Aug 12 03:58:02 orion upsd[18274]: write() failed for ::1: Broken pipe Aug 12 03:58:02 orion snmpd[2872]: Connection from UDP: [127.0.0.1]:50940 And then it returns to normal like this: Aug 12 03:58:04 orion upsd[18274]: UPS

APC Smart-UPS X 1500 Restart Issue. Hi All, I have installed nut-2.4.3. I have manually modified the files apc-hid.c and udev-rules to support 5G APC UPS. I took sample code from the 2.5 development tree. Shutdown process is working very well -- upsmon creates the file /etc/killpower - shutdown script checks for the file and issues /sbin/upsdrvctl shutdown - UPS cuts the power off. All

APC Smart-UPS X 1500 Restart Issue. Hi All, I have installed nut-2.4.3. I have manually modified the files apc-hid.c and udev-rules to support 5G APC UPS. I took sample code from the 2.5 development tree. Shutdown process is working very well -- upsmon creates the file /etc/killpower - shutdown script checks for the file and issues /sbin/upsdrvctl shutdown - UPS cuts the power off. All

Hallo, Following the tips found at https://calomel.org/nut_ups.html I was trying to make NUT operate "APC Back UPS CS-350". The device introduces itself as: #v+ ugen0 at uhub0 port 1 "American Power Conversion Back-UPS CS 350 FW:807.q7.I USB FW:q7" rev 1.10/0.06 addr 2 #v- My config: #v+ [apc] driver = usbhid-ups port = /dev/ugen0.00 pollfreq =

Hallo, Following the tips found at https://calomel.org/nut_ups.html I was trying to make NUT operate "APC Back UPS CS-350". The device introduces itself as: #v+ ugen0 at uhub0 port 1 "American Power Conversion Back-UPS CS 350 FW:807.q7.I USB FW:q7" rev 1.10/0.06 addr 2 #v- My config: #v+ [apc] driver = usbhid-ups port = /dev/ugen0.00 pollfreq =

Linux NUT 2.7.1 Eaton 5PX usbhid-ups It would appear that interrupts are not actually working on my 5PX using the usbhid-ups driver. I will be trying the serial mge-shut driver next. It just seemed like it was working before because of the default pollinterval of 2 seconds. The status update comes in during the pollinterval no matter what I have pollfreq set to. And I can set pollonly and

W dniu 22.08.2018 o 14:41, Charles Lepple pisze: > /lib/nut/usbhid-ups -a apc -DDD -k Please see attachement. -- Karol Olszewski ipflow.pl -------------- next part -------------- A non-text attachment was scrubbed... Name: APC_BackUPS_CS_650_fsd.log.gz Type: application/gzip Size: 5735 bytes Desc: not available URL:

I have an APC USB UPS that was working on OpenBSD 5.5 with NUT 2.7.1 When I installed the latest 5.6 snapshot with NUT 2.7.2 the UPS no longer sends status messages when it loses line power. I asked over on the OpenBSD ports list and so far haven't had any luck getting this to work again. I disabled upd at boot as was suggested and that didn't change anything except stopping the

On 1/31/15, Charles Lepple <clepple at gmail.com> wrote: > On Jan 31, 2015, at 3:09 PM, Melvin Call <melvincall979 at gmail.com> wrote: > >> One last question if you don't mind. I noticed the "default" POWERDOWNFLAG) >> is >> set to /etc/killpower, but I changed that to /tmp and modified my >> umountroot >> script to mount it read only

On Sep 11, 2014, at 9:48 PM, Stan Gammons <sg063015 at gmail.com> wrote: > I have an APC USB UPS that was working on OpenBSD 5.5 with NUT 2.7.1 When I installed the latest 5.6 snapshot with NUT 2.7.2 the UPS no longer sends status messages when it loses line power. I asked over on the OpenBSD ports list and so far haven't had any luck getting this to work again. I disabled upd at

On Feb 1, 2015, at 7:04 AM, Melvin Call <melvincall979 at gmail.com> wrote: > Thank you Charles, for the assistance and the information. Everything is > completely functional here now. Not sure if the APC BackUPS ES550 is on the > list of compatible devices, but it works just fine with the usbhid-ups driver, > and supports several basic commands. You're welcome! We do have

On Sunday 08 December 2019 21:48:03 Charles Lepple wrote: > On Dec 7, 2019, at 7:01 PM, Gene Heskett <gheskett at shentel.net> wrote: > > What driver do I now put in /etc/nut/ups.conf? hid-generic doesn't > > seem to want to talk to it, and the original name _(usbhid-ups) > > doesn't work from new mobo. Oh wait, I can't spell. But that didn't > >