ThinkWiki - User contributions [en]

Installing Ubuntu 9.10 (Karmic Koala) on a ThinkPad T61p

2009-11-03T00:26:50Z

Ghosty: /* Battery control by tp_smapi */

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=
==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-03T00:24:32Z

Ghosty: â†Created page with 'Tested with new installation of Ubuntu Karmic Koala 64 bit =Getting the hardware to work= ==Fingerprint Reader== The [http://thinkfinger.sourceforge.net Thinkfinger] pac...'

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 a kernel module first:
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=
==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 ... :-(

Installation instructions for the ThinkPad T61p

2009-11-03T00:00:52Z

Ghosty: /* Ubuntu */

The links on this page are specific for installing distributions on the T61p

=== Debian ===
* [[Installing_Debian_lenny_on_a_ThinkPad_T61p | Debian Lenny]]
* [http://www.klabs.be/~fpiat/linux/debian/Etch_on_Thinkpad_T61.html Debian Etch], 2007-05-22

=== Fedora ===
* [[Installing_Fedora_7_on_a_ThinkPad_T61p | Fedora 7]]
* [[Installing_Fedora_8_on_a_ThinkPad_T61p | Fedora 8]]

=== Gentoo ===
* [http://schlitt.info/applications/blog/index.php?/archives/563-My-now-notebook.html Migrating Gentoo from T43p to T61p], 2007-09-27

=== OpenSUSE ===
* [[Installing OPENSUSE 10.3 on a ThinkPad T61p | OpenSUSE 10.3]]
* [[Installing OPENSUSE 11.0 on a ThinkPad T61p | OpenSUSE 11.0]]
* [[Installing OPENSUSE 11.1 on a ThinkPad T61p | OpenSUSE 11.1]]

=== Ubuntu ===
* [[Installing_Ubuntu_7.04_(Feisty_Fawn)_on_a_ThinkPad_T61 | 7.04 (Feisty Fawn)]]
* [[Install Ubuntu Gutsy Gibbon on a T61p | 7.10 (Gutsy Gibbon)]]
* [[Install Ubuntu Hardy Heron on a T61p | 8.04 (Hardy Heron)]]
* [[Install Ubuntu Intrepid Ibex on a T61p | 8.10 (Intrepid Ibex)]]
* [[Installing Ubuntu 9.04 (Jaunty Jackalope) on a ThinkPad T61p | 9.04 (Jaunty Jackalope)]]
* [[Installing Ubuntu 9.10 (Karmic Koala) on a ThinkPad T61p | 9.10 (Karmic Koala)]]

=== Other ===
* [http://lists.2rosenthals.com/ecs-t6x/List.html T61 eComStation (OS/2) Mailing List archives ]

(Note that the following categories applies to T60, They might also apply to T61 (test and update the list, please) : Thermal_Sensors Tp_smapi Table_of_ibm-acpi_LEDs Swsusp Software_Suspend_2 Rescue_and_Recovery Problems_with_SATA_and_Linux Problem_with_video_output_switching Problem_with_fan_noise Problem_with_high_pitch_noises How_to_control_fan_speed Embedded_Controller_Firmware

[[Category:T61p]]

Install Ubuntu Intrepid Ibex on a T61p

2008-12-21T17:37:45Z

Ghosty: /* Fingerprint Reader */

=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 compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. 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

==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=
== 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 (this should help against the loss of capacity through charging cycles). This functionality is similar to Windows Vista power management nowadays.
echo "90" | sudo tee -a /sys/devices/platform/smapi/BAT0/start_charge_thresh
(by default this was set to 86% on my laptop)

WARNING: before this entry said to use 90% for stop_charge_thresh, but this seems to have the adverse effect, that your battery only charges up to 90%!

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

= 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

2008-12-21T17:29:28Z

Ghosty: /* Fingerprint Reader */

=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 compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. 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

==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 pam_unix.so line and
try_first_pass
to the end of the pam_unix.so line.

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"

*edit the file:
{{cmduser|sudo gedit /etc/pam.d/gnome-screensaver}}
so it looks like this:
@include common-auth
auth sufficient pam_thinkfinger.so
auth optional pam_gnome_keyring.so

*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=
== 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 (this should help against the loss of capacity through charging cycles). This functionality is similar to Windows Vista power management nowadays.
echo "90" | sudo tee -a /sys/devices/platform/smapi/BAT0/start_charge_thresh
(by default this was set to 86% on my laptop)

WARNING: before this entry said to use 90% for stop_charge_thresh, but this seems to have the adverse effect, that your battery only charges up to 90%!

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

= 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

2008-12-21T17:06:20Z

Ghosty: /* Battery control by tp_smapi */

=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 compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. 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

==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 pam_unix.so line and
try_first_pass
to the end of the pam_unix.so line.

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"

*edit the file:
{{cmduser|sudo gedit /etc/pam.d/gnome-screensaver}}
so it looks like this:
@include common-auth
auth sufficient pam_thinkfinger.so
auth optional pam_gnome_keyring.so
auth required pam_unix.so try_first_pass nullok_secure

*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=
== 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 (this should help against the loss of capacity through charging cycles). This functionality is similar to Windows Vista power management nowadays.
echo "90" | sudo tee -a /sys/devices/platform/smapi/BAT0/start_charge_thresh
(by default this was set to 86% on my laptop)

WARNING: before this entry said to use 90% for stop_charge_thresh, but this seems to have the adverse effect, that your battery only charges up to 90%!

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

= 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

2008-12-21T17:05:49Z

Ghosty: /* Battery control by tp_smapi */

=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 compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. 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

==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 pam_unix.so line and
try_first_pass
to the end of the pam_unix.so line.

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"

*edit the file:
{{cmduser|sudo gedit /etc/pam.d/gnome-screensaver}}
so it looks like this:
@include common-auth
auth sufficient pam_thinkfinger.so
auth optional pam_gnome_keyring.so
auth required pam_unix.so try_first_pass nullok_secure

*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=
== 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 (this should help against the loss of capacity through charging cycles). This functionality is similar to Windows Vista power management nowadays.
echo "90" | sudo tee -a /sys/devices/platform/smapi/BAT0/start_charge_thresh
(by default this was set to 86% on my laptop)

WARNING: before this entry said to use 90% for stop_charge_thresh, but this seems to have the adverse effect, that your battery only charges up to 90%!

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

Or, 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

= 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

2008-12-15T03:07:16Z

Ghosty: /* Battery control by tp_smapi fixed typo */

=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 compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. 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

==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 pam_unix.so line and
try_first_pass
to the end of the pam_unix.so line.

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"

*edit the file:
{{cmduser|sudo gedit /etc/pam.d/gnome-screensaver}}
so it looks like this:
@include common-auth
auth sufficient pam_thinkfinger.so
auth optional pam_gnome_keyring.so
auth required pam_unix.so try_first_pass nullok_secure

*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=
== 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 (this should help against the loss of capacity through charging cycles).
echo "90" | sudo tee -a /sys/devices/platform/smapi/BAT0/stop_charge_thresh

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

Or, 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

= 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

2008-12-15T02:58:06Z

Ghosty: small changes to the battery recharge info with tp_smapi

=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 compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. 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

==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 pam_unix.so line and
try_first_pass
to the end of the pam_unix.so line.

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"

*edit the file:
{{cmduser|sudo gedit /etc/pam.d/gnome-screensaver}}
so it looks like this:
@include common-auth
auth sufficient pam_thinkfinger.so
auth optional pam_gnome_keyring.so
auth required pam_unix.so try_first_pass nullok_secure

*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=
== 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 (this should help against the loss of capacity through charging cycles).
echo "90" | sudo tee -a /sys/devices/platform/smapi/BAT0/stop_charge_thresh

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

Or, 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

= 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

2008-11-14T04:00:22Z

Ghosty:

=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 compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. 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

==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 pam_unix.so line and
try_first_pass
to the end of the pam_unix.so line.

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"

*edit the file:
{{cmduser|sudo gedit /etc/pam.d/gnome-screensaver}}
so it looks like this:
@include common-auth
auth sufficient pam_thinkfinger.so
auth optional pam_gnome_keyring.so
auth required pam_unix.so try_first_pass nullok_secure

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

= 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

2008-11-14T03:55:34Z

Ghosty: /* What works out of the box? */

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

==Microphone/Sound In==
Might need to be turned on in the mixer

==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 pam_unix.so line and
try_first_pass
to the end of the pam_unix.so line.

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"

*edit the file:
{{cmduser|sudo gedit /etc/pam.d/gnome-screensaver}}
so it looks like this:
@include common-auth
auth sufficient pam_thinkfinger.so
auth optional pam_gnome_keyring.so
auth required pam_unix.so try_first_pass nullok_secure

*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=
==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 compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. 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.

==Logging out or restarting X==
See the Display setup section for how to work around this problem.

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

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

=Other Information=
== 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.
== 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/

= 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

2008-11-14T03:51:13Z

Ghosty: /* Getting the hardware to work */

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

==Microphone/Sound In==
Might need to be turned on in the mixer

==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 pam_unix.so line and
try_first_pass
to the end of the pam_unix.so line.

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"

*edit the file:
{{cmduser|sudo gedit /etc/pam.d/gnome-screensaver}}
so it looks like this:
@include common-auth
auth sufficient pam_thinkfinger.so
auth optional pam_gnome_keyring.so
auth required pam_unix.so try_first_pass nullok_secure

*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=
==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 compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. 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.

==Logging out or restarting X==
See the Display setup section for how to work around this problem.

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

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

=Other Information=
== 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.
== 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/

= 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

2008-11-14T03:32:06Z

Ghosty: /* Getting the hardware to work */

=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.
*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
*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. Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not. However, 177 causes a log out bug that is addressed below.

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 increased the value from its default, GDM will give X more time before it assumes X is faulty.

==Microphone/Sound In==
Might need to be turned on in the mixer

==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 pam_unix.so line and
try_first_pass
to the end of the pam_unix.so line.

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"

*edit the file:
{{cmduser|sudo gedit /etc/pam.d/gnome-screensaver}}
so it looks like this:
@include common-auth
auth sufficient pam_thinkfinger.so
auth optional pam_gnome_keyring.so
auth required pam_unix.so try_first_pass nullok_secure

*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=
==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 compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. 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.

==Logging out or restarting X==
See the Display setup section for how to work around this problem.

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

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

=Other Information=
== 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.
== 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/

= 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

2008-11-14T03:30:22Z

Ghosty: /* Middle-button Scrolling */

=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.
*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
*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. Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not. However, 177 causes a log out bug that is addressed below.

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 increased the value from its default, GDM will give X more time before it assumes X is faulty.

==Microphone/Sound In==
Might need to be turned on in the mixer
==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]]

==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 pam_unix.so line and
try_first_pass
to the end of the pam_unix.so line.

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"

*edit the file:
{{cmduser|sudo gedit /etc/pam.d/gnome-screensaver}}
so it looks like this:
@include common-auth
auth sufficient pam_thinkfinger.so
auth optional pam_gnome_keyring.so
auth required pam_unix.so try_first_pass nullok_secure

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

=Other Problems=
==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 compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. 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.

==Logging out or restarting X==
See the Display setup section for how to work around this problem.

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

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

=Other Information=
== 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.
== 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/

= 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

2008-11-14T03:28:55Z

Ghosty: /* Front radio kill switch */

=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.
*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
*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. Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not. However, 177 causes a log out bug that is addressed below.

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 increased the value from its default, GDM will give X more time before it assumes X is faulty.

==Microphone/Sound In==
Might need to be turned on in the mixer
==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]]

==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 ==
[http://mvogt.wordpress.com/2008/08/15/xorg-evdev-and-emulatewheel/ Michael Vogt described] how to get middle-click scrolling to work again in Intrepid.
Xorg.conf is not used to configure mice and keyboards anymore, but evdev is. This makes the configuration of middle-click scrolling a little bit different than previous versions of Ubuntu.

Issue:

{{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 pam_unix.so line and
try_first_pass
to the end of the pam_unix.so line.

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"

*edit the file:
{{cmduser|sudo gedit /etc/pam.d/gnome-screensaver}}
so it looks like this:
@include common-auth
auth sufficient pam_thinkfinger.so
auth optional pam_gnome_keyring.so
auth required pam_unix.so try_first_pass nullok_secure

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

=Other Problems=
==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 compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. 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.

==Logging out or restarting X==
See the Display setup section for how to work around this problem.

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

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

=Other Information=
== 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.
== 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/

= 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

2008-11-14T03:28:31Z

Ghosty: /* Front radio kill switch */

=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.
*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
*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. Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not. However, 177 causes a log out bug that is addressed below.

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 increased the value from its default, GDM will give X more time before it assumes X is faulty.

==Microphone/Sound In==
Might need to be turned on in the mixer
==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]]

==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 should do the trick as well (at least for me)
* {{cmdroot|ip l s wlan0 up}}
* {{cmdroot|modprobe -r iwl3945 && modprobe iwl3945}}
* reboot
* suspend and resume

== Middle-button Scrolling ==
[http://mvogt.wordpress.com/2008/08/15/xorg-evdev-and-emulatewheel/ Michael Vogt described] how to get middle-click scrolling to work again in Intrepid.
Xorg.conf is not used to configure mice and keyboards anymore, but evdev is. This makes the configuration of middle-click scrolling a little bit different than previous versions of Ubuntu.

Issue:

{{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 pam_unix.so line and
try_first_pass
to the end of the pam_unix.so line.

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"

*edit the file:
{{cmduser|sudo gedit /etc/pam.d/gnome-screensaver}}
so it looks like this:
@include common-auth
auth sufficient pam_thinkfinger.so
auth optional pam_gnome_keyring.so
auth required pam_unix.so try_first_pass nullok_secure

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

=Other Problems=
==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 compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. 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.

==Logging out or restarting X==
See the Display setup section for how to work around this problem.

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

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

=Other Information=
== 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.
== 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/

= 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

2008-11-14T03:23:39Z

Ghosty: /* Middle-button Scrolling */

=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.
*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
*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. Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not. However, 177 causes a log out bug that is addressed below.

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 increased the value from its default, GDM will give X more time before it assumes X is faulty.

==Microphone/Sound In==
Might need to be turned on in the mixer
==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]]

==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):
* {{cmdroot|ip l s wlan0 up}}
* {{cmdroot|modprobe -r iwl3945 && modprobe iwl3945}}
* reboot
* suspend and resume

== Middle-button Scrolling ==
[http://mvogt.wordpress.com/2008/08/15/xorg-evdev-and-emulatewheel/ Michael Vogt described] how to get middle-click scrolling to work again in Intrepid.
Xorg.conf is not used to configure mice and keyboards anymore, but evdev is. This makes the configuration of middle-click scrolling a little bit different than previous versions of Ubuntu.

Issue:

{{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 pam_unix.so line and
try_first_pass
to the end of the pam_unix.so line.

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"

*edit the file:
{{cmduser|sudo gedit /etc/pam.d/gnome-screensaver}}
so it looks like this:
@include common-auth
auth sufficient pam_thinkfinger.so
auth optional pam_gnome_keyring.so
auth required pam_unix.so try_first_pass nullok_secure

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

=Other Problems=
==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 compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. 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.

==Logging out or restarting X==
See the Display setup section for how to work around this problem.

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

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

=Other Information=
== 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.
== 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/

= 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

2008-11-14T03:19:44Z

Ghosty: /* Middle-button Scrolling */

=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.
*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
*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. Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not. However, 177 causes a log out bug that is addressed below.

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 increased the value from its default, GDM will give X more time before it assumes X is faulty.

==Microphone/Sound In==
Might need to be turned on in the mixer
==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]]

==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):
* {{cmdroot|ip l s wlan0 up}}
* {{cmdroot|modprobe -r iwl3945 && modprobe iwl3945}}
* reboot
* suspend and resume

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

==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 pam_unix.so line and
try_first_pass
to the end of the pam_unix.so line.

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"

*edit the file:
{{cmduser|sudo gedit /etc/pam.d/gnome-screensaver}}
so it looks like this:
@include common-auth
auth sufficient pam_thinkfinger.so
auth optional pam_gnome_keyring.so
auth required pam_unix.so try_first_pass nullok_secure

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

=Other Problems=
==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 compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. 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.

==Logging out or restarting X==
See the Display setup section for how to work around this problem.

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

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

=Other Information=
== 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.
== 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/

= 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

2008-11-11T16:27:39Z

Ghosty: /* Saving power */

=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.
*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
*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. Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not. However, 177 causes a log out bug that is addressed below.

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 increased the value from its default, GDM will give X more time before it assumes X is faulty.

==Microphone/Sound In==
Might need to be turned on in the mixer
==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]]

