From owner-freebsd-questions Wed Jun 9 14:49:42 1999 Delivered-To: freebsd-questions@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id BDDE614D4C for ; Wed, 9 Jun 1999 14:49:40 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id OAA27753; Wed, 9 Jun 1999 14:48:23 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Wed, 9 Jun 1999 14:48:22 -0700 (PDT) From: Doug White To: John Reynolds~ Cc: freebsd-questions@FreeBSD.ORG Subject: Re: sio code--how much changed from 2.2.x -> 3.x? In-Reply-To: <14172.12574.525740.416458@hip186.ch.intel.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 7 Jun 1999, John Reynolds~ wrote: > I have recently configured a new box with 3.1-RELEASE and am having a terrible > time getting any sort of comm program running with the modem that I > purchased. The modem is an ActionTec DeskLink Master (ISA) V.90. > > I have the modem in on COM2 and can call into my ISP under Windows '98 just > fine (except I can't connect to their V.90 lines--the modem has never > auto-negotiated back down to a proper speed, I must call their V.34 lines). > However, under FreeBSD, when I load up minicom (1.82 I think--whatever version > came with 3.1-RELEASE in the ports tree) I cannot connect to even the > V.34 lines at my ISP. I can hear the modem call out, then the negotiate > 'screech' then I get "NO CARRIER". The modem just hangs up as soon as it's > about to make a good connection (or so it seems--I don't know if it's the > ISP hanging up, suffice to say I can use this same modem under Win98 and > a different computer with different modem to the same ISP very reliably). This is irrespective of the operating system in use. Most likey, Windows is sending an init string to the modem that configures some extra options. You should go into the Modem control panel and find out what string(s) it's sending to initialize the modem. You may want to issue the 'factory reset' command -- usually AT&F -- then dial and see if this remedies things. If so, write the status back to NVRAM with AT&W and init the modem with AT&F before dialing. Please consult your modem's manual for further commands. The OS serial-line drivers *CANNOT* and *DO NOT* impact the modem's handshake phase. Unless this is a WinModem, which it is not since you can use it under FreeBSD. :) Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message