Citeren Arnaud Quette [EMAIL PROTECTED]:
Attached is a patch adding support for tripplite's avr750u UPS.
Issues:
* productid still needs to be specified in ups.conf
you missed to add an entry in drivers/tripplite-hid.c
-tripplite_claim() for that ;-)
And beware that you need to put it in
Citeren Charles Lepple [EMAIL PROTECTED]:
Going out on a limb here, maybe it's something that we have to
explicitly poll (versus waiting for it to be reported on the interrupt
pipe), for the times when it is below 100%.
The usbhid-ups driver polls for practically all variables. The polling
Citeren Raphael Geissert [EMAIL PROTECTED]:
Attaching the output of usbhid-ups -.
That sucks... :-(
This device doesn't seem to report any measured voltage value, so I
wouldn't be surprised if the battery charge would something like an
online/onbatt flag too (100% @ online and 0% @
that is the case for usbhid-ups: the various functions that accept a
TIMEOUT use 4 sec...
That is still incorrect and I want to change that in the not so distant
future (time permitting). Unfortunately, that also requires some changes
in the hid_ups_walk() function that are not so trivial.
[...]
The output of lsusb and ls -lR /dev/bus/usb is the same for the two
versions.
thanks for your quick feedback Sven.
@Carlos: there is a clear regression here.
Poor Carlos, he is getting all the flak, while the problem is in the
megatec_usb.c... :-)
I'm thinking of a recent timeout
You may not be aware of it, but this is where the root of the problem
lies. Normally, when a UPS is told to shutdown, two things can happen:
1) The input power is gone and the UPS powers off and switches back on
when the power returns.
2) Input power is still available and the UPS cycles
tags 441342 upstream
thanks
Hi Robert,
thanks for your report and investigation.
We will check to fix this and give you news back.
2007/9/9, Robert Woodcock [EMAIL PROTECTED]:
Package: nut
Version: 2.2.0-2
Severity: important
I recently set up nut at work to monitor the 15 APC
I tried stracing /lib/nut/newhidups:
write(2, Path: UPS.Battery.ff86001b, Type..., 59) = 59
write(2, entering path_to_string()\n, 26) = 26
write(2, Looking up 00840004\n, 20) = 20
write(2, Looking up 00840012\n, 20) = 20
write(2, Looking up ff860016\n, 20) = 20
write(2, entering
Justin Piszcz wrote:
I've not had time (nor will have) to digg all the thread on the nut
ml, so can you update me about the status of the below one please.
Yeah basically any version newer than 2.0.4 says the battery is low
(which is incorrect) so for now I set it to hold at that version,
Justin Piszcz wrote:
$ ./configure --with-user=nut --with-group=nut
--prefix=/app/nut-trunk-1091
checking sys/time.h presence... yes
checking for sys/time.h... yes
./configure: line 5460: NUT_TYPE_SOCKLEN_T: command not found
./configure: line 5461: NUT_TYPE_UINT16_T: command not found
when configuring nut 2.2.0 the variable/symbol [EMAIL PROTECTED]@' is not
resolved by the libupsclient-config script. The attached patch changes
[EMAIL PROTECTED]@' to [EMAIL PROTECTED]@'
[EMAIL PROTECTED]@' to [EMAIL PROTECTED]@'
which should solve this issue.
This was already solved in
11 matches
Mail list logo
