ThinkWiki - User contributions [en]

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61

2008-05-14T00:14:28Z

Pascal: /* Suspend with Nv140m */

== Items that work out of the box ==

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

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

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

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

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

'''Wireless switch''' Tested

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Also you want to set the following parameter in

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

{{NOTE|This works for me with mode 6460, except for one problem: You may get a white screen in xorg after resume when using compiz. If you don't have a 6460 with nvidia this file may break things for you because it doesn't care about the modell and sets the parameter for any lenovo product}}
{{HELP|Anyone with more knowledge of hal and acpi-support is welcome to clean this up. I also don't know why this setting can be done via hal and in acpi-support.
See below!}}

'''Working on hardy final'''

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

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

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

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

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

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

[[Category: T61]]

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

=== Audio ===

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

To unmute the microphone:

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

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

Input Source
Capture

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

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

*Click Options and under capture source select internal mic.

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

This solution has been tested with Sound Recorder and Skype.

To get the volume controls working:

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

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

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

=== Multimedia Keys ===

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

* Fn-PgUp activates/deactivates the thinklight
* Fn-Up will trigger stop on a media player
* Fn-Down will toggle pause and play on a media player
* Fn-Left/Right go to prev/next tracks on a media player
* Fn-F2 properly locks the screen
* Fn-F3 shows remaining battery >>does not work on all machines<<
* Fn-F4 suspends (to ram)
* Fn-F9 ejects cds
* Fn-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

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

=== Hotswapping ===

With the new kernel, bay-drivers changed, so if you remove the ultrabay it will freeze your system! You can hack it with a simple comand, first you have to look where the device is:

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

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

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

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

Now you should be able to remove the device.

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

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

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

=== Wireless activity LED ===

The LED is not implemented at least in the IWL4965 driver.

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

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

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

To active WiFi LED,

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

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

=== Hidden SSID ===
It has been reported that users wanting to access Hidden SSIDs have to enter the SSID and password manually in Network Manager to connect. Even after the SSID is saved in Network Manager, it will not reconnect automatically. The user has to connect manually by entering the information as previously described. Please post any fixes here.

=== Hard Disk Parking ===
Getting hard disk parking to work is a 3 step process:

1. Patch your system with tp_smapi.

2. Patch your kernel with the 'protect' patch.

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

See the following link for instructions on implementing Hard Disk Parking:
http://www.thinkwiki.org/wiki/How_to_protect_the_harddisk_through_APS

