ThinkWiki - User contributions [en]

Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T60

2007-02-14T05:14:46Z

Ischg:

Ubuntu Feisty Fawn is still under development (''alpha status'') and works fine on a T60 UT-049GE and 2007-72U.

The installation worked without any problems. The new network manager is great as it now supports a useful roaming mode. The system runs stable since 3 days of work. No crash, no severe bugs. I would recommend it for experimental systems lovers. :)

Installation instructions for the ThinkPad T60

2007-01-26T03:02:10Z

Ischg: /* Ubuntu */

Specific installation notes for the ThinkPad {{T60}}.

==Distribution-specific instructions==

=== Ubuntu ===

*{{Install|Ubuntu| 7.04 (Feisty Fawn)| T60}}
*{{Install|Ubuntu| 6.10 (Edgy Eft)| T60}}
*{{Install|Ubuntu| 6.06 Flight 5|T60}}

=== Fedora ===

*{{Install|Fedora| Core 6| T60}}
*{{Install|Fedora| Core 5| T60}}

=== openSUSE / SUSE LINUX ===

*{{Install|Suse| 10.1| T60}}
*[[Installing openSUSE 10.2 on an IBM ThinkPad T60]]

=== Gentoo ===

* For Gentoo, there exists [[Installation_instructions_for_the_ThinkPad_T60p|installation instructions for T60p]], the sister model.

== Compatibility ==
* [http://www.emperorlinux.com/mfgr/lenovo/toucan/?tab=details&id=358 Thinkpad T60] page on [http://www.emperorlinux.com emperorlinux.com] (compatibility review and custom kernel)

Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T60

2007-01-26T03:01:13Z

Ischg:

Ubuntu Feisty Fawn is still in development (aka a ''beta version'') and appears '''not ready for installation''' (as of January 12, 2007). In particular, on a 2007-72U the installer crashed - see [https://launchpad.net/ubuntu/+source/ubiquity/+bug/79029 bug report]. The next beta releases are planned for February 1st and 15th, respectively (see [https://wiki.ubuntu.com/FeistyReleaseSchedule?highlight=%28feisty%29 Feisty Release Schedule]). The final release is planned for April 19th 2007.

Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T60

2007-01-26T02:57:33Z

Ischg: Installing Ubuntu 7.04 Herd 2 (Feisty Fawn) on a ThinkPad T60 moved to Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T60: Original name was specific to a beta release of Feisty Fawn

This page is obsolete and should be deleted (name is specific to a beta release of Ubuntu Feisty Fawn).

Installing Ubuntu 7.04 Herd 2 (Feisty Fawn) on a ThinkPad T60

2007-01-26T02:57:33Z

Ischg: Installing Ubuntu 7.04 Herd 2 (Feisty Fawn) on a ThinkPad T60 moved to Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T60: Original name was specific to a beta release of Feisty Fawn

#REDIRECT [[Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T60]]

Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T60

2007-01-26T02:56:38Z

Ischg:

This page is obsolete and should be deleted (name is specific to a beta release of Ubuntu Feisty Fawn).

Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60

2007-01-24T04:59:21Z

Ischg: /* Non-Intel Network Cards */

Created by: [[User:Keithvassallo|Keithvassallo]] 14:39, 16 December 2006 (CET)

Thanks for valuable contributions by:

: [[User:Ischg|Ischg]]
: [[User:Soon|Soon]]
: [[User:Mgrusin|Mgrusin]]
: [[User:Mattcohn|Mattcohn]]
: [[User:Dchao|Dchao]]
: [[User:The.ant|The.ant]]
: [[User:Stevie|Stevie]]
: [[User:Gagarine|Gagarine]]

Also, thanks to contributions by Malta Linux User Group (http://www.linux.org.mt) members:

: dave abrahams
: Limo Driver

===Abstract===

This article describes how to get Ubuntu Linux 6.10 (Edgy) installed on an IBM/Lenovo ThinkPad T60. It's not meant to be a definite guide to installing Ubuntu (the Ubuntu Guide at http://www.ubuntuguide.org does a very good job of that). This article is meant to describe how to get most of the ThinkPad features working on Ubuntu system. It also discusses how to get Multimedia, some cool-looking effects such as Beryl, gDesklets and similar working on Ubuntu. Finally, we discuss some common problems encountered on Ubuntu and ThinkPads alike.

{{NOTE|I am in no means an expert, the methods described here are those which got everything to work for me - your mileage may vary. A big thank you to all ThinkWiki users who keep contributing on improving this article.}}

===My ThinkPad===

Although this guide should work on most recent ThinkPads, I cannot guarantee that. These are the specifications of my machine. The closer your specs are, the greater the chance of success.

: Figure 1. ThinkPad T60 2007, complete with Tux sticker :-)
: [[Image:thinkpad.jpg]]

* Lenovo ThinkPad T60 2007.
* Intel Centrino Duo T2400 / 1.83 GHz.
* Mobile Intel 945PM Express Chipset.
* Intel Wireless LAN.
* Integrated Bluetooth.
* ATI Mobility Radeon X1400 - PCI Express x16, 128MB dedicated RAM.
* 100 GB - Serial ATA-150 Hard Drive.
* 15' TFT Active Matrix Display (1400x1050).

That's basically all you need to know. As far as I know, all other features are common to all ThinkPads manufactured by Lenovo since they acquired IBM's computer business.

===Why Ubuntu? (or rather, Why not SUSE?)===

In June 2006, Lenovo announced it would be shipping ThinkPad T60p laptops with SUSE Linux Enterprise Desktop (SLED) 10 pre-installed, since SLED apparently supports all of the features of the T60p. I contacted my local IBM supplier, who said that Lenovo were no longer manufacturing the T60p, since the company which was making the displays went out of business. This meant I could not get a T60p with SLED pre-installed. I decided to go for the T60 2007, which is the closest thing I could find to the T60p. This comes with Windows XP Professional pre-installed.

I first tried to get SLED installed on the T60. Although it did indeed install, and most features worked, I soon got bored of SLED. Firstly, SLED uses Gnome 2.12, which is by now ancient. Secondly, although the Lenovo utilities do work on SLED, they only work well if you use KDE as your defauly desktop environment, which is a pity since I'm a Gnome user. The utilities were very unstable to me too. Finally, what made me give up SLED was the usual problem - it's an RPM based distribution. Once you start using Debian derivatives, with their apt based installer, you won't want to go back. That's when I decided to try Ubuntu, and have not regretted it since.

===What Works?===

* Ubuntu and all programs it comes with.
* Most of the function keys, except the ones mentioned below
* The fingerprint reader.
* The ATI proprietary graphics drivers.
* Brightness, Volume and Mute with OSD (On-Screen Display).
* ThinkLight, TrackPoint II and the touchpad.

===What Doesn't Work? (Known Issues)===

* FN+F7, FN+F8, FN+F9.
* Sending files to Bluetooth devices via GUI.
* Suspend to Disk (works with sufficient memory).
* Suspend to RAM (though it works on occasions).

There are probably ways and means to get the offending buttons to work, I've tried several fora but none seem to address my exact problem. I'll update this article should I find out anything. As for the Bluetooth bug, this is a HAL bug and can only be fixed by a future update. Suspend to Disk and Suspend to RAM are broken apparently due to the ATI drivers. Again, this can only be fixed by ATI.

===First Things First - Creating a Windows Recovery Disc===

If you've purchased a T60, chances are it came with Windows XP Professional. The other option is for you to have FreeDOS installed, in which case you can skip this section. You could remove the Windows partition altogether, and reserve your ThinkPad for Linux, but that's not the route I've chosen. The ThinkVantage utilities in Windows allow you to do a lot of cool things, such as set-up a boot-up fingerprint security scan. You can't do this from Linux (as far as I know) so it's best to leave the Windows partition in place. So, boot your ThinkPad and complete the Windows XP setup (which asks you to add a user account and enroll yourself using the ThinkVantage Client Security Solution). While you're there, use the ThinkVantage productivy centre to enroll your fingerprint (I suggest enrolling more than one) and make sure you check the option to require a fingerprint scan on boot (not for security, for geek points). When you reboot, press ESC or F2 to get to BIOS, and make sure you check the option to require a supervisor password. This will make your ThinkPad prompt you for your fingerprint when you power it up.

: Figure 2. Configuring fingerprint security from Windows
: [[Image:winprint.jpg]]

Now that's working, you should create a recovery DVD using the ThinkVantage recovery utilities. This will allow you to recover your Windows installation should you manage to screw your partitions up in the following stages. I highly recommend you do this, as Lenovo does not provide Windows XP CDs with this Laptop - so the hard disk partition is all you've got. Once this is done, we're ready to install Ubuntu!

: Figure 3. Creating recovery discs from Windows
: [[Image:recovery.jpg]]

===Getting Ubuntu installed===

Download the latest Edgy live CD from the Ubuntu website, you can find a list of mirrors at http://www.ubuntu.com/products/GetUbuntu/download#currentrelease. You may also try Kubuntu, Edubuntu or any of it's derivatives, but I'll stick with Ubuntu here for simplicity's sake. Once that's downloaded, burn the ISO to disc using any program of your choice (If this is your first Linux experience and you're using Windows, try using Nero - http://www.nero.com).

Once the burning process is complete, reboot your machine ensuring that the Ubuntu CD is in the drive. You should see an Ubuntu menu. If you don't, your BIOS is not set to boot from CD. Reboot your ThinkPad and change the boot order from BIOS (by default ThinkPads boot from CD-ROM before the hard disk, so this is probably not necessary). Once the menu shows up, select 'Start or install Ubuntu' and let it boot. This will take a while as everything is loaded from CD. You should eventually end up in a Gnome desktop. If you see an error about the Gnome Settings Daemon not being able to load, simply ignore it, as this is not necessary for now. For the purposes of the installation, it's best if you have a wired ethernet connection, as it's unlikely the wireless network card will work until we boot into our installed Ubuntu system.

: Figure 4. Select the first option to start Ubuntu
: [[Image:boot.jpg]]

Double-Click on the 'install' icon on the Desktop to start installation. The installation should be pretty straight-forward. If you need additional help, check out the walk-through with screen-shots at http://www.debianadmin.com/ubuntu-edgy-eft-desktop-installation-with-screenshots.html. The only stage at which we need to make changes is the partitioning stage. This to make sure we preserve our Windows partition, and the IBM vendor_diag partition which allows recovery of the laptop when things go hay-wire. In the 'Prepare disk space' section of the installer, select the third option, 'Manually edit partition table'. A bar will be displayed showing your existing partitions. If you have Windows installed you will see two partitions. The first is a 4.89 GB IBM Vendor Diagnostic partition, which we do not want to touch. The second will be your Windows partition, which will fill the rest of the disk. Click on this partition, Then click the 'Resize/Move' button. I resized my Windows partition to 24 GB. This is enough to accommodate the 10 GB already in use on that partition, as well as giving Windows another 14 GB of free space. 6 GB of free space would probably be enough though.

Now it's time to create partitions for Linux. You need at least two partitions; a swap partition which should be roughly double the amount of RAM you have, and a root partition to install Linux. I opted for four partitions, as follows:

<table border=1>
<tr><td>'''Purpose'''</td><td>'''Size'''</td><td>'''File-System'''</td></tr>
<tr><td>Swap</td><td>2 GB</td><td>swap</td></tr>
<tr><td>/boot</td><td>5 GB</td><td>ext3</td></tr>
<tr><td>/ (root)</td><td>20 GB</td><td>ext3</td></tr>
<tr><td>/home</td><td>37.25 GB (what's left of the disk)</td><td>ext3</td></tr>
</table>

To create these paritions, click on the 'New' button and select 'Extended Partition' in the 'create as' drop-down list. Leave all other settings as-is, and click 'Add'. Now, click on the newly created partition, and create each of the partitions you want to create, simply specify the size of the partition in the 'New Size (MiB)' text box. To convert GB to MiB, multiply by 1024. So for your swap partition you should specify a size of 2048. Repeat until you have created all the required partitions. If you follow my parition layout, the partition editor should look something like Figure 5.

: Figure 5. Our partitions, ready to be created
: [[Image:partitioning.jpg]]

You will not see mount-points in your diagram, because the screen-shot above was taken after they were assigned, but you should get the general idea. After this screen, you will be asked to assign mount-points to the partitions you have just created. If you created the partitions in the same order I did, you can assign mount points as I have (i.e. /dev/sda5 for swap, /dev/sda6 for /boot, /dev/sda7 for /, /dev/sda8 for /home). Additionally, I mounted my Windows partition as /media/sda1 and my IBM Vendor Diagnostic partition as /media/sda2. These are optional. After this step, continue installation as normal. When the installation is complete, click the 'reboot' button to restart into your fresh Ubuntu System.

When booting, the GRUB boot-loader will be displayed, asking you what you want to load. You will probably see four options. The first two being Ubuntu Linux and Ubuntu Linux recovery mode (showing the kernel version). The other two will be Microsoft Windows XP, and 'Other Windows XP/2000/NT' partition. This is your IBM Vendor Diagnostic partition, which is based on the Windows kernel, apparently. Select the first entry to boot Ubuntu. The next time you boot Windows, it will bring up a chkdsk screen. This is entirely normal and happens because we have resized the Windows partition. Make sure you do not skip this check and let it complete.

===Wireless LAN===

{{WARN|Another ThinkWiki user notes that not all T60s come with the Intel wireless chip. If you are not entirely sure what wireless NIC you use, please read the following section (Non-Intel Network Cards).}}

The first thing we should do is to get wireless networking working. Luckily, getting the Centrino wireless LAN chip working in Ubuntu is quite easy, if you use the gnome-network-manager applet. Just go to System - Administration - Synaptic Package Manager. Then click 'Search' and set the 'look-in' field to 'name'. In the 'Search' text box type:

<pre>network-manager</pre>

: Figure 6. Installing the network manager applet
: [[Image:networkmanager.jpg]]

Click on the box beside 'network-manager' and click 'Mark for installation'. Do the same for 'network-manager-gnome'.

Now, to avoid problems Run:
: {{cmduser|gksudo gedit /etc/network/interfaces}}

Save a copy in /etc/network/interfaces.back for backup

After that, remove all lines except:
<pre>
auto lo
iface lo inet loopback
</pre>

Reboot your ThinkPad. An applet will show up in the gnome notification area. Click on it, and a list of detected wireless networks will be displayed. Simply click on one of them, enter any authentication details necessary, and you'll be connected to the wireless network.

: Figure 7. gnome-network-manager showing available wireless networks
: [[Image:available-accesspoints.jpg]]

===Non-Intel Network Cards===

Not all versions of the T60 have the Intel Wireless LAN as described above. Run the following command to see details about detected wireless cards:

: {{cmduser| lspci}}

Look for a line which shows detected network cards. Users of Intel network cards will see something similar to the following output:

<pre>03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)</pre>

If you see the above, you can jump to the next section. If you do not see the above, your network card is not Intel. You may see something similar to:

<pre>03:00.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)</pre>

If that's the output you get, you're going to have to take some additional steps to get wireless networking working. Read more at http://ubuntuforums.org/showthread.php?t=38972

running:

: {{cmdroot| dmesg | grep hal}}

may yield output like this:

<pre>
[17179590.420000] ath_hal: module license 'Proprietary' taints kernel.
[17179590.424000] ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
</pre>

Which suggests the hardware abstraction layer is in place.

If not, or if the output contains "HAL Status 13" it suggests your card is not supported by the current drivers, and you need to upgrade.

In some cases there is a problem with the mode (a,b,g etc) of the wireless connection. Try

: {{cmdroot| iwpriv ath0 mode 2}}

===Getting the ThinkVantage Buttons to work===

Ubuntu does not recognise all the ThinkVantage buttons correctly by default. This can be fixed quite easily. In a terminal, type:

: {{cmduser| sudo gedit /etc/X11/Xmodmap}}

Then paste the following in the file:

<pre>
keycode 234 = XF86Back
keycode 233 = XF86Forward
keycode 159 = XF86Start
keycode 162 = XF86AudioPlay
keycode 164 = XF86AudioStop
keycode 153 = XF86AudioNext
keycode 144 = XF86AudioPrev
keycode 227 = XF86LaunchF
keycode 249 = XF86ZoomIn
</pre>

Save and close the file, then logout and back in again. You can now assign the buttons to do anything you want. For example, use the Back and Forward buttons (next the cursor keys) to flip desktops using the cube effect in Beryl (set this using the Beryl settings manager). You can set most of the other keys using Gnome vis System - Preferences - Keyboard Shortcuts.

For the ThinkVantage and Zoom buttons, I used xbindkeys. Open a terminal and type:

: {{cmduser| sudo apt-get install xbindkeys xbindkeys-config}}
: {{cmduser| xbindkeys --defaults > ~/.xbindkeysrc}}
: {{cmduser| xbindkeys-config}}

This will bring up a but-ugly configuration screen. Just click "New" and assign a remark to the new shortcut. Then press "Grab" and press the combination you want (ex: The ThinkVantage button). You can then set the action you want executed in the "Action" field. I made my zoom button open the resolution properties (gnome-display-settings) and ThinkVantage open the Gnome control centre (gnome-control-center).

===Installing the ATI display drivers===

If your ThinkPad has an Intel graphics adapter, you should skip this section as Ubuntu installs the best driver automatically. Ubuntu does not install the ATI proprietary drivers by default because they are, er, proprietary. Luckily, installing them is easy enough. Open a terminal (Applications - Accessories - Terminal) and type the following:

: {{cmduser| sudo apt-get update}}
: {{cmduser| sudo apt-get install xorg-driver-fglrx fglrx-control}}

Now we make sure the proprietary driver is not disabled by the kernel. Type the following, and remove any lines referring to fglrx

: {{cmduser|sudo gedit /etc/default/linux-restricted-modules-common}}

{{HINT|An alternative to gedit (Gnome) is nano (sudo nano -w /etc...) for a CLI editor.}}

Finally, we need to configure the X server to use the ATI drivers. Type the following:

: {{cmduser|sudo depmod -a}}
: {{cmduser|sudo aticonfig --initial}}
: {{cmduser|sudo aticonfig --overlay-type<nowiki>=</nowiki>Xv}}

One last thing. In order to correct a very common problem of getting a jerky video display, type the following:

: {{cmduser|sudo gedit /etc/X11/xorg.conf}}

Scroll to the end of the file, and add the text below.

<pre>
Section "Extensions"
Option "Composite" "0"
EndSection
</pre>

Save the file and exit. Now, to apply the changes either press CTRL+ALT+Backspace or reboot. The resolution should have switched to 1400x1050 and everything should look prettier and render faster. Just to make sure everything is working, open up a terminal and type

: {{cmduser|fglrxinfo}}

This should display:

<pre>
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Mobility Radeon X1400 Generic
OpenGL version string: 2.0.6011 (8.28.8)
</pre>

The above is what I get on my ThinkPad, and you should see something similar. As long as you see your graphics card model listed, everything should be OK. If, instead, you see a bunch of lines containing 'Mesa' then you have a problem. In that case, I recommend consulting https://help.ubuntu.com/community/BinaryDriverHowto/ATI and the Ubuntu forums at http://ubuntuforums.org

===The Fingerprint Reader===

Although IBM does not officially support it, the fingerprint reader does in fact work with most Linux distributions. Getting it to work with Ubuntu can be a bit of a pain, but it does work. Basically, a bioAPI plugin is provided for PAM. PAM-aware applications such as GDM and gnome-screensaver will then automatically use the fingerprint reader, which is uber cool. Anyway, enough theory, I've probably lost the newbies amongst you already. Go to http://www.qrivy.net/~michael/temp/ and download the latest bioapi package (at the time of writing, bioapi_1.2.3_i386.deb). When asked, tell Firefox to open the file with the GDebi package installer.

That will install bioAPI. What we need now is the driver for our fingerprint device, which is manufactured by UPEK. Go to http://www.upek.com/support/dl_linux_bsp.asp and download the latest version, currently UPEK_BSP_LIN_1.0.zip. Extract this file, then open a terminal (and don't close it until I say so).

: {{cmduser|cd /path/to/where/you/extracted/the/file}}
: {{cmduser|sudo bash}}
: {{cmdroot|sh install.sh /usr/lib}}

Now we need to assign the right permissions so non-root applications can use the driver:

: {{cmdroot|addgroup --system bioapi}}
: {{cmdroot|addgroup --system usbfs}}
: {{cmdroot|adduser yourusername bioapi}}
: {{cmdroot|adduser yourusername usbfs}}
: {{cmdroot|chown -R root:bioapi /usr/var/bioapi/}}
: {{cmdroot|chmod -R 770 /usr/var/bioapi/}}
: {{cmdroot|chown -R root:usbfs /proc/bus/usb}}
: {{cmdroot|chmod -R g+X /proc/bus/usb}}

Of course, replace 'yourusername' with the username you use to login. Now, we need to set the usb file system (usbfs) to be usable by users in the usbfs group. To do this, we need to determine the group ID of the usbfs group. Type the following:

: {{cmdroot|cat /etc/group | grep usbfs | cut -d':' -f 3}}

In my case the number is 116, it might be different for you. Now, open the file /etc/fstab:

: {{cmdroot|gedit /etc/fstab}}

and type the following:

<pre>none /proc/bus/usb usbfs defaults,devgid=116,devmode=0660,busgid=116,busmode=0770,listgid=116,listmode=0660 0 0</pre>

Please type the above code in one line in your file. Remember to replace 116 if you got a different number with the previous cat command. The last permission-related thing we need to fool around with is UDEV. Open the udev permissions file

: {{cmdroot|gedit /etc/udev/rules.d/40-permissions.rules}}

and find the line:

<pre>SUBSYSTEM=="usb_device", MODE="0664"</pre>

It's line 65 in my file. Change it so it looks like this:

<pre>SUBSYSTEM=="usb_device", MODE="0660", GROUP="usbfs"</pre>

Now we need to enroll our fingerprint with the system. To do this, we need a utility called Sample, which is only distributed in source-code form with the driver. This is great, only I couldn't get it to compile on Ubuntu. Luckily, there is a binary version available from one of the earlier releases of the driver (beta 2). To get this, download it from ftp://linux:Tuc-nak3@delta.upek.com/TFMESS_BSP_LIN_1.0beta2.zip. Now, extract the file and type:

: {{cmdroot|cd /path/to/where/you/extracted/the/archive}}
: {{cmdroot|cd NonGUI_sample}}
: {{cmdroot|chmod a+x Sample}}
: {{cmdroot|./Sample}}

Press (e) to enroll a new user, and enter your username when asked for the user ID. You will be asked to swipe your finger three times. Now press (v) and swipe your finger, a green check should be displayed showing you have successfully authenticated.

If the Sample utility does not work, you may not have the PAM development modules installed. Try this:

: {{cmdroot|sudo apt-get install libpam0g-dev}}

: Figure 8. The fingerprint swipe prompt
: [[Image:touchchip.jpg]]

Wonderful! Now, quit the application (q) and type exit to become a normal user. A file called yourusername.bir should have been created, copy this to your home directory:

: {{cmdroot|cp yourusername.bir /home/yourusername/}}

You can now close the terminal window. The next step is to install the BioAPI plug-in for PAM, and to make applications use the plugin. So, get the pam_bioapi plugin from http://www.nax.cz/pub/bioapi/pam_bioapi/pam-bioapi_0.3.0.tar.gz and extract it. Now open a terminal and type:

: {{cmduser|sudo apt-get install build-essential}}
: {{cmduser|sudo apt-get install libpam0g-dev}}

Now, you can compile and install the plugin

: {{cmduser|cd /path/to/where/you/extracted/the/arcive}}
: {{cmduser|./configure --libdir<nowiki>=</nowiki>/lib --enable-file-store && make}}
: {{cmduser|sudo make install}}

That's installed the plugin. Now, open a terminal and type the following:

: {{cmduser|cd ~}}
: {{cmduser|sudo bash}}

This will open a root session. Please do not close this until instructed. Now, paste the following scary command:

<pre>
SERIAL=`BioAPITest | sed -ne "/Fingerprint/{n;n;s/^.*: $.\{9\}$$.\{4\}$$.\{4\}$$.\{4\}$$.*$/\1-\2-\3-\4-\5/gp}"`
</pre>

Type the following to register your username and serial with the bioAPI.

: {{cmdroot|mkdir -p /etc/bioapi/pam/$SERIAL}}
: {{cmdroot|cp yourusername.bir /etc/bioapi/pam/$SERIAL}}
: {{cmdroot|exit}}

Phew. Now, to make applications actually use the fingerprint reader. Open a terminal window, and type:

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

Delete everything in the file, and paste this instead:

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

Save and close the file. That will make all PAM-aware applications use the fingerprint reader. Unfortunately, this also includes sudo. Since sudo is a command line application, it will display prompts in a terminal for you to swipe your finger, which is all well and good. The problem with this is that many Ubuntu administrative applications (such as Synaptic) use gksu to present a graphical front-end to sudo, which will output messages on the command line which you'll never see. Result? Administrative programs won't work from the gnome menu. The solution is to make sudo use the good old password. Open a terminal and type:

: {{cmduser|sudo gedit /etc/pam.d/sudo}}

Delete everything in the file, and instead paste:

<pre>
#%PAM-1.0

#@include common-auth
auth required pam_unix.so nullok_secure
@include common-account
</pre>

If you like to use the fingerprint reader in the terminal too, you can use the following /etc/pam.d/sudo file instead:

<pre>
#%PAM-1.0

#@include common-auth
auth sufficient pam_unix.so nullok_secure
auth required pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
password required pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
@include common-account
</pre>

With this file, you are first asked to provide your password, but you can just press enter and then you will be asked to swipe your finger.

Now, save the file and close it, and reboot your system. GDM will ask you for a username, and then show a pretty prompt where you can scan your fingerprint! Same goes for gnome-screensaver when you set it to lock. Sometimes gnome-screensaver will not display the prompt, but you should still swipe your finger and be able to log back in.

{{NOTE|In case you use Kubuntu KDM won't show you a prompt. Just press Enter instead of a password and then (when the cursor stops blinking) swipe your finger.}}

===Bluetooth with Mobile Phones/PDAs===

Rather strangely, Ubuntu seems to have taken a step backwards with Bluetooth usability in Edgy. What worked out of the box with Dapper, now requires configuration. First, open System - Preferences - Sessions and go to the Startup Programs tab. Then, find the entry labeled 'bt-applet --sm-disable'. Highlight it and click disable. Click add and in the command field type 'bt-applet'. Repeat this process, adding an entry for 'gnome-obex-server'. Now, open Synaptic Package Manager (System - Administration - Synaptic Package Manager) and click Search. Type 'gnome-bluetooth' to find the package, then mark it for installation. Now repeat this process for 'bluez-passkey-gnome'. Click apply to make changes.

Now that everything is installed, log-out of Gnome and log back in again. From your phone/PDA, search for devices until you see your ThinkPad (the hostname will be displayed). Pair with the device. When asked for a passkey, enter 1234, which is the default. If you want to change your passkey (and you should), open a terminal and type:

: {{cmduser|sudo gedit /etc/bluetooth/hcid.conf}}

Find the line which says 'Default PIN for incoming connections' and change the PIN on the line beneath it:

<pre>
# Default PIN code for incoming connections
passkey "4017";
</pre>

Save and close the file, then type:

: {{cmduser|sudo /etc/init.d/bluetooth restart}}

You will now be able to use your new PIN code. To send files from your device to the ThinkPad, simply select the file you want to send and click Send Via Bluetooth (or whatever option your device presents). A dialog will pop-up in Gnome showing you a new file has been received.

: Figure 9. Gnome informing us that a file has been received
: [[Image:bluetooth.jpg]]

Sending files from your ThinkPad to your device requires more effort. The way it should work is that you right-click on a file, click send to, then make sure 'Bluetooth (OBEX)' is selected. Your device should be displayed and you could just click send. Unfortunately, due to a bug in gnome-bluetooth (described in https://launchpad.net/distros/ubuntu/+source/gnome-bluetooth/+bug/70718) this method does not work. If it does work for you, the bug has been solved and you can skip the rest of this section.

Your only other option is to use the command line to send files to your device. Open a terminal, then type:

: {{cmduser|hcitool scan}}

A list of detected bluetooth devices will be shown, for example, my output shows the following:

<pre>
Scanning ...
00:09:DD:60:02:EB Photosmart 8100 series
00:14:A7:99:3C:1F ThElInK
</pre>

The first field is the MAC address of the device, the second is the name of the device. In this case my bluetooth printer and mobile phone (ThElInK) were detected. In order to send files to my phone, I use:

: {{cmduser|gnome-obex-send -d 00:14:A7:99:3C:1F myPicture.jpg}}

Replace the MAC address with that of your device and myPicture.jpg with the file you want to send.

===TrackPoint Scrolling===

By default you can use the right and bottom edges of your touchpad to scroll through documents. If you use the TrackPoint instad of the touchpad (and believe me, you should), you'll find that scrolling is disabled by default. To enable it, open a terminal and type:

: {{cmduser|sudo gedit /etc/X11/xorg.conf}}

Now find the entry for your TrackPoint device. In my configuration file, the TrackPoint entry is the first mouse entry, after the keyboard entry, and looks something like this:

<pre>
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection
</pre>

Right after this entry is my touchpad entry. My entry is on line 66, but yours may be different. Now, add the follwing two options in that InputDevice section:

<pre>
Option "EmulateWheel" "on"
Option "EmulateWheelButton" "2"
</pre>

Save and exit the file. Restart your ThinkPad (or logout, and press CTRL-ALT-BACKSPACE). You should now be able to scoll by holding down the middle button for your TrackPoint and using the TrackPoint to scroll.

===Getting Multimedia to Work===

Due to patents and similar legal crap, Ubuntu will not play most media files by default. You also won't get browser plugins for multimedia. Luckily, this is easily fixed. Open a terminal and type the following:

: {{cmduser|sudo cp /etc/apt/sources.list /etc/apt/sources.list.backup}}
: {{cmduser|sudo gedit /etc/apt/sources.list}}

Delete everything in the file, and instead paste the following:

<pre>
deb-src http://archive.ubuntu.com/ubuntu edgy main restricted universe multiverse
#deb http://archive.ubuntu.com/ubuntu edgy-proposed main restricted universe multiverse

## MAJOR BUG FIX UPDATES produced after the final release
deb-src http://archive.ubuntu.com/ubuntu edgy-updates main restricted universe multiverse

## UBUNTU SECURITY UPDATES
deb http://security.ubuntu.com/ubuntu edgy-security main restricted universe multiverse
deb-src http://security.ubuntu.com/ubuntu edgy-security main restricted universe multiverse

## BACKPORTS REPOSITORY (Unsupported. May contain illegal packages. Use at own risk.)
#deb http://archive.ubuntu.com/ubuntu edgy-backports main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu edgy-backports main restricted universe multiverse

## PLF REPOSITORY
deb http://packages.freecontrib.org/ubuntu/plf edgy-plf free
deb-src http://packages.freecontrib.org/ubuntu/plf edgy-plf free
deb http://packages.freecontrib.org/ubuntu/plf edgy-plf non-free
deb-src http://packages.freecontrib.org/ubuntu/plf edgy-plf non-free

## CANONICAL COMMERCIAL REPOSITORY (Hosted on Canonical servers, not Ubuntu
## servers. RealPlayer10, Opera, DesktopSecure and more to come.)
deb http://archive.canonical.com/ubuntu edgy-commercial main

## Listen
#deb http://theli.free.fr/packages/ edgy listen

## Automatix repo
deb http://www.getautomatix.com/apt edgy main
</pre>

Now, open a terminal and type the following:

: {{cmduser|wget <nowiki>http://packages.freecontrib.org/ubuntu/plf/12B83718.gpg</nowiki> -O- <nowiki>|</nowiki> sudo apt-key add -}}
: {{cmduser|wget <nowiki>http://www.getautomatix.com/apt/key.gpg.asc</nowiki>}}
: {{cmduser|gpg --import key.gpg.asc}}
: {{cmduser|gpg --export --armor 521A9C7C <nowiki>|</nowiki> sudo apt-key add -}}
: {{cmduser|sudo apt-get update}}
: {{cmduser|sudo apt-get install automatix2}}
: {{cmduser|wget <nowiki>http://easyubuntu.freecontrib.org/files/easyubuntu-3.023.tar.gz</nowiki>}}
: {{cmduser|tar -zxf easyubuntu-3.023.tar.gz}}
: {{cmduser|cd easyubuntu}}
: {{cmduser|cp packagelist-dapper.pot packagelist-edgy.pot}}
: {{cmduser|cp packagelist-dapper.xml packagelist-edgy.xml}}
: {{cmduser|sudo python easyubuntu.in}}

Don't worry if you get errors from the Ubuntu PLF repository. PLF mirrors are about as stable as wild bull in a farm full of cows. Select what you want to install from the resulting window. Make sure you do not select the totem-mozilla plugin, as this just doens't work, for me at least. When EasyUbuntu has finished installing packages, you should be returned to a terminal, which you can close. Now go to Applications - System Tools - Automatix. Read and agree to the warning. Check what you want to install. Make sure you check 'Mplayer and FF plugin'. When ready, click the 'install' button. That should get multimedia working nicely.

: Figure 10. The Automatix user interface
: [[Image:automatix.jpg]]

===Beryl - fancy 3D desktop===

MAC OS X has Aqua and Windows Vista has Aero. Well, Linux has XGL/Beryl which can get effects which are as good looking (or sometimes better!) than the former two. Installing Beryl on Ubuntu is not that hard. First, open a terminal and type the following:

: {{cmduser|sudo gedit /etc/apt/sources.list}}

At the end of the file, append the following:

<pre>
##Beryl
deb http://ubuntu.beryl-project.org/ edgy main
</pre>

Save and close the file. Now type:

: {{cmduser|wget <nowiki>http://ubuntu.beryl-project.org/root@lupine.me.uk.gpg</nowiki> -O- <nowiki>|</nowiki> sudo apt-key add -}}
: {{cmduser|sudo apt-get update}}

ATI Users Only: type

: {{cmduser|sudo apt-get install xserver-xgl}}

Now, to install beryl:

: {{cmduser|sudo apt-get install beryl emerald-themes}}

To make Ubuntu use the 3D effects. Open a terminal:

: {{cmduser|sudo gedit /usr/local/bin/startxgl.sh}}

In that file, paste the following if you use an ATI card:

<pre>
#!/bin/sh
Xgl -fullscreen :1 -ac -br -accel glx:pbuffer -accel xv:pbuffer &
sleep 4
export DISPLAY=:1
cookie="$(xauth -i nextract - :0 | cut -d ' ' -f 9)"
xauth -i add :1 . "$cookie"
exec gnome-session
</pre>

If you use an Intel card, paste the following instead:

<pre>
#!/bin/sh
beryl-manager
sleep 4
exec gnome-session
</pre>

Save the file and close. Now we need to make the file executable:

: {{cmduser|sudo chmod a+x /usr/local/bin/startxgl.sh}}

All that's left now is to create a login script which makes gnome use the 3D effects. In a terminal, type:

: {{cmduser|sudo gedit /usr/share/xsessions/xgl.desktop}}

Now, in this file paste:

<pre>
[Desktop Entry]
Encoding=UTF-8
Name=Xgl
Exec=/usr/local/bin/startxgl.sh
Icon=
Type=Application
</pre>

Save and close the file. Now type:

: {{cmduser|sudo gedit /usr/local/bin/start_beryl.sh}}

In this file, paste:

<pre>
#!/bin/bash
#
# Start beryl-manager within gnome-session
#
if [ `ps -A -o comm | grep -c '^Xgl$'` == "1" ]; then
DISPLAY=:1 beryl-manager
DISPLAY=:1 beryl-xgl
else echo "${0}: Error: beryl-manager not launched. Xgl not running?"
fi
</pre>

Now make the file executable:

: {{cmduser|sudo chmod a+x /usr/local/bin/start_beryl.sh}}

Now go to System - Preferences - Sessions, go to the Startup Programs tab, and click add, then type

: {{cmduser|/usr/local/bin/start_beryl.sh}}

Now, reboot your ThinkPad. When you come to the login screen, click the 'Sessions' button on the bottom left corner, and select XGL. login, et voila! beautiful 3D effects!

: Figure 11. Beryl's Cube effect
: [[Image:cube.jpg]]

If you have NetBeans installed, try launching it now. It probably won't work due to Beryl. Luckily, this is easily solved. Open a terminal and type:

: {{cmduser|sudo gedit /etc/environment}}

Then add the following line to the end of the file.

<pre>AWT_TOOLKIT="MToolkit"</pre>

Now save, close and reboot. Netbeans should now work!

===Problem: Can't add programs to session===

So you tried to add something to your startup programs, it shows up in the list, but it doesn't start up. You then launch the sessions program again, only to find your program has disappeared from the list. This problem is being caused by incorrect permissions in your home directory, and can happen on some occasions. To fix it, open a terminal and type the following:

: {{cmduser|sudo chown -R username:usergroup /home/username/.config/}}

Replace username with your username and usergroup with your group (by default, in Ubuntu your usergroup is the same as your username). Everything should be OK now!

===Problem: Virtual terminals not working===

One problem I had after installing the ATI drivers was that virtual terminals stopped working. Instead of seeing a console when pressing CTRL+ALT+F1...F6 I was seeing a yellow/orange garbled output. Luckily, solving this with ATI drivers is trivial. Open a terminal, and type:

: {{cmduser|sudo gedit /boot/grub/menu.lst}}

Find the line which says

<pre>#defoptions=quiet splash</pre>

and replace it with

<pre>#defoptions=quiet splash vga=791</pre>

Now, find the line which boots the kernel you are currently using, this is just under '## ## End Default Options ##. In the 'kernel' line, add:

<pre>vga=791</pre>

Before:

<pre>kernel /vmlinuz-2.6.17-10-generic root=/dev/sda7 ro quiet splash</pre>

After:

<pre>kernel /vmlinuz-2.6.17-10-generic root=/dev/sda7 ro quiet splash vga=791</pre>

Now save and exit the file, and reboot. Virtual terminals should now work. If you use Intel drivers, you're going to have to bite the bullet and remove the 'splash' keyword from both the defoptions and kernel lines. You'll lose the pretty bootup screen, but at least virtual terminals will work, which are important to recover a crashed system.

===Problem: Microphone doesn't work===

On my system, I could get the microphone to work by simply un-muting the correct channels using alsamixer. To do this, open the ALSA mixer GUI form a terminal:

: {{cmduser| alsamixer}}

The alsamixer GUI will be displayed:

[[Image:alsamixer.jpg]]

Now make sure all outputs are un-muted. Scroll through the outputs using the {{key|LEFT}} and {{key|RIGHT}} arrow keys, and press {{key|M}} to un-mute a channel (muted channels show an MM symbol). Use the {{key|UP}} and {{key|DOWN}} arrow keys to raise and lower the volume for each channel. Press {{key|TAB}} to switch to capture settings. Select Mic and press {{key|SPACE}} to enable the microphone. Now enable microphone capture my selecting Capture, and pressing {{key|SPACE}}. Depending on your microphone, you may need to enable MIC boost to get some extra umph from your sound input.

The volume of the input channels depends on your microphone. These settings worked best for me on a desktop microphone:

: MIC: 71
: MIC Boost: 33
: Capture: 73

Now test the microphone by going to Applications - Sound & Video - Sound Recorder and select "Capture" in the "Record from input" field. On my system, mixing worked too - meaning I could play games whilst talking on TeamSpeak or Skype.

After following the above steps, your microphone may still not work, which appears to be linked to the a missing file /etc/asound.names. Executing

: {{cmduser|sudo alsactl names}}
: {{cmduser|sudo alsactl store}}

to generate /etc/asound.names and /var/lib/alsa/asound.state seems to fix sound problems.

===Problem: I don't have any sound!===

If Ubuntu seems to recognize your sound-card (82801G ICH7) but still cannot initialize it (so you don't hear a thing), you have most probably turned the modem off in the system-bios.
If you turn it on again, it should work again.
If you don't want to do that [http://www.ubuntuforums.org/showthread.php?t=279241 this] might help you.

===Problem: I keep logging out!===

If you're using Beryl, and find that you keep getting logged out, you've just encountered one of Beryl's most annoying bugs. Shift+Backspace causes a logout. To fix this, open a terminal and type:

: {{cmduser|gedit /home/username/annoymenot.sh}}

Remember to replace 'username' with your username. Now, in this file type:

: {{cmduser|xmodmap -e "keycode 22 <nowiki>=</nowiki> BackSpace BackSpace Terminate_Server" }}

Save and close the file, and make it executable:

: {{cmduser|chmod 755 /home/username/annoymenot.sh}}

Now go to System - Preferences - Session, Startup Programs. Click add, and type

: {{cmduser|/home/username/annoymenot.sh}}

Logout and back in, problem solved! While you're at it, how about getting the start button to work? Go to System - Preferences - Keyboard - Layout Options - Alt/Win Key behaviour and select 'Super is mapped to Win keys (default)'.

===Problem: Hibernate (Suspend to Disk) does not work!===

It was possible on some machines to get hibernate working by installing the hibernate script. However, when too many programs where open I got a "Not enough memory" error. You will have to try it.

To install the script type

: {{cmduser|sudo apt-get install hibernate}}

To go to hibernate type

: {{cmduser|sudo hibernate}}

The computer will go to hibernate and turn off. To switch it on again, you will have to press the power button. It will boot and restore the system as you left it.

===Desktop envy===

We're living in an age of desktop prettyness, and Linux can be just as pretty as MAC OS X or Vista. You've already got Beryl installed. Now go to Applications - Accesories - gDesklets. If the gDesklets entry is not there, make sure you install it, either using Synaptic or Automatix. Desklets are small programs you can add to your desktop, ala OS X's Deskbar or Vista's Sidebar. To make them start on boot, add gdesklets in System - Preferences - Sessions, Startup Programs.

Another cool program is cairo clock. Download it from http://macslow.thepimp.net/projects/cairo-clock/cairo-clock_0.3.2-1_i386.deb and install it by double-clicking. To make it start automatically, add it to your sessions as mentioned above. I've found the following command makes it work best for me:

<pre>cairo-clock -s -w 175 -g 175 -x 1219 -y 7 -t radium</pre>

Finally, make sure you click that Ruby icon in your notification area, it allows you to configure Beryl to do all sorts of cool stuff!

===Conclusion===

Well, that's about it! A dream Linux system on a dream laptop! Check out these cool technologies for an even better system:

* Beagle
* Tomboy
* Deskbar

===References===

* ATI on Ubuntu - https://help.ubuntu.com/community/BinaryDriverHowto/ATI
* Garbled Virtual Terminal Bug - https://launchpad.net/distros/ubuntu/+source/usplash/+bug/63558
* Beryl logout Bug - http://forum.beryl-project.org/viewtopic.php?p=1295&sid=6feedd09a7f01bca68feb05a5f2f033c
* Beryl Netbeans Bug - http://ubuntuforums.org/showthread.php?t=252594
* Beryl on Ubuntu - http://wiki.beryl-project.org/index.php/Install/Ubuntu/Edgy/XGL
* Home directory permissions bug - http://www.ubuntuforums.org/showthread.php?p=1789997
* gnome-bluetooth bug - https://launchpad.net/distros/ubuntu/+source/gnome-bluetooth/+bug/70718
* Atheros network cards on Ubuntu - http://ubuntuforums.org/showthread.php?t=38972
* Enabling the microphone - http://ubuntu.wordpress.com/2005/12/05/fixing-the-errant-microphone/
* Enabling the microphone (2) - http://ubuntuforums.org/showthread.php?t=272166

Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60

2007-01-24T04:58:21Z

Ischg: /* The Fingerprint Reader */

Created by: [[User:Keithvassallo|Keithvassallo]] 14:39, 16 December 2006 (CET)

Thanks for valuable contributions by:

: [[User:Ischg|Ischg]]
: [[User:Soon|Soon]]
: [[User:Mgrusin|Mgrusin]]
: [[User:Mattcohn|Mattcohn]]
: [[User:Dchao|Dchao]]
: [[User:The.ant|The.ant]]
: [[User:Stevie|Stevie]]
: [[User:Gagarine|Gagarine]]

Also, thanks to contributions by Malta Linux User Group (http://www.linux.org.mt) members:

: dave abrahams
: Limo Driver

===Abstract===

This article describes how to get Ubuntu Linux 6.10 (Edgy) installed on an IBM/Lenovo ThinkPad T60. It's not meant to be a definite guide to installing Ubuntu (the Ubuntu Guide at http://www.ubuntuguide.org does a very good job of that). This article is meant to describe how to get most of the ThinkPad features working on Ubuntu system. It also discusses how to get Multimedia, some cool-looking effects such as Beryl, gDesklets and similar working on Ubuntu. Finally, we discuss some common problems encountered on Ubuntu and ThinkPads alike.

{{NOTE|I am in no means an expert, the methods described here are those which got everything to work for me - your mileage may vary. A big thank you to all ThinkWiki users who keep contributing on improving this article.}}

===My ThinkPad===

Although this guide should work on most recent ThinkPads, I cannot guarantee that. These are the specifications of my machine. The closer your specs are, the greater the chance of success.

: Figure 1. ThinkPad T60 2007, complete with Tux sticker :-)
: [[Image:thinkpad.jpg]]

* Lenovo ThinkPad T60 2007.
* Intel Centrino Duo T2400 / 1.83 GHz.
* Mobile Intel 945PM Express Chipset.
* Intel Wireless LAN.
* Integrated Bluetooth.
* ATI Mobility Radeon X1400 - PCI Express x16, 128MB dedicated RAM.
* 100 GB - Serial ATA-150 Hard Drive.
* 15' TFT Active Matrix Display (1400x1050).

That's basically all you need to know. As far as I know, all other features are common to all ThinkPads manufactured by Lenovo since they acquired IBM's computer business.

===Why Ubuntu? (or rather, Why not SUSE?)===

In June 2006, Lenovo announced it would be shipping ThinkPad T60p laptops with SUSE Linux Enterprise Desktop (SLED) 10 pre-installed, since SLED apparently supports all of the features of the T60p. I contacted my local IBM supplier, who said that Lenovo were no longer manufacturing the T60p, since the company which was making the displays went out of business. This meant I could not get a T60p with SLED pre-installed. I decided to go for the T60 2007, which is the closest thing I could find to the T60p. This comes with Windows XP Professional pre-installed.

I first tried to get SLED installed on the T60. Although it did indeed install, and most features worked, I soon got bored of SLED. Firstly, SLED uses Gnome 2.12, which is by now ancient. Secondly, although the Lenovo utilities do work on SLED, they only work well if you use KDE as your defauly desktop environment, which is a pity since I'm a Gnome user. The utilities were very unstable to me too. Finally, what made me give up SLED was the usual problem - it's an RPM based distribution. Once you start using Debian derivatives, with their apt based installer, you won't want to go back. That's when I decided to try Ubuntu, and have not regretted it since.

===What Works?===

* Ubuntu and all programs it comes with.
* Most of the function keys, except the ones mentioned below
* The fingerprint reader.
* The ATI proprietary graphics drivers.
* Brightness, Volume and Mute with OSD (On-Screen Display).
* ThinkLight, TrackPoint II and the touchpad.

===What Doesn't Work? (Known Issues)===

* FN+F7, FN+F8, FN+F9.
* Sending files to Bluetooth devices via GUI.
* Suspend to Disk (works with sufficient memory).
* Suspend to RAM (though it works on occasions).

There are probably ways and means to get the offending buttons to work, I've tried several fora but none seem to address my exact problem. I'll update this article should I find out anything. As for the Bluetooth bug, this is a HAL bug and can only be fixed by a future update. Suspend to Disk and Suspend to RAM are broken apparently due to the ATI drivers. Again, this can only be fixed by ATI.

===First Things First - Creating a Windows Recovery Disc===

If you've purchased a T60, chances are it came with Windows XP Professional. The other option is for you to have FreeDOS installed, in which case you can skip this section. You could remove the Windows partition altogether, and reserve your ThinkPad for Linux, but that's not the route I've chosen. The ThinkVantage utilities in Windows allow you to do a lot of cool things, such as set-up a boot-up fingerprint security scan. You can't do this from Linux (as far as I know) so it's best to leave the Windows partition in place. So, boot your ThinkPad and complete the Windows XP setup (which asks you to add a user account and enroll yourself using the ThinkVantage Client Security Solution). While you're there, use the ThinkVantage productivy centre to enroll your fingerprint (I suggest enrolling more than one) and make sure you check the option to require a fingerprint scan on boot (not for security, for geek points). When you reboot, press ESC or F2 to get to BIOS, and make sure you check the option to require a supervisor password. This will make your ThinkPad prompt you for your fingerprint when you power it up.

: Figure 2. Configuring fingerprint security from Windows
: [[Image:winprint.jpg]]

Now that's working, you should create a recovery DVD using the ThinkVantage recovery utilities. This will allow you to recover your Windows installation should you manage to screw your partitions up in the following stages. I highly recommend you do this, as Lenovo does not provide Windows XP CDs with this Laptop - so the hard disk partition is all you've got. Once this is done, we're ready to install Ubuntu!

: Figure 3. Creating recovery discs from Windows
: [[Image:recovery.jpg]]

===Getting Ubuntu installed===

Download the latest Edgy live CD from the Ubuntu website, you can find a list of mirrors at http://www.ubuntu.com/products/GetUbuntu/download#currentrelease. You may also try Kubuntu, Edubuntu or any of it's derivatives, but I'll stick with Ubuntu here for simplicity's sake. Once that's downloaded, burn the ISO to disc using any program of your choice (If this is your first Linux experience and you're using Windows, try using Nero - http://www.nero.com).

Once the burning process is complete, reboot your machine ensuring that the Ubuntu CD is in the drive. You should see an Ubuntu menu. If you don't, your BIOS is not set to boot from CD. Reboot your ThinkPad and change the boot order from BIOS (by default ThinkPads boot from CD-ROM before the hard disk, so this is probably not necessary). Once the menu shows up, select 'Start or install Ubuntu' and let it boot. This will take a while as everything is loaded from CD. You should eventually end up in a Gnome desktop. If you see an error about the Gnome Settings Daemon not being able to load, simply ignore it, as this is not necessary for now. For the purposes of the installation, it's best if you have a wired ethernet connection, as it's unlikely the wireless network card will work until we boot into our installed Ubuntu system.

: Figure 4. Select the first option to start Ubuntu
: [[Image:boot.jpg]]

Double-Click on the 'install' icon on the Desktop to start installation. The installation should be pretty straight-forward. If you need additional help, check out the walk-through with screen-shots at http://www.debianadmin.com/ubuntu-edgy-eft-desktop-installation-with-screenshots.html. The only stage at which we need to make changes is the partitioning stage. This to make sure we preserve our Windows partition, and the IBM vendor_diag partition which allows recovery of the laptop when things go hay-wire. In the 'Prepare disk space' section of the installer, select the third option, 'Manually edit partition table'. A bar will be displayed showing your existing partitions. If you have Windows installed you will see two partitions. The first is a 4.89 GB IBM Vendor Diagnostic partition, which we do not want to touch. The second will be your Windows partition, which will fill the rest of the disk. Click on this partition, Then click the 'Resize/Move' button. I resized my Windows partition to 24 GB. This is enough to accommodate the 10 GB already in use on that partition, as well as giving Windows another 14 GB of free space. 6 GB of free space would probably be enough though.

Now it's time to create partitions for Linux. You need at least two partitions; a swap partition which should be roughly double the amount of RAM you have, and a root partition to install Linux. I opted for four partitions, as follows:

<table border=1>
<tr><td>'''Purpose'''</td><td>'''Size'''</td><td>'''File-System'''</td></tr>
<tr><td>Swap</td><td>2 GB</td><td>swap</td></tr>
<tr><td>/boot</td><td>5 GB</td><td>ext3</td></tr>
<tr><td>/ (root)</td><td>20 GB</td><td>ext3</td></tr>
<tr><td>/home</td><td>37.25 GB (what's left of the disk)</td><td>ext3</td></tr>
</table>

To create these paritions, click on the 'New' button and select 'Extended Partition' in the 'create as' drop-down list. Leave all other settings as-is, and click 'Add'. Now, click on the newly created partition, and create each of the partitions you want to create, simply specify the size of the partition in the 'New Size (MiB)' text box. To convert GB to MiB, multiply by 1024. So for your swap partition you should specify a size of 2048. Repeat until you have created all the required partitions. If you follow my parition layout, the partition editor should look something like Figure 5.

: Figure 5. Our partitions, ready to be created
: [[Image:partitioning.jpg]]

You will not see mount-points in your diagram, because the screen-shot above was taken after they were assigned, but you should get the general idea. After this screen, you will be asked to assign mount-points to the partitions you have just created. If you created the partitions in the same order I did, you can assign mount points as I have (i.e. /dev/sda5 for swap, /dev/sda6 for /boot, /dev/sda7 for /, /dev/sda8 for /home). Additionally, I mounted my Windows partition as /media/sda1 and my IBM Vendor Diagnostic partition as /media/sda2. These are optional. After this step, continue installation as normal. When the installation is complete, click the 'reboot' button to restart into your fresh Ubuntu System.

When booting, the GRUB boot-loader will be displayed, asking you what you want to load. You will probably see four options. The first two being Ubuntu Linux and Ubuntu Linux recovery mode (showing the kernel version). The other two will be Microsoft Windows XP, and 'Other Windows XP/2000/NT' partition. This is your IBM Vendor Diagnostic partition, which is based on the Windows kernel, apparently. Select the first entry to boot Ubuntu. The next time you boot Windows, it will bring up a chkdsk screen. This is entirely normal and happens because we have resized the Windows partition. Make sure you do not skip this check and let it complete.

===Wireless LAN===

{{WARN|Another ThinkWiki user notes that not all T60s come with the Intel wireless chip. If you are not entirely sure what wireless NIC you use, please read the following section (Non-Intel Network Cards).}}

The first thing we should do is to get wireless networking working. Luckily, getting the Centrino wireless LAN chip working in Ubuntu is quite easy, if you use the gnome-network-manager applet. Just go to System - Administration - Synaptic Package Manager. Then click 'Search' and set the 'look-in' field to 'name'. In the 'Search' text box type:

<pre>network-manager</pre>

: Figure 6. Installing the network manager applet
: [[Image:networkmanager.jpg]]

Click on the box beside 'network-manager' and click 'Mark for installation'. Do the same for 'network-manager-gnome'.

Now, to avoid problems Run:
: {{cmduser|gksudo gedit /etc/network/interfaces}}

Save a copy in /etc/network/interfaces.back for backup

After that, remove all lines except:
<pre>
auto lo
iface lo inet loopback
</pre>

Reboot your ThinkPad. An applet will show up in the gnome notification area. Click on it, and a list of detected wireless networks will be displayed. Simply click on one of them, enter any authentication details necessary, and you'll be connected to the wireless network.

: Figure 7. gnome-network-manager showing available wireless networks
: [[Image:available-accesspoints.jpg]]

===Non-Intel Network Cards===

Not all versions of the T60 have the Intel Wireless LAN as described above. Run the following command to see details about detected wireless cards:

: {{cmduser| lspci}}

Look for a line which shows detected network cards. Users of Intel network cards will see something similar to the following output:

<pre>03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)</pre>

If you see the above, you can jump to the next section. If you do not see the above, your network card is not Intel. You may see something similar to:

<pre>03:00.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)</pre>

If that's the output you get, you're going to have to take some additional steps to get wireless networking working. Read more at http://ubuntuforums.org/showthread.php?t=38972

running:

: {{cmdroot| dmesg <nowiki>|</nowiki> grep hal}}

may yield output like this:

<pre>
[17179590.420000] ath_hal: module license 'Proprietary' taints kernel.
[17179590.424000] ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
</pre>

Which suggests the hardware abstraction layer is in place.

If not, or if the output contains "HAL Status 13" it suggests your card is not supported by the current drivers, and you need to upgrade.

In some cases there is a problem with the mode (a,b,g etc) of the wireless connection. Try

: {{cmdroot| iwpriv ath0 mode 2}}

===Getting the ThinkVantage Buttons to work===

Ubuntu does not recognise all the ThinkVantage buttons correctly by default. This can be fixed quite easily. In a terminal, type:

: {{cmduser| sudo gedit /etc/X11/Xmodmap}}

Then paste the following in the file:

<pre>
keycode 234 = XF86Back
keycode 233 = XF86Forward
keycode 159 = XF86Start
keycode 162 = XF86AudioPlay
keycode 164 = XF86AudioStop
keycode 153 = XF86AudioNext
keycode 144 = XF86AudioPrev
keycode 227 = XF86LaunchF
keycode 249 = XF86ZoomIn
</pre>

Save and close the file, then logout and back in again. You can now assign the buttons to do anything you want. For example, use the Back and Forward buttons (next the cursor keys) to flip desktops using the cube effect in Beryl (set this using the Beryl settings manager). You can set most of the other keys using Gnome vis System - Preferences - Keyboard Shortcuts.

For the ThinkVantage and Zoom buttons, I used xbindkeys. Open a terminal and type:

: {{cmduser| sudo apt-get install xbindkeys xbindkeys-config}}
: {{cmduser| xbindkeys --defaults > ~/.xbindkeysrc}}
: {{cmduser| xbindkeys-config}}

This will bring up a but-ugly configuration screen. Just click "New" and assign a remark to the new shortcut. Then press "Grab" and press the combination you want (ex: The ThinkVantage button). You can then set the action you want executed in the "Action" field. I made my zoom button open the resolution properties (gnome-display-settings) and ThinkVantage open the Gnome control centre (gnome-control-center).

===Installing the ATI display drivers===

If your ThinkPad has an Intel graphics adapter, you should skip this section as Ubuntu installs the best driver automatically. Ubuntu does not install the ATI proprietary drivers by default because they are, er, proprietary. Luckily, installing them is easy enough. Open a terminal (Applications - Accessories - Terminal) and type the following:

: {{cmduser| sudo apt-get update}}
: {{cmduser| sudo apt-get install xorg-driver-fglrx fglrx-control}}

Now we make sure the proprietary driver is not disabled by the kernel. Type the following, and remove any lines referring to fglrx

: {{cmduser|sudo gedit /etc/default/linux-restricted-modules-common}}

{{HINT|An alternative to gedit (Gnome) is nano (sudo nano -w /etc...) for a CLI editor.}}

Finally, we need to configure the X server to use the ATI drivers. Type the following:

: {{cmduser|sudo depmod -a}}
: {{cmduser|sudo aticonfig --initial}}
: {{cmduser|sudo aticonfig --overlay-type<nowiki>=</nowiki>Xv}}

One last thing. In order to correct a very common problem of getting a jerky video display, type the following:

: {{cmduser|sudo gedit /etc/X11/xorg.conf}}

Scroll to the end of the file, and add the text below.

<pre>
Section "Extensions"
Option "Composite" "0"
EndSection
</pre>

Save the file and exit. Now, to apply the changes either press CTRL+ALT+Backspace or reboot. The resolution should have switched to 1400x1050 and everything should look prettier and render faster. Just to make sure everything is working, open up a terminal and type

: {{cmduser|fglrxinfo}}

This should display:

<pre>
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Mobility Radeon X1400 Generic
OpenGL version string: 2.0.6011 (8.28.8)
</pre>

The above is what I get on my ThinkPad, and you should see something similar. As long as you see your graphics card model listed, everything should be OK. If, instead, you see a bunch of lines containing 'Mesa' then you have a problem. In that case, I recommend consulting https://help.ubuntu.com/community/BinaryDriverHowto/ATI and the Ubuntu forums at http://ubuntuforums.org

===The Fingerprint Reader===

Although IBM does not officially support it, the fingerprint reader does in fact work with most Linux distributions. Getting it to work with Ubuntu can be a bit of a pain, but it does work. Basically, a bioAPI plugin is provided for PAM. PAM-aware applications such as GDM and gnome-screensaver will then automatically use the fingerprint reader, which is uber cool. Anyway, enough theory, I've probably lost the newbies amongst you already. Go to http://www.qrivy.net/~michael/temp/ and download the latest bioapi package (at the time of writing, bioapi_1.2.3_i386.deb). When asked, tell Firefox to open the file with the GDebi package installer.

That will install bioAPI. What we need now is the driver for our fingerprint device, which is manufactured by UPEK. Go to http://www.upek.com/support/dl_linux_bsp.asp and download the latest version, currently UPEK_BSP_LIN_1.0.zip. Extract this file, then open a terminal (and don't close it until I say so).

: {{cmduser|cd /path/to/where/you/extracted/the/file}}
: {{cmduser|sudo bash}}
: {{cmdroot|sh install.sh /usr/lib}}

Now we need to assign the right permissions so non-root applications can use the driver:

: {{cmdroot|addgroup --system bioapi}}
: {{cmdroot|addgroup --system usbfs}}
: {{cmdroot|adduser yourusername bioapi}}
: {{cmdroot|adduser yourusername usbfs}}
: {{cmdroot|chown -R root:bioapi /usr/var/bioapi/}}
: {{cmdroot|chmod -R 770 /usr/var/bioapi/}}
: {{cmdroot|chown -R root:usbfs /proc/bus/usb}}
: {{cmdroot|chmod -R g+X /proc/bus/usb}}

Of course, replace 'yourusername' with the username you use to login. Now, we need to set the usb file system (usbfs) to be usable by users in the usbfs group. To do this, we need to determine the group ID of the usbfs group. Type the following:

: {{cmdroot|cat /etc/group | grep usbfs | cut -d':' -f 3}}

In my case the number is 116, it might be different for you. Now, open the file /etc/fstab:

: {{cmdroot|gedit /etc/fstab}}

and type the following:

<pre>none /proc/bus/usb usbfs defaults,devgid=116,devmode=0660,busgid=116,busmode=0770,listgid=116,listmode=0660 0 0</pre>

Please type the above code in one line in your file. Remember to replace 116 if you got a different number with the previous cat command. The last permission-related thing we need to fool around with is UDEV. Open the udev permissions file

: {{cmdroot|gedit /etc/udev/rules.d/40-permissions.rules}}

and find the line:

<pre>SUBSYSTEM=="usb_device", MODE="0664"</pre>

It's line 65 in my file. Change it so it looks like this:

<pre>SUBSYSTEM=="usb_device", MODE="0660", GROUP="usbfs"</pre>

Now we need to enroll our fingerprint with the system. To do this, we need a utility called Sample, which is only distributed in source-code form with the driver. This is great, only I couldn't get it to compile on Ubuntu. Luckily, there is a binary version available from one of the earlier releases of the driver (beta 2). To get this, download it from ftp://linux:Tuc-nak3@delta.upek.com/TFMESS_BSP_LIN_1.0beta2.zip. Now, extract the file and type:

: {{cmdroot|cd /path/to/where/you/extracted/the/archive}}
: {{cmdroot|cd NonGUI_sample}}
: {{cmdroot|chmod a+x Sample}}
: {{cmdroot|./Sample}}

Press (e) to enroll a new user, and enter your username when asked for the user ID. You will be asked to swipe your finger three times. Now press (v) and swipe your finger, a green check should be displayed showing you have successfully authenticated.

If the Sample utility does not work, you may not have the PAM development modules installed. Try this:

: {{cmdroot|sudo apt-get install libpam0g-dev}}

: Figure 8. The fingerprint swipe prompt
: [[Image:touchchip.jpg]]

Wonderful! Now, quit the application (q) and type exit to become a normal user. A file called yourusername.bir should have been created, copy this to your home directory:

: {{cmdroot|cp yourusername.bir /home/yourusername/}}

You can now close the terminal window. The next step is to install the BioAPI plug-in for PAM, and to make applications use the plugin. So, get the pam_bioapi plugin from http://www.nax.cz/pub/bioapi/pam_bioapi/pam-bioapi_0.3.0.tar.gz and extract it. Now open a terminal and type:

: {{cmduser|sudo apt-get install build-essential}}
: {{cmduser|sudo apt-get install libpam0g-dev}}

Now, you can compile and install the plugin

: {{cmduser|cd /path/to/where/you/extracted/the/arcive}}
: {{cmduser|./configure --libdir<nowiki>=</nowiki>/lib --enable-file-store && make}}
: {{cmduser|sudo make install}}

That's installed the plugin. Now, open a terminal and type the following:

: {{cmduser|cd ~}}
: {{cmduser|sudo bash}}

This will open a root session. Please do not close this until instructed. Now, paste the following scary command:

<pre>
SERIAL=`BioAPITest | sed -ne "/Fingerprint/{n;n;s/^.*: $.\{9\}$$.\{4\}$$.\{4\}$$.\{4\}$$.*$/\1-\2-\3-\4-\5/gp}"`
</pre>

Type the following to register your username and serial with the bioAPI.

: {{cmdroot|mkdir -p /etc/bioapi/pam/$SERIAL}}
: {{cmdroot|cp yourusername.bir /etc/bioapi/pam/$SERIAL}}
: {{cmdroot|exit}}

Phew. Now, to make applications actually use the fingerprint reader. Open a terminal window, and type:

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

Delete everything in the file, and paste this instead:

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

Save and close the file. That will make all PAM-aware applications use the fingerprint reader. Unfortunately, this also includes sudo. Since sudo is a command line application, it will display prompts in a terminal for you to swipe your finger, which is all well and good. The problem with this is that many Ubuntu administrative applications (such as Synaptic) use gksu to present a graphical front-end to sudo, which will output messages on the command line which you'll never see. Result? Administrative programs won't work from the gnome menu. The solution is to make sudo use the good old password. Open a terminal and type:

: {{cmduser|sudo gedit /etc/pam.d/sudo}}

Delete everything in the file, and instead paste:

<pre>
#%PAM-1.0

#@include common-auth
auth required pam_unix.so nullok_secure
@include common-account
</pre>

If you like to use the fingerprint reader in the terminal too, you can use the following /etc/pam.d/sudo file instead:

<pre>
#%PAM-1.0

#@include common-auth
auth sufficient pam_unix.so nullok_secure
auth required pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
password required pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
@include common-account
</pre>

With this file, you are first asked to provide your password, but you can just press enter and then you will be asked to swipe your finger.

Now, save the file and close it, and reboot your system. GDM will ask you for a username, and then show a pretty prompt where you can scan your fingerprint! Same goes for gnome-screensaver when you set it to lock. Sometimes gnome-screensaver will not display the prompt, but you should still swipe your finger and be able to log back in.

{{NOTE|In case you use Kubuntu KDM won't show you a prompt. Just press Enter instead of a password and then (when the cursor stops blinking) swipe your finger.}}

===Bluetooth with Mobile Phones/PDAs===

Rather strangely, Ubuntu seems to have taken a step backwards with Bluetooth usability in Edgy. What worked out of the box with Dapper, now requires configuration. First, open System - Preferences - Sessions and go to the Startup Programs tab. Then, find the entry labeled 'bt-applet --sm-disable'. Highlight it and click disable. Click add and in the command field type 'bt-applet'. Repeat this process, adding an entry for 'gnome-obex-server'. Now, open Synaptic Package Manager (System - Administration - Synaptic Package Manager) and click Search. Type 'gnome-bluetooth' to find the package, then mark it for installation. Now repeat this process for 'bluez-passkey-gnome'. Click apply to make changes.

Now that everything is installed, log-out of Gnome and log back in again. From your phone/PDA, search for devices until you see your ThinkPad (the hostname will be displayed). Pair with the device. When asked for a passkey, enter 1234, which is the default. If you want to change your passkey (and you should), open a terminal and type:

: {{cmduser|sudo gedit /etc/bluetooth/hcid.conf}}

Find the line which says 'Default PIN for incoming connections' and change the PIN on the line beneath it:

<pre>
# Default PIN code for incoming connections
passkey "4017";
</pre>

Save and close the file, then type:

: {{cmduser|sudo /etc/init.d/bluetooth restart}}

You will now be able to use your new PIN code. To send files from your device to the ThinkPad, simply select the file you want to send and click Send Via Bluetooth (or whatever option your device presents). A dialog will pop-up in Gnome showing you a new file has been received.

: Figure 9. Gnome informing us that a file has been received
: [[Image:bluetooth.jpg]]

Sending files from your ThinkPad to your device requires more effort. The way it should work is that you right-click on a file, click send to, then make sure 'Bluetooth (OBEX)' is selected. Your device should be displayed and you could just click send. Unfortunately, due to a bug in gnome-bluetooth (described in https://launchpad.net/distros/ubuntu/+source/gnome-bluetooth/+bug/70718) this method does not work. If it does work for you, the bug has been solved and you can skip the rest of this section.

Your only other option is to use the command line to send files to your device. Open a terminal, then type:

: {{cmduser|hcitool scan}}

A list of detected bluetooth devices will be shown, for example, my output shows the following:

<pre>
Scanning ...
00:09:DD:60:02:EB Photosmart 8100 series
00:14:A7:99:3C:1F ThElInK
</pre>

The first field is the MAC address of the device, the second is the name of the device. In this case my bluetooth printer and mobile phone (ThElInK) were detected. In order to send files to my phone, I use:

: {{cmduser|gnome-obex-send -d 00:14:A7:99:3C:1F myPicture.jpg}}

Replace the MAC address with that of your device and myPicture.jpg with the file you want to send.

===TrackPoint Scrolling===

By default you can use the right and bottom edges of your touchpad to scroll through documents. If you use the TrackPoint instad of the touchpad (and believe me, you should), you'll find that scrolling is disabled by default. To enable it, open a terminal and type:

: {{cmduser|sudo gedit /etc/X11/xorg.conf}}

Now find the entry for your TrackPoint device. In my configuration file, the TrackPoint entry is the first mouse entry, after the keyboard entry, and looks something like this:

<pre>
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection
</pre>

Right after this entry is my touchpad entry. My entry is on line 66, but yours may be different. Now, add the follwing two options in that InputDevice section:

<pre>
Option "EmulateWheel" "on"
Option "EmulateWheelButton" "2"
</pre>

Save and exit the file. Restart your ThinkPad (or logout, and press CTRL-ALT-BACKSPACE). You should now be able to scoll by holding down the middle button for your TrackPoint and using the TrackPoint to scroll.

===Getting Multimedia to Work===

Due to patents and similar legal crap, Ubuntu will not play most media files by default. You also won't get browser plugins for multimedia. Luckily, this is easily fixed. Open a terminal and type the following:

: {{cmduser|sudo cp /etc/apt/sources.list /etc/apt/sources.list.backup}}
: {{cmduser|sudo gedit /etc/apt/sources.list}}

Delete everything in the file, and instead paste the following:

<pre>
deb-src http://archive.ubuntu.com/ubuntu edgy main restricted universe multiverse
#deb http://archive.ubuntu.com/ubuntu edgy-proposed main restricted universe multiverse

## MAJOR BUG FIX UPDATES produced after the final release
deb-src http://archive.ubuntu.com/ubuntu edgy-updates main restricted universe multiverse

## UBUNTU SECURITY UPDATES
deb http://security.ubuntu.com/ubuntu edgy-security main restricted universe multiverse
deb-src http://security.ubuntu.com/ubuntu edgy-security main restricted universe multiverse

## BACKPORTS REPOSITORY (Unsupported. May contain illegal packages. Use at own risk.)
#deb http://archive.ubuntu.com/ubuntu edgy-backports main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu edgy-backports main restricted universe multiverse

## PLF REPOSITORY
deb http://packages.freecontrib.org/ubuntu/plf edgy-plf free
deb-src http://packages.freecontrib.org/ubuntu/plf edgy-plf free
deb http://packages.freecontrib.org/ubuntu/plf edgy-plf non-free
deb-src http://packages.freecontrib.org/ubuntu/plf edgy-plf non-free

## CANONICAL COMMERCIAL REPOSITORY (Hosted on Canonical servers, not Ubuntu
## servers. RealPlayer10, Opera, DesktopSecure and more to come.)
deb http://archive.canonical.com/ubuntu edgy-commercial main

## Listen
#deb http://theli.free.fr/packages/ edgy listen

## Automatix repo
deb http://www.getautomatix.com/apt edgy main
</pre>

Now, open a terminal and type the following:

: {{cmduser|wget <nowiki>http://packages.freecontrib.org/ubuntu/plf/12B83718.gpg</nowiki> -O- <nowiki>|</nowiki> sudo apt-key add -}}
: {{cmduser|wget <nowiki>http://www.getautomatix.com/apt/key.gpg.asc</nowiki>}}
: {{cmduser|gpg --import key.gpg.asc}}
: {{cmduser|gpg --export --armor 521A9C7C <nowiki>|</nowiki> sudo apt-key add -}}
: {{cmduser|sudo apt-get update}}
: {{cmduser|sudo apt-get install automatix2}}
: {{cmduser|wget <nowiki>http://easyubuntu.freecontrib.org/files/easyubuntu-3.023.tar.gz</nowiki>}}
: {{cmduser|tar -zxf easyubuntu-3.023.tar.gz}}
: {{cmduser|cd easyubuntu}}
: {{cmduser|cp packagelist-dapper.pot packagelist-edgy.pot}}
: {{cmduser|cp packagelist-dapper.xml packagelist-edgy.xml}}
: {{cmduser|sudo python easyubuntu.in}}

Don't worry if you get errors from the Ubuntu PLF repository. PLF mirrors are about as stable as wild bull in a farm full of cows. Select what you want to install from the resulting window. Make sure you do not select the totem-mozilla plugin, as this just doens't work, for me at least. When EasyUbuntu has finished installing packages, you should be returned to a terminal, which you can close. Now go to Applications - System Tools - Automatix. Read and agree to the warning. Check what you want to install. Make sure you check 'Mplayer and FF plugin'. When ready, click the 'install' button. That should get multimedia working nicely.

: Figure 10. The Automatix user interface
: [[Image:automatix.jpg]]

===Beryl - fancy 3D desktop===

MAC OS X has Aqua and Windows Vista has Aero. Well, Linux has XGL/Beryl which can get effects which are as good looking (or sometimes better!) than the former two. Installing Beryl on Ubuntu is not that hard. First, open a terminal and type the following:

: {{cmduser|sudo gedit /etc/apt/sources.list}}

At the end of the file, append the following:

<pre>
##Beryl
deb http://ubuntu.beryl-project.org/ edgy main
</pre>

Save and close the file. Now type:

: {{cmduser|wget <nowiki>http://ubuntu.beryl-project.org/root@lupine.me.uk.gpg</nowiki> -O- <nowiki>|</nowiki> sudo apt-key add -}}
: {{cmduser|sudo apt-get update}}

ATI Users Only: type

: {{cmduser|sudo apt-get install xserver-xgl}}

Now, to install beryl:

: {{cmduser|sudo apt-get install beryl emerald-themes}}

To make Ubuntu use the 3D effects. Open a terminal:

: {{cmduser|sudo gedit /usr/local/bin/startxgl.sh}}

In that file, paste the following if you use an ATI card:

<pre>
#!/bin/sh
Xgl -fullscreen :1 -ac -br -accel glx:pbuffer -accel xv:pbuffer &
sleep 4
export DISPLAY=:1
cookie="$(xauth -i nextract - :0 | cut -d ' ' -f 9)"
xauth -i add :1 . "$cookie"
exec gnome-session
</pre>

If you use an Intel card, paste the following instead:

<pre>
#!/bin/sh
beryl-manager
sleep 4
exec gnome-session
</pre>

Save the file and close. Now we need to make the file executable:

: {{cmduser|sudo chmod a+x /usr/local/bin/startxgl.sh}}

All that's left now is to create a login script which makes gnome use the 3D effects. In a terminal, type:

: {{cmduser|sudo gedit /usr/share/xsessions/xgl.desktop}}

Now, in this file paste:

<pre>
[Desktop Entry]
Encoding=UTF-8
Name=Xgl
Exec=/usr/local/bin/startxgl.sh
Icon=
Type=Application
</pre>

Save and close the file. Now type:

: {{cmduser|sudo gedit /usr/local/bin/start_beryl.sh}}

In this file, paste:

<pre>
#!/bin/bash
#
# Start beryl-manager within gnome-session
#
if [ `ps -A -o comm | grep -c '^Xgl$'` == "1" ]; then
DISPLAY=:1 beryl-manager
DISPLAY=:1 beryl-xgl
else echo "${0}: Error: beryl-manager not launched. Xgl not running?"
fi
</pre>

Now make the file executable:

: {{cmduser|sudo chmod a+x /usr/local/bin/start_beryl.sh}}

Now go to System - Preferences - Sessions, go to the Startup Programs tab, and click add, then type

: {{cmduser|/usr/local/bin/start_beryl.sh}}

Now, reboot your ThinkPad. When you come to the login screen, click the 'Sessions' button on the bottom left corner, and select XGL. login, et voila! beautiful 3D effects!

: Figure 11. Beryl's Cube effect
: [[Image:cube.jpg]]

If you have NetBeans installed, try launching it now. It probably won't work due to Beryl. Luckily, this is easily solved. Open a terminal and type:

: {{cmduser|sudo gedit /etc/environment}}

Then add the following line to the end of the file.

<pre>AWT_TOOLKIT="MToolkit"</pre>

Now save, close and reboot. Netbeans should now work!

===Problem: Can't add programs to session===

So you tried to add something to your startup programs, it shows up in the list, but it doesn't start up. You then launch the sessions program again, only to find your program has disappeared from the list. This problem is being caused by incorrect permissions in your home directory, and can happen on some occasions. To fix it, open a terminal and type the following:

: {{cmduser|sudo chown -R username:usergroup /home/username/.config/}}

Replace username with your username and usergroup with your group (by default, in Ubuntu your usergroup is the same as your username). Everything should be OK now!

===Problem: Virtual terminals not working===

One problem I had after installing the ATI drivers was that virtual terminals stopped working. Instead of seeing a console when pressing CTRL+ALT+F1...F6 I was seeing a yellow/orange garbled output. Luckily, solving this with ATI drivers is trivial. Open a terminal, and type:

: {{cmduser|sudo gedit /boot/grub/menu.lst}}

Find the line which says

<pre>#defoptions=quiet splash</pre>

and replace it with

<pre>#defoptions=quiet splash vga=791</pre>

Now, find the line which boots the kernel you are currently using, this is just under '## ## End Default Options ##. In the 'kernel' line, add:

<pre>vga=791</pre>

Before:

<pre>kernel /vmlinuz-2.6.17-10-generic root=/dev/sda7 ro quiet splash</pre>

After:

<pre>kernel /vmlinuz-2.6.17-10-generic root=/dev/sda7 ro quiet splash vga=791</pre>

Now save and exit the file, and reboot. Virtual terminals should now work. If you use Intel drivers, you're going to have to bite the bullet and remove the 'splash' keyword from both the defoptions and kernel lines. You'll lose the pretty bootup screen, but at least virtual terminals will work, which are important to recover a crashed system.

===Problem: Microphone doesn't work===

On my system, I could get the microphone to work by simply un-muting the correct channels using alsamixer. To do this, open the ALSA mixer GUI form a terminal:

: {{cmduser| alsamixer}}

The alsamixer GUI will be displayed:

[[Image:alsamixer.jpg]]

Now make sure all outputs are un-muted. Scroll through the outputs using the {{key|LEFT}} and {{key|RIGHT}} arrow keys, and press {{key|M}} to un-mute a channel (muted channels show an MM symbol). Use the {{key|UP}} and {{key|DOWN}} arrow keys to raise and lower the volume for each channel. Press {{key|TAB}} to switch to capture settings. Select Mic and press {{key|SPACE}} to enable the microphone. Now enable microphone capture my selecting Capture, and pressing {{key|SPACE}}. Depending on your microphone, you may need to enable MIC boost to get some extra umph from your sound input.

The volume of the input channels depends on your microphone. These settings worked best for me on a desktop microphone:

: MIC: 71
: MIC Boost: 33
: Capture: 73

Now test the microphone by going to Applications - Sound & Video - Sound Recorder and select "Capture" in the "Record from input" field. On my system, mixing worked too - meaning I could play games whilst talking on TeamSpeak or Skype.

After following the above steps, your microphone may still not work, which appears to be linked to the a missing file /etc/asound.names. Executing

: {{cmduser|sudo alsactl names}}
: {{cmduser|sudo alsactl store}}

to generate /etc/asound.names and /var/lib/alsa/asound.state seems to fix sound problems.

===Problem: I don't have any sound!===

If Ubuntu seems to recognize your sound-card (82801G ICH7) but still cannot initialize it (so you don't hear a thing), you have most probably turned the modem off in the system-bios.
If you turn it on again, it should work again.
If you don't want to do that [http://www.ubuntuforums.org/showthread.php?t=279241 this] might help you.

===Problem: I keep logging out!===

If you're using Beryl, and find that you keep getting logged out, you've just encountered one of Beryl's most annoying bugs. Shift+Backspace causes a logout. To fix this, open a terminal and type:

: {{cmduser|gedit /home/username/annoymenot.sh}}

Remember to replace 'username' with your username. Now, in this file type:

: {{cmduser|xmodmap -e "keycode 22 <nowiki>=</nowiki> BackSpace BackSpace Terminate_Server" }}

Save and close the file, and make it executable:

: {{cmduser|chmod 755 /home/username/annoymenot.sh}}

Now go to System - Preferences - Session, Startup Programs. Click add, and type

: {{cmduser|/home/username/annoymenot.sh}}

Logout and back in, problem solved! While you're at it, how about getting the start button to work? Go to System - Preferences - Keyboard - Layout Options - Alt/Win Key behaviour and select 'Super is mapped to Win keys (default)'.

===Problem: Hibernate (Suspend to Disk) does not work!===

It was possible on some machines to get hibernate working by installing the hibernate script. However, when too many programs where open I got a "Not enough memory" error. You will have to try it.

To install the script type

: {{cmduser|sudo apt-get install hibernate}}

To go to hibernate type

: {{cmduser|sudo hibernate}}

The computer will go to hibernate and turn off. To switch it on again, you will have to press the power button. It will boot and restore the system as you left it.

===Desktop envy===

We're living in an age of desktop prettyness, and Linux can be just as pretty as MAC OS X or Vista. You've already got Beryl installed. Now go to Applications - Accesories - gDesklets. If the gDesklets entry is not there, make sure you install it, either using Synaptic or Automatix. Desklets are small programs you can add to your desktop, ala OS X's Deskbar or Vista's Sidebar. To make them start on boot, add gdesklets in System - Preferences - Sessions, Startup Programs.

Another cool program is cairo clock. Download it from http://macslow.thepimp.net/projects/cairo-clock/cairo-clock_0.3.2-1_i386.deb and install it by double-clicking. To make it start automatically, add it to your sessions as mentioned above. I've found the following command makes it work best for me:

<pre>cairo-clock -s -w 175 -g 175 -x 1219 -y 7 -t radium</pre>

Finally, make sure you click that Ruby icon in your notification area, it allows you to configure Beryl to do all sorts of cool stuff!

===Conclusion===

Well, that's about it! A dream Linux system on a dream laptop! Check out these cool technologies for an even better system:

* Beagle
* Tomboy
* Deskbar

===References===

* ATI on Ubuntu - https://help.ubuntu.com/community/BinaryDriverHowto/ATI
* Garbled Virtual Terminal Bug - https://launchpad.net/distros/ubuntu/+source/usplash/+bug/63558
* Beryl logout Bug - http://forum.beryl-project.org/viewtopic.php?p=1295&sid=6feedd09a7f01bca68feb05a5f2f033c
* Beryl Netbeans Bug - http://ubuntuforums.org/showthread.php?t=252594
* Beryl on Ubuntu - http://wiki.beryl-project.org/index.php/Install/Ubuntu/Edgy/XGL
* Home directory permissions bug - http://www.ubuntuforums.org/showthread.php?p=1789997
* gnome-bluetooth bug - https://launchpad.net/distros/ubuntu/+source/gnome-bluetooth/+bug/70718
* Atheros network cards on Ubuntu - http://ubuntuforums.org/showthread.php?t=38972
* Enabling the microphone - http://ubuntu.wordpress.com/2005/12/05/fixing-the-errant-microphone/
* Enabling the microphone (2) - http://ubuntuforums.org/showthread.php?t=272166

Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T60

2007-01-13T05:18:09Z

Ischg:

Ubuntu Feisty Fawn is still in development (aka a ''beta version'') and appears '''not ready for installation''' (as of January 12, 2007). In particular, on a 2007-72U the installer crashed - see [https://launchpad.net/ubuntu/+source/ubiquity/+bug/79029 bug report]. The next beta release is planned for February 1st (see [https://wiki.ubuntu.com/FeistyReleaseSchedule?highlight=%28feisty%29 Feisty Release Schedule]).

Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T60

2007-01-13T05:11:26Z

Ischg:

Ubuntu Feisty Fawn is still in development (aka a ''beta version'') and appears '''not ready for installation''' (as of January 12, 2007). In particular, on a 2007-72U the installer crashed - see [[https://launchpad.net/ubuntu/+source/ubiquity/+bug/79029 bug report]]. The next beta release is planned for February 1st (see [[https://wiki.ubuntu.com/FeistyReleaseSchedule?highlight=%28feisty%29 Feisty Release Schedule]]).

Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T60

2007-01-13T05:06:30Z

Ischg:

Installation instructions for the ThinkPad T60

2007-01-13T04:57:18Z

Ischg: /* Ubuntu */

Specific installation notes for the ThinkPad {{T60}}.

==Distribution-specific instructions==

=== Ubuntu ===

*{{Install|Ubuntu| 7.04 Herd 2 (Feisty Fawn)| T60}}
*{{Install|Ubuntu| 6.10 (Edgy Eft)| T60}}
*{{Install|Ubuntu| 6.06 Flight 5|T60}}

=== Fedora ===

*{{Install|Fedora| Core 6| T60}}
*{{Install|Fedora| Core 5| T60}}

=== openSUSE / SUSE LINUX ===

*{{Install|Suse| 10.1| T60}}
*[[Installing openSUSE 10.2 on an IBM ThinkPad T60]]

=== Gentoo ===

* For Gentoo, there exists [[Installation_instructions_for_the_ThinkPad_T60p|installation instructions for T60p]], the sister model.

== Compatibility ==
* [http://www.emperorlinux.com/mfgr/lenovo/toucan/?tab=details&id=358 Thinkpad T60] page on [http://www.emperorlinux.com emperorlinux.com] (compatibility review and custom kernel)

Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60

2006-12-24T18:57:59Z

Ischg: /* Problem: Microphone doesn't work */

Created by: [[User:Keithvassallo|Keithvassallo]] 14:39, 16 December 2006 (CET)

Thanks for valuable contributions by:

: [[User:Ischg|Ischg]]
: [[User:Soon|Soon]]

===Abstract===

This article describes how to get Ubuntu Linux 6.10 (Edgy) installed on an IBM/Lenovo ThinkPad T60. It's not meant to be a definite guide to installing Ubuntu (the Ubuntu Guide at http://www.ubuntuguide.org does a very good job of that). This article is meant to describe how to get most of the ThinkPad features working on Ubuntu system. It also discusses how to get Multimedia, some cool-looking effects such as Beryl, gDesklets and similar working on Ubuntu. Finally, we discuss some common problems encountered on Ubuntu and ThinkPads alike.

{{NOTE|I am in no means an expert, the methods described here are those which got everything to work for me - your mileage may vary. A big thank you to all ThinkWiki users who keep contributing on improving this article.}}

===My ThinkPad===

Although this guide should work on most recent ThinkPads, I cannot guarantee that. These are the specifications of my machine. The closer your specs are, the greater the chance of success.

: Figure 1. ThinkPad T60 2007, complete with Tux sticker :-)
: [[Image:thinkpad.jpg]]

* Lenovo ThinkPad T60 2007.
* Intel Centrino Duo T2400 / 1.83 GHz.
* Mobile Intel 945PM Express Chipset.
* Intel Wireless LAN.
* Integrated Bluetooth.
* ATI Mobility Radeon X1400 - PCI Express x16, 128MB dedicated RAM.
* 100 GB - Serial ATA-150 Hard Drive.
* 15' TFT Active Matrix Display (1400x1050).

That's basically all you need to know. As far as I know, all other features are common to all ThinkPads manufactured by Lenovo since they acquired IBM's computer business.

===Why Ubuntu? (or rather, Why not SUSE?)===

In June 2006, Lenovo announced it would be shipping ThinkPad T60p laptops with SUSE Linux Enterprise Desktop (SLED) 10 pre-installed, since SLED apparently supports all of the features of the T60p. I contacted my local IBM supplier, who said that Lenovo were no longer manufacturing the T60p, since the company which was making the displays went out of business. This meant I could not get a T60p with SLED pre-installed. I decided to go for the T60 2007, which is the closest thing I could find to the T60p. This comes with Windows XP Professional pre-installed.

I first tried to get SLED installed on the T60. Although it did indeed install, and most features worked, I soon got bored of SLED. Firstly, SLED uses Gnome 2.12, which is by now ancient. Secondly, although the Lenovo utilities do work on SLED, they only work well if you use KDE as your defauly desktop environment, which is a pity since I'm a Gnome user. The utilities were very unstable to me too. Finally, what made me give up SLED was the usual problem - it's an RPM based distribution. Once you start using Debian derivatives, with their apt based installer, you won't want to go back. That's when I decided to try Ubuntu, and have not regretted it since.

===What Works?===

* Ubuntu and all programs it comes with.
* Most of the function keys, except the ones mentioned below
* The fingerprint reader.
* The ATI proprietary graphics drivers.
* Suspend to RAM (Sleep) and Suspend to Disk (Hibernate).
* Brightness, Volume and Mute with OSD (On-Screen Display).
* ThinkLight, TrackPoint II and the touchpad.

===What Doesn't Work? (Known Issues)===

* FN+F8, FN+F9, FN+ZOOM.
* The BACK and FORWARD buttons (next to the cursor keys).
* The ThinkVantage button (in Linux, still works on boot).
* Sending files to Bluetooth devices via GUI.

There are probably ways and means to get the offending buttons to work, I've tried several fora but none seem to address my exact problem. I'll update this article should I find out anything.

===First Things First - Creating a Windows Recovery Disc===

If you've purchased a T60, chances are it came with Windows XP Professional. The other option is for you to have FreeDOS installed, in which case you can skip this section. You could remove the Windows partition altogether, and reserve your ThinkPad for Linux, but that's not the route I've chosen. The ThinkVantage utilities in Windows allow you to do a lot of cool things, such as set-up a boot-up fingerprint security scan. You can't do this from Linux (as far as I know) so it's best to leave the Windows partition in place. So, boot your ThinkPad and complete the Windows XP setup (which asks you to add a user account and enroll yourself using the ThinkVantage Client Security Solution). While you're there, use the ThinkVantage productivy centre to enroll your fingerprint (I suggest enrolling more than one) and make sure you check the option to require a fingerprint scan on boot (not for security, for geek points). When you reboot, press ESC or F2 to get to BIOS, and make sure you check the option to require a supervisor password. This will make your ThinkPad prompt you for your fingerprint when you power it up.

: Figure 2. Configuring fingerprint security from Windows
: [[Image:winprint.jpg]]

Now that's working, you should create a recovery DVD using the ThinkVantage recovery utilities. This will allow you to recover your Windows installation should you manage to screw your partitions up in the following stages. I highly recommend you do this, as Lenovo does not provide Windows XP CDs with this Laptop - so the hard disk partition is all you've got. Once this is done, we're ready to install Ubuntu!

: Figure 3. Creating recovery discs from Windows
: [[Image:recovery.jpg]]

===Getting Ubuntu installed===

Download the latest Edgy live CD from the Ubuntu website, you can find a list of mirrors at http://www.ubuntu.com/products/GetUbuntu/download#currentrelease. You may also try Kubuntu, Edubuntu or any of it's derivatives, but I'll stick with Ubuntu here for simplicity's sake. Once that's downloaded, burn the ISO to disc using any program of your choice (If this is your first Linux experience and you're using Windows, try using Nero - http://www.nero.com).

Once the burning process is complete, reboot your machine ensuring that the Ubuntu CD is in the drive. You should see an Ubuntu menu. If you don't, your BIOS is not set to boot from CD. Reboot your ThinkPad and change the boot order from BIOS (by default ThinkPads boot from CD-ROM before the hard disk, so this is probably not necessary). Once the menu shows up, select 'Start or install Ubuntu' and let it boot. This will take a while as everything is loaded from CD. You should eventually end up in a Gnome desktop. If you see an error about the Gnome Settings Daemon not being able to load, simply ignore it, as this is not necessary for now. For the purposes of the installation, it's best if you have a wired ethernet connection, as it's unlikely the wireless network card will work until we boot into our installed Ubuntu system.

: Figure 4. Select the first option to start Ubuntu
: [[Image:boot.jpg]]

Double-Click on the 'install' icon on the Desktop to start installation. The installation should be pretty straight-forward. If you need additional help, check out the walk-through with screen-shots at http://www.debianadmin.com/ubuntu-edgy-eft-desktop-installation-with-screenshots.html. The only stage at which we need to make changes is the partitioning stage. This to make sure we preserve our Windows partition, and the IBM vendor_diag partition which allows recovery of the laptop when things go hay-wire. In the 'Prepare disk space' section of the installer, select the third option, 'Manually edit partition table'. A bar will be displayed showing your existing partitions. If you have Windows installed you will see two partitions. The first is a 4.89 GB IBM Vendor Diagnostic partition, which we do not want to touch. The second will be your Windows partition, which will fill the rest of the disk. Click on this partition, Then click the 'Resize/Move' button. I resized my Windows partition to 24 GB. This is enough to accommodate the 10 GB already in use on that partition, as well as giving Windows another 14 GB of free space. 6 GB of free space would probably be enough though.

Now it's time to create partitions for Linux. You need at least two partitions; a swap partition which should be roughly double the amount of RAM you have, and a root partition to install Linux. I opted for four partitions, as follows:

<table border=1>
<tr><td>'''Purpose'''</td><td>'''Size'''</td><td>'''File-System'''</td></tr>
<tr><td>Swap</td><td>2 GB</td><td>swap</td></tr>
<tr><td>/boot</td><td>5 GB</td><td>ext3</td></tr>
<tr><td>/ (root)</td><td>20 GB</td><td>ext3</td></tr>
<tr><td>/home</td><td>37.25 GB (what's left of the disk)</td><td>ext3</td></tr>
</table>

To create these paritions, click on the 'New' button and select 'Extended Partition' in the 'create as' drop-down list. Leave all other settings as-is, and click 'Add'. Now, click on the newly created partition, and create each of the partitions you want to create, simply specify the size of the partition in the 'New Size (MiB)' text box. To convert GB to MiB, multiply by 1024. So for your swap partition you should specify a size of 2048. Repeat until you have created all the required partitions. If you follow my parition layout, the partition editor should look something like Figure 5.

: Figure 5. Our partitions, ready to be created
: [[Image:partitioning.jpg]]

You will not see mount-points in your diagram, because the screen-shot above was taken after they were assigned, but you should get the general idea. After this screen, you will be asked to assign mount-points to the partitions you have just created. If you created the partitions in the same order I did, you can assign mount points as I have (i.e. /dev/sda5 for swap, /dev/sda6 for /boot, /dev/sda7 for /, /dev/sda8 for /home). Additionally, I mounted my Windows partition as /media/sda1 and my IBM Vendor Diagnostic partition as /media/sda2. These are optional. After this step, continue installation as normal. When the installation is complete, click the 'reboot' button to restart into your fresh Ubuntu System.

When booting, the GRUB boot-loader will be displayed, asking you what you want to load. You will probably see four options. The first two being Ubuntu Linux and Ubuntu Linux recovery mode (showing the kernel version). The other two will be Microsoft Windows XP, and 'Other Windows XP/2000/NT' partition. This is your IBM Vendor Diagnostic partition, which is based on the Windows kernel, apparently. Select the first entry to boot Ubuntu. The next time you boot Windows, it will bring up a chkdsk screen. This is entirely normal and happens because we have resized the Windows partition. Make sure you do not skip this check and let it complete.

===Wireless LAN===

{{WARN|Another ThinkWiki user notes that not all T60s come with the Intel wireless chip. If you are not entirely sure what wireless NIC you use, please read the following section (Non-Intel Network Cards).}}

The first thing we should do is to get wireless networking working. Luckily, getting the Centrino wireless LAN chip working in Ubuntu is quite easy, if you use the gnome-network-manager applet. Just go to System - Administration - Synaptic Package Manager. Then click 'Search' and set the 'look-in' field to 'name'. In the 'Search' text box type:

<pre>network-manager</pre>

: Figure 6. Installing the network manager applet
: [[Image:networkmanager.jpg]]

Click on the box beside 'network-manager' and click 'Mark for installation'. Do the same for 'network-manager-gnome'. Once installed, reboot your ThinkPad. An applet will show up in the gnome notification area. Click on it, and a list of detected wireless networks will be displayed. Simply click on one of them, enter any authentication details necessary, and you'll be connected to the wireless network.

: Figure 7. gnome-network-manager showing available wireless networks
: [[Image:available-accesspoints.jpg]]

===Non-Intel Network Cards===

Not all versions of the T60 have the Intel Wireless LAN as described above. Run the following command to see details about detected wireless cards:

: {{cmduser| lspci}}

Look for a line which shows detected network cards. Users of Intel network cards will see something similar to the following output:

<pre>03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)</pre>

If you see the above, you can jump to the next section. If you do not see the above, your network card is not Intel. You may see something similar to:

<pre>03:00.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)</pre>

If that's the output you get, you're going to have to take some additional steps to get wireless networking working. Read more at http://ubuntuforums.org/showthread.php?t=38972

running:

: {{cmdroot| dmesg <nowiki>|</nowiki> grep hal}}

may yield output like this:

<pre>
[17179590.420000] ath_hal: module license 'Proprietary' taints kernel.
[17179590.424000] ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
</pre>

Which suggests the hardware abstraction layer is in place.

If not, or if the output contains "HAL Status 13" it suggests your card is not supported by the current drivers, and you need to upgrade.

===Installing the ATI display drivers===

If your ThinkPad has an Intel graphics adapter, you should skip this section as Ubuntu installs the best driver automatically. Ubuntu does not install the ATI proprietary drivers by default because they are, er, proprietary. Luckily, installing them is easy enough. Open a terminal (Applications - Accessories - Terminal) and type the following:

: {{cmduser| sudo apt-get update}}
: {{cmduser| sudo apt-get install xorg-driver-fglrx fglrx-control}}

Now we make sure the proprietary driver is not disabled by the kernel. Type the following, and remove any lines referring to fglrx

: {{cmduser|sudo gedit /etc/default/linux-restricted-modules-common}}

An alternative to gedit (Gnome) is nano (sudo nano -w /etc...) for a CLI editor.

Finally, we need to configure the X server to use the ATI drivers. Type the following:

: {{cmduser|sudo depmod -a}}
: {{cmduser|sudo aticonfig --initial}}
: {{cmduser|sudo aticonfig --overlay-type<nowiki>=</nowiki>Xv}}

One last thing. In order to correct a very common problem of getting a jerky video display, type the following:

: {{cmduser|sudo gedit /etc/X11/xorg.conf}}

Scroll to the end of the file, and add the text below.

<pre>
Section "Extensions"
Option "Composite" "0"
EndSection
</pre>

Save the file and exit. Now, to apply the changes either press CTRL+ALT+Backspace or reboot. The resolution should have switched to 1400x1050 and everything should look prettier and render faster. Just to make sure everything is working, open up a terminal and type

: {{cmduser|fglrxinfo}}

This should display:

<pre>
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Mobility Radeon X1400 Generic
OpenGL version string: 2.0.6011 (8.28.8)
</pre>

The above is what I get on my ThinkPad, and you should see something similar. As long as you see your graphics card model listed, everything should be OK. If, instead, you see a bunch of lines containing 'Mesa' then you have a problem. In that case, I recommend consulting https://help.ubuntu.com/community/BinaryDriverHowto/ATI and the Ubuntu forums at http://ubuntuforums.org

===The Fingerprint Reader===

Although IBM does not officially support it, the fingerprint reader does in fact work with most Linux distributions. Getting it to work with Ubuntu can be a bit of a pain, but it does work. Basically, a bioAPI plugin is provided for PAM. PAM-aware applications such as GDM and gnome-screensaver will then automatically use the fingerprint reader, which is uber cool. Anyway, enough theory, I've probably lost the newbies amongst you already. Go to http://www.qrivy.net/~michael/temp/ and download the latest bioapi package (at the time of writing, bioapi_1.2.3_i386.deb). When asked, tell Firefox to open the file with the GDebi package installer.

That will install bioAPI. What we need now is the driver for our fingerprint device, which is manufactured by UPEK. Go to http://www.upek.com/support/dl_linux_bsp.asp and download the latest version, currently UPEK_BSP_LIN_1.0.zip. Extract this file, then open a terminal (and don't close it until I say so).

: {{cmduser|cd /path/to/where/you/extracted/the/file}}
: {{cmduser|sudo bash}}
: {{cmdroot|sh install.sh /usr/lib}}

Now we need to assign the right permissions so non-root applications can use the driver:

: {{cmdroot|addgroup --system bioapi}}
: {{cmdroot|addgroup --system usbfs}}
: {{cmdroot|adduser yourusername bioapi}}
: {{cmdroot|adduser yourusername usbfs}}
: {{cmdroot|chown -R root:bioapi /usr/var/bioapi/}}
: {{cmdroot|chmod -R 770 /usr/var/bioapi/}}
: {{cmdroot|chown -R root:usbfs /proc/bus/usb}}
: {{cmdroot|chmod -R g+X /proc/bus/usb}}

Of course, replace 'yourusername' with the username you use to login. Now, we need to set the usb file system (usbfs) to be usable by users in the usbfs group. To do this, we need to determine the group ID of the usbfs group. Type the following:

: {{cmdroot|cat /etc/group <nowiki>|</nowiki> grep usbfs <nowiki>|</nowiki> cut -d':' -f 3}}

In my case the number is 116, it might be different for you. Now, open the file /etc/fstab:

: {{cmdroot|gedit /etc/fstab}}

and type the following:

<pre>none /proc/bus/usb usbfs defaults,devgid=116,devmode=0660,busgid=116,busmode=0770,listgid=116,listmode=0660 0 0</pre>

Please type the above code in one line in your file. Remember to replace 116 if you got a different number with the previous cat command. The last permission-related thing we need to fool around with is UDEV. Open the udev permissions file

: {{cmdroot|gedit /etc/udev/rules.d/40-permissions.rules}}

and find the line:

<pre>SUBSYSTEM=="usb_device", MODE="0664"</pre>

It's line 65 in my file. Change it so it looks like this:

<pre>SUBSYSTEM=="usb_device", MODE="0660", GROUP="usbfs"</pre>

Now we need to enroll our fingerprint with the system. To do this, we need a utility called Sample, which is only distributed in source-code form with the driver. This is great, only I couldn't get it to compile on Ubuntu. Luckily, there is a binary version available from one of the earlier releases of the driver (beta 2). To get this, download it from ftp://linux:Tuc-nak3@delta.upek.com/TFMESS_BSP_LIN_1.0beta2.zip. Now, extract the file and type:

: {{cmdroot|cd /path/to/where/you/extracted/the/archive}}
: {{cmdroot|cd NonGUI_sample}}
: {{cmdroot|chmod a+x Sample}}
: {{cmdroot|./Sample}}

Press (e) to enroll a new user, and enter your username when asked for the user ID. You will be asked to swipe your finger three times. Now press (v) and swipe your finger, a green check should be displayed showing you have successfully authenticated.

: Figure 8. The fingerprint swipe prompt
: [[Image:touchchip.jpg]]

Wonderful! Now, quit the application (q) and type exit to become a normal user. A file called yourusername.bir should have been created, copy this to your home directory:

: {{cmdroot|cp yourusername.bir /home/yourusername/}}

You can now close the terminal window. The next step is to install the BioAPI plug-in for PAM, and to make applications use the plugin. So, get the pam_bioapi plugin from http://www.nax.cz/pub/bioapi/pam_bioapi/pam-bioapi_0.3.0.tar.gz and extract it. Now open a terminal and type:

Comment: you will have to install some libraries in order to be able to compile the plugin

: {{cmduser|sudo apt-get install build-essential}}
: {{cmduser|sudo apt-get install libpam0g-dev}}

Now, you can compile and install the plugin

: {{cmduser|cd /path/to/where/you/extracted/the/arcive}}
: {{cmduser|./configure --libdir<nowiki>=</nowiki>/lib --enable-file-store && make}}
: {{cmduser|sudo make install}}

That's installed the plugin. Now, open a terminal and type the following:

: {{cmduser|cd ~}}
: {{cmduser|sudo bash}}

This will open a root session. Please do not close this until instructed. Now, paste the following scary command:

<pre>
SERIAL=`BioAPITest | sed -ne "/Fingerprint/{n;n;s/^.*: $.\{9\}$$.\{4\}$$.\{4\}$$.\{4\}$$.*$/\1-\2-\3-\4-\5/gp}"`
</pre>

Type the following to register your username and serial with the bioAPI.

: {{cmdroot|mkdir -p /etc/bioapi/pam/$SERIAL}}
: {{cmdroot|cp yourusername.bir /etc/bioapi/pam/$SERIAL}}
: {{cmdroot|exit}}

Phew. Now, to make applications actually use the fingerprint reader. Open a terminal window, and type:

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

Delete everything in the file, and paste this instead:

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

Save and close the file. That will make all PAM-aware applications use the fingerprint reader. Unfortunately, this also includes sudo. Since sudo is a command line application, it will display prompts in a terminal for you to swipe your finger, which is all well and good. The problem with this is that many Ubuntu administrative applications (such as Synaptic) use gksu to present a graphical front-end to sudo, which will output messages on the command line which you'll never see. Result? Administrative programs won't work from the gnome menu. The solution is to make sudo use the good old password. Open a terminal and type:

: {{cmduser|sudo gedit /etc/pam.d/sudo}}

Delete everything in the file, and instead paste:

<pre>
#%PAM-1.0

#@include common-auth
auth required pam_unix.so nullok_secure
@include common-account
</pre>

Now, save the file and close it, and reboot your system. GDM will ask you for a username, and then show a pretty prompt where you can scan your fingerprint! Same goes for gnome-screensaver when you set it to lock. Sometimes gnome-screensaver will not display the prompt, but you should still swipe your finger and be able to log back in.

===Bluetooth with Mobile Phones/PDAs===

Rather strangely, Ubuntu seems to have taken a step backwards with Bluetooth useability in Edgy. What worked out of the box with Dapper, now requires configuratio. First, open System - Preferences - Sessions and go to the Startup Programs tab. Then, find the entry labelled 'bt-applet --sm-disable'. Highlight it and click disable. Click add and in the command field type 'bt-applet'. Repeat this process, adding an entry for 'gnome-obex-server'. Now, open Synaptic Package Manager (System - Administration - Synaptic Package Manager) and click Search. Type 'gnome-bluetooth' to find the package, then mark it for installation. Now repeat this process for 'bluez-passkey-gnome'. Click apply to make changes.

Now that everything is installed, log-out of Gnome and log back in again. From your phone/PDA, search for devices untill you see your ThinkPad (the hostname will be displayed). Pair with the device. When asked for a passkey, enter 1234, which is the default. If you want to change your passkey (and you should), open a terminal and type:

: {{cmduser|sudo gedit /etc/bluetooth/hcid.conf}}

Find the line which says 'Default PIN for incoming connections' and change the PIN on the line beneath it:

<pre>
# Default PIN code for incoming connections
passkey "4017";
</pre>

Save and close the file, then type:

: {{cmduser|sudo /etc/init.d/bluetooth restart}}

You will now be able to use your new PIN code. To send files from your device to the ThinkPad, simply select the file you want to send and click Send Via Bluetooth (or whatever option your device presents). A dialog will pop-up in Gnome showing you a new file has been received.

: Figure 9. Gnome informing us that a file has been received
: [[Image:bluetooth.jpg]]

Sending files from your ThinkPad to your device requires more effort. The way it should work is that you right-click on a file, click send to, then make sure 'Bluetooth (OBEX)' is selected. Your device should be displayed and you could just click send. Unfortunately, due to a bug in gnome-bluetooth (described in https://launchpad.net/distros/ubuntu/+source/gnome-bluetooth/+bug/70718) this method does not work. If it does work for you, the bug has been solved and you can skip the rest of this section.

Your only other option is to use the command line to send files to your device. Open a terminal, then type:

: {{cmduser|hcitool scan}}

A list of detected bluetooth devices will be shown, for example, my output shows the following:

<pre>
Scanning ...
00:09:DD:60:02:EB Photosmart 8100 series
00:14:A7:99:3C:1F ThElInK
</pre>

The first field is the MAC address of the device, the second is the name of the device. In this case my bluetooth printer and mobile phone (ThElInK) were detected. In order to send files to my phone, I use:

: {{cmduser|gnome-obex-send -d 00:14:A7:99:3C:1F myPicture.jpg}}

Replace the MAC address with that of your device and myPicture.jpg with the file you want to send.

===TrackPoint Scrolling===

By default you can use the right and bottom edges of your touchpad to scroll through documents. If you use the TrackPoint instad of the touchpad (and believe me, you should), you'll find that scrolling is disabled by default. To enable it, open a terminal and type:

: {{cmduser|sudo gedit /etc/X11/xorg.conf}}

Now find the entry for your TrackPoint device. In my configuration file, the TrackPoint entry is the first mouse entry, after the keyboard entry, and looks something like this:

<pre>
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection
</pre>

Right after this entry is my touchpad entry. My entry is on line 66, but yours may be different. Now, add the follwing two options in that InputDevice section:

<pre>
Option "EmulateWheel" "on"
Option "EmulateWheelButton" "2"
</pre>

Save and exit the file. Restart your ThinkPad (or logout, and press CTRL-ALT-BACKSPACE). You should now be able to scoll by holding down the middle button for your TrackPoint and using the TrackPoint to scroll.

===Getting Multimedia to Work===

Due to patents and similar legal crap, Ubuntu will not play most media files by default. You also won't get browser plugins for multimedia. Luckily, this is easily fixed. Open a terminal and type the following:

: {{cmduser|sudo cp /etc/apt/sources.list /etc/apt/sources.list.backup}}
: {{cmduser|sudo gedit /etc/apt/sources.list}}

Delete everything in the file, and instead paste the following:

<pre>
deb-src http://archive.ubuntu.com/ubuntu edgy main restricted universe multiverse
#deb http://archive.ubuntu.com/ubuntu edgy-proposed main restricted universe multiverse

## MAJOR BUG FIX UPDATES produced after the final release
deb-src http://archive.ubuntu.com/ubuntu edgy-updates main restricted universe multiverse

## UBUNTU SECURITY UPDATES
deb http://security.ubuntu.com/ubuntu edgy-security main restricted universe multiverse
deb-src http://security.ubuntu.com/ubuntu edgy-security main restricted universe multiverse

## BACKPORTS REPOSITORY (Unsupported. May contain illegal packages. Use at own risk.)
#deb http://archive.ubuntu.com/ubuntu edgy-backports main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu edgy-backports main restricted universe multiverse

## PLF REPOSITORY
deb http://packages.freecontrib.org/ubuntu/plf edgy-plf free
deb-src http://packages.freecontrib.org/ubuntu/plf edgy-plf free
deb http://packages.freecontrib.org/ubuntu/plf edgy-plf non-free
deb-src http://packages.freecontrib.org/ubuntu/plf edgy-plf non-free

## CANONICAL COMMERCIAL REPOSITORY (Hosted on Canonical servers, not Ubuntu
## servers. RealPlayer10, Opera, DesktopSecure and more to come.)
deb http://archive.canonical.com/ubuntu edgy-commercial main

## Listen
#deb http://theli.free.fr/packages/ edgy listen

## Automatix repo
deb http://www.getautomatix.com/apt edgy main
</pre>

Now, open a terminal and type the following:

: {{cmduser|wget <nowiki>http://packages.freecontrib.org/ubuntu/plf/12B83718.gpg</nowiki> -O- <nowiki>|</nowiki> sudo apt-key add -}}
: {{cmduser|wget <nowiki>http://www.getautomatix.com/apt/key.gpg.asc</nowiki>}}
: {{cmduser|gpg --import key.gpg.asc}}
: {{cmduser|gpg --export --armor 521A9C7C <nowiki>|</nowiki> sudo apt-key add -}}
: {{cmduser|sudo apt-get update}}
: {{cmduser|sudo apt-get install automatix2}}
: {{cmduser|wget <nowiki>http://easyubuntu.freecontrib.org/files/easyubuntu-3.023.tar.gz</nowiki>}}
: {{cmduser|tar -zxf easyubuntu-3.023.tar.gz}}
: {{cmduser|cd easyubuntu}}
: {{cmduser|cp packagelist-dapper.pot packagelist-edgy.pot}}
: {{cmduser|cp packagelist-dapper.xml packagelist-edgy.xml}}
: {{cmduser|sudo python easyubuntu.in}}

Don't worry if you get errors from the Ubuntu PLF repository. PLF mirrors are about as stable as wild bull in a farm full of cows. Select what you want to install from the resulting window. Make sure you do not select the totem-mozilla plugin, as this just doens't work, for me at least. When EasyUbuntu has finished installing packages, you should be returned to a terminal, which you can close. Now go to Applications - System Tools - Automatix. Read and agree to the warning. Check what you want to install. Make sure you check 'Mplayer and FF plugin'. When ready, click the 'install' button. That should get multimedia working nicely.

: Figure 10. The Automatix user interface
: [[Image:automatix.jpg]]

===Beryl - fancy 3D desktop===

MAC OS X has Aqua and Windows Vista has Aero. Well, Linux has XGL/Beryl which can get effects which are as good looking (or sometimes better!) than the former two. Installing Beryl on Ubuntu is not that hard. First, open a terminal and type the following:

: {{cmduser|sudo gedit /etc/apt/sources.list}}

At the end of the file, append the following:

<pre>
##Beryl
deb http://ubuntu.beryl-project.org/ edgy main
</pre>

Save and close the file. Now type:

: {{cmduser|wget <nowiki>http://beryl-mirror.lupine.me.uk/1609B551.gpg</nowiki> -O- <nowiki>|</nowiki> sudo apt-key add -}}
: {{cmduser|sudo apt-get update}}

ATI Users Only: type

: {{cmduser|sudo apt-get install xserver-xgl}}

Now, to install beryl:

: {{cmduser|sudo apt-get install beryl emerald-themes}}

To make Ubuntu use the 3D effects. Open a terminal:

: {{cmduser|sudo gedit /usr/local/bin/startxgl.sh}}

In that file, paste the following if you use an ATI card:

<pre>
#!/bin/sh
Xgl -fullscreen :1 -ac -br -accel glx:pbuffer -accel xv:pbuffer &
sleep 4
export DISPLAY=:1
exec gnome-session
</pre>

If you use an Intel card, paste the following instead:

<pre>
#!/bin/sh
beryl-manager
sleep 4
exec gnome-session
</pre>

Save the file and close. Now we need to make the file executable:

: {{cmduser|sudo chmod a+x /usr/local/bin/startxgl.sh}}

All that's left now is to create a login script which makes gnome use the 3D effects. In a terminal, type:

: {{cmduser|sudo gedit /usr/share/xsessions/xgl.desktop}}

Now, in this file paste:

<pre>
[Desktop Entry]
Encoding=UTF-8
Name=Xgl
Exec=/usr/local/bin/startxgl.sh
Icon=
Type=Application
</pre>

Save and close the file. Now type:

: {{cmduser|sudo gedit /usr/local/bin/start_beryl.sh}}

In this file, paste:

<pre>
#!/bin/bash
#
# Start beryl-manager within gnome-session
#
if [ `ps -A -o comm | grep -c '^Xgl$'` == "1" ]; then
DISPLAY=:1 beryl-manager
DISPLAY=:1 beryl-xgl
else echo "${0}: Error: beryl-manager not launched. Xgl not running?"
fi
</pre>

Now make the file executable:

: {{cmduser|sudo chmod a+x /usr/local/bin/start_beryl.sh}}

Now go to System - Preferences - Sessions, go to the Startup Programs tab, and click add, then type

: {{cmduser|/usr/local/bin/start_beryl.sh}}

Now, reboot your ThinkPad. When you come to the login screen, click the 'Sessions' button on the bottom left corner, and select XGL. login, et voila! beautiful 3D effects!

: Figure 11. Beryl's Cube effect
: [[Image:cube.jpg]]

If you have NetBeans installed, try launching it now. It probably won't work due to Beryl. Luckily, this is easily solved. Open a terminal and type:

: {{cmduser|sudo gedit /etc/environment}}

Then add the following line to the end of the file.

<pre>AWT_TOOLKIT="MToolkit"</pre>

Now save, close and reboot. Netbeans should now work!

===Problem: Can't add programs to session===

So you tried to add something to your startup programs, it shows up in the list, but it doesn't start up. You then launch the sessions program again, only to find your program has disappeared from the list. This problem is being caused by incorrect permissions in your home directory, and can happen on some occasions. To fix it, open a terminal and type the following:

: {{cmduser|sudo chown -R username:usergroup /home/username/.config/}}

Replace username with your username and usergroup with your group (by default, in Ubuntu your usergroup is the same as your username). Everything should be OK now!

===Problem: Virtual terminals not working===

One problem I had after installing the ATI drivers was that virtual terminals stopped working. Instead of seeing a console when pressing CTRL+ALT+F1...F6 I was seeing a yellow/orange garbled output. Luckily, solving this with ATI drivers is trivial. Open a terminal, and type:

: {{cmduser|sudo gedit /boot/grub/menu.lst}}

Find the line which says

<pre>#defoptions=quiet splash</pre>

and replace it with

<pre>#defoptions=quiet splash vga=791</pre>

Now, find the line which boots the kernel you are currently using, this is just under '## ## End Default Options ##. In the 'kernel' line, add:

<pre>vga=791</pre>

Before:

<pre>kernel /vmlinuz-2.6.17-10-generic root=/dev/sda7 ro quiet splash</pre>

After:

<pre>kernel /vmlinuz-2.6.17-10-generic root=/dev/sda7 ro quiet splash vga=791</pre>

Now save and exit the file, and reboot. Virtual terminals should now work. If you use Intel drivers, you're going to have to bite the bullet and remove the 'splash' keyword from both the defoptions and kernel lines. You'll lose the pretty bootup screen, but at least virtual terminals will work, which are important to recover a crashed system.

===Problem: Microphone doesn't work===

Initially, the microphone didn't work, which appears to be linked to the a missing file /etc/asound.names. Executing

: {{cmduser|sudo alsactl names}}
: {{cmduser|sudo alsactl store}}

to generate /etc/asound.names and /var/lib/alsa/asound.state seems to fix sound problems.

(the original fix is on http://ubuntuforums.org/showthread.php?t=272166)

===Problem: I keep logging out!===

If you're using Beryl, and find that you keep getting logged out, you've just encountered one of Beryl's most annoying bugs. Shift+Backspace causes a logout. To fix this, open a terminal and type:

: {{cmduser|gedit /home/username/annoymenot.sh}}

Remember to replace 'username' with your username. Now, in this file type:

: {{cmduser|xmodmap -e "keycode 22 <nowiki>=</nowiki> BackSpace BackSpace Terminate_Server" }}

Save and close the file, and make it executable:

: {{cmduser|chmod 755 /home/username/annoymenot.sh}}

Now go to System - Preferences - Session, Startup Programs. Click add, and type

: {{cmduser|/home/username/annoymenot.sh}}

Logout and back in, problem solved! While you're at it, how about getting the start button to work? Go to System - Preferences - Keyboard - Layout Options - Alt/Win Key behaviour and select 'Super is mapped to Win keys (default)'.

===Desktop envy===

We're living in an age of desktop prettyness, and Linux can be just as pretty as MAC OS X or Vista. You've already got Beryl installed. Now go to Applications - Accesories - gDesklets. If the gDesklets entry is not there, make sure you install it, either using Synaptic or Automatix. Desklets are small programs you can add to your desktop, ala OS X's Deskbar or Vista's Sidebar. To make them start on boot, add gdesklets in System - Preferences - Sessions, Startup Programs.

Another cool program is cairo clock. Download it from http://macslow.thepimp.net/projects/cairo-clock/cairo-clock_0.3.2-1_i386.deb and install it by double-clicking. To make it start automatically, add it to your sessions as mentioned above. I've found the following command makes it work best for me:

<pre>cairo-clock -s -w 175 -g 175 -x 1219 -y 7 -t radium</pre>

Finally, make sure you click that Ruby icon in your notification area, it allows you to configure Beryl to do all sorts of cool stuff!

===Conclusion===

Well, that's about it! A dream Linux system on a dream laptop! Check out these cool technologies for an even better system:

* Beagle
* Tomboy
* Deskbar

===References===

* ATI on Ubuntu - https://help.ubuntu.com/community/BinaryDriverHowto/ATI
* Garbled Virtual Terminal Bug - https://launchpad.net/distros/ubuntu/+source/usplash/+bug/63558
* Beryl logout Bug - http://forum.beryl-project.org/viewtopic.php?p=1295&sid=6feedd09a7f01bca68feb05a5f2f033c
* Beryl Netbeans Bug - http://ubuntuforums.org/showthread.php?t=252594
* Beryl on Ubuntu - http://wiki.beryl-project.org/index.php/Install/Ubuntu/Edgy/XGL
* Home directory permissions bug - http://www.ubuntuforums.org/showthread.php?p=1789997
* gnome-bluetooth bug - https://launchpad.net/distros/ubuntu/+source/gnome-bluetooth/+bug/70718
* Atheros network cards on Ubuntu - http://ubuntuforums.org/showthread.php?t=38972

Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60

2006-12-24T18:57:06Z

Ischg: /* Problem: Microphone doesn't work */

Created by: [[User:Keithvassallo|Keithvassallo]] 14:39, 16 December 2006 (CET)

Thanks for valuable contributions by:

: [[User:Ischg|Ischg]]
: [[User:Soon|Soon]]

===Abstract===

This article describes how to get Ubuntu Linux 6.10 (Edgy) installed on an IBM/Lenovo ThinkPad T60. It's not meant to be a definite guide to installing Ubuntu (the Ubuntu Guide at http://www.ubuntuguide.org does a very good job of that). This article is meant to describe how to get most of the ThinkPad features working on Ubuntu system. It also discusses how to get Multimedia, some cool-looking effects such as Beryl, gDesklets and similar working on Ubuntu. Finally, we discuss some common problems encountered on Ubuntu and ThinkPads alike.

{{NOTE|I am in no means an expert, the methods described here are those which got everything to work for me - your mileage may vary. A big thank you to all ThinkWiki users who keep contributing on improving this article.}}

===My ThinkPad===

Although this guide should work on most recent ThinkPads, I cannot guarantee that. These are the specifications of my machine. The closer your specs are, the greater the chance of success.

: Figure 1. ThinkPad T60 2007, complete with Tux sticker :-)
: [[Image:thinkpad.jpg]]

* Lenovo ThinkPad T60 2007.
* Intel Centrino Duo T2400 / 1.83 GHz.
* Mobile Intel 945PM Express Chipset.
* Intel Wireless LAN.
* Integrated Bluetooth.
* ATI Mobility Radeon X1400 - PCI Express x16, 128MB dedicated RAM.
* 100 GB - Serial ATA-150 Hard Drive.
* 15' TFT Active Matrix Display (1400x1050).

That's basically all you need to know. As far as I know, all other features are common to all ThinkPads manufactured by Lenovo since they acquired IBM's computer business.

===Why Ubuntu? (or rather, Why not SUSE?)===

In June 2006, Lenovo announced it would be shipping ThinkPad T60p laptops with SUSE Linux Enterprise Desktop (SLED) 10 pre-installed, since SLED apparently supports all of the features of the T60p. I contacted my local IBM supplier, who said that Lenovo were no longer manufacturing the T60p, since the company which was making the displays went out of business. This meant I could not get a T60p with SLED pre-installed. I decided to go for the T60 2007, which is the closest thing I could find to the T60p. This comes with Windows XP Professional pre-installed.

I first tried to get SLED installed on the T60. Although it did indeed install, and most features worked, I soon got bored of SLED. Firstly, SLED uses Gnome 2.12, which is by now ancient. Secondly, although the Lenovo utilities do work on SLED, they only work well if you use KDE as your defauly desktop environment, which is a pity since I'm a Gnome user. The utilities were very unstable to me too. Finally, what made me give up SLED was the usual problem - it's an RPM based distribution. Once you start using Debian derivatives, with their apt based installer, you won't want to go back. That's when I decided to try Ubuntu, and have not regretted it since.

===What Works?===

* Ubuntu and all programs it comes with.
* Most of the function keys, except the ones mentioned below
* The fingerprint reader.
* The ATI proprietary graphics drivers.
* Suspend to RAM (Sleep) and Suspend to Disk (Hibernate).
* Brightness, Volume and Mute with OSD (On-Screen Display).
* ThinkLight, TrackPoint II and the touchpad.

===What Doesn't Work? (Known Issues)===

* FN+F8, FN+F9, FN+ZOOM.
* The BACK and FORWARD buttons (next to the cursor keys).
* The ThinkVantage button (in Linux, still works on boot).
* Sending files to Bluetooth devices via GUI.

There are probably ways and means to get the offending buttons to work, I've tried several fora but none seem to address my exact problem. I'll update this article should I find out anything.

===First Things First - Creating a Windows Recovery Disc===

If you've purchased a T60, chances are it came with Windows XP Professional. The other option is for you to have FreeDOS installed, in which case you can skip this section. You could remove the Windows partition altogether, and reserve your ThinkPad for Linux, but that's not the route I've chosen. The ThinkVantage utilities in Windows allow you to do a lot of cool things, such as set-up a boot-up fingerprint security scan. You can't do this from Linux (as far as I know) so it's best to leave the Windows partition in place. So, boot your ThinkPad and complete the Windows XP setup (which asks you to add a user account and enroll yourself using the ThinkVantage Client Security Solution). While you're there, use the ThinkVantage productivy centre to enroll your fingerprint (I suggest enrolling more than one) and make sure you check the option to require a fingerprint scan on boot (not for security, for geek points). When you reboot, press ESC or F2 to get to BIOS, and make sure you check the option to require a supervisor password. This will make your ThinkPad prompt you for your fingerprint when you power it up.

: Figure 2. Configuring fingerprint security from Windows
: [[Image:winprint.jpg]]

Now that's working, you should create a recovery DVD using the ThinkVantage recovery utilities. This will allow you to recover your Windows installation should you manage to screw your partitions up in the following stages. I highly recommend you do this, as Lenovo does not provide Windows XP CDs with this Laptop - so the hard disk partition is all you've got. Once this is done, we're ready to install Ubuntu!

: Figure 3. Creating recovery discs from Windows
: [[Image:recovery.jpg]]

===Getting Ubuntu installed===

Download the latest Edgy live CD from the Ubuntu website, you can find a list of mirrors at http://www.ubuntu.com/products/GetUbuntu/download#currentrelease. You may also try Kubuntu, Edubuntu or any of it's derivatives, but I'll stick with Ubuntu here for simplicity's sake. Once that's downloaded, burn the ISO to disc using any program of your choice (If this is your first Linux experience and you're using Windows, try using Nero - http://www.nero.com).

Once the burning process is complete, reboot your machine ensuring that the Ubuntu CD is in the drive. You should see an Ubuntu menu. If you don't, your BIOS is not set to boot from CD. Reboot your ThinkPad and change the boot order from BIOS (by default ThinkPads boot from CD-ROM before the hard disk, so this is probably not necessary). Once the menu shows up, select 'Start or install Ubuntu' and let it boot. This will take a while as everything is loaded from CD. You should eventually end up in a Gnome desktop. If you see an error about the Gnome Settings Daemon not being able to load, simply ignore it, as this is not necessary for now. For the purposes of the installation, it's best if you have a wired ethernet connection, as it's unlikely the wireless network card will work until we boot into our installed Ubuntu system.

: Figure 4. Select the first option to start Ubuntu
: [[Image:boot.jpg]]

Double-Click on the 'install' icon on the Desktop to start installation. The installation should be pretty straight-forward. If you need additional help, check out the walk-through with screen-shots at http://www.debianadmin.com/ubuntu-edgy-eft-desktop-installation-with-screenshots.html. The only stage at which we need to make changes is the partitioning stage. This to make sure we preserve our Windows partition, and the IBM vendor_diag partition which allows recovery of the laptop when things go hay-wire. In the 'Prepare disk space' section of the installer, select the third option, 'Manually edit partition table'. A bar will be displayed showing your existing partitions. If you have Windows installed you will see two partitions. The first is a 4.89 GB IBM Vendor Diagnostic partition, which we do not want to touch. The second will be your Windows partition, which will fill the rest of the disk. Click on this partition, Then click the 'Resize/Move' button. I resized my Windows partition to 24 GB. This is enough to accommodate the 10 GB already in use on that partition, as well as giving Windows another 14 GB of free space. 6 GB of free space would probably be enough though.

Now it's time to create partitions for Linux. You need at least two partitions; a swap partition which should be roughly double the amount of RAM you have, and a root partition to install Linux. I opted for four partitions, as follows:

<table border=1>
<tr><td>'''Purpose'''</td><td>'''Size'''</td><td>'''File-System'''</td></tr>
<tr><td>Swap</td><td>2 GB</td><td>swap</td></tr>
<tr><td>/boot</td><td>5 GB</td><td>ext3</td></tr>
<tr><td>/ (root)</td><td>20 GB</td><td>ext3</td></tr>
<tr><td>/home</td><td>37.25 GB (what's left of the disk)</td><td>ext3</td></tr>
</table>

To create these paritions, click on the 'New' button and select 'Extended Partition' in the 'create as' drop-down list. Leave all other settings as-is, and click 'Add'. Now, click on the newly created partition, and create each of the partitions you want to create, simply specify the size of the partition in the 'New Size (MiB)' text box. To convert GB to MiB, multiply by 1024. So for your swap partition you should specify a size of 2048. Repeat until you have created all the required partitions. If you follow my parition layout, the partition editor should look something like Figure 5.

: Figure 5. Our partitions, ready to be created
: [[Image:partitioning.jpg]]

You will not see mount-points in your diagram, because the screen-shot above was taken after they were assigned, but you should get the general idea. After this screen, you will be asked to assign mount-points to the partitions you have just created. If you created the partitions in the same order I did, you can assign mount points as I have (i.e. /dev/sda5 for swap, /dev/sda6 for /boot, /dev/sda7 for /, /dev/sda8 for /home). Additionally, I mounted my Windows partition as /media/sda1 and my IBM Vendor Diagnostic partition as /media/sda2. These are optional. After this step, continue installation as normal. When the installation is complete, click the 'reboot' button to restart into your fresh Ubuntu System.

When booting, the GRUB boot-loader will be displayed, asking you what you want to load. You will probably see four options. The first two being Ubuntu Linux and Ubuntu Linux recovery mode (showing the kernel version). The other two will be Microsoft Windows XP, and 'Other Windows XP/2000/NT' partition. This is your IBM Vendor Diagnostic partition, which is based on the Windows kernel, apparently. Select the first entry to boot Ubuntu. The next time you boot Windows, it will bring up a chkdsk screen. This is entirely normal and happens because we have resized the Windows partition. Make sure you do not skip this check and let it complete.

===Wireless LAN===

{{WARN|Another ThinkWiki user notes that not all T60s come with the Intel wireless chip. If you are not entirely sure what wireless NIC you use, please read the following section (Non-Intel Network Cards).}}

The first thing we should do is to get wireless networking working. Luckily, getting the Centrino wireless LAN chip working in Ubuntu is quite easy, if you use the gnome-network-manager applet. Just go to System - Administration - Synaptic Package Manager. Then click 'Search' and set the 'look-in' field to 'name'. In the 'Search' text box type:

<pre>network-manager</pre>

: Figure 6. Installing the network manager applet
: [[Image:networkmanager.jpg]]

Click on the box beside 'network-manager' and click 'Mark for installation'. Do the same for 'network-manager-gnome'. Once installed, reboot your ThinkPad. An applet will show up in the gnome notification area. Click on it, and a list of detected wireless networks will be displayed. Simply click on one of them, enter any authentication details necessary, and you'll be connected to the wireless network.

: Figure 7. gnome-network-manager showing available wireless networks
: [[Image:available-accesspoints.jpg]]

===Non-Intel Network Cards===

Not all versions of the T60 have the Intel Wireless LAN as described above. Run the following command to see details about detected wireless cards:

: {{cmduser| lspci}}

Look for a line which shows detected network cards. Users of Intel network cards will see something similar to the following output:

<pre>03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)</pre>

If you see the above, you can jump to the next section. If you do not see the above, your network card is not Intel. You may see something similar to:

<pre>03:00.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)</pre>

If that's the output you get, you're going to have to take some additional steps to get wireless networking working. Read more at http://ubuntuforums.org/showthread.php?t=38972

running:

: {{cmdroot| dmesg <nowiki>|</nowiki> grep hal}}

may yield output like this:

<pre>
[17179590.420000] ath_hal: module license 'Proprietary' taints kernel.
[17179590.424000] ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
</pre>

Which suggests the hardware abstraction layer is in place.

If not, or if the output contains "HAL Status 13" it suggests your card is not supported by the current drivers, and you need to upgrade.

===Installing the ATI display drivers===

If your ThinkPad has an Intel graphics adapter, you should skip this section as Ubuntu installs the best driver automatically. Ubuntu does not install the ATI proprietary drivers by default because they are, er, proprietary. Luckily, installing them is easy enough. Open a terminal (Applications - Accessories - Terminal) and type the following:

: {{cmduser| sudo apt-get update}}
: {{cmduser| sudo apt-get install xorg-driver-fglrx fglrx-control}}

Now we make sure the proprietary driver is not disabled by the kernel. Type the following, and remove any lines referring to fglrx

: {{cmduser|sudo gedit /etc/default/linux-restricted-modules-common}}

An alternative to gedit (Gnome) is nano (sudo nano -w /etc...) for a CLI editor.

Finally, we need to configure the X server to use the ATI drivers. Type the following:

: {{cmduser|sudo depmod -a}}
: {{cmduser|sudo aticonfig --initial}}
: {{cmduser|sudo aticonfig --overlay-type<nowiki>=</nowiki>Xv}}

One last thing. In order to correct a very common problem of getting a jerky video display, type the following:

: {{cmduser|sudo gedit /etc/X11/xorg.conf}}

Scroll to the end of the file, and add the text below.

<pre>
Section "Extensions"
Option "Composite" "0"
EndSection
</pre>

Save the file and exit. Now, to apply the changes either press CTRL+ALT+Backspace or reboot. The resolution should have switched to 1400x1050 and everything should look prettier and render faster. Just to make sure everything is working, open up a terminal and type

: {{cmduser|fglrxinfo}}

This should display:

<pre>
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Mobility Radeon X1400 Generic
OpenGL version string: 2.0.6011 (8.28.8)
</pre>

The above is what I get on my ThinkPad, and you should see something similar. As long as you see your graphics card model listed, everything should be OK. If, instead, you see a bunch of lines containing 'Mesa' then you have a problem. In that case, I recommend consulting https://help.ubuntu.com/community/BinaryDriverHowto/ATI and the Ubuntu forums at http://ubuntuforums.org

===The Fingerprint Reader===

Although IBM does not officially support it, the fingerprint reader does in fact work with most Linux distributions. Getting it to work with Ubuntu can be a bit of a pain, but it does work. Basically, a bioAPI plugin is provided for PAM. PAM-aware applications such as GDM and gnome-screensaver will then automatically use the fingerprint reader, which is uber cool. Anyway, enough theory, I've probably lost the newbies amongst you already. Go to http://www.qrivy.net/~michael/temp/ and download the latest bioapi package (at the time of writing, bioapi_1.2.3_i386.deb). When asked, tell Firefox to open the file with the GDebi package installer.

That will install bioAPI. What we need now is the driver for our fingerprint device, which is manufactured by UPEK. Go to http://www.upek.com/support/dl_linux_bsp.asp and download the latest version, currently UPEK_BSP_LIN_1.0.zip. Extract this file, then open a terminal (and don't close it until I say so).

: {{cmduser|cd /path/to/where/you/extracted/the/file}}
: {{cmduser|sudo bash}}
: {{cmdroot|sh install.sh /usr/lib}}

Now we need to assign the right permissions so non-root applications can use the driver:

: {{cmdroot|addgroup --system bioapi}}
: {{cmdroot|addgroup --system usbfs}}
: {{cmdroot|adduser yourusername bioapi}}
: {{cmdroot|adduser yourusername usbfs}}
: {{cmdroot|chown -R root:bioapi /usr/var/bioapi/}}
: {{cmdroot|chmod -R 770 /usr/var/bioapi/}}
: {{cmdroot|chown -R root:usbfs /proc/bus/usb}}
: {{cmdroot|chmod -R g+X /proc/bus/usb}}

Of course, replace 'yourusername' with the username you use to login. Now, we need to set the usb file system (usbfs) to be usable by users in the usbfs group. To do this, we need to determine the group ID of the usbfs group. Type the following:

: {{cmdroot|cat /etc/group <nowiki>|</nowiki> grep usbfs <nowiki>|</nowiki> cut -d':' -f 3}}

In my case the number is 116, it might be different for you. Now, open the file /etc/fstab:

: {{cmdroot|gedit /etc/fstab}}

and type the following:

<pre>none /proc/bus/usb usbfs defaults,devgid=116,devmode=0660,busgid=116,busmode=0770,listgid=116,listmode=0660 0 0</pre>

Please type the above code in one line in your file. Remember to replace 116 if you got a different number with the previous cat command. The last permission-related thing we need to fool around with is UDEV. Open the udev permissions file

: {{cmdroot|gedit /etc/udev/rules.d/40-permissions.rules}}

and find the line:

<pre>SUBSYSTEM=="usb_device", MODE="0664"</pre>

It's line 65 in my file. Change it so it looks like this:

<pre>SUBSYSTEM=="usb_device", MODE="0660", GROUP="usbfs"</pre>

Now we need to enroll our fingerprint with the system. To do this, we need a utility called Sample, which is only distributed in source-code form with the driver. This is great, only I couldn't get it to compile on Ubuntu. Luckily, there is a binary version available from one of the earlier releases of the driver (beta 2). To get this, download it from ftp://linux:Tuc-nak3@delta.upek.com/TFMESS_BSP_LIN_1.0beta2.zip. Now, extract the file and type:

: {{cmdroot|cd /path/to/where/you/extracted/the/archive}}
: {{cmdroot|cd NonGUI_sample}}
: {{cmdroot|chmod a+x Sample}}
: {{cmdroot|./Sample}}

Press (e) to enroll a new user, and enter your username when asked for the user ID. You will be asked to swipe your finger three times. Now press (v) and swipe your finger, a green check should be displayed showing you have successfully authenticated.

: Figure 8. The fingerprint swipe prompt
: [[Image:touchchip.jpg]]

Wonderful! Now, quit the application (q) and type exit to become a normal user. A file called yourusername.bir should have been created, copy this to your home directory:

: {{cmdroot|cp yourusername.bir /home/yourusername/}}

You can now close the terminal window. The next step is to install the BioAPI plug-in for PAM, and to make applications use the plugin. So, get the pam_bioapi plugin from http://www.nax.cz/pub/bioapi/pam_bioapi/pam-bioapi_0.3.0.tar.gz and extract it. Now open a terminal and type:

Comment: you will have to install some libraries in order to be able to compile the plugin

: {{cmduser|sudo apt-get install build-essential}}
: {{cmduser|sudo apt-get install libpam0g-dev}}

Now, you can compile and install the plugin

: {{cmduser|cd /path/to/where/you/extracted/the/arcive}}
: {{cmduser|./configure --libdir<nowiki>=</nowiki>/lib --enable-file-store && make}}
: {{cmduser|sudo make install}}

That's installed the plugin. Now, open a terminal and type the following:

: {{cmduser|cd ~}}
: {{cmduser|sudo bash}}

This will open a root session. Please do not close this until instructed. Now, paste the following scary command:

<pre>
SERIAL=`BioAPITest | sed -ne "/Fingerprint/{n;n;s/^.*: $.\{9\}$$.\{4\}$$.\{4\}$$.\{4\}$$.*$/\1-\2-\3-\4-\5/gp}"`
</pre>

Type the following to register your username and serial with the bioAPI.

: {{cmdroot|mkdir -p /etc/bioapi/pam/$SERIAL}}
: {{cmdroot|cp yourusername.bir /etc/bioapi/pam/$SERIAL}}
: {{cmdroot|exit}}

Phew. Now, to make applications actually use the fingerprint reader. Open a terminal window, and type:

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

Delete everything in the file, and paste this instead:

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

Save and close the file. That will make all PAM-aware applications use the fingerprint reader. Unfortunately, this also includes sudo. Since sudo is a command line application, it will display prompts in a terminal for you to swipe your finger, which is all well and good. The problem with this is that many Ubuntu administrative applications (such as Synaptic) use gksu to present a graphical front-end to sudo, which will output messages on the command line which you'll never see. Result? Administrative programs won't work from the gnome menu. The solution is to make sudo use the good old password. Open a terminal and type:

: {{cmduser|sudo gedit /etc/pam.d/sudo}}

Delete everything in the file, and instead paste:

<pre>
#%PAM-1.0

#@include common-auth
auth required pam_unix.so nullok_secure
@include common-account
</pre>

Now, save the file and close it, and reboot your system. GDM will ask you for a username, and then show a pretty prompt where you can scan your fingerprint! Same goes for gnome-screensaver when you set it to lock. Sometimes gnome-screensaver will not display the prompt, but you should still swipe your finger and be able to log back in.

===Bluetooth with Mobile Phones/PDAs===

Rather strangely, Ubuntu seems to have taken a step backwards with Bluetooth useability in Edgy. What worked out of the box with Dapper, now requires configuratio. First, open System - Preferences - Sessions and go to the Startup Programs tab. Then, find the entry labelled 'bt-applet --sm-disable'. Highlight it and click disable. Click add and in the command field type 'bt-applet'. Repeat this process, adding an entry for 'gnome-obex-server'. Now, open Synaptic Package Manager (System - Administration - Synaptic Package Manager) and click Search. Type 'gnome-bluetooth' to find the package, then mark it for installation. Now repeat this process for 'bluez-passkey-gnome'. Click apply to make changes.

Now that everything is installed, log-out of Gnome and log back in again. From your phone/PDA, search for devices untill you see your ThinkPad (the hostname will be displayed). Pair with the device. When asked for a passkey, enter 1234, which is the default. If you want to change your passkey (and you should), open a terminal and type:

: {{cmduser|sudo gedit /etc/bluetooth/hcid.conf}}

Find the line which says 'Default PIN for incoming connections' and change the PIN on the line beneath it:

<pre>
# Default PIN code for incoming connections
passkey "4017";
</pre>

Save and close the file, then type:

: {{cmduser|sudo /etc/init.d/bluetooth restart}}

You will now be able to use your new PIN code. To send files from your device to the ThinkPad, simply select the file you want to send and click Send Via Bluetooth (or whatever option your device presents). A dialog will pop-up in Gnome showing you a new file has been received.

: Figure 9. Gnome informing us that a file has been received
: [[Image:bluetooth.jpg]]

Sending files from your ThinkPad to your device requires more effort. The way it should work is that you right-click on a file, click send to, then make sure 'Bluetooth (OBEX)' is selected. Your device should be displayed and you could just click send. Unfortunately, due to a bug in gnome-bluetooth (described in https://launchpad.net/distros/ubuntu/+source/gnome-bluetooth/+bug/70718) this method does not work. If it does work for you, the bug has been solved and you can skip the rest of this section.

Your only other option is to use the command line to send files to your device. Open a terminal, then type:

: {{cmduser|hcitool scan}}

A list of detected bluetooth devices will be shown, for example, my output shows the following:

<pre>
Scanning ...
00:09:DD:60:02:EB Photosmart 8100 series
00:14:A7:99:3C:1F ThElInK
</pre>

The first field is the MAC address of the device, the second is the name of the device. In this case my bluetooth printer and mobile phone (ThElInK) were detected. In order to send files to my phone, I use:

: {{cmduser|gnome-obex-send -d 00:14:A7:99:3C:1F myPicture.jpg}}

Replace the MAC address with that of your device and myPicture.jpg with the file you want to send.

===TrackPoint Scrolling===

By default you can use the right and bottom edges of your touchpad to scroll through documents. If you use the TrackPoint instad of the touchpad (and believe me, you should), you'll find that scrolling is disabled by default. To enable it, open a terminal and type:

: {{cmduser|sudo gedit /etc/X11/xorg.conf}}

Now find the entry for your TrackPoint device. In my configuration file, the TrackPoint entry is the first mouse entry, after the keyboard entry, and looks something like this:

<pre>
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection
</pre>

Right after this entry is my touchpad entry. My entry is on line 66, but yours may be different. Now, add the follwing two options in that InputDevice section:

<pre>
Option "EmulateWheel" "on"
Option "EmulateWheelButton" "2"
</pre>

Save and exit the file. Restart your ThinkPad (or logout, and press CTRL-ALT-BACKSPACE). You should now be able to scoll by holding down the middle button for your TrackPoint and using the TrackPoint to scroll.

===Getting Multimedia to Work===

Due to patents and similar legal crap, Ubuntu will not play most media files by default. You also won't get browser plugins for multimedia. Luckily, this is easily fixed. Open a terminal and type the following:

: {{cmduser|sudo cp /etc/apt/sources.list /etc/apt/sources.list.backup}}
: {{cmduser|sudo gedit /etc/apt/sources.list}}

Delete everything in the file, and instead paste the following:

<pre>
deb-src http://archive.ubuntu.com/ubuntu edgy main restricted universe multiverse
#deb http://archive.ubuntu.com/ubuntu edgy-proposed main restricted universe multiverse

## MAJOR BUG FIX UPDATES produced after the final release
deb-src http://archive.ubuntu.com/ubuntu edgy-updates main restricted universe multiverse

## UBUNTU SECURITY UPDATES
deb http://security.ubuntu.com/ubuntu edgy-security main restricted universe multiverse
deb-src http://security.ubuntu.com/ubuntu edgy-security main restricted universe multiverse

## BACKPORTS REPOSITORY (Unsupported. May contain illegal packages. Use at own risk.)
#deb http://archive.ubuntu.com/ubuntu edgy-backports main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu edgy-backports main restricted universe multiverse

## PLF REPOSITORY
deb http://packages.freecontrib.org/ubuntu/plf edgy-plf free
deb-src http://packages.freecontrib.org/ubuntu/plf edgy-plf free
deb http://packages.freecontrib.org/ubuntu/plf edgy-plf non-free
deb-src http://packages.freecontrib.org/ubuntu/plf edgy-plf non-free

## CANONICAL COMMERCIAL REPOSITORY (Hosted on Canonical servers, not Ubuntu
## servers. RealPlayer10, Opera, DesktopSecure and more to come.)
deb http://archive.canonical.com/ubuntu edgy-commercial main

## Listen
#deb http://theli.free.fr/packages/ edgy listen

## Automatix repo
deb http://www.getautomatix.com/apt edgy main
</pre>

Now, open a terminal and type the following:

: {{cmduser|wget <nowiki>http://packages.freecontrib.org/ubuntu/plf/12B83718.gpg</nowiki> -O- <nowiki>|</nowiki> sudo apt-key add -}}
: {{cmduser|wget <nowiki>http://www.getautomatix.com/apt/key.gpg.asc</nowiki>}}
: {{cmduser|gpg --import key.gpg.asc}}
: {{cmduser|gpg --export --armor 521A9C7C <nowiki>|</nowiki> sudo apt-key add -}}
: {{cmduser|sudo apt-get update}}
: {{cmduser|sudo apt-get install automatix2}}
: {{cmduser|wget <nowiki>http://easyubuntu.freecontrib.org/files/easyubuntu-3.023.tar.gz</nowiki>}}
: {{cmduser|tar -zxf easyubuntu-3.023.tar.gz}}
: {{cmduser|cd easyubuntu}}
: {{cmduser|cp packagelist-dapper.pot packagelist-edgy.pot}}
: {{cmduser|cp packagelist-dapper.xml packagelist-edgy.xml}}
: {{cmduser|sudo python easyubuntu.in}}

Don't worry if you get errors from the Ubuntu PLF repository. PLF mirrors are about as stable as wild bull in a farm full of cows. Select what you want to install from the resulting window. Make sure you do not select the totem-mozilla plugin, as this just doens't work, for me at least. When EasyUbuntu has finished installing packages, you should be returned to a terminal, which you can close. Now go to Applications - System Tools - Automatix. Read and agree to the warning. Check what you want to install. Make sure you check 'Mplayer and FF plugin'. When ready, click the 'install' button. That should get multimedia working nicely.

: Figure 10. The Automatix user interface
: [[Image:automatix.jpg]]

===Beryl - fancy 3D desktop===

MAC OS X has Aqua and Windows Vista has Aero. Well, Linux has XGL/Beryl which can get effects which are as good looking (or sometimes better!) than the former two. Installing Beryl on Ubuntu is not that hard. First, open a terminal and type the following:

: {{cmduser|sudo gedit /etc/apt/sources.list}}

At the end of the file, append the following:

<pre>
##Beryl
deb http://ubuntu.beryl-project.org/ edgy main
</pre>

Save and close the file. Now type:

: {{cmduser|wget <nowiki>http://beryl-mirror.lupine.me.uk/1609B551.gpg</nowiki> -O- <nowiki>|</nowiki> sudo apt-key add -}}
: {{cmduser|sudo apt-get update}}

ATI Users Only: type

: {{cmduser|sudo apt-get install xserver-xgl}}

Now, to install beryl:

: {{cmduser|sudo apt-get install beryl emerald-themes}}

To make Ubuntu use the 3D effects. Open a terminal:

: {{cmduser|sudo gedit /usr/local/bin/startxgl.sh}}

In that file, paste the following if you use an ATI card:

<pre>
#!/bin/sh
Xgl -fullscreen :1 -ac -br -accel glx:pbuffer -accel xv:pbuffer &
sleep 4
export DISPLAY=:1
exec gnome-session
</pre>

If you use an Intel card, paste the following instead:

<pre>
#!/bin/sh
beryl-manager
sleep 4
exec gnome-session
</pre>

Save the file and close. Now we need to make the file executable:

: {{cmduser|sudo chmod a+x /usr/local/bin/startxgl.sh}}

All that's left now is to create a login script which makes gnome use the 3D effects. In a terminal, type:

: {{cmduser|sudo gedit /usr/share/xsessions/xgl.desktop}}

Now, in this file paste:

<pre>
[Desktop Entry]
Encoding=UTF-8
Name=Xgl
Exec=/usr/local/bin/startxgl.sh
Icon=
Type=Application
</pre>

Save and close the file. Now type:

: {{cmduser|sudo gedit /usr/local/bin/start_beryl.sh}}

In this file, paste:

<pre>
#!/bin/bash
#
# Start beryl-manager within gnome-session
#
if [ `ps -A -o comm | grep -c '^Xgl$'` == "1" ]; then
DISPLAY=:1 beryl-manager
DISPLAY=:1 beryl-xgl
else echo "${0}: Error: beryl-manager not launched. Xgl not running?"
fi
</pre>

Now make the file executable:

: {{cmduser|sudo chmod a+x /usr/local/bin/start_beryl.sh}}

Now go to System - Preferences - Sessions, go to the Startup Programs tab, and click add, then type

: {{cmduser|/usr/local/bin/start_beryl.sh}}

Now, reboot your ThinkPad. When you come to the login screen, click the 'Sessions' button on the bottom left corner, and select XGL. login, et voila! beautiful 3D effects!

: Figure 11. Beryl's Cube effect
: [[Image:cube.jpg]]

If you have NetBeans installed, try launching it now. It probably won't work due to Beryl. Luckily, this is easily solved. Open a terminal and type:

: {{cmduser|sudo gedit /etc/environment}}

Then add the following line to the end of the file.

<pre>AWT_TOOLKIT="MToolkit"</pre>

Now save, close and reboot. Netbeans should now work!

===Problem: Can't add programs to session===

So you tried to add something to your startup programs, it shows up in the list, but it doesn't start up. You then launch the sessions program again, only to find your program has disappeared from the list. This problem is being caused by incorrect permissions in your home directory, and can happen on some occasions. To fix it, open a terminal and type the following:

: {{cmduser|sudo chown -R username:usergroup /home/username/.config/}}

Replace username with your username and usergroup with your group (by default, in Ubuntu your usergroup is the same as your username). Everything should be OK now!

===Problem: Virtual terminals not working===

One problem I had after installing the ATI drivers was that virtual terminals stopped working. Instead of seeing a console when pressing CTRL+ALT+F1...F6 I was seeing a yellow/orange garbled output. Luckily, solving this with ATI drivers is trivial. Open a terminal, and type:

: {{cmduser|sudo gedit /boot/grub/menu.lst}}

Find the line which says

<pre>#defoptions=quiet splash</pre>

and replace it with

<pre>#defoptions=quiet splash vga=791</pre>

Now, find the line which boots the kernel you are currently using, this is just under '## ## End Default Options ##. In the 'kernel' line, add:

<pre>vga=791</pre>

Before:

<pre>kernel /vmlinuz-2.6.17-10-generic root=/dev/sda7 ro quiet splash</pre>

After:

<pre>kernel /vmlinuz-2.6.17-10-generic root=/dev/sda7 ro quiet splash vga=791</pre>

Now save and exit the file, and reboot. Virtual terminals should now work. If you use Intel drivers, you're going to have to bite the bullet and remove the 'splash' keyword from both the defoptions and kernel lines. You'll lose the pretty bootup screen, but at least virtual terminals will work, which are important to recover a crashed system.

===Problem: Microphone doesn't work===

Initially, the microphone didn't work, which appears to be linked to the a missing file /etc/asound.names. Executing

sudo alsactl names
sudo alsactl store

to generate /etc/asound.names and /var/lib/alsa/asound.state seems to fix sound problems.

(the original fix is on http://ubuntuforums.org/showthread.php?t=272166)

===Problem: I keep logging out!===

If you're using Beryl, and find that you keep getting logged out, you've just encountered one of Beryl's most annoying bugs. Shift+Backspace causes a logout. To fix this, open a terminal and type:

: {{cmduser|gedit /home/username/annoymenot.sh}}

Remember to replace 'username' with your username. Now, in this file type:

: {{cmduser|xmodmap -e "keycode 22 <nowiki>=</nowiki> BackSpace BackSpace Terminate_Server" }}

Save and close the file, and make it executable:

: {{cmduser|chmod 755 /home/username/annoymenot.sh}}

Now go to System - Preferences - Session, Startup Programs. Click add, and type

: {{cmduser|/home/username/annoymenot.sh}}

Logout and back in, problem solved! While you're at it, how about getting the start button to work? Go to System - Preferences - Keyboard - Layout Options - Alt/Win Key behaviour and select 'Super is mapped to Win keys (default)'.

===Desktop envy===

We're living in an age of desktop prettyness, and Linux can be just as pretty as MAC OS X or Vista. You've already got Beryl installed. Now go to Applications - Accesories - gDesklets. If the gDesklets entry is not there, make sure you install it, either using Synaptic or Automatix. Desklets are small programs you can add to your desktop, ala OS X's Deskbar or Vista's Sidebar. To make them start on boot, add gdesklets in System - Preferences - Sessions, Startup Programs.

Another cool program is cairo clock. Download it from http://macslow.thepimp.net/projects/cairo-clock/cairo-clock_0.3.2-1_i386.deb and install it by double-clicking. To make it start automatically, add it to your sessions as mentioned above. I've found the following command makes it work best for me:

<pre>cairo-clock -s -w 175 -g 175 -x 1219 -y 7 -t radium</pre>

Finally, make sure you click that Ruby icon in your notification area, it allows you to configure Beryl to do all sorts of cool stuff!

===Conclusion===

Well, that's about it! A dream Linux system on a dream laptop! Check out these cool technologies for an even better system:

* Beagle
* Tomboy
* Deskbar

===References===

* ATI on Ubuntu - https://help.ubuntu.com/community/BinaryDriverHowto/ATI
* Garbled Virtual Terminal Bug - https://launchpad.net/distros/ubuntu/+source/usplash/+bug/63558
* Beryl logout Bug - http://forum.beryl-project.org/viewtopic.php?p=1295&sid=6feedd09a7f01bca68feb05a5f2f033c
* Beryl Netbeans Bug - http://ubuntuforums.org/showthread.php?t=252594
* Beryl on Ubuntu - http://wiki.beryl-project.org/index.php/Install/Ubuntu/Edgy/XGL
* Home directory permissions bug - http://www.ubuntuforums.org/showthread.php?p=1789997
* gnome-bluetooth bug - https://launchpad.net/distros/ubuntu/+source/gnome-bluetooth/+bug/70718
* Atheros network cards on Ubuntu - http://ubuntuforums.org/showthread.php?t=38972

Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60

2006-12-24T18:51:50Z

Ischg:

Created by: [[User:Keithvassallo|Keithvassallo]] 14:39, 16 December 2006 (CET)

Thanks for valuable contributions by:

: [[User:Ischg|Ischg]]
: [[User:Soon|Soon]]

===Abstract===

This article describes how to get Ubuntu Linux 6.10 (Edgy) installed on an IBM/Lenovo ThinkPad T60. It's not meant to be a definite guide to installing Ubuntu (the Ubuntu Guide at http://www.ubuntuguide.org does a very good job of that). This article is meant to describe how to get most of the ThinkPad features working on Ubuntu system. It also discusses how to get Multimedia, some cool-looking effects such as Beryl, gDesklets and similar working on Ubuntu. Finally, we discuss some common problems encountered on Ubuntu and ThinkPads alike.

{{NOTE|I am in no means an expert, the methods described here are those which got everything to work for me - your mileage may vary. A big thank you to all ThinkWiki users who keep contributing on improving this article.}}

===My ThinkPad===

Although this guide should work on most recent ThinkPads, I cannot guarantee that. These are the specifications of my machine. The closer your specs are, the greater the chance of success.

: Figure 1. ThinkPad T60 2007, complete with Tux sticker :-)
: [[Image:thinkpad.jpg]]

* Lenovo ThinkPad T60 2007.
* Intel Centrino Duo T2400 / 1.83 GHz.
* Mobile Intel 945PM Express Chipset.
* Intel Wireless LAN.
* Integrated Bluetooth.
* ATI Mobility Radeon X1400 - PCI Express x16, 128MB dedicated RAM.
* 100 GB - Serial ATA-150 Hard Drive.
* 15' TFT Active Matrix Display (1400x1050).

That's basically all you need to know. As far as I know, all other features are common to all ThinkPads manufactured by Lenovo since they acquired IBM's computer business.

===Why Ubuntu? (or rather, Why not SUSE?)===

In June 2006, Lenovo announced it would be shipping ThinkPad T60p laptops with SUSE Linux Enterprise Desktop (SLED) 10 pre-installed, since SLED apparently supports all of the features of the T60p. I contacted my local IBM supplier, who said that Lenovo were no longer manufacturing the T60p, since the company which was making the displays went out of business. This meant I could not get a T60p with SLED pre-installed. I decided to go for the T60 2007, which is the closest thing I could find to the T60p. This comes with Windows XP Professional pre-installed.

I first tried to get SLED installed on the T60. Although it did indeed install, and most features worked, I soon got bored of SLED. Firstly, SLED uses Gnome 2.12, which is by now ancient. Secondly, although the Lenovo utilities do work on SLED, they only work well if you use KDE as your defauly desktop environment, which is a pity since I'm a Gnome user. The utilities were very unstable to me too. Finally, what made me give up SLED was the usual problem - it's an RPM based distribution. Once you start using Debian derivatives, with their apt based installer, you won't want to go back. That's when I decided to try Ubuntu, and have not regretted it since.

===What Works?===

* Ubuntu and all programs it comes with.
* Most of the function keys, except the ones mentioned below
* The fingerprint reader.
* The ATI proprietary graphics drivers.
* Suspend to RAM (Sleep) and Suspend to Disk (Hibernate).
* Brightness, Volume and Mute with OSD (On-Screen Display).
* ThinkLight, TrackPoint II and the touchpad.

===What Doesn't Work? (Known Issues)===

* FN+F8, FN+F9, FN+ZOOM.
* The BACK and FORWARD buttons (next to the cursor keys).
* The ThinkVantage button (in Linux, still works on boot).
* Sending files to Bluetooth devices via GUI.

There are probably ways and means to get the offending buttons to work, I've tried several fora but none seem to address my exact problem. I'll update this article should I find out anything.

===First Things First - Creating a Windows Recovery Disc===

If you've purchased a T60, chances are it came with Windows XP Professional. The other option is for you to have FreeDOS installed, in which case you can skip this section. You could remove the Windows partition altogether, and reserve your ThinkPad for Linux, but that's not the route I've chosen. The ThinkVantage utilities in Windows allow you to do a lot of cool things, such as set-up a boot-up fingerprint security scan. You can't do this from Linux (as far as I know) so it's best to leave the Windows partition in place. So, boot your ThinkPad and complete the Windows XP setup (which asks you to add a user account and enroll yourself using the ThinkVantage Client Security Solution). While you're there, use the ThinkVantage productivy centre to enroll your fingerprint (I suggest enrolling more than one) and make sure you check the option to require a fingerprint scan on boot (not for security, for geek points). When you reboot, press ESC or F2 to get to BIOS, and make sure you check the option to require a supervisor password. This will make your ThinkPad prompt you for your fingerprint when you power it up.

: Figure 2. Configuring fingerprint security from Windows
: [[Image:winprint.jpg]]

Now that's working, you should create a recovery DVD using the ThinkVantage recovery utilities. This will allow you to recover your Windows installation should you manage to screw your partitions up in the following stages. I highly recommend you do this, as Lenovo does not provide Windows XP CDs with this Laptop - so the hard disk partition is all you've got. Once this is done, we're ready to install Ubuntu!

: Figure 3. Creating recovery discs from Windows
: [[Image:recovery.jpg]]

===Getting Ubuntu installed===

Download the latest Edgy live CD from the Ubuntu website, you can find a list of mirrors at http://www.ubuntu.com/products/GetUbuntu/download#currentrelease. You may also try Kubuntu, Edubuntu or any of it's derivatives, but I'll stick with Ubuntu here for simplicity's sake. Once that's downloaded, burn the ISO to disc using any program of your choice (If this is your first Linux experience and you're using Windows, try using Nero - http://www.nero.com).

Once the burning process is complete, reboot your machine ensuring that the Ubuntu CD is in the drive. You should see an Ubuntu menu. If you don't, your BIOS is not set to boot from CD. Reboot your ThinkPad and change the boot order from BIOS (by default ThinkPads boot from CD-ROM before the hard disk, so this is probably not necessary). Once the menu shows up, select 'Start or install Ubuntu' and let it boot. This will take a while as everything is loaded from CD. You should eventually end up in a Gnome desktop. If you see an error about the Gnome Settings Daemon not being able to load, simply ignore it, as this is not necessary for now. For the purposes of the installation, it's best if you have a wired ethernet connection, as it's unlikely the wireless network card will work until we boot into our installed Ubuntu system.

: Figure 4. Select the first option to start Ubuntu
: [[Image:boot.jpg]]

Double-Click on the 'install' icon on the Desktop to start installation. The installation should be pretty straight-forward. If you need additional help, check out the walk-through with screen-shots at http://www.debianadmin.com/ubuntu-edgy-eft-desktop-installation-with-screenshots.html. The only stage at which we need to make changes is the partitioning stage. This to make sure we preserve our Windows partition, and the IBM vendor_diag partition which allows recovery of the laptop when things go hay-wire. In the 'Prepare disk space' section of the installer, select the third option, 'Manually edit partition table'. A bar will be displayed showing your existing partitions. If you have Windows installed you will see two partitions. The first is a 4.89 GB IBM Vendor Diagnostic partition, which we do not want to touch. The second will be your Windows partition, which will fill the rest of the disk. Click on this partition, Then click the 'Resize/Move' button. I resized my Windows partition to 24 GB. This is enough to accommodate the 10 GB already in use on that partition, as well as giving Windows another 14 GB of free space. 6 GB of free space would probably be enough though.

Now it's time to create partitions for Linux. You need at least two partitions; a swap partition which should be roughly double the amount of RAM you have, and a root partition to install Linux. I opted for four partitions, as follows:

<table border=1>
<tr><td>'''Purpose'''</td><td>'''Size'''</td><td>'''File-System'''</td></tr>
<tr><td>Swap</td><td>2 GB</td><td>swap</td></tr>
<tr><td>/boot</td><td>5 GB</td><td>ext3</td></tr>
<tr><td>/ (root)</td><td>20 GB</td><td>ext3</td></tr>
<tr><td>/home</td><td>37.25 GB (what's left of the disk)</td><td>ext3</td></tr>
</table>

To create these paritions, click on the 'New' button and select 'Extended Partition' in the 'create as' drop-down list. Leave all other settings as-is, and click 'Add'. Now, click on the newly created partition, and create each of the partitions you want to create, simply specify the size of the partition in the 'New Size (MiB)' text box. To convert GB to MiB, multiply by 1024. So for your swap partition you should specify a size of 2048. Repeat until you have created all the required partitions. If you follow my parition layout, the partition editor should look something like Figure 5.

: Figure 5. Our partitions, ready to be created
: [[Image:partitioning.jpg]]

You will not see mount-points in your diagram, because the screen-shot above was taken after they were assigned, but you should get the general idea. After this screen, you will be asked to assign mount-points to the partitions you have just created. If you created the partitions in the same order I did, you can assign mount points as I have (i.e. /dev/sda5 for swap, /dev/sda6 for /boot, /dev/sda7 for /, /dev/sda8 for /home). Additionally, I mounted my Windows partition as /media/sda1 and my IBM Vendor Diagnostic partition as /media/sda2. These are optional. After this step, continue installation as normal. When the installation is complete, click the 'reboot' button to restart into your fresh Ubuntu System.

When booting, the GRUB boot-loader will be displayed, asking you what you want to load. You will probably see four options. The first two being Ubuntu Linux and Ubuntu Linux recovery mode (showing the kernel version). The other two will be Microsoft Windows XP, and 'Other Windows XP/2000/NT' partition. This is your IBM Vendor Diagnostic partition, which is based on the Windows kernel, apparently. Select the first entry to boot Ubuntu. The next time you boot Windows, it will bring up a chkdsk screen. This is entirely normal and happens because we have resized the Windows partition. Make sure you do not skip this check and let it complete.

===Wireless LAN===

{{WARN|Another ThinkWiki user notes that not all T60s come with the Intel wireless chip. If you are not entirely sure what wireless NIC you use, please read the following section (Non-Intel Network Cards).}}

The first thing we should do is to get wireless networking working. Luckily, getting the Centrino wireless LAN chip working in Ubuntu is quite easy, if you use the gnome-network-manager applet. Just go to System - Administration - Synaptic Package Manager. Then click 'Search' and set the 'look-in' field to 'name'. In the 'Search' text box type:

<pre>network-manager</pre>

: Figure 6. Installing the network manager applet
: [[Image:networkmanager.jpg]]

Click on the box beside 'network-manager' and click 'Mark for installation'. Do the same for 'network-manager-gnome'. Once installed, reboot your ThinkPad. An applet will show up in the gnome notification area. Click on it, and a list of detected wireless networks will be displayed. Simply click on one of them, enter any authentication details necessary, and you'll be connected to the wireless network.

: Figure 7. gnome-network-manager showing available wireless networks
: [[Image:available-accesspoints.jpg]]

===Non-Intel Network Cards===

Not all versions of the T60 have the Intel Wireless LAN as described above. Run the following command to see details about detected wireless cards:

: {{cmduser| lspci}}

Look for a line which shows detected network cards. Users of Intel network cards will see something similar to the following output:

<pre>03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)</pre>

If you see the above, you can jump to the next section. If you do not see the above, your network card is not Intel. You may see something similar to:

<pre>03:00.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)</pre>

If that's the output you get, you're going to have to take some additional steps to get wireless networking working. Read more at http://ubuntuforums.org/showthread.php?t=38972

running:

: {{cmdroot| dmesg <nowiki>|</nowiki> grep hal}}

may yield output like this:

<pre>
[17179590.420000] ath_hal: module license 'Proprietary' taints kernel.
[17179590.424000] ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
</pre>

Which suggests the hardware abstraction layer is in place.

If not, or if the output contains "HAL Status 13" it suggests your card is not supported by the current drivers, and you need to upgrade.

===Installing the ATI display drivers===

If your ThinkPad has an Intel graphics adapter, you should skip this section as Ubuntu installs the best driver automatically. Ubuntu does not install the ATI proprietary drivers by default because they are, er, proprietary. Luckily, installing them is easy enough. Open a terminal (Applications - Accessories - Terminal) and type the following:

: {{cmduser| sudo apt-get update}}
: {{cmduser| sudo apt-get install xorg-driver-fglrx fglrx-control}}

Now we make sure the proprietary driver is not disabled by the kernel. Type the following, and remove any lines referring to fglrx

: {{cmduser|sudo gedit /etc/default/linux-restricted-modules-common}}

An alternative to gedit (Gnome) is nano (sudo nano -w /etc...) for a CLI editor.

Finally, we need to configure the X server to use the ATI drivers. Type the following:

: {{cmduser|sudo depmod -a}}
: {{cmduser|sudo aticonfig --initial}}
: {{cmduser|sudo aticonfig --overlay-type<nowiki>=</nowiki>Xv}}

One last thing. In order to correct a very common problem of getting a jerky video display, type the following:

: {{cmduser|sudo gedit /etc/X11/xorg.conf}}

Scroll to the end of the file, and add the text below.

<pre>
Section "Extensions"
Option "Composite" "0"
EndSection
</pre>

Save the file and exit. Now, to apply the changes either press CTRL+ALT+Backspace or reboot. The resolution should have switched to 1400x1050 and everything should look prettier and render faster. Just to make sure everything is working, open up a terminal and type

: {{cmduser|fglrxinfo}}

This should display:

<pre>
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Mobility Radeon X1400 Generic
OpenGL version string: 2.0.6011 (8.28.8)
</pre>

The above is what I get on my ThinkPad, and you should see something similar. As long as you see your graphics card model listed, everything should be OK. If, instead, you see a bunch of lines containing 'Mesa' then you have a problem. In that case, I recommend consulting https://help.ubuntu.com/community/BinaryDriverHowto/ATI and the Ubuntu forums at http://ubuntuforums.org

===The Fingerprint Reader===

Although IBM does not officially support it, the fingerprint reader does in fact work with most Linux distributions. Getting it to work with Ubuntu can be a bit of a pain, but it does work. Basically, a bioAPI plugin is provided for PAM. PAM-aware applications such as GDM and gnome-screensaver will then automatically use the fingerprint reader, which is uber cool. Anyway, enough theory, I've probably lost the newbies amongst you already. Go to http://www.qrivy.net/~michael/temp/ and download the latest bioapi package (at the time of writing, bioapi_1.2.3_i386.deb). When asked, tell Firefox to open the file with the GDebi package installer.

That will install bioAPI. What we need now is the driver for our fingerprint device, which is manufactured by UPEK. Go to http://www.upek.com/support/dl_linux_bsp.asp and download the latest version, currently UPEK_BSP_LIN_1.0.zip. Extract this file, then open a terminal (and don't close it until I say so).

: {{cmduser|cd /path/to/where/you/extracted/the/file}}
: {{cmduser|sudo bash}}
: {{cmdroot|sh install.sh /usr/lib}}

Now we need to assign the right permissions so non-root applications can use the driver:

: {{cmdroot|addgroup --system bioapi}}
: {{cmdroot|addgroup --system usbfs}}
: {{cmdroot|adduser yourusername bioapi}}
: {{cmdroot|adduser yourusername usbfs}}
: {{cmdroot|chown -R root:bioapi /usr/var/bioapi/}}
: {{cmdroot|chmod -R 770 /usr/var/bioapi/}}
: {{cmdroot|chown -R root:usbfs /proc/bus/usb}}
: {{cmdroot|chmod -R g+X /proc/bus/usb}}

Of course, replace 'yourusername' with the username you use to login. Now, we need to set the usb file system (usbfs) to be usable by users in the usbfs group. To do this, we need to determine the group ID of the usbfs group. Type the following:

: {{cmdroot|cat /etc/group <nowiki>|</nowiki> grep usbfs <nowiki>|</nowiki> cut -d':' -f 3}}

In my case the number is 116, it might be different for you. Now, open the file /etc/fstab:

: {{cmdroot|gedit /etc/fstab}}

and type the following:

<pre>none /proc/bus/usb usbfs defaults,devgid=116,devmode=0660,busgid=116,busmode=0770,listgid=116,listmode=0660 0 0</pre>

Please type the above code in one line in your file. Remember to replace 116 if you got a different number with the previous cat command. The last permission-related thing we need to fool around with is UDEV. Open the udev permissions file

: {{cmdroot|gedit /etc/udev/rules.d/40-permissions.rules}}

and find the line:

<pre>SUBSYSTEM=="usb_device", MODE="0664"</pre>

It's line 65 in my file. Change it so it looks like this:

<pre>SUBSYSTEM=="usb_device", MODE="0660", GROUP="usbfs"</pre>

Now we need to enroll our fingerprint with the system. To do this, we need a utility called Sample, which is only distributed in source-code form with the driver. This is great, only I couldn't get it to compile on Ubuntu. Luckily, there is a binary version available from one of the earlier releases of the driver (beta 2). To get this, download it from ftp://linux:Tuc-nak3@delta.upek.com/TFMESS_BSP_LIN_1.0beta2.zip. Now, extract the file and type:

: {{cmdroot|cd /path/to/where/you/extracted/the/archive}}
: {{cmdroot|cd NonGUI_sample}}
: {{cmdroot|chmod a+x Sample}}
: {{cmdroot|./Sample}}

Press (e) to enroll a new user, and enter your username when asked for the user ID. You will be asked to swipe your finger three times. Now press (v) and swipe your finger, a green check should be displayed showing you have successfully authenticated.

: Figure 8. The fingerprint swipe prompt
: [[Image:touchchip.jpg]]

Wonderful! Now, quit the application (q) and type exit to become a normal user. A file called yourusername.bir should have been created, copy this to your home directory:

: {{cmdroot|cp yourusername.bir /home/yourusername/}}

You can now close the terminal window. The next step is to install the BioAPI plug-in for PAM, and to make applications use the plugin. So, get the pam_bioapi plugin from http://www.nax.cz/pub/bioapi/pam_bioapi/pam-bioapi_0.3.0.tar.gz and extract it. Now open a terminal and type:

Comment: you will have to install some libraries in order to be able to compile the plugin

: {{cmduser|sudo apt-get install build-essential}}
: {{cmduser|sudo apt-get install libpam0g-dev}}

Now, you can compile and install the plugin

: {{cmduser|cd /path/to/where/you/extracted/the/arcive}}
: {{cmduser|./configure --libdir<nowiki>=</nowiki>/lib --enable-file-store && make}}
: {{cmduser|sudo make install}}

That's installed the plugin. Now, open a terminal and type the following:

: {{cmduser|cd ~}}
: {{cmduser|sudo bash}}

This will open a root session. Please do not close this until instructed. Now, paste the following scary command:

<pre>
SERIAL=`BioAPITest | sed -ne "/Fingerprint/{n;n;s/^.*: $.\{9\}$$.\{4\}$$.\{4\}$$.\{4\}$$.*$/\1-\2-\3-\4-\5/gp}"`
</pre>

Type the following to register your username and serial with the bioAPI.

: {{cmdroot|mkdir -p /etc/bioapi/pam/$SERIAL}}
: {{cmdroot|cp yourusername.bir /etc/bioapi/pam/$SERIAL}}
: {{cmdroot|exit}}

Phew. Now, to make applications actually use the fingerprint reader. Open a terminal window, and type:

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

Delete everything in the file, and paste this instead:

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

Save and close the file. That will make all PAM-aware applications use the fingerprint reader. Unfortunately, this also includes sudo. Since sudo is a command line application, it will display prompts in a terminal for you to swipe your finger, which is all well and good. The problem with this is that many Ubuntu administrative applications (such as Synaptic) use gksu to present a graphical front-end to sudo, which will output messages on the command line which you'll never see. Result? Administrative programs won't work from the gnome menu. The solution is to make sudo use the good old password. Open a terminal and type:

: {{cmduser|sudo gedit /etc/pam.d/sudo}}

Delete everything in the file, and instead paste:

<pre>
#%PAM-1.0

#@include common-auth
auth required pam_unix.so nullok_secure
@include common-account
</pre>

Now, save the file and close it, and reboot your system. GDM will ask you for a username, and then show a pretty prompt where you can scan your fingerprint! Same goes for gnome-screensaver when you set it to lock. Sometimes gnome-screensaver will not display the prompt, but you should still swipe your finger and be able to log back in.

===Bluetooth with Mobile Phones/PDAs===

Rather strangely, Ubuntu seems to have taken a step backwards with Bluetooth useability in Edgy. What worked out of the box with Dapper, now requires configuratio. First, open System - Preferences - Sessions and go to the Startup Programs tab. Then, find the entry labelled 'bt-applet --sm-disable'. Highlight it and click disable. Click add and in the command field type 'bt-applet'. Repeat this process, adding an entry for 'gnome-obex-server'. Now, open Synaptic Package Manager (System - Administration - Synaptic Package Manager) and click Search. Type 'gnome-bluetooth' to find the package, then mark it for installation. Now repeat this process for 'bluez-passkey-gnome'. Click apply to make changes.

Now that everything is installed, log-out of Gnome and log back in again. From your phone/PDA, search for devices untill you see your ThinkPad (the hostname will be displayed). Pair with the device. When asked for a passkey, enter 1234, which is the default. If you want to change your passkey (and you should), open a terminal and type:

: {{cmduser|sudo gedit /etc/bluetooth/hcid.conf}}

Find the line which says 'Default PIN for incoming connections' and change the PIN on the line beneath it:

<pre>
# Default PIN code for incoming connections
passkey "4017";
</pre>

Save and close the file, then type:

: {{cmduser|sudo /etc/init.d/bluetooth restart}}

You will now be able to use your new PIN code. To send files from your device to the ThinkPad, simply select the file you want to send and click Send Via Bluetooth (or whatever option your device presents). A dialog will pop-up in Gnome showing you a new file has been received.

: Figure 9. Gnome informing us that a file has been received
: [[Image:bluetooth.jpg]]

Sending files from your ThinkPad to your device requires more effort. The way it should work is that you right-click on a file, click send to, then make sure 'Bluetooth (OBEX)' is selected. Your device should be displayed and you could just click send. Unfortunately, due to a bug in gnome-bluetooth (described in https://launchpad.net/distros/ubuntu/+source/gnome-bluetooth/+bug/70718) this method does not work. If it does work for you, the bug has been solved and you can skip the rest of this section.

Your only other option is to use the command line to send files to your device. Open a terminal, then type:

: {{cmduser|hcitool scan}}

A list of detected bluetooth devices will be shown, for example, my output shows the following:

<pre>
Scanning ...
00:09:DD:60:02:EB Photosmart 8100 series
00:14:A7:99:3C:1F ThElInK
</pre>

The first field is the MAC address of the device, the second is the name of the device. In this case my bluetooth printer and mobile phone (ThElInK) were detected. In order to send files to my phone, I use:

: {{cmduser|gnome-obex-send -d 00:14:A7:99:3C:1F myPicture.jpg}}

Replace the MAC address with that of your device and myPicture.jpg with the file you want to send.

===TrackPoint Scrolling===

By default you can use the right and bottom edges of your touchpad to scroll through documents. If you use the TrackPoint instad of the touchpad (and believe me, you should), you'll find that scrolling is disabled by default. To enable it, open a terminal and type:

: {{cmduser|sudo gedit /etc/X11/xorg.conf}}

Now find the entry for your TrackPoint device. In my configuration file, the TrackPoint entry is the first mouse entry, after the keyboard entry, and looks something like this:

<pre>
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection
</pre>

Right after this entry is my touchpad entry. My entry is on line 66, but yours may be different. Now, add the follwing two options in that InputDevice section:

<pre>
Option "EmulateWheel" "on"
Option "EmulateWheelButton" "2"
</pre>

Save and exit the file. Restart your ThinkPad (or logout, and press CTRL-ALT-BACKSPACE). You should now be able to scoll by holding down the middle button for your TrackPoint and using the TrackPoint to scroll.

===Getting Multimedia to Work===

Due to patents and similar legal crap, Ubuntu will not play most media files by default. You also won't get browser plugins for multimedia. Luckily, this is easily fixed. Open a terminal and type the following:

: {{cmduser|sudo cp /etc/apt/sources.list /etc/apt/sources.list.backup}}
: {{cmduser|sudo gedit /etc/apt/sources.list}}

Delete everything in the file, and instead paste the following:

<pre>
deb-src http://archive.ubuntu.com/ubuntu edgy main restricted universe multiverse
#deb http://archive.ubuntu.com/ubuntu edgy-proposed main restricted universe multiverse

## MAJOR BUG FIX UPDATES produced after the final release
deb-src http://archive.ubuntu.com/ubuntu edgy-updates main restricted universe multiverse

## UBUNTU SECURITY UPDATES
deb http://security.ubuntu.com/ubuntu edgy-security main restricted universe multiverse
deb-src http://security.ubuntu.com/ubuntu edgy-security main restricted universe multiverse

## BACKPORTS REPOSITORY (Unsupported. May contain illegal packages. Use at own risk.)
#deb http://archive.ubuntu.com/ubuntu edgy-backports main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu edgy-backports main restricted universe multiverse

## PLF REPOSITORY
deb http://packages.freecontrib.org/ubuntu/plf edgy-plf free
deb-src http://packages.freecontrib.org/ubuntu/plf edgy-plf free
deb http://packages.freecontrib.org/ubuntu/plf edgy-plf non-free
deb-src http://packages.freecontrib.org/ubuntu/plf edgy-plf non-free

## CANONICAL COMMERCIAL REPOSITORY (Hosted on Canonical servers, not Ubuntu
## servers. RealPlayer10, Opera, DesktopSecure and more to come.)
deb http://archive.canonical.com/ubuntu edgy-commercial main

## Listen
#deb http://theli.free.fr/packages/ edgy listen

## Automatix repo
deb http://www.getautomatix.com/apt edgy main
</pre>

Now, open a terminal and type the following:

: {{cmduser|wget <nowiki>http://packages.freecontrib.org/ubuntu/plf/12B83718.gpg</nowiki> -O- <nowiki>|</nowiki> sudo apt-key add -}}
: {{cmduser|wget <nowiki>http://www.getautomatix.com/apt/key.gpg.asc</nowiki>}}
: {{cmduser|gpg --import key.gpg.asc}}
: {{cmduser|gpg --export --armor 521A9C7C <nowiki>|</nowiki> sudo apt-key add -}}
: {{cmduser|sudo apt-get update}}
: {{cmduser|sudo apt-get install automatix2}}
: {{cmduser|wget <nowiki>http://easyubuntu.freecontrib.org/files/easyubuntu-3.023.tar.gz</nowiki>}}
: {{cmduser|tar -zxf easyubuntu-3.023.tar.gz}}
: {{cmduser|cd easyubuntu}}
: {{cmduser|cp packagelist-dapper.pot packagelist-edgy.pot}}
: {{cmduser|cp packagelist-dapper.xml packagelist-edgy.xml}}
: {{cmduser|sudo python easyubuntu.in}}

Don't worry if you get errors from the Ubuntu PLF repository. PLF mirrors are about as stable as wild bull in a farm full of cows. Select what you want to install from the resulting window. Make sure you do not select the totem-mozilla plugin, as this just doens't work, for me at least. When EasyUbuntu has finished installing packages, you should be returned to a terminal, which you can close. Now go to Applications - System Tools - Automatix. Read and agree to the warning. Check what you want to install. Make sure you check 'Mplayer and FF plugin'. When ready, click the 'install' button. That should get multimedia working nicely.

: Figure 10. The Automatix user interface
: [[Image:automatix.jpg]]

===Beryl - fancy 3D desktop===

MAC OS X has Aqua and Windows Vista has Aero. Well, Linux has XGL/Beryl which can get effects which are as good looking (or sometimes better!) than the former two. Installing Beryl on Ubuntu is not that hard. First, open a terminal and type the following:

: {{cmduser|sudo gedit /etc/apt/sources.list}}

At the end of the file, append the following:

<pre>
##Beryl
deb http://ubuntu.beryl-project.org/ edgy main
</pre>

Save and close the file. Now type:

: {{cmduser|wget <nowiki>http://beryl-mirror.lupine.me.uk/1609B551.gpg</nowiki> -O- <nowiki>|</nowiki> sudo apt-key add -}}
: {{cmduser|sudo apt-get update}}

ATI Users Only: type

: {{cmduser|sudo apt-get install xserver-xgl}}

Now, to install beryl:

: {{cmduser|sudo apt-get install beryl emerald-themes}}

To make Ubuntu use the 3D effects. Open a terminal:

: {{cmduser|sudo gedit /usr/local/bin/startxgl.sh}}

In that file, paste the following if you use an ATI card:

<pre>
#!/bin/sh
Xgl -fullscreen :1 -ac -br -accel glx:pbuffer -accel xv:pbuffer &
sleep 4
export DISPLAY=:1
exec gnome-session
</pre>

If you use an Intel card, paste the following instead:

<pre>
#!/bin/sh
beryl-manager
sleep 4
exec gnome-session
</pre>

Save the file and close. Now we need to make the file executable:

: {{cmduser|sudo chmod a+x /usr/local/bin/startxgl.sh}}

All that's left now is to create a login script which makes gnome use the 3D effects. In a terminal, type:

: {{cmduser|sudo gedit /usr/share/xsessions/xgl.desktop}}

Now, in this file paste:

<pre>
[Desktop Entry]
Encoding=UTF-8
Name=Xgl
Exec=/usr/local/bin/startxgl.sh
Icon=
Type=Application
</pre>

Save and close the file. Now type:

: {{cmduser|sudo gedit /usr/local/bin/start_beryl.sh}}

In this file, paste:

<pre>
#!/bin/bash
#
# Start beryl-manager within gnome-session
#
if [ `ps -A -o comm | grep -c '^Xgl$'` == "1" ]; then
DISPLAY=:1 beryl-manager
DISPLAY=:1 beryl-xgl
else echo "${0}: Error: beryl-manager not launched. Xgl not running?"
fi
</pre>

Now make the file executable:

: {{cmduser|sudo chmod a+x /usr/local/bin/start_beryl.sh}}

Now go to System - Preferences - Sessions, go to the Startup Programs tab, and click add, then type

: {{cmduser|/usr/local/bin/start_beryl.sh}}

Now, reboot your ThinkPad. When you come to the login screen, click the 'Sessions' button on the bottom left corner, and select XGL. login, et voila! beautiful 3D effects!

: Figure 11. Beryl's Cube effect
: [[Image:cube.jpg]]

If you have NetBeans installed, try launching it now. It probably won't work due to Beryl. Luckily, this is easily solved. Open a terminal and type:

: {{cmduser|sudo gedit /etc/environment}}

Then add the following line to the end of the file.

<pre>AWT_TOOLKIT="MToolkit"</pre>

Now save, close and reboot. Netbeans should now work!

===Problem: Can't add programs to session===

So you tried to add something to your startup programs, it shows up in the list, but it doesn't start up. You then launch the sessions program again, only to find your program has disappeared from the list. This problem is being caused by incorrect permissions in your home directory, and can happen on some occasions. To fix it, open a terminal and type the following:

: {{cmduser|sudo chown -R username:usergroup /home/username/.config/}}

Replace username with your username and usergroup with your group (by default, in Ubuntu your usergroup is the same as your username). Everything should be OK now!

===Problem: Virtual terminals not working===

One problem I had after installing the ATI drivers was that virtual terminals stopped working. Instead of seeing a console when pressing CTRL+ALT+F1...F6 I was seeing a yellow/orange garbled output. Luckily, solving this with ATI drivers is trivial. Open a terminal, and type:

: {{cmduser|sudo gedit /boot/grub/menu.lst}}

Find the line which says

<pre>#defoptions=quiet splash</pre>

and replace it with

<pre>#defoptions=quiet splash vga=791</pre>

Now, find the line which boots the kernel you are currently using, this is just under '## ## End Default Options ##. In the 'kernel' line, add:

<pre>vga=791</pre>

Before:

<pre>kernel /vmlinuz-2.6.17-10-generic root=/dev/sda7 ro quiet splash</pre>

After:

<pre>kernel /vmlinuz-2.6.17-10-generic root=/dev/sda7 ro quiet splash vga=791</pre>

Now save and exit the file, and reboot. Virtual terminals should now work. If you use Intel drivers, you're going to have to bite the bullet and remove the 'splash' keyword from both the defoptions and kernel lines. You'll lose the pretty bootup screen, but at least virtual terminals will work, which are important to recover a crashed system.

===Problem: Microphone doesn't work===

===Problem: I keep logging out!===

If you're using Beryl, and find that you keep getting logged out, you've just encountered one of Beryl's most annoying bugs. Shift+Backspace causes a logout. To fix this, open a terminal and type:

: {{cmduser|gedit /home/username/annoymenot.sh}}

Remember to replace 'username' with your username. Now, in this file type:

: {{cmduser|xmodmap -e "keycode 22 <nowiki>=</nowiki> BackSpace BackSpace Terminate_Server" }}

Save and close the file, and make it executable:

: {{cmduser|chmod 755 /home/username/annoymenot.sh}}

Now go to System - Preferences - Session, Startup Programs. Click add, and type

: {{cmduser|/home/username/annoymenot.sh}}

Logout and back in, problem solved! While you're at it, how about getting the start button to work? Go to System - Preferences - Keyboard - Layout Options - Alt/Win Key behaviour and select 'Super is mapped to Win keys (default)'.

===Desktop envy===

We're living in an age of desktop prettyness, and Linux can be just as pretty as MAC OS X or Vista. You've already got Beryl installed. Now go to Applications - Accesories - gDesklets. If the gDesklets entry is not there, make sure you install it, either using Synaptic or Automatix. Desklets are small programs you can add to your desktop, ala OS X's Deskbar or Vista's Sidebar. To make them start on boot, add gdesklets in System - Preferences - Sessions, Startup Programs.

Another cool program is cairo clock. Download it from http://macslow.thepimp.net/projects/cairo-clock/cairo-clock_0.3.2-1_i386.deb and install it by double-clicking. To make it start automatically, add it to your sessions as mentioned above. I've found the following command makes it work best for me:

<pre>cairo-clock -s -w 175 -g 175 -x 1219 -y 7 -t radium</pre>

Finally, make sure you click that Ruby icon in your notification area, it allows you to configure Beryl to do all sorts of cool stuff!

===Conclusion===

Well, that's about it! A dream Linux system on a dream laptop! Check out these cool technologies for an even better system:

* Beagle
* Tomboy
* Deskbar

===References===

* ATI on Ubuntu - https://help.ubuntu.com/community/BinaryDriverHowto/ATI
* Garbled Virtual Terminal Bug - https://launchpad.net/distros/ubuntu/+source/usplash/+bug/63558
* Beryl logout Bug - http://forum.beryl-project.org/viewtopic.php?p=1295&sid=6feedd09a7f01bca68feb05a5f2f033c
* Beryl Netbeans Bug - http://ubuntuforums.org/showthread.php?t=252594
* Beryl on Ubuntu - http://wiki.beryl-project.org/index.php/Install/Ubuntu/Edgy/XGL
* Home directory permissions bug - http://www.ubuntuforums.org/showthread.php?p=1789997
* gnome-bluetooth bug - https://launchpad.net/distros/ubuntu/+source/gnome-bluetooth/+bug/70718
* Atheros network cards on Ubuntu - http://ubuntuforums.org/showthread.php?t=38972

Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60

2006-12-20T17:36:26Z

Ischg: /* Getting Multimedia to Work */

[[User:Keithvassallo|Keithvassallo]] 14:39, 16 December 2006 (CET)

===Abstract===

This article describes how to get Ubuntu Linux 6.10 (Edgy) installed on an IBM/Lenovo ThinkPad T60. It's not meant to be a definite guide to installing Ubuntu (the Ubuntu Guide at http://www.ubuntuguide.org does a very good job of that). This article is meant to describe how to get most of the ThinkPad features working on Ubuntu system. It also discusses how to get Multimedia, some cool-looking effects such as Beryl, gDesklets and similar working on Ubuntu. Finally, we discuss some common problems encountered on Ubuntu and ThinkPads alike.

===My ThinkPad===

Although this guide should work on most recent ThinkPads, I cannot guarantee that. These are the specifications of my machine. The closer your specs are, the greater the chance of success.

: Figure 1. ThinkPad T60 2007, complete with Tux sticker :-)
: [[Image:thinkpad.jpg]]

* Lenovo ThinkPad T60 2007.
* Intel Centrino Duo T2400 / 1.83 GHz.
* Mobile Intel 945PM Express Chipset.
* Intel Wireless LAN.
* Integrated Bluetooth.
* ATI Mobility Radeon X1400 - PCI Express x16, 128MB dedicated RAM.
* 100 GB - Serial ATA-150 Hard Drive.
* 15' TFT Active Matrix Display (1400x1050).

That's basically all you need to know. As far as I know, all other features are common to all ThinkPads manufactured by Lenovo since they acquired IBM's computer business.

===Why Ubuntu? (or rather, Why not SUSE?)===

In June 2006, Lenovo announced it would be shipping ThinkPad T60p laptops with SUSE Linux Enterprise Desktop (SLED) 10 pre-installed, since SLED apparently supports all of the features of the T60p. I contacted my local IBM supplier, who said that Lenovo were no longer manufacturing the T60p, since the company which was making the displays went out of business. This meant I could not get a T60p with SLED pre-installed. I decided to go for the T60 2007, which is the closest thing I could find to the T60p. This comes with Windows XP Professional pre-installed.

I first tried to get SLED installed on the T60. Although it did indeed install, and most features worked, I soon got bored of SLED. Firstly, SLED uses Gnome 2.12, which is by now ancient. Secondly, although the Lenovo utilities do work on SLED, they only work well if you use KDE as your defauly desktop environment, which is a pity since I'm a Gnome user. The utilities were very unstable to me too. Finally, what made me give up SLED was the usual problem - it's an RPM based distribution. Once you start using Debian derivatives, with their apt based installer, you won't want to go back. That's when I decided to try Ubuntu, and have not regretted it since.

===What Works?===

* Ubuntu and all programs it comes with.
* Most of the function keys, except the ones mentioned below
* The fingerprint reader.
* The ATI proprietary graphics drivers.
* Suspend to RAM (Sleep) and Suspend to Disk (Hibernate).
* Brightness, Volume and Mute with OSD (On-Screen Display).
* ThinkLight, TrackPoint II and the touchpad.

===What Doesn't Work? (Known Issues)===

* FN+F8, FN+F9, FN+ZOOM.
* The BACK and FORWARD buttons (next to the cursor keys).
* The ThinkVantage button (in Linux, still works on boot).
* Sending files to Bluetooth devices via GUI.

There are probably ways and means to get the offending buttons to work, I've tried several fora but none seem to address my exact problem. I'll update this article should I find out anything.

===First Things First - Creating a Windows Recovery Disc===

If you've purchased a T60, chances are it came with Windows XP Professional. The other option is for you to have FreeDOS installed, in which case you can skip this section. You could remove the Windows partition altogether, and reserve your ThinkPad for Linux, but that's not the route I've chosen. The ThinkVantage utilities in Windows allow you to do a lot of cool things, such as set-up a boot-up fingerprint security scan. You can't do this from Linux (as far as I know) so it's best to leave the Windows partition in place. So, boot your ThinkPad and complete the Windows XP setup (which asks you to add a user account and enroll yourself using the ThinkVantage Client Security Solution). While you're there, use the ThinkVantage productivy centre to enroll your fingerprint (I suggest enrolling more than one) and make sure you check the option to require a fingerprint scan on boot (not for security, for geek points). When you reboot, press ESC or F2 to get to BIOS, and make sure you check the option to require a supervisor password. This will make your ThinkPad prompt you for your fingerprint when you power it up.

: Figure 2. Configuring fingerprint security from Windows
: [[Image:winprint.jpg]]

Now that's working, you should create a recovery DVD using the ThinkVantage recovery utilities. This will allow you to recover your Windows installation should you manage to screw your partitions up in the following stages. I highly recommend you do this, as Lenovo does not provide Windows XP CDs with this Laptop - so the hard disk partition is all you've got. Once this is done, we're ready to install Ubuntu!

: Figure 3. Creating recovery discs from Windows
: [[Image:recovery.jpg]]

===Getting Ubuntu installed===

Download the latest Edgy live CD from the Ubuntu website, you can find a list of mirrors at http://www.ubuntu.com/products/GetUbuntu/download#currentrelease. You may also try Kubuntu, Edubuntu or any of it's derivatives, but I'll stick with Ubuntu here for simplicity's sake. Once that's downloaded, burn the ISO to disc using any program of your choice (If this is your first Linux experience and you're using Windows, try using Nero - http://www.nero.com).

Once the burning process is complete, reboot your machine ensuring that the Ubuntu CD is in the drive. You should see an Ubuntu menu. If you don't, your BIOS is not set to boot from CD. Reboot your ThinkPad and change the boot order from BIOS (by default ThinkPads boot from CD-ROM before the hard disk, so this is probably not necessary). Once the menu shows up, select 'Start or install Ubuntu' and let it boot. This will take a while as everything is loaded from CD. You should eventually end up in a Gnome desktop. If you see an error about the Gnome Settings Daemon not being able to load, simply ignore it, as this is not necessary for now. For the purposes of the installation, it's best if you have a wired ethernet connection, as it's unlikely the wireless network card will work until we boot into our installed Ubuntu system.

: Figure 4. Select the first option to start Ubuntu
: [[Image:boot.jpg]]

Double-Click on the 'install' icon on the Desktop to start installation. The installation should be pretty straight-forward. If you need additional help, check out the walk-through with screen-shots at http://www.debianadmin.com/ubuntu-edgy-eft-desktop-installation-with-screenshots.html. The only stage at which we need to make changes is the partitioning stage. This to make sure we preserve our Windows partition, and the IBM vendor_diag partition which allows recovery of the laptop when things go hay-wire. In the 'Prepare disk space' section of the installer, select the third option, 'Manually edit partition table'. A bar will be displayed showing your existing partitions. If you have Windows installed you will see two partitions. The first is a 4.89 GB IBM Vendor Diagnostic partition, which we do not want to touch. The second will be your Windows partition, which will fill the rest of the disk. Click on this partition, Then click the 'Resize/Move' button. I resized my Windows partition to 24 GB. This is enough to accommodate the 10 GB already in use on that partition, as well as giving Windows another 14 GB of free space. 6 GB of free space would probably be enough though.

Now it's time to create partitions for Linux. You need at least two partitions; a swap partition which should be roughly double the amount of RAM you have, and a root partition to install Linux. I opted for four partitions, as follows:

<table border=1>
<tr><td>'''Purpose'''</td><td>'''Size'''</td><td>'''File-System'''</td></tr>
<tr><td>Swap</td><td>2 GB</td><td>swap</td></tr>
<tr><td>/boot</td><td>5 GB</td><td>ext3</td></tr>
<tr><td>/ (root)</td><td>20 GB</td><td>ext3</td></tr>
<tr><td>/home</td><td>37.25 GB (what's left of the disk)</td><td>ext3</td></tr>
</table>

To create these paritions, click on the 'New' button and select 'Extended Partition' in the 'create as' drop-down list. Leave all other settings as-is, and click 'Add'. Now, click on the newly created partition, and create each of the partitions you want to create, simply specify the size of the partition in the 'New Size (MiB)' text box. To convert GB to MiB, multiply by 1024. So for your swap partition you should specify a size of 2048. Repeat until you have created all the required partitions. If you follow my parition layout, the partition editor should look something like Figure 5.

: Figure 5. Our partitions, ready to be created
: [[Image:partitioning.jpg]]

You will not see mount-points in your diagram, because the screen-shot above was taken after they were assigned, but you should get the general idea. After this screen, you will be asked to assign mount-points to the partitions you have just created. If you created the partitions in the same order I did, you can assign mount points as I have (i.e. /dev/sda5 for swap, /dev/sda6 for /boot, /dev/sda7 for /, /dev/sda8 for /home). Additionally, I mounted my Windows partition as /media/sda1 and my IBM Vendor Diagnostic partition as /media/sda2. These are optional. After this step, continue installation as normal. When the installation is complete, click the 'reboot' button to restart into your fresh Ubuntu System.

When booting, the GRUB boot-loader will be displayed, asking you what you want to load. You will probably see four options. The first two being Ubuntu Linux and Ubuntu Linux recovery mode (showing the kernel version). The other two will be Microsoft Windows XP, and 'Other Windows XP/2000/NT' partition. This is your IBM Vendor Diagnostic partition, which is based on the Windows kernel, apparently. Select the first entry to boot Ubuntu. The next time you boot Windows, it will bring up a chkdsk screen. This is entirely normal and happens because we have resized the Windows partition. Make sure you do not skip this check and let it complete.

===Wireless LAN===

The first thing we should do is to get wireless networking working. Luckily, getting the Centrino wireless LAN chip working in Ubuntu is quite easy, if you use the gnome-network-manager applet. Just go to System - Administration - Synaptic Package Manager. Then click 'Search' and set the 'look-in' field to 'name'. In the 'Search' text box type:

<pre>network-manager</pre>

: Figure 6. Installing the network manager applet
: [[Image:networkmanager.jpg]]

Click on the box beside 'network-manager' and click 'Mark for installation'. Do the same for 'network-manager-gnome'. Once installed, reboot your thinkpad. An applet will show up in the gnome notification area. Click on it, and a list of detected wireless networks will be displayed. Simply click on one of them, enter any authentication details necessary, and you'll be connected to the wireless network.

: Figure 7. gnome-network-manager showing available wireless networks
: [[Image:available-accesspoints.jpg]]

Note! Not all versions of the T60 has the Intel Wireless LAN as described above. Run lspci from the command line and look for details of your wifi card. E.g.:

03:00.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)

suggest you have a different wifi card. Read this forum thread http://ubuntuforums.org/showthread.php?t=38972

running:
# dmesg | grep hal

may yield output like this, which apparently suggests the hardware abstraction layer is in place.
[17179590.420000] ath_hal: module license 'Proprietary' taints kernel.
[17179590.424000] ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)

If not, or if the output contains "HAL Status 13" it apparently suggests your card is not supported by the current drivers, and you need to upgrade.

===Installing the ATI display drivers===

If your ThinkPad has an Intel graphics adapter, you should skip this section as Ubuntu installs the best driver automatically. Ubuntu does not install the ATI proprietary drivers by default because they are, er, proprietary. Luckily, installing them is easy enough. Open a terminal (Applications - Accessories - Terminal) and type the following:

: {{cmduser| sudo apt-get update}}
: {{cmduser| sudo apt-get install xorg-driver-fglrx fglrx-control}}

Now we make sure the proprietary driver is not disabled by the kernel. Type the following, and remove any lines referring to fglrx

: {{cmduser|sudo gedit /etc/default/linux-restricted-modules-common}}

An alternative to gedit (Gnome) is nano (sudo nano -w /etc...) for a CLI editor.

Finally, we need to configure the X server to use the ATI drivers. Type the following:

: {{cmduser|sudo depmod -a}}
: {{cmduser|sudo aticonfig --initial}}
: {{cmduser|sudo aticonfig --overlay-type<nowiki>=</nowiki>Xv}}

One last thing. In order to correct a very common problem of getting a jerky video display, type the following:

: {{cmduser|sudo gedit /etc/X11/xorg.conf}}

Scroll to the end of the file, and add the text below.

<pre>
Section "Extensions"
Option "Composite" "0"
EndSection
</pre>

Save the file and exit. Now, to apply the changes either press CTRL+ALT+Backspace or reboot. The resolution should have switched to 1400x1050 and everything should look prettier and render faster. Just to make sure everything is working, open up a terminal and type

: {{cmduser|fglrxinfo}}

This should display:

<pre>
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Mobility Radeon X1400 Generic
OpenGL version string: 2.0.6011 (8.28.8)
</pre>

The above is what I get on my ThinkPad, and you should see something similar. As long as you see your graphics card model listed, everything should be OK. If, instead, you see a bunch of lines containing 'Mesa' then you have a problem. In that case, I recommend consulting https://help.ubuntu.com/community/BinaryDriverHowto/ATI and the Ubuntu forums at http://ubuntuforums.org

===The fingerprint reader===

Although IBM does not officially support it, the fingerprint reader does in fact work with most Linux distributions. Getting it to work with Ubuntu can be a bit of a pain, but it does work. Basically, a bioAPI plugin is provided for PAM. PAM-aware applications such as GDM and gnome-screensaver will then automatically use the fingerprint reader, which is uber cool. Anyway, enough theory, I've probably lost the newbies amongst you already. Go to http://www.qrivy.net/~michael/temp/ and download the latest bioapi package (at the time of writing, bioapi_1.2.3_i386.deb). When asked, tell Firefox to open the file with the GDebi package installer.

That will install bioAPI. What we need now is the driver for our fingerprint device, which is manufactured by UPEK. Go to http://www.upek.com/support/dl_linux_bsp.asp and download the latest version, currently UPEK_BSP_LIN_1.0.zip. Extract this file, then open a terminal (and don't close it until I say so).

: {{cmduser|cd /path/to/where/you/extracted/the/file}}
: {{cmduser|sudo bash}}
: {{cmdroot|sh install.sh /usr/lib}}

Now we need to assign the right permissions so non-root applications can use the driver:

: {{cmdroot|addgroup --system bioapi}}
: {{cmdroot|addgroup --system usbfs}}
: {{cmdroot|adduser yourusername bioapi}}
: {{cmdroot|adduser yourusername usbfs}}
: {{cmdroot|chown -R root:bioapi /usr/var/bioapi/}}
: {{cmdroot|chmod -R 770 /usr/var/bioapi/}}
: {{cmdroot|chown -R root:usbfs /proc/bus/usb}}
: {{cmdroot|chmod -R g+X /proc/bus/usb}}

Of course, replace 'yourusername' with the username you use to login. Now, we need to set the usb file system (usbfs) to be usable by users in the usbfs group. To do this, we need to determine the group ID of the usbfs group. Type the following:

: {{cmdroot|cat /etc/group <nowiki>|</nowiki> grep usbfs <nowiki>|</nowiki> cut -d':' -f 3}}

In my case the number is 116, it might be different for you. Now, open the file /etc/fstab:

: {{cmdroot|gedit /etc/fstab}}

and type the following:

<pre>none /proc/bus/usb usbfs defaults,devgid=116,devmode=0660,busgid=116,busmode=0770,listgid=116,listmode=0660 0 0</pre>

Please type the above code in one line in your file. Remember to replace 116 if you got a different number with the previous cat command. The last permission-related thing we need to fool around with is UDEV. Open the udev permissions file

: {{cmdroot|gedit /etc/udev/rules.d/40-permissions.rules}}

and find the line:

<pre>SUBSYSTEM=="usb_device", MODE="0664"</pre>

It's line 65 in my file. Change it so it looks like this:

<pre>SUBSYSTEM=="usb_device", MODE="0660", GROUP="usbfs"</pre>

Now we need to enroll our fingerprint with the system. To do this, we need a utility called Sample, which is only distributed in source-code form with the driver. This is great, only I couldn't get it to compile on Ubuntu. Luckily, there is a binary version available from one of the earlier releases of the driver (beta 2). To get this, download it from ftp://linux:Tuc-nak3@delta.upek.com/TFMESS_BSP_LIN_1.0beta2.zip. Now, extract the file and type:

: {{cmdroot|cd /path/to/where/you/extracted/the/archive}}
: {{cmdroot|cd NonGUI_sample}}
: {{cmdroot|chmod a+x Sample}}
: {{cmdroot|./Sample}}

Press (e) to enroll a new user, and enter your username when asked for the user ID. You will be asked to swipe your finger three times. Now press (v) and swipe your finger, a green check should be displayed showing you have successfully authenticated.

: Figure 8. The fingerprint swipe prompt
: [[Image:touchchip.jpg]]

Wonderful! Now, quit the application (q) and type exit to become a normal user. A file called yourusername.bir should have been created, copy this to your home directory:

: {{cmdroot|cp yourusername.bir /home/yourusername/}}

You can now close the terminal window. The next step is to install the BioAPI plug-in for PAM, and to make applications use the plugin. So, get the pam_bioapi plugin from http://www.nax.cz/pub/bioapi/pam_bioapi/pam-bioapi_0.3.0.tar.gz and extract it. Now open a terminal and type:

Comment: you will have to install some libraries in order to be able to compile the plugin

: {{cmduser|sudo apt-get install build-essential}}
: {{cmduser|sudo apt-get install libpam0g-dev}}

Now, you can compile and install the plugin

: {{cmduser|cd /path/to/where/you/extracted/the/arcive}}
: {{cmduser|./configure --libdir<nowiki>=</nowiki>/lib --enable-file-store && make}}
: {{cmduser|sudo make install}}

That's installed the plugin. Now, open a terminal and type the following scary commands: (Note: The line starting 'SERIAL=' and the line following it should be in the same line). {{Todo|comment from a user of this page: the third command is not displayed correctly (issue of wrapping the "<nowiki>|</nowiki>" character).}}

: {{cmduser|cd ~}}
: {{cmduser|sudo bash}}
: {{cmdroot|SERIAL=`BioAPITest | sed -ne "/Fingerprint/{n;n;s/^.*: $.\{9\}$$.\{4\}$$.\{4\}$$.\{4\}$$.*$/\1-\2-\3-\4-\5/gp}"`}}
: {{cmdroot|mkdir -p /etc/bioapi/pam/$SERIAL}}
: {{cmdroot|cp yourusername.bir /etc/bioapi/pam/$SERIAL}}
: {{cmdroot|exit}}

Phew. Now, to make applications actually use the fingerprint reader. Open a terminal window, and type:

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

Delete everything in the file, and paste this instead:

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

Save and close the file. That will make all PAM-aware applications use the fingerprint reader. Unfortunately, this also includes sudo. Since sudo is a command line application, it will display prompts in a terminal for you to swipe your finger, which is all well and good. The problem with this is that many Ubuntu administrative applications (such as Synaptic) use gksu to present a graphical front-end to sudo, which will output messages on the command line which you'll never see. Result? Administrative programs won't work from the gnome menu. The solution is to make sudo use the good old password. Open a terminal and type:

: {{cmduser|sudo gedit /etc/pam.d/sudo}}

Delete everything in the file, and instead paste:

<pre>
#%PAM-1.0

#@include common-auth
auth required pam_unix.so nullok_secure
@include common-account
</pre>

Now, save the file and close it, and reboot your system. GDM will ask you for a username, and then show a pretty prompt where you can scan your fingerprint! Same goes for gnome-screensaver when you set it to lock. Sometimes gnome-screensaver will not display the prompt, but you should still swipe your finger and be able to log back in.

===Bluetooth with Mobile Phones/PDAs===

Rather strangely, Ubuntu seems to have taken a step backwards with Bluetooth useability in Edgy. What worked out of the box with Dapper, now requires configuratio. First, open System - Preferences - Sessions and go to the Startup Programs tab. Then, find the entry labelled 'bt-applet --sm-disable'. Highlight it and click disable. Click add and in the command field type 'bt-applet'. Repeat this process, adding an entry for 'gnome-obex-server'. Now, open Synaptic Package Manager (System - Administration - Synaptic Package Manager) and click Search. Type 'gnome-bluetooth' to find the package, then mark it for installation. Now repeat this process for 'bluez-passkey-gnome'. Click apply to make changes.

Now that everything is installed, log-out of Gnome and log back in again. From your phone/PDA, search for devices untill you see your ThinkPad (the hostname will be displayed). Pair with the device. When asked for a passkey, enter 1234, which is the default. If you want to change your passkey (and you should), open a terminal and type:

: {{cmduser|sudo gedit /etc/bluetooth/hcid.conf}}

Find the line which says 'Default PIN for incoming connections' and change the PIN on the line beneath it:

<pre>
# Default PIN code for incoming connections
passkey "4017";
</pre>

Save and close the file, then type:

: {{cmduser|sudo /etc/init.d/bluetooth restart}}

You will now be able to use your new PIN code. To send files from your device to the ThinkPad, simply select the file you want to send and click Send Via Bluetooth (or whatever option your device presents). A dialog will pop-up in Gnome showing you a new file has been received.

: Figure 9. Gnome informing us that a file has been received
: [[Image:bluetooth.jpg]]

Sending files from your ThinkPad to your device requires more effort. The way it should work is that you right-click on a file, click send to, then make sure 'Bluetooth (OBEX)' is selected. Your device should be displayed and you could just click send. Unfortunately, due to a bug in gnome-bluetooth (described in https://launchpad.net/distros/ubuntu/+source/gnome-bluetooth/+bug/70718) this method does not work. If it does work for you, the bug has been solved and you can skip the rest of this section.

Your only other option is to use the command line to send files to your device. Open a terminal, then type:

: {{cmduser|hcitool scan}}

A list of detected bluetooth devices will be shown, for example, my output shows the following:

<pre>
Scanning ...
00:09:DD:60:02:EB Photosmart 8100 series
00:14:A7:99:3C:1F ThElInK
</pre>

The first field is the MAC address of the device, the second is the name of the device. In this case my bluetooth printer and mobile phone (ThElInK) were detected. In order to send files to my phone, I use:

: {{cmduser|gnome-obex-send -d 00:14:A7:99:3C:1F myPicture.jpg}}

Replace the MAC address with that of your device and myPicture.jpg with the file you want to send.

===TrackPoint Scrolling===

By default you can use the right and bottom edges of your touchpad to scroll through documents. If you use the TrackPoint instad of the touchpad (and believe me, you should), you'll find that scrolling is disabled by default. To enable it, open a terminal and type:

: {{cmduser|sudo gedit /etc/X11/xorg.conf}}

Now find the entry for your TrackPoint device. In my configuration file, the TrackPoint entry is the first mouse entry, after the keyboard entry, and looks something like this:

<pre>
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection
</pre>

Right after this entry is my touchpad entry. My entry is on line 66, but yours may be different. Now, add the follwing two options in that InputDevice section:

<pre>
Option "EmulateWheel" "on"
Option "EmulateWheelButton" "2"
</pre>

Save and exit the file. Restart your ThinkPad (or logout, and press CTRL-ALT-BACKSPACE). You should now be able to scoll by holding down the middle button for your TrackPoint and using the TrackPoint to scroll.

===Getting Multimedia to Work===

Due to patents and similar legal crap, Ubuntu will not play most media files by default. You also won't get browser plugins for multimedia. Luckily, this is easily fixed. Open a terminal and type the following:

: {{cmduser|sudo cp /etc/apt/sources.list /etc/apt/sources.list.backup}}
: {{cmduser|sudo gedit /etc/apt/sources.list}}

Delete everything in the file, and instead paste the following:

<pre>
deb-src http://archive.ubuntu.com/ubuntu edgy main restricted universe multiverse
#deb http://archive.ubuntu.com/ubuntu edgy-proposed main restricted universe multiverse

## MAJOR BUG FIX UPDATES produced after the final release
deb-src http://archive.ubuntu.com/ubuntu edgy-updates main restricted universe multiverse

## UBUNTU SECURITY UPDATES
deb http://security.ubuntu.com/ubuntu edgy-security main restricted universe multiverse
deb-src http://security.ubuntu.com/ubuntu edgy-security main restricted universe multiverse

## BACKPORTS REPOSITORY (Unsupported. May contain illegal packages. Use at own risk.)
#deb http://archive.ubuntu.com/ubuntu edgy-backports main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu edgy-backports main restricted universe multiverse

## PLF REPOSITORY
deb http://packages.freecontrib.org/ubuntu/plf edgy-plf free
deb-src http://packages.freecontrib.org/ubuntu/plf edgy-plf free
deb http://packages.freecontrib.org/ubuntu/plf edgy-plf non-free
deb-src http://packages.freecontrib.org/ubuntu/plf edgy-plf non-free

## CANONICAL COMMERCIAL REPOSITORY (Hosted on Canonical servers, not Ubuntu
## servers. RealPlayer10, Opera, DesktopSecure and more to come.)
deb http://archive.canonical.com/ubuntu edgy-commercial main

## Listen
#deb http://theli.free.fr/packages/ edgy listen

## Automatix repo
deb http://www.getautomatix.com/apt edgy main
</pre>

Now, open a terminal and type the following:

: {{cmduser|wget <nowiki>http://packages.freecontrib.org/ubuntu/plf/12B83718.gpg</nowiki> -O- <nowiki>|</nowiki> sudo apt-key add -}}
: {{cmduser|wget <nowiki>http://www.getautomatix.com/apt/key.gpg.asc</nowiki>}}
: {{cmduser|gpg --import key.gpg.asc}}
: {{cmduser|gpg --export --armor 521A9C7C <nowiki>|</nowiki> sudo apt-key add -}}
: {{cmduser|sudo apt-get update}}
: {{cmduser|sudo apt-get install automatix2}}
: {{cmduser|wget <nowiki>http://easyubuntu.freecontrib.org/files/easyubuntu-3.023.tar.gz</nowiki>}}
: {{cmduser|tar -zxf easyubuntu-3.023.tar.gz}}
: {{cmduser|cd easyubuntu}}
: {{cmduser|cp packagelist-dapper.pot packagelist-edgy.pot}}
: {{cmduser|cp packagelist-dapper.xml packagelist-edgy.xml}}
: {{cmduser|sudo python easyubuntu.in}}

Don't worry if you get errors from the Ubuntu PLF repository. PLF mirrors are about as stable as wild bull in a farm full of cows. Select what you want to install from the resulting window. Make sure you do not select the totem-mozilla plugin, as this just doens't work, for me at least. When EasyUbuntu has finished installing packages, you should be returned to a terminal, which you can close. Now go to Applications - System Tools - Automatix. Read and agree to the warning. Check what you want to install. Make sure you check 'Mplayer and FF plugin'. When ready, click the 'install' button. That should get multimedia working nicely.

: Figure 10. The Automatix user interface
: [[Image:automatix.jpg]]

===Beryl - fancy 3D desktop===

MAC OS X has Aqua and Windows Vista has Aero. Well, Linux has XGL/Beryl which can get effects which are as good looking (or sometimes better!) than the former two. Installing Beryl on Ubuntu is not that hard. First, open a terminal and type the following:

: {{cmduser|sudo gedit /etc/apt/sources.list}}

At the end of the file, append the following:

<pre>
##Beryl
deb http://ubuntu.beryl-project.org/ edgy main
</pre>

Save and close the file. Now type:

: {{cmduser|wget <nowiki>http://beryl-mirror.lupine.me.uk/1609B551.gpg</nowiki> -O- <nowiki>|</nowiki> sudo apt-key add -}}
: {{cmduser|sudo apt-get update}}

ATI Users Only: type

: {{cmduser|sudo apt-get install xserver-xgl}}

Now, to install beryl:

: {{cmduser|sudo apt-get install beryl emerald-themes}}

To make Ubuntu use the 3D effects. Open a terminal:

: {{cmduser|sudo gedit /usr/local/bin/startxgl.sh}}

In that file, paste the following if you use an ATI card:

<pre>
#!/bin/sh
Xgl -fullscreen :1 -ac -br -accel glx:pbuffer -accel xv:pbuffer &
sleep 4
export DISPLAY=:1
exec gnome-session
</pre>

If you use an Intel card, paste the following instead:

<pre>
#!/bin/sh
beryl-manager
sleep 4
exec gnome-session
</pre>

Save the file and close. Now we need to make the file executable:

: {{cmduser|sudo chmod a+x /usr/local/bin/startxgl.sh}}

All that's left now is to create a login script which makes gnome use the 3D effects. In a terminal, type:

: {{cmduser|sudo gedit /usr/share/xsessions/xgl.desktop}}

Now, in this file paste:

<pre>
[Desktop Entry]
Encoding=UTF-8
Name=Xgl
Exec=/usr/local/bin/startxgl.sh
Icon=
Type=Application
</pre>

Save and close the file. Now type:

: {{cmduser|sudo gedit /usr/local/bin/start_beryl.sh}}

In this file, paste:

<pre>
#!/bin/bash
#
# Start beryl-manager within gnome-session
#
if [ `ps -A -o comm | grep -c '^Xgl$'` == "1" ]; then
DISPLAY=:1 beryl-manager
DISPLAY=:1 beryl-xgl
else echo "${0}: Error: beryl-manager not launched. Xgl not running?"
fi
</pre>

Now make the file executable:

: {{cmduser|sudo chmod a+x /usr/local/bin/start_beryl.sh}}

Now go to System - Preferences - Sessions, go to the Startup Programs tab, and click add, then type

: {{cmduser|/usr/local/bin/start_beryl.sh}}

Now, reboot your ThinkPad. When you come to the login screen, click the 'Sessions' button on the bottom left corner, and select XGL. login, et voila! beautiful 3D effects!

: Figure 11. Beryl's Cube effect
: [[Image:cube.jpg]]

If you have NetBeans installed, try launching it now. It probably won't work due to Beryl. Luckily, this is easily solved. Open a terminal and type:

: {{cmduser|sudo gedit /etc/environment}}

Then add the following line to the end of the file.

<pre>AWT_TOOLKIT="MToolkit"</pre>

Now save, close and reboot. Netbeans should now work!

===Problem: Can't add programs to session===

So you tried to add something to your startup programs, it shows up in the list, but it doesn't start up. You then launch the sessions program again, only to find your program has disappeared from the list. This problem is being caused by incorrect permissions in your home directory, and can happen on some occasions. To fix it, open a terminal and type the following:

: {{cmduser|sudo chown -R username:usergroup /home/username/.config/}}

Replace username with your username and usergroup with your group (by default, in Ubuntu your usergroup is the same as your username). Everything should be OK now!

===Problem: Virtual terminals not working===

One problem I had after installing the ATI drivers was that virtual terminals stopped working. Instead of seeing a console when pressing CTRL+ALT+F1...F6 I was seeing a yellow/orange garbled output. Luckily, solving this with ATI drivers is trivial. Open a terminal, and type:

: {{cmduser|sudo gedit /boot/grub/menu.lst}}

Find the line which says

<pre>#defoptions=quiet splash</pre>

and replace it with

<pre>#defoptions=quiet splash vga=791</pre>

Now, find the line which boots the kernel you are currently using, this is just under '## ## End Default Options ##. In the 'kernel' line, add:

<pre>vga=791</pre>

Before:

<pre>kernel /vmlinuz-2.6.17-10-generic root=/dev/sda7 ro quiet splash</pre>

After:

<pre>kernel /vmlinuz-2.6.17-10-generic root=/dev/sda7 ro quiet splash vga=791</pre>

Now save and exit the file, and reboot. Virtual terminals should now work. If you use Intel drivers, you're going to have to bite the bullet and remove the 'splash' keyword from both the defoptions and kernel lines. You'll lose the pretty bootup screen, but at least virtual terminals will work, which are important to recover a crashed system.

===Problem: I keep logging out!===

If you're using Beryl, and find that you keep getting logged out, you've just encountered one of Beryl's most annoying bugs. Shift+Backspace causes a logout. To fix this, open a terminal and type:

: {{cmduser|gedit /home/username/annoymenot.sh}}

Remember to replace 'username' with your username. Now, in this file type:

: {{cmduser|xmodmap -e "keycode 22 <nowiki>=</nowiki> BackSpace BackSpace Terminate_Server" }}

Save and close the file, and make it executable:

: {{cmduser|chmod 755 /home/username/annoymenot.sh}}

Now go to System - Preferences - Session, Startup Programs. Click add, and type

: {{cmduser|/home/username/annoymenot.sh}}

Logout and back in, problem solved! While you're at it, how about getting the start button to work? Go to System - Preferences - Keyboard - Layout Options - Alt/Win Key behaviour and select 'Super is mapped to Win keys (default)'.

===Desktop envy===

We're living in an age of desktop prettyness, and Linux can be just as pretty as MAC OS X or Vista. You've already got Beryl installed. Now go to Applications - Accesories - gDesklets. If the gDesklets entry is not there, make sure you install it, either using Synaptic or Automatix. Desklets are small programs you can add to your desktop, ala OS X's Deskbar or Vista's Sidebar. To make them start on boot, add gdesklets in System - Preferences - Sessions, Startup Programs.

Another cool program is cairo clock. Download it from http://macslow.thepimp.net/projects/cairo-clock/cairo-clock_0.3.2-1_i386.deb and install it by double-clicking. To make it start automatically, add it to your sessions as mentioned above. I've found the following command makes it work best for me:

<pre>cairo-clock -s -w 175 -g 175 -x 1219 -y 7 -t radium</pre>

Finally, make sure you click that Ruby icon in your notification area, it allows you to configure Beryl to do all sorts of cool stuff!

===Conclusion===

Well, that's about it! A dream Linux system on a dream laptop! Check out these cool technologies for an even better system:

* Beagle
* Tomboy
* Deskbar

===References===

* ATI on Ubuntu - https://help.ubuntu.com/community/BinaryDriverHowto/ATI
* Garbled Virtual Terminal Bug - https://launchpad.net/distros/ubuntu/+source/usplash/+bug/63558
* Beryl logout Bug - http://forum.beryl-project.org/viewtopic.php?p=1295&sid=6feedd09a7f01bca68feb05a5f2f033c
* Beryl Netbeans Bug - http://ubuntuforums.org/showthread.php?t=252594
* Beryl on Ubuntu - http://wiki.beryl-project.org/index.php/Install/Ubuntu/Edgy/XGL
* Home directory permissions bug - http://www.ubuntuforums.org/showthread.php?p=1789997
* gnome-bluetooth bug - https://launchpad.net/distros/ubuntu/+source/gnome-bluetooth/+bug/70718

Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60

2006-12-20T08:27:19Z

Ischg: /* Beryl - fancy 3D desktop */

[[User:Keithvassallo|Keithvassallo]] 14:39, 16 December 2006 (CET)

===Abstract===

This article describes how to get Ubuntu Linux 6.10 (Edgy) installed on an IBM/Lenovo ThinkPad T60. It's not meant to be a definite guide to installing Ubuntu (the Ubuntu Guide at http://www.ubuntuguide.org does a very good job of that). This article is meant to describe how to get most of the ThinkPad features working on Ubuntu system. It also discusses how to get Multimedia, some cool-looking effects such as Beryl, gDesklets and similar working on Ubuntu. Finally, we discuss some common problems encountered on Ubuntu and ThinkPads alike.

===My ThinkPad===

Although this guide should work on most recent ThinkPads, I cannot guarantee that. These are the specifications of my machine. The closer your specs are, the greater the chance of success.

: Figure 1. ThinkPad T60 2007, complete with Tux sticker :-)
: [[Image:thinkpad.jpg]]

* Lenovo ThinkPad T60 2007.
* Intel Centrino Duo T2400 / 1.83 GHz.
* Mobile Intel 945PM Express Chipset.
* Intel Wireless LAN.
* Integrated Bluetooth.
* ATI Mobility Radeon X1400 - PCI Express x16, 128MB dedicated RAM.
* 100 GB - Serial ATA-150 Hard Drive.
* 15' TFT Active Matrix Display (1400x1050).

That's basically all you need to know. As far as I know, all other features are common to all ThinkPads manufactured by Lenovo since they acquired IBM's computer business.

===Why Ubuntu? (or rather, Why not SUSE?)===

In June 2006, Lenovo announced it would be shipping ThinkPad T60p laptops with SUSE Linux Enterprise Desktop (SLED) 10 pre-installed, since SLED apparently supports all of the features of the T60p. I contacted my local IBM supplier, who said that Lenovo were no longer manufacturing the T60p, since the company which was making the displays went out of business. This meant I could not get a T60p with SLED pre-installed. I decided to go for the T60 2007, which is the closest thing I could find to the T60p. This comes with Windows XP Professional pre-installed.

I first tried to get SLED installed on the T60. Although it did indeed install, and most features worked, I soon got bored of SLED. Firstly, SLED uses Gnome 2.12, which is by now ancient. Secondly, although the Lenovo utilities do work on SLED, they only work well if you use KDE as your defauly desktop environment, which is a pity since I'm a Gnome user. The utilities were very unstable to me too. Finally, what made me give up SLED was the usual problem - it's an RPM based distribution. Once you start using Debian derivatives, with their apt based installer, you won't want to go back. That's when I decided to try Ubuntu, and have not regretted it since.

===What Works?===

* Ubuntu and all programs it comes with.
* Most of the function keys, except the ones mentioned below
* The fingerprint reader.
* The ATI proprietary graphics drivers.
* Suspend to RAM (Sleep) and Suspend to Disk (Hibernate).
* Brightness, Volume and Mute with OSD (On-Screen Display).
* ThinkLight, TrackPoint II and the touchpad.

===What Doesn't Work? (Known Issues)===

* FN+F8, FN+F9, FN+ZOOM.
* The BACK and FORWARD buttons (next to the cursor keys).
* The ThinkVantage button (in Linux, still works on boot).
* Sending files to Bluetooth devices via GUI.

There are probably ways and means to get the offending buttons to work, I've tried several fora but none seem to address my exact problem. I'll update this article should I find out anything.

===First Things First - Creating a Windows Recovery Disc===

If you've purchased a T60, chances are it came with Windows XP Professional. The other option is for you to have FreeDOS installed, in which case you can skip this section. You could remove the Windows partition altogether, and reserve your ThinkPad for Linux, but that's not the route I've chosen. The ThinkVantage utilities in Windows allow you to do a lot of cool things, such as set-up a boot-up fingerprint security scan. You can't do this from Linux (as far as I know) so it's best to leave the Windows partition in place. So, boot your ThinkPad and complete the Windows XP setup (which asks you to add a user account and enroll yourself using the ThinkVantage Client Security Solution). While you're there, use the ThinkVantage productivy centre to enroll your fingerprint (I suggest enrolling more than one) and make sure you check the option to require a fingerprint scan on boot (not for security, for geek points). When you reboot, press ESC or F2 to get to BIOS, and make sure you check the option to require a supervisor password. This will make your ThinkPad prompt you for your fingerprint when you power it up.

: Figure 2. Configuring fingerprint security from Windows
: [[Image:winprint.jpg]]

Now that's working, you should create a recovery DVD using the ThinkVantage recovery utilities. This will allow you to recover your Windows installation should you manage to screw your partitions up in the following stages. I highly recommend you do this, as Lenovo does not provide Windows XP CDs with this Laptop - so the hard disk partition is all you've got. Once this is done, we're ready to install Ubuntu!

: Figure 3. Creating recovery discs from Windows
: [[Image:recovery.jpg]]

===Getting Ubuntu installed===

Download the latest Edgy live CD from the Ubuntu website, you can find a list of mirrors at http://www.ubuntu.com/products/GetUbuntu/download#currentrelease. You may also try Kubuntu, Edubuntu or any of it's derivatives, but I'll stick with Ubuntu here for simplicity's sake. Once that's downloaded, burn the ISO to disc using any program of your choice (If this is your first Linux experience and you're using Windows, try using Nero - http://www.nero.com).

Once the burning process is complete, reboot your machine ensuring that the Ubuntu CD is in the drive. You should see an Ubuntu menu. If you don't, your BIOS is not set to boot from CD. Reboot your ThinkPad and change the boot order from BIOS (by default ThinkPads boot from CD-ROM before the hard disk, so this is probably not necessary). Once the menu shows up, select 'Start or install Ubuntu' and let it boot. This will take a while as everything is loaded from CD. You should eventually end up in a Gnome desktop. If you see an error about the Gnome Settings Daemon not being able to load, simply ignore it, as this is not necessary for now. For the purposes of the installation, it's best if you have a wired ethernet connection, as it's unlikely the wireless network card will work until we boot into our installed Ubuntu system.

: Figure 4. Select the first option to start Ubuntu
: [[Image:boot.jpg]]

Double-Click on the 'install' icon on the Desktop to start installation. The installation should be pretty straight-forward. If you need additional help, check out the walk-through with screen-shots at http://www.debianadmin.com/ubuntu-edgy-eft-desktop-installation-with-screenshots.html. The only stage at which we need to make changes is the partitioning stage. This to make sure we preserve our Windows partition, and the IBM vendor_diag partition which allows recovery of the laptop when things go hay-wire. In the 'Prepare disk space' section of the installer, select the third option, 'Manually edit partition table'. A bar will be displayed showing your existing partitions. If you have Windows installed you will see two partitions. The first is a 4.89 GB IBM Vendor Diagnostic partition, which we do not want to touch. The second will be your Windows partition, which will fill the rest of the disk. Click on this partition, Then click the 'Resize/Move' button. I resized my Windows partition to 24 GB. This is enough to accommodate the 10 GB already in use on that partition, as well as giving Windows another 14 GB of free space. 6 GB of free space would probably be enough though.

Now it's time to create partitions for Linux. You need at least two partitions; a swap partition which should be roughly double the amount of RAM you have, and a root partition to install Linux. I opted for four partitions, as follows:

<table border=1>
<tr><td>'''Purpose'''</td><td>'''Size'''</td><td>'''File-System'''</td></tr>
<tr><td>Swap</td><td>2 GB</td><td>swap</td></tr>
<tr><td>/boot</td><td>5 GB</td><td>ext3</td></tr>
<tr><td>/ (root)</td><td>20 GB</td><td>ext3</td></tr>
<tr><td>/home</td><td>37.25 GB (what's left of the disk)</td><td>ext3</td></tr>
</table>

To create these paritions, click on the 'New' button and select 'Extended Partition' in the 'create as' drop-down list. Leave all other settings as-is, and click 'Add'. Now, click on the newly created partition, and create each of the partitions you want to create, simply specify the size of the partition in the 'New Size (MiB)' text box. To convert GB to MiB, multiply by 1024. So for your swap partition you should specify a size of 2048. Repeat until you have created all the required partitions. If you follow my parition layout, the partition editor should look something like Figure 5.

: Figure 5. Our partitions, ready to be created
: [[Image:partitioning.jpg]]

You will not see mount-points in your diagram, because the screen-shot above was taken after they were assigned, but you should get the general idea. After this screen, you will be asked to assign mount-points to the partitions you have just created. If you created the partitions in the same order I did, you can assign mount points as I have (i.e. /dev/sda5 for swap, /dev/sda6 for /boot, /dev/sda7 for /, /dev/sda8 for /home). Additionally, I mounted my Windows partition as /media/sda1 and my IBM Vendor Diagnostic partition as /media/sda2. These are optional. After this step, continue installation as normal. When the installation is complete, click the 'reboot' button to restart into your fresh Ubuntu System.

When booting, the GRUB boot-loader will be displayed, asking you what you want to load. You will probably see four options. The first two being Ubuntu Linux and Ubuntu Linux recovery mode (showing the kernel version). The other two will be Microsoft Windows XP, and 'Other Windows XP/2000/NT' partition. This is your IBM Vendor Diagnostic partition, which is based on the Windows kernel, apparently. Select the first entry to boot Ubuntu. The next time you boot Windows, it will bring up a chkdsk screen. This is entirely normal and happens because we have resized the Windows partition. Make sure you do not skip this check and let it complete.

===Wireless LAN===

The first thing we should do is to get wireless networking working. Luckily, getting the Centrino wireless LAN chip working in Ubuntu is quite easy, if you use the gnome-network-manager applet. Just go to System - Administration - Synaptic Package Manager. Then click 'Search' and set the 'look-in' field to 'name'. In the 'Search' text box type:

<pre>network-manager</pre>

: Figure 6. Installing the network manager applet
: [[Image:networkmanager.jpg]]

Click on the box beside 'network-manager' and click 'Mark for installation'. Do the same for 'network-manager-gnome'. Once installed, reboot your thinkpad. An applet will show up in the gnome notification area. Click on it, and a list of detected wireless networks will be displayed. Simply click on one of them, enter any authentication details necessary, and you'll be connected to the wireless network.

: Figure 7. gnome-network-manager showing available wireless networks
: [[Image:available-accesspoints.jpg]]

Note! Not all versions of the T60 has the Intel Wireless LAN as described above. Run lspci from the command line and look for details of your wifi card. E.g.:

03:00.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)

suggest you have a different wifi card. Read this forum thread http://ubuntuforums.org/showthread.php?t=38972

running:
# dmesg | grep hal

may yield output like this, which apparently suggests the hardware abstraction layer is in place.
[17179590.420000] ath_hal: module license 'Proprietary' taints kernel.
[17179590.424000] ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)

If not, or if the output contains "HAL Status 13" it apparently suggests your card is not supported by the current drivers, and you need to upgrade.

===Installing the ATI display drivers===

If your ThinkPad has an Intel graphics adapter, you should skip this section as Ubuntu installs the best driver automatically. Ubuntu does not install the ATI proprietary drivers by default because they are, er, proprietary. Luckily, installing them is easy enough. Open a terminal (Applications - Accessories - Terminal) and type the following:

: {{cmduser| sudo apt-get update}}
: {{cmduser| sudo apt-get install xorg-driver-fglrx fglrx-control}}

Now we make sure the proprietary driver is not disabled by the kernel. Type the following, and remove any lines referring to fglrx

: {{cmduser|sudo gedit /etc/default/linux-restricted-modules-common}}

An alternative to gedit (Gnome) is nano (sudo nano -w /etc...) for a CLI editor.

Finally, we need to configure the X server to use the ATI drivers. Type the following:

: {{cmduser|sudo depmod -a}}
: {{cmduser|sudo aticonfig --initial}}
: {{cmduser|sudo aticonfig --overlay-type<nowiki>=</nowiki>Xv}}

One last thing. In order to correct a very common problem of getting a jerky video display, type the following:

: {{cmduser|sudo gedit /etc/X11/xorg.conf}}

Scroll to the end of the file, and add the text below.

<pre>
Section "Extensions"
Option "Composite" "0"
EndSection
</pre>

Save the file and exit. Now, to apply the changes either press CTRL+ALT+Backspace or reboot. The resolution should have switched to 1400x1050 and everything should look prettier and render faster. Just to make sure everything is working, open up a terminal and type

: {{cmduser|fglrxinfo}}

This should display:

<pre>
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Mobility Radeon X1400 Generic
OpenGL version string: 2.0.6011 (8.28.8)
</pre>

The above is what I get on my ThinkPad, and you should see something similar. As long as you see your graphics card model listed, everything should be OK. If, instead, you see a bunch of lines containing 'Mesa' then you have a problem. In that case, I recommend consulting https://help.ubuntu.com/community/BinaryDriverHowto/ATI and the Ubuntu forums at http://ubuntuforums.org

===The fingerprint reader===

Although IBM does not officially support it, the fingerprint reader does in fact work with most Linux distributions. Getting it to work with Ubuntu can be a bit of a pain, but it does work. Basically, a bioAPI plugin is provided for PAM. PAM-aware applications such as GDM and gnome-screensaver will then automatically use the fingerprint reader, which is uber cool. Anyway, enough theory, I've probably lost the newbies amongst you already. Go to http://www.qrivy.net/~michael/temp/ and download the latest bioapi package (at the time of writing, bioapi_1.2.3_i386.deb). When asked, tell Firefox to open the file with the GDebi package installer.

That will install bioAPI. What we need now is the driver for our fingerprint device, which is manufactured by UPEK. Go to http://www.upek.com/support/dl_linux_bsp.asp and download the latest version, currently UPEK_BSP_LIN_1.0.zip. Extract this file, then open a terminal (and don't close it until I say so).

: {{cmduser|cd /path/to/where/you/extracted/the/file}}
: {{cmduser|sudo bash}}
: {{cmdroot|sh install.sh /usr/lib}}

Now we need to assign the right permissions so non-root applications can use the driver:

: {{cmdroot|addgroup --system bioapi}}
: {{cmdroot|addgroup --system usbfs}}
: {{cmdroot|adduser yourusername bioapi}}
: {{cmdroot|adduser yourusername usbfs}}
: {{cmdroot|chown -R root:bioapi /usr/var/bioapi/}}
: {{cmdroot|chmod -R 770 /usr/var/bioapi/}}
: {{cmdroot|chown -R root:usbfs /proc/bus/usb}}
: {{cmdroot|chmod -R g+X /proc/bus/usb}}

Of course, replace 'yourusername' with the username you use to login. Now, we need to set the usb file system (usbfs) to be usable by users in the usbfs group. To do this, we need to determine the group ID of the usbfs group. Type the following:

: {{cmdroot|cat /etc/group <nowiki>|</nowiki> grep usbfs <nowiki>|</nowiki> cut -d':' -f 3}}

In my case the number is 116, it might be different for you. Now, open the file /etc/fstab:

: {{cmdroot|gedit /etc/fstab}}

and type the following:

<pre>none /proc/bus/usb usbfs defaults,devgid=116,devmode=0660,busgid=116,busmode=0770,listgid=116,listmode=0660 0 0</pre>

Please type the above code in one line in your file. Remember to replace 116 if you got a different number with the previous cat command. The last permission-related thing we need to fool around with is UDEV. Open the udev permissions file

: {{cmdroot|gedit /etc/udev/rules.d/40-permissions.rules}}

and find the line:

<pre>SUBSYSTEM=="usb_device", MODE="0664"</pre>

It's line 65 in my file. Change it so it looks like this:

<pre>SUBSYSTEM=="usb_device", MODE="0660", GROUP="usbfs"</pre>

Now we need to enroll our fingerprint with the system. To do this, we need a utility called Sample, which is only distributed in source-code form with the driver. This is great, only I couldn't get it to compile on Ubuntu. Luckily, there is a binary version available from one of the earlier releases of the driver (beta 2). To get this, download it from ftp://linux:Tuc-nak3@delta.upek.com/TFMESS_BSP_LIN_1.0beta2.zip. Now, extract the file and type:

: {{cmdroot|cd /path/to/where/you/extracted/the/archive}}
: {{cmdroot|cd NonGUI_sample}}
: {{cmdroot|chmod a+x Sample}}
: {{cmdroot|./Sample}}

Press (e) to enroll a new user, and enter your username when asked for the user ID. You will be asked to swipe your finger three times. Now press (v) and swipe your finger, a green check should be displayed showing you have successfully authenticated.

: Figure 8. The fingerprint swipe prompt
: [[Image:touchchip.jpg]]

Wonderful! Now, quit the application (q) and type exit to become a normal user. A file called yourusername.bir should have been created, copy this to your home directory:

: {{cmdroot|cp yourusername.bir /home/yourusername/}}

You can now close the terminal window. The next step is to install the BioAPI plug-in for PAM, and to make applications use the plugin. So, get the pam_bioapi plugin from http://www.nax.cz/pub/bioapi/pam_bioapi/pam-bioapi_0.3.0.tar.gz and extract it. Now open a terminal and type:

Comment: you will have to install some libraries in order to be able to compile the plugin

: {{cmduser|sudo apt-get install build-essential}}
: {{cmduser|sudo apt-get install libpam0g-dev}}

Now, you can compile and install the plugin

: {{cmduser|cd /path/to/where/you/extracted/the/arcive}}
: {{cmduser|./configure --libdir<nowiki>=</nowiki>/lib --enable-file-store && make}}
: {{cmduser|sudo make install}}

That's installed the plugin. Now, open a terminal and type the following scary commands: (Note: The line starting 'SERIAL=' and the line following it should be in the same line). {{Todo|comment from a user of this page: the third command is not displayed correctly (issue of wrapping the "<nowiki>|</nowiki>" character).}}

: {{cmduser|cd ~}}
: {{cmduser|sudo bash}}
: {{cmdroot|SERIAL=`BioAPITest | sed -ne "/Fingerprint/{n;n;s/^.*: $.\{9\}$$.\{4\}$$.\{4\}$$.\{4\}$$.*$/\1-\2-\3-\4-\5/gp}"`}}
: {{cmdroot|mkdir -p /etc/bioapi/pam/$SERIAL}}
: {{cmdroot|cp yourusername.bir /etc/bioapi/pam/$SERIAL}}
: {{cmdroot|exit}}

Phew. Now, to make applications actually use the fingerprint reader. Open a terminal window, and type:

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

Delete everything in the file, and paste this instead:

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

Save and close the file. That will make all PAM-aware applications use the fingerprint reader. Unfortunately, this also includes sudo. Since sudo is a command line application, it will display prompts in a terminal for you to swipe your finger, which is all well and good. The problem with this is that many Ubuntu administrative applications (such as Synaptic) use gksu to present a graphical front-end to sudo, which will output messages on the command line which you'll never see. Result? Administrative programs won't work from the gnome menu. The solution is to make sudo use the good old password. Open a terminal and type:

: {{cmduser|sudo gedit /etc/pam.d/sudo}}

Delete everything in the file, and instead paste:

<pre>
#%PAM-1.0

#@include common-auth
auth required pam_unix.so nullok_secure
@include common-account
</pre>

Now, save the file and close it, and reboot your system. GDM will ask you for a username, and then show a pretty prompt where you can scan your fingerprint! Same goes for gnome-screensaver when you set it to lock. Sometimes gnome-screensaver will not display the prompt, but you should still swipe your finger and be able to log back in.

===Bluetooth with Mobile Phones/PDAs===

Rather strangely, Ubuntu seems to have taken a step backwards with Bluetooth useability in Edgy. What worked out of the box with Dapper, now requires configuratio. First, open System - Preferences - Sessions and go to the Startup Programs tab. Then, find the entry labelled 'bt-applet --sm-disable'. Highlight it and click disable. Click add and in the command field type 'bt-applet'. Repeat this process, adding an entry for 'gnome-obex-server'. Now, open Synaptic Package Manager (System - Administration - Synaptic Package Manager) and click Search. Type 'gnome-bluetooth' to find the package, then mark it for installation. Now repeat this process for 'bluez-passkey-gnome'. Click apply to make changes.

Now that everything is installed, log-out of Gnome and log back in again. From your phone/PDA, search for devices untill you see your ThinkPad (the hostname will be displayed). Pair with the device. When asked for a passkey, enter 1234, which is the default. If you want to change your passkey (and you should), open a terminal and type:

: {{cmduser|sudo gedit /etc/bluetooth/hcid.conf}}

Find the line which says 'Default PIN for incoming connections' and change the PIN on the line beneath it:

<pre>
# Default PIN code for incoming connections
passkey "4017";
</pre>

Save and close the file, then type:

: {{cmduser|sudo /etc/init.d/bluetooth restart}}

You will now be able to use your new PIN code. To send files from your device to the ThinkPad, simply select the file you want to send and click Send Via Bluetooth (or whatever option your device presents). A dialog will pop-up in Gnome showing you a new file has been received.

: Figure 9. Gnome informing us that a file has been received
: [[Image:bluetooth.jpg]]

Sending files from your ThinkPad to your device requires more effort. The way it should work is that you right-click on a file, click send to, then make sure 'Bluetooth (OBEX)' is selected. Your device should be displayed and you could just click send. Unfortunately, due to a bug in gnome-bluetooth (described in https://launchpad.net/distros/ubuntu/+source/gnome-bluetooth/+bug/70718) this method does not work. If it does work for you, the bug has been solved and you can skip the rest of this section.

Your only other option is to use the command line to send files to your device. Open a terminal, then type:

: {{cmduser|hcitool scan}}

A list of detected bluetooth devices will be shown, for example, my output shows the following:

<pre>
Scanning ...
00:09:DD:60:02:EB Photosmart 8100 series
00:14:A7:99:3C:1F ThElInK
</pre>

The first field is the MAC address of the device, the second is the name of the device. In this case my bluetooth printer and mobile phone (ThElInK) were detected. In order to send files to my phone, I use:

: {{cmduser|gnome-obex-send -d 00:14:A7:99:3C:1F myPicture.jpg}}

Replace the MAC address with that of your device and myPicture.jpg with the file you want to send.

===TrackPoint Scrolling===

By default you can use the right and bottom edges of your touchpad to scroll through documents. If you use the TrackPoint instad of the touchpad (and believe me, you should), you'll find that scrolling is disabled by default. To enable it, open a terminal and type:

: {{cmduser|sudo gedit /etc/X11/xorg.conf}}

Now find the entry for your TrackPoint device. In my configuration file, the TrackPoint entry is the first mouse entry, after the keyboard entry, and looks something like this:

<pre>
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection
</pre>

Right after this entry is my touchpad entry. My entry is on line 66, but yours may be different. Now, add the follwing two options in that InputDevice section:

<pre>
Option "EmulateWheel" "on"
Option "EmulateWheelButton" "2"
</pre>

Save and exit the file. Restart your ThinkPad (or logout, and press CTRL-ALT-BACKSPACE). You should now be able to scoll by holding down the middle button for your TrackPoint and using the TrackPoint to scroll.

===Getting Multimedia to Work===

Due to patents and similar legal crap, Ubuntu will not play most media files by default. You also won't get browser plugins for multimedia. Luckily, this is easily fixed. Open a terminal and type the following:

: {{cmduser|sudo cp /etc/apt/sources.list /etc/apt/sources.list.backup}}
: {{cmduser|sudo gedit /etc/apt/sources.list}}

Delete everything in the file, and instead paste the following:

<pre>
deb-src http://archive.ubuntu.com/ubuntu edgy main restricted universe multiverse
#deb http://archive.ubuntu.com/ubuntu edgy-proposed main restricted universe multiverse

## MAJOR BUG FIX UPDATES produced after the final release
deb-src http://archive.ubuntu.com/ubuntu edgy-updates main restricted universe multiverse

## UBUNTU SECURITY UPDATES
deb http://security.ubuntu.com/ubuntu edgy-security main restricted universe multiverse
deb-src http://security.ubuntu.com/ubuntu edgy-security main restricted universe multiverse

## BACKPORTS REPOSITORY (Unsupported. May contain illegal packages. Use at own risk.)
#deb http://archive.ubuntu.com/ubuntu edgy-backports main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu edgy-backports main restricted universe multiverse

## PLF REPOSITORY
deb http://packages.freecontrib.org/ubuntu/plf edgy-plf free
deb-src http://packages.freecontrib.org/ubuntu/plf edgy-plf free
deb http://packages.freecontrib.org/ubuntu/plf edgy-plf non-free
deb-src http://packages.freecontrib.org/ubuntu/plf edgy-plf non-free

## CANONICAL COMMERCIAL REPOSITORY (Hosted on Canonical servers, not Ubuntu
## servers. RealPlayer10, Opera, DesktopSecure and more to come.)
deb http://archive.canonical.com/ubuntu edgy-commercial main

## Listen
#deb http://theli.free.fr/packages/ edgy listen

## Automatix repo
deb http://www.getautomatix.com/apt edgy main
</pre>

Now, open a terminal and type the following:

: {{cmduser|wget http://packages.freecontrib.org/ubuntu/plf/12B83718.gpg -O- | sudo apt-key add -}}
: {{cmduser|wget http://www.getautomatix.com/apt/key.gpg.asc}}
: {{cmduser|gpg --import key.gpg.asc}}
: {{cmduser|gpg --export --armor 521A9C7C | sudo apt-key add -}}
: {{cmduser|sudo apt-get update}}
: {{cmduser|sudo apt-get install automatix2}}
: {{cmduser|wget http://easyubuntu.freecontrib.org/files/easyubuntu-3.023.tar.gz}}
: {{cmduser|tar -zxf easyubuntu-3.023.tar.gz}}
: {{cmduser|cd easyubuntu}}
: {{cmduser|cp packagelist-dapper.pot packagelist-edgy.pot}}
: {{cmduser|cp packagelist-dapper.xml packagelist-edgy.xml}}
: {{cmduser|sudo python easyubuntu.in}}

Don't worry if you get errors from the Ubuntu PLF repository. PLF mirrors are about as stable as wild bull in a farm full of cows. Select what you want to install from the resulting window. Make sure you do not select the totem-mozilla plugin, as this just doens't work, for me at least. When EasyUbuntu has finished installing packages, you should be returned to a terminal, which you can close. Now go to Applications - System Tools - Automatix. Read and agree to the warning. Check what you want to install. Make sure you check 'Mplayer and FF plugin'. When ready, click the 'install' button. That should get multimedia working nicely.

: Figure 10. The Automatix user interface
: [[Image:automatix.jpg]]

===Beryl - fancy 3D desktop===

MAC OS X has Aqua and Windows Vista has Aero. Well, Linux has XGL/Beryl which can get effects which are as good looking (or sometimes better!) than the former two. Installing Beryl on Ubuntu is not that hard. First, open a terminal and type the following:

: {{cmduser|sudo gedit /etc/apt/sources.list}}

At the end of the file, append the following:

<pre>
##Beryl
deb http://ubuntu.beryl-project.org/ edgy main
</pre>

Save and close the file. Now type:

: {{cmduser|wget <nowiki>http://beryl-mirror.lupine.me.uk/1609B551.gpg</nowiki> -O- <nowiki>|</nowiki> sudo apt-key add -}}
: {{cmduser|sudo apt-get update}}

ATI Users Only: type

: {{cmduser|sudo apt-get install xserver-xgl}}

Now, to install beryl:

: {{cmduser|sudo apt-get install beryl emerald-themes}}

To make Ubuntu use the 3D effects. Open a terminal:

: {{cmduser|sudo gedit /usr/local/bin/startxgl.sh}}

In that file, paste the following if you use an ATI card:

<pre>
#!/bin/sh
Xgl -fullscreen :1 -ac -br -accel glx:pbuffer -accel xv:pbuffer &
sleep 4
export DISPLAY=:1
exec gnome-session
</pre>

If you use an Intel card, paste the following instead:

<pre>
#!/bin/sh
beryl-manager
sleep 4
exec gnome-session
</pre>

Save the file and close. Now we need to make the file executable:

: {{cmduser|sudo chmod a+x /usr/local/bin/startxgl.sh}}

All that's left now is to create a login script which makes gnome use the 3D effects. In a terminal, type:

: {{cmduser|sudo gedit /usr/share/xsessions/xgl.desktop}}

Now, in this file paste:

<pre>
[Desktop Entry]
Encoding=UTF-8
Name=Xgl
Exec=/usr/local/bin/startxgl.sh
Icon=
Type=Application
</pre>

Save and close the file. Now type:

: {{cmduser|sudo gedit /usr/local/bin/start_beryl.sh}}

In this file, paste:

<pre>
#!/bin/bash
#
# Start beryl-manager within gnome-session
#
if [ `ps -A -o comm | grep -c '^Xgl$'` == "1" ]; then
DISPLAY=:1 beryl-manager
DISPLAY=:1 beryl-xgl
else echo "${0}: Error: beryl-manager not launched. Xgl not running?"
fi
</pre>

Now make the file executable:

: {{cmduser|sudo chmod a+x /usr/local/bin/start_beryl.sh}}

Now go to System - Preferences - Sessions, go to the Startup Programs tab, and click add, then type

: {{cmduser|/usr/local/bin/start_beryl.sh}}

Now, reboot your ThinkPad. When you come to the login screen, click the 'Sessions' button on the bottom left corner, and select XGL. login, et voila! beautiful 3D effects!

: Figure 11. Beryl's Cube effect
: [[Image:cube.jpg]]

If you have NetBeans installed, try launching it now. It probably won't work due to Beryl. Luckily, this is easily solved. Open a terminal and type:

: {{cmduser|sudo gedit /etc/environment}}

Then add the following line to the end of the file.

<pre>AWT_TOOLKIT="MToolkit"</pre>

Now save, close and reboot. Netbeans should now work!

===Problem: Can't add programs to session===

So you tried to add something to your startup programs, it shows up in the list, but it doesn't start up. You then launch the sessions program again, only to find your program has disappeared from the list. This problem is being caused by incorrect permissions in your home directory, and can happen on some occasions. To fix it, open a terminal and type the following:

: {{cmduser|sudo chown -R username:usergroup /home/username/.config/}}

Replace username with your username and usergroup with your group (by default, in Ubuntu your usergroup is the same as your username). Everything should be OK now!

===Problem: Virtual terminals not working===

One problem I had after installing the ATI drivers was that virtual terminals stopped working. Instead of seeing a console when pressing CTRL+ALT+F1...F6 I was seeing a yellow/orange garbled output. Luckily, solving this with ATI drivers is trivial. Open a terminal, and type:

: {{cmduser|sudo gedit /boot/grub/menu.lst}}

Find the line which says

<pre>#defoptions=quiet splash</pre>

and replace it with

<pre>#defoptions=quiet splash vga=791</pre>

Now, find the line which boots the kernel you are currently using, this is just under '## ## End Default Options ##. In the 'kernel' line, add:

<pre>vga=791</pre>

Before:

<pre>kernel /vmlinuz-2.6.17-10-generic root=/dev/sda7 ro quiet splash</pre>

After:

<pre>kernel /vmlinuz-2.6.17-10-generic root=/dev/sda7 ro quiet splash vga=791</pre>

Now save and exit the file, and reboot. Virtual terminals should now work. If you use Intel drivers, you're going to have to bite the bullet and remove the 'splash' keyword from both the defoptions and kernel lines. You'll lose the pretty bootup screen, but at least virtual terminals will work, which are important to recover a crashed system.

===Problem: I keep logging out!===

If you're using Beryl, and find that you keep getting logged out, you've just encountered one of Beryl's most annoying bugs. Shift+Backspace causes a logout. To fix this, open a terminal and type:

: {{cmduser|gedit /home/username/annoymenot.sh}}

Remember to replace 'username' with your username. Now, in this file type:

: {{cmduser|xmodmap -e "keycode 22 <nowiki>=</nowiki> BackSpace BackSpace Terminate_Server" }}

Save and close the file, and make it executable:

: {{cmduser|chmod 755 /home/username/annoymenot.sh}}

Now go to System - Preferences - Session, Startup Programs. Click add, and type

: {{cmduser|/home/username/annoymenot.sh}}

Logout and back in, problem solved! While you're at it, how about getting the start button to work? Go to System - Preferences - Keyboard - Layout Options - Alt/Win Key behaviour and select 'Super is mapped to Win keys (default)'.

===Desktop envy===

We're living in an age of desktop prettyness, and Linux can be just as pretty as MAC OS X or Vista. You've already got Beryl installed. Now go to Applications - Accesories - gDesklets. If the gDesklets entry is not there, make sure you install it, either using Synaptic or Automatix. Desklets are small programs you can add to your desktop, ala OS X's Deskbar or Vista's Sidebar. To make them start on boot, add gdesklets in System - Preferences - Sessions, Startup Programs.

Another cool program is cairo clock. Download it from http://macslow.thepimp.net/projects/cairo-clock/cairo-clock_0.3.2-1_i386.deb and install it by double-clicking. To make it start automatically, add it to your sessions as mentioned above. I've found the following command makes it work best for me:

<pre>cairo-clock -s -w 175 -g 175 -x 1219 -y 7 -t radium</pre>

Finally, make sure you click that Ruby icon in your notification area, it allows you to configure Beryl to do all sorts of cool stuff!

===Conclusion===

Well, that's about it! A dream Linux system on a dream laptop! Check out these cool technologies for an even better system:

* Beagle
* Tomboy
* Deskbar

===References===

* ATI on Ubuntu - https://help.ubuntu.com/community/BinaryDriverHowto/ATI
* Garbled Virtual Terminal Bug - https://launchpad.net/distros/ubuntu/+source/usplash/+bug/63558
* Beryl logout Bug - http://forum.beryl-project.org/viewtopic.php?p=1295&sid=6feedd09a7f01bca68feb05a5f2f033c
* Beryl Netbeans Bug - http://ubuntuforums.org/showthread.php?t=252594
* Beryl on Ubuntu - http://wiki.beryl-project.org/index.php/Install/Ubuntu/Edgy/XGL
* Home directory permissions bug - http://www.ubuntuforums.org/showthread.php?p=1789997
* gnome-bluetooth bug - https://launchpad.net/distros/ubuntu/+source/gnome-bluetooth/+bug/70718

Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60

2006-12-20T08:08:47Z

Ischg: /* The fingerprint reader */

[[User:Keithvassallo|Keithvassallo]] 14:39, 16 December 2006 (CET)

===Abstract===

This article describes how to get Ubuntu Linux 6.10 (Edgy) installed on an IBM/Lenovo ThinkPad T60. It's not meant to be a definite guide to installing Ubuntu (the Ubuntu Guide at http://www.ubuntuguide.org does a very good job of that). This article is meant to describe how to get most of the ThinkPad features working on Ubuntu system. It also discusses how to get Multimedia, some cool-looking effects such as Beryl, gDesklets and similar working on Ubuntu. Finally, we discuss some common problems encountered on Ubuntu and ThinkPads alike.

===My ThinkPad===

Although this guide should work on most recent ThinkPads, I cannot guarantee that. These are the specifications of my machine. The closer your specs are, the greater the chance of success.

: Figure 1. ThinkPad T60 2007, complete with Tux sticker :-)
: [[Image:thinkpad.jpg]]

* Lenovo ThinkPad T60 2007.
* Intel Centrino Duo T2400 / 1.83 GHz.
* Mobile Intel 945PM Express Chipset.
* Intel Wireless LAN.
* Integrated Bluetooth.
* ATI Mobility Radeon X1400 - PCI Express x16, 128MB dedicated RAM.
* 100 GB - Serial ATA-150 Hard Drive.
* 15' TFT Active Matrix Display (1400x1050).

That's basically all you need to know. As far as I know, all other features are common to all ThinkPads manufactured by Lenovo since they acquired IBM's computer business.

===Why Ubuntu? (or rather, Why not SUSE?)===

In June 2006, Lenovo announced it would be shipping ThinkPad T60p laptops with SUSE Linux Enterprise Desktop (SLED) 10 pre-installed, since SLED apparently supports all of the features of the T60p. I contacted my local IBM supplier, who said that Lenovo were no longer manufacturing the T60p, since the company which was making the displays went out of business. This meant I could not get a T60p with SLED pre-installed. I decided to go for the T60 2007, which is the closest thing I could find to the T60p. This comes with Windows XP Professional pre-installed.

I first tried to get SLED installed on the T60. Although it did indeed install, and most features worked, I soon got bored of SLED. Firstly, SLED uses Gnome 2.12, which is by now ancient. Secondly, although the Lenovo utilities do work on SLED, they only work well if you use KDE as your defauly desktop environment, which is a pity since I'm a Gnome user. The utilities were very unstable to me too. Finally, what made me give up SLED was the usual problem - it's an RPM based distribution. Once you start using Debian derivatives, with their apt based installer, you won't want to go back. That's when I decided to try Ubuntu, and have not regretted it since.

===What Works?===

* Ubuntu and all programs it comes with.
* Most of the function keys, except the ones mentioned below
* The fingerprint reader.
* The ATI proprietary graphics drivers.
* Suspend to RAM (Sleep) and Suspend to Disk (Hibernate).
* Brightness, Volume and Mute with OSD (On-Screen Display).
* ThinkLight, TrackPoint II and the touchpad.

===What Doesn't Work? (Known Issues)===

* FN+F8, FN+F9, FN+ZOOM.
* The BACK and FORWARD buttons (next to the cursor keys).
* The ThinkVantage button (in Linux, still works on boot).
* Sending files to Bluetooth devices via GUI.

There are probably ways and means to get the offending buttons to work, I've tried several fora but none seem to address my exact problem. I'll update this article should I find out anything.

===First Things First - Creating a Windows Recovery Disc===

If you've purchased a T60, chances are it came with Windows XP Professional. The other option is for you to have FreeDOS installed, in which case you can skip this section. You could remove the Windows partition altogether, and reserve your ThinkPad for Linux, but that's not the route I've chosen. The ThinkVantage utilities in Windows allow you to do a lot of cool things, such as set-up a boot-up fingerprint security scan. You can't do this from Linux (as far as I know) so it's best to leave the Windows partition in place. So, boot your ThinkPad and complete the Windows XP setup (which asks you to add a user account and enroll yourself using the ThinkVantage Client Security Solution). While you're there, use the ThinkVantage productivy centre to enroll your fingerprint (I suggest enrolling more than one) and make sure you check the option to require a fingerprint scan on boot (not for security, for geek points). When you reboot, press ESC or F2 to get to BIOS, and make sure you check the option to require a supervisor password. This will make your ThinkPad prompt you for your fingerprint when you power it up.

: Figure 2. Configuring fingerprint security from Windows
: [[Image:winprint.jpg]]

Now that's working, you should create a recovery DVD using the ThinkVantage recovery utilities. This will allow you to recover your Windows installation should you manage to screw your partitions up in the following stages. I highly recommend you do this, as Lenovo does not provide Windows XP CDs with this Laptop - so the hard disk partition is all you've got. Once this is done, we're ready to install Ubuntu!

: Figure 3. Creating recovery discs from Windows
: [[Image:recovery.jpg]]

===Getting Ubuntu installed===

Download the latest Edgy live CD from the Ubuntu website, you can find a list of mirrors at http://www.ubuntu.com/products/GetUbuntu/download#currentrelease. You may also try Kubuntu, Edubuntu or any of it's derivatives, but I'll stick with Ubuntu here for simplicity's sake. Once that's downloaded, burn the ISO to disc using any program of your choice (If this is your first Linux experience and you're using Windows, try using Nero - http://www.nero.com).

Once the burning process is complete, reboot your machine ensuring that the Ubuntu CD is in the drive. You should see an Ubuntu menu. If you don't, your BIOS is not set to boot from CD. Reboot your ThinkPad and change the boot order from BIOS (by default ThinkPads boot from CD-ROM before the hard disk, so this is probably not necessary). Once the menu shows up, select 'Start or install Ubuntu' and let it boot. This will take a while as everything is loaded from CD. You should eventually end up in a Gnome desktop. If you see an error about the Gnome Settings Daemon not being able to load, simply ignore it, as this is not necessary for now. For the purposes of the installation, it's best if you have a wired ethernet connection, as it's unlikely the wireless network card will work until we boot into our installed Ubuntu system.

: Figure 4. Select the first option to start Ubuntu
: [[Image:boot.jpg]]

Double-Click on the 'install' icon on the Desktop to start installation. The installation should be pretty straight-forward. If you need additional help, check out the walk-through with screen-shots at http://www.debianadmin.com/ubuntu-edgy-eft-desktop-installation-with-screenshots.html. The only stage at which we need to make changes is the partitioning stage. This to make sure we preserve our Windows partition, and the IBM vendor_diag partition which allows recovery of the laptop when things go hay-wire. In the 'Prepare disk space' section of the installer, select the third option, 'Manually edit partition table'. A bar will be displayed showing your existing partitions. If you have Windows installed you will see two partitions. The first is a 4.89 GB IBM Vendor Diagnostic partition, which we do not want to touch. The second will be your Windows partition, which will fill the rest of the disk. Click on this partition, Then click the 'Resize/Move' button. I resized my Windows partition to 24 GB. This is enough to accommodate the 10 GB already in use on that partition, as well as giving Windows another 14 GB of free space. 6 GB of free space would probably be enough though.

Now it's time to create partitions for Linux. You need at least two partitions; a swap partition which should be roughly double the amount of RAM you have, and a root partition to install Linux. I opted for four partitions, as follows:

<table border=1>
<tr><td>'''Purpose'''</td><td>'''Size'''</td><td>'''File-System'''</td></tr>
<tr><td>Swap</td><td>2 GB</td><td>swap</td></tr>
<tr><td>/boot</td><td>5 GB</td><td>ext3</td></tr>
<tr><td>/ (root)</td><td>20 GB</td><td>ext3</td></tr>
<tr><td>/home</td><td>37.25 GB (what's left of the disk)</td><td>ext3</td></tr>
</table>

To create these paritions, click on the 'New' button and select 'Extended Partition' in the 'create as' drop-down list. Leave all other settings as-is, and click 'Add'. Now, click on the newly created partition, and create each of the partitions you want to create, simply specify the size of the partition in the 'New Size (MiB)' text box. To convert GB to MiB, multiply by 1024. So for your swap partition you should specify a size of 2048. Repeat until you have created all the required partitions. If you follow my parition layout, the partition editor should look something like Figure 5.

: Figure 5. Our partitions, ready to be created
: [[Image:partitioning.jpg]]

You will not see mount-points in your diagram, because the screen-shot above was taken after they were assigned, but you should get the general idea. After this screen, you will be asked to assign mount-points to the partitions you have just created. If you created the partitions in the same order I did, you can assign mount points as I have (i.e. /dev/sda5 for swap, /dev/sda6 for /boot, /dev/sda7 for /, /dev/sda8 for /home). Additionally, I mounted my Windows partition as /media/sda1 and my IBM Vendor Diagnostic partition as /media/sda2. These are optional. After this step, continue installation as normal. When the installation is complete, click the 'reboot' button to restart into your fresh Ubuntu System.

When booting, the GRUB boot-loader will be displayed, asking you what you want to load. You will probably see four options. The first two being Ubuntu Linux and Ubuntu Linux recovery mode (showing the kernel version). The other two will be Microsoft Windows XP, and 'Other Windows XP/2000/NT' partition. This is your IBM Vendor Diagnostic partition, which is based on the Windows kernel, apparently. Select the first entry to boot Ubuntu. The next time you boot Windows, it will bring up a chkdsk screen. This is entirely normal and happens because we have resized the Windows partition. Make sure you do not skip this check and let it complete.

===Wireless LAN===

The first thing we should do is to get wireless networking working. Luckily, getting the Centrino wireless LAN chip working in Ubuntu is quite easy, if you use the gnome-network-manager applet. Just go to System - Administration - Synaptic Package Manager. Then click 'Search' and set the 'look-in' field to 'name'. In the 'Search' text box type:

<pre>network-manager</pre>

: Figure 6. Installing the network manager applet
: [[Image:networkmanager.jpg]]

Click on the box beside 'network-manager' and click 'Mark for installation'. Do the same for 'network-manager-gnome'. Once installed, reboot your thinkpad. An applet will show up in the gnome notification area. Click on it, and a list of detected wireless networks will be displayed. Simply click on one of them, enter any authentication details necessary, and you'll be connected to the wireless network.

: Figure 7. gnome-network-manager showing available wireless networks
: [[Image:available-accesspoints.jpg]]

Note! Not all versions of the T60 has the Intel Wireless LAN as described above. Run lspci from the command line and look for details of your wifi card. E.g.:

03:00.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)

suggest you have a different wifi card. Read this forum thread http://ubuntuforums.org/showthread.php?t=38972

running:
# dmesg | grep hal

may yield output like this, which apparently suggests the hardware abstraction layer is in place.
[17179590.420000] ath_hal: module license 'Proprietary' taints kernel.
[17179590.424000] ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)

If not, or if the output contains "HAL Status 13" it apparently suggests your card is not supported by the current drivers, and you need to upgrade.

===Installing the ATI display drivers===

If your ThinkPad has an Intel graphics adapter, you should skip this section as Ubuntu installs the best driver automatically. Ubuntu does not install the ATI proprietary drivers by default because they are, er, proprietary. Luckily, installing them is easy enough. Open a terminal (Applications - Accessories - Terminal) and type the following:

: {{cmduser| sudo apt-get update}}
: {{cmduser| sudo apt-get install xorg-driver-fglrx fglrx-control}}

Now we make sure the proprietary driver is not disabled by the kernel. Type the following, and remove any lines referring to fglrx

: {{cmduser|sudo gedit /etc/default/linux-restricted-modules-common}}

An alternative to gedit (Gnome) is nano (sudo nano -w /etc...) for a CLI editor.

Finally, we need to configure the X server to use the ATI drivers. Type the following:

: {{cmduser|sudo depmod -a}}
: {{cmduser|sudo aticonfig --initial}}
: {{cmduser|sudo aticonfig --overlay-type<nowiki>=</nowiki>Xv}}

One last thing. In order to correct a very common problem of getting a jerky video display, type the following:

: {{cmduser|sudo gedit /etc/X11/xorg.conf}}

Scroll to the end of the file, and add the text below.

<pre>
Section "Extensions"
Option "Composite" "0"
EndSection
</pre>

Save the file and exit. Now, to apply the changes either press CTRL+ALT+Backspace or reboot. The resolution should have switched to 1400x1050 and everything should look prettier and render faster. Just to make sure everything is working, open up a terminal and type

: {{cmduser|fglrxinfo}}

This should display:

<pre>
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Mobility Radeon X1400 Generic
OpenGL version string: 2.0.6011 (8.28.8)
</pre>

The above is what I get on my ThinkPad, and you should see something similar. As long as you see your graphics card model listed, everything should be OK. If, instead, you see a bunch of lines containing 'Mesa' then you have a problem. In that case, I recommend consulting https://help.ubuntu.com/community/BinaryDriverHowto/ATI and the Ubuntu forums at http://ubuntuforums.org

===The fingerprint reader===

Although IBM does not officially support it, the fingerprint reader does in fact work with most Linux distributions. Getting it to work with Ubuntu can be a bit of a pain, but it does work. Basically, a bioAPI plugin is provided for PAM. PAM-aware applications such as GDM and gnome-screensaver will then automatically use the fingerprint reader, which is uber cool. Anyway, enough theory, I've probably lost the newbies amongst you already. Go to http://www.qrivy.net/~michael/temp/ and download the latest bioapi package (at the time of writing, bioapi_1.2.3_i386.deb). When asked, tell Firefox to open the file with the GDebi package installer.

That will install bioAPI. What we need now is the driver for our fingerprint device, which is manufactured by UPEK. Go to http://www.upek.com/support/dl_linux_bsp.asp and download the latest version, currently UPEK_BSP_LIN_1.0.zip. Extract this file, then open a terminal (and don't close it until I say so).

: {{cmduser|cd /path/to/where/you/extracted/the/file}}
: {{cmduser|sudo bash}}
: {{cmdroot|sh install.sh /usr/lib}}

Now we need to assign the right permissions so non-root applications can use the driver:

: {{cmdroot|addgroup --system bioapi}}
: {{cmdroot|addgroup --system usbfs}}
: {{cmdroot|adduser yourusername bioapi}}
: {{cmdroot|adduser yourusername usbfs}}
: {{cmdroot|chown -R root:bioapi /usr/var/bioapi/}}
: {{cmdroot|chmod -R 770 /usr/var/bioapi/}}
: {{cmdroot|chown -R root:usbfs /proc/bus/usb}}
: {{cmdroot|chmod -R g+X /proc/bus/usb}}

Of course, replace 'yourusername' with the username you use to login. Now, we need to set the usb file system (usbfs) to be usable by users in the usbfs group. To do this, we need to determine the group ID of the usbfs group. Type the following:

: {{cmdroot|cat /etc/group <nowiki>|</nowiki> grep usbfs <nowiki>|</nowiki> cut -d':' -f 3}}

In my case the number is 116, it might be different for you. Now, open the file /etc/fstab:

: {{cmdroot|gedit /etc/fstab}}

and type the following:

<pre>none /proc/bus/usb usbfs defaults,devgid=116,devmode=0660,busgid=116,busmode=0770,listgid=116,listmode=0660 0 0</pre>

Please type the above code in one line in your file. Remember to replace 116 if you got a different number with the previous cat command. The last permission-related thing we need to fool around with is UDEV. Open the udev permissions file

: {{cmdroot|gedit /etc/udev/rules.d/40-permissions.rules}}

and find the line:

<pre>SUBSYSTEM=="usb_device", MODE="0664"</pre>

It's line 65 in my file. Change it so it looks like this:

<pre>SUBSYSTEM=="usb_device", MODE="0660", GROUP="usbfs"</pre>

Now we need to enroll our fingerprint with the system. To do this, we need a utility called Sample, which is only distributed in source-code form with the driver. This is great, only I couldn't get it to compile on Ubuntu. Luckily, there is a binary version available from one of the earlier releases of the driver (beta 2). To get this, download it from ftp://linux:Tuc-nak3@delta.upek.com/TFMESS_BSP_LIN_1.0beta2.zip. Now, extract the file and type:

: {{cmdroot|cd /path/to/where/you/extracted/the/archive}}
: {{cmdroot|cd NonGUI_sample}}
: {{cmdroot|chmod a+x Sample}}
: {{cmdroot|./Sample}}

Press (e) to enroll a new user, and enter your username when asked for the user ID. You will be asked to swipe your finger three times. Now press (v) and swipe your finger, a green check should be displayed showing you have successfully authenticated.

: Figure 8. The fingerprint swipe prompt
: [[Image:touchchip.jpg]]

Wonderful! Now, quit the application (q) and type exit to become a normal user. A file called yourusername.bir should have been created, copy this to your home directory:

: {{cmdroot|cp yourusername.bir /home/yourusername/}}

You can now close the terminal window. The next step is to install the BioAPI plug-in for PAM, and to make applications use the plugin. So, get the pam_bioapi plugin from http://www.nax.cz/pub/bioapi/pam_bioapi/pam-bioapi_0.3.0.tar.gz and extract it. Now open a terminal and type:

Comment: you will have to install some libraries in order to be able to compile the plugin

: {{cmduser|sudo apt-get install build-essential}}
: {{cmduser|sudo apt-get install libpam0g-dev}}

Now, you can compile and install the plugin

: {{cmduser|cd /path/to/where/you/extracted/the/arcive}}
: {{cmduser|./configure --libdir<nowiki>=</nowiki>/lib --enable-file-store && make}}
: {{cmduser|sudo make install}}

That's installed the plugin. Now, open a terminal and type the following scary commands: (Note: The line starting 'SERIAL=' and the line following it should be in the same line). {{Todo|comment from a user of this page: the third command is not displayed correctly (issue of wrapping the "<nowiki>|</nowiki>" character).}}

: {{cmduser|cd ~}}
: {{cmduser|sudo bash}}
: {{cmdroot|SERIAL=`BioAPITest | sed -ne "/Fingerprint/{n;n;s/^.*: $.\{9\}$$.\{4\}$$.\{4\}$$.\{4\}$$.*$/\1-\2-\3-\4-\5/gp}"`}}
: {{cmdroot|mkdir -p /etc/bioapi/pam/$SERIAL}}
: {{cmdroot|cp yourusername.bir /etc/bioapi/pam/$SERIAL}}
: {{cmdroot|exit}}

Phew. Now, to make applications actually use the fingerprint reader. Open a terminal window, and type:

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

Delete everything in the file, and paste this instead:

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

Save and close the file. That will make all PAM-aware applications use the fingerprint reader. Unfortunately, this also includes sudo. Since sudo is a command line application, it will display prompts in a terminal for you to swipe your finger, which is all well and good. The problem with this is that many Ubuntu administrative applications (such as Synaptic) use gksu to present a graphical front-end to sudo, which will output messages on the command line which you'll never see. Result? Administrative programs won't work from the gnome menu. The solution is to make sudo use the good old password. Open a terminal and type:

: {{cmduser|sudo gedit /etc/pam.d/sudo}}

Delete everything in the file, and instead paste:

<pre>
#%PAM-1.0

#@include common-auth
auth required pam_unix.so nullok_secure
@include common-account
</pre>

Now, save the file and close it, and reboot your system. GDM will ask you for a username, and then show a pretty prompt where you can scan your fingerprint! Same goes for gnome-screensaver when you set it to lock. Sometimes gnome-screensaver will not display the prompt, but you should still swipe your finger and be able to log back in.

===Bluetooth with Mobile Phones/PDAs===

Rather strangely, Ubuntu seems to have taken a step backwards with Bluetooth useability in Edgy. What worked out of the box with Dapper, now requires configuratio. First, open System - Preferences - Sessions and go to the Startup Programs tab. Then, find the entry labelled 'bt-applet --sm-disable'. Highlight it and click disable. Click add and in the command field type 'bt-applet'. Repeat this process, adding an entry for 'gnome-obex-server'. Now, open Synaptic Package Manager (System - Administration - Synaptic Package Manager) and click Search. Type 'gnome-bluetooth' to find the package, then mark it for installation. Now repeat this process for 'bluez-passkey-gnome'. Click apply to make changes.

Now that everything is installed, log-out of Gnome and log back in again. From your phone/PDA, search for devices untill you see your ThinkPad (the hostname will be displayed). Pair with the device. When asked for a passkey, enter 1234, which is the default. If you want to change your passkey (and you should), open a terminal and type:

: {{cmduser|sudo gedit /etc/bluetooth/hcid.conf}}

Find the line which says 'Default PIN for incoming connections' and change the PIN on the line beneath it:

<pre>
# Default PIN code for incoming connections
passkey "4017";
</pre>

Save and close the file, then type:

: {{cmduser|sudo /etc/init.d/bluetooth restart}}

You will now be able to use your new PIN code. To send files from your device to the ThinkPad, simply select the file you want to send and click Send Via Bluetooth (or whatever option your device presents). A dialog will pop-up in Gnome showing you a new file has been received.

: Figure 9. Gnome informing us that a file has been received
: [[Image:bluetooth.jpg]]

Sending files from your ThinkPad to your device requires more effort. The way it should work is that you right-click on a file, click send to, then make sure 'Bluetooth (OBEX)' is selected. Your device should be displayed and you could just click send. Unfortunately, due to a bug in gnome-bluetooth (described in https://launchpad.net/distros/ubuntu/+source/gnome-bluetooth/+bug/70718) this method does not work. If it does work for you, the bug has been solved and you can skip the rest of this section.

Your only other option is to use the command line to send files to your device. Open a terminal, then type:

: {{cmduser|hcitool scan}}

A list of detected bluetooth devices will be shown, for example, my output shows the following:

<pre>
Scanning ...
00:09:DD:60:02:EB Photosmart 8100 series
00:14:A7:99:3C:1F ThElInK
</pre>

The first field is the MAC address of the device, the second is the name of the device. In this case my bluetooth printer and mobile phone (ThElInK) were detected. In order to send files to my phone, I use:

: {{cmduser|gnome-obex-send -d 00:14:A7:99:3C:1F myPicture.jpg}}

Replace the MAC address with that of your device and myPicture.jpg with the file you want to send.

===TrackPoint Scrolling===

By default you can use the right and bottom edges of your touchpad to scroll through documents. If you use the TrackPoint instad of the touchpad (and believe me, you should), you'll find that scrolling is disabled by default. To enable it, open a terminal and type:

: {{cmduser|sudo gedit /etc/X11/xorg.conf}}

Now find the entry for your TrackPoint device. In my configuration file, the TrackPoint entry is the first mouse entry, after the keyboard entry, and looks something like this:

<pre>
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection
</pre>

Right after this entry is my touchpad entry. My entry is on line 66, but yours may be different. Now, add the follwing two options in that InputDevice section:

<pre>
Option "EmulateWheel" "on"
Option "EmulateWheelButton" "2"
</pre>

Save and exit the file. Restart your ThinkPad (or logout, and press CTRL-ALT-BACKSPACE). You should now be able to scoll by holding down the middle button for your TrackPoint and using the TrackPoint to scroll.

===Getting Multimedia to Work===

Due to patents and similar legal crap, Ubuntu will not play most media files by default. You also won't get browser plugins for multimedia. Luckily, this is easily fixed. Open a terminal and type the following:

: {{cmduser|sudo cp /etc/apt/sources.list /etc/apt/sources.list.backup}}
: {{cmduser|sudo gedit /etc/apt/sources.list}}

Delete everything in the file, and instead paste the following:

<pre>
deb-src http://archive.ubuntu.com/ubuntu edgy main restricted universe multiverse
#deb http://archive.ubuntu.com/ubuntu edgy-proposed main restricted universe multiverse

## MAJOR BUG FIX UPDATES produced after the final release
deb-src http://archive.ubuntu.com/ubuntu edgy-updates main restricted universe multiverse

## UBUNTU SECURITY UPDATES
deb http://security.ubuntu.com/ubuntu edgy-security main restricted universe multiverse
deb-src http://security.ubuntu.com/ubuntu edgy-security main restricted universe multiverse

## BACKPORTS REPOSITORY (Unsupported. May contain illegal packages. Use at own risk.)
#deb http://archive.ubuntu.com/ubuntu edgy-backports main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu edgy-backports main restricted universe multiverse

## PLF REPOSITORY
deb http://packages.freecontrib.org/ubuntu/plf edgy-plf free
deb-src http://packages.freecontrib.org/ubuntu/plf edgy-plf free
deb http://packages.freecontrib.org/ubuntu/plf edgy-plf non-free
deb-src http://packages.freecontrib.org/ubuntu/plf edgy-plf non-free

## CANONICAL COMMERCIAL REPOSITORY (Hosted on Canonical servers, not Ubuntu
## servers. RealPlayer10, Opera, DesktopSecure and more to come.)
deb http://archive.canonical.com/ubuntu edgy-commercial main

## Listen
#deb http://theli.free.fr/packages/ edgy listen

## Automatix repo
deb http://www.getautomatix.com/apt edgy main
</pre>

Now, open a terminal and type the following:

: {{cmduser|wget http://packages.freecontrib.org/ubuntu/plf/12B83718.gpg -O- | sudo apt-key add -}}
: {{cmduser|wget http://www.getautomatix.com/apt/key.gpg.asc}}
: {{cmduser|gpg --import key.gpg.asc}}
: {{cmduser|gpg --export --armor 521A9C7C | sudo apt-key add -}}
: {{cmduser|sudo apt-get update}}
: {{cmduser|sudo apt-get install automatix2}}
: {{cmduser|wget http://easyubuntu.freecontrib.org/files/easyubuntu-3.023.tar.gz}}
: {{cmduser|tar -zxf easyubuntu-3.023.tar.gz}}
: {{cmduser|cd easyubuntu}}
: {{cmduser|cp packagelist-dapper.pot packagelist-edgy.pot}}
: {{cmduser|cp packagelist-dapper.xml packagelist-edgy.xml}}
: {{cmduser|sudo python easyubuntu.in}}

Don't worry if you get errors from the Ubuntu PLF repository. PLF mirrors are about as stable as wild bull in a farm full of cows. Select what you want to install from the resulting window. Make sure you do not select the totem-mozilla plugin, as this just doens't work, for me at least. When EasyUbuntu has finished installing packages, you should be returned to a terminal, which you can close. Now go to Applications - System Tools - Automatix. Read and agree to the warning. Check what you want to install. Make sure you check 'Mplayer and FF plugin'. When ready, click the 'install' button. That should get multimedia working nicely.

: Figure 10. The Automatix user interface
: [[Image:automatix.jpg]]

===Beryl - fancy 3D desktop===

MAC OS X has Aqua and Windows Vista has Aero. Well, Linux has XGL/Beryl which can get effects which are as good looking (or sometimes better!) than the former two. Installing Beryl on Ubuntu is not that hard. First, open a terminal and type the following:

: {{cmduser|sudo gedit /etc/apt/sources.list}}

At the end of the file, append the following:

<pre>
##Beryl
deb http://ubuntu.beryl-project.org/ edgy main
</pre>

Save and close the file. Now type:

: {{cmduser|wget http://beryl-mirror.lupine.me.uk/1609B551.gpg -O- | sudo apt-key add -}}
: {{cmduser|sudo apt-get update}}

ATI Users Only: type

: {{cmduser|sudo apt-get install xserver-xgl}}

Now, to install beryl:

: {{cmduser|sudo apt-get install beryl emerald-themes}}

To make Ubuntu use the 3D effects. Open a terminal:

: {{cmduser|sudo gedit /usr/local/bin/startxgl.sh}}

In that file, paste the following if you use an ATI card:

<pre>
#!/bin/sh
Xgl -fullscreen :1 -ac -br -accel glx:pbuffer -accel xv:pbuffer &
sleep 4
export DISPLAY=:1
exec gnome-session
</pre>

If you use an Intel card, paste the following instead:

<pre>
#!/bin/sh
beryl-manager
sleep 4
exec gnome-session
</pre>

Save the file and close. Now we need to make the file executable:

: {{cmduser|sudo chmod a+x /usr/local/bin/startxgl.sh}}

All that's left now is to create a login script which makes gnome use the 3D effects. In a terminal, type:

: {{cmduser|sudo gedit /usr/share/xsessions/xgl.desktop}}

Now, in this file paste:

<pre>
[Desktop Entry]
Encoding=UTF-8
Name=Xgl
Exec=/usr/local/bin/startxgl.sh
Icon=
Type=Application
</pre>

Save and close the file. Now type:

: {{cmduser|sudo gedit /usr/local/bin/start_beryl.sh}}

In this file, paste:

<pre>
#!/bin/bash
#
# Start beryl-manager within gnome-session
#
if [ `ps -A -o comm | grep -c '^Xgl$'` == "1" ]; then
DISPLAY=:1 beryl-manager
DISPLAY=:1 beryl-xgl
else echo "${0}: Error: beryl-manager not launched. Xgl not running?"
fi
</pre>

Now make the file executable:

: {{cmduser|sudo chmod a+x /usr/local/bin/start_beryl.sh}}

Now go to System - Preferences - Sessions, go to the Startup Programs tab, and click add, then type

: {{cmduser|/usr/local/bin/start_beryl.sh}}

Now, reboot your ThinkPad. When you come to the login screen, click the 'Sessions' button on the bottom left corner, and select XGL. login, et voila! beautiful 3D effects!

: Figure 11. Beryl's Cube effect
: [[Image:cube.jpg]]

If you have NetBeans installed, try launching it now. It probably won't work due to Beryl. Luckily, this is easily solved. Open a terminal and type:

: {{cmduser|sudo gedit /etc/environment}}

Then add the following line to the end of the file.

<pre>AWT_TOOLKIT="MToolkit"</pre>

Now save, close and reboot. Netbeans should now work!

===Problem: Can't add programs to session===

So you tried to add something to your startup programs, it shows up in the list, but it doesn't start up. You then launch the sessions program again, only to find your program has disappeared from the list. This problem is being caused by incorrect permissions in your home directory, and can happen on some occasions. To fix it, open a terminal and type the following:

: {{cmduser|sudo chown -R username:usergroup /home/username/.config/}}

Replace username with your username and usergroup with your group (by default, in Ubuntu your usergroup is the same as your username). Everything should be OK now!

===Problem: Virtual terminals not working===

One problem I had after installing the ATI drivers was that virtual terminals stopped working. Instead of seeing a console when pressing CTRL+ALT+F1...F6 I was seeing a yellow/orange garbled output. Luckily, solving this with ATI drivers is trivial. Open a terminal, and type:

: {{cmduser|sudo gedit /boot/grub/menu.lst}}

Find the line which says

<pre>#defoptions=quiet splash</pre>

and replace it with

<pre>#defoptions=quiet splash vga=791</pre>

Now, find the line which boots the kernel you are currently using, this is just under '## ## End Default Options ##. In the 'kernel' line, add:

<pre>vga=791</pre>

Before:

<pre>kernel /vmlinuz-2.6.17-10-generic root=/dev/sda7 ro quiet splash</pre>

After:

<pre>kernel /vmlinuz-2.6.17-10-generic root=/dev/sda7 ro quiet splash vga=791</pre>

Now save and exit the file, and reboot. Virtual terminals should now work. If you use Intel drivers, you're going to have to bite the bullet and remove the 'splash' keyword from both the defoptions and kernel lines. You'll lose the pretty bootup screen, but at least virtual terminals will work, which are important to recover a crashed system.

===Problem: I keep logging out!===

If you're using Beryl, and find that you keep getting logged out, you've just encountered one of Beryl's most annoying bugs. Shift+Backspace causes a logout. To fix this, open a terminal and type:

: {{cmduser|gedit /home/username/annoymenot.sh}}

Remember to replace 'username' with your username. Now, in this file type:

: {{cmduser|xmodmap -e "keycode 22 <nowiki>=</nowiki> BackSpace BackSpace Terminate_Server" }}

Save and close the file, and make it executable:

: {{cmduser|chmod 755 /home/username/annoymenot.sh}}

Now go to System - Preferences - Session, Startup Programs. Click add, and type

: {{cmduser|/home/username/annoymenot.sh}}

Logout and back in, problem solved! While you're at it, how about getting the start button to work? Go to System - Preferences - Keyboard - Layout Options - Alt/Win Key behaviour and select 'Super is mapped to Win keys (default)'.

===Desktop envy===

We're living in an age of desktop prettyness, and Linux can be just as pretty as MAC OS X or Vista. You've already got Beryl installed. Now go to Applications - Accesories - gDesklets. If the gDesklets entry is not there, make sure you install it, either using Synaptic or Automatix. Desklets are small programs you can add to your desktop, ala OS X's Deskbar or Vista's Sidebar. To make them start on boot, add gdesklets in System - Preferences - Sessions, Startup Programs.

Another cool program is cairo clock. Download it from http://macslow.thepimp.net/projects/cairo-clock/cairo-clock_0.3.2-1_i386.deb and install it by double-clicking. To make it start automatically, add it to your sessions as mentioned above. I've found the following command makes it work best for me:

<pre>cairo-clock -s -w 175 -g 175 -x 1219 -y 7 -t radium</pre>

Finally, make sure you click that Ruby icon in your notification area, it allows you to configure Beryl to do all sorts of cool stuff!

===Conclusion===

Well, that's about it! A dream Linux system on a dream laptop! Check out these cool technologies for an even better system:

* Beagle
* Tomboy
* Deskbar

===References===

* ATI on Ubuntu - https://help.ubuntu.com/community/BinaryDriverHowto/ATI
* Garbled Virtual Terminal Bug - https://launchpad.net/distros/ubuntu/+source/usplash/+bug/63558
* Beryl logout Bug - http://forum.beryl-project.org/viewtopic.php?p=1295&sid=6feedd09a7f01bca68feb05a5f2f033c
* Beryl Netbeans Bug - http://ubuntuforums.org/showthread.php?t=252594
* Beryl on Ubuntu - http://wiki.beryl-project.org/index.php/Install/Ubuntu/Edgy/XGL
* Home directory permissions bug - http://www.ubuntuforums.org/showthread.php?p=1789997
* gnome-bluetooth bug - https://launchpad.net/distros/ubuntu/+source/gnome-bluetooth/+bug/70718

Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60

2006-12-20T07:53:28Z

Ischg: /* The fingerprint reader */

[[User:Keithvassallo|Keithvassallo]] 14:39, 16 December 2006 (CET)

===Abstract===

This article describes how to get Ubuntu Linux 6.10 (Edgy) installed on an IBM/Lenovo ThinkPad T60. It's not meant to be a definite guide to installing Ubuntu (the Ubuntu Guide at http://www.ubuntuguide.org does a very good job of that). This article is meant to describe how to get most of the ThinkPad features working on Ubuntu system. It also discusses how to get Multimedia, some cool-looking effects such as Beryl, gDesklets and similar working on Ubuntu. Finally, we discuss some common problems encountered on Ubuntu and ThinkPads alike.

===My ThinkPad===

Although this guide should work on most recent ThinkPads, I cannot guarantee that. These are the specifications of my machine. The closer your specs are, the greater the chance of success.

: Figure 1. ThinkPad T60 2007, complete with Tux sticker :-)
: [[Image:thinkpad.jpg]]

* Lenovo ThinkPad T60 2007.
* Intel Centrino Duo T2400 / 1.83 GHz.
* Mobile Intel 945PM Express Chipset.
* Intel Wireless LAN.
* Integrated Bluetooth.
* ATI Mobility Radeon X1400 - PCI Express x16, 128MB dedicated RAM.
* 100 GB - Serial ATA-150 Hard Drive.
* 15' TFT Active Matrix Display (1400x1050).

That's basically all you need to know. As far as I know, all other features are common to all ThinkPads manufactured by Lenovo since they acquired IBM's computer business.

===Why Ubuntu? (or rather, Why not SUSE?)===

In June 2006, Lenovo announced it would be shipping ThinkPad T60p laptops with SUSE Linux Enterprise Desktop (SLED) 10 pre-installed, since SLED apparently supports all of the features of the T60p. I contacted my local IBM supplier, who said that Lenovo were no longer manufacturing the T60p, since the company which was making the displays went out of business. This meant I could not get a T60p with SLED pre-installed. I decided to go for the T60 2007, which is the closest thing I could find to the T60p. This comes with Windows XP Professional pre-installed.

I first tried to get SLED installed on the T60. Although it did indeed install, and most features worked, I soon got bored of SLED. Firstly, SLED uses Gnome 2.12, which is by now ancient. Secondly, although the Lenovo utilities do work on SLED, they only work well if you use KDE as your defauly desktop environment, which is a pity since I'm a Gnome user. The utilities were very unstable to me too. Finally, what made me give up SLED was the usual problem - it's an RPM based distribution. Once you start using Debian derivatives, with their apt based installer, you won't want to go back. That's when I decided to try Ubuntu, and have not regretted it since.

===What Works?===

* Ubuntu and all programs it comes with.
* Most of the function keys, except the ones mentioned below
* The fingerprint reader.
* The ATI proprietary graphics drivers.
* Suspend to RAM (Sleep) and Suspend to Disk (Hibernate).
* Brightness, Volume and Mute with OSD (On-Screen Display).
* ThinkLight, TrackPoint II and the touchpad.

===What Doesn't Work? (Known Issues)===

* FN+F8, FN+F9, FN+ZOOM.
* The BACK and FORWARD buttons (next to the cursor keys).
* The ThinkVantage button (in Linux, still works on boot).
* Sending files to Bluetooth devices via GUI.

There are probably ways and means to get the offending buttons to work, I've tried several fora but none seem to address my exact problem. I'll update this article should I find out anything.

===First Things First - Creating a Windows Recovery Disc===

If you've purchased a T60, chances are it came with Windows XP Professional. The other option is for you to have FreeDOS installed, in which case you can skip this section. You could remove the Windows partition altogether, and reserve your ThinkPad for Linux, but that's not the route I've chosen. The ThinkVantage utilities in Windows allow you to do a lot of cool things, such as set-up a boot-up fingerprint security scan. You can't do this from Linux (as far as I know) so it's best to leave the Windows partition in place. So, boot your ThinkPad and complete the Windows XP setup (which asks you to add a user account and enroll yourself using the ThinkVantage Client Security Solution). While you're there, use the ThinkVantage productivy centre to enroll your fingerprint (I suggest enrolling more than one) and make sure you check the option to require a fingerprint scan on boot (not for security, for geek points). When you reboot, press ESC or F2 to get to BIOS, and make sure you check the option to require a supervisor password. This will make your ThinkPad prompt you for your fingerprint when you power it up.

: Figure 2. Configuring fingerprint security from Windows
: [[Image:winprint.jpg]]

Now that's working, you should create a recovery DVD using the ThinkVantage recovery utilities. This will allow you to recover your Windows installation should you manage to screw your partitions up in the following stages. I highly recommend you do this, as Lenovo does not provide Windows XP CDs with this Laptop - so the hard disk partition is all you've got. Once this is done, we're ready to install Ubuntu!

: Figure 3. Creating recovery discs from Windows
: [[Image:recovery.jpg]]

===Getting Ubuntu installed===

Download the latest Edgy live CD from the Ubuntu website, you can find a list of mirrors at http://www.ubuntu.com/products/GetUbuntu/download#currentrelease. You may also try Kubuntu, Edubuntu or any of it's derivatives, but I'll stick with Ubuntu here for simplicity's sake. Once that's downloaded, burn the ISO to disc using any program of your choice (If this is your first Linux experience and you're using Windows, try using Nero - http://www.nero.com).

Once the burning process is complete, reboot your machine ensuring that the Ubuntu CD is in the drive. You should see an Ubuntu menu. If you don't, your BIOS is not set to boot from CD. Reboot your ThinkPad and change the boot order from BIOS (by default ThinkPads boot from CD-ROM before the hard disk, so this is probably not necessary). Once the menu shows up, select 'Start or install Ubuntu' and let it boot. This will take a while as everything is loaded from CD. You should eventually end up in a Gnome desktop. If you see an error about the Gnome Settings Daemon not being able to load, simply ignore it, as this is not necessary for now. For the purposes of the installation, it's best if you have a wired ethernet connection, as it's unlikely the wireless network card will work until we boot into our installed Ubuntu system.

: Figure 4. Select the first option to start Ubuntu
: [[Image:boot.jpg]]

Double-Click on the 'install' icon on the Desktop to start installation. The installation should be pretty straight-forward. If you need additional help, check out the walk-through with screen-shots at http://www.debianadmin.com/ubuntu-edgy-eft-desktop-installation-with-screenshots.html. The only stage at which we need to make changes is the partitioning stage. This to make sure we preserve our Windows partition, and the IBM vendor_diag partition which allows recovery of the laptop when things go hay-wire. In the 'Prepare disk space' section of the installer, select the third option, 'Manually edit partition table'. A bar will be displayed showing your existing partitions. If you have Windows installed you will see two partitions. The first is a 4.89 GB IBM Vendor Diagnostic partition, which we do not want to touch. The second will be your Windows partition, which will fill the rest of the disk. Click on this partition, Then click the 'Resize/Move' button. I resized my Windows partition to 24 GB. This is enough to accommodate the 10 GB already in use on that partition, as well as giving Windows another 14 GB of free space. 6 GB of free space would probably be enough though.

Now it's time to create partitions for Linux. You need at least two partitions; a swap partition which should be roughly double the amount of RAM you have, and a root partition to install Linux. I opted for four partitions, as follows:

<table border=1>
<tr><td>'''Purpose'''</td><td>'''Size'''</td><td>'''File-System'''</td></tr>
<tr><td>Swap</td><td>2 GB</td><td>swap</td></tr>
<tr><td>/boot</td><td>5 GB</td><td>ext3</td></tr>
<tr><td>/ (root)</td><td>20 GB</td><td>ext3</td></tr>
<tr><td>/home</td><td>37.25 GB (what's left of the disk)</td><td>ext3</td></tr>
</table>

To create these paritions, click on the 'New' button and select 'Extended Partition' in the 'create as' drop-down list. Leave all other settings as-is, and click 'Add'. Now, click on the newly created partition, and create each of the partitions you want to create, simply specify the size of the partition in the 'New Size (MiB)' text box. To convert GB to MiB, multiply by 1024. So for your swap partition you should specify a size of 2048. Repeat until you have created all the required partitions. If you follow my parition layout, the partition editor should look something like Figure 5.

: Figure 5. Our partitions, ready to be created
: [[Image:partitioning.jpg]]

You will not see mount-points in your diagram, because the screen-shot above was taken after they were assigned, but you should get the general idea. After this screen, you will be asked to assign mount-points to the partitions you have just created. If you created the partitions in the same order I did, you can assign mount points as I have (i.e. /dev/sda5 for swap, /dev/sda6 for /boot, /dev/sda7 for /, /dev/sda8 for /home). Additionally, I mounted my Windows partition as /media/sda1 and my IBM Vendor Diagnostic partition as /media/sda2. These are optional. After this step, continue installation as normal. When the installation is complete, click the 'reboot' button to restart into your fresh Ubuntu System.

When booting, the GRUB boot-loader will be displayed, asking you what you want to load. You will probably see four options. The first two being Ubuntu Linux and Ubuntu Linux recovery mode (showing the kernel version). The other two will be Microsoft Windows XP, and 'Other Windows XP/2000/NT' partition. This is your IBM Vendor Diagnostic partition, which is based on the Windows kernel, apparently. Select the first entry to boot Ubuntu. The next time you boot Windows, it will bring up a chkdsk screen. This is entirely normal and happens because we have resized the Windows partition. Make sure you do not skip this check and let it complete.

===Wireless LAN===

The first thing we should do is to get wireless networking working. Luckily, getting the Centrino wireless LAN chip working in Ubuntu is quite easy, if you use the gnome-network-manager applet. Just go to System - Administration - Synaptic Package Manager. Then click 'Search' and set the 'look-in' field to 'name'. In the 'Search' text box type:

<pre>network-manager</pre>

: Figure 6. Installing the network manager applet
: [[Image:networkmanager.jpg]]

Click on the box beside 'network-manager' and click 'Mark for installation'. Do the same for 'network-manager-gnome'. Once installed, reboot your thinkpad. An applet will show up in the gnome notification area. Click on it, and a list of detected wireless networks will be displayed. Simply click on one of them, enter any authentication details necessary, and you'll be connected to the wireless network.

: Figure 7. gnome-network-manager showing available wireless networks
: [[Image:available-accesspoints.jpg]]

Note! Not all versions of the T60 has the Intel Wireless LAN as described above. Run lspci from the command line and look for details of your wifi card. E.g.:

03:00.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)

suggest you have a different wifi card. Read this forum thread http://ubuntuforums.org/showthread.php?t=38972

running:
# dmesg | grep hal

may yield output like this, which apparently suggests the hardware abstraction layer is in place.
[17179590.420000] ath_hal: module license 'Proprietary' taints kernel.
[17179590.424000] ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)

If not, or if the output contains "HAL Status 13" it apparently suggests your card is not supported by the current drivers, and you need to upgrade.

===Installing the ATI display drivers===

If your ThinkPad has an Intel graphics adapter, you should skip this section as Ubuntu installs the best driver automatically. Ubuntu does not install the ATI proprietary drivers by default because they are, er, proprietary. Luckily, installing them is easy enough. Open a terminal (Applications - Accessories - Terminal) and type the following:

: {{cmduser| sudo apt-get update}}
: {{cmduser| sudo apt-get install xorg-driver-fglrx fglrx-control}}

Now we make sure the proprietary driver is not disabled by the kernel. Type the following, and remove any lines referring to fglrx

: {{cmduser|sudo gedit /etc/default/linux-restricted-modules-common}}

An alternative to gedit (Gnome) is nano (sudo nano -w /etc...) for a CLI editor.

Finally, we need to configure the X server to use the ATI drivers. Type the following:

: {{cmduser|sudo depmod -a}}
: {{cmduser|sudo aticonfig --initial}}
: {{cmduser|sudo aticonfig --overlay-type<nowiki>=</nowiki>Xv}}

One last thing. In order to correct a very common problem of getting a jerky video display, type the following:

: {{cmduser|sudo gedit /etc/X11/xorg.conf}}

Scroll to the end of the file, and add the text below.

<pre>
Section "Extensions"
Option "Composite" "0"
EndSection
</pre>

Save the file and exit. Now, to apply the changes either press CTRL+ALT+Backspace or reboot. The resolution should have switched to 1400x1050 and everything should look prettier and render faster. Just to make sure everything is working, open up a terminal and type

: {{cmduser|fglrxinfo}}

This should display:

<pre>
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Mobility Radeon X1400 Generic
OpenGL version string: 2.0.6011 (8.28.8)
</pre>

The above is what I get on my ThinkPad, and you should see something similar. As long as you see your graphics card model listed, everything should be OK. If, instead, you see a bunch of lines containing 'Mesa' then you have a problem. In that case, I recommend consulting https://help.ubuntu.com/community/BinaryDriverHowto/ATI and the Ubuntu forums at http://ubuntuforums.org

===The fingerprint reader===

Although IBM does not officially support it, the fingerprint reader does in fact work with most Linux distributions. Getting it to work with Ubuntu can be a bit of a pain, but it does work. Basically, a bioAPI plugin is provided for PAM. PAM-aware applications such as GDM and gnome-screensaver will then automatically use the fingerprint reader, which is uber cool. Anyway, enough theory, I've probably lost the newbies amongst you already. Go to http://www.qrivy.net/~michael/temp/ and download the latest bioapi package (at the time of writing, bioapi_1.2.3_i386.deb). When asked, tell Firefox to open the file with the GDebi package installer.

That will install bioAPI. What we need now is the driver for our fingerprint device, which is manufactured by UPEK. Go to http://www.upek.com/support/dl_linux_bsp.asp and download the latest version, currently UPEK_BSP_LIN_1.0.zip. Extract this file, then open a terminal (and don't close it until I say so).

: {{cmduser|cd /path/to/where/you/extracted/the/file}}
: {{cmduser|sudo bash}}
: {{cmdroot|sh install.sh /usr/lib}}

Now we need to assign the right permissions so non-root applications can use the driver:

: {{cmdroot|addgroup --system bioapi}}
: {{cmdroot|addgroup --system usbfs}}
: {{cmdroot|adduser yourusername bioapi}}
: {{cmdroot|adduser yourusername usbfs}}
: {{cmdroot|chown -R root:bioapi /usr/var/bioapi/}}
: {{cmdroot|chmod -R 770 /usr/var/bioapi/}}
: {{cmdroot|chown -R root:usbfs /proc/bus/usb}}
: {{cmdroot|chmod -R g+X /proc/bus/usb}}

Of course, replace 'yourusername' with the username you use to login. Now, we need to set the usb file system (usbfs) to be usable by users in the usbfs group. To do this, we need to determine the group ID of the usbfs group. Type the following:

: {{cmdroot|cat /etc/group <nowiki>|</nowiki> grep usbfs <nowiki>|</nowiki> cut -d':' -f 3}}

In my case the number is 116, it might be different for you. Now, open the file /etc/fstab:

: {{cmdroot|gedit /etc/fstab}}

and type the following:

<pre>none /proc/bus/usb usbfs defaults,devgid=116,devmode=0660,busgid=116,busmode=0770,listgid=116,listmode=0660 0 0</pre>

Please type the above code in one line in your file. Remember to replace 116 if you got a different number with the previous cat command. The last permission-related thing we need to fool around with is UDEV. Open the udev permissions file

: {{cmdroot|gedit /etc/udev/rules.d/40-permissions.rules}}

and find the line:

<pre>SUBSYSTEM=="usb_device", MODE="0664"</pre>

It's line 65 in my file. Change it so it looks like this:

<pre>SUBSYSTEM=="usb_device", MODE="0660", GROUP="usbfs"</pre>

Now we need to enroll our fingerprint with the system. To do this, we need a utility called Sample, which is only distributed in source-code form with the driver. This is great, only I couldn't get it to compile on Ubuntu. Luckily, there is a binary version available from one of the earlier releases of the driver (beta 2). To get this, download it from ftp://linux:Tuc-nak3@delta.upek.com/TFMESS_BSP_LIN_1.0beta2.zip. Now, extract the file and type:

: {{cmdroot|cd /path/to/where/you/extracted/the/archive}}
: {{cmdroot|cd NonGUI_sample}}
: {{cmdroot|chmod a+x Sample}}
: {{cmdroot|./Sample}}

Press (e) to enroll a new user, and enter your username when asked for the user ID. You will be asked to swipe your finger three times. Now press (v) and swipe your finger, a green check should be displayed showing you have successfully authenticated.

: Figure 8. The fingerprint swipe prompt
: [[Image:touchchip.jpg]]

Wonderful! Now, quit the application (q) and type exit to become a normal user. A file called yourusername.bir should have been created, copy this to your home directory:

: {{cmdroot|cp yourusername.bir /home/yourusername/}}

You can now close the terminal window. The next step is to install the BioAPI plug-in for PAM, and to make applications use the plugin. So, get the pam_bioapi plugin from http://www.nax.cz/pub/bioapi/pam_bioapi/pam-bioapi_0.3.0.tar.gz and extract it. Now open a terminal and type:

Comment: you will have to install some libraries in order to be able to compile the plugin

: {{cmduser|sudo apt-get install build-essential}}
: {{cmduser|sudo apt-get install libpam0g-dev}}

Now, you can compile and install the plugin

: {{cmduser|cd /path/to/where/you/extracted/the/arcive}}
: {{cmduser|./configure --libdir<nowiki>=</nowiki>/lib --enable-file-store && make}}
: {{cmduser|sudo make install}}

That's installed the plugin. Now, open a terminal and type the following scary commands: (Note: The line starting 'SERIAL=' and the line following it should be in the same line).

: {{cmduser|cd ~}}
: {{cmduser|sudo bash}}
: {{cmdroot|SERIAL=`BioAPITest | sed -ne "/Fingerprint/{n;n;s/^.*: $.\{9\}$$.\{4\}$$.\{4\}$$.\{4\}$$.*$/\1-\2-\3-\4-\5/gp}"`}}
: {{cmdroot|mkdir -p /etc/bioapi/pam/$SERIAL}}
: {{cmdroot|cp yourusername.bir /etc/bioapi/pam/$SERIAL}}
: {{cmdroot|exit}}

Phew. Now, to make applications actually use the fingerprint reader. Open a terminal window, and type:

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

Delete everything in the file, and paste this instead:

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

Save and close the file. That will make all PAM-aware applications use the fingerprint reader. Unfortunately, this also includes sudo. Since sudo is a command line application, it will display prompts in a terminal for you to swipe your finger, which is all well and good. The problem with this is that many Ubuntu administrative applications (such as Synaptic) use gksu to present a graphical front-end to sudo, which will output messages on the command line which you'll never see. Result? Administrative programs won't work from the gnome menu. The solution is to make sudo use the good old password. Open a terminal and type:

: {{cmduser|sudo gedit /etc/pam.d/sudo}}

Delete everything in the file, and instead paste:

<pre>
#%PAM-1.0

#@include common-auth
auth required pam_unix.so nullok_secure
@include common-account
</pre>

Now, save the file and close it, and reboot your system. GDM will ask you for a username, and then show a pretty prompt where you can scan your fingerprint! Same goes for gnome-screensaver when you set it to lock. Sometimes gnome-screensaver will not display the prompt, but you should still swipe your finger and be able to log back in.

===Bluetooth with Mobile Phones/PDAs===

Rather strangely, Ubuntu seems to have taken a step backwards with Bluetooth useability in Edgy. What worked out of the box with Dapper, now requires configuratio. First, open System - Preferences - Sessions and go to the Startup Programs tab. Then, find the entry labelled 'bt-applet --sm-disable'. Highlight it and click disable. Click add and in the command field type 'bt-applet'. Repeat this process, adding an entry for 'gnome-obex-server'. Now, open Synaptic Package Manager (System - Administration - Synaptic Package Manager) and click Search. Type 'gnome-bluetooth' to find the package, then mark it for installation. Now repeat this process for 'bluez-passkey-gnome'. Click apply to make changes.

Now that everything is installed, log-out of Gnome and log back in again. From your phone/PDA, search for devices untill you see your ThinkPad (the hostname will be displayed). Pair with the device. When asked for a passkey, enter 1234, which is the default. If you want to change your passkey (and you should), open a terminal and type:

: {{cmduser|sudo gedit /etc/bluetooth/hcid.conf}}

Find the line which says 'Default PIN for incoming connections' and change the PIN on the line beneath it:

<pre>
# Default PIN code for incoming connections
passkey "4017";
</pre>

Save and close the file, then type:

: {{cmduser|sudo /etc/init.d/bluetooth restart}}

You will now be able to use your new PIN code. To send files from your device to the ThinkPad, simply select the file you want to send and click Send Via Bluetooth (or whatever option your device presents). A dialog will pop-up in Gnome showing you a new file has been received.

: Figure 9. Gnome informing us that a file has been received
: [[Image:bluetooth.jpg]]

Sending files from your ThinkPad to your device requires more effort. The way it should work is that you right-click on a file, click send to, then make sure 'Bluetooth (OBEX)' is selected. Your device should be displayed and you could just click send. Unfortunately, due to a bug in gnome-bluetooth (described in https://launchpad.net/distros/ubuntu/+source/gnome-bluetooth/+bug/70718) this method does not work. If it does work for you, the bug has been solved and you can skip the rest of this section.

Your only other option is to use the command line to send files to your device. Open a terminal, then type:

: {{cmduser|hcitool scan}}

A list of detected bluetooth devices will be shown, for example, my output shows the following:

<pre>
Scanning ...
00:09:DD:60:02:EB Photosmart 8100 series
00:14:A7:99:3C:1F ThElInK
</pre>

The first field is the MAC address of the device, the second is the name of the device. In this case my bluetooth printer and mobile phone (ThElInK) were detected. In order to send files to my phone, I use:

: {{cmduser|gnome-obex-send -d 00:14:A7:99:3C:1F myPicture.jpg}}

Replace the MAC address with that of your device and myPicture.jpg with the file you want to send.

===TrackPoint Scrolling===

By default you can use the right and bottom edges of your touchpad to scroll through documents. If you use the TrackPoint instad of the touchpad (and believe me, you should), you'll find that scrolling is disabled by default. To enable it, open a terminal and type:

: {{cmduser|sudo gedit /etc/X11/xorg.conf}}

Now find the entry for your TrackPoint device. In my configuration file, the TrackPoint entry is the first mouse entry, after the keyboard entry, and looks something like this:

<pre>
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection
</pre>

Right after this entry is my touchpad entry. My entry is on line 66, but yours may be different. Now, add the follwing two options in that InputDevice section:

<pre>
Option "EmulateWheel" "on"
Option "EmulateWheelButton" "2"
</pre>

Save and exit the file. Restart your ThinkPad (or logout, and press CTRL-ALT-BACKSPACE). You should now be able to scoll by holding down the middle button for your TrackPoint and using the TrackPoint to scroll.

===Getting Multimedia to Work===

Due to patents and similar legal crap, Ubuntu will not play most media files by default. You also won't get browser plugins for multimedia. Luckily, this is easily fixed. Open a terminal and type the following:

: {{cmduser|sudo cp /etc/apt/sources.list /etc/apt/sources.list.backup}}
: {{cmduser|sudo gedit /etc/apt/sources.list}}

Delete everything in the file, and instead paste the following:

<pre>
deb-src http://archive.ubuntu.com/ubuntu edgy main restricted universe multiverse
#deb http://archive.ubuntu.com/ubuntu edgy-proposed main restricted universe multiverse

## MAJOR BUG FIX UPDATES produced after the final release
deb-src http://archive.ubuntu.com/ubuntu edgy-updates main restricted universe multiverse

## UBUNTU SECURITY UPDATES
deb http://security.ubuntu.com/ubuntu edgy-security main restricted universe multiverse
deb-src http://security.ubuntu.com/ubuntu edgy-security main restricted universe multiverse

## BACKPORTS REPOSITORY (Unsupported. May contain illegal packages. Use at own risk.)
#deb http://archive.ubuntu.com/ubuntu edgy-backports main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu edgy-backports main restricted universe multiverse

## PLF REPOSITORY
deb http://packages.freecontrib.org/ubuntu/plf edgy-plf free
deb-src http://packages.freecontrib.org/ubuntu/plf edgy-plf free
deb http://packages.freecontrib.org/ubuntu/plf edgy-plf non-free
deb-src http://packages.freecontrib.org/ubuntu/plf edgy-plf non-free

## CANONICAL COMMERCIAL REPOSITORY (Hosted on Canonical servers, not Ubuntu
## servers. RealPlayer10, Opera, DesktopSecure and more to come.)
deb http://archive.canonical.com/ubuntu edgy-commercial main

## Listen
#deb http://theli.free.fr/packages/ edgy listen

## Automatix repo
deb http://www.getautomatix.com/apt edgy main
</pre>

Now, open a terminal and type the following:

: {{cmduser|wget http://packages.freecontrib.org/ubuntu/plf/12B83718.gpg -O- | sudo apt-key add -}}
: {{cmduser|wget http://www.getautomatix.com/apt/key.gpg.asc}}
: {{cmduser|gpg --import key.gpg.asc}}
: {{cmduser|gpg --export --armor 521A9C7C | sudo apt-key add -}}
: {{cmduser|sudo apt-get update}}
: {{cmduser|sudo apt-get install automatix2}}
: {{cmduser|wget http://easyubuntu.freecontrib.org/files/easyubuntu-3.023.tar.gz}}
: {{cmduser|tar -zxf easyubuntu-3.023.tar.gz}}
: {{cmduser|cd easyubuntu}}
: {{cmduser|cp packagelist-dapper.pot packagelist-edgy.pot}}
: {{cmduser|cp packagelist-dapper.xml packagelist-edgy.xml}}
: {{cmduser|sudo python easyubuntu.in}}

Don't worry if you get errors from the Ubuntu PLF repository. PLF mirrors are about as stable as wild bull in a farm full of cows. Select what you want to install from the resulting window. Make sure you do not select the totem-mozilla plugin, as this just doens't work, for me at least. When EasyUbuntu has finished installing packages, you should be returned to a terminal, which you can close. Now go to Applications - System Tools - Automatix. Read and agree to the warning. Check what you want to install. Make sure you check 'Mplayer and FF plugin'. When ready, click the 'install' button. That should get multimedia working nicely.

: Figure 10. The Automatix user interface
: [[Image:automatix.jpg]]

===Beryl - fancy 3D desktop===

MAC OS X has Aqua and Windows Vista has Aero. Well, Linux has XGL/Beryl which can get effects which are as good looking (or sometimes better!) than the former two. Installing Beryl on Ubuntu is not that hard. First, open a terminal and type the following:

: {{cmduser|sudo gedit /etc/apt/sources.list}}

At the end of the file, append the following:

<pre>
##Beryl
deb http://ubuntu.beryl-project.org/ edgy main
</pre>

Save and close the file. Now type:

: {{cmduser|wget http://beryl-mirror.lupine.me.uk/1609B551.gpg -O- | sudo apt-key add -}}
: {{cmduser|sudo apt-get update}}

ATI Users Only: type

: {{cmduser|sudo apt-get install xserver-xgl}}

Now, to install beryl:

: {{cmduser|sudo apt-get install beryl emerald-themes}}

To make Ubuntu use the 3D effects. Open a terminal:

: {{cmduser|sudo gedit /usr/local/bin/startxgl.sh}}

In that file, paste the following if you use an ATI card:

<pre>
#!/bin/sh
Xgl -fullscreen :1 -ac -br -accel glx:pbuffer -accel xv:pbuffer &
sleep 4
export DISPLAY=:1
exec gnome-session
</pre>

If you use an Intel card, paste the following instead:

<pre>
#!/bin/sh
beryl-manager
sleep 4
exec gnome-session
</pre>

Save the file and close. Now we need to make the file executable:

: {{cmduser|sudo chmod a+x /usr/local/bin/startxgl.sh}}

All that's left now is to create a login script which makes gnome use the 3D effects. In a terminal, type:

: {{cmduser|sudo gedit /usr/share/xsessions/xgl.desktop}}

Now, in this file paste:

<pre>
[Desktop Entry]
Encoding=UTF-8
Name=Xgl
Exec=/usr/local/bin/startxgl.sh
Icon=
Type=Application
</pre>

Save and close the file. Now type:

: {{cmduser|sudo gedit /usr/local/bin/start_beryl.sh}}

In this file, paste:

<pre>
#!/bin/bash
#
# Start beryl-manager within gnome-session
#
if [ `ps -A -o comm | grep -c '^Xgl$'` == "1" ]; then
DISPLAY=:1 beryl-manager
DISPLAY=:1 beryl-xgl
else echo "${0}: Error: beryl-manager not launched. Xgl not running?"
fi
</pre>

Now make the file executable:

: {{cmduser|sudo chmod a+x /usr/local/bin/start_beryl.sh}}

Now go to System - Preferences - Sessions, go to the Startup Programs tab, and click add, then type

: {{cmduser|/usr/local/bin/start_beryl.sh}}

Now, reboot your ThinkPad. When you come to the login screen, click the 'Sessions' button on the bottom left corner, and select XGL. login, et voila! beautiful 3D effects!

: Figure 11. Beryl's Cube effect
: [[Image:cube.jpg]]

If you have NetBeans installed, try launching it now. It probably won't work due to Beryl. Luckily, this is easily solved. Open a terminal and type:

: {{cmduser|sudo gedit /etc/environment}}

Then add the following line to the end of the file.

<pre>AWT_TOOLKIT="MToolkit"</pre>

Now save, close and reboot. Netbeans should now work!

===Problem: Can't add programs to session===

So you tried to add something to your startup programs, it shows up in the list, but it doesn't start up. You then launch the sessions program again, only to find your program has disappeared from the list. This problem is being caused by incorrect permissions in your home directory, and can happen on some occasions. To fix it, open a terminal and type the following:

: {{cmduser|sudo chown -R username:usergroup /home/username/.config/}}

Replace username with your username and usergroup with your group (by default, in Ubuntu your usergroup is the same as your username). Everything should be OK now!

===Problem: Virtual terminals not working===

One problem I had after installing the ATI drivers was that virtual terminals stopped working. Instead of seeing a console when pressing CTRL+ALT+F1...F6 I was seeing a yellow/orange garbled output. Luckily, solving this with ATI drivers is trivial. Open a terminal, and type:

: {{cmduser|sudo gedit /boot/grub/menu.lst}}

Find the line which says

<pre>#defoptions=quiet splash</pre>

and replace it with

<pre>#defoptions=quiet splash vga=791</pre>

Now, find the line which boots the kernel you are currently using, this is just under '## ## End Default Options ##. In the 'kernel' line, add:

<pre>vga=791</pre>

Before:

<pre>kernel /vmlinuz-2.6.17-10-generic root=/dev/sda7 ro quiet splash</pre>

After:

<pre>kernel /vmlinuz-2.6.17-10-generic root=/dev/sda7 ro quiet splash vga=791</pre>

Now save and exit the file, and reboot. Virtual terminals should now work. If you use Intel drivers, you're going to have to bite the bullet and remove the 'splash' keyword from both the defoptions and kernel lines. You'll lose the pretty bootup screen, but at least virtual terminals will work, which are important to recover a crashed system.

===Problem: I keep logging out!===

If you're using Beryl, and find that you keep getting logged out, you've just encountered one of Beryl's most annoying bugs. Shift+Backspace causes a logout. To fix this, open a terminal and type:

: {{cmduser|gedit /home/username/annoymenot.sh}}

Remember to replace 'username' with your username. Now, in this file type:

: {{cmduser|xmodmap -e "keycode 22 <nowiki>=</nowiki> BackSpace BackSpace Terminate_Server" }}

Save and close the file, and make it executable:

: {{cmduser|chmod 755 /home/username/annoymenot.sh}}

Now go to System - Preferences - Session, Startup Programs. Click add, and type

: {{cmduser|/home/username/annoymenot.sh}}

Logout and back in, problem solved! While you're at it, how about getting the start button to work? Go to System - Preferences - Keyboard - Layout Options - Alt/Win Key behaviour and select 'Super is mapped to Win keys (default)'.

===Desktop envy===

We're living in an age of desktop prettyness, and Linux can be just as pretty as MAC OS X or Vista. You've already got Beryl installed. Now go to Applications - Accesories - gDesklets. If the gDesklets entry is not there, make sure you install it, either using Synaptic or Automatix. Desklets are small programs you can add to your desktop, ala OS X's Deskbar or Vista's Sidebar. To make them start on boot, add gdesklets in System - Preferences - Sessions, Startup Programs.

Another cool program is cairo clock. Download it from http://macslow.thepimp.net/projects/cairo-clock/cairo-clock_0.3.2-1_i386.deb and install it by double-clicking. To make it start automatically, add it to your sessions as mentioned above. I've found the following command makes it work best for me:

<pre>cairo-clock -s -w 175 -g 175 -x 1219 -y 7 -t radium</pre>

Finally, make sure you click that Ruby icon in your notification area, it allows you to configure Beryl to do all sorts of cool stuff!

===Conclusion===

Well, that's about it! A dream Linux system on a dream laptop! Check out these cool technologies for an even better system:

* Beagle
* Tomboy
* Deskbar

===References===

* ATI on Ubuntu - https://help.ubuntu.com/community/BinaryDriverHowto/ATI
* Garbled Virtual Terminal Bug - https://launchpad.net/distros/ubuntu/+source/usplash/+bug/63558
* Beryl logout Bug - http://forum.beryl-project.org/viewtopic.php?p=1295&sid=6feedd09a7f01bca68feb05a5f2f033c
* Beryl Netbeans Bug - http://ubuntuforums.org/showthread.php?t=252594
* Beryl on Ubuntu - http://wiki.beryl-project.org/index.php/Install/Ubuntu/Edgy/XGL
* Home directory permissions bug - http://www.ubuntuforums.org/showthread.php?p=1789997
* gnome-bluetooth bug - https://launchpad.net/distros/ubuntu/+source/gnome-bluetooth/+bug/70718

Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60

2006-12-20T07:28:18Z

Ischg: /* The fingerprint reader */

[[User:Keithvassallo|Keithvassallo]] 14:39, 16 December 2006 (CET)

===Abstract===

This article describes how to get Ubuntu Linux 6.10 (Edgy) installed on an IBM/Lenovo ThinkPad T60. It's not meant to be a definite guide to installing Ubuntu (the Ubuntu Guide at http://www.ubuntuguide.org does a very good job of that). This article is meant to describe how to get most of the ThinkPad features working on Ubuntu system. It also discusses how to get Multimedia, some cool-looking effects such as Beryl, gDesklets and similar working on Ubuntu. Finally, we discuss some common problems encountered on Ubuntu and ThinkPads alike.

===My ThinkPad===

Although this guide should work on most recent ThinkPads, I cannot guarantee that. These are the specifications of my machine. The closer your specs are, the greater the chance of success.

: Figure 1. ThinkPad T60 2007, complete with Tux sticker :-)
: [[Image:thinkpad.jpg]]

* Lenovo ThinkPad T60 2007.
* Intel Centrino Duo T2400 / 1.83 GHz.
* Mobile Intel 945PM Express Chipset.
* Intel Wireless LAN.
* Integrated Bluetooth.
* ATI Mobility Radeon X1400 - PCI Express x16, 128MB dedicated RAM.
* 100 GB - Serial ATA-150 Hard Drive.
* 15' TFT Active Matrix Display (1400x1050).

That's basically all you need to know. As far as I know, all other features are common to all ThinkPads manufactured by Lenovo since they acquired IBM's computer business.

===Why Ubuntu? (or rather, Why not SUSE?)===

In June 2006, Lenovo announced it would be shipping ThinkPad T60p laptops with SUSE Linux Enterprise Desktop (SLED) 10 pre-installed, since SLED apparently supports all of the features of the T60p. I contacted my local IBM supplier, who said that Lenovo were no longer manufacturing the T60p, since the company which was making the displays went out of business. This meant I could not get a T60p with SLED pre-installed. I decided to go for the T60 2007, which is the closest thing I could find to the T60p. This comes with Windows XP Professional pre-installed.

I first tried to get SLED installed on the T60. Although it did indeed install, and most features worked, I soon got bored of SLED. Firstly, SLED uses Gnome 2.12, which is by now ancient. Secondly, although the Lenovo utilities do work on SLED, they only work well if you use KDE as your defauly desktop environment, which is a pity since I'm a Gnome user. The utilities were very unstable to me too. Finally, what made me give up SLED was the usual problem - it's an RPM based distribution. Once you start using Debian derivatives, with their apt based installer, you won't want to go back. That's when I decided to try Ubuntu, and have not regretted it since.

===What Works?===

* Ubuntu and all programs it comes with.
* Most of the function keys, except the ones mentioned below
* The fingerprint reader.
* The ATI proprietary graphics drivers.
* Suspend to RAM (Sleep) and Suspend to Disk (Hibernate).
* Brightness, Volume and Mute with OSD (On-Screen Display).
* ThinkLight, TrackPoint II and the touchpad.

===What Doesn't Work? (Known Issues)===

* FN+F8, FN+F9, FN+ZOOM.
* The BACK and FORWARD buttons (next to the cursor keys).
* The ThinkVantage button (in Linux, still works on boot).
* Sending files to Bluetooth devices via GUI.

There are probably ways and means to get the offending buttons to work, I've tried several fora but none seem to address my exact problem. I'll update this article should I find out anything.

===First Things First - Creating a Windows Recovery Disc===

If you've purchased a T60, chances are it came with Windows XP Professional. The other option is for you to have FreeDOS installed, in which case you can skip this section. You could remove the Windows partition altogether, and reserve your ThinkPad for Linux, but that's not the route I've chosen. The ThinkVantage utilities in Windows allow you to do a lot of cool things, such as set-up a boot-up fingerprint security scan. You can't do this from Linux (as far as I know) so it's best to leave the Windows partition in place. So, boot your ThinkPad and complete the Windows XP setup (which asks you to add a user account and enroll yourself using the ThinkVantage Client Security Solution). While you're there, use the ThinkVantage productivy centre to enroll your fingerprint (I suggest enrolling more than one) and make sure you check the option to require a fingerprint scan on boot (not for security, for geek points). When you reboot, press ESC or F2 to get to BIOS, and make sure you check the option to require a supervisor password. This will make your ThinkPad prompt you for your fingerprint when you power it up.

: Figure 2. Configuring fingerprint security from Windows
: [[Image:winprint.jpg]]

Now that's working, you should create a recovery DVD using the ThinkVantage recovery utilities. This will allow you to recover your Windows installation should you manage to screw your partitions up in the following stages. I highly recommend you do this, as Lenovo does not provide Windows XP CDs with this Laptop - so the hard disk partition is all you've got. Once this is done, we're ready to install Ubuntu!

: Figure 3. Creating recovery discs from Windows
: [[Image:recovery.jpg]]

===Getting Ubuntu installed===

Download the latest Edgy live CD from the Ubuntu website, you can find a list of mirrors at http://www.ubuntu.com/products/GetUbuntu/download#currentrelease. You may also try Kubuntu, Edubuntu or any of it's derivatives, but I'll stick with Ubuntu here for simplicity's sake. Once that's downloaded, burn the ISO to disc using any program of your choice (If this is your first Linux experience and you're using Windows, try using Nero - http://www.nero.com).

Once the burning process is complete, reboot your machine ensuring that the Ubuntu CD is in the drive. You should see an Ubuntu menu. If you don't, your BIOS is not set to boot from CD. Reboot your ThinkPad and change the boot order from BIOS (by default ThinkPads boot from CD-ROM before the hard disk, so this is probably not necessary). Once the menu shows up, select 'Start or install Ubuntu' and let it boot. This will take a while as everything is loaded from CD. You should eventually end up in a Gnome desktop. If you see an error about the Gnome Settings Daemon not being able to load, simply ignore it, as this is not necessary for now. For the purposes of the installation, it's best if you have a wired ethernet connection, as it's unlikely the wireless network card will work until we boot into our installed Ubuntu system.

: Figure 4. Select the first option to start Ubuntu
: [[Image:boot.jpg]]

Double-Click on the 'install' icon on the Desktop to start installation. The installation should be pretty straight-forward. If you need additional help, check out the walk-through with screen-shots at http://www.debianadmin.com/ubuntu-edgy-eft-desktop-installation-with-screenshots.html. The only stage at which we need to make changes is the partitioning stage. This to make sure we preserve our Windows partition, and the IBM vendor_diag partition which allows recovery of the laptop when things go hay-wire. In the 'Prepare disk space' section of the installer, select the third option, 'Manually edit partition table'. A bar will be displayed showing your existing partitions. If you have Windows installed you will see two partitions. The first is a 4.89 GB IBM Vendor Diagnostic partition, which we do not want to touch. The second will be your Windows partition, which will fill the rest of the disk. Click on this partition, Then click the 'Resize/Move' button. I resized my Windows partition to 24 GB. This is enough to accommodate the 10 GB already in use on that partition, as well as giving Windows another 14 GB of free space. 6 GB of free space would probably be enough though.

Now it's time to create partitions for Linux. You need at least two partitions; a swap partition which should be roughly double the amount of RAM you have, and a root partition to install Linux. I opted for four partitions, as follows:

<table border=1>
<tr><td>'''Purpose'''</td><td>'''Size'''</td><td>'''File-System'''</td></tr>
<tr><td>Swap</td><td>2 GB</td><td>swap</td></tr>
<tr><td>/boot</td><td>5 GB</td><td>ext3</td></tr>
<tr><td>/ (root)</td><td>20 GB</td><td>ext3</td></tr>
<tr><td>/home</td><td>37.25 GB (what's left of the disk)</td><td>ext3</td></tr>
</table>

To create these paritions, click on the 'New' button and select 'Extended Partition' in the 'create as' drop-down list. Leave all other settings as-is, and click 'Add'. Now, click on the newly created partition, and create each of the partitions you want to create, simply specify the size of the partition in the 'New Size (MiB)' text box. To convert GB to MiB, multiply by 1024. So for your swap partition you should specify a size of 2048. Repeat until you have created all the required partitions. If you follow my parition layout, the partition editor should look something like Figure 5.

: Figure 5. Our partitions, ready to be created
: [[Image:partitioning.jpg]]

You will not see mount-points in your diagram, because the screen-shot above was taken after they were assigned, but you should get the general idea. After this screen, you will be asked to assign mount-points to the partitions you have just created. If you created the partitions in the same order I did, you can assign mount points as I have (i.e. /dev/sda5 for swap, /dev/sda6 for /boot, /dev/sda7 for /, /dev/sda8 for /home). Additionally, I mounted my Windows partition as /media/sda1 and my IBM Vendor Diagnostic partition as /media/sda2. These are optional. After this step, continue installation as normal. When the installation is complete, click the 'reboot' button to restart into your fresh Ubuntu System.

When booting, the GRUB boot-loader will be displayed, asking you what you want to load. You will probably see four options. The first two being Ubuntu Linux and Ubuntu Linux recovery mode (showing the kernel version). The other two will be Microsoft Windows XP, and 'Other Windows XP/2000/NT' partition. This is your IBM Vendor Diagnostic partition, which is based on the Windows kernel, apparently. Select the first entry to boot Ubuntu. The next time you boot Windows, it will bring up a chkdsk screen. This is entirely normal and happens because we have resized the Windows partition. Make sure you do not skip this check and let it complete.

===Wireless LAN===

The first thing we should do is to get wireless networking working. Luckily, getting the Centrino wireless LAN chip working in Ubuntu is quite easy, if you use the gnome-network-manager applet. Just go to System - Administration - Synaptic Package Manager. Then click 'Search' and set the 'look-in' field to 'name'. In the 'Search' text box type:

<pre>network-manager</pre>

: Figure 6. Installing the network manager applet
: [[Image:networkmanager.jpg]]

Click on the box beside 'network-manager' and click 'Mark for installation'. Do the same for 'network-manager-gnome'. Once installed, reboot your thinkpad. An applet will show up in the gnome notification area. Click on it, and a list of detected wireless networks will be displayed. Simply click on one of them, enter any authentication details necessary, and you'll be connected to the wireless network.

: Figure 7. gnome-network-manager showing available wireless networks
: [[Image:available-accesspoints.jpg]]

Note! Not all versions of the T60 has the Intel Wireless LAN as described above. Run lspci from the command line and look for details of your wifi card. E.g.:

03:00.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)

suggest you have a different wifi card. Read this forum thread http://ubuntuforums.org/showthread.php?t=38972

running:
# dmesg | grep hal

may yield output like this, which apparently suggests the hardware abstraction layer is in place.
[17179590.420000] ath_hal: module license 'Proprietary' taints kernel.
[17179590.424000] ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)

If not, or if the output contains "HAL Status 13" it apparently suggests your card is not supported by the current drivers, and you need to upgrade.

===Installing the ATI display drivers===

If your ThinkPad has an Intel graphics adapter, you should skip this section as Ubuntu installs the best driver automatically. Ubuntu does not install the ATI proprietary drivers by default because they are, er, proprietary. Luckily, installing them is easy enough. Open a terminal (Applications - Accessories - Terminal) and type the following:

: {{cmduser| sudo apt-get update}}
: {{cmduser| sudo apt-get install xorg-driver-fglrx fglrx-control}}

Now we make sure the proprietary driver is not disabled by the kernel. Type the following, and remove any lines referring to fglrx

: {{cmduser|sudo gedit /etc/default/linux-restricted-modules-common}}

An alternative to gedit (Gnome) is nano (sudo nano -w /etc...) for a CLI editor.

Finally, we need to configure the X server to use the ATI drivers. Type the following:

: {{cmduser|sudo depmod -a}}
: {{cmduser|sudo aticonfig --initial}}
: {{cmduser|sudo aticonfig --overlay-type<nowiki>=</nowiki>Xv}}

One last thing. In order to correct a very common problem of getting a jerky video display, type the following:

: {{cmduser|sudo gedit /etc/X11/xorg.conf}}

Scroll to the end of the file, and add the text below.

<pre>
Section "Extensions"
Option "Composite" "0"
EndSection
</pre>

Save the file and exit. Now, to apply the changes either press CTRL+ALT+Backspace or reboot. The resolution should have switched to 1400x1050 and everything should look prettier and render faster. Just to make sure everything is working, open up a terminal and type

: {{cmduser|fglrxinfo}}

This should display:

<pre>
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Mobility Radeon X1400 Generic
OpenGL version string: 2.0.6011 (8.28.8)
</pre>

The above is what I get on my ThinkPad, and you should see something similar. As long as you see your graphics card model listed, everything should be OK. If, instead, you see a bunch of lines containing 'Mesa' then you have a problem. In that case, I recommend consulting https://help.ubuntu.com/community/BinaryDriverHowto/ATI and the Ubuntu forums at http://ubuntuforums.org

===The fingerprint reader===

Although IBM does not officially support it, the fingerprint reader does in fact work with most Linux distributions. Getting it to work with Ubuntu can be a bit of a pain, but it does work. Basically, a bioAPI plugin is provided for PAM. PAM-aware applications such as GDM and gnome-screensaver will then automatically use the fingerprint reader, which is uber cool. Anyway, enough theory, I've probably lost the newbies amongst you already. Go to http://www.qrivy.net/~michael/temp/ and download the latest bioapi package (at the time of writing, bioapi_1.2.3_i386.deb). When asked, tell Firefox to open the file with the GDebi package installer.

That will install bioAPI. What we need now is the driver for our fingerprint device, which is manufactured by UPEK. Go to http://www.upek.com/support/dl_linux_bsp.asp and download the latest version, currently UPEK_BSP_LIN_1.0.zip. Extract this file, then open a terminal (and don't close it until I say so).

: {{cmduser|cd /path/to/where/you/extracted/the/file}}
: {{cmduser|sudo bash}}
: {{cmdroot|sh install.sh /usr/lib}}

Now we need to assign the right permissions so non-root applications can use the driver:

: {{cmdroot|addgroup --system bioapi}}
: {{cmdroot|addgroup --system usbfs}}
: {{cmdroot|adduser yourusername bioapi}}
: {{cmdroot|adduser yourusername usbfs}}
: {{cmdroot|chown -R root:bioapi /usr/var/bioapi/}}
: {{cmdroot|chmod -R 770 /usr/var/bioapi/}}
: {{cmdroot|chown -R root:usbfs /proc/bus/usb}}
: {{cmdroot|chmod -R g+X /proc/bus/usb}}

Of course, replace 'yourusername' with the username you use to login. Now, we need to set the usb file system (usbfs) to be usable by users in the usbfs group. To do this, we need to determine the group ID of the usbfs group. Type the following:

: {{cmdroot|cat /etc/group | grep usbfs | cut -d':' -f 3}}

In my case the number is 116, it might be different for you. Now, open the file /etc/fstab:

: {{cmdroot|gedit /etc/fstab}}

and type the following:

<pre>none /proc/bus/usb usbfs defaults,devgid=116,devmode=0660,busgid=116,busmode=0770,listgid=116,listmode=0660 0 0</pre>

Please type the above code in one line in your file. Remember to replace 116 if you got a different number with the previous cat command. The last permission-related thing we need to fool around with is UDEV. Open the udev permissions file

: {{cmdroot|gedit /etc/udev/rules.d/40-permissions.rules}}

and find the line:

<pre>SUBSYSTEM=="usb_device", MODE="0664"</pre>

It's line 65 in my file. Change it so it looks like this:

<pre>SUBSYSTEM=="usb_device", MODE="0660", GROUP="usbfs"</pre>

Now we need to enroll our fingerprint with the system. To do this, we need a utility called Sample, which is only distributed in source-code form with the driver. This is great, only I couldn't get it to compile on Ubuntu. Luckily, there is a binary version available from one of the earlier releases of the driver (beta 2). To get this, download it from ftp://linux:Tuc-nak3@delta.upek.com/TFMESS_BSP_LIN_1.0beta2.zip. Now, extract the file and type:

: {{cmdroot|cd /path/to/where/you/extracted/the/archive}}
: {{cmdroot|cd NonGUI_sample}}
: {{cmdroot|chmod a+x Sample}}
: {{cmdroot|./Sample}}

Press (e) to enroll a new user, and enter your username when asked for the user ID. You will be asked to swipe your finger three times. Now press (v) and swipe your finger, a green check should be displayed showing you have successfully authenticated.

: Figure 8. The fingerprint swipe prompt
: [[Image:touchchip.jpg]]

Wonderful! Now, quit the application (q) and type exit to become a normal user. A file called yourusername.bir should have been created, copy this to your home directory:

: {{cmdroot|cp yourusername.bir /home/yourusername/}}

You can now close the terminal window. The next step is to install the BioAPI plug-in for PAM, and to make applications use the plugin. So, get the pam_bioapi plugin from http://www.nax.cz/pub/bioapi/pam_bioapi/pam-bioapi_0.3.0.tar.gz and extract it. Now open a terminal and type:

Comment: you will have to install some libraries in order to be able to compile the plugin

: {{cmduser|sudo apt-get install build-essential}}
: {{cmduser|sudo apt-get install libpam0g-dev}}

Now, you can compile and install the plugin

: {{cmduser|cd /path/to/where/you/extracted/the/arcive}}
: {{cmduser|./configure --libdir<nowiki>=</nowiki>/lib --enable-file-store && make}}
: {{cmduser|sudo make install}}

That's installed the plugin. Now, open a terminal and type the following scary commands: (Note: The line starting 'SERIAL=' and the line following it should be in the same line).

: {{cmduser|cd ~}}
: {{cmduser|sudo bash}}
: {{cmdroot|SERIAL=`BioAPITest | sed -ne "/Fingerprint/{n;n;s/^.*: $.\{9\}$$.\{4\}$$.\{4\}$$.\{4\}$$.*$/\1-\2-\3-\4-\5/gp}"`}}
: {{cmdroot|mkdir -p /etc/bioapi/pam/$SERIAL}}
: {{cmdroot|cp yourusername.bir /etc/bioapi/pam/$SERIAL}}
: {{cmdroot|exit}}

Phew. Now, to make applications actually use the fingerprint reader. Open a terminal window, and type:

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

Delete everything in the file, and paste this instead:

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

Save and close the file. That will make all PAM-aware applications use the fingerprint reader. Unfortunately, this also includes sudo. Since sudo is a command line application, it will display prompts in a terminal for you to swipe your finger, which is all well and good. The problem with this is that many Ubuntu administrative applications (such as Synaptic) use gksu to present a graphical front-end to sudo, which will output messages on the command line which you'll never see. Result? Administrative programs won't work from the gnome menu. The solution is to make sudo use the good old password. Open a terminal and type:

: {{cmduser|sudo gedit /etc/pam.d/sudo}}

Delete everything in the file, and instead paste:

<pre>
#%PAM-1.0

#@include common-auth
auth required pam_unix.so nullok_secure
@include common-account
</pre>

Now, save the file and close it, and reboot your system. GDM will ask you for a username, and then show a pretty prompt where you can scan your fingerprint! Same goes for gnome-screensaver when you set it to lock. Sometimes gnome-screensaver will not display the prompt, but you should still swipe your finger and be able to log back in.

===Bluetooth with Mobile Phones/PDAs===

Rather strangely, Ubuntu seems to have taken a step backwards with Bluetooth useability in Edgy. What worked out of the box with Dapper, now requires configuratio. First, open System - Preferences - Sessions and go to the Startup Programs tab. Then, find the entry labelled 'bt-applet --sm-disable'. Highlight it and click disable. Click add and in the command field type 'bt-applet'. Repeat this process, adding an entry for 'gnome-obex-server'. Now, open Synaptic Package Manager (System - Administration - Synaptic Package Manager) and click Search. Type 'gnome-bluetooth' to find the package, then mark it for installation. Now repeat this process for 'bluez-passkey-gnome'. Click apply to make changes.

Now that everything is installed, log-out of Gnome and log back in again. From your phone/PDA, search for devices untill you see your ThinkPad (the hostname will be displayed). Pair with the device. When asked for a passkey, enter 1234, which is the default. If you want to change your passkey (and you should), open a terminal and type:

: {{cmduser|sudo gedit /etc/bluetooth/hcid.conf}}

Find the line which says 'Default PIN for incoming connections' and change the PIN on the line beneath it:

<pre>
# Default PIN code for incoming connections
passkey "4017";
</pre>

Save and close the file, then type:

: {{cmduser|sudo /etc/init.d/bluetooth restart}}

You will now be able to use your new PIN code. To send files from your device to the ThinkPad, simply select the file you want to send and click Send Via Bluetooth (or whatever option your device presents). A dialog will pop-up in Gnome showing you a new file has been received.

: Figure 9. Gnome informing us that a file has been received
: [[Image:bluetooth.jpg]]

Sending files from your ThinkPad to your device requires more effort. The way it should work is that you right-click on a file, click send to, then make sure 'Bluetooth (OBEX)' is selected. Your device should be displayed and you could just click send. Unfortunately, due to a bug in gnome-bluetooth (described in https://launchpad.net/distros/ubuntu/+source/gnome-bluetooth/+bug/70718) this method does not work. If it does work for you, the bug has been solved and you can skip the rest of this section.

Your only other option is to use the command line to send files to your device. Open a terminal, then type:

: {{cmduser|hcitool scan}}

A list of detected bluetooth devices will be shown, for example, my output shows the following:

<pre>
Scanning ...
00:09:DD:60:02:EB Photosmart 8100 series
00:14:A7:99:3C:1F ThElInK
</pre>

The first field is the MAC address of the device, the second is the name of the device. In this case my bluetooth printer and mobile phone (ThElInK) were detected. In order to send files to my phone, I use:

: {{cmduser|gnome-obex-send -d 00:14:A7:99:3C:1F myPicture.jpg}}

Replace the MAC address with that of your device and myPicture.jpg with the file you want to send.

===TrackPoint Scrolling===

By default you can use the right and bottom edges of your touchpad to scroll through documents. If you use the TrackPoint instad of the touchpad (and believe me, you should), you'll find that scrolling is disabled by default. To enable it, open a terminal and type:

: {{cmduser|sudo gedit /etc/X11/xorg.conf}}

Now find the entry for your TrackPoint device. In my configuration file, the TrackPoint entry is the first mouse entry, after the keyboard entry, and looks something like this:

<pre>
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection
</pre>

Right after this entry is my touchpad entry. My entry is on line 66, but yours may be different. Now, add the follwing two options in that InputDevice section:

<pre>
Option "EmulateWheel" "on"
Option "EmulateWheelButton" "2"
</pre>

Save and exit the file. Restart your ThinkPad (or logout, and press CTRL-ALT-BACKSPACE). You should now be able to scoll by holding down the middle button for your TrackPoint and using the TrackPoint to scroll.

===Getting Multimedia to Work===

Due to patents and similar legal crap, Ubuntu will not play most media files by default. You also won't get browser plugins for multimedia. Luckily, this is easily fixed. Open a terminal and type the following:

: {{cmduser|sudo cp /etc/apt/sources.list /etc/apt/sources.list.backup}}
: {{cmduser|sudo gedit /etc/apt/sources.list}}

Delete everything in the file, and instead paste the following:

<pre>
deb-src http://archive.ubuntu.com/ubuntu edgy main restricted universe multiverse
#deb http://archive.ubuntu.com/ubuntu edgy-proposed main restricted universe multiverse

## MAJOR BUG FIX UPDATES produced after the final release
deb-src http://archive.ubuntu.com/ubuntu edgy-updates main restricted universe multiverse

## UBUNTU SECURITY UPDATES
deb http://security.ubuntu.com/ubuntu edgy-security main restricted universe multiverse
deb-src http://security.ubuntu.com/ubuntu edgy-security main restricted universe multiverse

## BACKPORTS REPOSITORY (Unsupported. May contain illegal packages. Use at own risk.)
#deb http://archive.ubuntu.com/ubuntu edgy-backports main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu edgy-backports main restricted universe multiverse

## PLF REPOSITORY
deb http://packages.freecontrib.org/ubuntu/plf edgy-plf free
deb-src http://packages.freecontrib.org/ubuntu/plf edgy-plf free
deb http://packages.freecontrib.org/ubuntu/plf edgy-plf non-free
deb-src http://packages.freecontrib.org/ubuntu/plf edgy-plf non-free

## CANONICAL COMMERCIAL REPOSITORY (Hosted on Canonical servers, not Ubuntu
## servers. RealPlayer10, Opera, DesktopSecure and more to come.)
deb http://archive.canonical.com/ubuntu edgy-commercial main

## Listen
#deb http://theli.free.fr/packages/ edgy listen

## Automatix repo
deb http://www.getautomatix.com/apt edgy main
</pre>

Now, open a terminal and type the following:

: {{cmduser|wget http://packages.freecontrib.org/ubuntu/plf/12B83718.gpg -O- | sudo apt-key add -}}
: {{cmduser|wget http://www.getautomatix.com/apt/key.gpg.asc}}
: {{cmduser|gpg --import key.gpg.asc}}
: {{cmduser|gpg --export --armor 521A9C7C | sudo apt-key add -}}
: {{cmduser|sudo apt-get update}}
: {{cmduser|sudo apt-get install automatix2}}
: {{cmduser|wget http://easyubuntu.freecontrib.org/files/easyubuntu-3.023.tar.gz}}
: {{cmduser|tar -zxf easyubuntu-3.023.tar.gz}}
: {{cmduser|cd easyubuntu}}
: {{cmduser|cp packagelist-dapper.pot packagelist-edgy.pot}}
: {{cmduser|cp packagelist-dapper.xml packagelist-edgy.xml}}
: {{cmduser|sudo python easyubuntu.in}}

Don't worry if you get errors from the Ubuntu PLF repository. PLF mirrors are about as stable as wild bull in a farm full of cows. Select what you want to install from the resulting window. Make sure you do not select the totem-mozilla plugin, as this just doens't work, for me at least. When EasyUbuntu has finished installing packages, you should be returned to a terminal, which you can close. Now go to Applications - System Tools - Automatix. Read and agree to the warning. Check what you want to install. Make sure you check 'Mplayer and FF plugin'. When ready, click the 'install' button. That should get multimedia working nicely.

: Figure 10. The Automatix user interface
: [[Image:automatix.jpg]]

===Beryl - fancy 3D desktop===

MAC OS X has Aqua and Windows Vista has Aero. Well, Linux has XGL/Beryl which can get effects which are as good looking (or sometimes better!) than the former two. Installing Beryl on Ubuntu is not that hard. First, open a terminal and type the following:

: {{cmduser|sudo gedit /etc/apt/sources.list}}

At the end of the file, append the following:

<pre>
##Beryl
deb http://ubuntu.beryl-project.org/ edgy main
</pre>

Save and close the file. Now type:

: {{cmduser|wget http://beryl-mirror.lupine.me.uk/1609B551.gpg -O- | sudo apt-key add -}}
: {{cmduser|sudo apt-get update}}

ATI Users Only: type

: {{cmduser|sudo apt-get install xserver-xgl}}

Now, to install beryl:

: {{cmduser|sudo apt-get install beryl emerald-themes}}

To make Ubuntu use the 3D effects. Open a terminal:

: {{cmduser|sudo gedit /usr/local/bin/startxgl.sh}}

In that file, paste the following if you use an ATI card:

<pre>
#!/bin/sh
Xgl -fullscreen :1 -ac -br -accel glx:pbuffer -accel xv:pbuffer &
sleep 4
export DISPLAY=:1
exec gnome-session
</pre>

If you use an Intel card, paste the following instead:

<pre>
#!/bin/sh
beryl-manager
sleep 4
exec gnome-session
</pre>

Save the file and close. Now we need to make the file executable:

: {{cmduser|sudo chmod a+x /usr/local/bin/startxgl.sh}}

All that's left now is to create a login script which makes gnome use the 3D effects. In a terminal, type:

: {{cmduser|sudo gedit /usr/share/xsessions/xgl.desktop}}

Now, in this file paste:

<pre>
[Desktop Entry]
Encoding=UTF-8
Name=Xgl
Exec=/usr/local/bin/startxgl.sh
Icon=
Type=Application
</pre>

Save and close the file. Now type:

: {{cmduser|sudo gedit /usr/local/bin/start_beryl.sh}}

In this file, paste:

<pre>
#!/bin/bash
#
# Start beryl-manager within gnome-session
#
if [ `ps -A -o comm | grep -c '^Xgl$'` == "1" ]; then
DISPLAY=:1 beryl-manager
DISPLAY=:1 beryl-xgl
else echo "${0}: Error: beryl-manager not launched. Xgl not running?"
fi
</pre>

Now make the file executable:

: {{cmduser|sudo chmod a+x /usr/local/bin/start_beryl.sh}}

Now go to System - Preferences - Sessions, go to the Startup Programs tab, and click add, then type

: {{cmduser|/usr/local/bin/start_beryl.sh}}

Now, reboot your ThinkPad. When you come to the login screen, click the 'Sessions' button on the bottom left corner, and select XGL. login, et voila! beautiful 3D effects!

: Figure 11. Beryl's Cube effect
: [[Image:cube.jpg]]

If you have NetBeans installed, try launching it now. It probably won't work due to Beryl. Luckily, this is easily solved. Open a terminal and type:

: {{cmduser|sudo gedit /etc/environment}}

Then add the following line to the end of the file.

<pre>AWT_TOOLKIT="MToolkit"</pre>

Now save, close and reboot. Netbeans should now work!

===Problem: Can't add programs to session===

So you tried to add something to your startup programs, it shows up in the list, but it doesn't start up. You then launch the sessions program again, only to find your program has disappeared from the list. This problem is being caused by incorrect permissions in your home directory, and can happen on some occasions. To fix it, open a terminal and type the following:

: {{cmduser|sudo chown -R username:usergroup /home/username/.config/}}

Replace username with your username and usergroup with your group (by default, in Ubuntu your usergroup is the same as your username). Everything should be OK now!

===Problem: Virtual terminals not working===

One problem I had after installing the ATI drivers was that virtual terminals stopped working. Instead of seeing a console when pressing CTRL+ALT+F1...F6 I was seeing a yellow/orange garbled output. Luckily, solving this with ATI drivers is trivial. Open a terminal, and type:

: {{cmduser|sudo gedit /boot/grub/menu.lst}}

Find the line which says

<pre>#defoptions=quiet splash</pre>

and replace it with

<pre>#defoptions=quiet splash vga=791</pre>

Now, find the line which boots the kernel you are currently using, this is just under '## ## End Default Options ##. In the 'kernel' line, add:

<pre>vga=791</pre>

Before:

<pre>kernel /vmlinuz-2.6.17-10-generic root=/dev/sda7 ro quiet splash</pre>

After:

<pre>kernel /vmlinuz-2.6.17-10-generic root=/dev/sda7 ro quiet splash vga=791</pre>

Now save and exit the file, and reboot. Virtual terminals should now work. If you use Intel drivers, you're going to have to bite the bullet and remove the 'splash' keyword from both the defoptions and kernel lines. You'll lose the pretty bootup screen, but at least virtual terminals will work, which are important to recover a crashed system.

===Problem: I keep logging out!===

If you're using Beryl, and find that you keep getting logged out, you've just encountered one of Beryl's most annoying bugs. Shift+Backspace causes a logout. To fix this, open a terminal and type:

: {{cmduser|gedit /home/username/annoymenot.sh}}

Remember to replace 'username' with your username. Now, in this file type:

: {{cmduser|xmodmap -e "keycode 22 <nowiki>=</nowiki> BackSpace BackSpace Terminate_Server" }}

Save and close the file, and make it executable:

: {{cmduser|chmod 755 /home/username/annoymenot.sh}}

Now go to System - Preferences - Session, Startup Programs. Click add, and type

: {{cmduser|/home/username/annoymenot.sh}}

Logout and back in, problem solved! While you're at it, how about getting the start button to work? Go to System - Preferences - Keyboard - Layout Options - Alt/Win Key behaviour and select 'Super is mapped to Win keys (default)'.

===Desktop envy===

We're living in an age of desktop prettyness, and Linux can be just as pretty as MAC OS X or Vista. You've already got Beryl installed. Now go to Applications - Accesories - gDesklets. If the gDesklets entry is not there, make sure you install it, either using Synaptic or Automatix. Desklets are small programs you can add to your desktop, ala OS X's Deskbar or Vista's Sidebar. To make them start on boot, add gdesklets in System - Preferences - Sessions, Startup Programs.

Another cool program is cairo clock. Download it from http://macslow.thepimp.net/projects/cairo-clock/cairo-clock_0.3.2-1_i386.deb and install it by double-clicking. To make it start automatically, add it to your sessions as mentioned above. I've found the following command makes it work best for me:

<pre>cairo-clock -s -w 175 -g 175 -x 1219 -y 7 -t radium</pre>

Finally, make sure you click that Ruby icon in your notification area, it allows you to configure Beryl to do all sorts of cool stuff!

===Conclusion===

Well, that's about it! A dream Linux system on a dream laptop! Check out these cool technologies for an even better system:

* Beagle
* Tomboy
* Deskbar

===References===

* ATI on Ubuntu - https://help.ubuntu.com/community/BinaryDriverHowto/ATI
* Garbled Virtual Terminal Bug - https://launchpad.net/distros/ubuntu/+source/usplash/+bug/63558
* Beryl logout Bug - http://forum.beryl-project.org/viewtopic.php?p=1295&sid=6feedd09a7f01bca68feb05a5f2f033c
* Beryl Netbeans Bug - http://ubuntuforums.org/showthread.php?t=252594
* Beryl on Ubuntu - http://wiki.beryl-project.org/index.php/Install/Ubuntu/Edgy/XGL
* Home directory permissions bug - http://www.ubuntuforums.org/showthread.php?p=1789997
* gnome-bluetooth bug - https://launchpad.net/distros/ubuntu/+source/gnome-bluetooth/+bug/70718

Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60

2006-12-20T07:27:06Z

Ischg: /* The fingerprint reader */

[[User:Keithvassallo|Keithvassallo]] 14:39, 16 December 2006 (CET)

===Abstract===

This article describes how to get Ubuntu Linux 6.10 (Edgy) installed on an IBM/Lenovo ThinkPad T60. It's not meant to be a definite guide to installing Ubuntu (the Ubuntu Guide at http://www.ubuntuguide.org does a very good job of that). This article is meant to describe how to get most of the ThinkPad features working on Ubuntu system. It also discusses how to get Multimedia, some cool-looking effects such as Beryl, gDesklets and similar working on Ubuntu. Finally, we discuss some common problems encountered on Ubuntu and ThinkPads alike.

===My ThinkPad===

Although this guide should work on most recent ThinkPads, I cannot guarantee that. These are the specifications of my machine. The closer your specs are, the greater the chance of success.

: Figure 1. ThinkPad T60 2007, complete with Tux sticker :-)
: [[Image:thinkpad.jpg]]

* Lenovo ThinkPad T60 2007.
* Intel Centrino Duo T2400 / 1.83 GHz.
* Mobile Intel 945PM Express Chipset.
* Intel Wireless LAN.
* Integrated Bluetooth.
* ATI Mobility Radeon X1400 - PCI Express x16, 128MB dedicated RAM.
* 100 GB - Serial ATA-150 Hard Drive.
* 15' TFT Active Matrix Display (1400x1050).

That's basically all you need to know. As far as I know, all other features are common to all ThinkPads manufactured by Lenovo since they acquired IBM's computer business.

===Why Ubuntu? (or rather, Why not SUSE?)===

In June 2006, Lenovo announced it would be shipping ThinkPad T60p laptops with SUSE Linux Enterprise Desktop (SLED) 10 pre-installed, since SLED apparently supports all of the features of the T60p. I contacted my local IBM supplier, who said that Lenovo were no longer manufacturing the T60p, since the company which was making the displays went out of business. This meant I could not get a T60p with SLED pre-installed. I decided to go for the T60 2007, which is the closest thing I could find to the T60p. This comes with Windows XP Professional pre-installed.

I first tried to get SLED installed on the T60. Although it did indeed install, and most features worked, I soon got bored of SLED. Firstly, SLED uses Gnome 2.12, which is by now ancient. Secondly, although the Lenovo utilities do work on SLED, they only work well if you use KDE as your defauly desktop environment, which is a pity since I'm a Gnome user. The utilities were very unstable to me too. Finally, what made me give up SLED was the usual problem - it's an RPM based distribution. Once you start using Debian derivatives, with their apt based installer, you won't want to go back. That's when I decided to try Ubuntu, and have not regretted it since.

===What Works?===

* Ubuntu and all programs it comes with.
* Most of the function keys, except the ones mentioned below
* The fingerprint reader.
* The ATI proprietary graphics drivers.
* Suspend to RAM (Sleep) and Suspend to Disk (Hibernate).
* Brightness, Volume and Mute with OSD (On-Screen Display).
* ThinkLight, TrackPoint II and the touchpad.

===What Doesn't Work? (Known Issues)===

* FN+F8, FN+F9, FN+ZOOM.
* The BACK and FORWARD buttons (next to the cursor keys).
* The ThinkVantage button (in Linux, still works on boot).
* Sending files to Bluetooth devices via GUI.

There are probably ways and means to get the offending buttons to work, I've tried several fora but none seem to address my exact problem. I'll update this article should I find out anything.

===First Things First - Creating a Windows Recovery Disc===

If you've purchased a T60, chances are it came with Windows XP Professional. The other option is for you to have FreeDOS installed, in which case you can skip this section. You could remove the Windows partition altogether, and reserve your ThinkPad for Linux, but that's not the route I've chosen. The ThinkVantage utilities in Windows allow you to do a lot of cool things, such as set-up a boot-up fingerprint security scan. You can't do this from Linux (as far as I know) so it's best to leave the Windows partition in place. So, boot your ThinkPad and complete the Windows XP setup (which asks you to add a user account and enroll yourself using the ThinkVantage Client Security Solution). While you're there, use the ThinkVantage productivy centre to enroll your fingerprint (I suggest enrolling more than one) and make sure you check the option to require a fingerprint scan on boot (not for security, for geek points). When you reboot, press ESC or F2 to get to BIOS, and make sure you check the option to require a supervisor password. This will make your ThinkPad prompt you for your fingerprint when you power it up.

: Figure 2. Configuring fingerprint security from Windows
: [[Image:winprint.jpg]]

Now that's working, you should create a recovery DVD using the ThinkVantage recovery utilities. This will allow you to recover your Windows installation should you manage to screw your partitions up in the following stages. I highly recommend you do this, as Lenovo does not provide Windows XP CDs with this Laptop - so the hard disk partition is all you've got. Once this is done, we're ready to install Ubuntu!

: Figure 3. Creating recovery discs from Windows
: [[Image:recovery.jpg]]

===Getting Ubuntu installed===

Download the latest Edgy live CD from the Ubuntu website, you can find a list of mirrors at http://www.ubuntu.com/products/GetUbuntu/download#currentrelease. You may also try Kubuntu, Edubuntu or any of it's derivatives, but I'll stick with Ubuntu here for simplicity's sake. Once that's downloaded, burn the ISO to disc using any program of your choice (If this is your first Linux experience and you're using Windows, try using Nero - http://www.nero.com).

Once the burning process is complete, reboot your machine ensuring that the Ubuntu CD is in the drive. You should see an Ubuntu menu. If you don't, your BIOS is not set to boot from CD. Reboot your ThinkPad and change the boot order from BIOS (by default ThinkPads boot from CD-ROM before the hard disk, so this is probably not necessary). Once the menu shows up, select 'Start or install Ubuntu' and let it boot. This will take a while as everything is loaded from CD. You should eventually end up in a Gnome desktop. If you see an error about the Gnome Settings Daemon not being able to load, simply ignore it, as this is not necessary for now. For the purposes of the installation, it's best if you have a wired ethernet connection, as it's unlikely the wireless network card will work until we boot into our installed Ubuntu system.

: Figure 4. Select the first option to start Ubuntu
: [[Image:boot.jpg]]

Double-Click on the 'install' icon on the Desktop to start installation. The installation should be pretty straight-forward. If you need additional help, check out the walk-through with screen-shots at http://www.debianadmin.com/ubuntu-edgy-eft-desktop-installation-with-screenshots.html. The only stage at which we need to make changes is the partitioning stage. This to make sure we preserve our Windows partition, and the IBM vendor_diag partition which allows recovery of the laptop when things go hay-wire. In the 'Prepare disk space' section of the installer, select the third option, 'Manually edit partition table'. A bar will be displayed showing your existing partitions. If you have Windows installed you will see two partitions. The first is a 4.89 GB IBM Vendor Diagnostic partition, which we do not want to touch. The second will be your Windows partition, which will fill the rest of the disk. Click on this partition, Then click the 'Resize/Move' button. I resized my Windows partition to 24 GB. This is enough to accommodate the 10 GB already in use on that partition, as well as giving Windows another 14 GB of free space. 6 GB of free space would probably be enough though.

Now it's time to create partitions for Linux. You need at least two partitions; a swap partition which should be roughly double the amount of RAM you have, and a root partition to install Linux. I opted for four partitions, as follows:

<table border=1>
<tr><td>'''Purpose'''</td><td>'''Size'''</td><td>'''File-System'''</td></tr>
<tr><td>Swap</td><td>2 GB</td><td>swap</td></tr>
<tr><td>/boot</td><td>5 GB</td><td>ext3</td></tr>
<tr><td>/ (root)</td><td>20 GB</td><td>ext3</td></tr>
<tr><td>/home</td><td>37.25 GB (what's left of the disk)</td><td>ext3</td></tr>
</table>

To create these paritions, click on the 'New' button and select 'Extended Partition' in the 'create as' drop-down list. Leave all other settings as-is, and click 'Add'. Now, click on the newly created partition, and create each of the partitions you want to create, simply specify the size of the partition in the 'New Size (MiB)' text box. To convert GB to MiB, multiply by 1024. So for your swap partition you should specify a size of 2048. Repeat until you have created all the required partitions. If you follow my parition layout, the partition editor should look something like Figure 5.

: Figure 5. Our partitions, ready to be created
: [[Image:partitioning.jpg]]

You will not see mount-points in your diagram, because the screen-shot above was taken after they were assigned, but you should get the general idea. After this screen, you will be asked to assign mount-points to the partitions you have just created. If you created the partitions in the same order I did, you can assign mount points as I have (i.e. /dev/sda5 for swap, /dev/sda6 for /boot, /dev/sda7 for /, /dev/sda8 for /home). Additionally, I mounted my Windows partition as /media/sda1 and my IBM Vendor Diagnostic partition as /media/sda2. These are optional. After this step, continue installation as normal. When the installation is complete, click the 'reboot' button to restart into your fresh Ubuntu System.

When booting, the GRUB boot-loader will be displayed, asking you what you want to load. You will probably see four options. The first two being Ubuntu Linux and Ubuntu Linux recovery mode (showing the kernel version). The other two will be Microsoft Windows XP, and 'Other Windows XP/2000/NT' partition. This is your IBM Vendor Diagnostic partition, which is based on the Windows kernel, apparently. Select the first entry to boot Ubuntu. The next time you boot Windows, it will bring up a chkdsk screen. This is entirely normal and happens because we have resized the Windows partition. Make sure you do not skip this check and let it complete.

===Wireless LAN===

The first thing we should do is to get wireless networking working. Luckily, getting the Centrino wireless LAN chip working in Ubuntu is quite easy, if you use the gnome-network-manager applet. Just go to System - Administration - Synaptic Package Manager. Then click 'Search' and set the 'look-in' field to 'name'. In the 'Search' text box type:

<pre>network-manager</pre>

: Figure 6. Installing the network manager applet
: [[Image:networkmanager.jpg]]

Click on the box beside 'network-manager' and click 'Mark for installation'. Do the same for 'network-manager-gnome'. Once installed, reboot your thinkpad. An applet will show up in the gnome notification area. Click on it, and a list of detected wireless networks will be displayed. Simply click on one of them, enter any authentication details necessary, and you'll be connected to the wireless network.

: Figure 7. gnome-network-manager showing available wireless networks
: [[Image:available-accesspoints.jpg]]

Note! Not all versions of the T60 has the Intel Wireless LAN as described above. Run lspci from the command line and look for details of your wifi card. E.g.:

03:00.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)

suggest you have a different wifi card. Read this forum thread http://ubuntuforums.org/showthread.php?t=38972

running:
# dmesg | grep hal

may yield output like this, which apparently suggests the hardware abstraction layer is in place.
[17179590.420000] ath_hal: module license 'Proprietary' taints kernel.
[17179590.424000] ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)

If not, or if the output contains "HAL Status 13" it apparently suggests your card is not supported by the current drivers, and you need to upgrade.

===Installing the ATI display drivers===

If your ThinkPad has an Intel graphics adapter, you should skip this section as Ubuntu installs the best driver automatically. Ubuntu does not install the ATI proprietary drivers by default because they are, er, proprietary. Luckily, installing them is easy enough. Open a terminal (Applications - Accessories - Terminal) and type the following:

: {{cmduser| sudo apt-get update}}
: {{cmduser| sudo apt-get install xorg-driver-fglrx fglrx-control}}

Now we make sure the proprietary driver is not disabled by the kernel. Type the following, and remove any lines referring to fglrx

: {{cmduser|sudo gedit /etc/default/linux-restricted-modules-common}}

An alternative to gedit (Gnome) is nano (sudo nano -w /etc...) for a CLI editor.

Finally, we need to configure the X server to use the ATI drivers. Type the following:

: {{cmduser|sudo depmod -a}}
: {{cmduser|sudo aticonfig --initial}}
: {{cmduser|sudo aticonfig --overlay-type<nowiki>=</nowiki>Xv}}

One last thing. In order to correct a very common problem of getting a jerky video display, type the following:

: {{cmduser|sudo gedit /etc/X11/xorg.conf}}

Scroll to the end of the file, and add the text below.

<pre>
Section "Extensions"
Option "Composite" "0"
EndSection
</pre>

Save the file and exit. Now, to apply the changes either press CTRL+ALT+Backspace or reboot. The resolution should have switched to 1400x1050 and everything should look prettier and render faster. Just to make sure everything is working, open up a terminal and type

: {{cmduser|fglrxinfo}}

This should display:

<pre>
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Mobility Radeon X1400 Generic
OpenGL version string: 2.0.6011 (8.28.8)
</pre>

The above is what I get on my ThinkPad, and you should see something similar. As long as you see your graphics card model listed, everything should be OK. If, instead, you see a bunch of lines containing 'Mesa' then you have a problem. In that case, I recommend consulting https://help.ubuntu.com/community/BinaryDriverHowto/ATI and the Ubuntu forums at http://ubuntuforums.org

===The fingerprint reader===

Although IBM does not officially support it, the fingerprint reader does in fact work with most Linux distributions. Getting it to work with Ubuntu can be a bit of a pain, but it does work. Basically, a bioAPI plugin is provided for PAM. PAM-aware applications such as GDM and gnome-screensaver will then automatically use the fingerprint reader, which is uber cool. Anyway, enough theory, I've probably lost the newbies amongst you already. Go to http://www.qrivy.net/~michael/temp/ and download the latest bioapi package (at the time of writing, bioapi_1.2.3_i386.deb). When asked, tell Firefox to open the file with the GDebi package installer.

That will install bioAPI. What we need now is the driver for our fingerprint device, which is manufactured by UPEK. Go to http://www.upek.com/support/dl_linux_bsp.asp and download the latest version, currently UPEK_BSP_LIN_1.0.zip. Extract this file, then open a terminal (and don't close it until I say so).

: {{cmduser|cd /path/to/where/you/extracted/the/file}}
: {{cmduser|sudo bash}}
: {{cmdroot|sh install.sh /usr/lib}}

Now we need to assign the right permissions so non-root applications can use the driver:

: {{cmdroot|addgroup --system bioapi}}
: {{cmdroot|addgroup --system usbfs}}
: {{cmdroot|adduser yourusername bioapi}}
: {{cmdroot|adduser yourusername usbfs}}
: {{cmdroot|chown -R root:bioapi /usr/var/bioapi/}}
: {{cmdroot|chmod -R 770 /usr/var/bioapi/}}
: {{cmdroot|chown -R root:usbfs /proc/bus/usb}}
: {{cmdroot|chmod -R g+X /proc/bus/usb}}

Of course, replace 'yourusername' with the username you use to login. Now, we need to set the usb file system (usbfs) to be usable by users in the usbfs group. To do this, we need to determine the group ID of the usbfs group. Type the following:

: {{cmdroot|cat /etc/group | grep usbfs | cut -d':' -f 3}}

In my case the number is 116, it might be different for you. Now, open the file /etc/fstab:

: {{cmdroot|gedit /etc/fstab}}

and type the following:

<pre>none /proc/bus/usb usbfs defaults,devgid=116,devmode=0660,busgid=116,busmode=0770,listgid=116,listmode=0660 0 0</pre>

Please type the above code in one line in your file. Remember to replace 116 if you got a different number with the previous cat command. The last permission-related thing we need to fool around with is UDEV. Open the udev permissions file

: {{cmdroot|gedit /etc/udev/rules.d/40-permissions.rules}}

and find the line:

<pre>SUBSYSTEM=="usb_device", MODE="0664"</pre>

It's line 65 in my file. Change it so it looks like this:

<pre>SUBSYSTEM=="usb_device", MODE="0660", GROUP="usbfs"</pre>

Now we need to enroll our fingerprint with the system. To do this, we need a utility called Sample, which is only distributed in source-code form with the driver. This is great, only I couldn't get it to compile on Ubuntu. Luckily, there is a binary version available from one of the earlier releases of the driver (beta 2). To get this, download it from ftp://linux:Tuc-nak3@delta.upek.com/TFMESS_BSP_LIN_1.0beta2.zip. Now, extract the file and type:

: {{cmdroot|cd /path/to/where/you/extracted/the/archive}}
: {{cmdroot|cd NonGUI_sample}}
: {{cmdroot|chmod a+x Sample}}
: {{cmdroot|./Sample}}

Press (e) to enroll a new user, and enter your username when asked for the user ID. You will be asked to swipe your finger three times. Now press (v) and swipe your finger, a green check should be displayed showing you have successfully authenticated.

: Figure 8. The fingerprint swipe prompt
: [[Image:touchchip.jpg]]

Wonderful! Now, quit the application (q) and type exit to become a normal user. A file called yourusername.bir should have been created, copy this to your home directory:

: {{cmdroot|cp yourusername.bir /home/yourusername/}}

You can now close the terminal window. The next step is to install the BioAPI plug-in for PAM, and to make applications use the plugin. So, get the pam_bioapi plugin from http://www.nax.cz/pub/bioapi/pam_bioapi/pam-bioapi_0.3.0.tar.gz and extract it. Now open a terminal and type:

: {{cmduser|cd /path/to/where/you/extracted/the/arcive}}
: {{cmduser|./configure --libdir<nowiki>=</nowiki>/lib --enable-file-store && make}}
: {{cmduser|sudo make install}}

Comment: you will have to install some libraries in order to be able to compile the plugin

: {{cmduser|sudo apt-get install build-essential}}
: {{cmduser|sudo apt-get install libpam0g-dev}}

That's installed the plugin. Now, open a terminal and type the following scary commands: (Note: The line starting 'SERIAL=' and the line following it should be in the same line).

: {{cmduser|cd ~}}
: {{cmduser|sudo bash}}
: {{cmdroot|SERIAL=`BioAPITest | sed -ne "/Fingerprint/{n;n;s/^.*: $.\{9\}$$.\{4\}$$.\{4\}$$.\{4\}$$.*$/\1-\2-\3-\4-\5/gp}"`}}
: {{cmdroot|mkdir -p /etc/bioapi/pam/$SERIAL}}
: {{cmdroot|cp yourusername.bir /etc/bioapi/pam/$SERIAL}}
: {{cmdroot|exit}}

Phew. Now, to make applications actually use the fingerprint reader. Open a terminal window, and type:

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

Delete everything in the file, and paste this instead:

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

Save and close the file. That will make all PAM-aware applications use the fingerprint reader. Unfortunately, this also includes sudo. Since sudo is a command line application, it will display prompts in a terminal for you to swipe your finger, which is all well and good. The problem with this is that many Ubuntu administrative applications (such as Synaptic) use gksu to present a graphical front-end to sudo, which will output messages on the command line which you'll never see. Result? Administrative programs won't work from the gnome menu. The solution is to make sudo use the good old password. Open a terminal and type:

: {{cmduser|sudo gedit /etc/pam.d/sudo}}

Delete everything in the file, and instead paste:

<pre>
#%PAM-1.0

#@include common-auth
auth required pam_unix.so nullok_secure
@include common-account
</pre>

Now, save the file and close it, and reboot your system. GDM will ask you for a username, and then show a pretty prompt where you can scan your fingerprint! Same goes for gnome-screensaver when you set it to lock. Sometimes gnome-screensaver will not display the prompt, but you should still swipe your finger and be able to log back in.

===Bluetooth with Mobile Phones/PDAs===

Rather strangely, Ubuntu seems to have taken a step backwards with Bluetooth useability in Edgy. What worked out of the box with Dapper, now requires configuratio. First, open System - Preferences - Sessions and go to the Startup Programs tab. Then, find the entry labelled 'bt-applet --sm-disable'. Highlight it and click disable. Click add and in the command field type 'bt-applet'. Repeat this process, adding an entry for 'gnome-obex-server'. Now, open Synaptic Package Manager (System - Administration - Synaptic Package Manager) and click Search. Type 'gnome-bluetooth' to find the package, then mark it for installation. Now repeat this process for 'bluez-passkey-gnome'. Click apply to make changes.

Now that everything is installed, log-out of Gnome and log back in again. From your phone/PDA, search for devices untill you see your ThinkPad (the hostname will be displayed). Pair with the device. When asked for a passkey, enter 1234, which is the default. If you want to change your passkey (and you should), open a terminal and type:

: {{cmduser|sudo gedit /etc/bluetooth/hcid.conf}}

Find the line which says 'Default PIN for incoming connections' and change the PIN on the line beneath it:

<pre>
# Default PIN code for incoming connections
passkey "4017";
</pre>

Save and close the file, then type:

: {{cmduser|sudo /etc/init.d/bluetooth restart}}

You will now be able to use your new PIN code. To send files from your device to the ThinkPad, simply select the file you want to send and click Send Via Bluetooth (or whatever option your device presents). A dialog will pop-up in Gnome showing you a new file has been received.

: Figure 9. Gnome informing us that a file has been received
: [[Image:bluetooth.jpg]]

Sending files from your ThinkPad to your device requires more effort. The way it should work is that you right-click on a file, click send to, then make sure 'Bluetooth (OBEX)' is selected. Your device should be displayed and you could just click send. Unfortunately, due to a bug in gnome-bluetooth (described in https://launchpad.net/distros/ubuntu/+source/gnome-bluetooth/+bug/70718) this method does not work. If it does work for you, the bug has been solved and you can skip the rest of this section.

Your only other option is to use the command line to send files to your device. Open a terminal, then type:

: {{cmduser|hcitool scan}}

A list of detected bluetooth devices will be shown, for example, my output shows the following:

<pre>
Scanning ...
00:09:DD:60:02:EB Photosmart 8100 series
00:14:A7:99:3C:1F ThElInK
</pre>

The first field is the MAC address of the device, the second is the name of the device. In this case my bluetooth printer and mobile phone (ThElInK) were detected. In order to send files to my phone, I use:

: {{cmduser|gnome-obex-send -d 00:14:A7:99:3C:1F myPicture.jpg}}

Replace the MAC address with that of your device and myPicture.jpg with the file you want to send.

===TrackPoint Scrolling===

By default you can use the right and bottom edges of your touchpad to scroll through documents. If you use the TrackPoint instad of the touchpad (and believe me, you should), you'll find that scrolling is disabled by default. To enable it, open a terminal and type:

: {{cmduser|sudo gedit /etc/X11/xorg.conf}}

Now find the entry for your TrackPoint device. In my configuration file, the TrackPoint entry is the first mouse entry, after the keyboard entry, and looks something like this:

<pre>
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection
</pre>

Right after this entry is my touchpad entry. My entry is on line 66, but yours may be different. Now, add the follwing two options in that InputDevice section:

<pre>
Option "EmulateWheel" "on"
Option "EmulateWheelButton" "2"
</pre>

Save and exit the file. Restart your ThinkPad (or logout, and press CTRL-ALT-BACKSPACE). You should now be able to scoll by holding down the middle button for your TrackPoint and using the TrackPoint to scroll.

===Getting Multimedia to Work===

Due to patents and similar legal crap, Ubuntu will not play most media files by default. You also won't get browser plugins for multimedia. Luckily, this is easily fixed. Open a terminal and type the following:

: {{cmduser|sudo cp /etc/apt/sources.list /etc/apt/sources.list.backup}}
: {{cmduser|sudo gedit /etc/apt/sources.list}}

Delete everything in the file, and instead paste the following:

<pre>
deb-src http://archive.ubuntu.com/ubuntu edgy main restricted universe multiverse
#deb http://archive.ubuntu.com/ubuntu edgy-proposed main restricted universe multiverse

## MAJOR BUG FIX UPDATES produced after the final release
deb-src http://archive.ubuntu.com/ubuntu edgy-updates main restricted universe multiverse

## UBUNTU SECURITY UPDATES
deb http://security.ubuntu.com/ubuntu edgy-security main restricted universe multiverse
deb-src http://security.ubuntu.com/ubuntu edgy-security main restricted universe multiverse

## BACKPORTS REPOSITORY (Unsupported. May contain illegal packages. Use at own risk.)
#deb http://archive.ubuntu.com/ubuntu edgy-backports main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu edgy-backports main restricted universe multiverse

## PLF REPOSITORY
deb http://packages.freecontrib.org/ubuntu/plf edgy-plf free
deb-src http://packages.freecontrib.org/ubuntu/plf edgy-plf free
deb http://packages.freecontrib.org/ubuntu/plf edgy-plf non-free
deb-src http://packages.freecontrib.org/ubuntu/plf edgy-plf non-free

## CANONICAL COMMERCIAL REPOSITORY (Hosted on Canonical servers, not Ubuntu
## servers. RealPlayer10, Opera, DesktopSecure and more to come.)
deb http://archive.canonical.com/ubuntu edgy-commercial main

## Listen
#deb http://theli.free.fr/packages/ edgy listen

## Automatix repo
deb http://www.getautomatix.com/apt edgy main
</pre>

Now, open a terminal and type the following:

: {{cmduser|wget http://packages.freecontrib.org/ubuntu/plf/12B83718.gpg -O- | sudo apt-key add -}}
: {{cmduser|wget http://www.getautomatix.com/apt/key.gpg.asc}}
: {{cmduser|gpg --import key.gpg.asc}}
: {{cmduser|gpg --export --armor 521A9C7C | sudo apt-key add -}}
: {{cmduser|sudo apt-get update}}
: {{cmduser|sudo apt-get install automatix2}}
: {{cmduser|wget http://easyubuntu.freecontrib.org/files/easyubuntu-3.023.tar.gz}}
: {{cmduser|tar -zxf easyubuntu-3.023.tar.gz}}
: {{cmduser|cd easyubuntu}}
: {{cmduser|cp packagelist-dapper.pot packagelist-edgy.pot}}
: {{cmduser|cp packagelist-dapper.xml packagelist-edgy.xml}}
: {{cmduser|sudo python easyubuntu.in}}

Don't worry if you get errors from the Ubuntu PLF repository. PLF mirrors are about as stable as wild bull in a farm full of cows. Select what you want to install from the resulting window. Make sure you do not select the totem-mozilla plugin, as this just doens't work, for me at least. When EasyUbuntu has finished installing packages, you should be returned to a terminal, which you can close. Now go to Applications - System Tools - Automatix. Read and agree to the warning. Check what you want to install. Make sure you check 'Mplayer and FF plugin'. When ready, click the 'install' button. That should get multimedia working nicely.

: Figure 10. The Automatix user interface
: [[Image:automatix.jpg]]

===Beryl - fancy 3D desktop===

MAC OS X has Aqua and Windows Vista has Aero. Well, Linux has XGL/Beryl which can get effects which are as good looking (or sometimes better!) than the former two. Installing Beryl on Ubuntu is not that hard. First, open a terminal and type the following:

: {{cmduser|sudo gedit /etc/apt/sources.list}}

At the end of the file, append the following:

<pre>
##Beryl
deb http://ubuntu.beryl-project.org/ edgy main
</pre>

Save and close the file. Now type:

: {{cmduser|wget http://beryl-mirror.lupine.me.uk/1609B551.gpg -O- | sudo apt-key add -}}
: {{cmduser|sudo apt-get update}}

ATI Users Only: type

: {{cmduser|sudo apt-get install xserver-xgl}}

Now, to install beryl:

: {{cmduser|sudo apt-get install beryl emerald-themes}}

To make Ubuntu use the 3D effects. Open a terminal:

: {{cmduser|sudo gedit /usr/local/bin/startxgl.sh}}

In that file, paste the following if you use an ATI card:

<pre>
#!/bin/sh
Xgl -fullscreen :1 -ac -br -accel glx:pbuffer -accel xv:pbuffer &
sleep 4
export DISPLAY=:1
exec gnome-session
</pre>

If you use an Intel card, paste the following instead:

<pre>
#!/bin/sh
beryl-manager
sleep 4
exec gnome-session
</pre>

Save the file and close. Now we need to make the file executable:

: {{cmduser|sudo chmod a+x /usr/local/bin/startxgl.sh}}

All that's left now is to create a login script which makes gnome use the 3D effects. In a terminal, type:

: {{cmduser|sudo gedit /usr/share/xsessions/xgl.desktop}}

Now, in this file paste:

<pre>
[Desktop Entry]
Encoding=UTF-8
Name=Xgl
Exec=/usr/local/bin/startxgl.sh
Icon=
Type=Application
</pre>

Save and close the file. Now type:

: {{cmduser|sudo gedit /usr/local/bin/start_beryl.sh}}

In this file, paste:

<pre>
#!/bin/bash
#
# Start beryl-manager within gnome-session
#
if [ `ps -A -o comm | grep -c '^Xgl$'` == "1" ]; then
DISPLAY=:1 beryl-manager
DISPLAY=:1 beryl-xgl
else echo "${0}: Error: beryl-manager not launched. Xgl not running?"
fi
</pre>

Now make the file executable:

: {{cmduser|sudo chmod a+x /usr/local/bin/start_beryl.sh}}

Now go to System - Preferences - Sessions, go to the Startup Programs tab, and click add, then type

: {{cmduser|/usr/local/bin/start_beryl.sh}}

Now, reboot your ThinkPad. When you come to the login screen, click the 'Sessions' button on the bottom left corner, and select XGL. login, et voila! beautiful 3D effects!

: Figure 11. Beryl's Cube effect
: [[Image:cube.jpg]]

If you have NetBeans installed, try launching it now. It probably won't work due to Beryl. Luckily, this is easily solved. Open a terminal and type:

: {{cmduser|sudo gedit /etc/environment}}

Then add the following line to the end of the file.

<pre>AWT_TOOLKIT="MToolkit"</pre>

Now save, close and reboot. Netbeans should now work!

===Problem: Can't add programs to session===

So you tried to add something to your startup programs, it shows up in the list, but it doesn't start up. You then launch the sessions program again, only to find your program has disappeared from the list. This problem is being caused by incorrect permissions in your home directory, and can happen on some occasions. To fix it, open a terminal and type the following:

: {{cmduser|sudo chown -R username:usergroup /home/username/.config/}}

Replace username with your username and usergroup with your group (by default, in Ubuntu your usergroup is the same as your username). Everything should be OK now!

===Problem: Virtual terminals not working===

One problem I had after installing the ATI drivers was that virtual terminals stopped working. Instead of seeing a console when pressing CTRL+ALT+F1...F6 I was seeing a yellow/orange garbled output. Luckily, solving this with ATI drivers is trivial. Open a terminal, and type:

: {{cmduser|sudo gedit /boot/grub/menu.lst}}

Find the line which says

<pre>#defoptions=quiet splash</pre>

and replace it with

<pre>#defoptions=quiet splash vga=791</pre>

Now, find the line which boots the kernel you are currently using, this is just under '## ## End Default Options ##. In the 'kernel' line, add:

<pre>vga=791</pre>

Before:

<pre>kernel /vmlinuz-2.6.17-10-generic root=/dev/sda7 ro quiet splash</pre>

After:

<pre>kernel /vmlinuz-2.6.17-10-generic root=/dev/sda7 ro quiet splash vga=791</pre>

Now save and exit the file, and reboot. Virtual terminals should now work. If you use Intel drivers, you're going to have to bite the bullet and remove the 'splash' keyword from both the defoptions and kernel lines. You'll lose the pretty bootup screen, but at least virtual terminals will work, which are important to recover a crashed system.

===Problem: I keep logging out!===

If you're using Beryl, and find that you keep getting logged out, you've just encountered one of Beryl's most annoying bugs. Shift+Backspace causes a logout. To fix this, open a terminal and type:

: {{cmduser|gedit /home/username/annoymenot.sh}}

Remember to replace 'username' with your username. Now, in this file type:

: {{cmduser|xmodmap -e "keycode 22 <nowiki>=</nowiki> BackSpace BackSpace Terminate_Server" }}

Save and close the file, and make it executable:

: {{cmduser|chmod 755 /home/username/annoymenot.sh}}

Now go to System - Preferences - Session, Startup Programs. Click add, and type

: {{cmduser|/home/username/annoymenot.sh}}

Logout and back in, problem solved! While you're at it, how about getting the start button to work? Go to System - Preferences - Keyboard - Layout Options - Alt/Win Key behaviour and select 'Super is mapped to Win keys (default)'.

===Desktop envy===

We're living in an age of desktop prettyness, and Linux can be just as pretty as MAC OS X or Vista. You've already got Beryl installed. Now go to Applications - Accesories - gDesklets. If the gDesklets entry is not there, make sure you install it, either using Synaptic or Automatix. Desklets are small programs you can add to your desktop, ala OS X's Deskbar or Vista's Sidebar. To make them start on boot, add gdesklets in System - Preferences - Sessions, Startup Programs.

Another cool program is cairo clock. Download it from http://macslow.thepimp.net/projects/cairo-clock/cairo-clock_0.3.2-1_i386.deb and install it by double-clicking. To make it start automatically, add it to your sessions as mentioned above. I've found the following command makes it work best for me:

<pre>cairo-clock -s -w 175 -g 175 -x 1219 -y 7 -t radium</pre>

Finally, make sure you click that Ruby icon in your notification area, it allows you to configure Beryl to do all sorts of cool stuff!

===Conclusion===

Well, that's about it! A dream Linux system on a dream laptop! Check out these cool technologies for an even better system:

* Beagle
* Tomboy
* Deskbar

===References===

* ATI on Ubuntu - https://help.ubuntu.com/community/BinaryDriverHowto/ATI
* Garbled Virtual Terminal Bug - https://launchpad.net/distros/ubuntu/+source/usplash/+bug/63558
* Beryl logout Bug - http://forum.beryl-project.org/viewtopic.php?p=1295&sid=6feedd09a7f01bca68feb05a5f2f033c
* Beryl Netbeans Bug - http://ubuntuforums.org/showthread.php?t=252594
* Beryl on Ubuntu - http://wiki.beryl-project.org/index.php/Install/Ubuntu/Edgy/XGL
* Home directory permissions bug - http://www.ubuntuforums.org/showthread.php?p=1789997
* gnome-bluetooth bug - https://launchpad.net/distros/ubuntu/+source/gnome-bluetooth/+bug/70718

Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60

2006-12-20T07:13:50Z

Ischg: /* The fingerprint reader */

[[User:Keithvassallo|Keithvassallo]] 14:39, 16 December 2006 (CET)

===Abstract===

This article describes how to get Ubuntu Linux 6.10 (Edgy) installed on an IBM/Lenovo ThinkPad T60. It's not meant to be a definite guide to installing Ubuntu (the Ubuntu Guide at http://www.ubuntuguide.org does a very good job of that). This article is meant to describe how to get most of the ThinkPad features working on Ubuntu system. It also discusses how to get Multimedia, some cool-looking effects such as Beryl, gDesklets and similar working on Ubuntu. Finally, we discuss some common problems encountered on Ubuntu and ThinkPads alike.

===My ThinkPad===

Although this guide should work on most recent ThinkPads, I cannot guarantee that. These are the specifications of my machine. The closer your specs are, the greater the chance of success.

: Figure 1. ThinkPad T60 2007, complete with Tux sticker :-)
: [[Image:thinkpad.jpg]]

* Lenovo ThinkPad T60 2007.
* Intel Centrino Duo T2400 / 1.83 GHz.
* Mobile Intel 945PM Express Chipset.
* Intel Wireless LAN.
* Integrated Bluetooth.
* ATI Mobility Radeon X1400 - PCI Express x16, 128MB dedicated RAM.
* 100 GB - Serial ATA-150 Hard Drive.
* 15' TFT Active Matrix Display (1400x1050).

That's basically all you need to know. As far as I know, all other features are common to all ThinkPads manufactured by Lenovo since they acquired IBM's computer business.

===Why Ubuntu? (or rather, Why not SUSE?)===

In June 2006, Lenovo announced it would be shipping ThinkPad T60p laptops with SUSE Linux Enterprise Desktop (SLED) 10 pre-installed, since SLED apparently supports all of the features of the T60p. I contacted my local IBM supplier, who said that Lenovo were no longer manufacturing the T60p, since the company which was making the displays went out of business. This meant I could not get a T60p with SLED pre-installed. I decided to go for the T60 2007, which is the closest thing I could find to the T60p. This comes with Windows XP Professional pre-installed.

I first tried to get SLED installed on the T60. Although it did indeed install, and most features worked, I soon got bored of SLED. Firstly, SLED uses Gnome 2.12, which is by now ancient. Secondly, although the Lenovo utilities do work on SLED, they only work well if you use KDE as your defauly desktop environment, which is a pity since I'm a Gnome user. The utilities were very unstable to me too. Finally, what made me give up SLED was the usual problem - it's an RPM based distribution. Once you start using Debian derivatives, with their apt based installer, you won't want to go back. That's when I decided to try Ubuntu, and have not regretted it since.

===What Works?===

* Ubuntu and all programs it comes with.
* Most of the function keys, except the ones mentioned below
* The fingerprint reader.
* The ATI proprietary graphics drivers.
* Suspend to RAM (Sleep) and Suspend to Disk (Hibernate).
* Brightness, Volume and Mute with OSD (On-Screen Display).
* ThinkLight, TrackPoint II and the touchpad.

===What Doesn't Work? (Known Issues)===

* FN+F8, FN+F9, FN+ZOOM.
* The BACK and FORWARD buttons (next to the cursor keys).
* The ThinkVantage button (in Linux, still works on boot).
* Sending files to Bluetooth devices via GUI.

There are probably ways and means to get the offending buttons to work, I've tried several fora but none seem to address my exact problem. I'll update this article should I find out anything.

===First Things First - Creating a Windows Recovery Disc===

If you've purchased a T60, chances are it came with Windows XP Professional. The other option is for you to have FreeDOS installed, in which case you can skip this section. You could remove the Windows partition altogether, and reserve your ThinkPad for Linux, but that's not the route I've chosen. The ThinkVantage utilities in Windows allow you to do a lot of cool things, such as set-up a boot-up fingerprint security scan. You can't do this from Linux (as far as I know) so it's best to leave the Windows partition in place. So, boot your ThinkPad and complete the Windows XP setup (which asks you to add a user account and enroll yourself using the ThinkVantage Client Security Solution). While you're there, use the ThinkVantage productivy centre to enroll your fingerprint (I suggest enrolling more than one) and make sure you check the option to require a fingerprint scan on boot (not for security, for geek points). When you reboot, press ESC or F2 to get to BIOS, and make sure you check the option to require a supervisor password. This will make your ThinkPad prompt you for your fingerprint when you power it up.

: Figure 2. Configuring fingerprint security from Windows
: [[Image:winprint.jpg]]

Now that's working, you should create a recovery DVD using the ThinkVantage recovery utilities. This will allow you to recover your Windows installation should you manage to screw your partitions up in the following stages. I highly recommend you do this, as Lenovo does not provide Windows XP CDs with this Laptop - so the hard disk partition is all you've got. Once this is done, we're ready to install Ubuntu!

: Figure 3. Creating recovery discs from Windows
: [[Image:recovery.jpg]]

===Getting Ubuntu installed===

Download the latest Edgy live CD from the Ubuntu website, you can find a list of mirrors at http://www.ubuntu.com/products/GetUbuntu/download#currentrelease. You may also try Kubuntu, Edubuntu or any of it's derivatives, but I'll stick with Ubuntu here for simplicity's sake. Once that's downloaded, burn the ISO to disc using any program of your choice (If this is your first Linux experience and you're using Windows, try using Nero - http://www.nero.com).

Once the burning process is complete, reboot your machine ensuring that the Ubuntu CD is in the drive. You should see an Ubuntu menu. If you don't, your BIOS is not set to boot from CD. Reboot your ThinkPad and change the boot order from BIOS (by default ThinkPads boot from CD-ROM before the hard disk, so this is probably not necessary). Once the menu shows up, select 'Start or install Ubuntu' and let it boot. This will take a while as everything is loaded from CD. You should eventually end up in a Gnome desktop. If you see an error about the Gnome Settings Daemon not being able to load, simply ignore it, as this is not necessary for now. For the purposes of the installation, it's best if you have a wired ethernet connection, as it's unlikely the wireless network card will work until we boot into our installed Ubuntu system.

: Figure 4. Select the first option to start Ubuntu
: [[Image:boot.jpg]]

Double-Click on the 'install' icon on the Desktop to start installation. The installation should be pretty straight-forward. If you need additional help, check out the walk-through with screen-shots at http://www.debianadmin.com/ubuntu-edgy-eft-desktop-installation-with-screenshots.html. The only stage at which we need to make changes is the partitioning stage. This to make sure we preserve our Windows partition, and the IBM vendor_diag partition which allows recovery of the laptop when things go hay-wire. In the 'Prepare disk space' section of the installer, select the third option, 'Manually edit partition table'. A bar will be displayed showing your existing partitions. If you have Windows installed you will see two partitions. The first is a 4.89 GB IBM Vendor Diagnostic partition, which we do not want to touch. The second will be your Windows partition, which will fill the rest of the disk. Click on this partition, Then click the 'Resize/Move' button. I resized my Windows partition to 24 GB. This is enough to accommodate the 10 GB already in use on that partition, as well as giving Windows another 14 GB of free space. 6 GB of free space would probably be enough though.

Now it's time to create partitions for Linux. You need at least two partitions; a swap partition which should be roughly double the amount of RAM you have, and a root partition to install Linux. I opted for four partitions, as follows:

<table border=1>
<tr><td>'''Purpose'''</td><td>'''Size'''</td><td>'''File-System'''</td></tr>
<tr><td>Swap</td><td>2 GB</td><td>swap</td></tr>
<tr><td>/boot</td><td>5 GB</td><td>ext3</td></tr>
<tr><td>/ (root)</td><td>20 GB</td><td>ext3</td></tr>
<tr><td>/home</td><td>37.25 GB (what's left of the disk)</td><td>ext3</td></tr>
</table>

To create these paritions, click on the 'New' button and select 'Extended Partition' in the 'create as' drop-down list. Leave all other settings as-is, and click 'Add'. Now, click on the newly created partition, and create each of the partitions you want to create, simply specify the size of the partition in the 'New Size (MiB)' text box. To convert GB to MiB, multiply by 1024. So for your swap partition you should specify a size of 2048. Repeat until you have created all the required partitions. If you follow my parition layout, the partition editor should look something like Figure 5.

: Figure 5. Our partitions, ready to be created
: [[Image:partitioning.jpg]]

You will not see mount-points in your diagram, because the screen-shot above was taken after they were assigned, but you should get the general idea. After this screen, you will be asked to assign mount-points to the partitions you have just created. If you created the partitions in the same order I did, you can assign mount points as I have (i.e. /dev/sda5 for swap, /dev/sda6 for /boot, /dev/sda7 for /, /dev/sda8 for /home). Additionally, I mounted my Windows partition as /media/sda1 and my IBM Vendor Diagnostic partition as /media/sda2. These are optional. After this step, continue installation as normal. When the installation is complete, click the 'reboot' button to restart into your fresh Ubuntu System.

When booting, the GRUB boot-loader will be displayed, asking you what you want to load. You will probably see four options. The first two being Ubuntu Linux and Ubuntu Linux recovery mode (showing the kernel version). The other two will be Microsoft Windows XP, and 'Other Windows XP/2000/NT' partition. This is your IBM Vendor Diagnostic partition, which is based on the Windows kernel, apparently. Select the first entry to boot Ubuntu. The next time you boot Windows, it will bring up a chkdsk screen. This is entirely normal and happens because we have resized the Windows partition. Make sure you do not skip this check and let it complete.

===Wireless LAN===

The first thing we should do is to get wireless networking working. Luckily, getting the Centrino wireless LAN chip working in Ubuntu is quite easy, if you use the gnome-network-manager applet. Just go to System - Administration - Synaptic Package Manager. Then click 'Search' and set the 'look-in' field to 'name'. In the 'Search' text box type:

<pre>network-manager</pre>

: Figure 6. Installing the network manager applet
: [[Image:networkmanager.jpg]]

Click on the box beside 'network-manager' and click 'Mark for installation'. Do the same for 'network-manager-gnome'. Once installed, reboot your thinkpad. An applet will show up in the gnome notification area. Click on it, and a list of detected wireless networks will be displayed. Simply click on one of them, enter any authentication details necessary, and you'll be connected to the wireless network.

: Figure 7. gnome-network-manager showing available wireless networks
: [[Image:available-accesspoints.jpg]]

Note! Not all versions of the T60 has the Intel Wireless LAN as described above. Run lspci from the command line and look for details of your wifi card. E.g.:

03:00.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)

suggest you have a different wifi card. Read this forum thread http://ubuntuforums.org/showthread.php?t=38972

running:
# dmesg | grep hal

may yield output like this, which apparently suggests the hardware abstraction layer is in place.
[17179590.420000] ath_hal: module license 'Proprietary' taints kernel.
[17179590.424000] ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)

If not, or if the output contains "HAL Status 13" it apparently suggests your card is not supported by the current drivers, and you need to upgrade.

===Installing the ATI display drivers===

If your ThinkPad has an Intel graphics adapter, you should skip this section as Ubuntu installs the best driver automatically. Ubuntu does not install the ATI proprietary drivers by default because they are, er, proprietary. Luckily, installing them is easy enough. Open a terminal (Applications - Accessories - Terminal) and type the following:

: {{cmduser| sudo apt-get update}}
: {{cmduser| sudo apt-get install xorg-driver-fglrx fglrx-control}}

Now we make sure the proprietary driver is not disabled by the kernel. Type the following, and remove any lines referring to fglrx

: {{cmduser|sudo gedit /etc/default/linux-restricted-modules-common}}

An alternative to gedit (Gnome) is nano (sudo nano -w /etc...) for a CLI editor.

Finally, we need to configure the X server to use the ATI drivers. Type the following:

: {{cmduser|sudo depmod -a}}
: {{cmduser|sudo aticonfig --initial}}
: {{cmduser|sudo aticonfig --overlay-type<nowiki>=</nowiki>Xv}}

One last thing. In order to correct a very common problem of getting a jerky video display, type the following:

: {{cmduser|sudo gedit /etc/X11/xorg.conf}}

Scroll to the end of the file, and add the text below.

<pre>
Section "Extensions"
Option "Composite" "0"
EndSection
</pre>

Save the file and exit. Now, to apply the changes either press CTRL+ALT+Backspace or reboot. The resolution should have switched to 1400x1050 and everything should look prettier and render faster. Just to make sure everything is working, open up a terminal and type

: {{cmduser|fglrxinfo}}

This should display:

<pre>
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Mobility Radeon X1400 Generic
OpenGL version string: 2.0.6011 (8.28.8)
</pre>

The above is what I get on my ThinkPad, and you should see something similar. As long as you see your graphics card model listed, everything should be OK. If, instead, you see a bunch of lines containing 'Mesa' then you have a problem. In that case, I recommend consulting https://help.ubuntu.com/community/BinaryDriverHowto/ATI and the Ubuntu forums at http://ubuntuforums.org

===The fingerprint reader===

Although IBM does not officially support it, the fingerprint reader does in fact work with most Linux distributions. Getting it to work with Ubuntu can be a bit of a pain, but it does work. Basically, a bioAPI plugin is provided for PAM. PAM-aware applications such as GDM and gnome-screensaver will then automatically use the fingerprint reader, which is uber cool. Anyway, enough theory, I've probably lost the newbies amongst you already. Go to http://www.qrivy.net/~michael/temp/ and download the latest bioapi package (at the time of writing, bioapi_1.2.3_i386.deb). When asked, tell Firefox to open the file with the GDebi package installer.

That will install bioAPI. What we need now is the driver for our fingerprint device, which is manufactured by UPEK. Go to http://www.upek.com/support/dl_linux_bsp.asp and download the latest version, currently UPEK_BSP_LIN_1.0.zip. Extract this file, then open a terminal (and don't close it until I say so).

: {{cmduser|cd /path/to/where/you/extracted/the/file}}
: {{cmduser|sudo bash}}
: {{cmdroot|sh install.sh /usr/lib}}

Now we need to assign the right permissions so non-root applications can use the driver:

: {{cmdroot|addgroup --system bioapi}}
: {{cmdroot|addgroup --system usbfs}}
: {{cmdroot|adduser yourusername bioapi}}
: {{cmdroot|adduser yourusername usbfs}}
: {{cmdroot|chown -R root:bioapi /usr/var/bioapi/}}
: {{cmdroot|chmod -R 770 /usr/var/bioapi/}}
: {{cmdroot|chown -R root:usbfs /proc/bus/usb}}
: {{cmdroot|chmod -R g+X /proc/bus/usb}}

Of course, replace 'yourusername' with the username you use to login. Now, we need to set the usb file system (usbfs) to be usable by users in the usbfs group. To do this, we need to determine the group ID of the usbfs group. Type the following:

: {{cmdroot|cat /etc/group | grep usbfs | cut -d':' -f 3}}

In my case the number is 116, it might be different for you. Now, open the file /etc/fstab:

: {{cmdroot|gedit /etc/fstab}}

and type the following:

<pre>none /proc/bus/usb usbfs defaults,devgid=116,devmode=0660,busgid=116,busmode=0770,listgid=116,listmode=0660 0 0</pre>

Please type the above code in one line in your file. Remember to replace 116 if you got a different number with the previous cat command. The last permission-related thing we need to fool around with is UDEV. Open the udev permissions file

: {{cmdroot|gedit /etc/udev/rules.d/40-permissions.rules}}

and find the line:

<pre>SUBSYSTEM=="usb_device", MODE="0664"</pre>

It's line 65 in my file. Change it so it looks like this:

<pre>SUBSYSTEM=="usb_device", MODE="0660", GROUP="usbfs"</pre>

Now we need to enroll our fingerprint with the system. To do this, we need a utility called Sample, which is only distributed in source-code form with the driver. This is great, only I couldn't get it to compile on Ubuntu. Luckily, there is a binary version available from one of the earlier releases of the driver (beta 2). To get this, download it from ftp://linux:Tuc-nak3@delta.upek.com/TFMESS_BSP_LIN_1.0beta2.zip. Now, extract the file and type:

: {{cmdroot|cd /path/to/where/you/extracted/the/archive}}
: {{cmdroot|cd NonGUI_sample}}
: {{cmdroot|chmod a+x Sample}}
: {{cmdroot|./Sample}}

Press (e) to enroll a new user, and enter your username when asked for the user ID. You will be asked to swipe your finger three times. Now press (v) and swipe your finger, a green check should be displayed showing you have successfully authenticated.

: Figure 8. The fingerprint swipe prompt
: [[Image:touchchip.jpg]]

Wonderful! Now, quit the application (q) and type exit to become a normal user. A file called yourusername.bir should have been created, copy this to your home directory:

: {{cmdroot|cp yourusername.bir /home/yourusername/}}

You can now close the terminal window. The next step is to install the BioAPI plug-in for PAM, and to make applications use the plugin. So, get the pam_bioapi plugin from http://www.nax.cz/pub/bioapi/pam_bioapi/pam-bioapi_0.3.0.tar.gz and extract it. Now open a terminal and type:

: {{cmduser|cd /path/to/where/you/extracted/the/arcive}}
: {{cmduser|./configure --libdir<nowiki>=</nowiki>/lib --enable-file-store && make}}
: {{cmduser|sudo make install}}

That's installed the plugin. Now, open a terminal and type the following scary commands: (Note: The line starting 'SERIAL=' and the line following it should be in the same line).

: {{cmduser|cd ~}}
: {{cmduser|sudo bash}}
: {{cmdroot|SERIAL=`BioAPITest | sed -ne "/Fingerprint/{n;n;s/^.*: $.\{9\}$$.\{4\}$$.\{4\}$$.\{4\}$$.*$/\1-\2-\3-\4-\5/gp}"`}}
: {{cmdroot|mkdir -p /etc/bioapi/pam/$SERIAL}}
: {{cmdroot|cp yourusername.bir /etc/bioapi/pam/$SERIAL}}
: {{cmdroot|exit}}

Phew. Now, to make applications actually use the fingerprint reader. Open a terminal window, and type:

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

Delete everything in the file, and paste this instead:

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

Save and close the file. That will make all PAM-aware applications use the fingerprint reader. Unfortunately, this also includes sudo. Since sudo is a command line application, it will display prompts in a terminal for you to swipe your finger, which is all well and good. The problem with this is that many Ubuntu administrative applications (such as Synaptic) use gksu to present a graphical front-end to sudo, which will output messages on the command line which you'll never see. Result? Administrative programs won't work from the gnome menu. The solution is to make sudo use the good old password. Open a terminal and type:

: {{cmduser|sudo gedit /etc/pam.d/sudo}}

Delete everything in the file, and instead paste:

<pre>
#%PAM-1.0

#@include common-auth
auth required pam_unix.so nullok_secure
@include common-account
</pre>

Now, save the file and close it, and reboot your system. GDM will ask you for a username, and then show a pretty prompt where you can scan your fingerprint! Same goes for gnome-screensaver when you set it to lock. Sometimes gnome-screensaver will not display the prompt, but you should still swipe your finger and be able to log back in.

===Bluetooth with Mobile Phones/PDAs===

Rather strangely, Ubuntu seems to have taken a step backwards with Bluetooth useability in Edgy. What worked out of the box with Dapper, now requires configuratio. First, open System - Preferences - Sessions and go to the Startup Programs tab. Then, find the entry labelled 'bt-applet --sm-disable'. Highlight it and click disable. Click add and in the command field type 'bt-applet'. Repeat this process, adding an entry for 'gnome-obex-server'. Now, open Synaptic Package Manager (System - Administration - Synaptic Package Manager) and click Search. Type 'gnome-bluetooth' to find the package, then mark it for installation. Now repeat this process for 'bluez-passkey-gnome'. Click apply to make changes.

Now that everything is installed, log-out of Gnome and log back in again. From your phone/PDA, search for devices untill you see your ThinkPad (the hostname will be displayed). Pair with the device. When asked for a passkey, enter 1234, which is the default. If you want to change your passkey (and you should), open a terminal and type:

: {{cmduser|sudo gedit /etc/bluetooth/hcid.conf}}

Find the line which says 'Default PIN for incoming connections' and change the PIN on the line beneath it:

<pre>
# Default PIN code for incoming connections
passkey "4017";
</pre>

Save and close the file, then type:

: {{cmduser|sudo /etc/init.d/bluetooth restart}}

You will now be able to use your new PIN code. To send files from your device to the ThinkPad, simply select the file you want to send and click Send Via Bluetooth (or whatever option your device presents). A dialog will pop-up in Gnome showing you a new file has been received.

: Figure 9. Gnome informing us that a file has been received
: [[Image:bluetooth.jpg]]

Sending files from your ThinkPad to your device requires more effort. The way it should work is that you right-click on a file, click send to, then make sure 'Bluetooth (OBEX)' is selected. Your device should be displayed and you could just click send. Unfortunately, due to a bug in gnome-bluetooth (described in https://launchpad.net/distros/ubuntu/+source/gnome-bluetooth/+bug/70718) this method does not work. If it does work for you, the bug has been solved and you can skip the rest of this section.

Your only other option is to use the command line to send files to your device. Open a terminal, then type:

: {{cmduser|hcitool scan}}

A list of detected bluetooth devices will be shown, for example, my output shows the following:

<pre>
Scanning ...
00:09:DD:60:02:EB Photosmart 8100 series
00:14:A7:99:3C:1F ThElInK
</pre>

The first field is the MAC address of the device, the second is the name of the device. In this case my bluetooth printer and mobile phone (ThElInK) were detected. In order to send files to my phone, I use:

: {{cmduser|gnome-obex-send -d 00:14:A7:99:3C:1F myPicture.jpg}}

Replace the MAC address with that of your device and myPicture.jpg with the file you want to send.

===TrackPoint Scrolling===

By default you can use the right and bottom edges of your touchpad to scroll through documents. If you use the TrackPoint instad of the touchpad (and believe me, you should), you'll find that scrolling is disabled by default. To enable it, open a terminal and type:

: {{cmduser|sudo gedit /etc/X11/xorg.conf}}

Now find the entry for your TrackPoint device. In my configuration file, the TrackPoint entry is the first mouse entry, after the keyboard entry, and looks something like this:

<pre>
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection
</pre>

Right after this entry is my touchpad entry. My entry is on line 66, but yours may be different. Now, add the follwing two options in that InputDevice section:

<pre>
Option "EmulateWheel" "on"
Option "EmulateWheelButton" "2"
</pre>

Save and exit the file. Restart your ThinkPad (or logout, and press CTRL-ALT-BACKSPACE). You should now be able to scoll by holding down the middle button for your TrackPoint and using the TrackPoint to scroll.

===Getting Multimedia to Work===

Due to patents and similar legal crap, Ubuntu will not play most media files by default. You also won't get browser plugins for multimedia. Luckily, this is easily fixed. Open a terminal and type the following:

: {{cmduser|sudo cp /etc/apt/sources.list /etc/apt/sources.list.backup}}
: {{cmduser|sudo gedit /etc/apt/sources.list}}

Delete everything in the file, and instead paste the following:

<pre>
deb-src http://archive.ubuntu.com/ubuntu edgy main restricted universe multiverse
#deb http://archive.ubuntu.com/ubuntu edgy-proposed main restricted universe multiverse

## MAJOR BUG FIX UPDATES produced after the final release
deb-src http://archive.ubuntu.com/ubuntu edgy-updates main restricted universe multiverse

## UBUNTU SECURITY UPDATES
deb http://security.ubuntu.com/ubuntu edgy-security main restricted universe multiverse
deb-src http://security.ubuntu.com/ubuntu edgy-security main restricted universe multiverse

## BACKPORTS REPOSITORY (Unsupported. May contain illegal packages. Use at own risk.)
#deb http://archive.ubuntu.com/ubuntu edgy-backports main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu edgy-backports main restricted universe multiverse

## PLF REPOSITORY
deb http://packages.freecontrib.org/ubuntu/plf edgy-plf free
deb-src http://packages.freecontrib.org/ubuntu/plf edgy-plf free
deb http://packages.freecontrib.org/ubuntu/plf edgy-plf non-free
deb-src http://packages.freecontrib.org/ubuntu/plf edgy-plf non-free

## CANONICAL COMMERCIAL REPOSITORY (Hosted on Canonical servers, not Ubuntu
## servers. RealPlayer10, Opera, DesktopSecure and more to come.)
deb http://archive.canonical.com/ubuntu edgy-commercial main

## Listen
#deb http://theli.free.fr/packages/ edgy listen

## Automatix repo
deb http://www.getautomatix.com/apt edgy main
</pre>

Now, open a terminal and type the following:

: {{cmduser|wget http://packages.freecontrib.org/ubuntu/plf/12B83718.gpg -O- | sudo apt-key add -}}
: {{cmduser|wget http://www.getautomatix.com/apt/key.gpg.asc}}
: {{cmduser|gpg --import key.gpg.asc}}
: {{cmduser|gpg --export --armor 521A9C7C | sudo apt-key add -}}
: {{cmduser|sudo apt-get update}}
: {{cmduser|sudo apt-get install automatix2}}
: {{cmduser|wget http://easyubuntu.freecontrib.org/files/easyubuntu-3.023.tar.gz}}
: {{cmduser|tar -zxf easyubuntu-3.023.tar.gz}}
: {{cmduser|cd easyubuntu}}
: {{cmduser|cp packagelist-dapper.pot packagelist-edgy.pot}}
: {{cmduser|cp packagelist-dapper.xml packagelist-edgy.xml}}
: {{cmduser|sudo python easyubuntu.in}}

Don't worry if you get errors from the Ubuntu PLF repository. PLF mirrors are about as stable as wild bull in a farm full of cows. Select what you want to install from the resulting window. Make sure you do not select the totem-mozilla plugin, as this just doens't work, for me at least. When EasyUbuntu has finished installing packages, you should be returned to a terminal, which you can close. Now go to Applications - System Tools - Automatix. Read and agree to the warning. Check what you want to install. Make sure you check 'Mplayer and FF plugin'. When ready, click the 'install' button. That should get multimedia working nicely.

: Figure 10. The Automatix user interface
: [[Image:automatix.jpg]]

===Beryl - fancy 3D desktop===

MAC OS X has Aqua and Windows Vista has Aero. Well, Linux has XGL/Beryl which can get effects which are as good looking (or sometimes better!) than the former two. Installing Beryl on Ubuntu is not that hard. First, open a terminal and type the following:

: {{cmduser|sudo gedit /etc/apt/sources.list}}

At the end of the file, append the following:

<pre>
##Beryl
deb http://ubuntu.beryl-project.org/ edgy main
</pre>

Save and close the file. Now type:

: {{cmduser|wget http://beryl-mirror.lupine.me.uk/1609B551.gpg -O- | sudo apt-key add -}}
: {{cmduser|sudo apt-get update}}

ATI Users Only: type

: {{cmduser|sudo apt-get install xserver-xgl}}

Now, to install beryl:

: {{cmduser|sudo apt-get install beryl emerald-themes}}

To make Ubuntu use the 3D effects. Open a terminal:

: {{cmduser|sudo gedit /usr/local/bin/startxgl.sh}}

In that file, paste the following if you use an ATI card:

<pre>
#!/bin/sh
Xgl -fullscreen :1 -ac -br -accel glx:pbuffer -accel xv:pbuffer &
sleep 4
export DISPLAY=:1
exec gnome-session
</pre>

If you use an Intel card, paste the following instead:

<pre>
#!/bin/sh
beryl-manager
sleep 4
exec gnome-session
</pre>

Save the file and close. Now we need to make the file executable:

: {{cmduser|sudo chmod a+x /usr/local/bin/startxgl.sh}}

All that's left now is to create a login script which makes gnome use the 3D effects. In a terminal, type:

: {{cmduser|sudo gedit /usr/share/xsessions/xgl.desktop}}

Now, in this file paste:

<pre>
[Desktop Entry]
Encoding=UTF-8
Name=Xgl
Exec=/usr/local/bin/startxgl.sh
Icon=
Type=Application
</pre>

Save and close the file. Now type:

: {{cmduser|sudo gedit /usr/local/bin/start_beryl.sh}}

In this file, paste:

<pre>
#!/bin/bash
#
# Start beryl-manager within gnome-session
#
if [ `ps -A -o comm | grep -c '^Xgl$'` == "1" ]; then
DISPLAY=:1 beryl-manager
DISPLAY=:1 beryl-xgl
else echo "${0}: Error: beryl-manager not launched. Xgl not running?"
fi
</pre>

Now make the file executable:

: {{cmduser|sudo chmod a+x /usr/local/bin/start_beryl.sh}}

Now go to System - Preferences - Sessions, go to the Startup Programs tab, and click add, then type

: {{cmduser|/usr/local/bin/start_beryl.sh}}

Now, reboot your ThinkPad. When you come to the login screen, click the 'Sessions' button on the bottom left corner, and select XGL. login, et voila! beautiful 3D effects!

: Figure 11. Beryl's Cube effect
: [[Image:cube.jpg]]

If you have NetBeans installed, try launching it now. It probably won't work due to Beryl. Luckily, this is easily solved. Open a terminal and type:

: {{cmduser|sudo gedit /etc/environment}}

Then add the following line to the end of the file.

<pre>AWT_TOOLKIT="MToolkit"</pre>

Now save, close and reboot. Netbeans should now work!

===Problem: Can't add programs to session===

So you tried to add something to your startup programs, it shows up in the list, but it doesn't start up. You then launch the sessions program again, only to find your program has disappeared from the list. This problem is being caused by incorrect permissions in your home directory, and can happen on some occasions. To fix it, open a terminal and type the following:

: {{cmduser|sudo chown -R username:usergroup /home/username/.config/}}

Replace username with your username and usergroup with your group (by default, in Ubuntu your usergroup is the same as your username). Everything should be OK now!

===Problem: Virtual terminals not working===

One problem I had after installing the ATI drivers was that virtual terminals stopped working. Instead of seeing a console when pressing CTRL+ALT+F1...F6 I was seeing a yellow/orange garbled output. Luckily, solving this with ATI drivers is trivial. Open a terminal, and type:

: {{cmduser|sudo gedit /boot/grub/menu.lst}}

Find the line which says

<pre>#defoptions=quiet splash</pre>

and replace it with

<pre>#defoptions=quiet splash vga=791</pre>

Now, find the line which boots the kernel you are currently using, this is just under '## ## End Default Options ##. In the 'kernel' line, add:

<pre>vga=791</pre>

Before:

<pre>kernel /vmlinuz-2.6.17-10-generic root=/dev/sda7 ro quiet splash</pre>

After:

<pre>kernel /vmlinuz-2.6.17-10-generic root=/dev/sda7 ro quiet splash vga=791</pre>

Now save and exit the file, and reboot. Virtual terminals should now work. If you use Intel drivers, you're going to have to bite the bullet and remove the 'splash' keyword from both the defoptions and kernel lines. You'll lose the pretty bootup screen, but at least virtual terminals will work, which are important to recover a crashed system.

===Problem: I keep logging out!===

If you're using Beryl, and find that you keep getting logged out, you've just encountered one of Beryl's most annoying bugs. Shift+Backspace causes a logout. To fix this, open a terminal and type:

: {{cmduser|gedit /home/username/annoymenot.sh}}

Remember to replace 'username' with your username. Now, in this file type:

: {{cmduser|xmodmap -e "keycode 22 <nowiki>=</nowiki> BackSpace BackSpace Terminate_Server" }}

Save and close the file, and make it executable:

: {{cmduser|chmod 755 /home/username/annoymenot.sh}}

Now go to System - Preferences - Session, Startup Programs. Click add, and type

: {{cmduser|/home/username/annoymenot.sh}}

Logout and back in, problem solved! While you're at it, how about getting the start button to work? Go to System - Preferences - Keyboard - Layout Options - Alt/Win Key behaviour and select 'Super is mapped to Win keys (default)'.

===Desktop envy===

We're living in an age of desktop prettyness, and Linux can be just as pretty as MAC OS X or Vista. You've already got Beryl installed. Now go to Applications - Accesories - gDesklets. If the gDesklets entry is not there, make sure you install it, either using Synaptic or Automatix. Desklets are small programs you can add to your desktop, ala OS X's Deskbar or Vista's Sidebar. To make them start on boot, add gdesklets in System - Preferences - Sessions, Startup Programs.

Another cool program is cairo clock. Download it from http://macslow.thepimp.net/projects/cairo-clock/cairo-clock_0.3.2-1_i386.deb and install it by double-clicking. To make it start automatically, add it to your sessions as mentioned above. I've found the following command makes it work best for me:

<pre>cairo-clock -s -w 175 -g 175 -x 1219 -y 7 -t radium</pre>

Finally, make sure you click that Ruby icon in your notification area, it allows you to configure Beryl to do all sorts of cool stuff!

===Conclusion===

Well, that's about it! A dream Linux system on a dream laptop! Check out these cool technologies for an even better system:

* Beagle
* Tomboy
* Deskbar

===References===

* ATI on Ubuntu - https://help.ubuntu.com/community/BinaryDriverHowto/ATI
* Garbled Virtual Terminal Bug - https://launchpad.net/distros/ubuntu/+source/usplash/+bug/63558
* Beryl logout Bug - http://forum.beryl-project.org/viewtopic.php?p=1295&sid=6feedd09a7f01bca68feb05a5f2f033c
* Beryl Netbeans Bug - http://ubuntuforums.org/showthread.php?t=252594
* Beryl on Ubuntu - http://wiki.beryl-project.org/index.php/Install/Ubuntu/Edgy/XGL
* Home directory permissions bug - http://www.ubuntuforums.org/showthread.php?p=1789997
* gnome-bluetooth bug - https://launchpad.net/distros/ubuntu/+source/gnome-bluetooth/+bug/70718

Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60

2006-12-20T07:08:28Z

Ischg: /* The fingerprint reader */

[[User:Keithvassallo|Keithvassallo]] 14:39, 16 December 2006 (CET)

===Abstract===

This article describes how to get Ubuntu Linux 6.10 (Edgy) installed on an IBM/Lenovo ThinkPad T60. It's not meant to be a definite guide to installing Ubuntu (the Ubuntu Guide at http://www.ubuntuguide.org does a very good job of that). This article is meant to describe how to get most of the ThinkPad features working on Ubuntu system. It also discusses how to get Multimedia, some cool-looking effects such as Beryl, gDesklets and similar working on Ubuntu. Finally, we discuss some common problems encountered on Ubuntu and ThinkPads alike.

===My ThinkPad===

Although this guide should work on most recent ThinkPads, I cannot guarantee that. These are the specifications of my machine. The closer your specs are, the greater the chance of success.

: Figure 1. ThinkPad T60 2007, complete with Tux sticker :-)
: [[Image:thinkpad.jpg]]

* Lenovo ThinkPad T60 2007.
* Intel Centrino Duo T2400 / 1.83 GHz.
* Mobile Intel 945PM Express Chipset.
* Intel Wireless LAN.
* Integrated Bluetooth.
* ATI Mobility Radeon X1400 - PCI Express x16, 128MB dedicated RAM.
* 100 GB - Serial ATA-150 Hard Drive.
* 15' TFT Active Matrix Display (1400x1050).

That's basically all you need to know. As far as I know, all other features are common to all ThinkPads manufactured by Lenovo since they acquired IBM's computer business.

===Why Ubuntu? (or rather, Why not SUSE?)===

In June 2006, Lenovo announced it would be shipping ThinkPad T60p laptops with SUSE Linux Enterprise Desktop (SLED) 10 pre-installed, since SLED apparently supports all of the features of the T60p. I contacted my local IBM supplier, who said that Lenovo were no longer manufacturing the T60p, since the company which was making the displays went out of business. This meant I could not get a T60p with SLED pre-installed. I decided to go for the T60 2007, which is the closest thing I could find to the T60p. This comes with Windows XP Professional pre-installed.

I first tried to get SLED installed on the T60. Although it did indeed install, and most features worked, I soon got bored of SLED. Firstly, SLED uses Gnome 2.12, which is by now ancient. Secondly, although the Lenovo utilities do work on SLED, they only work well if you use KDE as your defauly desktop environment, which is a pity since I'm a Gnome user. The utilities were very unstable to me too. Finally, what made me give up SLED was the usual problem - it's an RPM based distribution. Once you start using Debian derivatives, with their apt based installer, you won't want to go back. That's when I decided to try Ubuntu, and have not regretted it since.

===What Works?===

* Ubuntu and all programs it comes with.
* Most of the function keys, except the ones mentioned below
* The fingerprint reader.
* The ATI proprietary graphics drivers.
* Suspend to RAM (Sleep) and Suspend to Disk (Hibernate).
* Brightness, Volume and Mute with OSD (On-Screen Display).
* ThinkLight, TrackPoint II and the touchpad.

===What Doesn't Work? (Known Issues)===

* FN+F8, FN+F9, FN+ZOOM.
* The BACK and FORWARD buttons (next to the cursor keys).
* The ThinkVantage button (in Linux, still works on boot).
* Sending files to Bluetooth devices via GUI.

There are probably ways and means to get the offending buttons to work, I've tried several fora but none seem to address my exact problem. I'll update this article should I find out anything.

===First Things First - Creating a Windows Recovery Disc===

If you've purchased a T60, chances are it came with Windows XP Professional. The other option is for you to have FreeDOS installed, in which case you can skip this section. You could remove the Windows partition altogether, and reserve your ThinkPad for Linux, but that's not the route I've chosen. The ThinkVantage utilities in Windows allow you to do a lot of cool things, such as set-up a boot-up fingerprint security scan. You can't do this from Linux (as far as I know) so it's best to leave the Windows partition in place. So, boot your ThinkPad and complete the Windows XP setup (which asks you to add a user account and enroll yourself using the ThinkVantage Client Security Solution). While you're there, use the ThinkVantage productivy centre to enroll your fingerprint (I suggest enrolling more than one) and make sure you check the option to require a fingerprint scan on boot (not for security, for geek points). When you reboot, press ESC or F2 to get to BIOS, and make sure you check the option to require a supervisor password. This will make your ThinkPad prompt you for your fingerprint when you power it up.

: Figure 2. Configuring fingerprint security from Windows
: [[Image:winprint.jpg]]

Now that's working, you should create a recovery DVD using the ThinkVantage recovery utilities. This will allow you to recover your Windows installation should you manage to screw your partitions up in the following stages. I highly recommend you do this, as Lenovo does not provide Windows XP CDs with this Laptop - so the hard disk partition is all you've got. Once this is done, we're ready to install Ubuntu!

: Figure 3. Creating recovery discs from Windows
: [[Image:recovery.jpg]]

===Getting Ubuntu installed===

Download the latest Edgy live CD from the Ubuntu website, you can find a list of mirrors at http://www.ubuntu.com/products/GetUbuntu/download#currentrelease. You may also try Kubuntu, Edubuntu or any of it's derivatives, but I'll stick with Ubuntu here for simplicity's sake. Once that's downloaded, burn the ISO to disc using any program of your choice (If this is your first Linux experience and you're using Windows, try using Nero - http://www.nero.com).

Once the burning process is complete, reboot your machine ensuring that the Ubuntu CD is in the drive. You should see an Ubuntu menu. If you don't, your BIOS is not set to boot from CD. Reboot your ThinkPad and change the boot order from BIOS (by default ThinkPads boot from CD-ROM before the hard disk, so this is probably not necessary). Once the menu shows up, select 'Start or install Ubuntu' and let it boot. This will take a while as everything is loaded from CD. You should eventually end up in a Gnome desktop. If you see an error about the Gnome Settings Daemon not being able to load, simply ignore it, as this is not necessary for now. For the purposes of the installation, it's best if you have a wired ethernet connection, as it's unlikely the wireless network card will work until we boot into our installed Ubuntu system.

: Figure 4. Select the first option to start Ubuntu
: [[Image:boot.jpg]]

Double-Click on the 'install' icon on the Desktop to start installation. The installation should be pretty straight-forward. If you need additional help, check out the walk-through with screen-shots at http://www.debianadmin.com/ubuntu-edgy-eft-desktop-installation-with-screenshots.html. The only stage at which we need to make changes is the partitioning stage. This to make sure we preserve our Windows partition, and the IBM vendor_diag partition which allows recovery of the laptop when things go hay-wire. In the 'Prepare disk space' section of the installer, select the third option, 'Manually edit partition table'. A bar will be displayed showing your existing partitions. If you have Windows installed you will see two partitions. The first is a 4.89 GB IBM Vendor Diagnostic partition, which we do not want to touch. The second will be your Windows partition, which will fill the rest of the disk. Click on this partition, Then click the 'Resize/Move' button. I resized my Windows partition to 24 GB. This is enough to accommodate the 10 GB already in use on that partition, as well as giving Windows another 14 GB of free space. 6 GB of free space would probably be enough though.

Now it's time to create partitions for Linux. You need at least two partitions; a swap partition which should be roughly double the amount of RAM you have, and a root partition to install Linux. I opted for four partitions, as follows:

<table border=1>
<tr><td>'''Purpose'''</td><td>'''Size'''</td><td>'''File-System'''</td></tr>
<tr><td>Swap</td><td>2 GB</td><td>swap</td></tr>
<tr><td>/boot</td><td>5 GB</td><td>ext3</td></tr>
<tr><td>/ (root)</td><td>20 GB</td><td>ext3</td></tr>
<tr><td>/home</td><td>37.25 GB (what's left of the disk)</td><td>ext3</td></tr>
</table>

To create these paritions, click on the 'New' button and select 'Extended Partition' in the 'create as' drop-down list. Leave all other settings as-is, and click 'Add'. Now, click on the newly created partition, and create each of the partitions you want to create, simply specify the size of the partition in the 'New Size (MiB)' text box. To convert GB to MiB, multiply by 1024. So for your swap partition you should specify a size of 2048. Repeat until you have created all the required partitions. If you follow my parition layout, the partition editor should look something like Figure 5.

: Figure 5. Our partitions, ready to be created
: [[Image:partitioning.jpg]]

You will not see mount-points in your diagram, because the screen-shot above was taken after they were assigned, but you should get the general idea. After this screen, you will be asked to assign mount-points to the partitions you have just created. If you created the partitions in the same order I did, you can assign mount points as I have (i.e. /dev/sda5 for swap, /dev/sda6 for /boot, /dev/sda7 for /, /dev/sda8 for /home). Additionally, I mounted my Windows partition as /media/sda1 and my IBM Vendor Diagnostic partition as /media/sda2. These are optional. After this step, continue installation as normal. When the installation is complete, click the 'reboot' button to restart into your fresh Ubuntu System.

When booting, the GRUB boot-loader will be displayed, asking you what you want to load. You will probably see four options. The first two being Ubuntu Linux and Ubuntu Linux recovery mode (showing the kernel version). The other two will be Microsoft Windows XP, and 'Other Windows XP/2000/NT' partition. This is your IBM Vendor Diagnostic partition, which is based on the Windows kernel, apparently. Select the first entry to boot Ubuntu. The next time you boot Windows, it will bring up a chkdsk screen. This is entirely normal and happens because we have resized the Windows partition. Make sure you do not skip this check and let it complete.

===Wireless LAN===

The first thing we should do is to get wireless networking working. Luckily, getting the Centrino wireless LAN chip working in Ubuntu is quite easy, if you use the gnome-network-manager applet. Just go to System - Administration - Synaptic Package Manager. Then click 'Search' and set the 'look-in' field to 'name'. In the 'Search' text box type:

<pre>network-manager</pre>

: Figure 6. Installing the network manager applet
: [[Image:networkmanager.jpg]]

Click on the box beside 'network-manager' and click 'Mark for installation'. Do the same for 'network-manager-gnome'. Once installed, reboot your thinkpad. An applet will show up in the gnome notification area. Click on it, and a list of detected wireless networks will be displayed. Simply click on one of them, enter any authentication details necessary, and you'll be connected to the wireless network.

: Figure 7. gnome-network-manager showing available wireless networks
: [[Image:available-accesspoints.jpg]]

Note! Not all versions of the T60 has the Intel Wireless LAN as described above. Run lspci from the command line and look for details of your wifi card. E.g.:

03:00.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)

suggest you have a different wifi card. Read this forum thread http://ubuntuforums.org/showthread.php?t=38972

running:
# dmesg | grep hal

may yield output like this, which apparently suggests the hardware abstraction layer is in place.
[17179590.420000] ath_hal: module license 'Proprietary' taints kernel.
[17179590.424000] ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)

If not, or if the output contains "HAL Status 13" it apparently suggests your card is not supported by the current drivers, and you need to upgrade.

===Installing the ATI display drivers===

If your ThinkPad has an Intel graphics adapter, you should skip this section as Ubuntu installs the best driver automatically. Ubuntu does not install the ATI proprietary drivers by default because they are, er, proprietary. Luckily, installing them is easy enough. Open a terminal (Applications - Accessories - Terminal) and type the following:

: {{cmduser| sudo apt-get update}}
: {{cmduser| sudo apt-get install xorg-driver-fglrx fglrx-control}}

Now we make sure the proprietary driver is not disabled by the kernel. Type the following, and remove any lines referring to fglrx

: {{cmduser|sudo gedit /etc/default/linux-restricted-modules-common}}

An alternative to gedit (Gnome) is nano (sudo nano -w /etc...) for a CLI editor.

Finally, we need to configure the X server to use the ATI drivers. Type the following:

: {{cmduser|sudo depmod -a}}
: {{cmduser|sudo aticonfig --initial}}
: {{cmduser|sudo aticonfig --overlay-type<nowiki>=</nowiki>Xv}}

One last thing. In order to correct a very common problem of getting a jerky video display, type the following:

: {{cmduser|sudo gedit /etc/X11/xorg.conf}}

Scroll to the end of the file, and add the text below.

<pre>
Section "Extensions"
Option "Composite" "0"
EndSection
</pre>

Save the file and exit. Now, to apply the changes either press CTRL+ALT+Backspace or reboot. The resolution should have switched to 1400x1050 and everything should look prettier and render faster. Just to make sure everything is working, open up a terminal and type

: {{cmduser|fglrxinfo}}

This should display:

<pre>
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Mobility Radeon X1400 Generic
OpenGL version string: 2.0.6011 (8.28.8)
</pre>

The above is what I get on my ThinkPad, and you should see something similar. As long as you see your graphics card model listed, everything should be OK. If, instead, you see a bunch of lines containing 'Mesa' then you have a problem. In that case, I recommend consulting https://help.ubuntu.com/community/BinaryDriverHowto/ATI and the Ubuntu forums at http://ubuntuforums.org

===The fingerprint reader===

Although IBM does not officially support it, the fingerprint reader does in fact work with most Linux distributions. Getting it to work with Ubuntu can be a bit of a pain, but it does work. Basically, a bioAPI plugin is provided for PAM. PAM-aware applications such as GDM and gnome-screensaver will then automatically use the fingerprint reader, which is uber cool. Anyway, enough theory, I've probably lost the newbies amongst you already. Go to http://www.qrivy.net/~michael/temp/ and download the latest bioapi package (at the time of writing, bioapi_1.2.3_i386.deb). When asked, tell Firefox to open the file with the GDebi package installer.

That will install bioAPI. What we need now is the driver for our fingerprint device, which is manufactured by UPEK. Go to http://www.upek.com/support/dl_linux_bsp.asp and download the latest version, currently UPEK_BSP_LIN_1.0.zip. Extract this file, then open a terminal (and don't close it until I say so).

: {{cmduser|cd /path/to/where/you/extracted/the/file}}
: {{cmduser|sudo bash}}
: {{cmdroot|sh install.sh /usr/lib}}

Now we need to assign the right permissions so non-root applications can use the driver:

: {{cmdroot|addgroup --system bioapi}}
: {{cmdroot|addgroup --system usbfs}}
: {{cmdroot|adduser yourusername bioapi}}
: {{cmdroot|adduser yourusername usbfs}}
: {{cmdroot|chown -R root:bioapi /usr/var/bioapi/}}
: {{cmdroot|chmod -R 770 /usr/var/bioapi/}}
: {{cmdroot|chown -R root:usbfs /proc/bus/usb}}
: {{cmdroot|chmod -R g+X /proc/bus/usb}}

Of course, replace 'yourusername' with the username you use to login. Now, we need to set the usb file system (usbfs) to be usable by users in the usbfs group. To do this, we need to determine the group ID of the usbfs group. Type the following:

: {{cmdroot|cat /etc/group | grep usbfs | cut -d':' -f 3}}

In my case the number is 116, it might be different for you. Now, open the file /etc/fstab:

: {{cmdroot|gedit /etc/fstab}}

and type the following:

<pre>none /proc/bus/usb usbfs defaults,devgid=116,devmode=0660,busgid=116,busmode=0770,listgid=116,listmode=0660 0 0</pre>

Please type the above code in one line in your file. Remember to replace 116 if you got a different number with the previous cat command. The last permission-related thing we need to fool around with is UDEV. Open the udev permissions file

: {{cmdroot|gedit /etc/udev/rules.d/40-permissions.rules}}

and find the line:

<pre>SUBSYSTEM=="usb_device", MODE="0664"</pre>

It's line 65 in my file. Change it so it looks like this:

<pre>SUBSYSTEM=="usb_device", MODE="0660", GROUP="usbfs"</pre>

Now we need to enroll our fingerprint with the system. To do this, we need a utility called Sample, which is only distributed in source-code form with the driver. This is great, only I couldn't get it to compile on Ubuntu. Luckily, there is a binary version available from one of the earlier releases of the driver (beta 2). To get this, download it from ftp://linux:Tuc-nak3@delta.upek.com/TFMESS_BSP_LIN_1.0beta2.zip. Now, extract the file and type:

: {{cmdroot|cd /path/to/where/you/extracted/the/archive}}
: {{cmdroot|cd NonGUI_sample}}
: {{cmdroot|./Sample}}

Press (e) to enroll a new user, and enter your username when asked for the user ID. You will be asked to swipe your finger three times. Now press (v) and swipe your finger, a green check should be displayed showing you have successfully authenticated.

: Figure 8. The fingerprint swipe prompt
: [[Image:touchchip.jpg]]

Wonderful! Now, quit the application (q) and type exit to become a normal user. A file called yourusername.bir should have been created, copy this to your home directory:

: {{cmdroot|cp yourusername.bir /home/yourusername/}}

You can now close the terminal window. The next step is to install the BioAPI plug-in for PAM, and to make applications use the plugin. So, get the pam_bioapi plugin from http://www.nax.cz/pub/bioapi/pam_bioapi/pam-bioapi_0.3.0.tar.gz and extract it. Now open a terminal and type:

: {{cmduser|cd /path/to/where/you/extracted/the/arcive}}
: {{cmduser|./configure --libdir<nowiki>=</nowiki>/lib --enable-file-store && make}}
: {{cmduser|sudo make install}}

That's installed the plugin. Now, open a terminal and type the following scary commands: (Note: The line starting 'SERIAL=' and the line following it should be in the same line).

: {{cmduser|cd ~}}
: {{cmduser|sudo bash}}
: {{cmdroot|SERIAL=`BioAPITest | sed -ne "/Fingerprint/{n;n;s/^.*: $.\{9\}$$.\{4\}$$.\{4\}$$.\{4\}$$.*$/\1-\2-\3-\4-\5/gp}"`}}
: {{cmdroot|mkdir -p /etc/bioapi/pam/$SERIAL}}
: {{cmdroot|cp yourusername.bir /etc/bioapi/pam/$SERIAL}}
: {{cmdroot|exit}}

Phew. Now, to make applications actually use the fingerprint reader. Open a terminal window, and type:

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

Delete everything in the file, and paste this instead:

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

Save and close the file. That will make all PAM-aware applications use the fingerprint reader. Unfortunately, this also includes sudo. Since sudo is a command line application, it will display prompts in a terminal for you to swipe your finger, which is all well and good. The problem with this is that many Ubuntu administrative applications (such as Synaptic) use gksu to present a graphical front-end to sudo, which will output messages on the command line which you'll never see. Result? Administrative programs won't work from the gnome menu. The solution is to make sudo use the good old password. Open a terminal and type:

: {{cmduser|sudo gedit /etc/pam.d/sudo}}

Delete everything in the file, and instead paste:

<pre>
#%PAM-1.0

#@include common-auth
auth required pam_unix.so nullok_secure
@include common-account
</pre>

Now, save the file and close it, and reboot your system. GDM will ask you for a username, and then show a pretty prompt where you can scan your fingerprint! Same goes for gnome-screensaver when you set it to lock. Sometimes gnome-screensaver will not display the prompt, but you should still swipe your finger and be able to log back in.

===Bluetooth with Mobile Phones/PDAs===

Rather strangely, Ubuntu seems to have taken a step backwards with Bluetooth useability in Edgy. What worked out of the box with Dapper, now requires configuratio. First, open System - Preferences - Sessions and go to the Startup Programs tab. Then, find the entry labelled 'bt-applet --sm-disable'. Highlight it and click disable. Click add and in the command field type 'bt-applet'. Repeat this process, adding an entry for 'gnome-obex-server'. Now, open Synaptic Package Manager (System - Administration - Synaptic Package Manager) and click Search. Type 'gnome-bluetooth' to find the package, then mark it for installation. Now repeat this process for 'bluez-passkey-gnome'. Click apply to make changes.

Now that everything is installed, log-out of Gnome and log back in again. From your phone/PDA, search for devices untill you see your ThinkPad (the hostname will be displayed). Pair with the device. When asked for a passkey, enter 1234, which is the default. If you want to change your passkey (and you should), open a terminal and type:

: {{cmduser|sudo gedit /etc/bluetooth/hcid.conf}}

Find the line which says 'Default PIN for incoming connections' and change the PIN on the line beneath it:

<pre>
# Default PIN code for incoming connections
passkey "4017";
</pre>

Save and close the file, then type:

: {{cmduser|sudo /etc/init.d/bluetooth restart}}

You will now be able to use your new PIN code. To send files from your device to the ThinkPad, simply select the file you want to send and click Send Via Bluetooth (or whatever option your device presents). A dialog will pop-up in Gnome showing you a new file has been received.

: Figure 9. Gnome informing us that a file has been received
: [[Image:bluetooth.jpg]]

Sending files from your ThinkPad to your device requires more effort. The way it should work is that you right-click on a file, click send to, then make sure 'Bluetooth (OBEX)' is selected. Your device should be displayed and you could just click send. Unfortunately, due to a bug in gnome-bluetooth (described in https://launchpad.net/distros/ubuntu/+source/gnome-bluetooth/+bug/70718) this method does not work. If it does work for you, the bug has been solved and you can skip the rest of this section.

Your only other option is to use the command line to send files to your device. Open a terminal, then type:

: {{cmduser|hcitool scan}}

A list of detected bluetooth devices will be shown, for example, my output shows the following:

<pre>
Scanning ...
00:09:DD:60:02:EB Photosmart 8100 series
00:14:A7:99:3C:1F ThElInK
</pre>

The first field is the MAC address of the device, the second is the name of the device. In this case my bluetooth printer and mobile phone (ThElInK) were detected. In order to send files to my phone, I use:

: {{cmduser|gnome-obex-send -d 00:14:A7:99:3C:1F myPicture.jpg}}

Replace the MAC address with that of your device and myPicture.jpg with the file you want to send.

===TrackPoint Scrolling===

By default you can use the right and bottom edges of your touchpad to scroll through documents. If you use the TrackPoint instad of the touchpad (and believe me, you should), you'll find that scrolling is disabled by default. To enable it, open a terminal and type:

: {{cmduser|sudo gedit /etc/X11/xorg.conf}}

Now find the entry for your TrackPoint device. In my configuration file, the TrackPoint entry is the first mouse entry, after the keyboard entry, and looks something like this:

<pre>
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection
</pre>

Right after this entry is my touchpad entry. My entry is on line 66, but yours may be different. Now, add the follwing two options in that InputDevice section:

<pre>
Option "EmulateWheel" "on"
Option "EmulateWheelButton" "2"
</pre>

Save and exit the file. Restart your ThinkPad (or logout, and press CTRL-ALT-BACKSPACE). You should now be able to scoll by holding down the middle button for your TrackPoint and using the TrackPoint to scroll.

===Getting Multimedia to Work===

Due to patents and similar legal crap, Ubuntu will not play most media files by default. You also won't get browser plugins for multimedia. Luckily, this is easily fixed. Open a terminal and type the following:

: {{cmduser|sudo cp /etc/apt/sources.list /etc/apt/sources.list.backup}}
: {{cmduser|sudo gedit /etc/apt/sources.list}}

Delete everything in the file, and instead paste the following:

<pre>
deb-src http://archive.ubuntu.com/ubuntu edgy main restricted universe multiverse
#deb http://archive.ubuntu.com/ubuntu edgy-proposed main restricted universe multiverse

## MAJOR BUG FIX UPDATES produced after the final release
deb-src http://archive.ubuntu.com/ubuntu edgy-updates main restricted universe multiverse

## UBUNTU SECURITY UPDATES
deb http://security.ubuntu.com/ubuntu edgy-security main restricted universe multiverse
deb-src http://security.ubuntu.com/ubuntu edgy-security main restricted universe multiverse

## BACKPORTS REPOSITORY (Unsupported. May contain illegal packages. Use at own risk.)
#deb http://archive.ubuntu.com/ubuntu edgy-backports main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu edgy-backports main restricted universe multiverse

## PLF REPOSITORY
deb http://packages.freecontrib.org/ubuntu/plf edgy-plf free
deb-src http://packages.freecontrib.org/ubuntu/plf edgy-plf free
deb http://packages.freecontrib.org/ubuntu/plf edgy-plf non-free
deb-src http://packages.freecontrib.org/ubuntu/plf edgy-plf non-free

## CANONICAL COMMERCIAL REPOSITORY (Hosted on Canonical servers, not Ubuntu
## servers. RealPlayer10, Opera, DesktopSecure and more to come.)
deb http://archive.canonical.com/ubuntu edgy-commercial main

## Listen
#deb http://theli.free.fr/packages/ edgy listen

## Automatix repo
deb http://www.getautomatix.com/apt edgy main
</pre>

Now, open a terminal and type the following:

: {{cmduser|wget http://packages.freecontrib.org/ubuntu/plf/12B83718.gpg -O- | sudo apt-key add -}}
: {{cmduser|wget http://www.getautomatix.com/apt/key.gpg.asc}}
: {{cmduser|gpg --import key.gpg.asc}}
: {{cmduser|gpg --export --armor 521A9C7C | sudo apt-key add -}}
: {{cmduser|sudo apt-get update}}
: {{cmduser|sudo apt-get install automatix2}}
: {{cmduser|wget http://easyubuntu.freecontrib.org/files/easyubuntu-3.023.tar.gz}}
: {{cmduser|tar -zxf easyubuntu-3.023.tar.gz}}
: {{cmduser|cd easyubuntu}}
: {{cmduser|cp packagelist-dapper.pot packagelist-edgy.pot}}
: {{cmduser|cp packagelist-dapper.xml packagelist-edgy.xml}}
: {{cmduser|sudo python easyubuntu.in}}

Don't worry if you get errors from the Ubuntu PLF repository. PLF mirrors are about as stable as wild bull in a farm full of cows. Select what you want to install from the resulting window. Make sure you do not select the totem-mozilla plugin, as this just doens't work, for me at least. When EasyUbuntu has finished installing packages, you should be returned to a terminal, which you can close. Now go to Applications - System Tools - Automatix. Read and agree to the warning. Check what you want to install. Make sure you check 'Mplayer and FF plugin'. When ready, click the 'install' button. That should get multimedia working nicely.

: Figure 10. The Automatix user interface
: [[Image:automatix.jpg]]

===Beryl - fancy 3D desktop===

MAC OS X has Aqua and Windows Vista has Aero. Well, Linux has XGL/Beryl which can get effects which are as good looking (or sometimes better!) than the former two. Installing Beryl on Ubuntu is not that hard. First, open a terminal and type the following:

: {{cmduser|sudo gedit /etc/apt/sources.list}}

At the end of the file, append the following:

<pre>
##Beryl
deb http://ubuntu.beryl-project.org/ edgy main
</pre>

Save and close the file. Now type:

: {{cmduser|wget http://beryl-mirror.lupine.me.uk/1609B551.gpg -O- | sudo apt-key add -}}
: {{cmduser|sudo apt-get update}}

ATI Users Only: type

: {{cmduser|sudo apt-get install xserver-xgl}}

Now, to install beryl:

: {{cmduser|sudo apt-get install beryl emerald-themes}}

To make Ubuntu use the 3D effects. Open a terminal:

: {{cmduser|sudo gedit /usr/local/bin/startxgl.sh}}

In that file, paste the following if you use an ATI card:

<pre>
#!/bin/sh
Xgl -fullscreen :1 -ac -br -accel glx:pbuffer -accel xv:pbuffer &
sleep 4
export DISPLAY=:1
exec gnome-session
</pre>

If you use an Intel card, paste the following instead:

<pre>
#!/bin/sh
beryl-manager
sleep 4
exec gnome-session
</pre>

Save the file and close. Now we need to make the file executable:

: {{cmduser|sudo chmod a+x /usr/local/bin/startxgl.sh}}

All that's left now is to create a login script which makes gnome use the 3D effects. In a terminal, type:

: {{cmduser|sudo gedit /usr/share/xsessions/xgl.desktop}}

Now, in this file paste:

<pre>
[Desktop Entry]
Encoding=UTF-8
Name=Xgl
Exec=/usr/local/bin/startxgl.sh
Icon=
Type=Application
</pre>

Save and close the file. Now type:

: {{cmduser|sudo gedit /usr/local/bin/start_beryl.sh}}

In this file, paste:

<pre>
#!/bin/bash
#
# Start beryl-manager within gnome-session
#
if [ `ps -A -o comm | grep -c '^Xgl$'` == "1" ]; then
DISPLAY=:1 beryl-manager
DISPLAY=:1 beryl-xgl
else echo "${0}: Error: beryl-manager not launched. Xgl not running?"
fi
</pre>

Now make the file executable:

: {{cmduser|sudo chmod a+x /usr/local/bin/start_beryl.sh}}

Now go to System - Preferences - Sessions, go to the Startup Programs tab, and click add, then type

: {{cmduser|/usr/local/bin/start_beryl.sh}}

Now, reboot your ThinkPad. When you come to the login screen, click the 'Sessions' button on the bottom left corner, and select XGL. login, et voila! beautiful 3D effects!

: Figure 11. Beryl's Cube effect
: [[Image:cube.jpg]]

If you have NetBeans installed, try launching it now. It probably won't work due to Beryl. Luckily, this is easily solved. Open a terminal and type:

: {{cmduser|sudo gedit /etc/environment}}

Then add the following line to the end of the file.

<pre>AWT_TOOLKIT="MToolkit"</pre>

Now save, close and reboot. Netbeans should now work!

===Problem: Can't add programs to session===

So you tried to add something to your startup programs, it shows up in the list, but it doesn't start up. You then launch the sessions program again, only to find your program has disappeared from the list. This problem is being caused by incorrect permissions in your home directory, and can happen on some occasions. To fix it, open a terminal and type the following:

: {{cmduser|sudo chown -R username:usergroup /home/username/.config/}}

Replace username with your username and usergroup with your group (by default, in Ubuntu your usergroup is the same as your username). Everything should be OK now!

===Problem: Virtual terminals not working===

One problem I had after installing the ATI drivers was that virtual terminals stopped working. Instead of seeing a console when pressing CTRL+ALT+F1...F6 I was seeing a yellow/orange garbled output. Luckily, solving this with ATI drivers is trivial. Open a terminal, and type:

: {{cmduser|sudo gedit /boot/grub/menu.lst}}

Find the line which says

<pre>#defoptions=quiet splash</pre>

and replace it with

<pre>#defoptions=quiet splash vga=791</pre>

Now, find the line which boots the kernel you are currently using, this is just under '## ## End Default Options ##. In the 'kernel' line, add:

<pre>vga=791</pre>

Before:

<pre>kernel /vmlinuz-2.6.17-10-generic root=/dev/sda7 ro quiet splash</pre>

After:

<pre>kernel /vmlinuz-2.6.17-10-generic root=/dev/sda7 ro quiet splash vga=791</pre>

Now save and exit the file, and reboot. Virtual terminals should now work. If you use Intel drivers, you're going to have to bite the bullet and remove the 'splash' keyword from both the defoptions and kernel lines. You'll lose the pretty bootup screen, but at least virtual terminals will work, which are important to recover a crashed system.

===Problem: I keep logging out!===

If you're using Beryl, and find that you keep getting logged out, you've just encountered one of Beryl's most annoying bugs. Shift+Backspace causes a logout. To fix this, open a terminal and type:

: {{cmduser|gedit /home/username/annoymenot.sh}}

Remember to replace 'username' with your username. Now, in this file type:

: {{cmduser|xmodmap -e "keycode 22 <nowiki>=</nowiki> BackSpace BackSpace Terminate_Server" }}

Save and close the file, and make it executable:

: {{cmduser|chmod 755 /home/username/annoymenot.sh}}

Now go to System - Preferences - Session, Startup Programs. Click add, and type

: {{cmduser|/home/username/annoymenot.sh}}

Logout and back in, problem solved! While you're at it, how about getting the start button to work? Go to System - Preferences - Keyboard - Layout Options - Alt/Win Key behaviour and select 'Super is mapped to Win keys (default)'.

===Desktop envy===

We're living in an age of desktop prettyness, and Linux can be just as pretty as MAC OS X or Vista. You've already got Beryl installed. Now go to Applications - Accesories - gDesklets. If the gDesklets entry is not there, make sure you install it, either using Synaptic or Automatix. Desklets are small programs you can add to your desktop, ala OS X's Deskbar or Vista's Sidebar. To make them start on boot, add gdesklets in System - Preferences - Sessions, Startup Programs.

Another cool program is cairo clock. Download it from http://macslow.thepimp.net/projects/cairo-clock/cairo-clock_0.3.2-1_i386.deb and install it by double-clicking. To make it start automatically, add it to your sessions as mentioned above. I've found the following command makes it work best for me:

<pre>cairo-clock -s -w 175 -g 175 -x 1219 -y 7 -t radium</pre>

Finally, make sure you click that Ruby icon in your notification area, it allows you to configure Beryl to do all sorts of cool stuff!

===Conclusion===

Well, that's about it! A dream Linux system on a dream laptop! Check out these cool technologies for an even better system:

* Beagle
* Tomboy
* Deskbar

===References===

* ATI on Ubuntu - https://help.ubuntu.com/community/BinaryDriverHowto/ATI
* Garbled Virtual Terminal Bug - https://launchpad.net/distros/ubuntu/+source/usplash/+bug/63558
* Beryl logout Bug - http://forum.beryl-project.org/viewtopic.php?p=1295&sid=6feedd09a7f01bca68feb05a5f2f033c
* Beryl Netbeans Bug - http://ubuntuforums.org/showthread.php?t=252594
* Beryl on Ubuntu - http://wiki.beryl-project.org/index.php/Install/Ubuntu/Edgy/XGL
* Home directory permissions bug - http://www.ubuntuforums.org/showthread.php?p=1789997
* gnome-bluetooth bug - https://launchpad.net/distros/ubuntu/+source/gnome-bluetooth/+bug/70718

Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60

2006-12-20T07:03:52Z

Ischg: /* The fingerprint reader */

[[User:Keithvassallo|Keithvassallo]] 14:39, 16 December 2006 (CET)

===Abstract===

This article describes how to get Ubuntu Linux 6.10 (Edgy) installed on an IBM/Lenovo ThinkPad T60. It's not meant to be a definite guide to installing Ubuntu (the Ubuntu Guide at http://www.ubuntuguide.org does a very good job of that). This article is meant to describe how to get most of the ThinkPad features working on Ubuntu system. It also discusses how to get Multimedia, some cool-looking effects such as Beryl, gDesklets and similar working on Ubuntu. Finally, we discuss some common problems encountered on Ubuntu and ThinkPads alike.

===My ThinkPad===

Although this guide should work on most recent ThinkPads, I cannot guarantee that. These are the specifications of my machine. The closer your specs are, the greater the chance of success.

: Figure 1. ThinkPad T60 2007, complete with Tux sticker :-)
: [[Image:thinkpad.jpg]]

* Lenovo ThinkPad T60 2007.
* Intel Centrino Duo T2400 / 1.83 GHz.
* Mobile Intel 945PM Express Chipset.
* Intel Wireless LAN.
* Integrated Bluetooth.
* ATI Mobility Radeon X1400 - PCI Express x16, 128MB dedicated RAM.
* 100 GB - Serial ATA-150 Hard Drive.
* 15' TFT Active Matrix Display (1400x1050).

That's basically all you need to know. As far as I know, all other features are common to all ThinkPads manufactured by Lenovo since they acquired IBM's computer business.

===Why Ubuntu? (or rather, Why not SUSE?)===

In June 2006, Lenovo announced it would be shipping ThinkPad T60p laptops with SUSE Linux Enterprise Desktop (SLED) 10 pre-installed, since SLED apparently supports all of the features of the T60p. I contacted my local IBM supplier, who said that Lenovo were no longer manufacturing the T60p, since the company which was making the displays went out of business. This meant I could not get a T60p with SLED pre-installed. I decided to go for the T60 2007, which is the closest thing I could find to the T60p. This comes with Windows XP Professional pre-installed.

I first tried to get SLED installed on the T60. Although it did indeed install, and most features worked, I soon got bored of SLED. Firstly, SLED uses Gnome 2.12, which is by now ancient. Secondly, although the Lenovo utilities do work on SLED, they only work well if you use KDE as your defauly desktop environment, which is a pity since I'm a Gnome user. The utilities were very unstable to me too. Finally, what made me give up SLED was the usual problem - it's an RPM based distribution. Once you start using Debian derivatives, with their apt based installer, you won't want to go back. That's when I decided to try Ubuntu, and have not regretted it since.

===What Works?===

* Ubuntu and all programs it comes with.
* Most of the function keys, except the ones mentioned below
* The fingerprint reader.
* The ATI proprietary graphics drivers.
* Suspend to RAM (Sleep) and Suspend to Disk (Hibernate).
* Brightness, Volume and Mute with OSD (On-Screen Display).
* ThinkLight, TrackPoint II and the touchpad.

===What Doesn't Work? (Known Issues)===

* FN+F8, FN+F9, FN+ZOOM.
* The BACK and FORWARD buttons (next to the cursor keys).
* The ThinkVantage button (in Linux, still works on boot).
* Sending files to Bluetooth devices via GUI.

There are probably ways and means to get the offending buttons to work, I've tried several fora but none seem to address my exact problem. I'll update this article should I find out anything.

===First Things First - Creating a Windows Recovery Disc===

If you've purchased a T60, chances are it came with Windows XP Professional. The other option is for you to have FreeDOS installed, in which case you can skip this section. You could remove the Windows partition altogether, and reserve your ThinkPad for Linux, but that's not the route I've chosen. The ThinkVantage utilities in Windows allow you to do a lot of cool things, such as set-up a boot-up fingerprint security scan. You can't do this from Linux (as far as I know) so it's best to leave the Windows partition in place. So, boot your ThinkPad and complete the Windows XP setup (which asks you to add a user account and enroll yourself using the ThinkVantage Client Security Solution). While you're there, use the ThinkVantage productivy centre to enroll your fingerprint (I suggest enrolling more than one) and make sure you check the option to require a fingerprint scan on boot (not for security, for geek points). When you reboot, press ESC or F2 to get to BIOS, and make sure you check the option to require a supervisor password. This will make your ThinkPad prompt you for your fingerprint when you power it up.

: Figure 2. Configuring fingerprint security from Windows
: [[Image:winprint.jpg]]

Now that's working, you should create a recovery DVD using the ThinkVantage recovery utilities. This will allow you to recover your Windows installation should you manage to screw your partitions up in the following stages. I highly recommend you do this, as Lenovo does not provide Windows XP CDs with this Laptop - so the hard disk partition is all you've got. Once this is done, we're ready to install Ubuntu!

: Figure 3. Creating recovery discs from Windows
: [[Image:recovery.jpg]]

===Getting Ubuntu installed===

Download the latest Edgy live CD from the Ubuntu website, you can find a list of mirrors at http://www.ubuntu.com/products/GetUbuntu/download#currentrelease. You may also try Kubuntu, Edubuntu or any of it's derivatives, but I'll stick with Ubuntu here for simplicity's sake. Once that's downloaded, burn the ISO to disc using any program of your choice (If this is your first Linux experience and you're using Windows, try using Nero - http://www.nero.com).

Once the burning process is complete, reboot your machine ensuring that the Ubuntu CD is in the drive. You should see an Ubuntu menu. If you don't, your BIOS is not set to boot from CD. Reboot your ThinkPad and change the boot order from BIOS (by default ThinkPads boot from CD-ROM before the hard disk, so this is probably not necessary). Once the menu shows up, select 'Start or install Ubuntu' and let it boot. This will take a while as everything is loaded from CD. You should eventually end up in a Gnome desktop. If you see an error about the Gnome Settings Daemon not being able to load, simply ignore it, as this is not necessary for now. For the purposes of the installation, it's best if you have a wired ethernet connection, as it's unlikely the wireless network card will work until we boot into our installed Ubuntu system.

: Figure 4. Select the first option to start Ubuntu
: [[Image:boot.jpg]]

Double-Click on the 'install' icon on the Desktop to start installation. The installation should be pretty straight-forward. If you need additional help, check out the walk-through with screen-shots at http://www.debianadmin.com/ubuntu-edgy-eft-desktop-installation-with-screenshots.html. The only stage at which we need to make changes is the partitioning stage. This to make sure we preserve our Windows partition, and the IBM vendor_diag partition which allows recovery of the laptop when things go hay-wire. In the 'Prepare disk space' section of the installer, select the third option, 'Manually edit partition table'. A bar will be displayed showing your existing partitions. If you have Windows installed you will see two partitions. The first is a 4.89 GB IBM Vendor Diagnostic partition, which we do not want to touch. The second will be your Windows partition, which will fill the rest of the disk. Click on this partition, Then click the 'Resize/Move' button. I resized my Windows partition to 24 GB. This is enough to accommodate the 10 GB already in use on that partition, as well as giving Windows another 14 GB of free space. 6 GB of free space would probably be enough though.

Now it's time to create partitions for Linux. You need at least two partitions; a swap partition which should be roughly double the amount of RAM you have, and a root partition to install Linux. I opted for four partitions, as follows:

<table border=1>
<tr><td>'''Purpose'''</td><td>'''Size'''</td><td>'''File-System'''</td></tr>
<tr><td>Swap</td><td>2 GB</td><td>swap</td></tr>
<tr><td>/boot</td><td>5 GB</td><td>ext3</td></tr>
<tr><td>/ (root)</td><td>20 GB</td><td>ext3</td></tr>
<tr><td>/home</td><td>37.25 GB (what's left of the disk)</td><td>ext3</td></tr>
</table>

To create these paritions, click on the 'New' button and select 'Extended Partition' in the 'create as' drop-down list. Leave all other settings as-is, and click 'Add'. Now, click on the newly created partition, and create each of the partitions you want to create, simply specify the size of the partition in the 'New Size (MiB)' text box. To convert GB to MiB, multiply by 1024. So for your swap partition you should specify a size of 2048. Repeat until you have created all the required partitions. If you follow my parition layout, the partition editor should look something like Figure 5.

: Figure 5. Our partitions, ready to be created
: [[Image:partitioning.jpg]]

You will not see mount-points in your diagram, because the screen-shot above was taken after they were assigned, but you should get the general idea. After this screen, you will be asked to assign mount-points to the partitions you have just created. If you created the partitions in the same order I did, you can assign mount points as I have (i.e. /dev/sda5 for swap, /dev/sda6 for /boot, /dev/sda7 for /, /dev/sda8 for /home). Additionally, I mounted my Windows partition as /media/sda1 and my IBM Vendor Diagnostic partition as /media/sda2. These are optional. After this step, continue installation as normal. When the installation is complete, click the 'reboot' button to restart into your fresh Ubuntu System.

When booting, the GRUB boot-loader will be displayed, asking you what you want to load. You will probably see four options. The first two being Ubuntu Linux and Ubuntu Linux recovery mode (showing the kernel version). The other two will be Microsoft Windows XP, and 'Other Windows XP/2000/NT' partition. This is your IBM Vendor Diagnostic partition, which is based on the Windows kernel, apparently. Select the first entry to boot Ubuntu. The next time you boot Windows, it will bring up a chkdsk screen. This is entirely normal and happens because we have resized the Windows partition. Make sure you do not skip this check and let it complete.

===Wireless LAN===

The first thing we should do is to get wireless networking working. Luckily, getting the Centrino wireless LAN chip working in Ubuntu is quite easy, if you use the gnome-network-manager applet. Just go to System - Administration - Synaptic Package Manager. Then click 'Search' and set the 'look-in' field to 'name'. In the 'Search' text box type:

<pre>network-manager</pre>

: Figure 6. Installing the network manager applet
: [[Image:networkmanager.jpg]]

Click on the box beside 'network-manager' and click 'Mark for installation'. Do the same for 'network-manager-gnome'. Once installed, reboot your thinkpad. An applet will show up in the gnome notification area. Click on it, and a list of detected wireless networks will be displayed. Simply click on one of them, enter any authentication details necessary, and you'll be connected to the wireless network.

: Figure 7. gnome-network-manager showing available wireless networks
: [[Image:available-accesspoints.jpg]]

Note! Not all versions of the T60 has the Intel Wireless LAN as described above. Run lspci from the command line and look for details of your wifi card. E.g.:

03:00.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)

suggest you have a different wifi card. Read this forum thread http://ubuntuforums.org/showthread.php?t=38972

running:
# dmesg | grep hal

may yield output like this, which apparently suggests the hardware abstraction layer is in place.
[17179590.420000] ath_hal: module license 'Proprietary' taints kernel.
[17179590.424000] ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)

If not, or if the output contains "HAL Status 13" it apparently suggests your card is not supported by the current drivers, and you need to upgrade.

===Installing the ATI display drivers===

If your ThinkPad has an Intel graphics adapter, you should skip this section as Ubuntu installs the best driver automatically. Ubuntu does not install the ATI proprietary drivers by default because they are, er, proprietary. Luckily, installing them is easy enough. Open a terminal (Applications - Accessories - Terminal) and type the following:

: {{cmduser| sudo apt-get update}}
: {{cmduser| sudo apt-get install xorg-driver-fglrx fglrx-control}}

Now we make sure the proprietary driver is not disabled by the kernel. Type the following, and remove any lines referring to fglrx

: {{cmduser|sudo gedit /etc/default/linux-restricted-modules-common}}

An alternative to gedit (Gnome) is nano (sudo nano -w /etc...) for a CLI editor.

Finally, we need to configure the X server to use the ATI drivers. Type the following:

: {{cmduser|sudo depmod -a}}
: {{cmduser|sudo aticonfig --initial}}
: {{cmduser|sudo aticonfig --overlay-type<nowiki>=</nowiki>Xv}}

One last thing. In order to correct a very common problem of getting a jerky video display, type the following:

: {{cmduser|sudo gedit /etc/X11/xorg.conf}}

Scroll to the end of the file, and add the text below.

<pre>
Section "Extensions"
Option "Composite" "0"
EndSection
</pre>

Save the file and exit. Now, to apply the changes either press CTRL+ALT+Backspace or reboot. The resolution should have switched to 1400x1050 and everything should look prettier and render faster. Just to make sure everything is working, open up a terminal and type

: {{cmduser|fglrxinfo}}

This should display:

<pre>
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Mobility Radeon X1400 Generic
OpenGL version string: 2.0.6011 (8.28.8)
</pre>

The above is what I get on my ThinkPad, and you should see something similar. As long as you see your graphics card model listed, everything should be OK. If, instead, you see a bunch of lines containing 'Mesa' then you have a problem. In that case, I recommend consulting https://help.ubuntu.com/community/BinaryDriverHowto/ATI and the Ubuntu forums at http://ubuntuforums.org

===The fingerprint reader===

Although IBM does not officially support it, the fingerprint reader does in fact work with most Linux distributions. Getting it to work with Ubuntu can be a bit of a pain, but it does work. Basically, a bioAPI plugin is provided for PAM. PAM-aware applications such as GDM and gnome-screensaver will then automatically use the fingerprint reader, which is uber cool. Anyway, enough theory, I've probably lost the newbies amongst you already. Go to http://www.qrivy.net/~michael/temp/ and download the latest bioapi package (at the time of writing, bioapi_1.2.3_i386.deb). When asked, tell Firefox to open the file with the GDebi package installer.

That will install bioAPI. What we need now is the driver for our fingerprint device, which is manufactured by UPEK. Go to http://www.upek.com/support/dl_linux_bsp.asp and download the latest version, currently UPEK_BSP_LIN_1.0.zip. Extract this file, then open a terminal (and don't close it until I say so).

: {{cmduser|cd /path/to/where/you/extracted/the/file}}
: {{cmduser|sudo bash}}
: {{cmdroot|sh install.sh /usr/lib}}

Now we need to assign the right permissions so non-root applications can use the driver:

: {{cmdroot|addgroup --system bioapi}}
: {{cmdroot|addgroup --system usbfs}}
: {{cmdroot|adduser yourusername bioapi}}
: {{cmdroot|adduser yourusername usbfs}}
: {{cmdroot|chown -R root:bioapi /usr/var/bioapi/}}
: {{cmdroot|chmod -R 770 /usr/var/bioapi/}}
: {{cmdroot|chown -R root:usbfs /proc/bus/usb}}
: {{cmdroot|chmod -R g+X /proc/bus/usb}}

Of course, replace 'yourusername' with the username you use to login. Now, we need to set the usb file system (usbfs) to be usable by users in the usbfs group. To do this, we need to determine the group ID of the usbfs group. Type the following:

: {{cmdroot|cat /etc/group | grep usbfs | cut -d':' -f 3}}

In my case the number is 116, it might be different for you. Now, open the file /etc/fstab:

: {{cmdroot|gedit /etc/fstab}}

and type the following:

<pre>none /proc/bus/usb usbfs defaults,devgid=116,devmode=0660,busgid=116,busmode=0770,listgid=116,listmode=0660 0 0</pre>

Please type the above code in one line in your file. Remember to replace 116 if you got a different number with the previous cat command. The last permission-related thing we need to fool around with is UDEV. Open the udev permissions file

: {{cmdroot|gedit /etc/udev/rules.d/40-permissions.rules}

and find the line:

<pre>SUBSYSTEM=="usb_device", MODE="0664"</pre>

It's line 65 in my file. Change it so it looks like this:

<pre>SUBSYSTEM=="usb_device", MODE="0660", GROUP="usbfs"</pre>

Now we need to enroll our fingerprint with the system. To do this, we need a utility called Sample, which is only distributed in source-code form with the driver. This is great, only I couldn't get it to compile on Ubuntu. Luckily, there is a binary version available from one of the earlier releases of the driver (beta 2). To get this, download it from ftp://linux:Tuc-nak3@delta.upek.com/TFMESS_BSP_LIN_1.0beta2.zip. Now, extract the file and type:

: {{cmdroot|cd /path/to/where/you/extracted/the/archive}}
: {{cmdroot|cd NonGUI_sample}}
: {{cmdroot|./Sample}}

Press (e) to enroll a new user, and enter your username when asked for the user ID. You will be asked to swipe your finger three times. Now press (v) and swipe your finger, a green check should be displayed showing you have successfully authenticated.

: Figure 8. The fingerprint swipe prompt
: [[Image:touchchip.jpg]]

Wonderful! Now, quit the application (q) and type exit to become a normal user. A file called yourusername.bir should have been created, copy this to your home directory:

: {{cmdroot|cp yourusername.bir /home/yourusername/}}

You can now close the terminal window. The next step is to install the BioAPI plug-in for PAM, and to make applications use the plugin. So, get the pam_bioapi plugin from http://www.nax.cz/pub/bioapi/pam_bioapi/pam-bioapi_0.3.0.tar.gz and extract it. Now open a terminal and type:

: {{cmduser|cd /path/to/where/you/extracted/the/arcive}}
: {{cmduser|./configure --libdir<nowiki>=</nowiki>/lib --enable-file-store && make}}
: {{cmduser|sudo make install}}

That's installed the plugin. Now, open a terminal and type the following scary commands: (Note: The line starting 'SERIAL=' and the line following it should be in the same line).

: {{cmduser|cd ~}}
: {{cmduser|sudo bash}}
: {{cmdroot|SERIAL=`BioAPITest | sed -ne "/Fingerprint/{n;n;s/^.*: $.\{9\}$$.\{4\}$$.\{4\}$$.\{4\}$$.*$/\1-\2-\3-\4-\5/gp}"`}}
: {{cmdroot|mkdir -p /etc/bioapi/pam/$SERIAL}}
: {{cmdroot|cp yourusername.bir /etc/bioapi/pam/$SERIAL}}
: {{cmdroot|exit}}

Phew. Now, to make applications actually use the fingerprint reader. Open a terminal window, and type:

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

Delete everything in the file, and paste this instead:

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

Save and close the file. That will make all PAM-aware applications use the fingerprint reader. Unfortunately, this also includes sudo. Since sudo is a command line application, it will display prompts in a terminal for you to swipe your finger, which is all well and good. The problem with this is that many Ubuntu administrative applications (such as Synaptic) use gksu to present a graphical front-end to sudo, which will output messages on the command line which you'll never see. Result? Administrative programs won't work from the gnome menu. The solution is to make sudo use the good old password. Open a terminal and type:

: {{cmduser|sudo gedit /etc/pam.d/sudo}}

Delete everything in the file, and instead paste:

<pre>
#%PAM-1.0

#@include common-auth
auth required pam_unix.so nullok_secure
@include common-account
</pre>

Now, save the file and close it, and reboot your system. GDM will ask you for a username, and then show a pretty prompt where you can scan your fingerprint! Same goes for gnome-screensaver when you set it to lock. Sometimes gnome-screensaver will not display the prompt, but you should still swipe your finger and be able to log back in.

===Bluetooth with Mobile Phones/PDAs===

Rather strangely, Ubuntu seems to have taken a step backwards with Bluetooth useability in Edgy. What worked out of the box with Dapper, now requires configuratio. First, open System - Preferences - Sessions and go to the Startup Programs tab. Then, find the entry labelled 'bt-applet --sm-disable'. Highlight it and click disable. Click add and in the command field type 'bt-applet'. Repeat this process, adding an entry for 'gnome-obex-server'. Now, open Synaptic Package Manager (System - Administration - Synaptic Package Manager) and click Search. Type 'gnome-bluetooth' to find the package, then mark it for installation. Now repeat this process for 'bluez-passkey-gnome'. Click apply to make changes.

Now that everything is installed, log-out of Gnome and log back in again. From your phone/PDA, search for devices untill you see your ThinkPad (the hostname will be displayed). Pair with the device. When asked for a passkey, enter 1234, which is the default. If you want to change your passkey (and you should), open a terminal and type:

: {{cmduser|sudo gedit /etc/bluetooth/hcid.conf}}

Find the line which says 'Default PIN for incoming connections' and change the PIN on the line beneath it:

<pre>
# Default PIN code for incoming connections
passkey "4017";
</pre>

Save and close the file, then type:

: {{cmduser|sudo /etc/init.d/bluetooth restart}}

You will now be able to use your new PIN code. To send files from your device to the ThinkPad, simply select the file you want to send and click Send Via Bluetooth (or whatever option your device presents). A dialog will pop-up in Gnome showing you a new file has been received.

: Figure 9. Gnome informing us that a file has been received
: [[Image:bluetooth.jpg]]

Sending files from your ThinkPad to your device requires more effort. The way it should work is that you right-click on a file, click send to, then make sure 'Bluetooth (OBEX)' is selected. Your device should be displayed and you could just click send. Unfortunately, due to a bug in gnome-bluetooth (described in https://launchpad.net/distros/ubuntu/+source/gnome-bluetooth/+bug/70718) this method does not work. If it does work for you, the bug has been solved and you can skip the rest of this section.

Your only other option is to use the command line to send files to your device. Open a terminal, then type:

: {{cmduser|hcitool scan}}

A list of detected bluetooth devices will be shown, for example, my output shows the following:

<pre>
Scanning ...
00:09:DD:60:02:EB Photosmart 8100 series
00:14:A7:99:3C:1F ThElInK
</pre>

The first field is the MAC address of the device, the second is the name of the device. In this case my bluetooth printer and mobile phone (ThElInK) were detected. In order to send files to my phone, I use:

: {{cmduser|gnome-obex-send -d 00:14:A7:99:3C:1F myPicture.jpg}}

Replace the MAC address with that of your device and myPicture.jpg with the file you want to send.

===TrackPoint Scrolling===

By default you can use the right and bottom edges of your touchpad to scroll through documents. If you use the TrackPoint instad of the touchpad (and believe me, you should), you'll find that scrolling is disabled by default. To enable it, open a terminal and type:

: {{cmduser|sudo gedit /etc/X11/xorg.conf}}

Now find the entry for your TrackPoint device. In my configuration file, the TrackPoint entry is the first mouse entry, after the keyboard entry, and looks something like this:

<pre>
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection
</pre>

Right after this entry is my touchpad entry. My entry is on line 66, but yours may be different. Now, add the follwing two options in that InputDevice section:

<pre>
Option "EmulateWheel" "on"
Option "EmulateWheelButton" "2"
</pre>

Save and exit the file. Restart your ThinkPad (or logout, and press CTRL-ALT-BACKSPACE). You should now be able to scoll by holding down the middle button for your TrackPoint and using the TrackPoint to scroll.

===Getting Multimedia to Work===

Due to patents and similar legal crap, Ubuntu will not play most media files by default. You also won't get browser plugins for multimedia. Luckily, this is easily fixed. Open a terminal and type the following:

: {{cmduser|sudo cp /etc/apt/sources.list /etc/apt/sources.list.backup}}
: {{cmduser|sudo gedit /etc/apt/sources.list}}

Delete everything in the file, and instead paste the following:

<pre>
deb-src http://archive.ubuntu.com/ubuntu edgy main restricted universe multiverse
#deb http://archive.ubuntu.com/ubuntu edgy-proposed main restricted universe multiverse

## MAJOR BUG FIX UPDATES produced after the final release
deb-src http://archive.ubuntu.com/ubuntu edgy-updates main restricted universe multiverse

## UBUNTU SECURITY UPDATES
deb http://security.ubuntu.com/ubuntu edgy-security main restricted universe multiverse
deb-src http://security.ubuntu.com/ubuntu edgy-security main restricted universe multiverse

## BACKPORTS REPOSITORY (Unsupported. May contain illegal packages. Use at own risk.)
#deb http://archive.ubuntu.com/ubuntu edgy-backports main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu edgy-backports main restricted universe multiverse

## PLF REPOSITORY
deb http://packages.freecontrib.org/ubuntu/plf edgy-plf free
deb-src http://packages.freecontrib.org/ubuntu/plf edgy-plf free
deb http://packages.freecontrib.org/ubuntu/plf edgy-plf non-free
deb-src http://packages.freecontrib.org/ubuntu/plf edgy-plf non-free

## CANONICAL COMMERCIAL REPOSITORY (Hosted on Canonical servers, not Ubuntu
## servers. RealPlayer10, Opera, DesktopSecure and more to come.)
deb http://archive.canonical.com/ubuntu edgy-commercial main

## Listen
#deb http://theli.free.fr/packages/ edgy listen

## Automatix repo
deb http://www.getautomatix.com/apt edgy main
</pre>

Now, open a terminal and type the following:

: {{cmduser|wget http://packages.freecontrib.org/ubuntu/plf/12B83718.gpg -O- | sudo apt-key add -}}
: {{cmduser|wget http://www.getautomatix.com/apt/key.gpg.asc}}
: {{cmduser|gpg --import key.gpg.asc}}
: {{cmduser|gpg --export --armor 521A9C7C | sudo apt-key add -}}
: {{cmduser|sudo apt-get update}}
: {{cmduser|sudo apt-get install automatix2}}
: {{cmduser|wget http://easyubuntu.freecontrib.org/files/easyubuntu-3.023.tar.gz}}
: {{cmduser|tar -zxf easyubuntu-3.023.tar.gz}}
: {{cmduser|cd easyubuntu}}
: {{cmduser|cp packagelist-dapper.pot packagelist-edgy.pot}}
: {{cmduser|cp packagelist-dapper.xml packagelist-edgy.xml}}
: {{cmduser|sudo python easyubuntu.in}}

Don't worry if you get errors from the Ubuntu PLF repository. PLF mirrors are about as stable as wild bull in a farm full of cows. Select what you want to install from the resulting window. Make sure you do not select the totem-mozilla plugin, as this just doens't work, for me at least. When EasyUbuntu has finished installing packages, you should be returned to a terminal, which you can close. Now go to Applications - System Tools - Automatix. Read and agree to the warning. Check what you want to install. Make sure you check 'Mplayer and FF plugin'. When ready, click the 'install' button. That should get multimedia working nicely.

: Figure 10. The Automatix user interface
: [[Image:automatix.jpg]]

===Beryl - fancy 3D desktop===

MAC OS X has Aqua and Windows Vista has Aero. Well, Linux has XGL/Beryl which can get effects which are as good looking (or sometimes better!) than the former two. Installing Beryl on Ubuntu is not that hard. First, open a terminal and type the following:

: {{cmduser|sudo gedit /etc/apt/sources.list}}

At the end of the file, append the following:

<pre>
##Beryl
deb http://ubuntu.beryl-project.org/ edgy main
</pre>

Save and close the file. Now type:

: {{cmduser|wget http://beryl-mirror.lupine.me.uk/1609B551.gpg -O- | sudo apt-key add -}}
: {{cmduser|sudo apt-get update}}

ATI Users Only: type

: {{cmduser|sudo apt-get install xserver-xgl}}

Now, to install beryl:

: {{cmduser|sudo apt-get install beryl emerald-themes}}

To make Ubuntu use the 3D effects. Open a terminal:

: {{cmduser|sudo gedit /usr/local/bin/startxgl.sh}}

In that file, paste the following if you use an ATI card:

<pre>
#!/bin/sh
Xgl -fullscreen :1 -ac -br -accel glx:pbuffer -accel xv:pbuffer &
sleep 4
export DISPLAY=:1
exec gnome-session
</pre>

If you use an Intel card, paste the following instead:

<pre>
#!/bin/sh
beryl-manager
sleep 4
exec gnome-session
</pre>

Save the file and close. Now we need to make the file executable:

: {{cmduser|sudo chmod a+x /usr/local/bin/startxgl.sh}}

All that's left now is to create a login script which makes gnome use the 3D effects. In a terminal, type:

: {{cmduser|sudo gedit /usr/share/xsessions/xgl.desktop}}

Now, in this file paste:

<pre>
[Desktop Entry]
Encoding=UTF-8
Name=Xgl
Exec=/usr/local/bin/startxgl.sh
Icon=
Type=Application
</pre>

Save and close the file. Now type:

: {{cmduser|sudo gedit /usr/local/bin/start_beryl.sh}}

In this file, paste:

<pre>
#!/bin/bash
#
# Start beryl-manager within gnome-session
#
if [ `ps -A -o comm | grep -c '^Xgl$'` == "1" ]; then
DISPLAY=:1 beryl-manager
DISPLAY=:1 beryl-xgl
else echo "${0}: Error: beryl-manager not launched. Xgl not running?"
fi
</pre>

Now make the file executable:

: {{cmduser|sudo chmod a+x /usr/local/bin/start_beryl.sh}}

Now go to System - Preferences - Sessions, go to the Startup Programs tab, and click add, then type

: {{cmduser|/usr/local/bin/start_beryl.sh}}

Now, reboot your ThinkPad. When you come to the login screen, click the 'Sessions' button on the bottom left corner, and select XGL. login, et voila! beautiful 3D effects!

: Figure 11. Beryl's Cube effect
: [[Image:cube.jpg]]

If you have NetBeans installed, try launching it now. It probably won't work due to Beryl. Luckily, this is easily solved. Open a terminal and type:

: {{cmduser|sudo gedit /etc/environment}}

Then add the following line to the end of the file.

<pre>AWT_TOOLKIT="MToolkit"</pre>

Now save, close and reboot. Netbeans should now work!

===Problem: Can't add programs to session===

So you tried to add something to your startup programs, it shows up in the list, but it doesn't start up. You then launch the sessions program again, only to find your program has disappeared from the list. This problem is being caused by incorrect permissions in your home directory, and can happen on some occasions. To fix it, open a terminal and type the following:

: {{cmduser|sudo chown -R username:usergroup /home/username/.config/}}

Replace username with your username and usergroup with your group (by default, in Ubuntu your usergroup is the same as your username). Everything should be OK now!

===Problem: Virtual terminals not working===

One problem I had after installing the ATI drivers was that virtual terminals stopped working. Instead of seeing a console when pressing CTRL+ALT+F1...F6 I was seeing a yellow/orange garbled output. Luckily, solving this with ATI drivers is trivial. Open a terminal, and type:

: {{cmduser|sudo gedit /boot/grub/menu.lst}}

Find the line which says

<pre>#defoptions=quiet splash</pre>

and replace it with

<pre>#defoptions=quiet splash vga=791</pre>

Now, find the line which boots the kernel you are currently using, this is just under '## ## End Default Options ##. In the 'kernel' line, add:

<pre>vga=791</pre>

Before:

<pre>kernel /vmlinuz-2.6.17-10-generic root=/dev/sda7 ro quiet splash</pre>

After:

<pre>kernel /vmlinuz-2.6.17-10-generic root=/dev/sda7 ro quiet splash vga=791</pre>

Now save and exit the file, and reboot. Virtual terminals should now work. If you use Intel drivers, you're going to have to bite the bullet and remove the 'splash' keyword from both the defoptions and kernel lines. You'll lose the pretty bootup screen, but at least virtual terminals will work, which are important to recover a crashed system.

===Problem: I keep logging out!===

If you're using Beryl, and find that you keep getting logged out, you've just encountered one of Beryl's most annoying bugs. Shift+Backspace causes a logout. To fix this, open a terminal and type:

: {{cmduser|gedit /home/username/annoymenot.sh}}

Remember to replace 'username' with your username. Now, in this file type:

: {{cmduser|xmodmap -e "keycode 22 <nowiki>=</nowiki> BackSpace BackSpace Terminate_Server" }}

Save and close the file, and make it executable:

: {{cmduser|chmod 755 /home/username/annoymenot.sh}}

Now go to System - Preferences - Session, Startup Programs. Click add, and type

: {{cmduser|/home/username/annoymenot.sh}}

Logout and back in, problem solved! While you're at it, how about getting the start button to work? Go to System - Preferences - Keyboard - Layout Options - Alt/Win Key behaviour and select 'Super is mapped to Win keys (default)'.

===Desktop envy===

We're living in an age of desktop prettyness, and Linux can be just as pretty as MAC OS X or Vista. You've already got Beryl installed. Now go to Applications - Accesories - gDesklets. If the gDesklets entry is not there, make sure you install it, either using Synaptic or Automatix. Desklets are small programs you can add to your desktop, ala OS X's Deskbar or Vista's Sidebar. To make them start on boot, add gdesklets in System - Preferences - Sessions, Startup Programs.

Another cool program is cairo clock. Download it from http://macslow.thepimp.net/projects/cairo-clock/cairo-clock_0.3.2-1_i386.deb and install it by double-clicking. To make it start automatically, add it to your sessions as mentioned above. I've found the following command makes it work best for me:

<pre>cairo-clock -s -w 175 -g 175 -x 1219 -y 7 -t radium</pre>

Finally, make sure you click that Ruby icon in your notification area, it allows you to configure Beryl to do all sorts of cool stuff!

===Conclusion===

Well, that's about it! A dream Linux system on a dream laptop! Check out these cool technologies for an even better system:

* Beagle
* Tomboy
* Deskbar

===References===

* ATI on Ubuntu - https://help.ubuntu.com/community/BinaryDriverHowto/ATI
* Garbled Virtual Terminal Bug - https://launchpad.net/distros/ubuntu/+source/usplash/+bug/63558
* Beryl logout Bug - http://forum.beryl-project.org/viewtopic.php?p=1295&sid=6feedd09a7f01bca68feb05a5f2f033c
* Beryl Netbeans Bug - http://ubuntuforums.org/showthread.php?t=252594
* Beryl on Ubuntu - http://wiki.beryl-project.org/index.php/Install/Ubuntu/Edgy/XGL
* Home directory permissions bug - http://www.ubuntuforums.org/showthread.php?p=1789997
* gnome-bluetooth bug - https://launchpad.net/distros/ubuntu/+source/gnome-bluetooth/+bug/70718

Problem with e1000: EEPROM Checksum Is Not Valid

2006-08-31T14:42:21Z

Ischg: /* Circumvention */

== Problem Description ==
On certain ThinkPads, [[e1000]] driver for [[Ethernet_Controllers#Intel_Gigabit_.2810.2F100.2F1000.29|Intel Gigabit controller]] fails to load with the following error message in /var/log/messages:

<pre>
e1000: 0000:02:00.0: e1000_probe: The EEPROM Checksum Is Not Valid
e1000: probe of 0000:02:00.0 failed with error -5
</pre>

== Circumvention ==

* Upgrade your BIOS

Lenovo has published newer BIOS revisions that appear to fix the issue for some users. The BIOS upgrade turns off "Deep smart power down" which has been known to cause issues at initialization time (the driver can re-enable the issue later if you desire, the feature works correctly then).

* Insert a cable

Inserting a linked network cable bypasses the problem.

* Dangerous: turn off checksum checking in the driver

''Disabling the checksum checking is dangerous: the network card has (obviously) read incorrect data from the EEPROM and will start operation based on these wrong values. You will see degraded network performance and possible data corruption and driver crashes. '''DO THIS AT YOUR OWN RISK'''.''

In <tt>e1000_main.c</tt>, find the following code and comment out err assignment and the goto statement:

<pre>
/* make sure the EEPROM is good */
if (e1000_validate_eeprom_checksum(&adapter->hw) < 0) {
DPRINTK(PROBE, ERR, "The EEPROM Checksum Is Not Valid\n");
/* err = -EIO;
goto err_eeprom; */
}
</pre>

<i>Note</i>: This is just a temporary solution until a better fix is developed. See the [http://sourceforge.net/tracker/index.php?func=detail&aid=1474679&group_id=42302&atid=447449 bug report] for more information.

* Remove/add kernel module

Removing and adding the kernel module is a possible work-around. As root, run

<pre>
# modprobe -r e1000
# modprobe e1000
</pre>

On some occasions, the commands have to be run twice before eth0 becomes useable.

== See also ==

* [http://sourceforge.net/tracker/index.php?func=detail&aid=1474679&group_id=42302&atid=447449 bug report] submitted for e1000 driver.
* Discussion at [http://forums.gentoo.org/viewtopic-t-476305-highlight-e1000.html Gentoo forums]

Known Problems

2006-08-23T02:36:03Z

Ischg:

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
Information on known problems with certain ThinkPad models.
|}
==Display Problems==
*[[Problem with unusable console | Console unusable]] <tt>(models with savage video chipset: T2x, A22e)</tt>
*[[Problem with Pixel Error | Dead pixels on TFT displays]] <tt>(all models)</tt>
*[[Problem with DVI throughput | DVI throughput on port replicators and docks]] <tt>(models from 2000-2004)</tt>
*[[Problems with fglrx | fglrx problems]] <tt>(ATI Radeon models)</tt>
*[[Problem with garbled screen | Garbled Screen]] <tt>(T40, T41, T42, R40, A30, A31, A31p)</tt>
*[[Problem with broken inverter | Inverter broken]] <tt>(all models)</tt>
*[[Problem with key and trackpoint markings on the display | Key and Trackpoint markings on display]]
*[https://bugs.freedesktop.org/show_bug.cgi?id=2187 Radeon 7500 "DynamicClocks" randomly hangs] <tt>(TP T4x, Xorg-X11 bug report)</tt>
*[[Problem with red display shadow | Red shadow on display]] <tt>(TP T41p)</tt>
*[[Problem with red tinted display | Red tinted display]] <tt>(TP 23)</tt>
*[[Problem with black X | Unmovable square black X in X]] <tt>(TP T2x)</tt>
*[[Problem with video related system lockup | System Lockups related to video adapter]] <tt>(TP T2x)</tt>
*[[Problem with video related system lockup II | System Lockups related to video adapter T42]] <tt>(TP T42, T42p)</tt>
*[[Problem with ati driver in xorg 6.9.x | System lockup soon after starting xorg 6.9.x ]] <tt>(TP T4x)</tt>
*[[Problem with video output switching | Video output switching]]

==Harddisk Drive related Problems==
*[[Problem with APS harddisk parking|APS harddisk parking]] <tt>(models featuring APS)</tt>
*[[Problem with too large harddrive|BIOS hangs with harddrive sized over 8G]] <tt>(560)</tt>
*[[Problem with hard drive clicking | Clicking Hard Drive]] <tt>(models with Hitachi's 5k80 hard drive)</tt>
*[[Problem with non-ThinkPad hard disks|Non-ThinkPad hard disks]] <tt>(T43, X41, R52)</tt>
*[[Problems with SATA and Linux|SATA and Linux]] <tt>(T43, X41, R52, Z60)</tt>

==Network Problems==
*[[Problem with 3Com 10/100 Ethernet card not being recognized|3Com 10/100 Ethernet card not recognized]] <tt>(models with that card)</tt>
*[[Problem with unauthorized MiniPCI network card|"Unauthorized" MiniPCI Wireless Network card error (Error 1802)]] <tt>(Recent TPs)</tt>
*[[Cisco Aironet Wireless 802.11b]] fails to work with certain firmware versions
*[[Problem with error 01C9 - More than one Ethernet devices | Error 01C9: More than one Ethernet Devices are found (Atheros WLAN MiniPCI)]] <tt>(T30, A31p, R40 and others)</tt>
*[[Problem with e1000: EEPROM Checksum Is Not Valid]] <tt>(T60, X60, may be others)</tt>

==Power Management, AC-adapter or Battery Problems==
*[[Problem with ThinkPad 600 batteries | 600 series Battery dying prematurely]] <tt>(TP 600/E/X)</tt>
*[[Damage in 56W AC-Adapter, plastic housing melted |AC-Adapter damaged, plastic housing melted]] <tt>(240, 390, i and s models)</tt>
*[[Problems with ACPI suspend-to-ram|ACPI suspend-to-ram]] <tt>(ACPI sleep troubles)</tt>
**[[Problem with display remaining black after resume|Blank display after resume]] <tt>(various models)</tt>
**[[Problem with high power drain in ACPI sleep | High power drain in ACPI sleep]] <tt>(various models)</tt>
**[[Problem with LCD backlight remaining on during ACPI sleep | LCD backlight remaining on during ACPI sleep]] <tt>(various models)</tt>
*[[Problem with fan noise | Fan noise]] <tt>(TP T4x/p, TP R5x/p)</tt>
*[[Problem with checking battery status | Checking battery status causes mouse to jerk around]] <tt>(R31)</tt>
*[[Battery drains despite seemingly being charged]] <tt>(A/C adapter issues)</tt>
*[[Problem with high pitch noises | High pitch noises]] <tt>(several models)</tt>

==Sound Problems==
*[[Problem with broken sound on ThinkPad 600 | Broken sound on ThinkPad 600/E]] <tt>(TP 600/E/X, 770Z)</tt>
*[[Problem with audio jacks | Audio jacks not working properly]] <tt>(TP T43)</tt>
*[[Problem with ALSA audio output | No audio heard with kernel 2.6.11+/ALSA]] <tt>(TP T43, T40)</tt>
*[[Problem with audio clipping|Audio clipping]] <tt>(TP T43)</tt>

==Misc Problems==
*[[Problem with Bending / Twisting|Casing malformed by bending/twising]] <tt>(X41)</tt>
*[[Problem with Dock USB Ports | Dock USB Ports]] <tt>(T30)</tt>
*[[High-pitch noise from AC-Adapter]] <tt>(T60/p)</tt>
*[[Problem with lm-sensors | lm_sensors kills ThinkPads]] <tt>(TP 570E, 770X/Z, 600E/X, 240, X20)</tt>
*[[Problem with USB 2.0 | USB 2.0 problems]] <tt>(T40)</tt>

[[de:Bekannte_Probleme]]

Problem with e1000: EEPROM Checksum Is Not Valid

2006-08-22T06:56:47Z

Ischg: /* Circumvention */

== Problem Description ==
On certain ThinkPads, [[e1000]] driver for [[Ethernet_Controllers#Intel_Gigabit_.2810.2F100.2F1000.29|Intel Gigabit controller]] fails to load with the following error message in /var/log/messages:

<pre>
e1000: 0000:02:00.0: e1000_probe: The EEPROM Checksum Is Not Valid
e1000: probe of 0000:02:00.0 failed with error -5
</pre>

== Circumvention ==

* Upgrade your BIOS

Lenovo has published newer BIOS revisions that appear to fix the issue for some users. The BIOS upgrade turns off "Deep smart power down" which has been known to cause issues at initialization time (the driver can re-enable the issue later if you desire, the feature works correctly then).

* Insert a cable

Inserting a linked network cable bypasses the problem.

* Dangerous: turn off checksum checking in the driver

''Disabling the checksum checking is dangerous: the network card has (obviously) read incorrect data from the EEPROM and will start operation based on these wrong values. You will see degraded network performance and possible data corruption and driver crashes. '''DO THIS AT YOUR OWN RISK'''.''

In <tt>e1000_main.c</tt>, find the following code and comment out err assignment and the goto statement:

<pre>
/* make sure the EEPROM is good */
if (e1000_validate_eeprom_checksum(&adapter->hw) < 0) {
DPRINTK(PROBE, ERR, "The EEPROM Checksum Is Not Valid\n");
/* err = -EIO;
goto err_eeprom; */
}
</pre>

<i>Note</i>: This is just a temporary solution until a better fix is developed. See the [http://sourceforge.net/tracker/index.php?func=detail&aid=1474679&group_id=42302&atid=447449 bug report] for more information.

* Remove/add kernel module

Removing and adding the kernel module is a possible work-around. As root, run

<pre>
# modprobe -r e1000
# modprobe e1000
</pre>

== See also ==

* [http://sourceforge.net/tracker/index.php?func=detail&aid=1474679&group_id=42302&atid=447449 bug report] submitted for e1000 driver.
* Discussion at [http://forums.gentoo.org/viewtopic-t-476305-highlight-e1000.html Gentoo forums]

Problem with high pitch noises

2006-08-19T18:47:01Z

Ischg: /* Affected Models */

Information on strange high pitch, low volume noises emitted by ThinkPads.

==Problem description==
Even though ThinkPads are known as very silent notebooks, they tend to emit different, mostly high pitch noises in certain circumstances. The noises are of low volume and hence not realized by everyone or at least tolerated by most people. However, there are those with "bat like ears" that hear them and might be annoyed by that.

==Affected Models==
Noises have been experienced in the following situations:
{| border="1" cellspacing="0" cellpadding="2"
|-
! style="vertical-align:top;background-color:#DDDDDD;" | situation
! style="vertical-align:top;background-color:#DDDDDD;" | noise description
! style="vertical-align:top;background-color:#DDDDDD;" | affected models
|-
| style="vertical-align:top;" |
Plugged into AC / running at high CPU frequency
| style="vertical-align:top;" |
soft crackling, buzzing noise
| style="vertical-align:top;" |
*{{T41}}
**2379-DJU
|-
| style="vertical-align:top;" |
ThinkPad suspended to RAM
| style="vertical-align:top;" |
constant high pitch noise
| style="vertical-align:top;" |
*{{T42p}}
|-
| style="vertical-align:top;" |
ThinkPad connected to power and switched off, with battery fully charged
| style="vertical-align:top;" |
constant high pitch noise
| style="vertical-align:top;" |
*{{T41p}}
**2373-GHG
|-
| style="vertical-align:top;" |
moving windows or just the mouse in xorg
| style="vertical-align:top;" |
strange noise like a rapid series of very short high pitch noises adding to a constant kind of whistling (only as long as the movement goes)
| style="vertical-align:top;" |
*{{T41p}}
**2373-GHG
|-
| style="vertical-align:top;" |
Thinkpad connected to power or working on battery, also when suspended to RAM
| style="vertical-align:top;" |
High pitch noise also when HD is powered down.
| style="vertical-align:top;" |
*{{T23}}
**2647-DG4
*{{X24}}
**2662-MWG
|-
| style="vertical-align:top;" |
Thinkpad connected to power battery charged less than 60%
| style="vertical-align:top;" |
High pitch noise till battery is charged more than 60%.
| style="vertical-align:top;" |
*{{T41p}}
**2373-GEG
|-
| style="vertical-align:top;" |
Constantly, if AC connected
| style="vertical-align:top;" |
High pitched, low volume constant noise.
| style="vertical-align:top;" |
*{{T40}}
**2373-88U
|-
| style="vertical-align:top;" |
When the CPU freq jumps up to 1Ghz or above, or when the laptop is in suspend mode
| style="vertical-align:top;" |
Constant high pitched
| style="vertical-align:top;" |
*{{R50}}
**1829-6DM
|-
| style="vertical-align:top;" |
(May come from harddisk.)
| style="vertical-align:top;" |
continuous, intermittent, low volume, high pitched
| style="vertical-align:top;" |
*{{600X}}
|-
| style="vertical-align:top;" |
ACPI puts the processor into the C3 or C4 power saving states (i.e., the system is idle).
| style="vertical-align:top;" |
High-pitched crackling noise.
| style="vertical-align:top;" |
*{{X41}}
*{{T43}}
**2686-DGU
*{{T43p}}
*{{T60}}
**2007-72U
*{{T21}}
|-
| style="vertical-align:top;" |
Cpufreqd (or powernowd etc.) slows down the processor, for exemple at the end of an heavy task.
| style="vertical-align:top;" |
High-pitched crackling noise.
| style="vertical-align:top;" |
*{{T42}}
|-
| style="vertical-align:top;" |
When on battery
| style="vertical-align:top;" |
Almost inaudible screeching sound, or sometimes beeping (when wifi is on)
| style="vertical-align:top;" |
*{{R52}}
**1858-A11
*{{T43}}
**2686-DGU
*{{T60}}
**2007-72U
*{{x60}}
*{{x31}}
**2673-CBU

|-
| CPU is used much AND laptop is on AC power AND the TFT panel is enabled.
| Screetching high pitch noise, like a million crickets
|
* {{X41}}

|-
| Network is pluged in and networkload is ~100%.
| low volume highfreq. pitch noise from left speaker or cpu.
|
*{{Z60}}
|}

==Affected Operating Systems==
All, though Linux appears especially susceptible.

==Possible sources==

* '''CPU activity:''' On some models the noise is triggered by certain CPU power states or activity patterns (as proven [http://www.wisdom.weizmann.ac.il/~tromer/acoustic here]).
* '''Graphics processor:''' In some models from the T2x era, e.g. the {{T23}}, the problem was related to the graphics circuitry and occured especially or only while making use of DirectDraw functions. IBM was able to fix it through a BIOS upgrade.
* '''Hard disk:''' On some ThinkPads the processor and hard disk are adjacent and produce similar noise. For example, in the {{X41}} the sound generated by the hard disk is likely to be loudest at the vent.

==Status==

The problem is highly specific to operating system, model and even individual machines. There is no universal solution, but on most machines one of the following will reduce or eliminate the noise (possibly at some cost in power consumption).

==Solutions for CPU-triggered noise==

===Limit ACPI CPU power states===

There are four ACPI CPU power states, called C1 through C4. Often only the extreme power saving modes C4 or C3 produce the noise, so the noise can be stopped by insructing the Linux ACPI code to use only lower modes.

To forbid the ACPI driver from using C4 (this fixed the problem with on some ThinkPad {{T43}}, {{T43p}} and {{T41}}):
* If the ACPI processor component is compiled as built-in (<tt>CONFIG_ACPI_PROCESSOR=y</tt>):
**Pass the {{bootparm|max_cstate|3}} kernel argument.
* If the ACPI processor component is loaded as a module (<tt>CONFIG_ACPI_PROCESSOR=m</tt> and <tt>processor</tt> shows in the output of {{cmdroot|lsmod}}), do either of:
** Pass the {{bootparm|processor.max_cstate|3}} kernel argument (this does not work in Ubuntu 5.10 with default kernel).
** Add <code>options processor max_cstate=3</code> to {{path|/etc/modprobe.conf}} (or {{path|/etc/modprobe.conf.local}}, or {{path|/etc/modprobe.d/...}}, depending on your system) (this does not work in Ubuntu 5.10 with default kernel).
** {{cmdroot|echo 3 > /sys/module/processor/parameters/max_cstate}} (this can be changed in runtime for experimentation). (If may need to be set again upon resume from suspend, e.g., in the wakeup script.)
** (On Ubuntu 5.10, the default kernel uses <code>processor</code> as a module. Unfortunately, the script loading it, {{path|/etc/init.d/acpid}}, ignores the <code>options processor max_cstate=3</code> setting in {{path|/etc/modprobe.d/<my file>}}. As a solution for this specific problem, add the line <code>echo 2 > /sys/module/processor/parameters/max_cstate</code> directly to {{path|/etc/init.d/acpid}}, at the end of the function <code>load_modules()</code>, immediately after the line <code>echo "$PRINTK" > /proc/sys/kernel/printk</code>.)

To also forbid the C3 state, replace "<tt>3</tt>" with "<tt>2</tt>" above (this fixed the problem on some ThinkPad {{X40}}, {{X41}}, and {{R52}}):

Note that these options affect power consumption when the CPU is idle. For example, here are the power consumption figures on a ThinkPad {{T43}}:
* {{bootparm|processor.max_cstate|4}}: 15160mW (default, noisy)
* {{bootparm|processor.max_cstate|3}}: 15770mW (660mW higher, silent)
* {{bootparm|processor.max_cstate|2}}: 16100mW (2940mW higher, silent)

See the [http://thinkwiki.org/wiki?title=Talk:Problem_with_high_pitch_noises discussion page] for further information and success reports.

*Jakob Schou Pedersen: Editing the file {{path|/etc/init.d/acpid}} as described above (the last solution) worked on my T43 :-)

===Turn off CPU power saving in in BIOS===

Go into the BIOS and turn off the power saving processor feature that puts it into idle mode. (This worked on a ThinkPad {{T43}}, {{T21}} and {{X60s}}.)

===Disable ACPI CPU power states===

Completely disable CPU ACPI power states. Discussion:

*From Martin Steigerwald: I made the observation that I get at least less high pitch noises on my {{T23}} when I do not use the two ACPI modules "processor" and "thermal" (depends on the first one). I have no clue, why. Anyone with similar experiences?
:Omar Yasin: I've got a {{R52}} and when I load the same ACPIO modules the high pitch noises are not as loud but I can still hear them.
*Niko Ehrenfeuchter: I'm experiencing the same here on my {{X24}}. Removing the "processor" module also stops the pitch noise, which does ONLY occur when setting the CPU to maximum speed (using cpufreq). On low speed it's completely silent, even having loaded the processor module.

*Rolf Adelsberger: I can confirm this: the high pitch noise is only remarkable (at least with my ears ;-) ) if the processor speed is set to maximum frequency.

*Stefan Baums: My {{X41}} produced a high-pitched crackle from the processor vent on the left. Changing HZ did nothing, and the 'processor' module could not easily be removed from the system (Ubuntu 5.04). What solved the problem for me was adding {{bootparm|idle|halt}} to the boot command line. Unfortunately, this solution only lasts until the first hibernation or suspend - when the computer ({{X41}}) resumes, the high-pitched crackle is back.

* The {{bootparm|idle|halt}} solution combined with setting <code>#define HZ 100</code> in the kernel fixes the problem on a {{T43}}.

* jhatch: {{bootparm|idle|halt}} plus <code>#define HZ 100</code> also worked on my {{T43}}. It still reverts back to noisy after a suspend/resume though. This needs to be fixed...

===Change the timer interrupt frequency===

Change the "HZ" kernel constants to alter the frequency of timer interrupts. Discussion:

{{NOTE|The timer interrupt frequency (HZ) in current Linux kernels is directly tied to the kernel task scheduler. Lower frequencies provide larger time-slices and thus also higher latencies (which may kill latency-sensitive applications like audio processing). 100Hz ended up as the recommended "server" setting (because it increases disk/CPU throughput in a latency-insensitive environment). Higher frequencies are better for latency-sensitive applications, and improve desktop responsivity at the cost of less processor throughput. 1000Hz ended up as the recommended "desktop" setting.}}

*Andreas Karnahl: i've read in several forums it has something to do with the "idle"-state (or "C3") of the processor. There is a frequency called "timer interrupt" (or so mething like that). Since kernel 2.6x it is set to 1000 Hz by default (compared to 100 Hz in Kernel 2.4x). The exact reason i don't know, but it is safe to change this frequency to 100 Hz in kernel 2.6x (by the way, windows up to XP uses 100 Hz by default).<br />Just do the following:<br />
: In {{path|[path to kernel-sources]/include/asm-i386/param.h}} find the line
:: <code>#define HZ 1000</code>
: and change the value of HZ to 100:
:: <code>#define HZ 100</code>
:Then recompile the kernel.<br />After i changed it on my ThinkPad {{A30}} (under SuSE 9.2 and 9.3) and recompiling the kernel the high pitch noise is gone away.

* Omar Yasin: Worked on my {{R52}}, thanks.

* [[User:Thinker|Thinker]]: In modern kernels this constant is in the kernel configuration {{kernelconf|CONFIG_HZ|Processor type and features||Timer Frequency|||||}}.

===Prevent idling===

Indirectly avoid power saving states by making sure the CPU is rarely idle:

* Paul RIVIER: Here is a really simple workaround. C3 / C4 states are mainly called when the cpu freq is higher than required, for example if your cpufreqd is lazy to slow down the frequency but quick to raise it. That is why I use powernowd with the builtin "passive" mode, which is lazy for raising frequency, but quick to go back to the lowest. Now I don't hear them as often as before, as I avoid C3/C4 states at high frequency.

* The problem also occurs on my {{X41}} with 2.6.11. Setting up [[How to make use of Dynamic Frequency Scaling|frequency scaling]] with the <code>ondemand</code> governor makes things a lot better, as the processor does not stay with the maximum frequency when in idle mode. It can be still heard sometimes, though.

* On a {{T43}} the noise was gone after dropping cpufreqd and switching to the ondemand governor - maybe because of the high sampling rate? (used the default: 10ms)

===Change the processor voltage===

Reducing the processor voltage (when possible) may decrease or eliminate the noise. On one ThinkPad {{T43}}, [[Pentium M undervolting and underclocking|undervolting the Pentium M processor]] eliminated the high-pitched noise. Compared to the other solutions this has the benefit of lower power consumption, both due to the undervolting itself and because there is no need to forbid high APCI CPU power saving modes.

==Other solutions==

===Disable UltraBay===
*Naheed Vora: My {{T41}} (2373-268) started to give high pitch noise ocassionally, when I upgraded to 2.6.11 kernel. I tried to unload lot of modules but finally figured out that disabling bay stops the noise. If you have [[ibm-acpi]], do (need a cleaner solution): {{cmduser|echo eject >/proc/acpi/ibm/bay}} .

===Disable IrDA===
*Mike Perry: I was able to cure an intermittent high-pitched whine on both my {{X24}} and {{X40}} by disabling the Infrared port.

===Disable the Linuxant Modem Driver===
*Joern Heissler: I made another experience. I played around with linuxant conexant [[Modem Devices|modem]] drivers. After loading them I got some noise on my {{T42p}}.

===Media Player paused===
*Eilif Muller: On my {{R52}} the high-pitched noises go away if I load XMMS, play something then pause it.
*Jacob: On my {{T43}} DGU it goes away if I open mplayerc.exe and press play then pause it. This is the high-pitched noise that only shows up when I'm on battery.

''I'd guess that the above tip works as when xmms or similar is running, it is uncompressing compressed audio/video, which is a processor intensive action. Keeping this paused means that the app won't 'let go' of the processor, forcing it to stay up and running, which stops it entering the higher powersave modes.''

===Upgrade BIOS===
On a ThinkPad [[X60s]], [[BIOS_Upgrade|upgrading the BIOS]] to version 1.06 eliminated the high pitch noise when running on battery.

Problem with high pitch noises

2006-08-19T18:45:49Z

Ischg: /* Affected Models */

Information on strange high pitch, low volume noises emitted by ThinkPads.

==Problem description==
Even though ThinkPads are known as very silent notebooks, they tend to emit different, mostly high pitch noises in certain circumstances. The noises are of low volume and hence not realized by everyone or at least tolerated by most people. However, there are those with "bat like ears" that hear them and might be annoyed by that.

==Affected Models==
Noises have been experienced in the following situations:
{| border="1" cellspacing="0" cellpadding="2"
|-
! style="vertical-align:top;background-color:#DDDDDD;" | situation
! style="vertical-align:top;background-color:#DDDDDD;" | noise description
! style="vertical-align:top;background-color:#DDDDDD;" | affected models
|-
| style="vertical-align:top;" |
Plugged into AC / running at high CPU frequency
| style="vertical-align:top;" |
soft crackling, buzzing noise
| style="vertical-align:top;" |
*{{T41}}
**2379-DJU
|-
| style="vertical-align:top;" |
ThinkPad suspended to RAM
| style="vertical-align:top;" |
constant high pitch noise
| style="vertical-align:top;" |
*{{T42p}}
|-
| style="vertical-align:top;" |
ThinkPad connected to power and switched off, with battery fully charged
| style="vertical-align:top;" |
constant high pitch noise
| style="vertical-align:top;" |
*{{T41p}}
**2373-GHG
|-
| style="vertical-align:top;" |
moving windows or just the mouse in xorg
| style="vertical-align:top;" |
strange noise like a rapid series of very short high pitch noises adding to a constant kind of whistling (only as long as the movement goes)
| style="vertical-align:top;" |
*{{T41p}}
**2373-GHG
|-
| style="vertical-align:top;" |
Thinkpad connected to power or working on battery, also when suspended to RAM
| style="vertical-align:top;" |
High pitch noise also when HD is powered down.
| style="vertical-align:top;" |
*{{T23}}
**2647-DG4
*{{X24}}
**2662-MWG
|-
| style="vertical-align:top;" |
Thinkpad connected to power battery charged less than 60%
| style="vertical-align:top;" |
High pitch noise till battery is charged more than 60%.
| style="vertical-align:top;" |
*{{T41p}}
**2373-GEG
|-
| style="vertical-align:top;" |
Constantly, if AC connected
| style="vertical-align:top;" |
High pitched, low volume constant noise.
| style="vertical-align:top;" |
*{{T40}}
**2373-88U
|-
| style="vertical-align:top;" |
When the CPU freq jumps up to 1Ghz or above, or when the laptop is in suspend mode
| style="vertical-align:top;" |
Constant high pitched
| style="vertical-align:top;" |
*{{R50}}
**1829-6DM
|-
| style="vertical-align:top;" |
(May come from harddisk.)
| style="vertical-align:top;" |
continuous, intermittent, low volume, high pitched
| style="vertical-align:top;" |
*{{600X}}
|-
| style="vertical-align:top;" |
ACPI puts the processor into the C3 or C4 power saving states (i.e., the system is idle).
| style="vertical-align:top;" |
High-pitched crackling noise.
| style="vertical-align:top;" |
*{{X41}}
*{{T43}}
**2686-DGU
*{{T43p}}
*{{T21}}
|-
| style="vertical-align:top;" |
Cpufreqd (or powernowd etc.) slows down the processor, for exemple at the end of an heavy task.
| style="vertical-align:top;" |
High-pitched crackling noise.
| style="vertical-align:top;" |
*{{T42}}
|-
| style="vertical-align:top;" |
When on battery
| style="vertical-align:top;" |
Almost inaudible screeching sound, or sometimes beeping (when wifi is on)
| style="vertical-align:top;" |
*{{R52}}
**1858-A11
*{{T43}}
**2686-DGU
*{{T60}}
**2007-72U
*{{x60}}
*{{x31}}
**2673-CBU

|-
| CPU is used much AND laptop is on AC power AND the TFT panel is enabled.
| Screetching high pitch noise, like a million crickets
|
* {{X41}}

|-
| Network is pluged in and networkload is ~100%.
| low volume highfreq. pitch noise from left speaker or cpu.
|
*{{Z60}}
|}

==Affected Operating Systems==
All, though Linux appears especially susceptible.

==Possible sources==

* '''CPU activity:''' On some models the noise is triggered by certain CPU power states or activity patterns (as proven [http://www.wisdom.weizmann.ac.il/~tromer/acoustic here]).
* '''Graphics processor:''' In some models from the T2x era, e.g. the {{T23}}, the problem was related to the graphics circuitry and occured especially or only while making use of DirectDraw functions. IBM was able to fix it through a BIOS upgrade.
* '''Hard disk:''' On some ThinkPads the processor and hard disk are adjacent and produce similar noise. For example, in the {{X41}} the sound generated by the hard disk is likely to be loudest at the vent.

==Status==

The problem is highly specific to operating system, model and even individual machines. There is no universal solution, but on most machines one of the following will reduce or eliminate the noise (possibly at some cost in power consumption).

==Solutions for CPU-triggered noise==

===Limit ACPI CPU power states===

There are four ACPI CPU power states, called C1 through C4. Often only the extreme power saving modes C4 or C3 produce the noise, so the noise can be stopped by insructing the Linux ACPI code to use only lower modes.

To forbid the ACPI driver from using C4 (this fixed the problem with on some ThinkPad {{T43}}, {{T43p}} and {{T41}}):
* If the ACPI processor component is compiled as built-in (<tt>CONFIG_ACPI_PROCESSOR=y</tt>):
**Pass the {{bootparm|max_cstate|3}} kernel argument.
* If the ACPI processor component is loaded as a module (<tt>CONFIG_ACPI_PROCESSOR=m</tt> and <tt>processor</tt> shows in the output of {{cmdroot|lsmod}}), do either of:
** Pass the {{bootparm|processor.max_cstate|3}} kernel argument (this does not work in Ubuntu 5.10 with default kernel).
** Add <code>options processor max_cstate=3</code> to {{path|/etc/modprobe.conf}} (or {{path|/etc/modprobe.conf.local}}, or {{path|/etc/modprobe.d/...}}, depending on your system) (this does not work in Ubuntu 5.10 with default kernel).
** {{cmdroot|echo 3 > /sys/module/processor/parameters/max_cstate}} (this can be changed in runtime for experimentation). (If may need to be set again upon resume from suspend, e.g., in the wakeup script.)
** (On Ubuntu 5.10, the default kernel uses <code>processor</code> as a module. Unfortunately, the script loading it, {{path|/etc/init.d/acpid}}, ignores the <code>options processor max_cstate=3</code> setting in {{path|/etc/modprobe.d/<my file>}}. As a solution for this specific problem, add the line <code>echo 2 > /sys/module/processor/parameters/max_cstate</code> directly to {{path|/etc/init.d/acpid}}, at the end of the function <code>load_modules()</code>, immediately after the line <code>echo "$PRINTK" > /proc/sys/kernel/printk</code>.)

To also forbid the C3 state, replace "<tt>3</tt>" with "<tt>2</tt>" above (this fixed the problem on some ThinkPad {{X40}}, {{X41}}, and {{R52}}):

Note that these options affect power consumption when the CPU is idle. For example, here are the power consumption figures on a ThinkPad {{T43}}:
* {{bootparm|processor.max_cstate|4}}: 15160mW (default, noisy)
* {{bootparm|processor.max_cstate|3}}: 15770mW (660mW higher, silent)
* {{bootparm|processor.max_cstate|2}}: 16100mW (2940mW higher, silent)

See the [http://thinkwiki.org/wiki?title=Talk:Problem_with_high_pitch_noises discussion page] for further information and success reports.

*Jakob Schou Pedersen: Editing the file {{path|/etc/init.d/acpid}} as described above (the last solution) worked on my T43 :-)

===Turn off CPU power saving in in BIOS===

Go into the BIOS and turn off the power saving processor feature that puts it into idle mode. (This worked on a ThinkPad {{T43}}, {{T21}} and {{X60s}}.)

===Disable ACPI CPU power states===

Completely disable CPU ACPI power states. Discussion:

*From Martin Steigerwald: I made the observation that I get at least less high pitch noises on my {{T23}} when I do not use the two ACPI modules "processor" and "thermal" (depends on the first one). I have no clue, why. Anyone with similar experiences?
:Omar Yasin: I've got a {{R52}} and when I load the same ACPIO modules the high pitch noises are not as loud but I can still hear them.
*Niko Ehrenfeuchter: I'm experiencing the same here on my {{X24}}. Removing the "processor" module also stops the pitch noise, which does ONLY occur when setting the CPU to maximum speed (using cpufreq). On low speed it's completely silent, even having loaded the processor module.

*Rolf Adelsberger: I can confirm this: the high pitch noise is only remarkable (at least with my ears ;-) ) if the processor speed is set to maximum frequency.

*Stefan Baums: My {{X41}} produced a high-pitched crackle from the processor vent on the left. Changing HZ did nothing, and the 'processor' module could not easily be removed from the system (Ubuntu 5.04). What solved the problem for me was adding {{bootparm|idle|halt}} to the boot command line. Unfortunately, this solution only lasts until the first hibernation or suspend - when the computer ({{X41}}) resumes, the high-pitched crackle is back.

* The {{bootparm|idle|halt}} solution combined with setting <code>#define HZ 100</code> in the kernel fixes the problem on a {{T43}}.

* jhatch: {{bootparm|idle|halt}} plus <code>#define HZ 100</code> also worked on my {{T43}}. It still reverts back to noisy after a suspend/resume though. This needs to be fixed...

===Change the timer interrupt frequency===

Change the "HZ" kernel constants to alter the frequency of timer interrupts. Discussion:

{{NOTE|The timer interrupt frequency (HZ) in current Linux kernels is directly tied to the kernel task scheduler. Lower frequencies provide larger time-slices and thus also higher latencies (which may kill latency-sensitive applications like audio processing). 100Hz ended up as the recommended "server" setting (because it increases disk/CPU throughput in a latency-insensitive environment). Higher frequencies are better for latency-sensitive applications, and improve desktop responsivity at the cost of less processor throughput. 1000Hz ended up as the recommended "desktop" setting.}}

*Andreas Karnahl: i've read in several forums it has something to do with the "idle"-state (or "C3") of the processor. There is a frequency called "timer interrupt" (or so mething like that). Since kernel 2.6x it is set to 1000 Hz by default (compared to 100 Hz in Kernel 2.4x). The exact reason i don't know, but it is safe to change this frequency to 100 Hz in kernel 2.6x (by the way, windows up to XP uses 100 Hz by default).<br />Just do the following:<br />
: In {{path|[path to kernel-sources]/include/asm-i386/param.h}} find the line
:: <code>#define HZ 1000</code>
: and change the value of HZ to 100:
:: <code>#define HZ 100</code>
:Then recompile the kernel.<br />After i changed it on my ThinkPad {{A30}} (under SuSE 9.2 and 9.3) and recompiling the kernel the high pitch noise is gone away.

* Omar Yasin: Worked on my {{R52}}, thanks.

* [[User:Thinker|Thinker]]: In modern kernels this constant is in the kernel configuration {{kernelconf|CONFIG_HZ|Processor type and features||Timer Frequency|||||}}.

===Prevent idling===

Indirectly avoid power saving states by making sure the CPU is rarely idle:

* Paul RIVIER: Here is a really simple workaround. C3 / C4 states are mainly called when the cpu freq is higher than required, for example if your cpufreqd is lazy to slow down the frequency but quick to raise it. That is why I use powernowd with the builtin "passive" mode, which is lazy for raising frequency, but quick to go back to the lowest. Now I don't hear them as often as before, as I avoid C3/C4 states at high frequency.

* The problem also occurs on my {{X41}} with 2.6.11. Setting up [[How to make use of Dynamic Frequency Scaling|frequency scaling]] with the <code>ondemand</code> governor makes things a lot better, as the processor does not stay with the maximum frequency when in idle mode. It can be still heard sometimes, though.

* On a {{T43}} the noise was gone after dropping cpufreqd and switching to the ondemand governor - maybe because of the high sampling rate? (used the default: 10ms)

===Change the processor voltage===

Reducing the processor voltage (when possible) may decrease or eliminate the noise. On one ThinkPad {{T43}}, [[Pentium M undervolting and underclocking|undervolting the Pentium M processor]] eliminated the high-pitched noise. Compared to the other solutions this has the benefit of lower power consumption, both due to the undervolting itself and because there is no need to forbid high APCI CPU power saving modes.

==Other solutions==

===Disable UltraBay===
*Naheed Vora: My {{T41}} (2373-268) started to give high pitch noise ocassionally, when I upgraded to 2.6.11 kernel. I tried to unload lot of modules but finally figured out that disabling bay stops the noise. If you have [[ibm-acpi]], do (need a cleaner solution): {{cmduser|echo eject >/proc/acpi/ibm/bay}} .

===Disable IrDA===
*Mike Perry: I was able to cure an intermittent high-pitched whine on both my {{X24}} and {{X40}} by disabling the Infrared port.

===Disable the Linuxant Modem Driver===
*Joern Heissler: I made another experience. I played around with linuxant conexant [[Modem Devices|modem]] drivers. After loading them I got some noise on my {{T42p}}.

===Media Player paused===
*Eilif Muller: On my {{R52}} the high-pitched noises go away if I load XMMS, play something then pause it.
*Jacob: On my {{T43}} DGU it goes away if I open mplayerc.exe and press play then pause it. This is the high-pitched noise that only shows up when I'm on battery.

''I'd guess that the above tip works as when xmms or similar is running, it is uncompressing compressed audio/video, which is a processor intensive action. Keeping this paused means that the app won't 'let go' of the processor, forcing it to stay up and running, which stops it entering the higher powersave modes.''

===Upgrade BIOS===
On a ThinkPad [[X60s]], [[BIOS_Upgrade|upgrading the BIOS]] to version 1.06 eliminated the high pitch noise when running on battery.