Installing Debian on a ThinkPad G41

What to do with existing Windows partition?

If you want to keep the Windows XP partition you should seriously consider whether you want it to be VFAT or NTFS, because on the very first bootup of the system it will automatically run a command to convert from VFAT to NTFS. I recommend disabling the automatic conversion as per instructions here, i.e.:

Using Knoppix, mount the XP partition under /win:

# mkdir /win; mount /dev/hda1 /win

windows/system32/convert.exe:

# mv /win/windows/system32/convert.exe /win/windows/system32/convert_.ex_

windows/system32/autoconv.exe:

# mv /win/windows/system32/autoconv.exe /win/windows/system32/autoconv_.ex_

i386/convert.exe

# mv /win/i386/convert.exe /win/i386/convert_.ex_

i386/autoconv.exe

# mv /win/i386/autoconv.exe /win/i386/autoconv_.ex_

I like to keep the Windows XP partition for at least a little while to run it and see how much development effort IBM has spent to make the user experience under Windows a full-featured one, complete with many assistant applications and helper utilities rich in multi-media content and graphics - in sharp contrast with what they provide for Linux users.

IBM does not provide the rescue/recovery CD set with this model so I suggest before anything else that you immediately boot into Windows and create the set if you think you will ever want to re-image the drive. You could always order the set from IBM for $45. The set from IBM consists of a "Rescue and Recovery" CD plus 6 "Product Recovery" CD's which contain the actual image that gets written to the hard drive.

After creating the recovery CD set I recommend going into the BIOS and setting the "IBM Predesktop Area" in the BIOS under "Security" to "Disabled". This enables you to remove the “PreDesktop Environment” area, which is the second partition and takes over 3 GB of disk space. The Predesktop Environment is not very useful unless you want to have the feature of being able to re-image your disk and re-install Windows from scratch. If you're really concerned that you will somehow badly screw up your Windows environment - if you ever use it :-) - you can always create restore points without wasting precious disk space on the Predesktop Environment.

Notes on the model used in this setup

This info is for setting up Debian on a G41 with the following features:

• Processor: Mobile Intel Pentium 4 Processor 548 with HT Technology
• Graphics: NVIDIA GeForce FX Go5200 (nVidia Corporation NV34M)
• Display: 1400x1050 SXGA+
• Wireless: ThinkPad 11b/g Wi-Fi Wireless (Atheros Communications, Inc. AR5212 802.11abg)
• Ethernet: Integrated Gigabit Ethernet (Broadcom Corporation NetXtreme BCM5705M_2)
• Sound: SoundMAX (Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller)

If your model does not have these features, then some or most of this information might not apply.

Disk Preparation and Partitioning

