ThinkWiki - User contributions [en]

AES NI

2011-11-17T15:33:49Z

Dveeden:

== Usage ==
To use AES NI you need to load the aesni_intel kernel module.
$ /sbin/modinfo aesni_intel
filename: /lib/modules/3.0.0-13-generic/kernel/arch/x86/crypto/aesni-intel.ko
alias: aes
license: GPL
description: Rijndael (AES) Cipher Algorithm, Intel AES-NI instructions optimized
srcversion: 61A51F44F192D7CE0FBA795
depends: cryptd,aes-x86_64
vermagic: 3.0.0-13-generic SMP mod_unload modversions

To see if your CPU supports AES NI check the output of "cat /proc/cpuinfo | grep aes"
$ cat /proc/cpuinfo | grep aes | wc -l
4

To check whether or not AES NI is enabled check the contents of /proc/crypto
$ grep module /proc/crypto | sort -u
module : aesni_intel
module : aes_x86_64
module : arc4
module : kernel

To see if OpenSSL supports AES-NI run openssl engine
$ openssl engine
(aesni) Intel AES-NI engine
(dynamic) Dynamic engine loading support

== Read More ==
* [http://www.phoronix.com/scan.php?page=article&item=intel_aesni_dmcrypt Benchmarking eCryptfs and dm-crypt performed by Phoronix]

AES NI

2011-11-17T15:30:43Z

Dveeden: â†Created page with '== Usage == To use AES NI you need to load the aesni_intel kernel module. $ /sbin/modinfo aesni_intel filename: /lib/modules/3.0.0-13-generic/kernel/arch/x86/crypt...'

Intel Core i5

2011-11-17T15:22:41Z

Dveeden: /* Features */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|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;">

The Intel Core i5 (Arrandale) is the successor of the [[Intel Core 2 Duo (Penryn)]] processor. Unlike the Penryn, Arrandale uses the new 32um process which makes it cooler and uses less power.

=Features=
*Dual Core
*EM64T
*[http://en.wikipedia.org/wiki/Vanderpool#Intel_Virtualization_Technology_.28Intel_VT.29 Intel Virtualization Technology ]
*XD-Bit
*[[SIMD|MMX]], [[SIMD|SSE]], [[SIMD|SSE2]], [[SIMD|SSE3]], [[SIMD|SSSE3]], [[SIMD|SSE4.1]], XD Bit, iAMT2, Intel VT instruction sets
*1066 MHz Memory controller integrated
*32 nm fabrication process
*3 MB L2-Cache
*[[SpeedStep|Enhanced Intel SpeedStep (EIST)]]
*Integrated [[Intel HD Graphics]]
* [[AES NI]]
</div>
|}

=Available Types and ThinkPads featuring them=
==Standard Voltage==
{| border=1 cellspacing=0 cellpadding=2
|- style="background:#ffdead;white-space:nowrap;"
! Nr. || colspan=5 | Frequency (MHz) || L2 Cache || VT || colspan=2 | core Voltage (V) || colspan=2 | TDP (W) || ThinkPad Models
|- style="background:#ffdead;"
! !! max. !! min. !!turbo !! GPU !! Memory!! !! !! high !! low !! high freq !! low freq !!
|-
| i5-430M || 2267 || ? || 2533 || 766 || 1066 || 3MB || yes || ? || ? || 35 || ? || {{T410i}}, {{T510i}}, {{X201i}}
|-
| i5-520M || 2400 || 1200 || 2930 || 766 || 1066 || 3MB || yes || ? || ? || 35 || ? || {{L412}}, {{L512}}, {{T410}}, {{T410s}}, {{T510}}, {{X201}}, {{X201i}}
|-
| i5-520E || 2400 || ? || 2930 || 766 || 1066 || 3MB || yes || ? || ? || 35 || ? ||
|-
| i5-540M || 2533 || ? || 3066 || 766 || 1066 || 3MB || yes || ? || ? || 35 || ? || {{L412}}, {{T410}}, {{T510}}, {{X201}}, {{X201i}}
|-
|}

==Ultra-Low Voltage==
{| border=1 cellspacing=0 cellpadding=2
|- style="background:#ffdead;white-space:nowrap;"
! Nr. || colspan=5 | Frequency (MHz) || L2 Cache || VT || colspan=2 | core Voltage (V) || colspan=2 | TDP (W) || ThinkPad Models
|- style="background:#ffdead;"
! !! max. !! min. !!turbo !! GPU !! Memory!! !! !! high !! low !! high freq !! low freq !!
|-
| i5-520UM || 1067 || ? || 1860 || 500 || 1066 || 3MB || yes || ? || ? || 18 || ? ||
|-
|}

=See also=
*[[Intel Core 2 Duo (Penryn)]]
*[[Intel Core i3]]
*[[Intel Core i7]]

== External Links ==
*[http://en.wikipedia.org/wiki/List_of_Intel_Core_i5_microprocessors#Dual-Core_Mobile_processors Wikipedia - Intel Core i5 mobile microprocessors]

[[Category:Components]]

Talk:Integrated camera

2011-11-17T15:20:27Z

Dveeden:

According to coloer preferences in GNOME3 on Ubuntu 11.10 the webcam in my T410s is a Chicony Electronics webcam.
[[User:Dveeden|Dveeden]]

Talk:Integrated camera

2011-11-17T15:20:13Z

Dveeden:

According to coloer preferences in GNOME3 on Ubuntu 11.10 the webcam in my T410s is a Chicony Electronics webcam.

Talk:Integrated camera

2011-11-17T15:19:58Z

Dveeden: â†Created page with 'According to coloer preferences in GNOME3 on Ubuntu 11.10 the webcam is a Chicony Electronics webcam.'

According to coloer preferences in GNOME3 on Ubuntu 11.10 the webcam is a Chicony Electronics webcam.

Integrated camera

2011-11-17T15:17:43Z

Dveeden:

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;" | [[Image:integrated_camera.jpg|Integrated Camera]] __NOTOC__
|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;">
=== The Integrated camera ===
Almost all recent ThinkPads have an integrated camera above the display. This camera (typically called a webcam) is USB attached. On some earlier ThinkPads a proprietary camera was used, but later models use a standard UVC camera which is supported by the [http://linux-uvc.berlios.de/ uvcvideo driver].
</div>
|}

== ThinkPads which may have a proprietary camera ==
These ThinkPads have a 0.3MP fixed focus Sonix SN9C201 camera which is supported by the '''gspca_sn9c20x''' driver.

* {{Z61t}}, {{Z61m}}

== ThinkPads which may have a UVC camera ==
'''0.3MP fixed focus'''
* {{Edge 11"}}, {{Edge 13"}}
* {{X100e}}, {{X120e}}

'''1.3MP fixed focus'''
* {{R61}}, {{R61i}}, {{R400}}, {{R500}}
* {{SL300}}
* {{T61}}, {{T400}}, {{T500}}
* {{W500}}, {{W700}}, {{W700ds}}
* {{X200}}, {{X200s}}, {{X200 Tablet}}, {{X300}}, {{X301}}

'''2.0MP fixed focus'''

USB ID: 17ef:480d (Lenovo Integrated Webcam [R5U877])
* {{Edge 14"}}, {{Edge 15"}}
* {{L412}}, {{L512}}
* {{SL400}}, {{SL410}}, {{SL500}}, {{SL510}}
* {{T400s}}, {{T410}}, {{T410i}}, {{T410s}}, {{T410si}}, {{T510}}, {{T510i}}
* {{W510}}, {{W701}}, {{W701ds}}
* {{X201}}, {{X201 Tablet}}

[[Category:Components]]

== Known Bugs ==
* Cheese in Ubuntu 11.10 [https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/888633 lp:888633]

Problem with CPU frequency scaling

2011-06-17T09:50:11Z

Dveeden: /* Affected Models */

{{stub}}

{{WARN|CPU frequency limitation is a safety feature of your ThinkPad, do not work around it! If you have set the BIOS to performance mode and it is still limiting maximum CPU frequency, there is almost always a damn good reason for that}}

==Symptom==
If the battery pack is removed and the laptop is powered by a 65W AC adapter only, the CPU downclocks to the lowest multiplier and remains locked in low speed. This happens irrespective of the scaling method in use (kernelspace or userspace) and of the frequency governor selected (ondemand, performance, etc.).

Output of cpufreq-info (on AC power without battery):

analyzing CPU 0:
driver: centrino
CPUs which need to switch frequency at the same time: 0 1
hardware limits: 1000 MHz - 1.83 GHz
available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: ondemand, userspace, powersave, performance
'''current policy: frequency should be within 1000 MHz and 1000 MHz.'''
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz (asserted by call to hardware).

analyzing CPU 1:
driver: centrino
CPUs which need to switch frequency at the same time: 0 1
hardware limits: 1000 MHz - 1.83 GHz
available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: ondemand, userspace, powersave, performance
'''current policy: frequency should be within 1000 MHz and 1000 MHz.'''
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz (asserted by call to hardware).

Output of cpufreq-info (on AC power with battery plugged in):

analyzing CPU 0:
driver: centrino
CPUs which need to switch frequency at the same time: 0 1
hardware limits: 1000 MHz - 1.83 GHz
available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: ondemand, userspace, powersave, performance
'''current policy: frequency should be within 1000 MHz and 1.83 GHz.'''
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz (asserted by call to hardware).

analyzing CPU 1:
driver: centrino
CPUs which need to switch frequency at the same time: 0 1
hardware limits: 1000 MHz - 1.83 GHz
available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: ondemand, userspace, powersave, performance
'''current policy: frequency should be within 1000 MHz and 1.83 GHz.'''
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz (asserted by call to hardware).

==Explanation==

The 65W AC adaptor does not supply enough power to handle peak power draws from the CPU/disk/GPU on the later ThinkPads. The battery is required to supply the peak demand and ensure correct system operation.

Messing with this can cause data loss, data corruption, and hardware damage.

==Solution==

Make sure no BIOS setting is limiting the CPU frequency range (like "thermal management" = "BALANCED").

# Buy a 90W AC adapter
# Don't use the laptop without the battery pack

Other solution than using the laptop with the battery pack always inserted is to add "processor.ignore_ppc=1" to kernel boot command line. This allows to disable BIOS frequency limit, but can be mischievous to the computer if it's power consumption is higher than 65W.

== Affected Models ==

* {{Z61m}}
* {{T43p}}
* {{T61}}
* {{T60p}}
* {{X201}}
* {{T410}}
* {{T410s}}

Probably ALL Lenovo ThinkPads. One can actually track this through the DSDT, but it is not worth the effort.

Mute button

2011-05-23T10:08:33Z

Dveeden:

Starting from Linux version 2.6.23, kernel passes OSI string "<tt>!Linux</tt>" to ACPI (instead of "<tt>Linux</tt>"). There is a number of reasons for that (see details in <tt>drivers/acpi/osl.c</tt> in the kernel source). But IBM/Lenovo has a consistently good record of supporting Linux, so this trick is not necessary for Thinkpads. Moreover, OSI string "<tt>Linux</tt>" is [http://linux.derkeiler.com/Mailing-Lists/Kernel/2008-01/msg04543.html needed] to make the '''Mute''' button work. For Thinkpads R61, T61 and X61, there are already hooks for that in <tt>drivers/acpi/blacklist.c</tt>. For most other models, you need to pass the string <tt>acpi_osi="Linux"</tt> to the kernel as a boot parameter.

==Needed for models==
{{T400}}, {{X200}}, {{X301}}

==Microphone Mute Button==
The Microphone Mute Button on the T410 and T410s does not work on Ubuntu 10.10 and Ubuntu 11.04.

https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/728310

==Needed for models==
{{T410}}, {{T410s}}

Mute button

2011-05-23T10:07:45Z

Dveeden:

Qualcomm Gobi 2000

2011-05-20T09:25:39Z

Dveeden: /* 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 <br />
apps.mbn <br />
UQCN.mbn
|
06f76ed398458dad7b91c2d99a85a0a7 <br />
88a60ed745d75fb1b92c539574ecc972 <br />
2dccbd125ddd2cb327309ba75c6054d2
|
D1055-STUTDSVD-3580 <br />
D1055-STUTDSVD-3580 <br />
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 <br />
apps.mbn <br />
UQCN.mbn
|
d25f247cbe0fa481378d9f92c65c3e5e <br />
46fcb2423c31fd96e4645a90956264d2 <br />
0ac877ed109f3c28d844b08f55c56185
|
D1055-STUTCSFD-3710 <br />
D1055-STUTCSFD-3710 <br />
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 <br />
apps.mbn <br />
UQCN.mbn
|
00c612a8a827dbef746f514e939fa77d <br />
7d12b38ec6851bef5039b74bffffd423 <br />
735db64a57802e252ca4ff05d06b2f10
|
D1025-STUTABOD-3601 <br />
D1025-STUTABOD-3601 <br />
D1025-STUTABOD-3601
| 02-umts_orange-02816-012
|-
| 12 || DoCoMo
|
amss.mbn <br />
apps.mbn <br />
UQCN.mbn
|
4d6203bf9fe8ae1af439d4d163e91596 <br />
385a22740f80c0d00f8acdd9ad637032 <br />
e868df00bfa88596d588a52f872ff703
|
D1025-STUTABED-3587 <br />
D1025-STUTABED-3587 <br />
D1025-UQCNABED-2009
| 02-umts_doco-03328-009
|-
| UMTS || Default Firmware
|
amss.mbn <br />
apps.mbn
|
80fcfbb41a7d4331d4b7145972f5f3c4 <br />
00cbd411048cdadc3e4caf0d89d14fca
|
D1025-STUTABGD-3600 <br />
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? <br /> O2 Germany
|-
| 7 || Telefónica ||
|-
| 8 || Telecom Italia ||
|-
| 9 || Orange ||
|-
| 12 || DoCoMo ||
|-
| UMTS || Default Firmware || UMTS unlocked, O2 UK? <br /> O2 Germany <br /> 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.com 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}}

Qualcomm Gobi 2000

2011-05-20T08:47:23Z

Dveeden: /* 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 <br />
apps.mbn <br />
UQCN.mbn
|
06f76ed398458dad7b91c2d99a85a0a7 <br />
88a60ed745d75fb1b92c539574ecc972 <br />
2dccbd125ddd2cb327309ba75c6054d2
|
D1055-STUTDSVD-3580 <br />
D1055-STUTDSVD-3580 <br />
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 <br />
apps.mbn <br />
UQCN.mbn
|
d25f247cbe0fa481378d9f92c65c3e5e <br />
46fcb2423c31fd96e4645a90956264d2 <br />
0ac877ed109f3c28d844b08f55c56185
|
D1055-STUTCSFD-3710 <br />
D1055-STUTCSFD-3710 <br />
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 <br />
apps.mbn <br />
UQCN.mbn
|
00c612a8a827dbef746f514e939fa77d <br />
7d12b38ec6851bef5039b74bffffd423 <br />
735db64a57802e252ca4ff05d06b2f10
|
D1025-STUTABOD-3601 <br />
D1025-STUTABOD-3601 <br />
D1025-STUTABOD-3601
| 02-umts_orange-02816-012
|-
| 12 || DoCoMo
|
amss.mbn <br />
apps.mbn <br />
UQCN.mbn
|
4d6203bf9fe8ae1af439d4d163e91596 <br />
385a22740f80c0d00f8acdd9ad637032 <br />
e868df00bfa88596d588a52f872ff703
|
D1025-STUTABED-3587 <br />
D1025-STUTABED-3587 <br />
D1025-UQCNABED-2009
| 02-umts_doco-03328-009
|-
| UMTS || Default Firmware
|
amss.mbn <br />
apps.mbn
|
80fcfbb41a7d4331d4b7145972f5f3c4 <br />
00cbd411048cdadc3e4caf0d89d14fca
|
D1025-STUTABGD-3600 <br />
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? <br /> O2 Germany
|-
| 7 || Telefónica ||
|-
| 8 || Telecom Italia ||
|-
| 9 || Orange ||
|-
| 12 || DoCoMo ||
|-
| UMTS || Default Firmware || UMTS unlocked, O2 UK? <br /> O2 Germany <br /> 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.com TangoGPS] or any other GPS tool which uses gpsd.

== 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:How to get special keys to work

2011-03-03T09:39:59Z

Dveeden:

__TOC__

The xmodmap step doesn't seem to work when using the "kdb" driver of xorg. Here are the changes I needed to make to my setup to get the "back" and "forward" keys to work (in diff -u format);

--- xkb/symbols/inet.oud 2004-12-01 08:36:04.000000000 +0100
+++ xkb/symbols/inet 2005-03-08 19:59:32.587636120 +0100
@@ -1875,6 +1875,16 @@
key <I76> { [ XF86AudioLowerVolume ] };
};

+// IBM ThinkPad 41 Internet Keys
+
+partial alphanumeric_keys
+xkb_symbols "tp41" {
+ name[Group1]= "IBM ThinkPad 41 Internet Keys";
+
+ key <I69> { [ F22 ] };
+ key <I6A> { [ F21 ] };
+};
+
// Trust

partial alphanumeric_keys<br>

--- xkb/rules/xorg.lst.oud 2004-12-01 08:36:05.000000000 +0100
+++ xkb/rules/xorg.lst 2005-03-07 20:55:21.000000000 +0100
@@ -97,6 +97,7 @@
sven SVEN Ergonomic 2500
symplon Symplon PaceBook (tablet PC)
toshiba_s3000 Toshiba Satellite S3000
+ tp41 IBM ThinkPad 41 Internet Keys
trust Trust Wireless Keyboard Classic
trustda Trust Direct Access Keyboard
yahoo Yahoo! Internet Keyboard

--- xkb/rules/xorg.oud 2004-12-01 08:36:05.000000000 +0100
+++ xkb/rules/xorg 2005-03-07 20:45:59.000000000 +0100
@@ -120,7 +120,7 @@
qtronix \
samsung4500 samsung4510 \
sk1300 sk2500 sk6200 sk7100 \
- sven symplon toshiba_s3000 trust trustda yahoo
+ sven symplon toshiba_s3000 tp41 trust trustda yahoo

! model = symbols
$inetkbds = +inet(%m)

--- xkb/rules/xorg.xml.oud 2004-12-01 08:36:05.000000000 +0100
+++ xkb/rules/xorg.xml 2005-03-07 20:52:35.000000000 +0100
@@ -975,6 +975,13 @@
</model>
<model>
<configItem>
+ <name>tp41</name>
+ <description>IBM Thinkpad 41 Internet Keys</description>
+ <description xml:lang="nl">IBM ThinkPad 41 internet toetsen</description>
+ </configItem>
+ </model>
+ <model>
+ <configItem>
<name>trust</name>
<description>Trust Wireless Keyboard Classic</description>
<description xml:lang="fr">clavier classique Trust Wireless</description>

Do not forget to add something like "+inet(tp41)" to /etc/X11/xorg.conf:
(...)
Option "XkbLayout" "us_intl+inet(tp41)"
(...)

----
I've filled a [https://bugs.freedesktop.org/show_bug.cgi?id=9779 bug] to freedesktop bugzilla, which has been applied. It adds inet(thinkpad) symbols with <I69>/<I6A> keys and adds thinkpad to $inetkbds list. So, Forward/Back keys will work out-of-box with thinkpad XkbModel. However, thinkpadintl model is not supported... --[[User:Raorn|Raorn]] 13:25, 27 January 2007 (CET)

== Not T41 specific ==

These keys are hardly T41 specific, they can also be found on the T30, T40, T42 and I'm sure several other ThinkPads in the X, R and G lineup.

Actually, the above patches could be completed with the information of the other special keys found on some Thinkpads (which is listed in [[How_to_get_special_keys_to_work#xmodmap_configuration]]) and submitted as a request for enhancement with [http://bugs.freedesktop.org xorg's bugzilla]. However, firefox doesn't yet recognize keysyms like XF86Back, XF86Forward, so then firefox still needs to be patched manually (unless an enhancement is requested for firefox too).

=== XF86Back in Firefox ===
I found that XF86Back and XF86Forward work for me with firefox. I was able to use the following in
/usr/lib/firefox/chrome/browser/content/browser/browser.xul
<key id="goBackKb" keycode="XF86Back" command="Browser:Back" />
<key id="goForwardKb" keycode="XF86Forward" command="Browser:Forward" />

My firefox version is Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.3) Gecko/20061201 Firefox/2.0.0.3 (Ubuntu-feisty)

----

This also works for me, but "XF86Back" seems to be *the same* (toggles the same command, but only in FireFox) as [Alt Gr]-Key on German keyboards, even if xev shows nothing like this. Bug in FireFox? Therefor I have stick to the F19/F20 workaround.

--[[User:BDKMPSS|BDKMPSS]] June 04 2007
----

Yes, this hint should be dropped. This was bug in firefox, fixed long time ago:
https://bugzilla.mozilla.org/show_bug.cgi?id=66519

It is fixed in firefox above 3.5 (and nobody should use older versions, really).
----

== Fake ACPI events? ==

Not all keys generate ACPI events. Maybe it is feasible to have the ibm-acpi module check the CMOS (instead of having tpb checking /dev/nvram) and generate fake ACPI events for those keys. Even if it is feasible, that is probably way to hacky for a kernel module ... Still, it would be nice to only have to use scripts triggered by ACPI events and not both scripts for ACPI events and scripts for tpb.

----
I think something like this is possible with ibm-acpi 0.10 already. It provides a proc file from which you can derive a table of CMOS states. You'd only have to figure the who is who of CMOS bits and write a daemon (or daemon like shell script) checking them regularly. This should be about what you suggest since tpb does the same thing with the bios ram. Of course generating ACPI events can not be done like that (or can it?), but you could trigger the ACPI action scripts directly then.

[[User:Wyrfel|Wyrfel]] 01:02, 14 Mar 2005 (CET)
----

It may be possible (I have a 770x, so don't have the special keys) to add the keys as real ACPI events, by altering the DSDT. I've done this to enable ACPI events for Fn-(every labelled F key),Home,End,PgUp,PgDn on mine, and they aren't labelled with anything physically (no thinklight and physical brightness control). The Embedded Controller reports all events, including keys, by calling one of the _Qxx functions (you'll find a whole pile in the sourcecode for the DSDT). If you then insert a fucntion in the same scope as the others like:-
Method (_Q12, 0, NotSerialized) { \_SB.HKEY.MHKQ (0x1003) } //Fn-F3
when executed, ibm-acpi will then report an acpi event numbered 0x0001003. You should find some functions, e.g. _Q1B For Fn-F12 identical to this.

I found some IBM DSDT's had functions that made MKHQ calls for EC functions _Q63, _Q64, _Q4E, _Q4F, but did nothing on mine---maybe these are a good starting point. Add a whole pile, and see if you get lucky! (At your own risk, of course... :/ But it should be pretty safe).

Yes, the above sounds pretty identical to tpb, except with /proc/ibm/ecdump instead of /dev/nvram. The above works very nicely, however there's luck involved in finding the right number, even if it exists!

[[User:lentinj|lentinj]]

----

Fn+F6 does not seem to generate an event on t41p even if the mask is set to 0xffff and experimental=1 is passed to ibm_acpi
[[User:tf|tf]]

----

==Bind Fn to super or hyper ==

Hello

Is it possible to bind Fn via Xmodmap to a key modifier such as hyper or super? Thanks
[[User:Oub|Oub]] 13:14, 6 February 2006 (CET):
----
I doubt it. The event for the {{key|Fn}} key is generated at release (as opposed to holding it where it serves it's usual special function). Hence you can't use it as a modifier. [[User:Wyrfel|Wyrfel]] 22:52, 6 February 2006 (CET)
----
I have added a paragraph how to get around the issue that {{key|Fn}} is not working with other key combos than the ones intended. Mebbe that helps you.
--[[User:Low|Low]] 12:09, 11 December 2008 (CET)
----

==Bind Fn 12 say to F34 ==
Thanks Wyrfel for your reply, in order to display my question better, I use a new header: can I bind all the Fn Fx to hay F34 and the like?
[[User:Oub|Oub]] 21:33, 10 February 2006 (CET):
----
You can do this with all key '''combinations''' that support xmodmap (see the table). That means you can't do it with {{key|Fn}}}{{key|F12}}, because that combination doesn't generate a key event at all (it only generates an APM/ACPI event. Hence there is nothing vor xmodmap to remap.

But what is your wider focus goal? I'm sure that what you want to do can be realized, anyway: You can write an ACPI script and event file for {{key|Fn}}{{key|F12}} and have the script start some tool that sends a F34 key to the X server. I'm sure this is possible.

[[User:Wyrfel|Wyrfel]] 00:03, 11 February 2006 (CET)
----
Hi,

{{key|Fn}} does not accept other key combos than the acpi ones (e.g. {{key|Fn}}+{{key|F4}}). However you can assign it to be CapsLock, and use the {{key|CapsLock}} then for the purpose of having key combos. See the paragraph about enabling fast NumPadding:

[[How to get special keys to work#NumPad (KeyPad) keys access by a key combination]]

--[[User:Low|Low]] 12:18, 11 December 2008 (CET)
----

==Can't bind Fn 12 ==

Hello

I am using a R51 and I have compiled ibm-acpi monolithic in the kernel (not as module, maybe this is a mistake?). Anyway, I am using
suspend2, which I compiled in the kernel as well. Now I have bound
''to hibernate '' first to Fn 4, with the following script
event=button[ /]sleep
action=/usr/local/sbin/mihibernate

This works fine. Now I want to do the same for Fn12, so following the key table I did:

event=button[/] ibm/hotkey HKEY 00000080 0000100c
action=/usr/local/sbin/mihibernate

But that does not work. What is the problem? I tried even
echo enable,0xffff >/proc/acpi/ibm/hotkey
without success. Can anybody help me?
[[User:Oub|Oub]] 16:27, 4 March 2006 (CET):
----
The proper event line is
event=ibm/hotkey HKEY 00000080 0000100c
.

Also, make sure that you are not using [thinkpad-acpi]. If <tt>event=button[ /]sleep</tt> works for {{key|Fn}}{{key|F4}}, that indicates that you do. It might block the ibm-acpi driver. Check your kernel config and disable any thinkpad acpi driver except ibm-acpi.

[[User:Wyrfel|Wyrfel]] 21:58, 4 March 2006 (CET)
----

:Hello
:
:It is odd, I am pretty sure, that I do not use [thinkpad-acpi], but [ibm-acpi], although event=button[ /]sleep works for FnF4, in any case I found out that
:
: event=(button/power|ibm/hotkey HKEY 00000080 0000100c)
:
:Works! What do you think of adding a subsection to the [[How to get special keys to work]] page, with some examples, like the following:
:
:from ''/etc/acpi/events/battery'':
event=(button/power|ibm/hotkey HKEY 00000080 0000100c)
action=/usr/local/sbin/hibernate
:from ''/etc/acpi/events/lid''
event=button/lid
action=/usr/local/bin/mysleepram
:from ''/etc/acpi/events/sleepbtn''
event=(button/sleep|ibm/hotkey HKEY 00000080 00001004)
action=/usr/local/bin/mysleepram
:
:(Also ''event=button/sleep '' works for me)
:and then restart acpi:
:
/etc/init.d/acpid restart
:
:[[User:Oub|Oub]] 13:22, 5 March 2006 (CET):
----
What you do with
event=(button/power|ibm/hotkey HKEY 00000080 0000100c)
is to make a logical nonexclusive OR between
event=button/power
and
event=ibm/hotkey HKEY 00000080 0000100c
. If the first works, the whole thing works. So that's pretty logical.

Please, do a {{cmdroot|dmesg <nowiki>|</nowiki> grep thinkpad-acpi}} and do a {{cmdroot|dmesg <nowiki>|</nowiki> grep ibm-acpi}}. What is the output in either case?

I see no sense in putting examples to the page that only confuse people because they are not correct. ibm-acpi generates the events listed in the table and nothing else. If you get something like <tt>button/sleep</tt> it's not ibm-acpi generating it. You are running Debian, right? Let's hope they didn't patch the driver to generate different events.

Also, you can always do {{cmdroot|tail -f /var/log/acpid}} to have a life view of the generated events.

I am pretty sure that you are using thinkpad-acpi or - if not so - that something else must interfere.

[[User:Wyrfel|Wyrfel]] 04:49, 6 March 2006 (CET)

----

:Hi
:
:Ok I admit everything is very odd. For the start, I seem to use
:ibm-acpi. As I said I am Debian, but I compiled my own kernel :(2.6.10)(but not as a module, maybe this was a bad idee??) and I used :the ibm-acpi driver which comes shipped with that kernel. I did not :download the driver from the official http://ibm-acpi.sourceforge.net/ :site. Here is the output of
:
:dmesg | grep acpi
Kernel command line: ro root=/dev/hda6 acpi_sleep=s3_bios
tbxface-0118 [02] acpi_load_tables : ACPI Tables successfully acquired
evxfevnt-0094 [03] acpi_enable : Transition to ACPI mode successful
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [df6ddaa8]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c1464768]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c1467328]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c146bba8]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c146b628]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c146b3e8]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c146b268]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c146dde8]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c1470d68]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c1470568]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c14719a8]
ibm_acpi: IBM ThinkPad ACPI Extras v0.8
ibm_acpi: http://ibm-acpi.sf.net/
acpi_bus-0081 [08] acpi_bus_get_device : Error getting context for object [c1467328]
ibm_acpi: dock device not present

:I don't understand the errors but anyway. Now the odd thing is that indeed the following works
:
event=button[ /]sleep
action=/usr/local/sbin/hibernate
:but
event=button[/]sleep
action=/usr/local/sbin/hibernate

:Does not work. But from what you said, using the ibm_acpi neither of '''these strings ''' should work? So I don't understand what is going on. [[User:Oub|Oub]] 20:28, 6 March 2006 (CET):

----

With any reasonably new kernel (2.6.16 in Thinkpad terms :-) ) and a good DSDT (say, like the one that comes inside the T43), you can get two classes of events: ACPI events (as in native ACPI events), and ibm-acpi hotkey events.

This has nothing to do with thinkpad-acpi.

Look under /proc/acpi/buttons. If you have sleep and maybe hibernate/suspend in there (I don't know how fn+f12 is called when properly supported through ACPI DSDT, the T43 doesn't support it like that), then your Thinkpad can, and will generate proper ACPI events without the help of ibm-acpi. This is valid for a complete ACPI config of kernel 2.6.16 with all modules loaded.

And it will generate regular ibm-acpi hotkey events if you enable the feature and use the correct mask, which may or may not confuse the thinkpad (I am not sure the correct DSDT handlers the BIOS expect to run are called in this case).

-- [[User:Hmh|hmh]] 2006-05-26 13:20 UTC

==Turn on/off Wifi on Fn5 ==
Hi

I hope this is the last question. I use a crude way to activate and deactivate my wificard: I remove and insert the relevant modules, with 2 simple scripts. Now the question is how can I bind Fn5 so, that it turns on and off the wificard? With my approach I need to fire up two scripts, and that I cannot bind to one button. Thanks
[[User:Oub|Oub]] 17:57, 5 March 2006 (CET):

Try a {{cmdroot|cat /proc/acpi/ibm/bluetooth}}. Maybe it returns the state. If not, the other way would be to check if the USB bluetooth controller device is listed in {{path|/proc/bus/usb}} somewhere. It shouldn't be there if bluetooth is switched off and should be there if it is on.

[[User:Wyrfel|Wyrfel]] 04:49, 6 March 2006 (CET)
----

==Split page?==
This page is getting too long. Maybe we should split it. I'd suggest moving the "Example applications" to a seperate page.

[[User:Pebolle|Paul Bolle]] 22:46, 3 April 2006 (CEST)

==DIY Firefox 1.5 xpi==
Here's how I maneged a Firefox 1.5 compatible plugin (source: google). Note that the wiki eats some of the xml tags (so look at the source too)

$ ls -1R tp41.xpi
tp41.xpi/:
chrome
chrome.manifest
install.rdf

tp41.xpi/chrome:
content

tp41.xpi/chrome/content:
tp41keysOverlay.xul

$ cat tp41.xpi/chrome.manifest
content tp41keys chrome/content/
overlay chrome://browser/content/browser.xul chrome://tp41keys/content/tp41keysOverlay.xul

$ cat tp41.xpi/install.rdf
<?xml version="1.0"?>

<RDF xmlns="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:em="http://www.mozilla.org/2004/em-rdf#">

<Description about="urn:mozilla:install-manifest">
<em:id>tp41keys@tp41keys.org</em:id>
<em:version>1.0</em:version>
<em:type>2</em:type>


<em:targetApplication>
<Description>
<em:id>{ec8030f7-c20a-464f-9b0e-13a3a9e97384}</em:id>
<em:minVersion>1.0+</em:minVersion>
<em:maxVersion>1.5.0.*</em:maxVersion>
</Description>
</em:targetApplication>


<em:name>IBM ThinkPad 41 Keys</em:name>
<em:description>Two Browser Navigation Keys</em:description>
<em:creator>Paul Bolle</em:creator>
<em:homepageURL>http://www.example.com/tp41keys.xpi</em:homepageURL>
</Description>
</RDF>

$ cat tp41.xpi/chrome/content/tp41keysOverlay.xul
<?xml version='1.0'?>
<!DOCTYPE overlay>

<overlay id='tp41keysOverlay'
xmlns='http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul'>

<keyset id='mainKeyset'>
<key id='tp41BackKey' keycode='VK_F21' command='Browser:Back' />
<key id='tp41ForwardKey' keycode='VK_F22' command='Browser:Forward' />
</keyset>

</overlay>

$ cat .mozilla/firefox/*.default/extensions/tp41keys\@tp41keys.org
~/tp41.xpi

==ibm-acpi hint==

I would like to add a hint under ibm-acpi to enable all hotkeys at boot, but I can not seem to get the HINT template to work:

<nowiki>{{HINT|To enable all hotkeys on boot in debian, create the file /etc/modprobe.d/ibm_acpi containing 'options ibm_acpi hotkey=enable,0xffff'}}</nowiki>

It outputs:

{{HINT|To enable all hotkeys on boot in debian, create the file /etc/modprobe.d/ibm_acpi containing 'options ibm_acpi hotkey=enable,0xffff'}}

Any ideas on how to get this to work? Also, does it even belong in the page?

--[[User:Paul Strefling|Paul Strefling]] 23:22, 10 August 2006 (CEST)

If you use ''ibm-apci'' as a module and have {{path|/proc}} filesystem enabled, you can tune it by
adding to {{path|/etc/modules.d/ibm_acpi}}:

post-install ibm-acpi /bin/echo enable,0x00d0 > /proc/acpi/ibm/hotkey
I added it after ''alias ibm-acpi ibm_acpi''. I'm not sure - if the order make sence. Params can be differ - it is an example.

Also works fine with {{cmdroot|modprobe}} (don't forget to run {{cmdroot|modules-update}} after editing {{path|/etc/modules.d/*}}).

(tested on Gentoo with vanilla kernel).

==Lock Screen with hotkey on models before T60==

In case it's of interest, it's possible to simulate the "lock screen" (Fn+F2) function of T60s on prior models. I wrote a little [http://forums.gentoo.org/viewtopic-p-3814885.html HOWTO] on the Gentoo forums explaining how to configure Fn+F3 to fire up xscreensaver instead of blanking the screen (though this could easily be changed to Fn+F2 instead). This was for my T42 but I presume it'd work on other models too. Perhaps it'd be worth mentioning in the Remarks column of the Fn+F2 row of the table at the top of the article? --[[User:Waveform|Waveform]] 03:42, 2 January 2007 (CET)

== Toggle touchpad with Fn-F8 ==

I often want to switch off the touchpad, since I tend to produce spurious taps while typing, sending my cursor to random places on the screen. To toggle touchpad operation, I use this little script:

#!/bin/sh
#
# toggle touchpad operation
# August 2, 2006
# (c) Michael Schmuker
#
if synclient -l | grep TouchpadOff | grep -q 0; then
synclient TouchpadOff=1;
kdialog --passivepopup "Touchpad is OFF" 2;
else
synclient TouchpadOff=0;
kdialog --passivepopup "Touchpad is ON" 2;
fi

This checks if the touchpad is on or off, and toggles its state accordingly. Note that it uses kdialog to display a notification on the desktop. This obviously works only with KDE, but there certainly is a similar mechanism for other desktop environments.

Now this script needs to be bound to the Fn-F8-key. On Suse 10.2, the ACPI-events produced by the thinkpad special keys are processed by powersaved. You need to edit the file {{path|/usr/lib/powersave/scripts/thinkpad_acpi_events}}.
There, thinkpad-ACPI events are bound to their actions. Where it comes to Fn-F8, just change it to the following (supposed you put the above script to {{path|/usr/local/bin/toggleTouchpad}} and make it executable):
4104) HOTKEY="Fn+F8" #toggle touchpad on/off
/usr/local/bin/toggleTouchpad
;;
Save the file, and the next time you press Fn-F8 you will toggle your touchpad.

Unfortunately, the notification via kdialog is not working when toggling with Fn-F8. If anyone finds out how to solve this: Let us know!

'''Possible Solutions:'''

1. You can instead use syndaemon, which can turn off the touchpad for a brief period while you are typing.

2. All acpi events are run as root. Therefore, to enable the kdialog, you will need to incorporate a script to determine which user is running on DISPLAY :0.0; something like the following should work (put it in your acpi file)
if ps -e | grep -q -E '(enlightenment|kwin|dwm)'; then
X_USER=`/usr/bin/who | /usr/bin/sed -n "s,^$.*$:0 .*$,\1,p"`
X_USER=${X_USER/ /};
export DISPLAY=:0.0
fi
if [ -n "$X_USER" ]; then su $X_USER -c "/usr/local/bin/toggleTouchpad";
else /usr/local/bin/toggleTouchpad;
fi
--[[User:Ppurka|Ppurka]] 18:43, 14 September 2007 (UTC)

== What about older machines? ==

On the 600X, Fn+PgUp and Fn+PgDn control speaker volume and Fn+Backspace toggles speaker mute. In addition, Fn+F2 is shows a battery icon and the manual states that it brings up a battery monitor. It hasn't worked since Windows 95. Fn+F11 shows a dripping tap and is meant to select a power mode. Fn+F8 has no icon but toggles screen expansion.

On the 750P, Fn+F5 and Fn+F6 control speaker volume, and I think Fn+F2 and Fn+F11 show the same icons as the 600X. However, that machine certainly doesn't have ACPI. Fn+F8 toggles screen inversion (black shows as white and vice-versa) on the monochrome models and Fn+F9 toggles brightness inversion (normal characters become bright and bright characters become normal). Those two only affect the internal LCD and not the signal on the VGA connector.

--[[User:Whizkid|Whizkid]] 19:32, 27 November 2007 (UTC)

Please add that information to the [[Default meanings of special keys]] page, including the description of the icons and functions. As for how to use these keys, it depends. How well does thinkpad-acpi work on the 600X and 750P? If it doesn't work at all, then you have to resort to tpb, which may have no idea how to access these keys in NVRAM :-(

--[[User:Hmh|hmh]] 14:18, 30 November 2007 (UTC)

I've updated the descriptions of functions on that page for 750P, 560E and 600X. There are no descriptions of icons anywhere on that page. An example to start with would be nice. The 750 family doesn't have ACPI at all.
--[[User:Whizkid|Whizkid]] 14:09, 25 December 2007 (UTC)

== ThinkVantage button not recognized by xev under Hardy ==

Hello,

I would like to set up the ThinkVantage button as XF86LaunchA, but I simply can't as it doesn't give any signal in xev. Any ideas how could I fix this?

Thanks, [[User:Nagyv|Nagyv]] 22:54, 3 July 2008 (CEST)

As the button is no "real keyboard button" it does not generate a keycode, but an acpi event (maybe thinkpad_acpi is needed for it to work) which you can set up to do what ever you want (well, not everything). see the article.

--[[User:BDKMPSS|BDKMPSS]] 23:45, 3 July 2008 (CEST)

Thank, this worked. I only had to add a new file under /etc/acpi/events. As there were many working examples, it was easy to write my own. Finally, I had to restart acpid.

thanks, [[User:Nagyv|Nagyv]]

== Who is the boss? Your Thinkpad's special keys or you? ==

The x tools setxkbmap and xbindkeys along with the kde 3.5 control center keyboard shortcuts and application links in ~/.kde/Autostart are the tools that I use to do every keyboard thing I want with my

----

* R61 7732-CTO

* BIOS 7LETC4WW (2.24), EC 7KHT24WW-1.08

* Intel(R) Core(TM)2 Duo CPU T5470 @ 1.60GHz, stepping 0d

* 4G Mushkin RAM

* 320G WDC WD3200BEKT

* Linux version 2.6.30-4-amd64

* kde 3.5.10

* Debian Stable

* Number of Packages: stable 1473, testing 473, unstable 199

----

You may also find xmodmap useful, I didn't.

check out:

http://www.palmix.org/xmodmap-en.html

http://xorg.freedesktop.org/archive/X11R7.0/doc/html/setxkbmap.1.html

https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch

man setxkbmap

man xbindkeys

man xbindkeys-config

anything else you need would be in /usr/share/doc/ on Debian

You must! learn to use Google effectively

An important command for getting this together was on the HotkeyResearch page:

xev | grep -A2 --line-buffered '^KeyRelease' | sed -n '/keycode /s/^.*keycode $[0-9]*$.* (.*, $.*$).*$/\1 \2/p'

It told me which fn-{key} had keycodes and what they were. I was surprised to find that some didn't have keycodes.

Here's the way to do it:

1) read the above references!! don't email me with questions that have answers in the text.

2) set your keyboard properly. I looked at /etc/X11/xkb/base.xml <name> tag values, then created in ~/.kde/Autostart with konqueror a "link to application" for the statement 'setxkbmap -model thinkpad60 -layout us'

3) use the above xev|etc. command to find the keycodes for the keys you need to map.

4) for fun you can look at the keycode to keysym correspondences that exist currently by executing xmodmap -pk at the command line

5) you may have to create an ~/.xmodmap with the keycode to keysym additions or modifications, I didn't

6) determine what functionality you want the key combinations to provide

7) use kde keyboard shortcuts to map key combinations (ex fn-F5) to your shortcut scheme. If it doesn't have something you want, like control of amarok with the multimedia keys you either need to create a menu item for the application and a command shortcut or you can use xbindkeys-config to do it. You can't do both.

8) I used xbindkeys-config for a few things but it became a little difficult to use so I created menu items. I later realized that xbindkeys-config and xev didn't see the same keys. I had to map fn-F4 with xbindkeys-config and fn-F12 with a command shortcut.

9) the amarok controller I used is remoot, just search for it, it isn't in Debian, but a Debian package is available

I will be writing sometime soon on suspension/hibernation. I use pm-suspend and pm-hibernate, which are in the pm-utils Debian package. If I can figure it out, you can too. Read the documentation.

Dare to be great! Kick butt!

[[User:rdskaroff+debian@gmail.com|Bob]]

== Microphone Mute Key ==
I've filled a bug report ([https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/728310 LP728310]) for the missing microphone mute support in Ubuntu 10.10.

This bug report contains some info about how to get a bit of the functionality working.

--[[User:Dveeden|Dveeden]] 10:39, 3 March 2011 (CET)

User:Dveeden

2011-03-02T10:14:02Z

Dveeden: â†Created page with 'PPA for Thinkpad Fixes: [https://launchpad.net/~dveeden/+archive/thinkpad-fixes ppa:dveeden/thinkpad-fixes]'

PPA for Thinkpad Fixes: [https://launchpad.net/~dveeden/+archive/thinkpad-fixes ppa:dveeden/thinkpad-fixes]

Talk:Ricoh MMC/SD Host Controller

2011-03-02T10:13:08Z

Dveeden:

Bug for missing support for Ricoh MemoryStick reader in Ubuntu:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/626823

MMC Support is tested on Ubuntu 10.10 x86_64 and found to be working for a 1G MMC card.

--[[User:Dveeden|Dveeden]] 11:13, 2 March 2011 (CET)

Talk:Ricoh MMC/SD Host Controller

2011-03-02T10:13:00Z

Dveeden:

Bug for missing support for Ricoh MemoryStick reader in Ubuntu:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/626823

MMC Support is tested on Ubuntu 10.10 x86_64 and found to be working for a 1G MMC card.
--[[User:Dveeden|Dveeden]] 11:13, 2 March 2011 (CET)

Talk:Ricoh MMC/SD Host Controller

2011-03-02T10:12:51Z

Dveeden: â†Created page with 'Bug for missing support for Ricoh MemoryStick reader in Ubuntu: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/626823 MMC Support is tested on Ubuntu 10.10 x86_64 a...'

Ricoh MMC/SD Host Controller

2011-03-02T10:11:25Z

Dveeden: /* Linux support */

{| width="100%"
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
This Ricoh MultiCard Reader is found on select ThinkPads, and supports MMC, SD, SDHC, Memory Stick and Memory Stick Pro cards. In addition, with an appropriate adapter it can support miniSD, microSD and Memory Stick M2.

SDXC should also works as they are identical to SDHC, however larger then 32GB SDXC by default uses the Microsoft exFAT filesystem which may be incompatible with the operating system in use.

Memory Stick XC support is unknown, but it also defaults to exFAT, so at that level has the same issues as SDXC.

* PCI 1180:e822 - MMC/SD Host Controller
* PCI 1180:e230 - Memory Stick Host Controller
</div>
|}
__NOTOC__

=== Linux support ===
This is a PCI device.

'''MMC'''
* works

'''SD / SDHC'''
* works through the '''sdhci''' driver

'''SDXC'''
* should work with the '''sdhci''' driver. Note however that larger then 32GB cards by default use the proprietary (patented) Microsoft exFAT filesystem which is not supported. The solution for such cards is to change filesystem, assuming that the devices the card is to be used with also support other filesystems.

'''MS / MS Pro'''
* No driver exists for this model Ricoh Memory Stick Host Controller.

=== Models featuring this Technology ===
* {{T410}}, {{T410i}}, {{T410s}}, {{T510}}, {{T510i}}
* {{W510}}, {{W701}}, {{W701ds}}
* {{X201}}, {{X201 Tablet}}

Qualcomm Gobi 2000

2011-03-02T10:00:17Z

Dveeden: /* GPS */

Qualcomm Gobi 2000

2011-03-02T09:59:46Z

Dveeden: /* GPS */

Qualcomm Gobi 2000

2011-03-02T09:57:41Z

Dveeden: /* GPS */

Qualcomm Gobi 2000

2011-03-02T09:52:46Z

Dveeden: /* GPS */

Intel Centrino Advanced-N 6200

2011-03-02T09:45:27Z

Dveeden: /* Features */

__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;">
== Intel Centrino Advanced-N 6200 ==
This is a Mini-PCI Express WiFi Adapter, supported by the iwlagn driver

== Features ==
* Chipset: ?
* IEEE Standards: 802.11a, 802.11b, 802.11g ,802.11n
* 2x2 MIMO up to 300Mbps
* PCI ID: 8086:4239
</div>
|style="vertical-align:top" |
[[image:IntelWiFi6200.jpg|Intel Centrino Advanced-N 6200]]<br/>
|}
=== Lenovo Partnumbers ===
* ?

=== Drivers ===
* Linux: iwlagn

=== Models featuring this Technology ===
* {{Edge 14"}}, {{Edge 15"}}
* {{L412}}, {{L512}}
* {{T410}}, {{T410s}}, {{T510}}
* {{X201}}, {{X201s}}, {{X201 Tablet}}

=== External Links===
* http://www.intel.com/network/connectivity/products/wireless/adapters/6200-6300/index.htm
* http://intellinuxwireless.org/ - Intel website for Linux drivers

Integrated camera

2011-03-02T09:20:37Z

Dveeden:

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;" | [[Image:integrated_camera.jpg|Integrated Camera]] __NOTOC__
|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;">
=== The Integrated camera ===
Almost all recent ThinkPads have an integrated camera above the display. This camera (typically called a webcam) is USB attached. On some earlier ThinkPads a proprietary camera was used, but later models use a standard UVC camera which is supported by the [http://linux-uvc.berlios.de/ uvcvideo driver].
</div>
|}

== ThinkPads which may have a proprietary camera ==
These ThinkPads have a 0.3MP fixed focus Sonix SN9C201 camera which is supported by the '''gspca_sn9c20x''' driver.

* {{Z61t}}, {{Z61m}}

== ThinkPads which may have a UVC camera ==
'''0.3MP fixed focus'''
* {{Edge 11"}}, {{Edge 13"}}
* {{X100e}}

'''1.3MP fixed focus'''
* {{R61}}, {{R61i}}, {{R400}}, {{R500}}
* {{SL300}}
* {{T61}}, {{T400}}, {{T500}}
* {{W500}}, {{W700}}, {{W700ds}}
* {{X200}}, {{X200s}}, {{X200 Tablet}}, {{X300}}, {{X301}}

'''2.0MP fixed focus'''

USB ID: 17ef:480d (Lenovo Integrated Webcam [R5U877])
* {{Edge 14"}}, {{Edge 15"}}
* {{L412}}, {{L512}}
* {{SL400}}, {{SL410}}, {{SL500}}, {{SL510}}
* {{T400s}}, {{T410}}, {{T410i}}, {{T410s}}, {{T410si}}, {{T510}}, {{T510i}}
* {{W510}}, {{W701}}, {{W701ds}}
* {{X201}}, {{X201 Tablet}}

[[Category:Components]]

Ricoh MMC/SD Host Controller

2011-03-02T09:16:11Z

Dveeden: /* Models featuring this Technology */

{| width="100%"
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
This Ricoh MultiCard Reader is found on select ThinkPads, and supports MMC, SD, SDHC, Memory Stick and Memory Stick Pro cards. In addition, with an appropriate adapter it can support miniSD, microSD and Memory Stick M2.

SDXC should also works as they are identical to SDHC, however larger then 32GB SDXC by default uses the Microsoft exFAT filesystem which may be incompatible with the operating system in use.

Memory Stick XC support is unknown, but it also defaults to exFAT, so at that level has the same issues as SDXC.

* PCI 1180:e822 - MMC/SD Host Controller
* PCI 1180:e230 - Memory Stick Host Controller
</div>
|}
__NOTOC__

=== Linux support ===
This is a PCI device.

'''MMC'''
* support unknown - should work
{{HELP|please test if you have the hardware and update the information here.}}

'''SD / SDHC'''
* works through the '''sdhci''' driver

'''SDXC'''
* should work with the '''sdhci''' driver. Note however that larger then 32GB cards by default use the proprietary (patented) Microsoft exFAT filesystem which is not supported. The solution for such cards is to change filesystem, assuming that the devices the card is to be used with also support other filesystems.

'''MS / MS Pro'''
* No driver exists for this model Ricoh Memory Stick Host Controller.

=== Models featuring this Technology ===
* {{T410}}, {{T410i}}, {{T410s}}, {{T510}}, {{T510i}}
* {{W510}}, {{W701}}, {{W701ds}}
* {{X201}}, {{X201 Tablet}}

Category:T410s

2011-03-02T09:15:49Z

Dveeden:

__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;">

=== ThinkPad T410s ===
This page gives an overview of all ThinkPad T410s related topics.

==== Machine Type ====
* 2901, 2904, 2912, 2924

==== Standard Features ====
*One of the following [[Intel Core i5]] processors:
** Intel® Core™ i5-520M (2.4GHz, 3MB L2)
** Intel® Core™ i5-560M (2.67Ghz, 3MB L2)
** Intel® Core™ i5-580M (2.66GHz, 3MB L2)
* [[Intel HD Graphics]]
* One of the following displays
** 14.1" TFT display with 1440x900 (WXGA+) resolution with LED backlight
** 14.1" TFT display with 1440x900 (WXGA+) resolution with LED backlight and [[MultiTouch]] (NOT recommended for Linux systems as of January 2011).
* 2, 3 or 4GB [[PC3-8500]] memory standard upgradable to 8GB
* One of the follow HDD
** 80GB SSD 1.8" HDD
** 128GB SSD 1.8" HDD
** 160GB SSD 1.8" HDD (Intel® SSDSA1M160G2LE)
** 120GB 5400rpm 1.8" SATA HDD
** 250GB 5400rpm 1.8" SATA HDD
* [[Ultrabay|Serial Ultrabay Slim]] with one of the following:
** [[Serial Ultrabay Slim DVD Burner II]]
* 2.0MP [[Integrated camera]] on select models
* [[ThinkPad Bluetooth with Enhanced Data Rate (BDC-2.1)|Bluetooth]] on select models
* [[Intel Gigabit Ethernet (10/100/1000) PCI-Express]]
* Intel HD Audio with a [[CX20585]] codec
* [[ExpressCard slot|ExpressCard/34 slot]] or [[Ricoh 5-in-1 MultiCard Reader]] (MS not supported on Linux)
* [[MiniPCI Express slot]] 1 with the following:
** [[Intel Centrino Advanced-N 6200]]
** [[Intel Centrino Advanced-N + WiMAX 6250]]
** [[Intel Centrino Ultimate-N 6300]]
** [[ThinkPad 11b/g/n Wireless LAN Mini-PCI Express Adapter II]]
* [[MiniPCI Express slot]] 2 with one of the following:
** None (empty)
** [[Qualcomm Gobi 2000]] WWAN with GPS
* [[Integrated Fingerprint Reader]] on select models
* [[UltraNav]] (TrackPoint / Touchpad combo)
* [[Embedded Security Subsystem|Trusted Computing Group TPM 1.2]]
* [[Active Protection System]]
* [[Intel Active Management Technology (AMT)]]
</div>
|style="vertical-align:top" |
[[Image:ThinkPadT410s.jpg|ThinkPad T410s|300px]]
|}

=== Linux Installation ===

Installation instructions for the {{ThinkPad|T410s|Installation instructions for the}}

[[Category:T Series]]

=== Automatic Display Switching on Resume ===

* See [[Automatic Display Switching on Resume]]

=== Color profile for the display ===

Some people find the display to have an ugly blue cast. To get rid of it, you can download this [http://biomachinelearning.net/T410sTwoDown.icc ICC profile] which, once loaded, should give you much more neutral colors. The profile was created with [http://argyllcms.org/ ArgyllCMS], a formidable free open source color management system. Once you installed Argyll, use this line to load the profile:
dispwin path/to/profile.icc

The profile was created with display bightness two ticks below maximum. Note that although the profile is likely to improve your color rendering, it may be not optimal for your display. For better results, get a colorimeter and create your own profile.

Your distribution might even offer packages of Argyll (e.g., openSUSE does in its [http://download.opensuse.org/repositories/multimedia:/photo/openSUSE_11.3/ multimedia:photo repository.]).

If you want to give me some feedback about the profile, you can do so on my [[User_talk:Shamuki |Talk page]].

[[Category:T Series]]

Talk:Qualcomm Gobi 2000

2011-02-21T11:01:22Z

Dveeden: /* GPS */

== 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!
--[[User: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)

Thanks a lot, Invented!

I also got some helpful advice from linrunner here: http://forum.ubuntuusers.de/topic/erneut-problem-mit-gobi-2000-umts-modem/

The trick was to remove the AC adapter as well as the battery and (what I didn't know before) press the power button for some time (> 30 sec.).
That did the job.
So I didn't come to the point trying out yours.
Both tricks might be helpful to know for others!

I suspect my problem either occurred because the USB support in qemu (in my case version 0.12.5) is still experimental or because the Lenovo drivers and programs do not run properly if they don't see a true Thinkpad hardware environment.

I might try out your trick once again with a native Windows installation.
But it doesn't seem too appealing to me for now.
Maybe someone finds out what the checkbox 'Auto Tracking' actually does.
Would be nice to get it working without any Windows installation.

Thanks again!

--[[User:stman|stman]] 9:50, 23 January 2011 (UTC)

Invented, I hope you don't mind I've added a 'Troubleshooting' section (describing the two ways of resetting the Gobi 2000) for the page.
--[[User:stman|stman]] 15:17, 23 January 2011 (UTC)

On Ubuntu 10.10 with a Gobi 2000 I had to make a minor change to the udev rulefile for gobi-loader to work consistently -- line 3 of /lib/udev/rules.d/60-gobi.rules should read
ACTION=="add", SUBSYSTEM=="tty" '''DEVNAME'''=="ttyUSB*" GOTO="gobi_rules"
as opposed to
ACTION=="add", SUBSYSTEM=="tty" '''KERNEL'''=="ttyUSB*" GOTO="gobi_rules"
--[[User:Derkacha|Derkacha]] 00:56, 9 February 2011 (CET)

I've created a PPA for the GPS enabled qcserial modules. This uses DKMS to automatically compile the module for the used kernel package. It's available on [https://launchpad.net/~dveeden/+archive/thinkpad-fixes ppa:dveeden/thinkpad-fixes]. GPS does work on a T410s with Gobi 2000 with the firmware loaded and without a SIM card.

--[[User:Dveeden|Dveeden]] 10:58, 21 February 2011 (CET)

Intel HD Graphics

2011-02-21T10:58:58Z

Dveeden: /* Resources */

__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;">

The '''Intel HD Graphics''' (sometimes also called GMA HD) is the Graphics Memory Accelerator (GMA) integrated in the [[Intel Core i3]], [[Intel Core i5]] and selected [[Intel Core i7]] processors.
== Features ==
* Chipset: Arrandale (GMCH Ironlake)
* PCI ID: 8086:0046
* PCI-E
{{NOTE|While almost all new ThinkPads have integrated '''Intel HD Graphics''', on those ThinkPads with a ''Descrete'' NVIDIA GPU, the Intel GPU is disabled and cannot be enabled. There is no support for ''Switchable Graphics''.}}
{{NOTE|Contrary to the statement above, you can select the GPU in the BIOS of recent models with Nvidia Optimus, e.g. the T510 4384GEG. Windows seems to be able to switch between the GPUs, too. }}
</div>
|style="vertical-align:top" |
|}

== Linux support ==
A very recent Linux distribution with kernel 2.6.33 and Intel Xorg driver 2.11 or newer is recommended.

Note that XVideo (Xv) playback at certain frame sizes does not work properly unless you have at least version 2.12 of the Intel Xorg driver.

== Models featuring this Technology ==
* ThinkPad {{Edge 11"}}, {{Edge 14"}}, {{Edge 15"}}
* ThinkPad {{L412}}, {{L512}}
* ThinkPad {{T410}}, {{T410i}}, {{T410s}}, {{T410si}}, {{T510}}, {{T510i}}
* ThinkPad {{X201}}, {{X201i}}, {{X201s}}, {{X201 Tablet}}

== Resources ==
* http://software.intel.com/en-us/articles/quick-reference-guide-to-intel-integrated-graphics/
* http://intellinuxgraphics.org/

Talk:Qualcomm Gobi 2000

2011-02-21T09:58:44Z

Dveeden: /* GPS */

== 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!
--[[User: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)

Thanks a lot, Invented!

I also got some helpful advice from linrunner here: http://forum.ubuntuusers.de/topic/erneut-problem-mit-gobi-2000-umts-modem/

The trick was to remove the AC adapter as well as the battery and (what I didn't know before) press the power button for some time (> 30 sec.).
That did the job.
So I didn't come to the point trying out yours.
Both tricks might be helpful to know for others!

I suspect my problem either occurred because the USB support in qemu (in my case version 0.12.5) is still experimental or because the Lenovo drivers and programs do not run properly if they don't see a true Thinkpad hardware environment.

I might try out your trick once again with a native Windows installation.
But it doesn't seem too appealing to me for now.
Maybe someone finds out what the checkbox 'Auto Tracking' actually does.
Would be nice to get it working without any Windows installation.

Thanks again!

--[[User:stman|stman]] 9:50, 23 January 2011 (UTC)

Invented, I hope you don't mind I've added a 'Troubleshooting' section (describing the two ways of resetting the Gobi 2000) for the page.
--[[User:stman|stman]] 15:17, 23 January 2011 (UTC)

On Ubuntu 10.10 with a Gobi 2000 I had to make a minor change to the udev rulefile for gobi-loader to work consistently -- line 3 of /lib/udev/rules.d/60-gobi.rules should read
ACTION=="add", SUBSYSTEM=="tty" '''DEVNAME'''=="ttyUSB*" GOTO="gobi_rules"
as opposed to
ACTION=="add", SUBSYSTEM=="tty" '''KERNEL'''=="ttyUSB*" GOTO="gobi_rules"
--[[User:Derkacha|Derkacha]] 00:56, 9 February 2011 (CET)

I've created a PPA for the GPS enabled qcserial modules. This uses DKMS to automatically compile the module for the used kernel package. It's available on [https://launchpad.net/~dveeden/+archive/thinkpad-fixes ppa:dveeden/thinkpad-fixes]

--[[User:Dveeden|Dveeden]] 10:58, 21 February 2011 (CET)