similar to: [nut-commits] svn commit r915 - in trunk: . drivers

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

Citeren Kjell Claesson <keyson-guest op alioth.debian.org>: > Author: keyson-guest > Date: Mon Mar 23 17:37:37 2009 > New Revision: 1817 > > Log: > data/driver.list, add Eaton Powerware 9130 compatibility with bcmxcp > and usbhid-ups. 1) Is this really true? I would have expected that this device would be supported through bcmxcp (serial) and bcmxcp_usb (USB), like

Hi Jordi, 2008/7/7 Jordi Mallach <jordi at debian.org>: > Package: nut > Version: 2.2.2-3 > Severity: important > > Hi Arnaud, > > I just tried backporting nut 2.2.2 to etch, and found the build fails > with: > > 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

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 :

Citeren Arnaud Quette <aquette.dev at gmail.com>: > Author: keyson-guest > Date: Wed Feb 4 15:03:36 2009 > New Revision: 1765 > > Log: > - Added mocrodowell.c/h into drivers/. add man/microdowell.8. Adjusted > drivers/Makefile.am and man/makefile.am. Adjusted the code for 2.4.0 in the > microdowell.c. Besides the things already mentioned by others and the obvious

Hi Kjell, a few notes: - you should bump the DRV_VERSION upon every change - you should track the drivers TODO list in a comment header (such as "implement smart load segment detection" completed with your info, ...). That would help to bootstrap new contributors. - you can also use the alioth trackers (features request, or task) to give some external visibility on what remains to be

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

As an experiment, I am attempting to build a more recent version of GNOME than 2.16.0 on CentOS 5.1. I've tried both garnome and jhbuild, and neither one works quite right. Jhbuild blows out looking for a dbus-glib-1 revision >= 0/74 (the release rev is 0.70), so I downloaded that and tried to build it. This results in the following error: gcc -g -O2 -Wall -Wchar-subscripts

I have a problem compiling Wine with Freetype. Not sure what to do: dpkg -i wine*.deb Code: checking for freetype-config... freetype-config checking for -lfreetype... not found configure: error: FreeType development files not found. Fonts will not be built. Dialog text may be invisible or unaligned. Use the --without-freetype option if you really want this. make: *** [config.status] Error 1

Hello I apologize in advance for my English. I compiled the new version of libvirt 1.2.8 on an environment Development Linux from Scratch with the following configure: configure: Configuration summary configure: ===================== configure: configure: Drivers configure: configure: Xen: no configure: QEMU: yes configure: UML: yes configure: OpenVZ: no configure: VMware:

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

Dear NUT developers, I am using NUT + bcmxcp + Powerware 9315. I would like to use NUT to shut down my systems if the air conditioning fails and the room get too hot. I want the same shutdown sequence as would be produced when the UPS goes on battery. The UPS has a terminal block at the front for up to six different 'building alarms'. I can connect a thermostat (35C) to the

I'm trying to compile GIT KWD, but i believe I am missing something here... joel at supernova:~/compiz/compiz$ make make all-recursive make[1]: Entering directory `/home/joel/compiz/compiz' Making all in include make[2]: Entering directory `/home/joel/compiz/compiz/include' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/home/joel/compiz/compiz/include'

> > The Buildbot has detected a new failure of Ubuntu-maverick-x86 on > Network UPS Tools. > Full details are available at: > http://buildbot.networkupstools.org/public/nut/builders/Ubuntu-maverick-x86/builds/32 > > Buildbot URL: http://buildbot.networkupstools.org/public/nut/ > > Buildslave for this Build: cayenne Fred, I had a few spare cycles and tried building

I get the following error on r809 (but it looks like the code change happened here). Does HIDDevice_t need to be defined/changed in one of the headers? if gcc -DHAVE_CONFIG_H -I. -I../../drivers -I../include -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 am trying to compile cairo-dock from source (failing to find an existing package for CentOS). I believe all dependencies are satisfied, but while doing "make", at some point it says (I can provide the full make output if it's needed): gcc -g -O2 -o cairo-dock -Wl,--export-dynamic cairo_dock-cairo-dock-callbacks.o cairo_dock-cairo-dock.o cairo_dock-cairo-dock-dbus.o

[was: svn commit r915 - in trunk: . drivers] Hi Kjell, sorry, I'm still much late in emptying my mail stack... 2007/5/25, Kjell Claesson <kjell.claesson at epost.tidanet.se>: > Den Friday 25 May 2007 08.52.20 skrev Arnaud Quette: > > > > I would be interested in some more info: > > - lshal -u <your device's UDI> > > the UDI can be obtained for ex.

Arjen de Korte wrote: > > + * drivers/apc-hid.c: > + - Commented out the 'fullycharged' status. If anyone can explain the > + use of this, please step forward. This flag is defined on p.36 of the "Universal Serial Bus Usage Tables for HID Power Devices", Release 1.0 November 1, 1997, a USB standards document available on the web. The document defines this

I'm trying to install Lords of The Realm II and while it doesn't affect whether or not you ca install the game, I have encountered two crashes if you allow the installer to test your system. The crashes occur when testing CDROM speed and when checking processor speed. CDROM speed test error: Code: 68 0x7eb1ee57 DispatchMessageW+0x103() in user32 (0x007fdff8) 69