ThinkWiki - User contributions [en]

Qualcomm Gobi 2000

2011-05-22T07:27:50Z

Invented: /* GPS */

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== Qualcomm Gobi 2000 ===
This is a Qualcomm WWAN Adapter that is installed in a Mini-PCI Express slot

{{NOTE|Specific versions of this card may come pre-configured for a certain carrier (AT&T, Verizon, Vodafone UK)}}

=== Features ===
* Chipset: Qualcomm Gobi 2000
* USB ID: 05c6:9204 (loader)
* USB ID: 05c6:9205 (modem)
* EV-DO/CDMA (800 & 1900Mhz)
* GSM/GPRS/EDGE (850, 900, 1800 & 1900MHz)
* HSPA/UMTS (800, 850, 900, 1900 & 2100MHz)
* GPS, AGPS
* Up to 7.2Mbps download, 5.76Mbps upload (HSPA/UMTS)
* Up to 3.1Mbps download, 1.8Mbps upload (EV-DO)
</div>
|style="vertical-align:top" |
[[image:Qualcomm_gobi_2000.jpg|thumb|Qualcomm Gobi 2000 WWAN Adapter]]
|}

== Lenovo Partnumbers ==
*ThinkPad AT&T® Gobi 2000 Broadband Option 78Y1398
*ThinkPad Gobi 2000 Broadband Option 78Y1399

== Firmware ==
The firmware for this device is not publicly downloadable. It consists of 3 files:
* amss.mbn (firmware stage 1)
* apps.mbn (firmware stage 2)
* UQCN.mbn (firmware stage 3 - includes configuration and carrier specific settings)

=== Obtaining the Firmware ===
There are two ways of obtaining the firmware files:
# From the pre-installed Lenovo Windows installation. Or from a clean Windows installation in a virtualizer that supports USB after installing the Qualcomm Gobi 2000 Wireless WAN Driver[http://www-307.ibm.com/pc/support/site.wss/MIGR-72938.html]. The default location for the firmware files is {{path|C:\Program Files (x86)\QUALCOMM\Images\Lenovo\}}
# Using Wine to execute the Qualcomm Gobi 2000 Wireless WAN Driver installer[http://www-307.ibm.com/pc/support/site.wss/MIGR-72938.html] that simply unpacks the real installer named GobiInstaller.msi. Then just extract[http://sysblogd.wordpress.com/2008/05/10/howto-extract-all-files-from-microsoft-installer-files-msi-rather-than-to-install-the-package/] the firmware images from the MSI file by {{cmduser|wine msiexec /a ~/.wine/drive_c/DRIVERS/WWANQL/Driver/GobiInstaller.msi TARGETDIR<nowiki>=</nowiki>C:\\DRIVERS\\GOBI}}.
{{HINT|For enabling GPS, you will need a Windows installation with the Qualcomm Gobi 2000 Wireless WAN Driver installed, anyhow.}}

=== Choosing the Right Firmware ===

The firmware images are located in 11 directories. In general, each "officially" supported carrier has its own directory, as depicted in table "Firmware Images". The revision can be found in every file. The amms and apps files have the same revision and this one is reported by the {{cmd|AT I|}} command. The internal name of the UQCN file shows whether the firmware is for UMTS or CDMA2000. If your UMTS carrier is not listed, the default firmware and the generic UMTS firmware should work as their revisions match. The table "Non-listed Carrier Compatibility" summarizes the experiences of the Talk page.

{| {{prettytable}}
|+Firmware Images (Version 1.1.170/2.0.7.3 Released 2010/10/28)
! Dir !! Carrier !! Image !! MD5 message digest !! Revision !! Internal UQCN name
|-
| 0 || Vodafone || UQCN.mbn || 25ebf8314ed23394d23fb30ec4d73bf8 || D1025-UQCNABFD-2011 || 02-umts_vod-01024-011
|-
| 1 || Verizon
|
amss.mbn 
apps.mbn 
UQCN.mbn
|
06f76ed398458dad7b91c2d99a85a0a7 
88a60ed745d75fb1b92c539574ecc972 
2dccbd125ddd2cb327309ba75c6054d2
|
D1055-STUTDSVD-3580 
D1055-STUTDSVD-3580 
D1055-STUTDSVD-3580
| 02-c2k_vzw-00256-018
|-
| 2 || AT&T || UQCN.mbn || 1743cbe6de3172d6a35ff183c2716445 || D1025-UQCNASDD-2016 || 02-umts_att_noxtra-00768-144
|-
| 3 || Sprint
|
amss.mbn 
apps.mbn 
UQCN.mbn
|
d25f247cbe0fa481378d9f92c65c3e5e 
46fcb2423c31fd96e4645a90956264d2 
0ac877ed109f3c28d844b08f55c56185
|
D1055-STUTCSFD-3710 
D1055-STUTCSFD-3710 
D1055-UQCNCSFD-2015
| 02-c2k_sprint-00512-015
|-
| 4 || T-Mobile || UQCN.mbn || b0f5df651b34601bc21e3d8fcb064b19 || D1025-UQCNABLD-2011 || 02-umts_tmo_noxtra-01280-139
|-
| 6 || Generic UMTS || UQCN.mbn || bdf27325ebb63251c1310cd3a8f7bab6 || D1025-STUTABGD-3600 || 02-umts_gen-02304-018
|-
| 7 || Telefónica || UQCN.mbn || a1b941dd4c24e4f6542916c3e1e4634d || D1025-UQCNABHD-2012 || 02-umts_tellfon_nogps-03073-012
|-
| 8 || Telecom Italia || UQCN.mbn || 2f2a1b2b7f81735f0b8e4ea15c72b10b || D1025-UQCNABID-2011 || 02-umts_telital_noxtra-03584-139
|-
| 9 || Orange
|
amss.mbn 
apps.mbn 
UQCN.mbn
|
00c612a8a827dbef746f514e939fa77d 
7d12b38ec6851bef5039b74bffffd423 
735db64a57802e252ca4ff05d06b2f10
|
D1025-STUTABOD-3601 
D1025-STUTABOD-3601 
D1025-STUTABOD-3601
| 02-umts_orange-02816-012
|-
| 12 || DoCoMo
|
amss.mbn 
apps.mbn 
UQCN.mbn
|
4d6203bf9fe8ae1af439d4d163e91596 
385a22740f80c0d00f8acdd9ad637032 
e868df00bfa88596d588a52f872ff703
|
D1025-STUTABED-3587 
D1025-STUTABED-3587 
D1025-UQCNABED-2009
| 02-umts_doco-03328-009
|-
| UMTS || Default Firmware
|
amss.mbn 
apps.mbn
|
80fcfbb41a7d4331d4b7145972f5f3c4 
00cbd411048cdadc3e4caf0d89d14fca
|
D1025-STUTABGD-3600 
D1025-STUTABGD-3600
|-
|}

{| {{prettytable}}
|+Non-listed Carrier Compatibility
! Dir !! Image !! Works with
|-
| 0 || Vodafone || E-Plus Germany
|-
| 1 || Verizon ||
|-
| 2 || AT&T ||
|-
| 3 || Sprint ||
|-
| 4 || T-Mobile ||
|-
| 6 || Generic UMTS || O2 UK? O2 Germany
|-
| 7 || Telefónica ||
|-
| 8 || Telecom Italia ||
|-
| 9 || Orange ||
|-
| 12 || DoCoMo ||
|-
| UMTS || Default Firmware || UMTS unlocked, O2 UK? O2 Germany E-Plus Germany
|-
|}

