Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!haven.umd.edu!darwin.sura.net!udel!sbcs.sunysb.edu!stark.UUCP!gene From: gene@cs.sunysb.edu!stark (Gene Stark) Newsgroups: comp.os.386bsd.questions Subject: Re: Anyone with problems with dial in/out? Date: 11 May 93 08:33:59 Organization: Gene Stark's home system Lines: 27 Message-ID: <GENE.93May11083359@stark.uucp> References: <C6u36D.1155@austin.ibm.com> NNTP-Posting-Host: stark.uucp In-reply-to: fredriks@austin.ibm.com's message of Mon, 10 May 1993 23:13:25 GMT In article <C6u36D.1155@austin.ibm.com> fredriks@austin.ibm.com (Lars Fredriksen) writes: > I have Chris' bidirectional com driver, and have noticed problems > when I have getty enabled on /dev/tty01. When you try to run tip or uucp > to dial out, you are lucky if you can connect to the modem 1 out of 5 tries. > In between I get all kinds of garbage that seems to come back from the modem, > but I suspect getty or the tty driver. Besides the echo problem, one stupid thing that puzzled me for some time was the proper tty speed setting for getty. I have a modem that automatically configures to the speed it sees from the DTE that it is connected to. On dialout I use it at 19200, but the actual modem rate is 2400 or 9600. Somehow I got the idea that if I were dialing in from a remote 2400B modem, then I should put something like "std.2400" or one of the cycling dialin entries in the /etc/ttys. *WRONG* I was confused for some time about why I couldn't seem to lock in the speed on dialing in. Finally it dawned on me that the proper thing was to put the fixed-speed "std.19200" in the /etc/ttys entry. Gene Stark -- stark@cs.sunysb.edu