ThinkWiki - User contributions [en]

How to enable the integrated fingerprint reader with ThinkFinger

2008-11-22T04:21:48Z

Jpeach: /* xscreensaver/gnome-screensaver */

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

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

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

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

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

{{cmdroot|tf-tool --add-user $USERNAME}}

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 --add-user 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}} (you may need to reboot for this to take effect if udev trigger does not work):
#
# 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, edit {{path|/etc/pam.d/gnome-screensaver}} so that it looks like this:
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 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)

How to enable the integrated fingerprint reader with ThinkFinger

2008-11-22T04:20:38Z

Jpeach: /* xscreensaver/gnome-screensaver */

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

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

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

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

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

{{cmdroot|tf-tool --add-user $USERNAME}}

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 --add-user 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}} (you may need to reboot for this to take effect if udev trigger does not work):
#
# 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, edit {{path|/etc/pam.d/gnome-screensaver}} so that it looks like this:
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 Intrep 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 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)

Installing Ubuntu 8.10 (Intrepid Ibex) on a ThinkPad T61

2008-11-22T04:12:12Z

Jpeach: /* Fingerprint Reader with ThinkFinger */

NOTE: I copied the 8.04 document and created this one with the information. Please help to update it so it accurately reflects 8.10.

== Items that work out of the box ==

'''Intel Video:''' 2D and 3D acceleration works

'''Nvidia Video:''' 2D and 3D acceleration works

'''Wireless:''' Intel cards tested. Atheros cards also works.

'''Wireless WAN:''' Cingular/AT&T card tested.

'''Network Card:''' Intel 10/100/1000 tested

'''Wireless switch:''' Tested (Only has an effect over the bluetooth, wifi is unaffected)

'''Webcam:''' Tested with cheese and skype.

'''Headphones:''' Works out of the box

