Date: Sat, 24 Aug 1996 20:04:09 -0700 (PDT) From: Doug White <dwhite@gdi.uoregon.edu> To: "Francis Percival C. Favoreal" <june@adn.edu.ph> Cc: freebsd-questions <questions@freebsd.ORG> Subject: Re: modem won't respond Message-ID: <Pine.BSI.3.94.960824200257.218P-100000@gdi.uoregon.edu> In-Reply-To: <Pine.LNX.3.91.960825015716.30944B-100000@sili.adn.edu.ph>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 25 Aug 1996, Francis Percival C. Favoreal wrote: > > > (Please reply directly to this address. I am not in the freebsd-question > mailing list) > > I have two modems connected to my freebsd box. Modem connected to COM1 > works just fine. However, I cannot talk with the modem connected in COM2. > > I was trying to configure the modem connected to COM2. I usually type, > > # tip cuaa1 > > and get > > # tip cuaa1 > connected Wow, that doesn't work here: gdi,ttyp1,/usr/local/etc,33>tip cuaa0 tip: unknown host cuaa0 Have you hacked /etc/remote? > Problem is, when I tried to type AT commands, I don't see it being > displayed on the console. The modem seems not responding. I'd check /etc/remote and other tip config files to make sure you know where cuaa1 is pointing to. Also check the settings on /dev/cuala1 and /dev/cuaa1 using stty. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.3.94.960824200257.218P-100000>