ThinkWiki - User contributions [en]

Installing Ubuntu 9.10 (Karmic Koala) on a ThinkPad T61p

2009-11-26T12:07:01Z

Trampas: /* Upgrades */

Tested with new installation of Ubuntu Karmic Koala 64 bit

=Getting the hardware to work=
==Fingerprint Reader==

The [http://thinkfinger.sourceforge.net Thinkfinger] package allows you to swipe a finger in most places where you would have to type your password. This works with sudo, gksudo and on the login page and with a little fix also for the screen saver. Also, you are still required to type your user name on the login screen.

1) Install the following packages:

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

2) For your user:

{{cmduser| sudo tf-tool --acquire && sudo tf-tool --verify}}

A completed fingerprint setup should look something like this:

frank@Laptop:~$ sudo tf-tool --acquire && sudo tf-tool --verify

ThinkFinger 0.3 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>

Initializing... done.
Please swipe your finger (successful swipes 3/3, failed swipes: 0)... done.
Storing data (/tmp/test.bir)... done.

ThinkFinger 0.3 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>

Initializing... done.
Please swipe your finger (successful swipes 1/1, failed swipes: 0)... done.
Result: Fingerprint does match.
frank@CLaptop:~$

This will store your fingerprint information in /home/$USERNAME/.thinkfinger.bir

You should do this step for each user who wants to use the fingerprint reader

3) Enable use of reader for authentication:

{{cmduser| sudo gedit /etc/pam.d/common-auth}}

add
auth sufficient pam_thinkfinger.so
before the line which contains pam_unix.so and add
try_first_pass
to the end of the line containing pam_unix.so.

So it should look something like this:
...
auth sufficient pam_thinkfinger.so
auth [success=1 default=ignore] pam_unix.so nullok_secure try_first_pass
...

4) Check uinput kernel module:

{{cmduser|lsmod | grep uinput}}
If the output starts with uinput, then you're done.
If you don't get any output, then it needs to be started and set to start on boot.

Start uinput:

{{cmduser|sudo modprobe uinput}}

Start on boot:

{{cmduser|sudo gedit /etc/modules}}

make sure there is a line like this or add it at the bottom:
uinput

5) Enabling thinkfinger for gnome-screensaver

*create this file:
{{cmduser|sudo gedit /etc/udev/rules.d/60-thinkfinger.rules}}
with this contents:
#
# 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/Install_Ubuntu_Intrepid_Ibex_on_a_T61p#Fingerprint_Reader
# which was taken and modified from:
# http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
# 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"

*Make the group:
{{cmduser|sudo groupadd fingerprint}}
*per user:
{{cmduser|sudo gpasswd -a $USERNAME fingerprint && sudo chown $USERNAME:root /home/$USERNAME/.thinkfinger.bir }}

Reboot your laptop and you should be ready to swipe!

