# Mostly OT from HPC: Wireless air cards

I just picked up a Verizon Wireless PCMCIA air card to go with the new Dell laptop. The HPC connection comes from this being the unit I take with me on-site. The wireless card is a PCMCIA unit, the PC5750. It is basically a PCMCIA -> USB bridge for a modem. I installed the Verizon software in the windows XP portion (didn’t check to see if it works in XP x64, which I had been still considering reloading that portion with). Did the usual dance for “autodetection”. Install the software, configure it, wait till it tells me to insert for “autodetection” and off it went. Took me a bit to get it connected, the speed was quite slow, but it was far better than nothing. It worked though, so that is important.

Ok, now under Linux. Followed the directions here. They seemed to work (kind of sort of). Except the modem was erroring out. No problem, I got minicom up, and tried it by hand.
Sure enough, the modem was having trouble with the semicolons in the chat script. So I edited the chat script to look like this:
 # AT\$QCMIPGETP "login" name used for MobileIP, which usually matches your MIN. # AT+GSN ESN in hex # AT+GMR firmware revision and build date. # AT+CSQ first number indicates the signal strength above -109 dBm (in # 2 dBm increments). A value of 7 or higher (-95 dBm) can be # considered adequate. 31 is the max. (Possible values in # Audiovox PC5740 are 0, 7, 15, 23, 31.) # AT+CDV=*22899 Update PRL. at+cdv=*22899 | OK | Lost carrier. ABORT 'NO CARRIER' ABORT ERROR ABORT 'NO DIALTONE' ABORT BUSY ABORT 'NO ANSWER' '' 'ATTEV1&F&D2&C1&C2S0=0S7=60' 'OK-ATTEV1&F&D2&C1&C2S0=0S7=60-OK-ATTEV1&F&D2&C1&C2S0=0S7=60-OK' 'AT+CSQ;D#777' TIMEOUT 70 'CONNECT-AT+CSQ;D#777-CONNECT'
with the /etc/ppp/peers/1xevdo looking like this
 ttyACM0 115200 debug noauth defaultroute usepeerdns connect-delay 30000 user INSERT_YOUR_NUMBER_HERE@vzw3g.com show-password crtscts lock lcp-echo-failure 4 lcp-echo-interval 65535 connect '/usr/sbin/chat -v -t3 -f /etc/ppp/peers/1xevdo_chat'
And then I did a
sudo pppd dial 1xevdo
It worked. All connected.
Better than that, it was fast. Quite a bit faster than windows. Not sure why (same hardware in both cases, different OSes). Best guess without looking into the details is the modem setup.
Really, it isn’t that hard. Setup time was a little longer in windows than in Linux, as it had to do the initialization. That said, it works, pretty well. I set up 2 buttons on the linux desktop to start and stop the connection. They work great as well.
I like it when stuff just works. Its nice that it just works under windows and linux. Interoperability is very important to me, to our customers.