'''Microphone:''' Just needs to be activated, see section [[#Audio|below]]

'''Keyboard Shortcuts:''' Most of them work out of the box, some need to be activated, see section [[#Multimedia_Keys|below]]

'''Fingerprint Reader:''' With ThinkFinger, not as functional after upgrade (need to hit 'Enter'), see below

== Items that need (some) tweaking to obtain full functionality ==

=== Open Source Intel Wifi Driver ===
The following information is important if you are upgrading from a previous version (2007 or earlier) of Ubuntu to 8.10.

Intel has created a new Linux Wifi driver project for Intel Wireless cards, "[[Iwlwifi]]". This driver is Open Source and no longer requires the Intel daemon to run in addition. This project will support the [[:Category:T61 | T61]]'s Wifi [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter | Intel 3945ABG network adapter]] and [[Intel PRO/Wireless 4965AGN Mini-PCI Express Adapter| Intel 4965AGN network adapter]].

An automatic migration will occur when upgrading from [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61|Ubuntu 7.10]] to Ubuntu 8.04. However, there is a caveat to be aware of:
* The new driver wants to name the interface wlan0 (by default -- you can rename it to anything you want), and requires a different entry in {{path|/etc/udev/rules.d/70-persistent-net.rules}}, which handles the naming of interfaces. Simply edit this file and delete your old entry for the ipw3945 driver, then unload/reload the new driver, or simply reboot. A new entry will automatically be created that is appropriate for the new driver. Here's an example of the lines to delete:
<pre>
# PCI device 0x8086:0x4227 (ipw3945)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1b:77:a4:0e:2f", NAME="eth1"
</pre>

If you need to perform a manual migration, the Ubuntu Help Community has written some [https://help.ubuntu.com/community/WifiDocs/Driver/iwlwifi_Intel_3945_4965/gutsy documentation] that will make this very easy to do.

An additional note
'''System lock-ups with Intel 4965 wireless'''

The version of the iwlagn wireless driver for Intel 4965 wireless chipsets included in Linux kernel version 2.6.27 causes kernel panics when used with 802.11n or 802.11g networks. Users affected by this issue can install the linux-backports-modules-intrepid package, to install a newer version of this driver that corrects the bug. (Because the known fix requires a new version of the driver, it is not expected to be possible to include this fix in the main kernel package.)
http://www.ubuntu.com/getubuntu/releasenotes/810

=== Network connection after suspend/resume ===
Networking may not work after a suspend or resume operation, this is because of the ath_pci driver and can be worked around by creating the file {{path|/etc/pm/config.d/madwifi}} and adding the single line
<pre>
SUSPEND_MODULES=ath_pci
</pre>
which causes the driver to be unloaded on suspend and reloaded on resume.

=== Fingerprint Reader with ThinkFinger ===
Here are the general instruction on [http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger how to enable the fingerprint reader with ThinkFinger]

If you are having a problem you may need to modify the following.

1. Open up your xorg.conf file:
sudo nano /etc/X11/xorg.conf
2. Add to it (or uncomment if it’s already there):
Section “InputDevice”
Identifier “Generic Keyboard”
Driver “kbd”
Option “XkbRules” “xorg”
Option “XkbModel” “pc105″
Option “XkbLayout” “us”
EndSection
3. Under Section “ServerLayout”, add:
InputDevice “Generic Keyboard”
From: [http://www.eastwoodzhao.com/ubuntu-810-intrepid-ibex-thinkfinger-fingerprint-reader/ Ubuntu 8.10 Intrepid Ibex - ThinkFinger Fingerprint Reader]

Note: this temporary fix appears to get in the way of Thinkpad keyboard configurations. With the method applied, the up arrow becomes "print screen" and volume buttons stop working.

Another solution is available at the T61p Ubuntu 8.10 page.

=== Emulate Wheel (Middle-click scrolling) ===
[http://mvogt.wordpress.com/2008/08/15/xorg-evdev-and-emulatewheel/ Michael Vogt described] how to get middle-click scrolling to work again in Intrepid. Xorg.conf is not used to configure mice and keyboards anymore, but evdev is. This makes the configuration of middle-click scrolling a little bit different than previous versions of Ubuntu. In terminal:
<pre>
sudo gedit /etc/hal/fdi/policy/mouse-wheel.fdi
</pre>
Past and save the following code, which will give vertical wheel emulation only:
<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.ZAxsisMapping" type="string">4 5</merge>
<merge key="input.x11_options.Emulate3Buttons" type="string">true</merge>
</match>
</pre>
There is [http://psung.blogspot.com/2008/09/scrolling-with-thinkpads-trackpoint-in.html another method] to get horizontal scrolling as well, but I don't think it worked for me.

[[Category: Ubuntu 8.10]]
[[Category: T61]]

Installing Ubuntu 8.10 (Intrepid Ibex) on a ThinkPad T61

2008-11-22T03:39:41Z

Jpeach: /* Fingerprint Reader with ThinkFinger */

NOTE: I copied the 8.04 document and created this one with the information. Please help to update it so it accurately reflects 8.10.

== Items that work out of the box ==

'''Intel Video:''' 2D and 3D acceleration works

'''Nvidia Video:''' 2D and 3D acceleration works

'''Wireless:''' Intel cards tested. Atheros cards also works.

'''Wireless WAN:''' Cingular/AT&T card tested.

'''Network Card:''' Intel 10/100/1000 tested

'''Wireless switch:''' Tested (Only has an effect over the bluetooth, wifi is unaffected)

'''Webcam:''' Tested with cheese and skype.

'''Headphones:''' Works out of the box

'''Microphone:''' Just needs to be activated, see section [[#Audio|below]]

'''Keyboard Shortcuts:''' Most of them work out of the box, some need to be activated, see section [[#Multimedia_Keys|below]]

'''Fingerprint Reader:''' With ThinkFinger, not as functional after upgrade (need to hit 'Enter'), see below

== Items that need (some) tweaking to obtain full functionality ==

=== Open Source Intel Wifi Driver ===
The following information is important if you are upgrading from a previous version (2007 or earlier) of Ubuntu to 8.10.

Intel has created a new Linux Wifi driver project for Intel Wireless cards, "[[Iwlwifi]]". This driver is Open Source and no longer requires the Intel daemon to run in addition. This project will support the [[:Category:T61 | T61]]'s Wifi [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter | Intel 3945ABG network adapter]] and [[Intel PRO/Wireless 4965AGN Mini-PCI Express Adapter| Intel 4965AGN network adapter]].

An automatic migration will occur when upgrading from [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61|Ubuntu 7.10]] to Ubuntu 8.04. However, there is a caveat to be aware of:
* The new driver wants to name the interface wlan0 (by default -- you can rename it to anything you want), and requires a different entry in {{path|/etc/udev/rules.d/70-persistent-net.rules}}, which handles the naming of interfaces. Simply edit this file and delete your old entry for the ipw3945 driver, then unload/reload the new driver, or simply reboot. A new entry will automatically be created that is appropriate for the new driver. Here's an example of the lines to delete:
<pre>
# PCI device 0x8086:0x4227 (ipw3945)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1b:77:a4:0e:2f", NAME="eth1"
</pre>

If you need to perform a manual migration, the Ubuntu Help Community has written some [https://help.ubuntu.com/community/WifiDocs/Driver/iwlwifi_Intel_3945_4965/gutsy documentation] that will make this very easy to do.

An additional note
'''System lock-ups with Intel 4965 wireless'''

The version of the iwlagn wireless driver for Intel 4965 wireless chipsets included in Linux kernel version 2.6.27 causes kernel panics when used with 802.11n or 802.11g networks. Users affected by this issue can install the linux-backports-modules-intrepid package, to install a newer version of this driver that corrects the bug. (Because the known fix requires a new version of the driver, it is not expected to be possible to include this fix in the main kernel package.)
http://www.ubuntu.com/getubuntu/releasenotes/810

=== Network connection after suspend/resume ===
Networking may not work after a suspend or resume operation, this is because of the ath_pci driver and can be worked around by creating the file {{path|/etc/pm/config.d/madwifi}} and adding the single line
<pre>
SUSPEND_MODULES=ath_pci
</pre>
which causes the driver to be unloaded on suspend and reloaded on resume.

=== Fingerprint Reader with ThinkFinger ===
Instructions on how to set up the fingerprint reader can be found at [http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger]

If you are having a problem you may need to modify the following.

1. Open up your xorg.conf file:
sudo nano /etc/X11/xorg.conf
2. Add to it (or uncomment if it’s already there):
Section “InputDevice”
Identifier “Generic Keyboard”
Driver “kbd”
Option “XkbRules” “xorg”
Option “XkbModel” “pc105″
Option “XkbLayout” “us”
EndSection
3. Under Section “ServerLayout”, add:
InputDevice “Generic Keyboard”
From: [http://www.eastwoodzhao.com/ubuntu-810-intrepid-ibex-thinkfinger-fingerprint-reader/ Ubuntu 8.10 Intrepid Ibex - ThinkFinger Fingerprint Reader]

Note: this temporary fix appears to get in the way of Thinkpad keyboard configurations. With the method applied, the up arrow becomes "print screen" and volume buttons stop working.

Another solution is available at the T61p Ubuntu 8.10 page.

=== Emulate Wheel (Middle-click scrolling) ===
[http://mvogt.wordpress.com/2008/08/15/xorg-evdev-and-emulatewheel/ Michael Vogt described] how to get middle-click scrolling to work again in Intrepid. Xorg.conf is not used to configure mice and keyboards anymore, but evdev is. This makes the configuration of middle-click scrolling a little bit different than previous versions of Ubuntu. In terminal:
<pre>
sudo gedit /etc/hal/fdi/policy/mouse-wheel.fdi
</pre>
Past and save the following code, which will give vertical wheel emulation only:
<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.ZAxsisMapping" type="string">4 5</merge>
<merge key="input.x11_options.Emulate3Buttons" type="string">true</merge>
</match>
</pre>
There is [http://psung.blogspot.com/2008/09/scrolling-with-thinkpads-trackpoint-in.html another method] to get horizontal scrolling as well, but I don't think it worked for me.

[[Category: Ubuntu 8.10]]
[[Category: T61]]

How to enable the integrated fingerprint reader with ThinkFinger

2008-11-08T04:57:40Z

Jpeach: /* Intrepid */

[[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/video/Fingerabdruck_Hack/fingerabdruck.mpg?language=en Video tutorial for forging fingerprints]

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

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

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

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

{{cmdroot|tf-tool --add-user $USERNAME}}

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 --add-user 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}} (you may need to reboot for this to take effect if udev trigger does not work):
#
# 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, edit {{path|/etc/pam.d/gnome-screensaver}} so that it looks like this:
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}}
# 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 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)

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T60

2008-05-06T00:14:34Z

Jpeach: /* Open Source Intel Wifi Driver */

== Features ==
=== Open Source Intel Wifi Driver ===
Intel has created a new Linux Wifi driver project for Intel Wireless cards, "[[Iwlwifi]]". This driver is Open Source and no longer requires the Intel daemon to run in addition. This project will support the [[:Category:T60 | T60]]'s Wifi [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter | 3945ABG network adapter]].

Automatic migration should occur when upgrading from [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a Thinkpad T60 | Ubuntu 7.10]] to Ubuntu 8.04. After the upgrade you can check to see if the iwlwifi driver is running by:

$ modprobe -l | grep iwlwifi
/lib/modules/2.6.24-16-generic/ubuntu/wireless/iwlwifi/iwlwifi/compatible/iwl4965.ko
/lib/modules/2.6.24-16-generic/ubuntu/wireless/iwlwifi/iwlwifi/compatible/iwl3945.ko
/lib/modules/2.6.24-16-generic/ubuntu/wireless/iwlwifi/mac80211/compatible/net/mac80211/iwlwifi_mac80211.ko
/lib/modules/2.6.24-16-generic/ubuntu/wireless/iwlwifi/mac80211/compatible/net/mac80211/iwlwifi_rc80211_simple.ko

If it does not and a migration is desired, Ubuntu Help Community has written some [https://help.ubuntu.com/community/WifiDocs/Driver/iwlwifi_Intel_3945_4965/gutsy documentation] that will make this very easy to do.

You may have trouble connecting to some access points as described in [https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.22/+bug/176602 this bug report]. I was connecting with WPA2 just fine at home and then went away on a trip and couldn't connect to an ''unencrypted'' network! The fix as described there is to install the linux-backports-modules-hardy package, which contains an updated driver.

=== Increased power savings ===
This release includes Linux-2.6.24, which has [[dynticks]] support. The power savings that have been available to 32-bit systems are now brought to 64-bit systems. This will have an effect on those T60 laptops with an [[Intel Core 2 Duo (Merom)]]. To get the most of [[dynticks]] it is a good idea to install powertop with {{cmduser|sudo aptitude install powertop}} and take the advice it gives when you invoke it. Powertop may recommend that you use [http://www.lesswatts.org/tips/disks.php SATA Link Power Management], in which case you'll want [[Suspend/Resume_Support_For_SATA_Link_Power_Management|this script]] to avoid long delays when resuming from suspend.

More information on power saving is available at http://www.lesswatts.org.

== Installation ==

my thinkpad: T60 with [[Intel Graphics Media Accelerator 950]] (WXSGA 1680x1050 display), atheros wireless card, 2GHz [[Intel Core 2 Duo (Merom)]].
poliahu $ lspci
00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA AHCI Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)
02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller
03:00.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)
15:00.0 CardBus bridge: Texas Instruments PCI1510 PC card Cardbus Controller
poliahu $

I booted on the Hardy Heron alpha 4 liveCD and installed from there on a 5GB primary ext3 partition.
No problem whatsoever during liveCD session and install. Everything went smooth. I have my home on a separate partition of course, and I created a "hardy" user just to play around.

=== Known Issues ===

====EXA issues with intel graphic card driver (945, 965)====

Hardy comes with the newest Xorg:

root@poliahu:/# Xorg -version
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
X.Org X Server 1.4.0.90
Release Date: 5 September 2007
X Protocol Version 11, Revision 0
Build Operating System: Linux Ubuntu (xorg-server 2:1.4.1~git20080131-1ubuntu3)
Current Operating System: Linux poliahu 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686
Build Date: 19 February 2008 04:52:29PM
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
root@poliahu:/#

and with X autoconfiguration (as far as I understand). So hardy installs a xorg.conf, but it is barebones. Most of the config is handled internally by the new server, and is handled fairly well. My screen and card were recognized, it configured it with the correct driver and resolution. I had 3D accel out of the box too, so that compiz was working without any tinkering. All good up to there.

The only problems I encountered in X (once more, this is only applicable to intel graphic hardware) were

(1) the trackpad was working but the scroll function was not (in previous version of ubuntu, moving your finger up and down in the right part of the trackpad would provide this functionality, here not). This is apparently a known regression (can't find the reference, but read it in some launchpad or ubuntu forum post). As it is a known regression, I assume it will be fixed for the final hardy release (?).

(2) The intel driver config adopted by default by the new xorg uses EXA acceleration, which is newer and performs overall better than the XAA. The problem is that on some intel hardware, it performs quite poorly for text processing. I noticed that immediately: when I had no window, or only a terminal around, compiz would be its usual smooth (e.g. when rotating cube or moving windows). With a few windows open, with text (e.g. firefox), compiz would be very jumpy / choppy. Copying over the xorg.conf form my gutsy installation and adding:
Option "AccelMethod" "XAA"
in the "Device" section (where the video intel driver is specified) solved the problem, and now I'm back to the old smooth compiz animations.

Using this -otherwise unmodified xorg.conf- had the side effect of killing my trackpad entirely. Now It's not responsive at all. Again, I expect these things will be ironed out for the final release. Another possibility would be to only add the XAA AccelMethod in the existing xorg.conf (hardy default), but I did not know nor researched how to do that.

[update 2008feb23: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/177492 describe the above problem. It turns out that there is another solution, keeping EXA. Keep the stock xorg.conf (the barebone one installed by default with hardy -clean install-. Just add:
Option "AccelMethod" "EXA"
Option "ExaNoComposite" "false"
Option "MigrationHeuristic" "greedy"

in the Section "Device" (so don't put XAA). With these settings, acceleration is smooth across the board (including wiht fonts) and compiz works like a charm. Cherry on the pie: you'll have XV (hardware video), so this means nice and smooth DVD and movie playing, much lighter cpu load, etc... compared to the x11 (software) video driver. As an extra, you can also use the INTEL_BATCH flag, which was reported by the vast majority of intel users to speed up graphical performance significantly (30%+). Put
INTEL_BATCH="1"
in your /etc/environment (I read you can also put it in your .bashrc, but I didn't try that). end update 2008feb23]

==== Multimedia keys don't work with Exaile ====

Another problem I noticed was that the multimedia keys were not operating in exaile. I haven't tested them in rythmbox or other apps.

Apart from that, everything I tested was fine: display, network (wired and wireless), sound (pulseaudio sounds noticeably better, but may be it's self induced), suspend (which worked for a couple of tests, and then I installed uswsusp -s2ram- 0.8, which has always been more reliable for me), haven't tried hibernate, nor bluetooth.

== Post-Installation Setup ==

== Notes ==

== See also ==

== References ==
* [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a Thinkpad T60]]

== External links ==

[[Category: T60]] [[Category: Ubuntu 8.04]]

Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61

2007-12-30T20:19:49Z

Jpeach: /* Fingerprint Reader */

==Introduction==

This document outlines configuring Ubuntu 7.10 (Gutsy Gibbon) on your Thinkpad T61. Most items will work out of the box and a base install should provide you with a completely working system. Due to the modular nature of the T61 there are many different configuration, please read carefully and only make the changes specific to your system.

Feel free to update this Wiki with your information however please ask questions on the Talk page.

==Installation Notes ==

*If booting with the live CD gives you a blank screen you should select the "Safe Graphics" menu choice.

== Display/Video ==

=== Accelerated Video and Desktop Effects ===
'''Intel''' 2D and 3D accelerated video work out of the box.

Due to [https://bugs.launchpad.net/xorg-server/+bug/111257 | bug 111257], compiz is disabled on the Intel i965 based video cards. All systems updated after 11/24/2007 should be fixed.

'''Nvidia''' 2D video works out of the box, to enable accelerated 3D support click System->Administration->Restricted Drivers Manager {{NOTE| If the Restricted Drivers Manager fails to install the driver you can use the Envy tool from: http://albertomilone.com/nvidia_scripts1.html. This tool is unsupported and the only supported method of installing the Nvidia drivers is via Synaptics and the Restricted Drivers Manager}}

===Multiple Monitors===

If you previously used Xinerama this is no longer a supported option, you should use one of the tools described below to configure dual displays.

====Nvidia N140m:====

When using the default drivers (The open source "nv" drivers) you can use Administration->"Screens and Graphics" to setup the second monitor

Using the proprietary drivers you must use the Nvidia tool located at Applications->System Tools-> Nvidia X Server Settings.

Note:
Twinview 'works' but doing anything with Twinview in fullscreen mode will cause it to span both monitors instead of just being on the second. This essencially kills the functionality of Twinview.

eg 1 --> you are an office working bringing your notebook to work to show a presentation but you can't use full screen.

eg 2 --> you want take your notebook to a friends house to watch a movie on his/her projector and fullscreen mode gets half displayed on the projector and half on the notebook monitor.

If you experience problems getting a working Twinview setup using nvidia-settings, please see [http://www.nvnews.net/vbulletin/showthread.php?t=101780 this thread]

====Intel X3100====

Plugging in an external monitor works, but is a clone of the built-in LCD by default. Using the Screens and Graphics tool located under Administration you can setup the second monitor as an extension of the existing screen or a clone for presentations, but it does not let you enable a second display on a second monitor.

'''Setting up dual monitors via the command line'''

If you like doing it via the command line and are using the Intel drivers or the open-source "nv" driver you can use this example (''Note all this should be possible using the Screens and Graphics tool so only make this change if you prefer the command line method''):

This is an example for a 1680x1050 built-in LCD and a 1600x1200 external LCD:
Add a "Virtual 3280 1200" line in the Display SubSection of the Screen Section in your xorg.conf:

Go to Applications -> Accessories -> Terminal and type the following:

{{cmdroot|sudo /etc/init.d/gdm stop}}

{{cmdroot|xrandr --output LVDS --auto}}

To set the built-in LCD to ouput 1680x1050

{{cmdroot|xrandr --output VGA --right-of LVDS}}

To extend the desktop

=== Fonts on High-Res Screens ===

On high-res screens (e.g. 15" 1680x1050), some users consider the default fonts too be too large ([https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/99145 Launchpad bug report]). You can fix this by following these steps:

# Open System->Preferences->Appearance
# Select the "Fonts" tab
# Click the "Details" button (lower right)
# Adjust the Resolution down to 96dpi
# Make sure you have Subpixel (LCD) Smoothing enabled
# Save the preferences

If you also want small fonts on the GDM login window, you can do this:

# Open System->Administration->Login Window
# Select the 'Security' tab
# Click the 'Configure X-Server' button
# Append '-dpi 96' (without quotes) to the text in the 'Command' field
# Reboot the computer.

=== Brightness ===
====Intel X3100:====
The brightness controls should work out of the box on a fresh install.

====Nvidia Quadro N140 and 570M:====
The brightness controls do not work out of the box, however you can switch to a virtual terminal (ctrl+alt+F1) increase or decrease the brightness and then switch back to X (ctrl+alt+F7) without disrupting the running applications (You should save anything open just to be safe). There is a new [http://www.nvidia.com/object/linux_display_ia32_169.04.html beta-driver (version 169.04)] by nvidia that fixes the brightness-controls. To install this driver use the Envy tool described above.

== Audio ==

=== Inextricably Linked to the Modem ===
Make sure that you have the modem enabled in the BIOS. If it is disabled, you may discover that your audio is also disabled. In this situation, your drivers may still load, but you will get an error message whenever you try to play audio.

===Enabling Audio controls===

By default, the sound may be disabled and the volume control buttons on the laptop (up by the ThinkVantage button) and the volume control applet (up by the clock) will not control the speaker volume (they actually control the microphone). To fix this:

# Right-click on the volume control applet (by the clock) and select "Open Volume Control"
# In the "Switches" tab, make sure "Headphone" and "Speaker" are both checked.
# Close the Volume control.
# Right-click on the volume control applet again and select "Preferences".
# Make sure the device is set to "HDA Intel (Alsa mixer)" and highlight the "PCM" option.
# Close the preferences.
# Select System->Preferences->Sound.
# In the "Default Mixer Tracks" section, make sure "PCM" is highlighted.
# Close the sound preferences.

You should now hear sound and be able to control the volume using the laptop buttons or volume applet.

A recent BIOS update [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-67989] fixes the mute button, you can then configure it to mute/unmute audio in Keyboard Shortcuts.

===Microphone===

There have been reports that the microphone may not work, please add your input to the talk page [http://www.thinkwiki.org/wiki/Talk:Installing_Ubuntu_7.10_%28Gutsy_Gibbon%29_on_a_ThinkPad_T61#Microphone] and update this section when a consensus on the problem and solution has been reached.

===Sound Cracking===

There have been intermittent reports of users experiencing cracking when listening to audio. Here are a few possible solutions:

* Try to switch to the OSS driver in system => preference => sound => devices => Music and movies, select OSS - Open sound system (instead of ALSA)

* If this issue is only occurring for Rhythmbox go to Edit > Preferences > Playback > and Check "Use Crossfading Backend". Restart Rhythmbox and you should have better audio quality.

* Check that the microphone is muted and modify your mixer settings by moving items like PCM down halfway and see if the cracking goes away.

===Hissing===
Some users experience hissing during playback, and even when idle. To solve this mute the microphone when it is not in use:

# Run "alsamixer" in the terminal.
# Arrow over to "Mic", and hit "M" to mute.
# Arrow over to the first "Docking", and hit "M" to mute.
# Arrow to the first "Internal", and hit "M" to mute.

Now, make sure that "Headphone" and/or "Speaker" are _not_ muted, and that "PCM" is at a reasonable level (say ~70) so you don't make your ears bleed, and try playing something back. ''(<Esc> will exit alsamixer)''

== Modem ==

The modem works with the Linuxant drivers available at http://www.linuxant.com

==Bluetooth==
Bluetooth works out of the box. Pressing Fn-F5 once will enable bluetooth, disable wireless, pressing again, enable both and pressing one more time will disable bluetooth.

If you would like to set bluetooth state independently the script below determines the current bluetooth state and toggles the device on or off.

First create a new file named bluetooth-toggle:
{{cmdroot|sudo touch /usr/sbin/bluetooth-toggle}}

Now open a editor:
{{cmdroot|sudo gedit /usr/sbin/bluetooth-toggle}}

Paste the following script:

#!/bin/bash
cat /proc/acpi/ibm/bluetooth | awk '{ print $2 }' | while read line;
do
if [ $line == "enabled" ]; then
echo disable > /proc/acpi/ibm/bluetooth
else
echo enable > /proc/acpi/ibm/bluetooth
fi
break
done

Now set the execute permissions:
{{cmdroot|sudo chmod +x /usr/sbin/bluetooth-toggle}}

You can invoke the script out of the console by typing sudo bluetooth-toggle or create a menu icon by using the menu editor under preferences using gksudo bluetooth-toggle as command line.

== Fingerprint Reader ==

The reader works with ThinkFinger. General instructions available [http://www.thinkwiki.org/wiki/Integrated_Fingerprint_Reader here] and [https://wiki.ubuntu.com/ThinkFinger here].
Instructions in French available at http://doc.ubuntu-fr.org/materiel/thinkfinger

Note that ThinkFinger in it's current version does not work with KDE and Kubuntu in any way (it crashes KDM and is not integrated at all).

Prebuilt packages are available from jldugger using Launchpad's PPA:

Add the thinkfinger package repository by creating {{path|/etc/apt/sources.list.d/thinkfinger.list}} with these two lines:

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

Then update the package database and install packages:

{{cmduser|sudo apt-get update}}
{{cmduser|sudo apt-get install libpam-thinkfinger libthinkfinger-dev libthinkfinger-doc libthinkfinger0 thinkfinger-tools}}

After the package is installed edit {{path|/etc/pam.d/common-auth}} and replace the line

auth required pam_unix.so nullok_secure

with

auth sufficient pam_thinkfinger.so
auth required pam_unix.so try_first_pass nullok_secure

Edit {{path|/etc/modules}} and add the following line:

uinput

Load the module manually for this session:

{{cmduser| sudo modprobe uinput}}

Summary:
* Recording fingerprints works
* Login works
* The password must be entered to unlock a locked screensaver
* sudo works
* gksu and gksudo hang : for example it is necessary to run synaptic twice and enter your password upon failure. To be able to use the Finger print reader in the session subsequently, kill the hanging gksu/gksudo process. A workaround is editing the Gnome System Menu (alacarte) to specify sudo instead of gksu/gksudo for the launching command and choose type "Application in Terminal" : this opens an extra terminal window for each superuser application you want to use though.

== Trackpad scrolling ==

Trackpad scrolling works out of the box in the standard thinkpad way: Slide your finger up and down the very right edge of the trackpad.
Note that /etc/X11/xorg.conf will be changed and the edge scrolling will be disabled after running nvidia-xconfig , copy the trackpad section from the backup of xorg.conf

To enable using the middle mouse button to scroll, add the following lines to the "Configured Mouse" section in
{{path|/etc/X11/xorg.conf}}:

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

== Hibernate/Suspend ==

=== Blank screen fix for intel graphics cards===

This fix is for Intel Graphics Cards only.

You may get a blank screen when resuming from suspend or hibernate ([https://bugs.launchpad.net/ubuntu/+bug/134391 Launchpad bug report]). To fix this:

1) Go to the in Applications -> Accessories -> Terminal

2) Enter "sudo nautilus" without the quotation marks.

3) Go to {{path|/boot/grub/}}, backup and then edit {{path|menu.lst}} by adding "acpi_sleep=s3_bios" (no quotes) to the "defoptions" list so that it looks something like this:

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash '''acpi_sleep=s3_bios'''

4) Once you have edited the line and added the acpi_sleep parameter, you need to run

<pre>sudo update-grub</pre>

in the terminal.

Note that if you get the blank screen upon resume, a quick-fix is to switch to a console (Ctrl-Alt-F1) and then back to X (Ctrl-Alt-F7). This will usually bring the display back to life. However, the long-term fix is to add the acpi_sleep parameter as shown above.

=== How to Suspend with nVidia 140m/570m ===

The suspend to RAM will work with the nVidia card and the proprietary drivers, but it requires some file editing. It did not work for me out of the box. Using the package manager, download and install the latest nVidia drivers (100.14.19+2.6.2.4-12.4 at time of writing). I also had to use the 2.6.22-12-generic kernel image (the 2.6.22-13 image did not work with this driver --- I'm assuming it has to match wit the nVidia version, but I am not an expert).

Once you have it installed and working, you have to make a change to {{path|/etc/default/acpi-support}}. Open the file in your favorite editor and change the following lines:

$ sudo nano /etc/default/acpi-support

{{path|/etc/default/acpi-support}}
# Should we save and restore state using the VESA BIOS Extensions?
SAVE_VBE_STATE=false
...
# Should we attempt to warm-boot the video hardware on resume?
POST_VIDEO=false
...
# Set the following to "platform" if you want to use ACPI to shut down
# your machine on hibernation
HIBERNATE_MODE=platform

This allowed me to suspend and resume, but after two suspends the wireless wouldn't work anymore. Theoretically, ACPI unloads the network drivers before suspending, but it doesn't seem to work correctly so I added these to the blacklist modules manually (in the same file as above:

{{path|/etc/default/acpi-support}}
# Add modules to this list to have them removed before suspend and reloaded
# on resume. An example would be MODULES="em8300 yenta_socket"
#
# Note that network cards and USB controllers will automatically be unloaded
# unless they're listed in MODULES_WHITELIST
MODULES="iwl4965 iwlwifi_mac80211 cfg80211"

Your wifi modules may be different. (I have the intel AGN wireless card -- I don't know if these modules are different for other cards.)

This allows me to suspend to ram; I haven't had any problems with it so far. I haven't gotten hibernate (suspend to disk) working, so there may be additional things you need to do for that. (I think part of my problem is that I don't have enough swap, but I don't care enough to actually fix it.)

If the system has been left in suspend off for a while, wireless might not reconnect at all (Thinkpad T61 8892-02U). Restarting netapplet
solves the problem.

{{path|/etc/default/acpi-support}}
# Add services to this list to stop them before suspend and restart them in
# the resume process.
STOP_SERVICES="netapplet"

/*The fix does not work for me. I have a T61 7664-17U(NVS 140m, 4965agn). The computers suspend, but when it wakes up it hangs up and I have to pull out the battery to restart it.*/

General hint: Do not install the package "hibernate" or "uswsusp" or the gnome-power-manager will fail to suspend/hibernate your computer. If you have installed the package don't forget to purge the configuration. (sudo apt-get remove hibernate --purge, uswsusp resp.)

The instructions for Intel video card recommends adding "acpi_sleep=s3_bios" to the kernel parameters in Grub configuration. According to a comment on [https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/139089 Launchpad BUG 139089], the correct setting for Nvidia is "acpi_sleep=s3_mode". Once I changed this, Suspend to ram worked. I have the T61 6459-CTO.

== Items that work out of the box ==

'''Intel Video:''' 2D and 3D acceleration works

'''Nvidia:''' 2D works, 3D requires the installation of the proprietary drivers

'''Wireless:''' Atheros and Intel cards both tested.

'''Bluetooth:''' Tested with both a bluetooth headset and an HTC 8525

'''Network Card''' Intel 10/100/1000 tested

'''Firewire''' Tested with hard drive

'''Wireless switch'''

'''4-in-1 card reader'''

'''Webcam'''

'''Headphones''' You may need to enable Headphone out: Right-click on the volume control and select open volume control. Click the switches tab and then check the headphones box.

'''Keyboard Shortcuts:'''
* Fn-PgUp activates/deactivates the thinklight
* Fn-Up will trigger stop on a media player
* Fn-Down will toggle pause and play on a media player
* Fn-Left/Right go to prev/next tracks on a media player
* Fn-F2 properly locks the screen
* Fn-F3 shows remaining battery >>does not work on all machines<<
* Fn-F4 suspends (to ram)
* Fn-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

'''Docking Stations:'''

All docking station models should work and the following features have been tested:

* DVI or Analog video: You can switch to it using "Administration->Screens and Graphics", if you are using the proprietary Nvidia drivers you must use the Nvidia Control Panel.

* Network Pass-through

* Modem Pass-through

* USB ports: Connected upon docking

* PS/2 Ports

== Items that don't work ==

=== Interrupt problem (PROBABLY SOLVED) ===
This bug is supposed to be solved by updating the system BIOS to the [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-67989 2.07]-Version (with 1.08 AMT). Still testing...
* https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/126369
* USB ports can end up temporarily disabled
* Wifi can break
* integrated cardreader can be disabled
* bluetooth can be disabled
* Setting IRQ's to "Auto" from factory default of "11" in the BIOS seems to help some people.
* The two USB ports on the left side of the computer may fail to connect storage devices during a session but will load them at boot up.
* booting with the "irqpoll" option seems to work for some people against the problem that usb-ports stop working.
* GLX (3d graphics) on intel 965 video card is broken: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/120834

=== Wireless activity LED ===

The LED is not implemented in either the IWL4965 or Atheros drivers.

== Power consumption ==

Gutsy is the first version of Ubuntu to feature a tickless kernel (i386 only, not in AMD64 yet). Power consumption
can be monitored using the powertop tool under Ubuntu and using Lenovo battery monitor
under Windows.

$ sudo apt-get install powertop
$ sudo powertop

I couldn't find any difference in power consumption between the i386 tickless kernel (even with 70ms average sleep in C4)
and AMD64 kernel (2ms average sleep in C4). It would be expected that considerably less power would be consumed for the
i386 tickless kernel.

There is also a graph available by Right-clicking on the battery icon and selecting Power History.

These are the figures measured on a T61 15.4" 1680x1050 screen 7300 processor (2GHz) 2GB RAM, Intel X3100 graphics
with 4965 wifi, Bluetooth and UWB.

{| border=1 cellpadding=5
|-
| 12.3W
| Windows XP Pro, all radios on, about 50% brightness
|-
| 16.7W
| Gutsy, all radios on, 50% brightness
|-
| 19.6W
| Gutsy, all radios on, 100% brightness
|-
| 14.2W
| Gutsy, all radios on, 10% brightness
|-
| -1.0W
| Turning the physical radio switch to off on the front reduces power consumption by 1 watt.
|}

Adding the Nvidia card increases the laptops power requirements.

These are the figures measured on a T61 14" 1440x900 screen 2.2ghz Core2Duo 2GB RAM, Nvidia 140m video, IWL4965 wifi and Bluetooth (Disabled):

{| border=1 cellpadding=5
|-
| 18.3W
| Gutsy, all radios on, 50% brightness
|-
| 19.4W
| Gutsy, all radios on, 100% brightness
|-
| 16.0W
| Gutsy, all radios on, 10% brightness
|-
|}

[[Category: T61]] [[Category: Ubuntu 7.10]]

Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61

2007-12-30T10:03:18Z

Jpeach: Removed question asking if it works in GNOME.... it does

==Introduction==

This document outlines configuring Ubuntu 7.10 (Gutsy Gibbon) on your Thinkpad T61. Most items will work out of the box and a base install should provide you with a completely working system. Due to the modular nature of the T61 there are many different configuration, please read carefully and only make the changes specific to your system.

Feel free to update this Wiki with your information however please ask questions on the Talk page.

==Installation Notes ==

*If booting with the live CD gives you a blank screen you should select the "Safe Graphics" menu choice.

== Display/Video ==

=== Accelerated Video and Desktop Effects ===
'''Intel''' 2D and 3D accelerated video work out of the box.

Due to [https://bugs.launchpad.net/xorg-server/+bug/111257 | bug 111257], compiz is disabled on the Intel i965 based video cards. All systems updated after 11/24/2007 should be fixed.

'''Nvidia''' 2D video works out of the box, to enable accelerated 3D support click System->Administration->Restricted Drivers Manager {{NOTE| If the Restricted Drivers Manager fails to install the driver you can use the Envy tool from: http://albertomilone.com/nvidia_scripts1.html. This tool is unsupported and the only supported method of installing the Nvidia drivers is via Synaptics and the Restricted Drivers Manager}}

===Multiple Monitors===

If you previously used Xinerama this is no longer a supported option, you should use one of the tools described below to configure dual displays.

====Nvidia N140m:====

When using the default drivers (The open source "nv" drivers) you can use Administration->"Screens and Graphics" to setup the second monitor

Using the proprietary drivers you must use the Nvidia tool located at Applications->System Tools-> Nvidia X Server Settings.

Note:
Twinview 'works' but doing anything with Twinview in fullscreen mode will cause it to span both monitors instead of just being on the second. This essencially kills the functionality of Twinview.

eg 1 --> you are an office working bringing your notebook to work to show a presentation but you can't use full screen.

eg 2 --> you want take your notebook to a friends house to watch a movie on his/her projector and fullscreen mode gets half displayed on the projector and half on the notebook monitor.

If you experience problems getting a working Twinview setup using nvidia-settings, please see [http://www.nvnews.net/vbulletin/showthread.php?t=101780 this thread]

====Intel X3100====

Plugging in an external monitor works, but is a clone of the built-in LCD by default. Using the Screens and Graphics tool located under Administration you can setup the second monitor as an extension of the existing screen or a clone for presentations, but it does not let you enable a second display on a second monitor.

'''Setting up dual monitors via the command line'''

If you like doing it via the command line and are using the Intel drivers or the open-source "nv" driver you can use this example (''Note all this should be possible using the Screens and Graphics tool so only make this change if you prefer the command line method''):

This is an example for a 1680x1050 built-in LCD and a 1600x1200 external LCD:
Add a "Virtual 3280 1200" line in the Display SubSection of the Screen Section in your xorg.conf:

Go to Applications -> Accessories -> Terminal and type the following:

{{cmdroot|sudo /etc/init.d/gdm stop}}

{{cmdroot|xrandr --output LVDS --auto}}

To set the built-in LCD to ouput 1680x1050

{{cmdroot|xrandr --output VGA --right-of LVDS}}

To extend the desktop

=== Fonts on High-Res Screens ===

On high-res screens (e.g. 15" 1680x1050), some users consider the default fonts too be too large ([https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/99145 Launchpad bug report]). You can fix this by following these steps:

# Open System->Preferences->Appearance
# Select the "Fonts" tab
# Click the "Details" button (lower right)
# Adjust the Resolution down to 96dpi
# Make sure you have Subpixel (LCD) Smoothing enabled
# Save the preferences

If you also want small fonts on the GDM login window, you can do this:

# Open System->Administration->Login Window
# Select the 'Security' tab
# Click the 'Configure X-Server' button
# Append '-dpi 96' (without quotes) to the text in the 'Command' field
# Reboot the computer.

=== Brightness ===
====Intel X3100:====
The brightness controls should work out of the box on a fresh install.

====Nvidia Quadro N140 and 570M:====
The brightness controls do not work out of the box, however you can switch to a virtual terminal (ctrl+alt+F1) increase or decrease the brightness and then switch back to X (ctrl+alt+F7) without disrupting the running applications (You should save anything open just to be safe). There is a new [http://www.nvidia.com/object/linux_display_ia32_169.04.html beta-driver (version 169.04)] by nvidia that fixes the brightness-controls. To install this driver use the Envy tool described above.

== Audio ==

=== Inextricably Linked to the Modem ===
Make sure that you have the modem enabled in the BIOS. If it is disabled, you may discover that your audio is also disabled. In this situation, your drivers may still load, but you will get an error message whenever you try to play audio.

===Enabling Audio controls===

By default, the sound may be disabled and the volume control buttons on the laptop (up by the ThinkVantage button) and the volume control applet (up by the clock) will not control the speaker volume (they actually control the microphone). To fix this:

# Right-click on the volume control applet (by the clock) and select "Open Volume Control"
# In the "Switches" tab, make sure "Headphone" and "Speaker" are both checked.
# Close the Volume control.
# Right-click on the volume control applet again and select "Preferences".
# Make sure the device is set to "HDA Intel (Alsa mixer)" and highlight the "PCM" option.
# Close the preferences.
# Select System->Preferences->Sound.
# In the "Default Mixer Tracks" section, make sure "PCM" is highlighted.
# Close the sound preferences.

You should now hear sound and be able to control the volume using the laptop buttons or volume applet.

A recent BIOS update [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-67989] fixes the mute button, you can then configure it to mute/unmute audio in Keyboard Shortcuts.

===Microphone===

There have been reports that the microphone may not work, please add your input to the talk page [http://www.thinkwiki.org/wiki/Talk:Installing_Ubuntu_7.10_%28Gutsy_Gibbon%29_on_a_ThinkPad_T61#Microphone] and update this section when a consensus on the problem and solution has been reached.

===Sound Cracking===

There have been intermittent reports of users experiencing cracking when listening to audio. Here are a few possible solutions:

* Try to switch to the OSS driver in system => preference => sound => devices => Music and movies, select OSS - Open sound system (instead of ALSA)

* If this issue is only occurring for Rhythmbox go to Edit > Preferences > Playback > and Check "Use Crossfading Backend". Restart Rhythmbox and you should have better audio quality.

* Check that the microphone is muted and modify your mixer settings by moving items like PCM down halfway and see if the cracking goes away.

===Hissing===
Some users experience hissing during playback, and even when idle. To solve this mute the microphone when it is not in use:

# Run "alsamixer" in the terminal.
# Arrow over to "Mic", and hit "M" to mute.
# Arrow over to the first "Docking", and hit "M" to mute.
# Arrow to the first "Internal", and hit "M" to mute.

Now, make sure that "Headphone" and/or "Speaker" are _not_ muted, and that "PCM" is at a reasonable level (say ~70) so you don't make your ears bleed, and try playing something back. ''(<Esc> will exit alsamixer)''

== Modem ==

The modem works with the Linuxant drivers available at http://www.linuxant.com

==Bluetooth==
Bluetooth works out of the box. Pressing Fn-F5 once will enable bluetooth, disable wireless, pressing again, enable both and pressing one more time will disable bluetooth.

If you would like to set bluetooth state independently the script below determines the current bluetooth state and toggles the device on or off.

First create a new file named bluetooth-toggle:
{{cmdroot|sudo touch /usr/sbin/bluetooth-toggle}}

Now open a editor:
{{cmdroot|sudo gedit /usr/sbin/bluetooth-toggle}}

Paste the following script:

#!/bin/bash
cat /proc/acpi/ibm/bluetooth | awk '{ print $2 }' | while read line;
do
if [ $line == "enabled" ]; then
echo disable > /proc/acpi/ibm/bluetooth
else
echo enable > /proc/acpi/ibm/bluetooth
fi
break
done

Now set the execute permissions:
{{cmdroot|sudo chmod +x /usr/sbin/bluetooth-toggle}}

You can invoke the script out of the console by typing sudo bluetooth-toggle or create a menu icon by using the menu editor under preferences using gksudo bluetooth-toggle as command line.

== Fingerprint Reader ==

The reader works with ThinkFinger. General instructions available [http://www.thinkwiki.org/wiki/Integrated_Fingerprint_Reader here] and [https://wiki.ubuntu.com/ThinkFinger here].
Instructions in French available at http://doc.ubuntu-fr.org/materiel/thinkfinger

Note that ThinkFinger in it's current version does not work with KDE and Kubuntu in any way (it crashes KDM and is not integrated at all).

Prebuilt packages are available from jldugger using Launchpad's PPA:

Add the thinkfinger package repository by creating {{path|/etc/apt/sources.list.d/thinkfinger.list}} with these two lines:

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

Then update the package database and install packages:

{{cmduser|sudo apt-get update}}
{{cmduser|sudo apt-get install libpam-thinkfinger libthinkfinger-dev libthinkfinger-doc libthinkfinger0 thinkfinger-tools}}

After the package is installed add the following two lines to the beginning of {{path|/etc/pam.d/common-auth}}

auth sufficient pam_thinkfinger.so
auth required pam_unix.so try_first_pass

Edit {{path|/etc/modules}} and add the following line:

uinput

Load the module manually for this session:

{{cmduser| sudo modprobe uinput}}

Summary:
* Recording fingerprints works
* Login works
* The password must be entered to unlock a locked screensaver
* sudo works
* gksu and gksudo hang : for example it is necessary to run synaptic twice and enter your password upon failure. To be able to use the Finger print reader in the session subsequently, kill the hanging gksu/gksudo process. A workaround is editing the Gnome System Menu (alacarte) to specify sudo instead of gksu/gksudo for the launching command and choose type "Application in Terminal" : this opens an extra terminal window for each superuser application you want to use though.

== Trackpad scrolling ==

Trackpad scrolling works out of the box in the standard thinkpad way: Slide your finger up and down the very right edge of the trackpad.
Note that /etc/X11/xorg.conf will be changed and the edge scrolling will be disabled after running nvidia-xconfig , copy the trackpad section from the backup of xorg.conf

To enable using the middle mouse button to scroll, add the following lines to the "Configured Mouse" section in
{{path|/etc/X11/xorg.conf}}:

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

== Hibernate/Suspend ==

=== Blank screen fix for intel graphics cards===

This fix is for Intel Graphics Cards only.

You may get a blank screen when resuming from suspend or hibernate ([https://bugs.launchpad.net/ubuntu/+bug/134391 Launchpad bug report]). To fix this:

1) Go to the in Applications -> Accessories -> Terminal

2) Enter "sudo nautilus" without the quotation marks.

3) Go to {{path|/boot/grub/}}, backup and then edit {{path|menu.lst}} by adding "acpi_sleep=s3_bios" (no quotes) to the "defoptions" list so that it looks something like this:

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash '''acpi_sleep=s3_bios'''

4) Once you have edited the line and added the acpi_sleep parameter, you need to run

<pre>sudo update-grub</pre>

in the terminal.

Note that if you get the blank screen upon resume, a quick-fix is to switch to a console (Ctrl-Alt-F1) and then back to X (Ctrl-Alt-F7). This will usually bring the display back to life. However, the long-term fix is to add the acpi_sleep parameter as shown above.

=== How to Suspend with nVidia 140m/570m ===

The suspend to RAM will work with the nVidia card and the proprietary drivers, but it requires some file editing. It did not work for me out of the box. Using the package manager, download and install the latest nVidia drivers (100.14.19+2.6.2.4-12.4 at time of writing). I also had to use the 2.6.22-12-generic kernel image (the 2.6.22-13 image did not work with this driver --- I'm assuming it has to match wit the nVidia version, but I am not an expert).

Once you have it installed and working, you have to make a change to {{path|/etc/default/acpi-support}}. Open the file in your favorite editor and change the following lines:

$ sudo nano /etc/default/acpi-support

{{path|/etc/default/acpi-support}}
# Should we save and restore state using the VESA BIOS Extensions?
SAVE_VBE_STATE=false
...
# Should we attempt to warm-boot the video hardware on resume?
POST_VIDEO=false
...
# Set the following to "platform" if you want to use ACPI to shut down
# your machine on hibernation
HIBERNATE_MODE=platform

This allowed me to suspend and resume, but after two suspends the wireless wouldn't work anymore. Theoretically, ACPI unloads the network drivers before suspending, but it doesn't seem to work correctly so I added these to the blacklist modules manually (in the same file as above:

{{path|/etc/default/acpi-support}}
# Add modules to this list to have them removed before suspend and reloaded
# on resume. An example would be MODULES="em8300 yenta_socket"
#
# Note that network cards and USB controllers will automatically be unloaded
# unless they're listed in MODULES_WHITELIST
MODULES="iwl4965 iwlwifi_mac80211 cfg80211"

Your wifi modules may be different. (I have the intel AGN wireless card -- I don't know if these modules are different for other cards.)

This allows me to suspend to ram; I haven't had any problems with it so far. I haven't gotten hibernate (suspend to disk) working, so there may be additional things you need to do for that. (I think part of my problem is that I don't have enough swap, but I don't care enough to actually fix it.)

If the system has been left in suspend off for a while, wireless might not reconnect at all (Thinkpad T61 8892-02U). Restarting netapplet
solves the problem.

{{path|/etc/default/acpi-support}}
# Add services to this list to stop them before suspend and restart them in
# the resume process.
STOP_SERVICES="netapplet"

/*The fix does not work for me. I have a T61 7664-17U(NVS 140m, 4965agn). The computers suspend, but when it wakes up it hangs up and I have to pull out the battery to restart it.*/

General hint: Do not install the package "hibernate" or "uswsusp" or the gnome-power-manager will fail to suspend/hibernate your computer. If you have installed the package don't forget to purge the configuration. (sudo apt-get remove hibernate --purge, uswsusp resp.)

The instructions for Intel video card recommends adding "acpi_sleep=s3_bios" to the kernel parameters in Grub configuration. According to a comment on [https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/139089 Launchpad BUG 139089], the correct setting for Nvidia is "acpi_sleep=s3_mode". Once I changed this, Suspend to ram worked. I have the T61 6459-CTO.

== Items that work out of the box ==

'''Intel Video:''' 2D and 3D acceleration works

'''Nvidia:''' 2D works, 3D requires the installation of the proprietary drivers

'''Wireless:''' Atheros and Intel cards both tested.

'''Bluetooth:''' Tested with both a bluetooth headset and an HTC 8525

'''Network Card''' Intel 10/100/1000 tested

'''Firewire''' Tested with hard drive

'''Wireless switch'''

'''4-in-1 card reader'''

'''Webcam'''

'''Headphones''' You may need to enable Headphone out: Right-click on the volume control and select open volume control. Click the switches tab and then check the headphones box.

'''Keyboard Shortcuts:'''
* Fn-PgUp activates/deactivates the thinklight
* Fn-Up will trigger stop on a media player
* Fn-Down will toggle pause and play on a media player
* Fn-Left/Right go to prev/next tracks on a media player
* Fn-F2 properly locks the screen
* Fn-F3 shows remaining battery >>does not work on all machines<<
* Fn-F4 suspends (to ram)
* Fn-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

'''Docking Stations:'''

All docking station models should work and the following features have been tested:

* DVI or Analog video: You can switch to it using "Administration->Screens and Graphics", if you are using the proprietary Nvidia drivers you must use the Nvidia Control Panel.

* Network Pass-through

* Modem Pass-through

* USB ports: Connected upon docking

* PS/2 Ports

== Items that don't work ==

=== Interrupt problem (PROBABLY SOLVED) ===
This bug is supposed to be solved by updating the system BIOS to the [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-67989 2.07]-Version (with 1.08 AMT). Still testing...
* https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/126369
* USB ports can end up temporarily disabled
* Wifi can break
* integrated cardreader can be disabled
* bluetooth can be disabled
* Setting IRQ's to "Auto" from factory default of "11" in the BIOS seems to help some people.
* The two USB ports on the left side of the computer may fail to connect storage devices during a session but will load them at boot up.
* booting with the "irqpoll" option seems to work for some people against the problem that usb-ports stop working.
* GLX (3d graphics) on intel 965 video card is broken: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/120834

=== Wireless activity LED ===

The LED is not implemented in either the IWL4965 or Atheros drivers.

== Power consumption ==

Gutsy is the first version of Ubuntu to feature a tickless kernel (i386 only, not in AMD64 yet). Power consumption
can be monitored using the powertop tool under Ubuntu and using Lenovo battery monitor
under Windows.

$ sudo apt-get install powertop
$ sudo powertop

I couldn't find any difference in power consumption between the i386 tickless kernel (even with 70ms average sleep in C4)
and AMD64 kernel (2ms average sleep in C4). It would be expected that considerably less power would be consumed for the
i386 tickless kernel.

There is also a graph available by Right-clicking on the battery icon and selecting Power History.

These are the figures measured on a T61 15.4" 1680x1050 screen 7300 processor (2GHz) 2GB RAM, Intel X3100 graphics
with 4965 wifi, Bluetooth and UWB.

{| border=1 cellpadding=5
|-
| 12.3W
| Windows XP Pro, all radios on, about 50% brightness
|-
| 16.7W
| Gutsy, all radios on, 50% brightness
|-
| 19.6W
| Gutsy, all radios on, 100% brightness
|-
| 14.2W
| Gutsy, all radios on, 10% brightness
|-
| -1.0W
| Turning the physical radio switch to off on the front reduces power consumption by 1 watt.
|}

Adding the Nvidia card increases the laptops power requirements.

These are the figures measured on a T61 14" 1440x900 screen 2.2ghz Core2Duo 2GB RAM, Nvidia 140m video, IWL4965 wifi and Bluetooth (Disabled):

{| border=1 cellpadding=5
|-
| 18.3W
| Gutsy, all radios on, 50% brightness
|-
| 19.4W
| Gutsy, all radios on, 100% brightness
|-
| 16.0W
| Gutsy, all radios on, 10% brightness
|-
|}

[[Category: T61]] [[Category: Ubuntu 7.10]]

Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61

2007-12-29T05:55:14Z

Jpeach: Making it clear where in the file the lines need to be added

==Introduction==

This document outlines configuring Ubuntu 7.10 (Gutsy Gibbon) on your Thinkpad T61. Most items will work out of the box and a base install should provide you with a completely working system. Due to the modular nature of the T61 there are many different configuration, please read carefully and only make the changes specific to your system.

Feel free to update this Wiki with your information however please ask questions on the Talk page.

==Installation Notes ==

*If booting with the live CD gives you a blank screen you should select the "Safe Graphics" menu choice.

== Display/Video ==

=== Accelerated Video and Desktop Effects ===
'''Intel''' 2D and 3D accelerated video work out of the box.

Due to [https://bugs.launchpad.net/xorg-server/+bug/111257 | bug 111257], compiz is disabled on the Intel i965 based video cards. All systems updated after 11/24/2007 should be fixed.

'''Nvidia''' 2D video works out of the box, to enable accelerated 3D support click System->Administration->Restricted Drivers Manager {{NOTE| If the Restricted Drivers Manager fails to install the driver you can use the Envy tool from: http://albertomilone.com/nvidia_scripts1.html. This tool is unsupported and the only supported method of installing the Nvidia drivers is via Synaptics and the Restricted Drivers Manager}}

===Multiple Monitors===

If you previously used Xinerama this is no longer a supported option, you should use one of the tools described below to configure dual displays.

====Nvidia N140m:====

When using the default drivers (The open source "nv" drivers) you can use Administration->"Screens and Graphics" to setup the second monitor

Using the proprietary drivers you must use the Nvidia tool located at Applications->System Tools-> Nvidia X Server Settings.

Note:
Twinview 'works' but doing anything with Twinview in fullscreen mode will cause it to span both monitors instead of just being on the second. This essencially kills the functionality of Twinview.

eg 1 --> you are an office working bringing your notebook to work to show a presentation but you can't use full screen.

eg 2 --> you want take your notebook to a friends house to watch a movie on his/her projector and fullscreen mode gets half displayed on the projector and half on the notebook monitor.

If you experience problems getting a working Twinview setup using nvidia-settings, please see [http://www.nvnews.net/vbulletin/showthread.php?t=101780 this thread]

====Intel X3100====

Plugging in an external monitor works, but is a clone of the built-in LCD by default. Using the Screens and Graphics tool located under Administration you can setup the second monitor as an extension of the existing screen or a clone for presentations, but it does not let you enable a second display on a second monitor.

'''Setting up dual monitors via the command line'''

If you like doing it via the command line and are using the Intel drivers or the open-source "nv" driver you can use this example (''Note all this should be possible using the Screens and Graphics tool so only make this change if you prefer the command line method''):

This is an example for a 1680x1050 built-in LCD and a 1600x1200 external LCD:
Add a "Virtual 3280 1200" line in the Display SubSection of the Screen Section in your xorg.conf:

Go to Applications -> Accessories -> Terminal and type the following:

{{cmdroot|sudo /etc/init.d/gdm stop}}

{{cmdroot|xrandr --output LVDS --auto}}

To set the built-in LCD to ouput 1680x1050

{{cmdroot|xrandr --output VGA --right-of LVDS}}

To extend the desktop

=== Fonts on High-Res Screens ===

On high-res screens (e.g. 15" 1680x1050), some users consider the default fonts too be too large ([https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/99145 Launchpad bug report]). You can fix this by following these steps:

# Open System->Preferences->Appearance
# Select the "Fonts" tab
# Click the "Details" button (lower right)
# Adjust the Resolution down to 96dpi
# Make sure you have Subpixel (LCD) Smoothing enabled
# Save the preferences

If you also want small fonts on the GDM login window, you can do this:

# Open System->Administration->Login Window
# Select the 'Security' tab
# Click the 'Configure X-Server' button
# Append '-dpi 96' (without quotes) to the text in the 'Command' field
# Reboot the computer.

=== Brightness ===
====Intel X3100:====
The brightness controls should work out of the box on a fresh install.

====Nvidia Quadro N140 and 570M:====
The brightness controls do not work out of the box, however you can switch to a virtual terminal (ctrl+alt+F1) increase or decrease the brightness and then switch back to X (ctrl+alt+F7) without disrupting the running applications (You should save anything open just to be safe). There is a new [http://www.nvidia.com/object/linux_display_ia32_169.04.html beta-driver (version 169.04)] by nvidia that fixes the brightness-controls. To install this driver use the Envy tool described above.

== Audio ==

=== Inextricably Linked to the Modem ===
Make sure that you have the modem enabled in the BIOS. If it is disabled, you may discover that your audio is also disabled. In this situation, your drivers may still load, but you will get an error message whenever you try to play audio.

===Enabling Audio controls===

By default, the sound may be disabled and the volume control buttons on the laptop (up by the ThinkVantage button) and the volume control applet (up by the clock) will not control the speaker volume (they actually control the microphone). To fix this:

# Right-click on the volume control applet (by the clock) and select "Open Volume Control"
# In the "Switches" tab, make sure "Headphone" and "Speaker" are both checked.
# Close the Volume control.
# Right-click on the volume control applet again and select "Preferences".
# Make sure the device is set to "HDA Intel (Alsa mixer)" and highlight the "PCM" option.
# Close the preferences.
# Select System->Preferences->Sound.
# In the "Default Mixer Tracks" section, make sure "PCM" is highlighted.
# Close the sound preferences.

You should now hear sound and be able to control the volume using the laptop buttons or volume applet.

A recent BIOS update [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-67989] fixes the mute button, you can then configure it to mute/unmute audio in Keyboard Shortcuts.

===Microphone===

There have been reports that the microphone may not work, please add your input to the talk page [http://www.thinkwiki.org/wiki/Talk:Installing_Ubuntu_7.10_%28Gutsy_Gibbon%29_on_a_ThinkPad_T61#Microphone] and update this section when a consensus on the problem and solution has been reached.

===Sound Cracking===

There have been intermittent reports of users experiencing cracking when listening to audio. Here are a few possible solutions:

* Try to switch to the OSS driver in system => preference => sound => devices => Music and movies, select OSS - Open sound system (instead of ALSA)

* If this issue is only occurring for Rhythmbox go to Edit > Preferences > Playback > and Check "Use Crossfading Backend". Restart Rhythmbox and you should have better audio quality.

* Check that the microphone is muted and modify your mixer settings by moving items like PCM down halfway and see if the cracking goes away.

===Hissing===
Some users experience hissing during playback, and even when idle. To solve this mute the microphone when it is not in use:

# Run "alsamixer" in the terminal.
# Arrow over to "Mic", and hit "M" to mute.
# Arrow over to the first "Docking", and hit "M" to mute.
# Arrow to the first "Internal", and hit "M" to mute.

Now, make sure that "Headphone" and/or "Speaker" are _not_ muted, and that "PCM" is at a reasonable level (say ~70) so you don't make your ears bleed, and try playing something back. ''(<Esc> will exit alsamixer)''

== Modem ==

The modem works with the Linuxant drivers available at http://www.linuxant.com

==Bluetooth==
Bluetooth works out of the box. Pressing Fn-F5 once will enable bluetooth, disable wireless, pressing again, enable both and pressing one more time will disable bluetooth.

If you would like to set bluetooth state independently the script below determines the current bluetooth state and toggles the device on or off.

First create a new file named bluetooth-toggle:
{{cmdroot|sudo touch /usr/sbin/bluetooth-toggle}}

Now open a editor:
{{cmdroot|sudo gedit /usr/sbin/bluetooth-toggle}}

Paste the following script:

#!/bin/bash
cat /proc/acpi/ibm/bluetooth | awk '{ print $2 }' | while read line;
do
if [ $line == "enabled" ]; then
echo disable > /proc/acpi/ibm/bluetooth
else
echo enable > /proc/acpi/ibm/bluetooth
fi
break
done

Now set the execute permissions:
{{cmdroot|sudo chmod +x /usr/sbin/bluetooth-toggle}}

You can invoke the script out of the console by typing sudo bluetooth-toggle or create a menu icon by using the menu editor under preferences using gksudo bluetooth-toggle as command line.

== Fingerprint Reader ==

The reader works with ThinkFinger. General instructions available [http://www.thinkwiki.org/wiki/Integrated_Fingerprint_Reader here] and [https://wiki.ubuntu.com/ThinkFinger here].
Instructions in French available at http://doc.ubuntu-fr.org/materiel/thinkfinger

Note that ThinkFinger in it's current version does not work with KDE and Kubuntu in any way (it crashes KDM and is not integrated at all).

Prebuilt packages are available from jldugger using Launchpad's PPA:

Add the thinkfinger package repository by creating {{path|/etc/apt/sources.list.d/thinkfinger.list}} with these two lines:

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

Then update the package database and install packages:

{{cmduser|sudo apt-get update}}
{{cmduser|sudo apt-get install libpam-thinkfinger libthinkfinger-dev libthinkfinger-doc libthinkfinger0 thinkfinger-tools}}

After the package is installed add the following two lines to the beginning of {{path|/etc/pam.d/common-auth}}

auth sufficient pam_thinkfinger.so
auth required pam_unix.so try_first_pass

Edit {{path|/etc/modules}} and add the following line:

uinput

Load the module manually for this session:

{{cmduser| sudo modprobe uinput}}

Summary:
* Recording fingerprints works
* Login works
* The password must be entered to unlock a locked screensaver
* sudo works
* gksu and gksudo hang : for example it is necessary to run synaptic twice and enter your password upon failure. To be able to use the Finger print reader in the session subsequently, kill the hanging gksu/gksudo process. A workaround is editing the Gnome System Menu (alacarte) to specify sudo instead of gksu/gksudo for the launching command and choose type "Application in Terminal" : this opens an extra terminal window for each superuser application you want to use though.

== Trackpad scrolling ==

Trackpad scrolling works out of the box in the standard thinkpad way: Slide your finger up and down the very right edge of the trackpad.
Note that /etc/X11/xorg.conf will be changed and the edge scrolling will be disabled after running nvidia-xconfig , copy the trackpad section from the backup of xorg.conf

To enable using the middle mouse button to scroll, add the following lines to the "Configured Mouse" section in
{{path|/etc/X11/xorg.conf}}:

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

== Hibernate/Suspend ==

=== Blank screen fix for intel graphics cards===

This fix is for Intel Graphics Cards only.

You may get a blank screen when resuming from suspend or hibernate ([https://bugs.launchpad.net/ubuntu/+bug/134391 Launchpad bug report]). To fix this:

1) Go to the in Applications -> Accessories -> Terminal

2) Enter "sudo nautilus" without the quotation marks.

3) Go to {{path|/boot/grub/}}, backup and then edit {{path|menu.lst}} by adding "acpi_sleep=s3_bios" (no quotes) to the "defoptions" list so that it looks something like this:

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash '''acpi_sleep=s3_bios'''

4) Once you have edited the line and added the acpi_sleep parameter, you need to run

<pre>sudo update-grub</pre>

in the terminal.

Note that if you get the blank screen upon resume, a quick-fix is to switch to a console (Ctrl-Alt-F1) and then back to X (Ctrl-Alt-F7). This will usually bring the display back to life. However, the long-term fix is to add the acpi_sleep parameter as shown above.

=== How to Suspend with nVidia 140m/570m ===

The suspend to RAM will work with the nVidia card and the proprietary drivers, but it requires some file editing. It did not work for me out of the box. Using the package manager, download and install the latest nVidia drivers (100.14.19+2.6.2.4-12.4 at time of writing). I also had to use the 2.6.22-12-generic kernel image (the 2.6.22-13 image did not work with this driver --- I'm assuming it has to match wit the nVidia version, but I am not an expert). (Note: I am using KDE. I would think these fixes would work for gnome as well, but someone else would have to test them.)

Once you have it installed and working, you have to make a change to {{path|/etc/default/acpi-support}}. Open the file in your favorite editor and change the following lines:

$ sudo nano /etc/default/acpi-support

{{path|/etc/default/acpi-support}}
# Should we save and restore state using the VESA BIOS Extensions?
SAVE_VBE_STATE=false
...
# Should we attempt to warm-boot the video hardware on resume?
POST_VIDEO=false
...
# Set the following to "platform" if you want to use ACPI to shut down
# your machine on hibernation
HIBERNATE_MODE=platform

This allowed me to suspend and resume, but after two suspends the wireless wouldn't work anymore. Theoretically, ACPI unloads the network drivers before suspending, but it doesn't seem to work correctly so I added these to the blacklist modules manually (in the same file as above:

{{path|/etc/default/acpi-support}}
# Add modules to this list to have them removed before suspend and reloaded
# on resume. An example would be MODULES="em8300 yenta_socket"
#
# Note that network cards and USB controllers will automatically be unloaded
# unless they're listed in MODULES_WHITELIST
MODULES="iwl4965 iwlwifi_mac80211 cfg80211"

Your wifi modules may be different. (I have the intel AGN wireless card -- I don't know if these modules are different for other cards.)

This allows me to suspend to ram; I haven't had any problems with it so far. I haven't gotten hibernate (suspend to disk) working, so there may be additional things you need to do for that. (I think part of my problem is that I don't have enough swap, but I don't care enough to actually fix it.)

If the system has been left in suspend off for a while, wireless might not reconnect at all (Thinkpad T61 8892-02U). Restarting netapplet
solves the problem.

{{path|/etc/default/acpi-support}}
# Add services to this list to stop them before suspend and restart them in
# the resume process.
STOP_SERVICES="netapplet"

/*The fix does not work for me. I have a T61 7664-17U(NVS 140m, 4965agn). The computers suspend, but when it wakes up it hangs up and I have to pull out the battery to restart it.*/

General hint: Do not install the package "hibernate" or "uswsusp" or the gnome-power-manager will fail to suspend/hibernate your computer. If you have installed the package don't forget to purge the configuration. (sudo apt-get remove hibernate --purge, uswsusp resp.)

The instructions for Intel video card recommends adding "acpi_sleep=s3_bios" to the kernel parameters in Grub configuration. According to a comment on [https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/139089 Launchpad BUG 139089], the correct setting for Nvidia is "acpi_sleep=s3_mode". Once I changed this, Suspend to ram worked. I have the T61 6459-CTO.

== Items that work out of the box ==

'''Intel Video:''' 2D and 3D acceleration works

'''Nvidia:''' 2D works, 3D requires the installation of the proprietary drivers

'''Wireless:''' Atheros and Intel cards both tested.

'''Bluetooth:''' Tested with both a bluetooth headset and an HTC 8525

'''Network Card''' Intel 10/100/1000 tested

'''Firewire''' Tested with hard drive

'''Wireless switch'''

'''4-in-1 card reader'''

'''Webcam'''

'''Headphones''' You may need to enable Headphone out: Right-click on the volume control and select open volume control. Click the switches tab and then check the headphones box.

'''Keyboard Shortcuts:'''
* Fn-PgUp activates/deactivates the thinklight
* Fn-Up will trigger stop on a media player
* Fn-Down will toggle pause and play on a media player
* Fn-Left/Right go to prev/next tracks on a media player
* Fn-F2 properly locks the screen
* Fn-F3 shows remaining battery >>does not work on all machines<<
* Fn-F4 suspends (to ram)
* Fn-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

'''Docking Stations:'''

All docking station models should work and the following features have been tested:

* DVI or Analog video: You can switch to it using "Administration->Screens and Graphics", if you are using the proprietary Nvidia drivers you must use the Nvidia Control Panel.

* Network Pass-through

* Modem Pass-through

* USB ports: Connected upon docking

* PS/2 Ports

== Items that don't work ==

=== Interrupt problem (PROBABLY SOLVED) ===
This bug is supposed to be solved by updating the system BIOS to the [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-67989 2.07]-Version (with 1.08 AMT). Still testing...
* https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/126369
* USB ports can end up temporarily disabled
* Wifi can break
* integrated cardreader can be disabled
* bluetooth can be disabled
* Setting IRQ's to "Auto" from factory default of "11" in the BIOS seems to help some people.
* The two USB ports on the left side of the computer may fail to connect storage devices during a session but will load them at boot up.
* booting with the "irqpoll" option seems to work for some people against the problem that usb-ports stop working.
* GLX (3d graphics) on intel 965 video card is broken: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/120834

=== Wireless activity LED ===

The LED is not implemented in either the IWL4965 or Atheros drivers.

== Power consumption ==

Gutsy is the first version of Ubuntu to feature a tickless kernel (i386 only, not in AMD64 yet). Power consumption
can be monitored using the powertop tool under Ubuntu and using Lenovo battery monitor
under Windows.

$ sudo apt-get install powertop
$ sudo powertop

I couldn't find any difference in power consumption between the i386 tickless kernel (even with 70ms average sleep in C4)
and AMD64 kernel (2ms average sleep in C4). It would be expected that considerably less power would be consumed for the
i386 tickless kernel.

There is also a graph available by Right-clicking on the battery icon and selecting Power History.

These are the figures measured on a T61 15.4" 1680x1050 screen 7300 processor (2GHz) 2GB RAM, Intel X3100 graphics
with 4965 wifi, Bluetooth and UWB.

{| border=1 cellpadding=5
|-
| 12.3W
| Windows XP Pro, all radios on, about 50% brightness
|-
| 16.7W
| Gutsy, all radios on, 50% brightness
|-
| 19.6W
| Gutsy, all radios on, 100% brightness
|-
| 14.2W
| Gutsy, all radios on, 10% brightness
|-
| -1.0W
| Turning the physical radio switch to off on the front reduces power consumption by 1 watt.
|}

Adding the Nvidia card increases the laptops power requirements.

These are the figures measured on a T61 14" 1440x900 screen 2.2ghz Core2Duo 2GB RAM, Nvidia 140m video, IWL4965 wifi and Bluetooth (Disabled):

{| border=1 cellpadding=5
|-
| 18.3W
| Gutsy, all radios on, 50% brightness
|-
| 19.4W
| Gutsy, all radios on, 100% brightness
|-
| 16.0W
| Gutsy, all radios on, 10% brightness
|-
|}

[[Category: T61]] [[Category: Ubuntu 7.10]]