I recently upgraded to RH5.0 from Debian1.2, keeping the same modem configuration, but with a newer version of mgetty. I can use minicom to dial out, but the modem will not answer. I have tried a variety of things to no avail. Here is the log (debug=9): ---- /var/log/log_mg.ttyS2 06/19 17:53:59 yS2 mgetty: experimental test release 1.1.9-Aug17 06/19 17:53:59 yS2 check for lockfiles 06/19 17:53:59 yS2 checklock: stat failed, no file 06/19 17:53:59 yS2 locking the line 06/19 17:53:59 yS2 makelock(ttyS2) called 06/19 17:53:59 yS2 do_makelock: lock='/var/lock/LCK..ttyS2' 06/19 17:53:59 yS2 lock made 06/19 17:54:00 yS2 tio_get_rs232_lines: status: RTS CTS DSR DTR RI 06/19 17:54:00 yS2 lowering DTR to reset Modem 06/19 17:54:00 yS2 tss: set speed to 38400 (017) 06/19 17:54:00 yS2 tio_set_flow_control( HARD ) 06/19 17:54:00 yS2 waiting for line to clear (VTIME), read: 06/19 17:54:01 yS2 send: \dATQ0V1H0[0d] 06/19 17:54:01 yS2 waiting for ``OK'' 06/19 17:54:01 yS2 got: [0d]ATQ0V1H0[0d] 06/19 17:54:20 yS2 CND: ATQ0V1H0 06/19 17:55:20 yS2 timeout in chat script, waiting for `OK' 06/19 17:55:20 yS2 init chat timed out, trying force-init-chat 06/19 17:55:20 yS2 send: \d[10][03]\d\d\d+++\d\d\d[0d]\dATQ0V1H0[0d] 06/19 17:55:24 yS2 waiting for ``OK'' 06/19 17:55:24 yS2 got: [0d][10][03]+++[0d] 06/19 17:55:40 yS2 CND: __+++ATQ0V1H0[0d] 06/19 17:55:40 yS2 CND: ATQ0V1H0 06/19 17:55:50 yS2 timeout in chat script, waiting for `OK' 06/19 17:55:50 yS2 init chat failed, exiting...: Interrupted system call 06/19 17:55:50 ##### failed in mg_init_data, dev=ttyS2, pid=1265 06/19 17:55:50 yS2 removing lock file this behavior is repeated ad infinitum. my inittab entry looks like this: s2:3:respawn:/sbin/mgetty /dev/ttyS2 I hope this is enough information - please let me know if more is needed. thanks, Graham Knopp -- PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES! http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject.
