Installing Slackware 11.0 on a ThinkPad R60

From ThinkWiki
Revision as of 08:02, 23 December 2006 by Lucidity (Talk | contribs) (HDAPS update)
Jump to: navigation, search


Slackware 11.0 requires a bit of work to get all of the major features of this notebook working. It may take some time, but don't be daunted, it can be done. This wiki is a work in progress (like all wiki's really) and i will try to make frequent updates until i have a fairly comprehensive guide, but i will especially focus on the issues that took some time (and head scratching) to resolve.

The R60 I am using has the following specifications:

  • Intel Core Duo T2400 (1.83GHz)
  • 512MB RAM
  • 60GB 5400rpm SATA HD
  • 15in 1400x1050 LCD
  • Intel 945GM/GMS/940GML Graphics Controller
  • Built in CDRW/DVD
  • Intel Corporation PRO/Wireless 3945ABG
  • Built in Modem
  • Broadcom Corporation NetXtreme BCM5751M Gigabit Ethernet
  • Built in fingerprint reader
  • IEEE 1394 (firewire)
  • 6c Li-Ion Battery


  • Intel "High-Def" audio
  • WiFi
  • Ethernet
  • Suspend-to-RAM (finally)
  • Dual core support (SMP)
  • DVD / CDRW with DMA support
  • Trackpoint
  • Synaptics touchpad (with scroll functionality)
  • The highest resolution in X: 1400x1050
  • Hard Drive Active Protection System (accelerometer)
  • (most everything else i don't mention below)

Not Yet Working

  • The special keys and key combos
  • The thumbprint reader (this is due to the fact that Slackware does not use PAM for authentication, not driver problems)
  • OpenGL hardware acceleration seems to not be working
  • Integrated security chip (getting errors trying to load kernel module tpm_atmel)


  • Hibernation (to disk), i normally only use Suspend to RAM, but i believe there are pages devoted to hibernation
  • Multi-headed VGA out
  • S-Video out
  • Firewire (probably works)
  • Modem

Before You Begin

Go into the BIOS and enable "compatibility mode" for the SATA controller

"compatibility mode" is necessary to be able to suspend-to-RAM later on

While you're there disable protection of the "recovery partition" if you know you won't be using Windows, and want to recover the extra 5GB (do at your own risk!) Make sure you have a basic understanding of lilo and how to recompile a kernel. Get the Slackware installation set (disks 1-3, but you may only need the first two)

I'll also assume that you are familiar with the basic steps of installing Slackware, if you're not, consult Slackware Installation


Begin by booting off disk 1 of Slackware 11.0. For the purposes of installation, Slackware uses the 2.4.33 kernel which will be installed by default. After the installation we'll be changing the kernel anyway, so it's okay to just install this default kernel for now.

The Hard Drive is /dev/sda not /dev/hda


I am using the kernel, others may work, but this is what i will be focusing on. For the [Active Protection System] to operate correctly, version 3 of the 2.6.18 kernel must be used at this time. I recommend getting it from instead of using the Slackware tarball. (There's no good reason, just my own personal preference) Before starting the configuration you will need two thing:

  1. The ieee80211 kernel patch needed for the wireless drivers which can be obtained here
  2. The default slackware configuration file for the kernel (which is in that kernel's tarball in the /extra branch) This is really only necessary if you're not a kernel pro, if you are, you don't need this.


The ieee80211 stack can be built as a modules without patching the kernel, but i have not been able to do this sucessfully, so i've found this the only way to get it to work.

Unpack the kernel and put it into the regular place (/usr/src) delete the linux link and relink it to the new kernel tree:

# rm /usr/src/linux

# ln -s /usr/src/linux- /usr/src/linux

Next unpack the ieee80211 stack, and patch it to the kernel source. From the ieee80211

# make patch_kernel

Next and most annoyingly, the files that were patched must be changed slightly for the modules to compile. In each .c file in the /usr/src/linux- directory the line

#include "compat.h"

must be changed to

#include <net/compat.h>
I did this completely by hand as i'm not very good at scripting, but if you know another way, more power to you

Next the patch for the Advanced Protections System (HDAPS) will be applied in the usual way. Download the patch from here.

This patch is VERY new as yet and should be considered unstable for the time being.

Copy the patch file to the /usr/src path (one directory below the kernel root.) Then apply it with:

$ patch -p0 <hdaps.patch (Your filename may differ.)

Kernel Config

Once you've completed this, copy the config-generic-smp- file from the Slackware kernel tarball to .config in the /usr/src/linux- directory. Now run:

$ make menuconfig

or your favorite configure method.

Do not optimize for Pentium-4 M or Pentium-M, these would work, but be less optimal

Parameters that must be given special attention:

  1. Optimize for "Pentium 4"
  2. Make sure SMP is enabled
  3. Enable all ACPI functions that apply to the thinkpad, especially ibm-acpi (Compile these into the kernel, do not make them modules)
  4. SATA options
  5. tg3 Gigabit ethernet
  6. TPM atmel (which is the security chip)

$ make bzImage

$ make modules

# make modules_install

Copy the bzImage (along with your new .config) to your /boot directory, and add it to /etc/lilo.conf Next add the following line to lilo.conf in the appropriate image:

append = "libata.atapi_enabled=1 combined_mode=libata"

This causes the SATA driver to pick up the DVD drive instead of the IDE driver. This is important because the IDE driver won't allow DMA to be enabled properly. This is one major difference from the other Thinkpad 60's which have a slightly different SATA controller. The DVD drive will be /dev/sr0

Finally run

# lilo


After you've booted your shiny new kernel, we'll start configuring the system:

Wireless Network

The first and most important thing to have working is your network connectivity. If you're using the gigabit ethernet card, this should already be working (so long as you compiled tg3). If you're like me, you need your wireless up as soon as possible.

The first thing to do is download the latest version of the ipw3945 drivers here.

Suspend-to-RAM functionallity

Currently the Suspend option in Klaptop from KDE works reliably. Also, as long as the ACPI drivers are compiled in the kernel (not as modules) you can use the Lid-close suspend in KDE even with the wifi connected. When you open the lid, everything should resume properly, and the wifi will automatically reconnect to the network you had previously been connected to.

Active Protection System

For the most part just follow the directions in How_to_protect_the_harddisk_through_APS. After you compile hdapsd:

$ gcc hdapsd-20060409.c (or whatever is the most recent version when you're doing this)

copy the hdapsd file to your /usr/local/sbin directory. Then add a command similar to:

# /usr/local/sbin/hdapsd -d sda -s 14 -a -b

to /etc/rc.d/rc.local

"14" refers to the sensitivity to shock. I found that 14 is about right for me. Your milage may differ.

If you're using kde i recommend getting khdapsmonitor which is a tray icon that shows that current status of the drive (more or less like the tray icon for the same purpose in WindoZe.) There are others for KDE such as khdapsmon, but this is now unmaintained. There are also others for different window managers such as gnome, but you're on your own there.

Synaptics Touchpad

Follow the directions for setting up the touchpad here. Although it isn't mentioned explicitly, the Trackpoint can be used in conjunction with the Touchpad, simply follow the directions as though you have an additional external mouse, but set it's device file to /dev/psmouse as well. Both devices go through the same interface, this way you can use the Trackpoint as the pointing device and the Touchpad as a scrolling device.

X11 Video

I'm using the pre-packaged i830 driver for XOrg, and i've found that it works nearly flawlessly in 16bpp mode, but in 24bpp more all kinds of (generally minor) screen corruptions occur. A program is necessary to enable the 1400x1050 resolution called 915resolution. This program writes the capability to the bios, at which point X is able to use it (providing that it's set up this way in your /etc/X11/xorg.conf file. I'm not using the external VGA nor S-Video at the moment, but fret not, this, as well as help setting up your xorg.conf file is available at Intel Graphics Media Accelerator 950.

External Sources