Difference between revisions of "IBM ThinkPad X60s"

From ArchWiki
Jump to: navigation, search
(Move unrelated 3g USB modem section to its own page)
m (With uswsusp: rm red link)
(16 intermediate revisions by 5 users not shown)
Line 1: Line 1:
[[Category:Laptops (English)]]
+
[[Category:IBM]]
Here are some of the key findings from my perspective.  Bear in mind the [[Beginners Guide]] is the bible.  I am focussed here on the X60s specific things I encountered.
+
{{Article summary start}}
 +
{{Article summary text|Installation instructions for the IBM ThinkPad X60s}}
 +
{{Article summary heading|Related articles}}
 +
{{Article summary wiki|IBM ThinkPad X60}}
 +
{{Article summary wiki|Lenovo Thinkpad X60 Tablet}}
 +
{{Article summary end}}
  
=Install from CD=
+
The IBM Thinkpad X60s is a small light laptop with a Core Duo or Core 2 Duo processor and [[Intel Graphics]]. It has no internal optical drive. You can see the specs at [http://www.thinkwiki.org/wiki/Category:X60s ThinkWiki], a wonderful resource with additional information.
Follow each menu item carefully, and do not skip any of them. Each one has place and a reason. A couple of key ones that have lasting effects:
+
  
1. prepare a partition strategy before you begin.  Arch has the smarts to give you separate partitions for boot, root, home and swap.  Some add others - i did not.  I used:
+
==Installation==
* boot - 128MB
+
First note that this laptop is available with two different processors.  
* Root - 20 Gb
+
* Swap - 2.5Gb (note I have since read that this is on the small side, but I have not seen any performance degradation and swap never gets used on this  machine so far. If I did it again I would go for 5 gig.  With Arch though you never do again, unless you miss the fun !
+
* home - the rest - in my case 70Gb
+
  
2. take special care in the menu item 'base system"Arch requires a network connection to continue the installation once the CD install is completed (the CD does not include Openoffice, Firefox, Gnome, XFCE for example). This can be either a wired ethernet connection which you can set up in the install CD menu (recommended) or you may wish to enable a wireless connection. For this read down the base list carefully, and select the following
+
* Core Duo
 +
:This processor requires the i686 (32-bit) version of Arch LinuxThe two RAM slots physically support 2x2GB=4GB RAM. However with a 32-bit kernel only up to ~3GB will be accessible. Unfortunately due to a chipset limitation, even compiling a kernel with the Physical Address Extension (PAE) option (CONFIG_HIGHMEM64G) [https://aur.archlinux.org/packages.php?ID=24469] will not allow access to more than 3GB.
 +
 
 +
* Core <b>2</b> Duo
 +
:This processor can run the x86_64 (64-bit) version of Arch Linux, and this is recommended in this case. The full 4GB RAM will be available with the standard Arch x86_64 kernel.
 +
 
 +
A basic Arch Linux installation will do just fine for almost everything. Select the i686 or x86_64
 +
version as indicated above. Install from a USB CD drive or a USB flash drive following the instructions in the [[Beginners Guide]].
 +
 
 +
It is easiest to do the initial installation with a wired ethernet connection which you can set up in the installation menu. In the base install package selection you can install the packages required for the wireless networking
 
  [*] wireless-tools
 
  [*] wireless-tools
 
  [*] iwlwifi-3945-ucode
 
  [*] iwlwifi-3945-ucode
So finish the base install, reboot, and you should be have a network hook present.
 
  
From terminal do iwconfig and look for something like wlan0 and a description that looks like your wireless card. Lets assume wlan0. Do this (no sudo required, because you are root at the moment - no users installed.)
+
Follow the [[Beginners Guide]] step by step to install sudo, add users, add to groups, video card driver, then install Xorg, and a desktop environment.
 +
 
 +
==Graphics==
 +
 
 +
See [[Intel Graphics]]. The required driver is xf86-video-intel.
  
ifconfig wlan0 up
+
==Ethernet==
iwconfig wlan0 essid "your_network_name" key [your key no brackets]
+
dhcpcd wlan0
+
  
Before you try to install anything you must update your system from the network to ensure all is up to date and all dependencies are correct. Arch is a rolling release model, therefore your install CD is out of date the moment you create it.
+
Gigabit ethernet works out of the box with the e1000e kernel module.
pacman -Syyu
+
  
The yy forces up update to local database register of installed programmes, and the u uprades your system.  Follow the prompts as required. 
+
==Wireless Networking==
  
Then follow the [[Beginners Guide]] step by step to install sudo, add users, add to groups, video card driver, then install Xorg, and a desktop environment.
+
See [[Wireless_Setup#iwl3945.2C_iwl4965_and_iwl5000-series]].
  
Once up and running, some additional things that took a little while:
+
==Special Keys==
  
=Suspend=
+
See http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work.
  
==With pm-utils==
+
==Suspend==
  
See the article on [[pm-utils]].
+
===With pm-utils===
  
==With uswsusp-fbsplash==
+
See the article on [[pm-utils]]. This works fine.
  
Install [[s2ram]]  (pacman -S uswsusp) and make these changes below.  This set of stuff is not well documented, but once I did this it was very smooth.   
+
===With uswsusp===
 +
{{Accuracy}}
 +
Install s2ram (pacman -S uswsusp) and make these changes below.  This set of stuff is not well documented, but once I did this it was very smooth.   
  
from http://aur.archlinux.org/packages/uswsusp-fbsplash/uswsusp-fbsplash/uswsusp.install  
+
from https://aur.archlinux.org/packages/uswsusp-fbsplash/uswsusp-fbsplash/uswsusp.install  
  
 
If suspend to ram doesn't work, edit the whitelist.c.diff
 
If suspend to ram doesn't work, edit the whitelist.c.diff
Line 62: Line 74:
 
sata, and/or scsi.
 
sata, and/or scsi.
 
Do not get this wrong.  Then rebuild the ramdisk with
 
Do not get this wrong.  Then rebuild the ramdisk with
  mkinitcpio -p kernel26
+
  mkinitcpio -p linux
  
 
Note, when I do s2ram --identify
 
Note, when I do s2ram --identify
Line 76: Line 88:
 
Next some file edits in policies.
 
Next some file edits in policies.
  
1.  As root edit {{Filename|/etc/acpi/actions/lm.lid.sh}}. Comment out everything, and add:
+
1.  As root edit {{ic|/etc/acpi/actions/lm.lid.sh}}. Comment out everything, and add:
  
 
<pre>
 
<pre>
Line 92: Line 104:
 
You should now have suspend working.
 
You should now have suspend working.
  
Another quirky thing is a hal error on shutdown preventing linux from turning the machine off.  From https://lists.ubuntu.com/archives/xubuntu-users/2009-June/001783.html I got this patch to {{Filename|/etc/PolicyKit/PolicyKit.conf}}
+
Another quirky thing is a hal error on shutdown preventing linux from turning the machine off.  From https://lists.ubuntu.com/archives/xubuntu-users/2009-June/001783.html I got this patch to {{ic|/etc/PolicyKit/PolicyKit.conf}}
  
 
<pre>
 
<pre>
Line 108: Line 120:
 
</pre>
 
</pre>
  
This file was blank but by adding the above, shutdown is now down by linux.  I need to study policykit and hal.  This is unclear, but my sense is that PolicyKit.conf is no longer used and a better fix is required in either [[/etc/acpi]] or [[/etc/hal.]]
+
This file was blank but by adding the above, shutdown is now down by linux.  I need to study policykit and hal.  This is unclear, but my sense is that PolicyKit.conf is no longer used and a better fix is required in either /etc/acpi or /etc/hal.

Revision as of 17:40, 11 June 2013

Template:Article summary start Template:Article summary text Template:Article summary heading Template:Article summary wiki Template:Article summary wiki Template:Article summary end

The IBM Thinkpad X60s is a small light laptop with a Core Duo or Core 2 Duo processor and Intel Graphics. It has no internal optical drive. You can see the specs at ThinkWiki, a wonderful resource with additional information.

Installation

First note that this laptop is available with two different processors.

  • Core Duo
This processor requires the i686 (32-bit) version of Arch Linux. The two RAM slots physically support 2x2GB=4GB RAM. However with a 32-bit kernel only up to ~3GB will be accessible. Unfortunately due to a chipset limitation, even compiling a kernel with the Physical Address Extension (PAE) option (CONFIG_HIGHMEM64G) [1] will not allow access to more than 3GB.
  • Core 2 Duo
This processor can run the x86_64 (64-bit) version of Arch Linux, and this is recommended in this case. The full 4GB RAM will be available with the standard Arch x86_64 kernel.

A basic Arch Linux installation will do just fine for almost everything. Select the i686 or x86_64 version as indicated above. Install from a USB CD drive or a USB flash drive following the instructions in the Beginners Guide.

It is easiest to do the initial installation with a wired ethernet connection which you can set up in the installation menu. In the base install package selection you can install the packages required for the wireless networking

[*] wireless-tools
[*] iwlwifi-3945-ucode

Follow the Beginners Guide step by step to install sudo, add users, add to groups, video card driver, then install Xorg, and a desktop environment.

Graphics

See Intel Graphics. The required driver is xf86-video-intel.

Ethernet

Gigabit ethernet works out of the box with the e1000e kernel module.

Wireless Networking

See Wireless_Setup#iwl3945.2C_iwl4965_and_iwl5000-series.

Special Keys

See http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work.

Suspend

With pm-utils

See the article on pm-utils. This works fine.

With uswsusp

Tango-inaccurate.pngThe factual accuracy of this article or section is disputed.Tango-inaccurate.png

Reason: please use the first argument of the template to provide a brief explanation. (Discuss in Talk:IBM ThinkPad X60s#)

Install s2ram (pacman -S uswsusp) and make these changes below. This set of stuff is not well documented, but once I did this it was very smooth.

from https://aur.archlinux.org/packages/uswsusp-fbsplash/uswsusp-fbsplash/uswsusp.install

If suspend to ram doesn't work, edit the whitelist.c.diff file to add your machine to the s2ram whitelist with the appropriate methods, then uncomment the line in the PKGBUILD where the patch is applied, eventually add the md5sum of the resulting patch and finally rebuild the package. Use 's2ram --identify' to identify your machine. Be sure to let the suspend-devel list know!

The new Software Suspend does not use kernel parameters to determine the suspend partition, instead it consults the /etc/suspend.conf file when booting. You MUST edit this file before you update your initrd.

You will need to update your mkinitcpio.conf file to include the hook uresume. Replace your 'resume' hook with 'uresume'. If you do not have a resume hook the uresume hook must go before filesystems but after ide, sata, and/or scsi. Do not get this wrong. Then rebuild the ramdisk with

mkinitcpio -p linux

Note, when I do s2ram --identify This machine can be identified by:

   sys_vendor   = "LENOVO"
   sys_product  = "1702HFU"
   sys_version  = "ThinkPad X60s"
   bios_version = "7BETD3WW (2.14 )"

See http://suspend.sf.net/s2ram-support.html for details

It is highly reassuring to see that your system is recognised. If you do not get recognised, there is a hal problem, and your earlier install is not complete.

Next some file edits in policies.

1. As root edit /etc/acpi/actions/lm.lid.sh. Comment out everything, and add:

if grep closed /proc/acpi/button/lid/LID/state >/dev/null ; then
    # if the lid is now closed, save the network state and suspend to ram
    netcfg all-suspend
    pm-suspend
else
    # if the lid is now open, restore the network state.
    # (if we are running, a wakeup has already occurred!)
    netcfg all-resume
fi

You should now have suspend working.

Another quirky thing is a hal error on shutdown preventing linux from turning the machine off. From https://lists.ubuntu.com/archives/xubuntu-users/2009-June/001783.html I got this patch to /etc/PolicyKit/PolicyKit.conf

<config version="0.1">
<match action="org.freedesktop.hal.storage.mount-removable">
<return result="yes"/>
</match>
<match action="org.freedesktop.hal.power-management.shutdown">
<return result="yes"/>
</match>
<match action="org.freedesktop.hal.power-management.reboot">
<return result="yes"/>
</match>
</config>

This file was blank but by adding the above, shutdown is now down by linux. I need to study policykit and hal. This is unclear, but my sense is that PolicyKit.conf is no longer used and a better fix is required in either /etc/acpi or /etc/hal.