Date: Wed, 23 Jun 1999 08:21:55 -0400 (EDT) From: Patrick Gardella <patrick@cre8tivegroup.com> To: "Andre M. Hedrick" <hedrick@Astro.Dyer.Vanderbilt.Edu> Cc: freebsd-questions@freebsd.org, apcupsd-devel@ro.com Subject: Re: PANIC: Cannot talk to UPS! Message-ID: <XFMail.990623082155.patrick@cre8tivegroup.com> In-Reply-To: <Pine.LNX.3.96.990622161207.5355A-100000@Astro.Dyer.Vanderbilt.Edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 22-Jun-99 Andre M. Hedrick wrote:
> On Tue, 22 Jun 1999, Patrick Gardella wrote:
>
>> I recently purchased another APC UPS (APC BackUPS Pro 280) for a
>> machine here in the office. When I went to run a known working copy
>> of apcupsd, it failed with a "PANIC! Cannot talk to UPS" error. I've
>> set the /etc/apcupsd.conf file correctly (UPSTYPE backupspro,
>> UPSCABLE 940-0024B DEVICE /dev/ttyd0).
>
> What is DEVICE /dev/ttyd0 ??
> Is this a raw serial device in FreeBSD?
> If the daemon can not setserial to 2400, then you will need to do
> this with an external tool before you call the daemon.
/dev/ttyd? for callin ports
/dev/ttyid?
/dev/ttyld? corresponding callin initial-state and lock-state
devices
/dev/cuaa? for callout ports
/dev/cuaia?
/dev/cuala? corresponding callout initial-state and lock-state
devices
I've also tried to communicate with the ups directly through the port
using cu -s 2400 -e -o -h -l /dev/ttyd0
Please remember that I have a SmartUPS 1400 working with FreeBSD using
/dev/ttyd0, and I've tried the same version on this system, with the
same problem.
>> Some specifics:
>> APC UPS BackUPS-Pro 280
>> FreeBSD 3.2-STABLE
>> Serial Port= /dev/ttyd0 (on linux, this would be /dev/ttyS0)
>
> Is there a lockpath problem that I do not know about?
If there is, I don't know about it either. fstat doesn't show that the
device is locked either.
Following another lead, I moved my mouse to ttyd0, and then the ups to
ttyd1, with exactly the same problems. (This entailed a reboot, just
to be safe, so the system is "clean".)
Could it be the cable? I don't think so, since Windows (and
PowerChute) communicates with it just fine.
>> The serial port is correctly detected by the kernel:
>> sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa
>> sio0: type 16550A
Patrick
---
Patrick S. Gardella Director of Web Development
The Creative Group 1-800-804-0783 ext 29 606-858-8029 (fax)
http://www.cre8tivegroup.com PGP Key ID 0xEE2D47A9
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.990623082155.patrick>