Re: Sprint Novatel Ovation U720 USB phone very slow on Fedora

[Phil Meyer]

Arch Willingham wrote:
>  Would it be called something else? There is no /etc/wvdial.conf file
> on my system. Since I was firing it off with kpp, here is the config file (I'm making
> a huge guess here):
>
>  /mycomputer/.kde/share/config/kppprc
>
>  pppdArguments=
>
>  [Account0]
>  AccountingEnabled=0
>  AccountingFile=
>  Authentication=4
>  AutoDNS=1
>  AutoName=0
>  BeforeConnect=
>  BeforeDisconnect=
>  CallbackPhone=
>  CallbackType=0
>  Command=
>  DNS=
>  DefaultRoute=1
>  DisconnectCommand=
>  Domain=
>  ExDNSDisabled=0
>  Gateway=0.0.0.0
>  IPAddr=0.0.0.0
>  Name=Sprint
>  Password=vzw
>  Phonenumber=#777
>  ScriptArguments=
>  ScriptCommands=
>  StorePassword=1
>  SubnetMask=0.0.0.0
>  Username=auburn(a)tigers.COM
>  VolumeAccountingEnabled=0
>  pppdArguments=
>
>  [General]
>  DefaultAccount=Sprint
>  DefaultModem=Sprint
>  NumberOfAccounts=1
>  NumberOfModems=1
>  PPPDebug=0
>  ShowLogWindow=1
>
>  [Graph]
>  Background=255,255,255
>  Enabled=true
>  InBytes=0,0,255
>  OutBytes=255,0,0
>  Text=0,0,0
>
>  [Modem0]
>  BusyWait=0
>  Device=/dev/ttyUSB0
>  Enter=CR
>  FlowControl=Hardware [CRTSCTS]
>  Name=Sprint
>  Speed=230400
>  Timeout=60
>  UseLockFile=1
>  Volume=1
>  WaitForDialTone=1
>
>  [WindowPosition]
>  WindowPositionConWinX=351
>  WindowPositionConWinY=328
>  WindowPositionStatWinX=326
>  WindowPositionStatWinY=175
>
>  Arch
>
>  -----Original Message-----
>  From: fedora-list-bounces(a)redhat.com
>  [mailto:[e-mail]]On Behalf Of Phil Meyer
>  Sent: Thursday, May 24, 2007 4:43 PM
>  To: For users of Fedora
>  Subject: Re: Sprint Novatel Ovation U720 USB phone very slow on Fedora
>
>
>  Arch Willingham wrote:
>    
> > I am trying to install a Sprint Mobile Broadband USB Modem (Novatel Ovation U720)
> cellular USB phone on a Dell laptop running FC7 test4. I found a variety of instructions
> on getting it to work with FC6 and applied it to my install and it works..sort of.
> >
> > I have the laptop set to dual boot with XP. I first made sure it worked under XP. It
> does and it extremely fast. I then did the install on FC7. After issuing
> "/sbin/modprobe usbserial vendor=0×1410 product=0×2110". Once that was done, the
> modem appeared as /dev/ttyUSB0 and /dev/ttyUSB1 (someone said they think the latter is a
> management and diagnostic interface; the former is used for the PPP connection). I was
> then able to use KPPP to set up a dialer connection. I started the dialer and bam it
> connected. Once connected I see this:
> >
> > # ifconfig
> > lo        Link encap:Local Loopback  
> >           inet addr:127.0.0.1  Mask:255.0.0.0
> >           inet6 addr: ::1/128 Scope:Host
> >           UP LOOPBACK RUNNING  MTU:16436  Metric:1
> >           RX packets:3249 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:3249 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:0 
> >           RX bytes:13067764 (12.4 MiB)  TX bytes:13067764 (12.4 MiB)
> >
> > ppp0      Link encap:Point-to-Point Protocol  
> >           inet addr:xx.11.222.aa  P-t-P:yy.28.249.bb  Mask:255.255.255.255
> >           UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
> >           RX packets:3850 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:3463 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:3 
> >           RX bytes:3681723 (3.5 MiB)  TX bytes:532348 (519.8 KiB)
> >
> > The only problem is that it is slow as glue. When I click on a website, it takes 30
> to 90 seconds to respond. Once it actually starts pulling data, it seems a little quicker
> but then bogs down when trying to go to the next website. I manually changed the
> "serial" bit rate in the configuration files to the same way it was set in XP
> (230400 bps) but that did not help.
> >
> > In XP, the IP is set as follows:
> >
> > Connected to NDIS:
> > 	Intel(R) PRO/100 VE Network Connection - Packet Scheduler Miniport
> > 		GUID:	TRUCK4FC-E323-407D-B802-9D7F4412345
> > 		MAC Address:		00-14-3F-F5-1F-CB
> > 		Type:			Ethernet Adapter
> > 		IPAddresses:		0.0.0.0
> > 		Gateway Addresses:	
> > 		DHCP Enabled.
> > 			Lease Obtained Sun Aug 06 23:28:58 2006
> > 			Lease Expires Sun Aug 06 23:28:58 2006
> > 		DHCP Server Addresses:	192.168.1.1
> > 		WINS Disabled.
> >
> >
> > 	WAN (PPP/SLIP) Interface
> > 		GUID:	1234FAEE-F7D6-49F8-A71E-E9666BB54321
> > 		MAC Address:		00-53-45-00-00-00
> > 		Type:			PPP Adapter
> > 		IPAddresses:		YY.243.236.BB
> > 		Gateway Addresses:	YY.243.236.BB
> > 		DHCP Disabled.
> > 		WINS Disabled. 
> >
> > Does anyone have any ideas?
> >
> > Arch
> >
> >   
> >     
>
>  That is an IPV6 address.
>
>  Can we see your: /etc/wvdial.conf ?
>
>  It is usually a matter of the 'correct' initialize/dial strings.
>
>     
No K bashing intended here:

wvdial is a package and required for dial up networking done with 
system-config-network

However, none of that matters to the argument at hand, its just easier 
for me to explain how to watch things.

With syslog set to debug you should be able to see the entire handshake 
and any error messages or unexpected results.

We use both EVDO and GSM based cards on trucks. The computer on the 
trucks run FC6. :)

----X----
#!/bin/sh
# add debug to syslog
ed << _EOF /etc/syslog.conf
/local7/
a

# Debug
*.debug /var/log/debug
.
w
q
_EOF

touch /var/log/debug
chmod 644 /var/log/debug

service syslog restart
----X----

Now you can:
% tail -f /var/log/debug
and watch the entire conversation during a dial up.

What you are looking for are the strings that begin with sending the 
modem 'AT'.

At the least you should see 'ATZ' and or 'ATM0' or something like:
'ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0'

These are all sort of generic initialization strings.

Unfortunately for use we cannot see what Windows driver is sending to 
the modem, but it will contain something like these.

This forum expresses similar issues as you are having ...

http://www.evdoforums.com/thread3308.html

The speed issue is explained here:

http://samat.org/weblog/20070127-high-speed-cellular-wireless-modems-in-u...

"Switching from 1xRTT to EVDO is not automatic (though I believe EVDO to 
1xRTT is). On Windows, I believe this is done manually by the connection 
manager software…"

This means that a dial up initialization string (AT command) needs to be 
added, or that a command has to be sent on the command channel (ttyUSB1) 
to set the mode.

Using the above degug data you should see a response from Sprint as to 
which mode is established when connecting.

The PCMCIA versions of similar cards default to EVDO mode (thankfully), 
but this one may not.

Beyond this, its not clear to me yet how to change the mode.

Hope this helps a little.

Good Luck!