Linux HowTo

Qualcom GOBI 2000 UMTS/GPS 3G modem with Gentoo (ThinkPad W510)

Details

Created on Wednesday, 27 April 2011 19:52

Last Updated on Thursday, 24 May 2012 14:55

I'll just shortly summarize my steps (15 overall) to get the Qualcom GOBI 2000 UMTS/3G/GPS modem in my Lenovo Thinkpad W510 up and running.

1. Stock 2.6.38.4 Kernel with CONFIG_USB_SERIAL_WWAN=m, CONFIG_USB_SERIAL_QCAUX=m, CONFIG_USB_SERIAL_QUALCOMM=m, CONFIG_PPP=y, CONFIG_PPP_MULTILINK=y, CONFIG_PPP_FILTER=y, CONFIG_PPP_ASYNC=y, CONFIG_PPP_SYNC_TTY=y, CONFIG_PPP_DEFLATE=y, CONFIG_PPP_BSDCOMP=y, CONFIG_PPP_MPPE=y, CONFIG_PPPOE=y
   (modules will be called usb_wwan, qcaux, qcserial)
2. Add "usb_wwan" to /etc/conf.d/modules
3. # modprobe qcserial
   (or reboot)
4. USE-flags for net-dialup/ppp: activefilter, dhcp, eap-tls,gtk, pam, -atm, -ipv6, -mppe-mppc, -radius
5. # emerge -av net-wireless/gobi_loader net-dialup/ppp
6. Snag the firmware files from a windows installation (/mnt/win/Program\ Files\ \(x86\)/QUALCOMM/Images/Lenovo/) and copy them to "/lib/firmware/gobi/"
   (I just copied all files and indicated the origin in the file name with the originating Dir a MD5SUM and the provider they are intended for. See list below - klick "Read more...")
7. Link the desired firmware files to UQCN.mbn, amss.mbn and apps.mbn (gobi_loader will only load exactly these file names)
8. # /lib64/udev/gobi_loader -2000 /dev/ttyUSB0 /lib/firmware/gobi
   (on boot a UDEV rule will do this for you) and check "dmsg". You should fond something like
   

   qcserial 2-1.4:1.1: Qualcomm USB modem converter detected
   usb 2-1.4: Qualcomm USB modem converter now attached to ttyUSB0
   qcserial 2-1.4:1.2: Qualcomm USB modem converter detected
   usb 2-1.4: Qualcomm USB modem converter now attached to ttyUSB1
   qcserial 2-1.4:1.3: Qualcomm USB modem converter detected
   usb 2-1.4: Qualcomm USB modem converter now attached to ttyUSB2
   

9. # emerge -av wvdial
10. Past the following into /etc/wvdial.conf (PASSWORD and USERNAME are arbitrary), but don't forget to set YOUR_PIN
    

    [Dialer Defaults]
    Modem = /dev/ttyUSB1
     
    [Dialer o2]
    Modem = /dev/ttyUSB1
    Phone = *99***1#
    Username = YOUR_USERNAME
    Password = YOUR_PASSWORD
    Init2 = ATZ
    Init3 = AT+CGDCONT=1,"IP","internet"
    Ask Password = 0
    Dial Command = ATDT
    Auto DNS = 1
    Check Def Route = 1
    Baud = 230400
    Stupid Mode = 1
    New PPPD = yes 
    Carrier check = no
     
    [Dialer pin]
    Modem = /dev/ttyUSB1
    Init1 = AT+CPIN=YOUR_PIN
    

11. # wvdial pin
12. # wvdial o2
    You should see something like
    

    root@larry $ wvdial o2
    --> WvDial: Internet dialer version 1.61
    --> Cannot get information for serial port.
    --> Initializing modem.
    --> Sending: ATZ
    ATZ
    OK
    --> Sending: ATZ
    ATZ
    OK
    --> Sending: AT+CGDCONT=1,"IP","internet"
    AT+CGDCONT=1,"IP","internet"
    OK
    --> Modem initialized.
    --> Sending: ATDT*99***1#
    --> Waiting for carrier.
    ATDT*99***1#
    CONNECT 7200000
    --> Carrier detected. Starting PPP immediately.
    --> Starting pppd at Wed Apr 27 20:34:57 2011
    --> Pid of pppd: 13687
    --> Using interface ppp0
    --> local IP address 10.54.182.34
    --> remote IP address 10.64.64.64
    --> primary DNS address 193.189.244.225
    --> secondary DNS address 193.189.244.206
    

13. If you can't connect a second time, just reload the firmware, this will reset the device.
14. NetworkManager Plasmoid in KDE4 works flawless and configuration is straight forward, but if you reload the firmware, the NetworkManager Plasmoid will loos track of the modem.
15. GPS is on /dev/ttyUSB2 and you have to run "echo "\$GPS_START" > /dev/ttyUSB2" to get it running (maybe you have to start it once under Windows).
    To stop the device run "echo "\$GPS_STOP" > /dev/ttyUSB2". The device uses the NMEA protocol.

Here's the list of the firmware files. All files follow this naming pattern:
{original name}-{Folder}-{MD5SUM}-{Provider}.mbn

UQCN-0-25ebf8314ed23394d23fb30ec4d73bf8-Vodafone.mbn
UQCN-1-2dccbd125ddd2cb327309ba75c6054d2-Verizon.mbn
UQCN-2-19eaec6cea1dc9b702b429dcb6032aa4-ATandT.mbn
UQCN-3-0ac877ed109f3c28d844b08f55c56185-Sprint.mbn
UQCN-4-b186fe81731e17e59ca16b92cb2069b6-TMobile.mbn
UQCN-6-bdf27325ebb63251c1310cd3a8f7bab6-Generic.mbn
UQCN-7-0e38dc59f7b3891b3605d9120a0ab149-Telefonica_O2.mbn
UQCN-8-0300af5e51c387d64c48db71169b5b23-Telecom_Italia.mbn
UQCN-9-735db64a57802e252ca4ff05d06b2f10-Orange.mbn
UQCN-12-e868df00bfa88596d588a52f872ff703-Unknown.mbn
amss-1-06f76ed398458dad7b91c2d99a85a0a7-Verizon.mbn
amss-3-d25f247cbe0fa481378d9f92c65c3e5e-Sprint.mbn
amss-12-4d6203bf9fe8ae1af439d4d163e91596-Unknown.mbn
amss-UMTS-80fcfbb41a7d4331d4b7145972f5f3c4-Generic.mbn
apps-1-88a60ed745d75fb1b92c539574ecc972-Verizon.mbn
apps-3-46fcb2423c31fd96e4645a90956264d2-Sprint.mbn
apps-12-385a22740f80c0d00f8acdd9ad637032-Unknown.mbn
apps-UMTS-00cbd411048cdadc3e4caf0d89d14fca-Generic.mbn

References: 1, 2, 3