ThinkWiki - User contributions [en]

Talk:Install Ubuntu Intrepid Ibex on a T61p

2009-01-26T17:10:12Z

Gertvdijk: fix start_charge_thresh

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

== 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-26T17:07:30Z

Gertvdijk: start_charge_thresh -> stop_charge_thresh

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

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

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

System --> Administration --> Hardware Drivers.

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

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

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

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

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

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

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

#!/bin/sh

while true; do

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

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

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

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

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

chmod a+x powermizer-loop powermizer-off

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

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

=== EDID misdetection ===

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

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

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

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

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

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

This will be solved in intrepid-updates eventually.

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

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

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

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

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

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

==Fingerprint Reader==

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

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

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

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

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

Enter in the popup window:

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

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

1) Install the following packages:

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

2) For your user:

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

A completed fingerprint setup should look something like this:

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

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

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

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

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

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

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

3) Enable use of reader for authentication:

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

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

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

4) Check uinput kernel module:

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

Start uinput:

{{cmduser|sudo modprobe uinput}}

Start on boot:

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

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

5) Enabling thinkfinger for gnome-screensaver

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

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

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

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

Reboot your laptop and you should be ready to swipe!

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

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

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

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

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

== Black Screen on Resume ==
On the 6459CTO with default 8.10 install suspend did not work. 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-26T17:00:20Z

Gertvdijk: changed way of adding intrepid-proposed to repositories (the GUI way)

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

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

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

System --> Administration --> Hardware Drivers.

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

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

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

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

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

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

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

#!/bin/sh

while true; do

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

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

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

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

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

chmod a+x powermizer-loop powermizer-off

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

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

=== EDID misdetection ===

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

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

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

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

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

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

This will be solved in intrepid-updates eventually.

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

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

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

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

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

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

==Fingerprint Reader==

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

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

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

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

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

Enter in the popup window:

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

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

1) Install the following packages:

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

2) For your user:

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

A completed fingerprint setup should look something like this:

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

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

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

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

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

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

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

3) Enable use of reader for authentication:

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

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

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

4) Check uinput kernel module:

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

Start uinput:

{{cmduser|sudo modprobe uinput}}

Start on boot:

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

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

5) Enabling thinkfinger for gnome-screensaver

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

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

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

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

Reboot your laptop and you should be ready to swipe!

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

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

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

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

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

== Black Screen on Resume ==
On the 6459CTO with default 8.10 install suspend did not work. 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/start_charge_thresh
(by default this was set to 86% on my laptop)

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

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

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

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

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

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

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

Install Ubuntu Intrepid Ibex on a T61p

2008-12-03T00:38:12Z

Gertvdijk: /* Battery control by tp_smapi */

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

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

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

System --> Administration --> Hardware Drivers.

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

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

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

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

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

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

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

#!/bin/sh

while true; do

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

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

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

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

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

chmod a+x powermizer-loop powermizer-off

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

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

=== EDID misdetection ===

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

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

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

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

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

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

This will be solved in intrepid-updates eventually.

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

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

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

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

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

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

==Fingerprint Reader==

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

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

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

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

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

Enter in the popup window:

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

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

1) Install the following packages:

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

2) For your user:

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

A completed fingerprint setup should look something like this:

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

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

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

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

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

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

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

3) Enable use of reader for authentication:

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

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

4) Check uinput kernel module:

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

Start uinput:

{{cmduser|sudo modprobe uinput}}

Start on boot:

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

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

5) Enabling thinkfinger for gnome-screensaver

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

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

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

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

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

Reboot your laptop and you should be ready to swipe!

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

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

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

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

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

SUSPEND_MODULES="ath_pci"

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

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

http://www.lesswatts.org

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

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

and run it with:

{{cmduser|sudo powertop}}

For more information see http://www.lesswatts.org/projects/powertop/
== Battery control by tp_smapi ==
You need to load a kernel module first:
{{cmduser|sudo modprobe tp_smapi}}
Now, you will be able to have significantly more control over your battery charging via /sys/devices/platform/smapi.

For example, you could set a threshold value of 90% for charging (this should help against the loss of capacity through charging cycles).
sudo su -
cd /sys/devices/platform/smapi/BAT0/
echo "90" > stop_charge_thresh

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

Or, while AC connected, force discharging of your battery:
sudo su -
cd /sys/devices/platform/smapi/BAT0/
echo "1" > force_discharge

For convenience, you could load the kernel module at boot time by adding it to /etc/modules.

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

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

Install Ubuntu Intrepid Ibex on a T61p

2008-12-03T00:37:41Z

Gertvdijk: added part: battery control by tp_smapi

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

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

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

System --> Administration --> Hardware Drivers.

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

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

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

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

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

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

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

#!/bin/sh

while true; do

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

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

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

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

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

chmod a+x powermizer-loop powermizer-off

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

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

=== EDID misdetection ===

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

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

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

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

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

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

This will be solved in intrepid-updates eventually.

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

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

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

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

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

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

==Fingerprint Reader==

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

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

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

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

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

Enter in the popup window:

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

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

1) Install the following packages:

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

2) For your user:

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

A completed fingerprint setup should look something like this:

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

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

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

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

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

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

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

3) Enable use of reader for authentication:

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

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

4) Check uinput kernel module:

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

Start uinput:

{{cmduser|sudo modprobe uinput}}

Start on boot:

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

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

5) Enabling thinkfinger for gnome-screensaver

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

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

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

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

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

Reboot your laptop and you should be ready to swipe!

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

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

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

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

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

SUSPEND_MODULES="ath_pci"

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

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

http://www.lesswatts.org

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

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

and run it with:

{{cmduser|sudo powertop}}

For more information see http://www.lesswatts.org/projects/powertop/
== Battery control by tp_smapi ==
You need to load a kernel module first:
{{cmduser|sudo modprobe tp_smapi}}
Now, you will be able to have significantly more control over your battery charging via {{{/sys/devices/platform/smapi}}}.

For example, you could set a threshold value of 90% for charging (this should help against the loss of capacity through charging cycles).
sudo su -
cd /sys/devices/platform/smapi/BAT0/
echo "90" > stop_charge_thresh

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

Or, while AC connected, force discharging of your battery:
sudo su -
cd /sys/devices/platform/smapi/BAT0/
echo "1" > force_discharge

For convenience, you could load the kernel module at boot time by adding it to /etc/modules.

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

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

Install Ubuntu Intrepid Ibex on a T61p

2008-11-06T18:20:07Z

Gertvdijk: /* Bugs and Regressions */

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

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

==Not working==
*Logging out or restarting X
** Workaround available (see below)
*The hard radio killswitch for Intel WLAN.

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

To enable 3D acceleration, the proprietary NVidia driver must be installed. The first time you boot into Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at System --> Administration --> Hardware Drivers. You will have a choice between the 173 and 177 version of the driver. I would strongly recommend the latter one, because it will provide Suspend to disk functionality in favour of the 173 version.

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

At the time of writing I am not able to restart X or log out from my GNOME session. X will fail to start and will eventually fall back to failsafe config (VESA drivers). A workaround is available. See below.

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

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

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

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

#!/bin/sh

while true; do

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

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

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

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

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

chmod a+x powermizer-loop powermizer-off

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

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

==== EDID misdetection ====

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

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

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

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

