[Bug 554099] Re: qualcomm gobi (2000) mobile broadband module not working after upgrade to lucid

Brian launchpad at peyser.net
Wed Jun 30 00:00:15 UTC 2010


I got this to work on my Dell E6410 with the "Dell Wireless 5620" Gobi
2000 over Verizon Wireless.

I found a pretty good walk-through I could adapt to Dell/Verizon at:
http://www.nulldevice.de/2010/06/wwan-lenovo-thinkpad-x100e-ubuntu-10-04/

I updated to the 2.6.35rc1 kernel, and built gobi_loader. The Dell device is in qcserial based on extrapolation from:
http://cateee.net/lkddb/web-lkddb/USB_SERIAL_QUALCOMM.html
(Dell device is: ID 413c:8186, or 413c:8185 before firmware is loaded.)

I got gobi_loader working with what I thought were the Verizon firmware
files, but after the card was activated with Verizon it still would not
connect.

Finally I imaged my primary partition to my /home partition and wiped
it, installed Windows 7 64b and the Dell drivers, then "activated" the
card. It then connected in Windows fine. (I think the process of
"activating" the card in Windows is just choosing the correct firmware
to load.) From my Windows 7 install, I copied the firmware files to a
USB stick and restored my Ubuntu installation. A warm reboot resulted in
the card working from Ubuntu. However, a cold reboot and the card
stopped working, and the Gobi 2000 acted like it did before running
Windows. I pulled the firmware files off of the memory stick and looked
at the md5sum values for the files. The firmware I got from the Dell
install was different from the Lenovo firmware. So I copied the Dell
firmware for Verizon (from the 1/ directory) to /lib/firmware/gobi/ and
did a cold reboot. Now the Gobi 2000 is working!

Here are the md5sum values for the "Dell Wireless 5620" firmware:

$ find -name "*.mbn" -exec md5sum {} \; | sort -k 2
1aa40f2f7e790243e1a0e8c6145c9d12  ./0/UQCN.mbn
9b0526b4f1cd016e9c2103db63536e4b  ./15/amss.mbn
c28c5f749e5481b472f6cfb7c04806cb  ./15/apps.mbn
68d2f4f631d2c72957d15a8b23fed3be  ./15/UQCN.mbn
51aa00c43b7eab331e6da1a422e37ff3  ./1/amss.mbn
4f46a856fcceb197943d0cf3257c3621  ./1/apps.mbn
6e05582f7997f9385e0edab431a4814c  ./1/UQCN.mbn
820e2ad056bce0450b9769e9ca7635ea  ./2/UQCN.mbn
86d9d0287b5fd8c0f1dae329c36be3c5  ./3/amss.mbn
d9ff7b27c491332650b1efbbee64ee31  ./3/apps.mbn
d3a317a0eb91b19cd17671fafb1ac35c  ./3/UQCN.mbn
9a85dfae619ef5e6df8d3ebc8efe81d7  ./6/UQCN.mbn
920000c8fd170956b436461203b38c97  ./UMTS/amss.mbn
d7496085f1af3d1bfdf0fa60c3222766  ./UMTS/apps.mbn

The directory structure seems to be the same--Verizon firmware is in the
./1/ directory. Although the firmware that is available is different.

-- 
qualcomm gobi (2000) mobile broadband module not working after upgrade to lucid
https://bugs.launchpad.net/bugs/554099
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux in ubuntu.




More information about the kernel-bugs mailing list