ThinkWiki - User contributions [en]

Thermal Sensors

2012-08-20T23:19:18Z

Papertiger:

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
This page summarizes known information about the locations and properties of thermal sensors on ThinkPad laptops.
|}

==Accessing the sensors==

===Basic ACPI system temperature sensors===
The primary means of accessing the thermal sensors is through the [[thinkpad-acpi]] module, up to 16 sensors are supported. When the module is loaded, the sensors (some of which may be inactive) are shown through the standard sysfs hwmon interface used by the lm-sensors utilities, and also in {{path|/proc/acpi/ibm/thermal}} (which is deprecated and has been removed from the latest versions of the module).

lm-sensors/libsensors uses the hwmon interface exposed through {{path|/sys/bus/platform/devices/thinkpad_hwmon/}} to read the temperatures, note that the sysfs interface returns normal open errors instead of weird values for sensors that are not active (which the simplistic '''sensors''' command ignore). lm-sensors/libsensors can be configured to give proper names to each sensor, which will be used by any properly written sensor applet.

{{cmdroot|sensors}}
{{cmdresult|thinkpad-isa-0000
Adapter: ISA adapter
fan1: 3914 RPM
CPU: +45.0°C
LAN/Heatsink/HDAPS: +44.0°C
PC-CARD slot: +35.0°C
GPU: +48.0°C
Main battery charger: +35.0°C
ERROR: Can't get value of subfeature temp6_input: Can't read
Bay battery charger: +0.0°C
Main battery cells: +30.0°C
ERROR: Can't get value of subfeature temp8_input: Can't read
Bay battery cells: +0.0°C
MCH: +42.0°C
PLL clock/ICH/WLAN: +50.0°C
Voltage regulator: +43.0°C}}

To have 'sensors' use describing labels like above, you can add the following section to /etc/sensors3.conf, if not already there. This is an example for the T43. Similar technique apply for the other models. Use the sensor location findings below.

chip "thinkpad-isa-0000"
label fan1 "Fan"
label temp1 "CPU"
label temp2 "HDAPS"
label temp3 "PCMCIA"
label temp4 "GPU"
label temp5 "System battery (front left, charging circuit)"
label temp7 "System battery (rear right)"
label temp9 "Bus between Northbridge and DRAM; Ethernet chip"
label temp10 "Southbridge, WLAN and clock generator"
label temp11 "Power circuitry"

The old method to access the thermal readings is through the {{path|/proc}} interface:

:{{cmdroot|cat /proc/acpi/ibm/thermal}}
:{{cmdresult|temperatures: 44 41 33 42 33 -128 30 -128}}

A value of -128 (i.e., 0x80 hex) means the sensor is not connected. For example, above the two -128 values belong to the UltraBay battery, which is not plugged in.

If the ThinkPad supports the extended sensor set, eight more values will be displayed:

:{{cmdroot|cat /proc/acpi/ibm/thermal}}
:{{cmdresult|temperatures: 44 41 33 42 33 -128 30 -128 48 50 49 -128 -128 -128 -128 -128}}

===HDAPS temperature sensor===
The [[Active Protection System]] firmware also reports a temperature, which is identical to one of the ACPI sensors. The corresponding sensor is actually not inside the HDAPS chip, and sometimes not even close to it.
:{{cmdroot|cat /sys/bus/platform/drivers/hdaps/hdaps/temp1}}
:{{cmdresult|41}}

===Harddisks SMART temperature sensor===
The system hard disk temperature can be read through the disk's SMART interface:
:{{cmdroot|<nowiki>smartctl -A /dev/hda | grep Temperature</nowiki>}}
:{{cmdresult|194 Temperature_Celsius 0x0022 145 097 000 Old_age Always - 31}}

Or, for SATA-equipped models running a recent Linux kernel (see [[Problems with SATA and Linux]]):

:{{cmdroot|<nowiki>smartctl -A -d ata /dev/sda | grep Temperature</nowiki>}}
:{{cmdresult|194 Temperature_Celsius 0x0022 145 097 000 Old_age Always - 31}}

When the [[UltraBay Slim HDD Adapter]] or [[UltraBay Slim SATA HDD Adapter]] are used, the second hard disk will typically provide another temperature readout via its SMART interface, analogously to the above.

Reading this sensor will typically cause a drive spin-up and head unload.

===Hitachi harddisks <tt>SENSE CONDITION</tt> temperature sensor===

Recent Hitachi disks provide a non-standard <tt>SENSE CONDITION</tt> command which reads the disk temperature without causing a spin-up or head load. The reported value is the same as when using SMART. This can be invoked, e.g., using {{cmdroot|hdparm -H}}, or the relevant code in {{CodeRef|tp-fancontrol}}. When using the <tt>libata</tt> driver, this requires kernel >= 2.6.19-rc1.

==Utilities for viewing temperatures==

