ThinkWiki - User contributions [en]

Installing Ubuntu 10.04 (Lucid Lynx) on a ThinkPad X61 Tablet

2010-07-12T08:07:09Z

Tripwired: /* automatic rotating of display in tablet mode */

This is a notes page for now. It will improve with time I have blatantly copied the 9.04 page as a template.

= Introduction =

This page covers the additional hardware setup required after installing Ubuntu 10.04 Jaunty to make the Thinkpad X61 Tablet Fully Functional.

=== What Works ===
==== Tested ====
Audio Buttons,
Brightness Fn Buttons,
Radio Fn Button,
Suspend Fn Button,
Tablet L/R/U/D Buttons,
Tablet Enter Button,
Tablet Esc Button,
NumberLock Fn Button,
Tablet Pen,
Wireless Radio,

==== Assumed Working ====
Forward / Back Buttons,
Power Fn Button,
Lock Fn Button,
Hibernate Fn Button,
Media Fn Buttons
Bluetooth Radio,

=== What Almost Works ===
Tablet Toolbox Button - causes lock or suspend,
Tablet Touch – Requires Calibration.

=== What Does Not Work ===
Tablet Control-Alt-Delete Button,
Tablet Rotate Button,
Middle Mouse Button,
ThinkVantage Button,
Magnify Fn Button,
Fingerprint Reader,
Automatic Screen Rotation,
ThinkVantage ActiveProtection,

= Fixing Touch =
Works out of the box, just needs some calibration.

== xsetwacom ==

It took me some time to find this one. So, i'll post it here so you won't have to spend time finding it. These numbers calibrate touch for my X61. I hope it will be the same for other X61's.

#!/bin/sh
xsetwacom set "Serial Wacom Tablet touch" topy "85"
xsetwacom set "Serial Wacom Tablet touch" topx "51"
xsetwacom set "Serial Wacom Tablet touch" bottomx "933"
xsetwacom set "Serial Wacom Tablet touch" bottomy "957"

The numbers where acquired using xinput_calibrator.

== xinput_calibrator ==

http://www.freedesktop.org/wiki/Software/xinput_calibrator

Using this tool you can find the numbers to calibrate your touchscreen.
It's a pity it is still not in the repositories (as of 24/06/2010)

Install as per instructions on the freedesktop site.

Then run:

xinput_calibrator_x11 --device "Serial Wacom Tablet touch"

'''The tool does not actually calibrate the tablet.''' It merely shows you the numbers needed for calibration. Work in progress, i guess.

== Wacomcpl (Will not work because HAL is missing) ==

(I think, it isn't working, because we haven't got wacomcpl in 10.04.)

Wacomcpl is no longer available in 10.04. The new package is xserver-xorg-input-wacom. How to calibrate the screen is being looked into. The xsetwacom command is still intact to set the calibrations though.

The Wacom Tablet in the X61t is a serial Wacom tablet. It can be configured by using wacomcpl. Wacomcpl is part of the wacom-tools package and can be retrieved in apt:

sudo apt-get install wacom-tools

After this wacomcpl can be run by typing:

wacomcpl

in Terminal.

=== Helping wacomcpl ===
Unfortunately HAL assigns names to wacom devices in a way that the recent wacomcpl from jaunty cant find them, to help wacomcpl to find them:

Open a terminal and type:

sudo gedit /etc/init.d/wacomtohal

and paste this code in:

#! /bin/sh
## find any wacom devices
for udi in `hal-find-by-property --key input.x11_driver --string wacom`
do
type=`hal-get-property --udi $udi --key input.x11_options.Type`
## rewrite the names that the Xserver will use
hal-set-property --udi $udi --key info.product --string $type
done

then run :

sudo chmod +x /etc/init.d/wacomtohal
sudo update-rc.d wacomtohal defaults 27

now reboot and launch wacomcpl

=== Making Wacomcpl Settings Restore on Reboot ===
If you lose your calibration after reboot:

In terminal:

sudo gedit ~/.xinitrc

Find the line that says:

. /etc/X11/xinit/xinitrc

and change it to

#. /etc/X11/xinit/xinitrc

Save and exit.

Go to System>Preferences>Startup Applications and create a new entry named whatever you want.

The command should be:

sh /home/yourusername/.xinitrc

Your wacomcpl settings will now restore on reboot

= Fixing the Tablet Toolbox Button =
This key needs to be set to a keycode. Pick any empty one (241 is usually empty)

sudo setkeycodes 68 241

Now you can bind this key to any command.

= Setup the Tablet Control-Alt-Delete Button =
This key needs to be set to a keycode. Pick any empty one (242 is usually empty)

sudo setkeycodes 67 242

Now you can bind this key to any command.

= Setup the Tablet Rotate Button =
This key needs to be set to a keycode. Pick any empty one (240 is usually empty)

sudo setkeycodes 6c 240

Now you can bind this key to any command. (It should be possible to write a script to interact with the autorotate given on this page)

= Setup the Middle Button Scrolling =

== The easy apt-get way ==

sudo apt-get install gpointing-device-settings

== The hard way ==

Which probably will not work because it depends op HAL.

Open a terminal and run each of the following for vertical scrolling:

xinput set-prop 'TPPS/2 IBM TrackPoint' "Evdev Wheel Emulation" 1
xinput set-prop 'TPPS/2 IBM TrackPoint' "Evdev Wheel Emulation Button" 2
xinput set-prop 'TPPS/2 IBM TrackPoint' "Evdev Wheel Emulation Timeout" 200

Add the following if you want horizontal scrolling:

xinput set-prop 'TPPS/2 IBM TrackPoint' "Evdev Wheel Emulation Axes" 6 7 4 5

If you do not want to run these commands every time you restart your computer, copy them to a script file.

In Ubuntu, create a new file in your Home directory called "Mouse_Wheel.sh". Using gedit, paste the commands into the file and save.

Open the terminal and type:
chmod +x Mouse_Wheel.sh
Go to System > Preferences > Startup Applications. Click on "Add", in the Name box type "Mouse Wheel" and in the Command box type "./Mouse_Wheel.sh".

In Kubuntu, place the script file in ~/.kde/Autostart.

HAL has been deprecated so the following might still work but is not suggested:
Create a new file called /etc/hal/fdi/policy/mouse-wheel.fdi typing:

sudo gedit /etc/hal/fdi/policy/mouse-wheel.fdi

And fill it with this code:

<?xml version="1.0" encoding="UTF-8"?>

<match key="info.product" string="TPPS/2 IBM TrackPoint">
<merge key="input.x11_options.EmulateWheel" type="string">true</merge>
<merge key="input.x11_options.EmulateWheelButton" type="string">2</merge>
<merge key="input.x11_options.XAxisMapping" type="string">6 7</merge>
<merge key="input.x11_options.YAxisMapping" type="string">4 5</merge>
<merge key="input.x11_options.ZAxsisMapping" type="string">4 5</merge>
<merge key="input.x11_options.Emulate3Buttons" type="string">true</merge>
</match>

Reboot

= Setup ThinkVantage Button =
The ThinkVantage button does not work only in that it is not bound to anything. To bind it go to System>Preferences>Keyboard Shortcuts and set it to perform any command.

= Setup Magnify Fn Button =
No Solution Yet.

= Setup Fingerprint Reader =

The Thinkfinger driver works fine on the X61. The following is the paraphrased commands from the installing thinkfinger page that are relevant to the X61 and Ubuntu 9.04.

In terminal, add a key:

sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com F2A12FABE936A7BBDC4EA33351DB180D1323E149

Add the PPA repositories to your sources.list (/etc/apt/sources.list):

deb http://ppa.launchpad.net/jon-oberheide/ppa/ubuntu jaunty main
deb-src http://ppa.launchpad.net/jon-oberheide/ppa/ubuntu jaunty main

Update installer:

sudo apt-get update

And install:

sudo apt-get install thinkfinger-tools libpam-thinkfinger

Now the driver is installed and should be working. You can try it (as root) with

sudo tf-tool --acquire

and

sudo tf-tool --verify

This will ask you to swipe your finger three times, save the fingerprint to /tmp/test.bir and then verify your fingerprint with the bir-file.

Setup Pam:

sudo /usr/lib/pam-thinkfinger/pam-thinkfinger-enable

Add user:

tf-tool --acquire $USERNAME

Optional: Change the login screen to allow keyboard-less login:

Go to: System>Administration>Login Window

Click on the 'Local' tab.

Set the drop-down boxes to: 'Themed with face browser' and 'Selected Only' and choose 'Human List' from the list of logins.

Note: it may take some time for the reader to startup, give it 5 seconds before use and before pressing enter to initiate login.

= Setup Automatic Screen Rotation =

== Automatic Switching from Laptop to Tablet mode ==
The following was inspired by [[Installing Ubuntu 8.10 (Intrepid Ibex) on an X61 Tablet]], with some minor additions:

* put the following in '''/etc/acpi/events/lenovo-rotate-normal'''

# /etc/acpi/events/lenovo-rotate-normal
# This is called when the user rotates the screen to laptop mode

event=ibm/hotkey HKEY 00000080 0000500a
action=/etc/acpi/thinkpad-rotatescreen.sh right

* put the following in '''/etc/acpi/events/lenovo-rotate-tablet'''

# /etc/acpi/events/lenovo-rotate-tablet
# This is called when the user rotates the screen to tablet mode

event=ibm/hotkey HKEY 00000080 00005009
action=/etc/acpi/thinkpad-rotatescreen.sh normal

* put the following in '''/etc/acpi/thinkpad-rotatescreen.sh''' and make it executable

#!/bin/sh
#
# This script rotates the display in TabletPCs when screen is changed from
# laptop to tablet mode, or when rotation button is pressed

test -f /usr/share/acpi-support/key-constants || exit 0

. /usr/share/acpi-support/power-funcs

# i'm not trusting this ...
#if [ -f /var/lib/acpi-support/screen-rotation ] ; then
# ROTATION=`cat /var/lib/acpi-support/screen-rotation`
#fi

# ... and thus calling this with a parameter
ROTATION="$1" # this should be called "ROTATION_FROM"

case "$ROTATION" in
right)
NEW_ROTATION="normal"
NEW_WACOM="none"
;;
*)
NEW_ROTATION="right"
NEW_WACOM="cw"
;;
esac

for x in /tmp/.X11-unix/*; do
displaynum=`echo $x | sed s#/tmp/.X11-unix/X##`
getXconsole;
if [ x"$XAUTHORITY" != x"" ]; then
export DISPLAY=":$displaynum"
/usr/bin/xrandr -o $NEW_ROTATION && echo $NEW_ROTATION > /var/lib/acpi-support/screen-rotation

# rotate the stylus
for type in "Serial Wacom Tablet eraser" "Serial Wacom Tablet touch" "Serial Wacom Tablet" ; do
/usr/bin/xsetwacom set "$type" rotate $NEW_WACOM
done

# rotate the arrow keys
case "$NEW_ROTATION" in
right)
xmodmap - <<END
keycode 114 = Up NoSymbol Up NoSymbol Up
keycode 111 = Left NoSymbol Left NoSymbol Left
keycode 116 = Right NoSymbol Right NoSymbol Right
keycode 113 = Down NoSymbol Down NoSymbol Down
END
;;
*)
xmodmap - <<END
keycode 111 = Up NoSymbol Up NoSymbol Up
keycode 113 = Left NoSymbol Left NoSymbol Left
keycode 114 = Right NoSymbol Right NoSymbol Right
keycode 116 = Down NoSymbol Down NoSymbol Down
END
;;
esac
fi
done

Note: check the output of
xsetwacom list dev
to identify the devices to put in the line
for type in "Serial Wacom Tablet eraser" "Serial Wacom Tablet touch" "Serial Wacom Tablet" ; do
My system has a touch and a cursor device.

== Automatic rotating of display in Tablet mode ==

Install [http://www.krizka.net/projects/autorotate/ Karol Krizka's AutoRotate daemon].

sudo add-apt-repository ppa:kkrizka/thinkpad-x61t
sudo apt-get update
sudo apt-get install python-glib python-dbus python-xrandr autorotate

Set up the daemon to start with Gnome
sudo gedit /etc/gdm/Init/Default
Add the following line before the last "exit"
auto-rotate.py &

Save your work before restarting Gnome
sudo /etc/init.d/gdm restart

You're all set. Note that there is also a manual-rotate.py script that comes with AutoRotate that can be bound to the special function Rotate key. See the author's site above for help with setting the keyboard shortcuts.

= Setup ThinkVantage ActiveProtection =

sudo cp /etc/modules /etc/modules_backup
sudo aptitude install tp-smapi-source
sudo module-assistant prepare tp-smapi
sudo module-assistant auto-install tp-smapi
sudo modprobe tp-smapi
sudo aptitude install hdapsd
echo 'tp-smapi' | sudo tee -a /etc/modules

You can set the activeprotection sensivity:

cd /etc/default/
gedit hdapsd

# sensitivity
SENSITIVITY=25

Now you can try, if the modules are loaded yet. Do so with

lsmod | grep hdaps

if not perform:

sudo modprobe -a thinkpad_ec tp_smapi hdaps

If the installation of hdapsd succeeded, you can test it by typing this into your terminal:

sudo hdapsd -d sda -s 15 -a -v -y

If you suddenly move your laptop the output will change! (stop it with pressing Ctr + C)

= Useful Task: Disable Bluetooth on Startup =
These instructions will disable the bluetooth radio being activated during the boot. The radio can then be activated at the users discretion using Fn F5 (Radio Fn Button).

edit /etc/rc.local and add:

chmod 666 /proc/acpi/ibm/bluetooth
echo "disable" > /proc/acpi/ibm/bluetooth

before the 'exit 0' line

*note chmod 666 makes this file editable by everyone, this may compromise security, try different settings to find the one that suits your needs (655 may work)

*note proc is depreciated and may not work in future releases

= Useful Task: Enable Laptop Mode =
Laptop mode is a power saving tool that allows the hard drive to spin down to conserve battery power. This is disabled by default as it has been known to cause problems on some computers, but it appears to work on the X61t.

*Warning: Laptop mode stores data in ram teporarily until it needs to write to disk. Power Loss in laptop mode could lead to significant data loss.

*Warning: Excessive spin-up spin-down cycles will wear out your hard drive much more quickly than normal use. Be careful when configuring laptop mode settings.

*Warning: Do Not Use Laptop Mode if you have a SSD. It is for platter drives only.

Edit /etc/default/acpi-support

sudo gedit /etc/default/acpi-support

Set: "ENABLE_LAPTOP_MODE=true"

Configure Laptop Mode

sudo gedit /etc/laptop-mode/laptop-mode.conf

= Optional Task: Adjusting Trackpoint Settings =
If you find that your trackpoint pointer is too slow, use [http://sourceforge.net/projects/tpctl/ control-trackpoint] to adjust your settings.

To install, install sysfsutils first, as per [http://tpctl.sourceforge.net/configure-trackpoint.html tpctl's documentaton]

sudo apt-get install sysfsutils

then install the .deb from sourceforge (the graphical installer worked for me). Once installed, run:

sudo configure-trackpoint

= Sources =
The above is a compilation of my notes from when I installed Jaunty on my X61t. The code and many of the instructions come from various pages and sources around the Internet. I will attempt to document them when time permits. If you see anything that should be added or wish to cite a source I missed, please edit the page.

[[Category:X61 Tablet]]

Talk:HDAPS

2010-07-12T02:37:36Z

Tripwired: /* Question regarding the example udev rule ? */

== Smackpad and Compiz ==

There are a few references to scripts that will switch the workspace when you tap the laptop on the side. I googled for a while and all I could find was pretty old stuff.

A few of the links I found are:

[http://wiki.compiz.org/Plugins/Smackpad Compiz Smackpad Plugin] This one looks very interesting but how do you install it?

[http://www.eugen-feller.de/?p=12 Compiz Smackpad] I could not clone the software.

[http://blog.micampe.it/articles/2006/06/04/here-comes-the-smackpad Here comes the smackpad] No luck here either.

Etc...

So, has anyone got this working recently? How?

Thanks! --[[User:Lunatico|Lunatico]] 18:15, 21 April 2010 (UTC)

== Careful with Gnome HDAPS applet ==

This applet polls /sys/block/sda/device/unload_heads and loads the corresponding icon from disk '''every 10th of a second'''. I'd like to talk to the upstream developer and fix that, but I wouldn't recommend its usage meanwhile. I guess we should warn users in the wiki page? --[[User:Berto|Berto]] 14:40, 3 April 2010 (UTC)

--[[User:Lunatico|Lunatico]] 17:45, 21 April 2010 (UTC) Can you elaborate more on this? I'm using the gnome applet and haven't had any perceivable issues.

--[[User:peepingtom|peepingtom]] Try running powertop to observe this. I just turned off the GUI monitoring stuff, you can hear the head park anyway

== Question regarding the example udev rule ? ==
The example udev rule is as follows.
* KERNEL=="event[0-9]*", ATTRS{phys}=="hdaps/input1", ATTRS{modalias}=="input:b0019v1014p5054e4801-*", SYMLINK+="input/hdaps/accelerometer-event"

Where is the '''b0019v1014p5054e4801''' being taken from?

It is from "udevinfo --attribute-walk --name /dev/input/event9" (only with the tp_smapi module)

{{HINT|Lucid does not have udevinfo. Instead, use:
udevadm info
}}

== Where can one find the recent hdapsd version mentioned in the article ? ==
The article mentions "New interface (requires hdapsd dated 2008-10-04 or newer)" without giving any clue about where one can find such a version, I looked in repositories, google and elsewhere in this very site and found an outdated http://www.dresco.co.uk/hdaps/ , as a newcomer here, it eludes me completely. [[User:Bugmenot1|Bugmenot1]] 21:38, 28 November 2008 (CET)

:I had the same problem, I think I found it via [[How_to_protect_the_harddisk_through_APS#Manual_compilation_from_source]], it links to a mailing list post at [http://article.gmane.org/gmane.linux.drivers.hdaps.devel/1040] which has an attached source file at [http://cache.gmane.org//gmane/linux/drivers/hdaps/devel/1040-001.bin], this can be compiled easily with ''gcc -o hdapsd hdapsd.c''. Why this is not released cleanly on the original homepage eludes me as well... --[[User:Centic|Centic]] 12:34, 30 November 2008 (CET)

== "Reduced Power" hdapsd Consuming More Power ==

There is a link to a "reduced power" version of hdapsd, which is supposed to lower the number of timer interrupts (thereby reducing the power consumed by the daemon). From my experiments (using powertop), however, this program requires about twice as many interrupts to operate in "low power" mode as it does using the (older) sysfs interface. It also consumes enough CPU cycles to force my CPU back on periodically, consuming more power. Has anybody else had this experience?

--[[User:Mbsullivan|Mbsullivan]] 05:41, 24 August 2007 (UTC)

:Well, not really. With tp_smapi 0.31 and older hdapsd I had wakeups from hdapsd and from the hdaps module, now powertop only shows about 50wakeups from hdapsd (which are really from the module, but this is a bug in powertop, it tells who first called a function, not whose function it is [it's a function in the module code]). So I get a lower power consumption with the newer pair of tpsmapi and hdapsd
:--[[User:Zhenech|Zhenech]] 07:26, 24 August 2007 (UTC)

== I hawe a problem ==

I tray to start working my IBM x40 with hdaps function but I can't make it right.

The main problem is in a not hanging variables when I read
/sys/devices/platform/hdaps/position

==I also have this problem!==
Hi, I also have this problem that on my X40 the device/platform/hdaps/position does not give the right response. It is simply constant (128,1).
Does anyone have a clue? I use the suse kernel 2.6.16.13-4-default from suse10.1. the hdaps sources in that kernel are the same as in the original kernel.
thanks in advance,
----

Does the HDAPS sensor work under Windows (as observed from actual disk parking, or the graphical animation)?
Also, try loading [[tp_smapi]], it includes some patches for the hdaps driver. Does it help?

--[[User:Thinker|Thinker]] 16:45, 8 June 2006 (CEST)
----

HI Again,
HDAPS does work under windows. When I had windows running and then reboot the machine, hdaps is running under suse10.1 also. If I, however, turn off the machine and restart it, then, hdaps does *not* work anymore.
I remember that with suse 10.0 and the separate module, hdaps did work.
HDAPS now works with tp_smapi as suggested above.
Still, where does the problem derive from?

----

The hdaps in the vanilla kernel has some bugs (i.e., in doesn't talk to the hardware correctly) which tp_smapi fixes. Looks like you've hit one of these.

--[[User:Thinker|Thinker]] 18:05, 12 June 2006 (CEST)
----

==laptop acpi problem with hdaps==
 UPDATE: the problem seems fixed in the version 0.21 
<s>
My my both IBM T42/T43 laptops freezes time to times with the follow:

kernel 2.6.16/sata patch 
hdaps build as a module from the kernel.
tp_smapi 0.20/hdapsd

The freez is quite common then I access CD-ROM,but it also might freez without touching anything. 
After the freez keyboard doesn't work or priting some character,power button doesn't work, however mouse might continue to work. 
KDE battery systray shows discarchged batteries. 
Still under investigation that cases the problem. 
The related software:
khdapsmon 0.1.2 
ibm-acpi build-in as a module from the kernel(for ksensors)
modified ksensors without lm_sensors with a patch
http://bugs.gentoo.org/show_bug.cgi?id=116661

--noname 00:25, 13 June 2006 (CEST)Anton

----

You're the 2nd one reporting this. The fact you can reproduce it on two machines may be very helpful! Are these machines configured identically? Do they run the same software? Can you send your kernel .config, and precise kernel version + patches, to the e-mail address in the tp_smapi README? Please specify which hdaps or tp_smapi -related applications you're typically running.

BTW, if you have [[swsusp]] or [[Software Suspend 2]] installed, you can do a suspend-to-disk cycle to recover from the hang.

--[[User:Thinker|Thinker]] 11:53, 13 June 2006 (CEST)
----

I also have the follow
[[Problems_with_SATA_and_Linux#No_DMA_on_DVD_drive]].
So I switched cdrom driver from IDE to ATA and it fixed the problem.
However HDAPS has stared to freez a machine if I shake it then HDD is active.
The issue might be not related to ACPI but I'll log it here for now.

I'll send configs. Thank you.
ps. 0.21 is out so let me try the new version.
--noname 08:34, 22 June 2006 (CEST)Anton
</s>

== hdaps and /sys ==

Hey Fellas,

I've just upgraded from 2.6.15.2, where the patches all dropped in ok and all was well, to 2.6.17.6, where hdaps is built into the kernel.
the hdapsd daemon referenced on thinkwiki looks in /sys/block/<drive>/queue/protect to get started.
The default drivers that come with 2.6.17.6 for hdaps apparently dont put anything in /queue there, so there is no 'protect' directory.
Has anyone else experienced this? I'd love to get my drive protection back :)
ON THE UPSIDE! - the Ricoh card reader in my z60m came to life, and I can read sd cards (but not sony memory sticks, oddly enough)
Any input would be awesome!
dan@itkinetix.com

----

You need an extra kernel patch for "protect". Please read the page more carefully.

--[[User:Thinker|Thinker]] 00:24, 22 July 2006 (CEST)
----

== Gnome HDAPS-Applet and the new interface ==

I just installed my first linux kernel with the new hdaps disk protection interface. Since the file that controls the (un)parking of the disk heads has changed with this interface, you have to edit the GNOME HDAPS applet source before compiling to make it work. Simply replace the lines 
 
<nowiki>#define SYSFS_PROTECT_FILE_HDA "/sys/block/hda/queue/protect"</nowiki> 
<nowiki>#define SYSFS_PROTECT_FILE_SDA "/sys/block/sda/queue/protect"</nowiki> 
 
with these: 
 
<nowiki>#define SYSFS_PROTECT_FILE_HDA "/sys/block/hda/device/unload_heads"</nowiki> 
<nowiki>#define SYSFS_PROTECT_FILE_SDA "/sys/block/sda/device/unload_heads"</nowiki> 
 
Then proceed with the instructions in the included INSTALL file. 
 
Another hint: On Ubuntu 8.10, install the hdapsd package, then compile the new version of hdapsd and replace the binary in /usr/sbin. Afterwards edit the /etc/init.d/hdapsd file so it looks for the new interface. Otherwise it will never start hdapsd bcause it's looking for the /sys/block/<device>/queue/protect file which simply doesn't exist. You may want to use the init script I posted at https://bugs.launchpad.net/ubuntu/+source/hdapsd/+bug/303915/comments/3 
And don't forget that udev-rule to create the symlink hdapsd needs to work!

Kind regards, 
--[[User:Gollo|Gollo]] 20:15, 18 December 2008 (CET)

== Older discussion ==

So, this is in the stable kernel now, but what userspace program do we need to actually park the heads?
--[[User:MrStaticVoid|MrStaticVoid]] 01:26, 30 Oct 2005 (CEST)
----
Yes the hdaps driver is in the 2.6.14 kernel, but support to park the heads quickly and freeze the disk queue (to prevent the heads from getting un-parked) is not. There is some disagreement into how that should be implemented.

In other words, the hdaps driver for the moment is rather useless, unless you want to use it to play games.

--[[User:Tonko|Tonko]] 02:10, 30 Oct 2005 (CEST)

----
I head rumours that you can make SDL handle this like a joystick, e.g. for playing Neverball. Can anyone confirm or deny that? Thanx --[[User:Nomeata|Nomeata]] 01:16, 16 Nov 2005 (CET)

Yes it is possible to use it as a joystick, as Tonko allready mentioned.
/dev/input/jsX modprobe joydev

Ozi

Thanks, I didn't have the joydev module. Rebuilding... --[[User:129.13.186.1|129.13.186.1]] 15:30, 16 Nov 2005 (CET)

----
Yeah, it's a pretty good party trick - set up the HDAPS joystick as xmame input. You can play Ms. Pac-man by tilting your laptop to make pac-man navigate the maze. You can imagine that the pac-man "rolls" downhill, just like those old wooden marble-puzzles that you see around. Heh, can actually clear a level or two.

Marble madness was strangely unsatisfying though, and just didn't work well (probably due to the diagonal nature of the screen in that game).

--[[User:gsmenden|gsmenden]] 20:10, 13 Jan 2006 (CEST)

----
Anyone got the queue freezing patch running on 2.6.16? I'm going to try to manually merge it but didn't want to duplicate someone else's work.

--[[User:Ajbarr|Ajbarr]] 19:12, 22 March 2006 (CET)

Tp smapi

2010-07-12T02:33:59Z

Tripwired: /* Installation on Ubuntu Lucid */

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

{{HINT|This appears to be the ideal solution. A description of DKMS, from [http://linux.dell.com/projects.shtml#dkms Dell]: "DKMS stands for Dynamic Kernel Module Support. It is designed to create a framework where kernel dependent module source can reside so that it is very easy to rebuild modules as you upgrade kernels."}}

====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=====
1 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-07-12T02:33:10Z

Tripwired: /* Installation on Ubuntu Lucid */

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

{{HINT|This appears to be the ideal solution. For anyone wondering what DKMS is, from [http://linux.dell.com/projects.shtml#dkms Dell]: "DKMS stands for Dynamic Kernel Module Support. It is designed to create a framework where kernel dependent module source can reside so that it is very easy to rebuild modules as you upgrade kernels."}}

====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=====
1 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-07-12T02:32:48Z

Tripwired: /* Installation on Ubuntu Lucid */

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

{{HINT|This appears to be the ideal solution. For anyone wondering what DKMS is, from [http://linux.dell.com/projects.shtml#dkms Dell]: "DKMS stands for Dynamic Kernel Module Support. It is designed to create a framework where kernel dependent module source can reside so that it is very easy to rebuild modules as you upgrade kernels.}}

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

Installing Ubuntu 10.04 (Lucid Lynx) on a ThinkPad Z61m

2010-07-12T02:24:15Z

Tripwired: /* Set up HDAPS accelerometer event */

= Installing from USB stick=

If you already use Ubuntu 9.10 Karmic, installing Ubuntu 10.04 from USB stick is very easy. Just download the [http://www.ubuntu.com/getubuntu/download latest ISO], plug the USB stick in and run System-->Administration-->Create a USB startup disk. Load the downloaded ISO and hit "Make Startup Disk". For more information check [https://help.ubuntu.com/community/Installation/FromUSBStick#Creating%20a%20bootable%20USB%20Drive this page]. After that reboot your Thinkpad and press F12. This will allow you to boot from USB stick and start the installation routine.

= Tested Configuration =
* Lenovo ThinkPad {{Z61m}} (9450-H9G)
** [[Intel Core 2 Duo]] T5500 (1,66 GHz, 2 MB L2, 667MHz FSB)
** 2 GB RAM (2x 1 GB [[PC2-5300]] DDR2 667MHz)
** 15.4" wide-screen TFT WXGA 1280x800
** [[Intel Graphics Media Accelerator 950]]
** Seagate Momentus 7200.3 ST9160411ASG (160 GB SATA 7200 RPM) [http://www.thinkwiki.org/wiki/Talk:Problem_with_hard_drive_clicking reflashed to Dell OEM Firmware]
** Ultrabay Enhanced DVD±RW Burner (GMA-4082N, FRU 39T2723)
** Intel HD Audio with [[AD1981HD]] codec
** [[Broadcom Gigabit Ethernet (10/100/1000)]]
** [[ThinkPad Bluetooth with Enhanced Data Rate (BDC-2)]]
** [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter]]
** [[IrDA]] 1.1 (FIR - 4Mbps)
** [[SD_Card_slot|4-in-1 digital media reader]] (MultiMedia Card, MemoryStick, SD)
** [[Integrated Fingerprint Reader]]
** [[ThinkLight]]
** [[UltraNav]]
** [[CardBus]] slot (Type 2)
** [[ExpressCard slot]] (54 or 34)
** [[UltraBay|UltraBay Enhanced]]
** 3x USB 2.0, Firewire, VGA out, S-Video out, Headphone Jack, Microphone Jack
** Built-in Microphone

= Hardware Support =

{| border="2"
|Device / Function
|Works?
|Comment
|-
|Suspend & Hibernate
|{{Cyes}}
|out of the box
|-
|Intel GMA950 2D and 3D
|{{Cyes}}
|out of the box
|-
|Intel 3945ABG WiFi
|{{Cyes}}
|out of the box
|-
|Bluetooth
|{{Cyes}}
|out of the box
|-
|Broadcom Gigabit Ethernet
|{{Cyes}}
|out of the box
|-
|DVD±RW Burner
|{{Cyes}}
|out of the box
|-
|Ultrabay Hotswapping
|{{Cpart}}
|hotswapping optical drives (like DVD±RW) works out of the box, for HDD hotswapping [http://www.thinkwiki.org/wiki/How_to_hotswap_Ultrabay_devices#Using_libata-acpi_and_udev look here]
|-
|Hard Drive Active Protection System
|{{Cyes}}
|must be activated and configured. [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_%28Lucid_Lynx%29_on_a_ThinkPad_Z61m#Setup_Hard_Drive_Active_Protection_System See here]

|-
|Intel HDA Sound
|{{Cyes}}
|out of the box, modem must be enabled in BIOS
|-
|PCMCIA
|{{Cyes}}
|out of the box
|-
|Express Card
|{{Cunk}} (should work)
|not tested
|-
|TPM
|{{Cunk}} (should work)
|not tested, for further information check out these links [http://die-klapsmuehle.org/2009/01/29/how-to-use-a-tpm-with-ubuntu/], [https://www.grounation.org/index.php?post/2008/07/04/8-how-to-use-a-tpm-with-linux]
|-
|Firewire
|{{Cunk}} (should work)
|not tested
|-
|USB
|{{Cyes}}
|out of the box
|-
|IRDA
|{{Cunk}} (should work)
|not tested
|-
|Docking
|{{Cunk}} (should work)
|not tested
|-
|Fingerprint Reader
|{{Cyes}}
|works with ThinkFinger. [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_%28Lucid_Lynx%29_on_a_ThinkPad_Z61m#Setup_Fingerprint_Reader See here]
|-
|VGA out
|{{Cyes}}
|out of the box
|-
|S-Video out
|{{Cpart}}
|a 100 Hz Sony TV was recognized as a 30 Hz TV, poor picture
|-
|Modem
|{{Cunk}}
|not tested
|-
|Microphone
|{{Cyes}}
|both internal and external mics work out of the box, but are muted by default. See bellow
|-
|Headphones
|{{Cyes}}
|out of the box
|-
|Touchpad
|{{Cyes}}
|out of the box
|-
|Trackpoint
|{{Cyes}}
|out of the box, to enable middle button scrolling see bellow
|-
|Multimedia Card Reader
|{{Cyes}}?
|works out of the box with all kinds of SD cards. No other cards have been tested
|-
|{{key|Fn}}{{key|Fx}}, {{key|Fn}}{{key|PageUp}}, {{key|Fn}}{{key|Home}}, {{key|Fn}}{{key|End}}
|{{Cyes}}
|out of the box, except of {{key|Fn}}{{key|F9}} and {{key|Fn}}{{key|Space}}. For configuring {{key|Fn}}{{key|Space}} [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_%28Lucid_Lynx%29_on_a_ThinkPad_Z61m#Make_Fn-Space_.28Screen_Magnify.29_work see here]
|-
|{{key|Fn}}{{key|Up}}, {{key|Fn}}{{key|Down}}, {{key|Fn}}{{key|Left}}, {{key|Fn}}{{key|Right}}
|{{Cpart}}
|depends on the player, works out of the box with Rhytmbox but not Audacious. Thus, needs additional configuration
|-
|{{ibmkey|ThinkVantage|#495988}}
|{{Cyes}}
|does nothing by default, but can be easily mapped to something useful. [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_%28Lucid_Lynx%29_on_a_ThinkPad_Z61m#Map_ThinkVantage_Button See here]
|-
|{{ibmkey|Volume up|#494949}}, {{ibmkey|Volume down|#494949}}, {{ibmkey|Volume mute|#494949}}
|{{Cpart}}
|the volume buttons work but don't affect the software (Pulse Audio) mixer. For possible workarounds [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_%28Lucid_Lynx%29_on_a_ThinkPad_Z61m#Workaround_for_the_Volume_Buttons see here]
|-
|Back and Forward keys (near the arrow keys)
|{{Cyes}}
|out of the box
|-
|{{key|Fn}}{{key|Space}} (Screen Magnify)
|{{Cyes}}
|requires some acpi hacking. [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_%28Lucid_Lynx%29_on_a_ThinkPad_Z61m#Make_Fn-Space_.28Screen_Magnify.29_work See here]
|}

[[Category:Z61m]]

= HOWTOS =

== Setup the Middle Button Scrolling ==

Start a terminal and run

sudo gedit /usr/lib/X11/xorg.conf.d/20-trackpoint.conf

paste this

Section "InputClass"
Identifier "Trackpoint"
MatchProduct "TPPS/2 IBM TrackPoint|DualPoint Stick|Synaptics Inc. Composite TouchPad / TrackPoint"
MatchDevicePath "/dev/input/event*"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
Option "EmulateWheelTimeout" "200"
Option "Emulate3Buttons" "false"
Option "YAxisMapping" "4 5"
Option "XAxisMapping" "6 7"
EndSection

and save. Reboot.

== Configure Trackpoint and Touchpad ==
The most convenient way to do this is to install GPointing Device Settings via
sudo apt-get install gpointing-device-settings
After that you will find it in System -> Preferences -> Pointing Devices

[[image:Screenshot-GPointing Device Settings-TrackPoint.png]]

GPointing Device Settings, however, can't configure such important Trackpoint settings as sensitivity, speed and press to select. To do this, open a terminal, run
sudo apt-get install sysfsutils
sudo gedit /etc/rc.local
paste

for i in 1 2 3
do
if [ -d /sys/devices/platform/i8042/serio1/serio$i ]; then
echo -n 200 > /sys/devices/platform/i8042/serio1/serio$i/speed
echo -n 150 > /sys/devices/platform/i8042/serio1/serio$i/sensitivity
echo -n 1 > /sys/devices/platform/i8042/serio1/serio$i/press_to_select
fi
done

before
exit 0
and save. This will set sensitivity to 200, speed to 150 and activate press to select. Replacing "echo -n 1" by "echo -n 0" in the file will deactivate press to select. To find the right speed and sensitivity values, you should do some tests before by issuing
echo -n 200 | sudo tee /sys/devices/platform/i8042/serio1/serio?/sensitivity
echo -n 150 | sudo tee /sys/devices/platform/i8042/serio1/serio?/speed
in the terminal and using different numerical values between 0 and 255. The default values are 128 for sensitivity and 97 for speed.

== Workaround for the Volume Buttons ==

Volume buttons work but don't control software mixer settings. Thus you effectively get two volume scales completely independent from each other: Ubuntu's software mixer and Z61m's hardware mixer. That's confusing and inconvenient but as of 2010-05-05 (see [https://bugs.launchpad.net/ubuntu/+source/linux/+bug/357673 Bug #357673]) still unfixed.

=== Possible Workaround #1 ===

A simple workaround is to set hardware volume control to an acceptable level and not to use those volume buttons afterwards. Instead, you can use the software mixer only. It's easy to configure {{key|Win}}{{key|F1}} and {{key|Win}}{{key|F2}} which are not used in Ubuntu by default to act as volume buttons for the software mixer. To do this go to '''System -> Preferenced -> Keyboard shortcuts''', click on "Volume Down" and press {{key|Win}}{{key|F1}}. Now click on "Volume Up" and press {{key|Win}}{{key|F2}}. If you also need mute, you can define {{key|Win}}{{key|1}} for that. The changes will be applied immediately.

[[File:Screenshot-Keyboard_Shortcuts.png]]

=== Possible Workaround #2 ===

If you still want to use volume keys for volume control, you should run
sudo gedit /etc/rc.local
and add this before "exit 0"
cp /sys/devices/platform/thinkpad_acpi/hotkey_all_mask /sys/devices/platform/thinkpad_acpi/hotkey_mask
This solution is still not really acceptable because it uses a quite weird volume scale resulting in maximum loudness already on 50% of the software mixer. If you've already applied workaround #1, be sure to map "Volume Up" and "Volume Down" back to the Thinkpad volume keys

== Make Fn-Space (Screen Magnify) work ==

Open a terminal and run
sudo apt-get install kmag
sudo gedit /etc/acpi/events/asus-rotate
replace it's content by the following
# /etc/acpi/events/ibmwireless
# This is called when the user presses Fn-Space
event=ibm/hotkey HKEY 00000080 00001014
action=/etc/acpi/ibm-zoom.sh
and save. Now run
sudo cp /etc/acpi/ibm-wireless.sh /etc/acpi/ibm-zoom.sh
sudo gedit /etc/acpi/ibm-zoom.sh
and replace its content by the following
#!/bin/sh
#
# This script activates gnome-mag when Fn+Space is pressed
test -f /usr/share/acpi-support/key-constants || exit 0
. /usr/share/acpi-support/power-funcs
magnifier_pid=`pidof kmag`
for x in /tmp/.X11-unix/*; do
displaynum=`echo $x | sed s#/tmp/.X11-unix/X##`
getXconsole;
if [ x"$XAUTHORITY" != x"" ]; then
export DISPLAY=":$displaynum"
if [ "$magnifier_pid" != "" ]; then
/usr/bin/killall kmag
break
else
/usr/bin/kmag &
break
fi
fi
done
Save and reboot. Now when pressing Fn-Space you can open KMagnifier. Pressing Fn-Space once again will close KMagnifier. You can configure KMagnifier as you like and your settings will be saved automatically

== Map ThinkVantage Button ==
ThinkVantage Button is recognized but is not mapped to any function so that pressing it does nothing. To change this go to '''System->Preferences-> Keyboard shortcuts'''. There you can look for some predefined actions ThinkVantage Button might do for you. To map the button to a certain action simply click on the action and press {{ibmkey|ThinkVantage|#495988}}. Via Add you can also add your own commands, for instance to start your browser or e-mail client.

== Setup External Monitor or Beamer (VGA) ==

Connect your monitor/beamer to VGA port and go to '''System -> Preferences -> Monitors'''. For quick access to those settings it might be useful to activate "Show monitors in panel".

[[File:Lucid_ext_Monitor_new.png]]

You can also use this to configure an external device connected to S-Video Out.

[[File:Z61m_svideo.JPG]]

== Setup Color Management ==
To use ICC/ICM profiles you should install [http://projects.gnome.org/gnome-color-manager/ GNOME Color Manager] via
sudo apt-get install gnome-color-manager
After that it should appear under '''System -> Preferences -> Color Profiles'''. Alternatively you can start it from the terminal by issuing
gcm-prefs
GCM should detect your Thinkpad monitor automatically. All you need to do is supply the correct ICC/ICM profile by clicking on the list under '''Color Profile''' and selecting '''Other profile ...'''

[[File:CMgment.jpg]]

Lenovo does supply ICM profiles for most Thinkpads, but in order to open the appropriate .exe-archive under Linux you'll need Wine. Install Wine by running
sudo apt-get install wine
After that download [http://www-307.ibm.com/pc/support/site.wss/migr-62923.html 79oi22ww.exe] and right-click the file. Go to the '''Properties''' tab and tick '''Allow executing file as program''' In the '''Open With''' tab select '''Wine Windows Program Loader''' and close the dialog. Now double-click 79oi22ww.exe, and hit Next -> I accept the agreement -> Next -> Next -> Install -> Finish. Using Nautilus go to "~/.wine/drive_c/DRIVERS/WIN/MONITOR". There you'll find different ICM profiles which can be used by GCM. '''TPFLX.icm''' is for [http://www.thinkwiki.org/wiki/Flexview#Flexview_.28IPS.29 FlexView] panels whereas '''TPMB60.ICM''' and '''TPMB72.ICM''' are for [http://www.thinkwiki.org/wiki/Flexview#MaxBright MaxBright] panels. If you have only a plain TFT panel (not MaxBright) then stick to '''TPLCD.icm'''.

After importing the appropriate profile to GCM and selecting it, be sure to go to '''Defaults''' tab and select '''Apply display correction''' and '''Set profile for color managed applications''' Unfortunately, GCM doesn't seem to support manual adjustments of gamma, brightness or contrast on Thinkpad displays.

At least adjusting gamma is possible when using '''xgamma'''. In a terminal run
xgamma
to see you current gamma settings. You should see something like
-> Red 1.000, Green 1.000, Blue 1.000
It is possible to adjust gamma values for all colors at the same time by issuing something like
xgamma -gamma 0.9
or for red, green and blue separately
xgamma -rgamma 0.815 -ggamma 0.844 -bgamma 1.0
If you want to be able to relate RGB gamma values to a certain colour temperature, take a look at [http://www.vendian.org/mncharity/dir3/blackbody/UnstableURLs/bbr_color.html this page by Mitchell Charity]. Thus, to get something like 7800K you'll have to issue
xgamma -rgamma 0.8115 -ggamma 0.8351 -bgamma 1.0
After having found your favourite settings, you'll probably want to make them persistent. To do this go to '''System -> Preferences -> Startup Applications''', select the "Startup Programms" tab, click Add and add something like this
Name: xgamma
Command: xgamma -rgamma 0.8 -ggamma 0.8 -bgamma 1.0
(replace these values by your values) Click Add and then Close. Now these xgamma settings will be applied on each Gnome startup

== Setup Fingerprint Reader ==

Although thinkfinger can be installed from Lucid repos, it contains some regressions which
prevent fingerprint authentication from working properly. For more information check out
[https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 Bug #256429] Martin Schwenke
provides a PPA with the fixed version of thinkfinger which seems to work quite well.

To install thinkfinger open a terminal and run
sudo add-apt-repository ppa:martin-meltin/ppa
sudo apt-get update
sudo apt-get install libpam-thinkfinger=0.3+r118-0ubuntu4ppamartinmeltin5
sudo /usr/lib/pam-thinkfinger/pam-thinkfinger-enable
after that run
tf-tool --acquire $USERNAME
to acquire your fingerprint. Now you can use Z61m's fingerprint reader when using sudo/gksudo or in GDM login screen.

There seems to be a gnome-keyring related problem in Lucid when using fingerprint to log in. In that case Network Manager (nm-applet) may not appear in the panel or freeze when trying to change connection settings ([https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/529338 Bug #529338]). A known workaround is not to use fingerprint when logging in. You, however, still can use fingerprint for sudo, gksudo and all other supported authentication prompts.

== Setup Hard Drive Active Protection System ==
Open a terminal and run
sudo apt-get install tp-smapi-dkms
sudo apt-get install python python-gtk2 python-gnome2 hdapsd
Now run
sudo gedit /etc/modules
and add
tp_smapi
to the very end of the file so that it looks like this (example)
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
lp
tp_smapi

Reboot. Now HDAPS should work. If you want to have a HDAPS icon in your notification area
like in Windows, follow these steps to install [http://thpani.at/projects/thinkhdaps/ ThinkHDAPS]

Download [https://launchpad.net/~andypiperuk/+archive/andypiper-ppa/+files/thinkhdaps_0.2.1-1_all.deb https://launchpad.net/~andypiperuk/+archive/andypiper-ppa/+files/thinkhdaps_0.2.1-1_all.deb] and put it into your home directory. Right click on the file and select "Extract Here". In terminal run
cd ~
cd thinkhdaps_0.2.1-1_all
sudo cp
tar -zxvf data.tar.gz
sudo cp usr/bin/thinkhdaps /usr/bin/
sudo chmod +x /usr/bin/thinkhdaps
sudo cp usr/share/pixmaps/* /usr/share/pixmaps/

Now you can run
thinkhdaps &
to make the '''ThinkHDAPS''' icon appear in the notification area

[[File:ThinkHDAPS.png]]

To make it autostart go to '''System -> Preferences -> Startup Applications''', select the "Startup Programms" tab, click Add and add this
Name: thinkhdaps
Command: thinkhdaps
Click Add and then Close. Now the ThinkHDAPS icon should be always visible in the notification area.

To change the sensitivity run
sudo gedit /etc/default/hdapsd
and change the SENSITIVITY value. Default is 15 whereas higher values mean less sensitive. For example 25 seems to be just fine.

== Set up HDAPS accelerometer event ==
This section assumes you set up [http://www.thinkwiki.org/wiki/Tp_smapi#Installation_on_Ubuntu_Lucid tp_smapi].

To add the device rule (this worked for X61t, there is more info about the udev rule on [http://www.thinkwiki.org/wiki/Talk:HDAPS#Question_regarding_the_example_udev_rule_.3F the HDAPS Talk page])
echo 'KERNEL=="event[0-9]*", ATTRS{phys}=="hdaps/input1",ATTRS{modalias}=="input:b0019v1014p5054e4801-*",SYMLINK+="input/hdaps/accelerometer-event"' | sudo tee /etc/udev/rules.d/51-hdaps.rules
Then force the reloading of rules.d
sudo udevadm trigger
Now you should have a
/dev/input/hdaps/accelerometer-event

= Power Management =

== Fix the hard drive clicking bug ==
If you don't know what the hard drive clicking bug is, read [http://www.thinkwiki.org/wiki/Problem_with_hard_drive_clicking this]. Although this bug was apparently fixed in Ubuntu Karmic, Lucid seems to be affected.

{{WARN|Here is a solution that worked for me. It's a bit dirty and turns off the power management of your HDD. This will slightly decrease your battery life but greatly improve your drive's lifetime.}}
{{HINT|If you have a better solution, be sure to share it here}}

To fix the bug open a terminal and run
sudo cp /usr/lib/pm-utils/power.d/95hdparm-apm /etc/pm/power.d/
sudo gedit /etc/pm/power.d/95hdparm-apm

Insert "hdparm -B 254 /dev/sda" after "resume_hdparm_apm" so that the appropriate section looks like this

case "$1" in
thaw|resume|true|false) # true and false for power.d
resume_hdparm_apm
hdparm -B 254 /dev/sda
;;
*)
exit 254
;;
esac

To test the fix try suspending/resuming and plugging/unpluging AC power. After each process run
sudo hdparm -B /dev/sda
hdparm should always report

/dev/sda:
APM_level = 254

== Setup Fan Control ==

{{WARN|Wrong fan control settings may seriously damage you Thinkpad. You do it on your own risk!}}

To override BIOS fan control you can install '''ThinkPad Fan Control'''. Go to '''System -> Administration -> Synaptic Package Manager'''. Switch to the "Third Party Software" tab and click on "Add". As APT line add this
deb http://ppa.launchpad.net/tp-fan/ppa/ubuntu jaunty main
Click "Add Source" then "Close" and finally "Reload" as suggested. Now use "Synaptic Package Manager" to install following packages
tpfand tpfan-admin tpfand-profiles
Go to '''System -> Administration -> ThinkPad Fan Control''' and click on "Unlock". Select "Control system fan by software" and you're done.

It's also possible to define your own fan control rules thus overriding the default settings. To do this select "Manually configure system fan trigger temperatures". Here is an example for a Z61m with Core2Duo T5500 and GMA 950.
Models with discrete graphics (like FireGL) will probably need lower threshholds as they usually produce more heat and thus require better cooling.

[[File:Screenshot-ThinkPad_Fan_Control_Configuration.png]]

{{HELP|Did someone else experience this problem and test the workaround?}}

Sometimes ThinkPad Fan Control's daemon '''tpfand''' crashes for unknown reasons causing software fan control to stop working (i.e. BIOS starts controlling the fan). It seems that this problem is somehow HAL related, since tpfand relies on HAL for determining the ThinkPad's model. If the detection routine fails, '''tpfand''' stops immediately(see [https://bugs.launchpad.net/tp-fan/+bug/575199 Bug #575199]). A quick and dirty solution is to tweak this detection by editing tpfand's settings.py
sudo gedit /usr/lib/python2.6/dist-packages/tpfand/settings.py
and replacing
self.product_id = None
self.product_name = None
self.product_pretty_vendor = None
self.product_pretty_name = None
self.product_pretty_id = None
by
self.product_id = ''
self.product_name = ''
self.product_pretty_vendor = ''
self.product_pretty_name = ''
self.product_pretty_id = ''
this will prevent '''tpfand''' from crashing even if it wasn't able to detect your ThinkPad's model.

== Configure Battery Charge Control ==

In a terminal run
sudo apt-get install sysfsutils
sudo apt-get install tp-smapi-dkms

Now run
sudo gedit /etc/modules
and add
tp_smapi
to the very end of the file. Run
sudo gedit /etc/sysfs.conf
and add
devices/platform/smapi/BAT0/start_charge_thresh=85
devices/platform/smapi/BAT0/stop_charge_thresh=96
to the very end of the file. Save and reboot. With this values your battery will start charging at 80% and stop charging at 96%. Of course you can also put other values between 1 and 100.

To check the current thresholds run
cat /sys/devices/platform/smapi/BAT0/start_charge_thresh
and
cat /sys/devices/platform/smapi/BAT0/stop_charge_thresh

= External Sources =
*[http://wiki.ubuntuusers.de/Trackpoint] Trackpoint Configuration (wiki.ubuntuusers.de)
*[http://fedoraproject.org/wiki/Features/ColorManagement] Gnome Color Manager (fedoraproject.org)
*[http://www.ubuntufieldmanual.com/?q=node/38] Calibrate your monitor (Ubuntu Field Manual)

Installing Ubuntu 10.04 (Lucid Lynx) on a ThinkPad Z61m

2010-07-12T02:23:49Z

Tripwired: /* Set up HDAPS accelerometer event */

= Installing from USB stick=

If you already use Ubuntu 9.10 Karmic, installing Ubuntu 10.04 from USB stick is very easy. Just download the [http://www.ubuntu.com/getubuntu/download latest ISO], plug the USB stick in and run System-->Administration-->Create a USB startup disk. Load the downloaded ISO and hit "Make Startup Disk". For more information check [https://help.ubuntu.com/community/Installation/FromUSBStick#Creating%20a%20bootable%20USB%20Drive this page]. After that reboot your Thinkpad and press F12. This will allow you to boot from USB stick and start the installation routine.

= Tested Configuration =
* Lenovo ThinkPad {{Z61m}} (9450-H9G)
** [[Intel Core 2 Duo]] T5500 (1,66 GHz, 2 MB L2, 667MHz FSB)
** 2 GB RAM (2x 1 GB [[PC2-5300]] DDR2 667MHz)
** 15.4" wide-screen TFT WXGA 1280x800
** [[Intel Graphics Media Accelerator 950]]
** Seagate Momentus 7200.3 ST9160411ASG (160 GB SATA 7200 RPM) [http://www.thinkwiki.org/wiki/Talk:Problem_with_hard_drive_clicking reflashed to Dell OEM Firmware]
** Ultrabay Enhanced DVD±RW Burner (GMA-4082N, FRU 39T2723)
** Intel HD Audio with [[AD1981HD]] codec
** [[Broadcom Gigabit Ethernet (10/100/1000)]]
** [[ThinkPad Bluetooth with Enhanced Data Rate (BDC-2)]]
** [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter]]
** [[IrDA]] 1.1 (FIR - 4Mbps)
** [[SD_Card_slot|4-in-1 digital media reader]] (MultiMedia Card, MemoryStick, SD)
** [[Integrated Fingerprint Reader]]
** [[ThinkLight]]
** [[UltraNav]]
** [[CardBus]] slot (Type 2)
** [[ExpressCard slot]] (54 or 34)
** [[UltraBay|UltraBay Enhanced]]
** 3x USB 2.0, Firewire, VGA out, S-Video out, Headphone Jack, Microphone Jack
** Built-in Microphone

= Hardware Support =

{| border="2"
|Device / Function
|Works?
|Comment
|-
|Suspend & Hibernate
|{{Cyes}}
|out of the box
|-
|Intel GMA950 2D and 3D
|{{Cyes}}
|out of the box
|-
|Intel 3945ABG WiFi
|{{Cyes}}
|out of the box
|-
|Bluetooth
|{{Cyes}}
|out of the box
|-
|Broadcom Gigabit Ethernet
|{{Cyes}}
|out of the box
|-
|DVD±RW Burner
|{{Cyes}}
|out of the box
|-
|Ultrabay Hotswapping
|{{Cpart}}
|hotswapping optical drives (like DVD±RW) works out of the box, for HDD hotswapping [http://www.thinkwiki.org/wiki/How_to_hotswap_Ultrabay_devices#Using_libata-acpi_and_udev look here]
|-
|Hard Drive Active Protection System
|{{Cyes}}
|must be activated and configured. [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_%28Lucid_Lynx%29_on_a_ThinkPad_Z61m#Setup_Hard_Drive_Active_Protection_System See here]

|-
|Intel HDA Sound
|{{Cyes}}
|out of the box, modem must be enabled in BIOS
|-
|PCMCIA
|{{Cyes}}
|out of the box
|-
|Express Card
|{{Cunk}} (should work)
|not tested
|-
|TPM
|{{Cunk}} (should work)
|not tested, for further information check out these links [http://die-klapsmuehle.org/2009/01/29/how-to-use-a-tpm-with-ubuntu/], [https://www.grounation.org/index.php?post/2008/07/04/8-how-to-use-a-tpm-with-linux]
|-
|Firewire
|{{Cunk}} (should work)
|not tested
|-
|USB
|{{Cyes}}
|out of the box
|-
|IRDA
|{{Cunk}} (should work)
|not tested
|-
|Docking
|{{Cunk}} (should work)
|not tested
|-
|Fingerprint Reader
|{{Cyes}}
|works with ThinkFinger. [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_%28Lucid_Lynx%29_on_a_ThinkPad_Z61m#Setup_Fingerprint_Reader See here]
|-
|VGA out
|{{Cyes}}
|out of the box
|-
|S-Video out
|{{Cpart}}
|a 100 Hz Sony TV was recognized as a 30 Hz TV, poor picture
|-
|Modem
|{{Cunk}}
|not tested
|-
|Microphone
|{{Cyes}}
|both internal and external mics work out of the box, but are muted by default. See bellow
|-
|Headphones
|{{Cyes}}
|out of the box
|-
|Touchpad
|{{Cyes}}
|out of the box
|-
|Trackpoint
|{{Cyes}}
|out of the box, to enable middle button scrolling see bellow
|-
|Multimedia Card Reader
|{{Cyes}}?
|works out of the box with all kinds of SD cards. No other cards have been tested
|-
|{{key|Fn}}{{key|Fx}}, {{key|Fn}}{{key|PageUp}}, {{key|Fn}}{{key|Home}}, {{key|Fn}}{{key|End}}
|{{Cyes}}
|out of the box, except of {{key|Fn}}{{key|F9}} and {{key|Fn}}{{key|Space}}. For configuring {{key|Fn}}{{key|Space}} [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_%28Lucid_Lynx%29_on_a_ThinkPad_Z61m#Make_Fn-Space_.28Screen_Magnify.29_work see here]
|-
|{{key|Fn}}{{key|Up}}, {{key|Fn}}{{key|Down}}, {{key|Fn}}{{key|Left}}, {{key|Fn}}{{key|Right}}
|{{Cpart}}
|depends on the player, works out of the box with Rhytmbox but not Audacious. Thus, needs additional configuration
|-
|{{ibmkey|ThinkVantage|#495988}}
|{{Cyes}}
|does nothing by default, but can be easily mapped to something useful. [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_%28Lucid_Lynx%29_on_a_ThinkPad_Z61m#Map_ThinkVantage_Button See here]
|-
|{{ibmkey|Volume up|#494949}}, {{ibmkey|Volume down|#494949}}, {{ibmkey|Volume mute|#494949}}
|{{Cpart}}
|the volume buttons work but don't affect the software (Pulse Audio) mixer. For possible workarounds [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_%28Lucid_Lynx%29_on_a_ThinkPad_Z61m#Workaround_for_the_Volume_Buttons see here]
|-
|Back and Forward keys (near the arrow keys)
|{{Cyes}}
|out of the box
|-
|{{key|Fn}}{{key|Space}} (Screen Magnify)
|{{Cyes}}
|requires some acpi hacking. [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_%28Lucid_Lynx%29_on_a_ThinkPad_Z61m#Make_Fn-Space_.28Screen_Magnify.29_work See here]
|}

[[Category:Z61m]]

= HOWTOS =

== Setup the Middle Button Scrolling ==

Start a terminal and run

sudo gedit /usr/lib/X11/xorg.conf.d/20-trackpoint.conf

paste this

Section "InputClass"
Identifier "Trackpoint"
MatchProduct "TPPS/2 IBM TrackPoint|DualPoint Stick|Synaptics Inc. Composite TouchPad / TrackPoint"
MatchDevicePath "/dev/input/event*"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
Option "EmulateWheelTimeout" "200"
Option "Emulate3Buttons" "false"
Option "YAxisMapping" "4 5"
Option "XAxisMapping" "6 7"
EndSection

and save. Reboot.

== Configure Trackpoint and Touchpad ==
The most convenient way to do this is to install GPointing Device Settings via
sudo apt-get install gpointing-device-settings
After that you will find it in System -> Preferences -> Pointing Devices

[[image:Screenshot-GPointing Device Settings-TrackPoint.png]]

GPointing Device Settings, however, can't configure such important Trackpoint settings as sensitivity, speed and press to select. To do this, open a terminal, run
sudo apt-get install sysfsutils
sudo gedit /etc/rc.local
paste

for i in 1 2 3
do
if [ -d /sys/devices/platform/i8042/serio1/serio$i ]; then
echo -n 200 > /sys/devices/platform/i8042/serio1/serio$i/speed
echo -n 150 > /sys/devices/platform/i8042/serio1/serio$i/sensitivity
echo -n 1 > /sys/devices/platform/i8042/serio1/serio$i/press_to_select
fi
done

before
exit 0
and save. This will set sensitivity to 200, speed to 150 and activate press to select. Replacing "echo -n 1" by "echo -n 0" in the file will deactivate press to select. To find the right speed and sensitivity values, you should do some tests before by issuing
echo -n 200 | sudo tee /sys/devices/platform/i8042/serio1/serio?/sensitivity
echo -n 150 | sudo tee /sys/devices/platform/i8042/serio1/serio?/speed
in the terminal and using different numerical values between 0 and 255. The default values are 128 for sensitivity and 97 for speed.

== Workaround for the Volume Buttons ==

Volume buttons work but don't control software mixer settings. Thus you effectively get two volume scales completely independent from each other: Ubuntu's software mixer and Z61m's hardware mixer. That's confusing and inconvenient but as of 2010-05-05 (see [https://bugs.launchpad.net/ubuntu/+source/linux/+bug/357673 Bug #357673]) still unfixed.

=== Possible Workaround #1 ===

A simple workaround is to set hardware volume control to an acceptable level and not to use those volume buttons afterwards. Instead, you can use the software mixer only. It's easy to configure {{key|Win}}{{key|F1}} and {{key|Win}}{{key|F2}} which are not used in Ubuntu by default to act as volume buttons for the software mixer. To do this go to '''System -> Preferenced -> Keyboard shortcuts''', click on "Volume Down" and press {{key|Win}}{{key|F1}}. Now click on "Volume Up" and press {{key|Win}}{{key|F2}}. If you also need mute, you can define {{key|Win}}{{key|1}} for that. The changes will be applied immediately.

[[File:Screenshot-Keyboard_Shortcuts.png]]

=== Possible Workaround #2 ===

If you still want to use volume keys for volume control, you should run
sudo gedit /etc/rc.local
and add this before "exit 0"
cp /sys/devices/platform/thinkpad_acpi/hotkey_all_mask /sys/devices/platform/thinkpad_acpi/hotkey_mask
This solution is still not really acceptable because it uses a quite weird volume scale resulting in maximum loudness already on 50% of the software mixer. If you've already applied workaround #1, be sure to map "Volume Up" and "Volume Down" back to the Thinkpad volume keys

== Make Fn-Space (Screen Magnify) work ==

Open a terminal and run
sudo apt-get install kmag
sudo gedit /etc/acpi/events/asus-rotate
replace it's content by the following
# /etc/acpi/events/ibmwireless
# This is called when the user presses Fn-Space
event=ibm/hotkey HKEY 00000080 00001014
action=/etc/acpi/ibm-zoom.sh
and save. Now run
sudo cp /etc/acpi/ibm-wireless.sh /etc/acpi/ibm-zoom.sh
sudo gedit /etc/acpi/ibm-zoom.sh
and replace its content by the following
#!/bin/sh
#
# This script activates gnome-mag when Fn+Space is pressed
test -f /usr/share/acpi-support/key-constants || exit 0
. /usr/share/acpi-support/power-funcs
magnifier_pid=`pidof kmag`
for x in /tmp/.X11-unix/*; do
displaynum=`echo $x | sed s#/tmp/.X11-unix/X##`
getXconsole;
if [ x"$XAUTHORITY" != x"" ]; then
export DISPLAY=":$displaynum"
if [ "$magnifier_pid" != "" ]; then
/usr/bin/killall kmag
break
else
/usr/bin/kmag &
break
fi
fi
done
Save and reboot. Now when pressing Fn-Space you can open KMagnifier. Pressing Fn-Space once again will close KMagnifier. You can configure KMagnifier as you like and your settings will be saved automatically

== Map ThinkVantage Button ==
ThinkVantage Button is recognized but is not mapped to any function so that pressing it does nothing. To change this go to '''System->Preferences-> Keyboard shortcuts'''. There you can look for some predefined actions ThinkVantage Button might do for you. To map the button to a certain action simply click on the action and press {{ibmkey|ThinkVantage|#495988}}. Via Add you can also add your own commands, for instance to start your browser or e-mail client.

== Setup External Monitor or Beamer (VGA) ==

Connect your monitor/beamer to VGA port and go to '''System -> Preferences -> Monitors'''. For quick access to those settings it might be useful to activate "Show monitors in panel".

[[File:Lucid_ext_Monitor_new.png]]

You can also use this to configure an external device connected to S-Video Out.

[[File:Z61m_svideo.JPG]]

== Setup Color Management ==
To use ICC/ICM profiles you should install [http://projects.gnome.org/gnome-color-manager/ GNOME Color Manager] via
sudo apt-get install gnome-color-manager
After that it should appear under '''System -> Preferences -> Color Profiles'''. Alternatively you can start it from the terminal by issuing
gcm-prefs
GCM should detect your Thinkpad monitor automatically. All you need to do is supply the correct ICC/ICM profile by clicking on the list under '''Color Profile''' and selecting '''Other profile ...'''

[[File:CMgment.jpg]]

Lenovo does supply ICM profiles for most Thinkpads, but in order to open the appropriate .exe-archive under Linux you'll need Wine. Install Wine by running
sudo apt-get install wine
After that download [http://www-307.ibm.com/pc/support/site.wss/migr-62923.html 79oi22ww.exe] and right-click the file. Go to the '''Properties''' tab and tick '''Allow executing file as program''' In the '''Open With''' tab select '''Wine Windows Program Loader''' and close the dialog. Now double-click 79oi22ww.exe, and hit Next -> I accept the agreement -> Next -> Next -> Install -> Finish. Using Nautilus go to "~/.wine/drive_c/DRIVERS/WIN/MONITOR". There you'll find different ICM profiles which can be used by GCM. '''TPFLX.icm''' is for [http://www.thinkwiki.org/wiki/Flexview#Flexview_.28IPS.29 FlexView] panels whereas '''TPMB60.ICM''' and '''TPMB72.ICM''' are for [http://www.thinkwiki.org/wiki/Flexview#MaxBright MaxBright] panels. If you have only a plain TFT panel (not MaxBright) then stick to '''TPLCD.icm'''.

After importing the appropriate profile to GCM and selecting it, be sure to go to '''Defaults''' tab and select '''Apply display correction''' and '''Set profile for color managed applications''' Unfortunately, GCM doesn't seem to support manual adjustments of gamma, brightness or contrast on Thinkpad displays.

At least adjusting gamma is possible when using '''xgamma'''. In a terminal run
xgamma
to see you current gamma settings. You should see something like
-> Red 1.000, Green 1.000, Blue 1.000
It is possible to adjust gamma values for all colors at the same time by issuing something like
xgamma -gamma 0.9
or for red, green and blue separately
xgamma -rgamma 0.815 -ggamma 0.844 -bgamma 1.0
If you want to be able to relate RGB gamma values to a certain colour temperature, take a look at [http://www.vendian.org/mncharity/dir3/blackbody/UnstableURLs/bbr_color.html this page by Mitchell Charity]. Thus, to get something like 7800K you'll have to issue
xgamma -rgamma 0.8115 -ggamma 0.8351 -bgamma 1.0
After having found your favourite settings, you'll probably want to make them persistent. To do this go to '''System -> Preferences -> Startup Applications''', select the "Startup Programms" tab, click Add and add something like this
Name: xgamma
Command: xgamma -rgamma 0.8 -ggamma 0.8 -bgamma 1.0
(replace these values by your values) Click Add and then Close. Now these xgamma settings will be applied on each Gnome startup

== Setup Fingerprint Reader ==

Although thinkfinger can be installed from Lucid repos, it contains some regressions which
prevent fingerprint authentication from working properly. For more information check out
[https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 Bug #256429] Martin Schwenke
provides a PPA with the fixed version of thinkfinger which seems to work quite well.

To install thinkfinger open a terminal and run
sudo add-apt-repository ppa:martin-meltin/ppa
sudo apt-get update
sudo apt-get install libpam-thinkfinger=0.3+r118-0ubuntu4ppamartinmeltin5
sudo /usr/lib/pam-thinkfinger/pam-thinkfinger-enable
after that run
tf-tool --acquire $USERNAME
to acquire your fingerprint. Now you can use Z61m's fingerprint reader when using sudo/gksudo or in GDM login screen.

There seems to be a gnome-keyring related problem in Lucid when using fingerprint to log in. In that case Network Manager (nm-applet) may not appear in the panel or freeze when trying to change connection settings ([https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/529338 Bug #529338]). A known workaround is not to use fingerprint when logging in. You, however, still can use fingerprint for sudo, gksudo and all other supported authentication prompts.

== Setup Hard Drive Active Protection System ==
Open a terminal and run
sudo apt-get install tp-smapi-dkms
sudo apt-get install python python-gtk2 python-gnome2 hdapsd
Now run
sudo gedit /etc/modules
and add
tp_smapi
to the very end of the file so that it looks like this (example)
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
lp
tp_smapi

Reboot. Now HDAPS should work. If you want to have a HDAPS icon in your notification area
like in Windows, follow these steps to install [http://thpani.at/projects/thinkhdaps/ ThinkHDAPS]

Download [https://launchpad.net/~andypiperuk/+archive/andypiper-ppa/+files/thinkhdaps_0.2.1-1_all.deb https://launchpad.net/~andypiperuk/+archive/andypiper-ppa/+files/thinkhdaps_0.2.1-1_all.deb] and put it into your home directory. Right click on the file and select "Extract Here". In terminal run
cd ~
cd thinkhdaps_0.2.1-1_all
sudo cp
tar -zxvf data.tar.gz
sudo cp usr/bin/thinkhdaps /usr/bin/
sudo chmod +x /usr/bin/thinkhdaps
sudo cp usr/share/pixmaps/* /usr/share/pixmaps/

Now you can run
thinkhdaps &
to make the '''ThinkHDAPS''' icon appear in the notification area

[[File:ThinkHDAPS.png]]

To make it autostart go to '''System -> Preferences -> Startup Applications''', select the "Startup Programms" tab, click Add and add this
Name: thinkhdaps
Command: thinkhdaps
Click Add and then Close. Now the ThinkHDAPS icon should be always visible in the notification area.

To change the sensitivity run
sudo gedit /etc/default/hdapsd
and change the SENSITIVITY value. Default is 15 whereas higher values mean less sensitive. For example 25 seems to be just fine.

== Set up HDAPS accelerometer event ==
This section assumes you set up [http://www.thinkwiki.org/wiki/Tp_smapi#Installation_on_Ubuntu_Lucid this page tp_smapi].

To add the device rule (this worked for X61t, there is more info about the udev rule on [http://www.thinkwiki.org/wiki/Talk:HDAPS#Question_regarding_the_example_udev_rule_.3F the HDAPS Talk page])
echo 'KERNEL=="event[0-9]*", ATTRS{phys}=="hdaps/input1",ATTRS{modalias}=="input:b0019v1014p5054e4801-*",SYMLINK+="input/hdaps/accelerometer-event"' | sudo tee /etc/udev/rules.d/51-hdaps.rules
Then force the reloading of rules.d
sudo udevadm trigger
Now you should have a
/dev/input/hdaps/accelerometer-event

= Power Management =

== Fix the hard drive clicking bug ==
If you don't know what the hard drive clicking bug is, read [http://www.thinkwiki.org/wiki/Problem_with_hard_drive_clicking this]. Although this bug was apparently fixed in Ubuntu Karmic, Lucid seems to be affected.

{{WARN|Here is a solution that worked for me. It's a bit dirty and turns off the power management of your HDD. This will slightly decrease your battery life but greatly improve your drive's lifetime.}}
{{HINT|If you have a better solution, be sure to share it here}}

To fix the bug open a terminal and run
sudo cp /usr/lib/pm-utils/power.d/95hdparm-apm /etc/pm/power.d/
sudo gedit /etc/pm/power.d/95hdparm-apm

Insert "hdparm -B 254 /dev/sda" after "resume_hdparm_apm" so that the appropriate section looks like this

case "$1" in
thaw|resume|true|false) # true and false for power.d
resume_hdparm_apm
hdparm -B 254 /dev/sda
;;
*)
exit 254
;;
esac

To test the fix try suspending/resuming and plugging/unpluging AC power. After each process run
sudo hdparm -B /dev/sda
hdparm should always report

/dev/sda:
APM_level = 254

== Setup Fan Control ==

{{WARN|Wrong fan control settings may seriously damage you Thinkpad. You do it on your own risk!}}

To override BIOS fan control you can install '''ThinkPad Fan Control'''. Go to '''System -> Administration -> Synaptic Package Manager'''. Switch to the "Third Party Software" tab and click on "Add". As APT line add this
deb http://ppa.launchpad.net/tp-fan/ppa/ubuntu jaunty main
Click "Add Source" then "Close" and finally "Reload" as suggested. Now use "Synaptic Package Manager" to install following packages
tpfand tpfan-admin tpfand-profiles
Go to '''System -> Administration -> ThinkPad Fan Control''' and click on "Unlock". Select "Control system fan by software" and you're done.

It's also possible to define your own fan control rules thus overriding the default settings. To do this select "Manually configure system fan trigger temperatures". Here is an example for a Z61m with Core2Duo T5500 and GMA 950.
Models with discrete graphics (like FireGL) will probably need lower threshholds as they usually produce more heat and thus require better cooling.

[[File:Screenshot-ThinkPad_Fan_Control_Configuration.png]]

{{HELP|Did someone else experience this problem and test the workaround?}}

Sometimes ThinkPad Fan Control's daemon '''tpfand''' crashes for unknown reasons causing software fan control to stop working (i.e. BIOS starts controlling the fan). It seems that this problem is somehow HAL related, since tpfand relies on HAL for determining the ThinkPad's model. If the detection routine fails, '''tpfand''' stops immediately(see [https://bugs.launchpad.net/tp-fan/+bug/575199 Bug #575199]). A quick and dirty solution is to tweak this detection by editing tpfand's settings.py
sudo gedit /usr/lib/python2.6/dist-packages/tpfand/settings.py
and replacing
self.product_id = None
self.product_name = None
self.product_pretty_vendor = None
self.product_pretty_name = None
self.product_pretty_id = None
by
self.product_id = ''
self.product_name = ''
self.product_pretty_vendor = ''
self.product_pretty_name = ''
self.product_pretty_id = ''
this will prevent '''tpfand''' from crashing even if it wasn't able to detect your ThinkPad's model.

== Configure Battery Charge Control ==

In a terminal run
sudo apt-get install sysfsutils
sudo apt-get install tp-smapi-dkms

Now run
sudo gedit /etc/modules
and add
tp_smapi
to the very end of the file. Run
sudo gedit /etc/sysfs.conf
and add
devices/platform/smapi/BAT0/start_charge_thresh=85
devices/platform/smapi/BAT0/stop_charge_thresh=96
to the very end of the file. Save and reboot. With this values your battery will start charging at 80% and stop charging at 96%. Of course you can also put other values between 1 and 100.

To check the current thresholds run
cat /sys/devices/platform/smapi/BAT0/start_charge_thresh
and
cat /sys/devices/platform/smapi/BAT0/stop_charge_thresh

= External Sources =
*[http://wiki.ubuntuusers.de/Trackpoint] Trackpoint Configuration (wiki.ubuntuusers.de)
*[http://fedoraproject.org/wiki/Features/ColorManagement] Gnome Color Manager (fedoraproject.org)
*[http://www.ubuntufieldmanual.com/?q=node/38] Calibrate your monitor (Ubuntu Field Manual)

Installing Ubuntu 10.04 (Lucid Lynx) on a ThinkPad Z61m

2010-07-12T02:22:29Z

Tripwired: /* Set up HDAPS accelerometer event */

= Installing from USB stick=

If you already use Ubuntu 9.10 Karmic, installing Ubuntu 10.04 from USB stick is very easy. Just download the [http://www.ubuntu.com/getubuntu/download latest ISO], plug the USB stick in and run System-->Administration-->Create a USB startup disk. Load the downloaded ISO and hit "Make Startup Disk". For more information check [https://help.ubuntu.com/community/Installation/FromUSBStick#Creating%20a%20bootable%20USB%20Drive this page]. After that reboot your Thinkpad and press F12. This will allow you to boot from USB stick and start the installation routine.

= Tested Configuration =
* Lenovo ThinkPad {{Z61m}} (9450-H9G)
** [[Intel Core 2 Duo]] T5500 (1,66 GHz, 2 MB L2, 667MHz FSB)
** 2 GB RAM (2x 1 GB [[PC2-5300]] DDR2 667MHz)
** 15.4" wide-screen TFT WXGA 1280x800
** [[Intel Graphics Media Accelerator 950]]
** Seagate Momentus 7200.3 ST9160411ASG (160 GB SATA 7200 RPM) [http://www.thinkwiki.org/wiki/Talk:Problem_with_hard_drive_clicking reflashed to Dell OEM Firmware]
** Ultrabay Enhanced DVD±RW Burner (GMA-4082N, FRU 39T2723)
** Intel HD Audio with [[AD1981HD]] codec
** [[Broadcom Gigabit Ethernet (10/100/1000)]]
** [[ThinkPad Bluetooth with Enhanced Data Rate (BDC-2)]]
** [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter]]
** [[IrDA]] 1.1 (FIR - 4Mbps)
** [[SD_Card_slot|4-in-1 digital media reader]] (MultiMedia Card, MemoryStick, SD)
** [[Integrated Fingerprint Reader]]
** [[ThinkLight]]
** [[UltraNav]]
** [[CardBus]] slot (Type 2)
** [[ExpressCard slot]] (54 or 34)
** [[UltraBay|UltraBay Enhanced]]
** 3x USB 2.0, Firewire, VGA out, S-Video out, Headphone Jack, Microphone Jack
** Built-in Microphone

= Hardware Support =

{| border="2"
|Device / Function
|Works?
|Comment
|-
|Suspend & Hibernate
|{{Cyes}}
|out of the box
|-
|Intel GMA950 2D and 3D
|{{Cyes}}
|out of the box
|-
|Intel 3945ABG WiFi
|{{Cyes}}
|out of the box
|-
|Bluetooth
|{{Cyes}}
|out of the box
|-
|Broadcom Gigabit Ethernet
|{{Cyes}}
|out of the box
|-
|DVD±RW Burner
|{{Cyes}}
|out of the box
|-
|Ultrabay Hotswapping
|{{Cpart}}
|hotswapping optical drives (like DVD±RW) works out of the box, for HDD hotswapping [http://www.thinkwiki.org/wiki/How_to_hotswap_Ultrabay_devices#Using_libata-acpi_and_udev look here]
|-
|Hard Drive Active Protection System
|{{Cyes}}
|must be activated and configured. [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_%28Lucid_Lynx%29_on_a_ThinkPad_Z61m#Setup_Hard_Drive_Active_Protection_System See here]

|-
|Intel HDA Sound
|{{Cyes}}
|out of the box, modem must be enabled in BIOS
|-
|PCMCIA
|{{Cyes}}
|out of the box
|-
|Express Card
|{{Cunk}} (should work)
|not tested
|-
|TPM
|{{Cunk}} (should work)
|not tested, for further information check out these links [http://die-klapsmuehle.org/2009/01/29/how-to-use-a-tpm-with-ubuntu/], [https://www.grounation.org/index.php?post/2008/07/04/8-how-to-use-a-tpm-with-linux]
|-
|Firewire
|{{Cunk}} (should work)
|not tested
|-
|USB
|{{Cyes}}
|out of the box
|-
|IRDA
|{{Cunk}} (should work)
|not tested
|-
|Docking
|{{Cunk}} (should work)
|not tested
|-
|Fingerprint Reader
|{{Cyes}}
|works with ThinkFinger. [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_%28Lucid_Lynx%29_on_a_ThinkPad_Z61m#Setup_Fingerprint_Reader See here]
|-
|VGA out
|{{Cyes}}
|out of the box
|-
|S-Video out
|{{Cpart}}
|a 100 Hz Sony TV was recognized as a 30 Hz TV, poor picture
|-
|Modem
|{{Cunk}}
|not tested
|-
|Microphone
|{{Cyes}}
|both internal and external mics work out of the box, but are muted by default. See bellow
|-
|Headphones
|{{Cyes}}
|out of the box
|-
|Touchpad
|{{Cyes}}
|out of the box
|-
|Trackpoint
|{{Cyes}}
|out of the box, to enable middle button scrolling see bellow
|-
|Multimedia Card Reader
|{{Cyes}}?
|works out of the box with all kinds of SD cards. No other cards have been tested
|-
|{{key|Fn}}{{key|Fx}}, {{key|Fn}}{{key|PageUp}}, {{key|Fn}}{{key|Home}}, {{key|Fn}}{{key|End}}
|{{Cyes}}
|out of the box, except of {{key|Fn}}{{key|F9}} and {{key|Fn}}{{key|Space}}. For configuring {{key|Fn}}{{key|Space}} [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_%28Lucid_Lynx%29_on_a_ThinkPad_Z61m#Make_Fn-Space_.28Screen_Magnify.29_work see here]
|-
|{{key|Fn}}{{key|Up}}, {{key|Fn}}{{key|Down}}, {{key|Fn}}{{key|Left}}, {{key|Fn}}{{key|Right}}
|{{Cpart}}
|depends on the player, works out of the box with Rhytmbox but not Audacious. Thus, needs additional configuration
|-
|{{ibmkey|ThinkVantage|#495988}}
|{{Cyes}}
|does nothing by default, but can be easily mapped to something useful. [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_%28Lucid_Lynx%29_on_a_ThinkPad_Z61m#Map_ThinkVantage_Button See here]
|-
|{{ibmkey|Volume up|#494949}}, {{ibmkey|Volume down|#494949}}, {{ibmkey|Volume mute|#494949}}
|{{Cpart}}
|the volume buttons work but don't affect the software (Pulse Audio) mixer. For possible workarounds [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_%28Lucid_Lynx%29_on_a_ThinkPad_Z61m#Workaround_for_the_Volume_Buttons see here]
|-
|Back and Forward keys (near the arrow keys)
|{{Cyes}}
|out of the box
|-
|{{key|Fn}}{{key|Space}} (Screen Magnify)
|{{Cyes}}
|requires some acpi hacking. [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_%28Lucid_Lynx%29_on_a_ThinkPad_Z61m#Make_Fn-Space_.28Screen_Magnify.29_work See here]
|}

[[Category:Z61m]]

= HOWTOS =

== Setup the Middle Button Scrolling ==

Start a terminal and run

sudo gedit /usr/lib/X11/xorg.conf.d/20-trackpoint.conf

paste this

Section "InputClass"
Identifier "Trackpoint"
MatchProduct "TPPS/2 IBM TrackPoint|DualPoint Stick|Synaptics Inc. Composite TouchPad / TrackPoint"
MatchDevicePath "/dev/input/event*"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
Option "EmulateWheelTimeout" "200"
Option "Emulate3Buttons" "false"
Option "YAxisMapping" "4 5"
Option "XAxisMapping" "6 7"
EndSection

and save. Reboot.

== Configure Trackpoint and Touchpad ==
The most convenient way to do this is to install GPointing Device Settings via
sudo apt-get install gpointing-device-settings
After that you will find it in System -> Preferences -> Pointing Devices

[[image:Screenshot-GPointing Device Settings-TrackPoint.png]]

GPointing Device Settings, however, can't configure such important Trackpoint settings as sensitivity, speed and press to select. To do this, open a terminal, run
sudo apt-get install sysfsutils
sudo gedit /etc/rc.local
paste

for i in 1 2 3
do
if [ -d /sys/devices/platform/i8042/serio1/serio$i ]; then
echo -n 200 > /sys/devices/platform/i8042/serio1/serio$i/speed
echo -n 150 > /sys/devices/platform/i8042/serio1/serio$i/sensitivity
echo -n 1 > /sys/devices/platform/i8042/serio1/serio$i/press_to_select
fi
done

before
exit 0
and save. This will set sensitivity to 200, speed to 150 and activate press to select. Replacing "echo -n 1" by "echo -n 0" in the file will deactivate press to select. To find the right speed and sensitivity values, you should do some tests before by issuing
echo -n 200 | sudo tee /sys/devices/platform/i8042/serio1/serio?/sensitivity
echo -n 150 | sudo tee /sys/devices/platform/i8042/serio1/serio?/speed
in the terminal and using different numerical values between 0 and 255. The default values are 128 for sensitivity and 97 for speed.

== Workaround for the Volume Buttons ==

Volume buttons work but don't control software mixer settings. Thus you effectively get two volume scales completely independent from each other: Ubuntu's software mixer and Z61m's hardware mixer. That's confusing and inconvenient but as of 2010-05-05 (see [https://bugs.launchpad.net/ubuntu/+source/linux/+bug/357673 Bug #357673]) still unfixed.

=== Possible Workaround #1 ===

A simple workaround is to set hardware volume control to an acceptable level and not to use those volume buttons afterwards. Instead, you can use the software mixer only. It's easy to configure {{key|Win}}{{key|F1}} and {{key|Win}}{{key|F2}} which are not used in Ubuntu by default to act as volume buttons for the software mixer. To do this go to '''System -> Preferenced -> Keyboard shortcuts''', click on "Volume Down" and press {{key|Win}}{{key|F1}}. Now click on "Volume Up" and press {{key|Win}}{{key|F2}}. If you also need mute, you can define {{key|Win}}{{key|1}} for that. The changes will be applied immediately.

[[File:Screenshot-Keyboard_Shortcuts.png]]

=== Possible Workaround #2 ===

If you still want to use volume keys for volume control, you should run
sudo gedit /etc/rc.local
and add this before "exit 0"
cp /sys/devices/platform/thinkpad_acpi/hotkey_all_mask /sys/devices/platform/thinkpad_acpi/hotkey_mask
This solution is still not really acceptable because it uses a quite weird volume scale resulting in maximum loudness already on 50% of the software mixer. If you've already applied workaround #1, be sure to map "Volume Up" and "Volume Down" back to the Thinkpad volume keys

== Make Fn-Space (Screen Magnify) work ==

Open a terminal and run
sudo apt-get install kmag
sudo gedit /etc/acpi/events/asus-rotate
replace it's content by the following
# /etc/acpi/events/ibmwireless
# This is called when the user presses Fn-Space
event=ibm/hotkey HKEY 00000080 00001014
action=/etc/acpi/ibm-zoom.sh
and save. Now run
sudo cp /etc/acpi/ibm-wireless.sh /etc/acpi/ibm-zoom.sh
sudo gedit /etc/acpi/ibm-zoom.sh
and replace its content by the following
#!/bin/sh
#
# This script activates gnome-mag when Fn+Space is pressed
test -f /usr/share/acpi-support/key-constants || exit 0
. /usr/share/acpi-support/power-funcs
magnifier_pid=`pidof kmag`
for x in /tmp/.X11-unix/*; do
displaynum=`echo $x | sed s#/tmp/.X11-unix/X##`
getXconsole;
if [ x"$XAUTHORITY" != x"" ]; then
export DISPLAY=":$displaynum"
if [ "$magnifier_pid" != "" ]; then
/usr/bin/killall kmag
break
else
/usr/bin/kmag &
break
fi
fi
done
Save and reboot. Now when pressing Fn-Space you can open KMagnifier. Pressing Fn-Space once again will close KMagnifier. You can configure KMagnifier as you like and your settings will be saved automatically

== Map ThinkVantage Button ==
ThinkVantage Button is recognized but is not mapped to any function so that pressing it does nothing. To change this go to '''System->Preferences-> Keyboard shortcuts'''. There you can look for some predefined actions ThinkVantage Button might do for you. To map the button to a certain action simply click on the action and press {{ibmkey|ThinkVantage|#495988}}. Via Add you can also add your own commands, for instance to start your browser or e-mail client.

== Setup External Monitor or Beamer (VGA) ==

Connect your monitor/beamer to VGA port and go to '''System -> Preferences -> Monitors'''. For quick access to those settings it might be useful to activate "Show monitors in panel".

[[File:Lucid_ext_Monitor_new.png]]

You can also use this to configure an external device connected to S-Video Out.

[[File:Z61m_svideo.JPG]]

== Setup Color Management ==
To use ICC/ICM profiles you should install [http://projects.gnome.org/gnome-color-manager/ GNOME Color Manager] via
sudo apt-get install gnome-color-manager
After that it should appear under '''System -> Preferences -> Color Profiles'''. Alternatively you can start it from the terminal by issuing
gcm-prefs
GCM should detect your Thinkpad monitor automatically. All you need to do is supply the correct ICC/ICM profile by clicking on the list under '''Color Profile''' and selecting '''Other profile ...'''

[[File:CMgment.jpg]]

Lenovo does supply ICM profiles for most Thinkpads, but in order to open the appropriate .exe-archive under Linux you'll need Wine. Install Wine by running
sudo apt-get install wine
After that download [http://www-307.ibm.com/pc/support/site.wss/migr-62923.html 79oi22ww.exe] and right-click the file. Go to the '''Properties''' tab and tick '''Allow executing file as program''' In the '''Open With''' tab select '''Wine Windows Program Loader''' and close the dialog. Now double-click 79oi22ww.exe, and hit Next -> I accept the agreement -> Next -> Next -> Install -> Finish. Using Nautilus go to "~/.wine/drive_c/DRIVERS/WIN/MONITOR". There you'll find different ICM profiles which can be used by GCM. '''TPFLX.icm''' is for [http://www.thinkwiki.org/wiki/Flexview#Flexview_.28IPS.29 FlexView] panels whereas '''TPMB60.ICM''' and '''TPMB72.ICM''' are for [http://www.thinkwiki.org/wiki/Flexview#MaxBright MaxBright] panels. If you have only a plain TFT panel (not MaxBright) then stick to '''TPLCD.icm'''.

After importing the appropriate profile to GCM and selecting it, be sure to go to '''Defaults''' tab and select '''Apply display correction''' and '''Set profile for color managed applications''' Unfortunately, GCM doesn't seem to support manual adjustments of gamma, brightness or contrast on Thinkpad displays.

At least adjusting gamma is possible when using '''xgamma'''. In a terminal run
xgamma
to see you current gamma settings. You should see something like
-> Red 1.000, Green 1.000, Blue 1.000
It is possible to adjust gamma values for all colors at the same time by issuing something like
xgamma -gamma 0.9
or for red, green and blue separately
xgamma -rgamma 0.815 -ggamma 0.844 -bgamma 1.0
If you want to be able to relate RGB gamma values to a certain colour temperature, take a look at [http://www.vendian.org/mncharity/dir3/blackbody/UnstableURLs/bbr_color.html this page by Mitchell Charity]. Thus, to get something like 7800K you'll have to issue
xgamma -rgamma 0.8115 -ggamma 0.8351 -bgamma 1.0
After having found your favourite settings, you'll probably want to make them persistent. To do this go to '''System -> Preferences -> Startup Applications''', select the "Startup Programms" tab, click Add and add something like this
Name: xgamma
Command: xgamma -rgamma 0.8 -ggamma 0.8 -bgamma 1.0
(replace these values by your values) Click Add and then Close. Now these xgamma settings will be applied on each Gnome startup

== Setup Fingerprint Reader ==

Although thinkfinger can be installed from Lucid repos, it contains some regressions which
prevent fingerprint authentication from working properly. For more information check out
[https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 Bug #256429] Martin Schwenke
provides a PPA with the fixed version of thinkfinger which seems to work quite well.

To install thinkfinger open a terminal and run
sudo add-apt-repository ppa:martin-meltin/ppa
sudo apt-get update
sudo apt-get install libpam-thinkfinger=0.3+r118-0ubuntu4ppamartinmeltin5
sudo /usr/lib/pam-thinkfinger/pam-thinkfinger-enable
after that run
tf-tool --acquire $USERNAME
to acquire your fingerprint. Now you can use Z61m's fingerprint reader when using sudo/gksudo or in GDM login screen.

There seems to be a gnome-keyring related problem in Lucid when using fingerprint to log in. In that case Network Manager (nm-applet) may not appear in the panel or freeze when trying to change connection settings ([https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/529338 Bug #529338]). A known workaround is not to use fingerprint when logging in. You, however, still can use fingerprint for sudo, gksudo and all other supported authentication prompts.

== Setup Hard Drive Active Protection System ==
Open a terminal and run
sudo apt-get install tp-smapi-dkms
sudo apt-get install python python-gtk2 python-gnome2 hdapsd
Now run
sudo gedit /etc/modules
and add
tp_smapi
to the very end of the file so that it looks like this (example)
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
lp
tp_smapi

Reboot. Now HDAPS should work. If you want to have a HDAPS icon in your notification area
like in Windows, follow these steps to install [http://thpani.at/projects/thinkhdaps/ ThinkHDAPS]

Download [https://launchpad.net/~andypiperuk/+archive/andypiper-ppa/+files/thinkhdaps_0.2.1-1_all.deb https://launchpad.net/~andypiperuk/+archive/andypiper-ppa/+files/thinkhdaps_0.2.1-1_all.deb] and put it into your home directory. Right click on the file and select "Extract Here". In terminal run
cd ~
cd thinkhdaps_0.2.1-1_all
sudo cp
tar -zxvf data.tar.gz
sudo cp usr/bin/thinkhdaps /usr/bin/
sudo chmod +x /usr/bin/thinkhdaps
sudo cp usr/share/pixmaps/* /usr/share/pixmaps/

Now you can run
thinkhdaps &
to make the '''ThinkHDAPS''' icon appear in the notification area

[[File:ThinkHDAPS.png]]

To make it autostart go to '''System -> Preferences -> Startup Applications''', select the "Startup Programms" tab, click Add and add this
Name: thinkhdaps
Command: thinkhdaps
Click Add and then Close. Now the ThinkHDAPS icon should be always visible in the notification area.

To change the sensitivity run
sudo gedit /etc/default/hdapsd
and change the SENSITIVITY value. Default is 15 whereas higher values mean less sensitive. For example 25 seems to be just fine.

== Set up HDAPS accelerometer event ==
This section assumes you have set up tp_smapi (see [http://www.thinkwiki.org/wiki/Tp_smapi#Installation_on_Ubuntu_Lucid this page] for instructions).

To add the device rule (this worked for X61t, there is more info about the udev rule on [http://www.thinkwiki.org/wiki/Talk:HDAPS#Question_regarding_the_example_udev_rule_.3F the HDAPS Talk page])
echo 'KERNEL=="event[0-9]*", ATTRS{phys}=="hdaps/input1",ATTRS{modalias}=="input:b0019v1014p5054e4801-*",SYMLINK+="input/hdaps/accelerometer-event"' | sudo tee /etc/udev/rules.d/51-hdaps.rules
Then force the reloading of rules.d
sudo udevadm trigger
Now you should have a
/dev/input/hdaps/accelerometer-event

= Power Management =

== Fix the hard drive clicking bug ==
If you don't know what the hard drive clicking bug is, read [http://www.thinkwiki.org/wiki/Problem_with_hard_drive_clicking this]. Although this bug was apparently fixed in Ubuntu Karmic, Lucid seems to be affected.

{{WARN|Here is a solution that worked for me. It's a bit dirty and turns off the power management of your HDD. This will slightly decrease your battery life but greatly improve your drive's lifetime.}}
{{HINT|If you have a better solution, be sure to share it here}}

To fix the bug open a terminal and run
sudo cp /usr/lib/pm-utils/power.d/95hdparm-apm /etc/pm/power.d/
sudo gedit /etc/pm/power.d/95hdparm-apm

Insert "hdparm -B 254 /dev/sda" after "resume_hdparm_apm" so that the appropriate section looks like this

case "$1" in
thaw|resume|true|false) # true and false for power.d
resume_hdparm_apm
hdparm -B 254 /dev/sda
;;
*)
exit 254
;;
esac

To test the fix try suspending/resuming and plugging/unpluging AC power. After each process run
sudo hdparm -B /dev/sda
hdparm should always report

/dev/sda:
APM_level = 254

== Setup Fan Control ==

{{WARN|Wrong fan control settings may seriously damage you Thinkpad. You do it on your own risk!}}

To override BIOS fan control you can install '''ThinkPad Fan Control'''. Go to '''System -> Administration -> Synaptic Package Manager'''. Switch to the "Third Party Software" tab and click on "Add". As APT line add this
deb http://ppa.launchpad.net/tp-fan/ppa/ubuntu jaunty main
Click "Add Source" then "Close" and finally "Reload" as suggested. Now use "Synaptic Package Manager" to install following packages
tpfand tpfan-admin tpfand-profiles
Go to '''System -> Administration -> ThinkPad Fan Control''' and click on "Unlock". Select "Control system fan by software" and you're done.

It's also possible to define your own fan control rules thus overriding the default settings. To do this select "Manually configure system fan trigger temperatures". Here is an example for a Z61m with Core2Duo T5500 and GMA 950.
Models with discrete graphics (like FireGL) will probably need lower threshholds as they usually produce more heat and thus require better cooling.

[[File:Screenshot-ThinkPad_Fan_Control_Configuration.png]]

{{HELP|Did someone else experience this problem and test the workaround?}}

Sometimes ThinkPad Fan Control's daemon '''tpfand''' crashes for unknown reasons causing software fan control to stop working (i.e. BIOS starts controlling the fan). It seems that this problem is somehow HAL related, since tpfand relies on HAL for determining the ThinkPad's model. If the detection routine fails, '''tpfand''' stops immediately(see [https://bugs.launchpad.net/tp-fan/+bug/575199 Bug #575199]). A quick and dirty solution is to tweak this detection by editing tpfand's settings.py
sudo gedit /usr/lib/python2.6/dist-packages/tpfand/settings.py
and replacing
self.product_id = None
self.product_name = None
self.product_pretty_vendor = None
self.product_pretty_name = None
self.product_pretty_id = None
by
self.product_id = ''
self.product_name = ''
self.product_pretty_vendor = ''
self.product_pretty_name = ''
self.product_pretty_id = ''
this will prevent '''tpfand''' from crashing even if it wasn't able to detect your ThinkPad's model.

== Configure Battery Charge Control ==

In a terminal run
sudo apt-get install sysfsutils
sudo apt-get install tp-smapi-dkms

Now run
sudo gedit /etc/modules
and add
tp_smapi
to the very end of the file. Run
sudo gedit /etc/sysfs.conf
and add
devices/platform/smapi/BAT0/start_charge_thresh=85
devices/platform/smapi/BAT0/stop_charge_thresh=96
to the very end of the file. Save and reboot. With this values your battery will start charging at 80% and stop charging at 96%. Of course you can also put other values between 1 and 100.

To check the current thresholds run
cat /sys/devices/platform/smapi/BAT0/start_charge_thresh
and
cat /sys/devices/platform/smapi/BAT0/stop_charge_thresh

= External Sources =
*[http://wiki.ubuntuusers.de/Trackpoint] Trackpoint Configuration (wiki.ubuntuusers.de)
*[http://fedoraproject.org/wiki/Features/ColorManagement] Gnome Color Manager (fedoraproject.org)
*[http://www.ubuntufieldmanual.com/?q=node/38] Calibrate your monitor (Ubuntu Field Manual)

Installing Ubuntu 10.04 (Lucid Lynx) on a ThinkPad Z61m

2010-07-12T02:21:30Z

Tripwired: /* Set up HDAPS accelerometer event */

= Installing from USB stick=

If you already use Ubuntu 9.10 Karmic, installing Ubuntu 10.04 from USB stick is very easy. Just download the [http://www.ubuntu.com/getubuntu/download latest ISO], plug the USB stick in and run System-->Administration-->Create a USB startup disk. Load the downloaded ISO and hit "Make Startup Disk". For more information check [https://help.ubuntu.com/community/Installation/FromUSBStick#Creating%20a%20bootable%20USB%20Drive this page]. After that reboot your Thinkpad and press F12. This will allow you to boot from USB stick and start the installation routine.

= Tested Configuration =
* Lenovo ThinkPad {{Z61m}} (9450-H9G)
** [[Intel Core 2 Duo]] T5500 (1,66 GHz, 2 MB L2, 667MHz FSB)
** 2 GB RAM (2x 1 GB [[PC2-5300]] DDR2 667MHz)
** 15.4" wide-screen TFT WXGA 1280x800
** [[Intel Graphics Media Accelerator 950]]
** Seagate Momentus 7200.3 ST9160411ASG (160 GB SATA 7200 RPM) [http://www.thinkwiki.org/wiki/Talk:Problem_with_hard_drive_clicking reflashed to Dell OEM Firmware]
** Ultrabay Enhanced DVD±RW Burner (GMA-4082N, FRU 39T2723)
** Intel HD Audio with [[AD1981HD]] codec
** [[Broadcom Gigabit Ethernet (10/100/1000)]]
** [[ThinkPad Bluetooth with Enhanced Data Rate (BDC-2)]]
** [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter]]
** [[IrDA]] 1.1 (FIR - 4Mbps)
** [[SD_Card_slot|4-in-1 digital media reader]] (MultiMedia Card, MemoryStick, SD)
** [[Integrated Fingerprint Reader]]
** [[ThinkLight]]
** [[UltraNav]]
** [[CardBus]] slot (Type 2)
** [[ExpressCard slot]] (54 or 34)
** [[UltraBay|UltraBay Enhanced]]
** 3x USB 2.0, Firewire, VGA out, S-Video out, Headphone Jack, Microphone Jack
** Built-in Microphone

= Hardware Support =

{| border="2"
|Device / Function
|Works?
|Comment
|-
|Suspend & Hibernate
|{{Cyes}}
|out of the box
|-
|Intel GMA950 2D and 3D
|{{Cyes}}
|out of the box
|-
|Intel 3945ABG WiFi
|{{Cyes}}
|out of the box
|-
|Bluetooth
|{{Cyes}}
|out of the box
|-
|Broadcom Gigabit Ethernet
|{{Cyes}}
|out of the box
|-
|DVD±RW Burner
|{{Cyes}}
|out of the box
|-
|Ultrabay Hotswapping
|{{Cpart}}
|hotswapping optical drives (like DVD±RW) works out of the box, for HDD hotswapping [http://www.thinkwiki.org/wiki/How_to_hotswap_Ultrabay_devices#Using_libata-acpi_and_udev look here]
|-
|Hard Drive Active Protection System
|{{Cyes}}
|must be activated and configured. [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_%28Lucid_Lynx%29_on_a_ThinkPad_Z61m#Setup_Hard_Drive_Active_Protection_System See here]

|-
|Intel HDA Sound
|{{Cyes}}
|out of the box, modem must be enabled in BIOS
|-
|PCMCIA
|{{Cyes}}
|out of the box
|-
|Express Card
|{{Cunk}} (should work)
|not tested
|-
|TPM
|{{Cunk}} (should work)
|not tested, for further information check out these links [http://die-klapsmuehle.org/2009/01/29/how-to-use-a-tpm-with-ubuntu/], [https://www.grounation.org/index.php?post/2008/07/04/8-how-to-use-a-tpm-with-linux]
|-
|Firewire
|{{Cunk}} (should work)
|not tested
|-
|USB
|{{Cyes}}
|out of the box
|-
|IRDA
|{{Cunk}} (should work)
|not tested
|-
|Docking
|{{Cunk}} (should work)
|not tested
|-
|Fingerprint Reader
|{{Cyes}}
|works with ThinkFinger. [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_%28Lucid_Lynx%29_on_a_ThinkPad_Z61m#Setup_Fingerprint_Reader See here]
|-
|VGA out
|{{Cyes}}
|out of the box
|-
|S-Video out
|{{Cpart}}
|a 100 Hz Sony TV was recognized as a 30 Hz TV, poor picture
|-
|Modem
|{{Cunk}}
|not tested
|-
|Microphone
|{{Cyes}}
|both internal and external mics work out of the box, but are muted by default. See bellow
|-
|Headphones
|{{Cyes}}
|out of the box
|-
|Touchpad
|{{Cyes}}
|out of the box
|-
|Trackpoint
|{{Cyes}}
|out of the box, to enable middle button scrolling see bellow
|-
|Multimedia Card Reader
|{{Cyes}}?
|works out of the box with all kinds of SD cards. No other cards have been tested
|-
|{{key|Fn}}{{key|Fx}}, {{key|Fn}}{{key|PageUp}}, {{key|Fn}}{{key|Home}}, {{key|Fn}}{{key|End}}
|{{Cyes}}
|out of the box, except of {{key|Fn}}{{key|F9}} and {{key|Fn}}{{key|Space}}. For configuring {{key|Fn}}{{key|Space}} [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_%28Lucid_Lynx%29_on_a_ThinkPad_Z61m#Make_Fn-Space_.28Screen_Magnify.29_work see here]
|-
|{{key|Fn}}{{key|Up}}, {{key|Fn}}{{key|Down}}, {{key|Fn}}{{key|Left}}, {{key|Fn}}{{key|Right}}
|{{Cpart}}
|depends on the player, works out of the box with Rhytmbox but not Audacious. Thus, needs additional configuration
|-
|{{ibmkey|ThinkVantage|#495988}}
|{{Cyes}}
|does nothing by default, but can be easily mapped to something useful. [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_%28Lucid_Lynx%29_on_a_ThinkPad_Z61m#Map_ThinkVantage_Button See here]
|-
|{{ibmkey|Volume up|#494949}}, {{ibmkey|Volume down|#494949}}, {{ibmkey|Volume mute|#494949}}
|{{Cpart}}
|the volume buttons work but don't affect the software (Pulse Audio) mixer. For possible workarounds [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_%28Lucid_Lynx%29_on_a_ThinkPad_Z61m#Workaround_for_the_Volume_Buttons see here]
|-
|Back and Forward keys (near the arrow keys)
|{{Cyes}}
|out of the box
|-
|{{key|Fn}}{{key|Space}} (Screen Magnify)
|{{Cyes}}
|requires some acpi hacking. [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_%28Lucid_Lynx%29_on_a_ThinkPad_Z61m#Make_Fn-Space_.28Screen_Magnify.29_work See here]
|}

[[Category:Z61m]]

= HOWTOS =

== Setup the Middle Button Scrolling ==

Start a terminal and run

sudo gedit /usr/lib/X11/xorg.conf.d/20-trackpoint.conf

paste this

Section "InputClass"
Identifier "Trackpoint"
MatchProduct "TPPS/2 IBM TrackPoint|DualPoint Stick|Synaptics Inc. Composite TouchPad / TrackPoint"
MatchDevicePath "/dev/input/event*"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
Option "EmulateWheelTimeout" "200"
Option "Emulate3Buttons" "false"
Option "YAxisMapping" "4 5"
Option "XAxisMapping" "6 7"
EndSection

and save. Reboot.

== Configure Trackpoint and Touchpad ==
The most convenient way to do this is to install GPointing Device Settings via
sudo apt-get install gpointing-device-settings
After that you will find it in System -> Preferences -> Pointing Devices

[[image:Screenshot-GPointing Device Settings-TrackPoint.png]]

GPointing Device Settings, however, can't configure such important Trackpoint settings as sensitivity, speed and press to select. To do this, open a terminal, run
sudo apt-get install sysfsutils
sudo gedit /etc/rc.local
paste

for i in 1 2 3
do
if [ -d /sys/devices/platform/i8042/serio1/serio$i ]; then
echo -n 200 > /sys/devices/platform/i8042/serio1/serio$i/speed
echo -n 150 > /sys/devices/platform/i8042/serio1/serio$i/sensitivity
echo -n 1 > /sys/devices/platform/i8042/serio1/serio$i/press_to_select
fi
done

before
exit 0
and save. This will set sensitivity to 200, speed to 150 and activate press to select. Replacing "echo -n 1" by "echo -n 0" in the file will deactivate press to select. To find the right speed and sensitivity values, you should do some tests before by issuing
echo -n 200 | sudo tee /sys/devices/platform/i8042/serio1/serio?/sensitivity
echo -n 150 | sudo tee /sys/devices/platform/i8042/serio1/serio?/speed
in the terminal and using different numerical values between 0 and 255. The default values are 128 for sensitivity and 97 for speed.

== Workaround for the Volume Buttons ==

Volume buttons work but don't control software mixer settings. Thus you effectively get two volume scales completely independent from each other: Ubuntu's software mixer and Z61m's hardware mixer. That's confusing and inconvenient but as of 2010-05-05 (see [https://bugs.launchpad.net/ubuntu/+source/linux/+bug/357673 Bug #357673]) still unfixed.

=== Possible Workaround #1 ===

A simple workaround is to set hardware volume control to an acceptable level and not to use those volume buttons afterwards. Instead, you can use the software mixer only. It's easy to configure {{key|Win}}{{key|F1}} and {{key|Win}}{{key|F2}} which are not used in Ubuntu by default to act as volume buttons for the software mixer. To do this go to '''System -> Preferenced -> Keyboard shortcuts''', click on "Volume Down" and press {{key|Win}}{{key|F1}}. Now click on "Volume Up" and press {{key|Win}}{{key|F2}}. If you also need mute, you can define {{key|Win}}{{key|1}} for that. The changes will be applied immediately.

[[File:Screenshot-Keyboard_Shortcuts.png]]

=== Possible Workaround #2 ===

If you still want to use volume keys for volume control, you should run
sudo gedit /etc/rc.local
and add this before "exit 0"
cp /sys/devices/platform/thinkpad_acpi/hotkey_all_mask /sys/devices/platform/thinkpad_acpi/hotkey_mask
This solution is still not really acceptable because it uses a quite weird volume scale resulting in maximum loudness already on 50% of the software mixer. If you've already applied workaround #1, be sure to map "Volume Up" and "Volume Down" back to the Thinkpad volume keys

== Make Fn-Space (Screen Magnify) work ==

Open a terminal and run
sudo apt-get install kmag
sudo gedit /etc/acpi/events/asus-rotate
replace it's content by the following
# /etc/acpi/events/ibmwireless
# This is called when the user presses Fn-Space
event=ibm/hotkey HKEY 00000080 00001014
action=/etc/acpi/ibm-zoom.sh
and save. Now run
sudo cp /etc/acpi/ibm-wireless.sh /etc/acpi/ibm-zoom.sh
sudo gedit /etc/acpi/ibm-zoom.sh
and replace its content by the following
#!/bin/sh
#
# This script activates gnome-mag when Fn+Space is pressed
test -f /usr/share/acpi-support/key-constants || exit 0
. /usr/share/acpi-support/power-funcs
magnifier_pid=`pidof kmag`
for x in /tmp/.X11-unix/*; do
displaynum=`echo $x | sed s#/tmp/.X11-unix/X##`
getXconsole;
if [ x"$XAUTHORITY" != x"" ]; then
export DISPLAY=":$displaynum"
if [ "$magnifier_pid" != "" ]; then
/usr/bin/killall kmag
break
else
/usr/bin/kmag &
break
fi
fi
done
Save and reboot. Now when pressing Fn-Space you can open KMagnifier. Pressing Fn-Space once again will close KMagnifier. You can configure KMagnifier as you like and your settings will be saved automatically

== Map ThinkVantage Button ==
ThinkVantage Button is recognized but is not mapped to any function so that pressing it does nothing. To change this go to '''System->Preferences-> Keyboard shortcuts'''. There you can look for some predefined actions ThinkVantage Button might do for you. To map the button to a certain action simply click on the action and press {{ibmkey|ThinkVantage|#495988}}. Via Add you can also add your own commands, for instance to start your browser or e-mail client.

== Setup External Monitor or Beamer (VGA) ==

Connect your monitor/beamer to VGA port and go to '''System -> Preferences -> Monitors'''. For quick access to those settings it might be useful to activate "Show monitors in panel".

[[File:Lucid_ext_Monitor_new.png]]

You can also use this to configure an external device connected to S-Video Out.

[[File:Z61m_svideo.JPG]]

== Setup Color Management ==
To use ICC/ICM profiles you should install [http://projects.gnome.org/gnome-color-manager/ GNOME Color Manager] via
sudo apt-get install gnome-color-manager
After that it should appear under '''System -> Preferences -> Color Profiles'''. Alternatively you can start it from the terminal by issuing
gcm-prefs
GCM should detect your Thinkpad monitor automatically. All you need to do is supply the correct ICC/ICM profile by clicking on the list under '''Color Profile''' and selecting '''Other profile ...'''

[[File:CMgment.jpg]]

Lenovo does supply ICM profiles for most Thinkpads, but in order to open the appropriate .exe-archive under Linux you'll need Wine. Install Wine by running
sudo apt-get install wine
After that download [http://www-307.ibm.com/pc/support/site.wss/migr-62923.html 79oi22ww.exe] and right-click the file. Go to the '''Properties''' tab and tick '''Allow executing file as program''' In the '''Open With''' tab select '''Wine Windows Program Loader''' and close the dialog. Now double-click 79oi22ww.exe, and hit Next -> I accept the agreement -> Next -> Next -> Install -> Finish. Using Nautilus go to "~/.wine/drive_c/DRIVERS/WIN/MONITOR". There you'll find different ICM profiles which can be used by GCM. '''TPFLX.icm''' is for [http://www.thinkwiki.org/wiki/Flexview#Flexview_.28IPS.29 FlexView] panels whereas '''TPMB60.ICM''' and '''TPMB72.ICM''' are for [http://www.thinkwiki.org/wiki/Flexview#MaxBright MaxBright] panels. If you have only a plain TFT panel (not MaxBright) then stick to '''TPLCD.icm'''.

After importing the appropriate profile to GCM and selecting it, be sure to go to '''Defaults''' tab and select '''Apply display correction''' and '''Set profile for color managed applications''' Unfortunately, GCM doesn't seem to support manual adjustments of gamma, brightness or contrast on Thinkpad displays.

At least adjusting gamma is possible when using '''xgamma'''. In a terminal run
xgamma
to see you current gamma settings. You should see something like
-> Red 1.000, Green 1.000, Blue 1.000
It is possible to adjust gamma values for all colors at the same time by issuing something like
xgamma -gamma 0.9
or for red, green and blue separately
xgamma -rgamma 0.815 -ggamma 0.844 -bgamma 1.0
If you want to be able to relate RGB gamma values to a certain colour temperature, take a look at [http://www.vendian.org/mncharity/dir3/blackbody/UnstableURLs/bbr_color.html this page by Mitchell Charity]. Thus, to get something like 7800K you'll have to issue
xgamma -rgamma 0.8115 -ggamma 0.8351 -bgamma 1.0
After having found your favourite settings, you'll probably want to make them persistent. To do this go to '''System -> Preferences -> Startup Applications''', select the "Startup Programms" tab, click Add and add something like this
Name: xgamma
Command: xgamma -rgamma 0.8 -ggamma 0.8 -bgamma 1.0
(replace these values by your values) Click Add and then Close. Now these xgamma settings will be applied on each Gnome startup

== Setup Fingerprint Reader ==

Although thinkfinger can be installed from Lucid repos, it contains some regressions which
prevent fingerprint authentication from working properly. For more information check out
[https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 Bug #256429] Martin Schwenke
provides a PPA with the fixed version of thinkfinger which seems to work quite well.

To install thinkfinger open a terminal and run
sudo add-apt-repository ppa:martin-meltin/ppa
sudo apt-get update
sudo apt-get install libpam-thinkfinger=0.3+r118-0ubuntu4ppamartinmeltin5
sudo /usr/lib/pam-thinkfinger/pam-thinkfinger-enable
after that run
tf-tool --acquire $USERNAME
to acquire your fingerprint. Now you can use Z61m's fingerprint reader when using sudo/gksudo or in GDM login screen.

There seems to be a gnome-keyring related problem in Lucid when using fingerprint to log in. In that case Network Manager (nm-applet) may not appear in the panel or freeze when trying to change connection settings ([https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/529338 Bug #529338]). A known workaround is not to use fingerprint when logging in. You, however, still can use fingerprint for sudo, gksudo and all other supported authentication prompts.

== Setup Hard Drive Active Protection System ==
Open a terminal and run
sudo apt-get install tp-smapi-dkms
sudo apt-get install python python-gtk2 python-gnome2 hdapsd
Now run
sudo gedit /etc/modules
and add
tp_smapi
to the very end of the file so that it looks like this (example)
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
lp
tp_smapi

Reboot. Now HDAPS should work. If you want to have a HDAPS icon in your notification area
like in Windows, follow these steps to install [http://thpani.at/projects/thinkhdaps/ ThinkHDAPS]

Download [https://launchpad.net/~andypiperuk/+archive/andypiper-ppa/+files/thinkhdaps_0.2.1-1_all.deb https://launchpad.net/~andypiperuk/+archive/andypiper-ppa/+files/thinkhdaps_0.2.1-1_all.deb] and put it into your home directory. Right click on the file and select "Extract Here". In terminal run
cd ~
cd thinkhdaps_0.2.1-1_all
sudo cp
tar -zxvf data.tar.gz
sudo cp usr/bin/thinkhdaps /usr/bin/
sudo chmod +x /usr/bin/thinkhdaps
sudo cp usr/share/pixmaps/* /usr/share/pixmaps/

Now you can run
thinkhdaps &
to make the '''ThinkHDAPS''' icon appear in the notification area

[[File:ThinkHDAPS.png]]

To make it autostart go to '''System -> Preferences -> Startup Applications''', select the "Startup Programms" tab, click Add and add this
Name: thinkhdaps
Command: thinkhdaps
Click Add and then Close. Now the ThinkHDAPS icon should be always visible in the notification area.

To change the sensitivity run
sudo gedit /etc/default/hdapsd
and change the SENSITIVITY value. Default is 15 whereas higher values mean less sensitive. For example 25 seems to be just fine.

== Set up HDAPS accelerometer event ==
This section assumes you have set up tp_smapi (see [http://www.thinkwiki.org/wiki/Tp_smapi#Installation_on_Ubuntu_Lucid this page] for instructions).

To add the device rule (this worked for X61t, for more info about the udev rule see [http://www.thinkwiki.org/wiki/Talk:HDAPS#Question_regarding_the_example_udev_rule_.3F])
echo 'KERNEL=="event[0-9]*", ATTRS{phys}=="hdaps/input1",ATTRS{modalias}=="input:b0019v1014p5054e4801-*",SYMLINK+="input/hdaps/accelerometer-event"' | sudo tee /etc/udev/rules.d/51-hdaps.rules
Then force the reloading of rules.d
sudo udevadm trigger
Now you should have a
/dev/input/hdaps/accelerometer-event

= Power Management =

== Fix the hard drive clicking bug ==
If you don't know what the hard drive clicking bug is, read [http://www.thinkwiki.org/wiki/Problem_with_hard_drive_clicking this]. Although this bug was apparently fixed in Ubuntu Karmic, Lucid seems to be affected.

{{WARN|Here is a solution that worked for me. It's a bit dirty and turns off the power management of your HDD. This will slightly decrease your battery life but greatly improve your drive's lifetime.}}
{{HINT|If you have a better solution, be sure to share it here}}

To fix the bug open a terminal and run
sudo cp /usr/lib/pm-utils/power.d/95hdparm-apm /etc/pm/power.d/
sudo gedit /etc/pm/power.d/95hdparm-apm

Insert "hdparm -B 254 /dev/sda" after "resume_hdparm_apm" so that the appropriate section looks like this

case "$1" in
thaw|resume|true|false) # true and false for power.d
resume_hdparm_apm
hdparm -B 254 /dev/sda
;;
*)
exit 254
;;
esac

To test the fix try suspending/resuming and plugging/unpluging AC power. After each process run
sudo hdparm -B /dev/sda
hdparm should always report

/dev/sda:
APM_level = 254

== Setup Fan Control ==

{{WARN|Wrong fan control settings may seriously damage you Thinkpad. You do it on your own risk!}}

To override BIOS fan control you can install '''ThinkPad Fan Control'''. Go to '''System -> Administration -> Synaptic Package Manager'''. Switch to the "Third Party Software" tab and click on "Add". As APT line add this
deb http://ppa.launchpad.net/tp-fan/ppa/ubuntu jaunty main
Click "Add Source" then "Close" and finally "Reload" as suggested. Now use "Synaptic Package Manager" to install following packages
tpfand tpfan-admin tpfand-profiles
Go to '''System -> Administration -> ThinkPad Fan Control''' and click on "Unlock". Select "Control system fan by software" and you're done.

It's also possible to define your own fan control rules thus overriding the default settings. To do this select "Manually configure system fan trigger temperatures". Here is an example for a Z61m with Core2Duo T5500 and GMA 950.
Models with discrete graphics (like FireGL) will probably need lower threshholds as they usually produce more heat and thus require better cooling.

[[File:Screenshot-ThinkPad_Fan_Control_Configuration.png]]

{{HELP|Did someone else experience this problem and test the workaround?}}

Sometimes ThinkPad Fan Control's daemon '''tpfand''' crashes for unknown reasons causing software fan control to stop working (i.e. BIOS starts controlling the fan). It seems that this problem is somehow HAL related, since tpfand relies on HAL for determining the ThinkPad's model. If the detection routine fails, '''tpfand''' stops immediately(see [https://bugs.launchpad.net/tp-fan/+bug/575199 Bug #575199]). A quick and dirty solution is to tweak this detection by editing tpfand's settings.py
sudo gedit /usr/lib/python2.6/dist-packages/tpfand/settings.py
and replacing
self.product_id = None
self.product_name = None
self.product_pretty_vendor = None
self.product_pretty_name = None
self.product_pretty_id = None
by
self.product_id = ''
self.product_name = ''
self.product_pretty_vendor = ''
self.product_pretty_name = ''
self.product_pretty_id = ''
this will prevent '''tpfand''' from crashing even if it wasn't able to detect your ThinkPad's model.

== Configure Battery Charge Control ==

In a terminal run
sudo apt-get install sysfsutils
sudo apt-get install tp-smapi-dkms

Now run
sudo gedit /etc/modules
and add
tp_smapi
to the very end of the file. Run
sudo gedit /etc/sysfs.conf
and add
devices/platform/smapi/BAT0/start_charge_thresh=85
devices/platform/smapi/BAT0/stop_charge_thresh=96
to the very end of the file. Save and reboot. With this values your battery will start charging at 80% and stop charging at 96%. Of course you can also put other values between 1 and 100.

To check the current thresholds run
cat /sys/devices/platform/smapi/BAT0/start_charge_thresh
and
cat /sys/devices/platform/smapi/BAT0/stop_charge_thresh

= External Sources =
*[http://wiki.ubuntuusers.de/Trackpoint] Trackpoint Configuration (wiki.ubuntuusers.de)
*[http://fedoraproject.org/wiki/Features/ColorManagement] Gnome Color Manager (fedoraproject.org)
*[http://www.ubuntufieldmanual.com/?q=node/38] Calibrate your monitor (Ubuntu Field Manual)

Installing Ubuntu 10.04 (Lucid Lynx) on a ThinkPad Z61m

2010-07-12T02:20:40Z

Tripwired: /* Set up HDAPS accelerometer event */

= Installing from USB stick=

If you already use Ubuntu 9.10 Karmic, installing Ubuntu 10.04 from USB stick is very easy. Just download the [http://www.ubuntu.com/getubuntu/download latest ISO], plug the USB stick in and run System-->Administration-->Create a USB startup disk. Load the downloaded ISO and hit "Make Startup Disk". For more information check [https://help.ubuntu.com/community/Installation/FromUSBStick#Creating%20a%20bootable%20USB%20Drive this page]. After that reboot your Thinkpad and press F12. This will allow you to boot from USB stick and start the installation routine.

= Tested Configuration =
* Lenovo ThinkPad {{Z61m}} (9450-H9G)
** [[Intel Core 2 Duo]] T5500 (1,66 GHz, 2 MB L2, 667MHz FSB)
** 2 GB RAM (2x 1 GB [[PC2-5300]] DDR2 667MHz)
** 15.4" wide-screen TFT WXGA 1280x800
** [[Intel Graphics Media Accelerator 950]]
** Seagate Momentus 7200.3 ST9160411ASG (160 GB SATA 7200 RPM) [http://www.thinkwiki.org/wiki/Talk:Problem_with_hard_drive_clicking reflashed to Dell OEM Firmware]
** Ultrabay Enhanced DVD±RW Burner (GMA-4082N, FRU 39T2723)
** Intel HD Audio with [[AD1981HD]] codec
** [[Broadcom Gigabit Ethernet (10/100/1000)]]
** [[ThinkPad Bluetooth with Enhanced Data Rate (BDC-2)]]
** [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter]]
** [[IrDA]] 1.1 (FIR - 4Mbps)
** [[SD_Card_slot|4-in-1 digital media reader]] (MultiMedia Card, MemoryStick, SD)
** [[Integrated Fingerprint Reader]]
** [[ThinkLight]]
** [[UltraNav]]
** [[CardBus]] slot (Type 2)
** [[ExpressCard slot]] (54 or 34)
** [[UltraBay|UltraBay Enhanced]]
** 3x USB 2.0, Firewire, VGA out, S-Video out, Headphone Jack, Microphone Jack
** Built-in Microphone

= Hardware Support =

{| border="2"
|Device / Function
|Works?
|Comment
|-
|Suspend & Hibernate
|{{Cyes}}
|out of the box
|-
|Intel GMA950 2D and 3D
|{{Cyes}}
|out of the box
|-
|Intel 3945ABG WiFi
|{{Cyes}}
|out of the box
|-
|Bluetooth
|{{Cyes}}
|out of the box
|-
|Broadcom Gigabit Ethernet
|{{Cyes}}
|out of the box
|-
|DVD±RW Burner
|{{Cyes}}
|out of the box
|-
|Ultrabay Hotswapping
|{{Cpart}}
|hotswapping optical drives (like DVD±RW) works out of the box, for HDD hotswapping [http://www.thinkwiki.org/wiki/How_to_hotswap_Ultrabay_devices#Using_libata-acpi_and_udev look here]
|-
|Hard Drive Active Protection System
|{{Cyes}}
|must be activated and configured. [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_%28Lucid_Lynx%29_on_a_ThinkPad_Z61m#Setup_Hard_Drive_Active_Protection_System See here]

|-
|Intel HDA Sound
|{{Cyes}}
|out of the box, modem must be enabled in BIOS
|-
|PCMCIA
|{{Cyes}}
|out of the box
|-
|Express Card
|{{Cunk}} (should work)
|not tested
|-
|TPM
|{{Cunk}} (should work)
|not tested, for further information check out these links [http://die-klapsmuehle.org/2009/01/29/how-to-use-a-tpm-with-ubuntu/], [https://www.grounation.org/index.php?post/2008/07/04/8-how-to-use-a-tpm-with-linux]
|-
|Firewire
|{{Cunk}} (should work)
|not tested
|-
|USB
|{{Cyes}}
|out of the box
|-
|IRDA
|{{Cunk}} (should work)
|not tested
|-
|Docking
|{{Cunk}} (should work)
|not tested
|-
|Fingerprint Reader
|{{Cyes}}
|works with ThinkFinger. [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_%28Lucid_Lynx%29_on_a_ThinkPad_Z61m#Setup_Fingerprint_Reader See here]
|-
|VGA out
|{{Cyes}}
|out of the box
|-
|S-Video out
|{{Cpart}}
|a 100 Hz Sony TV was recognized as a 30 Hz TV, poor picture
|-
|Modem
|{{Cunk}}
|not tested
|-
|Microphone
|{{Cyes}}
|both internal and external mics work out of the box, but are muted by default. See bellow
|-
|Headphones
|{{Cyes}}
|out of the box
|-
|Touchpad
|{{Cyes}}
|out of the box
|-
|Trackpoint
|{{Cyes}}
|out of the box, to enable middle button scrolling see bellow
|-
|Multimedia Card Reader
|{{Cyes}}?
|works out of the box with all kinds of SD cards. No other cards have been tested
|-
|{{key|Fn}}{{key|Fx}}, {{key|Fn}}{{key|PageUp}}, {{key|Fn}}{{key|Home}}, {{key|Fn}}{{key|End}}
|{{Cyes}}
|out of the box, except of {{key|Fn}}{{key|F9}} and {{key|Fn}}{{key|Space}}. For configuring {{key|Fn}}{{key|Space}} [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_%28Lucid_Lynx%29_on_a_ThinkPad_Z61m#Make_Fn-Space_.28Screen_Magnify.29_work see here]
|-
|{{key|Fn}}{{key|Up}}, {{key|Fn}}{{key|Down}}, {{key|Fn}}{{key|Left}}, {{key|Fn}}{{key|Right}}
|{{Cpart}}
|depends on the player, works out of the box with Rhytmbox but not Audacious. Thus, needs additional configuration
|-
|{{ibmkey|ThinkVantage|#495988}}
|{{Cyes}}
|does nothing by default, but can be easily mapped to something useful. [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_%28Lucid_Lynx%29_on_a_ThinkPad_Z61m#Map_ThinkVantage_Button See here]
|-
|{{ibmkey|Volume up|#494949}}, {{ibmkey|Volume down|#494949}}, {{ibmkey|Volume mute|#494949}}
|{{Cpart}}
|the volume buttons work but don't affect the software (Pulse Audio) mixer. For possible workarounds [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_%28Lucid_Lynx%29_on_a_ThinkPad_Z61m#Workaround_for_the_Volume_Buttons see here]
|-
|Back and Forward keys (near the arrow keys)
|{{Cyes}}
|out of the box
|-
|{{key|Fn}}{{key|Space}} (Screen Magnify)
|{{Cyes}}
|requires some acpi hacking. [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_%28Lucid_Lynx%29_on_a_ThinkPad_Z61m#Make_Fn-Space_.28Screen_Magnify.29_work See here]
|}

[[Category:Z61m]]

= HOWTOS =

== Setup the Middle Button Scrolling ==

Start a terminal and run

sudo gedit /usr/lib/X11/xorg.conf.d/20-trackpoint.conf

paste this

Section "InputClass"
Identifier "Trackpoint"
MatchProduct "TPPS/2 IBM TrackPoint|DualPoint Stick|Synaptics Inc. Composite TouchPad / TrackPoint"
MatchDevicePath "/dev/input/event*"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
Option "EmulateWheelTimeout" "200"
Option "Emulate3Buttons" "false"
Option "YAxisMapping" "4 5"
Option "XAxisMapping" "6 7"
EndSection

and save. Reboot.

== Configure Trackpoint and Touchpad ==
The most convenient way to do this is to install GPointing Device Settings via
sudo apt-get install gpointing-device-settings
After that you will find it in System -> Preferences -> Pointing Devices

[[image:Screenshot-GPointing Device Settings-TrackPoint.png]]

GPointing Device Settings, however, can't configure such important Trackpoint settings as sensitivity, speed and press to select. To do this, open a terminal, run
sudo apt-get install sysfsutils
sudo gedit /etc/rc.local
paste

for i in 1 2 3
do
if [ -d /sys/devices/platform/i8042/serio1/serio$i ]; then
echo -n 200 > /sys/devices/platform/i8042/serio1/serio$i/speed
echo -n 150 > /sys/devices/platform/i8042/serio1/serio$i/sensitivity
echo -n 1 > /sys/devices/platform/i8042/serio1/serio$i/press_to_select
fi
done

before
exit 0
and save. This will set sensitivity to 200, speed to 150 and activate press to select. Replacing "echo -n 1" by "echo -n 0" in the file will deactivate press to select. To find the right speed and sensitivity values, you should do some tests before by issuing
echo -n 200 | sudo tee /sys/devices/platform/i8042/serio1/serio?/sensitivity
echo -n 150 | sudo tee /sys/devices/platform/i8042/serio1/serio?/speed
in the terminal and using different numerical values between 0 and 255. The default values are 128 for sensitivity and 97 for speed.

== Workaround for the Volume Buttons ==

Volume buttons work but don't control software mixer settings. Thus you effectively get two volume scales completely independent from each other: Ubuntu's software mixer and Z61m's hardware mixer. That's confusing and inconvenient but as of 2010-05-05 (see [https://bugs.launchpad.net/ubuntu/+source/linux/+bug/357673 Bug #357673]) still unfixed.

=== Possible Workaround #1 ===

A simple workaround is to set hardware volume control to an acceptable level and not to use those volume buttons afterwards. Instead, you can use the software mixer only. It's easy to configure {{key|Win}}{{key|F1}} and {{key|Win}}{{key|F2}} which are not used in Ubuntu by default to act as volume buttons for the software mixer. To do this go to '''System -> Preferenced -> Keyboard shortcuts''', click on "Volume Down" and press {{key|Win}}{{key|F1}}. Now click on "Volume Up" and press {{key|Win}}{{key|F2}}. If you also need mute, you can define {{key|Win}}{{key|1}} for that. The changes will be applied immediately.

[[File:Screenshot-Keyboard_Shortcuts.png]]

=== Possible Workaround #2 ===

If you still want to use volume keys for volume control, you should run
sudo gedit /etc/rc.local
and add this before "exit 0"
cp /sys/devices/platform/thinkpad_acpi/hotkey_all_mask /sys/devices/platform/thinkpad_acpi/hotkey_mask
This solution is still not really acceptable because it uses a quite weird volume scale resulting in maximum loudness already on 50% of the software mixer. If you've already applied workaround #1, be sure to map "Volume Up" and "Volume Down" back to the Thinkpad volume keys

== Make Fn-Space (Screen Magnify) work ==

Open a terminal and run
sudo apt-get install kmag
sudo gedit /etc/acpi/events/asus-rotate
replace it's content by the following
# /etc/acpi/events/ibmwireless
# This is called when the user presses Fn-Space
event=ibm/hotkey HKEY 00000080 00001014
action=/etc/acpi/ibm-zoom.sh
and save. Now run
sudo cp /etc/acpi/ibm-wireless.sh /etc/acpi/ibm-zoom.sh
sudo gedit /etc/acpi/ibm-zoom.sh
and replace its content by the following
#!/bin/sh
#
# This script activates gnome-mag when Fn+Space is pressed
test -f /usr/share/acpi-support/key-constants || exit 0
. /usr/share/acpi-support/power-funcs
magnifier_pid=`pidof kmag`
for x in /tmp/.X11-unix/*; do
displaynum=`echo $x | sed s#/tmp/.X11-unix/X##`
getXconsole;
if [ x"$XAUTHORITY" != x"" ]; then
export DISPLAY=":$displaynum"
if [ "$magnifier_pid" != "" ]; then
/usr/bin/killall kmag
break
else
/usr/bin/kmag &
break
fi
fi
done
Save and reboot. Now when pressing Fn-Space you can open KMagnifier. Pressing Fn-Space once again will close KMagnifier. You can configure KMagnifier as you like and your settings will be saved automatically

== Map ThinkVantage Button ==
ThinkVantage Button is recognized but is not mapped to any function so that pressing it does nothing. To change this go to '''System->Preferences-> Keyboard shortcuts'''. There you can look for some predefined actions ThinkVantage Button might do for you. To map the button to a certain action simply click on the action and press {{ibmkey|ThinkVantage|#495988}}. Via Add you can also add your own commands, for instance to start your browser or e-mail client.

== Setup External Monitor or Beamer (VGA) ==

Connect your monitor/beamer to VGA port and go to '''System -> Preferences -> Monitors'''. For quick access to those settings it might be useful to activate "Show monitors in panel".

[[File:Lucid_ext_Monitor_new.png]]

You can also use this to configure an external device connected to S-Video Out.

[[File:Z61m_svideo.JPG]]

== Setup Color Management ==
To use ICC/ICM profiles you should install [http://projects.gnome.org/gnome-color-manager/ GNOME Color Manager] via
sudo apt-get install gnome-color-manager
After that it should appear under '''System -> Preferences -> Color Profiles'''. Alternatively you can start it from the terminal by issuing
gcm-prefs
GCM should detect your Thinkpad monitor automatically. All you need to do is supply the correct ICC/ICM profile by clicking on the list under '''Color Profile''' and selecting '''Other profile ...'''

[[File:CMgment.jpg]]

Lenovo does supply ICM profiles for most Thinkpads, but in order to open the appropriate .exe-archive under Linux you'll need Wine. Install Wine by running
sudo apt-get install wine
After that download [http://www-307.ibm.com/pc/support/site.wss/migr-62923.html 79oi22ww.exe] and right-click the file. Go to the '''Properties''' tab and tick '''Allow executing file as program''' In the '''Open With''' tab select '''Wine Windows Program Loader''' and close the dialog. Now double-click 79oi22ww.exe, and hit Next -> I accept the agreement -> Next -> Next -> Install -> Finish. Using Nautilus go to "~/.wine/drive_c/DRIVERS/WIN/MONITOR". There you'll find different ICM profiles which can be used by GCM. '''TPFLX.icm''' is for [http://www.thinkwiki.org/wiki/Flexview#Flexview_.28IPS.29 FlexView] panels whereas '''TPMB60.ICM''' and '''TPMB72.ICM''' are for [http://www.thinkwiki.org/wiki/Flexview#MaxBright MaxBright] panels. If you have only a plain TFT panel (not MaxBright) then stick to '''TPLCD.icm'''.

After importing the appropriate profile to GCM and selecting it, be sure to go to '''Defaults''' tab and select '''Apply display correction''' and '''Set profile for color managed applications''' Unfortunately, GCM doesn't seem to support manual adjustments of gamma, brightness or contrast on Thinkpad displays.

At least adjusting gamma is possible when using '''xgamma'''. In a terminal run
xgamma
to see you current gamma settings. You should see something like
-> Red 1.000, Green 1.000, Blue 1.000
It is possible to adjust gamma values for all colors at the same time by issuing something like
xgamma -gamma 0.9
or for red, green and blue separately
xgamma -rgamma 0.815 -ggamma 0.844 -bgamma 1.0
If you want to be able to relate RGB gamma values to a certain colour temperature, take a look at [http://www.vendian.org/mncharity/dir3/blackbody/UnstableURLs/bbr_color.html this page by Mitchell Charity]. Thus, to get something like 7800K you'll have to issue
xgamma -rgamma 0.8115 -ggamma 0.8351 -bgamma 1.0
After having found your favourite settings, you'll probably want to make them persistent. To do this go to '''System -> Preferences -> Startup Applications''', select the "Startup Programms" tab, click Add and add something like this
Name: xgamma
Command: xgamma -rgamma 0.8 -ggamma 0.8 -bgamma 1.0
(replace these values by your values) Click Add and then Close. Now these xgamma settings will be applied on each Gnome startup

== Setup Fingerprint Reader ==

Although thinkfinger can be installed from Lucid repos, it contains some regressions which
prevent fingerprint authentication from working properly. For more information check out
[https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 Bug #256429] Martin Schwenke
provides a PPA with the fixed version of thinkfinger which seems to work quite well.

To install thinkfinger open a terminal and run
sudo add-apt-repository ppa:martin-meltin/ppa
sudo apt-get update
sudo apt-get install libpam-thinkfinger=0.3+r118-0ubuntu4ppamartinmeltin5
sudo /usr/lib/pam-thinkfinger/pam-thinkfinger-enable
after that run
tf-tool --acquire $USERNAME
to acquire your fingerprint. Now you can use Z61m's fingerprint reader when using sudo/gksudo or in GDM login screen.

There seems to be a gnome-keyring related problem in Lucid when using fingerprint to log in. In that case Network Manager (nm-applet) may not appear in the panel or freeze when trying to change connection settings ([https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/529338 Bug #529338]). A known workaround is not to use fingerprint when logging in. You, however, still can use fingerprint for sudo, gksudo and all other supported authentication prompts.

== Setup Hard Drive Active Protection System ==
Open a terminal and run
sudo apt-get install tp-smapi-dkms
sudo apt-get install python python-gtk2 python-gnome2 hdapsd
Now run
sudo gedit /etc/modules
and add
tp_smapi
to the very end of the file so that it looks like this (example)
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
lp
tp_smapi

Reboot. Now HDAPS should work. If you want to have a HDAPS icon in your notification area
like in Windows, follow these steps to install [http://thpani.at/projects/thinkhdaps/ ThinkHDAPS]

Download [https://launchpad.net/~andypiperuk/+archive/andypiper-ppa/+files/thinkhdaps_0.2.1-1_all.deb https://launchpad.net/~andypiperuk/+archive/andypiper-ppa/+files/thinkhdaps_0.2.1-1_all.deb] and put it into your home directory. Right click on the file and select "Extract Here". In terminal run
cd ~
cd thinkhdaps_0.2.1-1_all
sudo cp
tar -zxvf data.tar.gz
sudo cp usr/bin/thinkhdaps /usr/bin/
sudo chmod +x /usr/bin/thinkhdaps
sudo cp usr/share/pixmaps/* /usr/share/pixmaps/

Now you can run
thinkhdaps &
to make the '''ThinkHDAPS''' icon appear in the notification area

[[File:ThinkHDAPS.png]]

To make it autostart go to '''System -> Preferences -> Startup Applications''', select the "Startup Programms" tab, click Add and add this
Name: thinkhdaps
Command: thinkhdaps
Click Add and then Close. Now the ThinkHDAPS icon should be always visible in the notification area.

To change the sensitivity run
sudo gedit /etc/default/hdapsd
and change the SENSITIVITY value. Default is 15 whereas higher values mean less sensitive. For example 25 seems to be just fine.

== Set up HDAPS accelerometer event ==
This section assumes you have set up tp_smapi (see [http://www.thinkwiki.org/wiki/Tp_smapi#Installation_on_Ubuntu_Lucid] for instructions).

To add the device rule (this worked for X61t, for more info about the udev rule see [http://www.thinkwiki.org/wiki/Talk:HDAPS#Question_regarding_the_example_udev_rule_.3F])
echo 'KERNEL=="event[0-9]*", ATTRS{phys}=="hdaps/input1",ATTRS{modalias}=="input:b0019v1014p5054e4801-*",SYMLINK+="input/hdaps/accelerometer-event"' | sudo tee /etc/udev/rules.d/51-hdaps.rules
Then force the reloading of rules.d
sudo udevadm trigger
Now you should have a
/dev/input/hdaps/accelerometer-event

= Power Management =

== Fix the hard drive clicking bug ==
If you don't know what the hard drive clicking bug is, read [http://www.thinkwiki.org/wiki/Problem_with_hard_drive_clicking this]. Although this bug was apparently fixed in Ubuntu Karmic, Lucid seems to be affected.

{{WARN|Here is a solution that worked for me. It's a bit dirty and turns off the power management of your HDD. This will slightly decrease your battery life but greatly improve your drive's lifetime.}}
{{HINT|If you have a better solution, be sure to share it here}}

To fix the bug open a terminal and run
sudo cp /usr/lib/pm-utils/power.d/95hdparm-apm /etc/pm/power.d/
sudo gedit /etc/pm/power.d/95hdparm-apm

Insert "hdparm -B 254 /dev/sda" after "resume_hdparm_apm" so that the appropriate section looks like this

case "$1" in
thaw|resume|true|false) # true and false for power.d
resume_hdparm_apm
hdparm -B 254 /dev/sda
;;
*)
exit 254
;;
esac

To test the fix try suspending/resuming and plugging/unpluging AC power. After each process run
sudo hdparm -B /dev/sda
hdparm should always report

/dev/sda:
APM_level = 254

== Setup Fan Control ==

{{WARN|Wrong fan control settings may seriously damage you Thinkpad. You do it on your own risk!}}

To override BIOS fan control you can install '''ThinkPad Fan Control'''. Go to '''System -> Administration -> Synaptic Package Manager'''. Switch to the "Third Party Software" tab and click on "Add". As APT line add this
deb http://ppa.launchpad.net/tp-fan/ppa/ubuntu jaunty main
Click "Add Source" then "Close" and finally "Reload" as suggested. Now use "Synaptic Package Manager" to install following packages
tpfand tpfan-admin tpfand-profiles
Go to '''System -> Administration -> ThinkPad Fan Control''' and click on "Unlock". Select "Control system fan by software" and you're done.

It's also possible to define your own fan control rules thus overriding the default settings. To do this select "Manually configure system fan trigger temperatures". Here is an example for a Z61m with Core2Duo T5500 and GMA 950.
Models with discrete graphics (like FireGL) will probably need lower threshholds as they usually produce more heat and thus require better cooling.

[[File:Screenshot-ThinkPad_Fan_Control_Configuration.png]]

{{HELP|Did someone else experience this problem and test the workaround?}}

Sometimes ThinkPad Fan Control's daemon '''tpfand''' crashes for unknown reasons causing software fan control to stop working (i.e. BIOS starts controlling the fan). It seems that this problem is somehow HAL related, since tpfand relies on HAL for determining the ThinkPad's model. If the detection routine fails, '''tpfand''' stops immediately(see [https://bugs.launchpad.net/tp-fan/+bug/575199 Bug #575199]). A quick and dirty solution is to tweak this detection by editing tpfand's settings.py
sudo gedit /usr/lib/python2.6/dist-packages/tpfand/settings.py
and replacing
self.product_id = None
self.product_name = None
self.product_pretty_vendor = None
self.product_pretty_name = None
self.product_pretty_id = None
by
self.product_id = ''
self.product_name = ''
self.product_pretty_vendor = ''
self.product_pretty_name = ''
self.product_pretty_id = ''
this will prevent '''tpfand''' from crashing even if it wasn't able to detect your ThinkPad's model.

== Configure Battery Charge Control ==

In a terminal run
sudo apt-get install sysfsutils
sudo apt-get install tp-smapi-dkms

Now run
sudo gedit /etc/modules
and add
tp_smapi
to the very end of the file. Run
sudo gedit /etc/sysfs.conf
and add
devices/platform/smapi/BAT0/start_charge_thresh=85
devices/platform/smapi/BAT0/stop_charge_thresh=96
to the very end of the file. Save and reboot. With this values your battery will start charging at 80% and stop charging at 96%. Of course you can also put other values between 1 and 100.

To check the current thresholds run
cat /sys/devices/platform/smapi/BAT0/start_charge_thresh
and
cat /sys/devices/platform/smapi/BAT0/stop_charge_thresh

= External Sources =
*[http://wiki.ubuntuusers.de/Trackpoint] Trackpoint Configuration (wiki.ubuntuusers.de)
*[http://fedoraproject.org/wiki/Features/ColorManagement] Gnome Color Manager (fedoraproject.org)
*[http://www.ubuntufieldmanual.com/?q=node/38] Calibrate your monitor (Ubuntu Field Manual)

Installing Ubuntu 10.04 (Lucid Lynx) on a ThinkPad Z61m

2010-07-12T02:17:55Z

Tripwired: accelerometer event howto

= Installing from USB stick=

If you already use Ubuntu 9.10 Karmic, installing Ubuntu 10.04 from USB stick is very easy. Just download the [http://www.ubuntu.com/getubuntu/download latest ISO], plug the USB stick in and run System-->Administration-->Create a USB startup disk. Load the downloaded ISO and hit "Make Startup Disk". For more information check [https://help.ubuntu.com/community/Installation/FromUSBStick#Creating%20a%20bootable%20USB%20Drive this page]. After that reboot your Thinkpad and press F12. This will allow you to boot from USB stick and start the installation routine.

= Tested Configuration =
* Lenovo ThinkPad {{Z61m}} (9450-H9G)
** [[Intel Core 2 Duo]] T5500 (1,66 GHz, 2 MB L2, 667MHz FSB)
** 2 GB RAM (2x 1 GB [[PC2-5300]] DDR2 667MHz)
** 15.4" wide-screen TFT WXGA 1280x800
** [[Intel Graphics Media Accelerator 950]]
** Seagate Momentus 7200.3 ST9160411ASG (160 GB SATA 7200 RPM) [http://www.thinkwiki.org/wiki/Talk:Problem_with_hard_drive_clicking reflashed to Dell OEM Firmware]
** Ultrabay Enhanced DVD±RW Burner (GMA-4082N, FRU 39T2723)
** Intel HD Audio with [[AD1981HD]] codec
** [[Broadcom Gigabit Ethernet (10/100/1000)]]
** [[ThinkPad Bluetooth with Enhanced Data Rate (BDC-2)]]
** [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter]]
** [[IrDA]] 1.1 (FIR - 4Mbps)
** [[SD_Card_slot|4-in-1 digital media reader]] (MultiMedia Card, MemoryStick, SD)
** [[Integrated Fingerprint Reader]]
** [[ThinkLight]]
** [[UltraNav]]
** [[CardBus]] slot (Type 2)
** [[ExpressCard slot]] (54 or 34)
** [[UltraBay|UltraBay Enhanced]]
** 3x USB 2.0, Firewire, VGA out, S-Video out, Headphone Jack, Microphone Jack
** Built-in Microphone

= Hardware Support =

{| border="2"
|Device / Function
|Works?
|Comment
|-
|Suspend & Hibernate
|{{Cyes}}
|out of the box
|-
|Intel GMA950 2D and 3D
|{{Cyes}}
|out of the box
|-
|Intel 3945ABG WiFi
|{{Cyes}}
|out of the box
|-
|Bluetooth
|{{Cyes}}
|out of the box
|-
|Broadcom Gigabit Ethernet
|{{Cyes}}
|out of the box
|-
|DVD±RW Burner
|{{Cyes}}
|out of the box
|-
|Ultrabay Hotswapping
|{{Cpart}}
|hotswapping optical drives (like DVD±RW) works out of the box, for HDD hotswapping [http://www.thinkwiki.org/wiki/How_to_hotswap_Ultrabay_devices#Using_libata-acpi_and_udev look here]
|-
|Hard Drive Active Protection System
|{{Cyes}}
|must be activated and configured. [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_%28Lucid_Lynx%29_on_a_ThinkPad_Z61m#Setup_Hard_Drive_Active_Protection_System See here]

|-
|Intel HDA Sound
|{{Cyes}}
|out of the box, modem must be enabled in BIOS
|-
|PCMCIA
|{{Cyes}}
|out of the box
|-
|Express Card
|{{Cunk}} (should work)
|not tested
|-
|TPM
|{{Cunk}} (should work)
|not tested, for further information check out these links [http://die-klapsmuehle.org/2009/01/29/how-to-use-a-tpm-with-ubuntu/], [https://www.grounation.org/index.php?post/2008/07/04/8-how-to-use-a-tpm-with-linux]
|-
|Firewire
|{{Cunk}} (should work)
|not tested
|-
|USB
|{{Cyes}}
|out of the box
|-
|IRDA
|{{Cunk}} (should work)
|not tested
|-
|Docking
|{{Cunk}} (should work)
|not tested
|-
|Fingerprint Reader
|{{Cyes}}
|works with ThinkFinger. [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_%28Lucid_Lynx%29_on_a_ThinkPad_Z61m#Setup_Fingerprint_Reader See here]
|-
|VGA out
|{{Cyes}}
|out of the box
|-
|S-Video out
|{{Cpart}}
|a 100 Hz Sony TV was recognized as a 30 Hz TV, poor picture
|-
|Modem
|{{Cunk}}
|not tested
|-
|Microphone
|{{Cyes}}
|both internal and external mics work out of the box, but are muted by default. See bellow
|-
|Headphones
|{{Cyes}}
|out of the box
|-
|Touchpad
|{{Cyes}}
|out of the box
|-
|Trackpoint
|{{Cyes}}
|out of the box, to enable middle button scrolling see bellow
|-
|Multimedia Card Reader
|{{Cyes}}?
|works out of the box with all kinds of SD cards. No other cards have been tested
|-
|{{key|Fn}}{{key|Fx}}, {{key|Fn}}{{key|PageUp}}, {{key|Fn}}{{key|Home}}, {{key|Fn}}{{key|End}}
|{{Cyes}}
|out of the box, except of {{key|Fn}}{{key|F9}} and {{key|Fn}}{{key|Space}}. For configuring {{key|Fn}}{{key|Space}} [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_%28Lucid_Lynx%29_on_a_ThinkPad_Z61m#Make_Fn-Space_.28Screen_Magnify.29_work see here]
|-
|{{key|Fn}}{{key|Up}}, {{key|Fn}}{{key|Down}}, {{key|Fn}}{{key|Left}}, {{key|Fn}}{{key|Right}}
|{{Cpart}}
|depends on the player, works out of the box with Rhytmbox but not Audacious. Thus, needs additional configuration
|-
|{{ibmkey|ThinkVantage|#495988}}
|{{Cyes}}
|does nothing by default, but can be easily mapped to something useful. [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_%28Lucid_Lynx%29_on_a_ThinkPad_Z61m#Map_ThinkVantage_Button See here]
|-
|{{ibmkey|Volume up|#494949}}, {{ibmkey|Volume down|#494949}}, {{ibmkey|Volume mute|#494949}}
|{{Cpart}}
|the volume buttons work but don't affect the software (Pulse Audio) mixer. For possible workarounds [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_%28Lucid_Lynx%29_on_a_ThinkPad_Z61m#Workaround_for_the_Volume_Buttons see here]
|-
|Back and Forward keys (near the arrow keys)
|{{Cyes}}
|out of the box
|-
|{{key|Fn}}{{key|Space}} (Screen Magnify)
|{{Cyes}}
|requires some acpi hacking. [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_%28Lucid_Lynx%29_on_a_ThinkPad_Z61m#Make_Fn-Space_.28Screen_Magnify.29_work See here]
|}

[[Category:Z61m]]

= HOWTOS =

== Setup the Middle Button Scrolling ==

Start a terminal and run

sudo gedit /usr/lib/X11/xorg.conf.d/20-trackpoint.conf

paste this

Section "InputClass"
Identifier "Trackpoint"
MatchProduct "TPPS/2 IBM TrackPoint|DualPoint Stick|Synaptics Inc. Composite TouchPad / TrackPoint"
MatchDevicePath "/dev/input/event*"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
Option "EmulateWheelTimeout" "200"
Option "Emulate3Buttons" "false"
Option "YAxisMapping" "4 5"
Option "XAxisMapping" "6 7"
EndSection

and save. Reboot.

== Configure Trackpoint and Touchpad ==
The most convenient way to do this is to install GPointing Device Settings via
sudo apt-get install gpointing-device-settings
After that you will find it in System -> Preferences -> Pointing Devices

[[image:Screenshot-GPointing Device Settings-TrackPoint.png]]

GPointing Device Settings, however, can't configure such important Trackpoint settings as sensitivity, speed and press to select. To do this, open a terminal, run
sudo apt-get install sysfsutils
sudo gedit /etc/rc.local
paste

for i in 1 2 3
do
if [ -d /sys/devices/platform/i8042/serio1/serio$i ]; then
echo -n 200 > /sys/devices/platform/i8042/serio1/serio$i/speed
echo -n 150 > /sys/devices/platform/i8042/serio1/serio$i/sensitivity
echo -n 1 > /sys/devices/platform/i8042/serio1/serio$i/press_to_select
fi
done

before
exit 0
and save. This will set sensitivity to 200, speed to 150 and activate press to select. Replacing "echo -n 1" by "echo -n 0" in the file will deactivate press to select. To find the right speed and sensitivity values, you should do some tests before by issuing
echo -n 200 | sudo tee /sys/devices/platform/i8042/serio1/serio?/sensitivity
echo -n 150 | sudo tee /sys/devices/platform/i8042/serio1/serio?/speed
in the terminal and using different numerical values between 0 and 255. The default values are 128 for sensitivity and 97 for speed.

== Workaround for the Volume Buttons ==

Volume buttons work but don't control software mixer settings. Thus you effectively get two volume scales completely independent from each other: Ubuntu's software mixer and Z61m's hardware mixer. That's confusing and inconvenient but as of 2010-05-05 (see [https://bugs.launchpad.net/ubuntu/+source/linux/+bug/357673 Bug #357673]) still unfixed.

=== Possible Workaround #1 ===

A simple workaround is to set hardware volume control to an acceptable level and not to use those volume buttons afterwards. Instead, you can use the software mixer only. It's easy to configure {{key|Win}}{{key|F1}} and {{key|Win}}{{key|F2}} which are not used in Ubuntu by default to act as volume buttons for the software mixer. To do this go to '''System -> Preferenced -> Keyboard shortcuts''', click on "Volume Down" and press {{key|Win}}{{key|F1}}. Now click on "Volume Up" and press {{key|Win}}{{key|F2}}. If you also need mute, you can define {{key|Win}}{{key|1}} for that. The changes will be applied immediately.

[[File:Screenshot-Keyboard_Shortcuts.png]]

=== Possible Workaround #2 ===

If you still want to use volume keys for volume control, you should run
sudo gedit /etc/rc.local
and add this before "exit 0"
cp /sys/devices/platform/thinkpad_acpi/hotkey_all_mask /sys/devices/platform/thinkpad_acpi/hotkey_mask
This solution is still not really acceptable because it uses a quite weird volume scale resulting in maximum loudness already on 50% of the software mixer. If you've already applied workaround #1, be sure to map "Volume Up" and "Volume Down" back to the Thinkpad volume keys

== Make Fn-Space (Screen Magnify) work ==

Open a terminal and run
sudo apt-get install kmag
sudo gedit /etc/acpi/events/asus-rotate
replace it's content by the following
# /etc/acpi/events/ibmwireless
# This is called when the user presses Fn-Space
event=ibm/hotkey HKEY 00000080 00001014
action=/etc/acpi/ibm-zoom.sh
and save. Now run
sudo cp /etc/acpi/ibm-wireless.sh /etc/acpi/ibm-zoom.sh
sudo gedit /etc/acpi/ibm-zoom.sh
and replace its content by the following
#!/bin/sh
#
# This script activates gnome-mag when Fn+Space is pressed
test -f /usr/share/acpi-support/key-constants || exit 0
. /usr/share/acpi-support/power-funcs
magnifier_pid=`pidof kmag`
for x in /tmp/.X11-unix/*; do
displaynum=`echo $x | sed s#/tmp/.X11-unix/X##`
getXconsole;
if [ x"$XAUTHORITY" != x"" ]; then
export DISPLAY=":$displaynum"
if [ "$magnifier_pid" != "" ]; then
/usr/bin/killall kmag
break
else
/usr/bin/kmag &
break
fi
fi
done
Save and reboot. Now when pressing Fn-Space you can open KMagnifier. Pressing Fn-Space once again will close KMagnifier. You can configure KMagnifier as you like and your settings will be saved automatically

== Map ThinkVantage Button ==
ThinkVantage Button is recognized but is not mapped to any function so that pressing it does nothing. To change this go to '''System->Preferences-> Keyboard shortcuts'''. There you can look for some predefined actions ThinkVantage Button might do for you. To map the button to a certain action simply click on the action and press {{ibmkey|ThinkVantage|#495988}}. Via Add you can also add your own commands, for instance to start your browser or e-mail client.

== Setup External Monitor or Beamer (VGA) ==

Connect your monitor/beamer to VGA port and go to '''System -> Preferences -> Monitors'''. For quick access to those settings it might be useful to activate "Show monitors in panel".

[[File:Lucid_ext_Monitor_new.png]]

You can also use this to configure an external device connected to S-Video Out.

[[File:Z61m_svideo.JPG]]

== Setup Color Management ==
To use ICC/ICM profiles you should install [http://projects.gnome.org/gnome-color-manager/ GNOME Color Manager] via
sudo apt-get install gnome-color-manager
After that it should appear under '''System -> Preferences -> Color Profiles'''. Alternatively you can start it from the terminal by issuing
gcm-prefs
GCM should detect your Thinkpad monitor automatically. All you need to do is supply the correct ICC/ICM profile by clicking on the list under '''Color Profile''' and selecting '''Other profile ...'''

[[File:CMgment.jpg]]

Lenovo does supply ICM profiles for most Thinkpads, but in order to open the appropriate .exe-archive under Linux you'll need Wine. Install Wine by running
sudo apt-get install wine
After that download [http://www-307.ibm.com/pc/support/site.wss/migr-62923.html 79oi22ww.exe] and right-click the file. Go to the '''Properties''' tab and tick '''Allow executing file as program''' In the '''Open With''' tab select '''Wine Windows Program Loader''' and close the dialog. Now double-click 79oi22ww.exe, and hit Next -> I accept the agreement -> Next -> Next -> Install -> Finish. Using Nautilus go to "~/.wine/drive_c/DRIVERS/WIN/MONITOR". There you'll find different ICM profiles which can be used by GCM. '''TPFLX.icm''' is for [http://www.thinkwiki.org/wiki/Flexview#Flexview_.28IPS.29 FlexView] panels whereas '''TPMB60.ICM''' and '''TPMB72.ICM''' are for [http://www.thinkwiki.org/wiki/Flexview#MaxBright MaxBright] panels. If you have only a plain TFT panel (not MaxBright) then stick to '''TPLCD.icm'''.

After importing the appropriate profile to GCM and selecting it, be sure to go to '''Defaults''' tab and select '''Apply display correction''' and '''Set profile for color managed applications''' Unfortunately, GCM doesn't seem to support manual adjustments of gamma, brightness or contrast on Thinkpad displays.

At least adjusting gamma is possible when using '''xgamma'''. In a terminal run
xgamma
to see you current gamma settings. You should see something like
-> Red 1.000, Green 1.000, Blue 1.000
It is possible to adjust gamma values for all colors at the same time by issuing something like
xgamma -gamma 0.9
or for red, green and blue separately
xgamma -rgamma 0.815 -ggamma 0.844 -bgamma 1.0
If you want to be able to relate RGB gamma values to a certain colour temperature, take a look at [http://www.vendian.org/mncharity/dir3/blackbody/UnstableURLs/bbr_color.html this page by Mitchell Charity]. Thus, to get something like 7800K you'll have to issue
xgamma -rgamma 0.8115 -ggamma 0.8351 -bgamma 1.0
After having found your favourite settings, you'll probably want to make them persistent. To do this go to '''System -> Preferences -> Startup Applications''', select the "Startup Programms" tab, click Add and add something like this
Name: xgamma
Command: xgamma -rgamma 0.8 -ggamma 0.8 -bgamma 1.0
(replace these values by your values) Click Add and then Close. Now these xgamma settings will be applied on each Gnome startup

== Setup Fingerprint Reader ==

Although thinkfinger can be installed from Lucid repos, it contains some regressions which
prevent fingerprint authentication from working properly. For more information check out
[https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 Bug #256429] Martin Schwenke
provides a PPA with the fixed version of thinkfinger which seems to work quite well.

To install thinkfinger open a terminal and run
sudo add-apt-repository ppa:martin-meltin/ppa
sudo apt-get update
sudo apt-get install libpam-thinkfinger=0.3+r118-0ubuntu4ppamartinmeltin5
sudo /usr/lib/pam-thinkfinger/pam-thinkfinger-enable
after that run
tf-tool --acquire $USERNAME
to acquire your fingerprint. Now you can use Z61m's fingerprint reader when using sudo/gksudo or in GDM login screen.

There seems to be a gnome-keyring related problem in Lucid when using fingerprint to log in. In that case Network Manager (nm-applet) may not appear in the panel or freeze when trying to change connection settings ([https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/529338 Bug #529338]). A known workaround is not to use fingerprint when logging in. You, however, still can use fingerprint for sudo, gksudo and all other supported authentication prompts.

== Setup Hard Drive Active Protection System ==
Open a terminal and run
sudo apt-get install tp-smapi-dkms
sudo apt-get install python python-gtk2 python-gnome2 hdapsd
Now run
sudo gedit /etc/modules
and add
tp_smapi
to the very end of the file so that it looks like this (example)
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
lp
tp_smapi

Reboot. Now HDAPS should work. If you want to have a HDAPS icon in your notification area
like in Windows, follow these steps to install [http://thpani.at/projects/thinkhdaps/ ThinkHDAPS]

Download [https://launchpad.net/~andypiperuk/+archive/andypiper-ppa/+files/thinkhdaps_0.2.1-1_all.deb https://launchpad.net/~andypiperuk/+archive/andypiper-ppa/+files/thinkhdaps_0.2.1-1_all.deb] and put it into your home directory. Right click on the file and select "Extract Here". In terminal run
cd ~
cd thinkhdaps_0.2.1-1_all
sudo cp
tar -zxvf data.tar.gz
sudo cp usr/bin/thinkhdaps /usr/bin/
sudo chmod +x /usr/bin/thinkhdaps
sudo cp usr/share/pixmaps/* /usr/share/pixmaps/

Now you can run
thinkhdaps &
to make the '''ThinkHDAPS''' icon appear in the notification area

[[File:ThinkHDAPS.png]]

To make it autostart go to '''System -> Preferences -> Startup Applications''', select the "Startup Programms" tab, click Add and add this
Name: thinkhdaps
Command: thinkhdaps
Click Add and then Close. Now the ThinkHDAPS icon should be always visible in the notification area.

To change the sensitivity run
sudo gedit /etc/default/hdapsd
and change the SENSITIVITY value. Default is 15 whereas higher values mean less sensitive. For example 25 seems to be just fine.

== Set up HDAPS accelerometer event ==
To add the device rule (this worked for X61t, for more info about the udev rule see [http://www.thinkwiki.org/wiki/Talk:HDAPS#Question_regarding_the_example_udev_rule_.3F])
echo 'KERNEL=="event[0-9]*", ATTRS{phys}=="hdaps/input1",ATTRS{modalias}=="input:b0019v1014p5054e4801-*",SYMLINK+="input/hdaps/accelerometer-event"' | sudo tee /etc/udev/rules.d/51-hdaps.rules
Then force the reloading of rules.d
sudo udevadm trigger
Now you should have a
/dev/input/hdaps/accelerometer-event

= Power Management =

== Fix the hard drive clicking bug ==
If you don't know what the hard drive clicking bug is, read [http://www.thinkwiki.org/wiki/Problem_with_hard_drive_clicking this]. Although this bug was apparently fixed in Ubuntu Karmic, Lucid seems to be affected.

{{WARN|Here is a solution that worked for me. It's a bit dirty and turns off the power management of your HDD. This will slightly decrease your battery life but greatly improve your drive's lifetime.}}
{{HINT|If you have a better solution, be sure to share it here}}

To fix the bug open a terminal and run
sudo cp /usr/lib/pm-utils/power.d/95hdparm-apm /etc/pm/power.d/
sudo gedit /etc/pm/power.d/95hdparm-apm

Insert "hdparm -B 254 /dev/sda" after "resume_hdparm_apm" so that the appropriate section looks like this

case "$1" in
thaw|resume|true|false) # true and false for power.d
resume_hdparm_apm
hdparm -B 254 /dev/sda
;;
*)
exit 254
;;
esac

To test the fix try suspending/resuming and plugging/unpluging AC power. After each process run
sudo hdparm -B /dev/sda
hdparm should always report

/dev/sda:
APM_level = 254

== Setup Fan Control ==

{{WARN|Wrong fan control settings may seriously damage you Thinkpad. You do it on your own risk!}}

To override BIOS fan control you can install '''ThinkPad Fan Control'''. Go to '''System -> Administration -> Synaptic Package Manager'''. Switch to the "Third Party Software" tab and click on "Add". As APT line add this
deb http://ppa.launchpad.net/tp-fan/ppa/ubuntu jaunty main
Click "Add Source" then "Close" and finally "Reload" as suggested. Now use "Synaptic Package Manager" to install following packages
tpfand tpfan-admin tpfand-profiles
Go to '''System -> Administration -> ThinkPad Fan Control''' and click on "Unlock". Select "Control system fan by software" and you're done.

It's also possible to define your own fan control rules thus overriding the default settings. To do this select "Manually configure system fan trigger temperatures". Here is an example for a Z61m with Core2Duo T5500 and GMA 950.
Models with discrete graphics (like FireGL) will probably need lower threshholds as they usually produce more heat and thus require better cooling.

[[File:Screenshot-ThinkPad_Fan_Control_Configuration.png]]

{{HELP|Did someone else experience this problem and test the workaround?}}

Sometimes ThinkPad Fan Control's daemon '''tpfand''' crashes for unknown reasons causing software fan control to stop working (i.e. BIOS starts controlling the fan). It seems that this problem is somehow HAL related, since tpfand relies on HAL for determining the ThinkPad's model. If the detection routine fails, '''tpfand''' stops immediately(see [https://bugs.launchpad.net/tp-fan/+bug/575199 Bug #575199]). A quick and dirty solution is to tweak this detection by editing tpfand's settings.py
sudo gedit /usr/lib/python2.6/dist-packages/tpfand/settings.py
and replacing
self.product_id = None
self.product_name = None
self.product_pretty_vendor = None
self.product_pretty_name = None
self.product_pretty_id = None
by
self.product_id = ''
self.product_name = ''
self.product_pretty_vendor = ''
self.product_pretty_name = ''
self.product_pretty_id = ''
this will prevent '''tpfand''' from crashing even if it wasn't able to detect your ThinkPad's model.

== Configure Battery Charge Control ==

In a terminal run
sudo apt-get install sysfsutils
sudo apt-get install tp-smapi-dkms

Now run
sudo gedit /etc/modules
and add
tp_smapi
to the very end of the file. Run
sudo gedit /etc/sysfs.conf
and add
devices/platform/smapi/BAT0/start_charge_thresh=85
devices/platform/smapi/BAT0/stop_charge_thresh=96
to the very end of the file. Save and reboot. With this values your battery will start charging at 80% and stop charging at 96%. Of course you can also put other values between 1 and 100.

To check the current thresholds run
cat /sys/devices/platform/smapi/BAT0/start_charge_thresh
and
cat /sys/devices/platform/smapi/BAT0/stop_charge_thresh

= External Sources =
*[http://wiki.ubuntuusers.de/Trackpoint] Trackpoint Configuration (wiki.ubuntuusers.de)
*[http://fedoraproject.org/wiki/Features/ColorManagement] Gnome Color Manager (fedoraproject.org)
*[http://www.ubuntufieldmanual.com/?q=node/38] Calibrate your monitor (Ubuntu Field Manual)