==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):
* {{cmdroot|ip l s wlan0 up}}
* {{cmdroot|modprobe -r iwl3945 && modprobe iwl3945}}
* reboot
* suspend and resume

== Middle-button Scrolling ==
Please add to this section

==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 pam_unix.so line and
try_first_pass
to the end of the pam_unix.so line.

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"

*edit the file:
{{cmduser|sudo gedit /etc/pam.d/gnome-screensaver}}
so it looks like this:
@include common-auth
auth sufficient pam_thinkfinger.so
auth optional pam_gnome_keyring.so
auth required pam_unix.so try_first_pass nullok_secure

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

=Other Problems=
==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 compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. 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.

==Logging out or restarting X==
See the Display setup section for how to work around this problem.

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

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

=Other Information=
== 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.
== 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/

= 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

2008-11-11T16:26:49Z

Ghosty: /* 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.
*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
*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. Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not. However, 177 causes a log out bug that is addressed below.

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 increased the value from its default, GDM will give X more time before it assumes X is faulty.

==Microphone/Sound In==
Might need to be turned on in the mixer
==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]]

==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):
* {{cmdroot|ip l s wlan0 up}}
* {{cmdroot|modprobe -r iwl3945 && modprobe iwl3945}}
* reboot
* suspend and resume

== Middle-button Scrolling ==
Please add to this section

==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 pam_unix.so line and
try_first_pass
to the end of the pam_unix.so line.

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"

*edit the file:
{{cmduser|sudo gedit /etc/pam.d/gnome-screensaver}}
so it looks like this:
@include common-auth
auth sufficient pam_thinkfinger.so
auth optional pam_gnome_keyring.so
auth required pam_unix.so try_first_pass nullok_secure

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

=Other Problems=
==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 compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. 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.

==Logging out or restarting X==
See the Display setup section for how to work around this problem.

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

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

=Other Information=
== 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.
== 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/

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

User:Ghosty

2008-11-11T14:50:25Z

Ghosty: â†Created page with '== Who is Ghosty?== Linux sysadmin, free and open source sympathiser. == My ThinkPads == Owner of a Thinkpad T61p, running ubuntu on it.'

== Who is Ghosty?==
Linux sysadmin, free and open source sympathiser.

== My ThinkPads ==
Owner of a Thinkpad T61p, running ubuntu on it.

Install Ubuntu Intrepid Ibex on a T61p

2008-11-11T14:38:18Z

Ghosty: /* Hard Drive Active Protection System (HDAPS) */

