ThinkWiki - User contributions [en]

Install Ubuntu Intrepid Ibex on a T61p

2009-01-27T16:17:09Z

Dickeywang: /* Display/Video */

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

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

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

System --> Administration --> Hardware Drivers.

You will have a choice between the 173 and 177 version of the driver (Note: if you want to have better 2D performance without breaking suspend/resume, you will have to manually install the 180.25 driver manually as it is not included in the official Intrepid repo).
*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 ...)
*Early version of the 180 drivers break the suspension/resume, however 180.25(beta) driver has fixed this issue as well as improved 2D performance in X. Unfortunately, as of Jan. 27, 2009, the 180 driver has not been included in Intrepid's official repo, so you will have to install it manually.

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

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

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

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

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

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

#!/bin/sh

while true; do

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

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

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

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

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

chmod a+x powermizer-loop powermizer-off

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

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

=== EDID misdetection ===

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

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

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

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

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

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

This will be solved in intrepid-updates eventually.

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

== Middle-button Scrolling ==
Xorg.conf is not used to configure mice and keyboards anymore, but evdev is. This makes the configuration of middle-click scrolling a little bit different than previous versions of Ubuntu.

[http://mvogt.wordpress.com/2008/08/15/xorg-evdev-and-emulatewheel/ Michael Vogt described] how to get middle-click scrolling to work again in Intrepid.

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

Paste and save the following code, which will give vertical wheel emulation only:
<match key="info.product" string="TPPS/2 IBM TrackPoint">
<merge key="input.x11_options.EmulateWheel" type="string">true</merge>
<merge key="input.x11_options.EmulateWheelButton" type="string">2</merge>
<merge key="input.x11_options.ZAxsisMapping" type="string">4 5</merge>
<merge key="input.x11_options.Emulate3Buttons" type="string">true</merge>
</match>
There is [http://psung.blogspot.com/2008/09/scrolling-with-thinkpads-trackpoint-in.html another method] to get horizontal scrolling as well, but this is not confirmed to work.

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

==Fingerprint Reader==

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

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

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

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

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

Enter in the popup window:

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

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

1) Install the following packages:

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

2) For your user:

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

A completed fingerprint setup should look something like this:

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

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

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

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

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

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

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

3) Enable use of reader for authentication:

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

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

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

4) Check uinput kernel module:

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

Start uinput:

{{cmduser|sudo modprobe uinput}}

Start on boot:

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

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

5) Enabling thinkfinger for gnome-screensaver

*create this file:
{{cmduser|sudo gedit /etc/udev/rules.d/60-thinkfinger.rules}}
with this contents:
#
# udev rules file for the thinkfinger fingerprint scanner
# gives access to the fingerprint reader to those in the "fingerprint" group
#
# Taken from:
# http://www.thinkwiki.org/wiki/Install_Ubuntu_Intrepid_Ibex_on_a_T61p#Fingerprint_Reader
# which was taken and modified from:
# http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
# http://article.gmane.org/gmane.linux.drivers.thinkfinger/329

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

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

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

Reboot your laptop and you should be ready to swipe!

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

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

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

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

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

== Black Screen on Resume ==
On the 6459CTO with default 8.10 install suspend did not work. Enabling the proposed updates to be installed to your system might fix this issue. To enable the proposed updates go to the 'Software Sources' - tab 'Updates' in System -> Administration. Tick the 'Proposed updates (intrepid-updates)' checkbox, close 'Software Sources' to reload the package lists. Then, check for updates with the software updater (there should be some), update and reboot afterwards.

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

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

SUSPEND_MODULES="ath_pci"

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

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

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

http://www.lesswatts.org

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

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

and run it with:

{{cmduser|sudo powertop}}

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

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

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

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

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

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

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

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

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

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

Talk:Install Ubuntu Intrepid Ibex on a T61p

2009-01-27T16:15:32Z

Dickeywang: /* Log out & NVidia */

== Log out & NVidia ==
This is a problem between the 177.* drivers and broken Lenovo DFP EDID.
You can make it work by increasing timeout in GDM:
e.g. set GdmXServerTimeout=45 in /etc/gdm/gdm.conf

This workaround works. I've read it on the LP bug report as well. I don't know if it has to do with the broken EDID. I've seen much more laptops with broked EDIDs, but this hang does not occur with Intrepid on those machines.--[[User:Gertvdijk|Gertvdijk]] 18:42, 6 November 2008 (CET)

Just want to point out that the 173.* driver broken EDID too. --[[User:Dickeywang|Dickeywang]] 16:15, 27 January 2009 (UTC)

== WiFi & HW RFkill ==
I think that the interface is just not brought up after the kill switch is disabled. Try:
ip l s wlan0 up

This works, just like reloading the module. Why is it so hard to fix in the the release?--[[User:Gertvdijk|Gertvdijk]] 18:42, 6 November 2008 (CET)

== UUOC award nomination ==

Looking at this line in the <code>powermizer-loop</code> script
powerstate=`cat /proc/acpi/ac_adapter/AC/state | awk '{print $2}'`
Can this be changed to
powerstate=`awk '{print $2}' /proc/acpi/ac_adapter/AC/state`
For [http://en.wikipedia.org/wiki/Cat_(Unix)#Useless_use_of_cat UUOC], see Wikipedia ;) [[User:Jomanchu|Jomanchu]] 08:51, 18 January 2009 (UTC)

== Possible Mistake in Tp_smapi section ==

Should
echo "90" | sudo tee -a /sys/devices/platform/smapi/BAT0/start_charge_thresh
be changed to
echo "90" | sudo tee -a /sys/devices/platform/smapi/BAT0/stop_charge_thresh
start-> stop? This section is talking about an upper limit, I thought.

You're right, Jomanchu. Fixed.--[[User:Gertvdijk|Gertvdijk]] 17:10, 26 January 2009 (UTC)

Talk:Install Ubuntu Intrepid Ibex on a T61p

2009-01-27T16:15:17Z

Dickeywang: /* Log out & NVidia */

== Log out & NVidia ==
This is a problem between the 177.* drivers and broken Lenovo DFP EDID.
You can make it work by increasing timeout in GDM:
e.g. set GdmXServerTimeout=45 in /etc/gdm/gdm.conf

This workaround works. I've read it on the LP bug report as well. I don't know if it has to do with the broken EDID. I've seen much more laptops with broked EDIDs, but this hang does not occur with Intrepid on those machines.--[[User:Gertvdijk|Gertvdijk]] 18:42, 6 November 2008 (CET)

Just want to point out that the 173.* driver broken EDID too.--DickeyWang

== WiFi & HW RFkill ==
I think that the interface is just not brought up after the kill switch is disabled. Try:
ip l s wlan0 up

This works, just like reloading the module. Why is it so hard to fix in the the release?--[[User:Gertvdijk|Gertvdijk]] 18:42, 6 November 2008 (CET)

== UUOC award nomination ==

Looking at this line in the <code>powermizer-loop</code> script
powerstate=`cat /proc/acpi/ac_adapter/AC/state | awk '{print $2}'`
Can this be changed to
powerstate=`awk '{print $2}' /proc/acpi/ac_adapter/AC/state`
For [http://en.wikipedia.org/wiki/Cat_(Unix)#Useless_use_of_cat UUOC], see Wikipedia ;) [[User:Jomanchu|Jomanchu]] 08:51, 18 January 2009 (UTC)

== Possible Mistake in Tp_smapi section ==

Should
echo "90" | sudo tee -a /sys/devices/platform/smapi/BAT0/start_charge_thresh
be changed to
echo "90" | sudo tee -a /sys/devices/platform/smapi/BAT0/stop_charge_thresh
start-> stop? This section is talking about an upper limit, I thought.

You're right, Jomanchu. Fixed.--[[User:Gertvdijk|Gertvdijk]] 17:10, 26 January 2009 (UTC)

Install Ubuntu Intrepid Ibex on a T61p

2009-01-27T16:13:15Z

Dickeywang: /* Display/Video */

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

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

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

System --> Administration --> Hardware Drivers.

You will have a choice between the 173 and 177 version of the driver.
*pro:
**Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not.
*con:
**version 177 causes a log out bug that is addressed below.
**version 177 might show some issues like terminal output not updating in some very weird cases (which I did not see in v173, this seems to have something to do with powermizer as well ...)
*Early version of the 180 drivers break the suspension/resume, however 180.25(beta) driver has fixed this issue as well as improved 2D performance in X. Unfortunately, as of Jan. 27, 2009, the 180 driver has not been included in Intrepid's official repo, so you will have to install it manually.

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

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

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

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

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

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

#!/bin/sh

while true; do

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

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

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

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

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

chmod a+x powermizer-loop powermizer-off

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

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

=== EDID misdetection ===

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

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

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

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

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

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

This will be solved in intrepid-updates eventually.

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

== Middle-button Scrolling ==
Xorg.conf is not used to configure mice and keyboards anymore, but evdev is. This makes the configuration of middle-click scrolling a little bit different than previous versions of Ubuntu.

[http://mvogt.wordpress.com/2008/08/15/xorg-evdev-and-emulatewheel/ Michael Vogt described] how to get middle-click scrolling to work again in Intrepid.

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

Paste and save the following code, which will give vertical wheel emulation only:
<match key="info.product" string="TPPS/2 IBM TrackPoint">
<merge key="input.x11_options.EmulateWheel" type="string">true</merge>
<merge key="input.x11_options.EmulateWheelButton" type="string">2</merge>
<merge key="input.x11_options.ZAxsisMapping" type="string">4 5</merge>
<merge key="input.x11_options.Emulate3Buttons" type="string">true</merge>
</match>
There is [http://psung.blogspot.com/2008/09/scrolling-with-thinkpads-trackpoint-in.html another method] to get horizontal scrolling as well, but this is not confirmed to work.

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

==Fingerprint Reader==

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

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

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

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

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

Enter in the popup window:

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

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

1) Install the following packages:

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

2) For your user:

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

A completed fingerprint setup should look something like this:

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

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

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

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

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

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

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

3) Enable use of reader for authentication:

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

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

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

4) Check uinput kernel module:

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

