Hello,
here are my notes on ups, usb and freebsd.
http://www.netng.org/bin/view/Main/NetworkUpsToolsUsb
HTH, -vlado
On Sun, 26 Nov 2006, Daniel O'Connor wrote:
On Friday 24 November 2006 00:33, Eric Masson wrote:
upsd monitors mge-shut without any glitch now.
I've had a kernel crash in usb su
On Monday 27 November 2006 10:20, Vladimir Botka wrote:
> here are my notes on ups, usb and freebsd.
> http://www.netng.org/bin/view/Main/NetworkUpsToolsUsb
I found I could read status OK (MGE Pulsar Extreme) but I could not set any
variables so I couldn't shut the UPS down.
--
Daniel O'Connor
On Friday 24 November 2006 00:33, Eric Masson wrote:
> upsd monitors mge-shut without any glitch now.
>
> I've had a kernel crash in usb subsystem while playing with newhidups
> yesterday evening, so usb stack could be the problem.
>
> I'll check with FreeBSD 6.2-RELEASE as soon as it becomes avail
Arjen de Korte a écrit :
Hello Arjen,
Could you try with the dummy-ups driver from SVN? Please add the following
two lines to your ups.conf file:
[dummy]
driver = dummy-ups
I've tried with mge-shut :
[EMAIL PROTECTED]:~> cat /usr/local/etc/nut/ups.conf
# Network UPS Tools: example up
> In my setup, upsd has never succeeded in connecting to newhidups.
Could you try with the dummy-ups driver from SVN? Please add the following
two lines to your ups.conf file:
[dummy]
driver = dummy-ups
If upsd is not able to monitor this dummy UPS, there is something very
wrong in your
> Is it possible to just use newhidups & upsd from latest svn to test or
> do I have to install the whole stuff ?
You'll need the full source, since there are changes in other parts of the
sources that are relevant too. Provided you make sure you start up the
driver in the correct way (preferably
Arjen de Korte a écrit :
Hello Arjen,
From SVN r595 the problem with the startup delay of upsd and
'synchronizing giving up' should be fixed.
Ok.
Is it possible to just use newhidups & upsd from latest svn to test or
do I have to install the whole stuff ?
Basically, this is a cosmeti
Eric Masson wrote:
> If I launch newhidups via :
> [EMAIL PROTECTED]:~# /usr/local/libexec/nut/upsdrvctl start mge
> Network UPS Tools - UPS driver controller 2.0.4
> Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4)
>
> Detected a UPS: MGE UPS SYSTEMS/ELLIPSE
> Using subdriver: MGE HID 0.9
Arnaud Quette a écrit :
'Lut Arnaud.
sorry for the late of the answer, but as told previously, I just had
my 2nd baby...
Félicitations, et à la maman aussi ;)
the problem seems to come, as Peter told, from the way you launch the
driver.
Ok.
upsd tells us that it's connected ("Connected
Peter Selinger a écrit :
Hello Peter,
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 defi
Arjen de Korte a écrit :
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 latest
development version would be a good idea now, since a few things have
changed in the newhidups driver lately.
> I've just received a mail from Pedro Côrte Real telling me that waiting
> before launching upsd could solve the problem.
>
> I've tried, but no luck. newhidups was launched 2 hours ago, and I tried
> to launch upsd 15 minutes ago.
>
> upsd output is :
> [EMAIL PROTECTED]:~> sudo upsd - -u ro
Eric Masson a écrit :
Hello,
I've tried to stop and relaunch it many times but output is always the
same.
I've just received a mail from Pedro Côrte Real telling me that waiting
before launching upsd could solve the problem.
I've tried, but no luck. newhidups was launched 2 hours ago, and
13 matches
Mail list logo
