It could be afew things.
1) Your serial board seems to be working, though there could be a hardware
conflict somewhere causing this. I am having the same problem right now
with another system I'm putting together....I'm switching from our
Bocaboard to our Stallion to see if it fixes it.
2) Your modems are setup wrong.
3) You need to find the initchat line in the proper mgetty source file
before compiling, and enter the appropriate info for your modems. It should
be easy to find the proper file.
Dan
At 05:17 PM 4/26/1998 -0400, [EMAIL PROTECTED] wrote:
>I followed the instructions on your page. It is laid out nice.
>I am having problems with mgetty though.
>This is the results of my /var/adm/mgetty.ttyS1 log
>it keeps repeating:
>04/26 17:18:25 yS1 mgetty: experimental test release 1.1.12-Jan27
>04/26 17:18:25 yS1 check for lockfiles
>04/26 17:18:25 yS1 locking the line
>04/26 17:18:26 yS1 WARNING: DCD line still active, check modem settings
(AT&Dx)
>04/26 17:18:26 yS1 lowering DTR to reset Modem
>04/26 17:18:26 yS1 send: \dATQ0V1H0[0d]
>04/26 17:18:27 yS1 waiting for ``OK''
>04/26 17:18:47 yS1 timeout in chat script, waiting for `OK'
>04/26 17:18:47 yS1 init chat timed out, trying force-init-chat
>04/26 17:18:47 yS1 send: \d[10][03]\d\d\d+++\d\d\d[0d]\dATQ0V1H0[0d]
>04/26 17:18:51 yS1 waiting for ``OK''
>04/26 17:19:11 yS1 timeout in chat script, waiting for `OK'
>04/26 17:19:11 yS1 init chat failed, exiting...: Interrupted system call
>04/26 17:19:11 ##### failed in mg_init_data, dev=ttyS1, pid=1158
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
