Modem doesn't pick up

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

The modem works fine on a other machine with the same cable. I never had
problems with the serial port before but it is possible that it's broken.
Could there be another reason for this behavior??

THNX, Sjoerd

-----Oorspronkelijk bericht-----
Van: Gert Doering <gert@greenie.muc.de>
Aan: svenema@comcare.nl <svenema@comcare.nl>; mgetty@muc.de <mgetty@muc.de>
Datum: donderdag 17 juni 1999 9:08
Onderwerp: Re: Modem doesn't pick up


>Hi,
>
>On Wed, Jun 16, 1999 at 01:40:02PM +0200, Sjoerd Venema wrote:
>> Hi, I'm trying to get mgetty to work. It seems that the program checks
>> the modem but the modem doesn't pick up the modem. In the logfile I get
>> the following message:
>>
>> > 06/16 12:38:33 yS1  mgetty: experimental test release 1.1.19-Nov24
>> > 06/16 12:38:33 yS1  check for lockfiles
>> > 06/16 12:38:33 yS1  locking the line
>> > 06/16 12:38:34 yS1  WARNING: DSR is off - modem turned off or bad
cable?
>> > 06/16 12:38:34 yS1  lowering DTR to reset Modem
>> > 06/16 12:38:34 yS1  send: \dATQ0V1H0[0d]
>> > 06/16 12:38:35 yS1  waiting for ``OK''
>> > 06/16 12:38:55 yS1  timeout in chat script, waiting for `OK'
>> > 06/16 12:38:55 yS1  init chat timed out, trying force-init-chat
>> > 06/16 12:38:55 yS1  send: \d[10][03]\d\d\d+++\d\d\d[0d]\dATQ0V1H0[0d]
>> > 06/16 12:38:59 yS1  waiting for ``OK''
>> > 06/16 12:39:19 yS1  timeout in chat script, waiting for `OK'
>> > 06/16 12:39:19 yS1  init chat failed, exiting...: Interrupted system
call
>> > 06/16 12:39:19 ##### failed in mg_init_data, dev=ttyS1, pid=177
>
>Looks like "no modem connected", or "broken serial cable", or "broken
>serial port".
>
>You sure you have connected the modem to ttyS1 (which is COM2 !! under
>DOS)?
>
>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
>