Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Finding the UPS serial port under OBSD

32 views
Skip to first unread message

Panagiotis Atmatzidis

unread,
Apr 29, 2007, 7:15:32 AM4/29/07
to
Hello,

I have a Guard 1500 S serial UPS. I want to make it work with openbsd
& NUT. I installed from source the latest NUT stable version. I found
the driver and everything should be fine except from the fact that I
can't understand which serial port to use!
I tried to locate the UPS through stty but every device I tried
returns the same results. Can someone tell me a way to find out the
serial device that the UPS listens?

I tried out /dev/tty0X and /dev/cua0X but with no positive results.

Thank you,

Panagiotis

Steve at fivetrees

unread,
Apr 29, 2007, 2:40:34 PM4/29/07
to
"Panagiotis Atmatzidis" <p.atma...@gmail.com> wrote in message
news:1177845332.4...@n76g2000hsh.googlegroups.com...

Hmmm. /dev/cua00 works for me (after re-assigning permissions to
_ups:wheel).

Is the serial port enabled in the BIOS? Are you using the correct cable (in
the case of APC, at least, they're non-standard)?

Steve
http://www.fivetrees.com


Panagiotis Atmatzidis

unread,
May 1, 2007, 9:15:02 AM5/1/07
to
Hi

Ο/Η Steve at fivetrees έγραψε:


> "Panagiotis Atmatzidis" <p.atma...@gmail.com> wrote in message
> news:1177845332.4...@n76g2000hsh.googlegroups.com...
> > Hello,
> >
> > I have a Guard 1500 S serial UPS. I want to make it work with openbsd
> > & NUT. I installed from source the latest NUT stable version. I found
> > the driver and everything should be fine except from the fact that I
> > can't understand which serial port to use!
> > I tried to locate the UPS through stty but every device I tried
> > returns the same results. Can someone tell me a way to find out the
> > serial device that the UPS listens?
> >
> > I tried out /dev/tty0X and /dev/cua0X but with no positive results.
>
> Hmmm. /dev/cua00 works for me (after re-assigning permissions to
> _ups:wheel).

Yeah these are both setup correctly according with the guide. The
error I get is the following:

# upsdrvctl start
Network UPS Tools - UPS driver controller 2.0.3
Network UPS Tools - PowerCom and similars protocol UPS driver $
Revision: 0.5 $ (2.0.3)

data receiving error (-1 instead of 11 bytes)

It's the same on every port. However take a look here:

# lsof |grep -i ups
powercom 31236 _ups cwd VDIR 0,4 512 123847 /var/
db/nut
powercom 31236 _ups txt VREG 0,6 3953635 989217 /usr/
lib/libc.so.39.3
powercom 31236 _ups txt VREG 0,6 42571 824364 /usr/
libexec/ld.so
powercom 31236 _ups txt VREG 0,6 43428 86078 /usr/
local/bin/powercom
powercom 31236 _ups txt VREG 0,4 5678 164873 /var/
run/ld.so.hints
powercom 31236 _ups 0u VCHR 2,2 0t0 1434 /dev/
null
powercom 31236 _ups 1u VCHR 2,2 0t0 1434 /dev/
null
powercom 31236 _ups 2u VCHR 2,2 0t0 1434 /dev/
null
powercom 31236 _ups 3u unix 0xd5e7b5a0 0t0 -
>0xd5ff70cc
powercom 31236 _ups 4u VCHR 8,129 0t3 1146 /dev/
cua01
powercom 31236 _ups 5u unix 0xd5e7b66c 0t0 /var/
db/nut/powercom-cua01
# upsdrvctl stop
Network UPS Tools - UPS driver controller 2.0.3
Stopping UPS: Guard
# lsof |grep -i ups
#

which means that it binds the port to /dev/cua01 (I'm using second
serial marked B on the external case which is factory builded).

stty reports device busy when the driver is started...

Any ideas? :-/

0 new messages