Start uinput:

{{cmduser|sudo modprobe uinput}}

Start on boot:

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

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

5) Enabling thinkfinger for gnome-screensaver

*create this file:
{{cmduser|sudo gedit /etc/udev/rules.d/60-thinkfinger.rules}}
with this contents:
#
# udev rules file for the thinkfinger fingerprint scanner
# gives access to the fingerprint reader to those in the "fingerprint" group
#
# Taken from:
# http://www.thinkwiki.org/wiki/Install_Ubuntu_Intrepid_Ibex_on_a_T61p#Fingerprint_Reader
# which was taken and modified from:
# http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
# http://article.gmane.org/gmane.linux.drivers.thinkfinger/329

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

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

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

Reboot your laptop and you should be ready to swipe!

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

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

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

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

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

== Black Screen on Resume ==
On the 6459CTO with default 8.10 install suspend did not work. Enabling the proposed updates to be installed to your system might fix this issue. To enable the proposed updates go to the 'Software Sources' - tab 'Updates' in System -> Administration. Tick the 'Proposed updates (intrepid-updates)' checkbox, close 'Software Sources' to reload the package lists. Then, check for updates with the software updater (there should be some), update and reboot afterwards.

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

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

SUSPEND_MODULES="ath_pci"

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

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

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

http://www.lesswatts.org

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

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

and run it with:

{{cmduser|sudo powertop}}

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

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

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

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

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

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

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

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

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

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

Install Ubuntu Intrepid Ibex on a T61p

2009-01-27T16:11:53Z

Dickeywang: /* Display/Video */

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

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

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

System --> Administration --> Hardware Drivers.

You will have a choice between the 173 and 177 version of the driver.
*pro:
**Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not.
*con:
**version 177 causes a log out bug that is addressed below.
**version 177 might show some issues like terminal output not updating in some very weird cases (which I did not see in v173, this seems to have something to do with powermizer as well ...)
*Early version of the 180 drivers break the suspension/resume, however this bug has been fixed in the 180.25 release. Unfortunately, as of Jan. 27, 2009, the 180 driver has not been included in Intrepid's official repo, so you will have to install it manually.

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

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

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

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

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

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

#!/bin/sh

while true; do

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

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

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

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

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

chmod a+x powermizer-loop powermizer-off

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

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

=== EDID misdetection ===

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

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

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

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

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

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

This will be solved in intrepid-updates eventually.

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

== Middle-button Scrolling ==
Xorg.conf is not used to configure mice and keyboards anymore, but evdev is. This makes the configuration of middle-click scrolling a little bit different than previous versions of Ubuntu.

[http://mvogt.wordpress.com/2008/08/15/xorg-evdev-and-emulatewheel/ Michael Vogt described] how to get middle-click scrolling to work again in Intrepid.

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

Paste and save the following code, which will give vertical wheel emulation only:
<match key="info.product" string="TPPS/2 IBM TrackPoint">
<merge key="input.x11_options.EmulateWheel" type="string">true</merge>
<merge key="input.x11_options.EmulateWheelButton" type="string">2</merge>
<merge key="input.x11_options.ZAxsisMapping" type="string">4 5</merge>
<merge key="input.x11_options.Emulate3Buttons" type="string">true</merge>
</match>
There is [http://psung.blogspot.com/2008/09/scrolling-with-thinkpads-trackpoint-in.html another method] to get horizontal scrolling as well, but this is not confirmed to work.

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

==Fingerprint Reader==

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

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

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

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

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

Enter in the popup window:

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

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

1) Install the following packages:

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

2) For your user:

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

A completed fingerprint setup should look something like this:

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

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

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

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

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

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

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

3) Enable use of reader for authentication:

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

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

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

4) Check uinput kernel module:

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

Start uinput:

{{cmduser|sudo modprobe uinput}}

Start on boot:

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

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

5) Enabling thinkfinger for gnome-screensaver

*create this file:
{{cmduser|sudo gedit /etc/udev/rules.d/60-thinkfinger.rules}}
with this contents:
#
# udev rules file for the thinkfinger fingerprint scanner
# gives access to the fingerprint reader to those in the "fingerprint" group
#
# Taken from:
# http://www.thinkwiki.org/wiki/Install_Ubuntu_Intrepid_Ibex_on_a_T61p#Fingerprint_Reader
# which was taken and modified from:
# http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
# http://article.gmane.org/gmane.linux.drivers.thinkfinger/329

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

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

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

Reboot your laptop and you should be ready to swipe!

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

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

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

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

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

== Black Screen on Resume ==
On the 6459CTO with default 8.10 install suspend did not work. Enabling the proposed updates to be installed to your system might fix this issue. To enable the proposed updates go to the 'Software Sources' - tab 'Updates' in System -> Administration. Tick the 'Proposed updates (intrepid-updates)' checkbox, close 'Software Sources' to reload the package lists. Then, check for updates with the software updater (there should be some), update and reboot afterwards.

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

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

SUSPEND_MODULES="ath_pci"

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

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

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

http://www.lesswatts.org

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

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

and run it with:

{{cmduser|sudo powertop}}

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

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

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

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

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

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

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

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

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

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

Install Ubuntu Intrepid Ibex on a T61p

2009-01-27T16:11:39Z

Dickeywang: /* Display/Video */

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

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

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

System --> Administration --> Hardware Drivers.

You will have a choice between the 173 and 177 version of the driver.
*pro:
**Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not.
*con:
**version 177 causes a log out bug that is addressed below.
**version 177 might show some issues like terminal output not updating in some very weird cases (which I did not see in v173, this seems to have something to do with powermizer as well ...)
**Early version of the 180 drivers break the suspension/resume, however this bug has been fixed in the 180.25 release. Unfortunately, as of Jan. 27, 2009, the 180 driver has not been included in Intrepid's official repo, so you will have to install it manually.

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

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

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

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

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

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

