Linux + Minicom = serial terminal???

Hello all.



Can anyone help me configure minicom to use my null modem cable on ttyS1
in order to log into an old HP server. The serial terminal Howto just
touches the subject but does not go into details.

any information or the location of good docs would be greatly appriciated.

thanks
Jeremy

>>>>> "jtg" == jtg <Jeremy> writes:
jtg>
jtg> Hello all.
jtg> Can anyone help me configure minicom to use my null modem cable
jtg> on ttyS1 in order to log into an old HP server. The serial
jtg> terminal Howto just touches the subject but does not go into
jtg> details.
jtg>
jtg>
jtg> any information or the location of good docs would be greatly
jtg> appriciated.

It all depends on what baud speed, stop bits, etc the old HP is
configured for. Start up minicom and keep changing the parameters
until hitting "enter" gives you the HP login screen. You might start
with 9600 baud, 8N1.

--Rob

In article <3f9f4c45$0$732$(E-Mail Removed)> (E-Mail Removed) (Jeremy)
writes:

>Can anyone help me configure minicom to use my null modem cable on
>ttyS1 in order to log into an old HP server. The serial terminal Howto
>just touches the subject but does not go into details.

You should be able to just plug everything in, configure minicom
to whatever speed/parity/data bits the HP wants, and get a login
prompt. Have you actually tried it yet?

Make sure you're using the proper port; go into "Configire minicom"
(control-A O if you're using the default command prefix), select
"Serial port setup", and make sure "Serial Device" is set to the
proper port (e.g. /dev/ttyS0). To test it, short pins 2 and 3
of the serial port connector together (doesn't matter whether
it's a DB-25 or a DE-9 connector - they swap pins 2 and 3 but
you're still connecting the transmit and receive lines together)
and anything you type should appear on the screen (doubled if
you have local echo turned on).

Make sure you really have a null modem cable and that you really
need one (I'm not sure just what the HP port is like). If it
doesn't work with a null modem, try again with a straight-through
cable.

If none of the above work, post a message with more detail.

>any information or the location of good docs would be greatly
>appriciated.

If you haven't done so yet, try "man minicom".

--
/~\ (E-Mail Removed)lid (Charlie Gibbs)
\ / I'm really at ac.dekanfrus if you read it the right way.
X Top-posted messages will probably be ignored. See RFC1855.
/ \ HTML will DEFINITELY be ignored. Join the ASCII ribbon campaign!

On Wed, 29 Oct 2003 06:55:15 GMT, Rob Ristroph <(E-Mail Removed)> wrote:
>>>>>> "jtg" == jtg <Jeremy> writes:
>jtg>
>jtg> Hello all.
>jtg> Can anyone help me configure minicom to use my null modem cable
>jtg> on ttyS1 in order to log into an old HP server. The serial
>jtg> terminal Howto just touches the subject but does not go into
>jtg> details.
>jtg>
>jtg>
>jtg> any information or the location of good docs would be greatly
>jtg> appriciated.
>
> It all depends on what baud speed, stop bits, etc the old HP is
> configured for. Start up minicom and keep changing the parameters
> until hitting "enter" gives you the HP login screen. You might start
> with 9600 baud, 8N1.

Also use -o switch for minicom so it does not try to initialize (with AT
commands) a non-existing modem on that serial port. Alternately you could
remove modem initialization strings from minicom setup, but then you might
have to put them back in to use it with a real modem.

--
David Efflandt - All spam ignored http://www.de-srv.com/
http://www.autox.chicago.il.us/ http://www.berniesfloral.net/
http://cgi-help.virtualave.net/ http://hammer.prohosting.com/~cgi-wiz/

"Jeremy" <(E-Mail Removed)> wrote in message
news:3f9f4c45$0$732$(E-Mail Removed)...
> Hello all.
>
>
>
> Can anyone help me configure minicom to use my null modem cable on ttyS1

Null Modem - thats a generic term for a whole range of cables - the common
thing is that they all have TX and RX crossed over.

But you then get options

DCD options -
- no DCD. HP needs to be happy with this situation
- DTR loops back to DCD at each end. Each end tricks itself into thinking
the other end is alive (probably only affects HP ).
- DTR from one end drives both ends DCD's.

DSR is used to tell the OS that the modem is actually powered on, but not
normally used. but of course the DTR line could also drive DSR, if
required.


RTS CTS options -
- none - OS needs to be set for XON/XOFF flow control or else there will be
no flow.
- loop back - RTS CTS flow control doesnt work , but flow happens as the
loopback stops RTS CTS flow control stopping flow.

- Crossed over- full hardware flow control - should allow flow control to
work.