=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.
*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
*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. Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not. However, 177 causes a log out bug that is addressed below.

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 increased the value from its default, GDM will give X more time before it assumes X is faulty.

==Microphone/Sound In==
Might need to be turned on in the mixer
==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]]

==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):
* {{cmdroot|ip l s wlan0 up}}
* {{cmdroot|modprobe -r iwl3945 && modprobe iwl3945}}
* reboot
* suspend and resume

== Middle-button Scrolling ==
Please add to this section

==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 pam_unix.so line and
try_first_pass
to the end of the pam_unix.so line.

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"

*edit the file:
{{cmduser|sudo gedit /etc/pam.d/gnome-screensaver}}
so it looks like this:
@include common-auth
auth sufficient pam_thinkfinger.so
auth optional pam_gnome_keyring.so
auth required pam_unix.so try_first_pass nullok_secure

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

=Other Problems=
==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 compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. 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.

==Logging out or restarting X==
See the Display setup section for how to work around this problem.

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

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

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

= 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

2008-11-11T00:20:30Z

Ghosty: /* Fingerprint Reader */

=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.
*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
*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. Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not. However, 177 causes a log out bug that is addressed below.

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 increased the value from its default, GDM will give X more time before it assumes X is faulty.

==Microphone/Sound In==
Might need to be turned on in the mixer
==Hard Drive Active Protection System (HDAPS)==
Please add to this section
==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):
* {{cmdroot|ip l s wlan0 up}}
* {{cmdroot|modprobe -r iwl3945 && modprobe iwl3945}}
* reboot
* suspend and resume

