From owner-freebsd-questions@FreeBSD.ORG Mon Jul 14 10:03:16 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 B890737B437 for ; Mon, 14 Jul 2003 10:03:16 -0700 (PDT) Received: from mta4.adelphia.net (mta4.adelphia.net [64.8.50.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id E5C5043F75 for ; Mon, 14 Jul 2003 10:03:15 -0700 (PDT) (envelope-from fbsd_user@a1poweruser.com) Received: from barbish ([68.169.105.49]) by mta4.adelphia.net (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with SMTP id <20030714170315.WXUV1347.mta4.adelphia.net@barbish>; Mon, 14 Jul 2003 13:03:15 -0400 From: "fbsd_user" To: "Gary W. Swearingen" , Date: Mon, 14 Jul 2003 13:03:14 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-Reply-To: Subject: RE: Modem replies to commands mostly not seen. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: fbsd_user@a1poweruser.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2003 17:03:17 -0000 Sounds like you have echo turned off in the modems internal prom setting. Use Hayes AT command to turn on echo function of modem hardware. Did these modems you tested work ok in FBSD 4.8? -----Original Message----- From: owner-freebsd-questions@freebsd.org [mailto:owner-freebsd-questions@freebsd.org]On Behalf Of Gary W. Swearingen Sent: Monday, July 14, 2003 12:26 AM To: freebsd-questions@freebsd.org Subject: Modem replies to commands mostly not seen. 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. _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"