Modem won't connect at full speed
eighner at io.com
Wed Aug 20 01:08:16 PDT 2003
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
> 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
and when I hung up the current settings looked like this:
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
LAST DIALED #: T4857440
changed to 115200 in mincom port setup and got:
Please log in with your username and password, or log in as 'new' to open
With 230400, it didn't change:
Forced &B=0 and got
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.
eighner at io.com -finger for geek code-
8800 N IH35 APT 1191 AUSTIN tx 78753-5266
More information about the freebsd-hackers