On 12/05/99 [EMAIL PROTECTED] wrote:
| > BAD ----->>>> 05/11 17:47:29 yS1 send: \dATQ0V1H0[0d]
| > BAD ----->>>> 05/11 17:47:30 yS1 waiting for ``OK''
| > BAD ----->>>> 05/11 17:47:30 yS1 got: [0d][0a]NO CARRIER
| > BAD ----->>>> 05/11 17:47:30 yS1 found action string: ``NO CARRIER''
| > BAD ----->>>> 05/11 17:47:30 yS1 init chat failed, exiting...: Invalid argument
| > BAD ----->>>> 05/11 17:47:30 ##### failed in mg_init_data, dev=ttyS1, pid=1585
| >
| What's BAD here? mgetty just resets modem (by lowering
| DTR), sends init string (just first line you marked as BAD?) and of
| cource he is waiting for 'OK', but got 'NO CARRIER'. So BAD is 'NO
| CARRIER' answer (reasons?).
I've marked a block of sequence that will fail during the init stript to show
what is going on. The first one is the correct init sequence (default).
The problem is that sometime (you must read randomly) the modem fail with
the 'NO CARRIER' answer. I think the problem is when pppd hangs, after
this the modem don't have enough time to send 'NO CARRIER' because the
port is closed to fast, so when mgetty reopen the port, and send the init
script will got the 'NO CARRIER' in place of the expected 'OK'.
| So you can play with init string but for me that looks like hardware
| problem. Try to update firmware of modem, it can help.
Yes! This is what I'm trying to do.
Roberto.
Xmeo 4.b9 on Windows 95 4.0 (Pentium)
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