== Middle-button Scrolling ==
Please add to this section

==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 pam_unix.so line and
try_first_pass
to the end of the pam_unix.so line.

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"

*edit the file:
{{cmduser|sudo gedit /etc/pam.d/gnome-screensaver}}
so it looks like this:
@include common-auth
auth sufficient pam_thinkfinger.so
auth optional pam_gnome_keyring.so
auth required pam_unix.so try_first_pass nullok_secure

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

=Other Problems=
==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 compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. 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.

==Logging out or restarting X==
See the Display setup section for how to work around this problem.

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

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

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

= 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

2008-11-11T00:16:57Z

Ghosty: /* Fingerprint Reader */

=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.
*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
*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. Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not. However, 177 causes a log out bug that is addressed below.

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 increased the value from its default, GDM will give X more time before it assumes X is faulty.

==Microphone/Sound In==
Might need to be turned on in the mixer
==Hard Drive Active Protection System (HDAPS)==
Please add to this section
==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):
* {{cmdroot|ip l s wlan0 up}}
* {{cmdroot|modprobe -r iwl3945 && modprobe iwl3945}}
* reboot
* suspend and resume

== Middle-button Scrolling ==
Please add to this section

==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 pam_unix.so line and
try_first_pass
to the end of the pam_unix.so line.

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"

