ThinkWiki - User contributions [en]

User:Low

2009-04-09T05:34:45Z

Low: /* about the System */

== about Low ==
I'm a linux noob, really. Though I spent 5 years maintaining a huge website, I had little exposure to the system itself. At work I'm 50% on HP-UX, also as a user. I learn as I progress.
== about the System ==
'''[[:Category:R60|R60]]''' [[9461-DXG]]

[[Intel Core 2 Duo (Merom)|Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz]]

15" 1400x1050px w/[[ATI Mobility Radeon X1400|ATI X1400]]

'''[[:Category:Slackware|Slackware]] 12.2''' (pretty much 'vanilla' - only added the [[fglrx]] package for the ATI and [[TuxOnIce]] - and as you might have guessed: after reinstalling and recompiling the kernel about 20 times till I found out that for SATA you need some SCSI modules...)

'''fvwm''' 2.5.26

= Low's Sandbox =

User:Low

2009-04-09T05:34:15Z

Low: /* about the System */

== about Low ==
I'm a linux noob, really. Though I spent 5 years maintaining a huge website, I had little exposure to the system itself. At work I'm 50% on HP-UX, also as a user. I learn as I progress.
== about the System ==
'''[[:Category:R60|R60]]''' [[9461-DXG]]

[[Intel Core 2 Duo (Merom)|Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz]]

15" 1400x1050px w/[[ATI Mobility Radeon X1400|ATI X1400]]

'''[[:Category:Slackware|Slackware]] 12.2''' (pretty much 'vanilla' - only added the [[fglrx]] package for the ATI and [[TuxonIce]] - and as you might have guessed: after reinstalling and recompiling the kernel about 20 times till I found out that for SATA you need some SCSI modules...)

'''fvwm''' 2.5.26

= Low's Sandbox =

Talk:Batteries

2009-01-19T19:42:50Z

Low: request for clarification

what means "stupid" and "intelligent" for batteries? please clarify this - as i dont think they pass a touring test altogether. --[[User:Low|Low]] 19:42, 19 January 2009 (UTC)

User:Low

2009-01-16T17:30:06Z

Low: /* Low's Sandbox */

== about Low ==
I'm a linux noob, really. Though I spent 5 years maintaining a huge website, I had little exposure to the system itself. At work I'm 50% on HP-UX, also as a user. I learn as I progress.
== about the System ==
'''[[:Category:R60|R60]]''' [[9461-DXG]]

[[Intel Core 2 Duo (Merom)|Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz]]

15" 1400x1050px w/[[ATI Mobility Radeon X1400|ATI X1400]]

'''[[:Category:Slackware|Slackware]] 12.1''' (pretty much 'vanilla' - only added the [[fglrx]] package for the ATI - and as you might have guessed: after reinstalling and recompiling the kernel about 20 times till I found out that for SATA you need some SCSI modules...)

'''fvwm''' 2.5.26

= Low's Sandbox =

User:Low

2009-01-16T17:29:40Z

Low:

== about Low ==
I'm a linux noob, really. Though I spent 5 years maintaining a huge website, I had little exposure to the system itself. At work I'm 50% on HP-UX, also as a user. I learn as I progress.
== about the System ==
'''[[:Category:R60|R60]]''' [[9461-DXG]]

[[Intel Core 2 Duo (Merom)|Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz]]

15" 1400x1050px w/[[ATI Mobility Radeon X1400|ATI X1400]]

'''[[:Category:Slackware|Slackware]] 12.1''' (pretty much 'vanilla' - only added the [[fglrx]] package for the ATI - and as you might have guessed: after reinstalling and recompiling the kernel about 20 times till I found out that for SATA you need some SCSI modules...)

'''fvwm''' 2.5.26

= Low's Sandbox =
{{R60}}

User:Low

2009-01-16T17:28:59Z

Low:

== about Low ==
I'm a linux noob, really. Though I spent 5 years maintaining a huge website, I had little exposure to the system itself. At work I'm 50% on HP-UX, also as a user. I learn as I progress.
== about the System ==
'''[[:Category:R60|R60]]''' [[9461-DXG]]

[[Intel Core 2 Duo (Merom)|Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz]]

15" 1400x1050px w/[[ATI Mobility Radeon X1400|ATI X1400]]

'''[[:Category:Slackware|Slackware]] 12.1''' (pretty much 'vanilla' - only added the [[fglrx]] package for the ATI - and as you might have guessed: after reinstalling and recompiling the kernel about 20 times till I found out that for SATA you need some SCSI modules...)

'''fvwm''' 2.5.26

= Low's Sandbox =

Talk:Install Ubuntu 8.10 (Intrepid Ibex) on a ThinkPad T400

2009-01-13T16:08:13Z

Low: /* Suspend/resume workaround */ what about unloading h

Added instructions for adding installing ath5k drivers, added a section about screen resolution issues, and fixed minor errors.

-[[kassanova708]]

== Suspend/resume workaround ==

I managed to get suspend/resume working by disabling Bluetooth.

===== which way? =====
How did you disable bluetooth?
Did you try unloading the bluetooth kernel module in the sleep script and loading it again on resume? Or did you use a hardware switch or maybe soft disabling the device in /sys/ /proc/ or something?
--[[User:Low|Low]] 17:08, 13 January 2009 (CET)

Talk:ThinkPad Dock II

2009-01-13T07:20:36Z

Low: /* Low Profile PCI? IBM says Half size. */ low profile may fit with mounting brackets

Got it! Actually able to run six monitors without any conflicts. Life is good.

Hope I doing this right. Look up the definition of novice in the dictionary and you will find my picture. That said, I have an R52 ThinkPad, a ThinkPad Dock II with an ATI FireMV 2400 PCI 128M video card in the dock PCI slot. Card supports 4 monitors. Was told by a guy at work just plug it all in, install the card drivers, set up the configuration of the monitors in display properties and your good to go. Not so. Display properties only shows 2 monitors. None of the four outputs of the card have a signal. I want to ultimately be able to use 5 monitors, the four supported by the the ATI card and the display on the R-52. Got any ideas where I can get help with this? Thanks for any help anyone can give me.
Eddie
----

I just installed a Nvidia Quadro NVS 50 PCI card in an attempt to add an additional monitor to my laptop (T41), and get 1920 x 1200 digital on my 24" widescreen. The Nvidia is not a dual monitor card, but I thought I would be able to use it as well as the laptop's existing card (ATI Mobility Radeon 7500). However the ATI card shows up in the hardware manager with the message "This device cannot start. (Code 10)". I then tried to enable the AGP as the primary video device in the BIOS (PCI was enabled). The on-board adapter came up, and the device manager listed no conflict, but the Nvidia would not come up as I tried to extend my desktop in display props. I got the message that I did not have admin rights to select the Nvidia, followed by messages that my drivers were not compatible with the newer version of Windows. I have never tried to use two monitors before, so I am not sure if it is feasible to have two video cards running at the same time. If this is possible, please let me know what I need to do, if it is not possible then I need to return the card and get one of your recommended ones.

TIA!
Tony
----
Hi Tony, can't help you much, i'm afraid. I have had a Radeon 9200 PCI card in the dock for a while, using it under Win. I think setting the AGP bus as the primary one in the BIOS is the way you should go. I had troubles with my Windows not booting up at all anymore when i changed it to PCI and was sure that it was the ATI driver having problems.

I would try to get the most recent drivers from the NVidia homepage. Best try uninstalling your drivers and reinstalling them. You might also check if your card is supported by the OMEGA drivers (http://www.omegadrivers.net).

Good luck, Wyrfel.

== Modify for compatibility? ==

I have an X41 Tablet on the way and am very disappointed that the only "Dock" available is more like a glorified port replicator. While I'm sure the X41 Tablet wouldn't ''fit'' on the Dock II, do you think it would be possible to remove the docking port from the plastic and connect it to the X41, or is it a different style connector? I would really appreciate audio jacks and a PCI slot.
^

== Who wrote this about the 1920 x 1200 on the dock II? ==

This is a very important subject to me since we used to buy a lot of T series Thinkpads but dont any longer because of the lack of support for the widescreen external DVI flat panels.

Who wrote this about the new driver from 8-11-05 - I have contacted IBM tech support (not Lenovo) and they have not heard such a thing and it is not listed - they have looked at the last video driver update to the T42p or T43p (I am looking for the 14" SXGA+ T42p model) with a dock II being able to drive externally 1920 x 1200 (UXGA+) WITHOUT an added PCI card. This would be NIRVANA for me.

Do you have anymore information about this driver and have you SEEN it work at all?

Thanks
Dean

dean@sigma-usa.com
----
Hei Dean,

i do not have a 1920x1200 display, but i have a 1600x1200 one which was unsupported before as well. The newest driver (upgraded via IBM Software Installer) indeed doesn't have the problem anymore which it had before with that resolution (1280x1024 was supported max). The newest Presentation Director supports the higher resolution as well.

I actually switched back from OMEGA drivers to the newest IBM release and experienced some strange behaviour which was gone after a few reboots). I guess some parts of OMEGA were not properly uninstalled in one go.

IBM might not know about this if they just upgraded the underlying Catalyst drivers.

However, you might wanna get a confirmation from someone using 1920x1200 before you celebrate. ;-)

[[User:Wyrfel|Wyrfel]] 01:16, 4 Oct 2005 (CEST)
----

BTW: I merged the information that was provided here on this issue into the [[Problem with DVI throughput]] page, since it was doubled in several places and belongs there. [[User:Wyrfel|Wyrfel]] 01:48, 4 Oct 2005 (CEST)
----
====newest drivers work with high resolution via DVI====
The above is a true statement. I have in Nov 2005 installed 3 Thinkpad T's (T42p and T43p) with 128 megs of ATI video RAM (Fire 3200) and with the Think Dock II using the pass through DVI port, i am driving Dell 20" WSXGA+ (1600 x 1050 widescreen) and Sony WUXGA (1900 x 1200) 23" widescreen flat panels. They work OUT OF THE BOX without having to install special drivers. This is a new feature of the Thinkpad line (at least for the T series).
----

== Low Profile PCI? IBM says Half size. ==

I don't think that LowProfile PCI-Cards will fit in the Dock II cause of the shorter mounting bracket.
I just successfully plugged a standard PCI card with the dimension
17.5 cm (without brackets and vga connector) x 9,9 cm (without pci connector, 10,7 cm with pci connector)
This seems to be the maximum dimensions possible...think the 'half size' written by ibm means the length of the card, not the width, as there are full size pci cards e.g. for video editing that reach all the way to the front through a standard tower case.

Afaik 'half size' means the length of the card. For low profile there should be mounting brackets available making them fit - however as always: check before you invest money.
--[[User:Low|Low]] 08:20, 13 January 2009 (CET)

== Z60 and T60 ==

These machines are not supported by the ''legacy'' docks, you need to use the new Z60 range of port replicators and docking stations.

--[[User:Tonko|Tonko]] 20:22, 11 Jan 2006 (CET)

== T60 And Dual Monitors ==

Yes, you can drive dual monitors with the ThinkPad Advanced Mini-Dock. I am running it under Windows Vista and it is great! The thing you need to do is download the ATI drivers from Lenovo and use the Catalyst Control center to disable your laptop LCD and then enable your analog monitor. By default, the DVI is enabled if both monitors are plugged in.

--[[User:Paul317|Paul317]] 22:30, 19 July 2007 (UTC)

----

So I can drive dual monitors with a T60 and an "THINKPAD ADVANCED MINI-DOCK"?

-- [[ryan.mchale@gmail.com | ryan]] 18:30, 18 April 2006 (CMT)
----
The docking solutions are listed [[Docking Solutions|here]], and indeed that includes the [[ThinkPad Advanced Mini Dock]] which supports the T60.

I do not personally have this hardware, but you should be able to do any of the following:

* ThinkPad LCD + Analog external monitor (VGA)
* ThinkPad LCD + External TV (Svideo)
* ThinkPad LCD + Digital external monitor (DVI)
* Analog external monitor (VGA) + Digital external monitor (DVI)
* Analog external monitor (VGA) + External TV (Svideo)

DVI requires that you have a Dock or Port-Replicator for your ThinkPad with a DVI passthrough port on it. Also you cannot have both DVI and Svideo, since (at least historically, not sure with the new ThinkPads), the Svideo port on the ThinkPad has been blocked by the dock or port replicator and no passthrough function is provided.

Also, I am not sure DVI is supported on the entry T60 model with GMA950 graphics.

--[[User:Tonko|Tonko]] 22:59, 19 April 2006 (CEST)

== Eject mechanism on Dock II ==

I've just acquired a used Dock II, and the eject mechanism seems to be a bit different from other Thinkpad docks and port replicators I'm familiar with. In particular, my question concerns the the square plugs on the dock base that help eject the laptop when the eject button is pressed. On the original dock for the A and T series, the original Port Replicator, and the newer Mini-Dock, the plugs are normally flush with the base, and are pushed up when the user presses the eject button. On the Docking Station II that I have, the plugs are spring loaded, are extruded from the base when no laptop is present, and are not affected by pressing the the eject button. That is, on the Docking Station II, the plugs are always applying pressure pushing the laptop up, and the laptop is held in place by the locking mechanism that is released when the eject button is pressed. Is this normal for the Docking Station II, or is there some linkage in my unit that's broken?

TIA,
Sanford

----

This is perfectly normal and maybe was an attempt from IBM to reduce the complex mechanics of the eject mechanism of the older docks.

--[[User:BDKMPSS|BDKMPSS]] 15:31, 11 July 2008 (CEST)

== R30, R31, and R32 are not supported ==

According to [http://www-307.ibm.com/pc/support/site.wss/MIGR-4NXNTP.html Docking station, port replicator, and expansion - ThinkPad General] R30, R31, and R32 are not supported by ThinkPad Dock II.

== Replace/unplug the noisy fan of Dock II ==

In the information page, it is said some user might replace or unplug the noisy fan, I attempt to open the Dock II so that I could reach the fan and do something about it, does some one here knows the steps to disassemble it? The noise of the fan is really LOUD!

Thanks ahead.

== Help pleas ==

These have been moved from the main page...

''Dock II Linux users: can anybody recommend kernel modules and parameters for using PCI video cards with the dock's PCI slot? I had it working once with the dock, pci_slot, pci_hotplug and acpiphp modules and the pci=assign-busses parameter but since an unknown change to my system occurred, combinations of the above are no longer sufficient.''

''Dock II owners: anybody tried to shoehorn a larger card in? ''

Sorry for cluttering up the article (with the upper question). I've asked on the forums and mailing list. So far the LKML has given me the most help but the patch they recommended didn't solve the problem when I recompiled the kernel. However I thought the article should have some mention of this problem as it is likely to be the first stop for people who wonder whether or not they can use the PCI slot for a video card in Linux. Every single time I have seen a video card stated to be compatible with this dock, the person saying this was either a Windows user or didn't specify which OS he or she used. So unless someone DOES have this working (I had it working for a few days before it broke) we should probably say that the exact steps for getting docked PCI video cards to work in Linux are unknown.
[[User:Connor Behan|Connor Behan]] 06:10, 13 January 2009 (CET)

Category talk:W500

2009-01-11T21:09:16Z

Low: â†Created page with '==distro pages== what do you think about splitting this document and putting the installation instructions into their own pages? ~~~~'

==distro pages==
what do you think about splitting this document and putting the installation instructions into their own pages? [[User:Low|Low]] 22:09, 11 January 2009 (CET)

Category:Z Series

2009-01-11T20:06:19Z

Low: /* ThinkPad Z series */ no longer 'new' series

{| width="100%"
| <div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=ThinkPad Z series=
The Z Series widescreen notebooks offer the ultimate multimedia experience.
</div>
|| <thinkwiki>7</thinkwiki>
|}

{{stub}}
[[Category:Models]]

Installing Fedora 10 on a ThinkPad T400

2009-01-11T19:52:16Z

Low: Install Fedora 10 on a Thinkpad T400 moved to Installing Fedora 10 on a Thinkpad T400: Installing <distro> on a <model>

[[:Category:T400|T400]] '''Site under construction. You are invited building an useful guidance!'''

==BIOS Issues To Deal With Before Installation==

If you have a t400 (or T500 for that matter) that has the Switchable Graphics there are some things you need to know about

* The switchable graphics doesn't really "work" so much under Linux. This is unfortunate, but there are plenty of discussion as to the why's and hows of this. So as a Linux user you get a choice at boot as to which one you want.
*** Go into the BIOS on boot (F1) go into Config -> Display -> Graphics Device
** Either way you are going to want to '''DISABLE''' OS detection of switchable graphics. Don't ask me why, but the BIOS has a tendency to switch the actual display adapter out from under you.
** You must now choose either the '''EXTERNAL''' display (I.E. the ATI/AMD graphics card) or the '''INTERNAL''' (I.E. the on board Intel graphics)

This step really needs to be done '''before''' you try to do the install or setup Linux. Now you can change this at any time, but keep in mind that you will likely need to make changes to your xorg.conf file to have it switch decently. You can take a look at and try something like [http://lenovoblogs.com/insidethebox/?p=154 this blog post] but this is left to the user to try / experiment with.

==What just works (tm)==

* Wireless with iwlagn driver ([[Intel WiFi Link 5100/5300 WLAN controller]])
** 802.11bg both work fine along with WEP/WPA/WPA2, status LED lights up and does what you would expect. NetworkManager seems to do the right thing, no issues there
* [[Ethernet Controllers#Intel Gigabit (10/100/1000)|Intel Gigabit Ethernet Controller]]
** No issues here, plug in a cable and it just works
* Intel driver for Integrated Graphics ([[Intel Integrated Intel GMA 4500MHD]])
** Just works, quite happy. Detects the screen properly as 1440x900 and just goes with it. Kudos to the Xorg team (now get working on the [[http://www.thinkwiki.org/wiki/Switchable_Graphics]])
* UltraNav (Touchpoint and Trackpad)
** Horizontal and Vertical scrolling just worked.
* Optical drive
* Sound card
** To use your internal microphone you have to change to "HDA Intel CONEXANT Analog (ALSA)" in audio-settings.
* 7-in-1 card reader from Ricoh (MMC, Memory Stick, Mem Stick Pro, SD, SDHC, XD, XD Type H Memory)
** I've only tested with SD & SDHC (as that's all I have at the moment) but they work fine. The system very quickly recognizes that you've inserted a disk, and mounts it as you would expect. Please note you need to push the card into it so that it's flush (you'll hear a click). To eject push on it and it will eject.
* Thinklight control (This is BIOS only anyway so does not have the issue with the button problems mentioned below)
* Wireless toggle mechanical toggle switch (at the front) - works and is detected by the system.
* Built-in webcam with Skype, along with using the built-in microphone (used pulse audio for the output and the input is circumventing pulse right now)
* ACPI in general seems to work, battery status, fan status, temperatures, etc.
* Optical (ultrabay) hot swapping
** It just works, pull the drive out Linux will happily disable and remove it, put it back in and Linux detects and deals with adding it back in. Go sata drives!
* Bluetooth
** I was able to pair with several devices including a keyboard and two phones. Was unable to do much more than get the keyboard to work but bluetooth does work.
* Suspend / Resume (there is a caveat, look under what doesn't work)

== What doesn't work at all ==
* ATI [[fglrx]] driver for Discrete Graphics ([[ATI Mobility Radeon 3470 graphics]])
** Seems to be a matter of the binary driver not having kept up. Even trying with the driver released Dec. 10th, 2008 did not actually get a usable screen configuration. Likely cause is due to Fedora 10's more up to date Xorg server. Watch [http://rpmfusion.org/ RPM Fusion] and see when they pick up the driver
* Fingerprint reader
** Uses a new chipset out of AuthenTec
T: Bus=04 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS= 8 #Cfgs= 1
P: Vendor=08ff ProdID=2810 Rev=17.03
S: Product=Fingerprint Sensor
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 8 Ivl=0ms
...
Bus 004 Device 002: ID 08ff:2810 AuthenTec, Inc.
there does seem to be some hope though as the fprint project should be working on it [http://reactivated.net/fprint/wiki/Unsupported_devices fprint posting on AuthenTec AES2810]

* Suspend Resume
** Specifically the problem seems to be that suspend works fine but resume doesn't work '''if''' you have compiz turned on resume fails for some reason.

== Display / Mice / Xorg ==

=== Synaptics Touchpad ===

There is an excellent utility that's available via Yum called GSynaptics which uses the synaptics driver (documented here [[Synaptics_TouchPad_driver_for_X]]) But it's worth noting how to get it working with your Fedora 10 system

Specifically when Fedora boots up it likely won't have written an xorg.conf file, choosing instead to let the whole thing autodetect. This, though odd, works. However to get the synaptics driver to have the options you want you need to actually get an xorg configuration file in place. Simplest way is to go under

System -> Administration -> Display

'''Note:''' if you do not have this option install the system-config-display package

Once there basically make sure that your monitor is setup as to have the actual resolution of your display. Once you've done that just hit 'ok' and it will write out an xorg.conf. Once you've done that you can go and edit the xorg.conf file (/etc/X11/xorg.conf) and add the xorg.conf section from the [[Synaptics_TouchPad_driver_for_X]] page.

Once you've done that add

InputDevice "Synaptics Touchpad" "CorePointer"

under the ServerLayout section. Restart X and you should now be able to use GSynaptics.

== Issues with Fedora 10 ==

Ok so I'll admit, I did a fresh install and expected everything to just work (tm) - it didn't quite. There are a few things that still need to be tweaked to make it all work but it's getting there

=== Pulseaudio w/ GStreamer ===

So fresh install and setup a new user account and log in. '''*BOOM*''' first thing you are greated with is the gnome-volume-control crashing and hitting reload will just come back with 'no crashed again reload or remove from panel'. Further if you try to start gnome-volume-control and get a dialogue window that says "No volume control GStreamer plugins and/or devices found." If you install the nautilus-sound-converter and you find that nautilus doesn't load at all, this is also a symptom. You are likely hitting the same problem for all of these issues. The problem *seems* to be that the permissions on the gstreamer directory in your home dir is set in correctly. Easiest way to fix this is to do:

chmod -R 777 ~/.gstreamer-0.10;rm -rf ~/.gstreamer-0.10

After you do this things should work as you would expect again.

=== Extra Thinkpad buttons only work for root ===

I will admit I do not have a fix for this one yet, but it is one that is annoying me greatly. Basically things like the volume control, display brightness, control over bluetooth being on/off, etc or anything that uses the <Fn> key or the volume controls only works for the root user. Since it seems to work for the root user I'm guessing this is a permissions problem, but I have not tracked it down yet.

'''NOTE:''' things like the 'ThinkLight' that are fully BIOS controlled are not affected by this and work as expected. So far all I've seen that does this is the ThinkLight but I haven't done and exhaustive check.

'''Addendum:''' So I got the brightness display working as the non-root user if your under Gnome go under:

System -> Preferences -> System -> Power Management

Once that loads you'll see a small icon added in your notification bar that looks like a battery, the brightness display should now work.

'''Addendum 2:''' So I got the audio buttons working as well for non-root users. If your under Gnome go under:

System -> Preferences -> System -> PulseAudio Preferences

One that loads you should have access to the buttons. Volume Up/Down will display and actually change the volume. The Mute button will actually mute the audio, however you won't see any indication of it sadly.

Also of note it seems the media buttons (fn+ left,right,up,down) which are next, stop, play, previous, seem to work within some applications within gnome as well. Basically anything that can handle the X/Gnome shortcut key can make use of these buttons.

=== Extra Thinkpad buttons extras ===

So many of the buttons can be made to work without too much issue, sadly however there are a few buttons that might be useful. Here are a couple of quick scripts to help with that:

==== Bluetooth enable / disable ====

edit '''/etc/acpi/events/thinkpad-bluetooth.conf''' and write:
event=ibm/hotkey HKEY 00000080 00001005
action=/usr/local/sbin/bttoggle

'''Note:''' it seems the last bit in the HKEY (00001005) does seem to cleanly map to the FN key thus 00001005 is F5 and 00001008 maps to F8.

Next create an executable script (chmod +x) in '''/usr/local/sbin/''' called '''bttoggle'''
#!/bin/bash
INFO=/proc/acpi/ibm/bluetooth
STATE=$( grep "status" "${INFO}" | awk '{ print $2;}' )
case "${STATE}" in
enabled)
echo -n "disable" > $INFO
;;
disabled)
echo "enable" -n > $INFO
;;
*)
echo "usage: disable, enable"
esac

restart acpid: sudo service acpid restart

==== Touchpad enable / disable ====

This does assume you have the synaptics tools installed and setup properly, but...

edit '''/etc/acpi/events/thinkpad-trackpad.conf''' and write:
event=ibm/hotkey HKEY 00000080 00001008
action=/usr/local/sbin/trackpad-toggle

'''Note:''' it seems the last bit in the HKEY (00001005) does seem to cleanly map to the FN key thus 00001005 is F5 and 00001008 maps to F8.

Next create an executable script (chmod +x) in '''/usr/local/sbin/''' called '''trackpad-toggle'''
#!/bin/bash
STATE=$( /usr/bin/synclient -l | grep "TouchpadOff" | awk '{ print $3; }' )
case "${STATE}" in
0)
/usr/bin/synclient TouchpadOff=1
;;
1)
/usr/bin/synclient TouchpadOff=0
;;
*)
echo "usage: 0,1"
esac

restart acpid: sudo service acpid restart

[[Category:T400]][[Category:Ubuntu]][[Category:Fedora]]

Installing Fedora 10 on a ThinkPad T400

2009-01-10T13:23:49Z

Low: fixed link to Category:Fedora

Madwifi

2009-01-10T13:21:59Z

Low: fixed link to Category:SUSE

'''Madwifi''' (Multiband Atheros Driver for Wifi) is Linux driver for 802.11a/b/g universal NIC cards - Cardbus, PCI, or miniPCI - using Atheros chip sets.

The following (incomplete) list of adapters sold by IBM use the Atheros chips:
* [[IBM Dual-Band 11a/b Wi-Fi Wireless Mini PCI Adapter]]
* [[IBM 11b/g Wireless LAN Mini PCI Adapter]]
* [[IBM 11a/b/g Wireless LAN Mini PCI Adapter]]
* [[IBM 11a/b/g Wireless LAN Mini PCI Adapter II]]
* [[ThinkPad 11a/b/g Wireless LAN Mini Express Adapter]]
* IBM 802.11a Wireless LAN Cardbus Adapter
* IBM 11 a/b/g Wireless Cardbus Adapter

* (11a/b/g/n) Atheros Communications, Inc. Unknown device 0024 (rev 01) (using SVN revision 2360+)

== Packages ==
*Official {{Debian}} packages in the [http://packages.debian.org/src:madwifi non-free section]. See also the [http://alioth.debian.org/projects/pkg-madwifi/ Alioth project page] and the [http://madwifi.org/wiki/UserDocs/Distro/Debian Madwifi wiki].
*{{Debian}} Packages: http://www.marlow.dk/madwifi
*{{Debian}} Packages: http://www.users.tpg.com.au/sigm/debian/pkg-madwifi/
*{{Fedora}} Packages(1): http://rpm.livna.org
*{{Fedora}} Packages(2): http://www.atrpms.net/name/madwifi/
*{{Gentoo}} ebuild: {{cmduser|emerge net-wireless/madwifi-driver net-wireless/madwifi-tools}}
*{{SUSE}} Packages http://www.madwifi.org/suse/
*{{Ubuntu}} Package: {{cmduser|sudo apt-get install linux-restricted-modules-`uname -r`}}
*[http://madwifi.org/wiki/UserDocs/GettingMadwifi MadWifi packages and source] for these and other distributions

== Source ==
Detailed instructions can be found [http://madwifi.org/wiki/UserDocs/GettingMadwifi on the MadWiFi Wiki].

* [http://snapshots.madwifi.org/ Daily Snapshots]
* madwifi-ng:
:{{cmduser|svn checkout http://svn.madwifi.org/trunk madwifi-ng}}
* madwifi-old:
:{{cmduser|svn checkout http://svn.madwifi.org/branches/madwifi-old madwifi-old}}

== Installation ==

*Make sure that you've got sysctl support and the net/radio enabled (wireless extensions) in your kernel. Install the driver with make & make install
* further more you like to install the wireless tools from [http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html wireless tools]. Make sure the versions fit together by
:{{cmduser|iwconfig --version}}

Setting up [[wpa_supplicant]] with wpa-psk.

You can enable the wireless LAN status LED on your Thinkpad by following [http://madwifi.org/wiki/UserDocs/EnableLEDs these instructions] (tested on Thinkpad x60s).

== Status ==
Release 0.9.3[http://madwifi.org/wiki/Releases/0.9.3] available

Release notes
* switch to newer HAL, v0.9.18.0
* ensure compilation against recent kernel versions up to 2.6.20
* ensure compatibility back to kernel 2.4.22, drop support for 2.4.21 and older
* allow compilation without support of features such as fast frames, turbo mode, etc.
* support for some PCI Express cards fixed
* some security-related issues have been patched
* interoperation with wpa_supplicant and hostapd improved
* real channel noise instead of fixed -95dBm noise floor presented
* lots of bugs fixed, for different architectures and various modes of operation
* further improvements for build system

== Free Software HAL ==
The "official" madwifi driver consists of a BSD/GPL wrapper with an unmodifiable HAL (Hardware Abstraction Layer). This HAL is not binary firmware as with the Intel wireless chips, but a piece of code that needs to run in the Linux kernel. It consists of header files for which no permisison to modify is granted, and pre-compiled object files.
The vendor's position is that the Linux community simply needs to accept this sourceless HAL, since in principle
the Atheros chip could be tuned to any frequency, and thus produce RF interference with systems operating in those frequencies.

This binary HAL is unacceptable to the Linux kernel developers, and the Atheros driver in this state will never become part of the official kernel. Some OpenBSD developers, facing the same issue, reverse-engineered the binary HAL and have produced an open source driver ([[ath5k]]), which has now been picked up by the madwifi team as the future direction. At the same time the madwifi driver has been labeled 'legacy' to reinforce this point.

== Problems with system-config-network and Fedora Core 5 ==
If you use the livna repository to install madwifi for Fedora Core 5, it doesn't correctly update the modprobe configuration files. A [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=187640 bug] has been filed. The quick fix is to move the lines that were in
/etc/modprobe.d/madwifi into /etc/modprobe.conf and system-config-network now can configure the card.

== Much easier on Fedora Core 6 ==

I'm using FC6 w/KDE on an X22 and wireless was very easy using madwifi from Livna and a Linksys WPC55AG PC card.
I had already installed knetworkmanager, klaptop and configured working radeonfb and
working S3 suspend.
I then simply used yum to install madwifi, including a kernel upgrade, enabled the knetworkmanager services and rebooted.
After restarting, knetworkmanager found the Atheros card and my AP. I just had to choose the connection and was online in seconds.

== Problems on Fedora Core 9 ==
When installing madwifi 0.9.4 on my new machine (from source), ath_pci would load fine, apparently, but I could only see the wlan0 interface via iwconfig, and no attempt to create an ath0 interface or start it (via ifconfig) would work. I finally found the problem ([http://forums.fedoraforum.org/forum/showthread.php?p=990516 described in this email trail]) which indicates the new ath5k module is the problem.

As directed, I fixed it by editing '''/etc/modprobe.d''' and creating a file called '''madwifi''' with the following in it:
<pre>
alias wlan0 ath_pci
blacklist ath5k
</pre>
Although this enables ath0, I have yet to get the wirelss to actually connect to anything.

==Using Madwifi with SUSE Linux 10.1==
As of [[:Category:SUSE|SUSE Linux]] 10.1, the Madwifi packages are no longer included in the SUSE distribution because of the presence of closed source code. However, I was able to download, install, and configure Madwifi for my [[:Category:T40|IBM T40]] with the
[[IBM 11a/b/g Wireless LAN Mini PCI Adapter|IBM 11a/b/g Wireless Adapter (Atheros AR5212 802.11abg)]] as follows:
* Start yast2 and select Software--Installation Source. Add http://madwifi.org/suse/ as a source
* Install packages <tt>madwifi</tt> and <tt>madwifi-kmp-default</tt> (the latter has the kernel module, replace <tt>default</tt> with <tt>smp</tt> or other non-default kernel package if you're not running the default Suse kernel package as determined by <tt>uname -r</tt>)
* Reboot so the kernel modules can be loaded.
* Load the kernel modules by hand and see if the kernel recognizes your hardware:
<tt>modprobe aes; modprobe wlan_ccmp; modprobe ath_pci; lsmod |egrep 'Module|aes|wlan|ath'</tt>
* If recognized, put the modprobe lines above in your <tt>/etc/init.d/boot.local</tt> file. Otherwise, check for Linux kernel/Madwifi incompatibilities and hardware issues.
* Start yast2 and go to Network Devices-->Network Card and add and configure your wireless card. I recommmend checking the "Network Manager" box, as that allows dynamic GUI control over the wireless and Ethernet NICs.
* I have WPA-PSK enabled, so here's the fields I filled out: "User Controlled" device activation, DHCP Automatic Address Setup, "Managed" operating mode, "any" ESSID, "WPA-PSK" auth mode, key input type "passphrase" and I typed in my passphrase. I left expert settings alone.

== External links ==
* [http://www.madwifi.org Official website]
* [http://madwifi.org/wiki/Compatibility Official hardware compatibility list]
* [http://www.madwifi.org/wiki MadWiFi Wiki]
* [http://team.vantronix.net/ar5k/ OpenSource Atheros HAL]
* [http://www.ath-driver.org/ OpenSource Atheros driver for Linux]

[[Category:Drivers]]

Installing Fedora Core 5 on a ThinkPad X40

2009-01-10T13:19:41Z

Low: /* External Sources */ fixed category Fedora Core to Fedora

==External Sources==
*[http://www.catb.org/esr/faqs/Fedora-Core-on-Thinkpad-X40/ Fedora Core on Thinkpad X40 Customization HOWTO]

[[Category:X40]] [[Category:Fedora]]

Template:X61t

2009-01-10T13:18:18Z

Low:

[[:Category:X61 Tablet|X61 Tablet]][[Category:X61 Tablet]]

Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad X61

2009-01-10T13:13:10Z

Low: fixed category Ubuntu

== Preface ==

This pages applies to {{Ubuntu 7.10}} Tribe 3 and should be updated as soon as a newer release is available.

If you do not own a Ultra-Bay docking station you should keep a small Windows partition to (eventually) run BIOS updates. External USB-CDROMs do '''not''' wok. I don't know of any way to update the BIOS without having Windows installed.

== Installation ==

Some tutorials state you have to activate the SATA compatibility mode in the BIOS (Hit F1 when booting, choose Config -> Serial ATA -> Mode), but I did not touch that setting before installation and everything worked fine.

I used the Desktop-Live D for installation which even activated Desktop effects by default.

== Wireless ==

The Intel a/b/g/n (IPW4965) card requires the iwlwifi drivers from Intel ([http://www.intellinuxwireless.org/]). I tried different versions, but they all crashed my machine when actually joining a network.

Note: scanning (iwlist wlan0 scan) works fine

== Sound ==

== Brightness ==

[[Category:X61]][[Category:X61s]]

Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad X61

2009-01-10T13:11:15Z

Low: added categories, fixed wanted "Category:X61,X61s"

== Preface ==

This pages applies to {{Ubuntu}} 7.10 Tribe 3 and should be updated as soon as a newer release is available.

If you do not own a Ultra-Bay docking station you should keep a small Windows partition to (eventually) run BIOS updates. External USB-CDROMs do '''not''' wok. I don't know of any way to update the BIOS without having Windows installed.

== Installation ==

Some tutorials state you have to activate the SATA compatibility mode in the BIOS (Hit F1 when booting, choose Config -> Serial ATA -> Mode), but I did not touch that setting before installation and everything worked fine.

I used the Desktop-Live D for installation which even activated Desktop effects by default.

== Wireless ==

The Intel a/b/g/n (IPW4965) card requires the iwlwifi drivers from Intel ([http://www.intellinuxwireless.org/]). I tried different versions, but they all crashed my machine when actually joining a network.

Note: scanning (iwlist wlan0 scan) works fine

== Sound ==

== Brightness ==

[[Category:X61]][[Category:X61s]]

User:Low

2009-01-10T12:59:47Z

Low: /* about the System */ added links

== about Low ==
I'm a linux noob, really. Though I spent 5 years maintaining a huge website, I had little exposure to the system itself. At work I'm 50% on HP-UX, also as a user. I learn as I progress.
== about the System ==
'''[[:Category:R60|R60]]''' [[9461-DXG]]

[[Intel Core 2 Duo (Merom)|Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz]]

15" 1400x1050px w/[[ATI Mobility Radeon X1400|ATI X1400]]

'''[[:Category:Slackware|Slackware]] 12.1''' (pretty much 'vanilla' - only added the [[fglrx]] package for the ATI - and as you might have guessed: after reinstalling and recompiling the kernel about 20 times till I found out that for SATA you need some SCSI modules...)

'''fvwm''' 2.5.26

How to get special keys to work

2009-01-10T12:59:22Z

Low: /* NumPad (KeyPad) keys access by a key combination */ added some links (templates)

==Overview==
The following table gives an overview over the special keys found on ThinkPads and what is needed to make them work.
{| {{prettytable}}
! key !! standard function{{footnote|1}} !! tools supporting key{{footnote|2}} !! configurability{{footnote|3}} !! remarks
|-
| {{key|Fn}} || - || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || on release without completed key combination
|-
| {{key|Fn}}{{key|F1}} || - || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full ||
|-
| {{key|Fn}}{{key|F2}} || lock screen || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full || in models from T/X/Z 60 onwards
|-
| {{key|Fn}}{{key|F3}} || blank screen || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full ||
|-
| {{key|Fn}}{{key|F4}} || suspend to ram || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full || may generate ACPI event when not enabled in the ibm-acpi hotkey mask
|-
| {{key|Fn}}{{key|F5}} || switch bluetooth || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full || in models starting from 2002
|-
| {{key|Fn}}{{key|F6}} || - || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full ||
|-
| {{key|Fn}}{{key|F7}} || toggle display || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]], [[#tpb configuration|tpb]] || additional actions || [[Sample Fn-F7 script]]
|-
| {{key|Fn}}{{key|F8}} || toggle trackpoint/touchpad || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]], [[#tpb configuration|tpb]] || additional actions ||
|-
| {{key|Fn}}{{key|F9}} || eject from dock || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full ||
|-
| {{key|Fn}}{{key|F10}} || - || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| {{key|Fn}}{{key|F11}} || - || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full ||
|-
| {{key|Fn}}{{key|F12}} || hibernate || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full || may generate ACPI event when not enabled in the ibm-acpi hotkey mask
|-
| {{key|Fn}}{{key|Home}} / {{key|Fn}}{{key|Pos1}} || brightness up || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]], [[#tpb configuration|tpb]], [[KMilo]] || additional actions ||
|-
| {{key|Fn}}{{key|End}} || brightness down || [[thinkpad-acpi]], [[#tpb configuration|tpb]], [[KMilo]] || additional actions ||
|-
| {{key|Fn}}{{key|PageUp}} || toggle thinklight || [[thinkpad-acpi]], [[#tpb configuration|tpb]], [[KMilo]] || additional actions ||
|-
| {{key|Fn}}{{key|Space}} || toggle zoom || [[thinkpad-acpi]], [[#tpb configuration|tpb]], [[KMilo]] || full ||
|-
| {{key|Fn}}{{key|Ins}} || - || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]]|| full ||
|-
| {{key|Fn}}{{key|Del}} || - || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| {{key|Fn}}{{key|Backspace}} || - || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| {{key|NumLock}} || - || [[#xmodmap configuration|xmodmap]] || make working ||
|-
| {{key|Windows}} || - || [[#xmodmap configuration|xmodmap]] || remapping ||
|-
| {{ibmkey|Access IBM|#495988}} or {{ibmkey|ThinkPad|#494949}} or {{ibmkey|ThinkVantage|#495988}} || help application || [[thinkpad-acpi]],[[#tpb configuration|tpb]], [[KMilo]] || full ||
|-
| {{ibmkey|Home|#494949}} || open web browser || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]], [[KMilo]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards
|-
| {{ibmkey|Search|#494949}} || open search application || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]], [[KMilo]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards
|-
| {{ibmkey|Mail|#494949}} || open mail application || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]], [[KMilo]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards
|-
| {{ibmkey|Favorites|#494949}} || open favorites || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards
|-
| {{ibmkey|Reload|#494949}} || reload web page || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards
|-
| {{ibmkey|Abort|#494949}} || abort loading page || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards
|-
| {{ibmkey|Backward|#494949}} || previous page || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || ext. keyboards and ThinkPads starting from 2002
|-
| {{ibmkey|Forward|#494949}} || next page || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || ext. keyboards and ThinkPads starting from 2002
|-
| {{ibmkey|Volume up|#494949}} || volume up || [[thinkpad-acpi]], [[#tpb configuration|tpb]], [[KMilo]] || additional actions ||
|-
| {{ibmkey|Volume down|#494949}} || volume down || [[thinkpad-acpi]], [[#tpb configuration|tpb]], [[KMilo]] || additional actions ||
|-
| {{ibmkey|Volume mute|#494949}} || mute volume || [[thinkpad-acpi]], [[#tpb configuration|tpb]], [[KMilo]] || additional actions ||
|-
| {{ibmkey|Play/Pause|#494949}} || start/pause playback || [[#xmodmap configuration|xmodmap]] || full || {{X60s}} (Fn+Arrow Down)
|-
| {{ibmkey|Stop|#494949}} || stop playback || [[#xmodmap configuration|xmodmap]] || full || {{X60s}} (Fn+Arrow Up)
|-
| {{ibmkey|Next|#494949}} || play next || [[#xmodmap configuration|xmodmap]] || full || {{X60s}} (Fn+Arrow Right)
|-
| {{ibmkey|Previous|#494949}} || play previous || [[#xmodmap configuration|xmodmap]] || full || {{X60s}} (Fn+Arrow Left)
|-
| {{ibmkey|Power|#494949}} || shutdown || [[#ibm-acpi events|ibm-acpi]],[[thinkpad-acpi]] || full || triggered on pressing 3secs, but notebook goes off on 5sec press
|-
| Display lid || blank screen || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full ||
|-
| Ultrabay lid || announce ultrabay change || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| Dock eject || eject from dock || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| {{ibmkey|Tablet power|#494949}} || shutdown || [[#ibm-acpi events|ibm-acpi]] || full || triggered on pressing 3secs, but notebook goes off on 5sec press
|-
| {{ibmkey|Tablet orientation|#494949}} || rotates screen || [[#Mapping keys with setkeycodes|setkeycodes]] || full ||
|-
| {{ibmkey|Tablet shortcut|#494949}} || shortcut menu || [[#Mapping keys with setkeycodes|setkeycodes]] || full ||
|-
| {{ibmkey|Tablet Esc|#494949}} || esc key || [[#Mapping keys with setkeycodes|setkeycodes]] || full ||
|-
| {{ibmkey|Tablet Enter|#494949}} || enter key || [[#mapping keys with setkeycodes|setkeycodes]] || full ||
|-
| {{ibmkey|Tablet Up|#494949}} || up key || [[#Mapping keys with setkeycodes|setkeycodes]] || full ||
|-
| {{ibmkey|Tablet Down|#494949}} || down key || [[#Mapping keys with setkeycodes|setkeycodes]] || full ||
|-
| {{ibmkey|Tablet (unlabeled)|#494949}} || down key || [[#Mapping keys with setkeycodes|setkeycodes]] || full ||
|}

For completeness, note that the WiFi enable/disable switch is located (on the X61 and other models that have it) just under the front edge of the base of the machine. You should see a small horizontal slider switch. Enable by sliding it rightwards, disable by sliding it leftwards.

Tablet buttons vary with model. See [[Tablet Hardware Buttons]].

==Triggering key events==
===ibm-acpi/thinkpad-acpi events===
Some of the following events require a {{cmdroot|echo enable,0xffff >/proc/acpi/ibm/hotkey}} (when using ibm-acpi) in order to make acpi able to get information on them. Since the newer thinkpad-acpi has a larger number of bits that can be set in the mask, you might try {{cmdroot|echo enable,0xffffffff >/proc/acpi/ibm/hotkey}} if you are using this driver. These events can be used to [[How to configure acpid|configure acpid]].

{| {{prettytable}}
|+ events triggered by [[ibm-acpi]] for {{path|/etc/acpi/events}} files. May vary on different models.
! key !! event
|-
| {{key|Fn}}{{key|F1}} || ibm/hotkey HKEY 00000080 00001001
|-
| {{key|Fn}}{{key|F2}} || ibm/hotkey HKEY 00000080 00001002
|-
| {{key|Fn}}{{key|F3}} || ibm/hotkey HKEY 00000080 00001003
|-
| {{key|Fn}}{{key|F4}} || ibm/hotkey HKEY 00000080 00001004
|-
| {{key|Fn}}{{key|F5}} || ibm/hotkey HKEY 00000080 00001005
|-
| {{key|Fn}}{{key|F6}} || ibm/hotkey HKEY 00000080 00001006
|-
| {{key|Fn}}{{key|F7}} || ibm/hotkey HKEY 00000080 00001007
|-
| {{key|Fn}}{{key|F8}} || ibm/hotkey HKEY 00000080 00001008
|-
| {{key|Fn}}{{key|F9}} || ibm/hotkey HKEY 00000080 00001009
|-
| {{key|Fn}}{{key|F10}} || ibm/hotkey HKEY 00000080 0000100a
|-
| {{key|Fn}}{{key|F11}} || ibm/hotkey HKEY 00000080 0000100b
|-
| {{key|Fn}}{{key|F12}} || ibm/hotkey HKEY 00000080 0000100c
|-
| {{key|Fn}}{{key|Backspace}} || ibm/hotkey HKEY 00000080 0000100d
|-
| {{key|Fn}}{{key|Ins}} || ibm/hotkey HKEY 00000080 0000100e
|-
| {{key|Fn}}{{key|Del}} || ibm/hotkey HKEY 00000080 0000100f
|-
| {{key|Fn}}{{key|Home}}/{{key|Fn}}{{key|Pos1}} || ibm/hotkey HKEY 00000080 00001010
|-
| {{key|Fn}}{{key|End}} || ibm/hotkey HKEY 00000080 00001011
|-
| {{key|Fn}}{{key|PgUp}} || ibm/hotkey HKEY 00000080 00001012
|-
| {{key|Fn}}{{key|Space}} || ibm/hotkey HKEY 00000080 00001014
|-
| {{ibmkey|Volume up|#494949}}|| ibm/hotkey HKEY 00000080 00001015
|-
| {{ibmkey|Volume down|#494949}} || ibm/hotkey HKEY 00000080 00001016
|-
| {{ibmkey|Volume mute|#494949}} || ibm/hotkey HKEY 00000080 00001017
|-
| {{ibmkey|Access IBM|#495988}} or {{ibmkey|ThinkPad|#494949}} or {{ibmkey|ThinkVantage|#495988}} || ibm/hotkey HKEY 00000080 00001018
|-
| Ultrabay eject || ibm/bay MSTR 00000003 00000000
|-
| Ultrabay inserted || ibm/bay MSTR 00000001 00000000
|-
| Dock eject || ibm/dock GDCK 00000003 00000001
|-
| Wireless switch || ibm/hotkey HKEY 00000080 00007000
|}

By disassembling and editing the DSDT, more events can be added. HKEY events are triggered by calls to the MKHQ function, e.g. <tt>\_SB.PCI0.LPC.EC.HKEY.MHKQ(0Ã—1007)</tt> will trigger "ibm/hotkey HKEY 00000080 00001007". Most of these can be found in <tt>_Qxx</tt> methods within the DSDT, which are executed on embedded controller events, e.g. _Q10 is triggered by pressing Fn-F7. You can add a call to MKHQ into an existing <tt>_Qxx</tt> method to get it recognized by ibm-acpi as well as creating new <tt>_Qxx</tt> methods, which if you're lucky will correspond to an EC event that IBM never used (e.g. A 770 will send Fn-Home/End/PgUp/PgDn to ibm-acpi if hacked in this fashion). For example, [http://www.wormnet.eu/ibm-g40/morebuttons.dsl this is a modified block of DSDT for a G40].

=== ACPI events from the <tt>button</tt> module===

A few keys can generate ACPI events that result from the <tt>button</tt> kernel module, as long as they are masked off in the <tt>ibm-acpi</tt>/<tt>thinkpad-acpi</tt> hotkey's mask or the hotkey function of the latter module is disabled.

If you want the ThinkPad's BIOS and ACPI methods to know about these keys being pressed, you probably want to leave them masked out from ibm-acpi, and use their non-HKEY events listed below, instead.

{| {{prettytable}}
|+ events triggered by ACPI when hotkey is masked out or disabled.
! key !! event !! T60 event
|-
| {{ibmkey|Power|#494949}} || button/power PWRF 00000080 xxxxxxxx || button/power PWRF 00000080 00000001
|-
| {{key|Fn}}{{key|F4}} || button/sleep SLPB 00000080 00000001 || button/sleep SLPB 00000080 00000001
|-
| Display lid || button/lid LID 00000080 xxxxxxxx || button/lid LID 00000080 00000001
|}

===tpb configuration===
{| {{prettytable}}
|+ configuration keywords for [[tpb]] (to put in {{path|/etc/tpbrc}})
! key !! config keyword
|-
| {{ibmkey|Access IBM|#495988}} or {{ibmkey|ThinkPad|#494949}} || THINKPAD
|-
| {{ibmkey|Home|#494949}} || HOME
|-
| {{ibmkey|Search|#494949}} || SEARCH
|-
| {{ibmkey|Mail|#494949}} || MAIL
|-
| {{ibmkey|Favorites|#494949}} || FAVORITES
|-
| {{ibmkey|Reload|#494949}} || RELOAD
|-
| {{ibmkey|Abort|#494949}} || ABORT
|-
| {{ibmkey|Backward|#494949}} || BACKWARD
|-
| {{ibmkey|Forward|#494949}} || FORWARD
|-
| {{key|Fn}} || FN
|-
| {{key|Fn}}{{key|Space}} || CALLBACK (zoom on/off)
|-
| {{key|Fn}}{{key|PageUp}} || CALLBACK (thinklight on/off)
|-
| {{key|Fn}}{{key|F7}} || CALLBACK (display lcd/crt/both)
|-
| {{key|Fn}}{{key|F8}} || CALLBACK (expand on/off)
|-
| {{key|Fn}}{{key|Home}} / {{key|Fn}}{{key|Pos1}} || CALLBACK (brightness <percent>)
|-
| {{key|Fn}}{{key|End}} || CALLBACK (brightness <percent>)
|-
| {{ibmkey|Volume up|#494949}} || CALLBACK (volume <percent>)
|-
| {{ibmkey|Volume down|#494949}} || CALLBACK (volume <percent>)
|-
| {{ibmkey|Volume mute|#494949}} || CALLBACK (mute on/off)
|}

To all parameter keywords should be assigned the full path to the executables supposed to be started on key press.
The exectable provided for the CALLBACK keyword should take the parameters given in parentheses and act according to them.
If you want to use xmodmap for the HOME, SEARCH, MAIL, FAVORITES, RELOAD, ABORT, BACKWARD, FORWARD and FN keys you should
provide a <tt>XEVENTS OFF</tt> in your {{path|/etc/tpbrc}}.
You can use an appropriate executable to [[How to inject fake keystrokes|inject fake keystrokes]].

For Debian users, tpb is started from {{path|/etc/X11/Xsession.d/90tpb}}.

'''Sound Button configuration'''

''Note: Tested on T60p with Ubuntu 6.06 LTS''

Most Thinkpads have a hardware sound mixer, thus the volumes buttons should work without configuration. However, this change is not reflected in the software mixer. tpb has a switch to enable software mixer support via OSS. The manual recommends this only for devices without a hardware mixer, but it also works for other hadware mixer enabled devices, even with the ALSA system. Just put MIXER ON in your {{path|/etc/tpbrc}} file and you can see the effect immediately in any ALSA mixer (e.g. kmix). For this to work you need write permissions to {{path|/dev/nvram}}.

''Note: Tested on X21 with Ubuntu 6.06 LTS''

On the ThinkPad X21 (and maybe some other older models) ACPI causes problems with tpb. On an X21 using acpi the volume buttons would work occasionally, and the OSD for tpb functions would rarely work. If a volume buttons was pressed too often, sometimes the computer would enter a low power (unplugged state) and would require a reboot. The solution is to use APM instead of ACPI. Instructions can be found in [[How_to_make_APM_work]].

===KMilo configuration===
The programs to be executed by [[KMilo]] are configured via the KDE Control Center (<tt>kcontrol</tt>), under <tt>System Administration --> IBM Thinkpad Laptop</tt>. Note that you can use appropriate commands to [[How to inject fake keystrokes|inject fake keystrokes]].

===xmodmap configuration===
xmodmap enables you to edit the modifier map and keymap tables that are used to translate keycodes into keysyms.
Understood? Well, basically it allows you to give the X server a dictionary for the translation of keycodes like "97" into more human readable synonyms like "Home". This way xmodmap allows you to make the special keys of your keyboard known to X applications.

To discover the keycode that a certain keypress produces, use the tool {{cmduser|xev}}

Usually you should write your keycode-keysym associations into the file {{path|~/.Xmodmap}}. This file is usually read by the X session startup scripts of your system, so that the mappings automatically get included everytime you run the X server.

The {{path|~/.Xmodmap}} lines for our purpose are in the form of
keycode <keycode> = <keysym>

Load the assocation using the command

{{cmduser|xmodmap ~/.Xmodmap}}

(some configurations do this automatically upon X startup).

The following table shows the keycodes generated by the ThinkPad special keys and sensible keysyms to assign them to.
{| {{prettytable}}
|+ keycodes and recommended keysyms
! key !! keycode !! keysym
|-
| {{ibmkey|Access IBM|#495988}} or {{ibmkey|ThinkPad|#494949}} || 159 || XF86LaunchA
|-
| {{ibmkey|Backward|#494949}} || 234 || XF86Back or F19
|-
| {{ibmkey|Forward|#494949}} || 233 || XF86Forward or F20
|-
| {{ibmkey|Play/Pause|#494949}} || 162 || XF86AudioPlay
|-
| {{ibmkey|Stop|#494949}} || 164 || XF86AudioStop
|-
| {{ibmkey|Next|#494949}} || 153 || XF86AudioNext
|-
| {{ibmkey|Previous|#494949}} || 144 || XF86AudioPrev
|-

| {{ibmkey|Home|#494949}} || 178 || XF86HomePage
|-
| {{ibmkey|Search|#494949}} || 229 || XF86Search
|-
| {{ibmkey|Mail|#494949}} || 236 || XF86Mail
|-
| {{ibmkey|Favorites|#494949}} || 230 || XF86AddFavorite or XF86Favorites
|-
| {{ibmkey|Reload|#494949}} || 231 || XF86Reload
|-
| {{ibmkey|Abort|#494949}} || 232 || XF86Stop
|-
| {{key|Fn}} || 227 || F35
|}

Note: You can also use xkeycaps (an X tool to display and edit the X keyboard mapping) to generate proper .Xmodmap.

Note: if you are running [[tpb]] you might need to add the line <tt>XEVENTS=off</tt> into your tpbrc to stop it from grabbing the key events and allow them to get through to X instead. See [[http://www.thinkwiki.org/wiki/Tpb]] for more detailed instruction on how to use tpb and xmodmap.

Note: XF86Forward and XF86Back do not work correctly in Firefox. You may want to map them to F19 and F20 instead if you use Firefox.

Note: The "XF86AudioPlay" etc. just works with a few programs. To make it work with more multimedia programs you have map the key to use something like [http://www.kde-apps.org/content/show.php/ReMoot?content=63140 ReMoot]. ReMoot is a command line wrapper that control 18 of the most common multimedia applications.

=====Enabling the Windows and Menu Keys=====
On some systems the Windows and Menu keys may not be recognized. You can enable then by
making the following changes:

keycode 115 = F13
keycode 227 = F35

F13 and F35 are used for the Windows and and Menu keys respectively. Labelling keycpode 227 as "Menu" may conflict with the right-mouse-click event.

=====Using Caps Lock as Super L (Windows key)=====
You can easily use Caps Lock as Win key by adding the following in your ~/.Xmodmap:
! No Caps Lock
clear lock
! Caps Lock as Win key
add mod4 = Caps_Lock
=====NumLock=====
On the ThinkPad {{600}}, {{T20}}, {{T21}}, {{T22}}, {{T30}}, {{X20}}, {{X21}}, {{X31}}, {{X40}}, {{T42p}}, {{T43}}, {{R51}}, {{R52}} and possibly other models, X does not recognize the keycode for {{key|NumLk}} = {{key|Shift}}+{{key|ScrLk}}. To fix this, add the following to {{path|~/.Xmodmap}} in your home directory or {{path|/etc/X11/Xmodmap}} and run <tt>xmodmap</tt>, ex: <tt>xmodmap ~/.Xmodmap</tt>:
keycode 77 = Num_Lock

This configuration also enables the respective LED.

Please note, pressing the {{key|Shift}}+{{key|ScrLk}} key combination, without first following the above configuration, will start an accessibility feature, which will allow the numeric keypad to maneuver the mouse pointer. Starting this accessibility feature and subsequently running xmodmap, as described above, results in the accessibility feature and the numeric lock LED functioning simultaneously. As such, the above configuration should be completed before the accessibility feature is started in order to produce numbers.
======T60 (and possibly others)======
It seems that on the T60, PrtSc, ScrLk and Pause all generate the correct keycodes, however Fn-PrtSc (labelled as SysRq) generates keycode 64 (Alt_L) followed by the expected 111 (Sys_Req) on down and the same thing in the opposite order on release. Fn-ScrLk (labelled as NmLk) does indeed toggle the Numlock, but only seems to register as an X event the first time it is engaged. The above solution does not appear to work. This is perhaps because the Numlock toggle is built into the firmware rather than controlled by the kernel. Finally, Fn-Pause (labelled as Break) generates keycode 37 (Control_L) followed by the expected keycode 110 (Break) on down and the same thing in reverse order on release.
=====NumPad (KeyPad) keys access by a key combination=====
The current state is that you have to switch NumLock '''on''' via {{key|Fn}}+{{key|ScrLk}} and then e.g. type {{key|u}} to get a {{key|KP_4}} (NumPad 4). To get back to normal keyboard, you have to type {{key|Fn}}+{{key|ScrLk}} again.

Some people (including me) are missing on recent Thinkpads the option to have Fn as a modifier key to access the NumPad instead, i.e. and e.g. {{key|Fn}}+{{key|u}} gives you {{key|KP_4}}.

There is currently no way to make this work in a simple way (pleeeease correct me if I am wrong!), though there is a work-around. Instead of using {{key|Fn}} for accessing the NumPad, {{key|CapsLock}} can get this function by being mapped as Mode_switch (the {{key|AltGr}} on international keyboards). The {{key|Fn}} can be remapped to be Caps_Lock - while at the same time retaining its function to access the special laptop functions (e.g. {{key|Fn}}+{{key|F4}} for sleep}}, by using .Xmodmap.

So on my {{R60}} running fvwm@{{Slackware}} 12.1 the .Xmodmap would look like this:

! Make the forward and back buttons work
keycode 233 = XF86Forward
keycode 234 = XF86Back
! Make the WIN key to Super modifier
keycode 115 = Super_L
! Set the Caps_Lock physical key to Mode_switch (like AltGr on intl. keyboards)
keycode 66 = Mode_switch
! Set the Fn key to work as Caps_Lock now. The special key combos like Fn-F4 for "sleep" still work then
keycode 227 = Caps_Lock
clear lock
add lock = Caps_Lock
! Now we activate those new keys. Find some free mod slots (xmodmap) and put them there.
clear mod4
clear mod5
add mod4 = Super_L
add mod3 = Mode_switch
! It's time to add the keypad keys to the third position of the key definition (pure shift mode_switch shift+mode_switch)
keycode 16 = 7 ampersand KP_7
keycode 17 = 8 asterisk KP_8
keycode 18 = 9 parenleft KP_9
keycode 19 = 0 parenright KP_Divide
keycode 30 = u U KP_4
keycode 31 = i I KP_5
keycode 32 = o O KP_6
keycode 33 = p P KP_Multiply
keycode 44 = j J KP_1
keycode 45 = k K KP_2
keycode 46 = l L KP_3
keycode 47 = semicolon colon KP_Subtract
keycode 58 = m M KP_0
! ... I have to use the coma key, too, on the keypad...so I set it to be F20 (which is not existing on normal keyboards and thus is free... check for side effects in programmes accepting F12+ keys!)
keycode 59 = comma less F20
keycode 60 = period greater KP_Decimal
keycode 61 = slash question KP_Add

{{WARN|Your keycodes might be different as well as your '''mod''#''''' settings.}}
Use {{cmduser|xmodmap}} and {{cmduser|xmodmap -pke}} to check your ModMap, and the tool {{cmduser|xev}} to obtain your exact key codes.

===Mapping keys with setkeycodes===
You can use the setkeycodes command to remap certain keys. I.e. you can use {{cmdroot|setkeycodes 6e 109 6d 104 69 28 6b 1}} to map the Tablets Up and Down keys to the standard PageUp and PageDown keys and Tablet Escape and Enter to their respective keys.

The following table shows the scancodes generated by the ThinkPad keys. They vary with model - see [[Tablet Hardware Buttons]].
{| {{prettytable}}
|+ scancodes
! key !! scancode
|-
| {{ibmkey|Tablet orientation|#494949}} || 0x6c
|-
| {{ibmkey|Tablet Shortcut|#494949}} || 0x68
|-
| {{ibmkey|Tablet Esc|#494949}} || 0x6b
|-
| {{ibmkey|Tablet Enter|#494949}} || 0x69
|-
| {{ibmkey|Tablet Up|#494949}} || 0x6d
|-
| {{ibmkey|Tablet Down|#494949}} || 0x6e
|-
| {{ibmkey|Tablet (unlabeled)|#494949}} || 0x67
|}

===acpi_fakekey===
You can turn acpi events into user-level xevents by putting <tt>acpi_fakekey</tt> commands into the acpi action scripts. There are several layers involved in using acpi keys in this way, so I'll go through the example of using the ThinkVantage button to open xmms.

My ThinkVantage button generates an '''acpi event''' "ibm/hotkey HKEY 00000080 00001018", so we have the event file <tt>/etc/acpi/events/ThinkVantage</tt> for it which executes the script <tt>/etc/acpi/actions/fakekey-macro.sh</tt>.
<pre>
event=ibm/hotkey HKEY 00000080 00001018
action=/etc/acpi/actions/fakekey-macro.sh
</pre>
In turn, the executable <tt>/etc/acpi/actions/fakekey-macro.sh</tt> script calls acpi_fakekey with the '''key number''' defined in <tt>/usr/share/acpi-support/key-constants</tt> as $KEY_MACRO which is 112 (you could just as well choose an other key number, just make sure that it doesn't belong to something else like the "j" key or something).
<pre>
#!/bin/sh
. /usr/share/acpi-support/key-constants
acpi_fakekey $KEY_MACRO
</pre>
I have no idea how this actually corresponds to which xevent is generated, so I can find out out by running the program <tt>xev</tt> and hitting the ThinkVantage button while the mouse is in the <tt>xev</tt> window (remember to <tt>/etc/init.d/acpid restart</tt> first if you just created the <tt>/etc/acpi/events/ThinkVantage</tt> file). I get something popping up in the terminal where I ran xev that looks like this:
<pre>
KeyPress event, serial 30, synthetic NO, window 0x2800001,
root 0x6a, subw 0x0, time 2000522842, (138,83), root:(781,500),
state 0x0, keycode 239 (keysym 0x0, NoSymbol), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 30, synthetic NO, window 0x2800001,
root 0x6a, subw 0x0, time 2000522842, (138,83), root:(781,500),
state 0x0, keycode 239 (keysym 0x0, NoSymbol), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
</pre>
This tells me that the <tt>acpi_fakekey 112</tt> as executed by hitting the ThinkVantage button generates KeyPress event followed by a KeyRelease event with '''keycode''' 239 and that this keycode has been assigned no corresponding '''keysym'''. Thus, I am free to assign the keycode to any keysym I want. You can find a list of available keysyms in <tt>/usr/share/X11/XKeysymDB</tt>. Again try and pick one that is not likely to have already been taken by something, such as <tt>XF86LaunchA</tt>. To assign this keysym to keycode 239, you can either edit ~/.Xmodmap on an individual user basis, or edit the systemwide <tt>/etc/X11/Xmodmap</tt> file to contain the line
<pre>
keycode 239 = XF86LaunchA
</pre>
If you choose to go with the former, you may need to run <tt>xmodmap ~/.Xmodmap</tt> for every login session in order to read in your ~/.Xmodmap file if your window manager does not do it for you. Regardless of which option you choose, you can run <tt>xmodmap <file></tt> to read in the updated Xmodmap file without logging out and logging back in.

You should now find that hitting the ThinkVantage button creates the following output from <tt>xev</tt>:
<pre>
KeyPress event, serial 55, synthetic NO, window 0x2800001,
root 0x6a, subw 0x0, time 2001286078, (0,106), root:(643,523),
state 0x0, keycode 239 (keysym 0x1008ff4a, XF86LaunchA), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 55, synthetic NO, window 0x2800001,
root 0x6a, subw 0x0, time 2001286078, (0,106), root:(643,523),
state 0x0, keycode 239 (keysym 0x1008ff4a, XF86LaunchA), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
</pre>
Note the change of <tt>(keysym 0x0, NoSymbol)</tt> to <tt>(keysym 0x1008ff4a, XF86LaunchA)</tt>.

You're now ready to map <tt>XF86LaunchA</tt> to executing xmms. This is highly dependent on what keygrabber you decide to use. For openbox, I edit my <tt>~/.config/openbox/rc.xml</tt> file and add the following entry in the <keyboard> section:
<pre>
<keybind key="XF86LaunchA">
<action name="Execute">
<startupnotify>
<enabled>true</enabled>
</startupnotify>
<command>
xmms
</command>
</action>
</keybind>
</pre>
After, right clicking on the desktop and selecting the "Reconfigure" menu option, you should then have xmms pop up when you hit the ThinkVantage key.

==Example Applications==
===Web Browsers===
====Firefox (<3.0)====

There are various ways to assign actions to the browser keys. The easiest way is to install [http://mozilla.dorando.at/keyconfig.xpi keyconfig.xpi] from http://mozilla.dorando.at, which adds a menu entry Tools->Keyconfig. Then you can assign any action you want to the F19/F20 keys (you still need to create {{path|~/.Xmodmap}} as explained above).

The remaining discussion gives you various more complicated ways to achieve the same thing.
To have firefox make use of the browser keys you need to modify one of its files{{footnote|4}}.
To do this you will first need to extract it from the {{path|browser.jar}} archive. Do...

Step 1: Edit .Xmodmap and add entries for F19 and F20 as explained above.

Step 2:

Note: <firefox-directory> is probably /usr/lib/firefox. Use your version so, if you have 3.0.1 or 3.0.2 use /usr/lib/firefox-3.0.1

:{{cmdroot|cd <firefox-directory>/chrome}} 
:{{cmdroot|unzip browser.jar}}

The file of interest is {{path|content/browser/browser.xul}}. Edit it {and don't forget to make a backup copy first}...
:{{cmdroot|vi content/browser/browser.xul}}

Look for the '''<keyset id="mainKeyset">''' section and add the following lines within...
<key id="goBackKb" keycode="VK_F19" command="Browser:Back" />
<key id="goForwardKb" keycode="VK_F20" command="Browser:Forward" />

The Command you need for Next Tab
<key id="goBackTabKb" keycode="VK_F19" oncommand="gBrowser.mTabContainer.advanceSelectedTab(-1)" />
For the Previous Tab
<key id="goForwardTabKb" keycode="VK_F20" oncommand="gBrowser.mTabContainer.advanceSelectedTab(1)" />

Now save the file and repackage the {{path|browser.jar}} archive...
:{{cmdroot|zip -rD0 browser.jar content/browser/}}

That's it.

Step 3: Restart Firefox.

{{HINT|Outdated: Another interesting Page on Firefox is http://dqd.com/~mayoff/notes/thinkpad/dqdnavkeys/ It uses different key mappings (F19 resp. F20) but a ready [http://dqd.com/~mayoff/notes/thinkpad/dqdnavkeys/dqdnavkeys-1.2.xpi .xpi] is provided which is pretty comfortable. However, this xpi file does not install on Firefox 1.5. or later.}}

{{HINT| You can also use the [http://extensionroom.mozdev.org/more-info/keyconfig keyconfig] extension to configure custom keys. This extension works with Firefox 1.5 and also with Firefox 2.0. The Command you need for Next Tab is gBrowser.mTabContainer.advanceSelectedTab(1,true); For Previous Tab its gBrowser.mTabContainer.advanceSelectedTab(-1,true); You can alternatively install the [http://www.pqrs.org/~tekezo/firefox/extensions/functions_for_keyconfig/index.html functions for keyconfig] and set the variable f4kc_NextTab to F20 and f4kc_PrevTab to F19.}}.

====Firefox 3.0====
Thankfully the people at Mozilla decided to include the expected functionality for the XF86Back and XF86Forward keysyms in the new release so all you need to do is
 <code># printf 'keycode 234 = XF86Back\nkeycode 233 = XF86Forward' >> /etc/X11/Xmodmap</code> 
And to make this take effect immediately (i.e., without having to log out and log in again), as a regular user run:
 <code>{{cmduser|Xmodmap /etc/X11/Xmodmap}}</code>

For Hardy Heron, the xmodmap command is all lowercase. Also, the /etc/X11/Xmodmap file is not being read on boot. I've added the command to my .bashrc to have it called on startup.

====Konqueror====
KDE allows you set key mappings for KDE applications (Go to KMenu > System > Control Center > Regional & Accessibility > Keyboard Shortcuts). By default (at least in KDE 3.5), XF86Back and XF86Forward are set as alternatives to Alt-Left and Alt-Right, and are mapped to KDE Back and Forward navigation actions.

If you use Konqueror as your only browser, you only need to set up {{path|~/.Xmodmap}} as described [[#xmodmap configuration|above]] to assign ThinkPad back/forward keys to the symbols XF86Back/XF86Forward. This also make these keys work for other KDE applications such as Quanta Plus, KPackage and so on (not all KDE applications honor this setting, e.g. KDE help system doesn't).

If you want to use Firefox, however, the above settings do not work. You will have to map ThinkPad back/forward keys to F19/F20 as described [[#Firefox|above]], and change KDE navigation key settings to use F19/F20 instead of the default.

====Opera====
However this isn't a simple configration file, you can set your browser manually. 
Go to Tool > Settings > Mouse and keyboard > Keyboard settings > Edit > Browser Window. There add F19 - Back and F20 - Forward. Now you can surf using your TP keys ;-)

====Epiphany====
To get the keys work in epiphany, you could use the extension from [http://crashman.homelinux.org/~andre/public/epiphany%20extensions/thinkpad%20browserkeys/ here]
You just need to edit your Xmodmap like described for Firefox < 3.0 (bind the keys on F19 and F20)

===Open an application===

To configure the ThinkVantage button to open a terminal window in Gnome:

Step 1:
Use xev to find the keycode generated by the button on your machine. In my case is is 159.

Step 2:
Create an entry in .Xmodmap like so

keycode 159 = XF86LaunchA

replacing 159 by the keycode found in step 1. Load the map using

:{{cmd|xmodmap ~/.Xmodmap}}

Step 3:
Configure the required function (e.g. open terminal window) in System->Preferences->Keyboard shortcuts

===Window Managers===
====fvwm====
To get the {{ibmkey|Forward|#494949}} and {{ibmkey|Backward|#494949}} keys to cycle through pages in the virtual desktop, add this to your {{path|~/.fvwmrc}}:
Key XF86Back A A Scroll -100000 0
Key XF86Forward A A Scroll +100000 0
If you use multiple virtual desktops, you could instead use the keys to flip between them by using GotoDesk.

====fluxbox====
To get the keys to cycle through pages in the virtual desktop, add this to your {{path|~/.fluxbox/keys}}:
None F19 :PrevWorkspace
None F20 :NextWorkspace

====pekwm configuration====
You can make the two browser keys switch workspaces in pekwm, by adding the following two lines to the {{path|~/.pekwm/keys}} file:
KeyPress = "Mod1 XF86Back" { Actions = "GoToWorkspace prev" }
KeyPress = "Mod1 XF86Forward" { Actions = "GoToWorkspace next" }

====pwm====
Another example how to use these two keys to switch between pwm tabs. These two lines should be added to {{path|~/.pwm/keys-default.conf}} or {{path|/etc/pwm/keys-default.conf}}:
kbind "Back", "switch_rot", -1
kbind "Forward", "switch_rot", 1

====IceWM====
To make IceWM cycle workspaces using the {{ibmkey|Forward|#494949}} and {{ibmkey|Backward|#494949}} keys, change these two options in {{path|~/.icewm/preferences}} (Provided you assigned keysyms F19 and F20 with xmodmap):
# "Previous workspace" shortcut
KeySysWorkspacePrev="F19"
# "Next workspace" shortcut
KeySysWorkspaceNext="F20"

==== Gnome/metacity ====

Follow the [https://wiki.ubuntu.com/Keybindings Ubuntu guide].

===Other Uses===
====Console tools configuraton====
To make the {{ibmkey|Forward|#494949}} and {{ibmkey|Backward|#494949}} keys useful in console, add this to your keymap ({{path|/etc/console/boottime.kmap.gz}} in {{Debian}}):
keycode 158 = Decr_Console
keycode 159 = Incr_Console

Alternatively you can load this script (perhaps on system startup) to enable Backward/Forward button console (VT) switch:

#!/bin/sh
echo keycode 158 = Decr_Console | loadkeys
echo keycode 159 = Incr_Console | loadkeys

It should work with any distro.

====Cycling through tabs====
In Gnome and Xfce4, Ctrl-PageUp/Ctrl-PageDown move to the previous/following open tab in all applications that have tabbed user interfaces (terminal emulator, web browser, ...). To make use of the {{ibmkey|Forward|#494949}} and {{ibmkey|Backward|#494949}} keys for this task, there're two possibilities.

For both ways, you should map the keycodes 233 and 234 to XF86Back and XF86Forward as described in [[#xmodmap_configuration|xmodmap configuration]].

=====Using xautomation=====
xautomation can be found [http://hoopajoo.net/projects/xautomation.html here].

Create two files with permissions 755:

{{path|/usr/local/bin/tp_back}}:
<bash>
#!/bin/bash
/usr/bin/xte 'keydown Control_L' 'keydown Page_Up' 'keyup Page_Up' 'keyup Control_L'
</bash>

{{path|/usr/local/bin/tp_forward}}:
<bash>
#!/bin/bash
/usr/bin/xte 'keydown Control_L' 'keydown Page_Down' 'keyup Page_Down' 'keyup Control_L'
</bash>

Use your desktop's keyboard shortcut editor to assign XF86Back as a shortcut for tp_back and XF86Forward as a shortcut for tp_forward.

This should work in all distros and with all window managers (you might have to use other key combinations than Ctrl-PageUp and Ctrl-PageDown).

=====Redirecting XF86Back/XF86Forward=====
Create {{path|/etc/X11/xkb/compat/thinkpad}}:
<pre>
// $XFree86$
// XFree86 special keysyms
default partial xkb_compatibility "basic" {
interpret.repeat= True;

interpret XF86Back {
action = Redirect(Key=<PGUP>, modifiers=Control);
};
interpret XF86Forward {
action = Redirect(Key=<PGDN>, modifiers=Control);
};
};
</pre>

Edit {{path|/etc/X11/xkb/compat/complete}} and add <tt>'''augment "thinkpad"'''</tt> so that it looks similar to the following:
<pre>
// $XKeyboardConfig: xkbdesc/compat/complete,v 1.3 2005/10/17 00:42:11 svu Exp $
// $Xorg: complete,v 1.3 2000/08/17 19:54:34 cpqbld Exp $
default xkb_compatibility "complete" {
include "basic"
augment "iso9995"
augment "mousekeys"
augment "accessx(full)"
augment "misc"
augment "xfree86"
augment "level5"
augment "thinkpad"
};
</pre>

==External Sources==
*[http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-51537 IBMs page on configuring the ThinkPad buttons (ThinkPad, Access IBM, Mail, Search, and Home buttons) under Linux]
*[http://dqd.com/~mayoff/notes/thinkpad/dqdnavkeys/ Rob Mayoffs page on using IBM Keyboard Navigation Keys in Linux Mozilla and Firefox]
*[http://snarfed.org/space/thinkpad+keys+in+firefox Ryan Barretts blog article about using the browser keys in Firefox]
*[http://chaotika.org/~bluesceada/?page=soft&sub=thinkpad#acpibutn DennisG's help to get the ibm-acpi buttons do useful things] on a {{Z61e}} and possibly {{Z61m}}, {{Z61t}} and {{Z61p}}

{{footnotes|
#Note that the associated functionality for Fn-F* key combinations is not consistent amongst all ThinkPads. We are maintaining [[Default meanings of special keys|a table of associated meanings]].
#if there are more than one tool listed, one is sufficient
#'full' means you can completely reassign any action to be triggered by the key, 'additional actions' means you can trigger actions in addition to the standard function of the key, which can not be changed.
#Thanks go to Ryan Barrett for writing the [http://snarfed.org/space/thinkpad+keys+in+firefox little howto] on [http://snarfed.org/space/start his blog].
}}

Intel Core 2 Duo (Penryn)

2009-01-10T10:06:44Z

Low: fixed link to Merom

{| 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;">

The Intel 2 Core is the successor of the [[Intel Core 2 Duo (Merom)]] processor. Unlike the Merom, Penryn uses the new 45um process which makes it cooler and uses less power.

=Features=
*Dual Core
*EM64T
*[http://en.wikipedia.org/wiki/Vanderpool#Intel_Virtualization_Technology_.28Intel_VT.29 Intel Virtualization Technology ]
*XD-Bit
*[[SIMD|MMX]], [[SIMD|SSE]], [[SIMD|SSE2]], [[SIMD|SSE3]], [[SIMD|SSSE3]], [[SIMD|SSE4.1]], XD Bit, iAMT2, Intel VT instruction sets
*800 or 1066 MHz FSB
*45 nm fabrication process
*3-6 MB L2-Cache
*[[SpeedStep|Enhanced Intel SpeedStep (EIST)]]
</div>
|}

=Available Types and ThinkPads featuring them=
==Standard Voltage==
{| border=1 cellspacing=0 cellpadding=2
|- style="background:#ffdead;white-space:nowrap;"
! Nr. || colspan=2 | Frequency (MHz) || L2 Cache || FSB (MHz)|| VT || colspan=2 | core Voltage (V) || colspan=2 | TDP (W) || ThinkPad Models
|- style="background:#ffdead;"
! !!max. !! min. !! !! !! !! high !! low !! high freq !! low freq !!
|-
| T8300 || 2400 || 800 || 3MB || 800 || yes || 1.25 || 1 ? || ? || ? || {{X61}}, {{T61}}
|-

|}

=See also=
[[Intel_Core_Solo_(Yonah)|Intel Core Solo (Yonah)]]

[[Intel Core Duo (Yonah)]]

== External Links ==
*[http://www.intel.com/products/processor_number/chart/core2duo.htm Intel - Processor Numbers and Features]
*[http://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors#Mobile_processors Wikipedia - Intel Core 2 mobile microprocessors]

[[Category:Components]]

Template:SL Series

2009-01-10T09:53:52Z

Low: â†Created page with 'SL SeriesCategory:SL_Series'

[[:Category:SL_Series|SL Series]][[Category:SL_Series]]

ThinkPad Advanced Dock

2009-01-10T09:27:17Z

Low: Added R60 to the "supported TPs" list

{| cellspacing="0" cellpadding="2" border="0"
| style="vertical-align:top;" | __TOC__
[[image:thinkpad-advanced-dock.gif|ThinkPad Advanced Dock]]
| 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;">
== ThinkPad Advanced Dock ==
The ThinkPad Advanced Dock (Model # 250310U) contains basic pass-through connections for notebook ports, including power pass-through. It comes with an integrated power supply. Besides all the pass-through ports the ThinkPad Advanced Dock comes with an UltraBay, PCI Express slot, 6-in-1 media card reader, On/Off switch, key lock and a slot for a cable lock.

=== Fix for Poweroff on Docking ===
http://www-307.ibm.com/pc/support/site.wss/MIGR-67382.html

=== Features ===
* Passthrough ports:
** Ethernet (RJ45)
** Modem (RJ11)
** [[VGA Port|VGA]]
** DVI-D
** [[Serial Port|Serial (DB9-M)]]
** [[Parallel Port|Parallel (DB25-F)]]
** [[PS/2 Port|Combined PS/2 Mouse + Keyboard]]
** Audio Microphone-in
** Audio Headphone-out
** Digital Audio (S/PDIF)
* USB (5-ports)
* [[UltraBay|Ultrabay Enhanced]]
* PCI-Express slot
{{NOTE|
Only 1x speed, but 16x graphics cards will work. Speeds of the interface will be between PCI and AGP bus speeds
standard length - i.e. about an inch longer than the connector. Only thin cards will fit. Many performance video cards with heat sink/fans are too thick.

Validated Cards:
* <Insert Cards here>
}}

* 6-in-1 media card reader
** [[xD Card slot|xD-Picture]]
** [[SD Card slot|SD]]
** [[CF Card slot|Compact Flash]]
** [[SD Card slot|MultiMedia Card]]
** [[SmartMedia Card slot|SmartMedia]]
** [[MS Card slot|Sony Memory Stick]]
* Kensington Lock connector
* Key lock
* Power button
* Integrated power supply
</div>
|}
* [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-61393 ThinkPad Advanced Dock - Publications]

==IBM part numbers==
* order part number: P/N 250410U
* FRU part number: 26R9061

== Supported ThinkPads ==
* ThinkPad {{T500}}, {{T400}}, {{T61}}, {{T61p}}, {{T60}}, {{T60p}}, {{W500}}, {{R500}}, {{R400}}, {{R60}}, {{R61}}, {{Z61}}, {{Z60}}, {{Z60m}}, {{Z60t}}, {{Z61p}}

Category:X200

2008-12-30T10:21:58Z

Low: /* Notes */ grammar fix

{| width="100%"
|style="vertical-align:top" |
=== ThinkPad X200 ===
This page gives an overview of all ThinkPad X200 related topics.

<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
==== Standard Features ====
* One of the following processors:
** [[Intel Core 2 Duo]] P8400, 2.26GHz, 3MB L2, 1066MHz FSB
** [[Intel Core 2 Duo]] P8600, 2.40GHz, 3MB L2, 1066MHz FSB
* Intel Graphics Media Accelerator 4500 MHD onboard graphics
** 12" CCFL with 1280×800 (WXGA, 200 nit)
* Support for up to 4GB DDR3-RAM [[PC3-8500]]
** As of 27 Aug 2008, 4GB option is most available and '''only''' if you select upgrade to Windows Vista Business 64
* One of the following hard drives:
** 80,160,250 GB SATA 2.5" 5400/7200RPM
** 320 GB 5400RPM
** 200 GB SATA 2.5" 7200RPM with [[Full Disk Encryption (FDE)]]
** 64,128 GB SATA 1.8" SSD
* ThinkPad X200 Ultrabase
** DVD-ROM, CD-RW/DVD-ROM, DVD Burner, Blu-ray
* One of the following expansion slots:
** 5-1 Media card Reader with Modem
** 3-1 Media card Reader without Modem (to save weight): SD, MMC, and another?
* [[Ethernet Controllers#Intel Gigabit (10/100/1000)|Intel Gigabit Ethernet Controller]]
* [[MiniPCI Express slot]] 1 with one of the following:
** [[ThinkPad 11b/g Wireless LAN Mini-PCI Express Adapter III]] (Atheros AR242x chipset)
** [[Intel Wifi Link 5100 (AGN)]]
** [[Intel Wifi Link 5300 (AGN)]]
* [[MiniPCI Express slot]] 2 with one of the following:
** Integrated WWAN with [[GPS]]
**: ''I believe this is a category, which includes the AT&T and Verizon cards below, rather than a distinct option. Unconfirmed. [[User:Mitchell|Mitchell]] 21:54, 28 October 2008 (CET)''
** [[Ericsson_F3507g_Mobile_Broadband_Module|Integrated Ultra Wide Band (UWB) for AT&T]]
** Integrated Ultra Wide Band (UWB) for Verizon
** WiMAX (late 2008)
** [[Intel® Turbo Memory hard drive cache]] 2GB
* Optional Features
** Integrated camera
** Integrated digital microphone
** Security cable slot
** [[Integrated Fingerprint Reader]]
* [[ThinkPad_Bluetooth_with_Enhanced_Data_Rate_(BDC-2)|Bluetooth]]
* [[Embedded Security Subsystem|IBM Embedded Security Subsystem 2.0]]
* [[Active Protection System|IBM Active Protection System]]
* TrackPoint '''only'''
* One of the following batteries
** 4-cell battery, 29 Wh (14.4 V, 2.0 Ah). up to 3.3 hr, 1.34kg
** 4-cell *tablet, 29 Wh (14.4 V, 2.0 Ah).
** 6-cell battery, 56 Wh (10.8 V, 5.2 Ah). up to 6.5 hr, 1.47kg (slightly elevates the back)
** 8-cell *tablet, 66 Wh (14.4 V, 4.6 Ah)
** 9-cell battery, 85 Wh (10.8 V, 7.8 Ah). up to 9.8 hr, 1.63kg (protrudes out back 22.8cm/.9in)
</div>

==== Resources ====
* [http://shop.lenovo.com/ISS_Static/merchandising/US/PDFs/x200_datasheet.pdf X200 Technical Specifications (pdf)]
* [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-70149 Hardware Maintenance Manual (HMM) - ThinkPad X200, August 2008 Edition] ''(from [http://www.lenovo.com/us/en/ lenovo] / Support / User's guides & manuals)''

==== Reviews ====
* [http://www.notebookreview.com/default.asp?newsID=4497 Notebookreview.com] 2008-07-15
* [http://www.laptopmag.com/review/laptops/lenovo-thinkpad-x200.aspx Laptopmag.com] 2007-07-14
* [http://reviews.cnet.com/laptops/lenovo-thinkpad-x200/4505-3121_7-33184078.html Cnet.com] 2008-08-14

==== Notes ====
Sometimes even basic information is hard to find. Here's a place for it.
* Lenovo is having fulfillment problems (2008 Q4). Take estimated ship dates with a grain of salt. Ordering from Lenovo seems to be working better than resellers. Some resellers have yet to receive their first unit. One person I know received an X200 within days (direct, replacing stolen machine), another has been waiting for ~2 months.
* The '''X200T does ''not'' support [http://en.wikipedia.org/wiki/Multi-touch Multi-touch]!'''. "MultiTouch" is Lenovo's misleading way of saying you can use your finger, in addition to a pen. The X200T uses Wacom's no-longer-cutting-edge non-multitouch screen. Only one contact point is available in hardware.
*: Though, hypothetically, you could get two points from a MultiTouch screen, one from finger contact, and one from a stylus hovering over but not touching the screen - they are available in linux as separate devices. It's not clear it's ever been done.
* [[GPS]] - If you have an optional WWAN card (AT&T or Verizon), you have GPS. ''unconfirmed''
* The 5300 normally has 3 x 3 antennas. Adding the webcam reduces this to 2 x 2. ''unconfirmed''
*: Any other conflicts? Bluetooth, etc?
* X200T configured with SSD do '''not''' include the [[Active Protection System]] accelerometer. Despite alternate uses (theft deterrence). Confirmed by Lenovo US sales phone, 2008-10. [[User:Mitchell|Mitchell]] 21:54, 28 October 2008 (CET)
* X200 configured with SSD include the [[Active Protection System]] accelerometer (at least 7454-CTO models shipped in Q4 2008). [[User:Vminko|Vminko]] 02:41, 30 December 2008 (CET)
* The [http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=AN&subtype=CA&htmlfid=897/ENUS108-588&appname=lenovous&language=en X200 Tablet Sleeve] supports 4 and 8 cell batteries, but not 9 cell. ''from announcement''
* The X200 does not have a touchpad. For folks who really want one, a somewhat messy possibility ''might'' be [http://www.ergonomictouchpad.com/ergonomic_touchpad.php www.ergonomictouchpad.com] (never used - no endorsement) which looks vaguely like a [http://www.cirque.com/cpages/?page=17 Cirque TSM9925 Touchpad] with velcro and wire added.
* There can be a ''big'' cost difference between preconfigured units from VARs, and custom configured units from shop.lenovo.com, as of 2008-10-31 ([http://alltp.blogspot.com/2008/10/heckuva-deal-on-lenovo-x200-tablet-pc.html examples]).
*: But shipping delays may be even greater than when ordering directly from Lenovo (2008 Q4).

[[Category:X Series]]

Talk:Harddrive Upgrade

2008-12-24T15:34:21Z

Low: Why are Seagate Momentus drives recommended?

Why are Seagate Momentus drives recommended?
--[[User:Low|Low]] 16:34, 24 December 2008 (CET)

Category talk:R61i

2008-12-24T07:34:36Z

Low: /* 4.2.2 Hotkeys that generated an event but did not work ootb */ - Hinto xmodmap

== 4.2 Hotkeys ==

I got some of the Fn+Cursor-keys to work by doing some work within /etc/X11/xkb/symbols; it worked fine for me in the first set up (Ubuntu 8.04 amd64) though it kind of stopped working when I re-installed to 8.10 x86. What's working for me at the moment is the Play/Pause hotkey (globally; associated in amarok's global shortcuts) and the Previous/Next Track/Stop keys (only with amarok focussed).

Here's a couple of pieces which still need assembling for a fully functional piece of advice:

I created the file /etc/X11/xkb/symbols/lenovo-thinkpad-r61i-hotkeys with this content:

// Layout for Lenovo Thinkpad R61i's multimedia keys
//
// $XFree86: xc/programs/xkbcomp/symbols/lenovo-thinkpad-r61i-hotkeys,v 0.1 2008/11/14 19:00:34 Pumba Exp $

default partial

xkb_symbols "audio" {

key <I20> { [ XF86AudioMute ] };
key <I2E> { [ XF86AudioLowerVolume ] };
key <I30> { [ XF86AudioRaiseVolume ] };

// Play, Pause
key <I22> { [ XF86AudioPlay ] };

// Previous track
key <I10> { [ XF86AudioPrev ] };

// Next track
key <I19> { [ XF86AudioNext ] };

// Stop
key <I24> { [ XF86AudioStop ] };

};

Then I edited "my" language's file in /etc/X11/xkb/symbols (the one that looks like your country code, probably) to include the lines I just wrote:

[...]

default

xkb_symbols "basic" {

include "latin(type4)"
include "lenovo-thinkpad-r61i-hotkeys(audio)"

[...]

};

If I could only remember how I figured out the "key <I#>" part... It had something to do with xev and comparing with some other files...

=== 4.2.1 Hotkeys that worked out-of-the-box ===

anyway, here's the keys that worked ootb for me:

{{key|Fn}}+{{key|Page Up}} -- small light on the edge of the screen. Seems to be built into the hardware

{{key|Fn}}+{{key|Pos 1}}

{{key|Fn}}+{{key|End}} -- increase/dim screen brightness (KDE)

{{key|Fn}}+{{key|Roll}} -- Num lock/enables "numeric keypad"

{{key|Fn}}+{{key|F5 }} -- Bluetooth (plus Wireless?)

{{key|Fn}}+{{key|F12}} -- Suspend to RAM

=== 4.2.2 Hotkeys that generated an event but did not work ootb ===

{{key|Fn}}+{{key|F2}} -- Lock Screen (generates event: XF86AudioMute)

{{key|Fn}}+{{key|F4}} -- Sleep (generates event: XF86Sleep)

{{key|Fn}} -- when being held for "a moment": generates event "XF86WakeUp"

-----

{{HELP|What does the xev output "XKeysymToKeycode" mean? Why does it sometimes return a different keycode than the key pressed actually generated? And is there any way of changing this?}}
{{HINT|Does that have anything to do with a remapping of keys via xmodmap? Check $ xmodmap -pke for details. Cheers, Low}}

List of DMI IDs

2008-12-15T18:32:13Z

Low: /* R series */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
This page maintains a database of [http://en.wikipedia.org/wiki/Desktop_Management_Interface DMI] information which can be used to identify ThinkPad models. It is intended as an aid for driver development.
{{HELP|We need more information about older models, especially those released before 2004. Please [[#Adding_entries|add your model]] to the database.}}
{{NOTE|If your ThinkPad is not using the [[BIOS Upgrade Downloads|latest BIOS]], and you would be willing to [[BIOS Upgrade|upgrade your BIOS]], please add your ThinkPad to this table twice: '''before''' and '''after''' the BIOS upgrade. This information helps us a great deal, so your contribution would be very appreciated.}}
|}

==DMI ID database==

<div style="font-size: 80%">
{| border="1" cellspacing="0" cellpadding="2"
|-
! Model
! <tt>system- manufa cturer</tt>
! <tt>system- product- name</tt>
! <tt>system- version</tt>
! <tt>baseboard- manufa cturer</tt>
! <tt>baseboard- product- name</tt>
! <tt>baseboard- version</tt>
! <tt>chassis- manufa cturer</tt>
! <tt>chassis- version</tt>
! <tt>bios- vendor</tt>
! <tt>bios- version</tt>
! <tt>bios- release- date</tt>
! Embedded controller
! Notes
|-
! colspan=14 style="text-align:center;background:#efefef;" |
====Numbered series====
|-
| {{600E}} 2645-5AU
|| IBM || 26455AU || Not Available || IBM || 26455AU || Not Available || IBM || Not Available || IBM || INET36WW || 11/20/1999
||
||
|-
| {{600X}} 2645-5FU
|| IBM || 26455FU || Not Available || IBM || 26455FU || Not Available || IBM || Not Available || IBM || INET55WW || 11/30/1999
||
||
|-
! colspan=14 style="text-align:center;background:#efefef;" |

====A series====
|-
| {{A21m}} 2628-FSG
|| IBM || 2628FSG || Not Available || IBM || 2628FSG || Not Available || IBM || Not Available || IBM || KXET24WW (1.02b) || 12/19/2000
||
||
|-
| {{A21m}} 2628-FSG
|| IBM || 2628FSG || Not Available || IBM || 2628FSG || Not Available || IBM || Not Available || IBM || KXET36WW (1.09 ) || 05/08/2003
||
||
|-
| {{A21m}} 2628-GTU
|| IBM || 2628GTU || Not Available || IBM || 2628GTU || Not Available || IBM || Not Available || IBM || KXET29WW (1.03d) || 03/21/2001
||
||
|-
| {{A22p}} 2629-USG
|| IBM || 2629USG || Not Available || IBM || 2629USG || Not Available || IBM || Not Available || IBM || KYET36WW (1.09a) || 10/17/2002
||
|| {{WARN|Outdated BIOS}}
|-
| {{A31}} 2652-PBU
|| IBM || 2652PBU || Not Available || IBM || 2652PBU || Not Available || IBM || Not Available || IBM || 1NET15WW (1.09 ) || 04/06/2005
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1NHT04WW-1.01 ]-</nowiki>
||
|-
| {{A31p}} 2653H6U
|| IBM || 2653H6U || Not Available || IBM || 2653H6U || Not Available || IBM || Not Available || IBM || 1GET31WW (1.03 ) || 07/23/2002
||
|| {{WARN|Missing EC string, extremely outdated BIOS}}{{HELP|We need a report to know if the latest BIOS fixes the missing EC string}}
|-
! colspan=14 style="text-align:center;background:#efefef;" |

====G series====
|-
| {{G41}} 2881-75M
|| IBM || 288175M || ThinkPad G41 || IBM || 288175M || Not Available || IBM || Not Available || IBM || 1XET47WW (1.06 ) || 01/14/2005
||
||
|-
! colspan=14 style="text-align:center;background:#efefef;" |
====R series====
|-
| {{R40}} 2681-5UU
|| IBM || 26815UU || Not Available || IBM || 26815UU || Not Available || IBM || Not Available || IBM || 1OET57WW (1.23 ) || 03/23/2005
||
|| {{WARN|Outdated BIOS}}
|-
| {{R40}} 2681-HSG
|| IBM || 2681HSG || Not Available || IBM || 2681HSG || Not Available || IBM || Not Available || IBM || 1OET61WW (1.27 ) || 06/29/2006
||
|| {{WARN|Outdated BIOS}}
|-
| {{R40}} 2722-B3G
|| IBM || 2722B3G || Not Available || IBM || 2722B3G || Not Available || IBM || Not Available || IBM || 1PET62WW (1.30 ) || 09/29/2005
||
||
|-
| {{R40}} 2897-B4U
|| IBM || 2897B4U || Not Available || IBM || 2897B4U || Not Available || IBM || Not Available || IBM || 1PET52WW (1.20 ) || 03/03/2004
||
||
|-
| {{R40e}} 2684-L8G
|| IBM || 2897B4U || Not Available || IBM || 2897B4U || Not Available || IBM || Not Available || IBM || 1SET62WW (1.30 ) || 07/09/2004
||
|| {{WARN|Outdated BIOS}}
|-
| {{R50}} 1829-7QG
|| IBM || 0123456 || ThinkPad R50 || IBM || 0123456 || Not Available || IBM || Not Available || IBM || 1RETDPWW (3.21 ) || 06/02/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
|{{R50e}} 1834-JAG
|| IBM || 1834JAG || ThinkPad R50e || IBM || 1834JAG || Not Available || IBM || Not Available || IBM || 1WET82WW (2.02 ) || 02/21/2005
|| <nowiki>Handle 0x0022, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1VHT28WW-1.04 ]-</nowiki>
||
|-
|{{R50p}} 1832-2AG
|| IBM || 18322AG || ThinkPad R50p || IBM || 18322AG || Not Available || IBM || Not Available || IBM || 1RETC2WW (3.03 ) || 04/07/2004
|| <nowiki>Handle 0x0029, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[1RHT66WW-3.00a ]-</nowiki>
||
|-
| {{R51}} 1829-DRG
|| IBM || 1829DRG || ThinkPad R51 || IBM || 1829DRG || Not Available || IBM || Not Available || IBM || 1RETC2WW (3.03 ) || 04/07/2004
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT66WW-3.00a ]-</nowiki>
||
|-
| {{R51}} 1829-9MG
|| IBM || 18299MG || ThinkPad R51 || IBM || 18299MG || Not Available || IBM || Not Available || IBM || 1RETDOWW (3.20 ) || 02/27/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{R51}} 1829-L7G
|| IBM || 1829L7G || ThinkPad R51 || IBM || 1829L7G || Not Available || IBM || Not Available || IBM || 1RETDNWW (3.19 ) || 10/13/2005
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[1RHT70WW-3.03 ]-</nowiki>
||
|-
| {{R51}} [[1830-DG4]]
|| IBM || 1830DG4 || ThinkPad R51 || IBM || 1830DG4 || Not Available || IBM || Not Available || IBM || 1RETDPWW (3.21 ) || 06/02/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{R51}} [[1830-DG4]]
|| IBM || 1830DG4 || ThinkPad R51 || IBM || 1830DG4 || Not Available || IBM || Not Available || IBM || 1RETDRWW (3.23 ) || 06/18/2007
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{R51}} 1836-GEU
|| IBM || 1836GEU || ThinkPad R51 || IBM || 1836GEU || Not Available || IBM || Not Available || IBM || 1RETDLWW (3.17 ) || 07/27/2005
|| <nowiki>Handle 0x0029, DMI type 11, 5 bytes. String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{R51}} 2883-ELU
|| IBM || 2883ELU || ThinkPad R51 || IBM || 2883ELU || Not Available || IBM || Not Available || IBM || 1VET69WW (1.27 ) || 03/03/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[1VHT28WW-1.04 ]-</nowiki>
||
|-
| {{R52}} 1846-AQG
|| IBM || 1846AQG || ThinkPad H || IBM || 1846AQG || Not Available || IBM || Not Available || IBM || 76ET58WW (1.18 ) || 07/19/2005
|| <nowiki>Handle 0x0029, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[76HT14WW-1.04 ]-</nowiki>
|| {{NOTE|Weird system version, this bug is known fixed in latest BIOS}}
|-
| {{R52}} 1846-AQG
|| IBM || 1846AQG || ThinkPad R52p || IBM || 1846AQG || Not Available || IBM || Not Available || IBM || 76ET68WW (1.28 ) || 11/15/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[76HT16WW-1.06 ]-</nowiki>
||
|-
| {{R52}} 1846-AQG
|| IBM || 1846AQG || ThinkPad R52p || IBM || 1846AQG || Not Available || IBM || Not Available || IBM || 76ET69WW (1.29 ) || 12/06/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[76HT16WW-1.06 ]-</nowiki>
||
|-
| {{R52}} 1847-CTO
|| IBM || 1847W15 || ThinkPad R52 || IBM || 1847W15 || Not Available || IBM || Not Available || IBM || 76ET69WW (1.29 ) || 12/06/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[76HT16WW-1.06 ]-</nowiki>
||
|-
| {{R52}} 1847-W62
|| IBM || 1847W62 || ThinkPad . || IBM || 1847W62 || Not Available || IBM || Not Available || IBM || 76ET58WW (1.18 ) || 07/19/2005
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[76HT14WW-1.04 ]-</nowiki>
|| {{NOTE|Weird system version, this bug is known fixed in latest BIOS}}
|-
| {{R52}} 1847-W62
|| IBM || 1847W62 || ThinkPad R52 || IBM || 1847W62 || Not Available || IBM || Not Available || IBM || 76ET65WW (1.25 ) || 05/18/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[76HT16WW-1.06 ]-</nowiki>
||
|-
| {{R52}} 1858-6MM
|| IBM || 18586MM || ThinkPad R52 || IBM || 18586MM || Not Available || IBM || Not Available || IBM || 70ET40WW (1.04 ) || 06/02/2005
|| <nowiki>Handle 0x0029, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[70HT26WW-1.03 ]-</nowiki>
||
|-
| {{R52}} 1858-6SM
|| IBM || 18586SM || ThinkPad R52 || IBM || 18586SM || Not Available || IBM || Not Available || IBM || 70ET57WW (1.17 ) || 07/15/2005
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[70HT26WW-1.03 ]-</nowiki>
||
|-
| {{R52}} 1846-4CG
|| IBM || 18464CG || ThinkPad R52 || IBM || 18464CG || Not Available || IBM || Not Available || IBM || 76ET65WW (1.25 ) || 05/18/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[76HT15WW-1.05 ]-</nowiki>
||
|-
| {{R52}} 1846-4CG
|| IBM || 18464CG || ThinkPad R52 || IBM || 18464CG || Not Available || IBM || Not Available || IBM || 76ET58WW (1.18 ) || 07/19/2005
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[76HT16WW-1.06 ]-</nowiki>
||
|-
| {{R52}} 1846-B5G
|| IBM || 1846B5G || ThinkPad H || IBM || 1846B5G || Not Available || IBM || Not Available || IBM || 76ET58WW (1.18 ) || 07/19/2005
|| <nowiki>Handle 0x0029, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[76HT14WW-1.04 ]-</nowiki>
||
|-
| {{R60e}} 0657-4TG
|| LENOVO || 06574TG || ThinkPad R60e || LENOVO || 06574TG || Not Available || LENOVO || Not Available || LENOVO || 7EET18WW (1.04 ) || 07/28/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[7EHT13WW-1.05 ]-</nowiki>
||
|-
| {{R60}} 9456-6FG
|| LENOVO || 94566FG || ThinkPad R60 || LENOVO || 94566FG || Not Available || LENOVO || Not Available || LENOVO || 7CET50WW (1.05 ) || 07/28/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7CHT19WW-1.07 ]-</nowiki>
||
|-
| {{R60}} 9456-6FG
|| LENOVO || 94566FG || ThinkPad R60 || LENOVO || 94566FG || Not Available || LENOVO || Not Available || LENOVO || 7CETB7WW (2.07 ) || 11/13/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7CHT21WW-1.09 ]-</nowiki>
||
|-
| {{R60}} 9461-54G
|| LENOVO || 946154G || ThinkPad R60 || LENOVO || 946154G || Not Available || LENOVO || Not Available || LENOVO || 7CET50WW (1.05 ) || 07/28/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7CHT19WW-1.07 ]-</nowiki>
||
|-
| {{R60}} 9461-54G
|| LENOVO || 946154G || ThinkPad R60 || LENOVO || 946154G || Not Available || LENOVO || Not Available || LENOVO || 7CETC1WW (2.11 ) || 01/09/2007
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7CHT21WW-1.09 ]-</nowiki>
|| {{NOTE|With this bios version the brightness control buttons don't work for kernel < 2.6.20}}
|-
| {{R60}} 9460MR2
|| LENOVO || 9460MR2 || ThinkPad R60 || LENOVO || 9460MR2 || Not Available || LENOVO || Not Available || LENOVO || 7CETC6WW (2.16 ) || 04/18/2007
|| <nowiki>Handle 0x0026, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[7CHT21WW-1.09 ]-</nowiki>
||
|-
| {{R60}} 9461-DXG
|| LENOVO || 9461DXG || ThinkPad R60 || LENOVO || 9461DXG || Not Available || LENOVO || Not Available || LENOVO || 7CETB6WW (2.06 ) || 10/16/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7CHT21WW-1.09 ]-</nowiki>
||
|-
| {{R60}} 9461-DXG
|| LENOVO || 9461DXG || ThinkPad R60 || LENOVO || 9461DXG || Not Available || LENOVO || Not Available || LENOVO || 7CETD2WW (2.22 ) || 05/28/2008 || <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7CHT22WW-1.10 ]-</nowiki>
||
|-
| {{R60}} 9462-GAG
|| LENOVO || 9462GAG || ThinkPad R60 || LENOVO || 9462GAG || Not Available || LENOVO || Not Available || LENOVO || 7CETB5WW (2.05 ) || 10/13/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7CHT21WW-1.09 ]-</nowiki>
||
|-
| {{R61}} 8918-5QG
|| LENOVO || 89185QG || ThinkPad R61 || LENOVO || 89185QG || Not Available || LENOVO || Not Available || LENOVO || 7KETA7WW (2.07 ) || 12/06/2007
|| <nowiki>Handle 0x0028, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[7KHT24WW-1.08 ]-</nowiki>
||
|-
| {{R61}} 8919-W4P
|| LENOVO || 8919W4P || ThinkPad R61 || LENOVO || 8919W4P || Not Available || LENOVO || Not Available || LENOVO || 7KET76WW (1.26 ) || 10/18/2007
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT22WW-1.06 ]-</nowiki>
|| {{NOTE|According to the sticker on the bottom of the notebook as well as according to Lenovo web it is 8919-CTO subtype}}
|-
| {{R61}} 8919-W6X
|| LENOVO || 8919W6X || ThinkPad R61 || LENOVO || 8919W6X || Not Available || LENOVO || Not Available || LENOVO || 7KET71WW (1.21 ) || 08/22/2007
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT22WW-1.06 ]-</nowiki>
||
|-
|
|| LENOVO || 8919W6X || ThinkPad R61 || LENOVO || 8919W6X || Not Available || LENOVO || Not Available || LENOVO || 7KETB9WW (2.19 ) || 06/05/2008
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT24WW-1.08 ]-</nowiki>
||
|-
| {{R61}} 8919-DFG
|| LENOVO || 8918DFG || ThinkPad R61 || LENOVO || 8918DFG || Not Available || LENOVO || Not Available || LENOVO || 7KETA9WW (2.09 ) || 12/27/2007
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT24WW-1.08 ]-</nowiki>
||
|-
| {{R61}} 8943-DMG
|| LENOVO || 8943DMG || ThinkPad R61 || LENOVO || 8943DMG || Not Available || LENOVO || Not Available || LENOVO || 7QET34WW (1.16 ) || 03/24/2008
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7QHT15WW-1.00 ]-</nowiki>
||
|-
| {{R61}} 7733-1ES
|| LENOVO || 77331ES || ThinkPad R61 || LENOVO || 77331ES || Not Available || LENOVO || Not Available || LENOVO || 7LETB0WW (2.10 ) || 01/21/2008
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT24WW-1.08 ]-</nowiki>
||
|-
| {{R61}} 7733-1ES
|| LENOVO || 77331ES || ThinkPad R61 || LENOVO || 77331ES || Not Available || LENOVO || Not Available || LENOVO || 7LETB4WW (2.14 ) || 03/24/2008
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT24WW-1.08 ]-</nowiki>
||
|-
| {{R61i}} 7650-D7G
|| LENOVO || 7650D7G || ThinkPad R61e || LENOVO || 7650D7G || Not Available || LENOVO || Not Available || LENOVO || 7PETB0WW (2.10 ) || 01/21/2008
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT24WW-1.08 ]-</nowiki>
||
|-
| {{R400}} 7439-A85
|| LENOVO || 7439A85 || ThinkPad R400 || LENOVO || 7439A85 || Not Available || LENOVO || Not Available || LENOVO || 7UET45WW (1.15 ) || 09/08/2008
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7VHT12WW-1.01 ]-</nowiki>
||
|-
! colspan=14 style="text-align:center;background:#efefef;" |

====S series====
|-
| {{s30}} 2639-4WJ
|| IBM || 26394WJ || Not Available || IBM || 2609BS1 || Not Available || IBM || Not Available || IBM || 18ET45WW (1.45) || 07/10/2001
|| <nowiki></nowiki>
||
|-
! colspan=14 style="text-align:center;background:#efefef;" |

====SL series====
|-
| {{SL500}} 2746-3ZG
|| LENOVO. || 27463ZG || ThinkPad SL500 || LENOVO || BOXSTER || LENOVO 6AET42WW || LENOVO || LENOVO 6AET42WW || LENOVO || 6AET42WW || 08/04/2008
|| <nowiki></nowiki>
|| {{WARN|IdeaPad EC and BIOS. This is an IdeaPad in disguise.}}
|-
! colspan=14 style="text-align:center;background:#efefef;" |

====T series====
|-
| {{T20}} 2647-UC2
|| IBM || 2647UC2 || Not Available || IBM || 2647UC2 || Not Available || IBM || Not Available || IBM || IYET45WW (1.08a) || 12/21/1999
||
|| {{WARN|Very outdated BIOS}}
|-
| {{T21}} 2647-8AU
|| IBM || 26478AU || Not Available || IBM || 26478AU || Not Available || IBM || Not Available || IBM || KZET34WW (1.16 ) || 04/28/2004
||
||
|-
| {{T22}} 2647-4EG
|| IBM || 26474EG || Not Available || IBM || 26474EG || Not Available || IBM || Not Available || IBM || 16ET31WW (1.11 ) || 03/20/2003
||
||
|-
| {{T22}} 2647-8EU
|| IBM || 26478EU || Not Available || IBM || 26478EU || Not Available || IBM || Not Available || IBM || 16ET32WW (1.12 ) || 04/27/2004
||
||
|-
| {{T23}} 2647-4NU
|| IBM || 26474NU || Not Available || IBM || 26474NU || Not Available || IBM || Not Available || IBM || 1AET62WW (1.18 ) || 07/06/2004
|| <nowiki>Handle 0x0024, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[1AHT23WW-1.06a ]-</nowiki>
||
|-
| {{T23}} 2647-8MG
|| IBM || 26478MG || Not Available || IBM || 26478MG || Not Available || IBM || Not Available || IBM || 1AET56WW (1.13 ) || 07/02/2002
||
|| {{NOTE|Missing EC string, this bug is known to be fixed in latest BIOS}}
|-
| {{T23}} 2647-8MG
|| IBM || 26478MG || Not Available || IBM || 26478MG || Not Available || IBM || Not Available || IBM || 1AET62WW (1.18 ) || 07/06/2004
|| <nowiki>Handle 0x0024, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[1AHT23WW-1.06a]-</nowiki>
||
|-
| {{T30}} 2366-85G
|| IBM || 236685G || Not Available || IBM || 236685G || Not Available || IBM || Not Available || IBM || 1IET69WW (2.08 ) || 06/11/2004
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[1IHT18WW-1.05 ]-</nowiki>
||
|-
| {{T30}} 2366-GU1
|| IBM || 2366GU1 || Not Available || IBM || 2366GU1 || Not Available || IBM || Not Available || IBM || 1IET69WW (2.08 ) || 06/11/2004
|| <nowiki>Handle 0x0024, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[1IHT19WW-1.06 ]-</nowiki>
||
|-
| {{T30}} 2366-JBU
|| IBM || 2366JBU || Not Available || IBM || 2366JBU || Not Available || IBM || Not Available || IBM || 1IET71WW (2.10 ) || 06/16/2006
|| <nowiki>Handle 0x0024, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1IHT20WW-1.07 ]-</nowiki>
||
|-
| {{T40}} 2378-D2U
|| IBM || 2378D2U || ThinkPad T40 || IBM || 2378D2U || Not Available || IBM || Not Available || IBM || 1RETC2WW (3.03 ) || 04/07/2004
||
|| {{NOTE|Missing EC string, this bug is known to be fixed in latest BIOS}}
|-
| {{T40p}} 2373-G1G
|| IBM || 2373G1G || ThinkPad T40p || IBM || 2373G1G || Not Available || IBM || Not Available || IBM || 1RETDPWW (3.21 ) || 06/02/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T41}} 2373-W63
|| IBM || 2373W63 || ThinkPad T41 || IBM || 2373W63 || Not Available || IBM || Not Available || IBM || 1RETDPWW (3.21 ) || 06/02/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T41}} 2373-XNX
|| IBM || 2373XNX || ThinkPad T41 || IBM || 2373XNX || Not Available || IBM || Not Available || IBM || 1RETDOWW (3.20 ) || 02/27/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T41}} 2373-2FG
|| IBM || 23732FG || ThinkPad T41 || IBM || 23732FG || Not Available || IBM || Not Available || IBM || 1RET84WW (2.11 ) || 10/30/2003
||
|| {{NOTE|Missing EC string, this bug is known to be fixed in latest BIOS}}
|-
| {{T41}} 2374-312
|| IBM || 2374312 || ThinkPad T41 || IBM || 2374312 || Not Available || IBM || Not Available || IBM || 1RETDRWW (3.23 ) || 06/18/2007
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T41}} 2379-DJU
|| IBM || 2379DJU || ThinkPad T41 || IBM || 2379DJU || Not Available || IBM || Not Available || IBM || 1RETDPWW (3.21 ) || 06/02/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T41p}} 2373-GHG
|| IBM || 2373GHG || ThinkPad T41p || IBM || 2373GHG || Not Available || IBM || Not Available || IBM || 1RETDIWW (3.14 ) || 01/20/2005
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T41p}} 2373-GEG
|| IBM || 2373GEG || ThinkPad T41p || IBM || 2373GEG || Not Available || IBM || Not Available || IBM || 1RETDNWW (3.19 ) || 10/13/2005
|| <nowiki> Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T41p}} 2373-GJJ
|| IBM || 2373GJJ || ThinkPad T41p || IBM || 2373GJJ || Not Available || IBM || Not Available || IBM || 1RETDOWW (3.20 ) || 02/27/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T42}} 2373-FWG
|| IBM || 2373FWG || ThinkPad T42 || IBM || 2373FWG || Not Available || IBM || Not Available || IBM || 1RETDHWW (3.13 ) || 10/29/2004
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T42}} 2373-M1G
|| IBM || 2373M1G || ThinkPad T42 || IBM || 2373M1G || Not Available || IBM || Not Available || IBM || 1RETDPWW (3.21 ) || 06/02/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T42}} 2374-WEH
|| IBM || 2374WEH || ThinkPad T42 || IBM || 2374WEH || Not Available || IBM || Not Available || IBM || 1RETDPWW (3.21 ) || 06/02/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T42}} 2378-FVU
|| IBM || 2378FVU || ThinkPad T42 || IBM || 2378FVU || Not Available || IBM || Not Available || IBM || 1RETDPWW (3.21 ) || 06/02/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T42p}} 2373-KXU
|| IBM || 2373KXU || ThinkPad T42p || IBM || 2373KXU || Not Available || IBM || Not Available || IBM || 1RETDPWW (3.21 ) || 06/02/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T42p}} 2373-KUU
|| IBM || 2373KUU || ThinkPad T42p || IBM || 2373KUU || Not Available || IBM || Not Available || IBM || 1RETDMWW (3.18 ) || 09/15/2005
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T42p}} 2373-GYG
|| IBM || 2373GYG || ThinkPad T42p || IBM || 2373GYG || Not Available || IBM || Not Available || IBM || 1RETDOWW (3.20 ) || 02/27/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T42p}} 2374-CP5
|| IBM || 2374CP5 || ThinkPad T42p || IBM || 2374CP5 || Not Available || IBM || Not Available || IBM || 1RETDPWW (3.21 ) || 06/02/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T42p}} 2379-DYU
|| IBM || 2379DYU || ThinkPad T42p || IBM || 2379DYU || Not Available || IBM || Not Available || IBM || 1RETDPWW (3.21 ) || 06/02/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T42p}} 2372-Q2G
|| IBM || 2373Q2G || ThinkPad T42p || IBM || 2373Q2G || Not Available || IBM || Not Available || IBM || 1RETDPWW (3.21 ) || 06/02/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T43}} 1871-4AG
|| IBM || 18714AG || ThinkPad T43 || IBM || 18714AG || Not Available || IBM || Not Available || IBM || 70ET64WW (1.24 ) || 02/13/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[70HT27WW-1.04 ]-</nowiki>
||
|-
| {{T43}} 1871-F1G
|| IBM || 1871F1G || ThinkPad T43 || IBM || 1871F1G || Not Available || IBM || Not Available || IBM || 70ET61WW (1.21 ) || 11/01/2005
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[70HT26WW-1.03 ]-</nowiki>
||
|-
| {{T43}} 2686-DGU
|| IBM || 2686DGU || ThinkPad T43 || IBM || 2686DGU || Not Available || IBM || Not Available || IBM || 1YET62WW (1.27 ) || 05/18/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[1YHT29WW-1.06 ]-</nowiki>
||
|-
| {{T43}} 2669-WE5
|| IBM || 2669WE5 || ThinkPad T43 || IBM || 2669WE5 || Not Available || IBM || Not Available || IBM || 1YET56WW (1.21 ) || 07/06/2005
|| <nowiki>String 1: IBM ThinkPad Embedded Controller -[1YHT26WW-1.03 ]-</nowiki>
|| {{NOTE|User reports this is really a 2669-CEU with 1GB RAM + BlueTooth, and not a 2669-WE5 (unverified if this makes sense)}}
|-
| {{T43p}} 2668-G2G
|| IBM || 2668G2G || ThinkPad T43p || IBM || 2668G2G || Not Available || IBM || Not Available || IBM || 1YET47WW (1.08 ) || 06/09/2005
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[1YHT26WW-1.03 ]-</nowiki>
||
|-
| {{T43p}} 2687-D5U
|| IBM || 2687D5U || ThinkPad T43p || IBM || 2687D5U || Not Available || IBM || Not Available || IBM || 1YET59WW (1.24 ) || 11/07/2005
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1YHT26WW-1.03 ]-</nowiki>
||
|-
| {{T60}} 1951-24G
|| LENOVO || 195124G || ThinkPad T60 || LENOVO || 195124G || Not Available || LENOVO || Not Available || LENOVO || 79ET65WW (1.09a) || 07/27/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[79HT48WW-1.05b ]-</nowiki>
||
|-
| {{T60}} 1952-W5R
|| LENOVO || 1952W5R || ThinkPad T60 || LENOVO || 1952W5R || Not Available || LENOVO || Not Available || LENOVO || 79ET61WW (1.06 ) || 05/24/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[79HT45WW-1.04 ]-</nowiki>
||
|-
| {{T60}} 1952-W5R
|| LENOVO || 1952W5R || ThinkPad T60 || LENOVO || 1952W5R || Not Available || LENOVO || Not Available || LENOVO || 79ETD2WW (2.12 ) || 04/12/2007
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[79HT50WW-1.07 ]-</nowiki>
||
|-
| {{T60}} 2007-49G
|| LENOVO || 200749G || ThinkPad T60 || LENOVO || 200749G || Not Available || LENOVO || Not Available || LENOVO || 79ET62WW (1.07 ) || 06/12/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[79HT45WW-1.04 ]-</nowiki>
||
|-
| {{T60}} 2007-77G
|| LENOVO || 200777G || ThinkPad T60 || LENOVO || 200777G || Not Available || LENOVO || Not Available || LENOVO || 79ETD1WW (2.11 ) || 03/15/2007
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[79HT50WW-1.07 ]-</nowiki>
||
|-
| {{T60}} 1951-CA2
|| LENOVO || 1951CA2 || ThinkPad T60 || LENOVO || 1951CA2 || Not Available || LENOVO || Not Available || LENOVO || 79ETD9WW (2.19 ) || 09/19/2007
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[79HT50WW-1.07 ]-</nowiki>
||
|-
| {{T60}} 2007-BF3
|| LENOVO || 2007BF3 || ThinkPad T60 || LENOVO || 2007BF3 || Not Available || LENOVO || Not Available || LENOVO || 79ETD7WW (2.17 ) || 08/23/2007
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[79HT50WW-1.07 ]-</nowiki>
||
|-
| {{T60p}} 2007-83U
|| LENOVO || 200783U || ThinkPad T60p || LENOVO || 200783U || Not Available || LENOVO || Not Available || LENOVO || 79ET60WW (1.05a) || 04/18/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[79HT43WW-1.02 ]-</nowiki>
||
|-
| {{T60p}} 2007-93G
|| LENOVO || 200793G || ThinkPad T60p || LENOVO || 200793G || Not Available || LENOVO || Not Available || LENOVO || 79ET62WW (1.07 ) || 06/12/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[79HT45WW-1.04 ]-</nowiki>
||
|-
| {{T60p}} 2007-93U
|| LENOVO || 200793U || ThinkPad T60p || LENOVO || 200793U || Not Available || LENOVO || Not Available || LENOVO || 79ET66WW (1.10 ) || 08/02/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[79HT48WW-1.05b ]-</nowiki>
||
|-
| {{T60p}} 2007-93U
|| LENOVO || 200793U || ThinkPad T60p || LENOVO || 200793U || Not Available || LENOVO || Not Available || LENOVO || 79ET67WW (1.11 ) || 08/29/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[79HT48WW-1.05b ]-</nowiki>
||
|-
| {{T60p}} 2007-93U
|| LENOVO || 200793U || ThinkPad T60p || LENOVO || 200793U || Not Available || LENOVO || Not Available || LENOVO || 79ETC3WW (2.03 ) || 11/10/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[79HT50WW-1.07 ]-</nowiki>
||
|-
| {{T60p}} 2007-ZK4
|| LENOVO || 2007ZK4 || ThinkPad T60p || LENOVO || 2007ZK4 || Not Available || LENOVO || Not Available || LENOVO || 79ETD3WW (2.13 ) || 04/30/2007
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[79HT50WW-1.07 ]-</nowiki>
||
|-
| {{T60p}} 2613-ESU
|| LENOVO || 2613ESU || ThinkPad T60p || LENOVO || 2613ESU || Not Available || LENOVO || Not Available || LENOVO || 79ET67WW (1.11 ) || 08/29/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[79HT48WW-1.05b ]-</nowiki>
||
|-
| {{T60p}} 2623-DDU
|| LENOVO || 2623DDU || ThinkPad T60p || LENOVO || 2623DDU || Not Available || LENOVO || Not Available || LENOVO || 79ETC3WW (2.03 ) || 11/10/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[79HT50WW-1.07 ]-</nowiki>
||
|-
| {{T61}} 6457-W2C
|| LENOVO || 6457W2C || ThinkPad T61 || LENOVO || 6457W2C || Not Available || LENOVO || Not Available || LENOVO || 7LETB0WW (2.10 ) || 01/21/2008
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT24WW-1.08 ]-</nowiki>
||
|-
| {{T61}} 6465-CTO
|| LENOVO || 6465CTO || ThinkPad T61 || LENOVO || 6465CTO || Not Available || LENOVO || Not Available || LENOVO || 7LETB2WW (2.12 ) || 02/20/2008
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT24WW-1.08 ]-</nowiki>
||
|-
| {{T61}} 7662-XDU
|| LENOVO || 7662XDU || ThinkPad T61 || LENOVO || 7662XDU || 7662XDU|| LENOVO || Not Available || LENOVO || 7LET37WW (1.07 ) || 04/17/2007
|| <nowiki>Handle 0x0028, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[7KHT19WW-1.03 ]-</nowiki>
|| {{WARN|BIOS and EC firmware have different IDs}}
|-
| {{T61}} 7661-A56
|| LENOVO || 7661A56 || ThinkPad T61 || LENOVO || 7661A56 || Not Available || LENOVO || Not Available || LENOVO || 7LET39WW (1.09 ) || 05/14/2007
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT21WW-1.05 ]-</nowiki>
||
|-
| {{T61}} 8897-CTO
|| LENOVO || 8897CTO || ThinkPad T61 || LENOVO || 8897CTO || Not Available || LENOVO || Not Available || LENOVO || 7LET52WW (1.22 ) || 08/27/2007
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT22WW-1.06 ]-</nowiki>
||
|-
| {{T61}} 8897-CTO
|| LENOVO || 8897CTO || ThinkPad T61 || LENOVO || 8897CTO || Not Available || LENOVO || Not Available || LENOVO || 7LET56WW (1.26 ) || 10/18/2007
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT22WW-1.06 ]-</nowiki>
||
|-
| {{T61p}} 6459-A12
|| LENOVO || 6459A12 || ThinkPad T61p || LENOVO || 6459A12 || Not Available || LENOVO || Not Available || LENOVO || 7LET56WW (1.26 ) || 10/18/2007
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT22WW-1.06 ]-</nowiki>
||
|-
| {{T500}} 2055-45G
|| LENOVO || 205545G || ThinkPad T500 || LENOVO || 205545G || Not Available || LENOVO || Not Available || LENOVO || 6FET49WW (1.19 ) || 10/17/2008
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7VHT12WW-1.01 ]-</nowiki>
||
|-
! colspan=14 style="text-align:center;background:#efefef;" |

====X series====
|-
| {{X20}} 266231G
|| IBM || 266231G || Not Available || IBM || 266231G || Not Available || IBM || Not Available || IBM || IZET9DWW (2.25 ) || 04/17/2003
||
||
|-
|| 266232G || IBM || 266232G || Not Available || IBM || 266232G || Not Available || IBM || Not Available || IBM || IZET9AWW (2.22 ) || 09/11/2002
|| <nowiki></nowiki>
||
|-
| {{X23}} 2662EBG
|| IBM || 2662EBG || Not Available || IBM || 2662EBG || Not Available || IBM || Not Available || IBM || 1DET70WW (1.32 ) || 06/10/2003
|| <nowiki></nowiki>
||
|-
| {{X24}} 2662-MPU
|| IBM || 62MPUFX || Not Available || IBM || 62MPUFX || Not Available || IBM || Not Available || IBM || 1DET67WW (1.29 ) || 12/18/2002
||
||
|-
| {{X30}} 2672-42G
|| IBM || 267242G || Not Available || IBM || 267242G || Not Available || IBM || Not Available || IBM || 1KET48WW (1.09 ) || 06/16/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1KHT18WW-1.06 ]-</nowiki>
||
|-
| {{X30}} 2672-4HU
|| IBM || 26724HU || Not Available || IBM || 26724HU || Not Available || IBM || Not Available || IBM || 1KET48WW (1.09 ) || 06/16/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1KHT18WW-1.06 ]-</nowiki>
||
|-
| {{X30}} 2672-PG3
|| IBM || 2672PG3 || Not Available || IBM || 2672PG3 || Not Available || IBM || Not Available || IBM || 1KET48WW (1.09 ) || 06/16/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1KHT18WW-1.06 ]-</nowiki>
||
|-
| {{X31}} 2672-JXU
|| IBM || 2672JXU || ThinkPad X31 || IBM || 2672JXU || Not Available || IBM || Not Available || IBM || 1QET97WW (3.02 ) || 09/22/2005
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1QHT23WW-1.08 ]-</nowiki>
||
|-
| {{X31}} 2672-FG2
|| IBM || 2672FG2 || ThinkPad X31 || IBM || 2672FG2 || Not Available || IBM || Not Available || IBM || 1QET73WW (2.11 ) || 02/13/2004
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1QHT16WW-1.03 ]-</nowiki>
||
|-
| {{X31}} 2672-FG2
|| IBM || 2672FG2 || ThinkPad X31 || IBM || 2672FG2 || Not Available || IBM || Not Available || IBM || 1QET97WW (3.02 ) || 09/22/2005
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1QHT23WW-1.08 ]-</nowiki>
||
|-
| {{X32}} 2884-A3U
|| IBM || 2884A3U || ThinkPad X32 || IBM || 2884A3U || Not Available || IBM || Not Available || IBM || 1QET94WW (3.00d) || 01/23/2005
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1QHT22WW-1.07b ]-</nowiki>
||
|-
| {{X32}} 2673-M4U
|| IBM || 2673M4U || ThinkPad X32 || IBM || 2673M4U || Not Available || IBM || Not Available || IBM || 1QET97WW (3.02 ) || 09/22/2005
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1QHT23WW-1.08 ]-</nowiki>
||
|-
| {{X40}} 2386-H4G
|| IBM || 2386H4G || ThinkPad X40 || IBM || 2386H4G || Not Available || IBM || Not Available || IBM || 1UET92WW (1.42 ) || 09/16/2004
|| <nowiki>Handle 0x0024, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[1UHT82WW-1.32 ]-</nowiki>
||
|-
| {{X40}} 2371-Y29
|| IBM || 2371Y29 || ThinkPad X40 || IBM || 2371Y29 || Not Available || IBM || Not Available || IBM || 1UETD3WW (2.08 ) || 12/21/2006
|| <nowiki>Handle 0x0024, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1UHTA6WW-1.56 ]-</nowiki>
||
|-
| {{X41}} 2525-HU1
|| IBM || 2525HU1 || ThinkPad X41 || IBM || 2525HU1 || Not Available || IBM || Not Available || IBM || 74ET48WW (1.17a) || 06/07/2005
|| <nowiki>Handle 0x0025, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[74HT25WW-1.00 ]-</nowiki>
||
|-
| {{X41t}} 1869-CLG
|| IBM || 1869CLG || ThinkPad X41 Tablet || IBM || 1869CLG || Not Available || IBM || Not Available || IBM || 75ET56WW (2.02 ) || 03/14/2006
|| <nowiki>Handle 0x0025, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[75HT19WW-1.01 ]-</nowiki>
||
|-
| {{X60}} 1709-47U
|| LENOVO || 170947U || ThinkPad X60 || LENOVO || 170947U || Not Available || LENOVO || Not Available || LENOVO || 7BET44WW (1.04 ) || 03/13/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[7BHT29WW-1.02 ]-</nowiki>
||
|-
| {{X60}} 1709-GDJ
|| LENOVO || 1709GDJ || ThinkPad X60 || LENOVO || 1709GDJ || Not Available || LENOVO || Not Available || LENOVO || 7BETC2WW (2.03 ) || 10/16/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7BHT36WW-1.09 ]-</nowiki>
||
|-
| {{X60}} 1706-B69
|| LENOVO || 1706B69 || ThinkPad X60 || LENOVO || 1706B69 || Not Available || LENOVO || Not Available || LENOVO || 7BETC8WW (2.09 ) || 03/14/2007
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7BHT37WW-1.10 ]-</nowiki>
||
|-
| {{X60s}} 1702-55G
|| LENOVO || 170255G || ThinkPad X60s || LENOVO || 170255G || Not Available || LENOVO || Not Available || LENOVO || 7BET44WW (1.04 ) || 03/13/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[7BHT29WW-1.02 ]-</nowiki>
||
|-
| {{X60s}} 1702-5FG
|| LENOVO || 17025FG || ThinkPad X60s || LENOVO || 17025FG || Not Available || LENOVO || Not Available || LENOVO || 7BET49WW (1.09 ) || 07/27/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7BHT34WW-1.07 ]-</nowiki>
||
|-
| {{X60s}} 1704-56G
|| LENOVO || 170456G || ThinkPad X60s || LENOVO || 170456G || Not Available || LENOVO || Not Available || LENOVO || 7BET43WW (1.03 ) || 02/13/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[7BHT28WW-1.01 ]-</nowiki>
||
|-
| {{X60s}} 1704-5UG
|| LENOVO || 17045UG || ThinkPad X60s || LENOVO || 17045UG || Not Available || LENOVO || Not Available || LENOVO || 7BETD2WW (2.13 ) || 08/10/2007
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7BHT40WW-1.13 ]-</nowiki>
||
|-
| {{X60t}} 6365-CTO
|| LENOVO || 6365CTO || ThinkPad X60 Tablet || LENOVO || 6365CTO || Not Available || LENOVO || Not Available || LENOVO || 7JET25WW (1.10 ) || 08/17/2007
|| <nowiki>Handle 0x0023, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7JHT13WW-1.04 ]-</nowiki>
||
|-
| {{X60t}} 6363-J3G
|| LENOVO || 6363J3G || ThinkPad X60 Tablet || LENOVO || 6363J3G || Not Available || LENOVO || Not Available || LENOVO || 7JET28WW (1.13 ) || 03/31/2008
|| <nowiki>Handle 0x0023, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7JHT13WW-1.04 ]-</nowiki>
|| A mean bitch to set up, nothing really worked out of the box :(
|-
| {{X60t}} 6363A7G
|| LENOVO || 6363A7G || ThinkPad X60 Tablet || LENOVO || 6363A7G || Not Available || LENOVO || Not Available || LENOVO || 7JET19WW (1.04 ) || 12/14/2006
|| <nowiki>Handle 0x0023, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7JHT12WW-1.03 ]-</nowiki>
||
|-
| {{X61}} 7675-4KU
|| LENOVO || 76754KU || ThinkPad X61 || LENOVO || 76754KU || Not Available || LENOVO || Not Available || LENOVO || 7NET30WW (1.11 ) || 11/15/2007
|| <nowiki>Handle 0x001F, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7MHT24WW-1.02 ]-</nowiki>
||
|-
| {{X61}} 7675-7KU
|| LENOVO || 76757KU || ThinkPad X61 || LENOVO || 76757KU || Not Available || LENOVO || Not Available || LENOVO || 7NETB1WW (2.11 ) || 03/24/2008
|| <nowiki>Handle 0x001F, DMI type 11, 5 bytes IBM ThinkPad Embedded Controller -[7MHT25WW-1.03 ]-</nowiki>
||
|-
| {{X61t}} 7762-95G
|| LENOVO || 776295G || ThinkPad X61 Tablet || LENOVO || 776295G || Not Available || LENOVO || Not Available || LENOVO || 7SET22WW (1.08 ) || 11/15/2007
|| <nowiki>Handle 0x001F, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7RHT16WW-1.02 ]-</nowiki>
||
|-
| {{X61t}} 7764-CTO
|| LENOVO || 7764CTO || ThinkPad X61 Tablet || LENOVO || 7764CTO || Not Available || LENOVO || Not Available || LENOVO || 7SET18WW (1.04 ) || 07/03/2007
|| <nowiki>Handle 0x001F, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7RHT16WW-1.02 ]-</nowiki>
||
|-
| {{X200}} Tablet 7449-F9U
|| LENOVO || 7449F9U || ThinkPad X200 Tablet || LENOVO || 7449F9U || Not Available || LENOVO || Not Available || LENOVO || 7WET24WW (1.02 ) || 09/09/2008
|| <nowiki>Handle 0x001D, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7WHT14WW-1.01 ]-</nowiki>
||
|-
| {{X300}} 6478-14G
|| LENOVO || 647814G || ThinkPad X300 || LENOVO || 647814G || Not Available || LENOVO || Not Available || LENOVO || 7TET23WW (1.00d) || 01/17/2008
|| <nowiki>Handle 0x0022, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7THT15WW-1.00c ]-</nowiki>
||
|-
| {{X300}} 6478-18M
|| LENOVO || 647818M || ThinkPad X300 || LENOVO || 647818M || Not Available || LENOVO || Not Available || LENOVO || 7TET26WW (1.02a) || 02/27/2008
|| <nowiki>Handle 0x0022, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7THT15WW-1.00c ]-</nowiki>
||
|-
| {{X301}} 2777-CTO
|| LENOVO || 2777CTO || ThinkPad X301 || LENOVO || 2777CTO || Not Available || LENOVO || Not Available || LENOVO || 6EET19WW (1.00g) || 07/30/2008
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[6EHT07WW-1.00b ]-</nowiki>
||
|-
! colspan=14 style="text-align:center;background:#efefef;" |

====Z series====
|-
| {{Z60t}} 2511-FEU
|| IBM || 2511FEU || ThinkPad Z60t || IBM || 2511FEU || Not Available || IBM || Not Available || IBM || 77ET42WW (1.05 ) || 11/19/2005
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[77HT28WW-1.02 ]-</nowiki>
||
|-
| {{Z60t}} 2511-FFG
|| IBM || 2511FFG || ThinkPad Z60t || IBM || 2511FFG || Not Available || IBM || Not Available || IBM || 77ET64WW (1.24 ) || 02/27/2007
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[77HT57WW-1.17 ]-</nowiki>
||
|-
| {{Z60m}} 2529-ETG
|| IBM || 2529ETG || ThinkPad Z60m || IBM || 2529ETG || Not Available || IBM || Not Available || IBM || 77ET59WW (1.19 ) || 04/24/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[77HT54WW-1.14 ]-</nowiki>
||
|-
| {{Z60m}} 2529-ETG
|| IBM || 2529ETG || ThinkPad Z60m || IBM || 2529ETG || Not Available || IBM || Not Available || IBM || 77ET64WW (1.24 ) || 02/27/2007
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[77HT58WW-1.18 ]-</nowiki>
||
|-
| {{Z60m}} 2529-FBG
|| IBM || 2529FBG || ThinkPad Z60m || IBM || 2529FBG || Not Available || IBM || Not Available || IBM || 77ET62WW (1.22 ) || 11/21/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[77HT58WW-1.18 ]-</nowiki>
||
|-
| {{Z60m}} 2529-FKG
|| IBM || 2529FKG || ThinkPad Z60m || IBM || 2529FKG || Not Available || IBM || Not Available || IBM || 77ET42WW (1.05 ) || 11/19/2005
|| <nowiki>String 1: IBM ThinkPad Embedded Controller -[77HT28WW-1.02 ]-</nowiki>
||
|-
| {{Z61m}} 9453-A11
|| LENOVO || 9453A11 || ThinkPad Z61m || LENOVO || 9453A11 || Not Available || LENOVO || Not Available || LENOVO || 7FET48WW (1.08 ) || 05/26/2006
|| <nowiki>String 1: IBM ThinkPad Embedded Controller -[7FHT21WW-1.03 ]-</nowiki>
||
|-
| {{Z61m}} 9452-8QG
|| LENOVO || 94528QG || ThinkPad Z61m || LENOVO || 94528QG || Not Available || LENOVO || Not Available || LENOVO || 7FETA4WW (2.22 ) || 10/19/2007
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7FHT26WW-1.08 ]-</nowiki>
||
|-
| {{Z61m}} 9452-W5Q
|| LENOVO || 9452W5Q || ThinkPad Z61m || LENOVO || 9452W5Q || Not Available || LENOVO || Not Available || LENOVO || 7FETA6WW (2.24 ) || 03/13/2008
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7FHT26WW-1.08 ]-</nowiki>
|-
| {{Z61m}} 9543-A11
|| LENOVO || 9453A11 || ThinkPad Z61m || LENOVO || 9453A11 || Not Available || LENOVO || Not Available || LENOVO || 7FET53WW (1.13 ) || 07/27/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7FHT23WW-1.05 ]-</nowiki>
||
|-
| {{Z61m}} 9543-A11
|| LENOVO || 9453A11 || ThinkPad Z61m || LENOVO || 9453A11 || Not Available || LENOVO || Not Available || LENOVO || 7FET93WW (2.11 ) || 11/10/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7FHT26WW-1.08 ]-</nowiki>
||
|-
| {{Z61m}} 9453-A11
|| LENOVO || 9453A11 || ThinkPad Z61m || LENOVO || 9453A11 || Not Available || LENOVO || Not Available || LENOVO || 7FET53WW (1.13 ) || 07/27/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7FHT23WW-1.05 ]-</nowiki>
||
|-
| {{Z61p}} 9453-A12
|| LENOVO || 9453A12 || ThinkPad Z61p || LENOVO || 9453A12 || Not Available || LENOVO || Not Available || LENOVO || 7FET45WW (1.05 ) || 04/20/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[7FHT19WW-1.01 ]-</nowiki>
||
|-
| {{Z61p}} 9450-3AU
|| LENOVO || 94503AU || ThinkPad Z61p || LENOVO || 94503AU || Not Available || LENOVO || Not Available || LENOVO || 7FET53WW (1.13 ) || 07/27/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7FHT23WW-1.05 ]-</nowiki>
||
|-
| {{Z61t}} 9440-2CU
|| LENOVO || 94402CU || ThinkPad Z61t || LENOVO || 94402CU || Not Available || LENOVO || Not Available || LENOVO || 7FET50WW (1.10 ) || 06/20/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7FHT22WW-1.04 ]-</nowiki>
||
|-
| {{Z61t}} 9443-4GG
|| LENOVO || 94434GG || ThinkPad Z61t || LENOVO || 94434GG || Not Available || LENOVO || Not Available || LENOVO || 7FET96WW (2.14 ) || 12/25/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7FHT26WW-1.08 ]-</nowiki>
||
|-
| {{Z61t}} 9440-CTO
|| LENOVO || 9440CTO || ThinkPad Z61t || LENOVO || 9440CTO || Not Available || LENOVO || Not Available || LENOVO || 7FET99WW (2.17 ) || 04/17/2007
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7FHT26WW-1.08 ]-</nowiki>
||
|-
| {{Z61t}} 9440-CTO
|| LENOVO || 9440CTO || ThinkPad Z61t || LENOVO || 9440CTO || Not Available || LENOVO || Not Available || LENOVO || 7FETA0WW (2.18 ) || 05/17/2007
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7FHT26WW-1.08 ]-</nowiki>
||
|-
| {{Z61t}} 9440-CTO
|| LENOVO || 9440CTO || ThinkPad Z61t || LENOVO || 9440CTO || Not Available || LENOVO || Not Available || LENOVO || 7FETA7WW (2.25 ) || 06/03/2008
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7FHT26WW-1.08 ]-</nowiki>
||
|-
! colspan=14 style="text-align:center;background:#efefef;" |

====Lenovo 3000 series====
|-
| [[:Category:Lenovo 3000| Lenovo 3000]] N200 TY2BAFR
|| LENOVO || 0769BAG || 3000 N200 || LENOVO || IEL10 || REFERENCE || No Enclosure || N/A || LENOVO || 68ET24WW || 08/15/2007
|| <nowiki></nowiki>
|| {{WARN|Non-ThinkPad EC firmware and BIOS}}
|-
|}
</div>

==Adding entries==

Click the "Edit" link on the appropriate series above and add an entry of the following form:
:<tt>| </tt>description of your model
:data line 1
:data line 2
:<tt>||</tt>
:<tt>|-</tt>

where the two data lines are generated by the following <tt>bash</tt> command:

<pre>
for X in system-{manufacturer,product-name,version} \
baseboard-{manufacturer,product-name,version} \
chassis-{manufacturer,version} bios-{vendor,version,release-date}; do \
echo -n "|| `sudo /usr/sbin/dmidecode -s $X` "; done; \
sudo /usr/sbin/dmidecode | perl -0777 -ne \
'm/\n(.*).\n.*\n(.*Embedded Cont.*)\n/i; print "\n|| <nowiki><</nowiki>nowiki>$1$2</nowiki>\n"'
</pre>

While at it, you may also want to test [[tp_smapi]] and update its [[tp_smapi#Model-specific_status|model-specific status table]].

==Software using ThinkPad DMI IDs==
* [[HDAPS]] driver whitelist
* [[tp_smapi]] driver whitelist
* [[ibm-acpi]]/thinkpad-acpi driver quirk list

How to save memory

2008-12-11T19:30:15Z

Low: /* Adjusting filesystems */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |This page is meant as a collection of information on how to save memory to make Linux work reasonable on older systems with limited amount of RAM.

Most distributions nowadays don't take much care about it anymore, so there are a lot of things you can do to save memory. To get a smoothly working Linux environment on a low memory machine you will need to consciously choose a lot of aspects of your system, most importantly the graphical environment, desktop environment and applications. This page provides detailed information about these various optimization possibilities.
|}

==Alternative graphical environments==
{{Todo|...}}

==Streamlining the desktop environment==
The common desktop environments GNOME and KDE are focused more on features, integration, and beauty rather than on saving resources. Understandable, but running Linux on an older ThinkPad with limited RAM requires a focus on limiting resource usage. The good thing about Linux is that a lot of things stay adjustable and customizable. So lets see what we can do about desktops.

One of the most important things is to decide for one graphical widget library and stick with that when you are choosing your desktop environment and applications. Having several toolkits in use means more libraries being loaded and hence more memory being used by those. Possibilities are:
* [http://www.fltk.org/ FLTK]
* [http://www.fox-toolkit.org/ FOX toolkit]
* [http://www.gnustep.org GNUstep toolkit]
* [http://www.gtk.org/ GTK] (not recommended, use GTK 2 if possible)
* [http://www.gtk.org/ GTK 2]
* [http://www.lesstif.org/ Lesstif] / [http://www.openmotif.org/ OpenMotif]
* [http://www.trolltech.com/products/qt/index.html QT]
* [http://www.windowmaker.org/development-wings.html WINGs] (kind of a lightweight GNUstep toolkit, provided by the WindowMaker developers)
* [http://www.x.org/ X Toolkit]

Of those, at current state, there are enough applications for the X Toolkit, GTK, GTK 2 and QT to provide you with a solution for every task you should want.

===GNOME===
It's like with humans, the worst feature is in most cases also the best one. For GNOME it is probably the many little parts it consists of. Makes it hard to install, but enables one to customize the installation. So, the first thing you should do to streamline GNOME is not to launch it. Sound stupid? Well, lets have a look.

GNOME is basically a set of libraries built around the GTK+ libs and extending its functionality. Add some nice little applications, a session manager, a panel, beautiful icons, and some other stuff and you have GNOME as you know it. Reversing those additions is what you can do to use GNOME applications on a machine that this desktop environment would normally take your nerves on.

The GNOME panel, the session manager, the desktop manager and the window manager are all parts of GNOME that eat a lot of memory for something that others can do in a maybe little less beautiful but much more resource saving way.
So first off configure your login manager not to launch gnome-session at login. If you are using GDM this is quite straight forward, you just need to add a different session script, launching your favorite window manager. See the list below and pick one, lets say i.e. WindowMaker. WindowMaker uses a desktop menu, a dock and a notification area to provide you with an organized way of launching applications and iconfying running ones. So we don't need a panel anymore. Also, think if you really need icons on your desktop. If you do, think about using something like ROX filer instead of nautilus for that. In any case, tell nautilus not to manage the desktop by default by unchecking the according setting within gconf-editor. To keep GNOME applications happy we would need to have gconf and gnome-settings-manager running at every session start. One way to do this is to either include them in your new session script. They both need to be running to make GNOME applications realize their settings properly.

===KDE===
{{Todo|...}}

===Alternative Desktop Environments===
First of all, it is important to notice that GNOME and KDE are not the only Desktop Environments around.
Other complete (featuring most of: window management, session management, desktop management, file management and panel) desktop environments are:
* [http://xfce.org/ XFCE] <tt>uses GTK 2</tt>
* [http://rox.sourceforge.net ROX Desktop]
* [http://ede.sourceforge.net Equinox Desktop Environment] <tt>uses eFLTK, a modified version of FLTK</tt>
* [http://www.nongnu.org/antiright/ AntiRight Desktop Environment] <tt>uses LessTif / OpenMotif</tt>
* [http://foxdesktop.sourceforge.net/ FOX Desktop Environment] <tt>uses FOX Toolkit</tt>
* [http://www.gnustep.org/ GNUstep] <tt>provides it's own toolkit</tt>

But also, some Window Managers exceed the task of managing windows towards providing a functional workbench. See below for a list.

===Building your own Desktop===

====Window Manager====
If you want to build your own customized desktop, a good start is choosing the window manager of your liking. A list of window managers is at [http://xwinman.org].

Here's a list of some of them:
*including basic Desktop Environment functionality
**the [[Wikipedia:NextStep|NextStep]] alike ones
***[http://www.windowmaker.org/ WindowMaker] <tt>(probably the most widespread NextStep like WM)</tt>
***[http://www.afterstep.org/ AfterStep] <tt>(another one of those)</tt>
**the Blackbox-like ones
***[http://blackboxwm.sourceforge.net/ BlackBox]
***[http://fluxbox.sourceforge.net/ FluxBox] <tt>(tabbed windows, lighweight)</tt>
***[http://www.icculus.org/openbox/ OpenBox] <tt>(written from scratch to be fully ICCCM and EWMH compliant, fast and light-weight)</tt>
**others
***[http://www.icewm.org/ IceWM] <tt>(lightweight, widespread)</tt>
***[http://enlightenment.sourceforge.net/ Enlightenment] <tt>(lots of features and eye candy)</tt>
***[http://www.pekwm.org PekWM] <tt>(kind of a one man show, but feature rich and extremely customizable)</tt>
*pure WindowManagers
**[http://golem.sourceforge.net/ Golem]
**[http://home.earthlink.net/~lab1701/larswm/ LarsWM] <tt>(unique tiling Window Manager)</tt>
**[http://www.nongnu.org/ratpoison/ ratpoison] <tt>(modeled after gnu screen)</tt>
**[http://fvwm.org/ fvwm] <tt>(small but powerful)</tt>
**[http://www.jfc.org.uk/software/lwm.html lwm] <tt>(very small, and fast)</tt>
**[http://www.all-day-breakfast.com/wm2/ wm2] <tt>really small Window Manager</tt>
**[http://www.all-day-breakfast.com/wmx/ wmx] <tt>slightly more featureful version of wm2</tt>
**[http://wmii.suckless.org wmii] <tt>keyboard driven approach, very small, dynamic window managing</tt>
**[http://dwm.suckless.org dwm] <tt>keyboard-only driven approach, yet smaller than wmii, dynamic window managing</tt>

====Taskbar/Panel====
Another thing that especially users coming to Linux from the Windows world would probably like is a Panel or Taskbar.

Here's a collection of independant low resource panels:
*[http://www.chatjunkies.org/fspanel/ F***ing Small Panel] <tt>(doesn't use any toolkit)</tt>
*[http://freshmeat.net/projects/hpanel/ HPanel] <tt>(doesn't use any toolkit)</tt>
*[http://fbpanel.sourceforge.net/ fbpanel] <tt>(depends on GTK 2)</tt>
*[http://jodrell.net/projects/perlpanel Perl Panel] <tt>(depends on GTK 2, gnomevfs, perl)</tt>
*[http://www.gkrellm.net/ GKrellM] <tt>(depends on GTK 2, flexible plugin based skinable vertical panel)</tt>

Furthermore most of the windowmanagers allow you to have something like a panel/taskbar configured, and system tray applications like [http://stalonetray.sourceforge.net/ stalonetray] supply support for persistent applications (i.e. those that on quit do not quit but minimize to a tray icon) like Skype.

====Desktop Pinboard====
Then, the next thing you might be looking for is how to get icons onto your desktop. Usually this is done by the file manager who displays the content of a special directory as icons on the desktop. See the File Manager section to follow this approach.

However, you might decide for a really lightwight file manager which doesn't offer this feature. In that case all hope is not lost, for there are also special programs specialized in desktop icon management. Such are:
* [http://idesk.sourceforge.net/ iDesk] <tt>(recent versions need imlib2 only)</tt>

====File Manager====
File Managers are the fourth really important compontent of a desktop environment. There are plenty out their ranging from resource hugs to really lightweight and slim ones.

File Managers come with three distinct general user interface approaches: the two pane gui, the spacial and the browser gui. The browser gui is the one the Windows Explorer starting from Windows 2000 uses as well as earlier versions of Nautilus. The spacial view is the one known from Windows 95 and more recent versions of Nautilus. The two pane view is know to many from Norten Commander, Directory Opus or your favorite FTP client.

The following list provides an overview.
*FLTK
** [http://www.oksid.ch/flfm/ Fast Light File Manager] <tt>(spacial gui)</tt>
* FOX toolkit
** [http://roland65.free.fr/xfe/ X File Explorer] <tt>(browser and two pane gui)</tt>
*GTK
** [http://www.kaisersite.de/dfm/ Desktop File Manager] <tt>(spacial gui, incl. desktop icon management)</tt>
** [http://www.uwyn.com/projects/fm/ FM] <tt>(spacial, MAC OS 9 like gui)</tt>
** [http://radekc.regnet.cz/ Seksi Commander] <tt>(two pane gui)</tt>
*GTK 2
** [http://rox.sourceforge.net/ ROX Filer] <tt>(highly productive spacial gui, incl. panel and desktop icon management)</tt>
** [http://blog.perldude.de/projects/filer/ Filer] <tt>(browser and two pane gui, requires Perl)</tt>
** [http://xffm.sourceforge.net/ XFFM] <tt>(browser and spacial gui, requires some XFCE libs)</tt>
** [http://logicaldesktop.sourceforge.net/ Logical Desktop] <tt>(browser gui, actually a very special approach)</tt>
** [http://tuxcmd.sourceforge.net/ Tux Commander] <tt>(two pane gui)</tt>
** [http://www.nongnu.org/gcmd/index.html Gnome Commander] <tt>(two pane gui)</tt>
** [http://emelfm2.net/emelFM2/ emelFM2] <tt>(two pane gui with full customizable menu and toolbar, the best for power users)</tt>
** [http://thunar.xfce.org/index.xhtml Thunar] <tt>(requires some XFCE libs)</tt>
** [http://pcmanfm.sourceforge.net/ PCMan File Manager] <tt>(An extremly fast and lightweight file manager which features tabbed browsing and user-friendly interface. Requires GTK+ version 2.8.x)</tt>
* OpenMotif
** [http://www.musikwissenschaft.uni-mainz.de/~ag/xplore/xplore.php Xplore] <tt>(browser gui with productive 4 pane concept)</tt>
* QT 2
** [http://www.hi-net.cz/blaza/bfcommander/en/index.html BF-Commander] <tt>(two pane gui)</tt>
*Qt3
** [http://www.beesoft.org/download_bsc.html Beesoft Commander] <tt> (fast & easy two panel file manager, like Norton Commander)</tt>
* Tcl/Tk
** [http://users.tkk.fi/~mkivinie/X-Files/ X-Files] <tt>(two pane gui)</tt>
*X Toolkit
** [http://www.musikwissenschaft.uni-mainz.de/~ag/xfm/ X File Manager] <tt>(spacial gui)</tt>
** [http://www.boomerangsworld.de/worker/ Worker] <tt>(two pane gui, highly productive and configurable)</tt>
** [http://xnc.dubna.su/ X Northern Captain] <tt>(interesting flexible two pane gui)</tt>
*3D Filemanagers
** [http://www.determinate.net/webdata/seg/tdfsb.html TDFSB] <tt>(3D gui, the most impressing 3D file browser so far)</tt>
** [http://www.forchheimer.se/bfm/ Brutal File Manager] <tt>(3D gui more for fun than productivity)</tt>
** [http://turma.sourceforge.net/software/3dfile/ 3DFile] <tt>(3D gui)</tt>
** [http://orbis.sourceforge.net/ Orbis] <tt>(3D gui)</tt>

==Choosing applications==
===Web Browser===
This is highly dependent on the way you use your browser, it's often worth it to try out all and just track general
memory usage. Remember that <tt>top</tt> and <tt>ps</tt> don't report correct memory usage, track totals only.

====Firefox====
Firefox is graphical web browser. One can install features like AdBlock and FlashClicktoplay which will decrease memory and
processor usage by hiding Flash and Java -adverts.

====Opera====
Opera is graphical web browser. You can easily enable/disable plug-ins and java (press F12) and decrease memory usage.
Opera uses QT as toolkit, so you may shave off some Mbytes off memory usage by using dynamically linked version if you use KDE.

====Konqueror====
Konqueror is graphical web browser. It's integrated with KDE and has several advanced features (esp. ca. KDE 3.5).
You may save some megabytes by using it instead of other browsers when using KDE.
It's not necessarily heavy even when used without running KDE.

====Dillo====
Dillo is minimalistic and very small graphical web browser.

====Elinks/Lynx====
elinks/lynx are both text mode web browsers. <tt>elinks</tt> handles tables and formatting much nicer than <tt>lynx</tt>.
Both go very easy on memory footprint.

{{Todo|...}}

==Disabling unneeded system deamons==
Another thing you can do to improve performance is to get rid of unneaded system daemons launched from your init scripts. Disable them by using the according configuration interface of your distro or by deleting links in the according runlevel directories (usually in <code>/etc/rc.d/</code>).

Daemons you usually don't need:
* httpd <tt>(Apache web server)</tt>
* mysqld <tt>(MySQL database server)</tt>
* smbd <tt>(SMB windows filesharing server)</tt>
* pppd <tt>(PPP server for connections through modems and serial lines)</tt>

==Adjusting filesystems==
You can also try to optimize memory usage by making sure that you have as little as possible of your filesystem residing in RAM. To do this make sure that the following mount points are set to reside on your harddisk in {{path|/etc/fstab}}. {{Todo|how?}}
* /dev (not possible if you use udev)
* /tmp

Also make sure that you mount filesystems with extensive usage with noatime parameter (mount -o remount,ro /...), which disabled access time writes every time you access some file. Note that many incremental backups needs atime to work, such backups will then behave like full backup everytime. This depends on backup systems.

==Other tips==
===Disk space===
When using Debian/Ubuntu/other derivative, use <tt>aptitude</tt> as package manager, and use it as soon as possible. Use it and only it to install and remove packages.

One of its most useful features is that it tracks packages you install and marks packages installed via dependency as such, so when you remove a package that is no longer used, or package updates and doesn't use a library anymore, that dependency will get uninstalled.

You can mark packages installed as automatically installed by hitting 'M' (uppercase m), it will be marked for deinstallation if it's not longer required.

You could also install <tt>localepurge</tt>, which will remove all unneeded locales and localized manpages for packages you install.

===System clock===
<tt>ntpd</tt> can occupy around 4MB of memory, which is a substantial proportion of many older systems' total. [http://chrony.sunsite.dk/ <tt>chrony</tt>] is a pair of programs that replace the standard <tt>ntp</tt> and require much less memory.

How to save memory

2008-12-11T19:26:44Z

Low: /* Taskbar/Panel */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |This page is meant as a collection of information on how to save memory to make Linux work reasonable on older systems with limited amount of RAM.

Most distributions nowadays don't take much care about it anymore, so there are a lot of things you can do to save memory. To get a smoothly working Linux environment on a low memory machine you will need to consciously choose a lot of aspects of your system, most importantly the graphical environment, desktop environment and applications. This page provides detailed information about these various optimization possibilities.
|}

==Alternative graphical environments==
{{Todo|...}}

==Streamlining the desktop environment==
The common desktop environments GNOME and KDE are focused more on features, integration, and beauty rather than on saving resources. Understandable, but running Linux on an older ThinkPad with limited RAM requires a focus on limiting resource usage. The good thing about Linux is that a lot of things stay adjustable and customizable. So lets see what we can do about desktops.

One of the most important things is to decide for one graphical widget library and stick with that when you are choosing your desktop environment and applications. Having several toolkits in use means more libraries being loaded and hence more memory being used by those. Possibilities are:
* [http://www.fltk.org/ FLTK]
* [http://www.fox-toolkit.org/ FOX toolkit]
* [http://www.gnustep.org GNUstep toolkit]
* [http://www.gtk.org/ GTK] (not recommended, use GTK 2 if possible)
* [http://www.gtk.org/ GTK 2]
* [http://www.lesstif.org/ Lesstif] / [http://www.openmotif.org/ OpenMotif]
* [http://www.trolltech.com/products/qt/index.html QT]
* [http://www.windowmaker.org/development-wings.html WINGs] (kind of a lightweight GNUstep toolkit, provided by the WindowMaker developers)
* [http://www.x.org/ X Toolkit]

Of those, at current state, there are enough applications for the X Toolkit, GTK, GTK 2 and QT to provide you with a solution for every task you should want.

===GNOME===
It's like with humans, the worst feature is in most cases also the best one. For GNOME it is probably the many little parts it consists of. Makes it hard to install, but enables one to customize the installation. So, the first thing you should do to streamline GNOME is not to launch it. Sound stupid? Well, lets have a look.

GNOME is basically a set of libraries built around the GTK+ libs and extending its functionality. Add some nice little applications, a session manager, a panel, beautiful icons, and some other stuff and you have GNOME as you know it. Reversing those additions is what you can do to use GNOME applications on a machine that this desktop environment would normally take your nerves on.

The GNOME panel, the session manager, the desktop manager and the window manager are all parts of GNOME that eat a lot of memory for something that others can do in a maybe little less beautiful but much more resource saving way.
So first off configure your login manager not to launch gnome-session at login. If you are using GDM this is quite straight forward, you just need to add a different session script, launching your favorite window manager. See the list below and pick one, lets say i.e. WindowMaker. WindowMaker uses a desktop menu, a dock and a notification area to provide you with an organized way of launching applications and iconfying running ones. So we don't need a panel anymore. Also, think if you really need icons on your desktop. If you do, think about using something like ROX filer instead of nautilus for that. In any case, tell nautilus not to manage the desktop by default by unchecking the according setting within gconf-editor. To keep GNOME applications happy we would need to have gconf and gnome-settings-manager running at every session start. One way to do this is to either include them in your new session script. They both need to be running to make GNOME applications realize their settings properly.

===KDE===
{{Todo|...}}

===Alternative Desktop Environments===
First of all, it is important to notice that GNOME and KDE are not the only Desktop Environments around.
Other complete (featuring most of: window management, session management, desktop management, file management and panel) desktop environments are:
* [http://xfce.org/ XFCE] <tt>uses GTK 2</tt>
* [http://rox.sourceforge.net ROX Desktop]
* [http://ede.sourceforge.net Equinox Desktop Environment] <tt>uses eFLTK, a modified version of FLTK</tt>
* [http://www.nongnu.org/antiright/ AntiRight Desktop Environment] <tt>uses LessTif / OpenMotif</tt>
* [http://foxdesktop.sourceforge.net/ FOX Desktop Environment] <tt>uses FOX Toolkit</tt>
* [http://www.gnustep.org/ GNUstep] <tt>provides it's own toolkit</tt>

But also, some Window Managers exceed the task of managing windows towards providing a functional workbench. See below for a list.

===Building your own Desktop===

====Window Manager====
If you want to build your own customized desktop, a good start is choosing the window manager of your liking. A list of window managers is at [http://xwinman.org].

Here's a list of some of them:
*including basic Desktop Environment functionality
**the [[Wikipedia:NextStep|NextStep]] alike ones
***[http://www.windowmaker.org/ WindowMaker] <tt>(probably the most widespread NextStep like WM)</tt>
***[http://www.afterstep.org/ AfterStep] <tt>(another one of those)</tt>
**the Blackbox-like ones
***[http://blackboxwm.sourceforge.net/ BlackBox]
***[http://fluxbox.sourceforge.net/ FluxBox] <tt>(tabbed windows, lighweight)</tt>
***[http://www.icculus.org/openbox/ OpenBox] <tt>(written from scratch to be fully ICCCM and EWMH compliant, fast and light-weight)</tt>
**others
***[http://www.icewm.org/ IceWM] <tt>(lightweight, widespread)</tt>
***[http://enlightenment.sourceforge.net/ Enlightenment] <tt>(lots of features and eye candy)</tt>
***[http://www.pekwm.org PekWM] <tt>(kind of a one man show, but feature rich and extremely customizable)</tt>
*pure WindowManagers
**[http://golem.sourceforge.net/ Golem]
**[http://home.earthlink.net/~lab1701/larswm/ LarsWM] <tt>(unique tiling Window Manager)</tt>
**[http://www.nongnu.org/ratpoison/ ratpoison] <tt>(modeled after gnu screen)</tt>
**[http://fvwm.org/ fvwm] <tt>(small but powerful)</tt>
**[http://www.jfc.org.uk/software/lwm.html lwm] <tt>(very small, and fast)</tt>
**[http://www.all-day-breakfast.com/wm2/ wm2] <tt>really small Window Manager</tt>
**[http://www.all-day-breakfast.com/wmx/ wmx] <tt>slightly more featureful version of wm2</tt>
**[http://wmii.suckless.org wmii] <tt>keyboard driven approach, very small, dynamic window managing</tt>
**[http://dwm.suckless.org dwm] <tt>keyboard-only driven approach, yet smaller than wmii, dynamic window managing</tt>

====Taskbar/Panel====
Another thing that especially users coming to Linux from the Windows world would probably like is a Panel or Taskbar.

Here's a collection of independant low resource panels:
*[http://www.chatjunkies.org/fspanel/ F***ing Small Panel] <tt>(doesn't use any toolkit)</tt>
*[http://freshmeat.net/projects/hpanel/ HPanel] <tt>(doesn't use any toolkit)</tt>
*[http://fbpanel.sourceforge.net/ fbpanel] <tt>(depends on GTK 2)</tt>
*[http://jodrell.net/projects/perlpanel Perl Panel] <tt>(depends on GTK 2, gnomevfs, perl)</tt>
*[http://www.gkrellm.net/ GKrellM] <tt>(depends on GTK 2, flexible plugin based skinable vertical panel)</tt>

Furthermore most of the windowmanagers allow you to have something like a panel/taskbar configured, and system tray applications like [http://stalonetray.sourceforge.net/ stalonetray] supply support for persistent applications (i.e. those that on quit do not quit but minimize to a tray icon) like Skype.

====Desktop Pinboard====
Then, the next thing you might be looking for is how to get icons onto your desktop. Usually this is done by the file manager who displays the content of a special directory as icons on the desktop. See the File Manager section to follow this approach.

However, you might decide for a really lightwight file manager which doesn't offer this feature. In that case all hope is not lost, for there are also special programs specialized in desktop icon management. Such are:
* [http://idesk.sourceforge.net/ iDesk] <tt>(recent versions need imlib2 only)</tt>

====File Manager====
File Managers are the fourth really important compontent of a desktop environment. There are plenty out their ranging from resource hugs to really lightweight and slim ones.

File Managers come with three distinct general user interface approaches: the two pane gui, the spacial and the browser gui. The browser gui is the one the Windows Explorer starting from Windows 2000 uses as well as earlier versions of Nautilus. The spacial view is the one known from Windows 95 and more recent versions of Nautilus. The two pane view is know to many from Norten Commander, Directory Opus or your favorite FTP client.

The following list provides an overview.
*FLTK
** [http://www.oksid.ch/flfm/ Fast Light File Manager] <tt>(spacial gui)</tt>
* FOX toolkit
** [http://roland65.free.fr/xfe/ X File Explorer] <tt>(browser and two pane gui)</tt>
*GTK
** [http://www.kaisersite.de/dfm/ Desktop File Manager] <tt>(spacial gui, incl. desktop icon management)</tt>
** [http://www.uwyn.com/projects/fm/ FM] <tt>(spacial, MAC OS 9 like gui)</tt>
** [http://radekc.regnet.cz/ Seksi Commander] <tt>(two pane gui)</tt>
*GTK 2
** [http://rox.sourceforge.net/ ROX Filer] <tt>(highly productive spacial gui, incl. panel and desktop icon management)</tt>
** [http://blog.perldude.de/projects/filer/ Filer] <tt>(browser and two pane gui, requires Perl)</tt>
** [http://xffm.sourceforge.net/ XFFM] <tt>(browser and spacial gui, requires some XFCE libs)</tt>
** [http://logicaldesktop.sourceforge.net/ Logical Desktop] <tt>(browser gui, actually a very special approach)</tt>
** [http://tuxcmd.sourceforge.net/ Tux Commander] <tt>(two pane gui)</tt>
** [http://www.nongnu.org/gcmd/index.html Gnome Commander] <tt>(two pane gui)</tt>
** [http://emelfm2.net/emelFM2/ emelFM2] <tt>(two pane gui with full customizable menu and toolbar, the best for power users)</tt>
** [http://thunar.xfce.org/index.xhtml Thunar] <tt>(requires some XFCE libs)</tt>
** [http://pcmanfm.sourceforge.net/ PCMan File Manager] <tt>(An extremly fast and lightweight file manager which features tabbed browsing and user-friendly interface. Requires GTK+ version 2.8.x)</tt>
* OpenMotif
** [http://www.musikwissenschaft.uni-mainz.de/~ag/xplore/xplore.php Xplore] <tt>(browser gui with productive 4 pane concept)</tt>
* QT 2
** [http://www.hi-net.cz/blaza/bfcommander/en/index.html BF-Commander] <tt>(two pane gui)</tt>
*Qt3
** [http://www.beesoft.org/download_bsc.html Beesoft Commander] <tt> (fast & easy two panel file manager, like Norton Commander)</tt>
* Tcl/Tk
** [http://users.tkk.fi/~mkivinie/X-Files/ X-Files] <tt>(two pane gui)</tt>
*X Toolkit
** [http://www.musikwissenschaft.uni-mainz.de/~ag/xfm/ X File Manager] <tt>(spacial gui)</tt>
** [http://www.boomerangsworld.de/worker/ Worker] <tt>(two pane gui, highly productive and configurable)</tt>
** [http://xnc.dubna.su/ X Northern Captain] <tt>(interesting flexible two pane gui)</tt>
*3D Filemanagers
** [http://www.determinate.net/webdata/seg/tdfsb.html TDFSB] <tt>(3D gui, the most impressing 3D file browser so far)</tt>
** [http://www.forchheimer.se/bfm/ Brutal File Manager] <tt>(3D gui more for fun than productivity)</tt>
** [http://turma.sourceforge.net/software/3dfile/ 3DFile] <tt>(3D gui)</tt>
** [http://orbis.sourceforge.net/ Orbis] <tt>(3D gui)</tt>

==Choosing applications==
===Web Browser===
This is highly dependent on the way you use your browser, it's often worth it to try out all and just track general
memory usage. Remember that <tt>top</tt> and <tt>ps</tt> don't report correct memory usage, track totals only.

====Firefox====
Firefox is graphical web browser. One can install features like AdBlock and FlashClicktoplay which will decrease memory and
processor usage by hiding Flash and Java -adverts.

====Opera====
Opera is graphical web browser. You can easily enable/disable plug-ins and java (press F12) and decrease memory usage.
Opera uses QT as toolkit, so you may shave off some Mbytes off memory usage by using dynamically linked version if you use KDE.

====Konqueror====
Konqueror is graphical web browser. It's integrated with KDE and has several advanced features (esp. ca. KDE 3.5).
You may save some megabytes by using it instead of other browsers when using KDE.
It's not necessarily heavy even when used without running KDE.

====Dillo====
Dillo is minimalistic and very small graphical web browser.

====Elinks/Lynx====
elinks/lynx are both text mode web browsers. <tt>elinks</tt> handles tables and formatting much nicer than <tt>lynx</tt>.
Both go very easy on memory footprint.

{{Todo|...}}

==Disabling unneeded system deamons==
Another thing you can do to improve performance is to get rid of unneaded system daemons launched from your init scripts. Disable them by using the according configuration interface of your distro or by deleting links in the according runlevel directories (usually in <code>/etc/rc.d/</code>).

Daemons you usually don't need:
* httpd <tt>(Apache web server)</tt>
* mysqld <tt>(MySQL database server)</tt>
* smbd <tt>(SMB windows filesharing server)</tt>
* pppd <tt>(PPP server for connections through modems and serial lines)</tt>

==Adjusting filesystems==
You can also try to optimize memory usage by making sure that you have as little as possible of your filesystem residing in RAM. To do this make sure that the following mount points are set to reside on your harddisk in {{path|/etc/fstab}}.
* /dev (not possible if you use udev)
* /tmp

Also make sure that you mount filesystems with extensive usage with noatime parameter (mount -o remount,ro /...), which disabled access time writes every time you access some file. Note that many incremental backups needs atime to work, such backups will then behave like full backup everytime. This depends on backup systems.

==Other tips==
===Disk space===
When using Debian/Ubuntu/other derivative, use <tt>aptitude</tt> as package manager, and use it as soon as possible. Use it and only it to install and remove packages.

One of its most useful features is that it tracks packages you install and marks packages installed via dependency as such, so when you remove a package that is no longer used, or package updates and doesn't use a library anymore, that dependency will get uninstalled.

You can mark packages installed as automatically installed by hitting 'M' (uppercase m), it will be marked for deinstallation if it's not longer required.

You could also install <tt>localepurge</tt>, which will remove all unneeded locales and localized manpages for packages you install.

===System clock===
<tt>ntpd</tt> can occupy around 4MB of memory, which is a substantial proportion of many older systems' total. [http://chrony.sunsite.dk/ <tt>chrony</tt>] is a pair of programs that replace the standard <tt>ntp</tt> and require much less memory.

How to get special keys to work

2008-12-11T15:16:33Z

Low: /* NumPad (KeyPad) keys access by a key combination */

==Overview==
The following table gives an overview over the special keys found on ThinkPads and what is needed to make them work.
{| {{prettytable}}
! key !! standard function{{footnote|1}} !! tools supporting key{{footnote|2}} !! configurability{{footnote|3}} !! remarks
|-
| {{key|Fn}} || - || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || on release without completed key combination
|-
| {{key|Fn}}{{key|F1}} || - || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full ||
|-
| {{key|Fn}}{{key|F2}} || lock screen || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full || in models from T/X/Z 60 onwards
|-
| {{key|Fn}}{{key|F3}} || blank screen || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full ||
|-
| {{key|Fn}}{{key|F4}} || suspend to ram || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full || may generate ACPI event when not enabled in the ibm-acpi hotkey mask
|-
| {{key|Fn}}{{key|F5}} || switch bluetooth || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full || in models starting from 2002
|-
| {{key|Fn}}{{key|F6}} || - || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full ||
|-
| {{key|Fn}}{{key|F7}} || toggle display || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]], [[#tpb configuration|tpb]] || additional actions || [[Sample Fn-F7 script]]
|-
| {{key|Fn}}{{key|F8}} || toggle trackpoint/touchpad || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]], [[#tpb configuration|tpb]] || additional actions ||
|-
| {{key|Fn}}{{key|F9}} || eject from dock || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full ||
|-
| {{key|Fn}}{{key|F10}} || - || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| {{key|Fn}}{{key|F11}} || - || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full ||
|-
| {{key|Fn}}{{key|F12}} || hibernate || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full || may generate ACPI event when not enabled in the ibm-acpi hotkey mask
|-
| {{key|Fn}}{{key|Home}} / {{key|Fn}}{{key|Pos1}} || brightness up || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]], [[#tpb configuration|tpb]], [[KMilo]] || additional actions ||
|-
| {{key|Fn}}{{key|End}} || brightness down || [[thinkpad-acpi]], [[#tpb configuration|tpb]], [[KMilo]] || additional actions ||
|-
| {{key|Fn}}{{key|PageUp}} || toggle thinklight || [[thinkpad-acpi]], [[#tpb configuration|tpb]], [[KMilo]] || additional actions ||
|-
| {{key|Fn}}{{key|Space}} || toggle zoom || [[thinkpad-acpi]], [[#tpb configuration|tpb]], [[KMilo]] || full ||
|-
| {{key|Fn}}{{key|Ins}} || - || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]]|| full ||
|-
| {{key|Fn}}{{key|Del}} || - || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| {{key|Fn}}{{key|Backspace}} || - || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| {{key|NumLock}} || - || [[#xmodmap configuration|xmodmap]] || make working ||
|-
| {{key|Windows}} || - || [[#xmodmap configuration|xmodmap]] || remapping ||
|-
| {{ibmkey|Access IBM|#495988}} or {{ibmkey|ThinkPad|#494949}} or {{ibmkey|ThinkVantage|#495988}} || help application || [[thinkpad-acpi]],[[#tpb configuration|tpb]], [[KMilo]] || full ||
|-
| {{ibmkey|Home|#494949}} || open web browser || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]], [[KMilo]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards
|-
| {{ibmkey|Search|#494949}} || open search application || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]], [[KMilo]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards
|-
| {{ibmkey|Mail|#494949}} || open mail application || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]], [[KMilo]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards
|-
| {{ibmkey|Favorites|#494949}} || open favorites || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards
|-
| {{ibmkey|Reload|#494949}} || reload web page || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards
|-
| {{ibmkey|Abort|#494949}} || abort loading page || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards
|-
| {{ibmkey|Backward|#494949}} || previous page || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || ext. keyboards and ThinkPads starting from 2002
|-
| {{ibmkey|Forward|#494949}} || next page || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || ext. keyboards and ThinkPads starting from 2002
|-
| {{ibmkey|Volume up|#494949}} || volume up || [[thinkpad-acpi]], [[#tpb configuration|tpb]], [[KMilo]] || additional actions ||
|-
| {{ibmkey|Volume down|#494949}} || volume down || [[thinkpad-acpi]], [[#tpb configuration|tpb]], [[KMilo]] || additional actions ||
|-
| {{ibmkey|Volume mute|#494949}} || mute volume || [[thinkpad-acpi]], [[#tpb configuration|tpb]], [[KMilo]] || additional actions ||
|-
| {{ibmkey|Play/Pause|#494949}} || start/pause playback || [[#xmodmap configuration|xmodmap]] || full || {{X60s}} (Fn+Arrow Down)
|-
| {{ibmkey|Stop|#494949}} || stop playback || [[#xmodmap configuration|xmodmap]] || full || {{X60s}} (Fn+Arrow Up)
|-
| {{ibmkey|Next|#494949}} || play next || [[#xmodmap configuration|xmodmap]] || full || {{X60s}} (Fn+Arrow Right)
|-
| {{ibmkey|Previous|#494949}} || play previous || [[#xmodmap configuration|xmodmap]] || full || {{X60s}} (Fn+Arrow Left)
|-
| {{ibmkey|Power|#494949}} || shutdown || [[#ibm-acpi events|ibm-acpi]],[[thinkpad-acpi]] || full || triggered on pressing 3secs, but notebook goes off on 5sec press
|-
| Display lid || blank screen || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full ||
|-
| Ultrabay lid || announce ultrabay change || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| Dock eject || eject from dock || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| {{ibmkey|Tablet power|#494949}} || shutdown || [[#ibm-acpi events|ibm-acpi]] || full || triggered on pressing 3secs, but notebook goes off on 5sec press
|-
| {{ibmkey|Tablet orientation|#494949}} || rotates screen || [[#Mapping keys with setkeycodes|setkeycodes]] || full ||
|-
| {{ibmkey|Tablet shortcut|#494949}} || shortcut menu || [[#Mapping keys with setkeycodes|setkeycodes]] || full ||
|-
| {{ibmkey|Tablet Esc|#494949}} || esc key || [[#Mapping keys with setkeycodes|setkeycodes]] || full ||
|-
| {{ibmkey|Tablet Enter|#494949}} || enter key || [[#mapping keys with setkeycodes|setkeycodes]] || full ||
|-
| {{ibmkey|Tablet Up|#494949}} || up key || [[#Mapping keys with setkeycodes|setkeycodes]] || full ||
|-
| {{ibmkey|Tablet Down|#494949}} || down key || [[#Mapping keys with setkeycodes|setkeycodes]] || full ||
|-
| {{ibmkey|Tablet (unlabeled)|#494949}} || down key || [[#Mapping keys with setkeycodes|setkeycodes]] || full ||
|}

For completeness, note that the WiFi enable/disable switch is located (on the X61 and other models that have it) just under the front edge of the base of the machine. You should see a small horizontal slider switch. Enable by sliding it rightwards, disable by sliding it leftwards.

==Triggering key events==
===ibm-acpi/thinkpad-acpi events===
Some of the following events require a {{cmdroot|echo enable,0xffff >/proc/acpi/ibm/hotkey}} (when using ibm-acpi) in order to make acpi able to get information on them. Since the newer thinkpad-acpi has a larger number of bits that can be set in the mask, you might try {{cmdroot|echo enable,0xffffffff >/proc/acpi/ibm/hotkey}} if you are using this driver. These events can be used to [[How to configure acpid|configure acpid]].

{| {{prettytable}}
|+ events triggered by [[ibm-acpi]] for {{path|/etc/acpi/events}} files. May vary on different models.
! key !! event
|-
| {{key|Fn}}{{key|F1}} || ibm/hotkey HKEY 00000080 00001001
|-
| {{key|Fn}}{{key|F2}} || ibm/hotkey HKEY 00000080 00001002
|-
| {{key|Fn}}{{key|F3}} || ibm/hotkey HKEY 00000080 00001003
|-
| {{key|Fn}}{{key|F4}} || ibm/hotkey HKEY 00000080 00001004
|-
| {{key|Fn}}{{key|F5}} || ibm/hotkey HKEY 00000080 00001005
|-
| {{key|Fn}}{{key|F6}} || ibm/hotkey HKEY 00000080 00001006
|-
| {{key|Fn}}{{key|F7}} || ibm/hotkey HKEY 00000080 00001007
|-
| {{key|Fn}}{{key|F8}} || ibm/hotkey HKEY 00000080 00001008
|-
| {{key|Fn}}{{key|F9}} || ibm/hotkey HKEY 00000080 00001009
|-
| {{key|Fn}}{{key|F10}} || ibm/hotkey HKEY 00000080 0000100a
|-
| {{key|Fn}}{{key|F11}} || ibm/hotkey HKEY 00000080 0000100b
|-
| {{key|Fn}}{{key|F12}} || ibm/hotkey HKEY 00000080 0000100c
|-
| {{key|Fn}}{{key|Backspace}} || ibm/hotkey HKEY 00000080 0000100d
|-
| {{key|Fn}}{{key|Ins}} || ibm/hotkey HKEY 00000080 0000100e
|-
| {{key|Fn}}{{key|Del}} || ibm/hotkey HKEY 00000080 0000100f
|-
| {{key|Fn}}{{key|Home}}/{{key|Fn}}{{key|Pos1}} || ibm/hotkey HKEY 00000080 00001010
|-
| {{key|Fn}}{{key|End}} || ibm/hotkey HKEY 00000080 00001011
|-
| {{key|Fn}}{{key|PgUp}} || ibm/hotkey HKEY 00000080 00001012
|-
| {{key|Fn}}{{key|Space}} || ibm/hotkey HKEY 00000080 00001014
|-
| {{ibmkey|Volume up|#494949}}|| ibm/hotkey HKEY 00000080 00001015
|-
| {{ibmkey|Volume down|#494949}} || ibm/hotkey HKEY 00000080 00001016
|-
| {{ibmkey|Volume mute|#494949}} || ibm/hotkey HKEY 00000080 00001017
|-
| {{ibmkey|Access IBM|#495988}} or {{ibmkey|ThinkPad|#494949}} or {{ibmkey|ThinkVantage|#495988}} || ibm/hotkey HKEY 00000080 00001018
|-
| Ultrabay eject || ibm/bay MSTR 00000003 00000000
|-
| Ultrabay inserted || ibm/bay MSTR 00000001 00000000
|-
| Dock eject || ibm/dock GDCK 00000003 00000001
|-
| Wireless switch || ibm/hotkey HKEY 00000080 00007000
|}

By disassembling and editing the DSDT, more events can be added. HKEY events are triggered by calls to the MKHQ function, e.g. <tt>\_SB.PCI0.LPC.EC.HKEY.MHKQ(0Ã—1007)</tt> will trigger "ibm/hotkey HKEY 00000080 00001007". Most of these can be found in <tt>_Qxx</tt> methods within the DSDT, which are executed on embedded controller events, e.g. _Q10 is triggered by pressing Fn-F7. You can add a call to MKHQ into an existing <tt>_Qxx</tt> method to get it recognized by ibm-acpi as well as creating new <tt>_Qxx</tt> methods, which if you're lucky will correspond to an EC event that IBM never used (e.g. A 770 will send Fn-Home/End/PgUp/PgDn to ibm-acpi if hacked in this fashion). For example, [http://www.wormnet.eu/ibm-g40/morebuttons.dsl this is a modified block of DSDT for a G40].

=== ACPI events from the <tt>button</tt> module===

A few keys can generate ACPI events that result from the <tt>button</tt> kernel module, as long as they are masked off in the <tt>ibm-acpi</tt>/<tt>thinkpad-acpi</tt> hotkey's mask or the hotkey function of the latter module is disabled.

If you want the ThinkPad's BIOS and ACPI methods to know about these keys being pressed, you probably want to leave them masked out from ibm-acpi, and use their non-HKEY events listed below, instead.

{| {{prettytable}}
|+ events triggered by ACPI when hotkey is masked out or disabled.
! key !! event !! T60 event
|-
| {{ibmkey|Power|#494949}} || button/power PWRF 00000080 xxxxxxxx || button/power PWRF 00000080 00000001
|-
| {{key|Fn}}{{key|F4}} || button/sleep SLPB 00000080 00000001 || button/sleep SLPB 00000080 00000001
|-
| Display lid || button/lid LID 00000080 xxxxxxxx || button/lid LID 00000080 00000001
|}

===tpb configuration===
{| {{prettytable}}
|+ configuration keywords for [[tpb]] (to put in {{path|/etc/tpbrc}})
! key !! config keyword
|-
| {{ibmkey|Access IBM|#495988}} or {{ibmkey|ThinkPad|#494949}} || THINKPAD
|-
| {{ibmkey|Home|#494949}} || HOME
|-
| {{ibmkey|Search|#494949}} || SEARCH
|-
| {{ibmkey|Mail|#494949}} || MAIL
|-
| {{ibmkey|Favorites|#494949}} || FAVORITES
|-
| {{ibmkey|Reload|#494949}} || RELOAD
|-
| {{ibmkey|Abort|#494949}} || ABORT
|-
| {{ibmkey|Backward|#494949}} || BACKWARD
|-
| {{ibmkey|Forward|#494949}} || FORWARD
|-
| {{key|Fn}} || FN
|-
| {{key|Fn}}{{key|Space}} || CALLBACK (zoom on/off)
|-
| {{key|Fn}}{{key|PageUp}} || CALLBACK (thinklight on/off)
|-
| {{key|Fn}}{{key|F7}} || CALLBACK (display lcd/crt/both)
|-
| {{key|Fn}}{{key|F8}} || CALLBACK (expand on/off)
|-
| {{key|Fn}}{{key|Home}} / {{key|Fn}}{{key|Pos1}} || CALLBACK (brightness <percent>)
|-
| {{key|Fn}}{{key|End}} || CALLBACK (brightness <percent>)
|-
| {{ibmkey|Volume up|#494949}} || CALLBACK (volume <percent>)
|-
| {{ibmkey|Volume down|#494949}} || CALLBACK (volume <percent>)
|-
| {{ibmkey|Volume mute|#494949}} || CALLBACK (mute on/off)
|}

To all parameter keywords should be assigned the full path to the executables supposed to be started on key press.
The exectable provided for the CALLBACK keyword should take the parameters given in parentheses and act according to them.
If you want to use xmodmap for the HOME, SEARCH, MAIL, FAVORITES, RELOAD, ABORT, BACKWARD, FORWARD and FN keys you should
provide a <tt>XEVENTS OFF</tt> in your {{path|/etc/tpbrc}}.
You can use an appropriate executable to [[How to inject fake keystrokes|inject fake keystrokes]].

For Debian users, tpb is started from {{path|/etc/X11/Xsession.d/90tpb}}.

'''Sound Button configuration'''

''Note: Tested on T60p with Ubuntu 6.06 LTS''

Most Thinkpads have a hardware sound mixer, thus the volumes buttons should work without configuration. However, this change is not reflected in the software mixer. tpb has a switch to enable software mixer support via OSS. The manual recommends this only for devices without a hardware mixer, but it also works for other hadware mixer enabled devices, even with the ALSA system. Just put MIXER ON in your {{path|/etc/tpbrc}} file and you can see the effect immediately in any ALSA mixer (e.g. kmix). For this to work you need write permissions to {{path|/dev/nvram}}.

''Note: Tested on X21 with Ubuntu 6.06 LTS''

On the ThinkPad X21 (and maybe some other older models) ACPI causes problems with tpb. On an X21 using acpi the volume buttons would work occasionally, and the OSD for tpb functions would rarely work. If a volume buttons was pressed too often, sometimes the computer would enter a low power (unplugged state) and would require a reboot. The solution is to use APM instead of ACPI. Instructions can be found in [[How_to_make_APM_work]].

===KMilo configuration===
The programs to be executed by [[KMilo]] are configured via the KDE Control Center (<tt>kcontrol</tt>), under <tt>System Administration --> IBM Thinkpad Laptop</tt>. Note that you can use appropriate commands to [[How to inject fake keystrokes|inject fake keystrokes]].

===xmodmap configuration===
xmodmap enables you to edit the modifier map and keymap tables that are used to translate keycodes into keysyms.
Understood? Well, basically it allows you to give the X server a dictionary for the translation of keycodes like "97" into more human readable synonyms like "Home". This way xmodmap allows you to make the special keys of your keyboard known to X applications.

To discover the keycode that a certain keypress produces, use the tool {{cmduser|xev}}

Usually you should write your keycode-keysym associations into the file {{path|~/.Xmodmap}}. This file is usually read by the X session startup scripts of your system, so that the mappings automatically get included everytime you run the X server.

The {{path|~/.Xmodmap}} lines for our purpose are in the form of
keycode <keycode> = <keysym>

Load the assocation using the command

{{cmduser|xmodmap ~/.Xmodmap}}

(some configurations do this automatically upon X startup).

The following table shows the keycodes generated by the ThinkPad special keys and sensible keysyms to assign them to.
{| {{prettytable}}
|+ keycodes and recommended keysyms
! key !! keycode !! keysym
|-
| {{ibmkey|Access IBM|#495988}} or {{ibmkey|ThinkPad|#494949}} || 159 || XF86LaunchA
|-
| {{ibmkey|Backward|#494949}} || 234 || XF86Back or F19
|-
| {{ibmkey|Forward|#494949}} || 233 || XF86Forward or F20
|-
| {{ibmkey|Play/Pause|#494949}} || 162 || XF86AudioPlay
|-
| {{ibmkey|Stop|#494949}} || 164 || XF86AudioStop
|-
| {{ibmkey|Next|#494949}} || 153 || XF86AudioNext
|-
| {{ibmkey|Previous|#494949}} || 144 || XF86AudioPrev
|-

| {{ibmkey|Home|#494949}} || 178 || XF86HomePage
|-
| {{ibmkey|Search|#494949}} || 229 || XF86Search
|-
| {{ibmkey|Mail|#494949}} || 236 || XF86Mail
|-
| {{ibmkey|Favorites|#494949}} || 230 || XF86AddFavorite or XF86Favorites
|-
| {{ibmkey|Reload|#494949}} || 231 || XF86Reload
|-
| {{ibmkey|Abort|#494949}} || 232 || XF86Stop
|-
| {{key|Fn}} || 227 || F35
|}

Note: You can also use xkeycaps (an X tool to display and edit the X keyboard mapping) to generate proper .Xmodmap.

Note: if you are running [[tpb]] you might need to add the line <tt>XEVENTS=off</tt> into your tpbrc to stop it from grabbing the key events and allow them to get through to X instead. See [[http://www.thinkwiki.org/wiki/Tpb]] for more detailed instruction on how to use tpb and xmodmap.

Note: XF86Forward and XF86Back do not work correctly in Firefox. You may want to map them to F19 and F20 instead if you use Firefox.

Note: The "XF86AudioPlay" etc. just works with a few programs. To make it work with more multimedia programs you have map the key to use something like [http://www.kde-apps.org/content/show.php/ReMoot?content=63140 ReMoot]. ReMoot is a command line wrapper that control 18 of the most common multimedia applications.

=====Enabling the Windows and Menu Keys=====
On some systems the Windows and Menu keys may not be recognized. You can enable then by
making the following changes:

keycode 115 = F13
keycode 227 = F35

F13 and F35 are used for the Windows and and Menu keys respectively. Labelling keycpode 227 as "Menu" may conflict with the right-mouse-click event.

=====Using Caps Lock as Super L (Windows key)=====
You can easily use Caps Lock as Win key by adding the following in your ~/.Xmodmap:
! No Caps Lock
clear lock
! Caps Lock as Win key
add mod4 = Caps_Lock
=====NumLock=====
On the ThinkPad {{600}}, {{T20}}, {{T21}}, {{T22}}, {{T30}}, {{X20}}, {{X21}}, {{X31}}, {{X40}}, {{T42p}}, {{T43}}, {{R51}}, {{R52}} and possibly other models, X does not recognize the keycode for {{key|NumLk}} = {{key|Shift}}+{{key|ScrLk}}. To fix this, add the following to {{path|~/.Xmodmap}} in your home directory or {{path|/etc/X11/Xmodmap}} and run <tt>xmodmap</tt>, ex: <tt>xmodmap ~/.Xmodmap</tt>:
keycode 77 = Num_Lock

This configuration also enables the respective LED.

Please note, pressing the {{key|Shift}}+{{key|ScrLk}} key combination, without first following the above configuration, will start an accessibility feature, which will allow the numeric keypad to maneuver the mouse pointer. Starting this accessibility feature and subsequently running xmodmap, as described above, results in the accessibility feature and the numeric lock LED functioning simultaneously. As such, the above configuration should be completed before the accessibility feature is started in order to produce numbers.
======T60 (and possibly others)======
It seems that on the T60, PrtSc, ScrLk and Pause all generate the correct keycodes, however Fn-PrtSc (labelled as SysRq) generates keycode 64 (Alt_L) followed by the expected 111 (Sys_Req) on down and the same thing in the opposite order on release. Fn-ScrLk (labelled as NmLk) does indeed toggle the Numlock, but only seems to register as an X event the first time it is engaged. The above solution does not appear to work. This is perhaps because the Numlock toggle is built into the firmware rather than controlled by the kernel. Finally, Fn-Pause (labelled as Break) generates keycode 37 (Control_L) followed by the expected keycode 110 (Break) on down and the same thing in reverse order on release.
=====NumPad (KeyPad) keys access by a key combination=====
The current state is that you have to switch NumLock '''on''' via {{key|Fn}}+{{key|ScrLk}} and then e.g. type {{key|u}} to get a {{key|KP_4}} (NumPad 4). To get back to normal keyboard, you have to type {{key|Fn}}+{{key|ScrLk}} again.

Some people (including me) are missing on recent Thinkpads the option to have Fn as a modifier key to access the NumPad instead, i.e. and e.g. {{key|Fn}}+{{key|u}} gives you {{key|KP_4}}.

There is currently no way to make this work in a simple way (pleeeease correct me if I am wrong!), though there is a work-around. Instead of using {{key|Fn}} for accessing the NumPad, {{key|CapsLock}} can get this function by being mapped as Mode_switch (the {{key|AltGr}} on international keyboards). The {{key|Fn}} can be remapped to be Caps_Lock - while at the same time retaining its function to access the special laptop functions (e.g. {{key|Fn}}+{{key|F4}} for sleep}}, by using .Xmodmap.

So on my R60 running fvwm@Slackware 12.1 the .Xmodmap would look like this:

! Make the forward and back buttons work
keycode 233 = XF86Forward
keycode 234 = XF86Back
! Make the WIN key to Super modifier
keycode 115 = Super_L
! Set the Caps_Lock physical key to Mode_switch (like AltGr on intl. keyboards)
keycode 66 = Mode_switch
! Set the Fn key to work as Caps_Lock now. The special key combos like Fn-F4 for "sleep" still work then
keycode 227 = Caps_Lock
clear lock
add lock = Caps_Lock
! Now we activate those new keys. Find some free mod slots (xmodmap) and put them there.
clear mod4
clear mod5
add mod4 = Super_L
add mod3 = Mode_switch
! It's time to add the keypad keys to the third position of the key definition (pure shift mode_switch shift+mode_switch)
keycode 16 = 7 ampersand KP_7
keycode 17 = 8 asterisk KP_8
keycode 18 = 9 parenleft KP_9
keycode 19 = 0 parenright KP_Divide
keycode 30 = u U KP_4
keycode 31 = i I KP_5
keycode 32 = o O KP_6
keycode 33 = p P KP_Multiply
keycode 44 = j J KP_1
keycode 45 = k K KP_2
keycode 46 = l L KP_3
keycode 47 = semicolon colon KP_Subtract
keycode 58 = m M KP_0
! ... I have to use the coma key, too, on the keypad...so I set it to be F20 (which is not existing on normal keyboards and thus is free... check for side effects in programmes accepting F12+ keys!)
keycode 59 = comma less F20
keycode 60 = period greater KP_Decimal
keycode 61 = slash question KP_Add

{{WARN|Your keycodes might be different as well as your '''mod''#''''' settings.}}
Use {{cmduser|xmodmap}} and {{cmduser|xmodmap -pke}} to check your ModMap, and the tool {{cmduser|xev}} to obtain your exact key codes.

===Mapping keys with setkeycodes===
You can use the setkeycodes command to remap certain keys. I.e. you can use {{cmdroot|setkeycodes 6e 109 6d 104 69 28 6b 1}} to map the Tablets Up and Down keys to the standard PageUp and PageDown keys and Tablet Escape and Enter to their respective keys.

The following table shows the keycodes generated by the ThinkPad keys.
{| {{prettytable}}
|+ keycodes
! key !! keycode
|-
| {{ibmkey|Tablet orientation|#494949}} || 0x6c
|-
| {{ibmkey|Tablet Shortcut|#494949}} || 0x68
|-
| {{ibmkey|Tablet Esc|#494949}} || 0x6b
|-
| {{ibmkey|Tablet Enter|#494949}} || 0x69
|-
| {{ibmkey|Tablet Up|#494949}} || 0x6d
|-
| {{ibmkey|Tablet Down|#494949}} || 0x6e
|-
| {{ibmkey|Tablet (unlabeled)|#494949}} || 0x67
|}

===acpi_fakekey===
You can turn acpi events into user-level xevents by putting <tt>acpi_fakekey</tt> commands into the acpi action scripts. There are several layers involved in using acpi keys in this way, so I'll go through the example of using the ThinkVantage button to open xmms.

My ThinkVantage button generates an '''acpi event''' "ibm/hotkey HKEY 00000080 00001018", so we have the event file <tt>/etc/acpi/events/ThinkVantage</tt> for it which executes the script <tt>/etc/acpi/actions/fakekey-macro.sh</tt>.
<pre>
event=ibm/hotkey HKEY 00000080 00001018
action=/etc/acpi/actions/fakekey-macro.sh
</pre>
In turn, the executable <tt>/etc/acpi/actions/fakekey-macro.sh</tt> script calls acpi_fakekey with the '''key number''' defined in <tt>/usr/share/acpi-support/key-constants</tt> as $KEY_MACRO which is 112 (you could just as well choose an other key number, just make sure that it doesn't belong to something else like the "j" key or something).
<pre>
#!/bin/sh
. /usr/share/acpi-support/key-constants
acpi_fakekey $KEY_MACRO
</pre>
I have no idea how this actually corresponds to which xevent is generated, so I can find out out by running the program <tt>xev</tt> and hitting the ThinkVantage button while the mouse is in the <tt>xev</tt> window (remember to <tt>/etc/init.d/acpid restart</tt> first if you just created the <tt>/etc/acpi/events/ThinkVantage</tt> file). I get something popping up in the terminal where I ran xev that looks like this:
<pre>
KeyPress event, serial 30, synthetic NO, window 0x2800001,
root 0x6a, subw 0x0, time 2000522842, (138,83), root:(781,500),
state 0x0, keycode 239 (keysym 0x0, NoSymbol), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 30, synthetic NO, window 0x2800001,
root 0x6a, subw 0x0, time 2000522842, (138,83), root:(781,500),
state 0x0, keycode 239 (keysym 0x0, NoSymbol), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
</pre>
This tells me that the <tt>acpi_fakekey 112</tt> as executed by hitting the ThinkVantage button generates KeyPress event followed by a KeyRelease event with '''keycode''' 239 and that this keycode has been assigned no corresponding '''keysym'''. Thus, I am free to assign the keycode to any keysym I want. You can find a list of available keysyms in <tt>/usr/share/X11/XKeysymDB</tt>. Again try and pick one that is not likely to have already been taken by something, such as <tt>XF86LaunchA</tt>. To assign this keysym to keycode 239, you can either edit ~/.Xmodmap on an individual user basis, or edit the systemwide <tt>/etc/X11/Xmodmap</tt> file to contain the line
<pre>
keycode 239 = XF86LaunchA
</pre>
If you choose to go with the former, you may need to run <tt>xmodmap ~/.Xmodmap</tt> for every login session in order to read in your ~/.Xmodmap file if your window manager does not do it for you. Regardless of which option you choose, you can run <tt>xmodmap <file></tt> to read in the updated Xmodmap file without logging out and logging back in.

You should now find that hitting the ThinkVantage button creates the following output from <tt>xev</tt>:
<pre>
KeyPress event, serial 55, synthetic NO, window 0x2800001,
root 0x6a, subw 0x0, time 2001286078, (0,106), root:(643,523),
state 0x0, keycode 239 (keysym 0x1008ff4a, XF86LaunchA), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 55, synthetic NO, window 0x2800001,
root 0x6a, subw 0x0, time 2001286078, (0,106), root:(643,523),
state 0x0, keycode 239 (keysym 0x1008ff4a, XF86LaunchA), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
</pre>
Note the change of <tt>(keysym 0x0, NoSymbol)</tt> to <tt>(keysym 0x1008ff4a, XF86LaunchA)</tt>.

You're now ready to map <tt>XF86LaunchA</tt> to executing xmms. This is highly dependent on what keygrabber you decide to use. For openbox, I edit my <tt>~/.config/openbox/rc.xml</tt> file and add the following entry in the <keyboard> section:
<pre>
<keybind key="XF86LaunchA">
<action name="Execute">
<startupnotify>
<enabled>true</enabled>
</startupnotify>
<command>
xmms
</command>
</action>
</keybind>
</pre>
After, right clicking on the desktop and selecting the "Reconfigure" menu option, you should then have xmms pop up when you hit the ThinkVantage key.

==Example Applications==
===Web Browsers===
====Firefox (<3.0)====

There are various ways to assign actions to the browser keys. The easiest way is to install [http://mozilla.dorando.at/keyconfig.xpi keyconfig.xpi] from http://mozilla.dorando.at, which adds a menu entry Tools->Keyconfig. Then you can assign any action you want to the F19/F20 keys (you still need to create {{path|~/.Xmodmap}} as explained above).

The remaining discussion gives you various more complicated ways to achieve the same thing.
To have firefox make use of the browser keys you need to modify one of its files{{footnote|4}}.
To do this you will first need to extract it from the {{path|browser.jar}} archive. Do...

Step 1: Edit .Xmodmap and add entries for F19 and F20 as explained above.

Step 2:

Note: <firefox-directory> is probably /usr/lib/firefox. Use your version so, if you have 3.0.1 or 3.0.2 use /usr/lib/firefox-3.0.1

:{{cmdroot|cd <firefox-directory>/chrome}} 
:{{cmdroot|unzip browser.jar}}

The file of interest is {{path|content/browser/browser.xul}}. Edit it {and don't forget to make a backup copy first}...
:{{cmdroot|vi content/browser/browser.xul}}

Look for the '''<keyset id="mainKeyset">''' section and add the following lines within...
<key id="goBackKb" keycode="VK_F19" command="Browser:Back" />
<key id="goForwardKb" keycode="VK_F20" command="Browser:Forward" />

The Command you need for Next Tab
<key id="goBackTabKb" keycode="VK_F19" oncommand="gBrowser.mTabContainer.advanceSelectedTab(-1)" />
For the Previous Tab
<key id="goForwardTabKb" keycode="VK_F20" oncommand="gBrowser.mTabContainer.advanceSelectedTab(1)" />

Now save the file and repackage the {{path|browser.jar}} archive...
:{{cmdroot|zip -rD0 browser.jar content/browser/}}

That's it.

Step 3: Restart Firefox.

{{HINT|Outdated: Another interesting Page on Firefox is http://dqd.com/~mayoff/notes/thinkpad/dqdnavkeys/ It uses different key mappings (F19 resp. F20) but a ready [http://dqd.com/~mayoff/notes/thinkpad/dqdnavkeys/dqdnavkeys-1.2.xpi .xpi] is provided which is pretty comfortable. However, this xpi file does not install on Firefox 1.5. or later.}}

{{HINT| You can also use the [http://extensionroom.mozdev.org/more-info/keyconfig keyconfig] extension to configure custom keys. This extension works with Firefox 1.5 and also with Firefox 2.0. The Command you need for Next Tab is gBrowser.mTabContainer.advanceSelectedTab(1,true); For Previous Tab its gBrowser.mTabContainer.advanceSelectedTab(-1,true); You can alternatively install the [http://www.pqrs.org/~tekezo/firefox/extensions/functions_for_keyconfig/index.html functions for keyconfig] and set the variable f4kc_NextTab to F20 and f4kc_PrevTab to F19.}}.

====Firefox 3.0====
Thankfully the people at Mozilla decided to include the expected functionality for the XF86Back and XF86Forward keysyms in the new release so all you need to do is
 <code># printf 'keycode 234 = XF86Back\nkeycode 233 = XF86Forward' >> /etc/X11/Xmodmap</code> 
And to make this take effect immediately (i.e., without having to log out and log in again), as a regular user run:
 <code>{{cmduser|Xmodmap /etc/X11/Xmodmap}}</code>

For Hardy Heron, the xmodmap command is all lowercase. Also, the /etc/X11/Xmodmap file is not being read on boot. I've added the command to my .bashrc to have it called on startup.

====Konqueror====
KDE allows you set key mappings for KDE applications (Go to KMenu > System > Control Center > Regional & Accessibility > Keyboard Shortcuts). By default (at least in KDE 3.5), XF86Back and XF86Forward are set as alternatives to Alt-Left and Alt-Right, and are mapped to KDE Back and Forward navigation actions.

If you use Konqueror as your only browser, you only need to set up {{path|~/.Xmodmap}} as described [[#xmodmap configuration|above]] to assign ThinkPad back/forward keys to the symbols XF86Back/XF86Forward. This also make these keys work for other KDE applications such as Quanta Plus, KPackage and so on (not all KDE applications honor this setting, e.g. KDE help system doesn't).

If you want to use Firefox, however, the above settings do not work. You will have to map ThinkPad back/forward keys to F19/F20 as described [[#Firefox|above]], and change KDE navigation key settings to use F19/F20 instead of the default.

====Opera====
However this isn't a simple configration file, you can set your browser manually. 
Go to Tool > Settings > Mouse and keyboard > Keyboard settings > Edit > Browser Window. There add F19 - Back and F20 - Forward. Now you can surf using your TP keys ;-)

====Epiphany====
To get the keys work in epiphany, you could use the extension from [http://crashman.homelinux.org/~andre/public/epiphany%20extensions/thinkpad%20browserkeys/ here]
You just need to edit your Xmodmap like described for Firefox < 3.0 (bind the keys on F19 and F20)

===Open an application===

To configure the ThinkVantage button to open a terminal window in Gnome:

Step 1:
Use xev to find the keycode generated by the button on your machine. In my case is is 159.

Step 2:
Create an entry in .Xmodmap like so

keycode 159 = XF86LaunchA

replacing 159 by the keycode found in step 1. Load the map using

:{{cmd|xmodmap ~/.Xmodmap}}

Step 3:
Configure the required function (e.g. open terminal window) in System->Preferences->Keyboard shortcuts

===Window Managers===
====fvwm====
To get the {{ibmkey|Forward|#494949}} and {{ibmkey|Backward|#494949}} keys to cycle through pages in the virtual desktop, add this to your {{path|~/.fvwmrc}}:
Key XF86Back A A Scroll -100000 0
Key XF86Forward A A Scroll +100000 0
If you use multiple virtual desktops, you could instead use the keys to flip between them by using GotoDesk.

====fluxbox====
To get the keys to cycle through pages in the virtual desktop, add this to your {{path|~/.fluxbox/keys}}:
None F19 :PrevWorkspace
None F20 :NextWorkspace

====pekwm configuration====
You can make the two browser keys switch workspaces in pekwm, by adding the following two lines to the {{path|~/.pekwm/keys}} file:
KeyPress = "Mod1 XF86Back" { Actions = "GoToWorkspace prev" }
KeyPress = "Mod1 XF86Forward" { Actions = "GoToWorkspace next" }

====pwm====
Another example how to use these two keys to switch between pwm tabs. These two lines should be added to {{path|~/.pwm/keys-default.conf}} or {{path|/etc/pwm/keys-default.conf}}:
kbind "Back", "switch_rot", -1
kbind "Forward", "switch_rot", 1

====IceWM====
To make IceWM cycle workspaces using the {{ibmkey|Forward|#494949}} and {{ibmkey|Backward|#494949}} keys, change these two options in {{path|~/.icewm/preferences}} (Provided you assigned keysyms F19 and F20 with xmodmap):
# "Previous workspace" shortcut
KeySysWorkspacePrev="F19"
# "Next workspace" shortcut
KeySysWorkspaceNext="F20"

==== Gnome/metacity ====

Follow the [https://wiki.ubuntu.com/Keybindings Ubuntu guide].

===Other Uses===
====Console tools configuraton====
To make the {{ibmkey|Forward|#494949}} and {{ibmkey|Backward|#494949}} keys useful in console, add this to your keymap ({{path|/etc/console/boottime.kmap.gz}} in {{Debian}}):
keycode 158 = Decr_Console
keycode 159 = Incr_Console

Alternatively you can load this script (perhaps on system startup) to enable Backward/Forward button console (VT) switch:

#!/bin/sh
echo keycode 158 = Decr_Console | loadkeys
echo keycode 159 = Incr_Console | loadkeys

It should work with any distro.

====Cycling through tabs====
In Gnome and Xfce4, Ctrl-PageUp/Ctrl-PageDown move to the previous/following open tab in all applications that have tabbed user interfaces (terminal emulator, web browser, ...). To make use of the {{ibmkey|Forward|#494949}} and {{ibmkey|Backward|#494949}} keys for this task, there're two possibilities.

For both ways, you should map the keycodes 233 and 234 to XF86Back and XF86Forward as described in [[#xmodmap_configuration|xmodmap configuration]].

=====Using xautomation=====
xautomation can be found [http://hoopajoo.net/projects/xautomation.html here].

Create two files with permissions 755:

{{path|/usr/local/bin/tp_back}}:
<bash>
#!/bin/bash
/usr/bin/xte 'keydown Control_L' 'keydown Page_Up' 'keyup Page_Up' 'keyup Control_L'
</bash>

{{path|/usr/local/bin/tp_forward}}:
<bash>
#!/bin/bash
/usr/bin/xte 'keydown Control_L' 'keydown Page_Down' 'keyup Page_Down' 'keyup Control_L'
</bash>

Use your desktop's keyboard shortcut editor to assign XF86Back as a shortcut for tp_back and XF86Forward as a shortcut for tp_forward.

This should work in all distros and with all window managers (you might have to use other key combinations than Ctrl-PageUp and Ctrl-PageDown).

=====Redirecting XF86Back/XF86Forward=====
Create {{path|/etc/X11/xkb/compat/thinkpad}}:
<pre>
// $XFree86$
// XFree86 special keysyms
default partial xkb_compatibility "basic" {
interpret.repeat= True;

interpret XF86Back {
action = Redirect(Key=<PGUP>, modifiers=Control);
};
interpret XF86Forward {
action = Redirect(Key=<PGDN>, modifiers=Control);
};
};
</pre>

Edit {{path|/etc/X11/xkb/compat/complete}} and add <tt>'''augment "thinkpad"'''</tt> so that it looks similar to the following:
<pre>
// $XKeyboardConfig: xkbdesc/compat/complete,v 1.3 2005/10/17 00:42:11 svu Exp $
// $Xorg: complete,v 1.3 2000/08/17 19:54:34 cpqbld Exp $
default xkb_compatibility "complete" {
include "basic"
augment "iso9995"
augment "mousekeys"
augment "accessx(full)"
augment "misc"
augment "xfree86"
augment "level5"
augment "thinkpad"
};
</pre>

==External Sources==
*[http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-51537 IBMs page on configuring the ThinkPad buttons (ThinkPad, Access IBM, Mail, Search, and Home buttons) under Linux]
*[http://dqd.com/~mayoff/notes/thinkpad/dqdnavkeys/ Rob Mayoffs page on using IBM Keyboard Navigation Keys in Linux Mozilla and Firefox]
*[http://snarfed.org/space/thinkpad+keys+in+firefox Ryan Barretts blog article about using the browser keys in Firefox]
*[http://chaotika.org/~bluesceada/?page=soft&sub=thinkpad#acpibutn DennisG's help to get the ibm-acpi buttons do useful things] on a {{Z61e}} and possibly {{Z61m}}, {{Z61t}} and {{Z61p}}

{{footnotes|
#Note that the associated functionality for Fn-F* key combinations is not consistent amongst all ThinkPads. We are maintaining [[Default meanings of special keys|a table of associated meanings]].
#if there are more than one tool listed, one is sufficient
#'full' means you can completely reassign any action to be triggered by the key, 'additional actions' means you can trigger actions in addition to the standard function of the key, which can not be changed.
#Thanks go to Ryan Barrett for writing the [http://snarfed.org/space/thinkpad+keys+in+firefox little howto] on [http://snarfed.org/space/start his blog].
}}

Talk:ThinkWiki

2008-12-11T12:44:59Z

Low: /* ThinkPad Buyers guide */

{|
|__TOC__
|{{NOTE|This is not a user support forum about general ThinkPad questions, please do not abuse the Wiki by posting such questions here!}}
|}

There are at least two different forms of date notation used on the main page.
One way should be picked. I would suggest ISO standard YYYY-MM-DD
http://www.cl.cam.ac.uk/~mgk25/iso-time.html
-David Mattli

The main page of ThinkWiki is not protected, so feel free to edit it. But do it with caution - it's the primary connection to the all content of our '''ThinkWiki''' ;-)

--[[User:Akw|akw]] 00:11, 25 Sep 2004 (CEST)
----
I added to wikipedia-like templates. To edit them go to Template:ThinkWiki_Preamble and Template:ThinkWiki_News.
Shall we put the other parts of the page in templates, too? If we do so, we could have that nice block design from wikipedia on our mainpage.

--[[User:Akw|akw]] 11:37, 25 Sep 2004 (CEST)

----
I think this is too much color. Makes it less readable, takes longer to orientate than the plain list style layout.

Liked it with only the two blocks in the beginning.

If we want to use blocks for everything, please stick to fewer colors. I think the yellow of the first block is not bad, and else i'd suggest light grey, maybe light blue.

However, if we stick to having all in blocks, how about [[User:Wyrfel/mainlayouttest | this color scheme]]?

[[User:Wyrfel|Wyrfel]] 16:35, 25 Sep 2004 (CEST)

----
Made [[User:Wyrfel/mainlayouttest-LTP | another Mainpage layout sketch]]. This tries to resemble the Tux and IBM logo colors and therefor looks quite "fresh".

[[User:Wyrfel|Wyrfel]] 18:59, 25 Sep 2004 (CEST)

: Too colorful for my taste, I think the other one is better --[[User:Nomeata|Nomeata]] 19:46, 28 Sep 2004 (CEST)
----
'''Important change:''' Moved Main_Page to ThinkWiki for cosmetical reasons..

--[[User:Akw|akw]] 16:54, 26 Sep 2004 (CEST)
----

== Needed: older ThinkPad specs... ==

As you can tell by my userid here, I've got a 600E. There are a whole lot of them out there thanks to the fact it was the current model during the Dot-Com era. We should cover the older ThinkPads and their quirks as well as the later models.

I also had a 365X, which is now living with a friend in the UK.

Yes, the next ThinkPad I'll probably score is a T4x, they are really kewl machines and inspire technolust in this geek. But until then, I love my 600E and I'm looking forward to some upgrades this weekend.

I will make copious notes on the upgrade process, which will include the installation of a 40GB hard drive and using the stock 10GB drive as extra Windows storage space. I have a hard drive bay module so the stock drive can be reused. The vast majority of the HD will be given over to an install of Debian Linux, with a 7GB Windows 2K partition because the University I will be attending a year from now demands it. (Yeah, I know, sucks, doesn't it.)

ThinkPad different,
Michelle

----
I totally agree.

All specs of all models can be found on the IBM support pages, we just need volunteers to transfer the infos into internal pages.

Since this is not the most interesting thing to do and hence it would be best if people using older ThinkPads transfer the specs for their models themselves. The same goes for other articles as installation infos, problems or whatever. I had a 570 once and loved it even though T30s where available at the same time...and i'd like to see more about these machines here, which everyone of them had some special characteristics and ideas behind them. So please show up, proud owners of Thinkpad 730TEs. 701s, 360Ps, Transnotes etc. ... ! ;)

Owners of the newer machines should take care of writing their articles (especially when creating new pages or sections) in a way that they are open for older models as well...i.e. make clear in the page or section title that its a specific topic for newer models.

Thanks,
[[User:Wyrfel|Wyrfel]] 00:45, 29 Sep 2004 (CEST)
----
I just inserted [[Special:Benchmarks|Benchmarks]] into the main menu.

--[[User:Akw|akw]] 14:07, 15 Oct 2004 (CEST)
----
I replaced the old logo with the great new one crafted by [[User:Wyrfel|Wyrfel]]

--[[User:Akw|akw]] 14:22, 1 Mar 2005 (CET)

:The new logo is too large to fit the sidebar. I can only see the yellow center with the ThinkWiki text and the left foot of Tux. I am using 1024x768 resolution and Opera. --[[User:137.226.40.2|137.226.40.2]] 14:37, 1 Mar 2005 (CET)
----

In Firefox the rest of the logo appears overlaid over the page frame. Interesting, that Opera doesn't do this.

However, we'll fix this soon.

[[User:Wyrfel|Wyrfel]] 19:57, 1 Mar 2005 (CET)

----
:Well, I am using Firefox and I only see half of Tux without any overlay. I guess I'll wait for the fix :-) --[[User:80.146.81.192|80.146.81.192]] 21:33, 1 Mar 2005 (CET)
----
Strange, it works with firefox and epiphany for me. I'll fix it.
----
Ok, now the smaller logo image is online. Looks nice for me :-)

--[[User:Akw|akw]] 22:15, 1 Mar 2005 (CET)
----
=== Main Page now protected ===
I had to protect the mainpage from editing because of vandalism.
Everyone who wants to add something to the mainpage is asked to post it here, the admins ([[User:Akw|akw]],
[[User:Wyrfel|Wyrfel]]) will insert it into the mainpage. You can also [[ThinkWiki:Contact|contact us]] to make your suggestions!

We're sorry for inconvenience. :-(

--[[User:Akw|akw]] 10:20, 2 Mar 2005 (CET)
----

Can I start a thread on DVD playback for the X60, please? I can play back DVDs using SUSE 10.3, however any fast action parts are blurred. I do not know if this is a limitation of the graphics, or monitor hardware, or something else. Thanks

=== Updates todo ===

== MediaWiki Update ==

I updated the thinkwiki software to version mediawiki 1.4.4. I hope this update will not be too painful.
There is still a problem with URL rewriting, so I had to deactivate the .htaccess file. Because of this, we got this ugly URLS with this '''index.php''' before the entry. The problem seems to be with the wiki config file '''LocalSettings.php''' and/or the '''.htaccess''' file.
I hope I get it fixed soon.

== Spelling: HOWTOs ==
Could anyone be so kind to correct "Howto's" to "Howtos"?
----
Done. [[User:Wyrfel|Wyrfel]] 12:00, 2 Aug 2005 (CEST)
----

== ThinkPad Buyers guide ==

It would be cool is there was a buyer guide to 2nd hand think pads.
- For people wishing to join in by getting their own Thinkpad!!
----
This is a bit hard to accomplish. Remember that ThinkWiki is a site with international scope. What makes sense (in my opinion) is a page that has some notes and hints about what to care for, what are weak parts etc. . But it wouldn't make much sense to create a list of sites where to get them. Or maybe that's just what you meant. ;-) I'll look into creating some infrastructure for that on occasion.

[[User:Wyrfel|Wyrfel]] 03:02, 11 Aug 2005 (CEST)
----
Could we have a section explaining Lenovo that their (and everybody else's) policy of only having wide screen displays nowadays sucks for anyone not watching movies all day on their laptops, please?
--[[User:Low|Low]] 13:44, 11 December 2008 (CET)

== This is a great general resource for ANY Thinkpad user ==

The promoted Linux-centricity is a minus, IMO. Regardless of the density of Linux content currently extant, the Linux focus seems exclusionary and probably drives away a lot of thinkpad users with useful content to add.

----
IBM probably has the best support website in the industry (albeit somewhat difficult to navigate), therefore ANY ThinkPad user may find general information there. The good thing about ThinkWiki is that it caters to a specific need, namely the (often difficult) task of installing the linux operating system on ThinkPad notebooks.
--[[User:MJK|MJK]] 14:54, 14 Sep 2005 (CEST)

----
I have to agree with MJK. ThinkWikis clear focus is Linux on ThinkPads. IBM provides pretty good support for Windows users, i.e. it wouldn't make sense to double driver listings and such here, since what IBM provides in this area is sufficient. What we can do, however, and what we are already doing here, is to provide additional information for Windows users as well. That's why we introduced Windows as one of our listed distributions and that's also why you find Windows related information scattered around the place. Linux users are searching Windows related ThinkPad sites for information that might be useful for their Linux installations. Let Windows users do the same the other way around. I'll add a little hint to the main page, but we won't change the primary focus. At least not now.

[[User:Wyrfel|Wyrfel]] 19:24, 15 Sep 2005 (CEST)
----

== TODO and FIXME templates? ==

Could a special way to add TODOs and FIXMEs to pages (maybe a template or whatever - I'm not to familiair with Wiki technologies) be considered? I'd like to add some TODOs and FIXMEs but would like to do that in a standardized way ...

[[User:Pebolle|Paul Bolle]] 22:42, 29 Sep 2005 (CEST)
----
Good point, i'll create templates. [[User:Wyrfel|Wyrfel]] 00:25, 30 Sep 2005 (CEST)
----
Ok, did some of it. There are Stub, Todo and Fixme templates now. Also, pages tagged with these templates will be categorized in [[:Category:NeedsEditing]]. Todo and Fixme should be used within sections and take one parameter, which should be a job description. Stub should only be used at the very beginning of a page.

[[User:Wyrfel|Wyrfel]] 01:52, 30 Sep 2005 (CEST)
----

== Nitpicking ==
Navigation bar: please s/$Think$p$ad$/\1P\2/g

Search bar: either drop Go or drop Search (they are equal, aren't they?)

How to read ThinkWiki seems to be better of as a normal entry in the first (upper left) table (and not as a "minor" item in the HOWTOs table).

I would suggest to make ThinkPad models (now a "minor" item in Hardware) the first entry in Hardware.

[[User:Pebolle|Paul Bolle]] 21:13, 8 Oct 2005 (CEST)
----
Hi, I am looking for some t series users for our beta program. Plese contact mtippett@ati.com.
----

: Search bar: Go will try to go an article by that name while search will actually search fro articles that contain the word. '''Must keep'''.

==A Forum?==

I'm just curious if the idea of a public forum (using phpBB, SMF, whatever) has ever been considered. I think this would be excellent add-on to complement the Wiki. It'd make asking questions for guests and member's alike easier, and possibly afterwards the answers could be contributed into the article. Just an idea. --[[User:DuffDudeX1|DuffDudeX1]] 20:45, 31 Oct 2005 (CET)
----
There are ThinkPad Forums already, i.e. look at the [[Links]] page.

Moreover, there's the linux-thinkpad [[Mailinglists|mailinglist]] that serves this purpose. ThinkWiki's role is rather to complement that mailing list with a more static way of gathering information and to be found more easily.

[[User:Wyrfel|Wyrfel]] 23:54, 31 Oct 2005 (CET)
----

Oh, thanks for pointing that out, I didn't even notice the links page, I'll have to take a look.

--[[User:DuffDudeX1|DuffDudeX1]] 00:04, 1 Nov 2005 (CET)

== Nice skin, folks... ==

We'd like to steal it, for our geographically local wiki, if no one minds. What pieces would we need for that? --baylink@wp, etc; jra@baylink.com

----
Just customize your main.css in your monobook folder.

--[[User:Akw|akw]] 10:00, 28 Dec 2005 (CET)
----

== Wiki ToDo List ==

Hi, I just setup a [[User:Akw/ToDo|ToDo List]] regarding the wiki for me on [[User:Akw/ToDo]].

This is for server admininstration tasks. Feel free to add some points if I forgot something more or less important.
I am going to work on the topic in the beginning of next year. I am offline now until 2006/01/06, so I wish a happy good year to all of you (except for the spammers and vandals, of course) ;-)

--[[User:Akw|akw]] 10:31, 29 Dec 2005 (CET)

----
== Anti Spam Policy ==

I decided to activate some anti spam / vandalism features. Now only logged in users can edit pages.

--[[User:Akw|akw]] 16:11, 17 January 2006 (CET)

== Non-ThinkPad Lenovo laptops ==

Are the new non-ThinkPad C-series Lenovo laptops within scope of this site?

--[[User:Thinker|Thinker]] 14:18, 27 February 2006 (CET)
----

I'd say "NO". They have nothing, and I do mean NOTHING in common with thinkpads.

--[[User:Hmh|hmh]] 18:27, 20 June 2008 (CEST)

== Spam Protection ==

Hi, could we include a [http://meta.wikimedia.org/wiki/Captcha_extensions CAPTCHA extension] to stop these spam posts.

--[[User:Whoopie|Whoopie]] 19:50, 17 June 2006 (CEST)

== Windows 98 ==

Hi, I have just spent ages getting Windows 98SE to work properly on a T30. Some of the drivers that IBM provide are not good, but my T30 is running 98SE quite nicely now.

I would quite like to start a page on installing 98SE and could provide some useful info.

--[[User:dieselnutjob|dieselnutjob]] 21st June 2006

Go for it. Windows information is welcome in this WiKi as long as it does not cause issues with the Linux information (i.e. be organized, keep them separate). Just add a "installing windows 98SE in a T30" page if you want (look at other "installing foo on bar" pages first to get an idea of the proper layout and page naming).

--[[User:Hmh|hmh]] 18:29, 20 June 2008 (CEST)

== Code in articles ==

We have many articles with long scripts, which tend to get very mess and unreadable.

Alternatives:
# Move all scripts to dedicated pages called Code/foo. For example, the huge code block in [[ACPI fan control script#Variable_speed_control_scripts]] goes to [[Code/tp-fancontrol]], with its metdata in the talk page. It is referenced as {{CodeRef|tp-fancontrol}} (that's <tt><nowiki>{{CodeRef|tp-fancontrol}}</nowiki></tt>)..
# Tell people to use an external hosting (http://sf.net, http://pastebin.ca etc.).
# Make Wikimedia support non-image uploads. But then we won't have nice diffs.

Opinions?

--[[User:Thinker|Thinker]] 13:51, 26 July 2006 (CEST)
----

I've fully converted [[ACPI fan control script]] as a test case. What do you think?

--[[User:Thinker|Thinker]] 23:34, 26 July 2006 (CEST)
----

== Benchmarks missing page ==

The benchmarks link on the main menu seems to be broken...

Rgrds

Peter

== Press coverage ==

"In addition, the ThinkPad PC product line has probably had more specific Linux support than any other computer brand. In fact, one of the most useful Linux community sites, ThinkWiki, is devoted to nothing but Linux on the ThinkPad." --[http://www.desktoplinux.com/news/NS7778908329.html desktoplinux.com]

== Exploding Batteries on Thinkpads? ==

Is this worth adding to the news page? Or somewhere else on thinkwiki? Or does a sensationalist forum post not a news item make? (Actually, I just found another mention of it on thinkwiki in [[Battery safety]])

An [http://hardware.slashdot.org/hardware/06/09/16/2236256.shtml article on Slashdot] mentioned in passing an incident where it appears at least one Thinkpad's battery exploded. [http://forums.somethingawful.com/showthread.php?s=&threadid=2069019#post315117641 The forum post reporting the explosion] (scroll down past the huge registration begging) also contains photographs. The laptop is allegedly a T42 or T42p, according to someone who examined the pictures, and while it ''certainly could be'' (it looks similar enough to mine), I don't know if we can postively identify it.
--[[User:Daxelrod|Daniel Axelrod]] 03:05, 18 September 2006 (CEST)

== Google ads ==

I have plans upgrading the hardware of the ThinkWiki server (DualCore SMP machine, more RAM, etc.) for getting faster response times.
This will happen in someday in november.
To pay the monthly fees for this new server, I decided to put some unobtrusive google text-only ads in a new box below the toolbox in the navigation area.
I hope this ads are not too offending. I really dislike ads on websites, but these text-only ads are IMHO an acceptable compromise. Opinions?

--[[User:Akw|akw]] 12:52, 4 October 2006 (CEST)

The ads on the navbar are indeed unobtrusive, and in their current position don't take up any screen real estate, so no objection (despite my dislike for ads). The ad strip at the bottom of the page is (very) slightly annoying, since pressing {{key|End}} now shows a few less lines from the article.

--[[User:Thinker|Thinker]]

Agreed. Go for it. Also, may I humbly suggest that you offer for '''purchase''' and also for '''subscription''' an off-line version of ThinkWiki? I have often needed access to the ThinkWiki data for reference while writing/debugging stuff on the road, and I would also sleep much better knowing I have all this information in a CD near me...

--[[User:Hmh|hmh]] 14:25, 4 October 2006 (CEST)

----

== MediaWiki Upgrade ==

I finally upgraded ThinkWiki to the latest [[Special:Version|MediaWiki 1.8.2]].
This included an update to the database structure. I hope the upgrade will bring a massive speed improvement.
Please report any issues regarding the update.

--[[User:Akw|akw]] 13:27, 23 October 2006 (CEST)

I just tweaked the apache config. This will greatly improve performance, I hope :-)

I also recompiled apache2 with some optimizations. Now the cpu load of the server is significantly lower. <g>

--[[User:Akw|akw]] 15:25, 26 October 2006 (CEST)

----

== VaioWiki ==

Anyone who owns a Sony VAIO please help me building [http://www.vaiowiki.org/ vaiowiki.org] which is a sister project of ThinkWiki, which I just started.
It hast got an independent database, but should have the same structure as ThinkWiki and of course, common articles can just be copied.

--[[User:Akw|akw]] 16:13, 15 March 2007 (CET)

== New user creation enabled again ==

Hi everyone. I just managed to install a captcha system on the new-user-creation. Also the captcha is needed on editing pages with external links in it.
Hope this will help us to get rid of the spam bots.

--[[User:Akw|akw]] 14:47, 9 May 2007 (CEST)

== Sorry for downtime yesterday ==

Yesterday the server experienced the threatful OOM-Killer ('''o'''ut-'''o'''f-'''m'''emory process killer). A memory upgrade (4GB) will be done as soon as possible.

--[[User:Akw|akw]] 07:42, 4 June 2007 (CEST)

== Implement 3-character searches ==

A lot of the content that I place in wikis benefit greatly from the ability to search for three character terms. This is definitely true for technically-oriented wikis where searches for 'AMD', 'CPU', etc. would be regularly entered. In my case, I was looking for 'fan' problems with the 'T40'. AFAIK, these can't be searched on ThinkWiki.

I've copied a snippet from another MediaWiki on the topic in case you're interested and this could help set it up for you...
<pre>
* http://en.wikipedia.org/wiki/Help:Short_words_in_searches
* http://www.mediawiki.org/wiki/Manual:FAQ#...is_a_search_for_a_short_keyword_giving_no_hits.3F
* http://dev.mysql.com/doc/refman/4.1/en/fulltext-fine-tuning.html
* http://dev.mysql.com/doc/refman/4.1/en/using-system-variables.html
* http://dev.mysql.com/doc/refman/4.1/en/option-files.html
* http://dev.mysql.com/doc/refman/4.1/en/mysql-config-wizard-file-location.html
</pre>

'''''(FYI: this is probably a Windows rant, but might be helpful.)'''''

I know no one else cares about this but I still wanted a forum to vent my frustrations..

I've been trying sporadically to get our mediawiki installation to allow us to have three-character search terms. This is to allow us to do searches on stuff such as 'asp', 'iis', 'svn', etc. The default minimum length is set to 4. (This is the mysql fulltext search default - not mediawiki limited.)

Simple matter, right? Lots of documentation on how to do this simple task... Modify a mysql .ini file or two, stop/restart a server and voila (or violas in my case.)

Most of the documentation talks about modifying my.ini files. There are several of these scattered on the mediawikivm file system. I updated them, stopped/started, debugged, etc., and still no change in behavior.

Then some documentation talked about the mysterious my.cnf files. Well, mediawikivm is a Windows 2003 box. There are zero (0 - zilch - nada) .cnf files on the system. There were some strange 'my' files identified as 'SpeedDial' but they didn't allow any operations.

I don't care how you set your Explorer File Preferences, there are none. Not to be easily cast aside, I rooted around some more in Google and found references to a magical registry entry named 'nevershowext' which precludes any Windows operations from showing the extension or allowing Edit/etc operations.

So, after modifying around 10 registry entries, finding the my.cnf file where it should be, changing the "ft_min_word_len=3" entry, we now have valid searches for those important/stupid cases.

==RSS feed ==
there is a bug on the RSS feed. when clicking on the RSS self discovery icon in the address bar of firefox on the [[Recentchanges]] page the following error appears:

XML Parsing Error: xml declaration not at start of external entity
Location: http://www.thinkwiki.org/index.php?title=Special:Recentchanges&feed=atom
Line Number 2, Column 1:<?xml version="1.0" encoding="utf-8"?>

The XML declaration must be on the first line and start at the first character position of the line.

== How does this site's search work? ==

I'd really appreciate info on getting a Google-driven site search working like on this site. I see Special:GoogleFind in the url but can't find info on that. I presume it's not [http://www.mediawiki.org/wiki/Extension:Google_Custom_Search_Engine Google Custom Search Engine]. Many thanks! --[[User:Chriswaterguy|Chriswaterguy]] 04:57, 29 April 2008 (CEST)

User:Low

2008-12-11T11:48:51Z

Low: /* about the System */

== about Low ==
I'm a linux noob, really. Though I spent 5 years maintaining a huge website, I had little exposure to the system itself. At work I'm 50% on HP-UX, also as a user. I learn as I progress.
== about the System ==
'''R60''' Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz, ATI X1400

'''Slackware 12.1''' (pretty much 'vanilla' - only added the fglrx package for the ATI - and as you might have guessed: after reinstalling and recompiling the kernel about 20 times till I found out that for SATA you need some SCSI modules...)

'''fvwm''' 2.5.26

User:Low

2008-12-11T11:47:56Z

Low: â†Created page with '== about Low == I'm a linux noob, really. Though I spent 5 years maintaining a huge website, I had little exposure to the system itself. At work I'm 50% on HP-UX, also as ...'

== about Low ==
I'm a linux noob, really. Though I spent 5 years maintaining a huge website, I had little exposure to the system itself. At work I'm 50% on HP-UX, also as a user. I learn as I progress.
== about the System ==
'''R60''' Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz, ATI X1400
'''Slackware 12.1''' (pretty much 'vanilla' - only added the fglrx package for the ATI - and as you might have guessed: after reinstalling and recompiling the kernel about 20 times till I found out that for SATA you need some SCSI modules...)
'''fvwm''' 2.5.26

Talk:How to get special keys to work

2008-12-11T11:18:32Z

Low: /* Bind Fn 12 say to F34 */

__TOC__

The xmodmap step doesn't seem to work when using the "kdb" driver of xorg. Here are the changes I needed to make to my setup to get the "back" and "forward" keys to work (in diff -u format);

--- xkb/symbols/inet.oud 2004-12-01 08:36:04.000000000 +0100
+++ xkb/symbols/inet 2005-03-08 19:59:32.587636120 +0100
@@ -1875,6 +1875,16 @@
key <I76> { [ XF86AudioLowerVolume ] };
};

+// IBM ThinkPad 41 Internet Keys
+
+partial alphanumeric_keys
+xkb_symbols "tp41" {
+ name[Group1]= "IBM ThinkPad 41 Internet Keys";
+
+ key <I69> { [ F22 ] };
+ key <I6A> { [ F21 ] };
+};
+
// Trust

partial alphanumeric_keys 

--- xkb/rules/xorg.lst.oud 2004-12-01 08:36:05.000000000 +0100
+++ xkb/rules/xorg.lst 2005-03-07 20:55:21.000000000 +0100
@@ -97,6 +97,7 @@
sven SVEN Ergonomic 2500
symplon Symplon PaceBook (tablet PC)
toshiba_s3000 Toshiba Satellite S3000
+ tp41 IBM ThinkPad 41 Internet Keys
trust Trust Wireless Keyboard Classic
trustda Trust Direct Access Keyboard
yahoo Yahoo! Internet Keyboard

--- xkb/rules/xorg.oud 2004-12-01 08:36:05.000000000 +0100
+++ xkb/rules/xorg 2005-03-07 20:45:59.000000000 +0100
@@ -120,7 +120,7 @@
qtronix \
samsung4500 samsung4510 \
sk1300 sk2500 sk6200 sk7100 \
- sven symplon toshiba_s3000 trust trustda yahoo
+ sven symplon toshiba_s3000 tp41 trust trustda yahoo

! model = symbols
$inetkbds = +inet(%m)

--- xkb/rules/xorg.xml.oud 2004-12-01 08:36:05.000000000 +0100
+++ xkb/rules/xorg.xml 2005-03-07 20:52:35.000000000 +0100
@@ -975,6 +975,13 @@
</model>
<model>
<configItem>
+ <name>tp41</name>
+ <description>IBM Thinkpad 41 Internet Keys</description>
+ <description xml:lang="nl">IBM ThinkPad 41 internet toetsen</description>
+ </configItem>
+ </model>
+ <model>
+ <configItem>
<name>trust</name>
<description>Trust Wireless Keyboard Classic</description>
<description xml:lang="fr">clavier classique Trust Wireless</description>

Do not forget to add something like "+inet(tp41)" to /etc/X11/xorg.conf:
(...)
Option "XkbLayout" "us_intl+inet(tp41)"
(...)

----
I've filled a [https://bugs.freedesktop.org/show_bug.cgi?id=9779 bug] to freedesktop bugzilla, which has been applied. It adds inet(thinkpad) symbols with <I69>/<I6A> keys and adds thinkpad to $inetkbds list. So, Forward/Back keys will work out-of-box with thinkpad XkbModel. However, thinkpadintl model is not supported... --[[User:Raorn|Raorn]] 13:25, 27 January 2007 (CET)

== Not T41 specific ==

These keys are hardly T41 specific, they can also be found on the T30, T40, T42 and I'm sure several other ThinkPads in the X, R and G lineup.

Actually, the above patches could be completed with the information of the other special keys found on some Thinkpads (which is listed in [[How_to_get_special_keys_to_work#xmodmap_configuration]]) and submitted as a request for enhancement with [http://bugs.freedesktop.org xorg's bugzilla]. However, firefox doesn't yet recognize keysyms like XF86Back, XF86Forward, so then firefox still needs to be patched manually (unless an enhancement is requested for firefox too).

=== XF86Back in Firefox ===
I found that XF86Back and XF86Forward work for me with firefox. I was able to use the following in
/usr/lib/firefox/chrome/browser/content/browser/browser.xul
<key id="goBackKb" keycode="XF86Back" command="Browser:Back" />
<key id="goForwardKb" keycode="XF86Forward" command="Browser:Forward" />

My firefox version is Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.3) Gecko/20061201 Firefox/2.0.0.3 (Ubuntu-feisty)

----

This also works for me, but "XF86Back" seems to be *the same* (toggles the same command, but only in FireFox) as [Alt Gr]-Key on German keyboards, even if xev shows nothing like this. Bug in FireFox? Therefor I have stick to the F19/F20 workaround.

--[[User:BDKMPSS|BDKMPSS]] June 04 2007
----

== Fake ACPI events? ==

Not all keys generate ACPI events. Maybe it is feasible to have the ibm-acpi module check the CMOS (instead of having tpb checking /dev/nvram) and generate fake ACPI events for those keys. Even if it is feasible, that is probably way to hacky for a kernel module ... Still, it would be nice to only have to use scripts triggered by ACPI events and not both scripts for ACPI events and scripts for tpb.

----
I think something like this is possible with ibm-acpi 0.10 already. It provides a proc file from which you can derive a table of CMOS states. You'd only have to figure the who is who of CMOS bits and write a daemon (or daemon like shell script) checking them regularly. This should be about what you suggest since tpb does the same thing with the bios ram. Of course generating ACPI events can not be done like that (or can it?), but you could trigger the ACPI action scripts directly then.

[[User:Wyrfel|Wyrfel]] 01:02, 14 Mar 2005 (CET)
----

It may be possible (I have a 770x, so don't have the special keys) to add the keys as real ACPI events, by altering the DSDT. I've done this to enable ACPI events for Fn-(every labelled F key),Home,End,PgUp,PgDn on mine, and they aren't labelled with anything physically (no thinklight and physical brightness control). The Embedded Controller reports all events, including keys, by calling one of the _Qxx functions (you'll find a whole pile in the sourcecode for the DSDT). If you then insert a fucntion in the same scope as the others like:-
Method (_Q12, 0, NotSerialized) { \_SB.HKEY.MHKQ (0x1003) } //Fn-F3
when executed, ibm-acpi will then report an acpi event numbered 0x0001003. You should find some functions, e.g. _Q1B For Fn-F12 identical to this.

I found some IBM DSDT's had functions that made MKHQ calls for EC functions _Q63, _Q64, _Q4E, _Q4F, but did nothing on mine---maybe these are a good starting point. Add a whole pile, and see if you get lucky! (At your own risk, of course... :/ But it should be pretty safe).

Yes, the above sounds pretty identical to tpb, except with /proc/ibm/ecdump instead of /dev/nvram. The above works very nicely, however there's luck involved in finding the right number, even if it exists!

[[User:lentinj|lentinj]]

----

Fn+F6 does not seem to generate an event on t41p even if the mask is set to 0xffff and experimental=1 is passed to ibm_acpi
[[User:tf|tf]]

----

==Bind Fn to super or hyper ==

Hello

Is it possible to bind Fn via Xmodmap to a key modifier such as hyper or super? Thanks
[[User:Oub|Oub]] 13:14, 6 February 2006 (CET):
----
I doubt it. The event for the {{key|Fn}} key is generated at release (as opposed to holding it where it serves it's usual special function). Hence you can't use it as a modifier. [[User:Wyrfel|Wyrfel]] 22:52, 6 February 2006 (CET)
----
I have added a paragraph how to get around the issue that {{key|Fn}} is not working with other key combos than the ones intended. Mebbe that helps you.
--[[User:Low|Low]] 12:09, 11 December 2008 (CET)
----

==Bind Fn 12 say to F34 ==
Thanks Wyrfel for your reply, in order to display my question better, I use a new header: can I bind all the Fn Fx to hay F34 and the like?
[[User:Oub|Oub]] 21:33, 10 February 2006 (CET):
----
You can do this with all key '''combinations''' that support xmodmap (see the table). That means you can't do it with {{key|Fn}}}{{key|F12}}, because that combination doesn't generate a key event at all (it only generates an APM/ACPI event. Hence there is nothing vor xmodmap to remap.

But what is your wider focus goal? I'm sure that what you want to do can be realized, anyway: You can write an ACPI script and event file for {{key|Fn}}{{key|F12}} and have the script start some tool that sends a F34 key to the X server. I'm sure this is possible.

[[User:Wyrfel|Wyrfel]] 00:03, 11 February 2006 (CET)
----
Hi,

{{key|Fn}} does not accept other key combos than the acpi ones (e.g. {{key|Fn}}+{{key|F4}}). However you can assign it to be CapsLock, and use the {{key|CapsLock}} then for the purpose of having key combos. See the paragraph about enabling fast NumPadding:

[[How to get special keys to work#NumPad (KeyPad) keys access by a key combination]]

--[[User:Low|Low]] 12:18, 11 December 2008 (CET)
----

==Can't bind Fn 12 ==

Hello

I am using a R51 and I have compiled ibm-acpi monolithic in the kernel (not as module, maybe this is a mistake?). Anyway, I am using
suspend2, which I compiled in the kernel as well. Now I have bound
''to hibernate '' first to Fn 4, with the following script
event=button[ /]sleep
action=/usr/local/sbin/mihibernate

This works fine. Now I want to do the same for Fn12, so following the key table I did:

event=button[/] ibm/hotkey HKEY 00000080 0000100c
action=/usr/local/sbin/mihibernate

But that does not work. What is the problem? I tried even
echo enable,0xffff >/proc/acpi/ibm/hotkey
without success. Can anybody help me?
[[User:Oub|Oub]] 16:27, 4 March 2006 (CET):
----
The proper event line is
event=ibm/hotkey HKEY 00000080 0000100c
.

Also, make sure that you are not using [thinkpad-acpi]. If <tt>event=button[ /]sleep</tt> works for {{key|Fn}}{{key|F4}}, that indicates that you do. It might block the ibm-acpi driver. Check your kernel config and disable any thinkpad acpi driver except ibm-acpi.

[[User:Wyrfel|Wyrfel]] 21:58, 4 March 2006 (CET)
----

:Hello
:
:It is odd, I am pretty sure, that I do not use [thinkpad-acpi], but [ibm-acpi], although event=button[ /]sleep works for FnF4, in any case I found out that
:
: event=(button/power|ibm/hotkey HKEY 00000080 0000100c)
:
:Works! What do you think of adding a subsection to the [[How to get special keys to work]] page, with some examples, like the following:
:
:from ''/etc/acpi/events/battery'':
event=(button/power|ibm/hotkey HKEY 00000080 0000100c)
action=/usr/local/sbin/hibernate
:from ''/etc/acpi/events/lid''
event=button/lid
action=/usr/local/bin/mysleepram
:from ''/etc/acpi/events/sleepbtn''
event=(button/sleep|ibm/hotkey HKEY 00000080 00001004)
action=/usr/local/bin/mysleepram
:
:(Also ''event=button/sleep '' works for me)
:and then restart acpi:
:
/etc/init.d/acpid restart
:
:[[User:Oub|Oub]] 13:22, 5 March 2006 (CET):
----
What you do with
event=(button/power|ibm/hotkey HKEY 00000080 0000100c)
is to make a logical nonexclusive OR between
event=button/power
and
event=ibm/hotkey HKEY 00000080 0000100c
. If the first works, the whole thing works. So that's pretty logical.

Please, do a {{cmdroot|dmesg <nowiki>|</nowiki> grep thinkpad-acpi}} and do a {{cmdroot|dmesg <nowiki>|</nowiki> grep ibm-acpi}}. What is the output in either case?

I see no sense in putting examples to the page that only confuse people because they are not correct. ibm-acpi generates the events listed in the table and nothing else. If you get something like <tt>button/sleep</tt> it's not ibm-acpi generating it. You are running Debian, right? Let's hope they didn't patch the driver to generate different events.

Also, you can always do {{cmdroot|tail -f /var/log/acpid}} to have a life view of the generated events.

I am pretty sure that you are using thinkpad-acpi or - if not so - that something else must interfere.

[[User:Wyrfel|Wyrfel]] 04:49, 6 March 2006 (CET)

----

:Hi
:
:Ok I admit everything is very odd. For the start, I seem to use
:ibm-acpi. As I said I am Debian, but I compiled my own kernel :(2.6.10)(but not as a module, maybe this was a bad idee??) and I used :the ibm-acpi driver which comes shipped with that kernel. I did not :download the driver from the official http://ibm-acpi.sourceforge.net/ :site. Here is the output of
:
:dmesg | grep acpi
Kernel command line: ro root=/dev/hda6 acpi_sleep=s3_bios
tbxface-0118 [02] acpi_load_tables : ACPI Tables successfully acquired
evxfevnt-0094 [03] acpi_enable : Transition to ACPI mode successful
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [df6ddaa8]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c1464768]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c1467328]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c146bba8]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c146b628]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c146b3e8]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c146b268]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c146dde8]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c1470d68]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c1470568]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c14719a8]
ibm_acpi: IBM ThinkPad ACPI Extras v0.8
ibm_acpi: http://ibm-acpi.sf.net/
acpi_bus-0081 [08] acpi_bus_get_device : Error getting context for object [c1467328]
ibm_acpi: dock device not present

:I don't understand the errors but anyway. Now the odd thing is that indeed the following works
:
event=button[ /]sleep
action=/usr/local/sbin/hibernate
:but
event=button[/]sleep
action=/usr/local/sbin/hibernate

:Does not work. But from what you said, using the ibm_acpi neither of '''these strings ''' should work? So I don't understand what is going on. [[User:Oub|Oub]] 20:28, 6 March 2006 (CET):

----

With any reasonably new kernel (2.6.16 in Thinkpad terms :-) ) and a good DSDT (say, like the one that comes inside the T43), you can get two classes of events: ACPI events (as in native ACPI events), and ibm-acpi hotkey events.

This has nothing to do with thinkpad-acpi.

Look under /proc/acpi/buttons. If you have sleep and maybe hibernate/suspend in there (I don't know how fn+f12 is called when properly supported through ACPI DSDT, the T43 doesn't support it like that), then your Thinkpad can, and will generate proper ACPI events without the help of ibm-acpi. This is valid for a complete ACPI config of kernel 2.6.16 with all modules loaded.

And it will generate regular ibm-acpi hotkey events if you enable the feature and use the correct mask, which may or may not confuse the thinkpad (I am not sure the correct DSDT handlers the BIOS expect to run are called in this case).

-- [[User:Hmh|hmh]] 2006-05-26 13:20 UTC

==Turn on/off Wifi on Fn5 ==
Hi

I hope this is the last question. I use a crude way to activate and deactivate my wificard: I remove and insert the relevant modules, with 2 simple scripts. Now the question is how can I bind Fn5 so, that it turns on and off the wificard? With my approach I need to fire up two scripts, and that I cannot bind to one button. Thanks
[[User:Oub|Oub]] 17:57, 5 March 2006 (CET):

Try a {{cmdroot|cat /proc/acpi/ibm/bluetooth}}. Maybe it returns the state. If not, the other way would be to check if the USB bluetooth controller device is listed in {{path|/proc/bus/usb}} somewhere. It shouldn't be there if bluetooth is switched off and should be there if it is on.

[[User:Wyrfel|Wyrfel]] 04:49, 6 March 2006 (CET)
----

==Split page?==
This page is getting too long. Maybe we should split it. I'd suggest moving the "Example applications" to a seperate page.

[[User:Pebolle|Paul Bolle]] 22:46, 3 April 2006 (CEST)

==DIY Firefox 1.5 xpi==
Here's how I maneged a Firefox 1.5 compatible plugin (source: google). Note that the wiki eats some of the xml tags (so look at the source too)

$ ls -1R tp41.xpi
tp41.xpi/:
chrome
chrome.manifest
install.rdf

tp41.xpi/chrome:
content

tp41.xpi/chrome/content:
tp41keysOverlay.xul

$ cat tp41.xpi/chrome.manifest
content tp41keys chrome/content/
overlay chrome://browser/content/browser.xul chrome://tp41keys/content/tp41keysOverlay.xul

$ cat tp41.xpi/install.rdf
<?xml version="1.0"?>

<RDF xmlns="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:em="http://www.mozilla.org/2004/em-rdf#">

<Description about="urn:mozilla:install-manifest">
<em:id>tp41keys@tp41keys.org</em:id>
<em:version>1.0</em:version>
<em:type>2</em:type>


<em:targetApplication>
<Description>
<em:id>{ec8030f7-c20a-464f-9b0e-13a3a9e97384}</em:id>
<em:minVersion>1.0+</em:minVersion>
<em:maxVersion>1.5.0.*</em:maxVersion>
</Description>
</em:targetApplication>


<em:name>IBM ThinkPad 41 Keys</em:name>
<em:description>Two Browser Navigation Keys</em:description>
<em:creator>Paul Bolle</em:creator>
<em:homepageURL>http://www.example.com/tp41keys.xpi</em:homepageURL>
</Description>
</RDF>

$ cat tp41.xpi/chrome/content/tp41keysOverlay.xul
<?xml version='1.0'?>
<!DOCTYPE overlay>

<overlay id='tp41keysOverlay'
xmlns='http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul'>

<keyset id='mainKeyset'>
<key id='tp41BackKey' keycode='VK_F21' command='Browser:Back' />
<key id='tp41ForwardKey' keycode='VK_F22' command='Browser:Forward' />
</keyset>

</overlay>

$ cat .mozilla/firefox/*.default/extensions/tp41keys\@tp41keys.org
~/tp41.xpi

==ibm-acpi hint==

I would like to add a hint under ibm-acpi to enable all hotkeys at boot, but I can not seem to get the HINT template to work:

<nowiki>{{HINT|To enable all hotkeys on boot in debian, create the file /etc/modprobe.d/ibm_acpi containing 'options ibm_acpi hotkey=enable,0xffff'}}</nowiki>

It outputs:

{{HINT|To enable all hotkeys on boot in debian, create the file /etc/modprobe.d/ibm_acpi containing 'options ibm_acpi hotkey=enable,0xffff'}}

Any ideas on how to get this to work? Also, does it even belong in the page?

--[[User:Paul Strefling|Paul Strefling]] 23:22, 10 August 2006 (CEST)

If you use ''ibm-apci'' as a module and have {{path|/proc}} filesystem enabled, you can tune it by
adding to {{path|/etc/modules.d/ibm_acpi}}:

post-install ibm-acpi /bin/echo enable,0x00d0 > /proc/acpi/ibm/hotkey
I added it after ''alias ibm-acpi ibm_acpi''. I'm not sure - if the order make sence. Params can be differ - it is an example.

Also works fine with {{cmdroot|modprobe}} (don't forget to run {{cmdroot|modules-update}} after editing {{path|/etc/modules.d/*}}).

(tested on Gentoo with vanilla kernel).

==Lock Screen with hotkey on models before T60==

In case it's of interest, it's possible to simulate the "lock screen" (Fn+F2) function of T60s on prior models. I wrote a little [http://forums.gentoo.org/viewtopic-p-3814885.html HOWTO] on the Gentoo forums explaining how to configure Fn+F3 to fire up xscreensaver instead of blanking the screen (though this could easily be changed to Fn+F2 instead). This was for my T42 but I presume it'd work on other models too. Perhaps it'd be worth mentioning in the Remarks column of the Fn+F2 row of the table at the top of the article? --[[User:Waveform|Waveform]] 03:42, 2 January 2007 (CET)

== Toggle touchpad with Fn-F8 ==

I often want to switch off the touchpad, since I tend to produce spurious taps while typing, sending my cursor to random places on the screen. To toggle touchpad operation, I use this little script:

#!/bin/sh
#
# toggle touchpad operation
# August 2, 2006
# (c) Michael Schmuker
#
if synclient -l | grep TouchpadOff | grep -q 0; then
synclient TouchpadOff=1;
kdialog --passivepopup "Touchpad is OFF" 2;
else
synclient TouchpadOff=0;
kdialog --passivepopup "Touchpad is ON" 2;
fi

This checks if the touchpad is on or off, and toggles its state accordingly. Note that it uses kdialog to display a notification on the desktop. This obviously works only with KDE, but there certainly is a similar mechanism for other desktop environments.

Now this script needs to be bound to the Fn-F8-key. On Suse 10.2, the ACPI-events produced by the thinkpad special keys are processed by powersaved. You need to edit the file {{path|/usr/lib/powersave/scripts/thinkpad_acpi_events}}.
There, thinkpad-ACPI events are bound to their actions. Where it comes to Fn-F8, just change it to the following (supposed you put the above script to {{path|/usr/local/bin/toggleTouchpad}} and make it executable):
4104) HOTKEY="Fn+F8" #toggle touchpad on/off
/usr/local/bin/toggleTouchpad
;;
Save the file, and the next time you press Fn-F8 you will toggle your touchpad.

Unfortunately, the notification via kdialog is not working when toggling with Fn-F8. If anyone finds out how to solve this: Let us know!

'''Possible Solutions:'''

1. You can instead use syndaemon, which can turn off the touchpad for a brief period while you are typing.

2. All acpi events are run as root. Therefore, to enable the kdialog, you will need to incorporate a script to determine which user is running on DISPLAY :0.0; something like the following should work (put it in your acpi file)
if ps -e | grep -q -E '(enlightenment|kwin|dwm)'; then
X_USER=`/usr/bin/who | /usr/bin/sed -n "s,^$.*$:0 .*$,\1,p"`
X_USER=${X_USER/ /};
export DISPLAY=:0.0
fi
if [ -n "$X_USER" ]; then su $X_USER -c "/usr/local/bin/toggleTouchpad";
else /usr/local/bin/toggleTouchpad;
fi
--[[User:Ppurka|Ppurka]] 18:43, 14 September 2007 (UTC)

== What about older machines? ==

On the 600X, Fn+PgUp and Fn+PgDn control speaker volume and Fn+Backspace toggles speaker mute. In addition, Fn+F2 is shows a battery icon and the manual states that it brings up a battery monitor. It hasn't worked since Windows 95. Fn+F11 shows a dripping tap and is meant to select a power mode. Fn+F8 has no icon but toggles screen expansion.

On the 750P, Fn+F5 and Fn+F6 control speaker volume, and I think Fn+F2 and Fn+F11 show the same icons as the 600X. However, that machine certainly doesn't have ACPI. Fn+F8 toggles screen inversion (black shows as white and vice-versa) on the monochrome models and Fn+F9 toggles brightness inversion (normal characters become bright and bright characters become normal). Those two only affect the internal LCD and not the signal on the VGA connector.

--[[User:Whizkid|Whizkid]] 19:32, 27 November 2007 (UTC)

Please add that information to the [[Default meanings of special keys]] page, including the description of the icons and functions. As for how to use these keys, it depends. How well does thinkpad-acpi work on the 600X and 750P? If it doesn't work at all, then you have to resort to tpb, which may have no idea how to access these keys in NVRAM :-(

--[[User:Hmh|hmh]] 14:18, 30 November 2007 (UTC)

I've updated the descriptions of functions on that page for 750P, 560E and 600X. There are no descriptions of icons anywhere on that page. An example to start with would be nice. The 750 family doesn't have ACPI at all.
--[[User:Whizkid|Whizkid]] 14:09, 25 December 2007 (UTC)

== ThinkVantage button not recognized by xev under Hardy ==

Hello,

I would like to set up the ThinkVantage button as XF86LaunchA, but I simply can't as it doesn't give any signal in xev. Any ideas how could I fix this?

Thanks, [[User:Nagyv|Nagyv]] 22:54, 3 July 2008 (CEST)

As the button is no "real keyboard button" it does not generate a keycode, but an acpi event (maybe thinkpad_acpi is needed for it to work) which you can set up to do what ever you want (well, not everything). see the article.

--[[User:BDKMPSS|BDKMPSS]] 23:45, 3 July 2008 (CEST)

Thank, this worked. I only had to add a new file under /etc/acpi/events. As there were many working examples, it was easy to write my own. Finally, I had to restart acpid.

thanks, [[User:Nagyv|Nagyv]]

Talk:How to get special keys to work

2008-12-11T11:09:45Z

Low: /* Bind Fn to super or hyper */

__TOC__

The xmodmap step doesn't seem to work when using the "kdb" driver of xorg. Here are the changes I needed to make to my setup to get the "back" and "forward" keys to work (in diff -u format);

--- xkb/symbols/inet.oud 2004-12-01 08:36:04.000000000 +0100
+++ xkb/symbols/inet 2005-03-08 19:59:32.587636120 +0100
@@ -1875,6 +1875,16 @@
key <I76> { [ XF86AudioLowerVolume ] };
};

+// IBM ThinkPad 41 Internet Keys
+
+partial alphanumeric_keys
+xkb_symbols "tp41" {
+ name[Group1]= "IBM ThinkPad 41 Internet Keys";
+
+ key <I69> { [ F22 ] };
+ key <I6A> { [ F21 ] };
+};
+
// Trust

partial alphanumeric_keys 

--- xkb/rules/xorg.lst.oud 2004-12-01 08:36:05.000000000 +0100
+++ xkb/rules/xorg.lst 2005-03-07 20:55:21.000000000 +0100
@@ -97,6 +97,7 @@
sven SVEN Ergonomic 2500
symplon Symplon PaceBook (tablet PC)
toshiba_s3000 Toshiba Satellite S3000
+ tp41 IBM ThinkPad 41 Internet Keys
trust Trust Wireless Keyboard Classic
trustda Trust Direct Access Keyboard
yahoo Yahoo! Internet Keyboard

--- xkb/rules/xorg.oud 2004-12-01 08:36:05.000000000 +0100
+++ xkb/rules/xorg 2005-03-07 20:45:59.000000000 +0100
@@ -120,7 +120,7 @@
qtronix \
samsung4500 samsung4510 \
sk1300 sk2500 sk6200 sk7100 \
- sven symplon toshiba_s3000 trust trustda yahoo
+ sven symplon toshiba_s3000 tp41 trust trustda yahoo

! model = symbols
$inetkbds = +inet(%m)

--- xkb/rules/xorg.xml.oud 2004-12-01 08:36:05.000000000 +0100
+++ xkb/rules/xorg.xml 2005-03-07 20:52:35.000000000 +0100
@@ -975,6 +975,13 @@
</model>
<model>
<configItem>
+ <name>tp41</name>
+ <description>IBM Thinkpad 41 Internet Keys</description>
+ <description xml:lang="nl">IBM ThinkPad 41 internet toetsen</description>
+ </configItem>
+ </model>
+ <model>
+ <configItem>
<name>trust</name>
<description>Trust Wireless Keyboard Classic</description>
<description xml:lang="fr">clavier classique Trust Wireless</description>

Do not forget to add something like "+inet(tp41)" to /etc/X11/xorg.conf:
(...)
Option "XkbLayout" "us_intl+inet(tp41)"
(...)

----
I've filled a [https://bugs.freedesktop.org/show_bug.cgi?id=9779 bug] to freedesktop bugzilla, which has been applied. It adds inet(thinkpad) symbols with <I69>/<I6A> keys and adds thinkpad to $inetkbds list. So, Forward/Back keys will work out-of-box with thinkpad XkbModel. However, thinkpadintl model is not supported... --[[User:Raorn|Raorn]] 13:25, 27 January 2007 (CET)

== Not T41 specific ==

These keys are hardly T41 specific, they can also be found on the T30, T40, T42 and I'm sure several other ThinkPads in the X, R and G lineup.

Actually, the above patches could be completed with the information of the other special keys found on some Thinkpads (which is listed in [[How_to_get_special_keys_to_work#xmodmap_configuration]]) and submitted as a request for enhancement with [http://bugs.freedesktop.org xorg's bugzilla]. However, firefox doesn't yet recognize keysyms like XF86Back, XF86Forward, so then firefox still needs to be patched manually (unless an enhancement is requested for firefox too).

=== XF86Back in Firefox ===
I found that XF86Back and XF86Forward work for me with firefox. I was able to use the following in
/usr/lib/firefox/chrome/browser/content/browser/browser.xul
<key id="goBackKb" keycode="XF86Back" command="Browser:Back" />
<key id="goForwardKb" keycode="XF86Forward" command="Browser:Forward" />

My firefox version is Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.3) Gecko/20061201 Firefox/2.0.0.3 (Ubuntu-feisty)

----

This also works for me, but "XF86Back" seems to be *the same* (toggles the same command, but only in FireFox) as [Alt Gr]-Key on German keyboards, even if xev shows nothing like this. Bug in FireFox? Therefor I have stick to the F19/F20 workaround.

--[[User:BDKMPSS|BDKMPSS]] June 04 2007
----

== Fake ACPI events? ==

Not all keys generate ACPI events. Maybe it is feasible to have the ibm-acpi module check the CMOS (instead of having tpb checking /dev/nvram) and generate fake ACPI events for those keys. Even if it is feasible, that is probably way to hacky for a kernel module ... Still, it would be nice to only have to use scripts triggered by ACPI events and not both scripts for ACPI events and scripts for tpb.

----
I think something like this is possible with ibm-acpi 0.10 already. It provides a proc file from which you can derive a table of CMOS states. You'd only have to figure the who is who of CMOS bits and write a daemon (or daemon like shell script) checking them regularly. This should be about what you suggest since tpb does the same thing with the bios ram. Of course generating ACPI events can not be done like that (or can it?), but you could trigger the ACPI action scripts directly then.

[[User:Wyrfel|Wyrfel]] 01:02, 14 Mar 2005 (CET)
----

It may be possible (I have a 770x, so don't have the special keys) to add the keys as real ACPI events, by altering the DSDT. I've done this to enable ACPI events for Fn-(every labelled F key),Home,End,PgUp,PgDn on mine, and they aren't labelled with anything physically (no thinklight and physical brightness control). The Embedded Controller reports all events, including keys, by calling one of the _Qxx functions (you'll find a whole pile in the sourcecode for the DSDT). If you then insert a fucntion in the same scope as the others like:-
Method (_Q12, 0, NotSerialized) { \_SB.HKEY.MHKQ (0x1003) } //Fn-F3
when executed, ibm-acpi will then report an acpi event numbered 0x0001003. You should find some functions, e.g. _Q1B For Fn-F12 identical to this.

I found some IBM DSDT's had functions that made MKHQ calls for EC functions _Q63, _Q64, _Q4E, _Q4F, but did nothing on mine---maybe these are a good starting point. Add a whole pile, and see if you get lucky! (At your own risk, of course... :/ But it should be pretty safe).

Yes, the above sounds pretty identical to tpb, except with /proc/ibm/ecdump instead of /dev/nvram. The above works very nicely, however there's luck involved in finding the right number, even if it exists!

[[User:lentinj|lentinj]]

----

Fn+F6 does not seem to generate an event on t41p even if the mask is set to 0xffff and experimental=1 is passed to ibm_acpi
[[User:tf|tf]]

----

==Bind Fn to super or hyper ==

Hello

Is it possible to bind Fn via Xmodmap to a key modifier such as hyper or super? Thanks
[[User:Oub|Oub]] 13:14, 6 February 2006 (CET):
----
I doubt it. The event for the {{key|Fn}} key is generated at release (as opposed to holding it where it serves it's usual special function). Hence you can't use it as a modifier. [[User:Wyrfel|Wyrfel]] 22:52, 6 February 2006 (CET)
----
I have added a paragraph how to get around the issue that {{key|Fn}} is not working with other key combos than the ones intended. Mebbe that helps you.
--[[User:Low|Low]] 12:09, 11 December 2008 (CET)
----

==Bind Fn 12 say to F34 ==
Thanks Wyrfel for your reply, in order to display my question better, I use a new header: can I bind all the Fn Fx to hay F34 and the like?
[[User:Oub|Oub]] 21:33, 10 February 2006 (CET):
----
You can do this with all key '''combinations''' that support xmodmap (see the table). That means you can't do it with {{key|Fn}}}{{key|F12}}, because that combination doesn't generate a key event at all (it only generates an APM/ACPI event. Hence there is nothing vor xmodmap to remap.

But what is your wider focus goal? I'm sure that what you want to do can be realized, anyway: You can write an ACPI script and event file for {{key|Fn}}{{key|F12}} and have the script start some tool that sends a F34 key to the X server. I'm sure this is possible.

[[User:Wyrfel|Wyrfel]] 00:03, 11 February 2006 (CET)
----
==Can't bind Fn 12 ==

Hello

I am using a R51 and I have compiled ibm-acpi monolithic in the kernel (not as module, maybe this is a mistake?). Anyway, I am using
suspend2, which I compiled in the kernel as well. Now I have bound
''to hibernate '' first to Fn 4, with the following script
event=button[ /]sleep
action=/usr/local/sbin/mihibernate

This works fine. Now I want to do the same for Fn12, so following the key table I did:

event=button[/] ibm/hotkey HKEY 00000080 0000100c
action=/usr/local/sbin/mihibernate

But that does not work. What is the problem? I tried even
echo enable,0xffff >/proc/acpi/ibm/hotkey
without success. Can anybody help me?
[[User:Oub|Oub]] 16:27, 4 March 2006 (CET):
----
The proper event line is
event=ibm/hotkey HKEY 00000080 0000100c
.

Also, make sure that you are not using [thinkpad-acpi]. If <tt>event=button[ /]sleep</tt> works for {{key|Fn}}{{key|F4}}, that indicates that you do. It might block the ibm-acpi driver. Check your kernel config and disable any thinkpad acpi driver except ibm-acpi.

[[User:Wyrfel|Wyrfel]] 21:58, 4 March 2006 (CET)
----

:Hello
:
:It is odd, I am pretty sure, that I do not use [thinkpad-acpi], but [ibm-acpi], although event=button[ /]sleep works for FnF4, in any case I found out that
:
: event=(button/power|ibm/hotkey HKEY 00000080 0000100c)
:
:Works! What do you think of adding a subsection to the [[How to get special keys to work]] page, with some examples, like the following:
:
:from ''/etc/acpi/events/battery'':
event=(button/power|ibm/hotkey HKEY 00000080 0000100c)
action=/usr/local/sbin/hibernate
:from ''/etc/acpi/events/lid''
event=button/lid
action=/usr/local/bin/mysleepram
:from ''/etc/acpi/events/sleepbtn''
event=(button/sleep|ibm/hotkey HKEY 00000080 00001004)
action=/usr/local/bin/mysleepram
:
:(Also ''event=button/sleep '' works for me)
:and then restart acpi:
:
/etc/init.d/acpid restart
:
:[[User:Oub|Oub]] 13:22, 5 March 2006 (CET):
----
What you do with
event=(button/power|ibm/hotkey HKEY 00000080 0000100c)
is to make a logical nonexclusive OR between
event=button/power
and
event=ibm/hotkey HKEY 00000080 0000100c
. If the first works, the whole thing works. So that's pretty logical.

Please, do a {{cmdroot|dmesg <nowiki>|</nowiki> grep thinkpad-acpi}} and do a {{cmdroot|dmesg <nowiki>|</nowiki> grep ibm-acpi}}. What is the output in either case?

I see no sense in putting examples to the page that only confuse people because they are not correct. ibm-acpi generates the events listed in the table and nothing else. If you get something like <tt>button/sleep</tt> it's not ibm-acpi generating it. You are running Debian, right? Let's hope they didn't patch the driver to generate different events.

Also, you can always do {{cmdroot|tail -f /var/log/acpid}} to have a life view of the generated events.

I am pretty sure that you are using thinkpad-acpi or - if not so - that something else must interfere.

[[User:Wyrfel|Wyrfel]] 04:49, 6 March 2006 (CET)

----

:Hi
:
:Ok I admit everything is very odd. For the start, I seem to use
:ibm-acpi. As I said I am Debian, but I compiled my own kernel :(2.6.10)(but not as a module, maybe this was a bad idee??) and I used :the ibm-acpi driver which comes shipped with that kernel. I did not :download the driver from the official http://ibm-acpi.sourceforge.net/ :site. Here is the output of
:
:dmesg | grep acpi
Kernel command line: ro root=/dev/hda6 acpi_sleep=s3_bios
tbxface-0118 [02] acpi_load_tables : ACPI Tables successfully acquired
evxfevnt-0094 [03] acpi_enable : Transition to ACPI mode successful
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [df6ddaa8]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c1464768]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c1467328]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c146bba8]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c146b628]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c146b3e8]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c146b268]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c146dde8]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c1470d68]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c1470568]
acpi_bus-0081 [06] acpi_bus_get_device : Error getting context for object [c14719a8]
ibm_acpi: IBM ThinkPad ACPI Extras v0.8
ibm_acpi: http://ibm-acpi.sf.net/
acpi_bus-0081 [08] acpi_bus_get_device : Error getting context for object [c1467328]
ibm_acpi: dock device not present

:I don't understand the errors but anyway. Now the odd thing is that indeed the following works
:
event=button[ /]sleep
action=/usr/local/sbin/hibernate
:but
event=button[/]sleep
action=/usr/local/sbin/hibernate

:Does not work. But from what you said, using the ibm_acpi neither of '''these strings ''' should work? So I don't understand what is going on. [[User:Oub|Oub]] 20:28, 6 March 2006 (CET):

----

With any reasonably new kernel (2.6.16 in Thinkpad terms :-) ) and a good DSDT (say, like the one that comes inside the T43), you can get two classes of events: ACPI events (as in native ACPI events), and ibm-acpi hotkey events.

This has nothing to do with thinkpad-acpi.

Look under /proc/acpi/buttons. If you have sleep and maybe hibernate/suspend in there (I don't know how fn+f12 is called when properly supported through ACPI DSDT, the T43 doesn't support it like that), then your Thinkpad can, and will generate proper ACPI events without the help of ibm-acpi. This is valid for a complete ACPI config of kernel 2.6.16 with all modules loaded.

And it will generate regular ibm-acpi hotkey events if you enable the feature and use the correct mask, which may or may not confuse the thinkpad (I am not sure the correct DSDT handlers the BIOS expect to run are called in this case).

-- [[User:Hmh|hmh]] 2006-05-26 13:20 UTC

==Turn on/off Wifi on Fn5 ==
Hi

I hope this is the last question. I use a crude way to activate and deactivate my wificard: I remove and insert the relevant modules, with 2 simple scripts. Now the question is how can I bind Fn5 so, that it turns on and off the wificard? With my approach I need to fire up two scripts, and that I cannot bind to one button. Thanks
[[User:Oub|Oub]] 17:57, 5 March 2006 (CET):

Try a {{cmdroot|cat /proc/acpi/ibm/bluetooth}}. Maybe it returns the state. If not, the other way would be to check if the USB bluetooth controller device is listed in {{path|/proc/bus/usb}} somewhere. It shouldn't be there if bluetooth is switched off and should be there if it is on.

[[User:Wyrfel|Wyrfel]] 04:49, 6 March 2006 (CET)
----

==Split page?==
This page is getting too long. Maybe we should split it. I'd suggest moving the "Example applications" to a seperate page.

[[User:Pebolle|Paul Bolle]] 22:46, 3 April 2006 (CEST)

==DIY Firefox 1.5 xpi==
Here's how I maneged a Firefox 1.5 compatible plugin (source: google). Note that the wiki eats some of the xml tags (so look at the source too)

$ ls -1R tp41.xpi
tp41.xpi/:
chrome
chrome.manifest
install.rdf

tp41.xpi/chrome:
content

tp41.xpi/chrome/content:
tp41keysOverlay.xul

$ cat tp41.xpi/chrome.manifest
content tp41keys chrome/content/
overlay chrome://browser/content/browser.xul chrome://tp41keys/content/tp41keysOverlay.xul

$ cat tp41.xpi/install.rdf
<?xml version="1.0"?>

<RDF xmlns="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:em="http://www.mozilla.org/2004/em-rdf#">

<Description about="urn:mozilla:install-manifest">
<em:id>tp41keys@tp41keys.org</em:id>
<em:version>1.0</em:version>
<em:type>2</em:type>


<em:targetApplication>
<Description>
<em:id>{ec8030f7-c20a-464f-9b0e-13a3a9e97384}</em:id>
<em:minVersion>1.0+</em:minVersion>
<em:maxVersion>1.5.0.*</em:maxVersion>
</Description>
</em:targetApplication>


<em:name>IBM ThinkPad 41 Keys</em:name>
<em:description>Two Browser Navigation Keys</em:description>
<em:creator>Paul Bolle</em:creator>
<em:homepageURL>http://www.example.com/tp41keys.xpi</em:homepageURL>
</Description>
</RDF>

$ cat tp41.xpi/chrome/content/tp41keysOverlay.xul
<?xml version='1.0'?>
<!DOCTYPE overlay>

<overlay id='tp41keysOverlay'
xmlns='http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul'>

<keyset id='mainKeyset'>
<key id='tp41BackKey' keycode='VK_F21' command='Browser:Back' />
<key id='tp41ForwardKey' keycode='VK_F22' command='Browser:Forward' />
</keyset>

</overlay>

$ cat .mozilla/firefox/*.default/extensions/tp41keys\@tp41keys.org
~/tp41.xpi

==ibm-acpi hint==

I would like to add a hint under ibm-acpi to enable all hotkeys at boot, but I can not seem to get the HINT template to work:

<nowiki>{{HINT|To enable all hotkeys on boot in debian, create the file /etc/modprobe.d/ibm_acpi containing 'options ibm_acpi hotkey=enable,0xffff'}}</nowiki>

It outputs:

{{HINT|To enable all hotkeys on boot in debian, create the file /etc/modprobe.d/ibm_acpi containing 'options ibm_acpi hotkey=enable,0xffff'}}

Any ideas on how to get this to work? Also, does it even belong in the page?

--[[User:Paul Strefling|Paul Strefling]] 23:22, 10 August 2006 (CEST)

If you use ''ibm-apci'' as a module and have {{path|/proc}} filesystem enabled, you can tune it by
adding to {{path|/etc/modules.d/ibm_acpi}}:

post-install ibm-acpi /bin/echo enable,0x00d0 > /proc/acpi/ibm/hotkey
I added it after ''alias ibm-acpi ibm_acpi''. I'm not sure - if the order make sence. Params can be differ - it is an example.

Also works fine with {{cmdroot|modprobe}} (don't forget to run {{cmdroot|modules-update}} after editing {{path|/etc/modules.d/*}}).

(tested on Gentoo with vanilla kernel).

==Lock Screen with hotkey on models before T60==

In case it's of interest, it's possible to simulate the "lock screen" (Fn+F2) function of T60s on prior models. I wrote a little [http://forums.gentoo.org/viewtopic-p-3814885.html HOWTO] on the Gentoo forums explaining how to configure Fn+F3 to fire up xscreensaver instead of blanking the screen (though this could easily be changed to Fn+F2 instead). This was for my T42 but I presume it'd work on other models too. Perhaps it'd be worth mentioning in the Remarks column of the Fn+F2 row of the table at the top of the article? --[[User:Waveform|Waveform]] 03:42, 2 January 2007 (CET)

== Toggle touchpad with Fn-F8 ==

I often want to switch off the touchpad, since I tend to produce spurious taps while typing, sending my cursor to random places on the screen. To toggle touchpad operation, I use this little script:

#!/bin/sh
#
# toggle touchpad operation
# August 2, 2006
# (c) Michael Schmuker
#
if synclient -l | grep TouchpadOff | grep -q 0; then
synclient TouchpadOff=1;
kdialog --passivepopup "Touchpad is OFF" 2;
else
synclient TouchpadOff=0;
kdialog --passivepopup "Touchpad is ON" 2;
fi

This checks if the touchpad is on or off, and toggles its state accordingly. Note that it uses kdialog to display a notification on the desktop. This obviously works only with KDE, but there certainly is a similar mechanism for other desktop environments.

Now this script needs to be bound to the Fn-F8-key. On Suse 10.2, the ACPI-events produced by the thinkpad special keys are processed by powersaved. You need to edit the file {{path|/usr/lib/powersave/scripts/thinkpad_acpi_events}}.
There, thinkpad-ACPI events are bound to their actions. Where it comes to Fn-F8, just change it to the following (supposed you put the above script to {{path|/usr/local/bin/toggleTouchpad}} and make it executable):
4104) HOTKEY="Fn+F8" #toggle touchpad on/off
/usr/local/bin/toggleTouchpad
;;
Save the file, and the next time you press Fn-F8 you will toggle your touchpad.

Unfortunately, the notification via kdialog is not working when toggling with Fn-F8. If anyone finds out how to solve this: Let us know!

'''Possible Solutions:'''

1. You can instead use syndaemon, which can turn off the touchpad for a brief period while you are typing.

2. All acpi events are run as root. Therefore, to enable the kdialog, you will need to incorporate a script to determine which user is running on DISPLAY :0.0; something like the following should work (put it in your acpi file)
if ps -e | grep -q -E '(enlightenment|kwin|dwm)'; then
X_USER=`/usr/bin/who | /usr/bin/sed -n "s,^$.*$:0 .*$,\1,p"`
X_USER=${X_USER/ /};
export DISPLAY=:0.0
fi
if [ -n "$X_USER" ]; then su $X_USER -c "/usr/local/bin/toggleTouchpad";
else /usr/local/bin/toggleTouchpad;
fi
--[[User:Ppurka|Ppurka]] 18:43, 14 September 2007 (UTC)

== What about older machines? ==

On the 600X, Fn+PgUp and Fn+PgDn control speaker volume and Fn+Backspace toggles speaker mute. In addition, Fn+F2 is shows a battery icon and the manual states that it brings up a battery monitor. It hasn't worked since Windows 95. Fn+F11 shows a dripping tap and is meant to select a power mode. Fn+F8 has no icon but toggles screen expansion.

On the 750P, Fn+F5 and Fn+F6 control speaker volume, and I think Fn+F2 and Fn+F11 show the same icons as the 600X. However, that machine certainly doesn't have ACPI. Fn+F8 toggles screen inversion (black shows as white and vice-versa) on the monochrome models and Fn+F9 toggles brightness inversion (normal characters become bright and bright characters become normal). Those two only affect the internal LCD and not the signal on the VGA connector.

--[[User:Whizkid|Whizkid]] 19:32, 27 November 2007 (UTC)

Please add that information to the [[Default meanings of special keys]] page, including the description of the icons and functions. As for how to use these keys, it depends. How well does thinkpad-acpi work on the 600X and 750P? If it doesn't work at all, then you have to resort to tpb, which may have no idea how to access these keys in NVRAM :-(

--[[User:Hmh|hmh]] 14:18, 30 November 2007 (UTC)

I've updated the descriptions of functions on that page for 750P, 560E and 600X. There are no descriptions of icons anywhere on that page. An example to start with would be nice. The 750 family doesn't have ACPI at all.
--[[User:Whizkid|Whizkid]] 14:09, 25 December 2007 (UTC)

== ThinkVantage button not recognized by xev under Hardy ==

Hello,

I would like to set up the ThinkVantage button as XF86LaunchA, but I simply can't as it doesn't give any signal in xev. Any ideas how could I fix this?

Thanks, [[User:Nagyv|Nagyv]] 22:54, 3 July 2008 (CEST)

As the button is no "real keyboard button" it does not generate a keycode, but an acpi event (maybe thinkpad_acpi is needed for it to work) which you can set up to do what ever you want (well, not everything). see the article.

--[[User:BDKMPSS|BDKMPSS]] 23:45, 3 July 2008 (CEST)

Thank, this worked. I only had to add a new file under /etc/acpi/events. As there were many working examples, it was easy to write my own. Finally, I had to restart acpid.

thanks, [[User:Nagyv|Nagyv]]

How to get special keys to work

2008-12-10T21:44:56Z

Low: /* NumPad (KeyPad) keys access by a key combination */

==Overview==
The following table gives an overview over the special keys found on ThinkPads and what is needed to make them work.
{| {{prettytable}}
! key !! standard function{{footnote|1}} !! tools supporting key{{footnote|2}} !! configurability{{footnote|3}} !! remarks
|-
| {{key|Fn}} || - || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || on release without completed key combination
|-
| {{key|Fn}}{{key|F1}} || - || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full ||
|-
| {{key|Fn}}{{key|F2}} || lock screen || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full || in models from T/X/Z 60 onwards
|-
| {{key|Fn}}{{key|F3}} || blank screen || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full ||
|-
| {{key|Fn}}{{key|F4}} || suspend to ram || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full || may generate ACPI event when not enabled in the ibm-acpi hotkey mask
|-
| {{key|Fn}}{{key|F5}} || switch bluetooth || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full || in models starting from 2002
|-
| {{key|Fn}}{{key|F6}} || - || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full ||
|-
| {{key|Fn}}{{key|F7}} || toggle display || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]], [[#tpb configuration|tpb]] || additional actions || [[Sample Fn-F7 script]]
|-
| {{key|Fn}}{{key|F8}} || toggle trackpoint/touchpad || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]], [[#tpb configuration|tpb]] || additional actions ||
|-
| {{key|Fn}}{{key|F9}} || eject from dock || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full ||
|-
| {{key|Fn}}{{key|F10}} || - || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| {{key|Fn}}{{key|F11}} || - || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full ||
|-
| {{key|Fn}}{{key|F12}} || hibernate || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full || may generate ACPI event when not enabled in the ibm-acpi hotkey mask
|-
| {{key|Fn}}{{key|Home}} / {{key|Fn}}{{key|Pos1}} || brightness up || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]], [[#tpb configuration|tpb]], [[KMilo]] || additional actions ||
|-
| {{key|Fn}}{{key|End}} || brightness down || [[thinkpad-acpi]], [[#tpb configuration|tpb]], [[KMilo]] || additional actions ||
|-
| {{key|Fn}}{{key|PageUp}} || toggle thinklight || [[thinkpad-acpi]], [[#tpb configuration|tpb]], [[KMilo]] || additional actions ||
|-
| {{key|Fn}}{{key|Space}} || toggle zoom || [[thinkpad-acpi]], [[#tpb configuration|tpb]], [[KMilo]] || full ||
|-
| {{key|Fn}}{{key|Ins}} || - || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]]|| full ||
|-
| {{key|Fn}}{{key|Del}} || - || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| {{key|Fn}}{{key|Backspace}} || - || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| {{key|NumLock}} || - || [[#xmodmap configuration|xmodmap]] || make working ||
|-
| {{key|Windows}} || - || [[#xmodmap configuration|xmodmap]] || remapping ||
|-
| {{ibmkey|Access IBM|#495988}} or {{ibmkey|ThinkPad|#494949}} or {{ibmkey|ThinkVantage|#495988}} || help application || [[thinkpad-acpi]],[[#tpb configuration|tpb]], [[KMilo]] || full ||
|-
| {{ibmkey|Home|#494949}} || open web browser || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]], [[KMilo]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards
|-
| {{ibmkey|Search|#494949}} || open search application || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]], [[KMilo]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards
|-
| {{ibmkey|Mail|#494949}} || open mail application || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]], [[KMilo]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards
|-
| {{ibmkey|Favorites|#494949}} || open favorites || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards
|-
| {{ibmkey|Reload|#494949}} || reload web page || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards
|-
| {{ibmkey|Abort|#494949}} || abort loading page || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards
|-
| {{ibmkey|Backward|#494949}} || previous page || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || ext. keyboards and ThinkPads starting from 2002
|-
| {{ibmkey|Forward|#494949}} || next page || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || ext. keyboards and ThinkPads starting from 2002
|-
| {{ibmkey|Volume up|#494949}} || volume up || [[thinkpad-acpi]], [[#tpb configuration|tpb]], [[KMilo]] || additional actions ||
|-
| {{ibmkey|Volume down|#494949}} || volume down || [[thinkpad-acpi]], [[#tpb configuration|tpb]], [[KMilo]] || additional actions ||
|-
| {{ibmkey|Volume mute|#494949}} || mute volume || [[thinkpad-acpi]], [[#tpb configuration|tpb]], [[KMilo]] || additional actions ||
|-
| {{ibmkey|Play/Pause|#494949}} || start/pause playback || [[#xmodmap configuration|xmodmap]] || full || {{X60s}} (Fn+Arrow Down)
|-
| {{ibmkey|Stop|#494949}} || stop playback || [[#xmodmap configuration|xmodmap]] || full || {{X60s}} (Fn+Arrow Up)
|-
| {{ibmkey|Next|#494949}} || play next || [[#xmodmap configuration|xmodmap]] || full || {{X60s}} (Fn+Arrow Right)
|-
| {{ibmkey|Previous|#494949}} || play previous || [[#xmodmap configuration|xmodmap]] || full || {{X60s}} (Fn+Arrow Left)
|-
| {{ibmkey|Power|#494949}} || shutdown || [[#ibm-acpi events|ibm-acpi]],[[thinkpad-acpi]] || full || triggered on pressing 3secs, but notebook goes off on 5sec press
|-
| Display lid || blank screen || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full ||
|-
| Ultrabay lid || announce ultrabay change || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| Dock eject || eject from dock || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| {{ibmkey|Tablet power|#494949}} || shutdown || [[#ibm-acpi events|ibm-acpi]] || full || triggered on pressing 3secs, but notebook goes off on 5sec press
|-
| {{ibmkey|Tablet orientation|#494949}} || rotates screen || [[#Mapping keys with setkeycodes|setkeycodes]] || full ||
|-
| {{ibmkey|Tablet shortcut|#494949}} || shortcut menu || [[#Mapping keys with setkeycodes|setkeycodes]] || full ||
|-
| {{ibmkey|Tablet Esc|#494949}} || esc key || [[#Mapping keys with setkeycodes|setkeycodes]] || full ||
|-
| {{ibmkey|Tablet Enter|#494949}} || enter key || [[#mapping keys with setkeycodes|setkeycodes]] || full ||
|-
| {{ibmkey|Tablet Up|#494949}} || up key || [[#Mapping keys with setkeycodes|setkeycodes]] || full ||
|-
| {{ibmkey|Tablet Down|#494949}} || down key || [[#Mapping keys with setkeycodes|setkeycodes]] || full ||
|-
| {{ibmkey|Tablet (unlabeled)|#494949}} || down key || [[#Mapping keys with setkeycodes|setkeycodes]] || full ||
|}

For completeness, note that the WiFi enable/disable switch is located (on the X61 and other models that have it) just under the front edge of the base of the machine. You should see a small horizontal slider switch. Enable by sliding it rightwards, disable by sliding it leftwards.

==Triggering key events==
===ibm-acpi/thinkpad-acpi events===
Some of the following events require a {{cmdroot|echo enable,0xffff >/proc/acpi/ibm/hotkey}} (when using ibm-acpi) in order to make acpi able to get information on them. Since the newer thinkpad-acpi has a larger number of bits that can be set in the mask, you might try {{cmdroot|echo enable,0xffffffff >/proc/acpi/ibm/hotkey}} if you are using this driver. These events can be used to [[How to configure acpid|configure acpid]].

{| {{prettytable}}
|+ events triggered by [[ibm-acpi]] for {{path|/etc/acpi/events}} files. May vary on different models.
! key !! event
|-
| {{key|Fn}}{{key|F1}} || ibm/hotkey HKEY 00000080 00001001
|-
| {{key|Fn}}{{key|F2}} || ibm/hotkey HKEY 00000080 00001002
|-
| {{key|Fn}}{{key|F3}} || ibm/hotkey HKEY 00000080 00001003
|-
| {{key|Fn}}{{key|F4}} || ibm/hotkey HKEY 00000080 00001004
|-
| {{key|Fn}}{{key|F5}} || ibm/hotkey HKEY 00000080 00001005
|-
| {{key|Fn}}{{key|F6}} || ibm/hotkey HKEY 00000080 00001006
|-
| {{key|Fn}}{{key|F7}} || ibm/hotkey HKEY 00000080 00001007
|-
| {{key|Fn}}{{key|F8}} || ibm/hotkey HKEY 00000080 00001008
|-
| {{key|Fn}}{{key|F9}} || ibm/hotkey HKEY 00000080 00001009
|-
| {{key|Fn}}{{key|F10}} || ibm/hotkey HKEY 00000080 0000100a
|-
| {{key|Fn}}{{key|F11}} || ibm/hotkey HKEY 00000080 0000100b
|-
| {{key|Fn}}{{key|F12}} || ibm/hotkey HKEY 00000080 0000100c
|-
| {{key|Fn}}{{key|Backspace}} || ibm/hotkey HKEY 00000080 0000100d
|-
| {{key|Fn}}{{key|Ins}} || ibm/hotkey HKEY 00000080 0000100e
|-
| {{key|Fn}}{{key|Del}} || ibm/hotkey HKEY 00000080 0000100f
|-
| {{key|Fn}}{{key|Home}}/{{key|Fn}}{{key|Pos1}} || ibm/hotkey HKEY 00000080 00001010
|-
| {{key|Fn}}{{key|End}} || ibm/hotkey HKEY 00000080 00001011
|-
| {{key|Fn}}{{key|PgUp}} || ibm/hotkey HKEY 00000080 00001012
|-
| {{key|Fn}}{{key|Space}} || ibm/hotkey HKEY 00000080 00001014
|-
| {{ibmkey|Volume up|#494949}}|| ibm/hotkey HKEY 00000080 00001015
|-
| {{ibmkey|Volume down|#494949}} || ibm/hotkey HKEY 00000080 00001016
|-
| {{ibmkey|Volume mute|#494949}} || ibm/hotkey HKEY 00000080 00001017
|-
| {{ibmkey|Access IBM|#495988}} or {{ibmkey|ThinkPad|#494949}} or {{ibmkey|ThinkVantage|#495988}} || ibm/hotkey HKEY 00000080 00001018
|-
| Ultrabay eject || ibm/bay MSTR 00000003 00000000
|-
| Ultrabay inserted || ibm/bay MSTR 00000001 00000000
|-
| Dock eject || ibm/dock GDCK 00000003 00000001
|-
| Wireless switch || ibm/hotkey HKEY 00000080 00007000
|}

By disassembling and editing the DSDT, more events can be added. HKEY events are triggered by calls to the MKHQ function, e.g. <tt>\_SB.PCI0.LPC.EC.HKEY.MHKQ(0Ã—1007)</tt> will trigger "ibm/hotkey HKEY 00000080 00001007". Most of these can be found in <tt>_Qxx</tt> methods within the DSDT, which are executed on embedded controller events, e.g. _Q10 is triggered by pressing Fn-F7. You can add a call to MKHQ into an existing <tt>_Qxx</tt> method to get it recognized by ibm-acpi as well as creating new <tt>_Qxx</tt> methods, which if you're lucky will correspond to an EC event that IBM never used (e.g. A 770 will send Fn-Home/End/PgUp/PgDn to ibm-acpi if hacked in this fashion). For example, [http://www.wormnet.eu/ibm-g40/morebuttons.dsl this is a modified block of DSDT for a G40].

=== ACPI events from the <tt>button</tt> module===

A few keys can generate ACPI events that result from the <tt>button</tt> kernel module, as long as they are masked off in the <tt>ibm-acpi</tt>/<tt>thinkpad-acpi</tt> hotkey's mask or the hotkey function of the latter module is disabled.

If you want the ThinkPad's BIOS and ACPI methods to know about these keys being pressed, you probably want to leave them masked out from ibm-acpi, and use their non-HKEY events listed below, instead.

{| {{prettytable}}
|+ events triggered by ACPI when hotkey is masked out or disabled.
! key !! event !! T60 event
|-
| {{ibmkey|Power|#494949}} || button/power PWRF 00000080 xxxxxxxx || button/power PWRF 00000080 00000001
|-
| {{key|Fn}}{{key|F4}} || button/sleep SLPB 00000080 00000001 || button/sleep SLPB 00000080 00000001
|-
| Display lid || button/lid LID 00000080 xxxxxxxx || button/lid LID 00000080 00000001
|}

===tpb configuration===
{| {{prettytable}}
|+ configuration keywords for [[tpb]] (to put in {{path|/etc/tpbrc}})
! key !! config keyword
|-
| {{ibmkey|Access IBM|#495988}} or {{ibmkey|ThinkPad|#494949}} || THINKPAD
|-
| {{ibmkey|Home|#494949}} || HOME
|-
| {{ibmkey|Search|#494949}} || SEARCH
|-
| {{ibmkey|Mail|#494949}} || MAIL
|-
| {{ibmkey|Favorites|#494949}} || FAVORITES
|-
| {{ibmkey|Reload|#494949}} || RELOAD
|-
| {{ibmkey|Abort|#494949}} || ABORT
|-
| {{ibmkey|Backward|#494949}} || BACKWARD
|-
| {{ibmkey|Forward|#494949}} || FORWARD
|-
| {{key|Fn}} || FN
|-
| {{key|Fn}}{{key|Space}} || CALLBACK (zoom on/off)
|-
| {{key|Fn}}{{key|PageUp}} || CALLBACK (thinklight on/off)
|-
| {{key|Fn}}{{key|F7}} || CALLBACK (display lcd/crt/both)
|-
| {{key|Fn}}{{key|F8}} || CALLBACK (expand on/off)
|-
| {{key|Fn}}{{key|Home}} / {{key|Fn}}{{key|Pos1}} || CALLBACK (brightness <percent>)
|-
| {{key|Fn}}{{key|End}} || CALLBACK (brightness <percent>)
|-
| {{ibmkey|Volume up|#494949}} || CALLBACK (volume <percent>)
|-
| {{ibmkey|Volume down|#494949}} || CALLBACK (volume <percent>)
|-
| {{ibmkey|Volume mute|#494949}} || CALLBACK (mute on/off)
|}

To all parameter keywords should be assigned the full path to the executables supposed to be started on key press.
The exectable provided for the CALLBACK keyword should take the parameters given in parentheses and act according to them.
If you want to use xmodmap for the HOME, SEARCH, MAIL, FAVORITES, RELOAD, ABORT, BACKWARD, FORWARD and FN keys you should
provide a <tt>XEVENTS OFF</tt> in your {{path|/etc/tpbrc}}.
You can use an appropriate executable to [[How to inject fake keystrokes|inject fake keystrokes]].

For Debian users, tpb is started from {{path|/etc/X11/Xsession.d/90tpb}}.

'''Sound Button configuration'''

''Note: Tested on T60p with Ubuntu 6.06 LTS''

Most Thinkpads have a hardware sound mixer, thus the volumes buttons should work without configuration. However, this change is not reflected in the software mixer. tpb has a switch to enable software mixer support via OSS. The manual recommends this only for devices without a hardware mixer, but it also works for other hadware mixer enabled devices, even with the ALSA system. Just put MIXER ON in your {{path|/etc/tpbrc}} file and you can see the effect immediately in any ALSA mixer (e.g. kmix). For this to work you need write permissions to {{path|/dev/nvram}}.

''Note: Tested on X21 with Ubuntu 6.06 LTS''

On the ThinkPad X21 (and maybe some other older models) ACPI causes problems with tpb. On an X21 using acpi the volume buttons would work occasionally, and the OSD for tpb functions would rarely work. If a volume buttons was pressed too often, sometimes the computer would enter a low power (unplugged state) and would require a reboot. The solution is to use APM instead of ACPI. Instructions can be found in [[How_to_make_APM_work]].

===KMilo configuration===
The programs to be executed by [[KMilo]] are configured via the KDE Control Center (<tt>kcontrol</tt>), under <tt>System Administration --> IBM Thinkpad Laptop</tt>. Note that you can use appropriate commands to [[How to inject fake keystrokes|inject fake keystrokes]].

===xmodmap configuration===
xmodmap enables you to edit the modifier map and keymap tables that are used to translate keycodes into keysyms.
Understood? Well, basically it allows you to give the X server a dictionary for the translation of keycodes like "97" into more human readable synonyms like "Home". This way xmodmap allows you to make the special keys of your keyboard known to X applications.

To discover the keycode that a certain keypress produces, use the tool {{cmduser|xev}}

Usually you should write your keycode-keysym associations into the file {{path|~/.Xmodmap}}. This file is usually read by the X session startup scripts of your system, so that the mappings automatically get included everytime you run the X server.

The {{path|~/.Xmodmap}} lines for our purpose are in the form of
keycode <keycode> = <keysym>

Load the assocation using the command

{{cmduser|xmodmap ~/.Xmodmap}}

(some configurations do this automatically upon X startup).

The following table shows the keycodes generated by the ThinkPad special keys and sensible keysyms to assign them to.
{| {{prettytable}}
|+ keycodes and recommended keysyms
! key !! keycode !! keysym
|-
| {{ibmkey|Access IBM|#495988}} or {{ibmkey|ThinkPad|#494949}} || 159 || XF86LaunchA
|-
| {{ibmkey|Backward|#494949}} || 234 || XF86Back or F19
|-
| {{ibmkey|Forward|#494949}} || 233 || XF86Forward or F20
|-
| {{ibmkey|Play/Pause|#494949}} || 162 || XF86AudioPlay
|-
| {{ibmkey|Stop|#494949}} || 164 || XF86AudioStop
|-
| {{ibmkey|Next|#494949}} || 153 || XF86AudioNext
|-
| {{ibmkey|Previous|#494949}} || 144 || XF86AudioPrev
|-

| {{ibmkey|Home|#494949}} || 178 || XF86HomePage
|-
| {{ibmkey|Search|#494949}} || 229 || XF86Search
|-
| {{ibmkey|Mail|#494949}} || 236 || XF86Mail
|-
| {{ibmkey|Favorites|#494949}} || 230 || XF86AddFavorite or XF86Favorites
|-
| {{ibmkey|Reload|#494949}} || 231 || XF86Reload
|-
| {{ibmkey|Abort|#494949}} || 232 || XF86Stop
|-
| {{key|Fn}} || 227 || F35
|}

Note: You can also use xkeycaps (an X tool to display and edit the X keyboard mapping) to generate proper .Xmodmap.

Note: if you are running [[tpb]] you might need to add the line <tt>XEVENTS=off</tt> into your tpbrc to stop it from grabbing the key events and allow them to get through to X instead. See [[http://www.thinkwiki.org/wiki/Tpb]] for more detailed instruction on how to use tpb and xmodmap.

Note: XF86Forward and XF86Back do not work correctly in Firefox. You may want to map them to F19 and F20 instead if you use Firefox.

Note: The "XF86AudioPlay" etc. just works with a few programs. To make it work with more multimedia programs you have map the key to use something like [http://www.kde-apps.org/content/show.php/ReMoot?content=63140 ReMoot]. ReMoot is a command line wrapper that control 18 of the most common multimedia applications.

=====Enabling the Windows and Menu Keys=====
On some systems the Windows and Menu keys may not be recognized. You can enable then by
making the following changes:

keycode 115 = F13
keycode 227 = F35

F13 and F35 are used for the Windows and and Menu keys respectively. Labelling keycpode 227 as "Menu" may conflict with the right-mouse-click event.

=====Using Caps Lock as Super L (Windows key)=====
You can easily use Caps Lock as Win key by adding the following in your ~/.Xmodmap:
! No Caps Lock
clear lock
! Caps Lock as Win key
add mod4 = Caps_Lock
=====NumLock=====
On the ThinkPad {{600}}, {{T20}}, {{T21}}, {{T22}}, {{T30}}, {{X20}}, {{X21}}, {{X31}}, {{X40}}, {{T42p}}, {{T43}}, {{R51}}, {{R52}} and possibly other models, X does not recognize the keycode for {{key|NumLk}} = {{key|Shift}}+{{key|ScrLk}}. To fix this, add the following to {{path|~/.Xmodmap}} in your home directory or {{path|/etc/X11/Xmodmap}} and run <tt>xmodmap</tt>, ex: <tt>xmodmap ~/.Xmodmap</tt>:
keycode 77 = Num_Lock

This configuration also enables the respective LED.

Please note, pressing the {{key|Shift}}+{{key|ScrLk}} key combination, without first following the above configuration, will start an accessibility feature, which will allow the numeric keypad to maneuver the mouse pointer. Starting this accessibility feature and subsequently running xmodmap, as described above, results in the accessibility feature and the numeric lock LED functioning simultaneously. As such, the above configuration should be completed before the accessibility feature is started in order to produce numbers.
======T60 (and possibly others)======
It seems that on the T60, PrtSc, ScrLk and Pause all generate the correct keycodes, however Fn-PrtSc (labelled as SysRq) generates keycode 64 (Alt_L) followed by the expected 111 (Sys_Req) on down and the same thing in the opposite order on release. Fn-ScrLk (labelled as NmLk) does indeed toggle the Numlock, but only seems to register as an X event the first time it is engaged. The above solution does not appear to work. This is perhaps because the Numlock toggle is built into the firmware rather than controlled by the kernel. Finally, Fn-Pause (labelled as Break) generates keycode 37 (Control_L) followed by the expected keycode 110 (Break) on down and the same thing in reverse order on release.
=====NumPad (KeyPad) keys access by a key combination=====
The current state is that you have to switch NumLock '''on''' via {{key|Fn}}+{{key|ScrLk}} and then e.g. type {{key|u}} to get a {{key|KP_4}} (NumPad 4). To get back to normal keyboard, you have to type {{key|Fn}}+{{key|ScrLk}} again.

Some people (including me) are missing on recent Thinkpads the option to have Fn as a modifier key to access the NumPad instead, i.e. and e.g. {{key|Fn}}+{{key|u}} gives you {{key|KP_4}}.

There is currently no way to make this work in a simple way (pleeeease correct me if I am wrong!), though there is a work-around. Instead of using {{key|Fn}} for accessing the NumPad, {{key|CapsLock}} can get this function by being mapped as Mode_switch (the {{key|AltGr}} on international keyboards). The {{key|Fn}} can be remapped to be Caps_Lock - while at the same time retaining its function to access the special laptop functions (e.g. {{key|Fn}}+{{key|F4}} for sleep}}, by using .Xmodmap.

So on my R60 running fvwm@Slackware 12.1 the .Xmodmap would look like this:

! Make the forward and back buttons work
keycode 233 = XF86Forward
keycode 234 = XF86Back
! Make the WIN key to Super modifier
keycode 115 = Super_L
! Set the Caps_Lock physical key to Mode_switch (like AltGr on intl. keyboards)
keycode 66 = Mode_switch
! Set the Fn key to work as Caps_Lock now. The special key combos like Fn-F4 for "sleep" still work then
keycode 227 = Caps_Lock
! Now we activate those new keys. Find some free mod slots (xmodmap) and put them there.
clear mod4
clear mod5
add mod4 = Super_L
add mod3 = Mode_switch
! It's time to add the keypad keys to the third position of the key definition (pure shift mode_switch shift+mode_switch)
keycode 16 = 7 ampersand KP_7
keycode 17 = 8 asterisk KP_8
keycode 18 = 9 parenleft KP_9
keycode 19 = 0 parenright KP_Divide
keycode 30 = u U KP_4
keycode 31 = i I KP_5
keycode 32 = o O KP_6
keycode 33 = p P KP_Multiply
keycode 44 = j J KP_1
keycode 45 = k K KP_2
keycode 46 = l L KP_3
keycode 47 = semicolon colon KP_Subtract
keycode 58 = m M KP_0
! ... I have to use the coma key, too, on the keypad...so I set it to be F20 (which is not existing on normal keyboards and thus is free... check for side effects in programmes accepting F12+ keys!)
keycode 59 = comma less F20
keycode 60 = period greater KP_Decimal
keycode 61 = slash question KP_Add

{{WARN|Your keycodes might be different as well as your '''mod''#''''' settings.}}
Use {{cmduser|xmodmap}} and {{cmduser|xmodmap -pke}} to check your ModMap, and the tool {{cmduser|xev}} to obtain your exact key codes.

===Mapping keys with setkeycodes===
You can use the setkeycodes command to remap certain keys. I.e. you can use {{cmdroot|setkeycodes 6e 109 6d 104 69 28 6b 1}} to map the Tablets Up and Down keys to the standard PageUp and PageDown keys and Tablet Escape and Enter to their respective keys.

The following table shows the keycodes generated by the ThinkPad keys.
{| {{prettytable}}
|+ keycodes
! key !! keycode
|-
| {{ibmkey|Tablet orientation|#494949}} || 0x6c
|-
| {{ibmkey|Tablet Shortcut|#494949}} || 0x68
|-
| {{ibmkey|Tablet Esc|#494949}} || 0x6b
|-
| {{ibmkey|Tablet Enter|#494949}} || 0x69
|-
| {{ibmkey|Tablet Up|#494949}} || 0x6d
|-
| {{ibmkey|Tablet Down|#494949}} || 0x6e
|-
| {{ibmkey|Tablet (unlabeled)|#494949}} || 0x67
|}

===acpi_fakekey===
You can turn acpi events into user-level xevents by putting <tt>acpi_fakekey</tt> commands into the acpi action scripts. There are several layers involved in using acpi keys in this way, so I'll go through the example of using the ThinkVantage button to open xmms.

My ThinkVantage button generates an '''acpi event''' "ibm/hotkey HKEY 00000080 00001018", so we have the event file <tt>/etc/acpi/events/ThinkVantage</tt> for it which executes the script <tt>/etc/acpi/actions/fakekey-macro.sh</tt>.
<pre>
event=ibm/hotkey HKEY 00000080 00001018
action=/etc/acpi/actions/fakekey-macro.sh
</pre>
In turn, the executable <tt>/etc/acpi/actions/fakekey-macro.sh</tt> script calls acpi_fakekey with the '''key number''' defined in <tt>/usr/share/acpi-support/key-constants</tt> as $KEY_MACRO which is 112 (you could just as well choose an other key number, just make sure that it doesn't belong to something else like the "j" key or something).
<pre>
#!/bin/sh
. /usr/share/acpi-support/key-constants
acpi_fakekey $KEY_MACRO
</pre>
I have no idea how this actually corresponds to which xevent is generated, so I can find out out by running the program <tt>xev</tt> and hitting the ThinkVantage button while the mouse is in the <tt>xev</tt> window (remember to <tt>/etc/init.d/acpid restart</tt> first if you just created the <tt>/etc/acpi/events/ThinkVantage</tt> file). I get something popping up in the terminal where I ran xev that looks like this:
<pre>
KeyPress event, serial 30, synthetic NO, window 0x2800001,
root 0x6a, subw 0x0, time 2000522842, (138,83), root:(781,500),
state 0x0, keycode 239 (keysym 0x0, NoSymbol), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 30, synthetic NO, window 0x2800001,
root 0x6a, subw 0x0, time 2000522842, (138,83), root:(781,500),
state 0x0, keycode 239 (keysym 0x0, NoSymbol), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
</pre>
This tells me that the <tt>acpi_fakekey 112</tt> as executed by hitting the ThinkVantage button generates KeyPress event followed by a KeyRelease event with '''keycode''' 239 and that this keycode has been assigned no corresponding '''keysym'''. Thus, I am free to assign the keycode to any keysym I want. You can find a list of available keysyms in <tt>/usr/share/X11/XKeysymDB</tt>. Again try and pick one that is not likely to have already been taken by something, such as <tt>XF86LaunchA</tt>. To assign this keysym to keycode 239, you can either edit ~/.Xmodmap on an individual user basis, or edit the systemwide <tt>/etc/X11/Xmodmap</tt> file to contain the line
<pre>
keycode 239 = XF86LaunchA
</pre>
If you choose to go with the former, you may need to run <tt>xmodmap ~/.Xmodmap</tt> for every login session in order to read in your ~/.Xmodmap file if your window manager does not do it for you. Regardless of which option you choose, you can run <tt>xmodmap <file></tt> to read in the updated Xmodmap file without logging out and logging back in.

You should now find that hitting the ThinkVantage button creates the following output from <tt>xev</tt>:
<pre>
KeyPress event, serial 55, synthetic NO, window 0x2800001,
root 0x6a, subw 0x0, time 2001286078, (0,106), root:(643,523),
state 0x0, keycode 239 (keysym 0x1008ff4a, XF86LaunchA), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 55, synthetic NO, window 0x2800001,
root 0x6a, subw 0x0, time 2001286078, (0,106), root:(643,523),
state 0x0, keycode 239 (keysym 0x1008ff4a, XF86LaunchA), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
</pre>
Note the change of <tt>(keysym 0x0, NoSymbol)</tt> to <tt>(keysym 0x1008ff4a, XF86LaunchA)</tt>.

You're now ready to map <tt>XF86LaunchA</tt> to executing xmms. This is highly dependent on what keygrabber you decide to use. For openbox, I edit my <tt>~/.config/openbox/rc.xml</tt> file and add the following entry in the <keyboard> section:
<pre>
<keybind key="XF86LaunchA">
<action name="Execute">
<startupnotify>
<enabled>true</enabled>
</startupnotify>
<command>
xmms
</command>
</action>
</keybind>
</pre>
After, right clicking on the desktop and selecting the "Reconfigure" menu option, you should then have xmms pop up when you hit the ThinkVantage key.

==Example Applications==
===Web Browsers===
====Firefox (<3.0)====

There are various ways to assign actions to the browser keys. The easiest way is to install [http://mozilla.dorando.at/keyconfig.xpi keyconfig.xpi] from http://mozilla.dorando.at, which adds a menu entry Tools->Keyconfig. Then you can assign any action you want to the F19/F20 keys (you still need to create {{path|~/.Xmodmap}} as explained above).

The remaining discussion gives you various more complicated ways to achieve the same thing.
To have firefox make use of the browser keys you need to modify one of its files{{footnote|4}}.
To do this you will first need to extract it from the {{path|browser.jar}} archive. Do...

Step 1: Edit .Xmodmap and add entries for F19 and F20 as explained above.

Step 2:

Note: <firefox-directory> is probably /usr/lib/firefox. Use your version so, if you have 3.0.1 or 3.0.2 use /usr/lib/firefox-3.0.1

:{{cmdroot|cd <firefox-directory>/chrome}} 
:{{cmdroot|unzip browser.jar}}

The file of interest is {{path|content/browser/browser.xul}}. Edit it {and don't forget to make a backup copy first}...
:{{cmdroot|vi content/browser/browser.xul}}

Look for the '''<keyset id="mainKeyset">''' section and add the following lines within...
<key id="goBackKb" keycode="VK_F19" command="Browser:Back" />
<key id="goForwardKb" keycode="VK_F20" command="Browser:Forward" />

The Command you need for Next Tab
<key id="goBackTabKb" keycode="VK_F19" oncommand="gBrowser.mTabContainer.advanceSelectedTab(-1)" />
For the Previous Tab
<key id="goForwardTabKb" keycode="VK_F20" oncommand="gBrowser.mTabContainer.advanceSelectedTab(1)" />

Now save the file and repackage the {{path|browser.jar}} archive...
:{{cmdroot|zip -rD0 browser.jar content/browser/}}

That's it.

Step 3: Restart Firefox.

{{HINT|Outdated: Another interesting Page on Firefox is http://dqd.com/~mayoff/notes/thinkpad/dqdnavkeys/ It uses different key mappings (F19 resp. F20) but a ready [http://dqd.com/~mayoff/notes/thinkpad/dqdnavkeys/dqdnavkeys-1.2.xpi .xpi] is provided which is pretty comfortable. However, this xpi file does not install on Firefox 1.5. or later.}}

{{HINT| You can also use the [http://extensionroom.mozdev.org/more-info/keyconfig keyconfig] extension to configure custom keys. This extension works with Firefox 1.5 and also with Firefox 2.0. The Command you need for Next Tab is gBrowser.mTabContainer.advanceSelectedTab(1,true); For Previous Tab its gBrowser.mTabContainer.advanceSelectedTab(-1,true); You can alternatively install the [http://www.pqrs.org/~tekezo/firefox/extensions/functions_for_keyconfig/index.html functions for keyconfig] and set the variable f4kc_NextTab to F20 and f4kc_PrevTab to F19.}}.

====Firefox 3.0====
Thankfully the people at Mozilla decided to include the expected functionality for the XF86Back and XF86Forward keysyms in the new release so all you need to do is
 <code># printf 'keycode 234 = XF86Back\nkeycode 233 = XF86Forward' >> /etc/X11/Xmodmap</code> 
And to make this take effect immediately (i.e., without having to log out and log in again), as a regular user run:
 <code>{{cmduser|Xmodmap /etc/X11/Xmodmap}}</code>

For Hardy Heron, the xmodmap command is all lowercase. Also, the /etc/X11/Xmodmap file is not being read on boot. I've added the command to my .bashrc to have it called on startup.

====Konqueror====
KDE allows you set key mappings for KDE applications (Go to KMenu > System > Control Center > Regional & Accessibility > Keyboard Shortcuts). By default (at least in KDE 3.5), XF86Back and XF86Forward are set as alternatives to Alt-Left and Alt-Right, and are mapped to KDE Back and Forward navigation actions.

If you use Konqueror as your only browser, you only need to set up {{path|~/.Xmodmap}} as described [[#xmodmap configuration|above]] to assign ThinkPad back/forward keys to the symbols XF86Back/XF86Forward. This also make these keys work for other KDE applications such as Quanta Plus, KPackage and so on (not all KDE applications honor this setting, e.g. KDE help system doesn't).

If you want to use Firefox, however, the above settings do not work. You will have to map ThinkPad back/forward keys to F19/F20 as described [[#Firefox|above]], and change KDE navigation key settings to use F19/F20 instead of the default.

====Opera====
However this isn't a simple configration file, you can set your browser manually. 
Go to Tool > Settings > Mouse and keyboard > Keyboard settings > Edit > Browser Window. There add F19 - Back and F20 - Forward. Now you can surf using your TP keys ;-)

====Epiphany====
To get the keys work in epiphany, you could use the extension from [http://crashman.homelinux.org/~andre/public/epiphany%20extensions/thinkpad%20browserkeys/ here]
You just need to edit your Xmodmap like described for Firefox < 3.0 (bind the keys on F19 and F20)

===Open an application===

To configure the ThinkVantage button to open a terminal window in Gnome:

Step 1:
Use xev to find the keycode generated by the button on your machine. In my case is is 159.

Step 2:
Create an entry in .Xmodmap like so

keycode 159 = XF86LaunchA

replacing 159 by the keycode found in step 1. Load the map using

:{{cmd|xmodmap ~/.Xmodmap}}

Step 3:
Configure the required function (e.g. open terminal window) in System->Preferences->Keyboard shortcuts

===Window Managers===
====fvwm====
To get the {{ibmkey|Forward|#494949}} and {{ibmkey|Backward|#494949}} keys to cycle through pages in the virtual desktop, add this to your {{path|~/.fvwmrc}}:
Key XF86Back A A Scroll -100000 0
Key XF86Forward A A Scroll +100000 0
If you use multiple virtual desktops, you could instead use the keys to flip between them by using GotoDesk.

====fluxbox====
To get the keys to cycle through pages in the virtual desktop, add this to your {{path|~/.fluxbox/keys}}:
None F19 :PrevWorkspace
None F20 :NextWorkspace

====pekwm configuration====
You can make the two browser keys switch workspaces in pekwm, by adding the following two lines to the {{path|~/.pekwm/keys}} file:
KeyPress = "Mod1 XF86Back" { Actions = "GoToWorkspace prev" }
KeyPress = "Mod1 XF86Forward" { Actions = "GoToWorkspace next" }

====pwm====
Another example how to use these two keys to switch between pwm tabs. These two lines should be added to {{path|~/.pwm/keys-default.conf}} or {{path|/etc/pwm/keys-default.conf}}:
kbind "Back", "switch_rot", -1
kbind "Forward", "switch_rot", 1

====IceWM====
To make IceWM cycle workspaces using the {{ibmkey|Forward|#494949}} and {{ibmkey|Backward|#494949}} keys, change these two options in {{path|~/.icewm/preferences}} (Provided you assigned keysyms F19 and F20 with xmodmap):
# "Previous workspace" shortcut
KeySysWorkspacePrev="F19"
# "Next workspace" shortcut
KeySysWorkspaceNext="F20"

==== Gnome/metacity ====

Follow the [https://wiki.ubuntu.com/Keybindings Ubuntu guide].

===Other Uses===
====Console tools configuraton====
To make the {{ibmkey|Forward|#494949}} and {{ibmkey|Backward|#494949}} keys useful in console, add this to your keymap ({{path|/etc/console/boottime.kmap.gz}} in {{Debian}}):
keycode 158 = Decr_Console
keycode 159 = Incr_Console

Alternatively you can load this script (perhaps on system startup) to enable Backward/Forward button console (VT) switch:

#!/bin/sh
echo keycode 158 = Decr_Console | loadkeys
echo keycode 159 = Incr_Console | loadkeys

It should work with any distro.

====Cycling through tabs====
In Gnome and Xfce4, Ctrl-PageUp/Ctrl-PageDown move to the previous/following open tab in all applications that have tabbed user interfaces (terminal emulator, web browser, ...). To make use of the {{ibmkey|Forward|#494949}} and {{ibmkey|Backward|#494949}} keys for this task, there're two possibilities.

For both ways, you should map the keycodes 233 and 234 to XF86Back and XF86Forward as described in [[#xmodmap_configuration|xmodmap configuration]].

=====Using xautomation=====
xautomation can be found [http://hoopajoo.net/projects/xautomation.html here].

Create two files with permissions 755:

{{path|/usr/local/bin/tp_back}}:
<bash>
#!/bin/bash
/usr/bin/xte 'keydown Control_L' 'keydown Page_Up' 'keyup Page_Up' 'keyup Control_L'
</bash>

{{path|/usr/local/bin/tp_forward}}:
<bash>
#!/bin/bash
/usr/bin/xte 'keydown Control_L' 'keydown Page_Down' 'keyup Page_Down' 'keyup Control_L'
</bash>

Use your desktop's keyboard shortcut editor to assign XF86Back as a shortcut for tp_back and XF86Forward as a shortcut for tp_forward.

This should work in all distros and with all window managers (you might have to use other key combinations than Ctrl-PageUp and Ctrl-PageDown).

=====Redirecting XF86Back/XF86Forward=====
Create {{path|/etc/X11/xkb/compat/thinkpad}}:
<pre>
// $XFree86$
// XFree86 special keysyms
default partial xkb_compatibility "basic" {
interpret.repeat= True;

interpret XF86Back {
action = Redirect(Key=<PGUP>, modifiers=Control);
};
interpret XF86Forward {
action = Redirect(Key=<PGDN>, modifiers=Control);
};
};
</pre>

Edit {{path|/etc/X11/xkb/compat/complete}} and add <tt>'''augment "thinkpad"'''</tt> so that it looks similar to the following:
<pre>
// $XKeyboardConfig: xkbdesc/compat/complete,v 1.3 2005/10/17 00:42:11 svu Exp $
// $Xorg: complete,v 1.3 2000/08/17 19:54:34 cpqbld Exp $
default xkb_compatibility "complete" {
include "basic"
augment "iso9995"
augment "mousekeys"
augment "accessx(full)"
augment "misc"
augment "xfree86"
augment "level5"
augment "thinkpad"
};
</pre>

==External Sources==
*[http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-51537 IBMs page on configuring the ThinkPad buttons (ThinkPad, Access IBM, Mail, Search, and Home buttons) under Linux]
*[http://dqd.com/~mayoff/notes/thinkpad/dqdnavkeys/ Rob Mayoffs page on using IBM Keyboard Navigation Keys in Linux Mozilla and Firefox]
*[http://snarfed.org/space/thinkpad+keys+in+firefox Ryan Barretts blog article about using the browser keys in Firefox]
*[http://chaotika.org/~bluesceada/?page=soft&sub=thinkpad#acpibutn DennisG's help to get the ibm-acpi buttons do useful things] on a {{Z61e}} and possibly {{Z61m}}, {{Z61t}} and {{Z61p}}

{{footnotes|
#Note that the associated functionality for Fn-F* key combinations is not consistent amongst all ThinkPads. We are maintaining [[Default meanings of special keys|a table of associated meanings]].
#if there are more than one tool listed, one is sufficient
#'full' means you can completely reassign any action to be triggered by the key, 'additional actions' means you can trigger actions in addition to the standard function of the key, which can not be changed.
#Thanks go to Ryan Barrett for writing the [http://snarfed.org/space/thinkpad+keys+in+firefox little howto] on [http://snarfed.org/space/start his blog].
}}

How to get special keys to work

2008-12-10T20:46:41Z

Low: /* xmodmap configuration */

==Overview==
The following table gives an overview over the special keys found on ThinkPads and what is needed to make them work.
{| {{prettytable}}
! key !! standard function{{footnote|1}} !! tools supporting key{{footnote|2}} !! configurability{{footnote|3}} !! remarks
|-
| {{key|Fn}} || - || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || on release without completed key combination
|-
| {{key|Fn}}{{key|F1}} || - || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full ||
|-
| {{key|Fn}}{{key|F2}} || lock screen || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full || in models from T/X/Z 60 onwards
|-
| {{key|Fn}}{{key|F3}} || blank screen || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full ||
|-
| {{key|Fn}}{{key|F4}} || suspend to ram || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full || may generate ACPI event when not enabled in the ibm-acpi hotkey mask
|-
| {{key|Fn}}{{key|F5}} || switch bluetooth || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full || in models starting from 2002
|-
| {{key|Fn}}{{key|F6}} || - || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full ||
|-
| {{key|Fn}}{{key|F7}} || toggle display || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]], [[#tpb configuration|tpb]] || additional actions || [[Sample Fn-F7 script]]
|-
| {{key|Fn}}{{key|F8}} || toggle trackpoint/touchpad || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]], [[#tpb configuration|tpb]] || additional actions ||
|-
| {{key|Fn}}{{key|F9}} || eject from dock || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full ||
|-
| {{key|Fn}}{{key|F10}} || - || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| {{key|Fn}}{{key|F11}} || - || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full ||
|-
| {{key|Fn}}{{key|F12}} || hibernate || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full || may generate ACPI event when not enabled in the ibm-acpi hotkey mask
|-
| {{key|Fn}}{{key|Home}} / {{key|Fn}}{{key|Pos1}} || brightness up || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]], [[#tpb configuration|tpb]], [[KMilo]] || additional actions ||
|-
| {{key|Fn}}{{key|End}} || brightness down || [[thinkpad-acpi]], [[#tpb configuration|tpb]], [[KMilo]] || additional actions ||
|-
| {{key|Fn}}{{key|PageUp}} || toggle thinklight || [[thinkpad-acpi]], [[#tpb configuration|tpb]], [[KMilo]] || additional actions ||
|-
| {{key|Fn}}{{key|Space}} || toggle zoom || [[thinkpad-acpi]], [[#tpb configuration|tpb]], [[KMilo]] || full ||
|-
| {{key|Fn}}{{key|Ins}} || - || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]]|| full ||
|-
| {{key|Fn}}{{key|Del}} || - || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| {{key|Fn}}{{key|Backspace}} || - || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| {{key|NumLock}} || - || [[#xmodmap configuration|xmodmap]] || make working ||
|-
| {{key|Windows}} || - || [[#xmodmap configuration|xmodmap]] || remapping ||
|-
| {{ibmkey|Access IBM|#495988}} or {{ibmkey|ThinkPad|#494949}} or {{ibmkey|ThinkVantage|#495988}} || help application || [[thinkpad-acpi]],[[#tpb configuration|tpb]], [[KMilo]] || full ||
|-
| {{ibmkey|Home|#494949}} || open web browser || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]], [[KMilo]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards
|-
| {{ibmkey|Search|#494949}} || open search application || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]], [[KMilo]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards
|-
| {{ibmkey|Mail|#494949}} || open mail application || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]], [[KMilo]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards
|-
| {{ibmkey|Favorites|#494949}} || open favorites || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards
|-
| {{ibmkey|Reload|#494949}} || reload web page || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards
|-
| {{ibmkey|Abort|#494949}} || abort loading page || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards
|-
| {{ibmkey|Backward|#494949}} || previous page || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || ext. keyboards and ThinkPads starting from 2002
|-
| {{ibmkey|Forward|#494949}} || next page || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || ext. keyboards and ThinkPads starting from 2002
|-
| {{ibmkey|Volume up|#494949}} || volume up || [[thinkpad-acpi]], [[#tpb configuration|tpb]], [[KMilo]] || additional actions ||
|-
| {{ibmkey|Volume down|#494949}} || volume down || [[thinkpad-acpi]], [[#tpb configuration|tpb]], [[KMilo]] || additional actions ||
|-
| {{ibmkey|Volume mute|#494949}} || mute volume || [[thinkpad-acpi]], [[#tpb configuration|tpb]], [[KMilo]] || additional actions ||
|-
| {{ibmkey|Play/Pause|#494949}} || start/pause playback || [[#xmodmap configuration|xmodmap]] || full || {{X60s}} (Fn+Arrow Down)
|-
| {{ibmkey|Stop|#494949}} || stop playback || [[#xmodmap configuration|xmodmap]] || full || {{X60s}} (Fn+Arrow Up)
|-
| {{ibmkey|Next|#494949}} || play next || [[#xmodmap configuration|xmodmap]] || full || {{X60s}} (Fn+Arrow Right)
|-
| {{ibmkey|Previous|#494949}} || play previous || [[#xmodmap configuration|xmodmap]] || full || {{X60s}} (Fn+Arrow Left)
|-
| {{ibmkey|Power|#494949}} || shutdown || [[#ibm-acpi events|ibm-acpi]],[[thinkpad-acpi]] || full || triggered on pressing 3secs, but notebook goes off on 5sec press
|-
| Display lid || blank screen || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full ||
|-
| Ultrabay lid || announce ultrabay change || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| Dock eject || eject from dock || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| {{ibmkey|Tablet power|#494949}} || shutdown || [[#ibm-acpi events|ibm-acpi]] || full || triggered on pressing 3secs, but notebook goes off on 5sec press
|-
| {{ibmkey|Tablet orientation|#494949}} || rotates screen || [[#Mapping keys with setkeycodes|setkeycodes]] || full ||
|-
| {{ibmkey|Tablet shortcut|#494949}} || shortcut menu || [[#Mapping keys with setkeycodes|setkeycodes]] || full ||
|-
| {{ibmkey|Tablet Esc|#494949}} || esc key || [[#Mapping keys with setkeycodes|setkeycodes]] || full ||
|-
| {{ibmkey|Tablet Enter|#494949}} || enter key || [[#mapping keys with setkeycodes|setkeycodes]] || full ||
|-
| {{ibmkey|Tablet Up|#494949}} || up key || [[#Mapping keys with setkeycodes|setkeycodes]] || full ||
|-
| {{ibmkey|Tablet Down|#494949}} || down key || [[#Mapping keys with setkeycodes|setkeycodes]] || full ||
|-
| {{ibmkey|Tablet (unlabeled)|#494949}} || down key || [[#Mapping keys with setkeycodes|setkeycodes]] || full ||
|}

For completeness, note that the WiFi enable/disable switch is located (on the X61 and other models that have it) just under the front edge of the base of the machine. You should see a small horizontal slider switch. Enable by sliding it rightwards, disable by sliding it leftwards.

==Triggering key events==
===ibm-acpi/thinkpad-acpi events===
Some of the following events require a {{cmdroot|echo enable,0xffff >/proc/acpi/ibm/hotkey}} (when using ibm-acpi) in order to make acpi able to get information on them. Since the newer thinkpad-acpi has a larger number of bits that can be set in the mask, you might try {{cmdroot|echo enable,0xffffffff >/proc/acpi/ibm/hotkey}} if you are using this driver. These events can be used to [[How to configure acpid|configure acpid]].

{| {{prettytable}}
|+ events triggered by [[ibm-acpi]] for {{path|/etc/acpi/events}} files. May vary on different models.
! key !! event
|-
| {{key|Fn}}{{key|F1}} || ibm/hotkey HKEY 00000080 00001001
|-
| {{key|Fn}}{{key|F2}} || ibm/hotkey HKEY 00000080 00001002
|-
| {{key|Fn}}{{key|F3}} || ibm/hotkey HKEY 00000080 00001003
|-
| {{key|Fn}}{{key|F4}} || ibm/hotkey HKEY 00000080 00001004
|-
| {{key|Fn}}{{key|F5}} || ibm/hotkey HKEY 00000080 00001005
|-
| {{key|Fn}}{{key|F6}} || ibm/hotkey HKEY 00000080 00001006
|-
| {{key|Fn}}{{key|F7}} || ibm/hotkey HKEY 00000080 00001007
|-
| {{key|Fn}}{{key|F8}} || ibm/hotkey HKEY 00000080 00001008
|-
| {{key|Fn}}{{key|F9}} || ibm/hotkey HKEY 00000080 00001009
|-
| {{key|Fn}}{{key|F10}} || ibm/hotkey HKEY 00000080 0000100a
|-
| {{key|Fn}}{{key|F11}} || ibm/hotkey HKEY 00000080 0000100b
|-
| {{key|Fn}}{{key|F12}} || ibm/hotkey HKEY 00000080 0000100c
|-
| {{key|Fn}}{{key|Backspace}} || ibm/hotkey HKEY 00000080 0000100d
|-
| {{key|Fn}}{{key|Ins}} || ibm/hotkey HKEY 00000080 0000100e
|-
| {{key|Fn}}{{key|Del}} || ibm/hotkey HKEY 00000080 0000100f
|-
| {{key|Fn}}{{key|Home}}/{{key|Fn}}{{key|Pos1}} || ibm/hotkey HKEY 00000080 00001010
|-
| {{key|Fn}}{{key|End}} || ibm/hotkey HKEY 00000080 00001011
|-
| {{key|Fn}}{{key|PgUp}} || ibm/hotkey HKEY 00000080 00001012
|-
| {{key|Fn}}{{key|Space}} || ibm/hotkey HKEY 00000080 00001014
|-
| {{ibmkey|Volume up|#494949}}|| ibm/hotkey HKEY 00000080 00001015
|-
| {{ibmkey|Volume down|#494949}} || ibm/hotkey HKEY 00000080 00001016
|-
| {{ibmkey|Volume mute|#494949}} || ibm/hotkey HKEY 00000080 00001017
|-
| {{ibmkey|Access IBM|#495988}} or {{ibmkey|ThinkPad|#494949}} or {{ibmkey|ThinkVantage|#495988}} || ibm/hotkey HKEY 00000080 00001018
|-
| Ultrabay eject || ibm/bay MSTR 00000003 00000000
|-
| Ultrabay inserted || ibm/bay MSTR 00000001 00000000
|-
| Dock eject || ibm/dock GDCK 00000003 00000001
|-
| Wireless switch || ibm/hotkey HKEY 00000080 00007000
|}

By disassembling and editing the DSDT, more events can be added. HKEY events are triggered by calls to the MKHQ function, e.g. <tt>\_SB.PCI0.LPC.EC.HKEY.MHKQ(0Ã—1007)</tt> will trigger "ibm/hotkey HKEY 00000080 00001007". Most of these can be found in <tt>_Qxx</tt> methods within the DSDT, which are executed on embedded controller events, e.g. _Q10 is triggered by pressing Fn-F7. You can add a call to MKHQ into an existing <tt>_Qxx</tt> method to get it recognized by ibm-acpi as well as creating new <tt>_Qxx</tt> methods, which if you're lucky will correspond to an EC event that IBM never used (e.g. A 770 will send Fn-Home/End/PgUp/PgDn to ibm-acpi if hacked in this fashion). For example, [http://www.wormnet.eu/ibm-g40/morebuttons.dsl this is a modified block of DSDT for a G40].

=== ACPI events from the <tt>button</tt> module===

A few keys can generate ACPI events that result from the <tt>button</tt> kernel module, as long as they are masked off in the <tt>ibm-acpi</tt>/<tt>thinkpad-acpi</tt> hotkey's mask or the hotkey function of the latter module is disabled.

If you want the ThinkPad's BIOS and ACPI methods to know about these keys being pressed, you probably want to leave them masked out from ibm-acpi, and use their non-HKEY events listed below, instead.

{| {{prettytable}}
|+ events triggered by ACPI when hotkey is masked out or disabled.
! key !! event !! T60 event
|-
| {{ibmkey|Power|#494949}} || button/power PWRF 00000080 xxxxxxxx || button/power PWRF 00000080 00000001
|-
| {{key|Fn}}{{key|F4}} || button/sleep SLPB 00000080 00000001 || button/sleep SLPB 00000080 00000001
|-
| Display lid || button/lid LID 00000080 xxxxxxxx || button/lid LID 00000080 00000001
|}

===tpb configuration===
{| {{prettytable}}
|+ configuration keywords for [[tpb]] (to put in {{path|/etc/tpbrc}})
! key !! config keyword
|-
| {{ibmkey|Access IBM|#495988}} or {{ibmkey|ThinkPad|#494949}} || THINKPAD
|-
| {{ibmkey|Home|#494949}} || HOME
|-
| {{ibmkey|Search|#494949}} || SEARCH
|-
| {{ibmkey|Mail|#494949}} || MAIL
|-
| {{ibmkey|Favorites|#494949}} || FAVORITES
|-
| {{ibmkey|Reload|#494949}} || RELOAD
|-
| {{ibmkey|Abort|#494949}} || ABORT
|-
| {{ibmkey|Backward|#494949}} || BACKWARD
|-
| {{ibmkey|Forward|#494949}} || FORWARD
|-
| {{key|Fn}} || FN
|-
| {{key|Fn}}{{key|Space}} || CALLBACK (zoom on/off)
|-
| {{key|Fn}}{{key|PageUp}} || CALLBACK (thinklight on/off)
|-
| {{key|Fn}}{{key|F7}} || CALLBACK (display lcd/crt/both)
|-
| {{key|Fn}}{{key|F8}} || CALLBACK (expand on/off)
|-
| {{key|Fn}}{{key|Home}} / {{key|Fn}}{{key|Pos1}} || CALLBACK (brightness <percent>)
|-
| {{key|Fn}}{{key|End}} || CALLBACK (brightness <percent>)
|-
| {{ibmkey|Volume up|#494949}} || CALLBACK (volume <percent>)
|-
| {{ibmkey|Volume down|#494949}} || CALLBACK (volume <percent>)
|-
| {{ibmkey|Volume mute|#494949}} || CALLBACK (mute on/off)
|}

To all parameter keywords should be assigned the full path to the executables supposed to be started on key press.
The exectable provided for the CALLBACK keyword should take the parameters given in parentheses and act according to them.
If you want to use xmodmap for the HOME, SEARCH, MAIL, FAVORITES, RELOAD, ABORT, BACKWARD, FORWARD and FN keys you should
provide a <tt>XEVENTS OFF</tt> in your {{path|/etc/tpbrc}}.
You can use an appropriate executable to [[How to inject fake keystrokes|inject fake keystrokes]].

For Debian users, tpb is started from {{path|/etc/X11/Xsession.d/90tpb}}.

'''Sound Button configuration'''

''Note: Tested on T60p with Ubuntu 6.06 LTS''

Most Thinkpads have a hardware sound mixer, thus the volumes buttons should work without configuration. However, this change is not reflected in the software mixer. tpb has a switch to enable software mixer support via OSS. The manual recommends this only for devices without a hardware mixer, but it also works for other hadware mixer enabled devices, even with the ALSA system. Just put MIXER ON in your {{path|/etc/tpbrc}} file and you can see the effect immediately in any ALSA mixer (e.g. kmix). For this to work you need write permissions to {{path|/dev/nvram}}.

''Note: Tested on X21 with Ubuntu 6.06 LTS''

On the ThinkPad X21 (and maybe some other older models) ACPI causes problems with tpb. On an X21 using acpi the volume buttons would work occasionally, and the OSD for tpb functions would rarely work. If a volume buttons was pressed too often, sometimes the computer would enter a low power (unplugged state) and would require a reboot. The solution is to use APM instead of ACPI. Instructions can be found in [[How_to_make_APM_work]].

===KMilo configuration===
The programs to be executed by [[KMilo]] are configured via the KDE Control Center (<tt>kcontrol</tt>), under <tt>System Administration --> IBM Thinkpad Laptop</tt>. Note that you can use appropriate commands to [[How to inject fake keystrokes|inject fake keystrokes]].

===xmodmap configuration===
xmodmap enables you to edit the modifier map and keymap tables that are used to translate keycodes into keysyms.
Understood? Well, basically it allows you to give the X server a dictionary for the translation of keycodes like "97" into more human readable synonyms like "Home". This way xmodmap allows you to make the special keys of your keyboard known to X applications.

To discover the keycode that a certain keypress produces, use the tool {{cmduser|xev}}

Usually you should write your keycode-keysym associations into the file {{path|~/.Xmodmap}}. This file is usually read by the X session startup scripts of your system, so that the mappings automatically get included everytime you run the X server.

The {{path|~/.Xmodmap}} lines for our purpose are in the form of
keycode <keycode> = <keysym>

Load the assocation using the command

{{cmduser|xmodmap ~/.Xmodmap}}

(some configurations do this automatically upon X startup).

The following table shows the keycodes generated by the ThinkPad special keys and sensible keysyms to assign them to.
{| {{prettytable}}
|+ keycodes and recommended keysyms
! key !! keycode !! keysym
|-
| {{ibmkey|Access IBM|#495988}} or {{ibmkey|ThinkPad|#494949}} || 159 || XF86LaunchA
|-
| {{ibmkey|Backward|#494949}} || 234 || XF86Back or F19
|-
| {{ibmkey|Forward|#494949}} || 233 || XF86Forward or F20
|-
| {{ibmkey|Play/Pause|#494949}} || 162 || XF86AudioPlay
|-
| {{ibmkey|Stop|#494949}} || 164 || XF86AudioStop
|-
| {{ibmkey|Next|#494949}} || 153 || XF86AudioNext
|-
| {{ibmkey|Previous|#494949}} || 144 || XF86AudioPrev
|-

| {{ibmkey|Home|#494949}} || 178 || XF86HomePage
|-
| {{ibmkey|Search|#494949}} || 229 || XF86Search
|-
| {{ibmkey|Mail|#494949}} || 236 || XF86Mail
|-
| {{ibmkey|Favorites|#494949}} || 230 || XF86AddFavorite or XF86Favorites
|-
| {{ibmkey|Reload|#494949}} || 231 || XF86Reload
|-
| {{ibmkey|Abort|#494949}} || 232 || XF86Stop
|-
| {{key|Fn}} || 227 || F35
|}

Note: You can also use xkeycaps (an X tool to display and edit the X keyboard mapping) to generate proper .Xmodmap.

Note: if you are running [[tpb]] you might need to add the line <tt>XEVENTS=off</tt> into your tpbrc to stop it from grabbing the key events and allow them to get through to X instead. See [[http://www.thinkwiki.org/wiki/Tpb]] for more detailed instruction on how to use tpb and xmodmap.

Note: XF86Forward and XF86Back do not work correctly in Firefox. You may want to map them to F19 and F20 instead if you use Firefox.

Note: The "XF86AudioPlay" etc. just works with a few programs. To make it work with more multimedia programs you have map the key to use something like [http://www.kde-apps.org/content/show.php/ReMoot?content=63140 ReMoot]. ReMoot is a command line wrapper that control 18 of the most common multimedia applications.

=====Enabling the Windows and Menu Keys=====
On some systems the Windows and Menu keys may not be recognized. You can enable then by
making the following changes:

keycode 115 = F13
keycode 227 = F35

F13 and F35 are used for the Windows and and Menu keys respectively. Labelling keycpode 227 as "Menu" may conflict with the right-mouse-click event.

=====Using Caps Lock as Super L (Windows key)=====
You can easily use Caps Lock as Win key by adding the following in your ~/.Xmodmap:
! No Caps Lock
clear lock
! Caps Lock as Win key
add mod4 = Caps_Lock
=====NumLock=====
On the ThinkPad {{600}}, {{T20}}, {{T21}}, {{T22}}, {{T30}}, {{X20}}, {{X21}}, {{X31}}, {{X40}}, {{T42p}}, {{T43}}, {{R51}}, {{R52}} and possibly other models, X does not recognize the keycode for {{key|NumLk}} = {{key|Shift}}+{{key|ScrLk}}. To fix this, add the following to {{path|~/.Xmodmap}} in your home directory or {{path|/etc/X11/Xmodmap}} and run <tt>xmodmap</tt>, ex: <tt>xmodmap ~/.Xmodmap</tt>:
keycode 77 = Num_Lock

This configuration also enables the respective LED.

Please note, pressing the {{key|Shift}}+{{key|ScrLk}} key combination, without first following the above configuration, will start an accessibility feature, which will allow the numeric keypad to maneuver the mouse pointer. Starting this accessibility feature and subsequently running xmodmap, as described above, results in the accessibility feature and the numeric lock LED functioning simultaneously. As such, the above configuration should be completed before the accessibility feature is started in order to produce numbers.
======T60 (and possibly others)======
It seems that on the T60, PrtSc, ScrLk and Pause all generate the correct keycodes, however Fn-PrtSc (labelled as SysRq) generates keycode 64 (Alt_L) followed by the expected 111 (Sys_Req) on down and the same thing in the opposite order on release. Fn-ScrLk (labelled as NmLk) does indeed toggle the Numlock, but only seems to register as an X event the first time it is engaged. The above solution does not appear to work. This is perhaps because the Numlock toggle is built into the firmware rather than controlled by the kernel. Finally, Fn-Pause (labelled as Break) generates keycode 37 (Control_L) followed by the expected keycode 110 (Break) on down and the same thing in reverse order on release.
=====NumPad (KeyPad) keys access by a key combination=====
The current state is that you have to switch NumLock '''on''' via {{key|Fn}}+{{key|ScrLk}} and then e.g. type {{key|u}} to get a {{key|KP_4}} (NumPad 4). To get back to normal keyboard, you have to type {{key|Fn}}+{{key|ScrLk}} again.

Some people (including me) are missing on recent Thinkpads the option to have Fn as a modifier key to access the NumPad instead, i.e. and e.g. {{key|Fn}}+{{key|u}} gives you {{key|KP_4}}.

There is currently no way to make this work in a simple way (pleeeease correct me if I am wrong!), though there is a work-around. Instead of using {{key|Fn}} for accessing the NumPad, {{key|CapsLock}} can get this function by being mapped as Mode_switch (the {{key|AltGr}} on international keyboards). The {{key|Fn}} can be remapped to be Caps_Lock - while at the same time retaining its function to access the special laptop functions (e.g. {{key|Fn}}+{{key|F4}} for sleep}}, by using .Xmodmap.

So on my R60 running fvwm@Slackware 12.1 the .Xmodmap would look like this:

! Make the forward and back buttons work
keycode 233 = XF86Forward
keycode 234 = XF86Back
! Make the WIN key to Super modifier
keycode 115 = Super_L
! Set the Caps_Lock physical key to Mode_switch (like AltGr on intl. keyboards)
keycode 66 = Mode_switch
! Set the Fn key to work as Caps_Lock now. The special key combos like Fn-F4 for "sleep" still work then
keycode 227 = Caps_Lock
! Now we activate those new keys. Find some free mod slots (xmodmap) and put them there.
clear mod4
clear mod5
!clear lock
add mod4 = Super_L
!add lock = Caps_Lock
add mod3 = Mode_switch
! It's time to add the keypad keys to the third position of the key definition (pure shift mode_switch shift+mode_switch)
keycode 16 = 7 ampersand KP_7
keycode 17 = 8 asterisk KP_8
keycode 18 = 9 parenleft KP_9
keycode 19 = 0 parenright KP_Divide
keycode 30 = u U KP_4
keycode 31 = i I KP_5
keycode 32 = o O KP_6
keycode 33 = p P KP_Multiply
keycode 44 = j J KP_1
keycode 45 = k K KP_2
keycode 46 = l L KP_3
keycode 47 = semicolon colon KP_Subtract
keycode 58 = m M KP_0
! ... I have to use the coma key, too, on the keypad...so I set it to be F20 (which is not existing on normal keyboards and thus is free... check for side effects in programmes accepting F12+ keys!)
keycode 59 = comma less F20
keycode 60 = period greater KP_Decimal
keycode 61 = slash question KP_Add

{{WARN|Your keycodes might be different as well as your '''mod''#''''' settings.}}
Use {{cmduser|xmodmap}} and {{cmduser|xmodmap -pke}} to check your ModMap, and the tool {{cmduser|xev}} to obtain your exact key codes.

===Mapping keys with setkeycodes===
You can use the setkeycodes command to remap certain keys. I.e. you can use {{cmdroot|setkeycodes 6e 109 6d 104 69 28 6b 1}} to map the Tablets Up and Down keys to the standard PageUp and PageDown keys and Tablet Escape and Enter to their respective keys.

The following table shows the keycodes generated by the ThinkPad keys.
{| {{prettytable}}
|+ keycodes
! key !! keycode
|-
| {{ibmkey|Tablet orientation|#494949}} || 0x6c
|-
| {{ibmkey|Tablet Shortcut|#494949}} || 0x68
|-
| {{ibmkey|Tablet Esc|#494949}} || 0x6b
|-
| {{ibmkey|Tablet Enter|#494949}} || 0x69
|-
| {{ibmkey|Tablet Up|#494949}} || 0x6d
|-
| {{ibmkey|Tablet Down|#494949}} || 0x6e
|-
| {{ibmkey|Tablet (unlabeled)|#494949}} || 0x67
|}

===acpi_fakekey===
You can turn acpi events into user-level xevents by putting <tt>acpi_fakekey</tt> commands into the acpi action scripts. There are several layers involved in using acpi keys in this way, so I'll go through the example of using the ThinkVantage button to open xmms.

My ThinkVantage button generates an '''acpi event''' "ibm/hotkey HKEY 00000080 00001018", so we have the event file <tt>/etc/acpi/events/ThinkVantage</tt> for it which executes the script <tt>/etc/acpi/actions/fakekey-macro.sh</tt>.
<pre>
event=ibm/hotkey HKEY 00000080 00001018
action=/etc/acpi/actions/fakekey-macro.sh
</pre>
In turn, the executable <tt>/etc/acpi/actions/fakekey-macro.sh</tt> script calls acpi_fakekey with the '''key number''' defined in <tt>/usr/share/acpi-support/key-constants</tt> as $KEY_MACRO which is 112 (you could just as well choose an other key number, just make sure that it doesn't belong to something else like the "j" key or something).
<pre>
#!/bin/sh
. /usr/share/acpi-support/key-constants
acpi_fakekey $KEY_MACRO
</pre>
I have no idea how this actually corresponds to which xevent is generated, so I can find out out by running the program <tt>xev</tt> and hitting the ThinkVantage button while the mouse is in the <tt>xev</tt> window (remember to <tt>/etc/init.d/acpid restart</tt> first if you just created the <tt>/etc/acpi/events/ThinkVantage</tt> file). I get something popping up in the terminal where I ran xev that looks like this:
<pre>
KeyPress event, serial 30, synthetic NO, window 0x2800001,
root 0x6a, subw 0x0, time 2000522842, (138,83), root:(781,500),
state 0x0, keycode 239 (keysym 0x0, NoSymbol), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 30, synthetic NO, window 0x2800001,
root 0x6a, subw 0x0, time 2000522842, (138,83), root:(781,500),
state 0x0, keycode 239 (keysym 0x0, NoSymbol), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
</pre>
This tells me that the <tt>acpi_fakekey 112</tt> as executed by hitting the ThinkVantage button generates KeyPress event followed by a KeyRelease event with '''keycode''' 239 and that this keycode has been assigned no corresponding '''keysym'''. Thus, I am free to assign the keycode to any keysym I want. You can find a list of available keysyms in <tt>/usr/share/X11/XKeysymDB</tt>. Again try and pick one that is not likely to have already been taken by something, such as <tt>XF86LaunchA</tt>. To assign this keysym to keycode 239, you can either edit ~/.Xmodmap on an individual user basis, or edit the systemwide <tt>/etc/X11/Xmodmap</tt> file to contain the line
<pre>
keycode 239 = XF86LaunchA
</pre>
If you choose to go with the former, you may need to run <tt>xmodmap ~/.Xmodmap</tt> for every login session in order to read in your ~/.Xmodmap file if your window manager does not do it for you. Regardless of which option you choose, you can run <tt>xmodmap <file></tt> to read in the updated Xmodmap file without logging out and logging back in.

You should now find that hitting the ThinkVantage button creates the following output from <tt>xev</tt>:
<pre>
KeyPress event, serial 55, synthetic NO, window 0x2800001,
root 0x6a, subw 0x0, time 2001286078, (0,106), root:(643,523),
state 0x0, keycode 239 (keysym 0x1008ff4a, XF86LaunchA), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 55, synthetic NO, window 0x2800001,
root 0x6a, subw 0x0, time 2001286078, (0,106), root:(643,523),
state 0x0, keycode 239 (keysym 0x1008ff4a, XF86LaunchA), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
</pre>
Note the change of <tt>(keysym 0x0, NoSymbol)</tt> to <tt>(keysym 0x1008ff4a, XF86LaunchA)</tt>.

You're now ready to map <tt>XF86LaunchA</tt> to executing xmms. This is highly dependent on what keygrabber you decide to use. For openbox, I edit my <tt>~/.config/openbox/rc.xml</tt> file and add the following entry in the <keyboard> section:
<pre>
<keybind key="XF86LaunchA">
<action name="Execute">
<startupnotify>
<enabled>true</enabled>
</startupnotify>
<command>
xmms
</command>
</action>
</keybind>
</pre>
After, right clicking on the desktop and selecting the "Reconfigure" menu option, you should then have xmms pop up when you hit the ThinkVantage key.

==Example Applications==
===Web Browsers===
====Firefox (<3.0)====

There are various ways to assign actions to the browser keys. The easiest way is to install [http://mozilla.dorando.at/keyconfig.xpi keyconfig.xpi] from http://mozilla.dorando.at, which adds a menu entry Tools->Keyconfig. Then you can assign any action you want to the F19/F20 keys (you still need to create {{path|~/.Xmodmap}} as explained above).

The remaining discussion gives you various more complicated ways to achieve the same thing.
To have firefox make use of the browser keys you need to modify one of its files{{footnote|4}}.
To do this you will first need to extract it from the {{path|browser.jar}} archive. Do...

Step 1: Edit .Xmodmap and add entries for F19 and F20 as explained above.

Step 2:

Note: <firefox-directory> is probably /usr/lib/firefox. Use your version so, if you have 3.0.1 or 3.0.2 use /usr/lib/firefox-3.0.1

:{{cmdroot|cd <firefox-directory>/chrome}} 
:{{cmdroot|unzip browser.jar}}

The file of interest is {{path|content/browser/browser.xul}}. Edit it {and don't forget to make a backup copy first}...
:{{cmdroot|vi content/browser/browser.xul}}

Look for the '''<keyset id="mainKeyset">''' section and add the following lines within...
<key id="goBackKb" keycode="VK_F19" command="Browser:Back" />
<key id="goForwardKb" keycode="VK_F20" command="Browser:Forward" />

The Command you need for Next Tab
<key id="goBackTabKb" keycode="VK_F19" oncommand="gBrowser.mTabContainer.advanceSelectedTab(-1)" />
For the Previous Tab
<key id="goForwardTabKb" keycode="VK_F20" oncommand="gBrowser.mTabContainer.advanceSelectedTab(1)" />

Now save the file and repackage the {{path|browser.jar}} archive...
:{{cmdroot|zip -rD0 browser.jar content/browser/}}

That's it.

Step 3: Restart Firefox.

{{HINT|Outdated: Another interesting Page on Firefox is http://dqd.com/~mayoff/notes/thinkpad/dqdnavkeys/ It uses different key mappings (F19 resp. F20) but a ready [http://dqd.com/~mayoff/notes/thinkpad/dqdnavkeys/dqdnavkeys-1.2.xpi .xpi] is provided which is pretty comfortable. However, this xpi file does not install on Firefox 1.5. or later.}}

{{HINT| You can also use the [http://extensionroom.mozdev.org/more-info/keyconfig keyconfig] extension to configure custom keys. This extension works with Firefox 1.5 and also with Firefox 2.0. The Command you need for Next Tab is gBrowser.mTabContainer.advanceSelectedTab(1,true); For Previous Tab its gBrowser.mTabContainer.advanceSelectedTab(-1,true); You can alternatively install the [http://www.pqrs.org/~tekezo/firefox/extensions/functions_for_keyconfig/index.html functions for keyconfig] and set the variable f4kc_NextTab to F20 and f4kc_PrevTab to F19.}}.

====Firefox 3.0====
Thankfully the people at Mozilla decided to include the expected functionality for the XF86Back and XF86Forward keysyms in the new release so all you need to do is
 <code># printf 'keycode 234 = XF86Back\nkeycode 233 = XF86Forward' >> /etc/X11/Xmodmap</code> 
And to make this take effect immediately (i.e., without having to log out and log in again), as a regular user run:
 <code>{{cmduser|Xmodmap /etc/X11/Xmodmap}}</code>

For Hardy Heron, the xmodmap command is all lowercase. Also, the /etc/X11/Xmodmap file is not being read on boot. I've added the command to my .bashrc to have it called on startup.

====Konqueror====
KDE allows you set key mappings for KDE applications (Go to KMenu > System > Control Center > Regional & Accessibility > Keyboard Shortcuts). By default (at least in KDE 3.5), XF86Back and XF86Forward are set as alternatives to Alt-Left and Alt-Right, and are mapped to KDE Back and Forward navigation actions.

If you use Konqueror as your only browser, you only need to set up {{path|~/.Xmodmap}} as described [[#xmodmap configuration|above]] to assign ThinkPad back/forward keys to the symbols XF86Back/XF86Forward. This also make these keys work for other KDE applications such as Quanta Plus, KPackage and so on (not all KDE applications honor this setting, e.g. KDE help system doesn't).

If you want to use Firefox, however, the above settings do not work. You will have to map ThinkPad back/forward keys to F19/F20 as described [[#Firefox|above]], and change KDE navigation key settings to use F19/F20 instead of the default.

====Opera====
However this isn't a simple configration file, you can set your browser manually. 
Go to Tool > Settings > Mouse and keyboard > Keyboard settings > Edit > Browser Window. There add F19 - Back and F20 - Forward. Now you can surf using your TP keys ;-)

====Epiphany====
To get the keys work in epiphany, you could use the extension from [http://crashman.homelinux.org/~andre/public/epiphany%20extensions/thinkpad%20browserkeys/ here]
You just need to edit your Xmodmap like described for Firefox < 3.0 (bind the keys on F19 and F20)

===Open an application===

To configure the ThinkVantage button to open a terminal window in Gnome:

Step 1:
Use xev to find the keycode generated by the button on your machine. In my case is is 159.

Step 2:
Create an entry in .Xmodmap like so

keycode 159 = XF86LaunchA

replacing 159 by the keycode found in step 1. Load the map using

:{{cmd|xmodmap ~/.Xmodmap}}

Step 3:
Configure the required function (e.g. open terminal window) in System->Preferences->Keyboard shortcuts

===Window Managers===
====fvwm====
To get the {{ibmkey|Forward|#494949}} and {{ibmkey|Backward|#494949}} keys to cycle through pages in the virtual desktop, add this to your {{path|~/.fvwmrc}}:
Key XF86Back A A Scroll -100000 0
Key XF86Forward A A Scroll +100000 0
If you use multiple virtual desktops, you could instead use the keys to flip between them by using GotoDesk.

====fluxbox====
To get the keys to cycle through pages in the virtual desktop, add this to your {{path|~/.fluxbox/keys}}:
None F19 :PrevWorkspace
None F20 :NextWorkspace

====pekwm configuration====
You can make the two browser keys switch workspaces in pekwm, by adding the following two lines to the {{path|~/.pekwm/keys}} file:
KeyPress = "Mod1 XF86Back" { Actions = "GoToWorkspace prev" }
KeyPress = "Mod1 XF86Forward" { Actions = "GoToWorkspace next" }

====pwm====
Another example how to use these two keys to switch between pwm tabs. These two lines should be added to {{path|~/.pwm/keys-default.conf}} or {{path|/etc/pwm/keys-default.conf}}:
kbind "Back", "switch_rot", -1
kbind "Forward", "switch_rot", 1

====IceWM====
To make IceWM cycle workspaces using the {{ibmkey|Forward|#494949}} and {{ibmkey|Backward|#494949}} keys, change these two options in {{path|~/.icewm/preferences}} (Provided you assigned keysyms F19 and F20 with xmodmap):
# "Previous workspace" shortcut
KeySysWorkspacePrev="F19"
# "Next workspace" shortcut
KeySysWorkspaceNext="F20"

==== Gnome/metacity ====

Follow the [https://wiki.ubuntu.com/Keybindings Ubuntu guide].

===Other Uses===
====Console tools configuraton====
To make the {{ibmkey|Forward|#494949}} and {{ibmkey|Backward|#494949}} keys useful in console, add this to your keymap ({{path|/etc/console/boottime.kmap.gz}} in {{Debian}}):
keycode 158 = Decr_Console
keycode 159 = Incr_Console

Alternatively you can load this script (perhaps on system startup) to enable Backward/Forward button console (VT) switch:

#!/bin/sh
echo keycode 158 = Decr_Console | loadkeys
echo keycode 159 = Incr_Console | loadkeys

It should work with any distro.

====Cycling through tabs====
In Gnome and Xfce4, Ctrl-PageUp/Ctrl-PageDown move to the previous/following open tab in all applications that have tabbed user interfaces (terminal emulator, web browser, ...). To make use of the {{ibmkey|Forward|#494949}} and {{ibmkey|Backward|#494949}} keys for this task, there're two possibilities.

For both ways, you should map the keycodes 233 and 234 to XF86Back and XF86Forward as described in [[#xmodmap_configuration|xmodmap configuration]].

=====Using xautomation=====
xautomation can be found [http://hoopajoo.net/projects/xautomation.html here].

Create two files with permissions 755:

{{path|/usr/local/bin/tp_back}}:
<bash>
#!/bin/bash
/usr/bin/xte 'keydown Control_L' 'keydown Page_Up' 'keyup Page_Up' 'keyup Control_L'
</bash>

{{path|/usr/local/bin/tp_forward}}:
<bash>
#!/bin/bash
/usr/bin/xte 'keydown Control_L' 'keydown Page_Down' 'keyup Page_Down' 'keyup Control_L'
</bash>

Use your desktop's keyboard shortcut editor to assign XF86Back as a shortcut for tp_back and XF86Forward as a shortcut for tp_forward.

This should work in all distros and with all window managers (you might have to use other key combinations than Ctrl-PageUp and Ctrl-PageDown).

=====Redirecting XF86Back/XF86Forward=====
Create {{path|/etc/X11/xkb/compat/thinkpad}}:
<pre>
// $XFree86$
// XFree86 special keysyms
default partial xkb_compatibility "basic" {
interpret.repeat= True;

interpret XF86Back {
action = Redirect(Key=<PGUP>, modifiers=Control);
};
interpret XF86Forward {
action = Redirect(Key=<PGDN>, modifiers=Control);
};
};
</pre>

Edit {{path|/etc/X11/xkb/compat/complete}} and add <tt>'''augment "thinkpad"'''</tt> so that it looks similar to the following:
<pre>
// $XKeyboardConfig: xkbdesc/compat/complete,v 1.3 2005/10/17 00:42:11 svu Exp $
// $Xorg: complete,v 1.3 2000/08/17 19:54:34 cpqbld Exp $
default xkb_compatibility "complete" {
include "basic"
augment "iso9995"
augment "mousekeys"
augment "accessx(full)"
augment "misc"
augment "xfree86"
augment "level5"
augment "thinkpad"
};
</pre>

==External Sources==
*[http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-51537 IBMs page on configuring the ThinkPad buttons (ThinkPad, Access IBM, Mail, Search, and Home buttons) under Linux]
*[http://dqd.com/~mayoff/notes/thinkpad/dqdnavkeys/ Rob Mayoffs page on using IBM Keyboard Navigation Keys in Linux Mozilla and Firefox]
*[http://snarfed.org/space/thinkpad+keys+in+firefox Ryan Barretts blog article about using the browser keys in Firefox]
*[http://chaotika.org/~bluesceada/?page=soft&sub=thinkpad#acpibutn DennisG's help to get the ibm-acpi buttons do useful things] on a {{Z61e}} and possibly {{Z61m}}, {{Z61t}} and {{Z61p}}

{{footnotes|
#Note that the associated functionality for Fn-F* key combinations is not consistent amongst all ThinkPads. We are maintaining [[Default meanings of special keys|a table of associated meanings]].
#if there are more than one tool listed, one is sufficient
#'full' means you can completely reassign any action to be triggered by the key, 'additional actions' means you can trigger actions in addition to the standard function of the key, which can not be changed.
#Thanks go to Ryan Barrett for writing the [http://snarfed.org/space/thinkpad+keys+in+firefox little howto] on [http://snarfed.org/space/start his blog].
}}

Harddrive Upgrade

2008-12-10T20:04:55Z

Low: /* Howto */

= Why? =

* More capacity
* Quieter drives
* Faster drives
* To replace a malfunctioning drive

= Options =

[http://www.seagate.com/www/en-us/products/laptops/momentus/ Seagate Momentus] 2.5-inch notebook drives are highly recommended.

= Howto =

# Buy the upgrade
# Buy a USB enclosure ~10USD
# Mount upgrade in the USB enclosure
# Boot with a liveCD such as Knoppix or Ubuntu's LiveCD

Normally your hard drive would be /dev/hda and your external USB hard drive upgrade should be /dev/sda. Check with `dmesg` if this is the case. There is [http://thinkwiki.org/wiki/How_to_copy_a_Linux_installation several different irksome ways to migrate your data to the upgrade.] I've performed the `cat` method:

cat /dev/hda > /dev/sda

This can take as much as an entire day to perform, depending on the size of your original hard drive. You can work out how long it takes if you know the USB throughput.

And then resize the partition with the tool `parted`. This takes far less time thankfully, 30 minutes in my case.

Now the tricky part, [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-42410 taking your hard drive out and replacing it with the upgrade.]

# Shutdown the machine, disconnect from the mains and take out the battery.
# Take the upgrade out the USB enclosure. In my case my upgrade got stuck in the USB enclosure. Be wary of these types of awful situations!
# With a good Philips screw driver remove the hard drive. Refer to [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-42410 IBM's documentation how to do this.] My tips are to have the lid open when performing this. The hard drive is mounted typically just above your audio jacks - though this depends on your model. Again, check IBM's documentation - there's also step by step instructions available.
# The side panel covering on the hard drive mount clips off and now mounting the new upgrade should be straight forward.
# You need to put the b(l)ack panel back on the mount, otherwise it is very difficult to get the hard drive out of Thinkpad's enclosure.
# Once the swap is complete you should be able to boot into your new hard drive. Thinkpads typically automagically detect the hard drive so, that's it!

= Source=

* http://natalian.org/archives/2006/02/03/dreading-the-upgrade/