{{HELP|Patch is outdated. It won't work under Gutsy kernel due to API changes. Please attach link to working patch. }}

[[Category: Ubuntu 8.04]]

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61

2008-05-14T00:13:27Z

Pascal: /* Suspend with Nv140m */

== Items that work out of the box ==

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

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

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

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

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

'''Wireless switch''' Tested

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Also you want to set the following parameter in

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

{{NOTE|This works for me with mode 6460, except for one problem: You may get a white screen in xorg after resume when using compiz. If you don't have a 6460 with nvidia this file may break things for you because it doesn't care about the modell and sets the parameter for any lenovo product}}
{{HELP|Anyone with more knowledge of hal and acpi-support is welcome to clean this up. I also don't know why this setting can be done via hal and in acpi-support
See below!}}

'''Working on hardy final'''

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

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

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

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

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

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

[[Category: T61]]

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

=== Audio ===

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

To unmute the microphone:

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

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

Input Source
Capture

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

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

*Click Options and under capture source select internal mic.

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

This solution has been tested with Sound Recorder and Skype.

To get the volume controls working:

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

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

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

=== Multimedia Keys ===

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

* Fn-PgUp activates/deactivates the thinklight
* Fn-Up will trigger stop on a media player
* Fn-Down will toggle pause and play on a media player
* Fn-Left/Right go to prev/next tracks on a media player
* Fn-F2 properly locks the screen
* Fn-F3 shows remaining battery >>does not work on all machines<<
* Fn-F4 suspends (to ram)
* Fn-F9 ejects cds
* Fn-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

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

=== Hotswapping ===

With the new kernel, bay-drivers changed, so if you remove the ultrabay it will freeze your system! You can hack it with a simple comand, first you have to look where the device is:

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

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

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

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

Now you should be able to remove the device.

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

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

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

=== Wireless activity LED ===

The LED is not implemented at least in the IWL4965 driver.

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

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

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

To active WiFi LED,

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

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

=== Hidden SSID ===
It has been reported that users wanting to access Hidden SSIDs have to enter the SSID and password manually in Network Manager to connect. Even after the SSID is saved in Network Manager, it will not reconnect automatically. The user has to connect manually by entering the information as previously described. Please post any fixes here.

=== Hard Disk Parking ===
Getting hard disk parking to work is a 3 step process:

1. Patch your system with tp_smapi.

2. Patch your kernel with the 'protect' patch.

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

See the following link for instructions on implementing Hard Disk Parking:
http://www.thinkwiki.org/wiki/How_to_protect_the_harddisk_through_APS

{{HELP|Patch is outdated. It won't work under Gutsy kernel due to API changes. Please attach link to working patch. }}

[[Category: Ubuntu 8.04]]

Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61

2007-11-23T02:18:31Z

Pascal: /* Interrupt problem */

==Introduction==

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

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

==Installation Notes ==

*If booting with the live CD gives you a blank screen you should select the "Safe Graphics" menu choice.

== Display/Video ==

=== Accelerated Video and Desktop Effects ===
'''Intel''' 2D and 3D accelerated video work out of the box.

Due to [https://bugs.launchpad.net/xorg-server/+bug/111257 | bug 111257], compiz is disabled on the Intel i965 based video cards. To fix it, download this file[http://www.fileden.com/files/2007/9/28/1467484/compizubuntuintel.zip], unzip it, and follow the instructions in "description and README."
.
''Note: If you enable Compiz on an Intel card there will be issues with viewing video files in Totem, please see the bug report above for details.

'''Nvidia''' 2D video works out of the box, to enable accelerated 3D support click System->Administration->Restricted Drivers Manager {{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 Synaptics and the Restricted Drivers Manager}}

===Multiple Monitors===

If you previously used Xinerama this is no longer a supported option, you should use one of the tools described below to configure dual displays.

'''Nvidia N140m:'''

When using the default drivers (The open source "nv" drivers) you can use Administration->"Screens and Graphics" to setup the second monitor

Using the proprietary drivers you must use the Nvidia tool located at Applications->System Tools-> Nvidia X Server Settings. Note:
Twinview works but a movie will span both the laptop screen and second monitor or projector.

If you experience problems getting a working Twinview setup using nvidia-settings, please see [http://www.nvnews.net/vbulletin/showthread.php?t=101780 this thread]

'''Intel X3100:'''

Plugging in an external monitor works, but is a clone of the built-in LCD by default. Using the Screens and Graphics tool located under Administration you can setup the second monitor as an extension of the existing screen or a clone for presentations.

'''Setting up dual monitors via the command line'''

If you like doing it via the command line and are using the Intel drivers or the open-source "nv" driver you can use this example (''Note all this should be possible using the Screens and Graphics tool so only make this change if you prefer the command line method''):

This is an example for a 1680x1050 built-in LCD and a 1600x1200 external LCD:
Add a "Virtual 3280 1200" line in the Display SubSection of the Screen Section in your xorg.conf:

Exit to a virtual terminal (press: ctrl-alt-F1), login and type the following:

{{cmdroot|sudo /etc/init.d/gdm stop}}

{{cmdroot|xrandr --output LVDS --auto}}

To set the built-in LCD to ouput 1680x1050

{{cmdroot|xrandr --output VGA --right-of LVDS}}

To extend the desktop

=== Fonts on High-Res Screens ===

On high-res screens (e.g. 15" 1680x1050), some users consider the default fonts too be too large ([https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/99145 Launchpad bug report]). You can fix this by following these steps:

# Open System->Preferences->Appearance
# Select the "Fonts" tab
# Click the "Details" button (lower right)
# Adjust the Resolution down to 96dpi
# Make sure you have Subpixel (LCD) Smoothing enabled
# Save the preferences

If you also want small fonts on the GDM login window, you can do this:

# Open System->Administration->Login Window
# Select the 'Security' tab
# Click the 'Configure X-Server' button
# Append '-dpi 96' (without quotes) to the text in the 'Command' field
# Reboot the computer.

=== Brightness ===
====Intel X3100:====
The brightness controls should work out of the box on a fresh install.

====Nvidia Quadro N140 and 570M:====
The brightness controls do not work out of the box, 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 (You should save anything open just to be safe). There is a new [http://www.nvidia.com/object/linux_display_ia32_169.04.html beta-driver (version 169.04)] by nvidia that fixes the brightness-controls but unfortunately there is currently no ubuntu-package for this driver so you will have to install it manually (which is normally not the preferred way of doing things).

-->please post a "howto install beta drivers" link here

{{QUOTE|Mike Kershaw|linux-thinkpad@linux-thinkpad.org|This problem was solved (for me) with the latest IBM bios release,
October 18, bios 1.26, 7KET56WW. In-X brightness works now via the hw
keys and acpi/ibm/brightness.}}

== Audio ==

=== Inextricably Linked to the Modem ===
Make sure that you have the modem enabled in the BIOS. If it is disabled, you may discover that your audio is also disabled. In this situation, your drivers may still load, but you will get an error message whenever you try to play audio.

===Enabling Audio controls===

By default, the sound may be disabled and the volume control buttons on the laptop (up by the ThinkVantage button) and the volume control applet (up by the clock) will not control the speaker volume (they actually control the microphone). To fix this:

# Right-click on the volume control applet (by the clock) and select "Open Volume Control"
# In the "Switches" tab, make sure "Headphone" and "Speaker" are both checked.
# Close the Volume control.
# Right-click on the volume control applet again and select "Preferences".
# Make sure the device is set to "HDA Intel (Alsa mixer)" and highlight the "PCM" option.
# Close the preferences.
# Select System->Preferences->Sound.
# In the "Default Mixer Tracks" section, make sure "PCM" is highlighted.
# Close the sound preferences.

You should now hear sound and be able to control the volume using the laptop buttons or volume applet.

A recent BIOS update [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-67989] fixes the mute button, you can then configure it to mute/unmute audio in Keyboard Shortcuts.

===Microphone===

There have been reports that the microphone may not work, please add your input to the talk page [http://www.thinkwiki.org/wiki/Talk:Installing_Ubuntu_7.10_%28Gutsy_Gibbon%29_on_a_ThinkPad_T61#Microphone] and update this section when a consensus on the problem and solution has been reached.

===Sound Cracking===

There have been intermittent reports of users experiencing cracking when listening to audio. Here are a few possible solutions:

* Try to switch to the OSS driver in system => preference => sound => devices => Music and movies, select OSS - Open sound system (instead of ALSA)

* If this issue is only occurring for Rhythmbox go to Edit > Preferences > Playback > and Check "Use Crossfading Backend". Restart Rhythmbox and you should have better audio quality.

* Check that the microphone is muted and modify your mixer settings by moving items like PCM down halfway and see if the cracking goes away.

===Hissing===
Some users experience hissing during playback, and even when idle. To solve this mute the microphone when it is not in use:

# Run "alsamixer" in the terminal.
# Arrow over to "Mic", and hit "M" to mute.
# Arrow over to the first "Docking", and hit "M" to mute.
# Arrow to the first "Internal", and hit "M" to mute.

Now, make sure that "Headphone" and/or "Speaker" are _not_ muted, and that "PCM" is at a reasonable level (say ~70) so you don't make your ears bleed, and try playing something back. ''(<Esc> will exit alsamixer)''

== Modem ==

The modem works with the Linuxant drivers available at http://www.linuxant.com

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

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.

== Fingerprint Reader ==

The reader works with ThinkFinger. General instructions available [http://www.thinkwiki.org/wiki/Integrated_Fingerprint_Reader here] and [https://wiki.ubuntu.com/ThinkFinger here].
Instructions in French available at http://doc.ubuntu-fr.org/materiel/thinkfinger

Note that ThinkFinger in it's current version does not work with KDE and Kubuntu in any way (it crashes KDM and is not integrated at all).

Prebuilt packages are available from jldugger using Launchpad's PPA:

Add the thinkfinger package repository by creating {{path|/etc/apt/sources.list.d/thinkfinger.list}} with these two lines:

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

Then update the package database and install packages:

{{cmduser|sudo apt-get update}}
{{cmduser|sudo apt-get install libpam-thinkfinger libthinkfinger-dev libthinkfinger-doc libthinkfinger0 thinkfinger-tools}}

After the package is installed add the following two lines to {{path|/etc/pam.d/common-auth}}

auth sufficient pam_thinkfinger.so
auth required pam_unix.so try_first_pass

Edit {{path|/etc/modules}} and add the following line:

uinput

Load the module manually for this session:

{{cmduser| sudo modprobe uinput}}

Summary:
* Recording fingerprints works
* Login works
* The password must be entered to unlock a locked screensaver
* sudo works
* gksu and gksudo hang : for example it is necessary to run synaptic twice and enter your password upon failure. To be able to use the Finger print reader in the session subsequently, kill the hanging gksu/gksudo process. A workaround is editing the Gnome System Menu (alacarte) to specify sudo instead of gksu/gksudo for the launching command and choose type "Application in Terminal" : this opens an extra terminal window for each superuser application you want to use though.

== Trackpad scrolling ==

Trackpad scrolling works out of the box in the standard thinkpad way: Slide your finger up and down the very right edge of the trackpad.
Note that /etc/X11/xorg.conf will be changed and the edge scrolling will be disabled after running nvidia-xconfig , copy the trackpad section from the backup of xorg.conf

To enable using the middle mouse button to scroll, add the following lines to the "Configured Mouse" section in
{{path|/etc/X11/xorg.conf}}:

Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"

== Hibernate/Suspend ==

=== Blank screen fix for intel graphics cards===

This fix is for Intel Graphics Cards only.

You may get a blank screen when resuming from suspend or hibernate ([https://bugs.launchpad.net/ubuntu/+bug/134391 Launchpad bug report]). To fix this:

1) Go to the in Applications -> Accessories -> Terminal

2) Enter "sudo nautilus" without the quotation marks.

3) Go to {{path|/boot/grub/}}, backup and then edit {{path|menu.lst}} by adding "acpi_sleep=s3_bios" (no quotes) to the "defoptions" list so that it looks something like this:

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash '''acpi_sleep=s3_bios'''

4) Once you have edited the line and added the acpi_sleep parameter, you need to run

<pre>sudo update-grub</pre>

in the terminal.

Note that if you get the blank screen upon resume, a quick-fix is to switch to a console (Ctrl-Alt-F1) and then back to X (Ctrl-Alt-F7). This will usually bring the display back to life. However, the long-term fix is to add the acpi_sleep parameter as shown above.

=== How to Suspend with nVidia 140m/570m ===

The suspend to RAM will work with the nVidia card and the proprietary drivers, but it requires some file editing. It did not work for me out of the box. Using the package manager, download and install the latest nVidia drivers (100.14.19+2.6.2.4-12.4 at time of writing). I also had to use the 2.6.22-12-generic kernel image (the 2.6.22-13 image did not work with this driver --- I'm assuming it has to match wit the nVidia version, but I am not an expert). (Note: I am using KDE. I would think these fixes would work for gnome as well, but someone else would have to test them.)

Once you have it installed and working, you have to make a change to {{path|/etc/default/acpi-support}}. Open the file in your favorite editor and change the following lines:

$ sudo nano /etc/default/acpi-support

{{path|/etc/default/acpi-support}}
# Should we save and restore state using the VESA BIOS Extensions?
SAVE_VBE_STATE=false
...
# Should we attempt to warm-boot the video hardware on resume?
POST_VIDEO=false
...
# Set the following to "platform" if you want to use ACPI to shut down
# your machine on hibernation
HIBERNATE_MODE=platform

This allowed me to suspend and resume, but after two suspends the wireless wouldn't work anymore. Theoretically, ACPI unloads the network drivers before suspending, but it doesn't seem to work correctly so I added these to the blacklist modules manually (in the same file as above:

{{path|/etc/default/acpi-support}}
# Add modules to this list to have them removed before suspend and reloaded
# on resume. An example would be MODULES="em8300 yenta_socket"
#
# Note that network cards and USB controllers will automatically be unloaded
# unless they're listed in MODULES_WHITELIST
MODULES="iwl4965 iwlwifi_mac80211 cfg80211"

Your wifi modules may be different. (I have the intel AGN wireless card -- I don't know if these modules are different for other cards.)

This allows me to suspend to ram; I haven't had any problems with it so far. I haven't gotten hibernate (suspend to disk) working, so there may be additional things you need to do for that. (I think part of my problem is that I don't have enough swap, but I don't care enough to actually fix it.)

/*The fix does not work for me. I have a T61 7664-17U(NVS 140m, 4965agn). The computers suspend, but when it wakes up it hangs up and I have to pull out the battery to restart it.*/

General hint: Do not install the package "hibernate" or "uswsusp" or the gnome-power-manager will fail to suspend/hibernate your computer. If you have installed the package don't forget to purge the configuration. (sudo apt-get remove hibernate --purge, uswsusp resp.)

The instructions for Intel video card recommends adding "acpi_sleep=s3_bios" to the kernel parameters in Grub configuration. According to a comment on [https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/139089 Launchpad BUG 139089], the correct setting for Nvidia is "acpi_sleep=s3_mode". Once I changed this, Suspend to ram worked. I have the T61 6459-CTO.

== Items that work out of the box ==

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

'''Nvidia:''' 2D works, 3D requires the installation of the proprietary drivers

'''Wireless:''' Atheros and Intel cards both tested.

'''Bluetooth:''' Tested with both a bluetooth headset and an HTC 8525

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

'''Firewire''' Tested with hard drive

'''Wireless switch'''

'''4-in-1 card reader'''

'''Webcam'''

'''Headphones''' You may need to enable Headphone out: Right-click on the volume control and select open volume control. Click the switches tab and then check the headphones box.

'''Keyboard Shortcuts:'''
* Fn-PgUp activates/deactivates the thinklight
* Fn-Up will trigger stop on a media player
* Fn-Down will toggle pause and play on a media player
* Fn-Left/Right go to prev/next tracks on a media player
* Fn-F2 properly locks the screen
* Fn-F3 shows remaining battery >>does not work on all machines<<
* Fn-F4 suspends (to ram)
* Fn-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

'''Docking Stations:'''

All docking station models should work and the following features have been tested:

* DVI or Analog video: You can switch to it using "Administration->Screens and Graphics", if you are using the proprietary Nvidia drivers you must use the Nvidia Control Panel.

* Network Pass-through

* Modem Pass-through

* USB ports: Connected upon docking

* PS/2 Ports

== Items that don't work ==

=== Interrupt problem ===
* https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/126369
* USB ports can end up temporarily disabled
* Wifi can break
* integrated cardreader can be disabled
* bluetooth can be disabled
* Setting IRQ's to "Auto" from factory default of "11" in the BIOS seems to help some people.
* The two USB ports on the left side of the computer may fail to connect storage devices during a session but will load them at boot up.
* booting with the "irqpoll" option seems to work for some people against the problem that usb-ports stop working.

=== Wireless activity LED ===

The LED is not implemented in either the IWL4965 or Atheros drivers.

== Power consumption ==

Gutsy is the first version of Ubuntu to feature a tickless kernel (i386 only, not in AMD64 yet). Power consumption
can be monitored using the powertop tool under Ubuntu and using Lenovo battery monitor
under Windows.

$ sudo apt-get install powertop
$ sudo powertop

I couldn't find any difference in power consumption between the i386 tickless kernel (even with 70ms average sleep in C4)
and AMD64 kernel (2ms average sleep in C4). It would be expected that considerably less power would be consumed for the
i386 tickless kernel.

There is also a graph available by Right-clicking on the battery icon and selecting Power History.

These are the figures measured on a T61 15.4" 1680x1050 screen 7300 processor (2GHz) 2GB RAM, Intel X3100 graphics
with 4965 wifi, Bluetooth and UWB.

{| border=1 cellpadding=5
|-
| 12.3W
| Windows XP Pro, all radios on, about 50% brightness
|-
| 16.7W
| Gutsy, all radios on, 50% brightness
|-
| 19.6W
| Gutsy, all radios on, 100% brightness
|-
| 14.2W
| Gutsy, all radios on, 10% brightness
|-
| -1.0W
| Turning the physical radio switch to off on the front reduces power consumption by 1 watt.
|}

Adding the Nvidia card increases the laptops power requirements.

These are the figures measured on a T61 14" 1440x900 screen 2.2ghz Core2Duo 2GB RAM, Nvidia 140m video, IWL4965 wifi and Bluetooth (Disabled):

{| border=1 cellpadding=5
|-
| 18.3W
| Gutsy, all radios on, 50% brightness
|-
| 19.4W
| Gutsy, all radios on, 100% brightness
|-
| 16.0W
| Gutsy, all radios on, 10% brightness
|-
|}

[[Category: T61]] [[Category: Ubuntu 7.10]]

Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61

2007-10-27T02:14:01Z

Pascal: /* Nvidia Quadro N140 and 570M: */

==Introduction==

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

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

==Installation Notes ==

*If booting with the live CD gives you a blank screen you should select the "Safe Graphics" menu choice.

== Display/Video ==

=== Accelerated Video and Desktop Effects ===
'''Intel''' 2D and 3D accelerated video work out of the box.

Due to [https://bugs.launchpad.net/xorg-server/+bug/111257 | bug 111257], compiz is disabled on the Intel i965 based video cards. To fix it, download this file[http://www.fileden.com/files/2007/9/28/1467484/compizubuntuintel.zip], unzip it, and follow the instructions in "description and README."

''Note: If you enable Compiz on an Intel card there will be issues with viewing media files, please see the bug report above for details''

'''Nvidia''' 2D video works out of the box, to enable accelerated 3D support click System->Administration->Restricted Drivers Manager {{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 Synaptics and the Restricted Drivers Manager}}

===Multiple Monitors===

If you previously used Xinerama this is no longer a supported option, you should use one of the tools described below to configure dual displays.

'''Nvidia N140m:'''

When using the default drivers (The open source "nv" drivers) you can use Administration->"Screens and Graphics" to setup the second monitor

Using the proprietary drivers you must use the Nvidia tool located at Applications->System Tools-> Nvidia X Server Settings. Note:
Twinview works but a movie will span both the laptop screen and second monitor or projector.

'''Intel X3100:'''

Plugging in an external monitor works, but is a clone of the built-in LCD by default. Using the Screens and Graphics tool located under Administration you can setup the second monitor as an extension of the existing screen or a clone for presentations.

'''Setting up dual monitors via the command line'''

If you like doing it via the command line and are using the Intel drivers or the open-source "nv" driver you can use this example (''Note all this should be possible using the Screens and Graphics tool so only make this change if you prefer the command line method''):

This is an example for a 1680x1050 built-in LCD and a 1600x1200 external LCD:
Add a "Virtual 3280 1200" line in the Display SubSection of the Screen Section in your xorg.conf:

Exit to a virtual terminal (press: ctrl-alt-F1), login and type the following:

{{cmdroot|sudo /etc/init.d/gdm stop}}

{{cmdroot|xrandr --output LVDS --auto}}

To set the built-in LCD to ouput 1680x1050

{{cmdroot|xrandr --output VGA --right-of LVDS}}

To extend the desktop

=== Fonts on High-Res Screens ===

On high-res screens (e.g. 15" 1680x1050), some users consider the default fonts too be too large ([https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/99145 Launchpad bug report]). You can fix this by following these steps:

# Open System->Preferences->Appearance
# Select the "Fonts" tab
# Click the "Details" button (lower right)
# Adjust the Resolution down to 96dpi
# Make sure you have Subpixel (LCD) Smoothing enabled
# Save the preferences

If you also want small fonts on the GDM login window, you can do this:

# Open System->Administration->Login Window
# Select the 'Security' tab
# Click the 'Configure X-Server' button
# Append '-dpi 96' (without quotes) to the text in the 'Command' field
# Reboot the computer.

=== Brightness ===
====Intel X3100:====
The brightness controls should work out of the box on a fresh install.

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

How? the brightness buttons aren't working for me in the virtual terminal either --Pascal 27-10-2007

== Audio ==

=== Inextricably Linked to the Modem ===
Make sure that you have the modem enabled in the BIOS. If it is disabled, you may discover (with much consternation) that your audio is also disabled. In this situation, your drivers may still load, but you will get an error message whenever you try to play audio.

After trying all of the ALSA related fixes for this machine, with no love, I remembered what a colleague had said about his T60, and tried this on a hunch. Blammo, it worked!

===Enabling Audio controls===

By default, the sound may be disabled and the volume control buttons on the laptop (up by the ThinkVantage button) and the volume control applet (up by the clock) will not control the speaker volume (they actually control the microphone!). https://bugs.launchpad.net/ubuntu/+bug/136287
this bug report links to a fixed version from an Ubuntu dev a fixed version is available
To fix this:

# Right-click on the volume control applet (by the clock) and select "Open Volume Control"
# In the "Switches" tab, make sure "Headphone" and "Speaker" are both checked.
# Close the Volume control.
# Right-click on the volume control applet again and select "Preferences".
# Make sure the device is set to "HDA Intel (Alsa mixer)" and highlight the "PCM" option.
# Close the preferences.
# Select System->Preferences->Sound.
# In the "Default Mixer Tracks" section, make sure "PCM" is highlighted.
# Close the sound preferences.

You should now hear sound and be able to control the volume using the laptop buttons or volume applet.

A recent BIOS update [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-67989] fixes the mute button, you can then configure it to mute/unmute audio in Keyboard Shortcuts.

===Microphone===

There have been reports that the microphone may not work, please add your input to the talk page [http://www.thinkwiki.org/wiki/Talk:Installing_Ubuntu_7.10_%28Gutsy_Gibbon%29_on_a_ThinkPad_T61#Microphone] and update this section when a consensus on the problem and solution has been reached.

===Sound Cracking===

There have been intermittent reports of users experiencing cracking when listening to audio. Here are a few possible solutions:

* Try to switch to the OSS driver in system => preference => sound => devices => Music and movies, select OSS - Open sound system (instead of ALSA)

* If this issue is only occurring for Rhythmbox go to Edit > Preferences > Playback > and Check "Use Crossfading Backend". Restart Rhythmbox and you should have better audio quality.

* Check that the microphone is muted and modify your mixer settings by moving items like PCM down halfway and see if the cracking goes away.

===Hissing===
Some users experience hissing during playback, and even when idle. To solve this mute the microphone when it is not in use:

# Run "alsamixer".
# Arrow over to "Mic", and hit "M" to mute.
# Arrow over to the first "Docking", and hit "M" to mute.
# Arrow to the first "Internal", and hit "M" to mute.

Now, make sure that "Headphone" and/or "Speaker" are _not_ muted, and that "PCM" is at a reasonable level (say ~70) so you don't make your ears bleed, and try playing something back. ''(<Esc> will exit alsamixer)''

== Modem ==

The modem works with the Linuxant drivers available at http://www.linuxant.com

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

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.

== Fingerprint Reader ==

The reader works with ThinkFinger. General instructions available [http://www.thinkwiki.org/wiki/Integrated_Fingerprint_Reader here] and [https://wiki.ubuntu.com/ThinkFinger here].
Instructions in French available at http://doc.ubuntu-fr.org/materiel/thinkfinger

Note that ThinkFinger in it's current version does not work with KDE and Kubuntu in any way (it crashes KDM and is not integrated at all).

Prebuilt packages are available from jldugger using Launchpad's PPA:

Add the thinkfinger package repository by creating {{path|/etc/apt/sources.list.d/thinkfinger.list}} with these two lines:

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

Then update the package database and install packages:

{{cmduser|sudo apt-get update}}
{{cmduser|sudo apt-get install libpam-thinkfinger libthinkfinger-dev libthinkfinger-doc libthinkfinger0 thinkfinger-tools}}

After the package is installed add the following two lines to {{path|/etc/pam.d/common-auth}}

auth sufficient pam_thinkfinger.so
auth required pam_unix.so try_first_pass

Edit {{path|/etc/modules}} and add the following line:

uinput

Load the module manually for this session:

{{cmduser| sudo modprobe uinput}}

Summary:
* Recording fingerprints works
* Login works
* The password must be entered to unlock a locked screensaver
* sudo works
* gksu and gksudo hang : for example it is necessary to run synaptic twice and enter your password upon failure. To be able to use the Finger print reader in the session subsequently, kill the hanging gksu/gksudo process. A workaround is editing the Gnome System Menu (alacarte) to specify sudo instead of gksu/gksudo for the launching command and choose type "Application in Terminal" : this opens an extra terminal window for each superuser application you want to use though.

== Trackpad scrolling ==

Trackpad scrolling works out of the box in the standard thinkpad way: Slide your finger up and down the very right edge of the trackpad.
Note that /etc/X11/xorg.conf will be changed and the edge scrolling will be disabled after running nvidia-xconfig , copy the trackpad section from the backup of xorg.conf

To enable using the middle mouse button to scroll, add the following lines to the "Configured Mouse" section in
{{path|/etc/X11/xorg.conf}}:

Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"

== Hibernate/Suspend ==

=== Blank screen fix for intel graphics cards===

This fix is for Intel Graphics Cards only.

You may get a blank screen when resuming from suspend or hibernate ([https://bugs.launchpad.net/ubuntu/+bug/134391 Launchpad bug report]). If so, try editing {{path|/boot/grub/menu.lst}}, adding "acpi_sleep=s3_bios" (no quotes) to the "defoptions" list so that it looks something like this:

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash '''acpi_sleep=s3_bios'''

Once you have edited the line and added the acpi_sleep parameter, you need to run

$ sudo update-grub

Note that if you get the blank screen upon resume, a quick-fix is to switch to a console (Ctrl-Alt-F1) and then back to X (Ctrl-Alt-F7). This will usually bring the display back to life. However, the long-term fix is to add the acpi_sleep parameter as shown above.

=== How to Suspend with nVidia 140m/570m ===

The suspend to RAM will work with the nVidia card and the proprietary drivers, but it requires some file editing. It did not work for me out of the box. Using the package manager, download and install the latest nVidia drivers (100.14.19+2.6.2.4-12.4 at time of writing). I also had to use the 2.6.22-12-generic kernel image (the 2.6.22-13 image did not work with this driver --- I'm assuming it has to match wit the nVidia version, but I am not an expert). (Note: I am using KDE. I would think these fixes would work for gnome as well, but someone else would have to test them.)

Once you have it installed and working, you have to make a change to {{path|/etc/default/acpi-support}}. Open the file in your favorite editor and change the following lines:

$ sudo nano /etc/default/acpi-support

{{path|/etc/default/acpi-support}}
# Should we save and restore state using the VESA BIOS Extensions?
SAVE_VBE_STATE=false
...
# Should we attempt to warm-boot the video hardware on resume?
POST_VIDEO=false
...
# Set the following to "platform" if you want to use ACPI to shut down
# your machine on hibernation
HIBERNATE_MODE=platform

This allowed me to suspend and resume, but after two suspends the wireless wouldn't work anymore. Theoretically, ACPI unloads the network drivers before suspending, but it doesn't seem to work correctly so I added these to the blacklist modules manually (in the same file as above:

{{path|/etc/default/acpi-support}}
# Add modules to this list to have them removed before suspend and reloaded
# on resume. An example would be MODULES="em8300 yenta_socket"
#
# Note that network cards and USB controllers will automatically be unloaded
# unless they're listed in MODULES_WHITELIST
MODULES="iwl4965 iwlwifi_mac80211 cfg80211"

Your wifi modules may be different. (I have the intel AGN wireless card -- I don't know if these modules are different for other cards.)

This allows me to suspend to ram; I haven't had any problems with it so far. I haven't gotten hibernate (suspend to disk) working, so there may be additional things you need to do for that. (I think part of my problem is that I don't have enough swap, but I don't care enough to actually fix it.)

/*The fix does not work for me. I have a T61 7664-17U(NVS 140m, 4965agn). The computers suspend, but when it wakes up it hangs up and I have to pull out the battery to restart it.*/

General hint: Do not install the package "hibernate" or "uswsusp" or the gnome-power-manager will fail to suspend/hibernate your computer. If you have installed the package don't forget to purge the configuration. (sudo apt-get remove hibernate --purge, uswsusp resp.)

== Items that work out of the box ==

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

'''Nvidia:''' 2D works, 3D requires the installation of the proprietary drivers

'''Wireless:''' Atheros and Intel cards both tested.

'''Bluetooth:''' Tested with both a bluetooth headset and an HTC 8525

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

'''Firewire''' Tested with hard drive

'''Wireless switch'''

'''4-in-1 card reader'''

'''Webcam'''

'''Headphones''' You may need to enable Headphone out: Right-click on the volume control and select open volume control. Click the switches tab and then check the headphones box.

'''Keyboard Shortcuts:'''
* Fn-PgUp activates/deactivates the thinklight
* Fn-Up will trigger stop on a media player
* Fn-Down will toggle pause and play on a media player
* Fn-Left/Right go to prev/next tracks on a media player
* Fn-F2 properly locks the screen
* Fn-F3 shows remaining battery >>does not work on all machines<<
* Fn-F4 suspends (to ram)
* Fn-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

'''Docking Stations:'''

All docking station models should work and the following features have been tested:

* DVI or Analog video: You can switch to it using "Administration->Screens and Graphics", if you are using the proprietary Nvidia drivers you must use the Nvidia Control Panel.

* Network Pass-through

* Modem Pass-through

* USB ports: Connected upon docking

* PS/2 Ports

== Items that don't work ==

=== Wireless USB/UWB ===

the two usb ports on the left side of the computer fail to connect storage devices during a session but will load them at boot up.

the one usb port on the right side consistently works.

I do not have this problem and nobody else has reported it that I have seen, you may have a bad set of ports. Maybe we should move this to the talk page to attempt to troubleshoot it? --[[User:Darrena|Darrena]] 02:49, 26 October 2007 (UTC)

I also have this problem. It seems to be the bug mentioned in the section below. This is not even about wireless usb --Pascal, 27-10-2007

=== Interrupt problem ===
* https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/126369
* USB ports can end up temporarily disabled
* Wifi can break
* integrated cardreader can be disabled
* bluetooth can be disabled
* Setting IRQ's to "Auto" from factory default of "11" in the BIOS seems to help some people.

=== Volume keys ===

* mute is inconsistent
1. sometimes fails to work at all
2. sometimes works but doesn't display the volume box on the screen
* unmute does not work --to unmute one must use the volume up or down buttons
* Control mic instead of speakers by default
* https://bugs.launchpad.net/ubuntu/+bug/136287

=== Wireless activity LED ===

does not turn on at all

doesn't seem to flicker properly.

== Power consumption ==

Gutsy is the first version of Ubuntu to feature a tickless kernel (i386 only, not in AMD64 yet). Power consumption
can be monitored using the powertop tool under Ubuntu and using Lenovo battery monitor
under Windows.

$ sudo apt-get install powertop
$ sudo powertop

I couldn't find any difference in power consumption between the i386 tickless kernel (even with 70ms average sleep in C4)
and AMD64 kernel (2ms average sleep in C4). It would be expected that considerably less power would be consumed for the
i386 tickless kernel.

There is also a graph available by Right-clicking on the battery icon and selecting Power History.

These are the figures measured on a T61 15.4" 1680x1050 screen 7300 processor (2GHz) 2GB RAM, Intel X3100 graphics
with 4965 wifi, Bluetooth and UWB.

{| border=1 cellpadding=5
|-
| 12.3W
| Windows XP Pro, all radios on, about 50% brightness
|-
| 16.7W
| Gutsy, all radios on, 50% brightness
|-
| 19.6W
| Gutsy, all radios on, 100% brightness
|-
| 14.2W
| Gutsy, all radios on, 10% brightness
|-
| -1.0W
| Turning the physical radio switch to off on the front reduces power consumption by 1 watt.
|}

Adding the Nvidia card increases the laptops power requirements.

These are the figures measured on a T61 14" 1440x900 screen 2.2ghz Core2Duo 2GB RAM, Nvidia 140m video, IWL4965 wifi and Bluetooth (Disabled):

{| border=1 cellpadding=5
|-
| 18.3W
| Gutsy, all radios on, 50% brightness
|-
| 19.4W
| Gutsy, all radios on, 100% brightness
|-
| 16.0W
| Gutsy, all radios on, 10% brightness
|-
|}

[[Category: T61]] [[Category: Ubuntu 7.10]]

Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61

2007-10-27T02:13:36Z

Pascal: /* Nvidia Quadro N140 and 570M: */

==Introduction==

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

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

==Installation Notes ==

*If booting with the live CD gives you a blank screen you should select the "Safe Graphics" menu choice.

== Display/Video ==

=== Accelerated Video and Desktop Effects ===
'''Intel''' 2D and 3D accelerated video work out of the box.

Due to [https://bugs.launchpad.net/xorg-server/+bug/111257 | bug 111257], compiz is disabled on the Intel i965 based video cards. To fix it, download this file[http://www.fileden.com/files/2007/9/28/1467484/compizubuntuintel.zip], unzip it, and follow the instructions in "description and README."

''Note: If you enable Compiz on an Intel card there will be issues with viewing media files, please see the bug report above for details''

'''Nvidia''' 2D video works out of the box, to enable accelerated 3D support click System->Administration->Restricted Drivers Manager {{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 Synaptics and the Restricted Drivers Manager}}

===Multiple Monitors===

If you previously used Xinerama this is no longer a supported option, you should use one of the tools described below to configure dual displays.

'''Nvidia N140m:'''

When using the default drivers (The open source "nv" drivers) you can use Administration->"Screens and Graphics" to setup the second monitor

Using the proprietary drivers you must use the Nvidia tool located at Applications->System Tools-> Nvidia X Server Settings. Note:
Twinview works but a movie will span both the laptop screen and second monitor or projector.

'''Intel X3100:'''

Plugging in an external monitor works, but is a clone of the built-in LCD by default. Using the Screens and Graphics tool located under Administration you can setup the second monitor as an extension of the existing screen or a clone for presentations.

'''Setting up dual monitors via the command line'''

If you like doing it via the command line and are using the Intel drivers or the open-source "nv" driver you can use this example (''Note all this should be possible using the Screens and Graphics tool so only make this change if you prefer the command line method''):

This is an example for a 1680x1050 built-in LCD and a 1600x1200 external LCD:
Add a "Virtual 3280 1200" line in the Display SubSection of the Screen Section in your xorg.conf:

Exit to a virtual terminal (press: ctrl-alt-F1), login and type the following:

{{cmdroot|sudo /etc/init.d/gdm stop}}

{{cmdroot|xrandr --output LVDS --auto}}

To set the built-in LCD to ouput 1680x1050

{{cmdroot|xrandr --output VGA --right-of LVDS}}

To extend the desktop

=== Fonts on High-Res Screens ===

On high-res screens (e.g. 15" 1680x1050), some users consider the default fonts too be too large ([https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/99145 Launchpad bug report]). You can fix this by following these steps:

# Open System->Preferences->Appearance
# Select the "Fonts" tab
# Click the "Details" button (lower right)
# Adjust the Resolution down to 96dpi
# Make sure you have Subpixel (LCD) Smoothing enabled
# Save the preferences

If you also want small fonts on the GDM login window, you can do this:

# Open System->Administration->Login Window
# Select the 'Security' tab
# Click the 'Configure X-Server' button
# Append '-dpi 96' (without quotes) to the text in the 'Command' field
# Reboot the computer.

=== Brightness ===
====Intel X3100:====
The brightness controls should work out of the box on a fresh install.

====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.
How? the brightness buttons aren't working for me in the virtual terminal either --Pascal 27-10-2007

== Audio ==

=== Inextricably Linked to the Modem ===
Make sure that you have the modem enabled in the BIOS. If it is disabled, you may discover (with much consternation) that your audio is also disabled. In this situation, your drivers may still load, but you will get an error message whenever you try to play audio.

After trying all of the ALSA related fixes for this machine, with no love, I remembered what a colleague had said about his T60, and tried this on a hunch. Blammo, it worked!

===Enabling Audio controls===

By default, the sound may be disabled and the volume control buttons on the laptop (up by the ThinkVantage button) and the volume control applet (up by the clock) will not control the speaker volume (they actually control the microphone!). https://bugs.launchpad.net/ubuntu/+bug/136287
this bug report links to a fixed version from an Ubuntu dev a fixed version is available
To fix this:

# Right-click on the volume control applet (by the clock) and select "Open Volume Control"
# In the "Switches" tab, make sure "Headphone" and "Speaker" are both checked.
# Close the Volume control.
# Right-click on the volume control applet again and select "Preferences".
# Make sure the device is set to "HDA Intel (Alsa mixer)" and highlight the "PCM" option.
# Close the preferences.
# Select System->Preferences->Sound.
# In the "Default Mixer Tracks" section, make sure "PCM" is highlighted.
# Close the sound preferences.

You should now hear sound and be able to control the volume using the laptop buttons or volume applet.

A recent BIOS update [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-67989] fixes the mute button, you can then configure it to mute/unmute audio in Keyboard Shortcuts.

===Microphone===

There have been reports that the microphone may not work, please add your input to the talk page [http://www.thinkwiki.org/wiki/Talk:Installing_Ubuntu_7.10_%28Gutsy_Gibbon%29_on_a_ThinkPad_T61#Microphone] and update this section when a consensus on the problem and solution has been reached.

===Sound Cracking===

There have been intermittent reports of users experiencing cracking when listening to audio. Here are a few possible solutions:

* Try to switch to the OSS driver in system => preference => sound => devices => Music and movies, select OSS - Open sound system (instead of ALSA)

* If this issue is only occurring for Rhythmbox go to Edit > Preferences > Playback > and Check "Use Crossfading Backend". Restart Rhythmbox and you should have better audio quality.

* Check that the microphone is muted and modify your mixer settings by moving items like PCM down halfway and see if the cracking goes away.

===Hissing===
Some users experience hissing during playback, and even when idle. To solve this mute the microphone when it is not in use:

# Run "alsamixer".
# Arrow over to "Mic", and hit "M" to mute.
# Arrow over to the first "Docking", and hit "M" to mute.
# Arrow to the first "Internal", and hit "M" to mute.

Now, make sure that "Headphone" and/or "Speaker" are _not_ muted, and that "PCM" is at a reasonable level (say ~70) so you don't make your ears bleed, and try playing something back. ''(<Esc> will exit alsamixer)''

== Modem ==

The modem works with the Linuxant drivers available at http://www.linuxant.com

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

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.

== Fingerprint Reader ==

The reader works with ThinkFinger. General instructions available [http://www.thinkwiki.org/wiki/Integrated_Fingerprint_Reader here] and [https://wiki.ubuntu.com/ThinkFinger here].
Instructions in French available at http://doc.ubuntu-fr.org/materiel/thinkfinger

Note that ThinkFinger in it's current version does not work with KDE and Kubuntu in any way (it crashes KDM and is not integrated at all).

Prebuilt packages are available from jldugger using Launchpad's PPA:

Add the thinkfinger package repository by creating {{path|/etc/apt/sources.list.d/thinkfinger.list}} with these two lines:

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

Then update the package database and install packages:

{{cmduser|sudo apt-get update}}
{{cmduser|sudo apt-get install libpam-thinkfinger libthinkfinger-dev libthinkfinger-doc libthinkfinger0 thinkfinger-tools}}

After the package is installed add the following two lines to {{path|/etc/pam.d/common-auth}}

auth sufficient pam_thinkfinger.so
auth required pam_unix.so try_first_pass

Edit {{path|/etc/modules}} and add the following line:

uinput

Load the module manually for this session:

{{cmduser| sudo modprobe uinput}}

Summary:
* Recording fingerprints works
* Login works
* The password must be entered to unlock a locked screensaver
* sudo works
* gksu and gksudo hang : for example it is necessary to run synaptic twice and enter your password upon failure. To be able to use the Finger print reader in the session subsequently, kill the hanging gksu/gksudo process. A workaround is editing the Gnome System Menu (alacarte) to specify sudo instead of gksu/gksudo for the launching command and choose type "Application in Terminal" : this opens an extra terminal window for each superuser application you want to use though.

== Trackpad scrolling ==

Trackpad scrolling works out of the box in the standard thinkpad way: Slide your finger up and down the very right edge of the trackpad.
Note that /etc/X11/xorg.conf will be changed and the edge scrolling will be disabled after running nvidia-xconfig , copy the trackpad section from the backup of xorg.conf

To enable using the middle mouse button to scroll, add the following lines to the "Configured Mouse" section in
{{path|/etc/X11/xorg.conf}}:

Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"

== Hibernate/Suspend ==

=== Blank screen fix for intel graphics cards===

This fix is for Intel Graphics Cards only.

You may get a blank screen when resuming from suspend or hibernate ([https://bugs.launchpad.net/ubuntu/+bug/134391 Launchpad bug report]). If so, try editing {{path|/boot/grub/menu.lst}}, adding "acpi_sleep=s3_bios" (no quotes) to the "defoptions" list so that it looks something like this:

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash '''acpi_sleep=s3_bios'''

Once you have edited the line and added the acpi_sleep parameter, you need to run

$ sudo update-grub

Note that if you get the blank screen upon resume, a quick-fix is to switch to a console (Ctrl-Alt-F1) and then back to X (Ctrl-Alt-F7). This will usually bring the display back to life. However, the long-term fix is to add the acpi_sleep parameter as shown above.

=== How to Suspend with nVidia 140m/570m ===

The suspend to RAM will work with the nVidia card and the proprietary drivers, but it requires some file editing. It did not work for me out of the box. Using the package manager, download and install the latest nVidia drivers (100.14.19+2.6.2.4-12.4 at time of writing). I also had to use the 2.6.22-12-generic kernel image (the 2.6.22-13 image did not work with this driver --- I'm assuming it has to match wit the nVidia version, but I am not an expert). (Note: I am using KDE. I would think these fixes would work for gnome as well, but someone else would have to test them.)

Once you have it installed and working, you have to make a change to {{path|/etc/default/acpi-support}}. Open the file in your favorite editor and change the following lines:

$ sudo nano /etc/default/acpi-support

{{path|/etc/default/acpi-support}}
# Should we save and restore state using the VESA BIOS Extensions?
SAVE_VBE_STATE=false
...
# Should we attempt to warm-boot the video hardware on resume?
POST_VIDEO=false
...
# Set the following to "platform" if you want to use ACPI to shut down
# your machine on hibernation
HIBERNATE_MODE=platform

This allowed me to suspend and resume, but after two suspends the wireless wouldn't work anymore. Theoretically, ACPI unloads the network drivers before suspending, but it doesn't seem to work correctly so I added these to the blacklist modules manually (in the same file as above:

{{path|/etc/default/acpi-support}}
# Add modules to this list to have them removed before suspend and reloaded
# on resume. An example would be MODULES="em8300 yenta_socket"
#
# Note that network cards and USB controllers will automatically be unloaded
# unless they're listed in MODULES_WHITELIST
MODULES="iwl4965 iwlwifi_mac80211 cfg80211"

Your wifi modules may be different. (I have the intel AGN wireless card -- I don't know if these modules are different for other cards.)

This allows me to suspend to ram; I haven't had any problems with it so far. I haven't gotten hibernate (suspend to disk) working, so there may be additional things you need to do for that. (I think part of my problem is that I don't have enough swap, but I don't care enough to actually fix it.)

/*The fix does not work for me. I have a T61 7664-17U(NVS 140m, 4965agn). The computers suspend, but when it wakes up it hangs up and I have to pull out the battery to restart it.*/

General hint: Do not install the package "hibernate" or "uswsusp" or the gnome-power-manager will fail to suspend/hibernate your computer. If you have installed the package don't forget to purge the configuration. (sudo apt-get remove hibernate --purge, uswsusp resp.)

== Items that work out of the box ==

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

'''Nvidia:''' 2D works, 3D requires the installation of the proprietary drivers

'''Wireless:''' Atheros and Intel cards both tested.

'''Bluetooth:''' Tested with both a bluetooth headset and an HTC 8525

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

'''Firewire''' Tested with hard drive

'''Wireless switch'''

'''4-in-1 card reader'''

'''Webcam'''

'''Headphones''' You may need to enable Headphone out: Right-click on the volume control and select open volume control. Click the switches tab and then check the headphones box.

'''Keyboard Shortcuts:'''
* Fn-PgUp activates/deactivates the thinklight
* Fn-Up will trigger stop on a media player
* Fn-Down will toggle pause and play on a media player
* Fn-Left/Right go to prev/next tracks on a media player
* Fn-F2 properly locks the screen
* Fn-F3 shows remaining battery >>does not work on all machines<<
* Fn-F4 suspends (to ram)
* Fn-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

'''Docking Stations:'''

All docking station models should work and the following features have been tested:

* DVI or Analog video: You can switch to it using "Administration->Screens and Graphics", if you are using the proprietary Nvidia drivers you must use the Nvidia Control Panel.

* Network Pass-through

* Modem Pass-through

* USB ports: Connected upon docking

* PS/2 Ports

== Items that don't work ==

=== Wireless USB/UWB ===

the two usb ports on the left side of the computer fail to connect storage devices during a session but will load them at boot up.

the one usb port on the right side consistently works.

I do not have this problem and nobody else has reported it that I have seen, you may have a bad set of ports. Maybe we should move this to the talk page to attempt to troubleshoot it? --[[User:Darrena|Darrena]] 02:49, 26 October 2007 (UTC)

I also have this problem. It seems to be the bug mentioned in the section below. This is not even about wireless usb --Pascal, 27-10-2007

=== Interrupt problem ===
* https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/126369
* USB ports can end up temporarily disabled
* Wifi can break
* integrated cardreader can be disabled
* bluetooth can be disabled
* Setting IRQ's to "Auto" from factory default of "11" in the BIOS seems to help some people.

=== Volume keys ===

* mute is inconsistent
1. sometimes fails to work at all
2. sometimes works but doesn't display the volume box on the screen
* unmute does not work --to unmute one must use the volume up or down buttons
* Control mic instead of speakers by default
* https://bugs.launchpad.net/ubuntu/+bug/136287

=== Wireless activity LED ===

does not turn on at all

doesn't seem to flicker properly.

== Power consumption ==

Gutsy is the first version of Ubuntu to feature a tickless kernel (i386 only, not in AMD64 yet). Power consumption
can be monitored using the powertop tool under Ubuntu and using Lenovo battery monitor
under Windows.

$ sudo apt-get install powertop
$ sudo powertop

I couldn't find any difference in power consumption between the i386 tickless kernel (even with 70ms average sleep in C4)
and AMD64 kernel (2ms average sleep in C4). It would be expected that considerably less power would be consumed for the
i386 tickless kernel.

There is also a graph available by Right-clicking on the battery icon and selecting Power History.

These are the figures measured on a T61 15.4" 1680x1050 screen 7300 processor (2GHz) 2GB RAM, Intel X3100 graphics
with 4965 wifi, Bluetooth and UWB.

{| border=1 cellpadding=5
|-
| 12.3W
| Windows XP Pro, all radios on, about 50% brightness
|-
| 16.7W
| Gutsy, all radios on, 50% brightness
|-
| 19.6W
| Gutsy, all radios on, 100% brightness
|-
| 14.2W
| Gutsy, all radios on, 10% brightness
|-
| -1.0W
| Turning the physical radio switch to off on the front reduces power consumption by 1 watt.
|}

Adding the Nvidia card increases the laptops power requirements.

These are the figures measured on a T61 14" 1440x900 screen 2.2ghz Core2Duo 2GB RAM, Nvidia 140m video, IWL4965 wifi and Bluetooth (Disabled):

{| border=1 cellpadding=5
|-
| 18.3W
| Gutsy, all radios on, 50% brightness
|-
| 19.4W
| Gutsy, all radios on, 100% brightness
|-
| 16.0W
| Gutsy, all radios on, 10% brightness
|-
|}

[[Category: T61]] [[Category: Ubuntu 7.10]]

Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61

2007-10-27T01:48:45Z

Pascal: /* Wireless USB/UWB */

==Introduction==

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

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

==Installation Notes ==

*If booting with the live CD gives you a blank screen you should select the "Safe Graphics" menu choice.

== Display/Video ==

=== Accelerated Video and Desktop Effects ===
'''Intel''' 2D and 3D accelerated video work out of the box.

Due to [https://bugs.launchpad.net/xorg-server/+bug/111257 | bug 111257], compiz is disabled on the Intel i965 based video cards. To fix it, download this file[http://www.fileden.com/files/2007/9/28/1467484/compizubuntuintel.zip], unzip it, and follow the instructions in "description and README."

''Note: If you enable Compiz on an Intel card there will be issues with viewing media files, please see the bug report above for details''

'''Nvidia''' 2D video works out of the box, to enable accelerated 3D support click System->Administration->Restricted Drivers Manager {{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 Synaptics and the Restricted Drivers Manager}}

===Multiple Monitors===

If you previously used Xinerama this is no longer a supported option, you should use one of the tools described below to configure dual displays.

'''Nvidia N140m:'''

When using the default drivers (The open source "nv" drivers) you can use Administration->"Screens and Graphics" to setup the second monitor

Using the proprietary drivers you must use the Nvidia tool located at Applications->System Tools-> Nvidia X Server Settings. Note:
Twinview works but a movie will span both the laptop screen and second monitor or projector.

'''Intel X3100:'''

Plugging in an external monitor works, but is a clone of the built-in LCD by default. Using the Screens and Graphics tool located under Administration you can setup the second monitor as an extension of the existing screen or a clone for presentations.

'''Setting up dual monitors via the command line'''

If you like doing it via the command line and are using the Intel drivers or the open-source "nv" driver you can use this example (''Note all this should be possible using the Screens and Graphics tool so only make this change if you prefer the command line method''):

This is an example for a 1680x1050 built-in LCD and a 1600x1200 external LCD:
Add a "Virtual 3280 1200" line in the Display SubSection of the Screen Section in your xorg.conf:

Exit to a virtual terminal (press: ctrl-alt-F1), login and type the following:

{{cmdroot|sudo /etc/init.d/gdm stop}}

{{cmdroot|xrandr --output LVDS --auto}}

To set the built-in LCD to ouput 1680x1050

{{cmdroot|xrandr --output VGA --right-of LVDS}}

To extend the desktop

=== Fonts on High-Res Screens ===

On high-res screens (e.g. 15" 1680x1050), some users consider the default fonts too be too large ([https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/99145 Launchpad bug report]). You can fix this by following these steps:

# Open System->Preferences->Appearance
# Select the "Fonts" tab
# Click the "Details" button (lower right)
# Adjust the Resolution down to 96dpi
# Make sure you have Subpixel (LCD) Smoothing enabled
# Save the preferences

If you also want small fonts on the GDM login window, you can do this:

# Open System->Administration->Login Window
# Select the 'Security' tab
# Click the 'Configure X-Server' button
# Append '-dpi 96' (without quotes) to the text in the 'Command' field
# Reboot the computer.

=== Brightness ===
====Intel X3100:====
The brightness controls should work out of the box on a fresh install.

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

== Audio ==

=== Inextricably Linked to the Modem ===
Make sure that you have the modem enabled in the BIOS. If it is disabled, you may discover (with much consternation) that your audio is also disabled. In this situation, your drivers may still load, but you will get an error message whenever you try to play audio.

After trying all of the ALSA related fixes for this machine, with no love, I remembered what a colleague had said about his T60, and tried this on a hunch. Blammo, it worked!

===Enabling Audio controls===

By default, the sound may be disabled and the volume control buttons on the laptop (up by the ThinkVantage button) and the volume control applet (up by the clock) will not control the speaker volume (they actually control the microphone!). https://bugs.launchpad.net/ubuntu/+bug/136287
this bug report links to a fixed version from an Ubuntu dev a fixed version is available
To fix this:

# Right-click on the volume control applet (by the clock) and select "Open Volume Control"
# In the "Switches" tab, make sure "Headphone" and "Speaker" are both checked.
# Close the Volume control.
# Right-click on the volume control applet again and select "Preferences".
# Make sure the device is set to "HDA Intel (Alsa mixer)" and highlight the "PCM" option.
# Close the preferences.
# Select System->Preferences->Sound.
# In the "Default Mixer Tracks" section, make sure "PCM" is highlighted.
# Close the sound preferences.

You should now hear sound and be able to control the volume using the laptop buttons or volume applet.

A recent BIOS update [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-67989] fixes the mute button, you can then configure it to mute/unmute audio in Keyboard Shortcuts.

===Microphone===

There have been reports that the microphone may not work, please add your input to the talk page [http://www.thinkwiki.org/wiki/Talk:Installing_Ubuntu_7.10_%28Gutsy_Gibbon%29_on_a_ThinkPad_T61#Microphone] and update this section when a consensus on the problem and solution has been reached.

===Sound Cracking===

There have been intermittent reports of users experiencing cracking when listening to audio. Here are a few possible solutions:

* Try to switch to the OSS driver in system => preference => sound => devices => Music and movies, select OSS - Open sound system (instead of ALSA)

* If this issue is only occurring for Rhythmbox go to Edit > Preferences > Playback > and Check "Use Crossfading Backend". Restart Rhythmbox and you should have better audio quality.

* Check that the microphone is muted and modify your mixer settings by moving items like PCM down halfway and see if the cracking goes away.

===Hissing===
Some users experience hissing during playback, and even when idle. To solve this mute the microphone when it is not in use:

# Run "alsamixer".
# Arrow over to "Mic", and hit "M" to mute.
# Arrow over to the first "Docking", and hit "M" to mute.
# Arrow to the first "Internal", and hit "M" to mute.

Now, make sure that "Headphone" and/or "Speaker" are _not_ muted, and that "PCM" is at a reasonable level (say ~70) so you don't make your ears bleed, and try playing something back. ''(<Esc> will exit alsamixer)''

== Modem ==

The modem works with the Linuxant drivers available at http://www.linuxant.com

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

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.

== Fingerprint Reader ==

The reader works with ThinkFinger. General instructions available [http://www.thinkwiki.org/wiki/Integrated_Fingerprint_Reader here] and [https://wiki.ubuntu.com/ThinkFinger here].
Instructions in French available at http://doc.ubuntu-fr.org/materiel/thinkfinger

Note that ThinkFinger in it's current version does not work with KDE and Kubuntu in any way (it crashes KDM and is not integrated at all).

Prebuilt packages are available from jldugger using Launchpad's PPA:

Add the thinkfinger package repository by creating {{path|/etc/apt/sources.list.d/thinkfinger.list}} with these two lines:

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

Then update the package database and install packages:

{{cmduser|sudo apt-get update}}
{{cmduser|sudo apt-get install libpam-thinkfinger libthinkfinger-dev libthinkfinger-doc libthinkfinger0 thinkfinger-tools}}

After the package is installed add the following two lines to {{path|/etc/pam.d/common-auth}}

auth sufficient pam_thinkfinger.so
auth required pam_unix.so try_first_pass

Edit {{path|/etc/modules}} and add the following line:

uinput

Load the module manually for this session:

{{cmduser| sudo modprobe uinput}}

Summary:
* Recording fingerprints works
* Login works
* The password must be entered to unlock a locked screensaver
* sudo works
* gksu and gksudo hang : for example it is necessary to run synaptic twice and enter your password upon failure. To be able to use the Finger print reader in the session subsequently, kill the hanging gksu/gksudo process. A workaround is editing the Gnome System Menu (alacarte) to specify sudo instead of gksu/gksudo for the launching command and choose type "Application in Terminal" : this opens an extra terminal window for each superuser application you want to use though.

== Trackpad scrolling ==

Trackpad scrolling works out of the box in the standard thinkpad way: Slide your finger up and down the very right edge of the trackpad.
Note that /etc/X11/xorg.conf will be changed and the edge scrolling will be disabled after running nvidia-xconfig , copy the trackpad section from the backup of xorg.conf

To enable using the middle mouse button to scroll, add the following lines to the "Configured Mouse" section in
{{path|/etc/X11/xorg.conf}}:

Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"

== Hibernate/Suspend ==

=== Blank screen fix for intel graphics cards===

This fix is for Intel Graphics Cards only.

You may get a blank screen when resuming from suspend or hibernate ([https://bugs.launchpad.net/ubuntu/+bug/134391 Launchpad bug report]). If so, try editing {{path|/boot/grub/menu.lst}}, adding "acpi_sleep=s3_bios" (no quotes) to the "defoptions" list so that it looks something like this:

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash '''acpi_sleep=s3_bios'''

Once you have edited the line and added the acpi_sleep parameter, you need to run

$ sudo update-grub

Note that if you get the blank screen upon resume, a quick-fix is to switch to a console (Ctrl-Alt-F1) and then back to X (Ctrl-Alt-F7). This will usually bring the display back to life. However, the long-term fix is to add the acpi_sleep parameter as shown above.

=== How to Suspend with nVidia 140m/570m ===

The suspend to RAM will work with the nVidia card and the proprietary drivers, but it requires some file editing. It did not work for me out of the box. Using the package manager, download and install the latest nVidia drivers (100.14.19+2.6.2.4-12.4 at time of writing). I also had to use the 2.6.22-12-generic kernel image (the 2.6.22-13 image did not work with this driver --- I'm assuming it has to match wit the nVidia version, but I am not an expert). (Note: I am using KDE. I would think these fixes would work for gnome as well, but someone else would have to test them.)

Once you have it installed and working, you have to make a change to {{path|/etc/default/acpi-support}}. Open the file in your favorite editor and change the following lines:

$ sudo nano /etc/default/acpi-support

{{path|/etc/default/acpi-support}}
# Should we save and restore state using the VESA BIOS Extensions?
SAVE_VBE_STATE=false
...
# Should we attempt to warm-boot the video hardware on resume?
POST_VIDEO=false
...
# Set the following to "platform" if you want to use ACPI to shut down
# your machine on hibernation
HIBERNATE_MODE=platform

This allowed me to suspend and resume, but after two suspends the wireless wouldn't work anymore. Theoretically, ACPI unloads the network drivers before suspending, but it doesn't seem to work correctly so I added these to the blacklist modules manually (in the same file as above:

{{path|/etc/default/acpi-support}}
# Add modules to this list to have them removed before suspend and reloaded
# on resume. An example would be MODULES="em8300 yenta_socket"
#
# Note that network cards and USB controllers will automatically be unloaded
# unless they're listed in MODULES_WHITELIST
MODULES="iwl4965 iwlwifi_mac80211 cfg80211"

Your wifi modules may be different. (I have the intel AGN wireless card -- I don't know if these modules are different for other cards.)

This allows me to suspend to ram; I haven't had any problems with it so far. I haven't gotten hibernate (suspend to disk) working, so there may be additional things you need to do for that. (I think part of my problem is that I don't have enough swap, but I don't care enough to actually fix it.)

/*The fix does not work for me. I have a T61 7664-17U(NVS 140m, 4965agn). The computers suspend, but when it wakes up it hangs up and I have to pull out the battery to restart it.*/

General hint: Do not install the package "hibernate" or "uswsusp" or the gnome-power-manager will fail to suspend/hibernate your computer. If you have installed the package don't forget to purge the configuration. (sudo apt-get remove hibernate --purge, uswsusp resp.)

== Items that work out of the box ==

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

'''Nvidia:''' 2D works, 3D requires the installation of the proprietary drivers

'''Wireless:''' Atheros and Intel cards both tested.

'''Bluetooth:''' Tested with both a bluetooth headset and an HTC 8525

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

'''Firewire''' Tested with hard drive

'''Wireless switch'''

'''4-in-1 card reader'''

'''Webcam'''

'''Headphones''' You may need to enable Headphone out: Right-click on the volume control and select open volume control. Click the switches tab and then check the headphones box.

'''Keyboard Shortcuts:'''
* Fn-PgUp activates/deactivates the thinklight
* Fn-Up will trigger stop on a media player
* Fn-Down will toggle pause and play on a media player
* Fn-Left/Right go to prev/next tracks on a media player
* Fn-F2 properly locks the screen
* Fn-F3 shows remaining battery >>does not work on all machines<<
* Fn-F4 suspends (to ram)
* Fn-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

'''Docking Stations:'''

All docking station models should work and the following features have been tested:

* DVI or Analog video: You can switch to it using "Administration->Screens and Graphics", if you are using the proprietary Nvidia drivers you must use the Nvidia Control Panel.

* Network Pass-through

* Modem Pass-through

* USB ports: Connected upon docking

* PS/2 Ports

== Items that don't work ==

=== Wireless USB/UWB ===

the two usb ports on the left side of the computer fail to connect storage devices during a session but will load them at boot up.

the one usb port on the right side consistently works.

I do not have this problem and nobody else has reported it that I have seen, you may have a bad set of ports. Maybe we should move this to the talk page to attempt to troubleshoot it? --[[User:Darrena|Darrena]] 02:49, 26 October 2007 (UTC)

I also have this problem. It seems to be the bug mentioned in the section below. This is not even about wireless usb --Pascal, 27-10-2007

=== Interrupt problem ===
* https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/126369
* USB ports can end up temporarily disabled
* Wifi can break
* integrated cardreader can be disabled
* bluetooth can be disabled
* Setting IRQ's to "Auto" from factory default of "11" in the BIOS seems to help some people.

=== Volume keys ===

* mute is inconsistent
1. sometimes fails to work at all
2. sometimes works but doesn't display the volume box on the screen
* unmute does not work --to unmute one must use the volume up or down buttons
* Control mic instead of speakers by default
* https://bugs.launchpad.net/ubuntu/+bug/136287

=== Wireless activity LED ===

does not turn on at all

doesn't seem to flicker properly.

== Power consumption ==

Gutsy is the first version of Ubuntu to feature a tickless kernel (i386 only, not in AMD64 yet). Power consumption
can be monitored using the powertop tool under Ubuntu and using Lenovo battery monitor
under Windows.

$ sudo apt-get install powertop
$ sudo powertop

I couldn't find any difference in power consumption between the i386 tickless kernel (even with 70ms average sleep in C4)
and AMD64 kernel (2ms average sleep in C4). It would be expected that considerably less power would be consumed for the
i386 tickless kernel.

There is also a graph available by Right-clicking on the battery icon and selecting Power History.

These are the figures measured on a T61 15.4" 1680x1050 screen 7300 processor (2GHz) 2GB RAM, Intel X3100 graphics
with 4965 wifi, Bluetooth and UWB.

{| border=1 cellpadding=5
|-
| 12.3W
| Windows XP Pro, all radios on, about 50% brightness
|-
| 16.7W
| Gutsy, all radios on, 50% brightness
|-
| 19.6W
| Gutsy, all radios on, 100% brightness
|-
| 14.2W
| Gutsy, all radios on, 10% brightness
|-
| -1.0W
| Turning the physical radio switch to off on the front reduces power consumption by 1 watt.
|}

Adding the Nvidia card increases the laptops power requirements.

These are the figures measured on a T61 14" 1440x900 screen 2.2ghz Core2Duo 2GB RAM, Nvidia 140m video, IWL4965 wifi and Bluetooth (Disabled):

{| border=1 cellpadding=5
|-
| 18.3W
| Gutsy, all radios on, 50% brightness
|-
| 19.4W
| Gutsy, all radios on, 100% brightness
|-
| 16.0W
| Gutsy, all radios on, 10% brightness
|-
|}

[[Category: T61]] [[Category: Ubuntu 7.10]]

Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61

2007-10-27T01:39:17Z

Pascal: /* Wireless USB/UWB */

==Introduction==

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

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

==Installation Notes ==

*If booting with the live CD gives you a blank screen you should select the "Safe Graphics" menu choice.

== Display/Video ==

=== Accelerated Video and Desktop Effects ===
'''Intel''' 2D and 3D accelerated video work out of the box.

Due to [https://bugs.launchpad.net/xorg-server/+bug/111257 | bug 111257], compiz is disabled on the Intel i965 based video cards. To fix it, download this file[http://www.fileden.com/files/2007/9/28/1467484/compizubuntuintel.zip], unzip it, and follow the instructions in "description and README."

''Note: If you enable Compiz on an Intel card there will be issues with viewing media files, please see the bug report above for details''

'''Nvidia''' 2D video works out of the box, to enable accelerated 3D support click System->Administration->Restricted Drivers Manager {{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 Synaptics and the Restricted Drivers Manager}}

===Multiple Monitors===

If you previously used Xinerama this is no longer a supported option, you should use one of the tools described below to configure dual displays.

'''Nvidia N140m:'''

When using the default drivers (The open source "nv" drivers) you can use Administration->"Screens and Graphics" to setup the second monitor

Using the proprietary drivers you must use the Nvidia tool located at Applications->System Tools-> Nvidia X Server Settings. Note:
Twinview works but a movie will span both the laptop screen and second monitor or projector.

'''Intel X3100:'''

Plugging in an external monitor works, but is a clone of the built-in LCD by default. Using the Screens and Graphics tool located under Administration you can setup the second monitor as an extension of the existing screen or a clone for presentations.

'''Setting up dual monitors via the command line'''

If you like doing it via the command line and are using the Intel drivers or the open-source "nv" driver you can use this example (''Note all this should be possible using the Screens and Graphics tool so only make this change if you prefer the command line method''):

This is an example for a 1680x1050 built-in LCD and a 1600x1200 external LCD:
Add a "Virtual 3280 1200" line in the Display SubSection of the Screen Section in your xorg.conf:

Exit to a virtual terminal (press: ctrl-alt-F1), login and type the following:

{{cmdroot|sudo /etc/init.d/gdm stop}}

{{cmdroot|xrandr --output LVDS --auto}}

To set the built-in LCD to ouput 1680x1050

{{cmdroot|xrandr --output VGA --right-of LVDS}}

To extend the desktop

=== Fonts on High-Res Screens ===

On high-res screens (e.g. 15" 1680x1050), some users consider the default fonts too be too large ([https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/99145 Launchpad bug report]). You can fix this by following these steps:

# Open System->Preferences->Appearance
# Select the "Fonts" tab
# Click the "Details" button (lower right)
# Adjust the Resolution down to 96dpi
# Make sure you have Subpixel (LCD) Smoothing enabled
# Save the preferences

If you also want small fonts on the GDM login window, you can do this:

# Open System->Administration->Login Window
# Select the 'Security' tab
# Click the 'Configure X-Server' button
# Append '-dpi 96' (without quotes) to the text in the 'Command' field
# Reboot the computer.

=== Brightness ===
====Intel X3100:====
The brightness controls should work out of the box on a fresh install.

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

== Audio ==

=== Inextricably Linked to the Modem ===
Make sure that you have the modem enabled in the BIOS. If it is disabled, you may discover (with much consternation) that your audio is also disabled. In this situation, your drivers may still load, but you will get an error message whenever you try to play audio.

After trying all of the ALSA related fixes for this machine, with no love, I remembered what a colleague had said about his T60, and tried this on a hunch. Blammo, it worked!

===Enabling Audio controls===

By default, the sound may be disabled and the volume control buttons on the laptop (up by the ThinkVantage button) and the volume control applet (up by the clock) will not control the speaker volume (they actually control the microphone!). https://bugs.launchpad.net/ubuntu/+bug/136287
this bug report links to a fixed version from an Ubuntu dev a fixed version is available
To fix this:

# Right-click on the volume control applet (by the clock) and select "Open Volume Control"
# In the "Switches" tab, make sure "Headphone" and "Speaker" are both checked.
# Close the Volume control.
# Right-click on the volume control applet again and select "Preferences".
# Make sure the device is set to "HDA Intel (Alsa mixer)" and highlight the "PCM" option.
# Close the preferences.
# Select System->Preferences->Sound.
# In the "Default Mixer Tracks" section, make sure "PCM" is highlighted.
# Close the sound preferences.

You should now hear sound and be able to control the volume using the laptop buttons or volume applet.

A recent BIOS update [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-67989] fixes the mute button, you can then configure it to mute/unmute audio in Keyboard Shortcuts.

===Microphone===

There have been reports that the microphone may not work, please add your input to the talk page [http://www.thinkwiki.org/wiki/Talk:Installing_Ubuntu_7.10_%28Gutsy_Gibbon%29_on_a_ThinkPad_T61#Microphone] and update this section when a consensus on the problem and solution has been reached.

===Sound Cracking===

There have been intermittent reports of users experiencing cracking when listening to audio. Here are a few possible solutions:

* Try to switch to the OSS driver in system => preference => sound => devices => Music and movies, select OSS - Open sound system (instead of ALSA)

* If this issue is only occurring for Rhythmbox go to Edit > Preferences > Playback > and Check "Use Crossfading Backend". Restart Rhythmbox and you should have better audio quality.

* Check that the microphone is muted and modify your mixer settings by moving items like PCM down halfway and see if the cracking goes away.

===Hissing===
Some users experience hissing during playback, and even when idle. To solve this mute the microphone when it is not in use:

# Run "alsamixer".
# Arrow over to "Mic", and hit "M" to mute.
# Arrow over to the first "Docking", and hit "M" to mute.
# Arrow to the first "Internal", and hit "M" to mute.

Now, make sure that "Headphone" and/or "Speaker" are _not_ muted, and that "PCM" is at a reasonable level (say ~70) so you don't make your ears bleed, and try playing something back. ''(<Esc> will exit alsamixer)''

== Modem ==

The modem works with the Linuxant drivers available at http://www.linuxant.com

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

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.

== Fingerprint Reader ==

The reader works with ThinkFinger. General instructions available [http://www.thinkwiki.org/wiki/Integrated_Fingerprint_Reader here] and [https://wiki.ubuntu.com/ThinkFinger here].
Instructions in French available at http://doc.ubuntu-fr.org/materiel/thinkfinger

Note that ThinkFinger in it's current version does not work with KDE and Kubuntu in any way (it crashes KDM and is not integrated at all).

Prebuilt packages are available from jldugger using Launchpad's PPA:

Add the thinkfinger package repository by creating {{path|/etc/apt/sources.list.d/thinkfinger.list}} with these two lines:

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

Then update the package database and install packages:

{{cmduser|sudo apt-get update}}
{{cmduser|sudo apt-get install libpam-thinkfinger libthinkfinger-dev libthinkfinger-doc libthinkfinger0 thinkfinger-tools}}

After the package is installed add the following two lines to {{path|/etc/pam.d/common-auth}}

auth sufficient pam_thinkfinger.so
auth required pam_unix.so try_first_pass

Edit {{path|/etc/modules}} and add the following line:

uinput

Load the module manually for this session:

{{cmduser| sudo modprobe uinput}}

Summary:
* Recording fingerprints works
* Login works
* The password must be entered to unlock a locked screensaver
* sudo works
* gksu and gksudo hang : for example it is necessary to run synaptic twice and enter your password upon failure. To be able to use the Finger print reader in the session subsequently, kill the hanging gksu/gksudo process. A workaround is editing the Gnome System Menu (alacarte) to specify sudo instead of gksu/gksudo for the launching command and choose type "Application in Terminal" : this opens an extra terminal window for each superuser application you want to use though.

== Trackpad scrolling ==

Trackpad scrolling works out of the box in the standard thinkpad way: Slide your finger up and down the very right edge of the trackpad.
Note that /etc/X11/xorg.conf will be changed and the edge scrolling will be disabled after running nvidia-xconfig , copy the trackpad section from the backup of xorg.conf

To enable using the middle mouse button to scroll, add the following lines to the "Configured Mouse" section in
{{path|/etc/X11/xorg.conf}}:

Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"

== Hibernate/Suspend ==

=== Blank screen fix for intel graphics cards===

This fix is for Intel Graphics Cards only.

You may get a blank screen when resuming from suspend or hibernate ([https://bugs.launchpad.net/ubuntu/+bug/134391 Launchpad bug report]). If so, try editing {{path|/boot/grub/menu.lst}}, adding "acpi_sleep=s3_bios" (no quotes) to the "defoptions" list so that it looks something like this:

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash '''acpi_sleep=s3_bios'''

Once you have edited the line and added the acpi_sleep parameter, you need to run

$ sudo update-grub

Note that if you get the blank screen upon resume, a quick-fix is to switch to a console (Ctrl-Alt-F1) and then back to X (Ctrl-Alt-F7). This will usually bring the display back to life. However, the long-term fix is to add the acpi_sleep parameter as shown above.

=== How to Suspend with nVidia 140m/570m ===

The suspend to RAM will work with the nVidia card and the proprietary drivers, but it requires some file editing. It did not work for me out of the box. Using the package manager, download and install the latest nVidia drivers (100.14.19+2.6.2.4-12.4 at time of writing). I also had to use the 2.6.22-12-generic kernel image (the 2.6.22-13 image did not work with this driver --- I'm assuming it has to match wit the nVidia version, but I am not an expert). (Note: I am using KDE. I would think these fixes would work for gnome as well, but someone else would have to test them.)

Once you have it installed and working, you have to make a change to {{path|/etc/default/acpi-support}}. Open the file in your favorite editor and change the following lines:

$ sudo nano /etc/default/acpi-support

{{path|/etc/default/acpi-support}}
# Should we save and restore state using the VESA BIOS Extensions?
SAVE_VBE_STATE=false
...
# Should we attempt to warm-boot the video hardware on resume?
POST_VIDEO=false
...
# Set the following to "platform" if you want to use ACPI to shut down
# your machine on hibernation
HIBERNATE_MODE=platform

This allowed me to suspend and resume, but after two suspends the wireless wouldn't work anymore. Theoretically, ACPI unloads the network drivers before suspending, but it doesn't seem to work correctly so I added these to the blacklist modules manually (in the same file as above:

{{path|/etc/default/acpi-support}}
# Add modules to this list to have them removed before suspend and reloaded
# on resume. An example would be MODULES="em8300 yenta_socket"
#
# Note that network cards and USB controllers will automatically be unloaded
# unless they're listed in MODULES_WHITELIST
MODULES="iwl4965 iwlwifi_mac80211 cfg80211"

Your wifi modules may be different. (I have the intel AGN wireless card -- I don't know if these modules are different for other cards.)

This allows me to suspend to ram; I haven't had any problems with it so far. I haven't gotten hibernate (suspend to disk) working, so there may be additional things you need to do for that. (I think part of my problem is that I don't have enough swap, but I don't care enough to actually fix it.)

/*The fix does not work for me. I have a T61 7664-17U(NVS 140m, 4965agn). The computers suspend, but when it wakes up it hangs up and I have to pull out the battery to restart it.*/

General hint: Do not install the package "hibernate" or "uswsusp" or the gnome-power-manager will fail to suspend/hibernate your computer. If you have installed the package don't forget to purge the configuration. (sudo apt-get remove hibernate --purge, uswsusp resp.)

== Items that work out of the box ==

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

'''Nvidia:''' 2D works, 3D requires the installation of the proprietary drivers

'''Wireless:''' Atheros and Intel cards both tested.

'''Bluetooth:''' Tested with both a bluetooth headset and an HTC 8525

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

'''Firewire''' Tested with hard drive

'''Wireless switch'''

'''4-in-1 card reader'''

'''Webcam'''

'''Headphones''' You may need to enable Headphone out: Right-click on the volume control and select open volume control. Click the switches tab and then check the headphones box.

'''Keyboard Shortcuts:'''
* Fn-PgUp activates/deactivates the thinklight
* Fn-Up will trigger stop on a media player
* Fn-Down will toggle pause and play on a media player
* Fn-Left/Right go to prev/next tracks on a media player
* Fn-F2 properly locks the screen
* Fn-F3 shows remaining battery >>does not work on all machines<<
* Fn-F4 suspends (to ram)
* Fn-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

'''Docking Stations:'''

All docking station models should work and the following features have been tested:

* DVI or Analog video: You can switch to it using "Administration->Screens and Graphics", if you are using the proprietary Nvidia drivers you must use the Nvidia Control Panel.

* Network Pass-through

* Modem Pass-through

* USB ports: Connected upon docking

* PS/2 Ports

== Items that don't work ==

=== Wireless USB/UWB ===

the two usb ports on the left side of the computer fail to connect storage devices during a session but will load them at boot up.

the one usb port on the right side consistently works.

I do not have this problem and nobody else has reported it that I have seen, you may have a bad set of ports. Maybe we should move this to the talk page to attempt to troubleshoot it? --[[User:Darrena|Darrena]] 02:49, 26 October 2007 (UTC)

I also have this problem. I was thinking I had bad ports, but maybe not. --Pascal, 27-10-2007

=== Interrupt problem ===
* https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/126369
* USB ports can end up temporarily disabled
* Wifi can break
* integrated cardreader can be disabled
* bluetooth can be disabled
* Setting IRQ's to "Auto" from factory default of "11" in the BIOS seems to help some people.

=== Volume keys ===

* mute is inconsistent
1. sometimes fails to work at all
2. sometimes works but doesn't display the volume box on the screen
* unmute does not work --to unmute one must use the volume up or down buttons
* Control mic instead of speakers by default
* https://bugs.launchpad.net/ubuntu/+bug/136287

=== Wireless activity LED ===

does not turn on at all

doesn't seem to flicker properly.

== Power consumption ==

Gutsy is the first version of Ubuntu to feature a tickless kernel (i386 only, not in AMD64 yet). Power consumption
can be monitored using the powertop tool under Ubuntu and using Lenovo battery monitor
under Windows.

$ sudo apt-get install powertop
$ sudo powertop

I couldn't find any difference in power consumption between the i386 tickless kernel (even with 70ms average sleep in C4)
and AMD64 kernel (2ms average sleep in C4). It would be expected that considerably less power would be consumed for the
i386 tickless kernel.

There is also a graph available by Right-clicking on the battery icon and selecting Power History.

These are the figures measured on a T61 15.4" 1680x1050 screen 7300 processor (2GHz) 2GB RAM, Intel X3100 graphics
with 4965 wifi, Bluetooth and UWB.

{| border=1 cellpadding=5
|-
| 12.3W
| Windows XP Pro, all radios on, about 50% brightness
|-
| 16.7W
| Gutsy, all radios on, 50% brightness
|-
| 19.6W
| Gutsy, all radios on, 100% brightness
|-
| 14.2W
| Gutsy, all radios on, 10% brightness
|-
| -1.0W
| Turning the physical radio switch to off on the front reduces power consumption by 1 watt.
|}

Adding the Nvidia card increases the laptops power requirements.

These are the figures measured on a T61 14" 1440x900 screen 2.2ghz Core2Duo 2GB RAM, Nvidia 140m video, IWL4965 wifi and Bluetooth (Disabled):

{| border=1 cellpadding=5
|-
| 18.3W
| Gutsy, all radios on, 50% brightness
|-
| 19.4W
| Gutsy, all radios on, 100% brightness
|-
| 16.0W
| Gutsy, all radios on, 10% brightness
|-
|}

[[Category: T61]] [[Category: Ubuntu 7.10]]

Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T61

2007-09-29T13:24:42Z

Pascal: /* ThinkFinger */

On the T61, [[Installing_Ubuntu_7.10_(Gutsy_Gibbon)_Tribe_5_on_a_ThinkPad_T61|Ubuntu 7.10 (Gutsy Gibbon)]] is recommended instead of 7.04 because video drivers and wifi, among other issues, work by default.
recomended

===My DVD drive/CD burner/DVD burner doesn't work (Solved)===

Follow these instructions to enable your [http://en.wikipedia.org/wiki/Optical_drive optical drive]: 
1) Reboot your T61. Press the ThinkVantage button quickly when you see the ThinkPad screen and then press F1 enter [http://en.wikipedia.org/wiki/BIOS BIOS]. 
2) In BIOS, select Configure -> Serial ATA. 
3) Now, select Compatibility instead of AHCI. 
4) Exit BIOS and start your computer normally. 
5) Go to Places -> Computer, right-click your CD-ROM/DVD/etc. drive, and select Properties. Then, go to Drive -> Settings. Set the mount point to ''cdrom'' (regardless of whether it's a CD-ROM drive, DVD drive, etc.).

----

At first, the Ubuntu Live CD would not start at all, this seems to be a problem with the SATA AHCI driver. I had to go into the BIOS and change the SATA driver from ACHI to compatibility (What is the difference? Am I loosing performance?).

----

After you've installed and booted, try the advice from [[Problems_with_SATA_and_Linux]]. Do this:
'''# echo options libata atapi_enabled=1>/etc/modprobe.d/atapienable && update-initramfs -u'''
Then try turning AHCI back on in the BIOS. On a custom-built 2.6.21.5 kernel, my DVD drive appears as /dev/hda and DMA works.
--[[User:Kc8tbe|Kc8tbe]] 12:45, 1 July 2007 (UTC)

If your DVD drive does not appear, modprobe pata-jmicron and ide-generic.
--[[User:Antikristian|Antikristian]] 01:23, 30 July 2007 (UTC)

===NVIDIA Quadro NVS 140M (Solved)===
After initial issues like those explained above in the SATA Issues, I received the xorg error 'fatal error: no screens found'. I was able to boot into Safe Graphics Mode and run the installer, though I had to move both window manager bars to see enough of the install window to use it.

Alternatively, you can download the drivers via wget in a console. Take care to follow the instructions in
[http://www.nvnews.net/vbulletin/showthread.php?t=72490 the NVidia Forum] and uninstall all the packages wit apt-get remove, as described.
Then run the nvidia installer.

Remember that, after you upgrade the kernel, you also have to re-install the drivers.

After installing the NVIDIA drivers, your laptop may not wake after suspend or hibernation. I followed these instructions to fix it [https://help.ubuntu.com/community/NvidiaLaptopBinaryDriverSuspend Ubuntu Community Help].

====Alternative NVIDIA driver installation====
Instead of installing the NVIDIA drivers manually as described above, you can try using [http://www.albertomilone.com/nvidia_scripts1.html Envy]. It automatically installs the latest NVIDIA drivers, and cleans up any previous installations.

=== Intel Graphics Media Accelerator X3100 (Chipset GM965) (Solved)===
After that the CD seemed to boot but the screen was just garbage [http://shadowarts.nonlogic.org/projects/thinkpad/screen_garbage.jpg Picture]. In order to get around that issue I had to go back and download the Alternate CD, which allows you to install in text only mode. From here, the text-only install went okay. Changing the VGA settings on the regular CD worked for me.

When I booted up after the installation, I was still getting the same garbage on the screen. To resolve this I edited my [http://shadowarts.nonlogic.org/projects/thinkpad/xorg.conf xorg.conf] file as shown. I also had to install the latest kernel for Feisty, as the one off of the install disk did have have /dev/agpgart. And I could then use X11. There were still some issues however. The screen seemed somewhat fuzzy. This was a little more challenging of a fix... I found [http://www.spinics.net/lists/xorg/msg25099.html this] mailing list posting, according to it, there was a small glitch in the driver. To fix it:
<pre>
apt-get source xserver-xorg-video-intel
cd xserver-xorg-video-intel-1.9.94/
vim src/i830_lvds.c
Goto line 230 and delete (PFIT_ENABLE | VERT_AUTSCALE ....);, replacing it with 0; then quit vim
dpkg-buildpackage -rfakeroot -uc -b
cd ..
dpkg -i xserver-xorg-video-intel_1.9.94-lubuntu3_amd64.deb (wont be amd64 with a 32-bit install)
</pre>
Now reboot your computer, and it should work. **NOTE: For some reason just restarting X didn't fix it, seems like you must reboot.** At this point you should have a nice, crisp display.

I am still working on aiglx and compiz (switching desktops on a cube doesnt seem to work, though I have some ideas...). There are some issues with OpenGL apps freezing Xorg as well, but the standard 2D desktop works flawlessly.
----
It doesn't seem to be necessary to modify the soruce of xserver-xorg-video-intel anymore, but 3D-acceleration doesn't seem to be stable yet and kdm occasionally needs to be restarted after a login attempt.--[[User:Kc8tbe|Kc8tbe]] 12:49, 1 July 2007 (UTC)

----
I was able to use the normal feisty install disk by changing the SATA setting in BIOS, then change the resolution to 800x600 prior to install, then sudo apt-get update and upgrade, and then sudo apt-get install xserver-xorg-video-intel, then change xorg.conf to match link above and 2D graphics work fine. Jul 18, 2008 - John E
----

It seems that everything works fine when using "apt pinning" and updating the xserver-xorg-video-intel, mesa and other packages to the versions provided by Gutsy. I did the following and the resolution and Compiz Fusion are working fine at the moment. The original source of the steps described below can be found here: [http://techreport.com/forums/viewtopic.php?p=714998#714998]

'''Instructions:'''
* Make a new file /etc/apt/preferences
* In the preferences file, put:
<pre>
Package: *
Pin: release a=feisty
Pin-Priority: 700

Package: *
Pin: release a=gutsy
Pin-Priority: 200
</pre>
* Now, edit your sources.list and copy the main and restricted (and others if you want) repo lines replacing feisty with gutsy:
<pre>
# original
deb http://archive.ubuntu.com/ubuntu feisty main restricted universe multiverse
deb-src http://security.ubuntu.com/ubuntu feisty main restricted universe multiverse

# your addition
deb http://archive.ubuntu.com/ubuntu gutsy main restricted universe multiverse
deb-src http://security.ubuntu.com/ubuntu gutsy main restricted universe multiverse
</pre>
* Now run:
<pre>
sudo apt-get update
</pre>
{{HINT|If you get an error while trying to update, it may be because your apt cache is too small. To fix this add the following to your "/etc/apt/apt.conf.d/70debconf":
<pre>
APT::Cache-Limit "118388608";
</pre>--[[User:Thefekete|Thefekete]] 04:14, 19 September 2007 (UTC)}}
*Then Run:
<pre>
sudo apt-get -t gutsy install xserver-xorg-video-intel
sudo apt-get -t gutsy install linux
sudo apt-get -t gutsy install libgl1-mesa-dri
</pre>
* Now reboot.

Probably now you have the weird effect that your GUI is scaled wrong and doesn't fill the full width of the monitor. To fix that, open your xorg.conf and make the following changes:
* Add the following section to your xorg.conf
<pre>
Section "Monitor"
Identifier "TVOutput"
Option "Disable" "true"
EndSection
</pre>
* Then in the "Device" section add the following line:
<pre>
Option "monitor-TV" "TVOutput"
</pre>

That should fix the scaling problem and now everything should work fine.
--[[User:Shuk|Shuk]] 02:26, 10 July 2007 (UTC)

{{HINT|If you experience problems with totem or other gstreamer apps crashing, try this:
<pre>
$ gstreamer-properties
</pre>
* Then under the "Video" tab, change the Output Plugin to "X Window System (No Xv)"
This will run the video through you processor, but won't crash gstreamer. --[[User:Thefekete|Thefekete]] 04:14, 19 September 2007 (UTC)}}

===ThinkFinger===
Ubuntu does not come with a package for thinkfinger. Downloading the most recent source and building it was simple enough: Download most recent version (0.3 at time of writing)
<pre>
sudo apt-get install libpam0g-dev libusb-dev
tar xvzf thinkfinger-0.3.tar.gz
cd thinkfinger-0.3/
./configure --with-securedir=/lib/security --with-birdir=/etc/pam_thinkfinger
make -j5 (hey its dual core!)
sudo make install
sudo ldconfig
</pre>

Configuring it is easy as well, open /etc/pam.d/common-auth:
<pre>
auth sufficient pam_thinkfinger.so
auth required pam_unix.so try_first_pass nullok_secure
</pre>

Create the data directory and set your fingerprint:
<pre>
sudo mkdir /etc/pam_thinkfinger
sudo tf-tool --add-user <username>
</pre>

To get be asked to swipe your finger when logging in or sudoing
<pre>
sudo modprobe uinput
</pre>
To make sure it works after reboot add "uinput" to the list in /etc/modules.

It will all be setup. (I found this somewhere on the web, I wish I could give a source but I'm afraid I cant find it, thank you Anonymous!).

===HDAPS===
This seems to be working fine now, I just follow the step on [[How_to_protect_the_harddisk_through_APS]]. Using hdaps-gl does the inverse of the accelerometer, though it's not really a big deal, the harddrive protection should still work.

Assuming that the (improved) hdaps code bundled with tp_smapi is being used, editing the transform_axis function in tp_smapi-0.32/hdaps.c will allow for the proper operation of the accelerometer. Assuming that the accelerometer is rotated 90 degrees from its proper orientation (as it is with the X61), the following code will suffice:

<pre>
static void transform_axes(int *x, int *y)
{
int temp = *x;
*x = -*y;
*y = temp;
}
</pre>

For those paying attention in linear algebra, this corresponds to a linear transformation that rotates a 2D coordinate system 90 degrees.
--[[User:Mbsullivan|Mbsullivan]] 04:21, 27 August 2007 (UTC)

Instead of editing the code, you can just pass the invert=1 parameter when loading the module; modprobe hdaps invert=1
--[[User:Vegar|Vegar]] 14:40, 17 September 2007 (UTC)

===WiFi===
If you have Intel 4965AGN WiFi card, you have to use ndiswrapper OR use backported kernel from Ubuntu Gutsy (Anybody have howto?) and use following:
http://kuscsik.blogspot.com/2007/06/how-to-install-intel-4965-wireless.html

'''Note:'''
Do not use the latest versions of iwlwifi and mac80211. For me with Gutsy mac80211-8.0.2 and iwlwifi-0.0.42 work with the latest firmware. No further modification needed.

If you have the Atheros card, Ubuntu should automatically install madwifi, which works out of the box
----
Works for me with iwlwifi-4965-ucode-4.44.15, iwlwifi-0.0.34, and mac80211-8.0.1. The catch is, you need to patch your kernel with mac80211, which will fail at compile time with the stock Ubuntu sources. Worked for me with vanilla 2.6.21.5 sources patched for tp_smapi and hdaps protect. Make sure to disable CONFIG_NET_WIRELESS_RTNETLINK in your kernel config.

You can download what you need for for iwlwifi and mac80211 from
http://intellinuxwireless.org .--[[User:Kc8tbe|Kc8tbe]] 13:00, 1 July 2007 (UTC)

Works for me with vanilla kernel v2.6.22.1, ucode 4.44.17, iwlwifi 0.1.2 and mac80211 9.0.2. --[[User:Mbsullivan|Mbsullivan]] 13:40, 24 July 2007 (UTC)

You can also use Kernel 2.6.22.9 and Ubuntu Modules 2.6.22.9 from Gutsy and you will not need to compile anything! Works very well.

===Keyboard/Apostrophe issues (Solved)===
When installing with the alternate CD, Ubuntu asks you if your keyboard as a character that appears to be a quotation mark (this character: "). If you're using a US English keyboard, say no; the character is actually an umlaut. [[User:SteveSims|SteveSims]] 02:15, 19 August 2007 (UTC)

My apostrophe key outputs ´ instead of '. I went to System -> Preferences -> Keyboard and could not figure out how to fix it. [[User:SteveSims|SteveSims]] 21:50, 11 August 2007 (UTC)

:Try switching your keyboard layout to US-Classic, and putting it on the top of the list. After you do that, it works perfectly. --[[User:Adamacious|Adamacious]] 04:29, 13 August 2007 (UTC)

::There is no "US Classic" option. Here's what I have: 
[[Image:Keyboard_options.png]] 
[[User:SteveSims|SteveSims]] 02:17, 15 August 2007 (UTC)

:::It started working, even though I changed nothing. I'm running it as a Macintosh US English keyboard. [[User:SteveSims|SteveSims]] 17:20, 15 August 2007 (UTC)

::::Sorry Steve, what you had to do (and what you did) is select US English, as in the header in the list. It doesn't look selectable, but it is.--[[User:Adamacious|Adamacious]] 20:02, 22 August 2007 (UTC)

===Audio===
====Fixed in Gutsy====
As of 29 August 2007 and [https://bugs.launchpad.net/bugs/122560 this issue], the 2.6.22-10 kernel in Gutsy Gibbon supports audio out-of-the-box (as well as WiFi and other things). Installing the Gutsy kernel via apt and rebooting fixed audio for me, both speakers and headphones. Remaining issues:

* The mute button mutes audio, but doesn't unmute. Pressing volume up or down does unmute it, but has no effect on volume.
* KMix's system tray volume control has no effect because it thinks it's setting the headphones while both outputs are using the speaker settings, but opening KMix and setting the PCM volume works. --lgarfiel

====Python script fix (slightly easier fix)====
First, you have to download the source for the [http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.22.5.tar.gz latest Linux kernel] (2.6.22-5 as of August 26th, 2007) and compile it, something most users cannot do. However, you won't have to compile ALSA and its modules from source if you do it this way.

1) Download the [http://launchpadlibrarian.net/8899521/t61_audio_hack.py T61 audio hack] from [[Launchpad]]. Move it to a convenient folder (e.g., not your desktop). 
2) Go to System -> Preferences -> Sessions -> Startup Programs -> Add. 
3) Name it whatever you want. Choose something simple like "Python audio fix." 
4) Go to Command, and enter the following (with quotation marks):
<pre>gksudo <nowiki>"[THE FOLDER THAT T61_AUDIO_HACK.PY IS IN]</nowiki>/t61_audio_hack.py"</pre>
For example, on my computer, I put t61_audio_hack.py into the /fixes folder in my home folder, so I entered:
<pre>sksudo "/home/sims/fixes/t61_audio_hack.py"</pre> into the Command textbox. 
5) Log out, log back in, and type your password quickly when prompted the second time.

References:
[https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/122560 Launchpad Bug #122560]
[https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/133105 Launchpad Bug #133105]

====ALSA driver update (hard fix, recommended for advanced users)====

:'''''Note: This section assumes a high level of technical proficiency. Please fix it.'''''
::*<s>At [http://www.alsa-project.org www.asla-project.org], did you download only alsa-driver-1.0.14? That and alsa-lib-1.0.14a?</s>
:::Download alsa-driver, alsa-kernel, alsa-lib, and alsa-utils, according to [http://alsa.opensrc.org/index.php/AlsaCVS http://alsa.opensrc.org/index.php/AlsaCVS]. Other sources, however, say only the driver is necessary. Perhaps alsa-project.org simply recommends the other two?
::*''How'' did you compile it from source? ''How'' did you add the patch?
::*In short, please explain ''how'' you did these things in addition to just telling us ''what'' you did. I´m not trying to be rude but seriously, not all Linux users are programmers ;). Thanks. [[User:SteveSims|SteveSims]] 22:19, 11 August 2007 (UTC)
After upgrading to 1.0.14 I still had no sound, and this took about a week to solved (though it was so sadly obvious though). Just upgrading to alsa 1.0.14 will not be enough, there were a few patches released right after the release that fix the Thinkpad's. The reason I missed this was because it was the same day so the release of 1.0.14!

---------------------------------------------------------------------------
VERY SIMPLE METHOD OF MAKING SOUND WORK
http://forums.fedoraforum.org/showthread.php?t=159516&page=1&pp=15
Just follow the instructions step by step, except for two small things:
When doing "cp ../patch_analog.c alsa-driver-1.0.14/alsa-kernel/pci/hda/" use "cp ../patch_analog.c alsa-kernel/pci/hda/" instead
Also, when you get to the part about modifying the modprobe.conf file, it doesn't exist in ubuntu. Adding "options snd-hda-intel index=0 model=thinkpad" to any file (even one you make yourself) inside etc/modprobe.d should work. I personally added it to the options file, and it works fine.

-credit for the guide goes to ciphermonk, and credit to the small changes needed to make this work on ubuntu go to my friend John.

-hotkeys control mic volume, not speaker volume for some reason. I do not know how to fix this

-this fix should provide sound for both headphones and speakers.

-this edit by fatalchaos
---------------------------------------------------------------------------------------

First make sure these packages are installed (System -> Administration -> Synaptic Package Manager) : automake, autoconfig, cvs, libtool, python-dev, build-essential

Then download the source code to the alsa-driver and apply these patches: (links to the revisions)

* [http://hg.alsa-project.org/alsa-kernel/rev/958b39f3e8dd Fix Oops with AD1984 thinkpad model]
* [http://hg.alsa-project.org/alsa-kernel/rev/47ca87407c84 Fix AD1984 basic model]
* [http://hg.alsa-project.org/alsa-kernel/rev/ca37aeeeb0ea Fix Thinkpad X61/T61 outputs]

'''Please use CVS version of ALSA instead. All of these patches are committed'''. The link to the CVS version of ALSA is dead[http://alsa.opensrc.org/index.php/AlsaCVS].

After doing a make and make install reboot your computer (or rrmmod snd-hda-intel && modprobe snd-hda-intel). And run alsamixer (for me it only works as root atm). If you can´t find alsamixer, you can run it in the terminal (Applications -> Accessories -> Terminal) by entering ''alsamixer''. You will have to play with the settings a bit. Make sure the speaker option is not muted and leave the Internal Mic Boost at 0, other wise you will have a really loud microphone feedback sort of sound constantly.

I had to chmod -R 777 /dev/snd/ to get everything work for now. (THIS IS NOT THE CORRECT WAY TO DO IT, IT WILL NOT STAY BETWEEN REBOOTS!).

Audio playback should then work, audio capture (microphone) doesn't seem to work, but I am probably not going to try and fix it, I don't use the capture so I am not concerned with that at the moment.
'''Update:''' With ALSA CVS, microphone seems to work

If you can't hear the mic boost mic settings. Here are my settings at KMix
Output
Mic - low
Mic Boost - full
Input
Mic boost [enable] - medium
capture [enable] - medium

works great with Skype. Also you can use the 'mic level meter' on KRecord to check the mic

In Gnome, default channel mapped to thinkpad volume buttons is MIC, which is bad. Go to ''System->Preferences->Sound->Default mixer tracks'' to change it

'''Please note''' that internal speakers doesn't work with ALSA CVS. Use the headphone jack. Solution?

----
When starting alsamixer over the terminal I couldn't activate the speakers and only had sound over the headphone. However, I figured out how to easily activate the speakers:
* Right-click on your microphone icon in the top panel.
* (If "Mute" is activated, deactivate it. I had that at the beginning and was confused since in alsa you don't really realize it.)
* Click on "Open Volume Control"
* Change to the tab "Switches" and activate the option for speaker.
That should be enough to make it work.
--[[User:Shuk|Shuk]] 02:51, 11 July 2007 (UTC)

I tried those patches, it didnt work for me. But this python script did: http://www.klabs.be/~fpiat/linux/debian/Etch_on_Thinkpad_T61.html#Sound .. apparently if you make the PC speaker play constantly, you cant hear it but you can then hear sound. Hopefully gutsy will fix this :/ --[[User:Rubin|Rubin]] 07:18, 14 July 2007 (UTC)

==Suspend==
Suspending doesn't work by default. It succesfully suspends, but after resuming, Kernel panic occurs. I didn't test hibernate.
I managed to get suspend to ram to work by using this script:

#!/bin/sh

# if launched through a lid event and lid is open, do nothing
echo "$1" | grep "button/lid" && grep -q open /proc/acpi/button/lid/LID/state && exit 0

# remove USB 1.1 driver
rmmod uhci_hcd
rmmod ehci_hcd

# sync filesystem and clock
sync
/sbin/hwclock --systohc

# switch to console
FGCONSOLE=`fgconsole`
chvt 6

# go to sleep
sleep 5 && echo -n "mem" > /sys/power/state

# readjust the clock (it might be off a bit after suspend)
/sbin/hwclock --adjust
/sbin/hwclock --hctosys

# reload USB 1.1 driver
modprobe uhci_hcd
modprobe ehci_hcd

# turn on the backlight and switch back to X
chvt $FGCONSOLE

It's very similar to script posted on thinkwiki, but I had to add ehci_hcd to removed modules and remove some radeon stuff (when using Nvidia)

'''Problems''' the problem with this suspend script is, that after resuming, the laptop is incredibly slow. Applications start about 20 seconds, Firefox is lagging. But processor doesn't run at highest frequency, nothing seems unusual. '''Suggestions?'''

This X-slow-after-resume is still here (T61p, nVidia Quadro FX 570 M, bleeding edge Gutsy 2.6.22-10-generic kernel). However, I found an official OpenSuSE 10.3 for this problem:
[https://bugzilla.novell.com/show_bug.cgi?id=290385]
--[[User:Lech|Lech]] 21:20, 2 September 2007 (UTC)

When using this script, my USB ports are 'dead' after resume (i.e. nothing connected to it gets any power). I have commented out 'rmmod ehci_hcd' and 'modprobe ehci_hcd' lines, to make the USB ports active after a suspend/resume cycle. (this is using nvidia card)

----
Suspend and hibernate work out-of-the-box for me with the 2.6.21.5 kernel, except that you need to put acpi_sleep=s3_bios in the kernel command line (i.e. at the end of each kernel line in /boot/grub/menu.lst).
--[[User:Kc8tbe|Kc8tbe]] 13:03, 1 July 2007 (UTC)

Hmm, with 2.6.21.5 + acpi_sleep=s3_bios, laptop suspends, but resume fails - machine locks up. This is with nvidia 140. Same result when doing it at console. When I resume, I hear a beep and the machine hangs. Have to hard-reset. Suggestions?

Some things seem to break after suspend for me, like network connections time out randomly, cdrom stops working etc. Running 'sudo /etc/init.d/dbus restart' seems to solve it for the most part.

----
We are having similar discussions in Ubunutu's Launchpad, and we found kind of a solution which rules out any 2D/3D graphics acceleration but allows to suspend/resume, at least on my 3 weeks old T61p and some other recent T6x/R6x models:

With thinkpad_acpi 0.16 (!) patches applied to 2.6.22 kernel, and with VESA driver only, it works perfectly so far for us.

The discussion and some links can be found at:
https://bugs.launchpad.net/ubuntu/+bug/139089
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/129125

I know it's not eye candy not to have satisfying GLX etc., but I consider working suspend/resume much more important than say playing with GoogleEarth.

--[[User:Lech|Lech]] 14:48, 16 September 2007 (UTC)

==Brightness==
Changing brightness doesn't work at all. There are many issues. I tried Gutsy and still the same (even worse)

Not a real solution, but if using the vesa driver, brightness control works. ''--Daniel06'' 11:58, 4 July 2007

doesnt work for me with vesa or intel --[[User:Rubin|Rubin]] 06:19, 14 July 2007 (UTC)

It works fine on mine and I have built-in graphics on my motherboard. [[User:SteveSims|SteveSims]] 02:19, 15 August 2007 (UTC)

=== one idea ===
echo "up" >/proc/acpi/ibm/brightness
...works. as does 'down' and 'level x' where x is 1-7. But how to tie that into the buttons? Seems they are currently using something else in /proc that doesnt exist for us. --[[User:Rubin|Rubin]] 06:19, 14 July 2007 (UTC)

=== yet another idea ===

You can add the Gnome power manager brightness applet to the gnome panel, which gives you a GUI tool to do the job, rather than hardware buttons. I don't know about KDE or other window managers. --[[User:Atoponce|Atoponce]] 13:07 22, Aug 2007

=== Another solution for Brightness, using xbacklight and laptop-mode ===

While the hardware buttons still don't work, I have a solution that will automatically raise and lower the backlight when plugged in or on battery.

First, make sure Gnome isn't trying to set the brightness, by going to System > Preferences > Power Management. In the On Battery Power tab, set "Dim display brightness by" to 0%.

Next, install xbacklight.

sudo apt-get install xbacklight

You can manually set the backlight by using "xbacklight -set <number from 1-100>". Note that by using xbacklight, you can make the backlight go brighter or dimmer than normally allowed by Windows or Ubuntu.

To automate brightness changes, first enable laptop-mode

sudo nano /etc/default/acpi-support

Scroll to the bottom and change ENABLE_LAPTOP_MODE to true

ENABLE_LAPTOP_MODE=true

Set laptop mode to start automatically

sudo update-rc.d laptop-mode multiuser

Edit laptop-mode.conf to automate brightness changes. Scroll down to LCD brightness settings. Modify the section to read as follows:

CONTROL_BRIGHTNESS=1

BATT_BRIGHTNESS_COMMAND="xbacklight -set 20"
LM_AC_BRIGHTNESS_COMMAND="xbacklight -set 100"
NOLM_AC_BRIGHTNESS_COMMAND="xbacklight -set 100"
BRIGHTNESS_OUTPUT="/dev/null"

Note: You can use any value from 1 to 100 after -set, I used 20 and 100 as examples. After this, start the laptop-mode daemon, and test if it works. You may have to restart acpid as well.

sudo /etc/init.d/laptop-mode start
sudo /etc/init.d/acpid restart

==Webcam==
The webcam in T61 is some sort of UVC camera: Found UVC 1.00 device Integrated Camera (17ef:1004). The module loads out of the box. I tested the camera using:
Luvcview: http://mxhaard.free.fr/spca50x/Investigation/uvc/luvcview-20070512.tar.gz
Just compile and run using ./luvcview -f yuv (JPG format doesn't work)

I also tried gqcam and webcam, but both doesn't work (first SEGFAULTs, second prints Invalid argument)

luvcview has a button to take pictures. Place your mouse over the buttons at the bottom of the window, and their function is revealed in the title bar. Unfortunately, the button for avi capture does not seem to work (although it does tell you what the video framerate is, which is helpful).

To capture a video stream, run ./luvcview -f yuv -S
To play back the video stream, run mplayer -demuxer rawvideo -rawvideo fps=7:w=320:h=240:yuy2 stream.raw

==64 bit systems issues==
If you are running 64 bit Ubuntu, you will face some problems with 32 bit only proprietary applications. Most of them can be solved.

===Firefox & Flash===
You can use 32bit version of Firefox (see google), or use http://gwenole.beauchesne.info/projects/nspluginwrapper/ nspluginwrapper] which i prefer:
sudo apt-get install ia32-libs ia32-libs-gtk linux32 lib32asound2 alien
Now download both nspluginwrapper rpms (Plugin + Viewer) and convert them:
sudo alien nspluginwrapper*.rpm
sudo dpkg -i nspluginwrapper*.deb

Download Adobe Flash Player: http://fpdownload.macromedia.com/get/flashplayer/current/install_flash_player_9_linux.tar.gz
tar -xvzf install_flash_player_9_linux.tar.gz
cd install_flash_player_9_linux
sudo install libflashplayer.so flashplayer.xpt /usr/lib/firefox/plugins
nspluginwrapper -i /usr/lib/firefox/plugins/libflashplayer.so
cd ~/.mozilla/plugins/
sudo install npwrapper.libflashplayer.so /usr/lib/mozilla-firefox/plugins/
This howto is taken from [http://webzine.smehlik.net/64bit-ubuntu-adobe-flash-plugin-pomoci-nspluginwrapper/ Smehlik Webzine (in Czech)]

===Skype===
Download Skype for Ubuntu Feisty
Use this commandlibdbus, libqt4-core, libqt4-gui, libsigc++ to determine missing libraries:
ldd /usr/bin/skype | grep not
It should be these:
libdbus, libqt4-core, libqt4-gui, libsigc++ (2.0 version)
Download them from http://packages.ubuntu.com (32bit versions!)
mkdir testlibs
dpkg-deb --extract <deb file> testlibs
Now copy everything from testlibs to /usr/lib32
cp -r testlibs/usr/lib/* /usr/lib32
Freedom lovers are advised to avoid proprietary systems like Skype, however. Centralized directories and signalling architectures can't be good for your health.

==Bluetooth==
works for me (TM)

==USB==
A short time after the system has booted, I get a message on the console of every window indicating IRQ# 23 has fired but noone is expecting it. After this message, the USB ports on the right side fail to work anymore. It was suggested on a forum that they will work, its just it takes it a long time to discover there is a new device. I looked in /proc and determined that the bluetooth device is using IRQ23, so it may be involved, but there may be sharing so it could be something else. Regardless, there are USB bus problems with the T61 and linux.

==Overall==
I initially had some big problems getting this working, but now its working quite well. The wifi card worked at startup (uses madwifi) and I am happy because I don't seem to need any proprietary software to run this system.

==Discussion==
In case you missed it the discussion page (for questions/responses) is right here: [[Talk: Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T61]]

==References==
* This guide is listed at the [http://tuxmobil.org/ibm.html TuxMobil Linux laptop and notebook installation guides survey (IBM/Lenovo)].
* Many other suggestions and references can be found in the following ubuntu forum: http://ubuntuforums.org/showthread.php?t=471563

[[Category:Ubuntu 7.04]]
[[Category:T61]]

Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T61

2007-09-29T13:24:01Z

Pascal: /* ThinkFinger */

On the T61, [[Installing_Ubuntu_7.10_(Gutsy_Gibbon)_Tribe_5_on_a_ThinkPad_T61|Ubuntu 7.10 (Gutsy Gibbon)]] is recommended instead of 7.04 because video drivers and wifi, among other issues, work by default.
recomended

===My DVD drive/CD burner/DVD burner doesn't work (Solved)===

Follow these instructions to enable your [http://en.wikipedia.org/wiki/Optical_drive optical drive]: 
1) Reboot your T61. Press the ThinkVantage button quickly when you see the ThinkPad screen and then press F1 enter [http://en.wikipedia.org/wiki/BIOS BIOS]. 
2) In BIOS, select Configure -> Serial ATA. 
3) Now, select Compatibility instead of AHCI. 
4) Exit BIOS and start your computer normally. 
5) Go to Places -> Computer, right-click your CD-ROM/DVD/etc. drive, and select Properties. Then, go to Drive -> Settings. Set the mount point to ''cdrom'' (regardless of whether it's a CD-ROM drive, DVD drive, etc.).

----

At first, the Ubuntu Live CD would not start at all, this seems to be a problem with the SATA AHCI driver. I had to go into the BIOS and change the SATA driver from ACHI to compatibility (What is the difference? Am I loosing performance?).

----

After you've installed and booted, try the advice from [[Problems_with_SATA_and_Linux]]. Do this:
'''# echo options libata atapi_enabled=1>/etc/modprobe.d/atapienable && update-initramfs -u'''
Then try turning AHCI back on in the BIOS. On a custom-built 2.6.21.5 kernel, my DVD drive appears as /dev/hda and DMA works.
--[[User:Kc8tbe|Kc8tbe]] 12:45, 1 July 2007 (UTC)

If your DVD drive does not appear, modprobe pata-jmicron and ide-generic.
--[[User:Antikristian|Antikristian]] 01:23, 30 July 2007 (UTC)

===NVIDIA Quadro NVS 140M (Solved)===
After initial issues like those explained above in the SATA Issues, I received the xorg error 'fatal error: no screens found'. I was able to boot into Safe Graphics Mode and run the installer, though I had to move both window manager bars to see enough of the install window to use it.

Alternatively, you can download the drivers via wget in a console. Take care to follow the instructions in
[http://www.nvnews.net/vbulletin/showthread.php?t=72490 the NVidia Forum] and uninstall all the packages wit apt-get remove, as described.
Then run the nvidia installer.

Remember that, after you upgrade the kernel, you also have to re-install the drivers.

After installing the NVIDIA drivers, your laptop may not wake after suspend or hibernation. I followed these instructions to fix it [https://help.ubuntu.com/community/NvidiaLaptopBinaryDriverSuspend Ubuntu Community Help].

====Alternative NVIDIA driver installation====
Instead of installing the NVIDIA drivers manually as described above, you can try using [http://www.albertomilone.com/nvidia_scripts1.html Envy]. It automatically installs the latest NVIDIA drivers, and cleans up any previous installations.

=== Intel Graphics Media Accelerator X3100 (Chipset GM965) (Solved)===
After that the CD seemed to boot but the screen was just garbage [http://shadowarts.nonlogic.org/projects/thinkpad/screen_garbage.jpg Picture]. In order to get around that issue I had to go back and download the Alternate CD, which allows you to install in text only mode. From here, the text-only install went okay. Changing the VGA settings on the regular CD worked for me.

When I booted up after the installation, I was still getting the same garbage on the screen. To resolve this I edited my [http://shadowarts.nonlogic.org/projects/thinkpad/xorg.conf xorg.conf] file as shown. I also had to install the latest kernel for Feisty, as the one off of the install disk did have have /dev/agpgart. And I could then use X11. There were still some issues however. The screen seemed somewhat fuzzy. This was a little more challenging of a fix... I found [http://www.spinics.net/lists/xorg/msg25099.html this] mailing list posting, according to it, there was a small glitch in the driver. To fix it:
<pre>
apt-get source xserver-xorg-video-intel
cd xserver-xorg-video-intel-1.9.94/
vim src/i830_lvds.c
Goto line 230 and delete (PFIT_ENABLE | VERT_AUTSCALE ....);, replacing it with 0; then quit vim
dpkg-buildpackage -rfakeroot -uc -b
cd ..
dpkg -i xserver-xorg-video-intel_1.9.94-lubuntu3_amd64.deb (wont be amd64 with a 32-bit install)
</pre>
Now reboot your computer, and it should work. **NOTE: For some reason just restarting X didn't fix it, seems like you must reboot.** At this point you should have a nice, crisp display.

I am still working on aiglx and compiz (switching desktops on a cube doesnt seem to work, though I have some ideas...). There are some issues with OpenGL apps freezing Xorg as well, but the standard 2D desktop works flawlessly.
----
It doesn't seem to be necessary to modify the soruce of xserver-xorg-video-intel anymore, but 3D-acceleration doesn't seem to be stable yet and kdm occasionally needs to be restarted after a login attempt.--[[User:Kc8tbe|Kc8tbe]] 12:49, 1 July 2007 (UTC)

----
I was able to use the normal feisty install disk by changing the SATA setting in BIOS, then change the resolution to 800x600 prior to install, then sudo apt-get update and upgrade, and then sudo apt-get install xserver-xorg-video-intel, then change xorg.conf to match link above and 2D graphics work fine. Jul 18, 2008 - John E
----

It seems that everything works fine when using "apt pinning" and updating the xserver-xorg-video-intel, mesa and other packages to the versions provided by Gutsy. I did the following and the resolution and Compiz Fusion are working fine at the moment. The original source of the steps described below can be found here: [http://techreport.com/forums/viewtopic.php?p=714998#714998]

'''Instructions:'''
* Make a new file /etc/apt/preferences
* In the preferences file, put:
<pre>
Package: *
Pin: release a=feisty
Pin-Priority: 700

Package: *
Pin: release a=gutsy
Pin-Priority: 200
</pre>
* Now, edit your sources.list and copy the main and restricted (and others if you want) repo lines replacing feisty with gutsy:
<pre>
# original
deb http://archive.ubuntu.com/ubuntu feisty main restricted universe multiverse
deb-src http://security.ubuntu.com/ubuntu feisty main restricted universe multiverse

# your addition
deb http://archive.ubuntu.com/ubuntu gutsy main restricted universe multiverse
deb-src http://security.ubuntu.com/ubuntu gutsy main restricted universe multiverse
</pre>
* Now run:
<pre>
sudo apt-get update
</pre>
{{HINT|If you get an error while trying to update, it may be because your apt cache is too small. To fix this add the following to your "/etc/apt/apt.conf.d/70debconf":
<pre>
APT::Cache-Limit "118388608";
</pre>--[[User:Thefekete|Thefekete]] 04:14, 19 September 2007 (UTC)}}
*Then Run:
<pre>
sudo apt-get -t gutsy install xserver-xorg-video-intel
sudo apt-get -t gutsy install linux
sudo apt-get -t gutsy install libgl1-mesa-dri
</pre>
* Now reboot.

Probably now you have the weird effect that your GUI is scaled wrong and doesn't fill the full width of the monitor. To fix that, open your xorg.conf and make the following changes:
* Add the following section to your xorg.conf
<pre>
Section "Monitor"
Identifier "TVOutput"
Option "Disable" "true"
EndSection
</pre>
* Then in the "Device" section add the following line:
<pre>
Option "monitor-TV" "TVOutput"
</pre>

That should fix the scaling problem and now everything should work fine.
--[[User:Shuk|Shuk]] 02:26, 10 July 2007 (UTC)

{{HINT|If you experience problems with totem or other gstreamer apps crashing, try this:
<pre>
$ gstreamer-properties
</pre>
* Then under the "Video" tab, change the Output Plugin to "X Window System (No Xv)"
This will run the video through you processor, but won't crash gstreamer. --[[User:Thefekete|Thefekete]] 04:14, 19 September 2007 (UTC)}}

===ThinkFinger===
Ubuntu does not come with a package for thinkfinger. Downloading the most recent source and building it was simple enough: Download most recent version (0.3 at time of writing)
<pre>
sudo apt-get install libpam0g-dev libusb-dev
tar xvzf thinkfinger-0.3.tar.gz
cd thinkfinger-0.3/
./configure --with-securedir=/lib/security --with-birdir=/etc/pam_thinkfinger
make -j5 (hey its dual core!)
sudo make install
sudo ldconfig
</pre>

Configuring it is easy as well, open /etc/pam.d/common-auth:
<pre>
auth sufficient pam_thinkfinger.so
auth required pam_unix.so try_first_pass nullok_secure
</pre>

Create the data directory and set your fingerprint:
<pre>
sudo mkdir /etc/pam_thinkfinger
sudo tf-tool --add-user <username>
</pre>

To get be asked to swipe your finger when logging in or sudoing
<pre>
sudo modprobe uinput
</pre>
To make sure it works after reboot add "uinput" to the list in /etc/modules
It will all be setup. (I found this somewhere on the web, I wish I could give a source but I'm afraid I cant find it, thank you Anonymous!).

===HDAPS===
This seems to be working fine now, I just follow the step on [[How_to_protect_the_harddisk_through_APS]]. Using hdaps-gl does the inverse of the accelerometer, though it's not really a big deal, the harddrive protection should still work.

Assuming that the (improved) hdaps code bundled with tp_smapi is being used, editing the transform_axis function in tp_smapi-0.32/hdaps.c will allow for the proper operation of the accelerometer. Assuming that the accelerometer is rotated 90 degrees from its proper orientation (as it is with the X61), the following code will suffice:

<pre>
static void transform_axes(int *x, int *y)
{
int temp = *x;
*x = -*y;
*y = temp;
}
</pre>

For those paying attention in linear algebra, this corresponds to a linear transformation that rotates a 2D coordinate system 90 degrees.
--[[User:Mbsullivan|Mbsullivan]] 04:21, 27 August 2007 (UTC)

Instead of editing the code, you can just pass the invert=1 parameter when loading the module; modprobe hdaps invert=1
--[[User:Vegar|Vegar]] 14:40, 17 September 2007 (UTC)

===WiFi===
If you have Intel 4965AGN WiFi card, you have to use ndiswrapper OR use backported kernel from Ubuntu Gutsy (Anybody have howto?) and use following:
http://kuscsik.blogspot.com/2007/06/how-to-install-intel-4965-wireless.html

'''Note:'''
Do not use the latest versions of iwlwifi and mac80211. For me with Gutsy mac80211-8.0.2 and iwlwifi-0.0.42 work with the latest firmware. No further modification needed.

If you have the Atheros card, Ubuntu should automatically install madwifi, which works out of the box
----
Works for me with iwlwifi-4965-ucode-4.44.15, iwlwifi-0.0.34, and mac80211-8.0.1. The catch is, you need to patch your kernel with mac80211, which will fail at compile time with the stock Ubuntu sources. Worked for me with vanilla 2.6.21.5 sources patched for tp_smapi and hdaps protect. Make sure to disable CONFIG_NET_WIRELESS_RTNETLINK in your kernel config.

You can download what you need for for iwlwifi and mac80211 from
http://intellinuxwireless.org .--[[User:Kc8tbe|Kc8tbe]] 13:00, 1 July 2007 (UTC)

Works for me with vanilla kernel v2.6.22.1, ucode 4.44.17, iwlwifi 0.1.2 and mac80211 9.0.2. --[[User:Mbsullivan|Mbsullivan]] 13:40, 24 July 2007 (UTC)

You can also use Kernel 2.6.22.9 and Ubuntu Modules 2.6.22.9 from Gutsy and you will not need to compile anything! Works very well.

===Keyboard/Apostrophe issues (Solved)===
When installing with the alternate CD, Ubuntu asks you if your keyboard as a character that appears to be a quotation mark (this character: "). If you're using a US English keyboard, say no; the character is actually an umlaut. [[User:SteveSims|SteveSims]] 02:15, 19 August 2007 (UTC)

My apostrophe key outputs ´ instead of '. I went to System -> Preferences -> Keyboard and could not figure out how to fix it. [[User:SteveSims|SteveSims]] 21:50, 11 August 2007 (UTC)

:Try switching your keyboard layout to US-Classic, and putting it on the top of the list. After you do that, it works perfectly. --[[User:Adamacious|Adamacious]] 04:29, 13 August 2007 (UTC)

::There is no "US Classic" option. Here's what I have: 
[[Image:Keyboard_options.png]] 
[[User:SteveSims|SteveSims]] 02:17, 15 August 2007 (UTC)

:::It started working, even though I changed nothing. I'm running it as a Macintosh US English keyboard. [[User:SteveSims|SteveSims]] 17:20, 15 August 2007 (UTC)

::::Sorry Steve, what you had to do (and what you did) is select US English, as in the header in the list. It doesn't look selectable, but it is.--[[User:Adamacious|Adamacious]] 20:02, 22 August 2007 (UTC)

===Audio===
====Fixed in Gutsy====
As of 29 August 2007 and [https://bugs.launchpad.net/bugs/122560 this issue], the 2.6.22-10 kernel in Gutsy Gibbon supports audio out-of-the-box (as well as WiFi and other things). Installing the Gutsy kernel via apt and rebooting fixed audio for me, both speakers and headphones. Remaining issues:

* The mute button mutes audio, but doesn't unmute. Pressing volume up or down does unmute it, but has no effect on volume.
* KMix's system tray volume control has no effect because it thinks it's setting the headphones while both outputs are using the speaker settings, but opening KMix and setting the PCM volume works. --lgarfiel

====Python script fix (slightly easier fix)====
First, you have to download the source for the [http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.22.5.tar.gz latest Linux kernel] (2.6.22-5 as of August 26th, 2007) and compile it, something most users cannot do. However, you won't have to compile ALSA and its modules from source if you do it this way.

1) Download the [http://launchpadlibrarian.net/8899521/t61_audio_hack.py T61 audio hack] from [[Launchpad]]. Move it to a convenient folder (e.g., not your desktop). 
2) Go to System -> Preferences -> Sessions -> Startup Programs -> Add. 
3) Name it whatever you want. Choose something simple like "Python audio fix." 
4) Go to Command, and enter the following (with quotation marks):
<pre>gksudo <nowiki>"[THE FOLDER THAT T61_AUDIO_HACK.PY IS IN]</nowiki>/t61_audio_hack.py"</pre>
For example, on my computer, I put t61_audio_hack.py into the /fixes folder in my home folder, so I entered:
<pre>sksudo "/home/sims/fixes/t61_audio_hack.py"</pre> into the Command textbox. 
5) Log out, log back in, and type your password quickly when prompted the second time.

References:
[https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/122560 Launchpad Bug #122560]
[https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/133105 Launchpad Bug #133105]

====ALSA driver update (hard fix, recommended for advanced users)====

:'''''Note: This section assumes a high level of technical proficiency. Please fix it.'''''
::*<s>At [http://www.alsa-project.org www.asla-project.org], did you download only alsa-driver-1.0.14? That and alsa-lib-1.0.14a?</s>
:::Download alsa-driver, alsa-kernel, alsa-lib, and alsa-utils, according to [http://alsa.opensrc.org/index.php/AlsaCVS http://alsa.opensrc.org/index.php/AlsaCVS]. Other sources, however, say only the driver is necessary. Perhaps alsa-project.org simply recommends the other two?
::*''How'' did you compile it from source? ''How'' did you add the patch?
::*In short, please explain ''how'' you did these things in addition to just telling us ''what'' you did. I´m not trying to be rude but seriously, not all Linux users are programmers ;). Thanks. [[User:SteveSims|SteveSims]] 22:19, 11 August 2007 (UTC)
After upgrading to 1.0.14 I still had no sound, and this took about a week to solved (though it was so sadly obvious though). Just upgrading to alsa 1.0.14 will not be enough, there were a few patches released right after the release that fix the Thinkpad's. The reason I missed this was because it was the same day so the release of 1.0.14!

---------------------------------------------------------------------------
VERY SIMPLE METHOD OF MAKING SOUND WORK
http://forums.fedoraforum.org/showthread.php?t=159516&page=1&pp=15
Just follow the instructions step by step, except for two small things:
When doing "cp ../patch_analog.c alsa-driver-1.0.14/alsa-kernel/pci/hda/" use "cp ../patch_analog.c alsa-kernel/pci/hda/" instead
Also, when you get to the part about modifying the modprobe.conf file, it doesn't exist in ubuntu. Adding "options snd-hda-intel index=0 model=thinkpad" to any file (even one you make yourself) inside etc/modprobe.d should work. I personally added it to the options file, and it works fine.

-credit for the guide goes to ciphermonk, and credit to the small changes needed to make this work on ubuntu go to my friend John.

-hotkeys control mic volume, not speaker volume for some reason. I do not know how to fix this

-this fix should provide sound for both headphones and speakers.

-this edit by fatalchaos
---------------------------------------------------------------------------------------

First make sure these packages are installed (System -> Administration -> Synaptic Package Manager) : automake, autoconfig, cvs, libtool, python-dev, build-essential

Then download the source code to the alsa-driver and apply these patches: (links to the revisions)

* [http://hg.alsa-project.org/alsa-kernel/rev/958b39f3e8dd Fix Oops with AD1984 thinkpad model]
* [http://hg.alsa-project.org/alsa-kernel/rev/47ca87407c84 Fix AD1984 basic model]
* [http://hg.alsa-project.org/alsa-kernel/rev/ca37aeeeb0ea Fix Thinkpad X61/T61 outputs]

'''Please use CVS version of ALSA instead. All of these patches are committed'''. The link to the CVS version of ALSA is dead[http://alsa.opensrc.org/index.php/AlsaCVS].

After doing a make and make install reboot your computer (or rrmmod snd-hda-intel && modprobe snd-hda-intel). And run alsamixer (for me it only works as root atm). If you can´t find alsamixer, you can run it in the terminal (Applications -> Accessories -> Terminal) by entering ''alsamixer''. You will have to play with the settings a bit. Make sure the speaker option is not muted and leave the Internal Mic Boost at 0, other wise you will have a really loud microphone feedback sort of sound constantly.

I had to chmod -R 777 /dev/snd/ to get everything work for now. (THIS IS NOT THE CORRECT WAY TO DO IT, IT WILL NOT STAY BETWEEN REBOOTS!).

Audio playback should then work, audio capture (microphone) doesn't seem to work, but I am probably not going to try and fix it, I don't use the capture so I am not concerned with that at the moment.
'''Update:''' With ALSA CVS, microphone seems to work

If you can't hear the mic boost mic settings. Here are my settings at KMix
Output
Mic - low
Mic Boost - full
Input
Mic boost [enable] - medium
capture [enable] - medium

works great with Skype. Also you can use the 'mic level meter' on KRecord to check the mic

In Gnome, default channel mapped to thinkpad volume buttons is MIC, which is bad. Go to ''System->Preferences->Sound->Default mixer tracks'' to change it

'''Please note''' that internal speakers doesn't work with ALSA CVS. Use the headphone jack. Solution?

----
When starting alsamixer over the terminal I couldn't activate the speakers and only had sound over the headphone. However, I figured out how to easily activate the speakers:
* Right-click on your microphone icon in the top panel.
* (If "Mute" is activated, deactivate it. I had that at the beginning and was confused since in alsa you don't really realize it.)
* Click on "Open Volume Control"
* Change to the tab "Switches" and activate the option for speaker.
That should be enough to make it work.
--[[User:Shuk|Shuk]] 02:51, 11 July 2007 (UTC)

I tried those patches, it didnt work for me. But this python script did: http://www.klabs.be/~fpiat/linux/debian/Etch_on_Thinkpad_T61.html#Sound .. apparently if you make the PC speaker play constantly, you cant hear it but you can then hear sound. Hopefully gutsy will fix this :/ --[[User:Rubin|Rubin]] 07:18, 14 July 2007 (UTC)

==Suspend==
Suspending doesn't work by default. It succesfully suspends, but after resuming, Kernel panic occurs. I didn't test hibernate.
I managed to get suspend to ram to work by using this script:

#!/bin/sh

# if launched through a lid event and lid is open, do nothing
echo "$1" | grep "button/lid" && grep -q open /proc/acpi/button/lid/LID/state && exit 0

# remove USB 1.1 driver
rmmod uhci_hcd
rmmod ehci_hcd

# sync filesystem and clock
sync
/sbin/hwclock --systohc

# switch to console
FGCONSOLE=`fgconsole`
chvt 6

# go to sleep
sleep 5 && echo -n "mem" > /sys/power/state

# readjust the clock (it might be off a bit after suspend)
/sbin/hwclock --adjust
/sbin/hwclock --hctosys

# reload USB 1.1 driver
modprobe uhci_hcd
modprobe ehci_hcd

# turn on the backlight and switch back to X
chvt $FGCONSOLE

It's very similar to script posted on thinkwiki, but I had to add ehci_hcd to removed modules and remove some radeon stuff (when using Nvidia)

'''Problems''' the problem with this suspend script is, that after resuming, the laptop is incredibly slow. Applications start about 20 seconds, Firefox is lagging. But processor doesn't run at highest frequency, nothing seems unusual. '''Suggestions?'''

This X-slow-after-resume is still here (T61p, nVidia Quadro FX 570 M, bleeding edge Gutsy 2.6.22-10-generic kernel). However, I found an official OpenSuSE 10.3 for this problem:
[https://bugzilla.novell.com/show_bug.cgi?id=290385]
--[[User:Lech|Lech]] 21:20, 2 September 2007 (UTC)

When using this script, my USB ports are 'dead' after resume (i.e. nothing connected to it gets any power). I have commented out 'rmmod ehci_hcd' and 'modprobe ehci_hcd' lines, to make the USB ports active after a suspend/resume cycle. (this is using nvidia card)

----
Suspend and hibernate work out-of-the-box for me with the 2.6.21.5 kernel, except that you need to put acpi_sleep=s3_bios in the kernel command line (i.e. at the end of each kernel line in /boot/grub/menu.lst).
--[[User:Kc8tbe|Kc8tbe]] 13:03, 1 July 2007 (UTC)

Hmm, with 2.6.21.5 + acpi_sleep=s3_bios, laptop suspends, but resume fails - machine locks up. This is with nvidia 140. Same result when doing it at console. When I resume, I hear a beep and the machine hangs. Have to hard-reset. Suggestions?

Some things seem to break after suspend for me, like network connections time out randomly, cdrom stops working etc. Running 'sudo /etc/init.d/dbus restart' seems to solve it for the most part.

----
We are having similar discussions in Ubunutu's Launchpad, and we found kind of a solution which rules out any 2D/3D graphics acceleration but allows to suspend/resume, at least on my 3 weeks old T61p and some other recent T6x/R6x models:

With thinkpad_acpi 0.16 (!) patches applied to 2.6.22 kernel, and with VESA driver only, it works perfectly so far for us.

The discussion and some links can be found at:
https://bugs.launchpad.net/ubuntu/+bug/139089
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/129125

I know it's not eye candy not to have satisfying GLX etc., but I consider working suspend/resume much more important than say playing with GoogleEarth.

--[[User:Lech|Lech]] 14:48, 16 September 2007 (UTC)

==Brightness==
Changing brightness doesn't work at all. There are many issues. I tried Gutsy and still the same (even worse)

Not a real solution, but if using the vesa driver, brightness control works. ''--Daniel06'' 11:58, 4 July 2007

doesnt work for me with vesa or intel --[[User:Rubin|Rubin]] 06:19, 14 July 2007 (UTC)

It works fine on mine and I have built-in graphics on my motherboard. [[User:SteveSims|SteveSims]] 02:19, 15 August 2007 (UTC)

=== one idea ===
echo "up" >/proc/acpi/ibm/brightness
...works. as does 'down' and 'level x' where x is 1-7. But how to tie that into the buttons? Seems they are currently using something else in /proc that doesnt exist for us. --[[User:Rubin|Rubin]] 06:19, 14 July 2007 (UTC)

=== yet another idea ===

You can add the Gnome power manager brightness applet to the gnome panel, which gives you a GUI tool to do the job, rather than hardware buttons. I don't know about KDE or other window managers. --[[User:Atoponce|Atoponce]] 13:07 22, Aug 2007

=== Another solution for Brightness, using xbacklight and laptop-mode ===

While the hardware buttons still don't work, I have a solution that will automatically raise and lower the backlight when plugged in or on battery.

First, make sure Gnome isn't trying to set the brightness, by going to System > Preferences > Power Management. In the On Battery Power tab, set "Dim display brightness by" to 0%.

Next, install xbacklight.

sudo apt-get install xbacklight

You can manually set the backlight by using "xbacklight -set <number from 1-100>". Note that by using xbacklight, you can make the backlight go brighter or dimmer than normally allowed by Windows or Ubuntu.

To automate brightness changes, first enable laptop-mode

sudo nano /etc/default/acpi-support

Scroll to the bottom and change ENABLE_LAPTOP_MODE to true

ENABLE_LAPTOP_MODE=true

Set laptop mode to start automatically

sudo update-rc.d laptop-mode multiuser

Edit laptop-mode.conf to automate brightness changes. Scroll down to LCD brightness settings. Modify the section to read as follows:

CONTROL_BRIGHTNESS=1

BATT_BRIGHTNESS_COMMAND="xbacklight -set 20"
LM_AC_BRIGHTNESS_COMMAND="xbacklight -set 100"
NOLM_AC_BRIGHTNESS_COMMAND="xbacklight -set 100"
BRIGHTNESS_OUTPUT="/dev/null"

Note: You can use any value from 1 to 100 after -set, I used 20 and 100 as examples. After this, start the laptop-mode daemon, and test if it works. You may have to restart acpid as well.

sudo /etc/init.d/laptop-mode start
sudo /etc/init.d/acpid restart

==Webcam==
The webcam in T61 is some sort of UVC camera: Found UVC 1.00 device Integrated Camera (17ef:1004). The module loads out of the box. I tested the camera using:
Luvcview: http://mxhaard.free.fr/spca50x/Investigation/uvc/luvcview-20070512.tar.gz
Just compile and run using ./luvcview -f yuv (JPG format doesn't work)

I also tried gqcam and webcam, but both doesn't work (first SEGFAULTs, second prints Invalid argument)

luvcview has a button to take pictures. Place your mouse over the buttons at the bottom of the window, and their function is revealed in the title bar. Unfortunately, the button for avi capture does not seem to work (although it does tell you what the video framerate is, which is helpful).

To capture a video stream, run ./luvcview -f yuv -S
To play back the video stream, run mplayer -demuxer rawvideo -rawvideo fps=7:w=320:h=240:yuy2 stream.raw

==64 bit systems issues==
If you are running 64 bit Ubuntu, you will face some problems with 32 bit only proprietary applications. Most of them can be solved.

===Firefox & Flash===
You can use 32bit version of Firefox (see google), or use http://gwenole.beauchesne.info/projects/nspluginwrapper/ nspluginwrapper] which i prefer:
sudo apt-get install ia32-libs ia32-libs-gtk linux32 lib32asound2 alien
Now download both nspluginwrapper rpms (Plugin + Viewer) and convert them:
sudo alien nspluginwrapper*.rpm
sudo dpkg -i nspluginwrapper*.deb

Download Adobe Flash Player: http://fpdownload.macromedia.com/get/flashplayer/current/install_flash_player_9_linux.tar.gz
tar -xvzf install_flash_player_9_linux.tar.gz
cd install_flash_player_9_linux
sudo install libflashplayer.so flashplayer.xpt /usr/lib/firefox/plugins
nspluginwrapper -i /usr/lib/firefox/plugins/libflashplayer.so
cd ~/.mozilla/plugins/
sudo install npwrapper.libflashplayer.so /usr/lib/mozilla-firefox/plugins/
This howto is taken from [http://webzine.smehlik.net/64bit-ubuntu-adobe-flash-plugin-pomoci-nspluginwrapper/ Smehlik Webzine (in Czech)]

===Skype===
Download Skype for Ubuntu Feisty
Use this commandlibdbus, libqt4-core, libqt4-gui, libsigc++ to determine missing libraries:
ldd /usr/bin/skype | grep not
It should be these:
libdbus, libqt4-core, libqt4-gui, libsigc++ (2.0 version)
Download them from http://packages.ubuntu.com (32bit versions!)
mkdir testlibs
dpkg-deb --extract <deb file> testlibs
Now copy everything from testlibs to /usr/lib32
cp -r testlibs/usr/lib/* /usr/lib32
Freedom lovers are advised to avoid proprietary systems like Skype, however. Centralized directories and signalling architectures can't be good for your health.

==Bluetooth==
works for me (TM)

==USB==
A short time after the system has booted, I get a message on the console of every window indicating IRQ# 23 has fired but noone is expecting it. After this message, the USB ports on the right side fail to work anymore. It was suggested on a forum that they will work, its just it takes it a long time to discover there is a new device. I looked in /proc and determined that the bluetooth device is using IRQ23, so it may be involved, but there may be sharing so it could be something else. Regardless, there are USB bus problems with the T61 and linux.

==Overall==
I initially had some big problems getting this working, but now its working quite well. The wifi card worked at startup (uses madwifi) and I am happy because I don't seem to need any proprietary software to run this system.

==Discussion==
In case you missed it the discussion page (for questions/responses) is right here: [[Talk: Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T61]]

==References==
* This guide is listed at the [http://tuxmobil.org/ibm.html TuxMobil Linux laptop and notebook installation guides survey (IBM/Lenovo)].
* Many other suggestions and references can be found in the following ubuntu forum: http://ubuntuforums.org/showthread.php?t=471563

[[Category:Ubuntu 7.04]]
[[Category:T61]]