mgetty-1.1.9 on Solaris2.5.1/Sparc

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

Hi,

Martin Spott wrote:
> > So, how does the mgetty log file look like?
> Here you are:
> 
> --
> 12/16 13:43:13 a/b mgetty: experimental test release 1.1.9-Aug17
[..]
> 12/16 13:43:20 a/b mdm_send: 'AT+FDCC=1,5,0,2,0,0,0,0'
> 12/16 13:43:20 a/b mdm_command: string 'AT+FDCC=1,5,0,2,0,0,0,0'
> 12/16 13:43:20 a/b mdm_command: string 'OK' -> OK
> 12/16 13:43:20 a/b waiting for line to clear (VTIME), read: 
> 12/16 13:43:20 a/b removing lock file
> 12/16 13:43:20 a/b waiting...

Everything fine...

> [ now I start minicom, about ten seconds later I see mgetty's init string in
> my minicom window ]
> 
> 12/16 13:43:34 a/b checking lockfiles, locking the line
> 12/16 13:43:34 a/b makelock(cua/b) called
> 12/16 13:43:34 a/b get_lock_name(cua/b) called
> 12/16 13:43:34 a/b -> ttyname /dev/cua/b
> 12/16 13:43:34 a/b lock file: /var/lock/LK.032.029.131073
> 12/16 13:43:34 a/b do_makelock: lock='/var/lock/LK.032.029.131073'
> 12/16 13:43:34 a/b lock made
> 12/16 13:43:34 a/b waiting for ``RING''

There was *NO* lock file from minicom here, or it was not valid. Please
try again, with "mgetty -x9", and just show me this part, between
 "waiting..."
and
 "waiting for ``RING''"

- this should show why mgetty is ignoring the minicom lock file.

> 12/16 13:43:34 a/b got: [0d]ATZ[0d][0d][0a]OK[0d][0a]

This is what minicom sends to the modem.

> 12/16 13:43:44 a/b timeout in chat script, waiting for `RING'
> 12/16 13:43:44 a/b huh? Junk on the line?
> 12/16 13:43:44 a/b removing lock file

mgetty gives up, and restarts.

> [ here I see a new mgetty starting, but minicom is still running ! ]

... the lock file has long been deleted (because mgetty didn't find it /
or didn't think it was valid).

> 12/16 13:43:49 a/b waiting for line to clear (VTIME), read: 
> 12/16 13:43:50 a/b send: \dATQ0V1H0[0d]
> 12/16 13:43:50 a/b waiting for ``OK''
> 12/16 13:43:50 a/b got: ATQ0V1H0[0d][0d][0a]OK ** found **
> 12/16 13:43:50 a/b send: AT&F0S0=0S10=40Q0W1&D0&K3&C1[0d]
> 12/16 13:43:50 a/b waiting for ``OK''
> 
> [ the following line is the only difference to the fist initialization
> sequence ]
> 
> 12/16 13:43:50 a/b got: [0d][0a]OK ** found **

Minicom is still on the line, and most likely reading the "AT..." command
echo.

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-35655025    gert.doering@physik.tu-muenchen.de
.