>> 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)
/safenet -a everpower1000 -D
> I think that the problem is that the device d
Hi Chris,
I am cc'ing this to the nut-upsuser mailing list.
Chris Hotte wrote:
>
> Hello Peter! First of all, allow me to thank you in advance for all the
> work and information you have assembled on UPS devices.
>
> I'm currently (not a pun) investigating UPS solutions for my Linux based
> s
2006/7/24, Charles Lepple <[EMAIL PROTECTED]>:
On 7/23/06, Kjell Claesson <[EMAIL PROTECTED]> wrote:> Hi Phil.>> lör 2006-07-22 klockan 12:25 -0500 skrev Phil DeBoest:> > I downloaded the latest development tree (revision 471), ran configure
> > with the following command:> > ./configure --with-use
On 7/23/06, Kjell Claesson <[EMAIL PROTECTED]> wrote:
Hi Phil.
lör 2006-07-22 klockan 12:25 -0500 skrev Phil DeBoest:
> I downloaded the latest development tree (revision 471), ran configure
> with the following command:
> ./configure --with-user=nut --with-drivers=tripplite-hid
[...]
It bombs
> # /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
Here's the relevant /proc/bus/usb/devices output:
T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 3 Spd=1.5 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=09ae ProdID=2005 Rev= 0.10
S: Manufacturer=Tripp Lite
S: Product=TRIPP LITE UPS
S: SerialNumber=692195 A
C
What does /proc/bus/usb/devices say about the UPS?
--
- Charles Lepple
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
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/
Thanks Kjell for the help with the build problem. Thanks for your input,
too, Charles.
Now I have a new problem that I think has already been solved. I have
Tripp Lite Smart1000LCD UPS (usb), but I can't get the newhidups driver
to communicate correctly. I found a thread on the development lis
Hi Daniel,2006/6/29, Daniel Johansson <[EMAIL PROTECTED]>:
Hello, I recently had a failure with my old MGE ESV8 ups, it just diedon me so I had to get a new one. I found a MGE ESV8+ cheap andeverything seems to work fine with it except the communication with thecomputer. The old ESV8 (non +) worked
Hello, I recently had a failure with my old MGE ESV8 ups, it just died
on me so I had to get a new one. I found a MGE ESV8+ cheap and
everything seems to work fine with it except the communication with the
computer. The old ESV8 (non +) worked fine with NUT after applying some
patches I got fro
> 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 interna
> 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 internal
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]: Ca
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
this
15 matches
Mail list logo