*edit the file:
{{cmduser|sudo gedit /etc/pam.d/gnome-screensaver}}
so it looks like this:
@include common-auth
auth sufficient pam_thinkfinger.so
auth optional pam_gnome_keyring.so
auth required pam_unix.so try_first_pass nullok_secure

*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 above 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| Fingerprint reader with gnome-screensaver section]]

=Other Problems=
==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 compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. 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.

==Logging out or restarting X==
See the Display setup section for how to work around this problem.

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

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

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

= 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

2008-11-11T00:16:05Z

Ghosty: /* Fingerprint Reader */

=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.
*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
*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. Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not. However, 177 causes a log out bug that is addressed below.

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 increased the value from its default, GDM will give X more time before it assumes X is faulty.

==Microphone/Sound In==
Might need to be turned on in the mixer
==Hard Drive Active Protection System (HDAPS)==
Please add to this section
==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):
* {{cmdroot|ip l s wlan0 up}}
* {{cmdroot|modprobe -r iwl3945 && modprobe iwl3945}}
* reboot
* suspend and resume

== Middle-button Scrolling ==
Please add to this section

==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 pam_unix.so line and
try_first_pass
to the end of the pam_unix.so line.

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"

*edit the file:
{{cmduser|sudo gedit /etc/pam.d/gnome-screensaver}}
so it looks like this:
@include common-auth
auth sufficient pam_thinkfinger.so
auth optional pam_gnome_keyring.so
auth required pam_unix.so try_first_pass nullok_secure

*Make the group:
{{cmduser|sudo groupadd fingerprint}}
*per user:
{{cmduser|sudo gpasswd -a $USERNAME fingerprint}}
{{cmduser|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 above 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| Fingerprint reader with gnome-screensaver section]]

=Other Problems=
==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 compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. 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.

==Logging out or restarting X==
See the Display setup section for how to work around this problem.

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

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

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

= 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

2008-11-11T00:11:19Z

Ghosty: /* Fingerprint Reader */

=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.
*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
*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. Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not. However, 177 causes a log out bug that is addressed below.

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 increased the value from its default, GDM will give X more time before it assumes X is faulty.

==Microphone/Sound In==
Might need to be turned on in the mixer
==Hard Drive Active Protection System (HDAPS)==
Please add to this section
==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):
* {{cmdroot|ip l s wlan0 up}}
* {{cmdroot|modprobe -r iwl3945 && modprobe iwl3945}}
* reboot
* suspend and resume

