public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: Ross Boylan <RossBoylan@stanfordalumni.org>
To: linux-serial@vger.kernel.org
Cc: Ross Boylan <RossBoylan@stanfordalumni.org>
Subject: Update on problems with UPS
Date: Thu, 20 Feb 2003 22:32:20 -0800	[thread overview]
Message-ID: <20030221063220.GF5567@wheat.boylan.org> (raw)

I wrote a few weeks ago about some problems using an APC UPS with the
serial port.

I've made some progress, but things are still not quite working right.

Originally, I got "LSR safety check engaged" on ttyS1 where the APC
was connected.  This went away when I disabled COM1 (aka ttyS0) in
BIOS, since I no longer use it.  However, I am still sharing an IRQ
between ttyS2 (from my ISA modem card) and the parallel printer.

It's not clear the sharing is causing trouble--both seem to be working
OK.  Does anyone know if it's a problem?

At any rate, it is puzzling to me that I can't control the IRQ for the
modem.  Only COM1/2 are configurable from BIOS.  I can also control
the parallel port from the BIOS, and I though putting it to IRQ5 would
force COM3 elsewhere.  It doesn't seem to.  I can reprogram the modem
through isapnp, but unless I put it to the IRQ 5 that ttyS2 gets on
startup, it doesn't work.  (Some people suggested the card might be
set through jumpers, but it's not).  I've also tried restarting after
reprogramming the modem, in hopes the new IRQ would stick, but it
doesn't.

Can anyone clarify what is going on with COM3?  I thought the modem
serial port was actually part of the card, and that reseting the card
through pnp would change the modem and the serial port.  The behavior
I'm seeing looks more like the serial port and the modem are distinct
devices, and pnp only affects the modem.  (My other theory is that pnp
affects both, but the serial driver doesn't know what's going on if I
move the location after startup.  This would also explain why the
modem doesn't work after I move the IRQ, but I thought I understood
someone on this list saying the serial driver could cope with such
moves.) 


On the original problem with the UPS, there is progress too.  It is no
longer disabled by the system.  I believe the cause is the the apcupsd
demon can now talk to the port, and puts more appropriate values out
to it.

Things aren't quite right at this level either, because the demon is
not responding, or responding properly, to power out signals.  I have
not yet had time to triple check my configuration settings for the
software; they might be off.  Or the software may not be quite right
for the cable I have, which has a slightly different model number than
any listed in the apcupsd software description.

Thanks for taking the time to read this.  If you have any thoughts,
answers or suggestions, I'd love to hear them.

             reply	other threads:[~2003-02-21  6:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-21  6:32 Ross Boylan [this message]
2003-02-21 10:41 ` Update on problems with UPS Gerald Emig
2003-02-23  8:01 ` David Lawyer
2003-02-27 20:42   ` Ross Boylan
  -- strict thread matches above, loose matches on Subject: below --
2003-02-27 21:29 Ed Vance
2003-02-27 21:49 ` David Lawyer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030221063220.GF5567@wheat.boylan.org \
    --to=rossboylan@stanfordalumni.org \
    --cc=linux-serial@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox