2012/3/5 McCann, Brian bmcc...@andmore.com:
Sorry about the delay.
no problem, better late than never.
thanks again for your report,
Arno
___
Nut-upsdev mailing list
Nut-upsdev@lists.alioth.debian.org
2012/2/28 Arnaud Quette aquette@gmail.com:
Hi Charles
2012/2/28 Charles Lepple clep...@gmail.com:
On Feb 28, 2012, at 3:44 AM, Arnaud Quette wrote:
Hi Billy,
switching back this thread to -upsdev
2012/2/27 William R. Elliot b...@wreassoc.com:
I have been able to set the 'FSD' from
- http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/
2012/2/28 Arnaud Quette aquette@gmail.com:
2012/2/27 Mario Giammarco mgiamma...@gmail.com:
I am not able to do the test
When I put protocol=zinto I get:
Fatal error: 'protocol' is not a valid variable name
Hi René,
2012/2/9 Arnaud Quette aquette@gmail.com:
2012/2/8 René Martín Rodríguez rmro...@ull.edu.es:
El 08/02/12 09:14, Arnaud Quette escribió:
Hi Charles,
please to see you jumping in ;-)
2012/2/8 Charles Leppleclep...@gmail.com:
Do you know which SVN revision or NUT release your
2012/2/27 Mario Giammarco mgiamma...@gmail.com:
I am not able to do the test
When I put protocol=zinto I get:
Fatal error: 'protocol' is not a valid variable name for this driver.
I have also tried subdriver=zinto without luck
could you please send back your ups.conf.
cheers,
Arno
2012/2/27 Thomas Maisl exp-122...@maisl.com:
Hello,
schrieb Arnaud Quette, Am 16.02.2012 18:48:
Can you please counter check, and report back upsc/upsrw/upscmd
upsc:
# upsc YQ450
battery.voltage: 13.40
beeper.status: disabled
device.type: ups
driver.name: blazer_usb
Hi Billy,
switching back this thread to -upsdev
2012/2/27 William R. Elliot b...@wreassoc.com:
I have been able to set the 'FSD' from the driver and it is picked up by
upsmon. That gives me the functionality that I was asked to put in the
driver. If that is against the rules then I'll make
Hi Bill
2012/2/27 William R. Elliot b...@wreassoc.com:
From private E-mail:
My question to you is how I should go about getting
the changes back into the system. My work has been exclusively on the
ONEAC
driver and man page. The driver .c file is almost completely redone.
how can you
Hi again Bill,
2012/2/28 William R. Elliot b...@wreassoc.com:
Arnaud' the original reason for this was due to having multiple
communication channels to the UPS. It is possible for the non-NUT channel
to start a UPS delayed shutdown that the NUT master and slaves need to know
about. Charles
2012/2/22 Laurent Lesage laur...@lesagepono.be:
Bonjour Arnaud,
Bonjour Laurent,
sorry for the lag in answering... long week end.
Arnaud Quette a écrit :
2012/2/21 Laurent Lesage laur...@lesagepono.be:
Hi all,
Bonjour Laurent,
I just changed my old MGE ellipse for a evolution 850
Hi Brian,
2012/2/22 McCann, Brian bmcc...@andmore.com:
CyberPower OR700LCDRM1U
(http://www.cyberpowersystems.com/products/ups-systems/smart-app-ups/rackmount-lcd/OR700LCDRM1U.html)
upsc output:
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 20
battery.mfr.date: CPS
2012/2/16 Mario Giammarco mgiamma...@gmail.com:
Tomorrow I will do the test!
Marco, Thomas,
before I switched to something else, I'd like to complete this case.
have you been able to do some testing on your side?
cheers,
Arnaud
--
Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com
Hi Stephen,
2012/2/19 Stephen st...@suasol.com:
Hey all, I've had a fairly unpleasant experience getting nut to work.
I like the nut architecture and understand
1. I check the nut hardware list for a usb model with five star support.
Great,
my supplier has an Eaton E Series NV.
2. I run
2012/2/17 johnm s...@forceway.com:
On 02/16/2012 01:16 PM, Richard Hughes wrote:
On 12 February 2012 22:01, johnm s...@forceway.com wrote:
shows. It seems upowerd doesn't like this value though. As you can see
below, upower -d reports 0%. Any fix for this?
What's upower meant to do if the
2012/2/15 Charles Lepple clep...@gmail.com:
On Feb 14, 2012, at 5:02 PM, William R. Elliot wrote:
I am trying to make ups.delay.shutdown writable so the user can use upsrw to
change it.
In the driver, after setting the variable to 0, I am using:
dstate_setflags(ups.delay.shutdown,
Hi again William,
2012/2/14 William R. Elliot b...@wreassoc.com:
As mentioned before I am working on an update to the ONEAC driver. Most of
the ONEAC UPS products use an output voltage window to trigger either a tap
change or the inverter to maintain the output voltage level. For this
Hi Oliver and Stuart,
2012/2/13 Arnaud Quette aquette@gmail.com:
2012/2/7 Oliver Kluge o...@kluge-digital.de:
Hi Arnaud,
Hi Oliver,
if you got tons of material including several protocol revisions, maybe a
broader approach might useful?
this is to be expected from me.
I don't want
Halo Thomas und Mario ;-)
2012/2/14 Thomas Maisl exp-122...@maisl.com:
attached information was retrieved while UPS was operating _offline_ (doing
a runtime test)
thanks a lot for your test results.
1. lsusb -v -d06dA:0002
2-6. blazer_usb using subdriver cypress|phoenix|ippon|krauler
Hi Roman,
thanks for your report.
2012/2/16 Roman Mamedov r...@romanrm.ru:
Package: nut
Version: 2.6.3-1
Severity: important
nut is completely broken on my system since quite some time ago.
$ dpkg -S /etc/udev/rules.d/52-nut-usbups.rules
nut: /etc/udev/rules.d/52-nut-usbups.rules
$
Hi Matt,
2012/2/13 Matt Schulte gimpyestr...@gmail.com:
Device manufacturer and name:
Tripp-Lite OmniSmart500
upsc output:
matt@backup:/etc$ sudo upsc tripplite
battery.charge: 100
battery.test.status: Battery OK
battery.voltage: 14.56
battery.voltage.nominal: 12
device.mfr: Tripp Lite
2012/2/13 Zach La Celle lace...@roboticresearch.com:
On 02/07/2012 10:58 AM, Zach La Celle wrote:
On 02/07/2012 10:41 AM, Arnaud Quette wrote:
that's what I was suspecting.
I've never seen that one before, though!
a driver debug output, Ie:
$ /lib/nut/usbhid-ups -D -a rack1ups
2012/2/4 Mario Giammarco mgiamma...@gmail.com:
2012/2/2 Arnaud Quette aquette@gmail.com:
2012/2/1 Mario Giammarco mgiamma...@gmail.com:
Here we go!
This one for 06da:0601:
...
ok, so that one seems almost good.
can you please send also upsc / upscmd / upsrw output?
upsc:
upsc
Hi Thomas,
2012/2/13 Thomas Maisl exp-122...@maisl.com:
schrieb Arnaud Quette, Am 13.02.2012 18:28:
for the 2nd, as per its USB IDs (06DA/0002), the driver should be bcmxcp_usb.
can you please try it in debug more and also send back the output?
A few minutes ago I managed to connect
2012/2/6 thomas schorpp thomas.scho...@googlemail.com:
Hi,
Hi Thomas,
I want the driver report the battery status from ABM charging controllers
-patch attached- :
thanks for your patch.
since it introduces a new variable (battery.status.abm), I prefer to
step back and think to something
2012/2/7 Oliver Kluge o...@kluge-digital.de:
Hi Arnaud,
Hi Oliver,
if you got tons of material including several protocol revisions, maybe a
broader approach might useful?
this is to be expected from me.
I don't want to talk you into rewriting all this code, but I see space for
some
2012/2/8 René Martín Rodríguez rmro...@ull.edu.es:
El 08/02/12 09:14, Arnaud Quette escribió:
Hi Charles,
please to see you jumping in ;-)
2012/2/8 Charles Leppleclep...@gmail.com:
Do you know which SVN revision or NUT release your patch was originally
based on? Possibly v2.4.3?
Never
Hi Charles,
please to see you jumping in ;-)
2012/2/8 Charles Lepple clep...@gmail.com:
Do you know which SVN revision or NUT release your patch was originally
based on? Possibly v2.4.3?
Never mind, it was easy to merge by hand. A temporary branch is on GitHub:
2012/2/6 Zach La Celle lace...@roboticresearch.com:
On 02/03/2012 08:51 PM, Charles Lepple wrote:
On Feb 3, 2012, at 3:10 PM, Arnaud Quette wrote:
On the USB side of things, something seems fishy with the APC usb
connection: it's been incrementing the Device ID, up to 124 from 004
Hi Gerhard,
2012/2/4 Gerhard Strangar g...@arcor.de:
Arnaud Quette wrote (2012-02-02 14:13):
I did a test with an older version of my UPS, same model, but no USB
connector. This time, everything worked fine:
Feb 4 12:01:37 b1 upsmon[1494]: UPS upsb1@localhost on battery
Feb 4 12:18:52 b1
Hi Oliver,
2012/2/5 Oliver Kluge o...@kluge-digital.de:
Hi Arnaud,
Arnaud Quette wrote:
I hope somebody else with jump in and answer your question.
serialmon (http://www.serialmon.com/) seems to be a good candidate.
but I'm not sure if it allows to dump the snif.
so if you're not in hurry
Zach,
2012/2/3 Zach La Celle lace...@roboticresearch.com:
We recently had to replace an old APC SmartUPS 3000 with a newer 3000VA (the
2U one). It has both serial and USB in the back (with an RJ-45 on the end
of the serial cable).
I can't get the apcsmart driver to connect. I figured it
2012/2/3 Zach La Celle lace...@roboticresearch.com:
Thank you guys for your responses.
- The Nut version I have installed (from the Ubuntu repositories) is
2.4.3-1ubuntu3.1.
- The OS is Ubuntu server 10.04 LTS x64 with the 2.6.35-std210-amd64 kernel.
- Driver output:
root@www:/etc/nut#
2012/2/3 Zach La Celle lace...@roboticresearch.com:
I upgraded manually to the new Nut, but still receive the same error:
I should have added: supported by the usbhid-ups driver (so USB only).
root@www:/etc/nut# /lib/nut/apcsmart -D -a rack1ups
Network UPS Tools - APC Smart protocol
Hi Stuart,
2012/2/3 Stuart D. Gathman stu...@bmsi.com:
Long ago, Nostradamus foresaw that on Feb 2, Oliver Kluge would write:
I'm trying to find, inside of Eaton, more information since I'm
currently lacking too much knowledge on this protocol.
Well, since Eaton bought Best Power a long
2012/2/1 Mario Giammarco mgiamma...@gmail.com:
Here we go!
This one for 06da:0601:
...
ok, so that one seems almost good.
can you please send also upsc / upscmd / upsrw output?
...
0.478318 Ratings read in 1 tries
0.480405 send: I
0.622185 read: I
this command seems
2012/2/1 Mario Giammarco mgiamma...@gmail.com:
And for 06da:0002:
...
this one has a problem.
could you please send back the following output (as root):
$ lsusb -v -d 06da:0002
it may turn out to be a HID device more than a megatec / Q1.
as for the other unit, you may also try other
2012/2/1 Gerhard Strangar g...@arcor.de:
Arnaud Quette wrote (2012-01-31 12:38):
Jan 9 05:37:07 b1 upsmon[67752]: UPS upsb1@localhost on battery
Jan 9 06:15:19 b1 syslogd: kernel boot file is /boot/kernel/kernel
as told above, being on battery is not sufficient to trigger a system
shutdown
2012/1/25 Rene Martín Rodríguez rmro...@ull.edu.es:
Hello!!
¡Hola René Martin ;-)
I'm a sysadmin at La Laguna University in Spain. We are using NUT to manage
our UPS with great success, but we miss a feature and we would like to send
this patch to you.
If you apply this patch running upsd
2012/1/31 Charles Lepple clep...@gmail.com:
On Jan 30, 2012, at 3:15 PM, Mario wrote:
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
Hi Martin,
thanks for your confirmation.
I'm now closing this bug.
Arnaud
** Changed in: nut (Ubuntu)
Assignee: (unassigned) = Arnaud Quette (aquette)
** Changed in: nut (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member
in: nut (Ubuntu)
Assignee: (unassigned) = Arnaud Quette (aquette)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
https://bugs.launchpad.net/bugs/575573
Title:
libusb_get_interrupt: Connection timed out
To manage
** Changed in: nut (Ubuntu)
Assignee: (unassigned) = Arnaud Quette (aquette)
** Changed in: nut (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
https://bugs.launchpad.net
Hi Martin,
thanks for your confirmation.
I'm now closing this bug.
Arnaud
** Changed in: nut (Ubuntu)
Assignee: (unassigned) = Arnaud Quette (aquette)
** Changed in: nut (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member
in: nut (Ubuntu)
Assignee: (unassigned) = Arnaud Quette (aquette)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/575573
Title:
libusb_get_interrupt: Connection timed out
To manage notifications about
** Changed in: nut (Ubuntu)
Assignee: (unassigned) = Arnaud Quette (aquette)
** Changed in: nut (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/920844
Version: 2.6.3-1
Distribution: unstable
Urgency: low
Maintainer: Arnaud Quette aque...@debian.org
Changed-By: Arnaud Quette aque...@debian.org
Description:
libups-nut-perl - network UPS tools - Perl bindings for NUT server
libupsclient1 - network UPS tools - client library
libupsclient1-dev
** Bug watch added: Debian Bug tracker #634858
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634858
** Also affects: nut (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634858
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
This has been fixed where it should, Ie in VirtualBox.
The fix seems to be available since VirtualBox 4.0:
https://www.virtualbox.org/ticket/7759
Arnaud
** Bug watch added: Virtualbox Trac #7759
http://www.virtualbox.org/ticket/7759
** Changed in: nut (Ubuntu)
Status: Confirmed = Fix
NUT release 2.6.2 has fixed the regression in udev rules file creation.
In case you're stuck with an older version, I've attached a udev rules file.
Just overwrite the one on your system, using:
1) first, identify the current location of the udev file:
$ ls /???/udev/rules.d/*nut*
This should
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad
** Attachment added: Fixed udev rules file for NUT
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/578200/+attachment/2690918/+files/52-nut-usbups.rules
** Changed in: nut (Ubuntu)
Status: New = Fix Released
--
Martin,
could you please check this bug report, and apply the udev related procedure
I've documented at the end of the thread:
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/578200
Once applied, stop nut, unplug/replug your UPS USB cord, and restart nut
(at least the driver), and report
** Bug watch added: Debian Bug tracker #634858
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634858
** Also affects: nut (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634858
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
This has been fixed where it should, Ie in VirtualBox.
The fix seems to be available since VirtualBox 4.0:
https://www.virtualbox.org/ticket/7759
Arnaud
** Bug watch added: Virtualbox Trac #7759
http://www.virtualbox.org/ticket/7759
** Changed in: nut (Ubuntu)
Status: Confirmed = Fix
NUT release 2.6.2 has fixed the regression in udev rules file creation.
In case you're stuck with an older version, I've attached a udev rules file.
Just overwrite the one on your system, using:
1) first, identify the current location of the udev file:
$ ls /???/udev/rules.d/*nut*
This should
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad
** Attachment added: Fixed udev rules file for NUT
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/578200/+attachment/2690918/+files/52-nut-usbups.rules
** Changed in: nut (Ubuntu)
Status: New = Fix Released
--
Martin,
could you please check this bug report, and apply the udev related procedure
I've documented at the end of the thread:
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/578200
Once applied, stop nut, unplug/replug your UPS USB cord, and restart nut
(at least the driver), and report
Expert RD - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/
2012/1/20 Arnaud Quette aquette@gmail.com
Hi Jorge,
2012/1/19 Jorge
2012/1/19 Dmitry Andreychuk 915...@bugs.launchpad.net:
Attaching logs with power failure for versions 2.6.1-2ubuntu2 and 2.6.3.
Power failures and power returns are marked with NOTE in the logs.
I noticed that UPS.PowerSummary.RemainingCapacity came with input report
only once. The device
2012/1/19 Dmitry Andreychuk 915...@bugs.launchpad.net:
Attaching logs with power failure for versions 2.6.1-2ubuntu2 and 2.6.3.
Power failures and power returns are marked with NOTE in the logs.
I noticed that UPS.PowerSummary.RemainingCapacity came with input report
only once. The device
Hi Stuart,
2012/1/20 Stuart D. Gathman stu...@bmsi.com:
Long ago, Nostradamus foresaw that on Jan 19, Arnaud Quette would write:
Perhaps it should leave status unchanged after a single corrupt
record from the UPS instead of reporting a problem.
if only the checksum is corrupted from time
Hi Regid,
2012/1/23 Regid Ichira regi...@yahoo.com:
--- upsmon.8 2012-01-23 11:52:34.0 +0200
+++ upsmon.8.mod 2012-01-23 11:53:27.0 +0200
@@ -35,7 +35,7 @@ upsmon \- UPS monitor and shutdown contr
.sp
\fBupsmon\fR \-c \fIcommand\fR
.sp
-\fBupsmon\fR [\-D] [\-p]
Free Software Developer - http://arnaud.quette.free.fr/
2012/1/23 Arnaud Quette aque...@alioth.debian.org:
Author: aquette
Date: Mon Jan 23 10:11:18 2012
New Revision: 3407
URL: http://trac.networkupstools.org/projects/nut/changeset/3407
Log:
Add the missing '-K' (Test for the shutdown flag
Hi Rainer,
first, I've redirected your mail to the users list, which is more suitable.
if you need to post further mail there, please subscribe to this list.
2012/1/20 Rainer Stumbaum rainer.stumb...@boerse-go.de:
Riello Netman Plus 102 Card plugged into a Riello Sentinel SDL 6000-7 and a
Hi Sergey,
cc'ing NUT users list, since others may be interested in the topic
(for those, follow the bug link below).
2012/1/16 Dmitry Andreychuk 915...@bugs.launchpad.net:
Hi Arnaud,
Thanks for your reply! Attaching output for 2.6.0-1ubuntu3.
** Attachment added:
Hi Sergey,
cc'ing NUT users list, since others may be interested in the topic
(for those, follow the bug link below).
2012/1/16 Dmitry Andreychuk 915...@bugs.launchpad.net:
Hi Arnaud,
Thanks for your reply! Attaching output for 2.6.0-1ubuntu3.
** Attachment added:
Hi Sergey,
cc'ing NUT users list, since others may be interested in the topic
(for those, follow the bug link below).
2012/1/16 Dmitry Andreychuk 915...@bugs.launchpad.net:
Hi Arnaud,
Thanks for your reply! Attaching output for 2.6.0-1ubuntu3.
** Attachment added:
Free Software Developer - http://arnaud.quette.free.fr/
On Monday, January 16, 2012 at 6:56 AM, Arnaud Quette wrote:
Dear Cobbler fellows,
First, to introduce myself, I'm Arnaud Quette.
I'm mainly in charge of the NUT - Network UPS Tools [1] project.
NUT is the main project for power devices
Dear Cobbler fellows,
First, to introduce myself, I'm Arnaud Quette.
I'm mainly in charge of the NUT - Network UPS Tools [1] project.
NUT is the main project for power devices (UPS, PDU, PSU, ... ) management
and protection, and provides the broadest list of supported devices in the
field [2
Hi Dmitry,
2012/1/13 Dmitry Andreychuk
Public bug reported:
Ubuntu 11.10
nut 2.6.1-2ubuntu2
UPS model: APC Back-UPS ES 525 (BE525-RS)
driver: usbhid-ups
I get the following error approximately every 30 seconds:
usb 4-2: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 2 ret
Hi Dmitry,
2012/1/13 Dmitry Andreychuk
Public bug reported:
Ubuntu 11.10
nut 2.6.1-2ubuntu2
UPS model: APC Back-UPS ES 525 (BE525-RS)
driver: usbhid-ups
I get the following error approximately every 30 seconds:
usb 4-2: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 2 ret
Hi
2012/1/11 William Seligman selig...@nevis.columbia.edu
The problem is solved, but first things first:
On 1/11/12 6:43 AM, Arnaud Quette wrote:
2012/1/9 William Seligman selig...@nevis.columbia.edu
On 1/9/12 9:53 AM, Arnaud Quette wrote:
2012/1/6 William Seligman selig
2012/1/9 William Seligman selig...@nevis.columbia.edu
On 1/9/12 9:53 AM, Arnaud Quette wrote:
2012/1/6 William Seligman selig...@nevis.columbia.edu
I've googled and RTFM'ed, but still can't solve this one. I hope you
folks
can.
This affects my entire computer cluster, but let's
2012/1/10 Charles Lepple clep...@gmail.com
On Jan 10, 2012, at 5:16 AM, Arnaud Quette wrote:
I'm not entirely sure of the format on my side though! Should it be:
Summary line
continuation
Or something else?
Summary (50 chars or less)
A more detailed explanation (after a blank
Blueprint changed by Arnaud Quette:
Whiteboard changed:
Work Items:
[aquette] support for power devices in OCS and Fusion inventory: INPROGRESS
- NUT integration in Cobbler (replace fence-agents): TODO
+ NUT integration in Cobbler (replace or complement fence-agents): TODO
[aquette] Write
Hi Eric,
2012/1/9 Eric S. Raymond e...@thyrsus.com
Arnaud Quette aquette@gmail.com:
Note that I have a few things stagging for the Powerchain branch, which
is not yet usable, but might be worth to commit.
But since I don't want to interfere with the git transition, this can
wait
Hi Michal
2012/1/10 Michal Hlavinka mihl-gu...@alioth.debian.org
Author: mihl-guest
Date: Tue Jan 10 09:10:04 2012
New Revision: 3383
URL: http://trac.networkupstools.org/projects/nut/changeset/3383
Log:
Creating a branch for Coverity reported problems
I'm very interested there!
Have
Hi William,
2012/1/6 William Seligman selig...@nevis.columbia.edu
I've googled and RTFM'ed, but still can't solve this one. I hope you folks
can.
This affects my entire computer cluster, but let's start simple: I've got a
computer running NUT; OS is Scientific Linux 5.5; kernel
2012/1/9 Charles Lepple clep...@gmail.com
On Jan 9, 2012, at 7:06 AM, Arnaud Quette wrote:
Hi Charles,
2012/1/8 Charles Lepple clep...@gmail.com
On Jan 6, 2012, at 7:34 PM, Eric S. Raymond wrote:
# 4. Is the new_UIs-root tag still useful? It doesn't seem to point
2012/1/9 Sadara Kael sad...@wildwoodgroup.com.au
hi all,
Hi Sadara,
really simple fix for the bestups driver:
In function:
upsdrv_makevartable()
you need to add the line
addvar(VAR_VALUE, battvoltmult, Battery voltage multiplier);
There are a number of simple improvements I could
Hi Glen,
first, please keep the traffic on the list, since others may be interested
in these info.
2012/1/6 Glen Ogilvie n...@linuxsolutions.co.nz
Hi Arnaud,
One thing to note.. not sure how to work around it yet, but:
The entry I am using is:
[nutdev1]
driver = blazer_usb
2012/1/6 Charles Lepple clep...@gmail.com
On Jan 6, 2012, at 6:42 AM, Arnaud Quette wrote:
2012/1/6 Glen Ogilvie n...@linuxsolutions.co.nz
[...]
The entry I am using is:
[nutdev1]
driver = blazer_usb
port = auto
vendorid = 0001
productid =
Hi Jack,
2012/1/5 Jack Challen jack.chal...@ocsl.co.uk
Hi,
This appears to be related to a thread from January 2010:
http://lists.alioth.debian.**org/pipermail/nut-upsdev/2010-**
January/004470.htmlhttp://lists.alioth.debian.org/pipermail/nut-upsdev/2010-January/004470.html
NB: This is on
Hi Denis,
2012/1/4 Serov Denis dns-...@yandex.ru
Hello NUT Team!
I've got some questions about NUT (Windows port), which I couldn't resolve
by myself.
I have a test environment that contains:
1. NUT network server (OS: Debian 6.0.3, x64, NUT 2.4.3)
2. Linux clients (OS: different, NUT
Hi Glen,
2012/1/5 Glen Ogilvie n...@linuxsolutions.co.nz
On Thu, 05 Jan 2012, Arnaud Quette wrote:
Network UPS Tools version 2.6.3 has been released:
http://www.networkupstools.org/
Direct access:
- Download: http://www.networkupstools.org/source/2.6/nut-2.6.3.tar.gz
- News: http
this has been fixed in nut-2.6.2 packages, though there is still a bug (missing
client init script).
Final fix scheduled for the next Debian upload / Ubuntu sync.
** Changed in: nut (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a
this has been fixed in nut-2.6.2 packages, though there is still a bug (missing
client init script).
Final fix scheduled for the next Debian upload / Ubuntu sync.
** Changed in: nut (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a
Network UPS Tools version 2.6.3 has been released:
http://www.networkupstools.org/
Direct access:
- Download: http://www.networkupstools.org/source/2.6/nut-2.6.3.tar.gz
- News: http://www.networkupstools.org/source/2.6/new-2.6.3.txt
- ChangeLog: http://www.networkupstools.org/source/2.6/ChangeLog
Bonsoir Edouard
2011/12/22 o...@netfusion.fr
Hi everybody,
It seems that my MGE Pulsar Evolution 1100 is not supported by the
usbhid-ups driver.
This is the output I get with the –x explore switch:
Network UPS Tools - Generic HID driver 0.35 (2.6.2)
USB communication driver 0.31
2011/12/22 Charles Lepple clep...@gmail.com
On Dec 21, 2011, at 12:42 PM, Mauricio Girardi wrote:
I installed NUT and followed all suggested procedures to
verify if my ups is supported.
No driver recognized my ups, and the genericups tests
get wrong.
Here I send some informations
Chetan,
the below error is the same than on Solaris Intel:
buildbot startup script needs to have PATH set so that it can find the
various needed binaries (svn, make, compiler, ...)
you may simply want to copy the intel one to the sparc...
I'm away from work and back on Jan. 3rd, so up to you to
I don't see any message related to usbhid-ups.
Is it started?
we can see hiddev0 (the device linked to the kernel module hiddev) loaded,
but nothing more.
So, try launching again nut, and check back /var/log/syslog for usb and nut
('ups') messages.
Arno
--
You received this bug notification
I don't see any message related to usbhid-ups.
Is it started?
we can see hiddev0 (the device linked to the kernel module hiddev) loaded,
but nothing more.
So, try launching again nut, and check back /var/log/syslog for usb and nut
('ups') messages.
Arno
--
You received this bug notification
2011/12/17 Charles Lepple clep...@gmail.com
On Dec 17, 2011, at 3:53 AM, Arnaud Quette wrote:
Author: aquette
Date: Sat Dec 17 08:53:41 2011
New Revision: 3363
URL: http://trac.networkupstools.org/projects/nut/changeset/3363
Log:
Try to fix language ID support for USB units from
Hi Martin,
I'm adding the nut users list, since other may be interested in.
2011/12/16 Martin Ewing martin.s.ew...@gmail.com
I do still have an issue with NUT on Ubuntu Natty (64 bit).
I attach my latest info. Will appreciate any further suggestions about
how to tame this problem - whether
Can you please test with the blazer_usb driver and report back?
This one has replaced megatec_usb officially since 2.4.3, but was already
available in 2.4.1 (though not as mature).
cheers,
Arnaud
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
There is an effort underway to provide the needed foundations for adding
a decent debconf for generating a suitable configuration.
I will leave this bug open as a reminder.
thanks for your report,
Arnaud
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Note for Ubuntu packagers:
- the original report was an issue with udev, and will be fixed with 2.6.3
upload,
- the 2nd one (Martin Ewing) was probably invalid, due to an already running
driver instance.
I've asked the user for some more feedback.
cheers,
Arnaud
--
You received this bug
Hi Martin,
I'm adding the nut users list, since other may be interested in.
2011/12/16 Martin Ewing martin.s.ew...@gmail.com
I do still have an issue with NUT on Ubuntu Natty (64 bit).
I attach my latest info. Will appreciate any further suggestions about
how to tame this problem - whether
Can you please test with the blazer_usb driver and report back?
This one has replaced megatec_usb officially since 2.4.3, but was already
available in 2.4.1 (though not as mature).
cheers,
Arnaud
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Note for Ubuntu packagers:
- the original report was an issue with udev, and will be fixed with 2.6.3
upload,
- the 2nd one (Martin Ewing) was probably invalid, due to an already running
driver instance.
I've asked the user for some more feedback.
cheers,
Arnaud
--
You received this bug
501 - 600 of 2433 matches
Mail list logo
