From owner-freebsd-questions Thu Oct 26 10:50:07 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA15625 for questions-outgoing; Thu, 26 Oct 1995 10:50:07 -0700 Received: from rocky.sri.MT.net (sri.MT.net [204.94.231.129]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA15618 for ; Thu, 26 Oct 1995 10:50:01 -0700 Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id LAA01345; Thu, 26 Oct 1995 11:52:09 -0600 Date: Thu, 26 Oct 1995 11:52:09 -0600 From: Nate Williams Message-Id: <199510261752.LAA01345@rocky.sri.MT.net> To: User Shepner Cc: freebsd-questions@freebsd.org In-Reply-To: <199510261734.MAA12397@Eris.Manchester.EDU> References: <199510261734.MAA12397@Eris.Manchester.EDU> Sender: owner-questions@freebsd.org Precedence: bulk First of all, I had to go dig through my back email to find out what you are talking about. Using a subject line is a wonderful thing, and context is even better. > The suggestion of using tip to connect to the modem and then typing AT&Q > then AT&W didnt seem to help either. I tried this with both AT&B1 and AT&B2. How fast did you connect with tip? > >ttyd0 "/usr/libexec/getty std.19200" unknown on ttyd1 "/usr/libexec/getty std.19200" dialup on A shot in the dark is to try using the 'dialup' keyword. I suspect FreeBSD and the modem hardware are not agreeing on something. I had the exact same problems you had this morning when I moved a modem from a SUN over to the machine, and I needed to do the advice I gave you earlier. However, since I setup the modem on the SUN I know all of the hardware settings of the modem. The modem must be setup to: 1) Use Hardware flow control 2) Lock the Computer-Modem speed to the speed of the getty 3) Do NOT ignore DTR 4) Use proper cabling to allow all of the above. Nate