mgetty on BSD/OS 2.0?

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

Hi,

Jack Patton wrote:
> On Tue, 28 Jan 1997, Gert Doering wrote:
> 
> > Sounds like your modem is not answering, but *is* correctly receiving the
> > AT commands (and the serial port is working).
> > 
> > Please try sending the modem an ATE1Q0V1, to make sure it will send
> > answers back (mgetty should do that itself, but you don't state which
> > version you use, nor did you include a log file *sigh*)
> 
> Hi Gert,
>  We just tried it with yesterday's release and get the same deal. Here is 
> an exerpt from the log file:
>  
> 01/29 12:40:42 B0f  mgetty: experimental test release 1.1.1-Jan28
[..]
> 01/29 12:40:43 B0f   tio_set_flow_control( HARD )
> 01/29 12:40:43 B0f   waiting for line to clear (VTIME), read: 
> 01/29 12:40:44 B0f  send: \dATQ0V1H0[0d]
> 01/29 12:40:44 B0f  waiting for ``OK''
> 01/29 12:40:44 B0f   got: 
> 01/29 12:41:04 B0f  timeout in chat script, waiting for `OK'

Hmmm, please try again with "FLOW_DATA" set to "FLOW_SOFT". It *might* be
some SunOS'ish weirdness (port not receiving data while DCD is low, *IFF*
hardware flow control is enabled), but I seriously doubt it.

Can you access the modem with a terminal program (cu, minicom) at the
selected port speed? Maybe simply your modem or serial port is broken.

gert

-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             gert@greenie.muc.de
fax: +49-89-3545980                         gert.doering@physik.tu-muenchen.de