Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!news.sprintlink.net!redstone.interpath.net!ddsw1!not-for-mail From: jal@MCS.COM (John A. LaCour III) Newsgroups: comp.os.386bsd.questions Subject: Re: Serial Strangeness under FreeBSD 1.1.5.1 Date: 19 Sep 1994 20:18:00 -0500 Organization: /usr/lib/news/organi[sz]ation Lines: 25 Message-ID: <35ld88$dr@Venus.mcs.com> References: <1994Sep19.225045.13922@ultb.isc.rit.edu> NNTP-Posting-Host: venus.mcs.com In article <1994Sep19.225045.13922@ultb.isc.rit.edu>, Ron Wilhelm <rew8422@ultb.rit.edu> wrote: >After several business trips, I am once again trying to get dialin working >under FreeBSD 1.1.5.1. It seems when I turn on ttyd1 in my /etc/ttys file, >my modem's receive and send data lights come on, and I am unable to use >cua01 to dial out-I get a device busy or something like that. If I turn off >the modem to reset it, I can use cua01, though the RD and SD light will come >back on. Make sure that your modem is configured to supress result codes and that local echo is turned off (ATE0Q1). Save these settings to the modems non-volatile RAM or set them with dip switches. What often happens is when the getty starts up, it will send a login: prompt out the port. The modem tries to interrupt that as a command and sends ERROR back or the modem simply echos the ''command'' back which confuses getty. The port and modem end up stuck in a loop talking to each other. Also, you want to make sure that the result codes are disabled so that when a caller connects, there isn't a CONNECT message sent back to login and confusing it. Hope that helps. John