== Middle-button Scrolling ==
Please add to this section

==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 pam_unix.so line and
try_first_pass
to the end of the pam_unix.so line.

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"

*edit the file:
{{cmduser|sudo gedit /etc/pam.d/gnome-screensaver}}
so it looks like this:
@include common-auth
auth sufficient pam_thinkfinger.so
auth optional pam_gnome_keyring.so
auth required pam_unix.so try_first_pass nullok_secure

*Make the group:
{{cmduser|sudo groupadd fingerprint}}
*per user:
{{cmduser|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 above 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| Fingerprint reader with gnome-screensaver section]]

=Other Problems=
==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 compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. 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.

==Logging out or restarting X==
See the Display setup section for how to work around this problem.

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

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

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

= 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

2008-11-11T00:10:59Z

Ghosty: /* Fingerprint Reader */

=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.
*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
*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. Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not. However, 177 causes a log out bug that is addressed below.

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 increased the value from its default, GDM will give X more time before it assumes X is faulty.

==Microphone/Sound In==
Might need to be turned on in the mixer
==Hard Drive Active Protection System (HDAPS)==
Please add to this section
==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):
* {{cmdroot|ip l s wlan0 up}}
* {{cmdroot|modprobe -r iwl3945 && modprobe iwl3945}}
* reboot
* suspend and resume

== Middle-button Scrolling ==
Please add to this section

==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 bug [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 pam_unix.so line and
try_first_pass
to the end of the pam_unix.so line.

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"

*edit the file:
{{cmduser|sudo gedit /etc/pam.d/gnome-screensaver}}
so it looks like this:
@include common-auth
auth sufficient pam_thinkfinger.so
auth optional pam_gnome_keyring.so
auth required pam_unix.so try_first_pass nullok_secure

*Make the group:
{{cmduser|sudo groupadd fingerprint}}
*per user:
{{cmduser|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 above 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| Fingerprint reader with gnome-screensaver section]]

=Other Problems=
==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 compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. 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.

==Logging out or restarting X==
See the Display setup section for how to work around this problem.

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

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

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

= 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

2008-11-11T00:06:41Z

Ghosty: /* Fingerprint Reader */

=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.
*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
*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. Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not. However, 177 causes a log out bug that is addressed below.

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 increased the value from its default, GDM will give X more time before it assumes X is faulty.

==Microphone/Sound In==
Might need to be turned on in the mixer
==Hard Drive Active Protection System (HDAPS)==
Please add to this section
==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):
* {{cmdroot|ip l s wlan0 up}}
* {{cmdroot|modprobe -r iwl3945 && modprobe iwl3945}}
* reboot
* suspend and resume

== Middle-button Scrolling ==
Please add to this section

==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 but not with the 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 bug [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 pam_unix.so line and
try_first_pass
to the end of the pam_unix.so line.

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"

*edit the file:
{{cmduser|sudo gedit /etc/pam.d/gnome-screensaver}}
so it looks like this:
@include common-auth
auth sufficient pam_thinkfinger.so
auth optional pam_gnome_keyring.so
auth required pam_unix.so try_first_pass nullok_secure

*Make the group:
{{cmduser|sudo groupadd fingerprint}}
*per user:
{{cmduser|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 above 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| Fingerprint reader with gnome-screensaver section]]

=Other Problems=
==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 compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. 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.

==Logging out or restarting X==
See the Display setup section for how to work around this problem.

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

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

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

= 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

2008-11-11T00:03:21Z

Ghosty: /* Fingerprint Reader */

=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.
*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
*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. Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not. However, 177 causes a log out bug that is addressed below.

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 increased the value from its default, GDM will give X more time before it assumes X is faulty.

==Microphone/Sound In==
Might need to be turned on in the mixer
==Hard Drive Active Protection System (HDAPS)==
Please add to this section
==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):
* {{cmdroot|ip l s wlan0 up}}
* {{cmdroot|modprobe -r iwl3945 && modprobe iwl3945}}
* reboot
* suspend and resume

== Middle-button Scrolling ==
Please add to this section

==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 but not with the 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 bug [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 pam_unix.so line and
try_first_pass
to the end of the pam_unix.so line.

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"

*edit the file:
{{cmduser|sudo gedit /etc/pam.d/gnome-screensaver}}
so it looks like this:
@include common-auth
auth sufficient pam_thinkfinger.so
auth optional pam_gnome_keyring.so
auth required pam_unix.so try_first_pass nullok_secure

*Make the group:
{{cmduser|sudo groupadd fingerprint}}
*per user:
{{cmduser|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 above 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| Fingerprint reader with gnome-screensaver section]]

=Other Problems=
==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 compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. 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.

==Logging out or restarting X==
See the Display setup section for how to work around this problem.

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

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

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

= 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

2008-11-11T00:01:12Z

Ghosty: /* Fingerprint Reader */

=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.
*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
*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. Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not. However, 177 causes a log out bug that is addressed below.

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 increased the value from its default, GDM will give X more time before it assumes X is faulty.

==Microphone/Sound In==
Might need to be turned on in the mixer
==Hard Drive Active Protection System (HDAPS)==
Please add to this section
==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):
* {{cmdroot|ip l s wlan0 up}}
* {{cmdroot|modprobe -r iwl3945 && modprobe iwl3945}}
* reboot
* suspend and resume

