similar to: Common Power Management : NUT and HAL (stage 1)

I bought a new CyberPower CP850AVRLCD ups, connected it to a usb port and I'm trying to use it with hal. I installed [root at phoenix ~]# rpm -q nut nut-client nut-2.2.0-6.1.fc8 nut-client-2.2.0-6.1.fc8 lsusb sees it: [root at phoenix docs]# lsusb Bus 001 Device 001: ID 0000:0000 Bus 005 Device 002: ID 0c45:1050 Microdia Bus 005 Device 001: ID 0000:0000 Bus 004 Device 001: ID 0000:0000

I've tried several recipes found with google, but hal likes to grab the USB ups before nut can get it. There are a number of klugey workarounds, like turn off port power until ready to start nut (so that hal doesn't see the UPS). Or killall hal-addon-hid-ups before starting nut. Here is one of recipes I googled: https://github.com/sdgathman/trippfix/blob/master/halpolicy.fdi It

On 5/23/07, Kjell Claesson <keyson-guest at alioth.debian.org> wrote: > Author: keyson-guest > Date: Wed May 23 21:12:51 2007 > New Revision: 915 > > Log: > - Enabled requested Alarm function in bcmxcp.c > > Modified: > trunk/ChangeLog > trunk/drivers/bcmxcp.c Looks like this breaks when HAL is enabled. At the end of:

Charles, It looks like the buildbot no longer builds (if it ever did, I don remember) the HAL addons, even if the requirements are met: configure:9680: checking for libhal version via pkg-config (0.5.8 minimum required) configure:9690: result: 0.5.11 found configure:9694: checking for libhal cflags via pkg-config configure:9703: result: -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/hal

Network UPS Tools version 2.4.3 has been released. http://www.networkupstools.org/ Note: this is only a bugfix release that only solves the regression on IPv6 activation. Direct access: - Download: http://www.networkupstools.org/source/2.4/nut-2.4.3.tar.gz - News: http://www.networkupstools.org/source/2.4/new-2.4.3.txt - ChangeLog: http://www.networkupstools.org/source/2.4/ChangeLog the NUT

Ladies and Gentlemen, I have been playing around with Arnaud's new HAL stuff a bit, and have some questions and observations. First my configuration: my UPS (Peter may remember): ups.mfr: APC ups.model: Back-UPS ES 650 ups.productid: 0002 ups.firmware: 818.w1.D ups.firmware.aux: w1 kernel: 2.6.18-92.1.6.el5 hal-0.5.8.1-35.el5, nut based on nut-2.2.2.tar.gz, small changes to

Greets all; I was just booted to mdv-2010-x64 where I found my lack of sound problems. Whoopy ding... But when I rebooted to fedora, now the driver cannot disconnect and gain access to the ups. I installed the 52-nut udev file in /etc/udev.d, and it reads that it should setup /dev/hiddev0 like this and with 0664 perms when it finds that ups: crw-rw-r-- 1 root nut 180, 0 2010-01-03 20:51

Hi fellows, As the NUT-NG draft will take me more time than I currently have (I found myself too optimistic since I got a baby ;-), below is the beginning of an answer to the "Common Power Management with UPS support" problem... First, NUT is pure userspace code, for portability issue, and will remain. USB is through libusb, snmp through net-snmp and serial through standard read/write.

Hi again, I've succeeded in compiling the svn trunk with the automake tools and wish to say thank you to Charles Lepple for his help. After fixing some parameters in the hotplug script I can now get access to the UPS on /dev/usb/hiddev0 (I added productid and vendorid of my ups to the usermap). I've decided to try the newhidups driver with -x generic parameter and got this response :

Hi Dave and HAL fellows, 2007/3/30, David Zeuthen <david@fubar.dk>: > > Hi! > > On Fri, 2007-03-30 at 11:22 +0200, Arnaud Quette wrote: > > I would really need an "addondir" variable in hal.pc to get to exact > > path to install the NUT addons... > > I just clarified this in the spec with this commit > >

Hi All, I've been trying to trace the cause of a hang on a 5.6 i386 system. After running for almost a year, it hung last week, when I plugged in a screen it was blank, machine was unresponsive to the keyboard, over the network ssh and other daemons didn't respond but the thing has two network cards and routing from one to the other was still working. So the kernel was up and I

On Feb 1, 2008 6:11 PM, Arnaud Quette <aquette at alioth.debian.org> wrote: > Author: aquette > Date: Fri Feb 1 23:11:33 2008 > New Revision: 1264 > > Log: > fix HAL support installation [Alioth Bug #304156] Arnaud, I tried to fix some of the errors that I was seeing in buildbot, but I still get the following error on "make distcheck", and I don't know how

Seems to be broken in the current SVN: [...] x86_64-linux-gnu-gcc -I../include -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/hal -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -DINET6 -O2 -D_REENTRANT -DNETSNMP_USE_INLINE -Wall -Dlinux -I. -I/usr/include -O2 -Wall -Wsign-compare -s -o energizerups energizerups.o ../common/upsconf.o ../common/parseconf.o ../common/state.o main.o dstate.o

On 11/13/2016 10:08 AM, Charles Lepple wrote: >> Here is one of recipes I googled: >> https://github.com/sdgathman/trippfix/blob/master/halpolicy.fdi > What if you convert the USB ID numbers to decimal? > > <match key="@info.parent:usb.vendor_id" int="2748"> > <match key="@info.parent:usb.product_id"

Hi David and fellows, I'm reviving this important thread about a common power management. To sum up, the first aim is to allow a better user experience on Linux by bridging NUT with Linux HAL, and Gnome Power Management / any PM GUI. But it also initiate a bigger investigation about how to integrate NUT support for UPSs into the native OS Power Management infrastructure for all supported

some notes: - for this kind of discussion, please cc upsdev list (I've added it), - I've fwded the full thread to upsdev, - this subject is part of what I call NUT-NG (next gen.), aka nut 3.0... - I'll study in depth the thread this week end, and complete with my thoughts, - thanks to Stan to have put us all in touch Arnaud 2006/3/10, Stanislav Brabec <sbrabec@suse.cz>: >

Hi, I was fooling around with the bcmxcp driver and enabling the alarm functions. I hade tested this on some of the ups'es so I was planning to submit it to the svn trunk. But, as the bcmxcp is shared code for serial and usb I got a problem. When enabling --with-hal it halt on the build of hald-addon-bcmxcp_usb. -------------------------------------------------------------- gcc

make fails at drivers: make[1]: Entering directory `/export/home/zoly/Documents/trunk/drivers' /bin/sh ../libtool --tag=CC --mode=link gcc -I../include -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/hal -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/sfw/include -g -Dsolaris2 -I. -I/usr/sfw/include -O -Wall -Wsign-compare -o al175 al175.o ../common/libcommon.a ../common/upsconf.o

Hi, is there anybody understanding HAL? I use CentOS 4 (RHEL 4) I need set specific mount options for USB flash disk. I found I can do it in /usr/share/hal/fdi/95userpolicy/storage-policy.fdi <?xml version="1.0" encoding="ISO-8859-1"?><!-- -*- SGML -*- --> <deviceinfo version="0.2"> <device> <match key="volume.fstype"

My UPS Powercom WOW-1000U does greatly work with NUT, but not auto-cofigurable... This UPS is not usb-hid ups, and works well with this settings in NUT: [powercom] desc = "powercom" driver = powercom port = "/dev/serial/by-id/usb-POWERCOM_CO.__LTD._USB_to_Serial-if00-port0" type = IMP lsusb -v fragment attached. Unlike other UPSes, gnome-power-manager does