From owner-freebsd-hackers Sun Jul 23 10:41:45 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id KAA08245 for hackers-outgoing; Sun, 23 Jul 1995 10:41:45 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id KAA08235 for ; Sun, 23 Jul 1995 10:41:37 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id DAA18866; Mon, 24 Jul 1995 03:38:28 +1000 Date: Mon, 24 Jul 1995 03:38:28 +1000 From: Bruce Evans Message-Id: <199507231738.DAA18866@godzilla.zeta.org.au> To: ache@astral.msk.su, terry@cs.weber.edu Subject: Re: dial up at > 9600 baud Cc: bde@zeta.org.au, hackers@freebsd.org, harry@hgac.com, jkh@violet.berkeley.edu Sender: hackers-owner@freebsd.org Precedence: bulk >> The problem: initial port speed 9600, getty speed 38400 f.e., >> port opened on carrier at 9600, modem detects it and set >> connection to 9600 too, _then_ getty change port speed to 38400 >> confusing modem completely. >> >> I understand that problem solves by locking port on 38400 >> initially, but it isn't nice solution, getty must able >> to open port at correct speed setted in its flags. There's nothing really wrong with setting the initial speed to 38400 (except 38400 is too slow - why not 115200? :-). Use `stty 115200 I guess I still don't understand how the modem magically detects >the port speed when the port sets the baud before it says anything >(like "login: "). Perhaps getty sometimes writes something before setting the speed. It does quite a let between the open and setting the speed. Bruce