ThinkWiki - User contributions [en]

Installing Ubuntu 9.04 (Jaunty Jackalope) on a ThinkPad T61p

2009-06-24T06:31:12Z

Chazchaz101: Tested Audio

This page describes issues and solutions for getting Ubuntu 9.04 working on a T61p.

=Hardware=
==Works Out of the Box==
*Wireless (Intel 3945ABG or 4965AGN)
*Touchpoint
*Trackpad
**Trackpad scrolling
*Sound card
**Volume up/down/mute buttons
**Audio out
*FN keys
**numlock
**Lock computer
**Battery information
**Screen brightness control
**Thinklight control
**sleep
**WLAN/BT on/off toggle
**Media player control
*Wired LAN
*ultranav scrolling
*Optical drive
*SD/MMC Memory card reader
*ACPI
**Battery status, power graphs, and history
**Lid open/close
**Suspend to RAM (with lvm encryption, but this shouldn't matter)

==Needs Tweaks==
*Video
**Nvidia drivers can be loaded by either:
***Enabling the restricted repository and running {{cmduser|sudo apt-get install nvidia-glx-180}}
***Installing the envyng-core package and running {{cmduser|envyng -t}}
*Sound In:
**Must be unmuted in Volume Control (Click on volume tray icon, click on Volume Control, select Capture: HDA Intel - AD198x)
**Internal mic is very quiet relative to line in, so you may have to turn it above 100% using the Manager utility from the padevchooser package.
*ThinkFinger
Append following line to '/etc/apt/sources.list':
<nowiki>deb http://ppa.launchpad.net/jon-oberheide/ubuntu jaunty main</nowiki>
Execute:
<nowiki>sudo apt-get install thinkfinger-tools libpam-thinkfinger libthinkfinger0</nowiki>
Restart
Execute:
<nowiki>tf-tool --acquire && tf-tool --verify</nowiki>

==Doesn't Work==
*ACPI
**Suspend to Disk (tested with LVM encryption): Successfully unlocks encrypted volume and starts "waking up stage." Video then becomes corrupted and computer locks up.
==Untested==
*fingerprint reader

=Other Issues=
=Compared to 8.10=
==Improvements==
==Bugs and Regressions==
*Restricted Driver panel does not immediately suggest the installation of the Nvidia binary driver as it did in previous releases. See fixes in Tweaks section.

Installing Ubuntu 9.04 (Jaunty Jackalope) on a ThinkPad T61p

2009-06-24T06:30:21Z

Chazchaz101: Cleaned up/Consolidated info on Nvidia drivers

This page describes issues and solutions for getting Ubuntu 9.04 working on a T61p.

=Hardware=
==Works Out of the Box==
*Wireless (Intel 3945ABG or 4965AGN)
*Touchpoint
*Trackpad
**Trackpad scrolling
*Sound card
**Volume up/down/mute buttons
**Audio out
*FN keys
**numlock
**Lock computer
**Battery information
**Screen brightness control
**Thinklight control
**sleep
**WLAN/BT on/off toggle
**Media player control
*Wired LAN
*ultranav scrolling
*Optical drive
*SD/MMC Memory card reader
*ACPI
**Battery status, power graphs, and history
**Lid open/close
**Suspend to RAM (with lvm encryption, but this shouldn't matter)

==Needs Tweaks==
*Video
**Nvidia drivers can be loaded by either:
***Enabling the restricted repository and running {{cmduser|sudo apt-get install nvidia-glx-180}}
***Installing the envyng-core package and running {{cmduser|envyng -t}}
*Sound In:
**Must be unmuted in Volume Control (Click on volume tray icon, click on Volume Control, select Capture: HDA Intel - AD198x)
**Internal mic is very quiet relative to line in, so you may have to turn it above 100% using the Manager utility from the padevchooser package.
*ThinkFinger
Append following line to '/etc/apt/sources.list':
<nowiki>deb http://ppa.launchpad.net/jon-oberheide/ubuntu jaunty main</nowiki>
Execute:
<nowiki>sudo apt-get install thinkfinger-tools libpam-thinkfinger libthinkfinger0</nowiki>
Restart
Execute:
<nowiki>tf-tool --acquire && tf-tool --verify</nowiki>

==Doesn't Work==
*ACPI
**Suspend to Disk (tested with LVM encryption): Successfully unlocks encrypted volume and starts "waking up stage." Video then becomes corrupted and computer locks up.
==Untested==

*Sound card
**Audio in
*fingerprint reader

=Other Issues=
=Compared to 8.10=
==Improvements==
==Bugs and Regressions==
*Restricted Driver panel does not immediately suggest the installation of the Nvidia binary driver as it did in previous releases. See fixes in Tweaks section.

Installing Ubuntu 9.04 (Jaunty Jackalope) on a ThinkPad T61p

2009-06-24T06:20:12Z

Chazchaz101: Details for Sound in and Hibernate

This page describes issues and solutions for getting Ubuntu 9.04 working on a T61p.

=Hardware=
==Works Out of the Box==
*Wireless (Intel 3945ABG or 4965AGN)
*Touchpoint
*Trackpad
**Trackpad scrolling
*Sound card
**Volume up/down/mute buttons
**Audio out
*FN keys
**numlock
**Lock computer
**Battery information
**Screen brightness control
**Thinklight control
**sleep
**WLAN/BT on/off toggle
**Media player control
*Wired LAN
*ultranav scrolling
*Optical drive
*SD/MMC Memory card reader
*ACPI
**Battery status, power graphs, and history
**Lid open/close
**Suspend to RAM (with lvm encryption, but this shouldn't matter)

==Needs Tweaks==
*Video
**Nvidia drivers can be loaded by installing the envyng-core package and running envyng -t. I Chose the recommended 180 version and 3D acceleration appears to be working properly.
*Sound In:
**Must be unmuted in Volume Control (Click on volume tray icon, click on Volume Control, select Capture: HDA Intel - AD198x)
**Internal mic is very quiet relative to line in, so you may have to turn it above 100% using the Manager utility from the padevchooser package.
*ThinkFinger
Append following line to '/etc/apt/sources.list':
<nowiki>deb http://ppa.launchpad.net/jon-oberheide/ubuntu jaunty main</nowiki>
Execute:
<nowiki>sudo apt-get install thinkfinger-tools libpam-thinkfinger libthinkfinger0</nowiki>
Restart
Execute:
<nowiki>tf-tool --acquire && tf-tool --verify</nowiki>

==Doesn't Work==
*ACPI
**Suspend to Disk (tested with LVM encryption): Successfully unlocks encrypted volume and starts "waking up stage." Video then becomes corrupted and computer locks up.
==Untested==

*Sound card
**Audio in
*fingerprint reader

=Other Issues=
=Compared to 8.10=
==Improvements==
==Bugs and Regressions==
As mentioned, the restricted Nvidia driver does not load by default. However, the driver can be loaded by enabling the restricted repository and running the following command:
sudo apt-get install nvidia-glx-180

[[Category:T61p]]

Installing Ubuntu 9.04 (Jaunty Jackalope) on a ThinkPad T61p

2009-06-24T05:50:46Z

Chazchaz101: /* Needs Tweaks */

This page describes issues and solutions for getting Ubuntu 9.04 working on a T61p.

=Hardware=
==Works Out of the Box==
*Wireless (Intel 3945ABG or 4965AGN)
*Touchpoint
*Trackpad
**Trackpad scrolling
*Sound card
**Volume up/down/mute buttons
**Audio out
*FN keys
**numlock
**Lock computer
**Battery information
**Screen brightness control
**Thinklight control
**sleep
**WLAN/BT on/off toggle
**Media player control
*Wired LAN
*ultranav scrolling
*Optical drive
*SD/MMC Memory card reader
*ACPI
**Battery status, power graphs, and history
**Lid open/close

==Needs Tweaks==
*Video
**Nvidia drivers can be loaded by installing the envyng-core package and running envyng -t. I Chose the recommended 180 version and 3D acceleration appears to be working properly.
*ACPI
**Suspend to RAM - monitor doesnt turn on on wake up.
*ThinkFinger
Append following line to '/etc/apt/sources.list':
<nowiki>deb http://ppa.launchpad.net/jon-oberheide/ubuntu jaunty main</nowiki>
Execute:
<nowiki>sudo apt-get install thinkfinger-tools libpam-thinkfinger libthinkfinger0</nowiki>
Restart
Execute:
<nowiki>tf-tool --acquire && tf-tool --verify</nowiki>

==Doesn't Work==
==Untested==

*Sound card
**Audio in
*fingerprint reader
*ACPI
**Suspend to Disk
**Suspend-to-RAM/Suspend-to-Disk under full disk LVM encryption

=Other Issues=
=Compared to 8.10=
==Improvements==
==Bugs and Regressions==
As mentioned, the restricted Nvidia driver does not load by default. However, the driver can be loaded by enabling the restricted repository and running the following command:
sudo apt-get install nvidia-glx-180

[[Category:T61p]]

Install Ubuntu Intrepid Ibex on a T61p

2008-12-26T03:47:41Z

Chazchaz101: /* Battery control by tp_smapi */ Clarification of battery threshhold info

=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, preventing the battery from charging all the way in exchange for a reduction in the loss of battery capacity that occurs after multiple cycles.
echo "90" | sudo tee -a /sys/devices/platform/smapi/BAT0/start_charge_thresh
(by default this was set to 86% on my laptop)

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

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

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

= 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-02T23:39:39Z

Chazchaz101: EDID Misdetection fix doesn't work on 1920x1200 displays

=What works and what doesn't?=
==Working 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.
*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)!

==(Small) Tweaks needed for...==
*Microphone/Sound In
**Might need to be turned on in the mixer
*HDAPS
**Not yet in this howto
*Choppy Compiz animations
**NVidia's PowerMizer feature will slow down the GPU when "inactive" even on AC power.

==Not working==
*Logging out or restarting X
** With 177 version of the NVidia binary (restricted) graphics driver on a Quadro FX 570M.

'''NOTE''':Following the suggestion in the 'discussion' page, I was successful in making logging out of X work with 177.80 by increasing the timeout in /etc/gdm/gdm.conf by changing the line GdmXServerTimeout=10 to GdmXServerTimeout=100. Thanks! --user.sarang2005}}

*The hard radio killswitch for Intel WLAN.

=Mandatory=
==Display/Video==
''This part is taken from [[Install Ubuntu Hardy Heron on a T61p | Hardy installation instructions]].''

To enable 3D acceleration, the proprietary NVidia driver must be installed. The first time you boot into 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. I would strongly recommend the latter one, because it will provide Suspend to disk functionality in favour of the 173 version.

This should also install the "NVidia X Server Settings" program in System --> Administration.

At the time of writing I am not able to restart X or log out from my GNOME session. X will fail to start and will eventually fall back to failsafe config (VESA drivers). This happens on my Quadro FX 570M and I'm not sure it is an issue of the new NVidia driver or the new X.org version in Intrepid.

{{NOTE|You should even install the binary NVidia driver if you won't use 3D acceleration because the open source nv driver will drain your battery much faster, because it doesn't support PowerMizer at all. This will keep the GPU in full speed all the time and will consume around 12 Watts more because of that (for the Quadro FX 570M), according to Powertop. That is 50% of the total usage!}}

=Optional=
==Fix for choppy Compiz animations==

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. If you do not see the 'Advanced Desktop Effects Settings' option, install compizconfig-settings-manager and follow the same steps after that.

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.

=Problems=
== Not able to restart X ==
This is quite an issue when you want to switch user or log out. The Xorg.0.log file doesn't give any errors or hints. Surprisingly both Suspend to RAM and Suspend to Disk are not failing.

