similar to: about the 2.0.5 release

I keep getting this kind of stuff in /var/log/messages Jan 18 17:45:03 bulldog tripplite_usb[9979]: libusb_get_interrupt() returned -110 instead of 8 Should I be worried about it? upsc seems to work fine... I tried building the 2.0.5 but none of the included spec files seemed to work with opensuse 10.2 and adapting their 2.0.4 spec file didn't seem to work out well either. Building from

I keep getting this kind of stuff in /var/log/messages Jan 18 17:45:03 bulldog tripplite_usb[9979]: libusb_get_interrupt() returned -110 instead of 8 Should I be worried about it? upsc seems to work fine... I tried building the 2.0.5 but none of the included spec files seemed to work with opensuse 10.2 and adapting their 2.0.4 spec file didn't seem to work out well either. Building from

Hello, I have a Yunto e a Zanto ups connected with usb with id 06da:0002 and 06da:0601. I have seen that people had some success using megatec driver. But now megatec is replaced by blazer-usb and I am not able to use my upses under nut. Can you help me? Thanks! Mario

Hi there, I'm preparing the 2.0.3-pre2 release. 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. That means that the updated newhidups, as well as tripplite_usb and bcmxcp_usb if these are fine. To Charles and Wolfgang: any comments, objections, last things to be

please keep the list cc'ed when replying me. ---------- Forwarded message ---------- From: Andreas Thienemann <andreas@bawue.net> Date: 15 nov. 2005 15:36 Subject: Re: RE New xanto driver for NUT To: Arnaud Quette <aquette.dev@gmail.com> Hello Arnaud, On Tue, 15 Nov 2005, Arnaud Quette wrote: > is there really a need to separate it from the megatec. > we're currently

please keep the list cc'ed when replying me. ---------- Forwarded message ---------- From: Andreas Thienemann <andreas@bawue.net> Date: 15 nov. 2005 15:36 Subject: Re: RE New xanto driver for NUT To: Arnaud Quette <aquette.dev@gmail.com> Hello Arnaud, On Tue, 15 Nov 2005, Arnaud Quette wrote: > is there really a need to separate it from the megatec. > we're currently

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

Hi Andy, I've forwarded your info to the development list, and Carlos Rodrigues (the megatec driver author and maintainer. As a side note, there is a megatec_usb driver underway. You might want to give it a try. @Carlos: I let you update the drivers.list. Thanks for your report, Arnaud Quette -- Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt Network UPS Tools (NUT) Project Leader -

can you also give a try to megatec and send us back some upsc output of your various tests? Mathias Mayrhofer wrote: > > Arnaud QUETTE wrote: > > > Mathias Mayrhofer wrote: > it works (except of the temperature) > > thanks a million!! > > > > Sorry to bother you, > > > 'nut' is great (it was the only thing that worked on by belkin usv), >

2006/10/2, Peter Selinger <selinger@mathstat.dal.ca>: > Arnaud Quette wrote: > > > > 2006/9/29, Peter Selinger <selinger@mathstat.dal.ca>: > > > > > I don't really understand the purpose of the "Testing" branch. It has > > > not been touched since July, as far as I can see. I also don't > > > understand NUT's release

Hello: I have a UPS model MXE II MAXIM brand online, 3500VA 2100W. Connects to the PC by a USB 2.0 port. I wanted to use nut, but this brand is not on the list of nut drivers. lsusb returns: ... Bus 003 Device 003: ID 06DA: 0201 Phoenixtec Power Co., Ltd ... I did not find this manufacturer in the driver list. Anyone know if you can have compatibility with other make and model of UPS. With

Hi guys, Please bare with me, as this is my first attempt at setting up a UPS under Linux. I've been trying to setup a UPS on one of my clients servers. The model of the UPS is a Square one QP1000/QP1010 1Kva I've looked on the following link http://eu1.networkupstools.org/compat/stable.html It says that it should be compatible with the "powermust" driver, then in my

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

Hello, i've a problem, this is my configuration: - Atlantis Land UPS with serial port - a generic RS232 to USB cable adapter (QinHeng Electronics HL-340 USB-Serial adapter for linux). The problem is in the syslog file where i find: [...] Aug 19 09:07:25 ProLiant megatec[1126]: Communications with UPS lost: No status from UPS. Aug 19 09:07:26 ProLiant megatec[1126]: Communications with UPS

Hi Sven, 2008/1/25, Sven Koch <haegar at sdinet.de>: > Package: nut > Version: 2.2.1-1 > Severity: normal > > I am using a Mustec PowerMust 1000 USB, connected with a USB cable to > the PC. > > With nut 2.2.0-2.1 everything works without problems - but since the > 2.2.1-1 update the "upsdrvctl start" from the init script just fails, > executing the

Arjen de Korte wrote: > Author: adkorte-guest > Date: Mon Jun 18 09:03:18 2007 > New Revision: 964 > > Log: > additional debug info in case commands fail > > Modified: > trunk/ChangeLog > trunk/drivers/megatec.c > > Modified: trunk/ChangeLog Arnaud, Carlos, I'd like to backport this change to Testing as well. Intermittent startup problems for

Dear NUT developers, I have converted NUT's build system to Automake/Libtool. Right now, the new build system is contained in the "automake" branch, at: ssh://svn.debian.org/svn/nut/branches/automake I plan to merge this into the main branch after a period of testing, if there are no objections. Here are some highlights: * automatic dependency tracking: no more need to do this

Arnaud Quette wrote: > Anyhow, I would more see this as a merge of all these drivers, with > some autodetection or flag/param to switch the mfr/model and maybe > capabilities... Whatever the driver name is, a good thing would be the > name of the protocol or something generic enough, though powermust is > fine. Ok, I made some minor changes to powermust, to make it less

Hello, I have Mustek Powermust 2000VA USB And installed latest nut. Problem is that I cannot get info from UPS: http://pastebin.com/BtpE2Be1 I got contact with UPS via blazer_usb driver http://pastebin.com/38BZteFC Ups.conf: http://pastebin.com/KwRrz5rf Upsd.conf: http://pastebin.com/i3jNHpVj Upsd.users: http://pastebin.com/TRJ5ahWR Lsusb: http://pastebin.com/WsEbkPqG Dmesg:

Hi developers, I would like to propose making a release soon from the current NUT trunk. There have been a lot of important changes since 2.0.5: new drivers added/refined (e.g. megatec_usb); the switch to Automake; the renaming of newhidups to usbhid-ups; automatic installation of hotplugging files; IPv6 support; improvements to the tripplite_usb driver; improvements to the gamatronic driver;