Hello list.
I'm contemplating buying new batteries and putting an older APC
Smart-UPS 3000XL back into service. Would that work well with NUT? Any
drawbacks to consider?
Thank you,
Tobias
--
Tobias Balle-Petersen
Kontrapunkt Group / System Administrator
Hello Kjell.
Kjell Claesson wrote:
You have been busy i see. OK it is possible to set the 9120 to requsted mode
only, and this is done by the serial driver part. And it should remain so
after power cycling.
How is this accomplished? Any chance of a step by step tutorial?
One thing that
Hello Arjen.
Arjen de Korte wrote:
In general, shutdown will be triggered when the UPS is both on battery
*and* reporting low battery. The latter may or may not be user
configurable. In your case, it looks like the driver has no way of
changing this level, so when this actually happens
Arnaud Quette wrote:
the source repository is also there (now) if you will to rebuild the package
;-)
Hmmm... I guess I need a kernel newer than the one in atable:
Unpacking nut (from nut_2.2.0-1_powerpc.deb) ...
Setting up nut (2.2.0-1) ...
udev requires a kernel = 2.6.15, not started.
Hi Arnaud.
Arnaud Quette wrote:
the source repository is also there (now) if you will to rebuild the package
;-)
Great, sounds good. I was just about to compile from the source on the site. I
guess this way is
better/easier. I'll give it a try and report back.
Thanks,
Tobias
Hello...
Just to make sure I did a clean install of debian etch and tested. I still get
the same errors. Nut
2.0.4.
Tobias
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Hello
Kjell Claesson wrote:
Then you should get new version of nut as 2.0.4 is past date.
I have updated to nut 2.2.0-1 as suggested. Unfortunately I still get the same
type of errors:
Network UPS Tools - UPS driver controller 2.2.0-
Network UPS Tools - BCMXCP UPS driver 0.11 (2.2.0-)
Hello Arjen.
Arjen de Korte wrote:
Have you tried the serial connection?
No, there is no serial port on my machine.
1) Apparently, this UPS needs to be told only to reply to specific
requests and not send unsollicited status updates. The bcmxcp (serial)
driver supposedly does this, the
Tobias Balle-Petersen wrote:
Hmmm... I guess I need a kernel newer than the one in atable:
Just realized I dont have the etch stable kernel on my testing system. Igonre
the above.
Thanks,
Tobias
___
Nut-upsuser mailing list
Nut-upsuser
Hi Arnaud.
Arnaud Quette wrote:
add this line to your /etc/apt/sources.list:
deb http://opensource.mgeops.com/stable/debian binary/
I'm running on a PowerPC. The repository only has i386 packages as far as I can
tell.
Tobias
___
Nut-upsuser
Hello all.
I have now connected the UPS via a serial-cable to a PC running Debian Etch and
Nut 2.0.4.
When running upsdrvctl -u root start I get:
Communications with UPS lost: Error executing command
Communications with UPS lost: Error executing command
Communications with UPS lost: Error
Hi Kjell.
Kjell Claesson wrote:
It looks like you have a problem with the usb connection. Check the cabling.
The driver is using a binary protocol with checksum, and is hard on bit
errors.
I have tried two different USB-cables. The one that came with the UPS and
another one I had lying
-driver does not allow the
UPS to be shut down. This is why I am now turning to USB.
Any ideas as to how I can get my setup running?
Thank you,
Tobias Balle-Petersen
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http
13 matches
Mail list logo