first of all, I am using version 2.0.2 on kernel 2.6.15
I played with the init.d startup script, and figured it was indeed a
permissions problem accessing the port file.
now I have, as you anticipated, a new problem : the protocol does not
seem to match.
this is what I get when I try:
# /etc/init.d/nut start
Starting Network UPS Tools:Network UPS Tools - UPS driver controller 2.0.2
Network UPS Tools - Generic SafeNet UPS driver 0.03 (2.0.2)
Communications with UPS lost: Status read failed
Communications with UPS lost: Status read failed
SafeNet protocol compatible UPS not found on /dev/ttyS1
Driver failed to start (exit status=1)
(upsdrvctl failed).
any suggestions?
Omry.
Arjen de Korte wrote:
I just got myself a new everpower-1000va.
according to the compatibility list, the 'safenet' driver supposed to
support it,
That depends. The hardware this driver is written for is usually OEM
equipment and vendors tend to shop for the lowest bidder. So quite often
they change the internals of the UPS, without changing the typenumber or
even the box it is packaged in. If your UPS came with 'SafeNet v1.0'
software for Windows (either in the box or via download) it should be
supported by this driver. If something else is bundled, you'll have to
continue your search as it probably won't be supported by this driver.
however, when I try, I get this in syslog:
Jul 24 15:05:22 tv upsd[26458]: Can't connect to UPS [everpower1000]
(safenet-ttyS1): No such file or directory
This usually means the safenet driver isn't running. You may want to run
the driver from the commandline with '-D' added to make it more
verbose. Chances are that it will be telling you why it can't be started.
This can be as trivial as a serial port without the proper permissions.
[...]
I am using nut installed via apt on debian-etch.
This isn't very helpful for people not running Debian. Please list version
number of kernel and NUT.
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser