ThinkWiki - User contributions [en]

How to enable the integrated fingerprint reader with ThinkFinger

2011-01-17T21:29:29Z

Vegar: /* Fix for the fingerprint reader getting too hot */ Cleanup of the fix-section

[[How to enable the fingerprint reader]] has a good explanation for using the fingerprint reader with the closed-source binary driver. But there is also an opensource project called [http://thinkfinger.sourceforge.net ThinkFinger] which does the same, but open.

However: The fingerprint reader is an INSECURE device and gives a false sense of security! There has been quite a bit of research by a hacker named Starbug, a member of the Chaos Computer Club, Berlin, Germany. He outlined in two very good talks how to forge each and every available fingerprint sensor available at the cost of a few euros, using materials from your local hardware store, a digicam and a laser printer! Here's some links:
* [http://www.ccc.de/updates/2007/umsonst-im-supermarkt?language=en Fingerprint recognition in supermarkets]
* [ftp://ftp.ccc.de/pub/documentation/Fingerabdruck_Hack/fingerabdruck.mpg Video tutorial for forging fingerprints]

'''NB:''' Thinkfinger is dead since two years. It was [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=546005 removed from debian] because of this.

== Installing ==
=== From source ===

Download thinkfinger-0.3.tar.gz from the [http://thinkfinger.sourceforge.net/ homepage] and unpack it somewhere, make sure you have the gcc compiler, libtool, pkg-config, libusb-dev and libpam0g-dev installed, then:

{{cmduser|cd thinkfinger-0.3}}

<code style="white-space:nowrap;color:#495988;background-color:white;"><nowiki>$</nowiki> ./configure --prefix=/usr --sysconfdir=/etc --with-securedir=/lib/security --with-birdir=/etc/pam_thinkfinger</code>

{{cmduser|make}}

{{cmdroot|make install}}

{{NOTE|/lib/security is the directory, where PAM assumes its modules on Debian and openSUSE, it may vary for your distro!}}

"make install" doesn't create the birdir we specified (where thinkfinger will store users' biometric info), so create it:

{{cmdroot|mkdir /etc/pam_thinkfinger}}

If everything went OK assert that you find pam_thinkfinger.so in /lib/security typing:

{{cmduser|ls /lib/security}}

=== From package ===

==== Debian ====
[http://packages.debian.org/source/experimental/thinkfinger Packages] arrived in Debian experimental on Aug 2nd, 2007 (cf. [http://bugs.debian.org/409563 bug #409563]). To access the experimental packages via apt, add the following lines to your sources.list:
<pre>
# experimental
deb ftp://mirrors.kernel.org/debian/ experimental main contrib non-free
deb-src ftp://mirrors.kernel.org/debian/ experimental main contrib non-free
</pre>
where of course you may replace mirrors.kernel.org with your mirror of choice. Just make sure that it hosts the experimental repositories.

{{cmdroot|aptitude update}}

{{cmdroot|aptitude install libthinkfinger0 libpam-thinkfinger thinkfinger-tools}}

should then get you up and running.

To make everything work you'll have to have permission to work the device ({{cmduser|sudo adduser myself plugdev}} worked for me), and you'll also have to follow instructions below about adding the device to your PAM methods.

==== Ubuntu ====

===== Gutsy =====

From https://wiki.ubuntu.com/ThinkFinger

Add PPA repositories to your sources.list:
<pre>
deb http://ppa.launchpad.net/jldugger/ubuntu gutsy main restricted universe multiverse
deb-src http://ppa.launchpad.net/jldugger/ubuntu gutsy main restricted universe multiverse
</pre>

Install necessary packages:

{{cmduser|sudo apt-get install thinkfinger-tools libpam-thinkfinger}}

===== Hardy =====

Hardy includes the latest thinkfinger and it is up to date with subversion. Install packages:

{{cmduser|sudo apt-get install thinkfinger-tools libpam-thinkfinger}}

Update the pam configuration files:

{{cmduser|sudo /usr/lib/pam-thinkfinger/pam-thinkfinger-enable}}

Enroll your fingerprint (creates $HOME/.thinkfinger.bir). If this gives an error about claiming the USB device then a reboot was claimed to work, but in fact it may just be a permissions problem. {{NOTE|Do not try to enroll using 'sudo' - it will cause hidden permission problems}}

{{cmduser|tf-tool --acquire}}

Check fingerprint enrollment

{{cmduser|tf-tool --verify}}

You can expect everything to work correctly. Note that you still have to enter your username if prompted but will be able
to swipe your finger instead of the password. The prompt will usually be "Password or swipe finger"

* Graphical login
* Text console login
* sudo
* screen lock/screen saver
* Administrative password prompt (eg for update or package managers). (Note no "or swipe finger" in prompt).

===== Intrepid =====
After installing from the normal repositories coming with Ubuntu 8.10, you would have to press enter after sweeping finger. (This bug: [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429])
Therefore Jon Oberheide made an update that can be found here:
[https://launchpad.net/~jon-oberheide/+archive https://launchpad.net/~jon-oberheide/+archive]
(As of 2/3/09, this no longer seems to be the case. Just proceed to the install step.)

Add the PPA repositories to your source.list (/etc/apt/source.list):
<pre>
deb http://ppa.launchpad.net/jon-oberheide/ubuntu intrepid main
deb-src http://ppa.launchpad.net/jon-oberheide/ubuntu intrepid main
</pre>

Update installer:

{{cmduser|sudo apt-get update}}

And install:

{{cmduser|sudo apt-get install thinkfinger-tools}}

===== Jaunty =====

The same package by Jon Oberheide is necessary, as with Intrepid, though the package thinkfinger-tools is installed by default.

Add key:

{{cmduser|sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com F2A12FABE936A7BBDC4EA33351DB180D1323E149}}

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

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

Update installer:

{{cmduser|sudo apt-get update}}

And install:

{{cmduser|sudo apt-get install thinkfinger-tools libpam-thinkfinger}}

===== Karmic =====

The syntax of udev rules is changed due to Karmic's new udev package. The correct rules should be:

<pre>
# SGS Thomson Microelectronics Fingerprint Reader
ENV{ID_VENDOR_ID}=="0483", ENV{ID_MODEL_ID}=="2016", SYMLINK+="input/thinkfinger-%k", MODE="0660", GROUP="fingerprint", ENV{GENERATED}="1"

# the also-needed uinput device
KERNEL=="uinput", MODE="0660", GROUP="fingerprint"
</pre>

Otherwise udev would accidentally change the ownership of /dev/null so that gdm would fail to start.

===== Lucid =====

From a working Karmic, upgrade to Lucid gave me a somewhat broken thinkfinger.

The scanner still works, but (in X windows) you need to hit "Enter" after doing a scan.
The scanner works fine while in terminal mode.

This is almost definitely because of the xorg version, see this message with no response for more info:
http://article.gmane.org/gmane.linux.drivers.thinkfinger/567

{{HINT|There is a PPA with working ThinkFinger for Lucid. At least it works fine on my Z61m. [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_(Lucid_Lynx)_on_a_ThinkPad_Z61m#Setup_Fingerprint_Reader See here] }}

{{HINT|ThinkFinger can be installed through Ubuntu Software Centre/Synaptic Package Manager/Terminal without special repositories enabled in Lucid. Search "ThinkFinger and install thinkfinger-tools (Synaptic/Software Centre), or type "sudo apt-get install thinkfinger-tools" (Terminal). }}

==== Fedora/Fedora Core ====
{{cmdroot|yum install thinkfinger}}

==== Gentoo ====
{{cmdroot|emerge sys-auth/thinkfinger}}

==== OpenSUSE ====
openSUSE 10.2 includes the package "libthinkfinger" (version 0.1-7) - you will find newer packages [http://beta1.suse.com/private/thoenig/10.2/thinkfinger/ here].

== Testing the driver ==

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

{{cmdroot|tf-tool --acquire}}

and

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

== Configuring PAM to use ThinkFinger ==
Now you can configure PAM to use ThinkFinger:

Open {{path|/etc/pam.d/common-auth}} (In FC6, F7, and Gentoo, this file is {{path|/etc/pam.d/system-auth}}):

{{cmdroot|nano -w /etc/pam.d/common-auth}}

Add this line before any pam_unix or pam_unix2 directives:
auth sufficient pam_thinkfinger.so

If your PAM uses the pam_unix and not the pam_unix2 module, you need to pass a specific argument in
the /etc/pam.d/common-auth directive to make it consider the password entered at the pam_thinkfinger prompt.
auth required pam_unix.so try_first_pass

For instance, {{path|/etc/pam.d/common-auth}} looks like this:
auth sufficient pam_thinkfinger.so
auth required pam_unix.so nullok_secure try_first_pass

On openSUSE 10.2, it looks like this now:
auth required pam_env.so
auth sufficient pam_thinkfinger.so
auth required pam_unix2.so

On Ubuntu 8.10 - Intrepid Ibex you should just add the following line the the /etc/pam.d/common-auth file so it looks like this:
<pre>
....
# here are the per-package modules (the "Primary" block)
auth sufficient pam_thinkfinger.so
auth [success=1 default=ignore] pam_unix.so try_first_pass nullok_secure
# here's the fallback if no module succeeds
....
</pre>

On Ubuntu 9.04, you don't need to edit manually, just type:

{{cmdroot|sudo /usr/lib/pam-thinkfinger/pam-thinkfinger-enable}}

Now we are ready to add users to thinkfinger. You can add a fingerprint for a user with:

{{cmdroot|tf-tool --acquire $USERNAME}}

{{NOTE|This may not work for you. Please read the Intrepid Ibex point in the discussion to this page.}}

Now the user should be able to login with his finger instead of the password.

If you would like to use thinkfinger for su, you have to enroll the fingerprint for root user with:

{{cmdroot|tf-tool --acquire root}}

{{NOTE|You should see the "Password or swipe finger:" prompt when trying to sudo or su. If you don't, you probably do not have the "User level driver support" compiled into your kernel or the "uinput" module loaded!}}

== xscreensaver/gnome-screensaver ==
{{NOTE|In Fedora 7, the package has been modified in such a way as to make doing this unnecessary.}}

If you'd like to be able to unlock your screen using the fingerprint reader, you must have current versions of xscreesaver (>~5.03) or gnome-screensaver (>~2.18.2). Then you must give yourself access to the fingerprint reader and your bir-file, because unlike login/gdm/su/sudo, both gnome-screensaver and xscreensaver do not run as root. The following procedure will make the fingerprint reader accessible to members of the "fingerprint" group.

Make the group: {{cmdroot|groupadd fingerprint}}

Save the following as {{path|/etc/udev/rules.d/60-thinkfinger.rules}} and run {{cmdroot|sudo /sbin/udevtrigger}}. If you are using a Debian-based distribution, it is likely you are affected by the following [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=489831 bug] where you need to replace {{path|udevtrigger}} with {{path|udevadm trigger}} (with the space!) in order for the following to work. You may need to reboot for this to take effect.
#
# udev rules file for the thinkfinger fingerprint scanner
#
# gives access to the fingerprint reader to those in the "fingerprint" group
#
# Taken from:
# http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
# which was taken and modified from:
# http://article.gmane.org/gmane.linux.drivers.thinkfinger/329
#

# SGS Thomson Microelectronics Fingerprint Reader
SYSFS{idVendor}=="0483", SYSFS{idProduct}=="2016", SYMLINK+="input/thinkfinger-%k", MODE="0660", GROUP="fingerprint"

# the also-needed uinput device
KERNEL=="uinput", MODE="0660", GROUP="fingerprint"

Finally, add the following lines at the end of {{path|/etc/pam.d/gnome-screensaver}}:
auth sufficient pam_thinkfinger.so
auth required pam_unix.so try_first_pass nullok_secure

Per user:

# Add him to the group: {{cmdroot|gpasswd -a $USERNAME fingerprint}}
{{NOTE|The following steps do not need to be done in Ubuntu Intrepid as the bir files are handled differently.}}
# Make him owner of his bir-file: {{cmdroot|chown $USERNAME:root /etc/pam_thinkfinger/$USERNAME.bir}}
# Give him read-only access to his bir-file: {{cmdroot|chmod 400 /etc/pam_thinkfinger/$USERNAME.bir}}
# Give "execute only" access to everyone for the /etc/pam_thinkfinger/ directory: {{cmdroot|chmod o+x /etc/pam_thinkfinger}} (WARNING: this opens up security a little).

== GNOME ==

{{NOTE|1=This problem should be solved if you're using sudo >= 1.6.9p9. Links: [http://savannah.nongnu.org/bugs/?19132], [http://www.sudo.ws/bugs/show_bug.cgi?id=180], [https://bugs.launchpad.net/ubuntu/+source/gksu/+bug/86843]}}

gksu/gksudo doesn't work correctly. It just stays invisible. When starting a su privileged application such as synaptics you will not get prompted for the password. Nevertheless you can swipe your finger and it should authenticate you. Starting synaptics twice makes gksudo visible.

There are two possibilities to solve it:
* Changing the string "Password or swipe finger:" to a plain "Password:" (like sudo normally would do) in the file pam/pam_thinkfinger.c of the thinkfinger source directory. Of course, in the console you will then only see a "Password:" instead of "Password or swipe finger:" but this is still more usefull than having gksu/gksudo crashing everytime.
* Patching libgksu with the following patch. This is also a nasty hack until a better solution is implemented.
<pre>
--- libgksu-2.0.3/libgksu/libgksu.c.orig 2007-06-17 16:00:24.000000000 +0200
+++ libgksu-2.0.3/libgksu/libgksu.c 2007-06-17 16:00:47.000000000 +0200
@@ -2663,7 +2663,7 @@
*/
for (counter = 0; counter < 50; counter++)
{
- if (strncmp (buffer, "GNOME_SUDO_PASS", 15) == 0)
+ if (strncmp (buffer, "GNOME_SUDO_PASS", 15) == 0 || strncmp (buffer, "Password or swi", 15) == 0)
break;

read_line (parent_pipe[0], buffer, 256);
@@ -2675,7 +2675,7 @@
if (context->debug)
fprintf (stderr, "brute force GNOME_SUDO_PASS ended...\n");

- if (strncmp(buffer, "GNOME_SUDO_PASS", 15) == 0)
+ if (strncmp(buffer, "GNOME_SUDO_PASS", 15) == 0 || strncmp(buffer, "Password or swi", 15) == 0)
{
gchar *password = NULL;
gboolean prompt_grab;
</pre>

== KDE ==

Integration in KDE and kdm seems not to be easily possible now. There is a filed [https://bugs.kde.org/show_bug.cgi?id=116682 bug] at kde.org where you can vote for this.

Moreover, kdm in openSUSE 10.3 and in Kubuntu 8.10 crashes when pam_thinkfinger is enabled. A possible "workaround" is downgrading to thinkfinger 0.2.2.

Another workaround is to use Fprint from [http://www.reactivated.net/fprint/wiki/Main_Page] which works quite nicely on my X61s and Kubuntu Hardy.

This Howto was copied from [[Installing Ubuntu 6.06 on a ThinkPad T43#Fingerprint_Reader]] and then slightly modified.

== Fix for the fingerprint reader getting too hot ==

If you notice that your fingerprint reader occasionally gets very hot then you might be interested in this section. Thanks to Tino Keitelon the linux-thinkpad mailing list for the solution.

=== Collect info ===
First we need to determine if the reader is not on autosuspend mode.
Open a terminal and run:

for i in `find /sys/devices/*/*/usb* -name level` ; do echo -n "$i: " ; cat $i ; done

We care about the devices that are with "on" state and we need to determine if one of those is the reader. So for each of those run something like:

cat /sys/devices/pci0000\:00/0000\:00\:1a.0/usb1/1-2/idVendor
0483

cat /sys/devices/pci0000\:00/0000\:00\:1a.0/usb1/1-2/idProduct
2016

Use the corresponding path of the devices that you got with "on" state and then compare the output with the output of the lsusb command. An example:

lsusb output: Bus 001 Device 004: ID 0483:2016 SGS Thomson Microelectronics Fingerprint Reader

Which matches the output above (0483:2016).

=== Enable autosuspend ===
Once you have determined the path of your reader then become root with su - and:

echo "auto" > /sys/<path-to-device>/power/level

Alternatively, if you're using Ubuntu:

echo auto | sudo tee /sys/<path-to-device>/power/level

After this, the fingerprint reader should be in "autosuspend" and will not get hot anymore. And it will still work as normal.

=== Making the changes permanent ===
The above will only work for the current session (until the next reboot). If you want to make the change persistent, do one of the following:
==== Using udev (recommended) ====
The simplest way to do this is to create a udev rule (requires no additional tools):

Put the following in {{path|/etc/udev/rules.d/69-fingerprint-sleep.rules}}

ATTR{idVendor}=="0483", ATTR{idProduct}=="2016", SUBSYSTEMS=="usb", ACTION=="add", ATTR{power/level}="auto"

(exchange 0483 and 2016 with what you found above if the numbers are different)
==== Using sysfsutils ====
Alternatively, if you have [http://linux-diag.sourceforge.net/Sysfsutils.html sysfsutils] installed, edit the file {{path|/etc/sysfs.conf}} and add the line

<path-to-device>/power/level = auto

Following the above example, that would be

devices/pci0000\:00/0000\:00\:1a.0/usb1/1-2/power/level = auto

==== Using init scripts ====
If, for some reason, neither of the two above methods don't work, you can install an init script:

sudo gedit /etc/init.d/ReaderNoMoreHot

Paste the following into it:

#!/bin/bash
#
echo "auto" > /sys/<path-to-device>/power/level

Save and close. Then:

sudo chmod 755 /etc/init.d/ReaderNoMoreHot
sudo update-rc.d ReaderNoMoreHot defaults 90

--[[User:Lunatico|Lunatico]] 19:19, 1 August 2008 (CEST), extended by --[[User:Michaelthomas h|Michaelthomas h]] 23:36, 9 August 2008 (CEST)

For the init script above, you can use the following more elaborate script, which does all the work for you of identifying the <path-to-device>. This can be useful since the USB device id can change under various circumstances (kernel upgrade etc).

<pre>
#!/bin/bash

# find the fingerprint reader and change its power level to autosuspend

usbname="SGS Thomson Microelectronics Fingerprint Reader"
usbid=$(lsusb |grep "$usbname" |cut -d' ' -f6);
[[ -z $usbid ]] && echo "USB Device \"$usbname\" not found" && exit 1

unset failed_bool
find /sys/devices/*/*/usb* -name idVendor -print | (
while read vfile; do
dir=$(dirname $vfile);
vendor=$(<$vfile);
product=$(<$dir/idProduct);
if [[ $vendor:$product = $usbid ]]; then
plevel_file=$dir/power/level
old_level=$(<$plevel_file);
[[ $old_level = auto ]] || echo auto >$plevel_file || failed_bool=1
break;
fi;
done
if [[ $failed_bool ]]; then
echo "Failed to set the fingerprint reader's power level to 'auto'."
exit 1
fi
)
</pre>

Here is an alternate script. The code is cleaner and it's about 20x faster (updated for jaunty):
<pre>
#!/bin/bash

# find the fingerprint reader and change its power level to autosuspend

find_manuf=STMicroelectronics
find_prod="Biometric Coprocessor"

for devdir in /sys/class/usb_*/*/device; do
[[ -r $devdir/manufacturer ]] || continue
manuf=$(<$devdir/manufacturer)
[[ $manuf = $find_manuf ]] || continue;
prod=$(<$devdir/product)
[[ $prod = $find_prod ]] || continue;
# if we get here then we have the right device!
plevel_file=$devdir/power/level
old_level=$(<$plevel_file);
# if it is already set properly then exit silently:
[[ $old_level = auto ]] && exit 0
# if we successfully change it then exit silently:
echo auto >$plevel_file && exit 0
echo "Failed to set the fingerprint reader's power level to 'auto'."
exit 1
done

# if we make it through the for loop without exiting, the search failed
echo "Could not find the $find_manuf $find_prod (fingerprint reader)"
exit 1
</pre>

How to enable the integrated fingerprint reader with ThinkFinger

2010-10-20T19:08:54Z

Vegar: /* Fix for the fingerprint reader getting too hot */

[[How to enable the fingerprint reader]] has a good explanation for using the fingerprint reader with the closed-source binary driver. But there is also an opensource project called [http://thinkfinger.sourceforge.net ThinkFinger] which does the same, but open.

However: The fingerprint reader is an INSECURE device and gives a false sense of security! There has been quite a bit of research by a hacker named Starbug, a member of the Chaos Computer Club, Berlin, Germany. He outlined in two very good talks how to forge each and every available fingerprint sensor available at the cost of a few euros, using materials from your local hardware store, a digicam and a laser printer! Here's some links:
* [http://www.ccc.de/updates/2007/umsonst-im-supermarkt?language=en Fingerprint recognition in supermarkets]
* [ftp://ftp.ccc.de/pub/documentation/Fingerabdruck_Hack/fingerabdruck.mpg Video tutorial for forging fingerprints]

'''NB:''' Thinkfinger is dead since two years. It was [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=546005 removed from debian] because of this.

== Installing ==
=== From source ===

Download thinkfinger-0.3.tar.gz from the [http://thinkfinger.sourceforge.net/ homepage] and unpack it somewhere, make sure you have the gcc compiler, libtool, pkg-config, libusb-dev and libpam0g-dev installed, then:

{{cmduser|cd thinkfinger-0.3}}

<code style="white-space:nowrap;color:#495988;background-color:white;"><nowiki>$</nowiki> ./configure --prefix=/usr --sysconfdir=/etc --with-securedir=/lib/security --with-birdir=/etc/pam_thinkfinger</code>

{{cmduser|make}}

{{cmdroot|make install}}

{{NOTE|/lib/security is the directory, where PAM assumes its modules on Debian and openSUSE, it may vary for your distro!}}

"make install" doesn't create the birdir we specified (where thinkfinger will store users' biometric info), so create it:

{{cmdroot|mkdir /etc/pam_thinkfinger}}

If everything went OK assert that you find pam_thinkfinger.so in /lib/security typing:

{{cmduser|ls /lib/security}}

=== From package ===

==== Debian ====
[http://packages.debian.org/source/experimental/thinkfinger Packages] arrived in Debian experimental on Aug 2nd, 2007 (cf. [http://bugs.debian.org/409563 bug #409563]). To access the experimental packages via apt, add the following lines to your sources.list:
<pre>
# experimental
deb ftp://mirrors.kernel.org/debian/ experimental main contrib non-free
deb-src ftp://mirrors.kernel.org/debian/ experimental main contrib non-free
</pre>
where of course you may replace mirrors.kernel.org with your mirror of choice. Just make sure that it hosts the experimental repositories.

{{cmdroot|aptitude update}}

{{cmdroot|aptitude install libthinkfinger0 libpam-thinkfinger thinkfinger-tools}}

should then get you up and running.

To make everything work you'll have to have permission to work the device ({{cmduser|sudo adduser myself plugdev}} worked for me), and you'll also have to follow instructions below about adding the device to your PAM methods.

==== Ubuntu ====

===== Gutsy =====

From https://wiki.ubuntu.com/ThinkFinger

Add PPA repositories to your sources.list:
<pre>
deb http://ppa.launchpad.net/jldugger/ubuntu gutsy main restricted universe multiverse
deb-src http://ppa.launchpad.net/jldugger/ubuntu gutsy main restricted universe multiverse
</pre>

Install necessary packages:

{{cmduser|sudo apt-get install thinkfinger-tools libpam-thinkfinger}}

===== Hardy =====

Hardy includes the latest thinkfinger and it is up to date with subversion. Install packages:

{{cmduser|sudo apt-get install thinkfinger-tools libpam-thinkfinger}}

Update the pam configuration files:

{{cmduser|sudo /usr/lib/pam-thinkfinger/pam-thinkfinger-enable}}

Enroll your fingerprint (creates $HOME/.thinkfinger.bir). If this gives an error about claiming the USB device then a reboot was claimed to work, but in fact it may just be a permissions problem. {{NOTE|Do not try to enroll using 'sudo' - it will cause hidden permission problems}}

{{cmduser|tf-tool --acquire}}

Check fingerprint enrollment

{{cmduser|tf-tool --verify}}

You can expect everything to work correctly. Note that you still have to enter your username if prompted but will be able
to swipe your finger instead of the password. The prompt will usually be "Password or swipe finger"

* Graphical login
* Text console login
* sudo
* screen lock/screen saver
* Administrative password prompt (eg for update or package managers). (Note no "or swipe finger" in prompt).

===== Intrepid =====
After installing from the normal repositories coming with Ubuntu 8.10, you would have to press enter after sweeping finger. (This bug: [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429])
Therefore Jon Oberheide made an update that can be found here:
[https://launchpad.net/~jon-oberheide/+archive https://launchpad.net/~jon-oberheide/+archive]
(As of 2/3/09, this no longer seems to be the case. Just proceed to the install step.)

Add the PPA repositories to your source.list (/etc/apt/source.list):
<pre>
deb http://ppa.launchpad.net/jon-oberheide/ubuntu intrepid main
deb-src http://ppa.launchpad.net/jon-oberheide/ubuntu intrepid main
</pre>

Update installer:

{{cmduser|sudo apt-get update}}

And install:

{{cmduser|sudo apt-get install thinkfinger-tools}}

===== Jaunty =====

The same package by Jon Oberheide is necessary, as with Intrepid, though the package thinkfinger-tools is installed by default.

Add key:

{{cmduser|sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com F2A12FABE936A7BBDC4EA33351DB180D1323E149}}

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

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

Update installer:

{{cmduser|sudo apt-get update}}

And install:

{{cmduser|sudo apt-get install thinkfinger-tools libpam-thinkfinger}}

===== Karmic =====

The syntax of udev rules is changed due to Karmic's new udev package. The correct rules should be:

<pre>
# SGS Thomson Microelectronics Fingerprint Reader
ENV{ID_VENDOR_ID}=="0483", ENV{ID_MODEL_ID}=="2016", SYMLINK+="input/thinkfinger-%k", MODE="0660", GROUP="fingerprint", ENV{GENERATED}="1"

# the also-needed uinput device
KERNEL=="uinput", MODE="0660", GROUP="fingerprint"
</pre>

Otherwise udev would accidentally change the ownership of /dev/null so that gdm would fail to start.

===== Lucid =====

From a working Karmic, upgrade to Lucid gave me a somewhat broken thinkfinger.

The scanner still works, but (in X windows) you need to hit "Enter" after doing a scan.
The scanner works fine while in terminal mode.

This is almost definitely because of the xorg version, see this message with no response for more info:
http://article.gmane.org/gmane.linux.drivers.thinkfinger/567

{{HINT|There is a PPA with working ThinkFinger for Lucid. At least it works fine on my Z61m. [http://www.thinkwiki.org/wiki/Installing_Ubuntu_10.04_(Lucid_Lynx)_on_a_ThinkPad_Z61m#Setup_Fingerprint_Reader See here] }}

{{HINT|ThinkFinger can be installed through Ubuntu Software Centre/Synaptic Package Manager/Terminal without special repositories enabled in Lucid. Search "ThinkFinger and install thinkfinger-tools (Synaptic/Software Centre), or type "sudo apt-get install thinkfinger-tools" (Terminal). }}

==== Fedora/Fedora Core ====
{{cmdroot|yum install thinkfinger}}

==== Gentoo ====
{{cmdroot|emerge sys-auth/thinkfinger}}

==== OpenSUSE ====
openSUSE 10.2 includes the package "libthinkfinger" (version 0.1-7) - you will find newer packages [http://beta1.suse.com/private/thoenig/10.2/thinkfinger/ here].

== Testing the driver ==

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

{{cmdroot|tf-tool --acquire}}

and

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

== Configuring PAM to use ThinkFinger ==
Now you can configure PAM to use ThinkFinger:

Open {{path|/etc/pam.d/common-auth}} (In FC6, F7, and Gentoo, this file is {{path|/etc/pam.d/system-auth}}):

{{cmdroot|nano -w /etc/pam.d/common-auth}}

Add this line before any pam_unix or pam_unix2 directives:
auth sufficient pam_thinkfinger.so

If your PAM uses the pam_unix and not the pam_unix2 module, you need to pass a specific argument in
the /etc/pam.d/common-auth directive to make it consider the password entered at the pam_thinkfinger prompt.
auth required pam_unix.so try_first_pass

For instance, {{path|/etc/pam.d/common-auth}} looks like this:
auth sufficient pam_thinkfinger.so
auth required pam_unix.so nullok_secure try_first_pass

On openSUSE 10.2, it looks like this now:
auth required pam_env.so
auth sufficient pam_thinkfinger.so
auth required pam_unix2.so

On Ubuntu 8.10 - Intrepid Ibex you should just add the following line the the /etc/pam.d/common-auth file so it looks like this:
<pre>
....
# here are the per-package modules (the "Primary" block)
auth sufficient pam_thinkfinger.so
auth [success=1 default=ignore] pam_unix.so try_first_pass nullok_secure
# here's the fallback if no module succeeds
....
</pre>

On Ubuntu 9.04, you don't need to edit manually, just type:

{{cmdroot|sudo /usr/lib/pam-thinkfinger/pam-thinkfinger-enable}}

Now we are ready to add users to thinkfinger. You can add a fingerprint for a user with:

{{cmdroot|tf-tool --acquire $USERNAME}}

{{NOTE|This may not work for you. Please read the Intrepid Ibex point in the discussion to this page.}}

Now the user should be able to login with his finger instead of the password.

If you would like to use thinkfinger for su, you have to enroll the fingerprint for root user with:

{{cmdroot|tf-tool --acquire root}}

{{NOTE|You should see the "Password or swipe finger:" prompt when trying to sudo or su. If you don't, you probably do not have the "User level driver support" compiled into your kernel or the "uinput" module loaded!}}

== xscreensaver/gnome-screensaver ==
{{NOTE|In Fedora 7, the package has been modified in such a way as to make doing this unnecessary.}}

If you'd like to be able to unlock your screen using the fingerprint reader, you must have current versions of xscreesaver (>~5.03) or gnome-screensaver (>~2.18.2). Then you must give yourself access to the fingerprint reader and your bir-file, because unlike login/gdm/su/sudo, both gnome-screensaver and xscreensaver do not run as root. The following procedure will make the fingerprint reader accessible to members of the "fingerprint" group.

Make the group: {{cmdroot|groupadd fingerprint}}

Save the following as {{path|/etc/udev/rules.d/60-thinkfinger.rules}} and run {{cmdroot|sudo /sbin/udevtrigger}}. If you are using a Debian-based distribution, it is likely you are affected by the following [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=489831 bug] where you need to replace {{path|udevtrigger}} with {{path|udevadm trigger}} (with the space!) in order for the following to work. You may need to reboot for this to take effect.
#
# udev rules file for the thinkfinger fingerprint scanner
#
# gives access to the fingerprint reader to those in the "fingerprint" group
#
# Taken from:
# http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
# which was taken and modified from:
# http://article.gmane.org/gmane.linux.drivers.thinkfinger/329
#

# SGS Thomson Microelectronics Fingerprint Reader
SYSFS{idVendor}=="0483", SYSFS{idProduct}=="2016", SYMLINK+="input/thinkfinger-%k", MODE="0660", GROUP="fingerprint"

# the also-needed uinput device
KERNEL=="uinput", MODE="0660", GROUP="fingerprint"

Finally, add the following lines at the end of {{path|/etc/pam.d/gnome-screensaver}}:
auth sufficient pam_thinkfinger.so
auth required pam_unix.so try_first_pass nullok_secure

Per user:

# Add him to the group: {{cmdroot|gpasswd -a $USERNAME fingerprint}}
{{NOTE|The following steps do not need to be done in Ubuntu Intrepid as the bir files are handled differently.}}
# Make him owner of his bir-file: {{cmdroot|chown $USERNAME:root /etc/pam_thinkfinger/$USERNAME.bir}}
# Give him read-only access to his bir-file: {{cmdroot|chmod 400 /etc/pam_thinkfinger/$USERNAME.bir}}
# Give "execute only" access to everyone for the /etc/pam_thinkfinger/ directory: {{cmdroot|chmod o+x /etc/pam_thinkfinger}} (WARNING: this opens up security a little).

== GNOME ==

{{NOTE|1=This problem should be solved if you're using sudo >= 1.6.9p9. Links: [http://savannah.nongnu.org/bugs/?19132], [http://www.sudo.ws/bugs/show_bug.cgi?id=180], [https://bugs.launchpad.net/ubuntu/+source/gksu/+bug/86843]}}

gksu/gksudo doesn't work correctly. It just stays invisible. When starting a su privileged application such as synaptics you will not get prompted for the password. Nevertheless you can swipe your finger and it should authenticate you. Starting synaptics twice makes gksudo visible.

There are two possibilities to solve it:
* Changing the string "Password or swipe finger:" to a plain "Password:" (like sudo normally would do) in the file pam/pam_thinkfinger.c of the thinkfinger source directory. Of course, in the console you will then only see a "Password:" instead of "Password or swipe finger:" but this is still more usefull than having gksu/gksudo crashing everytime.
* Patching libgksu with the following patch. This is also a nasty hack until a better solution is implemented.
<pre>
--- libgksu-2.0.3/libgksu/libgksu.c.orig 2007-06-17 16:00:24.000000000 +0200
+++ libgksu-2.0.3/libgksu/libgksu.c 2007-06-17 16:00:47.000000000 +0200
@@ -2663,7 +2663,7 @@
*/
for (counter = 0; counter < 50; counter++)
{
- if (strncmp (buffer, "GNOME_SUDO_PASS", 15) == 0)
+ if (strncmp (buffer, "GNOME_SUDO_PASS", 15) == 0 || strncmp (buffer, "Password or swi", 15) == 0)
break;

read_line (parent_pipe[0], buffer, 256);
@@ -2675,7 +2675,7 @@
if (context->debug)
fprintf (stderr, "brute force GNOME_SUDO_PASS ended...\n");

- if (strncmp(buffer, "GNOME_SUDO_PASS", 15) == 0)
+ if (strncmp(buffer, "GNOME_SUDO_PASS", 15) == 0 || strncmp(buffer, "Password or swi", 15) == 0)
{
gchar *password = NULL;
gboolean prompt_grab;
</pre>

== KDE ==

Integration in KDE and kdm seems not to be easily possible now. There is a filed [https://bugs.kde.org/show_bug.cgi?id=116682 bug] at kde.org where you can vote for this.

Moreover, kdm in openSUSE 10.3 and in Kubuntu 8.10 crashes when pam_thinkfinger is enabled. A possible "workaround" is downgrading to thinkfinger 0.2.2.

Another workaround is to use Fprint from [http://www.reactivated.net/fprint/wiki/Main_Page] which works quite nicely on my X61s and Kubuntu Hardy.

This Howto was copied from [[Installing Ubuntu 6.06 on a ThinkPad T43#Fingerprint_Reader]] and then slightly modified.

== Fix for the fingerprint reader getting too hot ==

If you notice that your fingerprint reader occasionally gets very hot then you might be interested in this section. Thanks to Tino Keitel, he actually gave me this solution through the linux-thinkpad mailing list.

First we need to determine if the reader is not on autosuspend mode.
Open a terminal and run:

for i in `find /sys/devices/*/*/usb* -name level` ; do echo -n "$i: " ; cat $i ; done

We care about the devices that are with "on" state and we need to determine if one of those is the reader. So for each of those run something like:

cat /sys/devices/pci0000\:00/0000\:00\:1a.0/usb1/1-2/idVendor
0483

cat /sys/devices/pci0000\:00/0000\:00\:1a.0/usb1/1-2/idProduct
2016

Use the corresponding path of the devices that you got with "on" state and then compare the output with the output of the lsusb command. An example:

lsusb output: Bus 001 Device 004: ID 0483:2016 SGS Thomson Microelectronics Fingerprint Reader

Which matches the output above (0483:2016). Once you have determined the path of your reader then become root with su - and:

echo "auto" > /sys/<path-to-device>/power/level

After this, the fingerprint reader should be in "autosuspend" and will not get hot anymore. And it will still work as normal.

This will only work for the current session. If you want to make this change persistent and have [http://linux-diag.sourceforge.net/Sysfsutils.html sysfsutils] installed, edit the file {{path|/etc/sysfs.conf}} and add the line

<path-to-device>/power/level = auto

Following the above example, that would be

devices/pci0000\:00/0000\:00\:1a.0/usb1/1-2/power/level = auto

Alternatively, you can install an init script:

sudo gedit /etc/init.d/ReaderNoMoreHot

Paste the following into it:

#!/bin/bash
#
echo "auto" > /sys/<path-to-device>/power/level

Save and close. Then:

sudo chmod 755 /etc/init.d/ReaderNoMoreHot
sudo update-rc.d ReaderNoMoreHot defaults 90

--[[User:Lunatico|Lunatico]] 19:19, 1 August 2008 (CEST), extended by --[[User:Michaelthomas h|Michaelthomas h]] 23:36, 9 August 2008 (CEST)

For the init script above, you can use the following more elaborate script, which does all the work for you of identifying the <path-to-device>. This can be useful since the USB device id can change under various circumstances (kernel upgrade etc).

<pre>
#!/bin/bash

# find the fingerprint reader and change its power level to autosuspend

usbname="SGS Thomson Microelectronics Fingerprint Reader"
usbid=$(lsusb |grep "$usbname" |cut -d' ' -f6);
[[ -z $usbid ]] && echo "USB Device \"$usbname\" not found" && exit 1

unset failed_bool
find /sys/devices/*/*/usb* -name idVendor -print | (
while read vfile; do
dir=$(dirname $vfile);
vendor=$(<$vfile);
product=$(<$dir/idProduct);
if [[ $vendor:$product = $usbid ]]; then
plevel_file=$dir/power/level
old_level=$(<$plevel_file);
[[ $old_level = auto ]] || echo auto >$plevel_file || failed_bool=1
break;
fi;
done
if [[ $failed_bool ]]; then
echo "Failed to set the fingerprint reader's power level to 'auto'."
exit 1
fi
)
</pre>

Here is an alternate script. The code is cleaner and it's about 20x faster (updated for jaunty):
<pre>
#!/bin/bash

# find the fingerprint reader and change its power level to autosuspend

find_manuf=STMicroelectronics
find_prod="Biometric Coprocessor"

for devdir in /sys/class/usb_*/*/device; do
[[ -r $devdir/manufacturer ]] || continue
manuf=$(<$devdir/manufacturer)
[[ $manuf = $find_manuf ]] || continue;
prod=$(<$devdir/product)
[[ $prod = $find_prod ]] || continue;
# if we get here then we have the right device!
plevel_file=$devdir/power/level
old_level=$(<$plevel_file);
# if it is already set properly then exit silently:
[[ $old_level = auto ]] && exit 0
# if we successfully change it then exit silently:
echo auto >$plevel_file && exit 0
echo "Failed to set the fingerprint reader's power level to 'auto'."
exit 1
done

# if we make it through the for loop without exiting, the search failed
echo "Could not find the $find_manuf $find_prod (fingerprint reader)"
exit 1
</pre>

So, I decided to see if udev (on Ubuntu hardy) could do the job in this regard. I put the following in {{path|/etc/udev/rules.d/99-fingerprint-reader.rules}} and IWFM:
<pre>
ACTION!="add", GOTO="fingerprint_end"

SUBSYSTEM=="usb" ATTR{idVendor}=="0483", ATTR{idProduct}=="2016", RUN+="/bin/sh -c 'echo auto > /sys/$devpath/power/level'"

LABEL="fingerprint_end"
</pre>
[[User:Bkuhn|Bkuhn]] 01:39, 12 August 2009 (UTC) (updated by [[User:liucougar|liucougar]] May 22, 2010 16:40 PST)

A shorter, more compact, less error-prone udev-only alternative:
Put the following in {{path|/etc/udev/rules.d/fingerprint-reader.rules}}
<pre>
SYSFS{idVendor}=="0483", SYSFS{idProduct}=="2016", SUBSYSTEMS=="usb", ACTION=="add", ATTR{power/level}="auto"
</pre>
Works on Ubuntu 10.10, should work on earlier versions as well.

How to hotswap Ultrabay devices

2008-11-07T01:56:06Z

Vegar: /* HAL support */ add PCI ID for T61

The following discusses hotswap (AKA "hotplug") of devices in the [[UltraBay]].

==Which driver?==
Since this may be confusing for SATA thinkpad owners, which are likely all the same for now, you have two busses and drivers: one SATA bus which works with the AHCI driver and one IDE bus for the ultrabay for which you should pick ata_piix (not piix/CONFIG_BLK_DEV_PIIX). See below for hotswapping.

==Choosing the right driver: new style <tt>ata_piix</tt> vs old style <tt>piix/ide-disk</tt>==
For ICH5,6,7,8, systems, whether you have an older IDE only thinkpad, or a newer thinkpad like the T/Z61p, there is one SATA bus for the system hard drive and an IDE bus for the ultrabay (even if your ultrabay happens to have a SATA drive, as it'll be seen as an IDE device), you'll have two drivers to chose from for your ultrabay: the old IDE/piix+ide-disk driver, and the newer PATA (=IDE) support of the newer ata_piix driver. 
<tt>piix+ide-disk</tt> are part of the old original IDE driver and your ultrabay device will show up as <tt>/dev/hda</tt>. <tt>ata-piix</tt> is the new SATA/PATA (=IDE) driver that will cause your ultrabay Hard Drive to show up as <tt>/dev/sda</tt> and your CD-Rom as <tt>/dev/sr0</tt>

The two things to know are: 1) you want to use ata_piix and 2) if you build piix in (CONFIG_BLK_DEV_PIIX enabled), or load it as a module, it'll take over the IDE bus and prevent ATA_PIIX from seeing your ultrabay. You don't want that.

The longer details are: 
You don't want the piix+ide-disk combo because even as modules, you will not be able to unload piix to reset the bus if there are issues swapping devices (with ata_piix, even if you forget to unregister a drive before removing it, you can unload the module and reload it to reset the bus after the fact if you have a newer thinkpad with a separate AHCI/SATA bus for the boot drive).

As for hotswap, with piix+ide-disk, you can read the section below, but after more than one day of trying on 2.6.22.15 (as piix+ide-disk was taking over my IDE bus, and stopping me from using ata_piix before I removed it), I was not able to get hotswapping to work with piix+ide-disk (lt_hotswap would not even build on 2.6.22.15).

hotswap just works with ata_pixx on 2.6.22, and reportedly with anything newer than 2.6.18, so you want to get rid of piix+ide-disk.
There are several ways to do that:
* if piix is built in your kernel (CONFIG_BLK_DEV_PIIX):
** rebuild your kernel with CONFIG_BLK_DEV_PIIX turned off.
** if you don't want to rebuild your kernel, try disabling the IDE bus grabbing by that driver with <tt>ide0=noprobe hda=noprobe hdb=noprobe</tt> in your grub/lilo config (adjust the drive letters as appropriate, but note that this did not work for me on 2.6.22.15: the drive didn't show up on the piix bus, but it didn't show up on the ata_piix bus either).
* if piix is built in as a module
** you can move out the module in {{path|/lib/modules/ver/kernel/drivers/ide/pci/piix.ko}} and reboot.
** or build a new kernel, again with CONFIG_BLK_DEV_PIIX turned off.
** or add <tt>options ide_core options="ide0=noprobe hda=noprobe hdb=noprobe"</tt> to your modprobe.conf is supposed to work too (but didn't work on 2.6.22.15, see comment above)

Then, continue this document to see how to do hotswap with ata_piix (if you are lucky enough to have a newer SATA thinkpad where the ata_piix driver only runs the ultrabay, and you have a separate bus and ahci driver for your main drive, it is recommended to have ata_piix as a module (<tt>CONFIG_ATA_PIIX=m</tt>) so that you can unload/reload it if your bus gets in a bad state after a failed hotswap)

==When using the <tt>ata_piix</tt> driver==
The following applies when using the <tt>ata_piix</tt> driver, which is necessary for many recent ThinkPad models that use an [[Intel ICH6-M]] controller. See also [[Problems with SATA and Linux]].

Mainline kernels before 2.6.18 cannot reliably recognize newly (re-)inserted UltraBay drives without a reboot. There are experimental hotplug patches against pre-2.6.18 mainline kernels [http://home-tj.org/wiki/index.php/Libata-tj-stable here].

* Available hotplug patches
**[http://home-tj.org/files/libata-tj-stable/libata-tj-2.6.16.16-20060512.tar.bz2 Patch tarball against 2.6.16.16] ([http://lwn.net/Articles/183407/ Announce])
**[http://home-tj.org/files/libata-tj-stable/libata-tj-2.6.17-20060625-1.tar.bz2 Patch tarball against 2.6.17/2.6.17.1] ([http://article.gmane.org/gmane.linux.ide/11598 Announce])
**[http://home-tj.org/files/libata-tj-stable/libata-tj-2.6.17.4-20060710.tar.bz2 Patch tarball against 2.6.17.4]
**[http://whoopie.gmxhome.de/linux/patches/2.6.17.14-tj/00-libata-tj-2.6.17.4-20060710.patch Patch against 2.6.17.14]

* Confirmed to work on the following laptops, with bus the following ID
**ThinkPad {{T23}}
**ThinkPad {{T30}}
**ThinkPad {{T43}}, {{T43p}}
**ThinkPad {{R52}}
**ThinkPad {{T60}} ID=4
**ThinkPad {{T61}} ID=0
**ThinkPad {{Z61p}} ID=4 (0-3:ahci, 5-6: ata_piix)
ID will typically be 1 if you only have an IDE bus (0 is boot drive, 1 is ultrabay), and it'll be 4 if you have a SATA bus your system boots from (ID 0-3) and an IDE bus for your ultrabay (ID 4-5). 
Note that even on a given laptop model the ID can vary depending on whether your kernel has drivers that configure your boot drive is using the old style IDE driver (which doesn't add IDs before your ultrabay), or whether your boot drive is using the new style driver (which adds IDs before your ultrabay)

Hotplug just works with kernels newer than 2.6.18 ( or older kernels that were patched to support <tt>ata_piix</tt> hotplug (don't try it otherwise!)) 
First, it is recommended you find the right SCSI ID for your drive to hotswap and unregister it before removing it (this works with all recent mainline kernels):
{{cmdroot|echo 1 > /sys/class/scsi_device/$ID:0:0:0/device/delete}}
{{cmdroot|echo eject > /proc/acpi/ibm/bay}}
The drive can now be ejected (without this, your IDE bus may complain if you just yank a drive, but you can usually recover by unloading/reloading the ata_piix module on a SATA laptop if your main drive is not on the ata_piix bus)

You can then issue the following after inserting an UltraBay drive to rescan the port:
{{cmdroot|echo 0 0 0 > /sys/class/scsi_host/host$ID/scan}}
The inserted drive should now be recognized by the kernel, and appropriate {{path|/dev/*}} entries created automatically (e.g., by <tt>udev</tt>).

Ted T'so has also written this hotswap patch, which may or may not be needed for you, see [http://www.mail-archive.com/linux-acpi@vger.kernel.org/msg04716.html hotswap patch] and report back

===Scripts for hotswapping===

The following scripts and [[acpid]] daemon configuration files do the following:
* Automatically unmounts the relevant filesystems and power off the UltraBay when the UltraBay eject lever is released. Screams if some filesystem can't be unmounted.
* Rescans the UltraBay port when then UltraBay eject lever is pushed back in.

They assumes you're using the <tt>ata_piix</tt> driver with an appropriate kernel (see above).

Create {{path|/usr/local/sbin/ultrabay_insert}} with permissions 755:
<pre>
#!/bin/bash
echo 12 > /proc/acpi/ibm/beep
sync
echo 0 0 0 > /sys/class/scsi_host/host1/scan
</pre>

Create {{path|/usr/local/sbin/ultrabay_eject}} with permissions 755:
<pre>
#!/bin/bash
ULTRABAY_SYSDIR='/sys/class/scsi_device/1:0:0:0/device'
shopt -s nullglob

# Umount the filesystem(s) backed by the given major:minor device(s)
unmount_rdev() { perl - "$@" <<'EOPERL' # let's do it in Perl
for $major_minor (@ARGV) {
$major_minor =~ m/^(\d+):(\d+)$/ or die;
push(@tgt_rdevs, ($1<<8)|$2);
}
# Sort by reverse length of mount point, to unmount sub-directories first
open MOUNTS,"</proc/mounts" or die "$!";
@mounts=sort { length($b->[1]) <=> length($a->[1]) } map { [ split ] } <MOUNTS>;
close MOUNTS;
foreach $m (@mounts) {
($dev,$dir)=@$m;
next unless -b $dev; $rdev=(stat($dev))[6];
next unless grep($_==$rdev, @tgt_rdevs);
system("umount","-v","$dir")==0 or $bad=1;
}
exit 1 if $bad;
EOPERL
}

# Get the UltraBay's /dev/foo block device node
ultrabay_dev_node() {
UDEV_PATH="`readlink -e "$ULTRABAY_SYSDIR/block:"*`" || return 1
UDEV_NAME="`udevinfo -q name -p $UDEV_PATH`" || return 1
echo /dev/$UDEV_NAME
}

if [ -d $ULTRABAY_SYSDIR ]; then
sync
# Unmount filesystems backed by this device
unmount_rdev `cat $ULTRABAY_SYSDIR/block\:*/dev \
$ULTRABAY_SYSDIR/block\:*/*/dev` \
|| {
echo 10 > /proc/acpi/ibm/beep; # error tone
exit 1;
}
sync
# Nicely power off the device
DEVNODE=`ultrabay_dev_node` && hdparm -Y $DEVNODE
# Let HAL+KDE notice the unmount and let the disk spin down
sleep 0.5
# Unregister this SCSI device:
sync
echo 1 > $ULTRABAY_SYSDIR/delete
fi
sync
# Turn off power to the UltraBay:
if [ -d /sys/devices/platform/bay.0 ]; then
echo 1 > /sys/devices/platform/bay.0/eject
elif [ -e /proc/acpi/ibm/bay ]; then
echo eject > /proc/acpi/ibm/bay
fi
# Tell the user we're OK
echo 12 > /proc/acpi/ibm/beep
</pre>

Use the modified version below if the above doesn't work for you (for kernels 2.6.25+ due to "ULTRABAY_SYSDIR/block\:*/dev" path change). It was tested on a Thinkpad X41 with Fedora 9 and kernel 2.6.25.11:

<pre>
#!/bin/bash
ULTRABAY_SYSDIR='/sys/class/scsi_device/1:0:0:0/device'
shopt -s nullglob

# Umount the filesystem(s) backed by the given major:minor device(s)
unmount_rdev() { perl - "$@" <<'EOPERL' # let's do it in Perl
for $major_minor (@ARGV) {
$major_minor =~ m/^(\d+):(\d+)$/ or die;
push(@tgt_rdevs, ($1<<8)|$2);
}
# Sort by reverse length of mount point, to unmount sub-directories first
open MOUNTS,"</proc/mounts" or die "$!";
@mounts=sort { length($b->[1]) <=> length($a->[1]) } map { [ split ] } <MOUNTS>;
close MOUNTS;
foreach $m (@mounts) {
($dev,$dir)=@$m;
next unless -b $dev; $rdev=(stat($dev))[6];
next unless grep($_==$rdev, @tgt_rdevs);
system("umount","-v","$dir")==0 or $bad=1;
}
exit 1 if $bad;
EOPERL
}

# Get the UltraBay's /dev/foo block device node
ultrabay_dev_node() {
UDEV_PATH="`readlink -e "$ULTRABAY_SYSDIR/block/"*`" || return 1
UDEV_NAME="`udevinfo -q name -p $UDEV_PATH`" || return 1
echo /dev/$UDEV_NAME
}

if [ -d $ULTRABAY_SYSDIR ]; then
sync
# Unmount filesystems backed by this device
unmount_rdev `cat $ULTRABAY_SYSDIR/block/*/dev \
$ULTRABAY_SYSDIR/block/*/*/dev` \
|| {
echo 10 > /proc/acpi/ibm/beep; # error tone
exit 1;
}
sync
# Nicely power off the device
DEVNODE=`ultrabay_dev_node` && hdparm -Y $DEVNODE
# Let HAL+KDE notice the unmount and let the disk spin down
sleep 0.5
# Unregister this SCSI device:
sync
echo 1 > $ULTRABAY_SYSDIR/delete
fi

# We really need a 3 sec pause here otherwise the system will freeze..
sleep 3

# Turn off power to the UltraBay:
if [ -d /sys/devices/platform/bay.0 ]; then
echo 1 > /sys/devices/platform/bay.0/eject
elif [ -e /proc/acpi/ibm/bay ]; then
echo eject > /proc/acpi/ibm/bay
fi
# Tell the user we're OK
echo 12 > /proc/acpi/ibm/beep
</pre>

Create {{path|/etc/acpi/events/ultrabay-insert}}:
<pre>
event=ibm/bay MSTR 00000001 00000000
action=/usr/local/sbin/ultrabay_insert
</pre>

Create {{path|/etc/acpi/events/ultrabay-eject}}:
<pre>
event=ibm/bay MSTR 00000003 00000000
action=/usr/local/sbin/ultrabay_eject
</pre>

Restart <tt>acpid</tt>.

If the <tt>ata_piix</tt> driver is built in the kernel, it will catch bay events and you will see the
following message in your system log:
<pre>
thinkpad_acpi: another device driver is already handling bay events
thinkpad_acpi: disabling subdriver bay
</pre>
You should load <tt>thinkpad_acpi</tt> before <tt>ata_piix</tt> if you want it to handle bay events.

===using the generic bay driver and udev===

Starting from kernel 2.6.23-rc3, it's possible to use the generic <tt>bay</tt> driver in combination with udev to hotswap. Please check if CONFIG_ACPI_BAY is enabled (module or built-in) in your kernel configuration.

Create {{path|/etc/udev/rules.d/ibm-ultrabay.rules}}:
<pre>
ENV{BAY_EVENT}=="3", KERNEL=="bay.0", ACTION=="change", SUBSYSTEM=="platform", RUN+="/usr/local/sbin/ultrabay_eject"
ENV{BAY_EVENT}=="1", KERNEL=="bay.0", ACTION=="change", SUBSYSTEM=="platform", RUN+="/usr/local/sbin/ultrabay_insert"
</pre>

===using libata-acpi and udev===

Starting from kernel 2.6.26-rc5, it's possible to use <tt>libata-acpi</tt> in combination with udev to hotswap. Please check if CONFIG_ATA_ACPI is enabled in your kernel configuration.

For 2.6.25, you need two patches which can be easily backported ([http://article.gmane.org/gmane.linux.acpi.devel/31159],[http://article.gmane.org/gmane.linux.acpi.devel/31369]).

Create {{path|/etc/udev/rules.d/ibm-ultrabay.rules}}:
<pre>
ENV{BAY_EVENT}=="3", ACTION=="change", SUBSYSTEM=="scsi", RUN+="/usr/local/sbin/ultrabay_eject"
</pre>

===Model-specific notes===
See the table above for a list of ata_piix supported laptops and the bus ID to use.

===HAL support===

{{NOTE| Starting from HAL 0.5.11, you need to replace "storage.physical_device" with "info.parent".}}

Many programs, KDE included, rely on [[HAL]] to get notifications and information about device hotplugging. You need to tell HAL that devices connected the UltraBay port are hotpluggable. To do so, create the file {{path|/etc/hal/fdi/information/10-ultrabay.fdi}} as follows:
<pre>
<?xml version="1.0" encoding="UTF-8"?> 

<deviceinfo version="0.2">
<device>


<match key="storage.bus" string="scsi">
<match key="storage.physical_device" string="/org/freedesktop/Hal/devices/pci_8086_2653_scsi_host_0_scsi_device_lun0">
<merge key="storage.hotpluggable" type="bool">true</merge>
</match>
</match>

</device>
</deviceinfo>
</pre>

The string "8086_2653" may need to be changed to match your ThinkPad model; see below.

====Details====

By default, HAL doesn't know that UltraBay devices are hotpluggable:

# PHYSDEV=/org/freedesktop/Hal/devices/pci_8086_2653_scsi_host_0_scsi_device_lun0
# UDI=`hal-find-by-property --key storage.physical_device --string $PHYSDEV` || echo Failed
# hal-get-property --udi $UDI --key block.device
/dev/sdb
# hal-get-property --udi $UDI --key storage.hotpluggable
false

After creating {{path|/etc/hal/fdi/information/10-ultrabay.fdi}} as above and re-plugging the device, it will get marked correctly:

# PHYSDEV=/org/freedesktop/Hal/devices/pci_8086_2653_scsi_host_0_scsi_device_lun0
# UDI=`hal-find-by-property --key storage.physical_device --string $PHYSDEV` || echo Failed
# hal-get-property --udi $UDI --key block.device
/dev/sdb
# hal-get-property --udi $UDI --key storage.hotpluggable
true

The string "8086_2653" gives the PCI ID of the [[Intel 82801FBM]] southbridge. If your model has a different southbridge, or the UltraBay is attached to a different port, then you can find the appropriate <tt>storage.physical_device</tt> value by finding out the block device of the currently running UltraBay device (<tt>/dev/sdb</tt> in the following example) and then running:

# DEVICE=/dev/sdb
# UDI=`hal-find-by-property --key block.device --string $DEVICE` || echo Failed
# hal-get-property --udi $UDI --key storage.physical_device
/org/freedesktop/Hal/devices/pci_8086_2653_scsi_host_0_scsi_device_lun0

If you have a different <tt>storage.physical_device</tt> value, please report your findings.

{| border=1
|+ Known South Bridge PCI IDs
! ID !! ThinkPad model !! South Bridge chip
|-
| 8086_248a || 2366-83U (T30), 2647-MG3 (T23)|| Intel 82801CAM IDE U100 (rev 2)
|-
| 8086_2653 || 2525FAG (X41), ? (T43) || Intel 82801FBM (ICH6-M)
|-
| 8086_24ca || 237358U (T40), 2373KXU (T42p) || Intel 82801DBM (ICH4-M)
|-
| 8086_27c4 || X60 || Intel 82801GBM (ICH7 Family)
|-
| 8086_27df || Z61p, T60, T60p || Intel 82801GBM/GHM (ICH7 Family)
|-
| 8086_2850 || T61, T61p || Intel 82801H (ICH8 Family)
|}

==When using the <tt>ide-disk</tt> driver==
The following applies if you use the <tt>ide-disk</tt> driver for the UltraBay device. 
Note that essentially, you shouldn't be using this driver, and use ata_piix instead unless you're running an older kernel where ata_piix won't work for you

Hotswapping is supposed to be supported as well, using either hdparm/[http://packages.debian.org/unstable/admin/hotswap Debian hotswap] or [[lt_hotswap]] to (un)register IDE devices. The latter is the recommended method with kernels from 2.6, since it will leave DMA working. However, for recent models (R52, T43, X41, Z60 and later) no method is known to work while maintaining DMA support; see [[Problems with SATA and Linux]].

Only IDE devices (HDD's, optical drives, zip drives) require special treatment - batteries, floppies and other devices can just be pulled from the bay, provided they are not mounted or in use at the time. However, you should still power them down first using the [[ibm-acpi]] eject function.

The [[ibm-acpi]] kernel module has an eject function ({{cmdroot|echo eject > /proc/acpi/ibm/bay}}). This only manages the ACPI calls to power down the device and the bay. It does not actually unregister the device from the IDE driver. {{cmdroot|cat /proc/acpi/ibm/bay}} shows "unoccupied" unless an IDE device is present, but the eject function still works and should still be used.

To unregister the device, you can either use the [http://packages.debian.org/unstable/admin/hotswap Debian hotswap] package, or [[lt_hotswap]]. Note that lt_hotswap doesn't seem to even build on recent (at 2.6.22 or newer, although it probably broke before 2.6.22) and on newer kernels, you should not build/load the old IDE PIIX (CONFIG_BLK_DEV_PIIX) and use the natively hotswapping ata_piix (CONFIG_ATA_PIIX) as explained on the top of this page.

[http://packages.debian.org/unstable/admin/hotswap Debian hotswap] also allows the drive to be swapped as a normal user by default, which is useful. You should use <tt>hotswap</tt> to unregister the device and then {{cmdroot|echo eject > /proc/acpi/ibm/bay}}. However, if you use this method on a 2.6 kernel, you will lose DMA support for the reinserted drive. This is due to kernel issues. This method was reported to work on a ThinkPad {{T23}} (kernels 2.6.8.1, 2.6.14.2 and 2.6.15-arch) and {{T42}} (kernel 2.6.13), but fails on a ThinkPad {{T43}} (kernel 2.6.14.3).

[[lt_hotswap]] is now the recommended method to un- and reregister the IDE device. It installs as a kernel module and has support for automatically unregistering (if loaded with the auto_eject=1 option) the device when the eject event is generated by [[ibm-acpi]]. It will leave DMA support intact. It has supported to work on a ThinkPad {{T22}} and {{T40}} and should work with many other models (but not recent models which require the <tt>ata_piix</tt> driver for disk DMA support). With the [[lt_hotswap]] kernel module loaded, run: {{cmdroot|modprobe -r ide_cd && modprobe -r cdrom && echo "MSTR eject" > /proc/acpi/lths}}

===HAL support===

HAL support also can also be configured To do so, create the file {{path|/etc/hal/fdi/information/10-ultrabay.fdi}} as follows:
<pre>
<?xml version="1.0" encoding="UTF-8"?> 

<deviceinfo version="0.2">
<device>


<match key="storage.bus" string="ide">
<match key="storage.physical_device" string="/org/freedesktop/Hal/devices/pci_8086_24ca_ide_1_0">
<merge key="storage.hotpluggable" type="bool">true</merge>
</match>
</match>

</device>
</deviceinfo>
</pre>
For more details see HAL section for ata driver.

==Other comments==

If you are hot-swapping a hard disk on a disk tray, make sure the disk does not have a password set, otherwise it will not be recognized on reinsertion.

[[Category:Scripts]]
[[Category:HOWTOs]]

How to configure the TrackPoint

2008-11-04T21:39:51Z

Vegar: /* TrackPoint under Ubuntu 8.10 using HAL */ Remove duplicate line

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |The [[Patch to enable advanced trackpoint configuration|kernel trackpoint driver]] is controlled by echoing values to special files. Common configuration options are outlined below.
{{NOTE|
*With kernels 2.6.19 and above config files for this driver are located in <tt>/sys/devices/platform/i8042/serio1</tt>.
*With kernels 2.6.13 (inclusive) to 2.6.19 (exclusive) config files for this driver are located in <tt>/sys/devices/platform/i8042/serio0/serio2</tt>.
*With kernels 2.6.11 (inclusive) to 2.6.13 (exclusive) config files for this driver are located in <tt>/sys/devices/platform/i8042/serio0</tt>.
*With kernels 2.6.9 (inclusive) to 2.6.11 (exclusive) config files for this driver are located in <tt>/proc/trackpoint</tt>.
*Prior to kernel 2.6.9, configuration was not done through files but through command-line options to the psmouse module. (Note this means you must compile psmouse as a module!) See http://stephen.evanchik.com/node/16.
}}
|}

==General Configuration==
The configuration options are reflected by the files you can find in {{path|/sys/devices/platform/i8042/serio0/serio2}}. See the [[Patch to enable advanced trackpoint configuration|TrackPoint driver page]] for a complete list.
Configuration is done by echoing the appropriate values into these special files.

If you want to set the sysfs parameters at boot, you can use the [http://linux-diag.sourceforge.net/Sysfsutils.html sysfsutils] and put the preferred value in /etc/sysfs.conf.

==Most common Features==
The most common settings are '''Press to Select''', '''sensitivity''', '''speed''' and '''scrolling'''.

===Press to Select===
Press to Select allows you to tap the control stick which will simulate a left click. You can enable this feature by typing the following in to a terminal (you may need to be root):

:{{cmdroot|echo -n 1 > /sys/devices/platform/i8042/serio0/serio2/press_to_select}}

Press to Select should now be enabled. You can disable it in a similar manner:

:{{cmdroot|echo -n 0 > /sys/devices/platform/i8042/serio0/serio2/press_to_select}}

You can use this script to automate the operation

#!/bin/bash
if [ "$1" = "1" ]; then
echo "Turning on tap on TrackPoint"
echo -n 1 > /sys/devices/platform/i8042/serio0/serio2/press_to_select
exit 0
fi
if [ "$1" = "0" ]; then
echo "Turning off tap on TrackPoint"
echo -n 0 > /sys/devices/platform/i8042/serio0/serio2/press_to_select
exit 0
fi
echo -n "Tap status: "
cat /sys/devices/platform/i8042/serio0/serio2/press_to_select

===Sensitivity & Speed===
Adjusting the speed and sensitivity of the TrackPoint requires echoing a value between 0 and 255 into the appropriate file. For example, for a speed of 120 and a sensitivity of 250, type the following into a terminal:

:{{cmdroot|echo -n 120 > /sys/devices/platform/i8042/serio0/serio2/speed}}
:{{cmdroot|echo -n 250 > /sys/devices/platform/i8042/serio0/serio2/sensitivity}}

Feel free to experiment with your settings until you find a combination that is comfortable.

When you satisfy your setting , add the two lines into /etc/rc.d/rc.local in order to avoid restoring the default setting every time the system reboots.

===Scrolling===
====Using a kernel prior to 2.6.11====
The scrolling action is essentially the same as is used in the TrackPoint Windows drivers. To enable this feature, type the following in to a terminal (you may need to be root):

:{{cmdroot|echo -n 1 > /proc/trackpoint/scroll}}

Then press the middle button and push the stick up and down to scroll. Similarly, to disable scrolling:

:{{cmdroot|echo -n 0 > /proc/trackpoint/scroll}}

====Using the X server (kernel 2.6.11+)====
The scroll setting has been removed from the trackpoint driver in kernel versions 2.6.11 and above. Scroll emulation should now be handled in the X server.

A nice side effect of that is, that middle button scrolling applies to any mouse and not just the TrackPoint interface, which can be a quite handy feature for desktop computers or people who prefer to use an external mouse, especially when scrolling through long lists or needing to use horizontal scrolling with a mouse which has only a vertical scroll wheel.

The necessary functionality, known as "EmulateWheelTimeout" allowing to use button 2 for a middle click, wasn't implemented in Xorg prior to 6.9/7.0. However, there was a patch included in most distributions packages of Xorg, which was announced [http://www.mail-archive.com/devel@xfree86.org/msg03333.html here]. You can find an updated version of the package in the experimental branch of {{Debian}} or try to build the mouse driver yourself with the information in the announcement. This has successfully been tried with FC3's 6.8.2 packages.

Once this functionality is in the X.org, add these lines to your TrackPoint configuration section in {{path|/etc/X11/xorg.conf}}:

Option "EmulateWheel" "on"
Option "EmulateWheelButton" "2"

It may also be necessary to add these lines:

Option "YAxisMapping" "4 5"
Option "XAxisMapping" "6 7"

which specify which buttons are mapped to motion in the vertical (Y) and horizontal (X) directions, respectively, in wheel emulation mode (see http://www.xfree86.org/current/mouse.4.html).

{{HINT| Use the program "xev" to see, what mouse button identifiers are sent by your mouse/touchpad/trackpoint. You might want to try: "xev | grep button"}}
{{HINT| If it does not work see if evdev is installed and remove it. On gentoo do the following: 
eix xf86-input-evdev 
emerge -C xf86-input-evdev 
and then remove the evdev flag in make.conf INPUT_DEVICES}}

So, a complete mouse section, that implements this nicely and works very well on my R51, even with a simultaneously connected USB mouse, looks like that (tried out today, 20th of September, 2006 on Dapper):

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "Emulate3Buttons" "on"
Option "Emulate3TimeOut" "50"
Option "EmulateWheel" "on"
Option "EmulateWheelTimeOut" "200"
Option "EmulateWheelButton" "2"
Option "YAxisMapping" "4 5"
Option "XAxisMapping" "6 7"
Option "ZAxisMapping" "4 5"
EndSection

The mappings for Y and Z are the same, since the "Z-Axis" refers to actual hardware scrolling wheels which usually scroll the screen along the Y-Axis. If there is no hardware scrolling wheel present, horizontal and vertical scrolling using the TrackPoint work fine without the Z-Axis line.

Now restart X and hold down button 2 and move the mouse to scroll, or just press and release button 2 for a middle click.

To make this work with the synaptics driver for the touchpad, you can add
Option "GuestMouseOff" "1"
to the synaptics device section. This will make the synaptics driver ignore the Trackpoint, so it will be handled by the mouse driver. This allowed me to disable the touchpad while making the TrackPoint work like it should.

{{NOTE| With the above mouse section in my xorg.conf all this works like a charm:
*I can press the wheel on my external USB mouse and move the mouse up and down for scrolling
*or I can just use the wheel on the external mouse for scrolling
*or pressing the MMB button of the trackpoint and use the trackpoint for scrolling.
*Even horizontal scrolling works automagically in Konqueror, for Firefox/Opera see below.

Simultaneously I can use
*a press on the external mouse's wheel
*or the MMB of the trackpoint

for pasting the buffer. Lovely! :) }}

{{HINT| If you don't use the middle-mouse-button for pasting and sometimes pasting things by mistake while scrolling (witch is really odd) simply set the "EmulateWheelTimeOut" to "1" as a (bloody) workaround. Middle click will only possible with pressing left and right button simultaneously!}}

===== EmulateWheelTimeout temporarily broken (-> fix for Ubuntu Dapper) =====

Unfortunately, there was a regression so that EmulateWheelTimeout was broken in X.org 6.9.0, and fixed
on March 20th, 2006.
You can see the [https://bugs.freedesktop.org/show_bug.cgi?id=5071 primary bug report] here, and also reports on the [http://qa.mandriva.com/show_bug.cgi?id=21196 Mandriva] and [http://lists.debian.org/debian-x/2006/01/msg00249.html Debian] ([http://bugs.debian.org/346098 #346098], [http://bugs.debian.org/320136 #320136]) packages.

Unfortunately, this bug is still present in Ubuntu Dapper Drake's xserver-xorg-input-mouse package (version 1.0.3.1+cvs.20060109-0ubuntu1)!

{{HINT|xserver-xorg-input-mouse (version 1.0.3.1+cvs.20060109-0ubuntu1.1) is in dapper-updates since July 3rd, 2006. You don't need to patch it anymore.}}

Use the following procedure to make it (middle button scrolling & middle button pasting) work:

:{{cmduser|cd /desired/path && mkdir tmp && cd tmp}} (create temporary directory somewhere)
:{{cmduser|sudo nano /etc/apt/sources.list}} (insert/uncomment the deb-src lines, save and exit)
:{{cmduser|sudo apt-get update}}
:{{cmduser|apt-get source xserver-xorg-input-mice}} (in order to get the source code)
:{{cmduser|sudo aptitude install xserver-xorg-dev}} (this package and the packages it depends on are needed in order to compile the source code, use aptitude for easy removal later on)
:{{cmduser|cd xserver-xorg-input-mouse-1.0.3.1+cvs.20060109/}}
:{{cmduser|wget http://librarian.launchpad.net/2639933/xserver-xorg-input-mouse_1.0.3.1+cvs.20060109-0ubuntu2.debdiff}} (downloads the patch that fixes the bug)
:{{cmduser|patch -p1 < xserver-xorg-input-mouse_1.0.3.1+cvs.20060109-0ubuntu2.debdiff}} (applies the bug fix)
:{{cmduser|fakeroot dpkg-buildpackage}} (rebuilds the package... watch out for errors and install other missing packages)
:{{cmduser|sudo dpkg -i ../xserver-xorg-input-mouse_1.0.3.1+cvs.20060109-0ubuntu2_i386.deb}} (installs the rebuilt built package)
:{{cmduser|sudo aptitude remove xserver-xorg-dev}} (removes the packages needed to rebuild the package)

Hope it works for you, it did work for me!
CrypTom

===== Older versions of X.org =====

For older versions of Xorg or for Xfree86 ({{path|/etc/X11/XF86Config}}) try this:

Option "Emulate3Buttons" "true"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"

Now restart X and hold down button two and move the mouse for scrolling. To get a middle click, press buttons 1 and 3 simultaneously.

==Soft Transparent Mode==
If you wish to connect a special device to the external PS/2 port, you should consider using "Soft Transparent Mode" so that the TrackPoint controller does not interpret any commands sent to the external PS/2 port. You can enable soft transparent mode by typing the following in to a terminal:

:{{cmdroot|echo -n 1 > /sys/devices/platform/i8042/serio0/serio2/transparent}}

Disabling soft transparent mode is similar:

:{{cmdroot|echo -n 0 > /sys/devices/platform/i8042/serio0/serio2/transparent}}

==Modify trackpoint parameter permanently in trackpoint.h==
If you do not want to run a script to reconfigure the trackpoint
you can change the default settings in the trackpoint header file that is located in
/usr/src/<KERNEL_VERSION>/drivers/input/mouse/trackpoint.h.

First you must convert the values (decimal numbers) you normaly echo to /sys/[...] to hex:

'''echo -e 'obase=16;<DECIMAL_NUMBER>' | bc'''

Then simply replace the default hex values in trackpoint.h, run 'make && make modules_install' to recompile and install psmouse.ko (should be compiled as module)

Example patch (speed=100, sensitivity=190, press_to_select=1):
<pre>
--- trackpoint.h.orig 2006-01-17 16:18:30.000000000 +0100
+++ trackpoint.h 2006-01-17 16:25:47.000000000 +0100
@@ -108,9 +108,9 @@
/*
* Default power on values
*/
-#define TP_DEF_SENS 0x80
+#define TP_DEF_SENS 0xBE
#define TP_DEF_INERTIA 0x06
-#define TP_DEF_SPEED 0x61
+#define TP_DEF_SPEED 0x64
#define TP_DEF_REACH 0x0A

#define TP_DEF_DRAGHYS 0xFF
@@ -123,7 +123,7 @@

/* Toggles */
#define TP_DEF_MB 0x00
-#define TP_DEF_PTSON 0x00
+#define TP_DEF_PTSON 0x01
#define TP_DEF_SKIPBACK 0x00
#define TP_DEF_EXT_DEV 0x01
</pre>

==Configure firefox for using trackpoint horizontal scrolling==
Vertical Scrolling seems to work out of the box in firefox if you followed the steps above.
Anyway, there is a problem when you don't scroll exactly vertical, because horizontal scrolling turns into
browser BACK/FORWARD commands.
You can avoid this by typing about:config + ENTER in the address bar of firefox.
You have to adjust the following options:

<pre>
mousewheel.horizscroll.withcontrolkey.action = 3;
mousewheel.horizscroll.withcontrolkey.numlines = 1;
mousewheel.horizscroll.withcontrolkey.sysnumlines = true;

mousewheel.horizscroll.withnokey.action = 0;
mousewheel.horizscroll.withnokey.numlines = 1;
mousewheel.horizscroll.withnokey.sysnumlines = true;

mousewheel.horizscroll.withshiftkey.action = 1;
mousewheel.horizscroll.withshiftkey.numlines = 1;
mousewheel.horizscroll.withshiftkey.sysnumlines = true;
</pre>

FWIW, you can change only the following value to remove the browser BACK/FORWARD commands:

<pre>
mousewheel.horizscroll.withnokey.action = 0;
</pre>

With that, you can still go BACK/FORWARD by pressing together the shift or the alt key, while with the control key you increase or decrease the font size.

==Configure Opera for using trackpoint horizontal scrolling==
You'll experience the same annoying problem with the popular browser Opera. To fix this you need to edit the configfile <tt>standard_mouse.ini</tt> in e.g. /usr/share/opera/ini/ (Debian) or /opt/opera/share/opera/ini/ (Gentoo) and comment out the following lines
<pre>
Button6 = Back
Button7 = Forward
</pre>
so they look like that
<pre>
;Button6 = Back
;Button7 = Forward
</pre>
Remember, Button6 and Button7 do not so coincidental correspond with our X configuration we know from above:
<pre>
Option "YAxisMapping" "6 7"
</pre>
After this change you will be able to scroll vertically and horizontally with your middle button.

==Fixing trackpoint under Ubuntu 7.10 Gutsy Gibbon==
===Using trackpoint deamon===
My default Ubuntu Gutsy (running on an X61s) would give the following error messages when running the trackpoint daemon. Running
<pre>
/etc/init.d/trackpoint restart
</pre>
caused a bunch of error messages, as the wrong device was in
<pre>
/etc/trackpoint/trackpoint.conf
</pre>

I fixed this by changing:
<pre>
echo -n > /sys/devices/platform/i8042/serio0/serio2/sensitivity
</pre>
to
<pre>
echo -n > /sys/devices/platform/i8042/serio1/sensitivity
</pre>
in /etc/trackpoint/trackpoint.conf.

In addition, Ubuntu ran the appropriate /etc/init.d/trackpoint script on booting, but would give a bunch of errors (which, oddly, I could never find in any of the log files).

It seems that it was running the scripts too early in the boot sequence. The Gutsy package provided
<pre>
/etc/rc2.d/S20trackpoint
</pre>

so I renamed this to S99trackpoint (and in all the other rc.? directories) and it now works on boot.

===Editing the kernel config files===
Another way of configuring the trackpoint without using the trackpoint daemon is to edit the values of the trackpoint files which, BTW, are located in
/sys/devices/platform/i8042/serio1/serio2.

The script should be executed during boot. This can be done in an init script (e.g. /etc/bootmisc.sh in some distros)

Script:
<pre>
#! /bin/sh

#
# configuration du trackpoint
#

# vitesse
echo -n 120 > /sys/devices/platform/i8042/serio1/serio2/speed

# sensibilité
echo -n 250 > /sys/devices/platform/i8042/serio1/serio2/sensitivity

# press to select
echo -n 1 > /sys/devices/platform/i8042/serio1/serio2/press_to_select
</pre>
===An Ubuntu/Fedora example===
Another script that I've created seems to work with all versions of Ubuntu/Fedora that I've been able to try (comment out and uncomment the appropriate lines for fedora/ubuntu as necessary)
Place in /etc/rc.local or equivalent for your distro:

Script:
<pre>
#*************************
## START TRACKPOINT CONFIG
#*************************

# For fedora (the slash after "speed" is returned)
# TRACKPATH=$(find /sys -print0 | grep -FzZ "/serio2/speed" | sed s^speed/^^)

# For ubuntu (the slash after "speed" is not returned)
TRACKPATH=$(find /sys -print0 | grep -FzZ "/serio2/speed" | sed s/speed//)

## Select "press_to_select" on the trackpoint input device
## We need to specify the TRACKPATH above because the device under "serio#"
## changes between system boots. (We first test to see if the file we want
## to modify exists, if it does, we make the change
#[ -f $TRACKPATH/press_to_select ] && echo -n 1 > $TRACKPATH/press_to_select

## Adjust the speed setting of the trackpoint input device
[ -f $TRACKPATH/speed ] && echo -n 120 > $TRACKPATH/speed
## Adjust the sensitivity setting of the trackpoint input device
[ -f $TRACKPATH/sensitivity ] && echo -n 200 > $TRACKPATH/sensitivity

#***********************
## END TRACKPOINT CONFIG
#***********************
</pre>

==TrackPoint under Ubuntu 8.10 using HAL==

Because Ubuntu 8.10 uses HAL you must do the following to get the scrolling working:
(see: http://forum.ubuntuusers.de/topic/mouse-wheel-emulation-in-xorg.conf/?highlight=hal+trackpoint#post-1558282 )

Create the file '''/etc/hal/fdi/policy/mouse-wheel.fdi''' as root with the following content:

<pre>
<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.YAxisMapping" type="string">4 5</merge>
<merge key="input.x11_options.XAxisMapping" type="string">6 7</merge>
<merge key="input.x11_options.Emulate3Buttons" type="string">true</merge>
<merge key="input.x11_options.EmulateWheelTimeout" type="string">200</merge>
</match>
</pre>

Note : I needed to reboot my TP for the changes to take effect.

https://wiki.ubuntu.com/X/Config

Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T61

2007-09-17T14:40:25Z

Vegar: /* HDAPS */ add comment about the hdaps inverted parameter

On the T61, [[Installing_Ubuntu_7.10_(Gutsy_Gibbon)_Tribe_5_on_a_ThinkPad_T61|Ubuntu 7.10 (Gutsy Gibbon)]] is recommended instead of 7.04 because video drivers and wifi, among other issues, work by default.
recomended

===My DVD drive/CD burner/DVD burner doesn't work (Solved)===

Follow these instructions to enable your [http://en.wikipedia.org/wiki/Optical_drive optical drive]: 
1) Reboot your T61. Press the ThinkVantage button quickly when you see the ThinkPad screen and then press F1 enter [http://en.wikipedia.org/wiki/BIOS BIOS]. 
2) In BIOS, select Configure -> Serial ATA. 
3) Now, select Compatibility instead of AHCI. 
4) Exit BIOS and start your computer normally. 
5) Go to Places -> Computer, right-click your CD-ROM/DVD/etc. drive, and select Properties. Then, go to Drive -> Settings. Set the mount point to ''cdrom'' (regardless of whether it's a CD-ROM drive, DVD drive, etc.).

----

At first, the Ubuntu Live CD would not start at all, this seems to be a problem with the SATA AHCI driver. I had to go into the BIOS and change the SATA driver from ACHI to compatibility (What is the difference? Am I loosing performance?).

----

After you've installed and booted, try the advice from [[Problems_with_SATA_and_Linux]]. Do this:
'''# echo options libata atapi_enabled=1>/etc/modprobe.d/atapienable && update-initramfs -u'''
Then try turning AHCI back on in the BIOS. On a custom-built 2.6.21.5 kernel, my DVD drive appears as /dev/hda and DMA works.
--[[User:Kc8tbe|Kc8tbe]] 12:45, 1 July 2007 (UTC)

If your DVD drive does not appear, modprobe pata-jmicron and ide-generic.
--[[User:Antikristian|Antikristian]] 01:23, 30 July 2007 (UTC)

===NVIDIA Quadro NVS 140M (Solved)===
After initial issues like those explained above in the SATA Issues, I received the xorg error 'fatal error: no screens found'. I was able to boot into Safe Graphics Mode and run the installer, though I had to move both window manager bars to see enough of the install window to use it.

Alternatively, you can download the drivers via wget in a console. Take care to follow the instructions in
[http://www.nvnews.net/vbulletin/showthread.php?t=72490 the NVidia Forum] and uninstall all the packages wit apt-get remove, as described.
Then run the nvidia installer.

Remember that, after you upgrade the kernel, you also have to re-install the drivers.

After installing the NVIDIA drivers, your laptop may not wake after suspend or hibernation. I followed these instructions to fix it [https://help.ubuntu.com/community/NvidiaLaptopBinaryDriverSuspend Ubuntu Community Help].

====Alternative NVIDIA driver installation====
Instead of installing the NVIDIA drivers manually as described above, you can try using [http://www.albertomilone.com/nvidia_scripts1.html Envy]. It automatically installs the latest NVIDIA drivers, and cleans up any previous installations.

=== Intel Graphics Media Accelerator X3100 (Chipset GM965) (Solved)===
After that the CD seemed to boot but the screen was just garbage [http://shadowarts.nonlogic.org/projects/thinkpad/screen_garbage.jpg Picture]. In order to get around that issue I had to go back and download the Alternate CD, which allows you to install in text only mode. From here, the text-only install went okay. Changing the VGA settings on the regular CD worked for me.

When I booted up after the installation, I was still getting the same garbage on the screen. To resolve this I edited my [http://shadowarts.nonlogic.org/projects/thinkpad/xorg.conf xorg.conf] file as shown. I also had to install the latest kernel for Feisty, as the one off of the install disk did have have /dev/agpgart. And I could then use X11. There were still some issues however. The screen seemed somewhat fuzzy. This was a little more challenging of a fix... I found [http://www.spinics.net/lists/xorg/msg25099.html this] mailing list posting, according to it, there was a small glitch in the driver. To fix it:
<pre>
apt-get source xserver-xorg-video-intel
cd xserver-xorg-video-intel-1.9.94/
vim src/i830_lvds.c
Goto line 230 and delete (PFIT_ENABLE | VERT_AUTSCALE ....);, replacing it with 0; then quit vim
dpkg-buildpackage -rfakeroot -uc -b
cd ..
dpkg -i xserver-xorg-video-intel_1.9.94-lubuntu3_amd64.deb (wont be amd64 with a 32-bit install)
</pre>
Now reboot your computer, and it should work. **NOTE: For some reason just restarting X didn't fix it, seems like you must reboot.** At this point you should have a nice, crisp display.

I am still working on aiglx and compiz (switching desktops on a cube doesnt seem to work, though I have some ideas...). There are some issues with OpenGL apps freezing Xorg as well, but the standard 2D desktop works flawlessly.
----
It doesn't seem to be necessary to modify the soruce of xserver-xorg-video-intel anymore, but 3D-acceleration doesn't seem to be stable yet and kdm occasionally needs to be restarted after a login attempt.--[[User:Kc8tbe|Kc8tbe]] 12:49, 1 July 2007 (UTC)

----
I was able to use the normal feisty install disk by changing the SATA setting in BIOS, then change the resolution to 800x600 prior to install, then sudo apt-get update and upgrade, and then sudo apt-get install xserver-xorg-video-intel, then change xorg.conf to match link above and 2D graphics work fine. Jul 18, 2008 - John E
----

It seems that everything works fine when using "apt pinning" and updating the xserver-xorg-video-intel, mesa and other packages to the versions provided by Gutsy. I did the following and the resolution and Compiz Fusion are working fine at the moment. The original source of the steps described below can be found here: [http://techreport.com/forums/viewtopic.php?p=714998#714998]

'''Instructions:'''
* Make a new file /etc/apt/preferences
* In the preferences file, put:
<pre>
Package: *
Pin: release a=feisty
Pin-Priority: 700

Package: *
Pin: release a=gutsy
Pin-Priority: 200
</pre>
* Now, edit your sources.list and copy the main and restricted (and others if you want) repo lines replacing feisty with gutsy:
<pre>
# original
deb http://archive.ubuntu.com/ubuntu feisty main restricted universe multiverse
deb-src http://security.ubuntu.com/ubuntu feisty main restricted universe multiverse

# your addition
deb http://archive.ubuntu.com/ubuntu gutsy main restricted universe multiverse
deb-src http://security.ubuntu.com/ubuntu gutsy main restricted universe multiverse
</pre>
* Now run:
<pre>
sudo apt-get update
sudo apt-get -t gutsy install xserver-xorg-video-intel
sudo apt-get -t gutsy install linux
sudo apt-get -t gutsy install libgl1-mesa-dri
</pre>
* Now reboot.

Probably now you have the weird effect that your GUI is scaled wrong and doesn't fill the full width of the monitor. To fix that, open your xorg.conf and make the following changes:
* Add the following section to your xorg.conf
<pre>
Section "Monitor"
Identifier "TVOutput"
Option "Disable" "true"
EndSection
</pre>
* Then in the "Device" section add the following line:
<pre>
Option "monitor-TV" "TVOutput"
</pre>

That should fix the scaling problem and now everything should work fine.
--[[User:Shuk|Shuk]] 02:26, 10 July 2007 (UTC)

===ThinkFinger===
Ubuntu does not come with a package for thinkfinger. Downloading the most recent source and building it was simple enough: Download most recent version (0.3 at time of writing)
<pre>
sudo apt-get install libpam0g-dev libusb-dev
tar xvzf thinkfinger-0.3.tar.gz
cd thinkfinger-0.3/
./configure --with-securedir=/lib/security --with-birdir=/etc/pam_thinkfinger
make -j5 (hey its dual core!)
sudo make install
sudo ldconfig
</pre>

Configuring it is easy as well, open /etc/pam.d/common-auth:
<pre>
auth sufficient pam_thinkfinger.so
auth required pam_unix.so try_first_pass nullok_secure
</pre>

Create the data directory and set your fingerprint:
<pre>
subo mkdir /etc/pam_thinkfinger
sudo tf-tool --add-user <username>
</pre>
It will all be setup. (I found this somewhere on the web, I wish I could give a source but I'm afraid I cant find it, thank you Anonymous!).

*I am having trouble. I get this error with the last command on the above instructions "tf-tool: error while loading shared libraries: libthinkfinger.so.0: cannot open shared object file: No such file or directory"
*type "ldconfig" as root after make insall. Then the it will work! (pls somebody refresh this article, im not familiar with wiki, sorry)

===HDAPS===
This seems to be working fine now, I just follow the step on [[How_to_protect_the_harddisk_through_APS]]. Using hdaps-gl does the inverse of the accelerometer, though it's not really a big deal, the harddrive protection should still work.

Assuming that the (improved) hdaps code bundled with tp_smapi is being used, editing the transform_axis function in tp_smapi-0.32/hdaps.c will allow for the proper operation of the accelerometer. Assuming that the accelerometer is rotated 90 degrees from its proper orientation (as it is with the X61), the following code will suffice:

<pre>
static void transform_axes(int *x, int *y)
{
int temp = *x;
*x = -*y;
*y = temp;
}
</pre>

For those paying attention in linear algebra, this corresponds to a linear transformation that rotates a 2D coordinate system 90 degrees.
--[[User:Mbsullivan|Mbsullivan]] 04:21, 27 August 2007 (UTC)

Instead of editing the code, you can just pass the inverted=1 parameter when loading the module; modprobe hdaps inverted=1
--[[User:Vegar|Vegar]] 14:40, 17 September 2007 (UTC)

===WiFi===
If you have Intel 4965AGN WiFi card, you have to use ndiswrapper OR use backported kernel from Ubuntu Gutsy (Anybody have howto?) and use following:
http://kuscsik.blogspot.com/2007/06/how-to-install-intel-4965-wireless.html

'''Note:'''
Do not use the latest versions of iwlwifi and mac80211. For me with Gutsy mac80211-8.0.2 and iwlwifi-0.0.42 work with the latest firmware. No further modification needed.

If you have the Atheros card, Ubuntu should automatically install madwifi, which works out of the box
----
Works for me with iwlwifi-4965-ucode-4.44.15, iwlwifi-0.0.34, and mac80211-8.0.1. The catch is, you need to patch your kernel with mac80211, which will fail at compile time with the stock Ubuntu sources. Worked for me with vanilla 2.6.21.5 sources patched for tp_smapi and hdaps protect. Make sure to disable CONFIG_NET_WIRELESS_RTNETLINK in your kernel config.

You can download what you need for for iwlwifi and mac80211 from
http://intellinuxwireless.org .--[[User:Kc8tbe|Kc8tbe]] 13:00, 1 July 2007 (UTC)

Works for me with vanilla kernel v2.6.22.1, ucode 4.44.17, iwlwifi 0.1.2 and mac80211 9.0.2. --[[User:Mbsullivan|Mbsullivan]] 13:40, 24 July 2007 (UTC)

You can also use Kernel 2.6.22.9 and Ubuntu Modules 2.6.22.9 from Gutsy and you will not need to compile anything! Works very well.

===Keyboard/Apostrophe issues (Solved)===
When installing with the alternate CD, Ubuntu asks you if your keyboard as a character that appears to be a quotation mark (this character: "). If you're using a US English keyboard, say no; the character is actually an umlaut. [[User:SteveSims|SteveSims]] 02:15, 19 August 2007 (UTC)

My apostrophe key outputs ´ instead of '. I went to System -> Preferences -> Keyboard and could not figure out how to fix it. [[User:SteveSims|SteveSims]] 21:50, 11 August 2007 (UTC)

:Try switching your keyboard layout to US-Classic, and putting it on the top of the list. After you do that, it works perfectly. --[[User:Adamacious|Adamacious]] 04:29, 13 August 2007 (UTC)

::There is no "US Classic" option. Here's what I have: 
[[Image:Keyboard_options.png]] 
[[User:SteveSims|SteveSims]] 02:17, 15 August 2007 (UTC)

:::It started working, even though I changed nothing. I'm running it as a Macintosh US English keyboard. [[User:SteveSims|SteveSims]] 17:20, 15 August 2007 (UTC)

::::Sorry Steve, what you had to do (and what you did) is select US English, as in the header in the list. It doesn't look selectable, but it is.--[[User:Adamacious|Adamacious]] 20:02, 22 August 2007 (UTC)

===Audio===
====Fixed in Gutsy====
As of 29 August 2007 and [https://bugs.launchpad.net/bugs/122560 this issue], the 2.6.22-10 kernel in Gutsy Gibbon supports audio out-of-the-box (as well as WiFi and other things). Installing the Gutsy kernel via apt and rebooting fixed audio for me, both speakers and headphones. Remaining issues:

* The mute button mutes audio, but doesn't unmute. Pressing volume up or down does unmute it, but has no effect on volume.
* KMix's system tray volume control has no effect because it thinks it's setting the headphones while both outputs are using the speaker settings, but opening KMix and setting the PCM volume works. --lgarfiel

====Python script fix (slightly easier fix)====
First, you have to download the source for the [http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.22.5.tar.gz latest Linux kernel] (2.6.22-5 as of August 26th, 2007) and compile it, something most users cannot do. However, you won't have to compile ALSA and its modules from source if you do it this way.

1) Download the [http://launchpadlibrarian.net/8899521/t61_audio_hack.py T61 audio hack] from [[Launchpad]]. Move it to a convenient folder (e.g., not your desktop). 
2) Go to System -> Preferences -> Sessions -> Startup Programs -> Add. 
3) Name it whatever you want. Choose something simple like "Python audio fix." 
4) Go to Command, and enter the following (with quotation marks):
<pre>gksudo <nowiki>"[THE FOLDER THAT T61_AUDIO_HACK.PY IS IN]</nowiki>/t61_audio_hack.py"</pre>
For example, on my computer, I put t61_audio_hack.py into the /fixes folder in my home folder, so I entered:
<pre>sksudo "/home/sims/fixes/t61_audio_hack.py"</pre> into the Command textbox. 
5) Log out, log back in, and type your password quickly when prompted the second time.

References:
[https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/122560 Launchpad Bug #122560]
[https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/133105 Launchpad Bug #133105]

====ALSA driver update (hard fix, recommended for advanced users)====

:'''''Note: This section assumes a high level of technical proficiency. Please fix it.'''''
::*<s>At [http://www.alsa-project.org www.asla-project.org], did you download only alsa-driver-1.0.14? That and alsa-lib-1.0.14a?</s>
:::Download alsa-driver, alsa-kernel, alsa-lib, and alsa-utils, according to [http://alsa.opensrc.org/index.php/AlsaCVS http://alsa.opensrc.org/index.php/AlsaCVS]. Other sources, however, say only the driver is necessary. Perhaps alsa-project.org simply recommends the other two?
::*''How'' did you compile it from source? ''How'' did you add the patch?
::*In short, please explain ''how'' you did these things in addition to just telling us ''what'' you did. I´m not trying to be rude but seriously, not all Linux users are programmers ;). Thanks. [[User:SteveSims|SteveSims]] 22:19, 11 August 2007 (UTC)
After upgrading to 1.0.14 I still had no sound, and this took about a week to solved (though it was so sadly obvious though). Just upgrading to alsa 1.0.14 will not be enough, there were a few patches released right after the release that fix the Thinkpad's. The reason I missed this was because it was the same day so the release of 1.0.14!

---------------------------------------------------------------------------
VERY SIMPLE METHOD OF MAKING SOUND WORK
http://forums.fedoraforum.org/showthread.php?t=159516&page=1&pp=15
Just follow the instructions step by step, except for two small things:
When doing "cp ../patch_analog.c alsa-driver-1.0.14/alsa-kernel/pci/hda/" use "cp ../patch_analog.c alsa-kernel/pci/hda/" instead
Also, when you get to the part about modifying the modprobe.conf file, it doesn't exist in ubuntu. Adding "options snd-hda-intel index=0 model=thinkpad" to any file (even one you make yourself) inside etc/modprobe.d should work. I personally added it to the options file, and it works fine.

-credit for the guide goes to ciphermonk, and credit to the small changes needed to make this work on ubuntu go to my friend John.

-hotkeys control mic volume, not speaker volume for some reason. I do not know how to fix this

-this fix should provide sound for both headphones and speakers.

-this edit by fatalchaos
---------------------------------------------------------------------------------------

First make sure these packages are installed (System -> Administration -> Synaptic Package Manager) : automake, autoconfig, cvs, libtool, python-dev, build-essential

Then download the source code to the alsa-driver and apply these patches: (links to the revisions)

* [http://hg.alsa-project.org/alsa-kernel/rev/958b39f3e8dd Fix Oops with AD1984 thinkpad model]
* [http://hg.alsa-project.org/alsa-kernel/rev/47ca87407c84 Fix AD1984 basic model]
* [http://hg.alsa-project.org/alsa-kernel/rev/ca37aeeeb0ea Fix Thinkpad X61/T61 outputs]

'''Please use CVS version of ALSA instead. All of these patches are committed'''. The link to the CVS version of ALSA is dead[http://alsa.opensrc.org/index.php/AlsaCVS].

After doing a make and make install reboot your computer (or rrmmod snd-hda-intel && modprobe snd-hda-intel). And run alsamixer (for me it only works as root atm). If you can´t find alsamixer, you can run it in the terminal (Applications -> Accessories -> Terminal) by entering ''alsamixer''. You will have to play with the settings a bit. Make sure the speaker option is not muted and leave the Internal Mic Boost at 0, other wise you will have a really loud microphone feedback sort of sound constantly.

I had to chmod -R 777 /dev/snd/ to get everything work for now. (THIS IS NOT THE CORRECT WAY TO DO IT, IT WILL NOT STAY BETWEEN REBOOTS!).

Audio playback should then work, audio capture (microphone) doesn't seem to work, but I am probably not going to try and fix it, I don't use the capture so I am not concerned with that at the moment.
'''Update:''' With ALSA CVS, microphone seems to work

If you can't hear the mic boost mic settings. Here are my settings at KMix
Output
Mic - low
Mic Boost - full
Input
Mic boost [enable] - medium
capture [enable] - medium

works great with Skype. Also you can use the 'mic level meter' on KRecord to check the mic

In Gnome, default channel mapped to thinkpad volume buttons is MIC, which is bad. Go to ''System->Preferences->Sound->Default mixer tracks'' to change it

'''Please note''' that internal speakers doesn't work with ALSA CVS. Use the headphone jack. Solution?

----
When starting alsamixer over the terminal I couldn't activate the speakers and only had sound over the headphone. However, I figured out how to easily activate the speakers:
* Right-click on your microphone icon in the top panel.
* (If "Mute" is activated, deactivate it. I had that at the beginning and was confused since in alsa you don't really realize it.)
* Click on "Open Volume Control"
* Change to the tab "Switches" and activate the option for speaker.
That should be enough to make it work.
--[[User:Shuk|Shuk]] 02:51, 11 July 2007 (UTC)

I tried those patches, it didnt work for me. But this python script did: http://www.klabs.be/~fpiat/linux/debian/Etch_on_Thinkpad_T61.html#Sound .. apparently if you make the PC speaker play constantly, you cant hear it but you can then hear sound. Hopefully gutsy will fix this :/ --[[User:Rubin|Rubin]] 07:18, 14 July 2007 (UTC)

==Suspend==
Suspending doesn't work by default. It succesfully suspends, but after resuming, Kernel panic occurs. I didn't test hibernate.
I managed to get suspend to ram to work by using this script:

#!/bin/sh

# if launched through a lid event and lid is open, do nothing
echo "$1" | grep "button/lid" && grep -q open /proc/acpi/button/lid/LID/state && exit 0

# remove USB 1.1 driver
rmmod uhci_hcd
rmmod ehci_hcd

# sync filesystem and clock
sync
/sbin/hwclock --systohc

# switch to console
FGCONSOLE=`fgconsole`
chvt 6

# go to sleep
sleep 5 && echo -n "mem" > /sys/power/state

# readjust the clock (it might be off a bit after suspend)
/sbin/hwclock --adjust
/sbin/hwclock --hctosys

# reload USB 1.1 driver
modprobe uhci_hcd
modprobe ehci_hcd

# turn on the backlight and switch back to X
chvt $FGCONSOLE

It's very similar to script posted on thinkwiki, but I had to add ehci_hcd to removed modules and remove some radeon stuff (when using Nvidia)

'''Problems''' the problem with this suspend script is, that after resuming, the laptop is incredibly slow. Applications start about 20 seconds, Firefox is lagging. But processor doesn't run at highest frequency, nothing seems unusual. '''Suggestions?'''

This X-slow-after-resume is still here (T61p, nVidia Quadro FX 570 M, bleeding edge Gutsy 2.6.22-10-generic kernel). However, I found an official OpenSuSE 10.3 for this problem:
[https://bugzilla.novell.com/show_bug.cgi?id=290385]
--[[User:Lech|Lech]] 21:20, 2 September 2007 (UTC)

When using this script, my USB ports are 'dead' after resume (i.e. nothing connected to it gets any power). I have commented out 'rmmod ehci_hcd' and 'modprobe ehci_hcd' lines, to make the USB ports active after a suspend/resume cycle. (this is using nvidia card)

----
Suspend and hibernate work out-of-the-box for me with the 2.6.21.5 kernel, except that you need to put acpi_sleep=s3_bios in the kernel command line (i.e. at the end of each kernel line in /boot/grub/menu.lst).
--[[User:Kc8tbe|Kc8tbe]] 13:03, 1 July 2007 (UTC)

Hmm, with 2.6.21.5 + acpi_sleep=s3_bios, laptop suspends, but resume fails - machine locks up. This is with nvidia 140. Same result when doing it at console. When I resume, I hear a beep and the machine hangs. Have to hard-reset. Suggestions?

Some things seem to break after suspend for me, like network connections time out randomly, cdrom stops working etc. Running 'sudo /etc/init.d/dbus restart' seems to solve it for the most part.

----
We are having similar discussions in Ubunutu's Launchpad, and we found kind of a solution which rules out any 2D/3D graphics acceleration but allows to suspend/resume, at least on my 3 weeks old T61p and some other recent T6x/R6x models:

With thinkpad_acpi 0.16 (!) patches applied to 2.6.22 kernel, and with VESA driver only, it works perfectly so far for us.

The discussion and some links can be found at:
https://bugs.launchpad.net/ubuntu/+bug/139089
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/129125

I know it's not eye candy not to have satisfying GLX etc., but I consider working suspend/resume much more important than say playing with GoogleEarth.

--[[User:Lech|Lech]] 14:48, 16 September 2007 (UTC)

==Brightness==
Changing brightness doesn't work at all. There are many issues. I tried Gutsy and still the same (even worse)

Not a real solution, but if using the vesa driver, brightness control works. ''--Daniel06'' 11:58, 4 July 2007

doesnt work for me with vesa or intel --[[User:Rubin|Rubin]] 06:19, 14 July 2007 (UTC)

It works fine on mine and I have built-in graphics on my motherboard. [[User:SteveSims|SteveSims]] 02:19, 15 August 2007 (UTC)

=== one idea ===
echo "up" >/proc/acpi/ibm/brightness
...works. as does 'down' and 'level x' where x is 1-7. But how to tie that into the buttons? Seems they are currently using something else in /proc that doesnt exist for us. --[[User:Rubin|Rubin]] 06:19, 14 July 2007 (UTC)

=== yet another idea ===

You can add the Gnome power manager brightness applet to the gnome panel, which gives you a GUI tool to do the job, rather than hardware buttons. I don't know about KDE or other window managers. --[[User:Atoponce|Atoponce]] 13:07 22, Aug 2007

=== Another solution for Brightness, using xbacklight and laptop-mode ===

While the hardware buttons still don't work, I have a solution that will automatically raise and lower the backlight when plugged in or on battery.

First, make sure Gnome isn't trying to set the brightness, by going to System > Preferences > Power Management. In the On Battery Power tab, set "Dim display brightness by" to 0%.

Next, install xbacklight.

sudo apt-get install xbacklight

You can manually set the backlight by using "xbacklight -set <number from 1-100>". Note that by using xbacklight, you can make the backlight go brighter or dimmer than normally allowed by Windows or Ubuntu.

To automate brightness changes, first enable laptop-mode

sudo nano /etc/default/acpi-support

Scroll to the bottom and change ENABLE_LAPTOP_MODE to true

ENABLE_LAPTOP_MODE=true

Set laptop mode to start automatically

sudo update-rc.d laptop-mode multiuser

Edit laptop-mode.conf to automate brightness changes. Scroll down to LCD brightness settings. Modify the section to read as follows:

CONTROL_BRIGHTNESS=1

BATT_BRIGHTNESS_COMMAND="xbacklight -set 20"
LM_AC_BRIGHTNESS_COMMAND="xbacklight -set 100"
NOLM_AC_BRIGHTNESS_COMMAND="xbacklight -set 100"
BRIGHTNESS_OUTPUT="/dev/null"

Note: You can use any value from 1 to 100 after -set, I used 20 and 100 as examples. After this, start the laptop-mode daemon, and test if it works. You may have to restart acpid as well.

sudo /etc/init.d/laptop-mode start
sudo /etc/init.d/acpid restart

==Webcam==
The webcam in T61 is some sort of UVC camera: Found UVC 1.00 device Integrated Camera (17ef:1004). The module loads out of the box. I tested the camera using:
Luvcview: http://mxhaard.free.fr/spca50x/Investigation/uvc/luvcview-20070512.tar.gz
Just compile and run using ./luvcview -f yuv (JPG format doesn't work)

I also tried gqcam and webcam, but both doesn't work (first SEGFAULTs, second prints Invalid argument)

luvcview has a button to take pictures. Place your mouse over the buttons at the bottom of the window, and their function is revealed in the title bar. Unfortunately, the button for avi capture does not seem to work (although it does tell you what the video framerate is, which is helpful).

To capture a video stream, run ./luvcview -f yuv -S
To play back the video stream, run mplayer -demuxer rawvideo -rawvideo fps=7:w=320:h=240:yuy2 stream.raw

==64 bit systems issues==
If you are running 64 bit Ubuntu, you will face some problems with 32 bit only proprietary applications. Most of them can be solved.

===Firefox & Flash===
You can use 32bit version of Firefox (see google), or use http://gwenole.beauchesne.info/projects/nspluginwrapper/ nspluginwrapper] which i prefer:
sudo apt-get install ia32-libs ia32-libs-gtk linux32 lib32asound2 alien
Now download both nspluginwrapper rpms (Plugin + Viewer) and convert them:
sudo alien nspluginwrapper*.rpm
sudo dpkg -i nspluginwrapper*.deb

Download Adobe Flash Player: http://fpdownload.macromedia.com/get/flashplayer/current/install_flash_player_9_linux.tar.gz
tar -xvzf install_flash_player_9_linux.tar.gz
cd install_flash_player_9_linux
sudo install libflashplayer.so flashplayer.xpt /usr/lib/firefox/plugins
nspluginwrapper -i /usr/lib/firefox/plugins/libflashplayer.so
cd ~/.mozilla/plugins/
sudo install npwrapper.libflashplayer.so /usr/lib/mozilla-firefox/plugins/
This howto is taken from [http://webzine.smehlik.net/64bit-ubuntu-adobe-flash-plugin-pomoci-nspluginwrapper/ Smehlik Webzine (in Czech)]

===Skype===
Download Skype for Ubuntu Feisty
Use this commandlibdbus, libqt4-core, libqt4-gui, libsigc++ to determine missing libraries:
ldd /usr/bin/skype | grep not
It should be these:
libdbus, libqt4-core, libqt4-gui, libsigc++ (2.0 version)
Download them from http://packages.ubuntu.com (32bit versions!)
mkdir testlibs
dpkg-deb --extract <deb file> testlibs
Now copy everything from testlibs to /usr/lib32
cp -r testlibs/usr/lib/* /usr/lib32
Freedom lovers are advised to avoid proprietary systems like Skype, however. Centralized directories and signalling architectures can't be good for your health.

==Bluetooth==
works for me (TM)

==USB==
A short time after the system has booted, I get a message on the console of every window indicating IRQ# 23 has fired but noone is expecting it. After this message, the USB ports on the right side fail to work anymore. It was suggested on a forum that they will work, its just it takes it a long time to discover there is a new device. I looked in /proc and determined that the bluetooth device is using IRQ23, so it may be involved, but there may be sharing so it could be something else. Regardless, there are USB bus problems with the T61 and linux.

==Overall==
I initially had some big problems getting this working, but now its working quite well. The wifi card worked at startup (uses madwifi) and I am happy because I don't seem to need any proprietary software to run this system.

==Discussion==
In case you missed it the discussion page (for questions/responses) is right here: [[Talk: Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T61]]

==References==
* This guide is listed at the [http://tuxmobil.org/ibm.html TuxMobil Linux laptop and notebook installation guides survey (IBM/Lenovo)].
* Many other suggestions and references can be found in the following ubuntu forum: http://ubuntuforums.org/showthread.php?t=471563

[[Category:Ubuntu 7.04]]
[[Category:T61]]

Tp smapi

2007-09-16T19:41:29Z

Vegar: /* HDAPS axis orientation */ Added note about the inverted parameter

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

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

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

===Features===
*Battery charge/discharge control
*Battery status information

===Project Homepage / Availability===
* Project page: http://tpctl.sourceforge.net/
* You need to [http://sourceforge.net/project/showfiles.php?group_id=1212&package_id=171579 download] only the <tt>tp_smapi</tt> package.

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

For testing, you can simply compile and load the driver within the current
working directory:
:{{cmdroot|tar xzvf tp_smapi-0.32.tgz}}
:{{cmdroot|cd tp_smapi-0.32}}
:{{cmdroot|make load}}

To 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):
:{{cmdroot|1=make load HDAPS=1}}
or, to compile and 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/packages/?category=app-laptop;name=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:

* Configure <tt>hdaps</tt> as module in your kernel
* Add the <tt>HDAPS</tt> use flag in {{path|/etc/make.conf}}
* {{cmdroot|rmmod hdaps}}

Then:

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

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

====Installation on 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-essentials</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. As Ubuntu adds '-generic' to the kernel-version, the following command works for Debian users only:
<pre><nowiki>apt-get install linux-source-`uname -r`</nowiki></pre>
Ubuntu users use the kernel-version they got by the command before, e.g. 'linux-source-2.6.20'

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, please check that there is a symlink from the modules dir to the kernel source:
<pre><nowiki>root@localhost:~#ls -l /lib/modules/2.6.20-16-generic
lrwxrwxrwx 1 root root 28 2007-02-02 08:39 source -> /usr/src/linux-source-2.6.20</nowiki></pre>
Create the link if the line above is not existent:
<pre><nowiki>root@localhost:~#ln -s /usr/src/linux-source-2.6.20 /lib/modules/2.6.20-16-generic/source</nowiki></pre>

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

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

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

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

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

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

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

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

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

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

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

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

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

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

===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 charge stop threshold.

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

The tp_smapi package includes a modified version of the <tt>hdaps</tt> Linux kernel driver used by the [[HDAPS]] system. To use <tt>tp_smapi</tt> and <tt>hdaps</tt> concurrently, you '''must''' use the modified version.

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

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

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

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

===Troubleshooting===

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

===Model-specific status===

<div style="font-size: 92%">
{| border="1" cellspacing="0" cellpadding="2"
|+<tt>tp_smapi</tt> feature support matrix
|-
! colspan=11 style="text-align:center;background:#efefef;" |
=====A series=====
|-
{{tp_smapi/model_status_table_header}}
|-
! {{A22p}} 2629-USG
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cunk}} || || ||
|-
! {{A30}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || ||
|-
! colspan=11 style="text-align:center;background:#efefef;" |
=====G series=====
|-
{{tp_smapi/model_status_table_header}}
|-
! {{G41}}
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || || ||
|-
! colspan=11 style="text-align:center;background:#efefef;" |
=====R series=====
|-
{{tp_smapi/model_status_table_header}}
|-
! {{R31}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cunk}} || || || No SMAPI BIOS
|-
! {{R40}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || || ||
|-
! {{R50}}
| {{Cunk}} || {{Cno}} || {{Cunk}} || {{Cunk}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || ||
|-
! {{R50e}} 1834-JAG
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || ||
|-
! {{R50p}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || ||
|-
! {{R51}} 18*
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes|text=}} X'=X, Y'=Y || 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=}} X'=X, Y'=Y || 0.32 || 1.29 ||
|-
! {{R60}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} ||{{Cyes}} || {{Cunk}} || || ||
|-

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

=====T series=====
|-
{{tp_smapi/model_status_table_header}}
|-
! {{T20}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cunk}} || || || Has SMAPI BIOS but no function is supported. EC LPC3 protocol fails.
|-
! {{T22}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cunk}} || || || Has SMAPI BIOS but no function is supported. EC LPC3 protocol fails.
|-
! {{T23}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || ||
|-
! {{T30}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || ||
|-
! {{T40}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || ||
|-
! {{T40p}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || ||
|-
! {{T41}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || ||
|-
! {{T41p}} 2373-AM9
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cyes}} || {{Cyes|text=}} X'=-X, Y'=-Y || 0.32 || 3.20 || EC v3.04
|-
! {{T42}}
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || ||
|-
! {{T42p}} 2373-KXU
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes|text=}} X'=-X, Y'=-Y || 0.32 || 3.21 || Stop charge threshold works in Windows. dmesg output:
smapi smapi: smapi_request: SMAPI error: Function is not supported by SMAPI BIOS (func=211a)
smapi smapi: __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=}} X'=X, Y'=Y || 0.32 || 1.27 ||
|-
! {{T43p}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || ||
|-
! {{T60}}
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} X'=Y, Y'=-X || 0.32 || ||
|-
! {{T60p}} 8743-CTO
| {{Cunk}} || {{Cunk}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes|text=}} X'=-X, Y'=-Y || 0.32 || ||
|-
! {{T61}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} X'=-X, Y'=-Y || 0.32 || || [http://ubuntuforums.org/showthread.php?p=3146719 ref]
|-
! colspan=11 style="text-align:center;background:#efefef;" |

=====X series=====
|-
{{tp_smapi/model_status_table_header}}
|-
! {{X20}} 2662-31G
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cunk}} || || ||
|-
! {{X24}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || ||
|-
! {{X31}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || ||
|-
! {{X32}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || || ||
|-
! {{X40}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} X'=X, Y'=-Y || 0.32 || 2.08 || EC v1.62
|-
! {{X41}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cno|text=}} X'=X, Y'=-Y || 0.32 || ||
|-
! {{X60}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}} X'=-Y, Y'=X || || 2.07 || EC v1.10, 2.6.20 issue (see discussion)
|-
! {{X61s}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cyes}} || {{Cno|text=}} X'=X, Y'=-Y || 0.32 || || [http://www.slackwiki.org/ThinkPad_X61s ref]
|-
! {{X60T}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cyes}} || {{Cunk}} || || || [http://luke.no-ip.org/x60tablet/ ref] [http://rad.bioinfo.ulaval.ca/hardware/x60tablet ref]
|-
! {{X61T}}
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cyes}} || {{Cyes}} || {{Cno|text=}}X'=-Y, Y'=X || 0.32 || ||
|-
! colspan=11 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=}} X'=X, Y'=Y || 0.32 || ||
|-
! {{Z61t}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || || || [https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/45014 ref]
|}
</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=====
HDAPS axis orientation notation: X,Y are the hardware readouts, X',Y' are horizontal and vertical. You can use [[HDAPS#Visualisation_of_ThinkPad_orientation|hdaps visualisation]] to check for correctness.

If the axis are inverted, you can pass the inverted parameter to the module, like this:
modprobe hdaps inverted=1

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