Inmarsat Telephon+Modem System

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

Martin Bartsch <Martin@Bartsch.com> wrote:
> The problem is, if he start minicom he get the message /dev/modem is locked.

Has minicom the right to write to the lock directory ?  Can you give
some lines of /var/log/mgetty.ttyS0 (or equivalent lock file) ?

Is /dev/modem used by both mgetty (see /etc/inittab) and minicom ?
Does that device point (ls -la /dev/modem) to /dev/ttyS0 (or 1, or 2,
or 3) or to /dev/cua[0123] (the latter would be wrong) ?

> We have checked the system with an normal modem - it was OK.

You didn't have the /dev/modem locked problem ?  So forget about the
above, and just report the mgetty log file. Presumably mgetty is
attempting to initialize the modem, but fails, and retries, and this
creates the minicom problem above.

> Have you some experience or information about the connection with similar 
> INMARSAT systems?

Did you try *without* mgetty but just with minicom ? Does the ``modem''
answer minicom's AT (or manual) command sequences ?