== Middle-button Scrolling ==
Please add to this section

==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 but not with the 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 bug [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 pam_unix.so line and
try_first_pass
to the end of the pam_unix.so line.

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"

*edit the file:
{{cmduser|sudo gedit /etc/pam.d/gnome-screensaver}}
so it looks like this:
@include common-auth
auth sufficient pam_thinkfinger.so
auth optional pam_gnome_keyring.so
auth required pam_unix.so try_first_pass nullok_secure

*Make the group:
{{cmduser|sudo groupadd fingerprint}}
*per user:
{{cmduser|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 above 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| Fingerprint reader with gnome-screensaver section]]

=Other Problems=
==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 compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. 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.

==Logging out or restarting X==
See the Display setup section for how to work around this problem.

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

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

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

= 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

2008-11-11T00:00:18Z

Ghosty: /* Fingerprint Reader */

=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.
*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
*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. Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not. However, 177 causes a log out bug that is addressed below.

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 increased the value from its default, GDM will give X more time before it assumes X is faulty.

==Microphone/Sound In==
Might need to be turned on in the mixer
==Hard Drive Active Protection System (HDAPS)==
Please add to this section
==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):
* {{cmdroot|ip l s wlan0 up}}
* {{cmdroot|modprobe -r iwl3945 && modprobe iwl3945}}
* reboot
* suspend and resume

== Middle-button Scrolling ==
Please add to this section

==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 but not with the 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 bug [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 pam_unix.so line and
try_first_pass
to the end of the pam_unix.so line.

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"

*edit the file:
{{cmduser|sudo gedit /etc/pam.d/gnome-screensaver}}
so it looks like this:
@include common-auth
auth sufficient pam_thinkfinger.so
auth optional pam_gnome_keyring.so
auth required pam_unix.so try_first_pass nullok_secure

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

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 above 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| Fingerprint reader with gnome-screensaver section]]

=Other Problems=
==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 compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. 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.

==Logging out or restarting X==
See the Display setup section for how to work around this problem.

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

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

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

= 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

2008-11-10T23:25:10Z

Ghosty: /* Fingerprint Reader */

=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.
*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
*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. Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not. However, 177 causes a log out bug that is addressed below.

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 increased the value from its default, GDM will give X more time before it assumes X is faulty.

==Microphone/Sound In==
Might need to be turned on in the mixer
==Hard Drive Active Protection System (HDAPS)==
Please add to this section
==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):
* {{cmdroot|ip l s wlan0 up}}
* {{cmdroot|modprobe -r iwl3945 && modprobe iwl3945}}
* reboot
* suspend and resume

== Middle-button Scrolling ==
Please add to this section

==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 but not with the the screen saver. Also, you are still required to type your user name on the login screen.

There appears to be a method to make the reader work for the screensaver, but I haven't tested it yet.

