From owner-freebsd-questions Wed Dec 21 12:53:29 1994 Return-Path: questions-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id MAA16513 for questions-outgoing; Wed, 21 Dec 1994 12:53:29 -0800 Received: from late5.e-technik.uni-erlangen.de (late5.e-technik.uni-erlangen.de [131.188.254.132]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id UAA16498 for ; Wed, 21 Dec 1994 20:53:24 GMT Received: (from tuucp@localhost) by late5.e-technik.uni-erlangen.de (8.6.8.1/8.6.6) id PAA26163 for questions@freebsd.org; Wed, 21 Dec 1994 15:53:16 -0500 Received: from odin (iwte01-2.dialin.rrze.uni-erlangen.de [192.44.83.18]) by iwte01.dialin.rrze.uni-erlangen.de (8.6.9/8.6.6) with ESMTP id TAA09882; Tue, 20 Dec 1994 19:15:27 +0100 Received: (from eilts@localhost) by odin (8.6.8/8.6.6) id TAA00274; Tue, 20 Dec 1994 19:14:31 +0100 Date: Tue, 20 Dec 1994 19:14:31 +0100 From: Hinrich Eilts Message-Id: <199412201814.TAA00274@odin> Received: by NeXT.Mailer (1.100) Received: by NeXT Mailer (1.100) To: starkhome!gene@sbstark.cs.sunysb.edu (Gene Stark) Subject: Re: Bug in serial-line communication Cc: questions@freebsd.org Sender: questions-owner@freebsd.org Precedence: bulk >>System is FreeBSD-2.0R (486/16MB): >> >>A UUCP-connection started by "uucico -r1 -x chat -slate" >>has a chat >>chat "" atz\r\d\c OK atm1 OK atdt\D name: ... >>and results in a chat-timeout with following text in Debug: >>uucico late - (1994-12-04 16:28:18.49 234) Calling system late (port cua02) >>uucico late - (1994-12-04 16:28:18.49 234) DEBUG: fcsend: Writing "atz\r" sleep >>uucico late - (1994-12-04 16:28:19.50 234) DEBUG: icexpect: Looking for 2 "OK" >>uucico late - (1994-12-04 16:28:19.50 234) DEBUG: icexpect: Got "atz\r\r\nOK" (found it) >>uucico late - (1994-12-04 16:28:19.66 234) DEBUG: fcsend: Writing "atm1" >>uucico late - (1994-12-04 16:28:19.66 234) DEBUG: icexpect: Looking for 2 "OK" >>uucico late - (1994-12-04 16:28:19.66 234) DEBUG: icexpect: Got "\r\n" (timed out) >>uucico late - (1994-12-04 16:29:19.66 234) ERROR: Timed out in chat script > >Check your modem cable and/or RTS/CTS and DTR settings. I suspect that >your modem cable is not properly passing DTR to the modem, so that your >modem is hanging waiting for DTR to be asserted before producing the "OK". Thanks for your reply. Hardware and modem-configuration is unchanged to 1.1, on which all worked. I checked DTR, it's asserted all the time. I suspect a timing problem in sio which occurs on my hardware, but the new sio (1.1.5) is quite different to the old. Hinrich