From owner-freebsd-questions@FreeBSD.ORG Sun Jul 13 21:23:41 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 55A2037B401 for ; Sun, 13 Jul 2003 21:23:41 -0700 (PDT) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id B77C843F93 for ; Sun, 13 Jul 2003 21:23:40 -0700 (PDT) (envelope-from underway@comcast.net) Received: from localhost.localdomain (12-230-74-101.client.attbi.com[12.230.74.101](untrusted sender)) by attbi.com (rwcrmhc13) with ESMTP id <2003071404234001500i6ed0e>; Mon, 14 Jul 2003 04:23:40 +0000 Received: from localhost.localdomain (localhost [127.0.0.1]) by localhost.localdomain (8.12.9/8.12.9) with ESMTP id h6E4Q2H3002883 for ; Sun, 13 Jul 2003 21:26:02 -0700 (PDT) (envelope-from underway@comcast.net) Received: (from jojo@localhost) by localhost.localdomain (8.12.9/8.12.9/Submit) id h6E4Pt9F002882; Sun, 13 Jul 2003 21:25:55 -0700 (PDT) (envelope-from underway@comcast.net) To: freebsd-questions@freebsd.org From: underway@comcast.net (Gary W. Swearingen) Date: Sun, 13 Jul 2003 21:25:54 -0700 Message-ID: User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.1 (Cuyahoga Valley, berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Modem replies to commands mostly not seen. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2003 04:23:41 -0000 I hooked up an external 28.8 modem after continuity-cheking the cable but the lights didn't seem right, as I remember them. (I've not use my modem for several years.) Modem doesn't respond to terminal emulator commands and seems broken, so I throw in an internal (non-winmodem) Sportster (that I've just seen working OK under Linux). Boot message looks OK as it flashes by; it identifies the proper UART, IRQs, etc, (but not an ID string from the modem -- I don't know if that's expected or not). I hand-set the "COM #" and "IRQ" and made things match in /boot/device.hints. And it sort of works. I'm using "/dev/cuaa3". When I run a terminal emulator (tip, seyon, and minicom, so far), I get the same behavior: 1) Each character typed isn't seen until I type the next character. 2) Giving it the "AT" command (or most others), it never says "OK", but a few info commands, like "ATI6" will slowly spit out their reply (even ending with "OK") if I bang away on the keys, one or two characters per key. Looks like some kind of flow-control problem, but I've tried lots of fixes (using the terminal emulator's config controls) and always get the same behavior. I've even messed with some of the "stty" stuff, though I think that should be overruled by the terminal emulators (except maybe "tip", which I barely know). Any hints? Thanks.