ThinkWiki - User contributions [en]

Installing Ubuntu 11.04 (Natty Narwhal) on a ThinkPad X220

2013-11-03T15:35:48Z

MarkStosberg: accessories purchased a particular person are not of general interest.

[[User:Jdthood|I]] installed Ubuntu 11.04 (Natty Narwhal) on a ThinkPad {{X220}}, model 42902GW.

I have since upgraded to Ubuntu 11.10 (Oneiric Ocelot) and have updated some of the information below accordingly.

== Netboot ==
As a source of network installation files I made use of another GNU/Linux computer on my home LAN
which is connected to the Internet through a familiar ADSL-modem/gateway/router/caching nameserver/DHCP server (call it "the gateway") at address 172.19.3.1.
The gateway's DHCP server issues leases in the range 172.19.3.2 to 172.19.3.100.

First I set up the "source" machine, in my case one which already also had Ubuntu 11.04 installed.
It has address 172.19.3.7 (assigned to it by the gateway's DHCP server).
For the X220 to boot from it the machine needs to run a DHCP server and a TFTP server.
The DHCP server serves only this special purpose since, as I mentioned, the gateway is the network's main DHCP server.
The source's DHCP server must be so configured that it doesn't conflict with the existing DHCP server.

Install the <tt>isc-dhcp-server</tt> package and edit <tt>/etc/dhcp/dhcpd.conf</tt> using the following as a model.
I am not sure that every line is needed, but this worked for me.
<pre>
ddns-update-style none;
option domain-name-servers 172.19.3.1; # This is the address of my gateway
option routers 172.19.3.1; # This is the address of my gateway
option subnet-mask 255.255.0.0; # This is the netmask of my home network
default-lease-time 600;
max-lease-time 7200;
allow booting;
allow bootp;

subnet 172.19.3.0 netmask 255.255.255.0 {
range 172.19.3.220 172.19.3.229; # This is a range separate from the one used by the gateway and includes the address below
}

group {
next-server 172.19.3.7; # This is the address of the "source"
host trawsfynydd { # 'trawsfynydd' is the name I chose for my X220
hardware ethernet f0:de:f1:6b:22:bf; # This is the Ethernet address of the X220
fixed-address 172.19.3.220; # This is an address in the range as defined above
filename "/pxelinux.0";
}
}
</pre>

Now install the <tt>tftpd-hpa</tt> package, download the network installation tarball and untar it into the location whence <tt>tftpd</tt> serves files.

<pre>
$ cd /tmp
$ wget http://archive.ubuntu.com/ubuntu/dists/natty/main/installer-amd64/current/images/netboot/netboot.tar.gz
$ cd /var/lib/tftpboot
$ sudo tar zxf /tmp/netboot.tar.gz
</pre>

Second set up the X220 for PXE (Pre-boot eXecution Environment).
* Switch on the X220 and press F1. ThinkPad Setup starts.
* Set Config | Network | Ethernet LAN Option ROM to "Enabled".
* Select Startup | Boot; select "PCI LAN IBA GE Slot..." and use the [+] key to move it to the top of the boot priority order
* Press F10 to save and exit.

Voilà, the X220 boots the Ubuntu installer.

== Installation ==

I won't describe the Ubuntu installer.
I'll just mention some little problems I had.

''First'', when it came time to resize the existing (ntfs) partition the partitioner asked what size I would like for "this partition". Did it mean the to-be-resized ntfs partition or the new ext4 partition?

Turns out it meant: the to-be-resized ntfs partition, so the suggested "max" selection was the opposite of what I wanted.

''Second'', when I selected (only) the "Ubuntu desktop" task the installation reported failure without explaining what had gone wrong.

I de-selected all tasks and the installation succeeded.

''Third'', after reboot the screen came up black.

I pressed CTRL-ALT-F1 to get the system console so I could log in.

After logging in I ran <tt>tasksel</tt> and installed "Ubuntu desktop" and this time no failure was reported.

== Information ==

=== BIOS ===

Originally:
<pre>
BIOS Version: 8DET46WW (1.16)
</pre>
From Windows 7 I ran Lenovo ThinkVantage Tools to upgrade the BIOS. Now:
<pre>
BIOS Version: 8DET51WW (1.21)
</pre>

=== dmidecode ===
<pre>
# dmidecode -s system-manufacturer
LENOVO
# dmidecode -s system-product-name
42902WG
# dmidecode -s system-version
ThinkPad X220
</pre>
=== /proc/cpuinfo ===
<pre>
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 42
model name : Intel(R) Core(TM) i5-2540M CPU @ 2.60GHz
stepping : 7
cpu MHz : 800.000
cache size : 3072 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 x2apic popcnt aes xsave avx lahf_lm ida arat epb xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid
bogomips : 5182.27
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
</pre>

=== lspci ===
<pre>
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series Chipset Family MEI Controller #1 (rev 04)
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04)
00:1a.0 USB Controller: Intel Corporation 6 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 6 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 6 Series Chipset Family PCI Express Root Port 1 (rev b4)
00:1c.1 PCI bridge: Intel Corporation 6 Series Chipset Family PCI Express Root Port 2 (rev b4)
00:1c.3 PCI bridge: Intel Corporation 6 Series Chipset Family PCI Express Root Port 4 (rev b4)
00:1c.4 PCI bridge: Intel Corporation 6 Series Chipset Family PCI Express Root Port 5 (rev b4)
00:1d.0 USB Controller: Intel Corporation 6 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation 6 Series Chipset Family LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 6 Series Chipset Family 6 port SATA AHCI Controller (rev 04)
00:1f.3 SMBus: Intel Corporation 6 Series Chipset Family SMBus Controller (rev 04)
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205 (rev 34)
0d:00.0 System peripheral: Ricoh Co Ltd Device e823 (rev 04)
</pre>

=== lsusb ===
<pre>
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 006: ID 04f2:b217 Chicony Electronics Co., Ltd
Bus 001 Device 005: ID 0a5c:217f Broadcom Corp. Bluetooth Controller
Bus 001 Device 004: ID 147e:2016 Upek Biometric Touchchip/Touchstrip Fingerprint Sensor
Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
</pre>

=== Key table ===
This table was prepared ''before'' keys were remapped as discussed elsewhere on this page.

