ThinkWiki - User contributions [en]

How to enable the integrated fingerprint reader with ThinkFinger

2009-05-06T20:09:47Z

Dirk: /* Configuring PAM to use ThinkFinger */

[[How to enable the fingerprint reader]] has a good explanation for using the fingerprint reader with the closed-source binary driver. But there is also an opensource project called [http://thinkfinger.sourceforge.net ThinkFinger] which does the same, but open.

However: The fingerprint reader is an INSECURE device and gives a false sense of security! There has been quite a bit of research by a hacker named Starbug, a member of the Chaos Computer Club, Berlin, Germany. He outlined in two very good talks how to forge each and every available fingerprint sensor available at the cost of a few euros, using materials from your local hardware store, a digicam and a laser printer! Here's some links:
* [http://www.ccc.de/updates/2007/umsonst-im-supermarkt?language=en Fingerprint recognition in supermarkets]
* [ftp://ftp.ccc.de/pub/documentation/Fingerabdruck_Hack/fingerabdruck.mpg Video tutorial for forging fingerprints]

== Installing ==
=== From source ===

Download thinkfinger-0.3.tar.gz from the [http://thinkfinger.sourceforge.net/ homepage] and unpack it somewhere, make sure you have the gcc compiler, libtool, pkg-config, libusb-dev and libpam0g-dev installed, then:

{{cmduser|cd thinkfinger-0.3}}

<code style="white-space:nowrap;color:#495988;background-color:white;"><nowiki>$</nowiki> ./configure --prefix=/usr --sysconfdir=/etc --with-securedir=/lib/security --with-birdir=/etc/pam_thinkfinger</code>

{{cmduser|make}}

{{cmdroot|make install}}

{{NOTE|/lib/security is the directory, where PAM assumes its modules on Debian and openSUSE, it may vary for your distro!}}

"make install" doesn't create the birdir we specified (where thinkfinger will store users' biometric info), so create it:

{{cmdroot|mkdir /etc/pam_thinkfinger}}

If everything went OK assert that you find pam_thinkfinger.so in /lib/security typing:

{{cmduser|ls /lib/security}}

=== From package ===

==== Debian ====
[http://packages.debian.org/source/experimental/thinkfinger Packages] arrived in Debian experimental on Aug 2nd, 2007 (cf. [http://bugs.debian.org/409563 bug #409563]). To access the experimental packages via apt, add the following lines to your sources.list:
<pre>
# experimental
deb ftp://mirrors.kernel.org/debian/ experimental main contrib non-free
deb-src ftp://mirrors.kernel.org/debian/ experimental main contrib non-free
</pre>
where of course you may replace mirrors.kernel.org with your mirror of choice. Just make sure that it hosts the experimental repositories.

{{cmdroot|aptitude update}}

{{cmdroot|aptitude install libthinkfinger0 libpam-thinkfinger thinkfinger-tools}}

should then get you up and running.

To make everything work you'll have to have permission to work the device ({{cmduser|sudo adduser myself plugdev}} worked for me), and you'll also have to follow instructions below about adding the device to your PAM methods.

==== Ubuntu ====

===== Gutsy =====

From https://wiki.ubuntu.com/ThinkFinger

Add PPA repositories to your sources.list:
<pre>
deb http://ppa.launchpad.net/jldugger/ubuntu gutsy main restricted universe multiverse
deb-src http://ppa.launchpad.net/jldugger/ubuntu gutsy main restricted universe multiverse
</pre>

Install necessary packages:

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

===== Hardy =====

Hardy includes the latest thinkfinger and it is up to date with subversion. Install packages:

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

Update the pam configuration files:

{{cmduser|sudo /usr/lib/pam-thinkfinger/pam-thinkfinger-enable}}

Enroll your fingerprint (creates $HOME/.thinkfinger.bir). If this gives an error about claiming the USB device then a reboot was claimed to work, but in fact it may just be a permissions problem. {{NOTE|Do not try to enroll using 'sudo' - it will cause hidden permission problems}}

{{cmduser|tf-tool --acquire}}

Check fingerprint enrollment

{{cmduser|tf-tool --verify}}

You can expect everything to work correctly. Note that you still have to enter your username if prompted but will be able
to swipe your finger instead of the password. The prompt will usually be "Password or swipe finger"

* Graphical login
* Text console login
* sudo
* screen lock/screen saver
* Administrative password prompt (eg for update or package managers). (Note no "or swipe finger" in prompt).

===== Intrepid =====
After installing from the normal repositories coming with Ubuntu 8.10, you would have to press enter after sweeping finger. (This bug: [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429])
Therefore Jon Oberheide made an update that can be found here:
[https://launchpad.net/~jon-oberheide/+archive https://launchpad.net/~jon-oberheide/+archive]
(As of 2/3/09, this no longer seems to be the case. Just proceed to the install step.)

Add the PPA repositories to your source.list (/etc/apt/source.list):
<pre>
deb http://ppa.launchpad.net/jon-oberheide/ubuntu intrepid main
deb-src http://ppa.launchpad.net/jon-oberheide/ubuntu intrepid main
</pre>

Update installer:

{{cmduser|sudo apt-get update}}

And install:

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

===== Jaunty =====

The same package by Jon Oberheide is necessary, as with Intrepid, though the package thinkfinger-tools is installed by default.

Add key:

{{cmduser|sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com F2A12FABE936A7BBDC4EA33351DB180D1323E149}}

Add the PPA repositories to your source.list (/etc/apt/source.list):

<pre>
deb http://ppa.launchpad.net/jon-oberheide/ppa/ubuntu jaunty main
deb-src http://ppa.launchpad.net/jon-oberheide/ppa/ubuntu jaunty main
</pre>

Update installer:

{{cmduser|sudo apt-get update}}

And install:

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

==== Fedora/Fedora Core ====
{{cmdroot|yum install thinkfinger}}

==== Gentoo ====
{{cmdroot|emerge sys-auth/thinkfinger}}

==== OpenSUSE ====
openSUSE 10.2 includes the package "libthinkfinger" (version 0.1-7) - you will find newer packages [http://beta1.suse.com/private/thoenig/10.2/thinkfinger/ here].

== Testing the driver ==

Now the driver is installed and should be working. You can try it (as root) with

{{cmdroot|tf-tool --acquire}}

and

{{cmdroot|tf-tool --verify}}

This will ask you to swipe your finger three times, save the fingerprint to /tmp/test.bir and then verify your fingerprint with the bir-file.

== Configuring PAM to use ThinkFinger ==
Now you can configure PAM to use ThinkFinger:

Open {{path|/etc/pam.d/common-auth}} (In FC6, F7, and Gentoo, this file is {{path|/etc/pam.d/system-auth}}):

{{cmdroot|nano -w /etc/pam.d/common-auth}}

Add this line before any pam_unix or pam_unix2 directives:
auth sufficient pam_thinkfinger.so

If your PAM uses the pam_unix and not the pam_unix2 module, you need to pass a specific argument in
the /etc/pam.d/common-auth directive to make it consider the password entered at the pam_thinkfinger prompt.
auth required pam_unix.so try_first_pass

For instance, {{path|/etc/pam.d/common-auth}} looks like this:
auth sufficient pam_thinkfinger.so
auth required pam_unix.so nullok_secure try_first_pass

On openSUSE 10.2, it looks like this now:
auth required pam_env.so
auth sufficient pam_thinkfinger.so
auth required pam_unix2.so

On Ubuntu 8.10 - Intrepid Ibex you should just add the following line the the /etc/pam.d/common-auth file so it looks like this:
<pre>
....
# here are the per-package modules (the "Primary" block)
auth sufficient pam_thinkfinger.so
auth [success=1 default=ignore] pam_unix.so try_first_pass nullok_secure
# here's the fallback if no module succeeds
....
</pre>

On Ubuntu 9.04, you don't need to edit manually, just type:

{{cmdroot|sudo /usr/lib/pam-thinkfinger/pam-thinkfinger-enable}}

Now we are ready to add users to thinkfinger. You can add a fingerprint for a user with:

{{cmdroot|tf-tool --acquire $USERNAME}}

{{NOTE|This may not work for you. Please read the Intrepid Ibex point in the discussion to this page.}}

Now the user should be able to login with his finger instead of the password.

If you would like to use thinkfinger for su, you have to enroll the fingerprint for root user with:

{{cmdroot|tf-tool --acquire root}}

{{NOTE|You should see the "Password or swipe finger:" prompt when trying to sudo or su. If you don't, you probably do not have the "User level driver support" compiled into your kernel or the "uinput" module loaded!}}

== xscreensaver/gnome-screensaver ==
{{NOTE|In Fedora 7, the package has been modified in such a way as to make doing this unnecessary.}}

If you'd like to be able to unlock your screen using the fingerprint reader, you must have current versions of xscreesaver (>~5.03) or gnome-screensaver (>~2.18.2). Then you must give yourself access to the fingerprint reader and your bir-file, because unlike login/gdm/su/sudo, both gnome-screensaver and xscreensaver do not run as root. The following procedure will make the fingerprint reader accessible to members of the "fingerprint" group.

Make the group: {{cmdroot|groupadd fingerprint}}

Save the following as {{path|/etc/udev/rules.d/60-thinkfinger.rules}} and run {{cmdroot|sudo /sbin/udevtrigger}}. If you are using a Debian-based distribution, it is likely you are affected by the following [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=489831 bug] where you need to replace {{path|udevtrigger}} with {{path|udevadm trigger}} (with the space!) in order for the following to work. You may need to reboot for this to take effect.
#
# udev rules file for the thinkfinger fingerprint scanner
#
# gives access to the fingerprint reader to those in the "fingerprint" group
#
# Taken from:
# http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
# which was taken and modified from:
# http://article.gmane.org/gmane.linux.drivers.thinkfinger/329
#

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

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

Finally, edit {{path|/etc/pam.d/gnome-screensaver}} so that it looks like this:
auth sufficient pam_thinkfinger.so
auth required pam_unix.so try_first_pass nullok_secure

Per user:

# Add him to the group: {{cmdroot|gpasswd -a $USERNAME fingerprint}}
{{NOTE|The following steps do not need to be done in Ubuntu Intrepid as the bir files are handled differently.}}
# Make him owner of his bir-file: {{cmdroot|chown $USERNAME:root /etc/pam_thinkfinger/$USERNAME.bir}}
# Give him read-only access to his bir-file: {{cmdroot|chmod 400 /etc/pam_thinkfinger/$USERNAME.bir}}
# Give "execute only" access to everyone for the /etc/pam_thinkfinger/ directory: {{cmdroot|chmod o+x /etc/pam_thinkfinger}} (WARNING: this opens up security a little).

== GNOME ==

{{NOTE|1=This problem should be solved if you're using sudo >= 1.6.9p9. Links: [http://savannah.nongnu.org/bugs/?19132], [http://www.sudo.ws/bugs/show_bug.cgi?id=180], [https://bugs.launchpad.net/ubuntu/+source/gksu/+bug/86843]}}

gksu/gksudo doesn't work correctly. It just stays invisible. When starting a su privileged application such as synaptics you will not get prompted for the password. Nevertheless you can swipe your finger and it should authenticate you. Starting synaptics twice makes gksudo visible.

There are two possibilities to solve it:
* Changing the string "Password or swipe finger:" to a plain "Password:" (like sudo normally would do) in the file pam/pam_thinkfinger.c of the thinkfinger source directory. Of course, in the console you will then only see a "Password:" instead of "Password or swipe finger:" but this is still more usefull than having gksu/gksudo crashing everytime.
* Patching libgksu with the following patch. This is also a nasty hack until a better solution is implemented.
<pre>
--- libgksu-2.0.3/libgksu/libgksu.c.orig 2007-06-17 16:00:24.000000000 +0200
+++ libgksu-2.0.3/libgksu/libgksu.c 2007-06-17 16:00:47.000000000 +0200
@@ -2663,7 +2663,7 @@
*/
for (counter = 0; counter < 50; counter++)
{
- if (strncmp (buffer, "GNOME_SUDO_PASS", 15) == 0)
+ if (strncmp (buffer, "GNOME_SUDO_PASS", 15) == 0 || strncmp (buffer, "Password or swi", 15) == 0)
break;

read_line (parent_pipe[0], buffer, 256);
@@ -2675,7 +2675,7 @@
if (context->debug)
fprintf (stderr, "brute force GNOME_SUDO_PASS ended...\n");

- if (strncmp(buffer, "GNOME_SUDO_PASS", 15) == 0)
+ if (strncmp(buffer, "GNOME_SUDO_PASS", 15) == 0 || strncmp(buffer, "Password or swi", 15) == 0)
{
gchar *password = NULL;
gboolean prompt_grab;
</pre>

== KDE ==

Integration in KDE and kdm seems not to be easily possible now. There is a filed [https://bugs.kde.org/show_bug.cgi?id=116682 bug] at kde.org where you can vote for this.

Moreover, kdm in openSUSE 10.3 and in Kubuntu 8.10 crashes when pam_thinkfinger is enabled. A possible "workaround" is downgrading to thinkfinger 0.2.2.

Another workaround is to use Fprint from [http://www.reactivated.net/fprint/wiki/Main_Page] which works quite nicely on my X61s and Kubuntu Hardy.

This Howto was copied from [[Installing Ubuntu 6.06 on a ThinkPad T43#Fingerprint_Reader]] and then slightly modified.

== Fix for the fingerprint reader getting too hot ==

If you notice that your fingerprint reader occasionally gets very hot then you might be interested in this section. Thanks to Tino Keitel, he actually gave me this solution through the linux-thinkpad mailing list.

First we need to determine if the reader is not on autosuspend mode.
Open a terminal and run:

for i in `find /sys/devices/*/*/usb* -name level` ; do echo -n "$i: " ; cat $i ; done

We care about the devices that are with "on" state and we need to determine if one of those is the reader. So for each of those run something like:

cat /sys/devices/pci0000\:00/0000\:00\:1a.0/usb1/1-2/idVendor
0483

cat /sys/devices/pci0000\:00/0000\:00\:1a.0/usb1/1-2/idProduct
2016

Use the corresponding path of the devices that you got with "on" state and then compare the output with the output of the lsusb command. An example:

lsusb output: Bus 001 Device 004: ID 0483:2016 SGS Thomson Microelectronics Fingerprint Reader

Which matches the output above (0483:2016). Once you have determined the path of your reader then become root with su - and:

echo "auto" > /sys/<path-to-device>/power/level

After this, the fingerprint reader should be in "autosuspend" and will not get hot anymore. And it will still work as normal.

This will only work for the current session. If you want to make this change persistent and have [http://linux-diag.sourceforge.net/Sysfsutils.html sysfsutils] installed, edit the file {{path|/etc/sysfs.conf}} and add the line

<path-to-device>/power/level = auto

Following the above example, that would be

devices/pci0000\:00/0000\:00\:1a.0/usb1/1-2/power/level = auto

Alternatively, you can install an init script:

sudo gedit /etc/init.d/ReaderNoMoreHot

Paste the following into it:

#!/bin/bash
#
echo "auto" > /sys/<path-to-device>/power/level

Save and close. Then:

sudo chmod 755 /etc/init.d/ReaderNoMoreHot
sudo update-rc.d ReaderNoMoreHot defaults 90

--[[User:Lunatico|Lunatico]] 19:19, 1 August 2008 (CEST), extended by --[[User:Michaelthomas h|Michaelthomas h]] 23:36, 9 August 2008 (CEST)

For the init script above, you can use the following more elaborate script, which does all the work for you of identifying the <path-to-device>. This can be useful since the USB device id can change under various circumstances (kernel upgrade etc).

#!/bin/bash

# Set to the proper device name for you as shown in lsusb output
usbname="SGS Thomson Microelectronics Fingerprint Reader"

usbid=`lsusb |grep "$usbname" |cut -d' ' -f6`
[ "d$usbid" = "d" ] && echo USB Device $usbname not found && exit 1
#echo $usbid

for i in `find /sys/devices/*/*/usb* -name idVendor` ; do
dir=`dirname $i`
ven=`cat $i`
prod=`cat $dir/idProduct`
[ "$ven:$prod" = "$usbid" ] && devdir=$dir && break
done
[ "d$devdir" = "d" ] && echo sys dir not found for $usbid && exit 1
#echo $devdir

devpw=$devdir/power/level

echo Current power level: `cat $devpw`
echo "auto" > $devpw || ( echo Failed to set powerlevel. You need to run as root. && exit 1 )
echo New power level: `cat $devpw`

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-10-10T08:48:18Z

Dirk:

== My Thinkpad ==
<pre>
Lenovo Thinkpad R60 9461 HRG
Intel Core2Duo (Merom) 1.83 CPU
120 GB SATA Hitachi HTS54161 Harddisk
2 GB RAM
ATI Mobility X1400
</pre>

Originally equipped with a preinstalled MS Windows Vista Business. So the Harddisk was parted into two Partitions.

1. The Rescue & Recovery Partition

2. The preinstalled Windows Vista Partition

And as the parcel with my new Thinkpad arrived I was surprized, that there was a Windows Vista DVD (only 32 Bit Version) with it.
So I tried Vista - but I was a little bit shocked by it's performance. I never thought that a new computer could take so much time to boot up completely.

I decided to do a clean install of Vista, but I want to have Windows XP and Ubuntu Feisty on the Harddisk too.

== New Installation ==

I wanted to use all Space of the Harddisk, so I decided to kill the Rescue & and Recovery Partition, but to have the chance to go back to the factory default state I ordered Recovery DVD's at the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4HWSE3#Lenovo Support Call Center for Germany].
They shipped the 3 DVD's to me - free of charge - but I think it's only free if your Thinkpad is still in the warranty. I don't know exactly.

Then I created 2 Partitions on my Harddisk, 64 GB for Vista, 20 GB for XP, so 29 GB left free for Linux.

I installed Vista and XP and all the Thinkpad Stuff for each system.

When this was finished I took a Ubuntu Feisty Fawn installation CD and boot my Notebook with it. I created a 4 GB linux-swap partition and a 25 GB root / partition.

Because I want to boot my Ubuntu with the Windows Vista Boot Loader, I decided to install Grub to /dev/sda4 which is my Linux root partition.

The installation of Ubuntu Feisty Fawn works fine, NO PROBLEMS.

NOW I want to boot Linux from the Vista Bootloader, because I don't want to wait for two Bootscreens, and I wan't to have the chance to access the Repair Console of Windows Vista.

First I have to copy the Bootsector of my Linux Partition with:

<pre>
sudo dd if=/dev/sda4 of=/tmp/bootsect.lin bs=512 count=1
</pre>

Copy the bootsect.lin file to a USB-Stick or a writable partition which you can access from Windows Vista.

Now boot Windows Vista and copy the file bootsect.lin to your Systemdrive. In an Command Window with Administrator privileges type:

<pre>
copy bootsect.lin %SYSTEMDRIVE%\

bcdedit /create /d “Ubuntu” /application BOOTSECTOR
</pre>

You will receice an ID like this {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} from bcdedit. This is a uniqe identifier for your new Boot Entry in the Vista Bootloader. Now you will have to manipulate the entry with the following commands:

<pre>
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} device boot
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} PATH \bootsect.lin
bcdedit /displayorder {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} /addlast
bcdedit /timeout 10
</pre>

Then I booted my Ubuntu an did :

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

In this file I canged the entry the following entries:

<pre>
timeout 2
hiddenmenu
</pre>

So the computer starts up with the Windows Vista bootloader and gives me the option to start Windows XP, Windows Vista, Ubuntu and I have the option to do the repair tasks with the {{key|F8}} button on Vista if something fails. If I choose to boot Ubuntu I have the option to press the {{key|ESC}} key within the two seconds delay of the hidden Grub Menu. I.E. to boot another Linux Kernel.

== The tp_smapi modules ==

I did it under Feisty and, after the Upgrade under Gutsy, like described here : [http://www.thinkwiki.org/wiki/Tp_smapi#Installation TP SMAPI] in the Section "Installation on Ubuntu/Debian"
It worked, hdaps-gl and hdaps-pivot shows me now the movements of my Thinkpad. Like you can see here:

[[Image:Hdaps-pivot.png]]

[[Image:Hdaps-gl.png]]

== The Upgrade to Gutsy Gibbon ==

NO PROBLEMS. So why should I upgrade ?

OK I really wanted to get hdapsd (Harddisk Active Protection) to work. I tried a lot of things with Feisty, but I didn't get it going. And after a lot of seach through the Internet I found out that Gutsy Gibbon, the next Release of Ubuntu should have the Package for hdapsd on board.
SO I decided to upgrade to Gutsy - with the knowledge that it is still in Beta Stadium.

Upgrading Ubuntu is really simple, you only have to do the following steps:

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

Search all feisty entries and change them to gutsy. Save and Close the file.

Do:

{{cmduser| sudo apt-get update}}
{{cmduser| sudo apt-get upgrade}}

Go and drink a cup of Tea or Coffee. When you are back you have a message, that you should reboot your System, to get all packages active. So do it.

After the reboot I installed the hdapsd package and I tried to activate the Harddisk Protection with:

{{cmduser| sudo hdapsd -d sda -s 14 -a -v}}

But I still get the message "open(protect_file): No such file or directory". ---- The Same Message that I get in Feisty before I did the Upgrade. So I banged my head on the table and noticed that I'm not tough enough to get this thing working. Maybe someone else.

I decided to get the other things to work.

UPDATE: After some days I tried to get hdapsd to work, again !

== The hdapsd - Deamon (IBM Active Disk Protection) ==

Because I never had compiled or patched a kernel under Ubuntu I had to find out how this works ! After a lot of search in the Internet, the Ubuntu Help and at Thinkwiki.org I found the (hopefully) correct way to do it.

The best information I found was this :
[http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.04_on_a_ThinkPad_T43#Active_Protection_System_.28acceleration_monitor.29|Installing Ubuntu 7.04 on a ThinkPad T43] in section "Disk protection"

Here is what I did to get it to work:

1. Make sure that you have the required packages, with:

{{cmduser|sudo apt-get install build-essential fakeroot kernel-package libncurses5-dev wget bzip2 linux-source}}

2. Get the correct kernel patch for your running kernel from here : [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch_.28apply_using_.27patch_-p1_-l_.3C_hdaps_xx.patch.27.29| HDAPS] section "8.1.1 Kernel patch (apply using 'patch -p1 -l < hdaps_xx.patch')"

After all my experiences I was not sure that there was a patch available for my Gutsy-kernel (2.6.22-7-generic), but I still had my old kernel on the disk. So I booted up the old one (2.6.20-16-generic). Check the running kernel with:

{{cmduser|uname -r}}

You should see something like: 2.6.20-7-generic

Now change to /usr/src and look that the sources for the running kernel are there with:

{{cmduser|cd /usr/src}}
{{cmduser|ls -d linux-source*}}

You should see a file with the name "linux-source-2.6.20.tar.bz2" wich includes the packed kernel sources. You have to extract it, so do:

{{cmduser|sudo su}}
{{cmdroot|tar xvfj linux-source-2.6.20.tar.bz2}}

Now you have the kernel sources in the /usr/src/linux-source-2.6.20 directory. Take a look if there is a link from /usr/src/linux to an other kernel source directory (It's maybe there if you tried to compile a kernel some time before).

{{cmdroot|ls -l linux}}

If you see that linux is linked to an other source than your running kernel remove the link and create a new one with:

{{cmdroot|rm linux}}
{{cmdroot|ln -s /usr/src/linux-source-2.6.20 linux}}

Change to the source directory and patch the kernel with this:

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|patch -p1 -l < /home/dirk/993-001.bin}}

The file "993-001.bin" is the kernel patch for the 2.6.20 and 2.6.21 kernels, I downloaded it here : [http://article.gmane.org/gmane.linux.drivers.hdaps.devel/993]

After the patchwork I did this :

{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --append-to-version=.hdapscustom kernel_image --initrd binary

This would take its time, so go and clean up your house ;-)
{{HELP|I think the last command (with --append-to-version was an error ! I need help from an specialist in kernel compiling. Please read ahead at the next section "The hdapsd - Deamon (next try)". }}
After your house is clean you can do :

{{cmdroot|cd /usr/src}}
{{cmdroot|ls -l linux*.deb}}

You should see some newly builded Debian Pakage files. Install them with:

{{cmdroot|dpkg -i linux-headers-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-doc-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-image-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-manual-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-source-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}

After the installation you should reboot your computer, when Grub comes up make sure that you select your newly builded kernel.
Check it with:

{{cmduser|uname -r}}

You should see this "2.6.20.3-ubuntu1.hdapscustom". But now you have the Problem, that you have to recompile the tp_smapi driver.

{{cmduser|cd tp_smapi-0.31}}
$ sudo make install HDAPS=1
{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdaps}}

After :

<pre>
$ dmesg | grep hdaps
</pre>

You should see something like this:

[ 893.752000] hdaps: initial mode latch is 0x05
[ 893.752000] hdaps: setting ec_rate=250, filter_order=2
[ 893.752000] hdaps: fake_data_mode set to 0
[ 893.756000] hdaps: device successfully initialized.
[ 893.756000] input: hdaps as /class/input/input10
[ 893.756000] hdaps: driver successfully loaded.

Now we are ready to try out the hdapsd Deamon which is included in the Gutsy repositories, if you are using Feisty you have to compile it yourself like described here: [http://www.thinkwiki.org/wiki/How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS].

{{cmdroot|sudo hdapsd -d sda -s 12 -a -v}}

Should show this:

[[Image:hdapsd.png]]

If you load it with :

{{cmdroot|sudo hdapsd -d sda -s 12 -a}}

You get nothing until you move your Thinkpad, then you see:

Fri Jul 13 12:30:42 2007: parking
Fri Jul 13 12:30:43 2007: un-parking
Fri Jul 13 12:30:44 2007: parking
Fri Jul 13 12:30:45 2007: un-parking

Now, after I have a working hdaps-deamon I want it to be started at boot time. Because I have upgraded to Gutsy and installed the hdapsd - Package I have a script called /etc/default/hdapsd. Here I have to change some things. HINT: Remember that you still need the /etc/init.d/hdapsd file if you try this on Feisty and maybe you have to do:

{{cmduser|sudo update-rc.d hdapsd defaults}}

to create the init links for the hdapsd init script. My links was already there. My /etc/default/hdapsd script now looks like this:

<pre>
# hdapsd default file

# start hdapsd at boottime?
START="yes"

# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
DISK="sda"

# sensitivity
SENSITIVITY=12

# other options to pass to hdapsd.
# the -d $DISK, -s $SENSITIVITY, -b and -p $PIDFILE options are always passed.
OPTIONS="-a"

</pre>

Now I could use the gnome-hdaps-applet with the following comands:

{{cmduser|mkdir gnome-hdaps-applet}}
{{cmduser|cd gnome-hdaps-applet}}
{{cmduser|wget http://www.zen24593.zen.co.uk/hdaps/gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|tar -xzf gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|sudo apt-get install libpanel-applet2-dev}}
{{cmduser|gcc $(pkg-config --cflags --libs libpanelapplet-2.0) -o gnome-hdaps-applet gnome-hdaps-applet.c}}
{{cmduser|sudo cp gnome-hdaps-applet /usr/bin/}}
{{cmduser|sudo mkdir /usr/share/pixmaps/gnome-hdaps-applet/}}
{{cmduser|sudo cp *.png /usr/share/pixmaps/gnome-hdaps-applet/}}
$ sudo cp GNOME_HDAPS_StatusApplet.server /usr/lib/bonobo/servers/

Now after a restart of the Gnome Session I could find a "HDAPS Status" applet in the "Add to Panel" dialog. I added it, and when I move the Thinkpad it shows me the "Pause" [[Image:Hdaps-paused-small.png]] Symbol, otherwise it shows "Play" [[Image:Hdaps-running-small.png]].

So far so good !!! After I got this running I tried the same steps with the normal Gutsy Kernel (2.6.22-7-generic) on the same way, and it worked ! To my surprise with the same kernel patch.

The only Problem that I now have is that I cannot use restricted modules with my new kernels. Now I have to figure out how to compile restricted modules agains selfmade kernels.

{{HELP| }}

== The hdapsd - Deamon (next try) ==

I am not satisfied with the above result, because I cannot use the accelerated xorg-fglrx driver for my ATI Graphics Card and I cannot use my wireless Intel card ipw3945 driver. And the Ubuntu restricted-manager is not working. PLEASE can someone help me to compile a Ubuntu kernel in the correct way, so that I can use the whole hardware ?

I have done a - I think really ugly hack - to get the restricted-manager working :

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|cp /boot/config-2.6.20-16-generic /lib/modules/2.6.20-16-generic/.config}}
{{cmdroot|gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -16-generic".
Then I compiled the kernel again with:

{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I moved my modules with :

{{cmdroot|mv /lib/modules/2.6.20-16-generic /lib/modules/2.6.20-16-generic.orginal}}

And installed the kernel with:

{{cmdroot|dpkg -i linux-image-2.6.20-16-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers as described above.
Finally I copied the ipw3945.ucode with

{{cmdroot|cp /lib/firmware/2.6.22-7-generic/ipw3945.ucode /lib/firmware/2.6.20-16-generic/ipw3945.ucode}}

My wireless-card is working now !
My ATI Card cannot be configured with restricted-manager!

{{HELP|Please can someone who is conform in compiling Ubuntu kernels and restricted modules help me to do it in the correct way ! And can someone recheck the things described above, because I am not sure about all things that I have written here.
}}

After some days Ubuntu updated the kernel to version 2.6.22-9-generic, so I need to do the steps described above again, with "EXTRAVERSION = -9-generic". But now my wireless card and my grapics card did not work. The restricted-manager crashes when I start it.
So I downloaded the packages ipw3945-1.2.1.tgz and ati-driver-installer-8.39.4-x86.x86_64.run.

== The Wireless Card ==

First I extracted and installed the Intel Pro Wireless Package:

{{cmduser|tar xzvf ipw3945-1.2.1.tgz}}
{{cmduser|cd ipw3945-1.2.1}}
{{cmduser|make}}
{{cmduser|sudo make install}}

After this I could do :

{{cmduser|sudo modprobe ipw3945}}

The module was loaded, and i was able to use my wireless card now.

== The Graphics Card ==

For my Radeon Mobility X1400 I did the following steps:

{{cmduser|sudo apt get update}}
{{cmduser|sudo apt-get install module-assistant build-essential fakeroot dh-make debhelper debconf libstdc++5}}

Created a Debian Package with:

{{cmduser|sudo bash ati-driver-installer-8.39.4-x86.x86_64.run --buildpkg Ubuntu/gutsy}}

And blacklisted the old fglrx module with:

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

I added "fglrx" to the line with "DISABLED_MODULES". Then I installed the created Debian Packages with:

{{cmduser|sudo dpkg -i xorg-driver-fglrx_8.39.4-1_i386.deb fglrx-kernel-source_8.39.4-1_i386.deb fglrx-amdcccle_8.39.4-1_i386.deb}}

Then I compiled the kernel Modules:

{{cmduser|sudo module-assistant prepare}}
{{cmduser|sudo module-assistant update}}
{{cmduser|sudo module-assistant build fglrx}}
{{cmduser|sudo module-assistant install fglrx}}
{{cmduser|sudo depmod -a}}

The helpful informations for this was found at http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide.

After this steps my wifi-card and my graphics-card was working and restricted-manager was not crashing when I tried to start it.

== After The Kernel Update (HDAPS AGAIN) ==

On 9.October 2007 Ubuntu released the Kernelpackage linux-image-2.6.22-14-generic and I installed it. So here is what I have done to get it working:

{{cmduser|sudo apt-get install linux-headers-generic}}
{{cmduser|sudo ln -s /usr/src/linux-source-2.6.22 /lib/modules/2.6.22-14-generic/source}}
{{cmduser|sudo cd /usr/src/linux}}
{{cmduser|sudo make clean}}
{{cmduser|sudo cp /boot/config-2.6.22-14-generic .config}}
{{cmduser|sudo cp /boot/config-2.6.22-14-generic /lib/modules/2.6.22-14-generic/.config}}
{{cmduser|sudo gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -14-generic".

{{cmduser|sudo gedit .config}}

In the .config file I changed the entry " # CONFIG_SND_HDA_INTEL is not set " to " CONFIG_SND_HDA_INTEL=m ". This was needed to compile the module for my sound card.

Then I compiled the kernel again with:

{{cmduser|sudo make oldconfig}}
{{cmduser|sudo fakeroot make-kpkg clean}}
$ sudo fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I copied my modules with :

{{cmduser|sudo cp -R /lib/modules/2.6.22-14-generic /lib/modules/2.6.22-14-generic.orginal}}

And installed the kernel with:

{{cmduser|sudo dpkg -r linux-headers-generic linux-headers-2.6.22-14-generic}}
{{cmduser|cd ..}}
{{cmduser|sudo dpkg -i linux-image-2.6.22-14-generic_4711_i386.deb}}

When you install the new kernel you get this messages:

[[Image:Kernel1.png]]
[[Image:Kernel2.png]]
[[Image:Kernel3.png]]

Then I rebooted the computer and recompiled the tp_smapi drivers with:

{{cmduser|cd /home/dirk/tp_smapi-0.32}}
$ sudo make install HDAPS=1

After this I load the modules with:

{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdaps}}

And test it with:

{{cmduser|hdaps-gl}}

Now I had to get my sound-card working. The module from ubuntu is not working, I don't know why. So I did this:

{{cmduser|sudo mv /lib/modules/2.6.22-14-generic/ubuntu/media/snd-hda-intel/snd-hda-intel.ko
/lib/modules/2.6.22-14-generic/ubuntu/media/snd-hda-intel/snd-hda-intel.ko.orginal}}
{{cmduser|sudo cp /usr/src/linux-source-2.6.22/sound/pci/hda/snd-hda-intel.ko
/lib/modules/2.6.22-14-generic/ubuntu/media/snd-hda-intel/snd/hda-intel.ko}}

After this I load the modules with:

{{cmduser|sudo modprobe snd-hda-intel}}

To get my graphics card accelerated again I recompiled the kernel modules for it:

{{cmduser|sudo module-assistant prepare}}
{{cmduser|sudo module-assistant update}}
{{cmduser|sudo module-assistant build fglrx}}
{{cmduser|sudo module-assistant install fglrx}}
{{cmduser|sudo depmod -a}}

After this I restarted my computer and checked the acceleration with:

{{cmduser|glxgears}}

You should get something around 3100 FPS in 5 seconds (without acceleration it is around 700 FPS per 5 seconds).

== The Browser Buttons ==

I wanted to use the Browser Forward & Backward Buttons within Firefox. After the upgrade my Firefox had version 2.0.0.4

I did :

{{cmduser| gedit ~/.Xmodmap}}

and added the following lines :

keycode 234 = F19

keycode 233 = F20

I saved and closed the file. HINT: You have to re-login to Gnome to get the .Xmodmap file active.

Then I did the things described in [http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work#Firefox How to get special keys to work].

For the Windows Key I added "keycode 115 = F13" to my .Xmodmap File, then I klicked on "System - Einstellungen - Tastenkombinationen"
sorry I don't know how it is called in English. And changed the Entry "Das Panelmenü anzeigen" to F13

== The Brightness Buttons ==

When I wanted to control the brightness, I was not able to change it with {{key|Fn}}{{key|End}}.

So I did the Workaround menitioned here [http://thinkwiki.org/wiki/Problem_with_LCD_brightness_buttons#Workaround for Fedora Core 6 Users].
After this I was able to change the brightness with {{key|Fn}}{{key|Home}} and {{key|Fn}}{{key|End}}, but I don't have the OSD anymore.

UPDATE: You don't need to do this since kernel version 2.6.22 on Ubuntu

== The Fingerprint Reader ==

Do the steps which are described in [http://www.thinkwiki.org/wiki/Installing_Ubuntu_6.10_%28Edgy_Eft%29_on_a_ThinkPad_T60#The_Fingerprint_Reader Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60] until you get to the Point where Keithvassallo says:
"Phew. Now, to make applications actually use the fingerprint reader."

I have done the following things instead of his version:

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

Change the file as following:

<pre>
#%PAM-1.0
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
auth requisite pam_nologin.so
auth required pam_env.so
@include common-auth
@include common-account
session required pam_limits.so
@include common-session
@include common-password
</pre>

and:

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

Change this file as following:

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

With this changes you have the advantage, that you are now able to login to Gnome or KDE whitout entering your password. But if you cancel the "Fingerprint Login", you are still able to login whit your username/password combination.

After I was able to login to my desktop I was unsatisfied, because my Computer still wants to get passwords i.e. when I tried to open Synaptic or when I do any sudo actions.

So I tried to figure out how this sudo thing works. I did the following change to /etc/pam.d/sudo with:

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

<pre>
#%PAM-1.0

auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/ :0
password sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam :0
auth required pam_unix.so nillock_secure
@include common-account

</pre>

With this change I was able to open System Administration tasks with my fingerprint, but the ugly thing is, that you get no information to swipe your finger over the reader when you have switched to a console session with {{Key|Ctrl}}+{{Key|Alt}}+{{Key|F1}}. The fingerprint scanner software will appear at your running X session.

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-10-10T08:33:53Z

Dirk: /* After The Kernel Update */

== My Thinkpad ==
<pre>
Lenovo Thinkpad R60 9461 HRG
Intel Core2Duo (Merom) 1.83 CPU
120 GB SATA Hitachi HTS54161 Harddisk
2 GB RAM
ATI Mobility X1400
</pre>

Originally equipped with a preinstalled MS Windows Vista Business. So the Harddisk was parted into two Partitions.

1. The Rescue & Recovery Partition

2. The preinstalled Windows Vista Partition

And as the parcel with my new Thinkpad arrived I was surprized, that there was a Windows Vista DVD (only 32 Bit Version) with it.
So I tried Vista - but I was a little bit shocked by it's performance. I never thought that a new computer could take so much time to boot up completely.

I decided to do a clean install of Vista, but I want to have Windows XP and Ubuntu Feisty on the Harddisk too.

== New Installation ==

I wanted to use all Space of the Harddisk, so I decided to kill the Rescue & and Recovery Partition, but to have the chance to go back to the factory default state I ordered Recovery DVD's at the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4HWSE3#Lenovo Support Call Center for Germany].
They shipped the 3 DVD's to me - free of charge - but I think it's only free if your Thinkpad is still in the warranty. I don't know exactly.

Then I created 2 Partitions on my Harddisk, 64 GB for Vista, 20 GB for XP, so 29 GB left free for Linux.

I installed Vista and XP and all the Thinkpad Stuff for each system.

When this was finished I took a Ubuntu Feisty Fawn installation CD and boot my Notebook with it. I created a 4 GB linux-swap partition and a 25 GB root / partition.

Because I want to boot my Ubuntu with the Windows Vista Boot Loader, I decided to install Grub to /dev/sda4 which is my Linux root partition.

The installation of Ubuntu Feisty Fawn works fine, NO PROBLEMS.

NOW I want to boot Linux from the Vista Bootloader, because I don't want to wait for two Bootscreens, and I wan't to have the chance to access the Repair Console of Windows Vista.

First I have to copy the Bootsector of my Linux Partition with:

<pre>
sudo dd if=/dev/sda4 of=/tmp/bootsect.lin bs=512 count=1
</pre>

Copy the bootsect.lin file to a USB-Stick or a writable partition which you can access from Windows Vista.

Now boot Windows Vista and copy the file bootsect.lin to your Systemdrive. In an Command Window with Administrator privileges type:

<pre>
copy bootsect.lin %SYSTEMDRIVE%\

bcdedit /create /d “Ubuntu” /application BOOTSECTOR
</pre>

You will receice an ID like this {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} from bcdedit. This is a uniqe identifier for your new Boot Entry in the Vista Bootloader. Now you will have to manipulate the entry with the following commands:

<pre>
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} device boot
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} PATH \bootsect.lin
bcdedit /displayorder {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} /addlast
bcdedit /timeout 10
</pre>

Then I booted my Ubuntu an did :

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

In this file I canged the entry the following entries:

<pre>
timeout 2
hiddenmenu
</pre>

So the computer starts up with the Windows Vista bootloader and gives me the option to start Windows XP, Windows Vista, Ubuntu and I have the option to do the repair tasks with the {{key|F8}} button on Vista if something fails. If I choose to boot Ubuntu I have the option to press the {{key|ESC}} key within the two seconds delay of the hidden Grub Menu. I.E. to boot another Linux Kernel.

== The tp_smapi modules ==

I did it under Feisty and, after the Upgrade under Gutsy, like described here : [http://www.thinkwiki.org/wiki/Tp_smapi#Installation TP SMAPI] in the Section "Installation on Ubuntu/Debian"
It worked, hdaps-gl and hdaps-pivot shows me now the movements of my Thinkpad. Like you can see here:

[[Image:Hdaps-pivot.png]]

[[Image:Hdaps-gl.png]]

== The Upgrade to Gutsy Gibbon ==

NO PROBLEMS. So why should I upgrade ?

OK I really wanted to get hdapsd (Harddisk Active Protection) to work. I tried a lot of things with Feisty, but I didn't get it going. And after a lot of seach through the Internet I found out that Gutsy Gibbon, the next Release of Ubuntu should have the Package for hdapsd on board.
SO I decided to upgrade to Gutsy - with the knowledge that it is still in Beta Stadium.

Upgrading Ubuntu is really simple, you only have to do the following steps:

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

Search all feisty entries and change them to gutsy. Save and Close the file.

Do:

{{cmduser| sudo apt-get update}}
{{cmduser| sudo apt-get upgrade}}

Go and drink a cup of Tea or Coffee. When you are back you have a message, that you should reboot your System, to get all packages active. So do it.

After the reboot I installed the hdapsd package and I tried to activate the Harddisk Protection with:

{{cmduser| sudo hdapsd -d sda -s 14 -a -v}}

But I still get the message "open(protect_file): No such file or directory". ---- The Same Message that I get in Feisty before I did the Upgrade. So I banged my head on the table and noticed that I'm not tough enough to get this thing working. Maybe someone else.

I decided to get the other things to work.

UPDATE: After some days I tried to get hdapsd to work, again !

== The hdapsd - Deamon (IBM Active Disk Protection) ==

Because I never had compiled or patched a kernel under Ubuntu I had to find out how this works ! After a lot of search in the Internet, the Ubuntu Help and at Thinkwiki.org I found the (hopefully) correct way to do it.

The best information I found was this :
[http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.04_on_a_ThinkPad_T43#Active_Protection_System_.28acceleration_monitor.29|Installing Ubuntu 7.04 on a ThinkPad T43] in section "Disk protection"

Here is what I did to get it to work:

1. Make sure that you have the required packages, with:

{{cmduser|sudo apt-get install build-essential fakeroot kernel-package libncurses5-dev wget bzip2 linux-source}}

2. Get the correct kernel patch for your running kernel from here : [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch_.28apply_using_.27patch_-p1_-l_.3C_hdaps_xx.patch.27.29| HDAPS] section "8.1.1 Kernel patch (apply using 'patch -p1 -l < hdaps_xx.patch')"

After all my experiences I was not sure that there was a patch available for my Gutsy-kernel (2.6.22-7-generic), but I still had my old kernel on the disk. So I booted up the old one (2.6.20-16-generic). Check the running kernel with:

{{cmduser|uname -r}}

You should see something like: 2.6.20-7-generic

Now change to /usr/src and look that the sources for the running kernel are there with:

{{cmduser|cd /usr/src}}
{{cmduser|ls -d linux-source*}}

You should see a file with the name "linux-source-2.6.20.tar.bz2" wich includes the packed kernel sources. You have to extract it, so do:

{{cmduser|sudo su}}
{{cmdroot|tar xvfj linux-source-2.6.20.tar.bz2}}

Now you have the kernel sources in the /usr/src/linux-source-2.6.20 directory. Take a look if there is a link from /usr/src/linux to an other kernel source directory (It's maybe there if you tried to compile a kernel some time before).

{{cmdroot|ls -l linux}}

If you see that linux is linked to an other source than your running kernel remove the link and create a new one with:

{{cmdroot|rm linux}}
{{cmdroot|ln -s /usr/src/linux-source-2.6.20 linux}}

Change to the source directory and patch the kernel with this:

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|patch -p1 -l < /home/dirk/993-001.bin}}

The file "993-001.bin" is the kernel patch for the 2.6.20 and 2.6.21 kernels, I downloaded it here : [http://article.gmane.org/gmane.linux.drivers.hdaps.devel/993]

After the patchwork I did this :

{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --append-to-version=.hdapscustom kernel_image --initrd binary

This would take its time, so go and clean up your house ;-)
{{HELP|I think the last command (with --append-to-version was an error ! I need help from an specialist in kernel compiling. Please read ahead at the next section "The hdapsd - Deamon (next try)". }}
After your house is clean you can do :

{{cmdroot|cd /usr/src}}
{{cmdroot|ls -l linux*.deb}}

You should see some newly builded Debian Pakage files. Install them with:

{{cmdroot|dpkg -i linux-headers-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-doc-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-image-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-manual-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-source-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}

After the installation you should reboot your computer, when Grub comes up make sure that you select your newly builded kernel.
Check it with:

{{cmduser|uname -r}}

You should see this "2.6.20.3-ubuntu1.hdapscustom". But now you have the Problem, that you have to recompile the tp_smapi driver.

{{cmduser|cd tp_smapi-0.31}}
$ sudo make install HDAPS=1
{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdaps}}

After :

<pre>
$ dmesg | grep hdaps
</pre>

You should see something like this:

[ 893.752000] hdaps: initial mode latch is 0x05
[ 893.752000] hdaps: setting ec_rate=250, filter_order=2
[ 893.752000] hdaps: fake_data_mode set to 0
[ 893.756000] hdaps: device successfully initialized.
[ 893.756000] input: hdaps as /class/input/input10
[ 893.756000] hdaps: driver successfully loaded.

Now we are ready to try out the hdapsd Deamon which is included in the Gutsy repositories, if you are using Feisty you have to compile it yourself like described here: [http://www.thinkwiki.org/wiki/How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS].

{{cmdroot|sudo hdapsd -d sda -s 12 -a -v}}

Should show this:

[[Image:hdapsd.png]]

If you load it with :

{{cmdroot|sudo hdapsd -d sda -s 12 -a}}

You get nothing until you move your Thinkpad, then you see:

Fri Jul 13 12:30:42 2007: parking
Fri Jul 13 12:30:43 2007: un-parking
Fri Jul 13 12:30:44 2007: parking
Fri Jul 13 12:30:45 2007: un-parking

Now, after I have a working hdaps-deamon I want it to be started at boot time. Because I have upgraded to Gutsy and installed the hdapsd - Package I have a script called /etc/default/hdapsd. Here I have to change some things. HINT: Remember that you still need the /etc/init.d/hdapsd file if you try this on Feisty and maybe you have to do:

{{cmduser|sudo update-rc.d hdapsd defaults}}

to create the init links for the hdapsd init script. My links was already there. My /etc/default/hdapsd script now looks like this:

<pre>
# hdapsd default file

# start hdapsd at boottime?
START="yes"

# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
DISK="sda"

# sensitivity
SENSITIVITY=12

# other options to pass to hdapsd.
# the -d $DISK, -s $SENSITIVITY, -b and -p $PIDFILE options are always passed.
OPTIONS="-a"

</pre>

Now I could use the gnome-hdaps-applet with the following comands:

{{cmduser|mkdir gnome-hdaps-applet}}
{{cmduser|cd gnome-hdaps-applet}}
{{cmduser|wget http://www.zen24593.zen.co.uk/hdaps/gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|tar -xzf gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|sudo apt-get install libpanel-applet2-dev}}
{{cmduser|gcc $(pkg-config --cflags --libs libpanelapplet-2.0) -o gnome-hdaps-applet gnome-hdaps-applet.c}}
{{cmduser|sudo cp gnome-hdaps-applet /usr/bin/}}
{{cmduser|sudo mkdir /usr/share/pixmaps/gnome-hdaps-applet/}}
{{cmduser|sudo cp *.png /usr/share/pixmaps/gnome-hdaps-applet/}}
$ sudo cp GNOME_HDAPS_StatusApplet.server /usr/lib/bonobo/servers/

Now after a restart of the Gnome Session I could find a "HDAPS Status" applet in the "Add to Panel" dialog. I added it, and when I move the Thinkpad it shows me the "Pause" [[Image:Hdaps-paused-small.png]] Symbol, otherwise it shows "Play" [[Image:Hdaps-running-small.png]].

So far so good !!! After I got this running I tried the same steps with the normal Gutsy Kernel (2.6.22-7-generic) on the same way, and it worked ! To my surprise with the same kernel patch.

The only Problem that I now have is that I cannot use restricted modules with my new kernels. Now I have to figure out how to compile restricted modules agains selfmade kernels.

{{HELP| }}

== The hdapsd - Deamon (next try) ==

I am not satisfied with the above result, because I cannot use the accelerated xorg-fglrx driver for my ATI Graphics Card and I cannot use my wireless Intel card ipw3945 driver. And the Ubuntu restricted-manager is not working. PLEASE can someone help me to compile a Ubuntu kernel in the correct way, so that I can use the whole hardware ?

I have done a - I think really ugly hack - to get the restricted-manager working :

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|cp /boot/config-2.6.20-16-generic /lib/modules/2.6.20-16-generic/.config}}
{{cmdroot|gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -16-generic".
Then I compiled the kernel again with:

{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I moved my modules with :

{{cmdroot|mv /lib/modules/2.6.20-16-generic /lib/modules/2.6.20-16-generic.orginal}}

And installed the kernel with:

{{cmdroot|dpkg -i linux-image-2.6.20-16-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers as described above.
Finally I copied the ipw3945.ucode with

{{cmdroot|cp /lib/firmware/2.6.22-7-generic/ipw3945.ucode /lib/firmware/2.6.20-16-generic/ipw3945.ucode}}

My wireless-card is working now !
My ATI Card cannot be configured with restricted-manager!

{{HELP|Please can someone who is conform in compiling Ubuntu kernels and restricted modules help me to do it in the correct way ! And can someone recheck the things described above, because I am not sure about all things that I have written here.
}}

After some days Ubuntu updated the kernel to version 2.6.22-9-generic, so I need to do the steps described above again, with "EXTRAVERSION = -9-generic". But now my wireless card and my grapics card did not work. The restricted-manager crashes when I start it.
So I downloaded the packages ipw3945-1.2.1.tgz and ati-driver-installer-8.39.4-x86.x86_64.run.

== The Wireless Card ==

First I extracted and installed the Intel Pro Wireless Package:

{{cmduser|tar xzvf ipw3945-1.2.1.tgz}}
{{cmduser|cd ipw3945-1.2.1}}
{{cmduser|make}}
{{cmduser|sudo make install}}

After this I could do :

{{cmduser|sudo modprobe ipw3945}}

The module was loaded, and i was able to use my wireless card now.

== The Graphics Card ==

For my Radeon Mobility X1400 I did the following steps:

{{cmduser|sudo apt get update}}
{{cmduser|sudo apt-get install module-assistant build-essential fakeroot dh-make debhelper debconf libstdc++5}}

Created a Debian Package with:

{{cmduser|sudo bash ati-driver-installer-8.39.4-x86.x86_64.run --buildpkg Ubuntu/gutsy}}

And blacklisted the old fglrx module with:

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

I added "fglrx" to the line with "DISABLED_MODULES". Then I installed the created Debian Packages with:

{{cmduser|sudo dpkg -i xorg-driver-fglrx_8.39.4-1_i386.deb fglrx-kernel-source_8.39.4-1_i386.deb fglrx-amdcccle_8.39.4-1_i386.deb}}

Then I compiled the kernel Modules:

{{cmduser|sudo module-assistant prepare}}
{{cmduser|sudo module-assistant update}}
{{cmduser|sudo module-assistant build fglrx}}
{{cmduser|sudo module-assistant install fglrx}}
{{cmduser|sudo depmod -a}}

The helpful informations for this was found at http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide.

After this steps my wifi-card and my graphics-card was working and restricted-manager was not crashing when I tried to start it.

== After The Kernel Update ==

On 9.October 2007 Ubuntu released the Kernelpackage linux-image-2.6.22-14-generic and I installed it. So here is what I have done to get it working:

{{cmduser|sudo apt-get install linux-headers-generic}}
{{cmduser|sudo ln -s /usr/src/linux-source-2.6.22 /lib/modules/2.6.22-14-generic/source}}
{{cmduser|sudo cd /usr/src/linux}}
{{cmduser|sudo make clean}}
{{cmduser|sudo cp /boot/config-2.6.22-14-generic .config}}
{{cmduser|sudo cp /boot/config-2.6.22-14-generic /lib/modules/2.6.22-14-generic/.config}}
{{cmduser|sudo gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -14-generic".

{{cmduser|sudo gedit .config}}

In the .config file I changed the entry " # CONFIG_SND_HDA_INTEL is not set " to " CONFIG_SND_HDA_INTEL=m ". This was needed to compile the module for my sound card.

Then I compiled the kernel again with:

{{cmduser|sudo make oldconfig}}
{{cmduser|sudo fakeroot make-kpkg clean}}
$ sudo fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I copied my modules with :

{{cmduser|sudo cp -R /lib/modules/2.6.22-14-generic /lib/modules/2.6.22-14-generic.orginal}}

And installed the kernel with:

{{cmduser|sudo dpkg -r linux-headers-generic linux-headers-2.6.22-14-generic}}
{{cmduser|cd ..}}
{{cmduser|sudo dpkg -i linux-image-2.6.22-14-generic_4711_i386.deb}}

When you install the new kernel you get this messages:

[[Image:Kernel1.png]]
[[Image:Kernel2.png]]
[[Image:Kernel3.png]]

Then I rebooted the computer and recompiled the tp_smapi drivers with:

{{cmduser|cd /home/dirk/tp_smapi-0.32}}
$ sudo make install HDAPS=1

After this I load the modules with:

{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdaps}}

And test it with:

{{cmduser|hdaps-gl}}

Now I had to get my sound-card working. The module from ubuntu is not working, I don't know why. So I did this:

{{cmduser|sudo mv /lib/modules/2.6.22-14-generic/ubuntu/media/snd-hda-intel/snd-hda-intel.ko
/lib/modules/2.6.22-14-generic/ubuntu/media/snd-hda-intel/snd-hda-intel.ko.orginal}}
{{cmduser|sudo cp /usr/src/linux-source-2.6.22/sound/pci/hda/snd-hda-intel.ko
/lib/modules/2.6.22-14-generic/ubuntu/media/snd-hda-intel/snd/hda-intel.ko}}

After this I load the modules with:

{{cmduser|sudo modprobe snd-hda-intel}}

To get my graphics card accelerated again I recompiled the kernel modules for it:

{{cmduser|sudo module-assistant prepare}}
{{cmduser|sudo module-assistant update}}
{{cmduser|sudo module-assistant build fglrx}}
{{cmduser|sudo module-assistant install fglrx}}
{{cmduser|sudo depmod -a}}

After this I restarted my computer and checked the acceleration with:

{{cmduser|glxgears}}

You should get something around 3100 FPS in 5 seconds (without acceleration it is around 700 FPS per 5 seconds).

== The Browser Buttons ==

I wanted to use the Browser Forward & Backward Buttons within Firefox. After the upgrade my Firefox had version 2.0.0.4

I did :

{{cmduser| gedit ~/.Xmodmap}}

and added the following lines :

keycode 234 = F19

keycode 233 = F20

I saved and closed the file. HINT: You have to re-login to Gnome to get the .Xmodmap file active.

Then I did the things described in [http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work#Firefox How to get special keys to work].

For the Windows Key I added "keycode 115 = F13" to my .Xmodmap File, then I klicked on "System - Einstellungen - Tastenkombinationen"
sorry I don't know how it is called in English. And changed the Entry "Das Panelmenü anzeigen" to F13

== The Brightness Buttons ==

When I wanted to control the brightness, I was not able to change it with {{key|Fn}}{{key|End}}.

So I did the Workaround menitioned here [http://thinkwiki.org/wiki/Problem_with_LCD_brightness_buttons#Workaround for Fedora Core 6 Users].
After this I was able to change the brightness with {{key|Fn}}{{key|Home}} and {{key|Fn}}{{key|End}}, but I don't have the OSD anymore.

UPDATE: You don't need to do this since kernel version 2.6.22 on Ubuntu

== The Fingerprint Reader ==

Do the steps which are described in [http://www.thinkwiki.org/wiki/Installing_Ubuntu_6.10_%28Edgy_Eft%29_on_a_ThinkPad_T60#The_Fingerprint_Reader Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60] until you get to the Point where Keithvassallo says:
"Phew. Now, to make applications actually use the fingerprint reader."

I have done the following things instead of his version:

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

Change the file as following:

<pre>
#%PAM-1.0
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
auth requisite pam_nologin.so
auth required pam_env.so
@include common-auth
@include common-account
session required pam_limits.so
@include common-session
@include common-password
</pre>

and:

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

Change this file as following:

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

With this changes you have the advantage, that you are now able to login to Gnome or KDE whitout entering your password. But if you cancel the "Fingerprint Login", you are still able to login whit your username/password combination.

After I was able to login to my desktop I was unsatisfied, because my Computer still wants to get passwords i.e. when I tried to open Synaptic or when I do any sudo actions.

So I tried to figure out how this sudo thing works. I did the following change to /etc/pam.d/sudo with:

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

<pre>
#%PAM-1.0

auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/ :0
password sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam :0
auth required pam_unix.so nillock_secure
@include common-account

</pre>

With this change I was able to open System Administration tasks with my fingerprint, but the ugly thing is, that you get no information to swipe your finger over the reader when you have switched to a console session with {{Key|Ctrl}}+{{Key|Alt}}+{{Key|F1}}. The fingerprint scanner software will appear at your running X session.

File:Kernel3.png

2007-10-10T08:33:05Z

Dirk:

File:Kernel2.png

2007-10-10T08:32:49Z

Dirk:

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-10-10T08:32:14Z

Dirk: /* After The Kernel Update */

== My Thinkpad ==
<pre>
Lenovo Thinkpad R60 9461 HRG
Intel Core2Duo (Merom) 1.83 CPU
120 GB SATA Hitachi HTS54161 Harddisk
2 GB RAM
ATI Mobility X1400
</pre>

Originally equipped with a preinstalled MS Windows Vista Business. So the Harddisk was parted into two Partitions.

1. The Rescue & Recovery Partition

2. The preinstalled Windows Vista Partition

And as the parcel with my new Thinkpad arrived I was surprized, that there was a Windows Vista DVD (only 32 Bit Version) with it.
So I tried Vista - but I was a little bit shocked by it's performance. I never thought that a new computer could take so much time to boot up completely.

I decided to do a clean install of Vista, but I want to have Windows XP and Ubuntu Feisty on the Harddisk too.

== New Installation ==

I wanted to use all Space of the Harddisk, so I decided to kill the Rescue & and Recovery Partition, but to have the chance to go back to the factory default state I ordered Recovery DVD's at the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4HWSE3#Lenovo Support Call Center for Germany].
They shipped the 3 DVD's to me - free of charge - but I think it's only free if your Thinkpad is still in the warranty. I don't know exactly.

Then I created 2 Partitions on my Harddisk, 64 GB for Vista, 20 GB for XP, so 29 GB left free for Linux.

I installed Vista and XP and all the Thinkpad Stuff for each system.

When this was finished I took a Ubuntu Feisty Fawn installation CD and boot my Notebook with it. I created a 4 GB linux-swap partition and a 25 GB root / partition.

Because I want to boot my Ubuntu with the Windows Vista Boot Loader, I decided to install Grub to /dev/sda4 which is my Linux root partition.

The installation of Ubuntu Feisty Fawn works fine, NO PROBLEMS.

NOW I want to boot Linux from the Vista Bootloader, because I don't want to wait for two Bootscreens, and I wan't to have the chance to access the Repair Console of Windows Vista.

First I have to copy the Bootsector of my Linux Partition with:

<pre>
sudo dd if=/dev/sda4 of=/tmp/bootsect.lin bs=512 count=1
</pre>

Copy the bootsect.lin file to a USB-Stick or a writable partition which you can access from Windows Vista.

Now boot Windows Vista and copy the file bootsect.lin to your Systemdrive. In an Command Window with Administrator privileges type:

<pre>
copy bootsect.lin %SYSTEMDRIVE%\

bcdedit /create /d “Ubuntu” /application BOOTSECTOR
</pre>

You will receice an ID like this {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} from bcdedit. This is a uniqe identifier for your new Boot Entry in the Vista Bootloader. Now you will have to manipulate the entry with the following commands:

<pre>
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} device boot
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} PATH \bootsect.lin
bcdedit /displayorder {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} /addlast
bcdedit /timeout 10
</pre>

Then I booted my Ubuntu an did :

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

In this file I canged the entry the following entries:

<pre>
timeout 2
hiddenmenu
</pre>

So the computer starts up with the Windows Vista bootloader and gives me the option to start Windows XP, Windows Vista, Ubuntu and I have the option to do the repair tasks with the {{key|F8}} button on Vista if something fails. If I choose to boot Ubuntu I have the option to press the {{key|ESC}} key within the two seconds delay of the hidden Grub Menu. I.E. to boot another Linux Kernel.

== The tp_smapi modules ==

I did it under Feisty and, after the Upgrade under Gutsy, like described here : [http://www.thinkwiki.org/wiki/Tp_smapi#Installation TP SMAPI] in the Section "Installation on Ubuntu/Debian"
It worked, hdaps-gl and hdaps-pivot shows me now the movements of my Thinkpad. Like you can see here:

[[Image:Hdaps-pivot.png]]

[[Image:Hdaps-gl.png]]

== The Upgrade to Gutsy Gibbon ==

NO PROBLEMS. So why should I upgrade ?

OK I really wanted to get hdapsd (Harddisk Active Protection) to work. I tried a lot of things with Feisty, but I didn't get it going. And after a lot of seach through the Internet I found out that Gutsy Gibbon, the next Release of Ubuntu should have the Package for hdapsd on board.
SO I decided to upgrade to Gutsy - with the knowledge that it is still in Beta Stadium.

Upgrading Ubuntu is really simple, you only have to do the following steps:

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

Search all feisty entries and change them to gutsy. Save and Close the file.

Do:

{{cmduser| sudo apt-get update}}
{{cmduser| sudo apt-get upgrade}}

Go and drink a cup of Tea or Coffee. When you are back you have a message, that you should reboot your System, to get all packages active. So do it.

After the reboot I installed the hdapsd package and I tried to activate the Harddisk Protection with:

{{cmduser| sudo hdapsd -d sda -s 14 -a -v}}

But I still get the message "open(protect_file): No such file or directory". ---- The Same Message that I get in Feisty before I did the Upgrade. So I banged my head on the table and noticed that I'm not tough enough to get this thing working. Maybe someone else.

I decided to get the other things to work.

UPDATE: After some days I tried to get hdapsd to work, again !

== The hdapsd - Deamon (IBM Active Disk Protection) ==

Because I never had compiled or patched a kernel under Ubuntu I had to find out how this works ! After a lot of search in the Internet, the Ubuntu Help and at Thinkwiki.org I found the (hopefully) correct way to do it.

The best information I found was this :
[http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.04_on_a_ThinkPad_T43#Active_Protection_System_.28acceleration_monitor.29|Installing Ubuntu 7.04 on a ThinkPad T43] in section "Disk protection"

Here is what I did to get it to work:

1. Make sure that you have the required packages, with:

{{cmduser|sudo apt-get install build-essential fakeroot kernel-package libncurses5-dev wget bzip2 linux-source}}

2. Get the correct kernel patch for your running kernel from here : [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch_.28apply_using_.27patch_-p1_-l_.3C_hdaps_xx.patch.27.29| HDAPS] section "8.1.1 Kernel patch (apply using 'patch -p1 -l < hdaps_xx.patch')"

After all my experiences I was not sure that there was a patch available for my Gutsy-kernel (2.6.22-7-generic), but I still had my old kernel on the disk. So I booted up the old one (2.6.20-16-generic). Check the running kernel with:

{{cmduser|uname -r}}

You should see something like: 2.6.20-7-generic

Now change to /usr/src and look that the sources for the running kernel are there with:

{{cmduser|cd /usr/src}}
{{cmduser|ls -d linux-source*}}

You should see a file with the name "linux-source-2.6.20.tar.bz2" wich includes the packed kernel sources. You have to extract it, so do:

{{cmduser|sudo su}}
{{cmdroot|tar xvfj linux-source-2.6.20.tar.bz2}}

Now you have the kernel sources in the /usr/src/linux-source-2.6.20 directory. Take a look if there is a link from /usr/src/linux to an other kernel source directory (It's maybe there if you tried to compile a kernel some time before).

{{cmdroot|ls -l linux}}

If you see that linux is linked to an other source than your running kernel remove the link and create a new one with:

{{cmdroot|rm linux}}
{{cmdroot|ln -s /usr/src/linux-source-2.6.20 linux}}

Change to the source directory and patch the kernel with this:

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|patch -p1 -l < /home/dirk/993-001.bin}}

The file "993-001.bin" is the kernel patch for the 2.6.20 and 2.6.21 kernels, I downloaded it here : [http://article.gmane.org/gmane.linux.drivers.hdaps.devel/993]

After the patchwork I did this :

{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --append-to-version=.hdapscustom kernel_image --initrd binary

This would take its time, so go and clean up your house ;-)
{{HELP|I think the last command (with --append-to-version was an error ! I need help from an specialist in kernel compiling. Please read ahead at the next section "The hdapsd - Deamon (next try)". }}
After your house is clean you can do :

{{cmdroot|cd /usr/src}}
{{cmdroot|ls -l linux*.deb}}

You should see some newly builded Debian Pakage files. Install them with:

{{cmdroot|dpkg -i linux-headers-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-doc-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-image-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-manual-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-source-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}

After the installation you should reboot your computer, when Grub comes up make sure that you select your newly builded kernel.
Check it with:

{{cmduser|uname -r}}

You should see this "2.6.20.3-ubuntu1.hdapscustom". But now you have the Problem, that you have to recompile the tp_smapi driver.

{{cmduser|cd tp_smapi-0.31}}
$ sudo make install HDAPS=1
{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdaps}}

After :

<pre>
$ dmesg | grep hdaps
</pre>

You should see something like this:

[ 893.752000] hdaps: initial mode latch is 0x05
[ 893.752000] hdaps: setting ec_rate=250, filter_order=2
[ 893.752000] hdaps: fake_data_mode set to 0
[ 893.756000] hdaps: device successfully initialized.
[ 893.756000] input: hdaps as /class/input/input10
[ 893.756000] hdaps: driver successfully loaded.

Now we are ready to try out the hdapsd Deamon which is included in the Gutsy repositories, if you are using Feisty you have to compile it yourself like described here: [http://www.thinkwiki.org/wiki/How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS].

{{cmdroot|sudo hdapsd -d sda -s 12 -a -v}}

Should show this:

[[Image:hdapsd.png]]

If you load it with :

{{cmdroot|sudo hdapsd -d sda -s 12 -a}}

You get nothing until you move your Thinkpad, then you see:

Fri Jul 13 12:30:42 2007: parking
Fri Jul 13 12:30:43 2007: un-parking
Fri Jul 13 12:30:44 2007: parking
Fri Jul 13 12:30:45 2007: un-parking

Now, after I have a working hdaps-deamon I want it to be started at boot time. Because I have upgraded to Gutsy and installed the hdapsd - Package I have a script called /etc/default/hdapsd. Here I have to change some things. HINT: Remember that you still need the /etc/init.d/hdapsd file if you try this on Feisty and maybe you have to do:

{{cmduser|sudo update-rc.d hdapsd defaults}}

to create the init links for the hdapsd init script. My links was already there. My /etc/default/hdapsd script now looks like this:

<pre>
# hdapsd default file

# start hdapsd at boottime?
START="yes"

# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
DISK="sda"

# sensitivity
SENSITIVITY=12

# other options to pass to hdapsd.
# the -d $DISK, -s $SENSITIVITY, -b and -p $PIDFILE options are always passed.
OPTIONS="-a"

</pre>

Now I could use the gnome-hdaps-applet with the following comands:

{{cmduser|mkdir gnome-hdaps-applet}}
{{cmduser|cd gnome-hdaps-applet}}
{{cmduser|wget http://www.zen24593.zen.co.uk/hdaps/gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|tar -xzf gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|sudo apt-get install libpanel-applet2-dev}}
{{cmduser|gcc $(pkg-config --cflags --libs libpanelapplet-2.0) -o gnome-hdaps-applet gnome-hdaps-applet.c}}
{{cmduser|sudo cp gnome-hdaps-applet /usr/bin/}}
{{cmduser|sudo mkdir /usr/share/pixmaps/gnome-hdaps-applet/}}
{{cmduser|sudo cp *.png /usr/share/pixmaps/gnome-hdaps-applet/}}
$ sudo cp GNOME_HDAPS_StatusApplet.server /usr/lib/bonobo/servers/

Now after a restart of the Gnome Session I could find a "HDAPS Status" applet in the "Add to Panel" dialog. I added it, and when I move the Thinkpad it shows me the "Pause" [[Image:Hdaps-paused-small.png]] Symbol, otherwise it shows "Play" [[Image:Hdaps-running-small.png]].

So far so good !!! After I got this running I tried the same steps with the normal Gutsy Kernel (2.6.22-7-generic) on the same way, and it worked ! To my surprise with the same kernel patch.

The only Problem that I now have is that I cannot use restricted modules with my new kernels. Now I have to figure out how to compile restricted modules agains selfmade kernels.

{{HELP| }}

== The hdapsd - Deamon (next try) ==

I am not satisfied with the above result, because I cannot use the accelerated xorg-fglrx driver for my ATI Graphics Card and I cannot use my wireless Intel card ipw3945 driver. And the Ubuntu restricted-manager is not working. PLEASE can someone help me to compile a Ubuntu kernel in the correct way, so that I can use the whole hardware ?

I have done a - I think really ugly hack - to get the restricted-manager working :

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|cp /boot/config-2.6.20-16-generic /lib/modules/2.6.20-16-generic/.config}}
{{cmdroot|gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -16-generic".
Then I compiled the kernel again with:

{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I moved my modules with :

{{cmdroot|mv /lib/modules/2.6.20-16-generic /lib/modules/2.6.20-16-generic.orginal}}

And installed the kernel with:

{{cmdroot|dpkg -i linux-image-2.6.20-16-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers as described above.
Finally I copied the ipw3945.ucode with

{{cmdroot|cp /lib/firmware/2.6.22-7-generic/ipw3945.ucode /lib/firmware/2.6.20-16-generic/ipw3945.ucode}}

My wireless-card is working now !
My ATI Card cannot be configured with restricted-manager!

{{HELP|Please can someone who is conform in compiling Ubuntu kernels and restricted modules help me to do it in the correct way ! And can someone recheck the things described above, because I am not sure about all things that I have written here.
}}

After some days Ubuntu updated the kernel to version 2.6.22-9-generic, so I need to do the steps described above again, with "EXTRAVERSION = -9-generic". But now my wireless card and my grapics card did not work. The restricted-manager crashes when I start it.
So I downloaded the packages ipw3945-1.2.1.tgz and ati-driver-installer-8.39.4-x86.x86_64.run.

== The Wireless Card ==

First I extracted and installed the Intel Pro Wireless Package:

{{cmduser|tar xzvf ipw3945-1.2.1.tgz}}
{{cmduser|cd ipw3945-1.2.1}}
{{cmduser|make}}
{{cmduser|sudo make install}}

After this I could do :

{{cmduser|sudo modprobe ipw3945}}

The module was loaded, and i was able to use my wireless card now.

== The Graphics Card ==

For my Radeon Mobility X1400 I did the following steps:

{{cmduser|sudo apt get update}}
{{cmduser|sudo apt-get install module-assistant build-essential fakeroot dh-make debhelper debconf libstdc++5}}

Created a Debian Package with:

{{cmduser|sudo bash ati-driver-installer-8.39.4-x86.x86_64.run --buildpkg Ubuntu/gutsy}}

And blacklisted the old fglrx module with:

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

I added "fglrx" to the line with "DISABLED_MODULES". Then I installed the created Debian Packages with:

{{cmduser|sudo dpkg -i xorg-driver-fglrx_8.39.4-1_i386.deb fglrx-kernel-source_8.39.4-1_i386.deb fglrx-amdcccle_8.39.4-1_i386.deb}}

Then I compiled the kernel Modules:

{{cmduser|sudo module-assistant prepare}}
{{cmduser|sudo module-assistant update}}
{{cmduser|sudo module-assistant build fglrx}}
{{cmduser|sudo module-assistant install fglrx}}
{{cmduser|sudo depmod -a}}

The helpful informations for this was found at http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide.

After this steps my wifi-card and my graphics-card was working and restricted-manager was not crashing when I tried to start it.

== After The Kernel Update ==

On 9.October 2007 Ubuntu released the Kernelpackage linux-image-2.6.22-14-generic and I installed it. So here is what I have done to get it working:

{{cmduser|sudo apt-get install linux-headers-generic}}
{{cmduser|sudo ln -s /usr/src/linux-source-2.6.22 /lib/modules/2.6.22-14-generic/source}}
{{cmduser|sudo cd /usr/src/linux}}
{{cmduser|sudo make clean}}
{{cmduser|sudo cp /boot/config-2.6.22-14-generic .config}}
{{cmduser|sudo cp /boot/config-2.6.22-14-generic /lib/modules/2.6.22-14-generic/.config}}
{{cmduser|sudo gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -14-generic".

{{cmduser|sudo gedit .config}}

In the .config file I changed the entry " # CONFIG_SND_HDA_INTEL is not set " to " CONFIG_SND_HDA_INTEL=m ". This was needed to compile the module for my sound card.

Then I compiled the kernel again with:

{{cmduser|sudo make oldconfig}}
{{cmduser|sudo fakeroot make-kpkg clean}}
$ sudo fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I copied my modules with :

{{cmduser|sudo cp -R /lib/modules/2.6.22-14-generic /lib/modules/2.6.22-14-generic.orginal}}

And installed the kernel with:

{{cmduser|sudo dpkg -r linux-headers-generic linux-headers-2.6.22-14-generic}}
{{cmduser|cd ..}}
{{cmduser|sudo dpkg -i linux-image-2.6.22-14-generic_4711_i386.deb}}

When you install the new kernel you get this messages:

[[Image:Kernel1.png]]

Then I rebooted the computer and recompiled the tp_smapi drivers with:

{{cmduser|cd /home/dirk/tp_smapi-0.32}}
$ sudo make install HDAPS=1

After this I load the modules with:

{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdaps}}

And test it with:

{{cmduser|hdaps-gl}}

Now I had to get my sound-card working. The module from ubuntu is not working, I don't know why. So I did this:

{{cmduser|sudo mv /lib/modules/2.6.22-14-generic/ubuntu/media/snd-hda-intel/snd-hda-intel.ko
/lib/modules/2.6.22-14-generic/ubuntu/media/snd-hda-intel/snd-hda-intel.ko.orginal}}
{{cmduser|sudo cp /usr/src/linux-source-2.6.22/sound/pci/hda/snd-hda-intel.ko
/lib/modules/2.6.22-14-generic/ubuntu/media/snd-hda-intel/snd/hda-intel.ko}}

After this I load the modules with:

{{cmduser|sudo modprobe snd-hda-intel}}

To get my graphics card accelerated again I recompiled the kernel modules for it:

{{cmduser|sudo module-assistant prepare}}
{{cmduser|sudo module-assistant update}}
{{cmduser|sudo module-assistant build fglrx}}
{{cmduser|sudo module-assistant install fglrx}}
{{cmduser|sudo depmod -a}}

After this I restarted my computer and checked the acceleration with:

{{cmduser|glxgears}}

You should get something around 3100 FPS in 5 seconds (without acceleration it is around 700 FPS per 5 seconds).

== The Browser Buttons ==

I wanted to use the Browser Forward & Backward Buttons within Firefox. After the upgrade my Firefox had version 2.0.0.4

I did :

{{cmduser| gedit ~/.Xmodmap}}

and added the following lines :

keycode 234 = F19

keycode 233 = F20

I saved and closed the file. HINT: You have to re-login to Gnome to get the .Xmodmap file active.

Then I did the things described in [http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work#Firefox How to get special keys to work].

For the Windows Key I added "keycode 115 = F13" to my .Xmodmap File, then I klicked on "System - Einstellungen - Tastenkombinationen"
sorry I don't know how it is called in English. And changed the Entry "Das Panelmenü anzeigen" to F13

== The Brightness Buttons ==

When I wanted to control the brightness, I was not able to change it with {{key|Fn}}{{key|End}}.

So I did the Workaround menitioned here [http://thinkwiki.org/wiki/Problem_with_LCD_brightness_buttons#Workaround for Fedora Core 6 Users].
After this I was able to change the brightness with {{key|Fn}}{{key|Home}} and {{key|Fn}}{{key|End}}, but I don't have the OSD anymore.

UPDATE: You don't need to do this since kernel version 2.6.22 on Ubuntu

== The Fingerprint Reader ==

Do the steps which are described in [http://www.thinkwiki.org/wiki/Installing_Ubuntu_6.10_%28Edgy_Eft%29_on_a_ThinkPad_T60#The_Fingerprint_Reader Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60] until you get to the Point where Keithvassallo says:
"Phew. Now, to make applications actually use the fingerprint reader."

I have done the following things instead of his version:

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

Change the file as following:

<pre>
#%PAM-1.0
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
auth requisite pam_nologin.so
auth required pam_env.so
@include common-auth
@include common-account
session required pam_limits.so
@include common-session
@include common-password
</pre>

and:

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

Change this file as following:

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

With this changes you have the advantage, that you are now able to login to Gnome or KDE whitout entering your password. But if you cancel the "Fingerprint Login", you are still able to login whit your username/password combination.

After I was able to login to my desktop I was unsatisfied, because my Computer still wants to get passwords i.e. when I tried to open Synaptic or when I do any sudo actions.

So I tried to figure out how this sudo thing works. I did the following change to /etc/pam.d/sudo with:

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

<pre>
#%PAM-1.0

auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/ :0
password sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam :0
auth required pam_unix.so nillock_secure
@include common-account

</pre>

With this change I was able to open System Administration tasks with my fingerprint, but the ugly thing is, that you get no information to swipe your finger over the reader when you have switched to a console session with {{Key|Ctrl}}+{{Key|Alt}}+{{Key|F1}}. The fingerprint scanner software will appear at your running X session.

File:Kernel1.png

2007-10-10T08:30:15Z

Dirk:

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-10-10T08:26:02Z

Dirk: /* After The Kernel Update */

== My Thinkpad ==
<pre>
Lenovo Thinkpad R60 9461 HRG
Intel Core2Duo (Merom) 1.83 CPU
120 GB SATA Hitachi HTS54161 Harddisk
2 GB RAM
ATI Mobility X1400
</pre>

Originally equipped with a preinstalled MS Windows Vista Business. So the Harddisk was parted into two Partitions.

1. The Rescue & Recovery Partition

2. The preinstalled Windows Vista Partition

And as the parcel with my new Thinkpad arrived I was surprized, that there was a Windows Vista DVD (only 32 Bit Version) with it.
So I tried Vista - but I was a little bit shocked by it's performance. I never thought that a new computer could take so much time to boot up completely.

I decided to do a clean install of Vista, but I want to have Windows XP and Ubuntu Feisty on the Harddisk too.

== New Installation ==

I wanted to use all Space of the Harddisk, so I decided to kill the Rescue & and Recovery Partition, but to have the chance to go back to the factory default state I ordered Recovery DVD's at the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4HWSE3#Lenovo Support Call Center for Germany].
They shipped the 3 DVD's to me - free of charge - but I think it's only free if your Thinkpad is still in the warranty. I don't know exactly.

Then I created 2 Partitions on my Harddisk, 64 GB for Vista, 20 GB for XP, so 29 GB left free for Linux.

I installed Vista and XP and all the Thinkpad Stuff for each system.

When this was finished I took a Ubuntu Feisty Fawn installation CD and boot my Notebook with it. I created a 4 GB linux-swap partition and a 25 GB root / partition.

Because I want to boot my Ubuntu with the Windows Vista Boot Loader, I decided to install Grub to /dev/sda4 which is my Linux root partition.

The installation of Ubuntu Feisty Fawn works fine, NO PROBLEMS.

NOW I want to boot Linux from the Vista Bootloader, because I don't want to wait for two Bootscreens, and I wan't to have the chance to access the Repair Console of Windows Vista.

First I have to copy the Bootsector of my Linux Partition with:

<pre>
sudo dd if=/dev/sda4 of=/tmp/bootsect.lin bs=512 count=1
</pre>

Copy the bootsect.lin file to a USB-Stick or a writable partition which you can access from Windows Vista.

Now boot Windows Vista and copy the file bootsect.lin to your Systemdrive. In an Command Window with Administrator privileges type:

<pre>
copy bootsect.lin %SYSTEMDRIVE%\

bcdedit /create /d “Ubuntu” /application BOOTSECTOR
</pre>

You will receice an ID like this {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} from bcdedit. This is a uniqe identifier for your new Boot Entry in the Vista Bootloader. Now you will have to manipulate the entry with the following commands:

<pre>
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} device boot
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} PATH \bootsect.lin
bcdedit /displayorder {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} /addlast
bcdedit /timeout 10
</pre>

Then I booted my Ubuntu an did :

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

In this file I canged the entry the following entries:

<pre>
timeout 2
hiddenmenu
</pre>

So the computer starts up with the Windows Vista bootloader and gives me the option to start Windows XP, Windows Vista, Ubuntu and I have the option to do the repair tasks with the {{key|F8}} button on Vista if something fails. If I choose to boot Ubuntu I have the option to press the {{key|ESC}} key within the two seconds delay of the hidden Grub Menu. I.E. to boot another Linux Kernel.

== The tp_smapi modules ==

I did it under Feisty and, after the Upgrade under Gutsy, like described here : [http://www.thinkwiki.org/wiki/Tp_smapi#Installation TP SMAPI] in the Section "Installation on Ubuntu/Debian"
It worked, hdaps-gl and hdaps-pivot shows me now the movements of my Thinkpad. Like you can see here:

[[Image:Hdaps-pivot.png]]

[[Image:Hdaps-gl.png]]

== The Upgrade to Gutsy Gibbon ==

NO PROBLEMS. So why should I upgrade ?

OK I really wanted to get hdapsd (Harddisk Active Protection) to work. I tried a lot of things with Feisty, but I didn't get it going. And after a lot of seach through the Internet I found out that Gutsy Gibbon, the next Release of Ubuntu should have the Package for hdapsd on board.
SO I decided to upgrade to Gutsy - with the knowledge that it is still in Beta Stadium.

Upgrading Ubuntu is really simple, you only have to do the following steps:

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

Search all feisty entries and change them to gutsy. Save and Close the file.

Do:

{{cmduser| sudo apt-get update}}
{{cmduser| sudo apt-get upgrade}}

Go and drink a cup of Tea or Coffee. When you are back you have a message, that you should reboot your System, to get all packages active. So do it.

After the reboot I installed the hdapsd package and I tried to activate the Harddisk Protection with:

{{cmduser| sudo hdapsd -d sda -s 14 -a -v}}

But I still get the message "open(protect_file): No such file or directory". ---- The Same Message that I get in Feisty before I did the Upgrade. So I banged my head on the table and noticed that I'm not tough enough to get this thing working. Maybe someone else.

I decided to get the other things to work.

UPDATE: After some days I tried to get hdapsd to work, again !

== The hdapsd - Deamon (IBM Active Disk Protection) ==

Because I never had compiled or patched a kernel under Ubuntu I had to find out how this works ! After a lot of search in the Internet, the Ubuntu Help and at Thinkwiki.org I found the (hopefully) correct way to do it.

The best information I found was this :
[http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.04_on_a_ThinkPad_T43#Active_Protection_System_.28acceleration_monitor.29|Installing Ubuntu 7.04 on a ThinkPad T43] in section "Disk protection"

Here is what I did to get it to work:

1. Make sure that you have the required packages, with:

{{cmduser|sudo apt-get install build-essential fakeroot kernel-package libncurses5-dev wget bzip2 linux-source}}

2. Get the correct kernel patch for your running kernel from here : [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch_.28apply_using_.27patch_-p1_-l_.3C_hdaps_xx.patch.27.29| HDAPS] section "8.1.1 Kernel patch (apply using 'patch -p1 -l < hdaps_xx.patch')"

After all my experiences I was not sure that there was a patch available for my Gutsy-kernel (2.6.22-7-generic), but I still had my old kernel on the disk. So I booted up the old one (2.6.20-16-generic). Check the running kernel with:

{{cmduser|uname -r}}

You should see something like: 2.6.20-7-generic

Now change to /usr/src and look that the sources for the running kernel are there with:

{{cmduser|cd /usr/src}}
{{cmduser|ls -d linux-source*}}

You should see a file with the name "linux-source-2.6.20.tar.bz2" wich includes the packed kernel sources. You have to extract it, so do:

{{cmduser|sudo su}}
{{cmdroot|tar xvfj linux-source-2.6.20.tar.bz2}}

Now you have the kernel sources in the /usr/src/linux-source-2.6.20 directory. Take a look if there is a link from /usr/src/linux to an other kernel source directory (It's maybe there if you tried to compile a kernel some time before).

{{cmdroot|ls -l linux}}

If you see that linux is linked to an other source than your running kernel remove the link and create a new one with:

{{cmdroot|rm linux}}
{{cmdroot|ln -s /usr/src/linux-source-2.6.20 linux}}

Change to the source directory and patch the kernel with this:

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|patch -p1 -l < /home/dirk/993-001.bin}}

The file "993-001.bin" is the kernel patch for the 2.6.20 and 2.6.21 kernels, I downloaded it here : [http://article.gmane.org/gmane.linux.drivers.hdaps.devel/993]

After the patchwork I did this :

{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --append-to-version=.hdapscustom kernel_image --initrd binary

This would take its time, so go and clean up your house ;-)
{{HELP|I think the last command (with --append-to-version was an error ! I need help from an specialist in kernel compiling. Please read ahead at the next section "The hdapsd - Deamon (next try)". }}
After your house is clean you can do :

{{cmdroot|cd /usr/src}}
{{cmdroot|ls -l linux*.deb}}

You should see some newly builded Debian Pakage files. Install them with:

{{cmdroot|dpkg -i linux-headers-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-doc-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-image-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-manual-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-source-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}

After the installation you should reboot your computer, when Grub comes up make sure that you select your newly builded kernel.
Check it with:

{{cmduser|uname -r}}

You should see this "2.6.20.3-ubuntu1.hdapscustom". But now you have the Problem, that you have to recompile the tp_smapi driver.

{{cmduser|cd tp_smapi-0.31}}
$ sudo make install HDAPS=1
{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdaps}}

After :

<pre>
$ dmesg | grep hdaps
</pre>

You should see something like this:

[ 893.752000] hdaps: initial mode latch is 0x05
[ 893.752000] hdaps: setting ec_rate=250, filter_order=2
[ 893.752000] hdaps: fake_data_mode set to 0
[ 893.756000] hdaps: device successfully initialized.
[ 893.756000] input: hdaps as /class/input/input10
[ 893.756000] hdaps: driver successfully loaded.

Now we are ready to try out the hdapsd Deamon which is included in the Gutsy repositories, if you are using Feisty you have to compile it yourself like described here: [http://www.thinkwiki.org/wiki/How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS].

{{cmdroot|sudo hdapsd -d sda -s 12 -a -v}}

Should show this:

[[Image:hdapsd.png]]

If you load it with :

{{cmdroot|sudo hdapsd -d sda -s 12 -a}}

You get nothing until you move your Thinkpad, then you see:

Fri Jul 13 12:30:42 2007: parking
Fri Jul 13 12:30:43 2007: un-parking
Fri Jul 13 12:30:44 2007: parking
Fri Jul 13 12:30:45 2007: un-parking

Now, after I have a working hdaps-deamon I want it to be started at boot time. Because I have upgraded to Gutsy and installed the hdapsd - Package I have a script called /etc/default/hdapsd. Here I have to change some things. HINT: Remember that you still need the /etc/init.d/hdapsd file if you try this on Feisty and maybe you have to do:

{{cmduser|sudo update-rc.d hdapsd defaults}}

to create the init links for the hdapsd init script. My links was already there. My /etc/default/hdapsd script now looks like this:

<pre>
# hdapsd default file

# start hdapsd at boottime?
START="yes"

# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
DISK="sda"

# sensitivity
SENSITIVITY=12

# other options to pass to hdapsd.
# the -d $DISK, -s $SENSITIVITY, -b and -p $PIDFILE options are always passed.
OPTIONS="-a"

</pre>

Now I could use the gnome-hdaps-applet with the following comands:

{{cmduser|mkdir gnome-hdaps-applet}}
{{cmduser|cd gnome-hdaps-applet}}
{{cmduser|wget http://www.zen24593.zen.co.uk/hdaps/gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|tar -xzf gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|sudo apt-get install libpanel-applet2-dev}}
{{cmduser|gcc $(pkg-config --cflags --libs libpanelapplet-2.0) -o gnome-hdaps-applet gnome-hdaps-applet.c}}
{{cmduser|sudo cp gnome-hdaps-applet /usr/bin/}}
{{cmduser|sudo mkdir /usr/share/pixmaps/gnome-hdaps-applet/}}
{{cmduser|sudo cp *.png /usr/share/pixmaps/gnome-hdaps-applet/}}
$ sudo cp GNOME_HDAPS_StatusApplet.server /usr/lib/bonobo/servers/

Now after a restart of the Gnome Session I could find a "HDAPS Status" applet in the "Add to Panel" dialog. I added it, and when I move the Thinkpad it shows me the "Pause" [[Image:Hdaps-paused-small.png]] Symbol, otherwise it shows "Play" [[Image:Hdaps-running-small.png]].

So far so good !!! After I got this running I tried the same steps with the normal Gutsy Kernel (2.6.22-7-generic) on the same way, and it worked ! To my surprise with the same kernel patch.

The only Problem that I now have is that I cannot use restricted modules with my new kernels. Now I have to figure out how to compile restricted modules agains selfmade kernels.

{{HELP| }}

== The hdapsd - Deamon (next try) ==

I am not satisfied with the above result, because I cannot use the accelerated xorg-fglrx driver for my ATI Graphics Card and I cannot use my wireless Intel card ipw3945 driver. And the Ubuntu restricted-manager is not working. PLEASE can someone help me to compile a Ubuntu kernel in the correct way, so that I can use the whole hardware ?

I have done a - I think really ugly hack - to get the restricted-manager working :

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|cp /boot/config-2.6.20-16-generic /lib/modules/2.6.20-16-generic/.config}}
{{cmdroot|gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -16-generic".
Then I compiled the kernel again with:

{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I moved my modules with :

{{cmdroot|mv /lib/modules/2.6.20-16-generic /lib/modules/2.6.20-16-generic.orginal}}

And installed the kernel with:

{{cmdroot|dpkg -i linux-image-2.6.20-16-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers as described above.
Finally I copied the ipw3945.ucode with

{{cmdroot|cp /lib/firmware/2.6.22-7-generic/ipw3945.ucode /lib/firmware/2.6.20-16-generic/ipw3945.ucode}}

My wireless-card is working now !
My ATI Card cannot be configured with restricted-manager!

{{HELP|Please can someone who is conform in compiling Ubuntu kernels and restricted modules help me to do it in the correct way ! And can someone recheck the things described above, because I am not sure about all things that I have written here.
}}

After some days Ubuntu updated the kernel to version 2.6.22-9-generic, so I need to do the steps described above again, with "EXTRAVERSION = -9-generic". But now my wireless card and my grapics card did not work. The restricted-manager crashes when I start it.
So I downloaded the packages ipw3945-1.2.1.tgz and ati-driver-installer-8.39.4-x86.x86_64.run.

== The Wireless Card ==

First I extracted and installed the Intel Pro Wireless Package:

{{cmduser|tar xzvf ipw3945-1.2.1.tgz}}
{{cmduser|cd ipw3945-1.2.1}}
{{cmduser|make}}
{{cmduser|sudo make install}}

After this I could do :

{{cmduser|sudo modprobe ipw3945}}

The module was loaded, and i was able to use my wireless card now.

== The Graphics Card ==

For my Radeon Mobility X1400 I did the following steps:

{{cmduser|sudo apt get update}}
{{cmduser|sudo apt-get install module-assistant build-essential fakeroot dh-make debhelper debconf libstdc++5}}

Created a Debian Package with:

{{cmduser|sudo bash ati-driver-installer-8.39.4-x86.x86_64.run --buildpkg Ubuntu/gutsy}}

And blacklisted the old fglrx module with:

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

I added "fglrx" to the line with "DISABLED_MODULES". Then I installed the created Debian Packages with:

{{cmduser|sudo dpkg -i xorg-driver-fglrx_8.39.4-1_i386.deb fglrx-kernel-source_8.39.4-1_i386.deb fglrx-amdcccle_8.39.4-1_i386.deb}}

Then I compiled the kernel Modules:

{{cmduser|sudo module-assistant prepare}}
{{cmduser|sudo module-assistant update}}
{{cmduser|sudo module-assistant build fglrx}}
{{cmduser|sudo module-assistant install fglrx}}
{{cmduser|sudo depmod -a}}

The helpful informations for this was found at http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide.

After this steps my wifi-card and my graphics-card was working and restricted-manager was not crashing when I tried to start it.

== After The Kernel Update ==

On 9.October 2007 Ubuntu released the Kernelpackage linux-image-2.6.22-14-generic and I installed it. So here is what I have done to get it working:

{{cmduser|sudo apt-get install linux-headers-generic}}
{{cmduser|sudo ln -s /usr/src/linux-source-2.6.22 /lib/modules/2.6.22-14-generic/source}}
{{cmduser|sudo cd /usr/src/linux}}
{{cmduser|sudo make clean}}
{{cmduser|sudo cp /boot/config-2.6.22-14-generic .config}}
{{cmduser|sudo cp /boot/config-2.6.22-14-generic /lib/modules/2.6.22-14-generic/.config}}
{{cmduser|sudo gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -14-generic".

{{cmduser|sudo gedit .config}}

In the .config file I changed the entry " # CONFIG_SND_HDA_INTEL is not set " to " CONFIG_SND_HDA_INTEL=m ". This was needed to compile the module for my sound card.

Then I compiled the kernel again with:

{{cmduser|sudo make oldconfig}}
{{cmduser|sudo fakeroot make-kpkg clean}}
$ sudo fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I copied my modules with :

{{cmduser|sudo cp -R /lib/modules/2.6.22-14-generic /lib/modules/2.6.22-14-generic.orginal}}

And installed the kernel with:

{{cmduser|sudo dpkg -r linux-headers-generic linux-headers-2.6.22-14-generic}}
{{cmduser|cd ..}}
{{cmduser|sudo dpkg -i linux-image-2.6.22-14-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers with:

{{cmduser|cd /home/dirk/tp_smapi-0.32}}
$ sudo make install HDAPS=1

After this I load the modules with:

{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdaps}}

And test it with:

{{cmduser|hdaps-gl}}

Now I had to get my sound-card working. The module from ubuntu is not working, I don't know why. So I did this:

{{cmduser|sudo mv /lib/modules/2.6.22-14-generic/ubuntu/media/snd-hda-intel/snd-hda-intel.ko
/lib/modules/2.6.22-14-generic/ubuntu/media/snd-hda-intel/snd-hda-intel.ko.orginal}}
{{cmduser|sudo cp /usr/src/linux-source-2.6.22/sound/pci/hda/snd-hda-intel.ko
/lib/modules/2.6.22-14-generic/ubuntu/media/snd-hda-intel/snd/hda-intel.ko}}

After this I load the modules with:

{{cmduser|sudo modprobe snd-hda-intel}}

To get my graphics card accelerated again I recompiled the kernel modules for it:

{{cmduser|sudo module-assistant prepare}}
{{cmduser|sudo module-assistant update}}
{{cmduser|sudo module-assistant build fglrx}}
{{cmduser|sudo module-assistant install fglrx}}
{{cmduser|sudo depmod -a}}

After this I restarted my computer and checked the acceleration with:

{{cmduser|glxgears}}

You should get something around 3100 FPS in 5 seconds (without acceleration it is around 700 FPS per 5 seconds).

== The Browser Buttons ==

I wanted to use the Browser Forward & Backward Buttons within Firefox. After the upgrade my Firefox had version 2.0.0.4

I did :

{{cmduser| gedit ~/.Xmodmap}}

and added the following lines :

keycode 234 = F19

keycode 233 = F20

I saved and closed the file. HINT: You have to re-login to Gnome to get the .Xmodmap file active.

Then I did the things described in [http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work#Firefox How to get special keys to work].

For the Windows Key I added "keycode 115 = F13" to my .Xmodmap File, then I klicked on "System - Einstellungen - Tastenkombinationen"
sorry I don't know how it is called in English. And changed the Entry "Das Panelmenü anzeigen" to F13

== The Brightness Buttons ==

When I wanted to control the brightness, I was not able to change it with {{key|Fn}}{{key|End}}.

So I did the Workaround menitioned here [http://thinkwiki.org/wiki/Problem_with_LCD_brightness_buttons#Workaround for Fedora Core 6 Users].
After this I was able to change the brightness with {{key|Fn}}{{key|Home}} and {{key|Fn}}{{key|End}}, but I don't have the OSD anymore.

UPDATE: You don't need to do this since kernel version 2.6.22 on Ubuntu

== The Fingerprint Reader ==

Do the steps which are described in [http://www.thinkwiki.org/wiki/Installing_Ubuntu_6.10_%28Edgy_Eft%29_on_a_ThinkPad_T60#The_Fingerprint_Reader Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60] until you get to the Point where Keithvassallo says:
"Phew. Now, to make applications actually use the fingerprint reader."

I have done the following things instead of his version:

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

Change the file as following:

<pre>
#%PAM-1.0
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
auth requisite pam_nologin.so
auth required pam_env.so
@include common-auth
@include common-account
session required pam_limits.so
@include common-session
@include common-password
</pre>

and:

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

Change this file as following:

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

With this changes you have the advantage, that you are now able to login to Gnome or KDE whitout entering your password. But if you cancel the "Fingerprint Login", you are still able to login whit your username/password combination.

After I was able to login to my desktop I was unsatisfied, because my Computer still wants to get passwords i.e. when I tried to open Synaptic or when I do any sudo actions.

So I tried to figure out how this sudo thing works. I did the following change to /etc/pam.d/sudo with:

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

<pre>
#%PAM-1.0

auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/ :0
password sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam :0
auth required pam_unix.so nillock_secure
@include common-account

</pre>

With this change I was able to open System Administration tasks with my fingerprint, but the ugly thing is, that you get no information to swipe your finger over the reader when you have switched to a console session with {{Key|Ctrl}}+{{Key|Alt}}+{{Key|F1}}. The fingerprint scanner software will appear at your running X session.

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-10-10T08:16:15Z

Dirk: /* After The Kernel Update */

== My Thinkpad ==
<pre>
Lenovo Thinkpad R60 9461 HRG
Intel Core2Duo (Merom) 1.83 CPU
120 GB SATA Hitachi HTS54161 Harddisk
2 GB RAM
ATI Mobility X1400
</pre>

Originally equipped with a preinstalled MS Windows Vista Business. So the Harddisk was parted into two Partitions.

1. The Rescue & Recovery Partition

2. The preinstalled Windows Vista Partition

And as the parcel with my new Thinkpad arrived I was surprized, that there was a Windows Vista DVD (only 32 Bit Version) with it.
So I tried Vista - but I was a little bit shocked by it's performance. I never thought that a new computer could take so much time to boot up completely.

I decided to do a clean install of Vista, but I want to have Windows XP and Ubuntu Feisty on the Harddisk too.

== New Installation ==

I wanted to use all Space of the Harddisk, so I decided to kill the Rescue & and Recovery Partition, but to have the chance to go back to the factory default state I ordered Recovery DVD's at the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4HWSE3#Lenovo Support Call Center for Germany].
They shipped the 3 DVD's to me - free of charge - but I think it's only free if your Thinkpad is still in the warranty. I don't know exactly.

Then I created 2 Partitions on my Harddisk, 64 GB for Vista, 20 GB for XP, so 29 GB left free for Linux.

I installed Vista and XP and all the Thinkpad Stuff for each system.

When this was finished I took a Ubuntu Feisty Fawn installation CD and boot my Notebook with it. I created a 4 GB linux-swap partition and a 25 GB root / partition.

Because I want to boot my Ubuntu with the Windows Vista Boot Loader, I decided to install Grub to /dev/sda4 which is my Linux root partition.

The installation of Ubuntu Feisty Fawn works fine, NO PROBLEMS.

NOW I want to boot Linux from the Vista Bootloader, because I don't want to wait for two Bootscreens, and I wan't to have the chance to access the Repair Console of Windows Vista.

First I have to copy the Bootsector of my Linux Partition with:

<pre>
sudo dd if=/dev/sda4 of=/tmp/bootsect.lin bs=512 count=1
</pre>

Copy the bootsect.lin file to a USB-Stick or a writable partition which you can access from Windows Vista.

Now boot Windows Vista and copy the file bootsect.lin to your Systemdrive. In an Command Window with Administrator privileges type:

<pre>
copy bootsect.lin %SYSTEMDRIVE%\

bcdedit /create /d “Ubuntu” /application BOOTSECTOR
</pre>

You will receice an ID like this {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} from bcdedit. This is a uniqe identifier for your new Boot Entry in the Vista Bootloader. Now you will have to manipulate the entry with the following commands:

<pre>
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} device boot
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} PATH \bootsect.lin
bcdedit /displayorder {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} /addlast
bcdedit /timeout 10
</pre>

Then I booted my Ubuntu an did :

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

In this file I canged the entry the following entries:

<pre>
timeout 2
hiddenmenu
</pre>

So the computer starts up with the Windows Vista bootloader and gives me the option to start Windows XP, Windows Vista, Ubuntu and I have the option to do the repair tasks with the {{key|F8}} button on Vista if something fails. If I choose to boot Ubuntu I have the option to press the {{key|ESC}} key within the two seconds delay of the hidden Grub Menu. I.E. to boot another Linux Kernel.

== The tp_smapi modules ==

I did it under Feisty and, after the Upgrade under Gutsy, like described here : [http://www.thinkwiki.org/wiki/Tp_smapi#Installation TP SMAPI] in the Section "Installation on Ubuntu/Debian"
It worked, hdaps-gl and hdaps-pivot shows me now the movements of my Thinkpad. Like you can see here:

[[Image:Hdaps-pivot.png]]

[[Image:Hdaps-gl.png]]

== The Upgrade to Gutsy Gibbon ==

NO PROBLEMS. So why should I upgrade ?

OK I really wanted to get hdapsd (Harddisk Active Protection) to work. I tried a lot of things with Feisty, but I didn't get it going. And after a lot of seach through the Internet I found out that Gutsy Gibbon, the next Release of Ubuntu should have the Package for hdapsd on board.
SO I decided to upgrade to Gutsy - with the knowledge that it is still in Beta Stadium.

Upgrading Ubuntu is really simple, you only have to do the following steps:

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

Search all feisty entries and change them to gutsy. Save and Close the file.

Do:

{{cmduser| sudo apt-get update}}
{{cmduser| sudo apt-get upgrade}}

Go and drink a cup of Tea or Coffee. When you are back you have a message, that you should reboot your System, to get all packages active. So do it.

After the reboot I installed the hdapsd package and I tried to activate the Harddisk Protection with:

{{cmduser| sudo hdapsd -d sda -s 14 -a -v}}

But I still get the message "open(protect_file): No such file or directory". ---- The Same Message that I get in Feisty before I did the Upgrade. So I banged my head on the table and noticed that I'm not tough enough to get this thing working. Maybe someone else.

I decided to get the other things to work.

UPDATE: After some days I tried to get hdapsd to work, again !

== The hdapsd - Deamon (IBM Active Disk Protection) ==

Because I never had compiled or patched a kernel under Ubuntu I had to find out how this works ! After a lot of search in the Internet, the Ubuntu Help and at Thinkwiki.org I found the (hopefully) correct way to do it.

The best information I found was this :
[http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.04_on_a_ThinkPad_T43#Active_Protection_System_.28acceleration_monitor.29|Installing Ubuntu 7.04 on a ThinkPad T43] in section "Disk protection"

Here is what I did to get it to work:

1. Make sure that you have the required packages, with:

{{cmduser|sudo apt-get install build-essential fakeroot kernel-package libncurses5-dev wget bzip2 linux-source}}

2. Get the correct kernel patch for your running kernel from here : [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch_.28apply_using_.27patch_-p1_-l_.3C_hdaps_xx.patch.27.29| HDAPS] section "8.1.1 Kernel patch (apply using 'patch -p1 -l < hdaps_xx.patch')"

After all my experiences I was not sure that there was a patch available for my Gutsy-kernel (2.6.22-7-generic), but I still had my old kernel on the disk. So I booted up the old one (2.6.20-16-generic). Check the running kernel with:

{{cmduser|uname -r}}

You should see something like: 2.6.20-7-generic

Now change to /usr/src and look that the sources for the running kernel are there with:

{{cmduser|cd /usr/src}}
{{cmduser|ls -d linux-source*}}

You should see a file with the name "linux-source-2.6.20.tar.bz2" wich includes the packed kernel sources. You have to extract it, so do:

{{cmduser|sudo su}}
{{cmdroot|tar xvfj linux-source-2.6.20.tar.bz2}}

Now you have the kernel sources in the /usr/src/linux-source-2.6.20 directory. Take a look if there is a link from /usr/src/linux to an other kernel source directory (It's maybe there if you tried to compile a kernel some time before).

{{cmdroot|ls -l linux}}

If you see that linux is linked to an other source than your running kernel remove the link and create a new one with:

{{cmdroot|rm linux}}
{{cmdroot|ln -s /usr/src/linux-source-2.6.20 linux}}

Change to the source directory and patch the kernel with this:

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|patch -p1 -l < /home/dirk/993-001.bin}}

The file "993-001.bin" is the kernel patch for the 2.6.20 and 2.6.21 kernels, I downloaded it here : [http://article.gmane.org/gmane.linux.drivers.hdaps.devel/993]

After the patchwork I did this :

{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --append-to-version=.hdapscustom kernel_image --initrd binary

This would take its time, so go and clean up your house ;-)
{{HELP|I think the last command (with --append-to-version was an error ! I need help from an specialist in kernel compiling. Please read ahead at the next section "The hdapsd - Deamon (next try)". }}
After your house is clean you can do :

{{cmdroot|cd /usr/src}}
{{cmdroot|ls -l linux*.deb}}

You should see some newly builded Debian Pakage files. Install them with:

{{cmdroot|dpkg -i linux-headers-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-doc-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-image-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-manual-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-source-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}

After the installation you should reboot your computer, when Grub comes up make sure that you select your newly builded kernel.
Check it with:

{{cmduser|uname -r}}

You should see this "2.6.20.3-ubuntu1.hdapscustom". But now you have the Problem, that you have to recompile the tp_smapi driver.

{{cmduser|cd tp_smapi-0.31}}
$ sudo make install HDAPS=1
{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdaps}}

After :

<pre>
$ dmesg | grep hdaps
</pre>

You should see something like this:

[ 893.752000] hdaps: initial mode latch is 0x05
[ 893.752000] hdaps: setting ec_rate=250, filter_order=2
[ 893.752000] hdaps: fake_data_mode set to 0
[ 893.756000] hdaps: device successfully initialized.
[ 893.756000] input: hdaps as /class/input/input10
[ 893.756000] hdaps: driver successfully loaded.

Now we are ready to try out the hdapsd Deamon which is included in the Gutsy repositories, if you are using Feisty you have to compile it yourself like described here: [http://www.thinkwiki.org/wiki/How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS].

{{cmdroot|sudo hdapsd -d sda -s 12 -a -v}}

Should show this:

[[Image:hdapsd.png]]

If you load it with :

{{cmdroot|sudo hdapsd -d sda -s 12 -a}}

You get nothing until you move your Thinkpad, then you see:

Fri Jul 13 12:30:42 2007: parking
Fri Jul 13 12:30:43 2007: un-parking
Fri Jul 13 12:30:44 2007: parking
Fri Jul 13 12:30:45 2007: un-parking

Now, after I have a working hdaps-deamon I want it to be started at boot time. Because I have upgraded to Gutsy and installed the hdapsd - Package I have a script called /etc/default/hdapsd. Here I have to change some things. HINT: Remember that you still need the /etc/init.d/hdapsd file if you try this on Feisty and maybe you have to do:

{{cmduser|sudo update-rc.d hdapsd defaults}}

to create the init links for the hdapsd init script. My links was already there. My /etc/default/hdapsd script now looks like this:

<pre>
# hdapsd default file

# start hdapsd at boottime?
START="yes"

# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
DISK="sda"

# sensitivity
SENSITIVITY=12

# other options to pass to hdapsd.
# the -d $DISK, -s $SENSITIVITY, -b and -p $PIDFILE options are always passed.
OPTIONS="-a"

</pre>

Now I could use the gnome-hdaps-applet with the following comands:

{{cmduser|mkdir gnome-hdaps-applet}}
{{cmduser|cd gnome-hdaps-applet}}
{{cmduser|wget http://www.zen24593.zen.co.uk/hdaps/gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|tar -xzf gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|sudo apt-get install libpanel-applet2-dev}}
{{cmduser|gcc $(pkg-config --cflags --libs libpanelapplet-2.0) -o gnome-hdaps-applet gnome-hdaps-applet.c}}
{{cmduser|sudo cp gnome-hdaps-applet /usr/bin/}}
{{cmduser|sudo mkdir /usr/share/pixmaps/gnome-hdaps-applet/}}
{{cmduser|sudo cp *.png /usr/share/pixmaps/gnome-hdaps-applet/}}
$ sudo cp GNOME_HDAPS_StatusApplet.server /usr/lib/bonobo/servers/

Now after a restart of the Gnome Session I could find a "HDAPS Status" applet in the "Add to Panel" dialog. I added it, and when I move the Thinkpad it shows me the "Pause" [[Image:Hdaps-paused-small.png]] Symbol, otherwise it shows "Play" [[Image:Hdaps-running-small.png]].

So far so good !!! After I got this running I tried the same steps with the normal Gutsy Kernel (2.6.22-7-generic) on the same way, and it worked ! To my surprise with the same kernel patch.

The only Problem that I now have is that I cannot use restricted modules with my new kernels. Now I have to figure out how to compile restricted modules agains selfmade kernels.

{{HELP| }}

== The hdapsd - Deamon (next try) ==

I am not satisfied with the above result, because I cannot use the accelerated xorg-fglrx driver for my ATI Graphics Card and I cannot use my wireless Intel card ipw3945 driver. And the Ubuntu restricted-manager is not working. PLEASE can someone help me to compile a Ubuntu kernel in the correct way, so that I can use the whole hardware ?

I have done a - I think really ugly hack - to get the restricted-manager working :

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|cp /boot/config-2.6.20-16-generic /lib/modules/2.6.20-16-generic/.config}}
{{cmdroot|gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -16-generic".
Then I compiled the kernel again with:

{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I moved my modules with :

{{cmdroot|mv /lib/modules/2.6.20-16-generic /lib/modules/2.6.20-16-generic.orginal}}

And installed the kernel with:

{{cmdroot|dpkg -i linux-image-2.6.20-16-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers as described above.
Finally I copied the ipw3945.ucode with

{{cmdroot|cp /lib/firmware/2.6.22-7-generic/ipw3945.ucode /lib/firmware/2.6.20-16-generic/ipw3945.ucode}}

My wireless-card is working now !
My ATI Card cannot be configured with restricted-manager!

{{HELP|Please can someone who is conform in compiling Ubuntu kernels and restricted modules help me to do it in the correct way ! And can someone recheck the things described above, because I am not sure about all things that I have written here.
}}

After some days Ubuntu updated the kernel to version 2.6.22-9-generic, so I need to do the steps described above again, with "EXTRAVERSION = -9-generic". But now my wireless card and my grapics card did not work. The restricted-manager crashes when I start it.
So I downloaded the packages ipw3945-1.2.1.tgz and ati-driver-installer-8.39.4-x86.x86_64.run.

== The Wireless Card ==

First I extracted and installed the Intel Pro Wireless Package:

{{cmduser|tar xzvf ipw3945-1.2.1.tgz}}
{{cmduser|cd ipw3945-1.2.1}}
{{cmduser|make}}
{{cmduser|sudo make install}}

After this I could do :

{{cmduser|sudo modprobe ipw3945}}

The module was loaded, and i was able to use my wireless card now.

== The Graphics Card ==

For my Radeon Mobility X1400 I did the following steps:

{{cmduser|sudo apt get update}}
{{cmduser|sudo apt-get install module-assistant build-essential fakeroot dh-make debhelper debconf libstdc++5}}

Created a Debian Package with:

{{cmduser|sudo bash ati-driver-installer-8.39.4-x86.x86_64.run --buildpkg Ubuntu/gutsy}}

And blacklisted the old fglrx module with:

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

I added "fglrx" to the line with "DISABLED_MODULES". Then I installed the created Debian Packages with:

{{cmduser|sudo dpkg -i xorg-driver-fglrx_8.39.4-1_i386.deb fglrx-kernel-source_8.39.4-1_i386.deb fglrx-amdcccle_8.39.4-1_i386.deb}}

Then I compiled the kernel Modules:

{{cmduser|sudo module-assistant prepare}}
{{cmduser|sudo module-assistant update}}
{{cmduser|sudo module-assistant build fglrx}}
{{cmduser|sudo module-assistant install fglrx}}
{{cmduser|sudo depmod -a}}

The helpful informations for this was found at http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide.

After this steps my wifi-card and my graphics-card was working and restricted-manager was not crashing when I tried to start it.

== After The Kernel Update ==

On 9.October 2007 Ubuntu released the Kernelpackage linux-image-2.6.22-14-generic and I installed it. So here is what I have done to get it working:

{{cmduser|sudo apt-get install linux-headers-generic}}
{{cmduser|sudo ln -s /usr/src/linux-source-2.6.22 /lib/modules/2.6.22-14-generic/source}}
{{cmduser|sudo cd /usr/src/linux}}
{{cmduser|sudo make clean}}
{{cmduser|sudo cp /boot/config-2.6.22-14-generic .config}}
{{cmduser|sudo cp /boot/config-2.6.22-14-generic /lib/modules/2.6.22-14-generic/.config}}
{{cmduser|sudo gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -14-generic".

{{cmduser|sudo gedit .config}}

In the .config file I changed the entry " # CONFIG_SND_HDA_INTEL is not set " to " CONFIG_SND_HDA_INTEL=m ". This was needed to compile the module for my sound card.

Then I compiled the kernel again with:

{{cmduser|sudo make oldconfig}}
{{cmduser|sudo fakeroot make-kpkg clean}}
$ sudo fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I copied my modules with :

{{cmduser|sudo cp -R /lib/modules/2.6.22-14-generic /lib/modules/2.6.22-14-generic.orginal}}

And installed the kernel with:

{{cmduser|sudo dpkg -r linux-headers-generic linux-headers-2.6.22-14-generic}}
{{cmduser|cd ..}}
{{cmduser|sudo dpkg -i linux-image-2.6.22-14-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers with:

{{cmduser|cd /home/dirk/tp_smapi-0.32}}
$ sudo make install HDAPS=1

After this I load the modules with:

{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdaps}}

And test it with:

{{cmduser|hdaps-gl}}

Now I had to get my sound-card working. The module from ubuntu is not working, I don't know why. So I did this:

{{cmduser|sudo mv /lib/modules/2.6.22-14-generic/ubuntu/media/snd-hda-intel/snd-hda-intel.ko
/lib/modules/2.6.22-14-generic/ubuntu/media/snd-hda-intel/snd-hda-intel.ko.orginal}}
{{cmduser|sudo cp /usr/src/linux-source-2.6.22/sound/pci/hda/snd-hda-intel.ko
/lib/modules/2.6.22-14-generic/ubuntu/media/snd-hda-intel/snd/hda-intel.ko}}

After this I load the modules with:

{{cmduser|sudo modprobe snd-hda-intel}}

== The Browser Buttons ==

I wanted to use the Browser Forward & Backward Buttons within Firefox. After the upgrade my Firefox had version 2.0.0.4

I did :

{{cmduser| gedit ~/.Xmodmap}}

and added the following lines :

keycode 234 = F19

keycode 233 = F20

I saved and closed the file. HINT: You have to re-login to Gnome to get the .Xmodmap file active.

Then I did the things described in [http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work#Firefox How to get special keys to work].

For the Windows Key I added "keycode 115 = F13" to my .Xmodmap File, then I klicked on "System - Einstellungen - Tastenkombinationen"
sorry I don't know how it is called in English. And changed the Entry "Das Panelmenü anzeigen" to F13

== The Brightness Buttons ==

When I wanted to control the brightness, I was not able to change it with {{key|Fn}}{{key|End}}.

So I did the Workaround menitioned here [http://thinkwiki.org/wiki/Problem_with_LCD_brightness_buttons#Workaround for Fedora Core 6 Users].
After this I was able to change the brightness with {{key|Fn}}{{key|Home}} and {{key|Fn}}{{key|End}}, but I don't have the OSD anymore.

UPDATE: You don't need to do this since kernel version 2.6.22 on Ubuntu

== The Fingerprint Reader ==

Do the steps which are described in [http://www.thinkwiki.org/wiki/Installing_Ubuntu_6.10_%28Edgy_Eft%29_on_a_ThinkPad_T60#The_Fingerprint_Reader Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60] until you get to the Point where Keithvassallo says:
"Phew. Now, to make applications actually use the fingerprint reader."

I have done the following things instead of his version:

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

Change the file as following:

<pre>
#%PAM-1.0
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
auth requisite pam_nologin.so
auth required pam_env.so
@include common-auth
@include common-account
session required pam_limits.so
@include common-session
@include common-password
</pre>

and:

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

Change this file as following:

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

With this changes you have the advantage, that you are now able to login to Gnome or KDE whitout entering your password. But if you cancel the "Fingerprint Login", you are still able to login whit your username/password combination.

After I was able to login to my desktop I was unsatisfied, because my Computer still wants to get passwords i.e. when I tried to open Synaptic or when I do any sudo actions.

So I tried to figure out how this sudo thing works. I did the following change to /etc/pam.d/sudo with:

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

<pre>
#%PAM-1.0

auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/ :0
password sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam :0
auth required pam_unix.so nillock_secure
@include common-account

</pre>

With this change I was able to open System Administration tasks with my fingerprint, but the ugly thing is, that you get no information to swipe your finger over the reader when you have switched to a console session with {{Key|Ctrl}}+{{Key|Alt}}+{{Key|F1}}. The fingerprint scanner software will appear at your running X session.

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-10-10T08:15:24Z

Dirk: /* After The Kernel Update */

== My Thinkpad ==
<pre>
Lenovo Thinkpad R60 9461 HRG
Intel Core2Duo (Merom) 1.83 CPU
120 GB SATA Hitachi HTS54161 Harddisk
2 GB RAM
ATI Mobility X1400
</pre>

Originally equipped with a preinstalled MS Windows Vista Business. So the Harddisk was parted into two Partitions.

1. The Rescue & Recovery Partition

2. The preinstalled Windows Vista Partition

And as the parcel with my new Thinkpad arrived I was surprized, that there was a Windows Vista DVD (only 32 Bit Version) with it.
So I tried Vista - but I was a little bit shocked by it's performance. I never thought that a new computer could take so much time to boot up completely.

I decided to do a clean install of Vista, but I want to have Windows XP and Ubuntu Feisty on the Harddisk too.

== New Installation ==

I wanted to use all Space of the Harddisk, so I decided to kill the Rescue & and Recovery Partition, but to have the chance to go back to the factory default state I ordered Recovery DVD's at the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4HWSE3#Lenovo Support Call Center for Germany].
They shipped the 3 DVD's to me - free of charge - but I think it's only free if your Thinkpad is still in the warranty. I don't know exactly.

Then I created 2 Partitions on my Harddisk, 64 GB for Vista, 20 GB for XP, so 29 GB left free for Linux.

I installed Vista and XP and all the Thinkpad Stuff for each system.

When this was finished I took a Ubuntu Feisty Fawn installation CD and boot my Notebook with it. I created a 4 GB linux-swap partition and a 25 GB root / partition.

Because I want to boot my Ubuntu with the Windows Vista Boot Loader, I decided to install Grub to /dev/sda4 which is my Linux root partition.

The installation of Ubuntu Feisty Fawn works fine, NO PROBLEMS.

NOW I want to boot Linux from the Vista Bootloader, because I don't want to wait for two Bootscreens, and I wan't to have the chance to access the Repair Console of Windows Vista.

First I have to copy the Bootsector of my Linux Partition with:

<pre>
sudo dd if=/dev/sda4 of=/tmp/bootsect.lin bs=512 count=1
</pre>

Copy the bootsect.lin file to a USB-Stick or a writable partition which you can access from Windows Vista.

Now boot Windows Vista and copy the file bootsect.lin to your Systemdrive. In an Command Window with Administrator privileges type:

<pre>
copy bootsect.lin %SYSTEMDRIVE%\

bcdedit /create /d “Ubuntu” /application BOOTSECTOR
</pre>

You will receice an ID like this {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} from bcdedit. This is a uniqe identifier for your new Boot Entry in the Vista Bootloader. Now you will have to manipulate the entry with the following commands:

<pre>
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} device boot
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} PATH \bootsect.lin
bcdedit /displayorder {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} /addlast
bcdedit /timeout 10
</pre>

Then I booted my Ubuntu an did :

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

In this file I canged the entry the following entries:

<pre>
timeout 2
hiddenmenu
</pre>

So the computer starts up with the Windows Vista bootloader and gives me the option to start Windows XP, Windows Vista, Ubuntu and I have the option to do the repair tasks with the {{key|F8}} button on Vista if something fails. If I choose to boot Ubuntu I have the option to press the {{key|ESC}} key within the two seconds delay of the hidden Grub Menu. I.E. to boot another Linux Kernel.

== The tp_smapi modules ==

I did it under Feisty and, after the Upgrade under Gutsy, like described here : [http://www.thinkwiki.org/wiki/Tp_smapi#Installation TP SMAPI] in the Section "Installation on Ubuntu/Debian"
It worked, hdaps-gl and hdaps-pivot shows me now the movements of my Thinkpad. Like you can see here:

[[Image:Hdaps-pivot.png]]

[[Image:Hdaps-gl.png]]

== The Upgrade to Gutsy Gibbon ==

NO PROBLEMS. So why should I upgrade ?

OK I really wanted to get hdapsd (Harddisk Active Protection) to work. I tried a lot of things with Feisty, but I didn't get it going. And after a lot of seach through the Internet I found out that Gutsy Gibbon, the next Release of Ubuntu should have the Package for hdapsd on board.
SO I decided to upgrade to Gutsy - with the knowledge that it is still in Beta Stadium.

Upgrading Ubuntu is really simple, you only have to do the following steps:

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

Search all feisty entries and change them to gutsy. Save and Close the file.

Do:

{{cmduser| sudo apt-get update}}
{{cmduser| sudo apt-get upgrade}}

Go and drink a cup of Tea or Coffee. When you are back you have a message, that you should reboot your System, to get all packages active. So do it.

After the reboot I installed the hdapsd package and I tried to activate the Harddisk Protection with:

{{cmduser| sudo hdapsd -d sda -s 14 -a -v}}

But I still get the message "open(protect_file): No such file or directory". ---- The Same Message that I get in Feisty before I did the Upgrade. So I banged my head on the table and noticed that I'm not tough enough to get this thing working. Maybe someone else.

I decided to get the other things to work.

UPDATE: After some days I tried to get hdapsd to work, again !

== The hdapsd - Deamon (IBM Active Disk Protection) ==

Because I never had compiled or patched a kernel under Ubuntu I had to find out how this works ! After a lot of search in the Internet, the Ubuntu Help and at Thinkwiki.org I found the (hopefully) correct way to do it.

The best information I found was this :
[http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.04_on_a_ThinkPad_T43#Active_Protection_System_.28acceleration_monitor.29|Installing Ubuntu 7.04 on a ThinkPad T43] in section "Disk protection"

Here is what I did to get it to work:

1. Make sure that you have the required packages, with:

{{cmduser|sudo apt-get install build-essential fakeroot kernel-package libncurses5-dev wget bzip2 linux-source}}

2. Get the correct kernel patch for your running kernel from here : [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch_.28apply_using_.27patch_-p1_-l_.3C_hdaps_xx.patch.27.29| HDAPS] section "8.1.1 Kernel patch (apply using 'patch -p1 -l < hdaps_xx.patch')"

After all my experiences I was not sure that there was a patch available for my Gutsy-kernel (2.6.22-7-generic), but I still had my old kernel on the disk. So I booted up the old one (2.6.20-16-generic). Check the running kernel with:

{{cmduser|uname -r}}

You should see something like: 2.6.20-7-generic

Now change to /usr/src and look that the sources for the running kernel are there with:

{{cmduser|cd /usr/src}}
{{cmduser|ls -d linux-source*}}

You should see a file with the name "linux-source-2.6.20.tar.bz2" wich includes the packed kernel sources. You have to extract it, so do:

{{cmduser|sudo su}}
{{cmdroot|tar xvfj linux-source-2.6.20.tar.bz2}}

Now you have the kernel sources in the /usr/src/linux-source-2.6.20 directory. Take a look if there is a link from /usr/src/linux to an other kernel source directory (It's maybe there if you tried to compile a kernel some time before).

{{cmdroot|ls -l linux}}

If you see that linux is linked to an other source than your running kernel remove the link and create a new one with:

{{cmdroot|rm linux}}
{{cmdroot|ln -s /usr/src/linux-source-2.6.20 linux}}

Change to the source directory and patch the kernel with this:

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|patch -p1 -l < /home/dirk/993-001.bin}}

The file "993-001.bin" is the kernel patch for the 2.6.20 and 2.6.21 kernels, I downloaded it here : [http://article.gmane.org/gmane.linux.drivers.hdaps.devel/993]

After the patchwork I did this :

{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --append-to-version=.hdapscustom kernel_image --initrd binary

This would take its time, so go and clean up your house ;-)
{{HELP|I think the last command (with --append-to-version was an error ! I need help from an specialist in kernel compiling. Please read ahead at the next section "The hdapsd - Deamon (next try)". }}
After your house is clean you can do :

{{cmdroot|cd /usr/src}}
{{cmdroot|ls -l linux*.deb}}

You should see some newly builded Debian Pakage files. Install them with:

{{cmdroot|dpkg -i linux-headers-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-doc-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-image-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-manual-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-source-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}

After the installation you should reboot your computer, when Grub comes up make sure that you select your newly builded kernel.
Check it with:

{{cmduser|uname -r}}

You should see this "2.6.20.3-ubuntu1.hdapscustom". But now you have the Problem, that you have to recompile the tp_smapi driver.

{{cmduser|cd tp_smapi-0.31}}
$ sudo make install HDAPS=1
{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdaps}}

After :

<pre>
$ dmesg | grep hdaps
</pre>

You should see something like this:

[ 893.752000] hdaps: initial mode latch is 0x05
[ 893.752000] hdaps: setting ec_rate=250, filter_order=2
[ 893.752000] hdaps: fake_data_mode set to 0
[ 893.756000] hdaps: device successfully initialized.
[ 893.756000] input: hdaps as /class/input/input10
[ 893.756000] hdaps: driver successfully loaded.

Now we are ready to try out the hdapsd Deamon which is included in the Gutsy repositories, if you are using Feisty you have to compile it yourself like described here: [http://www.thinkwiki.org/wiki/How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS].

{{cmdroot|sudo hdapsd -d sda -s 12 -a -v}}

Should show this:

[[Image:hdapsd.png]]

If you load it with :

{{cmdroot|sudo hdapsd -d sda -s 12 -a}}

You get nothing until you move your Thinkpad, then you see:

Fri Jul 13 12:30:42 2007: parking
Fri Jul 13 12:30:43 2007: un-parking
Fri Jul 13 12:30:44 2007: parking
Fri Jul 13 12:30:45 2007: un-parking

Now, after I have a working hdaps-deamon I want it to be started at boot time. Because I have upgraded to Gutsy and installed the hdapsd - Package I have a script called /etc/default/hdapsd. Here I have to change some things. HINT: Remember that you still need the /etc/init.d/hdapsd file if you try this on Feisty and maybe you have to do:

{{cmduser|sudo update-rc.d hdapsd defaults}}

to create the init links for the hdapsd init script. My links was already there. My /etc/default/hdapsd script now looks like this:

<pre>
# hdapsd default file

# start hdapsd at boottime?
START="yes"

# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
DISK="sda"

# sensitivity
SENSITIVITY=12

# other options to pass to hdapsd.
# the -d $DISK, -s $SENSITIVITY, -b and -p $PIDFILE options are always passed.
OPTIONS="-a"

</pre>

Now I could use the gnome-hdaps-applet with the following comands:

{{cmduser|mkdir gnome-hdaps-applet}}
{{cmduser|cd gnome-hdaps-applet}}
{{cmduser|wget http://www.zen24593.zen.co.uk/hdaps/gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|tar -xzf gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|sudo apt-get install libpanel-applet2-dev}}
{{cmduser|gcc $(pkg-config --cflags --libs libpanelapplet-2.0) -o gnome-hdaps-applet gnome-hdaps-applet.c}}
{{cmduser|sudo cp gnome-hdaps-applet /usr/bin/}}
{{cmduser|sudo mkdir /usr/share/pixmaps/gnome-hdaps-applet/}}
{{cmduser|sudo cp *.png /usr/share/pixmaps/gnome-hdaps-applet/}}
$ sudo cp GNOME_HDAPS_StatusApplet.server /usr/lib/bonobo/servers/

Now after a restart of the Gnome Session I could find a "HDAPS Status" applet in the "Add to Panel" dialog. I added it, and when I move the Thinkpad it shows me the "Pause" [[Image:Hdaps-paused-small.png]] Symbol, otherwise it shows "Play" [[Image:Hdaps-running-small.png]].

So far so good !!! After I got this running I tried the same steps with the normal Gutsy Kernel (2.6.22-7-generic) on the same way, and it worked ! To my surprise with the same kernel patch.

The only Problem that I now have is that I cannot use restricted modules with my new kernels. Now I have to figure out how to compile restricted modules agains selfmade kernels.

{{HELP| }}

== The hdapsd - Deamon (next try) ==

I am not satisfied with the above result, because I cannot use the accelerated xorg-fglrx driver for my ATI Graphics Card and I cannot use my wireless Intel card ipw3945 driver. And the Ubuntu restricted-manager is not working. PLEASE can someone help me to compile a Ubuntu kernel in the correct way, so that I can use the whole hardware ?

I have done a - I think really ugly hack - to get the restricted-manager working :

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|cp /boot/config-2.6.20-16-generic /lib/modules/2.6.20-16-generic/.config}}
{{cmdroot|gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -16-generic".
Then I compiled the kernel again with:

{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I moved my modules with :

{{cmdroot|mv /lib/modules/2.6.20-16-generic /lib/modules/2.6.20-16-generic.orginal}}

And installed the kernel with:

{{cmdroot|dpkg -i linux-image-2.6.20-16-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers as described above.
Finally I copied the ipw3945.ucode with

{{cmdroot|cp /lib/firmware/2.6.22-7-generic/ipw3945.ucode /lib/firmware/2.6.20-16-generic/ipw3945.ucode}}

My wireless-card is working now !
My ATI Card cannot be configured with restricted-manager!

{{HELP|Please can someone who is conform in compiling Ubuntu kernels and restricted modules help me to do it in the correct way ! And can someone recheck the things described above, because I am not sure about all things that I have written here.
}}

After some days Ubuntu updated the kernel to version 2.6.22-9-generic, so I need to do the steps described above again, with "EXTRAVERSION = -9-generic". But now my wireless card and my grapics card did not work. The restricted-manager crashes when I start it.
So I downloaded the packages ipw3945-1.2.1.tgz and ati-driver-installer-8.39.4-x86.x86_64.run.

== The Wireless Card ==

First I extracted and installed the Intel Pro Wireless Package:

{{cmduser|tar xzvf ipw3945-1.2.1.tgz}}
{{cmduser|cd ipw3945-1.2.1}}
{{cmduser|make}}
{{cmduser|sudo make install}}

After this I could do :

{{cmduser|sudo modprobe ipw3945}}

The module was loaded, and i was able to use my wireless card now.

== The Graphics Card ==

For my Radeon Mobility X1400 I did the following steps:

{{cmduser|sudo apt get update}}
{{cmduser|sudo apt-get install module-assistant build-essential fakeroot dh-make debhelper debconf libstdc++5}}

Created a Debian Package with:

{{cmduser|sudo bash ati-driver-installer-8.39.4-x86.x86_64.run --buildpkg Ubuntu/gutsy}}

And blacklisted the old fglrx module with:

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

I added "fglrx" to the line with "DISABLED_MODULES". Then I installed the created Debian Packages with:

{{cmduser|sudo dpkg -i xorg-driver-fglrx_8.39.4-1_i386.deb fglrx-kernel-source_8.39.4-1_i386.deb fglrx-amdcccle_8.39.4-1_i386.deb}}

Then I compiled the kernel Modules:

{{cmduser|sudo module-assistant prepare}}
{{cmduser|sudo module-assistant update}}
{{cmduser|sudo module-assistant build fglrx}}
{{cmduser|sudo module-assistant install fglrx}}
{{cmduser|sudo depmod -a}}

The helpful informations for this was found at http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide.

After this steps my wifi-card and my graphics-card was working and restricted-manager was not crashing when I tried to start it.

== After The Kernel Update ==

On 9.October 2007 Ubuntu released the Kernelpackage linux-image-2.6.22-14-generic and I installed it. So here is what I have done to get it working:

{{cmduser|sudo apt-get install linux-headers-generic}}
{{cmduser|sudo ln -s /usr/src/linux-source-2.6.22 /lib/modules/2.6.22-14-generic/source}}
{{cmduser|sudo cd /usr/src/linux}}
{{cmduser|sudo make clean}}
{{cmduser|sudo cp /boot/config-2.6.22-14-generic .config}}
{{cmduser|sudo cp /boot/config-2.6.22-14-generic /lib/modules/2.6.22-14-generic/.config}}
{{cmduser|sudo gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -14-generic".

{{cmduser|sudo gedit .config}}

In the .config file I changed the entry " # CONFIG_SND_HDA_INTEL is not set " to " CONFIG_SND_HDA_INTEL=m ". This was needed to compile the module for my sound card.

Then I compiled the kernel again with:

{{cmduser|sudo make oldconfig}}
{{cmduser|sudo fakeroot make-kpkg clean}}
$ sudo fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I copied my modules with :

{{cmduser|sudo cp -R /lib/modules/2.6.22-14-generic /lib/modules/2.6.22-14-generic.orginal}}

And installed the kernel with:

{{cmduser|sudo dpkg -r linux-headers-generic linux-headers-2.6.22-14-generic}}
{{cmduser|cd ..}}
{{cmduser|sudo dpkg -i linux-image-2.6.22-14-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers with:

{{cmduser|cd /home/dirk/tp_smapi-0.32}}
$ sudo make install HDAPS=1

After this I load the modules with:

{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdaps}}

And test it with:

{{cmduser|hdaps-gl}}

Now I had to get my sound-card working. The module from ubuntu is not working, I don't know why. So I did this:

{{cmduser|sudo mv /lib/modules/2.6.22-14-generic/ubuntu/media/snd-hda-intel/snd-hda-intel.ko /lib/modules/2.6.22-14-generic/ubuntu/media/snd-hda-intel/snd-hda-intel.ko.orginal}}
{{cmduser|sudo cp /usr/src/linux-source-2.6.22/sound/pci/hda/snd-hda-intel.ko /lib/modules/2.6.22-14-generic/ubuntu/media/snd-hda-intel/snd/hda-intel.ko}}

After this I load the modules with:

{{cmduser|sudo modprobe snd-hda-intel}}

== The Browser Buttons ==

I wanted to use the Browser Forward & Backward Buttons within Firefox. After the upgrade my Firefox had version 2.0.0.4

I did :

{{cmduser| gedit ~/.Xmodmap}}

and added the following lines :

keycode 234 = F19

keycode 233 = F20

I saved and closed the file. HINT: You have to re-login to Gnome to get the .Xmodmap file active.

Then I did the things described in [http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work#Firefox How to get special keys to work].

For the Windows Key I added "keycode 115 = F13" to my .Xmodmap File, then I klicked on "System - Einstellungen - Tastenkombinationen"
sorry I don't know how it is called in English. And changed the Entry "Das Panelmenü anzeigen" to F13

== The Brightness Buttons ==

When I wanted to control the brightness, I was not able to change it with {{key|Fn}}{{key|End}}.

So I did the Workaround menitioned here [http://thinkwiki.org/wiki/Problem_with_LCD_brightness_buttons#Workaround for Fedora Core 6 Users].
After this I was able to change the brightness with {{key|Fn}}{{key|Home}} and {{key|Fn}}{{key|End}}, but I don't have the OSD anymore.

UPDATE: You don't need to do this since kernel version 2.6.22 on Ubuntu

== The Fingerprint Reader ==

Do the steps which are described in [http://www.thinkwiki.org/wiki/Installing_Ubuntu_6.10_%28Edgy_Eft%29_on_a_ThinkPad_T60#The_Fingerprint_Reader Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60] until you get to the Point where Keithvassallo says:
"Phew. Now, to make applications actually use the fingerprint reader."

I have done the following things instead of his version:

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

Change the file as following:

<pre>
#%PAM-1.0
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
auth requisite pam_nologin.so
auth required pam_env.so
@include common-auth
@include common-account
session required pam_limits.so
@include common-session
@include common-password
</pre>

and:

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

Change this file as following:

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

With this changes you have the advantage, that you are now able to login to Gnome or KDE whitout entering your password. But if you cancel the "Fingerprint Login", you are still able to login whit your username/password combination.

After I was able to login to my desktop I was unsatisfied, because my Computer still wants to get passwords i.e. when I tried to open Synaptic or when I do any sudo actions.

So I tried to figure out how this sudo thing works. I did the following change to /etc/pam.d/sudo with:

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

<pre>
#%PAM-1.0

auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/ :0
password sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam :0
auth required pam_unix.so nillock_secure
@include common-account

</pre>

With this change I was able to open System Administration tasks with my fingerprint, but the ugly thing is, that you get no information to swipe your finger over the reader when you have switched to a console session with {{Key|Ctrl}}+{{Key|Alt}}+{{Key|F1}}. The fingerprint scanner software will appear at your running X session.

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-10-10T08:09:37Z

Dirk: /* After The Kernel Update */

== My Thinkpad ==
<pre>
Lenovo Thinkpad R60 9461 HRG
Intel Core2Duo (Merom) 1.83 CPU
120 GB SATA Hitachi HTS54161 Harddisk
2 GB RAM
ATI Mobility X1400
</pre>

Originally equipped with a preinstalled MS Windows Vista Business. So the Harddisk was parted into two Partitions.

1. The Rescue & Recovery Partition

2. The preinstalled Windows Vista Partition

And as the parcel with my new Thinkpad arrived I was surprized, that there was a Windows Vista DVD (only 32 Bit Version) with it.
So I tried Vista - but I was a little bit shocked by it's performance. I never thought that a new computer could take so much time to boot up completely.

I decided to do a clean install of Vista, but I want to have Windows XP and Ubuntu Feisty on the Harddisk too.

== New Installation ==

I wanted to use all Space of the Harddisk, so I decided to kill the Rescue & and Recovery Partition, but to have the chance to go back to the factory default state I ordered Recovery DVD's at the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4HWSE3#Lenovo Support Call Center for Germany].
They shipped the 3 DVD's to me - free of charge - but I think it's only free if your Thinkpad is still in the warranty. I don't know exactly.

Then I created 2 Partitions on my Harddisk, 64 GB for Vista, 20 GB for XP, so 29 GB left free for Linux.

I installed Vista and XP and all the Thinkpad Stuff for each system.

When this was finished I took a Ubuntu Feisty Fawn installation CD and boot my Notebook with it. I created a 4 GB linux-swap partition and a 25 GB root / partition.

Because I want to boot my Ubuntu with the Windows Vista Boot Loader, I decided to install Grub to /dev/sda4 which is my Linux root partition.

The installation of Ubuntu Feisty Fawn works fine, NO PROBLEMS.

NOW I want to boot Linux from the Vista Bootloader, because I don't want to wait for two Bootscreens, and I wan't to have the chance to access the Repair Console of Windows Vista.

First I have to copy the Bootsector of my Linux Partition with:

<pre>
sudo dd if=/dev/sda4 of=/tmp/bootsect.lin bs=512 count=1
</pre>

Copy the bootsect.lin file to a USB-Stick or a writable partition which you can access from Windows Vista.

Now boot Windows Vista and copy the file bootsect.lin to your Systemdrive. In an Command Window with Administrator privileges type:

<pre>
copy bootsect.lin %SYSTEMDRIVE%\

bcdedit /create /d “Ubuntu” /application BOOTSECTOR
</pre>

You will receice an ID like this {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} from bcdedit. This is a uniqe identifier for your new Boot Entry in the Vista Bootloader. Now you will have to manipulate the entry with the following commands:

<pre>
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} device boot
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} PATH \bootsect.lin
bcdedit /displayorder {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} /addlast
bcdedit /timeout 10
</pre>

Then I booted my Ubuntu an did :

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

In this file I canged the entry the following entries:

<pre>
timeout 2
hiddenmenu
</pre>

So the computer starts up with the Windows Vista bootloader and gives me the option to start Windows XP, Windows Vista, Ubuntu and I have the option to do the repair tasks with the {{key|F8}} button on Vista if something fails. If I choose to boot Ubuntu I have the option to press the {{key|ESC}} key within the two seconds delay of the hidden Grub Menu. I.E. to boot another Linux Kernel.

== The tp_smapi modules ==

I did it under Feisty and, after the Upgrade under Gutsy, like described here : [http://www.thinkwiki.org/wiki/Tp_smapi#Installation TP SMAPI] in the Section "Installation on Ubuntu/Debian"
It worked, hdaps-gl and hdaps-pivot shows me now the movements of my Thinkpad. Like you can see here:

[[Image:Hdaps-pivot.png]]

[[Image:Hdaps-gl.png]]

== The Upgrade to Gutsy Gibbon ==

NO PROBLEMS. So why should I upgrade ?

OK I really wanted to get hdapsd (Harddisk Active Protection) to work. I tried a lot of things with Feisty, but I didn't get it going. And after a lot of seach through the Internet I found out that Gutsy Gibbon, the next Release of Ubuntu should have the Package for hdapsd on board.
SO I decided to upgrade to Gutsy - with the knowledge that it is still in Beta Stadium.

Upgrading Ubuntu is really simple, you only have to do the following steps:

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

Search all feisty entries and change them to gutsy. Save and Close the file.

Do:

{{cmduser| sudo apt-get update}}
{{cmduser| sudo apt-get upgrade}}

Go and drink a cup of Tea or Coffee. When you are back you have a message, that you should reboot your System, to get all packages active. So do it.

After the reboot I installed the hdapsd package and I tried to activate the Harddisk Protection with:

{{cmduser| sudo hdapsd -d sda -s 14 -a -v}}

But I still get the message "open(protect_file): No such file or directory". ---- The Same Message that I get in Feisty before I did the Upgrade. So I banged my head on the table and noticed that I'm not tough enough to get this thing working. Maybe someone else.

I decided to get the other things to work.

UPDATE: After some days I tried to get hdapsd to work, again !

== The hdapsd - Deamon (IBM Active Disk Protection) ==

Because I never had compiled or patched a kernel under Ubuntu I had to find out how this works ! After a lot of search in the Internet, the Ubuntu Help and at Thinkwiki.org I found the (hopefully) correct way to do it.

The best information I found was this :
[http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.04_on_a_ThinkPad_T43#Active_Protection_System_.28acceleration_monitor.29|Installing Ubuntu 7.04 on a ThinkPad T43] in section "Disk protection"

Here is what I did to get it to work:

1. Make sure that you have the required packages, with:

{{cmduser|sudo apt-get install build-essential fakeroot kernel-package libncurses5-dev wget bzip2 linux-source}}

2. Get the correct kernel patch for your running kernel from here : [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch_.28apply_using_.27patch_-p1_-l_.3C_hdaps_xx.patch.27.29| HDAPS] section "8.1.1 Kernel patch (apply using 'patch -p1 -l < hdaps_xx.patch')"

After all my experiences I was not sure that there was a patch available for my Gutsy-kernel (2.6.22-7-generic), but I still had my old kernel on the disk. So I booted up the old one (2.6.20-16-generic). Check the running kernel with:

{{cmduser|uname -r}}

You should see something like: 2.6.20-7-generic

Now change to /usr/src and look that the sources for the running kernel are there with:

{{cmduser|cd /usr/src}}
{{cmduser|ls -d linux-source*}}

You should see a file with the name "linux-source-2.6.20.tar.bz2" wich includes the packed kernel sources. You have to extract it, so do:

{{cmduser|sudo su}}
{{cmdroot|tar xvfj linux-source-2.6.20.tar.bz2}}

Now you have the kernel sources in the /usr/src/linux-source-2.6.20 directory. Take a look if there is a link from /usr/src/linux to an other kernel source directory (It's maybe there if you tried to compile a kernel some time before).

{{cmdroot|ls -l linux}}

If you see that linux is linked to an other source than your running kernel remove the link and create a new one with:

{{cmdroot|rm linux}}
{{cmdroot|ln -s /usr/src/linux-source-2.6.20 linux}}

Change to the source directory and patch the kernel with this:

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|patch -p1 -l < /home/dirk/993-001.bin}}

The file "993-001.bin" is the kernel patch for the 2.6.20 and 2.6.21 kernels, I downloaded it here : [http://article.gmane.org/gmane.linux.drivers.hdaps.devel/993]

After the patchwork I did this :

{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --append-to-version=.hdapscustom kernel_image --initrd binary

This would take its time, so go and clean up your house ;-)
{{HELP|I think the last command (with --append-to-version was an error ! I need help from an specialist in kernel compiling. Please read ahead at the next section "The hdapsd - Deamon (next try)". }}
After your house is clean you can do :

{{cmdroot|cd /usr/src}}
{{cmdroot|ls -l linux*.deb}}

You should see some newly builded Debian Pakage files. Install them with:

{{cmdroot|dpkg -i linux-headers-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-doc-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-image-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-manual-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-source-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}

After the installation you should reboot your computer, when Grub comes up make sure that you select your newly builded kernel.
Check it with:

{{cmduser|uname -r}}

You should see this "2.6.20.3-ubuntu1.hdapscustom". But now you have the Problem, that you have to recompile the tp_smapi driver.

{{cmduser|cd tp_smapi-0.31}}
$ sudo make install HDAPS=1
{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdaps}}

After :

<pre>
$ dmesg | grep hdaps
</pre>

You should see something like this:

[ 893.752000] hdaps: initial mode latch is 0x05
[ 893.752000] hdaps: setting ec_rate=250, filter_order=2
[ 893.752000] hdaps: fake_data_mode set to 0
[ 893.756000] hdaps: device successfully initialized.
[ 893.756000] input: hdaps as /class/input/input10
[ 893.756000] hdaps: driver successfully loaded.

Now we are ready to try out the hdapsd Deamon which is included in the Gutsy repositories, if you are using Feisty you have to compile it yourself like described here: [http://www.thinkwiki.org/wiki/How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS].

{{cmdroot|sudo hdapsd -d sda -s 12 -a -v}}

Should show this:

[[Image:hdapsd.png]]

If you load it with :

{{cmdroot|sudo hdapsd -d sda -s 12 -a}}

You get nothing until you move your Thinkpad, then you see:

Fri Jul 13 12:30:42 2007: parking
Fri Jul 13 12:30:43 2007: un-parking
Fri Jul 13 12:30:44 2007: parking
Fri Jul 13 12:30:45 2007: un-parking

Now, after I have a working hdaps-deamon I want it to be started at boot time. Because I have upgraded to Gutsy and installed the hdapsd - Package I have a script called /etc/default/hdapsd. Here I have to change some things. HINT: Remember that you still need the /etc/init.d/hdapsd file if you try this on Feisty and maybe you have to do:

{{cmduser|sudo update-rc.d hdapsd defaults}}

to create the init links for the hdapsd init script. My links was already there. My /etc/default/hdapsd script now looks like this:

<pre>
# hdapsd default file

# start hdapsd at boottime?
START="yes"

# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
DISK="sda"

# sensitivity
SENSITIVITY=12

# other options to pass to hdapsd.
# the -d $DISK, -s $SENSITIVITY, -b and -p $PIDFILE options are always passed.
OPTIONS="-a"

</pre>

Now I could use the gnome-hdaps-applet with the following comands:

{{cmduser|mkdir gnome-hdaps-applet}}
{{cmduser|cd gnome-hdaps-applet}}
{{cmduser|wget http://www.zen24593.zen.co.uk/hdaps/gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|tar -xzf gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|sudo apt-get install libpanel-applet2-dev}}
{{cmduser|gcc $(pkg-config --cflags --libs libpanelapplet-2.0) -o gnome-hdaps-applet gnome-hdaps-applet.c}}
{{cmduser|sudo cp gnome-hdaps-applet /usr/bin/}}
{{cmduser|sudo mkdir /usr/share/pixmaps/gnome-hdaps-applet/}}
{{cmduser|sudo cp *.png /usr/share/pixmaps/gnome-hdaps-applet/}}
$ sudo cp GNOME_HDAPS_StatusApplet.server /usr/lib/bonobo/servers/

Now after a restart of the Gnome Session I could find a "HDAPS Status" applet in the "Add to Panel" dialog. I added it, and when I move the Thinkpad it shows me the "Pause" [[Image:Hdaps-paused-small.png]] Symbol, otherwise it shows "Play" [[Image:Hdaps-running-small.png]].

So far so good !!! After I got this running I tried the same steps with the normal Gutsy Kernel (2.6.22-7-generic) on the same way, and it worked ! To my surprise with the same kernel patch.

The only Problem that I now have is that I cannot use restricted modules with my new kernels. Now I have to figure out how to compile restricted modules agains selfmade kernels.

{{HELP| }}

== The hdapsd - Deamon (next try) ==

I am not satisfied with the above result, because I cannot use the accelerated xorg-fglrx driver for my ATI Graphics Card and I cannot use my wireless Intel card ipw3945 driver. And the Ubuntu restricted-manager is not working. PLEASE can someone help me to compile a Ubuntu kernel in the correct way, so that I can use the whole hardware ?

I have done a - I think really ugly hack - to get the restricted-manager working :

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|cp /boot/config-2.6.20-16-generic /lib/modules/2.6.20-16-generic/.config}}
{{cmdroot|gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -16-generic".
Then I compiled the kernel again with:

{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I moved my modules with :

{{cmdroot|mv /lib/modules/2.6.20-16-generic /lib/modules/2.6.20-16-generic.orginal}}

And installed the kernel with:

{{cmdroot|dpkg -i linux-image-2.6.20-16-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers as described above.
Finally I copied the ipw3945.ucode with

{{cmdroot|cp /lib/firmware/2.6.22-7-generic/ipw3945.ucode /lib/firmware/2.6.20-16-generic/ipw3945.ucode}}

My wireless-card is working now !
My ATI Card cannot be configured with restricted-manager!

{{HELP|Please can someone who is conform in compiling Ubuntu kernels and restricted modules help me to do it in the correct way ! And can someone recheck the things described above, because I am not sure about all things that I have written here.
}}

After some days Ubuntu updated the kernel to version 2.6.22-9-generic, so I need to do the steps described above again, with "EXTRAVERSION = -9-generic". But now my wireless card and my grapics card did not work. The restricted-manager crashes when I start it.
So I downloaded the packages ipw3945-1.2.1.tgz and ati-driver-installer-8.39.4-x86.x86_64.run.

== The Wireless Card ==

First I extracted and installed the Intel Pro Wireless Package:

{{cmduser|tar xzvf ipw3945-1.2.1.tgz}}
{{cmduser|cd ipw3945-1.2.1}}
{{cmduser|make}}
{{cmduser|sudo make install}}

After this I could do :

{{cmduser|sudo modprobe ipw3945}}

The module was loaded, and i was able to use my wireless card now.

== The Graphics Card ==

For my Radeon Mobility X1400 I did the following steps:

{{cmduser|sudo apt get update}}
{{cmduser|sudo apt-get install module-assistant build-essential fakeroot dh-make debhelper debconf libstdc++5}}

Created a Debian Package with:

{{cmduser|sudo bash ati-driver-installer-8.39.4-x86.x86_64.run --buildpkg Ubuntu/gutsy}}

And blacklisted the old fglrx module with:

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

I added "fglrx" to the line with "DISABLED_MODULES". Then I installed the created Debian Packages with:

{{cmduser|sudo dpkg -i xorg-driver-fglrx_8.39.4-1_i386.deb fglrx-kernel-source_8.39.4-1_i386.deb fglrx-amdcccle_8.39.4-1_i386.deb}}

Then I compiled the kernel Modules:

{{cmduser|sudo module-assistant prepare}}
{{cmduser|sudo module-assistant update}}
{{cmduser|sudo module-assistant build fglrx}}
{{cmduser|sudo module-assistant install fglrx}}
{{cmduser|sudo depmod -a}}

The helpful informations for this was found at http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide.

After this steps my wifi-card and my graphics-card was working and restricted-manager was not crashing when I tried to start it.

== After The Kernel Update ==

On 9.October 2007 Ubuntu released the Kernelpackage linux-image-2.6.22-14-generic and I installed it. So here is what I have done to get it working:

{{cmduser|sudo apt-get install linux-headers-generic}}
{{cmduser|sudo ln -s /usr/src/linux-source-2.6.22 /lib/modules/2.6.22-14-generic/source}}
{{cmduser|sudo cd /usr/src/linux}}
{{cmduser|sudo make clean}}
{{cmduser|sudo cp /boot/config-2.6.22-14-generic .config}}
{{cmduser|sudo cp /boot/config-2.6.22-14-generic /lib/modules/2.6.22-14-generic/.config}}
{{cmduser|sudo gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -14-generic".

{{cmduser|sudo gedit .config}}

In the .config file I changed the entry " # CONFIG_SND_HDA_INTEL is not set " to " CONFIG_SND_HDA_INTEL=m ". This was needed to compile the module for my sound card.

Then I compiled the kernel again with:

{{cmduser|sudo make oldconfig}}
{{cmduser|sudo fakeroot make-kpkg clean}}
$ sudo fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I copied my modules with :

{{cmduser|sudo cp -R /lib/modules/2.6.22-14-generic /lib/modules/2.6.22-14-generic.orginal}}

And installed the kernel with:

{{cmduser|sudo dpkg -r linux-headers-generic linux-headers-2.6.22-14-generic}}
{{cmduser|cd ..}}
{{cmduser|sudo dpkg -i linux-image-2.6.22-14-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers with:

{{cmduser|cd /home/dirk/tp_smapi-0.32}}
$ sudo make install HDAPS=1

After this I load the modules with:

{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdaps}}

And test it with:

{{cmduser|hdaps-gl}}

Now I had to get my sound-card working. The module from ubuntu is not working, I don't know why. So I did this:

{{cmduser|sudo mv /lib/modules/2.6.22-14-generic/ubuntu/media/snd-hda-intel/snd-hda-intel.ko /lib/modules/2.6.22-14-generic/ubuntu/media/snd-hda-intel/snd-hda-intel.ko.orginal}}

== The Browser Buttons ==

I wanted to use the Browser Forward & Backward Buttons within Firefox. After the upgrade my Firefox had version 2.0.0.4

I did :

{{cmduser| gedit ~/.Xmodmap}}

and added the following lines :

keycode 234 = F19

keycode 233 = F20

I saved and closed the file. HINT: You have to re-login to Gnome to get the .Xmodmap file active.

Then I did the things described in [http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work#Firefox How to get special keys to work].

For the Windows Key I added "keycode 115 = F13" to my .Xmodmap File, then I klicked on "System - Einstellungen - Tastenkombinationen"
sorry I don't know how it is called in English. And changed the Entry "Das Panelmenü anzeigen" to F13

== The Brightness Buttons ==

When I wanted to control the brightness, I was not able to change it with {{key|Fn}}{{key|End}}.

So I did the Workaround menitioned here [http://thinkwiki.org/wiki/Problem_with_LCD_brightness_buttons#Workaround for Fedora Core 6 Users].
After this I was able to change the brightness with {{key|Fn}}{{key|Home}} and {{key|Fn}}{{key|End}}, but I don't have the OSD anymore.

UPDATE: You don't need to do this since kernel version 2.6.22 on Ubuntu

== The Fingerprint Reader ==

Do the steps which are described in [http://www.thinkwiki.org/wiki/Installing_Ubuntu_6.10_%28Edgy_Eft%29_on_a_ThinkPad_T60#The_Fingerprint_Reader Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60] until you get to the Point where Keithvassallo says:
"Phew. Now, to make applications actually use the fingerprint reader."

I have done the following things instead of his version:

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

Change the file as following:

<pre>
#%PAM-1.0
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
auth requisite pam_nologin.so
auth required pam_env.so
@include common-auth
@include common-account
session required pam_limits.so
@include common-session
@include common-password
</pre>

and:

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

Change this file as following:

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

With this changes you have the advantage, that you are now able to login to Gnome or KDE whitout entering your password. But if you cancel the "Fingerprint Login", you are still able to login whit your username/password combination.

After I was able to login to my desktop I was unsatisfied, because my Computer still wants to get passwords i.e. when I tried to open Synaptic or when I do any sudo actions.

So I tried to figure out how this sudo thing works. I did the following change to /etc/pam.d/sudo with:

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

<pre>
#%PAM-1.0

auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/ :0
password sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam :0
auth required pam_unix.so nillock_secure
@include common-account

</pre>

With this change I was able to open System Administration tasks with my fingerprint, but the ugly thing is, that you get no information to swipe your finger over the reader when you have switched to a console session with {{Key|Ctrl}}+{{Key|Alt}}+{{Key|F1}}. The fingerprint scanner software will appear at your running X session.

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-10-10T08:02:01Z

Dirk: /* After The Kernel Update */

== My Thinkpad ==
<pre>
Lenovo Thinkpad R60 9461 HRG
Intel Core2Duo (Merom) 1.83 CPU
120 GB SATA Hitachi HTS54161 Harddisk
2 GB RAM
ATI Mobility X1400
</pre>

Originally equipped with a preinstalled MS Windows Vista Business. So the Harddisk was parted into two Partitions.

1. The Rescue & Recovery Partition

2. The preinstalled Windows Vista Partition

And as the parcel with my new Thinkpad arrived I was surprized, that there was a Windows Vista DVD (only 32 Bit Version) with it.
So I tried Vista - but I was a little bit shocked by it's performance. I never thought that a new computer could take so much time to boot up completely.

I decided to do a clean install of Vista, but I want to have Windows XP and Ubuntu Feisty on the Harddisk too.

== New Installation ==

I wanted to use all Space of the Harddisk, so I decided to kill the Rescue & and Recovery Partition, but to have the chance to go back to the factory default state I ordered Recovery DVD's at the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4HWSE3#Lenovo Support Call Center for Germany].
They shipped the 3 DVD's to me - free of charge - but I think it's only free if your Thinkpad is still in the warranty. I don't know exactly.

Then I created 2 Partitions on my Harddisk, 64 GB for Vista, 20 GB for XP, so 29 GB left free for Linux.

I installed Vista and XP and all the Thinkpad Stuff for each system.

When this was finished I took a Ubuntu Feisty Fawn installation CD and boot my Notebook with it. I created a 4 GB linux-swap partition and a 25 GB root / partition.

Because I want to boot my Ubuntu with the Windows Vista Boot Loader, I decided to install Grub to /dev/sda4 which is my Linux root partition.

The installation of Ubuntu Feisty Fawn works fine, NO PROBLEMS.

NOW I want to boot Linux from the Vista Bootloader, because I don't want to wait for two Bootscreens, and I wan't to have the chance to access the Repair Console of Windows Vista.

First I have to copy the Bootsector of my Linux Partition with:

<pre>
sudo dd if=/dev/sda4 of=/tmp/bootsect.lin bs=512 count=1
</pre>

Copy the bootsect.lin file to a USB-Stick or a writable partition which you can access from Windows Vista.

Now boot Windows Vista and copy the file bootsect.lin to your Systemdrive. In an Command Window with Administrator privileges type:

<pre>
copy bootsect.lin %SYSTEMDRIVE%\

bcdedit /create /d “Ubuntu” /application BOOTSECTOR
</pre>

You will receice an ID like this {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} from bcdedit. This is a uniqe identifier for your new Boot Entry in the Vista Bootloader. Now you will have to manipulate the entry with the following commands:

<pre>
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} device boot
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} PATH \bootsect.lin
bcdedit /displayorder {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} /addlast
bcdedit /timeout 10
</pre>

Then I booted my Ubuntu an did :

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

In this file I canged the entry the following entries:

<pre>
timeout 2
hiddenmenu
</pre>

So the computer starts up with the Windows Vista bootloader and gives me the option to start Windows XP, Windows Vista, Ubuntu and I have the option to do the repair tasks with the {{key|F8}} button on Vista if something fails. If I choose to boot Ubuntu I have the option to press the {{key|ESC}} key within the two seconds delay of the hidden Grub Menu. I.E. to boot another Linux Kernel.

== The tp_smapi modules ==

I did it under Feisty and, after the Upgrade under Gutsy, like described here : [http://www.thinkwiki.org/wiki/Tp_smapi#Installation TP SMAPI] in the Section "Installation on Ubuntu/Debian"
It worked, hdaps-gl and hdaps-pivot shows me now the movements of my Thinkpad. Like you can see here:

[[Image:Hdaps-pivot.png]]

[[Image:Hdaps-gl.png]]

== The Upgrade to Gutsy Gibbon ==

NO PROBLEMS. So why should I upgrade ?

OK I really wanted to get hdapsd (Harddisk Active Protection) to work. I tried a lot of things with Feisty, but I didn't get it going. And after a lot of seach through the Internet I found out that Gutsy Gibbon, the next Release of Ubuntu should have the Package for hdapsd on board.
SO I decided to upgrade to Gutsy - with the knowledge that it is still in Beta Stadium.

Upgrading Ubuntu is really simple, you only have to do the following steps:

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

Search all feisty entries and change them to gutsy. Save and Close the file.

Do:

{{cmduser| sudo apt-get update}}
{{cmduser| sudo apt-get upgrade}}

Go and drink a cup of Tea or Coffee. When you are back you have a message, that you should reboot your System, to get all packages active. So do it.

After the reboot I installed the hdapsd package and I tried to activate the Harddisk Protection with:

{{cmduser| sudo hdapsd -d sda -s 14 -a -v}}

But I still get the message "open(protect_file): No such file or directory". ---- The Same Message that I get in Feisty before I did the Upgrade. So I banged my head on the table and noticed that I'm not tough enough to get this thing working. Maybe someone else.

I decided to get the other things to work.

UPDATE: After some days I tried to get hdapsd to work, again !

== The hdapsd - Deamon (IBM Active Disk Protection) ==

Because I never had compiled or patched a kernel under Ubuntu I had to find out how this works ! After a lot of search in the Internet, the Ubuntu Help and at Thinkwiki.org I found the (hopefully) correct way to do it.

The best information I found was this :
[http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.04_on_a_ThinkPad_T43#Active_Protection_System_.28acceleration_monitor.29|Installing Ubuntu 7.04 on a ThinkPad T43] in section "Disk protection"

Here is what I did to get it to work:

1. Make sure that you have the required packages, with:

{{cmduser|sudo apt-get install build-essential fakeroot kernel-package libncurses5-dev wget bzip2 linux-source}}

2. Get the correct kernel patch for your running kernel from here : [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch_.28apply_using_.27patch_-p1_-l_.3C_hdaps_xx.patch.27.29| HDAPS] section "8.1.1 Kernel patch (apply using 'patch -p1 -l < hdaps_xx.patch')"

After all my experiences I was not sure that there was a patch available for my Gutsy-kernel (2.6.22-7-generic), but I still had my old kernel on the disk. So I booted up the old one (2.6.20-16-generic). Check the running kernel with:

{{cmduser|uname -r}}

You should see something like: 2.6.20-7-generic

Now change to /usr/src and look that the sources for the running kernel are there with:

{{cmduser|cd /usr/src}}
{{cmduser|ls -d linux-source*}}

You should see a file with the name "linux-source-2.6.20.tar.bz2" wich includes the packed kernel sources. You have to extract it, so do:

{{cmduser|sudo su}}
{{cmdroot|tar xvfj linux-source-2.6.20.tar.bz2}}

Now you have the kernel sources in the /usr/src/linux-source-2.6.20 directory. Take a look if there is a link from /usr/src/linux to an other kernel source directory (It's maybe there if you tried to compile a kernel some time before).

{{cmdroot|ls -l linux}}

If you see that linux is linked to an other source than your running kernel remove the link and create a new one with:

{{cmdroot|rm linux}}
{{cmdroot|ln -s /usr/src/linux-source-2.6.20 linux}}

Change to the source directory and patch the kernel with this:

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|patch -p1 -l < /home/dirk/993-001.bin}}

The file "993-001.bin" is the kernel patch for the 2.6.20 and 2.6.21 kernels, I downloaded it here : [http://article.gmane.org/gmane.linux.drivers.hdaps.devel/993]

After the patchwork I did this :

{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --append-to-version=.hdapscustom kernel_image --initrd binary

This would take its time, so go and clean up your house ;-)
{{HELP|I think the last command (with --append-to-version was an error ! I need help from an specialist in kernel compiling. Please read ahead at the next section "The hdapsd - Deamon (next try)". }}
After your house is clean you can do :

{{cmdroot|cd /usr/src}}
{{cmdroot|ls -l linux*.deb}}

You should see some newly builded Debian Pakage files. Install them with:

{{cmdroot|dpkg -i linux-headers-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-doc-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-image-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-manual-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-source-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}

After the installation you should reboot your computer, when Grub comes up make sure that you select your newly builded kernel.
Check it with:

{{cmduser|uname -r}}

You should see this "2.6.20.3-ubuntu1.hdapscustom". But now you have the Problem, that you have to recompile the tp_smapi driver.

{{cmduser|cd tp_smapi-0.31}}
$ sudo make install HDAPS=1
{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdaps}}

After :

<pre>
$ dmesg | grep hdaps
</pre>

You should see something like this:

[ 893.752000] hdaps: initial mode latch is 0x05
[ 893.752000] hdaps: setting ec_rate=250, filter_order=2
[ 893.752000] hdaps: fake_data_mode set to 0
[ 893.756000] hdaps: device successfully initialized.
[ 893.756000] input: hdaps as /class/input/input10
[ 893.756000] hdaps: driver successfully loaded.

Now we are ready to try out the hdapsd Deamon which is included in the Gutsy repositories, if you are using Feisty you have to compile it yourself like described here: [http://www.thinkwiki.org/wiki/How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS].

{{cmdroot|sudo hdapsd -d sda -s 12 -a -v}}

Should show this:

[[Image:hdapsd.png]]

If you load it with :

{{cmdroot|sudo hdapsd -d sda -s 12 -a}}

You get nothing until you move your Thinkpad, then you see:

Fri Jul 13 12:30:42 2007: parking
Fri Jul 13 12:30:43 2007: un-parking
Fri Jul 13 12:30:44 2007: parking
Fri Jul 13 12:30:45 2007: un-parking

Now, after I have a working hdaps-deamon I want it to be started at boot time. Because I have upgraded to Gutsy and installed the hdapsd - Package I have a script called /etc/default/hdapsd. Here I have to change some things. HINT: Remember that you still need the /etc/init.d/hdapsd file if you try this on Feisty and maybe you have to do:

{{cmduser|sudo update-rc.d hdapsd defaults}}

to create the init links for the hdapsd init script. My links was already there. My /etc/default/hdapsd script now looks like this:

<pre>
# hdapsd default file

# start hdapsd at boottime?
START="yes"

# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
DISK="sda"

# sensitivity
SENSITIVITY=12

# other options to pass to hdapsd.
# the -d $DISK, -s $SENSITIVITY, -b and -p $PIDFILE options are always passed.
OPTIONS="-a"

</pre>

Now I could use the gnome-hdaps-applet with the following comands:

{{cmduser|mkdir gnome-hdaps-applet}}
{{cmduser|cd gnome-hdaps-applet}}
{{cmduser|wget http://www.zen24593.zen.co.uk/hdaps/gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|tar -xzf gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|sudo apt-get install libpanel-applet2-dev}}
{{cmduser|gcc $(pkg-config --cflags --libs libpanelapplet-2.0) -o gnome-hdaps-applet gnome-hdaps-applet.c}}
{{cmduser|sudo cp gnome-hdaps-applet /usr/bin/}}
{{cmduser|sudo mkdir /usr/share/pixmaps/gnome-hdaps-applet/}}
{{cmduser|sudo cp *.png /usr/share/pixmaps/gnome-hdaps-applet/}}
$ sudo cp GNOME_HDAPS_StatusApplet.server /usr/lib/bonobo/servers/

Now after a restart of the Gnome Session I could find a "HDAPS Status" applet in the "Add to Panel" dialog. I added it, and when I move the Thinkpad it shows me the "Pause" [[Image:Hdaps-paused-small.png]] Symbol, otherwise it shows "Play" [[Image:Hdaps-running-small.png]].

So far so good !!! After I got this running I tried the same steps with the normal Gutsy Kernel (2.6.22-7-generic) on the same way, and it worked ! To my surprise with the same kernel patch.

The only Problem that I now have is that I cannot use restricted modules with my new kernels. Now I have to figure out how to compile restricted modules agains selfmade kernels.

{{HELP| }}

== The hdapsd - Deamon (next try) ==

I am not satisfied with the above result, because I cannot use the accelerated xorg-fglrx driver for my ATI Graphics Card and I cannot use my wireless Intel card ipw3945 driver. And the Ubuntu restricted-manager is not working. PLEASE can someone help me to compile a Ubuntu kernel in the correct way, so that I can use the whole hardware ?

I have done a - I think really ugly hack - to get the restricted-manager working :

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|cp /boot/config-2.6.20-16-generic /lib/modules/2.6.20-16-generic/.config}}
{{cmdroot|gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -16-generic".
Then I compiled the kernel again with:

{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I moved my modules with :

{{cmdroot|mv /lib/modules/2.6.20-16-generic /lib/modules/2.6.20-16-generic.orginal}}

And installed the kernel with:

{{cmdroot|dpkg -i linux-image-2.6.20-16-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers as described above.
Finally I copied the ipw3945.ucode with

{{cmdroot|cp /lib/firmware/2.6.22-7-generic/ipw3945.ucode /lib/firmware/2.6.20-16-generic/ipw3945.ucode}}

My wireless-card is working now !
My ATI Card cannot be configured with restricted-manager!

{{HELP|Please can someone who is conform in compiling Ubuntu kernels and restricted modules help me to do it in the correct way ! And can someone recheck the things described above, because I am not sure about all things that I have written here.
}}

After some days Ubuntu updated the kernel to version 2.6.22-9-generic, so I need to do the steps described above again, with "EXTRAVERSION = -9-generic". But now my wireless card and my grapics card did not work. The restricted-manager crashes when I start it.
So I downloaded the packages ipw3945-1.2.1.tgz and ati-driver-installer-8.39.4-x86.x86_64.run.

== The Wireless Card ==

First I extracted and installed the Intel Pro Wireless Package:

{{cmduser|tar xzvf ipw3945-1.2.1.tgz}}
{{cmduser|cd ipw3945-1.2.1}}
{{cmduser|make}}
{{cmduser|sudo make install}}

After this I could do :

{{cmduser|sudo modprobe ipw3945}}

The module was loaded, and i was able to use my wireless card now.

== The Graphics Card ==

For my Radeon Mobility X1400 I did the following steps:

{{cmduser|sudo apt get update}}
{{cmduser|sudo apt-get install module-assistant build-essential fakeroot dh-make debhelper debconf libstdc++5}}

Created a Debian Package with:

{{cmduser|sudo bash ati-driver-installer-8.39.4-x86.x86_64.run --buildpkg Ubuntu/gutsy}}

And blacklisted the old fglrx module with:

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

I added "fglrx" to the line with "DISABLED_MODULES". Then I installed the created Debian Packages with:

{{cmduser|sudo dpkg -i xorg-driver-fglrx_8.39.4-1_i386.deb fglrx-kernel-source_8.39.4-1_i386.deb fglrx-amdcccle_8.39.4-1_i386.deb}}

Then I compiled the kernel Modules:

{{cmduser|sudo module-assistant prepare}}
{{cmduser|sudo module-assistant update}}
{{cmduser|sudo module-assistant build fglrx}}
{{cmduser|sudo module-assistant install fglrx}}
{{cmduser|sudo depmod -a}}

The helpful informations for this was found at http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide.

After this steps my wifi-card and my graphics-card was working and restricted-manager was not crashing when I tried to start it.

== After The Kernel Update ==

On 9.October 2007 Ubuntu released the Kernelpackage linux-image-2.6.22-14-generic and I installed it. So here is what I have done to get it working:

{{cmduser|sudo apt-get install linux-headers-generic}}
{{cmduser|sudo ln -s /usr/src/linux-source-2.6.22 /lib/modules/2.6.22-14-generic/source}}
{{cmduser|sudo cd /usr/src/linux}}
{{cmduser|sudo make clean}}
{{cmduser|sudo cp /boot/config-2.6.22-14-generic .config}}
{{cmduser|sudo cp /boot/config-2.6.22-14-generic /lib/modules/2.6.22-14-generic/.config}}
{{cmduser|sudo gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -14-generic".

{{cmduser|sudo gedit .config}}

In the .config file I changed the entry " # CONFIG_SND_HDA_INTEL is not set " to " CONFIG_SND_HDA_INTEL=m ". This was needed to compile the module for my sound card.

Then I compiled the kernel again with:

{{cmduser|sudo make oldconfig}}
{{cmduser|sudo fakeroot make-kpkg clean}}
$ sudo fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I copied my modules with :

{{cmduser|sudo cp -R /lib/modules/2.6.22-14-generic /lib/modules/2.6.22-14-generic.orginal}}

And installed the kernel with:

{{cmduser|sudo dpkg -r linux-headers-generic linux-headers-2.6.22-14-generic}}
{{cmduser|cd ..}}
{{cmduser|sudo dpkg -i linux-image-2.6.22-14-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers with:

{{cmduser|cd /home/dirk/tp_smapi-0.32}}
$ sudo make install HDAPS=1

After this I load the modules with:

{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdaps}}

And test it with:

{{cmduser|hdaps-gl}}

== The Browser Buttons ==

I wanted to use the Browser Forward & Backward Buttons within Firefox. After the upgrade my Firefox had version 2.0.0.4

I did :

{{cmduser| gedit ~/.Xmodmap}}

and added the following lines :

keycode 234 = F19

keycode 233 = F20

I saved and closed the file. HINT: You have to re-login to Gnome to get the .Xmodmap file active.

Then I did the things described in [http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work#Firefox How to get special keys to work].

For the Windows Key I added "keycode 115 = F13" to my .Xmodmap File, then I klicked on "System - Einstellungen - Tastenkombinationen"
sorry I don't know how it is called in English. And changed the Entry "Das Panelmenü anzeigen" to F13

== The Brightness Buttons ==

When I wanted to control the brightness, I was not able to change it with {{key|Fn}}{{key|End}}.

So I did the Workaround menitioned here [http://thinkwiki.org/wiki/Problem_with_LCD_brightness_buttons#Workaround for Fedora Core 6 Users].
After this I was able to change the brightness with {{key|Fn}}{{key|Home}} and {{key|Fn}}{{key|End}}, but I don't have the OSD anymore.

UPDATE: You don't need to do this since kernel version 2.6.22 on Ubuntu

== The Fingerprint Reader ==

Do the steps which are described in [http://www.thinkwiki.org/wiki/Installing_Ubuntu_6.10_%28Edgy_Eft%29_on_a_ThinkPad_T60#The_Fingerprint_Reader Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60] until you get to the Point where Keithvassallo says:
"Phew. Now, to make applications actually use the fingerprint reader."

I have done the following things instead of his version:

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

Change the file as following:

<pre>
#%PAM-1.0
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
auth requisite pam_nologin.so
auth required pam_env.so
@include common-auth
@include common-account
session required pam_limits.so
@include common-session
@include common-password
</pre>

and:

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

Change this file as following:

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

With this changes you have the advantage, that you are now able to login to Gnome or KDE whitout entering your password. But if you cancel the "Fingerprint Login", you are still able to login whit your username/password combination.

After I was able to login to my desktop I was unsatisfied, because my Computer still wants to get passwords i.e. when I tried to open Synaptic or when I do any sudo actions.

So I tried to figure out how this sudo thing works. I did the following change to /etc/pam.d/sudo with:

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

<pre>
#%PAM-1.0

auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/ :0
password sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam :0
auth required pam_unix.so nillock_secure
@include common-account

</pre>

With this change I was able to open System Administration tasks with my fingerprint, but the ugly thing is, that you get no information to swipe your finger over the reader when you have switched to a console session with {{Key|Ctrl}}+{{Key|Alt}}+{{Key|F1}}. The fingerprint scanner software will appear at your running X session.

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-10-10T07:54:00Z

Dirk: /* After The Kernel Update */

== My Thinkpad ==
<pre>
Lenovo Thinkpad R60 9461 HRG
Intel Core2Duo (Merom) 1.83 CPU
120 GB SATA Hitachi HTS54161 Harddisk
2 GB RAM
ATI Mobility X1400
</pre>

Originally equipped with a preinstalled MS Windows Vista Business. So the Harddisk was parted into two Partitions.

1. The Rescue & Recovery Partition

2. The preinstalled Windows Vista Partition

And as the parcel with my new Thinkpad arrived I was surprized, that there was a Windows Vista DVD (only 32 Bit Version) with it.
So I tried Vista - but I was a little bit shocked by it's performance. I never thought that a new computer could take so much time to boot up completely.

I decided to do a clean install of Vista, but I want to have Windows XP and Ubuntu Feisty on the Harddisk too.

== New Installation ==

I wanted to use all Space of the Harddisk, so I decided to kill the Rescue & and Recovery Partition, but to have the chance to go back to the factory default state I ordered Recovery DVD's at the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4HWSE3#Lenovo Support Call Center for Germany].
They shipped the 3 DVD's to me - free of charge - but I think it's only free if your Thinkpad is still in the warranty. I don't know exactly.

Then I created 2 Partitions on my Harddisk, 64 GB for Vista, 20 GB for XP, so 29 GB left free for Linux.

I installed Vista and XP and all the Thinkpad Stuff for each system.

When this was finished I took a Ubuntu Feisty Fawn installation CD and boot my Notebook with it. I created a 4 GB linux-swap partition and a 25 GB root / partition.

Because I want to boot my Ubuntu with the Windows Vista Boot Loader, I decided to install Grub to /dev/sda4 which is my Linux root partition.

The installation of Ubuntu Feisty Fawn works fine, NO PROBLEMS.

NOW I want to boot Linux from the Vista Bootloader, because I don't want to wait for two Bootscreens, and I wan't to have the chance to access the Repair Console of Windows Vista.

First I have to copy the Bootsector of my Linux Partition with:

<pre>
sudo dd if=/dev/sda4 of=/tmp/bootsect.lin bs=512 count=1
</pre>

Copy the bootsect.lin file to a USB-Stick or a writable partition which you can access from Windows Vista.

Now boot Windows Vista and copy the file bootsect.lin to your Systemdrive. In an Command Window with Administrator privileges type:

<pre>
copy bootsect.lin %SYSTEMDRIVE%\

bcdedit /create /d “Ubuntu” /application BOOTSECTOR
</pre>

You will receice an ID like this {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} from bcdedit. This is a uniqe identifier for your new Boot Entry in the Vista Bootloader. Now you will have to manipulate the entry with the following commands:

<pre>
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} device boot
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} PATH \bootsect.lin
bcdedit /displayorder {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} /addlast
bcdedit /timeout 10
</pre>

Then I booted my Ubuntu an did :

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

In this file I canged the entry the following entries:

<pre>
timeout 2
hiddenmenu
</pre>

So the computer starts up with the Windows Vista bootloader and gives me the option to start Windows XP, Windows Vista, Ubuntu and I have the option to do the repair tasks with the {{key|F8}} button on Vista if something fails. If I choose to boot Ubuntu I have the option to press the {{key|ESC}} key within the two seconds delay of the hidden Grub Menu. I.E. to boot another Linux Kernel.

== The tp_smapi modules ==

I did it under Feisty and, after the Upgrade under Gutsy, like described here : [http://www.thinkwiki.org/wiki/Tp_smapi#Installation TP SMAPI] in the Section "Installation on Ubuntu/Debian"
It worked, hdaps-gl and hdaps-pivot shows me now the movements of my Thinkpad. Like you can see here:

[[Image:Hdaps-pivot.png]]

[[Image:Hdaps-gl.png]]

== The Upgrade to Gutsy Gibbon ==

NO PROBLEMS. So why should I upgrade ?

OK I really wanted to get hdapsd (Harddisk Active Protection) to work. I tried a lot of things with Feisty, but I didn't get it going. And after a lot of seach through the Internet I found out that Gutsy Gibbon, the next Release of Ubuntu should have the Package for hdapsd on board.
SO I decided to upgrade to Gutsy - with the knowledge that it is still in Beta Stadium.

Upgrading Ubuntu is really simple, you only have to do the following steps:

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

Search all feisty entries and change them to gutsy. Save and Close the file.

Do:

{{cmduser| sudo apt-get update}}
{{cmduser| sudo apt-get upgrade}}

Go and drink a cup of Tea or Coffee. When you are back you have a message, that you should reboot your System, to get all packages active. So do it.

After the reboot I installed the hdapsd package and I tried to activate the Harddisk Protection with:

{{cmduser| sudo hdapsd -d sda -s 14 -a -v}}

But I still get the message "open(protect_file): No such file or directory". ---- The Same Message that I get in Feisty before I did the Upgrade. So I banged my head on the table and noticed that I'm not tough enough to get this thing working. Maybe someone else.

I decided to get the other things to work.

UPDATE: After some days I tried to get hdapsd to work, again !

== The hdapsd - Deamon (IBM Active Disk Protection) ==

Because I never had compiled or patched a kernel under Ubuntu I had to find out how this works ! After a lot of search in the Internet, the Ubuntu Help and at Thinkwiki.org I found the (hopefully) correct way to do it.

The best information I found was this :
[http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.04_on_a_ThinkPad_T43#Active_Protection_System_.28acceleration_monitor.29|Installing Ubuntu 7.04 on a ThinkPad T43] in section "Disk protection"

Here is what I did to get it to work:

1. Make sure that you have the required packages, with:

{{cmduser|sudo apt-get install build-essential fakeroot kernel-package libncurses5-dev wget bzip2 linux-source}}

2. Get the correct kernel patch for your running kernel from here : [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch_.28apply_using_.27patch_-p1_-l_.3C_hdaps_xx.patch.27.29| HDAPS] section "8.1.1 Kernel patch (apply using 'patch -p1 -l < hdaps_xx.patch')"

After all my experiences I was not sure that there was a patch available for my Gutsy-kernel (2.6.22-7-generic), but I still had my old kernel on the disk. So I booted up the old one (2.6.20-16-generic). Check the running kernel with:

{{cmduser|uname -r}}

You should see something like: 2.6.20-7-generic

Now change to /usr/src and look that the sources for the running kernel are there with:

{{cmduser|cd /usr/src}}
{{cmduser|ls -d linux-source*}}

You should see a file with the name "linux-source-2.6.20.tar.bz2" wich includes the packed kernel sources. You have to extract it, so do:

{{cmduser|sudo su}}
{{cmdroot|tar xvfj linux-source-2.6.20.tar.bz2}}

Now you have the kernel sources in the /usr/src/linux-source-2.6.20 directory. Take a look if there is a link from /usr/src/linux to an other kernel source directory (It's maybe there if you tried to compile a kernel some time before).

{{cmdroot|ls -l linux}}

If you see that linux is linked to an other source than your running kernel remove the link and create a new one with:

{{cmdroot|rm linux}}
{{cmdroot|ln -s /usr/src/linux-source-2.6.20 linux}}

Change to the source directory and patch the kernel with this:

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|patch -p1 -l < /home/dirk/993-001.bin}}

The file "993-001.bin" is the kernel patch for the 2.6.20 and 2.6.21 kernels, I downloaded it here : [http://article.gmane.org/gmane.linux.drivers.hdaps.devel/993]

After the patchwork I did this :

{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --append-to-version=.hdapscustom kernel_image --initrd binary

This would take its time, so go and clean up your house ;-)
{{HELP|I think the last command (with --append-to-version was an error ! I need help from an specialist in kernel compiling. Please read ahead at the next section "The hdapsd - Deamon (next try)". }}
After your house is clean you can do :

{{cmdroot|cd /usr/src}}
{{cmdroot|ls -l linux*.deb}}

You should see some newly builded Debian Pakage files. Install them with:

{{cmdroot|dpkg -i linux-headers-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-doc-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-image-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-manual-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-source-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}

After the installation you should reboot your computer, when Grub comes up make sure that you select your newly builded kernel.
Check it with:

{{cmduser|uname -r}}

You should see this "2.6.20.3-ubuntu1.hdapscustom". But now you have the Problem, that you have to recompile the tp_smapi driver.

{{cmduser|cd tp_smapi-0.31}}
$ sudo make install HDAPS=1
{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdaps}}

After :

<pre>
$ dmesg | grep hdaps
</pre>

You should see something like this:

[ 893.752000] hdaps: initial mode latch is 0x05
[ 893.752000] hdaps: setting ec_rate=250, filter_order=2
[ 893.752000] hdaps: fake_data_mode set to 0
[ 893.756000] hdaps: device successfully initialized.
[ 893.756000] input: hdaps as /class/input/input10
[ 893.756000] hdaps: driver successfully loaded.

Now we are ready to try out the hdapsd Deamon which is included in the Gutsy repositories, if you are using Feisty you have to compile it yourself like described here: [http://www.thinkwiki.org/wiki/How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS].

{{cmdroot|sudo hdapsd -d sda -s 12 -a -v}}

Should show this:

[[Image:hdapsd.png]]

If you load it with :

{{cmdroot|sudo hdapsd -d sda -s 12 -a}}

You get nothing until you move your Thinkpad, then you see:

Fri Jul 13 12:30:42 2007: parking
Fri Jul 13 12:30:43 2007: un-parking
Fri Jul 13 12:30:44 2007: parking
Fri Jul 13 12:30:45 2007: un-parking

Now, after I have a working hdaps-deamon I want it to be started at boot time. Because I have upgraded to Gutsy and installed the hdapsd - Package I have a script called /etc/default/hdapsd. Here I have to change some things. HINT: Remember that you still need the /etc/init.d/hdapsd file if you try this on Feisty and maybe you have to do:

{{cmduser|sudo update-rc.d hdapsd defaults}}

to create the init links for the hdapsd init script. My links was already there. My /etc/default/hdapsd script now looks like this:

<pre>
# hdapsd default file

# start hdapsd at boottime?
START="yes"

# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
DISK="sda"

# sensitivity
SENSITIVITY=12

# other options to pass to hdapsd.
# the -d $DISK, -s $SENSITIVITY, -b and -p $PIDFILE options are always passed.
OPTIONS="-a"

</pre>

Now I could use the gnome-hdaps-applet with the following comands:

{{cmduser|mkdir gnome-hdaps-applet}}
{{cmduser|cd gnome-hdaps-applet}}
{{cmduser|wget http://www.zen24593.zen.co.uk/hdaps/gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|tar -xzf gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|sudo apt-get install libpanel-applet2-dev}}
{{cmduser|gcc $(pkg-config --cflags --libs libpanelapplet-2.0) -o gnome-hdaps-applet gnome-hdaps-applet.c}}
{{cmduser|sudo cp gnome-hdaps-applet /usr/bin/}}
{{cmduser|sudo mkdir /usr/share/pixmaps/gnome-hdaps-applet/}}
{{cmduser|sudo cp *.png /usr/share/pixmaps/gnome-hdaps-applet/}}
$ sudo cp GNOME_HDAPS_StatusApplet.server /usr/lib/bonobo/servers/

Now after a restart of the Gnome Session I could find a "HDAPS Status" applet in the "Add to Panel" dialog. I added it, and when I move the Thinkpad it shows me the "Pause" [[Image:Hdaps-paused-small.png]] Symbol, otherwise it shows "Play" [[Image:Hdaps-running-small.png]].

So far so good !!! After I got this running I tried the same steps with the normal Gutsy Kernel (2.6.22-7-generic) on the same way, and it worked ! To my surprise with the same kernel patch.

The only Problem that I now have is that I cannot use restricted modules with my new kernels. Now I have to figure out how to compile restricted modules agains selfmade kernels.

{{HELP| }}

== The hdapsd - Deamon (next try) ==

I am not satisfied with the above result, because I cannot use the accelerated xorg-fglrx driver for my ATI Graphics Card and I cannot use my wireless Intel card ipw3945 driver. And the Ubuntu restricted-manager is not working. PLEASE can someone help me to compile a Ubuntu kernel in the correct way, so that I can use the whole hardware ?

I have done a - I think really ugly hack - to get the restricted-manager working :

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|cp /boot/config-2.6.20-16-generic /lib/modules/2.6.20-16-generic/.config}}
{{cmdroot|gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -16-generic".
Then I compiled the kernel again with:

{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I moved my modules with :

{{cmdroot|mv /lib/modules/2.6.20-16-generic /lib/modules/2.6.20-16-generic.orginal}}

And installed the kernel with:

{{cmdroot|dpkg -i linux-image-2.6.20-16-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers as described above.
Finally I copied the ipw3945.ucode with

{{cmdroot|cp /lib/firmware/2.6.22-7-generic/ipw3945.ucode /lib/firmware/2.6.20-16-generic/ipw3945.ucode}}

My wireless-card is working now !
My ATI Card cannot be configured with restricted-manager!

{{HELP|Please can someone who is conform in compiling Ubuntu kernels and restricted modules help me to do it in the correct way ! And can someone recheck the things described above, because I am not sure about all things that I have written here.
}}

After some days Ubuntu updated the kernel to version 2.6.22-9-generic, so I need to do the steps described above again, with "EXTRAVERSION = -9-generic". But now my wireless card and my grapics card did not work. The restricted-manager crashes when I start it.
So I downloaded the packages ipw3945-1.2.1.tgz and ati-driver-installer-8.39.4-x86.x86_64.run.

== The Wireless Card ==

First I extracted and installed the Intel Pro Wireless Package:

{{cmduser|tar xzvf ipw3945-1.2.1.tgz}}
{{cmduser|cd ipw3945-1.2.1}}
{{cmduser|make}}
{{cmduser|sudo make install}}

After this I could do :

{{cmduser|sudo modprobe ipw3945}}

The module was loaded, and i was able to use my wireless card now.

== The Graphics Card ==

For my Radeon Mobility X1400 I did the following steps:

{{cmduser|sudo apt get update}}
{{cmduser|sudo apt-get install module-assistant build-essential fakeroot dh-make debhelper debconf libstdc++5}}

Created a Debian Package with:

{{cmduser|sudo bash ati-driver-installer-8.39.4-x86.x86_64.run --buildpkg Ubuntu/gutsy}}

And blacklisted the old fglrx module with:

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

I added "fglrx" to the line with "DISABLED_MODULES". Then I installed the created Debian Packages with:

{{cmduser|sudo dpkg -i xorg-driver-fglrx_8.39.4-1_i386.deb fglrx-kernel-source_8.39.4-1_i386.deb fglrx-amdcccle_8.39.4-1_i386.deb}}

Then I compiled the kernel Modules:

{{cmduser|sudo module-assistant prepare}}
{{cmduser|sudo module-assistant update}}
{{cmduser|sudo module-assistant build fglrx}}
{{cmduser|sudo module-assistant install fglrx}}
{{cmduser|sudo depmod -a}}

The helpful informations for this was found at http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide.

After this steps my wifi-card and my graphics-card was working and restricted-manager was not crashing when I tried to start it.

== After The Kernel Update ==

On 9.October 2007 Ubuntu released the Kernelpackage linux-image-2.6.22-14-generic and I installed it. So here is what I have done to get it working:

{{cmduser|sudo apt-get install linux-headers-generic}}
{{cmduser|sudo ln -s /usr/src/linux-source-2.6.22 /lib/modules/2.6.22-14-generic/source}}
{{cmduser|sudo cd /usr/src/linux}}
{{cmduser|sudo make clean}}
{{cmduser|sudo cp /boot/config-2.6.22-14-generic .config}}
{{cmduser|sudo cp /boot/config-2.6.22-14-generic /lib/modules/2.6.22-14-generic/.config}}
{{cmduser|sudo gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -14-generic".

{{cmduser|sudo gedit .config}}

In the .config file I changed the entry " # CONFIG_SND_HDA_INTEL is not set " to " CONFIG_SND_HDA_INTEL=m ". This was needed to compile the module for my sound card.

Then I compiled the kernel again with:

{{cmduser|sudo make oldconfig}}
{{cmduser|sudo fakeroot make-kpkg clean}}
$ sudo fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I copied my modules with :

{{cmduser|sudo cp -R /lib/modules/2.6.22-14-generic /lib/modules/2.6.22-14-generic.orginal}}

And installed the kernel with:

{{cmduser|sudo dpkg -r linux-headers-generic linux-headers-2.6.22-14-generic}}
{{cmduser|cd ..}}
{{cmduser|sudo dpkg -i linux-image-2.6.22-14-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers with:

{{cmduser|cd /home/dirk/tp_smapi-0.32}}
$ sudo make install HDAPS=1

== The Browser Buttons ==

I wanted to use the Browser Forward & Backward Buttons within Firefox. After the upgrade my Firefox had version 2.0.0.4

I did :

{{cmduser| gedit ~/.Xmodmap}}

and added the following lines :

keycode 234 = F19

keycode 233 = F20

I saved and closed the file. HINT: You have to re-login to Gnome to get the .Xmodmap file active.

Then I did the things described in [http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work#Firefox How to get special keys to work].

For the Windows Key I added "keycode 115 = F13" to my .Xmodmap File, then I klicked on "System - Einstellungen - Tastenkombinationen"
sorry I don't know how it is called in English. And changed the Entry "Das Panelmenü anzeigen" to F13

== The Brightness Buttons ==

When I wanted to control the brightness, I was not able to change it with {{key|Fn}}{{key|End}}.

So I did the Workaround menitioned here [http://thinkwiki.org/wiki/Problem_with_LCD_brightness_buttons#Workaround for Fedora Core 6 Users].
After this I was able to change the brightness with {{key|Fn}}{{key|Home}} and {{key|Fn}}{{key|End}}, but I don't have the OSD anymore.

UPDATE: You don't need to do this since kernel version 2.6.22 on Ubuntu

== The Fingerprint Reader ==

Do the steps which are described in [http://www.thinkwiki.org/wiki/Installing_Ubuntu_6.10_%28Edgy_Eft%29_on_a_ThinkPad_T60#The_Fingerprint_Reader Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60] until you get to the Point where Keithvassallo says:
"Phew. Now, to make applications actually use the fingerprint reader."

I have done the following things instead of his version:

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

Change the file as following:

<pre>
#%PAM-1.0
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
auth requisite pam_nologin.so
auth required pam_env.so
@include common-auth
@include common-account
session required pam_limits.so
@include common-session
@include common-password
</pre>

and:

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

Change this file as following:

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

With this changes you have the advantage, that you are now able to login to Gnome or KDE whitout entering your password. But if you cancel the "Fingerprint Login", you are still able to login whit your username/password combination.

After I was able to login to my desktop I was unsatisfied, because my Computer still wants to get passwords i.e. when I tried to open Synaptic or when I do any sudo actions.

So I tried to figure out how this sudo thing works. I did the following change to /etc/pam.d/sudo with:

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

<pre>
#%PAM-1.0

auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/ :0
password sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam :0
auth required pam_unix.so nillock_secure
@include common-account

</pre>

With this change I was able to open System Administration tasks with my fingerprint, but the ugly thing is, that you get no information to swipe your finger over the reader when you have switched to a console session with {{Key|Ctrl}}+{{Key|Alt}}+{{Key|F1}}. The fingerprint scanner software will appear at your running X session.

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-10-10T07:52:54Z

Dirk: /* After The Kernel Update */

== My Thinkpad ==
<pre>
Lenovo Thinkpad R60 9461 HRG
Intel Core2Duo (Merom) 1.83 CPU
120 GB SATA Hitachi HTS54161 Harddisk
2 GB RAM
ATI Mobility X1400
</pre>

Originally equipped with a preinstalled MS Windows Vista Business. So the Harddisk was parted into two Partitions.

1. The Rescue & Recovery Partition

2. The preinstalled Windows Vista Partition

And as the parcel with my new Thinkpad arrived I was surprized, that there was a Windows Vista DVD (only 32 Bit Version) with it.
So I tried Vista - but I was a little bit shocked by it's performance. I never thought that a new computer could take so much time to boot up completely.

I decided to do a clean install of Vista, but I want to have Windows XP and Ubuntu Feisty on the Harddisk too.

== New Installation ==

I wanted to use all Space of the Harddisk, so I decided to kill the Rescue & and Recovery Partition, but to have the chance to go back to the factory default state I ordered Recovery DVD's at the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4HWSE3#Lenovo Support Call Center for Germany].
They shipped the 3 DVD's to me - free of charge - but I think it's only free if your Thinkpad is still in the warranty. I don't know exactly.

Then I created 2 Partitions on my Harddisk, 64 GB for Vista, 20 GB for XP, so 29 GB left free for Linux.

I installed Vista and XP and all the Thinkpad Stuff for each system.

When this was finished I took a Ubuntu Feisty Fawn installation CD and boot my Notebook with it. I created a 4 GB linux-swap partition and a 25 GB root / partition.

Because I want to boot my Ubuntu with the Windows Vista Boot Loader, I decided to install Grub to /dev/sda4 which is my Linux root partition.

The installation of Ubuntu Feisty Fawn works fine, NO PROBLEMS.

NOW I want to boot Linux from the Vista Bootloader, because I don't want to wait for two Bootscreens, and I wan't to have the chance to access the Repair Console of Windows Vista.

First I have to copy the Bootsector of my Linux Partition with:

<pre>
sudo dd if=/dev/sda4 of=/tmp/bootsect.lin bs=512 count=1
</pre>

Copy the bootsect.lin file to a USB-Stick or a writable partition which you can access from Windows Vista.

Now boot Windows Vista and copy the file bootsect.lin to your Systemdrive. In an Command Window with Administrator privileges type:

<pre>
copy bootsect.lin %SYSTEMDRIVE%\

bcdedit /create /d “Ubuntu” /application BOOTSECTOR
</pre>

You will receice an ID like this {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} from bcdedit. This is a uniqe identifier for your new Boot Entry in the Vista Bootloader. Now you will have to manipulate the entry with the following commands:

<pre>
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} device boot
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} PATH \bootsect.lin
bcdedit /displayorder {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} /addlast
bcdedit /timeout 10
</pre>

Then I booted my Ubuntu an did :

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

In this file I canged the entry the following entries:

<pre>
timeout 2
hiddenmenu
</pre>

So the computer starts up with the Windows Vista bootloader and gives me the option to start Windows XP, Windows Vista, Ubuntu and I have the option to do the repair tasks with the {{key|F8}} button on Vista if something fails. If I choose to boot Ubuntu I have the option to press the {{key|ESC}} key within the two seconds delay of the hidden Grub Menu. I.E. to boot another Linux Kernel.

== The tp_smapi modules ==

I did it under Feisty and, after the Upgrade under Gutsy, like described here : [http://www.thinkwiki.org/wiki/Tp_smapi#Installation TP SMAPI] in the Section "Installation on Ubuntu/Debian"
It worked, hdaps-gl and hdaps-pivot shows me now the movements of my Thinkpad. Like you can see here:

[[Image:Hdaps-pivot.png]]

[[Image:Hdaps-gl.png]]

== The Upgrade to Gutsy Gibbon ==

NO PROBLEMS. So why should I upgrade ?

OK I really wanted to get hdapsd (Harddisk Active Protection) to work. I tried a lot of things with Feisty, but I didn't get it going. And after a lot of seach through the Internet I found out that Gutsy Gibbon, the next Release of Ubuntu should have the Package for hdapsd on board.
SO I decided to upgrade to Gutsy - with the knowledge that it is still in Beta Stadium.

Upgrading Ubuntu is really simple, you only have to do the following steps:

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

Search all feisty entries and change them to gutsy. Save and Close the file.

Do:

{{cmduser| sudo apt-get update}}
{{cmduser| sudo apt-get upgrade}}

Go and drink a cup of Tea or Coffee. When you are back you have a message, that you should reboot your System, to get all packages active. So do it.

After the reboot I installed the hdapsd package and I tried to activate the Harddisk Protection with:

{{cmduser| sudo hdapsd -d sda -s 14 -a -v}}

But I still get the message "open(protect_file): No such file or directory". ---- The Same Message that I get in Feisty before I did the Upgrade. So I banged my head on the table and noticed that I'm not tough enough to get this thing working. Maybe someone else.

I decided to get the other things to work.

UPDATE: After some days I tried to get hdapsd to work, again !

== The hdapsd - Deamon (IBM Active Disk Protection) ==

Because I never had compiled or patched a kernel under Ubuntu I had to find out how this works ! After a lot of search in the Internet, the Ubuntu Help and at Thinkwiki.org I found the (hopefully) correct way to do it.

The best information I found was this :
[http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.04_on_a_ThinkPad_T43#Active_Protection_System_.28acceleration_monitor.29|Installing Ubuntu 7.04 on a ThinkPad T43] in section "Disk protection"

Here is what I did to get it to work:

1. Make sure that you have the required packages, with:

{{cmduser|sudo apt-get install build-essential fakeroot kernel-package libncurses5-dev wget bzip2 linux-source}}

2. Get the correct kernel patch for your running kernel from here : [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch_.28apply_using_.27patch_-p1_-l_.3C_hdaps_xx.patch.27.29| HDAPS] section "8.1.1 Kernel patch (apply using 'patch -p1 -l < hdaps_xx.patch')"

After all my experiences I was not sure that there was a patch available for my Gutsy-kernel (2.6.22-7-generic), but I still had my old kernel on the disk. So I booted up the old one (2.6.20-16-generic). Check the running kernel with:

{{cmduser|uname -r}}

You should see something like: 2.6.20-7-generic

Now change to /usr/src and look that the sources for the running kernel are there with:

{{cmduser|cd /usr/src}}
{{cmduser|ls -d linux-source*}}

You should see a file with the name "linux-source-2.6.20.tar.bz2" wich includes the packed kernel sources. You have to extract it, so do:

{{cmduser|sudo su}}
{{cmdroot|tar xvfj linux-source-2.6.20.tar.bz2}}

Now you have the kernel sources in the /usr/src/linux-source-2.6.20 directory. Take a look if there is a link from /usr/src/linux to an other kernel source directory (It's maybe there if you tried to compile a kernel some time before).

{{cmdroot|ls -l linux}}

If you see that linux is linked to an other source than your running kernel remove the link and create a new one with:

{{cmdroot|rm linux}}
{{cmdroot|ln -s /usr/src/linux-source-2.6.20 linux}}

Change to the source directory and patch the kernel with this:

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|patch -p1 -l < /home/dirk/993-001.bin}}

The file "993-001.bin" is the kernel patch for the 2.6.20 and 2.6.21 kernels, I downloaded it here : [http://article.gmane.org/gmane.linux.drivers.hdaps.devel/993]

After the patchwork I did this :

{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --append-to-version=.hdapscustom kernel_image --initrd binary

This would take its time, so go and clean up your house ;-)
{{HELP|I think the last command (with --append-to-version was an error ! I need help from an specialist in kernel compiling. Please read ahead at the next section "The hdapsd - Deamon (next try)". }}
After your house is clean you can do :

{{cmdroot|cd /usr/src}}
{{cmdroot|ls -l linux*.deb}}

You should see some newly builded Debian Pakage files. Install them with:

{{cmdroot|dpkg -i linux-headers-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-doc-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-image-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-manual-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-source-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}

After the installation you should reboot your computer, when Grub comes up make sure that you select your newly builded kernel.
Check it with:

{{cmduser|uname -r}}

You should see this "2.6.20.3-ubuntu1.hdapscustom". But now you have the Problem, that you have to recompile the tp_smapi driver.

{{cmduser|cd tp_smapi-0.31}}
$ sudo make install HDAPS=1
{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdaps}}

After :

<pre>
$ dmesg | grep hdaps
</pre>

You should see something like this:

[ 893.752000] hdaps: initial mode latch is 0x05
[ 893.752000] hdaps: setting ec_rate=250, filter_order=2
[ 893.752000] hdaps: fake_data_mode set to 0
[ 893.756000] hdaps: device successfully initialized.
[ 893.756000] input: hdaps as /class/input/input10
[ 893.756000] hdaps: driver successfully loaded.

Now we are ready to try out the hdapsd Deamon which is included in the Gutsy repositories, if you are using Feisty you have to compile it yourself like described here: [http://www.thinkwiki.org/wiki/How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS].

{{cmdroot|sudo hdapsd -d sda -s 12 -a -v}}

Should show this:

[[Image:hdapsd.png]]

If you load it with :

{{cmdroot|sudo hdapsd -d sda -s 12 -a}}

You get nothing until you move your Thinkpad, then you see:

Fri Jul 13 12:30:42 2007: parking
Fri Jul 13 12:30:43 2007: un-parking
Fri Jul 13 12:30:44 2007: parking
Fri Jul 13 12:30:45 2007: un-parking

Now, after I have a working hdaps-deamon I want it to be started at boot time. Because I have upgraded to Gutsy and installed the hdapsd - Package I have a script called /etc/default/hdapsd. Here I have to change some things. HINT: Remember that you still need the /etc/init.d/hdapsd file if you try this on Feisty and maybe you have to do:

{{cmduser|sudo update-rc.d hdapsd defaults}}

to create the init links for the hdapsd init script. My links was already there. My /etc/default/hdapsd script now looks like this:

<pre>
# hdapsd default file

# start hdapsd at boottime?
START="yes"

# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
DISK="sda"

# sensitivity
SENSITIVITY=12

# other options to pass to hdapsd.
# the -d $DISK, -s $SENSITIVITY, -b and -p $PIDFILE options are always passed.
OPTIONS="-a"

</pre>

Now I could use the gnome-hdaps-applet with the following comands:

{{cmduser|mkdir gnome-hdaps-applet}}
{{cmduser|cd gnome-hdaps-applet}}
{{cmduser|wget http://www.zen24593.zen.co.uk/hdaps/gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|tar -xzf gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|sudo apt-get install libpanel-applet2-dev}}
{{cmduser|gcc $(pkg-config --cflags --libs libpanelapplet-2.0) -o gnome-hdaps-applet gnome-hdaps-applet.c}}
{{cmduser|sudo cp gnome-hdaps-applet /usr/bin/}}
{{cmduser|sudo mkdir /usr/share/pixmaps/gnome-hdaps-applet/}}
{{cmduser|sudo cp *.png /usr/share/pixmaps/gnome-hdaps-applet/}}
$ sudo cp GNOME_HDAPS_StatusApplet.server /usr/lib/bonobo/servers/

Now after a restart of the Gnome Session I could find a "HDAPS Status" applet in the "Add to Panel" dialog. I added it, and when I move the Thinkpad it shows me the "Pause" [[Image:Hdaps-paused-small.png]] Symbol, otherwise it shows "Play" [[Image:Hdaps-running-small.png]].

So far so good !!! After I got this running I tried the same steps with the normal Gutsy Kernel (2.6.22-7-generic) on the same way, and it worked ! To my surprise with the same kernel patch.

The only Problem that I now have is that I cannot use restricted modules with my new kernels. Now I have to figure out how to compile restricted modules agains selfmade kernels.

{{HELP| }}

== The hdapsd - Deamon (next try) ==

I am not satisfied with the above result, because I cannot use the accelerated xorg-fglrx driver for my ATI Graphics Card and I cannot use my wireless Intel card ipw3945 driver. And the Ubuntu restricted-manager is not working. PLEASE can someone help me to compile a Ubuntu kernel in the correct way, so that I can use the whole hardware ?

I have done a - I think really ugly hack - to get the restricted-manager working :

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|cp /boot/config-2.6.20-16-generic /lib/modules/2.6.20-16-generic/.config}}
{{cmdroot|gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -16-generic".
Then I compiled the kernel again with:

{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I moved my modules with :

{{cmdroot|mv /lib/modules/2.6.20-16-generic /lib/modules/2.6.20-16-generic.orginal}}

And installed the kernel with:

{{cmdroot|dpkg -i linux-image-2.6.20-16-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers as described above.
Finally I copied the ipw3945.ucode with

{{cmdroot|cp /lib/firmware/2.6.22-7-generic/ipw3945.ucode /lib/firmware/2.6.20-16-generic/ipw3945.ucode}}

My wireless-card is working now !
My ATI Card cannot be configured with restricted-manager!

{{HELP|Please can someone who is conform in compiling Ubuntu kernels and restricted modules help me to do it in the correct way ! And can someone recheck the things described above, because I am not sure about all things that I have written here.
}}

After some days Ubuntu updated the kernel to version 2.6.22-9-generic, so I need to do the steps described above again, with "EXTRAVERSION = -9-generic". But now my wireless card and my grapics card did not work. The restricted-manager crashes when I start it.
So I downloaded the packages ipw3945-1.2.1.tgz and ati-driver-installer-8.39.4-x86.x86_64.run.

== The Wireless Card ==

First I extracted and installed the Intel Pro Wireless Package:

{{cmduser|tar xzvf ipw3945-1.2.1.tgz}}
{{cmduser|cd ipw3945-1.2.1}}
{{cmduser|make}}
{{cmduser|sudo make install}}

After this I could do :

{{cmduser|sudo modprobe ipw3945}}

The module was loaded, and i was able to use my wireless card now.

== The Graphics Card ==

For my Radeon Mobility X1400 I did the following steps:

{{cmduser|sudo apt get update}}
{{cmduser|sudo apt-get install module-assistant build-essential fakeroot dh-make debhelper debconf libstdc++5}}

Created a Debian Package with:

{{cmduser|sudo bash ati-driver-installer-8.39.4-x86.x86_64.run --buildpkg Ubuntu/gutsy}}

And blacklisted the old fglrx module with:

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

I added "fglrx" to the line with "DISABLED_MODULES". Then I installed the created Debian Packages with:

{{cmduser|sudo dpkg -i xorg-driver-fglrx_8.39.4-1_i386.deb fglrx-kernel-source_8.39.4-1_i386.deb fglrx-amdcccle_8.39.4-1_i386.deb}}

Then I compiled the kernel Modules:

{{cmduser|sudo module-assistant prepare}}
{{cmduser|sudo module-assistant update}}
{{cmduser|sudo module-assistant build fglrx}}
{{cmduser|sudo module-assistant install fglrx}}
{{cmduser|sudo depmod -a}}

The helpful informations for this was found at http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide.

After this steps my wifi-card and my graphics-card was working and restricted-manager was not crashing when I tried to start it.

== After The Kernel Update ==

On 9.October 2007 Ubuntu released the Kernelpackage linux-image-2.6.22-14-generic and I installed it. So here is what I have done to get it working:

{{cmduser|sudo apt-get install linux-headers-generic}}
{{cmduser|sudo ln -s /usr/src/linux-source-2.6.22 /lib/modules/2.6.22-14-generic/source}}
{{cmduser|sudo cd /usr/src/linux}}
{{cmduser|sudo make clean}}
{{cmduser|sudo cp /boot/config-2.6.22-14-generic .config}}
{{cmduser|sudo cp /boot/config-2.6.22-14-generic /lib/modules/2.6.22-14-generic/.config}}
{{cmduser|sudo gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -14-generic".
Then I compiled the kernel again with:

{{cmduser|sudo gedit .config}}

In the .config file I changed the entry " # CONFIG_SND_HDA_INTEL is not set " to " CONFIG_SND_HDA_INTEL=m ". This was needed to compile the module for my sound card.

{{cmduser|sudo make oldconfig}}
{{cmduser|sudo fakeroot make-kpkg clean}}
$ sudo fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I copied my modules with :

{{cmduser|sudo cp -R /lib/modules/2.6.22-14-generic /lib/modules/2.6.22-14-generic.orginal}}

And installed the kernel with:

{{cmduser|sudo dpkg -r linux-headers-generic linux-headers-2.6.22-14-generic}}
{{cmduser|cd ..}}
{{cmduser|sudo dpkg -i linux-image-2.6.22-14-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers with:

{{cmduser|cd /home/dirk/tp_smapi-0.32}}
$ sudo make install HDAPS=1

== The Browser Buttons ==

I wanted to use the Browser Forward & Backward Buttons within Firefox. After the upgrade my Firefox had version 2.0.0.4

I did :

{{cmduser| gedit ~/.Xmodmap}}

and added the following lines :

keycode 234 = F19

keycode 233 = F20

I saved and closed the file. HINT: You have to re-login to Gnome to get the .Xmodmap file active.

Then I did the things described in [http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work#Firefox How to get special keys to work].

For the Windows Key I added "keycode 115 = F13" to my .Xmodmap File, then I klicked on "System - Einstellungen - Tastenkombinationen"
sorry I don't know how it is called in English. And changed the Entry "Das Panelmenü anzeigen" to F13

== The Brightness Buttons ==

When I wanted to control the brightness, I was not able to change it with {{key|Fn}}{{key|End}}.

So I did the Workaround menitioned here [http://thinkwiki.org/wiki/Problem_with_LCD_brightness_buttons#Workaround for Fedora Core 6 Users].
After this I was able to change the brightness with {{key|Fn}}{{key|Home}} and {{key|Fn}}{{key|End}}, but I don't have the OSD anymore.

UPDATE: You don't need to do this since kernel version 2.6.22 on Ubuntu

== The Fingerprint Reader ==

Do the steps which are described in [http://www.thinkwiki.org/wiki/Installing_Ubuntu_6.10_%28Edgy_Eft%29_on_a_ThinkPad_T60#The_Fingerprint_Reader Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60] until you get to the Point where Keithvassallo says:
"Phew. Now, to make applications actually use the fingerprint reader."

I have done the following things instead of his version:

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

Change the file as following:

<pre>
#%PAM-1.0
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
auth requisite pam_nologin.so
auth required pam_env.so
@include common-auth
@include common-account
session required pam_limits.so
@include common-session
@include common-password
</pre>

and:

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

Change this file as following:

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

With this changes you have the advantage, that you are now able to login to Gnome or KDE whitout entering your password. But if you cancel the "Fingerprint Login", you are still able to login whit your username/password combination.

After I was able to login to my desktop I was unsatisfied, because my Computer still wants to get passwords i.e. when I tried to open Synaptic or when I do any sudo actions.

So I tried to figure out how this sudo thing works. I did the following change to /etc/pam.d/sudo with:

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

<pre>
#%PAM-1.0

auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/ :0
password sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam :0
auth required pam_unix.so nillock_secure
@include common-account

</pre>

With this change I was able to open System Administration tasks with my fingerprint, but the ugly thing is, that you get no information to swipe your finger over the reader when you have switched to a console session with {{Key|Ctrl}}+{{Key|Alt}}+{{Key|F1}}. The fingerprint scanner software will appear at your running X session.

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-10-10T07:40:36Z

Dirk: /* After The Kernel Update */

== My Thinkpad ==
<pre>
Lenovo Thinkpad R60 9461 HRG
Intel Core2Duo (Merom) 1.83 CPU
120 GB SATA Hitachi HTS54161 Harddisk
2 GB RAM
ATI Mobility X1400
</pre>

Originally equipped with a preinstalled MS Windows Vista Business. So the Harddisk was parted into two Partitions.

1. The Rescue & Recovery Partition

2. The preinstalled Windows Vista Partition

And as the parcel with my new Thinkpad arrived I was surprized, that there was a Windows Vista DVD (only 32 Bit Version) with it.
So I tried Vista - but I was a little bit shocked by it's performance. I never thought that a new computer could take so much time to boot up completely.

I decided to do a clean install of Vista, but I want to have Windows XP and Ubuntu Feisty on the Harddisk too.

== New Installation ==

I wanted to use all Space of the Harddisk, so I decided to kill the Rescue & and Recovery Partition, but to have the chance to go back to the factory default state I ordered Recovery DVD's at the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4HWSE3#Lenovo Support Call Center for Germany].
They shipped the 3 DVD's to me - free of charge - but I think it's only free if your Thinkpad is still in the warranty. I don't know exactly.

Then I created 2 Partitions on my Harddisk, 64 GB for Vista, 20 GB for XP, so 29 GB left free for Linux.

I installed Vista and XP and all the Thinkpad Stuff for each system.

When this was finished I took a Ubuntu Feisty Fawn installation CD and boot my Notebook with it. I created a 4 GB linux-swap partition and a 25 GB root / partition.

Because I want to boot my Ubuntu with the Windows Vista Boot Loader, I decided to install Grub to /dev/sda4 which is my Linux root partition.

The installation of Ubuntu Feisty Fawn works fine, NO PROBLEMS.

NOW I want to boot Linux from the Vista Bootloader, because I don't want to wait for two Bootscreens, and I wan't to have the chance to access the Repair Console of Windows Vista.

First I have to copy the Bootsector of my Linux Partition with:

<pre>
sudo dd if=/dev/sda4 of=/tmp/bootsect.lin bs=512 count=1
</pre>

Copy the bootsect.lin file to a USB-Stick or a writable partition which you can access from Windows Vista.

Now boot Windows Vista and copy the file bootsect.lin to your Systemdrive. In an Command Window with Administrator privileges type:

<pre>
copy bootsect.lin %SYSTEMDRIVE%\

bcdedit /create /d “Ubuntu” /application BOOTSECTOR
</pre>

You will receice an ID like this {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} from bcdedit. This is a uniqe identifier for your new Boot Entry in the Vista Bootloader. Now you will have to manipulate the entry with the following commands:

<pre>
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} device boot
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} PATH \bootsect.lin
bcdedit /displayorder {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} /addlast
bcdedit /timeout 10
</pre>

Then I booted my Ubuntu an did :

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

In this file I canged the entry the following entries:

<pre>
timeout 2
hiddenmenu
</pre>

So the computer starts up with the Windows Vista bootloader and gives me the option to start Windows XP, Windows Vista, Ubuntu and I have the option to do the repair tasks with the {{key|F8}} button on Vista if something fails. If I choose to boot Ubuntu I have the option to press the {{key|ESC}} key within the two seconds delay of the hidden Grub Menu. I.E. to boot another Linux Kernel.

== The tp_smapi modules ==

I did it under Feisty and, after the Upgrade under Gutsy, like described here : [http://www.thinkwiki.org/wiki/Tp_smapi#Installation TP SMAPI] in the Section "Installation on Ubuntu/Debian"
It worked, hdaps-gl and hdaps-pivot shows me now the movements of my Thinkpad. Like you can see here:

[[Image:Hdaps-pivot.png]]

[[Image:Hdaps-gl.png]]

== The Upgrade to Gutsy Gibbon ==

NO PROBLEMS. So why should I upgrade ?

OK I really wanted to get hdapsd (Harddisk Active Protection) to work. I tried a lot of things with Feisty, but I didn't get it going. And after a lot of seach through the Internet I found out that Gutsy Gibbon, the next Release of Ubuntu should have the Package for hdapsd on board.
SO I decided to upgrade to Gutsy - with the knowledge that it is still in Beta Stadium.

Upgrading Ubuntu is really simple, you only have to do the following steps:

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

Search all feisty entries and change them to gutsy. Save and Close the file.

Do:

{{cmduser| sudo apt-get update}}
{{cmduser| sudo apt-get upgrade}}

Go and drink a cup of Tea or Coffee. When you are back you have a message, that you should reboot your System, to get all packages active. So do it.

After the reboot I installed the hdapsd package and I tried to activate the Harddisk Protection with:

{{cmduser| sudo hdapsd -d sda -s 14 -a -v}}

But I still get the message "open(protect_file): No such file or directory". ---- The Same Message that I get in Feisty before I did the Upgrade. So I banged my head on the table and noticed that I'm not tough enough to get this thing working. Maybe someone else.

I decided to get the other things to work.

UPDATE: After some days I tried to get hdapsd to work, again !

== The hdapsd - Deamon (IBM Active Disk Protection) ==

Because I never had compiled or patched a kernel under Ubuntu I had to find out how this works ! After a lot of search in the Internet, the Ubuntu Help and at Thinkwiki.org I found the (hopefully) correct way to do it.

The best information I found was this :
[http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.04_on_a_ThinkPad_T43#Active_Protection_System_.28acceleration_monitor.29|Installing Ubuntu 7.04 on a ThinkPad T43] in section "Disk protection"

Here is what I did to get it to work:

1. Make sure that you have the required packages, with:

{{cmduser|sudo apt-get install build-essential fakeroot kernel-package libncurses5-dev wget bzip2 linux-source}}

2. Get the correct kernel patch for your running kernel from here : [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch_.28apply_using_.27patch_-p1_-l_.3C_hdaps_xx.patch.27.29| HDAPS] section "8.1.1 Kernel patch (apply using 'patch -p1 -l < hdaps_xx.patch')"

After all my experiences I was not sure that there was a patch available for my Gutsy-kernel (2.6.22-7-generic), but I still had my old kernel on the disk. So I booted up the old one (2.6.20-16-generic). Check the running kernel with:

{{cmduser|uname -r}}

You should see something like: 2.6.20-7-generic

Now change to /usr/src and look that the sources for the running kernel are there with:

{{cmduser|cd /usr/src}}
{{cmduser|ls -d linux-source*}}

You should see a file with the name "linux-source-2.6.20.tar.bz2" wich includes the packed kernel sources. You have to extract it, so do:

{{cmduser|sudo su}}
{{cmdroot|tar xvfj linux-source-2.6.20.tar.bz2}}

Now you have the kernel sources in the /usr/src/linux-source-2.6.20 directory. Take a look if there is a link from /usr/src/linux to an other kernel source directory (It's maybe there if you tried to compile a kernel some time before).

{{cmdroot|ls -l linux}}

If you see that linux is linked to an other source than your running kernel remove the link and create a new one with:

{{cmdroot|rm linux}}
{{cmdroot|ln -s /usr/src/linux-source-2.6.20 linux}}

Change to the source directory and patch the kernel with this:

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|patch -p1 -l < /home/dirk/993-001.bin}}

The file "993-001.bin" is the kernel patch for the 2.6.20 and 2.6.21 kernels, I downloaded it here : [http://article.gmane.org/gmane.linux.drivers.hdaps.devel/993]

After the patchwork I did this :

{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --append-to-version=.hdapscustom kernel_image --initrd binary

This would take its time, so go and clean up your house ;-)
{{HELP|I think the last command (with --append-to-version was an error ! I need help from an specialist in kernel compiling. Please read ahead at the next section "The hdapsd - Deamon (next try)". }}
After your house is clean you can do :

{{cmdroot|cd /usr/src}}
{{cmdroot|ls -l linux*.deb}}

You should see some newly builded Debian Pakage files. Install them with:

{{cmdroot|dpkg -i linux-headers-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-doc-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-image-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-manual-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-source-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}

After the installation you should reboot your computer, when Grub comes up make sure that you select your newly builded kernel.
Check it with:

{{cmduser|uname -r}}

You should see this "2.6.20.3-ubuntu1.hdapscustom". But now you have the Problem, that you have to recompile the tp_smapi driver.

{{cmduser|cd tp_smapi-0.31}}
$ sudo make install HDAPS=1
{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdaps}}

After :

<pre>
$ dmesg | grep hdaps
</pre>

You should see something like this:

[ 893.752000] hdaps: initial mode latch is 0x05
[ 893.752000] hdaps: setting ec_rate=250, filter_order=2
[ 893.752000] hdaps: fake_data_mode set to 0
[ 893.756000] hdaps: device successfully initialized.
[ 893.756000] input: hdaps as /class/input/input10
[ 893.756000] hdaps: driver successfully loaded.

Now we are ready to try out the hdapsd Deamon which is included in the Gutsy repositories, if you are using Feisty you have to compile it yourself like described here: [http://www.thinkwiki.org/wiki/How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS].

{{cmdroot|sudo hdapsd -d sda -s 12 -a -v}}

Should show this:

[[Image:hdapsd.png]]

If you load it with :

{{cmdroot|sudo hdapsd -d sda -s 12 -a}}

You get nothing until you move your Thinkpad, then you see:

Fri Jul 13 12:30:42 2007: parking
Fri Jul 13 12:30:43 2007: un-parking
Fri Jul 13 12:30:44 2007: parking
Fri Jul 13 12:30:45 2007: un-parking

Now, after I have a working hdaps-deamon I want it to be started at boot time. Because I have upgraded to Gutsy and installed the hdapsd - Package I have a script called /etc/default/hdapsd. Here I have to change some things. HINT: Remember that you still need the /etc/init.d/hdapsd file if you try this on Feisty and maybe you have to do:

{{cmduser|sudo update-rc.d hdapsd defaults}}

to create the init links for the hdapsd init script. My links was already there. My /etc/default/hdapsd script now looks like this:

<pre>
# hdapsd default file

# start hdapsd at boottime?
START="yes"

# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
DISK="sda"

# sensitivity
SENSITIVITY=12

# other options to pass to hdapsd.
# the -d $DISK, -s $SENSITIVITY, -b and -p $PIDFILE options are always passed.
OPTIONS="-a"

</pre>

Now I could use the gnome-hdaps-applet with the following comands:

{{cmduser|mkdir gnome-hdaps-applet}}
{{cmduser|cd gnome-hdaps-applet}}
{{cmduser|wget http://www.zen24593.zen.co.uk/hdaps/gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|tar -xzf gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|sudo apt-get install libpanel-applet2-dev}}
{{cmduser|gcc $(pkg-config --cflags --libs libpanelapplet-2.0) -o gnome-hdaps-applet gnome-hdaps-applet.c}}
{{cmduser|sudo cp gnome-hdaps-applet /usr/bin/}}
{{cmduser|sudo mkdir /usr/share/pixmaps/gnome-hdaps-applet/}}
{{cmduser|sudo cp *.png /usr/share/pixmaps/gnome-hdaps-applet/}}
$ sudo cp GNOME_HDAPS_StatusApplet.server /usr/lib/bonobo/servers/

Now after a restart of the Gnome Session I could find a "HDAPS Status" applet in the "Add to Panel" dialog. I added it, and when I move the Thinkpad it shows me the "Pause" [[Image:Hdaps-paused-small.png]] Symbol, otherwise it shows "Play" [[Image:Hdaps-running-small.png]].

So far so good !!! After I got this running I tried the same steps with the normal Gutsy Kernel (2.6.22-7-generic) on the same way, and it worked ! To my surprise with the same kernel patch.

The only Problem that I now have is that I cannot use restricted modules with my new kernels. Now I have to figure out how to compile restricted modules agains selfmade kernels.

{{HELP| }}

== The hdapsd - Deamon (next try) ==

I am not satisfied with the above result, because I cannot use the accelerated xorg-fglrx driver for my ATI Graphics Card and I cannot use my wireless Intel card ipw3945 driver. And the Ubuntu restricted-manager is not working. PLEASE can someone help me to compile a Ubuntu kernel in the correct way, so that I can use the whole hardware ?

I have done a - I think really ugly hack - to get the restricted-manager working :

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|cp /boot/config-2.6.20-16-generic /lib/modules/2.6.20-16-generic/.config}}
{{cmdroot|gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -16-generic".
Then I compiled the kernel again with:

{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I moved my modules with :

{{cmdroot|mv /lib/modules/2.6.20-16-generic /lib/modules/2.6.20-16-generic.orginal}}

And installed the kernel with:

{{cmdroot|dpkg -i linux-image-2.6.20-16-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers as described above.
Finally I copied the ipw3945.ucode with

{{cmdroot|cp /lib/firmware/2.6.22-7-generic/ipw3945.ucode /lib/firmware/2.6.20-16-generic/ipw3945.ucode}}

My wireless-card is working now !
My ATI Card cannot be configured with restricted-manager!

{{HELP|Please can someone who is conform in compiling Ubuntu kernels and restricted modules help me to do it in the correct way ! And can someone recheck the things described above, because I am not sure about all things that I have written here.
}}

After some days Ubuntu updated the kernel to version 2.6.22-9-generic, so I need to do the steps described above again, with "EXTRAVERSION = -9-generic". But now my wireless card and my grapics card did not work. The restricted-manager crashes when I start it.
So I downloaded the packages ipw3945-1.2.1.tgz and ati-driver-installer-8.39.4-x86.x86_64.run.

== The Wireless Card ==

First I extracted and installed the Intel Pro Wireless Package:

{{cmduser|tar xzvf ipw3945-1.2.1.tgz}}
{{cmduser|cd ipw3945-1.2.1}}
{{cmduser|make}}
{{cmduser|sudo make install}}

After this I could do :

{{cmduser|sudo modprobe ipw3945}}

The module was loaded, and i was able to use my wireless card now.

== The Graphics Card ==

For my Radeon Mobility X1400 I did the following steps:

{{cmduser|sudo apt get update}}
{{cmduser|sudo apt-get install module-assistant build-essential fakeroot dh-make debhelper debconf libstdc++5}}

Created a Debian Package with:

{{cmduser|sudo bash ati-driver-installer-8.39.4-x86.x86_64.run --buildpkg Ubuntu/gutsy}}

And blacklisted the old fglrx module with:

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

I added "fglrx" to the line with "DISABLED_MODULES". Then I installed the created Debian Packages with:

{{cmduser|sudo dpkg -i xorg-driver-fglrx_8.39.4-1_i386.deb fglrx-kernel-source_8.39.4-1_i386.deb fglrx-amdcccle_8.39.4-1_i386.deb}}

Then I compiled the kernel Modules:

{{cmduser|sudo module-assistant prepare}}
{{cmduser|sudo module-assistant update}}
{{cmduser|sudo module-assistant build fglrx}}
{{cmduser|sudo module-assistant install fglrx}}
{{cmduser|sudo depmod -a}}

The helpful informations for this was found at http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide.

After this steps my wifi-card and my graphics-card was working and restricted-manager was not crashing when I tried to start it.

== After The Kernel Update ==

On 9.October 2007 Ubuntu released the Kernelpackage linux-image-2.6.22-14-generic and I installed it. So here is what I have done to get it working:

{{cmduser|sudo apt-get install linux-headers-generic}}
{{cmduser|sudo ln -s /usr/src/linux-source-2.6.22 /lib/modules/2.6.22-14-generic/source}}
{{cmduser|sudo cd /usr/src/linux}}
{{cmduser|sudo make clean}}
{{cmduser|sudo cp /boot/config-2.6.22-14-generic .config}}
{{cmduser|sudo cp /boot/config-2.6.22-14-generic /lib/modules/2.6.22-14-generic/.config}}
{{cmduser|sudo gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -14-generic".
Then I compiled the kernel again with:

{{cmduser|sudo gedit .config}}

In the .config file I changed the entry " # CONFIG_SND_HDA_INTEL is not set " to " CONFIG_SND_HDA_INTEL=m ". This was needed to compile the module for my sound card.

{{cmduser|sudo make oldconfig}}
{{cmduser|sudo fakeroot make-kpkg clean}}
$ sudo fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I copied my modules with :

{{cmduser|sudo cp -R /lib/modules/2.6.22-14-generic /lib/modules/2.6.22-14-generic.orginal}}

And installed the kernel with:

{{cmduser|dpkg -i linux-image-2.6.22-14-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers with:

{{cmduser|cd /home/dirk/tp_smapi-0.32}}
$ sudo make install HDAPS=1

== The Browser Buttons ==

I wanted to use the Browser Forward & Backward Buttons within Firefox. After the upgrade my Firefox had version 2.0.0.4

I did :

{{cmduser| gedit ~/.Xmodmap}}

and added the following lines :

keycode 234 = F19

keycode 233 = F20

I saved and closed the file. HINT: You have to re-login to Gnome to get the .Xmodmap file active.

Then I did the things described in [http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work#Firefox How to get special keys to work].

For the Windows Key I added "keycode 115 = F13" to my .Xmodmap File, then I klicked on "System - Einstellungen - Tastenkombinationen"
sorry I don't know how it is called in English. And changed the Entry "Das Panelmenü anzeigen" to F13

== The Brightness Buttons ==

When I wanted to control the brightness, I was not able to change it with {{key|Fn}}{{key|End}}.

So I did the Workaround menitioned here [http://thinkwiki.org/wiki/Problem_with_LCD_brightness_buttons#Workaround for Fedora Core 6 Users].
After this I was able to change the brightness with {{key|Fn}}{{key|Home}} and {{key|Fn}}{{key|End}}, but I don't have the OSD anymore.

UPDATE: You don't need to do this since kernel version 2.6.22 on Ubuntu

== The Fingerprint Reader ==

Do the steps which are described in [http://www.thinkwiki.org/wiki/Installing_Ubuntu_6.10_%28Edgy_Eft%29_on_a_ThinkPad_T60#The_Fingerprint_Reader Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60] until you get to the Point where Keithvassallo says:
"Phew. Now, to make applications actually use the fingerprint reader."

I have done the following things instead of his version:

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

Change the file as following:

<pre>
#%PAM-1.0
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
auth requisite pam_nologin.so
auth required pam_env.so
@include common-auth
@include common-account
session required pam_limits.so
@include common-session
@include common-password
</pre>

and:

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

Change this file as following:

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

With this changes you have the advantage, that you are now able to login to Gnome or KDE whitout entering your password. But if you cancel the "Fingerprint Login", you are still able to login whit your username/password combination.

After I was able to login to my desktop I was unsatisfied, because my Computer still wants to get passwords i.e. when I tried to open Synaptic or when I do any sudo actions.

So I tried to figure out how this sudo thing works. I did the following change to /etc/pam.d/sudo with:

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

<pre>
#%PAM-1.0

auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/ :0
password sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam :0
auth required pam_unix.so nillock_secure
@include common-account

</pre>

With this change I was able to open System Administration tasks with my fingerprint, but the ugly thing is, that you get no information to swipe your finger over the reader when you have switched to a console session with {{Key|Ctrl}}+{{Key|Alt}}+{{Key|F1}}. The fingerprint scanner software will appear at your running X session.

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-10-10T07:40:16Z

Dirk: /* After The Kernel Update */

== My Thinkpad ==
<pre>
Lenovo Thinkpad R60 9461 HRG
Intel Core2Duo (Merom) 1.83 CPU
120 GB SATA Hitachi HTS54161 Harddisk
2 GB RAM
ATI Mobility X1400
</pre>

Originally equipped with a preinstalled MS Windows Vista Business. So the Harddisk was parted into two Partitions.

1. The Rescue & Recovery Partition

2. The preinstalled Windows Vista Partition

And as the parcel with my new Thinkpad arrived I was surprized, that there was a Windows Vista DVD (only 32 Bit Version) with it.
So I tried Vista - but I was a little bit shocked by it's performance. I never thought that a new computer could take so much time to boot up completely.

I decided to do a clean install of Vista, but I want to have Windows XP and Ubuntu Feisty on the Harddisk too.

== New Installation ==

I wanted to use all Space of the Harddisk, so I decided to kill the Rescue & and Recovery Partition, but to have the chance to go back to the factory default state I ordered Recovery DVD's at the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4HWSE3#Lenovo Support Call Center for Germany].
They shipped the 3 DVD's to me - free of charge - but I think it's only free if your Thinkpad is still in the warranty. I don't know exactly.

Then I created 2 Partitions on my Harddisk, 64 GB for Vista, 20 GB for XP, so 29 GB left free for Linux.

I installed Vista and XP and all the Thinkpad Stuff for each system.

When this was finished I took a Ubuntu Feisty Fawn installation CD and boot my Notebook with it. I created a 4 GB linux-swap partition and a 25 GB root / partition.

Because I want to boot my Ubuntu with the Windows Vista Boot Loader, I decided to install Grub to /dev/sda4 which is my Linux root partition.

The installation of Ubuntu Feisty Fawn works fine, NO PROBLEMS.

NOW I want to boot Linux from the Vista Bootloader, because I don't want to wait for two Bootscreens, and I wan't to have the chance to access the Repair Console of Windows Vista.

First I have to copy the Bootsector of my Linux Partition with:

<pre>
sudo dd if=/dev/sda4 of=/tmp/bootsect.lin bs=512 count=1
</pre>

Copy the bootsect.lin file to a USB-Stick or a writable partition which you can access from Windows Vista.

Now boot Windows Vista and copy the file bootsect.lin to your Systemdrive. In an Command Window with Administrator privileges type:

<pre>
copy bootsect.lin %SYSTEMDRIVE%\

bcdedit /create /d “Ubuntu” /application BOOTSECTOR
</pre>

You will receice an ID like this {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} from bcdedit. This is a uniqe identifier for your new Boot Entry in the Vista Bootloader. Now you will have to manipulate the entry with the following commands:

<pre>
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} device boot
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} PATH \bootsect.lin
bcdedit /displayorder {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} /addlast
bcdedit /timeout 10
</pre>

Then I booted my Ubuntu an did :

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

In this file I canged the entry the following entries:

<pre>
timeout 2
hiddenmenu
</pre>

So the computer starts up with the Windows Vista bootloader and gives me the option to start Windows XP, Windows Vista, Ubuntu and I have the option to do the repair tasks with the {{key|F8}} button on Vista if something fails. If I choose to boot Ubuntu I have the option to press the {{key|ESC}} key within the two seconds delay of the hidden Grub Menu. I.E. to boot another Linux Kernel.

== The tp_smapi modules ==

I did it under Feisty and, after the Upgrade under Gutsy, like described here : [http://www.thinkwiki.org/wiki/Tp_smapi#Installation TP SMAPI] in the Section "Installation on Ubuntu/Debian"
It worked, hdaps-gl and hdaps-pivot shows me now the movements of my Thinkpad. Like you can see here:

[[Image:Hdaps-pivot.png]]

[[Image:Hdaps-gl.png]]

== The Upgrade to Gutsy Gibbon ==

NO PROBLEMS. So why should I upgrade ?

OK I really wanted to get hdapsd (Harddisk Active Protection) to work. I tried a lot of things with Feisty, but I didn't get it going. And after a lot of seach through the Internet I found out that Gutsy Gibbon, the next Release of Ubuntu should have the Package for hdapsd on board.
SO I decided to upgrade to Gutsy - with the knowledge that it is still in Beta Stadium.

Upgrading Ubuntu is really simple, you only have to do the following steps:

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

Search all feisty entries and change them to gutsy. Save and Close the file.

Do:

{{cmduser| sudo apt-get update}}
{{cmduser| sudo apt-get upgrade}}

Go and drink a cup of Tea or Coffee. When you are back you have a message, that you should reboot your System, to get all packages active. So do it.

After the reboot I installed the hdapsd package and I tried to activate the Harddisk Protection with:

{{cmduser| sudo hdapsd -d sda -s 14 -a -v}}

But I still get the message "open(protect_file): No such file or directory". ---- The Same Message that I get in Feisty before I did the Upgrade. So I banged my head on the table and noticed that I'm not tough enough to get this thing working. Maybe someone else.

I decided to get the other things to work.

UPDATE: After some days I tried to get hdapsd to work, again !

== The hdapsd - Deamon (IBM Active Disk Protection) ==

Because I never had compiled or patched a kernel under Ubuntu I had to find out how this works ! After a lot of search in the Internet, the Ubuntu Help and at Thinkwiki.org I found the (hopefully) correct way to do it.

The best information I found was this :
[http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.04_on_a_ThinkPad_T43#Active_Protection_System_.28acceleration_monitor.29|Installing Ubuntu 7.04 on a ThinkPad T43] in section "Disk protection"

Here is what I did to get it to work:

1. Make sure that you have the required packages, with:

{{cmduser|sudo apt-get install build-essential fakeroot kernel-package libncurses5-dev wget bzip2 linux-source}}

2. Get the correct kernel patch for your running kernel from here : [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch_.28apply_using_.27patch_-p1_-l_.3C_hdaps_xx.patch.27.29| HDAPS] section "8.1.1 Kernel patch (apply using 'patch -p1 -l < hdaps_xx.patch')"

After all my experiences I was not sure that there was a patch available for my Gutsy-kernel (2.6.22-7-generic), but I still had my old kernel on the disk. So I booted up the old one (2.6.20-16-generic). Check the running kernel with:

{{cmduser|uname -r}}

You should see something like: 2.6.20-7-generic

Now change to /usr/src and look that the sources for the running kernel are there with:

{{cmduser|cd /usr/src}}
{{cmduser|ls -d linux-source*}}

You should see a file with the name "linux-source-2.6.20.tar.bz2" wich includes the packed kernel sources. You have to extract it, so do:

{{cmduser|sudo su}}
{{cmdroot|tar xvfj linux-source-2.6.20.tar.bz2}}

Now you have the kernel sources in the /usr/src/linux-source-2.6.20 directory. Take a look if there is a link from /usr/src/linux to an other kernel source directory (It's maybe there if you tried to compile a kernel some time before).

{{cmdroot|ls -l linux}}

If you see that linux is linked to an other source than your running kernel remove the link and create a new one with:

{{cmdroot|rm linux}}
{{cmdroot|ln -s /usr/src/linux-source-2.6.20 linux}}

Change to the source directory and patch the kernel with this:

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|patch -p1 -l < /home/dirk/993-001.bin}}

The file "993-001.bin" is the kernel patch for the 2.6.20 and 2.6.21 kernels, I downloaded it here : [http://article.gmane.org/gmane.linux.drivers.hdaps.devel/993]

After the patchwork I did this :

{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --append-to-version=.hdapscustom kernel_image --initrd binary

This would take its time, so go and clean up your house ;-)
{{HELP|I think the last command (with --append-to-version was an error ! I need help from an specialist in kernel compiling. Please read ahead at the next section "The hdapsd - Deamon (next try)". }}
After your house is clean you can do :

{{cmdroot|cd /usr/src}}
{{cmdroot|ls -l linux*.deb}}

You should see some newly builded Debian Pakage files. Install them with:

{{cmdroot|dpkg -i linux-headers-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-doc-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-image-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-manual-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-source-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}

After the installation you should reboot your computer, when Grub comes up make sure that you select your newly builded kernel.
Check it with:

{{cmduser|uname -r}}

You should see this "2.6.20.3-ubuntu1.hdapscustom". But now you have the Problem, that you have to recompile the tp_smapi driver.

{{cmduser|cd tp_smapi-0.31}}
$ sudo make install HDAPS=1
{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdaps}}

After :

<pre>
$ dmesg | grep hdaps
</pre>

You should see something like this:

[ 893.752000] hdaps: initial mode latch is 0x05
[ 893.752000] hdaps: setting ec_rate=250, filter_order=2
[ 893.752000] hdaps: fake_data_mode set to 0
[ 893.756000] hdaps: device successfully initialized.
[ 893.756000] input: hdaps as /class/input/input10
[ 893.756000] hdaps: driver successfully loaded.

Now we are ready to try out the hdapsd Deamon which is included in the Gutsy repositories, if you are using Feisty you have to compile it yourself like described here: [http://www.thinkwiki.org/wiki/How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS].

{{cmdroot|sudo hdapsd -d sda -s 12 -a -v}}

Should show this:

[[Image:hdapsd.png]]

If you load it with :

{{cmdroot|sudo hdapsd -d sda -s 12 -a}}

You get nothing until you move your Thinkpad, then you see:

Fri Jul 13 12:30:42 2007: parking
Fri Jul 13 12:30:43 2007: un-parking
Fri Jul 13 12:30:44 2007: parking
Fri Jul 13 12:30:45 2007: un-parking

Now, after I have a working hdaps-deamon I want it to be started at boot time. Because I have upgraded to Gutsy and installed the hdapsd - Package I have a script called /etc/default/hdapsd. Here I have to change some things. HINT: Remember that you still need the /etc/init.d/hdapsd file if you try this on Feisty and maybe you have to do:

{{cmduser|sudo update-rc.d hdapsd defaults}}

to create the init links for the hdapsd init script. My links was already there. My /etc/default/hdapsd script now looks like this:

<pre>
# hdapsd default file

# start hdapsd at boottime?
START="yes"

# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
DISK="sda"

# sensitivity
SENSITIVITY=12

# other options to pass to hdapsd.
# the -d $DISK, -s $SENSITIVITY, -b and -p $PIDFILE options are always passed.
OPTIONS="-a"

</pre>

Now I could use the gnome-hdaps-applet with the following comands:

{{cmduser|mkdir gnome-hdaps-applet}}
{{cmduser|cd gnome-hdaps-applet}}
{{cmduser|wget http://www.zen24593.zen.co.uk/hdaps/gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|tar -xzf gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|sudo apt-get install libpanel-applet2-dev}}
{{cmduser|gcc $(pkg-config --cflags --libs libpanelapplet-2.0) -o gnome-hdaps-applet gnome-hdaps-applet.c}}
{{cmduser|sudo cp gnome-hdaps-applet /usr/bin/}}
{{cmduser|sudo mkdir /usr/share/pixmaps/gnome-hdaps-applet/}}
{{cmduser|sudo cp *.png /usr/share/pixmaps/gnome-hdaps-applet/}}
$ sudo cp GNOME_HDAPS_StatusApplet.server /usr/lib/bonobo/servers/

Now after a restart of the Gnome Session I could find a "HDAPS Status" applet in the "Add to Panel" dialog. I added it, and when I move the Thinkpad it shows me the "Pause" [[Image:Hdaps-paused-small.png]] Symbol, otherwise it shows "Play" [[Image:Hdaps-running-small.png]].

So far so good !!! After I got this running I tried the same steps with the normal Gutsy Kernel (2.6.22-7-generic) on the same way, and it worked ! To my surprise with the same kernel patch.

The only Problem that I now have is that I cannot use restricted modules with my new kernels. Now I have to figure out how to compile restricted modules agains selfmade kernels.

{{HELP| }}

== The hdapsd - Deamon (next try) ==

I am not satisfied with the above result, because I cannot use the accelerated xorg-fglrx driver for my ATI Graphics Card and I cannot use my wireless Intel card ipw3945 driver. And the Ubuntu restricted-manager is not working. PLEASE can someone help me to compile a Ubuntu kernel in the correct way, so that I can use the whole hardware ?

I have done a - I think really ugly hack - to get the restricted-manager working :

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|cp /boot/config-2.6.20-16-generic /lib/modules/2.6.20-16-generic/.config}}
{{cmdroot|gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -16-generic".
Then I compiled the kernel again with:

{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I moved my modules with :

{{cmdroot|mv /lib/modules/2.6.20-16-generic /lib/modules/2.6.20-16-generic.orginal}}

And installed the kernel with:

{{cmdroot|dpkg -i linux-image-2.6.20-16-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers as described above.
Finally I copied the ipw3945.ucode with

{{cmdroot|cp /lib/firmware/2.6.22-7-generic/ipw3945.ucode /lib/firmware/2.6.20-16-generic/ipw3945.ucode}}

My wireless-card is working now !
My ATI Card cannot be configured with restricted-manager!

{{HELP|Please can someone who is conform in compiling Ubuntu kernels and restricted modules help me to do it in the correct way ! And can someone recheck the things described above, because I am not sure about all things that I have written here.
}}

After some days Ubuntu updated the kernel to version 2.6.22-9-generic, so I need to do the steps described above again, with "EXTRAVERSION = -9-generic". But now my wireless card and my grapics card did not work. The restricted-manager crashes when I start it.
So I downloaded the packages ipw3945-1.2.1.tgz and ati-driver-installer-8.39.4-x86.x86_64.run.

== The Wireless Card ==

First I extracted and installed the Intel Pro Wireless Package:

{{cmduser|tar xzvf ipw3945-1.2.1.tgz}}
{{cmduser|cd ipw3945-1.2.1}}
{{cmduser|make}}
{{cmduser|sudo make install}}

After this I could do :

{{cmduser|sudo modprobe ipw3945}}

The module was loaded, and i was able to use my wireless card now.

== The Graphics Card ==

For my Radeon Mobility X1400 I did the following steps:

{{cmduser|sudo apt get update}}
{{cmduser|sudo apt-get install module-assistant build-essential fakeroot dh-make debhelper debconf libstdc++5}}

Created a Debian Package with:

{{cmduser|sudo bash ati-driver-installer-8.39.4-x86.x86_64.run --buildpkg Ubuntu/gutsy}}

And blacklisted the old fglrx module with:

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

I added "fglrx" to the line with "DISABLED_MODULES". Then I installed the created Debian Packages with:

{{cmduser|sudo dpkg -i xorg-driver-fglrx_8.39.4-1_i386.deb fglrx-kernel-source_8.39.4-1_i386.deb fglrx-amdcccle_8.39.4-1_i386.deb}}

Then I compiled the kernel Modules:

{{cmduser|sudo module-assistant prepare}}
{{cmduser|sudo module-assistant update}}
{{cmduser|sudo module-assistant build fglrx}}
{{cmduser|sudo module-assistant install fglrx}}
{{cmduser|sudo depmod -a}}

The helpful informations for this was found at http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide.

After this steps my wifi-card and my graphics-card was working and restricted-manager was not crashing when I tried to start it.

== After The Kernel Update ==

On 9.October 2007 Ubuntu released the Kernelpackage linux-image-2.6.22-14-generic and I installed it. So here is what I have done to get it working:

{{cmduser|sudo apt-get install linux-headers-generic}}
{{cmduser|sudo ln -s /usr/src/linux-source-2.6.22 /lib/modules/2.6.22-14-generic/source}}
{{cmduser|sudo cd /usr/src/linux}}
{{cmduser|sudo make clean}}
{{cmduser|sudo cp /boot/config-2.6.22-14-generic .config}}
{{cmduser|sudo cp /boot/config-2.6.22-14-generic /lib/modules/2.6.22-14-generic/.config}}
{{cmduser|sudo gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -14-generic".
Then I compiled the kernel again with:

{{cmduser|sudo gedit .config}}

In the .config file I changed the entry " # CONFIG_SND_HDA_INTEL is not set " to " CONFIG_SND_HDA_INTEL=m ". This was needed to compile the module for my sound card.

{{cmduser|sudo make oldconfig}}
{{cmduser|sudo fakeroot make-kpkg clean}}
# sudo fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I copied my modules with :

{{cmduser|sudo cp -R /lib/modules/2.6.22-14-generic /lib/modules/2.6.22-14-generic.orginal}}

And installed the kernel with:

{{cmduser|dpkg -i linux-image-2.6.22-14-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers with:

{{cmduser|cd /home/dirk/tp_smapi-0.32}}
$ sudo make install HDAPS=1

== The Browser Buttons ==

I wanted to use the Browser Forward & Backward Buttons within Firefox. After the upgrade my Firefox had version 2.0.0.4

I did :

{{cmduser| gedit ~/.Xmodmap}}

and added the following lines :

keycode 234 = F19

keycode 233 = F20

I saved and closed the file. HINT: You have to re-login to Gnome to get the .Xmodmap file active.

Then I did the things described in [http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work#Firefox How to get special keys to work].

For the Windows Key I added "keycode 115 = F13" to my .Xmodmap File, then I klicked on "System - Einstellungen - Tastenkombinationen"
sorry I don't know how it is called in English. And changed the Entry "Das Panelmenü anzeigen" to F13

== The Brightness Buttons ==

When I wanted to control the brightness, I was not able to change it with {{key|Fn}}{{key|End}}.

So I did the Workaround menitioned here [http://thinkwiki.org/wiki/Problem_with_LCD_brightness_buttons#Workaround for Fedora Core 6 Users].
After this I was able to change the brightness with {{key|Fn}}{{key|Home}} and {{key|Fn}}{{key|End}}, but I don't have the OSD anymore.

UPDATE: You don't need to do this since kernel version 2.6.22 on Ubuntu

== The Fingerprint Reader ==

Do the steps which are described in [http://www.thinkwiki.org/wiki/Installing_Ubuntu_6.10_%28Edgy_Eft%29_on_a_ThinkPad_T60#The_Fingerprint_Reader Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60] until you get to the Point where Keithvassallo says:
"Phew. Now, to make applications actually use the fingerprint reader."

I have done the following things instead of his version:

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

Change the file as following:

<pre>
#%PAM-1.0
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
auth requisite pam_nologin.so
auth required pam_env.so
@include common-auth
@include common-account
session required pam_limits.so
@include common-session
@include common-password
</pre>

and:

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

Change this file as following:

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

With this changes you have the advantage, that you are now able to login to Gnome or KDE whitout entering your password. But if you cancel the "Fingerprint Login", you are still able to login whit your username/password combination.

After I was able to login to my desktop I was unsatisfied, because my Computer still wants to get passwords i.e. when I tried to open Synaptic or when I do any sudo actions.

So I tried to figure out how this sudo thing works. I did the following change to /etc/pam.d/sudo with:

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

<pre>
#%PAM-1.0

auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/ :0
password sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam :0
auth required pam_unix.so nillock_secure
@include common-account

</pre>

With this change I was able to open System Administration tasks with my fingerprint, but the ugly thing is, that you get no information to swipe your finger over the reader when you have switched to a console session with {{Key|Ctrl}}+{{Key|Alt}}+{{Key|F1}}. The fingerprint scanner software will appear at your running X session.

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-10-10T07:01:09Z

Dirk: /* The Brightness Buttons */

== My Thinkpad ==
<pre>
Lenovo Thinkpad R60 9461 HRG
Intel Core2Duo (Merom) 1.83 CPU
120 GB SATA Hitachi HTS54161 Harddisk
2 GB RAM
ATI Mobility X1400
</pre>

Originally equipped with a preinstalled MS Windows Vista Business. So the Harddisk was parted into two Partitions.

1. The Rescue & Recovery Partition

2. The preinstalled Windows Vista Partition

And as the parcel with my new Thinkpad arrived I was surprized, that there was a Windows Vista DVD (only 32 Bit Version) with it.
So I tried Vista - but I was a little bit shocked by it's performance. I never thought that a new computer could take so much time to boot up completely.

I decided to do a clean install of Vista, but I want to have Windows XP and Ubuntu Feisty on the Harddisk too.

== New Installation ==

I wanted to use all Space of the Harddisk, so I decided to kill the Rescue & and Recovery Partition, but to have the chance to go back to the factory default state I ordered Recovery DVD's at the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4HWSE3#Lenovo Support Call Center for Germany].
They shipped the 3 DVD's to me - free of charge - but I think it's only free if your Thinkpad is still in the warranty. I don't know exactly.

Then I created 2 Partitions on my Harddisk, 64 GB for Vista, 20 GB for XP, so 29 GB left free for Linux.

I installed Vista and XP and all the Thinkpad Stuff for each system.

When this was finished I took a Ubuntu Feisty Fawn installation CD and boot my Notebook with it. I created a 4 GB linux-swap partition and a 25 GB root / partition.

Because I want to boot my Ubuntu with the Windows Vista Boot Loader, I decided to install Grub to /dev/sda4 which is my Linux root partition.

The installation of Ubuntu Feisty Fawn works fine, NO PROBLEMS.

NOW I want to boot Linux from the Vista Bootloader, because I don't want to wait for two Bootscreens, and I wan't to have the chance to access the Repair Console of Windows Vista.

First I have to copy the Bootsector of my Linux Partition with:

<pre>
sudo dd if=/dev/sda4 of=/tmp/bootsect.lin bs=512 count=1
</pre>

Copy the bootsect.lin file to a USB-Stick or a writable partition which you can access from Windows Vista.

Now boot Windows Vista and copy the file bootsect.lin to your Systemdrive. In an Command Window with Administrator privileges type:

<pre>
copy bootsect.lin %SYSTEMDRIVE%\

bcdedit /create /d “Ubuntu” /application BOOTSECTOR
</pre>

You will receice an ID like this {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} from bcdedit. This is a uniqe identifier for your new Boot Entry in the Vista Bootloader. Now you will have to manipulate the entry with the following commands:

<pre>
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} device boot
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} PATH \bootsect.lin
bcdedit /displayorder {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} /addlast
bcdedit /timeout 10
</pre>

Then I booted my Ubuntu an did :

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

In this file I canged the entry the following entries:

<pre>
timeout 2
hiddenmenu
</pre>

So the computer starts up with the Windows Vista bootloader and gives me the option to start Windows XP, Windows Vista, Ubuntu and I have the option to do the repair tasks with the {{key|F8}} button on Vista if something fails. If I choose to boot Ubuntu I have the option to press the {{key|ESC}} key within the two seconds delay of the hidden Grub Menu. I.E. to boot another Linux Kernel.

== The tp_smapi modules ==

I did it under Feisty and, after the Upgrade under Gutsy, like described here : [http://www.thinkwiki.org/wiki/Tp_smapi#Installation TP SMAPI] in the Section "Installation on Ubuntu/Debian"
It worked, hdaps-gl and hdaps-pivot shows me now the movements of my Thinkpad. Like you can see here:

[[Image:Hdaps-pivot.png]]

[[Image:Hdaps-gl.png]]

== The Upgrade to Gutsy Gibbon ==

NO PROBLEMS. So why should I upgrade ?

OK I really wanted to get hdapsd (Harddisk Active Protection) to work. I tried a lot of things with Feisty, but I didn't get it going. And after a lot of seach through the Internet I found out that Gutsy Gibbon, the next Release of Ubuntu should have the Package for hdapsd on board.
SO I decided to upgrade to Gutsy - with the knowledge that it is still in Beta Stadium.

Upgrading Ubuntu is really simple, you only have to do the following steps:

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

Search all feisty entries and change them to gutsy. Save and Close the file.

Do:

{{cmduser| sudo apt-get update}}
{{cmduser| sudo apt-get upgrade}}

Go and drink a cup of Tea or Coffee. When you are back you have a message, that you should reboot your System, to get all packages active. So do it.

After the reboot I installed the hdapsd package and I tried to activate the Harddisk Protection with:

{{cmduser| sudo hdapsd -d sda -s 14 -a -v}}

But I still get the message "open(protect_file): No such file or directory". ---- The Same Message that I get in Feisty before I did the Upgrade. So I banged my head on the table and noticed that I'm not tough enough to get this thing working. Maybe someone else.

I decided to get the other things to work.

UPDATE: After some days I tried to get hdapsd to work, again !

== The hdapsd - Deamon (IBM Active Disk Protection) ==

Because I never had compiled or patched a kernel under Ubuntu I had to find out how this works ! After a lot of search in the Internet, the Ubuntu Help and at Thinkwiki.org I found the (hopefully) correct way to do it.

The best information I found was this :
[http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.04_on_a_ThinkPad_T43#Active_Protection_System_.28acceleration_monitor.29|Installing Ubuntu 7.04 on a ThinkPad T43] in section "Disk protection"

Here is what I did to get it to work:

1. Make sure that you have the required packages, with:

{{cmduser|sudo apt-get install build-essential fakeroot kernel-package libncurses5-dev wget bzip2 linux-source}}

2. Get the correct kernel patch for your running kernel from here : [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch_.28apply_using_.27patch_-p1_-l_.3C_hdaps_xx.patch.27.29| HDAPS] section "8.1.1 Kernel patch (apply using 'patch -p1 -l < hdaps_xx.patch')"

After all my experiences I was not sure that there was a patch available for my Gutsy-kernel (2.6.22-7-generic), but I still had my old kernel on the disk. So I booted up the old one (2.6.20-16-generic). Check the running kernel with:

{{cmduser|uname -r}}

You should see something like: 2.6.20-7-generic

Now change to /usr/src and look that the sources for the running kernel are there with:

{{cmduser|cd /usr/src}}
{{cmduser|ls -d linux-source*}}

You should see a file with the name "linux-source-2.6.20.tar.bz2" wich includes the packed kernel sources. You have to extract it, so do:

{{cmduser|sudo su}}
{{cmdroot|tar xvfj linux-source-2.6.20.tar.bz2}}

Now you have the kernel sources in the /usr/src/linux-source-2.6.20 directory. Take a look if there is a link from /usr/src/linux to an other kernel source directory (It's maybe there if you tried to compile a kernel some time before).

{{cmdroot|ls -l linux}}

If you see that linux is linked to an other source than your running kernel remove the link and create a new one with:

{{cmdroot|rm linux}}
{{cmdroot|ln -s /usr/src/linux-source-2.6.20 linux}}

Change to the source directory and patch the kernel with this:

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|patch -p1 -l < /home/dirk/993-001.bin}}

The file "993-001.bin" is the kernel patch for the 2.6.20 and 2.6.21 kernels, I downloaded it here : [http://article.gmane.org/gmane.linux.drivers.hdaps.devel/993]

After the patchwork I did this :

{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --append-to-version=.hdapscustom kernel_image --initrd binary

This would take its time, so go and clean up your house ;-)
{{HELP|I think the last command (with --append-to-version was an error ! I need help from an specialist in kernel compiling. Please read ahead at the next section "The hdapsd - Deamon (next try)". }}
After your house is clean you can do :

{{cmdroot|cd /usr/src}}
{{cmdroot|ls -l linux*.deb}}

You should see some newly builded Debian Pakage files. Install them with:

{{cmdroot|dpkg -i linux-headers-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-doc-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-image-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-manual-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-source-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}

After the installation you should reboot your computer, when Grub comes up make sure that you select your newly builded kernel.
Check it with:

{{cmduser|uname -r}}

You should see this "2.6.20.3-ubuntu1.hdapscustom". But now you have the Problem, that you have to recompile the tp_smapi driver.

{{cmduser|cd tp_smapi-0.31}}
$ sudo make install HDAPS=1
{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdaps}}

After :

<pre>
$ dmesg | grep hdaps
</pre>

You should see something like this:

[ 893.752000] hdaps: initial mode latch is 0x05
[ 893.752000] hdaps: setting ec_rate=250, filter_order=2
[ 893.752000] hdaps: fake_data_mode set to 0
[ 893.756000] hdaps: device successfully initialized.
[ 893.756000] input: hdaps as /class/input/input10
[ 893.756000] hdaps: driver successfully loaded.

Now we are ready to try out the hdapsd Deamon which is included in the Gutsy repositories, if you are using Feisty you have to compile it yourself like described here: [http://www.thinkwiki.org/wiki/How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS].

{{cmdroot|sudo hdapsd -d sda -s 12 -a -v}}

Should show this:

[[Image:hdapsd.png]]

If you load it with :

{{cmdroot|sudo hdapsd -d sda -s 12 -a}}

You get nothing until you move your Thinkpad, then you see:

Fri Jul 13 12:30:42 2007: parking
Fri Jul 13 12:30:43 2007: un-parking
Fri Jul 13 12:30:44 2007: parking
Fri Jul 13 12:30:45 2007: un-parking

Now, after I have a working hdaps-deamon I want it to be started at boot time. Because I have upgraded to Gutsy and installed the hdapsd - Package I have a script called /etc/default/hdapsd. Here I have to change some things. HINT: Remember that you still need the /etc/init.d/hdapsd file if you try this on Feisty and maybe you have to do:

{{cmduser|sudo update-rc.d hdapsd defaults}}

to create the init links for the hdapsd init script. My links was already there. My /etc/default/hdapsd script now looks like this:

<pre>
# hdapsd default file

# start hdapsd at boottime?
START="yes"

# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
DISK="sda"

# sensitivity
SENSITIVITY=12

# other options to pass to hdapsd.
# the -d $DISK, -s $SENSITIVITY, -b and -p $PIDFILE options are always passed.
OPTIONS="-a"

</pre>

Now I could use the gnome-hdaps-applet with the following comands:

{{cmduser|mkdir gnome-hdaps-applet}}
{{cmduser|cd gnome-hdaps-applet}}
{{cmduser|wget http://www.zen24593.zen.co.uk/hdaps/gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|tar -xzf gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|sudo apt-get install libpanel-applet2-dev}}
{{cmduser|gcc $(pkg-config --cflags --libs libpanelapplet-2.0) -o gnome-hdaps-applet gnome-hdaps-applet.c}}
{{cmduser|sudo cp gnome-hdaps-applet /usr/bin/}}
{{cmduser|sudo mkdir /usr/share/pixmaps/gnome-hdaps-applet/}}
{{cmduser|sudo cp *.png /usr/share/pixmaps/gnome-hdaps-applet/}}
$ sudo cp GNOME_HDAPS_StatusApplet.server /usr/lib/bonobo/servers/

Now after a restart of the Gnome Session I could find a "HDAPS Status" applet in the "Add to Panel" dialog. I added it, and when I move the Thinkpad it shows me the "Pause" [[Image:Hdaps-paused-small.png]] Symbol, otherwise it shows "Play" [[Image:Hdaps-running-small.png]].

So far so good !!! After I got this running I tried the same steps with the normal Gutsy Kernel (2.6.22-7-generic) on the same way, and it worked ! To my surprise with the same kernel patch.

The only Problem that I now have is that I cannot use restricted modules with my new kernels. Now I have to figure out how to compile restricted modules agains selfmade kernels.

{{HELP| }}

== The hdapsd - Deamon (next try) ==

I am not satisfied with the above result, because I cannot use the accelerated xorg-fglrx driver for my ATI Graphics Card and I cannot use my wireless Intel card ipw3945 driver. And the Ubuntu restricted-manager is not working. PLEASE can someone help me to compile a Ubuntu kernel in the correct way, so that I can use the whole hardware ?

I have done a - I think really ugly hack - to get the restricted-manager working :

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|cp /boot/config-2.6.20-16-generic /lib/modules/2.6.20-16-generic/.config}}
{{cmdroot|gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -16-generic".
Then I compiled the kernel again with:

{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I moved my modules with :

{{cmdroot|mv /lib/modules/2.6.20-16-generic /lib/modules/2.6.20-16-generic.orginal}}

And installed the kernel with:

{{cmdroot|dpkg -i linux-image-2.6.20-16-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers as described above.
Finally I copied the ipw3945.ucode with

{{cmdroot|cp /lib/firmware/2.6.22-7-generic/ipw3945.ucode /lib/firmware/2.6.20-16-generic/ipw3945.ucode}}

My wireless-card is working now !
My ATI Card cannot be configured with restricted-manager!

{{HELP|Please can someone who is conform in compiling Ubuntu kernels and restricted modules help me to do it in the correct way ! And can someone recheck the things described above, because I am not sure about all things that I have written here.
}}

After some days Ubuntu updated the kernel to version 2.6.22-9-generic, so I need to do the steps described above again, with "EXTRAVERSION = -9-generic". But now my wireless card and my grapics card did not work. The restricted-manager crashes when I start it.
So I downloaded the packages ipw3945-1.2.1.tgz and ati-driver-installer-8.39.4-x86.x86_64.run.

== The Wireless Card ==

First I extracted and installed the Intel Pro Wireless Package:

{{cmduser|tar xzvf ipw3945-1.2.1.tgz}}
{{cmduser|cd ipw3945-1.2.1}}
{{cmduser|make}}
{{cmduser|sudo make install}}

After this I could do :

{{cmduser|sudo modprobe ipw3945}}

The module was loaded, and i was able to use my wireless card now.

== The Graphics Card ==

For my Radeon Mobility X1400 I did the following steps:

{{cmduser|sudo apt get update}}
{{cmduser|sudo apt-get install module-assistant build-essential fakeroot dh-make debhelper debconf libstdc++5}}

Created a Debian Package with:

{{cmduser|sudo bash ati-driver-installer-8.39.4-x86.x86_64.run --buildpkg Ubuntu/gutsy}}

And blacklisted the old fglrx module with:

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

I added "fglrx" to the line with "DISABLED_MODULES". Then I installed the created Debian Packages with:

{{cmduser|sudo dpkg -i xorg-driver-fglrx_8.39.4-1_i386.deb fglrx-kernel-source_8.39.4-1_i386.deb fglrx-amdcccle_8.39.4-1_i386.deb}}

Then I compiled the kernel Modules:

{{cmduser|sudo module-assistant prepare}}
{{cmduser|sudo module-assistant update}}
{{cmduser|sudo module-assistant build fglrx}}
{{cmduser|sudo module-assistant install fglrx}}
{{cmduser|sudo depmod -a}}

The helpful informations for this was found at http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide.

After this steps my wifi-card and my graphics-card was working and restricted-manager was not crashing when I tried to start it.

== After The Kernel Update ==

On 9.October 2007 Ubuntu released the Kernelpackage linux-image-2.6.22-14-generic and I installed it. So here is what I have done to get it working:

{{cmduser|sudo apt-get install linux-headers-generic}}
{{cmduser|sudo ln -s /usr/src/linux-source-2.6.22 /lib/modules/2.6.22-14-generic/source}}
{{cmduser|sudo cd /usr/src/linux}}
{{cmduser|sudo make clean}}
{{cmduser|sudo cp /boot/config-2.6.22-14-generic .config}}
{{cmduser|sudo cp /boot/config-2.6.22-14-generic /lib/modules/2.6.22-14-generic/.config}}
{{cmduser|sudo gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -14-generic".
Then I compiled the kernel again with:

{{cmduser|sudo gedit .config}}

In the .config file I changed the entry " # CONFIG_SND_HDA_INTEL is not set " to " CONFIG_SND_HDA_INTEL=m ". This was needed to compile the module for my sound card.

{{cmduser|sudo make oldconfig}}
{{cmduser|sudo fakeroot make-kpkg clean}}
# fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I copied my modules with :

{{cmduser|sudo cp -R /lib/modules/2.6.22-14-generic /lib/modules/2.6.22-14-generic.orginal}}

And installed the kernel with:

{{cmduser|dpkg -i linux-image-2.6.22-14-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers with:

{{cmduser|cd /home/dirk/tp_smapi-0.32}}
$ sudo make install HDAPS=1

== The Browser Buttons ==

I wanted to use the Browser Forward & Backward Buttons within Firefox. After the upgrade my Firefox had version 2.0.0.4

I did :

{{cmduser| gedit ~/.Xmodmap}}

and added the following lines :

keycode 234 = F19

keycode 233 = F20

I saved and closed the file. HINT: You have to re-login to Gnome to get the .Xmodmap file active.

Then I did the things described in [http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work#Firefox How to get special keys to work].

For the Windows Key I added "keycode 115 = F13" to my .Xmodmap File, then I klicked on "System - Einstellungen - Tastenkombinationen"
sorry I don't know how it is called in English. And changed the Entry "Das Panelmenü anzeigen" to F13

== The Brightness Buttons ==

When I wanted to control the brightness, I was not able to change it with {{key|Fn}}{{key|End}}.

So I did the Workaround menitioned here [http://thinkwiki.org/wiki/Problem_with_LCD_brightness_buttons#Workaround for Fedora Core 6 Users].
After this I was able to change the brightness with {{key|Fn}}{{key|Home}} and {{key|Fn}}{{key|End}}, but I don't have the OSD anymore.

UPDATE: You don't need to do this since kernel version 2.6.22 on Ubuntu

== The Fingerprint Reader ==

Do the steps which are described in [http://www.thinkwiki.org/wiki/Installing_Ubuntu_6.10_%28Edgy_Eft%29_on_a_ThinkPad_T60#The_Fingerprint_Reader Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60] until you get to the Point where Keithvassallo says:
"Phew. Now, to make applications actually use the fingerprint reader."

I have done the following things instead of his version:

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

Change the file as following:

<pre>
#%PAM-1.0
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
auth requisite pam_nologin.so
auth required pam_env.so
@include common-auth
@include common-account
session required pam_limits.so
@include common-session
@include common-password
</pre>

and:

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

Change this file as following:

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

With this changes you have the advantage, that you are now able to login to Gnome or KDE whitout entering your password. But if you cancel the "Fingerprint Login", you are still able to login whit your username/password combination.

After I was able to login to my desktop I was unsatisfied, because my Computer still wants to get passwords i.e. when I tried to open Synaptic or when I do any sudo actions.

So I tried to figure out how this sudo thing works. I did the following change to /etc/pam.d/sudo with:

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

<pre>
#%PAM-1.0

auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/ :0
password sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam :0
auth required pam_unix.so nillock_secure
@include common-account

</pre>

With this change I was able to open System Administration tasks with my fingerprint, but the ugly thing is, that you get no information to swipe your finger over the reader when you have switched to a console session with {{Key|Ctrl}}+{{Key|Alt}}+{{Key|F1}}. The fingerprint scanner software will appear at your running X session.

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-10-10T06:58:24Z

Dirk: /* The Browser Buttons */

== My Thinkpad ==
<pre>
Lenovo Thinkpad R60 9461 HRG
Intel Core2Duo (Merom) 1.83 CPU
120 GB SATA Hitachi HTS54161 Harddisk
2 GB RAM
ATI Mobility X1400
</pre>

Originally equipped with a preinstalled MS Windows Vista Business. So the Harddisk was parted into two Partitions.

1. The Rescue & Recovery Partition

2. The preinstalled Windows Vista Partition

And as the parcel with my new Thinkpad arrived I was surprized, that there was a Windows Vista DVD (only 32 Bit Version) with it.
So I tried Vista - but I was a little bit shocked by it's performance. I never thought that a new computer could take so much time to boot up completely.

I decided to do a clean install of Vista, but I want to have Windows XP and Ubuntu Feisty on the Harddisk too.

== New Installation ==

I wanted to use all Space of the Harddisk, so I decided to kill the Rescue & and Recovery Partition, but to have the chance to go back to the factory default state I ordered Recovery DVD's at the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4HWSE3#Lenovo Support Call Center for Germany].
They shipped the 3 DVD's to me - free of charge - but I think it's only free if your Thinkpad is still in the warranty. I don't know exactly.

Then I created 2 Partitions on my Harddisk, 64 GB for Vista, 20 GB for XP, so 29 GB left free for Linux.

I installed Vista and XP and all the Thinkpad Stuff for each system.

When this was finished I took a Ubuntu Feisty Fawn installation CD and boot my Notebook with it. I created a 4 GB linux-swap partition and a 25 GB root / partition.

Because I want to boot my Ubuntu with the Windows Vista Boot Loader, I decided to install Grub to /dev/sda4 which is my Linux root partition.

The installation of Ubuntu Feisty Fawn works fine, NO PROBLEMS.

NOW I want to boot Linux from the Vista Bootloader, because I don't want to wait for two Bootscreens, and I wan't to have the chance to access the Repair Console of Windows Vista.

First I have to copy the Bootsector of my Linux Partition with:

<pre>
sudo dd if=/dev/sda4 of=/tmp/bootsect.lin bs=512 count=1
</pre>

Copy the bootsect.lin file to a USB-Stick or a writable partition which you can access from Windows Vista.

Now boot Windows Vista and copy the file bootsect.lin to your Systemdrive. In an Command Window with Administrator privileges type:

<pre>
copy bootsect.lin %SYSTEMDRIVE%\

bcdedit /create /d “Ubuntu” /application BOOTSECTOR
</pre>

You will receice an ID like this {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} from bcdedit. This is a uniqe identifier for your new Boot Entry in the Vista Bootloader. Now you will have to manipulate the entry with the following commands:

<pre>
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} device boot
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} PATH \bootsect.lin
bcdedit /displayorder {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} /addlast
bcdedit /timeout 10
</pre>

Then I booted my Ubuntu an did :

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

In this file I canged the entry the following entries:

<pre>
timeout 2
hiddenmenu
</pre>

So the computer starts up with the Windows Vista bootloader and gives me the option to start Windows XP, Windows Vista, Ubuntu and I have the option to do the repair tasks with the {{key|F8}} button on Vista if something fails. If I choose to boot Ubuntu I have the option to press the {{key|ESC}} key within the two seconds delay of the hidden Grub Menu. I.E. to boot another Linux Kernel.

== The tp_smapi modules ==

I did it under Feisty and, after the Upgrade under Gutsy, like described here : [http://www.thinkwiki.org/wiki/Tp_smapi#Installation TP SMAPI] in the Section "Installation on Ubuntu/Debian"
It worked, hdaps-gl and hdaps-pivot shows me now the movements of my Thinkpad. Like you can see here:

[[Image:Hdaps-pivot.png]]

[[Image:Hdaps-gl.png]]

== The Upgrade to Gutsy Gibbon ==

NO PROBLEMS. So why should I upgrade ?

OK I really wanted to get hdapsd (Harddisk Active Protection) to work. I tried a lot of things with Feisty, but I didn't get it going. And after a lot of seach through the Internet I found out that Gutsy Gibbon, the next Release of Ubuntu should have the Package for hdapsd on board.
SO I decided to upgrade to Gutsy - with the knowledge that it is still in Beta Stadium.

Upgrading Ubuntu is really simple, you only have to do the following steps:

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

Search all feisty entries and change them to gutsy. Save and Close the file.

Do:

{{cmduser| sudo apt-get update}}
{{cmduser| sudo apt-get upgrade}}

Go and drink a cup of Tea or Coffee. When you are back you have a message, that you should reboot your System, to get all packages active. So do it.

After the reboot I installed the hdapsd package and I tried to activate the Harddisk Protection with:

{{cmduser| sudo hdapsd -d sda -s 14 -a -v}}

But I still get the message "open(protect_file): No such file or directory". ---- The Same Message that I get in Feisty before I did the Upgrade. So I banged my head on the table and noticed that I'm not tough enough to get this thing working. Maybe someone else.

I decided to get the other things to work.

UPDATE: After some days I tried to get hdapsd to work, again !

== The hdapsd - Deamon (IBM Active Disk Protection) ==

Because I never had compiled or patched a kernel under Ubuntu I had to find out how this works ! After a lot of search in the Internet, the Ubuntu Help and at Thinkwiki.org I found the (hopefully) correct way to do it.

The best information I found was this :
[http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.04_on_a_ThinkPad_T43#Active_Protection_System_.28acceleration_monitor.29|Installing Ubuntu 7.04 on a ThinkPad T43] in section "Disk protection"

Here is what I did to get it to work:

1. Make sure that you have the required packages, with:

{{cmduser|sudo apt-get install build-essential fakeroot kernel-package libncurses5-dev wget bzip2 linux-source}}

2. Get the correct kernel patch for your running kernel from here : [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch_.28apply_using_.27patch_-p1_-l_.3C_hdaps_xx.patch.27.29| HDAPS] section "8.1.1 Kernel patch (apply using 'patch -p1 -l < hdaps_xx.patch')"

After all my experiences I was not sure that there was a patch available for my Gutsy-kernel (2.6.22-7-generic), but I still had my old kernel on the disk. So I booted up the old one (2.6.20-16-generic). Check the running kernel with:

{{cmduser|uname -r}}

You should see something like: 2.6.20-7-generic

Now change to /usr/src and look that the sources for the running kernel are there with:

{{cmduser|cd /usr/src}}
{{cmduser|ls -d linux-source*}}

You should see a file with the name "linux-source-2.6.20.tar.bz2" wich includes the packed kernel sources. You have to extract it, so do:

{{cmduser|sudo su}}
{{cmdroot|tar xvfj linux-source-2.6.20.tar.bz2}}

Now you have the kernel sources in the /usr/src/linux-source-2.6.20 directory. Take a look if there is a link from /usr/src/linux to an other kernel source directory (It's maybe there if you tried to compile a kernel some time before).

{{cmdroot|ls -l linux}}

If you see that linux is linked to an other source than your running kernel remove the link and create a new one with:

{{cmdroot|rm linux}}
{{cmdroot|ln -s /usr/src/linux-source-2.6.20 linux}}

Change to the source directory and patch the kernel with this:

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|patch -p1 -l < /home/dirk/993-001.bin}}

The file "993-001.bin" is the kernel patch for the 2.6.20 and 2.6.21 kernels, I downloaded it here : [http://article.gmane.org/gmane.linux.drivers.hdaps.devel/993]

After the patchwork I did this :

{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --append-to-version=.hdapscustom kernel_image --initrd binary

This would take its time, so go and clean up your house ;-)
{{HELP|I think the last command (with --append-to-version was an error ! I need help from an specialist in kernel compiling. Please read ahead at the next section "The hdapsd - Deamon (next try)". }}
After your house is clean you can do :

{{cmdroot|cd /usr/src}}
{{cmdroot|ls -l linux*.deb}}

You should see some newly builded Debian Pakage files. Install them with:

{{cmdroot|dpkg -i linux-headers-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-doc-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-image-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-manual-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-source-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}

After the installation you should reboot your computer, when Grub comes up make sure that you select your newly builded kernel.
Check it with:

{{cmduser|uname -r}}

You should see this "2.6.20.3-ubuntu1.hdapscustom". But now you have the Problem, that you have to recompile the tp_smapi driver.

{{cmduser|cd tp_smapi-0.31}}
$ sudo make install HDAPS=1
{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdaps}}

After :

<pre>
$ dmesg | grep hdaps
</pre>

You should see something like this:

[ 893.752000] hdaps: initial mode latch is 0x05
[ 893.752000] hdaps: setting ec_rate=250, filter_order=2
[ 893.752000] hdaps: fake_data_mode set to 0
[ 893.756000] hdaps: device successfully initialized.
[ 893.756000] input: hdaps as /class/input/input10
[ 893.756000] hdaps: driver successfully loaded.

Now we are ready to try out the hdapsd Deamon which is included in the Gutsy repositories, if you are using Feisty you have to compile it yourself like described here: [http://www.thinkwiki.org/wiki/How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS].

{{cmdroot|sudo hdapsd -d sda -s 12 -a -v}}

Should show this:

[[Image:hdapsd.png]]

If you load it with :

{{cmdroot|sudo hdapsd -d sda -s 12 -a}}

You get nothing until you move your Thinkpad, then you see:

Fri Jul 13 12:30:42 2007: parking
Fri Jul 13 12:30:43 2007: un-parking
Fri Jul 13 12:30:44 2007: parking
Fri Jul 13 12:30:45 2007: un-parking

Now, after I have a working hdaps-deamon I want it to be started at boot time. Because I have upgraded to Gutsy and installed the hdapsd - Package I have a script called /etc/default/hdapsd. Here I have to change some things. HINT: Remember that you still need the /etc/init.d/hdapsd file if you try this on Feisty and maybe you have to do:

{{cmduser|sudo update-rc.d hdapsd defaults}}

to create the init links for the hdapsd init script. My links was already there. My /etc/default/hdapsd script now looks like this:

<pre>
# hdapsd default file

# start hdapsd at boottime?
START="yes"

# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
DISK="sda"

# sensitivity
SENSITIVITY=12

# other options to pass to hdapsd.
# the -d $DISK, -s $SENSITIVITY, -b and -p $PIDFILE options are always passed.
OPTIONS="-a"

</pre>

Now I could use the gnome-hdaps-applet with the following comands:

{{cmduser|mkdir gnome-hdaps-applet}}
{{cmduser|cd gnome-hdaps-applet}}
{{cmduser|wget http://www.zen24593.zen.co.uk/hdaps/gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|tar -xzf gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|sudo apt-get install libpanel-applet2-dev}}
{{cmduser|gcc $(pkg-config --cflags --libs libpanelapplet-2.0) -o gnome-hdaps-applet gnome-hdaps-applet.c}}
{{cmduser|sudo cp gnome-hdaps-applet /usr/bin/}}
{{cmduser|sudo mkdir /usr/share/pixmaps/gnome-hdaps-applet/}}
{{cmduser|sudo cp *.png /usr/share/pixmaps/gnome-hdaps-applet/}}
$ sudo cp GNOME_HDAPS_StatusApplet.server /usr/lib/bonobo/servers/

Now after a restart of the Gnome Session I could find a "HDAPS Status" applet in the "Add to Panel" dialog. I added it, and when I move the Thinkpad it shows me the "Pause" [[Image:Hdaps-paused-small.png]] Symbol, otherwise it shows "Play" [[Image:Hdaps-running-small.png]].

So far so good !!! After I got this running I tried the same steps with the normal Gutsy Kernel (2.6.22-7-generic) on the same way, and it worked ! To my surprise with the same kernel patch.

The only Problem that I now have is that I cannot use restricted modules with my new kernels. Now I have to figure out how to compile restricted modules agains selfmade kernels.

{{HELP| }}

== The hdapsd - Deamon (next try) ==

I am not satisfied with the above result, because I cannot use the accelerated xorg-fglrx driver for my ATI Graphics Card and I cannot use my wireless Intel card ipw3945 driver. And the Ubuntu restricted-manager is not working. PLEASE can someone help me to compile a Ubuntu kernel in the correct way, so that I can use the whole hardware ?

I have done a - I think really ugly hack - to get the restricted-manager working :

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|cp /boot/config-2.6.20-16-generic /lib/modules/2.6.20-16-generic/.config}}
{{cmdroot|gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -16-generic".
Then I compiled the kernel again with:

{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I moved my modules with :

{{cmdroot|mv /lib/modules/2.6.20-16-generic /lib/modules/2.6.20-16-generic.orginal}}

And installed the kernel with:

{{cmdroot|dpkg -i linux-image-2.6.20-16-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers as described above.
Finally I copied the ipw3945.ucode with

{{cmdroot|cp /lib/firmware/2.6.22-7-generic/ipw3945.ucode /lib/firmware/2.6.20-16-generic/ipw3945.ucode}}

My wireless-card is working now !
My ATI Card cannot be configured with restricted-manager!

{{HELP|Please can someone who is conform in compiling Ubuntu kernels and restricted modules help me to do it in the correct way ! And can someone recheck the things described above, because I am not sure about all things that I have written here.
}}

After some days Ubuntu updated the kernel to version 2.6.22-9-generic, so I need to do the steps described above again, with "EXTRAVERSION = -9-generic". But now my wireless card and my grapics card did not work. The restricted-manager crashes when I start it.
So I downloaded the packages ipw3945-1.2.1.tgz and ati-driver-installer-8.39.4-x86.x86_64.run.

== The Wireless Card ==

First I extracted and installed the Intel Pro Wireless Package:

{{cmduser|tar xzvf ipw3945-1.2.1.tgz}}
{{cmduser|cd ipw3945-1.2.1}}
{{cmduser|make}}
{{cmduser|sudo make install}}

After this I could do :

{{cmduser|sudo modprobe ipw3945}}

The module was loaded, and i was able to use my wireless card now.

== The Graphics Card ==

For my Radeon Mobility X1400 I did the following steps:

{{cmduser|sudo apt get update}}
{{cmduser|sudo apt-get install module-assistant build-essential fakeroot dh-make debhelper debconf libstdc++5}}

Created a Debian Package with:

{{cmduser|sudo bash ati-driver-installer-8.39.4-x86.x86_64.run --buildpkg Ubuntu/gutsy}}

And blacklisted the old fglrx module with:

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

I added "fglrx" to the line with "DISABLED_MODULES". Then I installed the created Debian Packages with:

{{cmduser|sudo dpkg -i xorg-driver-fglrx_8.39.4-1_i386.deb fglrx-kernel-source_8.39.4-1_i386.deb fglrx-amdcccle_8.39.4-1_i386.deb}}

Then I compiled the kernel Modules:

{{cmduser|sudo module-assistant prepare}}
{{cmduser|sudo module-assistant update}}
{{cmduser|sudo module-assistant build fglrx}}
{{cmduser|sudo module-assistant install fglrx}}
{{cmduser|sudo depmod -a}}

The helpful informations for this was found at http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide.

After this steps my wifi-card and my graphics-card was working and restricted-manager was not crashing when I tried to start it.

== After The Kernel Update ==

On 9.October 2007 Ubuntu released the Kernelpackage linux-image-2.6.22-14-generic and I installed it. So here is what I have done to get it working:

{{cmduser|sudo apt-get install linux-headers-generic}}
{{cmduser|sudo ln -s /usr/src/linux-source-2.6.22 /lib/modules/2.6.22-14-generic/source}}
{{cmduser|sudo cd /usr/src/linux}}
{{cmduser|sudo make clean}}
{{cmduser|sudo cp /boot/config-2.6.22-14-generic .config}}
{{cmduser|sudo cp /boot/config-2.6.22-14-generic /lib/modules/2.6.22-14-generic/.config}}
{{cmduser|sudo gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -14-generic".
Then I compiled the kernel again with:

{{cmduser|sudo gedit .config}}

In the .config file I changed the entry " # CONFIG_SND_HDA_INTEL is not set " to " CONFIG_SND_HDA_INTEL=m ". This was needed to compile the module for my sound card.

{{cmduser|sudo make oldconfig}}
{{cmduser|sudo fakeroot make-kpkg clean}}
# fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I copied my modules with :

{{cmduser|sudo cp -R /lib/modules/2.6.22-14-generic /lib/modules/2.6.22-14-generic.orginal}}

And installed the kernel with:

{{cmduser|dpkg -i linux-image-2.6.22-14-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers with:

{{cmduser|cd /home/dirk/tp_smapi-0.32}}
$ sudo make install HDAPS=1

== The Browser Buttons ==

I wanted to use the Browser Forward & Backward Buttons within Firefox. After the upgrade my Firefox had version 2.0.0.4

I did :

{{cmduser| gedit ~/.Xmodmap}}

and added the following lines :

keycode 234 = F19

keycode 233 = F20

I saved and closed the file. HINT: You have to re-login to Gnome to get the .Xmodmap file active.

Then I did the things described in [http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work#Firefox How to get special keys to work].

For the Windows Key I added "keycode 115 = F13" to my .Xmodmap File, then I klicked on "System - Einstellungen - Tastenkombinationen"
sorry I don't know how it is called in English. And changed the Entry "Das Panelmenü anzeigen" to F13

== The Brightness Buttons ==

When I wanted to control the brightness, I was not able to change it with {{key|Fn}}{{key|End}}.

So I did the Workaround menitioned here [http://thinkwiki.org/wiki/Problem_with_LCD_brightness_buttons#Workaround for Fedora Core 6 Users].
After this I was able to change the brightness with {{key|Fn}}{{key|Home}} and {{key|Fn}}{{key|End}}, but I don't have the OSD anymore.

== The Fingerprint Reader ==

Do the steps which are described in [http://www.thinkwiki.org/wiki/Installing_Ubuntu_6.10_%28Edgy_Eft%29_on_a_ThinkPad_T60#The_Fingerprint_Reader Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60] until you get to the Point where Keithvassallo says:
"Phew. Now, to make applications actually use the fingerprint reader."

I have done the following things instead of his version:

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

Change the file as following:

<pre>
#%PAM-1.0
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
auth requisite pam_nologin.so
auth required pam_env.so
@include common-auth
@include common-account
session required pam_limits.so
@include common-session
@include common-password
</pre>

and:

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

Change this file as following:

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

With this changes you have the advantage, that you are now able to login to Gnome or KDE whitout entering your password. But if you cancel the "Fingerprint Login", you are still able to login whit your username/password combination.

After I was able to login to my desktop I was unsatisfied, because my Computer still wants to get passwords i.e. when I tried to open Synaptic or when I do any sudo actions.

So I tried to figure out how this sudo thing works. I did the following change to /etc/pam.d/sudo with:

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

<pre>
#%PAM-1.0

auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/ :0
password sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam :0
auth required pam_unix.so nillock_secure
@include common-account

</pre>

With this change I was able to open System Administration tasks with my fingerprint, but the ugly thing is, that you get no information to swipe your finger over the reader when you have switched to a console session with {{Key|Ctrl}}+{{Key|Alt}}+{{Key|F1}}. The fingerprint scanner software will appear at your running X session.

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-10-10T06:55:08Z

Dirk:

== My Thinkpad ==
<pre>
Lenovo Thinkpad R60 9461 HRG
Intel Core2Duo (Merom) 1.83 CPU
120 GB SATA Hitachi HTS54161 Harddisk
2 GB RAM
ATI Mobility X1400
</pre>

Originally equipped with a preinstalled MS Windows Vista Business. So the Harddisk was parted into two Partitions.

1. The Rescue & Recovery Partition

2. The preinstalled Windows Vista Partition

And as the parcel with my new Thinkpad arrived I was surprized, that there was a Windows Vista DVD (only 32 Bit Version) with it.
So I tried Vista - but I was a little bit shocked by it's performance. I never thought that a new computer could take so much time to boot up completely.

I decided to do a clean install of Vista, but I want to have Windows XP and Ubuntu Feisty on the Harddisk too.

== New Installation ==

I wanted to use all Space of the Harddisk, so I decided to kill the Rescue & and Recovery Partition, but to have the chance to go back to the factory default state I ordered Recovery DVD's at the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4HWSE3#Lenovo Support Call Center for Germany].
They shipped the 3 DVD's to me - free of charge - but I think it's only free if your Thinkpad is still in the warranty. I don't know exactly.

Then I created 2 Partitions on my Harddisk, 64 GB for Vista, 20 GB for XP, so 29 GB left free for Linux.

I installed Vista and XP and all the Thinkpad Stuff for each system.

When this was finished I took a Ubuntu Feisty Fawn installation CD and boot my Notebook with it. I created a 4 GB linux-swap partition and a 25 GB root / partition.

Because I want to boot my Ubuntu with the Windows Vista Boot Loader, I decided to install Grub to /dev/sda4 which is my Linux root partition.

The installation of Ubuntu Feisty Fawn works fine, NO PROBLEMS.

NOW I want to boot Linux from the Vista Bootloader, because I don't want to wait for two Bootscreens, and I wan't to have the chance to access the Repair Console of Windows Vista.

First I have to copy the Bootsector of my Linux Partition with:

<pre>
sudo dd if=/dev/sda4 of=/tmp/bootsect.lin bs=512 count=1
</pre>

Copy the bootsect.lin file to a USB-Stick or a writable partition which you can access from Windows Vista.

Now boot Windows Vista and copy the file bootsect.lin to your Systemdrive. In an Command Window with Administrator privileges type:

<pre>
copy bootsect.lin %SYSTEMDRIVE%\

bcdedit /create /d “Ubuntu” /application BOOTSECTOR
</pre>

You will receice an ID like this {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} from bcdedit. This is a uniqe identifier for your new Boot Entry in the Vista Bootloader. Now you will have to manipulate the entry with the following commands:

<pre>
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} device boot
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} PATH \bootsect.lin
bcdedit /displayorder {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} /addlast
bcdedit /timeout 10
</pre>

Then I booted my Ubuntu an did :

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

In this file I canged the entry the following entries:

<pre>
timeout 2
hiddenmenu
</pre>

So the computer starts up with the Windows Vista bootloader and gives me the option to start Windows XP, Windows Vista, Ubuntu and I have the option to do the repair tasks with the {{key|F8}} button on Vista if something fails. If I choose to boot Ubuntu I have the option to press the {{key|ESC}} key within the two seconds delay of the hidden Grub Menu. I.E. to boot another Linux Kernel.

== The tp_smapi modules ==

I did it under Feisty and, after the Upgrade under Gutsy, like described here : [http://www.thinkwiki.org/wiki/Tp_smapi#Installation TP SMAPI] in the Section "Installation on Ubuntu/Debian"
It worked, hdaps-gl and hdaps-pivot shows me now the movements of my Thinkpad. Like you can see here:

[[Image:Hdaps-pivot.png]]

[[Image:Hdaps-gl.png]]

== The Upgrade to Gutsy Gibbon ==

NO PROBLEMS. So why should I upgrade ?

OK I really wanted to get hdapsd (Harddisk Active Protection) to work. I tried a lot of things with Feisty, but I didn't get it going. And after a lot of seach through the Internet I found out that Gutsy Gibbon, the next Release of Ubuntu should have the Package for hdapsd on board.
SO I decided to upgrade to Gutsy - with the knowledge that it is still in Beta Stadium.

Upgrading Ubuntu is really simple, you only have to do the following steps:

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

Search all feisty entries and change them to gutsy. Save and Close the file.

Do:

{{cmduser| sudo apt-get update}}
{{cmduser| sudo apt-get upgrade}}

Go and drink a cup of Tea or Coffee. When you are back you have a message, that you should reboot your System, to get all packages active. So do it.

After the reboot I installed the hdapsd package and I tried to activate the Harddisk Protection with:

{{cmduser| sudo hdapsd -d sda -s 14 -a -v}}

But I still get the message "open(protect_file): No such file or directory". ---- The Same Message that I get in Feisty before I did the Upgrade. So I banged my head on the table and noticed that I'm not tough enough to get this thing working. Maybe someone else.

I decided to get the other things to work.

UPDATE: After some days I tried to get hdapsd to work, again !

== The hdapsd - Deamon (IBM Active Disk Protection) ==

Because I never had compiled or patched a kernel under Ubuntu I had to find out how this works ! After a lot of search in the Internet, the Ubuntu Help and at Thinkwiki.org I found the (hopefully) correct way to do it.

The best information I found was this :
[http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.04_on_a_ThinkPad_T43#Active_Protection_System_.28acceleration_monitor.29|Installing Ubuntu 7.04 on a ThinkPad T43] in section "Disk protection"

Here is what I did to get it to work:

1. Make sure that you have the required packages, with:

{{cmduser|sudo apt-get install build-essential fakeroot kernel-package libncurses5-dev wget bzip2 linux-source}}

2. Get the correct kernel patch for your running kernel from here : [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch_.28apply_using_.27patch_-p1_-l_.3C_hdaps_xx.patch.27.29| HDAPS] section "8.1.1 Kernel patch (apply using 'patch -p1 -l < hdaps_xx.patch')"

After all my experiences I was not sure that there was a patch available for my Gutsy-kernel (2.6.22-7-generic), but I still had my old kernel on the disk. So I booted up the old one (2.6.20-16-generic). Check the running kernel with:

{{cmduser|uname -r}}

You should see something like: 2.6.20-7-generic

Now change to /usr/src and look that the sources for the running kernel are there with:

{{cmduser|cd /usr/src}}
{{cmduser|ls -d linux-source*}}

You should see a file with the name "linux-source-2.6.20.tar.bz2" wich includes the packed kernel sources. You have to extract it, so do:

{{cmduser|sudo su}}
{{cmdroot|tar xvfj linux-source-2.6.20.tar.bz2}}

Now you have the kernel sources in the /usr/src/linux-source-2.6.20 directory. Take a look if there is a link from /usr/src/linux to an other kernel source directory (It's maybe there if you tried to compile a kernel some time before).

{{cmdroot|ls -l linux}}

If you see that linux is linked to an other source than your running kernel remove the link and create a new one with:

{{cmdroot|rm linux}}
{{cmdroot|ln -s /usr/src/linux-source-2.6.20 linux}}

Change to the source directory and patch the kernel with this:

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|patch -p1 -l < /home/dirk/993-001.bin}}

The file "993-001.bin" is the kernel patch for the 2.6.20 and 2.6.21 kernels, I downloaded it here : [http://article.gmane.org/gmane.linux.drivers.hdaps.devel/993]

After the patchwork I did this :

{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --append-to-version=.hdapscustom kernel_image --initrd binary

This would take its time, so go and clean up your house ;-)
{{HELP|I think the last command (with --append-to-version was an error ! I need help from an specialist in kernel compiling. Please read ahead at the next section "The hdapsd - Deamon (next try)". }}
After your house is clean you can do :

{{cmdroot|cd /usr/src}}
{{cmdroot|ls -l linux*.deb}}

You should see some newly builded Debian Pakage files. Install them with:

{{cmdroot|dpkg -i linux-headers-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-doc-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-image-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-manual-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-source-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}

After the installation you should reboot your computer, when Grub comes up make sure that you select your newly builded kernel.
Check it with:

{{cmduser|uname -r}}

You should see this "2.6.20.3-ubuntu1.hdapscustom". But now you have the Problem, that you have to recompile the tp_smapi driver.

{{cmduser|cd tp_smapi-0.31}}
$ sudo make install HDAPS=1
{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdaps}}

After :

<pre>
$ dmesg | grep hdaps
</pre>

You should see something like this:

[ 893.752000] hdaps: initial mode latch is 0x05
[ 893.752000] hdaps: setting ec_rate=250, filter_order=2
[ 893.752000] hdaps: fake_data_mode set to 0
[ 893.756000] hdaps: device successfully initialized.
[ 893.756000] input: hdaps as /class/input/input10
[ 893.756000] hdaps: driver successfully loaded.

Now we are ready to try out the hdapsd Deamon which is included in the Gutsy repositories, if you are using Feisty you have to compile it yourself like described here: [http://www.thinkwiki.org/wiki/How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS].

{{cmdroot|sudo hdapsd -d sda -s 12 -a -v}}

Should show this:

[[Image:hdapsd.png]]

If you load it with :

{{cmdroot|sudo hdapsd -d sda -s 12 -a}}

You get nothing until you move your Thinkpad, then you see:

Fri Jul 13 12:30:42 2007: parking
Fri Jul 13 12:30:43 2007: un-parking
Fri Jul 13 12:30:44 2007: parking
Fri Jul 13 12:30:45 2007: un-parking

Now, after I have a working hdaps-deamon I want it to be started at boot time. Because I have upgraded to Gutsy and installed the hdapsd - Package I have a script called /etc/default/hdapsd. Here I have to change some things. HINT: Remember that you still need the /etc/init.d/hdapsd file if you try this on Feisty and maybe you have to do:

{{cmduser|sudo update-rc.d hdapsd defaults}}

to create the init links for the hdapsd init script. My links was already there. My /etc/default/hdapsd script now looks like this:

<pre>
# hdapsd default file

# start hdapsd at boottime?
START="yes"

# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
DISK="sda"

# sensitivity
SENSITIVITY=12

# other options to pass to hdapsd.
# the -d $DISK, -s $SENSITIVITY, -b and -p $PIDFILE options are always passed.
OPTIONS="-a"

</pre>

Now I could use the gnome-hdaps-applet with the following comands:

{{cmduser|mkdir gnome-hdaps-applet}}
{{cmduser|cd gnome-hdaps-applet}}
{{cmduser|wget http://www.zen24593.zen.co.uk/hdaps/gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|tar -xzf gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|sudo apt-get install libpanel-applet2-dev}}
{{cmduser|gcc $(pkg-config --cflags --libs libpanelapplet-2.0) -o gnome-hdaps-applet gnome-hdaps-applet.c}}
{{cmduser|sudo cp gnome-hdaps-applet /usr/bin/}}
{{cmduser|sudo mkdir /usr/share/pixmaps/gnome-hdaps-applet/}}
{{cmduser|sudo cp *.png /usr/share/pixmaps/gnome-hdaps-applet/}}
$ sudo cp GNOME_HDAPS_StatusApplet.server /usr/lib/bonobo/servers/

Now after a restart of the Gnome Session I could find a "HDAPS Status" applet in the "Add to Panel" dialog. I added it, and when I move the Thinkpad it shows me the "Pause" [[Image:Hdaps-paused-small.png]] Symbol, otherwise it shows "Play" [[Image:Hdaps-running-small.png]].

So far so good !!! After I got this running I tried the same steps with the normal Gutsy Kernel (2.6.22-7-generic) on the same way, and it worked ! To my surprise with the same kernel patch.

The only Problem that I now have is that I cannot use restricted modules with my new kernels. Now I have to figure out how to compile restricted modules agains selfmade kernels.

{{HELP| }}

== The hdapsd - Deamon (next try) ==

I am not satisfied with the above result, because I cannot use the accelerated xorg-fglrx driver for my ATI Graphics Card and I cannot use my wireless Intel card ipw3945 driver. And the Ubuntu restricted-manager is not working. PLEASE can someone help me to compile a Ubuntu kernel in the correct way, so that I can use the whole hardware ?

I have done a - I think really ugly hack - to get the restricted-manager working :

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|cp /boot/config-2.6.20-16-generic /lib/modules/2.6.20-16-generic/.config}}
{{cmdroot|gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -16-generic".
Then I compiled the kernel again with:

{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I moved my modules with :

{{cmdroot|mv /lib/modules/2.6.20-16-generic /lib/modules/2.6.20-16-generic.orginal}}

And installed the kernel with:

{{cmdroot|dpkg -i linux-image-2.6.20-16-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers as described above.
Finally I copied the ipw3945.ucode with

{{cmdroot|cp /lib/firmware/2.6.22-7-generic/ipw3945.ucode /lib/firmware/2.6.20-16-generic/ipw3945.ucode}}

My wireless-card is working now !
My ATI Card cannot be configured with restricted-manager!

{{HELP|Please can someone who is conform in compiling Ubuntu kernels and restricted modules help me to do it in the correct way ! And can someone recheck the things described above, because I am not sure about all things that I have written here.
}}

After some days Ubuntu updated the kernel to version 2.6.22-9-generic, so I need to do the steps described above again, with "EXTRAVERSION = -9-generic". But now my wireless card and my grapics card did not work. The restricted-manager crashes when I start it.
So I downloaded the packages ipw3945-1.2.1.tgz and ati-driver-installer-8.39.4-x86.x86_64.run.

== The Wireless Card ==

First I extracted and installed the Intel Pro Wireless Package:

{{cmduser|tar xzvf ipw3945-1.2.1.tgz}}
{{cmduser|cd ipw3945-1.2.1}}
{{cmduser|make}}
{{cmduser|sudo make install}}

After this I could do :

{{cmduser|sudo modprobe ipw3945}}

The module was loaded, and i was able to use my wireless card now.

== The Graphics Card ==

For my Radeon Mobility X1400 I did the following steps:

{{cmduser|sudo apt get update}}
{{cmduser|sudo apt-get install module-assistant build-essential fakeroot dh-make debhelper debconf libstdc++5}}

Created a Debian Package with:

{{cmduser|sudo bash ati-driver-installer-8.39.4-x86.x86_64.run --buildpkg Ubuntu/gutsy}}

And blacklisted the old fglrx module with:

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

I added "fglrx" to the line with "DISABLED_MODULES". Then I installed the created Debian Packages with:

{{cmduser|sudo dpkg -i xorg-driver-fglrx_8.39.4-1_i386.deb fglrx-kernel-source_8.39.4-1_i386.deb fglrx-amdcccle_8.39.4-1_i386.deb}}

Then I compiled the kernel Modules:

{{cmduser|sudo module-assistant prepare}}
{{cmduser|sudo module-assistant update}}
{{cmduser|sudo module-assistant build fglrx}}
{{cmduser|sudo module-assistant install fglrx}}
{{cmduser|sudo depmod -a}}

The helpful informations for this was found at http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide.

After this steps my wifi-card and my graphics-card was working and restricted-manager was not crashing when I tried to start it.

== After The Kernel Update ==

On 9.October 2007 Ubuntu released the Kernelpackage linux-image-2.6.22-14-generic and I installed it. So here is what I have done to get it working:

{{cmduser|sudo apt-get install linux-headers-generic}}
{{cmduser|sudo ln -s /usr/src/linux-source-2.6.22 /lib/modules/2.6.22-14-generic/source}}
{{cmduser|sudo cd /usr/src/linux}}
{{cmduser|sudo make clean}}
{{cmduser|sudo cp /boot/config-2.6.22-14-generic .config}}
{{cmduser|sudo cp /boot/config-2.6.22-14-generic /lib/modules/2.6.22-14-generic/.config}}
{{cmduser|sudo gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -14-generic".
Then I compiled the kernel again with:

{{cmduser|sudo gedit .config}}

In the .config file I changed the entry " # CONFIG_SND_HDA_INTEL is not set " to " CONFIG_SND_HDA_INTEL=m ". This was needed to compile the module for my sound card.

{{cmduser|sudo make oldconfig}}
{{cmduser|sudo fakeroot make-kpkg clean}}
# fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I copied my modules with :

{{cmduser|sudo cp -R /lib/modules/2.6.22-14-generic /lib/modules/2.6.22-14-generic.orginal}}

And installed the kernel with:

{{cmduser|dpkg -i linux-image-2.6.22-14-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers with:

{{cmduser|cd /home/dirk/tp_smapi-0.32}}
$ sudo make install HDAPS=1

== The Browser Buttons ==

I wanted to use the Browser Forward & Backward Buttons within Firefox. After the upgrade my Firefox had version 2.0.0.4

I did :

{{cmduser| sudo gedit ~/.Xmodmap}}

and added the following lines :

keycode 234 = F19

keycode 233 = F20

I saved and closed the file. HINT: You have to re-login to Gnome to get the .Xmodmap file active.

Then I did the things described in [http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work#Firefox How to get special keys to work].

For the Windows Key I added "keycode 115 = F13" to my .Xmodmap File, then I klicked on "System - Einstellungen - Tastenkombinationen"
sorry I don't know how it is called in English. And changed the Entry "Das Panelmenü anzeigen" to F13

== The Brightness Buttons ==

When I wanted to control the brightness, I was not able to change it with {{key|Fn}}{{key|End}}.

So I did the Workaround menitioned here [http://thinkwiki.org/wiki/Problem_with_LCD_brightness_buttons#Workaround for Fedora Core 6 Users].
After this I was able to change the brightness with {{key|Fn}}{{key|Home}} and {{key|Fn}}{{key|End}}, but I don't have the OSD anymore.

== The Fingerprint Reader ==

Do the steps which are described in [http://www.thinkwiki.org/wiki/Installing_Ubuntu_6.10_%28Edgy_Eft%29_on_a_ThinkPad_T60#The_Fingerprint_Reader Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60] until you get to the Point where Keithvassallo says:
"Phew. Now, to make applications actually use the fingerprint reader."

I have done the following things instead of his version:

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

Change the file as following:

<pre>
#%PAM-1.0
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
auth requisite pam_nologin.so
auth required pam_env.so
@include common-auth
@include common-account
session required pam_limits.so
@include common-session
@include common-password
</pre>

and:

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

Change this file as following:

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

With this changes you have the advantage, that you are now able to login to Gnome or KDE whitout entering your password. But if you cancel the "Fingerprint Login", you are still able to login whit your username/password combination.

After I was able to login to my desktop I was unsatisfied, because my Computer still wants to get passwords i.e. when I tried to open Synaptic or when I do any sudo actions.

So I tried to figure out how this sudo thing works. I did the following change to /etc/pam.d/sudo with:

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

<pre>
#%PAM-1.0

auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/ :0
password sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam :0
auth required pam_unix.so nillock_secure
@include common-account

</pre>

With this change I was able to open System Administration tasks with my fingerprint, but the ugly thing is, that you get no information to swipe your finger over the reader when you have switched to a console session with {{Key|Ctrl}}+{{Key|Alt}}+{{Key|F1}}. The fingerprint scanner software will appear at your running X session.

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-10-10T06:53:20Z

Dirk:

== My Thinkpad ==
<pre>
Lenovo Thinkpad R60 9461 HRG
Intel Core2Duo (Merom) 1.83 CPU
120 GB SATA Hitachi HTS54161 Harddisk
2 GB RAM
ATI Mobility X1400
</pre>

Originally equipped with a preinstalled MS Windows Vista Business. So the Harddisk was parted into two Partitions.

1. The Rescue & Recovery Partition

2. The preinstalled Windows Vista Partition

And as the parcel with my new Thinkpad arrived I was surprized, that there was a Windows Vista DVD (only 32 Bit Version) with it.
So I tried Vista - but I was a little bit shocked by it's performance. I never thought that a new computer could take so much time to boot up completely.

I decided to do a clean install of Vista, but I want to have Windows XP and Ubuntu Feisty on the Harddisk too.

== New Installation ==

I wanted to use all Space of the Harddisk, so I decided to kill the Rescue & and Recovery Partition, but to have the chance to go back to the factory default state I ordered Recovery DVD's at the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4HWSE3#Lenovo Support Call Center for Germany].
They shipped the 3 DVD's to me - free of charge - but I think it's only free if your Thinkpad is still in the warranty. I don't know exactly.

Then I created 2 Partitions on my Harddisk, 64 GB for Vista, 20 GB for XP, so 29 GB left free for Linux.

I installed Vista and XP and all the Thinkpad Stuff for each system.

When this was finished I took a Ubuntu Feisty Fawn installation CD and boot my Notebook with it. I created a 4 GB linux-swap partition and a 25 GB root / partition.

Because I want to boot my Ubuntu with the Windows Vista Boot Loader, I decided to install Grub to /dev/sda4 which is my Linux root partition.

The installation of Ubuntu Feisty Fawn works fine, NO PROBLEMS.

NOW I want to boot Linux from the Vista Bootloader, because I don't want to wait for two Bootscreens, and I wan't to have the chance to access the Repair Console of Windows Vista.

First I have to copy the Bootsector of my Linux Partition with:

<pre>
sudo dd if=/dev/sda4 of=/tmp/bootsect.lin bs=512 count=1
</pre>

Copy the bootsect.lin file to a USB-Stick or a writable partition which you can access from Windows Vista.

Now boot Windows Vista and copy the file bootsect.lin to your Systemdrive. In an Command Window with Administrator privileges type:

<pre>
copy bootsect.lin %SYSTEMDRIVE%\

bcdedit /create /d “Ubuntu” /application BOOTSECTOR
</pre>

You will receice an ID like this {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} from bcdedit. This is a uniqe identifier for your new Boot Entry in the Vista Bootloader. Now you will have to manipulate the entry with the following commands:

<pre>
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} device boot
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} PATH \bootsect.lin
bcdedit /displayorder {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} /addlast
bcdedit /timeout 10
</pre>

Then I booted my Ubuntu an did :

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

In this file I canged the entry the following entries:

<pre>
timeout 2
hiddenmenu
</pre>

So the computer starts up with the Windows Vista bootloader and gives me the option to start Windows XP, Windows Vista, Ubuntu and I have the option to do the repair tasks with the {{key|F8}} button on Vista if something fails. If I choose to boot Ubuntu I have the option to press the {{key|ESC}} key within the two seconds delay of the hidden Grub Menu. I.E. to boot another Linux Kernel.

== The tp_smapi modules ==

I did it under Feisty and, after the Upgrade under Gutsy, like described here : [http://www.thinkwiki.org/wiki/Tp_smapi#Installation TP SMAPI] in the Section "Installation on Ubuntu/Debian"
It worked, hdaps-gl and hdaps-pivot shows me now the movements of my Thinkpad. Like you can see here:

[[Image:Hdaps-pivot.png]]

[[Image:Hdaps-gl.png]]

== The Upgrade to Gutsy Gibbon ==

NO PROBLEMS. So why should I upgrade ?

OK I really wanted to get hdapsd (Harddisk Active Protection) to work. I tried a lot of things with Feisty, but I didn't get it going. And after a lot of seach through the Internet I found out that Gutsy Gibbon, the next Release of Ubuntu should have the Package for hdapsd on board.
SO I decided to upgrade to Gutsy - with the knowledge that it is still in Beta Stadium.

Upgrading Ubuntu is really simple, you only have to do the following steps:

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

Search all feisty entries and change them to gutsy. Save and Close the file.

Do:

{{cmduser| sudo apt-get update}}
{{cmduser| sudo apt-get upgrade}}

Go and drink a cup of Tea or Coffee. When you are back you have a message, that you should reboot your System, to get all packages active. So do it.

After the reboot I installed the hdapsd package and I tried to activate the Harddisk Protection with:

{{cmduser| sudo hdapsd -d sda -s 14 -a -v}}

But I still get the message "open(protect_file): No such file or directory". ---- The Same Message that I get in Feisty before I did the Upgrade. So I banged my head on the table and noticed that I'm not tough enough to get this thing working. Maybe someone else.

I decided to get the other things to work.

UPDATE: After some days I tried to get hdapsd to work, again !

== The hdapsd - Deamon (IBM Active Disk Protection) ==

Because I never had compiled or patched a kernel under Ubuntu I had to find out how this works ! After a lot of search in the Internet, the Ubuntu Help and at Thinkwiki.org I found the (hopefully) correct way to do it.

The best information I found was this :
[http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.04_on_a_ThinkPad_T43#Active_Protection_System_.28acceleration_monitor.29|Installing Ubuntu 7.04 on a ThinkPad T43] in section "Disk protection"

Here is what I did to get it to work:

1. Make sure that you have the required packages, with:

{{cmduser|sudo apt-get install build-essential fakeroot kernel-package libncurses5-dev wget bzip2 linux-source}}

2. Get the correct kernel patch for your running kernel from here : [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch_.28apply_using_.27patch_-p1_-l_.3C_hdaps_xx.patch.27.29| HDAPS] section "8.1.1 Kernel patch (apply using 'patch -p1 -l < hdaps_xx.patch')"

After all my experiences I was not sure that there was a patch available for my Gutsy-kernel (2.6.22-7-generic), but I still had my old kernel on the disk. So I booted up the old one (2.6.20-16-generic). Check the running kernel with:

{{cmduser|uname -r}}

You should see something like: 2.6.20-7-generic

Now change to /usr/src and look that the sources for the running kernel are there with:

{{cmduser|cd /usr/src}}
{{cmduser|ls -d linux-source*}}

You should see a file with the name "linux-source-2.6.20.tar.bz2" wich includes the packed kernel sources. You have to extract it, so do:

{{cmduser|sudo su}}
{{cmdroot|tar xvfj linux-source-2.6.20.tar.bz2}}

Now you have the kernel sources in the /usr/src/linux-source-2.6.20 directory. Take a look if there is a link from /usr/src/linux to an other kernel source directory (It's maybe there if you tried to compile a kernel some time before).

{{cmdroot|ls -l linux}}

If you see that linux is linked to an other source than your running kernel remove the link and create a new one with:

{{cmdroot|rm linux}}
{{cmdroot|ln -s /usr/src/linux-source-2.6.20 linux}}

Change to the source directory and patch the kernel with this:

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|patch -p1 -l < /home/dirk/993-001.bin}}

The file "993-001.bin" is the kernel patch for the 2.6.20 and 2.6.21 kernels, I downloaded it here : [http://article.gmane.org/gmane.linux.drivers.hdaps.devel/993]

After the patchwork I did this :

{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --append-to-version=.hdapscustom kernel_image --initrd binary

This would take its time, so go and clean up your house ;-)
{{HELP|I think the last command (with --append-to-version was an error ! I need help from an specialist in kernel compiling. Please read ahead at the next section "The hdapsd - Deamon (next try)". }}
After your house is clean you can do :

{{cmdroot|cd /usr/src}}
{{cmdroot|ls -l linux*.deb}}

You should see some newly builded Debian Pakage files. Install them with:

{{cmdroot|dpkg -i linux-headers-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-doc-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-image-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-manual-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-source-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}

After the installation you should reboot your computer, when Grub comes up make sure that you select your newly builded kernel.
Check it with:

{{cmduser|uname -r}}

You should see this "2.6.20.3-ubuntu1.hdapscustom". But now you have the Problem, that you have to recompile the tp_smapi driver.

{{cmduser|cd tp_smapi-0.31}}
$ sudo make install HDAPS=1
{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdaps}}

After :

<pre>
$ dmesg | grep hdaps
</pre>

You should see something like this:

[ 893.752000] hdaps: initial mode latch is 0x05
[ 893.752000] hdaps: setting ec_rate=250, filter_order=2
[ 893.752000] hdaps: fake_data_mode set to 0
[ 893.756000] hdaps: device successfully initialized.
[ 893.756000] input: hdaps as /class/input/input10
[ 893.756000] hdaps: driver successfully loaded.

Now we are ready to try out the hdapsd Deamon which is included in the Gutsy repositories, if you are using Feisty you have to compile it yourself like described here: [http://www.thinkwiki.org/wiki/How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS].

{{cmdroot|sudo hdapsd -d sda -s 12 -a -v}}

Should show this:

[[Image:hdapsd.png]]

If you load it with :

{{cmdroot|sudo hdapsd -d sda -s 12 -a}}

You get nothing until you move your Thinkpad, then you see:

Fri Jul 13 12:30:42 2007: parking
Fri Jul 13 12:30:43 2007: un-parking
Fri Jul 13 12:30:44 2007: parking
Fri Jul 13 12:30:45 2007: un-parking

Now, after I have a working hdaps-deamon I want it to be started at boot time. Because I have upgraded to Gutsy and installed the hdapsd - Package I have a script called /etc/default/hdapsd. Here I have to change some things. HINT: Remember that you still need the /etc/init.d/hdapsd file if you try this on Feisty and maybe you have to do:

{{cmduser|sudo update-rc.d hdapsd defaults}}

to create the init links for the hdapsd init script. My links was already there. My /etc/default/hdapsd script now looks like this:

<pre>
# hdapsd default file

# start hdapsd at boottime?
START="yes"

# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
DISK="sda"

# sensitivity
SENSITIVITY=12

# other options to pass to hdapsd.
# the -d $DISK, -s $SENSITIVITY, -b and -p $PIDFILE options are always passed.
OPTIONS="-a"

</pre>

Now I could use the gnome-hdaps-applet with the following comands:

{{cmduser|mkdir gnome-hdaps-applet}}
{{cmduser|cd gnome-hdaps-applet}}
{{cmduser|wget http://www.zen24593.zen.co.uk/hdaps/gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|tar -xzf gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|sudo apt-get install libpanel-applet2-dev}}
{{cmduser|gcc $(pkg-config --cflags --libs libpanelapplet-2.0) -o gnome-hdaps-applet gnome-hdaps-applet.c}}
{{cmduser|sudo cp gnome-hdaps-applet /usr/bin/}}
{{cmduser|sudo mkdir /usr/share/pixmaps/gnome-hdaps-applet/}}
{{cmduser|sudo cp *.png /usr/share/pixmaps/gnome-hdaps-applet/}}
$ sudo cp GNOME_HDAPS_StatusApplet.server /usr/lib/bonobo/servers/

Now after a restart of the Gnome Session I could find a "HDAPS Status" applet in the "Add to Panel" dialog. I added it, and when I move the Thinkpad it shows me the "Pause" [[Image:Hdaps-paused-small.png]] Symbol, otherwise it shows "Play" [[Image:Hdaps-running-small.png]].

So far so good !!! After I got this running I tried the same steps with the normal Gutsy Kernel (2.6.22-7-generic) on the same way, and it worked ! To my surprise with the same kernel patch.

The only Problem that I now have is that I cannot use restricted modules with my new kernels. Now I have to figure out how to compile restricted modules agains selfmade kernels.

{{HELP| }}

== The hdapsd - Deamon (next try) ==

I am not satisfied with the above result, because I cannot use the accelerated xorg-fglrx driver for my ATI Graphics Card and I cannot use my wireless Intel card ipw3945 driver. And the Ubuntu restricted-manager is not working. PLEASE can someone help me to compile a Ubuntu kernel in the correct way, so that I can use the whole hardware ?

I have done a - I think really ugly hack - to get the restricted-manager working :

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|cp /boot/config-2.6.20-16-generic /lib/modules/2.6.20-16-generic/.config}}
{{cmdroot|gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -16-generic".
Then I compiled the kernel again with:

{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I moved my modules with :

{{cmdroot|mv /lib/modules/2.6.20-16-generic /lib/modules/2.6.20-16-generic.orginal}}

And installed the kernel with:

{{cmdroot|dpkg -i linux-image-2.6.20-16-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers as described above.
Finally I copied the ipw3945.ucode with

{{cmdroot|cp /lib/firmware/2.6.22-7-generic/ipw3945.ucode /lib/firmware/2.6.20-16-generic/ipw3945.ucode}}

My wireless-card is working now !
My ATI Card cannot be configured with restricted-manager!

{{HELP|Please can someone who is conform in compiling Ubuntu kernels and restricted modules help me to do it in the correct way ! And can someone recheck the things described above, because I am not sure about all things that I have written here.
}}

After some days Ubuntu updated the kernel to version 2.6.22-9-generic, so I need to do the steps described above again, with "EXTRAVERSION = -9-generic". But now my wireless card and my grapics card did not work. The restricted-manager crashes when I start it.
So I downloaded the packages ipw3945-1.2.1.tgz and ati-driver-installer-8.39.4-x86.x86_64.run.

First I extracted and installed the Intel Pro Wireless Package:

{{cmduser|tar xzvf ipw3945-1.2.1.tgz}}
{{cmduser|cd ipw3945-1.2.1}}
{{cmduser|make}}
{{cmduser|sudo make install}}

After this I could do :

{{cmduser|sudo modprobe ipw3945}}

The module was loaded, and i was able to use my wireless card now.

== The Graphics Card ==

For my Radeon Mobility X1400 I did the following steps:

{{cmduser|sudo apt get update}}
{{cmduser|sudo apt-get install module-assistant build-essential fakeroot dh-make debhelper debconf libstdc++5}}

Created a Debian Package with:

{{cmduser|sudo bash ati-driver-installer-8.39.4-x86.x86_64.run --buildpkg Ubuntu/gutsy}}

And blacklisted the old fglrx module with:

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

I added "fglrx" to the line with "DISABLED_MODULES". Then I installed the created Debian Packages with:

{{cmduser|sudo dpkg -i xorg-driver-fglrx_8.39.4-1_i386.deb fglrx-kernel-source_8.39.4-1_i386.deb fglrx-amdcccle_8.39.4-1_i386.deb}}

Then I compiled the kernel Modules:

{{cmduser|sudo module-assistant prepare}}
{{cmduser|sudo module-assistant update}}
{{cmduser|sudo module-assistant build fglrx}}
{{cmduser|sudo module-assistant install fglrx}}
{{cmduser|sudo depmod -a}}

The helpful informations for this was found at http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide.

After this steps my wifi-card and my graphics-card was working and restricted-manager was not crashing when I tried to start it.

== After The Kernel Update ==

On 9.October 2007 Ubuntu released the Kernelpackage linux-image-2.6.22-14-generic and I installed it. So here is what I have done to get it working:

{{cmduser|sudo apt-get install linux-headers-generic}}
{{cmduser|sudo ln -s /usr/src/linux-source-2.6.22 /lib/modules/2.6.22-14-generic/source}}
{{cmduser|sudo cd /usr/src/linux}}
{{cmduser|sudo make clean}}
{{cmduser|sudo cp /boot/config-2.6.22-14-generic .config}}
{{cmduser|sudo cp /boot/config-2.6.22-14-generic /lib/modules/2.6.22-14-generic/.config}}
{{cmduser|sudo gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -14-generic".
Then I compiled the kernel again with:

{{cmduser|sudo gedit .config}}

In the .config file I changed the entry " # CONFIG_SND_HDA_INTEL is not set " to " CONFIG_SND_HDA_INTEL=m ". This was needed to compile the module for my sound card.

{{cmduser|sudo make oldconfig}}
{{cmduser|sudo fakeroot make-kpkg clean}}
# fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I copied my modules with :

{{cmduser|sudo cp -R /lib/modules/2.6.22-14-generic /lib/modules/2.6.22-14-generic.orginal}}

And installed the kernel with:

{{cmduser|dpkg -i linux-image-2.6.22-14-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers with:

{{cmduser|cd /home/dirk/tp_smapi-0.32}}
$ sudo make install HDAPS=1

== The Browser Buttons ==

I wanted to use the Browser Forward & Backward Buttons within Firefox. After the upgrade my Firefox had version 2.0.0.4

I did :

{{cmduser| sudo gedit ~/.Xmodmap}}

and added the following lines :

keycode 234 = F19

keycode 233 = F20

I saved and closed the file. HINT: You have to re-login to Gnome to get the .Xmodmap file active.

Then I did the things described in [http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work#Firefox How to get special keys to work].

For the Windows Key I added "keycode 115 = F13" to my .Xmodmap File, then I klicked on "System - Einstellungen - Tastenkombinationen"
sorry I don't know how it is called in English. And changed the Entry "Das Panelmenü anzeigen" to F13

== The Brightness Buttons ==

When I wanted to control the brightness, I was not able to change it with {{key|Fn}}{{key|End}}.

So I did the Workaround menitioned here [http://thinkwiki.org/wiki/Problem_with_LCD_brightness_buttons#Workaround for Fedora Core 6 Users].
After this I was able to change the brightness with {{key|Fn}}{{key|Home}} and {{key|Fn}}{{key|End}}, but I don't have the OSD anymore.

== The Fingerprint Reader ==

Do the steps which are described in [http://www.thinkwiki.org/wiki/Installing_Ubuntu_6.10_%28Edgy_Eft%29_on_a_ThinkPad_T60#The_Fingerprint_Reader Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60] until you get to the Point where Keithvassallo says:
"Phew. Now, to make applications actually use the fingerprint reader."

I have done the following things instead of his version:

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

Change the file as following:

<pre>
#%PAM-1.0
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
auth requisite pam_nologin.so
auth required pam_env.so
@include common-auth
@include common-account
session required pam_limits.so
@include common-session
@include common-password
</pre>

and:

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

Change this file as following:

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

With this changes you have the advantage, that you are now able to login to Gnome or KDE whitout entering your password. But if you cancel the "Fingerprint Login", you are still able to login whit your username/password combination.

After I was able to login to my desktop I was unsatisfied, because my Computer still wants to get passwords i.e. when I tried to open Synaptic or when I do any sudo actions.

So I tried to figure out how this sudo thing works. I did the following change to /etc/pam.d/sudo with:

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

<pre>
#%PAM-1.0

auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/ :0
password sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam :0
auth required pam_unix.so nillock_secure
@include common-account

</pre>

With this change I was able to open System Administration tasks with my fingerprint, but the ugly thing is, that you get no information to swipe your finger over the reader when you have switched to a console session with {{Key|Ctrl}}+{{Key|Alt}}+{{Key|F1}}. The fingerprint scanner software will appear at your running X session.

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-10-10T06:49:56Z

Dirk: /* After The Kernel Update */

== My Thinkpad ==
<pre>
Lenovo Thinkpad R60 9461 HRG
Intel Core2Duo (Merom) 1.83 CPU
120 GB SATA Hitachi HTS54161 Harddisk
2 GB RAM
ATI Mobility X1400
</pre>

Originally equipped with a preinstalled MS Windows Vista Business. So the Harddisk was parted into two Partitions.

1. The Rescue & Recovery Partition

2. The preinstalled Windows Vista Partition

And as the parcel with my new Thinkpad arrived I was surprized, that there was a Windows Vista DVD (only 32 Bit Version) with it.
So I tried Vista - but I was a little bit shocked by it's performance. I never thought that a new computer could take so much time to boot up completely.

I decided to do a clean install of Vista, but I want to have Windows XP and Ubuntu Feisty on the Harddisk too.

== New Installation ==

I wanted to use all Space of the Harddisk, so I decided to kill the Rescue & and Recovery Partition, but to have the chance to go back to the factory default state I ordered Recovery DVD's at the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4HWSE3#Lenovo Support Call Center for Germany].
They shipped the 3 DVD's to me - free of charge - but I think it's only free if your Thinkpad is still in the warranty. I don't know exactly.

Then I created 2 Partitions on my Harddisk, 64 GB for Vista, 20 GB for XP, so 29 GB left free for Linux.

I installed Vista and XP and all the Thinkpad Stuff for each system.

When this was finished I took a Ubuntu Feisty Fawn installation CD and boot my Notebook with it. I created a 4 GB linux-swap partition and a 25 GB root / partition.

Because I want to boot my Ubuntu with the Windows Vista Boot Loader, I decided to install Grub to /dev/sda4 which is my Linux root partition.

The installation of Ubuntu Feisty Fawn works fine, NO PROBLEMS.

NOW I want to boot Linux from the Vista Bootloader, because I don't want to wait for two Bootscreens, and I wan't to have the chance to access the Repair Console of Windows Vista.

First I have to copy the Bootsector of my Linux Partition with:

<pre>
sudo dd if=/dev/sda4 of=/tmp/bootsect.lin bs=512 count=1
</pre>

Copy the bootsect.lin file to a USB-Stick or a writable partition which you can access from Windows Vista.

Now boot Windows Vista and copy the file bootsect.lin to your Systemdrive. In an Command Window with Administrator privileges type:

<pre>
copy bootsect.lin %SYSTEMDRIVE%\

bcdedit /create /d “Ubuntu” /application BOOTSECTOR
</pre>

You will receice an ID like this {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} from bcdedit. This is a uniqe identifier for your new Boot Entry in the Vista Bootloader. Now you will have to manipulate the entry with the following commands:

<pre>
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} device boot
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} PATH \bootsect.lin
bcdedit /displayorder {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} /addlast
bcdedit /timeout 10
</pre>

Then I booted my Ubuntu an did :

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

In this file I canged the entry the following entries:

<pre>
timeout 2
hiddenmenu
</pre>

So the computer starts up with the Windows Vista bootloader and gives me the option to start Windows XP, Windows Vista, Ubuntu and I have the option to do the repair tasks with the {{key|F8}} button on Vista if something fails. If I choose to boot Ubuntu I have the option to press the {{key|ESC}} key within the two seconds delay of the hidden Grub Menu. I.E. to boot another Linux Kernel.

== The tp_smapi modules ==

I did it under Feisty and, after the Upgrade under Gutsy, like described here : [http://www.thinkwiki.org/wiki/Tp_smapi#Installation TP SMAPI] in the Section "Installation on Ubuntu/Debian"
It worked, hdaps-gl and hdaps-pivot shows me now the movements of my Thinkpad. Like you can see here:

[[Image:Hdaps-pivot.png]]

[[Image:Hdaps-gl.png]]

== The Upgrade to Gutsy Gibbon ==

NO PROBLEMS. So why should I upgrade ?

OK I really wanted to get hdapsd (Harddisk Active Protection) to work. I tried a lot of things with Feisty, but I didn't get it going. And after a lot of seach through the Internet I found out that Gutsy Gibbon, the next Release of Ubuntu should have the Package for hdapsd on board.
SO I decided to upgrade to Gutsy - with the knowledge that it is still in Beta Stadium.

Upgrading Ubuntu is really simple, you only have to do the following steps:

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

Search all feisty entries and change them to gutsy. Save and Close the file.

Do:

{{cmduser| sudo apt-get update}}
{{cmduser| sudo apt-get upgrade}}

Go and drink a cup of Tea or Coffee. When you are back you have a message, that you should reboot your System, to get all packages active. So do it.

After the reboot I installed the hdapsd package and I tried to activate the Harddisk Protection with:

{{cmduser| sudo hdapsd -d sda -s 14 -a -v}}

But I still get the message "open(protect_file): No such file or directory". ---- The Same Message that I get in Feisty before I did the Upgrade. So I banged my head on the table and noticed that I'm not tough enough to get this thing working. Maybe someone else.

I decided to get the other things to work.

UPDATE: After some days I tried to get hdapsd to work, again !

== The hdapsd - Deamon (IBM Active Disk Protection) ==

Because I never had compiled or patched a kernel under Ubuntu I had to find out how this works ! After a lot of search in the Internet, the Ubuntu Help and at Thinkwiki.org I found the (hopefully) correct way to do it.

The best information I found was this :
[http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.04_on_a_ThinkPad_T43#Active_Protection_System_.28acceleration_monitor.29|Installing Ubuntu 7.04 on a ThinkPad T43] in section "Disk protection"

Here is what I did to get it to work:

1. Make sure that you have the required packages, with:

{{cmduser|sudo apt-get install build-essential fakeroot kernel-package libncurses5-dev wget bzip2 linux-source}}

2. Get the correct kernel patch for your running kernel from here : [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch_.28apply_using_.27patch_-p1_-l_.3C_hdaps_xx.patch.27.29| HDAPS] section "8.1.1 Kernel patch (apply using 'patch -p1 -l < hdaps_xx.patch')"

After all my experiences I was not sure that there was a patch available for my Gutsy-kernel (2.6.22-7-generic), but I still had my old kernel on the disk. So I booted up the old one (2.6.20-16-generic). Check the running kernel with:

{{cmduser|uname -r}}

You should see something like: 2.6.20-7-generic

Now change to /usr/src and look that the sources for the running kernel are there with:

{{cmduser|cd /usr/src}}
{{cmduser|ls -d linux-source*}}

You should see a file with the name "linux-source-2.6.20.tar.bz2" wich includes the packed kernel sources. You have to extract it, so do:

{{cmduser|sudo su}}
{{cmdroot|tar xvfj linux-source-2.6.20.tar.bz2}}

Now you have the kernel sources in the /usr/src/linux-source-2.6.20 directory. Take a look if there is a link from /usr/src/linux to an other kernel source directory (It's maybe there if you tried to compile a kernel some time before).

{{cmdroot|ls -l linux}}

If you see that linux is linked to an other source than your running kernel remove the link and create a new one with:

{{cmdroot|rm linux}}
{{cmdroot|ln -s /usr/src/linux-source-2.6.20 linux}}

Change to the source directory and patch the kernel with this:

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|patch -p1 -l < /home/dirk/993-001.bin}}

The file "993-001.bin" is the kernel patch for the 2.6.20 and 2.6.21 kernels, I downloaded it here : [http://article.gmane.org/gmane.linux.drivers.hdaps.devel/993]

After the patchwork I did this :

{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --append-to-version=.hdapscustom kernel_image --initrd binary

This would take its time, so go and clean up your house ;-)
{{HELP|I think the last command (with --append-to-version was an error ! I need help from an specialist in kernel compiling. Please read ahead at the next section "The hdapsd - Deamon (next try)". }}
After your house is clean you can do :

{{cmdroot|cd /usr/src}}
{{cmdroot|ls -l linux*.deb}}

You should see some newly builded Debian Pakage files. Install them with:

{{cmdroot|dpkg -i linux-headers-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-doc-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-image-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-manual-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-source-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}

After the installation you should reboot your computer, when Grub comes up make sure that you select your newly builded kernel.
Check it with:

{{cmduser|uname -r}}

You should see this "2.6.20.3-ubuntu1.hdapscustom". But now you have the Problem, that you have to recompile the tp_smapi driver.

{{cmduser|cd tp_smapi-0.31}}
$ sudo make install HDAPS=1
{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdaps}}

After :

<pre>
$ dmesg | grep hdaps
</pre>

You should see something like this:

[ 893.752000] hdaps: initial mode latch is 0x05
[ 893.752000] hdaps: setting ec_rate=250, filter_order=2
[ 893.752000] hdaps: fake_data_mode set to 0
[ 893.756000] hdaps: device successfully initialized.
[ 893.756000] input: hdaps as /class/input/input10
[ 893.756000] hdaps: driver successfully loaded.

Now we are ready to try out the hdapsd Deamon which is included in the Gutsy repositories, if you are using Feisty you have to compile it yourself like described here: [http://www.thinkwiki.org/wiki/How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS].

{{cmdroot|sudo hdapsd -d sda -s 12 -a -v}}

Should show this:

[[Image:hdapsd.png]]

If you load it with :

{{cmdroot|sudo hdapsd -d sda -s 12 -a}}

You get nothing until you move your Thinkpad, then you see:

Fri Jul 13 12:30:42 2007: parking
Fri Jul 13 12:30:43 2007: un-parking
Fri Jul 13 12:30:44 2007: parking
Fri Jul 13 12:30:45 2007: un-parking

Now, after I have a working hdaps-deamon I want it to be started at boot time. Because I have upgraded to Gutsy and installed the hdapsd - Package I have a script called /etc/default/hdapsd. Here I have to change some things. HINT: Remember that you still need the /etc/init.d/hdapsd file if you try this on Feisty and maybe you have to do:

{{cmduser|sudo update-rc.d hdapsd defaults}}

to create the init links for the hdapsd init script. My links was already there. My /etc/default/hdapsd script now looks like this:

<pre>
# hdapsd default file

# start hdapsd at boottime?
START="yes"

# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
DISK="sda"

# sensitivity
SENSITIVITY=12

# other options to pass to hdapsd.
# the -d $DISK, -s $SENSITIVITY, -b and -p $PIDFILE options are always passed.
OPTIONS="-a"

</pre>

Now I could use the gnome-hdaps-applet with the following comands:

{{cmduser|mkdir gnome-hdaps-applet}}
{{cmduser|cd gnome-hdaps-applet}}
{{cmduser|wget http://www.zen24593.zen.co.uk/hdaps/gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|tar -xzf gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|sudo apt-get install libpanel-applet2-dev}}
{{cmduser|gcc $(pkg-config --cflags --libs libpanelapplet-2.0) -o gnome-hdaps-applet gnome-hdaps-applet.c}}
{{cmduser|sudo cp gnome-hdaps-applet /usr/bin/}}
{{cmduser|sudo mkdir /usr/share/pixmaps/gnome-hdaps-applet/}}
{{cmduser|sudo cp *.png /usr/share/pixmaps/gnome-hdaps-applet/}}
$ sudo cp GNOME_HDAPS_StatusApplet.server /usr/lib/bonobo/servers/

Now after a restart of the Gnome Session I could find a "HDAPS Status" applet in the "Add to Panel" dialog. I added it, and when I move the Thinkpad it shows me the "Pause" [[Image:Hdaps-paused-small.png]] Symbol, otherwise it shows "Play" [[Image:Hdaps-running-small.png]].

So far so good !!! After I got this running I tried the same steps with the normal Gutsy Kernel (2.6.22-7-generic) on the same way, and it worked ! To my surprise with the same kernel patch.

The only Problem that I now have is that I cannot use restricted modules with my new kernels. Now I have to figure out how to compile restricted modules agains selfmade kernels.

{{HELP| }}

== The hdapsd - Deamon (next try) ==

I am not satisfied with the above result, because I cannot use the accelerated xorg-fglrx driver for my ATI Graphics Card and I cannot use my wireless Intel card ipw3945 driver. And the Ubuntu restricted-manager is not working. PLEASE can someone help me to compile a Ubuntu kernel in the correct way, so that I can use the whole hardware ?

I have done a - I think really ugly hack - to get the restricted-manager working :

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|cp /boot/config-2.6.20-16-generic /lib/modules/2.6.20-16-generic/.config}}
{{cmdroot|gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -16-generic".
Then I compiled the kernel again with:

{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I moved my modules with :

{{cmdroot|mv /lib/modules/2.6.20-16-generic /lib/modules/2.6.20-16-generic.orginal}}

And installed the kernel with:

{{cmdroot|dpkg -i linux-image-2.6.20-16-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers as described above.
Finally I copied the ipw3945.ucode with

{{cmdroot|cp /lib/firmware/2.6.22-7-generic/ipw3945.ucode /lib/firmware/2.6.20-16-generic/ipw3945.ucode}}

My wireless-card is working now !
My ATI Card cannot be configured with restricted-manager!

{{HELP|Please can someone who is conform in compiling Ubuntu kernels and restricted modules help me to do it in the correct way ! And can someone recheck the things described above, because I am not sure about all things that I have written here.
}}

After some days Ubuntu updated the kernel to version 2.6.22-9-generic, so I need to do the steps described above again, with "EXTRAVERSION = -9-generic". But now my wireless card and my grapics card did not work. The restricted-manager crashes when I start it.
So I downloaded the packages ipw3945-1.2.1.tgz and ati-driver-installer-8.39.4-x86.x86_64.run.

First I extracted and installed the Intel Pro Wireless Package:

{{cmduser|tar xzvf ipw3945-1.2.1.tgz}}
{{cmduser|cd ipw3945-1.2.1}}
{{cmduser|make}}
{{cmduser|sudo make install}}

After this I could do :

{{cmduser|sudo modprobe ipw3945}}

The module was loaded, and i was able to use my wireless card now.

For my Radeon Mobility X1400 I did the following steps:

{{cmduser|sudo apt get update}}
{{cmduser|sudo apt-get install module-assistant build-essential fakeroot dh-make debhelper debconf libstdc++5}}

Created a Debian Package with:

{{cmduser|sudo bash ati-driver-installer-8.39.4-x86.x86_64.run --buildpkg Ubuntu/gutsy}}

And blacklisted the old fglrx module with:

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

I added "fglrx" to the line with "DISABLED_MODULES". Then I installed the created Debian Packages with:

{{cmduser|sudo dpkg -i xorg-driver-fglrx_8.39.4-1_i386.deb fglrx-kernel-source_8.39.4-1_i386.deb fglrx-amdcccle_8.39.4-1_i386.deb}}

Then I compiled the kernel Modules:

{{cmduser|sudo module-assistant prepare}}
{{cmduser|sudo module-assistant update}}
{{cmduser|sudo module-assistant build fglrx}}
{{cmduser|sudo module-assistant install fglrx}}
{{cmduser|sudo depmod -a}}

The helpful informations for this was found at http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide.

After this steps my wifi-card and my graphics-card was working and restricted-manager was not crashing when I tried to start it.

== After The Kernel Update ==

On 9.October 2007 Ubuntu released the Kernelpackage linux-image-2.6.22-14-generic and I installed it. So here is what I have done to get it working:

{{cmduser|sudo apt-get install linux-headers-generic}}
{{cmduser|sudo ln -s /usr/src/linux-source-2.6.22 /lib/modules/2.6.22-14-generic/source}}
{{cmduser|sudo cd /usr/src/linux}}
{{cmduser|sudo make clean}}
{{cmduser|sudo cp /boot/config-2.6.22-14-generic .config}}
{{cmduser|sudo cp /boot/config-2.6.22-14-generic /lib/modules/2.6.22-14-generic/.config}}
{{cmduser|sudo gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -14-generic".
Then I compiled the kernel again with:

{{cmduser|sudo gedit .config}}

In the .config file I changed the entry " # CONFIG_SND_HDA_INTEL is not set " to " CONFIG_SND_HDA_INTEL=m ". This was needed to compile the module for my sound card.

{{cmduser|sudo make oldconfig}}
{{cmduser|sudo fakeroot make-kpkg clean}}
# fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I copied my modules with :

{{cmduser|sudo cp -R /lib/modules/2.6.22-14-generic /lib/modules/2.6.22-14-generic.orginal}}

And installed the kernel with:

{{cmduser|dpkg -i linux-image-2.6.22-14-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers with:

{{cmduser|cd /home/dirk/tp_smapi-0.32}}
$ sudo make install HDAPS=1

== The Browser Buttons ==

I wanted to use the Browser Forward & Backward Buttons within Firefox. After the upgrade my Firefox had version 2.0.0.4

I did :

{{cmduser| sudo gedit ~/.Xmodmap}}

and added the following lines :

keycode 234 = F19

keycode 233 = F20

I saved and closed the file. HINT: You have to re-login to Gnome to get the .Xmodmap file active.

Then I did the things described in [http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work#Firefox How to get special keys to work].

For the Windows Key I added "keycode 115 = F13" to my .Xmodmap File, then I klicked on "System - Einstellungen - Tastenkombinationen"
sorry I don't know how it is called in English. And changed the Entry "Das Panelmenü anzeigen" to F13

== The Brightness Buttons ==

When I wanted to control the brightness, I was not able to change it with {{key|Fn}}{{key|End}}.

So I did the Workaround menitioned here [http://thinkwiki.org/wiki/Problem_with_LCD_brightness_buttons#Workaround for Fedora Core 6 Users].
After this I was able to change the brightness with {{key|Fn}}{{key|Home}} and {{key|Fn}}{{key|End}}, but I don't have the OSD anymore.

== The Fingerprint Reader ==

Do the steps which are described in [http://www.thinkwiki.org/wiki/Installing_Ubuntu_6.10_%28Edgy_Eft%29_on_a_ThinkPad_T60#The_Fingerprint_Reader Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60] until you get to the Point where Keithvassallo says:
"Phew. Now, to make applications actually use the fingerprint reader."

I have done the following things instead of his version:

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

Change the file as following:

<pre>
#%PAM-1.0
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
auth requisite pam_nologin.so
auth required pam_env.so
@include common-auth
@include common-account
session required pam_limits.so
@include common-session
@include common-password
</pre>

and:

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

Change this file as following:

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

With this changes you have the advantage, that you are now able to login to Gnome or KDE whitout entering your password. But if you cancel the "Fingerprint Login", you are still able to login whit your username/password combination.

After I was able to login to my desktop I was unsatisfied, because my Computer still wants to get passwords i.e. when I tried to open Synaptic or when I do any sudo actions.

So I tried to figure out how this sudo thing works. I did the following change to /etc/pam.d/sudo with:

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

<pre>
#%PAM-1.0

auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/ :0
password sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam :0
auth required pam_unix.so nillock_secure
@include common-account

</pre>

With this change I was able to open System Administration tasks with my fingerprint, but the ugly thing is, that you get no information to swipe your finger over the reader when you have switched to a console session with {{Key|Ctrl}}+{{Key|Alt}}+{{Key|F1}}. The fingerprint scanner software will appear at your running X session.

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-10-10T06:48:38Z

Dirk: /* After The Kernel Update */

== My Thinkpad ==
<pre>
Lenovo Thinkpad R60 9461 HRG
Intel Core2Duo (Merom) 1.83 CPU
120 GB SATA Hitachi HTS54161 Harddisk
2 GB RAM
ATI Mobility X1400
</pre>

Originally equipped with a preinstalled MS Windows Vista Business. So the Harddisk was parted into two Partitions.

1. The Rescue & Recovery Partition

2. The preinstalled Windows Vista Partition

And as the parcel with my new Thinkpad arrived I was surprized, that there was a Windows Vista DVD (only 32 Bit Version) with it.
So I tried Vista - but I was a little bit shocked by it's performance. I never thought that a new computer could take so much time to boot up completely.

I decided to do a clean install of Vista, but I want to have Windows XP and Ubuntu Feisty on the Harddisk too.

== New Installation ==

I wanted to use all Space of the Harddisk, so I decided to kill the Rescue & and Recovery Partition, but to have the chance to go back to the factory default state I ordered Recovery DVD's at the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4HWSE3#Lenovo Support Call Center for Germany].
They shipped the 3 DVD's to me - free of charge - but I think it's only free if your Thinkpad is still in the warranty. I don't know exactly.

Then I created 2 Partitions on my Harddisk, 64 GB for Vista, 20 GB for XP, so 29 GB left free for Linux.

I installed Vista and XP and all the Thinkpad Stuff for each system.

When this was finished I took a Ubuntu Feisty Fawn installation CD and boot my Notebook with it. I created a 4 GB linux-swap partition and a 25 GB root / partition.

Because I want to boot my Ubuntu with the Windows Vista Boot Loader, I decided to install Grub to /dev/sda4 which is my Linux root partition.

The installation of Ubuntu Feisty Fawn works fine, NO PROBLEMS.

NOW I want to boot Linux from the Vista Bootloader, because I don't want to wait for two Bootscreens, and I wan't to have the chance to access the Repair Console of Windows Vista.

First I have to copy the Bootsector of my Linux Partition with:

<pre>
sudo dd if=/dev/sda4 of=/tmp/bootsect.lin bs=512 count=1
</pre>

Copy the bootsect.lin file to a USB-Stick or a writable partition which you can access from Windows Vista.

Now boot Windows Vista and copy the file bootsect.lin to your Systemdrive. In an Command Window with Administrator privileges type:

<pre>
copy bootsect.lin %SYSTEMDRIVE%\

bcdedit /create /d “Ubuntu” /application BOOTSECTOR
</pre>

You will receice an ID like this {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} from bcdedit. This is a uniqe identifier for your new Boot Entry in the Vista Bootloader. Now you will have to manipulate the entry with the following commands:

<pre>
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} device boot
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} PATH \bootsect.lin
bcdedit /displayorder {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} /addlast
bcdedit /timeout 10
</pre>

Then I booted my Ubuntu an did :

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

In this file I canged the entry the following entries:

<pre>
timeout 2
hiddenmenu
</pre>

So the computer starts up with the Windows Vista bootloader and gives me the option to start Windows XP, Windows Vista, Ubuntu and I have the option to do the repair tasks with the {{key|F8}} button on Vista if something fails. If I choose to boot Ubuntu I have the option to press the {{key|ESC}} key within the two seconds delay of the hidden Grub Menu. I.E. to boot another Linux Kernel.

== The tp_smapi modules ==

I did it under Feisty and, after the Upgrade under Gutsy, like described here : [http://www.thinkwiki.org/wiki/Tp_smapi#Installation TP SMAPI] in the Section "Installation on Ubuntu/Debian"
It worked, hdaps-gl and hdaps-pivot shows me now the movements of my Thinkpad. Like you can see here:

[[Image:Hdaps-pivot.png]]

[[Image:Hdaps-gl.png]]

== The Upgrade to Gutsy Gibbon ==

NO PROBLEMS. So why should I upgrade ?

OK I really wanted to get hdapsd (Harddisk Active Protection) to work. I tried a lot of things with Feisty, but I didn't get it going. And after a lot of seach through the Internet I found out that Gutsy Gibbon, the next Release of Ubuntu should have the Package for hdapsd on board.
SO I decided to upgrade to Gutsy - with the knowledge that it is still in Beta Stadium.

Upgrading Ubuntu is really simple, you only have to do the following steps:

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

Search all feisty entries and change them to gutsy. Save and Close the file.

Do:

{{cmduser| sudo apt-get update}}
{{cmduser| sudo apt-get upgrade}}

Go and drink a cup of Tea or Coffee. When you are back you have a message, that you should reboot your System, to get all packages active. So do it.

After the reboot I installed the hdapsd package and I tried to activate the Harddisk Protection with:

{{cmduser| sudo hdapsd -d sda -s 14 -a -v}}

But I still get the message "open(protect_file): No such file or directory". ---- The Same Message that I get in Feisty before I did the Upgrade. So I banged my head on the table and noticed that I'm not tough enough to get this thing working. Maybe someone else.

I decided to get the other things to work.

UPDATE: After some days I tried to get hdapsd to work, again !

== The hdapsd - Deamon (IBM Active Disk Protection) ==

Because I never had compiled or patched a kernel under Ubuntu I had to find out how this works ! After a lot of search in the Internet, the Ubuntu Help and at Thinkwiki.org I found the (hopefully) correct way to do it.

The best information I found was this :
[http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.04_on_a_ThinkPad_T43#Active_Protection_System_.28acceleration_monitor.29|Installing Ubuntu 7.04 on a ThinkPad T43] in section "Disk protection"

Here is what I did to get it to work:

1. Make sure that you have the required packages, with:

{{cmduser|sudo apt-get install build-essential fakeroot kernel-package libncurses5-dev wget bzip2 linux-source}}

2. Get the correct kernel patch for your running kernel from here : [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch_.28apply_using_.27patch_-p1_-l_.3C_hdaps_xx.patch.27.29| HDAPS] section "8.1.1 Kernel patch (apply using 'patch -p1 -l < hdaps_xx.patch')"

After all my experiences I was not sure that there was a patch available for my Gutsy-kernel (2.6.22-7-generic), but I still had my old kernel on the disk. So I booted up the old one (2.6.20-16-generic). Check the running kernel with:

{{cmduser|uname -r}}

You should see something like: 2.6.20-7-generic

Now change to /usr/src and look that the sources for the running kernel are there with:

{{cmduser|cd /usr/src}}
{{cmduser|ls -d linux-source*}}

You should see a file with the name "linux-source-2.6.20.tar.bz2" wich includes the packed kernel sources. You have to extract it, so do:

{{cmduser|sudo su}}
{{cmdroot|tar xvfj linux-source-2.6.20.tar.bz2}}

Now you have the kernel sources in the /usr/src/linux-source-2.6.20 directory. Take a look if there is a link from /usr/src/linux to an other kernel source directory (It's maybe there if you tried to compile a kernel some time before).

{{cmdroot|ls -l linux}}

If you see that linux is linked to an other source than your running kernel remove the link and create a new one with:

{{cmdroot|rm linux}}
{{cmdroot|ln -s /usr/src/linux-source-2.6.20 linux}}

Change to the source directory and patch the kernel with this:

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|patch -p1 -l < /home/dirk/993-001.bin}}

The file "993-001.bin" is the kernel patch for the 2.6.20 and 2.6.21 kernels, I downloaded it here : [http://article.gmane.org/gmane.linux.drivers.hdaps.devel/993]

After the patchwork I did this :

{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --append-to-version=.hdapscustom kernel_image --initrd binary

This would take its time, so go and clean up your house ;-)
{{HELP|I think the last command (with --append-to-version was an error ! I need help from an specialist in kernel compiling. Please read ahead at the next section "The hdapsd - Deamon (next try)". }}
After your house is clean you can do :

{{cmdroot|cd /usr/src}}
{{cmdroot|ls -l linux*.deb}}

You should see some newly builded Debian Pakage files. Install them with:

{{cmdroot|dpkg -i linux-headers-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-doc-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-image-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-manual-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-source-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}

After the installation you should reboot your computer, when Grub comes up make sure that you select your newly builded kernel.
Check it with:

{{cmduser|uname -r}}

You should see this "2.6.20.3-ubuntu1.hdapscustom". But now you have the Problem, that you have to recompile the tp_smapi driver.

{{cmduser|cd tp_smapi-0.31}}
$ sudo make install HDAPS=1
{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdaps}}

After :

<pre>
$ dmesg | grep hdaps
</pre>

You should see something like this:

[ 893.752000] hdaps: initial mode latch is 0x05
[ 893.752000] hdaps: setting ec_rate=250, filter_order=2
[ 893.752000] hdaps: fake_data_mode set to 0
[ 893.756000] hdaps: device successfully initialized.
[ 893.756000] input: hdaps as /class/input/input10
[ 893.756000] hdaps: driver successfully loaded.

Now we are ready to try out the hdapsd Deamon which is included in the Gutsy repositories, if you are using Feisty you have to compile it yourself like described here: [http://www.thinkwiki.org/wiki/How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS].

{{cmdroot|sudo hdapsd -d sda -s 12 -a -v}}

Should show this:

[[Image:hdapsd.png]]

If you load it with :

{{cmdroot|sudo hdapsd -d sda -s 12 -a}}

You get nothing until you move your Thinkpad, then you see:

Fri Jul 13 12:30:42 2007: parking
Fri Jul 13 12:30:43 2007: un-parking
Fri Jul 13 12:30:44 2007: parking
Fri Jul 13 12:30:45 2007: un-parking

Now, after I have a working hdaps-deamon I want it to be started at boot time. Because I have upgraded to Gutsy and installed the hdapsd - Package I have a script called /etc/default/hdapsd. Here I have to change some things. HINT: Remember that you still need the /etc/init.d/hdapsd file if you try this on Feisty and maybe you have to do:

{{cmduser|sudo update-rc.d hdapsd defaults}}

to create the init links for the hdapsd init script. My links was already there. My /etc/default/hdapsd script now looks like this:

<pre>
# hdapsd default file

# start hdapsd at boottime?
START="yes"

# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
DISK="sda"

# sensitivity
SENSITIVITY=12

# other options to pass to hdapsd.
# the -d $DISK, -s $SENSITIVITY, -b and -p $PIDFILE options are always passed.
OPTIONS="-a"

</pre>

Now I could use the gnome-hdaps-applet with the following comands:

{{cmduser|mkdir gnome-hdaps-applet}}
{{cmduser|cd gnome-hdaps-applet}}
{{cmduser|wget http://www.zen24593.zen.co.uk/hdaps/gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|tar -xzf gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|sudo apt-get install libpanel-applet2-dev}}
{{cmduser|gcc $(pkg-config --cflags --libs libpanelapplet-2.0) -o gnome-hdaps-applet gnome-hdaps-applet.c}}
{{cmduser|sudo cp gnome-hdaps-applet /usr/bin/}}
{{cmduser|sudo mkdir /usr/share/pixmaps/gnome-hdaps-applet/}}
{{cmduser|sudo cp *.png /usr/share/pixmaps/gnome-hdaps-applet/}}
$ sudo cp GNOME_HDAPS_StatusApplet.server /usr/lib/bonobo/servers/

Now after a restart of the Gnome Session I could find a "HDAPS Status" applet in the "Add to Panel" dialog. I added it, and when I move the Thinkpad it shows me the "Pause" [[Image:Hdaps-paused-small.png]] Symbol, otherwise it shows "Play" [[Image:Hdaps-running-small.png]].

So far so good !!! After I got this running I tried the same steps with the normal Gutsy Kernel (2.6.22-7-generic) on the same way, and it worked ! To my surprise with the same kernel patch.

The only Problem that I now have is that I cannot use restricted modules with my new kernels. Now I have to figure out how to compile restricted modules agains selfmade kernels.

{{HELP| }}

== The hdapsd - Deamon (next try) ==

I am not satisfied with the above result, because I cannot use the accelerated xorg-fglrx driver for my ATI Graphics Card and I cannot use my wireless Intel card ipw3945 driver. And the Ubuntu restricted-manager is not working. PLEASE can someone help me to compile a Ubuntu kernel in the correct way, so that I can use the whole hardware ?

I have done a - I think really ugly hack - to get the restricted-manager working :

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|cp /boot/config-2.6.20-16-generic /lib/modules/2.6.20-16-generic/.config}}
{{cmdroot|gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -16-generic".
Then I compiled the kernel again with:

{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I moved my modules with :

{{cmdroot|mv /lib/modules/2.6.20-16-generic /lib/modules/2.6.20-16-generic.orginal}}

And installed the kernel with:

{{cmdroot|dpkg -i linux-image-2.6.20-16-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers as described above.
Finally I copied the ipw3945.ucode with

{{cmdroot|cp /lib/firmware/2.6.22-7-generic/ipw3945.ucode /lib/firmware/2.6.20-16-generic/ipw3945.ucode}}

My wireless-card is working now !
My ATI Card cannot be configured with restricted-manager!

{{HELP|Please can someone who is conform in compiling Ubuntu kernels and restricted modules help me to do it in the correct way ! And can someone recheck the things described above, because I am not sure about all things that I have written here.
}}

After some days Ubuntu updated the kernel to version 2.6.22-9-generic, so I need to do the steps described above again, with "EXTRAVERSION = -9-generic". But now my wireless card and my grapics card did not work. The restricted-manager crashes when I start it.
So I downloaded the packages ipw3945-1.2.1.tgz and ati-driver-installer-8.39.4-x86.x86_64.run.

First I extracted and installed the Intel Pro Wireless Package:

{{cmduser|tar xzvf ipw3945-1.2.1.tgz}}
{{cmduser|cd ipw3945-1.2.1}}
{{cmduser|make}}
{{cmduser|sudo make install}}

After this I could do :

{{cmduser|sudo modprobe ipw3945}}

The module was loaded, and i was able to use my wireless card now.

For my Radeon Mobility X1400 I did the following steps:

{{cmduser|sudo apt get update}}
{{cmduser|sudo apt-get install module-assistant build-essential fakeroot dh-make debhelper debconf libstdc++5}}

Created a Debian Package with:

{{cmduser|sudo bash ati-driver-installer-8.39.4-x86.x86_64.run --buildpkg Ubuntu/gutsy}}

And blacklisted the old fglrx module with:

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

I added "fglrx" to the line with "DISABLED_MODULES". Then I installed the created Debian Packages with:

{{cmduser|sudo dpkg -i xorg-driver-fglrx_8.39.4-1_i386.deb fglrx-kernel-source_8.39.4-1_i386.deb fglrx-amdcccle_8.39.4-1_i386.deb}}

Then I compiled the kernel Modules:

{{cmduser|sudo module-assistant prepare}}
{{cmduser|sudo module-assistant update}}
{{cmduser|sudo module-assistant build fglrx}}
{{cmduser|sudo module-assistant install fglrx}}
{{cmduser|sudo depmod -a}}

The helpful informations for this was found at http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide.

After this steps my wifi-card and my graphics-card was working and restricted-manager was not crashing when I tried to start it.

== After The Kernel Update ==

On 9.October 2007 Ubuntu released the Kernelpackage linux-image-2.6.22-14-generic and I installed it. So here is what I have done to get it working:

{{cmduser|sudo apt-get install linux-headers-generic}}
{{cmduser|sudo ln -s /usr/src/linux-source-2.6.22 /lib/modules/2.6.22-14-generic/source}}
{{cmduser|sudo cd /usr/src/linux}}
{{cmduser|sudo make clean}}
{{cmduser|sudo cp /boot/config-2.6.22-14-generic .config}}
{{cmduser|sudo cp /boot/config-2.6.22-14-generic /lib/modules/2.6.22-14-generic/.config}}
{{cmduser|sudo gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -14-generic".
Then I compiled the kernel again with:

{{cmduser|gedit .config}}

In the .config file I changed the entry " # CONFIG_SND_HDA_INTEL is not set " to " CONFIG_SND_HDA_INTEL=m ". This was needed to compile the module for my sound card.

{{cmduser|sudo make oldconfig}}
{{cmduser|sudo fakeroot make-kpkg clean}}
# fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I copied my modules with :

{{cmduser|sudo cp -R /lib/modules/2.6.22-14-generic /lib/modules/2.6.22-14-generic.orginal}}

And installed the kernel with:

{{cmduser|dpkg -i linux-image-2.6.22-14-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers with:

{{cmduser|cd /home/dirk/tp_smapi-0.32}}
{{cmduser|sudo make install HDAPS=1}}

== The Browser Buttons ==

I wanted to use the Browser Forward & Backward Buttons within Firefox. After the upgrade my Firefox had version 2.0.0.4

I did :

{{cmduser| sudo gedit ~/.Xmodmap}}

and added the following lines :

keycode 234 = F19

keycode 233 = F20

I saved and closed the file. HINT: You have to re-login to Gnome to get the .Xmodmap file active.

Then I did the things described in [http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work#Firefox How to get special keys to work].

For the Windows Key I added "keycode 115 = F13" to my .Xmodmap File, then I klicked on "System - Einstellungen - Tastenkombinationen"
sorry I don't know how it is called in English. And changed the Entry "Das Panelmenü anzeigen" to F13

== The Brightness Buttons ==

When I wanted to control the brightness, I was not able to change it with {{key|Fn}}{{key|End}}.

So I did the Workaround menitioned here [http://thinkwiki.org/wiki/Problem_with_LCD_brightness_buttons#Workaround for Fedora Core 6 Users].
After this I was able to change the brightness with {{key|Fn}}{{key|Home}} and {{key|Fn}}{{key|End}}, but I don't have the OSD anymore.

== The Fingerprint Reader ==

Do the steps which are described in [http://www.thinkwiki.org/wiki/Installing_Ubuntu_6.10_%28Edgy_Eft%29_on_a_ThinkPad_T60#The_Fingerprint_Reader Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60] until you get to the Point where Keithvassallo says:
"Phew. Now, to make applications actually use the fingerprint reader."

I have done the following things instead of his version:

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

Change the file as following:

<pre>
#%PAM-1.0
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
auth requisite pam_nologin.so
auth required pam_env.so
@include common-auth
@include common-account
session required pam_limits.so
@include common-session
@include common-password
</pre>

and:

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

Change this file as following:

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

With this changes you have the advantage, that you are now able to login to Gnome or KDE whitout entering your password. But if you cancel the "Fingerprint Login", you are still able to login whit your username/password combination.

After I was able to login to my desktop I was unsatisfied, because my Computer still wants to get passwords i.e. when I tried to open Synaptic or when I do any sudo actions.

So I tried to figure out how this sudo thing works. I did the following change to /etc/pam.d/sudo with:

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

<pre>
#%PAM-1.0

auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/ :0
password sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam :0
auth required pam_unix.so nillock_secure
@include common-account

</pre>

With this change I was able to open System Administration tasks with my fingerprint, but the ugly thing is, that you get no information to swipe your finger over the reader when you have switched to a console session with {{Key|Ctrl}}+{{Key|Alt}}+{{Key|F1}}. The fingerprint scanner software will appear at your running X session.

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-10-10T06:29:52Z

Dirk:

== My Thinkpad ==
<pre>
Lenovo Thinkpad R60 9461 HRG
Intel Core2Duo (Merom) 1.83 CPU
120 GB SATA Hitachi HTS54161 Harddisk
2 GB RAM
ATI Mobility X1400
</pre>

Originally equipped with a preinstalled MS Windows Vista Business. So the Harddisk was parted into two Partitions.

1. The Rescue & Recovery Partition

2. The preinstalled Windows Vista Partition

And as the parcel with my new Thinkpad arrived I was surprized, that there was a Windows Vista DVD (only 32 Bit Version) with it.
So I tried Vista - but I was a little bit shocked by it's performance. I never thought that a new computer could take so much time to boot up completely.

I decided to do a clean install of Vista, but I want to have Windows XP and Ubuntu Feisty on the Harddisk too.

== New Installation ==

I wanted to use all Space of the Harddisk, so I decided to kill the Rescue & and Recovery Partition, but to have the chance to go back to the factory default state I ordered Recovery DVD's at the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4HWSE3#Lenovo Support Call Center for Germany].
They shipped the 3 DVD's to me - free of charge - but I think it's only free if your Thinkpad is still in the warranty. I don't know exactly.

Then I created 2 Partitions on my Harddisk, 64 GB for Vista, 20 GB for XP, so 29 GB left free for Linux.

I installed Vista and XP and all the Thinkpad Stuff for each system.

When this was finished I took a Ubuntu Feisty Fawn installation CD and boot my Notebook with it. I created a 4 GB linux-swap partition and a 25 GB root / partition.

Because I want to boot my Ubuntu with the Windows Vista Boot Loader, I decided to install Grub to /dev/sda4 which is my Linux root partition.

The installation of Ubuntu Feisty Fawn works fine, NO PROBLEMS.

NOW I want to boot Linux from the Vista Bootloader, because I don't want to wait for two Bootscreens, and I wan't to have the chance to access the Repair Console of Windows Vista.

First I have to copy the Bootsector of my Linux Partition with:

<pre>
sudo dd if=/dev/sda4 of=/tmp/bootsect.lin bs=512 count=1
</pre>

Copy the bootsect.lin file to a USB-Stick or a writable partition which you can access from Windows Vista.

Now boot Windows Vista and copy the file bootsect.lin to your Systemdrive. In an Command Window with Administrator privileges type:

<pre>
copy bootsect.lin %SYSTEMDRIVE%\

bcdedit /create /d “Ubuntu” /application BOOTSECTOR
</pre>

You will receice an ID like this {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} from bcdedit. This is a uniqe identifier for your new Boot Entry in the Vista Bootloader. Now you will have to manipulate the entry with the following commands:

<pre>
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} device boot
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} PATH \bootsect.lin
bcdedit /displayorder {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} /addlast
bcdedit /timeout 10
</pre>

Then I booted my Ubuntu an did :

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

In this file I canged the entry the following entries:

<pre>
timeout 2
hiddenmenu
</pre>

So the computer starts up with the Windows Vista bootloader and gives me the option to start Windows XP, Windows Vista, Ubuntu and I have the option to do the repair tasks with the {{key|F8}} button on Vista if something fails. If I choose to boot Ubuntu I have the option to press the {{key|ESC}} key within the two seconds delay of the hidden Grub Menu. I.E. to boot another Linux Kernel.

== The tp_smapi modules ==

I did it under Feisty and, after the Upgrade under Gutsy, like described here : [http://www.thinkwiki.org/wiki/Tp_smapi#Installation TP SMAPI] in the Section "Installation on Ubuntu/Debian"
It worked, hdaps-gl and hdaps-pivot shows me now the movements of my Thinkpad. Like you can see here:

[[Image:Hdaps-pivot.png]]

[[Image:Hdaps-gl.png]]

== The Upgrade to Gutsy Gibbon ==

NO PROBLEMS. So why should I upgrade ?

OK I really wanted to get hdapsd (Harddisk Active Protection) to work. I tried a lot of things with Feisty, but I didn't get it going. And after a lot of seach through the Internet I found out that Gutsy Gibbon, the next Release of Ubuntu should have the Package for hdapsd on board.
SO I decided to upgrade to Gutsy - with the knowledge that it is still in Beta Stadium.

Upgrading Ubuntu is really simple, you only have to do the following steps:

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

Search all feisty entries and change them to gutsy. Save and Close the file.

Do:

{{cmduser| sudo apt-get update}}
{{cmduser| sudo apt-get upgrade}}

Go and drink a cup of Tea or Coffee. When you are back you have a message, that you should reboot your System, to get all packages active. So do it.

After the reboot I installed the hdapsd package and I tried to activate the Harddisk Protection with:

{{cmduser| sudo hdapsd -d sda -s 14 -a -v}}

But I still get the message "open(protect_file): No such file or directory". ---- The Same Message that I get in Feisty before I did the Upgrade. So I banged my head on the table and noticed that I'm not tough enough to get this thing working. Maybe someone else.

I decided to get the other things to work.

UPDATE: After some days I tried to get hdapsd to work, again !

== The hdapsd - Deamon (IBM Active Disk Protection) ==

Because I never had compiled or patched a kernel under Ubuntu I had to find out how this works ! After a lot of search in the Internet, the Ubuntu Help and at Thinkwiki.org I found the (hopefully) correct way to do it.

The best information I found was this :
[http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.04_on_a_ThinkPad_T43#Active_Protection_System_.28acceleration_monitor.29|Installing Ubuntu 7.04 on a ThinkPad T43] in section "Disk protection"

Here is what I did to get it to work:

1. Make sure that you have the required packages, with:

{{cmduser|sudo apt-get install build-essential fakeroot kernel-package libncurses5-dev wget bzip2 linux-source}}

2. Get the correct kernel patch for your running kernel from here : [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch_.28apply_using_.27patch_-p1_-l_.3C_hdaps_xx.patch.27.29| HDAPS] section "8.1.1 Kernel patch (apply using 'patch -p1 -l < hdaps_xx.patch')"

After all my experiences I was not sure that there was a patch available for my Gutsy-kernel (2.6.22-7-generic), but I still had my old kernel on the disk. So I booted up the old one (2.6.20-16-generic). Check the running kernel with:

{{cmduser|uname -r}}

You should see something like: 2.6.20-7-generic

Now change to /usr/src and look that the sources for the running kernel are there with:

{{cmduser|cd /usr/src}}
{{cmduser|ls -d linux-source*}}

You should see a file with the name "linux-source-2.6.20.tar.bz2" wich includes the packed kernel sources. You have to extract it, so do:

{{cmduser|sudo su}}
{{cmdroot|tar xvfj linux-source-2.6.20.tar.bz2}}

Now you have the kernel sources in the /usr/src/linux-source-2.6.20 directory. Take a look if there is a link from /usr/src/linux to an other kernel source directory (It's maybe there if you tried to compile a kernel some time before).

{{cmdroot|ls -l linux}}

If you see that linux is linked to an other source than your running kernel remove the link and create a new one with:

{{cmdroot|rm linux}}
{{cmdroot|ln -s /usr/src/linux-source-2.6.20 linux}}

Change to the source directory and patch the kernel with this:

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|patch -p1 -l < /home/dirk/993-001.bin}}

The file "993-001.bin" is the kernel patch for the 2.6.20 and 2.6.21 kernels, I downloaded it here : [http://article.gmane.org/gmane.linux.drivers.hdaps.devel/993]

After the patchwork I did this :

{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --append-to-version=.hdapscustom kernel_image --initrd binary

This would take its time, so go and clean up your house ;-)
{{HELP|I think the last command (with --append-to-version was an error ! I need help from an specialist in kernel compiling. Please read ahead at the next section "The hdapsd - Deamon (next try)". }}
After your house is clean you can do :

{{cmdroot|cd /usr/src}}
{{cmdroot|ls -l linux*.deb}}

You should see some newly builded Debian Pakage files. Install them with:

{{cmdroot|dpkg -i linux-headers-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-doc-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-image-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-manual-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-source-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}

After the installation you should reboot your computer, when Grub comes up make sure that you select your newly builded kernel.
Check it with:

{{cmduser|uname -r}}

You should see this "2.6.20.3-ubuntu1.hdapscustom". But now you have the Problem, that you have to recompile the tp_smapi driver.

{{cmduser|cd tp_smapi-0.31}}
$ sudo make install HDAPS=1
{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdaps}}

After :

<pre>
$ dmesg | grep hdaps
</pre>

You should see something like this:

[ 893.752000] hdaps: initial mode latch is 0x05
[ 893.752000] hdaps: setting ec_rate=250, filter_order=2
[ 893.752000] hdaps: fake_data_mode set to 0
[ 893.756000] hdaps: device successfully initialized.
[ 893.756000] input: hdaps as /class/input/input10
[ 893.756000] hdaps: driver successfully loaded.

Now we are ready to try out the hdapsd Deamon which is included in the Gutsy repositories, if you are using Feisty you have to compile it yourself like described here: [http://www.thinkwiki.org/wiki/How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS].

{{cmdroot|sudo hdapsd -d sda -s 12 -a -v}}

Should show this:

[[Image:hdapsd.png]]

If you load it with :

{{cmdroot|sudo hdapsd -d sda -s 12 -a}}

You get nothing until you move your Thinkpad, then you see:

Fri Jul 13 12:30:42 2007: parking
Fri Jul 13 12:30:43 2007: un-parking
Fri Jul 13 12:30:44 2007: parking
Fri Jul 13 12:30:45 2007: un-parking

Now, after I have a working hdaps-deamon I want it to be started at boot time. Because I have upgraded to Gutsy and installed the hdapsd - Package I have a script called /etc/default/hdapsd. Here I have to change some things. HINT: Remember that you still need the /etc/init.d/hdapsd file if you try this on Feisty and maybe you have to do:

{{cmduser|sudo update-rc.d hdapsd defaults}}

to create the init links for the hdapsd init script. My links was already there. My /etc/default/hdapsd script now looks like this:

<pre>
# hdapsd default file

# start hdapsd at boottime?
START="yes"

# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
DISK="sda"

# sensitivity
SENSITIVITY=12

# other options to pass to hdapsd.
# the -d $DISK, -s $SENSITIVITY, -b and -p $PIDFILE options are always passed.
OPTIONS="-a"

</pre>

Now I could use the gnome-hdaps-applet with the following comands:

{{cmduser|mkdir gnome-hdaps-applet}}
{{cmduser|cd gnome-hdaps-applet}}
{{cmduser|wget http://www.zen24593.zen.co.uk/hdaps/gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|tar -xzf gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|sudo apt-get install libpanel-applet2-dev}}
{{cmduser|gcc $(pkg-config --cflags --libs libpanelapplet-2.0) -o gnome-hdaps-applet gnome-hdaps-applet.c}}
{{cmduser|sudo cp gnome-hdaps-applet /usr/bin/}}
{{cmduser|sudo mkdir /usr/share/pixmaps/gnome-hdaps-applet/}}
{{cmduser|sudo cp *.png /usr/share/pixmaps/gnome-hdaps-applet/}}
$ sudo cp GNOME_HDAPS_StatusApplet.server /usr/lib/bonobo/servers/

Now after a restart of the Gnome Session I could find a "HDAPS Status" applet in the "Add to Panel" dialog. I added it, and when I move the Thinkpad it shows me the "Pause" [[Image:Hdaps-paused-small.png]] Symbol, otherwise it shows "Play" [[Image:Hdaps-running-small.png]].

So far so good !!! After I got this running I tried the same steps with the normal Gutsy Kernel (2.6.22-7-generic) on the same way, and it worked ! To my surprise with the same kernel patch.

The only Problem that I now have is that I cannot use restricted modules with my new kernels. Now I have to figure out how to compile restricted modules agains selfmade kernels.

{{HELP| }}

== The hdapsd - Deamon (next try) ==

I am not satisfied with the above result, because I cannot use the accelerated xorg-fglrx driver for my ATI Graphics Card and I cannot use my wireless Intel card ipw3945 driver. And the Ubuntu restricted-manager is not working. PLEASE can someone help me to compile a Ubuntu kernel in the correct way, so that I can use the whole hardware ?

I have done a - I think really ugly hack - to get the restricted-manager working :

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|cp /boot/config-2.6.20-16-generic /lib/modules/2.6.20-16-generic/.config}}
{{cmdroot|gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -16-generic".
Then I compiled the kernel again with:

{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I moved my modules with :

{{cmdroot|mv /lib/modules/2.6.20-16-generic /lib/modules/2.6.20-16-generic.orginal}}

And installed the kernel with:

{{cmdroot|dpkg -i linux-image-2.6.20-16-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers as described above.
Finally I copied the ipw3945.ucode with

{{cmdroot|cp /lib/firmware/2.6.22-7-generic/ipw3945.ucode /lib/firmware/2.6.20-16-generic/ipw3945.ucode}}

My wireless-card is working now !
My ATI Card cannot be configured with restricted-manager!

{{HELP|Please can someone who is conform in compiling Ubuntu kernels and restricted modules help me to do it in the correct way ! And can someone recheck the things described above, because I am not sure about all things that I have written here.
}}

After some days Ubuntu updated the kernel to version 2.6.22-9-generic, so I need to do the steps described above again, with "EXTRAVERSION = -9-generic". But now my wireless card and my grapics card did not work. The restricted-manager crashes when I start it.
So I downloaded the packages ipw3945-1.2.1.tgz and ati-driver-installer-8.39.4-x86.x86_64.run.

First I extracted and installed the Intel Pro Wireless Package:

{{cmduser|tar xzvf ipw3945-1.2.1.tgz}}
{{cmduser|cd ipw3945-1.2.1}}
{{cmduser|make}}
{{cmduser|sudo make install}}

After this I could do :

{{cmduser|sudo modprobe ipw3945}}

The module was loaded, and i was able to use my wireless card now.

For my Radeon Mobility X1400 I did the following steps:

{{cmduser|sudo apt get update}}
{{cmduser|sudo apt-get install module-assistant build-essential fakeroot dh-make debhelper debconf libstdc++5}}

Created a Debian Package with:

{{cmduser|sudo bash ati-driver-installer-8.39.4-x86.x86_64.run --buildpkg Ubuntu/gutsy}}

And blacklisted the old fglrx module with:

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

I added "fglrx" to the line with "DISABLED_MODULES". Then I installed the created Debian Packages with:

{{cmduser|sudo dpkg -i xorg-driver-fglrx_8.39.4-1_i386.deb fglrx-kernel-source_8.39.4-1_i386.deb fglrx-amdcccle_8.39.4-1_i386.deb}}

Then I compiled the kernel Modules:

{{cmduser|sudo module-assistant prepare}}
{{cmduser|sudo module-assistant update}}
{{cmduser|sudo module-assistant build fglrx}}
{{cmduser|sudo module-assistant install fglrx}}
{{cmduser|sudo depmod -a}}

The helpful informations for this was found at http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide.

After this steps my wifi-card and my graphics-card was working and restricted-manager was not crashing when I tried to start it.

== After The Kernel Update ==

== The Browser Buttons ==

I wanted to use the Browser Forward & Backward Buttons within Firefox. After the upgrade my Firefox had version 2.0.0.4

I did :

{{cmduser| sudo gedit ~/.Xmodmap}}

and added the following lines :

keycode 234 = F19

keycode 233 = F20

I saved and closed the file. HINT: You have to re-login to Gnome to get the .Xmodmap file active.

Then I did the things described in [http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work#Firefox How to get special keys to work].

For the Windows Key I added "keycode 115 = F13" to my .Xmodmap File, then I klicked on "System - Einstellungen - Tastenkombinationen"
sorry I don't know how it is called in English. And changed the Entry "Das Panelmenü anzeigen" to F13

== The Brightness Buttons ==

When I wanted to control the brightness, I was not able to change it with {{key|Fn}}{{key|End}}.

So I did the Workaround menitioned here [http://thinkwiki.org/wiki/Problem_with_LCD_brightness_buttons#Workaround for Fedora Core 6 Users].
After this I was able to change the brightness with {{key|Fn}}{{key|Home}} and {{key|Fn}}{{key|End}}, but I don't have the OSD anymore.

== The Fingerprint Reader ==

Do the steps which are described in [http://www.thinkwiki.org/wiki/Installing_Ubuntu_6.10_%28Edgy_Eft%29_on_a_ThinkPad_T60#The_Fingerprint_Reader Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60] until you get to the Point where Keithvassallo says:
"Phew. Now, to make applications actually use the fingerprint reader."

I have done the following things instead of his version:

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

Change the file as following:

<pre>
#%PAM-1.0
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
auth requisite pam_nologin.so
auth required pam_env.so
@include common-auth
@include common-account
session required pam_limits.so
@include common-session
@include common-password
</pre>

and:

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

Change this file as following:

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

With this changes you have the advantage, that you are now able to login to Gnome or KDE whitout entering your password. But if you cancel the "Fingerprint Login", you are still able to login whit your username/password combination.

After I was able to login to my desktop I was unsatisfied, because my Computer still wants to get passwords i.e. when I tried to open Synaptic or when I do any sudo actions.

So I tried to figure out how this sudo thing works. I did the following change to /etc/pam.d/sudo with:

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

<pre>
#%PAM-1.0

auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/ :0
password sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam :0
auth required pam_unix.so nillock_secure
@include common-account

</pre>

With this change I was able to open System Administration tasks with my fingerprint, but the ugly thing is, that you get no information to swipe your finger over the reader when you have switched to a console session with {{Key|Ctrl}}+{{Key|Alt}}+{{Key|F1}}. The fingerprint scanner software will appear at your running X session.

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-10-10T06:03:09Z

Dirk: /* The hdapsd - Deamon (next try) */

== My Thinkpad ==
<pre>
Lenovo Thinkpad R60 9461 HRG
Intel Core2Duo (Merom) 1.83 CPU
120 GB SATA Hitachi HTS54161 Harddisk
2 GB RAM
ATI Mobility X1400
</pre>

Originally equipped with a preinstalled MS Windows Vista Business. So the Harddisk was parted into two Partitions.

1. The Rescue & Recovery Partition

2. The preinstalled Windows Vista Partition

And as the parcel with my new Thinkpad arrived I was surprized, that there was a Windows Vista DVD (only 32 Bit Version) with it.
So I tried Vista - but I was a little bit shocked by it's performance. I never thought that a new computer could take so much time to boot up completely.

I decided to do a clean install of Vista, but I want to have Windows XP and Ubuntu Feisty on the Harddisk too.

== New Installation ==

I wanted to use all Space of the Harddisk, so I decided to kill the Rescue & and Recovery Partition, but to have the chance to go back to the factory default state I ordered Recovery DVD's at the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4HWSE3#Lenovo Support Call Center for Germany].
They shipped the 3 DVD's to me - free of charge - but I think it's only free if your Thinkpad is still in the warranty. I don't know exactly.

Then I created 2 Partitions on my Harddisk, 64 GB for Vista, 20 GB for XP, so 29 GB left free for Linux.

I installed Vista and XP and all the Thinkpad Stuff for each system.

When this was finished I took a Ubuntu Feisty Fawn installation CD and boot my Notebook with it. I created a 4 GB linux-swap partition and a 25 GB root / partition.

Because I want to boot my Ubuntu with the Windows Vista Boot Loader, I decided to install Grub to /dev/sda4 which is my Linux root partition.

The installation of Ubuntu Feisty Fawn works fine, NO PROBLEMS.

NOW I want to boot Linux from the Vista Bootloader, because I don't want to wait for two Bootscreens, and I wan't to have the chance to access the Repair Console of Windows Vista.

First I have to copy the Bootsector of my Linux Partition with:

<pre>
sudo dd if=/dev/sda4 of=/tmp/bootsect.lin bs=512 count=1
</pre>

Copy the bootsect.lin file to a USB-Stick or a writable partition which you can access from Windows Vista.

Now boot Windows Vista and copy the file bootsect.lin to your Systemdrive. In an Command Window with Administrator privileges type:

<pre>
copy bootsect.lin %SYSTEMDRIVE%\

bcdedit /create /d “Ubuntu” /application BOOTSECTOR
</pre>

You will receice an ID like this {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} from bcdedit. This is a uniqe identifier for your new Boot Entry in the Vista Bootloader. Now you will have to manipulate the entry with the following commands:

<pre>
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} device boot
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} PATH \bootsect.lin
bcdedit /displayorder {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} /addlast
bcdedit /timeout 10
</pre>

Then I booted my Ubuntu an did :

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

In this file I canged the entry the following entries:

<pre>
timeout 2
hiddenmenu
</pre>

So the computer starts up with the Windows Vista bootloader and gives me the option to start Windows XP, Windows Vista, Ubuntu and I have the option to do the repair tasks with the {{key|F8}} button on Vista if something fails. If I choose to boot Ubuntu I have the option to press the {{key|ESC}} key within the two seconds delay of the hidden Grub Menu. I.E. to boot another Linux Kernel.

== The tp_smapi modules ==

I did it under Feisty and, after the Upgrade under Gutsy, like described here : [http://www.thinkwiki.org/wiki/Tp_smapi#Installation TP SMAPI] in the Section "Installation on Ubuntu/Debian"
It worked, hdaps-gl and hdaps-pivot shows me now the movements of my Thinkpad. Like you can see here:

[[Image:Hdaps-pivot.png]]

[[Image:Hdaps-gl.png]]

== The Upgrade to Gutsy Gibbon ==

NO PROBLEMS. So why should I upgrade ?

OK I really wanted to get hdapsd (Harddisk Active Protection) to work. I tried a lot of things with Feisty, but I didn't get it going. And after a lot of seach through the Internet I found out that Gutsy Gibbon, the next Release of Ubuntu should have the Package for hdapsd on board.
SO I decided to upgrade to Gutsy - with the knowledge that it is still in Beta Stadium.

Upgrading Ubuntu is really simple, you only have to do the following steps:

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

Search all feisty entries and change them to gutsy. Save and Close the file.

Do:

{{cmduser| sudo apt-get update}}
{{cmduser| sudo apt-get upgrade}}

Go and drink a cup of Tea or Coffee. When you are back you have a message, that you should reboot your System, to get all packages active. So do it.

After the reboot I installed the hdapsd package and I tried to activate the Harddisk Protection with:

{{cmduser| sudo hdapsd -d sda -s 14 -a -v}}

But I still get the message "open(protect_file): No such file or directory". ---- The Same Message that I get in Feisty before I did the Upgrade. So I banged my head on the table and noticed that I'm not tough enough to get this thing working. Maybe someone else.

I decided to get the other things to work.

UPDATE: After some days I tried to get hdapsd to work, again !

== The hdapsd - Deamon (IBM Active Disk Protection) ==

Because I never had compiled or patched a kernel under Ubuntu I had to find out how this works ! After a lot of search in the Internet, the Ubuntu Help and at Thinkwiki.org I found the (hopefully) correct way to do it.

The best information I found was this :
[http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.04_on_a_ThinkPad_T43#Active_Protection_System_.28acceleration_monitor.29|Installing Ubuntu 7.04 on a ThinkPad T43] in section "Disk protection"

Here is what I did to get it to work:

1. Make sure that you have the required packages, with:

{{cmduser|sudo apt-get install build-essential fakeroot kernel-package libncurses5-dev wget bzip2 linux-source}}

2. Get the correct kernel patch for your running kernel from here : [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch_.28apply_using_.27patch_-p1_-l_.3C_hdaps_xx.patch.27.29| HDAPS] section "8.1.1 Kernel patch (apply using 'patch -p1 -l < hdaps_xx.patch')"

After all my experiences I was not sure that there was a patch available for my Gutsy-kernel (2.6.22-7-generic), but I still had my old kernel on the disk. So I booted up the old one (2.6.20-16-generic). Check the running kernel with:

{{cmduser|uname -r}}

You should see something like: 2.6.20-7-generic

Now change to /usr/src and look that the sources for the running kernel are there with:

{{cmduser|cd /usr/src}}
{{cmduser|ls -d linux-source*}}

You should see a file with the name "linux-source-2.6.20.tar.bz2" wich includes the packed kernel sources. You have to extract it, so do:

{{cmduser|sudo su}}
{{cmdroot|tar xvfj linux-source-2.6.20.tar.bz2}}

Now you have the kernel sources in the /usr/src/linux-source-2.6.20 directory. Take a look if there is a link from /usr/src/linux to an other kernel source directory (It's maybe there if you tried to compile a kernel some time before).

{{cmdroot|ls -l linux}}

If you see that linux is linked to an other source than your running kernel remove the link and create a new one with:

{{cmdroot|rm linux}}
{{cmdroot|ln -s /usr/src/linux-source-2.6.20 linux}}

Change to the source directory and patch the kernel with this:

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|patch -p1 -l < /home/dirk/993-001.bin}}

The file "993-001.bin" is the kernel patch for the 2.6.20 and 2.6.21 kernels, I downloaded it here : [http://article.gmane.org/gmane.linux.drivers.hdaps.devel/993]

After the patchwork I did this :

{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --append-to-version=.hdapscustom kernel_image --initrd binary

This would take its time, so go and clean up your house ;-)
{{HELP|I think the last command (with --append-to-version was an error ! I need help from an specialist in kernel compiling. Please read ahead at the next section "The hdapsd - Deamon (next try)". }}
After your house is clean you can do :

{{cmdroot|cd /usr/src}}
{{cmdroot|ls -l linux*.deb}}

You should see some newly builded Debian Pakage files. Install them with:

{{cmdroot|dpkg -i linux-headers-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-doc-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-image-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-manual-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-source-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}

After the installation you should reboot your computer, when Grub comes up make sure that you select your newly builded kernel.
Check it with:

{{cmduser|uname -r}}

You should see this "2.6.20.3-ubuntu1.hdapscustom". But now you have the Problem, that you have to recompile the tp_smapi driver.

{{cmduser|cd tp_smapi-0.31}}
$ sudo make install HDAPS=1
{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdaps}}

After :

<pre>
$ dmesg | grep hdaps
</pre>

You should see something like this:

[ 893.752000] hdaps: initial mode latch is 0x05
[ 893.752000] hdaps: setting ec_rate=250, filter_order=2
[ 893.752000] hdaps: fake_data_mode set to 0
[ 893.756000] hdaps: device successfully initialized.
[ 893.756000] input: hdaps as /class/input/input10
[ 893.756000] hdaps: driver successfully loaded.

Now we are ready to try out the hdapsd Deamon which is included in the Gutsy repositories, if you are using Feisty you have to compile it yourself like described here: [http://www.thinkwiki.org/wiki/How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS].

{{cmdroot|sudo hdapsd -d sda -s 12 -a -v}}

Should show this:

[[Image:hdapsd.png]]

If you load it with :

{{cmdroot|sudo hdapsd -d sda -s 12 -a}}

You get nothing until you move your Thinkpad, then you see:

Fri Jul 13 12:30:42 2007: parking
Fri Jul 13 12:30:43 2007: un-parking
Fri Jul 13 12:30:44 2007: parking
Fri Jul 13 12:30:45 2007: un-parking

Now, after I have a working hdaps-deamon I want it to be started at boot time. Because I have upgraded to Gutsy and installed the hdapsd - Package I have a script called /etc/default/hdapsd. Here I have to change some things. HINT: Remember that you still need the /etc/init.d/hdapsd file if you try this on Feisty and maybe you have to do:

{{cmduser|sudo update-rc.d hdapsd defaults}}

to create the init links for the hdapsd init script. My links was already there. My /etc/default/hdapsd script now looks like this:

<pre>
# hdapsd default file

# start hdapsd at boottime?
START="yes"

# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
DISK="sda"

# sensitivity
SENSITIVITY=12

# other options to pass to hdapsd.
# the -d $DISK, -s $SENSITIVITY, -b and -p $PIDFILE options are always passed.
OPTIONS="-a"

</pre>

Now I could use the gnome-hdaps-applet with the following comands:

{{cmduser|mkdir gnome-hdaps-applet}}
{{cmduser|cd gnome-hdaps-applet}}
{{cmduser|wget http://www.zen24593.zen.co.uk/hdaps/gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|tar -xzf gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|sudo apt-get install libpanel-applet2-dev}}
{{cmduser|gcc $(pkg-config --cflags --libs libpanelapplet-2.0) -o gnome-hdaps-applet gnome-hdaps-applet.c}}
{{cmduser|sudo cp gnome-hdaps-applet /usr/bin/}}
{{cmduser|sudo mkdir /usr/share/pixmaps/gnome-hdaps-applet/}}
{{cmduser|sudo cp *.png /usr/share/pixmaps/gnome-hdaps-applet/}}
$ sudo cp GNOME_HDAPS_StatusApplet.server /usr/lib/bonobo/servers/

Now after a restart of the Gnome Session I could find a "HDAPS Status" applet in the "Add to Panel" dialog. I added it, and when I move the Thinkpad it shows me the "Pause" [[Image:Hdaps-paused-small.png]] Symbol, otherwise it shows "Play" [[Image:Hdaps-running-small.png]].

So far so good !!! After I got this running I tried the same steps with the normal Gutsy Kernel (2.6.22-7-generic) on the same way, and it worked ! To my surprise with the same kernel patch.

The only Problem that I now have is that I cannot use restricted modules with my new kernels. Now I have to figure out how to compile restricted modules agains selfmade kernels.

{{HELP| }}

== The hdapsd - Deamon (next try) ==

I am not satisfied with the above result, because I cannot use the accelerated xorg-fglrx driver for my ATI Graphics Card and I cannot use my wireless Intel card ipw3945 driver. And the Ubuntu restricted-manager is not working. PLEASE can someone help me to compile a Ubuntu kernel in the correct way, so that I can use the whole hardware ?

I have done a - I think really ugly hack - to get the restricted-manager working :

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|cp /boot/config-2.6.20-16-generic /lib/modules/2.6.20-16-generic/.config}}
{{cmdroot|gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -16-generic".
Then I compiled the kernel again with:

{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I moved my modules with :

{{cmdroot|mv /lib/modules/2.6.20-16-generic /lib/modules/2.6.20-16-generic.orginal}}

And installed the kernel with:

{{cmdroot|dpkg -i linux-image-2.6.20-16-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers as described above.
Finally I copied the ipw3945.ucode with

{{cmdroot|cp /lib/firmware/2.6.22-7-generic/ipw3945.ucode /lib/firmware/2.6.20-16-generic/ipw3945.ucode}}

My wireless-card is working now !
My ATI Card cannot be configured with restricted-manager!

{{HELP|Please can someone who is conform in compiling Ubuntu kernels and restricted modules help me to do it in the correct way ! And can someone recheck the things described above, because I am not sure about all things that I have written here.
}}

After some days Ubuntu updated the kernel to version 2.6.22-9-generic, so I need to do the steps described above again, with "EXTRAVERSION = -9-generic". But now my wireless card and my grapics card did not work. The restricted-manager crashes when I start it.
So I downloaded the packages ipw3945-1.2.1.tgz and ati-driver-installer-8.39.4-x86.x86_64.run.

First I extracted and installed the Intel Pro Wireless Package:

{{cmduser|tar xzvf ipw3945-1.2.1.tgz}}
{{cmduser|cd ipw3945-1.2.1}}
{{cmduser|make}}
{{cmduser|sudo make install}}

After this I could do :

{{cmduser|sudo modprobe ipw3945}}

The module was loaded, and i was able to use my wireless card now.

For my Radeon Mobility X1400 I did the following steps:

{{cmduser|sudo apt get update}}
{{cmduser|sudo apt-get install module-assistant build-essential fakeroot dh-make debhelper debconf libstdc++5}}

Created a Debian Package with:

{{cmduser|sudo bash ati-driver-installer-8.39.4-x86.x86_64.run --buildpkg Ubuntu/gutsy}}

And blacklisted the old fglrx module with:

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

I added "fglrx" to the line with "DISABLED_MODULES". Then I installed the created Debian Packages with:

{{cmduser|sudo dpkg -i xorg-driver-fglrx_8.39.4-1_i386.deb fglrx-kernel-source_8.39.4-1_i386.deb fglrx-amdcccle_8.39.4-1_i386.deb}}

Then I compiled the kernel Modules:

{{cmduser|sudo module-assistant prepare}}
{{cmduser|sudo module-assistant update}}
{{cmduser|sudo module-assistant build fglrx}}
{{cmduser|sudo module-assistant install fglrx}}
{{cmduser|sudo depmod -a}}

The helpful informations for this was found at http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide.

After this steps my wifi-card and my graphics-card was working and restricted-manager was not crashing when I tried to start it.

== The Browser Buttons ==

I wanted to use the Browser Forward & Backward Buttons within Firefox. After the upgrade my Firefox had version 2.0.0.4

I did :

{{cmduser| sudo gedit ~/.Xmodmap}}

and added the following lines :

keycode 234 = F19

keycode 233 = F20

I saved and closed the file. HINT: You have to re-login to Gnome to get the .Xmodmap file active.

Then I did the things described in [http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work#Firefox How to get special keys to work].

For the Windows Key I added "keycode 115 = F13" to my .Xmodmap File, then I klicked on "System - Einstellungen - Tastenkombinationen"
sorry I don't know how it is called in English. And changed the Entry "Das Panelmenü anzeigen" to F13

== The Brightness Buttons ==

When I wanted to control the brightness, I was not able to change it with {{key|Fn}}{{key|End}}.

So I did the Workaround menitioned here [http://thinkwiki.org/wiki/Problem_with_LCD_brightness_buttons#Workaround for Fedora Core 6 Users].
After this I was able to change the brightness with {{key|Fn}}{{key|Home}} and {{key|Fn}}{{key|End}}, but I don't have the OSD anymore.

== The Fingerprint Reader ==

Do the steps which are described in [http://www.thinkwiki.org/wiki/Installing_Ubuntu_6.10_%28Edgy_Eft%29_on_a_ThinkPad_T60#The_Fingerprint_Reader Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60] until you get to the Point where Keithvassallo says:
"Phew. Now, to make applications actually use the fingerprint reader."

I have done the following things instead of his version:

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

Change the file as following:

<pre>
#%PAM-1.0
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
auth requisite pam_nologin.so
auth required pam_env.so
@include common-auth
@include common-account
session required pam_limits.so
@include common-session
@include common-password
</pre>

and:

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

Change this file as following:

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

With this changes you have the advantage, that you are now able to login to Gnome or KDE whitout entering your password. But if you cancel the "Fingerprint Login", you are still able to login whit your username/password combination.

After I was able to login to my desktop I was unsatisfied, because my Computer still wants to get passwords i.e. when I tried to open Synaptic or when I do any sudo actions.

So I tried to figure out how this sudo thing works. I did the following change to /etc/pam.d/sudo with:

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

<pre>
#%PAM-1.0

auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/ :0
password sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam :0
auth required pam_unix.so nillock_secure
@include common-account

</pre>

With this change I was able to open System Administration tasks with my fingerprint, but the ugly thing is, that you get no information to swipe your finger over the reader when you have switched to a console session with {{Key|Ctrl}}+{{Key|Alt}}+{{Key|F1}}. The fingerprint scanner software will appear at your running X session.

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-10-10T06:02:30Z

Dirk: /* The hdapsd - Deamon (next try) */

== My Thinkpad ==
<pre>
Lenovo Thinkpad R60 9461 HRG
Intel Core2Duo (Merom) 1.83 CPU
120 GB SATA Hitachi HTS54161 Harddisk
2 GB RAM
ATI Mobility X1400
</pre>

Originally equipped with a preinstalled MS Windows Vista Business. So the Harddisk was parted into two Partitions.

1. The Rescue & Recovery Partition

2. The preinstalled Windows Vista Partition

And as the parcel with my new Thinkpad arrived I was surprized, that there was a Windows Vista DVD (only 32 Bit Version) with it.
So I tried Vista - but I was a little bit shocked by it's performance. I never thought that a new computer could take so much time to boot up completely.

I decided to do a clean install of Vista, but I want to have Windows XP and Ubuntu Feisty on the Harddisk too.

== New Installation ==

I wanted to use all Space of the Harddisk, so I decided to kill the Rescue & and Recovery Partition, but to have the chance to go back to the factory default state I ordered Recovery DVD's at the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4HWSE3#Lenovo Support Call Center for Germany].
They shipped the 3 DVD's to me - free of charge - but I think it's only free if your Thinkpad is still in the warranty. I don't know exactly.

Then I created 2 Partitions on my Harddisk, 64 GB for Vista, 20 GB for XP, so 29 GB left free for Linux.

I installed Vista and XP and all the Thinkpad Stuff for each system.

When this was finished I took a Ubuntu Feisty Fawn installation CD and boot my Notebook with it. I created a 4 GB linux-swap partition and a 25 GB root / partition.

Because I want to boot my Ubuntu with the Windows Vista Boot Loader, I decided to install Grub to /dev/sda4 which is my Linux root partition.

The installation of Ubuntu Feisty Fawn works fine, NO PROBLEMS.

NOW I want to boot Linux from the Vista Bootloader, because I don't want to wait for two Bootscreens, and I wan't to have the chance to access the Repair Console of Windows Vista.

First I have to copy the Bootsector of my Linux Partition with:

<pre>
sudo dd if=/dev/sda4 of=/tmp/bootsect.lin bs=512 count=1
</pre>

Copy the bootsect.lin file to a USB-Stick or a writable partition which you can access from Windows Vista.

Now boot Windows Vista and copy the file bootsect.lin to your Systemdrive. In an Command Window with Administrator privileges type:

<pre>
copy bootsect.lin %SYSTEMDRIVE%\

bcdedit /create /d “Ubuntu” /application BOOTSECTOR
</pre>

You will receice an ID like this {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} from bcdedit. This is a uniqe identifier for your new Boot Entry in the Vista Bootloader. Now you will have to manipulate the entry with the following commands:

<pre>
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} device boot
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} PATH \bootsect.lin
bcdedit /displayorder {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} /addlast
bcdedit /timeout 10
</pre>

Then I booted my Ubuntu an did :

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

In this file I canged the entry the following entries:

<pre>
timeout 2
hiddenmenu
</pre>

So the computer starts up with the Windows Vista bootloader and gives me the option to start Windows XP, Windows Vista, Ubuntu and I have the option to do the repair tasks with the {{key|F8}} button on Vista if something fails. If I choose to boot Ubuntu I have the option to press the {{key|ESC}} key within the two seconds delay of the hidden Grub Menu. I.E. to boot another Linux Kernel.

== The tp_smapi modules ==

I did it under Feisty and, after the Upgrade under Gutsy, like described here : [http://www.thinkwiki.org/wiki/Tp_smapi#Installation TP SMAPI] in the Section "Installation on Ubuntu/Debian"
It worked, hdaps-gl and hdaps-pivot shows me now the movements of my Thinkpad. Like you can see here:

[[Image:Hdaps-pivot.png]]

[[Image:Hdaps-gl.png]]

== The Upgrade to Gutsy Gibbon ==

NO PROBLEMS. So why should I upgrade ?

OK I really wanted to get hdapsd (Harddisk Active Protection) to work. I tried a lot of things with Feisty, but I didn't get it going. And after a lot of seach through the Internet I found out that Gutsy Gibbon, the next Release of Ubuntu should have the Package for hdapsd on board.
SO I decided to upgrade to Gutsy - with the knowledge that it is still in Beta Stadium.

Upgrading Ubuntu is really simple, you only have to do the following steps:

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

Search all feisty entries and change them to gutsy. Save and Close the file.

Do:

{{cmduser| sudo apt-get update}}
{{cmduser| sudo apt-get upgrade}}

Go and drink a cup of Tea or Coffee. When you are back you have a message, that you should reboot your System, to get all packages active. So do it.

After the reboot I installed the hdapsd package and I tried to activate the Harddisk Protection with:

{{cmduser| sudo hdapsd -d sda -s 14 -a -v}}

But I still get the message "open(protect_file): No such file or directory". ---- The Same Message that I get in Feisty before I did the Upgrade. So I banged my head on the table and noticed that I'm not tough enough to get this thing working. Maybe someone else.

I decided to get the other things to work.

UPDATE: After some days I tried to get hdapsd to work, again !

== The hdapsd - Deamon (IBM Active Disk Protection) ==

Because I never had compiled or patched a kernel under Ubuntu I had to find out how this works ! After a lot of search in the Internet, the Ubuntu Help and at Thinkwiki.org I found the (hopefully) correct way to do it.

The best information I found was this :
[http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.04_on_a_ThinkPad_T43#Active_Protection_System_.28acceleration_monitor.29|Installing Ubuntu 7.04 on a ThinkPad T43] in section "Disk protection"

Here is what I did to get it to work:

1. Make sure that you have the required packages, with:

{{cmduser|sudo apt-get install build-essential fakeroot kernel-package libncurses5-dev wget bzip2 linux-source}}

2. Get the correct kernel patch for your running kernel from here : [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch_.28apply_using_.27patch_-p1_-l_.3C_hdaps_xx.patch.27.29| HDAPS] section "8.1.1 Kernel patch (apply using 'patch -p1 -l < hdaps_xx.patch')"

After all my experiences I was not sure that there was a patch available for my Gutsy-kernel (2.6.22-7-generic), but I still had my old kernel on the disk. So I booted up the old one (2.6.20-16-generic). Check the running kernel with:

{{cmduser|uname -r}}

You should see something like: 2.6.20-7-generic

Now change to /usr/src and look that the sources for the running kernel are there with:

{{cmduser|cd /usr/src}}
{{cmduser|ls -d linux-source*}}

You should see a file with the name "linux-source-2.6.20.tar.bz2" wich includes the packed kernel sources. You have to extract it, so do:

{{cmduser|sudo su}}
{{cmdroot|tar xvfj linux-source-2.6.20.tar.bz2}}

Now you have the kernel sources in the /usr/src/linux-source-2.6.20 directory. Take a look if there is a link from /usr/src/linux to an other kernel source directory (It's maybe there if you tried to compile a kernel some time before).

{{cmdroot|ls -l linux}}

If you see that linux is linked to an other source than your running kernel remove the link and create a new one with:

{{cmdroot|rm linux}}
{{cmdroot|ln -s /usr/src/linux-source-2.6.20 linux}}

Change to the source directory and patch the kernel with this:

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|patch -p1 -l < /home/dirk/993-001.bin}}

The file "993-001.bin" is the kernel patch for the 2.6.20 and 2.6.21 kernels, I downloaded it here : [http://article.gmane.org/gmane.linux.drivers.hdaps.devel/993]

After the patchwork I did this :

{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --append-to-version=.hdapscustom kernel_image --initrd binary

This would take its time, so go and clean up your house ;-)
{{HELP|I think the last command (with --append-to-version was an error ! I need help from an specialist in kernel compiling. Please read ahead at the next section "The hdapsd - Deamon (next try)". }}
After your house is clean you can do :

{{cmdroot|cd /usr/src}}
{{cmdroot|ls -l linux*.deb}}

You should see some newly builded Debian Pakage files. Install them with:

{{cmdroot|dpkg -i linux-headers-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-doc-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-image-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-manual-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-source-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}

After the installation you should reboot your computer, when Grub comes up make sure that you select your newly builded kernel.
Check it with:

{{cmduser|uname -r}}

You should see this "2.6.20.3-ubuntu1.hdapscustom". But now you have the Problem, that you have to recompile the tp_smapi driver.

{{cmduser|cd tp_smapi-0.31}}
$ sudo make install HDAPS=1
{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdaps}}

After :

<pre>
$ dmesg | grep hdaps
</pre>

You should see something like this:

[ 893.752000] hdaps: initial mode latch is 0x05
[ 893.752000] hdaps: setting ec_rate=250, filter_order=2
[ 893.752000] hdaps: fake_data_mode set to 0
[ 893.756000] hdaps: device successfully initialized.
[ 893.756000] input: hdaps as /class/input/input10
[ 893.756000] hdaps: driver successfully loaded.

Now we are ready to try out the hdapsd Deamon which is included in the Gutsy repositories, if you are using Feisty you have to compile it yourself like described here: [http://www.thinkwiki.org/wiki/How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS].

{{cmdroot|sudo hdapsd -d sda -s 12 -a -v}}

Should show this:

[[Image:hdapsd.png]]

If you load it with :

{{cmdroot|sudo hdapsd -d sda -s 12 -a}}

You get nothing until you move your Thinkpad, then you see:

Fri Jul 13 12:30:42 2007: parking
Fri Jul 13 12:30:43 2007: un-parking
Fri Jul 13 12:30:44 2007: parking
Fri Jul 13 12:30:45 2007: un-parking

Now, after I have a working hdaps-deamon I want it to be started at boot time. Because I have upgraded to Gutsy and installed the hdapsd - Package I have a script called /etc/default/hdapsd. Here I have to change some things. HINT: Remember that you still need the /etc/init.d/hdapsd file if you try this on Feisty and maybe you have to do:

{{cmduser|sudo update-rc.d hdapsd defaults}}

to create the init links for the hdapsd init script. My links was already there. My /etc/default/hdapsd script now looks like this:

<pre>
# hdapsd default file

# start hdapsd at boottime?
START="yes"

# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
DISK="sda"

# sensitivity
SENSITIVITY=12

# other options to pass to hdapsd.
# the -d $DISK, -s $SENSITIVITY, -b and -p $PIDFILE options are always passed.
OPTIONS="-a"

</pre>

Now I could use the gnome-hdaps-applet with the following comands:

{{cmduser|mkdir gnome-hdaps-applet}}
{{cmduser|cd gnome-hdaps-applet}}
{{cmduser|wget http://www.zen24593.zen.co.uk/hdaps/gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|tar -xzf gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|sudo apt-get install libpanel-applet2-dev}}
{{cmduser|gcc $(pkg-config --cflags --libs libpanelapplet-2.0) -o gnome-hdaps-applet gnome-hdaps-applet.c}}
{{cmduser|sudo cp gnome-hdaps-applet /usr/bin/}}
{{cmduser|sudo mkdir /usr/share/pixmaps/gnome-hdaps-applet/}}
{{cmduser|sudo cp *.png /usr/share/pixmaps/gnome-hdaps-applet/}}
$ sudo cp GNOME_HDAPS_StatusApplet.server /usr/lib/bonobo/servers/

Now after a restart of the Gnome Session I could find a "HDAPS Status" applet in the "Add to Panel" dialog. I added it, and when I move the Thinkpad it shows me the "Pause" [[Image:Hdaps-paused-small.png]] Symbol, otherwise it shows "Play" [[Image:Hdaps-running-small.png]].

So far so good !!! After I got this running I tried the same steps with the normal Gutsy Kernel (2.6.22-7-generic) on the same way, and it worked ! To my surprise with the same kernel patch.

The only Problem that I now have is that I cannot use restricted modules with my new kernels. Now I have to figure out how to compile restricted modules agains selfmade kernels.

{{HELP| }}

== The hdapsd - Deamon (next try) ==

I am not satisfied with the above result, because I cannot use the accelerated xorg-fglrx driver for my ATI Graphics Card and I cannot use my wireless Intel card ipw3945 driver. And the Ubuntu restricted-manager is not working. PLEASE can someone help me to compile a Ubuntu kernel in the correct way, so that I can use the whole hardware ?

I have done a - I think really ugly hack - to get the restricted-manager working :

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|cp /boot/config-2.6.20-16-generic /lib/modules/2.6.20-16-generic/.config}}
{{cmdroot|gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -16-generic".
Then I did compile the kernel again with:

{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I moved my modules with :

{{cmdroot|mv /lib/modules/2.6.20-16-generic /lib/modules/2.6.20-16-generic.orginal}}

And installed the kernel with:

{{cmdroot|dpkg -i linux-image-2.6.20-16-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers as described above.
Finally I copied the ipw3945.ucode with

{{cmdroot|cp /lib/firmware/2.6.22-7-generic/ipw3945.ucode /lib/firmware/2.6.20-16-generic/ipw3945.ucode}}

My wireless-card is working now !
My ATI Card cannot be configured with restricted-manager!

{{HELP|Please can someone who is conform in compiling Ubuntu kernels and restricted modules help me to do it in the correct way ! And can someone recheck the things described above, because I am not sure about all things that I have written here.
}}

After some days Ubuntu updated the kernel to version 2.6.22-9-generic, so I need to do the steps described above again, with "EXTRAVERSION = -9-generic". But now my wireless card and my grapics card did not work. The restricted-manager crashes when I start it.
So I downloaded the packages ipw3945-1.2.1.tgz and ati-driver-installer-8.39.4-x86.x86_64.run.

First I extracted and installed the Intel Pro Wireless Package:

{{cmduser|tar xzvf ipw3945-1.2.1.tgz}}
{{cmduser|cd ipw3945-1.2.1}}
{{cmduser|make}}
{{cmduser|sudo make install}}

After this I could do :

{{cmduser|sudo modprobe ipw3945}}

The module was loaded, and i was able to use my wireless card now.

For my Radeon Mobility X1400 I did the following steps:

{{cmduser|sudo apt get update}}
{{cmduser|sudo apt-get install module-assistant build-essential fakeroot dh-make debhelper debconf libstdc++5}}

Created a Debian Package with:

{{cmduser|sudo bash ati-driver-installer-8.39.4-x86.x86_64.run --buildpkg Ubuntu/gutsy}}

And blacklisted the old fglrx module with:

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

I added "fglrx" to the line with "DISABLED_MODULES". Then I installed the created Debian Packages with:

{{cmduser|sudo dpkg -i xorg-driver-fglrx_8.39.4-1_i386.deb fglrx-kernel-source_8.39.4-1_i386.deb fglrx-amdcccle_8.39.4-1_i386.deb}}

Then I compiled the kernel Modules:

{{cmduser|sudo module-assistant prepare}}
{{cmduser|sudo module-assistant update}}
{{cmduser|sudo module-assistant build fglrx}}
{{cmduser|sudo module-assistant install fglrx}}
{{cmduser|sudo depmod -a}}

The helpful informations for this was found at http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide.

After this steps my wifi-card and my graphics-card was working and restricted-manager was not crashing when I tried to start it.

== The Browser Buttons ==

I wanted to use the Browser Forward & Backward Buttons within Firefox. After the upgrade my Firefox had version 2.0.0.4

I did :

{{cmduser| sudo gedit ~/.Xmodmap}}

and added the following lines :

keycode 234 = F19

keycode 233 = F20

I saved and closed the file. HINT: You have to re-login to Gnome to get the .Xmodmap file active.

Then I did the things described in [http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work#Firefox How to get special keys to work].

For the Windows Key I added "keycode 115 = F13" to my .Xmodmap File, then I klicked on "System - Einstellungen - Tastenkombinationen"
sorry I don't know how it is called in English. And changed the Entry "Das Panelmenü anzeigen" to F13

== The Brightness Buttons ==

When I wanted to control the brightness, I was not able to change it with {{key|Fn}}{{key|End}}.

So I did the Workaround menitioned here [http://thinkwiki.org/wiki/Problem_with_LCD_brightness_buttons#Workaround for Fedora Core 6 Users].
After this I was able to change the brightness with {{key|Fn}}{{key|Home}} and {{key|Fn}}{{key|End}}, but I don't have the OSD anymore.

== The Fingerprint Reader ==

Do the steps which are described in [http://www.thinkwiki.org/wiki/Installing_Ubuntu_6.10_%28Edgy_Eft%29_on_a_ThinkPad_T60#The_Fingerprint_Reader Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60] until you get to the Point where Keithvassallo says:
"Phew. Now, to make applications actually use the fingerprint reader."

I have done the following things instead of his version:

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

Change the file as following:

<pre>
#%PAM-1.0
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
auth requisite pam_nologin.so
auth required pam_env.so
@include common-auth
@include common-account
session required pam_limits.so
@include common-session
@include common-password
</pre>

and:

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

Change this file as following:

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

With this changes you have the advantage, that you are now able to login to Gnome or KDE whitout entering your password. But if you cancel the "Fingerprint Login", you are still able to login whit your username/password combination.

After I was able to login to my desktop I was unsatisfied, because my Computer still wants to get passwords i.e. when I tried to open Synaptic or when I do any sudo actions.

So I tried to figure out how this sudo thing works. I did the following change to /etc/pam.d/sudo with:

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

<pre>
#%PAM-1.0

auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/ :0
password sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam :0
auth required pam_unix.so nillock_secure
@include common-account

</pre>

With this change I was able to open System Administration tasks with my fingerprint, but the ugly thing is, that you get no information to swipe your finger over the reader when you have switched to a console session with {{Key|Ctrl}}+{{Key|Alt}}+{{Key|F1}}. The fingerprint scanner software will appear at your running X session.

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-09-25T05:41:39Z

Dirk: /* The hdapsd - Deamon (IBM Active Disk Protection) */

== My Thinkpad ==
<pre>
Lenovo Thinkpad R60 9461 HRG
Intel Core2Duo (Merom) 1.83 CPU
120 GB SATA Hitachi HTS54161 Harddisk
2 GB RAM
ATI Mobility X1400
</pre>

Originally equipped with a preinstalled MS Windows Vista Business. So the Harddisk was parted into two Partitions.

1. The Rescue & Recovery Partition

2. The preinstalled Windows Vista Partition

And as the parcel with my new Thinkpad arrived I was surprized, that there was a Windows Vista DVD (only 32 Bit Version) with it.
So I tried Vista - but I was a little bit shocked by it's performance. I never thought that a new computer could take so much time to boot up completely.

I decided to do a clean install of Vista, but I want to have Windows XP and Ubuntu Feisty on the Harddisk too.

== New Installation ==

I wanted to use all Space of the Harddisk, so I decided to kill the Rescue & and Recovery Partition, but to have the chance to go back to the factory default state I ordered Recovery DVD's at the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4HWSE3#Lenovo Support Call Center for Germany].
They shipped the 3 DVD's to me - free of charge - but I think it's only free if your Thinkpad is still in the warranty. I don't know exactly.

Then I created 2 Partitions on my Harddisk, 64 GB for Vista, 20 GB for XP, so 29 GB left free for Linux.

I installed Vista and XP and all the Thinkpad Stuff for each system.

When this was finished I took a Ubuntu Feisty Fawn installation CD and boot my Notebook with it. I created a 4 GB linux-swap partition and a 25 GB root / partition.

Because I want to boot my Ubuntu with the Windows Vista Boot Loader, I decided to install Grub to /dev/sda4 which is my Linux root partition.

The installation of Ubuntu Feisty Fawn works fine, NO PROBLEMS.

NOW I want to boot Linux from the Vista Bootloader, because I don't want to wait for two Bootscreens, and I wan't to have the chance to access the Repair Console of Windows Vista.

First I have to copy the Bootsector of my Linux Partition with:

<pre>
sudo dd if=/dev/sda4 of=/tmp/bootsect.lin bs=512 count=1
</pre>

Copy the bootsect.lin file to a USB-Stick or a writable partition which you can access from Windows Vista.

Now boot Windows Vista and copy the file bootsect.lin to your Systemdrive. In an Command Window with Administrator privileges type:

<pre>
copy bootsect.lin %SYSTEMDRIVE%\

bcdedit /create /d “Ubuntu” /application BOOTSECTOR
</pre>

You will receice an ID like this {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} from bcdedit. This is a uniqe identifier for your new Boot Entry in the Vista Bootloader. Now you will have to manipulate the entry with the following commands:

<pre>
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} device boot
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} PATH \bootsect.lin
bcdedit /displayorder {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} /addlast
bcdedit /timeout 10
</pre>

Then I booted my Ubuntu an did :

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

In this file I canged the entry the following entries:

<pre>
timeout 2
hiddenmenu
</pre>

So the computer starts up with the Windows Vista bootloader and gives me the option to start Windows XP, Windows Vista, Ubuntu and I have the option to do the repair tasks with the {{key|F8}} button on Vista if something fails. If I choose to boot Ubuntu I have the option to press the {{key|ESC}} key within the two seconds delay of the hidden Grub Menu. I.E. to boot another Linux Kernel.

== The tp_smapi modules ==

I did it under Feisty and, after the Upgrade under Gutsy, like described here : [http://www.thinkwiki.org/wiki/Tp_smapi#Installation TP SMAPI] in the Section "Installation on Ubuntu/Debian"
It worked, hdaps-gl and hdaps-pivot shows me now the movements of my Thinkpad. Like you can see here:

[[Image:Hdaps-pivot.png]]

[[Image:Hdaps-gl.png]]

== The Upgrade to Gutsy Gibbon ==

NO PROBLEMS. So why should I upgrade ?

OK I really wanted to get hdapsd (Harddisk Active Protection) to work. I tried a lot of things with Feisty, but I didn't get it going. And after a lot of seach through the Internet I found out that Gutsy Gibbon, the next Release of Ubuntu should have the Package for hdapsd on board.
SO I decided to upgrade to Gutsy - with the knowledge that it is still in Beta Stadium.

Upgrading Ubuntu is really simple, you only have to do the following steps:

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

Search all feisty entries and change them to gutsy. Save and Close the file.

Do:

{{cmduser| sudo apt-get update}}
{{cmduser| sudo apt-get upgrade}}

Go and drink a cup of Tea or Coffee. When you are back you have a message, that you should reboot your System, to get all packages active. So do it.

After the reboot I installed the hdapsd package and I tried to activate the Harddisk Protection with:

{{cmduser| sudo hdapsd -d sda -s 14 -a -v}}

But I still get the message "open(protect_file): No such file or directory". ---- The Same Message that I get in Feisty before I did the Upgrade. So I banged my head on the table and noticed that I'm not tough enough to get this thing working. Maybe someone else.

I decided to get the other things to work.

UPDATE: After some days I tried to get hdapsd to work, again !

== The hdapsd - Deamon (IBM Active Disk Protection) ==

Because I never had compiled or patched a kernel under Ubuntu I had to find out how this works ! After a lot of search in the Internet, the Ubuntu Help and at Thinkwiki.org I found the (hopefully) correct way to do it.

The best information I found was this :
[http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.04_on_a_ThinkPad_T43#Active_Protection_System_.28acceleration_monitor.29|Installing Ubuntu 7.04 on a ThinkPad T43] in section "Disk protection"

Here is what I did to get it to work:

1. Make sure that you have the required packages, with:

{{cmduser|sudo apt-get install build-essential fakeroot kernel-package libncurses5-dev wget bzip2 linux-source}}

2. Get the correct kernel patch for your running kernel from here : [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch_.28apply_using_.27patch_-p1_-l_.3C_hdaps_xx.patch.27.29| HDAPS] section "8.1.1 Kernel patch (apply using 'patch -p1 -l < hdaps_xx.patch')"

After all my experiences I was not sure that there was a patch available for my Gutsy-kernel (2.6.22-7-generic), but I still had my old kernel on the disk. So I booted up the old one (2.6.20-16-generic). Check the running kernel with:

{{cmduser|uname -r}}

You should see something like: 2.6.20-7-generic

Now change to /usr/src and look that the sources for the running kernel are there with:

{{cmduser|cd /usr/src}}
{{cmduser|ls -d linux-source*}}

You should see a file with the name "linux-source-2.6.20.tar.bz2" wich includes the packed kernel sources. You have to extract it, so do:

{{cmduser|sudo su}}
{{cmdroot|tar xvfj linux-source-2.6.20.tar.bz2}}

Now you have the kernel sources in the /usr/src/linux-source-2.6.20 directory. Take a look if there is a link from /usr/src/linux to an other kernel source directory (It's maybe there if you tried to compile a kernel some time before).

{{cmdroot|ls -l linux}}

If you see that linux is linked to an other source than your running kernel remove the link and create a new one with:

{{cmdroot|rm linux}}
{{cmdroot|ln -s /usr/src/linux-source-2.6.20 linux}}

Change to the source directory and patch the kernel with this:

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|patch -p1 -l < /home/dirk/993-001.bin}}

The file "993-001.bin" is the kernel patch for the 2.6.20 and 2.6.21 kernels, I downloaded it here : [http://article.gmane.org/gmane.linux.drivers.hdaps.devel/993]

After the patchwork I did this :

{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --append-to-version=.hdapscustom kernel_image --initrd binary

This would take its time, so go and clean up your house ;-)
{{HELP|I think the last command (with --append-to-version was an error ! I need help from an specialist in kernel compiling. Please read ahead at the next section "The hdapsd - Deamon (next try)". }}
After your house is clean you can do :

{{cmdroot|cd /usr/src}}
{{cmdroot|ls -l linux*.deb}}

You should see some newly builded Debian Pakage files. Install them with:

{{cmdroot|dpkg -i linux-headers-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-doc-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-image-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-manual-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-source-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}

After the installation you should reboot your computer, when Grub comes up make sure that you select your newly builded kernel.
Check it with:

{{cmduser|uname -r}}

You should see this "2.6.20.3-ubuntu1.hdapscustom". But now you have the Problem, that you have to recompile the tp_smapi driver.

{{cmduser|cd tp_smapi-0.31}}
$ sudo make install HDAPS=1
{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdaps}}

After :

<pre>
$ dmesg | grep hdaps
</pre>

You should see something like this:

[ 893.752000] hdaps: initial mode latch is 0x05
[ 893.752000] hdaps: setting ec_rate=250, filter_order=2
[ 893.752000] hdaps: fake_data_mode set to 0
[ 893.756000] hdaps: device successfully initialized.
[ 893.756000] input: hdaps as /class/input/input10
[ 893.756000] hdaps: driver successfully loaded.

Now we are ready to try out the hdapsd Deamon which is included in the Gutsy repositories, if you are using Feisty you have to compile it yourself like described here: [http://www.thinkwiki.org/wiki/How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS].

{{cmdroot|sudo hdapsd -d sda -s 12 -a -v}}

Should show this:

[[Image:hdapsd.png]]

If you load it with :

{{cmdroot|sudo hdapsd -d sda -s 12 -a}}

You get nothing until you move your Thinkpad, then you see:

Fri Jul 13 12:30:42 2007: parking
Fri Jul 13 12:30:43 2007: un-parking
Fri Jul 13 12:30:44 2007: parking
Fri Jul 13 12:30:45 2007: un-parking

Now, after I have a working hdaps-deamon I want it to be started at boot time. Because I have upgraded to Gutsy and installed the hdapsd - Package I have a script called /etc/default/hdapsd. Here I have to change some things. HINT: Remember that you still need the /etc/init.d/hdapsd file if you try this on Feisty and maybe you have to do:

{{cmduser|sudo update-rc.d hdapsd defaults}}

to create the init links for the hdapsd init script. My links was already there. My /etc/default/hdapsd script now looks like this:

<pre>
# hdapsd default file

# start hdapsd at boottime?
START="yes"

# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
DISK="sda"

# sensitivity
SENSITIVITY=12

# other options to pass to hdapsd.
# the -d $DISK, -s $SENSITIVITY, -b and -p $PIDFILE options are always passed.
OPTIONS="-a"

</pre>

Now I could use the gnome-hdaps-applet with the following comands:

{{cmduser|mkdir gnome-hdaps-applet}}
{{cmduser|cd gnome-hdaps-applet}}
{{cmduser|wget http://www.zen24593.zen.co.uk/hdaps/gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|tar -xzf gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|sudo apt-get install libpanel-applet2-dev}}
{{cmduser|gcc $(pkg-config --cflags --libs libpanelapplet-2.0) -o gnome-hdaps-applet gnome-hdaps-applet.c}}
{{cmduser|sudo cp gnome-hdaps-applet /usr/bin/}}
{{cmduser|sudo mkdir /usr/share/pixmaps/gnome-hdaps-applet/}}
{{cmduser|sudo cp *.png /usr/share/pixmaps/gnome-hdaps-applet/}}
$ sudo cp GNOME_HDAPS_StatusApplet.server /usr/lib/bonobo/servers/

Now after a restart of the Gnome Session I could find a "HDAPS Status" applet in the "Add to Panel" dialog. I added it, and when I move the Thinkpad it shows me the "Pause" [[Image:Hdaps-paused-small.png]] Symbol, otherwise it shows "Play" [[Image:Hdaps-running-small.png]].

So far so good !!! After I got this running I tried the same steps with the normal Gutsy Kernel (2.6.22-7-generic) on the same way, and it worked ! To my surprise with the same kernel patch.

The only Problem that I now have is that I cannot use restricted modules with my new kernels. Now I have to figure out how to compile restricted modules agains selfmade kernels.

{{HELP| }}

== The hdapsd - Deamon (next try) ==

I am not satisfied with the above result, because I cannot use the accelerated xorg-fglrx driver for my ATI Graphics Card and I cannot use my wireless Intel card ipw3945 driver. And the Ubuntu restricted-manager is not working. PLEASE can someone help me to compile a Ubuntu kernel in the correct way, so that I can use the whole hardware ?

I have done a - I think really ugly hack - to get the restricted-manager working :

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|cp /boot/config-2.6.20-16-generic /lib/modules/2.6.20-generic/.config}}
{{cmdroot|gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -16-generic".
Then I did compile the kernel again with:

{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I moved my modules with :

{{cmdroot|mv /lib/modules/2.6.20-16-generic /lib/modules/2.6.20-16-generic.orginal}}

And installed the kernel with:

{{cmdroot|dpkg -i linux-image-2.6.20-16-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers as described above.
Finally I copied the ipw3945.ucode with

{{cmdroot|cp /lib/firmware/2.6.22-7-generic/ipw3945.ucode /lib/firmware/2.6.20-16-generic/ipw3945.ucode}}

My wireless-card is working now !
My ATI Card cannot be configured with restricted-manager!

{{HELP|Please can someone who is conform in compiling Ubuntu kernels and restricted modules help me to do it in the correct way ! And can someone recheck the things described above, because I am not sure about all things that I have written here.
}}

After some days Ubuntu updated the kernel to version 2.6.22-9-generic, so I need to do the steps described above again, with "EXTRAVERSION = -9-generic". But now my wireless card and my grapics card did not work. The restricted-manager crashes when I start it.
So I downloaded the packages ipw3945-1.2.1.tgz and ati-driver-installer-8.39.4-x86.x86_64.run.

First I extracted and installed the Intel Pro Wireless Package:

{{cmduser|tar xzvf ipw3945-1.2.1.tgz}}
{{cmduser|cd ipw3945-1.2.1}}
{{cmduser|make}}
{{cmduser|sudo make install}}

After this I could do :

{{cmduser|sudo modprobe ipw3945}}

The module was loaded, and i was able to use my wireless card now.

For my Radeon Mobility X1400 I did the following steps:

{{cmduser|sudo apt get update}}
{{cmduser|sudo apt-get install module-assistant build-essential fakeroot dh-make debhelper debconf libstdc++5}}

Created a Debian Package with:

{{cmduser|sudo bash ati-driver-installer-8.39.4-x86.x86_64.run --buildpkg Ubuntu/gutsy}}

And blacklisted the old fglrx module with:

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

I added "fglrx" to the line with "DISABLED_MODULES". Then I installed the created Debian Packages with:

{{cmduser|sudo dpkg -i xorg-driver-fglrx_8.39.4-1_i386.deb fglrx-kernel-source_8.39.4-1_i386.deb fglrx-amdcccle_8.39.4-1_i386.deb}}

Then I compiled the kernel Modules:

{{cmduser|sudo module-assistant prepare}}
{{cmduser|sudo module-assistant update}}
{{cmduser|sudo module-assistant build fglrx}}
{{cmduser|sudo module-assistant install fglrx}}
{{cmduser|sudo depmod -a}}

The helpful informations for this was found at http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide.

After this steps my wifi-card and my graphics-card was working and restricted-manager was not crashing when I tried to start it.

== The Browser Buttons ==

I wanted to use the Browser Forward & Backward Buttons within Firefox. After the upgrade my Firefox had version 2.0.0.4

I did :

{{cmduser| sudo gedit ~/.Xmodmap}}

and added the following lines :

keycode 234 = F19

keycode 233 = F20

I saved and closed the file. HINT: You have to re-login to Gnome to get the .Xmodmap file active.

Then I did the things described in [http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work#Firefox How to get special keys to work].

For the Windows Key I added "keycode 115 = F13" to my .Xmodmap File, then I klicked on "System - Einstellungen - Tastenkombinationen"
sorry I don't know how it is called in English. And changed the Entry "Das Panelmenü anzeigen" to F13

== The Brightness Buttons ==

When I wanted to control the brightness, I was not able to change it with {{key|Fn}}{{key|End}}.

So I did the Workaround menitioned here [http://thinkwiki.org/wiki/Problem_with_LCD_brightness_buttons#Workaround for Fedora Core 6 Users].
After this I was able to change the brightness with {{key|Fn}}{{key|Home}} and {{key|Fn}}{{key|End}}, but I don't have the OSD anymore.

== The Fingerprint Reader ==

Do the steps which are described in [http://www.thinkwiki.org/wiki/Installing_Ubuntu_6.10_%28Edgy_Eft%29_on_a_ThinkPad_T60#The_Fingerprint_Reader Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60] until you get to the Point where Keithvassallo says:
"Phew. Now, to make applications actually use the fingerprint reader."

I have done the following things instead of his version:

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

Change the file as following:

<pre>
#%PAM-1.0
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
auth requisite pam_nologin.so
auth required pam_env.so
@include common-auth
@include common-account
session required pam_limits.so
@include common-session
@include common-password
</pre>

and:

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

Change this file as following:

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

With this changes you have the advantage, that you are now able to login to Gnome or KDE whitout entering your password. But if you cancel the "Fingerprint Login", you are still able to login whit your username/password combination.

After I was able to login to my desktop I was unsatisfied, because my Computer still wants to get passwords i.e. when I tried to open Synaptic or when I do any sudo actions.

So I tried to figure out how this sudo thing works. I did the following change to /etc/pam.d/sudo with:

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

<pre>
#%PAM-1.0

auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/ :0
password sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam :0
auth required pam_unix.so nillock_secure
@include common-account

</pre>

With this change I was able to open System Administration tasks with my fingerprint, but the ugly thing is, that you get no information to swipe your finger over the reader when you have switched to a console session with {{Key|Ctrl}}+{{Key|Alt}}+{{Key|F1}}. The fingerprint scanner software will appear at your running X session.

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-09-06T08:47:23Z

Dirk: /* The hdapsd - Deamon (IBM Active Disk Protection) */

== My Thinkpad ==
<pre>
Lenovo Thinkpad R60 9461 HRG
Intel Core2Duo (Merom) 1.83 CPU
120 GB SATA Hitachi HTS54161 Harddisk
2 GB RAM
ATI Mobility X1400
</pre>

Originally equipped with a preinstalled MS Windows Vista Business. So the Harddisk was parted into two Partitions.

1. The Rescue & Recovery Partition

2. The preinstalled Windows Vista Partition

And as the parcel with my new Thinkpad arrived I was surprized, that there was a Windows Vista DVD (only 32 Bit Version) with it.
So I tried Vista - but I was a little bit shocked by it's performance. I never thought that a new computer could take so much time to boot up completely.

I decided to do a clean install of Vista, but I want to have Windows XP and Ubuntu Feisty on the Harddisk too.

== New Installation ==

I wanted to use all Space of the Harddisk, so I decided to kill the Rescue & and Recovery Partition, but to have the chance to go back to the factory default state I ordered Recovery DVD's at the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4HWSE3#Lenovo Support Call Center for Germany].
They shipped the 3 DVD's to me - free of charge - but I think it's only free if your Thinkpad is still in the warranty. I don't know exactly.

Then I created 2 Partitions on my Harddisk, 64 GB for Vista, 20 GB for XP, so 29 GB left free for Linux.

I installed Vista and XP and all the Thinkpad Stuff for each system.

When this was finished I took a Ubuntu Feisty Fawn installation CD and boot my Notebook with it. I created a 4 GB linux-swap partition and a 25 GB root / partition.

Because I want to boot my Ubuntu with the Windows Vista Boot Loader, I decided to install Grub to /dev/sda4 which is my Linux root partition.

The installation of Ubuntu Feisty Fawn works fine, NO PROBLEMS.

NOW I want to boot Linux from the Vista Bootloader, because I don't want to wait for two Bootscreens, and I wan't to have the chance to access the Repair Console of Windows Vista.

First I have to copy the Bootsector of my Linux Partition with:

<pre>
sudo dd if=/dev/sda4 of=/tmp/bootsect.lin bs=512 count=1
</pre>

Copy the bootsect.lin file to a USB-Stick or a writable partition which you can access from Windows Vista.

Now boot Windows Vista and copy the file bootsect.lin to your Systemdrive. In an Command Window with Administrator privileges type:

<pre>
copy bootsect.lin %SYSTEMDRIVE%\

bcdedit /create /d “Ubuntu” /application BOOTSECTOR
</pre>

You will receice an ID like this {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} from bcdedit. This is a uniqe identifier for your new Boot Entry in the Vista Bootloader. Now you will have to manipulate the entry with the following commands:

<pre>
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} device boot
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} PATH \bootsect.lin
bcdedit /displayorder {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} /addlast
bcdedit /timeout 10
</pre>

Then I booted my Ubuntu an did :

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

In this file I canged the entry the following entries:

<pre>
timeout 2
hiddenmenu
</pre>

So the computer starts up with the Windows Vista bootloader and gives me the option to start Windows XP, Windows Vista, Ubuntu and I have the option to do the repair tasks with the {{key|F8}} button on Vista if something fails. If I choose to boot Ubuntu I have the option to press the {{key|ESC}} key within the two seconds delay of the hidden Grub Menu. I.E. to boot another Linux Kernel.

== The tp_smapi modules ==

I did it under Feisty and, after the Upgrade under Gutsy, like described here : [http://www.thinkwiki.org/wiki/Tp_smapi#Installation TP SMAPI] in the Section "Installation on Ubuntu/Debian"
It worked, hdaps-gl and hdaps-pivot shows me now the movements of my Thinkpad. Like you can see here:

[[Image:Hdaps-pivot.png]]

[[Image:Hdaps-gl.png]]

== The Upgrade to Gutsy Gibbon ==

NO PROBLEMS. So why should I upgrade ?

OK I really wanted to get hdapsd (Harddisk Active Protection) to work. I tried a lot of things with Feisty, but I didn't get it going. And after a lot of seach through the Internet I found out that Gutsy Gibbon, the next Release of Ubuntu should have the Package for hdapsd on board.
SO I decided to upgrade to Gutsy - with the knowledge that it is still in Beta Stadium.

Upgrading Ubuntu is really simple, you only have to do the following steps:

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

Search all feisty entries and change them to gutsy. Save and Close the file.

Do:

{{cmduser| sudo apt-get update}}
{{cmduser| sudo apt-get upgrade}}

Go and drink a cup of Tea or Coffee. When you are back you have a message, that you should reboot your System, to get all packages active. So do it.

After the reboot I installed the hdapsd package and I tried to activate the Harddisk Protection with:

{{cmduser| sudo hdapsd -d sda -s 14 -a -v}}

But I still get the message "open(protect_file): No such file or directory". ---- The Same Message that I get in Feisty before I did the Upgrade. So I banged my head on the table and noticed that I'm not tough enough to get this thing working. Maybe someone else.

I decided to get the other things to work.

UPDATE: After some days I tried to get hdapsd to work, again !

== The hdapsd - Deamon (IBM Active Disk Protection) ==

Because I never had compiled or patched a kernel under Ubuntu I had to find out how this works ! After a lot of search in the Internet, the Ubuntu Help and at Thinkwiki.org I found the (hopefully) correct way to do it.

The best information I found was this :
[http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.04_on_a_ThinkPad_T43#Active_Protection_System_.28acceleration_monitor.29|Installing Ubuntu 7.04 on a ThinkPad T43] in section "Disk protection"

Here is what I did to get it to work:

1. Make sure that you have the required packages, with:

{{cmduser|sudo apt-get install build-essential fakeroot kernel-package libncurses5-dev wget bzip2 linux-source}}

2. Get the correct kernel patch for your running kernel from here : [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch_.28apply_using_.27patch_-p1_-l_.3C_hdaps_xx.patch.27.29| HDAPS] section "8.1.1 Kernel patch (apply using 'patch -p1 -l < hdaps_xx.patch')"

After all my experiences I was not sure that there was a patch available for my Gutsy-kernel (2.6.22-7-generic), but I still had my old kernel on the disk. So I booted up the old one (2.6.20-16-generic). Check the running kernel with:

{{cmduser|uname -r}}

You should see something like: 2.6.20-7-generic

Now change to /usr/src and look that the sources for the running kernel are there with:

{{cmduser|cd /usr/src}}
{{cmduser|ls -d linux-source*}}

You should see a file with the name "linux-source-2.6.20.tar.bz2" wich includes the packed kernel sources. You have to extract it, so do:

{{cmduser|sudo su}}
{{cmdroot|tar xvfj linux-source-2.6.20.tar.bz2}}

Now you have the kernel sources in the /usr/src/linux-source-2.6.20 directory. Take a look if there is a link from /usr/src/linux to an other kernel source directory (It's maybe there if you tried to compile a kernel some time before).

{{cmdroot|ls -l linux}}

If you see that linux is linked to an other source than your running kernel remove the link and create a new one with:

{{cmdroot|rm -r linux}}
{{cmdroot|ln -s /usr/src/linux-source-2.6.20 linux}}

Change to the source directory and patch the kernel with this:

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|patch -p1 -l < /home/dirk/993-001.bin}}

The file "993-001.bin" is the kernel patch for the 2.6.20 and 2.6.21 kernels, I downloaded it here : [http://article.gmane.org/gmane.linux.drivers.hdaps.devel/993]

After the patchwork I did this :

{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --append-to-version=.hdapscustom kernel_image --initrd binary

This would take its time, so go and clean up your house ;-)
{{HELP|I think the last command (with --append-to-version was an error ! I need help from an specialist in kernel compiling. Please read ahead at the next section "The hdapsd - Deamon (next try)". }}
After your house is clean you can do :

{{cmdroot|cd /usr/src}}
{{cmdroot|ls -l linux*.deb}}

You should see some newly builded Debian Pakage files. Install them with:

{{cmdroot|dpkg -i linux-headers-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-doc-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-image-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-manual-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-source-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}

After the installation you should reboot your computer, when Grub comes up make sure that you select your newly builded kernel.
Check it with:

{{cmduser|uname -r}}

You should see this "2.6.20.3-ubuntu1.hdapscustom". But now you have the Problem, that you have to recompile the tp_smapi driver.

{{cmduser|cd tp_smapi-0.31}}
$ sudo make install HDAPS=1
{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdaps}}

After :

<pre>
$ dmesg | grep hdaps
</pre>

You should see something like this:

[ 893.752000] hdaps: initial mode latch is 0x05
[ 893.752000] hdaps: setting ec_rate=250, filter_order=2
[ 893.752000] hdaps: fake_data_mode set to 0
[ 893.756000] hdaps: device successfully initialized.
[ 893.756000] input: hdaps as /class/input/input10
[ 893.756000] hdaps: driver successfully loaded.

Now we are ready to try out the hdapsd Deamon which is included in the Gutsy repositories, if you are using Feisty you have to compile it yourself like described here: [http://www.thinkwiki.org/wiki/How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS].

{{cmdroot|sudo hdapsd -d sda -s 12 -a -v}}

Should show this:

[[Image:hdapsd.png]]

If you load it with :

{{cmdroot|sudo hdapsd -d sda -s 12 -a}}

You get nothing until you move your Thinkpad, then you see:

Fri Jul 13 12:30:42 2007: parking
Fri Jul 13 12:30:43 2007: un-parking
Fri Jul 13 12:30:44 2007: parking
Fri Jul 13 12:30:45 2007: un-parking

Now, after I have a working hdaps-deamon I want it to be started at boot time. Because I have upgraded to Gutsy and installed the hdapsd - Package I have a script called /etc/default/hdapsd. Here I have to change some things. HINT: Remember that you still need the /etc/init.d/hdapsd file if you try this on Feisty and maybe you have to do:

{{cmduser|sudo update-rc.d hdapsd defaults}}

to create the init links for the hdapsd init script. My links was already there. My /etc/default/hdapsd script now looks like this:

<pre>
# hdapsd default file

# start hdapsd at boottime?
START="yes"

# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
DISK="sda"

# sensitivity
SENSITIVITY=12

# other options to pass to hdapsd.
# the -d $DISK, -s $SENSITIVITY, -b and -p $PIDFILE options are always passed.
OPTIONS="-a"

</pre>

Now I could use the gnome-hdaps-applet with the following comands:

{{cmduser|mkdir gnome-hdaps-applet}}
{{cmduser|cd gnome-hdaps-applet}}
{{cmduser|wget http://www.zen24593.zen.co.uk/hdaps/gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|tar -xzf gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|sudo apt-get install libpanel-applet2-dev}}
{{cmduser|gcc $(pkg-config --cflags --libs libpanelapplet-2.0) -o gnome-hdaps-applet gnome-hdaps-applet.c}}
{{cmduser|sudo cp gnome-hdaps-applet /usr/bin/}}
{{cmduser|sudo mkdir /usr/share/pixmaps/gnome-hdaps-applet/}}
{{cmduser|sudo cp *.png /usr/share/pixmaps/gnome-hdaps-applet/}}
$ sudo cp GNOME_HDAPS_StatusApplet.server /usr/lib/bonobo/servers/

Now after a restart of the Gnome Session I could find a "HDAPS Status" applet in the "Add to Panel" dialog. I added it, and when I move the Thinkpad it shows me the "Pause" [[Image:Hdaps-paused-small.png]] Symbol, otherwise it shows "Play" [[Image:Hdaps-running-small.png]].

So far so good !!! After I got this running I tried the same steps with the normal Gutsy Kernel (2.6.22-7-generic) on the same way, and it worked ! To my surprise with the same kernel patch.

The only Problem that I now have is that I cannot use restricted modules with my new kernels. Now I have to figure out how to compile restricted modules agains selfmade kernels.

{{HELP| }}

== The hdapsd - Deamon (next try) ==

I am not satisfied with the above result, because I cannot use the accelerated xorg-fglrx driver for my ATI Graphics Card and I cannot use my wireless Intel card ipw3945 driver. And the Ubuntu restricted-manager is not working. PLEASE can someone help me to compile a Ubuntu kernel in the correct way, so that I can use the whole hardware ?

I have done a - I think really ugly hack - to get the restricted-manager working :

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|cp /boot/config-2.6.20-16-generic /lib/modules/2.6.20-generic/.config}}
{{cmdroot|gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -16-generic".
Then I did compile the kernel again with:

{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I moved my modules with :

{{cmdroot|mv /lib/modules/2.6.20-16-generic /lib/modules/2.6.20-16-generic.orginal}}

And installed the kernel with:

{{cmdroot|dpkg -i linux-image-2.6.20-16-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers as described above.
Finally I copied the ipw3945.ucode with

{{cmdroot|cp /lib/firmware/2.6.22-7-generic/ipw3945.ucode /lib/firmware/2.6.20-16-generic/ipw3945.ucode}}

My wireless-card is working now !
My ATI Card cannot be configured with restricted-manager!

{{HELP|Please can someone who is conform in compiling Ubuntu kernels and restricted modules help me to do it in the correct way ! And can someone recheck the things described above, because I am not sure about all things that I have written here.
}}

After some days Ubuntu updated the kernel to version 2.6.22-9-generic, so I need to do the steps described above again, with "EXTRAVERSION = -9-generic". But now my wireless card and my grapics card did not work. The restricted-manager crashes when I start it.
So I downloaded the packages ipw3945-1.2.1.tgz and ati-driver-installer-8.39.4-x86.x86_64.run.

First I extracted and installed the Intel Pro Wireless Package:

{{cmduser|tar xzvf ipw3945-1.2.1.tgz}}
{{cmduser|cd ipw3945-1.2.1}}
{{cmduser|make}}
{{cmduser|sudo make install}}

After this I could do :

{{cmduser|sudo modprobe ipw3945}}

The module was loaded, and i was able to use my wireless card now.

For my Radeon Mobility X1400 I did the following steps:

{{cmduser|sudo apt get update}}
{{cmduser|sudo apt-get install module-assistant build-essential fakeroot dh-make debhelper debconf libstdc++5}}

Created a Debian Package with:

{{cmduser|sudo bash ati-driver-installer-8.39.4-x86.x86_64.run --buildpkg Ubuntu/gutsy}}

And blacklisted the old fglrx module with:

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

I added "fglrx" to the line with "DISABLED_MODULES". Then I installed the created Debian Packages with:

{{cmduser|sudo dpkg -i xorg-driver-fglrx_8.39.4-1_i386.deb fglrx-kernel-source_8.39.4-1_i386.deb fglrx-amdcccle_8.39.4-1_i386.deb}}

Then I compiled the kernel Modules:

{{cmduser|sudo module-assistant prepare}}
{{cmduser|sudo module-assistant update}}
{{cmduser|sudo module-assistant build fglrx}}
{{cmduser|sudo module-assistant install fglrx}}
{{cmduser|sudo depmod -a}}

The helpful informations for this was found at http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide.

After this steps my wifi-card and my graphics-card was working and restricted-manager was not crashing when I tried to start it.

== The Browser Buttons ==

I wanted to use the Browser Forward & Backward Buttons within Firefox. After the upgrade my Firefox had version 2.0.0.4

I did :

{{cmduser| sudo gedit ~/.Xmodmap}}

and added the following lines :

keycode 234 = F19

keycode 233 = F20

I saved and closed the file. HINT: You have to re-login to Gnome to get the .Xmodmap file active.

Then I did the things described in [http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work#Firefox How to get special keys to work].

For the Windows Key I added "keycode 115 = F13" to my .Xmodmap File, then I klicked on "System - Einstellungen - Tastenkombinationen"
sorry I don't know how it is called in English. And changed the Entry "Das Panelmenü anzeigen" to F13

== The Brightness Buttons ==

When I wanted to control the brightness, I was not able to change it with {{key|Fn}}{{key|End}}.

So I did the Workaround menitioned here [http://thinkwiki.org/wiki/Problem_with_LCD_brightness_buttons#Workaround for Fedora Core 6 Users].
After this I was able to change the brightness with {{key|Fn}}{{key|Home}} and {{key|Fn}}{{key|End}}, but I don't have the OSD anymore.

== The Fingerprint Reader ==

Do the steps which are described in [http://www.thinkwiki.org/wiki/Installing_Ubuntu_6.10_%28Edgy_Eft%29_on_a_ThinkPad_T60#The_Fingerprint_Reader Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60] until you get to the Point where Keithvassallo says:
"Phew. Now, to make applications actually use the fingerprint reader."

I have done the following things instead of his version:

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

Change the file as following:

<pre>
#%PAM-1.0
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
auth requisite pam_nologin.so
auth required pam_env.so
@include common-auth
@include common-account
session required pam_limits.so
@include common-session
@include common-password
</pre>

and:

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

Change this file as following:

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

With this changes you have the advantage, that you are now able to login to Gnome or KDE whitout entering your password. But if you cancel the "Fingerprint Login", you are still able to login whit your username/password combination.

After I was able to login to my desktop I was unsatisfied, because my Computer still wants to get passwords i.e. when I tried to open Synaptic or when I do any sudo actions.

So I tried to figure out how this sudo thing works. I did the following change to /etc/pam.d/sudo with:

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

<pre>
#%PAM-1.0

auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/ :0
password sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam :0
auth required pam_unix.so nillock_secure
@include common-account

</pre>

With this change I was able to open System Administration tasks with my fingerprint, but the ugly thing is, that you get no information to swipe your finger over the reader when you have switched to a console session with {{Key|Ctrl}}+{{Key|Alt}}+{{Key|F1}}. The fingerprint scanner software will appear at your running X session.

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-08-06T11:45:12Z

Dirk: /* The hdapsd - Deamon (next try) */

== My Thinkpad ==
<pre>
Lenovo Thinkpad R60 9461 HRG
Intel Core2Duo (Merom) 1.83 CPU
120 GB SATA Hitachi HTS54161 Harddisk
2 GB RAM
ATI Mobility X1400
</pre>

Originally equipped with a preinstalled MS Windows Vista Business. So the Harddisk was parted into two Partitions.

1. The Rescue & Recovery Partition

2. The preinstalled Windows Vista Partition

And as the parcel with my new Thinkpad arrived I was surprized, that there was a Windows Vista DVD (only 32 Bit Version) with it.
So I tried Vista - but I was a little bit shocked by it's performance. I never thought that a new computer could take so much time to boot up completely.

I decided to do a clean install of Vista, but I want to have Windows XP and Ubuntu Feisty on the Harddisk too.

== New Installation ==

I wanted to use all Space of the Harddisk, so I decided to kill the Rescue & and Recovery Partition, but to have the chance to go back to the factory default state I ordered Recovery DVD's at the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4HWSE3#Lenovo Support Call Center for Germany].
They shipped the 3 DVD's to me - free of charge - but I think it's only free if your Thinkpad is still in the warranty. I don't know exactly.

Then I created 2 Partitions on my Harddisk, 64 GB for Vista, 20 GB for XP, so 29 GB left free for Linux.

I installed Vista and XP and all the Thinkpad Stuff for each system.

When this was finished I took a Ubuntu Feisty Fawn installation CD and boot my Notebook with it. I created a 4 GB linux-swap partition and a 25 GB root / partition.

Because I want to boot my Ubuntu with the Windows Vista Boot Loader, I decided to install Grub to /dev/sda4 which is my Linux root partition.

The installation of Ubuntu Feisty Fawn works fine, NO PROBLEMS.

NOW I want to boot Linux from the Vista Bootloader, because I don't want to wait for two Bootscreens, and I wan't to have the chance to access the Repair Console of Windows Vista.

First I have to copy the Bootsector of my Linux Partition with:

<pre>
sudo dd if=/dev/sda4 of=/tmp/bootsect.lin bs=512 count=1
</pre>

Copy the bootsect.lin file to a USB-Stick or a writable partition which you can access from Windows Vista.

Now boot Windows Vista and copy the file bootsect.lin to your Systemdrive. In an Command Window with Administrator privileges type:

<pre>
copy bootsect.lin %SYSTEMDRIVE%\

bcdedit /create /d “Ubuntu” /application BOOTSECTOR
</pre>

You will receice an ID like this {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} from bcdedit. This is a uniqe identifier for your new Boot Entry in the Vista Bootloader. Now you will have to manipulate the entry with the following commands:

<pre>
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} device boot
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} PATH \bootsect.lin
bcdedit /displayorder {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} /addlast
bcdedit /timeout 10
</pre>

Then I booted my Ubuntu an did :

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

In this file I canged the entry the following entries:

<pre>
timeout 2
hiddenmenu
</pre>

So the computer starts up with the Windows Vista bootloader and gives me the option to start Windows XP, Windows Vista, Ubuntu and I have the option to do the repair tasks with the {{key|F8}} button on Vista if something fails. If I choose to boot Ubuntu I have the option to press the {{key|ESC}} key within the two seconds delay of the hidden Grub Menu. I.E. to boot another Linux Kernel.

== The tp_smapi modules ==

I did it under Feisty and, after the Upgrade under Gutsy, like described here : [http://www.thinkwiki.org/wiki/Tp_smapi#Installation TP SMAPI] in the Section "Installation on Ubuntu/Debian"
It worked, hdaps-gl and hdaps-pivot shows me now the movements of my Thinkpad. Like you can see here:

[[Image:Hdaps-pivot.png]]

[[Image:Hdaps-gl.png]]

== The Upgrade to Gutsy Gibbon ==

NO PROBLEMS. So why should I upgrade ?

OK I really wanted to get hdapsd (Harddisk Active Protection) to work. I tried a lot of things with Feisty, but I didn't get it going. And after a lot of seach through the Internet I found out that Gutsy Gibbon, the next Release of Ubuntu should have the Package for hdapsd on board.
SO I decided to upgrade to Gutsy - with the knowledge that it is still in Beta Stadium.

Upgrading Ubuntu is really simple, you only have to do the following steps:

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

Search all feisty entries and change them to gutsy. Save and Close the file.

Do:

{{cmduser| sudo apt-get update}}
{{cmduser| sudo apt-get upgrade}}

Go and drink a cup of Tea or Coffee. When you are back you have a message, that you should reboot your System, to get all packages active. So do it.

After the reboot I installed the hdapsd package and I tried to activate the Harddisk Protection with:

{{cmduser| sudo hdapsd -d sda -s 14 -a -v}}

But I still get the message "open(protect_file): No such file or directory". ---- The Same Message that I get in Feisty before I did the Upgrade. So I banged my head on the table and noticed that I'm not tough enough to get this thing working. Maybe someone else.

I decided to get the other things to work.

UPDATE: After some days I tried to get hdapsd to work, again !

== The hdapsd - Deamon (IBM Active Disk Protection) ==

Because I never had compiled or patched a kernel under Ubuntu I had to find out how this works ! After a lot of search in the Internet, the Ubuntu Help and at Thinkwiki.org I found the (hopefully) correct way to do it.

The best information I found was this :
[http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.04_on_a_ThinkPad_T43#Active_Protection_System_.28acceleration_monitor.29|Installing Ubuntu 7.04 on a ThinkPad T43] in section "Disk protection"

Here is what I did to get it to work:

1. Make sure that you have the required packages, with:

{{cmduser|sudo apt-get install build-essential fakeroot kernel-package libncurses5-dev wget bzip2 linux-source}}

2. Get the correct kernel patch for your running kernel from here : [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch_.28apply_using_.27patch_-p1_-l_.3C_hdaps_xx.patch.27.29| HDAPS] section "8.1.1 Kernel patch (apply using 'patch -p1 -l < hdaps_xx.patch')"

After all my experiences I was not sure that there was a patch available for my Gutsy-kernel (2.6.22-7-generic), but I still had my old kernel on the disk. So I booted up the old one (2.6.20-16-generic). Check the running kernel with:

{{cmduser|uname -r}}

You should see something like: 2.6.20-7-generic

Now change to /usr/src and look that the sources for the running kernel are there with:

{{cmduser|cd /usr/src}}
{{cmduser|ls -d linux-source*}}

You should see a file with the name "linux-source-2.6.20.tar.bz2" wich includes the packed kernel sources. You have to extract it, so do:

{{cmduser|sudo su}}
{{cmdroot|tar xvfj linux-source-2.6.20.tar.bz2}}

Now you have the kernel sources in the /usr/src/linux-source-2.6.20 directory. Take a look if there is a link from /usr/src/linux to an other kernel source directory (It's maybe there if you tried to compile a kernel some time before).

{{cmdroot|ls -l linux}}

If you see that linux is linked to an other source than your running kernel remove the link and create a new one with:

{{cmdroot|rm -r linux}}
{{cmdroot|ln -s /usr/src/linux-source-2.6.20 linux}}

Change to the source directory and patch the kernel with this:

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|patch -p1 -l < /home/dirk/993-001.bin}}

The file "993-001.bin" is the kernel patch for the 2.6.20 and 2.6.21 kernels, I downloaded it here : [http://article.gmane.org/gmane.linux.drivers.hdaps.devel/993]

After the patchwork I did this :

{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --append-to-version=.hdapscustom kernel_image --initrd binary

This would take its time, so go and clean up your house ;-)
{{HELP|I think the last command (with --append-to-version was an error ! I need help from an specialist in kernel compiling. Please read ahead at the next section "The hdapsd - Deamon (next try)". }}
After your house is clean you can do :

{{cmdroot|cd /usr/src}}
{{cmdroot|ls -l linux*.deb}}

You should see some newly builded Debian Pakage files. Install them with:

{{cmdroot|dpkg -i linux-headers-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-doc-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-image-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-manual-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-source-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}

After the installation you should reboot your computer, when Grub comes up make sure that you select your newly builded kernel.
Check it with:

{{cmduser|uname -r}}

You should see this "2.6.20.3-ubuntu1.hdapscustom". But now you have the Problem, that you have to recompile the tp_smapi driver.

{{cmduser|cd tp_smapi-0.31}}
$ sudo make install HDAPS=1
{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdpas}}

After :

<pre>
$ dmesg | grep hdaps
</pre>

You should see something like this:

[ 893.752000] hdaps: initial mode latch is 0x05
[ 893.752000] hdaps: setting ec_rate=250, filter_order=2
[ 893.752000] hdaps: fake_data_mode set to 0
[ 893.756000] hdaps: device successfully initialized.
[ 893.756000] input: hdaps as /class/input/input10
[ 893.756000] hdaps: driver successfully loaded.

Now we are ready to try out the hdapsd Deamon which is included in the Gutsy repositories, if you are using Feisty you have to compile it yourself like described here: [http://www.thinkwiki.org/wiki/How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS].

{{cmdroot|sudo hdapsd -d sda -s 12 -a -v}}

Should show this:

[[Image:hdapsd.png]]

If you load it with :

{{cmdroot|sudo hdapsd -d sda -s 12 -a}}

You get nothing until you move your Thinkpad, then you see:

Fri Jul 13 12:30:42 2007: parking
Fri Jul 13 12:30:43 2007: un-parking
Fri Jul 13 12:30:44 2007: parking
Fri Jul 13 12:30:45 2007: un-parking

Now, after I have a working hdaps-deamon I want it to be started at boot time. Because I have upgraded to Gutsy and installed the hdapsd - Package I have a script called /etc/default/hdapsd. Here I have to change some things. HINT: Remember that you still need the /etc/init.d/hdapsd file if you try this on Feisty and maybe you have to do:

{{cmduser|sudo update-rc.d hdapsd defaults}}

to create the init links for the hdapsd init script. My links was already there. My /etc/default/hdapsd script now looks like this:

<pre>
# hdapsd default file

# start hdapsd at boottime?
START="yes"

# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
DISK="sda"

# sensitivity
SENSITIVITY=12

# other options to pass to hdapsd.
# the -d $DISK, -s $SENSITIVITY, -b and -p $PIDFILE options are always passed.
OPTIONS="-a"

</pre>

Now I could use the gnome-hdaps-applet with the following comands:

{{cmduser|mkdir gnome-hdaps-applet}}
{{cmduser|cd gnome-hdaps-applet}}
{{cmduser|wget http://www.zen24593.zen.co.uk/hdaps/gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|tar -xzf gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|sudo apt-get install libpanel-applet2-dev}}
{{cmduser|gcc $(pkg-config --cflags --libs libpanelapplet-2.0) -o gnome-hdaps-applet gnome-hdaps-applet.c}}
{{cmduser|sudo cp gnome-hdaps-applet /usr/bin/}}
{{cmduser|sudo mkdir /usr/share/pixmaps/gnome-hdaps-applet/}}
{{cmduser|sudo cp *.png /usr/share/pixmaps/gnome-hdaps-applet/}}
$ sudo cp GNOME_HDAPS_StatusApplet.server /usr/lib/bonobo/servers/

Now after a restart of the Gnome Session I could find a "HDAPS Status" applet in the "Add to Panel" dialog. I added it, and when I move the Thinkpad it shows me the "Pause" [[Image:Hdaps-paused-small.png]] Symbol, otherwise it shows "Play" [[Image:Hdaps-running-small.png]].

So far so good !!! After I got this running I tried the same steps with the normal Gutsy Kernel (2.6.22-7-generic) on the same way, and it worked ! To my surprise with the same kernel patch.

The only Problem that I now have is that I cannot use restricted modules with my new kernels. Now I have to figure out how to compile restricted modules agains selfmade kernels.

{{HELP| }}

== The hdapsd - Deamon (next try) ==

I am not satisfied with the above result, because I cannot use the accelerated xorg-fglrx driver for my ATI Graphics Card and I cannot use my wireless Intel card ipw3945 driver. And the Ubuntu restricted-manager is not working. PLEASE can someone help me to compile a Ubuntu kernel in the correct way, so that I can use the whole hardware ?

I have done a - I think really ugly hack - to get the restricted-manager working :

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|cp /boot/config-2.6.20-16-generic /lib/modules/2.6.20-generic/.config}}
{{cmdroot|gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -16-generic".
Then I did compile the kernel again with:

{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I moved my modules with :

{{cmdroot|mv /lib/modules/2.6.20-16-generic /lib/modules/2.6.20-16-generic.orginal}}

And installed the kernel with:

{{cmdroot|dpkg -i linux-image-2.6.20-16-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers as described above.
Finally I copied the ipw3945.ucode with

{{cmdroot|cp /lib/firmware/2.6.22-7-generic/ipw3945.ucode /lib/firmware/2.6.20-16-generic/ipw3945.ucode}}

My wireless-card is working now !
My ATI Card cannot be configured with restricted-manager!

{{HELP|Please can someone who is conform in compiling Ubuntu kernels and restricted modules help me to do it in the correct way ! And can someone recheck the things described above, because I am not sure about all things that I have written here.
}}

After some days Ubuntu updated the kernel to version 2.6.22-9-generic, so I need to do the steps described above again, with "EXTRAVERSION = -9-generic". But now my wireless card and my grapics card did not work. The restricted-manager crashes when I start it.
So I downloaded the packages ipw3945-1.2.1.tgz and ati-driver-installer-8.39.4-x86.x86_64.run.

First I extracted and installed the Intel Pro Wireless Package:

{{cmduser|tar xzvf ipw3945-1.2.1.tgz}}
{{cmduser|cd ipw3945-1.2.1}}
{{cmduser|make}}
{{cmduser|sudo make install}}

After this I could do :

{{cmduser|sudo modprobe ipw3945}}

The module was loaded, and i was able to use my wireless card now.

For my Radeon Mobility X1400 I did the following steps:

{{cmduser|sudo apt get update}}
{{cmduser|sudo apt-get install module-assistant build-essential fakeroot dh-make debhelper debconf libstdc++5}}

Created a Debian Package with:

{{cmduser|sudo bash ati-driver-installer-8.39.4-x86.x86_64.run --buildpkg Ubuntu/gutsy}}

And blacklisted the old fglrx module with:

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

I added "fglrx" to the line with "DISABLED_MODULES". Then I installed the created Debian Packages with:

{{cmduser|sudo dpkg -i xorg-driver-fglrx_8.39.4-1_i386.deb fglrx-kernel-source_8.39.4-1_i386.deb fglrx-amdcccle_8.39.4-1_i386.deb}}

Then I compiled the kernel Modules:

{{cmduser|sudo module-assistant prepare}}
{{cmduser|sudo module-assistant update}}
{{cmduser|sudo module-assistant build fglrx}}
{{cmduser|sudo module-assistant install fglrx}}
{{cmduser|sudo depmod -a}}

The helpful informations for this was found at http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide.

After this steps my wifi-card and my graphics-card was working and restricted-manager was not crashing when I tried to start it.

== The Browser Buttons ==

I wanted to use the Browser Forward & Backward Buttons within Firefox. After the upgrade my Firefox had version 2.0.0.4

I did :

{{cmduser| sudo gedit ~/.Xmodmap}}

and added the following lines :

keycode 234 = F19

keycode 233 = F20

I saved and closed the file. HINT: You have to re-login to Gnome to get the .Xmodmap file active.

Then I did the things described in [http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work#Firefox How to get special keys to work].

For the Windows Key I added "keycode 115 = F13" to my .Xmodmap File, then I klicked on "System - Einstellungen - Tastenkombinationen"
sorry I don't know how it is called in English. And changed the Entry "Das Panelmenü anzeigen" to F13

== The Brightness Buttons ==

When I wanted to control the brightness, I was not able to change it with {{key|Fn}}{{key|End}}.

So I did the Workaround menitioned here [http://thinkwiki.org/wiki/Problem_with_LCD_brightness_buttons#Workaround for Fedora Core 6 Users].
After this I was able to change the brightness with {{key|Fn}}{{key|Home}} and {{key|Fn}}{{key|End}}, but I don't have the OSD anymore.

== The Fingerprint Reader ==

Do the steps which are described in [http://www.thinkwiki.org/wiki/Installing_Ubuntu_6.10_%28Edgy_Eft%29_on_a_ThinkPad_T60#The_Fingerprint_Reader Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60] until you get to the Point where Keithvassallo says:
"Phew. Now, to make applications actually use the fingerprint reader."

I have done the following things instead of his version:

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

Change the file as following:

<pre>
#%PAM-1.0
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
auth requisite pam_nologin.so
auth required pam_env.so
@include common-auth
@include common-account
session required pam_limits.so
@include common-session
@include common-password
</pre>

and:

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

Change this file as following:

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

With this changes you have the advantage, that you are now able to login to Gnome or KDE whitout entering your password. But if you cancel the "Fingerprint Login", you are still able to login whit your username/password combination.

After I was able to login to my desktop I was unsatisfied, because my Computer still wants to get passwords i.e. when I tried to open Synaptic or when I do any sudo actions.

So I tried to figure out how this sudo thing works. I did the following change to /etc/pam.d/sudo with:

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

<pre>
#%PAM-1.0

auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/ :0
password sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam :0
auth required pam_unix.so nillock_secure
@include common-account

</pre>

With this change I was able to open System Administration tasks with my fingerprint, but the ugly thing is, that you get no information to swipe your finger over the reader when you have switched to a console session with {{Key|Ctrl}}+{{Key|Alt}}+{{Key|F1}}. The fingerprint scanner software will appear at your running X session.

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-07-18T12:06:19Z

Dirk: /* The hdapsd - Deamon (next try) */

== My Thinkpad ==
<pre>
Lenovo Thinkpad R60 9461 HRG
Intel Core2Duo (Merom) 1.83 CPU
120 GB SATA Hitachi HTS54161 Harddisk
2 GB RAM
ATI Mobility X1400
</pre>

Originally equipped with a preinstalled MS Windows Vista Business. So the Harddisk was parted into two Partitions.

1. The Rescue & Recovery Partition

2. The preinstalled Windows Vista Partition

And as the parcel with my new Thinkpad arrived I was surprized, that there was a Windows Vista DVD (only 32 Bit Version) with it.
So I tried Vista - but I was a little bit shocked by it's performance. I never thought that a new computer could take so much time to boot up completely.

I decided to do a clean install of Vista, but I want to have Windows XP and Ubuntu Feisty on the Harddisk too.

== New Installation ==

I wanted to use all Space of the Harddisk, so I decided to kill the Rescue & and Recovery Partition, but to have the chance to go back to the factory default state I ordered Recovery DVD's at the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4HWSE3#Lenovo Support Call Center for Germany].
They shipped the 3 DVD's to me - free of charge - but I think it's only free if your Thinkpad is still in the warranty. I don't know exactly.

Then I created 2 Partitions on my Harddisk, 64 GB for Vista, 20 GB for XP, so 29 GB left free for Linux.

I installed Vista and XP and all the Thinkpad Stuff for each system.

When this was finished I took a Ubuntu Feisty Fawn installation CD and boot my Notebook with it. I created a 4 GB linux-swap partition and a 25 GB root / partition.

Because I want to boot my Ubuntu with the Windows Vista Boot Loader, I decided to install Grub to /dev/sda4 which is my Linux root partition.

The installation of Ubuntu Feisty Fawn works fine, NO PROBLEMS.

NOW I want to boot Linux from the Vista Bootloader, because I don't want to wait for two Bootscreens, and I wan't to have the chance to access the Repair Console of Windows Vista.

First I have to copy the Bootsector of my Linux Partition with:

<pre>
sudo dd if=/dev/sda4 of=/tmp/bootsect.lin bs=512 count=1
</pre>

Copy the bootsect.lin file to a USB-Stick or a writable partition which you can access from Windows Vista.

Now boot Windows Vista and copy the file bootsect.lin to your Systemdrive. In an Command Window with Administrator privileges type:

<pre>
copy bootsect.lin %SYSTEMDRIVE%\

bcdedit /create /d “Ubuntu” /application BOOTSECTOR
</pre>

You will receice an ID like this {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} from bcdedit. This is a uniqe identifier for your new Boot Entry in the Vista Bootloader. Now you will have to manipulate the entry with the following commands:

<pre>
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} device boot
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} PATH \bootsect.lin
bcdedit /displayorder {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} /addlast
bcdedit /timeout 10
</pre>

Then I booted my Ubuntu an did :

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

In this file I canged the entry the following entries:

<pre>
timeout 2
hiddenmenu
</pre>

So the computer starts up with the Windows Vista bootloader and gives me the option to start Windows XP, Windows Vista, Ubuntu and I have the option to do the repair tasks with the {{key|F8}} button on Vista if something fails. If I choose to boot Ubuntu I have the option to press the {{key|ESC}} key within the two seconds delay of the hidden Grub Menu. I.E. to boot another Linux Kernel.

== The tp_smapi modules ==

I did it under Feisty and, after the Upgrade under Gutsy, like described here : [http://www.thinkwiki.org/wiki/Tp_smapi#Installation TP SMAPI] in the Section "Installation on Ubuntu/Debian"
It worked, hdaps-gl and hdaps-pivot shows me now the movements of my Thinkpad. Like you can see here:

[[Image:Hdaps-pivot.png]]

[[Image:Hdaps-gl.png]]

== The Upgrade to Gutsy Gibbon ==

NO PROBLEMS. So why should I upgrade ?

OK I really wanted to get hdapsd (Harddisk Active Protection) to work. I tried a lot of things with Feisty, but I didn't get it going. And after a lot of seach through the Internet I found out that Gutsy Gibbon, the next Release of Ubuntu should have the Package for hdapsd on board.
SO I decided to upgrade to Gutsy - with the knowledge that it is still in Beta Stadium.

Upgrading Ubuntu is really simple, you only have to do the following steps:

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

Search all feisty entries and change them to gutsy. Save and Close the file.

Do:

{{cmduser| sudo apt-get update}}
{{cmduser| sudo apt-get upgrade}}

Go and drink a cup of Tea or Coffee. When you are back you have a message, that you should reboot your System, to get all packages active. So do it.

After the reboot I installed the hdapsd package and I tried to activate the Harddisk Protection with:

{{cmduser| sudo hdapsd -d sda -s 14 -a -v}}

But I still get the message "open(protect_file): No such file or directory". ---- The Same Message that I get in Feisty before I did the Upgrade. So I banged my head on the table and noticed that I'm not tough enough to get this thing working. Maybe someone else.

I decided to get the other things to work.

UPDATE: After some days I tried to get hdapsd to work, again !

== The hdapsd - Deamon (IBM Active Disk Protection) ==

Because I never had compiled or patched a kernel under Ubuntu I had to find out how this works ! After a lot of search in the Internet, the Ubuntu Help and at Thinkwiki.org I found the (hopefully) correct way to do it.

The best information I found was this :
[http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.04_on_a_ThinkPad_T43#Active_Protection_System_.28acceleration_monitor.29|Installing Ubuntu 7.04 on a ThinkPad T43] in section "Disk protection"

Here is what I did to get it to work:

1. Make sure that you have the required packages, with:

{{cmduser|sudo apt-get install build-essential fakeroot kernel-package libncurses5-dev wget bzip2 linux-source}}

2. Get the correct kernel patch for your running kernel from here : [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch_.28apply_using_.27patch_-p1_-l_.3C_hdaps_xx.patch.27.29| HDAPS] section "8.1.1 Kernel patch (apply using 'patch -p1 -l < hdaps_xx.patch')"

After all my experiences I was not sure that there was a patch available for my Gutsy-kernel (2.6.22-7-generic), but I still had my old kernel on the disk. So I booted up the old one (2.6.20-16-generic). Check the running kernel with:

{{cmduser|uname -r}}

You should see something like: 2.6.20-7-generic

Now change to /usr/src and look that the sources for the running kernel are there with:

{{cmduser|cd /usr/src}}
{{cmduser|ls -d linux-source*}}

You should see a file with the name "linux-source-2.6.20.tar.bz2" wich includes the packed kernel sources. You have to extract it, so do:

{{cmduser|sudo su}}
{{cmdroot|tar xvfj linux-source-2.6.20.tar.bz2}}

Now you have the kernel sources in the /usr/src/linux-source-2.6.20 directory. Take a look if there is a link from /usr/src/linux to an other kernel source directory (It's maybe there if you tried to compile a kernel some time before).

{{cmdroot|ls -l linux}}

If you see that linux is linked to an other source than your running kernel remove the link and create a new one with:

{{cmdroot|rm -r linux}}
{{cmdroot|ln -s /usr/src/linux-source-2.6.20 linux}}

Change to the source directory and patch the kernel with this:

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|patch -p1 -l < /home/dirk/993-001.bin}}

The file "993-001.bin" is the kernel patch for the 2.6.20 and 2.6.21 kernels, I downloaded it here : [http://article.gmane.org/gmane.linux.drivers.hdaps.devel/993]

After the patchwork I did this :

{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --append-to-version=.hdapscustom kernel_image --initrd binary

This would take its time, so go and clean up your house ;-)
{{HELP|I think the last command (with --append-to-version was an error ! I need help from an specialist in kernel compiling. Please read ahead at the next section "The hdapsd - Deamon (next try)". }}
After your house is clean you can do :

{{cmdroot|cd /usr/src}}
{{cmdroot|ls -l linux*.deb}}

You should see some newly builded Debian Pakage files. Install them with:

{{cmdroot|dpkg -i linux-headers-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-doc-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-image-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-manual-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-source-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}

After the installation you should reboot your computer, when Grub comes up make sure that you select your newly builded kernel.
Check it with:

{{cmduser|uname -r}}

You should see this "2.6.20.3-ubuntu1.hdapscustom". But now you have the Problem, that you have to recompile the tp_smapi driver.

{{cmduser|cd tp_smapi-0.31}}
$ sudo make install HDAPS=1
{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdpas}}

After :

<pre>
$ dmesg | grep hdaps
</pre>

You should see something like this:

[ 893.752000] hdaps: initial mode latch is 0x05
[ 893.752000] hdaps: setting ec_rate=250, filter_order=2
[ 893.752000] hdaps: fake_data_mode set to 0
[ 893.756000] hdaps: device successfully initialized.
[ 893.756000] input: hdaps as /class/input/input10
[ 893.756000] hdaps: driver successfully loaded.

Now we are ready to try out the hdapsd Deamon which is included in the Gutsy repositories, if you are using Feisty you have to compile it yourself like described here: [http://www.thinkwiki.org/wiki/How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS].

{{cmdroot|sudo hdapsd -d sda -s 12 -a -v}}

Should show this:

[[Image:hdapsd.png]]

If you load it with :

{{cmdroot|sudo hdapsd -d sda -s 12 -a}}

You get nothing until you move your Thinkpad, then you see:

Fri Jul 13 12:30:42 2007: parking
Fri Jul 13 12:30:43 2007: un-parking
Fri Jul 13 12:30:44 2007: parking
Fri Jul 13 12:30:45 2007: un-parking

Now, after I have a working hdaps-deamon I want it to be started at boot time. Because I have upgraded to Gutsy and installed the hdapsd - Package I have a script called /etc/default/hdapsd. Here I have to change some things. HINT: Remember that you still need the /etc/init.d/hdapsd file if you try this on Feisty and maybe you have to do:

{{cmduser|sudo update-rc.d hdapsd defaults}}

to create the init links for the hdapsd init script. My links was already there. My /etc/default/hdapsd script now looks like this:

<pre>
# hdapsd default file

# start hdapsd at boottime?
START="yes"

# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
DISK="sda"

# sensitivity
SENSITIVITY=12

# other options to pass to hdapsd.
# the -d $DISK, -s $SENSITIVITY, -b and -p $PIDFILE options are always passed.
OPTIONS="-a"

</pre>

Now I could use the gnome-hdaps-applet with the following comands:

{{cmduser|mkdir gnome-hdaps-applet}}
{{cmduser|cd gnome-hdaps-applet}}
{{cmduser|wget http://www.zen24593.zen.co.uk/hdaps/gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|tar -xzf gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|sudo apt-get install libpanel-applet2-dev}}
{{cmduser|gcc $(pkg-config --cflags --libs libpanelapplet-2.0) -o gnome-hdaps-applet gnome-hdaps-applet.c}}
{{cmduser|sudo cp gnome-hdaps-applet /usr/bin/}}
{{cmduser|sudo mkdir /usr/share/pixmaps/gnome-hdaps-applet/}}
{{cmduser|sudo cp *.png /usr/share/pixmaps/gnome-hdaps-applet/}}
$ sudo cp GNOME_HDAPS_StatusApplet.server /usr/lib/bonobo/servers/

Now after a restart of the Gnome Session I could find a "HDAPS Status" applet in the "Add to Panel" dialog. I added it, and when I move the Thinkpad it shows me the "Pause" [[Image:Hdaps-paused-small.png]] Symbol, otherwise it shows "Play" [[Image:Hdaps-running-small.png]].

So far so good !!! After I got this running I tried the same steps with the normal Gutsy Kernel (2.6.22-7-generic) on the same way, and it worked ! To my surprise with the same kernel patch.

The only Problem that I now have is that I cannot use restricted modules with my new kernels. Now I have to figure out how to compile restricted modules agains selfmade kernels.

{{HELP| }}

== The hdapsd - Deamon (next try) ==

I am not satisfied with the above result, because I cannot use the accelerated xorg-fglrx driver for my ATI Graphics Card and I cannot use my wireless Intel card ipw3945 driver. And the Ubuntu restricted-manager is not working. PLEASE can someone help me to compile a Ubuntu kernel in the correct way, so that I can use the whole hardware ?

I have done a - I think really ugly hack - to get the restricted-manager working :

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|cp /boot/config-2.6.20-16-generic /lib/modules/2.6.20-generic/.config}}
{{cmdroot|gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -16-generic".
Then I did compile the kernel again with:

{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I moved my modules with :

{{cmdroot|mv /lib/modules/2.6.20-16-generic /lib/modules/2.6.20-16-generic.orginal}}

And installed the kernel with:

{{cmdroot|dpkg -i linux-image-2.6.20-16-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers as described above.
Finally I copied the ipw3945.ucode with

{{cmdroot|cp /lib/firmware/2.6.22-7-generic/ipw3945.ucode /lib/firmware/2.6.20-16-generic/ipw3945.ucode}}

My wireless-card is working now !
My ATI Card cannot be configured with restricted-manager!

{{HELP|Please can someone who is conform in compiling Ubuntu kernels and restricted modules help me to do it in the correct way ! And can someone recheck the things described above, because I am not sure about all things that I have written here.
}}

== The Browser Buttons ==

I wanted to use the Browser Forward & Backward Buttons within Firefox. After the upgrade my Firefox had version 2.0.0.4

I did :

{{cmduser| sudo gedit ~/.Xmodmap}}

and added the following lines :

keycode 234 = F19

keycode 233 = F20

I saved and closed the file. HINT: You have to re-login to Gnome to get the .Xmodmap file active.

Then I did the things described in [http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work#Firefox How to get special keys to work].

For the Windows Key I added "keycode 115 = F13" to my .Xmodmap File, then I klicked on "System - Einstellungen - Tastenkombinationen"
sorry I don't know how it is called in English. And changed the Entry "Das Panelmenü anzeigen" to F13

== The Brightness Buttons ==

When I wanted to control the brightness, I was not able to change it with {{key|Fn}}{{key|End}}.

So I did the Workaround menitioned here [http://thinkwiki.org/wiki/Problem_with_LCD_brightness_buttons#Workaround for Fedora Core 6 Users].
After this I was able to change the brightness with {{key|Fn}}{{key|Home}} and {{key|Fn}}{{key|End}}, but I don't have the OSD anymore.

== The Fingerprint Reader ==

Do the steps which are described in [http://www.thinkwiki.org/wiki/Installing_Ubuntu_6.10_%28Edgy_Eft%29_on_a_ThinkPad_T60#The_Fingerprint_Reader Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60] until you get to the Point where Keithvassallo says:
"Phew. Now, to make applications actually use the fingerprint reader."

I have done the following things instead of his version:

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

Change the file as following:

<pre>
#%PAM-1.0
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
auth requisite pam_nologin.so
auth required pam_env.so
@include common-auth
@include common-account
session required pam_limits.so
@include common-session
@include common-password
</pre>

and:

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

Change this file as following:

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

With this changes you have the advantage, that you are now able to login to Gnome or KDE whitout entering your password. But if you cancel the "Fingerprint Login", you are still able to login whit your username/password combination.

After I was able to login to my desktop I was unsatisfied, because my Computer still wants to get passwords i.e. when I tried to open Synaptic or when I do any sudo actions.

So I tried to figure out how this sudo thing works. I did the following change to /etc/pam.d/sudo with:

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

<pre>
#%PAM-1.0

auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/ :0
password sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam :0
auth required pam_unix.so nillock_secure
@include common-account

</pre>

With this change I was able to open System Administration tasks with my fingerprint, but the ugly thing is, that you get no information to swipe your finger over the reader when you have switched to a console session with {{Key|Ctrl}}+{{Key|Alt}}+{{Key|F1}}. The fingerprint scanner software will appear at your running X session.

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-07-16T13:40:30Z

Dirk: /* The hdapsd - Deamon (next try) */

== My Thinkpad ==
<pre>
Lenovo Thinkpad R60 9461 HRG
Intel Core2Duo (Merom) 1.83 CPU
120 GB SATA Hitachi HTS54161 Harddisk
2 GB RAM
ATI Mobility X1400
</pre>

Originally equipped with a preinstalled MS Windows Vista Business. So the Harddisk was parted into two Partitions.

1. The Rescue & Recovery Partition

2. The preinstalled Windows Vista Partition

And as the parcel with my new Thinkpad arrived I was surprized, that there was a Windows Vista DVD (only 32 Bit Version) with it.
So I tried Vista - but I was a little bit shocked by it's performance. I never thought that a new computer could take so much time to boot up completely.

I decided to do a clean install of Vista, but I want to have Windows XP and Ubuntu Feisty on the Harddisk too.

== New Installation ==

I wanted to use all Space of the Harddisk, so I decided to kill the Rescue & and Recovery Partition, but to have the chance to go back to the factory default state I ordered Recovery DVD's at the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4HWSE3#Lenovo Support Call Center for Germany].
They shipped the 3 DVD's to me - free of charge - but I think it's only free if your Thinkpad is still in the warranty. I don't know exactly.

Then I created 2 Partitions on my Harddisk, 64 GB for Vista, 20 GB for XP, so 29 GB left free for Linux.

I installed Vista and XP and all the Thinkpad Stuff for each system.

When this was finished I took a Ubuntu Feisty Fawn installation CD and boot my Notebook with it. I created a 4 GB linux-swap partition and a 25 GB root / partition.

Because I want to boot my Ubuntu with the Windows Vista Boot Loader, I decided to install Grub to /dev/sda4 which is my Linux root partition.

The installation of Ubuntu Feisty Fawn works fine, NO PROBLEMS.

NOW I want to boot Linux from the Vista Bootloader, because I don't want to wait for two Bootscreens, and I wan't to have the chance to access the Repair Console of Windows Vista.

First I have to copy the Bootsector of my Linux Partition with:

<pre>
sudo dd if=/dev/sda4 of=/tmp/bootsect.lin bs=512 count=1
</pre>

Copy the bootsect.lin file to a USB-Stick or a writable partition which you can access from Windows Vista.

Now boot Windows Vista and copy the file bootsect.lin to your Systemdrive. In an Command Window with Administrator privileges type:

<pre>
copy bootsect.lin %SYSTEMDRIVE%\

bcdedit /create /d “Ubuntu” /application BOOTSECTOR
</pre>

You will receice an ID like this {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} from bcdedit. This is a uniqe identifier for your new Boot Entry in the Vista Bootloader. Now you will have to manipulate the entry with the following commands:

<pre>
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} device boot
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} PATH \bootsect.lin
bcdedit /displayorder {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} /addlast
bcdedit /timeout 10
</pre>

Then I booted my Ubuntu an did :

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

In this file I canged the entry the following entries:

<pre>
timeout 2
hiddenmenu
</pre>

So the computer starts up with the Windows Vista bootloader and gives me the option to start Windows XP, Windows Vista, Ubuntu and I have the option to do the repair tasks with the {{key|F8}} button on Vista if something fails. If I choose to boot Ubuntu I have the option to press the {{key|ESC}} key within the two seconds delay of the hidden Grub Menu. I.E. to boot another Linux Kernel.

== The tp_smapi modules ==

I did it under Feisty and, after the Upgrade under Gutsy, like described here : [http://www.thinkwiki.org/wiki/Tp_smapi#Installation TP SMAPI] in the Section "Installation on Ubuntu/Debian"
It worked, hdaps-gl and hdaps-pivot shows me now the movements of my Thinkpad. Like you can see here:

[[Image:Hdaps-pivot.png]]

[[Image:Hdaps-gl.png]]

== The Upgrade to Gutsy Gibbon ==

NO PROBLEMS. So why should I upgrade ?

OK I really wanted to get hdapsd (Harddisk Active Protection) to work. I tried a lot of things with Feisty, but I didn't get it going. And after a lot of seach through the Internet I found out that Gutsy Gibbon, the next Release of Ubuntu should have the Package for hdapsd on board.
SO I decided to upgrade to Gutsy - with the knowledge that it is still in Beta Stadium.

Upgrading Ubuntu is really simple, you only have to do the following steps:

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

Search all feisty entries and change them to gutsy. Save and Close the file.

Do:

{{cmduser| sudo apt-get update}}
{{cmduser| sudo apt-get upgrade}}

Go and drink a cup of Tea or Coffee. When you are back you have a message, that you should reboot your System, to get all packages active. So do it.

After the reboot I installed the hdapsd package and I tried to activate the Harddisk Protection with:

{{cmduser| sudo hdapsd -d sda -s 14 -a -v}}

But I still get the message "open(protect_file): No such file or directory". ---- The Same Message that I get in Feisty before I did the Upgrade. So I banged my head on the table and noticed that I'm not tough enough to get this thing working. Maybe someone else.

I decided to get the other things to work.

UPDATE: After some days I tried to get hdapsd to work, again !

== The hdapsd - Deamon (IBM Active Disk Protection) ==

Because I never had compiled or patched a kernel under Ubuntu I had to find out how this works ! After a lot of search in the Internet, the Ubuntu Help and at Thinkwiki.org I found the (hopefully) correct way to do it.

The best information I found was this :
[http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.04_on_a_ThinkPad_T43#Active_Protection_System_.28acceleration_monitor.29|Installing Ubuntu 7.04 on a ThinkPad T43] in section "Disk protection"

Here is what I did to get it to work:

1. Make sure that you have the required packages, with:

{{cmduser|sudo apt-get install build-essential fakeroot kernel-package libncurses5-dev wget bzip2 linux-source}}

2. Get the correct kernel patch for your running kernel from here : [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch_.28apply_using_.27patch_-p1_-l_.3C_hdaps_xx.patch.27.29| HDAPS] section "8.1.1 Kernel patch (apply using 'patch -p1 -l < hdaps_xx.patch')"

After all my experiences I was not sure that there was a patch available for my Gutsy-kernel (2.6.22-7-generic), but I still had my old kernel on the disk. So I booted up the old one (2.6.20-16-generic). Check the running kernel with:

{{cmduser|uname -r}}

You should see something like: 2.6.20-7-generic

Now change to /usr/src and look that the sources for the running kernel are there with:

{{cmduser|cd /usr/src}}
{{cmduser|ls -d linux-source*}}

You should see a file with the name "linux-source-2.6.20.tar.bz2" wich includes the packed kernel sources. You have to extract it, so do:

{{cmduser|sudo su}}
{{cmdroot|tar xvfj linux-source-2.6.20.tar.bz2}}

Now you have the kernel sources in the /usr/src/linux-source-2.6.20 directory. Take a look if there is a link from /usr/src/linux to an other kernel source directory (It's maybe there if you tried to compile a kernel some time before).

{{cmdroot|ls -l linux}}

If you see that linux is linked to an other source than your running kernel remove the link and create a new one with:

{{cmdroot|rm -r linux}}
{{cmdroot|ln -s /usr/src/linux-source-2.6.20 linux}}

Change to the source directory and patch the kernel with this:

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|patch -p1 -l < /home/dirk/993-001.bin}}

The file "993-001.bin" is the kernel patch for the 2.6.20 and 2.6.21 kernels, I downloaded it here : [http://article.gmane.org/gmane.linux.drivers.hdaps.devel/993]

After the patchwork I did this :

{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --append-to-version=.hdapscustom kernel_image --initrd binary

This would take its time, so go and clean up your house ;-)
{{HELP|I think the last command (with --append-to-version was an error ! I need help from an specialist in kernel compiling. Please read ahead at the next section "The hdapsd - Deamon (next try)". }}
After your house is clean you can do :

{{cmdroot|cd /usr/src}}
{{cmdroot|ls -l linux*.deb}}

You should see some newly builded Debian Pakage files. Install them with:

{{cmdroot|dpkg -i linux-headers-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-doc-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-image-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-manual-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-source-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}

After the installation you should reboot your computer, when Grub comes up make sure that you select your newly builded kernel.
Check it with:

{{cmduser|uname -r}}

You should see this "2.6.20.3-ubuntu1.hdapscustom". But now you have the Problem, that you have to recompile the tp_smapi driver.

{{cmduser|cd tp_smapi-0.31}}
$ sudo make install HDAPS=1
{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdpas}}

After :

<pre>
$ dmesg | grep hdaps
</pre>

You should see something like this:

[ 893.752000] hdaps: initial mode latch is 0x05
[ 893.752000] hdaps: setting ec_rate=250, filter_order=2
[ 893.752000] hdaps: fake_data_mode set to 0
[ 893.756000] hdaps: device successfully initialized.
[ 893.756000] input: hdaps as /class/input/input10
[ 893.756000] hdaps: driver successfully loaded.

Now we are ready to try out the hdapsd Deamon which is included in the Gutsy repositories, if you are using Feisty you have to compile it yourself like described here: [http://www.thinkwiki.org/wiki/How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS].

{{cmdroot|sudo hdapsd -d sda -s 12 -a -v}}

Should show this:

[[Image:hdapsd.png]]

If you load it with :

{{cmdroot|sudo hdapsd -d sda -s 12 -a}}

You get nothing until you move your Thinkpad, then you see:

Fri Jul 13 12:30:42 2007: parking
Fri Jul 13 12:30:43 2007: un-parking
Fri Jul 13 12:30:44 2007: parking
Fri Jul 13 12:30:45 2007: un-parking

Now, after I have a working hdaps-deamon I want it to be started at boot time. Because I have upgraded to Gutsy and installed the hdapsd - Package I have a script called /etc/default/hdapsd. Here I have to change some things. HINT: Remember that you still need the /etc/init.d/hdapsd file if you try this on Feisty and maybe you have to do:

{{cmduser|sudo update-rc.d hdapsd defaults}}

to create the init links for the hdapsd init script. My links was already there. My /etc/default/hdapsd script now looks like this:

<pre>
# hdapsd default file

# start hdapsd at boottime?
START="yes"

# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
DISK="sda"

# sensitivity
SENSITIVITY=12

# other options to pass to hdapsd.
# the -d $DISK, -s $SENSITIVITY, -b and -p $PIDFILE options are always passed.
OPTIONS="-a"

</pre>

Now I could use the gnome-hdaps-applet with the following comands:

{{cmduser|mkdir gnome-hdaps-applet}}
{{cmduser|cd gnome-hdaps-applet}}
{{cmduser|wget http://www.zen24593.zen.co.uk/hdaps/gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|tar -xzf gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|sudo apt-get install libpanel-applet2-dev}}
{{cmduser|gcc $(pkg-config --cflags --libs libpanelapplet-2.0) -o gnome-hdaps-applet gnome-hdaps-applet.c}}
{{cmduser|sudo cp gnome-hdaps-applet /usr/bin/}}
{{cmduser|sudo mkdir /usr/share/pixmaps/gnome-hdaps-applet/}}
{{cmduser|sudo cp *.png /usr/share/pixmaps/gnome-hdaps-applet/}}
$ sudo cp GNOME_HDAPS_StatusApplet.server /usr/lib/bonobo/servers/

Now after a restart of the Gnome Session I could find a "HDAPS Status" applet in the "Add to Panel" dialog. I added it, and when I move the Thinkpad it shows me the "Pause" [[Image:Hdaps-paused-small.png]] Symbol, otherwise it shows "Play" [[Image:Hdaps-running-small.png]].

So far so good !!! After I got this running I tried the same steps with the normal Gutsy Kernel (2.6.22-7-generic) on the same way, and it worked ! To my surprise with the same kernel patch.

The only Problem that I now have is that I cannot use restricted modules with my new kernels. Now I have to figure out how to compile restricted modules agains selfmade kernels.

{{HELP| }}

== The hdapsd - Deamon (next try) ==

I am not satisfied with the above result, because I cannot use the accelerated xorg-fglrx driver for my ATI Graphics Card and I cannot use my wireless Intel card ipw3945 driver. And the Ubuntu restricted-manager is not working. PLEASE can someone help me to compile a Ubuntu kernel in the correct way, so that I can use the whole hardware ?

I have done a - I think really ugly hack - to get the restricted-manager working :

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|cp /boot/config-2.6.20-16-generic /lib/modules/2.6.20-generic/.config}}
{{cmdroot|gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -16-generic".
Then I did compile the kernel again with:

{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I moved my modules with :

{{cmdroot|mv /lib/modules/2.6.20-16-generic /lib/modules/2.6.20-16-generic.orginal}}

And installed the kernel with:

{{cmdroot|dpkg -i linux-image-2.6.20-16-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers as described above.
Finally I copied the ipw3945.ucode with

{{cmdroot|cp /lib/firmware/2.6.22-7-generic/ipw3945.ucode /lib/firmware/2.6.20-16-generic/ipw3945.ucode}}

I think my wireless-card is working now, I check it when I'm at home again.
But my ATI Card is still not working correct.

{{HELP|Please can someone who is conform in compiling Ubuntu kernels and restricted modules help me to do it in the correct way ! And can someone recheck the things described above, because I am not sure about all things that I have written here.
}}

== The Browser Buttons ==

I wanted to use the Browser Forward & Backward Buttons within Firefox. After the upgrade my Firefox had version 2.0.0.4

I did :

{{cmduser| sudo gedit ~/.Xmodmap}}

and added the following lines :

keycode 234 = F19

keycode 233 = F20

I saved and closed the file. HINT: You have to re-login to Gnome to get the .Xmodmap file active.

Then I did the things described in [http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work#Firefox How to get special keys to work].

For the Windows Key I added "keycode 115 = F13" to my .Xmodmap File, then I klicked on "System - Einstellungen - Tastenkombinationen"
sorry I don't know how it is called in English. And changed the Entry "Das Panelmenü anzeigen" to F13

== The Brightness Buttons ==

When I wanted to control the brightness, I was not able to change it with {{key|Fn}}{{key|End}}.

So I did the Workaround menitioned here [http://thinkwiki.org/wiki/Problem_with_LCD_brightness_buttons#Workaround for Fedora Core 6 Users].
After this I was able to change the brightness with {{key|Fn}}{{key|Home}} and {{key|Fn}}{{key|End}}, but I don't have the OSD anymore.

== The Fingerprint Reader ==

Do the steps which are described in [http://www.thinkwiki.org/wiki/Installing_Ubuntu_6.10_%28Edgy_Eft%29_on_a_ThinkPad_T60#The_Fingerprint_Reader Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60] until you get to the Point where Keithvassallo says:
"Phew. Now, to make applications actually use the fingerprint reader."

I have done the following things instead of his version:

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

Change the file as following:

<pre>
#%PAM-1.0
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
auth requisite pam_nologin.so
auth required pam_env.so
@include common-auth
@include common-account
session required pam_limits.so
@include common-session
@include common-password
</pre>

and:

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

Change this file as following:

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

With this changes you have the advantage, that you are now able to login to Gnome or KDE whitout entering your password. But if you cancel the "Fingerprint Login", you are still able to login whit your username/password combination.

After I was able to login to my desktop I was unsatisfied, because my Computer still wants to get passwords i.e. when I tried to open Synaptic or when I do any sudo actions.

So I tried to figure out how this sudo thing works. I did the following change to /etc/pam.d/sudo with:

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

<pre>
#%PAM-1.0

auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/ :0
password sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam :0
auth required pam_unix.so nillock_secure
@include common-account

</pre>

With this change I was able to open System Administration tasks with my fingerprint, but the ugly thing is, that you get no information to swipe your finger over the reader when you have switched to a console session with {{Key|Ctrl}}+{{Key|Alt}}+{{Key|F1}}. The fingerprint scanner software will appear at your running X session.

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-07-16T13:36:47Z

Dirk:

== My Thinkpad ==
<pre>
Lenovo Thinkpad R60 9461 HRG
Intel Core2Duo (Merom) 1.83 CPU
120 GB SATA Hitachi HTS54161 Harddisk
2 GB RAM
ATI Mobility X1400
</pre>

Originally equipped with a preinstalled MS Windows Vista Business. So the Harddisk was parted into two Partitions.

1. The Rescue & Recovery Partition

2. The preinstalled Windows Vista Partition

And as the parcel with my new Thinkpad arrived I was surprized, that there was a Windows Vista DVD (only 32 Bit Version) with it.
So I tried Vista - but I was a little bit shocked by it's performance. I never thought that a new computer could take so much time to boot up completely.

I decided to do a clean install of Vista, but I want to have Windows XP and Ubuntu Feisty on the Harddisk too.

== New Installation ==

I wanted to use all Space of the Harddisk, so I decided to kill the Rescue & and Recovery Partition, but to have the chance to go back to the factory default state I ordered Recovery DVD's at the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4HWSE3#Lenovo Support Call Center for Germany].
They shipped the 3 DVD's to me - free of charge - but I think it's only free if your Thinkpad is still in the warranty. I don't know exactly.

Then I created 2 Partitions on my Harddisk, 64 GB for Vista, 20 GB for XP, so 29 GB left free for Linux.

I installed Vista and XP and all the Thinkpad Stuff for each system.

When this was finished I took a Ubuntu Feisty Fawn installation CD and boot my Notebook with it. I created a 4 GB linux-swap partition and a 25 GB root / partition.

Because I want to boot my Ubuntu with the Windows Vista Boot Loader, I decided to install Grub to /dev/sda4 which is my Linux root partition.

The installation of Ubuntu Feisty Fawn works fine, NO PROBLEMS.

NOW I want to boot Linux from the Vista Bootloader, because I don't want to wait for two Bootscreens, and I wan't to have the chance to access the Repair Console of Windows Vista.

First I have to copy the Bootsector of my Linux Partition with:

<pre>
sudo dd if=/dev/sda4 of=/tmp/bootsect.lin bs=512 count=1
</pre>

Copy the bootsect.lin file to a USB-Stick or a writable partition which you can access from Windows Vista.

Now boot Windows Vista and copy the file bootsect.lin to your Systemdrive. In an Command Window with Administrator privileges type:

<pre>
copy bootsect.lin %SYSTEMDRIVE%\

bcdedit /create /d “Ubuntu” /application BOOTSECTOR
</pre>

You will receice an ID like this {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} from bcdedit. This is a uniqe identifier for your new Boot Entry in the Vista Bootloader. Now you will have to manipulate the entry with the following commands:

<pre>
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} device boot
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} PATH \bootsect.lin
bcdedit /displayorder {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} /addlast
bcdedit /timeout 10
</pre>

Then I booted my Ubuntu an did :

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

In this file I canged the entry the following entries:

<pre>
timeout 2
hiddenmenu
</pre>

So the computer starts up with the Windows Vista bootloader and gives me the option to start Windows XP, Windows Vista, Ubuntu and I have the option to do the repair tasks with the {{key|F8}} button on Vista if something fails. If I choose to boot Ubuntu I have the option to press the {{key|ESC}} key within the two seconds delay of the hidden Grub Menu. I.E. to boot another Linux Kernel.

== The tp_smapi modules ==

I did it under Feisty and, after the Upgrade under Gutsy, like described here : [http://www.thinkwiki.org/wiki/Tp_smapi#Installation TP SMAPI] in the Section "Installation on Ubuntu/Debian"
It worked, hdaps-gl and hdaps-pivot shows me now the movements of my Thinkpad. Like you can see here:

[[Image:Hdaps-pivot.png]]

[[Image:Hdaps-gl.png]]

== The Upgrade to Gutsy Gibbon ==

NO PROBLEMS. So why should I upgrade ?

OK I really wanted to get hdapsd (Harddisk Active Protection) to work. I tried a lot of things with Feisty, but I didn't get it going. And after a lot of seach through the Internet I found out that Gutsy Gibbon, the next Release of Ubuntu should have the Package for hdapsd on board.
SO I decided to upgrade to Gutsy - with the knowledge that it is still in Beta Stadium.

Upgrading Ubuntu is really simple, you only have to do the following steps:

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

Search all feisty entries and change them to gutsy. Save and Close the file.

Do:

{{cmduser| sudo apt-get update}}
{{cmduser| sudo apt-get upgrade}}

Go and drink a cup of Tea or Coffee. When you are back you have a message, that you should reboot your System, to get all packages active. So do it.

After the reboot I installed the hdapsd package and I tried to activate the Harddisk Protection with:

{{cmduser| sudo hdapsd -d sda -s 14 -a -v}}

But I still get the message "open(protect_file): No such file or directory". ---- The Same Message that I get in Feisty before I did the Upgrade. So I banged my head on the table and noticed that I'm not tough enough to get this thing working. Maybe someone else.

I decided to get the other things to work.

UPDATE: After some days I tried to get hdapsd to work, again !

== The hdapsd - Deamon (IBM Active Disk Protection) ==

Because I never had compiled or patched a kernel under Ubuntu I had to find out how this works ! After a lot of search in the Internet, the Ubuntu Help and at Thinkwiki.org I found the (hopefully) correct way to do it.

The best information I found was this :
[http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.04_on_a_ThinkPad_T43#Active_Protection_System_.28acceleration_monitor.29|Installing Ubuntu 7.04 on a ThinkPad T43] in section "Disk protection"

Here is what I did to get it to work:

1. Make sure that you have the required packages, with:

{{cmduser|sudo apt-get install build-essential fakeroot kernel-package libncurses5-dev wget bzip2 linux-source}}

2. Get the correct kernel patch for your running kernel from here : [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch_.28apply_using_.27patch_-p1_-l_.3C_hdaps_xx.patch.27.29| HDAPS] section "8.1.1 Kernel patch (apply using 'patch -p1 -l < hdaps_xx.patch')"

After all my experiences I was not sure that there was a patch available for my Gutsy-kernel (2.6.22-7-generic), but I still had my old kernel on the disk. So I booted up the old one (2.6.20-16-generic). Check the running kernel with:

{{cmduser|uname -r}}

You should see something like: 2.6.20-7-generic

Now change to /usr/src and look that the sources for the running kernel are there with:

{{cmduser|cd /usr/src}}
{{cmduser|ls -d linux-source*}}

You should see a file with the name "linux-source-2.6.20.tar.bz2" wich includes the packed kernel sources. You have to extract it, so do:

{{cmduser|sudo su}}
{{cmdroot|tar xvfj linux-source-2.6.20.tar.bz2}}

Now you have the kernel sources in the /usr/src/linux-source-2.6.20 directory. Take a look if there is a link from /usr/src/linux to an other kernel source directory (It's maybe there if you tried to compile a kernel some time before).

{{cmdroot|ls -l linux}}

If you see that linux is linked to an other source than your running kernel remove the link and create a new one with:

{{cmdroot|rm -r linux}}
{{cmdroot|ln -s /usr/src/linux-source-2.6.20 linux}}

Change to the source directory and patch the kernel with this:

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|patch -p1 -l < /home/dirk/993-001.bin}}

The file "993-001.bin" is the kernel patch for the 2.6.20 and 2.6.21 kernels, I downloaded it here : [http://article.gmane.org/gmane.linux.drivers.hdaps.devel/993]

After the patchwork I did this :

{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --append-to-version=.hdapscustom kernel_image --initrd binary

This would take its time, so go and clean up your house ;-)
{{HELP|I think the last command (with --append-to-version was an error ! I need help from an specialist in kernel compiling. Please read ahead at the next section "The hdapsd - Deamon (next try)". }}
After your house is clean you can do :

{{cmdroot|cd /usr/src}}
{{cmdroot|ls -l linux*.deb}}

You should see some newly builded Debian Pakage files. Install them with:

{{cmdroot|dpkg -i linux-headers-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-doc-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-image-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-manual-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-source-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}

After the installation you should reboot your computer, when Grub comes up make sure that you select your newly builded kernel.
Check it with:

{{cmduser|uname -r}}

You should see this "2.6.20.3-ubuntu1.hdapscustom". But now you have the Problem, that you have to recompile the tp_smapi driver.

{{cmduser|cd tp_smapi-0.31}}
$ sudo make install HDAPS=1
{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdpas}}

After :

<pre>
$ dmesg | grep hdaps
</pre>

You should see something like this:

[ 893.752000] hdaps: initial mode latch is 0x05
[ 893.752000] hdaps: setting ec_rate=250, filter_order=2
[ 893.752000] hdaps: fake_data_mode set to 0
[ 893.756000] hdaps: device successfully initialized.
[ 893.756000] input: hdaps as /class/input/input10
[ 893.756000] hdaps: driver successfully loaded.

Now we are ready to try out the hdapsd Deamon which is included in the Gutsy repositories, if you are using Feisty you have to compile it yourself like described here: [http://www.thinkwiki.org/wiki/How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS].

{{cmdroot|sudo hdapsd -d sda -s 12 -a -v}}

Should show this:

[[Image:hdapsd.png]]

If you load it with :

{{cmdroot|sudo hdapsd -d sda -s 12 -a}}

You get nothing until you move your Thinkpad, then you see:

Fri Jul 13 12:30:42 2007: parking
Fri Jul 13 12:30:43 2007: un-parking
Fri Jul 13 12:30:44 2007: parking
Fri Jul 13 12:30:45 2007: un-parking

Now, after I have a working hdaps-deamon I want it to be started at boot time. Because I have upgraded to Gutsy and installed the hdapsd - Package I have a script called /etc/default/hdapsd. Here I have to change some things. HINT: Remember that you still need the /etc/init.d/hdapsd file if you try this on Feisty and maybe you have to do:

{{cmduser|sudo update-rc.d hdapsd defaults}}

to create the init links for the hdapsd init script. My links was already there. My /etc/default/hdapsd script now looks like this:

<pre>
# hdapsd default file

# start hdapsd at boottime?
START="yes"

# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
DISK="sda"

# sensitivity
SENSITIVITY=12

# other options to pass to hdapsd.
# the -d $DISK, -s $SENSITIVITY, -b and -p $PIDFILE options are always passed.
OPTIONS="-a"

</pre>

Now I could use the gnome-hdaps-applet with the following comands:

{{cmduser|mkdir gnome-hdaps-applet}}
{{cmduser|cd gnome-hdaps-applet}}
{{cmduser|wget http://www.zen24593.zen.co.uk/hdaps/gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|tar -xzf gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|sudo apt-get install libpanel-applet2-dev}}
{{cmduser|gcc $(pkg-config --cflags --libs libpanelapplet-2.0) -o gnome-hdaps-applet gnome-hdaps-applet.c}}
{{cmduser|sudo cp gnome-hdaps-applet /usr/bin/}}
{{cmduser|sudo mkdir /usr/share/pixmaps/gnome-hdaps-applet/}}
{{cmduser|sudo cp *.png /usr/share/pixmaps/gnome-hdaps-applet/}}
$ sudo cp GNOME_HDAPS_StatusApplet.server /usr/lib/bonobo/servers/

Now after a restart of the Gnome Session I could find a "HDAPS Status" applet in the "Add to Panel" dialog. I added it, and when I move the Thinkpad it shows me the "Pause" [[Image:Hdaps-paused-small.png]] Symbol, otherwise it shows "Play" [[Image:Hdaps-running-small.png]].

So far so good !!! After I got this running I tried the same steps with the normal Gutsy Kernel (2.6.22-7-generic) on the same way, and it worked ! To my surprise with the same kernel patch.

The only Problem that I now have is that I cannot use restricted modules with my new kernels. Now I have to figure out how to compile restricted modules agains selfmade kernels.

{{HELP| }}

== The hdapsd - Deamon (next try) ==

I am not satisfied with the above result, because I cannot use the accelerated xorg-fglrx driver for my ATI Graphics Card and I cannot use my wireless Intel card ipw3945 driver. And the Ubuntu restricted-manager is not working. PLEASE can someone help me to compile a Ubuntu kernel in the correct way, so that I can use the whole hardware ?

I have done a - I think really ugly hack - to get the restricted-manager working :

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|cp /boot/config-2.6.20-16-generic /lib/modules/2.6.20-generic/.config}}
{{cmdroot|gedit /usr/src/linux/Makefile}}

In the Makefile I changed the entry EXTRAVERSION to my running kernel version like this "EXTRAVERSION = -16-generic".
Then I did compile the kernel again with:

{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --revision=4711 kernel_image --initrd binary

Then I moved my modules with :

{{cmdroot|mv /lib/modules/2.6.20-16-generic /lib/modules/2.6.20-16-generic.orginal}}

And installed the kernel with:

{{cmdroot|dpkg -i linux-image-2.6.20-16-generic_4711_i386.deb}}

Then I rebooted the computer and recompiled the tp_smapi drivers as described above.
Finally I copied the ipw3945.ucode with

{{cmdroot|cp /lib/firmware/2.6.22-7-generic/ipw3945.ucode /lib/firmware/2.6.20-16-generic/ipw3945.ucode}}

I think my wireless-card is working now, I check it when I'm at home again.
But my ATI Card is still not working correct.

{{HELP|Please can someone who is conform in compiling Ubuntu kernels and restricted modules help me to do it in the correct way ! And can someone recheck the things described above, because I am not sure about all things that I have written here.

== The Browser Buttons ==

I wanted to use the Browser Forward & Backward Buttons within Firefox. After the upgrade my Firefox had version 2.0.0.4

I did :

{{cmduser| sudo gedit ~/.Xmodmap}}

and added the following lines :

keycode 234 = F19

keycode 233 = F20

I saved and closed the file. HINT: You have to re-login to Gnome to get the .Xmodmap file active.

Then I did the things described in [http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work#Firefox How to get special keys to work].

For the Windows Key I added "keycode 115 = F13" to my .Xmodmap File, then I klicked on "System - Einstellungen - Tastenkombinationen"
sorry I don't know how it is called in English. And changed the Entry "Das Panelmenü anzeigen" to F13

== The Brightness Buttons ==

When I wanted to control the brightness, I was not able to change it with {{key|Fn}}{{key|End}}.

So I did the Workaround menitioned here [http://thinkwiki.org/wiki/Problem_with_LCD_brightness_buttons#Workaround for Fedora Core 6 Users].
After this I was able to change the brightness with {{key|Fn}}{{key|Home}} and {{key|Fn}}{{key|End}}, but I don't have the OSD anymore.

== The Fingerprint Reader ==

Do the steps which are described in [http://www.thinkwiki.org/wiki/Installing_Ubuntu_6.10_%28Edgy_Eft%29_on_a_ThinkPad_T60#The_Fingerprint_Reader Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60] until you get to the Point where Keithvassallo says:
"Phew. Now, to make applications actually use the fingerprint reader."

I have done the following things instead of his version:

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

Change the file as following:

<pre>
#%PAM-1.0
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
auth requisite pam_nologin.so
auth required pam_env.so
@include common-auth
@include common-account
session required pam_limits.so
@include common-session
@include common-password
</pre>

and:

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

Change this file as following:

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

With this changes you have the advantage, that you are now able to login to Gnome or KDE whitout entering your password. But if you cancel the "Fingerprint Login", you are still able to login whit your username/password combination.

After I was able to login to my desktop I was unsatisfied, because my Computer still wants to get passwords i.e. when I tried to open Synaptic or when I do any sudo actions.

So I tried to figure out how this sudo thing works. I did the following change to /etc/pam.d/sudo with:

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

<pre>
#%PAM-1.0

auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/ :0
password sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam :0
auth required pam_unix.so nillock_secure
@include common-account

</pre>

With this change I was able to open System Administration tasks with my fingerprint, but the ugly thing is, that you get no information to swipe your finger over the reader when you have switched to a console session with {{Key|Ctrl}}+{{Key|Alt}}+{{Key|F1}}. The fingerprint scanner software will appear at your running X session.

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-07-16T12:58:14Z

Dirk: /* The hdapsd - Deamon (IBM Active Disk Protection) */

== My Thinkpad ==
<pre>
Lenovo Thinkpad R60 9461 HRG
Intel Core2Duo (Merom) 1.83 CPU
120 GB SATA Hitachi HTS54161 Harddisk
2 GB RAM
ATI Mobility X1400
</pre>

Originally equipped with a preinstalled MS Windows Vista Business. So the Harddisk was parted into two Partitions.

1. The Rescue & Recovery Partition

2. The preinstalled Windows Vista Partition

And as the parcel with my new Thinkpad arrived I was surprized, that there was a Windows Vista DVD (only 32 Bit Version) with it.
So I tried Vista - but I was a little bit shocked by it's performance. I never thought that a new computer could take so much time to boot up completely.

I decided to do a clean install of Vista, but I want to have Windows XP and Ubuntu Feisty on the Harddisk too.

== New Installation ==

I wanted to use all Space of the Harddisk, so I decided to kill the Rescue & and Recovery Partition, but to have the chance to go back to the factory default state I ordered Recovery DVD's at the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4HWSE3#Lenovo Support Call Center for Germany].
They shipped the 3 DVD's to me - free of charge - but I think it's only free if your Thinkpad is still in the warranty. I don't know exactly.

Then I created 2 Partitions on my Harddisk, 64 GB for Vista, 20 GB for XP, so 29 GB left free for Linux.

I installed Vista and XP and all the Thinkpad Stuff for each system.

When this was finished I took a Ubuntu Feisty Fawn installation CD and boot my Notebook with it. I created a 4 GB linux-swap partition and a 25 GB root / partition.

Because I want to boot my Ubuntu with the Windows Vista Boot Loader, I decided to install Grub to /dev/sda4 which is my Linux root partition.

The installation of Ubuntu Feisty Fawn works fine, NO PROBLEMS.

NOW I want to boot Linux from the Vista Bootloader, because I don't want to wait for two Bootscreens, and I wan't to have the chance to access the Repair Console of Windows Vista.

First I have to copy the Bootsector of my Linux Partition with:

<pre>
sudo dd if=/dev/sda4 of=/tmp/bootsect.lin bs=512 count=1
</pre>

Copy the bootsect.lin file to a USB-Stick or a writable partition which you can access from Windows Vista.

Now boot Windows Vista and copy the file bootsect.lin to your Systemdrive. In an Command Window with Administrator privileges type:

<pre>
copy bootsect.lin %SYSTEMDRIVE%\

bcdedit /create /d “Ubuntu” /application BOOTSECTOR
</pre>

You will receice an ID like this {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} from bcdedit. This is a uniqe identifier for your new Boot Entry in the Vista Bootloader. Now you will have to manipulate the entry with the following commands:

<pre>
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} device boot
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} PATH \bootsect.lin
bcdedit /displayorder {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} /addlast
bcdedit /timeout 10
</pre>

Then I booted my Ubuntu an did :

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

In this file I canged the entry the following entries:

<pre>
timeout 2
hiddenmenu
</pre>

So the computer starts up with the Windows Vista bootloader and gives me the option to start Windows XP, Windows Vista, Ubuntu and I have the option to do the repair tasks with the {{key|F8}} button on Vista if something fails. If I choose to boot Ubuntu I have the option to press the {{key|ESC}} key within the two seconds delay of the hidden Grub Menu. I.E. to boot another Linux Kernel.

== The tp_smapi modules ==

I did it under Feisty and, after the Upgrade under Gutsy, like described here : [http://www.thinkwiki.org/wiki/Tp_smapi#Installation TP SMAPI] in the Section "Installation on Ubuntu/Debian"
It worked, hdaps-gl and hdaps-pivot shows me now the movements of my Thinkpad. Like you can see here:

[[Image:Hdaps-pivot.png]]

[[Image:Hdaps-gl.png]]

== The Upgrade to Gutsy Gibbon ==

NO PROBLEMS. So why should I upgrade ?

OK I really wanted to get hdapsd (Harddisk Active Protection) to work. I tried a lot of things with Feisty, but I didn't get it going. And after a lot of seach through the Internet I found out that Gutsy Gibbon, the next Release of Ubuntu should have the Package for hdapsd on board.
SO I decided to upgrade to Gutsy - with the knowledge that it is still in Beta Stadium.

Upgrading Ubuntu is really simple, you only have to do the following steps:

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

Search all feisty entries and change them to gutsy. Save and Close the file.

Do:

{{cmduser| sudo apt-get update}}
{{cmduser| sudo apt-get upgrade}}

Go and drink a cup of Tea or Coffee. When you are back you have a message, that you should reboot your System, to get all packages active. So do it.

After the reboot I installed the hdapsd package and I tried to activate the Harddisk Protection with:

{{cmduser| sudo hdapsd -d sda -s 14 -a -v}}

But I still get the message "open(protect_file): No such file or directory". ---- The Same Message that I get in Feisty before I did the Upgrade. So I banged my head on the table and noticed that I'm not tough enough to get this thing working. Maybe someone else.

I decided to get the other things to work.

UPDATE: After some days I tried to get hdapsd to work, again !

== The hdapsd - Deamon (IBM Active Disk Protection) ==

Because I never had compiled or patched a kernel under Ubuntu I had to find out how this works ! After a lot of search in the Internet, the Ubuntu Help and at Thinkwiki.org I found the (hopefully) correct way to do it.

The best information I found was this :
[http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.04_on_a_ThinkPad_T43#Active_Protection_System_.28acceleration_monitor.29|Installing Ubuntu 7.04 on a ThinkPad T43] in section "Disk protection"

Here is what I did to get it to work:

1. Make sure that you have the required packages, with:

{{cmduser|sudo apt-get install build-essential fakeroot kernel-package libncurses5-dev wget bzip2 linux-source}}

2. Get the correct kernel patch for your running kernel from here : [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch_.28apply_using_.27patch_-p1_-l_.3C_hdaps_xx.patch.27.29| HDAPS] section "8.1.1 Kernel patch (apply using 'patch -p1 -l < hdaps_xx.patch')"

After all my experiences I was not sure that there was a patch available for my Gutsy-kernel (2.6.22-7-generic), but I still had my old kernel on the disk. So I booted up the old one (2.6.20-16-generic). Check the running kernel with:

{{cmduser|uname -r}}

You should see something like: 2.6.20-7-generic

Now change to /usr/src and look that the sources for the running kernel are there with:

{{cmduser|cd /usr/src}}
{{cmduser|ls -d linux-source*}}

You should see a file with the name "linux-source-2.6.20.tar.bz2" wich includes the packed kernel sources. You have to extract it, so do:

{{cmduser|sudo su}}
{{cmdroot|tar xvfj linux-source-2.6.20.tar.bz2}}

Now you have the kernel sources in the /usr/src/linux-source-2.6.20 directory. Take a look if there is a link from /usr/src/linux to an other kernel source directory (It's maybe there if you tried to compile a kernel some time before).

{{cmdroot|ls -l linux}}

If you see that linux is linked to an other source than your running kernel remove the link and create a new one with:

{{cmdroot|rm -r linux}}
{{cmdroot|ln -s /usr/src/linux-source-2.6.20 linux}}

Change to the source directory and patch the kernel with this:

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|patch -p1 -l < /home/dirk/993-001.bin}}

The file "993-001.bin" is the kernel patch for the 2.6.20 and 2.6.21 kernels, I downloaded it here : [http://article.gmane.org/gmane.linux.drivers.hdaps.devel/993]

After the patchwork I did this :

{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --append-to-version=.hdapscustom kernel_image --initrd binary

This would take its time, so go and clean up your house ;-)
{{HELP|I think the last command (with --append-to-version was an error ! I need help from an specialist in kernel compiling. Please read ahead at the next section. }}
After your house is clean you can do :

{{cmdroot|cd /usr/src}}
{{cmdroot|ls -l linux*.deb}}

You should see some newly builded Debian Pakage files. Install them with:

{{cmdroot|dpkg -i linux-headers-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-doc-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-image-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-manual-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-source-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}

After the installation you should reboot your computer, when Grub comes up make sure that you select your newly builded kernel.
Check it with:

{{cmduser|uname -r}}

You should see this "2.6.20.3-ubuntu1.hdapscustom". But now you have the Problem, that you have to recompile the tp_smapi driver.

{{cmduser|cd tp_smapi-0.31}}
$ sudo make install HDAPS=1
{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdpas}}

After :

<pre>
$ dmesg | grep hdaps
</pre>

You should see something like this:

[ 893.752000] hdaps: initial mode latch is 0x05
[ 893.752000] hdaps: setting ec_rate=250, filter_order=2
[ 893.752000] hdaps: fake_data_mode set to 0
[ 893.756000] hdaps: device successfully initialized.
[ 893.756000] input: hdaps as /class/input/input10
[ 893.756000] hdaps: driver successfully loaded.

Now we are ready to try out the hdapsd Deamon which is included in the Gutsy repositories, if you are using Feisty you have to compile it yourself like described here: [http://www.thinkwiki.org/wiki/How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS].

{{cmdroot|sudo hdapsd -d sda -s 12 -a -v}}

Should show this:

[[Image:hdapsd.png]]

If you load it with :

{{cmdroot|sudo hdapsd -d sda -s 12 -a}}

You get nothing until you move your Thinkpad, then you see:

Fri Jul 13 12:30:42 2007: parking
Fri Jul 13 12:30:43 2007: un-parking
Fri Jul 13 12:30:44 2007: parking
Fri Jul 13 12:30:45 2007: un-parking

Now, after I have a working hdaps-deamon I want it to be started at boot time. Because I have upgraded to Gutsy and installed the hdapsd - Package I have a script called /etc/default/hdapsd. Here I have to change some things. HINT: Remember that you still need the /etc/init.d/hdapsd file if you try this on Feisty and maybe you have to do:

{{cmduser|sudo update-rc.d hdapsd defaults}}

to create the init links for the hdapsd init script. My links was already there. My /etc/default/hdapsd script now looks like this:

<pre>
# hdapsd default file

# start hdapsd at boottime?
START="yes"

# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
DISK="sda"

# sensitivity
SENSITIVITY=12

# other options to pass to hdapsd.
# the -d $DISK, -s $SENSITIVITY, -b and -p $PIDFILE options are always passed.
OPTIONS="-a"

</pre>

Now I could use the gnome-hdaps-applet with the following comands:

{{cmduser|mkdir gnome-hdaps-applet}}
{{cmduser|cd gnome-hdaps-applet}}
{{cmduser|wget http://www.zen24593.zen.co.uk/hdaps/gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|tar -xzf gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|sudo apt-get install libpanel-applet2-dev}}
{{cmduser|gcc $(pkg-config --cflags --libs libpanelapplet-2.0) -o gnome-hdaps-applet gnome-hdaps-applet.c}}
{{cmduser|sudo cp gnome-hdaps-applet /usr/bin/}}
{{cmduser|sudo mkdir /usr/share/pixmaps/gnome-hdaps-applet/}}
{{cmduser|sudo cp *.png /usr/share/pixmaps/gnome-hdaps-applet/}}
$ sudo cp GNOME_HDAPS_StatusApplet.server /usr/lib/bonobo/servers/

Now after a restart of the Gnome Session I could find a "HDAPS Status" applet in the "Add to Panel" dialog. I added it, and when I move the Thinkpad it shows me the "Pause" [[Image:Hdaps-paused-small.png]] Symbol, otherwise it shows "Play" [[Image:Hdaps-running-small.png]].

So far so good !!! After I got this running I tried the same steps with the normal Gutsy Kernel (2.6.22-7-generic) on the same way, and it worked ! To my surprise with the same kernel patch.

The only Problem that I now have is that I cannot use restricted modules with my new kernels. Now I have to figure out how to compile restricted modules agains selfmade kernels.

== The Browser Buttons ==

I wanted to use the Browser Forward & Backward Buttons within Firefox. After the upgrade my Firefox had version 2.0.0.4

I did :

{{cmduser| sudo gedit ~/.Xmodmap}}

and added the following lines :

keycode 234 = F19

keycode 233 = F20

I saved and closed the file. HINT: You have to re-login to Gnome to get the .Xmodmap file active.

Then I did the things described in [http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work#Firefox How to get special keys to work].

For the Windows Key I added "keycode 115 = F13" to my .Xmodmap File, then I klicked on "System - Einstellungen - Tastenkombinationen"
sorry I don't know how it is called in English. And changed the Entry "Das Panelmenü anzeigen" to F13

== The Brightness Buttons ==

When I wanted to control the brightness, I was not able to change it with {{key|Fn}}{{key|End}}.

So I did the Workaround menitioned here [http://thinkwiki.org/wiki/Problem_with_LCD_brightness_buttons#Workaround for Fedora Core 6 Users].
After this I was able to change the brightness with {{key|Fn}}{{key|Home}} and {{key|Fn}}{{key|End}}, but I don't have the OSD anymore.

== The Fingerprint Reader ==

Do the steps which are described in [http://www.thinkwiki.org/wiki/Installing_Ubuntu_6.10_%28Edgy_Eft%29_on_a_ThinkPad_T60#The_Fingerprint_Reader Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60] until you get to the Point where Keithvassallo says:
"Phew. Now, to make applications actually use the fingerprint reader."

I have done the following things instead of his version:

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

Change the file as following:

<pre>
#%PAM-1.0
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
auth requisite pam_nologin.so
auth required pam_env.so
@include common-auth
@include common-account
session required pam_limits.so
@include common-session
@include common-password
</pre>

and:

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

Change this file as following:

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

With this changes you have the advantage, that you are now able to login to Gnome or KDE whitout entering your password. But if you cancel the "Fingerprint Login", you are still able to login whit your username/password combination.

After I was able to login to my desktop I was unsatisfied, because my Computer still wants to get passwords i.e. when I tried to open Synaptic or when I do any sudo actions.

So I tried to figure out how this sudo thing works. I did the following change to /etc/pam.d/sudo with:

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

<pre>
#%PAM-1.0

auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/ :0
password sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam :0
auth required pam_unix.so nillock_secure
@include common-account

</pre>

With this change I was able to open System Administration tasks with my fingerprint, but the ugly thing is, that you get no information to swipe your finger over the reader when you have switched to a console session with {{Key|Ctrl}}+{{Key|Alt}}+{{Key|F1}}. The fingerprint scanner software will appear at your running X session.

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-07-16T06:45:29Z

Dirk: /* The hdapsd - Deamon (IBM Active Disk Protection) */

== My Thinkpad ==
<pre>
Lenovo Thinkpad R60 9461 HRG
Intel Core2Duo (Merom) 1.83 CPU
120 GB SATA Hitachi HTS54161 Harddisk
2 GB RAM
ATI Mobility X1400
</pre>

Originally equipped with a preinstalled MS Windows Vista Business. So the Harddisk was parted into two Partitions.

1. The Rescue & Recovery Partition

2. The preinstalled Windows Vista Partition

And as the parcel with my new Thinkpad arrived I was surprized, that there was a Windows Vista DVD (only 32 Bit Version) with it.
So I tried Vista - but I was a little bit shocked by it's performance. I never thought that a new computer could take so much time to boot up completely.

I decided to do a clean install of Vista, but I want to have Windows XP and Ubuntu Feisty on the Harddisk too.

== New Installation ==

I wanted to use all Space of the Harddisk, so I decided to kill the Rescue & and Recovery Partition, but to have the chance to go back to the factory default state I ordered Recovery DVD's at the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4HWSE3#Lenovo Support Call Center for Germany].
They shipped the 3 DVD's to me - free of charge - but I think it's only free if your Thinkpad is still in the warranty. I don't know exactly.

Then I created 2 Partitions on my Harddisk, 64 GB for Vista, 20 GB for XP, so 29 GB left free for Linux.

I installed Vista and XP and all the Thinkpad Stuff for each system.

When this was finished I took a Ubuntu Feisty Fawn installation CD and boot my Notebook with it. I created a 4 GB linux-swap partition and a 25 GB root / partition.

Because I want to boot my Ubuntu with the Windows Vista Boot Loader, I decided to install Grub to /dev/sda4 which is my Linux root partition.

The installation of Ubuntu Feisty Fawn works fine, NO PROBLEMS.

NOW I want to boot Linux from the Vista Bootloader, because I don't want to wait for two Bootscreens, and I wan't to have the chance to access the Repair Console of Windows Vista.

First I have to copy the Bootsector of my Linux Partition with:

<pre>
sudo dd if=/dev/sda4 of=/tmp/bootsect.lin bs=512 count=1
</pre>

Copy the bootsect.lin file to a USB-Stick or a writable partition which you can access from Windows Vista.

Now boot Windows Vista and copy the file bootsect.lin to your Systemdrive. In an Command Window with Administrator privileges type:

<pre>
copy bootsect.lin %SYSTEMDRIVE%\

bcdedit /create /d “Ubuntu” /application BOOTSECTOR
</pre>

You will receice an ID like this {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} from bcdedit. This is a uniqe identifier for your new Boot Entry in the Vista Bootloader. Now you will have to manipulate the entry with the following commands:

<pre>
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} device boot
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} PATH \bootsect.lin
bcdedit /displayorder {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} /addlast
bcdedit /timeout 10
</pre>

Then I booted my Ubuntu an did :

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

In this file I canged the entry the following entries:

<pre>
timeout 2
hiddenmenu
</pre>

So the computer starts up with the Windows Vista bootloader and gives me the option to start Windows XP, Windows Vista, Ubuntu and I have the option to do the repair tasks with the {{key|F8}} button on Vista if something fails. If I choose to boot Ubuntu I have the option to press the {{key|ESC}} key within the two seconds delay of the hidden Grub Menu. I.E. to boot another Linux Kernel.

== The tp_smapi modules ==

I did it under Feisty and, after the Upgrade under Gutsy, like described here : [http://www.thinkwiki.org/wiki/Tp_smapi#Installation TP SMAPI] in the Section "Installation on Ubuntu/Debian"
It worked, hdaps-gl and hdaps-pivot shows me now the movements of my Thinkpad. Like you can see here:

[[Image:Hdaps-pivot.png]]

[[Image:Hdaps-gl.png]]

== The Upgrade to Gutsy Gibbon ==

NO PROBLEMS. So why should I upgrade ?

OK I really wanted to get hdapsd (Harddisk Active Protection) to work. I tried a lot of things with Feisty, but I didn't get it going. And after a lot of seach through the Internet I found out that Gutsy Gibbon, the next Release of Ubuntu should have the Package for hdapsd on board.
SO I decided to upgrade to Gutsy - with the knowledge that it is still in Beta Stadium.

Upgrading Ubuntu is really simple, you only have to do the following steps:

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

Search all feisty entries and change them to gutsy. Save and Close the file.

Do:

{{cmduser| sudo apt-get update}}
{{cmduser| sudo apt-get upgrade}}

Go and drink a cup of Tea or Coffee. When you are back you have a message, that you should reboot your System, to get all packages active. So do it.

After the reboot I installed the hdapsd package and I tried to activate the Harddisk Protection with:

{{cmduser| sudo hdapsd -d sda -s 14 -a -v}}

But I still get the message "open(protect_file): No such file or directory". ---- The Same Message that I get in Feisty before I did the Upgrade. So I banged my head on the table and noticed that I'm not tough enough to get this thing working. Maybe someone else.

I decided to get the other things to work.

UPDATE: After some days I tried to get hdapsd to work, again !

== The hdapsd - Deamon (IBM Active Disk Protection) ==

Because I never had compiled or patched a kernel under Ubuntu I had to find out how this works ! After a lot of search in the Internet, the Ubuntu Help and at Thinkwiki.org I found the (hopefully) correct way to do it.

The best information I found was this :
[http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.04_on_a_ThinkPad_T43#Active_Protection_System_.28acceleration_monitor.29|Installing Ubuntu 7.04 on a ThinkPad T43] in section "Disk protection"

Here is what I did to get it to work:

1. Make sure that you have the required packages, with:

{{cmduser|sudo apt-get install build-essential fakeroot kernel-package libncurses5-dev wget bzip2 linux-source}}

2. Get the correct kernel patch for your running kernel from here : [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch_.28apply_using_.27patch_-p1_-l_.3C_hdaps_xx.patch.27.29| HDAPS] section "8.1.1 Kernel patch (apply using 'patch -p1 -l < hdaps_xx.patch')"

After all my experiences I was not sure that there was a patch available for my Gutsy-kernel (2.6.22-7-generic), but I still had my old kernel on the disk. So I booted up the old one (2.6.20-16-generic). Check the running kernel with:

{{cmduser|uname -r}}

You should see something like: 2.6.20-7-generic

Now change to /usr/src and look that the sources for the running kernel are there with:

{{cmduser|cd /usr/src}}
{{cmduser|ls -d linux-source*}}

You should see a file with the name "linux-source-2.6.20.tar.bz2" wich includes the packed kernel sources. You have to extract it, so do:

{{cmduser|sudo su}}
{{cmdroot|tar xvfj linux-source-2.6.20.tar.bz2}}

Now you have the kernel sources in the /usr/src/linux-source-2.6.20 directory. Take a look if there is a link from /usr/src/linux to an other kernel source directory (It's maybe there if you tried to compile a kernel some time before).

{{cmdroot|ls -l linux}}

If you see that linux is linked to an other source than your running kernel remove the link and create a new one with:

{{cmdroot|rm -r linux}}
{{cmdroot|ln -s /usr/src/linux-source-2.6.20 linux}}

Change to the source directory and patch the kernel with this:

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|patch -p1 -l < /home/dirk/993-001.bin}}

The file "993-001.bin" is the kernel patch for the 2.6.20 and 2.6.21 kernels, I downloaded it here : [http://article.gmane.org/gmane.linux.drivers.hdaps.devel/993]

After the patchwork I did this :

{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --append-to-version=.hdapscustom kernel_image --initrd binary

This would take its time, so go and clean up your house ;-)
After your house is clean you can do :

{{cmdroot|cd /usr/src}}
{{cmdroot|ls -l linux*.deb}}

You should see some newly builded Debian Pakage files. Install them with:

{{cmdroot|dpkg -i linux-headers-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-doc-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-image-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-manual-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-source-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}

After the installation you should reboot your computer, when Grub comes up make sure that you select your newly builded kernel.
Check it with:

{{cmduser|uname -r}}

You should see this "2.6.20.3-ubuntu1.hdapscustom". But now you have the Problem, that you have to recompile the tp_smapi driver.

{{cmduser|cd tp_smapi-0.31}}
$ sudo make install HDAPS=1
{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdpas}}

After :

<pre>
$ dmesg | grep hdaps
</pre>

You should see something like this:

[ 893.752000] hdaps: initial mode latch is 0x05
[ 893.752000] hdaps: setting ec_rate=250, filter_order=2
[ 893.752000] hdaps: fake_data_mode set to 0
[ 893.756000] hdaps: device successfully initialized.
[ 893.756000] input: hdaps as /class/input/input10
[ 893.756000] hdaps: driver successfully loaded.

Now we are ready to try out the hdapsd Deamon which is included in the Gutsy repositories, if you are using Feisty you have to compile it yourself like described here: [http://www.thinkwiki.org/wiki/How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS].

{{cmdroot|sudo hdapsd -d sda -s 12 -a -v}}

Should show this:

[[Image:hdapsd.png]]

If you load it with :

{{cmdroot|sudo hdapsd -d sda -s 12 -a}}

You get nothing until you move your Thinkpad, then you see:

Fri Jul 13 12:30:42 2007: parking
Fri Jul 13 12:30:43 2007: un-parking
Fri Jul 13 12:30:44 2007: parking
Fri Jul 13 12:30:45 2007: un-parking

Now, after I have a working hdaps-deamon I want it to be started at boot time. Because I have upgraded to Gutsy and installed the hdapsd - Package I have a script called /etc/default/hdapsd. Here I have to change some things. HINT: Remember that you still need the /etc/init.d/hdapsd file if you try this on Feisty and maybe you have to do:

{{cmduser|sudo update-rc.d hdapsd defaults}}

to create the init links for the hdapsd init script. My links was already there. My /etc/default/hdapsd script now looks like this:

<pre>
# hdapsd default file

# start hdapsd at boottime?
START="yes"

# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
DISK="sda"

# sensitivity
SENSITIVITY=12

# other options to pass to hdapsd.
# the -d $DISK, -s $SENSITIVITY, -b and -p $PIDFILE options are always passed.
OPTIONS="-a"

</pre>

Now I could use the gnome-hdaps-applet with the following comands:

{{cmduser|mkdir gnome-hdaps-applet}}
{{cmduser|cd gnome-hdaps-applet}}
{{cmduser|wget http://www.zen24593.zen.co.uk/hdaps/gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|tar -xzf gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|sudo apt-get install libpanel-applet2-dev}}
{{cmduser|gcc $(pkg-config --cflags --libs libpanelapplet-2.0) -o gnome-hdaps-applet gnome-hdaps-applet.c}}
{{cmduser|sudo cp gnome-hdaps-applet /usr/bin/}}
{{cmduser|sudo mkdir /usr/share/pixmaps/gnome-hdaps-applet/}}
{{cmduser|sudo cp *.png /usr/share/pixmaps/gnome-hdaps-applet/}}
$ sudo cp GNOME_HDAPS_StatusApplet.server /usr/lib/bonobo/servers/

Now after a restart of the Gnome Session I could find a "HDAPS Status" applet in the "Add to Panel" dialog. I added it, and when I move the Thinkpad it shows me the "Pause" [[Image:Hdaps-paused-small.png]] Symbol, otherwise it shows "Play" [[Image:Hdaps-running-small.png]].

So far so good !!! After I got this running I tried the same steps with the normal Gutsy Kernel (2.6.22-7-generic) on the same way, and it worked ! To my surprise with the same kernel patch.

The only Problem that I now have is that I cannot use restricted modules with my new kernels. Now I have to figure out how to compile restricted modules agains selfmade kernels.

== The Browser Buttons ==

I wanted to use the Browser Forward & Backward Buttons within Firefox. After the upgrade my Firefox had version 2.0.0.4

I did :

{{cmduser| sudo gedit ~/.Xmodmap}}

and added the following lines :

keycode 234 = F19

keycode 233 = F20

I saved and closed the file. HINT: You have to re-login to Gnome to get the .Xmodmap file active.

Then I did the things described in [http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work#Firefox How to get special keys to work].

For the Windows Key I added "keycode 115 = F13" to my .Xmodmap File, then I klicked on "System - Einstellungen - Tastenkombinationen"
sorry I don't know how it is called in English. And changed the Entry "Das Panelmenü anzeigen" to F13

== The Brightness Buttons ==

When I wanted to control the brightness, I was not able to change it with {{key|Fn}}{{key|End}}.

So I did the Workaround menitioned here [http://thinkwiki.org/wiki/Problem_with_LCD_brightness_buttons#Workaround for Fedora Core 6 Users].
After this I was able to change the brightness with {{key|Fn}}{{key|Home}} and {{key|Fn}}{{key|End}}, but I don't have the OSD anymore.

== The Fingerprint Reader ==

Do the steps which are described in [http://www.thinkwiki.org/wiki/Installing_Ubuntu_6.10_%28Edgy_Eft%29_on_a_ThinkPad_T60#The_Fingerprint_Reader Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60] until you get to the Point where Keithvassallo says:
"Phew. Now, to make applications actually use the fingerprint reader."

I have done the following things instead of his version:

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

Change the file as following:

<pre>
#%PAM-1.0
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
auth requisite pam_nologin.so
auth required pam_env.so
@include common-auth
@include common-account
session required pam_limits.so
@include common-session
@include common-password
</pre>

and:

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

Change this file as following:

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

With this changes you have the advantage, that you are now able to login to Gnome or KDE whitout entering your password. But if you cancel the "Fingerprint Login", you are still able to login whit your username/password combination.

After I was able to login to my desktop I was unsatisfied, because my Computer still wants to get passwords i.e. when I tried to open Synaptic or when I do any sudo actions.

So I tried to figure out how this sudo thing works. I did the following change to /etc/pam.d/sudo with:

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

<pre>
#%PAM-1.0

auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/ :0
password sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam :0
auth required pam_unix.so nillock_secure
@include common-account

</pre>

With this change I was able to open System Administration tasks with my fingerprint, but the ugly thing is, that you get no information to swipe your finger over the reader when you have switched to a console session with {{Key|Ctrl}}+{{Key|Alt}}+{{Key|F1}}. The fingerprint scanner software will appear at your running X session.

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-07-13T13:45:28Z

Dirk: /* The hdapsd - Deamon (IBM Active Disk Protection) */

== My Thinkpad ==
<pre>
Lenovo Thinkpad R60 9461 HRG
Intel Core2Duo (Merom) 1.83 CPU
120 GB SATA Hitachi HTS54161 Harddisk
2 GB RAM
ATI Mobility X1400
</pre>

Originally equipped with a preinstalled MS Windows Vista Business. So the Harddisk was parted into two Partitions.

1. The Rescue & Recovery Partition

2. The preinstalled Windows Vista Partition

And as the parcel with my new Thinkpad arrived I was surprized, that there was a Windows Vista DVD (only 32 Bit Version) with it.
So I tried Vista - but I was a little bit shocked by it's performance. I never thought that a new computer could take so much time to boot up completely.

I decided to do a clean install of Vista, but I want to have Windows XP and Ubuntu Feisty on the Harddisk too.

== New Installation ==

I wanted to use all Space of the Harddisk, so I decided to kill the Rescue & and Recovery Partition, but to have the chance to go back to the factory default state I ordered Recovery DVD's at the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4HWSE3#Lenovo Support Call Center for Germany].
They shipped the 3 DVD's to me - free of charge - but I think it's only free if your Thinkpad is still in the warranty. I don't know exactly.

Then I created 2 Partitions on my Harddisk, 64 GB for Vista, 20 GB for XP, so 29 GB left free for Linux.

I installed Vista and XP and all the Thinkpad Stuff for each system.

When this was finished I took a Ubuntu Feisty Fawn installation CD and boot my Notebook with it. I created a 4 GB linux-swap partition and a 25 GB root / partition.

Because I want to boot my Ubuntu with the Windows Vista Boot Loader, I decided to install Grub to /dev/sda4 which is my Linux root partition.

The installation of Ubuntu Feisty Fawn works fine, NO PROBLEMS.

NOW I want to boot Linux from the Vista Bootloader, because I don't want to wait for two Bootscreens, and I wan't to have the chance to access the Repair Console of Windows Vista.

First I have to copy the Bootsector of my Linux Partition with:

<pre>
sudo dd if=/dev/sda4 of=/tmp/bootsect.lin bs=512 count=1
</pre>

Copy the bootsect.lin file to a USB-Stick or a writable partition which you can access from Windows Vista.

Now boot Windows Vista and copy the file bootsect.lin to your Systemdrive. In an Command Window with Administrator privileges type:

<pre>
copy bootsect.lin %SYSTEMDRIVE%\

bcdedit /create /d “Ubuntu” /application BOOTSECTOR
</pre>

You will receice an ID like this {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} from bcdedit. This is a uniqe identifier for your new Boot Entry in the Vista Bootloader. Now you will have to manipulate the entry with the following commands:

<pre>
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} device boot
bcdedit /set {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} PATH \bootsect.lin
bcdedit /displayorder {4cdcfd5b-1f3a-11dc-bb90-0019d2b3e926} /addlast
bcdedit /timeout 10
</pre>

Then I booted my Ubuntu an did :

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

In this file I canged the entry the following entries:

<pre>
timeout 2
hiddenmenu
</pre>

So the computer starts up with the Windows Vista bootloader and gives me the option to start Windows XP, Windows Vista, Ubuntu and I have the option to do the repair tasks with the {{key|F8}} button on Vista if something fails. If I choose to boot Ubuntu I have the option to press the {{key|ESC}} key within the two seconds delay of the hidden Grub Menu. I.E. to boot another Linux Kernel.

== The tp_smapi modules ==

I did it under Feisty and, after the Upgrade under Gutsy, like described here : [http://www.thinkwiki.org/wiki/Tp_smapi#Installation TP SMAPI] in the Section "Installation on Ubuntu/Debian"
It worked, hdaps-gl and hdaps-pivot shows me now the movements of my Thinkpad. Like you can see here:

[[Image:Hdaps-pivot.png]]

[[Image:Hdaps-gl.png]]

== The Upgrade to Gutsy Gibbon ==

NO PROBLEMS. So why should I upgrade ?

OK I really wanted to get hdapsd (Harddisk Active Protection) to work. I tried a lot of things with Feisty, but I didn't get it going. And after a lot of seach through the Internet I found out that Gutsy Gibbon, the next Release of Ubuntu should have the Package for hdapsd on board.
SO I decided to upgrade to Gutsy - with the knowledge that it is still in Beta Stadium.

Upgrading Ubuntu is really simple, you only have to do the following steps:

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

Search all feisty entries and change them to gutsy. Save and Close the file.

Do:

{{cmduser| sudo apt-get update}}
{{cmduser| sudo apt-get upgrade}}

Go and drink a cup of Tea or Coffee. When you are back you have a message, that you should reboot your System, to get all packages active. So do it.

After the reboot I installed the hdapsd package and I tried to activate the Harddisk Protection with:

{{cmduser| sudo hdapsd -d sda -s 14 -a -v}}

But I still get the message "open(protect_file): No such file or directory". ---- The Same Message that I get in Feisty before I did the Upgrade. So I banged my head on the table and noticed that I'm not tough enough to get this thing working. Maybe someone else.

I decided to get the other things to work.

UPDATE: After some days I tried to get hdapsd to work, again !

== The hdapsd - Deamon (IBM Active Disk Protection) ==

Because I never had compiled or patched a kernel under Ubuntu I had to find out how this works ! After a lot of search in the Internet, the Ubuntu Help and at Thinkwiki.org I found the (hopefully) correct way to do it.

The best information I found was this :
[http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.04_on_a_ThinkPad_T43#Active_Protection_System_.28acceleration_monitor.29|Installing Ubuntu 7.04 on a ThinkPad T43] in section "Disk protection"

Here is what I did to get it to work:

1. Make sure that you have the required packages, with:

{{cmduser|sudo apt-get install build-essential fakeroot kernel-package libncurses5-dev wget bzip2 linux-source}}

2. Get the correct kernel patch for your running kernel from here : [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch_.28apply_using_.27patch_-p1_-l_.3C_hdaps_xx.patch.27.29| HDAPS] section "8.1.1 Kernel patch (apply using 'patch -p1 -l < hdaps_xx.patch')"

After all my experiences I was not sure that there was a patch available for my Gutsy-kernel (2.6.22-7-generic), but I still had my old kernel on the disk. So I booted up the old one (2.6.20-16-generic). Check the running kernel with:

{{cmduser|uname -r}}

You should see something like: 2.6.20-7-generic

Now change to /usr/src and look that the sources for the running kernel are there with:

{{cmduser|cd /usr/src}}
{{cmduser|ls -d linux-source*}}

You should see a file with the name "linux-source-2.6.20.tar.bz2" wich includes the packed kernel sources. You have to extract it, so do:

{{cmduser|sudo su}}
{{cmdroot|tar xvfj linux-source-2.6.20.tar.bz2}}

Now you have the kernel sources in the /usr/src/linux-source-2.6.20 directory. Take a look if there is a link from /usr/src/linux to an other kernel source directory (It's maybe there if you tried to compile a kernel some time before).

{{cmdroot|ls -l linux}}

If you see that linux is linked to an other source than your running kernel remove the link and create a new one with:

{{cmdroot|rm -r linux}}
{{cmdroot|ln -s /usr/src/linux-source-2.6.20 linux}}

Change to the source directory and patch the kernel with this:

{{cmdroot|cd /usr/src/linux}}
{{cmdroot|patch -p1 -l < /home/dirk/993-001.bin}}

The file "993-001.bin" is the kernel patch for the 2.6.20 and 2.6.21 kernels, I downloaded it here : [http://article.gmane.org/gmane.linux.drivers.hdaps.devel/993]

After the patchwork I did this :

{{cmdroot|make clean}}
{{cmdroot|cp /boot/config-2.6.20-16-generic .config}}
{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --append-to-version=.hdapscustom kernel_image --initrd binary

This would take its time, so go and clean up your house ;-)
After your house is clean you can do :

{{cmdroot|cd /usr/src}}
{{cmdroot|ls -l linux*.deb}}

You should see some newly builded Debian Pakage files. Install them with:

{{cmdroot|dpkg -i linux-headers-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-doc-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-image-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-manual-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}
{{cmdroot|dpkg -i linux-source-2.6.20.3-ubuntu.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}

After the installation you should reboot your computer, when Grub comes up make sure that you select your newly builded kernel.
Check it with:

{{cmduser|uname -r}}

You should see this "2.6.20.hdapscustom". But now you have the Problem, that you have to recompile the tp_smapi driver.

{{cmduser|cd tp_smapi-0.31}}
$ sudo make install HDAPS=1
{{cmduser|sudo modprobe tp_smapi}}
{{cmduser|sudo modprobe hdpas}}

After :

<pre>
$ dmesg | grep hdaps
</pre>

You should see something like this:

[ 893.752000] hdaps: initial mode latch is 0x05
[ 893.752000] hdaps: setting ec_rate=250, filter_order=2
[ 893.752000] hdaps: fake_data_mode set to 0
[ 893.756000] hdaps: device successfully initialized.
[ 893.756000] input: hdaps as /class/input/input10
[ 893.756000] hdaps: driver successfully loaded.

Now we are ready to try out the hdapsd Deamon which is included in the Gutsy repositories, if you are using Feisty you have to compile it yourself like described here: [http://www.thinkwiki.org/wiki/How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS].

{{cmdroot|sudo hdapsd -d sda -s 12 -a -v}}

Should show this:

[[Image:hdapsd.png]]

If you load it with :

{{cmdroot|sudo hdapsd -d sda -s 12 -a}}

You get nothing until you move your Thinkpad, then you see:

Fri Jul 13 12:30:42 2007: parking
Fri Jul 13 12:30:43 2007: un-parking
Fri Jul 13 12:30:44 2007: parking
Fri Jul 13 12:30:45 2007: un-parking

Now, after I have a working hdaps-deamon I want it to be started at boot time. Because I have upgraded to Gutsy and installed the hdapsd - Package I have a script called /etc/default/hdapsd. Here I have to change some things. HINT: Remember that you still need the /etc/init.d/hdapsd file if you try this on Feisty and maybe you have to do:

{{cmduser|sudo update-rc.d hdapsd defaults}}

to create the init links for the hdapsd init script. My links was already there. My /etc/default/hdapsd script now looks like this:

<pre>
# hdapsd default file

# start hdapsd at boottime?
START="yes"

# the name of the disk device that hdapsd should monitor.
#
# usually this is 'hda' the primary master or 'sda'
# on SATA ThinkPads.
DISK="sda"

# sensitivity
SENSITIVITY=12

# other options to pass to hdapsd.
# the -d $DISK, -s $SENSITIVITY, -b and -p $PIDFILE options are always passed.
OPTIONS="-a"

</pre>

Now I could use the gnome-hdaps-applet with the following comands:

{{cmduser|mkdir gnome-hdaps-applet}}
{{cmduser|cd gnome-hdaps-applet}}
{{cmduser|wget http://www.zen24593.zen.co.uk/hdaps/gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|tar -xzf gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|sudo apt-get install libpanel-applet2-dev}}
{{cmduser|gcc $(pkg-config --cflags --libs libpanelapplet-2.0) -o gnome-hdaps-applet gnome-hdaps-applet.c}}
{{cmduser|sudo cp gnome-hdaps-applet /usr/bin/}}
{{cmduser|sudo mkdir /usr/share/pixmaps/gnome-hdaps-applet/}}
{{cmduser|sudo cp *.png /usr/share/pixmaps/gnome-hdaps-applet/}}
$ sudo cp GNOME_HDAPS_StatusApplet.server /usr/lib/bonobo/servers/

Now after a restart of the Gnome Session I could find a "HDAPS Status" applet in the "Add to Panel" dialog. I added it, and when I move the Thinkpad it shows me the "Pause" [[Image:Hdaps-paused-small.png]] Symbol, otherwise it shows "Play" [[Image:Hdaps-running-small.png]].

So far so good !!! After I got this running I tried the same steps with the normal Gutsy Kernel (2.6.22-7-generic) on the same way, and it worked ! To my surprise with the same kernel patch.

The only Problem that I now have is that I cannot use restricted modules with my new kernels. Now I have to figure out how to compile restricted modules agains selfmade kernels.

== The Browser Buttons ==

I wanted to use the Browser Forward & Backward Buttons within Firefox. After the upgrade my Firefox had version 2.0.0.4

I did :

{{cmduser| sudo gedit ~/.Xmodmap}}

and added the following lines :

keycode 234 = F19

keycode 233 = F20

I saved and closed the file. HINT: You have to re-login to Gnome to get the .Xmodmap file active.

Then I did the things described in [http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work#Firefox How to get special keys to work].

For the Windows Key I added "keycode 115 = F13" to my .Xmodmap File, then I klicked on "System - Einstellungen - Tastenkombinationen"
sorry I don't know how it is called in English. And changed the Entry "Das Panelmenü anzeigen" to F13

== The Brightness Buttons ==

When I wanted to control the brightness, I was not able to change it with {{key|Fn}}{{key|End}}.

So I did the Workaround menitioned here [http://thinkwiki.org/wiki/Problem_with_LCD_brightness_buttons#Workaround for Fedora Core 6 Users].
After this I was able to change the brightness with {{key|Fn}}{{key|Home}} and {{key|Fn}}{{key|End}}, but I don't have the OSD anymore.

== The Fingerprint Reader ==

Do the steps which are described in [http://www.thinkwiki.org/wiki/Installing_Ubuntu_6.10_%28Edgy_Eft%29_on_a_ThinkPad_T60#The_Fingerprint_Reader Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60] until you get to the Point where Keithvassallo says:
"Phew. Now, to make applications actually use the fingerprint reader."

I have done the following things instead of his version:

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

Change the file as following:

<pre>
#%PAM-1.0
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
auth requisite pam_nologin.so
auth required pam_env.so
@include common-auth
@include common-account
session required pam_limits.so
@include common-session
@include common-password
</pre>

and:

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

Change this file as following:

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

With this changes you have the advantage, that you are now able to login to Gnome or KDE whitout entering your password. But if you cancel the "Fingerprint Login", you are still able to login whit your username/password combination.

After I was able to login to my desktop I was unsatisfied, because my Computer still wants to get passwords i.e. when I tried to open Synaptic or when I do any sudo actions.

So I tried to figure out how this sudo thing works. I did the following change to /etc/pam.d/sudo with:

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

<pre>
#%PAM-1.0

auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/ :0
password sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam :0
auth required pam_unix.so nillock_secure
@include common-account

</pre>

With this change I was able to open System Administration tasks with my fingerprint, but the ugly thing is, that you get no information to swipe your finger over the reader when you have switched to a console session with {{Key|Ctrl}}+{{Key|Alt}}+{{Key|F1}}. The fingerprint scanner software will appear at your running X session.

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-07-13T13:37:05Z

Dirk: /* The hdapsd - Deamon (IBM Active Disk Protection) */

File:Hdaps-running-small.png

2007-07-13T13:36:32Z

Dirk: gnome-hdaps running

gnome-hdaps running

File:Hdaps-paused-small.png

2007-07-13T13:35:05Z

Dirk: gnome-hdaps paused

gnome-hdaps paused

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-07-13T13:29:07Z

Dirk: /* The hdapsd - Deamon (IBM Active Disk Protection) */

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-07-13T13:22:52Z

Dirk: /* The hdapsd - Deamon (IBM Active Disk Protection) */

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-07-13T13:06:53Z

Dirk: /* The hdapsd - Deamon (IBM Active Disk Protection) */

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-07-13T11:40:32Z

Dirk: /* New Installation */

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-07-13T11:36:40Z

Dirk: /* My Thinkpad */

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-07-13T11:29:58Z

Dirk: /* The Fingerprint Reader */

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-07-13T11:29:13Z

Dirk: /* The Browser Buttons */

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-07-13T11:28:26Z

Dirk: /* The Upgrade to Gutsy Gibbon */

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-07-13T11:25:22Z

Dirk: /* The hdapsd - Deamon (IBM Active Disk Protection) */

File:Hdapsd.png

2007-07-13T11:22:04Z

Dirk: hdapsd Deamon working

hdapsd Deamon working

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-07-13T10:47:27Z

Dirk: /* The hdapsd - Deamon (IBM Active Disk Protection) */

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-07-13T10:42:32Z

Dirk: /* The hdapsd - Deamon (IBM Active Disk Protection) */

Installing Ubuntu (Gutsy Gibbon) 7.10 on a ThinkPad R60

2007-07-13T10:41:17Z

Dirk: /* The hdapsd - Deamon (IBM Active Disk Protection) */