Run the driver in debug mode, I already suggested this in the previous
message. The driver will be more verbose about what the cause is that it
won't run.
how do I run it in debug mode?
Run (as root)
path to driver/safenet -a everpower1000 -D
I think that the problem is that the
Here is my output:
# /lib/nut/safenet -a everpower1000 -D
Network UPS Tools - Generic SafeNet UPS driver 0.03 (2.0.2)
debug level is '5'
C : ZCADLIOPERJD
S : [empty]
C : ZCADLIOPERJD
S : [empty]
C : ZCADLIOPERJD
S : [empty]
C : ZCADLIOPERJD
S : [empty]
Communications with UPS lost:
Omry Yadan wrote:
Here is my output:
# /lib/nut/safenet -a everpower1000 -D
Network UPS Tools - Generic SafeNet UPS driver 0.03 (2.0.2)
debug level is '5'
C : ZCADLIOPERJD
S : [empty]
C : ZCADLIOPERJD
S : [empty]
C : ZCADLIOPERJD
S : [empty]
C : ZCADLIOPERJD
S :
Hi List,
I just got myself a new everpower-1000va.
according to the compatibility list, the 'safenet' driver supposed to
support it,
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
mån 2006-07-24 klockan 15:06 +0300 skrev Omry Yadan:
Hi List,
Hi Omry,
I just got myself a new everpower-1000va.
according to the compatibility list, the 'safenet' driver supposed to
support it,
however, when I try, I get this in syslog:
Jul 24 15:05:22 tv upsd[26458]: Can't
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
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:
#
7 matches
Mail list logo
