ThinkWiki - User contributions [en]

Tp smapi

2010-07-03T15:03:27Z

BDKMPSS: /* X series */ fix wrong BIOS/ECfw IDs created by lazy cp&paste

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
The <tt>tp_smapi</tt> kernel module exposes some features of the ThinkPad hardware/firmware via a <tt>sysfs</tt> interface. Currently, the main implemented functionality is control of battery charging and extended battery status. The tp_smapi software package also includes an improved version of the [[HDAPS]] driver. The underlying hardware interfaces are [[SMAPI support for Linux|SMAPI]] and direct access to the embedded controller.

This driver uses undocumented features and direct hardware access, so it may work unreliably or even damage your hardware; but so far no such damage has been reported.
|}

===Features===
*<tt>tp_smapi</tt> driver
**Battery charge/discharge control
**Battery status information
*<tt>hdaps</tt> driver (compared with the standard <tt>hdaps</tt> driver)
**Improved stability
**Improved model support
**Improved functionality

===Project Homepage / Availability===
* Project page: http://tpctl.sourceforge.net/
* Download page: http://sourceforge.net/projects/tpctl/files/tp_smapi
* You need to download only the <i>tp_smapi</i> package.

===Installation===
====Installation from source====
You will need the kernel headers and makefiles corresponding to your current kernel version. On {{Fedora}}, this means {{cmdroot|yum install kernel-devel-$(uname -r)}} .

:{{cmdroot|tar xzvf tp_smapi-0.40.tgz}}
:{{cmdroot|cd tp_smapi-0.40}}

Then, either compile and load the driver within the current working directory (for testing):
:{{cmdroot|make load}}
OR compile and install into the kernel's module path:
:{{cmdroot|make install}}

If you use the [[HDAPS]] driver, add <tt>HDAPS=1</tt> to also patch the <tt>hdaps</tt> for compatibility with <tt>tp_smapi</tt> (this requires a kernel source tree matching the current kernel).
Again, either load the driver within the current working directory:
:{{cmdroot|1=make load HDAPS=1}}
OR install into the kernel's module path:
:{{cmdroot|1=make install HDAPS=1}}

To prepare a stand-alone patch against the current kernel tree (including
a patch against <tt>hdaps</tt> and new <tt>Kconfig</tt> entries):
:{{cmdroot|make patch}}

To delete all autogenerated files:
:{{cmdroot|make clean}}

The original kernel tree is never modified by any these commands.
The {{path|/lib/modules}} directory is modified only by {{cmdroot|make install}}.

====Installation in Gentoo====
The {{Gentoo}} portage system carries a [http://packages.gentoo.org/package/app-laptop/tp_smapi tp_smapi package], which follows the latest version pretty closely. On a Gentoo system, you can install and load as follows.

If you use the [[HDAPS]] driver, do this first:

* Disable the <tt>hdaps</tt> module in your kernel configuration (Device Drivers → Hardware Monitoring Support → IBM Hard Drive Active Protection System)
* Rebuild and install the kernel
* Add the <tt>hdaps</tt> use flag in {{path|/etc/make.conf}}
* {{cmdroot|rmmod hdaps}}

Then:
* {{cmdroot|emerge tp_smapi}} (or install tp_smapi with hdaps support manually, as above)
* {{cmdroot|echo "tp_smapi" >> /etc/modules.autoload.d/kernel-2.6}}
* {{cmdroot|echo "hdaps" >> /etc/modules.autoload.d/kernel-2.6}}

Then reboot, or run:
* {{cmdroot|modprobe tp_smapi}}
* {{cmdroot|modprobe hdaps}}

'''NOTE:''' If {{cmdroot|modprobe}} fails and dmesg says something about <tt>__stack_chk_fail()</tt>, you probably just compiled your modules with <tt>-fstack-protector</tt> and/or <tt>-fstack-protector-all</tt> without having a kernel that supports it. You can either configure your kernel to have <tt>CC_STACKPROTECTOR</tt> enabled (in ''Processor type and features'' if you use {{cmdroot|make menuconfig}}) or edit your <tt>make.conf</tt> (or, if you're using paludis, your <tt>/etc/paludis/bashrc</tt>) and remove <tt>-fstack-protector</tt> and <tt>-fstack-protector-all</tt> from your <tt>CFLAGS</tt>. If you choose to enable it in the kernel, be aware that you need a patched GCC for it (and I do not know if the gcc in stage3 is patched).

====Installation on Debian unstable (sid), testing (squeeze) or stable (lenny)====
Debian now contains the [http://packages.debian.org/tp-smapi packaged module source] and prebuilt modules for Debian kernels.

If you use a stock Debian kernel, you can install the tp_smapi modules with:
* {{cmdroot|apt-get install tp-smapi-modules-`uname -r`}}
* in order to make sure the modules package is kept in sync with the kernel one, you may also want to install the <code>tm-smapi-modules-2.6-686</code> or <code>tm-smapi-modules-2.6-amd64</code> package, depending on your architecture

If you use a custom kernel, you can build tp_smapi with module-assistant:
* {{cmdroot|aptitude install tp-smapi-source}}
* {{cmdroot|m-a -t a-i tp-smapi}}

====Installation on openSUSE====
openSUSE provides rpm packages. Look for them at the package search: [http://software.opensuse.org/search/], search for the package named "tp_smapi".

A step-by-step guide on how a relative linux newbie installed tp_smapi on a Thinkpad W500 running openSuse 11.1 using YAST Software Manager is available [http://forums.opensuse.org/hardware/laptop/417254-tp_smapi-lenovo-thinkpad-t400-t500-w500-step-step.html#post2005932 here]

In case you are taking the hard way around, while compiling on 11.0, make complained about not being able to locate the kernel sources. It worked for me after I did this:
<pre><nowiki>cp /usr/include/linux/aio_abi.h /lib/modules/`uname -r`/build/include/linux/</nowiki></pre>

====Installation on Ubuntu====
Ubuntu ships tp_smapi in their <tt>linux-ubuntu-modules-*</tt> package for Hardy, so you don't have to build it yourself. Please note that they have renamed tp_smapi's modified <tt>hdaps</tt> module to <tt>hdaps_ec</tt> so that the two can coexist. You should load <tt>hdaps_ec</tt>, not <tt>hdaps</tt>.

Ubuntu Intrepid and Jaunty, however, lack the <tt>hdaps_ec</tt> module, as reported [https://bugs.launchpad.net/ubuntu/+source/linux/+bug/297213 here]. It will not be included again until said [[#Bundled hdaps driver|bundled hdaps driver]] is merged into mainline.

=====Installation on Ubuntu Jaunty=====
I have posted my experiences [http://meandmyubuntu.blogspot.com/2009/05/getting-hdasp-to-work-on-jaunty.html here]

=====Installation on Ubuntu Karmic=====
Ubuntu does not ship the precompiled module tp_smapi any more. However the source code is still present in the repository. It can be installed through module-assistant :
:{{cmdroot|aptitude install tp-smapi-source}}
:{{cmdroot|module-assistant prepare tp-smapi}}
:{{cmdroot|module-assistant auto-install tp-smapi}}
:{{cmdroot|modprobe tp-smapi}}

=====Installation on Ubuntu Lucid=====
The Karmic solution above works well.

As an alternative, one can use the dkms flavour of the packages via
:{{cmdroot|aptitude install tp-smapi-dkms}}
:{{cmdroot|modprobe tp_smapi}}

====Installation on older Ubuntu/Debian====
Installation on Ubuntu or Debian is quite easy, but there are a few things to look after:

To get your system ready for compiling code, install the build-essentials (as root, of course, as all of the following comands; Ubuntu users have to prepend 'sudo' to every line and enter their own password when prompted):
<pre><nowiki>apt-get install build-essential</nowiki></pre>

To get tp_smapi to work, obtain the latest source as mentioned above and unpack it. If you want to use HDAPS, you need to install the kernel source matching te kernel you are running. To do so, issue this:
<pre><nowiki>uname -r</nowiki></pre>
This will give you the version of your current kernel.
Debian users execute the following:
<pre><nowiki>apt-get install linux-source-`uname -r`</nowiki></pre>
Ubuntu users execute the following using the kernel-version only (exclude -XX-generic; e.g. 'linux-source-2.6.20'):
<pre><nowiki>apt-get install linux-source-`uname -r`</nowiki></pre>

Be sure to unpack the source file. The easiest way is to open Nautilus as root:
<pre><nowiki>sudo nautilus</nowiki></pre>
Then browse to /usr/src/ and extract the source file to that directory.

Now change to the tp_smapi dir:
<pre><nowiki>cd tp_smapi-X.YY</nowiki></pre> (X.YY being the version-number of [[tp_smapi]])
and make and install tp_smapi as instructed above.

If you get an error that the kernel version isn't matching (or that you need to set KSRC/KBUILD), please check that there is a symlink from the modules dir to the kernel source:
<pre><nowiki>root@localhost:~#ls -l /lib/modules/2.6.20-16-generic
lrwxrwxrwx 1 root root 28 2007-02-02 08:39 build -> /usr/src/linux-source-2.6.20</nowiki></pre>
Create the link if the line above does not exist:
<pre><nowiki>root@localhost:~#ln -s /usr/src/linux-source-2.6.20 /lib/modules/2.6.20-16-generic/build</nowiki></pre>

Now the following will build and install the correct modules to their locations:
<pre><nowiki>make install HDAPS=1</nowiki></pre>
To make sure your system loads the modules at boot time, do this:
<pre><nowiki>echo "tp_smapi" >> /etc/modules
echo "hdaps" >> /etc/modules</nowiki></pre>
and update your initramfs:
<pre><nowiki>update-initramfs -u</nowiki></pre>

To get tp_smapi running now, just load the modules:
<pre><nowiki>modprobe -a tp_smapi hdaps</nowiki></pre>

This description was tested on Kubuntu 'Feisty Fawn' and should work on all Debian-based distros with minor tweaks.

'''EDIT:''' Works on Kubuntu 7.10 ("Gutsy Gibbon"), too

===Battery charge control features===
To set the thresholds for starting and stopping battery charging (in percent of current full charge capacity):
:{{cmdroot|echo 40 > /sys/devices/platform/smapi/BAT0/start_charge_thresh}}
:{{cmdroot|echo 70 > /sys/devices/platform/smapi/BAT0/stop_charge_thresh}}
:{{cmdroot|cat /sys/devices/platform/smapi/BAT0/*_charge_thresh}}
{{HINT|Battery charging thresholds can be used to keep Li-Ion and Li-Polymer batteries partially charged, in order to [[Maintenance#Battery_treatment|increase their lifetime]].}}
To prevent charging for 17 minutes (regardless of thresholds):
:{{cmdroot|echo 17 > /sys/devices/platform/smapi/BAT0/inhibit_charge_minutes}}
{{HINT|Charge inhibiting can be used to reduce the power draw of the laptop, in order to use an under-spec power supply that can't handle the combined power draw of running and charging. It can also be used to control which battery is charged when [[How to use UltraBay batteries|using an Ultrabay battery]].}}

To cancel charging preventation:
:{{cmdroot|echo 0 > /sys/devices/platform/smapi/BAT0/inhibit_charge_minutes}}

To force battery discharging (even if connected to AC):
:{{cmdroot|echo 1 > /sys/devices/platform/smapi/BAT0/force_discharge}}
{{HINT|This can be used to choose which battery is discharged when [[How to use UltraBay batteries|using an UltraBay battery]]. For example, see the {{CodeRef|tp-bat-balance}} script.}}

To cancel forced discharge:
:{{cmdroot|echo 0 > /sys/devices/platform/smapi/BAT0/force_discharge}}

====Making the settings permanent on reboot====

If you always use the same type of battery, then you may want the same settings to be configured each time you boot the machine.

If you use various types of battery, then you may want to consider writing some scripts to detect the battery type and apply the appropriate settings.

=====Debian=====

It is not necessary to create your own init.d script or modify /etc/rc.local - you just need the package sysfsutils:
:{{cmdroot|apt-get install sysfsutils}}

Now, put your desired settings in /etc/sysfs.conf:

<pre><nowiki># cat >> /etc/sysfs.conf << EOF
# For a LiIon battery in a Thinkpad
devices/platform/smapi/BAT0/start_charge_thresh = 50
devices/platform/smapi/BAT0/stop_charge_thresh = 80
EOF</nowiki></pre>

The init script supplied by sysfsutils will load these settings on each boot.

===Battery status features===
To view extended battery status such as charging state, voltage, current, capacity, cycle count and model information:

<pre>
# cat /sys/devices/platform/smapi/BAT0/installed
# cat /sys/devices/platform/smapi/BAT0/state # idle/charging/discharging
# cat /sys/devices/platform/smapi/BAT0/cycle_count
# cat /sys/devices/platform/smapi/BAT0/current_now # instantaneous current
# cat /sys/devices/platform/smapi/BAT0/current_avg # last minute average
# cat /sys/devices/platform/smapi/BAT0/power_now # instantaneous power
# cat /sys/devices/platform/smapi/BAT0/power_avg # last minute average
# cat /sys/devices/platform/smapi/BAT0/last_full_capacity
# cat /sys/devices/platform/smapi/BAT0/remaining_percent
# cat /sys/devices/platform/smapi/BAT0/remaining_running_time
# cat /sys/devices/platform/smapi/BAT0/remaining_charging_time
# cat /sys/devices/platform/smapi/BAT0/remaining_capacity
# cat /sys/devices/platform/smapi/BAT0/design_capacity
# cat /sys/devices/platform/smapi/BAT0/voltage
# cat /sys/devices/platform/smapi/BAT0/design_voltage
# cat /sys/devices/platform/smapi/BAT0/manufacturer
# cat /sys/devices/platform/smapi/BAT0/model
# cat /sys/devices/platform/smapi/BAT0/barcoding
# cat /sys/devices/platform/smapi/BAT0/chemistry
# cat /sys/devices/platform/smapi/BAT0/serial
# cat /sys/devices/platform/smapi/BAT0/manufacture_date
# cat /sys/devices/platform/smapi/BAT0/first_use_date
# cat /sys/devices/platform/smapi/BAT0/temperature # in milli-Celsius
# cat /sys/devices/platform/smapi/ac_connected
</pre>

The raw status data is also available, including some fields not listed above (in case you can figure them out):

:{{cmdroot|cat /sys/devices/platform/smapi/BAT0/dump}}

In all of the above, replace <tt>BAT0</tt> with <tt>BAT1</tt> to address the 2nd battery.

Note that the battery status readout conflicts with the stock [[HDAPS|hdaps]] driver, so if you use <tt>hdaps</tt> you will need to load <tt>tp_smapi</tt> using {{cmdroot|1=make load HDAPS=1}} (see [[#Bundled hdaps driver|Bundled hdaps driver]] below).

On [[ACPI]]-enabled systems, most of above information is also available through the files under {{path|/proc/acpi/battery}}. However, the ACPI interface does not include the instantaneous power and cycle count readouts, and does not work well when [[How to use UltraBay batteries|hotswapping UltraBay batteries]].

====Scripts====
Some scripts can make it easier to grep the information you need from tp_smapi
* [[battery.rb]]

===Other features===

There is also [[sysfs]] attribute for making direct SMAPI requests to the SM BIOS firmware. Don't touch it unless you really know what you're doing. Example:
# echo '211a 100 0 0' > /sys/devices/platform/smapi/smapi_request; cat /sys/devices/platform/smapi/smapi_request
211a 34b b2 0 0 0 'OK'
The "4b" in the 2nd value, converted to decimal, is 75: the current charging stop threshold (stop_charge_thresh).

===Bundled <tt>hdaps</tt> driver===

The tp_smapi package includes a modified version of the <tt>hdaps</tt> Linux kernel driver used by the [[HDAPS]] system. It has remained outside the mainline kernel for a few years for several reasons, [https://lists.ubuntu.com/archives/kernel-team/2009-April/005565.html] including the upstream maintainer's assertion that the new code's anonymous author was under a NDA. (Although this would not normally expose the kernel team to litigation.) [http://lkml.org/lkml/2008/9/15/126] [http://lkml.org/lkml/2008/10/7/403] [http://lkml.org/lkml/2008/10/7/428]

To use <tt>tp_smapi</tt> and <tt>hdaps</tt> concurrently, you '''must''' use the modified version.

To build the modified version, simply append the <tt>HDAPS=1</tt> parameter to the <tt>make</tt> command (see [[#Installation|Installation]] above):
:{{cmdroot|1=make load HDAPS=1}}
or
:{{cmdroot|1=make install HDAPS=1}}

If you don't do that, you will not be able to load <tt>tp_smapi</tt> (and its support module <tt>thinkpad_ec</tt>) when <tt>hdaps</tt> is loaded, and vice versa. You can use <tt>rmmod</tt> to switch between these modules.

Note that some of the battery status is also visible through ACPI ({{path|/proc/acpi/battery/*}}), independently of <tt>tp_smapi</tt>.

The modified <tt>hdaps</tt> has several changes:
* The <tt>hdaps</tt> driver in mainline kernels conflicts with the extended battery status (they use the same IO ports). The modified <tt>hdaps</tt> coordinates this access through the bundled <tt>thinkpad_ec</tt> driver.
* The modified <tt>hdaps</tt> driver fixes reliability and improves support for recent ThinkPad models (*60 and newer), since unlike the mainline driver, it correctly follows the Embedded Controller communication protocol.
* Several other improvements, such as the ability to control the polling rate.

===Troubleshooting===
==== <tt>thinkpad_ec: cannot claim io ports 0x1600-0x161f</tt> ====
The "<tt>thinkpad_ec: cannot claim io ports 0x1600-0x161f!</tt>" error message is printed when loading the <tt>thinkpad_ec</tt> module on some recent ThinkPad models. This occurs because the ACPI BIOS DSDT is reserving ports used by tp_smapi.

As a workaround, add the <tt>force_io=1</tt> module parameter to <tt>thinkpad_ec</tt> in {{path|/etc/modprobe.conf}} (or your distribution's equivalent). Add the line:
: options thinkpad_ec force_io=1

For transient testing, load the modules as follows:

: {{cmdroot|1=make load HDAPS=1 FORCE_IO=1}}

Note: force_io option was added in tp_smapi v0.40 (released 2008-12-16).

Models which need this option include:
* ThinkPad {{T400}}
* ThinkPad {{T500}}
* ThinkPad {{X301}}

More information:
* http://bugzilla.kernel.org/show_bug.cgi?id=12221
* http://www.nabble.com/thinkpad_ec-fails-to-load-on-Thinkpad-T500-td19932985.html

==== <tt>thinkpad_ec: no ThinkPad embedded controller!</tt> ====
If you get "<tt>thinkpad_ec: no ThinkPad embedded controller!</tt>" when trying to load the module on a supported model listed below, you should [[BIOS_Upgrade|upgrade your BIOS]]. Some early BIOS (like 1.x on the X31) don't handle the embedded controller.

==== <tt>T60p writing to start_charge_thresh/stop_charge_thresh does not work!</tt> ====
Writing to /sys/devices/platform/smapi/BAT0/start_charge_thresh succeeds, but the older value does not change. Solution: unknown. If you know a solution please update here.

UPDATE: Failure to effectively change sysfs values sometimes happens at boot time (through sysfs.conf OR etc/local.start for instance) when the values have never previously been changed manually (ie using echo from a shell). Try initializing the values manually before including them in boot-time scripting.

===Model-specific status===

<div style="font-size: 92%">
{| border="1" cellspacing="0" cellpadding="2"
|+<tt>tp_smapi</tt> feature support matrix
|-
! colspan=12 style="text-align:center;background:#efefef;" |
=====A series=====
|-
{{tp_smapi/model_status_table_header}}
|-
! {{A22p}} 2629-USG
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || N/A || N/A || || || ||
|-
! {{A30}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || N/A || N/A || || || ||
|-
! colspan=12 style="text-align:center;background:#efefef;" |
=====G series=====
|-
{{tp_smapi/model_status_table_header}}
|-
! {{G41}}
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || N/A || N/A || || || ||
|-
! colspan=12 style="text-align:center;background:#efefef;" |

=====R series=====
|-
{{tp_smapi/model_status_table_header}}
|-
! {{R31}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || N/A || N/A || || || || No SMAPI BIOS
|-
! {{R40}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || N/A || N/A || || || ||
|-
! {{R50}}
| {{Cunk}} || {{Cno}} || {{Cunk}} || {{Cunk}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || || ||
|-
! {{R50e}} 1834-JAG
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || N/A || N/A || || || ||
|-
! {{R50e}} 1834-5US
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || N/A || N/A || || || ||
|-
! {{R50p}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || || ||
|-
! {{R51}} 18*
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes|text=}} 0 || 0.32 || 3.22 || || Machine types 1829, 1830, 1831 and 1836
|-
! {{R51}} 28*
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || 1.29 || || Machine types 2883, 2887, 2888, 2889, 2894 and 2495
|-
! {{R52}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes|text=}} 0 || 0.33 || 1.29 || 1.06 ||
|-
! {{R60}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} ||{{Cyes}} || {{Cno|text=}} 1 || 0.33 || || ||
|-
! {{R61}}
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cyes}} ||{{Cyes}} || {{Cyes|text=}} 1 || 0.35-test1 || 7KETA7WW 2.07 || 7KHT24WW 1.08 || Machine type 8918
|-
! {{R61i}}
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cyes}} ||{{Cunk}} || {{Cunk}} || || || || Machine type 8250
|-
! {{R400}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} ||{{Cyes}} || {{Cyes|text=}} 1 || 0.40-1 || || || Machine type 7443
|-
! {{R500}}
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cyes}} ||{{Cunk}} || {{Cyes|text=}} 1 || 0.40-1 || || ||
|-
! colspan=12 style="text-align:center;background:#efefef;" |

=====T series=====
|-
{{tp_smapi/model_status_table_header}}
|-
! {{T20}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || N/A || N/A || || || || Has SMAPI BIOS but no function is supported. EC LPC3 protocol fails.
|-
! {{T22}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || N/A || N/A || || || || Has SMAPI BIOS but no function is supported. EC LPC3 protocol fails.
|-
! {{T23}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || N/A || N/A || || || ||
|-
! {{T30}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || N/A || N/A || || || ||
|-
! {{T40}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || N/A || N/A || || || ||
|-
! {{T40p}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || N/A || N/A || || || ||
|-
! {{T41}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || 0.37 || 3.23 || 3.04 ||
|-
! {{T41}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || 0.40 || 3.20 || 3.04 ||
|-
! {{T41}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || 0.40 || 3.23 || 3.04 ||
|-
! {{T41p}} 2373-AM9
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cyes}} || {{Cyes|text=}} 1 || 0.32 || 3.20 || v3.04 ||
|-
! {{T42}}
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || || ||
|-
! {{T42p}} 2373-KXU
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes|text=}} 1 || 0.32 || 3.21 || || Stop charge threshold works in Windows, but dmesg says "__get_real_thresh: cannot get stop_thresh of bat=0: Function is not supported by SMAPI BIOS".
|-
! {{T42p}} 2373-KUU
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || || ||
|-
! {{T43}} 2686
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes|text=}} 0 || 0.33 || 1.27 || ||
|-
! {{T43p}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cyes|text=}} 0 || || || ||
|-
! {{T60}}
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} 7 || 0.32 || || ||
|-
! {{T60}}
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} 1 || 0.34 || || ||
|-
! {{T60}} 1951-24G
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || 0.36 || 1.09a || ||
|-
! {{T60}} 2007-FSG
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || 0.39 || 1.10 || 1.05b ||
|-
! {{T60}} 1951-CZ1
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes|text=}} 1 || 0.40 || 2.23 || 1.07 ||
|-
! {{T60p}} 8743-CTO
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes|text=}} 1 || 0.32 || || ||
|-
! {{T61}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} 1 || 0.32 || || || [http://ubuntuforums.org/showthread.php?p=3146719 ref]
|-
! {{T61p}} 6457-7XG
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} 1 || 0.32 || || || [http://ubuntuforums.org/showthread.php?p=3146719 ref]
|-
! {{T400}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes|text=}} 1 || 0.40 || 1.19 || || Requires <tt>force_io=1</tt> parameter to <tt>thinkpad_ec</tt>
|-
! {{T400s}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes|text=}} 2 || 0.40 || 1.06 || || Requires <tt>invert=2</tt> paramteter to <tt>hdaps</tt>
|-
|-
! {{T410}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes|text=}} 1 || 0.40 || 1.25 || ||
|-
! {{T500}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes|text=}} 1 || 0.40 || 2.07 || || Requires <tt>force_io=1</tt> parameter to <tt>thinkpad_ec</tt>
|-
! {{T510}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} 7 || 0.40 || 1.12 || 1.08 || ||
|-
! colspan=12 style="text-align:center;background:#efefef;" |

=====W series=====
|-
{{tp_smapi/model_status_table_header}}
|-
! {{W700}} 2757-CTO
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || 0.40 || 2.08 || 1.05 ||
|-

! colspan=12 style="text-align:center;background:#efefef;" |

=====X series=====
|-
{{tp_smapi/model_status_table_header}}
|-
! {{X22}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || N/A || N/A || || || || no EC controller found
|-
! {{X24}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cyes}} || N/A || N/A || || || ||
|-
! {{X30}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || N/A || N/A || 0.34 || 1.09 || ||
|-
! {{X31}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cyes}} || N/A || N/A || || || ||
|-
! {{X32}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || N/A || N/A || || || ||
|-
! {{X40}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} 3 || 0.32 || 2.08 || 1.62 ||
|-
! {{X41}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} 3 || 0.32 || || ||
|-
! {{X41_Tablet}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} 3 || 0.40 || 75ET60WW (2.06 ) || 75HT20WW (1.02) ||
|-
! {{X60}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} 6 || || 2.07 || 1.10 || 2.6.20 issue (see discussion)
|-
! {{X60_Tablet}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} 3 || 0.34 || 7JET25WW (1.10 ) || 7JHT13WW 1.04 || [http://luke.no-ip.org/x60tablet/ ref] [http://rad.bioinfo.ulaval.ca/hardware/x60tablet ref]
|-
! {{X60s}} 1704-5UG
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cno|text=}} 3 || 0.34 || 7BETD2WW 2.13 || 7BHT40WW 1.13 ||
|-
! {{X60s}} 1704-56G
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cno|text=}} 3 || 0.40 || 7BETD5WW 2.16 || 7BHT40WW 1.13 ||
|-
! {{X61}} 7673-CTO
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || 0.37 || 7NETB9WW (2.19) || {{Cunk}} ||
|-
! {{X61}} 7675-CTO
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cyes}} || {{Cno|text=}} 6 || 0.35-test1 || || ||
|-
! {{X61}} 7675-4KU
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} 6 || 0.34 || 7NET30WW (1.11 ) || 7MHT24WW 1.02 ||
|-
! {{X61_Tablet}}
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} 6 || 0.32 || || ||
|-
! {{X61s}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} 6 / 3 || 0.32 || || || [http://www.slackwiki.org/ThinkPad_X61s ref] says 3 but conflicting report received
|-
! {{X100e}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || 0.40 || 6XET36WW (1.20a) || 6XHT36WW (1.176000) || x100e NTS4UTX, dual-core L625 also works (NTT27MH)
|-
! {{X200}}
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} 7 || 0.40 || 6DET40WW (2.04 ) || 7XHT22WW 1.04 ||
|-
! {{X200s}} 7470-X01
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} 5 || 0.40 || 6DET63WW (3.13) || 7XHT24WW 1.06 ||
|-
! {{X201s}}
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} 5 || 0.40 || 6QET44WW (1.14 ) || ECP: 1.09/1.09 ||
|-
! {{X300}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || 0.37 || 7TET25WW (1.02 ) || 7THT15WW 1.00c ||
|-
! colspan=12 style="text-align:center;background:#efefef;" |

=====Z series=====
|-
{{tp_smapi/model_status_table_header}}
|-
! {{Z60m}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || || ||
|-
! {{Z60t}}
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || || ||
|-
! {{Z61m}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes|text=}} 0 || 0.32 || || ||
|-
! {{Z61t}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || || || || [https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/45014 ref]
|-
! {{Z61p}}
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || || || ||
|-
! colspan=12 style="text-align:center;background:#efefef;" |

=====SL series and IdeaPad=====
|-
! colspan=12 style="text-align:left" |
The ThinkPad SL series and IdeaPad series have firmware that is completely different from other ThinkPad models. Neither [[tp_smapi]] nor [[thinkpad-acpi]] support these models.
|}
</div>

SMAPI capabilities may depend on the BIOS version as well, so upgrading to the latest version of the BIOS might provide more SMAPI functions (especially true for long-lived BIOS with lots of releases, like the TP-1R).

Please update the above and report your experience on the [[Talk:tp_smapi|discussion]] page. If the module loads but gives a "<tt>not supported</tt>" or "<tt>not implementeded</tt>" error when you try to use some specific file in {{path|/sys/devices/platform/smapi/}}, please report the <tt>dmesg</tt> output and whether the corresponding functionality is available under Windows - maybe your ThinkPad just can't do that.

While at it, you may also want to add your laptop to the [[list of DMI IDs]].

=====HDAPS axis orientation=====
<sup>1</sup> The HDAPS axis orientation is set using the <tt>invert</tt> module parameter (at load time) or sysfs attribute (at runtime). The <tt>hdaps</tt> driver of tp_smapi supports all 8 possible sensor orientations (inversion and swapping). You can use [[HDAPS#Visualisation_of_ThinkPad_orientation|hdaps visualisation]] to check if the settings is correct.

The <tt>invert</tt> parameter is an integer between 0 and 7, whose meaning is defined below. (This is confusing. Most people will find it easier to just try all 8 possibilities.)

Let <tt>X</tt> and <tt>Y</tt> denote the hardware readouts. Let <tt>R</tt> denote the laptop's roll (tilt left/right), and let <tt>P</tt> denote the laptop's pitch (tilt forward/backward). The possible values are as follows:
invert=0: R= X P= Y (same as mainline)
invert=1: R=-X P=-Y (same as mainline)
invert=2: R=-X P= Y (new)
invert=3: R= X P=-Y (new)
invert=4: R= Y P= X (new)
invert=5: R=-Y P=-X (new)
invert=6: R=-Y P= X (new)
invert=7: R= Y P=-X (new)

[[Category:Drivers]] [[Category:Patches]]

===Tools using this driver===

The driver's interface can be accessed directly through the files under {{path|/sys/devices/platform/smapi}}, or via the following tools:
* [[KThinkBat]] - display battery status on the KDE <tt>kicker</tt> panel.
* [[gkrellm-ThinkBat]] - battery status plugin for Gkrellm2
* {{CodeRef|thinkpad-smapi.sh}} - script to display various SMAPI information using tp_smapi module.

== Headline text ==

Tp smapi

2010-06-23T17:41:32Z

BDKMPSS: /* X series */ add my X200s,

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
The <tt>tp_smapi</tt> kernel module exposes some features of the ThinkPad hardware/firmware via a <tt>sysfs</tt> interface. Currently, the main implemented functionality is control of battery charging and extended battery status. The tp_smapi software package also includes an improved version of the [[HDAPS]] driver. The underlying hardware interfaces are [[SMAPI support for Linux|SMAPI]] and direct access to the embedded controller.

This driver uses undocumented features and direct hardware access, so it may work unreliably or even damage your hardware; but so far no such damage has been reported.
|}

===Features===
*<tt>tp_smapi</tt> driver
**Battery charge/discharge control
**Battery status information
*<tt>hdaps</tt> driver (compared with the standard <tt>hdaps</tt> driver)
**Improved stability
**Improved model support
**Improved functionality

===Project Homepage / Availability===
* Project page: http://tpctl.sourceforge.net/
* Download page: http://sourceforge.net/projects/tpctl/files/tp_smapi
* You need to download only the <i>tp_smapi</i> package.

===Installation===
====Installation from source====
You will need the kernel headers and makefiles corresponding to your current kernel version. On {{Fedora}}, this means {{cmdroot|yum install kernel-devel-$(uname -r)}} .

:{{cmdroot|tar xzvf tp_smapi-0.40.tgz}}
:{{cmdroot|cd tp_smapi-0.40}}

Then, either compile and load the driver within the current working directory (for testing):
:{{cmdroot|make load}}
OR compile and install into the kernel's module path:
:{{cmdroot|make install}}

If you use the [[HDAPS]] driver, add <tt>HDAPS=1</tt> to also patch the <tt>hdaps</tt> for compatibility with <tt>tp_smapi</tt> (this requires a kernel source tree matching the current kernel).
Again, either load the driver within the current working directory:
:{{cmdroot|1=make load HDAPS=1}}
OR install into the kernel's module path:
:{{cmdroot|1=make install HDAPS=1}}

To prepare a stand-alone patch against the current kernel tree (including
a patch against <tt>hdaps</tt> and new <tt>Kconfig</tt> entries):
:{{cmdroot|make patch}}

To delete all autogenerated files:
:{{cmdroot|make clean}}

The original kernel tree is never modified by any these commands.
The {{path|/lib/modules}} directory is modified only by {{cmdroot|make install}}.

====Installation in Gentoo====
The {{Gentoo}} portage system carries a [http://packages.gentoo.org/package/app-laptop/tp_smapi tp_smapi package], which follows the latest version pretty closely. On a Gentoo system, you can install and load as follows.

If you use the [[HDAPS]] driver, do this first:

* Disable the <tt>hdaps</tt> module in your kernel configuration (Device Drivers → Hardware Monitoring Support → IBM Hard Drive Active Protection System)
* Rebuild and install the kernel
* Add the <tt>hdaps</tt> use flag in {{path|/etc/make.conf}}
* {{cmdroot|rmmod hdaps}}

Then:
* {{cmdroot|emerge tp_smapi}} (or install tp_smapi with hdaps support manually, as above)
* {{cmdroot|echo "tp_smapi" >> /etc/modules.autoload.d/kernel-2.6}}
* {{cmdroot|echo "hdaps" >> /etc/modules.autoload.d/kernel-2.6}}

Then reboot, or run:
* {{cmdroot|modprobe tp_smapi}}
* {{cmdroot|modprobe hdaps}}

'''NOTE:''' If {{cmdroot|modprobe}} fails and dmesg says something about <tt>__stack_chk_fail()</tt>, you probably just compiled your modules with <tt>-fstack-protector</tt> and/or <tt>-fstack-protector-all</tt> without having a kernel that supports it. You can either configure your kernel to have <tt>CC_STACKPROTECTOR</tt> enabled (in ''Processor type and features'' if you use {{cmdroot|make menuconfig}}) or edit your <tt>make.conf</tt> (or, if you're using paludis, your <tt>/etc/paludis/bashrc</tt>) and remove <tt>-fstack-protector</tt> and <tt>-fstack-protector-all</tt> from your <tt>CFLAGS</tt>. If you choose to enable it in the kernel, be aware that you need a patched GCC for it (and I do not know if the gcc in stage3 is patched).

====Installation on Debian unstable (sid), testing (squeeze) or stable (lenny)====
Debian now contains the [http://packages.debian.org/tp-smapi packaged module source] and prebuilt modules for Debian kernels.

If you use a stock Debian kernel, you can install the tp_smapi modules with:
* {{cmdroot|apt-get install tp-smapi-modules-`uname -r`}}
* in order to make sure the modules package is kept in sync with the kernel one, you may also want to install the <code>tm-smapi-modules-2.6-686</code> or <code>tm-smapi-modules-2.6-amd64</code> package, depending on your architecture

If you use a custom kernel, you can build tp_smapi with module-assistant:
* {{cmdroot|aptitude install tp-smapi-source}}
* {{cmdroot|m-a -t a-i tp-smapi}}

====Installation on openSUSE====
openSUSE provides rpm packages. Look for them at the package search: [http://software.opensuse.org/search/], search for the package named "tp_smapi".

A step-by-step guide on how a relative linux newbie installed tp_smapi on a Thinkpad W500 running openSuse 11.1 using YAST Software Manager is available [http://forums.opensuse.org/hardware/laptop/417254-tp_smapi-lenovo-thinkpad-t400-t500-w500-step-step.html#post2005932 here]

In case you are taking the hard way around, while compiling on 11.0, make complained about not being able to locate the kernel sources. It worked for me after I did this:
<pre><nowiki>cp /usr/include/linux/aio_abi.h /lib/modules/`uname -r`/build/include/linux/</nowiki></pre>

====Installation on Ubuntu====
Ubuntu ships tp_smapi in their <tt>linux-ubuntu-modules-*</tt> package for Hardy, so you don't have to build it yourself. Please note that they have renamed tp_smapi's modified <tt>hdaps</tt> module to <tt>hdaps_ec</tt> so that the two can coexist. You should load <tt>hdaps_ec</tt>, not <tt>hdaps</tt>.

Ubuntu Intrepid and Jaunty, however, lack the <tt>hdaps_ec</tt> module, as reported [https://bugs.launchpad.net/ubuntu/+source/linux/+bug/297213 here]. It will not be included again until said [[#Bundled hdaps driver|bundled hdaps driver]] is merged into mainline.

=====Installation on Ubuntu Jaunty=====
I have posted my experiences [http://meandmyubuntu.blogspot.com/2009/05/getting-hdasp-to-work-on-jaunty.html here]

=====Installation on Ubuntu Karmic=====
Ubuntu does not ship the precompiled module tp_smapi any more. However the source code is still present in the repository. It can be installed through module-assistant :
:{{cmdroot|aptitude install tp-smapi-source}}
:{{cmdroot|module-assistant prepare tp-smapi}}
:{{cmdroot|module-assistant auto-install tp-smapi}}
:{{cmdroot|modprobe tp-smapi}}

=====Installation on Ubuntu Lucid=====
The Karmic solution above works well.

As an alternative, one can use the dkms flavour of the packages via
:{{cmdroot|aptitude install tp-smapi-dkms}}
:{{cmdroot|modprobe tp_smapi}}

====Installation on older Ubuntu/Debian====
Installation on Ubuntu or Debian is quite easy, but there are a few things to look after:

To get your system ready for compiling code, install the build-essentials (as root, of course, as all of the following comands; Ubuntu users have to prepend 'sudo' to every line and enter their own password when prompted):
<pre><nowiki>apt-get install build-essential</nowiki></pre>

To get tp_smapi to work, obtain the latest source as mentioned above and unpack it. If you want to use HDAPS, you need to install the kernel source matching te kernel you are running. To do so, issue this:
<pre><nowiki>uname -r</nowiki></pre>
This will give you the version of your current kernel.
Debian users execute the following:
<pre><nowiki>apt-get install linux-source-`uname -r`</nowiki></pre>
Ubuntu users execute the following using the kernel-version only (exclude -XX-generic; e.g. 'linux-source-2.6.20'):
<pre><nowiki>apt-get install linux-source-`uname -r`</nowiki></pre>

Be sure to unpack the source file. The easiest way is to open Nautilus as root:
<pre><nowiki>sudo nautilus</nowiki></pre>
Then browse to /usr/src/ and extract the source file to that directory.

Now change to the tp_smapi dir:
<pre><nowiki>cd tp_smapi-X.YY</nowiki></pre> (X.YY being the version-number of [[tp_smapi]])
and make and install tp_smapi as instructed above.

If you get an error that the kernel version isn't matching (or that you need to set KSRC/KBUILD), please check that there is a symlink from the modules dir to the kernel source:
<pre><nowiki>root@localhost:~#ls -l /lib/modules/2.6.20-16-generic
lrwxrwxrwx 1 root root 28 2007-02-02 08:39 build -> /usr/src/linux-source-2.6.20</nowiki></pre>
Create the link if the line above does not exist:
<pre><nowiki>root@localhost:~#ln -s /usr/src/linux-source-2.6.20 /lib/modules/2.6.20-16-generic/build</nowiki></pre>

Now the following will build and install the correct modules to their locations:
<pre><nowiki>make install HDAPS=1</nowiki></pre>
To make sure your system loads the modules at boot time, do this:
<pre><nowiki>echo "tp_smapi" >> /etc/modules
echo "hdaps" >> /etc/modules</nowiki></pre>
and update your initramfs:
<pre><nowiki>update-initramfs -u</nowiki></pre>

To get tp_smapi running now, just load the modules:
<pre><nowiki>modprobe -a tp_smapi hdaps</nowiki></pre>

This description was tested on Kubuntu 'Feisty Fawn' and should work on all Debian-based distros with minor tweaks.

'''EDIT:''' Works on Kubuntu 7.10 ("Gutsy Gibbon"), too

===Battery charge control features===
To set the thresholds for starting and stopping battery charging (in percent of current full charge capacity):
:{{cmdroot|echo 40 > /sys/devices/platform/smapi/BAT0/start_charge_thresh}}
:{{cmdroot|echo 70 > /sys/devices/platform/smapi/BAT0/stop_charge_thresh}}
:{{cmdroot|cat /sys/devices/platform/smapi/BAT0/*_charge_thresh}}
{{HINT|Battery charging thresholds can be used to keep Li-Ion and Li-Polymer batteries partially charged, in order to [[Maintenance#Battery_treatment|increase their lifetime]].}}
To prevent charging for 17 minutes (regardless of thresholds):
:{{cmdroot|echo 17 > /sys/devices/platform/smapi/BAT0/inhibit_charge_minutes}}
{{HINT|Charge inhibiting can be used to reduce the power draw of the laptop, in order to use an under-spec power supply that can't handle the combined power draw of running and charging. It can also be used to control which battery is charged when [[How to use UltraBay batteries|using an Ultrabay battery]].}}

To cancel charging preventation:
:{{cmdroot|echo 0 > /sys/devices/platform/smapi/BAT0/inhibit_charge_minutes}}

To force battery discharging (even if connected to AC):
:{{cmdroot|echo 1 > /sys/devices/platform/smapi/BAT0/force_discharge}}
{{HINT|This can be used to choose which battery is discharged when [[How to use UltraBay batteries|using an UltraBay battery]]. For example, see the {{CodeRef|tp-bat-balance}} script.}}

To cancel forced discharge:
:{{cmdroot|echo 0 > /sys/devices/platform/smapi/BAT0/force_discharge}}

====Making the settings permanent on reboot====

If you always use the same type of battery, then you may want the same settings to be configured each time you boot the machine.

If you use various types of battery, then you may want to consider writing some scripts to detect the battery type and apply the appropriate settings.

=====Debian=====

It is not necessary to create your own init.d script or modify /etc/rc.local - you just need the package sysfsutils:
:{{cmdroot|apt-get install sysfsutils}}

Now, put your desired settings in /etc/sysfs.conf:

<pre><nowiki># cat >> /etc/sysfs.conf << EOF
# For a LiIon battery in a Thinkpad
devices/platform/smapi/BAT0/start_charge_thresh = 50
devices/platform/smapi/BAT0/stop_charge_thresh = 80
EOF</nowiki></pre>

The init script supplied by sysfsutils will load these settings on each boot.

===Battery status features===
To view extended battery status such as charging state, voltage, current, capacity, cycle count and model information:

<pre>
# cat /sys/devices/platform/smapi/BAT0/installed
# cat /sys/devices/platform/smapi/BAT0/state # idle/charging/discharging
# cat /sys/devices/platform/smapi/BAT0/cycle_count
# cat /sys/devices/platform/smapi/BAT0/current_now # instantaneous current
# cat /sys/devices/platform/smapi/BAT0/current_avg # last minute average
# cat /sys/devices/platform/smapi/BAT0/power_now # instantaneous power
# cat /sys/devices/platform/smapi/BAT0/power_avg # last minute average
# cat /sys/devices/platform/smapi/BAT0/last_full_capacity
# cat /sys/devices/platform/smapi/BAT0/remaining_percent
# cat /sys/devices/platform/smapi/BAT0/remaining_running_time
# cat /sys/devices/platform/smapi/BAT0/remaining_charging_time
# cat /sys/devices/platform/smapi/BAT0/remaining_capacity
# cat /sys/devices/platform/smapi/BAT0/design_capacity
# cat /sys/devices/platform/smapi/BAT0/voltage
# cat /sys/devices/platform/smapi/BAT0/design_voltage
# cat /sys/devices/platform/smapi/BAT0/manufacturer
# cat /sys/devices/platform/smapi/BAT0/model
# cat /sys/devices/platform/smapi/BAT0/barcoding
# cat /sys/devices/platform/smapi/BAT0/chemistry
# cat /sys/devices/platform/smapi/BAT0/serial
# cat /sys/devices/platform/smapi/BAT0/manufacture_date
# cat /sys/devices/platform/smapi/BAT0/first_use_date
# cat /sys/devices/platform/smapi/BAT0/temperature # in milli-Celsius
# cat /sys/devices/platform/smapi/ac_connected
</pre>

The raw status data is also available, including some fields not listed above (in case you can figure them out):

:{{cmdroot|cat /sys/devices/platform/smapi/BAT0/dump}}

In all of the above, replace <tt>BAT0</tt> with <tt>BAT1</tt> to address the 2nd battery.

Note that the battery status readout conflicts with the stock [[HDAPS|hdaps]] driver, so if you use <tt>hdaps</tt> you will need to load <tt>tp_smapi</tt> using {{cmdroot|1=make load HDAPS=1}} (see [[#Bundled hdaps driver|Bundled hdaps driver]] below).

On [[ACPI]]-enabled systems, most of above information is also available through the files under {{path|/proc/acpi/battery}}. However, the ACPI interface does not include the instantaneous power and cycle count readouts, and does not work well when [[How to use UltraBay batteries|hotswapping UltraBay batteries]].

====Scripts====
Some scripts can make it easier to grep the information you need from tp_smapi
* [[battery.rb]]

===Other features===

There is also [[sysfs]] attribute for making direct SMAPI requests to the SM BIOS firmware. Don't touch it unless you really know what you're doing. Example:
# echo '211a 100 0 0' > /sys/devices/platform/smapi/smapi_request; cat /sys/devices/platform/smapi/smapi_request
211a 34b b2 0 0 0 'OK'
The "4b" in the 2nd value, converted to decimal, is 75: the current charging stop threshold (stop_charge_thresh).

===Bundled <tt>hdaps</tt> driver===

The tp_smapi package includes a modified version of the <tt>hdaps</tt> Linux kernel driver used by the [[HDAPS]] system. It has remained outside the mainline kernel for a few years for several reasons, [https://lists.ubuntu.com/archives/kernel-team/2009-April/005565.html] including the upstream maintainer's assertion that the new code's anonymous author was under a NDA. (Although this would not normally expose the kernel team to litigation.) [http://lkml.org/lkml/2008/9/15/126] [http://lkml.org/lkml/2008/10/7/403] [http://lkml.org/lkml/2008/10/7/428]

To use <tt>tp_smapi</tt> and <tt>hdaps</tt> concurrently, you '''must''' use the modified version.

To build the modified version, simply append the <tt>HDAPS=1</tt> parameter to the <tt>make</tt> command (see [[#Installation|Installation]] above):
:{{cmdroot|1=make load HDAPS=1}}
or
:{{cmdroot|1=make install HDAPS=1}}

If you don't do that, you will not be able to load <tt>tp_smapi</tt> (and its support module <tt>thinkpad_ec</tt>) when <tt>hdaps</tt> is loaded, and vice versa. You can use <tt>rmmod</tt> to switch between these modules.

Note that some of the battery status is also visible through ACPI ({{path|/proc/acpi/battery/*}}), independently of <tt>tp_smapi</tt>.

The modified <tt>hdaps</tt> has several changes:
* The <tt>hdaps</tt> driver in mainline kernels conflicts with the extended battery status (they use the same IO ports). The modified <tt>hdaps</tt> coordinates this access through the bundled <tt>thinkpad_ec</tt> driver.
* The modified <tt>hdaps</tt> driver fixes reliability and improves support for recent ThinkPad models (*60 and newer), since unlike the mainline driver, it correctly follows the Embedded Controller communication protocol.
* Several other improvements, such as the ability to control the polling rate.

===Troubleshooting===
==== <tt>thinkpad_ec: cannot claim io ports 0x1600-0x161f</tt> ====
The "<tt>thinkpad_ec: cannot claim io ports 0x1600-0x161f!</tt>" error message is printed when loading the <tt>thinkpad_ec</tt> module on some recent ThinkPad models. This occurs because the ACPI BIOS DSDT is reserving ports used by tp_smapi.

As a workaround, add the <tt>force_io=1</tt> module parameter to <tt>thinkpad_ec</tt> in {{path|/etc/modprobe.conf}} (or your distribution's equivalent). Add the line:
: options thinkpad_ec force_io=1

For transient testing, load the modules as follows:

: {{cmdroot|1=make load HDAPS=1 FORCE_IO=1}}

Note: force_io option was added in tp_smapi v0.40 (released 2008-12-16).

Models which need this option include:
* ThinkPad {{T400}}
* ThinkPad {{T500}}
* ThinkPad {{X301}}

More information:
* http://bugzilla.kernel.org/show_bug.cgi?id=12221
* http://www.nabble.com/thinkpad_ec-fails-to-load-on-Thinkpad-T500-td19932985.html

==== <tt>thinkpad_ec: no ThinkPad embedded controller!</tt> ====
If you get "<tt>thinkpad_ec: no ThinkPad embedded controller!</tt>" when trying to load the module on a supported model listed below, you should [[BIOS_Upgrade|upgrade your BIOS]]. Some early BIOS (like 1.x on the X31) don't handle the embedded controller.

==== <tt>T60p writing to start_charge_thresh/stop_charge_thresh does not work!</tt> ====
Writing to /sys/devices/platform/smapi/BAT0/start_charge_thresh succeeds, but the older value does not change. Solution: unknown. If you know a solution please update here.

UPDATE: Failure to effectively change sysfs values sometimes happens at boot time (through sysfs.conf OR etc/local.start for instance) when the values have never previously been changed manually (ie using echo from a shell). Try initializing the values manually before including them in boot-time scripting.

===Model-specific status===

<div style="font-size: 92%">
{| border="1" cellspacing="0" cellpadding="2"
|+<tt>tp_smapi</tt> feature support matrix
|-
! colspan=12 style="text-align:center;background:#efefef;" |
=====A series=====
|-
{{tp_smapi/model_status_table_header}}
|-
! {{A22p}} 2629-USG
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || N/A || N/A || || || ||
|-
! {{A30}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || N/A || N/A || || || ||
|-
! colspan=12 style="text-align:center;background:#efefef;" |
=====G series=====
|-
{{tp_smapi/model_status_table_header}}
|-
! {{G41}}
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || N/A || N/A || || || ||
|-
! colspan=12 style="text-align:center;background:#efefef;" |

=====R series=====
|-
{{tp_smapi/model_status_table_header}}
|-
! {{R31}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || N/A || N/A || || || || No SMAPI BIOS
|-
! {{R40}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || N/A || N/A || || || ||
|-
! {{R50}}
| {{Cunk}} || {{Cno}} || {{Cunk}} || {{Cunk}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || || ||
|-
! {{R50e}} 1834-JAG
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || N/A || N/A || || || ||
|-
! {{R50e}} 1834-5US
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || N/A || N/A || || || ||
|-
! {{R50p}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || || ||
|-
! {{R51}} 18*
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes|text=}} 0 || 0.32 || 3.22 || || Machine types 1829, 1830, 1831 and 1836
|-
! {{R51}} 28*
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || 1.29 || || Machine types 2883, 2887, 2888, 2889, 2894 and 2495
|-
! {{R52}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes|text=}} 0 || 0.33 || 1.29 || 1.06 ||
|-
! {{R60}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} ||{{Cyes}} || {{Cno|text=}} 1 || 0.33 || || ||
|-
! {{R61}}
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cyes}} ||{{Cyes}} || {{Cyes|text=}} 1 || 0.35-test1 || 7KETA7WW 2.07 || 7KHT24WW 1.08 || Machine type 8918
|-
! {{R61i}}
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cyes}} ||{{Cunk}} || {{Cunk}} || || || || Machine type 8250
|-
! {{R400}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} ||{{Cyes}} || {{Cyes|text=}} 1 || 0.40-1 || || || Machine type 7443
|-
! {{R500}}
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cyes}} ||{{Cunk}} || {{Cyes|text=}} 1 || 0.40-1 || || ||
|-
! colspan=12 style="text-align:center;background:#efefef;" |

=====T series=====
|-
{{tp_smapi/model_status_table_header}}
|-
! {{T20}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || N/A || N/A || || || || Has SMAPI BIOS but no function is supported. EC LPC3 protocol fails.
|-
! {{T22}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || N/A || N/A || || || || Has SMAPI BIOS but no function is supported. EC LPC3 protocol fails.
|-
! {{T23}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || N/A || N/A || || || ||
|-
! {{T30}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || N/A || N/A || || || ||
|-
! {{T40}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || N/A || N/A || || || ||
|-
! {{T40p}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || N/A || N/A || || || ||
|-
! {{T41}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || 0.37 || 3.23 || 3.04 ||
|-
! {{T41}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || 0.40 || 3.20 || 3.04 ||
|-
! {{T41}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || 0.40 || 3.23 || 3.04 ||
|-
! {{T41p}} 2373-AM9
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cyes}} || {{Cyes|text=}} 1 || 0.32 || 3.20 || v3.04 ||
|-
! {{T42}}
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || || ||
|-
! {{T42p}} 2373-KXU
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes|text=}} 1 || 0.32 || 3.21 || || Stop charge threshold works in Windows, but dmesg says "__get_real_thresh: cannot get stop_thresh of bat=0: Function is not supported by SMAPI BIOS".
|-
! {{T42p}} 2373-KUU
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || || ||
|-
! {{T43}} 2686
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes|text=}} 0 || 0.33 || 1.27 || ||
|-
! {{T43p}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cyes|text=}} 0 || || || ||
|-
! {{T60}}
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} 7 || 0.32 || || ||
|-
! {{T60}}
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} 1 || 0.34 || || ||
|-
! {{T60}} 1951-24G
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || 0.36 || 1.09a || ||
|-
! {{T60}} 2007-FSG
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || 0.39 || 1.10 || 1.05b ||
|-
! {{T60}} 1951-CZ1
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes|text=}} 1 || 0.40 || 2.23 || 1.07 ||
|-
! {{T60p}} 8743-CTO
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes|text=}} 1 || 0.32 || || ||
|-
! {{T61}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} 1 || 0.32 || || || [http://ubuntuforums.org/showthread.php?p=3146719 ref]
|-
! {{T61p}} 6457-7XG
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} 1 || 0.32 || || || [http://ubuntuforums.org/showthread.php?p=3146719 ref]
|-
! {{T400}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes|text=}} 1 || 0.40 || 1.19 || || Requires <tt>force_io=1</tt> parameter to <tt>thinkpad_ec</tt>
|-
! {{T400s}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes|text=}} 2 || 0.40 || 1.06 || || Requires <tt>invert=2</tt> paramteter to <tt>hdaps</tt>
|-
|-
! {{T410}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes|text=}} 1 || 0.40 || 1.25 || ||
|-
! {{T500}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes|text=}} 1 || 0.40 || 2.07 || || Requires <tt>force_io=1</tt> parameter to <tt>thinkpad_ec</tt>
|-
! {{T510}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} 7 || 0.40 || 1.12 || 1.08 || ||
|-
! colspan=12 style="text-align:center;background:#efefef;" |

=====W series=====
|-
{{tp_smapi/model_status_table_header}}
|-
! {{W700}} 2757-CTO
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || 0.40 || 2.08 || 1.05 ||
|-

! colspan=12 style="text-align:center;background:#efefef;" |

=====X series=====
|-
{{tp_smapi/model_status_table_header}}
|-
! {{X22}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || N/A || N/A || || || || no EC controller found
|-
! {{X24}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cyes}} || N/A || N/A || || || ||
|-
! {{X30}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || N/A || N/A || 0.34 || 1.09 || ||
|-
! {{X31}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cyes}} || N/A || N/A || || || ||
|-
! {{X32}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || N/A || N/A || || || ||
|-
! {{X40}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} 3 || 0.32 || 2.08 || 1.62 ||
|-
! {{X41}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} 3 || 0.32 || || ||
|-
! {{X41_Tablet}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} (see ref) || 0.32 || || [http://sourceforge.net/mailarchive/message.php?msg_name=4757BD30.8080808%40ugcs.caltech.edu ref] ||
|-
! {{X60}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} 6 || || 2.07 || 1.10 || 2.6.20 issue (see discussion)
|-
! {{X60_Tablet}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} 3 || 0.34 || 7JET25WW (1.10 ) || 7JHT13WW 1.04 || [http://luke.no-ip.org/x60tablet/ ref] [http://rad.bioinfo.ulaval.ca/hardware/x60tablet ref]
|-
! {{X60s}} 1704-5UG
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cno|text=}} 3 || 0.34 || 7BETD2WW 2.13 || 7BHT40WW 1.13 ||
|-
! {{X60s}} 1704-56G
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cno|text=}} 3 || 0.40 || 7BETD5WW 2.16 || 7BHT40WW 1.13 ||
|-
! {{X61}} 7673-CTO
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || 0.37 || 7NETB9WW (2.19) || {{Cunk}} ||
|-
! {{X61}} 7675-CTO
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cyes}} || {{Cno|text=}} 6 || 0.35-test1 || || ||
|-
! {{X61}} 7675-4KU
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} 6 || 0.34 || 7NET30WW (1.11 ) || 7MHT24WW 1.02 ||
|-
! {{X61_Tablet}}
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} 6 || 0.32 || || ||
|-
! {{X61s}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} 6 / 3 || 0.32 || || || [http://www.slackwiki.org/ThinkPad_X61s ref] says 3 but conflicting report received
|-
! {{X100e}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || 0.40 || 6XET36WW (1.20a) || 6XHT36WW (1.176000) || x100e NTS4UTX, dual-core L625 also works (NTT27MH)
|-
! {{X200}}
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} 7 || 0.40 || 6DET40WW (2.04 ) || 7XHT22WW 1.04 ||
|-
! {{X200s}} 7470-X01
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} 5 || 0.40 || 6DET40WW (3.13 ) || 7XHT22WW 1.06 ||
|-
! {{X201s}}
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} 5 || 0.40 || 6QET44WW (1.14 ) || ECP: 1.09/1.09 ||
|-
! {{X300}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || 0.37 || 7TET25WW (1.02 ) || 7THT15WW 1.00c ||
|-
! colspan=12 style="text-align:center;background:#efefef;" |

=====Z series=====
|-
{{tp_smapi/model_status_table_header}}
|-
! {{Z60m}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || || ||
|-
! {{Z60t}}
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || || ||
|-
! {{Z61m}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes|text=}} 0 || 0.32 || || ||
|-
! {{Z61t}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || || || || [https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/45014 ref]
|-
! {{Z61p}}
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || || || ||
|-
! colspan=12 style="text-align:center;background:#efefef;" |

=====SL series and IdeaPad=====
|-
! colspan=12 style="text-align:left" |
The ThinkPad SL series and IdeaPad series have firmware that is completely different from other ThinkPad models. Neither [[tp_smapi]] nor [[thinkpad-acpi]] support these models.
|}
</div>

SMAPI capabilities may depend on the BIOS version as well, so upgrading to the latest version of the BIOS might provide more SMAPI functions (especially true for long-lived BIOS with lots of releases, like the TP-1R).

Please update the above and report your experience on the [[Talk:tp_smapi|discussion]] page. If the module loads but gives a "<tt>not supported</tt>" or "<tt>not implementeded</tt>" error when you try to use some specific file in {{path|/sys/devices/platform/smapi/}}, please report the <tt>dmesg</tt> output and whether the corresponding functionality is available under Windows - maybe your ThinkPad just can't do that.

While at it, you may also want to add your laptop to the [[list of DMI IDs]].

=====HDAPS axis orientation=====
<sup>1</sup> The HDAPS axis orientation is set using the <tt>invert</tt> module parameter (at load time) or sysfs attribute (at runtime). The <tt>hdaps</tt> driver of tp_smapi supports all 8 possible sensor orientations (inversion and swapping). You can use [[HDAPS#Visualisation_of_ThinkPad_orientation|hdaps visualisation]] to check if the settings is correct.

The <tt>invert</tt> parameter is an integer between 0 and 7, whose meaning is defined below. (This is confusing. Most people will find it easier to just try all 8 possibilities.)

Let <tt>X</tt> and <tt>Y</tt> denote the hardware readouts. Let <tt>R</tt> denote the laptop's roll (tilt left/right), and let <tt>P</tt> denote the laptop's pitch (tilt forward/backward). The possible values are as follows:
invert=0: R= X P= Y (same as mainline)
invert=1: R=-X P=-Y (same as mainline)
invert=2: R=-X P= Y (new)
invert=3: R= X P=-Y (new)
invert=4: R= Y P= X (new)
invert=5: R=-Y P=-X (new)
invert=6: R=-Y P= X (new)
invert=7: R= Y P=-X (new)

[[Category:Drivers]] [[Category:Patches]]

===Tools using this driver===

The driver's interface can be accessed directly through the files under {{path|/sys/devices/platform/smapi}}, or via the following tools:
* [[KThinkBat]] - display battery status on the KDE <tt>kicker</tt> panel.
* [[gkrellm-ThinkBat]] - battery status plugin for Gkrellm2
* {{CodeRef|thinkpad-smapi.sh}} - script to display various SMAPI information using tp_smapi module.

== Headline text ==

Talk:Intel PRO/Wireless 2915ABG Mini-PCI Adapter

2009-04-03T17:48:19Z

BDKMPSS: /* Card habitually loses connection unlss using WEP */ works @ X31 @ Fedora

__TOC__

==Linux ==

Hello,

Could anybody please confirm that the ipw2200 driver works for that card?

Thanks

-- [[User:Oub|Oub]] 18:46, 23 March 2006 (CET)
----

Yes, it does. You should always use Intel's latest stable version, though, and not whatever happened to come with the distribution kernel you're using. Usually the very latest development drivers from Intel are good as well.

-- [[User:Hmh|hmh]] 2006-03-24 12:07 UTC-0300

==Difference to 2200?==
Is it correct, that the only difference between 2200 and 2915 is the 802.11a which is supported by 2915? Does the possible a-mode needs more power (so a 2915 needs more than a 2200 while connected to the same g-network)? --[[User:Zhenech|Zhenech]] 14:18, 11 May 2007 (CEST)

== Does this card really work in an X24? ==

I bought a card from a parts distributer, Option 27K9936, but after installing it, Windows finds the card and installs the drivers but says "This device cannot start (10)". I have tried both the latest Intel and IBM supplied drivers, and neither seem to help. I have also tried updating to the latest BIOS version as well.

== Card habitually loses connection unlss using WEP ==

I've just got an X32 with this card installed, latest drivers on XP Pro SP3. It frequently loses connection with a Linksys WRT54G router using anything but WEP. Wondering if anyone else has encountered unreliability with this card for more sophisticated encryption protocols (WPA, WPA2)? Thanks.... -- [[User:Davidspalding|Davidspalding]] 14:48, 3 April 2009 (UTC)

I use this card in my X31, which is the same machine except for the CPU, running Fedora 10 and it works with no encryption, WEP, WPA and WPA2 without any problem. Maybe its a problem between the router and your System or a Problem of Windows/Drivers.
--[[User:BDKMPSS|BDKMPSS]] 17:48, 3 April 2009 (UTC)

User:BDKMPSS

2009-02-21T23:12:12Z

BDKMPSS: /* my ThinkPad Workstation */ minor fixup

==my ThinkPad '''''Workstation'''''==
ThinkPad [[:Category:X31|X31]] (Model: 2672-C2G) running [[:Category:Debian|Debian]] Testing

===Default Features===
* Intel Pentium M 1.4
* 256 MB PC2100
* 40GB Hitachi HDD
* Intel 10/100 Ethernet controller (PXE boot enabled)
* CDC slot with Modem Daughter Card (MDC)
* MiniPCI slot with Intel PRO/Wireless LAN 2100 3B Mini PCI Adapter

===Changed/Upgraded to/with:===
* Intel Pentium M 1.4 undervolted
* 2 GB DDR 400 RAM (Kingston KVR400X64SC3A/1G) running at 266MHz
* 160 GB Hitachi TravelStar 5K160 (HTS541616J9AT00)
* Intel Pro/Wireless 2915 ABG MiniPCI card
* Modem Daughter Card (MDC) removed
* PXE boot via Bios disabled
* latest BIOS/EC-Frimware (3.02/1.08)

===why I have chosen/stick to this very model===
I think this is may the last Thinkpad purchase I ever made, not because I don't like it, actually I love it, but I don't like these "newer ones" (ThinkPad X40 and higher).

For me this this very model was/is the (second) last '''''perfect''''' one, so I never got a newer one and the last known good, the X32, is not a update which is really enhancing.
My X31 is '''''very solid''''', '''''ultraportable''''' and '''''fast enough''''' for the "office" stuff I do with it.

This is partly may also featured by the newer ones, but I miss some things of my X31 '''''very''''' much on them:
*the port-layout is much better than the "newer one". I hate ports on the sides especially on the right one, and all newer ones have all ports there...
*the battery in the back makes the newer ones sort of unbalanced and causes these port-layout problems
*the LCD cover with this thick, wide, "salient" borders is absolutely robust and "unbreakable". Or at least feels like this ;)
*the overall case feels much better engineered, like I could walk over it without doing any damage, the newer ones just don't feel like this (no I am not going to try it)
*its one of the last fully IBM engineered ones
*even if at first seemed like Lenovo could keep up the "legendary" quality, or even increase it to the old "pre-outsourcing" level, it now seems like this was wishful thinking

Pentium M undervolting and underclocking

2008-12-07T23:10:51Z

BDKMPSS: correct indentation and some minor changes on my reported values

== Background ==

Intel Pentium M processors from the [[Intel Pentium M (Dothan)|Dothan]] and [[Intel Pentium M (Banias)|Banias]] families can be instructed to operate at voltage and clock frequencies lower than the nominal ones recommended by Intel and used by ThinkPads by default. Experience shows that the processor may continue working correctly at lower-than-nominal voltages and frequencies, thereby reducing power consumption, heat and fan noise.

In the Pentium M, speed and voltage are controlled by software (through the MSR registers). It is up to the operating system to choose the right voltage for each frequency. Normally this is done according to tables published by Intel or according to ACPI tables. However, this can be overriden - in the case of Linux, by a kernel patch.

{{WARN|Following this instructions will operate your CPU under conditions it was not designed for. Even if your system seems stable, it may still suffer transient faults leading to arbitrary data corruption. In addition, errors in following these instructions (or changes between processor models) may operate the CPU ''above'' its nominal parameters, which, if taken too far, can cause kernel panics or even possibly hardware damage}}

For an example of what may be achieved, consider these examples: when voltages on one ThinkPad {{T43}} were reduced by 20-30%, stable CPU temperature dropped by 7-10deg under both idle and burn-in conditions. Combined with [[how to control fan speed|fan speed control]], this greatly reduced the [[Problem with fan noise|problem with fan noise]]. On one user's ThinkPad {{R51}}, an undervolt brought the full-load processor temperature down from 87 degrees to 63 degrees while maintaining full stability. The effect was, however, negligible at idle.

{{NOTE|While under''volting'' has a clear measurable effect, it's not clear if under''clocking'' really works. <tt>/proc/cpuinfo</tt> reflects the underclocked frequency, but enabling debug output on <tt>cpufreq</tt> causes it to say things like "<tt>CPU frequency out of sync: cpufreq and timing core thinks of 533000, is 800000 kHz.</tt>" where the former is the chosen underclocked frequency and the latter is the documented minimum frequency. This discrepancy also causes [[Software Suspend 2]] to oops during suspend.}}

There are several methods to control CPU voltage in Linux, and currently all of them require a patched kernel.

== Alternative 0: linux-phc ==

Use the [[linux-phc]] kernel patch. '''This is the recommended method, as it is most generic and best supported.'''
* [http://phc.athousandnights.de/ linux-phc home page]

The sysfs interface of linux-phc (version 0.3.0 or newer) requires you to specify VID (Voltage ID) numbers; see the documentation in the source package. For pre-Core Intel CPUs, VID is related to voltage (in mV) as follows: <tt>VID=(voltage-700)/16</tt>.

A typical configuration command would look something like this:

{{cmdroot|echo '27 22 16 10 3' > /sys/devices/system/cpu/cpu0/cpufreq/phc_vids}}

== Alternative 1: patch with hard-coded voltages ==
=== Instructions ===

# Determine the stable voltages for each frequency, using some overclocking/undervolting utility that has specific support for Pentium M ("Centrino") processors. It seems that no such utility exists for Linux. For windows, one good choice is [http://www.pbus-167.com/chc.htm Notebook Hardware Control (NHC)], which conveniently also includes a table of nominal frequencies and voltages (in its help file).<br> Ascertain that at the undervolted settings the CPU actually performs correct computation ([http://www.mersenne.org/freesoft.htm Prime95] in "Tortute Test" mode seems to be a good partial test emphasizing FPU and memory access).<br> Note that beside reducing voltages (undervolting), you can also try to add lower frequencies (underclocking). If you undervolt a particular frequency too much your machine is likely to crash, so try not to have any other programs open.
# Determine the model name string reported by the CPU, e.g., via the "<tt>Model name</tt>" line in {{path|/proc/cpuinfo}}, and likewise the <tt>cpu_family</tt>, <tt>model</tt> and <tt>stepping</tt>.
# Grab a copy of the example patch below and update it to reflect the parameters, frequencies and voltages you found.
# Apply the patch to your kernel (tested with 2.6.13.1 and 2.6.14-rc2).
# To prevent the ACPI table from overriding your table, disable the <tt>CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI</tt> kernel option.
# Compile and install the new kernel.

The changes should be active now. If you want to see debug information attesting to thus, do the following:

# Reboot in <tt>single</tt> mode.
# {{cmdroot|echo 2 > /sys/module/cpufreq/parameters/debug}}
# {{cmdroot|modprobe speedstep-centrino}}
# {{cmdroot|dmesg}} and check for the message "<tt>speedstep-centrino: found "Intel(R) Pentium(R) M processor </tt>..."

If you don't see that message, you got the <tt>cpu_id</tt> or <tt>model_name</tt> parmaeters wrong. If your system crashes, re-test the voltages and adjust accordingly.

Please report your results (including voltages)!

=== Linux kernel patch (example) ===

The following example shows how to undervolt a Pentium M 750 (1.86GHz) on a ThinkPad {{T43}}. As discussed above, the parameters are specific to this one CPU. You will need to experimentally find the correct settings for your own CPU and adjust the patch accordingly.

Note that the Pentium M 750 has a 533MHz FSB (quad-pumped 133MHz), hence the use of <tt>OP133</tt>. If you have a Pentium M with 400MHz FSB (i.e., quad-pumped 100MHz, found in [[Intel Pentium M (Banias)|Banias]] and older [[Intel Pentium M (Dothan)|Dothan]]) then in the voltage table change <tt>OP133</tt> to <tt>OP</tt>.

{{CodeRef|undervolt-pentium-m-2.6.13.1.patch}}

Don't forget to disable <tt>CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI</tt>.

== Alternative 2: patch with user-space control ==

If you want to use the Ubuntu 2.6.15 Kernel, please have a look at this thread: http://ubuntuforums.org/showthread.php?t=146366

The [http://fabrice.bellamy.club.fr/bdz.undervolt.2005.10.22.a.patch bdz.undervolt.2005.10.22.a.patch] patch, written by Gentoo-Wiki user "Bdz", allows voltages to be changed without reboot.

It presents a userspace interface, as in the following example:
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/voltage_table}}
:{{cmdresult|1356,1356,1356,1356,1356,1356,1356,1244,1116,988}}
:{{cmdroot|echo "1084,1084,1084,1084,1084,1084,1084,988,908,860" >/sys/devices/system/cpu/cpu0/cpufreq/voltage_table}}

The relevant [http://gentoo-wiki.com/HOWTO_Undervolt_a_Pentium_M_CPU page] on Gentoo-Wiki providues further information and some helpful hints and scripts for voltage adjustment.

When applying this patch be sure to keep the "ACPI tables for decoding frequency pairs" option -- this patch only allows adjustment of the voltages for the normal clock speeds as reported by the ACPI table in the BIOS. On some models (e.g., ThinkPad {{T43}}) this does not include all clock speeds supported by the processor.

=== Initscript ===
This is a Gentoo initscript for the patch from Gentoo-Wiki user "Bdz".

==== Configuration file ====
<bash>
# /etc/conf.d/undervoltage

# voltage table sysfs interface
VTABLE_SYSFS="/sys/devices/system/cpu/cpu0/cpufreq/voltage_table"

# switch back to DEFAULT_VTABLE if undervoltage is stopped? [yes/no]
SWITCH_BACK="no"

# pentium-m banias 1,7GHz default voltages
DEFAULT_VTABLE="1484,1308,1228,1116,1004,956"
# pentium-m banias 1,7GHz lowered voltages [ -208mV ]
MOD_VTABLE="1276,1100,1020,908,796,748"
</bash>

==== Initscript ====
<bash>
#!/sbin/runscript
# Copyright 1999-2005 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $

sysfs_check() {

if ! [ -e ${VTABLE_SYSFS} ]; then
logger "No sysfs voltage_table present. Modifying vcore voltage failed."
eerror "It seems that the undervolting patch has not been applied to the kernel."
eerror "see http://gentoo-wiki.com/HOWTO_Undervolt_a_Pentium_M_CPU for further information"
return 1
fi
}

start() {
sysfs_check || return 1
ebegin "Switching to modified voltage table [${MOD_VTABLE}]"
echo ${MOD_VTABLE} > ${VTABLE_SYSFS}
eend $?
}

# I think it is not necessary to switch to the default voltage table on shutdown
stop() {
if [ $SWITCH_BACK = "yes" ]; then
ebegin "Switching back to default voltage table [${DEFAULT_VTABLE}]"
echo ${DEFAULT_VTABLE} > ${VTABLE_SYSFS}
eend $?
fi
}
</bash>

== Alternative 3: another patch with user-space control ==

The [http://avkrok.net/nw8240/centrino-voltages.diff centrino-voltages.diff] patch, written by Rickard Holmberg, also provides user-space control. See [http://avkrok.net/nw8240/ here] and [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-December/030772.html here] for usage.

== Stress Testing ==

This [[Undervolt Stress Testing Script|script]] illustrates a very conservative method to stress test your lowered voltage settings.

== Tested frequencies/voltages ==

If you have done excessive testing with user defined frequencies (stable system for over a month).
and no lookups occur when computing primes with mprime http://mersenne.org/ (gentoo: 'emerge gimps')
you can post your frequencies here. But note that this is just a rough indication, since the stable values will differ between individual processors, even in the same model.

{| {{prettytable}}
! CPU Type !! GHz !! Frequency Steps
|-
| Pentium-M Banias || 1.6 || 1212,1084,956,860,796,748
|-
| Pentium-M Banias || 1.7 || 1276,1100,1020,908,796,748
|-
| Pentium-M Dothan || 1.4 || 924,892,860,828,796,764,732,700
|-
| Pentium-M Dothan || 1.86 || 1068,972,876,780,700
|-
| Pentium-M SL6F7 || 1.6 || 1196,1052,956,860,780,732
|-
| Pentium-M Dothan || 1.5 || 924,892,860,828,812,796,764,732,700
|-
| Pentium-M Dothan || 2.0 || 1084,940,844,764,748
|}

Following values were obtained with: (running at the same time)
<bash>
nice -n19 glxgears &
mplayer somedivx.avi &
cd /usr/src/linux && make -j2
</bash>
* note1: for pre-Core Intel CPUs, VID is related to voltage (in mV) as follows: VID=(voltage-700)/16 (or: voltage=(VID*16+700) mV)
* note2: when testing for stability you should pay attention to sound too, occasional distortions which disappear after bumping voltage a notch or two
* note4: if you use phc_vids for your script, then take only second number in each pair
{| {{prettytable}}
! Machine !! CPU Type !! GHz !! phc_controls (fid:vid)
|-
| {{T42}} || Pentium-M Dothan (735) || 1.7 || 17:19 14:12 12:8 10:4 8:1 6:1
|-
| {{X31}} || Pentium-M Banias (1.4) || 1.4 || 14:35 12:32 10:25 8:20 6:10 (fairly conservative)
|-
| {{X32}} || Pentium-M Dothan (745) || 1.8 || 18:26 16:20 14:15 12:11 10:6 8:2 6:1
|-
| {{X40}} || Pentium-M Banias LV (718) || 1.2 || 12:18 11:15 10:12 9:9 8:6 6:3
|-
| {{X41T}} || Pentium-M Dothan LV (758) || 1.5 || 15:15 14:13 13:11 12:9 11:7 10:5 9:3 8:2 6:2
|}

[[Category:Patches]]

Talk:ThinkPad Dock II

2008-07-11T13:31:41Z

BDKMPSS: /* Eject mechanism on Dock II */

Got it! Actually able to run six monitors without any conflicts. Life is good.

Hope I doing this right. Look up the definition of novice in the dictionary and you will find my picture. That said, I have an R52 ThinkPad, a ThinkPad Dock II with an ATI FireMV 2400 PCI 128M video card in the dock PCI slot. Card supports 4 monitors. Was told by a guy at work just plug it all in, install the card drivers, set up the configuration of the monitors in display properties and your good to go. Not so. Display properties only shows 2 monitors. None of the four outputs of the card have a signal. I want to ultimately be able to use 5 monitors, the four supported by the the ATI card and the display on the R-52. Got any ideas where I can get help with this? Thanks for any help anyone can give me.
Eddie
----

I just installed a Nvidia Quadro NVS 50 PCI card in an attempt to add an additional monitor to my laptop (T41), and get 1920 x 1200 digital on my 24" widescreen. The Nvidia is not a dual monitor card, but I thought I would be able to use it as well as the laptop's existing card (ATI Mobility Radeon 7500). However the ATI card shows up in the hardware manager with the message "This device cannot start. (Code 10)". I then tried to enable the AGP as the primary video device in the BIOS (PCI was enabled). The on-board adapter came up, and the device manager listed no conflict, but the Nvidia would not come up as I tried to extend my desktop in display props. I got the message that I did not have admin rights to select the Nvidia, followed by messages that my drivers were not compatible with the newer version of Windows. I have never tried to use two monitors before, so I am not sure if it is feasible to have two video cards running at the same time. If this is possible, please let me know what I need to do, if it is not possible then I need to return the card and get one of your recommended ones.

TIA!
Tony
----
Hi Tony, can't help you much, i'm afraid. I have had a Radeon 9200 PCI card in the dock for a while, using it under Win. I think setting the AGP bus as the primary one in the BIOS is the way you should go. I had troubles with my Windows not booting up at all anymore when i changed it to PCI and was sure that it was the ATI driver having problems.

I would try to get the most recent drivers from the NVidia homepage. Best try uninstalling your drivers and reinstalling them. You might also check if your card is supported by the OMEGA drivers (http://www.omegadrivers.net).

Good luck, Wyrfel.

== Modify for compatibility? ==

I have an X41 Tablet on the way and am very disappointed that the only "Dock" available is more like a glorified port replicator. While I'm sure the X41 Tablet wouldn't ''fit'' on the Dock II, do you think it would be possible to remove the docking port from the plastic and connect it to the X41, or is it a different style connector? I would really appreciate audio jacks and a PCI slot.
^

== Who wrote this about the 1920 x 1200 on the dock II? ==

This is a very important subject to me since we used to buy a lot of T series Thinkpads but dont any longer because of the lack of support for the widescreen external DVI flat panels.

Who wrote this about the new driver from 8-11-05 - I have contacted IBM tech support (not Lenovo) and they have not heard such a thing and it is not listed - they have looked at the last video driver update to the T42p or T43p (I am looking for the 14" SXGA+ T42p model) with a dock II being able to drive externally 1920 x 1200 (UXGA+) WITHOUT an added PCI card. This would be NIRVANA for me.

Do you have anymore information about this driver and have you SEEN it work at all?

Thanks
Dean

dean@sigma-usa.com
----
Hei Dean,

i do not have a 1920x1200 display, but i have a 1600x1200 one which was unsupported before as well. The newest driver (upgraded via IBM Software Installer) indeed doesn't have the problem anymore which it had before with that resolution (1280x1024 was supported max). The newest Presentation Director supports the higher resolution as well.

I actually switched back from OMEGA drivers to the newest IBM release and experienced some strange behaviour which was gone after a few reboots). I guess some parts of OMEGA were not properly uninstalled in one go.

IBM might not know about this if they just upgraded the underlying Catalyst drivers.

However, you might wanna get a confirmation from someone using 1920x1200 before you celebrate. ;-)

[[User:Wyrfel|Wyrfel]] 01:16, 4 Oct 2005 (CEST)
----

BTW: I merged the information that was provided here on this issue into the [[Problem with DVI throughput]] page, since it was doubled in several places and belongs there. [[User:Wyrfel|Wyrfel]] 01:48, 4 Oct 2005 (CEST)
----
====newest drivers work with high resolution via DVI====
The above is a true statement. I have in Nov 2005 installed 3 Thinkpad T's (T42p and T43p) with 128 megs of ATI video RAM (Fire 3200) and with the Think Dock II using the pass through DVI port, i am driving Dell 20" WSXGA+ (1600 x 1050 widescreen) and Sony WUXGA (1900 x 1200) 23" widescreen flat panels. They work OUT OF THE BOX without having to install special drivers. This is a new feature of the Thinkpad line (at least for the T series).
----

== Low Profile PCI? IBM says Half size. ==

I don't think that LowProfile PCI-Cards will fit in the Dock II cause of the shorter mounting bracket.
I just successfully plugged a standard PCI card with the dimension
17.5 cm (without brackets and vga connector) x 9,9 cm (without pci connector, 10,7 cm with pci connector)
This seems to be the maximum dimensions possible...think the 'half size' written by ibm means the length of the card, not the width, as there are full size pci cards e.g. for video editing that reach all the way to the front through a standard tower case.

== Z60 and T60 ==

These machines are not supported by the ''legacy'' docks, you need to use the new Z60 range of port replicators and docking stations.

--[[User:Tonko|Tonko]] 20:22, 11 Jan 2006 (CET)

== T60 And Dual Monitors ==

Yes, you can drive dual monitors with the ThinkPad Advanced Mini-Dock. I am running it under Windows Vista and it is great! The thing you need to do is download the ATI drivers from Lenovo and use the Catalyst Control center to disable your laptop LCD and then enable your analog monitor. By default, the DVI is enabled if both monitors are plugged in.

--[[User:Paul317|Paul317]] 22:30, 19 July 2007 (UTC)

----

So I can drive dual monitors with a T60 and an "THINKPAD ADVANCED MINI-DOCK"?

-- [[ryan.mchale@gmail.com | ryan]] 18:30, 18 April 2006 (CMT)
----
The docking solutions are listed [[Docking Solutions|here]], and indeed that includes the [[ThinkPad Advanced Mini Dock]] which supports the T60.

I do not personally have this hardware, but you should be able to do any of the following:

* ThinkPad LCD + Analog external monitor (VGA)
* ThinkPad LCD + External TV (Svideo)
* ThinkPad LCD + Digital external monitor (DVI)
* Analog external monitor (VGA) + Digital external monitor (DVI)
* Analog external monitor (VGA) + External TV (Svideo)

DVI requires that you have a Dock or Port-Replicator for your ThinkPad with a DVI passthrough port on it. Also you cannot have both DVI and Svideo, since (at least historically, not sure with the new ThinkPads), the Svideo port on the ThinkPad has been blocked by the dock or port replicator and no passthrough function is provided.

Also, I am not sure DVI is supported on the entry T60 model with GMA950 graphics.

--[[User:Tonko|Tonko]] 22:59, 19 April 2006 (CEST)

== Eject mechanism on Dock II ==

I've just acquired a used Dock II, and the eject mechanism seems to be a bit different from other Thinkpad docks and port replicators I'm familiar with. In particular, my question concerns the the square plugs on the dock base that help eject the laptop when the eject button is pressed. On the original dock for the A and T series, the original Port Replicator, and the newer Mini-Dock, the plugs are normally flush with the base, and are pushed up when the user presses the eject button. On the Docking Station II that I have, the plugs are spring loaded, are extruded from the base when no laptop is present, and are not affected by pressing the the eject button. That is, on the Docking Station II, the plugs are always applying pressure pushing the laptop up, and the laptop is held in place by the locking mechanism that is released when the eject button is pressed. Is this normal for the Docking Station II, or is there some linkage in my unit that's broken?

TIA,
Sanford

----

This is perfectly normal and maybe was an attempt from IBM to reduce the complex mechanics of the eject mechanism of the older docks.

--[[User:BDKMPSS|BDKMPSS]] 15:31, 11 July 2008 (CEST)

== R30, R31, and R32 are not supported ==

According to [http://www-307.ibm.com/pc/support/site.wss/MIGR-4NXNTP.html Docking station, port replicator, and expansion - ThinkPad General] R30, R31, and R32 are not supported by ThinkPad Dock II.

== Replace/unplug the noisy fan of Dock II ==

In the information page, it is said some user might replace or unplug the noisy fan, I attempt to open the Dock II so that I could reach the fan and do something about it, does some one here knows the steps to disassemble it? The noise of the fan is really LOUD!

Thanks ahead.

Talk:How to get special keys to work

2008-07-03T21:45:07Z

BDKMPSS: /* ThinkVantage button not recognized by xev under Hardy */

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

== 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)
----
==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)
----
==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)

Pentium M undervolting and underclocking

2008-07-03T18:14:27Z

BDKMPSS: /* Tested frequencies/voltages */ seems like the CPU needs more voltage to be stable at "extreme" high ambient temperatures

== Background ==

Intel Pentium M processors from the [[Intel Pentium M (Dothan)|Dothan]] and [[Intel Pentium M (Banias)|Banias]] families can be instructed to operate at voltage and clock frequencies lower than the nominal ones recommended by Intel and used by ThinkPads by default. Experience shows that the processor may continue working correctly at lower-than-nominal voltages and frequencies, thereby reducing power consumption, heat and fan noise.

In the Pentium M, speed and voltage are controlled by software (through the MSR registers). It is up to the operating system to choose the right voltage for each frequency. Normally this is done according to tables published by Intel or according to ACPI tables. However, this can be overriden - in the case of Linux, by a kernel patch.

{{WARN|Following this instructions will operate your CPU under conditions it was not designed for. Even if your system seems stable, it may still suffer transient faults leading to arbitrary data corruption. In addition, errors in following these instructions (or changes between processor models) may operate the CPU ''above'' its nominal parameters, which, if taken too far, can cause kernel panics or even possibly hardware damage}}

For an example of what may be achieved, consider these examples: when voltages on one ThinkPad {{T43}} were reduced by 20-30%, stable CPU temperature dropped by 7-10deg under both idle and burn-in conditions. Combined with [[how to control fan speed|fan speed control]], this greatly reduced the [[Problem with fan noise|problem with fan noise]]. On one user's ThinkPad {{R51}}, an undervolt brought the full-load processor temperature down from 87 degrees to 63 degrees while maintaining full stability. The effect was, however, negligible at idle.

{{NOTE|While under''volting'' has a clear measurable effect, it's not clear if under''clocking'' really works. <tt>/proc/cpuinfo</tt> reflects the underclocked frequency, but enabling debug output on <tt>cpufreq</tt> causes it to say things like "<tt>CPU frequency out of sync: cpufreq and timing core thinks of 533000, is 800000 kHz.</tt>" where the former is the chosen underclocked frequency and the latter is the documented minimum frequency. This discrepancy also causes [[Software Suspend 2]] to oops during suspend.}}

There are several methods to control CPU voltage in Linux, and currently all of them require a patched kernel.

==Alternative 0: linux-phc==

Use the [[linux-phc]] kernel patch. '''This is the recommended method, as it is most generic and best supported.'''
* [http://phc.athousandnights.de/ linux-phc home page]

The sysfs interface of linux-phc (version 0.3.0 or newer) requires you to specify VID (Voltage ID) numbers; see the documentation in the source package. For pre-Core Intel CPUs, VID is related to voltage (in mV) as follows: <tt>VID=(voltage-700)/16</tt>.

A typical configuration command would look something like this:

{{cmdroot|echo '27 22 16 10 3' > /sys/devices/system/cpu/cpu0/cpufreq/phc_vids}}

== Alternative 1: patch with hard-coded voltages ==
=== Instructions ===

# Determine the stable voltages for each frequency, using some overclocking/undervolting utility that has specific support for Pentium M ("Centrino") processors. It seems that no such utility exists for Linux. For windows, one good choice is [http://www.pbus-167.com/chc.htm Notebook Hardware Control (NHC)], which conveniently also includes a table of nominal frequencies and voltages (in its help file).<br> Ascertain that at the undervolted settings the CPU actually performs correct computation ([http://www.mersenne.org/freesoft.htm Prime95] in "Tortute Test" mode seems to be a good partial test emphasizing FPU and memory access).<br> Note that beside reducing voltages (undervolting), you can also try to add lower frequencies (underclocking). If you undervolt a particular frequency too much your machine is likely to crash, so try not to have any other programs open.
# Determine the model name string reported by the CPU, e.g., via the "<tt>Model name</tt>" line in {{path|/proc/cpuinfo}}, and likewise the <tt>cpu_family</tt>, <tt>model</tt> and <tt>stepping</tt>.
# Grab a copy of the example patch below and update it to reflect the parameters, frequencies and voltages you found.
# Apply the patch to your kernel (tested with 2.6.13.1 and 2.6.14-rc2).
# To prevent the ACPI table from overriding your table, disable the <tt>CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI</tt> kernel option.
# Compile and install the new kernel.

The changes should be active now. If you want to see debug information attesting to thus, do the following:

# Reboot in <tt>single</tt> mode.
# {{cmdroot|echo 2 > /sys/module/cpufreq/parameters/debug}}
# {{cmdroot|modprobe speedstep-centrino}}
# {{cmdroot|dmesg}} and check for the message "<tt>speedstep-centrino: found "Intel(R) Pentium(R) M processor </tt>..."

If you don't see that message, you got the <tt>cpu_id</tt> or <tt>model_name</tt> parmaeters wrong. If your system crashes, re-test the voltages and adjust accordingly.

Please report your results (including voltages)!

=== Linux kernel patch (example) ===

The following example shows how to undervolt a Pentium M 750 (1.86GHz) on a ThinkPad {{T43}}. As discussed above, the parameters are specific to this one CPU. You will need to experimentally find the correct settings for your own CPU and adjust the patch accordingly.

Note that the Pentium M 750 has a 533MHz FSB (quad-pumped 133MHz), hence the use of <tt>OP133</tt>. If you have a Pentium M with 400MHz FSB (i.e., quad-pumped 100MHz, found in [[Intel Pentium M (Banias)|Banias]] and older [[Intel Pentium M (Dothan)|Dothan]]) then in the voltage table change <tt>OP133</tt> to <tt>OP</tt>.

{{CodeRef|undervolt-pentium-m-2.6.13.1.patch}}

Don't forget to disable <tt>CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI</tt>.

==Alternative 2: patch with user-space control==

If you want to use the Ubuntu 2.6.15 Kernel, please have a look at this thread: http://ubuntuforums.org/showthread.php?t=146366

The [http://fabrice.bellamy.club.fr/bdz.undervolt.2005.10.22.a.patch bdz.undervolt.2005.10.22.a.patch] patch, written by Gentoo-Wiki user "Bdz", allows voltages to be changed without reboot.

It presents a userspace interface, as in the following example:
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/voltage_table}}
:{{cmdresult|1356,1356,1356,1356,1356,1356,1356,1244,1116,988}}
:{{cmdroot|echo "1084,1084,1084,1084,1084,1084,1084,988,908,860" >/sys/devices/system/cpu/cpu0/cpufreq/voltage_table}}

The relevant [http://gentoo-wiki.com/HOWTO_Undervolt_a_Pentium_M_CPU page] on Gentoo-Wiki providues further information and some helpful hints and scripts for voltage adjustment.

When applying this patch be sure to keep the "ACPI tables for decoding frequency pairs" option -- this patch only allows adjustment of the voltages for the normal clock speeds as reported by the ACPI table in the BIOS. On some models (e.g., ThinkPad {{T43}}) this does not include all clock speeds supported by the processor.

=Initscript=
This is a Gentoo initscript for the patch from Gentoo-Wiki user "Bdz".

=== Configuration file ===
<bash>
# /etc/conf.d/undervoltage

# voltage table sysfs interface
VTABLE_SYSFS="/sys/devices/system/cpu/cpu0/cpufreq/voltage_table"

# switch back to DEFAULT_VTABLE if undervoltage is stopped? [yes/no]
SWITCH_BACK="no"

# pentium-m banias 1,7GHz default voltages
DEFAULT_VTABLE="1484,1308,1228,1116,1004,956"
# pentium-m banias 1,7GHz lowered voltages [ -208mV ]
MOD_VTABLE="1276,1100,1020,908,796,748"
</bash>

=== Initscript ===
<bash>
#!/sbin/runscript
# Copyright 1999-2005 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $

sysfs_check() {

if ! [ -e ${VTABLE_SYSFS} ]; then
logger "No sysfs voltage_table present. Modifying vcore voltage failed."
eerror "It seems that the undervolting patch has not been applied to the kernel."
eerror "see http://gentoo-wiki.com/HOWTO_Undervolt_a_Pentium_M_CPU for further information"
return 1
fi
}

start() {
sysfs_check || return 1
ebegin "Switching to modified voltage table [${MOD_VTABLE}]"
echo ${MOD_VTABLE} > ${VTABLE_SYSFS}
eend $?
}

# I think it is not necessary to switch to the default voltage table on shutdown
stop() {
if [ $SWITCH_BACK = "yes" ]; then
ebegin "Switching back to default voltage table [${DEFAULT_VTABLE}]"
echo ${DEFAULT_VTABLE} > ${VTABLE_SYSFS}
eend $?
fi
}
</bash>

==Alternative 3: another patch with user-space control==

The [http://avkrok.net/nw8240/centrino-voltages.diff centrino-voltages.diff] patch, written by Rickard Holmberg, also provides user-space control. See [http://avkrok.net/nw8240/ here] and [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-December/030772.html here] for usage.

==Stress Testing==

This [[Undervolt Stress Testing Script|script]] illustrates a very conservative method to stress test your lowered voltage settings.

==Tested frequencies/voltages==

If you have done excessive testing with user defined frequencies (stable system for over a month).
and no lookups occur when computing primes with mprime http://mersenne.org/ (gentoo: 'emerge gimps')
you can post your frequencies here. But note that this is just a rough indication, since the stable values will differ between individual processors, even in the same model.

{| {{prettytable}}
! CPU Type !! GHz !! Frequency Steps
|-
| Pentium-M Banias || 1.6 || 1212,1084,956,860,796,748
|-
| Pentium-M Banias || 1.7 || 1276,1100,1020,908,796,748
|-
| Pentium-M Dothan || 1.4 || 924,892,860,828,796,764,732,700
|-
| Pentium-M Dothan || 1.86 || 1068,972,876,780,700
|-
| Pentium-M SL6F7 || 1.6 || 1196,1052,956,860,780,732
|-
| Pentium-M Dothan || 1.5 || 924,892,860,828,812,796,764,732,700
|-
| Pentium-M Dothan || 2.0 || 1084,940,844,764,748
|}

Following values were obtained with: (running at the same time)
<bash>
nice -n19 glxgears &
mplayer somedivx.avi &
cd /usr/src/linux && make -j2
</bash>
* note1: for pre-Core Intel CPUs, VID is related to voltage (in mV) as follows: VID=(voltage-700)/16 (or: voltage=(VID*16+700) mV)
* note2: when testing for stability you should pay attention to sound too, occasional distortions which disappear after bumping voltage a notch or two
* note4: if you use phc_vids for your script, then take only second number in each pair
{| {{prettytable}}
! Machine !! CPU Type !! GHz !! phc_controls (fid:vid)
|-
| {{T42}} || Pentium-M Dothan (735) || 1.7 || 17:19 14:12 12:8 10:4 8:1 6:1
|-
| {{X31}} || Pentium-M Banias (1.4) || 1.4 || 14:32 12:30 10:23 8:16 6:5 (fairly conservative)
|-
| {{X32}} || Pentium-M Dothan (745) || 1.8 || 18:26 16:20 14:15 12:11 10:6 8:2 6:1
|-
| {{X41T}} || Pentium-M Dothan LV (758) || 1.5 || 15:15 14:13 13:11 12:9 11:7 10:5 9:3 8:2 6:2
|}

[[Category:Patches]]

User:BDKMPSS

2008-06-28T21:12:03Z

BDKMPSS:

==my ThinkPad '''''Workstation'''''==
ThinkPad [[:Category:X31|X31]] (Model: 2672-C2G) running [[:Category:Debian|Debian]] Testing

===Default Features===
* Intel Pentium M 1.4
* 256 MB PC2100
* 40GB Hitachi HDD
* Intel 10/100 Ethernet controller (PXE boot enabled)
* CDC slot with Modem Daughter Card (MDC)
* MiniPCI slot with Intel PRO/Wireless LAN 2100 3B Mini PCI Adapter

===Changed/Upgraded to/with:===
* Intel Pentium M 1.4 undervolted
* 2 GB DDR 400 RAM (Kingston KVR400X64SC3A/1G) running at 266MHz
* 160 GB Hitachi TravelStar 5K160 (HTS541616J9AT00)
* Intel Pro/Wireless 2915 ABG MiniPCI card
* Modem Daughter Card (MDC) removed
* PXE boot via Bios disabled
* newest BIOS/EC-Frimware (3.02/1.08)

===why I have chosen/stick to this very model===
I think this is may the last Thinkpad purchase I ever made, not because I don't like it, actually I love it, but I don't like the "newer ones" (ThinkPad X40 and higher).

For me this this very model was/is the (second) last '''''perfect''''' one, so I never got a newer one and the last known good, the X32, is not a update which is really enhancing.
My X31 is '''''very solid''''', '''''ultraportable''''' and '''''fast enough''''' for the "office" stuff I do with it.

This is partly may also featured by the newer ones, but I miss some things of my X31 '''''very''''' much on them:
*the port-layout is much better than the "newer one". I hate ports on the sides especially on the right one, and all newer ones have all ports there...
*the LCD cover with this thick, wide, "salient" borders is absolutely robust and "unbreakable". Or at least feels like this ;)
*the overall case feels much better engineered, like I could walk over it without doing any damage, the newer ones just don't feel like this (no I am not going to try it)
*its one of the last fully IBM crafted ones, as I am not comfortable with this strange 3rd party manufacturing outsourcing somewhere in deeper China witch started right after the X31 was constructed
*Even if it first seemed like Lenovo could keep up the "legendary" quality, or even increase it to the old "pre-outsourcing" level, it now seems like this was wishful thinking

Intel Pentium M (Dothan)

2008-06-28T15:10:34Z

BDKMPSS: shouldn't use generation two times in different contexts

{| 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 Pentium M "Dothan" is the second generation Pentium M processor. The fabrication process was reduced to 90 nm and the L2-Cache was doubled to 2 MB. The second revision of Dothan Pentium M processors features a 533 MHz FSB and accompanies the Sonoma [[Centrino]] platform.

==Features==
*1.0 - 2.26 GHz clock speed
*400/533 MHz FSB
*170 Million Transistors
*90 nm fabrication process
*2 MB L2-Cache
*[[SpeedStep|(Enhanced) EIST]], [[QuickStart and Deeper Sleep|Deeper Sleep]]
* XD-Bit (on most models)
*[[SIMD|MMX]], [[SIMD|SSE]], [[SIMD|SSE2]] instruction sets
</div>
|}

==Available Types and ThinkPads featuring them==
{| border=1 cellspacing=0 cellpadding=2
|- style="background:#ffdead;white-space:nowrap;"
! Nr. || colspan=2 | Frequency (MHz) || FSB (MHz)|| XD-Bit || colspan=2 | core Voltage (V) || colspan=2 | TDP (W) || ThinkPad Models
|- style="background:#ffdead;"
! !!max. !! min. !! !! !! high !! low !! high !! low !!
|- style="background:#efefef;"
! colspan="10" | Pentium M
|-
| 780 || 2266 || 800 || 533 || • || 1.372 || ... || 27 || 11 || {{R52}}, {{T43}}. {{T43p}}
|-
| 770 || 2133 || 800 || 533 || • || 1.372 || 0.988 || 27 || 11 || {{R52}}, {{T43}}, {{T43p}}
|-
| 765 || 2100 || 600 || 400 || || 1.34 || 0.988 || 21 || 8 || {{T42p}}
|-
| 760 || 2000 || 800 || 533 || • || 1.372 || 0.988 || 27 || 11 || {{R52}}, {{T43}}, {{T43p}}, {{Z60m}}, {{Z60t}}
|-
| 755 || 2000 || 600 || 400 || || 1.34 || 0.988 || 21 || 8 || {{T42p}}, {{X32}}
|-
| 750 || 1866 || 800 || 533 || • || 1.372 || 0.988 || 27 || 11 || {{R52}}, {{T43}}, {{T43p}}, {{Z60m}}, {{Z60t}}
|-
| 745 || 1800 || 600 || 400 || || 1.34 || 0.988 || 21 || 8 || {{T42}}, {{T42p}}, {{X32}}, {{R51}}
|-
| 740 || 1733 || 800 || 533 || • || 1.372 || 0.988 || 27 || 11 || {{R51e}}, {{R52}}, {{T43}}, {{Z60m}}, {{Z60t}}
|-
| 735 || 1700 || 600 || 400 || || 1.34 || 0.988 || 21 || 8 || {{R50e}}, {{R51}}, {{T42}}, {{X32}}
|-
| 730 || 1600 || 800 || 533 || • || 1.372 || 0.988 || 27 || 11 || {{T43}}
|-
| 725a || 1600 || 600 || 400 || || ... || ... || ... || ... || {{R50e}}, {{R51}}, {{R52}}
|-
| 725 || 1600 || 600 || 400 || || 1.34 || 0.988 || 21 || 8 || {{R50e}}, {{R51}}, {{T42}}, {{X32}}
|-
| 715a || 1500 || 600 || 400 || || ... || ... || ... || ... || {{R50e}}, {{R51}}
|-
| 715 || 1500 || 600 || 400 || || 1.34 || 0.988 || 21 || 8 || {{R50e}}, {{R51}}
|-
| 710 || 1400 || ... || 400 || || ... || ... || ... || ... || {{R50e}}, {{R51}}
|- style="background:#efefef;"
! colspan="10" | Pentium M (Low Voltage)
|-
| 778 || 1600 || ... || 400 || • || 1.116 || ... || 10 || ... || {{X40}}, {{X41}}, {{X41T}}
|-
| 758 || 1500 || 600 || 400 || • || 1.116 || 0.988 || 10 || ... || {{X40}}, {{X41}}, {{X41T}}
|-
| 738 || 1400 || ... || 400 || || 1.116 || 0.988 || 10 || ... || {{X40}}
|- style="background:#efefef;"
! colspan="10" | Pentium M (Ultra Low Voltage)
|-
| 773 || 1300 || ... || 400 || • || ... || ... || ... || ... ||
|-
| 753 || 1200 || ... || 400 || • || 0.940 || 0.812 || 5 || ... || {{X41T}}
|-
| 733J || 1100 || ... || 400 || • || .... || ... || ... || ... ||
|-
| 733 || 1100 || ... || 400 || || 0.940 || 0.812 || 5 || ... || {{X40}}
|-
| 723 || 1000 || ... || 400 || || 0.940 || 0.812 || 5 || ... ||
|}

==Thermal Specifications==
The max. Core Temperature is 100°C.

==GCC Optimization Flags==
You should use the following for GCC version 3.4.4 and later if you have a Pentium M:
-Os -march=pentium-m -pipe

For GCC version 3.3.5 and earlier use the following:
-Os -march=pentium3 -msse2 -pipe

Also, if you don't plan to use debugging information, then you can safely add the following to either of the above for a possible performance improvement:
-fomit-frame-pointer

==See also==
* [[Intel Pentium M (Banias)]]
* [[Intel Core Duo (Yonah)]]
* [[Pentium M undervolting and underclocking]]

[[Category:Components]]

Pentium M undervolting and underclocking

2008-06-28T14:48:55Z

BDKMPSS: /* Tested frequencies/voltages */ adding my X31; apply some order

== Background ==

Intel Pentium M processors from the [[Intel Pentium M (Dothan)|Dothan]] and [[Intel Pentium M (Banias)|Banias]] families can be instructed to operate at voltage and clock frequencies lower than the nominal ones recommended by Intel and used by ThinkPads by default. Experience shows that the processor may continue working correctly at lower-than-nominal voltages and frequencies, thereby reducing power consumption, heat and fan noise.

In the Pentium M, speed and voltage are controlled by software (through the MSR registers). It is up to the operating system to choose the right voltage for each frequency. Normally this is done according to tables published by Intel or according to ACPI tables. However, this can be overriden - in the case of Linux, by a kernel patch.

{{WARN|Following this instructions will operate your CPU under conditions it was not designed for. Even if your system seems stable, it may still suffer transient faults leading to arbitrary data corruption. In addition, errors in following these instructions (or changes between processor models) may operate the CPU ''above'' its nominal parameters, which, if taken too far, can cause kernel panics or even possibly hardware damage}}

For an example of what may be achieved, consider these examples: when voltages on one ThinkPad {{T43}} were reduced by 20-30%, stable CPU temperature dropped by 7-10deg under both idle and burn-in conditions. Combined with [[how to control fan speed|fan speed control]], this greatly reduced the [[Problem with fan noise|problem with fan noise]]. On one user's ThinkPad {{R51}}, an undervolt brought the full-load processor temperature down from 87 degrees to 63 degrees while maintaining full stability. The effect was, however, negligible at idle.

{{NOTE|While under''volting'' has a clear measurable effect, it's not clear if under''clocking'' really works. <tt>/proc/cpuinfo</tt> reflects the underclocked frequency, but enabling debug output on <tt>cpufreq</tt> causes it to say things like "<tt>CPU frequency out of sync: cpufreq and timing core thinks of 533000, is 800000 kHz.</tt>" where the former is the chosen underclocked frequency and the latter is the documented minimum frequency. This discrepancy also causes [[Software Suspend 2]] to oops during suspend.}}

There are several methods to control CPU voltage in Linux, and currently all of them require a patched kernel.

==Alternative 0: linux-phc==

Use the [[linux-phc]] kernel patch. '''This is the recommended method, as it is most generic and best supported.'''
* [http://phc.athousandnights.de/ linux-phc home page]

The sysfs interface of linux-phc (version 0.3.0 or newer) requires you to specify VID (Voltage ID) numbers; see the documentation in the source package. For pre-Core Intel CPUs, VID is related to voltage (in mV) as follows: <tt>VID=(voltage-700)/16</tt>.

A typical configuration command would look something like this:

{{cmdroot|echo '27 22 16 10 3' > /sys/devices/system/cpu/cpu0/cpufreq/phc_vids}}

== Alternative 1: patch with hard-coded voltages ==
=== Instructions ===

# Determine the stable voltages for each frequency, using some overclocking/undervolting utility that has specific support for Pentium M ("Centrino") processors. It seems that no such utility exists for Linux. For windows, one good choice is [http://www.pbus-167.com/chc.htm Notebook Hardware Control (NHC)], which conveniently also includes a table of nominal frequencies and voltages (in its help file).<br> Ascertain that at the undervolted settings the CPU actually performs correct computation ([http://www.mersenne.org/freesoft.htm Prime95] in "Tortute Test" mode seems to be a good partial test emphasizing FPU and memory access).<br> Note that beside reducing voltages (undervolting), you can also try to add lower frequencies (underclocking). If you undervolt a particular frequency too much your machine is likely to crash, so try not to have any other programs open.
# Determine the model name string reported by the CPU, e.g., via the "<tt>Model name</tt>" line in {{path|/proc/cpuinfo}}, and likewise the <tt>cpu_family</tt>, <tt>model</tt> and <tt>stepping</tt>.
# Grab a copy of the example patch below and update it to reflect the parameters, frequencies and voltages you found.
# Apply the patch to your kernel (tested with 2.6.13.1 and 2.6.14-rc2).
# To prevent the ACPI table from overriding your table, disable the <tt>CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI</tt> kernel option.
# Compile and install the new kernel.

The changes should be active now. If you want to see debug information attesting to thus, do the following:

# Reboot in <tt>single</tt> mode.
# {{cmdroot|echo 2 > /sys/module/cpufreq/parameters/debug}}
# {{cmdroot|modprobe speedstep-centrino}}
# {{cmdroot|dmesg}} and check for the message "<tt>speedstep-centrino: found "Intel(R) Pentium(R) M processor </tt>..."

If you don't see that message, you got the <tt>cpu_id</tt> or <tt>model_name</tt> parmaeters wrong. If your system crashes, re-test the voltages and adjust accordingly.

Please report your results (including voltages)!

=== Linux kernel patch (example) ===

The following example shows how to undervolt a Pentium M 750 (1.86GHz) on a ThinkPad {{T43}}. As discussed above, the parameters are specific to this one CPU. You will need to experimentally find the correct settings for your own CPU and adjust the patch accordingly.

Note that the Pentium M 750 has a 533MHz FSB (quad-pumped 133MHz), hence the use of <tt>OP133</tt>. If you have a Pentium M with 400MHz FSB (i.e., quad-pumped 100MHz, found in [[Intel Pentium M (Banias)|Banias]] and older [[Intel Pentium M (Dothan)|Dothan]]) then in the voltage table change <tt>OP133</tt> to <tt>OP</tt>.

{{CodeRef|undervolt-pentium-m-2.6.13.1.patch}}

Don't forget to disable <tt>CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI</tt>.

==Alternative 2: patch with user-space control==

If you want to use the Ubuntu 2.6.15 Kernel, please have a look at this thread: http://ubuntuforums.org/showthread.php?t=146366

The [http://fabrice.bellamy.club.fr/bdz.undervolt.2005.10.22.a.patch bdz.undervolt.2005.10.22.a.patch] patch, written by Gentoo-Wiki user "Bdz", allows voltages to be changed without reboot.

It presents a userspace interface, as in the following example:
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/voltage_table}}
:{{cmdresult|1356,1356,1356,1356,1356,1356,1356,1244,1116,988}}
:{{cmdroot|echo "1084,1084,1084,1084,1084,1084,1084,988,908,860" >/sys/devices/system/cpu/cpu0/cpufreq/voltage_table}}

The relevant [http://gentoo-wiki.com/HOWTO_Undervolt_a_Pentium_M_CPU page] on Gentoo-Wiki providues further information and some helpful hints and scripts for voltage adjustment.

When applying this patch be sure to keep the "ACPI tables for decoding frequency pairs" option -- this patch only allows adjustment of the voltages for the normal clock speeds as reported by the ACPI table in the BIOS. On some models (e.g., ThinkPad {{T43}}) this does not include all clock speeds supported by the processor.

=Initscript=
This is a Gentoo initscript for the patch from Gentoo-Wiki user "Bdz".

=== Configuration file ===
<bash>
# /etc/conf.d/undervoltage

# voltage table sysfs interface
VTABLE_SYSFS="/sys/devices/system/cpu/cpu0/cpufreq/voltage_table"

# switch back to DEFAULT_VTABLE if undervoltage is stopped? [yes/no]
SWITCH_BACK="no"

# pentium-m banias 1,7GHz default voltages
DEFAULT_VTABLE="1484,1308,1228,1116,1004,956"
# pentium-m banias 1,7GHz lowered voltages [ -208mV ]
MOD_VTABLE="1276,1100,1020,908,796,748"
</bash>

=== Initscript ===
<bash>
#!/sbin/runscript
# Copyright 1999-2005 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $

sysfs_check() {

if ! [ -e ${VTABLE_SYSFS} ]; then
logger "No sysfs voltage_table present. Modifying vcore voltage failed."
eerror "It seems that the undervolting patch has not been applied to the kernel."
eerror "see http://gentoo-wiki.com/HOWTO_Undervolt_a_Pentium_M_CPU for further information"
return 1
fi
}

start() {
sysfs_check || return 1
ebegin "Switching to modified voltage table [${MOD_VTABLE}]"
echo ${MOD_VTABLE} > ${VTABLE_SYSFS}
eend $?
}

# I think it is not necessary to switch to the default voltage table on shutdown
stop() {
if [ $SWITCH_BACK = "yes" ]; then
ebegin "Switching back to default voltage table [${DEFAULT_VTABLE}]"
echo ${DEFAULT_VTABLE} > ${VTABLE_SYSFS}
eend $?
fi
}
</bash>

==Alternative 3: another patch with user-space control==

The [http://avkrok.net/nw8240/centrino-voltages.diff centrino-voltages.diff] patch, written by Rickard Holmberg, also provides user-space control. See [http://avkrok.net/nw8240/ here] and [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-December/030772.html here] for usage.

==Stress Testing==

This [[Undervolt Stress Testing Script|script]] illustrates a very conservative method to stress test your lowered voltage settings.

==Tested frequencies/voltages==

If you have done excessive testing with user defined frequencies (stable system for over a month).
and no lookups occur when computing primes with mprime http://mersenne.org/ (gentoo: 'emerge gimps')
you can post your frequencies here. But note that this is just a rough indication, since the stable values will differ between individual processors, even in the same model.

{| {{prettytable}}
! CPU Type !! GHz !! Frequency Steps
|-
| Pentium-M Banias || 1.6 || 1212,1084,956,860,796,748
|-
| Pentium-M Banias || 1.7 || 1276,1100,1020,908,796,748
|-
| Pentium-M Dothan || 1.4 || 924,892,860,828,796,764,732,700
|-
| Pentium-M Dothan || 1.86 || 1068,972,876,780,700
|-
| Pentium-M SL6F7 || 1.6 || 1196,1052,956,860,780,732
|-
| Pentium-M Dothan || 1.5 || 924,892,860,828,812,796,764,732,700
|-
| Pentium-M Dothan || 2.0 || 1084,940,844,764,748
|}

Following values were obtained with: (running at the same time)
<bash>
nice -n19 glxgears &
mplayer somedivx.avi &
cd /usr/src/linux && make -j2
</bash>
* note1: for pre-Core Intel CPUs, VID is related to voltage (in mV) as follows: VID=(voltage-700)/16 (or: voltage=(VID*16+700) mV)
* note2: when testing for stability you should pay attention to sound too, occasional distortions which disappear after bumping voltage a notch or two
* note3: if you use phc_vids for your script, then take only second number in each pair
{| {{prettytable}}
! Machine !! CPU Type !! GHz !! phc_controls (fid:vid)
|-
| {{T42}} || Pentium-M Dothan (735) || 1.7 || 17:19 14:12 12:8 10:4 8:1 6:1
|-
| {{X31}} || Pentium-M Banias (1.4) || 1.4 || 14:25 12:20 10:15 8:10 6:5 (fairly conservative)
|-
| {{X32}} || Pentium-M Dothan (745) || 1.8 || 18:26 16:20 14:15 12:11 10:6 8:2 6:1
|-
| {{X41T}} || Pentium-M Dothan LV (758) || 1.5 || 15:15 14:13 13:11 12:9 11:7 10:5 9:3 8:2 6:2
|}

[[Category:Patches]]

Xorg RandR 1.2

2008-02-24T18:26:38Z

BDKMPSS: /* Using xrandr to do useful things */ fixed typo

== Overview ==

'''X RandR '''is used to configure which display ports are enabled (e.g. LCD, VGA and DVI), and to configure display modes and properties such as orientation, reflection and DPI.

This is the simplest and most powerful way to get multi-monitor systems working using recent versions of Linux such as {{Ubuntu 7.10}} with graphics chipsets such as the Intel 945GM/GMS and ATI Radeon found in Thinkpads.

'''xrandr''' is the command line interface to the RandR X extension. As usual with X, good documentation is hard to find; first try the following commands:

* {{cmduser|xrandr --help}}
* {{cmduser|man xrandr}}

* for Intel graphics: {{cmduser|man intel}}
* for ATI graphics: {{cmduser|man radeon}}

The rest of this page refers to a laptop with a built in 1024x768 pixel screen and an external 1600x1200 VGA monitor. Simply replace the relevant numbers with your own system specifications and all should work fine.

== Supported drivers ==
{{Ubuntu 7.10}} '''Gutsy Gibbon'''
* X.org [[intel]] driver, version ??? (included in Xorg ???) and later. Ubuntu version: [https://launchpad.net/ubuntu/+source/xserver-xorg-video-intel/2:2.1.1-0ubuntu2 2:2.1.1-0ubuntu2] with [https://launchpad.net/ubuntu/gutsy/i386/xrandr/1:1.2.2-0ubuntu1 xrandr 1:1.2.2-0ubuntu1]

* X.org [[radeon]] driver, 6.7.192 and later (in ubuntu [http://packages.ubuntu.com/gutsy/x11/xserver-xorg-video-ati gutsy] and [http://packages.ubuntu.com/hardy/x11/xserver-xorg-video-ati hardy], but they still have [http://bugs.launchpad.net/bugs/148408 very serious issues] for some Thinkpads).

== xorg.conf ==
Recent versions of xorg.conf intended for use with xrandr 1.2 considerably simplify the video section of the configuration. If you upgrading from an earlier version you may find your existing xorg.conf works against the effective deployment of xrandr. So it is best to start with a new Xorg configuration.

'''an updated Xorg.conf should:'''
* omit dual Device/Screen/Monitor sections
* omit MonitorLayout option and Screen lines from the remaining Device section
* omit dual Screen lines from the ServerLayout section
* omit RightOf/LeftOf indication to the remaining Screen line in ServerLayout section
* add a "Virtual 2048 2048" line in SubSection "Display" to create a large virtual screen

To create a new xorg.conf or Ubuntu and other Debian based distributions connect the external display to the VGA port, turn on that display, and run
{{cmduser|sudo dpkg-reconfigure -phigh xserver-xorg}}

The resulting {{path|/etc/X11/xorg.conf}} should include something like

Section "Device"
Identifier "Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller"
Driver "intel"
BusID "PCI:0:2:0"
'''# ADD THIS IF YOUR LAPTOP DOES NOT HAVE A TV CONNECTOR or DOCKING STATION '''
'''Option "monitor-TV" "TV" '''
EndSection
Section "Monitor"
Identifier "Generic Monitor"
Option "DPMS"
EndSection
''' # ADD THIS IF YOUR LAPTOP DOES NOT HAVE A TV CONNECTOR or DOCKING STATION '''
'''Section "Monitor" '''
'''Identifier "TV" '''
'''Option "Ignore" "True" '''
EndSection '''
Section "Screen"
Identifier "Default Screen"
Device "Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller"
Monitor "Generic Monitor"
DefaultDepth 24
...
SubSection "Display"
Depth 24
Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"
'''# ADD A VIRTUAL LINE TO PROVIDE FOR THE LARGEST SCREENS YOU WILL HOTPLUG '''
'''Virtual 2048 2048 '''
EndSubSection
EndSection
Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
InputDevice "stylus" "SendCoreEvents"
InputDevice "cursor" "SendCoreEvents"
InputDevice "eraser" "SendCoreEvents"
InputDevice "Synaptics Touchpad"
EndSection

after creating a clean Xorg.conf restart X and logon

You may find you have a display only on the external VGA screen at its default max resolution, do not worry xrandr can fix this.

== Using {{cmduser|xrandr}} ==

===First discover what we have ===
Open a terminal window to use the command line: 'Applications:Accessories:Terminal'

{{HINT|First look at the 'help' and 'man' pages. }}

{{cmduser|xrandr --help}}
{{cmduser|man xrandr}}

To find what version of xrandr is running, type the following command:
{{cmduser| xrandr -v}}
Server reports RandR version 1.2

To query what screens are connected, type the following: (The output shown indicates nothing is connected to the VGA port.)
{{cmduser| xrandr -q }}
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 1920 x 1440
VGA disconnected (normal left inverted right)
LVDS connected 1024x768+0+0 (normal left inverted right) 304mm x 228mm
1024x768 60.0*+ 50.0
800x600 60.3
640x480 60.0 59.9
TV disconnected (normal left inverted right)

If you see the 'TV disconnected' line but have neither TV connector nor docking station (eg Thinkpad R60e) then add to the Monitor and Device sections of xorg.conf as noted above. This will prevent the external (VGA) flashing off for a few seconds every time xrandr is used. (Newer versions of the intel driver may fix this.)

The same command as above, but with the VGA monitor plugged in and powered off, should give something like the following output: (The VGA monitor is now shown as 'connected'.)
{{cmduser| xrandr -q }}
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 1920 x 1440
VGA connected (normal left inverted right)
1920x1440@60 60.0
1920x1440 60.0
1600x1200@60 60.0
1600x1200 60.0
1280x960 60.0
640x480@60 60.0
LVDS connected 1024x768+0+0 (normal left inverted right) 304mm x 228mm
1024x768 60.0*+ 50.0
800x600 60.3
640x480 60.0 59.9
TV disconnected (normal left inverted right)

Powering on the VGA monitor and issuing the same command again will give the following output: (The size and position of the VGA output within the virtual screen is now shown.)
{{cmduser| xrandr -q }}
Screen 0: minimum 320 x 200, current 2624 x 1200, maximum 2624 x 2048
VGA connected 1600x1200+1024+0 (normal left inverted right) 367mm x 275mm
1600x1200 60.0*+
1920x1440@60 60.0
1600x1200@60 60.0
640x480@60 60.0
640x480 60.0
LVDS connected 1024x768+0+0 (normal left inverted right) 304mm x 228mm
1024x768 60.0*+ 50.0
800x600 60.3
640x480 60.0 59.9
TV disconnected (normal left inverted right)

For bug reporting and diagnosis use xrandr with the verbose option:
{{cmduser| xrandr --verbose}}

===Using xrandr to do useful things===
In general the commands will specify the output name and either --off or --auto. In the examples here the external screen is named ''VGA'', as used by the Intel driver, with an ATI card the name will probably be ''VGA-0''. In general use {{cmduser| xrandr -q}} to discover the appropriate output names for your configuration. The --auto option will select the preferred resolution for each output, this is starred(*) in the {{cmduser| xrandr -q}} listing and is normally the best resolution available. It is also possible to set a particular mode eg --mode 1024x768.

First clone the two screens, (the smaller screen will display the top left portion of the virtual screen)
{{cmduser| xrandr --output LVDS --auto --output VGA --auto --same-as LVDS}}

To turn off the VGA monitor.
{{cmduser| xrandr --output VGA --off }}

To turn the VGA monitor back on, with its viewport to the right of the laptop monitor:
{{cmduser| xrandr --output VGA --auto --right-of LVDS}}
This will probably give an error message similar to:
xrandr: screen cannot be larger than 1600x1600 (desired size 2624x1200)

This can be fixed by editing xorg.conf and changing the ''virtual'' line (see example above) to something like:
Virtual 2624 1200
Note that the maximum supported size of the virtual desktop for the Intel 945GM series of chipset with 3D acceleration enabled, is 2048x2048. The virtual screen can be larger but DRI will be disabled. This may matter if you like games and compiz desktop effects, or if you want Google Earth to display in better than geological time. Obviously the larger the virtual desktop, the more graphics memory is used. So for good performance with a shared graphics system such as Intel the Virtual should be no larger than necessary.

It is possible to set screen locations as ''--left-of'', ''--right-of'', ''--above'' and ''--below''. Assuming displays sizes of 1024x768 and 1200x1600:
{{cmduser| xrandr --output LVDS --auto --output VGA --auto --right-of LVDS}}
and
{{cmduser| xrandr --output LVDS --mode 1024x768 --pos 0x0 --output VGA --mode 1600x1200 --pos 1024x0}}
are equivalent. Both will place the external monitor to the right of the laptop display within the virtual screen.

If the Virtual size is only 2048 wide the above command will fail as the combined width of the two displays exceeds the maximum virtual size. However it is possible to have overlap the display viewports. So to fit within the 2048 limit:
{{cmduser| xrandr --output VGA --mode 1024x768 --pos 0x0 --output VGA --mode 1600x1200 --pos 448x0}}

===[[Sample Fn-F7 script]]===
For further examples of the use of xrandr commands and a script to switch the display using the Fuction key Fn7 see [[Sample Fn-F7 script]].

== Summing up ==

'''xrandr''' enables dynamic resizing of screens, switching both external and laptop screens on and off, and the applications windows can be dragged from one screen to the other. None of this requires configuring anything special for {{path|/etc/X11/xorg.conf}}.

===the Virtual screen===
A Virtual line is needed in the 'Display' SubSection of the of xorg.conf; it determines the size of the frame buffer into which the displays must fit. Without it the maximum virtual size will be limited to the size of the largest display that was connected when X was started. The maximum virtual size cannot be changed once X starts so needs to be large enough to accommodate the largest combination of displays you want to hotplug without having to restart X. If it is greater than 2048x2048 and you are using an Intel 945 (or less) chip then DRI is not possible. Making the Virtual size square makes rotation easy. A bigger Virtual requires more memory.

[[Image:Intel-DualHead.png|monitor windows must fit within the virtual screen]]

=== Output port names ===

'''Intel driver'''
* '''VGA''' - Analog VGA output
* '''LVDS''' - Laptop panel
* '''TV''' - Integrated TV output
* '''TMDS-1''' - First DVI SDVO output
* '''TMDS-2''' - Second DVI SDVO output
The '''SDVO''' and '''DVO TV''' outputs are not supported by the driver at this time.

'''[[radeon]] driver '''
* '''VGA-0''' - Analog VGA output
* '''LVDS''' - Laptop panel
* '''S-video''' - Integrated TV output
* '''DVI-0''' - DVI output

===Note for Gnome users===
Gnome places the menu bar on screen 0 and thus with the Intel chip and driver Screen 0 (the external VGA monitor) will always be the default display if it is connected. This applies even if the external monitor is switched off but the cable connected: if you have a blank laptop monitor check if you have anything plugged in to the VGA port. Also beware that desktop icons and windows can disappear into the invisible parts of the virtual display. (see diagram below)

===Note for Ubuntu Gutsy users===
There is a Graphical Configuration Tool, ([https://launchpad.net/ubuntu/+source/displayconfig-gtk/0.2+20070731ubuntu1 displayconfig-gtk]) included with {{Ubuntu 7.10}}. At present [https://bugs.launchpad.net/ubuntu/+source/displayconfig-gtk it dosn't work too well].It is found in the menu: 'System: Administration: Screens and Graphics'. As using it will wreck your xorg.conf I recommend removing it.

== Gleanings ==
=== Notes from xserver-xorg-video-intel.readme ===
'''Known Limitations'''
- No support for "zaphod mode" dualhead. This is the mode in which two
Device sections are placed in the config file, and doesn't support DRI or
many other features. Instead, only "MergedFB-style" dualhead is supported.
- No support for X Screens larger than 2048 pixels in either direction
before the 965. This reflects hardware limitations in the x direction on
those older chips, and limits dualhead functionality. It may be possible to
extend the limit vertically on these older chips.
- i855 XV may cause hangs. This was present in the previous release, and no
workaround is known.
- SDVO TV-out cards not supported. This should be fixed in the next
release.
- Gray output with integrated TV-out and PAL TVs.
- EXA support unstable on i845.
- Some GM965 systems, such as the Thinkpad T61, probe the TV as being connected
even when no output connector is available.

'''Common issues not caused by the driver'''
- Font sizes (DPI) are wrong. Some displays incorrectly report their
physical size, which is harmless on most OSes that always assume 96dpi
displays. This can be fixed through quirks for specific monitors in the X
Server, and the output of xrandr --prop along with a physical measurement of
the screen size in a bug report against the server can help get that fixed.
- gnome-panel is located in the middle of the screen. gnome-panel places
itself within head #0's boundaries, which doesn't work well with a second
head covering the same area as head #0 but larger.
- Older resolution-changing applications have poor results in
multihead systems. Previous extensions such as RandR 1.1 exposed only a
single output to client programs, and those requests map poorly to multi-head
systems. Currently, those requests map to just one of the outputs in the
RandR 1.2 environment, and those applications need to be updated to RandR 1.2
API when available for better results.

=== Xorg mailing list ===
[http://lists.freedesktop.org/archives/xorg/2007-June/025469.html FreeDesktop.org 2007-June 025469]
[http://lists.freedesktop.org/archives/xorg/2007-June/025484.html FreeDesktop.org 2007-June 025484]
[http://lists.freedesktop.org/archives/xorg/2007-July/026340.html FreeDesktop.org 2007-July 026340]

the 3D engine has an 11 bit coordinate space at one point making it
impossible to draw to areas beyond 2048x2048. At another point, it has a
stride limit of 8192 bytes, so you can't even draw to a subset of a
larger frame buffer.

One more bit in both of these registers would have solved the problem
for pretty much any supportable monitor configuration (the chip can only
support two single-channel DVI outputs at the most; 1920 is the widest
size supported at single-channel speeds).

For multiple monitors, the driver could allocate multiple frame buffers
and step through them one at a time with appropriate clipping. It would
be icky, but could be made to work.

Of course, the latest hardware (965G/965GM) has plenty of coordinate
space, which does tend to reduce the odds that someone will get excited
enough to go fix the driver for older chips.

The Gnome menu bar lands on Xinerama Screen 0 at this
point, which isn't currently something that you can set through RandR. On Intel the allocation to Screen 0 is determined by CRTC order and LVDS only runs on screen 1.

[http://lists.freedesktop.org/archives/xorg/2007-June/026053.html FreeDesktop.org 2007-June 026053]

[http://lists.freedesktop.org/archives/xorg/2007-August/027616.html Blanking of external screen when using xrandr]

it's checking to see if you have anything connected to the TV output.
To do that, it needs to temporarily unplug the VGA.
You can avoid this by ignoring the TV output
Section "Monitor"
Identifier "TV"
Option "Ignore" "True"
EndSection
Section "Device"
Option "monitor-TV" "TV"
EndSection
If your machine cannot ever have a TV adapter (even with a docking station),
we can add a quirk to the driver to never look at the TV output. That requires
the pci subsystem values (from lspci -n -v) to plug into the quirk table.

[http://lists.freedesktop.org/archives/xorg/2007-August/027632.html default for 'Virtual']
> Version 2.1.1-0ubuntu2 seems to set the default Virtual size (maximum
> screen size) to 1920 x 1920, if there is no entry in xorg.conf. I take
> it the maximum screen size for the i915 chipset family is 2048 x 2048,
> so why not have it at that? This would make dualscreen setups a bit easier.
The default settings is found by taking the largest resolution in either
x or y dimension and making a square from that. This allows for easy
rotation should you want to do so.
I believe you should be able to do dual screen up to 8192x8192, though
only through two monitors (Only two pipes are available for output), but
that 3D acceleration is only supported up to 2048x2048. Thus as soon as
you set your virtual size above 2048x2048, you lose 3D acceleration.
The current driver cannot reallocate the frame buffer, so whatever size
you start with is the maximum the screen can ever become, and that this
amount of physical memory is tied down for the whole X server run.

[http://lists.freedesktop.org/archives/xorg/2007-August/027670.html Primary output for Laptop + external screen]
>the desired behavior of the video
> drivers in typical laptop situations with an internal display and an
> external screen attached (extending the desktop).
>
> Currently for example the intel driver uses the external screen as the
> primary output. It is listed first with xrandr. I'm not sure if this is
> intentional or just coincidence.
It's coincidence -- the laptop hardware has two crtcs, and the LVDS can
only be driven by the second.
Note that RandR doesn't really want the order to be significant; it
would be better if the desktop environment knew about outputs and could
refer to a specific output as 'primary' or 'holds toolbar' or whatever.

[mailto:gekkoman@illimitable.com  ] Uncovered a workaround for black and white TV-out "known limitation" listed above on a intel 945GM chipset running i810-2.1.1 driver and xrandr-1.2.2. Get TV running in black and white. Then run command.

xrandr --output TV --set TV_FORMAT PAL; xrandr --output TV --mode 1024x768

substitute TV_FORMAT and mode as required. Note that the command "xrandr --output TV --set TV_FORMAT PAL" gives an error but appears to work as the subsequent mode change converts screen to colour.

=== Notes for X31,T30 / Radeon 7000,Radeon 7500 users ===
My {{X31}} has an [[ATI Mobility Radeon 7000]] with only 16MB RAM. This is not enough for big screens and DRI. Neither with [[radeon]]-default virtual size of 2048x1200, nor with my customized virtual of 2304x1024 (for one 1024x768 and one 1280x1024 screen). But this only applies for 24-bit color depth. Now I'm using only 16-bit and DRI works fine with the big virtual screen.

If you really want 24-bit depth, and do not need a bigger screen as your LCD, try setting Virtual to "1024 768", this will enable DRI in 24-bit too, but you won't be able to extend your screen anymore (well, clone will still work though).

== References ==

* XRandR 1.2
** [http://gitweb.freedesktop.org/?p=xorg/proto/randrproto.git;f=randrproto.txt;a=blob RandR 1.2 protocol specifications] - this defines the model and terminology
** [http://wiki.x.org/wiki/XDC2007Notes#head-11895d48723a8d0308571bec8829b7cc3ef87d7b In Xorg Developer Conference 2007]
** [http://burtonini.com/blog/computers/randr-2007-02-06-17-50 tutorial blog post]

* Ubuntu
** Version 7.10 (Gutsy) of Ubuntu includes support for Xorg 7.3 with RandR 1.2 [https://wiki.ubuntu.com/Xorg7.3Integration Xorg 7.3]
** [[Installing Ubuntu on a ThinkPad R60e]] for a revised and more specific version of this page
** [https://launchpad.net/ubuntu/+source/xserver-xorg-video-intel/ Ubuntu source for Intel]
** [https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/148408 gutsy version of xserver-xorg-ati has some major problems on ATI Radeon] for ([[:Category:X Series]]) and possibly others. The solution is to downgrade to the [https://launchpad.net/ubuntu/feisty/i386/xserver-xorg-video-ati/1:6.6.3-2ubuntu6 feisty version]

* X.org
** [http://lists.freedesktop.org/mailman/listinfo/xorg FreeDesktop.org mailing list]
** [http://lists.freedesktop.org/archives/xorg/ FreeDesktop.org Xorg archive]

* Useful page to supplement the minimal documentation [http://wiki.x.org/wiki/Development/Documentation/HowVideoCardsWork How video cards work]
* [http://wiki.debian.org/XStrikeForce/ReleaseNotes xserver-xorg-core and xserver-xorg-video-intel might cause some trouble but also brings nice features.]
* [http://andrew.mcmillan.net.nz/taxonomy/term/18 Seamless Monitor Hotplugging with X Windows]
* [http://www.intellinuxgraphics.org/ Linux Graphics Drivers from Intel]
* [http://zdzichubg.jogger.pl/2007/05/07/xrandr-1-2-sweetness/ blog post] with xrandr-1.2 commands and photos. Narrative is in polish.

User:BDKMPSS

2008-02-20T00:00:20Z

BDKMPSS: removed my homepage... sold the domain

==my ThinkPad '''''Workstation'''''==
ThinkPad [[:Category:X31|X31]] (Model: 2672-C2G) running [[:Category:Debian|Debian]] Testing

===Default Features===
* Intel Pentium M 1.4
* 256 MB PC2100
* 40GB Hitachi HDD
* Intel 10/100 Ethernet controller (PXE boot enabled)
* CDC slot with Modem Daughter Card (MDC)
* MiniPCI slot with Intel PRO/Wireless LAN 2100 3B Mini PCI Adapter

===Changed/Upgraded to/with:===
* 2 GB DDR 400 RAM (Kingston KVR400X64SC3A/1G) running at 266MHz
* 120 GB Hitachi TravelStar 4K120 (HTS421212H9AT00)
* Intel Pro/Wireless 2915 ABG MiniPCI card
* Modem Daughter Card (MDC) removed
* PXE boot via Bios disabled
* newest BIOS/EC-Frimware (3.02/1.08)

===why I have chosen/stick to this very model===
I think this is may the last Thinkpad purchase I ever made, not because I don't like it, actually I love it, but I don't like the "newer ones" (ThinkPad X40 and higher).

For me this this very model was/is the (second) last '''''perfect''''' one, so I never got a newer one and the last known good, the X32, is not a update which is really enhancing.
My X31 is '''''very solid''''', '''''ultraportable''''' and '''''fast enough''''' for the "office" stuff I do with it.

This is partly may also featured by the newer ones, but I miss some things of my X31 '''''very''''' much on them:
*the port-layout is much better than the "newer one". I hate ports on the sides especially on the right one, and all newer ones have all ports there...
*the LCD cover with this thick, wide, "salient" borders is absolutely robust and "unbreakable". Or at least feels like this ;)
*the overall case feels much better engineered, like I could walk over it without doing any damage, the newer ones just don't feel like this (no I am not going to try it)
*its one of the last fully IBM crafted ones, as I am not comfortable with this strange 3rd party manufacturing outsourcing somewhere in deeper China witch started right after the X31 was constructed
*Even if it first seemed like Lenovo could keep up the "legendary" quality, or even increase it to the old "pre-outsourcing" level, it now seems like this was wishful thinking

==things related to (my) ThinPads I am currently on==
I am currently start to build my own "Debian Testing on the X31"-how to, leaving the "simple installation", but aiming at the configuration.

Automatically reduce brightness

2008-02-18T21:47:29Z

BDKMPSS: /* The idea */ clarification

== The idea ==
When watching someone working with an iBook I noticed that the brightness automatically faded to the lowest level after a few seconds of inactivity. I think that this is a simple way to save power. I wrote a c-daemon which uses the XScreenSaver extension to check whether the user is active. If he is not, it lowers the brightness to a specific level. When he is active again, the brightness is reset to the previous level.

{{NOTE|This Feature is implemented in the "gnome-power-manager" (at least from gnome 2.14) and can be used without this script (Prerequisites are needed anyway). Enable it under Gnome's Power management settings ([[:Category:Debian|Debian]] Etch: Gnome-Menu/Desktop/Preferences/Power Management) -> General-Tab -> "Dim the laptop panel when idle". "when idle" in this case means, when the gnome-screensaver sets the session idle. Change time at Gnome's Screensaver settings ([[:Category:Debian|Debian]] Etch: Gnome-Menu/Desktop/Preferences/Screensaver). If you want to see the actual content of the screen when dimmed, you should disable "Activate screensaver when session is idle".}}

== Prerequisites ==
A recent kernel with the [[ibm-acpi]] driver (You should have a directory called {{path|/sys/class/backlight/ibm/}} or {{path|/sys/class/backlight/thinkpad_screen/}}).

== Installation ==
# Download the [http://www.pberndt.com/Programme/Linux/brightd/_download/latest.phpc brightness control daemon]
# Unpack it and chdir into the {{path|brightd}} directory
# Call {{cmduser|make}}
# Move the {{path|brightd}} executable into a directory like {{path|/usr/local/bin}}
# Put {{cmduser|brightd -d}} into your {{path|~/.Xsession}} (or another distro-specific startup script)
# Change the permissions of {{path|/sys/class/backlight/ibm/brightness}} so that your user can write to that file

See the README for more detailled instructions and command line parameters.

== Example installation for Gentoo linux and XFCE4 ==
The following is an example which shows how to install brightd manually. The prefered way to install brightd on gentoo is to use the [http://bugs.gentoo.org/show_bug.cgi?id=177214 ebuild from bugzilla].
$ wget -o /dev/null -O brightd.tar.bz2 "http://www.pberndt.com/raw/Programme/Linux/brightd/_download/brightd-0.3_pre2.tar.bz2"
$ tar xjf brightd.tar.bz2
$ cd brightd-*/
$ make
gcc -lX11 -lXss -o brightd brightd.c
$ make install
install -Ds brightd //usr/bin/brightd
install -D brightd.1 //usr/share/man/man1/brightd.1
$ cd /etc/xdg/xfce4
$ vi xinitrc
73Gi
/usr/local/bin/brightd -s 5 -w 2 -d
<escape>:x
$ cd /etc/init.d/
$ cat > permissions
start() {
ebegin "Setting permissions on /sys"

chmod g+w /sys/class/backlight/*/brightness
chgrp wheel /sys/class/backlight/*/brightness

eend $?
}
$ chmod a+x permissions
$ rc-update add permissions boot
$ ./permissions start

Done. Restart X to see it working. Have a look at the "-x" parameter if you intend to start the daemon from an init-script.

== Example installation for Debian Sid ==
brightd isn't yet in the official Debian archives ([http://bugs.debian.org/419329 an ITP was filled]), but you can get precompiled binaries for unstable from [[User:Zhenech|Zhenech]]'s page.

{{cmduser|wget http://debian.die-welt.net/pool/main/brightd/brightd_0.1-1_i386.deb}}

{{cmdroot|dpkg -i brightd_0.1-1_i386.deb}}

Done. Relogin into your X session and brightd will be started. You can change this and other settings by editing {{path|/etc/default/brightd}}.
{{NOTE|Changing permissions is not needed, because the binary is installed suid-root.}}

== Possible problems ==
=== brightd does not fade, screensaver deactivated ===
On my Debian Sid box, brightd can run for hours and just do nothing. This happens because it thinks the screensaver is deactivated and screen shouldn't be faded (useful while watching videos).
But in fact the screensaver isn't deactivated. To solve this problem, just execute the following command before starting bright:

{{cmduser|xset s default}}

=== brightd says it is fading, but does not ===
On my Z61m {{path|/sys/class/backlight/ibm/brightness}} is 0 after the laptop boots up. As long it is 0, brightd does nothing, because it thinks, brightness is already as low as possible, so I need to initialize the brightness-level before using brightd:

{{cmdroot|echo 7>/sys/class/backlight/ibm/brightness}}

Talk:Code/tp-fancontrol

2008-01-21T19:31:05Z

BDKMPSS: you have to use "libata", please use the discussion page on "Fan_control_scripts" (http://www.thinkwiki.org/wiki/Talk:Fan_control_scripts)

{{CodeHeader|
|filename=tp-fancontrol
|context=[[ACPI fan control script#Comprehensive_bash_script_with_fine_control_over_fan_speed]]
|author=[[User:Thinker|Thinker]] and [[User:Spiney|Spiney]]
|license=GPL v2 or later, or GFDL v1.2 or later
}}

----

Please use [[Talk:Fan_control_scripts]] to post bugs, questions and other "discussion"-items.

=== Discussion ===

Great work, guys!

I have a hitachi HTS548080M9AT00 in my T42 (2373-M1U).<br />
It DOES provide the SENSE CONDITION command<br />
(works with hdparm -H /dev/hda, or your perl script read_hitachi_temp /dev/hda)<br />
however, my system does not provide /sys/block/$DEV/device/model<br />
...so the script gives an error about not finding that file, and does the energy-taxing read.

I'm not sure where else to look for that model number ... it's in dmesg, of course. Perhaps it would be appropriate to change the script to just read that information once, from an alternate source (in the case 'model' is not provided in /sys/block/hda/device) rather than every time it polls?

My fan seems to be running pretty consistently at level 2, about 3000 rpm, whether I use the script or leave it to auto-control.

~David Emerson

You have to use the "libata"-kernel-driver for this function to work!
It is not used (by default) if you have a IDE drive (as you do).
You can use it, but your drive than appears as sda, not hda.

Please use [[Talk:Fan_control_scripts]] for discussions about the script and MOVE both our posts there. I think your question was asked there some time ago.

--[[User:BDKMPSS|BDKMPSS]] 20:31, 21 January 2008 (CET)

Talk:Hard disk drives

2007-11-02T14:36:50Z

BDKMPSS: /* Modding ZIF connectors for AT connection in X41 */ "hint" to IBM/Lenovo Support

Could anybody just give a brief hind on how to replace the hard disc? I haven't gotten a single clue, and I seem not to be able to find any documentation on that topic. I would really be greatful for any help whatsoever. :)

----
I wonder where you are looking for that documentation.
*the printed manuals that should have come with your ThinkPad include that documentation
*the Access IBM help application in Windows includes that documentation
*the hardware maintenance manuals linked from almost every model page in ThinkWiki includes that documentation
*googling for "thinkpad replace harddisk" has [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-44101 this] link in 5th position and replacing "thinkpad" with your actual model will for sure lead you to more specific documentation

I guess you've just been waiting for someone to throw it into your letter box.

[[User:Wyrfel|Wyrfel]] 14:11, 4 Nov 2005 (CET)
----

== FUJITSU MHV2120AH suitable for T41? ==

Hello guys,

I've bought a Fujitsu MHV2120AH. Has anyone experience whether that harddisk is suitable for the Thinkpad T41? It seems that I can't insert the harddisk entirely.

Thanks a lot.
Marcus

== Modding ZIF connectors for AT connection in X41 ==

I've been searching online for a new hard disk for my Thinkpad X41 (2525), it has one of those little 1.8" TravelStar drives that seems to have a PATA interface (rows of pins) on it. It looks like these 1.8" drives have been pretty much discontinued by Hitachi and they only sell the same disk but with a ZIF (Zero Insertion Force) connector.

Does anyone know if it is possible to get a PATA to ZIF connector to work in a Thinkpad?
or indeed any source of the HTC***AT drives?

--[[User:Callum|Callum]] 15:44, 26 September 2007 (UTC)

There are no ZIF-2-PATA adapters (which would fit into the notebook), as far as I can tell.
The 1.8" HDDs are produced with ZIF or PATA and all system manufacturers alway use these connectors directly.
I think Hitachi is/was the only HDD-manufacturer which offered PATA-Interfaces.

Have you tried to get the HDD through IBM/Lenovo?

They offer parts for at least 5 Years for most products (IBM does, maybe Lenovo as well?). Sure they are a little overpriced, but any replacement part I bought for my X31 was "in range" and one was surprisingly cheap.

--[[User:BDKMPSS|BDKMPSS]] 14:36, 2 November 2007 (UTC)

== 1.8" drives ==

I recommend once your Deathstar 1.8" drive dies, just use an external drive like I do here:

http://www.flickr.com/photos/hendry/1508630532/

X40s can boot Linux fine from external USB hard drives.

If you want to attempt to pull data off an old 1.8" drive, you can actually use an 2.5" IDE USB enclosure like I do here:

http://www.flickr.com/photos/hendry/1809483099/

[[User:Hendry|Hendry]] 21:02, 31 October 2007 (UTC)

This does not solve the problem, because you have to carry the external hard drive where ever you go and use it every time, which successfully defeats the concept of a notebook, especially of any sub-notebook like the X-Series ones.

Its better to do it, then using your ThinkPad as a paperweight, but no real solution of roadwarriors.

--[[User:BDKMPSS|BDKMPSS]] 14:16, 2 November 2007 (UTC)

Talk:Hard disk drives

2007-11-02T14:16:30Z

BDKMPSS: /* 1.8" drives */ this is a very wacky workaround

Could anybody just give a brief hind on how to replace the hard disc? I haven't gotten a single clue, and I seem not to be able to find any documentation on that topic. I would really be greatful for any help whatsoever. :)

----
I wonder where you are looking for that documentation.
*the printed manuals that should have come with your ThinkPad include that documentation
*the Access IBM help application in Windows includes that documentation
*the hardware maintenance manuals linked from almost every model page in ThinkWiki includes that documentation
*googling for "thinkpad replace harddisk" has [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-44101 this] link in 5th position and replacing "thinkpad" with your actual model will for sure lead you to more specific documentation

I guess you've just been waiting for someone to throw it into your letter box.

[[User:Wyrfel|Wyrfel]] 14:11, 4 Nov 2005 (CET)
----

== FUJITSU MHV2120AH suitable for T41? ==

Hello guys,

I've bought a Fujitsu MHV2120AH. Has anyone experience whether that harddisk is suitable for the Thinkpad T41? It seems that I can't insert the harddisk entirely.

Thanks a lot.
Marcus

== Modding ZIF connectors for AT connection in X41 ==

I've been searching online for a new hard disk for my Thinkpad X41 (2525), it has one of those little 1.8" TravelStar drives that seems to have a PATA interface (rows of pins) on it. It looks like these 1.8" drives have been pretty much discontinued by Hitachi and they only sell the same disk but with a ZIF (Zero Insertion Force) connector.

Does anyone know if it is possible to get a PATA to ZIF connector to work in a Thinkpad?
or indeed any source of the HTC***AT drives?

--[[User:Callum|Callum]] 15:44, 26 September 2007 (UTC)

== 1.8" drives ==

I recommend once your Deathstar 1.8" drive dies, just use an external drive like I do here:

http://www.flickr.com/photos/hendry/1508630532/

X40s can boot Linux fine from external USB hard drives.

If you want to attempt to pull data off an old 1.8" drive, you can actually use an 2.5" IDE USB enclosure like I do here:

http://www.flickr.com/photos/hendry/1809483099/

[[User:Hendry|Hendry]] 21:02, 31 October 2007 (UTC)

This does not solve the problem, because you have to carry the external hard drive where ever you go and use it every time, which successfully defeats the concept of a notebook, especially of any sub-notebook like the X-Series ones.

Its better to do it, then using your ThinkPad as a paperweight, but no real solution of roadwarriors.

--[[User:BDKMPSS|BDKMPSS]] 14:16, 2 November 2007 (UTC)

Issues with the Wiki

2007-10-21T00:32:48Z

BDKMPSS: /* Your signature with timestamp button */ i'm sorry

This page is a provisorium. It's a list of things that are going wrong after the update to help [[User:akw|Akw]] track and fix them.

== Suggestions and requests ==

=== Enabling user Javascript and CSS for MediaWiki ===

Could ThinkWiki's MediaWiki installation get these options enabled (typically set in LocalSettings.php):

* [http://www.mediawiki.org/wiki/Manual:%24wgAllowUserCss wgAllowUserCss]
* [http://www.mediawiki.org/wiki/Manual:%24wgAllowUserJs wgAllowUserJs]

These options allow users to have their own custom Javascript and CSS. I (and others) like to have our own custom themes and Javascript when working with MediaWiki-powered websites.

--[[User:SamatJain|SamatJain]] 22:04, 28 July 2007 (UTC)

This is a great security risk. What is it good for?

--[[User:Thinker|Thinker]] 00:14, 29 July 2007 (UTC)

It allowers users to set their own customizations via Javascript and CSS. It's a minor security risk which is why MediaWiki ships with it off, but Wikipedia and other popular websites using MediaWiki ship with it on.

--[[User:SamatJain|SamatJain]] 20:49, 29 July 2007 (UTC)

There is nothing minor about it. The web security model is site-wise when dealing with MediaWiki, there is no easy (read: manageable) way for an user, even one that uses NoScript+Firefox or something else equally powerful, to really filter out trusted from untrusted content when you start allowing people to write JavaScript into a Wiki.

CSS is less of a problem, but it could still hork the site if one is not careful, and MediaWiki already allows us to change the pages well enough. If you need to change thinkwiki CSS for your own viewing pleasure, any browser worth its bytes lets you layer your own CSS on top of a site's. I would not be strongly against enabling CSS, but I don't see any reason to do it, either.

JavaScript submissions, OTOH, is something that must remain disabled. IMO, if you really can't survive without tacking different JavaScript code than what thinkwiki already has, you can use greasemonkey or some other such system to do it in your own browser.

If thinkwiki starts allowing users to set javascript on their pages, I would have to block javascript completely on my side, for example. At that time, it is likely I will just go away. Other contributors might feel the same. It is not that I have anything against JavaScript. It is the fact that I cannot *trust* user-submitted JavaScript.

--[[User:Hmh|hmh]] 12:26, 30 July 2007 (UTC)

These options only enable Javascript and CSS for user pages, i.e. for User:User/Monobook.css and User/Monobook.js, specifically ''not'' for other pages. Disabling these options was done by default as a precaution against XSS vulnerabilies [http://www.gossamer-threads.com/lists/wiki/mediawiki-announce/28572 long since been fixed]. Unfortunately, while I agree with you about disabling user Javascript as a precaution, I do not think the wgAllowUserCss option has any effect unless the wgAllowUserJs option is enabled as well.

--[[User:SamatJain|SamatJain]] 18:52, 30 July 2007 (UTC)

I don't get the point ether.
Why you want to use css/javascript on user pages? You always say why you think its no problem, but not what you want to do. If you need some funky looking stuff or buttons there you should use something like myspace. This Wikis (and almost all other) purpose is collecting the main - Thinkpad - content, not something cool/funky/special on userpages

As Hmh, I would block js immediately and may leave the site, even if its only on userpages, because I don't want to mind clicking "the false links"

--[[User:BDKMPSS|BDKMPSS]], 30 July 2007

[http://en.wikipedia.org/wiki/MediaWiki#Customisation Wikipedia's section on MediaWiki customization] describes some of the extensions and addons available. For example, [http://en.wikipedia.org/wiki/User:Cacycle/wikEd wikiEd] is a WYSIWYG editor such that instead of having to remember MediaWiki's markup, they use an editor that's only enabled for use them. This kind of extending is difficult to do with Stylish or Greasemonkey.

I'll repeat, since I've not been apparently misunderstood:
* Users ''won't'' be able to add Javascript or CSS to arbitrary pages, only those under their user profile (these are called "user pages")
* Only those users logged in will see these their own changes, no other users will.
Given these things, I don't understand why people need to threaten they're going to stop contributing to ThinkWiki? There isn't a way you're going to turn ThinkWiki into MySpace. If you don't use specifically use any CSS or Javascript through these features, it will not effect you at all.

What I personally want to do, I want to use a MediaWiki modification I wrote, [http://meta.wikimedia.org/wiki/Gallery_of_user_styles#Nullbook Nullbook]. I feel as if I am much more efficient with this theme.

--[[User:SamatJain|SamatJain]] 21:58, 30 July 2007 (UTC)

I don't understand what exactly $wgAllowUserJs is supposed to do, and its [http://www.mediawiki.org/wiki/Manual:%24wgAllowUserCss documentation] is worthless. The crux of the matter is this: if those features are enabled, is there any way ''you'' can cause ''me'' to execute JavaScript (or apply CSS) that ''you'' wrote, in ''any'' page on ThinkWiki? If not, why?

--[[User:Thinker|Thinker]] 22:17, 30 July 2007 (UTC)

[http://meta.wikimedia.org/wiki/User_styles User styles on the MediaWiki site] describes a bit more how these options work and what is provided to any modification that depends upon them. Unless there exist security-related bugs (which is the reason these features are tagged possible security risks, and why they are proactively disabled by default), by design, no, there is no way that I can cause you to execute Javascript or apply CSS that I had put into one of my own "user pages" (i.e. those under [[User:SamatJain]]).

--[[User:SamatJain|SamatJain]] 22:53, 30 July 2007 (UTC)

'''If and only if''' such javascript and css changes are limited so that the user who made them is the only one who gets them, then I have nothing against it.

That said, I'd prefer if the relevant mediawiki code was audited a bit before it is enabled.

PS: Whomever is doing it, please stop screwing around with the formatting: there must be one empty line before and after signatures, it makes the dialog a '''lot''' more readable.

--[[User:Hmh|hmh]] 02:53, 1 August 2007 (UTC)

== Troubles encountered ==

=== Problems with Language.php ===

Some pages are not happy with mediawiki 1.11.0, and return:
Warning: array_slice() [function.array-slice]: The first argument should be an array in /home/thinkwiki/htdocs/mediawiki-1.11.0/languages/Language.php on line 1153

For an example, see: [[User:Akw | Akw's user page]]

--[[User:Hmh|hmh]] 01:14, 20 October 2007 (UTC)

=== Problem with cmdroot ===

Following String is not handled correct by template cmdroot:
"fakeroot make-kpkg --initrd --revision=thinkpad.1.0 kernel_image"

see here:
{{cmdroot|fakeroot make-kpkg --initrd --revision=thinkpad.1.0 kernel_image}}

=== Can not open page to edit without introducing modifications ===

If I open the [[X31]] model page and without touching anything I hit preview, the div token is decomposed and appears in the preview page, and of course, the photo is not in the right place.

--[[User:Ungoliant|Ungoliant]] 19:24, 20 February 2007 (CET)

=== Uploading SVG files ===

'''Can not upload SVG'''
I get the upload warning:
".svg" is not a recommended image file format.
--[[User:Matt|Matt]] 14:02, 3 December 2006 (CET)

=== SpamBlackList not working ===

* [[ThinkWiki:SpamBlackList]] does not appear to work anymore

--[[User:Tonko|Tonko]] 03:40, 11 March 2006 (CET)

=== Multiline cmdresult template ===

You can't (easliy do a multiline {{cmdresult|cmdresult}}, can you? See:

{{cmdresult|foo
bar
baz}}

or

{{cmdresult|foo
bar (after whitespace)
baz (after whitespace)}}

This works (but is not so nice)

{{cmdresult|foo

bar (after empty line)

baz (after empty line)}}

Any suggestions?

--[[User:Pebolle|Paul Bolle]] 10:27, 24 January 2006 (CET)

----

I think the best way is to use single cmdresult calls for each line and prefix them with a colon. Like so:
<pre><nowiki>
:{{cmdresult|foo}}
:{{cmdresult|bar}}
:{{cmdresult|baz}}
</nowiki></pre>, which results in
:{{cmdresult|foo}}
:{{cmdresult|bar}}
:{{cmdresult|baz}}

Alternatively, you can use <br /> at the ende of each line within one call, like this:
<tt><nowiki>{{cmdresult|foo<br />
bar<br />
baz}}</nowiki></tt>
, which will result in

{{cmdresult|foo<br />
bar<br />
baz}}

--[[User:Wyrfel|Wyrfel]] 12:13, 24 January 2006 (CET)

=== Server time out-of-sync ===

The server time would appear to be off a lot, is it possible to setup ntpd, or to run ntpdate every hour or so using cron?

--[[User:Tonko|Tonko]] 05:11, 22 February 2006 (CET)

=== Missing imagemagick on server ===

Error creating thumbnail: /home/thinkwiki/htdocs/mediawiki-1.10.0/bin/ulimit4.sh: line 4: /usr/bin/convert: No such file or directory

I think the computer this wiki is running on is missing the imagemagick software tools especially convert to create thumbnails of images

--[[User:Markusw|Markusw]] 10:21, 26 August 2007 (UTC)

=== Your signature with timestamp button ===

This Button simply doesn't work, it adds <nowiki>--~~~~</nowiki><br>
I think its a bunch on javascript so I may add:<br>
I use Firefox (branded as Icewasel) on Debian Testing<br>
Preferences:<br>
Raw signatures (without automatic link) OFF<br>
Show edit toolbar (JavaScript) ON<br>
(Oh... Yes its javascript)

EDIT:
Even in my Windows XP SP2 Virtual Machine it don't work in Internet Explorer 7.0

--[[User:BDKMPSS|BDKMPSS]] 29 July 2007

I have been using this button for quite a while now, and it seems to work just fine. It does insert <nowiki>--~~~</nowiki>, but upon submitting previews or saving the page, it gets converted into my signature.

--[[User:Hmh|hmh]] 01:27, 20 October 2007 (UTC)

hm... (wow a nice joke...)

lets try this

--[[User:BDKMPSS|BDKMPSS]] 00:30, 21 October 2007 (UTC)

OK, its all fine... I'm sorry but this seems to be extremely non-intuitive...

--[[User:BDKMPSS|BDKMPSS]] 00:32, 21 October 2007 (UTC)

== Problems fixed ==

* List emptied, since everything in it was more than one year old

Issues with the Wiki

2007-10-21T00:30:43Z

BDKMPSS: /* Your signature with timestamp button */ try

This page is a provisorium. It's a list of things that are going wrong after the update to help [[User:akw|Akw]] track and fix them.

== Suggestions and requests ==

=== Enabling user Javascript and CSS for MediaWiki ===

Could ThinkWiki's MediaWiki installation get these options enabled (typically set in LocalSettings.php):

* [http://www.mediawiki.org/wiki/Manual:%24wgAllowUserCss wgAllowUserCss]
* [http://www.mediawiki.org/wiki/Manual:%24wgAllowUserJs wgAllowUserJs]

These options allow users to have their own custom Javascript and CSS. I (and others) like to have our own custom themes and Javascript when working with MediaWiki-powered websites.

--[[User:SamatJain|SamatJain]] 22:04, 28 July 2007 (UTC)

This is a great security risk. What is it good for?

--[[User:Thinker|Thinker]] 00:14, 29 July 2007 (UTC)

It allowers users to set their own customizations via Javascript and CSS. It's a minor security risk which is why MediaWiki ships with it off, but Wikipedia and other popular websites using MediaWiki ship with it on.

--[[User:SamatJain|SamatJain]] 20:49, 29 July 2007 (UTC)

There is nothing minor about it. The web security model is site-wise when dealing with MediaWiki, there is no easy (read: manageable) way for an user, even one that uses NoScript+Firefox or something else equally powerful, to really filter out trusted from untrusted content when you start allowing people to write JavaScript into a Wiki.

CSS is less of a problem, but it could still hork the site if one is not careful, and MediaWiki already allows us to change the pages well enough. If you need to change thinkwiki CSS for your own viewing pleasure, any browser worth its bytes lets you layer your own CSS on top of a site's. I would not be strongly against enabling CSS, but I don't see any reason to do it, either.

JavaScript submissions, OTOH, is something that must remain disabled. IMO, if you really can't survive without tacking different JavaScript code than what thinkwiki already has, you can use greasemonkey or some other such system to do it in your own browser.

If thinkwiki starts allowing users to set javascript on their pages, I would have to block javascript completely on my side, for example. At that time, it is likely I will just go away. Other contributors might feel the same. It is not that I have anything against JavaScript. It is the fact that I cannot *trust* user-submitted JavaScript.

--[[User:Hmh|hmh]] 12:26, 30 July 2007 (UTC)

These options only enable Javascript and CSS for user pages, i.e. for User:User/Monobook.css and User/Monobook.js, specifically ''not'' for other pages. Disabling these options was done by default as a precaution against XSS vulnerabilies [http://www.gossamer-threads.com/lists/wiki/mediawiki-announce/28572 long since been fixed]. Unfortunately, while I agree with you about disabling user Javascript as a precaution, I do not think the wgAllowUserCss option has any effect unless the wgAllowUserJs option is enabled as well.

--[[User:SamatJain|SamatJain]] 18:52, 30 July 2007 (UTC)

I don't get the point ether.
Why you want to use css/javascript on user pages? You always say why you think its no problem, but not what you want to do. If you need some funky looking stuff or buttons there you should use something like myspace. This Wikis (and almost all other) purpose is collecting the main - Thinkpad - content, not something cool/funky/special on userpages

As Hmh, I would block js immediately and may leave the site, even if its only on userpages, because I don't want to mind clicking "the false links"

--[[User:BDKMPSS|BDKMPSS]], 30 July 2007

[http://en.wikipedia.org/wiki/MediaWiki#Customisation Wikipedia's section on MediaWiki customization] describes some of the extensions and addons available. For example, [http://en.wikipedia.org/wiki/User:Cacycle/wikEd wikiEd] is a WYSIWYG editor such that instead of having to remember MediaWiki's markup, they use an editor that's only enabled for use them. This kind of extending is difficult to do with Stylish or Greasemonkey.

I'll repeat, since I've not been apparently misunderstood:
* Users ''won't'' be able to add Javascript or CSS to arbitrary pages, only those under their user profile (these are called "user pages")
* Only those users logged in will see these their own changes, no other users will.
Given these things, I don't understand why people need to threaten they're going to stop contributing to ThinkWiki? There isn't a way you're going to turn ThinkWiki into MySpace. If you don't use specifically use any CSS or Javascript through these features, it will not effect you at all.

What I personally want to do, I want to use a MediaWiki modification I wrote, [http://meta.wikimedia.org/wiki/Gallery_of_user_styles#Nullbook Nullbook]. I feel as if I am much more efficient with this theme.

--[[User:SamatJain|SamatJain]] 21:58, 30 July 2007 (UTC)

I don't understand what exactly $wgAllowUserJs is supposed to do, and its [http://www.mediawiki.org/wiki/Manual:%24wgAllowUserCss documentation] is worthless. The crux of the matter is this: if those features are enabled, is there any way ''you'' can cause ''me'' to execute JavaScript (or apply CSS) that ''you'' wrote, in ''any'' page on ThinkWiki? If not, why?

--[[User:Thinker|Thinker]] 22:17, 30 July 2007 (UTC)

[http://meta.wikimedia.org/wiki/User_styles User styles on the MediaWiki site] describes a bit more how these options work and what is provided to any modification that depends upon them. Unless there exist security-related bugs (which is the reason these features are tagged possible security risks, and why they are proactively disabled by default), by design, no, there is no way that I can cause you to execute Javascript or apply CSS that I had put into one of my own "user pages" (i.e. those under [[User:SamatJain]]).

--[[User:SamatJain|SamatJain]] 22:53, 30 July 2007 (UTC)

'''If and only if''' such javascript and css changes are limited so that the user who made them is the only one who gets them, then I have nothing against it.

That said, I'd prefer if the relevant mediawiki code was audited a bit before it is enabled.

PS: Whomever is doing it, please stop screwing around with the formatting: there must be one empty line before and after signatures, it makes the dialog a '''lot''' more readable.

--[[User:Hmh|hmh]] 02:53, 1 August 2007 (UTC)

== Troubles encountered ==

=== Problems with Language.php ===

Some pages are not happy with mediawiki 1.11.0, and return:
Warning: array_slice() [function.array-slice]: The first argument should be an array in /home/thinkwiki/htdocs/mediawiki-1.11.0/languages/Language.php on line 1153

For an example, see: [[User:Akw | Akw's user page]]

--[[User:Hmh|hmh]] 01:14, 20 October 2007 (UTC)

=== Problem with cmdroot ===

Following String is not handled correct by template cmdroot:
"fakeroot make-kpkg --initrd --revision=thinkpad.1.0 kernel_image"

see here:
{{cmdroot|fakeroot make-kpkg --initrd --revision=thinkpad.1.0 kernel_image}}

=== Can not open page to edit without introducing modifications ===

If I open the [[X31]] model page and without touching anything I hit preview, the div token is decomposed and appears in the preview page, and of course, the photo is not in the right place.

--[[User:Ungoliant|Ungoliant]] 19:24, 20 February 2007 (CET)

=== Uploading SVG files ===

'''Can not upload SVG'''
I get the upload warning:
".svg" is not a recommended image file format.
--[[User:Matt|Matt]] 14:02, 3 December 2006 (CET)

=== SpamBlackList not working ===

* [[ThinkWiki:SpamBlackList]] does not appear to work anymore

--[[User:Tonko|Tonko]] 03:40, 11 March 2006 (CET)

=== Multiline cmdresult template ===

You can't (easliy do a multiline {{cmdresult|cmdresult}}, can you? See:

{{cmdresult|foo
bar
baz}}

or

{{cmdresult|foo
bar (after whitespace)
baz (after whitespace)}}

This works (but is not so nice)

{{cmdresult|foo

bar (after empty line)

baz (after empty line)}}

Any suggestions?

--[[User:Pebolle|Paul Bolle]] 10:27, 24 January 2006 (CET)

----

I think the best way is to use single cmdresult calls for each line and prefix them with a colon. Like so:
<pre><nowiki>
:{{cmdresult|foo}}
:{{cmdresult|bar}}
:{{cmdresult|baz}}
</nowiki></pre>, which results in
:{{cmdresult|foo}}
:{{cmdresult|bar}}
:{{cmdresult|baz}}

Alternatively, you can use <br /> at the ende of each line within one call, like this:
<tt><nowiki>{{cmdresult|foo<br />
bar<br />
baz}}</nowiki></tt>
, which will result in

{{cmdresult|foo<br />
bar<br />
baz}}

--[[User:Wyrfel|Wyrfel]] 12:13, 24 January 2006 (CET)

=== Server time out-of-sync ===

The server time would appear to be off a lot, is it possible to setup ntpd, or to run ntpdate every hour or so using cron?

--[[User:Tonko|Tonko]] 05:11, 22 February 2006 (CET)

=== Missing imagemagick on server ===

Error creating thumbnail: /home/thinkwiki/htdocs/mediawiki-1.10.0/bin/ulimit4.sh: line 4: /usr/bin/convert: No such file or directory

I think the computer this wiki is running on is missing the imagemagick software tools especially convert to create thumbnails of images

--[[User:Markusw|Markusw]] 10:21, 26 August 2007 (UTC)

=== Your signature with timestamp button ===

This Button simply doesn't work, it adds <nowiki>--~~~~</nowiki><br>
I think its a bunch on javascript so I may add:<br>
I use Firefox (branded as Icewasel) on Debian Testing<br>
Preferences:<br>
Raw signatures (without automatic link) OFF<br>
Show edit toolbar (JavaScript) ON<br>
(Oh... Yes its javascript)

EDIT:
Even in my Windows XP SP2 Virtual Machine it don't work in Internet Explorer 7.0

--[[User:BDKMPSS|BDKMPSS]] 29 July 2007

I have been using this button for quite a while now, and it seems to work just fine. It does insert <nowiki>--~~~</nowiki>, but upon submitting previews or saving the page, it gets converted into my signature.

--[[User:Hmh|hmh]] 01:27, 20 October 2007 (UTC)

hm... (wow a nice joke...)

lets try this

--[[User:BDKMPSS|BDKMPSS]] 00:30, 21 October 2007 (UTC)

== Problems fixed ==

* List emptied, since everything in it was more than one year old

How to reduce power consumption

2007-10-09T17:47:33Z

BDKMPSS: /* CPU */ added wiki link to powertop

Reducing system power consumption will extend battery life, reduce system
temperature and (on some models) reduce system fan noise.
Power consumption can be greatly improved from a stock distribution configuration
to a fine tuned system. The general rules are :
* Unload drivers for unused devices (ie. USB 1.1, Yenta/PCMCIA, Wireless, IRDA, Bluetooth, ...)
* Reduce polling on devices (drives, USB subsystem, nvram, ...)
* Reduce hard drive activity
* Reduce LCD brightness to the minimum you can stand
* Reduce CPU wakeups, so it can stay longer in deep power saving c-states

==Tools==
Arjan van de Ven's [[PowerTOP]] utility
is a gold mine to improve energy efficiency, but is almost only CPU-oriented. This tool helps to easily detect
the top power offenders, both userland and kernel modules, which prevent the use of CPU power saving mechanisms and sometime suggest
fixes accordingly.
PowerTOP users collected some [http://www.linuxpowertop.org/known.php tips & tricks]
and an informative [http://www.linuxpowertop.org/faq.php faq].

Alternatively (or complementary) to PowerTOP, running <code>strace -p $(pidof yourapp)</code>
for all your favorite or background running applications while they are expected to be
idle, will show the misbehaviors.

Beside CPU wakeups, disks spins are also power angry. To detect what make your disk spinning,

<code>
sysctl vm.block_dump=1
</code>

will list all applications causing disks wakeups on the kernel's dmesg.
Other useful tools for this purpose are blktrace, iostat and lm-profiler
(from laptop-mode-tools suite).

==BIOS settings==
Some Thinkpad BIOS (like 2.08 BIOS on {{X40}}) offer two very lame options,
with a very misleading online help (saying "Usually not needed"). That's

<code>
CPU power management: (default disabled)
PCI bus power management: (default disabled)
</code>

You should indeed enable them, else the deepest C3 and C4 ACPI C-states
are disabled.

==CPU==
Look at:
* [[How to make use of Dynamic Frequency Scaling]]
* [[Pentium M undervolting and underclocking]]

A good thing to keep in mind is that every CPU wakeup, even if it's for
a trivial light job, reduce the time the CPU stays on a deep power
saving C-state (like C3 or C4). Therefore you should ensure your applications
stay really idle when they meant to be idle (track shorts select timeouts
in loop, etc. with [[PowerTOP]]).

Also note that manually locking the CPU in the lowest P-state (frequency)
available is '''not''' an efficient way to improve battery lifetime. This will
cause the CPU to stay longer in C0 (power angry C-state) doing hard work when
there is something to do, while it could have done this work faster by augmenting
the CPU freq, and returned back faster to a deeper, economic, C-state and to a
lower frequency (P-state).
The best is to let the kernel select the appropriates CPU frequencies by itself
with the help of in kernel CPU governors.
Have a look at [http://www.bughost.org/pipermail/power/2007-May/000166.html this explanation]
from Intel's kernel developer Arjan van de Ven.

==Kernel settings and patches==

===General settings===
The 2.6.21 kernel brought some very effective changes (like dynticks). If
it's not already on your distribution and you value power efficiency, you
may think about compiling it (or a more recent one) yourself.

Here are a few options (beside the ACPI and APM related one) that matter to
reduce power consumption or to help diagnosing consumers:

<code>
# From PowerTOP's FAQ:
CONFIG_NO_HZ
CONFIG_HIGH_RES_TIMERS
CONFIG_HPET
CONFIG_CPU_FREQ_GOV_ONDEMAND
CONFIG_USB_SUSPEND
CONFIG_SND_AC97_POWER_SAVE
CONFIG_TIMER_STATS
CONFIG_ACPI_BATTERY
CONFIG_CPU_FREQ_STAT
# Not from the PowerTOP FAQ:
CONFIG_BLK_DEV_IO_TRACE
CONFIG_X86_ACPI_CPUFREQ
CONFIG_X86_SPEEDSTEP_CENTRINO
CONFIG_X86_SPEEDSTEP_ICH
CONFIG_X86_SPEEDSTEP_SMI
CONFIG_X86_ACPI_CPUFREQ
</code>

Those options are already in Fedora Core 7 and Ubuntu Gutsy (not Feisty) default i686 kernels.
PowerTOP FAQ also suggest to '''disable'''
CONFIG_IRQBALANCE et CONFIG_ACPI_DEBUG.

Also, you need to properly set APM and ACPI. Look at:
* [[Power Management]]
* [[How to make use of Power Management features]]

===Useful Patchs===

Thomas Gleixner High Resolution Timers (hrt) patchset brings many improvements,
like the cpuidle work and Udo A. Steinberg and Venki Pallipadi "force
enable HPET" patches (non HPET timers causes about 20-40 CPU wakeups/second, but
HPET is often hidden by the BIOS due to Windows XP deficiencies).
See http://www.tglx.de/projects/hrtimers/

Kristen Carlson Accardi from Intel has a patchset to turn on "Aggressive
Link Power Management" (ALPM) for the AHCI driver (for SATA bus). See:
http://www.kernel.org/pub/linux/kernel/people/kristen/patches/SATA/alpm/

The [[HDAPS]] disk protection systems can reduce battery life.
Matthew Garrett provides [http://www.linuxpowertop.org/patches/hdaps.patch a patch]
that prevents hdaps kernel module to generate interrupts when
this feature isn't used.

===Useful sysctls===
The meaning of those settings is explained case by case on the relevant
sections of this document. But for convenience sake, we group them here too.

Note that the "ondemand" scaling governor is recommended by Intel developers
for energy efficiency: it's expected to be more efficient than the "powersave"
governor, or than userspace daemons (like cpufreq-utils, cpufreqd, powernowd...).
Look [http://www.bughost.org/pipermail/power/2007-May/000071.html here],
[http://www.bughost.org/pipermail/power/2007-May/000073.html here], or
[http://www.bughost.org/pipermail/power/2007-May/000166.html here] for a
kernel developer explanation about "ondemand" being better on modern Intel CPUs.

The "link_power_management_policy" tunable won't be available unless you
run Kirsten patchset, have an Intel AHCI compatible chipset, and use SATA drives.

<code>
echo 5 > /proc/sys/vm/laptop_mode
echo 0 > /proc/sys/kernel/nmi_watchdog
echo Y > /sys/module/snd_ac97_codec/parameters/power_save
echo 1 > /sys/devices/system/cpu/sched_mc_power_savings
echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo min_power > /sys/class/scsi_host/host0/link_power_management_policy
echo min_power > /sys/class/scsi_host/host1/link_power_management_policy
echo 1500 > /proc/sys/vm/dirty_writeback_centisecs
</code>

If you're running a kernel older than 2.6.22 do this. Not needed for kernels 2.6.22 onward:

<code>
cd /sys/devices/system/cpu/cpu0/cpufreq
cat ondemand/sampling_rate_max > ondemand/sampling_rate
</code>

==ATA drives==
Hard drives and CDRom drives spinning is very costly. To improve battery
lifetime, you should reduce disks access (or devices polling) the more you
can.

===Hard Drives===
The files access time update, while mandated by POSIX, is causing lots of
disks access; even accessing files on disk cache may wake the ATA or USB
bus. If you don't use this feature, disable it via:

<code>
mount -o remount,noatime / # and so on for all mounted fs
</code>

The laptop_mode reduce disk usage by regrouping writes. You should enable
it, at least while on battery. See [[Laptop-mode]] for more details:

<code>
echo 5 > /proc/sys/vm/laptop_mode
</code>

The default kernel dirty page writeback frequency is very conservative. On
a laptop running on battery, one might find more appropriate to reduce it:

<code>
echo 1500 > /proc/sys/vm/dirty_writeback_centisecs
</code>

Some power saving hard drives features can be activated with hdparm.
For more details look at [[How to make use of Power Management features]] :

<code>
hdparm -B 1 -S 12 /dev/sda # and/or any other disk device
</code>

===Optical drive===
The optical drive is reported to consume power even when not accessed. See

* [[How to hotswap UltraBay devices|Eject the UltraBay optical drive]], or just turn off its power supply (i.e., run the appropriate eject script but leave the drive inserted).
* [[How to set optical drive speed|Reduce the spinning speed of the optical drive]].

The hald daemon polling tends to maintain the ATA buses out of power saving
modes, and to wakeup CDROM drive. If you have a recent hald version, you
can stop this polling when on battery:

<code>
hal-disable-polling /dev/scd0 # or whatever your CD drive is
</code>

If your hald is not recent enough, consider stopping it on battery.

==LCD Backlight/Brightness==
The LCD backlight is one of the very major power drain.
Reducing brightness to the lowest readable
level will save a lot of battery lifetime. Also, don't forget to configure
your screen saver to shutdown the screen backlight (rather than displaying some
eye candy), when no activity for a few minutes.

You can also let the system [[automatically reduce brightness]] after a
period of inactivity.

If you're choosing your Thinkpad laptop model, keep in mind that the screen
size affect the battery time greatly: more power needed for larger screens.

==Graphic controllers==
All xorg Thinkpad graphics chipsets drivers (ati, radeon, fglrx, i810) have
the same bug causing very frequent CPU wakeups when DRI is activated, even
when you don't use any 3D application.
This problem is partly fixed on xorg git tree but not released as of xorg
7.2. If you value more battery than 3D, you should disable DRI: put this on
the /etc/X11/xorg.conf "Device" of you graphic controller:

<code>
Option "NoDRI"
</code>

Also be sure that DPMS is working: <code>grep DPMS /var/log/Xorg.0.log</code>
should output "DPMS enabled". If not, put <code>Option "DPMS"</code> in your config.

On recent xrandr/xorg versions, you can disable the TV output when you're
not using it (it's known to consume power) :

<code>
xrandr --output TV -off
</code>

When you don't have an external monitor plugged, disable CRT and DVI output
(for some, this can make a difference in power usage) :
<code>
echo crt_disable > /proc/acpi/ibm/video
echo dvi_disable > /proc/acpi/ibm/video
</code>

Some drivers have specials power saving mode, and/or allows underclocking the GPU. See also:
* [[How to make use of Graphics Chips Power Management features]], or with [[Rovclock]] on ATI.
* [[Problem with high power drain in ACPI sleep]]

==USB Subsystem==
The kernel support an efficient USB 2.0 power saving feature if you enabled
CONFIG_USB_SUSPEND. This may not trigger in when you have an USB device
plugged (and beside, USB devices tends to suck power on their own), so avoid
using such devices when on battery.

USB 1.1 is worst. It needs polling the bus frequently, hence can't really go
in a low power mode when you enabled it, even if you don't have any device
plugged. You'd better remove it when you don't use a 1.1 device:

<code>
rmmod uhci_hcd
</code>

If you don't intend to use any USB 1.1 device (unfortunately, the built-in bluetooth and fingerprint-reader are USB 1.1 devices), the USB 1.1 support can also be totaly avoided. On Debian and derivatives, just do:

<code>
echo "blacklist uhci_hcd" >> /etc/modprobe.d/blacklist
</code>

==Sound==
ALSA has a power saving feature that should be enabled on your kernel
(CONFIG_SND_AC97_POWER_SAVE). Note that this low power mode won't trigger in
unless you muted all sound inputs (micro, line in etc.). This feature has
to be activated with:

<code>
amixer set Line mute nocap
amixer set Mic mute nocap
echo Y > /sys/module/snd_ac97_codec/parameters/power_save
</code>

More radical: you can unload all sound related modules when you are on
battery, or mute the sound system (echo mute > /proc/acpi/ibm/volume).

Seel also [[How to enable AC97 power saving]].

==Wireless Interface==
Wireless network consume a lot of power.
To save power on ipw adapters, you can kill the Wi-Fi radio when it's not in use:

<code>
echo 1 > /sys/bus/pci/drivers/ipw*/*/rf_kill
</code>

If you need Wi-Fi, you can also reduce power consumption (at the price of
performances) by activating the power saving modes:

<code>
iwpriv eth1 set_power 5
</code>

Reducing beacon intervals on your Access Point to 1 per second will also
reduce network card interrupts, therefore power savings. This shouldn't have
negatives side effects.

See also, to activate power saving on the wireless network card:
* For [[Intel PRO/Wireless 2200BG Mini-PCI Adapter]] and [[Intel PRO/Wireless 2915ABG Mini-PCI Adapter]], see instructions for the [[ipw2200]] driver.
* For [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter]], see the [http://ipw3945.sourceforge.net/README.ipw3945 ipw3945 driver README]

==Ethernet Controler==
If you don't use Wake-on-LAN, you should disable it for your network card,
because it sucks a lot of power:

<code>
ethtool -s eth0 wol d
</code>

If you can, try to reduce useless network activity on your ethernet
segment, coming to your NIC (ie. uneeded broadcasts), those cause
interrupts and CPU wakeups.

==Bluetooth==
When you don't need bluetooth, disable it. Because of its radio,
bluetooth is not power friendly.

<code>
hciconfig hci0 down ; rmmod hci_usb
echo disable > /proc/acpi/ibm/bluetooth
</code>

==Modem==
When was the last time you used your analog modem? If you can't remember, you probably just don't need it. If it is on a separate module in your laptop, simply remove it. Store it in a ESD safe place (like the bag in which your last addon card or hard drive was packed), in case you should need it again. This won't save you a lot of power and weight, but why carry something around you never use.

==System Fans==
Fans consumes power when running, so you may look at the [[ACPI fan control script]].

==Misbehaving Userland==
You should avoid using Beagle, Compiz, Beryl, XMMS, gnome-power-manager
and Evolution while on battery.
Look at the PowerTOP's [http://www.linuxpowertop.org/known.php known problems]
list.

Deactivate desktop animations (blinking cursor on the terms, animated wallpapers, ...): they cause regular X (therefore kernel and CPU) wakeups.

In short, while on battery, you should stop all applications that don't really stay idle when you're not using them. This means applications that:
* Wakes up the CPU too often (by polling something, because of too short select() timeouts, ...)
* Access the disks at regular intervals
* Access an hardware bus (USB, ATA, ...) at regular intervals
To find those offenders run:
* <code>strace -p $(pidof yourapp)</code> # for all your running applications
* <code>powertop</code>
* <code>sysctl vm.block_dump=1</code> # and look at dmesg
* <code>ps aux | awk '{print$10,$11}' | sort -n</code> # will list all running softs sorted by used cpu time
Please, don't forget to fill a bug when you find such a misbehaving software.
{{NOTE|Not all software is evil, buggy or badly written. Some produce regular activity because they have to and the purpose of the software is doing it like this. Just think twice before fill bugs like this.}}

==See Also==
* [[How to measure power consumption]]
* [[Script for monitoring power consumption]]
* Battery [[maintenance]]

==External resources==
* [http://www.free-it.de/archiv/talks_2005/paper-11017/paper-11017.html ''Current trends in Linux Kernel Power Management''], Dominik Brodowski, 2005
* [http://www.linuxpowertop.org PowerTOP] website
* [http://www.gentoo.org/doc/en/power-management-guide.xml Power Management Guide] from the Gentoo Linux documentation
* [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-November/030478.html When/where/what for low power consumption?] (thread on Linux-Thinkpad)
* ''8 hours of battery life on your lap(top)'' ([http://atrey.karlin.mff.cuni.cz/~pavel/swsusp/8hours.odp ODP]/[http://atrey.karlin.mff.cuni.cz/~pavel/swsusp/8hours.pdf PDF]), a presentation by Pavel Machek

[[Category:600X]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:A30]] [[Category:A30p]] [[Category:A31]] [[Category:A31p]] [[Category:i1200]] [[Category:i1300]] [[Category:i1620]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50e]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:R60]] [[Category:R60e]] [[Category:T20]] [[Category:T21]] [[Category:T22]] [[Category:T23]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:T60]] [[Category:T60p]] [[Category:T61]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]] [[Category:X41 Tablet]] [[Category:X60]] [[Category:X60s]] [[Category:Z60m]] [[Category:Z60t]] [[Category:Z61t]] [[Category:Z61e]] [[Category:TransNote]]

How to reduce power consumption

2007-10-09T17:46:46Z

BDKMPSS: /* Tools */ added linkt to (think)wiki page, noted that is is mostly all about CPU wakeups only

Reducing system power consumption will extend battery life, reduce system
temperature and (on some models) reduce system fan noise.
Power consumption can be greatly improved from a stock distribution configuration
to a fine tuned system. The general rules are :
* Unload drivers for unused devices (ie. USB 1.1, Yenta/PCMCIA, Wireless, IRDA, Bluetooth, ...)
* Reduce polling on devices (drives, USB subsystem, nvram, ...)
* Reduce hard drive activity
* Reduce LCD brightness to the minimum you can stand
* Reduce CPU wakeups, so it can stay longer in deep power saving c-states

==Tools==
Arjan van de Ven's [[PowerTOP]] utility
is a gold mine to improve energy efficiency, but is almost only CPU-oriented. This tool helps to easily detect
the top power offenders, both userland and kernel modules, which prevent the use of CPU power saving mechanisms and sometime suggest
fixes accordingly.
PowerTOP users collected some [http://www.linuxpowertop.org/known.php tips & tricks]
and an informative [http://www.linuxpowertop.org/faq.php faq].

Alternatively (or complementary) to PowerTOP, running <code>strace -p $(pidof yourapp)</code>
for all your favorite or background running applications while they are expected to be
idle, will show the misbehaviors.

Beside CPU wakeups, disks spins are also power angry. To detect what make your disk spinning,

<code>
sysctl vm.block_dump=1
</code>

will list all applications causing disks wakeups on the kernel's dmesg.
Other useful tools for this purpose are blktrace, iostat and lm-profiler
(from laptop-mode-tools suite).

==BIOS settings==
Some Thinkpad BIOS (like 2.08 BIOS on {{X40}}) offer two very lame options,
with a very misleading online help (saying "Usually not needed"). That's

<code>
CPU power management: (default disabled)
PCI bus power management: (default disabled)
</code>

You should indeed enable them, else the deepest C3 and C4 ACPI C-states
are disabled.

==CPU==
Look at:
* [[How to make use of Dynamic Frequency Scaling]]
* [[Pentium M undervolting and underclocking]]

A good thing to keep in mind is that every CPU wakeup, even if it's for
a trivial light job, reduce the time the CPU stays on a deep power
saving C-state (like C3 or C4). Therefore you should ensure your applications
stay really idle when they meant to be idle (track shorts select timeouts
in loop, etc. with powertop).

Also note that manually locking the CPU in the lowest P-state (frequency)
available is '''not''' an efficient way to improve battery lifetime. This will
cause the CPU to stay longer in C0 (power angry C-state) doing hard work when
there is something to do, while it could have done this work faster by augmenting
the CPU freq, and returned back faster to a deeper, economic, C-state and to a
lower frequency (P-state).
The best is to let the kernel select the appropriates CPU frequencies by itself
with the help of in kernel CPU governors.
Have a look at [http://www.bughost.org/pipermail/power/2007-May/000166.html this explanation]
from Intel's kernel developer Arjan van de Ven.

==Kernel settings and patches==

===General settings===
The 2.6.21 kernel brought some very effective changes (like dynticks). If
it's not already on your distribution and you value power efficiency, you
may think about compiling it (or a more recent one) yourself.

Here are a few options (beside the ACPI and APM related one) that matter to
reduce power consumption or to help diagnosing consumers:

<code>
# From PowerTOP's FAQ:
CONFIG_NO_HZ
CONFIG_HIGH_RES_TIMERS
CONFIG_HPET
CONFIG_CPU_FREQ_GOV_ONDEMAND
CONFIG_USB_SUSPEND
CONFIG_SND_AC97_POWER_SAVE
CONFIG_TIMER_STATS
CONFIG_ACPI_BATTERY
CONFIG_CPU_FREQ_STAT
# Not from the PowerTOP FAQ:
CONFIG_BLK_DEV_IO_TRACE
CONFIG_X86_ACPI_CPUFREQ
CONFIG_X86_SPEEDSTEP_CENTRINO
CONFIG_X86_SPEEDSTEP_ICH
CONFIG_X86_SPEEDSTEP_SMI
CONFIG_X86_ACPI_CPUFREQ
</code>

Those options are already in Fedora Core 7 and Ubuntu Gutsy (not Feisty) default i686 kernels.
PowerTOP FAQ also suggest to '''disable'''
CONFIG_IRQBALANCE et CONFIG_ACPI_DEBUG.

Also, you need to properly set APM and ACPI. Look at:
* [[Power Management]]
* [[How to make use of Power Management features]]

===Useful Patchs===

Thomas Gleixner High Resolution Timers (hrt) patchset brings many improvements,
like the cpuidle work and Udo A. Steinberg and Venki Pallipadi "force
enable HPET" patches (non HPET timers causes about 20-40 CPU wakeups/second, but
HPET is often hidden by the BIOS due to Windows XP deficiencies).
See http://www.tglx.de/projects/hrtimers/

Kristen Carlson Accardi from Intel has a patchset to turn on "Aggressive
Link Power Management" (ALPM) for the AHCI driver (for SATA bus). See:
http://www.kernel.org/pub/linux/kernel/people/kristen/patches/SATA/alpm/

The [[HDAPS]] disk protection systems can reduce battery life.
Matthew Garrett provides [http://www.linuxpowertop.org/patches/hdaps.patch a patch]
that prevents hdaps kernel module to generate interrupts when
this feature isn't used.

===Useful sysctls===
The meaning of those settings is explained case by case on the relevant
sections of this document. But for convenience sake, we group them here too.

Note that the "ondemand" scaling governor is recommended by Intel developers
for energy efficiency: it's expected to be more efficient than the "powersave"
governor, or than userspace daemons (like cpufreq-utils, cpufreqd, powernowd...).
Look [http://www.bughost.org/pipermail/power/2007-May/000071.html here],
[http://www.bughost.org/pipermail/power/2007-May/000073.html here], or
[http://www.bughost.org/pipermail/power/2007-May/000166.html here] for a
kernel developer explanation about "ondemand" being better on modern Intel CPUs.

The "link_power_management_policy" tunable won't be available unless you
run Kirsten patchset, have an Intel AHCI compatible chipset, and use SATA drives.

<code>
echo 5 > /proc/sys/vm/laptop_mode
echo 0 > /proc/sys/kernel/nmi_watchdog
echo Y > /sys/module/snd_ac97_codec/parameters/power_save
echo 1 > /sys/devices/system/cpu/sched_mc_power_savings
echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo min_power > /sys/class/scsi_host/host0/link_power_management_policy
echo min_power > /sys/class/scsi_host/host1/link_power_management_policy
echo 1500 > /proc/sys/vm/dirty_writeback_centisecs
</code>

If you're running a kernel older than 2.6.22 do this. Not needed for kernels 2.6.22 onward:

<code>
cd /sys/devices/system/cpu/cpu0/cpufreq
cat ondemand/sampling_rate_max > ondemand/sampling_rate
</code>

==ATA drives==
Hard drives and CDRom drives spinning is very costly. To improve battery
lifetime, you should reduce disks access (or devices polling) the more you
can.

===Hard Drives===
The files access time update, while mandated by POSIX, is causing lots of
disks access; even accessing files on disk cache may wake the ATA or USB
bus. If you don't use this feature, disable it via:

<code>
mount -o remount,noatime / # and so on for all mounted fs
</code>

The laptop_mode reduce disk usage by regrouping writes. You should enable
it, at least while on battery. See [[Laptop-mode]] for more details:

<code>
echo 5 > /proc/sys/vm/laptop_mode
</code>

The default kernel dirty page writeback frequency is very conservative. On
a laptop running on battery, one might find more appropriate to reduce it:

<code>
echo 1500 > /proc/sys/vm/dirty_writeback_centisecs
</code>

Some power saving hard drives features can be activated with hdparm.
For more details look at [[How to make use of Power Management features]] :

<code>
hdparm -B 1 -S 12 /dev/sda # and/or any other disk device
</code>

===Optical drive===
The optical drive is reported to consume power even when not accessed. See

* [[How to hotswap UltraBay devices|Eject the UltraBay optical drive]], or just turn off its power supply (i.e., run the appropriate eject script but leave the drive inserted).
* [[How to set optical drive speed|Reduce the spinning speed of the optical drive]].

The hald daemon polling tends to maintain the ATA buses out of power saving
modes, and to wakeup CDROM drive. If you have a recent hald version, you
can stop this polling when on battery:

<code>
hal-disable-polling /dev/scd0 # or whatever your CD drive is
</code>

If your hald is not recent enough, consider stopping it on battery.

==LCD Backlight/Brightness==
The LCD backlight is one of the very major power drain.
Reducing brightness to the lowest readable
level will save a lot of battery lifetime. Also, don't forget to configure
your screen saver to shutdown the screen backlight (rather than displaying some
eye candy), when no activity for a few minutes.

You can also let the system [[automatically reduce brightness]] after a
period of inactivity.

If you're choosing your Thinkpad laptop model, keep in mind that the screen
size affect the battery time greatly: more power needed for larger screens.

==Graphic controllers==
All xorg Thinkpad graphics chipsets drivers (ati, radeon, fglrx, i810) have
the same bug causing very frequent CPU wakeups when DRI is activated, even
when you don't use any 3D application.
This problem is partly fixed on xorg git tree but not released as of xorg
7.2. If you value more battery than 3D, you should disable DRI: put this on
the /etc/X11/xorg.conf "Device" of you graphic controller:

<code>
Option "NoDRI"
</code>

Also be sure that DPMS is working: <code>grep DPMS /var/log/Xorg.0.log</code>
should output "DPMS enabled". If not, put <code>Option "DPMS"</code> in your config.

On recent xrandr/xorg versions, you can disable the TV output when you're
not using it (it's known to consume power) :

<code>
xrandr --output TV -off
</code>

When you don't have an external monitor plugged, disable CRT and DVI output
(for some, this can make a difference in power usage) :
<code>
echo crt_disable > /proc/acpi/ibm/video
echo dvi_disable > /proc/acpi/ibm/video
</code>

Some drivers have specials power saving mode, and/or allows underclocking the GPU. See also:
* [[How to make use of Graphics Chips Power Management features]], or with [[Rovclock]] on ATI.
* [[Problem with high power drain in ACPI sleep]]

==USB Subsystem==
The kernel support an efficient USB 2.0 power saving feature if you enabled
CONFIG_USB_SUSPEND. This may not trigger in when you have an USB device
plugged (and beside, USB devices tends to suck power on their own), so avoid
using such devices when on battery.

USB 1.1 is worst. It needs polling the bus frequently, hence can't really go
in a low power mode when you enabled it, even if you don't have any device
plugged. You'd better remove it when you don't use a 1.1 device:

<code>
rmmod uhci_hcd
</code>

If you don't intend to use any USB 1.1 device (unfortunately, the built-in bluetooth and fingerprint-reader are USB 1.1 devices), the USB 1.1 support can also be totaly avoided. On Debian and derivatives, just do:

<code>
echo "blacklist uhci_hcd" >> /etc/modprobe.d/blacklist
</code>

==Sound==
ALSA has a power saving feature that should be enabled on your kernel
(CONFIG_SND_AC97_POWER_SAVE). Note that this low power mode won't trigger in
unless you muted all sound inputs (micro, line in etc.). This feature has
to be activated with:

<code>
amixer set Line mute nocap
amixer set Mic mute nocap
echo Y > /sys/module/snd_ac97_codec/parameters/power_save
</code>

More radical: you can unload all sound related modules when you are on
battery, or mute the sound system (echo mute > /proc/acpi/ibm/volume).

Seel also [[How to enable AC97 power saving]].

==Wireless Interface==
Wireless network consume a lot of power.
To save power on ipw adapters, you can kill the Wi-Fi radio when it's not in use:

<code>
echo 1 > /sys/bus/pci/drivers/ipw*/*/rf_kill
</code>

If you need Wi-Fi, you can also reduce power consumption (at the price of
performances) by activating the power saving modes:

<code>
iwpriv eth1 set_power 5
</code>

Reducing beacon intervals on your Access Point to 1 per second will also
reduce network card interrupts, therefore power savings. This shouldn't have
negatives side effects.

See also, to activate power saving on the wireless network card:
* For [[Intel PRO/Wireless 2200BG Mini-PCI Adapter]] and [[Intel PRO/Wireless 2915ABG Mini-PCI Adapter]], see instructions for the [[ipw2200]] driver.
* For [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter]], see the [http://ipw3945.sourceforge.net/README.ipw3945 ipw3945 driver README]

==Ethernet Controler==
If you don't use Wake-on-LAN, you should disable it for your network card,
because it sucks a lot of power:

<code>
ethtool -s eth0 wol d
</code>

If you can, try to reduce useless network activity on your ethernet
segment, coming to your NIC (ie. uneeded broadcasts), those cause
interrupts and CPU wakeups.

==Bluetooth==
When you don't need bluetooth, disable it. Because of its radio,
bluetooth is not power friendly.

<code>
hciconfig hci0 down ; rmmod hci_usb
echo disable > /proc/acpi/ibm/bluetooth
</code>

==Modem==
When was the last time you used your analog modem? If you can't remember, you probably just don't need it. If it is on a separate module in your laptop, simply remove it. Store it in a ESD safe place (like the bag in which your last addon card or hard drive was packed), in case you should need it again. This won't save you a lot of power and weight, but why carry something around you never use.

==System Fans==
Fans consumes power when running, so you may look at the [[ACPI fan control script]].

==Misbehaving Userland==
You should avoid using Beagle, Compiz, Beryl, XMMS, gnome-power-manager
and Evolution while on battery.
Look at the PowerTOP's [http://www.linuxpowertop.org/known.php known problems]
list.

Deactivate desktop animations (blinking cursor on the terms, animated wallpapers, ...): they cause regular X (therefore kernel and CPU) wakeups.

In short, while on battery, you should stop all applications that don't really stay idle when you're not using them. This means applications that:
* Wakes up the CPU too often (by polling something, because of too short select() timeouts, ...)
* Access the disks at regular intervals
* Access an hardware bus (USB, ATA, ...) at regular intervals
To find those offenders run:
* <code>strace -p $(pidof yourapp)</code> # for all your running applications
* <code>powertop</code>
* <code>sysctl vm.block_dump=1</code> # and look at dmesg
* <code>ps aux | awk '{print$10,$11}' | sort -n</code> # will list all running softs sorted by used cpu time
Please, don't forget to fill a bug when you find such a misbehaving software.
{{NOTE|Not all software is evil, buggy or badly written. Some produce regular activity because they have to and the purpose of the software is doing it like this. Just think twice before fill bugs like this.}}

==See Also==
* [[How to measure power consumption]]
* [[Script for monitoring power consumption]]
* Battery [[maintenance]]

==External resources==
* [http://www.free-it.de/archiv/talks_2005/paper-11017/paper-11017.html ''Current trends in Linux Kernel Power Management''], Dominik Brodowski, 2005
* [http://www.linuxpowertop.org PowerTOP] website
* [http://www.gentoo.org/doc/en/power-management-guide.xml Power Management Guide] from the Gentoo Linux documentation
* [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-November/030478.html When/where/what for low power consumption?] (thread on Linux-Thinkpad)
* ''8 hours of battery life on your lap(top)'' ([http://atrey.karlin.mff.cuni.cz/~pavel/swsusp/8hours.odp ODP]/[http://atrey.karlin.mff.cuni.cz/~pavel/swsusp/8hours.pdf PDF]), a presentation by Pavel Machek

[[Category:600X]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:A30]] [[Category:A30p]] [[Category:A31]] [[Category:A31p]] [[Category:i1200]] [[Category:i1300]] [[Category:i1620]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50e]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:R60]] [[Category:R60e]] [[Category:T20]] [[Category:T21]] [[Category:T22]] [[Category:T23]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:T60]] [[Category:T60p]] [[Category:T61]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]] [[Category:X41 Tablet]] [[Category:X60]] [[Category:X60s]] [[Category:Z60m]] [[Category:Z60t]] [[Category:Z61t]] [[Category:Z61e]] [[Category:TransNote]]

Issues with the Wiki

2007-10-03T18:42:12Z

BDKMPSS: /* Troubles encountered */ E-Mail confirmation works now

This page is a provisorium. It's a list of things that are going wrong after the update to help [[User:akw|Akw]] track and fix them.

== JavaScript and CSS ==

'''Enabling user Javascript and CSS for MediaWiki'''

Could ThinkWiki's MediaWiki installation get these options enabled (typically set in LocalSettings.php):

* [http://www.mediawiki.org/wiki/Manual:%24wgAllowUserCss wgAllowUserCss]
* [http://www.mediawiki.org/wiki/Manual:%24wgAllowUserJs wgAllowUserJs]

These options allow users to have their own custom Javascript and CSS. I (and others) like to have our own custom themes and Javascript when working with MediaWiki-powered websites.

--[[User:SamatJain|SamatJain]] 22:04, 28 July 2007 (UTC)

This is a great security risk. What is it good for?

--[[User:Thinker|Thinker]] 00:14, 29 July 2007 (UTC)

It allowers users to set their own customizations via Javascript and CSS. It's a minor security risk which is why MediaWiki ships with it off, but Wikipedia and other popular websites using MediaWiki ship with it on.

--[[User:SamatJain|SamatJain]] 20:49, 29 July 2007 (UTC)

There is nothing minor about it. The web security model is site-wise when dealing with MediaWiki, there is no easy (read: manageable) way for an user, even one that uses NoScript+Firefox or something else equally powerful, to really filter out trusted from untrusted content when you start allowing people to write JavaScript into a Wiki.

CSS is less of a problem, but it could still hork the site if one is not careful, and MediaWiki already allows us to change the pages well enough. If you need to change thinkwiki CSS for your own viewing pleasure, any browser worth its bytes lets you layer your own CSS on top of a site's. I would not be strongly against enabling CSS, but I don't see any reason to do it, either.

JavaScript submissions, OTOH, is something that must remain disabled. IMO, if you really can't survive without tacking different JavaScript code than what thinkwiki already has, you can use greasemonkey or some other such system to do it in your own browser.

If thinkwiki starts allowing users to set javascript on their pages, I would have to block javascript completely on my side, for example. At that time, it is likely I will just go away. Other contributors might feel the same. It is not that I have anything against JavaScript. It is the fact that I cannot *trust* user-submitted JavaScript.

--[[User:Hmh|hmh]] 12:26, 30 July 2007 (UTC)

These options only enable Javascript and CSS for user pages, i.e. for User:User/Monobook.css and User/Monobook.js, specifically ''not'' for other pages. Disabling these options was done by default as a precaution against XSS vulnerabilies [http://www.gossamer-threads.com/lists/wiki/mediawiki-announce/28572 long since been fixed]. Unfortunately, while I agree with you about disabling user Javascript as a precaution, I do not think the wgAllowUserCss option has any effect unless the wgAllowUserJs option is enabled as well.

--[[User:SamatJain|SamatJain]] 18:52, 30 July 2007 (UTC)

I don't get the point ether.
Why you want to use css/javascript on user pages? You always say why you think its no problem, but not what you want to do. If you need some funky looking stuff or buttons there you should use something like myspace. This Wikis (and almost all other) purpose is collecting the main - Thinkpad - content, not something cool/funky/special on userpages

As Hmh, I would block js immediately and may leave the site, even if its only on userpages, because I don't want to mind clicking "the false links"

--[[User:BDKMPSS|BDKMPSS]], 30 July 2007

[http://en.wikipedia.org/wiki/MediaWiki#Customisation Wikipedia's section on MediaWiki customization] describes some of the extensions and addons available. For example, [http://en.wikipedia.org/wiki/User:Cacycle/wikEd wikiEd] is a WYSIWYG editor such that instead of having to remember MediaWiki's markup, they use an editor that's only enabled for use them. This kind of extending is difficult to do with Stylish or Greasemonkey.

I'll repeat, since I've not been apparently misunderstood:
* Users ''won't'' be able to add Javascript or CSS to arbitrary pages, only those under their user profile (these are called "user pages")
* Only those users logged in will see these their own changes, no other users will.
Given these things, I don't understand why people need to threaten they're going to stop contributing to ThinkWiki? There isn't a way you're going to turn ThinkWiki into MySpace. If you don't use specifically use any CSS or Javascript through these features, it will not effect you at all.

What I personally want to do, I want to use a MediaWiki modification I wrote, [http://meta.wikimedia.org/wiki/Gallery_of_user_styles#Nullbook Nullbook]. I feel as if I am much more efficient with this theme.

--[[User:SamatJain|SamatJain]] 21:58, 30 July 2007 (UTC)

I don't understand what exactly $wgAllowUserJs is supposed to do, and its [http://www.mediawiki.org/wiki/Manual:%24wgAllowUserCss documentation] is worthless. The crux of the matter is this: if those features are enabled, is there any way ''you'' can cause ''me'' to execute JavaScript (or apply CSS) that ''you'' wrote, in ''any'' page on ThinkWiki? If not, why?

--[[User:Thinker|Thinker]] 22:17, 30 July 2007 (UTC)

[http://meta.wikimedia.org/wiki/User_styles User styles on the MediaWiki site] describes a bit more how these options work and what is provided to any modification that depends upon them. Unless there exist security-related bugs (which is the reason these features are tagged possible security risks, and why they are proactively disabled by default), by design, no, there is no way that I can cause you to execute Javascript or apply CSS that I had put into one of my own "user pages" (i.e. those under [[User:SamatJain]]).

--[[User:SamatJain|SamatJain]] 22:53, 30 July 2007 (UTC)

'''If and only if''' such javascript and css changes are limited so that the user who made them is the only one who gets them, then I have nothing against it.

That said, I'd prefer if the relevant mediawiki code was audited a bit before it is enabled.

PS: Whomever is doing it, please stop screwing around with the formatting: there must be one empty line before and after signatures, it makes the dialog a '''lot''' more readable.

--[[User:Hmh|hmh]] 02:53, 1 August 2007 (UTC)

== Troubles encountered ==

'''/usr/bin/convert'''

I think the computer this wiki is running on is missing the imagemagick software tools especially convert to create thumbnails of images --[[User:Markusw|Markusw]] 10:21, 26 August 2007 (UTC)

----

'''Problem with cmdroot'''

Following String is not handled correct by template cmdroot:
"fakeroot make-kpkg --initrd --revision=thinkpad.1.0 kernel_image"

see here:
{{cmdroot|fakeroot make-kpkg --initrd --revision=thinkpad.1.0 kernel_image}}

----

'''Can not open page to edit without introducing modifications'''

If I open the [[X31]] model page and without touching anything I hit preview, the div token is decomposed and appears in the preview page, and of course, the photo is not in the right place.

:[[User:Ungoliant|Ungoliant]] 19:24, 20 February 2007 (CET)

----

'''Can not upload SVG'''
I get the upload warning:
".svg" is not a recommended image file format.
:[[User:Matt|Matt]] 14:02, 3 December 2006 (CET)

----

Is there a way to contact a registered user, for example to confirm information. I have found that AdamZ claims that the X20 is bootable via USB. My information indicates the contrary. Isn't there a way to contact a registered user through MediaWiki? --[[User:Rolf|Rolf]] 00:30, 9 September 2006 (CEST)

php error encountered when attempting to update Bios Upgrade page:
<blockquote>
Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 133781 bytes) in /home/akw/htdocs/thinkwiki.org/mediawiki-1.5.6/includes/MagicWord.php on line 250
</blockquote>
--[[User:roadends|roadends]] 02:30, 20 March 2006 (EDT)
----

* [[ThinkWiki:SpamBlackList]] does not appear to work anymore
--[[User:Tonko|Tonko]] 03:40, 11 March 2006 (CET)
----
You can't (easliy do a multiline {{cmdresult|cmdresult}}, can you? See:

{{cmdresult|foo
bar
baz}}

or

{{cmdresult|foo
bar (after whitespace)
baz (after whitespace)}}

This works (but is not so nice)

{{cmdresult|foo

bar (after empty line)

baz (after empty line)}}

Any suggestions?

[[User:Pebolle|Paul Bolle]] 10:27, 24 January 2006 (CET)
----
I think the best way is to use single cmdresult calls for each line and prefix them with a colon. Like so:
<pre><nowiki>
:{{cmdresult|foo}}
:{{cmdresult|bar}}
:{{cmdresult|baz}}
</nowiki></pre>, which results in
:{{cmdresult|foo}}
:{{cmdresult|bar}}
:{{cmdresult|baz}}

Alternatively, you can use <br /> at the ende of each line within one call, like this:
<tt><nowiki>{{cmdresult|foo<br />
bar<br />
baz}}</nowiki></tt>
, which will result in

{{cmdresult|foo<br />
bar<br />
baz}}

[[User:Wyrfel|Wyrfel]] 12:13, 24 January 2006 (CET)
----
I have just got a MySQL problem when I edited a page, a query was not to its liking. It is quite easy to reproduce, just edit any page ;-)

History did get updated, and the page was also updated, so I have no idea what broke when that query failed.

A database query syntax error has occurred. This may indicate a bug in the software. The last attempted database query was:
(SQL query hidden)
from within function "SearchMySQL4::update". MySQL returned error "1062: Duplicate entry ' ' for key 3 (localhost)".

[[User:Hmh|hmh]] 2006-02-17, 20:12 UTC
----
More database problems, this time the search function:

A database query syntax error has occurred. This may indicate a bug in the software. The last attempted database query was:
(SQL query hidden)
from within function "". MySQL returned error "145: Table './thinkwiki/searchindex' is marked as crashed and should be repaired (localhost)".

[[User:Hmh|hmh]] 2006-02-21, 15:07 UTC
----
The server time would appear to be off a lot, is it possible to setup ntpd, or to run ntpdate every hour or so using cron?
--[[User:Tonko|Tonko]] 05:11, 22 February 2006 (CET)
----
Search still seems broken, searching for DVI brings up nothing.
--[[User:Jumpfroggy|Jumpfroggy]] 00:03, 17 March 2006 (CET)
----
Error creating thumbnail: /home/thinkwiki/htdocs/mediawiki-1.10.0/bin/ulimit4.sh: line 4: /usr/bin/convert: No such file or directory

----

'''"Your signature with timestamp"-Button'''

This Button simply doesn't work, it adds <nowiki>--~~~~</nowiki><br>
I think its a bunch on javascript so I may add:<br>
I use Firefox (branded as Icewasel) on Debian Testing<br>
Preferences:<br>
Raw signatures (without automatic link) OFF<br>
Show edit toolbar (JavaScript) ON<br>
(Oh... Yes its javascript)

EDIT:
Even in my Windows XP SP2 Virtual Machine it don't work in Internet Explorer 7.0

--[[User:BDKMPSS|BDKMPSS]] 29 July 2007

----

'''Confirmation E-mail'''

It just don't work. It neither is in my spam dir nor works with any other address.
Tried multiple times, waited hours, days, weeks... gave up and wrote this here...

--[[User:BDKMPSS|BDKMPSS]] 29 July 2007

The E-Mail confirmation feature works now

--[[User:BDKMPSS|BDKMPSS]] 10 October 2007

----

== Troubles confirmed ==
* [[Special:Benchmarks]] doesn't find it's data

(update 2007-03-24: this page is not listed in the special pages category anymore, so the bug is now worked around).

== Fixed problems ==
* http://thinkwiki.org/ reverted again to the default MediaWiki theme. '''Cannot reproduce this one (15.01.06, akw)'''
* File upload is disabled - '''Argh. Fixed (15.01.06, akw)'''
* URL contains index.php(/) before the actual page name - '''This has been fixed (28.05.05, akw)'''
* The categories page doesn't link to [[:Category:ThinkWiki]] - '''Fixed (29.05.05, akw)'''
* http://thinkwiki.org/ is broken (no www prefix), this was working before - '''Fixed (29.05.05, akw)'''
* On logging in a requester pops up asking to confirm a password change - '''seems like it's implicitly been fixed (29.05.2005, wyrfel)'''
* In Navigation bar, "&lt;download&gt;" leads to [http://www.thinkwiki.org/wiki/--error:_link_target_missing--] - '''fixed (30.06.2005)'''
* direct link to [[:Category:Models]] missing in Navigation '''Fixed (10.07.05, akw)'''
* It seems the Wiki has trouble updating the edit history, i'm getting mysql query errors on saving pages. The pages get saved, however. '''Fixed (12.05.2005)'''

How to make use of Power Management features

2007-09-28T18:04:36Z

BDKMPSS: /* See also */ added link to Idle_consumptions

==General Information about Power Management features==
This page should give you all the information you need to make use of your ThinkPads [[Power Management]] features under [[:Category:Distributions|Linux]] and hence effectively enhance your battery life.

Note that different distributions and kernels have different results. ThinkPad-365 and 365X used to perform
blank, sleep and hibernation well using HW with W95,OS/2,and Linux installed (1998). Later ThinkPads such as 240X,600E,T20 with recent Debian 2.4 kernels and ACPI=off will sleep, (also MDK-2.6 kernels).
However, blank and hibernation to disk do not work. Better results are expected with 2.6.11+.

===APM vs. ACPI===
All IBM ThinkPads support APM, and a lot support ACPI as well. Newer Lenovo ThinkPads support only ACPI. Quality of ACPI implementation varies from model to model. Both technologies cannot be used simultaneously; you'll have to make a choice. Which to use depends on the model as well as on the state of ACPI support in the kernel.

On older models you are surely better off with APM, if they feature ACPI at all.

It seems that at least in recent models from the A, G, R, T and X series ACPI generally works fine and is a lot more flexible than APM, but with a lot of them also a [[Problem with high power drain in ACPI sleep]] has been experienced.

Please check our [[APM vs. ACPI | APM vs. ACPI success table]] to find out about APM and ACPI support in specific models.

On the other hand simply switching from APM to ACPI extended my X31 battery runtime from about 3.5h to 4h. This had
nothing to do with Dynamic Frequency Scaling which was active in both configurations.

{{Todo|more precise and extended info should be provided here}}

==How to enable certain features==
The following links will take you to separate pages dealing with the various topics.
*[[How to make APM work]] <tt>(Screen Blanking, Suspend to RAM, Suspend to Disk)</tt>
*[[How to make ACPI work]] <tt>(Screen Blanking, Suspend to RAM, Suspend to Disk)</tt>
*[[How to make use of Dynamic Frequency Scaling]] <tt>(Speedstep, Throttling, etc.)</tt>
*[[How to make use of Harddisk Power Management features]] <tt>(Laptop-mode, Spindown, etc.)</tt>
*[[How to make use of Graphics Chips Power Management features]] <tt>(save even more battery power)</tt>
*[[How to use UltraBay batteries]] <tt>(advanced control for a secondary battery)</tt>

==See also==
*[[How to reduce power consumption]]
*[[Idle_consumptions]]

Idle consumptions

2007-09-28T18:03:46Z

BDKMPSS: added my X31

This page reports the minimal consumptions of Thinkpads when idle. This means, in principle: minimum brightness, CPU and GPU at lowest speed, no wifi, hard drive spun down, no pcmcia cards inserted (see details of each entry).

This kind of information has several uses: comparing one's consumption with that of other people's setups, knowing which model to use as a gateway/file server, etc.

{| border="1" cellspacing="0" cellpadding="2"

! Model !! OS !! Remarks !! consumption
|----
|{{600E}} PII/366 || Debian Lenny/2.6.21 gnome || back light off, laptop-mode-tools enabled, fan on, idling, measured with powertop || 6W
|----
|{{600E}} PII/366 || Debian Lenny/2.6.21 gnome || Min brightness, laptop-mode-tools enabled, fan on, idling, measured with powertop || 7.5W
|----
|{{600E}} PII/366 || Debian Lenny/2.6.21 gnome || Max brightness, laptop-mode-tools enabled, fan on, idling, measured with powertop || 9.2W
|----
|{{600E}} PII/366 || Debian Lenny/2.6.21 gnome || Max brightness, laptop-mode-tools enabled, fan on, 100% cpu utilisation, measured with powertop || ~22W
|----
|{{600E}} PIII/450 || Archlinux 0.8/xfce || || 9W
|----
|{{R50e}}|| Gentoo (linux-2.6.22-rc4 force_HPET, fluxbox) ||With Networking, USB, firefox, thunderbird || 11.1W
|----
|{{R50e}}|| Gentoo (linux-2.6.22-rc4 force_HPET, fluxbox) ||Fluxbox + shell (+fan) || 10.5W
|----
|{{R50e}}|| Gentoo (linux-2.6.22-rc4 force_HPET, fluxbox) ||Blank Screen after 20min idle (+fan) || 7.1W
|----
|{{R52}}|| Gentoo (linux-2.6.22-rc6 + phc + hrt) ||Min brightness, tp-fancontrol, ipw2200 with power_save 5, undervolted, ondemand, laptop_mode, rovclock -c 100 -m 100<br />virtual console (idle kde desktop adds about 0.2W) || 12.1W
|----
|{{R61}}||Ubuntu 7.04||Wireless on||16.4W
|----
|{{T23}}||Ubuntu 7.04|| || 10.7W
|----
|{{T40}}||Gentoo (2.6.23-rc6-hrt2)|| [http://www.linuxpowertop.org/patches/kernel-2.6.22-rc1.patch Bg-timer patch], HPET-patches, radeon, <tt>rovclock -c 105 -m 122</tt>, no DRI, sound power_save = Y, min. brightness, no networking, with USB, Laptop-Mode, X & 1x URxvt || 7,4W
|----
|{{T41p}}||Ubuntu 7.04|| Undervolted, fglrx, no dri; fan->+0.5W, powerstate=2->+0.7W, HD->+1.5W || 8.3W
|----
|{{T42}} (2373)||Debian 4.0 Etch|| Kernel 2.6.21_rc5 + hrtimer, rovclock -c 100 -m 120 (Radeon M10), no DRI, min bright. (+3W max), no wifi (+1W if idle) || 9.4W
|----
|{{T43}} (1871)||Debian (Linux 2.6.21, fluxbox)|| DRI, alsa (power_save=1), with usb, no networking || 10.1W (12.0W with HD)
|----
|{{T43}} (2669)||Gentoo (2.6.20-gentoo-r5)|| Undervolted, fglrx (powerstate=1), DRI, no alsa, no usb modules, no networking || 12.7W
|----
|{{T43}} (2686)||Fedora Core 6 (2.6.19.x patched)|| Undervolted, radeon, <tt>rovclock -c 125 -m 130</tt>, no DRI, ALSA <tt>power_save=1</tt>, no usb modules, no networking, min brightness, HDD spun down || 15W
|----
|{{T60}} (2007)||Fedora Core 6|| Wireless kill switch on, 1400x1050 panel @ min brightness, fglrx (powerstate=1), HDD spun up (~1W saving without) || 16W
|----
|{{T60}} (2007)||KUbuntu 7.04|| Wireless on, 1680x1050 panel @ medium brightness, fglrx (powerstate=1) || 16W
|----
|{{T60}} (2623D6U)||Debian testing (linux-2.6.21-1-686)||1400x1050 14" min-bright, iwpriv wlan0 set_power 7, VESA driver|| 12,7W
|----
|{{X21}}||Kubuntu 7.04|| Minimal consumption with kde loaded.||5.5W
|----
|{{X31}}||Debian Etch||2.6.22rc6+hrt1 patch+radeon patch||~ 8 W
|----
|{{X31}} (2672-C2G)||Debian Etch||vanilla 2.6.23rc8 tickless kernel, wireless rf-kill on, min brightness, hdd idle but spinning||~ 9.6 W
|----
|{{X60}}||Ubuntu 7.04||Wireless kill switch on, min brightness||10.2W
|----
|{{X60s}}||Debian Etch||2.6.21 tickless kernel, processes tweaked with powertop, usb/fw unloaded, hd spun down, min brightness, ipw3945 set to powersave mode 7||8.3W
|----
|{{X60s}}||Debian Etch||2.6.21 tickless kernel, processes tweaked with powertop, usb/fw unloaded, hd spun down, min brightness,ipw3945 unloaded||9W
|----
|{{X60s}}||Debian Lenny(testing)|| 2.6.22 tickless kernel, hrt-patch, alpm-patches, almost everything unloaded (wifi,pcmcia,ethernet,usb,firewire,sd,snd) and stopped (no X11,only cron/syslog), no vesa-fb, min brightness, 5 min idle, measured with powertop 1.7 (ACPI)||7.7W
|----
|{{X60s}}||Debian Lenny(testing)|| 2.6.22 tickless kernel, hrt-patch, alpm-patches, almost everything unloaded (wifi,pcmcia,ethernet,usb,firewire,sd,snd), with X11 (latest intel-xorg-driver, DRI enabled) and one x-terminal running, min brightness, 5 min idle, measured with powertop 1.7 (ACPI)||8.3W
|----
|{{X61T}}||Ubuntu Gutsy(tribe6)|| 2.6.23-rc6-hrt1 x86_64, everything unloaded & stopped, lcd backlight off, hd powered down, powertop 1.8||8.5W
|----

Category:X32

2007-09-28T17:56:45Z

BDKMPSS: fix typo X21-> X31

{| 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 X32 ===
This page gives an overview of all ThinkPad X32 related topics.
==== Standard Features ====
* [[Intel Pentium M (Dothan)]] 1.6, 1.7, 1.8 or 2.0GHz CPU
* [[ATI Mobility Radeon 7000]] with 16MB
** 12.1" TFT display with 1024x768 resolution
* 256 or 512MB [[PC2700]] memory standard (2GB max)
* 40, 60 or 80GB HDD
* [[AD1981B]] AC'97 Audio controller
* [[Ethernet Controllers|Intel 10/100/1000 Ethernet controller]]
* [[CDC slot]] with one of the following:
** [[IBM Integrated 56K Modem (MDC-2)]]
** [[IBM Integrated Bluetooth IV with 56K Modem (BMDC-3)]]
* [[MiniPCI slot]] with one of the following:
** none (open)
** [[Intel PRO/Wireless 2200BG Mini-PCI Adapter]]
** [[Intel PRO/Wireless 2915ABG Mini-PCI Adapter]]
** [[IBM 11a/b/g Wireless LAN Mini PCI Adapter II]]
* [[Embedded Security Subsystem|IBM Embedded Security Subsystem 2.0]]
* [[CF Card slot]]
* [[CardBus slot]] (Type 2)
* Firewire (IEEE1394)
* Weight: 3.6lbs (1.7kg)
</div>
|style="vertical-align:top" |
[[image:ThinkPadX31.jpg|ThinkPad X32]]
|}
* [ftp://ftp.software.ibm.com/pc/pccbbs/mobiles_pdf/39t2219.pdf ThinkPad X30, X31, X32 - Hardware Maintenance Manual (March 2005)] (4,369,265 Bytes)
* [ftp://ftp.software.ibm.com/pc/pccbbs/mobiles_pdf/39t6189.pdf ThinkPad X30, X31, X32 - Hardware Maintenance Manual (July 2005)] (4,375,026 Bytes)

[[Category:X Series]]

Thermal Sensors

2007-09-13T23:36:33Z

BDKMPSS: /* ThinkPad {{X31}} */ 0x7D and 0x7F are sensors found Extended-Life-Battery

{| 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 [[ibm-acpi]] module. Up to Linux 2.6.19, ibm-acpi supported only 8 sensors, but since Linux 2.6.20-rc2, up to 16 sensors are supported. When the module is loaded, the sensors (some of which may be inactive) are shown in {{path|/proc/acpi/ibm/thermal}}:

:{{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}}

====Patch for accessing the extra ACPI sensors through <tt>thermal</tt>====
If you don't use a recent-enough [[ibm-acpi]], you can patch it to make the extra 3 sensors show up on {{path|/proc/acpi/ibm/thermal}} just like the 8 basic sensors, apply the {{CodeRef|ibm_acpi-extra-thermal.patch}} kernel patch to [[ibm-acpi]].

Then:

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

If you apply this patch in conjunction with [[ACPI_fan_control_script#Comprehensive_bash_script_with_fine_control_over_fan_speed|tp-fancontrol]], you'll need tp-fancontrol 0.2.9 or newer.

===Accessing the thermal sensors through <tt>ecdump</tt>===
Load [[ibm-acpi]] with the <tt>experimental=1</tt> option, and parse {{path|/proc/acpi/ibm/ecdump}}. The 8 basic sensors are on offsets 0x78-0x7f, and the extended sensors (if supported) are on offsets 0xc0-0xc7.

To read the first three extended sensors:
:{{cmdroot|perl -ne 'm/^EC 0xc0: .(..) .(..) .(..) / or next; print hex($1)." ".hex($2)." ".hex($3)."\n"' < /proc/acpi/ibm/ecdump}}
:{{cmdresult|40 48 43}}

Future models might provide additional extra sensors beyond those three. To see all candidates:
:{{cmdroot|perl -ne 'print join(" ",map(hex,m/\w+/g))."\n" if s/^EC 0xc0://' < /proc/acpi/ibm/ecdump}}
:{{cmdresult|40 48 43 128 128 128 128 128 0 0 0 0 0 0 0 0}}

{{WARN|'''ecdump''' is not a playground, and even just reading it causes side-effects to the ThinkPad. The ibm-acpi maintainer wants to make it clear that he considers it a very dumb idea to use ecdump constantly in a script}}

===HDAPS temperature sensor===
The [[Active Protection System]] accelerometer also reports a temperature, which is identical to one of the ACPI sensors. The corresponding sensor is actually not inside the HDAPS chip, but fairly close.
:{{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://www.elliptique.net/~ken/kima/ 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}}.
* [http://www.zolnott.de/software/applications/ibm-acpi-applet-for-gnome-210-and-higher.html IBM ACPI applet] is a small gnome panel applet which shows the fan speed and thermal informations.
* 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 [[ibm-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 none Bus between Northbridge and DRAM
0xC1 none Southbridge, WLAN and clock generator (under Mini-PCI card, under touchpad)
0xC2 none 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 0
0x79 2 HDD
0x7A 3 HDD
0x7B 4 GPU
0x7C 5 Battery
0x7D 6 n/a
0x7E 7 Battery
0x7F 8 n/a
0xC0 none ?
0xC1 none ?
0xC2 none ?

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 {{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.

QuickStart and Deeper Sleep

2007-08-20T01:21:25Z

BDKMPSS: /* QuickStart and Deeper Sleep */ added more descriptions, removed "in thinkpads" as it may looks like this is a thinkpad only feature

== QuickStart and Deeper Sleep ==

QuickStart and Deeper Sleep are two processor features appearing in some Intel processors.

===Intels discription===

'''QuickStart''' extends battery life by reducing power during pauses in user activity, such as between keystrokes.

'''Deeper Sleep''' alert state is a dynamic power management mode which is enabled during less than a millisecond of inactivity by the user, such as between keystrokes, delivering longer battery life

===QuickStart===

This is one of the earlier C-State implementations, which was discarded/renamed in more recent processors.

===Deeper Sleep===

This is most commonly the last and deepest sleep-state available, but in fact its implementation was changed almost anytime in a new processor, just the names stays the same.

== References ==

http://www.intel.com/cd/channel/reseller/emea/spa/products/mobile/processors/proc_mobile_p3/index.htm

Intel Core 2 Duo (Merom)

2007-08-20T00:56:44Z

BDKMPSS: /* Features */ add link to deeper sleep

{| 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;">
===Intel Core 2 Duo ===
The Intel 2 Core is the successor of the [[Intel Core Duo (Yonah)]] processor. Even if the name seems like a second version, the Core 2 Duo is "only" a mobile version of the desktop processor with the same name and not designed for mobile applications in the first place like its predecessor. The architecture is changed in many ways, which introduced EM64T, [[SIMD|SSSE3]] and improved the performance by up to 25 percent. The 667 MHz FSB versions are part of the "Napa"- and the 800MHz FSB versions of the "Santa Rosa"-platform. It is part of the hardware from both the Centrino Duo and Centrino Pro brands.

===Features===
*Dual Core
*EM64T
*[http://en.wikipedia.org/wiki/Vanderpool#Intel_VT_.28IVT.29 Intel Virtualization Technology]
*XD-Bit
*[[SIMD|MMX]], [[SIMD|SSE]], [[SIMD|SSE2]], [[SIMD|SSE3]], [[SIMD|SSSE3]] instruction sets
*667 or 800 MHz FSB
*65 nm fabrication process
*4 MB or 2 MB L2-Cache with dynamic cache sizing
*[[SpeedStep|Enhanced Intel SpeedStep (EIST)]], power states: normal (C0), AutoHALT/MWAIT (C1), Stop Grant (C2), Deep Sleep (C3), [[QuickStart and Deeper Sleep|Deeper Sleep]] (C4)
</div>
|}

==Available Types and ThinkPads featuring them==
{| border=1 cellspacing=0 cellpadding=2
|- style="background:#ffdead;white-space:nowrap;"
! Nr. || colspan=2 | Frequency (MHz) || L2 Cache || FSB (MHz)|| VT || colspan=2 | core Voltage (V) || colspan=2 | TDP (W) || ThinkPad Models
|- style="background:#ffdead;"
! !!max. !! min. !! !! !! !! high !! low !! high freq !! low freq !!
|-
| T7700 || 2400 || 1000 || 4MB || 800 || yes || ? || ? || 35 || ? || {{R61}},{{T61}}
|-
| T7600 || 2333 || 1000 || 4MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{T60}},{{T60p}}
|-
| T7500 || 2200 || 1000 || 4MB || 800 || yes || ? || ? || 35 || ? || {{R61}},{{T61}}
|-
| T7400 || 2166 || 1000 || 4MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{T60}},{{Z61t}}
|-
| T7300 || 2000 || 1000 || 4MB || 800 || yes || 1.30 || 0.95 || 35 || ? || {{R61}},{{T61}}, {{X61s}}
|-
| T7200 || 2000 || 1000 || 4MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{R60}},{{T60}},{{X60}},{{Z61m}},{{Z61t}}
|-
| T7100 || 1800 || 1000 || 2MB || 800 || yes || ? || ? || 35 || ? || {{R61}},{{T61}}
|-
| T5600 || 1833 || 1000 || 2MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{R60}},{{T60}},{{X60}},{{Z61t}}
|-
| T5500 || 1666 || 1000 || 2MB || 667 || no || 1.30 || 0.95 || 34 || 20 || {{R60}},{{T60}},{{X60}},{{Z61m}},{{Z61t}}
|}

==Thermal Specifications==
The maximum temperature for safe operation is 100°C.

The catastrophic thermal protection temperature is 125°C.

==GCC Optimization Flags==
==See also==
[[Intel_Core_Solo_(Yonah)|Intel Core Solo (Yonah)]]

[[Intel Core Duo (Yonah)]]

==Links==
*[http://www.intel.com/products/processor_number/chart/core2duo.htm Intel - Processor Numbers and Features]
*[http://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors#Mobile_processors Wikipedia - Intel Core 2 mobile microprocessors]
[[Category:Components]]

Intel Core Solo (Yonah)

2007-08-20T00:56:00Z

BDKMPSS: /* Features */ add link to deeper sleep

Intel Core Duo (Yonah)

2007-08-20T00:55:16Z

BDKMPSS: /* Features */ add link to deeper sleep

{| 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;">
===Intel Core Duo (Yonah)===
The Intel Core is the successor of the [[Intel_Pentium_M_(Dothan)|Pentium M processor]]. The fabrication process was reduced again to 65 nm and with this generation Intel introduced Dual Core processors to the mobile market. The Intel Core processors feature a 667 MHz FSB and accompany the Napa Centrino platform.

===Features===
*Dual Core
*1.5 - 2.33 GHz clock speed
*15 (low voltage) or 31 (normal voltage) watt thermal design power consumption
*667 MHz FSB
*151 Million Transistors
*65 nm fabrication process
*2 MB L2-Cache with dynamic cache sizing
*[[SpeedStep|Enhanced Intel SpeedStep (EIST)]], power states: normal (C0), AutoHALT/MWAIT (C1), Stop Grant (C2), Deep Sleep (C3), [[QuickStart and Deeper Sleep|Deeper Sleep]] (C4)
*[[SIMD|MMX]], [[SIMD|SSE]], [[SIMD|SSE2]], [[SIMD|SSE3]] instruction sets, XD-Bit
*[http://en.wikipedia.org/wiki/Vanderpool#Intel_VT_.28IVT.29 Intel Virtualization Extensions], except for T2300e
</div>
|}

==Available Types and ThinkPads featuring them==
{| border=1 cellspacing=0 cellpadding=2
|- style="background:#ffdead;white-space:nowrap;"
! Nr. || colspan=2 | Frequency (MHz) || FSB (MHz)|| XD-Bit || colspan=2 | core Voltage (V) || colspan=2 | TDP (W) || ThinkPad Models
|- style="background:#ffdead;"
! !!max. !! min. !! !! !! high !! low !! high freq !! low freq !!
|- style="background:#efefef;"
! colspan=10 | Intel Core Duo
|-
| T2700 || 2333 || 1000 || 667 || yes || 1.2 || ... || 31 || 13.1 || {{T60}}, {{T60p}}
|-
| T2600 || 2166 || 1000 || 667 || yes || 1.2 || ... || 31 || 13.1 || {{T60p}}
|-
| T2500 || 2000 || 1000 || 667 || yes || 1.2 || ... || 31 || 13.1 || {{T60}}, {{T60p}}, {{Z61m}}
|-
| T2400 || 1833 || 1000 || 667 || yes || 1.2 || ... || 31 || 13.1 || {{T60}}, {{X60}}, {{z61m}}, {{R60}}
|-
| T2300 || 1666 || 1000 || 667 || yes || 1.2 || ... || 31 || 13.1 || {{T60}}, {{X60}}, {{Z61e}}
|-
| T2300E || 1666 || 1000 || 667 || yes || 1.2 || ... || 31 || 13.1 || {{R60e}}
|- style="background:#efefef;"
! colspan=10 | Intel Core Duo (Low Voltage)
|-
| L2500 || 1833 || 1000 || 667 || yes || 1.1 || ... || 15 || 13.1 || {{X60t}}
|-
| L2400 || 1666 || 1000 || 667 || yes || 1.1 || ... || 15 || 13.1 || {{X60s}}, {{X60t}}
|-
| L2300 || 1500 || 1000 || 667 || yes || 1.1 || ... || 15 || 13.1 || {{X60s}}
|}

==Thermal Specifications==
The maximum temperature for safe operation is 100 Â°C.

==GCC Optimization Flags==
Safe, recommended optimizations for GCC 3.4.x and later:
-pipe -O2 -march=prescott -fomit-frame-pointer

Possibly unsafe optimizations for GCC 3.3.x and later:
-mfpmath=sse

Optimizations likely to break binary-only compatibility:
-ffast-math

==See also==
* [[Intel Pentium M (Dothan)]]
* [[Intel Core Solo (Yonah)]]
* [[Intel Core 2 Duo]]

[[Category:Components]]

Intel Pentium M (Dothan)

2007-08-20T00:53:09Z

BDKMPSS: /* Features */ same here... features deeper sleep but no quickstart

{| 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;">
===Intel Pentium M (Dothan)===
The Pentium M "Dothan" is the second generation Pentium M processor. The fabrication process was reduced to 90 nm and the L2-Cache was doubled to 2 MB. The second generation of Dothan Pentium M processors features a 533 MHz FSB and accompanies the Sonoma Centrino platform.

===Features===
*1.0 - 2.26 GHz clock speed
*400/533 MHz FSB
*170 Million Transistors
*90 nm fabrication process
*2 MB L2-Cache
*[[SpeedStep|(Enhanced) EIST]], [[QuickStart and Deeper Sleep|Deeper Sleep]]
* XD-Bit (on most models)
*[[SIMD|MMX]], [[SIMD|SSE]], [[SIMD|SSE2]] instruction sets
</div>
|}

==Available Types and ThinkPads featuring them==
{| border=1 cellspacing=0 cellpadding=2
|- style="background:#ffdead;white-space:nowrap;"
! Nr. || colspan=2 | Frequency (MHz) || FSB (MHz)|| XD-Bit || colspan=2 | core Voltage (V) || colspan=2 | TDP (W) || ThinkPad Models
|- style="background:#ffdead;"
! !!max. !! min. !! !! !! high !! low !! high !! low !!
|- style="background:#efefef;"
! colspan="10" | Pentium M
|-
| 780 || 2266 || 800 || 533 || • || 1.372 || ... || 27 || 11 || {{R52}}, {{T43}}. {{T43p}}
|-
| 770 || 2133 || 800 || 533 || • || 1.372 || 0.988 || 27 || 11 || {{R52}}, {{T43}}, {{T43p}}
|-
| 765 || 2100 || 600 || 400 || || 1.34 || 0.988 || 21 || 8 || {{T42p}}
|-
| 760 || 2000 || 800 || 533 || • || 1.372 || 0.988 || 27 || 11 || {{R52}}, {{T43}}, {{T43p}}, {{Z60m}}, {{Z60t}}
|-
| 755 || 2000 || 600 || 400 || || 1.34 || 0.988 || 21 || 8 || {{T42p}}, {{X32}}
|-
| 750 || 1866 || 800 || 533 || • || 1.372 || 0.988 || 27 || 11 || {{R52}}, {{T43}}, {{T43p}}, {{Z60m}}, {{Z60t}}
|-
| 745 || 1800 || 600 || 400 || || 1.34 || 0.988 || 21 || 8 || {{T42}}, {{T42p}}, {{X32}}, {{R51}}
|-
| 740 || 1733 || 800 || 533 || • || 1.372 || 0.988 || 27 || 11 || {{R51e}}, {{R52}}, {{T43}}, {{Z60m}}, {{Z60t}}
|-
| 735 || 1700 || 600 || 400 || || 1.34 || 0.988 || 21 || 8 || {{R50e}}, {{R51}}, {{T42}}, {{X32}}
|-
| 730 || 1600 || 800 || 533 || • || 1.372 || 0.988 || 27 || 11 || {{T43}}
|-
| 725a || 1600 || 600 || 400 || || ... || ... || ... || ... || {{R50e}}, {{R51}}, {{R52}}
|-
| 725 || 1600 || 600 || 400 || || 1.34 || 0.988 || 21 || 8 || {{R50e}}, {{R51}}, {{T42}}, {{X32}}
|-
| 715a || 1500 || 600 || 400 || || ... || ... || ... || ... || {{R50e}}, {{R51}}
|-
| 715 || 1500 || 600 || 400 || || 1.34 || 0.988 || 21 || 8 || {{R50e}}, {{R51}}
|-
| 710 || 1400 || ... || 400 || || ... || ... || ... || ... || {{R50e}}, {{R51}}
|- style="background:#efefef;"
! colspan="10" | Pentium M (Low Voltage)
|-
| 778 || 1600 || ... || 400 || • || 1.116 || ... || 10 || ... || {{X40}}, {{X41}}, {{X41T}}
|-
| 758 || 1500 || 600 || 400 || • || 1.116 || 0.988 || 10 || ... || {{X40}}, {{X41}}, {{X41T}}
|-
| 738 || 1400 || ... || 400 || || 1.116 || 0.988 || 10 || ... || {{X40}}
|- style="background:#efefef;"
! colspan="10" | Pentium M (Ultra Low Voltage)
|-
| 773 || 1300 || ... || 400 || • || ... || ... || ... || ... ||
|-
| 753 || 1200 || ... || 400 || • || 0.940 || 0.812 || 5 || ... || {{X41T}}
|-
| 733J || 1100 || ... || 400 || • || .... || ... || ... || ... ||
|-
| 733 || 1100 || ... || 400 || || 0.940 || 0.812 || 5 || ... || {{X40}}
|-
| 723 || 1000 || ... || 400 || || 0.940 || 0.812 || 5 || ... ||
|}

==Thermal Specifications==
The max. Core Temperature is 100°C.

==GCC Optimization Flags==
You should use the following for GCC version 3.4.4 and later if you have a Pentium M:
-Os -march=pentium-m -pipe

For GCC version 3.3.5 and earlier use the following:
-Os -march=pentium3 -msse2 -pipe

Also, if you don't plan to use debugging information, then you can safely add the following to either of the above for a possible performance improvement:
-fomit-frame-pointer

==See also==
* [[Intel Pentium M (Banias)]]
* [[Intel Core Duo (Yonah)]]
* [[Pentium M undervolting and underclocking]]

[[Category:Components]]

Intel Pentium M (Banias)

2007-08-20T00:52:01Z

BDKMPSS: /* Features */ Pentium M features Deeper Sleep to (but not Quickstart...)

{| 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;">
===Intel Mobile Pentium M (Banias)===
After the efficiency problems with the [[Intel_Mobile_Pentium_4-M|Pentium 4 based mobile processors]], Intel decided to go back to the [[Intel Mobile Pentium III-M|Tualatin]] architecture as development base, extending its potential. The result is the Pentium M mobile processor.

===Features===
*1.3-1.7 GHz tact
*400 MHz FSB
*77 Million Transistors
*0.13µm fabrication process
*0.07µm gates
*1 MB L2-Cache
*[[SpeedStep|(Enhanced) EIST]], [[QuickStart and Deeper Sleep|Deeper Sleep]]
*[[SIMD|MMX]], [[SIMD|SSE]], [[SIMD|SSE2]] instruction sets
</div>
|}

==Available Types and ThinkPads featuring them==
{| border=1 cellspacing=0 cellpadding=2
|- style="background:#ffdead;white-space:nowrap;"
! Nr. || colspan=2 | Frequency (MHz) || FSB (MHz)|| colspan=2 | core Voltage (V) || colspan=2 | Power cons. (W) || ThinkPad Models
|- style="background:#ffdead;"
! !!max. !! min. !! !! high !! low !! high !! low !!
|- style="background:#efefef;"
! colspan=9 | Mobile Pentium M
|-
| || 1700 || 600 || 400 || 1.484 || 0.956 || 24.5 || ... || {{R50}}, {{R50p}}, {{R51}}, {{T41}}, {{T41p}}, {{X31}}
|-
| || 1600 || 600 || 400 || 1.484 || 0.956 || 24.5 || ... || {{R50}}, {{R51}}, {{T40}}, {{T40p}}, {{T41}}, {{X31}}
|-
| 705 || 1500 || ... || 400 || 1.484 || 0.956 || 24.5 || ... || {{R40}}, {{R50}}, {{R50e}}, {{R51}}, {{T40}}, {{X31}}, {{T42}}
|-
| || 1400 || 600 || 400 || 1.484 || 0.956 || 22 || ... || {{R40}}, {{R50}}, {{T40}}, {{T41}}, {{X31}}
|-
| || 1300 || 600 || 400 || 1.388 || 0.960 || 22 || ... || {{R40}}, {{T40}}, {{X31}}
|- style="background:#efefef;"
! colspan=9 | Mobile Pentium M (Low Voltage)
|-
| 718 || 1300 || ... || 400 || 1.18 || 0.956 || 12 || ... || {{X40}}
|-
| || 1200 || ... || 400 || 1.18 || 0.956 || 12 || ... || {{X40}}
|-
| || 1100 || ... || 400 || 1.18 || 0.956 || 12 || ... ||
|- style="background:#efefef;"
! colspan=9 | Mobile Pentium M (Ultra Low Voltage)
|-
| 713 || 1100 || ... || 400 || 1.004 || 0.844 || 7 || ... || {{X40}}
|-
| || 1000 || ... || 400 || 1.00 || 0.85 || 7 || ... || {{X40}}
|-
| || 900 || ... || 400 || 1.00 || 0.85 || 7 || ... ||
|-
| || 600 || ... || 400 || 0.956 || ... || ... || ... ||
|-
| || 600 || ... || 400 || 0.844 || ... || ... || ... ||
|}

==Thermal Specifications==
The max. Core Temperature is 100°C.

==GCC Optimization Flags==
CFLAGS="-march=pentium3 -O3 -pipe -msse2 -fomit-frame-pointer -fforce-addr -fprefetch-loop-arrays"

==See also==
* [[Intel_Mobile_Pentium_III-M]]
* [[Intel Pentium M (Dothan)]]
* [[Pentium M undervolting and underclocking]]

==Links==
* [http://download.intel.com/design/mobile/datashts/25261203.pdf Intel Datasheet for the Pentium-M Banias, Order Number 252612-003, April 2004] - PDF Document

[[Category:Components]]

Intel Core Duo (Yonah)

2007-08-20T00:26:31Z

BDKMPSS: /* See also */ added link to the predecessor

{| 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;">
===Intel Core Duo (Yonah)===
The Intel Core is the successor of the [[Intel_Pentium_M_(Dothan)|Pentium M processor]]. The fabrication process was reduced again to 65 nm and with this generation Intel introduced Dual Core processors to the mobile market. The Intel Core processors feature a 667 MHz FSB and accompany the Napa Centrino platform.

===Features===
*Dual Core
*1.5 - 2.33 GHz clock speed
*15 (low voltage) or 31 (normal voltage) watt thermal design power consumption
*667 MHz FSB
*151 Million Transistors
*65 nm fabrication process
*2 MB L2-Cache with dynamic cache sizing
*[[SpeedStep|Enhanced Intel SpeedStep (EIST)]], power states: normal (C0), AutoHALT/MWAIT (C1), Stop Grant (C2), Deep Sleep (C3), Deeper Sleep (C4)
*[[SIMD|MMX]], [[SIMD|SSE]], [[SIMD|SSE2]], [[SIMD|SSE3]] instruction sets, XD-Bit
*[http://en.wikipedia.org/wiki/Vanderpool#Intel_VT_.28IVT.29 Intel Virtualization Extensions], except for T2300e
</div>
|}

==Available Types and ThinkPads featuring them==
{| border=1 cellspacing=0 cellpadding=2
|- style="background:#ffdead;white-space:nowrap;"
! Nr. || colspan=2 | Frequency (MHz) || FSB (MHz)|| XD-Bit || colspan=2 | core Voltage (V) || colspan=2 | TDP (W) || ThinkPad Models
|- style="background:#ffdead;"
! !!max. !! min. !! !! !! high !! low !! high freq !! low freq !!
|- style="background:#efefef;"
! colspan=10 | Intel Core Duo
|-
| T2700 || 2333 || 1000 || 667 || yes || 1.2 || ... || 31 || 13.1 || {{T60}}, {{T60p}}
|-
| T2600 || 2166 || 1000 || 667 || yes || 1.2 || ... || 31 || 13.1 || {{T60p}}
|-
| T2500 || 2000 || 1000 || 667 || yes || 1.2 || ... || 31 || 13.1 || {{T60}}, {{T60p}}, {{Z61m}}
|-
| T2400 || 1833 || 1000 || 667 || yes || 1.2 || ... || 31 || 13.1 || {{T60}}, {{X60}}, {{z61m}}, {{R60}}
|-
| T2300 || 1666 || 1000 || 667 || yes || 1.2 || ... || 31 || 13.1 || {{T60}}, {{X60}}, {{Z61e}}
|-
| T2300E || 1666 || 1000 || 667 || yes || 1.2 || ... || 31 || 13.1 || {{R60e}}
|- style="background:#efefef;"
! colspan=10 | Intel Core Duo (Low Voltage)
|-
| L2500 || 1833 || 1000 || 667 || yes || 1.1 || ... || 15 || 13.1 || {{X60t}}
|-
| L2400 || 1666 || 1000 || 667 || yes || 1.1 || ... || 15 || 13.1 || {{X60s}}, {{X60t}}
|-
| L2300 || 1500 || 1000 || 667 || yes || 1.1 || ... || 15 || 13.1 || {{X60s}}
|}

==Thermal Specifications==
The maximum temperature for safe operation is 100 Â°C.

==GCC Optimization Flags==
Safe, recommended optimizations for GCC 3.4.x and later:
-pipe -O2 -march=prescott -fomit-frame-pointer

Possibly unsafe optimizations for GCC 3.3.x and later:
-mfpmath=sse

Optimizations likely to break binary-only compatibility:
-ffast-math

==See also==
* [[Intel Pentium M (Dothan)]]
* [[Intel Core Solo (Yonah)]]
* [[Intel Core 2 Duo]]

[[Category:Components]]

Intel Pentium M (Dothan)

2007-08-20T00:24:15Z

BDKMPSS: /* See also */ adding link to successor

{| 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;">
===Intel Pentium M (Dothan)===
The Pentium M "Dothan" is the second generation Pentium M processor. The fabrication process was reduced to 90 nm and the L2-Cache was doubled to 2 MB. The second generation of Dothan Pentium M processors features a 533 MHz FSB and accompanies the Sonoma Centrino platform.

===Features===
*1.0 - 2.26 GHz clock speed
*400/533 MHz FSB
*170 Million Transistors
*90 nm fabrication process
*2 MB L2-Cache
*[[SpeedStep|(Enhanced) EIST]], XD-Bit (on most models)
*[[SIMD|MMX]], [[SIMD|SSE]], [[SIMD|SSE2]] instruction sets
</div>
|}

==Available Types and ThinkPads featuring them==
{| border=1 cellspacing=0 cellpadding=2
|- style="background:#ffdead;white-space:nowrap;"
! Nr. || colspan=2 | Frequency (MHz) || FSB (MHz)|| XD-Bit || colspan=2 | core Voltage (V) || colspan=2 | TDP (W) || ThinkPad Models
|- style="background:#ffdead;"
! !!max. !! min. !! !! !! high !! low !! high !! low !!
|- style="background:#efefef;"
! colspan="10" | Pentium M
|-
| 780 || 2266 || 800 || 533 || • || 1.372 || ... || 27 || 11 || {{R52}}, {{T43}}. {{T43p}}
|-
| 770 || 2133 || 800 || 533 || • || 1.372 || 0.988 || 27 || 11 || {{R52}}, {{T43}}, {{T43p}}
|-
| 765 || 2100 || 600 || 400 || || 1.34 || 0.988 || 21 || 8 || {{T42p}}
|-
| 760 || 2000 || 800 || 533 || • || 1.372 || 0.988 || 27 || 11 || {{R52}}, {{T43}}, {{T43p}}, {{Z60m}}, {{Z60t}}
|-
| 755 || 2000 || 600 || 400 || || 1.34 || 0.988 || 21 || 8 || {{T42p}}, {{X32}}
|-
| 750 || 1866 || 800 || 533 || • || 1.372 || 0.988 || 27 || 11 || {{R52}}, {{T43}}, {{T43p}}, {{Z60m}}, {{Z60t}}
|-
| 745 || 1800 || 600 || 400 || || 1.34 || 0.988 || 21 || 8 || {{T42}}, {{T42p}}, {{X32}}, {{R51}}
|-
| 740 || 1733 || 800 || 533 || • || 1.372 || 0.988 || 27 || 11 || {{R51e}}, {{R52}}, {{T43}}, {{Z60m}}, {{Z60t}}
|-
| 735 || 1700 || 600 || 400 || || 1.34 || 0.988 || 21 || 8 || {{R50e}}, {{R51}}, {{T42}}, {{X32}}
|-
| 730 || 1600 || 800 || 533 || • || 1.372 || 0.988 || 27 || 11 || {{T43}}
|-
| 725a || 1600 || 600 || 400 || || ... || ... || ... || ... || {{R50e}}, {{R51}}, {{R52}}
|-
| 725 || 1600 || 600 || 400 || || 1.34 || 0.988 || 21 || 8 || {{R50e}}, {{R51}}, {{T42}}, {{X32}}
|-
| 715a || 1500 || 600 || 400 || || ... || ... || ... || ... || {{R50e}}, {{R51}}
|-
| 715 || 1500 || 600 || 400 || || 1.34 || 0.988 || 21 || 8 || {{R50e}}, {{R51}}
|-
| 710 || 1400 || ... || 400 || || ... || ... || ... || ... || {{R50e}}, {{R51}}
|- style="background:#efefef;"
! colspan="10" | Pentium M (Low Voltage)
|-
| 778 || 1600 || ... || 400 || • || 1.116 || ... || 10 || ... || {{X40}}, {{X41}}, {{X41T}}
|-
| 758 || 1500 || 600 || 400 || • || 1.116 || 0.988 || 10 || ... || {{X40}}, {{X41}}, {{X41T}}
|-
| 738 || 1400 || ... || 400 || || 1.116 || 0.988 || 10 || ... || {{X40}}
|- style="background:#efefef;"
! colspan="10" | Pentium M (Ultra Low Voltage)
|-
| 773 || 1300 || ... || 400 || • || ... || ... || ... || ... ||
|-
| 753 || 1200 || ... || 400 || • || 0.940 || 0.812 || 5 || ... || {{X41T}}
|-
| 733J || 1100 || ... || 400 || • || .... || ... || ... || ... ||
|-
| 733 || 1100 || ... || 400 || || 0.940 || 0.812 || 5 || ... || {{X40}}
|-
| 723 || 1000 || ... || 400 || || 0.940 || 0.812 || 5 || ... ||
|}

==Thermal Specifications==
The max. Core Temperature is 100°C.

==GCC Optimization Flags==
You should use the following for GCC version 3.4.4 and later if you have a Pentium M:
-Os -march=pentium-m -pipe

For GCC version 3.3.5 and earlier use the following:
-Os -march=pentium3 -msse2 -pipe

Also, if you don't plan to use debugging information, then you can safely add the following to either of the above for a possible performance improvement:
-fomit-frame-pointer

==See also==
* [[Intel Pentium M (Banias)]]
* [[Intel Core Duo (Yonah)]]
* [[Pentium M undervolting and underclocking]]

[[Category:Components]]

Intel Pentium M (Banias)

2007-08-20T00:19:55Z

BDKMPSS: adding link to the predecessor, extending the description

{| 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;">
===Intel Mobile Pentium M (Banias)===
After the efficiency problems with the [[Intel_Mobile_Pentium_4-M|Pentium 4 based mobile processors]], Intel decided to go back to the [[Intel Mobile Pentium III-M|Tualatin]] architecture as development base, extending its potential. The result is the Pentium M mobile processor.

===Features===
*1.3-1.7 GHz tact
*400 MHz FSB
*77 Million Transistors
*0.13µm fabrication process
*0.07µm gates
*1 MB L2-Cache
*[[SpeedStep|(Enhanced) EIST]]
*[[SIMD|MMX]], [[SIMD|SSE]], [[SIMD|SSE2]] instruction sets
</div>
|}

==Available Types and ThinkPads featuring them==
{| border=1 cellspacing=0 cellpadding=2
|- style="background:#ffdead;white-space:nowrap;"
! Nr. || colspan=2 | Frequency (MHz) || FSB (MHz)|| colspan=2 | core Voltage (V) || colspan=2 | Power cons. (W) || ThinkPad Models
|- style="background:#ffdead;"
! !!max. !! min. !! !! high !! low !! high !! low !!
|- style="background:#efefef;"
! colspan=9 | Mobile Pentium M
|-
| || 1700 || 600 || 400 || 1.484 || 0.956 || 24.5 || ... || {{R50}}, {{R50p}}, {{R51}}, {{T41}}, {{T41p}}, {{X31}}
|-
| || 1600 || 600 || 400 || 1.484 || 0.956 || 24.5 || ... || {{R50}}, {{R51}}, {{T40}}, {{T40p}}, {{T41}}, {{X31}}
|-
| 705 || 1500 || ... || 400 || 1.484 || 0.956 || 24.5 || ... || {{R40}}, {{R50}}, {{R50e}}, {{R51}}, {{T40}}, {{X31}}, {{T42}}
|-
| || 1400 || 600 || 400 || 1.484 || 0.956 || 22 || ... || {{R40}}, {{R50}}, {{T40}}, {{T41}}, {{X31}}
|-
| || 1300 || 600 || 400 || 1.388 || 0.960 || 22 || ... || {{R40}}, {{T40}}, {{X31}}
|- style="background:#efefef;"
! colspan=9 | Mobile Pentium M (Low Voltage)
|-
| 718 || 1300 || ... || 400 || 1.18 || 0.956 || 12 || ... || {{X40}}
|-
| || 1200 || ... || 400 || 1.18 || 0.956 || 12 || ... || {{X40}}
|-
| || 1100 || ... || 400 || 1.18 || 0.956 || 12 || ... ||
|- style="background:#efefef;"
! colspan=9 | Mobile Pentium M (Ultra Low Voltage)
|-
| 713 || 1100 || ... || 400 || 1.004 || 0.844 || 7 || ... || {{X40}}
|-
| || 1000 || ... || 400 || 1.00 || 0.85 || 7 || ... || {{X40}}
|-
| || 900 || ... || 400 || 1.00 || 0.85 || 7 || ... ||
|-
| || 600 || ... || 400 || 0.956 || ... || ... || ... ||
|-
| || 600 || ... || 400 || 0.844 || ... || ... || ... ||
|}

==Thermal Specifications==
The max. Core Temperature is 100°C.

==GCC Optimization Flags==
CFLAGS="-march=pentium3 -O3 -pipe -msse2 -fomit-frame-pointer -fforce-addr -fprefetch-loop-arrays"

==See also==
* [[Intel_Mobile_Pentium_III-M]]
* [[Intel Pentium M (Dothan)]]
* [[Pentium M undervolting and underclocking]]

==Links==
* [http://download.intel.com/design/mobile/datashts/25261203.pdf Intel Datasheet for the Pentium-M Banias, Order Number 252612-003, April 2004] - PDF Document

[[Category:Components]]

Intel Mobile Pentium III-M

2007-08-20T00:15:08Z

BDKMPSS: link is not external, tulatin is not exactly reborn as P-M

{| 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;">
===Intel Mobile Pentium III-M===
Featuring the Tualatin core the Mobile Pentium III-M is a lot more powerful than the [[Intel Mobile Pentium III|Mobile Pentium III]]. This is proven in being the development base for the [[Intel Pentium M (Banias)|Pentium M]].

===Features===
*700-1200 MHz tact
*133 MHz FSB (100 on some of the lv and ulv models)
*44 Million Transistors
*0.13µm fabrication process
*0.07µm gates
*1.40/1.15 VCore
*2x 16 KB L1-Cache
*512 KB L2-Cache
*[[SpeedStep|Enhanced SpeedStep]], [[QuickStart and Deeper Sleep|QuickStart]], [[QuickStart and Deeper Sleep|Deeper Sleep]]
*[[SIMD|MMX]], [[SIMD|SSE]] instruction sets
</div>
|}

==Available Types and ThinkPads featuring them==
{| border=1 cellspacing=0 cellpadding=2
|- style="background:#ffdead;"
! colspan=2 | Frequency (MHz) || Bus Speed (MHz)|| colspan=2 | core Voltage (V) || colspan=2 | TDP (W) || ThinkPad Models
|- style="background:#ffdead;"
!max. !! min. !! !! high !! low !! high !! low !!
|- style="background:#efefef;"
! colspan=8 | Mobile Pentium III-M
|-
| 1333 || 800 || 133 || 1.40 || 1.15 || 22.0 || 9.8 ||
|-
| 1266 || 800 || 133 || 1.40 || 1.15 || 22.0 || 9.8 ||
|-
| 1200 || 800 || 133 || 1.40 || 1.15 || 22.0 || 9.8 || {{A30p}}, {{T23}}, {{X30}}
|-
| 1133 || 733 || 133 || 1.40 || 1.15 || 21.8 || 9.3 || {{A30}}, {{R31}}, {{T23}}, {{X24}}
|-
| 1066 || 733 || 133 || 1.40 || 1.15 || 21.0 || 9.3 || {{X30}}
|-
| 1000 || 733 || 133 || 1.40 || 1.15 || 20.5 || 9.3 || {{A30}}, {{R31}}, {{T23}}
|-
| 933 || 733 || 133 || 1.40 || 1.15 || 20.1 || 9.3 || {{A30}}
|-
| 866 || 667 || 133 || 1.40 || 1.15 || 19.5 || 8.9 || {{T23}}
|- style="background:#efefef;"
! colspan=8 | Mobile Pentium III-M (Low Voltage)
|-
| 1000 || 533 || 133 || 1.15 || 1.05 || 10.9 || 6.1 ||
|-
| 933 || 533 || 133 || 1.15 || 1.05 || 10.5 || 6.1 ||
|-
| 866 || 533 || 133 || 1.15 || 1.05 || 10.1 || 6.1 || {{X23}}?
|-
| 850 || 500 || 100 || 1.15 || 1.05 || 10.0 || 5.9 ||
|-
| 800 || 533 || 133 || 1.15 || 1.05 || 9.8 || 5.9 || {{X22}}?, {{X23}}?
|-
| 750 || 450 || 100 || 1.15 || 1.05 || 9.4 || 5.7 ||
|-
| 733 || 466 || 133 || 1.15 || 1.05 || 9.3 || 5.8 || {{X22}}?
|- style="background:#efefef;"
! colspan=8 | Mobile Pentium III-M (Ultra Low Voltage)
|-
| 866 || 400 || 133 || 1.10 || 0.95 || 7 || 3.4 ||
|-
| 850 || 400 || 100 || 1.10 || 0.95 || 7 || 3.4 ||
|-
| 800 || 400 || 100 || 1.10 || 0.95 || 7 || 3.4 ||
|-
| 750 || 350 || 100 || 1.10 || 0.95 || 7 || 3.1 ||
|-
| 733 || 400 || 133 || 1.10 || 0.95 || 7 || 3.4 ||
|-
| 700 || 300 || 100 || 1.10 || 0.95 || 7 || 3.0 ||
|}

==Thermal Specifications==

==Speedstepping==

[[Installing_Ubuntu_on_a_ThinkPad_T23#Power_Management|The page on installing Ubuntu on a T23]] includes tips for monitoring and managing the processor speed settings.

==GCC Optimization Flags==
You should use the following if you have a Mobile Pentium III-M:
-Os -march=pentium3m -fomit-frame-pointer -pipe

"-Os" means optimise for size. "-O2" is usually the default and is probably more prefferable. If you're feeling brave you could try using "-O3", but many programs fail to compile with this (attempting to compile binutils, gcc or any other core tools with "-O3" is not recommended)

==See also==
* [[Intel_Mobile_Pentium_III]]
* [[Intel Pentium M (Banias)]]

[[Category:Components]]

Buyers Guide

2007-08-10T15:39:13Z

BDKMPSS: /* Long-time Weaknesses of certain models */ The T4x drive is a standard UltraBay Slim Device, nothing to bogous to get a replacement for.

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
This page is dedicated to hints about buying used or new ThinkPad models. You can find notes about typical weaknesses of used ThinkPads here and other things you should care about when choosing a ThinkPad and where to buy it.
|}
==Build it yourself and save money==
Lenovo offers more flexibility than any other major manufacturer of laptop computers, at least that I know of. Their "configure-to-order" (CTO) offerings let you build the computer you want, without paying for anything you don't want. The basic CTO includes the mainboard and CPU, but no RAM, disk, mini-PCI cards, software, or other add-ons. You can even get a laptop in a CTO configuration.

I built my {{X32}} notebook with 1GB RAM, 60GB 5400RPM hard drive, USB DVD-ROM CD-RW drive, and 802.11a/b/g mini-PCI for a grand total of US$1,206, including tax and shipping.

Start with the complete list of [https://www-03.ibm.com/lenovo/shop/personalpages/public/public/products/dsp_product_list.cfm products]. Look for items that end with "CTO" or "Custom." Choose the chassis you want. Then add whatever [http://www-132.ibm.com/content/home/store_IBMPublicUSA/en_US/Upgrades.html upgrades] you need that only Lenovo offers (such as WiFi). Fill in the rest of the components from other, less expensive vendors.

Update: you cant do this nowadays. They will not sell you a CTO barebone. At least you cant do it online. You might have to 'con' a sales agent.

Response to update: I did not need to con anyone. I just ordered the CTO chassis and the parts I needed from their website. I placed the order on August 18, 2005 and received all the shipments by August 26, 2005.

Comment from visitor: [https://www-03.ibm.com/lenovo/shop/personalpages/public/public/products/dsp_feature_product.cfm?display=main&cat_id=24 Try this page]. You can at least get a Z60 with the titanium cover in a more stripped down model than is otherwise available.

==Various deals==

Special prices: You can get a laptop from Lenovo for special price if you are a student, alumni, researcher
or something like that. You need to go to education -> computers for home -> students (or such), and
now click on "My Account" to create a new account. Perhaps there is another way, but you must end up with a student
account. Then you get around 5% off the web price.

You can also buy a Lenovo thinkpad pre-configured with Linux from [http://www.linuxcertified.com/linux-laptop-lctp60.html here]

The [https://www.directlenovo.com/public/ Lenovo USA sales web site] offers some attractive deals in its [http://www.directlenovo.com/public/public/search/dsp_product_features.cfm?category=9953&featured_display=Template surplus outlet].

IBM sells [http://www-132.ibm.com/webapp/wcs/stores/servlet/CategoryDisplay?storeId=1&catalogId=-840&langId=-1&categoryId=2576396 refurbished ThinkPads].

== Special deals for certain customer groups ==
IBM makes huge discounts to students and teachers:
{| border="1" cellspacing="0" cellpadding="2" style="text-align:left;"
! country !! shops & target groups
|-
| Austria ||
* [http://www.studentline.at/ Studentline.at] (students, university staff, pupils and teachers)
* [http://www.notebook4u.at/ notebook4u.at] (students, university staff, pupils and teachers)
* [http://www.abax.at/academic/ ABAX] (students, university staff, pupils and teachers)
* [http://www.bostelmann.com/ Computer Bostelmann] (students, university staff, pupils and teachers)
|- style="vertical-align:top;"
| France ||
*[http://www.ibm.com/easyaccess/education IBM education homepage]
|- style="vertical-align:top;"
| Germany ||
*[http://www.notebooksbilliger.de notebooksbilliger.de] (pupils, students)
*[http://www.lapstars.de lapstars.de] (students, university staff, pupils and teachers)
*[http://www.ok1.de ok1] (students, university staff, pupils and teachers)
*[http://www.campusrabatt.de/index.php ADD Datensysteme: CampusRabatt] (students, university staff, pupils and teachers)
*[http://www.pro-com.org pro-com Datensysteme]:
**[http://www.pro-com.org/b2b pro-com b2b] (businesses)
**[http://www.nofost.de/ NOFOST] (students & university staff)
**[http://www.no4ed.de/ NOFOED] (pupils & teachers)
**[http://www.nofoch.de/ NOFOCH] (clinics and medical institutions and their staff)
**[http://www.pro-com.org/lf pro-com luf] (universities, schools & other educational and research institutes)
|- style="vertical-align:top;"
| Switzerland ||
*[http://www.rabais-etudiant.ch/ Rabais-Etudiant] (students, teachers, schools)
*[http://www.studentenrabatt.ch/ Studentenrabatt] (students, teachers, schools)
|- style="vertical-align:top;"
| United States ||
* [http://www.pc.ibm.com/us/education/ Education] (K-12 and Higher Education)
* [http://www.dealmine.com/search_by_product.php?s=thinkpad Comparison shop] at DealMine.com to find Thinkpad and membership discounts [http://www.dealmine.com/deals_from/Union_Plus/23 AFL-CIO/AFT] matched up at various stores
* IBM Employee Purchase Program (EPP) for IBM employees and their family and friends: [http://www.ibm.com/shop/us/epp/ IBM store] / [http://shoplenovo.i2.com/SEUILibrary/controller/Lenovo:EnterStdAffinity?affinity=eppibm Lenovo store]
* Corporate Perks program for corporate employees (e.g., accessible through the Microsoft Alumni Network)
|}

== Buying FRUs ==

You can buy single components, called, FRU (Field Replacement Unit), directly from Lenovo.

* US orders: https://www-132.ibm.com/content/home/store_IBMPublicUSA/en_US/parts/parts_r.html
* Other countries: http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-50278&sitestyle=lenovo

To find the right FRU, you can look up your model's part lists here:
* [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=TPAD-FRU Service parts list index - ThinkPad General]

== Official list of linux certified computers ==

* A [http://www.lenovo.com/pc/support/site.wss/MIGR-48NT8D.html list] of completed Linux certifications on [http://www.lenovo.com lenovo web site]

==Where to by Linux preinstalled thinkpad==
* [http://laclinux.com/en/Laptop Los Alamos Computers] Custom Linux Thinkpads - T Series, Z Series, X Series 23 Apr 2007

== Buying on eBay ==
* Many sellers do not know exactly what they have. Get the full 7-digit machine type if at all possible. Compare it to the specifications in the *book.pdf series: twbook.pdf, tabook.pdf, tawbook.pdf, etc, to determine actual screen size, original CPU speed, original hard disk, etc.
* You can try getting the serial number as well to check the warranty status at IBMs support pages.
* Check completed auctions carefully to determine going prices for comparable machines.
* Be aware if any port covers are missing. If they are, see if any current auctions are running to check availability.
* If the unit doesn't come with a hard drive, know whether it has the caddy and cover. Make sure that the three passwords are NOT set or that you know the right passwords before you install your hard drive! If you don't: A password can be set into your hard disk automatically, making it a brick - useful for door stopping only!
* Anything with a PIII or later most likely came with a Windows Certificate of Authenticity. Find out whether the listed machine does. Even if you don't want it, it may help resale value when you '''sell''' the machine.
* Read the feedback of the seller on items he has sold, especially electronics, computers and laptops. If meangranny is suddenly selling T43's after three years of lace, stay away.
* If it seems too good to be true, it probably is. There's a reason no one else is bidding on it.

==Long-time Weaknesses of certain models==
{| border="1" cellspacing="0" cellpadding="2"
! Model !! Issues
|-
| {{390X}} || *models with 15" display are said to have weak display cables that tend to break.
|-
| {{600X}} || Battery problems.
|-
||{{A20p}}, {{390}}, {{390E}}, {{390X}} || *Base cover corners are prone to crack, root cause stiff display hinges
|-
||{{A31}} || Several reports of [[Problem with garbled screen]] independent on Operating System
|-
| {{A30}}, {{A30p}}, {{A31}}, {{A31p}} || *seem to have a mechanical design that can cause the motherboard to break. At least there are a significant number of reports of broken motherboards on these models.
|-
| {{T30}} || *had a problem with memory sockets detaching from the system board. IBM replaced these free of charge even after warranties expired.
|-
| {{T20}} || Many models have a problem of gradually dying. Attempting to turn on will only cause a blinking light, and many attempts must be made in order to start the machine. Eventually, the machine is no longer bootable.
|-
| {{T43}} || A number of laptops from the T-line are very thin (everything since {{T40}}?), which was to some degree possible by using the newer [[UltraBay|UltraBay Slim]], which is used in almost all Thinkpads now, instead of the old [[UltraBay|UltraBay Plus]]. This limits the available alternatives for optical drives, as they are not compatible with the industrial standard slimline drives, which are to thick. Some {{T43}}s have Matshita UJ-822S drives, and Matshita is infamous for striving extra to enforce the DVD regional codes. Purchasing such a laptop would effectively mean being locked to one DVD region, or you have to spend extra money and effort to get a better [[UltraBay_Devices#UltraBay Slim Devices|UltraBay Slim Drive]]. The {{T43}} family is also notorious for its [[problem with fan noise]] and has a [[problem with non-ThinkPad hard disks]]; its predecessor, the {{T42}} family, had none of these problems and offered better battery life.
|}

How to configure and use libata SATA / PATA drivers

2007-08-06T15:46:35Z

BDKMPSS: a note should be a note, right? ;)

==How to configure and use libata SATA / PATA drivers==

For now this mosty is for libata PATA drivers. Should work for SATA as well, I can't test it since I do not have an SATA based ThinkPad.

Configure your kernel as follows:

<pre>CONFIG_ATA=y
CONFIG_ATA_PIIX=y
CONFIG_ATA_GENERIC=y
CONFIG_BLK_DEV_SD=y
CONFIG_BLK_DEV_SR=m</pre>

You find those in "Device / Serial ATA (prod) and Parallel ATA (experimental) drivers" and "Device Drivers / SCSI device support" in menuconfig.

You need CONFIG_ATA_PIIX for current Intel chipsets - I got the hint from
Serge Belyshev out from a thread on the [http://members.optusnet.com.au/ckolivas/kernel/ ck mailinglist]. It is a labeled a bit misleading:
<pre>[ ] ServerWorks Frodo / Apple K2 SATA support
[*] Intel PIIX/ICH SATA support <--- there
[ ] Marvell SATA support (HIGHLY EXPERIMENTAL)</pre>

The other PIIX related options are for older chipsets.

{{NOTE|As of 2.6.22, the above option seems to be called "Intel ESB, ICH, PIIX3, PIIX4 PATA/SATA support" and is under Device Drivers -> Serial ATA (prod) and Pallel ATA (experimental)}}

Above configuration should also work for SATA as well, ATA_PIIX does SATA and PATA. For T60/X60/R60/Z60 series according to Henrique de Moraes Holschuh you might also need <tt>CONFIG_SATA_AHCI</tt>.

==Switching from old IDE drivers to libata drivers==

I tested libata PATA drivers on ThinkPad T23 and ThinkPad T42.

You can and probably should disable the whole IDE driver subsystem ("ATA/ATAPI/MFM/RLL support") when you switch from old IDE drivers to the new libata PATA drivers:

<pre>CONFIG_IDE=n</pre>

You need to change the bootloader configuration, rename all <tt>/dev/hd*</tt> to <tt>/dev/sd*</tt>. At least upto kernel 2.6.20 you also need to add the kernel boot option <tt>atapi_enabled=1</tt> to get out of the box working CD-ROM support. Otherwise you manually need to load the module sr_mod with modprobe sr_mod. This option will likely become the default in 2.6.21 or 2.6.22 as Henrique de Moraes Holschuh noted.

This is an example entry:

<pre>title Debian GNU/Linux, kernel 2.6.20.3-ck1-tp42-sws2-2.2.9.9
root (hd0,0)
kernel /boot/vmlinuz-2.6.20.3-ck1-tp42-sws2-2.2.9.9 root=/dev/sda1 ro resume2=swap:/dev/sda5 resume=/dev/sda5 vga=792 atap
i_enabled=1
savedefault</pre>

(on Debian/Ubuntu and possibly other distros you better change the kopt line and run update-grub)

You also need to change /etc/fstab. Replace any relevant <tt>dev/hd*</tt> with <tt>/dev/sd*</tt>. Better yet use labels or uuids. An example:

<pre># Debian
LABEL=debian / xfs defaults,logbufs=8 0 1
LABEL=swap none swap sw 0 2
proc /proc proc defaults 0 2
LABEL=home /home xfs defaults,logbufs=8 0 2</pre>

You need to set labels for your partition via specific filesystem or swapspace tools like <tt>xfs_admin -L</tt>, <tt>tune2fs -L</tt> and <tt>mkswap -L</tt>. This way fstab setup is independant of concrete device file names and thus you can switch back to old IDE drivers easily.

For the CD-ROM drive use <tt>/dev/scd0</tt>:

<pre>/dev/scd0 /cdrom iso9660 ro,user,noauto 0 0</pre>

This should enough to get the system up and running with the new libata PATA drivers. You may need to change other configuration files that refer to device files such as <tt>/etc/hdparm.conf</tt> and possibly <tt>/etc/sysfs.conf</tt> if you set an IO scheduler there (I just removed my cfq scheduler entries as it is the default in the meanwhile.

==Smartmontools and libata driven devices==

For libata driven devices you should use smartmontools 5.37 and the <tt>-d sat</tt> option. An example entry for ''/etc/smartd.conf'' would be:

<pre># Short selftest wednesday, sunday at 13 o clock.
# Long selftest thursday, 13 Uhr
# Email me on problems and use raw temperature values
/dev/sda -d sat -r 194 -a -o on -S on -n standby -m martin@deepdance -s (S/../../(3|7)/13|L/../../4/13)</pre>

==References==
[http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2007-March/038383.html Thread on linux-thinkpad mailing list]

SIMD

2007-08-04T11:50:30Z

BDKMPSS: added ssse3

SIMD (Single Instruction, Multiple Data) is a set of operations for efficiently handling large amounts of data. It makes it possible to execute one command on a set of data instances instead of having the same command to be executed on each of the data instances.

First introduced in large-scale supercomputers SIMD instrucion sets have become popular in personal computing hardware, hence being mostly associated with these units. The most widely known SIMD instructions sets are AIMs (Apple-IBM-Motorola) [[WikiPedia:AltiVec|AltiVec]] for the PowerPC, AMDs [[Wikipedia:3DNow!|3DNow!]] and Intels MMX and SSE sets in their various versions.

==MMX==
MMX is a SIMD instruction introduced by Intel with later models of the Pentium processor line. It provides integer operations only and has a strong limitation in that it makes it difficult to work with integer and floating point data at the same time, since it reuses the IA-32 FPU registers.

==SSE==
SSE is a set of instuctions optimized for handling floating point operations on a 128 bit level.

==SSE 2==
SSE 2 contains 144 new commands for Cache and Memory management and the 64 bit commands of the MMX set were improved and extended to 128 bit.

==SSE 3==
SSE 3 extends the SSE 2 command set by 13 instrucions for converting floating point numbers into integer numbers, for complex arithmetics, video encoding, image processing and thread communications.

==SSSE 3==
SSSE 3 extends the SSE 3 command set by 16 instrucions for both 32 and 64 Bit data (Intel counts it as 32)

[[Category:Glossary]]

Intel Core 2 Duo (Merom)

2007-08-04T11:44:40Z

BDKMPSS: added ssse3 to description

{| 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;">
===Intel Core 2 Duo ===
The Intel 2 Core is the successor of the [[Intel Core Duo (Yonah)]] processor. Even if the name seems like a second version, the Core 2 Duo is "only" a mobile version of the desktop processor with the same name and not designed for mobile applications in the first place like its predecessor. The architecture is changed in many ways, which introduced EM64T, [[SIMD|SSSE3]] and improved the performance by up to 25 percent. The 667 MHz FSB versions are part of the "Napa"- and the 800MHz FSB versions of the "Santa Rosa"-platform. It is part of the hardware from both the Centrino Duo and Centrino Pro brands.

===Features===
*Dual Core
*EM64T
*[http://en.wikipedia.org/wiki/Vanderpool#Intel_VT_.28IVT.29 Intel Virtualization Technology]
*XD-Bit
*[[SIMD|MMX]], [[SIMD|SSE]], [[SIMD|SSE2]], [[SIMD|SSE3]], [[SIMD|SSSE3]] instruction sets
*667 or 800 MHz FSB
*65 nm fabrication process
*4 MB or 2 MB L2-Cache with dynamic cache sizing
*[[SpeedStep|Enhanced Intel SpeedStep (EIST)]], power states: normal (C0), AutoHALT/MWAIT (C1), Stop Grant (C2), Deep Sleep (C3), Deeper Sleep (C4)
</div>
|}

==Available Types and ThinkPads featuring them==
{| border=1 cellspacing=0 cellpadding=2
|- style="background:#ffdead;white-space:nowrap;"
! Nr. || colspan=2 | Frequency (MHz) || L2 Cache || FSB (MHz)|| VT || colspan=2 | core Voltage (V) || colspan=2 | TDP (W) || ThinkPad Models
|- style="background:#ffdead;"
! !!max. !! min. !! !! !! !! high !! low !! high freq !! low freq !!
|-
| T7700 || 2400 || 1000 || 4MB || 800 || yes || ? || ? || 35 || ? || {{R61}},{{T61}}
|-
| T7600 || 2333 || 1000 || 4MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{T60}},{{T60p}}
|-
| T7500 || 2200 || 1000 || 4MB || 800 || yes || ? || ? || 35 || ? || {{R61}},{{T61}}
|-
| T7400 || 2166 || 1000 || 4MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{T60}},{{Z61t}}
|-
| T7300 || 1400 || 1000 || 4MB || 800 || yes || ? || ? || 35 || ? || {{R61}},{{T61}}, {{X61s}}
|-
| T7200 || 2000 || 1000 || 4MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{R60}},{{T60}},{{X60}},{{Z61m}},{{Z61t}}
|-
| T7100 || 1800 || 1000 || 2MB || 800 || yes || ? || ? || 35 || ? || {{R61}},{{T61}}
|-
| T5600 || 1833 || 1000 || 2MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{R60}},{{T60}},{{X60}},{{Z61t}}
|-
| T5500 || 1666 || 1000 || 2MB || 667 || no || 1.30 || 0.95 || 34 || 20 || {{R60}},{{T60}},{{X60}},{{Z61m}},{{Z61t}}
|}

==Thermal Specifications==
The maximum temperature for safe operation is 100°C.

The catastrophic thermal protection temperature is 125°C.

==GCC Optimization Flags==
==See also==
[[Intel_Core_Solo_(Yonah)|Intel Core Solo (Yonah)]]

[[Intel Core Duo (Yonah)]]

==Links==
*[http://www.intel.com/products/processor_number/chart/core2duo.htm Intel - Processor Numbers and Features]
*[http://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors#Mobile_processors Wikipedia - Intel Core 2 mobile microprocessors]
[[Category:Components]]

SIMD

2007-08-03T21:16:59Z

BDKMPSS: /* MMX */ MMX was not introduced with the Pentium, it was an later addition to them

Intel Core 2 Duo (Merom)

2007-08-03T21:12:35Z

BDKMPSS: /* Features */ and MMX, SSE1/2/3.... and SSSE3

{| 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;">
===Intel Core 2 Duo ===
The Intel 2 Core is the successor of the [[Intel Core Duo (Yonah)]] processor. Even if the name seems like a second version, the Core 2 Duo is "only" a mobile version of the desktop processor with the same name and not designed for mobile applications in the first place like its predecessor. The architecture is changed in many ways, which introduced EM64T and improved the performance by up to 25 percent. The 667 MHz FSB versions are part of the "Napa"- and the 800MHz FSB versions of the "Santa Rosa"-platform. It is part of the hardware from both the Centrino Duo and Centrino Pro brands.

===Features===
*Dual Core
*EM64T
*[http://en.wikipedia.org/wiki/Vanderpool#Intel_VT_.28IVT.29 Intel Virtualization Technology]
*XD-Bit
*[[SIMD|MMX]], [[SIMD|SSE]], [[SIMD|SSE2]], [[SIMD|SSE3]], [[SIMD|SSSE3]] instruction sets
*667 or 800 MHz FSB
*65 nm fabrication process
*4 MB or 2 MB L2-Cache with dynamic cache sizing
*[[SpeedStep|Enhanced Intel SpeedStep (EIST)]], power states: normal (C0), AutoHALT/MWAIT (C1), Stop Grant (C2), Deep Sleep (C3), Deeper Sleep (C4)
</div>
|}

==Available Types and ThinkPads featuring them==
{| border=1 cellspacing=0 cellpadding=2
|- style="background:#ffdead;white-space:nowrap;"
! Nr. || colspan=2 | Frequency (MHz) || L2 Cache || FSB (MHz)|| VT || colspan=2 | core Voltage (V) || colspan=2 | TDP (W) || ThinkPad Models
|- style="background:#ffdead;"
! !!max. !! min. !! !! !! !! high !! low !! high freq !! low freq !!
|-
| T7700 || 2400 || 1000 || 4MB || 800 || yes || ? || ? || 35 || ? || {{R61}},{{T61}}
|-
| T7600 || 2333 || 1000 || 4MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{T60}},{{T60p}}
|-
| T7500 || 2200 || 1000 || 4MB || 800 || yes || ? || ? || 35 || ? || {{R61}},{{T61}}
|-
| T7400 || 2166 || 1000 || 4MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{T60}},{{Z61t}}
|-
| T7300 || 1400 || 1000 || 4MB || 800 || yes || ? || ? || 35 || ? || {{R61}},{{T61}}, {{X61s}}
|-
| T7200 || 2000 || 1000 || 4MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{R60}},{{T60}},{{X60}},{{Z61m}},{{Z61t}}
|-
| T7100 || 1800 || 1000 || 2MB || 800 || yes || ? || ? || 35 || ? || {{R61}},{{T61}}
|-
| T5600 || 1833 || 1000 || 2MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{R60}},{{T60}},{{X60}},{{Z61t}}
|-
| T5500 || 1666 || 1000 || 2MB || 667 || no || 1.30 || 0.95 || 34 || 20 || {{R60}},{{T60}},{{X60}},{{Z61m}},{{Z61t}}
|}

==Thermal Specifications==
The maximum temperature for safe operation is 100°C.

The catastrophic thermal protection temperature is 125°C.

==GCC Optimization Flags==
==See also==
[[Intel_Core_Solo_(Yonah)|Intel Core Solo (Yonah)]]

[[Intel Core Duo (Yonah)]]

==Links==
*[http://www.intel.com/products/processor_number/chart/core2duo.htm Intel - Processor Numbers and Features]
*[http://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors#Mobile_processors Wikipedia - Intel Core 2 mobile microprocessors]
[[Category:Components]]

Intel Core 2 Duo (Merom)

2007-08-03T21:10:17Z

BDKMPSS: /* Features */ any core 2 duo should have the XD-Bit

{| 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;">
===Intel Core 2 Duo ===
The Intel 2 Core is the successor of the [[Intel Core Duo (Yonah)]] processor. Even if the name seems like a second version, the Core 2 Duo is "only" a mobile version of the desktop processor with the same name and not designed for mobile applications in the first place like its predecessor. The architecture is changed in many ways, which introduced EM64T and improved the performance by up to 25 percent. The 667 MHz FSB versions are part of the "Napa"- and the 800MHz FSB versions of the "Santa Rosa"-platform. It is part of the hardware from both the Centrino Duo and Centrino Pro brands.

===Features===
*Dual Core
*EM64T
*[http://en.wikipedia.org/wiki/Vanderpool#Intel_VT_.28IVT.29 Intel Virtualization Technology]
*XD-Bit
*667 or 800 MHz FSB
*65 nm fabrication process
*4 MB or 2 MB L2-Cache with dynamic cache sizing
*[[SpeedStep|Enhanced Intel SpeedStep (EIST)]], power states: normal (C0), AutoHALT/MWAIT (C1), Stop Grant (C2), Deep Sleep (C3), Deeper Sleep (C4)
</div>
|}

==Available Types and ThinkPads featuring them==
{| border=1 cellspacing=0 cellpadding=2
|- style="background:#ffdead;white-space:nowrap;"
! Nr. || colspan=2 | Frequency (MHz) || L2 Cache || FSB (MHz)|| VT || colspan=2 | core Voltage (V) || colspan=2 | TDP (W) || ThinkPad Models
|- style="background:#ffdead;"
! !!max. !! min. !! !! !! !! high !! low !! high freq !! low freq !!
|-
| T7700 || 2400 || 1000 || 4MB || 800 || yes || ? || ? || 35 || ? || {{R61}},{{T61}}
|-
| T7600 || 2333 || 1000 || 4MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{T60}},{{T60p}}
|-
| T7500 || 2200 || 1000 || 4MB || 800 || yes || ? || ? || 35 || ? || {{R61}},{{T61}}
|-
| T7400 || 2166 || 1000 || 4MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{T60}},{{Z61t}}
|-
| T7300 || 1400 || 1000 || 4MB || 800 || yes || ? || ? || 35 || ? || {{R61}},{{T61}}, {{X61s}}
|-
| T7200 || 2000 || 1000 || 4MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{R60}},{{T60}},{{X60}},{{Z61m}},{{Z61t}}
|-
| T7100 || 1800 || 1000 || 2MB || 800 || yes || ? || ? || 35 || ? || {{R61}},{{T61}}
|-
| T5600 || 1833 || 1000 || 2MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{R60}},{{T60}},{{X60}},{{Z61t}}
|-
| T5500 || 1666 || 1000 || 2MB || 667 || no || 1.30 || 0.95 || 34 || 20 || {{R60}},{{T60}},{{X60}},{{Z61m}},{{Z61t}}
|}

==Thermal Specifications==
The maximum temperature for safe operation is 100°C.

The catastrophic thermal protection temperature is 125°C.

==GCC Optimization Flags==
==See also==
[[Intel_Core_Solo_(Yonah)|Intel Core Solo (Yonah)]]

[[Intel Core Duo (Yonah)]]

==Links==
*[http://www.intel.com/products/processor_number/chart/core2duo.htm Intel - Processor Numbers and Features]
*[http://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors#Mobile_processors Wikipedia - Intel Core 2 mobile microprocessors]
[[Category:Components]]

Intel Core 2 Duo (Merom)

2007-08-03T21:07:48Z

BDKMPSS: /* Intel Core 2 Duo */ fixed some bugs in my English

{| 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;">
===Intel Core 2 Duo ===
The Intel 2 Core is the successor of the [[Intel Core Duo (Yonah)]] processor. Even if the name seems like a second version, the Core 2 Duo is "only" a mobile version of the desktop processor with the same name and not designed for mobile applications in the first place like its predecessor. The architecture is changed in many ways, which introduced EM64T and improved the performance by up to 25 percent. The 667 MHz FSB versions are part of the "Napa"- and the 800MHz FSB versions of the "Santa Rosa"-platform. It is part of the hardware from both the Centrino Duo and Centrino Pro brands.

===Features===
*Dual Core
*EM64T
*[http://en.wikipedia.org/wiki/Vanderpool#Intel_VT_.28IVT.29 Intel Virtualization Technology]
*667 or 800 MHz FSB
*65 nm fabrication process
*4 MB or 2 MB L2-Cache with dynamic cache sizing
*[[SpeedStep|Enhanced Intel SpeedStep (EIST)]], power states: normal (C0), AutoHALT/MWAIT (C1), Stop Grant (C2), Deep Sleep (C3), Deeper Sleep (C4)
</div>
|}

==Available Types and ThinkPads featuring them==
{| border=1 cellspacing=0 cellpadding=2
|- style="background:#ffdead;white-space:nowrap;"
! Nr. || colspan=2 | Frequency (MHz) || L2 Cache || FSB (MHz)|| VT || colspan=2 | core Voltage (V) || colspan=2 | TDP (W) || ThinkPad Models
|- style="background:#ffdead;"
! !!max. !! min. !! !! !! !! high !! low !! high freq !! low freq !!
|-
| T7700 || 2400 || 1000 || 4MB || 800 || yes || ? || ? || 35 || ? || {{R61}},{{T61}}
|-
| T7600 || 2333 || 1000 || 4MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{T60}},{{T60p}}
|-
| T7500 || 2200 || 1000 || 4MB || 800 || yes || ? || ? || 35 || ? || {{R61}},{{T61}}
|-
| T7400 || 2166 || 1000 || 4MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{T60}},{{Z61t}}
|-
| T7300 || 1400 || 1000 || 4MB || 800 || yes || ? || ? || 35 || ? || {{R61}},{{T61}}, {{X61s}}
|-
| T7200 || 2000 || 1000 || 4MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{R60}},{{T60}},{{X60}},{{Z61m}},{{Z61t}}
|-
| T7100 || 1800 || 1000 || 2MB || 800 || yes || ? || ? || 35 || ? || {{R61}},{{T61}}
|-
| T5600 || 1833 || 1000 || 2MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{R60}},{{T60}},{{X60}},{{Z61t}}
|-
| T5500 || 1666 || 1000 || 2MB || 667 || no || 1.30 || 0.95 || 34 || 20 || {{R60}},{{T60}},{{X60}},{{Z61m}},{{Z61t}}
|}

==Thermal Specifications==
The maximum temperature for safe operation is 100°C.

The catastrophic thermal protection temperature is 125°C.

==GCC Optimization Flags==
==See also==
[[Intel_Core_Solo_(Yonah)|Intel Core Solo (Yonah)]]

[[Intel Core Duo (Yonah)]]

==Links==
*[http://www.intel.com/products/processor_number/chart/core2duo.htm Intel - Processor Numbers and Features]
*[http://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors#Mobile_processors Wikipedia - Intel Core 2 mobile microprocessors]
[[Category:Components]]

Intel Core 2 Duo (Merom)

2007-08-03T21:05:43Z

BDKMPSS: expanded "The Intel 2 Core is..." a little bit, fixed °C signs

{| 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;">
===Intel Core 2 Duo ===
The Intel 2 Core is the successor of the [[Intel Core Duo (Yonah)]] processor. Even the name seems like a second version, the Core 2 Duo is "only" a mobile version of the desktop processor with the same name, not a designed for mobile applications in the first place like its predecessor. The architecture is changed in many ways, which introduced EM64T and improved the performance by up to 25 percent. The 667 MHz FSB versions are part of the "Napa"- and the 800MHz FSB versions of the "Santa Rosa"-platform. It is part of the hardware from both the Centrino Duo and Centrino Pro brands.

===Features===
*Dual Core
*EM64T
*[http://en.wikipedia.org/wiki/Vanderpool#Intel_VT_.28IVT.29 Intel Virtualization Technology]
*667 or 800 MHz FSB
*65 nm fabrication process
*4 MB or 2 MB L2-Cache with dynamic cache sizing
*[[SpeedStep|Enhanced Intel SpeedStep (EIST)]], power states: normal (C0), AutoHALT/MWAIT (C1), Stop Grant (C2), Deep Sleep (C3), Deeper Sleep (C4)
</div>
|}

==Available Types and ThinkPads featuring them==
{| border=1 cellspacing=0 cellpadding=2
|- style="background:#ffdead;white-space:nowrap;"
! Nr. || colspan=2 | Frequency (MHz) || L2 Cache || FSB (MHz)|| VT || colspan=2 | core Voltage (V) || colspan=2 | TDP (W) || ThinkPad Models
|- style="background:#ffdead;"
! !!max. !! min. !! !! !! !! high !! low !! high freq !! low freq !!
|-
| T7700 || 2400 || 1000 || 4MB || 800 || yes || ? || ? || 35 || ? || {{R61}},{{T61}}
|-
| T7600 || 2333 || 1000 || 4MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{T60}},{{T60p}}
|-
| T7500 || 2200 || 1000 || 4MB || 800 || yes || ? || ? || 35 || ? || {{R61}},{{T61}}
|-
| T7400 || 2166 || 1000 || 4MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{T60}},{{Z61t}}
|-
| T7300 || 1400 || 1000 || 4MB || 800 || yes || ? || ? || 35 || ? || {{R61}},{{T61}}, {{X61s}}
|-
| T7200 || 2000 || 1000 || 4MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{R60}},{{T60}},{{X60}},{{Z61m}},{{Z61t}}
|-
| T7100 || 1800 || 1000 || 2MB || 800 || yes || ? || ? || 35 || ? || {{R61}},{{T61}}
|-
| T5600 || 1833 || 1000 || 2MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{R60}},{{T60}},{{X60}},{{Z61t}}
|-
| T5500 || 1666 || 1000 || 2MB || 667 || no || 1.30 || 0.95 || 34 || 20 || {{R60}},{{T60}},{{X60}},{{Z61m}},{{Z61t}}
|}

==Thermal Specifications==
The maximum temperature for safe operation is 100°C.

The catastrophic thermal protection temperature is 125°C.

==GCC Optimization Flags==
==See also==
[[Intel_Core_Solo_(Yonah)|Intel Core Solo (Yonah)]]

[[Intel Core Duo (Yonah)]]

==Links==
*[http://www.intel.com/products/processor_number/chart/core2duo.htm Intel - Processor Numbers and Features]
*[http://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors#Mobile_processors Wikipedia - Intel Core 2 mobile microprocessors]
[[Category:Components]]

Problem with unauthorized MiniPCI network card

2007-08-02T11:12:26Z

BDKMPSS: /* Successful BIOS Modifications */ added another success

==Problem Description==
Although the MiniPCI slot is an industry standard and can accept any MiniPCI adapter, the IBM BIOS is set to only allow you to boot with an 'authorized' adapter installed. Attempts to install an unsupported card will result in the following message:

1802: Unauthorized network card is plugged in - Power off and remove the miniPCI network card.

This is because the card's sub-vendor PCI-ID (which can be seen using ''lspci -v'') are checked against a [[Wikipedia:Whitelist|whitelist]] in the BIOS. IBM's reasoning for this is that the combination of MiniPCI card and the integrated antenna in the ThinkPad needs to be certified by the US FCC (Federal Communications Commission).{{footnote|1}} or similar agencies in other countries.

==Affected Models==
All machines with integrated WiFi, or machines with WiFi added

==Affected Operating Systems==
All - problem is in the BIOS

==Status==
* Workarounds exist for most affected models.

==Solutions==
It may be possible to use the computer with the unauthorized card deactivated (but not removed). Press {{key|F1}} to enter the BIOS and deactivate the WLAN card, then attempt to boot with the card disabled. This does not make the wireless card work, but it may allow you to boot the computer normally.

{{NOTE|Any of the following solutions should suffice to make the wireless card useable. You only need to perform one of them.}}

* You may can modify the BIOS whitelist to include the PCI-ID of the card you wish to use. The complete instructions for this procedure are [http://www.paul.sladen.org/thinkpad-r31/wifi-card-pci-ids.html here].
{{WARN|It is dangerous to mess with your BIOS, you can easily make your machine unbootable, proceed with caution!}}

* A safer method than modifying the BIOS is modifying the PCI-ID of the wlan card. The instructions are [http://www.dagarlas.org/stuff/computing/article0001.php here]. This page is for Atheros-based cards and HP notebooks, but it applies to Thinkpads as well. It also has links on how to edit the PCI-ID on Intel Pro Wireless cards.
{{NOTE|Modifying your PCI-ID will require either a laptop without a BIOS lock or a PCI adapter for your desktop. Also, this procedure can render your card useless, but that's better than bricking your laptop.}}

* You can use the [[Problem with error 01C9 - More than one Ethernet devices | no-1802 and no-01C9 Linux Live CD]] without applying the no-01C9 patch. It is very convenient to use and based on the C code below.

* You can use the DOS [http://jcnp.pku.edu.cn/~shadow/1802/no-1802.com no-1802] utility, written by Tisheng Chen.{{footnote|2}} It will set a certain bit in the CMOS memory which disables the whitelist check, but it has been reported not to work on the latest machines, such as the T43 and X41

* You can compile and run (as root) the following C-code, which was written by Matthew Garrett. It was based on the code written by Vojtech Pavlik, which in turn was based on the assembly used in the no-1802 program. {{footnote|3}}

<code>
#include <stdio.h>
#include <sys/types.h>
#include <unistd.h>
#include <sys/stat.h>
#include <fcntl.h>

int main(void)
{
int fd;
unsigned char data;

fd = open("/dev/nvram", O_RDWR);
if (fd==-1) {
printf("Opening /dev/nvram failed\n");
return 1;
}
printf("Disabling WiFi whitelist check.\n");

/* BIG INFORMATIONAL WARNING */
/* The linux nvram driver doesn't give access to the first 14 bytes of
the CMOS. As a result, we seek to 0x5c rather than 0x6a. If you're
implementing this under another OS, then you'll have to go to whichever
address is appropriate for your access method */

lseek(fd, 0x5c, SEEK_SET);
read(fd, &data, 1);
printf("CMOS address 0x5c: %02x->", data);
data |= 0x80;
printf("%02x\n", data);
lseek(fd, 0x5c, SEEK_SET);
if (write(fd, &data, 1)<0) {
printf("Unable to write to /dev/nvram - hack failed\n");
close(fd);
return 2;
}
close(fd);
printf("Done.\n");
return 0;
}

</code>
{{NOTE|On the R32, T43, X41, X60 and probably others, the BIOS hacks and the "no-1802" utility don't work.}}

==Successful BIOS Modifications==
{{WARN|This table is meant to give users an idea of what models have been successfully modified and how. As stated before, it is dangerous to mess with your BIOS, you can easily make your machine unbootable. Please proceed with caution!}}

The following table contains information about ThinkPad models that have been successfully modified to run an unauthorized Mini PCI card. {{footnote|4}}

{| align="center" cellpadding="2" width="100%" style="border:1px; background:grey;"
! style="background:#efefef;"| Model
! style="background:#efefef;"| Type
! style="background:#efefef;"| BIOS Version
! style="background:#efefef;"| Operating System
! style="background:#efefef;"| Method
! style="background:#efefef;"| Success
|- style="background: white;"
| ThinkPad 240
| 2609-21G
| 1.18
| Damn Small Linux
| Matthew Garrett code {{footnote|3}}
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad G40
| 2388-2UU
| 1.21 (2006/2/24; 1TETA6WW)
| Windows XP Home
| no-1802 DOS 6.22 floppy
! style ="color:green;"| Yes
|- style="background: white;"
| ThinkPad R31
| 2656-6FG
| 3.11 (12-01-2004)
| Windows XP Boot Disk
| no-1802 utility
! style ="color:green;"| Yes
|- style="background: white;"
| ThinkPad R32
| 2656-EG1
| 2.16 (16-06-2006)
| DOS Boot Disk
| no-1802 utility
! style ="color:red;"| No
|- style="background: white;"
| ThinkPad R40
| 2656-69U
| ?
| Windows 2000 Pro
| no-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad R40
| 2681-F7G
| n/a
| Windows XP Pro SP2 w/ Intel 2200BG
| No-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad R40
| 2896-J3U
| 1.24 (10-18-2005)
| Fedora Core 4
| Vojtech Pavlik code
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad R40
| 2681-L7U
| 1.24 (10-18-2005)
| Windows XP Pro
| no-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad R40
| 2681-CDG
| 1.27 (10-06-2006)
| Windows XP Pro
| no-1802 LiveCD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad R40
| 2681-CFM
| 1.24 (10-17-2005)
| Gentoo & XP Pro
| no-1802 utility (boot from USB key to apply)
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad R40
| 2724
| 1.30 (10-19-2005)
| FreeBSD 6.1-p1
| code by Matthew Garrett, compiled and run on bactrack
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad R40
| 2724-3XU
| 1.33 (06-29-2006)
| Windows XP Pro
| no-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad R40
| 2682
| 1.01 (2003-01-24)
| Debian GNU/Linux etch (March 2007)
| Matthew Garret's code
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad R40
| 2722-BDG
| 1.33 (2006/6/29)
| Lunar Linux (2007/03/04)
| Matthew Garret's code
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad R50
| 1829-7RG
| 3.21 (02-06-2006)
| Windows XP Pro
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad R50p
| 1832-2AG
| 3.19 (13-10-2005)
| Ubuntu 5.10 (kernel 2.6.12-10-686)
| Vojtech Pavlik code
! style ="color:green;"| Yes
|- style="background: white; color:black;"
|ThinkPad R51
| 2887-W2C
| 1.27 (03-03-2006)
| Windows XP Pro SP2
| no-1802 utility (boot from USB key to apply)
! style ="color:green;"| Yes
|- style="background: white; color:black;"
|ThinkPad R52
| 1849-BMU
|1.27 (09-20-2006)
| Windows XP Pro SP2
| no-1802 utility (boot from external USB floppy)
! style ="color:red;"| No
|- style="background: white; color:black;"
|ThinkPad T23
| 2647-4MU
| 1.18 (08-06-2004)
| Windows XP Pro/SP2
| no-1802 utility (W98se-bootfloppy)
! style ="color:green;"| Yes
|- style="background: white; color:black;"
|ThinkPad T30
| 2366-68G
| 2.09 (08-08-2005)
| Windows XP Pro
| no-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
|ThinkPad T30
| 2366-ES1
| 2.10
| Windows XP Pro
| no-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T30
| 2366-97G
| 2.09 (08-08-2005)
| Windows XP Pro
| no-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T30
| 2366-N6G
| 2.09 (08-08-2005)
| Windows XP Pro
| no-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T30
| 2366-N6G
| 2.10 (26-06-2006)
| Windows XP Pro
| no-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T30
| 2366-81U
| 2.10 (27-06-2006)
| Windows XP Pro
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T30
| 2366-86U
| 2.10 (27-06-2006)
| Windows XP Pro SP 2
| no-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T30
| 2366-DU9
| 2.10 (27-06-2006)
| Suse Linux 10.1
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T40
| 2373-7CU
| 3.21
| Windows XP Pro
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T40
| 2373-4BG
| 3.21
| Windows XP Pro SP2
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T40
| 2373-7CU
| 3.21 (06-02-2006)
| Windows XP Pro SP2
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T40
| 2373-75U
| 3.21 (09-12-2006)
| Fedora 6 w Intel 2915ABG
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T40
| 2373-82U
| 3.18 (09-15-2005)
| Windows XP/ SUSE 10.1
| No-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T40
| 2373-8CG
| 3.05a (2004-05-14)
| Arch Linux
| No-1802 LiveCD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T40
| 2373-PU7
| 3.21 (09-12-2006)
| Windows XP Professional
| No-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T40
| 2373-42G
| 3.20 (11-05-2006)
| Windows 2000 Pro
| no-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T40
| 2374-8CG
| 3.20 (11-05-2006)
| Ubuntu 6.06 LTS w/Intel Pro Lan2200
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; coloar:black;"
| ThinkPad T40
| 2374-DG1
| 3.21 (06-02-2006)
| Ubuntu 6.10 w/Broadcom 4306
| Matthew Garrett's code
! style ="color:green;"| Yes
|- style="background: white; coloar:black;"
| ThinkPad T40p
| 2373-G1G
| 3.19 (10-13-2005)
| Debian GNU/Linux (sid)
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; coloar:black;"
| ThinkPad T40p
| 2373-G5G
| 3.21 (2006-06-02)
| Windows XP Pro SP2 / Gentoo 2007.0
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T41
| 2373-1FG
| 3.21 (2007-06-18)
| Windows XP Pro SP2
| no-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T41
| 2373-5G1
| 2004
| Fedora Core 6 w/Intel Pro 2915ABG a/b/g
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; coloar:black;"
|ThinkPad T41
| 2373-9HU
| n/a
| Ubuntu 6.10 w/Atheros 5212 a/b/g
| no-1802 Linux Live CD
! style="color:green;"| Yes
|- style="background: white; color:black;"
|ThinkPad T41
| 2373-2FG
| n/a
| Windows XP Pro SR2 w/ Intel 2200BG
| no-1802 utility
! style="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T41p
| 2373-GEG
| BIOS Build ID: 1RETDOWW(3.20)
| Gentoo / XP pro SP2
| Matthew Garrett's code {{footnote|3}}
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T41p
| 2374-GGU
| 3.21 (1RETDPWW) 6/2/2006
| Slackware / XP pro SP2
| Matthew Garrett's code
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T42
| 2373-4TG
| 3.13 (1RETDHWW) (29-10-2004)
| Windows XP Pro SP2 w/ Intel PRO 2200BG
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; coloar:black;"
| ThinkPad T42
| 2373-K2G
| 3.17 (07-27-2005)
| Windows XP Pro SP2 w/ Intel 2915ABG
| No-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T42
| 2373-M1U
| 3.13 1RETDHWW (10/29/2004)
| Fedora 7 w/ Intel PRO 2200BG
| Matthew Garrett's code
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T42
| 2378-EXU
| 3.18 (09-15-2005)
| Windows XP Pro SP2
| No-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X22
| 2662-95G
| 1.32 (2003-06-10)
| Debian GNU/Linux testing, kernel 2.6.18-3-686
| Matthew Garrett's code
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X30
| 2672-41j
| 1.08 (08-09-2005)
| Gentoo Kernel 2.6.15
| no-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X30
| 2672-4XU
| 1.09
| Win XP Pro SP2
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X30
| 2673-EU2
| 1.09
| Windows XP Pro SP2
| no-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X31
| 2672-C2G
| 3.02 (22-09-2005)
| Debian Etch (Testing), Kernel 2.6.22-rc7
| no-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X31
| 2672-PG9
| 2.04 (2003-11-10)
| Debian Etch (Testing), Kernel 2.6.21-2
| Matthew Garrett's code
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X31
| 2673-C27
| 3.02 (22-09-2005)
| Ubuntu 5.10 (kernel 2.6.12-9-386)
| Matthew Garrett code {{footnote|3}}
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X31
| 2672-1UG
| 3.02 (22-09-2005)
| FreeBSD 6-STABLE
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X31
| 2672-CEG
| 3.02 (22-09-2005)
| Debian Etch (Testing), Kernel 2.6.17-2-686
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X31
| 2672-CXU
| 2.04
| Windows XP Pro
| no-1802 DOS boot CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X31
| 2672-PBU
| 3.02
| Windows XP Pro
| no-1802 DOS boot CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X31
| 2672-C8G
| 3.02
| Debian (kernel 2.6.16.20-386)
| Matthew Garrett code {{footnote|3}}
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X31
| 2672-CEG
| 2.11 (02/13/2004)
| Debian (kernel 2.6.18-4-686, gcc 4.1.2)
| Matthew Garrett code {{footnote|3}}
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X40
| 2371-8EU
| 1.42 (2004/09/16; 1UET92WW)
| Windows XP Pro
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X41
| 1866-6SU
| ?
| Windows XP Pro
| no-1802 DOS boot CD
! style ="color:red;"| No
|- style="background: white; color:black;"
| ThinkPad X41
| 2525-A2U
| 2.06 (2006/03/14; 74ET61WW)
| Windows XP Pro
| no-1802 Linux Live CD
! style ="color:red;"| No
|- style="background: white; color:black;"
| ThinkPad X41
| 2528-ELU
| 2.06 (2006/03/14; 74ET61WW)
| Windows XP Pro / OSX 10.4.8 / Ubuntu Edgy
| no-1802 Linux Live CD
! style ="color:red;"| No
|- style="background: white; color:black;"
| ThinkPad X60s
| 1702-3JU
| ?
| Debian Testing
| Matthew Garrett's code
! style ="color:red;"| NO (bricked)
|-
|}

==External Sources==
* Additional Information about "Unauthorised" MiniPCI adapters can be found on [http://www.srcf.ucam.org/~mjg59/thinkpad/wireless.html Matthew Garrett's website].

* Thinkpad Mini PCI Wireless [http://www.srcf.ucam.org/~mjg59/thinkpad/tables.html compatibility matrix].

* Bootable "no-1802" [http://www.command-tab.com/2006/02/26/unauthorized-wireless-cards/ CD and floppy image]

{{footnotes|
#This is explained in a [http://lkml.org/lkml/2003/6/3/162 message to the LKML] and subsequently [http://lkml.org/lkml/2003/6/9/50 clarified].
#The no-1802 tool was announced and explaned in a [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2004-June/018253.html message to the Linux-Thinkpad ML].
#Vojtech Pavlik's C-code was originally posted in a [http://lkml.org/lkml/2004/6/13/69 message to the LKML]. It was based on the assembly used in the no-1802 program. Matthew Garrett [http://www.srcf.ucam.org/~mjg59/thinkpad/hacks.html rewrote] the code to provide more error checking.
#This information has been added by users. Please feel free to add systems if you have had personal success or failure.
}}

Category:X Series

2007-07-31T14:01:17Z

BDKMPSS: added link to Thinkpad series page to avoid double entry's like on the t series page

* '''ThinkPad X''': Subnotebook, very small and light, hard drive internal, no internal optical drive, small screen.

A comparison and development list of this series can be found on the overview page about all [[ThinkPad series#ThinkPad_X_series|series of ThinkPad computers]]

[[Category:Models]]

Category:T Series

2007-07-31T13:59:46Z

BDKMPSS: added link to Thinkpad series page to avoid double entry's

=ThinkPad T series=
As the successor of the [[ThinkPad_series#ThinkPad_600_series|600 series]], the T series became IBM mobile productivity line. Usually leading the ThinkPad range in technology, innovation and price, the T series was intended for the travelling businessman.

A comparison and development list of this series can be found on the overview page about all [[ThinkPad series#ThinkPad_T_series|series of ThinkPad computers]]

[[Category:Models]]

Category:R Series

2007-07-31T13:56:56Z

BDKMPSS: added link to Thinkpad series page to avoid double entrys like on the t series page

* '''ThinkPad R''': Traditionally the budget laptop line, they are 'mobile workstation' configurations to replace the discontinued [[:Category:A_Series|A series]].

A comparison and development list of this series can be found on the overview page about all [[ThinkPad series#ThinkPad_R_series|series of ThinkPad computers]]

[[Category:Models]]

ThinkPad series

2007-07-31T13:49:11Z

BDKMPSS: /* Current Series */ merge with T-Series-Model-Overview-Page, added some links

=Current Series=
==ThinkPad R series==
Dropping the [[#ThinkPad A series|A series]], IBM introduced a mainstream budget line of ThinkPads in the R series. The RXXe series lacks some of "normal" RXX series features like stereo speakers, [[IrDA]] port, touchpad, hot-swappable CD/DVD drive, firewire and some other things. It also usualy features slower CPU like Intel Celeron (but in newer models also slower Intel Core processors). ACPI functions in modern RXX-e models are just as well supported in Linux as they are for regular RXX models.

==ThinkPad T series==
As successor of the [[#ThinkPad 600 series|600 series]], the T series became IBM mobile productivity line. Usually leading the ThinkPad range in technology, innovation and price, the T series was intended for the travelling businessman - comparatively more stylish, functional, and rugged machines; and easy to disassemble for repair or upgrades. T series ThinkPads are clad in black non-slip rubber with embedded glitter. The case lid has tabs along the edge that interlocks with depressions in the lower case when closed, to reduce case flexing.

===ThinkPad T2x series===
The ThinkPad T2x models ([[:Category:T20|T20]], [[:Category:T21|T21]], [[:Category:T22|T22]], [[:Category:T23|T23]]) were [[Intel Mobile Pentium III-M]] based, sub-5 lb (2.3 kg) class machines. These machines typically had 14.1 inch XGA screens, S3 Savage graphics chips and Cirrus Logic sound chips. The T2x series introduced the [[UltraBay|UltraBay 2000]] optical drive bay and titanium-reinforced screen lids. With the [[:Category:T23|T23]], an internal WiFi antenna became available, so WiFi miniPCI cards could be used. Also the [[:Category:T23|T23]] was the first ThinkPad featuring an [[UltraBay|UltraBay Plus]] drive and [[Embedded Security Subsystem]].

===ThinkPad T3x series===
The T3x series only saw one model, the [[:Category:T30|T30]]. Powered by a [[Intel Mobile Pentium 4-M]] and a Radeon 7500 graphics chip with 16 MB of discrete video memory, the T30 was available with 14.1 inch XGA or SXGA screens. The [[:Category:T30|T30]] introduced the [[UltraNav]] touchpad and integrated Bluetooth among ThinkPads. Other features include the [[Embedded Security Subsystem]], [[UltraBay|Ultrabay Plus]] drive, integrated Wireless LAN. The shell is titanium reinforced composite. The whole package was a bit heavier and thicker than both the T2x and the T4x series.

===ThinkPad T4x series===
Includes the [[:Category:T40|T40]], [[:Category:T41|T41]], [[:Category:T42|T42]], [[:Category:T43|T43]], and associated "p" series (for "performance"; e.g., [[:Category:T43p|T43p]]). A typical T4x weighs 2.2 kg (4.9 lb), slightly less than the [[#ThinkPad 600 series|600 series]], and features an [[Intel Pentium M (Dothan)]] Processor, a 14.1 or 15 inch LCD (XGA or SXGA+), an integrated GPU ([[Intel Graphics Media Accelerator 900]]) or a discrete GPU ([[ATI Mobility Radeon 7500]], [[ATI Mobility Radeon 9000|9000]], [[ATI Mobility Radeon X300|X300]], [[ATI Mobility FireGL 9000]], FireGL 9600, [[ATI Mobility FireGL T2| FireGL T2]] and [[ATI Mobility FireGL V3200|FireGL V3200]]), and a hard drive ranging in size from 30 to 100 GB with the [[Active Protection System]] to protect the hard drive ([[:Category:T41|T41]] and later models). "p" (mobile workstation) models are also available with a 14" SXGA+ or a 15 inch UXGA FlexView display with wide viewing angle and high density IPS technology with resolutions up to 1600x1200. These 15 inch display models weigh slightly more than their lesser brethren, with optical drive and battery, at 2.7 kg (5.9 lb). Some [[:Category:T42|T42]] and [[:Category:T43|T43]] models feature a biometric security system with [[Integrated Fingerprint Reader]].

===ThinkPad T6x series===
ThinkPad [[:Category:T60|T60]] contained the [[Intel Core Duo (Yonah)]]. It was paired with either a [[ATI Mobility Radeon X1300]] or [[ATI Mobility Radeon X1400|x1400]] or with an [[ATI Mobility FireGL V5200]] for the performance model. The [[:Category:T60|T60]] was also the first of its kind to support Wireless Wide Area Network (WWAN) out of the box if the option was selected.

The ThinkPad [[:Category:T60|T60]] refresh contained the [[Intel Core 2 Duo (Merom)]]. It gave a processing speed of up to twenty five percent faster than the [[Intel Core Duo (Yonah)|Yonah]] and introduced EM64T into the mobile realm. It was paired with either a [[ATI Mobility Radeon X1300]] or [[ATI Mobility Radeon X1400|x1400]] or with an [[ATI Mobility FireGL V5250]] for the performance model.

ThinkPad [[:Category:T61|T61]] features the Santa Rosa chipset, in addition to the existing [[Intel Core 2 Duo (Merom)]]. The designers found it prudent to move from an ATI based Mobility Radeon to NVIDIA's Quadro NVS series discrete video processors. The move also marked a more aggressive shift to the wide screen format. Introductory [[:Category:T61|T61]] models only shipped with a wide screen. In addition, the designers added a Roll Cage for the screen to decrease the likelihood of damage in the event of a fall. Finally fan blades were overhauled to decrease fan noise and temperature.

==ThinkPad X series==
===ThinkPad X2x series===
[[Intel Mobile Pentium III]] with [[ATI Rage Mobility M]] ([[:Category:X20|X20]], [[:Category:X21|X21]]) or [[Intel Mobile Pentium III-M]] with [[ATI Mobility Radeon 7000]] ([[:Category:X22|X22]], [[:Category:X23|X23]], [[:Category:X24|X24]]), sub-4 lb machines. Contained processors ranging from [[Intel Mobile Pentium III|MPIII]] 500 MHz to [[Intel Mobile Pentium III-M|PIII-M]] 1+ GHz. 12.1 inch XGA screens. Used miniPCI form factor cards, which supports modem and/or ethernet. With the [[:Category:X22|X22]] and later machines, provisions for wireless networking support are built into the chassis. [[UltraBay|UltraBay 2000]] optical drive support can be fitted via the [[UltraBase X2]] portable docking station option, and extended batteries can give the series a 5 hour running time.

===ThinkPad X3x series===
[[Intel Mobile Pentium III-M]] with [[Intel Graphics Technology]] ([[:Category:X30|X30]]) or [[Intel Pentium M (Banias)]]/[[Intel Pentium M (Dothan)|(Dothan)]] with [[ATI Mobility Radeon 7000]] ([[:Category:X31|X31]], [[:Category:X32|X32]]), 12.1 inch XGA screens, [[IrDA]], FireWire, Compact Flash card slot. No built-in optical drive. Like the X2x series [[UltraBay|UltraBay Plus]] optical drive support can be fitted via the [[UltraBase X3]] portable docking station option. As the [[UltraBase X3]] can take the same battery as the notebook, the running time can be increased to amazing 10 hours.

===ThinkPad X4x Series===
A continuation of the lightweight X series. Weighing in at 1.2 kg (2.7 lb), the lightest [[:Category:X41|X41]] is 25% lighter than its predecessor, the [[:Category:X31|X31]]. Part of the X4x series, the [[:Category:X41 Tablet|X41 Tablet]] is the first Tablet PC (convertible) ThinkPad. They also get [[UltraBay|UltraBay Slim]] optical drive support via the [[UltraBase X4]] portable docking station option, but it is not compatible with the [[:Category:X41 Tablet|X41 Tablet]].

===ThinkPad X6x Series===
Includes, as of 2006, the [[:Category:X60|X60]]; the next generation of the X6x Series ThinkPads; this is the first X Series ThinkPad to feature Intel "Yonah" Dual Core Technology. A "slim", the [[:Category:X60s|X60s]], and a Tablet PC version, the [[:Category:X60 Tablet|X60 Tablet]], are also available. The fitting portable docking station option is the [[UltraBase X6]].

=Withdrawn Series=
==ThinkPad 200 series==
The 200 series ([[:Category:220|220]], [[:Category:230|230]], [[:Category:235|235]], [[:Category:240|240]] and their various sub series) was a subnotebook series. This means they were extremely small and light crossovers between notebooks and PDAs. The series ended with the [[:Category:240X|240X]]. With the changing from the numeric to the alphanumeric naming scheme in 2000, IBM stopped developing subnotebook class ThinkPads. Only in the Asia-Pacific only [[#ThinkPad S series|S series]] did in find a rather short revival.

==ThinkPad 300 series==
The 300 series ([[:Category:300|300]], [[:Category:310|310]], [[:Category:350|350]], [[:Category:360|360]], [[:Category:365E|365E]], [[:Category:380|380]], [[:Category:385ED|385ED]], [[:Category:390|390]] and their various sub series) was a long running value series starting at the [[Intel 386|Intel 386SL-33]] going all the way to the [[Intel Mobile Pentium III]]. The ThinkPad 300 was also produced for IBM by Zenith Data Systems. They were a bit large and slower than the more full featured models but offered a less expensive ThinkPad. The successor of this series is the [[#ThinkPad R series|R series]].

==ThinkPad 500 series==
The 500 series ([[:Category:500|500]], [[:Category:510Cs|510Cs]], [[:Category:560|560]], [[:Category:570|570]] and their various sub series) were the main line of the ultraportable ThinkPads. Starting with the [[IBM 486|IBM 486BL-25 Blue Lightening]] to the [[Intel Mobile Pentium III]], these machines had only a hard disk onboard. Any other drives were either external or available in the respective [[Docking Solutions]]. The successor of the 500 series is the [[#ThinkPad X series|X series]].

==ThinkPad 600 series==
The 600 series ([[:Category:600|600]], [[:Category:600D|600D]], [[:Category:600E|600E]] and [[:Category:600X|600X]]) are the direct predecessors of the [[#ThinkPad T series|T series]], and are legendary for their portability and sturdy construction. Most 600 series models packed a 13.3 inch LCD, [[Intel Mobile Pentium II]] or [[Intel Mobile Pentium III]] processor and full sized keyboard into a package weighing roughly 2.3 kg (5 lb). The [[UltraBay|UltraSlimBay]] was introduced with the 600 series. IBM was able to create this light, fully featured machine by using lightweight but strong carbon fibre composite plastics.

==ThinkPad 700 series==
The 700 series ([[:Category:700|700]], [[:Category:701C|701C]], [[:Category:730T|730T]], [[:Category:750|750]], [[:Category:755C|755C]], [[:Category:760E|760E]], [[:Category:765D|765D]], [[:Category:770|770]] and their various sub series) were the cutting edge Intel-based ThinkPads. They featured the best screens, largest hard drives and fastest processors available at the time.

==ThinkPad 800 series==
The PowerPC ThinkPad series, (800, [[:Category:820|820]], 821, 822, 823, [[:Category:850|850]], 851, [[:Category:860|860]]) were unique in that they ran on the PowerPC architecture, and not the x86 architecture. They all used the [[IBM PowerPC 603|IBM PowerPC 603e]] CPU. The 800 may have used a 603, and it is unclear if the 800 was experimental or not. All units used SCSI 2 instead of IDE. The units are believed to have all been extremely expensive, as the [[:Category:850|850]] cost upwards of $12,000 USD. The 800 series can run Windows NT 3.5 (probably 4.0 as well), OS/2, AIX 4.14, Solaris Desktop 2.5.1 PowerPC Edition and Linux.

==ThinkPad Transnote==
The IBM [[:Category:TransNote|TransNote]] was a pen based PC in a notebook. Data could not only be entered through keyboard, TrackPoint and TouchScreen, but also through a unique paper notepad with integrated digitizer which was produced in cooperation with Cross AT. This ThinkPad expanded on IBM's previous pen based notebooks ([[:Category:360P|360P]](E), [[:Category:730T|730T]](E), and 755(P).

==ThinkPad A series==
The A series was developed as an allround productivity machine, equipped with hardware powerful enough to make it a desktop replacement. Hence it was the biggest and heaviest ThinkPad series at its time, but also had features not even found in a [[#ThinkPad T series|T series]] of the same age. The A series was dropped in favour of the [[#ThinkPad G series|G series]] and [[#ThinkPad R series|R series]].

==ThinkPad G series==
The G series consists of only two models so far, the [[:Category:G40|G40]] and [[:Category:G41|G41]]. Being large and heavy machines, equipped with powerful desktop processors, this line of ThinkPads is consequently specialised in serving as a desktop replacement.

==ThinkPad i series==
The i series introduced the [[ThinkLight]] and were also the first notebooks equipped with Wireless LAN.

==ThinkPad S series==
A subnotebook series consisting of only two models: the [[:Category:S30|S30]] and [[:Category:S31|S31]].
[[Category:Models]]

==ThinkPad Z series==
The widescreen ThinkPad build to offer the ultimate multimedia experience. Internal similar to the [[#ThinkPad T series|T series]], but they have a widescreen and are available with a Titanium Special Edition Cover on selected models. This was the first ThinkPad series completely developed by Lenovo. This series was discontinued as the [[#ThinkPad T series|T series]] are available with widescreen displays.

===ThinkPad Z60x Series===
The first widescreen ThinkPads, internal similar to the T4x series, but they are available with 14" ([[:Category:Z60t|Z60t]]) or 15.4" ([[:Category:Z60m|Z60m]]) widescreens (some with optional MaxBright-technology). Travel weight starting at 4.1 lb and they are less than 1.1" thin. They are the first ThinkPads completely developed by Lenovo.

===ThinkPad Z61x Series===
Second generation Z series, upgraded to the internal technology level of the T60 series ThinkPads.