#!/bin/sh

while true; do

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

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

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

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

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

chmod a+x powermizer-loop powermizer-off

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

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

=== EDID misdetection ===

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

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

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

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

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

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

This will be solved in intrepid-updates eventually.

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

== Middle-button Scrolling ==
Xorg.conf is not used to configure mice and keyboards anymore, but evdev is. This makes the configuration of middle-click scrolling a little bit different than previous versions of Ubuntu.

[http://mvogt.wordpress.com/2008/08/15/xorg-evdev-and-emulatewheel/ Michael Vogt described] how to get middle-click scrolling to work again in Intrepid.

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

Paste and save the following code, which will give vertical wheel emulation only:
<match key="info.product" string="TPPS/2 IBM TrackPoint">
<merge key="input.x11_options.EmulateWheel" type="string">true</merge>
<merge key="input.x11_options.EmulateWheelButton" type="string">2</merge>
<merge key="input.x11_options.ZAxsisMapping" type="string">4 5</merge>
<merge key="input.x11_options.Emulate3Buttons" type="string">true</merge>
</match>
There is [http://psung.blogspot.com/2008/09/scrolling-with-thinkpads-trackpoint-in.html another method] to get horizontal scrolling as well, but this is not confirmed to work.

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

==Fingerprint Reader==

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

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

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

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

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

Enter in the popup window:

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

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

1) Install the following packages:

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

2) For your user:

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

A completed fingerprint setup should look something like this:

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

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

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

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

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

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

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

3) Enable use of reader for authentication:

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

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

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

4) Check uinput kernel module:

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

Start uinput:

{{cmduser|sudo modprobe uinput}}

Start on boot:

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

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

5) Enabling thinkfinger for gnome-screensaver

*create this file:
{{cmduser|sudo gedit /etc/udev/rules.d/60-thinkfinger.rules}}
with this contents:
#
# udev rules file for the thinkfinger fingerprint scanner
# gives access to the fingerprint reader to those in the "fingerprint" group
#
# Taken from:
# http://www.thinkwiki.org/wiki/Install_Ubuntu_Intrepid_Ibex_on_a_T61p#Fingerprint_Reader
# which was taken and modified from:
# http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
# http://article.gmane.org/gmane.linux.drivers.thinkfinger/329

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

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

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

Reboot your laptop and you should be ready to swipe!

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

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

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

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

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

== Black Screen on Resume ==
On the 6459CTO with default 8.10 install suspend did not work. Enabling the proposed updates to be installed to your system might fix this issue. To enable the proposed updates go to the 'Software Sources' - tab 'Updates' in System -> Administration. Tick the 'Proposed updates (intrepid-updates)' checkbox, close 'Software Sources' to reload the package lists. Then, check for updates with the software updater (there should be some), update and reboot afterwards.

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

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

SUSPEND_MODULES="ath_pci"

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

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

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

http://www.lesswatts.org

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

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

and run it with:

{{cmduser|sudo powertop}}

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

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

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

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

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

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

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

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

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

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

Install Ubuntu Intrepid Ibex on a T61p

2009-01-27T16:11:21Z

Dickeywang:

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

**Early version of the 180 drivers break the suspension/resume, however this bug has been fixed in the 180.25 release. Unfortunately, as of Jan. 27, 2009, the 180 driver has not been included in Intrepid's official repo, so you will have to install it manually.

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

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

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

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

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

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

#!/bin/sh

while true; do

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

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

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

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

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

chmod a+x powermizer-loop powermizer-off

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

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

=== EDID misdetection ===

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

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

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

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

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

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

This will be solved in intrepid-updates eventually.

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

== Middle-button Scrolling ==
Xorg.conf is not used to configure mice and keyboards anymore, but evdev is. This makes the configuration of middle-click scrolling a little bit different than previous versions of Ubuntu.

[http://mvogt.wordpress.com/2008/08/15/xorg-evdev-and-emulatewheel/ Michael Vogt described] how to get middle-click scrolling to work again in Intrepid.

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

Paste and save the following code, which will give vertical wheel emulation only:
<match key="info.product" string="TPPS/2 IBM TrackPoint">
<merge key="input.x11_options.EmulateWheel" type="string">true</merge>
<merge key="input.x11_options.EmulateWheelButton" type="string">2</merge>
<merge key="input.x11_options.ZAxsisMapping" type="string">4 5</merge>
<merge key="input.x11_options.Emulate3Buttons" type="string">true</merge>
</match>
There is [http://psung.blogspot.com/2008/09/scrolling-with-thinkpads-trackpoint-in.html another method] to get horizontal scrolling as well, but this is not confirmed to work.

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

==Fingerprint Reader==

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

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

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

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

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

Enter in the popup window:

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

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

1) Install the following packages:

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

2) For your user:

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

A completed fingerprint setup should look something like this:

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

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

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

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

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

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

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

3) Enable use of reader for authentication:

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

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

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

4) Check uinput kernel module:

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

Start uinput:

{{cmduser|sudo modprobe uinput}}

Start on boot:

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

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

5) Enabling thinkfinger for gnome-screensaver

*create this file:
{{cmduser|sudo gedit /etc/udev/rules.d/60-thinkfinger.rules}}
with this contents:
#
# udev rules file for the thinkfinger fingerprint scanner
# gives access to the fingerprint reader to those in the "fingerprint" group
#
# Taken from:
# http://www.thinkwiki.org/wiki/Install_Ubuntu_Intrepid_Ibex_on_a_T61p#Fingerprint_Reader
# which was taken and modified from:
# http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
# http://article.gmane.org/gmane.linux.drivers.thinkfinger/329

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

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

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

Reboot your laptop and you should be ready to swipe!

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

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

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

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

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

== Black Screen on Resume ==
On the 6459CTO with default 8.10 install suspend did not work. Enabling the proposed updates to be installed to your system might fix this issue. To enable the proposed updates go to the 'Software Sources' - tab 'Updates' in System -> Administration. Tick the 'Proposed updates (intrepid-updates)' checkbox, close 'Software Sources' to reload the package lists. Then, check for updates with the software updater (there should be some), update and reboot afterwards.

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

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

SUSPEND_MODULES="ath_pci"

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

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

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

http://www.lesswatts.org

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

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

and run it with:

{{cmduser|sudo powertop}}

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

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

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

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

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

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

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

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

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

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

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61p

2008-11-13T17:59:28Z

Dickeywang: /* EDID misdetection */

==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.
*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. 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
**Only tested with a single 6-cell battery

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

==What doesn't work at the moment?==
*Suspend-to-Disk (Hibernate)
*Wireless LAN issues (both fixed in Intrepid):
**LED not working.
**Broken PEAP/TTLS WPA enterprise authentication.

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

Optionally, 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 aptitude install nvidia-settings}}

which will add the NVidia X Server Settings panel to the Administration menu.
However, this version of the driver will not provide you proper suspend functionality. The easiest way to install more recent drivers is by using Envy, described below.
==== Installation of more recent Envy driver ====
Alternately, more recent versions of the NVidia driver can be installed using EnvyNG.

{{cmduser| sudo aptitude install envyng-gtk}}

After installation, simply start EnvyNG (you can find it in the System Tools menu) and let it install the NVidia driver. Using more recent drivers than the one offered in the Hardware Drivers panel will provide proper suspend functionality.

Unfortunately, there are still some annoying bugs in the NVidia driver. The most annoying one is that after resuming from suspend, you might get a blank white screen, instead of a simple box asking for your password. To get past it, simply type in your password (blindly) 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. You might still see the white screen for a short amount of time. For suspend functionality you might need to follow the steps in the Suspend section below.

As far as I know there is no NVidia X Server Settings program available for the Envy driver, since it conflicts with the Envy driver when you try to install it from the repositories.

==== Choppy Compiz animations ====

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

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. It seems that the interval of the PowerMizer is way too long and is not speeding up when using in bursts. 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 ====
One final bug is that EDID (Extended Display Identification Data) might be misdetected for your display, 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.) If you encouter this problem, add 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. The 40-70 values are just an example. You should put the values of your display there.

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.

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]

