problem with modems not answereing

Gert Doering (gert@greenie.muc.de)
Sun, 26 Jul 1998 03:28:30 +0200


Hi,

MACN Tech. Group wrote:
> we have a peoblem with some of the modems not answering. here is a snip
> from the log file.
> 
> -----cut-----
> 
> 07/25 10:57:21 yC0  mgetty: experimental test release 1.1.16-Jul05
> 07/25 10:57:21 yC0  check for lockfiles
> 07/25 10:57:21 yC0  locking the line
> 07/25 10:57:22 yC0  WARNING: DSR is off - modem turned off or bad cable?
> 07/25 10:57:22 yC0  lowering DTR to reset Modem
> 07/25 10:57:22 yC0  WARNING: obsolete setserial spd_hi/spd_vhi used, 38400
> is not real port speed

Don't do that...  (but that's not the cause of the problem).

> 07/25 10:57:22 yC0  send: AT&F&H1&R2&B1S0=0&K1&M4&S1S2=43[0d]
> 07/25 10:57:22 yC0  waiting for ``OK'' ** found **
> 07/25 10:57:23 yC0  waiting...
> 07/25 11:57:23 yC0  checking if modem is still alive
> 07/25 11:57:23 yC0  mdm_send: 'AT'
> 07/25 11:57:33 yC0  Warning: got alarm signal!
> 07/25 11:57:33 yC0  mdm_read_byte: read returned -1: Interrupted system
> call
> 07/25 11:57:33 yC0  mdm_get_line: cannot read byte, return: Interrupted
> system call -> ERROR
> 07/25 11:57:33 yC0  mdm_send: 'AT'
> 07/25 11:57:43 yC0  Warning: got alarm signal!

The modem stopped answering.  Either it died, or the serial port got
"in a bad state".

Make sure you use the *very latest* Cyclades drivers (there have been 
a number of bug fixes) and that you compile your system kernel with
the proper C compiler (gcc 2.7.2.3, do not use egcs or gcc 2.8!).

gert
-- 
Gert Doering
Mobile communications ... right now writing from *AWAY* :-)) 
... mobile phone: +49 177 2160221 ... or mail me:  gert@greenie.muc.de