similar to: Preparing the 2.0.3-pre2 release

On 10/1/05, Arnaud Quette <aquette.dev@gmail.com> wrote: > I've decided, as an exception (the second with the ones for 2.0.2, > but hey, nut has a lot of late to resorb) to merge the USB > improvements from the CVS Development branch. I took a look at backporting tripplite_usb to Testing. I don't see the regex matcher, though. Do we want to merge that, too? Or should I

Peter, attached is a proposed patch to fix compilation of generic-hid.c when libusb's usb.h is not in /usr/include (but the -I flag is provided by "libusb-config --cflags"). It fixes the build under OS X, where Fink installs libusb with --prefix=/sw. I changed "usb.h" to <usb.h> so that 'make depend' wouldn't generate a dependency on 'usb.h' with

[I'm switching my dev address to @gmail.com instead of @mgeups... please, update your bookmark] Peter Selinger wrote: > > Arnaud Quette wrote: > > > > Here is the status of PSE (Peter Selinger) NUT patches > > for newhidups (hidparser, apc support, ...). > > > > - nut-cvs-patch-REOPEN-2005-08-24: > > approved and applied on Development tree > >

Hi there, [ http://www.contribs.org/bugzilla/show_bug.cgi?id=654 ] I just received this: Broadcast message from nut (Sat Feb 4 04:02:45 2006): UPS UPS@localhost battery is low and Feb 4 04:02:45 bigted upsmon[11532]: UPS UPS@localhost battery is low Feb 4 04:02:45 bigted wall[4032]: wall: user nut broadcasted 1 lines (34 chars) but I believe this looks o.k., except for the input voltage

Hi there, I'm trying to track down a problem with said combination. Broadcast message from nut (Thu Jan 26 13:22:06 2006): Communications with UPS UPS@localhost lost Broadcast message from nut (Thu Jan 26 13:22:11 2006): UPS UPS@localhost is unavailable "newhidups -DDD hiddev0" seems happy enough, as does "upsd -DDD -f" - at least until I start upsmon. Then I

Hi, I need to get a USB based UPS for a system which is running NUT 2.0.4 (a Debian Etch system). Does anyone know of a UPS that I can buy today that is supported by 2.0.4? Unfortunately upgrading the OS (and NUT) isn't an option. Previously, we used the Powerware 5110 (which used the bcmxcp_usb driver) and that worked fine, however that UPS has been discontinued and is no longer

--- Arjen de Korte <nut+users at de-korte.org> wrote: > > > I also did: > > > > # ./megatec_usb -DDDDD -x vendor=06da -x mfr=OMRON > > /dev/usb/hiddev0 > > Please have a look at 'man 8 megatec_usb' again. > > You probably need to specify the '-x vendorid' and > '-x productid' options > and most likely, the

--- Arjen de Korte <nut+users at de-korte.org> wrote: > > > I also did: > > > > # ./megatec_usb -DDDDD -x vendor=06da -x mfr=OMRON > > /dev/usb/hiddev0 > > Please have a look at 'man 8 megatec_usb' again. > > You probably need to specify the '-x vendorid' and > '-x productid' options > and most likely, the

Hi fellows, I'm really pleased to announce that a first stage of NUT and HAL [1] integration has been reached: NUT drivers (in fact, only newhidups, tripplite_usb and bcmxcp_usb for the moment) can feed HAL data. It's a "quick and dirty" hack, as a proof of concept, and there is still lots of things to be done, both on NUT and HAL sides. But it's a good base, and very

I have an FC5 system with a powerware 5110 usb ups. The system seems to find the UPS ------------------------------ [root@b1 src]# lsusb Bus 004 Device 001: ID 0000:0000 Bus 003 Device 002: ID 0592:0002 Powerware Corp. Bus 003 Device 001: ID 0000:0000 Bus 002 Device 001: ID 0000:0000 Bus 005 Device 001: ID 0000:0000 Bus 001 Device 001: ID 0000:0000 ------------------------------- [root@b1

Hi, I have got a Powerware 5110 UPS which has a usb interface on it. I have downloaded and compiled nut-2.0.3-pre2 with the usb drivers enabled on RedHat Enterprise V3 however I have been unable to get nut to connect to the UPS. I have tried executing the driver directly (using bcmxcp_usb -DD -u root /proc/bus/usb/002/002) as well as using upsdrvctl with the port set to auto (am I correct in

Hi, I'm having a hard time configuring a Mustek Powermust 600VA ups to work via USB with nut. I read somewhere that nut works OK via the rs232 cable, but unfortunately I don't have a COM port in my computer. The kernel detects the ups as an Xbox pad :) and loads the xpad module. I tried running /lib/nut/megatec with different /dev/ttySx but it displays megatec protocol UPS was not

Is there a particular reason why we are setting the alternate interface to 0 in drivers/libusb.c? I have seen some documentation which indicates that this should already done by the OS when the device is enumerated. If that is the case, then there is no reason why we should hardcode the alternate interface to 0. If I remove the following code, tripplite_usb seems to work*:

Hi there, I'm one of the maintainers of the SME Server distro (www.contribs.org) and we've been chasing this one for some time: http://www.contribs.org/bugzilla/show_bug.cgi?id=352 http://lists.alioth.debian.org/pipermail/nut-upsdev/2006-January/000543.html Many thanks to Peter Selinger and everyone else who helped with the debugging and patches. Thanks, Gordon

The -pre2 version of HDT 0.3.6 is out. Gert was a great source of motivation for making that -pre2. He found many bugs and gave nice ideas. Thanks Gert for your time and your _many_ tests. This release will be more or less what will be included in the incoming syslinux 3.84. Since -pre1, here come the Changelog * Reporting CPU L1 & L2 cache * Report "Hw.Virt" in cpu

The -pre2 version of HDT 0.3.6 is out. Gert was a great source of motivation for making that -pre2. He found many bugs and gave nice ideas. Thanks Gert for your time and your _many_ tests. This release will be more or less what will be included in the incoming syslinux 3.84. Since -pre1, here come the Changelog * Reporting CPU L1 & L2 cache * Report "Hw.Virt" in cpu

Good evening, I tried getting this to work a couple years back but didn't have enough time to do all the debugging that was needed (apologies to the devs who tried to help at that time). It's working much better now, but I'm still not able to get an answer from upsc. Can anyone help me work out why I'm getting the error when querying with upsc: Error: Data stale My

Good evening, I tried getting this to work a couple years back but didn't have enough time to do all the debugging that was needed (apologies to the devs who tried to help at that time). It's working much better now, but I'm still not able to get an answer from upsc. Can anyone help me work out why I'm getting the error when querying with upsc: Error: Data stale My

I'm trying to see if we can make upsd autodetect the driver sockets from the STATEPATH. This works quite well and uses surprisingly little code (much less than parsing the 'ups.conf' file). However, since I can no longer read the name from the 'ups.conf' file, I need to extract this from the name of the socket. We might simply strip the drivername from the socket name again,

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