Sources:
* [[Install_Ubuntu_Gutsy_Gibbon_on_a_T61p#Fingerprint_Reader| Install Ubuntu Gutsy Gibbon on a T61p]]
* [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 Bug #256429: Carriage-return required after finger scan] & [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429/comments/21 Solution for the bug in the comments]
* [[How_to_enable_the_fingerprint_reader_with_ThinkFinger| General page about Fingerprint reader with thinkfinger]] & [[How_to_enable_the_fingerprint_reader_with_ThinkFinger#xscreensaver.2Fgnome-screensaver| Specific gnome-screensaver section]]

== Battery control by tp_smapi ==
The kernel module is not present for some reason in Karmic Koala but there is a source package:
sudo apt-get install tp-smapi-source
cd /usr/src/
sudo tar -xjf tp-smapi.tar.bz2
cd modules/tp-smapi/debian/
sudo module-assistant prepare tp-smapi
sudo module-assistant auto-install tp-smapi

You need to load the kernel module:
sudo modprobe tp_smapi

Check if it was succesfully loaded:
sudo lsmod | grep tp_smapi

For convenience, you could load the kernel module at boot time by adding it to /etc/modules.
echo "tp_smapi" | sudo tee -a /etc/modules

Now, you will be able to have significantly more control over your battery charging via /sys/devices/platform/smapi.

For example, you could set a threshold value of 90% for charging, preventing the battery from charging all the way in exchange for a reduction in the loss of battery capacity that occurs after multiple cycles.
echo "90" | sudo tee -a /sys/devices/platform/smapi/BAT0/stop_charge_thresh

View the number of charge cycles your battery has had in its lifetime:
cat /sys/devices/platform/smapi/BAT0/cycle_count

While AC connected, force discharging of your battery:
echo "1" | sudo tee -a /sys/devices/platform/smapi/BAT0/force_discharge

If you have an Ultrabay battery, you might want to place this [http://forum.thinkpads.com/viewtopic.php?p=433463#p433463 script] into <code>/etc/crontab</code> to keep the Ultrabay battery from being completely discharged to 0%, which permanently damages the battery.
# rolls to BAT0 when remaining capacity on BAT1 is less than 20%. Change .2 if wanted. Swap BAT0 and BAT1 if tp_smapi thinks the ultrabay is BAT0.
awk '{if (/remaining capacity/) left=$3; if (/last full capacity/) full=$4} END {if ((left/full) < .2) system("echo 1 > /sys/devices/platform/smapi/BAT0/force_discharge")}' /proc/acpi/battery/BAT1/*
Remember the script needs root in order to write to the files in <code>/sys/devices/platform/smapi/BAT{0,1}/</code>.

=Problems=
==Compiz==
With compiz enabled flash plug-in for browser will not receive key presses.This is apparently a problem with latest Gnome. This is in the x64 bit version not tested on 32bit.

==Upgrades==
With Nvidia drivers installed from Nvidia it appears that when a new kernel is installed your machine will become unbootable. It will boot to a loginin screen for tty0 which flashes and will randomly ignore key presses thus making it impossible to login. Basically 9.10 sucks and user should stay with 9.04. If you do get to the flashing tty1 login screen try the following key combination, Alt+SysRq+i, to stop flashing and allow you to login and run the Nvidia driver again.

==Suspend==
*Does not work with SD card installed, card needs umounted before sleeping. User can modify sleep to umount /dev/mmcblk0*

==Hibernate==

Waking up from hibernation does something like this:
*It shows a mangled screen and waits 15 seconds
*It beeps (hardware beep which i have no idea how to disable)
*It reinitializes the graphics card
*It mangles the screen again and waits 15 seconds
*Again hardware beep
*It reinitilizes the screen again
*Finally everything should be ok and it should be back from hibernation
It takes shorter to just shut down and restart then to hibernate/wake up currently ... :-(

Installing Ubuntu 9.10 (Karmic Koala) on a ThinkPad T61p

2009-11-25T23:00:10Z

Trampas: /* Compiz */

Tested with new installation of Ubuntu Karmic Koala 64 bit

=Getting the hardware to work=
==Fingerprint Reader==

The [http://thinkfinger.sourceforge.net Thinkfinger] package allows you to swipe a finger in most places where you would have to type your password. This works with sudo, gksudo and on the login page and with a little fix also for the screen saver. Also, you are still required to type your user name on the login screen.

1) Install the following packages:

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

2) For your user:

{{cmduser| sudo tf-tool --acquire && sudo tf-tool --verify}}

A completed fingerprint setup should look something like this:

frank@Laptop:~$ sudo tf-tool --acquire && sudo tf-tool --verify

ThinkFinger 0.3 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>

Initializing... done.
Please swipe your finger (successful swipes 3/3, failed swipes: 0)... done.
Storing data (/tmp/test.bir)... done.

ThinkFinger 0.3 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>

Initializing... done.
Please swipe your finger (successful swipes 1/1, failed swipes: 0)... done.
Result: Fingerprint does match.
frank@CLaptop:~$

This will store your fingerprint information in /home/$USERNAME/.thinkfinger.bir

You should do this step for each user who wants to use the fingerprint reader

3) Enable use of reader for authentication:

{{cmduser| sudo gedit /etc/pam.d/common-auth}}

add
auth sufficient pam_thinkfinger.so
before the line which contains pam_unix.so and add
try_first_pass
to the end of the line containing pam_unix.so.

So it should look something like this:
...
auth sufficient pam_thinkfinger.so
auth [success=1 default=ignore] pam_unix.so nullok_secure try_first_pass
...

4) Check uinput kernel module:

{{cmduser|lsmod | grep uinput}}
If the output starts with uinput, then you're done.
If you don't get any output, then it needs to be started and set to start on boot.

Start uinput:

{{cmduser|sudo modprobe uinput}}

Start on boot:

{{cmduser|sudo gedit /etc/modules}}

make sure there is a line like this or add it at the bottom:
uinput

5) Enabling thinkfinger for gnome-screensaver

*create this file:
{{cmduser|sudo gedit /etc/udev/rules.d/60-thinkfinger.rules}}
with this contents:
#
# 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/Install_Ubuntu_Intrepid_Ibex_on_a_T61p#Fingerprint_Reader
# which was taken and modified from:
# http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
# 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"

*Make the group:
{{cmduser|sudo groupadd fingerprint}}
*per user:
{{cmduser|sudo gpasswd -a $USERNAME fingerprint && sudo chown $USERNAME:root /home/$USERNAME/.thinkfinger.bir }}

Reboot your laptop and you should be ready to swipe!

Sources:
* [[Install_Ubuntu_Gutsy_Gibbon_on_a_T61p#Fingerprint_Reader| Install Ubuntu Gutsy Gibbon on a T61p]]
* [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 Bug #256429: Carriage-return required after finger scan] & [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429/comments/21 Solution for the bug in the comments]
* [[How_to_enable_the_fingerprint_reader_with_ThinkFinger| General page about Fingerprint reader with thinkfinger]] & [[How_to_enable_the_fingerprint_reader_with_ThinkFinger#xscreensaver.2Fgnome-screensaver| Specific gnome-screensaver section]]

== Battery control by tp_smapi ==
The kernel module is not present for some reason in Karmic Koala but there is a source package:
sudo apt-get install tp-smapi-source
cd /usr/src/
sudo tar -xjf tp-smapi.tar.bz2
cd modules/tp-smapi/debian/
sudo module-assistant prepare tp-smapi
sudo module-assistant auto-install tp-smapi

You need to load the kernel module:
sudo modprobe tp_smapi

Check if it was succesfully loaded:
sudo lsmod | grep tp_smapi

For convenience, you could load the kernel module at boot time by adding it to /etc/modules.
echo "tp_smapi" | sudo tee -a /etc/modules

Now, you will be able to have significantly more control over your battery charging via /sys/devices/platform/smapi.

For example, you could set a threshold value of 90% for charging, preventing the battery from charging all the way in exchange for a reduction in the loss of battery capacity that occurs after multiple cycles.
echo "90" | sudo tee -a /sys/devices/platform/smapi/BAT0/stop_charge_thresh

View the number of charge cycles your battery has had in its lifetime:
cat /sys/devices/platform/smapi/BAT0/cycle_count

While AC connected, force discharging of your battery:
echo "1" | sudo tee -a /sys/devices/platform/smapi/BAT0/force_discharge

If you have an Ultrabay battery, you might want to place this [http://forum.thinkpads.com/viewtopic.php?p=433463#p433463 script] into <code>/etc/crontab</code> to keep the Ultrabay battery from being completely discharged to 0%, which permanently damages the battery.
# rolls to BAT0 when remaining capacity on BAT1 is less than 20%. Change .2 if wanted. Swap BAT0 and BAT1 if tp_smapi thinks the ultrabay is BAT0.
awk '{if (/remaining capacity/) left=$3; if (/last full capacity/) full=$4} END {if ((left/full) < .2) system("echo 1 > /sys/devices/platform/smapi/BAT0/force_discharge")}' /proc/acpi/battery/BAT1/*
Remember the script needs root in order to write to the files in <code>/sys/devices/platform/smapi/BAT{0,1}/</code>.

=Problems=
==Compiz==
With compiz enabled flash plug-in for browser will not receive key presses.This is apparently a problem with latest Gnome. This is in the x64 bit version not tested on 32bit.

==Upgrades==
With Nvidia drivers installed from Nvidia it appears that when a new kernel is installed your machine will become unbootable. It will boot to a loginin screen for tty0 which flashes and will randomly ignore key presses thus making it impossible to login. Basically 9.10 sucks and user should stay with 9.04.

==Suspend==
*Does not work with SD card installed, card needs umounted before sleeping. User can modify sleep to umount /dev/mmcblk0*

==Hibernate==

Waking up from hibernation does something like this:
*It shows a mangled screen and waits 15 seconds
*It beeps (hardware beep which i have no idea how to disable)
*It reinitializes the graphics card
*It mangles the screen again and waits 15 seconds
*Again hardware beep
*It reinitilizes the screen again
*Finally everything should be ok and it should be back from hibernation
It takes shorter to just shut down and restart then to hibernate/wake up currently ... :-(

Installing Ubuntu 9.10 (Karmic Koala) on a ThinkPad T61p

2009-11-25T22:59:37Z

Trampas: /* Problems */

Tested with new installation of Ubuntu Karmic Koala 64 bit

=Getting the hardware to work=
==Fingerprint Reader==

The [http://thinkfinger.sourceforge.net Thinkfinger] package allows you to swipe a finger in most places where you would have to type your password. This works with sudo, gksudo and on the login page and with a little fix also for the screen saver. Also, you are still required to type your user name on the login screen.

1) Install the following packages:

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

2) For your user:

{{cmduser| sudo tf-tool --acquire && sudo tf-tool --verify}}

A completed fingerprint setup should look something like this:

frank@Laptop:~$ sudo tf-tool --acquire && sudo tf-tool --verify

ThinkFinger 0.3 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>

Initializing... done.
Please swipe your finger (successful swipes 3/3, failed swipes: 0)... done.
Storing data (/tmp/test.bir)... done.

ThinkFinger 0.3 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>

Initializing... done.
Please swipe your finger (successful swipes 1/1, failed swipes: 0)... done.
Result: Fingerprint does match.
frank@CLaptop:~$

This will store your fingerprint information in /home/$USERNAME/.thinkfinger.bir

You should do this step for each user who wants to use the fingerprint reader

3) Enable use of reader for authentication:

{{cmduser| sudo gedit /etc/pam.d/common-auth}}

add
auth sufficient pam_thinkfinger.so
before the line which contains pam_unix.so and add
try_first_pass
to the end of the line containing pam_unix.so.

So it should look something like this:
...
auth sufficient pam_thinkfinger.so
auth [success=1 default=ignore] pam_unix.so nullok_secure try_first_pass
...

4) Check uinput kernel module:

{{cmduser|lsmod | grep uinput}}
If the output starts with uinput, then you're done.
If you don't get any output, then it needs to be started and set to start on boot.

Start uinput:

{{cmduser|sudo modprobe uinput}}

Start on boot:

{{cmduser|sudo gedit /etc/modules}}

make sure there is a line like this or add it at the bottom:
uinput

5) Enabling thinkfinger for gnome-screensaver

*create this file:
{{cmduser|sudo gedit /etc/udev/rules.d/60-thinkfinger.rules}}
with this contents:
#
# 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/Install_Ubuntu_Intrepid_Ibex_on_a_T61p#Fingerprint_Reader
# which was taken and modified from:
# http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
# 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"

*Make the group:
{{cmduser|sudo groupadd fingerprint}}
*per user:
{{cmduser|sudo gpasswd -a $USERNAME fingerprint && sudo chown $USERNAME:root /home/$USERNAME/.thinkfinger.bir }}

Reboot your laptop and you should be ready to swipe!

Sources:
* [[Install_Ubuntu_Gutsy_Gibbon_on_a_T61p#Fingerprint_Reader| Install Ubuntu Gutsy Gibbon on a T61p]]
* [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 Bug #256429: Carriage-return required after finger scan] & [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429/comments/21 Solution for the bug in the comments]
* [[How_to_enable_the_fingerprint_reader_with_ThinkFinger| General page about Fingerprint reader with thinkfinger]] & [[How_to_enable_the_fingerprint_reader_with_ThinkFinger#xscreensaver.2Fgnome-screensaver| Specific gnome-screensaver section]]

== Battery control by tp_smapi ==
The kernel module is not present for some reason in Karmic Koala but there is a source package:
sudo apt-get install tp-smapi-source
cd /usr/src/
sudo tar -xjf tp-smapi.tar.bz2
cd modules/tp-smapi/debian/
sudo module-assistant prepare tp-smapi
sudo module-assistant auto-install tp-smapi

You need to load the kernel module:
sudo modprobe tp_smapi

Check if it was succesfully loaded:
sudo lsmod | grep tp_smapi

For convenience, you could load the kernel module at boot time by adding it to /etc/modules.
echo "tp_smapi" | sudo tee -a /etc/modules

Now, you will be able to have significantly more control over your battery charging via /sys/devices/platform/smapi.

For example, you could set a threshold value of 90% for charging, preventing the battery from charging all the way in exchange for a reduction in the loss of battery capacity that occurs after multiple cycles.
echo "90" | sudo tee -a /sys/devices/platform/smapi/BAT0/stop_charge_thresh

View the number of charge cycles your battery has had in its lifetime:
cat /sys/devices/platform/smapi/BAT0/cycle_count

While AC connected, force discharging of your battery:
echo "1" | sudo tee -a /sys/devices/platform/smapi/BAT0/force_discharge

If you have an Ultrabay battery, you might want to place this [http://forum.thinkpads.com/viewtopic.php?p=433463#p433463 script] into <code>/etc/crontab</code> to keep the Ultrabay battery from being completely discharged to 0%, which permanently damages the battery.
# rolls to BAT0 when remaining capacity on BAT1 is less than 20%. Change .2 if wanted. Swap BAT0 and BAT1 if tp_smapi thinks the ultrabay is BAT0.
awk '{if (/remaining capacity/) left=$3; if (/last full capacity/) full=$4} END {if ((left/full) < .2) system("echo 1 > /sys/devices/platform/smapi/BAT0/force_discharge")}' /proc/acpi/battery/BAT1/*
Remember the script needs root in order to write to the files in <code>/sys/devices/platform/smapi/BAT{0,1}/</code>.

=Problems=
==Compiz==
With compiz enabled flash plug-in for browser will not receive key presses.This is apparently a problem with latest Gnome.

==Upgrades==
With Nvidia drivers installed from Nvidia it appears that when a new kernel is installed your machine will become unbootable. It will boot to a loginin screen for tty0 which flashes and will randomly ignore key presses thus making it impossible to login. Basically 9.10 sucks and user should stay with 9.04.

==Suspend==
*Does not work with SD card installed, card needs umounted before sleeping. User can modify sleep to umount /dev/mmcblk0*

==Hibernate==

Waking up from hibernation does something like this:
*It shows a mangled screen and waits 15 seconds
*It beeps (hardware beep which i have no idea how to disable)
*It reinitializes the graphics card
*It mangles the screen again and waits 15 seconds
*Again hardware beep
*It reinitilizes the screen again
*Finally everything should be ok and it should be back from hibernation
It takes shorter to just shut down and restart then to hibernate/wake up currently ... :-(

Installing Ubuntu 9.10 (Karmic Koala) on a ThinkPad T61p

2009-11-25T22:59:12Z

Trampas: /* Problems */

Tested with new installation of Ubuntu Karmic Koala 64 bit

=Getting the hardware to work=
==Fingerprint Reader==

The [http://thinkfinger.sourceforge.net Thinkfinger] package allows you to swipe a finger in most places where you would have to type your password. This works with sudo, gksudo and on the login page and with a little fix also for the screen saver. Also, you are still required to type your user name on the login screen.

1) Install the following packages:

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

2) For your user:

{{cmduser| sudo tf-tool --acquire && sudo tf-tool --verify}}

A completed fingerprint setup should look something like this:

frank@Laptop:~$ sudo tf-tool --acquire && sudo tf-tool --verify

ThinkFinger 0.3 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>

Initializing... done.
Please swipe your finger (successful swipes 3/3, failed swipes: 0)... done.
Storing data (/tmp/test.bir)... done.

ThinkFinger 0.3 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>

Initializing... done.
Please swipe your finger (successful swipes 1/1, failed swipes: 0)... done.
Result: Fingerprint does match.
frank@CLaptop:~$

This will store your fingerprint information in /home/$USERNAME/.thinkfinger.bir

You should do this step for each user who wants to use the fingerprint reader

3) Enable use of reader for authentication:

{{cmduser| sudo gedit /etc/pam.d/common-auth}}

add
auth sufficient pam_thinkfinger.so
before the line which contains pam_unix.so and add
try_first_pass
to the end of the line containing pam_unix.so.

So it should look something like this:
...
auth sufficient pam_thinkfinger.so
auth [success=1 default=ignore] pam_unix.so nullok_secure try_first_pass
...

4) Check uinput kernel module:

{{cmduser|lsmod | grep uinput}}
If the output starts with uinput, then you're done.
If you don't get any output, then it needs to be started and set to start on boot.

Start uinput:

{{cmduser|sudo modprobe uinput}}

Start on boot:

{{cmduser|sudo gedit /etc/modules}}

make sure there is a line like this or add it at the bottom:
uinput

5) Enabling thinkfinger for gnome-screensaver

*create this file:
{{cmduser|sudo gedit /etc/udev/rules.d/60-thinkfinger.rules}}
with this contents:
#
# 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/Install_Ubuntu_Intrepid_Ibex_on_a_T61p#Fingerprint_Reader
# which was taken and modified from:
# http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
# 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"

*Make the group:
{{cmduser|sudo groupadd fingerprint}}
*per user:
{{cmduser|sudo gpasswd -a $USERNAME fingerprint && sudo chown $USERNAME:root /home/$USERNAME/.thinkfinger.bir }}

Reboot your laptop and you should be ready to swipe!

Sources:
* [[Install_Ubuntu_Gutsy_Gibbon_on_a_T61p#Fingerprint_Reader| Install Ubuntu Gutsy Gibbon on a T61p]]
* [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 Bug #256429: Carriage-return required after finger scan] & [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429/comments/21 Solution for the bug in the comments]
* [[How_to_enable_the_fingerprint_reader_with_ThinkFinger| General page about Fingerprint reader with thinkfinger]] & [[How_to_enable_the_fingerprint_reader_with_ThinkFinger#xscreensaver.2Fgnome-screensaver| Specific gnome-screensaver section]]

== Battery control by tp_smapi ==
The kernel module is not present for some reason in Karmic Koala but there is a source package:
sudo apt-get install tp-smapi-source
cd /usr/src/
sudo tar -xjf tp-smapi.tar.bz2
cd modules/tp-smapi/debian/
sudo module-assistant prepare tp-smapi
sudo module-assistant auto-install tp-smapi

You need to load the kernel module:
sudo modprobe tp_smapi

Check if it was succesfully loaded:
sudo lsmod | grep tp_smapi

For convenience, you could load the kernel module at boot time by adding it to /etc/modules.
echo "tp_smapi" | sudo tee -a /etc/modules

Now, you will be able to have significantly more control over your battery charging via /sys/devices/platform/smapi.

For example, you could set a threshold value of 90% for charging, preventing the battery from charging all the way in exchange for a reduction in the loss of battery capacity that occurs after multiple cycles.
echo "90" | sudo tee -a /sys/devices/platform/smapi/BAT0/stop_charge_thresh

View the number of charge cycles your battery has had in its lifetime:
cat /sys/devices/platform/smapi/BAT0/cycle_count

While AC connected, force discharging of your battery:
echo "1" | sudo tee -a /sys/devices/platform/smapi/BAT0/force_discharge

If you have an Ultrabay battery, you might want to place this [http://forum.thinkpads.com/viewtopic.php?p=433463#p433463 script] into <code>/etc/crontab</code> to keep the Ultrabay battery from being completely discharged to 0%, which permanently damages the battery.
# rolls to BAT0 when remaining capacity on BAT1 is less than 20%. Change .2 if wanted. Swap BAT0 and BAT1 if tp_smapi thinks the ultrabay is BAT0.
awk '{if (/remaining capacity/) left=$3; if (/last full capacity/) full=$4} END {if ((left/full) < .2) system("echo 1 > /sys/devices/platform/smapi/BAT0/force_discharge")}' /proc/acpi/battery/BAT1/*
Remember the script needs root in order to write to the files in <code>/sys/devices/platform/smapi/BAT{0,1}/</code>.

=Problems=
==Compiz==
With compiz enabled flash plug-in for browser will not receive key presses.This is apparently a problem with latest Gnome.

==Upgrades===
With Nvidia drivers installed from Nvidia it appears that when a new kernel is installed your machine will become unbootable. It will boot to a loginin screen for tty0 which flashes and will randomly ignore key presses thus making it impossible to login. Basically 9.10 sucks and user should stay with 9.04.

==Suspend==
*Does not work with SD card installed, card needs umounted before sleeping. User can modify sleep to umount /dev/mmcblk0*

==Hibernate==

Waking up from hibernation does something like this:
*It shows a mangled screen and waits 15 seconds
*It beeps (hardware beep which i have no idea how to disable)
*It reinitializes the graphics card
*It mangles the screen again and waits 15 seconds
*Again hardware beep
*It reinitilizes the screen again
*Finally everything should be ok and it should be back from hibernation
It takes shorter to just shut down and restart then to hibernate/wake up currently ... :-(

Installing Ubuntu 9.10 (Karmic Koala) on a ThinkPad T61p

2009-11-25T22:57:37Z

Trampas: /* Problems */

Tested with new installation of Ubuntu Karmic Koala 64 bit

=Getting the hardware to work=
==Fingerprint Reader==

The [http://thinkfinger.sourceforge.net Thinkfinger] package allows you to swipe a finger in most places where you would have to type your password. This works with sudo, gksudo and on the login page and with a little fix also for the screen saver. Also, you are still required to type your user name on the login screen.

1) Install the following packages:

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

2) For your user:

{{cmduser| sudo tf-tool --acquire && sudo tf-tool --verify}}

A completed fingerprint setup should look something like this:

frank@Laptop:~$ sudo tf-tool --acquire && sudo tf-tool --verify

ThinkFinger 0.3 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>

Initializing... done.
Please swipe your finger (successful swipes 3/3, failed swipes: 0)... done.
Storing data (/tmp/test.bir)... done.

ThinkFinger 0.3 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>

Initializing... done.
Please swipe your finger (successful swipes 1/1, failed swipes: 0)... done.
Result: Fingerprint does match.
frank@CLaptop:~$

This will store your fingerprint information in /home/$USERNAME/.thinkfinger.bir

You should do this step for each user who wants to use the fingerprint reader

3) Enable use of reader for authentication:

{{cmduser| sudo gedit /etc/pam.d/common-auth}}

add
auth sufficient pam_thinkfinger.so
before the line which contains pam_unix.so and add
try_first_pass
to the end of the line containing pam_unix.so.

So it should look something like this:
...
auth sufficient pam_thinkfinger.so
auth [success=1 default=ignore] pam_unix.so nullok_secure try_first_pass
...

4) Check uinput kernel module:

{{cmduser|lsmod | grep uinput}}
If the output starts with uinput, then you're done.
If you don't get any output, then it needs to be started and set to start on boot.

Start uinput:

{{cmduser|sudo modprobe uinput}}

Start on boot:

{{cmduser|sudo gedit /etc/modules}}

make sure there is a line like this or add it at the bottom:
uinput

5) Enabling thinkfinger for gnome-screensaver

*create this file:
{{cmduser|sudo gedit /etc/udev/rules.d/60-thinkfinger.rules}}
with this contents:
#
# 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/Install_Ubuntu_Intrepid_Ibex_on_a_T61p#Fingerprint_Reader
# which was taken and modified from:
# http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
# 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"

*Make the group:
{{cmduser|sudo groupadd fingerprint}}
*per user:
{{cmduser|sudo gpasswd -a $USERNAME fingerprint && sudo chown $USERNAME:root /home/$USERNAME/.thinkfinger.bir }}

Reboot your laptop and you should be ready to swipe!

Sources:
* [[Install_Ubuntu_Gutsy_Gibbon_on_a_T61p#Fingerprint_Reader| Install Ubuntu Gutsy Gibbon on a T61p]]
* [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 Bug #256429: Carriage-return required after finger scan] & [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429/comments/21 Solution for the bug in the comments]
* [[How_to_enable_the_fingerprint_reader_with_ThinkFinger| General page about Fingerprint reader with thinkfinger]] & [[How_to_enable_the_fingerprint_reader_with_ThinkFinger#xscreensaver.2Fgnome-screensaver| Specific gnome-screensaver section]]

== Battery control by tp_smapi ==
The kernel module is not present for some reason in Karmic Koala but there is a source package:
sudo apt-get install tp-smapi-source
cd /usr/src/
sudo tar -xjf tp-smapi.tar.bz2
cd modules/tp-smapi/debian/
sudo module-assistant prepare tp-smapi
sudo module-assistant auto-install tp-smapi

You need to load the kernel module:
sudo modprobe tp_smapi

Check if it was succesfully loaded:
sudo lsmod | grep tp_smapi

For convenience, you could load the kernel module at boot time by adding it to /etc/modules.
echo "tp_smapi" | sudo tee -a /etc/modules

Now, you will be able to have significantly more control over your battery charging via /sys/devices/platform/smapi.

For example, you could set a threshold value of 90% for charging, preventing the battery from charging all the way in exchange for a reduction in the loss of battery capacity that occurs after multiple cycles.
echo "90" | sudo tee -a /sys/devices/platform/smapi/BAT0/stop_charge_thresh

View the number of charge cycles your battery has had in its lifetime:
cat /sys/devices/platform/smapi/BAT0/cycle_count

While AC connected, force discharging of your battery:
echo "1" | sudo tee -a /sys/devices/platform/smapi/BAT0/force_discharge

If you have an Ultrabay battery, you might want to place this [http://forum.thinkpads.com/viewtopic.php?p=433463#p433463 script] into <code>/etc/crontab</code> to keep the Ultrabay battery from being completely discharged to 0%, which permanently damages the battery.
# rolls to BAT0 when remaining capacity on BAT1 is less than 20%. Change .2 if wanted. Swap BAT0 and BAT1 if tp_smapi thinks the ultrabay is BAT0.
awk '{if (/remaining capacity/) left=$3; if (/last full capacity/) full=$4} END {if ((left/full) < .2) system("echo 1 > /sys/devices/platform/smapi/BAT0/force_discharge")}' /proc/acpi/battery/BAT1/*
Remember the script needs root in order to write to the files in <code>/sys/devices/platform/smapi/BAT{0,1}/</code>.

=Problems=
==Upgrades===
With Nvidia drivers installed from Nvidia it appears that when a new kernel is installed your machine will become unbootable. It will boot to a loginin screen for tty0 which flashes and will randomly ignore key presses thus making it impossible to login. Basically 9.10 sucks and user should stay with 9.04.

==Suspend==
*Does not work with SD card installed, card needs umounted before sleeping. User can modify sleep to umount /dev/mmcblk0*

==Hibernate==

Waking up from hibernation does something like this:
*It shows a mangled screen and waits 15 seconds
*It beeps (hardware beep which i have no idea how to disable)
*It reinitializes the graphics card
*It mangles the screen again and waits 15 seconds
*Again hardware beep
*It reinitilizes the screen again
*Finally everything should be ok and it should be back from hibernation
It takes shorter to just shut down and restart then to hibernate/wake up currently ... :-(

Install Ubuntu Intrepid Ibex on a T61p

2009-01-18T16:23:00Z

Trampas: /* Other Problems */

=What works out of the box?=
*Wireless (Intel 3945ABG or 4965AGN)
**Only tested G mode
*Wired LAN
*Video (VESA)
**Hardware Drivers panel offers to install nVIDIA proprietary drivers on first boot.
*Touchpoint and Trackpad
**Including scroll at the right side of the pad by default.
**Middle-button scrolling does NOT work (fix below)
*Optical drive
**Optiarc AD-7910A works fine with Brasero disc burning
***Tested: CD-R, DVD+R
*Sound card
*SD/MMC Memory card reader (Ricoh)
**Only tested SD (non-HC) cards.
*Control buttons/Hotkeys
**Volume control buttons
**Screen brightness control
**Thinklight control
**WLAN/BT/OFF toggle
**Media player control
**fingerprint reader does NOT work (fix below)
*Some ACPI features
**Battery status, power graphs and history
**Lid states and events
**Only tested with a single 6-cell battery
*ACPI features
** Suspend to RAM
** Suspend to Disk (Hibernate) FINALLY!! Be patient, though.
** STR and STD work even with full disk encryption (DM-crypt + LVM)!

=Getting the hardware to work=
==Display/Video==
Installing the proprietary NVidia drivers is highly recommended, EVEN IF you won't use 3D acceleration, because the open source nv driver will drain your battery much faster since it does not support PowerMizer at all. Practically, this means that the GPU will constantly run at full speed, thus consuming ~12 Watts more than it would otherwise (which is a LOT of power for a laptop).

The first time you boot Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at

System --> Administration --> Hardware Drivers.

You will have a choice between the 173 and 177 version of the driver.
*pro:
**Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not.
*con:
**version 177 causes a log out bug that is addressed below.
**version 177 might show some issues like terminal output not updating in some very weird cases (which I did not see in v173, this seems to have something to do with powermizer as well ...)
**version 180 as of 180.22 is known to have issue with suspend. Stay with version 177 until problem is fixed.

Once the proprietary drivers are installed, the "NVidia X Server Settings" program will be available in System --> Administration.

===Version 177 logout/X restart fix===
There is a known issue in the v177 proprietary NVidia driver - See Launchpad bug [http://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-177/+bug/258357 258357]. Once you install the v177 driver, logging out or restarting X will cease to work, though suspend to RAM/Disk will continue to function.

The work around is as follows:
* In /etc/gdm/gdm.conf , increase the value for GdmXserverTimeout to about 60. When logging out or restarting X, X will hang for ~35 seconds. By increasing the value from its default, GDM will give X more time before it assumes X is faulty.

===Choppy Compiz animations===
NVidia's PowerMizer feature will slow down the GPU when "inactive" even on AC power.

The NVidia driver does not report the correct refresh rate of the display to Compiz, resulting in choppy animations and effects. To fix this, install the <code>compizconfig-settings-manager</code> package, then go to System --> Preferences --> Advanced Desktop Effects Settings (also might be called CompizConfig Settings Manager). Click on General Options, go to the Display Settings tab, uncheck the Detect Refresh rate box and drag the Refresh Rate slider to 60. Also, check the Sync To VBlank box. This will improve the smoothness of the window animations significantly if you're sensitive to the choppy animations.

Compiz animations can also be choppy due to NVidia's PowerMizer feature, which slows down the GPU to conserve power when it is not in use. This works well for 3D games which constantly use 3D acceleration, but poorly for Compiz which uses the GPU in small bursts. It seems that the interval of the PowerMizer is way too long and is not speeding up when using in bursts. Fortunately, the situation seems to have improved in version 177 of the NVidia driver. To workaround this problem, I made a couple of shell scripts which keep the GPU at its highest speed while running on AC power. The first one is named "powermizer-loop" and does most of the work:

#!/bin/sh

while true; do

powerstate=`cat /proc/acpi/ac_adapter/AC/state | awk '{print $2}'`

if [ $powerstate = "on-line" ]; then
nvidia-settings -q all > /dev/null
fi
sleep 25;
done

The second is named "powermizer-off" and starts up powermizer-loop when I log in, ensuring that only one copy runs at a time:

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

I put both of these scripts in my home directory and made them executable by doing:

chmod a+x powermizer-loop powermizer-off

Then to make powermizer-off run on login, I opened System --> Preferences --> Sessions, clicked on Add, and entered the command to run the script, i.e. "/home/<user>/powermizer-off".

Of course, performance still suffers when running on battery, but hopefully NVidia will fix this problem in a future version of their driver.

=== EDID misdetection ===

EDID (Extended Display Identification Data) might be misdetected for your display, which reduces the number of resolutions available in the NVidia X Server Settings application. (For example, I was unable to set my laptop's screen to 1024x768 for use with a projector during a presentation.) If you encounter this problem, add the following lines to /etc/X11/xorg.conf in the "Screen" section:

Option "UseEdidFreqs" "FALSE"
Option "HorizSync" "40-70"

The 40-70 values are just an example. They seem to work well with my 1680x1050 display. You should put the values of your display there. On a 1920x1200 display, making this change prevents the display from coming on when X starts.

A better but more complicated way would be using Phoenix EDID Designer to dump and fix the EDID data and then setup the Nvidia driver so it will use the customized EDID data, as described at [http://myricci.com/index.php?option=com_content&task=view&id=36]

==Microphone/Sound In==
Might need to be turned on in the mixer. See [[Install Ubuntu Hardy Heron on a T61p#Internal Microphone/Microphone Input Jack]]

==Front radio kill switch==
When killing Wireless LAN with the killswitch at the front, you won't be able to get WLAN back up after switching back. See Launchpad bugs [http://bugs.launchpad.net/ubuntu/+source/hal/+bug/289286 289286] and [http://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.24/+bug/193970 193970] and the [https://wiki.ubuntu.com/IntrepidReleaseNotes#Cannot%20reactivate%20Intel%203945/4965%20wireless%20if%20booting%20with%20killswitch%20enabled Release Notes] on the Ubuntu Wiki.

This will be solved in intrepid-updates eventually.

For now there are a few ways to bring the interface back up (choose one):
* Right click the network manager icon in the tray, uncheck Enable Wireless, then check it again does the trick (at least for me)
* {{cmdroot|ip l s wlan0 up}}
* {{cmdroot|modprobe -r iwl3945 && modprobe iwl3945}}
* reboot
* suspend and resume

== Middle-button Scrolling ==
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.

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

{{cmduser| sudo gedit /etc/hal/fdi/policy/mouse-wheel.fdi}}

Paste and save the following code, which will give vertical wheel emulation only:
<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>
There is [http://psung.blogspot.com/2008/09/scrolling-with-thinkpads-trackpoint-in.html another method] to get horizontal scrolling as well, but this is not confirmed to work.

source:
*[[Installing_Ubuntu_8.10_%28Intrepid_Ibex%29_on_a_ThinkPad_T61#Emulate_Wheel_.28Middle-click_scrolling.29| Installing Ubuntu 8.10 (Intrepid Ibex) on a ThinkPad T61 - Emulate Wheel (Middle-click scrolling)]]

==Fingerprint Reader==

The [http://thinkfinger.sourceforge.net Thinkfinger] package allows you to swipe a finger in most places where you would have to type your password. This works with sudo, gksudo and on the login page and with a little fix also for the screen saver. Also, you are still required to type your user name on the login screen.

0) Set up the third party repository (optional but recommended!)

due to this [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 Bug #256429: Carriage-return required after finger scan] you need to press the return key after you swipe your finger with the current version of the kernel and the packages in ubuntu. The bug is caused by the fact that it does not recognize the fingerprint reader 100% correctly ([https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429/comments/29 Description of the root cause]) , as a temporary workaround there is a special package repository.

The packages present in ubuntu intrepid will work but you need to press enter after you swipe your finger.

Click System -> administration -> software sources
go to the tab "third-party software" and click Add ...

Enter in the popup window:

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

Click Add source, it will ask to refresh the package list, click reload.

1) Install the following packages:

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

2) For your user:

{{cmduser| sudo tf-tool --acquire && sudo tf-tool --verify}}

A completed fingerprint setup should look something like this:

frank@Laptop:~$ sudo tf-tool --acquire && sudo tf-tool --verify

ThinkFinger 0.3 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>

Initializing... done.
Please swipe your finger (successful swipes 3/3, failed swipes: 0)... done.
Storing data (/tmp/test.bir)... done.

ThinkFinger 0.3 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>

Initializing... done.
Please swipe your finger (successful swipes 1/1, failed swipes: 0)... done.
Result: Fingerprint does match.
frank@CLaptop:~$

This will store your fingerprint information in /home/$USERNAME/.thinkfinger.bir

You should do this step for each user who wants to use the fingerprint reader

3) Enable use of reader for authentication:

{{cmduser| sudo gedit /etc/pam.d/common-auth}}

add
auth sufficient pam_thinkfinger.so
before the line which contains pam_unix.so and add
try_first_pass
to the end of the line containing pam_unix.so.

So it should look something like this:
...
auth sufficient pam_thinkfinger.so
auth [success=1 default=ignore] pam_unix.so nullok_secure try_first_pass
...

4) Check uinput kernel module:

{{cmduser|lsmod | grep uinput}}
If the output starts with uinput, then you're done.
If you don't get any output, then it needs to be started and set to start on boot.

Start uinput:

{{cmduser|sudo modprobe uinput}}

Start on boot:

{{cmduser|sudo gedit /etc/modules}}

make sure there is a line like this or add it at the bottom:
uinput

5) Enabling thinkfinger for gnome-screensaver

*create this file:
{{cmduser|sudo gedit /etc/udev/rules.d/60-thinkfinger.rules}}
with this contents:
#
# 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/Install_Ubuntu_Intrepid_Ibex_on_a_T61p#Fingerprint_Reader
# which was taken and modified from:
# http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
# 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"

*Make the group:
{{cmduser|sudo groupadd fingerprint}}
*per user:
{{cmduser|sudo gpasswd -a $USERNAME fingerprint && sudo chown $USERNAME:root /home/$USERNAME/.thinkfinger.bir }}

Reboot your laptop and you should be ready to swipe!

Sources:
* [[Install_Ubuntu_Gutsy_Gibbon_on_a_T61p#Fingerprint_Reader| Install Ubuntu Gutsy Gibbon on a T61p]]
* [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 Bug #256429: Carriage-return required after finger scan] & [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429/comments/21 Solution for the bug in the comments]
* [https://launchpad.net/~jon-oberheide/+archive Repository for the third party fix] credits to [https://launchpad.net/~jon-oberheide Jon Oberheide]
* [[How_to_enable_the_fingerprint_reader_with_ThinkFinger| General page about Fingerprint reader with thinkfinger]] & [[How_to_enable_the_fingerprint_reader_with_ThinkFinger#xscreensaver.2Fgnome-screensaver| Specific gnome-screensaver section]]

==Hard Drive Active Protection System (APS ~ HDAPS)==
Please add to this section

Some interesting links:
* [[Active_Protection_System| Description of APS]]
* [[How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS]]
* [[Tp_smapi| tp_smapi kernel modules]]

=Other Problems=
== Resume Disables WLAN ==
On power up CDMA WLAN module is enabled, if user suspense and resumes it is turned off - no known fix.
Additionally fn-F5 turns off bluetooth but no option to turn off WLAN using function keys. This is problem is on the 6459CTO.

== Resume Requests WIFI Network Key ==
On resume Network Manager request the wifi network key several times before connecting to network. This has been noted on a 6459CTO laptop and no known fix is available. Currently with this problem it takes several minutes to regain network access after resume.

== Black Screen on Resume ==
On the 6459CTO with default 8.10 install suspend did not work. Installing the proposed updated fixed the problem. To do this add the following line to /etc/apt/sources.list

deb http://us.archive.ubuntu.com/ubuntu/ intrepid-proposed restricted main universe multiverse

== Wireless not working after resume (Atheros) ==
After resuming from suspend, I am unable to reconnect to my wireless network. Network Manager asks me for my password over and over again but never succeeds in connecting. I'm using the Thinkpad (Atheros) A/B/G wireless card.

To fix this problem, I followed the instructions listed at https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/275692. Specifically, I created a file called /etc/pm/config.d/01-modules and put the following line in it:

SUSPEND_MODULES="ath_pci"

== Brightness control on battery power ==
By default, when unplugging the AC power while the system is running, the brightness of the display goes down even when you have set not to in the Power Management settings and you are not able to reach a brightness level as high as possible when connected to AC power. This is not a software setting or GNOME bug, but a BIOS setting. In the BIOS you can find a brightness setting in the Power section. Set it to high for normal, expected behavior. You can let the GNOME Power Manager still lower the brightness, but you will be able to increase it when needed.

=Software Install=
==Adobe Flash==
Adobe has plug-ins direct for 32 bit version for x64 download the libflashplayer.so file from here:
http://labs.adobe.com/downloads/flashplayer10.html
Then copy to the mozilla plugins directory
sudo cp libflashplayer.so /usr/lib/firefox-addons/plugins/

=Other Information=
== Saving power ==
Some nice information on power saving you can find at

http://www.lesswatts.org

A tool that allows you to test most tips and tricks to reduce power is powertop, you can install it using

{{cmduser|sudo apt-get install powertop}}

and run it with:

{{cmduser|sudo powertop}}

For more information see http://www.lesswatts.org/projects/powertop/
== Battery control by tp_smapi ==
You need to load a kernel module first:
sudo modprobe tp_smapi

Now, you will be able to have significantly more control over your battery charging via /sys/devices/platform/smapi.

For example, you could set a threshold value of 90% for charging, preventing the battery from charging all the way in exchange for a reduction in the loss of battery capacity that occurs after multiple cycles.
echo "90" | sudo tee -a /sys/devices/platform/smapi/BAT0/start_charge_thresh
(by default this was set to 86% on my laptop)

View the number of charge cycles your battery has had in its lifetime:
cat /sys/devices/platform/smapi/BAT0/cycle_count

While AC connected, force discharging of your battery:
echo "1" | sudo tee -a /sys/devices/platform/smapi/BAT0/force_discharge

For convenience, you could load the kernel module at boot time by adding it to /etc/modules.
echo "tp_smapi" | sudo tee -a /etc/modules

If you have an Ultrabay battery, you might want to place this [http://forum.thinkpads.com/viewtopic.php?p=433463#p433463 script] into <code>/etc/crontab</code> to keep the Ultrabay battery from being completely discharged to 0%, which permanently damages the battery.
# rolls to BAT0 when remaining capacity on BAT1 is less than 20%. Change .2 if wanted. Swap BAT0 and BAT1 if tp_smapi thinks the ultrabay is BAT0.
awk '{if (/remaining capacity/) left=$3; if (/last full capacity/) full=$4} END {if ((left/full) < .2) system("echo 1 > /sys/devices/platform/smapi/BAT0/force_discharge")}' /proc/acpi/battery/BAT1/*
Remember the script needs root in order to write to the files in <code>/sys/devices/platform/smapi/BAT{0,1}/</code>.

= Compared to Hardy (8.04) =
Why upgrade your T61p to Intrepid or why not? (Specific for T61p)
== Improvements ==
*Ricoh SD card reader now reads read-only SD card. (Tested with Adata 150X 2GB SD card)
*Newer Wireless LAN drivers. For Intel cards this results in working LED, more sensitive reception, increased stability of connections and some 802.1x bugfixes.
*Out-of-the-box Suspend to RAM functionality (also faster resume). Not on 6459, (see above)
*Working but slow Suspend to Disk functionality.

== Bugs and Regressions ==
*Hard radio killswitch (at the front) cannot bring WLAN back up after killing it. (workaround available)
*X hangs for approx. 35 seconds when restarting or logging out. (workaround available)
*Atheros WLAN not working after resume from Suspend to RAM (but a workaround is available; [[#Wireless_not_working_after_resume_.28Atheros.29|see above]]).

[[Category:T61p]]
[[Category:Ubuntu]]
[[Category:Ubuntu 8.10]]

Install Ubuntu Intrepid Ibex on a T61p

2009-01-18T16:07:25Z

Trampas: /* Adobe Flash */

=What works out of the box?=
*Wireless (Intel 3945ABG or 4965AGN)
**Only tested G mode
*Wired LAN
*Video (VESA)
**Hardware Drivers panel offers to install nVIDIA proprietary drivers on first boot.
*Touchpoint and Trackpad
**Including scroll at the right side of the pad by default.
**Middle-button scrolling does NOT work (fix below)
*Optical drive
**Optiarc AD-7910A works fine with Brasero disc burning
***Tested: CD-R, DVD+R
*Sound card
*SD/MMC Memory card reader (Ricoh)
**Only tested SD (non-HC) cards.
*Control buttons/Hotkeys
**Volume control buttons
**Screen brightness control
**Thinklight control
**WLAN/BT/OFF toggle
**Media player control
**fingerprint reader does NOT work (fix below)
*Some ACPI features
**Battery status, power graphs and history
**Lid states and events
**Only tested with a single 6-cell battery
*ACPI features
** Suspend to RAM
** Suspend to Disk (Hibernate) FINALLY!! Be patient, though.
** STR and STD work even with full disk encryption (DM-crypt + LVM)!

=Getting the hardware to work=
==Display/Video==
Installing the proprietary NVidia drivers is highly recommended, EVEN IF you won't use 3D acceleration, because the open source nv driver will drain your battery much faster since it does not support PowerMizer at all. Practically, this means that the GPU will constantly run at full speed, thus consuming ~12 Watts more than it would otherwise (which is a LOT of power for a laptop).

The first time you boot Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at

System --> Administration --> Hardware Drivers.

You will have a choice between the 173 and 177 version of the driver.
*pro:
**Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not.
*con:
**version 177 causes a log out bug that is addressed below.
**version 177 might show some issues like terminal output not updating in some very weird cases (which I did not see in v173, this seems to have something to do with powermizer as well ...)
**version 180 as of 180.22 is known to have issue with suspend. Stay with version 177 until problem is fixed.

Once the proprietary drivers are installed, the "NVidia X Server Settings" program will be available in System --> Administration.

===Version 177 logout/X restart fix===
There is a known issue in the v177 proprietary NVidia driver - See Launchpad bug [http://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-177/+bug/258357 258357]. Once you install the v177 driver, logging out or restarting X will cease to work, though suspend to RAM/Disk will continue to function.

The work around is as follows:
* In /etc/gdm/gdm.conf , increase the value for GdmXserverTimeout to about 60. When logging out or restarting X, X will hang for ~35 seconds. By increasing the value from its default, GDM will give X more time before it assumes X is faulty.

===Choppy Compiz animations===
NVidia's PowerMizer feature will slow down the GPU when "inactive" even on AC power.

The NVidia driver does not report the correct refresh rate of the display to Compiz, resulting in choppy animations and effects. To fix this, install the <code>compizconfig-settings-manager</code> package, then go to System --> Preferences --> Advanced Desktop Effects Settings (also might be called CompizConfig Settings Manager). Click on General Options, go to the Display Settings tab, uncheck the Detect Refresh rate box and drag the Refresh Rate slider to 60. Also, check the Sync To VBlank box. This will improve the smoothness of the window animations significantly if you're sensitive to the choppy animations.

Compiz animations can also be choppy due to NVidia's PowerMizer feature, which slows down the GPU to conserve power when it is not in use. This works well for 3D games which constantly use 3D acceleration, but poorly for Compiz which uses the GPU in small bursts. It seems that the interval of the PowerMizer is way too long and is not speeding up when using in bursts. Fortunately, the situation seems to have improved in version 177 of the NVidia driver. To workaround this problem, I made a couple of shell scripts which keep the GPU at its highest speed while running on AC power. The first one is named "powermizer-loop" and does most of the work:

#!/bin/sh

while true; do

powerstate=`cat /proc/acpi/ac_adapter/AC/state | awk '{print $2}'`

if [ $powerstate = "on-line" ]; then
nvidia-settings -q all > /dev/null
fi
sleep 25;
done

The second is named "powermizer-off" and starts up powermizer-loop when I log in, ensuring that only one copy runs at a time:

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

I put both of these scripts in my home directory and made them executable by doing:

chmod a+x powermizer-loop powermizer-off

Then to make powermizer-off run on login, I opened System --> Preferences --> Sessions, clicked on Add, and entered the command to run the script, i.e. "/home/<user>/powermizer-off".

Of course, performance still suffers when running on battery, but hopefully NVidia will fix this problem in a future version of their driver.

=== EDID misdetection ===

EDID (Extended Display Identification Data) might be misdetected for your display, which reduces the number of resolutions available in the NVidia X Server Settings application. (For example, I was unable to set my laptop's screen to 1024x768 for use with a projector during a presentation.) If you encounter this problem, add the following lines to /etc/X11/xorg.conf in the "Screen" section:

Option "UseEdidFreqs" "FALSE"
Option "HorizSync" "40-70"

The 40-70 values are just an example. They seem to work well with my 1680x1050 display. You should put the values of your display there. On a 1920x1200 display, making this change prevents the display from coming on when X starts.

A better but more complicated way would be using Phoenix EDID Designer to dump and fix the EDID data and then setup the Nvidia driver so it will use the customized EDID data, as described at [http://myricci.com/index.php?option=com_content&task=view&id=36]

==Microphone/Sound In==
Might need to be turned on in the mixer. See [[Install Ubuntu Hardy Heron on a T61p#Internal Microphone/Microphone Input Jack]]

==Front radio kill switch==
When killing Wireless LAN with the killswitch at the front, you won't be able to get WLAN back up after switching back. See Launchpad bugs [http://bugs.launchpad.net/ubuntu/+source/hal/+bug/289286 289286] and [http://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.24/+bug/193970 193970] and the [https://wiki.ubuntu.com/IntrepidReleaseNotes#Cannot%20reactivate%20Intel%203945/4965%20wireless%20if%20booting%20with%20killswitch%20enabled Release Notes] on the Ubuntu Wiki.

This will be solved in intrepid-updates eventually.

For now there are a few ways to bring the interface back up (choose one):
* Right click the network manager icon in the tray, uncheck Enable Wireless, then check it again does the trick (at least for me)
* {{cmdroot|ip l s wlan0 up}}
* {{cmdroot|modprobe -r iwl3945 && modprobe iwl3945}}
* reboot
* suspend and resume

== Middle-button Scrolling ==
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.

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

{{cmduser| sudo gedit /etc/hal/fdi/policy/mouse-wheel.fdi}}

Paste and save the following code, which will give vertical wheel emulation only:
<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>
There is [http://psung.blogspot.com/2008/09/scrolling-with-thinkpads-trackpoint-in.html another method] to get horizontal scrolling as well, but this is not confirmed to work.

source:
*[[Installing_Ubuntu_8.10_%28Intrepid_Ibex%29_on_a_ThinkPad_T61#Emulate_Wheel_.28Middle-click_scrolling.29| Installing Ubuntu 8.10 (Intrepid Ibex) on a ThinkPad T61 - Emulate Wheel (Middle-click scrolling)]]

==Fingerprint Reader==

The [http://thinkfinger.sourceforge.net Thinkfinger] package allows you to swipe a finger in most places where you would have to type your password. This works with sudo, gksudo and on the login page and with a little fix also for the screen saver. Also, you are still required to type your user name on the login screen.

0) Set up the third party repository (optional but recommended!)

due to this [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 Bug #256429: Carriage-return required after finger scan] you need to press the return key after you swipe your finger with the current version of the kernel and the packages in ubuntu. The bug is caused by the fact that it does not recognize the fingerprint reader 100% correctly ([https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429/comments/29 Description of the root cause]) , as a temporary workaround there is a special package repository.

The packages present in ubuntu intrepid will work but you need to press enter after you swipe your finger.

Click System -> administration -> software sources
go to the tab "third-party software" and click Add ...

Enter in the popup window:

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

Click Add source, it will ask to refresh the package list, click reload.

1) Install the following packages:

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

2) For your user:

{{cmduser| sudo tf-tool --acquire && sudo tf-tool --verify}}

A completed fingerprint setup should look something like this:

frank@Laptop:~$ sudo tf-tool --acquire && sudo tf-tool --verify

ThinkFinger 0.3 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>

Initializing... done.
Please swipe your finger (successful swipes 3/3, failed swipes: 0)... done.
Storing data (/tmp/test.bir)... done.

ThinkFinger 0.3 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>

Initializing... done.
Please swipe your finger (successful swipes 1/1, failed swipes: 0)... done.
Result: Fingerprint does match.
frank@CLaptop:~$

This will store your fingerprint information in /home/$USERNAME/.thinkfinger.bir

You should do this step for each user who wants to use the fingerprint reader

3) Enable use of reader for authentication:

{{cmduser| sudo gedit /etc/pam.d/common-auth}}

add
auth sufficient pam_thinkfinger.so
before the line which contains pam_unix.so and add
try_first_pass
to the end of the line containing pam_unix.so.

So it should look something like this:
...
auth sufficient pam_thinkfinger.so
auth [success=1 default=ignore] pam_unix.so nullok_secure try_first_pass
...

4) Check uinput kernel module:

{{cmduser|lsmod | grep uinput}}
If the output starts with uinput, then you're done.
If you don't get any output, then it needs to be started and set to start on boot.

Start uinput:

{{cmduser|sudo modprobe uinput}}

Start on boot:

{{cmduser|sudo gedit /etc/modules}}

make sure there is a line like this or add it at the bottom:
uinput

5) Enabling thinkfinger for gnome-screensaver

*create this file:
{{cmduser|sudo gedit /etc/udev/rules.d/60-thinkfinger.rules}}
with this contents:
#
# 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/Install_Ubuntu_Intrepid_Ibex_on_a_T61p#Fingerprint_Reader
# which was taken and modified from:
# http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
# 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"

*Make the group:
{{cmduser|sudo groupadd fingerprint}}
*per user:
{{cmduser|sudo gpasswd -a $USERNAME fingerprint && sudo chown $USERNAME:root /home/$USERNAME/.thinkfinger.bir }}

Reboot your laptop and you should be ready to swipe!

Sources:
* [[Install_Ubuntu_Gutsy_Gibbon_on_a_T61p#Fingerprint_Reader| Install Ubuntu Gutsy Gibbon on a T61p]]
* [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 Bug #256429: Carriage-return required after finger scan] & [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429/comments/21 Solution for the bug in the comments]
* [https://launchpad.net/~jon-oberheide/+archive Repository for the third party fix] credits to [https://launchpad.net/~jon-oberheide Jon Oberheide]
* [[How_to_enable_the_fingerprint_reader_with_ThinkFinger| General page about Fingerprint reader with thinkfinger]] & [[How_to_enable_the_fingerprint_reader_with_ThinkFinger#xscreensaver.2Fgnome-screensaver| Specific gnome-screensaver section]]

==Hard Drive Active Protection System (APS ~ HDAPS)==
Please add to this section

Some interesting links:
* [[Active_Protection_System| Description of APS]]
* [[How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS]]
* [[Tp_smapi| tp_smapi kernel modules]]

=Other Problems=

== Resume Requests Network Key ==
On resume Network Manager request the wifi network key several times before connecting to network. This has been noted on a 6459CTO laptop and no known fix is available. Currently with this problem it takes several minutes to regain network access after resume.

== Black Screen on Resume ==
On the 6459CTO with default 8.10 install suspend did not work. Installing the proposed updated fixed the problem. To do this add the following line to /etc/apt/sources.list

deb http://us.archive.ubuntu.com/ubuntu/ intrepid-proposed restricted main universe multiverse

== Wireless not working after resume (Atheros) ==
After resuming from suspend, I am unable to reconnect to my wireless network. Network Manager asks me for my password over and over again but never succeeds in connecting. I'm using the Thinkpad (Atheros) A/B/G wireless card.

To fix this problem, I followed the instructions listed at https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/275692. Specifically, I created a file called /etc/pm/config.d/01-modules and put the following line in it:

SUSPEND_MODULES="ath_pci"

== Brightness control on battery power ==
By default, when unplugging the AC power while the system is running, the brightness of the display goes down even when you have set not to in the Power Management settings and you are not able to reach a brightness level as high as possible when connected to AC power. This is not a software setting or GNOME bug, but a BIOS setting. In the BIOS you can find a brightness setting in the Power section. Set it to high for normal, expected behavior. You can let the GNOME Power Manager still lower the brightness, but you will be able to increase it when needed.

=Software Install=
==Adobe Flash==
Adobe has plug-ins direct for 32 bit version for x64 download the libflashplayer.so file from here:
http://labs.adobe.com/downloads/flashplayer10.html
Then copy to the mozilla plugins directory
sudo cp libflashplayer.so /usr/lib/firefox-addons/plugins/

=Other Information=
== Saving power ==
Some nice information on power saving you can find at

http://www.lesswatts.org

A tool that allows you to test most tips and tricks to reduce power is powertop, you can install it using

{{cmduser|sudo apt-get install powertop}}

and run it with:

{{cmduser|sudo powertop}}

For more information see http://www.lesswatts.org/projects/powertop/
== Battery control by tp_smapi ==
You need to load a kernel module first:
sudo modprobe tp_smapi

Now, you will be able to have significantly more control over your battery charging via /sys/devices/platform/smapi.

For example, you could set a threshold value of 90% for charging, preventing the battery from charging all the way in exchange for a reduction in the loss of battery capacity that occurs after multiple cycles.
echo "90" | sudo tee -a /sys/devices/platform/smapi/BAT0/start_charge_thresh
(by default this was set to 86% on my laptop)

View the number of charge cycles your battery has had in its lifetime:
cat /sys/devices/platform/smapi/BAT0/cycle_count

While AC connected, force discharging of your battery:
echo "1" | sudo tee -a /sys/devices/platform/smapi/BAT0/force_discharge

For convenience, you could load the kernel module at boot time by adding it to /etc/modules.
echo "tp_smapi" | sudo tee -a /etc/modules

If you have an Ultrabay battery, you might want to place this [http://forum.thinkpads.com/viewtopic.php?p=433463#p433463 script] into <code>/etc/crontab</code> to keep the Ultrabay battery from being completely discharged to 0%, which permanently damages the battery.
# rolls to BAT0 when remaining capacity on BAT1 is less than 20%. Change .2 if wanted. Swap BAT0 and BAT1 if tp_smapi thinks the ultrabay is BAT0.
awk '{if (/remaining capacity/) left=$3; if (/last full capacity/) full=$4} END {if ((left/full) < .2) system("echo 1 > /sys/devices/platform/smapi/BAT0/force_discharge")}' /proc/acpi/battery/BAT1/*
Remember the script needs root in order to write to the files in <code>/sys/devices/platform/smapi/BAT{0,1}/</code>.

= Compared to Hardy (8.04) =
Why upgrade your T61p to Intrepid or why not? (Specific for T61p)
== Improvements ==
*Ricoh SD card reader now reads read-only SD card. (Tested with Adata 150X 2GB SD card)
*Newer Wireless LAN drivers. For Intel cards this results in working LED, more sensitive reception, increased stability of connections and some 802.1x bugfixes.
*Out-of-the-box Suspend to RAM functionality (also faster resume). Not on 6459, (see above)
*Working but slow Suspend to Disk functionality.

== Bugs and Regressions ==
*Hard radio killswitch (at the front) cannot bring WLAN back up after killing it. (workaround available)
*X hangs for approx. 35 seconds when restarting or logging out. (workaround available)
*Atheros WLAN not working after resume from Suspend to RAM (but a workaround is available; [[#Wireless_not_working_after_resume_.28Atheros.29|see above]]).

[[Category:T61p]]
[[Category:Ubuntu]]
[[Category:Ubuntu 8.10]]

Install Ubuntu Intrepid Ibex on a T61p

2009-01-18T16:06:55Z

Trampas: /* Adobe Flash */

=What works out of the box?=
*Wireless (Intel 3945ABG or 4965AGN)
**Only tested G mode
*Wired LAN
*Video (VESA)
**Hardware Drivers panel offers to install nVIDIA proprietary drivers on first boot.
*Touchpoint and Trackpad
**Including scroll at the right side of the pad by default.
**Middle-button scrolling does NOT work (fix below)
*Optical drive
**Optiarc AD-7910A works fine with Brasero disc burning
***Tested: CD-R, DVD+R
*Sound card
*SD/MMC Memory card reader (Ricoh)
**Only tested SD (non-HC) cards.
*Control buttons/Hotkeys
**Volume control buttons
**Screen brightness control
**Thinklight control
**WLAN/BT/OFF toggle
**Media player control
**fingerprint reader does NOT work (fix below)
*Some ACPI features
**Battery status, power graphs and history
**Lid states and events
**Only tested with a single 6-cell battery
*ACPI features
** Suspend to RAM
** Suspend to Disk (Hibernate) FINALLY!! Be patient, though.
** STR and STD work even with full disk encryption (DM-crypt + LVM)!

=Getting the hardware to work=
==Display/Video==
Installing the proprietary NVidia drivers is highly recommended, EVEN IF you won't use 3D acceleration, because the open source nv driver will drain your battery much faster since it does not support PowerMizer at all. Practically, this means that the GPU will constantly run at full speed, thus consuming ~12 Watts more than it would otherwise (which is a LOT of power for a laptop).

The first time you boot Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at

System --> Administration --> Hardware Drivers.

You will have a choice between the 173 and 177 version of the driver.
*pro:
**Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not.
*con:
**version 177 causes a log out bug that is addressed below.
**version 177 might show some issues like terminal output not updating in some very weird cases (which I did not see in v173, this seems to have something to do with powermizer as well ...)
**version 180 as of 180.22 is known to have issue with suspend. Stay with version 177 until problem is fixed.

Once the proprietary drivers are installed, the "NVidia X Server Settings" program will be available in System --> Administration.

===Version 177 logout/X restart fix===
There is a known issue in the v177 proprietary NVidia driver - See Launchpad bug [http://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-177/+bug/258357 258357]. Once you install the v177 driver, logging out or restarting X will cease to work, though suspend to RAM/Disk will continue to function.

The work around is as follows:
* In /etc/gdm/gdm.conf , increase the value for GdmXserverTimeout to about 60. When logging out or restarting X, X will hang for ~35 seconds. By increasing the value from its default, GDM will give X more time before it assumes X is faulty.

===Choppy Compiz animations===
NVidia's PowerMizer feature will slow down the GPU when "inactive" even on AC power.

The NVidia driver does not report the correct refresh rate of the display to Compiz, resulting in choppy animations and effects. To fix this, install the <code>compizconfig-settings-manager</code> package, then go to System --> Preferences --> Advanced Desktop Effects Settings (also might be called CompizConfig Settings Manager). Click on General Options, go to the Display Settings tab, uncheck the Detect Refresh rate box and drag the Refresh Rate slider to 60. Also, check the Sync To VBlank box. This will improve the smoothness of the window animations significantly if you're sensitive to the choppy animations.

Compiz animations can also be choppy due to NVidia's PowerMizer feature, which slows down the GPU to conserve power when it is not in use. This works well for 3D games which constantly use 3D acceleration, but poorly for Compiz which uses the GPU in small bursts. It seems that the interval of the PowerMizer is way too long and is not speeding up when using in bursts. Fortunately, the situation seems to have improved in version 177 of the NVidia driver. To workaround this problem, I made a couple of shell scripts which keep the GPU at its highest speed while running on AC power. The first one is named "powermizer-loop" and does most of the work:

#!/bin/sh

while true; do

powerstate=`cat /proc/acpi/ac_adapter/AC/state | awk '{print $2}'`

if [ $powerstate = "on-line" ]; then
nvidia-settings -q all > /dev/null
fi
sleep 25;
done

The second is named "powermizer-off" and starts up powermizer-loop when I log in, ensuring that only one copy runs at a time:

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

I put both of these scripts in my home directory and made them executable by doing:

chmod a+x powermizer-loop powermizer-off

Then to make powermizer-off run on login, I opened System --> Preferences --> Sessions, clicked on Add, and entered the command to run the script, i.e. "/home/<user>/powermizer-off".

Of course, performance still suffers when running on battery, but hopefully NVidia will fix this problem in a future version of their driver.

=== EDID misdetection ===

EDID (Extended Display Identification Data) might be misdetected for your display, which reduces the number of resolutions available in the NVidia X Server Settings application. (For example, I was unable to set my laptop's screen to 1024x768 for use with a projector during a presentation.) If you encounter this problem, add the following lines to /etc/X11/xorg.conf in the "Screen" section:

Option "UseEdidFreqs" "FALSE"
Option "HorizSync" "40-70"

The 40-70 values are just an example. They seem to work well with my 1680x1050 display. You should put the values of your display there. On a 1920x1200 display, making this change prevents the display from coming on when X starts.

A better but more complicated way would be using Phoenix EDID Designer to dump and fix the EDID data and then setup the Nvidia driver so it will use the customized EDID data, as described at [http://myricci.com/index.php?option=com_content&task=view&id=36]

==Microphone/Sound In==
Might need to be turned on in the mixer. See [[Install Ubuntu Hardy Heron on a T61p#Internal Microphone/Microphone Input Jack]]

==Front radio kill switch==
When killing Wireless LAN with the killswitch at the front, you won't be able to get WLAN back up after switching back. See Launchpad bugs [http://bugs.launchpad.net/ubuntu/+source/hal/+bug/289286 289286] and [http://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.24/+bug/193970 193970] and the [https://wiki.ubuntu.com/IntrepidReleaseNotes#Cannot%20reactivate%20Intel%203945/4965%20wireless%20if%20booting%20with%20killswitch%20enabled Release Notes] on the Ubuntu Wiki.

This will be solved in intrepid-updates eventually.

For now there are a few ways to bring the interface back up (choose one):
* Right click the network manager icon in the tray, uncheck Enable Wireless, then check it again does the trick (at least for me)
* {{cmdroot|ip l s wlan0 up}}
* {{cmdroot|modprobe -r iwl3945 && modprobe iwl3945}}
* reboot
* suspend and resume

== Middle-button Scrolling ==
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.

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

{{cmduser| sudo gedit /etc/hal/fdi/policy/mouse-wheel.fdi}}

Paste and save the following code, which will give vertical wheel emulation only:
<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>
There is [http://psung.blogspot.com/2008/09/scrolling-with-thinkpads-trackpoint-in.html another method] to get horizontal scrolling as well, but this is not confirmed to work.

source:
*[[Installing_Ubuntu_8.10_%28Intrepid_Ibex%29_on_a_ThinkPad_T61#Emulate_Wheel_.28Middle-click_scrolling.29| Installing Ubuntu 8.10 (Intrepid Ibex) on a ThinkPad T61 - Emulate Wheel (Middle-click scrolling)]]

==Fingerprint Reader==

The [http://thinkfinger.sourceforge.net Thinkfinger] package allows you to swipe a finger in most places where you would have to type your password. This works with sudo, gksudo and on the login page and with a little fix also for the screen saver. Also, you are still required to type your user name on the login screen.

0) Set up the third party repository (optional but recommended!)

due to this [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 Bug #256429: Carriage-return required after finger scan] you need to press the return key after you swipe your finger with the current version of the kernel and the packages in ubuntu. The bug is caused by the fact that it does not recognize the fingerprint reader 100% correctly ([https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429/comments/29 Description of the root cause]) , as a temporary workaround there is a special package repository.

The packages present in ubuntu intrepid will work but you need to press enter after you swipe your finger.

Click System -> administration -> software sources
go to the tab "third-party software" and click Add ...

Enter in the popup window:

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

Click Add source, it will ask to refresh the package list, click reload.

1) Install the following packages:

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

2) For your user:

{{cmduser| sudo tf-tool --acquire && sudo tf-tool --verify}}

A completed fingerprint setup should look something like this:

frank@Laptop:~$ sudo tf-tool --acquire && sudo tf-tool --verify

ThinkFinger 0.3 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>

Initializing... done.
Please swipe your finger (successful swipes 3/3, failed swipes: 0)... done.
Storing data (/tmp/test.bir)... done.

ThinkFinger 0.3 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>

Initializing... done.
Please swipe your finger (successful swipes 1/1, failed swipes: 0)... done.
Result: Fingerprint does match.
frank@CLaptop:~$

This will store your fingerprint information in /home/$USERNAME/.thinkfinger.bir

You should do this step for each user who wants to use the fingerprint reader

3) Enable use of reader for authentication:

{{cmduser| sudo gedit /etc/pam.d/common-auth}}

add
auth sufficient pam_thinkfinger.so
before the line which contains pam_unix.so and add
try_first_pass
to the end of the line containing pam_unix.so.

So it should look something like this:
...
auth sufficient pam_thinkfinger.so
auth [success=1 default=ignore] pam_unix.so nullok_secure try_first_pass
...

4) Check uinput kernel module:

{{cmduser|lsmod | grep uinput}}
If the output starts with uinput, then you're done.
If you don't get any output, then it needs to be started and set to start on boot.

Start uinput:

{{cmduser|sudo modprobe uinput}}

Start on boot:

{{cmduser|sudo gedit /etc/modules}}

make sure there is a line like this or add it at the bottom:
uinput

5) Enabling thinkfinger for gnome-screensaver

*create this file:
{{cmduser|sudo gedit /etc/udev/rules.d/60-thinkfinger.rules}}
with this contents:
#
# 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/Install_Ubuntu_Intrepid_Ibex_on_a_T61p#Fingerprint_Reader
# which was taken and modified from:
# http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
# 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"

*Make the group:
{{cmduser|sudo groupadd fingerprint}}
*per user:
{{cmduser|sudo gpasswd -a $USERNAME fingerprint && sudo chown $USERNAME:root /home/$USERNAME/.thinkfinger.bir }}

Reboot your laptop and you should be ready to swipe!

Sources:
* [[Install_Ubuntu_Gutsy_Gibbon_on_a_T61p#Fingerprint_Reader| Install Ubuntu Gutsy Gibbon on a T61p]]
* [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 Bug #256429: Carriage-return required after finger scan] & [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429/comments/21 Solution for the bug in the comments]
* [https://launchpad.net/~jon-oberheide/+archive Repository for the third party fix] credits to [https://launchpad.net/~jon-oberheide Jon Oberheide]
* [[How_to_enable_the_fingerprint_reader_with_ThinkFinger| General page about Fingerprint reader with thinkfinger]] & [[How_to_enable_the_fingerprint_reader_with_ThinkFinger#xscreensaver.2Fgnome-screensaver| Specific gnome-screensaver section]]

==Hard Drive Active Protection System (APS ~ HDAPS)==
Please add to this section

Some interesting links:
* [[Active_Protection_System| Description of APS]]
* [[How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS]]
* [[Tp_smapi| tp_smapi kernel modules]]

=Other Problems=

== Resume Requests Network Key ==
On resume Network Manager request the wifi network key several times before connecting to network. This has been noted on a 6459CTO laptop and no known fix is available. Currently with this problem it takes several minutes to regain network access after resume.

== Black Screen on Resume ==
On the 6459CTO with default 8.10 install suspend did not work. Installing the proposed updated fixed the problem. To do this add the following line to /etc/apt/sources.list

deb http://us.archive.ubuntu.com/ubuntu/ intrepid-proposed restricted main universe multiverse

== Wireless not working after resume (Atheros) ==
After resuming from suspend, I am unable to reconnect to my wireless network. Network Manager asks me for my password over and over again but never succeeds in connecting. I'm using the Thinkpad (Atheros) A/B/G wireless card.

To fix this problem, I followed the instructions listed at https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/275692. Specifically, I created a file called /etc/pm/config.d/01-modules and put the following line in it:

SUSPEND_MODULES="ath_pci"

== Brightness control on battery power ==
By default, when unplugging the AC power while the system is running, the brightness of the display goes down even when you have set not to in the Power Management settings and you are not able to reach a brightness level as high as possible when connected to AC power. This is not a software setting or GNOME bug, but a BIOS setting. In the BIOS you can find a brightness setting in the Power section. Set it to high for normal, expected behavior. You can let the GNOME Power Manager still lower the brightness, but you will be able to increase it when needed.

=Software Install=
==Adobe Flash==
Adobe has plug-ins direct for 32 bit version for x64 download the libflashplayer.so file from here:
http://labs.adobe.com/downloads/flashplayer10.html
Then copy to the mozilla plugins directory

{{cmduser|sudo cp libflashplayer.so /usr/lib/firefox-addons/plugins/}}

=Other Information=
== Saving power ==
Some nice information on power saving you can find at

http://www.lesswatts.org

A tool that allows you to test most tips and tricks to reduce power is powertop, you can install it using

{{cmduser|sudo apt-get install powertop}}

and run it with:

{{cmduser|sudo powertop}}

For more information see http://www.lesswatts.org/projects/powertop/
== Battery control by tp_smapi ==
You need to load a kernel module first:
sudo modprobe tp_smapi

Now, you will be able to have significantly more control over your battery charging via /sys/devices/platform/smapi.

For example, you could set a threshold value of 90% for charging, preventing the battery from charging all the way in exchange for a reduction in the loss of battery capacity that occurs after multiple cycles.
echo "90" | sudo tee -a /sys/devices/platform/smapi/BAT0/start_charge_thresh
(by default this was set to 86% on my laptop)

View the number of charge cycles your battery has had in its lifetime:
cat /sys/devices/platform/smapi/BAT0/cycle_count

While AC connected, force discharging of your battery:
echo "1" | sudo tee -a /sys/devices/platform/smapi/BAT0/force_discharge

For convenience, you could load the kernel module at boot time by adding it to /etc/modules.
echo "tp_smapi" | sudo tee -a /etc/modules

If you have an Ultrabay battery, you might want to place this [http://forum.thinkpads.com/viewtopic.php?p=433463#p433463 script] into <code>/etc/crontab</code> to keep the Ultrabay battery from being completely discharged to 0%, which permanently damages the battery.
# rolls to BAT0 when remaining capacity on BAT1 is less than 20%. Change .2 if wanted. Swap BAT0 and BAT1 if tp_smapi thinks the ultrabay is BAT0.
awk '{if (/remaining capacity/) left=$3; if (/last full capacity/) full=$4} END {if ((left/full) < .2) system("echo 1 > /sys/devices/platform/smapi/BAT0/force_discharge")}' /proc/acpi/battery/BAT1/*
Remember the script needs root in order to write to the files in <code>/sys/devices/platform/smapi/BAT{0,1}/</code>.

= Compared to Hardy (8.04) =
Why upgrade your T61p to Intrepid or why not? (Specific for T61p)
== Improvements ==
*Ricoh SD card reader now reads read-only SD card. (Tested with Adata 150X 2GB SD card)
*Newer Wireless LAN drivers. For Intel cards this results in working LED, more sensitive reception, increased stability of connections and some 802.1x bugfixes.
*Out-of-the-box Suspend to RAM functionality (also faster resume). Not on 6459, (see above)
*Working but slow Suspend to Disk functionality.

== Bugs and Regressions ==
*Hard radio killswitch (at the front) cannot bring WLAN back up after killing it. (workaround available)
*X hangs for approx. 35 seconds when restarting or logging out. (workaround available)
*Atheros WLAN not working after resume from Suspend to RAM (but a workaround is available; [[#Wireless_not_working_after_resume_.28Atheros.29|see above]]).

[[Category:T61p]]
[[Category:Ubuntu]]
[[Category:Ubuntu 8.10]]

Install Ubuntu Intrepid Ibex on a T61p

2009-01-18T16:06:03Z

Trampas: /* Other Information */

=What works out of the box?=
*Wireless (Intel 3945ABG or 4965AGN)
**Only tested G mode
*Wired LAN
*Video (VESA)
**Hardware Drivers panel offers to install nVIDIA proprietary drivers on first boot.
*Touchpoint and Trackpad
**Including scroll at the right side of the pad by default.
**Middle-button scrolling does NOT work (fix below)
*Optical drive
**Optiarc AD-7910A works fine with Brasero disc burning
***Tested: CD-R, DVD+R
*Sound card
*SD/MMC Memory card reader (Ricoh)
**Only tested SD (non-HC) cards.
*Control buttons/Hotkeys
**Volume control buttons
**Screen brightness control
**Thinklight control
**WLAN/BT/OFF toggle
**Media player control
**fingerprint reader does NOT work (fix below)
*Some ACPI features
**Battery status, power graphs and history
**Lid states and events
**Only tested with a single 6-cell battery
*ACPI features
** Suspend to RAM
** Suspend to Disk (Hibernate) FINALLY!! Be patient, though.
** STR and STD work even with full disk encryption (DM-crypt + LVM)!

=Getting the hardware to work=
==Display/Video==
Installing the proprietary NVidia drivers is highly recommended, EVEN IF you won't use 3D acceleration, because the open source nv driver will drain your battery much faster since it does not support PowerMizer at all. Practically, this means that the GPU will constantly run at full speed, thus consuming ~12 Watts more than it would otherwise (which is a LOT of power for a laptop).

The first time you boot Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at

System --> Administration --> Hardware Drivers.

You will have a choice between the 173 and 177 version of the driver.
*pro:
**Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not.
*con:
**version 177 causes a log out bug that is addressed below.
**version 177 might show some issues like terminal output not updating in some very weird cases (which I did not see in v173, this seems to have something to do with powermizer as well ...)
**version 180 as of 180.22 is known to have issue with suspend. Stay with version 177 until problem is fixed.

Once the proprietary drivers are installed, the "NVidia X Server Settings" program will be available in System --> Administration.

===Version 177 logout/X restart fix===
There is a known issue in the v177 proprietary NVidia driver - See Launchpad bug [http://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-177/+bug/258357 258357]. Once you install the v177 driver, logging out or restarting X will cease to work, though suspend to RAM/Disk will continue to function.

The work around is as follows:
* In /etc/gdm/gdm.conf , increase the value for GdmXserverTimeout to about 60. When logging out or restarting X, X will hang for ~35 seconds. By increasing the value from its default, GDM will give X more time before it assumes X is faulty.

===Choppy Compiz animations===
NVidia's PowerMizer feature will slow down the GPU when "inactive" even on AC power.

The NVidia driver does not report the correct refresh rate of the display to Compiz, resulting in choppy animations and effects. To fix this, install the <code>compizconfig-settings-manager</code> package, then go to System --> Preferences --> Advanced Desktop Effects Settings (also might be called CompizConfig Settings Manager). Click on General Options, go to the Display Settings tab, uncheck the Detect Refresh rate box and drag the Refresh Rate slider to 60. Also, check the Sync To VBlank box. This will improve the smoothness of the window animations significantly if you're sensitive to the choppy animations.

Compiz animations can also be choppy due to NVidia's PowerMizer feature, which slows down the GPU to conserve power when it is not in use. This works well for 3D games which constantly use 3D acceleration, but poorly for Compiz which uses the GPU in small bursts. It seems that the interval of the PowerMizer is way too long and is not speeding up when using in bursts. Fortunately, the situation seems to have improved in version 177 of the NVidia driver. To workaround this problem, I made a couple of shell scripts which keep the GPU at its highest speed while running on AC power. The first one is named "powermizer-loop" and does most of the work:

#!/bin/sh

while true; do

powerstate=`cat /proc/acpi/ac_adapter/AC/state | awk '{print $2}'`

if [ $powerstate = "on-line" ]; then
nvidia-settings -q all > /dev/null
fi
sleep 25;
done

The second is named "powermizer-off" and starts up powermizer-loop when I log in, ensuring that only one copy runs at a time:

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

I put both of these scripts in my home directory and made them executable by doing:

chmod a+x powermizer-loop powermizer-off

Then to make powermizer-off run on login, I opened System --> Preferences --> Sessions, clicked on Add, and entered the command to run the script, i.e. "/home/<user>/powermizer-off".

Of course, performance still suffers when running on battery, but hopefully NVidia will fix this problem in a future version of their driver.

=== EDID misdetection ===

EDID (Extended Display Identification Data) might be misdetected for your display, which reduces the number of resolutions available in the NVidia X Server Settings application. (For example, I was unable to set my laptop's screen to 1024x768 for use with a projector during a presentation.) If you encounter this problem, add the following lines to /etc/X11/xorg.conf in the "Screen" section:

Option "UseEdidFreqs" "FALSE"
Option "HorizSync" "40-70"

The 40-70 values are just an example. They seem to work well with my 1680x1050 display. You should put the values of your display there. On a 1920x1200 display, making this change prevents the display from coming on when X starts.

A better but more complicated way would be using Phoenix EDID Designer to dump and fix the EDID data and then setup the Nvidia driver so it will use the customized EDID data, as described at [http://myricci.com/index.php?option=com_content&task=view&id=36]

==Microphone/Sound In==
Might need to be turned on in the mixer. See [[Install Ubuntu Hardy Heron on a T61p#Internal Microphone/Microphone Input Jack]]

==Front radio kill switch==
When killing Wireless LAN with the killswitch at the front, you won't be able to get WLAN back up after switching back. See Launchpad bugs [http://bugs.launchpad.net/ubuntu/+source/hal/+bug/289286 289286] and [http://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.24/+bug/193970 193970] and the [https://wiki.ubuntu.com/IntrepidReleaseNotes#Cannot%20reactivate%20Intel%203945/4965%20wireless%20if%20booting%20with%20killswitch%20enabled Release Notes] on the Ubuntu Wiki.

This will be solved in intrepid-updates eventually.

For now there are a few ways to bring the interface back up (choose one):
* Right click the network manager icon in the tray, uncheck Enable Wireless, then check it again does the trick (at least for me)
* {{cmdroot|ip l s wlan0 up}}
* {{cmdroot|modprobe -r iwl3945 && modprobe iwl3945}}
* reboot
* suspend and resume

== Middle-button Scrolling ==
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.

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

{{cmduser| sudo gedit /etc/hal/fdi/policy/mouse-wheel.fdi}}

Paste and save the following code, which will give vertical wheel emulation only:
<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>
There is [http://psung.blogspot.com/2008/09/scrolling-with-thinkpads-trackpoint-in.html another method] to get horizontal scrolling as well, but this is not confirmed to work.

source:
*[[Installing_Ubuntu_8.10_%28Intrepid_Ibex%29_on_a_ThinkPad_T61#Emulate_Wheel_.28Middle-click_scrolling.29| Installing Ubuntu 8.10 (Intrepid Ibex) on a ThinkPad T61 - Emulate Wheel (Middle-click scrolling)]]

==Fingerprint Reader==

The [http://thinkfinger.sourceforge.net Thinkfinger] package allows you to swipe a finger in most places where you would have to type your password. This works with sudo, gksudo and on the login page and with a little fix also for the screen saver. Also, you are still required to type your user name on the login screen.

0) Set up the third party repository (optional but recommended!)

due to this [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 Bug #256429: Carriage-return required after finger scan] you need to press the return key after you swipe your finger with the current version of the kernel and the packages in ubuntu. The bug is caused by the fact that it does not recognize the fingerprint reader 100% correctly ([https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429/comments/29 Description of the root cause]) , as a temporary workaround there is a special package repository.

The packages present in ubuntu intrepid will work but you need to press enter after you swipe your finger.

Click System -> administration -> software sources
go to the tab "third-party software" and click Add ...

Enter in the popup window:

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

Click Add source, it will ask to refresh the package list, click reload.

1) Install the following packages:

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

2) For your user:

{{cmduser| sudo tf-tool --acquire && sudo tf-tool --verify}}

A completed fingerprint setup should look something like this:

frank@Laptop:~$ sudo tf-tool --acquire && sudo tf-tool --verify

ThinkFinger 0.3 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>

Initializing... done.
Please swipe your finger (successful swipes 3/3, failed swipes: 0)... done.
Storing data (/tmp/test.bir)... done.

ThinkFinger 0.3 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>

Initializing... done.
Please swipe your finger (successful swipes 1/1, failed swipes: 0)... done.
Result: Fingerprint does match.
frank@CLaptop:~$

This will store your fingerprint information in /home/$USERNAME/.thinkfinger.bir

You should do this step for each user who wants to use the fingerprint reader

3) Enable use of reader for authentication:

{{cmduser| sudo gedit /etc/pam.d/common-auth}}

add
auth sufficient pam_thinkfinger.so
before the line which contains pam_unix.so and add
try_first_pass
to the end of the line containing pam_unix.so.

So it should look something like this:
...
auth sufficient pam_thinkfinger.so
auth [success=1 default=ignore] pam_unix.so nullok_secure try_first_pass
...

4) Check uinput kernel module:

{{cmduser|lsmod | grep uinput}}
If the output starts with uinput, then you're done.
If you don't get any output, then it needs to be started and set to start on boot.

Start uinput:

{{cmduser|sudo modprobe uinput}}

Start on boot:

{{cmduser|sudo gedit /etc/modules}}

make sure there is a line like this or add it at the bottom:
uinput

5) Enabling thinkfinger for gnome-screensaver

*create this file:
{{cmduser|sudo gedit /etc/udev/rules.d/60-thinkfinger.rules}}
with this contents:
#
# 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/Install_Ubuntu_Intrepid_Ibex_on_a_T61p#Fingerprint_Reader
# which was taken and modified from:
# http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
# 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"

*Make the group:
{{cmduser|sudo groupadd fingerprint}}
*per user:
{{cmduser|sudo gpasswd -a $USERNAME fingerprint && sudo chown $USERNAME:root /home/$USERNAME/.thinkfinger.bir }}

Reboot your laptop and you should be ready to swipe!

Sources:
* [[Install_Ubuntu_Gutsy_Gibbon_on_a_T61p#Fingerprint_Reader| Install Ubuntu Gutsy Gibbon on a T61p]]
* [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 Bug #256429: Carriage-return required after finger scan] & [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429/comments/21 Solution for the bug in the comments]
* [https://launchpad.net/~jon-oberheide/+archive Repository for the third party fix] credits to [https://launchpad.net/~jon-oberheide Jon Oberheide]
* [[How_to_enable_the_fingerprint_reader_with_ThinkFinger| General page about Fingerprint reader with thinkfinger]] & [[How_to_enable_the_fingerprint_reader_with_ThinkFinger#xscreensaver.2Fgnome-screensaver| Specific gnome-screensaver section]]

==Hard Drive Active Protection System (APS ~ HDAPS)==
Please add to this section

Some interesting links:
* [[Active_Protection_System| Description of APS]]
* [[How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS]]
* [[Tp_smapi| tp_smapi kernel modules]]

=Other Problems=

== Resume Requests Network Key ==
On resume Network Manager request the wifi network key several times before connecting to network. This has been noted on a 6459CTO laptop and no known fix is available. Currently with this problem it takes several minutes to regain network access after resume.

== Black Screen on Resume ==
On the 6459CTO with default 8.10 install suspend did not work. Installing the proposed updated fixed the problem. To do this add the following line to /etc/apt/sources.list

deb http://us.archive.ubuntu.com/ubuntu/ intrepid-proposed restricted main universe multiverse

== Wireless not working after resume (Atheros) ==
After resuming from suspend, I am unable to reconnect to my wireless network. Network Manager asks me for my password over and over again but never succeeds in connecting. I'm using the Thinkpad (Atheros) A/B/G wireless card.

To fix this problem, I followed the instructions listed at https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/275692. Specifically, I created a file called /etc/pm/config.d/01-modules and put the following line in it:

SUSPEND_MODULES="ath_pci"

== Brightness control on battery power ==
By default, when unplugging the AC power while the system is running, the brightness of the display goes down even when you have set not to in the Power Management settings and you are not able to reach a brightness level as high as possible when connected to AC power. This is not a software setting or GNOME bug, but a BIOS setting. In the BIOS you can find a brightness setting in the Power section. Set it to high for normal, expected behavior. You can let the GNOME Power Manager still lower the brightness, but you will be able to increase it when needed.

=Software Install=
==Adobe Flash==
Adobe has plug-ins direct for 32 bit version for x64 download the libflashplayer.so file from here:
http://labs.adobe.com/downloads/flashplayer10.html
Then copy to the mozilla plugins directory

sudo cp libflashplayer.so /usr/lib/firefox-addons/plugins/

=Other Information=
== Saving power ==
Some nice information on power saving you can find at

http://www.lesswatts.org

A tool that allows you to test most tips and tricks to reduce power is powertop, you can install it using

{{cmduser|sudo apt-get install powertop}}

and run it with:

{{cmduser|sudo powertop}}

For more information see http://www.lesswatts.org/projects/powertop/
== Battery control by tp_smapi ==
You need to load a kernel module first:
sudo modprobe tp_smapi

Now, you will be able to have significantly more control over your battery charging via /sys/devices/platform/smapi.

For example, you could set a threshold value of 90% for charging, preventing the battery from charging all the way in exchange for a reduction in the loss of battery capacity that occurs after multiple cycles.
echo "90" | sudo tee -a /sys/devices/platform/smapi/BAT0/start_charge_thresh
(by default this was set to 86% on my laptop)

View the number of charge cycles your battery has had in its lifetime:
cat /sys/devices/platform/smapi/BAT0/cycle_count

While AC connected, force discharging of your battery:
echo "1" | sudo tee -a /sys/devices/platform/smapi/BAT0/force_discharge

For convenience, you could load the kernel module at boot time by adding it to /etc/modules.
echo "tp_smapi" | sudo tee -a /etc/modules

If you have an Ultrabay battery, you might want to place this [http://forum.thinkpads.com/viewtopic.php?p=433463#p433463 script] into <code>/etc/crontab</code> to keep the Ultrabay battery from being completely discharged to 0%, which permanently damages the battery.
# rolls to BAT0 when remaining capacity on BAT1 is less than 20%. Change .2 if wanted. Swap BAT0 and BAT1 if tp_smapi thinks the ultrabay is BAT0.
awk '{if (/remaining capacity/) left=$3; if (/last full capacity/) full=$4} END {if ((left/full) < .2) system("echo 1 > /sys/devices/platform/smapi/BAT0/force_discharge")}' /proc/acpi/battery/BAT1/*
Remember the script needs root in order to write to the files in <code>/sys/devices/platform/smapi/BAT{0,1}/</code>.

= Compared to Hardy (8.04) =
Why upgrade your T61p to Intrepid or why not? (Specific for T61p)
== Improvements ==
*Ricoh SD card reader now reads read-only SD card. (Tested with Adata 150X 2GB SD card)
*Newer Wireless LAN drivers. For Intel cards this results in working LED, more sensitive reception, increased stability of connections and some 802.1x bugfixes.
*Out-of-the-box Suspend to RAM functionality (also faster resume). Not on 6459, (see above)
*Working but slow Suspend to Disk functionality.

== Bugs and Regressions ==
*Hard radio killswitch (at the front) cannot bring WLAN back up after killing it. (workaround available)
*X hangs for approx. 35 seconds when restarting or logging out. (workaround available)
*Atheros WLAN not working after resume from Suspend to RAM (but a workaround is available; [[#Wireless_not_working_after_resume_.28Atheros.29|see above]]).

[[Category:T61p]]
[[Category:Ubuntu]]
[[Category:Ubuntu 8.10]]

Install Ubuntu Intrepid Ibex on a T61p

2009-01-18T16:00:40Z

Trampas: /* Improvements */

=What works out of the box?=
*Wireless (Intel 3945ABG or 4965AGN)
**Only tested G mode
*Wired LAN
*Video (VESA)
**Hardware Drivers panel offers to install nVIDIA proprietary drivers on first boot.
*Touchpoint and Trackpad
**Including scroll at the right side of the pad by default.
**Middle-button scrolling does NOT work (fix below)
*Optical drive
**Optiarc AD-7910A works fine with Brasero disc burning
***Tested: CD-R, DVD+R
*Sound card
*SD/MMC Memory card reader (Ricoh)
**Only tested SD (non-HC) cards.
*Control buttons/Hotkeys
**Volume control buttons
**Screen brightness control
**Thinklight control
**WLAN/BT/OFF toggle
**Media player control
**fingerprint reader does NOT work (fix below)
*Some ACPI features
**Battery status, power graphs and history
**Lid states and events
**Only tested with a single 6-cell battery
*ACPI features
** Suspend to RAM
** Suspend to Disk (Hibernate) FINALLY!! Be patient, though.
** STR and STD work even with full disk encryption (DM-crypt + LVM)!

=Getting the hardware to work=
==Display/Video==
Installing the proprietary NVidia drivers is highly recommended, EVEN IF you won't use 3D acceleration, because the open source nv driver will drain your battery much faster since it does not support PowerMizer at all. Practically, this means that the GPU will constantly run at full speed, thus consuming ~12 Watts more than it would otherwise (which is a LOT of power for a laptop).

The first time you boot Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at

System --> Administration --> Hardware Drivers.

You will have a choice between the 173 and 177 version of the driver.
*pro:
**Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not.
*con:
**version 177 causes a log out bug that is addressed below.
**version 177 might show some issues like terminal output not updating in some very weird cases (which I did not see in v173, this seems to have something to do with powermizer as well ...)
**version 180 as of 180.22 is known to have issue with suspend. Stay with version 177 until problem is fixed.

Once the proprietary drivers are installed, the "NVidia X Server Settings" program will be available in System --> Administration.

===Version 177 logout/X restart fix===
There is a known issue in the v177 proprietary NVidia driver - See Launchpad bug [http://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-177/+bug/258357 258357]. Once you install the v177 driver, logging out or restarting X will cease to work, though suspend to RAM/Disk will continue to function.

The work around is as follows:
* In /etc/gdm/gdm.conf , increase the value for GdmXserverTimeout to about 60. When logging out or restarting X, X will hang for ~35 seconds. By increasing the value from its default, GDM will give X more time before it assumes X is faulty.

===Choppy Compiz animations===
NVidia's PowerMizer feature will slow down the GPU when "inactive" even on AC power.

The NVidia driver does not report the correct refresh rate of the display to Compiz, resulting in choppy animations and effects. To fix this, install the <code>compizconfig-settings-manager</code> package, then go to System --> Preferences --> Advanced Desktop Effects Settings (also might be called CompizConfig Settings Manager). Click on General Options, go to the Display Settings tab, uncheck the Detect Refresh rate box and drag the Refresh Rate slider to 60. Also, check the Sync To VBlank box. This will improve the smoothness of the window animations significantly if you're sensitive to the choppy animations.

Compiz animations can also be choppy due to NVidia's PowerMizer feature, which slows down the GPU to conserve power when it is not in use. This works well for 3D games which constantly use 3D acceleration, but poorly for Compiz which uses the GPU in small bursts. It seems that the interval of the PowerMizer is way too long and is not speeding up when using in bursts. Fortunately, the situation seems to have improved in version 177 of the NVidia driver. To workaround this problem, I made a couple of shell scripts which keep the GPU at its highest speed while running on AC power. The first one is named "powermizer-loop" and does most of the work:

#!/bin/sh

while true; do

powerstate=`cat /proc/acpi/ac_adapter/AC/state | awk '{print $2}'`

if [ $powerstate = "on-line" ]; then
nvidia-settings -q all > /dev/null
fi
sleep 25;
done

The second is named "powermizer-off" and starts up powermizer-loop when I log in, ensuring that only one copy runs at a time:

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

I put both of these scripts in my home directory and made them executable by doing:

chmod a+x powermizer-loop powermizer-off

Then to make powermizer-off run on login, I opened System --> Preferences --> Sessions, clicked on Add, and entered the command to run the script, i.e. "/home/<user>/powermizer-off".

Of course, performance still suffers when running on battery, but hopefully NVidia will fix this problem in a future version of their driver.

=== EDID misdetection ===

EDID (Extended Display Identification Data) might be misdetected for your display, which reduces the number of resolutions available in the NVidia X Server Settings application. (For example, I was unable to set my laptop's screen to 1024x768 for use with a projector during a presentation.) If you encounter this problem, add the following lines to /etc/X11/xorg.conf in the "Screen" section:

Option "UseEdidFreqs" "FALSE"
Option "HorizSync" "40-70"

The 40-70 values are just an example. They seem to work well with my 1680x1050 display. You should put the values of your display there. On a 1920x1200 display, making this change prevents the display from coming on when X starts.

A better but more complicated way would be using Phoenix EDID Designer to dump and fix the EDID data and then setup the Nvidia driver so it will use the customized EDID data, as described at [http://myricci.com/index.php?option=com_content&task=view&id=36]

==Microphone/Sound In==
Might need to be turned on in the mixer. See [[Install Ubuntu Hardy Heron on a T61p#Internal Microphone/Microphone Input Jack]]

==Front radio kill switch==
When killing Wireless LAN with the killswitch at the front, you won't be able to get WLAN back up after switching back. See Launchpad bugs [http://bugs.launchpad.net/ubuntu/+source/hal/+bug/289286 289286] and [http://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.24/+bug/193970 193970] and the [https://wiki.ubuntu.com/IntrepidReleaseNotes#Cannot%20reactivate%20Intel%203945/4965%20wireless%20if%20booting%20with%20killswitch%20enabled Release Notes] on the Ubuntu Wiki.

This will be solved in intrepid-updates eventually.

For now there are a few ways to bring the interface back up (choose one):
* Right click the network manager icon in the tray, uncheck Enable Wireless, then check it again does the trick (at least for me)
* {{cmdroot|ip l s wlan0 up}}
* {{cmdroot|modprobe -r iwl3945 && modprobe iwl3945}}
* reboot
* suspend and resume

== Middle-button Scrolling ==
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.

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

{{cmduser| sudo gedit /etc/hal/fdi/policy/mouse-wheel.fdi}}

Paste and save the following code, which will give vertical wheel emulation only:
<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>
There is [http://psung.blogspot.com/2008/09/scrolling-with-thinkpads-trackpoint-in.html another method] to get horizontal scrolling as well, but this is not confirmed to work.

source:
*[[Installing_Ubuntu_8.10_%28Intrepid_Ibex%29_on_a_ThinkPad_T61#Emulate_Wheel_.28Middle-click_scrolling.29| Installing Ubuntu 8.10 (Intrepid Ibex) on a ThinkPad T61 - Emulate Wheel (Middle-click scrolling)]]

==Fingerprint Reader==

The [http://thinkfinger.sourceforge.net Thinkfinger] package allows you to swipe a finger in most places where you would have to type your password. This works with sudo, gksudo and on the login page and with a little fix also for the screen saver. Also, you are still required to type your user name on the login screen.

0) Set up the third party repository (optional but recommended!)

due to this [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 Bug #256429: Carriage-return required after finger scan] you need to press the return key after you swipe your finger with the current version of the kernel and the packages in ubuntu. The bug is caused by the fact that it does not recognize the fingerprint reader 100% correctly ([https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429/comments/29 Description of the root cause]) , as a temporary workaround there is a special package repository.

The packages present in ubuntu intrepid will work but you need to press enter after you swipe your finger.

Click System -> administration -> software sources
go to the tab "third-party software" and click Add ...

Enter in the popup window:

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

Click Add source, it will ask to refresh the package list, click reload.

1) Install the following packages:

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

2) For your user:

{{cmduser| sudo tf-tool --acquire && sudo tf-tool --verify}}

A completed fingerprint setup should look something like this:

frank@Laptop:~$ sudo tf-tool --acquire && sudo tf-tool --verify

ThinkFinger 0.3 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>

Initializing... done.
Please swipe your finger (successful swipes 3/3, failed swipes: 0)... done.
Storing data (/tmp/test.bir)... done.

ThinkFinger 0.3 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>

Initializing... done.
Please swipe your finger (successful swipes 1/1, failed swipes: 0)... done.
Result: Fingerprint does match.
frank@CLaptop:~$

This will store your fingerprint information in /home/$USERNAME/.thinkfinger.bir

You should do this step for each user who wants to use the fingerprint reader

3) Enable use of reader for authentication:

{{cmduser| sudo gedit /etc/pam.d/common-auth}}

add
auth sufficient pam_thinkfinger.so
before the line which contains pam_unix.so and add
try_first_pass
to the end of the line containing pam_unix.so.

So it should look something like this:
...
auth sufficient pam_thinkfinger.so
auth [success=1 default=ignore] pam_unix.so nullok_secure try_first_pass
...

4) Check uinput kernel module:

{{cmduser|lsmod | grep uinput}}
If the output starts with uinput, then you're done.
If you don't get any output, then it needs to be started and set to start on boot.

Start uinput:

{{cmduser|sudo modprobe uinput}}

Start on boot:

{{cmduser|sudo gedit /etc/modules}}

make sure there is a line like this or add it at the bottom:
uinput

5) Enabling thinkfinger for gnome-screensaver

*create this file:
{{cmduser|sudo gedit /etc/udev/rules.d/60-thinkfinger.rules}}
with this contents:
#
# 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/Install_Ubuntu_Intrepid_Ibex_on_a_T61p#Fingerprint_Reader
# which was taken and modified from:
# http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
# 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"

*Make the group:
{{cmduser|sudo groupadd fingerprint}}
*per user:
{{cmduser|sudo gpasswd -a $USERNAME fingerprint && sudo chown $USERNAME:root /home/$USERNAME/.thinkfinger.bir }}

Reboot your laptop and you should be ready to swipe!

Sources:
* [[Install_Ubuntu_Gutsy_Gibbon_on_a_T61p#Fingerprint_Reader| Install Ubuntu Gutsy Gibbon on a T61p]]
* [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 Bug #256429: Carriage-return required after finger scan] & [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429/comments/21 Solution for the bug in the comments]
* [https://launchpad.net/~jon-oberheide/+archive Repository for the third party fix] credits to [https://launchpad.net/~jon-oberheide Jon Oberheide]
* [[How_to_enable_the_fingerprint_reader_with_ThinkFinger| General page about Fingerprint reader with thinkfinger]] & [[How_to_enable_the_fingerprint_reader_with_ThinkFinger#xscreensaver.2Fgnome-screensaver| Specific gnome-screensaver section]]

==Hard Drive Active Protection System (APS ~ HDAPS)==
Please add to this section

Some interesting links:
* [[Active_Protection_System| Description of APS]]
* [[How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS]]
* [[Tp_smapi| tp_smapi kernel modules]]

=Other Problems=

== Resume Requests Network Key ==
On resume Network Manager request the wifi network key several times before connecting to network. This has been noted on a 6459CTO laptop and no known fix is available. Currently with this problem it takes several minutes to regain network access after resume.

== Black Screen on Resume ==
On the 6459CTO with default 8.10 install suspend did not work. Installing the proposed updated fixed the problem. To do this add the following line to /etc/apt/sources.list

deb http://us.archive.ubuntu.com/ubuntu/ intrepid-proposed restricted main universe multiverse

== Wireless not working after resume (Atheros) ==
After resuming from suspend, I am unable to reconnect to my wireless network. Network Manager asks me for my password over and over again but never succeeds in connecting. I'm using the Thinkpad (Atheros) A/B/G wireless card.

To fix this problem, I followed the instructions listed at https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/275692. Specifically, I created a file called /etc/pm/config.d/01-modules and put the following line in it:

SUSPEND_MODULES="ath_pci"

== Brightness control on battery power ==
By default, when unplugging the AC power while the system is running, the brightness of the display goes down even when you have set not to in the Power Management settings and you are not able to reach a brightness level as high as possible when connected to AC power. This is not a software setting or GNOME bug, but a BIOS setting. In the BIOS you can find a brightness setting in the Power section. Set it to high for normal, expected behavior. You can let the GNOME Power Manager still lower the brightness, but you will be able to increase it when needed.

=Other Information=
== Saving power ==
Some nice information on power saving you can find at

http://www.lesswatts.org

A tool that allows you to test most tips and tricks to reduce power is powertop, you can install it using

{{cmduser|sudo apt-get install powertop}}

and run it with:

{{cmduser|sudo powertop}}

For more information see http://www.lesswatts.org/projects/powertop/
== Battery control by tp_smapi ==
You need to load a kernel module first:
sudo modprobe tp_smapi

Now, you will be able to have significantly more control over your battery charging via /sys/devices/platform/smapi.

For example, you could set a threshold value of 90% for charging, preventing the battery from charging all the way in exchange for a reduction in the loss of battery capacity that occurs after multiple cycles.
echo "90" | sudo tee -a /sys/devices/platform/smapi/BAT0/start_charge_thresh
(by default this was set to 86% on my laptop)

View the number of charge cycles your battery has had in its lifetime:
cat /sys/devices/platform/smapi/BAT0/cycle_count

While AC connected, force discharging of your battery:
echo "1" | sudo tee -a /sys/devices/platform/smapi/BAT0/force_discharge

For convenience, you could load the kernel module at boot time by adding it to /etc/modules.
echo "tp_smapi" | sudo tee -a /etc/modules

If you have an Ultrabay battery, you might want to place this [http://forum.thinkpads.com/viewtopic.php?p=433463#p433463 script] into <code>/etc/crontab</code> to keep the Ultrabay battery from being completely discharged to 0%, which permanently damages the battery.
# rolls to BAT0 when remaining capacity on BAT1 is less than 20%. Change .2 if wanted. Swap BAT0 and BAT1 if tp_smapi thinks the ultrabay is BAT0.
awk '{if (/remaining capacity/) left=$3; if (/last full capacity/) full=$4} END {if ((left/full) < .2) system("echo 1 > /sys/devices/platform/smapi/BAT0/force_discharge")}' /proc/acpi/battery/BAT1/*
Remember the script needs root in order to write to the files in <code>/sys/devices/platform/smapi/BAT{0,1}/</code>.

= Compared to Hardy (8.04) =
Why upgrade your T61p to Intrepid or why not? (Specific for T61p)
== Improvements ==
*Ricoh SD card reader now reads read-only SD card. (Tested with Adata 150X 2GB SD card)
*Newer Wireless LAN drivers. For Intel cards this results in working LED, more sensitive reception, increased stability of connections and some 802.1x bugfixes.
*Out-of-the-box Suspend to RAM functionality (also faster resume). Not on 6459, (see above)
*Working but slow Suspend to Disk functionality.

== Bugs and Regressions ==
*Hard radio killswitch (at the front) cannot bring WLAN back up after killing it. (workaround available)
*X hangs for approx. 35 seconds when restarting or logging out. (workaround available)
*Atheros WLAN not working after resume from Suspend to RAM (but a workaround is available; [[#Wireless_not_working_after_resume_.28Atheros.29|see above]]).

[[Category:T61p]]
[[Category:Ubuntu]]
[[Category:Ubuntu 8.10]]

Install Ubuntu Intrepid Ibex on a T61p

2009-01-18T15:57:41Z

Trampas: /* Other Problems */

=What works out of the box?=
*Wireless (Intel 3945ABG or 4965AGN)
**Only tested G mode
*Wired LAN
*Video (VESA)
**Hardware Drivers panel offers to install nVIDIA proprietary drivers on first boot.
*Touchpoint and Trackpad
**Including scroll at the right side of the pad by default.
**Middle-button scrolling does NOT work (fix below)
*Optical drive
**Optiarc AD-7910A works fine with Brasero disc burning
***Tested: CD-R, DVD+R
*Sound card
*SD/MMC Memory card reader (Ricoh)
**Only tested SD (non-HC) cards.
*Control buttons/Hotkeys
**Volume control buttons
**Screen brightness control
**Thinklight control
**WLAN/BT/OFF toggle
**Media player control
**fingerprint reader does NOT work (fix below)
*Some ACPI features
**Battery status, power graphs and history
**Lid states and events
**Only tested with a single 6-cell battery
*ACPI features
** Suspend to RAM
** Suspend to Disk (Hibernate) FINALLY!! Be patient, though.
** STR and STD work even with full disk encryption (DM-crypt + LVM)!

=Getting the hardware to work=
==Display/Video==
Installing the proprietary NVidia drivers is highly recommended, EVEN IF you won't use 3D acceleration, because the open source nv driver will drain your battery much faster since it does not support PowerMizer at all. Practically, this means that the GPU will constantly run at full speed, thus consuming ~12 Watts more than it would otherwise (which is a LOT of power for a laptop).

The first time you boot Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at

System --> Administration --> Hardware Drivers.

You will have a choice between the 173 and 177 version of the driver.
*pro:
**Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not.
*con:
**version 177 causes a log out bug that is addressed below.
**version 177 might show some issues like terminal output not updating in some very weird cases (which I did not see in v173, this seems to have something to do with powermizer as well ...)
**version 180 as of 180.22 is known to have issue with suspend. Stay with version 177 until problem is fixed.

Once the proprietary drivers are installed, the "NVidia X Server Settings" program will be available in System --> Administration.

===Version 177 logout/X restart fix===
There is a known issue in the v177 proprietary NVidia driver - See Launchpad bug [http://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-177/+bug/258357 258357]. Once you install the v177 driver, logging out or restarting X will cease to work, though suspend to RAM/Disk will continue to function.

The work around is as follows:
* In /etc/gdm/gdm.conf , increase the value for GdmXserverTimeout to about 60. When logging out or restarting X, X will hang for ~35 seconds. By increasing the value from its default, GDM will give X more time before it assumes X is faulty.

===Choppy Compiz animations===
NVidia's PowerMizer feature will slow down the GPU when "inactive" even on AC power.

The NVidia driver does not report the correct refresh rate of the display to Compiz, resulting in choppy animations and effects. To fix this, install the <code>compizconfig-settings-manager</code> package, then go to System --> Preferences --> Advanced Desktop Effects Settings (also might be called CompizConfig Settings Manager). Click on General Options, go to the Display Settings tab, uncheck the Detect Refresh rate box and drag the Refresh Rate slider to 60. Also, check the Sync To VBlank box. This will improve the smoothness of the window animations significantly if you're sensitive to the choppy animations.

Compiz animations can also be choppy due to NVidia's PowerMizer feature, which slows down the GPU to conserve power when it is not in use. This works well for 3D games which constantly use 3D acceleration, but poorly for Compiz which uses the GPU in small bursts. It seems that the interval of the PowerMizer is way too long and is not speeding up when using in bursts. Fortunately, the situation seems to have improved in version 177 of the NVidia driver. To workaround this problem, I made a couple of shell scripts which keep the GPU at its highest speed while running on AC power. The first one is named "powermizer-loop" and does most of the work:

#!/bin/sh

while true; do

powerstate=`cat /proc/acpi/ac_adapter/AC/state | awk '{print $2}'`

if [ $powerstate = "on-line" ]; then
nvidia-settings -q all > /dev/null
fi
sleep 25;
done

The second is named "powermizer-off" and starts up powermizer-loop when I log in, ensuring that only one copy runs at a time:

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

I put both of these scripts in my home directory and made them executable by doing:

chmod a+x powermizer-loop powermizer-off

Then to make powermizer-off run on login, I opened System --> Preferences --> Sessions, clicked on Add, and entered the command to run the script, i.e. "/home/<user>/powermizer-off".

Of course, performance still suffers when running on battery, but hopefully NVidia will fix this problem in a future version of their driver.

=== EDID misdetection ===

EDID (Extended Display Identification Data) might be misdetected for your display, which reduces the number of resolutions available in the NVidia X Server Settings application. (For example, I was unable to set my laptop's screen to 1024x768 for use with a projector during a presentation.) If you encounter this problem, add the following lines to /etc/X11/xorg.conf in the "Screen" section:

Option "UseEdidFreqs" "FALSE"
Option "HorizSync" "40-70"

The 40-70 values are just an example. They seem to work well with my 1680x1050 display. You should put the values of your display there. On a 1920x1200 display, making this change prevents the display from coming on when X starts.

A better but more complicated way would be using Phoenix EDID Designer to dump and fix the EDID data and then setup the Nvidia driver so it will use the customized EDID data, as described at [http://myricci.com/index.php?option=com_content&task=view&id=36]

==Microphone/Sound In==
Might need to be turned on in the mixer. See [[Install Ubuntu Hardy Heron on a T61p#Internal Microphone/Microphone Input Jack]]

==Front radio kill switch==
When killing Wireless LAN with the killswitch at the front, you won't be able to get WLAN back up after switching back. See Launchpad bugs [http://bugs.launchpad.net/ubuntu/+source/hal/+bug/289286 289286] and [http://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.24/+bug/193970 193970] and the [https://wiki.ubuntu.com/IntrepidReleaseNotes#Cannot%20reactivate%20Intel%203945/4965%20wireless%20if%20booting%20with%20killswitch%20enabled Release Notes] on the Ubuntu Wiki.

This will be solved in intrepid-updates eventually.

For now there are a few ways to bring the interface back up (choose one):
* Right click the network manager icon in the tray, uncheck Enable Wireless, then check it again does the trick (at least for me)
* {{cmdroot|ip l s wlan0 up}}
* {{cmdroot|modprobe -r iwl3945 && modprobe iwl3945}}
* reboot
* suspend and resume

== Middle-button Scrolling ==
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.

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

{{cmduser| sudo gedit /etc/hal/fdi/policy/mouse-wheel.fdi}}

Paste and save the following code, which will give vertical wheel emulation only:
<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>
There is [http://psung.blogspot.com/2008/09/scrolling-with-thinkpads-trackpoint-in.html another method] to get horizontal scrolling as well, but this is not confirmed to work.

source:
*[[Installing_Ubuntu_8.10_%28Intrepid_Ibex%29_on_a_ThinkPad_T61#Emulate_Wheel_.28Middle-click_scrolling.29| Installing Ubuntu 8.10 (Intrepid Ibex) on a ThinkPad T61 - Emulate Wheel (Middle-click scrolling)]]

==Fingerprint Reader==

The [http://thinkfinger.sourceforge.net Thinkfinger] package allows you to swipe a finger in most places where you would have to type your password. This works with sudo, gksudo and on the login page and with a little fix also for the screen saver. Also, you are still required to type your user name on the login screen.

0) Set up the third party repository (optional but recommended!)

due to this [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 Bug #256429: Carriage-return required after finger scan] you need to press the return key after you swipe your finger with the current version of the kernel and the packages in ubuntu. The bug is caused by the fact that it does not recognize the fingerprint reader 100% correctly ([https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429/comments/29 Description of the root cause]) , as a temporary workaround there is a special package repository.

The packages present in ubuntu intrepid will work but you need to press enter after you swipe your finger.

Click System -> administration -> software sources
go to the tab "third-party software" and click Add ...

Enter in the popup window:

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

Click Add source, it will ask to refresh the package list, click reload.

1) Install the following packages:

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

2) For your user:

{{cmduser| sudo tf-tool --acquire && sudo tf-tool --verify}}

A completed fingerprint setup should look something like this:

frank@Laptop:~$ sudo tf-tool --acquire && sudo tf-tool --verify

ThinkFinger 0.3 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>

Initializing... done.
Please swipe your finger (successful swipes 3/3, failed swipes: 0)... done.
Storing data (/tmp/test.bir)... done.

ThinkFinger 0.3 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>

Initializing... done.
Please swipe your finger (successful swipes 1/1, failed swipes: 0)... done.
Result: Fingerprint does match.
frank@CLaptop:~$

This will store your fingerprint information in /home/$USERNAME/.thinkfinger.bir

You should do this step for each user who wants to use the fingerprint reader

3) Enable use of reader for authentication:

{{cmduser| sudo gedit /etc/pam.d/common-auth}}

add
auth sufficient pam_thinkfinger.so
before the line which contains pam_unix.so and add
try_first_pass
to the end of the line containing pam_unix.so.

So it should look something like this:
...
auth sufficient pam_thinkfinger.so
auth [success=1 default=ignore] pam_unix.so nullok_secure try_first_pass
...

4) Check uinput kernel module:

{{cmduser|lsmod | grep uinput}}
If the output starts with uinput, then you're done.
If you don't get any output, then it needs to be started and set to start on boot.

Start uinput:

{{cmduser|sudo modprobe uinput}}

Start on boot:

{{cmduser|sudo gedit /etc/modules}}

make sure there is a line like this or add it at the bottom:
uinput

5) Enabling thinkfinger for gnome-screensaver

*create this file:
{{cmduser|sudo gedit /etc/udev/rules.d/60-thinkfinger.rules}}
with this contents:
#
# 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/Install_Ubuntu_Intrepid_Ibex_on_a_T61p#Fingerprint_Reader
# which was taken and modified from:
# http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
# 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"

*Make the group:
{{cmduser|sudo groupadd fingerprint}}
*per user:
{{cmduser|sudo gpasswd -a $USERNAME fingerprint && sudo chown $USERNAME:root /home/$USERNAME/.thinkfinger.bir }}

Reboot your laptop and you should be ready to swipe!

Sources:
* [[Install_Ubuntu_Gutsy_Gibbon_on_a_T61p#Fingerprint_Reader| Install Ubuntu Gutsy Gibbon on a T61p]]
* [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 Bug #256429: Carriage-return required after finger scan] & [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429/comments/21 Solution for the bug in the comments]
* [https://launchpad.net/~jon-oberheide/+archive Repository for the third party fix] credits to [https://launchpad.net/~jon-oberheide Jon Oberheide]
* [[How_to_enable_the_fingerprint_reader_with_ThinkFinger| General page about Fingerprint reader with thinkfinger]] & [[How_to_enable_the_fingerprint_reader_with_ThinkFinger#xscreensaver.2Fgnome-screensaver| Specific gnome-screensaver section]]

==Hard Drive Active Protection System (APS ~ HDAPS)==
Please add to this section

Some interesting links:
* [[Active_Protection_System| Description of APS]]
* [[How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS]]
* [[Tp_smapi| tp_smapi kernel modules]]

=Other Problems=

== Resume Requests Network Key ==
On resume Network Manager request the wifi network key several times before connecting to network. This has been noted on a 6459CTO laptop and no known fix is available. Currently with this problem it takes several minutes to regain network access after resume.

== Black Screen on Resume ==
On the 6459CTO with default 8.10 install suspend did not work. Installing the proposed updated fixed the problem. To do this add the following line to /etc/apt/sources.list

deb http://us.archive.ubuntu.com/ubuntu/ intrepid-proposed restricted main universe multiverse

== Wireless not working after resume (Atheros) ==
After resuming from suspend, I am unable to reconnect to my wireless network. Network Manager asks me for my password over and over again but never succeeds in connecting. I'm using the Thinkpad (Atheros) A/B/G wireless card.

To fix this problem, I followed the instructions listed at https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/275692. Specifically, I created a file called /etc/pm/config.d/01-modules and put the following line in it:

SUSPEND_MODULES="ath_pci"

== Brightness control on battery power ==
By default, when unplugging the AC power while the system is running, the brightness of the display goes down even when you have set not to in the Power Management settings and you are not able to reach a brightness level as high as possible when connected to AC power. This is not a software setting or GNOME bug, but a BIOS setting. In the BIOS you can find a brightness setting in the Power section. Set it to high for normal, expected behavior. You can let the GNOME Power Manager still lower the brightness, but you will be able to increase it when needed.

=Other Information=
== Saving power ==
Some nice information on power saving you can find at

http://www.lesswatts.org

A tool that allows you to test most tips and tricks to reduce power is powertop, you can install it using

{{cmduser|sudo apt-get install powertop}}

and run it with:

{{cmduser|sudo powertop}}

For more information see http://www.lesswatts.org/projects/powertop/
== Battery control by tp_smapi ==
You need to load a kernel module first:
sudo modprobe tp_smapi

Now, you will be able to have significantly more control over your battery charging via /sys/devices/platform/smapi.

For example, you could set a threshold value of 90% for charging, preventing the battery from charging all the way in exchange for a reduction in the loss of battery capacity that occurs after multiple cycles.
echo "90" | sudo tee -a /sys/devices/platform/smapi/BAT0/start_charge_thresh
(by default this was set to 86% on my laptop)

View the number of charge cycles your battery has had in its lifetime:
cat /sys/devices/platform/smapi/BAT0/cycle_count

While AC connected, force discharging of your battery:
echo "1" | sudo tee -a /sys/devices/platform/smapi/BAT0/force_discharge

For convenience, you could load the kernel module at boot time by adding it to /etc/modules.
echo "tp_smapi" | sudo tee -a /etc/modules

If you have an Ultrabay battery, you might want to place this [http://forum.thinkpads.com/viewtopic.php?p=433463#p433463 script] into <code>/etc/crontab</code> to keep the Ultrabay battery from being completely discharged to 0%, which permanently damages the battery.
# rolls to BAT0 when remaining capacity on BAT1 is less than 20%. Change .2 if wanted. Swap BAT0 and BAT1 if tp_smapi thinks the ultrabay is BAT0.
awk '{if (/remaining capacity/) left=$3; if (/last full capacity/) full=$4} END {if ((left/full) < .2) system("echo 1 > /sys/devices/platform/smapi/BAT0/force_discharge")}' /proc/acpi/battery/BAT1/*
Remember the script needs root in order to write to the files in <code>/sys/devices/platform/smapi/BAT{0,1}/</code>.

= Compared to Hardy (8.04) =
Why upgrade your T61p to Intrepid or why not? (Specific for T61p)
== Improvements ==
*Ricoh SD card reader now reads read-only SD card. (Tested with Adata 150X 2GB SD card)
*Newer Wireless LAN drivers. For Intel cards this results in working LED, more sensitive reception, increased stability of connections and some 802.1x bugfixes.
*Out-of-the-box Suspend to RAM functionality (also faster resume).
*Working but slow Suspend to Disk functionality.
== Bugs and Regressions ==
*Hard radio killswitch (at the front) cannot bring WLAN back up after killing it. (workaround available)
*X hangs for approx. 35 seconds when restarting or logging out. (workaround available)
*Atheros WLAN not working after resume from Suspend to RAM (but a workaround is available; [[#Wireless_not_working_after_resume_.28Atheros.29|see above]]).

[[Category:T61p]]
[[Category:Ubuntu]]
[[Category:Ubuntu 8.10]]

Install Ubuntu Intrepid Ibex on a T61p

2009-01-18T15:35:18Z

Trampas: /* Display/Video */

=What works out of the box?=
*Wireless (Intel 3945ABG or 4965AGN)
**Only tested G mode
*Wired LAN
*Video (VESA)
**Hardware Drivers panel offers to install nVIDIA proprietary drivers on first boot.
*Touchpoint and Trackpad
**Including scroll at the right side of the pad by default.
**Middle-button scrolling does NOT work (fix below)
*Optical drive
**Optiarc AD-7910A works fine with Brasero disc burning
***Tested: CD-R, DVD+R
*Sound card
*SD/MMC Memory card reader (Ricoh)
**Only tested SD (non-HC) cards.
*Control buttons/Hotkeys
**Volume control buttons
**Screen brightness control
**Thinklight control
**WLAN/BT/OFF toggle
**Media player control
**fingerprint reader does NOT work (fix below)
*Some ACPI features
**Battery status, power graphs and history
**Lid states and events
**Only tested with a single 6-cell battery
*ACPI features
** Suspend to RAM
** Suspend to Disk (Hibernate) FINALLY!! Be patient, though.
** STR and STD work even with full disk encryption (DM-crypt + LVM)!

=Getting the hardware to work=
==Display/Video==
Installing the proprietary NVidia drivers is highly recommended, EVEN IF you won't use 3D acceleration, because the open source nv driver will drain your battery much faster since it does not support PowerMizer at all. Practically, this means that the GPU will constantly run at full speed, thus consuming ~12 Watts more than it would otherwise (which is a LOT of power for a laptop).

The first time you boot Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at

System --> Administration --> Hardware Drivers.

You will have a choice between the 173 and 177 version of the driver.
*pro:
**Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not.
*con:
**version 177 causes a log out bug that is addressed below.
**version 177 might show some issues like terminal output not updating in some very weird cases (which I did not see in v173, this seems to have something to do with powermizer as well ...)
**version 180 as of 180.22 is known to have issue with suspend. Stay with version 177 until problem is fixed.

Once the proprietary drivers are installed, the "NVidia X Server Settings" program will be available in System --> Administration.

===Version 177 logout/X restart fix===
There is a known issue in the v177 proprietary NVidia driver - See Launchpad bug [http://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-177/+bug/258357 258357]. Once you install the v177 driver, logging out or restarting X will cease to work, though suspend to RAM/Disk will continue to function.

The work around is as follows:
* In /etc/gdm/gdm.conf , increase the value for GdmXserverTimeout to about 60. When logging out or restarting X, X will hang for ~35 seconds. By increasing the value from its default, GDM will give X more time before it assumes X is faulty.

===Choppy Compiz animations===
NVidia's PowerMizer feature will slow down the GPU when "inactive" even on AC power.

The NVidia driver does not report the correct refresh rate of the display to Compiz, resulting in choppy animations and effects. To fix this, install the <code>compizconfig-settings-manager</code> package, then go to System --> Preferences --> Advanced Desktop Effects Settings (also might be called CompizConfig Settings Manager). Click on General Options, go to the Display Settings tab, uncheck the Detect Refresh rate box and drag the Refresh Rate slider to 60. Also, check the Sync To VBlank box. This will improve the smoothness of the window animations significantly if you're sensitive to the choppy animations.

Compiz animations can also be choppy due to NVidia's PowerMizer feature, which slows down the GPU to conserve power when it is not in use. This works well for 3D games which constantly use 3D acceleration, but poorly for Compiz which uses the GPU in small bursts. It seems that the interval of the PowerMizer is way too long and is not speeding up when using in bursts. Fortunately, the situation seems to have improved in version 177 of the NVidia driver. To workaround this problem, I made a couple of shell scripts which keep the GPU at its highest speed while running on AC power. The first one is named "powermizer-loop" and does most of the work:

#!/bin/sh

while true; do

powerstate=`cat /proc/acpi/ac_adapter/AC/state | awk '{print $2}'`

if [ $powerstate = "on-line" ]; then
nvidia-settings -q all > /dev/null
fi
sleep 25;
done

The second is named "powermizer-off" and starts up powermizer-loop when I log in, ensuring that only one copy runs at a time:

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

I put both of these scripts in my home directory and made them executable by doing:

chmod a+x powermizer-loop powermizer-off

Then to make powermizer-off run on login, I opened System --> Preferences --> Sessions, clicked on Add, and entered the command to run the script, i.e. "/home/<user>/powermizer-off".

Of course, performance still suffers when running on battery, but hopefully NVidia will fix this problem in a future version of their driver.

=== EDID misdetection ===

EDID (Extended Display Identification Data) might be misdetected for your display, which reduces the number of resolutions available in the NVidia X Server Settings application. (For example, I was unable to set my laptop's screen to 1024x768 for use with a projector during a presentation.) If you encounter this problem, add the following lines to /etc/X11/xorg.conf in the "Screen" section:

Option "UseEdidFreqs" "FALSE"
Option "HorizSync" "40-70"

The 40-70 values are just an example. They seem to work well with my 1680x1050 display. You should put the values of your display there. On a 1920x1200 display, making this change prevents the display from coming on when X starts.

A better but more complicated way would be using Phoenix EDID Designer to dump and fix the EDID data and then setup the Nvidia driver so it will use the customized EDID data, as described at [http://myricci.com/index.php?option=com_content&task=view&id=36]

==Microphone/Sound In==
Might need to be turned on in the mixer. See [[Install Ubuntu Hardy Heron on a T61p#Internal Microphone/Microphone Input Jack]]

==Front radio kill switch==
When killing Wireless LAN with the killswitch at the front, you won't be able to get WLAN back up after switching back. See Launchpad bugs [http://bugs.launchpad.net/ubuntu/+source/hal/+bug/289286 289286] and [http://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.24/+bug/193970 193970] and the [https://wiki.ubuntu.com/IntrepidReleaseNotes#Cannot%20reactivate%20Intel%203945/4965%20wireless%20if%20booting%20with%20killswitch%20enabled Release Notes] on the Ubuntu Wiki.

This will be solved in intrepid-updates eventually.

For now there are a few ways to bring the interface back up (choose one):
* Right click the network manager icon in the tray, uncheck Enable Wireless, then check it again does the trick (at least for me)
* {{cmdroot|ip l s wlan0 up}}
* {{cmdroot|modprobe -r iwl3945 && modprobe iwl3945}}
* reboot
* suspend and resume

== Middle-button Scrolling ==
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.

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

{{cmduser| sudo gedit /etc/hal/fdi/policy/mouse-wheel.fdi}}

Paste and save the following code, which will give vertical wheel emulation only:
<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>
There is [http://psung.blogspot.com/2008/09/scrolling-with-thinkpads-trackpoint-in.html another method] to get horizontal scrolling as well, but this is not confirmed to work.

source:
*[[Installing_Ubuntu_8.10_%28Intrepid_Ibex%29_on_a_ThinkPad_T61#Emulate_Wheel_.28Middle-click_scrolling.29| Installing Ubuntu 8.10 (Intrepid Ibex) on a ThinkPad T61 - Emulate Wheel (Middle-click scrolling)]]

==Fingerprint Reader==

The [http://thinkfinger.sourceforge.net Thinkfinger] package allows you to swipe a finger in most places where you would have to type your password. This works with sudo, gksudo and on the login page and with a little fix also for the screen saver. Also, you are still required to type your user name on the login screen.

0) Set up the third party repository (optional but recommended!)

due to this [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 Bug #256429: Carriage-return required after finger scan] you need to press the return key after you swipe your finger with the current version of the kernel and the packages in ubuntu. The bug is caused by the fact that it does not recognize the fingerprint reader 100% correctly ([https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429/comments/29 Description of the root cause]) , as a temporary workaround there is a special package repository.

The packages present in ubuntu intrepid will work but you need to press enter after you swipe your finger.

Click System -> administration -> software sources
go to the tab "third-party software" and click Add ...

Enter in the popup window:

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

Click Add source, it will ask to refresh the package list, click reload.

1) Install the following packages:

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

2) For your user:

{{cmduser| sudo tf-tool --acquire && sudo tf-tool --verify}}

A completed fingerprint setup should look something like this:

frank@Laptop:~$ sudo tf-tool --acquire && sudo tf-tool --verify

ThinkFinger 0.3 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>

Initializing... done.
Please swipe your finger (successful swipes 3/3, failed swipes: 0)... done.
Storing data (/tmp/test.bir)... done.

ThinkFinger 0.3 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>

Initializing... done.
Please swipe your finger (successful swipes 1/1, failed swipes: 0)... done.
Result: Fingerprint does match.
frank@CLaptop:~$

This will store your fingerprint information in /home/$USERNAME/.thinkfinger.bir

You should do this step for each user who wants to use the fingerprint reader

3) Enable use of reader for authentication:

{{cmduser| sudo gedit /etc/pam.d/common-auth}}

add
auth sufficient pam_thinkfinger.so
before the line which contains pam_unix.so and add
try_first_pass
to the end of the line containing pam_unix.so.

So it should look something like this:
...
auth sufficient pam_thinkfinger.so
auth [success=1 default=ignore] pam_unix.so nullok_secure try_first_pass
...

4) Check uinput kernel module:

{{cmduser|lsmod | grep uinput}}
If the output starts with uinput, then you're done.
If you don't get any output, then it needs to be started and set to start on boot.

Start uinput:

{{cmduser|sudo modprobe uinput}}

Start on boot:

{{cmduser|sudo gedit /etc/modules}}

make sure there is a line like this or add it at the bottom:
uinput

5) Enabling thinkfinger for gnome-screensaver

*create this file:
{{cmduser|sudo gedit /etc/udev/rules.d/60-thinkfinger.rules}}
with this contents:
#
# 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/Install_Ubuntu_Intrepid_Ibex_on_a_T61p#Fingerprint_Reader
# which was taken and modified from:
# http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
# 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"

*Make the group:
{{cmduser|sudo groupadd fingerprint}}
*per user:
{{cmduser|sudo gpasswd -a $USERNAME fingerprint && sudo chown $USERNAME:root /home/$USERNAME/.thinkfinger.bir }}

Reboot your laptop and you should be ready to swipe!

Sources:
* [[Install_Ubuntu_Gutsy_Gibbon_on_a_T61p#Fingerprint_Reader| Install Ubuntu Gutsy Gibbon on a T61p]]
* [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 Bug #256429: Carriage-return required after finger scan] & [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429/comments/21 Solution for the bug in the comments]
* [https://launchpad.net/~jon-oberheide/+archive Repository for the third party fix] credits to [https://launchpad.net/~jon-oberheide Jon Oberheide]
* [[How_to_enable_the_fingerprint_reader_with_ThinkFinger| General page about Fingerprint reader with thinkfinger]] & [[How_to_enable_the_fingerprint_reader_with_ThinkFinger#xscreensaver.2Fgnome-screensaver| Specific gnome-screensaver section]]

==Hard Drive Active Protection System (APS ~ HDAPS)==
Please add to this section

Some interesting links:
* [[Active_Protection_System| Description of APS]]
* [[How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS]]
* [[Tp_smapi| tp_smapi kernel modules]]

=Other Problems=
== Black Screen on Resume ==
On the 6459CTO with default 8.10 install suspend did not work. Installing the proposed updated fixed the problem. To do this add the following line to /etc/apt/sources.list

deb http://us.archive.ubuntu.com/ubuntu/ intrepid-proposed restricted main universe multiverse

== Wireless not working after resume (Atheros) ==
After resuming from suspend, I am unable to reconnect to my wireless network. Network Manager asks me for my password over and over again but never succeeds in connecting. I'm using the Thinkpad (Atheros) A/B/G wireless card.

To fix this problem, I followed the instructions listed at https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/275692. Specifically, I created a file called /etc/pm/config.d/01-modules and put the following line in it:

SUSPEND_MODULES="ath_pci"

== Brightness control on battery power ==
By default, when unplugging the AC power while the system is running, the brightness of the display goes down even when you have set not to in the Power Management settings and you are not able to reach a brightness level as high as possible when connected to AC power. This is not a software setting or GNOME bug, but a BIOS setting. In the BIOS you can find a brightness setting in the Power section. Set it to high for normal, expected behavior. You can let the GNOME Power Manager still lower the brightness, but you will be able to increase it when needed.

=Other Information=
== Saving power ==
Some nice information on power saving you can find at

http://www.lesswatts.org

A tool that allows you to test most tips and tricks to reduce power is powertop, you can install it using

{{cmduser|sudo apt-get install powertop}}

and run it with:

{{cmduser|sudo powertop}}

For more information see http://www.lesswatts.org/projects/powertop/
== Battery control by tp_smapi ==
You need to load a kernel module first:
sudo modprobe tp_smapi

Now, you will be able to have significantly more control over your battery charging via /sys/devices/platform/smapi.

For example, you could set a threshold value of 90% for charging, preventing the battery from charging all the way in exchange for a reduction in the loss of battery capacity that occurs after multiple cycles.
echo "90" | sudo tee -a /sys/devices/platform/smapi/BAT0/start_charge_thresh
(by default this was set to 86% on my laptop)

View the number of charge cycles your battery has had in its lifetime:
cat /sys/devices/platform/smapi/BAT0/cycle_count

While AC connected, force discharging of your battery:
echo "1" | sudo tee -a /sys/devices/platform/smapi/BAT0/force_discharge

For convenience, you could load the kernel module at boot time by adding it to /etc/modules.
echo "tp_smapi" | sudo tee -a /etc/modules

If you have an Ultrabay battery, you might want to place this [http://forum.thinkpads.com/viewtopic.php?p=433463#p433463 script] into <code>/etc/crontab</code> to keep the Ultrabay battery from being completely discharged to 0%, which permanently damages the battery.
# rolls to BAT0 when remaining capacity on BAT1 is less than 20%. Change .2 if wanted. Swap BAT0 and BAT1 if tp_smapi thinks the ultrabay is BAT0.
awk '{if (/remaining capacity/) left=$3; if (/last full capacity/) full=$4} END {if ((left/full) < .2) system("echo 1 > /sys/devices/platform/smapi/BAT0/force_discharge")}' /proc/acpi/battery/BAT1/*
Remember the script needs root in order to write to the files in <code>/sys/devices/platform/smapi/BAT{0,1}/</code>.

= Compared to Hardy (8.04) =
Why upgrade your T61p to Intrepid or why not? (Specific for T61p)
== Improvements ==
*Ricoh SD card reader now reads read-only SD card. (Tested with Adata 150X 2GB SD card)
*Newer Wireless LAN drivers. For Intel cards this results in working LED, more sensitive reception, increased stability of connections and some 802.1x bugfixes.
*Out-of-the-box Suspend to RAM functionality (also faster resume).
*Working but slow Suspend to Disk functionality.
== Bugs and Regressions ==
*Hard radio killswitch (at the front) cannot bring WLAN back up after killing it. (workaround available)
*X hangs for approx. 35 seconds when restarting or logging out. (workaround available)
*Atheros WLAN not working after resume from Suspend to RAM (but a workaround is available; [[#Wireless_not_working_after_resume_.28Atheros.29|see above]]).

[[Category:T61p]]
[[Category:Ubuntu]]
[[Category:Ubuntu 8.10]]

Install Ubuntu Intrepid Ibex on a T61p

2009-01-18T15:32:28Z

Trampas: /* Other Problems */

=What works out of the box?=
*Wireless (Intel 3945ABG or 4965AGN)
**Only tested G mode
*Wired LAN
*Video (VESA)
**Hardware Drivers panel offers to install nVIDIA proprietary drivers on first boot.
*Touchpoint and Trackpad
**Including scroll at the right side of the pad by default.
**Middle-button scrolling does NOT work (fix below)
*Optical drive
**Optiarc AD-7910A works fine with Brasero disc burning
***Tested: CD-R, DVD+R
*Sound card
*SD/MMC Memory card reader (Ricoh)
**Only tested SD (non-HC) cards.
*Control buttons/Hotkeys
**Volume control buttons
**Screen brightness control
**Thinklight control
**WLAN/BT/OFF toggle
**Media player control
**fingerprint reader does NOT work (fix below)
*Some ACPI features
**Battery status, power graphs and history
**Lid states and events
**Only tested with a single 6-cell battery
*ACPI features
** Suspend to RAM
** Suspend to Disk (Hibernate) FINALLY!! Be patient, though.
** STR and STD work even with full disk encryption (DM-crypt + LVM)!

=Getting the hardware to work=
==Display/Video==
Installing the proprietary NVidia drivers is highly recommended, EVEN IF you won't use 3D acceleration, because the open source nv driver will drain your battery much faster since it does not support PowerMizer at all. Practically, this means that the GPU will constantly run at full speed, thus consuming ~12 Watts more than it would otherwise (which is a LOT of power for a laptop).

The first time you boot Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at

System --> Administration --> Hardware Drivers.

You will have a choice between the 173 and 177 version of the driver.
*pro:
**Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not.
*con:
**version 177 causes a log out bug that is addressed below.
**version 177 might show some issues like terminal output not updating in some very weird cases (which I did not see in v173, this seems to have something to do with powermizer as well ...)

Once the proprietary drivers are installed, the "NVidia X Server Settings" program will be available in System --> Administration.

===Version 177 logout/X restart fix===
There is a known issue in the v177 proprietary NVidia driver - See Launchpad bug [http://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-177/+bug/258357 258357]. Once you install the v177 driver, logging out or restarting X will cease to work, though suspend to RAM/Disk will continue to function.

The work around is as follows:
* In /etc/gdm/gdm.conf , increase the value for GdmXserverTimeout to about 60. When logging out or restarting X, X will hang for ~35 seconds. By increasing the value from its default, GDM will give X more time before it assumes X is faulty.

===Choppy Compiz animations===
NVidia's PowerMizer feature will slow down the GPU when "inactive" even on AC power.

The NVidia driver does not report the correct refresh rate of the display to Compiz, resulting in choppy animations and effects. To fix this, install the <code>compizconfig-settings-manager</code> package, then go to System --> Preferences --> Advanced Desktop Effects Settings (also might be called CompizConfig Settings Manager). Click on General Options, go to the Display Settings tab, uncheck the Detect Refresh rate box and drag the Refresh Rate slider to 60. Also, check the Sync To VBlank box. This will improve the smoothness of the window animations significantly if you're sensitive to the choppy animations.

Compiz animations can also be choppy due to NVidia's PowerMizer feature, which slows down the GPU to conserve power when it is not in use. This works well for 3D games which constantly use 3D acceleration, but poorly for Compiz which uses the GPU in small bursts. It seems that the interval of the PowerMizer is way too long and is not speeding up when using in bursts. Fortunately, the situation seems to have improved in version 177 of the NVidia driver. To workaround this problem, I made a couple of shell scripts which keep the GPU at its highest speed while running on AC power. The first one is named "powermizer-loop" and does most of the work:

#!/bin/sh

while true; do

powerstate=`cat /proc/acpi/ac_adapter/AC/state | awk '{print $2}'`

if [ $powerstate = "on-line" ]; then
nvidia-settings -q all > /dev/null
fi
sleep 25;
done

The second is named "powermizer-off" and starts up powermizer-loop when I log in, ensuring that only one copy runs at a time:

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

I put both of these scripts in my home directory and made them executable by doing:

chmod a+x powermizer-loop powermizer-off

Then to make powermizer-off run on login, I opened System --> Preferences --> Sessions, clicked on Add, and entered the command to run the script, i.e. "/home/<user>/powermizer-off".

Of course, performance still suffers when running on battery, but hopefully NVidia will fix this problem in a future version of their driver.

=== EDID misdetection ===

EDID (Extended Display Identification Data) might be misdetected for your display, which reduces the number of resolutions available in the NVidia X Server Settings application. (For example, I was unable to set my laptop's screen to 1024x768 for use with a projector during a presentation.) If you encounter this problem, add the following lines to /etc/X11/xorg.conf in the "Screen" section:

Option "UseEdidFreqs" "FALSE"
Option "HorizSync" "40-70"

The 40-70 values are just an example. They seem to work well with my 1680x1050 display. You should put the values of your display there. On a 1920x1200 display, making this change prevents the display from coming on when X starts.

A better but more complicated way would be using Phoenix EDID Designer to dump and fix the EDID data and then setup the Nvidia driver so it will use the customized EDID data, as described at [http://myricci.com/index.php?option=com_content&task=view&id=36]

==Microphone/Sound In==
Might need to be turned on in the mixer. See [[Install Ubuntu Hardy Heron on a T61p#Internal Microphone/Microphone Input Jack]]

==Front radio kill switch==
When killing Wireless LAN with the killswitch at the front, you won't be able to get WLAN back up after switching back. See Launchpad bugs [http://bugs.launchpad.net/ubuntu/+source/hal/+bug/289286 289286] and [http://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.24/+bug/193970 193970] and the [https://wiki.ubuntu.com/IntrepidReleaseNotes#Cannot%20reactivate%20Intel%203945/4965%20wireless%20if%20booting%20with%20killswitch%20enabled Release Notes] on the Ubuntu Wiki.

This will be solved in intrepid-updates eventually.

For now there are a few ways to bring the interface back up (choose one):
* Right click the network manager icon in the tray, uncheck Enable Wireless, then check it again does the trick (at least for me)
* {{cmdroot|ip l s wlan0 up}}
* {{cmdroot|modprobe -r iwl3945 && modprobe iwl3945}}
* reboot
* suspend and resume

== Middle-button Scrolling ==
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.

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

{{cmduser| sudo gedit /etc/hal/fdi/policy/mouse-wheel.fdi}}

Paste and save the following code, which will give vertical wheel emulation only:
<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>
There is [http://psung.blogspot.com/2008/09/scrolling-with-thinkpads-trackpoint-in.html another method] to get horizontal scrolling as well, but this is not confirmed to work.

source:
*[[Installing_Ubuntu_8.10_%28Intrepid_Ibex%29_on_a_ThinkPad_T61#Emulate_Wheel_.28Middle-click_scrolling.29| Installing Ubuntu 8.10 (Intrepid Ibex) on a ThinkPad T61 - Emulate Wheel (Middle-click scrolling)]]

==Fingerprint Reader==

The [http://thinkfinger.sourceforge.net Thinkfinger] package allows you to swipe a finger in most places where you would have to type your password. This works with sudo, gksudo and on the login page and with a little fix also for the screen saver. Also, you are still required to type your user name on the login screen.

0) Set up the third party repository (optional but recommended!)

due to this [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 Bug #256429: Carriage-return required after finger scan] you need to press the return key after you swipe your finger with the current version of the kernel and the packages in ubuntu. The bug is caused by the fact that it does not recognize the fingerprint reader 100% correctly ([https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429/comments/29 Description of the root cause]) , as a temporary workaround there is a special package repository.

The packages present in ubuntu intrepid will work but you need to press enter after you swipe your finger.

Click System -> administration -> software sources
go to the tab "third-party software" and click Add ...

Enter in the popup window:

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

Click Add source, it will ask to refresh the package list, click reload.

1) Install the following packages:

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

2) For your user:

{{cmduser| sudo tf-tool --acquire && sudo tf-tool --verify}}

A completed fingerprint setup should look something like this:

frank@Laptop:~$ sudo tf-tool --acquire && sudo tf-tool --verify

ThinkFinger 0.3 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>

Initializing... done.
Please swipe your finger (successful swipes 3/3, failed swipes: 0)... done.
Storing data (/tmp/test.bir)... done.

ThinkFinger 0.3 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>

Initializing... done.
Please swipe your finger (successful swipes 1/1, failed swipes: 0)... done.
Result: Fingerprint does match.
frank@CLaptop:~$

This will store your fingerprint information in /home/$USERNAME/.thinkfinger.bir

You should do this step for each user who wants to use the fingerprint reader

3) Enable use of reader for authentication:

{{cmduser| sudo gedit /etc/pam.d/common-auth}}

add
auth sufficient pam_thinkfinger.so
before the line which contains pam_unix.so and add
try_first_pass
to the end of the line containing pam_unix.so.

So it should look something like this:
...
auth sufficient pam_thinkfinger.so
auth [success=1 default=ignore] pam_unix.so nullok_secure try_first_pass
...

4) Check uinput kernel module:

{{cmduser|lsmod | grep uinput}}
If the output starts with uinput, then you're done.
If you don't get any output, then it needs to be started and set to start on boot.

Start uinput:

{{cmduser|sudo modprobe uinput}}

Start on boot:

{{cmduser|sudo gedit /etc/modules}}

make sure there is a line like this or add it at the bottom:
uinput

5) Enabling thinkfinger for gnome-screensaver

*create this file:
{{cmduser|sudo gedit /etc/udev/rules.d/60-thinkfinger.rules}}
with this contents:
#
# 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/Install_Ubuntu_Intrepid_Ibex_on_a_T61p#Fingerprint_Reader
# which was taken and modified from:
# http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
# 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"

*Make the group:
{{cmduser|sudo groupadd fingerprint}}
*per user:
{{cmduser|sudo gpasswd -a $USERNAME fingerprint && sudo chown $USERNAME:root /home/$USERNAME/.thinkfinger.bir }}

Reboot your laptop and you should be ready to swipe!

Sources:
* [[Install_Ubuntu_Gutsy_Gibbon_on_a_T61p#Fingerprint_Reader| Install Ubuntu Gutsy Gibbon on a T61p]]
* [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 Bug #256429: Carriage-return required after finger scan] & [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429/comments/21 Solution for the bug in the comments]
* [https://launchpad.net/~jon-oberheide/+archive Repository for the third party fix] credits to [https://launchpad.net/~jon-oberheide Jon Oberheide]
* [[How_to_enable_the_fingerprint_reader_with_ThinkFinger| General page about Fingerprint reader with thinkfinger]] & [[How_to_enable_the_fingerprint_reader_with_ThinkFinger#xscreensaver.2Fgnome-screensaver| Specific gnome-screensaver section]]

==Hard Drive Active Protection System (APS ~ HDAPS)==
Please add to this section

Some interesting links:
* [[Active_Protection_System| Description of APS]]
* [[How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS]]
* [[Tp_smapi| tp_smapi kernel modules]]

=Other Problems=
== Black Screen on Resume ==
On the 6459CTO with default 8.10 install suspend did not work. Installing the proposed updated fixed the problem. To do this add the following line to /etc/apt/sources.list

deb http://us.archive.ubuntu.com/ubuntu/ intrepid-proposed restricted main universe multiverse

== Wireless not working after resume (Atheros) ==
After resuming from suspend, I am unable to reconnect to my wireless network. Network Manager asks me for my password over and over again but never succeeds in connecting. I'm using the Thinkpad (Atheros) A/B/G wireless card.

To fix this problem, I followed the instructions listed at https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/275692. Specifically, I created a file called /etc/pm/config.d/01-modules and put the following line in it:

SUSPEND_MODULES="ath_pci"

== Brightness control on battery power ==
By default, when unplugging the AC power while the system is running, the brightness of the display goes down even when you have set not to in the Power Management settings and you are not able to reach a brightness level as high as possible when connected to AC power. This is not a software setting or GNOME bug, but a BIOS setting. In the BIOS you can find a brightness setting in the Power section. Set it to high for normal, expected behavior. You can let the GNOME Power Manager still lower the brightness, but you will be able to increase it when needed.

=Other Information=
== Saving power ==
Some nice information on power saving you can find at

http://www.lesswatts.org

A tool that allows you to test most tips and tricks to reduce power is powertop, you can install it using

{{cmduser|sudo apt-get install powertop}}

and run it with:

{{cmduser|sudo powertop}}

For more information see http://www.lesswatts.org/projects/powertop/
== Battery control by tp_smapi ==
You need to load a kernel module first:
sudo modprobe tp_smapi

Now, you will be able to have significantly more control over your battery charging via /sys/devices/platform/smapi.

For example, you could set a threshold value of 90% for charging, preventing the battery from charging all the way in exchange for a reduction in the loss of battery capacity that occurs after multiple cycles.
echo "90" | sudo tee -a /sys/devices/platform/smapi/BAT0/start_charge_thresh
(by default this was set to 86% on my laptop)

View the number of charge cycles your battery has had in its lifetime:
cat /sys/devices/platform/smapi/BAT0/cycle_count

While AC connected, force discharging of your battery:
echo "1" | sudo tee -a /sys/devices/platform/smapi/BAT0/force_discharge

For convenience, you could load the kernel module at boot time by adding it to /etc/modules.
echo "tp_smapi" | sudo tee -a /etc/modules

If you have an Ultrabay battery, you might want to place this [http://forum.thinkpads.com/viewtopic.php?p=433463#p433463 script] into <code>/etc/crontab</code> to keep the Ultrabay battery from being completely discharged to 0%, which permanently damages the battery.
# rolls to BAT0 when remaining capacity on BAT1 is less than 20%. Change .2 if wanted. Swap BAT0 and BAT1 if tp_smapi thinks the ultrabay is BAT0.
awk '{if (/remaining capacity/) left=$3; if (/last full capacity/) full=$4} END {if ((left/full) < .2) system("echo 1 > /sys/devices/platform/smapi/BAT0/force_discharge")}' /proc/acpi/battery/BAT1/*
Remember the script needs root in order to write to the files in <code>/sys/devices/platform/smapi/BAT{0,1}/</code>.

= Compared to Hardy (8.04) =
Why upgrade your T61p to Intrepid or why not? (Specific for T61p)
== Improvements ==
*Ricoh SD card reader now reads read-only SD card. (Tested with Adata 150X 2GB SD card)
*Newer Wireless LAN drivers. For Intel cards this results in working LED, more sensitive reception, increased stability of connections and some 802.1x bugfixes.
*Out-of-the-box Suspend to RAM functionality (also faster resume).
*Working but slow Suspend to Disk functionality.
== Bugs and Regressions ==
*Hard radio killswitch (at the front) cannot bring WLAN back up after killing it. (workaround available)
*X hangs for approx. 35 seconds when restarting or logging out. (workaround available)
*Atheros WLAN not working after resume from Suspend to RAM (but a workaround is available; [[#Wireless_not_working_after_resume_.28Atheros.29|see above]]).

[[Category:T61p]]
[[Category:Ubuntu]]
[[Category:Ubuntu 8.10]]

Install Ubuntu Intrepid Ibex on a T61p

2009-01-18T15:31:33Z

Trampas: /* Other Problems */

=What works out of the box?=
*Wireless (Intel 3945ABG or 4965AGN)
**Only tested G mode
*Wired LAN
*Video (VESA)
**Hardware Drivers panel offers to install nVIDIA proprietary drivers on first boot.
*Touchpoint and Trackpad
**Including scroll at the right side of the pad by default.
**Middle-button scrolling does NOT work (fix below)
*Optical drive
**Optiarc AD-7910A works fine with Brasero disc burning
***Tested: CD-R, DVD+R
*Sound card
*SD/MMC Memory card reader (Ricoh)
**Only tested SD (non-HC) cards.
*Control buttons/Hotkeys
**Volume control buttons
**Screen brightness control
**Thinklight control
**WLAN/BT/OFF toggle
**Media player control
**fingerprint reader does NOT work (fix below)
*Some ACPI features
**Battery status, power graphs and history
**Lid states and events
**Only tested with a single 6-cell battery
*ACPI features
** Suspend to RAM
** Suspend to Disk (Hibernate) FINALLY!! Be patient, though.
** STR and STD work even with full disk encryption (DM-crypt + LVM)!

=Getting the hardware to work=
==Display/Video==
Installing the proprietary NVidia drivers is highly recommended, EVEN IF you won't use 3D acceleration, because the open source nv driver will drain your battery much faster since it does not support PowerMizer at all. Practically, this means that the GPU will constantly run at full speed, thus consuming ~12 Watts more than it would otherwise (which is a LOT of power for a laptop).

The first time you boot Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at

System --> Administration --> Hardware Drivers.

You will have a choice between the 173 and 177 version of the driver.
*pro:
**Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not.
*con:
**version 177 causes a log out bug that is addressed below.
**version 177 might show some issues like terminal output not updating in some very weird cases (which I did not see in v173, this seems to have something to do with powermizer as well ...)

Once the proprietary drivers are installed, the "NVidia X Server Settings" program will be available in System --> Administration.

===Version 177 logout/X restart fix===
There is a known issue in the v177 proprietary NVidia driver - See Launchpad bug [http://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-177/+bug/258357 258357]. Once you install the v177 driver, logging out or restarting X will cease to work, though suspend to RAM/Disk will continue to function.

The work around is as follows:
* In /etc/gdm/gdm.conf , increase the value for GdmXserverTimeout to about 60. When logging out or restarting X, X will hang for ~35 seconds. By increasing the value from its default, GDM will give X more time before it assumes X is faulty.

===Choppy Compiz animations===
NVidia's PowerMizer feature will slow down the GPU when "inactive" even on AC power.

The NVidia driver does not report the correct refresh rate of the display to Compiz, resulting in choppy animations and effects. To fix this, install the <code>compizconfig-settings-manager</code> package, then go to System --> Preferences --> Advanced Desktop Effects Settings (also might be called CompizConfig Settings Manager). Click on General Options, go to the Display Settings tab, uncheck the Detect Refresh rate box and drag the Refresh Rate slider to 60. Also, check the Sync To VBlank box. This will improve the smoothness of the window animations significantly if you're sensitive to the choppy animations.

Compiz animations can also be choppy due to NVidia's PowerMizer feature, which slows down the GPU to conserve power when it is not in use. This works well for 3D games which constantly use 3D acceleration, but poorly for Compiz which uses the GPU in small bursts. It seems that the interval of the PowerMizer is way too long and is not speeding up when using in bursts. Fortunately, the situation seems to have improved in version 177 of the NVidia driver. To workaround this problem, I made a couple of shell scripts which keep the GPU at its highest speed while running on AC power. The first one is named "powermizer-loop" and does most of the work:

#!/bin/sh

while true; do

powerstate=`cat /proc/acpi/ac_adapter/AC/state | awk '{print $2}'`

if [ $powerstate = "on-line" ]; then
nvidia-settings -q all > /dev/null
fi
sleep 25;
done

The second is named "powermizer-off" and starts up powermizer-loop when I log in, ensuring that only one copy runs at a time:

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

I put both of these scripts in my home directory and made them executable by doing:

chmod a+x powermizer-loop powermizer-off

Then to make powermizer-off run on login, I opened System --> Preferences --> Sessions, clicked on Add, and entered the command to run the script, i.e. "/home/<user>/powermizer-off".

Of course, performance still suffers when running on battery, but hopefully NVidia will fix this problem in a future version of their driver.

=== EDID misdetection ===

EDID (Extended Display Identification Data) might be misdetected for your display, which reduces the number of resolutions available in the NVidia X Server Settings application. (For example, I was unable to set my laptop's screen to 1024x768 for use with a projector during a presentation.) If you encounter this problem, add the following lines to /etc/X11/xorg.conf in the "Screen" section:

Option "UseEdidFreqs" "FALSE"
Option "HorizSync" "40-70"

The 40-70 values are just an example. They seem to work well with my 1680x1050 display. You should put the values of your display there. On a 1920x1200 display, making this change prevents the display from coming on when X starts.

A better but more complicated way would be using Phoenix EDID Designer to dump and fix the EDID data and then setup the Nvidia driver so it will use the customized EDID data, as described at [http://myricci.com/index.php?option=com_content&task=view&id=36]

==Microphone/Sound In==
Might need to be turned on in the mixer. See [[Install Ubuntu Hardy Heron on a T61p#Internal Microphone/Microphone Input Jack]]

==Front radio kill switch==
When killing Wireless LAN with the killswitch at the front, you won't be able to get WLAN back up after switching back. See Launchpad bugs [http://bugs.launchpad.net/ubuntu/+source/hal/+bug/289286 289286] and [http://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.24/+bug/193970 193970] and the [https://wiki.ubuntu.com/IntrepidReleaseNotes#Cannot%20reactivate%20Intel%203945/4965%20wireless%20if%20booting%20with%20killswitch%20enabled Release Notes] on the Ubuntu Wiki.

This will be solved in intrepid-updates eventually.

For now there are a few ways to bring the interface back up (choose one):
* Right click the network manager icon in the tray, uncheck Enable Wireless, then check it again does the trick (at least for me)
* {{cmdroot|ip l s wlan0 up}}
* {{cmdroot|modprobe -r iwl3945 && modprobe iwl3945}}
* reboot
* suspend and resume

== Middle-button Scrolling ==
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.

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

{{cmduser| sudo gedit /etc/hal/fdi/policy/mouse-wheel.fdi}}

Paste and save the following code, which will give vertical wheel emulation only:
<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>
There is [http://psung.blogspot.com/2008/09/scrolling-with-thinkpads-trackpoint-in.html another method] to get horizontal scrolling as well, but this is not confirmed to work.

source:
*[[Installing_Ubuntu_8.10_%28Intrepid_Ibex%29_on_a_ThinkPad_T61#Emulate_Wheel_.28Middle-click_scrolling.29| Installing Ubuntu 8.10 (Intrepid Ibex) on a ThinkPad T61 - Emulate Wheel (Middle-click scrolling)]]

==Fingerprint Reader==

The [http://thinkfinger.sourceforge.net Thinkfinger] package allows you to swipe a finger in most places where you would have to type your password. This works with sudo, gksudo and on the login page and with a little fix also for the screen saver. Also, you are still required to type your user name on the login screen.

0) Set up the third party repository (optional but recommended!)

due to this [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 Bug #256429: Carriage-return required after finger scan] you need to press the return key after you swipe your finger with the current version of the kernel and the packages in ubuntu. The bug is caused by the fact that it does not recognize the fingerprint reader 100% correctly ([https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429/comments/29 Description of the root cause]) , as a temporary workaround there is a special package repository.

The packages present in ubuntu intrepid will work but you need to press enter after you swipe your finger.

Click System -> administration -> software sources
go to the tab "third-party software" and click Add ...

Enter in the popup window:

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

Click Add source, it will ask to refresh the package list, click reload.

1) Install the following packages:

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

2) For your user:

{{cmduser| sudo tf-tool --acquire && sudo tf-tool --verify}}

A completed fingerprint setup should look something like this:

frank@Laptop:~$ sudo tf-tool --acquire && sudo tf-tool --verify

ThinkFinger 0.3 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>

Initializing... done.
Please swipe your finger (successful swipes 3/3, failed swipes: 0)... done.
Storing data (/tmp/test.bir)... done.

ThinkFinger 0.3 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>

Initializing... done.
Please swipe your finger (successful swipes 1/1, failed swipes: 0)... done.
Result: Fingerprint does match.
frank@CLaptop:~$

This will store your fingerprint information in /home/$USERNAME/.thinkfinger.bir

You should do this step for each user who wants to use the fingerprint reader

3) Enable use of reader for authentication:

{{cmduser| sudo gedit /etc/pam.d/common-auth}}

add
auth sufficient pam_thinkfinger.so
before the line which contains pam_unix.so and add
try_first_pass
to the end of the line containing pam_unix.so.

So it should look something like this:
...
auth sufficient pam_thinkfinger.so
auth [success=1 default=ignore] pam_unix.so nullok_secure try_first_pass
...

4) Check uinput kernel module:

{{cmduser|lsmod | grep uinput}}
If the output starts with uinput, then you're done.
If you don't get any output, then it needs to be started and set to start on boot.

Start uinput:

{{cmduser|sudo modprobe uinput}}

Start on boot:

{{cmduser|sudo gedit /etc/modules}}

make sure there is a line like this or add it at the bottom:
uinput

5) Enabling thinkfinger for gnome-screensaver

*create this file:
{{cmduser|sudo gedit /etc/udev/rules.d/60-thinkfinger.rules}}
with this contents:
#
# 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/Install_Ubuntu_Intrepid_Ibex_on_a_T61p#Fingerprint_Reader
# which was taken and modified from:
# http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
# 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"

*Make the group:
{{cmduser|sudo groupadd fingerprint}}
*per user:
{{cmduser|sudo gpasswd -a $USERNAME fingerprint && sudo chown $USERNAME:root /home/$USERNAME/.thinkfinger.bir }}

Reboot your laptop and you should be ready to swipe!

Sources:
* [[Install_Ubuntu_Gutsy_Gibbon_on_a_T61p#Fingerprint_Reader| Install Ubuntu Gutsy Gibbon on a T61p]]
* [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 Bug #256429: Carriage-return required after finger scan] & [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429/comments/21 Solution for the bug in the comments]
* [https://launchpad.net/~jon-oberheide/+archive Repository for the third party fix] credits to [https://launchpad.net/~jon-oberheide Jon Oberheide]
* [[How_to_enable_the_fingerprint_reader_with_ThinkFinger| General page about Fingerprint reader with thinkfinger]] & [[How_to_enable_the_fingerprint_reader_with_ThinkFinger#xscreensaver.2Fgnome-screensaver| Specific gnome-screensaver section]]

==Hard Drive Active Protection System (APS ~ HDAPS)==
Please add to this section

Some interesting links:
* [[Active_Protection_System| Description of APS]]
* [[How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS]]
* [[Tp_smapi| tp_smapi kernel modules]]

=Other Problems=
== Black Screen on Resume ==
On the 6459CTO with default 8.10 install suspend did not work. Installing the proposed updated fixed the problem. To do this add the following line to /etc/apt/sources.list

deb http://us.archive.ubuntu.com/ubuntu/ intrepid-proposed restricted main universe multiverse

== Wireless not working after resume (Atheros) ==
After resuming from suspend, I am unable to reconnect to my wireless network. Network Manager asks me for my password over and over again but never succeeds in connecting. I'm using the Thinkpad (Atheros) A/B/G wireless card.

To fix this problem, I followed the instructions listed at https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/275692. Specifically, I created a file called /etc/pm/config.d/01-modules and put the following line in it:

SUSPEND_MODULES="ath_pci"

== Brightness control on battery power ==
By default, when unplugging the AC power while the system is running, the brightness of the display goes down even when you have set not to in the Power Management settings and you are not able to reach a brightness level as high as possible when connected to AC power. This is not a software setting or GNOME bug, but a BIOS setting. In the BIOS you can find a brightness setting in the Power section. Set it to high for normal, expected behavior. You can let the GNOME Power Manager still lower the brightness, but you will be able to increase it when needed.

=Other Information=
== Saving power ==
Some nice information on power saving you can find at

http://www.lesswatts.org

A tool that allows you to test most tips and tricks to reduce power is powertop, you can install it using

{{cmduser|sudo apt-get install powertop}}

and run it with:

{{cmduser|sudo powertop}}

For more information see http://www.lesswatts.org/projects/powertop/
== Battery control by tp_smapi ==
You need to load a kernel module first:
sudo modprobe tp_smapi

Now, you will be able to have significantly more control over your battery charging via /sys/devices/platform/smapi.

For example, you could set a threshold value of 90% for charging, preventing the battery from charging all the way in exchange for a reduction in the loss of battery capacity that occurs after multiple cycles.
echo "90" | sudo tee -a /sys/devices/platform/smapi/BAT0/start_charge_thresh
(by default this was set to 86% on my laptop)

View the number of charge cycles your battery has had in its lifetime:
cat /sys/devices/platform/smapi/BAT0/cycle_count

While AC connected, force discharging of your battery:
echo "1" | sudo tee -a /sys/devices/platform/smapi/BAT0/force_discharge

For convenience, you could load the kernel module at boot time by adding it to /etc/modules.
echo "tp_smapi" | sudo tee -a /etc/modules

If you have an Ultrabay battery, you might want to place this [http://forum.thinkpads.com/viewtopic.php?p=433463#p433463 script] into <code>/etc/crontab</code> to keep the Ultrabay battery from being completely discharged to 0%, which permanently damages the battery.
# rolls to BAT0 when remaining capacity on BAT1 is less than 20%. Change .2 if wanted. Swap BAT0 and BAT1 if tp_smapi thinks the ultrabay is BAT0.
awk '{if (/remaining capacity/) left=$3; if (/last full capacity/) full=$4} END {if ((left/full) < .2) system("echo 1 > /sys/devices/platform/smapi/BAT0/force_discharge")}' /proc/acpi/battery/BAT1/*
Remember the script needs root in order to write to the files in <code>/sys/devices/platform/smapi/BAT{0,1}/</code>.

= Compared to Hardy (8.04) =
Why upgrade your T61p to Intrepid or why not? (Specific for T61p)
== Improvements ==
*Ricoh SD card reader now reads read-only SD card. (Tested with Adata 150X 2GB SD card)
*Newer Wireless LAN drivers. For Intel cards this results in working LED, more sensitive reception, increased stability of connections and some 802.1x bugfixes.
*Out-of-the-box Suspend to RAM functionality (also faster resume).
*Working but slow Suspend to Disk functionality.
== Bugs and Regressions ==
*Hard radio killswitch (at the front) cannot bring WLAN back up after killing it. (workaround available)
*X hangs for approx. 35 seconds when restarting or logging out. (workaround available)
*Atheros WLAN not working after resume from Suspend to RAM (but a workaround is available; [[#Wireless_not_working_after_resume_.28Atheros.29|see above]]).

[[Category:T61p]]
[[Category:Ubuntu]]
[[Category:Ubuntu 8.10]]

Installing Ubuntu 7.04 Feisty Fawn on a ThinkPad T60p

2007-08-02T12:36:26Z

Trampas: /* T60p Hardware setups */

= Installing Unbuntu Feisty Fawn =

'''THIS IS A DRAFT WRITTEN FROM MEMORY AND HAVE NOT BEEN VERIFIED YET.'''

== The long, but easy way ==
* Install earlier version of Ubuntu (6.06/6.10) and dist-upgrade. If you start from 6.06 you will have to upgrade to 6.10, and then upgrade to 7.04.

== The fast way ==
* Be sure to have a *wired* network connection ready (wifi will not work yet)
* Download a ubuntu 7.04 feisty fawn image from ubuntu.com
* Boot from the CD, and wait ... the installation will break down when attempting to start the graphical part of the installation (X).
The problem is, that the ATI driver required for X is not working. Luckily it is already in the ubuntu repos, so we just install it temporarily (in RAM), so we can get on with the installation. When you have a console prompt, do a:
apt-get update
apt-get install xorg-driver-fglrx fglrx-control
depmod -a
then restart X with:
/etc/init.d/gdm restart
With any luck X should launch, so you can click on the desktop icon and continue the installation.

If X doesn't launch, try changing the Driver in /etc/X11/xorg.conf from "vesa" to "fglrx", then restart X.

= T60p Hardware setups =

'''THIS IS A DRAFT WRITTEN FROM MEMORY AND HAVE NOT BEEN VERIFIED YET.'''
* The t60p uses an Atheros network device with this signature "Atheros Communications, Inc. Unknown device 0024 (rev 01)". It will work with any [[Madwifi]] driver version later than subversion revision '''2360'''. This means that the madwifi included in Feisty Fawn will *NOT* work. Either get a newer release (when available), or build from SVN.
* The fans are too noisy and can be throttled down by using the [[ACPI fan control script]]. Increase the min and max to 70, 100 on the GPU. This will lower the fan speed to <3000 for normal usage (XGL/Compiz fusion setup).
* You should install a 'generic' kernel i favor of the i386 to gain better performance of the dual core, and better suspend.
* Compiz fusion (previously compiz and beryl) will run smoothly of this hardware, using ATI's fglrx and XGL. Use trevinos repository [http://ubuntuforums.org/showthread.php?t=481314 http://ubuntuforums.org/showthread.php?t=481314]

NOTE July 2007 I tried the instructions for Compiz and to date was unable to get it working on the T60p, if anyone has some better instructions please update them here.

* You can tweak the 'fn' keys to work well too.

Installing Fedora 7 on a ThinkPad T60

2007-07-17T01:29:47Z

Trampas: /* Suspend */

Created by: [[User:spot|TomCallaway]] 09:45, March 20, 2007

===Abstract===

This article describes how I got Fedora 7 installed on my IBM/Lenovo ThinkPad T60. Now, I know that Fedora 7 isn't out yet, so this information is specific to the test releases. When Fedora 7 comes out, I'll update this page to reflect any changes.

===My ThinkPad===

These are the specifications of my machine.

* Lenovo ThinkPad T60 (6369-CTO)
* [[Intel Core 2 Duo (Merom)]] T7200 @ 2.00GHz
* [[Intel Graphics Media Accelerator 950]]
* [[Ethernet Controllers#Intel Gigabit (10/100/1000)|Intel Gigabit Ethernet Controller]]
* [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter]]
* Integrated Bluetooth.
* [[Integrated Fingerprint Reader]]
* 100 GB - Serial ATA-150 Hard Drive.
* 15.4" TFT display with 1680x1050 resolution (widescreen)
* Intel 82801G (ICH7 Family) High Definition Audio Controller (rev 02)

===What Works?===

* Fedora
* Most of the function keys, except the ones mentioned below
* The fingerprint reader.
* Video, 2D and 3D.
* Brightness, Volume and Mute with OSD (On-Screen Display).
* ThinkLight, TrackPoint II and the touchpad.
* Bluetooth
* Infrared
* Suspend

===What Doesn't Work? (Known Issues)===

* Modem
* Hibernate

===Kernel Drivers===

The laptop uses the following hardware specific kernel drivers:

* iwlwifi (wireless)
* e1000 (ethernet)
* snd_hda_intel (sound)
* nsc_ircc (infrared)

===Installing Fedora===

I really have no interest in dual-booting my laptop. There are plenty of good guides to setting up a computer for dual-boot on the internet. I burned a copy of the FC 6.91 DVD iso, booted off of it, and told the installer to delete all existing partitions. The install went off without a hitch. After installation, I ran yum update, and rebooted into the new kernel.

===Post Install===
The Fedora repositories have some useful packages for ThinkPads. After I installed the OS, I used yum to install the following packages:

* thinkfinger: Support for the Fingerprint Reader
* tpb: ThinkPad button support utility and onscreen display
* beryl-gnome: Eyecandy!
* iwlwifi-firmware: The firmware for the new intel wireless driver
* xbindkeys: A utility to help us bind the "special" thinkpad keys
* xorg-x11-drv-i810: Driver for the Intel Graphics Chipsets

===Wireless LAN===
The latest Fedora 7 kernels include a new driver for the Intel 3945 chipset, called iwlwifi. This driver works, but it is a bit new, so you must be patient with it. If you didn't install the iwlwifi-firmware package, do so now. The kernel should have detected the wireless device, and configured iwlwifi for you.

Step 1: Turn on the radio
Make sure the switch on the front is pushed to the right (you should be able to see green on the left). Then, as root, run:

: {{cmdroot| /sbin/ifconfig wlan0 up}}

Step 2: Scan for access points
Even if you know the ESSID, the iwlwifi driver needs to also be told the frequency and access point that you want to connect to. Hopefully, this will be fixed in a later revision of the driver.

As root, run:
: {{cmdroot| /sbin/iwlist wlan0 scanning}}

You should see something like:

<pre>
Cell 03 - Address: 00:01:02:03:04:05
ESSID:"freewifi"
Mode:Master
Frequency:2.462 GHz
Signal level=-80 dBm
Encryption key:on
Extra:tsf=000000deadb33fabc
Extra:bcn_int=100
Extra:rssi=-80
Extra:capab=0x0411
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
</pre>

Assuming that's the AP we want to connect to, note the Frequency, Address, and ESSID.

Step 3: Tell wlan0 about our AP
Now, we just need to configure wlan0 to find our AP:
As root, run:

: {{cmdroot| /sbin/iwconfig wlan0 freq 2.462G}}
: {{cmdroot| /sbin/iwconfig wlan0 ap 00:01:02:03:04:05}}
: {{cmdroot| /sbin/iwconfig wlan0 essid "freewifi"}}

Step 4: Get an IP Address
Assuming the wireless network is DHCP, as root, run:

: {{cmdroot| /sbin/dhclient wlan0}}

Now your wireless is up and running!
(Note: Your mileage may vary. There are lots of bug reports against iwlwifi. Maybe it is only a problem with NetworkManager, but my experience is that Fedora 7 test 4 (6.93) has unworkable wifi out of the box, at least on a T60p with an ipw3945.)
As of 15 June 2007, NetworkManager still doesn't work very well with the iwlwifi device.
There is a discussion on this on the fedora test list, starting with
https://www.redhat.com/archives/fedora-test-list/2007-April/msg00539.html

===Bluetooth===
Bluetooth works out of the box, but Gnome GUI only provides limited functionality (like Obex file transfers).
To configure bluetooth serial ports (those are used to connect to internet via Your bluetooth enabled mobile phone, to use bluetooth GPS devices etc), You have to manually tweak {{path|/etc/bluetooth/rfcomm.conf}} file.

At first run:
: {{cmduser| hcitool scan}}

The output should be something like
<pre>
Scanning ...
00:0A:D9:ED:89:4E Anttix P900
</pre>

Note the MAC address of Your phone, then run:
: {{cmduser| sdptool browse MAC_ADDRESS_OF_YOUR_PHONE}}

Find modem channel by looking for an entry like this:
<pre>
Service Name: Dial-up Networking
Service Description: Dial-up Networking
Service Provider: Sony Ericsson
Service RecHandle: 0x10001
Service Class ID List:
"Dialup Networking" (0x1103)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 7
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Dialup Networking" (0x1103)
Version: 0x0100
</pre>

Now edit {{path|/etc/bluetooth/rfcomm.conf}}.
Uncomment the lines for rfcomm0 and replace MAC and channel numbers with the ones from Your phone.
Also make sure to turn on automatic binding on startup.
The final config will look like this:
<pre>
rfcomm0 {
# Automatically bind the device at startup
bind yes;

# Bluetooth address of the device
device 00:0A:D9:ED:89:4E;

# RFCOMM channel for the connection
channel 7;

# Description of the connection
comment "My GSM Dialup Networking";
}
</pre>

Restart bluetooth subsystem:

{{cmdroot|service bluetooth restart}}

Now run network configuration tool, add a new modem to device {{path|/dev/rfcomm0}} and configure an internet connection as usual. The phone number depends on Your phone make, but most of the time it's <code>*99#</code>. You might also need to add additional modem initialization string <code>AT+cgdcont=1,"IP","internet",,0,0</code> to configure Your GPRS service name.

Make sure that Gnome bluetooth applet is running. If not, run it by typing bluetooth-applet.

Activate the connection. You should be prompted for PIN by both: the phone and the applet. Enter the same number on both sides to pair the connection.

===Infrared===
T60 has an NSC FIR chip. The driver needs to know a Dongle ID so it must be manually configured.

Edit {{path|/etc/modprobe.conf}}, add the following two lines:
<pre>
alias irda0 nsc-ircc
options nsc-ircc dongle_id=0x09
</pre>

Edit {{path|/etc/sysconfig/irda}}:
<pre>
IRDA=yes
DEVICE=irda0
DISCOVERY=yes
</pre>

Start IRDA

{{cmdroot|service irda start}}

If You want IRDA to be enabled during system boot, turn it on like this:

{{cmdroot|chkconfig irda on}}

===Getting the ThinkVantage Buttons to work===

Fedora does not recognize all the ThinkVantage buttons correctly by default. This can be fixed quite easily. Just edit /etc/X11/Xmodmap.

Then paste the following in the file:

<pre>
keycode 234 = XF86Back
keycode 233 = XF86Forward
keycode 159 = XF86Start
keycode 162 = XF86AudioPlay
keycode 164 = XF86AudioStop
keycode 153 = XF86AudioNext
keycode 144 = XF86AudioPrev
keycode 227 = XF86LaunchF
keycode 249 = XF86ZoomIn
</pre>

Save and close the file, then logout and back in again. You can now assign the buttons to do anything you want. For example, use the Back and Forward buttons (next the cursor keys) to flip desktops using the cube effect in Beryl (set this using the Beryl settings manager). You can set most of the other keys using Gnome vis System - Preferences - Keyboard Shortcuts.

For the ThinkVantage and Zoom buttons, I used xbindkeys. Open a terminal and type:

: {{cmduser| xbindkeys --defaults > ~/.xbindkeysrc}}
: {{cmduser| xbindkeys-config}}

Click "New" and assign a remark to the new shortcut. Then press "Grab" and press the combination you want (ex: The ThinkVantage button). You can then set the action you want executed in the "Action" field.

=== Video Drivers ===

====Intel Graphics Media Accelerator 950 (GMA950)====
Since the Fedora installer didn't detect the graphics device properly, it uses the Vesa driver. Which works, but that's not really what we want to use. After installing the xorg-x11-drv-i810 package, I edited the /etc/X11/xorg.conf, and changed the driver from "vesa" to "intel". Then, restart X. That's it.

====ATI Mobility Radeon X1300 (M52) & X1400 (M54)====
At this moment, ATI's drivers do not work with Fedora 7 because they can't handle the xorg version there. A fix might be available sometime in June 2007.

===The Fingerprint Reader===

Thanks to the efforts of the ThinkFinger guys, the fingerprint reader works very well in Linux using entirely Free Software. After installing thinkfinger, you need to edit /etc/pam.d/system-auth as root (be careful!):

Above the line that reads:

<pre>
auth sufficient pam_unix.so nullok try_first_pass
</pre>

Add a new line that reads:

<pre>
auth sufficient pam_thinkfinger.so
</pre>

So, the auth section of your /etc/pam.d/system-auth file should look like:

<pre>
auth required pam_env.so
auth sufficient pam_thinkfinger.so
auth sufficient pam_unix.so nullok try_first_pass
auth requisite pam_succeed_if.so uid >= 500 quiet
auth required pam_deny.so
</pre>

Save the updated /etc/pam.d/system-auth, then as root, run:

: {{cmdroot| /usr/sbin/tf-tool --add-user spot}}

Of course, if your username isn't spot, change it! It will prompt you to swipe your finger over the reader three times.

Thats it! Now, you can login using either a password or a fingerprint.

===Beryl - eyecandy===
Beryl is shiny desktop eyecandy. To get it running, you can follow the steps here:
http://wiki.beryl-project.org/wiki/Install/Fedora_Core

===Suspend===
Create a new file {{path|/etc/rc.modules}} and put the following lines into it:
<pre>
# Turn on correct suspend flags for T60
echo 3 > /proc/sys/kernel/acpi_video_flags
</pre>
Then make it executable:

{{cmdroot|chmod 755 /etc/rc.modules}}

After reboot the machine should suspend and wake up fine.

NOTE: I have tried the above with FC7 and T60p and still have not gotten suspend to work. It worked out of the box on FC6. I have also added the following lines to the kernel parameters but with no luck. pci=noacpi acpi_sleep=s3_bios,s3_mode.

===Thanks===
Much credit goes to [[User:Keithvassallo|Keithvassallo]] for his [http://thinkwiki.org/wiki/Installing_Ubuntu_6.10_%28Edgy_Eft%29_on_a_ThinkPad_T60 Installing Ubuntu Edgy Eft on the Thinkpad T60] page.

[[Category:T60]]
[[Category:Fedora]]