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:
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: www.nulldevice. de/2010/ 06/wwan- lenovo- thinkpad- x100e-ubuntu- 10-04/
http://
I updated to the 2.6.35rc1 kernel, and built gobi_loader. The Dell device is in qcserial based on extrapolation from: cateee. net/lkddb/ web-lkddb/ USB_SERIAL_ QUALCOMM. html
http://
(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 3e1a0e8c6145c9d 12 ./0/UQCN.mbn e9c2103db63536e 4b ./15/amss.mbn 472f6cfb7c04806 cb ./15/apps.mbn 957d15a8b23fed3 be ./15/UQCN.mbn 31e6da1a422e37f f3 ./1/amss.mbn 7943d0cf3257c36 21 ./1/apps.mbn 85e0edab431a481 4c ./1/UQCN.mbn 50b9769e9ca7635 ea ./2/UQCN.mbn 0f1dae329c36be3 c5 ./3/amss.mbn 650b1efbbee64ee 31 ./3/apps.mbn cd17671fafb1ac3 5c ./3/UQCN.mbn 6df8d3ebc8efe81 d7 ./6/UQCN.mbn 6b436461203b38c 97 ./UMTS/amss.mbn bfdf0fa60c32227 66 ./UMTS/apps.mbn
1aa40f2f7e79024
9b0526b4f1cd016
c28c5f749e5481b
68d2f4f631d2c72
51aa00c43b7eab3
4f46a856fcceb19
6e05582f7997f93
820e2ad056bce04
86d9d0287b5fd8c
d9ff7b27c491332
d3a317a0eb91b19
9a85dfae619ef5e
920000c8fd17095
d7496085f1af3d1
The directory structure seems to be the same--Verizon firmware is in the ./1/ directory. Although the firmware that is available is different.