Gustav:
I finally figured out one of the problems. In minicom, the default port
was /dev/ttys0 (note the case). As soon as I went back and changed this,
voila, instant sucess in minicom. I was able to send AT commands, and
kept getting OK back from the modem.
second, even though I don't have a modem on /dev/ttyS1, I set minicom to
now look at /dev/ttyS1. Installed of failing like it did before, it
recognized it as a valid tty, and actually started up minicom. The screen
just sat there, because the initialization string won't do anything if
there is no modem there. But, I was in the terminal window :)
Now the question left to figure out is, why does the install script for
the UPS not see /dev/ttyS1 as a valid tty. Apparently, it runs a binary
to actually check the tty, a program called ttycheck. In the script, it
has a case statement checking on the exit status of running ttycheck.
I'm baffled at this point. I'm gonna see if I can borrow a firend's
external modem, and insure that COM 2 is working.
The only thing I saw in the install script was a mention that the UPS
needed to have exclusive access to COM 2, if that was the port I selected
to install on. I do not have anything else using that port, as nothing
else is plugged into it.
Hope this helps a litle more. We're getting closer :)
- Mike
On Fri, 4 Feb 2000, Gustav Schaffter wrote:
> I'm not a minicom expert.
>
> You did that as root, right?
>
> No other application on ttys0, right?
>
> Did you try ttys1?
>
> Regards
> Gustav
>
>
> "Michael J. McGillick" wrote:
> >
> > Gustav:
> >
> > As a follow-up to this, when I try to start up minicom, as either root
> > with the -s option, or as a normal user, I get the error message:
> >
> > minicom: cannot open /dev/ttys0: Input/output error
> >
> > Any ideas?
> >
> > - Mike
> >
> > On Fri, 4 Feb 2000, Gustav Schaffter wrote:
> >
> > > Michael,
> > >
> > > When you say, "I get the prompt back", does the APC on COM2 actually
> > > *tell* you something? If so, what?
> > >
> > > Do you have any old external modem laying around? Even a 2400bps or
> > > slower will do.
> > >
> > > If so, connect it to ttys1 (Yes, COM2) and use minicom to talk to it.
> > > Your 'AT' commnad should return 'OK'. So, you have contact with the
> > > outside world through ttys1.
> > >
> > > Some (most?) APC units need to have the DIP switches correctly set to be
> > > able to talk to a PowerChute software. (Read the APC manuals.) Have you
> > > been able to run PowerChute to this unit under another OS?
> > >
> > >
> > > Regards
> > > Gustav
> > >
> > >
> > > "Michael J. McGillick" wrote:
> > > >
> > > > Evening:
> > > >
> > > > I'm working on trying to get the APC Powerchute software to work on my
> > > > Linux box. The first thing I did was go in and check the BIOS settings
> > > > for my machine. I have COM 1 disabled, because I have an internal U.S.
> > > > Robotics Courier V.Everything installed. Com 2 is configured and has the
> > > > normal ioports associated with it (I believe this is 2F8 or something like
> > > > that). I also booted to a DOS disk, adn tried from the command line the
> > > > following 2 commands:
> > > >
> > > > echo "AT" > com1
> > > > echo "AT" > com2
> > > >
> > > > In both cases, I get the prompt back, which tells me that the machine is
> > > > recognizing both ports and is able to talk to them.
> > > >
> > > > I then booted my machine into Linux, and downloaded and installed the
> > > > latest powerchute rpm from APC's site. It installed just fine, and I
> > > > followed the directions to run the configuration script. I am able to
> > > > answer everything in the installation, and when it asks where the UPS is
> > > > connected to, I select /dev/ttyS1 (COM2 I believe) because this is where
> > > > the cable is connected to on the computer.
> > > >
> > > > When the script finishes, it keeps telling me that /dev/ttyS1 does not
> > > > appear to be a valid tty. What am I doing wrong? Where or what should I
> > > > be looking at to try and resolve this issue?
> > > >
> > > > - Mike
> > > >
> > > > --
> > > > To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> > > > as the Subject.
> > >
> > > --
> > > pgp = Pretty Good Privacy.
> > >
> > > To get my public pgp key, send an e-mail to: [EMAIL PROTECTED]
> > >
> > > Visit my web site at http://www.schaffter.com
> > >
> > >
> > > --
> > > To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> > > as the Subject.
> > >
> >
> > --
> > To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> > as the Subject.
>
> --
> pgp = Pretty Good Privacy.
>
> To get my public pgp key, send an e-mail to: [EMAIL PROTECTED]
>
> Visit my web site at http://www.schaffter.com
>
>
> --
> To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> as the Subject.
>
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.