==== 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, espected behavior. You can let the GNOME Power Manager still lower the brightness, but you will be able to higher it when needed.

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

Basically, it comes down to changing the power_management.quirk.s3_bios key value to false. 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, when resuming quickly, I have to switch to the X terminal manually by pressing alt+F7 and the sleep LED will blink for a while, 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 longer time of sleep (more than one minute approx.).

{{NOTE|This has been fixed in the latest builds of the hal-info package for Ubuntu Hardy. [https://bugs.launchpad.net/ubuntu/+source/hal/+bug/253223 Launchpad bug #253223]}}

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

== Kubuntu KDE 4.1 on the t61p ==

=== What works? ===

=== What does not work? ===
*Screen brightness control
*Volume control buttons

=== Screen brightness control ===
There is a known bug in Kubuntu/KDE 4.1 which causes acpi_fakekey information to be lost. This in turn breaks the /etc/acpi/video_brightnessdown.sh and video_brightnessup.sh scripts. See https://bugs.launchpad.net/ubuntu/+source/kdeutils-kde4/+bug/223643

Here's a workaround: change the above scripts as follows:
<pre>
root@t61p:/etc/acpi# cat video_brightnessdown.sh
#!/bin/bash
brightness=$(cat /sys/class/backlight/acpi_video1/actual_brightness)
new_brightness=$[brightness-1]
echo $new_brightness > /sys/class/backlight/acpi_video1/brightness

root@t61p:/etc/acpi# cat video_brightnessup.sh
#!/bin/bash
brightness=$(cat /sys/class/backlight/acpi_video1/actual_brightness)
new_brightness=$[brightness+1]
echo $new_brightness > /sys/class/backlight/acpi_video1/brightness
</pre>
[[Category:T61p]]
[[Category:Ubuntu]]
[[Category:Ubuntu 8.04]]

Install Ubuntu Intrepid Ibex on a T61p

2008-11-13T17:57:16Z

Dickeywang: /* EDID misdetection */

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

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

The first time you boot Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at System --> Administration --> Hardware Drivers. You will have a choice between the 173 and 177 version of the driver. Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not. However, 177 causes a log out bug that is addressed below.

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

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

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

==Microphone/Sound In==
Might need to be turned on in the mixer
==Hard Drive Active Protection System (APS ~ HDAPS)==
Please add to this section

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

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

This will be solved in intrepid-updates eventually.

For now there are a few ways to bring the interface back up (choose one):
* {{cmdroot|ip l s wlan0 up}}
* {{cmdroot|modprobe -r iwl3945 && modprobe iwl3945}}
* reboot
* suspend and resume

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

==Fingerprint Reader==

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

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

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

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

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

Enter in the popup window:

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

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

1) Install the following packages:

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

2) For your user:

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

A completed fingerprint setup should look something like this:

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

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

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

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

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

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

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

3) Enable use of reader for authentication:

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

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

4) Check uinput kernel module:

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

Start uinput:

{{cmduser|sudo modprobe uinput}}

Start on boot:

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

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

5) Enabling thinkfinger for gnome-screensaver

*create this file:
{{cmduser|sudo gedit /etc/udev/rules.d/60-thinkfinger.rules}}
with this contents:
#
# udev rules file for the thinkfinger fingerprint scanner
# gives access to the fingerprint reader to those in the "fingerprint" group
#
# Taken from:
# http://www.thinkwiki.org/wiki/Install_Ubuntu_Intrepid_Ibex_on_a_T61p#Fingerprint_Reader
# which was taken and modified from:
# http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
# http://article.gmane.org/gmane.linux.drivers.thinkfinger/329

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

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

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

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

Reboot your laptop and you should be ready to swipe!

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

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

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

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

#!/bin/sh

while true; do

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

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

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

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

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

chmod a+x powermizer-loop powermizer-off

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

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

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

== EDID misdetection ==

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

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

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

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

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

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

SUSPEND_MODULES="ath_pci"

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

http://www.lesswatts.org

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

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

and run it with:

{{cmduser|sudo powertop}}

For more information see http://www.lesswatts.org/projects/powertop/

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

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

Install Ubuntu Intrepid Ibex on a T61p

2008-11-13T17:56:47Z

Dickeywang: /* EDID misdetection */

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

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

The first time you boot Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at System --> Administration --> Hardware Drivers. You will have a choice between the 173 and 177 version of the driver. Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not. However, 177 causes a log out bug that is addressed below.

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

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

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

==Microphone/Sound In==
Might need to be turned on in the mixer
==Hard Drive Active Protection System (APS ~ HDAPS)==
Please add to this section

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

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

This will be solved in intrepid-updates eventually.

For now there are a few ways to bring the interface back up (choose one):
* {{cmdroot|ip l s wlan0 up}}
* {{cmdroot|modprobe -r iwl3945 && modprobe iwl3945}}
* reboot
* suspend and resume

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

==Fingerprint Reader==

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

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

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

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

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

Enter in the popup window:

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

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

1) Install the following packages:

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

2) For your user:

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

A completed fingerprint setup should look something like this:

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

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

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

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

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

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

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

3) Enable use of reader for authentication:

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

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

4) Check uinput kernel module:

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

Start uinput:

{{cmduser|sudo modprobe uinput}}

Start on boot:

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

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

5) Enabling thinkfinger for gnome-screensaver

*create this file:
{{cmduser|sudo gedit /etc/udev/rules.d/60-thinkfinger.rules}}
with this contents:
#
# udev rules file for the thinkfinger fingerprint scanner
# gives access to the fingerprint reader to those in the "fingerprint" group
#
# Taken from:
# http://www.thinkwiki.org/wiki/Install_Ubuntu_Intrepid_Ibex_on_a_T61p#Fingerprint_Reader
# which was taken and modified from:
# http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
# http://article.gmane.org/gmane.linux.drivers.thinkfinger/329

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

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

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

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

Reboot your laptop and you should be ready to swipe!

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

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

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

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

#!/bin/sh

while true; do

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

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

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

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

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

chmod a+x powermizer-loop powermizer-off

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

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

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

== EDID misdetection ==

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

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

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

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

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

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

SUSPEND_MODULES="ath_pci"

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

http://www.lesswatts.org

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

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

and run it with:

{{cmduser|sudo powertop}}

For more information see http://www.lesswatts.org/projects/powertop/

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

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

Install Ubuntu Intrepid Ibex on a T61p

2008-11-13T17:55:51Z

Dickeywang: /* EDID misdetection */

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

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

The first time you boot Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at System --> Administration --> Hardware Drivers. You will have a choice between the 173 and 177 version of the driver. Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not. However, 177 causes a log out bug that is addressed below.

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

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

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

==Microphone/Sound In==
Might need to be turned on in the mixer
==Hard Drive Active Protection System (APS ~ HDAPS)==
Please add to this section

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

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

This will be solved in intrepid-updates eventually.

For now there are a few ways to bring the interface back up (choose one):
* {{cmdroot|ip l s wlan0 up}}
* {{cmdroot|modprobe -r iwl3945 && modprobe iwl3945}}
* reboot
* suspend and resume

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

==Fingerprint Reader==

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

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

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

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

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

Enter in the popup window:

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

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

1) Install the following packages:

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

2) For your user:

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

A completed fingerprint setup should look something like this:

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

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

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

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

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

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

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

3) Enable use of reader for authentication:

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

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

4) Check uinput kernel module:

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

Start uinput:

{{cmduser|sudo modprobe uinput}}

Start on boot:

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

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

5) Enabling thinkfinger for gnome-screensaver

*create this file:
{{cmduser|sudo gedit /etc/udev/rules.d/60-thinkfinger.rules}}
with this contents:
#
# udev rules file for the thinkfinger fingerprint scanner
# gives access to the fingerprint reader to those in the "fingerprint" group
#
# Taken from:
# http://www.thinkwiki.org/wiki/Install_Ubuntu_Intrepid_Ibex_on_a_T61p#Fingerprint_Reader
# which was taken and modified from:
# http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
# http://article.gmane.org/gmane.linux.drivers.thinkfinger/329

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

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

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

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