=== Loading the Firmware ===
The firmware for this device must be loaded prior to using the device. It persists in the memory of the device until the next cold boot. Then, it has to be loaded again. The firmware can be loaded automatically via udev using the gobi_loader application[http://www.codon.org.uk/~mjg59/gobi_loader/]. This application expects the firmware image files (amss.mbn, apps.mbn, and UQCN.mbn) in {{path|/lib/firmware/gobi/}}. Thus, create this directory as root, when it does not exist, and copy the appropriate firmware files into the directory. The previous section helps you to obtain the correct files.

Technically, the firmware loading interface is exposed over USB as id 05c6:9204 which can be accessed as a character (ttyUSB) device under Linux using the qcserial driver. After successfully loading the firmware, the device switches to the USB id 05c6:9205 and exposes three character devices (ttyUSB).

== Modem ==
After the firmware is loaded, the modem is exposed over USB as id 05c6:9205 which can be accessed as a character (ttyUSB) device. Normal dial-up software can be used to create a 3G connection.

== GPS ==
Since kernel 2.6.37, or with a small kernel patch (submitted upstream: [http://marc.info/?l=linux-kernel&m=128534473802312&w=2]), two additional serial ports are available:
Diagnostics Monitor and NMEA GPS. The three serial ports are:
# /dev/ttyUSB0 -> Diagnostics
# /dev/ttyUSB1 -> 3G Modem
# /dev/ttyUSB2 -> NMEA GPS port

There is a PPA for the qcserial module for Ubuntu 10.10 which uses DKMS: [https://launchpad.net/~dveeden/+archive/thinkpad-fixes ppa:dveeden/thinkpad-fixes].

If you have another serial USB device activated before the Gobi the ttyUSB-numbers will certainly change.

The Diagnostics Monitor uses Qualcomm's DM protocol; I used libqcdm (ModemManager) to talk to it, found it working, but at least DM commands 12 and 64 are not implemented on my device (Thinkpad x100e).

The GPS port and how to enable it has been confirmed now in the Gobi 3000 source code at: https://www.codeaurora.org/patches/quic/gobi/ Enable/disable GPS with:
echo "\$GPS_START" > /dev/ttyUSB2
# use GPS
echo "\$GPS_STOP" > /dev/ttyUSB2

{{NOTE|Preconditions: this has only been tested with and without a 3G SIM card attached to the device and the firmware successfully loaded. It is not necessary though to be connected via 3G to be able to use GPS.
Also before you can use "$GPS_START/$GPS_STOP" feature, "Auto tracking" has to be enabled in the Options of the Lenovo Thinkvantage GPS Windows application[http://www-307.ibm.com/pc/support/site.wss/MIGR-73724.html]. The Thinkvantage GPS Windows application works with a clean Windows installation in a virtualizer that supports USB. However, it requires the Qualcomm Gobi 2000 Wireless WAN Driver[http://www-307.ibm.com/pc/support/site.wss/MIGR-72938.html] to be installed.
You will need to enable it only once.}}

To verify if the device is in the right mode use gpscat
$ gpscat /dev/ttyUSB2
6,,,,26,,,,13,,,*70
$GPGSV,4,2,16,14,,,,25,,,,08,,,,09,,,*7B
$GPGSV,4,3,16,32,,,,24,,,,,11,,,*73

You could use gpsctl to verify if gpsd detected the device correctly:
$ gpsctl
gpsctl: /dev/ttyUSB2 identified as Generic NMEA at 9600

Detection can take a few minutes.

If gpsd didn't detect the serial port the use the following line:
sudo /lib/udev/gpsd.hotplug add /dev/ttyUSB2

Use xgps or cgps to verify if the GPS has a fix. If it does have a fix you could use [http://www.tangogps.org TangoGPS] or any other GPS tool which uses gpsd.

To use GPS for time synchronization add the following lines to /etc/ntp.conf:
server 127.127.28.0 minpoll 4 prefer
fudge 127.127.28.0 time1 0.183 refid NMEA

The 0.183 is for [http://en.wikipedia.org/wiki/NMEA_0183 NMEA 0183]

If it works it will look like this:
# ntpq -c peers
remote refid st t when poll reach delay offset jitter
==============================================================================
*SHM(0) .NMEA. 0 l 15 16 317 0.000 -49.965 5.312

== Carrier specific configurations ==
Each device is intended to be used with a specific carrier, and is shipped with firmware to support that carrier. Notebooks are often also shipped with a pre-installed SIM. Other carriers may work by loading a different firmware version. The 'generic UMTS' stage 3 firmware is known to with with O2, an unsupported UK carrier. See above for a list of known firmware files.

{{NOTE|It may be illegal or a breach of contract in various countries to bypass a carrier lock}}

== Troubleshooting ==

Some users have experienced the modem entering a strange state in which it refuses any attempt of loading the firmware.
There seem to be at least two ways to reset the modem to get it working as normally again:

1) try to disable WWAN in BIOS and boot your computer.
Then shut down it, and enable WWAN again. OR:

2) remove the AC adapter as well as the battery pack and then hold the power button for some time (approx 30 sec. - 1 min.).
Then insert the battery again and boot as usual.

See discussion page (22 - 23 January 2011) for further details.
--[[User:stman|stman]] 10:10, 23 January 2011 (UTC)

== Links ==
* [http://www.gobianywhere.com/sites/default/files/gobi2000_overview.pdf Gobi 2000 Product Sheet]
* [http://mail.cdmwireless.com/gobi2000/docs/AT_Command_Set_Gobi.pdf AT Command Set in Gobi]
* [http://mail.cdmwireless.com/gobi2000/docs/Gobi_Connection_Manager_FAQ.pdf Gobi Connection Manager FAQ]

== ThinkPads this device may be found in ==
'''AT&T service contract may be required'''
* {{Edge 14"}}, {{Edge 15"}}
* {{T410}}, {{T410s}}, {{T510}}
* {{W510}}
* {{X100e}}

'''Verizon service contract may be required'''
* {{Edge 14"}}, {{Edge 15"}}
* {{L412}}, {{L512}}
* {{T410}}, {{T410s}}, {{T410si}}, {{T510}}
* {{X201}}, {{X201 Tablet}}

'''Gobi 2000 WWAN upgradable'''
{{NOTE|not every ThinkPad listed here can actually be upgraded}}
* {{Edge 13"}}
* {{T410}}, {{T410s}}, {{T410si}}, {{T510}}
* {{W510}}
* {{X100e}}, {{X201}}, {{X201 Tablet}}

Talk:Qualcomm Gobi 2000

2011-01-23T09:29:28Z

Invented:

== Firmware ==

I found out a way to get the firmware on a linux-only system. Mine is a debian squeeze, but it should apply to any system.

First, I entered my model number on the [http://www.lenovo.com/support/ Lenovo support page] in the right siderow (Select you system / Quick Path) to get to my drivers page. There I clicked to download drivers and on the UMTS drivers. Afterwards I downloaded the "<code>7xwc42ww.exe</code>" driver package.

You dont need to enter your serial number to the lenovo support page. With some googling i came up with [http://www-307.ibm.com/pc/support/site.wss/MIGR-72938.html this] page. This is very useful for all those owning a laptop not built by lenovo. ([[User:Bob the builder|bob]])

With wine I was able to install the driver package, but all it does, was unpacking the GOBI driver setup. This one comes packaged as a <code>.msi</code> file, so we have to [http://sysblogd.wordpress.com/2008/05/10/howto-extract-all-files-from-microsoft-installer-files-msi-rather-than-to-install-the-package/ unpack] it:

user@machine:~$ wine msiexec /a ~/.wine/drive_c/DRIVERS/WWANQL/Driver/GobiInstaller.msi TARGETDIR=C:\\DRIVERS\\GOBI

The installer quits with errors, but leaves the files on the disk, success. But now there are several subdirectories, in which the files for the specific network operators reside:

{| {{prettytable}}
! Dir !! Image !! Remarks
|-
| 0 || Vodafone Image ||
|-
| 1 || Verizon Image ||
|-
| 2 || ATT Image ||
|-
| 3 || Sprint Image || includes special Firmware
|-
| 4 || T-Mobile Image ||
|-
| 6 || Generic UMTS Image ||
|-
| 7 || Telefonica Image ||
|-
| 8 || Telecom Italia Image ||
|-
| 9 || Orange Image ||
|-
| 12 || DoCoMo Image || includes special Firmware
|-
| UMTS || Default Firmware || the MD5-sum on the page matches these
|}
t

I found this out by reading the <code>ReadMe.rtf</code>, looking into the <code>UQCN.mbn</code>-Files and apply a little bit of thinking.

Now I'll move the files over and try them out.
------------------------------------------------------------------------------------------------------------------------------------------

So I got the Sprint Image with firmware, how does one flash the Gobi with this firmware?

You do not need to flash the gobi as such. Firmware must be loaded at every boot. Simply use the gobi_loader mentioned on the main page, with the 3 firmware files from the sprint directory. You will need to modify it to match your USB IDs. After the firmware it loaded it will last until you power off your laptop. I usually reboot after loading the firmware, but before trying to use the modem. The firmware remains loaded. [[User:Catphish|Catphish]]

--
I appear to have got the WWAN portion functioning but can't find any reference to anyone using the GPS part. Does this work under Linux yet? [[User:Bjb|Bjb]]

For me this images work with eplus germany --[[User:Lynxis|Lynxis]] 23:13, 8 June 2010 (UTC)

84d002b0ef003cde6c95826bfbf067fe /lib/firmware/gobi/amss.mbn
d7496085f1af3d1bfdf0fa60c3222766 /lib/firmware/gobi/apps.mbn
c3d6fd93ae2e52775ef9cd8fccbc20be /lib/firmware/gobi/UQCN.mbn

$ find -type f -exec md5sum {} \; | sort -k 2
c3d6fd93ae2e52775ef9cd8fccbc20be ./0/UQCN.mbn
4d6203bf9fe8ae1af439d4d163e91596 ./12/amss.mbn
385a22740f80c0d00f8acdd9ad637032 ./12/apps.mbn
e868df00bfa88596d588a52f872ff703 ./12/UQCN.mbn
48191d62dc4091fb9d23e0b947611c58 ./1/amss.mbn
4f46a856fcceb197943d0cf3257c3621 ./1/apps.mbn
bb05d912e27b822348d4de93fc3ac911 ./1/UQCN.mbn
ff935ec4da6f6711b48caaddcf737566 ./2/UQCN.mbn
4f74d79ed8df027db3b75e36feb2bd27 ./3/amss.mbn
d9ff7b27c491332650b1efbbee64ee31 ./3/apps.mbn
6f6462fe0cc185cc3dc24720a28770fb ./3/UQCN.mbn
46418504e70971bda7b2ee34cc80b5b7 ./4/UQCN.mbn
1aa5727b034dd1f371a3412d5800c1a3 ./6/UQCN.mbn
9f6773625d59098f9360c24263d99615 ./7/UQCN.mbn
e012286117c0c7708369f8dbc7906e64 ./8/UQCN.mbn
c65246da47695b4ecaaf098a02718c9d ./9/UQCN.mbn
84d002b0ef003cde6c95826bfbf067fe ./UMTS/amss.mbn
d7496085f1af3d1bfdf0fa60c3222766 ./UMTS/apps.mbn

For me this tutorial above worked, too. Is there anything which prevents us from copying it to the page itself? --[[User:Aneiser|Aneiser]] 20:58, 21 August 2010 (UTC)

== 2.6.32, 2.6.34, git snapshots and later ==

so it's working with recent kernels or no? And add any info about GPS, please. [[User:Tensai.cirno|Tensai.cirno]] 02:26, 16 June 2010 (UTC)

I had no luck with 2.6.34. however i tested 2.6.35-rc3 + gobi_loader 0.6 and it worked. had to load the firmware by hand though ...
"/lib/udev/gobi_loader -2000 /dev/ttyUSB0 /lib/firmware/gobi" but i guess the id in the udev file is not the right one for my card. --[[User:Max p|Max p]] 02:09, 22 June 2010 (UTC)

Thanks a lot, this is ''very good'' news. [[User:Tensai.cirno|Tensai.cirno]] 06:54, 23 June 2010 (UTC)

Yes, with 2.6.35 and gobi_loader 0.7 it works for me (T510, O2 Germany, Generic firmware) --[[User:Aneiser|Aneiser]] 21:00, 21 August 2010 (UTC)

The modem also works with 2.6.36 (2.6.36-1~experimental.1) and gobi-loader 0.6.1 from current Debian Testing/Sid/Experimental. GPS doesn’t, although I did apply the patch; /dev/ttyUSB2 doesn't output anything at all – maybe testing outside is necessary. [[User:X2017|X2017]] 20:44, 14 November 2010 (UTC)

== GPS ==

Has anyone managed to get GPS to work yet? I think one has to send certain AT commands to receive the NMEA information (at least that is how it works with some Ericsson modems).
Unfortunately I can't find an AT command reference for the Qualcomm Gobi 2000 ...
[[User:Flyser|Flyser]] 14:15, 27 July 2010 (UTC)

i was asking the qualcomm support about that subject, handing out all AT commands. lets say it that way they were not very cooperative. but you could ask them as well, maybe you got more effective than me and we can have the commands :)--[[User:Max p|Max p]] 09:10, 4 August 2010 (UTC)

so did I. I was told to contact Lenovo about the issue -.- --[[User:Flyser|Flyser]] 08:10, 9 August 2010 (UTC)

You can find the documentation and sdk [http://gobianywhere.com/sdk/index.php here]. However I didn't find any useful AT commands, and I think the SDK is win only. [[User:bbandi|bbandi]] 22:32, 14 August 2010 (UTC)

Did you try to install the SDK? Is it possible to analyze how GPS works? --[[User:Aneiser|Aneiser]] 22:00, 21 August 2010 (UTC)

Has anyone managed to get GPS to work with the information published on this wiki page? I get all three devices (ttyUSB[012]), but ttyUSB2 does not output anything. Do I have to connect to a wireless network to get this to work? Could someone publish a more detailed guide how to _use_ the gps? I tried:
# cat /dev/ttyUSB2 &
# echo -n "\$GPS_START" > /dev/ttyUSB2
--[[User:Flyser|Flyser]] 11:03, 30 September 2010 (UTC)

I also cannot get the GPS to work even with the new instructions. Googling around, I found that the start string could be "$GPS-START" (Hyphen instead of underline). However, this doesn't work either. The GPS *did* work on the preinstalled Windows 7. I'm using basic UMTS firmware (firmware from folders "UMTS" and "6").
--[[User:Zarhan|Zarhan]] 06:40, 1 October 2010 (UTC)

I was able to get it to work on a X201, after using the 6/UQCN.mbn image from my Windows 7 x64 partition. This seems to be different from the files/checksums above:
root@polaris:~# md5sum /lib/firmware/gobi/*.mbn
84d002b0ef003cde6c95826bfbf067fe /lib/firmware/gobi/amss.mbn
d7496085f1af3d1bfdf0fa60c3222766 /lib/firmware/gobi/apps.mbn
68e46b936d5400862a0381b101af3972 /lib/firmware/gobi/UQCN.mbn

Now to seems to work:
root@polaris:~# cat /dev/ttyUSB2 &
[1] 3320
root@polaris:~# echo "\$GPS_START" > /dev/ttyUSB2; sleep 3; echo "\$GPS_STOP" > /dev/ttyUSB2
$GPGSA,A,1,,,,,,,,,,,,,,,*1E
$GPGSV,4,1,16,14,33,050,35,24,42,115,28,20,55,246,26,19,19,172,25*77
$GPGSV,4,2,16,11,75,237,,17,29,309,,23,07,192,,28,10,267,*7F
$GPGSV,4,3,16,31,08,106,,32,80,227,,30,,,,29,,,*72
$GPGSV,4,4,16,27,,,,26,,,,25,,,,22,,,*78
$GPGGA,192126.0,,,,,0,,,,,,,,*77
$PQXFI,192126.0,,,,,,,,*6B
$GPVTG,,T,,M,,N,,K,N*2C
$GPRMC,,V,,,,,,,,,,N*53
$GPGSA,A,1,,,,,,,,,,,,,,,*1E
$GPGGA,192127.0,52xx.xxxxxx,N,0xxxx.xxxxxx,E,1,05,1.8,30.6,M,46.0,M,,*61
$PQXFI,192127.0,52xx.xxxxxx,N,0xxxx.xxxxxx,E,30.6,80.58,93.58,3.17*5B
$GPVTG,nan,T,nan,M,0.0,N,0.0,K,A*23
root@polaris:~#

On Debian, using '/lib/udev/gpsd.hotplug add /dev/ttyUSB2' you can tell gpsd about the serial device.
--[[User:Shoragan|Shoragan]] 20:07, 11 October 2010 (UTC)

I'm using exactly same firmwares as Shoragan, and I can see the ttyUSB2 device - however, no NMEA data starts to appear after issuing $GPS_START. I'm using W510 --[[User:Zarhan|Zarhan]] 06:03, 13 October 2010 (UTC)

Same here: using {{openSUSE}} 11.3 with kernel of the day (2.6.37-rc3-3, includes the qcserial patches), gobi_loader 0.7 and current fw files from win partition:
* Gps works in win 7/64 ({{T510i}}) with drivers updated yesterday (most fw files have different md5 sums from those above)
* Copied fw from 1/ to /lib/firmware/gobi/ (also tried the others, but these are the ones working in windows)
* Usb device id changes from x9204 to x9205 automatically (fw gets loaded)
* 3 tty devices appear automatically (udev and module config is ok)
* Modem at ttyUSB1 is functional (at i command in minicom gives fw version and imei)
* ttyUSB0 and ttyUSB2 seem to be dead though (cat, minicom)
--[[User:Joban|Joban]] 19:08, 13 December 2010 (UTC)
*** In windows GPS & wifi work simultaneously? Maybe you should switch off wifi & try GPS? I read official "Lenovo Russia" blog - in the earlier versions BIOS in X100e you can use only wifi '''or''' 3G --[[User:Evadim|Evadim]] 21:10, 13 December 2010 (UTC)

Evadim, I assume with wifi you mean UMTS/GSM, not WLAN (agn) I don't know. I don't use UMTS/GSM (for now). How would I explicitly deactivate 3G/wifi/UMTS/GSM in linux?
Btw. I narrowed down used fw a bit: The firmwares in the "1" directory sometimes hangs the boot process for me and fw dosn't load. I use UMTS/ and 6/
files now --[[User:Joban|Joban]] 16:26, 16 December 2010 (UTC)

I tried with newer firmware that comes with the latest WWan driver (driver version 2.0.7.3) at http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-72938&medium=rssW510#20101028 - still doesn't work. --[[User:Zarhan|Zarhan]] 15:25, 29 November 2010 (UTC)

Got it! Wooohooo! I think it work after last BIOS upgrade (lenovo s10-3t), I install win7 for testing GOBI module, upgrade BIOS, test GPS & 3G. After I reboot in to linux - GPS start working. --[[User:Evadim|Evadim]] 17:01, 5 December 2010 (UTC)

Guys! 4 hours of sex with USB protocol debugging in Qemu and "$GPS_START/GPS_STOP" is working now! :)
No firmwares, no bios upgrades, forget about it.
All is simple, in default Lenovo GPS application(ThinkVantage GPS) all NMEA data goes through broadband ethernet virtual interface and enabled by some proprietary protocol. Windows NMEA port is uneuseful before you click button "Start" in ThinkVantage GPS(driver automatically prepend GPS_START string to any connection started on qualcomm nmea port). But if we go to the Preferences of this GPS tracker, and enable checkbox "Auto tracking", Gobi 2000 start to automaticlly enable GPS through its proprietary protocol when new connection appears on NMEA port and it see string "$GPS_START".

So, u only need to install Windows on your machine(or install it on virtual machine), install GPS tracker from Lenovo and simple enable "Auto tracking" checkbox in GPS tracker preferences. After that, u can remove Windows and enjoy GPS in any OS on your notebook. --[[User:Invented|Invented]] 21:50, 25 December 2010 (UTC)

I can confirm that the above trick works. I simply installed VirtualBox, placed Windows XP in it, set Virtualbox to pass-through Qualcomm USB to the Windows, and installed the WWan drivers (see link above) and the GPS Tracker software. Thanks a lot! --[[User:Zarhan|Zarhan]] 08:30, 27 December 2010 (UTC)

I owe you a beer if this works. Sounds awesome, thanks!
EDIT: works fine (also with the vbox method). --[[User:Flyser|Flyser]] 14:36, 29 December 2010 (UTC)

I use WinXP I have updated my WWAN driver and have enabled the checkbox "Auto tracking" and rebooted my linux but I just have a ttyUSB0 what to do?

You have to use a kernel newer than 2.6.37 or you have to apply this patch to your kernel http://marc.info/?l=linux-kernel&m=128534473802312&w=2 --[[User:Flyser|Flyser]] 9. Januar 2011

I tryed Ubuntu alpha 1 with 2.6.37.X but just got a ttyUSB0. Do you know a liveCD in wich the gobi GPS is working?

You also need to install firmware and load it with gobi-loader. See other parts of discussion. If you type "lsusb" and see 05c6:9204, you haven't loaded the firmware and see just ttyUSB0. Once you have loaded the firmware, lsusb shows 05c6:9205, and you should have ttyUSB0-2. --[[User:Zarhan|Zarhan]] 08:53, 11 January 2011 (UTC)

After a long time of waiting for better support for the Gobi 2000, I was really happy to read the advise by Invented from Dec. 25, on how to get the GPS working.
Before that I had already been able to get the firmware loaded properly and (with the kernel patch mentioned above) all three devices showed up as /dev/ttyUSB[012].
The modem had also been working as expected.
With the hint from Invented, I was confident to get the GPS working, too.

I'm running Ubuntu GNU/Linux Maverick Meerkat on my T410.
I don't have multiboot, so Windows XP (all official updates installed) is running under qemu with kvm.
SIM card is inserted (FONIC, using the German O2 network).

I've given full access to all the USB (sudo chmod -R 777 /dev/bus/usb/) and started qemu with command line option: -usbdevice host:05c6:9205 (passing through the USB-device).
I've installed the installed the drivers for the Gobi 2000 (7xwc45ww.exe) and ThinkVantage GPS (81gp09ww.exe).
After realizing that ThinkVantage GPS wouldn't run, I also installed Access Connections (85cx28ww.exe).
Then I was able to start ThinkVantage GPS, followed the instructions to turn off the hardware switch,
checked the Auto Tracking box (also switched to km/h and unchecked the warning box),
closed ThinkVantage GPS, and shut down Windows.

After that I performed a reboot of my host system.
And here's were the problem started: Something slowed down the boot process by several minutes
(meanwhile I know that it's the gobi_loader that hangs).
After logging into the system I saw only /dev/ttyUSB0.
Checking lsusb, I realized that the firmware had not been loaded yet.
Trying to run gobi_loader manually resulted in a hangup of gobi_loader.
Several subsequent reboots and even disconnecting the laptop from power and battery did not solve the problem.

I also tried to pass through host:05c6:9204 to the virtual machine and hoped for Windows to load the firmware.
But the usb device 05c6:9204 wouldn't even show up in the device manager nor in the qemu montior (info usb).

Is there any way to reset the Gobi 2000 to the original state?
Is there any explanation what went wrong?

Thanks a lot in advance!
--[[stman|stman]] 22 January 2011

stman, try to disable WWAN in BIOS and boot your computer. Then shut down it, and enable WWAN again. This works for me, when my gobi 200 enters some strange state and refuses to load firmware. --[[User:Invented|Invented]] 09:29, 23 January 2011 (UTC)

Talk:Qualcomm Gobi 2000

2010-12-25T22:27:39Z

Invented:

Qualcomm Gobi 2000

2010-12-25T22:26:00Z

Invented: /* GPS */

Talk:Qualcomm Gobi 2000

2010-12-25T22:23:31Z

Invented:

== Firmware ==

I found out a way to get the firmware on a linux-only system. Mine is a debian squeeze, but it should apply to any system.

First, I entered my model number on the [http://www.lenovo.com/support/ Lenovo support page] in the right siderow (Select you system / Quick Path) to get to my drivers page. There I clicked to download drivers and on the UMTS drivers. Afterwards I downloaded the "<code>7xwc42ww.exe</code>" driver package.

You dont need to enter your serial number to the lenovo support page. With some googling i came up with [http://www-307.ibm.com/pc/support/site.wss/MIGR-72938.html this] page. This is very useful for all those owning a laptop not built by lenovo. ([[User:Bob the builder|bob]])

With wine I was able to install the driver package, but all it does, was unpacking the GOBI driver setup. This one comes packaged as a <code>.msi</code> file, so we have to [http://sysblogd.wordpress.com/2008/05/10/howto-extract-all-files-from-microsoft-installer-files-msi-rather-than-to-install-the-package/ unpack] it:

user@machine:~$ wine msiexec /a ~/.wine/drive_c/DRIVERS/WWANQL/Driver/GobiInstaller.msi TARGETDIR=C:\\DRIVERS\\GOBI

The installer quits with errors, but leaves the files on the disk, success. But now there are several subdirectories, in which the files for the specific network operators reside:

{| {{prettytable}}
! Dir !! Image !! Remarks
|-
| 0 || Vodafone Image ||
|-
| 1 || Verizon Image ||
|-
| 2 || ATT Image ||
|-
| 3 || Sprint Image || includes special Firmware
|-
| 4 || T-Mobile Image ||
|-
| 6 || Generic UMTS Image ||
|-
| 7 || Telefonica Image ||
|-
| 8 || Telecom Italia Image ||
|-
| 9 || Orange Image ||
|-
| 12 || DoCoMo Image || includes special Firmware
|-
| UMTS || Default Firmware || the MD5-sum on the page matches these
|}
t

I found this out by reading the <code>ReadMe.rtf</code>, looking into the <code>UQCN.mbn</code>-Files and apply a little bit of thinking.

Now I'll move the files over and try them out.
------------------------------------------------------------------------------------------------------------------------------------------

So I got the Sprint Image with firmware, how does one flash the Gobi with this firmware?

You do not need to flash the gobi as such. Firmware must be loaded at every boot. Simply use the gobi_loader mentioned on the main page, with the 3 firmware files from the sprint directory. You will need to modify it to match your USB IDs. After the firmware it loaded it will last until you power off your laptop. I usually reboot after loading the firmware, but before trying to use the modem. The firmware remains loaded. [[User:Catphish|Catphish]]

--
I appear to have got the WWAN portion functioning but can't find any reference to anyone using the GPS part. Does this work under Linux yet? [[User:Bjb|Bjb]]

For me this images work with eplus germany --[[User:Lynxis|Lynxis]] 23:13, 8 June 2010 (UTC)

84d002b0ef003cde6c95826bfbf067fe /lib/firmware/gobi/amss.mbn
d7496085f1af3d1bfdf0fa60c3222766 /lib/firmware/gobi/apps.mbn
c3d6fd93ae2e52775ef9cd8fccbc20be /lib/firmware/gobi/UQCN.mbn

$ find -type f -exec md5sum {} \; | sort -k 2
c3d6fd93ae2e52775ef9cd8fccbc20be ./0/UQCN.mbn
4d6203bf9fe8ae1af439d4d163e91596 ./12/amss.mbn
385a22740f80c0d00f8acdd9ad637032 ./12/apps.mbn
e868df00bfa88596d588a52f872ff703 ./12/UQCN.mbn
48191d62dc4091fb9d23e0b947611c58 ./1/amss.mbn
4f46a856fcceb197943d0cf3257c3621 ./1/apps.mbn
bb05d912e27b822348d4de93fc3ac911 ./1/UQCN.mbn
ff935ec4da6f6711b48caaddcf737566 ./2/UQCN.mbn
4f74d79ed8df027db3b75e36feb2bd27 ./3/amss.mbn
d9ff7b27c491332650b1efbbee64ee31 ./3/apps.mbn
6f6462fe0cc185cc3dc24720a28770fb ./3/UQCN.mbn
46418504e70971bda7b2ee34cc80b5b7 ./4/UQCN.mbn
1aa5727b034dd1f371a3412d5800c1a3 ./6/UQCN.mbn
9f6773625d59098f9360c24263d99615 ./7/UQCN.mbn
e012286117c0c7708369f8dbc7906e64 ./8/UQCN.mbn
c65246da47695b4ecaaf098a02718c9d ./9/UQCN.mbn
84d002b0ef003cde6c95826bfbf067fe ./UMTS/amss.mbn
d7496085f1af3d1bfdf0fa60c3222766 ./UMTS/apps.mbn

For me this tutorial above worked, too. Is there anything which prevents us from copying it to the page itself? --[[User:Aneiser|Aneiser]] 20:58, 21 August 2010 (UTC)

== 2.6.32, 2.6.34, git snapshots and later ==

so it's working with recent kernels or no? And add any info about GPS, please. [[User:Tensai.cirno|Tensai.cirno]] 02:26, 16 June 2010 (UTC)

I had no luck with 2.6.34. however i tested 2.6.35-rc3 + gobi_loader 0.6 and it worked. had to load the firmware by hand though ...
"/lib/udev/gobi_loader -2000 /dev/ttyUSB0 /lib/firmware/gobi" but i guess the id in the udev file is not the right one for my card. --[[User:Max p|Max p]] 02:09, 22 June 2010 (UTC)

Thanks a lot, this is ''very good'' news. [[User:Tensai.cirno|Tensai.cirno]] 06:54, 23 June 2010 (UTC)

Yes, with 2.6.35 and gobi_loader 0.7 it works for me (T510, O2 Germany, Generic firmware) --[[User:Aneiser|Aneiser]] 21:00, 21 August 2010 (UTC)

The modem also works with 2.6.36 (2.6.36-1~experimental.1) and gobi-loader 0.6.1 from current Debian Testing/Sid/Experimental. GPS doesn’t, although I did apply the patch; /dev/ttyUSB2 doesn't output anything at all – maybe testing outside is necessary. [[User:X2017|X2017]] 20:44, 14 November 2010 (UTC)

== GPS ==

Has anyone managed to get GPS to work yet? I think one has to send certain AT commands to receive the NMEA information (at least that is how it works with some Ericsson modems).
Unfortunately I can't find an AT command reference for the Qualcomm Gobi 2000 ...
[[User:Flyser|Flyser]] 14:15, 27 July 2010 (UTC)

i was asking the qualcomm support about that subject, handing out all AT commands. lets say it that way they were not very cooperative. but you could ask them as well, maybe you got more effective than me and we can have the commands :)--[[User:Max p|Max p]] 09:10, 4 August 2010 (UTC)

so did I. I was told to contact Lenovo about the issue -.- --[[User:Flyser|Flyser]] 08:10, 9 August 2010 (UTC)

You can find the documentation and sdk [http://gobianywhere.com/sdk/index.php here]. However I didn't find any useful AT commands, and I think the SDK is win only. [[User:bbandi|bbandi]] 22:32, 14 August 2010 (UTC)

Did you try to install the SDK? Is it possible to analyze how GPS works? --[[User:Aneiser|Aneiser]] 22:00, 21 August 2010 (UTC)

Has anyone managed to get GPS to work with the information published on this wiki page? I get all three devices (ttyUSB[012]), but ttyUSB2 does not output anything. Do I have to connect to a wireless network to get this to work? Could someone publish a more detailed guide how to _use_ the gps? I tried:
# cat /dev/ttyUSB2 &
# echo -n "\$GPS_START" > /dev/ttyUSB2
--[[User:Flyser|Flyser]] 11:03, 30 September 2010 (UTC)

I also cannot get the GPS to work even with the new instructions. Googling around, I found that the start string could be "$GPS-START" (Hyphen instead of underline). However, this doesn't work either. The GPS *did* work on the preinstalled Windows 7. I'm using basic UMTS firmware (firmware from folders "UMTS" and "6").
--[[User:Zarhan|Zarhan]] 06:40, 1 October 2010 (UTC)

I was able to get it to work on a X201, after using the 6/UQCN.mbn image from my Windows 7 x64 partition. This seems to be different from the files/checksums above:
root@polaris:~# md5sum /lib/firmware/gobi/*.mbn
84d002b0ef003cde6c95826bfbf067fe /lib/firmware/gobi/amss.mbn
d7496085f1af3d1bfdf0fa60c3222766 /lib/firmware/gobi/apps.mbn
68e46b936d5400862a0381b101af3972 /lib/firmware/gobi/UQCN.mbn

Now to seems to work:
root@polaris:~# cat /dev/ttyUSB2 &
[1] 3320
root@polaris:~# echo "\$GPS_START" > /dev/ttyUSB2; sleep 3; echo "\$GPS_STOP" > /dev/ttyUSB2
$GPGSA,A,1,,,,,,,,,,,,,,,*1E
$GPGSV,4,1,16,14,33,050,35,24,42,115,28,20,55,246,26,19,19,172,25*77
$GPGSV,4,2,16,11,75,237,,17,29,309,,23,07,192,,28,10,267,*7F
$GPGSV,4,3,16,31,08,106,,32,80,227,,30,,,,29,,,*72
$GPGSV,4,4,16,27,,,,26,,,,25,,,,22,,,*78
$GPGGA,192126.0,,,,,0,,,,,,,,*77
$PQXFI,192126.0,,,,,,,,*6B
$GPVTG,,T,,M,,N,,K,N*2C
$GPRMC,,V,,,,,,,,,,N*53
$GPGSA,A,1,,,,,,,,,,,,,,,*1E
$GPGGA,192127.0,52xx.xxxxxx,N,0xxxx.xxxxxx,E,1,05,1.8,30.6,M,46.0,M,,*61
$PQXFI,192127.0,52xx.xxxxxx,N,0xxxx.xxxxxx,E,30.6,80.58,93.58,3.17*5B
$GPVTG,nan,T,nan,M,0.0,N,0.0,K,A*23
root@polaris:~#

On Debian, using '/lib/udev/gpsd.hotplug add /dev/ttyUSB2' you can tell gpsd about the serial device.
--[[User:Shoragan|Shoragan]] 20:07, 11 October 2010 (UTC)

I'm using exactly same firmwares as Shoragan, and I can see the ttyUSB2 device - however, no NMEA data starts to appear after issuing $GPS_START. I'm using W510 --[[User:Zarhan|Zarhan]] 06:03, 13 October 2010 (UTC)

Same here: using {{openSUSE}} 11.3 with kernel of the day (2.6.37-rc3-3, includes the qcserial patches), gobi_loader 0.7 and current fw files from win partition:
* Gps works in win 7/64 ({{T510i}}) with drivers updated yesterday (most fw files have different md5 sums from those above)
* Copied fw from 1/ to /lib/firmware/gobi/ (also tried the others, but these are the ones working in windows)
* Usb device id changes from x9204 to x9205 automatically (fw gets loaded)
* 3 tty devices appear automatically (udev and module config is ok)
* Modem at ttyUSB1 is functional (at i command in minicom gives fw version and imei)
* ttyUSB0 and ttyUSB2 seem to be dead though (cat, minicom)
--[[User:Joban|Joban]] 19:08, 13 December 2010 (UTC)
*** In windows GPS & wifi work simultaneously? Maybe you should switch off wifi & try GPS? I read official "Lenovo Russia" blog - in the earlier versions BIOS in X100e you can use only wifi '''or''' 3G --[[User:Evadim|Evadim]] 21:10, 13 December 2010 (UTC)

Evadim, I assume with wifi you mean UMTS/GSM, not WLAN (agn) I don't know. I don't use UMTS/GSM (for now). How would I explicitly deactivate 3G/wifi/UMTS/GSM in linux?
Btw. I narrowed down used fw a bit: The firmwares in the "1" directory sometimes hangs the boot process for me and fw dosn't load. I use UMTS/ and 6/
files now --[[User:Joban|Joban]] 16:26, 16 December 2010 (UTC)

I tried with newer firmware that comes with the latest WWan driver (driver version 2.0.7.3) at http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-72938&medium=rssW510#20101028 - still doesn't work. --[[User:Zarhan|Zarhan]] 15:25, 29 November 2010 (UTC)

Got it! Wooohooo! I think it work after last BIOS upgrade (lenovo s10-3t), I install win7 for testing GOBI module, upgrade BIOS, test GPS & 3G. After I reboot in to linux - GPS start working. --[[User:Evadim|Evadim]] 17:01, 5 December 2010 (UTC)

Guys! 4 hours of sex with USB protocol debugging in Qemu and "$GPS_START/GPS_STOP" is working now! :)
No firmwares, no bios upgrades, forget about it.
All is simple, in default Lenovo GPS application(GPS tracker) all NMEA data goes through broadband ethernet vitrual interface and enabled by some proprietary protocol. Windows NMEA port is uneuseful before you click button "Start" in GPS tracker(driver adds GPS_START string to any connection started on qualcomm nmea port). But if we go to the Preferences of this GPS tracker, and enable checkbox "Auto tracking", Gobi 2000 start to automaticlly enable GPS when new connection appears on NMEA port and it see string "$GPS_START".

So, u only need to install Windows on your machine(or install it on virtual machine), install GPS tracker from Lenovo and simple enable "Auto tracking" checkbox in GPS tracker preferences. After that, u can remove Windows and enjoy GPS in any OS on your notebook. --[[User:Invented|Invented]] 21:50, 25 December 2010 (UTC)

Talk:Qualcomm Gobi 2000

2010-12-25T21:50:48Z

Invented:

== Firmware ==

I found out a way to get the firmware on a linux-only system. Mine is a debian squeeze, but it should apply to any system.

First, I entered my model number on the [http://www.lenovo.com/support/ Lenovo support page] in the right siderow (Select you system / Quick Path) to get to my drivers page. There I clicked to download drivers and on the UMTS drivers. Afterwards I downloaded the "<code>7xwc42ww.exe</code>" driver package.

You dont need to enter your serial number to the lenovo support page. With some googling i came up with [http://www-307.ibm.com/pc/support/site.wss/MIGR-72938.html this] page. This is very useful for all those owning a laptop not built by lenovo. ([[User:Bob the builder|bob]])

With wine I was able to install the driver package, but all it does, was unpacking the GOBI driver setup. This one comes packaged as a <code>.msi</code> file, so we have to [http://sysblogd.wordpress.com/2008/05/10/howto-extract-all-files-from-microsoft-installer-files-msi-rather-than-to-install-the-package/ unpack] it:

user@machine:~$ wine msiexec /a ~/.wine/drive_c/DRIVERS/WWANQL/Driver/GobiInstaller.msi TARGETDIR=C:\\DRIVERS\\GOBI

The installer quits with errors, but leaves the files on the disk, success. But now there are several subdirectories, in which the files for the specific network operators reside:

{| {{prettytable}}
! Dir !! Image !! Remarks
|-
| 0 || Vodafone Image ||
|-
| 1 || Verizon Image ||
|-
| 2 || ATT Image ||
|-
| 3 || Sprint Image || includes special Firmware
|-
| 4 || T-Mobile Image ||
|-
| 6 || Generic UMTS Image ||
|-
| 7 || Telefonica Image ||
|-
| 8 || Telecom Italia Image ||
|-
| 9 || Orange Image ||
|-
| 12 || DoCoMo Image || includes special Firmware
|-
| UMTS || Default Firmware || the MD5-sum on the page matches these
|}
t

I found this out by reading the <code>ReadMe.rtf</code>, looking into the <code>UQCN.mbn</code>-Files and apply a little bit of thinking.

Now I'll move the files over and try them out.
------------------------------------------------------------------------------------------------------------------------------------------

So I got the Sprint Image with firmware, how does one flash the Gobi with this firmware?

You do not need to flash the gobi as such. Firmware must be loaded at every boot. Simply use the gobi_loader mentioned on the main page, with the 3 firmware files from the sprint directory. You will need to modify it to match your USB IDs. After the firmware it loaded it will last until you power off your laptop. I usually reboot after loading the firmware, but before trying to use the modem. The firmware remains loaded. [[User:Catphish|Catphish]]

--
I appear to have got the WWAN portion functioning but can't find any reference to anyone using the GPS part. Does this work under Linux yet? [[User:Bjb|Bjb]]

For me this images work with eplus germany --[[User:Lynxis|Lynxis]] 23:13, 8 June 2010 (UTC)

84d002b0ef003cde6c95826bfbf067fe /lib/firmware/gobi/amss.mbn
d7496085f1af3d1bfdf0fa60c3222766 /lib/firmware/gobi/apps.mbn
c3d6fd93ae2e52775ef9cd8fccbc20be /lib/firmware/gobi/UQCN.mbn

$ find -type f -exec md5sum {} \; | sort -k 2
c3d6fd93ae2e52775ef9cd8fccbc20be ./0/UQCN.mbn
4d6203bf9fe8ae1af439d4d163e91596 ./12/amss.mbn
385a22740f80c0d00f8acdd9ad637032 ./12/apps.mbn
e868df00bfa88596d588a52f872ff703 ./12/UQCN.mbn
48191d62dc4091fb9d23e0b947611c58 ./1/amss.mbn
4f46a856fcceb197943d0cf3257c3621 ./1/apps.mbn
bb05d912e27b822348d4de93fc3ac911 ./1/UQCN.mbn
ff935ec4da6f6711b48caaddcf737566 ./2/UQCN.mbn
4f74d79ed8df027db3b75e36feb2bd27 ./3/amss.mbn
d9ff7b27c491332650b1efbbee64ee31 ./3/apps.mbn
6f6462fe0cc185cc3dc24720a28770fb ./3/UQCN.mbn
46418504e70971bda7b2ee34cc80b5b7 ./4/UQCN.mbn
1aa5727b034dd1f371a3412d5800c1a3 ./6/UQCN.mbn
9f6773625d59098f9360c24263d99615 ./7/UQCN.mbn
e012286117c0c7708369f8dbc7906e64 ./8/UQCN.mbn
c65246da47695b4ecaaf098a02718c9d ./9/UQCN.mbn
84d002b0ef003cde6c95826bfbf067fe ./UMTS/amss.mbn
d7496085f1af3d1bfdf0fa60c3222766 ./UMTS/apps.mbn

For me this tutorial above worked, too. Is there anything which prevents us from copying it to the page itself? --[[User:Aneiser|Aneiser]] 20:58, 21 August 2010 (UTC)

== 2.6.32, 2.6.34, git snapshots and later ==

so it's working with recent kernels or no? And add any info about GPS, please. [[User:Tensai.cirno|Tensai.cirno]] 02:26, 16 June 2010 (UTC)

I had no luck with 2.6.34. however i tested 2.6.35-rc3 + gobi_loader 0.6 and it worked. had to load the firmware by hand though ...
"/lib/udev/gobi_loader -2000 /dev/ttyUSB0 /lib/firmware/gobi" but i guess the id in the udev file is not the right one for my card. --[[User:Max p|Max p]] 02:09, 22 June 2010 (UTC)

Thanks a lot, this is ''very good'' news. [[User:Tensai.cirno|Tensai.cirno]] 06:54, 23 June 2010 (UTC)

Yes, with 2.6.35 and gobi_loader 0.7 it works for me (T510, O2 Germany, Generic firmware) --[[User:Aneiser|Aneiser]] 21:00, 21 August 2010 (UTC)

The modem also works with 2.6.36 (2.6.36-1~experimental.1) and gobi-loader 0.6.1 from current Debian Testing/Sid/Experimental. GPS doesn’t, although I did apply the patch; /dev/ttyUSB2 doesn't output anything at all – maybe testing outside is necessary. [[User:X2017|X2017]] 20:44, 14 November 2010 (UTC)

== GPS ==

Has anyone managed to get GPS to work yet? I think one has to send certain AT commands to receive the NMEA information (at least that is how it works with some Ericsson modems).
Unfortunately I can't find an AT command reference for the Qualcomm Gobi 2000 ...
[[User:Flyser|Flyser]] 14:15, 27 July 2010 (UTC)

i was asking the qualcomm support about that subject, handing out all AT commands. lets say it that way they were not very cooperative. but you could ask them as well, maybe you got more effective than me and we can have the commands :)--[[User:Max p|Max p]] 09:10, 4 August 2010 (UTC)

so did I. I was told to contact Lenovo about the issue -.- --[[User:Flyser|Flyser]] 08:10, 9 August 2010 (UTC)

You can find the documentation and sdk [http://gobianywhere.com/sdk/index.php here]. However I didn't find any useful AT commands, and I think the SDK is win only. [[User:bbandi|bbandi]] 22:32, 14 August 2010 (UTC)

Did you try to install the SDK? Is it possible to analyze how GPS works? --[[User:Aneiser|Aneiser]] 22:00, 21 August 2010 (UTC)

Has anyone managed to get GPS to work with the information published on this wiki page? I get all three devices (ttyUSB[012]), but ttyUSB2 does not output anything. Do I have to connect to a wireless network to get this to work? Could someone publish a more detailed guide how to _use_ the gps? I tried:
# cat /dev/ttyUSB2 &
# echo -n "\$GPS_START" > /dev/ttyUSB2
--[[User:Flyser|Flyser]] 11:03, 30 September 2010 (UTC)

I also cannot get the GPS to work even with the new instructions. Googling around, I found that the start string could be "$GPS-START" (Hyphen instead of underline). However, this doesn't work either. The GPS *did* work on the preinstalled Windows 7. I'm using basic UMTS firmware (firmware from folders "UMTS" and "6").
--[[User:Zarhan|Zarhan]] 06:40, 1 October 2010 (UTC)

I was able to get it to work on a X201, after using the 6/UQCN.mbn image from my Windows 7 x64 partition. This seems to be different from the files/checksums above:
root@polaris:~# md5sum /lib/firmware/gobi/*.mbn
84d002b0ef003cde6c95826bfbf067fe /lib/firmware/gobi/amss.mbn
d7496085f1af3d1bfdf0fa60c3222766 /lib/firmware/gobi/apps.mbn
68e46b936d5400862a0381b101af3972 /lib/firmware/gobi/UQCN.mbn

Now to seems to work:
root@polaris:~# cat /dev/ttyUSB2 &
[1] 3320
root@polaris:~# echo "\$GPS_START" > /dev/ttyUSB2; sleep 3; echo "\$GPS_STOP" > /dev/ttyUSB2
$GPGSA,A,1,,,,,,,,,,,,,,,*1E
$GPGSV,4,1,16,14,33,050,35,24,42,115,28,20,55,246,26,19,19,172,25*77
$GPGSV,4,2,16,11,75,237,,17,29,309,,23,07,192,,28,10,267,*7F
$GPGSV,4,3,16,31,08,106,,32,80,227,,30,,,,29,,,*72
$GPGSV,4,4,16,27,,,,26,,,,25,,,,22,,,*78
$GPGGA,192126.0,,,,,0,,,,,,,,*77
$PQXFI,192126.0,,,,,,,,*6B
$GPVTG,,T,,M,,N,,K,N*2C
$GPRMC,,V,,,,,,,,,,N*53
$GPGSA,A,1,,,,,,,,,,,,,,,*1E
$GPGGA,192127.0,52xx.xxxxxx,N,0xxxx.xxxxxx,E,1,05,1.8,30.6,M,46.0,M,,*61
$PQXFI,192127.0,52xx.xxxxxx,N,0xxxx.xxxxxx,E,30.6,80.58,93.58,3.17*5B
$GPVTG,nan,T,nan,M,0.0,N,0.0,K,A*23
root@polaris:~#

On Debian, using '/lib/udev/gpsd.hotplug add /dev/ttyUSB2' you can tell gpsd about the serial device.
--[[User:Shoragan|Shoragan]] 20:07, 11 October 2010 (UTC)

I'm using exactly same firmwares as Shoragan, and I can see the ttyUSB2 device - however, no NMEA data starts to appear after issuing $GPS_START. I'm using W510 --[[User:Zarhan|Zarhan]] 06:03, 13 October 2010 (UTC)

Same here: using {{openSUSE}} 11.3 with kernel of the day (2.6.37-rc3-3, includes the qcserial patches), gobi_loader 0.7 and current fw files from win partition:
* Gps works in win 7/64 ({{T510i}}) with drivers updated yesterday (most fw files have different md5 sums from those above)
* Copied fw from 1/ to /lib/firmware/gobi/ (also tried the others, but these are the ones working in windows)
* Usb device id changes from x9204 to x9205 automatically (fw gets loaded)
* 3 tty devices appear automatically (udev and module config is ok)
* Modem at ttyUSB1 is functional (at i command in minicom gives fw version and imei)
* ttyUSB0 and ttyUSB2 seem to be dead though (cat, minicom)
--[[User:Joban|Joban]] 19:08, 13 December 2010 (UTC)
*** In windows GPS & wifi work simultaneously? Maybe you should switch off wifi & try GPS? I read official "Lenovo Russia" blog - in the earlier versions BIOS in X100e you can use only wifi '''or''' 3G --[[User:Evadim|Evadim]] 21:10, 13 December 2010 (UTC)

Evadim, I assume with wifi you mean UMTS/GSM, not WLAN (agn) I don't know. I don't use UMTS/GSM (for now). How would I explicitly deactivate 3G/wifi/UMTS/GSM in linux?
Btw. I narrowed down used fw a bit: The firmwares in the "1" directory sometimes hangs the boot process for me and fw dosn't load. I use UMTS/ and 6/
files now --[[User:Joban|Joban]] 16:26, 16 December 2010 (UTC)

I tried with newer firmware that comes with the latest WWan driver (driver version 2.0.7.3) at http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-72938&medium=rssW510#20101028 - still doesn't work. --[[User:Zarhan|Zarhan]] 15:25, 29 November 2010 (UTC)

Got it! Wooohooo! I think it work after last BIOS upgrade (lenovo s10-3t), I install win7 for testing GOBI module, upgrade BIOS, test GPS & 3G. After I reboot in to linux - GPS start working. --[[User:Evadim|Evadim]] 17:01, 5 December 2010 (UTC)

Guys! 4 hours of sex with USB protocol debugging in Qemu and "$GPS_START/GPS_STOP" is working now! :)
No firmwares, no bios upgrades, forget about it.
All is simple, in default Lenovo GPS application(GPS tracker) all NMEA data goes through broadband ethernet vitrual interface and enabled by some proprietary protocol. Windows NMEA port is uneuseful before you click button "Start" in GPS tracker(driver adds GPS_START string to any connection started on qualcomm nmea port). But if we go to the Preferences of this GPS tracker, and enable checkbox "Auto tracking", Gobi 2000 start to automaticlly enable GPS when new connection appears on NMEA port and it see string "$GPS_START".

So, u only need to install Windows on your machine(or install it on virtual machine), install GPS tracker from Lenovo and simple enable "Auto tracking" checkbox in GPS tracker preferences. After that, u can enjoy GPS in any OS on your notebook. --[[User:Invented|Invented]] 21:50, 25 December 2010 (UTC)