ThinkWiki - User contributions [en]

Tp smapi

2008-06-17T03:03:53Z

Paisa: status for R61i

{| 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. It 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.

For older ThinkPad models, see also [[tpctl]].

{{WARN|This driver uses undocumented features and direct hardware access. It thus cannot be guaranteed to work and could conceivably damage your computer (though so far no incidents have been reported).}}
|}

===Features===
*Battery charge/discharge control
*Battery status information
*Modified [[HDAPS]] driver with improved stability, model support and functionality

===Project Homepage / Availability===
* Project page: http://tpctl.sourceforge.net/
* You need to [http://sourceforge.net/project/showfiles.php?group_id=1212&package_id=171579 download] only the <tt>tp_smapi</tt> 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.34.tgz}}
:{{cmdroot|cd tp_smapi-0.34}}

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

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

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

If you use a stock Debian kernel, you can install the tp_smapi modules with:
* {{cmdroot|apt-get install tp-smapi-modules-`uname -r`}}

====Installation on Ubuntu Hardy====
Ubuntu ships tp_smapi in their linux-ubuntu-modules Package since 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>. You should load <tt>hdaps_ec</tt>, not <tt>hdaps</tt>.

====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 source -> /usr/src/linux-source-2.6.20</nowiki></pre>
Create the link if the line above is not existent:
<pre><nowiki>root@localhost:~#ln -s /usr/src/linux-source-2.6.20 /lib/modules/2.6.20-16-generic/source</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 ad 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]].}}

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

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

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.

===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}} || {{Cunk}} || {{Cunk}} || || || ||
|-
! {{A30}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || || ||
|-
! colspan=12 style="text-align:center;background:#efefef;" |
=====G series=====
|-
{{tp_smapi/model_status_table_header}}
|-
! {{G41}}
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || || || ||
|-
! colspan=12 style="text-align:center;background:#efefef;" |
=====R series=====
|-
{{tp_smapi/model_status_table_header}}
|-
! {{R31}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cunk}} || || || || No SMAPI BIOS
|-
! {{R40}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || || || ||
|-
! {{R50}}
| {{Cunk}} || {{Cno}} || {{Cunk}} || {{Cunk}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || || ||
|-
! {{R50e}} 1834-JAG
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || || ||
|-
! {{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}}
| {{Cunk}} || {{Cunk}} || {{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 ||
|-

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

=====T series=====
|-
{{tp_smapi/model_status_table_header}}
|-
! {{T20}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cunk}} || || || || Has SMAPI BIOS but no function is supported. EC LPC3 protocol fails.
|-
! {{T22}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cunk}} || || || || Has SMAPI BIOS but no function is supported. EC LPC3 protocol fails.
|-
! {{T23}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || || ||
|-
! {{T30}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || || ||
|-
! {{T40}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || || ||
|-
! {{T40p}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || || ||
|-
! {{T41}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || || ||
|-
! {{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 || ||
|-
! {{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]
|-
! colspan=12 style="text-align:center;background:#efefef;" |

=====X series=====
|-
{{tp_smapi/model_status_table_header}}
|-
! {{X20}} 2662-31G
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cunk}} || || || ||
|-
! {{X24}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || || ||
|-
! {{X30}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || 0.34 || 1.09 || ||
|-
! {{X31}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || || ||
|-
! {{X32}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || || ||
|-
! {{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}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{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)
|-
! {{X60s}} 1704-5UG
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cno|text=}} 3 || 0.34 || 7BETD2WW 2.13 || 7BHT40WW 1.13 ||
|-
! {{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
|-
! {{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]
|-
! {{X61_Tablet}}
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} 6 || 0.32 || || ||
|-
! {{X61}} 7675-4KU
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} 6 || 0.34 || 7NET30WW (1.11 ) || 7MHT24WW-1.02 ||
|-
! {{X61}} 7675-CTO
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cyes}} || {{Cno|text=}} 6 || 0.35-test1 || || ||
|-
! {{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}} || || || ||
|}
</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 tp_smapi's hdaps driver 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.

<tt>invert</tt> is an integer between 0 and 7, whose meaning is as follows. 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.

Pre-Installation steps

2008-06-06T03:31:29Z

Paisa: Shrinking a Vista partition

==Rescue and Recovery Media==
Most modern ThinkPads ship with Windows preinstalled on the hard disk only -- no recovery disks are included. Instead, Lenovo ThinkVantage software allows you to create a Rescue and Recovery CD-ROM and a Product Recovery DVD-ROM. These will allow you to restore the hard disk to its exact factory installed state. They can also perform other useful system recovery functions.

Even if you have no intention of using Windows, your first action should be to create these disks. Later, you or someone else may want to use Windows again. The recovery disks make it very simple to reinstall Windows, perfectly configured for your ThinkPad. Here's how:

1. Turn on the system and boot Windows.

2. Start the recovery media creation program with ''Start | All Programs | ThinkVantage | Create Recovery Media''.

3. Choose to create ''Recovery Disks''. The other alternative, ''Rescue Media'', creates only the first of the ''Recovery Disks''.

4. Insert a blank CD-ROM as instructed. This will become a bootable Rescue and Recovery disk.

5. Insert one DVD-ROM (or a series of seven CD-ROMs) as instructed. This will become the Product Recovery disk that contains the bulk of the data on the hard disk.

6. Save the disks in a safe place.

When you want to erase everything on the hard disk and restore the system to its factory preinstalled state, boot from the Rescue and Recovery disk, and run ''Restore Your System''.

If you forget to make recovery disks, Lenovo [[Ordering_Recovery_CDs|offers]] shipment of a pack of rescue disks if you call the support hotline. Also, recovery CDs for older ThinkPads are [http://stores.ebay.com/Recovery-CDs-Disks sold on eBay] (you must supply your own Windows disk). However, the only way to get recovery disks that match your system exactly is to make them now.

The copy of Windows that came with your ThinkPad cannot be legally transferred to any other system. Leave the Windows license sticker intact. The resale value of your ThinkPad will be lower without it.

==Resizing your Windows Partition==
Modern ThinkPads ship with a FAT32 recovery partition of about 5GB, and a Windows NTFS partition that consumes the rest of the hard disk. If you want to keep Windows on your system, you will need to shrink the Windows disk partition to make room for Linux. The easy way is to use commercial software like Partition Magic (US$70) or [http://www.partition-manager.com Partition Manager] (US$50).

If you do not want to pay for Partition Magic or Partition Manager, you can use [http://mlf.linux.rulez.org/mlf/ezaz/ntfsresize.html ntfsresize]. I recommend booting {{Kanotix}} or {{Knoppix}}, getting it online and using the latest version to be found at the ntfsresize link because the live CD distributions tend to come with slightly out-dated versions. Be sure not to forget to resize your Windows partition (e.g. with cfdisk) AFTER having resized ntfs and TAKE CARE not to make the partition smaller than you made the ntfs. If you like it safe and smooth you can also take a look at the program "qtparted" which reportedly takes care of ntfsresize and partition table changing in one go and allows you to adjust partition sizes in a GUI. But I have not tested this software personally.

If you want to retain Rescue and Recovery functionality, do not delete the 5GB recovery partition. You can either move it or leave it in place at the end of the hard disk. A procedure for moving it appears in the next section.

'''Please be careful before taking the following steps. I suggest that you should create rescue and product recovery CDs (6 CDS will be required) before going for the following so that if anything goes wrong you can go back to the factory setting using those CDs.'''

==Moving the Recovery partition using a Linux rescue system==
On newer models (e.g., the T43) the preinstalled HDD has two partitions; the first one containing the OS and second one having the rescue files used to boot the machine when {{ibmkey|Access IBM|#495988}} button is pressed before Windows XP takes control of the laptop. One can use his Linux distributions boot CD (usually the first CD) to boot into rescue mode and shift the rescue partition from the end of the HDD to somewhere in between leaving required space for Windows. This can be done in following steps:

===Creating a temporary rescue partition===
* Run {{cmdroot|fdisk /dev/sda}}.
* Delete the 1st partition ({{path|/dev/sda1}}).
* Create a partition {{path|/dev/sda3}} immediately before the rescue partition ({{path|/dev/sda2}}) with exactly the same number of cylinders as the rescue partition.
* Save the partition table and quit fdisk. Reboot.
{{HINT|To be on the safe side, reboot the machine every time the partition table is modified and saved using fdisk from linux rescue mode.}}
* rawcopy the contents of {{path|/dev/sda2}} to {{path|/dev/sda3}} with
:{{cmdroot|1=dd if=/dev/sda2 of=/dev/sda3}}

===Creating the rescue partition in its final position===
* Run {{cmdroot|fdisk /dev/sda}}.
* Delete the rescue partition {{path|/dev/sda2}} (we just backed it up to {{path|/dev/sda3}}).
* Create a partition {{path|/dev/sda2}} immediately after the space you want to leave for Windows. Note that this new partition again should have exactly the same number of cylinders as the rescue partition (now {{path|/dev/sda3}}).
* Save the partition table and quit fdisk. Reboot.
* rawcopy the contents of {{path|/dev/sda3}} to the newly created {{path|/dev/sda2}}:
:{{cmdroot|1=dd if=/dev/sda3 of=/dev/sda2}}
* Run {{cmdroot|fdisk /dev/sda}}.
* Delete the temporary rescue partition {{path|/dev/sda3}} (we just copied it to {{path|/dev/sda2}})
* Save the partition table and quit fdisk.
* Reboot the machine and press {{ibmkey|Access IBM|#495988}} Button to restore the Windows XP from the rescue partition. Windows XP will occupy only the space available before the new rescue partition.

Once Windows XP is recovered follow the standard mechanism for installing Linux in the available free space at the end of the HDD. If you have created Rescue and Product Recovery CDs, then the Rescue Partition also can be deleted at this stage to make more room for your Linux installation.

= Alternative Method: Dual Booting and retaining ThinkVantage Utility =

Note: T60 2913 with 60 GB drive

The key here is to find a bootable CD version of Linux that has the PartEd package on it (preferrably with qtparted also). I used SystemRescueCd (http://www.sysresccd.org/Main_Page). I've read people say to defragment Windows, but according to the PartEd website, the PartEd resize command (http://www.gnu.org/software/parted/manual/parted.html#resize) will take care of all that. Now boot with the SystemRescueCd and when you get the prompt, press F2. This will list available images. I used fb1024, because I wanted to use qtparted (graphical, fb1024 is framebuffer at 1024x768 vs fb800 is framebuffer at 800x600, etc), not parted (commandline).

What I saw was a 3 partition device sda. Only touch the NTFS partition (sda1 on mine, should be on yours if it is factory settings). You do not want to move the VFAT at the end of the device nor touch that little section (sda-1) at the beginning. I resized sda1 (NTFS) down to 20 GB, what you should see is the the New Size + the Free Space After = Old Size of sda1. Click the commit under the file menu to write the changes. That's it.

I then rebooted with Fedora Core 5 disk 1 and used Anaconda and its utilities to partition the free space to be a 20 GB mount point "/", a 512 MB swap, and a 10 GB vfat, these could have been done using qtparted, or pretty much any distribution's install. The swap and VFAT were shown inside a logical partition. I set up GRUB in the MBR and clicked the GRUB advanced setup checkbox. This allowed me to add entries, in addition to Linux, for GRUB. I added the NTFS (Windows) partition and the VFAT (ThinkVantage partition, not the 10 GB I created, because that would be silly).

The results are: On boot, the post screen tells you to press the ThinkVantage button, and... It does nothing, but once GRUB starts, press the key GRUB tells you to which shows the boot list, and there you have Linux, Windows, and ThinkVantage. I tried it and I can boot into all 3. When you first boot into Windows, you may get a chkdsk (I did), but it should be fine.

A word of warning. Be careful, I've heard some people say GRUB in the MBR while dual booting WinXP can result in false positives from virus software, but I didn't have that issue. Also, be very careful about the resize of the NTFS partition with qtparted. Any change in the placement of the start of the pre-existing partitions, and all bets are off. I'm just saying this because I don't know what might happen if Windows isn't where it wants to be. Also I think the placement of the ThinkVantage utility on the disk is very important from my reading. However, since pressing the ThinkVantage at POST doesn't do anything, I may have screwed that up, but with GRUB pointing at that VFAT, I can still get to the ThinkVantage utilities, so I'm happy.

=Resizing a Windows Vista partition=

My ThinkPad R61 came with an 8GB Rescue & Recovery (version 4) partition at the beginning of the 160GB disk, and Vista on the rest. The Vista partition could not be resized beyond 70GB, either with its built-in resizing program or with a live CD -- there were some unmovable MFT blocks in the middle of the partition, even after using several defragmentation programs. Reinstalling from the Rescue & Recovery partition also didn't help; by the time the installation was over (7 reboots!), the MFT blocks were there again.

===Solution 1===
To get it working, I had to start the recovery process (this also gave me the chance to get rid of AOL, Norton, and various other useless programs), and then catch it on its first reboot and resize, after the partition is made but before it's filled with files. I used [http://gparted.sourceforge.net/livecd.php GParted live CD]. First I tried to resize the partition with ntfsresize/fdisk, because I had read that GParted had some trouble with resizing Vista partitions -- it seemed to work at first, but when the next step of the installation came, it just showed a blank desktop for a while and rebooted.

Although GParted was much slower (about 1½ hours to do the resizing), it was more successful. After the next reboot, Vista ran chkdsk, and then continued with the installation, on a smaller (32GB) partition.

'''Note: You should probably make a recovery disk (from Windows) before doing this, in case something unexpected happens during this process.'''

'''Update:''' ''hircus, September 17th 2007''
Newer versions of ''ntfsresize'' seem to be able to resize Vista's NTFS partition without problems. On a Thinkpad T61, hard drive freshly restored to initial state, I let Windows install all its updates, then tried using Disk Management's Shrink Partition. It would only release about 40GB, even after turning swap off.

Booted openSUSE 10.3 beta 3's GNOME install CD, told it to shrink the Windows partition and the whole operation took only several minutes. Better than Microsoft's own (free) tools!

===Solution 2===

Vista's tool (Computer -> Manage -> Disk Management) doesn't seem to move data blocks around. If you happens to have some data sitting toward the end of the partition, it only let you shrink down to where that data sits.

[http://www.howtogeek.com/howto/windows-vista/working-around-windows-vistas-shrink-volume-inadequacy-problems/ | This guide]
suggests getting rid off as many system files as possible (disable pagefile, system snapshot, hibernation, kernel debug info dump, ...) then defragments the partition. However, Vista's defrag program seems to just group data blocks together, but doesn't move
them to the beginning of the partition.
Diskeeper Home Edition (bundled with my Lenovo) moves data blocks up to the beginning, but cannot move system blocks.
Depending on your luck (how your system blocks scatter on your partition) you might be able to shrink Vista partition by a few Gigs.
I could shrinked mine 112 Gb partition by 11 Gb.

[http://www.raxco.com/products/downloadit/ | PerfectDisk] (30 days free trial) can defrags system blocks and relocate them up toward the beginning of
the partition. After doing that, Vista offers to shrink my partition by 47 Gb. My partition was only 35 Gb out of 112 Gb full,
so I was surprised that I couldn't shrink more. Anyway, 47Gb wasn't bad. I hit "OK" and got ... "Access Denied" :-P.
I lowered this number to 40 Gb and Vista shrank the partition just fine.

[[Category:Windows]]