Reboot your laptop and you should be ready to swipe!

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

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

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

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

#!/bin/sh

while true; do

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

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

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

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

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

chmod a+x powermizer-loop powermizer-off

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

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

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

== EDID misdetection ==

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

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

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

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

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

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

SUSPEND_MODULES="ath_pci"

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

http://www.lesswatts.org

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

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

and run it with:

{{cmduser|sudo powertop}}

For more information see http://www.lesswatts.org/projects/powertop/

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

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

Install Ubuntu Intrepid Ibex on a T61p

2008-11-13T17:55:30Z

Dickeywang: /* EDID misdetection */

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

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

The first time you boot Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at System --> Administration --> Hardware Drivers. You will have a choice between the 173 and 177 version of the driver. Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not. However, 177 causes a log out bug that is addressed below.

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

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

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

==Microphone/Sound In==
Might need to be turned on in the mixer
==Hard Drive Active Protection System (APS ~ HDAPS)==
Please add to this section

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

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

This will be solved in intrepid-updates eventually.

For now there are a few ways to bring the interface back up (choose one):
* {{cmdroot|ip l s wlan0 up}}
* {{cmdroot|modprobe -r iwl3945 && modprobe iwl3945}}
* reboot
* suspend and resume

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

==Fingerprint Reader==

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

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

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

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

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

Enter in the popup window:

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

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

1) Install the following packages:

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

2) For your user:

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

A completed fingerprint setup should look something like this:

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

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

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

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

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

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

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

3) Enable use of reader for authentication:

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

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

4) Check uinput kernel module:

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

Start uinput:

{{cmduser|sudo modprobe uinput}}

Start on boot:

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

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

5) Enabling thinkfinger for gnome-screensaver

*create this file:
{{cmduser|sudo gedit /etc/udev/rules.d/60-thinkfinger.rules}}
with this contents:
#
# udev rules file for the thinkfinger fingerprint scanner
# gives access to the fingerprint reader to those in the "fingerprint" group
#
# Taken from:
# http://www.thinkwiki.org/wiki/Install_Ubuntu_Intrepid_Ibex_on_a_T61p#Fingerprint_Reader
# which was taken and modified from:
# http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
# http://article.gmane.org/gmane.linux.drivers.thinkfinger/329

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

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

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

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

Reboot your laptop and you should be ready to swipe!

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

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

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

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

#!/bin/sh

while true; do

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

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

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

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

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

chmod a+x powermizer-loop powermizer-off

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

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

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

== EDID misdetection ==

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

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

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

{{NOTE|A better but more complicated way would be use 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] }}

{{NOTE| }}

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

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

SUSPEND_MODULES="ath_pci"

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

http://www.lesswatts.org

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

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

and run it with:

{{cmduser|sudo powertop}}

For more information see http://www.lesswatts.org/projects/powertop/

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

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

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61

2008-08-05T06:01:44Z

Dickeywang: /* Wireless activity LED */

== Items that work out of the box ==

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

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

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

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

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

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

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

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

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

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

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

=== Open Source Intel Wifi Driver ===
The following information is important if you are upgrading from a previous version of Ubuntu to 8.04.

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

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

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

=== Compiz and XV Playback on Intel GM965/GL960 ===

With Ubuntu 7.10 (Gutsy Gibbon) you currently have to choose between using Compiz and working video playback using XV. On 8.04 (Hardy Heron) alpha 5 you can play videos using XV under compiz, it works right out of the box using the Live-CD.

=== Suspend with Nv140m ===

** Update as of July 17th 2008 -- Using 8.04.1 with the newest nvidea drivers, I had no problems suspending without any additional configuration. **

Suspend may not work even after editing acpi-support. Enable bluetooth (Fn+F5) may result in a successful suspend. NOTE: that although the wifi led does not change when Fn+F5 is used, the wifi is still toggled by this key.

'''Hal "S3 BIOS" parameter issue!'''