See also: [[How_to_enable_the_fingerprint_reader_with_ThinkFinger#Intrepid| How to enable the fingerprint reader with ThinkFinger]]

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

due to this bug [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 here:

https://launchpad.net/~jon-oberheide/+archive

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 pam_unix.so line and
try_first_pass
to the end of the pam_unix.so line.

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

At this point, you should be ready to swipe!

Usage examples:
*At the login prompt: enter your name, when prompted for password swipe your finger (and press enter if you do not have the third party repository!)
*if you want to perform an action with sudo, it will ask for your password, just swipe your finger (and press enter)

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 above in the comments]
* [https://launchpad.net/~jon-oberheide/+archive| Repository for the third party fix] credits to [https://launchpad.net/~jon-oberheide| Jon Oberheide]

=Other Problems=
==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 compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. 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.

==Logging out or restarting X==
See the Display setup section for how to work around this problem.

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

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

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

= 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

2008-11-10T23:24:53Z

Ghosty: /* Fingerprint Reader */

=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.
*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
*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. Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not. However, 177 causes a log out bug that is addressed below.

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 increased the value from its default, GDM will give X more time before it assumes X is faulty.

==Microphone/Sound In==
Might need to be turned on in the mixer
==Hard Drive Active Protection System (HDAPS)==
Please add to this section
==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):
* {{cmdroot|ip l s wlan0 up}}
* {{cmdroot|modprobe -r iwl3945 && modprobe iwl3945}}
* reboot
* suspend and resume

== Middle-button Scrolling ==
Please add to this section

==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 but not with the the screen saver. Also, you are still required to type your user name on the login screen.

There appears to be a method to make the reader work for the screensaver, but I haven't tested it yet.
See also: [[How_to_enable_the_fingerprint_reader_with_ThinkFinger#Intrepid| How to enable the fingerprint reader with ThinkFinger]]

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

due to this bug [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 here:

https://launchpad.net/~jon-oberheide/+archive

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 pam_unix.so line and
try_first_pass
to the end of the pam_unix.so line.

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

At this point, you should be ready to swipe!

Usage examples:
*At the login prompt: enter your name, when prompted for password swipe your finger (and press enter if you do not have the third party repository!)
*if you want to perform an action with sudo, it will ask for your password, just swipe your finger (and press enter)

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 above in the comments]
* [https://launchpad.net/~jon-oberheide/+archive| Repository for the third party fix] credits to [https://launchpad.net/~jon-oberheide| Jon Oberheide]

=Other Problems=
==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 compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. 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.

==Logging out or restarting X==
See the Display setup section for how to work around this problem.

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

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

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

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

Talk:Installing Ubuntu 8.10 (Intrepid Ibex) on a ThinkPad T61

2008-11-10T22:40:04Z

Ghosty:

Have you tried connecting an external monitor? I'm trying to get dual monitor working. I tried enabling it thru nvidia-settings tool, but it didn't work (I think there's a documented bug).

== Missing information: how to activate microphone ==

The text says
Microphone: Just needs to be activated, see section below
But there is no "below" (or #audio, respectively)

== Better description of the fingerprint reader problem ==
I think this will be the same on a T61 (but since i have a T61p i cannot verify, not exactly sure where the differences are!)

http://www.thinkwiki.org/wiki/Install_Ubuntu_Intrepid_Ibex_on_a_T61p#Fingerprint_Reader

Install Ubuntu Intrepid Ibex on a T61p

2008-11-10T22:30:10Z

Ghosty: /* Fingerprint Reader */

=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.
*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
*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. Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not. However, 177 causes a log out bug that is addressed below.

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 increased the value from its default, GDM will give X more time before it assumes X is faulty.

==Microphone/Sound In==
Might need to be turned on in the mixer
==Hard Drive Active Protection System (HDAPS)==
Please add to this section
==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):
* {{cmdroot|ip l s wlan0 up}}
* {{cmdroot|modprobe -r iwl3945 && modprobe iwl3945}}
* reboot
* suspend and resume

== Middle-button Scrolling ==
Please add to this section

==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 but not with the the screen saver. Also, you are still required to type your user name on the login screen.

There appears to be a method to make the reader work for the screensaver, but I haven't tested it yet.

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

due to this bug [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 here:

https://launchpad.net/~jon-oberheide/+archive

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 pam_unix.so line and
try_first_pass
to the end of the pam_unix.so line.

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

At this point, you should be ready to swipe!

Usage examples:
*At the login prompt: enter your name, when prompted for password swipe your finger (and press enter if you do not have the third party repository!)
*if you want to perform an action with sudo, it will ask for your password, just swipe your finger (and press enter)

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 above in the comments]
* [https://launchpad.net/~jon-oberheide/+archive| Repository for the third party fix] credits to [https://launchpad.net/~jon-oberheide| Jon Oberheide]

=Other Problems=
==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 compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. 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.

==Logging out or restarting X==
See the Display setup section for how to work around this problem.

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

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

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

= 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

2008-11-10T22:27:49Z

Ghosty: /* Fingerprint Reader */

=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.
*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
*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. Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not. However, 177 causes a log out bug that is addressed below.

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 increased the value from its default, GDM will give X more time before it assumes X is faulty.

==Microphone/Sound In==
Might need to be turned on in the mixer
==Hard Drive Active Protection System (HDAPS)==
Please add to this section
==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):
* {{cmdroot|ip l s wlan0 up}}
* {{cmdroot|modprobe -r iwl3945 && modprobe iwl3945}}
* reboot
* suspend and resume

== Middle-button Scrolling ==
Please add to this section

==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 but not with the the screen saver. Also, you are still required to type your user name on the login screen.

There appears to be a method to make the reader work for the screensaver, but I haven't tested it yet.

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

due to this bug [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 here:

https://launchpad.net/~jon-oberheide/+archive

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 pam_unix.so line and
try_first_pass
to the end of the pam_unix.so line.

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

At this point, you should be ready to swipe!

Usage examples:
*At the login prompt: enter your name, when prompted for password swipe your finger (and press enter if you do not have the third party repository!)
*if you want to perform an action with sudo, it will ask for your password, just swipe your finger (and press enter)

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 above in the comments]
* [https://launchpad.net/~jon-oberheide/+archive|Repository for the third party fix]] credits to [https://launchpad.net/~jon-oberheide|Jon Oberheide]

=Other Problems=
==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 compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. 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.

==Logging out or restarting X==
See the Display setup section for how to work around this problem.

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

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

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

= 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

2008-11-08T18:09:02Z

Ghosty: /* Fingerprint Reader */

Install Ubuntu Intrepid Ibex on a T61p

2008-11-08T17:57:47Z

Ghosty: added fingerprint reader information (slightly adapted over the gutsy install)