The following utilities display the ThinkPad-specific thermal sensor readouts:
* The above shell commands.
* The "Sensors" builtin of [[GKrellM]] can show 6 specific ACPI sensors (out of up to 11).
* [http://kima.sourceforge.net/ Kima] is a KDE applet that can display the 8 first ACPI sensors as well as the HDAPS sensor.
* [http://www.kraus.tk/projects/IBMDoK/ IBMDoK], another KDE applet. Shows 4 specific sensors (out of up to 11). So far only tested at the {{T60}}.
* There is an [http://munin.projects.linpro.no/wiki/plugin-ibm_acpi ibm_acpi plugin] for [http://munin.projects.linpro.no/ Munin].
* [http://sensors-applet.sourceforge.net/ GNOME Sensors Applet] supports ibm_acpi.

==Sensor locations==
This information is model specific.

===ThinkPad {{A31}}===
Found by Milos Popovic using cooling spray to cool down components on a completely removed, running motherboard, to locate the sensors. Also reported [http://forum.thinkpads.com/viewtopic.php?t=31837 here].
EC offset Index in "thermal" Location (estimated)
0x78 1 CPU
0x79 2 Battery (this one heats up when on battery power)
0x7A 3 Power (sensor near power diodes and CPU; heats up when high power consumption, has crosstalk from CPU)
0x7B 4 Ultrabay 2000 battery?
0x7C 5 Northbridge (sensor next to Northbridge, also somewhat near GPU)
0x7D 6 PCMCIA/ambient (sensor is a National Semiconductor LM75 Digital Temperature Sensor/Thermal Watchdog chip
next to the 9-pin VGA connector; sits right under PCMCIA slots but doesn't touch)
0x7E 7 Battery (this one stays near ambient temperature, even when on battery power)
0x7F 8 Ultrabay 2000 battery?
0xC0 none zero
0xC1 none zero
0xC2 none zero
The following photos (resolution reduced for server space) show the locations found for the listed temperature sensors.
{{gallery_start}}
{{thumb|A31_2652M3U_systemboardtop_DSCN6105_tempsensors_lores.jpg|ThinkPad A31 sensor locations on top of motherboard.}}
{{thumb|A31_2652M3U_systemboardbottom_DSCN6105_tempsensors_lores.jpg|ThinkPad A31 sensor locations on bottom of motherboard.}}
{{gallery_end}}
On this A31 systemboard (FRU 26P8398), there is a [http://www.maxim-ic.com/quick_view2.cfm/qv_pk/2313 Maxim MAX1668] 5-channel remote/local temperature sensor (4 remote + 1 self temperature) on top of the systemboard, and a [http://www.national.com/pf/LM/LM75.html National Semiconductor LM75] single-channel "digital temperature sensor and thermal watchdog" chip. It would appear that the LM75 has the ability to hard shutdown the processor (without software intervention) if its temperature exceeds a given threshold. I'm not sure if it is wired for this, nor whether the Thinkpad changes the threshold temperature from the chip's power-up default of 80Â°C. A software application with drivers on the LM75 webpage is available that claims to allow direct access to the thermal sensor chip (this hasn't been tried, but could be useful in other models to determine if this sensor is somewhere on the MB, and which register it corresponds to). The MAX1668's self-temperature reading does not appear anywhere in the above temperature registers; it's not clear whether it is read at all, and whether it is to be found elsewhere in the EC memory. These two chips (LM75 and MAX1668) account for some of the sensors.

===ThinkPad {{R51}}===
The [[thinkpad-acpi]] documentation includes the report by Thomas Gruber:
EC offset Index in "thermal" Location (estimated)
0x78 1 CPU
0x79 2 Mini-PCI
0x7A 3 HDD
0x7B 4 GPU
0x7C 5 System battery
0x7D 6 UltraBay battery
0x7E 7 System battery
0x7F 8 UltraBay battery
0xC0 none ?
0xC1 none ?
0xC2 none ?

===ThinkPad {{T40}}===
The location of one of the sensors is identified [http://forum.thinkpads.com/viewtopic.php?t=11574 here].
EC offset Index in "thermal" Location (estimated)
0x78 1 CPU
0x79 2 System board under rear left corner of Mini-PCI module
0x7A 3 ?
0x7B 4 GPU
0x7C 5 Battery
0x7D 6 n/a
0x7E 7 Battery
0x7F 8 n/a
0xC0 none n/a
0xC1 none n/a
0xC2 none n/a

===ThinkPad {{T43}}, {{T43p}}===
Found by Shmidoax using cooling spray to cool down components and observe the effect on the sensors.
EC offset Index in "thermal" Location (estimated)
0x78 1 CPU
0x79 2 Between PCMCIA slot and CPU (same as HDAPS module)
0x7A 3 PCMCIA slot
0x7B 4 GPU
0x7C 5 System battery (front left = charging circuit)
0x7D 6 UltraBay battery
0x7E 7 System battery (rear right)
0x7F 8 UltraBay battery
0xC0 9 Bus between Northbridge and DRAM; Ethernet chip
0xC1 10 Southbridge, WLAN and clock generator (under Mini-PCI card, under touchpad)
0xC2 11 Power circuitry, on underside of system board under F2 key
{{gallery_start}}
{{thumb|T43-thermal-sensors.jpg|ThinkPad T43 sensor locations}}
{{thumb|T43-2668-thermal-sensors-zoom.jpg|ThinkPad T43 sensor locations detail}}
{{thumb|T43p-H8S2161.jpg|ThinkPad T43/p 26xx Embedded Controller Renesas H8S/2161BV}}
{{gallery_end}}

===ThinkPad {{T60}}===
Found by Marco Kraus for use in [http://www.kraus.tk/projects/IBMDoK/ IBMDok].
EC offset Index in "thermal" Location (estimated)
0x78 1 CPU
0x79 2 APS
0x7A 3 PCM
0x7B 4 GPU
0x7C 5 BAT
0x7D 6 n/a
0x7E 7 BAT
0x7F 8 n/a
0xC0 9 n/a
0xC1 10 n/a
0xC2 11 n/a
0xC3 12 n/a
0xC4 13 n/a
0xC5 14 n/a
0xC6 15 n/a
0xC7 16 n/a

/etc/sensors.d/tpsensors
chip "acpitz-virtual-0"
label temp1 "CPU_0"
label temp2 "CPU_1"
chip "thinkpad-isa-0000"
label fan1 "FAN"
label temp1 "CPU"
label temp2 "APS"
label temp3 "PCM"
label temp4 "GPU"
label temp5 "BAT"
ignore temp6 "n/a"
label temp7 "BAT"
ignore temp8 "n/a"
label temp9 "BUS"
label temp10 "PCI"
label temp11 "PWR"
ignore temp12 "n/a"
ignore temp13 "n/a"
ignore temp14 "n/a"
ignore temp15 "n/a"
ignore temp16 "n/a"

The CPU thermal sensors seem to be exposed in both {{path|/proc/acpi/thermal_zone/THM0/temperature}} and {{path|/proc/acpi/thermal_zone/THM1/temperature}}, though the latter curiously seems to exist only in this file and nowhere in {{path|/proc/acpi/ibm/ecdump}}.

===ThinkPad {{T61}}===

'''Sensor numbering correlated with {{path|/sys/devices/platform/thinkpad_hwmon/temp*_input}}'''

{| border="1" cellspacing="0" cellpadding="2"
! Thermal ID !! Location/Related Hardware !! Confirmed !! Notes
|-
| 1 || CPU || {{Cyes}} ||
|-
| 2 || North-bridge || {{Cpart}} ||
|-
| 3 || Cardbus/ExpressCard Bay || {{Cyes}} ||
|-
| 4 || GPU || {{Cyes}} || seperate from GPU's integrated sensor
|-
| 5 || 9-Cell Battery - Secondary || {{Cyes}} || static @ 50C on 6-cell
|-
| 6 || Ultrabay - Secondary || {{Cyes}} || Available only when device present
|-
| 7 || 6/9-Cell Battery - Primary || {{Cyes}} ||
|-
| 8 || UltraBay - Primary || {{Cyes}} || Available only when device present
|-
| 9 || RAM || {{Cyes}} ||
|-
| 10 || Right of RAM, Under Touchpad || {{Cyes}} ||
|-
| 11 || Mini-PCI Area || {{Cpart}} ||
|}
{{Todo|determine sensor 6 and 8 relavence for other UltraBay accessories}}
{{Todo|confirm sensor 11}}

'''Contributors:''' ''Daniel Castro, [[User:Lunatico|Lunatico]], [[User:andrewcbates|Andrew C Bates]]''

===ThinkPad {{T61p}}===

'''Sensor numbering correlated with {{path|/sys/devices/platform/thinkpad_hwmon/temp*_input}}'''

{| border="1" cellspacing="0" cellpadding="2"
! Thermal ID !! Location/Related Hardware !! Confirmed !! Notes
|-
| 1 || CPU || {{Cyes}} ||
|-
| 2 || North-bridge || {{Cpart}} ||
|-
| 3 || Cardbus/ExpressCard Bay || {{Cyes}} ||
|-
| 4 || GPU || {{Cyes}} || seperate from GPU's integrated sensor
|-
| 5 || 9-Cell Battery - Secondary || {{Cyes}} || static @ 50C on 6-cell
|-
| 6 || Ultrabay - Secondary || {{Cyes}} || Available only when device present
|-
| 7 || 6/9-Cell Battery - Primary || {{Cyes}} ||
|-
| 8 || UltraBay - Primary || {{Cyes}} || Available only when device present
|-
| 9 || RAM || {{Cyes}} ||
|-
| 10 || Right of RAM, Under Touchpad || {{Cyes}} ||
|-
| 11 || Mini-PCI Area || {{Cpart}} ||
|}
{{Todo|determine sensor 6 and 8 relavence for other UltraBay accessories}}
{{Todo|confirm sensor 11}}

'''Contributors:''' ''[[User:andrewcbates|Andrew C Bates]]''

===ThinkPad {{T400}}===
Experimenting with a hair dryer, fgl_glxgears, grep and tools like that I ([[User:Dummyaccount|Dummyaccount]]) came to the following conclusions for the sensor-index mapping. More comments are provided at [http://www.cosy.sbg.ac.at/~shuber/misc-t400.php#temp_sensors].

Index in "thermal" Location
1 CPU neighbourhood (also via ACPI THM0)
2 Ultrabay
3 Express card
4 ATI graphics module
5 Main battery (always around 50°C)
6 n/a (probably ultrabay battery)
7 Main Battery (fits about the value reported by smapi)
8 n/a (probably ultrabay battery)
9 Hard disc
10 Intel graphics module
11 Heatsink?
12 n/a
13 n/a
14 n/a
15 n/a
16 n/a

===ThinkPad {{T400s}}===

Index in "thermal" Location
1 CPU neighbourhood (same as ACPI THM0)
2 ?
3 ?
4 n/a
5 Main battery
6 Ultrabay battery
7 Main Battery
8 Ultrabay battery
9 ?
10 n/a
11 ?
12 n/a
13 n/a
14 n/a
15 n/a
16 n/a

None of the these matches ACPI THM1, which (judging by the dramatic response to CPU load) is probably the CPU's on-die thermal sensor.

===ThinkPad {{T500}}===
According to [http://forum.thinkpads.com/viewtopic.php?f=45&t=75032], the sensors in the T500 "may be identical to those reported for the [[#ThinkPad T61|T61]]", with the possibility that #11 may be the CPU heatsink. "It is very closely correlated to cpu load but shows a lot more inertia than sensor 1 which changes almost instantaneously with cpu load."

I ([[User:Nandhp]]) experimented with running glxgears, this produces a spike in #9, which does not occur under regular CPU load. #5 and #7 both belong to the main battery, for they disappear when it is removed. [http://www.kernel.org/doc/Documentation/laptops/thinkpad-acpi.txt] suggests #6 and #8 should be for the UltraBay battery. It also implies that #4 should be for the GPU, however, my model (which has an integrated GPU) does not have a #4 sensor. --[[User:Nandhp|Nandhp]] 19:27, 17 June 2009 (UTC)

Index in "thermal" Location
1 CPU (also via ACPI THM0)
2 ? (very similar to HDD smart temp)
3 ? (also via ACPI THM1)
4 n/a
5 Main Battery A
6 n/a (probably Second Battery A)
7 Main Battery B
8 n/a (probably Second Battery B)
9 ? (possibly (integrated) GPU)
10 ?
11 ? (possibly heatsink)
12 n/a
13 n/a
14 n/a
15 n/a
16 n/a

===ThinkPad {{X22}} {{X23}} {{X24}}===
There is a chip very close to the CPU, which monitors the processor and its own temperature, reports as temperatures 1 and 2 respectively. In X22, this sensor is ADM1023ARQ. In X24, the chip is NE1618. I think the sensor for temperature 3 is on the underside. Temperature 3 is high while charging battery.

EC offset Index in "thermal" Location
0x78 1 CPU
0x79 2 just in front of CPU
0x7A 3 ? gets hot when charging battery

{{gallery_start}}
{{thumb|X22_heatsink.JPG|location of CPU thermal monitor}}
{{gallery_end}}

===ThinkPad {{X31}}===
I figured these out by myself ([[User:BDKMPSS|BDKMPSS]]), as there are just a few available, this wasn't a huge problem. I verified my presumptions with a contactless thermometer.
EC offset Index in "thermal" Location (estimated)
0x78 1 CPU
0x79 2 n/a
0x7A 3 GPU?
0x7B 4 near or the ICH4M Southbrige, on the back of the Motherboard
0x7C 5 Battery
0x7D 6 Extended-Life-Battery; may also UltraBay battery
0x7E 7 Battery
0x7F 8 Extended-Life-Battery; may also UltraBay battery
0xC0 none n/a
0xC1 none n/a
0xC2 none n/a

0x7A "GPU?" is pretty hot and seems like the GPU, but as the Chipset and the GPU are cooled with the same heatsink it is difficult to separate them without roasting the machine. However the left and GPU side of the heatsink is much closer to the shown value than the right Chipset side.

===ThinkPad {{X61}}===
[[User:Jdthood|I]] have started to figure out which sensors are which.

Index Location How known?
1 CPU Increases immediately on computationally intensive task
2 HDAPS Always the same value as /sys/bus/platform/drivers/hdaps/hdaps/temp1
3
4
5 Battery Disappears if battery removed
7 Battery Disappears if battery removed
9
10

===ThinkPad {{X200 Tablet}}===
That's what [[User:Jdthood|I]] found out so far. Hope the guys in the german tp-forum have some more details. [http://thinkpad-forum.de/threads/143790-Temperatursensoren-im-X200-Tablet thread]

Sensors Location How known?
temp1 CPU Increases immediately on computationally intensive task
temp5 Battery Disappears if battery removed
temp7 Battery Disappears if battery removed

===ThinkPad {{X220}}===
On [[User:Jdthood|my]] X220 there is only one sensor, named <tt>fan1</tt>.

<pre>
$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +49.0°C (crit = +99.0°C)

thinkpad-isa-0000
Adapter: ISA adapter
fan1: 1954 RPM
$ lsmod | grep '^t[hp]'
thinkpad_acpi 81587 0
tpm_tis 18537 1
tpm 22267 1 tpm_tis
tpm_bios 13684 1 tpm
tp_smapi 28471 0
thinkpad_ec 14450 2 hdaps,tp_smapi
$ modinfo thinkpad-acpi|grep vers
filename: /lib/modules/2.6.38-11-generic/kernel/drivers/platform/x86/thinkpad_acpi.ko
version: 0.24
srcversion: 0B6457473BB90551EE1D20F
vermagic: 2.6.38-11-generic SMP mod_unload modversions
</pre>

Extending battery life on X200

2012-05-19T13:46:22Z

Papertiger: Changed markup for external urls to the correct one

== Overview ==

I own the beautiful Lenovo X200 and run Ubuntu Intrepid on the machine. Its battery life is significantly lower than that under Windows and many users have reported that it runs hotter than under Windows.

With the changes below and a 9 cell battery I get over 9 hours on an idle system with backlight at the lowest level and wireless radios off. Before the changes I was only getting 5 hours.

The system also runs a lot cooler and I do not need tpfan (sw fan control for the ThinkPad available [[Fan_control_scripts|here]]), the built-in hw controller falls back to the lower speeds shortly after a CPU load subsides.

=== Details ===

The changes fall into 3 categories:
* '''Removing packages that create unnecessarily frequent wake up interrupts.'''
**These interrupts wake up the CPU, preventing it from staying in its most energy efficient state.
**I used Powertop from [http://www.lesswatts.org www.lesswatts.org] for this task.
* '''Lowering the voltage supplied to the CPU.'''
** Lowering CPU voltage does ''not'' impact performance since the clock frequency is unaffected
**I used phc patches and phctools available at [http://www.linux-phc.org www.linux-phc.org] for this task.
*'''Turning off radios that are not needed''
**My X200 has 3 wireless radios: Wifi, Bluetooth, Broadband wireless

== Finding and removing high interrupt packages ==
Install PowerTOP from [http://www.lesswatts.org/projects/powertop/download.php here].

Run PowerTOP as root (sudo powertop) and look for the packages that come up on top of the interrupt frequency list. These are the packages that wake up the CPU most frequently.

In my case the majority of the ''easily'' ''preventable'' interrupts were from 3 packages:
*i915, the intel graphics driver
*SCIM
*Gnome Power Manager

With the first one accounting for the bulk of the battery life improvement.

The %'s in PowerTOP give you an indication of what to focus on, no need to worry about a 1% problem (unless it is easy to prevent that it), it will not have much impact on your battery life.

Remember that over time these packages will improve and will not need to be removed.
=== Turning off DRI ===
Just insert: Option "NoDRI"
to the "Device" section in /etc/X11/xorg.conf. This turns off all 3D, so no compiz or other fancy effect. Worth it for me because the impact on battery life is substantial.
===Turning off SCIM===
I had my system set to accept foreign characters. Going to System > Language Support > Disable support to enter complex characters does the trick.
===Turning off Gnome Power Manager===
You may decide you cannot live without it, but on my system I disabled Gnome Power Manager from the startup list: System > Sessions > Power Management daemon.

I replaced it with the ''Gnome Panel'' Battery Charge Monitor (Add to Panel...) which works well enough for me.

== Reducing CPU voltage ==
===Installing phc module patches===
The phc module patches are available [http://www.ubuntuforums.org/showthread.php?t=786402 here], make sure you get the version that matches you kernel version. You can easily check by typing uname -r in a console.

You need not compile your own module, check the thread, users have posted already compiled versions of the acpi-cpufreg.ko module for most kernel versions.

Once you have the apci-cpufreq.ko module, back up the old module:
sudo cp /lib/modules/$(uname -r)/kernel/arch/x86/kernel/cpu/cpufreq/acpi_cpufreq.ko
/lib/modules/$(uname -r)/kernel/arch/x86/kernel/cpu/cpufreq/acpi_cpufreq.ko.bak

Then copy the new module to the right place:
sudo cp acpi_cpufreq.ko /lib/modules/$(uname -r)/kernel/arch/x86/kernel/cpu/cpufreq

Restart your system and check that you now have voltage controls by typing:
more /sys/devices/system/cpu/cpu0/cpufreq/phc_vids

You should see something like:
38 29 23 13 (your values may be different)
These are the voltage index values for the 4 frequencies available on your CPU. They are directly related to the actual voltages, phctools does the computation for you as explained below.

'''Notes:'''
*If you check phc_fids you will see values that do not make sense
more /sys/devices/system/cpu/cpu0/cpufreq/phc_fids
These are supposed to be the available frequency indexes, which are the ratios of CPU frequency to FSB frequency, sometimes called multipliers. There is a bug in the phc patches which affects how the multiplers are reported. This bug does not affect undervolting your CPU.

===Intalling phctools===
Download them [http://www.linux-phc.org/ here].

Unpack the package in a directory where you can conveniently access it. Use the install script (install.sh) to enable pctools to run without requiring a password.

Also download [http://www.linux-phc.org/viewtopic.php?f=9&t=16 here] the update which supports the Core2Duo CPU.

Unpack the archive and copy the file to"inc/libs" within the PHCTool directory (replace the old one).

Lastly made sure the module msr is loaded. PhcTool works without it, but having it loaded allows it to display the actual votage fed into your CPU.
sudo modprobe msr

You can make this module load automatically by adding it to the file /etc/modules

Also install the burnMMX application, it is designed to put a heavy load on your system and is necessary to make sure the voltages you choose will work under load:
sudo apt-get install burnMMX

===Experimenting with lower voltages===
This is the scary part: you will have to crash your system on purpose. I found it to be harmless, but be forewarned that some users have reported that it could damage your system.

DO NOT RUN THIS TEST WITH A CUSTOM PROGRAM TO CONTROL THE FAN, YOU COULD FRY YOUR SYSTEM. FIRST REVERT TO HW CONTROLLED FAN IF YOU MADE ANY CHANGES TO FAN CONTROL.

Check that you are using "ondemand" as the frequency scaling governor. This governor delivers the lowest power consumption according to Intel. An easy way to do this is to use Frequency Scaling Monitor Gnome panel applet.

Another way is to check:
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
which returns the currently active governor. You can echo a new value as root, it takes effect immediately.

Start phctools:
phctools.sh

On the Info tab, you will see your CPU identified and the available frequencies for this CPU:
2267Mhz 2266Mhz 1600Mhz 800Mhz

On the Voltage tab you will see the VID and corresponding voltage for each frequency as well as the difference from the default values.

The phc patches prevent you from using a value higher than the highest defaults voltage or a value lower than the lowest default voltage even though phctools will let you enter higher and lower values. They will have no effect, so stay within the range defined by the highest and lowest VID value.

The default values are also reloaded each time you restart the system. Do NOT set phctools to "restore VID on load" at this time.

Now the fun begins...
#Start burnMMX in a terminal window. WARNING this puts a lot of stress on your sys
#Lower the first VID value, 25 should work to get started. Do this for both CPU's (tab on the left for CPU0 and CPU1
#Save values
#Use your system for a bit and see if it is stable
#Lower the first VID value until your system crashes (or stop before if you do not dare).

My threshold was 15, at this VID my system crashes after less than a minute. At this point reboot your system, restart phctools and set the VID for 2267Mhz to the value that crashed '''+ 2'''. Do this for both CPU's.

Restart and work on the other frequencies, using the Frequency Scaling Monitor applet to force the CPU to the frequency you want to test.

On my system the safe values were:
17 15 13 13

===Making the voltages stick===
One you have found the lowest VID's that your system can safely run with, enter them on phctools Voltages for both CPU0 and CPU1, then go to settings and click "restore VID's on load".

All that is left is to make phctools restore your VID's each time you boot. Add the command:
yourphcdirectory/phctools.sh background
to your startup applications in System > Sessions. It will automatically start phctools, make it restore your VID's and quit.

Note that if you do nothing, the original VID's are automatically reloaded each time you reboot the system.

==Turning off the wireless radios==
The X200 has a great feature: a button on the left side to disable all radios. Use it when you do not need wireless.
When you need wireless, use FN + F5 to turn on/off Wifi and Blutooth.

The hidden power hog is the 3G broadband modem (Ericsson F3507g), even when the 3G led is off. To completely shut down power to the modem:
sudo echo 0 > /sys/devices/platform/thinkpad_acpi/wwan_enable

There are scripts to do this automatically [[Ericsson_F3507g_Mobile_Broadband_Module | here]].

[[Category:X200]]
[[Category:HOWTOs]]

Wacom Serial Tablet PC Stylus

2010-03-12T22:24:10Z

Papertiger: changed rotation of cursor keys from static to variable keycodes

__NOTOC__
{| width="100%"
|style="vertical-align:top" |[[Image:Logo_wacom.gif|Wacom Logo]]
|style="vertical-align:top" |
<div style="margin:0px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== Wacom Serial Tablet PC Stylus ===
This is a stylus made for tablet PCs by Wacom.
=== Features ===
* Chipset: Wacom
* Serial: irq 5 port 0x0200
</div>
|}

==Linux Support==
The pen is supported by the XFree/Xorg Wacom driver. New tablets also have the [[MultiTouch]] capability. [[MultiTouch]] is experimentally supported presently by the Linux wacom project. The pen works regardless of [[MultiTouch]] support.

==Fist steps==
Get the [http://linuxwacom.sourceforge.net/index.php/dl linux wacom driver] and install it on your system.

The pen uses serial and appears on some {{path|/dev/ttySnn}} device where <tt>nn</tt> is a number. An easy way to find it is to map {{path|/dev/ttyS0}} to the pen's port and irq. The values can be found under the windows driver properties. Using values from an {{X41T}} 1869-5CU, the command is: {{cmdroot|setserial /dev/ttyS0 port 0x0200 irq 5 autoconfig}} (you need to run this after every suspend/resume cycle).

This may be inserted into startup scripts in {{path|/etc/rc.d/}} or {{path|/etc/rc.local}}

After mapping the pen, you can check its output with {{cmdroot|wacdump -f tpc /dev/ttyS0}}. This will list raw information about the pens position an click status. Hit Ctrl+C to exit wacdump.

==Setting up your Xorg.conf==
Now that you see the pen working correctly you should configure your Xserver to use the stylus. Add the following sections to your xorg.conf:

Section "InputDevice"
Driver "wacom"
Identifier "cursor"
Option "Device" "/dev/ttyS0"
Option "Type" "cursor"
Option "ForceDevice" "ISDV4"
Option "Mode" "Absolute"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "stylus"
Option "Device" "/dev/ttyS0"
Option "Type" "stylus"
Option "ForceDevice" "ISDV4"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "eraser"
Option "Device" "/dev/ttyS0"
Option "Type" "eraser"
Option "ForceDevice" "ISDV4"
EndSection

# support for "touch" (with finger, available on x200t and some x61t)
Section "InputDevice"
Driver "wacom"
Identifier "touch"
Option "Device" "/dev/ttyS0" # SERIAL ONLY
Option "Type" "touch"
Option "ForceDevice" "ISDV4" # Serial Tablet PC ONLY
EndSection

Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Default Screen" 0 0
InputDevice "Configured Mouse" "CorePointer"
InputDevice "cursor" "SendCoreEvents"
InputDevice "stylus" "SendCoreEvents"
InputDevice "eraser" "SendCoreEvents"
#InputDevice "touch" "SendCoreEvents" #Uncomment if you have this feature.
EndSection

Check the wacom driver man page and [http://linuxwacom.sf.net/ website] for other options.

For handwriting recognition using pen you can use [[CellWriter]].

To get the right mouse button to map to the stylus button use this script and run it through .bashrc

#!/bin/bash
xsetwacom set stylus Button1 1
xsetwacom set stylus Button2 3
xsetwacom set stylus Button3 3

==Wacomcpl==
I found it useful to create a .desktop file for launching the wacomcpl program which is used for many user options for the tablet pen.

[Desktop Entry]
Type=Application
Encoding=UTF-8
Name=wacomcpl
GenericName=linux wacom config
Comment=linux wacom configuration tool
TryExec=wacomcpl
Exec=wacomcpl
Terminal=false
Categories=System;
Icon=wacomcpl.png

To have your settings restore after logout/suspend/restart you will need to edit {{path|/home/yourusername/.xinitrc}}.
Go to the last line and change

. /etc/X11/xinit/xinitrc

to read as

# . /etc/X11/xinit/xinitrc

Next you need to create a new sessions preference to load the user file.

For Debian [lenny] go to System > Preferences > Sessions.
Add a new startup program and add the command
sh /home/yourusername/.xinitrc
click ok.

For Ubuntu use System > Preferences > Startup Applications.
add the same startup program as above.

--[[User:Jeremy!|Jeremy!]] 14:49, 29 October 2009 (UTC)

==xrandr Rotation==

There is work underway to create a [https://code.edge.launchpad.net/~karl.hegbloom/tabuntu/tablet-screen-rotation-support Tablet Screen Rotation Support] package for Ubuntu. Because I can afford only one tablet computer, and since this is relatively new and not many others have put any work into it yet, so far it mainly supports the Lenovo Thinkpad X61 Tablet. The next phase of development involves refactoring in such a way that it can easily be expanded to support other brands and models of tablet computer. The planned mechanism is similar to that used by the scripts in the Debian acpi-support package.

So far, it supports auto-rotation on conversion from laptop to tablet mode, including rebinding the navpad keys and turning the logical orientation of the Wacom tablet to match. It is done as an event called when the X Server has changed it's xRandR orientation. The actual work is carried out by a quick set of shell scripts that can easily be adapted and extended. The idea is that no matter what piece of software actually caused the X Server to rotate, the same things need to happen whenever it does. So the best place to hook in the support event is on an event handler for the RandR Rotate event. The programs and packaging are simple, and the source is available at the URL above. I encourage you to get a copy and learn from it while helping make it work for a new kind of tablet no other developer has created support for yet! If you can write an essay, you can write the necessary program.

Because this ThinkWiki page is one of the sources I drew from when I initially created tablet-screen-rotation-support. The following scripts by Gtx, radix, and Papertiger probably contain some elements in common. --[[User:KarlHegbloom|KarlHegbloom]] 21:55, 9 February 2009 (UTC)

=== xrotate support scripts ===

linuxwacom is very buggy. I needed some time to get the tablet work with "xrandr -r". I use the script below to do screen rotation. copy the source an put it in /usr/local/bin/xrotate. You may change output and devices to fit to you're system (the default values work fine for an x41 tablet)

you can use "xrotate +" to rotate the screen CCW or "xrotate -" to rotate clockwise. use "xrotate x" where x is
* 0 to set rotation to normal
* 1 to set rotation to left
* 2 to set rotation to inverted
* 3 to set rotation to right

#!/bin/sh

output=LVDS
if [ "$XROT_OUTPUT" ]
then
output=$XROT_OUTPUT;
fi
devices="stylus cursor"

geomnbr=0
xrandr=normal
wacom=normal
if [ "$1" == "-" ] || [ "$1" == "+" ] || ! [ "$1" ];
then
operator="$1";
[ "$1" ] || operator='+';
case `xrandr --verbose | grep "^$output " | sed "s/^[^ ]* [^ ]* [^ ]* ([^(]*) $[a-z]*$.*/\1/"` in
normal) geom=0;;
left) geom=1;;
inverted) geom=2;;
right) geom=3;;
esac
let geom=${geom}${operator}1+4
let geom=${geom}%4
else
geom="$1"
fi

case $geom in
1) wacom=2; xrandr=left ;;
2) wacom=3; xrandr=inverted ;;
3) wacom=1; xrandr=right ;;
*) wacom=0; xrandr=normal ;;
esac

echo "xrandr to $xrandr, xsetwacom to $wacom" >&2

if xrandr --output "$output" --rotate "$xrandr"; then
for d in $devices
do
xsetwacom set "$device" Rotate "$wacom"
done
fi

#workaround for linuxwacom bug
if [ "`xsetwacom get stylus Mode`" == '1' ]; then
for d in $devices
do
xsetwacom set stylus CoreEvent "off"
xsetwacom set stylus Mode "off"
done
{ sleep 1;
for d in $devices
do
xsetwacom set stylus Mode "on"
xsetwacom set stylus CoreEvent "on"
done; } &
fi

--[[User:Gtx|Gtx]] 13:34, 22 April 2008 (CEST)

modified script for linuxwacom 0.8.1-1.

#!/bin/sh

output="(normal left inverted right)" #LVDS
# if [ "$XROT_OUTPUT" ]
# then
# output=$XROT_OUTPUT;
# fi
devices="stylus cursor"

geomnbr=0
xrandr=normal
wacom=normal
if [ "$1" == "-" ] || [ "$1" == "+" ] || ! [ "$1" ];
then
operator="$1";
[ "$1" ] || operator='+';
case `xrandr --verbose | grep "$output" | sed "s/^[^ ]* [^ ]* [^ ]* ([^(]*) $[a-z]*$.*/\1/"` in
normal) geom=0;;
left) geom=1;;
inverted) geom=2;;
right) geom=3;;
esac
let geom=${geom}${operator}1+4
let geom=${geom}%4
else
geom="$1"
fi
case $geom in
1) wacom=2; xrandr=left ;;
2) wacom=3; xrandr=inverted ;;
3) wacom=1; xrandr=right ;;
*) wacom=0; xrandr=normal ;;
esac

echo "xrandr to $xrandr, xsetwacom to $wacom" >&2

if xrandr -o "$xrandr"; then
for d in $devices
do
xsetwacom set "stylus" Rotate "$wacom"
done
fi

#workaround for linuxwacom bug
if [ "`xsetwacom get stylus Mode`" == '1' ]; then
for d in $devices
do
xsetwacom set stylus CoreEvent "off"
xsetwacom set stylus Mode "off"
done
{ sleep 1;
for d in $devices
do
xsetwacom set stylus Mode "on"
xsetwacom set stylus CoreEvent "on"
done; } &
fi

--[[User:radix|radix]] 13:15, 28 August 2008 (CEST)

Additional code for rotating the 4 navigation keys on the display frame.

<pre>
key_up=111
key_down=116
key_left=113
key_right=114

case $geom in
1) xmodmap -e "keycode $key_up = Right";xmodmap -e "keycode $key_left = Up";xmodmap -e "keycode $key_right = Down";xmodmap -e "keycode $key_down = Left";;
2) xmodmap -e "keycode $key_up = Down";xmodmap -e "keycode $key_left = Right";xmodmap -e "keycode $key_right = Left";xmodmap -e "keycode $key_down = Up";;
3) xmodmap -e "keycode $key_up = Left";xmodmap -e "keycode $key_left = Down";xmodmap -e "keycode $key_right = Up";xmodmap -e "keycode $key_down = Right";;
*) xmodmap -e "keycode $key_up = Up";xmodmap -e "keycode $key_left = Left";xmodmap -e "keycode $key_right = Right";xmodmap -e "keycode $key_down = Down";;
esac
</pre>
--[[User:Papertiger|Papertiger]] 22:24, 12 March 2010 (UTC)

==Troubleshooting==

If the stylus still doesn't work try to reset the bios. This fixed it for me. --[[User:Gtx|Gtx]] 08:22, 21 April 2008 (CEST)

==Models featuring this Device==
*ThinkPad {{X41_Tablet}}
*ThinkPad {{X60_Tablet}}
*ThinkPad {{X61_Tablet}}
*ThinkPad {{X200_Tablet}}

[[Category:Components]]

Wacom Serial Tablet PC Stylus

2009-01-16T02:05:51Z

Papertiger: