It's not included in v2.0.2, but it will be included in the next
v2.0.3, and it is also included in the Development version in CVS.
http://www.networkupstools.org/source.html
for information on how to obtain the sources from CVS. -- Peter
David L. Day wrote:
Hi - I've seen some notes on
list, and not to me
personally.
-- Peter
doug reynolds wrote:
Peter Selinger wrote:
Hi Doug,
looks like you should try to start the driver manually, and with
debugging enabled.
./drivers/cyberpower -DD -a hiveups
This should give additional information on why the driver does
Dear Ashley,
I have no personal experience with the Tower-Rack series, but someone
reported on the Nut-upsuser mailing list on 29 Nov 2005 that these
models work with the belkin driver of the NUT software
(http://www.networkupstools.org/). This is for the serial port. For
USB, the NUT newhidups
Hi Ashley,
yes, try the newhidups driver. It should work. If there are problems,
we can improve the driver. -- Peter
P.S. please keep the mailing list cc'd.
Ashley M. Kirchner wrote:
Eric S. Johansson wrote:
The software that Belkin includes is the Bulldog software. They do
offer a
Ted Bardusch wrote:
OK, I've installed libusb and gd (for the cgi stuff). I have the UPS
connected, and built NUT with newhidups. but now I need to know what
to set the ups.conf port to. Any ideas on that?
Please see the newhidups(8) man page, section IMPLEMENTATION.
IMPLEMENTATION
This is a permissions problem; note the nobody in:
/proc/bus/usb/002:
dr-xr-xr-x 2 root root 0 Feb 3 12:40 .
drwxr-xr-x 6 root root 0 Feb 3 12:40 ..
-rw-r--r-- 1 root root 43 Feb 3 12:40 001
-rw-r--r-- 1 root nobody 52 Feb 3 12:40 002
This should be the ups user. The solution is
it to something more
intuitive before the next release.
any idea what's going on?
steve
Peter Selinger wrote:
Steve,
use newhidups, not hidups. You should do either this:
./configure --with-drivers=newhidups
make
(to compile only the newhidups driver - saves a lot
-tared the source
* i configured for the build with:
o ./configure --with-user=nut
o make
o make usb
* then i ran make install
but none of the usb drivers showed up in /usr/local/ups/bin
any idea what's going on?
steve
Peter Selinger wrote
Looks like a permissions problem. USB drivers require some special
setting-up. They key is to start by running the driver with -u root.
I wrote some instructions for APC/newhidups at
http://www.mathstat.dal.ca/~selinger/ups/backups.html; they might
help.
-- Peter
Gregory Gulik wrote:
I
communicates
with the driver through a socket that is owned by the driver.
The ups.conf file has the following:
[tripplite]
driver = tripplite_usb
port = auto
desc = Tripp-Lite 1500RM XL2U
This is on Fedora Core 4 if it makes a difference.
Peter Selinger wrote
usb_os_find_devices: couldn't open device /dev/ugen0.00: Permission denied
Looks like a permissions problem to me. Who owns /dev/ugen0.00?
Perhaps you have to run the driver with -u root, until it works,
then set up hotplugging. -- Peter
Nevil Thatcher wrote:
Hi Arnaud,
Thanks for the
Arjen de Korte wrote:
I tried running the driver on its own:
destiny:/usr/local/ups/bin# ./apcsmart /dev/ttyS0 -x cable=3D940-0024C
Network UPS Tools (version 2.0.2) - APC Smart protocol driver
Driver version 1.99.7, command table version 2.0
getpwnam(nut): Success
?
-- Peter
Peter Selinger wrote:
No. The 'getpwnam(nut): Success' should not be displayed by the driver as
far as I can tell. Throughout the sources, the word 'getpwnam' is only
used to display a fatal error when NUT isn't able to locate a userid, in
this case for 'nut'. Where
; make; make
install). Please report back to the list.
Thanks! -- Peter
Arnaud Quette wrote:
2006/3/1, Peter Selinger [EMAIL PROTECTED]:
This is a duplicate bug report. It was first reported by Gordon Rowell
on Feb 06 on the Nut-upsdev list, and has subsequently been fixed in
CVS. See
aerios wrote:
Hello all,
I'm new to nut, i've donwloaded and installed without problem apparently
nut 2.0.3 on a slackware 10.x (1 i think).
/usr/local/ups/bin/upsdrvctl start
seems to work correctly.
but when i do:
/usr/local/ups/sbin/upsd
i've got:
Network UPS Tools upsd 2.0.3
decimal poin=
t.
I'll too need to take a look at those logs (taken when the UPS is
fully charged), posting them to the list is a good idea.
On 4/23/06, Peter Selinger [EMAIL PROTECTED] wrote:
Could the reason be that the UPS reports voltage to more than one
decimal, and the value used
lonely wolf wrote:
Secondary question: as you can see at
http://wdl.lug.ro/ablerex/upsilon.status.screen (and
http://wdl.lug.ro/ablerex/upsilon.config.screen ), upsilon reports:
ACfail Shutdown Delay: 1440 Min
UPS Turn Off Delay : 10.0 Min
1440 min = a 24h (maximum allowed
Hi Vlado,
your issue seems to be an issue of lower-level USB support. Not only
does NUT fail to find your ups, but it fails to find *any* USB devices
or controllers. Normal output from newhidups -u root -D auto
should look like this:
Network UPS Tools: New USB/HID UPS driver 0.28 (2.1.0)
Scott Tuc Ellentuch at T-B-O-H wrote:
Hi,
FINALLY got my UPS working, YEA But now it brings
up even more issues.. (BOOO!!)
1) I'm thinking this is a UPS issue, but when I pull the plug
on my UPS, it goes from 100 to 30 in just a short amount of
time (Minutes). This causes
-upsdev around
November 7 involving Joel Peshkin, and also posts by Dean Gibson
ca. Nov 26.
-- Peter
Joseph Scanlan wrote:
On Thu, 11 May 2006, Joseph Scanlan wrote:
On Thu, 11 May 2006, Charles Lepple wrote:
However, Peter Selinger has made some changes post-2.0.3 to better handle
Scott Tuc Ellentuch at T-B-O-H wrote:
You did not configure your shutdown scripts correctly; see item 11
under Configuring shutdowns for low battery events in INSTALL. Your
computer is supposed to power off (after going through the usual
shutdown procedure) by letting the UPS know to
Try poking around in /etc/rc.d, /etc/rc.d/rc.0.
There is a reasonable explanation of how BSD init scripts work, with
example scripts, at
http://www.linuxfromscratch.org/hints/downloads/files/bsd-init.txt
My understanding is that rc.shutdown is called before the actual
shutdown procedure, and
Joseph Scanlan wrote:
On Fri, 12 May 2006, Peter Selinger wrote:
There is a temporary fix. Check out the thread on nut-upsdev around
November 7 involving Joel Peshkin, and also posts by Dean Gibson ca.
Nov 26.
http://lists.alioth.debian.org/pipermail/nut-upsdev/2005-November/000318
Are you sure this is an error message? It looks like a warning to me.
If it works with -D, it should work without -D - the only
difference is whether debug messages are printed or not.
Of course, you would not expect the driver to output anything. It
should run silently without the -D.
-- Peter
Pete,
/sbin/service is just a shell script that calls the appropriate script
in /etc/init.d/. You should look at your /etc/init.d/ups to see what,
if anything, it does.
I have simply put this in my rc.local:
start_ups_driver() {
/usr/bin/upsdrvctl start /dev/null
}
start_ups_daemon() {
You can use strace(1) to track the system calls the software makes,
which should allow you to monitor the communications and figure out
the protocol. -- Peter
gypsy wrote:
gypsy wrote:
Although this SmartLink comes with a Linux program to monitor it, I'd
rather use nut if possible.
can expect at a given load, so just buy one that
says you get at least 20 minutes for some reasonable load.
-- Peter
Arjen de Korte wrote:
Peter Selinger wrote:
I am running a home box (600watt total load, may expand to 800-900) and
I need a UPS that can sustain power to that for at least
usb_submit_urb() is a kernel function. Error code 28 is ENOSPC, which
means no space left on device, which is a strange error to occur in
this context. It does not look like a NUT problem to me. -- Peter
Rodrigo Ventura wrote:
I'm getting dmesg flooded with messages like this one:
Eli,
Gamatronic is not currently supported by the newhidups driver. You
have two options:
(1) look at the file data/driver.list or
http://www.networkupstools.org/compat/ to find a serial driver
that matches your device, and/or
(2) post the output of
newhidups -DD -u root -x
Hi Eli,
sorry, I forgot to say: you should first get and compile the newest
development tree of NUT from the SVN repository. The -x generic flag
will not work with 2.0.3. See
http://www.networkupstools.org/source.html
-- Peter
Eli Wapniarski wrote:
Hi Peter
Thanks for responding.
for notifications...
Keeps on repeating the same thing over and over again until I press
Control C.
Eli
On Wednesday, 14 =3DD7=3D91June 2006 18:52, Peter Selinger wrote:
Hi Eli,
sorry, I forgot to say: you should first get and compile the newest
development tree
Eli,
you should be doing the next step. Run the driver and upsd (not
upsmon), and see what output you can get from upsc.
-- Peter
Eli Wapniarski wrote:
OK... Waiting for whats next
Eli
On Friday, 16 =D7=91June 2006 18:02, Peter Selinger wrote:
Yup, that's fine. It doesn't matter
): No such=
=20
file or directory
Synchronizing.. giving up
ups.conf contains.
[Gamatronic_D-Compact]
driver=3D newhidups
port =3D auto
desc =3D Gamatronic D-Compact
Eli
On Friday, 16 =D7=91June 2006 18:40, Peter Selinger wrote:
Eli,
you should
Eli Wapniarski wrote:
upsdrvctl -D -u root start produces
Network UPS Tools - UPS driver controller 2.1.0
Starting UPS: Gamatronic_D-Compact
exec: /usr/bin/ -a Gamatronic_D-Compact
execv: Permission denied
Driver failed to start (exit status=1)
I think I understand the problem
Arnaud Quette wrote:
gamatronic units are also supported by the gamatronic driver (much
derived from the old sec driver). You should give it a try.
About the newhidups issue, the given path might refer to some SEC
protocol. But that needs some decoding (ie get the data for each path,
Hi Chris,
I am cc'ing this to the nut-upsuser mailing list.
Chris Hotte wrote:
Hello Peter! First of all, allow me to thank you in advance for all the
work and information you have assembled on UPS devices.
I'm currently (not a pun) investigating UPS solutions for my Linux based
Hi Barry, Jonathan, etc,
I just caught up with this thread. Yes, I agree with Jonathan's
diagnosis that this might be a HID device, although it is not 100%
sure. The many Input features make me suspicious that it could still
be a fancy serial-over-USB.
[ A general remark to anyone on this
Phil DeBoest wrote:
Peter Selinger wrote:
I have just committed some changes to the development branch that
hopefully solve this problem. Now I retrieve the HID descriptor in two
different ways, and when in doubt, use the second value (the same as
lsusb). I have also made libusb_open
: 164.0
output.voltage.nominal: 120
ups.beeper.status: enabled
ups.delay.reboot: 65535
ups.delay.shutdown: 65535
ups.mfr: Tripp Lite
ups.model: TRIPP LITE UPS
ups.power.nominal: 1200
ups.serial: 692199 B
ups.status: OL CHRG
-James
-Original Message-
From: Peter Selinger
James,
thanks, this is useful info. Comments below. -- Peter
James Pooton wrote:
I saw on the list that you were looking for some details. Sorry I'm not
part of the list, but here are my results:
[EMAIL PROTECTED] bin]# ./newhidups -DDD -u root [EMAIL PROTECTED]
Network UPS Tools:
Daniel O'Connor wrote:
--nextPart2732627.jUZ38zfOrR
Content-Type: text/plain;
charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
On Sunday 13 August 2006 16:49, Peter Selinger wrote:
Not all UPS hardward and not all drivers support ondelay
Ben wrote:
On 8/13/06, Peter Selinger [EMAIL PROTECTED] wrote:
Ben,
Not all UPS hardward and not all drivers support ondelay/offdelay. In
any case, you should let your system shutdown script kill the UPS, at
the very end, after all the disks have been mounted read-only, and
just
Yes, that is helpful. It seems that your Tripp Lite has different bugs
than James's. That means it will be more tricky to fix.
In any case, I am glad to see that the driver is now working. The bugs
are minor and only affect how the voltages are displayed.
-- Peter
Phil DeBoest wrote:
Hi Brian,
Tripp Lite support for this model was only added in the last few
weeks; your NUT 2.0.3 is too old. You should get the very latest
development version from the SVN repository. Follow the instructions
on http://eu1.networkupstools.org/source.html under Development
Tree.
You should then
Matt,
Cyber Power was not supported by NUT in 2.0.3. However, it is
supported now, so you should upgrade NUT to the newest development
version from SVN. Follow the instructions at
http://www.networkupstools.org/source.html
under Development tree. You should use the newhidups driver.
-- Peter
Martin Ivanov wrote:
1. How to make the UPS power off after the PC powers off in case of power
failure. Of course when there is no power failure, but I issue shutdown
command to the system, the UPS must not power off.
The answer to this question in contained in the file INSTALL that is
Paolo,
I recently fixed some bugs regarding the report descriptor retrieval.
Please try it with the newest development version from SVN. You can
follow the instructions at
http://www.networkupstools.org/source.html
under Development tree to get it. It might solve the problem, or if
it
Great! Please let the mailing list know if you run into any further
problems. -- Peter
Paolo Pedroni wrote:
Alle 16:38, venerd=EC 25 agosto 2006, hai scritto:
Paolo,
I recently fixed some bugs regarding the report descriptor retrieval.
Please try it with the newest development version
Dear Marc,
first, the 'powercom' driver is a serial driver, so it will not work
for USB.
Second, newhidups does not currently support Powercom. The reason is
simple: this is (as far as I remember) the first time we are seeing a
Powercom USB device. It might not be too difficult to add support
Marc Collin wrote:
Le vendredi 25 ao=C3=BBt 2006 21:51, vous avez =C3=A9crit=C2=A0:
Marc,
interesting, actually, we have seen this device before; see the posts
by Barry Fawthrop around August 1. It is a HID device, but it does not
follow the USB HID standard for power devices. So
That is very odd indeed. Why should the system shut off abruptly? If
the log shows nothing, then it seems that the UPS just turned off the
power.
I recommend testing this while attaching, say, a lamp to the UPS,
instead of a computer. (You can still use your computer to monitor the
UPS, just
Marc Collin wrote:
linux64:/home/collinm/Download/trunk # /usr/local/ups/bin/upsc [EMAIL
PROTECTED]
driver.name: newhidups
driver.parameter.port: /dev/hiddev0
driver.version: 2.1.0
driver.version.data: PowerCom HID 0.1
driver.version.internal: 0.30
powercom.coll2.feature3: 1
Paolo Pedroni wrote:
Anyway, I have found something in the debug output that does not seem norma=
l,
and maybe you may want to check it. The relevant output
(/lib/nut/newhidups -DD -a SmartUps1500) is as follows:
(snip)
Waiting for notifications...
upsdrv_updateinfo...
Waiting for
. This
would yank the power from your UPS. In the above setup, you would see
the lamp go off as the computer is preparing to shut down.
-- Peter
Peter Selinger wrote:
That is very odd indeed. Why should the system shut off abruptly? If
the log shows nothing, then it seems that the UPS just
Arnaud Quette wrote:
Hi
2006/8/27, Peter Selinger [EMAIL PROTECTED]:
...
What's to do here for the NUT developers is: first, improve support
for interrupt transfers in newhidups.
right, as we still rely on the (very) early code I first wrote.
moreover, the big nested if in update
Arnaud Quette wrote:
2006/8/30, Peter Selinger [EMAIL PROTECTED]:
Arnaud Quette wrote:
Hi
2006/8/27, Peter Selinger [EMAIL PROTECTED]:
...
What's to do here for the NUT developers is: first, improve support
for interrupt transfers in newhidups.
right, as we still
on the NUT site, but maybe not the
correct ones?
Rob
Peter Selinger wrote:
Rob wrote:
What would I be looking for that I didn't see in my testing with my
windows box? Should I be trying to sniff the serial connection to see
if the UPS is for some reason sending a weird signal
Charles Lepple wrote:
On 9/8/06, Hans Fugal [EMAIL PROTECTED] wrote:
I have a Tripp Lite OMNI900LCD.
...
I can't get newhidups to recognize it at all.
Support for newer Tripp-Lite USB/HID models is still in the
development tree (the trunk in SVN). Instructions for grabbing it via
OK, in any case, once Hans gets the development version of NUT, he can
then produce enough debugging output so that we can hopefully support
the model. -- Peter
Marc Collin wrote:
Le vendredi 8 septembre 2006 15:35, Peter Selinger a =E9crit=A0:
Charles Lepple wrote:
On 9/8/06, Hans Fugal
Rob wrote:
I would try the following: plug your computer into a wall outlet, plug
a desk lamp into the UPS. First, start the driver and upsd (but not
upsmon). Monitor the ups variables with upsc. Pull the power, wait 5
minutes or more, see what happens. Are there changes to ups.status?
Rob wrote:
While plugged into the wall:
battery.charge: 100.0
battery.runtime: 64:41
driver.name: cpsups
driver.parameter.port: /dev/ttyS2
driver.version: 2.0.4
driver.version.internal: .04
input.frequency: 60
input.voltage: 122
output.voltage: 122
ups.load: 9
ups.mfr:
Hi Magnus,
I didn't understand your compiler's error message (they were not in
English).
However, it seems that you need to install libusb, version 0.1.8 or
later, before compiling nut. I wrote some instructions for setting up
NUT with the APC Back-UPS at:
After what's been said here, and the data that Rob sent, it seems that
the UPSs are faulty; I cannot think of any reason why they should yank
the power after 5 minutes, without any warning sign, and with brand
new batteries. Even stranger that it still does this when the power is
interrupted only
Denis Hainsworth wrote:
holy crap. just rpm'd the hotplug stuff for fc3. added an appropriate
line to usb.usermap and a script that changes permissions and group
and it just worked.
Excellent. I have added your device F6C550-AVR (050d/0551) to our
standard hotplug scripts in SVN as well.
Denis Hainsworth wrote:
usb 1-1: usbfs: process 32652 (newhidups) did not claim interface 0
before use
so I found two places where supposedly you guys have added code to
address the above issue I am having.
Maybe you can tell us what two places you are talking about? -- Peter
As far
Denis Hainsworth wrote:
On Sun, Sep 17, 2006 at 11:54:32AM -0300, Peter Selinger wrote:
Denis Hainsworth wrote:
usb 1-1: usbfs: process 32652 (newhidups) did not claim interface 0
before use
so I found two places where supposedly you guys have added code to
address
Michael Helmling wrote:
Excellent, it works with megatec and /dev/ttyS0. Thank you very
much! Someone could add that to the hardware database.
Please let me know if I can provide you with any information that
might help to get the USB interface working, too.
To get the USB interface
That device is not currently supported (we have never seen it before).
It looks like a HID device, so it should be possible to write a
subdriver for it, see docs/hid-subdrivers.txt.
However, the data returned by the device looks strange; all the values
are 0. I am not sure if this will work
at least one of
the values would dropped to a negative value. What should I do next? Thanks.
On Sat, 23 Sep 2006 16:06:37 -0300 (ADT)
[EMAIL PROTECTED] (Peter Selinger) wrote:
The patch I just sent may not work; please try this one instead.
-- Peter
=?iso-8859-1?Q?Fr=E9d=E9ric_POTTER?= wrote:
Thanks jimmy for the hints, but I'm afraid the description of the
problem I have was not clear.
The problem I have is NOT a software configuration issue of NUT.
The problem I have is that the UPS, when reaching battey.charge.low
SHUTS DOWN
Strange. Is the problem reproducible? I have never seen it before.
You might try the Development version of NUT from SVN (see
http://www.networkupstools.org/source.html under Development tree).
There has been quite a lot of work on the newhidups driver since
2.0.4.
-- Peter
Jan Zuchhold
You should first get a current version of NUT. Get release 2.0.4 or
later, and preferably the Development version (see
http://www.networkupstools.org/source.html - Develoment Tree).
The driver to use is newhidups. -- Peter
Philipp Leusmann wrote:
Hi,
is there a way to use my Belkin F6H650
: Peter Selinger [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 19. Oktober 2006 14:52
An: Philipp Leusmann
Cc: nut-upsuser@lists.alioth.debian.org
Betreff: Re: [Nut-upsuser] Belkin F6H650 on USB port
You should first get a current version of NUT. Get release 2.0.4 or
later
don't know about. I am not very hopeful about
being able to guess it. -- Peter
-Urspr=FCngliche Nachricht-
Von: Peter Selinger [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 19. Oktober 2006 19:18
An: Philipp Leusmann
Cc: Nut-upsuser@lists.alioth.debian.org
Betreff: Re: AW: [Nut
Dear Gabriel,
we would need some information to be able to help you, for example:
* NUT version
* operating system type and version
* what driver were you using
* what did you do
* what error messages did you get?
-- Peter
Gabriel =?iso-8859-1?q?Fern=E1ndez?= wrote:
I have not been able to
Hi Carlos,
as far as I know, there is a standard serial over USB interface. I
think the USB specification discourages such interfaces.
All the serial over USB devices that I have seen have used a
manufacturer-specific hack. So connecting to a USB device should not
usually be as simple as
Philipp
-Urspr=FCngliche Nachricht-
Von: nut-upsuser-bounces+philipp.leusmann=3Drwth-
[EMAIL PROTECTED] [mailto:nut-upsuser-
[EMAIL PROTECTED] Im
Auftrag von Peter Selinger
Gesendet: Donnerstag, 2. November 2006 03:54
An: Carlos Rodrigues
Cc: [EMAIL PROTECTED]; nut-
[EMAIL
Yes, this has been fixed some time ago in the SVN version. -- Peter
Magnus Johansson wrote:
Hi!
I'm running NUT 2.0.4 and occasionally I get a segfault when starting
newhidups and if I don't get a segfault when starting newhidups the
process starts eating away at my memory. I sat down
I can only guess. Perhaps you are starting the components in the wrong
order? You have to start:
First the driver (upsdrvctl).
Second upsd.
Third upsmon.
-- Peter
=?ISO-8859-1?Q?Pedro_C=F4rte-Real?= wrote:
On 11/12/06, Peter Selinger [EMAIL PROTECTED] wrote:
Try an analogous setting
To answer that question, we would have to see the script. This is not
the Ubuntu/Debian mailing list, so what's standard to them may not be
standard to us. -- Peter
=?ISO-8859-1?Q?Pedro_C=F4rte-Real?= wrote:
On 11/13/06, Peter Selinger [EMAIL PROTECTED] wrote:
I can only guess. Perhaps you
for communication. In other words, it is intended to be
started as:
upsd
and not
upsd
If upsd is started in the latter way, then upsmon could be started too
soon. -- Peter
=?ISO-8859-1?Q?Pedro_C=F4rte-Real?= wrote:
On 11/13/06, Peter Selinger [EMAIL PROTECTED] wrote:
To answer that question
Hi Bryan,
thanks for your report. I am not sure what issue you are referring to.
All the output you posted appears to be normal. Did the driver give
you any particular problems? -- Peter
Bryan Bond wrote:
I am having an issue running NUT and using an TrippLite OMNI900LCD.
When I run
=?ISO-8859-1?Q?Pedro_C=F4rte-Real?= wrote:
/etc/nut/upsd.conf is world readable
/etc/nut/upsd.users is world readable
That is probably a really bad idea, since /usr/etc/upsd.users contains
passwords that would allow any user to shut down your machine.
-- Peter
Arjen de Korte wrote:
I guess the problem is that Synchronizing... step.
Indeed. Either the driver needs more time to dump all the data than is
allowed for in upsd or it could also be that the first connection to the
driver always fails. Since we first declare a driver stale before
Eric Masson wrote:
Arjen de Korte a =E9crit :
Hello Arjen,
This is a different problem, your driver is not answering at all and it
looks like the dumpall command is not processed. Upgrading to the lates=
t
development version would be a good idea now, since a few things have
Your problem may be related to the way upsd and upsdrvctl interact.
There are several ways to start the driver:
(1) newhidups [options] auto
(2) newhidups [options] -a myprofile
(3) upsdrvctl start myprofile
where myprofile is the name of a profile defined in ups.conf.
Except for testing
upsd installed from an older version).
-- Peter
Eric Masson wrote:
Peter Selinger a =E9crit :
Hello Peter,
Your problem may be related to the way upsd and upsdrvctl interact.
There are several ways to start the driver:
=20
(1) newhidups [options] auto
(2) newhidups [options
Hi Tim,
if you are using NUT 2.0.4, then you should look at the instructions
in the file INSTALL. Step 2 is the following:
2. Build the programs.
make
Optionaly, you can also build the USB drivers (requires libusb) using:
make usb
The same goes for the SNMP driver
Hi Marek,
you should use newhidups, not hidups. -- Peter
Marek Szuba wrote:
Hello,
I have encountered problems trying to set up nut to work with APC BackUps Pro
CS connected over USB to an AMD64 machine running Debian. While apcupsd works
fine with that device, whenever I start upsd I
CyberPower support was added to newhidups after release 2.0.3 (a very
old release). You should use NUT 2.0.4, or even better: the newest
development snapshot from SVN (http://www.networkupstools.org/source.html)
-- Peter
henri wrote:
i can't seem to get newhidups to detect my UPS..
i'm
HID v1.11 Device [Belkin Belkin UPS] on usb1:2.0
- jamie
On Dec 8, 2006, at 4:22 PM, Peter Selinger wrote:
Jamie Fiedler wrote:
is there a way to override the productid (like -x productid=3D1234)
when using newhidups?
Hi Jamie, I like simple yes/no questions! The answer is yes
Did you set correct permissions on /dev/tts/0? If that device is owned
by root, then your driver cannot write to or read from it. -- Peter
Vitaly Oborsky wrote:
Good afternoon. I try to put nut on gentoo. Has executed installation
by a standard command emerge nut. All has passed successfully.
Hi Marc,
the answer to your question is contained in the file INSTALL,
distributed with NUT, section 6 Set ownership data and permissions on
your serial or USB ports that go to your UPS hardware.
Quote:
The setup for USB ports is slightly more complicated. Device
files for USB devices,
Miwa Forever wrote:
2006/12/28, Peter Selinger [EMAIL PROTECTED]:
Miwa Forever wrote:
Hello.
So as my english is not so good, i'll try to write my story in bash
commands
:o)
[EMAIL PROTECTED] uname -mrs
FreeBSD 5.5-STABLE i386
[EMAIL PROTECTED] su
[EMAIL
Arjen de Korte wrote:
Miwa Forever wrote:
As for changing MAXAGE directive - with values 60 and greater ups become
available from pc, at least i can see it's state with upsc. But in
/var/log/messages we can see next:
Dec 29 17:13:37 zork3 upsd[14370]: UPS [MGE-Ellipse] data is no
Daniel Gimpelevich wrote:
On Sat, 30 Dec 2006 15:15:45 -0400, Peter Selinger wrote:
Hi Daniel,
we have seen device 0d9f/0001 before (possibly under a different name,
but this is common), and as far as I remember we could not get it to
work. See the thread named Gentoo Ultra USB UPS
Please upgrade to NUT 2.0.5-pre2. APC support was much improved since
2.0.4.
Also, try these instructions:
http://www.mathstat.dal.ca/~selinger/ups/backups.html
If it still doesn't work, please write to the list again with more
specific information.
-- Peter
Ernest Aigner wrote:
Hello,
Paul Cooley wrote:
Hello NUT-UPSUSERS,
I would just like to try and help other and indicate that I was able to use
the development trunk and get the Tripp Lite OMNI1000LCD UPS (USB) working
with the newhidups drivers on Gentoo Linux. The one that is currently
available at many local
Hi Richard,
This is bizarre. Using -DD, you should get more output between debug
level is '2' and No appropriate HID device found. You should at
least get something like:
debug level is '2'
Checking device (/) (005/001)
- VendorID:
- ProductID:
- Manufacturer: Linux
This question has a clear answer: no. There is no such Make/Config
option.
However, why not just do the following?
./configure [options]
cd clients
make upsmon upsc
You can't use make install with this method. But if you have to, you
could install these two binaries by hand:
cp upsmon
1 - 100 of 150 matches
Mail list logo