After doing the changes to the /etc/default/acpi-support file (described [http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.10_(Gutsy_Gibbon)_on_a_ThinkPad_T61#How_to_Suspend_with_nVidia_140m.2F570m here]), I for one, managed to have '''stable''' suspend support by creating a new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
</match>
</device>
</deviceinfo>
</pre>
{{NOTE|The problem (after reading the HAL and pm-utils documentations) is the fact that (as far as I can tell) the T61 Lenovo doesn't allow the S3 BIOS to be called *during* suspend/resume, which HAL seems to do by default (who knows, maybe there are T61s out there that do work with this default)!

This did not seem to be necessary for previous versions of Ubuntu. Also note that I have an NVIDIA card so I have no idea what to do for Intel versions.The change should also be resistant to HAL and pm-utils upgrades.}}

'''Still no suspend with nvs140m? Got Modell 6460 or 6458?'''

Fix above didn't work for me on a 15.4 wide T61 Modell 6460 with nv140m. Bios is updated to 2.14 but didn't change anything, except the usb bug is fix. Suspend seems to work fine, but resume gives me a black screen (backlight off - no reaction to brightness up) and I can hear 2 beeps. Most of the time I can reboot with ctrl+alt+delete but the screen stays dark until bios.

follow the instructions above but create the new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents instead:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</device>
</deviceinfo>
</pre>

Also you want to set the following parameter in

{{path|/etc/default/acpi-support}}
<pre>
SAVE_VIDEO_PCI_STATE=true
</pre>

{{NOTE|This works for me with mode 6460, except for one problem: You may get a white screen in xorg after resume when using compiz. If you don't have a 6460 with nvidia this file may break things for you because it doesn't care about the modell and sets the parameter for any lenovo product}}
{{NOTE|This also works for me with mode 6458, but the first wakeup from suspend takes about 20seconds, the following wakeups only some seconds. Please note that i had to change back the settings described [http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.10_(Gutsy_Gibbon)_on_a_ThinkPad_T61#How_to_Suspend_with_nVidia_140m.2F570m here] but still SAVE_VIDEO_PCI_STATE set to true}}
{{HELP|Anyone with more knowledge of hal and acpi-support is welcome to clean this up. I also don't know why this setting can be done via hal and in acpi-support.
See below!}}

'''Works for a 6457CTO:'''

After trying out all these recipes on my 6457CTO waking up from suspend still did not work. Finally I came across a blog entry which pointed out the right way: [[http://david.goodlad.ca/2008/3/14/suspend-hibernate-on-lenovo-t61 David Goodlad's blog]]. I realized that all the fixes proposing editing the acpi-support file or adding a kernel parameter acpi_sleep=s3_mode must be wrong because since hardy gnome-power-manager gets its information solely from hal. So setting up correct hal information is the right way but the proposed solution (creating a /etc/hal/fdi/information/lenovo.fdi file) did not work for me. Ok, but now step by step:

# Revert ALL the proposed fixes from above. I found out that at least the lenovo.fdi solution is actually breaking the real fix. So for sure delete /etc/hal/fdi/information/lenovo.fdi
# Find out about the excact hal name of your machine: <pre>hal-device |grep 6457</pre> where 6457 is the model number of my t61, replace it with your own. In my case it spits out something like this: system.hardware.product = '6457CTO'. So now I know that hal identifies my machine as 6457CTO.
# <pre>sudo gedit /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi</pre> and add a section to the end of the file, just above the </device> tag and replace 6457CTO with your hal device name:
<pre>

<match key="system.hardware.product" string="6457CTO">

<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</pre>

Now save and reboot. Now you might run into the problem of coming back from resume into a completely white screen where normally should be the password dialog. Entering your password blindly is not nice but at least you can resume.

{{NOTE|Somehow I couldn't make the wildcard matching work as they did in the lenovo.fdi solution, but that might be due to my shortcomings on that syntax. Anyway matching the device by its full name worked for me. Probably somebody who knows more about the matching could make that wildcard thing work to have a more general solution. Because hal also knows the xorg driver name (info.linux.driver) there should be a way to set up the quirks depending on the driver.}}

[[Category: T61]]

=== TrackPoint ===
The [[TrackPoint]] works out of the box, but does not scroll nor does the tap-clicking (press to select) feature work. Therefor see: [[#tap-to-click feature]] To enable using the middle mouse button to scroll, replace the "Configured Mouse" section in {{path|/etc/X11/xorg.conf}} with the following:
<pre>
Section "InputDevice"
Identifier "Trackpoint"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
EndSection
</pre>

{{NOTE|However, if you need to use external usb mouse, the above configuration is wrong. It will cause odd behavior. Try the following configuration from [http://gentoo-wiki.com/HARDWARE_IBM_Specific_Laptop_Guide#TrackPoint Gentoo Wiki]:}}
<pre>
Section "InputDevice"
Identifier "UltraNav TrackPoint"
Driver "mouse"
Option "Device" "/dev/input/mouse1"
Option "Protocol" "ExplorerPS/2"
Option "Emulate3Buttons" "on"
Option "Emulate3TimeOut" "50"
Option "EmulateWheel" "on"
Option "EmulateWheelTimeOut" "200"
Option "EmulateWheelButton" "2"
Option "YAxisMapping" "4 5"
Option "XAxisMapping" "6 7"
Option "ZAxisMapping" "4 5"
EndSection
</pre>

=== Audio ===

Works great out of the box, just the microphone has to be activated, it is considered a generic capture source and is muted by default.

To unmute the microphone:

*Right Click on the volume icon next to the clock and click on "Open Volume Control"

*Click Edit -> Preferences. A list of devices will be displayed, you should check the following (Do not uncheck any existing items):

Input Source
Capture

*Click Close and there should be two additional tabs "Recording" and "Options". -

*Click Recording and click on the microphone under the Capture slider so that it no longer has a red line through it, and put the slider up as it may be deactivated.

*Click Options and under capture source select internal mic.

To test your mic using Sound Recorder select Capture as the sound source.

This solution has been tested with Sound Recorder and Skype.

To get the volume controls working:

*add the following line to /etc/modprobe.d/alsa-base, then reboot

options snd-hda-intel index=0 model=thinkpad

{{NOTE|The volume controls worked fine for me out of the box on a 6460.}}

=== Multimedia Keys ===

Most Multimedia Keys work out of the box, though play, forward and stop buttons often need to be adjusted, therefore, press alt + F2 and type in gnome-keybinding-properties. Then everything works as followed:

* Fn-PgUp activates/deactivates the thinklight
* Fn-Up will trigger stop on a media player
* Fn-Down will toggle pause and play on a media player
* Fn-Left/Right go to prev/next tracks on a media player
* Fn-F2 properly locks the screen
* Fn-F3 shows remaining battery >>does not work on all machines<<
* Fn-F4 suspends (to ram)
* Fn-F9 ejects cds >>does not work on all machines, I think this is supposed to eject from a "dock"<< >>fixable with System > Preferences > Keyboard Shortcuts
* Fn-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

To enable the back, forward, and the menu keys you'll need to teach XKB what they are.

* Check the '''XkbLayout''' option (under '''InputDevice''') in your {{path|/etc/X11/xorg.conf}} file to determine which keyboard layout Ubuntu is using (I'll use 'us' for the example).
* Navigate to {{path|/etc/X11/xkb/symbols}} and, as root, open the appropriate layout file (as determined above) in your favorite editor.
{{cmduser|cd /etc/X11/xkb/symbols}}
{{cmduser|sudo gedit us}}
* In the '''xkb_symbols "basic"''' section after the '''name[Group1]= "x";''' (where x is a country name, or similar) line add the following:
key <I63> { [ Menu ] };
key <I69> { [ XF86Forward ] };
key <I6A> { [ XF86Back ] };
* Now log out and back in and all three of the buttons should function.

=== Thinkpad Button ===

Paste the following into /usr/share/hotkey-setup/ibm.hk
setkeycodes e017 148 # thinkpad button
You can also just type this into a terminal, to test it for the time of the current session.

Paste the following into the right file in /usr/share/xmodmap (check your country code)
keycode 159 = XF86Terminal
For immediate availability of the button, reload the file by executing
xmodmap <xmodmap.file>

Then use the "Keyboard Shortcuts" tool under "Preferences".

== Items that don't work (a.k.a.: items that need more intense tweaking to get fixed)==

=== tap-to-click feature ===

For the tap-to-click feature (taping the stick instead of using the left mouse button) i used a configure trackpoint utility: [http://tpctl.sourceforge.net/configure-trackpoint.html] there is a package for ubuntu 7.04 i386, but i compiled it by myself (using amd64):

1.) download the .tar.gz file

2.) unpack it

3.) install libgnomeui-dev

{{cmduser|sudo aptitude install libgnomeui-dev}}

4.) in the folder, do:

{{cmduser|./configure}}

if everything worked fine:

{{cmduser|make}}

then install it:

{{cmduser|sudo make install}}

5.a) Gnome : Open it: System > configure trackpoint, and configure on your needs

5.b) Kde : K-menu > Prefences > configure trackpoint > right-click > edit entry, edit "command" to "kdesu configure-trackpoint"

Save & exit

Open it : K-menu > Prefences > configure trackpoint and configure on your needs

=== Hotswapping ===

{{HELP|We need someone who is able to get hotswaping to work properly, this is not the right was to do this!}}
With the new kernel, bay-drivers changed, so if you remove the ultrabay it will freeze your system! You can hack it with a simple comand, first you have to look where the device is:

{{cmduser|less /sys/class/scsi_device/(x)\:0\:0\:0/device/model}}

for (x) first put in 0, if it tells you DVD or the name of the model you want to hotswap youre right. if not, go on with 1, 2 or 3...

then, once you are sure (I deactivated my harddisk like that) you put in:

{{cmduser|echo 1 {{!}} sudo tee /sys/class/scsi_device/(x)\:0\:0\:0/device/delete}}

Now you should be able to remove the device.

{{WARN|Do not use it for harddisks, be sure you unmounted it before! This is just a bad hack, if anyone knows how to get it right --> publish!}}

If Ubuntu does not reactivate the device after putting it in again, do:

{{cmduser|echo 0 0 0 {{!}} sudo tee /sys/class/scsi_host/host1/scan}}

=== Wireless activity LED ===

The LED is not implemented at least in the IWL4965 driver. For the Atheros wifi cards look at the solution below.

A patch posted in this [http://bughost.org/bugzilla/show_bug.cgi?id=1209 thread] works for me on R61 with IWL4965 card.

{{HELP|A howto is needed showing the process of implementing the patch in Hardy Heron. If anyone knows how to do this, please create a quick howto and either put it here or link to it from this page. Please and thank you.}}

As an alternative, you can install a backported IWL4965 driver that ''may'' fix the LED problem on your system.

To active WiFi LED,

sudo apt-get install linux-backports-modules-hardy

{{NOTE|On some machines, (at least one running IWL3945 & IWL4965) applying the above turns on the LED permanently. It should flicker as data is being transmitted. Also, with the above modification, after turning off wireless and then turning it back on (via the switch on the front of the machine) wireless is not reactivated, so not very helpful}}

You can download a compatible [http://wireless.kernel.org/download/compat-wireless-2.6/compat-wireless-2.6.tar.bz2 driver] which supports WiFi led flicking and build it with modifying the {{path|config.mk}} by adding {{bootparm|CONFIG_IWL3945_LEDS|y}} and {{bootparm|CONFIG_IWLWIFI_LEDS|y}} these two options. For Ubuntu/Debian users, build-essential, linux-source-2.6.24 and linux-headers-generic packages are required.

{{HELP|I added the above lines to the config.mk file and it would not make or make install correctly. I received an error 2 at the end of the make. If you have had success, where did you put the items in the config.mk file for it to make and make install correctly? Thanks in advance.}}

To compile the with these two options enabled, you need to insert the following command into config.mk as well:

CONFIG_IWLWIFI_DEBUG=y

==== To enable the Wifi LED with the Atheros cards ====

First check if this solution works on your computer. Open a terminal and run this commands:

sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3

Now connect to a wireless network and the LED should start working. If so and you want to make the changes permanent then:

1) Create a file ~/wifiLED and copy/paste the following into it:

#!/bin/bash
#
# Commands to enable the wireless LED
sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3

2) sudo cp ~/wifiLED /etc/init.d

3) sudo chmod 755 /etc/init.d/wifiLED

4) sudo update-rc.d wifiLED defaults 90

After you reboot your wireless led should be working.

--[[User:Lunatico|Lunatico]] 14:50, 26 July 2008 (CEST)

=== Hidden SSID ===
It has been reported that users wanting to access Hidden SSIDs have to enter the SSID and password manually in Network Manager to connect. Even after the SSID is saved in Network Manager, it will not reconnect automatically. The user has to connect manually by entering the information as previously described.
It appears that updating the driver by following the instructions [http://linuxwireless.org/en/users/Download here] resolves this issue.

=== Hard Disk Parking ===
Getting hard disk parking to work:

tp_smapi patch is not needed in [http://packages.ubuntu.com/search?keywords=linux-image-2.6.24-18&searchon=names&suite=hardy&section=all linux-image-2.6.24-18]

1. Patch your kernel with the 'protect' [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch patch].

2. Installing the hdapsd daemon which does the actual parking.

{{cmduser|sudo apt-get install hdapsd hdaps-utils}}

== some other tweaks ==

=== screenblank with {{key|Fn}} + {{key|F3}} ===

Its ok, and might be usefull to get the estimated batterytime when pressing {{key|Fn}}+{{key|F3}}, as it should be. But i dont need that, i find the earlier command for {{key|F3}}, to blank the screen, more useful to save batterylife better.

For that, you must edit {{path|/etc/acpi/thinkpad-lockbattery.sh}} and replace LENOVO by IBM, and IBM by LENOVO :). Do not forget to copy the file before you change it!

=== Enable normal User to Limit CPU Speed ===
To let user set the CPU limit you need to open a Terminal an type there
sudo dpkg-reconfigure gnome-applets
answer the question with yes

=== Fix bluish WSXGA+ displays ===
Many T61 owners complain about a very bluish color temperature: My T61 WSXGA+ was also way too blue. I came across a thread at the notebook review forum http://forum.notebookreview.com/showthread.php?t=174408 which provided two useful ICC profiles which fixed the situation for me. Just install xcalib
sudo apt-get install xcalib
and load one of these profiles.

[[Category: Ubuntu 8.04]]

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

2008-08-04T22:23:58Z

Dickeywang: /* Hibernation */

== Hotswap ==

i really dont understand the thinkwiki hotspap howto, cant we put the most important in here, if people who got hotswapping right can show their fixes with ubuntu? [[User:Karlrt|Karlrt]] 23:13, 2 June 2008 (CEST)

The Hotswap-problem can be solved by booting the kernel with "libata.noacpi=1". This can be done under Ubuntu by adding "options libata noacpi=1" to /etc/modprobe.d/options and running "update-initramfs -u".
See also [http://www.mail-archive.com/ibm-acpi-devel@lists.sourceforge.net/msg01204.html this discussion] --[[User:Crowley12|Crowley12]] 21:49, 2 June 2008 (CEST)

Hi, I'm new here.
I just got a T61, and discovered that the instructions for enabling the trackpoint [[Installing_Ubuntu_7.10_%28Gutsy_Gibbon%29_on_a_ThinkPad_T61#Trackpad_scrolling | which worked for 7.10]] no longer work in 8.04. This seems to be due to the change to X.org 7.3. Does someone want to add that to the page, or know of a fix? [[User:Zedlander|Zedlander]] 07:56, 6 April 2008 (CEST)

== Trackpoint ==

The trackpoint seems to be working in the latest beta on my T61 without issue.

== Article purpose ==

Should this article be divided into an upgrade section and a fresh install section? Should there be an upgrade article and a fresh install article?

== Hibernation ==
As for me there is a big problem with hibernation on Nvidia enabled Thinkpads. After resume, screen is covered with black and green patteren with a half of the slash screen in the background.. After 30 s computer reboots. This issue still persists under stable 8.04 (I'm using hardy from tribe 4).
--[[User:Barteq|Barteq]] 21:43, 6 May 2008 (CEST)

It is mentioned[http://www.nvnews.net/vbulletin/showpost.php?p=1625535&postcount=17] that the new 173.08 Nvidia driver does solve the hibernate problem, however since it is a beta driver, it will not be included in EnvyNG, so anyone who want to try it out need to install the driver manually.

Same thing on this driver.. Unable to wake up from hibernation.
Additional it doesn't (yet?) support <nowiki>"OnDemandVBlankInterrupts" "true"</nowiki> xorg option making 120 wakeups / s in powertop, while second monitor attached..
--[[User:Barteq|Barteq]] 21:43, 6 May 2008 (CEST)

Any confirmation that 173.08 does fix hibernation?

With the new driver 173.14.05 hibernation seems to work. But during resume these black and green patterns still appear.
Suspend to ram works only partially. Sometimes the screen remains blank, even with the hal-fix applied. Any ideas?
--[[User:Mstephan|Mstephan]] 10:02, 30 May 2008 (CEST)

Suspend to ram works still fine under the newest driver. I haven't checked hibernation, but my kernel supports tux-on-ice - so results may be different.
--[[User:Barteq|Barteq]] 03:50, 2 June 2008 (CEST)

173.14.05 OK, finally I am able to get both suspend and hibernate to work with the new 173.14.05 driver on my T61p (64-bit Hardy). pm-hibernate seems to work automatically, although someone has suggested to modify the [http://launchpadlibrarian.net/14044012/acpi-support /etc/default/acpi-support] so that suspend won't report some oops.
--[[User:dickeywang|Dickey]]

Dickey -- what files did you have to modify for successful suspend and hibernate?

My Model: 6458 (DL3) // Suspend and Hibernate works with Hardy (without the .1 already), but it takes up to 5 minutes to resume, with a lot of strange and colorized effects on the screen (with no config changes). After doing the changes to /etc/default/acpi-support described [http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.10_(Gutsy_Gibbon)_on_a_ThinkPad_T61#How_to_Suspend_with_nVidia_140m.2F570m here] it stopped working at all. After reverting the changes except SAVE_VIDEO_PCI_STATE=true and adding the 2 additional lines to lenovo.fdi '''(so i only did the steps described in "Still no suspend with nvs140m? Got Modell 6460?") gives me a working and fast suspend''', but the first suspend wakeup needs more than 20 seconds. And hibernate still takes a very long time to resume. --[[User:Dedi|Dedi]] 23:45, 2 August 2008 (CEST)

The hibernate does take a lot of time to resume(much longer than a complete reboot), but I assume it is normal since when resume from hibernate the machine needs to read a lot of memory pages from the HDD. I didn't do any modification except I installed the new Nvidia driver and followed the guide on the official Ubuntu page[https://help.ubuntu.com/community/NvidiaLaptopBinaryDriverSuspend].
However, I just found that installing linux-backport-module(which is said to solve the wifi LED problem) would cause some reliability problem of suspend to RAM. It seems when the backport module is installed, if suspend/resume for a few times, the iwl4965 module could not disable the AGN card before the machine goes into suspend, therefore after resume, the iwl4965 would try to re-enable the already enabled AGN card which causes the wireless to stop working. I tried to compile the compact-wirless driver, but it seems the up-to-date compact wireless driver (as of August 4,2008) is even more unstable than the backport module.
--[[User:DickeyWang|Dickey]] August 4 2008

== Docking Station ==
Any luck on getting the DVI port on the advanced mini dock working?

On nvidia card with binary drivers it works fine. Even while writing this ;)
Use nvidia-settings or change boot display in bios to vga+dvi
--[[User:Barteq|Barteq]] 03:50, 2 June 2008 (CEST)

== HDAPS protection ==
Best way to use it is http://zen-sources.org/ kernel. Works like a charm. The only bad thing is hat hdapsd uses 50 wakeups/s so it consumes battery more quickly.

<nowiki>
[ 7352.997416] scsi_protect_queue(): head parked..
[ 7355.762197] scsi_unprotect_queue(): No pending I/O, re-enabling power management..
</nowiki>

== Wireless activity LED ==
with the latest (K)ubuntu kernel für Hardy Heron 8.04, the WLAN light shows, when WLAN is activated

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

2008-08-04T22:22:21Z

Dickeywang: /* Hibernation */

== Hotswap ==

i really dont understand the thinkwiki hotspap howto, cant we put the most important in here, if people who got hotswapping right can show their fixes with ubuntu? [[User:Karlrt|Karlrt]] 23:13, 2 June 2008 (CEST)

The Hotswap-problem can be solved by booting the kernel with "libata.noacpi=1". This can be done under Ubuntu by adding "options libata noacpi=1" to /etc/modprobe.d/options and running "update-initramfs -u".
See also [http://www.mail-archive.com/ibm-acpi-devel@lists.sourceforge.net/msg01204.html this discussion] --[[User:Crowley12|Crowley12]] 21:49, 2 June 2008 (CEST)

Hi, I'm new here.
I just got a T61, and discovered that the instructions for enabling the trackpoint [[Installing_Ubuntu_7.10_%28Gutsy_Gibbon%29_on_a_ThinkPad_T61#Trackpad_scrolling | which worked for 7.10]] no longer work in 8.04. This seems to be due to the change to X.org 7.3. Does someone want to add that to the page, or know of a fix? [[User:Zedlander|Zedlander]] 07:56, 6 April 2008 (CEST)

== Trackpoint ==

The trackpoint seems to be working in the latest beta on my T61 without issue.

== Article purpose ==

Should this article be divided into an upgrade section and a fresh install section? Should there be an upgrade article and a fresh install article?

== Hibernation ==
As for me there is a big problem with hibernation on Nvidia enabled Thinkpads. After resume, screen is covered with black and green patteren with a half of the slash screen in the background.. After 30 s computer reboots. This issue still persists under stable 8.04 (I'm using hardy from tribe 4).
--[[User:Barteq|Barteq]] 21:43, 6 May 2008 (CEST)

It is mentioned[http://www.nvnews.net/vbulletin/showpost.php?p=1625535&postcount=17] that the new 173.08 Nvidia driver does solve the hibernate problem, however since it is a beta driver, it will not be included in EnvyNG, so anyone who want to try it out need to install the driver manually.

Same thing on this driver.. Unable to wake up from hibernation.
Additional it doesn't (yet?) support <nowiki>"OnDemandVBlankInterrupts" "true"</nowiki> xorg option making 120 wakeups / s in powertop, while second monitor attached..
--[[User:Barteq|Barteq]] 21:43, 6 May 2008 (CEST)

Any confirmation that 173.08 does fix hibernation?

With the new driver 173.14.05 hibernation seems to work. But during resume these black and green patterns still appear.
Suspend to ram works only partially. Sometimes the screen remains blank, even with the hal-fix applied. Any ideas?
--[[User:Mstephan|Mstephan]] 10:02, 30 May 2008 (CEST)

Suspend to ram works still fine under the newest driver. I haven't checked hibernation, but my kernel supports tux-on-ice - so results may be different.
--[[User:Barteq|Barteq]] 03:50, 2 June 2008 (CEST)

173.14.05 OK, finally I am able to get both suspend and hibernate to work with the new 173.14.05 driver on my T61p (64-bit Hardy). pm-hibernate seems to work automatically, although someone has suggested to modify the [http://launchpadlibrarian.net/14044012/acpi-support /etc/default/acpi-support] so that suspend won't report some oops.
--[[User:dickeywang|Dickey]]

Dickey -- what files did you have to modify for successful suspend and hibernate?

My Model: 6458 (DL3) // Suspend and Hibernate works with Hardy (without the .1 already), but it takes up to 5 minutes to resume, with a lot of strange and colorized effects on the screen (with no config changes). After doing the changes to /etc/default/acpi-support described [http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.10_(Gutsy_Gibbon)_on_a_ThinkPad_T61#How_to_Suspend_with_nVidia_140m.2F570m here] it stopped working at all. After reverting the changes except SAVE_VIDEO_PCI_STATE=true and adding the 2 additional lines to lenovo.fdi '''(so i only did the steps described in "Still no suspend with nvs140m? Got Modell 6460?") gives me a working and fast suspend''', but the first suspend wakeup needs more than 20 seconds. And hibernate still takes a very long time to resume. --[[User:Dedi|Dedi]] 23:45, 2 August 2008 (CEST)

The hibernate does take a lot of time to resume(much longer than a complete reboot), but I assume it is normal since when resume from hibernate the machine needs to read a lot of memory pages from the HDD. I didn't do any modification except I installed the new Nvidia driver and followed the guide on the official Ubuntu page[https://help.ubuntu.com/community/NvidiaLaptopBinaryDriverSuspend].
However, I just found that installing linux-backport-module(which is said to solve the wifi LED problem) would cause some reliability problem of suspend to RAM. It seems when the backport module is installed, if suspend/resume for a few times, the iwl4965 module could not disable the AGN card therefore after resume, the wireless would stop working. I tried to compile the compact-wirless driver, but it seems the up-to-date compact wireless driver (as of August 4,2008) is even more unstable than the backport module.
--[[User:DickeyWang|Dickey]] August 4 2008

== Docking Station ==
Any luck on getting the DVI port on the advanced mini dock working?

On nvidia card with binary drivers it works fine. Even while writing this ;)
Use nvidia-settings or change boot display in bios to vga+dvi
--[[User:Barteq|Barteq]] 03:50, 2 June 2008 (CEST)

== HDAPS protection ==
Best way to use it is http://zen-sources.org/ kernel. Works like a charm. The only bad thing is hat hdapsd uses 50 wakeups/s so it consumes battery more quickly.

<nowiki>
[ 7352.997416] scsi_protect_queue(): head parked..
[ 7355.762197] scsi_unprotect_queue(): No pending I/O, re-enabling power management..
</nowiki>

== Wireless activity LED ==
with the latest (K)ubuntu kernel für Hardy Heron 8.04, the WLAN light shows, when WLAN is activated

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

2008-06-14T22:50:35Z

Dickeywang: /* Hibernation */

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

2008-06-14T22:31:02Z

Dickeywang: /* Hibernation */

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

2008-05-06T09:19:08Z

Dickeywang: /* Hibernation */

Hi, I'm new here.
I just got a T61, and discovered that the instructions for enabling the trackpoint [[Installing_Ubuntu_7.10_%28Gutsy_Gibbon%29_on_a_ThinkPad_T61#Trackpad_scrolling | which worked for 7.10]] no longer work in 8.04. This seems to be due to the change to X.org 7.3. Does someone want to add that to the page, or know of a fix? [[User:Zedlander|Zedlander]] 07:56, 6 April 2008 (CEST)

== Trackpoint ==

The trackpoint seems to be working in the latest beta on my T61 without issue.

== Article purpose ==

Should this article be divided into an upgrade section and a fresh install section? Should there be an upgrade article and a fresh install article?

== Hibernation ==
As for me there is a big problem with hibernation on Nvidia enabled Thinkpads. After resume, screen is covered with black and green patteren with a half of the slash screen in the background.. After 30 s computer reboots. This issue still persists under stable 8.04 (I'm using hardy from tribe 4).

It is mentioned[http://www.nvnews.net/vbulletin/showpost.php?p=1625535&postcount=17] that the new 173.08 Nvidia driver does solve the hibernate problem, however since it is a beta driver, it will not be included in EnvyNG, so anyone who want to try it out need to install the driver manually.