Re: Trying to get GOBI modem [back] to working

[Dan Williams <dcbw redhat com>]

On Thu, 2012-11-29 at 14:12 -0500, Adam Tauno Williams wrote:
> On Thu, 2012-11-29 at 13:12 -0500, Adam Tauno Williams wrote:
> > openSUSE 12.2 i686
> > NetworkManager-0.9.4.0-5.13.1.i586
> > ModemManager-0.5.2.0-2.4.1.i586
> > 3.4.11-2.16-desktop #1 SMP PREEMPT
> > I have an HP Netbook Pavilion dm1.
> > Device is 03f0:241d Hewlett-Packard Gobi 2000 Wireless
> > It worked on a previous install, at least at some point.  Now the device
> > does not appear to be available [we appear to have at least the same
> > version of ModemManager - I do have
> > a /usr/lib/ModemManager/libmm-plugin-gobi.so].
> > Does NetworkManager / ModemManager initialize this device or does that
> > still fall to the gobi_loader?
> > Previously in /var/log/message we'd see -
> > Sep 27 18:32:14 linux kernel: [    3.303672] USB Serial support
> > registered for Qualcomm USB modem
> > Sep 27 18:32:14 linux kernel: [    3.305245] qcserial 1-5:1.1: Qualcomm
> > USB modem converter detected
> > Sep 27 18:32:14 linux kernel: [    3.305360] usb 1-5: Qualcomm USB modem
> > converter now attached to ttyUSB0
> > Sep 27 18:32:14 linux kernel: [    3.307537] qcserial 1-5:1.2: Qualcomm
> > USB modem converter detected
> > Sep 27 18:32:14 linux kernel: [    3.307810] usb 1-5: Qualcomm USB modem
> > converter now attached to ttyUSB1
> > Sep 27 18:32:14 linux kernel: [    3.309392] qcserial 1-5:1.3: Qualcomm
> > USB modem converter detected
> > Sep 27 18:32:14 linux kernel: [    3.309549] usb 1-5: Qualcomm USB modem
> > converter now attached to ttyUSB2
> > The device configured as wwan0 "HP un2420 Mobile Broadband Module".
> > Now these additional devices do not appear [assuming the firmware is not
> > initialized].
> 
> Nevermind, I now have NetworkManager recognizing the device [at least].
> 
> <http://lists.opensuse.org/opensuse/2012-11/msg00789.html>
> 
> It was a firmware issue.
> 
> Product: HP un2420 Mobile Broadband Module
> /lib/firmware/gobi # ls -l
> total 14236
> -rw-r--r-- 1 root root 11333684 Nov 29 13:40 amss.mbn
> -rw-r--r-- 1 root root  3223596 Nov 29 13:40 apps.mbn
> -rw-r--r-- 1 root root    10748 Nov 29 13:40 UQCN.mbn
> pc02813:/lib/firmware/gobi # md5sum *
> 80fcfbb41a7d4331d4b7145972f5f3c4  amss.mbn
> 00cbd411048cdadc3e4caf0d89d14fca  apps.mbn
> bdf27325ebb63251c1310cd3a8f7bab6  UQCN.mbn

If it's Verizon, you need to load CDMA/EVDO firmware, not UMTS firmware.
Which is why you get the wrong configuration in the dialog that asks for
a "Plan Name".  Try directory '1' perhaps; I have these MD5 sums:

06f76ed398458dad7b91c2d99a85a0a7  1/amss.mbn
88a60ed745d75fb1b92c539574ecc972  1/apps.mbn
e4d8d4dbd0a10d17f01f7f3bbd2ea734  1/UQCN.mbn

One way to check is to do something like:

cd /where/your/firmware/is
strings 0/* | grep -i vzw
strings 1/* | grep -i vzw
strings 2/* | grep -i vzw
strings 3/* | grep -i vzw
(etc)

until you get a hit for something, like @vzw3g.com.

Dan