References:
* [https://wiki.ubuntu.com/Hotkeys Hotkey architecture in Ubuntu]
* [https://wiki.ubuntu.com/Hotkeys/Troubleshooting Hotkey troubleshooting instructions]
* <tt>/usr/include/linux/input.h</tt> -- list of Linux key codes
* [[Default meanings of special keys]]

{| border="1" cellspacing="0" cellpadding="2"
! Key combination !! Extra function symbol !! ACPI event<br>(<tt>acpi_listen</tt>) !! Scan code<br>(<tt>showkey -s</tt>)<br><i>(hex)</i> !! Linux key code<br>(<tt>showkey -k</tt>) !! Input event<br>(<tt>input-events</tt>) !! ... on input device(*) !! X KeyCode<br>(<tt>xev</tt>) !! Keyboard Shortcuts name
|-
| {{key|📢⃥}} (loudspeaker icon with stroke) || || (none) || down: e0 20<br>up: e0 a0 || 113 || KEY_MIN_INTERESTING (0x71) || 3 || 121 || XF86AudioMute
|-
| {{key|−📢}} (minus sign, loudspeaker icon) || || (none) || down: e0 2e<br>up: e0 ae || 114 || KEY_VOLUMEDOWN (0x72) || 3 ||122 || XF86AudioLowerVolume
|-
| {{key|📢+}} (loudspeaker icon, plus sign) || || (none) || down: e0 30<br>up: e0 b0 || 115 || KEY_VOLUMEUP (0x73) || 3 || 123 || XF86AudioRaiseVolume
|-
| {{key|🎤⃥}} (microphone icon with stroke) || || ibm/hotkey HKEY 00000080 0000101b || (none) || 240 (rop) || KEY_UNKNOWN (0xf0) || 6 || 248 || "∅" (sic)
|-
| {{ibmkey|ThinkVantage|#495988}} || || ibm/hotkey HKEY 00000080 00001018 || down: e0 1f e0 9f || 148 (rop) || KEY_PROG1 (0x94) || 6 || 156 || XF86Launch1
|-
| {{ibmkey|Fn|#494949}} || || (none) || up: e0 63 e0 e3 || 143 || KEY_WAKEUP (0x8f) || 3 || 151 || XF86WakeUp
|-
| {{ibmkey|Fn|#494949}}-{{ibmkey|F1|#494949}} || || ibm/hotkey HKEY 00000080 00001001 || (none) || 466 (rop) || KEY_FN_F1 (0x1d2) || 6 || (none) || (none)
|-
| {{ibmkey|Fn|#494949}}-{{ibmkey|F2|#494949}} || 🔒 (padlock symbol) || ibm/hotkey HKEY 00000080 00001002 || down: e0 12 e0 92 || 152 (rop) || KEY_SCREENLOCK (0x98) || 6 || 160 || XF86ScreenSaver
|-
| {{ibmkey|Fn|#494949}}-{{ibmkey|F3|#494949}} || 🔋 (battery symbol) || ibm/hotkey HKEY 00000080 00001003 || down: e0 71 e0 f1 || 236 (rop) || KEY_BATTERY (0xec) || 6 || 244 || XF86Battery
|-
| {{ibmkey|Fn|#494949}}-{{ibmkey|F4|#494949}} || ☾ || ibm/hotkey HKEY 00000080 00001004 || down: e0 5f e0 df<br>(but sometimes nothing) || 142 (rop) || KEY_SLEEP (0x8e) || 6 || 150 || XF86Sleep
|-
| {{ibmkey|Fn|#494949}}-{{ibmkey|F5|#494949}} || ⸨💻⸩ (radiating computer symbol) || ibm/hotkey HKEY 00000080 00001005 || down: e0 73 e0 f3 || 238 (rop) || KEY_WLAN (0xee) || 6 || 246 || XF86WLAN
|-
| {{ibmkey|Fn|#494949}}-{{ibmkey|F6|#494949}} || (camera, headset) || ibm/hotkey HKEY 00000080 00001006 || down: e0 3b e0 bb || 212 (rop) || KEY_CAMERA (0xd4) || 6 || 220 || XF86WebCam
|-
| {{ibmkey|Fn|#494949}}-{{ibmkey|F7|#494949}} || 💻⎚ (computer symbol, screen symbol) || ibm/hotkey HKEY 00000080 00001007 || down: e0 56 e0 d6 || 227 (rop) || KEY_SWITCHVIDEOMODE (0xe3) || 6 || 235 || XF86Display
|-
| {{ibmkey|Fn|#494949}}-{{ibmkey|F8|#494949}} || (trackpoint symbol, vertical bar, trackpad symbol) || ibm/hotkey HKEY 00000080 00001008 || down: e0 74 e0 f4 || 191 (rop) || KEY_F21 (0xbf) || 6 || 199 || XF86TouchpadToggle
|-
| {{ibmkey|Fn|#494949}}-{{ibmkey|F9|#494949}} || || ibm/hotkey HKEY 00000080 00001009 || down: 6f ef || 194 (rop) || KEY_F24 (0xc2) || 6 || 202 || "Ê" (sic)
|-
| {{ibmkey|Fn|#494949}}-{{ibmkey|F10|#494949}} || || (none) || (none) || || (none) || || (none) || (none)
|-
| {{ibmkey|Fn|#494949}}-{{ibmkey|F11|#494949}} || || ibm/hotkey HKEY 00000080 0000100b || (none) || 476 (rop) || KEY_FN_F11 (0x1dc) || 6 || (none) || (none)
|-
| {{ibmkey|Fn|#494949}}-{{ibmkey|F12|#494949}} || 💻 ▶❍ (computer symbol, right arrowhead, diskpack symbol) || ibm/hotkey HKEY 00000080 0000100c || down: e0 25 e0 a5<br>(but sometimes nothing) || 205 (rop) || KEY_SUSPEND (0xcd) || 6 || 213 || XF86Suspend
|-
| {{ibmkey|Fn|#494949}}-{{ibmkey|Home|#494949}} || ☀▴ || ibm/hotkey HKEY 00000080 00001010 and video LCD0 00000086 00000000 || down: e0 54 e0 d4 e0 54 e0 d4 || 225 (double) (rop) || KEY_BRIGHTNESSUP (0xe1) || 4, 6 || 233 || XF86MonBrightnessUp
|-
| {{ibmkey|Fn|#494949}}-{{ibmkey|End|#494949}} || ☀▾ || ibm/hotkey HKEY 00000080 00001011 and video LCD0 00000087 00000000 || down: e0 4c e0 cc e0 4c e0 cc || 224 (double) (rop) || KEY_BRIGHTNESSDOWN (0xe0) || 4, 6 || 232 || XF86MonBrightnessDown
|-
| {{ibmkey|Fn|#494949}}-{{ibmkey|PgUp|#494949}} || (illuminating overhead lamp symbol) || (none) || (none) || (none) || (none) || (none) || (none) || (none)
|-
| {{ibmkey|Fn|#494949}}-{{ibmkey|Space|#494949}} || [🔍+] (screen with magnifying glass symbol and plus sign, i.e., "zoom" symbol) || ibm/hotkey HKEY 00000080 00001014 || (none) || 372 (rop) || KEY_ZOOM (0x174) || 6 || (none) || (none)
|-
| {{ibmkey|Fn|#494949}}-{{ibmkey|→|#494949}} || ⏭ (barred right arrowhead, i.e., "next" symbol) || (none) || down: e0 19<br>up: e0 99 || 163 || KEY_NEXTSONG (0xa3) || 3 || 171 || XF86AudioNext
|-
| {{ibmkey|Fn|#494949}}-{{ibmkey|↓|#494949}} || ⏯ (right arrowhead, double bar, i.e., "play/pause" symbol) || (none) || down: e0 22<br>up: e0 a2 || 164 || KEY_PLAYPAUSE (0xa4) || 3 || 172 || XF86AudioPlay
|-
| {{ibmkey|Fn|#494949}}-{{ibmkey|←|#494949}} || ⏮ (barred left arrowhead, i.e., "prev" symbol) || (none) || down: e0 10<br>up: e0 90 || 165 || KEY_PREVIOUSSONG (0xa5) || 3 || 173 || XF86AudioPrev
|-
| {{ibmkey|Fn|#494949}}-{{ibmkey|↑|#494949}} || ∎ ("stop play" symbol) || (none) || down: e0 24<br>up: e0 a4 || 166 || KEY_STOPCD (0xa6) || 3 || 174 || XF86AudioStop
|-
| {{ibmkey|◂ ⎗|#494949}} (left arrowhead, page icon) || || (none) || down: e0 6a<br>up: e0 ea || 158 || KEY_BACK (0x9e) || 3 || 166 || XF86Back
|-
| {{ibmkey|⎘ ▸|#494949}} (page icon, right arrowhead) || || (none) || down: e0 69<br>up: e0 e9 || 159 || KEY_FORWARD (0x9f) || 3 || 167 || XF86Forward
|}

In the Linux key code column, "rop" means "release on press", i.e., the release event is generated at the same time as the press event.

The button on the UltraBase doesn't seem to generate any events visible to userspace.

Input device numbers and types as reported by <tt>lsinput</tt>:
{| border="1" cellspacing="0" cellpadding="2"
|+ (*) /dev/input/event<i>n</i>
! n !! name
|-
| 0 || "Lid Switch"
|-
| 1 || "Sleep Button"
|-
| 2 || "Power Button"
|-
| 3 || "AT Translated Set @ keyboard"
|-
| 4 || "Video Bus"
|-
| 5 || "Integrated Camera"
|-
| 6 || "ThinkPad Extra Buttons"
|-
| 7 || "SynPS/2 Synaptics TouchPad"
|-
| 8 || "TPPS/2 IBM TrackPoint"
|}

Hotkey mask when the above table was compiled:
<pre>
$ cat /sys/devices/platform/thinkpad_acpi/hotkey_mask
0x078dffff
$ cat /sys/devices/platform/thinkpad_acpi/hotkey_all_mask
0x07ffffff
$ cat /sys/devices/platform/thinkpad_acpi/hotkey_recommended_mask
0x078dffff
$ cat /sys/devices/platform/thinkpad_acpi/hotkey_report_mode
1
</pre>

== Configuration and solved problems ==

=== Fingerprint reader ===
See [[How to enable integrated fingerprint reader with fprint|how to enable the integrated fingerprint reader with fprint]].

=== Fix for [https://bugs.freedesktop.org/show_bug.cgi?id=11227 hotkey shortcomings] ===
(Updated November 2011 for Oneiric.)

By default the "zoom" (Fn-Space) and "microphone-mute" (button next to the ThinkVantage button) hotkeys do nothing.

'''Zoom''': The <tt>thinkpad-acpi</tt> module, kernel and <tt>udev</tt> map the zoom key's ACPI event (<tt>ibm/hotkey HKEY 00000080 00001014</tt>) to input event <tt>KEY_ZOOM</tt> whose numerical value, 372, is greater than 255, the highest key-event code that X can handle.

'''Micmute''': The <tt>thinkpad-acpi</tt> module and kernel generate an ACPI event (<tt>ibm/hotkey HKEY 00000080 0000101b</tt>) for the microphone mute button but in releases earlier than precise this is not mapped to anything; in precise it is mapped to 256 which is also greater than 255, the highest that X can handle. Bug reported [https://bugs.launchpad.net/ubuntu/+source/udev/+bug/408903 here].

The fault lies with X which can't handle key codes above 255. But as discussed, e.g., [https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/313514 here], it may be a long time before this gets fixed in X.

There is a fairly easy workaround.
Install version 175 or later of the <tt>udev</tt> package and do the following.
<pre>
# sudo su
# mkdir /etc/udev/keymaps
# cp /lib/udev/keymaps/module-lenovo /etc/udev/keymaps
</pre>
Now edit <tt>/etc/udev/keymaps/module-lenovo</tt> so that 0x13 and 0x1A get mapped to <tt>search</tt> and <tt>prog2</tt>, respectively (instead of <tt>zoom</tt> and <tt>micmute</tt>, respectively).

Then in System Settings | Keyboard | Shortcuts assign a behavior to the <tt>XF86Search</tt> event, the X event corresponding to <tt>search</tt>. This behavior will be invoked by Fn-Space.

There is no built-in function for muting the microphone but it is straightforward to concoct one using <tt>amixer</tt>.
In Keyboard | Shortcuts select Custom Shortcuts and press <tt>+</tt> to create a new shortcut named "Microphone mute" whose command-content is the following.
<pre>
sh -c "if amixer get Capture,0 | grep -q '\[on\]' ; then amixer -q set Capture,0 nocap ; else amixer -q set Capture,0 cap; fi"
</pre>
Assign this to <tt>XF86Launch2</tt> which is the X event corresponding to input event <tt>prog2</tt>. This behavior will be invoked by the microphone-mute key.

[Added June 2013:] This will [https://bugs.launchpad.net/ubuntu/+source/udev/+bug/408903 supposedly] be fixed for Ubuntu 13.10 (Saucy). The microphone-mute ACPI event will be mapped to f20 instead of prog2 but making use of this will require patches to other packages: https://code.launchpad.net/~jm-leddy/

=== Fix for [https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/486154 the known no-system-beep problem] ===
As I described in more detail [[Installing Ubuntu 9.10 (Karmic Koala) on a ThinkPad X61#Partially solved problem: No beep|earlier]]:
* Create <tt>.xprofile</tt> containing
<pre>
pactl upload-sample /usr/share/sounds/gnome/default/alerts/glass.ogg bell.ogg
</pre>
* Run <tt>gconf-editor</tt> and at <tt>desktop | gnome | peripherals | keyboard</tt> change the value of <tt>bell_mode</tt> from <tt>off</tt> to <tt>on</tt>.
* If the default bell volume of 50 (percent) is not loud enough, add a line like the following to <tt>~/.bashrc</tt>.
<pre>
xset b 100
</pre>
* To cause terminal bells to ring also in non-X terminals (e.g., the console terminal), comment out the <tt>blacklist pcspkr</tt> line in <tt>/etc/modprobe.d/blacklist.conf</tt>.

=== Fix for "[drm:i915_hangcheck_ring_idle] *ERROR* Hangcheck timer elapsed... blt ring idle..." problem ===
To fix [https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/761065 this known problem] upgrade the kernel: install the <tt>linux-image-2.6.38-11-generic</tt> package and reboot.

=== [[Tp smapi|tp-smapi]] loading ===
First, it is as usual necessary to add
<pre>
tp-smapi
</pre>
to <tt>/etc/modules</tt> so that <tt>modoprobe</tt> will attempt to load the module at boot time.

=== <tt>hdaps</tt> ===
Having loaded <tt>hdaps</tt> do:
<pre>
sudo add-apt-repository ppa:linrunner/thinkpad-extras
sudo apt-get update
sudo apt-get install hdaps-utils
hdaps-gl
</pre>

Result:

[[Image:ThinkPad_X220_running_hdaps-gl.jpg|Tilted ThinkPad X220 running hdaps-gl|300px]]

=== Miscellaneous configuration ===
* Having installed bare Ubuntu I had to run <tt>tasksel</tt> and select at least "Ubuntu Desktop".

* In order to allow NetworkManager to manage eth0 I had to comment out the "eth0" stanza in <tt>/etc/network/interfaces</tt>

* I used System Settings | Ubuntu Software Center to install <tt>ccsm</tt> ("Advanced Desktop Effects Settings") so I could enable Wobbly Windows and so I can initiate window resize with Alt+Button3 which is easier than the default Alt-Button2 (i.e., Alt-scrollwheelbutton).

* Add PPAs to apt sources list for additional indicators

=== Unity automaximizes ===
To disable this (annoying) behavior, run <tt>gconf-editor</tt> and set <tt>apps|compiz-1|plugins|grid|screen0|options|top_edge_action</tt> to 0 (originally 10).

== Ex-problems ==
=== Suspend causes kernel panic ===
"Suspend-to-RAM and brightness control of the display work with kernel >= 3.0-rc6" according to [[Installing Gentoo on a ThinkPad X220|this fellow]].

Since I upgraded to kernel 2.6.38-11-generic I haven't had any kernel panics on suspend.

=== TPM can't be used ===
To try it out, install <tt>tpm-tools</tt>.

When I first tried it, the <tt>tpm_version</tt> program failed with "Communication failure".

But now it prints this:
<pre>
TPM 1.2 Version Info:
Chip Version: 1.2.8.32
Spec Level: 2
Errata Revision: 3
TPM Vendor ID: STM
TPM Version: 01010000
Manufacturer Info: 53544d20
</pre>

Presumably the new kernel fixed this.

=== memtest86+ didn't work ===

Upgrading to the oneiric version, v4.20, fixed this.

=== Multiple monitors ===
Configuring an extended desktop over two monitors led to malfunction. Side-by-side worked, one above the other did not.

In natty the solution was just to avoid the layouts that caused the malfunction.

The problems appear to have been completely solved in Ubuntu 11.10 (Oneiric Ocelot).

=== Bluetooth-related crashes ===
Switching bluetooth on or off either using the indicator or Fn-F5 sometimes crashed the machine.

I haven't seen this problem in Ubuntu 10.10 (Oneiric Ocelot).

=== [[Tp smapi|tp-smapi]] loading problem ===
The distributed <tt>tp-smapi</tt> and <tt>hdaps</tt> modules didn't load on my X220
and <tt>thinkpad-acpi</tt> reported the EC firmware number as "unknown".

The BIOS setup program reports this information about the BIOS:
* Model 42902WG
* UEFI BIOS 8DET46WW (1.16) 2011-05-18
* Embedded Controller 8DHT23WW (1.07)

This problem was fixed in <tt>tp-smapi</tt> version 0.41-1. As of 7 August 2011 <tt>tp-smapi-dkms</tt> is available in Debian unstable (Ubuntu uses Debian <tt>tp-smapi</tt> packages with no changes) and this is the version in Ubuntu 11.10 (Oneiric Ocelot).

Output from <tt>dmesg</tt> after <tt>modprobe</tt>ing <tt>thinkpad-ec</tt>, <tt>tp-smapi</tt> and <tt>hdaps</tt>:
<pre>
[ 714.842090] thinkpad_ec: thinkpad_ec 0.41 loaded.
[ 721.983409] tp_smapi 0.41 loading...
[ 721.984742] tp_smapi successfully loaded (smapi_port=0xb2).
[ 729.462533] hdaps: LENOVO ThinkPad X220 detected, setting orientation 4
[ 729.462894] hdaps: initial mode latch is 0x05
[ 729.463022] hdaps: setting ec_rate=250, filter_order=2
[ 729.463242] hdaps: device successfully initialized.
[ 729.463799] input: ThinkPad HDAPS joystick emulation as /devices/virtual/input/input15
[ 729.464101] input: ThinkPad HDAPS accelerometer data as /devices/virtual/input/input16
[ 729.464342] hdaps: driver successfully loaded.
</pre>

Modinfo:
<pre>
$ modinfo tp-smapi
filename: /lib/modules/2.6.38-11-generic/updates/dkms/tp_smapi.ko
license: GPL
version: 0.41
description: ThinkPad SMAPI Support
author: Shem Multinymous
srcversion: B6841670771B2FF5222BFFD
depends: thinkpad_ec
vermagic: 2.6.38-11-generic SMP mod_unload modversions
parm: debug:Debug level (0=off, 1=on) (int)
</pre>

== Remaining problems ==

=== Indicator lamp on microphone mute key doesn't work ===
The problem has been discussed, e.g., [https://bugs.launchpad.net/ubuntu/+source/linux/+bug/408903 here].

== Comparison with [[Installing Ubuntu 10.10 (Maverick Meerkat) on a ThinkPad X220|a Ubuntu 10.10 user's experience]] ==
* (improvements)
** I didn't have to do anything special to have the <tt>thinkpad-acpi</tt> module loaded or use special keys
** The mute-microphone button can be made to work as described above
** Both left and right microphones are seen
** I have no difficulties with the fans
** I have no difficulties with SD cards
** The "Hangcheck timer elapsed" problem has been fixed in a new kernel version, as described above

== Things to remember ==
To get Google Earth to work you have to do
<pre>
sudo apt-get install libgl1-mesa-glx:i386
</pre>

[[Category:Ubuntu 11.04]][[Category:Ubuntu 11.10]]

Intel Gigabit Ethernet PCI-Express Controller

2013-02-02T01:35:01Z

MarkStosberg: /* Features */ clarify "Auto MDIX" in layman's terms

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== Intel Gigabit Ethernet PCI-Express controller ===
This is a PCI Express Intel Ethernet chip that is integrated on the systemboard of select ThinkPads.

=== Features ===
* 10Base-T, 100Base-T and 1000Base-T support
* Auto MDIX (Automatic Crossover)

</div>
|style="vertical-align:top" |
|}

=== Linux support ===
These Ethernet chips are supported by the '''e1000e''' driver.

=== Links ===
* ...

===ThinkPads this component may be found in===

'''Intel 82573L'''
* {{T60}}, {{T60p}}
* {{X60}}, {{X60s}}

'''Intel 82566MM''' (w/ [[Intel Active Management Technology (AMT)]])
* {{R61}}, {{R61i}}
* {{T61}}, {{T61p}}
* {{X61}}, {{X61s}}, {{X61 Tablet}}, {{X300}}

'''Intel 82567LM''' (w/ [[Intel Active Management Technology (AMT)]]) [8086:10f5]
* {{R400}}
* {{T400}}, {{T400s}}, {{T500}}
* {{W500}}, {{W700}}, {{W700ds}}
* {{X200}}, {{X200s}}, {{X200 Tablet}}, {{X301}}

'''Intel 82577LM''' (w/ [[Intel Active Management Technology (AMT)]]) [8086:10ea]
* {{T410}}, {{T410i}}, {{T410s}}, {{T410si}}, {{T510}}, {{T510i}}
* {{W510}}, {{W701}}, {{W701ds}}
* {{X201}}, {{X201i}}, {{X201s}}, {{X201 Tablet}}

'''Intel 82579LM''' (w/ [[Intel Active Management Technology (AMT)]]) [8086:1502]
{{NOTE|Supported by Linux 2.6.36 and higher}}
* {{W520}}
* {{X220}}
* {{T430}}

[[Category:Components]]

Intel Gigabit Ethernet Controller

2013-02-02T01:34:14Z

MarkStosberg: /* Features */ clarify "Auto MDIX" in layman's terms

Problem with error 01C9 - More than one Ethernet devices

2011-10-29T22:31:32Z

MarkStosberg: /* Related Links: */ de-spam

==Problem Description==
Certain ThinkPads show a warning message during [[POST]] when a WLAN card with an Atheros chipset is present in the MiniPCI or PCMCIA slot:

WARNING
01C9: More than one Ethernet devices are found. Remove one of them.
Press <Esc> to continue.

Also, boot-up during POST may be taking longer than expected.

At POST, the BIOS conducts a scan for ethernet devices. It does this by reading the "PCI Class Codes" of every connected device. If more than one ethernet device is found, it produces the 01C9 error message. Unlike other wireless cards, which identify themselves as "other" network adapters, Atheros classify themselves as "ethernet". This collides with the internal ethernet controller (also a PCI device) and causes the 01C9 to appear. BIOS processing of the situation and generating the error message noticeably slow down boot-up time, at least in some models.

== Affected Models ==
* ThinkPad {{A31}}, {{A31p}}
* ThinkPad {{T23}}, {{T30}}
* ThinkPad {{R32}}, {{R40}}
* ThinkPad {{X22}}, {{X23}}, {{X24}}, {{X30}}

'''Not affected are'''
*ThinkPad T4x series
*ThinkPad X4x series

== Solution ==
The solution is to modify the Atheros EEPROM so that the card correctly identifies itself as an "other" instead of an "ethernet" network adapter. A Linux Live CD that automates this and can also remove the 1802 error message is now available.

{{WARN|This software was designed FOR ATHEROS CARDS ONLY. Even though most users confirm it working fine, it can potentially harm your computer. The authors are in no way to be held liable for damage caused by this program. There is no warranty given, either express or implied for any fitness for any kind of purpose. YOU AGREE TO USE THIS ENTIRELY AT YOUR OWN RISK. Please also be aware that ath_info is still under development, so be just as cautious with the manual solutions suggested below.}}

NOTICE: The Live CD Version 2 is released now. Download it via ''Rapidshare'' [http://rapidshare.com/files/145019337/wifi_v2.zip.html here.] (~ 4 MB).
Download links appear to break regularly but will be fixed whenever necessity arises.

'''Functionality.''' The 01C9-patch changes the PCI Class ID from 0x0200 to 0x0280, which corresponds "network device: other". It manipulates the Atheros card, not the computer/BIOS/CMOS. It changes neither the PCI vendor ID nor the device ID. Therefore, functionality of drivers and operating systems will not be affected. Uninstalling drivers is not necessary before using this patch. The Live CD auto-detects whether an Atheros adapter is installed and will only then proceed. NOTE: Read the [[Problem_with_unauthorized_MiniPCI_network_card]] article on functionality of the 1802 patch.

'''Usage.'''
# Burn the .ISO file to a CD/DVD. Make sure not to burn it as a file within a filesystem, but as an image.
# If you want to remove the 01C9 error only, skip to step 8.
# To remove the 1802 error, make sure you do not have the Atheros card plugged into the slot.
# Boot from the disc.
# Choose to remove the 1802 error.
# Shut down after pressing Ctrl-Alt-Del.
# Plug in the Atheros card now.
# Boot from the disc (again).
# Choose not to apply the no-1802.
# Choose to apply the 01C9 patch.
# Shut down after pressing Ctrl-Alt-Del. Upon 'cold' reboot, the 01C9 should be gone.

== Limitations ==
Many newer Atheros adapters (chipsets equal to and newer than AR5004x) incorporate an EEPROM write protection by default. The Live CD may or may not be able to automatically patch these devices.

=== Possible solutions ===
Should the automated solution fail, you can try to manually set a GPIO (general purpose input/output) bit to enable write access. Depending on your adapter, this might activate the EEPROM write-enable channel. After the Live CD finishes, it will drop to a Linux shell prompt. Try typing the following:
lspci -vd 168c: |sed -n 's/.*Memory at $[^ ]*$.*/0x\1/p'
This will present you with the EEPROM base address. This you can use to switch the GPIO:
/root/ath_info -g 4:0 -w <base_address>
In this example, you are setting GPIO 4 to low. Restart the patch script to see whether this enabled patching.
/root/patch.sh
After writing you may dump the complete eeprom with "-d" and find the new pci class at (16 bit) offset 2 for verification.

=== Manual method: Ath_info from a LiveCD ===
The Linux Live CD depends on ath_info, a tool derived from the [http://www.madwifi.org Madwifi] Atheros driver project. You can also install ath_info yourself and manually replicate the steps laid out above. If you cannot use ath_info from your current operating system (say if you use [http://www.freebsd.org/ FreeBSD]), you can use [http://grml.org/ grml] to perform this "operation". The grml Live CD contains a C compiler, the Subversion client and loads the Madwifi drivers on boot. So all you need to do is to fetch the source and build ath_info:
svn co http://madwifi-project.org/svn/ath_info/trunk ath_info
cd ath_info
make
Again, you need to find the address at which your card can be accessed (see above). Once you know it. instead of using the script, run
ath_info -v -w <base_address> pci_class 0x0280
Read this manual page [http://madwifi.org/wiki/UserDocs/AthInfo] for further details.

== Successful applications ==
Please add PCI IDs to this list. In Linux, type (case sensitive!):
lspci |grep Ath && lspci -n |grep 168c
* Askey Computer Corp AR2413A (802.11b/g) FCC ID:PPD-AR5BMB5 IC:4104A-AR5BMB5 (AR5005GS chipset)
* SMC2835W, FCC ID: HED2835WACC (Cardbus card)
* Gigabyte GN-WI01HT (802.11abg), AR5006SX-based
* Generic unbranded AR5006X (802.11abg, 108Mbps super a/g+) , PCI ID: 168c:001b (rev 01), Subsystem: 10cf:1329
* Compex Wireless 802.11 b/g MiniPCI Adapter, Rev A1 [WLM54G]
* Atheros Communications Inc. AR5212/AR5213 Multiprotocol MAC/baseband processor [168c:0013] (rev 01)
* Atheros Communications Inc. AR2413 802.11bg NIC (rev 01)

Installing Ltmodem driver for Mandriva

2010-07-20T00:41:21Z

MarkStosberg: remove obsolete link, add timestamp for last known-working year.

Getting the "ltserial" modem to work was relatively easy.

Going through the Mandriva Control Center wizard with Mandriva 2006, the modem
was recognized, but it expects me to install a "ltmodem-kernel" package from
an external source.

Since this package wasn't found, I was not able to complete the wizard and
manage the modem through through the Mandriva Control Center. It can work fine
despite this.

There's a [http://www.linuxquestions.org/questions/showthread.php?p=910257#post910257 thread at LinuxQuestions.org] with details.
The ALK packages they reference are [http://linmodems.technion.ac.il/packages/ltmodem/kernel-2.6/ here].

After rebooting, /dev/modem may disappear. One solution to that is referencing
/dev/ttyLTM0 directly for the modem device, instead of trying to figure how to keep that symbolic link intact.

In 2006, the modem was confirmed to work with penggy, an AOL dialer.

[[Category:Mandriva]] [[Category:T23]]

Installing Ubuntu on a ThinkPad T23

2009-03-29T15:35:56Z

MarkStosberg: /* Ubuntu 8.04 Hardy Heron */ Projector details

== Ubuntu 8.04 Hardy Heron ==

The upgrade from Gutsy to Hardy goes fairly smoothly.

=== Regressions ===

The following features quit working after the upgrade:

* Having Caps Lock work as a second Control key works, but the Caps Lock status light toggles on and off as Control is pressed, giving the impression that Caps Lock is actually on. This is set in System: Preferences: Keyboard: Layouts: Layout Options: Ctrl Key Position. Track Ubuntu [https://bugs.launchpad.net/ubuntu/+bug/173350/ Bug #173350] for the latest updates.
* On Screen Display of special key actions quits working. The keys include the brightness and volume adjustment keys, as well as mute. [https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/198197 bug report] has been filed about this, and you can subscribe to it to follow the progress. A workaround is to boot the 2.6.22 kernel supplied with Gutsy. This is already on your system by default after an upgrade from Gutsy to Hardy. See [https://help.ubuntu.com/community/GrubHowto/ChangeDefaultOS ChangeDefaultOS] for details on how to change the "default" line in /boot/grub/menu.lst and then run ''sudo update-grub''' for the change to take effect.

=== Sound After Suspend ===

After a Suspend/Resume cycle, sound may need to be unmuted. This can automated as follows.

First, always be sure to enter suspend by pressing "Fn-F4". Using the Suspend option on the logout menu may not produce the same result.

Open "Applications: Accessories: Text Editor" and copy/paste in the following:

# fix sound-after-resume on the ThinkPad T23.
# Make sure that "amixer" is present, which is provided by the "alsa-utils" package.
case "$1" in hibernate|suspend)
# nothing to do
;;
thaw|resume)
mixers="Master PCM CD"
for mixer in $mixers ; do
/usr/bin/amixer -q sset $mixer mute
/usr/bin/amixer -q sset $mixer unmute
done
;;
*)
;;
esac
exit $?

Save the file on your desktop, naming it as "sound". Then after opening "Applications: Accessories: Terminal",
copy/paste in the following commands. You will be prompted for your password.

sudo cp ~/Desktop/sound /etc/pm/sleep.d/sound
sudo chmod+x !$

The first command copies the file in the proper location. The second one makes sure the script marked is as "executable". Now whenever Ubuntu resumes it should automatically run this script and unmute the volume. If for some reason it doesn't work, you can still run the script manually to unmute the volume, also using the terminal:

sh /etc/pm/sleep.d/sound

=== Skype Video with Logitech QuickCam Pro 9000 ===

Skype video can be sent or received. Doing both at the same time results in regular crashes. When sending video, the small thumbnail video of what's being sent doesn't show up. These issues could be related to the hardware being at or below the minimum recommended system requirements for Skype and this webcam.

=== Using a Projector ===

Using Fn-F7 does not cause the video to appear to on a projector. To make video appear on a projector, install S3switch. ( In a terminal: sudo apt-get install s3switch ). Once installed, you can mirror the video to a projector using the terminal:

sudo s3switch both

To switch back to only the laptop screen

sudo s3switch lcd

== Ubuntu 7.10 Gutsy Gibbon ==

Things generally work fine, with the following notes

=== Power Management ===

==== Sound After Suspend ====

See notes for Hardy, above.

=== Dual Monitors ===

Gutsy Gibbon has a new "Screens and Graphics" preferences area. It shows a second monitor possibility. Trying a test does make both the LCD and external screen active as one big gray monitor...but only for the test. Choosing the option to accept the settings does not actually cause monitor-spanning to work, but monitor mirroring does.

=== CPU Frequency Scaling ===

CPU Frequency Scaling seems to be working automatically. To see your current speed level, activate the CPU Frequency Scaling Monitor Applet. Right click on the toolbar and select "add to panel". You can search for "Frequency" to find it.

== Ubuntu 7.04 Feisty Fawn ==

=== Power Management ===

The chips in T23s have the ability to run at speeds slower than their maximum, in order to save power. To see your current speed level, activate the CPU Frequency Scaling Monitor Applet. Right click on the toolbar and select "add to panel". You can search for "Frequency" to find it.

You can also enable this applet to allow you manually change the speed and scaling policy. To do that, run this in a terminal: "sudo dpkg-reconfigure gnome-applets".

These instructions are also available [http://www.ubuntugeek.com/howto-change-cpu-frequency-scaling-in-ubuntu.html illustrated with screenshots].

You may also need to add a couple of lines to "/etc/modules" to allow you to be able to change the processor speed and governor. The lines are:

acpi-cpufreq
cpufreq_ondemand

These will now be loaded on at boot time. To activate them immediately:

sudo modprobe acpi-cpufreq
sudo modprobe cpufreq_ondemand

Some technical details are explained on the [[SpeedStep]] page.

== External Resources ==

*[http://del.icio.us/tags/ubuntu+t23 Bookmarks tagged with Ubuntu and T23] on del.icio.us
*[http://ubuntuforums.org/tags/index.php/t23/ Forum posts tagged with T23] on ubuntuforums.org
[[Category:T23]]
[[Category:Ubuntu 7.04]]

Installing Ubuntu on a ThinkPad T23

2009-03-29T15:27:31Z

MarkStosberg: /* Sound After Suspend */ mention that Fn-F4 makes a difference when entering suspend

== Ubuntu 8.04 Hardy Heron ==

The upgrade from Gutsy to Hardy goes fairly smoothly.

=== Regressions ===

The following features quit working after the upgrade:

* Having Caps Lock work as a second Control key works, but the Caps Lock status light toggles on and off as Control is pressed, giving the impression that Caps Lock is actually on. This is set in System: Preferences: Keyboard: Layouts: Layout Options: Ctrl Key Position. Track Ubuntu [https://bugs.launchpad.net/ubuntu/+bug/173350/ Bug #173350] for the latest updates.
* On Screen Display of special key actions quits working. The keys include the brightness and volume adjustment keys, as well as mute. [https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/198197 bug report] has been filed about this, and you can subscribe to it to follow the progress. A workaround is to boot the 2.6.22 kernel supplied with Gutsy. This is already on your system by default after an upgrade from Gutsy to Hardy. See [https://help.ubuntu.com/community/GrubHowto/ChangeDefaultOS ChangeDefaultOS] for details on how to change the "default" line in /boot/grub/menu.lst and then run ''sudo update-grub''' for the change to take effect.

=== Sound After Suspend ===

After a Suspend/Resume cycle, sound may need to be unmuted. This can automated as follows.

First, always be sure to enter suspend by pressing "Fn-F4". Using the Suspend option on the logout menu may not produce the same result.

Open "Applications: Accessories: Text Editor" and copy/paste in the following:

# fix sound-after-resume on the ThinkPad T23.
# Make sure that "amixer" is present, which is provided by the "alsa-utils" package.
case "$1" in hibernate|suspend)
# nothing to do
;;
thaw|resume)
mixers="Master PCM CD"
for mixer in $mixers ; do
/usr/bin/amixer -q sset $mixer mute
/usr/bin/amixer -q sset $mixer unmute
done
;;
*)
;;
esac
exit $?

Save the file on your desktop, naming it as "sound". Then after opening "Applications: Accessories: Terminal",
copy/paste in the following commands. You will be prompted for your password.

sudo cp ~/Desktop/sound /etc/pm/sleep.d/sound
sudo chmod+x !$

The first command copies the file in the proper location. The second one makes sure the script marked is as "executable". Now whenever Ubuntu resumes it should automatically run this script and unmute the volume. If for some reason it doesn't work, you can still run the script manually to unmute the volume, also using the terminal:

sh /etc/pm/sleep.d/sound

=== Skype Video with Logitech QuickCam Pro 9000 ===

Skype video can be sent or received. Doing both at the same time results in regular crashes. When sending video, the small thumbnail video of what's being sent doesn't show up. These issues could be related to the hardware being at or below the minimum recommended system requirements for Skype and this webcam.

== Ubuntu 7.10 Gutsy Gibbon ==

Things generally work fine, with the following notes

=== Power Management ===

==== Sound After Suspend ====

See notes for Hardy, above.

=== Dual Monitors ===

Gutsy Gibbon has a new "Screens and Graphics" preferences area. It shows a second monitor possibility. Trying a test does make both the LCD and external screen active as one big gray monitor...but only for the test. Choosing the option to accept the settings does not actually cause monitor-spanning to work, but monitor mirroring does.

=== CPU Frequency Scaling ===

CPU Frequency Scaling seems to be working automatically. To see your current speed level, activate the CPU Frequency Scaling Monitor Applet. Right click on the toolbar and select "add to panel". You can search for "Frequency" to find it.

== Ubuntu 7.04 Feisty Fawn ==

=== Power Management ===

The chips in T23s have the ability to run at speeds slower than their maximum, in order to save power. To see your current speed level, activate the CPU Frequency Scaling Monitor Applet. Right click on the toolbar and select "add to panel". You can search for "Frequency" to find it.

You can also enable this applet to allow you manually change the speed and scaling policy. To do that, run this in a terminal: "sudo dpkg-reconfigure gnome-applets".

These instructions are also available [http://www.ubuntugeek.com/howto-change-cpu-frequency-scaling-in-ubuntu.html illustrated with screenshots].

You may also need to add a couple of lines to "/etc/modules" to allow you to be able to change the processor speed and governor. The lines are:

acpi-cpufreq
cpufreq_ondemand

These will now be loaded on at boot time. To activate them immediately:

sudo modprobe acpi-cpufreq
sudo modprobe cpufreq_ondemand

Some technical details are explained on the [[SpeedStep]] page.

== External Resources ==

*[http://del.icio.us/tags/ubuntu+t23 Bookmarks tagged with Ubuntu and T23] on del.icio.us
*[http://ubuntuforums.org/tags/index.php/t23/ Forum posts tagged with T23] on ubuntuforums.org
[[Category:T23]]
[[Category:Ubuntu 7.04]]

Installing Ubuntu on a ThinkPad T22

2009-02-10T13:08:50Z

MarkStosberg: Add link to T20 page

== Ubuntu 8.10 Intrepid Ibex ==

Ubuntu 8.10 Intrepid Ibex installs and runs reasonably well on an IBM ThinkPad T22.

=== X fails to initialize, shows black screen ===

X may not initialize due a [https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-savage/+bug/33617 bug]. Here's a reliable workaround:

1. Install from the Alternate install CD (which avoids graphics issues)
2. On first boot, press "escape" as you briefly pass through the GRUB bootloader stage, and select "Recovery Mode". From there, select the "root shell" option.
3. Fix the xorg.conf file:

# sudo nano /etc/X11/xorg.conf

scroll down to the "Device" section and add this line:

Option "BusType" "PCI"

Control-X to save the file, and then type "exit" at the shell prompt to return the recovery console menu. You should be able now select "resume" and have the issue solved for good. (as long as the xorg.conf file isn't changed)

=== Sound-after-Suspend ===

There's also a problem with sound working after suspend. There is a workaround to install which involves forcefully killing and restarting all applications which are using sound. [https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.24/+bug/198218/comments/56 See the workaround].

== See Also ==

The T22 is has very similar hardware to the T20 and T21, so tips for those models likely apply here as well. In particular see:

* [[Installing Ubuntu on a ThinkPad T20]]

Installing Ubuntu on a ThinkPad T22

2009-02-10T13:06:28Z

MarkStosberg: create new page for Ubuntu on the T22

Installation instructions for the ThinkPad T22

2008-12-13T17:42:36Z

MarkStosberg: New external source

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

==General Notes==

The T20, T21 and T23 are rather similar models, so pages like [[Installation instructions for the ThinkPad T20]] may also be helpful.

==Distro specific Instructions==

'''Ubuntu 6.06 Desktop'''

S3 Savage chip will cause Thinkpad T20, T21, T22 to freeze when booting into X Windows. Please see [[Installation instructions for the ThinkPad T21]].

==External Sources==

* [http://www.jarviser.co.uk/jarviser/ubuntu8ont22.html Jarvisers tips for Ubuntu Hardy 8.04 on the T22]

Installing Ubuntu on a ThinkPad T23

2008-11-08T13:49:11Z

MarkStosberg: New section notes experience using T23/Ubuntu/ Skype/ webcam

== Ubuntu 8.04 Hardy Heron ==

The upgrade from Gutsy to Hardy goes fairly smoothly.

=== Regressions ===

The following features quit working after the upgrade:

* Having Caps Lock work as a second Control key works, but the Caps Lock status light toggles on and off as Control is pressed, giving the impression that Caps Lock is actually on. This is set in System: Preferences: Keyboard: Layouts: Layout Options: Ctrl Key Position. Track Ubuntu [https://bugs.launchpad.net/ubuntu/+bug/173350/ Bug #173350] for the latest updates.
* On Screen Display of special key actions quits working. The keys include the brightness and volume adjustment keys, as well as mute. [https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/198197 bug report] has been filed about this, and you can subscribe to it to follow the progress. A workaround is to boot the 2.6.22 kernel supplied with Gutsy. This is already on your system by default after an upgrade from Gutsy to Hardy. See [https://help.ubuntu.com/community/GrubHowto/ChangeDefaultOS ChangeDefaultOS] for details on how to change the "default" line in /boot/grub/menu.lst and then run ''sudo update-grub''' for the change to take effect.

=== Sound After Suspend ===

After a Suspend/Resume cycle, sound may need to be unmuted. This can automated as follows.

Open "Applications: Accessories: Text Editor" and copy/paste in the following:

# fix sound-after-resume on the ThinkPad T23.
# Make sure that "amixer" is present, which is provided by the "alsa-utils" package.
case "$1" in hibernate|suspend)
# nothing to do
;;
thaw|resume)
mixers="Master PCM CD"
for mixer in $mixers ; do
/usr/bin/amixer -q sset $mixer mute
/usr/bin/amixer -q sset $mixer unmute
done
;;
*)
;;
esac
exit $?

Save the file on your desktop, naming it as "sound". Then after opening "Applications: Accessories: Terminal",
copy/paste in the following commands. You will be prompted for your password.

sudo cp ~/Desktop/sound /etc/pm/sleep.d/sound
sudo chmod+x !$

The first command copies the file in the proper location. The second one makes sure the script marked is as "executable". Now whenever Ubuntu resumes it should automatically run this script and unmute the volume. If for some reason it doesn't work, you can still run the script manually to unmute the volume, also using the terminal:

sh /etc/pm/sleep.d/sound

=== Skype Video with Logitech QuickCam Pro 9000 ===

Skype video can be sent or received. Doing both at the same time results in regular crashes. When sending video, the small thumbnail video of what's being sent doesn't show up. These issues could be related to the hardware being at or below the minimum recommended system requirements for Skype and this webcam.

== Ubuntu 7.10 Gutsy Gibbon ==

Things generally work fine, with the following notes

=== Power Management ===

==== Sound After Suspend ====

See notes for Hardy, above.

=== Dual Monitors ===

Gutsy Gibbon has a new "Screens and Graphics" preferences area. It shows a second monitor possibility. Trying a test does make both the LCD and external screen active as one big gray monitor...but only for the test. Choosing the option to accept the settings does not actually cause monitor-spanning to work, but monitor mirroring does.

=== CPU Frequency Scaling ===

CPU Frequency Scaling seems to be working automatically. To see your current speed level, activate the CPU Frequency Scaling Monitor Applet. Right click on the toolbar and select "add to panel". You can search for "Frequency" to find it.

== Ubuntu 7.04 Feisty Fawn ==

=== Power Management ===

The chips in T23s have the ability to run at speeds slower than their maximum, in order to save power. To see your current speed level, activate the CPU Frequency Scaling Monitor Applet. Right click on the toolbar and select "add to panel". You can search for "Frequency" to find it.

You can also enable this applet to allow you manually change the speed and scaling policy. To do that, run this in a terminal: "sudo dpkg-reconfigure gnome-applets".

These instructions are also available [http://www.ubuntugeek.com/howto-change-cpu-frequency-scaling-in-ubuntu.html illustrated with screenshots].

You may also need to add a couple of lines to "/etc/modules" to allow you to be able to change the processor speed and governor. The lines are:

acpi-cpufreq
cpufreq_ondemand

These will now be loaded on at boot time. To activate them immediately:

sudo modprobe acpi-cpufreq
sudo modprobe cpufreq_ondemand

Some technical details are explained on the [[SpeedStep]] page.

== External Resources ==

*[http://del.icio.us/tags/ubuntu+t23 Bookmarks tagged with Ubuntu and T23] on del.icio.us
*[http://ubuntuforums.org/tags/index.php/t23/ Forum posts tagged with T23] on ubuntuforums.org
[[Category:T23]]
[[Category:Ubuntu 7.04]]

Installing Ubuntu on a ThinkPad T23

2008-06-29T13:28:17Z

MarkStosberg: breakthrough tip for fixing sound-after-suspend with T23 and Ubuntu Hardy or Gutsy

== Ubuntu 8.04 Hardy Heron ==

The upgrade from Gutsy to Hardy goes fairly smoothly.

=== Regressions ===

The following features quit working after the upgrade:

* Having Caps Lock work as a second Control key works, but the Caps Lock status light toggles on and off as Control is pressed, giving the impression that Caps Lock is actually on. This is set in System: Preferences: Keyboard: Layouts: Layout Options: Ctrl Key Position. Track Ubuntu [https://bugs.launchpad.net/ubuntu/+bug/173350/ Bug #173350] for the latest updates.
* On Screen Display of special key actions quits working. The keys include the brightness and volume adjustment keys, as well as mute. [https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/198197 bug report] has been filed about this, and you can subscribe to it to follow the progress. A workaround is to boot the 2.6.22 kernel supplied with Gutsy. This is already on your system by default after an upgrade from Gutsy to Hardy. See [https://help.ubuntu.com/community/GrubHowto/ChangeDefaultOS ChangeDefaultOS] for details on how to change the "default" line in /boot/grub/menu.lst and then run ''sudo update-grub''' for the change to take effect.

=== Sound After Suspend ===

After a Suspend/Resume cycle, sound may need to be unmuted. This can automated as follows.

Open "Applications: Accessories: Text Editor" and copy/paste in the following:

# fix sound-after-resume on the ThinkPad T23.
# Make sure that "amixer" is present, which is provided by the "alsa-utils" package.
case "$1" in hibernate|suspend)
# nothing to do
;;
thaw|resume)
mixers="Master PCM CD"
for mixer in $mixers ; do
/usr/bin/amixer -q sset $mixer mute
/usr/bin/amixer -q sset $mixer unmute
done
;;
*)
;;
esac
exit $?

Save the file on your desktop, naming it as "sound". Then after opening "Applications: Accessories: Terminal",
copy/paste in the following commands. You will be prompted for your password.

sudo cp ~/Desktop/sound /etc/pm/sleep.d/sound
sudo chmod+x !$

The first command copies the file in the proper location. The second one makes sure the script marked is as "executable". Now whenever Ubuntu resumes it should automatically run this script and unmute the volume. If for some reason it doesn't work, you can still run the script manually to unmute the volume, also using the terminal:

sh /etc/pm/sleep.d/sound

== Ubuntu 7.10 Gutsy Gibbon ==

Things generally work fine, with the following notes

=== Power Management ===

==== Sound After Suspend ====

See notes for Hardy, above.

=== Dual Monitors ===

Gutsy Gibbon has a new "Screens and Graphics" preferences area. It shows a second monitor possibility. Trying a test does make both the LCD and external screen active as one big gray monitor...but only for the test. Choosing the option to accept the settings does not actually cause monitor-spanning to work, but monitor mirroring does.

=== CPU Frequency Scaling ===

CPU Frequency Scaling seems to be working automatically. To see your current speed level, activate the CPU Frequency Scaling Monitor Applet. Right click on the toolbar and select "add to panel". You can search for "Frequency" to find it.

== Ubuntu 7.04 Feisty Fawn ==

=== Power Management ===

The chips in T23s have the ability to run at speeds slower than their maximum, in order to save power. To see your current speed level, activate the CPU Frequency Scaling Monitor Applet. Right click on the toolbar and select "add to panel". You can search for "Frequency" to find it.

You can also enable this applet to allow you manually change the speed and scaling policy. To do that, run this in a terminal: "sudo dpkg-reconfigure gnome-applets".

These instructions are also available [http://www.ubuntugeek.com/howto-change-cpu-frequency-scaling-in-ubuntu.html illustrated with screenshots].

You may also need to add a couple of lines to "/etc/modules" to allow you to be able to change the processor speed and governor. The lines are:

acpi-cpufreq
cpufreq_ondemand

These will now be loaded on at boot time. To activate them immediately:

sudo modprobe acpi-cpufreq
sudo modprobe cpufreq_ondemand

Some technical details are explained on the [[SpeedStep]] page.

== External Resources ==

*[http://del.icio.us/tags/ubuntu+t23 Bookmarks tagged with Ubuntu and T23] on del.icio.us
*[http://ubuntuforums.org/tags/index.php/t23/ Forum posts tagged with T23] on ubuntuforums.org
[[Category:T23]]
[[Category:Ubuntu 7.04]]

Installing Ubuntu on a ThinkPad T23

2008-06-29T13:14:18Z

MarkStosberg: just some clean-up

== Ubuntu 8.04 Hardy Heron ==

The upgrade from Gutsy to Hardy goes fairly smoothly.

=== Regressions ===

The following features quit working after the upgrade:

* Having Caps Lock work as a second Control key works, but the Caps Lock status light toggles on and off as Control is pressed, giving the impression that Caps Lock is actually on. This is set in System: Preferences: Keyboard: Layouts: Layout Options: Ctrl Key Position. Track Ubuntu [https://bugs.launchpad.net/ubuntu/+bug/173350/ Bug #173350] for the latest updates.
* On Screen Display of special key actions quits working. The keys include the brightness and volume adjustment keys, as well as mute. [https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/198197 bug report] has been filed about this, and you can subscribe to it to follow the progress. A workaround is to boot the 2.6.22 kernel supplied with Gutsy. This is already on your system by default after an upgrade from Gutsy to Hardy. See [https://help.ubuntu.com/community/GrubHowto/ChangeDefaultOS ChangeDefaultOS] for details on how to change the "default" line in /boot/grub/menu.lst and then run ''sudo update-grub''' for the change to take effect.

=== Annoyances ===

Also, the issue with "sound after suspend" described below in the Gutsy section
remains with Hardy.

== Ubuntu 7.10 Gutsy Gibbon ==

Things generally work fine, with the following notes

=== Power Management ===

==== Sound After Suspend ====

Sound may not work after a suspend/resume cycle. The problem may be that some volume levels have been muted. To fix that save the following into a script:

#!/bin/sh
mixers="Master PCM CD"
for mixer in $mixers ; do
/usr/bin/amixer -q sset $mixer mute
/usr/bin/amixer -q sset $mixer unmute
done

The script should save to /etc/acpi/resume.d/70-sound-unmute.sh
Make sure the file is executable

chmod +x /etc/acpi/resume.d/70-sound-unmute.sh

In theory, that should make sound work automatically after suspend. It still may not, but you can run the script manually to bring sound back:

sh /etc/acpi/resume.d/70-sound-unmute.sh

=== Dual Monitors ===

Gutsy Gibbon has a new "Screens and Graphics" preferences area. It shows a second monitor possibility. Trying a test does make both the LCD and external screen active as one big gray monitor...but only for the test. Choosing the option to accept the settings does not actually cause monitor-spanning to work, but monitor mirroring does.

=== CPU Frequency Scaling ===

CPU Frequency Scaling seems to be working automatically. To see your current speed level, activate the CPU Frequency Scaling Monitor Applet. Right click on the toolbar and select "add to panel". You can search for "Frequency" to find it.

== Ubuntu 7.04 Feisty Fawn ==

=== Power Management ===

The chips in T23s have the ability to run at speeds slower than their maximum, in order to save power. To see your current speed level, activate the CPU Frequency Scaling Monitor Applet. Right click on the toolbar and select "add to panel". You can search for "Frequency" to find it.

You can also enable this applet to allow you manually change the speed and scaling policy. To do that, run this in a terminal: "sudo dpkg-reconfigure gnome-applets".

These instructions are also available [http://www.ubuntugeek.com/howto-change-cpu-frequency-scaling-in-ubuntu.html illustrated with screenshots].

You may also need to add a couple of lines to "/etc/modules" to allow you to be able to change the processor speed and governor. The lines are:

acpi-cpufreq
cpufreq_ondemand

These will now be loaded on at boot time. To activate them immediately:

sudo modprobe acpi-cpufreq
sudo modprobe cpufreq_ondemand

Some technical details are explained on the [[SpeedStep]] page.

== External Resources ==

*[http://del.icio.us/tags/ubuntu+t23 Bookmarks tagged with Ubuntu and T23] on del.icio.us
*[http://ubuntuforums.org/tags/index.php/t23/ Forum posts tagged with T23] on ubuntuforums.org
[[Category:T23]]
[[Category:Ubuntu 7.04]]

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad X61 Tablet

2008-05-10T11:50:18Z

MarkStosberg: Simplify introduction.

Installed from the alternate version CD.

= Graphic =
== Graphics Card ==
3D acceleration and Compiz Fusion worked out of the box.

== X ==
Edit /etc/X11/xorg.conf and add to Section Screen

SubSection "Display"
Virtual 3000 2250
EndSubSection

The Parameters behind Virtual must be bigger than all your Displays added together (3000 = 1400 + 1600)
Now you can adust you settings with xrandr. e.g.:

xrandr --output LVDS --rotate left
xrandr --output LVDS --rotate normal
xrandr --output VGA --auto --right-of LVDS
…

== Konsole ==

Edit /etc/modprobe.d/blacklist-framebuffer and comment this out:

#blacklist vesafb
#blacklist vga16fb

Add to /etc/initramfs-tools/modules

fbcon
vesafb
vga16fb

Run

sudo update-initramfs -u

Edit /boot/grub/menu.lst and change at defoptions:

vga=0x31b

Run

sudo update-grub

= Input Devices =
== Keyboard ==

In some cases the mute button won't work.

For this add in the /boot/grub/menu.lst file following kernel parameter:

acpi_osi="Linux"

Run

sudo update-grub

== Stylus ==
Enable it as described in [[Wacom_Serial_Tablet_PC_Stylus]]:
Add to /etc/X11/xorg.conf:

Section "InputDevice"
Driver "wacom"
Identifier "cursor"
Option "Device" "/dev/ttyS0"
Option "Type" "cursor"
Option "ForceDevice" "ISDV4"
Option "Mode" "Absolute"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "stylus"
Option "Device" "/dev/ttyS0"
Option "Type" "stylus"
Option "ForceDevice" "ISDV4"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "eraser"
Option "Device" "/dev/ttyS0"
Option "Type" "eraser"
Option "ForceDevice" "ISDV4"
EndSection

and in Section ServerLayout:

InputDevice "cursor" "SendCoreEvents"
InputDevice "stylus" "SendCoreEvents"

== Trackpoint ==
The three mouse buttons and trackpoint nipple/stick/nub work out of the box.

If you want the middle mouse button and the nipple to function together as a mouse wheel, add the following to the ''Configured Mouse'' Input Device section in /etc/X11/xorg.config:
<pre><nowiki>Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2" </nowiki></pre>

= Tilt Detection =
These steps have been referenced from [http://www.krizka.net/2008/01/23/thinkpad-x61-tablet-tilt-detection-and-ubuntu-hardy-heron/ Krizka's Blog] with a few changes.

1) Install the necessary build tools:
<pre><nowiki>sudo aptitude install build-essential linux-kernel-headers</nowiki></pre>

2) Download the tp_smapi package. It contains all the necessary sources for the hdaps module. This tutorial will be using tp_smapi version 0.36. [http://sourceforge.net/project/showfiles.php?group_id=1212 Download Here]. I downloaded the package to /opt.

3) Extract the packge:
<pre><nowiki>sudo tar -xvzf tp_smapi-0.36.tgz</nowiki></pre>

4) After unpacking, I didn't have permissions to enter the folder. Still being new to Linux, I changed the folder's access permissions using:
<pre><nowiki>sudo chmod 777 tp_smapi-0.36</nowiki></pre>
For those of you who know better, I wouldn't recommend using 777, as that allows the folder to be read and edited by anyone. Enter the folder:
<pre><nowiki>cd tp_smapi-0.36</nowiki></pre>

5) Build the sources:
<pre><nowiki>sudo make HDAPS=1 KSRC=/usr/src/linux-headers-`uname -r`</nowiki></pre>

6) Install the module:
<pre><nowiki>sudo make install HDAPS=1 KSRC=/usr/src/linux-headers-`uname -r`</nowiki></pre>

7) Install hdaps-utils in order to test the new module:
<pre><nowiki>sudo aptitude install hdaps-utils</nowiki></pre>

8) Load the new modules:
<pre><nowiki>sudo modprobe -a tp_smapi hdaps</nowiki></pre>

9) Run a test. hdaps-gl should open up a new window showing the tablet's orientation. If you don't want to use a graphical tool, hdaps-pivot prints its output to the command line:
<pre><nowiki>hdaps-gl</nowiki></pre>

10) To make sure your system loads the modules at boot time add "tp_smapi" and "hdaps", without the quotes and one per line, to /etc/modules. Using echo didn't work for me, so I used pico:
<pre><nowiki>sudo pico /etc/modules</nowiki></pre>

11) And update your initramfs:
<pre><nowiki>sudo update-initramfs -u</nowiki></pre>

== External Links ==
[http://blog.aliencam.net/?page_id=438 Customized Ubuntu Hardy Setup Guide on X61t Hardware].

[[Category:X61 Tablet]]

Installing Ubuntu on a ThinkPad T23

2008-04-28T02:25:55Z

MarkStosberg: /* Regressions */ clarify sentence.

== Ubuntu 8.04 Hardy Heron ==

The upgrade from Gutsy to Hardy goes fairly smoothly.

=== Regressions ===

The following features quit working after the upgrade:

* Having Caps Lock work as a second Control key works, but the Caps Lock status light toggles on and off as Control is pressed, giving the impression that Caps Lock is actually on. This is set in System: Preferences: Keyboard: Layouts: Layout Options: Ctrl Key Position. Track Ubuntu [https://bugs.launchpad.net/ubuntu/+bug/173350/ Bug #173350] for the latest updates.
* On Screen Display of special key actions quits working. The keys include the brightness and volume adjustment keys, as well as mute. [https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/198197 bug report] has been filed about this, and you can subscribe to it to follow the progress. A workaround is to boot the 2.6.22 kernel
supplied with Gutsy. This is already on your system by default after an upgrade from Gutsy to Hardy.
See ChangeDefaultOS for details on how to change the "default" line in /boot/grub/menu.lst and then run ''sudo update-grub''' for the change to take effect.

=== Annoyances ===

Also, the issue with "sound after suspend" described below in the Gutsy section
remains with Hardy.

== Ubuntu 7.10 Gutsy Gibbon ==

Things generally work fine, with the following notes

=== Power Management ===

==== Sound After Suspend ====

Sound may not work after a suspend/resume cycle. The problem may be that some volume levels have been muted. To fix that save the following into a script:

#!/bin/sh
mixers="Master PCM CD"
for mixer in $mixers ; do
/usr/bin/amixer -q sset $mixer mute
/usr/bin/amixer -q sset $mixer unmute
done

The script should save to /etc/acpi/resume.d/70-sound-unmute.sh
Make sure the file is executable

chmod +x /etc/acpi/resume.d/70-sound-unmute.sh

In theory, that should make sound work automatically after suspend. It still may not, but you can run the script manually to bring sound back:

sh /etc/acpi/resume.d/70-sound-unmute.sh

=== Dual Monitors ===

Gutsy Gibbon has a new "Screens and Graphics" preferences area. It shows a second monitor possibility. Trying a test does make both the LCD and external screen active as one big gray monitor...but only for the test. Choosing the option to accept the settings does not actually cause monitor-spanning to work, but monitor mirroring does.

=== CPU Frequency Scaling ===

CPU Frequency Scaling seems to be working automatically. To see your current speed level, activate the CPU Frequency Scaling Monitor Applet. Right click on the toolbar and select "add to panel". You can search for "Frequency" to find it.

== Ubuntu 7.04 Feisty Fawn ==

=== Power Management ===

The chips in T23s have the ability to run at speeds slower than their maximum, in order to save power. To see your current speed level, activate the CPU Frequency Scaling Monitor Applet. Right click on the toolbar and select "add to panel". You can search for "Frequency" to find it.

You can also enable this applet to allow you manually change the speed and scaling policy. To do that, run this in a terminal: "sudo dpkg-reconfigure gnome-applets".

These instructions are also available [http://www.ubuntugeek.com/howto-change-cpu-frequency-scaling-in-ubuntu.html illustrated with screenshots].

You may also need to add a couple of lines to "/etc/modules" to allow you to be able to change the processor speed and governor. The lines are:

acpi-cpufreq
cpufreq_ondemand

These will now be loaded on at boot time. To activate them immediately:

sudo modprobe acpi-cpufreq
sudo modprobe cpufreq_ondemand

Some technical details are explained on the [[SpeedStep]] page.

== External Resources ==

*[http://del.icio.us/tags/ubuntu+t23 Bookmarks tagged with Ubuntu and T23] on del.icio.us
*[http://ubuntuforums.org/tags/index.php/t23/ Forum posts tagged with T23] on ubuntuforums.org
[[Category:T23]]
[[Category:Ubuntu 7.04]]

Installing Ubuntu on a ThinkPad T23

2008-04-28T02:25:01Z

MarkStosberg: /* Ubuntu 8.04 Hardy Heron */ add bug report report to Caps/Control regression.

== Ubuntu 8.04 Hardy Heron ==

The upgrade from Gutsy to Hardy goes fairly smoothly.

=== Regressions ===

The following features quit working after the upgrade:

* Having Caps Lock work as a second Control key works, but the Caps Lock status light toggles on and off as Control is pressed. This is set in System: Preferences: Keyboard: Layouts: Layout Options: Ctrl Key Position. Track Ubuntu [https://bugs.launchpad.net/ubuntu/+bug/173350/ Bug #173350] for the latest updates.
* On Screen Display of special key actions quits working. The keys include the brightness and volume adjustment keys, as well as mute. [https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/198197 bug report] has been filed about this, and you can subscribe to it to follow the progress. A workaround is to boot the 2.6.22 kernel
supplied with Gutsy. This is already on your system by default after an upgrade from Gutsy to Hardy.
See ChangeDefaultOS for details on how to change the "default" line in /boot/grub/menu.lst and then run ''sudo update-grub''' for the change to take effect.

=== Annoyances ===

Also, the issue with "sound after suspend" described below in the Gutsy section
remains with Hardy.

== Ubuntu 7.10 Gutsy Gibbon ==

Things generally work fine, with the following notes

=== Power Management ===

==== Sound After Suspend ====

Sound may not work after a suspend/resume cycle. The problem may be that some volume levels have been muted. To fix that save the following into a script:

#!/bin/sh
mixers="Master PCM CD"
for mixer in $mixers ; do
/usr/bin/amixer -q sset $mixer mute
/usr/bin/amixer -q sset $mixer unmute
done

The script should save to /etc/acpi/resume.d/70-sound-unmute.sh
Make sure the file is executable

chmod +x /etc/acpi/resume.d/70-sound-unmute.sh

In theory, that should make sound work automatically after suspend. It still may not, but you can run the script manually to bring sound back:

sh /etc/acpi/resume.d/70-sound-unmute.sh

=== Dual Monitors ===

Gutsy Gibbon has a new "Screens and Graphics" preferences area. It shows a second monitor possibility. Trying a test does make both the LCD and external screen active as one big gray monitor...but only for the test. Choosing the option to accept the settings does not actually cause monitor-spanning to work, but monitor mirroring does.

=== CPU Frequency Scaling ===

CPU Frequency Scaling seems to be working automatically. To see your current speed level, activate the CPU Frequency Scaling Monitor Applet. Right click on the toolbar and select "add to panel". You can search for "Frequency" to find it.

== Ubuntu 7.04 Feisty Fawn ==

=== Power Management ===

The chips in T23s have the ability to run at speeds slower than their maximum, in order to save power. To see your current speed level, activate the CPU Frequency Scaling Monitor Applet. Right click on the toolbar and select "add to panel". You can search for "Frequency" to find it.

You can also enable this applet to allow you manually change the speed and scaling policy. To do that, run this in a terminal: "sudo dpkg-reconfigure gnome-applets".

These instructions are also available [http://www.ubuntugeek.com/howto-change-cpu-frequency-scaling-in-ubuntu.html illustrated with screenshots].

You may also need to add a couple of lines to "/etc/modules" to allow you to be able to change the processor speed and governor. The lines are:

acpi-cpufreq
cpufreq_ondemand

These will now be loaded on at boot time. To activate them immediately:

sudo modprobe acpi-cpufreq
sudo modprobe cpufreq_ondemand

Some technical details are explained on the [[SpeedStep]] page.

== External Resources ==

*[http://del.icio.us/tags/ubuntu+t23 Bookmarks tagged with Ubuntu and T23] on del.icio.us
*[http://ubuntuforums.org/tags/index.php/t23/ Forum posts tagged with T23] on ubuntuforums.org
[[Category:T23]]
[[Category:Ubuntu 7.04]]

Installing Ubuntu on a ThinkPad T23

2008-04-28T02:11:55Z

MarkStosberg: /* Ubuntu 8.04 Hardy Heron */ provide workaround for non-working OSD On T23 after Hardy upgrade.

== Ubuntu 8.04 Hardy Heron ==

The upgrade from Gutsy to Hardy goes family smoothly. The following features quit working after the upgrade:

* Having Caps Lock work as a second Control key quits working. This still show as being set correctly in System: Preferences: Keyboard: Layouts: Layout Options: Ctrl Key Position.
* On Screen Display of special key actions quits working. The keys include the brightness and volume adjustment keys, as well as mute. [https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/198197 bug report] has been filed about this, and you can subscribe to it to follow the progress. A workaround is to boot the 2.6.22 kernel
supplied with Gutsy. This is already on your system by default after an upgrade from Gutsy to Hardy.
See ChangeDefaultOS for details on how to change the "default" line in /boot/grub/menu.lst and then run ''sudo update-grub''' for the change to take effect.

Also, the issue with "sound after suspend" described below in the Gutsy section
remains with Hardy.

== Ubuntu 7.10 Gutsy Gibbon ==

Things generally work fine, with the following notes

=== Power Management ===

==== Sound After Suspend ====

Sound may not work after a suspend/resume cycle. The problem may be that some volume levels have been muted. To fix that save the following into a script:

#!/bin/sh
mixers="Master PCM CD"
for mixer in $mixers ; do
/usr/bin/amixer -q sset $mixer mute
/usr/bin/amixer -q sset $mixer unmute
done

The script should save to /etc/acpi/resume.d/70-sound-unmute.sh
Make sure the file is executable

chmod +x /etc/acpi/resume.d/70-sound-unmute.sh

In theory, that should make sound work automatically after suspend. It still may not, but you can run the script manually to bring sound back:

sh /etc/acpi/resume.d/70-sound-unmute.sh

=== Dual Monitors ===

Gutsy Gibbon has a new "Screens and Graphics" preferences area. It shows a second monitor possibility. Trying a test does make both the LCD and external screen active as one big gray monitor...but only for the test. Choosing the option to accept the settings does not actually cause monitor-spanning to work, but monitor mirroring does.

=== CPU Frequency Scaling ===

CPU Frequency Scaling seems to be working automatically. To see your current speed level, activate the CPU Frequency Scaling Monitor Applet. Right click on the toolbar and select "add to panel". You can search for "Frequency" to find it.

== Ubuntu 7.04 Feisty Fawn ==

=== Power Management ===

The chips in T23s have the ability to run at speeds slower than their maximum, in order to save power. To see your current speed level, activate the CPU Frequency Scaling Monitor Applet. Right click on the toolbar and select "add to panel". You can search for "Frequency" to find it.

You can also enable this applet to allow you manually change the speed and scaling policy. To do that, run this in a terminal: "sudo dpkg-reconfigure gnome-applets".

These instructions are also available [http://www.ubuntugeek.com/howto-change-cpu-frequency-scaling-in-ubuntu.html illustrated with screenshots].

You may also need to add a couple of lines to "/etc/modules" to allow you to be able to change the processor speed and governor. The lines are:

acpi-cpufreq
cpufreq_ondemand

These will now be loaded on at boot time. To activate them immediately:

sudo modprobe acpi-cpufreq
sudo modprobe cpufreq_ondemand

Some technical details are explained on the [[SpeedStep]] page.

== External Resources ==

*[http://del.icio.us/tags/ubuntu+t23 Bookmarks tagged with Ubuntu and T23] on del.icio.us
*[http://ubuntuforums.org/tags/index.php/t23/ Forum posts tagged with T23] on ubuntuforums.org
[[Category:T23]]
[[Category:Ubuntu 7.04]]

Installing Ubuntu on a ThinkPad T23

2008-04-28T01:26:35Z

MarkStosberg: /* Ubuntu 8.04 Hardy Heron */ link to specific bug report in Ubuntu

== Ubuntu 8.04 Hardy Heron ==

The upgrade from Gutsy to Hardy goes family smoothly. The following features quit working after the upgrade:

* Having Caps Lock work as a second Control key quits working. This still show as being set correctly in System: Preferences: Keyboard: Layouts: Layout Options: Ctrl Key Position.
* On Screen Display of special key actions quits working. The keys include the brightness and volume adjustment keys, as well as mute. [https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/198197 bug report] has been filed about this, and you can subscribe to it to follow the progress.

Also, the issue with "sound after suspend" described below in the Gutsy section
remains with Hardy.

== Ubuntu 7.10 Gutsy Gibbon ==

Things generally work fine, with the following notes

=== Power Management ===

==== Sound After Suspend ====

Sound may not work after a suspend/resume cycle. The problem may be that some volume levels have been muted. To fix that save the following into a script:

#!/bin/sh
mixers="Master PCM CD"
for mixer in $mixers ; do
/usr/bin/amixer -q sset $mixer mute
/usr/bin/amixer -q sset $mixer unmute
done

The script should save to /etc/acpi/resume.d/70-sound-unmute.sh
Make sure the file is executable

chmod +x /etc/acpi/resume.d/70-sound-unmute.sh

In theory, that should make sound work automatically after suspend. It still may not, but you can run the script manually to bring sound back:

sh /etc/acpi/resume.d/70-sound-unmute.sh

=== Dual Monitors ===

Gutsy Gibbon has a new "Screens and Graphics" preferences area. It shows a second monitor possibility. Trying a test does make both the LCD and external screen active as one big gray monitor...but only for the test. Choosing the option to accept the settings does not actually cause monitor-spanning to work, but monitor mirroring does.

=== CPU Frequency Scaling ===

CPU Frequency Scaling seems to be working automatically. To see your current speed level, activate the CPU Frequency Scaling Monitor Applet. Right click on the toolbar and select "add to panel". You can search for "Frequency" to find it.

== Ubuntu 7.04 Feisty Fawn ==

=== Power Management ===

The chips in T23s have the ability to run at speeds slower than their maximum, in order to save power. To see your current speed level, activate the CPU Frequency Scaling Monitor Applet. Right click on the toolbar and select "add to panel". You can search for "Frequency" to find it.

You can also enable this applet to allow you manually change the speed and scaling policy. To do that, run this in a terminal: "sudo dpkg-reconfigure gnome-applets".

These instructions are also available [http://www.ubuntugeek.com/howto-change-cpu-frequency-scaling-in-ubuntu.html illustrated with screenshots].

You may also need to add a couple of lines to "/etc/modules" to allow you to be able to change the processor speed and governor. The lines are:

acpi-cpufreq
cpufreq_ondemand

These will now be loaded on at boot time. To activate them immediately:

sudo modprobe acpi-cpufreq
sudo modprobe cpufreq_ondemand

Some technical details are explained on the [[SpeedStep]] page.

== External Resources ==

*[http://del.icio.us/tags/ubuntu+t23 Bookmarks tagged with Ubuntu and T23] on del.icio.us
*[http://ubuntuforums.org/tags/index.php/t23/ Forum posts tagged with T23] on ubuntuforums.org
[[Category:T23]]
[[Category:Ubuntu 7.04]]

Installing Ubuntu on a ThinkPad T23

2008-04-28T01:13:49Z

MarkStosberg: /* Ubuntu 8.04 Hardy Heron */ Note problems experience with the Hardy Heron upgrade on a T23.

== Ubuntu 8.04 Hardy Heron ==

The upgrade from Gutsy to Hardy goes family smoothly. The following features quit working after the upgrade:

* Having Caps Lock work as a second Control key quits working. This still show as being set correctly in System: Preferences: Keyboard: Layouts: Layout Options: Ctrl Key Position.
* On Screen Display of special key actions quits working. The keys include the brightness and volume adjustment keys, as well as mute.

Also, the issue with "sound after suspend" described below in the Gutsy section
remains with Hardy.

== Ubuntu 7.10 Gutsy Gibbon ==

Things generally work fine, with the following notes

=== Power Management ===

==== Sound After Suspend ====

Sound may not work after a suspend/resume cycle. The problem may be that some volume levels have been muted. To fix that save the following into a script:

#!/bin/sh
mixers="Master PCM CD"
for mixer in $mixers ; do
/usr/bin/amixer -q sset $mixer mute
/usr/bin/amixer -q sset $mixer unmute
done

The script should save to /etc/acpi/resume.d/70-sound-unmute.sh
Make sure the file is executable

chmod +x /etc/acpi/resume.d/70-sound-unmute.sh

In theory, that should make sound work automatically after suspend. It still may not, but you can run the script manually to bring sound back:

sh /etc/acpi/resume.d/70-sound-unmute.sh

=== Dual Monitors ===

Gutsy Gibbon has a new "Screens and Graphics" preferences area. It shows a second monitor possibility. Trying a test does make both the LCD and external screen active as one big gray monitor...but only for the test. Choosing the option to accept the settings does not actually cause monitor-spanning to work, but monitor mirroring does.

=== CPU Frequency Scaling ===

CPU Frequency Scaling seems to be working automatically. To see your current speed level, activate the CPU Frequency Scaling Monitor Applet. Right click on the toolbar and select "add to panel". You can search for "Frequency" to find it.

== Ubuntu 7.04 Feisty Fawn ==

=== Power Management ===

The chips in T23s have the ability to run at speeds slower than their maximum, in order to save power. To see your current speed level, activate the CPU Frequency Scaling Monitor Applet. Right click on the toolbar and select "add to panel". You can search for "Frequency" to find it.

You can also enable this applet to allow you manually change the speed and scaling policy. To do that, run this in a terminal: "sudo dpkg-reconfigure gnome-applets".

These instructions are also available [http://www.ubuntugeek.com/howto-change-cpu-frequency-scaling-in-ubuntu.html illustrated with screenshots].

You may also need to add a couple of lines to "/etc/modules" to allow you to be able to change the processor speed and governor. The lines are:

acpi-cpufreq
cpufreq_ondemand

These will now be loaded on at boot time. To activate them immediately:

sudo modprobe acpi-cpufreq
sudo modprobe cpufreq_ondemand

Some technical details are explained on the [[SpeedStep]] page.

== External Resources ==

*[http://del.icio.us/tags/ubuntu+t23 Bookmarks tagged with Ubuntu and T23] on del.icio.us
*[http://ubuntuforums.org/tags/index.php/t23/ Forum posts tagged with T23] on ubuntuforums.org
[[Category:T23]]
[[Category:Ubuntu 7.04]]

Installing Ubuntu on a ThinkPad T23

2008-04-27T23:51:55Z

MarkStosberg: add new Hardy section

== Ubuntu 8.04 Hardy Heron ==

The upgrade from Gutsy to Hardy goes smoothly.

The issue with "sound after suspend" described below in the Gutsy section
remains with Hardy.

== Ubuntu 7.10 Gutsy Gibbon ==

Things generally work fine, with the following notes

=== Power Management ===

==== Sound After Suspend ====

Sound may not work after a suspend/resume cycle. The problem may be that some volume levels have been muted. To fix that save the following into a script:

#!/bin/sh
mixers="Master PCM CD"
for mixer in $mixers ; do
/usr/bin/amixer -q sset $mixer mute
/usr/bin/amixer -q sset $mixer unmute
done

The script should save to /etc/acpi/resume.d/70-sound-unmute.sh
Make sure the file is executable

chmod +x /etc/acpi/resume.d/70-sound-unmute.sh

In theory, that should make sound work automatically after suspend. It still may not, but you can run the script manually to bring sound back:

sh /etc/acpi/resume.d/70-sound-unmute.sh

=== Dual Monitors ===

Gutsy Gibbon has a new "Screens and Graphics" preferences area. It shows a second monitor possibility. Trying a test does make both the LCD and external screen active as one big gray monitor...but only for the test. Choosing the option to accept the settings does not actually cause monitor-spanning to work, but monitor mirroring does.

=== CPU Frequency Scaling ===

CPU Frequency Scaling seems to be working automatically. To see your current speed level, activate the CPU Frequency Scaling Monitor Applet. Right click on the toolbar and select "add to panel". You can search for "Frequency" to find it.

== Ubuntu 7.04 Feisty Fawn ==

=== Power Management ===

The chips in T23s have the ability to run at speeds slower than their maximum, in order to save power. To see your current speed level, activate the CPU Frequency Scaling Monitor Applet. Right click on the toolbar and select "add to panel". You can search for "Frequency" to find it.

You can also enable this applet to allow you manually change the speed and scaling policy. To do that, run this in a terminal: "sudo dpkg-reconfigure gnome-applets".

These instructions are also available [http://www.ubuntugeek.com/howto-change-cpu-frequency-scaling-in-ubuntu.html illustrated with screenshots].

You may also need to add a couple of lines to "/etc/modules" to allow you to be able to change the processor speed and governor. The lines are:

acpi-cpufreq
cpufreq_ondemand

These will now be loaded on at boot time. To activate them immediately:

sudo modprobe acpi-cpufreq
sudo modprobe cpufreq_ondemand

Some technical details are explained on the [[SpeedStep]] page.

== External Resources ==

*[http://del.icio.us/tags/ubuntu+t23 Bookmarks tagged with Ubuntu and T23] on del.icio.us
*[http://ubuntuforums.org/tags/index.php/t23/ Forum posts tagged with T23] on ubuntuforums.org
[[Category:T23]]
[[Category:Ubuntu 7.04]]

Installing Ubuntu on a ThinkPad T23

2007-12-13T01:33:17Z

MarkStosberg: /* Sound After Suspend */ show manual tip for bringing sound back.

== Ubuntu 7.10 Gutsy Gibbon ==

Things generally work fine, with the following notes

=== Power Management ===

==== Sound After Suspend ====

Sound may not work after a suspend/resume cycle. The problem may be that some volume levels have been muted. To fix that save the following into a script:

#!/bin/sh
mixers="Master PCM CD"
for mixer in $mixers ; do
/usr/bin/amixer -q sset $mixer mute
/usr/bin/amixer -q sset $mixer unmute
done

The script should save to /etc/acpi/resume.d/70-sound-unmute.sh
Make sure the file is executable

chmod +x /etc/acpi/resume.d/70-sound-unmute.sh

In theory, that should make sound work automatically after suspend. It still may not, but you can run the script manually to bring sound back:

sh /etc/acpi/resume.d/70-sound-unmute.sh

=== Dual Monitors ===

Gutsy Gibbon has a new "Screens and Graphics" preferences area. It shows a second monitor possibility. Trying a test does make both the LCD and external screen active as one big gray monitor...but only for the test. Choosing the option to accept the settings does not actually cause monitor-spanning to work, but monitor mirroring does.

=== CPU Frequency Scaling ===

CPU Frequency Scaling seems to be working automatically. To see your current speed level, activate the CPU Frequency Scaling Monitor Applet. Right click on the toolbar and select "add to panel". You can search for "Frequency" to find it.

== Ubuntu 7.04 Feisty Fawn ==

=== Power Management ===

The chips in T23s have the ability to run at speeds slower than their maximum, in order to save power. To see your current speed level, activate the CPU Frequency Scaling Monitor Applet. Right click on the toolbar and select "add to panel". You can search for "Frequency" to find it.

You can also enable this applet to allow you manually change the speed and scaling policy. To do that, run this in a terminal: "sudo dpkg-reconfigure gnome-applets".

These instructions are also available [http://www.ubuntugeek.com/howto-change-cpu-frequency-scaling-in-ubuntu.html illustrated with screenshots].

You may also need to add a couple of lines to "/etc/modules" to allow you to be able to change the processor speed and governor. The lines are:

acpi-cpufreq
cpufreq_ondemand

These will now be loaded on at boot time. To activate them immediately:

sudo modprobe acpi-cpufreq
sudo modprobe cpufreq_ondemand

Some technical details are explained on the [[SpeedStep]] page.

== External Resources ==

*[http://del.icio.us/tags/ubuntu+t23 Bookmarks tagged with Ubuntu and T23] on del.icio.us
*[http://ubuntuforums.org/tags/index.php/t23/ Forum posts tagged with T23] on ubuntuforums.org
[[Category:T23]]
[[Category:Ubuntu 7.04]]

Installing Ubuntu on a ThinkPad T23

2007-12-04T04:40:23Z

MarkStosberg: Post a tip for fixing sound-after-suspend with Ubuntu on a T23.

== Ubuntu 7.10 Gutsy Gibbon ==

Things generally work fine, with the following notes

=== Power Management ===

==== Sound After Suspend ====

Sound may not work after a suspend/resume cycle. The problem may be that some volume levels have been muted. To fix that save the following into a script:

#!/bin/sh
mixers="Master PCM CD"
for mixer in $mixers ; do
/usr/bin/amixer -q sset $mixer mute
/usr/bin/amixer -q sset $mixer unmute
done

The script should save to /etc/acpi/resume.d/70-sound-unmute.sh
Make sure the file is executable

chmod +x /etc/acpi/resume.d/70-sound-unmute.sh

Now, after a suspend/resume cycle, sound should work automatically!

=== Dual Monitors ===

Gutsy Gibbon has a new "Screens and Graphics" preferences area. It shows a second monitor possibility. Trying a test does make both the LCD and external screen active as one big gray monitor...but only for the test. Choosing the option to accept the settings does not actually cause monitor-spanning to work, but monitor mirroring does.

=== CPU Frequency Scaling ===

CPU Frequency Scaling seems to be working automatically. To see your current speed level, activate the CPU Frequency Scaling Monitor Applet. Right click on the toolbar and select "add to panel". You can search for "Frequency" to find it.

== Ubuntu 7.04 Feisty Fawn ==

=== Power Management ===

The chips in T23s have the ability to run at speeds slower than their maximum, in order to save power. To see your current speed level, activate the CPU Frequency Scaling Monitor Applet. Right click on the toolbar and select "add to panel". You can search for "Frequency" to find it.

You can also enable this applet to allow you manually change the speed and scaling policy. To do that, run this in a terminal: "sudo dpkg-reconfigure gnome-applets".

These instructions are also available [http://www.ubuntugeek.com/howto-change-cpu-frequency-scaling-in-ubuntu.html illustrated with screenshots].

You may also need to add a couple of lines to "/etc/modules" to allow you to be able to change the processor speed and governor. The lines are:

acpi-cpufreq
cpufreq_ondemand

These will now be loaded on at boot time. To activate them immediately:

sudo modprobe acpi-cpufreq
sudo modprobe cpufreq_ondemand

Some technical details are explained on the [[SpeedStep]] page.

== External Resources ==

*[http://del.icio.us/tags/ubuntu+t23 Bookmarks tagged with Ubuntu and T23] on del.icio.us
*[http://ubuntuforums.org/tags/index.php/t23/ Forum posts tagged with T23] on ubuntuforums.org
[[Category:T23]]
[[Category:Ubuntu 7.04]]

Sample Fn-F7 script

2007-11-27T23:30:21Z

MarkStosberg: typo fix

This guide will help you configure Fn-F7 key combination to toggle between internal, mirror, external, or both screens. This was tested on ThinkPad X60s running Fedora 8, please comment if it works or does not work for you.

Works like a charm on X61s with Xubuntu 7.10.
Working with R60e with some modifications noted below.

==configuring the virtual screen size==
Add a "Virtual" statement to your /etc/X11/xorg.conf, the total resolution should be large enough to fit all your screens in the configuration you want, for example if you have 1600x1200 monitor to the left of your internal 1024x768 monitor, your total max resolution is 2624x1200 (See [[Xorg RandR 1.2]] for more details):

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
<b>Virtual 2624 1200</b>
EndSubSection
EndSection

Restart X server at this point (i.e. logout and login).

== configuring acpi ==
Create /etc/acpi/events/thinkpad.conf:

event=ibm/hotkey HKEY 00000080 00001007
action=/usr/local/sbin/thinkpad-fn-f7

or you may (eg Ubuntu 7.10) already have /etc/acpi/events/ibm-videobtn
# /etc/acpi/events/ibm-videobtn
# This is called when the user presses the video button. It is currently
# a placeholder.
event=ibm/hotkey HKEY 00000080 00001007
action=/bin/true

in which case modify the line 'action=/bin/true' to run the script as above.

It may also be necessary to enable acpi events as per [[How to get special keys to work]] with (in root terminal)
{{cmdroot|echo enable,0x084e > /proc/acpi/ibm/hotkey}}
Note this command isn't persistent. so you will also need to add the line to /etc/rc.local to enable hotkeys at boot, and to re-enable the hotkeys after suspend to disk or RAM, create the file
/etc/acpi/resume.d/91-ibm-hotkey-enable.sh consisting of

#!/bin/bash
# enable ibm-hotkeys (specifically Fn2, Fn7)
# 12 bit mask, little end is F1 default 0x080c = F12+F4+F3
echo enable,0x084e > /proc/acpi/ibm/hotkey

ref: [[http://tilmanfrosch.de/wp/index.php/2007/05/05/howto-make-a-ubuntu-linux-on-an-ibm-t41-thinkpad-work-with-an-external-widescreen-wxga-display/ frosch.org.uk]] and [[http://ibm-acpi.sourceforge.net/README ibm-acpi.sourceforge]]

==identify output devices==
Note the names of your output devices as you will have to change EXTERNAL_OUTPUT and INTERNAL_OUTPUT to what xrandr shows, for example VGA and LVDS in this case:

$ xrandr -q
'''VGA''' connected 1600x1200+0+0 (normal left inverted right x axis y axis) 432mm x 324mm
...
'''LVDS''' connected (normal left inverted right x axis y axis)

==The bash script==
Create /usr/local/sbin/thinkpad-fn-f7, you can set EXTERNAL_LOCATION to one of: left, right, above, or below.

#!/bin/bash

# External output may be "VGA" or "VGA-0" or "DVI-0"
EXTERNAL_OUTPUT="'''VGA'''"
INTERNAL_OUTPUT="'''LVDS'''"
EXTERNAL_LOCATION="'''left'''"

# Figure out which user and X11 display to work on
# TODO there has to be a better way to do this?
X_USER=$(w -h -s | grep ":[0-9]" | head -1 | awk '{print $1}')
export DISPLAY=$(w -h -s | grep ":[0-9]" | head -1 | awk '{print $3}')

# Switch to X user if necessary
if [ "$X_USER" != "$USER" ]; then
SU="su $X_USER -c"
fi

case "$EXTERNAL_LOCATION" in
left|LEFT)
EXTERNAL_LOCATION="--left-of $INTERNAL_OUTPUT"
;;
right|RIGHT)
EXTERNAL_LOCATION="--right-of $INTERNAL_OUTPUT"
;;
top|TOP|above|ABOVE)
EXTERNAL_LOCATION="--above $INTERNAL_OUTPUT"
;;
bottom|BOTTOM|below|BELOW)
EXTERNAL_LOCATION="--below $INTERNAL_OUTPUT"
;;
*)
EXTERNAL_LOCATION="--left-of $INTERNAL_OUTPUT"
;;
esac

# Figure out current state
INTERNAL_STATE=$($SU xrandr | grep ^$INTERNAL_OUTPUT | grep con | sed "s/.*connected //" | sed "s/(.*//")
EXTERNAL_STATE=$($SU xrandr | grep ^$EXTERNAL_OUTPUT | grep con | sed "s/.*connected //" | sed "s/(.*//")

if [ -z "$INTERNAL_STATE" ]; then
STATE="external"
elif [ -z "$EXTERNAL_STATE" ]; then
STATE="internal"
else
INTERNAL_STATE=$(echo $INTERNAL_STATE | sed "s/[0-9]*x[0-9]*//")
EXTERNAL_STATE=$(echo $EXTERNAL_STATE | sed "s/[0-9]*x[0-9]*//")
if [ "$INTERNAL_STATE" = "$EXTERNAL_STATE" ]; then
STATE="mirror"
else
STATE="both"
fi
fi

function screen_external(){
$SU "xrandr --output $INTERNAL_OUTPUT --off"
$SU "xrandr --output $EXTERNAL_OUTPUT --auto"
}

function screen_internal(){
$SU "xrandr --output $EXTERNAL_OUTPUT --off"
$SU "xrandr --output $INTERNAL_OUTPUT --auto"
}

function screen_mirror(){
$SU "xrandr --output $INTERNAL_OUTPUT --auto"
$SU "xrandr --output $EXTERNAL_OUTPUT --auto --same-as $INTERNAL_OUTPUT"
}

function screen_both(){
$SU "xrandr --output $INTERNAL_OUTPUT --auto"
$SU "xrandr --output $EXTERNAL_OUTPUT --auto $EXTERNAL_LOCATION"
}

function screen_toggle(){
case "$STATE" in
internal)
screen_mirror
;;
mirror)
screen_external
;;
external)
screen_both
;;
both)
screen_internal
;;
*)
screen_internal
;;
esac
}

# What should we do?
DO="$1"
if [ -z "$DO" ]; then
if [ $(basename $0) = "thinkpad-fn-f7" ]; then
DO="toggle"
fi
fi

case "$DO" in
toggle)
screen_toggle
;;
internal)
screen_internal
;;
external)
screen_external
;;
mirror)
screen_mirror
;;
both)
screen_both
;;
status)
echo "Current Fn-F7 state is: $STATE"
echo
echo "Attached monitors:"
$SU xrandr | grep "\Wconnected" | sed "s/^/ /"
;;
*)
echo "usage: $0 <command>" >&2
echo >&2
echo " commands:" >&2
echo " status" >&2
echo " internal" >&2
echo " external" >&2
echo " mirror" >&2
echo " both" >&2
echo " toggle" >&2
echo >&2
;;
esac

== set permissions and restart acpi ==
As root, or using sudo run the following commands,

{{cmduser|sudo chmod 755 /usr/local/sbin/thinkpad-fn-f7}}
{{cmduser|sudo service acpid restart}}
OR
{{cmduser|sudo /etc/init.d/acpid restart}}

You should be ready to go, just press Fn-F7 to try.

==Alternative script using .Xauthority rather than su ==
Use this script as an alternative
action=/usr/local/sbin/toggle-display.sh
for /etc/acpi/events/ibm-videobtn

#!/bin/bash
# usr/local/sbin/toggle-display.sh
# based on /etc/acpi/screenblank.sh (Ubuntu 7.10)
#
# . /usr/share/acpi-support/power-funcs # for getXuser
umask 022;
PATH="$PATH:/usr/bin/X11"
getXuser() {
user=`finger| grep -m1 ":$displaynum " | awk '{print $1}'`
if [ x"$user" = x"" ]; then
user=`finger| grep -m1 ":$displaynum" | awk '{print $1}'`
fi
if [ x"$user" != x"" ]; then
userhome=`getent passwd $user | cut -d: -f6`
export XAUTHORITY=$userhome/.Xauthority
else
export XAUTHORITY=""
fi
}
# end of getXuser from /usr/share/acpi-support/power-funcs
#
for x in /tmp/.X11-unix/*; do
displaynum=`echo $x | sed s#/tmp/.X11-unix/X##`
getXuser;
if [ x"$XAUTHORITY" != x"" ]; then
export DISPLAY=":$displaynum"
## . /usr/share/acpi-support/screenblank.sh
/usr/local/bin/toggle.py
fi
done

Each user has an ~/.Xauthority file with one line for each X display containing a 'magic cookie' (Run {{cmduser| xauth list}} to see the contents). The Xserver reads the record in ~/.Xauthority matching its display. When an X client application starts it also looks for that record and passes the magic cookie to the server. If it matches, the connection to the Xserver is allowed. The above example runs the python script below but could run a modified version of /usr/local/sbin/thinkpad-fn-f7 without the USER, and DISPLAY detection SU commands.

== A Python Toggle script ==
This is a somewhat over-elaborate script which could be cut down when run by the /usr/local/sbin/toggle-display.sh script above. It was written to explore all the possibilities rather than economy of execution. The functions 'toggle_full', 'position', 'toggle_limited' and the OptionParser in 'main' may be omitted with suitable changes to function7. The appropriate outputs can be specified on the command line and it is not necessary to call it via acpi.
eg you can run it as {{cmduser|/usr/local/bin/toggle.py --help}}

#! /usr/bin/python
# -*- coding: utf-8 -*-
#
# stinkpad(a)blueyonder.co.uk 2007-11-26
"""Toggle internal and external displays (equivalent to ThinkPad Fn7)
Simple; cloned: on+off, on+on, off+on.
Full; as simple plus xinerama: right, below, left, above.
Limited; as full but display will overlap if virtual screen is too small.
Use 'xrandr -q' to determine output names.
Further information: http://www.thinkwiki.org/wiki/Xorg_RandR_1.2
"""
__usage__ = "usage: %prog [--help]|[[-i internal][-e external][-d displays]]"
__version__ = "toggle [djclark.eu 2007-11-26]"
#
# Output names; Intel: LVDS VGA TV TMDS-1 TMDS-2
# ATI: LVDS VGA-0 S-video DVI-0
LAPTOP = 'LVDS'
MONITOR = 'VGA'
SEQUENCE = 'simple'
#
import sys
import os
import re

# "LVDS connected 1024x768+0+0 (normal left inverted right) 304mm x 228mm"
REGEX_OUTPUT = re.compile(r'''
(?x) # ignore whitespace
^ # start of string
(?P<output>[A-Za-z0-9\-]*)[ ] # LVDS VGA etc
(?P<connect>(dis)?connected)[ ] # dis/connected
(( # a group
(?P<width>\d+)x # either 1024x768+0+0
(?P<height>\d+)[+]
(?P<horizontal>\d+)[+]
(?P<vertical>\d+)
)|[\D]) # or not a digit
.* # ignore rest of line
''')

# "Screen 0: minimum 320 x 200, current 1024 x 768, maximum 2624 x 1968"
REGEX_SCREEN = re.compile(r'''
(?x) # ignore whitespace
^ # start of string
Screen[ ]
(?P<screen>\d)[: ]+
minimum[ ]
(?P<minWidth>\d+)[ x]+
(?P<minHeight>\d+)[, ]+
current[ ]+
(?P<curWidth>\d+)[ x]+
(?P<curHeight>\d+)[, ]+
maximum[ ]+
(?P<maxWidth>\d+)[ x]+
(?P<maxHeight>\d+)
''')

def toggle_simple(d0, d1):
"""Toggle display states: on+off, on+on, off+on"""
if d1['connect'] == 'disconnected': # external unplugged
return ('auto','off','') # switch off external
if d1['width'] is 0: # external off
return ('auto','auto','') # both on
if d0['width'] is 0: # laptop off
return ('auto','off','') # laptop on
return ('off','auto','') # both on, laptop off

def toggle_full(d0, d1):
"""Toggle display states: 1+0, 1+1, 0+1, 1+E, 1+S, 1+W, 1+N"""
if d1['connect'] == 'disconnected': # external unplugged
return ('auto','off','') # switch off external
place = '--%s ' + d0['output']
if d1['width'] == 0: # external off
return ('auto','auto',place%'same-as') # external on
if d0['width'] == 0: # laptop off
return ('auto','off','') # laptop on
if d1['horizontal'] > 0: # external to right
return ('auto','auto',place%'below') # make below
if d1['vertical'] > 0: # external below
return ('auto','auto',place%'left-of') # make left
if d0['horizontal'] > 0: # external left
return ('auto','auto',place%'above') # make above
if d0['vertical'] > 0: # external above
return ('off','auto','') # laptop off
return ('auto','auto',place%'right-of') # is same, make right

def position(orientation, da, db, screen):
"""Calculate offset position of second display"""
p = 'auto --pos %sx%s'
if orientation == 'V':
if (da['height'] + db['height']) <= screen['maxHeight']:
return p%(0, da['height'])
return p%(0, screen['maxHeight'] - db['height'])
else:
if (da['width'] + db['width']) <= screen['maxWidth']:
return p%(da['width'],0)
return p%(screen['maxWidth'] - db['width'],0)

def toggle_limited(d0, d1, sz):
"""Toggle display states (overlapped): 1+0,1+1,0+1,1+E,1+S,1+W,1+N"""
if d1['connect'] == 'disconnected': # external unplugged
return ('auto','off') # switch off external
if d1['width'] == 0: # external off
return ('auto --pos 0x0','auto --pos 0x0') # both on
if d0['width'] == 0: # laptop off
return ('auto --pos 0x0','off') # laptop on
if d1['horizontal'] > 0: # external to right
return ('auto --pos 0x0',position('V',d0,d1,sz)) # put *below
if d1['vertical'] > 0: # external below
return (position('H',d1,d0,sz),'auto --pos 0x0') # put *left
if d0['horizontal'] > 0: # external left
return (position('V',d1,d0,sz),'auto --pos 0x0') # put *above
if d0['vertical'] > 0: # external above
return ('off','auto --pos 0x0') # laptop off
return ('auto --pos 0x0',position('H',d0,d1,sz)) # both, put*right

class DisplayNameError(UnboundLocalError):
"""Internal or External Display Name not found by xrandr -q """

def function7(disp0=LAPTOP, disp1=MONITOR, seq=SEQUENCE):
"""Use xrandr to read current display state and change state"""
for line in os.popen('xrandr -q').read().splitlines():
if line.startswith(disp0,0) :
d0_state = REGEX_OUTPUT.match(line).groupdict()
elif line.startswith(disp1,0):
d1_state = REGEX_OUTPUT.match(line).groupdict()
elif line.startswith('Screen',0):
screen_size = REGEX_SCREEN.match(line).groupdict()
else:
pass
for i in ('width','height','horizontal','vertical'):
try:
d0_state[i] = int(d0_state[i])
except TypeError:
d0_state[i] = 0
except UnboundLocalError:
raise DisplayNameError, 'Internal Display: %s not found'% disp0
try:
d1_state[i] = int(d1_state[i])
except TypeError:
d1_state[i] = 0
except UnboundLocalError:
raise DisplayNameError, 'External Display: %s not found'% disp1
for i in screen_size.keys():
try:
screen_size[i] = int(screen_size[i])
except TypeError:
screen_size[i] = 0
#
toggle = toggle_simple
xrandr ='xrandr --output '+disp0+' --%s --output '+disp1+' --%s %s'
if seq == 'full':
toggle = toggle_full
if seq == 'limited':
toggle = toggle_limited
xrandr ='xrandr --output '+disp0+' --%s --output '+disp1+' --%s'
os.popen(xrandr % toggle(d0_state, d1_state, screen_size))
else:
os.popen(xrandr % toggle(d0_state, d1_state))

def main():
""" Command line options """
global LAPTOP,MONITOR,SEQUENCE
from optparse import OptionParser
p = OptionParser(usage=__usage__, version=__version__, description=__doc__)
p.set_defaults(internal=LAPTOP, external=MONITOR, displays=SEQUENCE)
p.set_defaults(separator='comma', column=0)
p.add_option('-i','--internal', dest="internal", metavar=LAPTOP,
help="internal display")
p.add_option('-e','--external', dest="external", metavar=MONITOR,
help="external display")
p.add_option('-d','--displays', dest="displays", action="store",
choices=('simple', 'limited', 'full'), metavar=SEQUENCE,
help='simple/limited/full')
(opt, args) = p.parse_args()
try:
function7(opt.internal, opt.external, opt.displays)
except DisplayNameError, err:
print '\n'+str(err)+'\n'
print os.popen('xrandr -q').read()
#
if __name__ == '__main__': #only when run from cmd line
main()

Installing Mandriva Linux on a ThinkPad T20

2007-11-27T01:46:54Z

MarkStosberg: typo fix

=Mandriva 2007=
==Power Management==

Suspend works perfectly under the following conditions.

1. An older 2.6.12 Mandriva kernel is used. This may already be present if you are upgrading,
but should be possible to install after the fact for a fresh install.

2. The sound-restart tweaks to <code>/etc/sysconfig/suspend</code> described below are preserved. For reference,
a complete copy of this file that is known to work is here:

# -*- Mode: shell-script -*-

# Some broken BIOSes, like those found in early Gericom 3xC notebooks,
# won't wake up harddisks from suspend to disk unless they're set to PIO mode
# and 16-bit.
# Don't activate the following two lines unless you're getting
# "hda: lost interrupt" after returning from a suspend to disk.
#SUSPEND_DISK="-q -X0 -q -c0 -q -d0 -q -u0 -q -S0"
#SUSPEND_RESUME="-q -X66 -q -c1 -q -d1 -q -u1 -q -S30"

# If RESTART_NFS is set to yes, NFS filesystems will be unmounted at
# suspend, and remounted at resume (if possible).
RESTART_NFS="no"

# If NET_RESTART is set to yes, the network will be shut down at suspend and
# restarted at resume.
# This is especially useful if you're using DHCP, but usually won't hurt.
RESTART_NETWORK="yes"

# I got frequent problems mainly with scsi-pcmcia-cards on the cardbus. Use
# RESTART_PCMCIA="yes" to stop the whole pcmcia-subsystem on a suspend and
# to start it again after a resume. This can slow down your suspend and resume
# process.
# Use PCMCIA_TIMEOUT in order to set up the PCMCIA timeout.
# Some BIOSes are too buggy to handle cardctl suspend and cardctl resume
# properly, in these cases cardctl eject and cardctl insert can be used instead.
# However, this actually ejects the card on hardware supporting it, so if
# the BIOS isn't buggy, it shouldn't be used. Set PCMCIA_BIOS_BUG to yes if
# you are experiencing problems with PCMCIA cards after a resume.
# Since buggy BIOSes seem to be far more common than hardware that can eject
# PCMCIA cards (and it doesn't make a difference on systems that don't have
# either), it is enabled by default.
RESTART_PCMCIA="yes"
PCMCIA_BIOS_BUG="yes"
PCMCIA_WAIT="yes"
PCMCIA_TIMEOUT="10"

# if you have problems with your X display after returning from suspend mode
# give CHANGE_VT the number of the virtual terminal your X-Server runs on
CHANGE_VT="7"

# Set LOCK_XFREE to yes if you want to lock all your X displays at suspend
LOCK_XFREE="no"

# If you set this to yes, the clock will be synced with the hardware clock
# when the computer returns from suspend mode.
CLOCK_SYNC="yes"

# if your sound sometimes doesn't work after a resume set RESTORESOUND to "yes";
# this will kill all sound applications, remove and start the $SOUNDMODULES
# again
RESTORE_SOUND="yes"
#SOUND_MODULES="sb uart401 sound soundcore maestro cs4281"
SOUND_MODULES="sb uart401 sound soundcore maestro cs4281 snd-cs46xx"

# Sometime USB doen't support well the suspending, specially for mouse
# you may want to activate USBMOUSE_RESTART to make sure that your
# mouse will work, if you want to restart the whole usb system set the
# variable USB_RESTART

# changed from no to yes and back again on 12/16/2006 by mls
USB_RESTART="no"

# the error-beep of your terminal might be set to the default values after a
# resume so set TERMINAL_BEEP to "yes" to restore the values in
# /etc/sysconfig/keyboard
TERMINAL_BEEP="no"
BEEP_LENGTH=2

# List here the Services to Restart between Suspend/Resume
RESTART_SERVICES="haldaemon postfix ntpd xinetd nfs gpm pcmcia irda alsa anacron cpufreq cpufreqd mDNSResponder athcool mysqld"

## APM Specific config
# make an entry in the logfiles whenever the percentage of
# battery power changes below the value specified here
LOGPERCENTCHANGE=10

# warn on specified remainig battery percentage, use negative values
# to disable this feature
WARNPERCENT=5

# use -W to warn all users in a critical power state
ADDPARAMS="-W"

## SWSUSP Specific config
# Use SWSUSP_FORCE_SUSPEND_MODE to force use the SWSUSP feature
# suspension. If empty, this let the suspension
# behaviour unchanged. "0" will force shut off after
# suspension. "1" will force reboot. You can add an optional
# second parameter to tune the suspension display (see swsusp
# documentation for more information).
# p1 = 0 for halt + eatmem p1 = 2 for halt + freemem
# p2 = 2 for progress bar
# p3, p4 are optional debugging options for hackers (see swsusp kernel patch documentation).
# Default: "0 2", i.e. halt, eatmem, progress bar
#SWSUSP_FORCE_SUSPEND_MODE="0 2"

## Automatic waking up config
#Use AUTOWAKE to resume from a suspend to ram after a given amount of time
#and automatically launch a command.
#Useful to have an automatic suspend to disk after some time in
#suspend to ram.
#AUTOWAKE: enable/disable this functionnality
AUTOWAKE="no"
#AUTOWAKE_DELAY: Set delay before automatic resume, in minutes.
AUTOWAKE_DELAY=20
#AUTOWAKE_COMMAND: command to run after automatic resume.
#Use "/usr/bin/pmsuspend disk" if you want to trigger a suspend to disk
AUTOWAKE_COMMAND="/usr/bin/pmsuspend disk"

'''NOTE''': This solution conflicts PCMCIA improvements in the newer kernel, causing wireless cards not tobe recognized. [http://kernel.org/pub/linux/utils/kernel/pcmcia/cardmgr-to-pcmciautils.html details here.] The solution is to replace the newer pcmciautils package with the older pcmcia-cs package from the 2006 distribution.

urpme pcmciautils && urpmi pcmcia-cs

You may temporarily to have to add a 2006 repository source so that the 'pcmcia-cs' package can be found.

===Power Management alternative: use APM===

* noacpi acpi=off apm=on
* Once booted, edit {{/etc/sysconfig/suspend}}. Change RESTORE_SOUND to 'yes', and add {{snd-cs46xx}} to the list of SOUND_MODULES.
* In a terminal:
su
# allow users to run apm
chmod +s /usr/bin/apm
exit
apm --suspend

With that setup, you can just run "apm --suspend" in the future, and suspend/resume should work, including sound after the suspend/resume cycle.

===Power Management Options which failed with the Live CD===

Booting with the default ACPI support, trying Fn-F4 to suspend on this CD or selecting "Suspend" from the battery icon resulted in an error like "INIT PANIC: segmentation violation at 0x804e21d! sleeping for 30 sec."

Even following the steps to enable APM above, Fn-F4 just puts the computer in standby, but does not suspend. Selecting "Suspend" from the battery icon caused the laptop to suspend, but immediately resumed.

===Power Management Options which failed with a hard disk install===

Trying Fn-F4 with the default kernel would suspend and resume the first time, the moon icon never stops
blinking after resume, and further attempts to suspend or shutdown do not complete. Suspend attempts resume
immediately and shutting down hangs at a blitzed-out screen at the end, after the hard drive has spun down.

=Mandriva 2006=
==Basic Installation==
The basic install of {{Mandriva}} Linux 2006 works smoothly on a ThinkPad {{T20}}. Read on for things that need tweaking.

==DVD Notes==

With appropriate software installed, the combination of Mandriva and the T20 plays DVDS fine.
However, the frame rate will be noticeably reduced if the DVD is hotswapped in place of a battery, or if the laptop is suspended and resumed. This DMA-related phenomenon is explained more on the [[UltraBay]] page in the Hotswapping section. The issue is discussed more in a [http://qa.mandriva.com/show_bug.cgi?id=16046 this bug report] which seems to suggest that removing <code>/etc/sysconfig/suspend-scripts/suspend.d/ultrabay</code> could help, at the risk of causing the computer to freeze if the CD/DVD drive is ever removed while the system is running.

==Upgrading from 2005 LE to 2006==
Although the installer ran without incident, look out for several issues to address:

* Several things quit working until I switched to the 2.6.11 kernel that was installed. Notably, sound didn't work and the TrackPoint didn't work. You can use drakboot to change the default corner, or command line jockeys can edit {{path|/etc/lilo.conf}}

* The DVD drive could not be located. It was being sought at {{path|/mnt/cdrom}} but really existed at {{path|/mnt/cdrom2}}. Rebooting seemed to fix this.

* My Orinico wireless card quit working. It was being recognized at "eth0" now instead of "eth1". Copying my settings from the eth1 configuration to the eth0 configuration fixed that.

* Using the TrackPoint in combination with the middle mouse button as a scroll wheel quit working. I got it working by using this bit in my {{path|/etc/X11/xorg.conf}} file.

Section "InputDevice"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "ExplorerPS/2"
Option "Device" "/dev/mouse"
Option "Emulate3Buttons" "true"
Option "XAxisMapping" "4 5"
Option "YAxisMapping" "6 7"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
EndSection

If you haven't editted this file before, select "Run" from the start menu and then run a text editor (such as "kate") as root. Be sure to create an extra copy of the file before you change it in case there is a problem!
To make the changes take effect you'll need to restart X. Rebooting is one way to do that, or you could hold Control-Alt-Backspace to restart the X server.

* The "Suspend" option had disappeared from the KLaptop menu. It was necessary to go into the "Configure KLaptop" dialog and re-setup the "helper applications".

* Selecting "ondemand" as a Performance Profile seems to have no effect, through KLaptop or on the command line. It would be nice to solve this for better life.

* While suspending worked great with Mandriva LE, trying to suspend with APM, now resulted in a reboot upon resuming. What finally worked me was:
** Upgraded to 2.6.12 kernel (not sure if this mattered)
** Make sure acpi and acpid are installed and apmd is not
** Use the built-in suspend key to suspend (Fn-F4). (Using KLaptop instead resulted in no sound upon resume).

* My USB card reader quit working. My fix was to make sure the USB service was started at boot time, and to explicitly load the USB mass storage module at boot time.
**{{cmdroot|ln -s /etc/init.d/usb /etc/rc5.d/S50usb}}
**Edit {{path|/etc/sysconfig/usb}} and set <tt>STORAGE=yes</tt>

==Getting the modem to work==
The modem is not accessible through one of the default serial interfaces. It can, however, be queried through {{path|/dev/tty13}}.

For further information, see [[Installing_Ltmodem_driver_for_Mandriva]].

== Support for the Thinkpad buttons with Kmilo ==

[http://www.kde.me.uk/index.php?page=kmilo Kmilo ] is software that provides on screen feedback and some
extra configuration when using the Thinkpad-specific buttons such as the volume and brightness keys. It
is provided by Mandriva as part of KDE 3.5 bundle for Mandriva 2006. The package name is 'libkmilo1'.
It works after installing that package and rebooting. Now when visting {{path|settings:/Peripherals/}} you'll see
a new icon for "IBM Thinkpad", with a few option to configure it.

=Mandriva 2005 LE=

==Suspend/Resume==

Mandriva controls suspend/resume preferences through the file {{path|/etc/sysconfig/suspend}}.
It is a well-commented text file. Here are two options I set that seemed to help make sound
continue working after a suspend on the T20:

RESTORE_SOUND="yes"
SOUND_MODULES="sb uart401 sound soundcore maestro cs4281 snd-cs46xx"

I'm not sure if all the sound modules in this list are necessary. I added <tt>snd-cs46xx</tt> to the list
because I knew it was the one I was using.

From the Mandrake Control Center, I configured one specific Thinkpad-specific option for the sound
driver. I entered the "Hardware" area and then selected the sound card and clicked "Configure Module".
One of the options is labeled simply "thinkpad". I set it to "1".

===Screen Locking after Suspend===

My screen always came back locked after I suspended, and I couldn't figure out how to turn that off
at first. That preference is also in {{path|/etc/sysconfig/suspend}} and is named LOCK_XFREE.

I set it to "no", but can still lock the screen if I want by using the Klaptop "Lock & Suspend..." option

==External Sources==

*[http://mr.uue.org/gnulinux/t20/ Michael Reinsch's notes about Mandriva on a Thinkpad T20]
*[http://pmag.chez.tiscali.fr/mdk80ontpt20.html How to Install a Mandrake 8.0 on a IBM Thinkpad T20]
*This guide is listed at the [http://tuxmobil.org/ibm.html TuxMobil Linux laptop and notebook installation survey (IBM/Lenovo)].

[[Category:Mandriva]] [[Category:T20]]

Installing Ubuntu on a ThinkPad T23

2007-11-23T19:26:56Z

MarkStosberg: /* Suspend / Resume */ note that suggested fix may cause another problem...

== Ubuntu 7.10 Gutsy Gibbon ==

Things generally work fine, with the following notes

=== Suspend / Resume ===

After upgrading from Feisty, "suspending" may have problems including a blank screen upon resume, or sound upon resume. Selecting a 2.6.20 kernel instead of the 2.6.22 kernel that comes with Gutsy seems to remedy both of these, but USB-after-suspend may quit working. You can select a different default kernel to boot by editing the /boot/grub/menu.lst file. (Alt-F2 gsudo get /boot/grub/menu.lst). You'll want to update the line that says "default" and change the default number to the correspond to the entry for the 2.6.20 kernel you want to use. Remember to start counting from zero!

After you made the change and saved the file. Run update-grub in a terminal. (Alt-F2 update-grub, with "run in terminal box" checked).

=== Dual Monitors ===

Gutsy Gibbon has a new "Screens and Graphics" preferences area. It shows a second monitor possibility. Trying a test does make both the LCD and external screen active as one big gray monitor...but only for the test. Choosing the option to accept the settings does not actually cause monitor-spanning to work, but monitor mirroring does.

=== CPU Frequency Scaling ===

CPU Frequency Scaling seems to be working automatically. To see your current speed level, activate the CPU Frequency Scaling Monitor Applet. Right click on the toolbar and select "add to panel". You can search for "Frequency" to find it.

== Ubuntu 7.04 Feisty Fawn ==

=== Power Management ===

The chips in T23s have the ability to run at speeds slower than their maximum, in order to save power. To see your current speed level, activate the CPU Frequency Scaling Monitor Applet. Right click on the toolbar and select "add to panel". You can search for "Frequency" to find it.

You can also enable this applet to allow you manually change the speed and scaling policy. To do that, run this in a terminal: "sudo dpkg-reconfigure gnome-applets".

These instructions are also available [http://www.ubuntugeek.com/howto-change-cpu-frequency-scaling-in-ubuntu.html illustrated with screenshots].

You may also need to add a couple of lines to "/etc/modules" to allow you to be able to change the processor speed and governor. The lines are:

acpi-cpufreq
cpufreq_ondemand

These will now be loaded on at boot time. To activate them immediately:

sudo modprobe acpi-cpufreq
sudo modprobe cpufreq_ondemand

Some technical details are explained on the [[SpeedStep]] page.

== External Resources ==

*[http://del.icio.us/tags/ubuntu+t23 Bookmarks tagged with Ubuntu and T23] on del.icio.us
*[http://ubuntuforums.org/tags/index.php/t23/ Forum posts tagged with T23] on ubuntuforums.org
[[Category:T23]]
[[Category:Ubuntu 7.04]]

Installing Ubuntu on a ThinkPad T23

2007-11-23T18:26:18Z

MarkStosberg: initial T23/Ubuntu notes

== Ubuntu 7.10 Gutsy Gibbon ==

Things generally work fine, with the following notes

=== Suspend / Resume ===

After upgrading from Feisty, "suspending" may have problems including a blank screen upon resume, or sound upon resume. Selecting a 2.6.20 kernel instead of the 2.6.22 kernel that comes with Gutsy seems to remedy both of these. This can be done by editing the /boot/grub/menu.lst file. (Alt-F2 gsudo get /boot/grub/menu.lst). You'll want to update the line that says "default" and change the default number to the correspond to the entry for the 2.6.20 kernel you want to use. Remember to start counting from zero!

After you made the change and saved the file. Run update-grub in a terminal. (Alt-F2 update-grub, with "run in terminal box" checked).

=== Dual Monitors ===

Gutsy Gibbon has a new "Screens and Graphics" preferences area. It shows a second monitor possibility. Trying a test does make both the LCD and external screen active as one big gray monitor...but only for the test. Choosing the option to accept the settings does not actually cause monitor-spanning to work, but monitor mirroring does.

=== CPU Frequency Scaling ===

CPU Frequency Scaling seems to be working automatically. To see your current speed level, activate the CPU Frequency Scaling Monitor Applet. Right click on the toolbar and select "add to panel". You can search for "Frequency" to find it.

== Ubuntu 7.04 Feisty Fawn ==

=== Power Management ===

The chips in T23s have the ability to run at speeds slower than their maximum, in order to save power. To see your current speed level, activate the CPU Frequency Scaling Monitor Applet. Right click on the toolbar and select "add to panel". You can search for "Frequency" to find it.

You can also enable this applet to allow you manually change the speed and scaling policy. To do that, run this in a terminal: "sudo dpkg-reconfigure gnome-applets".

These instructions are also available [http://www.ubuntugeek.com/howto-change-cpu-frequency-scaling-in-ubuntu.html illustrated with screenshots].

You may also need to add a couple of lines to "/etc/modules" to allow you to be able to change the processor speed and governor. The lines are:

acpi-cpufreq
cpufreq_ondemand

These will now be loaded on at boot time. To activate them immediately:

sudo modprobe acpi-cpufreq
sudo modprobe cpufreq_ondemand

Some technical details are explained on the [[SpeedStep]] page.

== External Resources ==

*[http://del.icio.us/tags/ubuntu+t23 Bookmarks tagged with Ubuntu and T23] on del.icio.us
*[http://ubuntuforums.org/tags/index.php/t23/ Forum posts tagged with T23] on ubuntuforums.org
[[Category:T23]]
[[Category:Ubuntu 7.04]]

Installing Ubuntu on a ThinkPad T23

2007-11-09T02:21:59Z

MarkStosberg: add version heading

== Ubuntu 7.04 Feisty Fawn ==

=== Power Management ===

The chips in T23s have the ability to run at speeds slower than their maximum, in order to save power. To see your current speed level, activate the CPU Frequency Scaling Monitor Applet. Right click on the toolbar and select "add to panel". You can search for "Frequency" to find it.

You can also enable this applet to allow you manually change the speed and scaling policy. To do that, run this in a terminal: "sudo dpkg-reconfigure gnome-applets".

These instructions are also available [http://www.ubuntugeek.com/howto-change-cpu-frequency-scaling-in-ubuntu.html illustrated with screenshots].

You may also need to add a couple of lines to "/etc/modules" to allow you to be able to change the processor speed and governor. The lines are:

acpi-cpufreq
cpufreq_ondemand

These will now be loaded on at boot time. To activate them immediately:

sudo modprobe acpi-cpufreq
sudo modprobe cpufreq_ondemand

Some technical details are explained on the [[SpeedStep]] page.

== External Resources ==

*[http://del.icio.us/tags/ubuntu+t23 Bookmarks tagged with Ubuntu and T23] on del.icio.us
*[http://ubuntuforums.org/tags/index.php/t23/ Forum posts tagged with T23] on ubuntuforums.org
[[Category:T23]]
[[Category:Ubuntu 7.04]]

Installing Ubuntu on a ThinkPad T23

2007-11-09T02:19:16Z

MarkStosberg: Installing Ubuntu 7.04 on a ThinkPad T23 moved to Installing Ubuntu on a ThinkPad T23 over redirect: Removing the version is consistent with other pages like "Installing Ubuntu on a ThinkPad T20" and will give the page a longer lifespan.

=== Power Management ===

The chips in T23s have the ability to run at speeds slower than their maximum, in order to save power. To see your current speed level, activate the CPU Frequency Scaling Monitor Applet. Right click on the toolbar and select "add to panel". You can search for "Frequency" to find it.

You can also enable this applet to allow you manually change the speed and scaling policy. To do that, run this in a terminal: "sudo dpkg-reconfigure gnome-applets".

These instructions are also available [http://www.ubuntugeek.com/howto-change-cpu-frequency-scaling-in-ubuntu.html illustrated with screenshots].

You may also need to add a couple of lines to "/etc/modules" to allow you to be able to change the processor speed and governor. The lines are:

acpi-cpufreq
cpufreq_ondemand

These will now be loaded on at boot time. To activate them immediately:

sudo modprobe acpi-cpufreq
sudo modprobe cpufreq_ondemand

Some technical details are explained on the [[SpeedStep]] page.

== External Resources ==

*[http://del.icio.us/tags/ubuntu+t23 Bookmarks tagged with Ubuntu and T23] on del.icio.us
*[http://ubuntuforums.org/tags/index.php/t23/ Forum posts tagged with T23] on ubuntuforums.org
[[Category:T23]]
[[Category:Ubuntu 7.04]]

Installing Ubuntu 7.04 on a ThinkPad T23

2007-11-09T02:19:16Z

#REDIRECT [[Installing Ubuntu on a ThinkPad T23]]

Installation instructions for the ThinkPad T23

2007-11-06T01:34:25Z

MarkStosberg: /* Distro specific Instructions */ And link to existing Ubuntu page

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

==General Notes==
*[[How to make ACPI work on a ThinkPad T23]]

==Distro specific Instructions==
* [[Installing Ubuntu 7.04 on a ThinkPad T23]]
*{{Install|LFS||T23}}

==External Sources==
* [http://home.comcast.net/~jyavner/T23/ Debian "Etch" on ThinkPad T23]
* [https://systemausfall.org/wikis/howto/Debian_on_IBM_T23 Debian "Sid" on ThinkPad T23] - especially covers DRI, standby, suspend2 and the internal modem
* [https://systemausfall.org/wikis/howto/Ubuntu_on_IBM_T23 Ubuntu "Edgy Eft" on Thinkpad T23]
* [http://www.dotimes.com/articles/t23-slackware-index.html Slackware on Thinkpad T23]

Installing Ubuntu on a ThinkPad T23

2007-08-28T03:14:05Z

MarkStosberg: /* Power Management */ add a missing step for CPU Frequency Scaling

Problems with ACPI suspend-to-ram

2007-08-22T11:54:36Z

MarkStosberg: /* Troubles on suspend */ add new posible suspend problem to the page. No answer yet.

The following glitches may or may not occur in relation to suspending to RAM:

==Troubles on suspend==
;Permissions:If your suspend is failing, and a {{cmdroot|tail /var/log/acpid}} shows "Permission denied" errors, be sure that your new ACPI event and action scripts have the appropriate permissions.

;Write error:If {{cmdroot|echo mem > /sys/power/state}} shows "write error: Operation not permitted", verify that CONFIG_HOTPLUG_CPU option is enabled in the kernel. [[Software_Suspend_2|Suspend2]] automatically selects this option.

;Broken sysfs interface:You may experience problems when using {{cmdroot|echo standby > /sys/power/state}} or {{cmdroot|echo mem > /sys/power/state}} (machine goes to sleep and wakes up immediately). This can be avoided by using {{cmdroot|echo -n 3 >/proc/acpi/sleep}} to get it to sleep. This can be also happen if hotplug daemon is still running.

;Hangs on "switching to UP code":You may be using a [[How to make use of Dynamic Frequency Scaling|frequency scaling governor]] such as "conservative" or "ondemand", which sometimes have problems with suspending. Switching to a governor such as "powersave" or "performance" before suspending may solve this problem.

;MySQL daemon running:If you're running MySQL, sleep may also not work, so stop MySQL first, then sleep. Remember to restart MySQL when you wakeup.

;LCD backlight remains on during sleep:When your system is equiped with a Radeon Mobility graphic controller your [[Problem with LCD backlight remaining on during ACPI sleep|LCD backlight may not turn off automatically]]. Use [[radeontool]] to switch off your backlight prior suspend in your sleep action script.

;High power drain during sleep:Also, you might want to take note of the [[Problem with high power drain in ACPI sleep]].

;Built-in MMC reader:If you have an MMC reader, and the computer hangs when attempting suspend then remove sdhci, mmc_block, and mmc_core modules before suspending.

;Could not power down device <NULL>: error -22:If you have the acpi_cpufreq kernel module loaded, this prevents suspension.

;Immediate Resume, but Suspend "moon" light continues to flash:???

==Troubles on resume==
;Blank display on resume:
:When resuming from a suspend-to-ram the display might remain black (on {{X60}}) or might only show the pre-suspend output (the system is still rebootable via {{key|ctrl}}{{key|alt}}{{key|del}}). See [[Problem with display remaining black after resume]] for solutions. See also '''System hang on resume''' on this page - which may be potentially mismatched with this one.

;No mouse cursor on resume:
:When resuming from a suspend-to-ram your X cursor might be invisible(on {{X40}}) when using {{path|/sys/power/state}} directly to suspend, they way to fix this is to rerun the post bios code after returning for suspending.
:{{cmdroot|FGCONSOLE<nowiki>=</nowiki>`fgconsole\`}}
:{{cmdroot|chvt 1 && echo -n mem >/sys/power/state}}
:{{cmdroot|vbetool post && chvt 7 && chvt $FGCONSOLE}}

;Garbage on text consoles on resume:When resuming from suspend-to-ram the text console displays may show garbage instead of actual text. The machine is otherwise still responsive and X displays fine. If all of this is true, then adding the kernel option {{bootparm|acpi_sleep|s3_bios,s3_mode}} in your menu.lst or lilo.conf may solve the problem.

;Broken hardware support after resume:
:*The '''serial port''' of the port replicator might not work after resume.
:*The '''parallel port''' might not work after resume. A possible fix is to unload and reload the parallel port drivers: {{cmdroot|rmmod lp parport_pc parport; modprobe lp}}.
:*Problems with the '''CD-RW/DVD drive''' after wake up from ram have been experienced.
:*There is a known Problem regarding '''battery info''' after suspend to RAM. A [http://www.ussg.iu.edu/hypermail/linux/kernel/0511.0/2429.html small patch] exists for kernels 2.6.14/2.6.15.
:*On {{X20}} and {{X21}} (and possibly other) models, the '''sleep LED''' is not reset properly on resume and will keep blinking. If you have the [[ibm-acpi]] kernel module loaded with the {{bootparm|ibm-acpi.experimental|1}} option, you can switch it off on resume by appending the following line to your suspend script: {{cmdroot|echo 7 off > /proc/acpi/ibm/led}}

;Crash on resume:
:*When using '''older ATI proprietary drivers''' a crash on resume can be solved by using [http://freshmeat.net/projects/vbetool/ vbetool]. See the example suspend script [[Problem with display remaining black after resume#Solution for ThinkPads with Intel I830 Chipset]]. This is no longer necessary with recent revisions of the ATI proprietary driver.
:*A crash could also be caused by having '''apic support''' enabled in the kernel config. Try disabling it (in the "Processor type and features" section).
:*On machines with Savage chipsets, the '''savagefb framebuffer driver''' might crash the machine on resume. Make sure it is disabled in your kernel config and use the standard vesafb driver instead.
:*SATA-based laptops utilize the '''libata layer for disk access''' which does not have fully-working power-management support before Linux kernel 2.6.16 (ata_piix) and 2.6.19 (ahci). Suspend to RAM crashes these machines on resume. See the [[Problems with SATA and Linux#Hang on resume from suspend to RAM|relevant section]] on the [[Problems with SATA and Linux]] page.
:*Using [[HDAPS]] as a module causes a crash on resume with the Linux kernel 2.6.19 (possibly even earlier versions). This was observed on a {{X41}}. Try unloading the module before suspending.
:*Gnome-power-manager might be using the wrong backend. If you are able to suspend from the commandline with a certain method, make sure the others are not available so that g-p-m doesn't choose the wrong one. For example, if you suspend with {{cmdroot|echo mem > /sys/power/state}}, make sure '''uswsusp''' and '''hibernate''' are uninstalled.

;System hang on resume:
:When system resumes it hangs right after restarting tasks. Strange thing is, that you may be even able to restart your ThinkPad using {{key|ctrl}}{{key|alt}}{{key|del}}, but if you try to blindly exec a command, it will not work, (eg. touch FILE) so it's not only the problem of videocard. This may be fixed by passing {{bootparm|ec_intr|0}} on kernel cmdline. Affected models: {{T20,T21}} (at least [[2648-46U]] (T20),[[2647-8AG]] (T21)).
:'''Note:''' ''this is resolved in kernel 2.6.20, there is no need to pass the {{bootparm|ec_intr|0}} bootparam anymore (moreover, you are discouraged to use it) See [http://bugzilla.kernel.org/show_bug.cgi?id=6749 revelant kernel bug report]''

;Shutdown on resume:
:If your system immediately begins to shut down right after resume, make sure you don't have acpid running with the power button tied to shutdown. The system is simply sensing the power button event and shutting down. This issue has been reported as a bug against the kernel ACPI subsystem, refer to [http://bugzilla.kernel.org/show_bug.cgi?id=6612 kernel.org bugzilla bug #6612].

;Immediate suspend on resume:
:When running GNOME, sometimes gnome-power-manager will put the system back into suspend immediately after resuming. This is caused by a known bug in HAL that causes some ACPI events to be reported incorrectly after a suspend-to-ram. A simple workaround can be found [http://live.gnome.org/GnomePowerManager/Faq?action=recall&rev=28#head-b8b1280115b0a51c2cc27b13a57121130ebf36cb here].
:Note that suspend being triggered by unrelated ACPI events such as disconnecting the AC adapter may also be fixed by the above method.

;Power Off when suspended laptop is docked
:When T60p is suspended, docking laptop into Advanced Dock immediately turns off laptop and crescent moon sleep indicator LED. Pressing power button initiates cold boot. Also reported by multiple people on thinkpads.com.

;SectorIdNotFound disk errors when laptop is resumed
:The errors look like this:
Oct 14 17:35:02 cacharro kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Oct 14 17:35:02 cacharro kernel: hda: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=115896900, sector=115896900
Oct 14 17:35:02 cacharro kernel: ide: failed opcode was: unknown

:This happens when you have [[Hidden Protected Area]] (HPA) enabled on the hard drive. There is a [http://bugzilla.kernel.org/show_bug.cgi?id=6840 kernel bug report with an unfinished patch] to fix this. This is not fixed as of kernel 2.16.18.

How to make ACPI work on a ThinkPad T23

2007-08-22T02:54:43Z

MarkStosberg: /* Basic installation */ this kernel is not the default in many cases now.

This page deals with installing and running {{Gentoo}} Linux (2005.1) on a ThinkPad {{T23}}, Model 2647-4MG.

==Basic installation==
The Linux kernel (2.6.12-r6) boots OK, and recognises all the devices (modem not tested).

==ACPI==
Getting software suspend working requires some tweaking.

First of all, [[BIOS Upgrade|update to the latest BIOS and Embedded Controller Program]].

{{cmdroot|dmesg}} will probably tell you that ACPI isn't enabled in the BIOS, because the T23 BIOS has no mention of ACPI. Just add {{bootparm|lapic|}} to the kernel
arguments in {{path|/etc/lilo.conf}} or {{path|/boot/grub/menu.lst}}.

After that, you will probably get a lot of ACPI error messages, generally of the form <tt>AE_NOT_EXIST</tt>. Those can be fixed by recompiling your DSTD. To do just that, get the Intel iasl compiler source from [http://developer.intel.com/technology/iapc/acpi/downloads.htm their site] and compile it. It should build without troubles. De- and re-compile the DSDT. If it gives errors or remarks, try fixing them as best as you can or download final dsdt.dsl from [http://acpi.sourceforge.net/dsdt/view.php?id=758]. Then load the new DSDT on boot with the kernel's "Custom DSDT" option.

Now {{cmdroot|dmesg}} should show that the ACPI had found the ECDT and enabled the interpreter and you should find a full set of ACPI entries under {{path|/proc}}.

Done that, verify that the [[ibm-acpi]] driver is enabled by issuing {{cmdroot|ls /proc/acpi/ibm/*}}. If you see files in this directory, everything is alright. If the directory couldn't be found, you will have to enable [[ibm-acpi]] in your kernel config (as builtin or module) and recompile your kernel.

The next step is [[How to configure acpid|configuring acpid]], which handles the ACPI buttons through scripts in {{path|/etc/acpi}}.

To try if suspend to ram workd, press {{key|Fn}}{{key|F4}} or issue a {{cmdroot|echo -n mem >/sys/power/state}}.

===Resume problem===
If your system doesn't resume from sleep after that, use the power button to switch it off and restart. To solve the issue, try disabling S3 framebuffer support in your kernel config and recompile your kernel. Should that not be enough, try unloading suspicious drivers such as USB in your suspend script and reloading them on resume.

If all that doesn't help, build a monolithic kernel having everything you need builtin and only minimal options enabled. If it works with that kernel, start reenabling other options step by step.

===Button events===
By default, ACPI seems to handle three button events only - the Power button, the Suspend key ({{key|Fn}}{{key|F4}}) and the lid event. {{key|Fn}}{{key|F3}} (Screen blank) will need [[How to make ACPI work#Screen blanking (Standby)|extra configuration]], as well as {{key|Fn}}{{key|F12}} (Suspend to disk) (look [[How to make ACPI work#Suspend to disk (Hibernate)|here]]). {{key|Fn}}{{key|F7}}, (Switch to
video) at least blanks the LCD.

{{key|Fn}}{{key|Home}} (LED brighter), {{key|Fn}}{{key|End}} (LED dimmer), {{key|Fn}}{{key|PgUp}}
(Screen light) will work without any further effords, since they are not handled by the ACPI subsystem.

When the machine is running, the lid switch blanks the screen when
pressed and restores on release, but if the machine is suspended
pressing the switch does nothing and releasing it brings the machine out
of suspend mode.

Commands echoed to eg: {{path|/proc/acpi/ibm/light}} can be mixed with the appropriate keypresses (here,
{{key|Fn}}{{key|PgUp}}) without problems.

===Frequency Scaling===
The CPU (Pentium III-M) has power management and
throttling; use the '''acpi-cpufreq''' module instead of the '''speedstep-ich''' module to change speed automatically. The CPU has
only two speeds, and with the '''cpufreq_ondemand''' & '''cpufreq_conservative''' modules, dynamic scaling will be achieved. Alternatively, with the '''speedstep-ich''' module, you can use a shell script to flip between the performance and powersave kernel governors; everything needed can be found in the {{path|/sys/devices/system/cpu/cpu0/cpufreq}} directory.

===UltraBay LED stays lit===
The Bay LED wrongly stays lit even when in suspend to ram mode, but the most recent (1.1) [[ibm-acpi]] module provides an ACPI LED device which controls most of the LEDs (the Bay LED
is 4), so you can switch it off in your suspend script.
{{WARN|The UltraBay LED should stay lit when suspended to RAM. Any ThinkPads newer than the 600X have hot-swappable UltraBays, not warm-swappable ones. Attempting to remove or insert an UltraBay device when suspended will cause it to wake up and try to handle the request, but with Linux this usually causes lockups.}}

===Resume===
With the CPU on low speed (if it matters) and the LED off the power consumption in Suspend mode is around 580mW.

It looks as if the software to control full ACPI functionality has
only stabilised within the middle of 2005, so if you
have problems, try upgrading to IBM's latest BIOS and EBIOS, and a
kernel >=2.12. With luck, the next version or so of the S3 driver will
be free of its hang problem.

=External Sources=
*This guide is listed at the [http://tuxmobil.org/ibm.html TuxMobil Linux laptop and notebook installation survey (IBM/Lenovo)].

Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60

2007-08-20T02:56:14Z

MarkStosberg: clean up: move "Thanks" to the bottom of the page, remove personal Suse vs. Ubuntu opinion

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

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

=== Machine Specs Tested with ===

The following machine was used for testing

: Figure 1. ThinkPad T60 2007
: [[Image:thinkpad.jpg]]

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

===What Works?===

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

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

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

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

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

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

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

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

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

===Getting Ubuntu installed===

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

{{NOTE|If your Windows system is '''Vista''', you must '''not''' use the Ubuntu tool to resize your Windows partition. Instead, resize the partition now from Vista: type Win+R, and run "diskmgmt.msc". The right click on the Vista partition (the second one, probably named "SW_Preload"), and select "Reduce volume".}}

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

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

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

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

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

{{NOTE|5 GB is too much for /boot. 100MB is enough (and you will never be out of space).}}

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

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

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

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

===Wireless LAN===

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

The first thing we should do is to get wireless networking working. Luckily, getting the Centrino wireless LAN chip working in Ubuntu is quite easy, if you use the gnome-network-manager applet.

{{NOTE|On Ubuntu 7.04 the Network Manager applet is already installed. You can skip this section.}}

Just go to System - Administration - Synaptic Package Manager. Then click 'Search' and set the 'look-in' field to 'name'. In the 'Search' text box type:

<pre>network-manager</pre>

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

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

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

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

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

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

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

===Non-Intel Network Cards===

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

: {{cmduser| lspci}}

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

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

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

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

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

running:

: {{cmdroot| dmesg | grep hal}}

may yield output like this:

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

Which suggests the hardware abstraction layer is in place.

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

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

: {{cmdroot| iwpriv ath0 mode 2}}

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

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

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

Then paste the following in the file:

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

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

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

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

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

===Installing the ATI display drivers===

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

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

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

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

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

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

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

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

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

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

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

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

: {{cmduser|fglrxinfo}}

This should display:

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

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

===The Fingerprint Reader===

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

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

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

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

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

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

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

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

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

and type the following:

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

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

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

and find the line:

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

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

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

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

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

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

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

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

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

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

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

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

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

Now, you can compile and install the plugin

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

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

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

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

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

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

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

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

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

Delete everything in the file, and paste this instead:

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

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

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

Delete everything in the file, and instead paste:

<pre>
#%PAM-1.0

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

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

<pre>
#%PAM-1.0

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

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

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

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

If you use SSH to log remotely into your laptop, you need to disable common-auth procedures for ssh. Not doing so requires to physically swipe your finger when logging remotely - nonsense. For that, edit /etc/pam.d/ssh, comment out @include common-auth and add the old procedure instead:

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

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

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

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

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

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

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

Save and close the file, then type:

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

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

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

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

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

: {{cmduser|hcitool scan}}

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

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

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

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

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

===TrackPoint Scrolling===

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

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

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

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

Now, add the follwing two options in that InputDevice section:

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

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

===Enable/Disable Touchpad===

If the touchpad annoys you (as it does me), you'll want a quick way to disable and enable my synaptics touchpad at will.

Make sure that in your /etc/X11/xorg.conf file, you have:
<pre>
Section "InputDevice"
Identifier "Synaptics Touchpad"
Driver "synaptics"
Option "SendCoreEvents" "true"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
Option "HorizScrollDelta" "0"
Option "SHMConfig" "on"
EndSection
</pre>

Notice the Option “SHMConfig” “on” line — that is the one that you really need to have in there. This allows you to change some configuration parameters for the synaptics touchpad without restarting Xorg (Xserver).

Now that is taken care of.

All you have to do to disable your synaptics touchpad is to execute the command:
<pre>$synclient TouchpadOff=1</pre>

and to turn it back on, you can execute the command
<pre>$synclient TouchpadOff=0</pre>

Once that is in there on a T60, you can use FN+F8 to enable/disable the touchpad. Cool eh?

===Getting Multimedia to Work===

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

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

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

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

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

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

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

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

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

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

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

Now, open a terminal and type the following:

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

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

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

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

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

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

At the end of the file, append the following:

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

Save and close the file. Now type:

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

ATI Users Only: type

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

Now, to install beryl:

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

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

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

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

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

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

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

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

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

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

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

Now, in this file paste:

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

Save and close the file. Now type:

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

In this file, paste:

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

Now make the file executable:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Find the line which says

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

and replace it with

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

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

<pre>vga=791</pre>

Before:

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

After:

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

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

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

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

: {{cmduser| alsamixer}}

The alsamixer GUI will be displayed:

[[Image:alsamixer.jpg]]

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

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

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

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

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

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

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

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

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

As a last resort, you may have to install the latest version of ALSA. Try: http://www.alsa-project.org/alsa-doc/doc-php/template.php?module=hda-intel

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

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

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

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

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

Save and close the file, and make it executable:

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

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

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

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

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

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

To install the script type

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

To go to hibernate type

: {{cmduser|sudo hibernate}}

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

The sleep, though, works really well -reliable- when neither using gdm nor gnome at all. For example, using any lightweight window manager such as dwm from http://www.suckless.org .
In order to put the computer to sleep issue the following command:

: {{cmduser|sudo pmi action sleep}}

From within a standard ubuntu-desktop running gnome, the above works most of the time but not always. When it doesn't work, only a hard reboot will stop the moon from blinking and restore the system to a usable state.

Independently of all the above, there is one way to ensure your Thinkpad T60 core2 duo will sleep and resume flawlessly when using the standard gnome desktop. Create the following two scripts, under the respective folders as indicated in the comment in each:

First file:
<pre>
#!/bin/sh
# /etc/acpi/suspend.d/01-cpu-governor.sh
echo "performance" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo "performance" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
</pre>

Second file:
<pre>
#!/bin/sh
# /etc/acpi/resume.d/01-cpu-governor.sh
echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo "ondemand" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
</pre>

Note: I did this (on Feisty) and gnome-panel reported that one CPU is stuck in 'performance'. However, this seems to be spurious: see https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/80212

===Desktop envy===

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

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

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

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

===Conclusion===

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

* Beagle
* Tomboy
* Deskbar

===References===

* ATI on Ubuntu - https://help.ubuntu.com/community/BinaryDriverHowto/ATI
* Garbled Virtual Terminal Bug - https://launchpad.net/distros/ubuntu/+source/usplash/+bug/63558
* Beryl logout Bug - http://forum.beryl-project.org/viewtopic.php?p=1295&sid=6feedd09a7f01bca68feb05a5f2f033c
* Beryl Netbeans Bug - http://ubuntuforums.org/showthread.php?t=252594
* Beryl on Ubuntu - http://wiki.beryl-project.org/index.php/Install/Ubuntu/Edgy/XGL
* Home directory permissions bug - http://www.ubuntuforums.org/showthread.php?p=1789997
* gnome-bluetooth bug - https://launchpad.net/distros/ubuntu/+source/gnome-bluetooth/+bug/70718
* Atheros network cards on Ubuntu - http://ubuntuforums.org/showthread.php?t=38972
* Enabling the microphone - http://ubuntu.wordpress.com/2005/12/05/fixing-the-errant-microphone/
* Enabling the microphone (2) - http://ubuntuforums.org/showthread.php?t=272166
* This guide is listed at the [http://tuxmobil.org/ibm.html TuxMobil Linux laptop and notebook installation guides survey (IBM/Lenovo)].

=== Thanks ===

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

Thanks for valuable contributions by:

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

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

: dave abrahams
: Limo Driver

Other Thanks:

: Alex Penn, University of Berkeley
: Thomas Repantis, University of California

[[Category:Ubuntu]] [[Category:T60]]

Intel Mobile Pentium III-M

2007-08-19T17:38:53Z

MarkStosberg: /* Speedstepping */ replace todo with helpful reference.

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
===Intel Mobile Pentium III-M===
Featuring the Tualatin core the Mobile Pentium III-M is a lot more powerful than the [[Intel Mobile Pentium III|Mobile Pentium III]]. This is proven in it's rebirth as [[Intel Pentium M (Banias)|Pentium M]].

===Features===
*700-1200 MHz tact
*133 MHz FSB (100 on some of the lv and ulv models)
*44 Million Transistors
*0.13µm fabrication process
*0.07µm gates
*1.40/1.15 VCore
*2x 16 KB L1-Cache
*512 KB L2-Cache
*[[SpeedStep|Enhanced SpeedStep]], [[QuickStart and Deeper Sleep|QuickStart]], [[QuickStart and Deeper Sleep|Deeper Sleep]]
*[[SIMD|MMX]], [[SIMD|SSE]] instruction sets
</div>
|}

==Available Types and ThinkPads featuring them==
{| border=1 cellspacing=0 cellpadding=2
|- style="background:#ffdead;"
! colspan=2 | Frequency (MHz) || Bus Speed (MHz)|| colspan=2 | core Voltage (V) || colspan=2 | TDP (W) || ThinkPad Models
|- style="background:#ffdead;"
!max. !! min. !! !! high !! low !! high !! low !!
|- style="background:#efefef;"
! colspan=8 | Mobile Pentium III-M
|-
| 1333 || 800 || 133 || 1.40 || 1.15 || 22.0 || 9.8 ||
|-
| 1266 || 800 || 133 || 1.40 || 1.15 || 22.0 || 9.8 ||
|-
| 1200 || 800 || 133 || 1.40 || 1.15 || 22.0 || 9.8 || {{A30p}}, {{T23}}, {{X30}}
|-
| 1133 || 733 || 133 || 1.40 || 1.15 || 21.8 || 9.3 || {{A30}}, {{R31}}, {{T23}}, {{X24}}
|-
| 1066 || 733 || 133 || 1.40 || 1.15 || 21.0 || 9.3 || {{X30}}
|-
| 1000 || 733 || 133 || 1.40 || 1.15 || 20.5 || 9.3 || {{A30}}, {{R31}}, {{T23}}
|-
| 933 || 733 || 133 || 1.40 || 1.15 || 20.1 || 9.3 || {{A30}}
|-
| 866 || 667 || 133 || 1.40 || 1.15 || 19.5 || 8.9 || {{T23}}
|- style="background:#efefef;"
! colspan=8 | Mobile Pentium III-M (Low Voltage)
|-
| 1000 || 533 || 133 || 1.15 || 1.05 || 10.9 || 6.1 ||
|-
| 933 || 533 || 133 || 1.15 || 1.05 || 10.5 || 6.1 ||
|-
| 866 || 533 || 133 || 1.15 || 1.05 || 10.1 || 6.1 || {{X23}}?
|-
| 850 || 500 || 100 || 1.15 || 1.05 || 10.0 || 5.9 ||
|-
| 800 || 533 || 133 || 1.15 || 1.05 || 9.8 || 5.9 || {{X22}}?, {{X23}}?
|-
| 750 || 450 || 100 || 1.15 || 1.05 || 9.4 || 5.7 ||
|-
| 733 || 466 || 133 || 1.15 || 1.05 || 9.3 || 5.8 || {{X22}}?
|- style="background:#efefef;"
! colspan=8 | Mobile Pentium III-M (Ultra Low Voltage)
|-
| 866 || 400 || 133 || 1.10 || 0.95 || 7 || 3.4 ||
|-
| 850 || 400 || 100 || 1.10 || 0.95 || 7 || 3.4 ||
|-
| 800 || 400 || 100 || 1.10 || 0.95 || 7 || 3.4 ||
|-
| 750 || 350 || 100 || 1.10 || 0.95 || 7 || 3.1 ||
|-
| 733 || 400 || 133 || 1.10 || 0.95 || 7 || 3.4 ||
|-
| 700 || 300 || 100 || 1.10 || 0.95 || 7 || 3.0 ||
|}

==Thermal Specifications==

==Speedstepping==

[http://www.thinkwiki.org/wiki/Installing_Ubuntu_on_a_ThinkPad_T23#Power_Management The page on installing Ubuntu on a T23] includes tips for monitoring and managing the processor speed settings.

==GCC Optimization Flags==
You should use the following if you have a Mobile Pentium III-M:
-Os -march=pentium3m -fomit-frame-pointer -pipe

"-Os" means optimise for size. "-O2" is usually the default and is probably more prefferable. If you're feeling brave you could try using "-O3", but many programs fail to compile with this (attempting to compile binutils, gcc or any other core tools with "-O3" is not recommended)

[[Category:Components]]

Intel Mobile Pentium II

2007-08-19T13:17:37Z

MarkStosberg: /* Features */ link to QuickStart page

Intel Pentium 4

2007-08-19T13:16:20Z