failed in mg_init_data, dev=ttyC3 (Help! please)
Gert Doering (gert@greenie.muc.de)
Wed, 8 Jul 1998 23:12:07 +0200
Hi,
Avery wrote:
> The last items in every log entry is:
>
> 07/07 09:52:22 yC3 send: \dATQOVlHO[Odl
> 07/07 09:52:23 yC3 waiting for "OK"
> 07/07 09:52:23 yC3 got: ATQOVlHO[Od]
> 07/07 09:52:23 yC3 CND: ATQOVlHO[Od][Oa]OK ** found
> 07/07 09:52:23 yC3 send: ATSO=OQO&D3&Cl[Od]
> 07/07 09:52:23 yC3 waiting for "OK"
> 07/07 09:52:23 yC3 got: [0d]
> 07107 09:52:23 yC3 CND: OK[Oa]ATSO=OQO&D3&Cl[Odl
> 07/07 09:52:23 yC3 CND: ATSO=OQO&D3&Cl[OdIEOaIERROR
> 07/07 09:52:23 yC3 found action string: "ERROR"
> 07/07 09:52:23 yC3 init chat failed, exiting ... : Invalid argument
> 07/07 09:52:23 ##### failed in mg_init_data, dev=ttyC3, pid=31373
Have you typed this from memory? All the "zeroes" in your example above
are actually "capital-o"'s, and as such, will definitely cause errors.
Also, there is an AT&Cl in there ("cee ell"), which should be &C1 ("cee
one").
> Then it starts the initalization process over, and so on and so on...
Sure.
> This would seem to me that the modem is returning an error, right? What
> I don't understand is that sometimes it works, and sometimes it does
> not. Sometimes cycling the power on the modem will correct the
> situating, sometimes not.
Hmmm, from your log file, you're sending garbage to the modem, and the
modem returns garbage. Now I don't know whether the log is accurate...
> The modems are USR Sportster 28.8's.
Crapmodems...
> Any Ideas of what the problem may be?
Hard to say. The log file is very strange. But besides this, it could be
a bad serial port, broken modem, bad cable, bad wheather, who knows.
Try whether the initialization works fine from a terminal program then,
and if not, change modem, ports, cables, wheather, until the problem goes
away.
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