Next I ran Knoppix again and used the QTparted graphical disk partitioning tool to alter the partition layout of the drive. I deleted the recovery/predesktop partition (partition 2) and shrunk the XP partition (partition 1 to 8 GB. QTParted will correctly resize the XP partition regardless of whether it is VFAT or NTFS. Finally, I created a 2300 MB swap partition as the second partition and used the remainder of the disk (partition 3) as one large XFS filesystem for Linux. The reason I chose the high value for the swap partition size was so that it can accommodate suspend to disk, which requires a swap partition larger than the amount of installed RAM, and allowing for the maximum 2GB of RAM to be installed.

Debian installation

After this I installed Debian using an official i386 Debian minimal bootable CD netinst image obtained from http://www.us.debian.org/CD/netinst/

When the CD booted I pressed the F3 key which gave instructions to type "expert26" at the boot prompt in order to install in expert mode using a more recent 2.6 Linux kernel. I accepted the defaults for all questions except that when it asked about partitioning the disk I chose the option to "manually edit the partition table". This is because I already partitioned the disk with QTParted above and created the swap and XFS filesystems I plan to use. So in the manual partition setup section I simply told it to use hda2 as swap and to use hda3 as xfs, assign the mount point "/" to it, and to format the filesystem. Once this is done the rest is simple. When it asked about making Linux bootable directly from the hard disk, it is important to NOT chose the Grub boot loader since the version included with the installer has a serious problem dealing with XFS filesystems. Choose Lilo instead and everything will be fine.

After the first reboot during the install it asks to set up apt sources. I chose to use http and selected a local mirror in my country. It then asked if I want to choose packages to install and I said no. My philosophy is to install Debian with the minimal amount of stuff, get it working, and then later on install any other applications I want. Also, if you plan on dist-upgrading from stable to testing or Sid then it is easier to do with only a minimal installation.

Installing a few important packages

Here are a few important packages that it is good to install right away:

# apt-get install less vim

# apt-get remove --purge nvi

vim is a much better than nvi. Less is much better than more which is installed by default.

Building a Linux kernel with Software Suspend 2 Support

As of this writing Software Suspend 2 (swsusp2) is the only working implementation of power-saving functionality available. ACPI sleep and standby modes and the in-kernel software suspend do not work with this model. swsusp2 provides a patch for the kernel. Which version of kernel you use is dependent upon which version of swsusp2 you wish to use. There is a development version which has the latest-and-greatest features and bugfixes, and the stable version which is slightly older. For this article I chose to use the latest-and-greatest which was version 2.2-rc8 which requires Linux kernel version 2.6.14-rc3. This is a “release candidate” kernel which is available from the usual kernel repositories under the /testing subdirectory.

Preparing for the kernel build

There are a few packages that must be installed prior to compiling a kernel:

# apt-get install ncftp build-essential bin86 libncurses-dev bzip2

Getting the kernel source

Use an ftp client like ncftp to retrieve linux-2.6.14-rc3.tar.bz2 from ftp://ftp.kernel.org/pub/linux/kernel/v2.6/testing .

# cd /usr/src

# ncftp

ncftp> open ftp.kernel.org

ncftp> cd pub/linux/kernel/v2.6

ncftp> get linux-2.6.14-rc3.tar.bz2

ncftp> bye

Unpack the kernel, configure, and compile

# tar -xjf linux-2.6.14-rc3.tar.bz2

At this point I prefer to rename the kernel source tree so that if at some point in the future I wish to build another kernel version, I can do so in a separate tree.

# mv linux-2.6.14-rc3 linux-2.6.13-rc3-uni

I chose to append the name of the kernel with “-uni” as a shorthand for “uniprocessor”. This Pentium 4 CPU supports hyperthreading which when enabled causes the single CPU to appear as 2 separate CPUs which makes the system a Symmetric-Multiprocessing (SMP) system. However, currently there are issues with swsusp2 and SMP so we will leave hypterthreading disabled in the BIOS settings (under “Power”) so that the CPU appears as a uniprocessor, and then build the kernel for a uniprocessor. If you want to experiment later, you can build another kernel version linux-2.6.13-rc3-smp which has Symmetric-Multiprocessing support enabled in the kernel. If you do this, you would set the maximum number of CPU's to “2” in the kernel config and be sure to enable hyperthreading in the BIOS settings under the “Power” section. (NOTE: If you do in fact build an -smp kernel and accidently boot the machine with hyperthreading disabled using a kernel compiled without SMP support, or vice-versa, you run the -uni kernel but have hyperthreading enabled in the kernel, there will probably be a loss of performance but it should not harm your system.)

Hint:

A note on Hyperthreading/SMP vs. non-Hyperthreading/Uniprocessor

One further note about using hyperthreading or not: In order to find out if running the machine without hyperthreading and an SMP kernel was any slower than with hyperthreading/SMP, I ran a test in which I timed a complete kernel compilation. The compile times were identical in both cases. If you check /proc/cpuinfo you will see when hyperthreading is enabled (and you are running an SMP-enabled kernel) that two processors will show up each with a bogomips value of about 3320. With hyperthreading disabled and a uniprocessor kernel, only one CPU will appear in /proc/cpuinfo with a bogomips value of around 6640. This is not to say that there are not instances in which hyperthreading/SMP might provide better performance, but that in one fairly typical task it made no difference whatsoever.

Next, edit the Makefile in the top level of the kernel source and change the line EXTRAVERSION so that it reads: EXTRAVERSION = -rc3-uni

Then we are creating this symlink because when we compile some external kernel modules later they often prefer to have the current kernel source in /usr/src/linux which is a convention:

# ln -s linux-2.6.14-rc3 linux

And configure the kernel:

# cd linux

# make menuconfig

Prior to configuring the kernel it is important to have an inventory of the components in your system. Here is a list of the most important components in terms of how Linux sees them. You will need this list during menuconfig in order to enable support for these components.

• Intel Pentium 4 PC-compatible processor. It capable of Hyperthreading however if we are leaving Hypterthreading support off in the BIOS then we also do NOT want to choose Symmetric Multiprocessing support (SMP) in the kernel
• ACPI interface supporting CPU frequency scaling
• PCI bridge
• ISA bridge
• CardBus yenta-compatible PC Card controller
• PC-style parallel port
• Intel Ultra ATA ICH4 Storage Controller (IDE interface)
• Broadcom Tigon3 1000 Mbit ethernet controller
• PS/2 Mouse interface
• 8250/16550 compatible serial port
• Intel 855GM AGP chipset
• Intel 82801 (ICH) SMBus (I2C)
• VESA 2.0 compatible graphics chipset
• Intel AC97 Audio controller
• Intel MC97 Modem
• Intel UHCI USB controller
• Intel EHCI USB 2.0 controller

There are a few important things in the kernel config to be aware of.

• For this kernel, do not enable Symmetric-Multiprocessing support.
• Power Management/ACPI: I chose to not enable IBM laptop extras (ibm_acpi) in order to build a newer version later
• under ATA support be sure to select Intel PIIXn chipsets support
• You must enable Direct Rendering Manager support (without selecting any of the driver modules, since we will build our own later)
• In the Graphics section select VESA VGA graphics support but DO NOT select nVidia Framebuffer Support as it interferes with the nvidia DRM driver we will install below

# cp .config ../dot-config-2.6.14-rc3-uni #good to save a copy

# make

# make modules_install

# cp arch/i386/boot/bzImage /boot/vmlinuz-2.6.14-rc3-uni

# cp System.map /boot/System.map-2.6.14-rc3-uni

# vi /etc/lilo.conf

#lilo stanza for image from lilo.conf
image=/boot/vmlinuz-2.6.14-rc3-uni
# set the resume2 partition to whatever your swap partition is below:
append="resume2=swap:/dev/hda2" #needed for swsusp2 to work
label=2.6.14-rc3-uni
# the following sets the console to framebuffer mode 1280x1024
# you must have “VESA VGA graphics support” selected
# in the kernel under Device Drivers -> Graphics support
# otherwise set to “1” or “normal”
vga=0x31B 
read-only

Then run # lilo to install it to the MBR. Now it should be possible to boot into the new 2.6.14-rc3-uni kernel.

Setting up graphics

First, it is necessary to install the minimal essential components necessary to get the graphical environment working:

# apt-get install x-window-system-core

Setting up the proprietary nvidia driver (optional)

The easiest way to install the proprietary nvidia driver this is with Debian's module-assistant utility:

# apt-get install module-assistant

# m-a prepare

# m-a a-i nvidia

# apt-get install nvidia-glx nvidia-settings

# echo nvidia >> /etc/modules

# modprobe nvidia

Configuring the X server

# dpkg-reconfigure xserver-xfree86

If you are using Sid, then use :# dpkg-reconfigure xserver-xorg.

This will ask a lot of questions about X setup. Here are options I selected:

• allow it to attempt to autodetect video hardware. It will automatically select the "nv" driver, which is the one we want if we are going to use swsusp2. Unfortunately this driver does not support OpenGL so you have to choose between 3D graphics acceleration or the ability to suspend-to-disk. If however you decide you want the nvidia driver scroll down one and select it.
• leave video RAM setting blank. X server will autodetect it
• do NOT use kernel framebuffer interface
• for keyboard layout do not select default "us" value, but replace with "intl" (this is better because it also supports multi-key on the right-alt key)
• XKB rule set accept default value
• for keyboard model replace "pc105" with "pc102"
• attempt mouse autodetection and use the default /dev/input/mouse
• Mouse protocol: select ImPS/2 (should be default)
• yes to emulate 3 button mouse
• yes to enable scroll events
• accept all modules (default)
• under display setup, select only mode 1400x1050
• under choose method, select medium
• select 1400x1050 @ 75Hz
• select default color depth of 24 (you can select 16 which is slightly lower, and might give slightly better performance)

At this point you should be able to start X from the command line with the startx command. But it will not look very appealing. Install a window manager/desktop environment, e.g.

# apt-get install openbox obconf openbox-themes fbpanel

And some fonts to go along with it:

# apt-get install ttf-dustin ttf-freefont ttf-opensymbol ttf-thryomanes \

ttf-xfree86-nonfree xfonts-100dpi xfonts-100dpi-transcoded xfonts-75dpi \ xfonts-75dpi-transcoded xfonts-artwiz xfonts-base xfonts-base-transcoded \ xfonts-biznet-100dpi xfonts-biznet-75dpi xfonts-biznet-base xfonts-scalable \ defoma fontconfig

For the fontconfig debconf question I chose to use Freetype

Then create a .xsession file in your home directory to invoke openbox/fbpanel when you run "startx":

  #!/bin/sh
  # ~/.xsession: stuff to do when starting X
  #
  #set the background
  xsetroot -solid DarkSlateGrey 
  # increase the mouse sensitivity a bit, good for Trackpoints
  xset m 4 1
  #run fbpanel               
  fbpanel &    
  # run openbox, our window manager                               
  exec openbox                          

Setting up the Wireless driver

lspci listing should show the Atheros Communications 802.11abg adapter. Here is how to get it working using the madwifi driver:

# apt-get install cvs

# cd /usr/local/src

# cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/madwifi co madwifi

# cd madwifi

# make && make install

# modprobe ath_pci

# apt-get install wireless-tools dhcp3-client

See /usr/local/src/madwifi/README for useful information about the configuring the interface.

Before running any of the wireless utilities and configuring it you may need to bring the interface up first:

# ifconfig ath0 up

The easiest way to configure the interface is to install kwifimanager

# apt-get install kwifimanager

Once I scanned and had a list of access points (using :# iwlist ath0 scan) basically all I had to do was go into the “Settings” menu and select “Configuration Editor”. In there under “Network Name” enter the SSID of an access point, which is the name of the wireless network (not the BSSID which is the long hex address). Make sure that “ath0” is selected in the “Settings apply to interface” text box (click “Autodetect” button and it should show up). After activating the config it should associate with the AP. Then run dhclient on the interface to obtain an IP address from the access point:

# dhclient ath0

Setting up sound

The ALSA sound module is snd_intel8x0m

# apt-get install alsa-base alsa-utils alsamixergui

# alsaconfig

Power management

According to power/video.txt in the Linux kernel source documentation ACPI suspend-to-RAM mode (a.k.a. "Standby" or "Sleep") does not and can not work with Hyperthreading CPUs:

"S3 has absolutely no chance of working with SMP/HT. Be sure it to turn it off before testing (swsusp should work ok, OTOH)."

In order to get Software Suspend 2 fully working you also need to download and install the hibernate-script from the Software Suspend 2 site. This will install a shell script called "hibernate" in /usr/local/sbin and also a configuration directory /etc/hibernate. Once installed, if your kernel was configured correctly, you should be able to run the command # hibernate. The system will save the current contents of RAM to the swap partiton (make sure you have set the correct resume2=swap: parameter in your bootloader config or else it will not work). The next time you restart the system it will detect that the swap partition contains the suspended information and automatically restore the system. If there is a problem with swsusp2 it may freeze while resuming. The only time that I personally experienced a resume problem was when I was running the # top command in a gnome-terminal during a suspend operation.

ibm-acpi

It is probably worth installing the latest ibm-acpi, which adds functionality for Fn key combinations, allows setting of threshold temperatures for fans, and more. As of this writing much of this functionality is untested or unknown on the G41. Still it doesn't hurt to install it:

Go to the IBM-acpi driver website and download the latest driver (0.11 as of this writing) into /usr/local/src.

# tar -xzf ibm-acpi-0.11.tar.gz

# cd ibm-acpi-0.11

# make

# make install

# modprobe ibm_acpi

# echo "ibm_acpi" >> /etc/modules

You can see the currently installed version with:

# cat /proc/acpi/ibm/driver

Further stuff

tpb is a neat program that enables the on-screen display for certain keys functions such as the volume control and LCD brightness levels. # apt-get install tpb and then edit /etc/tpbrc.

TODO

This page still needs a section on configuring the modem. The last time I tested on another Thinkpad model, neither the Open-Source nor the proprietary driver for the "slmodem" Intel AC'97 Modem Controller seemed to work to well. Fortunately I have a miniPCI card with a true Lucent WinModem which uses the "alk" driver available here. If you are planning to use the modem a lot it may be worth the $5 to pick one of these up on Ebay as it is much easier to configure and works quite reliably under Linux.