It is a known issue in the 177 version of the binary NVidia driver which has not yet been addressed by NVidia. See Launchpad bug [http://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-177/+bug/258357 258357]. Workaround is to use the older 173 version (without Suspend to Disk functionality and with slower resume from Suspend to RAM).

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

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

= Information, not Ubuntu issues =
== 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 =
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.
*Atheros WLAN not working after resume from Suspend to RAM (but a workaround is available; [[#Wireless_not_working_after_resume_.28Atheros.29|see above]]).

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

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61p

2008-09-08T09:10:23Z

Chazchaz101: /* Suspend */ Added reminder to install latest drivers

==What works out of the box?==
*Wireless (Intel 3945ABG or 4965AGN)
**Only tested G mode
**LED not working yet. Known issue in kernel driver.
*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
*Optical drive
**Optiarc AD-7910A
*Sound card
**No Microphone
*Memory card reader
**Only tested SD (non-HC) cards. Didn't take locked (read-only) 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
**LCD brightness adjustment on power source
**Only tested with a single 6-cell battery

==What needs some tweaks?==
*Suspend-to-RAM (Standby, Suspend)
*Microphone/Sound In
{{Todo|HDAPS (harddrive protection system)}}

==What doesn't work at the moment?==
*Suspend-to-Disk (Hibernate)
*Wireless LAN power/activity LED

== Display / Video ==

To enable 3D acceleration, the proprietary NVidia driver must be installed. The first time you boot into 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.

If you want more options for configuring your video card than is provided by the Ubuntu control panels, you can install the NVidia Control Panel with

{{cmduser| sudo apt-get install nvidia-settings}}

which will add the NVidia X Server Settings panel to the Administration menu.

Alternately, more recent versions of the NVidia driver and Control Panel can be installed using EnvyNG (envyng-gtk in Synaptic). Simply start it up (System Tools --> EnvyNG) and ask it to install the NVidia driver. Using the most recent binary drivers, or at least ones more recent that
those installed by the Hardware Drivers panel, is required for proper Suspend functionality.

Unfortunately, there are some annoying bugs in the NVidia driver. The most annoying one is that after resuming from suspend, you will often get a blank white screen. To get past it, simply type in your password and press enter, and you will be returned to your desktop. Fortunately, Ubuntu has released a workaround for this bug, so it should go away once you update all your packages to the latest versions.

Another problem is that the driver does not report the correct refresh rate to Compiz, resulting in rough animation. 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.

Next, Compiz animations are also 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. To solve 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 755 powermizer-loop powermizer-off

Then to make powermizer-off run on login, I opened System --> Preferences --> Sessions, clicked on Add, and entered the command "/home/argilo/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.

One final bug is that EDID (Extended Display Identification Data) is misdetected, which causes problems with font sizes and greatly 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.) To correct this problem, I added the following lines to /etc/X11/xorg.conf in the "Screen" section:

Option "UseEdidDpi" "FALSE"
Option "DPI" "96 x 96"
Option "UseEdidFreqs" "FALSE"
Option "HorizSync" "40-70"

The first two lines fix the font size issue, and the last two lines fix the resolution problem. I'm not sure if the 40-70 values are actually correct, since I just took them from someone else's xorg.conf, but they seem to work.

NVidia seems to have corrected the EDID misdetection bug in the latest version of their driver, but it's not available in Hardy and I'm not aware of any easy way to install it.

== Suspend ==
Suspend is supposed to work out of the box if you're not using the Nvidia binary drivers. If you are using them, make sure the are updated as explained in the Display/Video section, and the following instructions will fix suspend to ram. Suspend to disk (hibernate) is not working at this time.

{{NOTE|These instructions worked on the T61p with type numbers 6460, 6457 (and perhaps 6465). It may also work with other type numbers.}}

To get suspend to ram working, you need to edit a configuration file, which apparently has some bad information in it.

{{cmduser |gksudo gedit /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi}}

Find the following section:
...

<match key="system.hardware.product" prefix_outof="6457;6460;6465">
<merge key="power_management.quirk.s3_bios" type="bool">true</merge>
<merge key="power_management.quirk.vbemode_restore" type="bool">true</merge>
</match>


<match key="system.hardware.product" prefix_outof="6459;7664;8918">
<merge key="power_management.quirk.none" type="bool">true</merge>
</match>


...

Remove the <code>6457;6460;</code> from the <code><match key="system.hardware.product" prefix_outof="6457;6460;6465"></code> line and add the following lines right before the <code></code> line:
<match key="system.hardware.product" prefix_outof="6457;6460">
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.vbemode_restore" type="bool">true</merge>
</match>

Based on [https://bugs.launchpad.net/ubuntu/+source/hal-info/+bug/235284 Bug #235284 in hal-info (Ubuntu)]

On (at least) the 6457 model you'll need the latest binary Nvidia graphics drivers (173.14.09 at time of writing for Envy) to be able to resume from suspend. Additionally I have to switch to the X terminal manually by pressing alt+F7.
The sleep LED will blink for a while after resume, but will stop eventually and the wireless devices will be switched back on. You may experience some resetting of the display when that happens. Just move the cursor to regain your desktop. N.B. This does not seem to occur when waking after a long time of sleep.

== Bluetooth ==
If installed, bluetooth must be enabled with the command:

{{cmduser | echo enable | sudo tee /proc/acpi/ibm/bluetooth}}

Replace enable with disable to turn it off.

You can now connect devices by following the instructions at [https://help.ubuntu.com/community/BluetoothSetup Ubuntu Help Bluetooth Setup page]
{{NOTE|On (at least) the 6457 model the Bluetooth and Wireless LAN toggle button (Fn+F5) seems to work fine. Be aware of the additional hardware switch at the front of the machine. This needs to be in the green setting.}}

== Internal Microphone/Microphone Input Jack ==
The microphone is muted out of the box. In order to enable it, double click on the the speaker icon in the task bar or run {{cmduser | gnome-volume-control}}. Under File > Change Device, select "Capture: ALSA PCM on front:0 (AD198x Analog) via DMA (PulseAudio Mixer)" and set the master slider to about 75%. Make sure that the mute and recording buttons below the slider do not show red Xs.

Go back to the Change Device menu and select "HDA Intel (Alsa mixer)". Then go to the edit menu and select preferences. In the window that opens, make sure that the boxes for Capture, Capture1, and both instances of Input Source. The Volume Control panel should now have four tabs: Playback, Recording, Switches and Options. In the options tab, select Internal Mic for the internal microphone or Mic for the mic input jack for both Input sources. As far as i can tell, the second one down doesn't seem to actually do anything. Now in the recording tab you can mute Capture 1 and adjust the sensitivity of the mic with the Capture slider. You can use Sound Recorder in Applications > Sound & Video to test out your settings.

In the past, I have spent a fair amount of time messing with the PulseAudio settings on this install, so it would be great if someone with a relatively unaltered install could verify these instructions and post a confirmation. The main thing I did before was follow the PulseAudio howto here: [http://ubuntuforums.org/showthread.php?t=789578 HOWTO: PulseAudio Fixes & System-Wide Equalizer Support] [[User:Chazchaz101|Chazchaz101]] 11:05, 8 September 2008 (CEST)

[[Category:T61p]]

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61p

2008-09-08T09:05:52Z

Chazchaz101: Added Microphone / Sound In section

==What works out of the box?==
*Wireless (Intel 3945ABG or 4965AGN)
**Only tested G mode
**LED not working yet. Known issue in kernel driver.
*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
*Optical drive
**Optiarc AD-7910A
*Sound card
**No Microphone
*Memory card reader
**Only tested SD (non-HC) cards. Didn't take locked (read-only) 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
**LCD brightness adjustment on power source
**Only tested with a single 6-cell battery

==What needs some tweaks?==
*Suspend-to-RAM (Standby, Suspend)
*Microphone/Sound In
{{Todo|HDAPS (harddrive protection system)}}

==What doesn't work at the moment?==
*Suspend-to-Disk (Hibernate)
*Wireless LAN power/activity LED

== Display / Video ==

To enable 3D acceleration, the proprietary NVidia driver must be installed. The first time you boot into 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.

If you want more options for configuring your video card than is provided by the Ubuntu control panels, you can install the NVidia Control Panel with

{{cmduser| sudo apt-get install nvidia-settings}}

which will add the NVidia X Server Settings panel to the Administration menu.

Alternately, more recent versions of the NVidia driver and Control Panel can be installed using EnvyNG (envyng-gtk in Synaptic). Simply start it up (System Tools --> EnvyNG) and ask it to install the NVidia driver. Using the most recent binary drivers, or at least ones more recent that
those installed by the Hardware Drivers panel, is required for proper Suspend functionality.

Unfortunately, there are some annoying bugs in the NVidia driver. The most annoying one is that after resuming from suspend, you will often get a blank white screen. To get past it, simply type in your password and press enter, and you will be returned to your desktop. Fortunately, Ubuntu has released a workaround for this bug, so it should go away once you update all your packages to the latest versions.

Another problem is that the driver does not report the correct refresh rate to Compiz, resulting in rough animation. 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.

Next, Compiz animations are also 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. To solve 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 755 powermizer-loop powermizer-off

Then to make powermizer-off run on login, I opened System --> Preferences --> Sessions, clicked on Add, and entered the command "/home/argilo/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.

One final bug is that EDID (Extended Display Identification Data) is misdetected, which causes problems with font sizes and greatly 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.) To correct this problem, I added the following lines to /etc/X11/xorg.conf in the "Screen" section:

Option "UseEdidDpi" "FALSE"
Option "DPI" "96 x 96"
Option "UseEdidFreqs" "FALSE"
Option "HorizSync" "40-70"

The first two lines fix the font size issue, and the last two lines fix the resolution problem. I'm not sure if the 40-70 values are actually correct, since I just took them from someone else's xorg.conf, but they seem to work.

NVidia seems to have corrected the EDID misdetection bug in the latest version of their driver, but it's not available in Hardy and I'm not aware of any easy way to install it.

== Suspend ==
Suspend is supposed to work out of the box if you're not using the Nvidia binary drivers. If you are using them, the following instructions will fix suspend to ram. Suspend to disk (hibernate) is not working at this time.

{{NOTE|These instructions worked on the T61p with type numbers 6460, 6457 (and perhaps 6465). It may also work with other type numbers.}}

To get suspend to ram working, you need to edit a configuration file, which apparently has some bad information in it.

{{cmduser |gksudo gedit /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi}}

Find the following section:
...

<match key="system.hardware.product" prefix_outof="6457;6460;6465">
<merge key="power_management.quirk.s3_bios" type="bool">true</merge>
<merge key="power_management.quirk.vbemode_restore" type="bool">true</merge>
</match>


<match key="system.hardware.product" prefix_outof="6459;7664;8918">
<merge key="power_management.quirk.none" type="bool">true</merge>
</match>


...

Remove the <code>6457;6460;</code> from the <code><match key="system.hardware.product" prefix_outof="6457;6460;6465"></code> line and add the following lines right before the <code></code> line:
<match key="system.hardware.product" prefix_outof="6457;6460">
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.vbemode_restore" type="bool">true</merge>
</match>

Based on [https://bugs.launchpad.net/ubuntu/+source/hal-info/+bug/235284 Bug #235284 in hal-info (Ubuntu)]

On (at least) the 6457 model you'll need the latest binary Nvidia graphics drivers (173.14.09 at time of writing for Envy) to be able to resume from suspend. Additionally I have to switch to the X terminal manually by pressing alt+F7.
The sleep LED will blink for a while after resume, but will stop eventually and the wireless devices will be switched back on. You may experience some resetting of the display when that happens. Just move the cursor to regain your desktop. N.B. This does not seem to occur when waking after a long time of sleep.

== Bluetooth ==
If installed, bluetooth must be enabled with the command:

{{cmduser | echo enable | sudo tee /proc/acpi/ibm/bluetooth}}

Replace enable with disable to turn it off.

You can now connect devices by following the instructions at [https://help.ubuntu.com/community/BluetoothSetup Ubuntu Help Bluetooth Setup page]
{{NOTE|On (at least) the 6457 model the Bluetooth and Wireless LAN toggle button (Fn+F5) seems to work fine. Be aware of the additional hardware switch at the front of the machine. This needs to be in the green setting.}}

== Internal Microphone/Microphone Input Jack ==
The microphone is muted out of the box. In order to enable it, double click on the the speaker icon in the task bar or run {{cmduser | gnome-volume-control}}. Under File > Change Device, select "Capture: ALSA PCM on front:0 (AD198x Analog) via DMA (PulseAudio Mixer)" and set the master slider to about 75%. Make sure that the mute and recording buttons below the slider do not show red Xs.

Go back to the Change Device menu and select "HDA Intel (Alsa mixer)". Then go to the edit menu and select preferences. In the window that opens, make sure that the boxes for Capture, Capture1, and both instances of Input Source. The Volume Control panel should now have four tabs: Playback, Recording, Switches and Options. In the options tab, select Internal Mic for the internal microphone or Mic for the mic input jack for both Input sources. As far as i can tell, the second one down doesn't seem to actually do anything. Now in the recording tab you can mute Capture 1 and adjust the sensitivity of the mic with the Capture slider. You can use Sound Recorder in Applications > Sound & Video to test out your settings.

In the past, I have spent a fair amount of time messing with the PulseAudio settings on this install, so it would be great if someone with a relatively unaltered install could verify these instructions and post a confirmation. The main thing I did before was follow the PulseAudio howto here: [http://ubuntuforums.org/showthread.php?t=789578 HOWTO: PulseAudio Fixes & System-Wide Equalizer Support] [[User:Chazchaz101|Chazchaz101]] 11:05, 8 September 2008 (CEST)

[[Category:T61p]]

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61p

2008-09-05T06:58:08Z

Chazchaz101: /* Display / Video */ Add explanation for why EnvyNG/Most recent drivers are needed

==What works out of the box?==
*Wireless (Intel 3945ABG or 4965AGN)
**Only tested G mode
**LED not working yet. Known issue in kernel driver.
*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
*Optical drive
**Optiarc AD-7910A
*Sound card
**Microphone not yet tested
*Memory card reader
**Only tested SD (non-HC) cards. Didn't take locked (read-only) 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
**LCD brightness adjustment on power source
**Only tested with a single 6-cell battery

==What needs some tweaks?==
*Suspend-to-RAM (Standby, Suspend)
{{Todo|HDAPS (harddrive protection system)}}

==What doesn't work at the moment?==
*Suspend-to-Disk (Hibernate)
*Wireless LAN power/activity LED

== Display / Video ==

To enable 3D acceleration, the proprietary NVidia driver must be installed. The first time you boot into 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.

If you want more options for configuring your video card than is provided by the Ubuntu control panels, you can install the NVidia Control Panel with

{{cmduser| sudo apt-get install nvidia-settings}}

which will add the NVidia X Server Settings panel to the Administration menu.

Alternately, more recent versions of the NVidia driver and Control Panel can be installed using EnvyNG (envyng-gtk in Synaptic). Simply start it up (System Tools --> EnvyNG) and ask it to install the NVidia driver. Using the most recent binary drivers, or at least ones more recent that
those installed by the Hardware Drivers panel, is required for proper Suspend functionality.

Unfortunately, there are some annoying bugs in the NVidia driver. The most annoying one is that after resuming from suspend, you will often get a blank white screen. To get past it, simply type in your password and press enter, and you will be returned to your desktop. Fortunately, Ubuntu has released a workaround for this bug, so it should go away once you update all your packages to the latest versions.

Another problem is that the driver does not report the correct refresh rate to Compiz, resulting in rough animation. 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.

Next, Compiz animations are also 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. To solve 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 755 powermizer-loop powermizer-off

Then to make powermizer-off run on login, I opened System --> Preferences --> Sessions, clicked on Add, and entered the command "/home/argilo/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.

One final bug is that EDID (Extended Display Identification Data) is misdetected, which causes problems with font sizes and greatly 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.) To correct this problem, I added the following lines to /etc/X11/xorg.conf in the "Screen" section:

Option "UseEdidDpi" "FALSE"
Option "DPI" "96 x 96"
Option "UseEdidFreqs" "FALSE"
Option "HorizSync" "40-70"

The first two lines fix the font size issue, and the last two lines fix the resolution problem. I'm not sure if the 40-70 values are actually correct, since I just took them from someone else's xorg.conf, but they seem to work.

NVidia seems to have corrected the EDID misdetection bug in the latest version of their driver, but it's not available in Hardy and I'm not aware of any easy way to install it.

== Suspend ==
Suspend is supposed to work out of the box if you're not using the Nvidia binary drivers. If you are using them, the following instructions will fix suspend to ram. Suspend to disk (hibernate) is not working at this time.

{{NOTE|These instructions worked on the T61p with type numbers 6460, 6457 (and perhaps 6465). It may also work with other type numbers.}}

To get suspend to ram working, you need to edit a configuration file, which apparently has some bad information in it.

{{cmduser |gksudo gedit /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi}}

Find the following section:
...

<match key="system.hardware.product" prefix_outof="6457;6460;6465">
<merge key="power_management.quirk.s3_bios" type="bool">true</merge>
<merge key="power_management.quirk.vbemode_restore" type="bool">true</merge>
</match>


<match key="system.hardware.product" prefix_outof="6459;7664;8918">
<merge key="power_management.quirk.none" type="bool">true</merge>
</match>


...

Remove the <code>6457;6460;</code> from the <code><match key="system.hardware.product" prefix_outof="6457;6460;6465"></code> line and add the following lines right before the <code></code> line:
<match key="system.hardware.product" prefix_outof="6457;6460">
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.vbemode_restore" type="bool">true</merge>
</match>

Based on [https://bugs.launchpad.net/ubuntu/+source/hal-info/+bug/235284 Bug #235284 in hal-info (Ubuntu)]

On (at least) the 6457 model you'll need the latest binary Nvidia graphics drivers (173.14.09 at time of writing for Envy) to be able to resume from suspend. Additionally I have to switch to the X terminal manually by pressing alt+F7.
The sleep LED will blink for a while after resume, but will stop eventually and the wireless devices will be switched back on. You may experience some resetting of the display when that happens. Just move the cursor to regain your desktop. N.B. This does not seem to occur when waking after a long time of sleep.

== Bluetooth ==
If installed, bluetooth must be enabled with the command:

{{cmduser | echo enable | sudo tee /proc/acpi/ibm/bluetooth}}

Replace enable with disable to turn it off.

You can now connect devices by following the instructions at [https://help.ubuntu.com/community/BluetoothSetup Ubuntu Help Bluetooth Setup page]
{{NOTE|On (at least) the 6457 model the Bluetooth and Wireless LAN toggle button (Fn+F5) seems to work fine. Be aware of the additional hardware switch at the front of the machine. This needs to be in the green setting.}}

[[Category:T61p]]

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61p

2008-07-10T08:33:47Z

Chazchaz101: Suspend with Nvidia binary drivers

==What works out of the box==
*Video driver
*Wireless (Intel 3945ABG or 4965AGN)
**Only tested G mode
*Video (VESA)
**Hardware Drivers panel offers to install NVidia proprietary drivers on first boot
*Touchpoint and trackpad
*Volume control buttons
*Screen brightness control

== Display / Video ==

To enable 3D acceleration, the proprietary NVidia driver must be installed. The first time you boot into 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.

If you want more options for configuring your video card than is provided by the Ubuntu control panels, you can install the NVidia Control Panel with

{{cmduser| sudo apt-get install nvidia-settings}}

which will add the NVidia X Server Settings panel to the Administration menu.

Alternately, the NVidia driver and Control Panel can be installed using EnvyNG (envyng-gtk in Synaptic). Simply start it up (System Tools --> EnvyNG) and ask it to install the NVidia driver.

Unfortunately, there are some annoying bugs in the NVidia driver. The most annoying one is that after resuming from suspend, you will often get a blank white screen. To get past it, simply type in your password and press enter, and you will be returned to your desktop. Fortunately, Ubuntu has released a workaround for this bug, so it should go away once you update all your packages to the latest versions.

Another problem is that the driver does not report the correct refresh rate to Compiz, resulting in rough animation. 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.

Next, Compiz animations are also 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. To solve 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 755 powermizer-loop powermizer-off

Then to make powermizer-off run on login, I opened System --> Preferences --> Sessions, clicked on Add, and entered the command "/home/argilo/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.

One final bug is that EDID (Extended Display Identification Data) is misdetected, which causes problems with font sizes and greatly 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.) To correct this problem, I added the following lines to /etc/X11/xorg.conf in the "Screen" section:

Option "UseEdidDpi" "FALSE"
Option "DPI" "96 x 96"
Option "UseEdidFreqs" "FALSE"
Option "HorizSync" "40-70"

The first two lines fix the font size issue, and the last two lines fix the resolution problem. I'm not sure if the 40-70 values are actually correct, since I just took them from someone else's xorg.conf, but they seem to work.

NVidia seems to have corrected the EDID misdetection bug in the latest version of their driver, but it's not available in Hardy and I'm not aware of any easy way to install it.

== Suspend ==
Suspend is supposed to work out of the box if you're not using the Nvidia binary drivers. If you are using them, the following instructions will fix suspend to ram. Suspend to disk (hibernate) is not working at this time.

{{NOTE|These instructions worked on my t61p with type number 6460. I'm not sure if this will work on machines with other type numbers.}}

To get suspend to ram working, you need to edit a configuration file, which apparently has some bad information in it.

{{cmduser |sudo gedit /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi}}

Find the following section:
...

<match key="system.hardware.product" prefix_outof="6457;6460;6465">
<merge key="power_management.quirk.s3_bios" type="bool">true</merge>
<merge key="power_management.quirk.vbemode_restore" type="bool">true</merge>
</match>


<match key="system.hardware.product" prefix_outof="6459;7664;8918">
<merge key="power_management.quirk.none" type="bool">true</merge>
</match>


...

Remove the <code>6460;</code> from the <code><match key="system.hardware.product" prefix_outof="6457;6460;6465"></code> line and add the following lines right before the <code></code> line:
<match key="system.hardware.product" prefix_outof="6460\">
<merge key="power_management.quirk.s3_bios\" type="bool">false</merge>
<merge key="power_management.quirk.vbemode_restore" type="bool">true</merge>
</match>

Based on [https://bugs.launchpad.net/ubuntu/+source/hal-info/+bug/235284 Bug #235284 in hal-info (Ubuntu)]
== Bluetooth ==
If installed, bluetooth must be enabled with the command:

{{cmduser | echo enable | sudo tee /proc/acpi/ibm/bluetooth}}

Replace enable with disable to turn it off.

You can now connect devices by following the instructions at [https://help.ubuntu.com/community/BluetoothSetup Ubuntu Help Bluetooth Setup page]

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61p

2008-06-26T23:23:37Z

Chazchaz101: Added Bluetooth Section

==What works out of the box==
*Video Driver
*Wireless (Intel 4965AGN)
**Only tested g mode
*Video (VESA)
**Hardware Drivers panel offers to install nvidia proprietary drivers on first boot
*Touchpoint and Trackpad
*Volume control Buttonsb
*Screen brightness control
== Display / Video ==

To enable 3D acceleration, the proprietary NVidia driver must be installed. The first time you boot into 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.

If you want more options for configuring your video card than is provided by the Ubuntu control panels, you can install the NVidia Control Panel with

{{cmduser| sudo apt-get install nvidia-settings}}

which will add the NVidia X Server Settings panel to the Administration menu.

Alternately, the NVidia driver and Control Panel can be installed using EnvyNG (envyng-gtk in Synaptic). Simply start it up (System Tools --> EnvyNG) and ask it to install the NVidia driver.

Unfortunately, there are some annoying bugs in the NVidia driver. The most annoying one is that after resuming from suspend, you will often get a blank white screen. To get past it, simply type in your password and press enter, and you will be returned to your desktop. Fortunately, Ubuntu has released a workaround for this bug, so it should go away once you update all your packages to the latest versions.

Another problem is that the driver does not report the correct refresh rate to Compiz, resulting in rough animation. 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.

Next, Compiz animations are also 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. To solve 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 755 powermizer-loop powermizer-off

Then to make powermizer-off run on login, I opened System --> Preferences --> Sessions, clicked on Add, and entered the command "/home/argilo/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.

One final bug is that EDID (Extended Display Identification Data) is misdetected, which causes problems with font sizes and greatly 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.) To correct this problem, I added the following lines to /etc/X11/xorg.conf in the "Screen" section:

Option "UseEdidDpi" "FALSE"
Option "DPI" "96 x 96"
Option "UseEdidFreqs" "FALSE"
Option "HorizSync" "40-70"

The first two lines fix the font size issue, and the last two lines fix the resolution problem. I'm not sure if the 40-70 values are actually correct, since I just took them from someone else's xorg.conf, but they seem to work.

NVidia seems to have corrected the EDID misdetection bug in the latest version of their driver, but it's not available in Hardy and I'm not aware of any easy way to install it.

== Bluetooth ==
If installed, bluetooth must be enabled with the command:

{{cmduser | echo enable | sudo tee /proc/acpi/ibm/bluetooth}}

Replace enable with disable to turn it off.

You can now connect devices by following the instructions at [https://help.ubuntu.com/community/BluetoothSetup Ubuntu Help Bluetooth Setup page]

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61p

2008-06-26T23:20:55Z

Chazchaz101: Added What Works Section

How to control fan speed

2008-06-22T04:22:04Z

Chazchaz101: /* Using a stock kernel */ added reboot required

This page discusses methods for controlling the system fan.

==For Linux==
===Using a patched kernel===
{{NOTE|The ibm-acpi driver is part of the Linux kernel 2.6.10 and later (option CONFIG_ACPI_IBM), so patching is not needed anymore.}}
{{WARN|This patch is superceded by the patches in [[ibm-acpi]] [[Git]] repository or [http://ibm-acpi.sourceforge.net ibm-acpi.sf.net] releases}}
{{NOTE|Advanced fan control through ibm-acpi has been merged in Linux 2.6.20-rc2 mainline, so users of 2.6.20 won't need to patch their kernels to get the '''fan level''' functionality anymore}}

The [[Patch for controlling fan speed]] provides a convenient interface via {{path|/proc/acpi/ibm/fan}}.

Manual speed control can be done through the [[patch for controlling fan speed]]:

'''#cat /proc/acpi/ibm/fan'''
status: enabled
level: auto
speed: 4219
commands: enable, disable, level <level>
(<level> is 0-7, auto or disengaged)

'''#echo level 2 > /proc/acpi/ibm/fan'''

'''#cat /proc/acpi/ibm/fan'''
status: enabled
level: 2
speed: 3142
commands: enable, disable, level <level>
(<level> is 0-7, auto or disengaged)

===Using a stock kernel===

{{NOTE|Fan control operations are disabled by default for safety reasons.}}

'''Linux Kernel 2.6.22 and Above (ibm-acpi has been replaced by [[thinkpad-acpi]])'''

To enable fan control, the module parameter <tt>fan_control=1</tt> must be given to thinkpad-acpi.

For example, in Ubuntu 8.04 (Hardy Heron), add the following to {{path|/etc/modprobe.d/options}}: <tt>options thinkpad_acpi fan_control=1</tt>

Having done so, reboot and you can use the following commands to control fan speed:

{{cmdroot|echo level 0 > /proc/acpi/ibm/fan}} (fan off)

{{cmdroot|echo level 2 > /proc/acpi/ibm/fan}} (low speed)

{{cmdroot|echo level 4 > /proc/acpi/ibm/fan}} (medium speed)

{{cmdroot|echo level 7 > /proc/acpi/ibm/fan}} (maximum speed)

{{cmdroot|echo level auto > /proc/acpi/ibm/fan}} (automatic - default)

{{cmdroot|echo level disengaged > /proc/acpi/ibm/fan}} (disengaged)

'''Older Linux Kernels (using [[ibm-acpi]])'''

To enable fan control, the module parameter <tt>experimental=1</tt> must be given to ibm-acpi. Then, you can control the fan by directly writing to the relevant embedded controller register, {{path|/proc/acpi/ibm/ecdump}}.

For example:

{{cmdroot|echo 0x2F 0x00 > /proc/acpi/ibm/ecdump}} (fan off)

{{cmdroot|echo 0x2F 0x02 > /proc/acpi/ibm/ecdump}} (low speed)

{{cmdroot|echo 0x2F 0x04 > /proc/acpi/ibm/ecdump}} (medium speed)

{{cmdroot|echo 0x2F 0x07 > /proc/acpi/ibm/ecdump}} (maximum speed)

{{cmdroot|echo 0x2F 0x80 > /proc/acpi/ibm/ecdump}} (automatic - default)

{{cmdroot|echo 0x2F 0x40 > /proc/acpi/ibm/ecdump}} (disengaged)

See the specifications below for the meaning of these modes.

===On/off control using stock kernel===

If you only wish to turn the fan on and off (with automatic control when it's on), you can use the following.

When loading [[ibm-acpi]] v0.11 with experimental switch ({{cmdroot|1=modprobe ibm_acpi experimental=1}}), it is possible to read and write the status of fan:

'''#cat /proc/acpi/ibm/fan'''
status: enabled
speed: 3580
commands: enable, disable

'''#echo disable > /proc/acpi/ibm/fan'''

'''cat /proc/acpi/ibm/fan'''
status: disabled
speed: 0
commands: enable, disable

When off, the fan will then '''never''' wake up. It is advised to use an automated control script to reduce the chance of hardware damage.

===Automated control scripts===

An [[ACPI fan control script#Variable speed control scripts|ACPI fan control script]] can be used to override the firmware's fan algorithm with gentler, quieter version. It monitors the laptop's [[thermal sensors]] and sets the fan speed accordingly, according to customizable thresholds. For the default behavior, simply save {{CodeRef|tp-fancontrol}} as {{path|tp-fancontrol}}, make sure you've loaded [[thinkpad-acpi]] with the "fan_control=1" parameter, and run: 
{{cmdroot|./tp-fancontrol}}

There is an distro independent daemon (http://projekte.f4.fhtw-berlin.de/trac/s0332819-linuxtools/wiki/), written in python. Packages are available for debian based linux systems.

[http://www.gambitchess.org/moin.py/ThinkPad_Fan_Control A GTK GUI program (packaged for Ubuntu 7.10 and 8.04)] may also help.

==For Windows==

Shimodax's ThinkPad fan control tool offers similar functionality (see [http://forum.thinkpads.com/viewtopic.php?t=17715 forum discussion] at thinkpads.com). Source and binaries are available through the [http://sourceforge.net/projects/tp4xfancontrol "Tp4xFanControl"] project on SourceForge.

==Hardware specs==

The following hardware behavior was discovered experimentally by [[User:Thinker|Thinker]] and neither provided by nor confirmed by IBM/Lenovo. The following description may be inaccurate and may vary by model (see list of models above). The terminology probably does not match the one used by IBM/Lenovo engineers.

{{NOTE|Information on other models is included in the [[ibm-acpi]] [[Git]] version.}}
{{NOTE|1=The ThinkPad {{X61s}} and {{X61}} with WWAN have a [http://forum.notebookreview.com/showthread.php?t=141931 second system fan]; its interface is currently unknown.}}

ACPI DSDT register HFSP (8 bits, offset 0x2F in the <tt>EmbeddedController</tt> address space, accessed through the standard EC interface at IO ports 0x62 and 0x66) is read/writable and has the following meaning:

Bits 7 6 5 4 3 2 1 0
---------------
Value 1 0 * * * * * * - automatic
* 1 * * * * * * - disengaged
0 0 N N N N N N - manual (0..63; 0=disable fan, 1=min, ..., 7=max)

Changing modes may not be immediate on all ThinkPads. Later ThinkPad models seem to take at least 5s to start responding to a fan mode change, for example.

After boot, the HFSP register may not reflect the true state of the EC (on some models it reads 0x07 even though the EC is actually in automatic mode).

=== Fan Tachometer ===

The embedded controller registers 0x84 (LSB), 0x85 (MSB) are the main fan tachometer, and report fan speed in RPM in everything since the {{A31}} and maybe a little earlier. Not much is know about the tachometer in earlier models, or even whether they had one or not.

=== Automatic mode ===
In ''automatic'' mode, the embedded controller sets the fan speed automatically according to system temperatures and some unknown algorithm.

Note that the ACPI DSDT may supplement this in some models. The {{X40}}, for example, changes the profile of speeds the automatic mode should use depending on battery status.

=== Manual mode ===

In ''manual'' mode, the fan level is forced to the given value and the EC will auto-regulate the fan to maintain at a (roughly) constant RPM, which is model-dependent. Manual speed levels 8-63 yield the same behavior as level 7, and the the ACPI DSDT uses level 7 for the emergency mode it enters upon critical CPU/GPU temperature, so apparently 7 is the real maximum level.

=== Disengaged (full-speed) mode ===

In ''disengaged'' mode, the embedded controller does not monitor the fan speed. It "disengages" the closed-loop control function that keeps track of fan speed, and uses an open-loop control function that ramps up the fan to its maximum speed (100% duty-cycle). The end speed is not stable, but it is often much faster than the maximum speed manual and automatic modes would set the fan to.

Most newer ThinkPads take quite a while (in excess of one minute) to fully enter disengaged mode. Exiting it is much faster. The {{A31}} acts differently, and switches to disengaged mode as fast as it switches to other modes.

For some reason, the embedded controller may stop updating the tachometer registers while entering or exiting disengaged mode in some ThinkPad firmware versions (hence the EC tachometer registers will not be updated on these models while entering/exiting disengaged mode). Once it arrives at maximum speed, or once it gets back at closed-loop cruise speed, the embedded controller starts updating the tachometer registers again. Later T models such as the {{T43}} have this problem, while the {{A31}} does not.

{{HINT|Apparently the [[Problem with fan noise|pulsing fan noise]] experienced by some users can be cured by repeatedly running 2-4 seconds of manual control followed by 0.5-1 seconds of disengaged mode. The pulse occurs when the the embedded controller computes the fan speed and adjusts the fan voltage adaptively every few seconds (~4.8sec for the ThinkPad T43); the aforementioned mode switching doesn't give it a chance to do so. One of the [[ACPI fan control script#Variable speed control scripts|ACPI fan control scripts]] implements this solution.}}

==Supported models==

The above was successfully tested on the following models:

* ThinkPad {{A31}} (fan levels RPM: 0 = off, 1-2 = ~3280-3380 (!), 3-5 = ~3200, 6-7 = ~3380, "disengaged" = ~4000 (see NOTE above))
* ThinkPad {{R50}} (highest manual level is 3; disengage mode works and reaches much higher RPM)
* ThinkPad {{R50p}} (fan levels RPM: 0 = off, 1-2 = ~3200, 3-5 = ~3500-3600, 6-7 = ~3700-3800, disengaged = ~5300)
* ThinkPad {{R51}} (fan levels RPM: 0 = off, 1-2 = ~3150, 3-5 = ~3350, 6 = ~3750, disengaged = ~5100)
* ThinkPad {{R51e}} (fan levels RPM: 0 = off, 1-2 = ~3300, 3-5 = ~3800, 6 = ~4150, disengaged = ~5100)
* ThinkPad {{R52}} (fan levels RPM: 0 = off, 1-2 = ~3350, 3-5 = ~3650, 6 = ~4250, disengaged = ~5245)
* ThinkPad {{R60}} (fan levels RPM: 0 = off, 1-1 = ~2650, 3-5 = ~3300, 6-7 = ~3950, disengaged = ~4800)
* ThinkPad {{R60e}}
* ThinkPad {{T22}}
* ThinkPad {{T23}} (low speed = ~2200, medium and maximum speed = ~4800; disengaged mode works at ~5800)
* ThinkPad {{T30}}
* ThinkPad {{T40}} (fan levels RPM: 1-2 = ~2950, 3-5 = ~3600, 6-7 = ~4050; disengaged = ~5400)
* ThinkPad {{T41}}, {{T41p}} (fan levels RPM: 1-2 = ~2980, 3-5 = ~3500, 6-7 = ~4050; disengaged mode works at ~5100)
* ThinkPad {{T42}}, {{T42p}} (fan levels RPM: 1-2 = ~2900, 3-5 = ~3700, 6-7 = ~4700; disengaged mode works at ~5200)
* ThinkPad {{T43}}, {{T43p}} (fan levels RPM: 1-2 = ~3300, 3-5 = ~4100, 6-7 = ~4700; disengaged mode works at ~6450)
* ThinkPad {{T60}} (fan levels RPM: 1-2 = 3000-3100, 3-5 = ~3600, 6-7 = ~4500; disengaged mode works at ~5500)
* ThinkPad {{T61}} (fan levels RPM: 0 = off, 1-2 = ~2980, 3-5 = ~3330, 6-7 = ~3760; disengaged mode works at ~4500)
* ThinkPad {{X30}} (level 0 = off, low = ~3900, medium = ~4200, maximum = ~4650, disengaged = ~5900)
* ThinkPad {{X31}} (fan levels RPM: 0 = off, 1-2 = ~2850, 3-5 = ~3450, 6 = ~4050, 7 = ~4150; disengaged mode works at ~4975)
* ThinkPad {{X40}}
* ThinkPad {{X41}}
* ThinkPad {{X41T}}
* ThinkPad {{X60}}
* ThinkPad {{X61s}}
* ThinkPad {{Z60t}}, {{Z60m}} (fan levels RPM: 1-2 = ~1700, 3-5 = ~2800, 6-7 = ~3500)
* ThinkPad {{Z61m}}
* Thinkpad {{Z61p}} (fan levels 0-7, auto, disengaged; enable, disable; watchdog (untested))
Probably other models are supported too (please update this page if you confirm this; maintain some ordering too).

==Models using a different interface==

The following models also work, use a different access method which supported (only) via the {{path|/proc/acpi/ibm/fan}} of [[ibm-acpi]]. No need for patching.

* ThinkPad {{600E}}, {{600X}}, {{770E}}, {{770X}} (these use a different fan control interface)

==Unsupported models==

* ThinkPad {{560}} (these models don't have a fan)

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61p

2008-06-21T01:49:26Z

Chazchaz101: Changed to use Hardware Drivers to install Nvidia binaries

== Display / Video ==

To enable 3D acceleration, the proprietary NVidia driver must be installed. The first time you boot into 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.

If you want more options for configuring your video card than is provided by the Ubuntu control panels, you can install the nvidia control panel with

{{cmduser| sudo apt-get install nvidia-settings}}

which will add the Nvidia X Server Settings panel to the Administration menu.

Unfortunately, there are some annoying bugs in the NVidia driver. The most annoying one is that after resuming from suspend, you will often get a blank white screen. To get past it, simply type in your password and press enter, and you will be returned to your desktop. This bug is documented in Launchpad [https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/160264] and a partial workaround is available [https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/160264/comments/69]. The workaround may eventually become a part of Hardy.

Another problem is that the driver does not report the correct refresh rate to Compiz, resulting in rough animation. 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.

Next, Compiz animations are also 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. To solve 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 755 powermizer-loop powermizer-off

Then to make powermizer-off run on login, I opened System --> Preferences --> Sessions, clicked on Add, and entered the command "/home/argilo/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.

One final bug is that EDID (Extended Display Identification Data) is misdetected, which causes problems with font sizes and greatly 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.) To correct this problem, I added the following lines to /etc/X11/xorg.conf in the "Screen" section:

Option "UseEdidDpi" "FALSE"
Option "DPI" "96 x 96"
Option "UseEdidFreqs" "FALSE"
Option "HorizSync" "40-70"

The first two lines fix the font size issue, and the last two lines fix the resolution problem. I'm not sure if the 40-70 values are actually correct, since I just took them from someone else's xorg.conf, but they seem to work.

NVidia seems to have corrected the EDID misdetection bug in the latest version of their driver, but it's not available in Hardy and I'm not aware of any easy way to install it.

Talk:Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61p

2008-06-21T00:37:32Z

Chazchaz101: Envy not needed?

== Nvidia Binary Drivers ==
Envy is not required, at least for me, to install binary drivers and get compiz working. The Hardware Drivers administration panel offers to install it on the first boot. Is there any reason to use envy? [[User:Chazchaz101|Chazchaz101]] 02:37, 21 June 2008 (CEST)

Install Ubuntu Gutsy Gibbon on a T61p

2008-04-23T08:57:34Z

Chazchaz101: /* Fingerprint Reader */ Minor Link Cleanup

== Installing Gutsy Gibbon (7.10) on a T61p ==

== Introduction ==

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

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

== Installation Notes ==

Note: On lenovo t61p thinkpad with nVidia Corporation Quadro FX 570M graphics card the installer fails to create a usable xorg.conf file and the system reboots into an unusable black screen as X refuses to start. This is caused by the installer selecting the nv driver, which does not support this card. Using the vesa driver will allow X to start.

<ol>
<li>Install Ubuntu onto the laptop. The Live CD will boot in safe graphics mode for most users (but not all). However, the splash screen does not work for 64-bit users and perhaps 32-bit users as well. Be patient the system will boot, even though the screen is black. It may be faster to do the initial install using the alternate CD (text mode install).</li>

<li>After it is installed, fix issue: "no x session on first reboot after install" (see steps below)</li>
</ol>

To fix this, you have to reboot into rescue mode and hand-edit xorg.conf to use vesa driver until the restricted nvidia driver is enabled.

Steps:
<ol>
<li>Choose Recovery Mode from the Grub boot menu.</li>
<li>Edit the xorg.conf file:
{{cmdroot|nano /etc/X11/xorg.conf}}</li>
<li>Scroll down until you see the section listed below and replace nv with vesa on the driver line:

<code>
Section "Device"
Identifier "nVidia Corporation G80 [Quadro FX 570M]"
Driver "nv"
BusID "PCI:1:0:0"
EndSection
</code></li>
<li>Hit {{key|Ctrl}}{{key|X}} to exit, {{key|Y}} then {{key|Enter}} to save.</li>
<li>Reboot: {{cmdroot|reboot}}</li>
</ol>

You should now get the GUI login, but all of the accelerated graphics eye candy will be disabled until you have updated the nvidia drivers as per the Display/Video Section.

If you have a Ubuntu 7.10 DVD, you could use the same to first launch a live CD version of Ubuntu. When the live CD boots up it asks for the installation of restricted nVidia drivers (internet connection required). Once the restricted drivers are installed. Use the "Install" option from the live CD session to start the installation of Ubuntu.

==Alternate Fix==
#Boot from Ubuntu 7.10 Desktop CD
#If during the black screen you suspect that the Ubuntu Live CD is not going to boot, or you don't wish to wait, restart the installation and explicitly choose to install in safe graphics mode.
#When the safe graphics installation halts while trying to initialize the X server, press CTRL-ALT-F1 to bring up the command line.
#At the prompt, start X in Vesa mode with the command 'startx'. Continue the Live CD install as usual, switching back to the GUI installation process with CTRL-ALT-Function key if there are interrupting messages from another X server startup process.
#When the system restarts, skip to the command line again and when X fails to start, type 'startx' again to go into vesa mode.
#Now install the restricted nvidia drivers to resolve the problem.
[http://ubuntuforums.org/showpost.php?p=3566807&postcount=16 Citation]

== Display/Video ==

The '''nv''' driver does not support the Nvidia 570M card at all. To enable accelerated 3D support click System->Administration->Restricted Drivers Manager. It will allow you to download and install an updated set of nvidia drivers. {{NOTE| If this is a fresh installation, you will get an error "can't get source for nvidia-glx-new", which means you need to update the package list: first, be sure that in System->Administration->Software Sources, the entry "Proprietary drivers for devices (restricted)" is checked. Then either click System->Administration->Update Manager->Check, or open a terminal and type "sudo apt-get update".}} On the next reboot you should get accelerated support and full graphics resolution (but still no splashscreen).{{NOTE| If the Restricted Drivers Manager fails to install the driver you can use the Envy tool from: http://albertomilone.com/nvidia_scripts1.html. This tool is unsupported and the only supported method of installing the Nvidia drivers is via Synaptic or the Restricted Drivers Manager}}
On the model with 1920x1200 video, the default fonts are very tiny. Change them with System->Preferences->Appearance->Fonts->Details.

--[[User:Cmnorton|cmnorton]] 16:16, 20 March 2008 (CET)
I run my T61p in both a KVM (docked) and a solo environment. I found the only way to get the displays to work properly in both was to set the BIOS to VGA output (my KVM connectors are VGA), and use the vesa driver. Using other combinations with and without the nvidia driver caused display problems.

== Brightness ==
source: [[ Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61 ]]
====Nvidia Quadro N140 and 570M:====
The brightness controls do not work, however you can switch to a virtual terminal (ctrl+alt+F1) increase or decrease the brightness and then switch back to X (ctrl+alt+F7) without disrupting the running applications. In a few rare cases switching back to X (ctrl+alt+7) may freeze your computer with a black screen so save any open documents before switching out.

When using the '''vesa''' driver the brightness controls do work. So this problem seems to be related to the '''nvidia''' driver.

'''Update: Note that as of version 169.04 of the Nvidia driver brightness controls do work normally (with my 570M at least).''' (Gutsy Gibbon 7.10 comes with restricted Nvidia driver version 100.14). You can install the latest Nvidia binary drivers with "Envy" (see above)

== Audio ==
*Fix ALSA:
Gutsy uses ALSA v1.0.14 by default. Unfortunately, the audio card is not supported using that version. The solution is to upgrade to v1.0.15 or above. At the time of this writing, there are no packages for this version; however, new users should search Synaptic because that will make the process much easier: search for alsa-base and determine whether the available version is at least v1.0.15. If there are no packages available, the driver must be compiled from source. Follow this guide http://ubuntuforums.org/showthread.php?t=612605 to install the alsa v1.0.15.
After restarting, open a terminal and run alsamixer. Use the left/right arrow keys to select the channels; make sure that PCM and headphone are not muted (use m key). Muting/unmuting input channels can cause interference, so experiment to produce the best sound quality.
--[[User:Jbrown96|Jbrown96]] 22:57, 24 December 2007 (UTC)

I was unable to unmute sound using alsamixer or any other gui. Instead running this as root unmuted the channel and then everything worked fine. echo up > /proc/acpi/ibm/volume
--[[User:balsdorf|balsdorf]] 15:43, 30 January 2008

Everything except the mic works fine for me with ALSA 1.0.14. When I unmute the internal mic in alsamixer, it plays the mic sounds out the speakers.
--[[User:Chazchaz101|Chazchaz101]] 07:17, 28 December 2007 (UTC)

Same experience as Chazchaz101, but I could fix the microphone problem by adjusting the ALSA configuration as described in
source: [[Installing Ubuntu 7.10 (Gutsy_Gibbon) on a ThinkPad_T61#Microphone]].
--[[User:A-j|A-j]] 23:31, 28 January 2008 (UTC)

*fix sound buttons:
source: [[Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T61|Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T61]]

the volume control hotkeys are configured to control microphone volume out of the box.

fix: If you're using Gnome, from the System menu, click Preferences -> Sound, and in the Default Mixer Tracks field, choose PCM.

*fix volume control applet:

the volume control applet is configured to control microphone volume out of the box.

fix: If you're using Gnome, right-click the applet > preferences > Select the device and track to control

**do not change device (s/b HDA Intel)
**change track from Microphone to PCM

--[[User:Cmnorton|cmnorton]] 16:14, 20 March 2008 (CET)
In order to get sound to work, I added options snd-hda-intel model=thinkpad-t61p to the bottom of /etc/modprobe.d/alsa-base. This is referenced in [https://bugs.launchpad.net/ubuntu/+bug/122560] .

After installing the latest "BIOS update" with the ThinkVantage Update tool in Windows, sound was working on my laptop. I did not need to upgrade ALSA.
--[[User:gandy|gandy]] 14:55, 08 April 2008 (CET)

== Network/Internet ==

Some users report that IPv6 has large negative impact on internet connection speed (wired and wireless) on Ubuntu 7.10. If you are experiencing this, the following steps will allow you to disable IPv6 and restore your connection speed.
{{NOTE|There is a workaround to improve connectivity for Firefox. On the Firefox address bar type '''about:config''' and look for '''network.dns.disableIPv6''' and change its value to '''true'''[[Image:Ubuntu710_Firefox_Fix.png]].}}

Type the following in the terminal
{{cmduser|sudo gedit /etc/modprobe.d/aliases}}. The system may ask you to provide the Super User password. Once the file is opened, search for the following string, '''alias net-pf-10 ipv6'''.
Comment this line by prefixing a {{cmdresult|#}}. Now add a new line just below the commented line, '''alias net-pf-10 off'''.

[[Image:Update_to_Aliases.png]]

Now, save the file and restart Ubuntu.

Reference: Youtube video. [http://www.youtube.com/watch?v=Sd8nHsUevAY How-To: Fix a Slow Internet Connection in Ubuntu 7.10].

== Suspend with Nvidia Binary Driver ==

*Fix suspend with Nvidia binary drivers:

Follow the directions on the Ubuntu wiki. [https://help.ubuntu.com/community/NvidiaLaptopBinaryDriverSuspend Nvidia Binary Driver Suspend]

The link above reports "Note: enabling TwinView breaks suspend-to-ram (reported to work with drivers 96XX), if you know better please delete this note and write how you did it." I have not found a resolution, so if you know of one, please also delete this note and specify your solution. Thanks.

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

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

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

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

Paste the following script:

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

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

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

source: [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61]]

You can also create a launcher for this script that you can stick in the GNOME panel.

==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. At least for me, the most recent (0.3) version used here 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.

1) Add the launchpad repository to your sources:
{{cmduser| sudo gedit /etc/apt/sources.lst}}
note: if that file is not present or empty, try
{{cmduser| sudo gedit /etc/apt/sources.list}}
add the lines:
## LAUNCHPAD REPOSITORY
deb http://ppa.launchpad.net/jldugger/ubuntu gutsy main restricted universe multiverse
deb-src http://ppa.launchpad.net/jldugger/ubuntu gutsy main restricted universe multiverse

2) Install the following packages:

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

3) Test the package installation and connection to the reader:

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

A completed test 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:~$

4) 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.

5) Add User(s):
For each user:
{{cmduser| sudo tf-tool --add-user your_user_name}}

You can safely ignore the error:
Unable to set ACL of aquired file: /etc/pam_thinkfinger/charlie.bir: Operation not supported

6) 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}}
add the line:
uinput

At this point, you should be ready to swipe!

Sources:
* [https://wiki.ubuntu.com/ThinkFinger Ubuntu Wiki: ThinkFinger on Ubuntu]
* [[Installing_Ubuntu_6.06_on_a_ThinkPad_T43#Fingerprint_Reader|Installing Ubuntu 6.06 on a ThinkPad T43]]

==Touchpad and TouchPoint==
===Touchpad===
In order to adjust the Touchpad sensitivity and settings such as side scrolling and tapping, you must install the xserver-xorg-input-synaptics package:
{{cmduser| sudo apt-get install xserver-xorg-input-synaptics}}
If the newly installed Touchpad control panel gives you an error, you may will to modify your xorg.conf file.
{{cmduser| sudo gedit /etc/X11/xorg.conf}}

Add the line:
InputDevice "Touchpad"
to the ServerLayout section add the following lines before any existing mouse or pointer entries:
Section "InputDevice"
Identifier "Touchpad"
Driver "synaptics"
option "SendCoreEvents" "true"
option "Device" "/dev/psaux"
option "Protocol" "auto-dev"
option "HorizScrollDelta" "0"
option "SHMConfig" "on"
option "MaxTapTime" "180"
Option "ZAxisMapping" "4 5 6 7"
Option "Buttons" "9"
EndSection
This should allow you to open the Touchpad panel in the preferences menu and make permanent changes to the settings.
===TrackPoint===
In order to set the TrackPoint speed and sensitivity temporarily, you can can echo values between 0 and 255 to the proper sysfs location for example:

{{cmduser| echo -n 255|sudo tee /sys/devices/platform/i8042/serio1/serio2/speed}}

to set the speed to max or

{{cmduser| echo -n 76|sudo tee /sys/devices/platform/i8042/serio1/serio2/speed}}

to set the speed to 76.
In order to make these settings persist over reboots, you have to edit your rc.local:

{{cmduser| sudo gedit /etc/rc.local}}

and the following lines: before the line that says exit 0 :
echo -n 255 > /sys/devices/platform/i8042/serio1/serio2/sensitivity
echo -n 76 > /sys/devices/platform/i8042/serio1/serio2/speed
where the numbers are the same as the values as the temporary settings you want.

{{NOTE|Many how-to guides for other distros use the sysfsutils package and the accompanying sysfs.config file for setting the values instead of using rc.local. Unfortunately, it appears that Gutsy does not process this file at startup, so rc.local must be used instead.}}

Sources:
*Trackpad: [https://bugs.launchpad.net/ubuntu/+source/linux/+bug/163141/comments/8 Touchpad recognized as generic mouse on Thinkpad R61 laptop]
*TouchPoint: [[How_to_configure_the_TrackPoint|How to Configure the TrackPoint]]

[[Category:T61p]]

Install Ubuntu Gutsy Gibbon on a T61p

2008-04-23T08:53:37Z

Chazchaz101: Added Trackpad and Touchpoint Configuration

== Installing Gutsy Gibbon (7.10) on a T61p ==

== Introduction ==

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

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

== Installation Notes ==

Note: On lenovo t61p thinkpad with nVidia Corporation Quadro FX 570M graphics card the installer fails to create a usable xorg.conf file and the system reboots into an unusable black screen as X refuses to start. This is caused by the installer selecting the nv driver, which does not support this card. Using the vesa driver will allow X to start.

<ol>
<li>Install Ubuntu onto the laptop. The Live CD will boot in safe graphics mode for most users (but not all). However, the splash screen does not work for 64-bit users and perhaps 32-bit users as well. Be patient the system will boot, even though the screen is black. It may be faster to do the initial install using the alternate CD (text mode install).</li>

<li>After it is installed, fix issue: "no x session on first reboot after install" (see steps below)</li>
</ol>

To fix this, you have to reboot into rescue mode and hand-edit xorg.conf to use vesa driver until the restricted nvidia driver is enabled.

Steps:
<ol>
<li>Choose Recovery Mode from the Grub boot menu.</li>
<li>Edit the xorg.conf file:
{{cmdroot|nano /etc/X11/xorg.conf}}</li>
<li>Scroll down until you see the section listed below and replace nv with vesa on the driver line:

<code>
Section "Device"
Identifier "nVidia Corporation G80 [Quadro FX 570M]"
Driver "nv"
BusID "PCI:1:0:0"
EndSection
</code></li>
<li>Hit {{key|Ctrl}}{{key|X}} to exit, {{key|Y}} then {{key|Enter}} to save.</li>
<li>Reboot: {{cmdroot|reboot}}</li>
</ol>

You should now get the GUI login, but all of the accelerated graphics eye candy will be disabled until you have updated the nvidia drivers as per the Display/Video Section.

If you have a Ubuntu 7.10 DVD, you could use the same to first launch a live CD version of Ubuntu. When the live CD boots up it asks for the installation of restricted nVidia drivers (internet connection required). Once the restricted drivers are installed. Use the "Install" option from the live CD session to start the installation of Ubuntu.

==Alternate Fix==
#Boot from Ubuntu 7.10 Desktop CD
#If during the black screen you suspect that the Ubuntu Live CD is not going to boot, or you don't wish to wait, restart the installation and explicitly choose to install in safe graphics mode.
#When the safe graphics installation halts while trying to initialize the X server, press CTRL-ALT-F1 to bring up the command line.
#At the prompt, start X in Vesa mode with the command 'startx'. Continue the Live CD install as usual, switching back to the GUI installation process with CTRL-ALT-Function key if there are interrupting messages from another X server startup process.
#When the system restarts, skip to the command line again and when X fails to start, type 'startx' again to go into vesa mode.
#Now install the restricted nvidia drivers to resolve the problem.
[http://ubuntuforums.org/showpost.php?p=3566807&postcount=16 Citation]

== Display/Video ==

The '''nv''' driver does not support the Nvidia 570M card at all. To enable accelerated 3D support click System->Administration->Restricted Drivers Manager. It will allow you to download and install an updated set of nvidia drivers. {{NOTE| If this is a fresh installation, you will get an error "can't get source for nvidia-glx-new", which means you need to update the package list: first, be sure that in System->Administration->Software Sources, the entry "Proprietary drivers for devices (restricted)" is checked. Then either click System->Administration->Update Manager->Check, or open a terminal and type "sudo apt-get update".}} On the next reboot you should get accelerated support and full graphics resolution (but still no splashscreen).{{NOTE| If the Restricted Drivers Manager fails to install the driver you can use the Envy tool from: http://albertomilone.com/nvidia_scripts1.html. This tool is unsupported and the only supported method of installing the Nvidia drivers is via Synaptic or the Restricted Drivers Manager}}
On the model with 1920x1200 video, the default fonts are very tiny. Change them with System->Preferences->Appearance->Fonts->Details.

--[[User:Cmnorton|cmnorton]] 16:16, 20 March 2008 (CET)
I run my T61p in both a KVM (docked) and a solo environment. I found the only way to get the displays to work properly in both was to set the BIOS to VGA output (my KVM connectors are VGA), and use the vesa driver. Using other combinations with and without the nvidia driver caused display problems.

== Brightness ==
source: [[ Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61 ]]
====Nvidia Quadro N140 and 570M:====
The brightness controls do not work, however you can switch to a virtual terminal (ctrl+alt+F1) increase or decrease the brightness and then switch back to X (ctrl+alt+F7) without disrupting the running applications. In a few rare cases switching back to X (ctrl+alt+7) may freeze your computer with a black screen so save any open documents before switching out.

When using the '''vesa''' driver the brightness controls do work. So this problem seems to be related to the '''nvidia''' driver.

'''Update: Note that as of version 169.04 of the Nvidia driver brightness controls do work normally (with my 570M at least).''' (Gutsy Gibbon 7.10 comes with restricted Nvidia driver version 100.14). You can install the latest Nvidia binary drivers with "Envy" (see above)

== Audio ==
*Fix ALSA:
Gutsy uses ALSA v1.0.14 by default. Unfortunately, the audio card is not supported using that version. The solution is to upgrade to v1.0.15 or above. At the time of this writing, there are no packages for this version; however, new users should search Synaptic because that will make the process much easier: search for alsa-base and determine whether the available version is at least v1.0.15. If there are no packages available, the driver must be compiled from source. Follow this guide http://ubuntuforums.org/showthread.php?t=612605 to install the alsa v1.0.15.
After restarting, open a terminal and run alsamixer. Use the left/right arrow keys to select the channels; make sure that PCM and headphone are not muted (use m key). Muting/unmuting input channels can cause interference, so experiment to produce the best sound quality.
--[[User:Jbrown96|Jbrown96]] 22:57, 24 December 2007 (UTC)

I was unable to unmute sound using alsamixer or any other gui. Instead running this as root unmuted the channel and then everything worked fine. echo up > /proc/acpi/ibm/volume
--[[User:balsdorf|balsdorf]] 15:43, 30 January 2008

Everything except the mic works fine for me with ALSA 1.0.14. When I unmute the internal mic in alsamixer, it plays the mic sounds out the speakers.
--[[User:Chazchaz101|Chazchaz101]] 07:17, 28 December 2007 (UTC)

Same experience as Chazchaz101, but I could fix the microphone problem by adjusting the ALSA configuration as described in
source: [[Installing Ubuntu 7.10 (Gutsy_Gibbon) on a ThinkPad_T61#Microphone]].
--[[User:A-j|A-j]] 23:31, 28 January 2008 (UTC)

*fix sound buttons:
source: [[Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T61|Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T61]]

the volume control hotkeys are configured to control microphone volume out of the box.

fix: If you're using Gnome, from the System menu, click Preferences -> Sound, and in the Default Mixer Tracks field, choose PCM.

*fix volume control applet:

the volume control applet is configured to control microphone volume out of the box.

fix: If you're using Gnome, right-click the applet > preferences > Select the device and track to control

**do not change device (s/b HDA Intel)
**change track from Microphone to PCM

--[[User:Cmnorton|cmnorton]] 16:14, 20 March 2008 (CET)
In order to get sound to work, I added options snd-hda-intel model=thinkpad-t61p to the bottom of /etc/modprobe.d/alsa-base. This is referenced in [https://bugs.launchpad.net/ubuntu/+bug/122560] .

After installing the latest "BIOS update" with the ThinkVantage Update tool in Windows, sound was working on my laptop. I did not need to upgrade ALSA.
--[[User:gandy|gandy]] 14:55, 08 April 2008 (CET)

== Network/Internet ==

Some users report that IPv6 has large negative impact on internet connection speed (wired and wireless) on Ubuntu 7.10. If you are experiencing this, the following steps will allow you to disable IPv6 and restore your connection speed.
{{NOTE|There is a workaround to improve connectivity for Firefox. On the Firefox address bar type '''about:config''' and look for '''network.dns.disableIPv6''' and change its value to '''true'''[[Image:Ubuntu710_Firefox_Fix.png]].}}

Type the following in the terminal
{{cmduser|sudo gedit /etc/modprobe.d/aliases}}. The system may ask you to provide the Super User password. Once the file is opened, search for the following string, '''alias net-pf-10 ipv6'''.
Comment this line by prefixing a {{cmdresult|#}}. Now add a new line just below the commented line, '''alias net-pf-10 off'''.

[[Image:Update_to_Aliases.png]]

Now, save the file and restart Ubuntu.

Reference: Youtube video. [http://www.youtube.com/watch?v=Sd8nHsUevAY How-To: Fix a Slow Internet Connection in Ubuntu 7.10].

== Suspend with Nvidia Binary Driver ==

*Fix suspend with Nvidia binary drivers:

Follow the directions on the Ubuntu wiki. [https://help.ubuntu.com/community/NvidiaLaptopBinaryDriverSuspend Nvidia Binary Driver Suspend]

The link above reports "Note: enabling TwinView breaks suspend-to-ram (reported to work with drivers 96XX), if you know better please delete this note and write how you did it." I have not found a resolution, so if you know of one, please also delete this note and specify your solution. Thanks.

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

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

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

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

Paste the following script:

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

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

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

source: [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61]]

You can also create a launcher for this script that you can stick in the GNOME panel.

==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. At least for me, the most recent (0.3) version used here 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.

1) Add the launchpad repository to your sources:
{{cmduser| sudo gedit /etc/apt/sources.lst}}
note: if that file is not present or empty, try
{{cmduser| sudo gedit /etc/apt/sources.list}}
add the lines:
## LAUNCHPAD REPOSITORY
deb http://ppa.launchpad.net/jldugger/ubuntu gutsy main restricted universe multiverse
deb-src http://ppa.launchpad.net/jldugger/ubuntu gutsy main restricted universe multiverse

2) Install the following packages:

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

3) Test the package installation and connection to the reader:

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

A completed test 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:~$

4) 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.

5) Add User(s):
For each user:
{{cmduser| sudo tf-tool --add-user your_user_name}}

You can safely ignore the error:
Unable to set ACL of aquired file: /etc/pam_thinkfinger/charlie.bir: Operation not supported

6) 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}}
add the line:
uinput

At this point, you should be ready to swipe!

Sources:
* Install ThinkFinger on Ubuntu: https://wiki.ubuntu.com/ThinkFinger
* [[Installing_Ubuntu_6.06_on_a_ThinkPad_T43#Fingerprint_Reader|Installing Ubuntu 6.06 on a ThinkPad T43]]

==Touchpad and TouchPoint==
===Touchpad===
In order to adjust the Touchpad sensitivity and settings such as side scrolling and tapping, you must install the xserver-xorg-input-synaptics package:
{{cmduser| sudo apt-get install xserver-xorg-input-synaptics}}
If the newly installed Touchpad control panel gives you an error, you may will to modify your xorg.conf file.
{{cmduser| sudo gedit /etc/X11/xorg.conf}}

Add the line:
InputDevice "Touchpad"
to the ServerLayout section add the following lines before any existing mouse or pointer entries:
Section "InputDevice"
Identifier "Touchpad"
Driver "synaptics"
option "SendCoreEvents" "true"
option "Device" "/dev/psaux"
option "Protocol" "auto-dev"
option "HorizScrollDelta" "0"
option "SHMConfig" "on"
option "MaxTapTime" "180"
Option "ZAxisMapping" "4 5 6 7"
Option "Buttons" "9"
EndSection
This should allow you to open the Touchpad panel in the preferences menu and make permanent changes to the settings.
===TrackPoint===
In order to set the TrackPoint speed and sensitivity temporarily, you can can echo values between 0 and 255 to the proper sysfs location for example:

{{cmduser| echo -n 255|sudo tee /sys/devices/platform/i8042/serio1/serio2/speed}}

to set the speed to max or

{{cmduser| echo -n 76|sudo tee /sys/devices/platform/i8042/serio1/serio2/speed}}

to set the speed to 76.
In order to make these settings persist over reboots, you have to edit your rc.local:

{{cmduser| sudo gedit /etc/rc.local}}

and the following lines: before the line that says exit 0 :
echo -n 255 > /sys/devices/platform/i8042/serio1/serio2/sensitivity
echo -n 76 > /sys/devices/platform/i8042/serio1/serio2/speed
where the numbers are the same as the values as the temporary settings you want.

{{NOTE|Many how-to guides for other distros use the sysfsutils package and the accompanying sysfs.config file for setting the values instead of using rc.local. Unfortunately, it appears that Gutsy does not process this file at startup, so rc.local must be used instead.}}

Sources:
*Trackpad: [https://bugs.launchpad.net/ubuntu/+source/linux/+bug/163141/comments/8 Touchpad recognized as generic mouse on Thinkpad R61 laptop]
*TouchPoint: [[How_to_configure_the_TrackPoint|How to Configure the TrackPoint]]

[[Category:T61p]]

Patch for controlling fan speed

2008-03-24T00:08:41Z

Chazchaz101:

==Overview==

{{NOTE|The patch is no longer necessary with kernel > 2.6.10. After opening a root shell with '''$sudo -s''', you should be able to run al of these commands. See: [[How_to_control_fan_speed|How to control fan speed]]}}

This patch extends the [[ibm-acpi]] Linux kernel module to control fan speed. It can be used to reduce [[Problem with fan noise|fan noise]] (both speed and pulsing) and to decrease fan power consumption.

When this patch is applied and the <tt>ibm-acpi</tt> module is loaded with the <tt>experimental=1</tt> module parameter, the following new capabilities are added to {{path|/proc/acpi/ibm/fan}}:
* {{cmdroot|echo level LEVEL > /proc/acpi/ibm/fan}} sets a fan speed level between 0 and 7, where <tt>LEVEL</TT>=0 means fan off and <tt>LEVEL</tt>=7 is the fastest speed.
* {{cmdroot|echo level auto > /proc/acpi/ibm/fan}} tells the embedded controller to set the fan speed automatically according to system temperatures (this is the default).
* {{cmdroot|echo level disengaged > /proc/acpi/ibm/fan}} tells the embedded controller to disengage fan speed control (see specs below).
* {{cmdroot|cat /proc/acpi/ibm/fan}} shows the current fan level (in addition to the fan speed in RPM).

For example:

'''#cat /proc/acpi/ibm/fan'''
status: enabled
level: auto
speed: 4219
commands: enable, disable, level <level>
(<level> is 0-7, auto or disengaged)

'''#echo level 2 > /proc/acpi/ibm/fan'''

'''#cat /proc/acpi/ibm/fan'''
status: enabled
level: 2
speed: 3142
commands: enable, disable, level <level>
(<level> is 0-7, auto or disengaged)

This patch is best used with an [[ACPI fan control script#Variable speed control scripts|ACPI fan control script]] that monitors system temperature and sets the fan speed accordingly.

{{WARN|Overriding the system's automatic temperature control may cause permanent hardware damage. Even when using temperature monitoring software, it is not clear whether the software can access all temperature sensor accessible to the embedded controller and understand them correctly. Moreover, this patch relies on an undocumented hardware interface, and may thus have arbitrary effects (especially on models it wasn't tested on).}}

==The patch==

===for ibm-acpi 0.11===
{{CodeRef|ibm-acpi-0.11-2.6.13-fan.patch}}

This also includes a minor fix (rename of <tt>device_add</tt>) to make [[ibm-acpi]] 0.11 compile on kernel 2.6.13.

===for ibm-acpi 0.12a as found in kernels 2.6.14 and 2.6.17===

A slightly modified version which also keeps the lines in the format expected by the gkrellm plugin.

{{CodeRef|ibm-acpi-0.12a-2.6.14-fan.patch}}

{{CodeRef|ibm-acpi-0.12a-2.6.17-fan.patch}}

{{NOTE|In order to patch the ibm_acpi.c file you have to issue the following command: <code>patch -p0 -l < fanpatch</code>. The '-l' option is important because the patch pasted here doesn't have any tabs any more. Another piece of advice: Always try to patch the files first before really patching them. That is done by adding --dry-run to the command.}}

===Ideas for improvement===

* When fan speed is controlled from userspace (e.g., by the [[ACPI fan control script#Variable speed control scripts|ACPI fan control scripts]]), the userspace component may die (for whatever reason) leaving the fan at a low speed, potentially leading to damage. We can add a watchdog to the kernel component, which resets the fan to Embedded Controller control (<tt>leve: auto</tt>) if {{path|/proc/acpi/ibm/fan}} was not written to for ''N'' seconds.

==Alternative methods and hardware specs==

See [[How to control fan speed]].

==Supported models==

See [[How to control fan speed]].

[[Category:Patches]]

Patch for controlling fan speed

2008-03-24T00:07:48Z

Chazchaz101: change to previous note

==Overview==

{{NOTE|The patch is no longer necessary. After opening a root shell with '''$sudo -s''', you should be able to run al of these commands See [[How_to_control_fan_speed|How to control fan speed]]}}

This patch extends the [[ibm-acpi]] Linux kernel module to control fan speed. It can be used to reduce [[Problem with fan noise|fan noise]] (both speed and pulsing) and to decrease fan power consumption.

When this patch is applied and the <tt>ibm-acpi</tt> module is loaded with the <tt>experimental=1</tt> module parameter, the following new capabilities are added to {{path|/proc/acpi/ibm/fan}}:
* {{cmdroot|echo level LEVEL > /proc/acpi/ibm/fan}} sets a fan speed level between 0 and 7, where <tt>LEVEL</TT>=0 means fan off and <tt>LEVEL</tt>=7 is the fastest speed.
* {{cmdroot|echo level auto > /proc/acpi/ibm/fan}} tells the embedded controller to set the fan speed automatically according to system temperatures (this is the default).
* {{cmdroot|echo level disengaged > /proc/acpi/ibm/fan}} tells the embedded controller to disengage fan speed control (see specs below).
* {{cmdroot|cat /proc/acpi/ibm/fan}} shows the current fan level (in addition to the fan speed in RPM).

For example:

'''#cat /proc/acpi/ibm/fan'''
status: enabled
level: auto
speed: 4219
commands: enable, disable, level <level>
(<level> is 0-7, auto or disengaged)

'''#echo level 2 > /proc/acpi/ibm/fan'''

'''#cat /proc/acpi/ibm/fan'''
status: enabled
level: 2
speed: 3142
commands: enable, disable, level <level>
(<level> is 0-7, auto or disengaged)

This patch is best used with an [[ACPI fan control script#Variable speed control scripts|ACPI fan control script]] that monitors system temperature and sets the fan speed accordingly.

{{WARN|Overriding the system's automatic temperature control may cause permanent hardware damage. Even when using temperature monitoring software, it is not clear whether the software can access all temperature sensor accessible to the embedded controller and understand them correctly. Moreover, this patch relies on an undocumented hardware interface, and may thus have arbitrary effects (especially on models it wasn't tested on).}}

==The patch==

===for ibm-acpi 0.11===
{{CodeRef|ibm-acpi-0.11-2.6.13-fan.patch}}

This also includes a minor fix (rename of <tt>device_add</tt>) to make [[ibm-acpi]] 0.11 compile on kernel 2.6.13.

===for ibm-acpi 0.12a as found in kernels 2.6.14 and 2.6.17===

A slightly modified version which also keeps the lines in the format expected by the gkrellm plugin.

{{CodeRef|ibm-acpi-0.12a-2.6.14-fan.patch}}

{{CodeRef|ibm-acpi-0.12a-2.6.17-fan.patch}}

{{NOTE|In order to patch the ibm_acpi.c file you have to issue the following command: <code>patch -p0 -l < fanpatch</code>. The '-l' option is important because the patch pasted here doesn't have any tabs any more. Another piece of advice: Always try to patch the files first before really patching them. That is done by adding --dry-run to the command.}}

===Ideas for improvement===

* When fan speed is controlled from userspace (e.g., by the [[ACPI fan control script#Variable speed control scripts|ACPI fan control scripts]]), the userspace component may die (for whatever reason) leaving the fan at a low speed, potentially leading to damage. We can add a watchdog to the kernel component, which resets the fan to Embedded Controller control (<tt>leve: auto</tt>) if {{path|/proc/acpi/ibm/fan}} was not written to for ''N'' seconds.

==Alternative methods and hardware specs==

See [[How to control fan speed]].

==Supported models==

See [[How to control fan speed]].

[[Category:Patches]]

Talk:Patch for controlling fan speed

2008-03-24T00:04:43Z

Chazchaz101: Question about sudo

==Using sudo==
Any idea why I have to use '''sudo -s''' first instead of just using '''sudo <command>'''?

==Windows XP port==
How would I port this patch to Windows XP?

--Jason

You can't. But you can write a Windows device driver based on the specs and [[ibm-acpi]].

--[[User:Thinker|Thinker]] 18:54, 7 Nov 2005 (CET)

==gkrellm support==

I can confirm that it works on Thinkpad {{T43}} here. However after
applying the patch, the fan speed monitor of gkrellm 2.2.7 cannot read
value correctly. Maybe we gkrellm is reading the second line for speed
but instead find the line for level, so it got confused? Would it be possible to interchange the lines so that speed still appears in the
second line and level appears in the third instead? I'm no coder, just
a suggestion to improve the patch.

--Jiang

I'd say it's a bug in gkrellm. It should parse the line header rather than relying on line numbers. But feel free to change (and test) the patch if you wish.

--[[User:Thinker|Thinker]] 05:14, 26 Oct 2005 (CEST)

== patch to keep gkrell working against 2.6.14 ==

As in "works for me on a T43p", use with caution at your own risk. And thanks to thinker for the original patch, very nice work.

(See article for the actual patch)

--[[User:Spiney|Spiney]]

Looks excellent, why not add it to the article page? Also, care to provide a license (preferably public domain like my patch) so the kernel guys can handle it? Speaking of which, the kernel people seem to like their patches generated via "diff -up vanilla-kernel-2.6.14 patched-kernel-2.6.14".

--[[User:Thinker|Thinker]] 22:04, 1 Nov 2005 (CET)

Done, using the -p option for diff and "borrowing" your sentence for licensing purposes.

--[[User:Spiney|Spiney]]
----

== Updated script for unpatched kernels ==
Moved to the [[ACPI fan control script]] article page, after joint development by [[User:Spiney|Spiney]] and [[User:Thinker|Thinker]].

== whats the problem kernel 2.6.14 ==

hi all,

i patched the kernel with the patch for 2.6.14 with the option:
/usr/src/linux # patch -p0 -l -i ../ibm_acpi.patch (which i copy&pasted)

they dont show me errors or so. but after i reboot and load the modul ibm_acpi i cant see any /proc/acpi/ibm/fan

whats the problem? copy&past ( tab -> space?)
or is it a problem in my kernel config?

greetings and big thx from .ch,

system: ibm thinkpad t43p
kernel: 2.6.14

--[[User:62.203.29.204|62.203.29.204]] 19:22, 9 Nov 2005 (CET)kru

You need to pass the "<tt>experimental=1</tt>" module parameter to ibm-acpi:
# modprobe ibm_acpi experimental=1
--[[User:Thinker|Thinker]] 21:01, 9 Nov 2005 (CET)

big thx!!! problem solved.

--[[User:62.203.29.204|62.203.29.204]]

== Fan control does not work with Suse 10.1 ? ==

Hi,

I successfully installed and used the fan control script on my T43p with Suse 10.0.

Yesterday, I installed Suse 10.1 from scratch. Unfortunately fan control does not work with Suse 10.1:

\# echo level 2 > /proc/acpi/ibm/fan
bash: echo: write error: Invalid argument

Are there any substantial differences between Suse 10.0 and 10.1 with respect to ibm_acpi?

== Speed Control Patch for 2.6.18? ==

Hi All.
I'm trying to apply the speed control patch to vanilla 2.6.18 but it looks like it failed. Anyone who can point me to a direction for 2.6.18 patch?
Thanks

== ibm-acpi-0.12a-2.6.17-fan.patch broken? ==
The code is not completed.

Patch for controlling fan speed

2008-03-23T23:59:55Z

Chazchaz101: Note about the patch not being needed on 2.6.22-14

==Overview==

{{NOTE|It appears that the patch is no longer necessary. After opening a root shell with '''$sudo -s''', I was able to run these commands without problems with Ubuntu 6.10 default kernel (2.6.22-14-generic).}}

This patch extends the [[ibm-acpi]] Linux kernel module to control fan speed. It can be used to reduce [[Problem with fan noise|fan noise]] (both speed and pulsing) and to decrease fan power consumption.

When this patch is applied and the <tt>ibm-acpi</tt> module is loaded with the <tt>experimental=1</tt> module parameter, the following new capabilities are added to {{path|/proc/acpi/ibm/fan}}:
* {{cmdroot|echo level LEVEL > /proc/acpi/ibm/fan}} sets a fan speed level between 0 and 7, where <tt>LEVEL</TT>=0 means fan off and <tt>LEVEL</tt>=7 is the fastest speed.
* {{cmdroot|echo level auto > /proc/acpi/ibm/fan}} tells the embedded controller to set the fan speed automatically according to system temperatures (this is the default).
* {{cmdroot|echo level disengaged > /proc/acpi/ibm/fan}} tells the embedded controller to disengage fan speed control (see specs below).
* {{cmdroot|cat /proc/acpi/ibm/fan}} shows the current fan level (in addition to the fan speed in RPM).

For example:

'''#cat /proc/acpi/ibm/fan'''
status: enabled
level: auto
speed: 4219
commands: enable, disable, level <level>
(<level> is 0-7, auto or disengaged)

'''#echo level 2 > /proc/acpi/ibm/fan'''

'''#cat /proc/acpi/ibm/fan'''
status: enabled
level: 2
speed: 3142
commands: enable, disable, level <level>
(<level> is 0-7, auto or disengaged)

This patch is best used with an [[ACPI fan control script#Variable speed control scripts|ACPI fan control script]] that monitors system temperature and sets the fan speed accordingly.

{{WARN|Overriding the system's automatic temperature control may cause permanent hardware damage. Even when using temperature monitoring software, it is not clear whether the software can access all temperature sensor accessible to the embedded controller and understand them correctly. Moreover, this patch relies on an undocumented hardware interface, and may thus have arbitrary effects (especially on models it wasn't tested on).}}

==The patch==

===for ibm-acpi 0.11===
{{CodeRef|ibm-acpi-0.11-2.6.13-fan.patch}}

This also includes a minor fix (rename of <tt>device_add</tt>) to make [[ibm-acpi]] 0.11 compile on kernel 2.6.13.

===for ibm-acpi 0.12a as found in kernels 2.6.14 and 2.6.17===

A slightly modified version which also keeps the lines in the format expected by the gkrellm plugin.

{{CodeRef|ibm-acpi-0.12a-2.6.14-fan.patch}}

{{CodeRef|ibm-acpi-0.12a-2.6.17-fan.patch}}

{{NOTE|In order to patch the ibm_acpi.c file you have to issue the following command: <code>patch -p0 -l < fanpatch</code>. The '-l' option is important because the patch pasted here doesn't have any tabs any more. Another piece of advice: Always try to patch the files first before really patching them. That is done by adding --dry-run to the command.}}

===Ideas for improvement===

* When fan speed is controlled from userspace (e.g., by the [[ACPI fan control script#Variable speed control scripts|ACPI fan control scripts]]), the userspace component may die (for whatever reason) leaving the fan at a low speed, potentially leading to damage. We can add a watchdog to the kernel component, which resets the fan to Embedded Controller control (<tt>leve: auto</tt>) if {{path|/proc/acpi/ibm/fan}} was not written to for ''N'' seconds.

==Alternative methods and hardware specs==

See [[How to control fan speed]].

==Supported models==

See [[How to control fan speed]].

[[Category:Patches]]

How to enable integrated fingerprint reader with BioAPI

2008-01-08T06:37:21Z

Chazchaz101: /* Bioapi error #3 */ Fixed typo

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
This page describes the process of getting the [[Integrated Fingerprint Reader|integrated fingerprint reader]] to work under Linux, using bioapi and binary-only drivers. It is based on experiences in {{Ubuntu}} on a T43. The same works on {{Fedora}} 4 and 5, RHEL4, SuSE 9.3, SuSE 10, and {{Gentoo}}. Note that experimental open-source driver is available, see [[How to enable the fingerprint reader with ThinkFinger|the apropriate page]] for details.
|}

==Basic installation==
===Installing the bioapi framework===
====Automated installation script====
The [[Script for enabling the fingerprint reader]] automates the installation of most components (bioapi framework, driver, pam_bioapi, pam setup, device permissions, pamtester and enrolling), for some Linux distributions.

====Binary packages====

Note that these packages only take care of this one section. If you can use one, you should do so and then proceed to the section entitled, Installing and Configuring the Driver.

=====Debian/ Ubuntu Dapper=====
*If you're using {{Debian}} Sid (the unstable branch) or {{Ubuntu}} Dapper Drake 6.06 LTS you can try the packages from Michael R. Crusoe's site, either [http://www.qrivy.net/~michael/temp/ version 1.2.3] (recommended) or [http://www.qrivy.net/~michael/debs/unstable/ older versions] which might not work with the steps in this howto.

{{HINT|Ignore the warning about not finding ''/usr/lib/libqtpwbsp.so'', it's not fatal.}}

=====Gentoo=====
Gentoo now includes needed ebuilds. Just run

''ACCEPT_KEYWORDS=~x86 emerge pam_bioapi''

You can also grab the [http://www.qrivy.net/~michael/blua/bioapi/bioapi-1.2.2.ebuild.tar.bz2 ebuild], or use the source-install procedure below.

Also see [http://toe.ch/~tsa/ibm-fingerprint/ http://toe.ch/~tsa/ibm-fingerprint/] for alternative documentation on installing on Gentoo including ebuilds for all the packages used.

=====Fedora Core=====
RPM packages for Fedora Core and installation instructions are available [[Installing Fedora Core 5 on a ThinkPad X41 Tablet#Fingerprint_Reader|here]]

====Installing from source====
{{HINT|
For ubuntu (Gutsy) you'll need at least the:
build-essential
automake
packages, or building will fail.
}}
*Get the bioapi source:
:{{cmduser|wget http://bioapi-linux.googlecode.com/files/bioapi_1.2.3.tar.gz}}
*I could not compile bioapi with the graphical Qt tools. To do it manually, do the following:
:{{cmduser|tar xzf bioapi_1.2.3.tar.gz}}
:{{cmduser|cd bioapi-1.2.3}}
:{{cmduser|1=./configure --with-Qt-dir=no}}
:{{cmduser|make}}
:and then as root
:{{cmdroot|make install}}
:If make install fails, be sure you're root and then:
:{{cmdroot|1=export LD_LIBRARY_PATH=/usr/local/lib}}
:{{cmdroot|make install}}
:and if you want to compile [http://code.google.com/p/pam-bioapi/ pam_bioapi] for auth later
:{{cmdroot|cp include/bioapi_util.h include/installdefs.h imports/cdsa/v2_0/inc/cssmtype.h /usr/include}}
:Be aware that checkinstall will not work!
:(I got through configure with Qt, but got a cryptic build error. It all worked fine with Qt disabled as above)
:buzz: This is due to a wrong qt include path, set it manually in configure and everything should work.
*Bioapi (at least version 1.2.2) doesn't compile with GCC4. You need to patch it:
*This is neccessary to compile on SUSE 10.1 which it using gcc version 4.1.0.
:{{cmduser|wget http://upir.cz/linux/patches/bioapi-1.2.2-gcc4.patch}}
:{{cmduser|patch -p1 < bioapi-1.2.2-gcc4.patch}}
*Patch for gcc 4.1 is available here - http://cvs.pld-linux.org/cgi-bin/cvsweb/SOURCES/bioapi-c++.patch?rev=1.3
* By default, bioapi will install numerous files in {{path|/usr/local/<nowiki>{</nowiki>bin,lib,include<nowiki>}</nowiki>}}, including files with "self-explanatory" names such as {{path|/usr/local/bin/Sample}}. To prevent this pollution:
:Create a dedicated directory, for example {{path|/opt/bioapi}} .
:Append <tt>--prefix=/opt/bioapi</tt> to the above <tt>./configure</tt> command.
:Append {{path|/opt/bioapi/bin}} to <tt>$PATH</tt> and {{path|/opt/bioapi/lib}} to <tt>$LD_LIBRARY_PATH</tt>.
:When installing the driver (below), tell it the new install path: {{cmdroot|sh install.sh /opt/bioapi/lib}}

====Adjusting ldconfigs library search path====
At least on {{Fedora}} or {{Aurox}} 11, you may need to add {{path|/usr/local/lib}} to the library path so that the libraries referenced from <tt>pam_bioapi.so</tt> get picked up properly. The usual way to do this is adding it to the ldconfig configuration:
:{{cmdroot|echo '/usr/local/lib' > /etc/ld.so.conf.d/bioapi.conf}}
:{{cmdroot|ldconfig}}
Alternatively you can add it to the LD_LIBRARY variable.

If you see bioapi libs in the output of
:{{cmdroot|ldconfig -p | grep bioapi}}
then it should work.

===Installing and configuring the driver===
====Installing the driver====
*Download {{path|TFMESS_BSP_LIN_1.0.zip}} from the [http://www.upek.com/support/dl_linux_bsp.asp UPEK support site] and unzip it into a seperate folder, as it will not create one.
*Change to that folder and do as root:
:{{cmdroot|sh install.sh}}
:If you're running Gentoo, Debian or Ubuntu Dapper, use
:{{cmdroot|sh install.sh /usr/lib}}
{{HINT|
For me it didn't work this way, but following did:
:sh install.sh /usr/local/lib
greetings, tec}}
{{HINT|On my debian install I had to "cp libtfmessbsp.so /usr/lib" to avoid a errormessage during "sh install.sh /usr/lib": "Could not find file:/usr/lib/libtfmessbsp.so"}}
:If that fails, it may be that make install failed up above -- try setting LD_LIBRARY_PATH, do the make install again, and come back here and try this again. You also need {{cmd|mod_install|}} from bioapi in your PATH.
:May there still occures and error, which means mod_install: command not found.
:Then login as root - not su!
:Do this:
:{{cmdroot|sh install.sh}}
:again. It should work. SU to root does not work since then the /usr/local/bin directory is not used per default.

====Configuring permissions for non-root use====
If you want to use PAM-aware applications like xscreensaver that are NOT running with root permissions (as opposed to login, gdm or other authentication mechanisms), you may need to do all or at least some of the things in this section. More details on what is necessary on which distributions would be greately appreciated.
*Create two groups, one for access to BioAPI files and the other for access to the usb files. (This is done for full generality; i.e., you may have other USB devices which you want accessable to other users, without exposing your BioAPI configuration to them). Add your normal user (the one you wish to use PAM-aware applications with) to both of these groups.
On {{Debian}} this is done with
:{{cmdroot|addgroup --system bioapi}}
:{{cmdroot|addgroup --system usbfs}}
:{{cmdroot|adduser yournormaluser bioapi}}
:{{cmdroot|adduser yournormaluser usbfs}}
On {{SUSE}} this is done with
:{{cmdroot|groupadd --system bioapi}}
:{{cmdroot|groupadd --system usbfs}}
:{{cmdroot|groupmod -A yournormaluser bioapi}}
:{{cmdroot|groupmod -A yournormaluser usbfs}}
On {{Mandriva}} this is done with
:{{cmdroot|groupadd -r bioapi}}
:{{cmdroot|groupadd -r usbfs}}
:{{cmdroot|usermod -G bioapi,usbfs yournormaluser}}
On {{Fedora}} this is done with
:{{cmdroot|groupadd bioapi}}
:{{cmdroot|groupadd usbfs}}
:{{cmdroot|usermod -G bioapi,usbfs yournormaluser}}

:(where {{cmd|yournormaluser|}} is your normal user name). You will need to log out and log back in for this to take effect.
*Set permissions on the BioAPI config/registry directory:
:{{cmdroot|chown -R root:bioapi /usr/local/var/bioapi/}}
:{{cmdroot|chmod -R 770 /usr/local/var/bioapi/}}
:(change this path if you used an alternate BioAPI install directory above)
*Set permissions on the files in {{path|/proc/bus/usb}}:
:{{cmdroot|chown -R root:usbfs /proc/bus/usb}}
:{{cmdroot|chmod -R g+X /proc/bus/usb}}
:{{cmdroot|chown root:usbfs /proc/bus/usb/`lsusb <nowiki>|</nowiki> sed -ne "/0483:2016/s/Bus\ $.*$\ Device\ $.*$:\ .*/\1\/\2/p"`}}
:{{cmdroot|chmod 660 /proc/bus/usb/`lsusb <nowiki>|</nowiki> sed -ne "/0483:2016/s/Bus\ $.*$\ Device\ $.*$:\ .*/\1\/\2/p"`}}
:You may need to replace {{cmd|lsusb|}} with its full path, which is something like {{cmd|/sbin/lsusb|}} or {{cmd|/usr/bin/lsusb|}} depending on your distro. It might be necessary to put these lines into a script which is run at startup and resume from suspend/hibernate.
In {{Fedora}} {{cmd|lsusb|}} is not installed by default. To intall it just type:
:{{cmdroot|yum install usbutils}}

*As an alternative to the {{cmd|chown|}}/{{cmd|chmod|}} commands above, you can set mount options for usbfs with a line in {{path|/etc/fstab|}}; an example would be
none /proc/bus/usb usbfs defaults,devgid=108,devmode=0660,busgid=108,busmode=0770,listgid=108,listmode=0660 0 0
:where 108 is replaced with the numerical group ID of the usbfs group (you can determine this with something like {{cmd|cat /etc/group <nowiki>|</nowiki> grep usbfs <nowiki>|</nowiki> cut -d':' -f 3|}}). Make sure you only have one {{path|/proc/bus/usb}} entry in {{path|/etc/fstab}}. See the {{cmd|mount(8)|}} manpage for more information on these options. This is "cleaner" but seems to have a few weird issues -- see the talk page for details.
*You may also have files in {{path|/dev/bus/usb}}, which the driver will try before {{path|/proc/bus/usb}}. If this is another usbfs mount point ({{cmd|mount|}} shows a line containing {{cmdresult|/dev/bus/usb type usbfs}}), then simply follow the above instructions with {{path|/dev/bus/usb}} rather than {{path|/proc/bus/usb}}. Otherwise, you may be running a new kernel (i.e. 2.6.15) that makes usbfs-like files available through {{path|/dev/bus/usb}}.
*On systems running udev these files are dynamically created; you can configure their permissions by editing a udev config file. On Debian this is done by changing the <tt>usb_device</tt> line of {{path|/etc/udev/permissions.rules}} to read
SUBSYSTEM=="usb_device", MODE="0660", GROUP="usbfs"
*For the beta versions only, there is a logfile, which needs to exist with the proper permissions:
:{{cmdroot|touch /var/log/BSP.log && chown root:bioapi /var/log/BSP.log && chmod 660 /var/log/BSP.log}}

====Miscellaneous configuration====
* To increase the security level (minimize false accept rate), set this in {{path|/etc/tfmessbsp.cfg}}:
security-level="5"
{{WARN|Please see discussion section Security Level!}}

===Testing the driver and enrolling a fingerprint===
To test the driver and generate the file containing your fingerprint information, you need a sample program included with the driver. The compilation steps below were discovered by trial and error; if they don't work for you, try the binary {{cmd|Sample|}} utility that came with the beta versions of the driver (i.e., {{path|TFMESS_BSP_LIN_1.0beta2.zip}} as mentioned above).
Go to the folder where you extracted {{path|TFMESS_BSP_LIN_1.0.zip}} and do:
:{{cmdroot|cd NonGUI_Sample}}
:Edit {{path|main.c|}} and remove (or comment out) the line
#include "port/bioapi_port.h"
:then add the line
#include <stdlib.h>
:{{cmdroot|gcc -o Sample main.c -L/usr/local/lib -lbioapi100 -DUNIX -DLITTLE_ENDIAN}}
:{{cmdroot|./Sample}}
:Note that Sample may only run as root, unless you've already configured the usbfs file permissions.
:You can try to "e"nroll (to record a fingerprint for an account) and then "v"erify (to test a fingerprint against the one it expects for an account).
:You'll save a step later if you use your own login username as the username to enroll here.
:If running {{cmd |./Sample|}} produces the error message 'BioAPI_ModuleLoad failed, BioAPI Error Code: 6477 (0x194d)'
:then uncommenting the line
://BioAPI_SetGUICallbacks(gModuleHandle, NULL, NULL,TextGuiCallback, NULL);
:in {{path|main.c|}} can help.

==Login via pam_bioapi==

The following explains how to add fingerprint authentiation to programs that use the PAM (Pluggable Authentication Modules) framework, such as Gnome's GDM and KDE's KDM and screensaver.

===Getting required libs & tools===
====Installing pam_bioapi====
*Prerequisites
:On SuSE 10, I needed to install the pam-devel RPM
:In general, you will need pam itself (standard for most distros) as well as the pam development files (probably an optional package for your distro).
*Get and compile the pam_bioapi module.
{{HINT|A new version, pam_bioapi 0.3.0, with multi-finger and identification support can be found [http://www.nax.cz/pub/bioapi/pam_bioapi/pam-bioapi_0.3.0.tar.gz here].
There's work in progress. pam_bioapi and biometrics-manager can be downloaded [http://download.savannah.gnu.org/releases/pam-bioapi/ here].}}
:{{cmduser|wget http://www.qrivy.net/~michael/blua/pam_bioapi/pam_bioapi-latest.tar.bz2}}
:{{cmduser|tar xjf pam_bioapi-latest.tar.bz2}}
:{{cmduser|cd pam_bioapi-0.2.1}}
:{{cmduser|wget http://badcode.de/downloads/fingerprint.patch}}
:{{cmduser|patch -p0 < fingerprint.patch}}
:If you want to, review the patch. In general you should review all code you download and compile, if possible.
:{{cmduser|<nowiki>./configure --libdir=/lib && make </nowiki>}}
:and as root
:{{cmdroot| make install}}
{{NOTE|If you get a 'rpl_malloc' error in /var/log/auth.log when trying to use the fingerprint reader, redo these steps and remove the related term from Makefile after running ./configure. (FC3, Debian etch)}}
*If you get 'configure: error: cannot find required header: security/_pam_macros.h' and are on a Debian-like system, do "apt-get install libpam0g-dev" and try again. If you are using a Mandriva distribution, do "urpmi libpam0-devel" instead.
*If you get 'configure: error: cannot find required header: security/pam_modules.h' and are on a Debian-like system, do "apt-get install libpam0g-dev" and try again.
*If you get 'configure: error: cannot find required header: sqlite3.h' and are on a Debian-like system, do "apt-get install libsqlite3-dev" and try again.
*If you get 'make: msgfmt: command not found' and are on a Debian-like system, do "apt-get install gettext" and try again.
*If you get 'PAM [dlerror: /lib/security/pam_bioapi.so: undefined symbol: BioAPIMemoryFuncs]' error in your syslog, replace 'LIBS = ' line in {{path|libpam_bioapi/makefile}} with the following (of course, replace {{path|/opt/bioapi/}} with the path where you installed bioapi):
LIBS = -L/opt/bioapi/lib -lbioapi100 -lbioapi_mds300 -lmds_util
*Use the sample tool from the fingerprint reader to create {{path|<username>.bir}} (<tt><username></tt> '''must''' be the username you want to login with. gdm will probably break for any login name that has no .bir file).
*As root do:
:{{cmdroot|SERIAL<nowiki>=`BioAPITest | sed -ne "/Fingerprint/{n;n;s/^.*: $.\{9\}$$.\{4\}$$.\{4\}$$.\{4\}$$.*$/\1-\2-\3-\4-\5/gp}"` </nowiki>}}
:{{cmdroot|echo $SERIAL}} should print something like {{cmdresult|<nowiki>{5550454b-2054-464d-2f45-535320425350}</nowiki>}} now.
:If it does, do:
:{{cmdroot|mkdir -p /etc/bioapi/pam/$SERIAL}}
:{{cmdroot|cp <username>.bir /etc/bioapi/pam/$SERIAL}}
:If not, you might just try
:{{cmdroot|SERIAL<nowiki>={5550454b-2054-464d-2f45-535320425350}</nowiki>}}
:as this value is hardcoded into the UPEK docs.

===Configuring pam===
The following part is distribution specific. On {{Ubuntu}} or {{SUSE}} you can modify {{path|/etc/pam.d/common-auth}} (on {{Gentoo}} and {{Fedora}} it is {{path|/etc/pam.d/system-auth}}) to look like this:

#
# /etc/pam.d/common-auth - authentication settings common to all services
#
# This file is included from other service-specific PAM config files,
# and should contain a list of the authentication modules that define
# the central authentication scheme for use on the system
# (e.g., /etc/shadow, LDAP, Kerberos, etc.). The default is to use the
# traditional Unix authentication mechanisms.
#
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
password sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
auth required pam_unix.so nullok_secure

----
For '''Gentoo'''-Users - this allows you to attempt a password first. If you simply press enter, it then prompts for a fingerprints. Create a file named {{path|/etc/pam.d/bioapi}}. This also means that remote services, such as SSH keep working:

auth required pam_env.so
auth sufficient pam_unix.so likeauth nullok
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
auth required pam_deny.so

account required pam_unix.so

session required pam_limits.so
session required pam_unix.so

----

Now, simply replace "auth include system-auth" in all services that you wish to use fingerprint for with "auth include bioapi". For example, {{path|/etc/pam.d/kde}} by default contains

auth include system-auth
auth required pam_nologin.so

account include system-auth

password include system-auth

session include system-auth

Simply replace the first "system-auth" with bioapi and you can also get rid of KDE desktop lock with a fingerprint. If you do not wish to allow for "password fallback" then remove

auth sufficient pam_unix.so likeauth nullok

from {{path|/etc/pam.d/bioapi}}.

{{WARN|If su/sudo expects to receive the root password (SuSE 10), you need to have fingerprint settings for root (that is, copy in a root.bir as well as a your-username.bir). Otherwise, they get a segmentation fault. Which is a little unfortunate, given that you need to su or sudo to change your settings... }}
{{WARN|Not only SuSE 10 requires root.bir to be available for su to work. Just make sure you have root.bir when su is not working with your fingerprint reader but other applications are...}}
Note that sshd may pick up the fingerprint settings from {{path|/etc/pam.d/common-auth}}. I didn't want that, so I removed the "auth include common-auth" line from {{path|/etc/pam.d/sshd}} and replaced it with the lines that were originally in my {{path|/etc/pam.d/common-auth}}. That way most local services use the fingerprint reader, but sshd does not.

{{NOTE|su/sudo will call for your fingerprint even if you are remote via ssh. Pressing *CTLR-c* (or closing graphic window) will allow you the desired password option.}}

Another way to do this is to create a file ({{path|/etc/pam.d/bioapi|}} for example) which contains the {{cmd|pam_bioapi.so|}} lines, and explicitly {{cmd|@include|}} this '''before''' {{path|/etc/pam.d/common-auth|}} in the files for services which should use the fingerprint reader. In this case you should leave {{path|/etc/pam.d/common-auth|}} alone.

{{NOTE|This was discovered through trial and success, if it is plain wrong, wikorrect it, please.}}

In {{Fedora}} the original 'session' terms in {{path|/etc/pam.d/system-auth}} need to be kept.

{{HINT|The setup described above will/could affect remote ssh logins to also use biometric logins, which is a bit silly (who wants to remote ssh to the laptop, and then have to walk over to it and swipe your finger) To avoid that you can copy the default <tt>/etc/pam.d/system-auth</tt> to <tt>/etc/pam.d/sshd</tt> which will allow the sshd service to use the standard authentication procedure.}}

You can do some useful testing with [http://pamtester.sourceforge.net/ {{cmd|pamtester|}}], which calls the pam modules as if it were a program of your choice. Examples:
:{{cmdroot|pamtester xdm yourusername authenticate}}
:{{cmduser|pamtester xscreensaver yourusername authenticate}}
where {{cmd|yourusername|}} is your username. Note that {{cmd|pamtester|}} should run as root if and only if the program in question does.

===Application support===
The implementation of fingerprint scanning support in the relevant applications varies.

Here is the behaviour of the most common ones:
* In gdm enter your username and there should pop up an (ugly) image to swipe your finger and... magic - you can login without a password.
* kdm doesn't give any visual indication, other than that the cursor stops blinking. Just swipe your finger and hope it lets you log in.
* In xdm, enter your username and a blank password, then swipe (there is no popup as well). Identification support for xdm can be achieved with [http://www.nax.cz/pub/bioapi/2005/xdm/xdm_bio.patch this patch].
* The KDE screen saver in SUSE 10 requires you to enter an empty password (or select the correct user and then enter an empty password) in order to get the fingerprint prompt.
* For Fedora users, the redhat-config tools will crash if no root.bir presents. Also, there won't be any visual idication unless X server is properly configured for root to access. Just swipe your finger when the HDD stopped blinking or issue the following command in advance:
:{{cmduser|xhost +local:}}
* For RHEL4 users gdm, console (virtual terminal) logins and the xscreensaver all work

===kdm support===
To add graphical popup to kdm, you need following:
* Patch for pam_bioapi. This patch adds third parameter to {{path|pam_bioapi.so}} module, which is a name of file with additional environment variables that will be supplied to the UPEK driver.
:{{cmdroot|wget http://upir.cz/linux/patches/pam_bioapi-0.2.1-alter-environ.patch}}
:{{cmdroot|patch -p1 < pam_bioapi-0.2.1-alter-environ.patch}}
* Edit your {{path|Xsetup}} file (on SUSE 10 it's {{path|/etc/X11/xdm/Xsetup}}) and add these lines:
echo "XAUTHORITY=$XAUTHORITY" > /var/lib/xdm/kdm_env
echo "DISPLAY=$DISPLAY" >> /var/lib/xdm/kdm_env
* In {{path|/etc/pam.d/xdm}} file, add {{path|/var/lib/xdm/kdm_env}} as a third parameter for {{path|pam_bioapi.so}} module:
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/ /var/lib/xdm/kdm_env
* On Ubuntu simply do:
echo "DISPLAY=$DISPLAY" >> /var/lib/kdm/kdm_env
* If you have created /etc/pam.d/bioapi then modify:
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/ /var/lib/kdm/kdm_env

Please note, that this won't work if you have more than one Xserver.

==Make xscreensaver use the scanner==
If you are using Gentoo, you can get a portage overlay with the necessary patches here: http://www.zzamboni.org/brt/files/xscreensaver-fingerprint-overlay.tar.gz
*Get the needed xscreensaver sources:
:{{cmduser|wget http://www.jwz.org/xscreensaver/xscreensaver-4.23.tar.gz}}
:{{cmduser|tar xzf xscreensaver-4.23.tar.gz}}
:{{cmduser|cd xscreensaver-4.23}}
:{{cmduser|wget http://www.nax.cz/pub/bioapi/2005/xscreensaver/xscreensaver-4.22_alternativeAuth.diff mirror: http://zepan.org/files/xscreensaver-4.22_alternativeAuth.diff For xscreensaver 5.00, you can get a patch here: http://www.zzamboni.org/brt/files/xscreensaver-5.00-alternativeauth.patch}}
*After reviewing the patch (it's small and straightforward), do
:{{cmduser|patch -p1 < xscreensaver-4.22_alternativeAuth.diff}} The patch prevents xscreensaver from opening an authentification window and dispatches the authentification request to another program, in our case <tt>pam</tt> and <tt>pam_bioapi</tt>. It should apply with some offset, don't mind that. If it says something about rejected though, then there's a problem.
*Compile with
:{{cmduser|./configure --with-pam && make}} 
*If you receive an error like "Couldn't find X11 headers/libs" and are running a Debian-like system, try "apt-get install xlibs-dev"
*If you receive an error like "undefined reference to `XmuPrintDefaultErrorMessage'" then install the libxmu-dev package and run the previous line again and then install as root with
:{{cmduser|su -c make install}} .
*Make sure that the newly compiled xscreensaver is used:
:{{cmduser|which xscreensaver}} should return
:{{cmdresult|/usr/local/bin/xscreensaver}} .
*In case it doesn't, try adjusting your PATH.

==Common problems==
===Bioapi error #3===
This is sometimes caused by improper permissions. The full error message is "BioAPI Error Code: 3 (0x3)".

However, at least on Gentoo, recent upgrades to glibc and gcc 4.1.1 caused Bioapi to break down due to some sort of incompatibility with bioapi registry. Reinstalling does '''not''' repair the issue automatically. However, you can still fix the issue manually, by removing /var/bioapi. You need to reinstall tfm-fingerprint driver after reinstalling bioapi so that the driver is properly re-registered. As root, type

:{{cmdroot|emerge -C bioapi}}
:{{cmdroot|rm -rf /var/bioapi}}
:{{cmdroot|emerge -av1 bioapi tfm-fingerprint}}

Install Ubuntu Gutsy Gibbon on a T61p

2008-01-05T06:47:44Z

Chazchaz101: /* Fingerprint Reader */

Install Ubuntu Gutsy Gibbon on a T61p

2008-01-05T06:45:56Z

Chazchaz101: Added Fingerprint Reader Section

Install Ubuntu Gutsy Gibbon on a T61p

2007-12-28T07:25:18Z

Chazchaz101: Added Bluetooth Section

Install Ubuntu Gutsy Gibbon on a T61p

2007-12-28T07:17:32Z

Chazchaz101: /* Audio */

Install Ubuntu Gutsy Gibbon on a T61p

2007-12-17T08:50:46Z

Chazchaz101: /* Network/Internet */ Clarified what this does and removed unneeded heading

Install Ubuntu Gutsy Gibbon on a T61p

2007-12-17T08:43:00Z

Chazchaz101: /* Installation Notes */

Install Ubuntu Gutsy Gibbon on a T61p

2007-12-17T08:37:43Z

Chazchaz101: /* Display/Video */

Install Ubuntu Gutsy Gibbon on a T61p

2007-12-17T08:35:00Z

Chazchaz101: /* Installation Notes */

Install Ubuntu Gutsy Gibbon on a T61p

2007-12-17T08:31:12Z

Chazchaz101: /* Installation Notes */

Install Ubuntu Gutsy Gibbon on a T61p

2007-12-17T08:29:55Z

Chazchaz101: Specific instructions for switching xorg.conf to vesa

Install Ubuntu Gutsy Gibbon on a T61p

2007-12-17T08:08:41Z

Chazchaz101: /* Installation Notes */