🚀 go-pugleaf

In <nhBn2.166$7u.530@nsw.nnrp.telstra.net> "ochre small" <reddwarf@octa4.net.au> writes:


>Here's a puzzler...
>getting bizzare error messages from PPP....

...

This is not an error from pppd but from the chat script. It sends the
command ATZ to the modem, and waits for a return OK. It never gets it.

Instead of ATZ try sending ATE1 and see if you get any return from the
modem. (namely an OK). I looks to me like you either have the wrong port
for your modem, have the wrong rate, or have a "winmodem" ( which is a
modem like your tinkertoy car is a real car)

>Jan 14 21:41:17 reddwarf chat[1583]: abort on (NO DIALTONE)
>Jan 14 21:41:17 reddwarf chat[1583]: abort on (Invalid Login)

>Jan 14 21:41:17 reddwarf chat[1583]: abort on (Login incorrect)

>Jan 14 21:41:17 reddwarf chat[1583]: send (ATZ^M)

>Jan 14 21:41:17 reddwarf chat[1583]: expect (OK)

Here it says it is waiting fo rthe modem to send OK
But nothing at all gets sent back-- chat reports on everything returned.
After 45 sec (the default timeout) chat gives up (that is the alarm)

>Jan 14 21:42:02 reddwarf chat[1583]: alarm

>Jan 14 21:42:02 reddwarf pppd[1581]: Connect script failed

chat sent an error message to pppd saying it had failed, pppd reports
that the "connect script" (which called chat) failed, as it did.

>Jan 14 21:42:02 reddwarf chat[1583]: Failed

The exit error from chat arrived at the syslog after that from pppd., so
it got reported second, but it was actually chat which failed first.

>Jan 14 21:42:04 reddwarf pppd[1581]: Exit.

>Jan 14 21:42:09 reddwarf kernel: PPP: ppp line discipline successfully
>unregistered

And here is report from the kernel getting rid of the ppp module, since
it is no longer needed.