From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 20 01:08:16 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D52516A4BF; Wed, 20 Aug 2003 01:08:16 -0700 (PDT) Received: from david.io.com (david.io.com [199.170.88.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A4F843FBD; Wed, 20 Aug 2003 01:08:15 -0700 (PDT) (envelope-from eighner@io.com) Received: from io.com (aus-as2-120.io.com [199.170.89.120]) by david.io.com (8.11.6/8.11.2) with SMTP id h7K93Yb19845; Wed, 20 Aug 2003 04:03:34 -0500 Date: Wed, 20 Aug 2003 03:06:12 -0500 (CDT) From: Lars Eighner To: Don Lewis In-Reply-To: <200308200457.h7K4vJM7032458@gw.catspoiler.org> Message-ID: <20030820030423.I937@pearl.io.com> References: <200308200457.h7K4vJM7032458@gw.catspoiler.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: hackers@freebsd.org Subject: Re: Modem won't connect at full speed X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Aug 2003 08:08:16 -0000 On Tue, 19 Aug 2003, Don Lewis wrote: > On 19 Aug, Lars Eighner wrote: > > On Tue, 19 Aug 2003, Don Lewis wrote: > > > >> On 19 Aug, Lars Eighner wrote: > >> > This has been answered by somebody on some forum, but I lost it. > > > >> If you manually dial using cu or tip, what connection speed does the > >> modem report? > > > > Oh geez, pull out the manual and spend all night trying to figure > > out how to config cu or tip, whatever they are! > > You should be able to do the same with minicom. While on-hook, just > do > > ATDT your_isps_phone_number > > >> > BAUD=9600 PARITY=N WORDLEN=8 > >> > DIAL=TONE ON HOOK CID=0 > > > >> It is somewhat worrysome that your modem is reporting 9600 BAUD in the > >> fixed DTE speed setting. I don't know about USR Internal modems, but at > >> least some implementations will pace the data flow rate to the reported > >> DTE speed to avoid overwhelming the host with quick bursts of > >> interrupts. This might be the reason for your slow connection speeds. I set the port setup in minicom to 57600, and got this on connect: atdt4857440 CONNECT 29333/ARQ/V90/LAPM/V42BIS and when I hung up the current settings looked like this: ati4 U.S. Robotics 56K Voice INT Settings... B0 E1 F1 L1 M0 Q0 V1 X4 Y0 BAUD=57600 PARITY=N WORDLEN=8 DIAL=TONE ON HOOK CID=0 &A3 &B1 &C1 &D2 &G0 &H1 &I0 &K1 &M4 &N0 &P0 &R2 &S0 &T5 &U0 &Y1 S00=000 S01=000 S02=043 S03=013 S04=010 S05=008 S06=002 S07=060 S08=002 S09=006 S10=014 S11=070 S12=050 S13=000 S15=000 S16=000 S18=000 S19=000 S21=010 S22=017 S23=019 S25=005 S27=000 S28=008 S29=020 S30=000 S31=128 S32=002 S33=000 S34=000 S35=000 S36=014 S38=000 S39=000 S40=001 S41=000 S42=000 LAST DIALED #: T4857440 OK changed to 115200 in mincom port setup and got: atdt4857440 CONNECT 34666/ARQ/V90/LAPM/V42BIS Please log in with your username and password, or log in as 'new' to open NO CARRIER With 230400, it didn't change: atdt4857440 CONNECT 34666/ARQ/V90/LAPM/V42BIS Forced &B=0 and got AT&B0 OK atdt4857440 CONNECT 36000/ARQ/V90/LAPM/V42BIS which I guess is some improvement, but doesn't account for the huge discrepancies in actual download times/rates I am getting. I saved to NVRAM and exited. I adjusted the connect speed in ppp.conf to 115200. I rebooted and when ppp came up, no joy. Ppp.log looked much the same, but it doesn't log the whole CONNECT line. I really think this is a software thing, since all went well when I had a linux partition and did ppp from linux. As I said, someone solved this for me before, but my records of it got lost in deleting the linux partion and moving freebsd and my data to the big disk. A frantic search of wetware dimly suggests that the previous solution involved adding a couple of lines to a file one of which included "nobsdcomp" but that file wasn't in /etc/ppp, but was someplace really weird - maybe something to do with kernel mod loading. That solution worked in 4.x-STABLE but I am now running 5.0-x RELEASE. -- Lars Eighner eighner@io.com -finger for geek code- http://www.io.com/~eighner/index.html 8800 N IH35 APT 1191 AUSTIN tx 78753-5266