It is a known issue in the 177 version of the binary NVidia driver which has not yet been addressed by NVidia. See Launchpad bug [http://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-177/+bug/258357 258357].
There are two workarounds:
* Use the older 173 version (without Suspend to Disk functionality and with slower resume from Suspend to RAM).
* Set in /etc/gdm/gdm.conf the value for GdmXServerTimeout somewhat higher than 35, like 45. X will hang approx 35 seconds and this value is the treshold for GDM to assume X is faulty.

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

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

SUSPEND_MODULES="ath_pci"

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

This will be solved in intrepid-updates eventually.

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

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

= Compared to Hardy =
Why upgrade your T61p to Intrepid or why not? (Specific for T61p)
== Improvements ==
*Ricoh SD card reader now reads read-only SD card. (Tested with Adata 150X 2GB SD card)
*Newer Wireless LAN drivers. For Intel cards this results in working LED, more sensitive reception, increased stability of connections and some 802.1x bugfixes.
*Out-of-the-box Suspend to RAM functionality (also faster resume).
*Working but slow Suspend to Disk functionality.
== Bugs and Regressions ==
*Hard radio killswitch (at the front) cannot bring WLAN back up after killing it. (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-06T18:16:01Z

Gertvdijk: /* Fix for choppy Compiz animations */

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

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

==Not working==
*Logging out or restarting X
** Workaround available (see below)
*The hard radio killswitch for Intel WLAN.

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

To enable 3D acceleration, the proprietary NVidia driver must be installed. The first time you boot into Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at System --> Administration --> Hardware Drivers. You will have a choice between the 173 and 177 version of the driver. I would strongly recommend the latter one, because it will provide Suspend to disk functionality in favour of the 173 version.

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

At the time of writing I am not able to restart X or log out from my GNOME session. X will fail to start and will eventually fall back to failsafe config (VESA drivers). A workaround is available. See below.

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

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

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

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

#!/bin/sh

while true; do

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

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

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

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

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

chmod a+x powermizer-loop powermizer-off

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

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

==== EDID misdetection ====

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

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

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

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

It is a known issue in the 177 version of the binary NVidia driver which has not yet been addressed by NVidia. See Launchpad bug [http://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-177/+bug/258357 258357].
There are two workarounds:
* Use the older 173 version (without Suspend to Disk functionality and with slower resume from Suspend to RAM).
* Set in /etc/gdm/gdm.conf the value for GdmXServerTimeout somewhat higher than 35, like 45. X will hang approx 35 seconds and this value is the treshold for GDM to assume X is faulty.

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

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

SUSPEND_MODULES="ath_pci"

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

This will be solved in intrepid-updates eventually.

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

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

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

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

User:Gertvdijk

2008-11-06T18:10:21Z

Gertvdijk: â†Created page with 'Use my GPG key if you want: 0x88EF2026'

Use my GPG key if you want: 0x88EF2026

Install Ubuntu Intrepid Ibex on a T61p

2008-11-06T18:04:17Z

Gertvdijk: /* Display/Video */

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

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

==Not working==
*Logging out or restarting X
** Workaround available (see below)
*The hard radio killswitch for Intel WLAN.

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

To enable 3D acceleration, the proprietary NVidia driver must be installed. The first time you boot into Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at System --> Administration --> Hardware Drivers. You will have a choice between the 173 and 177 version of the driver. I would strongly recommend the latter one, because it will provide Suspend to disk functionality in favour of the 173 version.

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

At the time of writing I am not able to restart X or log out from my GNOME session. X will fail to start and will eventually fall back to failsafe config (VESA drivers). A workaround is available. See below.

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

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

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

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

#!/bin/sh

while true; do

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

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

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

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

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

chmod a+x powermizer-loop powermizer-off

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

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

==== EDID misdetection ====

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

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

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

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

It is a known issue in the 177 version of the binary NVidia driver which has not yet been addressed by NVidia. See Launchpad bug [http://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-177/+bug/258357 258357].
There are two workarounds:
* Use the older 173 version (without Suspend to Disk functionality and with slower resume from Suspend to RAM).
* Set in /etc/gdm/gdm.conf the value for GdmXServerTimeout somewhat higher than 35, like 45. X will hang approx 35 seconds and this value is the treshold for GDM to assume X is faulty.

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

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

SUSPEND_MODULES="ath_pci"

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

This will be solved in intrepid-updates eventually.

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

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

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

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

Install Ubuntu Intrepid Ibex on a T61p

2008-11-06T18:00:15Z

Gertvdijk: /* Not able to restart X */

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

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

==Not working==
*Logging out or restarting X
** Workaround available (see below)
*The hard radio killswitch for Intel WLAN.

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

To enable 3D acceleration, the proprietary NVidia driver must be installed. The first time you boot into Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at System --> Administration --> Hardware Drivers. You will have a choice between the 173 and 177 version of the driver. I would strongly recommend the latter one, because it will provide Suspend to disk functionality in favour of the 173 version.

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

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

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

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

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

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

#!/bin/sh

while true; do

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

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

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

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

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

chmod a+x powermizer-loop powermizer-off

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

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

==== EDID misdetection ====

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

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

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

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

It is a known issue in the 177 version of the binary NVidia driver which has not yet been addressed by NVidia. See Launchpad bug [http://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-177/+bug/258357 258357].
There are two workarounds:
* Use the older 173 version (without Suspend to Disk functionality and with slower resume from Suspend to RAM).
* Set in /etc/gdm/gdm.conf the value for GdmXServerTimeout somewhat higher than 35, like 45. X will hang approx 35 seconds and this value is the treshold for GDM to assume X is faulty.

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

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

SUSPEND_MODULES="ath_pci"

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

This will be solved in intrepid-updates eventually.

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

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

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

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

Install Ubuntu Intrepid Ibex on a T61p

2008-11-06T17:52:04Z

Gertvdijk: /* Radio Killswitch */

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

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

==Not working==
*Logging out or restarting X
** Workaround available (see below)
*The hard radio killswitch for Intel WLAN.

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

To enable 3D acceleration, the proprietary NVidia driver must be installed. The first time you boot into Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at System --> Administration --> Hardware Drivers. You will have a choice between the 173 and 177 version of the driver. I would strongly recommend the latter one, because it will provide Suspend to disk functionality in favour of the 173 version.

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

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

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

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

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

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

#!/bin/sh

while true; do

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

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

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

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

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

chmod a+x powermizer-loop powermizer-off

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

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

==== EDID misdetection ====

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

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

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

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

It is a known issue in the 177 version of the binary NVidia driver which has not yet been addressed by NVidia. See Launchpad bug [http://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-177/+bug/258357 258357].
There are two workarounds:
* Use the older 173 version (without Suspend to Disk functionality and with slower resume from Suspend to RAM).
* Set in /etc/gdm/gdm.conf the value for GdmXServerTimeout somewhat higher than 35, like 45. X will hang approx 35 seconds and this value is the treshold for GDM to assume X is faulty.

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

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

SUSPEND_MODULES="ath_pci"

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

This will be solved in intrepid-updates eventually.

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

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

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

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

Install Ubuntu Intrepid Ibex on a T61p

2008-11-06T17:48:57Z

Gertvdijk: /* Not able to restart X */

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

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

==Not working==
*Logging out or restarting X
** Workaround available (see below)
*The hard radio killswitch for Intel WLAN.

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

To enable 3D acceleration, the proprietary NVidia driver must be installed. The first time you boot into Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at System --> Administration --> Hardware Drivers. You will have a choice between the 173 and 177 version of the driver. I would strongly recommend the latter one, because it will provide Suspend to disk functionality in favour of the 173 version.

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

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

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

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

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

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

#!/bin/sh

while true; do

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

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

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

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

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

chmod a+x powermizer-loop powermizer-off

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

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

==== EDID misdetection ====

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

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

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

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

It is a known issue in the 177 version of the binary NVidia driver which has not yet been addressed by NVidia. See Launchpad bug [http://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-177/+bug/258357 258357].
There are two workarounds:
* Use the older 173 version (without Suspend to Disk functionality and with slower resume from Suspend to RAM).
* Set in /etc/gdm/gdm.conf the value for GdmXServerTimeout somewhat higher than 35, like 45. X will hang approx 35 seconds and this value is the treshold for GDM to assume X is faulty.

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

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

SUSPEND_MODULES="ath_pci"

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

This will be solved in intrepid-updates eventually.

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

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

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

Install Ubuntu Intrepid Ibex on a T61p

2008-11-06T17:45:48Z

Gertvdijk: /* Not working */

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

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

==Not working==
*Logging out or restarting X
** Workaround available (see below)
*The hard radio killswitch for Intel WLAN.

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

To enable 3D acceleration, the proprietary NVidia driver must be installed. The first time you boot into Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at System --> Administration --> Hardware Drivers. You will have a choice between the 173 and 177 version of the driver. I would strongly recommend the latter one, because it will provide Suspend to disk functionality in favour of the 173 version.

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

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

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

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

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

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

#!/bin/sh

while true; do

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

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

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

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

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

chmod a+x powermizer-loop powermizer-off

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

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

==== EDID misdetection ====

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

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

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

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

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

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

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

SUSPEND_MODULES="ath_pci"

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

This will be solved in intrepid-updates eventually.

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

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

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

Talk:Install Ubuntu Intrepid Ibex on a T61p

2008-11-06T17:42:51Z

Gertvdijk: /* WiFi & HW RFkill */

Talk:Install Ubuntu Intrepid Ibex on a T61p

2008-11-06T17:42:06Z

Gertvdijk: /* Log out & NVidia */

Install Ubuntu Intrepid Ibex on a T61p

2008-10-29T22:34:18Z

Gertvdijk:

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

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

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

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

To enable 3D acceleration, the proprietary NVidia driver must be installed. The first time you boot into Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at System --> Administration --> Hardware Drivers. You will have a choice between the 173 and 177 version of the driver. I would strongly recommend the latter one, because it will provide Suspend to disk functionality in favour of the 173 version.

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

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

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

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

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

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.

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

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

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

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

This will be solved in intrepid-updates eventually.

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

= Compared to Hardy =
Why upgrade your T61p to Intrepid or why not? (Specific for T61p)
== Improvements ==
*Ricoh SD card reader now reads read-only SD card. (Tested with Adata 150X 2GB SD card)
*Newer Wireless LAN drivers. For Intel cards this results in working LED, more sensitive reception, increased stability of connections and some 802.1x bugfixes.
*Out-of-the-box Suspend to RAM functionality (also faster resume).
*Working but slow Suspend to Disk functionality.
== Bugs and Regressions ==
*Hard radio killswitch (at the front) cannot bring WLAN back up after killing it.
*Atheros WLAN not working after resume from Suspend to RAM.

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

Install Ubuntu Intrepid Ibex on a T61p

2008-10-29T22:13:31Z

Gertvdijk: /* Working out-of-the-box */

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

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

==Small issues with...==
* The radio killswitch.

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

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

To enable 3D acceleration, the proprietary NVidia driver must be installed. The first time you boot into Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at System --> Administration --> Hardware Drivers. You will have a choice between the 173 and 177 version of the driver. I would strongly recommend the latter one, because it will provide Suspend to disk functionality in favour of the 173 version.

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

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

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

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

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

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.

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

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

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

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

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

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

Install Ubuntu Intrepid Ibex on a T61p

2008-10-29T22:12:43Z

Gertvdijk: /* Not able to restart X */

=What works and what doesn't?=
==Working out-of-the-box==
*Wireless (Intel 3945ABG or 4965AGN)
**Only tested G mode
*Wired LAN
*Video (VESA)
**Hardware Drivers panel offers to install nVIDIA proprietary drivers on first boot.
*Touchpoint and Trackpad
**Including scroll at the right side of the pad by default.
*Optical drive
**Optiarc AD-7910A works fine with Brasero disc burning
***Tested: CD-R, DVD+R
*Sound card
*SD/MMC Memory card reader (Ricoh)
**Only tested SD (non-HC) cards. 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
*ACPI features
** Suspend to RAM
** Suspend to Disk (Hibernate) FINALLY!! Be patient, though.
** STR and STD work even with full disk encryption (DM-crypt + LVM)!

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

==Small issues with...==
* The radio killswitch.

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

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

To enable 3D acceleration, the proprietary NVidia driver must be installed. The first time you boot into Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at System --> Administration --> Hardware Drivers. You will have a choice between the 173 and 177 version of the driver. I would strongly recommend the latter one, because it will provide Suspend to disk functionality in favour of the 173 version.

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

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

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

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

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

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.

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

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

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

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

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

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

Install Ubuntu Intrepid Ibex on a T61p

2008-10-29T22:08:44Z

Gertvdijk: /* Wireless not working after resume */

=What works and what doesn't?=
==Working out-of-the-box==
*Wireless (Intel 3945ABG or 4965AGN)
**Only tested G mode
*Wired LAN
*Video (VESA)
**Hardware Drivers panel offers to install nVIDIA proprietary drivers on first boot.
*Touchpoint and Trackpad
**Including scroll at the right side of the pad by default.
*Optical drive
**Optiarc AD-7910A works fine with Brasero disc burning
***Tested: CD-R, DVD+R
*Sound card
*SD/MMC Memory card reader (Ricoh)
**Only tested SD (non-HC) cards. 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
*ACPI features
** Suspend to RAM
** Suspend to Disk (Hibernate) FINALLY!! Be patient, though.
** STR and STD work even with full disk encryption (DM-crypt + LVM)!

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

==Small issues with...==
* The radio killswitch.

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

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

To enable 3D acceleration, the proprietary NVidia driver must be installed. The first time you boot into Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at System --> Administration --> Hardware Drivers. You will have a choice between the 173 and 177 version of the driver. I would strongly recommend the latter one, because it will provide Suspend to disk functionality in favour of the 173 version.

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

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

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

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

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

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.

=Problems=
== Not able to restart X ==
This is quite an issue when you want to switch user or log out. I'm not able to trace down the problem, because the Xorg.0.log file doesn't give any errors or hints. Surprisingly both Suspend to RAM and Suspend to Disk are not failing.--[[User:Gertvdijk|Gertvdijk]] 18:34, 23 October 2008 (CEST)
== 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.

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

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

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

Install Ubuntu Intrepid Ibex on a T61p

2008-10-29T22:07:49Z

Gertvdijk: /* Small issues with... */

=What works and what doesn't?=
==Working out-of-the-box==
*Wireless (Intel 3945ABG or 4965AGN)
**Only tested G mode
*Wired LAN
*Video (VESA)
**Hardware Drivers panel offers to install nVIDIA proprietary drivers on first boot.
*Touchpoint and Trackpad
**Including scroll at the right side of the pad by default.
*Optical drive
**Optiarc AD-7910A works fine with Brasero disc burning
***Tested: CD-R, DVD+R
*Sound card
*SD/MMC Memory card reader (Ricoh)
**Only tested SD (non-HC) cards. 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
*ACPI features
** Suspend to RAM
** Suspend to Disk (Hibernate) FINALLY!! Be patient, though.
** STR and STD work even with full disk encryption (DM-crypt + LVM)!

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

==Small issues with...==
* The radio killswitch.

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

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

To enable 3D acceleration, the proprietary NVidia driver must be installed. The first time you boot into Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at System --> Administration --> Hardware Drivers. You will have a choice between the 173 and 177 version of the driver. I would strongly recommend the latter one, because it will provide Suspend to disk functionality in favour of the 173 version.

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

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

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

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

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

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.

=Problems=
== Not able to restart X ==
This is quite an issue when you want to switch user or log out. I'm not able to trace down the problem, because the Xorg.0.log file doesn't give any errors or hints. Surprisingly both Suspend to RAM and Suspend to Disk are not failing.--[[User:Gertvdijk|Gertvdijk]] 18:34, 23 October 2008 (CEST)
== Wireless not working after resume ==
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.
== Radio Killswitch ==
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].

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

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

Install Ubuntu Intrepid Ibex on a T61p

2008-10-29T22:06:58Z

Gertvdijk: /* Radio Killswitch */

=What works and what doesn't?=
==Working out-of-the-box==
*Wireless (Intel 3945ABG or 4965AGN)
**Only tested G mode
*Wired LAN
*Video (VESA)
**Hardware Drivers panel offers to install nVIDIA proprietary drivers on first boot.
*Touchpoint and Trackpad
**Including scroll at the right side of the pad by default.
*Optical drive
**Optiarc AD-7910A works fine with Brasero disc burning
***Tested: CD-R, DVD+R
*Sound card
*SD/MMC Memory card reader (Ricoh)
**Only tested SD (non-HC) cards. 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
*ACPI features
** Suspend to RAM
** Suspend to Disk (Hibernate) FINALLY!! Be patient, though.
** STR and STD work even with full disk encryption (DM-crypt + LVM)!

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

==Small issues with...==
* The radio killswitch.
** Bluetooth and WLAN are turned off properly when using the killswitch at the front, but WLAN (3945) doensn't come up when enabling or will only show Channel 1 APs. Reloading the iwl3945 module will sometimes solve the issue.
** The soft-killswitch (Fn+F5) will only toggle Bluetooth instead of the four modes as in Hardy (BT+WLAN, BT, WLAN, ALL OFF).

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

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

To enable 3D acceleration, the proprietary NVidia driver must be installed. The first time you boot into Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at System --> Administration --> Hardware Drivers. You will have a choice between the 173 and 177 version of the driver. I would strongly recommend the latter one, because it will provide Suspend to disk functionality in favour of the 173 version.

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

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

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

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

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

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.

=Problems=
== Not able to restart X ==
This is quite an issue when you want to switch user or log out. I'm not able to trace down the problem, because the Xorg.0.log file doesn't give any errors or hints. Surprisingly both Suspend to RAM and Suspend to Disk are not failing.--[[User:Gertvdijk|Gertvdijk]] 18:34, 23 October 2008 (CEST)
== Wireless not working after resume ==
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.
== Radio Killswitch ==
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].

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

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

Install Ubuntu Intrepid Ibex on a T61p

2008-10-23T16:37:44Z

Gertvdijk: /* Working out-of-the-box */

Install Ubuntu Intrepid Ibex on a T61p

2008-10-23T16:34:54Z

Gertvdijk: â†Created page with '=What works and what doesn't?= ==Working out-of-the-box== *Wireless (Intel 3945ABG or 4965AGN) **Only tested G mode *Wired LAN *Video (VESA) **Hardware Drivers panel offer...'

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61p

2008-10-23T16:21:26Z

Gertvdijk:

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

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

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61p

2008-10-09T13:20:54Z

Gertvdijk: /* Suspend */

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

2008-10-01T23:33:23Z

Gertvdijk:

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

== Re: Nvidia Binary Drivers ==

You'll need them for the quirks to get Suspend To Ram to work. See my edit on the Wiki page. --[[User:Gertvdijk|Gertvdijk]] 12:32, 7 August 2008 (CEST)

== T61p category page ==

Why isn't this article in the T61p category page? [[Category:T61p]] --[[User:Gertvdijk|Gertvdijk]] 12:32, 7 August 2008 (CEST)

== Updated and cleaned ==

I've cleaned it all up a bit and gave it more structure by adding some headings and splitting long blobs of text and giving it some headings.--[[User:Gertvdijk|Gertvdijk]] 01:33, 2 October 2008 (CEST)

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61p

2008-10-01T23:24:12Z

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

==What works out of the box?==
*Wireless (Intel 3945ABG or 4965AGN)
**Only tested G mode
*Wired LAN
*Video (VESA)
**Hardware Drivers panel offers to install nVIDIA proprietary drivers on first boot.
*Touchpoint and Trackpad
**Including scroll at the right side of the pad by default.
*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.

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

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

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61p

2008-10-01T23:23:34Z

Gertvdijk: /* What needs some tweaks? */

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

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

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

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61p

2008-10-01T23:21:25Z

Gertvdijk: /* 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.
*Optical drive
**Optiarc AD-7910A works fine with Brasero disc burning
***Tried: 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
{{Todo|HDAPS (harddrive protection system)}}
*Smooth Compiz performance

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

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

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

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61p

2008-10-01T23:17:31Z

Gertvdijk: /* Suspend */

==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
***Tried: 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
{{Todo|HDAPS (harddrive protection system)}}
*Smooth Compiz performance

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

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

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

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61p

2008-10-01T23:12:59Z

Gertvdijk: /* What needs some tweaks? */

==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
***Tried: 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
{{Todo|HDAPS (harddrive protection system)}}
*Smooth Compiz performance

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

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

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

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

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

Find the following section:
...

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


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


...

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

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

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

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

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

Replace enable with disable to turn it off.

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

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

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

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

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

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61p

2008-10-01T23:12:10Z

Gertvdijk: /* 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.
*Optical drive
**Optiarc AD-7910A works fine with Brasero disc burning
***Tried: 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
{{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.

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

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

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

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

Find the following section:
...

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


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


...

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

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

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

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

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

Replace enable with disable to turn it off.

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

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

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

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

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

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61p

2008-10-01T23:02:55Z

Gertvdijk: /* 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.
*Optical drive
**Optiarc AD-7910A works fine with Brasero disc burning
***Tried: 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
{{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.

==== Compiz and daily life use ====

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.

One final bug is that EDID (Extended Display Identification Data) might be misdetected, which causes problems with font sizes and greatly reduces the number of resolutions available in the NVidia X Server Settings application. (For example, I was unable to set my laptop's screen to 1024x768 for use with a projector during a presentation.) 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.

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

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

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

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

Find the following section:
...

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


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


...

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

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

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

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

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

Replace enable with disable to turn it off.

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

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

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

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

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

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61p

2008-10-01T22:40:22Z

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

==What works out of the box?==
*Wireless (Intel 3945ABG or 4965AGN)
**Only tested G mode
*Wired LAN
*Video (VESA)
**Hardware Drivers panel offers to install nVIDIA proprietary drivers on first boot.
*Touchpoint and Trackpad
**Including scroll at the right side of the pad by default.
*Optical drive
**Optiarc AD-7910A works fine with Brasero disc burning
***Tried: 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
{{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.

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

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

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

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

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

Another problem is that the driver does not report the correct refresh rate to Compiz, resulting in rough animation. To fix this, install the compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. Click on General Options, go to the Display Settings tab, uncheck the Detect Refresh rate box and drag the Refresh Rate slider to 60. Also, check the Sync To VBlank box.

Next, Compiz animations are also choppy due to NVidia's PowerMizer feature, which slows down the GPU to conserve power when it is not in use. This works well for 3D games which constantly use 3D acceleration, but poorly for Compiz which uses the GPU in small bursts. To solve this problem, I made a couple of shell scripts which keep the GPU at its highest speed while running on AC power. The first one is named "powermizer-loop" and does most of the work:

#!/bin/sh

while true; do

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

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

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

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

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

chmod 755 powermizer-loop powermizer-off

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

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

One final bug is that EDID (Extended Display Identification Data) is misdetected, which causes problems with font sizes and greatly reduces the number of resolutions available in the NVidia X Server Settings application. (For example, I was unable to set my laptop's screen to 1024x768 for use with a projector during a presentation.) To correct this problem, I added the following lines to /etc/X11/xorg.conf in the "Screen" section:

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

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

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

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

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

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

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

Find the following section:
...

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


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


...

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

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

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

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

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

Replace enable with disable to turn it off.

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

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

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

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

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

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61p

2008-10-01T22:39:00Z

Gertvdijk: /* What doesn't work at the moment? */

==What works out of the box?==
*Wireless (Intel 3945ABG or 4965AGN)
**Only tested G mode
**LED not working yet. Known issue in kernel driver.
*Wired LAN
*Video (VESA)
**Hardware Drivers panel offers to install NVidia proprietary drivers on first boot
*Touchpoint and Trackpad
**Including scroll at the right side of the pad
*Optical drive
**Optiarc AD-7910A
*Sound card
**No Microphone
*Memory card reader
**Only tested SD (non-HC) cards. Didn't take locked (read-only) cards.
*Control buttons/Hotkeys
**Volume control buttons
**Screen brightness control
**Thinklight control
**WLAN/BT/OFF toggle
**Media player control
*Some ACPI features
**Battery status, power graphs and history
**Lid states and events
**LCD brightness adjustment on power source
**Only tested with a single 6-cell battery

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

==What doesn't work at the moment?==
*Suspend-to-Disk (Hibernate)
*Wireless LAN 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.

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

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

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

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

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

Another problem is that the driver does not report the correct refresh rate to Compiz, resulting in rough animation. To fix this, install the compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. Click on General Options, go to the Display Settings tab, uncheck the Detect Refresh rate box and drag the Refresh Rate slider to 60. Also, check the Sync To VBlank box.

Next, Compiz animations are also choppy due to NVidia's PowerMizer feature, which slows down the GPU to conserve power when it is not in use. This works well for 3D games which constantly use 3D acceleration, but poorly for Compiz which uses the GPU in small bursts. To solve this problem, I made a couple of shell scripts which keep the GPU at its highest speed while running on AC power. The first one is named "powermizer-loop" and does most of the work:

#!/bin/sh

while true; do

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

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

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

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

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

chmod 755 powermizer-loop powermizer-off

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

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

One final bug is that EDID (Extended Display Identification Data) is misdetected, which causes problems with font sizes and greatly reduces the number of resolutions available in the NVidia X Server Settings application. (For example, I was unable to set my laptop's screen to 1024x768 for use with a projector during a presentation.) To correct this problem, I added the following lines to /etc/X11/xorg.conf in the "Screen" section:

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

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

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

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

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

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

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

Find the following section:
...

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


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


...

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

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

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

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

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

Replace enable with disable to turn it off.

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

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

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

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

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

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61p

2008-08-26T19:30:53Z

Gertvdijk: /* What needs some tweaks? */

==What works out of the box?==
*Wireless (Intel 3945ABG or 4965AGN)
**Only tested G mode
**LED not working yet. Known issue in kernel driver.
*Wired LAN
*Video (VESA)
**Hardware Drivers panel offers to install NVidia proprietary drivers on first boot
*Touchpoint and Trackpad
**Including scroll at the right side of the pad
*Optical drive
**Optiarc AD-7910A
*Sound card
**Microphone not yet tested
*Memory card reader
**Only tested SD (non-HC) cards. Didn't take locked (read-only) cards.
*Control buttons/Hotkeys
**Volume control buttons
**Screen brightness control
**Thinklight control
**WLAN/BT/OFF toggle
**Media player control
*Some ACPI features
**Battery status, power graphs and history
**Lid states and events
**LCD brightness adjustment on power source
**Only tested with a single 6-cell battery

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

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

== Display / Video ==

To enable 3D acceleration, the proprietary NVidia driver must be installed. The first time you boot into Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at System --> Administration --> Hardware Drivers.

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

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

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

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

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

Another problem is that the driver does not report the correct refresh rate to Compiz, resulting in rough animation. To fix this, install the compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. Click on General Options, go to the Display Settings tab, uncheck the Detect Refresh rate box and drag the Refresh Rate slider to 60. Also, check the Sync To VBlank box.

Next, Compiz animations are also choppy due to NVidia's PowerMizer feature, which slows down the GPU to conserve power when it is not in use. This works well for 3D games which constantly use 3D acceleration, but poorly for Compiz which uses the GPU in small bursts. To solve this problem, I made a couple of shell scripts which keep the GPU at its highest speed while running on AC power. The first one is named "powermizer-loop" and does most of the work:

#!/bin/sh

while true; do

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

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

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

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

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

chmod 755 powermizer-loop powermizer-off

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

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

One final bug is that EDID (Extended Display Identification Data) is misdetected, which causes problems with font sizes and greatly reduces the number of resolutions available in the NVidia X Server Settings application. (For example, I was unable to set my laptop's screen to 1024x768 for use with a projector during a presentation.) To correct this problem, I added the following lines to /etc/X11/xorg.conf in the "Screen" section:

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

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

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

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

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

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

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

Find the following section:
...

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


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


...

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

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

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

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

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

Replace enable with disable to turn it off.

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

[[Category:T61p]]

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61p

2008-08-26T19:29:56Z

Gertvdijk:

==What works out of the box?==
*Wireless (Intel 3945ABG or 4965AGN)
**Only tested G mode
**LED not working yet. Known issue in kernel driver.
*Wired LAN
*Video (VESA)
**Hardware Drivers panel offers to install NVidia proprietary drivers on first boot
*Touchpoint and Trackpad
**Including scroll at the right side of the pad
*Optical drive
**Optiarc AD-7910A
*Sound card
**Microphone not yet tested
*Memory card reader
**Only tested SD (non-HC) cards. Didn't take locked (read-only) cards.
*Control buttons/Hotkeys
**Volume control buttons
**Screen brightness control
**Thinklight control
**WLAN/BT/OFF toggle
**Media player control
*Some ACPI features
**Battery status, power graphs and history
**Lid states and events
**LCD brightness adjustment on power source
**Only tested with a single 6-cell battery

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

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

== Display / Video ==

To enable 3D acceleration, the proprietary NVidia driver must be installed. The first time you boot into Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at System --> Administration --> Hardware Drivers.

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

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

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

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

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

Another problem is that the driver does not report the correct refresh rate to Compiz, resulting in rough animation. To fix this, install the compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. Click on General Options, go to the Display Settings tab, uncheck the Detect Refresh rate box and drag the Refresh Rate slider to 60. Also, check the Sync To VBlank box.

Next, Compiz animations are also choppy due to NVidia's PowerMizer feature, which slows down the GPU to conserve power when it is not in use. This works well for 3D games which constantly use 3D acceleration, but poorly for Compiz which uses the GPU in small bursts. To solve this problem, I made a couple of shell scripts which keep the GPU at its highest speed while running on AC power. The first one is named "powermizer-loop" and does most of the work:

#!/bin/sh

while true; do

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

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

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

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

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

chmod 755 powermizer-loop powermizer-off

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

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

One final bug is that EDID (Extended Display Identification Data) is misdetected, which causes problems with font sizes and greatly reduces the number of resolutions available in the NVidia X Server Settings application. (For example, I was unable to set my laptop's screen to 1024x768 for use with a projector during a presentation.) To correct this problem, I added the following lines to /etc/X11/xorg.conf in the "Screen" section:

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

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

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

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

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

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

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

Find the following section:
...

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


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


...

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

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

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

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

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

Replace enable with disable to turn it off.

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

[[Category:T61p]]

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61p

2008-08-26T19:27:18Z

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

==What works out of the box?==
*Wireless (Intel 3945ABG or 4965AGN)
**Only tested G mode
**LED not working yet. Known issue in kernel driver.
*Wired LAN
*Video (VESA)
**Hardware Drivers panel offers to install NVidia proprietary drivers on first boot
*Touchpoint and Trackpad
**Including scroll at the right side of the pad
*Optical drive
**Optiarc AD-7910A
*Sound card
**Microphone not yet tested
*Memory card reader
**Only tested SD (non-HC) cards. Didn't take locked (read-only) cards.
*Control buttons/Hotkeys
**Volume control buttons
**Screen brightness control
**Thinklight control
**WLAN/BT/OFF toggle
**Media player control
*Some ACPI features
**Battery status, power graphs and history
**Lid states and events
**LCD brightness adjustment on power source
**Only tested with a single 6-cell battery

==What needs some tweaks?==
*Suspend-to-RAM (Standby, Suspend)
*HDAPS (harddrive protection system)
**TODO

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

== Display / Video ==

To enable 3D acceleration, the proprietary NVidia driver must be installed. The first time you boot into Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at System --> Administration --> Hardware Drivers.

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

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

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

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

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

Another problem is that the driver does not report the correct refresh rate to Compiz, resulting in rough animation. To fix this, install the compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. Click on General Options, go to the Display Settings tab, uncheck the Detect Refresh rate box and drag the Refresh Rate slider to 60. Also, check the Sync To VBlank box.

Next, Compiz animations are also choppy due to NVidia's PowerMizer feature, which slows down the GPU to conserve power when it is not in use. This works well for 3D games which constantly use 3D acceleration, but poorly for Compiz which uses the GPU in small bursts. To solve this problem, I made a couple of shell scripts which keep the GPU at its highest speed while running on AC power. The first one is named "powermizer-loop" and does most of the work:

#!/bin/sh

while true; do

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

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

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

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

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

chmod 755 powermizer-loop powermizer-off

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

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

One final bug is that EDID (Extended Display Identification Data) is misdetected, which causes problems with font sizes and greatly reduces the number of resolutions available in the NVidia X Server Settings application. (For example, I was unable to set my laptop's screen to 1024x768 for use with a projector during a presentation.) To correct this problem, I added the following lines to /etc/X11/xorg.conf in the "Screen" section:

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

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

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

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

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

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

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

Find the following section:
...

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


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


...

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

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

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

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

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

Replace enable with disable to turn it off.

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

Install Ubuntu Gutsy Gibbon on a T61p

2008-08-26T19:24:57Z

Gertvdijk: /* Introduction */

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

== Introduction ==

This document outlines configuring Ubuntu 7.10 (Gutsy Gibbon) on your Thinkpad T61p. Most items will work out of the box and a base install will provide you with an almost completely working system. Due to the modular nature of the T61 there are many different configuration, please read carefully and only make the changes specific to your system.
In the successor of Ubuntu Gutsy Gibbon, Hardy Heron, more things are working out of the box. See the [[Install Ubuntu Hardy Heron on a T61p | how-to]] for Hardy Heron if you're looking for instructions installing Hardy Heron (recommended).

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

== Installation Notes ==

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

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

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

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

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

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

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

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

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

== Display/Video ==

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

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

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

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

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

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

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

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

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

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

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

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

*fix volume control applet:

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

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

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

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

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

== Network/Internet ==

If you have some kind of recent T61p (mid-2008), the Intel WifiLink 4965 wifi controler might not work out of the box. The easiest way to have it working is to use Intel's drivers for windows (http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&Inst=Yes&ProductID=2753&DwnldID=16617&strOSs=44&OSFullName=Windows*%20XP%20Professional&lang=eng) and use ndiswrapper on them :
*unzip the driver zip file somewhere (let's say you use $home)
*go to the driver directory $home/Disk/XP/Drivers/x32/
*run the command: ndiswrapper-1.9 NETw5x32.inf (you should check the driver version as it can become NETw6x32.inf after next release)
*remember to switch on wifi from both frontal switch (physical switch, under your left wrist) and then with Fn-F5 as well. The bluetooth led should be lightened.

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

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

[[Image:Update_to_Aliases.png]]

Now, save the file and restart Ubuntu.

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

== Suspend with Nvidia Binary Driver ==

*Fix suspend with Nvidia binary drivers:

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

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

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

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

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

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

Paste the following script:

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

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

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

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

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

==Fingerprint Reader==

The [http://thinkfinger.sourceforge.net/ Thinkfinger] package allows you to swipe a finger in most places where you would have to type your password. At least for me, the most recent (0.3) version used here works with sudo, gksudo and on the login page but not with the the screen saver. Also, you are still required to type your user name on the login screen.

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

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

2) Install the following packages:

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

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

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

A completed test should look something like this:

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

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

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

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

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

4) Enable use of reader for authentication:

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

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

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

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

6) Check uinput kernel module:

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

Start uinput:
{{cmduser|sudo modprobe uinput}}

Start on boot:
{{cmduser|sudo gedit /etc/modules}}
add the line:
uinput

At this point, you should be ready to swipe!

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

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

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

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

to set the speed to max or

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

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

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

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

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

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

[[Category:T61p]]

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

2008-08-07T10:32:42Z

Gertvdijk: /* Re: Nvidia Binary Drivers */

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

2008-08-07T10:32:30Z

Gertvdijk: New section: T61p category page

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

2008-08-07T10:29:39Z

Gertvdijk: New section: Re: Nvidia Binary Drivers

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61p

2008-08-02T00:41:05Z

Gertvdijk: /* What needs some tweaks? */

==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
*Optical drive
**Optiarc AD-7910A
*Sound card
**Microphone not yet tested
*Memory card reader
**Only tested SD (non-HC) cards. Didn't take locked (read-only) cards.
*Control buttons/Hotkeys
**Volume control buttons
**Screen brightness control
**Thinklight control
**WLAN/BT/OFF toggle
**Media player control
*Some ACPI features
**Battery status, power graphs and history
**Lid states and events
**LCD brightness adjustment on power source
**Only tested with a single 6-cell battery

==What needs some tweaks?==
*Suspend-to-RAM (Standby, Suspend)
*HDAPS (harddrive protection system)
**TODO

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

== Display / Video ==

To enable 3D acceleration, the proprietary NVidia driver must be installed. The first time you boot into Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at System --> Administration --> Hardware Drivers.

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

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

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

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

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

Another problem is that the driver does not report the correct refresh rate to Compiz, resulting in rough animation. To fix this, install the compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. Click on General Options, go to the Display Settings tab, uncheck the Detect Refresh rate box and drag the Refresh Rate slider to 60. Also, check the Sync To VBlank box.

Next, Compiz animations are also choppy due to NVidia's PowerMizer feature, which slows down the GPU to conserve power when it is not in use. This works well for 3D games which constantly use 3D acceleration, but poorly for Compiz which uses the GPU in small bursts. To solve this problem, I made a couple of shell scripts which keep the GPU at its highest speed while running on AC power. The first one is named "powermizer-loop" and does most of the work:

#!/bin/sh

while true; do

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

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

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

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

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

chmod 755 powermizer-loop powermizer-off

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

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

One final bug is that EDID (Extended Display Identification Data) is misdetected, which causes problems with font sizes and greatly reduces the number of resolutions available in the NVidia X Server Settings application. (For example, I was unable to set my laptop's screen to 1024x768 for use with a projector during a presentation.) To correct this problem, I added the following lines to /etc/X11/xorg.conf in the "Screen" section:

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

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

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

== Suspend ==
Suspend is supposed to work out of the box if you're not using the Nvidia binary drivers. If you are using them, the following instructions will fix suspend to ram. Suspend to disk (hibernate) is not working at this time.

{{NOTE|These instructions worked on the T61p with type numbers 6460, 6457 (and perhaps 6465). It may also work with other type numbers.}}

To get suspend to ram working, you need to edit a configuration file, which apparently has some bad information in it.

{{cmduser |gksudo gedit /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi}}

Find the following section:
...

<match key="system.hardware.product" prefix_outof="6457;6460;6465">
<merge key="power_management.quirk.s3_bios" type="bool">true</merge>
<merge key="power_management.quirk.vbemode_restore" type="bool">true</merge>
</match>


<match key="system.hardware.product" prefix_outof="6459;7664;8918">
<merge key="power_management.quirk.none" type="bool">true</merge>
</match>


...

Remove the <code>6457;6460;</code> from the <code><match key="system.hardware.product" prefix_outof="6457;6460;6465"></code> line and add the following lines right before the <code></code> line:
<match key="system.hardware.product" prefix_outof="6457;6460">
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.vbemode_restore" type="bool">true</merge>
</match>

Based on [https://bugs.launchpad.net/ubuntu/+source/hal-info/+bug/235284 Bug #235284 in hal-info (Ubuntu)]

On (at least) the 6457 model you'll need the latest binary Nvidia graphics drivers (173.14.09 at time of writing for Envy) to be able to resume from suspend. Additionally I have to switch to the X terminal manually by pressing alt+F7.
The sleep LED will blink for a while after resume, but will stop eventually and the wireless devices will be switched back on. You may experience some resetting of the display when that happens. Just move the cursor to regain your desktop. N.B. This does not seem to occur when waking after a long time of sleep.

== Bluetooth ==
If installed, bluetooth must be enabled with the command:

{{cmduser | echo enable | sudo tee /proc/acpi/ibm/bluetooth}}

Replace enable with disable to turn it off.

You can now connect devices by following the instructions at [https://help.ubuntu.com/community/BluetoothSetup Ubuntu Help Bluetooth Setup page]
{{NOTE|On (at least) the 6457 model the Bluetooth and Wireless LAN toggle button (Fn+F5) seems to work fine. Be aware of the additional hardware switch at the front of the machine. This needs to be in the green setting.}}

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61p

2008-08-02T00:39:51Z

Gertvdijk: /* Suspend */

==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
*Optical drive
**Optiarc AD-7910A
*Sound card
**Microphone not yet tested
*Memory card reader
**Only tested SD (non-HC) cards. Didn't take locked (read-only) cards.
*Control buttons/Hotkeys
**Volume control buttons
**Screen brightness control
**Thinklight control
**WLAN/BT/OFF toggle
**Media player control
*Some ACPI features
**Battery status, power graphs and history
**Lid states and events
**LCD brightness adjustment on power source
**Only tested with a single 6-cell battery

==What needs some tweaks?==
*Suspend-to-RAM (Standby, Suspend)

==What doesn't work at the moment?==
*Suspend-to-Disk (Hibernate)
*Wireless LAN power/activity LED

== Display / Video ==

To enable 3D acceleration, the proprietary NVidia driver must be installed. The first time you boot into Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at System --> Administration --> Hardware Drivers.

If you want more options for configuring your video card than is provided by the Ubuntu control panels, you can install the NVidia Control Panel with

{{cmduser| sudo apt-get install nvidia-settings}}

which will add the NVidia X Server Settings panel to the Administration menu.

Alternately, the NVidia driver and Control Panel can be installed using EnvyNG (envyng-gtk in Synaptic). Simply start it up (System Tools --> EnvyNG) and ask it to install the NVidia driver.

Unfortunately, there are some annoying bugs in the NVidia driver. The most annoying one is that after resuming from suspend, you will often get a blank white screen. To get past it, simply type in your password and press enter, and you will be returned to your desktop. Fortunately, Ubuntu has released a workaround for this bug, so it should go away once you update all your packages to the latest versions.

Another problem is that the driver does not report the correct refresh rate to Compiz, resulting in rough animation. To fix this, install the compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. Click on General Options, go to the Display Settings tab, uncheck the Detect Refresh rate box and drag the Refresh Rate slider to 60. Also, check the Sync To VBlank box.

Next, Compiz animations are also choppy due to NVidia's PowerMizer feature, which slows down the GPU to conserve power when it is not in use. This works well for 3D games which constantly use 3D acceleration, but poorly for Compiz which uses the GPU in small bursts. To solve this problem, I made a couple of shell scripts which keep the GPU at its highest speed while running on AC power. The first one is named "powermizer-loop" and does most of the work:

#!/bin/sh

while true; do

powerstate=`cat /proc/acpi/ac_adapter/AC/state | awk '{print $2}'`

if [ $powerstate = "on-line" ]; then
nvidia-settings -q all > /dev/null
fi
sleep 25;
done

The second is named "powermizer-off" and starts up powermizer-loop when I log in, ensuring that only one copy runs at a time:

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

I put both of these scripts in my home directory and made them executable by doing:

chmod 755 powermizer-loop powermizer-off

Then to make powermizer-off run on login, I opened System --> Preferences --> Sessions, clicked on Add, and entered the command "/home/argilo/powermizer-off".

Of course, performance still suffers when running on battery, but hopefully NVidia will fix this problem in a future version of their driver.

One final bug is that EDID (Extended Display Identification Data) is misdetected, which causes problems with font sizes and greatly reduces the number of resolutions available in the NVidia X Server Settings application. (For example, I was unable to set my laptop's screen to 1024x768 for use with a projector during a presentation.) To correct this problem, I added the following lines to /etc/X11/xorg.conf in the "Screen" section:

Option "UseEdidDpi" "FALSE"
Option "DPI" "96 x 96"
Option "UseEdidFreqs" "FALSE"
Option "HorizSync" "40-70"

The first two lines fix the font size issue, and the last two lines fix the resolution problem. I'm not sure if the 40-70 values are actually correct, since I just took them from someone else's xorg.conf, but they seem to work.

NVidia seems to have corrected the EDID misdetection bug in the latest version of their driver, but it's not available in Hardy and I'm not aware of any easy way to install it.

== Suspend ==
Suspend is supposed to work out of the box if you're not using the Nvidia binary drivers. If you are using them, the following instructions will fix suspend to ram. Suspend to disk (hibernate) is not working at this time.

{{NOTE|These instructions worked on the T61p with type numbers 6460, 6457 (and perhaps 6465). It may also work with other type numbers.}}

To get suspend to ram working, you need to edit a configuration file, which apparently has some bad information in it.

{{cmduser |gksudo gedit /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi}}

Find the following section:
...

<match key="system.hardware.product" prefix_outof="6457;6460;6465">
<merge key="power_management.quirk.s3_bios" type="bool">true</merge>
<merge key="power_management.quirk.vbemode_restore" type="bool">true</merge>
</match>


<match key="system.hardware.product" prefix_outof="6459;7664;8918">
<merge key="power_management.quirk.none" type="bool">true</merge>
</match>


...

Remove the <code>6457;6460;</code> from the <code><match key="system.hardware.product" prefix_outof="6457;6460;6465"></code> line and add the following lines right before the <code></code> line:
<match key="system.hardware.product" prefix_outof="6457;6460">
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.vbemode_restore" type="bool">true</merge>
</match>

Based on [https://bugs.launchpad.net/ubuntu/+source/hal-info/+bug/235284 Bug #235284 in hal-info (Ubuntu)]

On (at least) the 6457 model you'll need the latest binary Nvidia graphics drivers (173.14.09 at time of writing for Envy) to be able to resume from suspend. Additionally I have to switch to the X terminal manually by pressing alt+F7.
The sleep LED will blink for a while after resume, but will stop eventually and the wireless devices will be switched back on. You may experience some resetting of the display when that happens. Just move the cursor to regain your desktop. N.B. This does not seem to occur when waking after a long time of sleep.

== Bluetooth ==
If installed, bluetooth must be enabled with the command:

{{cmduser | echo enable | sudo tee /proc/acpi/ibm/bluetooth}}

Replace enable with disable to turn it off.

You can now connect devices by following the instructions at [https://help.ubuntu.com/community/BluetoothSetup Ubuntu Help Bluetooth Setup page]
{{NOTE|On (at least) the 6457 model the Bluetooth and Wireless LAN toggle button (Fn+F5) seems to work fine. Be aware of the additional hardware switch at the front of the machine. This needs to be in the green setting.}}

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61p

2008-07-31T00:17:54Z

Gertvdijk: /* Suspend */

==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
*Optical drive
**Optiarc AD-7910A
*Sound card
**Microphone not yet tested
*Memory card reader
**Only tested SD (non-HC) cards. Didn't take locked (read-only) cards.
*Control buttons/Hotkeys
**Volume control buttons
**Screen brightness control
**Thinklight control
**WLAN/BT/OFF toggle
**Media player control
*Some ACPI features
**Battery status, power graphs and history
**Lid states and events
**LCD brightness adjustment on power source
**Only tested with a single 6-cell battery

==What needs some tweaks?==
*Suspend-to-RAM (Standby, Suspend)

==What doesn't work at the moment?==
*Suspend-to-Disk (Hibernate)
*Wireless LAN power/activity LED

== Display / Video ==

To enable 3D acceleration, the proprietary NVidia driver must be installed. The first time you boot into Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at System --> Administration --> Hardware Drivers.

If you want more options for configuring your video card than is provided by the Ubuntu control panels, you can install the NVidia Control Panel with

{{cmduser| sudo apt-get install nvidia-settings}}

which will add the NVidia X Server Settings panel to the Administration menu.

Alternately, the NVidia driver and Control Panel can be installed using EnvyNG (envyng-gtk in Synaptic). Simply start it up (System Tools --> EnvyNG) and ask it to install the NVidia driver.

Unfortunately, there are some annoying bugs in the NVidia driver. The most annoying one is that after resuming from suspend, you will often get a blank white screen. To get past it, simply type in your password and press enter, and you will be returned to your desktop. Fortunately, Ubuntu has released a workaround for this bug, so it should go away once you update all your packages to the latest versions.

Another problem is that the driver does not report the correct refresh rate to Compiz, resulting in rough animation. To fix this, install the compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. Click on General Options, go to the Display Settings tab, uncheck the Detect Refresh rate box and drag the Refresh Rate slider to 60. Also, check the Sync To VBlank box.

Next, Compiz animations are also choppy due to NVidia's PowerMizer feature, which slows down the GPU to conserve power when it is not in use. This works well for 3D games which constantly use 3D acceleration, but poorly for Compiz which uses the GPU in small bursts. To solve this problem, I made a couple of shell scripts which keep the GPU at its highest speed while running on AC power. The first one is named "powermizer-loop" and does most of the work:

#!/bin/sh

while true; do

powerstate=`cat /proc/acpi/ac_adapter/AC/state | awk '{print $2}'`

if [ $powerstate = "on-line" ]; then
nvidia-settings -q all > /dev/null
fi
sleep 25;
done

The second is named "powermizer-off" and starts up powermizer-loop when I log in, ensuring that only one copy runs at a time:

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

I put both of these scripts in my home directory and made them executable by doing:

chmod 755 powermizer-loop powermizer-off

Then to make powermizer-off run on login, I opened System --> Preferences --> Sessions, clicked on Add, and entered the command "/home/argilo/powermizer-off".

Of course, performance still suffers when running on battery, but hopefully NVidia will fix this problem in a future version of their driver.

One final bug is that EDID (Extended Display Identification Data) is misdetected, which causes problems with font sizes and greatly reduces the number of resolutions available in the NVidia X Server Settings application. (For example, I was unable to set my laptop's screen to 1024x768 for use with a projector during a presentation.) To correct this problem, I added the following lines to /etc/X11/xorg.conf in the "Screen" section:

Option "UseEdidDpi" "FALSE"
Option "DPI" "96 x 96"
Option "UseEdidFreqs" "FALSE"
Option "HorizSync" "40-70"

The first two lines fix the font size issue, and the last two lines fix the resolution problem. I'm not sure if the 40-70 values are actually correct, since I just took them from someone else's xorg.conf, but they seem to work.

NVidia seems to have corrected the EDID misdetection bug in the latest version of their driver, but it's not available in Hardy and I'm not aware of any easy way to install it.

== Suspend ==
Suspend is supposed to work out of the box if you're not using the Nvidia binary drivers. If you are using them, the following instructions will fix suspend to ram. Suspend to disk (hibernate) is not working at this time.

{{NOTE|These instructions worked on the T61p with type numbers 6460, 6457 (and perhaps 6465). It may also work with other type numbers.}}

To get suspend to ram working, you need to edit a configuration file, which apparently has some bad information in it.

{{cmduser |gksudo gedit /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi}}

Find the following section:
...

<match key="system.hardware.product" prefix_outof="6457;6460;6465">
<merge key="power_management.quirk.s3_bios" type="bool">true</merge>
<merge key="power_management.quirk.vbemode_restore" type="bool">true</merge>
</match>


<match key="system.hardware.product" prefix_outof="6459;7664;8918">
<merge key="power_management.quirk.none" type="bool">true</merge>
</match>


...

Remove the <code>6457;6460;</code> from the <code><match key="system.hardware.product" prefix_outof="6457;6460;6465"></code> line and add the following lines right before the <code></code> line:
<match key="system.hardware.product" prefix_outof="6457;6460">
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.vbemode_restore" type="bool">true</merge>
</match>

Based on [https://bugs.launchpad.net/ubuntu/+source/hal-info/+bug/235284 Bug #235284 in hal-info (Ubuntu)]

On (at least) the 6457 model you'll need the latest binary Nvidia graphics drivers (173.14.09 at time of writing for Envy) to be able to resume from suspend. Additionally I have to switch to the X terminal manually by pressing alt+F7.
The sleep LED will blink for a while after resume, but will stop eventually and the wireless devices will be switched back on. You may experience some resetting of the display when that happens. Just move the cursor to regain your desktop.

== 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.}}

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61p

2008-07-31T00:11:29Z

Gertvdijk: /* What doesn't work at the moment? */

==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
*Optical drive
**Optiarc AD-7910A
*Sound card
**Microphone not yet tested
*Memory card reader
**Only tested SD (non-HC) cards. Didn't take locked (read-only) cards.
*Control buttons/Hotkeys
**Volume control buttons
**Screen brightness control
**Thinklight control
**WLAN/BT/OFF toggle
**Media player control
*Some ACPI features
**Battery status, power graphs and history
**Lid states and events
**LCD brightness adjustment on power source
**Only tested with a single 6-cell battery

==What needs some tweaks?==
*Suspend-to-RAM (Standby, Suspend)

==What doesn't work at the moment?==
*Suspend-to-Disk (Hibernate)
*Wireless LAN power/activity LED

== Display / Video ==

To enable 3D acceleration, the proprietary NVidia driver must be installed. The first time you boot into Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at System --> Administration --> Hardware Drivers.

If you want more options for configuring your video card than is provided by the Ubuntu control panels, you can install the NVidia Control Panel with

{{cmduser| sudo apt-get install nvidia-settings}}

which will add the NVidia X Server Settings panel to the Administration menu.

Alternately, the NVidia driver and Control Panel can be installed using EnvyNG (envyng-gtk in Synaptic). Simply start it up (System Tools --> EnvyNG) and ask it to install the NVidia driver.

Unfortunately, there are some annoying bugs in the NVidia driver. The most annoying one is that after resuming from suspend, you will often get a blank white screen. To get past it, simply type in your password and press enter, and you will be returned to your desktop. Fortunately, Ubuntu has released a workaround for this bug, so it should go away once you update all your packages to the latest versions.

Another problem is that the driver does not report the correct refresh rate to Compiz, resulting in rough animation. To fix this, install the compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. Click on General Options, go to the Display Settings tab, uncheck the Detect Refresh rate box and drag the Refresh Rate slider to 60. Also, check the Sync To VBlank box.

Next, Compiz animations are also choppy due to NVidia's PowerMizer feature, which slows down the GPU to conserve power when it is not in use. This works well for 3D games which constantly use 3D acceleration, but poorly for Compiz which uses the GPU in small bursts. To solve this problem, I made a couple of shell scripts which keep the GPU at its highest speed while running on AC power. The first one is named "powermizer-loop" and does most of the work:

#!/bin/sh

while true; do

powerstate=`cat /proc/acpi/ac_adapter/AC/state | awk '{print $2}'`

if [ $powerstate = "on-line" ]; then
nvidia-settings -q all > /dev/null
fi
sleep 25;
done

The second is named "powermizer-off" and starts up powermizer-loop when I log in, ensuring that only one copy runs at a time:

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

I put both of these scripts in my home directory and made them executable by doing:

chmod 755 powermizer-loop powermizer-off

Then to make powermizer-off run on login, I opened System --> Preferences --> Sessions, clicked on Add, and entered the command "/home/argilo/powermizer-off".

Of course, performance still suffers when running on battery, but hopefully NVidia will fix this problem in a future version of their driver.

One final bug is that EDID (Extended Display Identification Data) is misdetected, which causes problems with font sizes and greatly reduces the number of resolutions available in the NVidia X Server Settings application. (For example, I was unable to set my laptop's screen to 1024x768 for use with a projector during a presentation.) To correct this problem, I added the following lines to /etc/X11/xorg.conf in the "Screen" section:

Option "UseEdidDpi" "FALSE"
Option "DPI" "96 x 96"
Option "UseEdidFreqs" "FALSE"
Option "HorizSync" "40-70"

The first two lines fix the font size issue, and the last two lines fix the resolution problem. I'm not sure if the 40-70 values are actually correct, since I just took them from someone else's xorg.conf, but they seem to work.

NVidia seems to have corrected the EDID misdetection bug in the latest version of their driver, but it's not available in Hardy and I'm not aware of any easy way to install it.

== Suspend ==
Suspend is supposed to work out of the box if you're not using the Nvidia binary drivers. If you are using them, the following instructions will fix suspend to ram. Suspend to disk (hibernate) is not working at this time.

{{NOTE|These instructions worked on the T61p with type numbers 6460, 6457 (and perhaps 6465). It may also work with other type numbers.}}

To get suspend to ram working, you need to edit a configuration file, which apparently has some bad information in it.

{{cmduser |gksudo gedit /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi}}

Find the following section:
...

<match key="system.hardware.product" prefix_outof="6457;6460;6465">
<merge key="power_management.quirk.s3_bios" type="bool">true</merge>
<merge key="power_management.quirk.vbemode_restore" type="bool">true</merge>
</match>


<match key="system.hardware.product" prefix_outof="6459;7664;8918">
<merge key="power_management.quirk.none" type="bool">true</merge>
</match>


...

Remove the <code>6457;6460;</code> from the <code><match key="system.hardware.product" prefix_outof="6457;6460;6465"></code> line and add the following lines right before the <code></code> line:
<match key="system.hardware.product" prefix_outof="6457;6460">
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.vbemode_restore" type="bool">true</merge>
</match>

Based on [https://bugs.launchpad.net/ubuntu/+source/hal-info/+bug/235284 Bug #235284 in hal-info (Ubuntu)]

On (at least) the 6457 model you'll need the latest binary Nvidia graphics drivers (173.14.09 at time of writing for Envy) to be able to resume from suspend. Additionally I have to switch to the X terminal manually by pressing alt+F7.
The sleep LED will blink for a while after resume, but will stop eventually and the wireless devices will be switched back on.

== 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.}}

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61p

2008-07-31T00:10:25Z

Gertvdijk: /* What works out of the box? */

==What works out of the box?==
*Wireless (Intel 3945ABG or 4965AGN)
**Only tested G mode
*Wired LAN
*Video (VESA)
**Hardware Drivers panel offers to install NVidia proprietary drivers on first boot
*Touchpoint and Trackpad
**Including scroll at the right side of the pad
*Optical drive
**Optiarc AD-7910A
*Sound card
**Microphone not yet tested
*Memory card reader
**Only tested SD (non-HC) cards. Didn't take locked (read-only) cards.
*Control buttons/Hotkeys
**Volume control buttons
**Screen brightness control
**Thinklight control
**WLAN/BT/OFF toggle
**Media player control
*Some ACPI features
**Battery status, power graphs and history
**Lid states and events
**LCD brightness adjustment on power source
**Only tested with a single 6-cell battery

==What needs some tweaks?==
*Suspend-to-RAM (Standby, Suspend)

==What doesn't work at the moment?==
*Suspend-to-Disk (Hibernate)

== Display / Video ==

To enable 3D acceleration, the proprietary NVidia driver must be installed. The first time you boot into Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at System --> Administration --> Hardware Drivers.

If you want more options for configuring your video card than is provided by the Ubuntu control panels, you can install the NVidia Control Panel with

{{cmduser| sudo apt-get install nvidia-settings}}

which will add the NVidia X Server Settings panel to the Administration menu.

Alternately, the NVidia driver and Control Panel can be installed using EnvyNG (envyng-gtk in Synaptic). Simply start it up (System Tools --> EnvyNG) and ask it to install the NVidia driver.

Unfortunately, there are some annoying bugs in the NVidia driver. The most annoying one is that after resuming from suspend, you will often get a blank white screen. To get past it, simply type in your password and press enter, and you will be returned to your desktop. Fortunately, Ubuntu has released a workaround for this bug, so it should go away once you update all your packages to the latest versions.

Another problem is that the driver does not report the correct refresh rate to Compiz, resulting in rough animation. To fix this, install the compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. Click on General Options, go to the Display Settings tab, uncheck the Detect Refresh rate box and drag the Refresh Rate slider to 60. Also, check the Sync To VBlank box.

Next, Compiz animations are also choppy due to NVidia's PowerMizer feature, which slows down the GPU to conserve power when it is not in use. This works well for 3D games which constantly use 3D acceleration, but poorly for Compiz which uses the GPU in small bursts. To solve this problem, I made a couple of shell scripts which keep the GPU at its highest speed while running on AC power. The first one is named "powermizer-loop" and does most of the work:

#!/bin/sh

while true; do

powerstate=`cat /proc/acpi/ac_adapter/AC/state | awk '{print $2}'`

if [ $powerstate = "on-line" ]; then
nvidia-settings -q all > /dev/null
fi
sleep 25;
done

The second is named "powermizer-off" and starts up powermizer-loop when I log in, ensuring that only one copy runs at a time:

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

I put both of these scripts in my home directory and made them executable by doing:

chmod 755 powermizer-loop powermizer-off

Then to make powermizer-off run on login, I opened System --> Preferences --> Sessions, clicked on Add, and entered the command "/home/argilo/powermizer-off".

Of course, performance still suffers when running on battery, but hopefully NVidia will fix this problem in a future version of their driver.

One final bug is that EDID (Extended Display Identification Data) is misdetected, which causes problems with font sizes and greatly reduces the number of resolutions available in the NVidia X Server Settings application. (For example, I was unable to set my laptop's screen to 1024x768 for use with a projector during a presentation.) To correct this problem, I added the following lines to /etc/X11/xorg.conf in the "Screen" section:

Option "UseEdidDpi" "FALSE"
Option "DPI" "96 x 96"
Option "UseEdidFreqs" "FALSE"
Option "HorizSync" "40-70"

The first two lines fix the font size issue, and the last two lines fix the resolution problem. I'm not sure if the 40-70 values are actually correct, since I just took them from someone else's xorg.conf, but they seem to work.

NVidia seems to have corrected the EDID misdetection bug in the latest version of their driver, but it's not available in Hardy and I'm not aware of any easy way to install it.

== Suspend ==
Suspend is supposed to work out of the box if you're not using the Nvidia binary drivers. If you are using them, the following instructions will fix suspend to ram. Suspend to disk (hibernate) is not working at this time.

{{NOTE|These instructions worked on the T61p with type numbers 6460, 6457 (and perhaps 6465). It may also work with other type numbers.}}

To get suspend to ram working, you need to edit a configuration file, which apparently has some bad information in it.

{{cmduser |gksudo gedit /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi}}

Find the following section:
...

<match key="system.hardware.product" prefix_outof="6457;6460;6465">
<merge key="power_management.quirk.s3_bios" type="bool">true</merge>
<merge key="power_management.quirk.vbemode_restore" type="bool">true</merge>
</match>


<match key="system.hardware.product" prefix_outof="6459;7664;8918">
<merge key="power_management.quirk.none" type="bool">true</merge>
</match>


...

Remove the <code>6457;6460;</code> from the <code><match key="system.hardware.product" prefix_outof="6457;6460;6465"></code> line and add the following lines right before the <code></code> line:
<match key="system.hardware.product" prefix_outof="6457;6460">
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.vbemode_restore" type="bool">true</merge>
</match>

Based on [https://bugs.launchpad.net/ubuntu/+source/hal-info/+bug/235284 Bug #235284 in hal-info (Ubuntu)]

On (at least) the 6457 model you'll need the latest binary Nvidia graphics drivers (173.14.09 at time of writing for Envy) to be able to resume from suspend. Additionally I have to switch to the X terminal manually by pressing alt+F7.
The sleep LED will blink for a while after resume, but will stop eventually and the wireless devices will be switched back on.

== 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.}}

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61p

2008-07-31T00:08:33Z

Gertvdijk: /* What works out of the box */

==What works out of the box?==
*Wireless (Intel 3945ABG or 4965AGN)
**Only tested G mode
**WLAN LED not working
*Wired LAN
*Video (VESA)
**Hardware Drivers panel offers to install NVidia proprietary drivers on first boot
*Touchpoint and Trackpad
**Including scroll at the right side of the pad
*Optical drive
**Optiarc AD-7910A
*Sound card
**Microphone not yet tested
*Memory card reader
**Only tested SD cards. Didn't take locked (read-only) cards.
*Control buttons/Hotkeys
**Volume control buttons
**Screen brightness control
**Thinklight control
**WLAN/BT/OFF toggle
**Media player control
*Some ACPI features
**Battery status, power graphs and history
**Lid states and events
**LCD brightness adjustment on power source
**Only tested with a single 6-cell battery

==What needs some tweaks?==
*Suspend-to-RAM (Standby, Suspend)

==What doesn't work at the moment?==
*Suspend-to-Disk (Hibernate)

== Display / Video ==

To enable 3D acceleration, the proprietary NVidia driver must be installed. The first time you boot into Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at System --> Administration --> Hardware Drivers.

If you want more options for configuring your video card than is provided by the Ubuntu control panels, you can install the NVidia Control Panel with

{{cmduser| sudo apt-get install nvidia-settings}}

which will add the NVidia X Server Settings panel to the Administration menu.

Alternately, the NVidia driver and Control Panel can be installed using EnvyNG (envyng-gtk in Synaptic). Simply start it up (System Tools --> EnvyNG) and ask it to install the NVidia driver.

Unfortunately, there are some annoying bugs in the NVidia driver. The most annoying one is that after resuming from suspend, you will often get a blank white screen. To get past it, simply type in your password and press enter, and you will be returned to your desktop. Fortunately, Ubuntu has released a workaround for this bug, so it should go away once you update all your packages to the latest versions.

Another problem is that the driver does not report the correct refresh rate to Compiz, resulting in rough animation. To fix this, install the compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. Click on General Options, go to the Display Settings tab, uncheck the Detect Refresh rate box and drag the Refresh Rate slider to 60. Also, check the Sync To VBlank box.

Next, Compiz animations are also choppy due to NVidia's PowerMizer feature, which slows down the GPU to conserve power when it is not in use. This works well for 3D games which constantly use 3D acceleration, but poorly for Compiz which uses the GPU in small bursts. To solve this problem, I made a couple of shell scripts which keep the GPU at its highest speed while running on AC power. The first one is named "powermizer-loop" and does most of the work:

#!/bin/sh

while true; do

powerstate=`cat /proc/acpi/ac_adapter/AC/state | awk '{print $2}'`

if [ $powerstate = "on-line" ]; then
nvidia-settings -q all > /dev/null
fi
sleep 25;
done

The second is named "powermizer-off" and starts up powermizer-loop when I log in, ensuring that only one copy runs at a time:

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

I put both of these scripts in my home directory and made them executable by doing:

chmod 755 powermizer-loop powermizer-off

Then to make powermizer-off run on login, I opened System --> Preferences --> Sessions, clicked on Add, and entered the command "/home/argilo/powermizer-off".

Of course, performance still suffers when running on battery, but hopefully NVidia will fix this problem in a future version of their driver.

One final bug is that EDID (Extended Display Identification Data) is misdetected, which causes problems with font sizes and greatly reduces the number of resolutions available in the NVidia X Server Settings application. (For example, I was unable to set my laptop's screen to 1024x768 for use with a projector during a presentation.) To correct this problem, I added the following lines to /etc/X11/xorg.conf in the "Screen" section:

Option "UseEdidDpi" "FALSE"
Option "DPI" "96 x 96"
Option "UseEdidFreqs" "FALSE"
Option "HorizSync" "40-70"

The first two lines fix the font size issue, and the last two lines fix the resolution problem. I'm not sure if the 40-70 values are actually correct, since I just took them from someone else's xorg.conf, but they seem to work.

NVidia seems to have corrected the EDID misdetection bug in the latest version of their driver, but it's not available in Hardy and I'm not aware of any easy way to install it.

== Suspend ==
Suspend is supposed to work out of the box if you're not using the Nvidia binary drivers. If you are using them, the following instructions will fix suspend to ram. Suspend to disk (hibernate) is not working at this time.

{{NOTE|These instructions worked on the T61p with type numbers 6460, 6457 (and perhaps 6465). It may also work with other type numbers.}}

To get suspend to ram working, you need to edit a configuration file, which apparently has some bad information in it.

{{cmduser |gksudo gedit /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi}}

Find the following section:
...

<match key="system.hardware.product" prefix_outof="6457;6460;6465">
<merge key="power_management.quirk.s3_bios" type="bool">true</merge>
<merge key="power_management.quirk.vbemode_restore" type="bool">true</merge>
</match>


<match key="system.hardware.product" prefix_outof="6459;7664;8918">
<merge key="power_management.quirk.none" type="bool">true</merge>
</match>


...

Remove the <code>6457;6460;</code> from the <code><match key="system.hardware.product" prefix_outof="6457;6460;6465"></code> line and add the following lines right before the <code></code> line:
<match key="system.hardware.product" prefix_outof="6457;6460">
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.vbemode_restore" type="bool">true</merge>
</match>

Based on [https://bugs.launchpad.net/ubuntu/+source/hal-info/+bug/235284 Bug #235284 in hal-info (Ubuntu)]

On (at least) the 6457 model you'll need the latest binary Nvidia graphics drivers (173.14.09 at time of writing for Envy) to be able to resume from suspend. Additionally I have to switch to the X terminal manually by pressing alt+F7.
The sleep LED will blink for a while after resume, but will stop eventually and the wireless devices will be switched back on.

== 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.}}

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61p

2008-07-30T23:51:37Z

Gertvdijk: /* Bluetooth */

==What works out of the box==
*Video driver
*Wireless (Intel 3945ABG or 4965AGN)
**Only tested G mode
*Video (VESA)
**Hardware Drivers panel offers to install NVidia proprietary drivers on first boot
*Touchpoint and trackpad
*Volume control buttons
*Screen brightness control

== Display / Video ==

To enable 3D acceleration, the proprietary NVidia driver must be installed. The first time you boot into Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at System --> Administration --> Hardware Drivers.

If you want more options for configuring your video card than is provided by the Ubuntu control panels, you can install the NVidia Control Panel with

{{cmduser| sudo apt-get install nvidia-settings}}

which will add the NVidia X Server Settings panel to the Administration menu.

Alternately, the NVidia driver and Control Panel can be installed using EnvyNG (envyng-gtk in Synaptic). Simply start it up (System Tools --> EnvyNG) and ask it to install the NVidia driver.

Unfortunately, there are some annoying bugs in the NVidia driver. The most annoying one is that after resuming from suspend, you will often get a blank white screen. To get past it, simply type in your password and press enter, and you will be returned to your desktop. Fortunately, Ubuntu has released a workaround for this bug, so it should go away once you update all your packages to the latest versions.

Another problem is that the driver does not report the correct refresh rate to Compiz, resulting in rough animation. To fix this, install the compizconfig-settings-manager package, then go to System --> Preferences --> Advanced Desktop Effects Settings. Click on General Options, go to the Display Settings tab, uncheck the Detect Refresh rate box and drag the Refresh Rate slider to 60. Also, check the Sync To VBlank box.

Next, Compiz animations are also choppy due to NVidia's PowerMizer feature, which slows down the GPU to conserve power when it is not in use. This works well for 3D games which constantly use 3D acceleration, but poorly for Compiz which uses the GPU in small bursts. To solve this problem, I made a couple of shell scripts which keep the GPU at its highest speed while running on AC power. The first one is named "powermizer-loop" and does most of the work:

#!/bin/sh

while true; do

powerstate=`cat /proc/acpi/ac_adapter/AC/state | awk '{print $2}'`

if [ $powerstate = "on-line" ]; then
nvidia-settings -q all > /dev/null
fi
sleep 25;
done

The second is named "powermizer-off" and starts up powermizer-loop when I log in, ensuring that only one copy runs at a time:

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

I put both of these scripts in my home directory and made them executable by doing:

chmod 755 powermizer-loop powermizer-off

Then to make powermizer-off run on login, I opened System --> Preferences --> Sessions, clicked on Add, and entered the command "/home/argilo/powermizer-off".

Of course, performance still suffers when running on battery, but hopefully NVidia will fix this problem in a future version of their driver.

One final bug is that EDID (Extended Display Identification Data) is misdetected, which causes problems with font sizes and greatly reduces the number of resolutions available in the NVidia X Server Settings application. (For example, I was unable to set my laptop's screen to 1024x768 for use with a projector during a presentation.) To correct this problem, I added the following lines to /etc/X11/xorg.conf in the "Screen" section:

Option "UseEdidDpi" "FALSE"
Option "DPI" "96 x 96"
Option "UseEdidFreqs" "FALSE"
Option "HorizSync" "40-70"

The first two lines fix the font size issue, and the last two lines fix the resolution problem. I'm not sure if the 40-70 values are actually correct, since I just took them from someone else's xorg.conf, but they seem to work.

NVidia seems to have corrected the EDID misdetection bug in the latest version of their driver, but it's not available in Hardy and I'm not aware of any easy way to install it.

== Suspend ==
Suspend is supposed to work out of the box if you're not using the Nvidia binary drivers. If you are using them, the following instructions will fix suspend to ram. Suspend to disk (hibernate) is not working at this time.

{{NOTE|These instructions worked on the T61p with type numbers 6460, 6457 (and perhaps 6465). It may also work with other type numbers.}}

To get suspend to ram working, you need to edit a configuration file, which apparently has some bad information in it.

{{cmduser |gksudo gedit /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi}}

Find the following section:
...

<match key="system.hardware.product" prefix_outof="6457;6460;6465">
<merge key="power_management.quirk.s3_bios" type="bool">true</merge>
<merge key="power_management.quirk.vbemode_restore" type="bool">true</merge>
</match>


<match key="system.hardware.product" prefix_outof="6459;7664;8918">
<merge key="power_management.quirk.none" type="bool">true</merge>
</match>


...

Remove the <code>6457;6460;</code> from the <code><match key="system.hardware.product" prefix_outof="6457;6460;6465"></code> line and add the following lines right before the <code></code> line:
<match key="system.hardware.product" prefix_outof="6457;6460">
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.vbemode_restore" type="bool">true</merge>
</match>

Based on [https://bugs.launchpad.net/ubuntu/+source/hal-info/+bug/235284 Bug #235284 in hal-info (Ubuntu)]

On (at least) the 6457 model you'll need the latest binary Nvidia graphics drivers (173.14.09 at time of writing for Envy) to be able to resume from suspend. Additionally I have to switch to the X terminal manually by pressing alt+F7.
The sleep LED will blink for a while after resume, but will stop eventually and the wireless devices will be switched back on.

== 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.}}

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61p

2008-07-30T23:47:17Z

Gertvdijk: /* Suspend */