ThinkWiki - User contributions [en]

Talk:How to get special keys to work

2009-08-03T09:20:50Z

Rdskaroff:

__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]]

== Who is the boss? Your Thinkpad's special keys or you? ==

The x tools setxkbmap and xbindkeys along with the kde 3.5 control center keyboard shortcuts and application links in ~/.kde/Autostart are the tools that I use to do every keyboard thing I want with my

----

* R61 7732-CTO

* BIOS 7LETC4WW (2.24), EC 7KHT24WW-1.08

* Intel(R) Core(TM)2 Duo CPU T5470 @ 1.60GHz, stepping 0d

* 4G Mushkin RAM

* 320G WDC WD3200BEKT

* Linux version 2.6.30-4-amd64

* kde 3.5.10

* Debian Stable

* Number of Packages: stable 1473, testing 473, unstable 199

----

You may also find xmodmap useful, I didn't.

check out:

http://www.palmix.org/xmodmap-en.html

http://xorg.freedesktop.org/archive/X11R7.0/doc/html/setxkbmap.1.html

https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch

man setxkbmap

man xbindkeys

man xbindkeys-config

anything else you need would be in /usr/share/doc/ on Debian

You must! learn to use Google effectively

An important command for getting this together was on the HotkeyResearch page:

xev | grep -A2 --line-buffered '^KeyRelease' | sed -n '/keycode /s/^.*keycode $[0-9]*$.* (.*, $.*$).*$/\1 \2/p'

It told me which fn-{key} had keycodes and what they were. I was surprised to find that some didn't have keycodes.

Here's the way to do it:

1) read the above references!! don't email me with questions that have answers in the text.

2) set your keyboard properly. I looked at /etc/X11/xkb/base.xml <name> tag values, then created in ~/.kde/Autostart with konqueror a "link to application" for the statement 'setxkbmap -model thinkpad60 -layout us'

3) use the above xev|etc. command to find the keycodes for the keys you need to map.

4) for fun you can look at the keycode to keysym correspondences that exist currently by executing xmodmap -pk at the command line

5) you may have to create an ~/.xmodmap with the keycode to keysym additions or modifications, I didn't

6) determine what functionality you want the key combinations to provide

7) use kde keyboard shortcuts to map key combinations (ex fn-F5) to your shortcut scheme. If it doesn't have something you want, like control of amarok with the multimedia keys you either need to create a menu item for the application and a command shortcut or you can use xbindkeys-config to do it. You can't do both.

8) I used xbindkeys-config for a few things but it became a little difficult to use so I created menu items. I later realized that xbindkeys-config and xev didn't see the same keys. I had to map fn-F4 with xbindkeys-config and fn-F12 with a command shortcut.

9) the amarok controller I used is remoot, just search for it, it isn't in Debian, but a Debian package is available

I will be writing sometime soon on suspension/hibernation. I use pm-suspend and pm-hibernate, which are in the pm-utils Debian package. If I can figure it out, you can too. Read the documentation.

Dare to be great! Kick butt!

[[User:rdskaroff+debian@gmail.com|Bob]]

Talk:How to get special keys to work

2009-08-02T19:02:13Z

Rdskaroff: /* Some links and info */

__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]]

== Who is the boss? Your Thinkpad's special keys or you? ==

The x tools setxkbmap and xbindkeys along with the kde 3.5 control center keyboard shortcuts and application links in ~/.kde/Autostart are the tools that I use to do every keyboard thing I want with my

----

R61 7732-CTO,

BIOS 7LETC4WW (2.24), EC 7KHT24WW-1.08,

Intel(R) Core(TM)2 Duo CPU T5470 @ 1.60GHz, stepping 0d,

4G Mushkin RAM,

320G WDC WD3200BEKT,

Linux version 2.6.30-4-amd64,

kde 3.5.10,

Packages: stable 1473, testing 473, unstable 199

----

You may also find xmodmap useful, I didn't.

check out:

http://www.palmix.org/xmodmap-en.html

http://xorg.freedesktop.org/archive/X11R7.0/doc/html/setxkbmap.1.html

https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch

man setxkbmap

man xbindkeys

man xbindkeys-config

anything else you need would be in /usr/share/doc/ on Debian

You must! learn to use Google effectively

An important command for getting this together was on the HotkeyResearch page:

xev | grep -A2 --line-buffered '^KeyRelease' | sed -n '/keycode /s/^.*keycode $[0-9]*$.* (.*, $.*$).*$/\1 \2/p'

It told me which fn-{key} had keycodes and what they were. I was surprised to find that some didn't have keycodes.

Here's the way to do it:

1) read the above references!! don't email me with questions that have answers in the text.

2) set your keyboard properly. I looked at /etc/X11/xkb/base.xml <name> tag values, then created in ~/.kde/Autostart with konqueror a "link to application" for the statement 'setxkbmap -model thinkpad60 -layout us'

3) use the above xev|etc. command to find the keycodes for the keys you need to map.

4) for fun you can look at the keycode to keysym correspondences that exist currently by executing xmodmap -pk at the command line

5) you may have to create an ~/.xmodmap with the keycode to keysym additions or modifications, I didn't

6) determine what functionality you want the key combinations to provide

7) use kde keyboard shortcuts to map key combinations (ex fn-F5) to your shortcut scheme. If it doesn't have something you want, like control of amarok with the multimedia keys you either need to create a menu item for the application and a command shortcut or you can use xbindkeys-config to do it. You can't do both.

8) I used xbindkeys-config for a few things but it became a little difficult to use so I created menu items. I later realized that xbindkeys-config and xev didn't see the same keys. I had to map fn-F4 with xbindkeys-config and fn-F12 with a command shortcut.

9) the amarok controller I used is remoot, just search for it, it isn't in Debian, but a Debian package is available

I will be writing sometime soon on suspension/hibernation. I use pm-suspend and pm-hibernate, which are in the pm-utils Debian package. If I can figure it out, you can too. Read the documentation.

Dare to be great! Kick butt!

[[User:rdskaroff+debian@gmail.com|Bob]]

Talk:How to get special keys to work

2009-08-02T18:54:27Z

Rdskaroff: /* Some links and info */

__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]]

== Some links and info ==

The x tools setxkbmap and xbindkeys along with the kde 3.5 control center keyboard shortcuts and application links in ~/.kde/Autostart are the tools that I use to do every keyboard thing I want with my

----

R61 7732-CTO,

BIOS 7LETC4WW (2.24), EC 7KHT24WW-1.08,

Intel(R) Core(TM)2 Duo CPU T5470 @ 1.60GHz, stepping 0d,

4G Mushkin RAM,

320G WDC WD3200BEKT,

Linux version 2.6.30-4-amd64,

kde 3.5.10,

Packages: stable 1473, testing 473, unstable 199

----

You may also find xmodmap useful, I didn't.

check out:

http://www.palmix.org/xmodmap-en.html

http://xorg.freedesktop.org/archive/X11R7.0/doc/html/setxkbmap.1.html

https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch

man setxkbmap

man xbindkeys

man xbindkeys-config

anything else you need would be in /usr/share/doc/ on Debian

You must! learn to use Google effectively

An important command for getting this together was on the HotkeyResearch page:

xev | grep -A2 --line-buffered '^KeyRelease' | sed -n '/keycode /s/^.*keycode $[0-9]*$.* (.*, $.*$).*$/\1 \2/p'

It told me which fn-{key} had keycodes and what they were. I was surprised to find that some didn't have keycodes.

Here's the way to do it:

1) read the above references!! don't email me with questions that have answers in the text.

2) set your keyboard properly. I looked at /etc/X11/xkb/base.xml <name> tag values, then created in ~/.kde/Autostart with konqueror a "link to application" for the statement 'setxkbmap -model thinkpad60 -layout us'

3) use the above xev|etc. command to find the keycodes for the keys you need to map.

4) for fun you can look at the keycode to keysym correspondences that exist currently by executing xmodmap -pk at the command line

5) you may have to create an ~/.xmodmap with the keycode to keysym additions or modifications, I didn't

6) determine what functionality you want the key combinations to provide

7) use kde keyboard shortcuts to map key combinations (ex fn-F5) to your shortcut scheme. If it doesn't have something you want, like control of amarok with the multimedia keys you either need to create a menu item for the application and a command shortcut or you can use xbindkeys-config to do it. You can't do both.

8) I used xbindkeys-config for a few things but it became a little difficult to use so I created menu items. I later realized that xbindkeys-config and xev didn't see the same keys. I had to map fn-F4 with xbindkeys-config and fn-F12 with a command shortcut.

9) the amarok controller I used is remoot, just search for it, it isn't in Debian, but a Debian package is available

I will be writing sometime soon on suspension/hibernation. I use pm-suspend and pm-hibernate, which are in the pm-utils Debian package. If I can figure it out, you can too. Read the documentation.

Dare to be great! Kick butt!

[[User:rdskaroff+debian@gmail.com|Bob]]

Talk:How to get special keys to work

2009-08-02T18:53:03Z

Rdskaroff: /* Some links and info */

__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]]

== Some links and info ==

The x tools setxkbmap and xbindkeys along with the kde 3.5 control center keyboard shortcuts and application links in ~/.kde/Autostart are the tools that I use to do every keyboard thing I want with my

----

R61 7732-CTO,

BIOS 7LETC4WW (2.24), EC 7KHT24WW-1.08,

Intel(R) Core(TM)2 Duo CPU T5470 @ 1.60GHz, stepping 0d,

4G Mushkin RAM,

320G WDC WD3200BEKT,

Linux version 2.6.30-4-amd64,

kde 3.5.10,

Packages: stable 1473, testing 473, unstable 199

----

You may also find xmodmap useful, I didn't.

check out:

http://www.palmix.org/xmodmap-en.html

http://xorg.freedesktop.org/archive/X11R7.0/doc/html/setxkbmap.1.html

https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch

man setxkbmap

man xbindkeys

man xbindkeys-config

anything else you need would be in /usr/share/doc/ on Debian

You must! learn to use Google effectively

An important command for getting this together was on the HotkeyResearch page:

xev | grep -A2 --line-buffered '^KeyRelease' | sed -n '/keycode /s/^.*keycode $[0-9]*$.* (.*, $.*$).*$/\1 \2/p'

It told me which fn-{key} had keycodes and what they were. I was surprised to find that some didn't have keycodes.

Here's the way to do it:

1) read the above references!! don't email me with questions that have answers in the text.

2) set your keyboard properly. I looked at /etc/X11/xkb/base.xml <name> tag values, then created in ~/.kde/Autostart with konqueror a "link to application" for the statement 'setxkbmap -model thinkpad60 -layout us'

3) use the above xev|etc. command to find the keycodes for the keys you need to map.

4) for fun you can look at the keycode to keysym correspondences that exist currently by executing xmodmap -pk at the command line

5) you may have to create an ~/.xmodmap with the keycode to keysym additions or modifications, I didn't

6) determine what functionality you want the key combinations to provide

7) use kde keyboard shortcuts to map key combinations (ex fn-F5) to your shortcut scheme. If it doesn't have something you want, like control of amarok with the multimedia keys you either need to create a menu item for the application and a command shortcut or you can use xbindkeys-config to do it.

8) I used xbindkeys-config for a few things but it became a little difficult to use so I created menu items. I later realized that xbindkeys-config and xev didn't see the same keys. I had to map fn-F4 with xbindkeys-config and fn-F12 with a command shortcut.

9) the amarok controller I used is remoot, just search for it, it isn't in Debian, but a Debian package is available

I will be writing sometime soon on suspension/hibernation. I use pm-suspend and pm-hibernate, which are in the pm-utils Debian package. If I can figure it out, you can too. Read the documentation.

Dare to be great! Kick butt!

[[User:rdskaroff+debian@gmail.com|Bob]]

Talk:How to get special keys to work

2009-08-02T18:51:56Z

Rdskaroff: /* Some links and info */

__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]]

== Some links and info ==

The x tools setxkbmap and xbindkeys along with the kde 3.5 control center keyboard shortcuts and application links in ~/.kde/Autostart are the tools that I use to do every keyboard thing I want with my

----

R61 7732-CTO,

BIOS 7LETC4WW (2.24), EC 7KHT24WW-1.08,

Intel(R) Core(TM)2 Duo CPU T5470 @ 1.60GHz, stepping 0d,

4G Mushkin RAM,

320G WDC WD3200BEKT,

Linux version 2.6.30-4-amd64,

kde 3.5.10,

Packages: stable 1473, testing 473, unstable 199

----

You may also find xmodmap useful, I didn't.

check out:

http://www.palmix.org/xmodmap-en.html

http://xorg.freedesktop.org/archive/X11R7.0/doc/html/setxkbmap.1.html

https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch

man setxkbmap

man xbindkeys

man xbindkeys-config

anything else you need would be in /usr/share/doc/ on Debian

You must! learn to use Google effectively

An important command for getting this together was on the HotkeyResearch page:

xev | grep -A2 --line-buffered '^KeyRelease' | sed -n '/keycode /s/^.*keycode $[0-9]*$.* (.*, $.*$).*$/\1 \2/p'

It told me which fn-{key} had keycodes and what they were. I was surprised to find that some didn't have keycodes.

Here's the way to do it:

1) read the above references!! don't email me with questions that have answers in the text.

2) set your keyboard properly. I looked at /etc/X11/xkb/base.xml <name> tag values, then created in ~/.kde/Autostart with konqueror a "link to application" to the statement 'setxkbmap -model thinkpad60 -layout us'

3) use the above xev|etc. command to find the keycodes for the keys you need to map.

4) for fun you can look at the keycode to keysym correspondences that exist currently by executing xmodmap -pk at the command line

5) you may have to create an ~/.xmodmap with the keycode to keysym additions or modifications, I didn't

6) determine what functionality you want the key combinations to provide

7) use kde keyboard shortcuts to map key combinations (ex fn-F5) to your shortcut scheme. If it doesn't have something you want, like control of amarok with the multimedia keys you either need to create a menu item for the application and a command shortcut or you can use xbindkeys-config to do it.

8) I used xbindkeys-config for a few things but it became a little difficult to use so I created menu items. I later realized that xbindkeys-config and xev didn't see the same keys. I had to map fn-F4 with xbindkeys-config and fn-F12 with a command shortcut.

9) the amarok controller I used is remoot, just search for it, it isn't in Debian, but a Debian package is available

I will be writing sometime soon on suspension/hibernation. I use pm-suspend and pm-hibernate, which are in the pm-utils Debian package. If I can figure it out, you can too. Read the documentation.

Dare to be great! Kick butt!

[[User:rdskaroff+debian@gmail.com|Bob]]

Talk:How to get special keys to work

2009-08-02T18:51:29Z

Rdskaroff: /* Some links and info */

__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]]

== Some links and info ==

The x tools setxkbmap and xbindkeys along with the kde 3.5 control center keyboard shortcuts and application links in ~/.kde/Autostart are the tools that I use to do every keyboard thing I want with my

----

R61 7732-CTO,

BIOS 7LETC4WW (2.24), EC 7KHT24WW-1.08,

Intel(R) Core(TM)2 Duo CPU T5470 @ 1.60GHz, stepping 0d,

4G Mushkin RAM,

320G WDC WD3200BEKT,

Linux version 2.6.30-4-amd64,

kde 3.5.10,

Packages: stable 1473, testing 473, unstable 199

----

You may also find xmodmap useful, I didn't.

check out:

http://www.palmix.org/xmodmap-en.html

http://xorg.freedesktop.org/archive/X11R7.0/doc/html/setxkbmap.1.html

https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch

man setxkbmap

man xbindkeys

man xbindkeys-config

anything else you need would be in /usr/share/doc/ on Debian

You must! learn to use Google effectively

An important command for getting this together was on the HotkeyResearch page:

xev | grep -A2 --line-buffered '^KeyRelease' | sed -n '/keycode /s/^.*keycode $[0-9]*$.* (.*, $.*$).*$/\1 \2/p'

It told me which fn-{key} had keycodes and what they were. I was surprised to find that some didn't have keycodes.

Here's the way to do it:

1) read the above references!! don't email me with questions that have answers in the text.

2) set your keyboard properly. I looked at /etc/X11/xkb/base.xml <name> tag values, then created in ~/.kde/Autostart with konqueror a "link to application" to the statement 'setxkbmap -model thinkpad60 -layout us'

3) use the above xev|etc. command to find the keycodes for the keys you need to map.

4) for fun you can look at the keycode to keysym correspondences that exist currently by executing xmodmap -pk at the command line

5) you may have to create an ~/.xmodmap with the keycode to keysym additions or modifications, I didn't

6) determine what functionality you want the key combinations to provide

7) use kde keyboard shortcuts to map key combinations (ex fn-F5) to your shortcut scheme. If it doesn't have something you want, like control of amarok with the multimedia keys you either need to create a menu item for the application and a command shortcut or you can use xbindkeys-config to do it.

8) I used xbindkeys-config for a few things but it became a little difficult to use so I created menu items. I later realized that xbindkeys-config and xev didn't see the same keys. I had to map fn-F4 with xbindkeys-config and fn-F12 with a command shortcut.

9) the amarok controller I used is remoot, just search for it, it isn't in Debian, but a Debian package is available

I will be writing sometime soon on suspension/hibernation. I use pm-suspend and pm-hibernate, which are in the pm-utils Debian package. If I can figure it out, you can too. Read the documentation.

Dare to be great! Kick butt!

[[User:rdskaroff+debian@gmail.com|Bob]]

Talk:How to get special keys to work

2009-08-02T18:50:08Z

Rdskaroff: /* Some links and info */

__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]]

== Some links and info ==

The x tools setxkbmap and xbindkeys along with the kde 3.5 control center keyboard shortcuts and application links in ~/.kde/Autostart are the tools that I use to do every keyboard thing I want with my

----

R61 7732-CTO,

BIOS 7LETC4WW (2.24), EC 7KHT24WW-1.08,

Intel(R) Core(TM)2 Duo CPU T5470 @ 1.60GHz, stepping 0d,

4G Mushkin RAM,

320G WDC WD3200BEKT,

Linux version 2.6.30-4-amd64,

kde 3.5.10,

Packages: stable 1473, testing 473, unstable 199

----

You may also find xmodmap useful, I didn't.

check out:

http://www.palmix.org/xmodmap-en.html

http://xorg.freedesktop.org/archive/X11R7.0/doc/html/setxkbmap.1.html

https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch

man setxkbmap

man xbindkeys

man xbindkeys-config

anything else you need would be in /usr/share/doc/ on Debian or Google

An important command for getting this together was on the HotkeyResearch page:

xev | grep -A2 --line-buffered '^KeyRelease' | sed -n '/keycode /s/^.*keycode $[0-9]*$.* (.*, $.*$).*$/\1 \2/p'

It told me which fn-{key} had keycodes and what they were. I was surprised to find that some didn't have keycodes.

Here's the way to do it:

1) read the above references!! don't email me with questions that have answers in the text.

2) set your keyboard properly. I looked at /etc/X11/xkb/base.xml <name> tag values, then created in ~/.kde/Autostart with konqueror a "link to application" to the statement 'setxkbmap -model thinkpad60 -layout us'

3) use the above xev|etc. command to find the keycodes for the keys you need to map.

4) for fun you can look at the keycode to keysym correspondences that exist currently by executing xmodmap -pk at the command line

5) you may have to create an ~/.xmodmap with the keycode to keysym additions or modifications, I didn't

6) determine what functionality you want the key combinations to provide

7) use kde keyboard shortcuts to map key combinations (ex fn-F5) to your shortcut scheme. If it doesn't have something you want, like control of amarok with the multimedia keys you either need to create a menu item for the application and a command shortcut or you can use xbindkeys-config to do it.

8) I used xbindkeys-config for a few things but it became a little difficult to use so I created menu items. I later realized that xbindkeys-config and xev didn't see the same keys. I had to map fn-F4 with xbindkeys-config and fn-F12 with a command shortcut.

9) the amarok controller I used is remoot, just search for it, it isn't in Debian, but a Debian package is available

I will be writing sometime soon on suspension/hibernation. I use pm-suspend and pm-hibernate, which are in the pm-utils Debian package. If I can figure it out, you can too. Read the documentation.

Dare to be great! Kick butt!

[[User:rdskaroff+debian@gmail.com|Bob]]

Talk:How to get special keys to work

2009-08-02T18:49:38Z

Rdskaroff: /* Some links and info */

__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]]

== Some links and info ==

The x tools setxkbmap and xbindkeys along with the kde 3.5 control center keyboard shortcuts and application links in ~/.kde/Autostart are the tools that I use to do every keyboard thing I want with my

----

R61 7732-CTO,

BIOS 7LETC4WW (2.24), EC 7KHT24WW-1.08,

Intel(R) Core(TM)2 Duo CPU T5470 @ 1.60GHz, stepping 0d,

4G Mushkin RAM,

320G WDC WD3200BEKT,
Linux version 2.6.30-4-amd64,

kde 3.5.10,

Packages: stable 1473, testing 473, unstable 199

----

You may also find xmodmap useful, I didn't.

check out:

http://www.palmix.org/xmodmap-en.html

http://xorg.freedesktop.org/archive/X11R7.0/doc/html/setxkbmap.1.html

https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch

man setxkbmap

man xbindkeys

man xbindkeys-config

anything else you need would be in /usr/share/doc/ on Debian or Google

An important command for getting this together was on the HotkeyResearch page:

xev | grep -A2 --line-buffered '^KeyRelease' | sed -n '/keycode /s/^.*keycode $[0-9]*$.* (.*, $.*$).*$/\1 \2/p'

It told me which fn-{key} had keycodes and what they were. I was surprised to find that some didn't have keycodes.

Here's the way to do it:

1) read the above references!! don't email me with questions that have answers in the text.

2) set your keyboard properly. I looked at /etc/X11/xkb/base.xml <name> tag values, then created in ~/.kde/Autostart with konqueror a "link to application" to the statement 'setxkbmap -model thinkpad60 -layout us'

3) use the above xev|etc. command to find the keycodes for the keys you need to map.

4) for fun you can look at the keycode to keysym correspondences that exist currently by executing xmodmap -pk at the command line

5) you may have to create an ~/.xmodmap with the keycode to keysym additions or modifications, I didn't

6) determine what functionality you want the key combinations to provide

7) use kde keyboard shortcuts to map key combinations (ex fn-F5) to your shortcut scheme. If it doesn't have something you want, like control of amarok with the multimedia keys you either need to create a menu item for the application and a command shortcut or you can use xbindkeys-config to do it.

8) I used xbindkeys-config for a few things but it became a little difficult to use so I created menu items. I later realized that xbindkeys-config and xev didn't see the same keys. I had to map fn-F4 with xbindkeys-config and fn-F12 with a command shortcut.

9) the amarok controller I used is remoot, just search for it, it isn't in Debian, but a Debian package is available

I will be writing sometime soon on suspension/hibernation. I use pm-suspend and pm-hibernate, which are in the pm-utils Debian package. If I can figure it out, you can too. Read the documentation.

Dare to be great! Kick butt!

[[User:rdskaroff+debian@gmail.com|Bob]]

Talk:How to get special keys to work

2009-08-02T18:18:50Z

Rdskaroff: /* Some links and info */

__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]]

== Some links and info ==

The x tools setxkbmap and xbindkeys along with the kde 3.5 control center keyboard shortcuts and application links in ~/.kde/Autostart are the tools that I use to do every keyboard thing I want with my

R61 7732-CTO,

BIOS 7LETC4WW (2.24), EC 7KHT24WW-1.08,

Intel(R) Core(TM)2 Duo CPU T5470 @ 1.60GHz, stepping 0d,

4G Mushkin RAM,

320G WDC WD3200BEKT,
Linux version 2.6.30-4-amd64,

kde 3.5.10

You may also find xmodmap useful, I didn't.

check out:

http://www.palmix.org/xmodmap-en.html

http://xorg.freedesktop.org/archive/X11R7.0/doc/html/setxkbmap.1.html

https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch

man setxkbmap

man xbindkeys

man xbindkeys-config

anything else you need would be in /usr/share/doc/ on Debian or use Google

An important command for getting this together was on the HotkeyResearch page:

xev | grep -A2 --line-buffered '^KeyRelease' | sed -n '/keycode /s/^.*keycode $[0-9]*$.* (.*, $.*$).*$/\1 \2/p'

It told me which fn-{key} had keycodes and what they were. I was surprised to find that some didn't have keycodes.

Here's the way to do it:

1) read the above references!! don't email me with questions that have answers in the text.

2) set your keyboard properly. I looked at /etc/X11/xkb/base.xml <name> tag values, then created in ~/.kde/Autostart with konqueror a "link to application" to the statement 'setxkbmap -model thinkpad60 -layout us'

3) use the above xev|etc. command to find the keycodes for the keys you need to map.

4) look at the keycode to keysym correspondences that exist currently by executing xmodmap -pk at the command line

5) create an ~/.xmodmap with the keycode to keysym additions or modifications only if you need to.

6) determine what functionality you want the key combinations to provide

7) use kde keyboard shortcuts to map key combinations (ex fn-F5) to your shortcut scheme. If it doesn't have something you want, like control of amarok with the multimedia keys you either need to create a menu item for the application and a command shortcut or you can use xbindkeys-config to do it.

8) I used xbindkeys-config for a few things but it became a little difficult to use so I created menu items. I later realized that xbindkeys-config and xev didn't see the same keys. I had to map fn-F4 with xbindkeys-config and fn-F12 with a command shortcut.

9) the amarok controller I used is remoot, just search for it, it isn't in Debian, but a Debian package is available

I will be writing sometime soon on suspension/hibernation. I use pm-suspend and pm-hibernate, which are in the pm-utils Debian package. If I can figure it out, you can too. Read the documentation.

Dare to be great! Kick butt!

[[User:rdskaroff|Bob]]

Talk:How to get special keys to work

2009-08-02T18:16:46Z

Rdskaroff: /* Some links and info */

__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]]

== Some links and info ==

The x tools setxkbmap and xbindkeys along with the kde 3.5 control center keyboard shortcuts and application links in ~/.kde/Autostart are the tools that I use to do every keyboard thing I want with my R61 7732-CTO, BIOS 7LETC4WW (2.24 ), EC 7KHT24WW-1.08, Intel(R) Core(TM)2 Duo CPU T5470 @ 1.60GHz, stepping 0d, 4G RAM, 320G WDC WD3200BEKT, Linux version 2.6.30-4-amd64, kde

You may also find xmodmap useful, I didn't.

check out:

http://www.palmix.org/xmodmap-en.html

http://xorg.freedesktop.org/archive/X11R7.0/doc/html/setxkbmap.1.html

https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch

man setxkbmap

man xbindkeys

man xbindkeys-config

anything else you need would be in /usr/share/doc/ on Debian or use Google

An important command for getting this together was on the HotkeyResearch page:

xev | grep -A2 --line-buffered '^KeyRelease' | sed -n '/keycode /s/^.*keycode $[0-9]*$.* (.*, $.*$).*$/\1 \2/p'

It told me which fn-{key} had keycodes and what they were. I was surprised to find that some didn't have keycodes.

Here's the way to do it:

1) read the above references!! don't email me with questions that have answers in the text.

2) set your keyboard properly. I looked at /etc/X11/xkb/base.xml <name> tag values, then created in ~/.kde/Autostart with konqueror a "link to application" to the statement 'setxkbmap -model thinkpad60 -layout us'

3) use the above xev|etc. command to find the keycodes for the keys you need to map.

4) look at the keycode to keysym correspondences that exist currently by executing xmodmap -pk at the command line

5) create an ~/.xmodmap with the keycode to keysym additions or modifications only if you need to.

6) determine what functionality you want the key combinations to provide

7) use kde keyboard shortcuts to map key combinations (ex fn-F5) to your shortcut scheme. If it doesn't have something you want, like control of amarok with the multimedia keys you either need to create a menu item for the application and a command shortcut or you can use xbindkeys-config to do it.

8) I used xbindkeys-config for a few things but it became a little difficult to use so I created menu items. I later realized that xbindkeys-config and xev didn't see the same keys. I had to map fn-F4 with xbindkeys-config and fn-F12 with a command shortcut.

9) the amarok controller I used is remoot, just search for it, it isn't in Debian, but a Debian package is available

I will be writing sometime soon on suspension/hibernation. I use pm-suspend and pm-hibernate, which are in the pm-utils Debian package. If I can figure it out, you can too. Read the documentation.

Dare to be great! Kick butt!

[[User:rdskaroff|Bob]]

Talk:How to get special keys to work

2009-08-02T18:07:07Z

Rdskaroff: /* Some links and info */

__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]]

== Some links and info ==

The x tools setxkbmap and xbindkeys along with the kde 3.5 control center keyboard shortcuts and application links in ~/.kde/Autostart are the tools that I use to do every keyboard thing I want with my R61 7732-CTO.

You may also find xmodmap useful, I didn't.

check out:

http://www.palmix.org/xmodmap-en.html

http://xorg.freedesktop.org/archive/X11R7.0/doc/html/setxkbmap.1.html

https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch

man setxkbmap

man xbindkeys

man xbindkeys-config

anything else you need would be in /usr/share/doc/ on Debian or use Google

An important command for getting this together was on the HotkeyResearch page:

xev | grep -A2 --line-buffered '^KeyRelease' | sed -n '/keycode /s/^.*keycode $[0-9]*$.* (.*, $.*$).*$/\1 \2/p'

It told me which fn-{key} had keycodes and what they were. I was surprised to find that some didn't have keycodes.

Here's the way to do it:

1) read the above references!! don't email me with questions that have answers in the text.

2) set your keyboard properly. I looked at /etc/X11/xkb/base.xml <name> tag values, then created in ~/.kde/Autostart with konqueror a "link to application" to the statement 'setxkbmap -model thinkpad60 -layout us'

3) use the above xev|etc. command to find the keycodes for the keys you need to map.

4) look at the keycode to keysym correspondences that exist currently by executing xmodmap -pk at the command line

5) create an ~/.xmodmap with the keycode to keysym additions or modifications only if you need to.

6) determine what functionality you want the key combinations to provide

7) use kde keyboard shortcuts to map key combinations (ex fn-F5) to your shortcut scheme. If it doesn't have something you want, like control of amarok with the multimedia keys you either need to create a menu item for the application and a command shortcut or you can use xbindkeys-config to do it.

8) I used xbindkeys-config for a few things but it became a little difficult to use so I created menu items. I later realized that xbindkeys-config and xev didn't see the same keys. I had to map fn-F4 with xbindkeys-config and fn-F12 with a command shortcut.

9) the amarok controller I used is remoot, just search for it, it isn't in Debian, but a Debian package is available

I will be writing sometime soon on suspension/hibernation. I use pm-suspend and pm-hibernate, which are in the pm-utils Debian package. If I can figure it out, you can too. Read the documentation.

Dare to be great! Kick butt!

[[User:rdskaroff|Bob]]

Talk:How to get special keys to work

2009-08-02T18:06:31Z

Rdskaroff: /* Some links and info */

__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]]

== Some links and info ==

The x tools setxkbmap and xbindkeys along with the kde 3.5 control center keyboard shortcuts and application links in ~/.kde/Autostart are the tools that I use to do every keyboard thing I want with my R61 7732-CTO.

You may also find xmodmap useful, I didn't.

check out:

[http://www.palmix.org/xmodmap-en.html]

[http://xorg.freedesktop.org/archive/X11R7.0/doc/html/setxkbmap.1.html]

[https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch]

man setxkbmap

man xbindkeys

man xbindkeys-config

anything else you need would be in /usr/share/doc/ on Debian or use Google

An important command for getting this together was on the HotkeyResearch page:

xev | grep -A2 --line-buffered '^KeyRelease' | sed -n '/keycode /s/^.*keycode $[0-9]*$.* (.*, $.*$).*$/\1 \2/p'

It told me which fn-{key} had keycodes and what they were. I was surprised to find that some didn't have keycodes.

Here's the way to do it:

1) read the above references!! don't email me with questions that have answers in the text.

2) set your keyboard properly. I looked at /etc/X11/xkb/base.xml <name> tag values, then created in ~/.kde/Autostart with konqueror a "link to application" to the statement 'setxkbmap -model thinkpad60 -layout us'

3) use the above xev|etc. command to find the keycodes for the keys you need to map.

4) look at the keycode to keysym correspondences that exist currently by executing xmodmap -pk at the command line

5) create an ~/.xmodmap with the keycode to keysym additions or modifications only if you need to.

6) determine what functionality you want the key combinations to provide

7) use kde keyboard shortcuts to map key combinations (ex fn-F5) to your shortcut scheme. If it doesn't have something you want, like control of amarok with the multimedia keys you either need to create a menu item for the application and a command shortcut or you can use xbindkeys-config to do it.

8) I used xbindkeys-config for a few things but it became a little difficult to use so I created menu items. I later realized that xbindkeys-config and xev didn't see the same keys. I had to map fn-F4 with xbindkeys-config and fn-F12 with a command shortcut.

9) the amarok controller I used is remoot, just search for it, it isn't in Debian, but a Debian package is available

I will be writing sometime soon on suspension/hibernation. I use pm-suspend and pm-hibernate, which are in the pm-utils Debian package. If I can figure it out, you can too. Read the documentation.

Dare to be great! Kick butt!

[[User:rdskaroff|Bob]]

Talk:How to get special keys to work

2009-08-02T18:03:25Z

Rdskaroff: /* Some links and info */

__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]]

== Some links and info ==

The x tools setxkbmap and xbindkeys along with the kde 3.5 control center keyboard shortcuts and application links in ~/.kde/Autostart are the tools that I use to do every keyboard thing I want with my R61 7732-CTO.
You may also find xmodmap useful, I didn't.

check out:
[http://www.palmix.org/xmodmap-en.html]
[http://xorg.freedesktop.org/archive/X11R7.0/doc/html/setxkbmap.1.html]
[https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch]
man setxkbmap
man xbindkeys
man xbindkeys-config
anything else you need would be in /usr/share/doc/ on Debian or use Google

An important command for getting this together was on the HotkeyResearch page:

xev | grep -A2 --line-buffered '^KeyRelease' | sed -n '/keycode /s/^.*keycode $[0-9]*$.* (.*, $.*$).*$/\1 \2/p'

It told me which fn-{key} had keycodes and what they were. I was surprised to find that some didn't have keycodes.

Here's the way to do it:
1) read the above references!! don't email me qith questions that have answers in the text.
2) set your keyboard properly. I looked at /etc/X11/xkb/base.xml <name> tag values, then created in ~/.kde/Autostart with konqueror a "link to application" to the statement 'setxkbmap -model thinkpad60 -layout us'
3) use the above xev|etc. command to find the keycodes for the keys you need to map.
4) look at the keycode to keysym correspondences that exist currently by executing xmodmap -pk at the command line
5) create an ~/.xmodmap with the keycode to keysym additions or modifications only if you need to.
6) determine what functionality you want the key combinations to provide
7) use kde keyboard shortcuts to map key combinations (ex fn-F5) to your shortcut scheme. If it doesn't have something you want, like control of amarok with the multimedia keys you either need to create a menu item for the application and a command shortcut or you can use xbindkeys-config to do it.
8) I used xbindkeys-config for a few things but it became a little difficult to use so I created menu items. I later realized that xbindkeys-config and xev didn't see the same keys. I had to map fn-F4 with xbindkeys-config and fn-F12 with a command shortcut.
9) the amarok controller I used is remoot, just search for it, it isn't in Debian.

I will be writing sometime soon on suspension/hibernation. I use pm-suspend and pm-hibernate, which are in the pm-utils Debian package. If I can figure it out, you can too. Read the documentation.

Dare to be great! Kick butt!

[[User:rdskaroff|Bob]]

Talk:How to get special keys to work

2009-08-02T18:01:10Z

Rdskaroff: /* Some links and info */

__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]]

== Some links and info ==

The x tools setxkbmap, xbindkeys and xmodmap along with the kde 3.5 control center keyboard shortcuts and application links in ~/.kde/Autostart are the tools that I use to do every keyboard thing I want with my R61 7732-CTO.

check out:
[http://www.palmix.org/xmodmap-en.html]
[http://xorg.freedesktop.org/archive/X11R7.0/doc/html/setxkbmap.1.html]
[https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch]
man setxkbmap
man xbindkeys
man xbindkeys-config

An important command for getting this together was on the HotkeyResearch page:

xev | grep -A2 --line-buffered '^KeyRelease' | sed -n '/keycode /s/^.*keycode $[0-9]*$.* (.*, $.*$).*$/\1 \2/p'

It told me which fn-{key} had keycodes and what they were. I was surprised to find that some didn't have keycodes.

Here's the way to do it:
1) read the above references!! don't email me qith questions that have answers in the text.
2) set your keyboard properly. I looked at /etc/X11/xkb/base.xml <name> tag values, then created in ~/.kde/Autostart with konqueror a "link to application" to the statement 'setxkbmap -model thinkpad60 -layout us'
3) use the above xev|etc. command to find the keycodes for the keys you need to map.
4) look at the keycode to keysym correspondences that exist currently by executing xmodmap -pk at the command line
5) create an ~/.xmodmap with the keycode to keysym additions or modifications only if you need to.
6) determine what functionality you want the key combinations to provide
7) use kde keyboard shortcuts to map key combinations (ex fn-F5) to your shortcut scheme. If it doesn't have something you want, like control of amarok with the multimedia keys you either need to create a menu item for the application and a command shortcut or you can use xbindkeys-config to do it.
8) I used xbindkeys-config for a few things but it became a little difficult to use so I created menu items. I later realized that xbindkeys-config and xev didn't see the same keys. I had to map fn-F4 with xbindkeys-config and fn-F12 with a command shortcut.
9) the amarok controller I used is remoot, just search for it, it isn't in Debian.

I will be writing sometime soon on suspension/hibernation. I use pm-suspend and pm-hibernate, which are in the pm-utils Debian package. If I can figure it out, you can too. Read the documentation.

Dare to be great! Kick butt!

[[User:rdskaroff|Bob]]

Talk:How to get special keys to work

2009-08-02T17:58:13Z

Rdskaroff:

__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]]

== Some links and info ==

The x tools setxkbmap, xbindkeys and xmodmap along with the kde 3.5 control center keyboard shortcuts and application links in ~/.kde/Autostart are the tools that I use to do every keyboard thing I want with my R61 7732-CTO.

check out:
http://www.palmix.org/xmodmap-en.html
http://xorg.freedesktop.org/archive/X11R7.0/doc/html/setxkbmap.1.html
https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch
man setxkb

An important command for getting this together was on the HotkeyResearch page:

xev | grep -A2 --line-buffered '^KeyRelease' | sed -n '/keycode /s/^.*keycode $[0-9]*$.* (.*, $.*$).*$/\1 \2/p'

It told me which fn-{key} had keycodes and what they were. I was surprised to find that some didn't have keycodes.

Here's the way to do it:
1) read the above references!! don't email me qith questions that have answers in the text.
2) set your keyboard properly. I looked at /etc/X11/xkb/base.xml <name> tag values, then created in ~/.kde/Autostart with konqueror a "link to application" to the statement 'setxkbmap -model thinkpad60 -layout us'
3) use the above xev|etc. command to find the keycodes for the keys you need to map.
4) look at the keycode to keysym correspondences that exist currently by executing xmodmap -pk at the command line
5) create an ~/.Xmodmap with the keycode to keysym additions or modifications only if you need to.
6) determine what functionality you want the key combinations to provide
7) use kde keyboard shortcuts to map key combinations (ex fn-F5) to your shortcut scheme. If it doesn't have something you want, like control of amarok with the multimedia keys you either need to create a menu item for the application and a command shortcut or you can use xbindkeys-config to do it.
8) I used xbindkeys-config for a few things but it became a little difficult to use so I created menu items. I later realized that xbindkeys-config and xev didn't see the same keys. I had to map fn-F4 with xbindkeys-config and fn-F12 with a command shortcut.
9) the amarok controller I used is remoot, just search for it, it isn't in Debian.

I will be writing sometime soon on suspension/hibernation. I use pm-suspend and pm-hibernate, which are in the pm-utils Debian package.

Dare to be great! Kick butt!

[[User:rdskaroff|Bob]]

Talk:How to get special keys to work

2009-08-02T17:06:08Z

Rdskaroff:

__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]]

== Some links and info ==

The x tools setxkbmap, xbindkeys and xmodmap along with the kde 3.5 control center keyboard shortcuts and creating application links in ~/.kde/Autostart are the tools that I use to do everything I want with my R61 7732-CTO.

check out:
http://www.palmix.org/xmodmap-en.html
http://xorg.freedesktop.org/archive/X11R7.0/doc/html/setxkbmap.1.html
https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch

xev | grep -A2 --line-buffered '^KeyRelease' | sed -n '/keycode /s/^.*keycode $[0-9]*$.* (.*, $.*$).*$/\1 \2/p' told me which fn-{key} had keycodes and what they were. I was surprised to find that some didn't have keycodes.

Here's the way to do it:
1) read the above references
2) set your keyboard properly. I looked at /etc/X11/xkb/base.xml <name> tag values, then created in ~/.kde/Autostart with konqueror a "link to application" to the statement 'setxkbmap -model thinkpad60 -layout us'
3) use the above xev|etc. command to find the keycodes for the keys you need to map.
4) look at the keycode to keysym correspondences that exist currently by executing xmodmap -pk at the command line
5) create an ~/.Xmodmap with the keycode to keysym additions or modifications you need.
6) determine what functionality you want.
7) use kde keyboard shortcuts to map key combinations (ex fn-F5) to your shortcut scheme. If you don't have something you want, like control of amarok with the multimedia keys you either need to create a menu item for the application and a command shortcut to fire the app off when you press the key combination or you can use xbindkeys-config to do it.
8) I used xbindkeys-config for a few things but it became a little difficult to use so I created menu items.
9) the amarok controller I used is remoot, just search for it, it isn't in Debian.

Dare to be great! Kick butt!

Talk:How to get special keys to work

2009-08-02T17:03:36Z

Rdskaroff:

__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]]

== Some links and info ==

The x tools setxkbmap, xbindkeys and xmodmap along with the kde 3.5 control center keyboard shortcuts and creating application links in ~/.kde/Autostart are the tools that I use to do everything I want with my R61 7732-CTO.

check out:
http://www.palmix.org/xmodmap-en.html
http://xorg.freedesktop.org/archive/X11R7.0/doc/html/setxkbmap.1.html
https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch

xev | grep -A2 --line-buffered '^KeyRelease' | sed -n '/keycode /s/^.*keycode $[0-9]*$.* (.*, $.*$).*$/\1 \2/p' told me which fn-{key} had keycodes and what they were. I was surprised to find that some didn't have keycodes.

Here's the way to do it:
1) read the above references
2) set your keyboard properly. I looked at /etc/X11/xkb/base.xml <name> tag values, then created in ~/.kde/Autostart with konqueror a "link to application" to the statement 'setxkbmap -model thinkpad60 -layout us'
3) use the above xev|etc. command to find the keycodes for the keys you need to map.
4) look at the keycode to keysym correspondences that exist currently by executing xmodmap -pk at the command line
5) create an ~/.Xmodmap with the keycode to keysym additions or modifications you need.
6) determine what functionality you want.
7) use kde keyboard shortcuts to map key combinations (ex fn-F5) to your shortcut scheme. If you don't have something you want, like control of amarok with the multimedia keys you either need to create a menu item for the application to fire off when you press the key combination or you can use xbindkeys-config to do it.
8) I used xbindkeys-config for a few things but it became a little difficult to use so I created menu items.
8) the amarok controller I used is remoot, just search for it, it isn't in Debian.

BIOS Upgrade

2007-02-16T11:58:47Z

Rdskaroff: /* Does work: */

__TOC__

This page is meant to describe ways to update the BIOS on a ThinkPad that only runs Linux for users that don't have ready access to Windows. If you have Windows on your ThinkPad you can just boot into it and follow instructions on the IBM website.

{{NOTE| In one case ([[APM setup on a type 2379 ThinkPad T40]]) it was not possible to upgrade the BIOS from Windows XP; a downgrade to Windows 98 was required to successfully run the BIOS upgrade app. The symptoms in this case were that, once the files had been extracted to the hard disk, and the machine was to reboot into the upgrade app, it would beep and hang just before reboot, requiring a power cycle. Once the power was cycled, it would simply reboot back into XP without performing any BIOS upgrade actions. So even if you have Windows, you may still need to use the info on this page.}}

----
==Before You Begin==
Updating the BIOS in Linux (with few exceptions) '''is not officially supported''' by IBM. However there are work arounds.

{{WARN|By following any of the instructions here you are accepting the '''very real risk''' of turning your thinkpad into a big expensive paper weight, as a firmware update gone wrong can create unfixable problems.

'''Proceed at your own risk!'''

It is also '''important''' to understand that all newer thinkpads have 2 seperate firmwares, the BIOS and the Control Program. A specific version of the Control Program will only work with specific versions of the BIOS. The IBM documentation is sometimes confusing about the order of update. Updating the Control Program first, then the BIOS seems to be the correct order. Make sure to do the updates immediately following each other, otherwise you risk turning your thinkpad into a very nice paper weight.}}

==BIOS Upgrade Paths==

For every firmware (either BIOS or Control Program) update on the IBM site there are two different firmware update programs provided. A list of links to firmware downloads can be found at [[BIOS Upgrade Downloads]] for nearly all Thinkpad Models.

===The Diskette Updater===

This installer appears to be a 16bit dos program which asks you to accept a license agreement. It will run in Windows, DOS, OS/2, or [http://dosemu.sf.net Dosemu] perfectly, but requires a real floppy disk attached via a real floppy control. The USB Floppy Drive to the new Thinkpads doesn't count.

===The Non Diskette Updater===
{{WARN|Though this process was successfully tested on one version of .exe files found on IBMs website this doesn't mean it will work for all of them. Use at your own risk.}}

This installer appears to be a 32bit windows exe which is designed for updating the BIOS directly from a running Windows OS. It turns out that the .exe is really a wrapper license program arround windows .cab files (this information is in [[How_to_change_the_BIOS_bootsplash_screen|BIOS-Bootsplash]]). If you install the Linux program [http://freshmeat.net/projects/cabextract/ '''cabextract'''] you can expand these files directly. Run the following:

:{{cmduser|cabextract FILENAME.exe}}

You will get 8 files in the current directory. One of them will be FILENAME.img. You can test that this is really a floppy image by running:

:{{cmdroot|mkdir mntfloppy}}
:{{cmdroot|mount -o loop FILENAME.img mntfloppy}}
:{{cmdroot|ls -la mntfloppy}}

If the results of {{cmdroot|ls -la mntfloppy}} look like a dos floppy, and no read errors were displayed, you have a pretty good chance that the floppy image is usable.

If you were able to create the boot floppy per the Diskette update method, and you have a Floppy with your Thinkpad, the update should be simple.

==Updating an X60==
If there is no floppy, and no windows, but an external USB CD, then there is hope.

===Build a bootable CD with USB support===
Get the ISO Image style BIOS upgrade, and the freedos floppy (http://www.ankreuzen.de/freedos/files/fd9sr1/fdos1440.zip)

:{{cmdroot|su # get root}}
:{{cmdroot|mkdir /tmp/iso}}
:{{cmdroot|mkdir /tmp/cdimage}}
:{{cmdroot|mount -o loop <iso-bios-file> /tmp/iso}}
:{{cmdroot|cp /tmp/iso/* /tmp/cdimage}}
:{{cmdroot|cp <freedos-disk-image> /tmp/cdimage/floppy.img}}
:{{cmdroot|mkisofs -b floppy.img -o bootcd.iso /tmp/cdimage}}

finished.. now boot from cd and flash.

==Updating via CD/DVD Drive==

The whole thing gets more complicated if you neither have Windows nor a floppy drive installed. This is what this page is intended to describe.

Another possibility which works even without a CD-drive or network is to boot the disk image via the grub initrd mechanism.

Be aware that IBM officially does '''not''' support this! The official statement to my support request was:

<blockquote style="background: white; border: 1px solid black; padding: 1em;">
<pre><nowiki>
I'm afraid we only support the options listed on our web page and no you
can't burn a CD/DVD, however you can try to use an external USB FDD
(floppy) drive. The experts recommend a IBM USB FDD, however they have also
tested it with a Sony USB FDD drive.

In order to make sure the drive is recognised you can boot up the FDD with
a bootable dos diskette for w98
</nowiki></pre>
</blockquote>

But it seems to be possible as Mathias Dalheimer describes this [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/1998-January/009743.html here].

Another indication that it should work is that IBM uses PHLASH16.EXE (at least on T4x/p systems) to flash the BIOS into the chip. The same tool is used by [http://www.samsungpc.com/gb/support/p35/bios/bios-instructions.html other vendors] to flash the BIOS from bootable CD-ROMs.
{{WARN|Do '''not''' use the [http://syslinux.zytor.com/ SYSLINUX] image-loader [http://syslinux.zytor.com/memdisk.php MEMDISK] to boot the images! Some flash tools crash in that situation!}}

Some interesting but very technical information about the used flash tool can be found [http://www.paul.sladen.org/thinkpad-r31/wifi-card-pci-ids.html here].

===Creating a Floppy Image===
If you have created a boot floppy on another machine, you need to create an image file of that floppy. This can be easily done in linux by running a command line:

:{{cmdroot|1=dd bs=2x80x18b if=/dev/fd0 of=/tmp/floppy.img}}

You can also create a floppy image by using Ken Kato's [http://chitchat.at.infoseek.co.jp/vmware/vfd.html VMware's back]. It is a free Windoze tool that creates a virtual floppy drive and allows you to produce an image file ready to be ISO'ed. Note: you might have to 'manually' (through application's interface) assign the virtual drive a volume letter in order to be seen by IBM's application (as, by default, it seems not to do it).

You should verify this {{path|floppy.img}} as explained above.

===Creating a Bootable CD from a Floppy Image===
Once you have your floppy image, either from imaging a real floppy, or from extracting them via the cabextract method above, you need to make a boot CD out of it.

The eltorito bootable CD standard is a wonderful thing. What this means is that a bootable CD can be made with a bootable floppy in such as way that the CD believes that it is a 2.88 MB floppy drive. This allows you to replace a boot floppy by a boot CD in nearly all situations.

It is very easy to create such a bootable CD ISO image in Linux using the mkisofs tool. To do this run a command as follows:

:{{cmdroot|mkisofs -b bootfloppy.img -o bootcd.iso bootfloppy.img}}

Note: You don't strictly need the last {{path|bootfloppy.img}}, however some versions of mkisofs get confused about why you would want to create an iso with no contents, and thus won't let you. You don't actually care about the contents of the CD, you only care that the <tt>-b <boot image></tt> is applied to the CD. For more info on this read {{cmduser|man mkisofs}}.

You can now burn the {{path|bootcd.iso}} in your favorite CD burning program.

To get an overview which models have been tested with this version, here is a list:

===Does work:===
{| border="1" cellspacing="0" cellpadding="2"
| '''Model''' || '''Tested by'''
|-
| style="vertical-align:top;" | {{600X}} (2645) ||
*Jonathan Byrne <jonathan@RemoveThisToMailMe.yamame.org>. BIOS 1.11 from spsuit55.exe worked perfectly using cabextract/CD method.
|-
| style="vertical-align:top;" | {{A20p}} (2629-6VU) ||
*Chris Pickett http://www.sable.mcgill.ca/~cpicke/. BIOS 1.11 flashed fine with cabextract/CD method.
|-
| style="vertical-align:top;" | {{A21e}} (2628-JXU) ||
*Amit Gurdasani <gurdasani at yahoo dot com>. BIOS 1.13 flashed fine with cabextract/CD method. Alarmingly, after the BIOS update, the laptop beeped but did not shut down as was indicated onscreen -- that was frozen on the "do not shut down the laptop" screen. On power down and up again, the BIOS setup showed the newer BIOS image running, and Linux booted up fine. Linux ACPI didn't complain about the BIOS being too old either.
|-
| style="vertical-align:top;" | {{A31p}} (2653) ||
*Matthias Meinke largeeddy@gmx.at, BIOS 1.09 1NET15WW flashed fine with cabextract/CD method.
|-
| style="vertical-align:top;" | {{R31}} ||
*[http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/1998-January/009743.html Mathias Dalheimer]
*Sebastian Sauer (with cabextract/CD method)
|-
| style="vertical-align:top;" | {{R40}} ||
*Matthew Lambie, http://lambie.org
|-
| style="vertical-align:top;" | {{R50}} (1836-3SU) ||
*jlbartos <jlbartos at hotmail dot com>
|-
| style="vertical-align:top;" | {{R51}} (1829) ||
*Robert Uhl <rob dot uhl at gmx dot de>, Jellby <jellby at yahoo dot com>
|-
| style="vertical-align:top;" | {{R51}} (1830-RM7) ||
*Will Parker <stardotstar at sourcepoint dot com dot au> successfully flashed 3.20 using existing 3.04 ECP and retained custom boot splash.
|-
| style="vertical-align:top;" | {{R51}} (2887) ||
*Ingo van Lil <inguin at gmx dot de>
|-
| style="vertical-align:top;" | {{R52}} (1858) ||
*Stuart McCord <stuart dot mccord at gmail dot com> flashed both BIOS and ECP using cabextract, BIOS flashed first as on IBM website
|-
| style="vertical-align:top;" | {{T20}} ||
*Franz Hassels <fhassel at suse dot com>
|-
| style="vertical-align:top;" | {{T22}} ||
*Daniel Maier <nusse teamidiot de>
*Mathias Behrle (with cabextract/CD method, Version 1.07 => 1.12) --[[User:Mathiasb|Mathiasb]] 11:58, 14 December 2006 (CET)
*Bob Skaroff (cabextract/CD), 1.06 => 1.12
|-
| style="vertical-align:top;" | {{T23}} ||
*Bart Snapp <snapp at uiuc dot edu> Note: I followed IBM's instructions to flash the BIOS *first* and the Embedded Controller *second*.
*Moy Easwaran: BIOS 1.18 / EC 1.06a via cabextract and CD-boot. The BIOS-update exe generated errors in Windows 2000.
*Joe Renes: BIOS 1.18 / EC 1.06a on 2006-03-20 via cabextract and CD-boot. Piece of cake.
*Raphael Errani: BIOS 1.20 / EC 1.06a on 2006-11-06 via cabextract and CD-boot (using mkisofs). Worked without errors. 1st Bios, 2nd EC
|-
| style="vertical-align:top;" | {{T30}} ||
*Martin GÃ¼hring <guehring at gmail.com> BIOS 2.10 via cabextract the Non-Diskette BIOS -> mkisofs '''in the directory the exe was extracted''' to generate the iso -> burn the iso -> boot the CD
|-
| style="vertical-align:top;" | {{T40}} ||
*Sean Dague, http://dague.net
*Justin Mason, http://jmason.org
*Ivanhoe (Bios 3.19)
|-
| style="vertical-align:top;" | {{T40p}} ||
*Lukas KrÃ¤henbÃ¼hl, ismo at pop dot agri dot ch
*Thomas Achtemichuk, tom at tomchuk dot com. BIOS 3.15 flashed fine with cabextract/CD method
|-
| style="vertical-align:top;" | {{T41}} ||
*Lev Givon (Bios 3.15 / EC 3.04) <lev at columbia dot edu>
*Ernesto HernÃ¡ndez-Novich (Bios 3.19 / CP 3.04) < emhn at usb dot ve >
|-
| style="vertical-align:top;" | {{T41p}} ||
*Nils Newman, work great. (Version: Bios 3.14 / Embedded Controller 3.04)
|-
| style="vertical-align:top;" | {{T42}} ||
*Dan (BIOS 3.20 / EC 3.04, cabextract/CD method) <tronic171 at evilphb.org>
|-
| style="vertical-align:top;" | {{T42p}} ||
*Robert Schiele <rschiele@uni-mannheim.de>, Joern Heissler <joern@heissler.de>
|-
| style="vertical-align:top;" | {{T43}} ||
*Conrad Rentsch <Conrad dot Rentsch at t-online dot de> (Version: Bios 1.29 / Embedded Controller 1.06)
*Tom Heady <tom-thinkwiki.org@punch.net>
*Carsten SÃ¶hrens <casoe at gmx dot de> (Version: Bios 1.05 / Embedded Controller 1.03)
*Carsten SÃ¶hrens <casoe at gmx dot de> (Version: Bios 1.24 / Embedded Controller 1.04)
*Florian Boucault <florian at boucault dot ath dot cx> (Model : 1871-W34 & Version: Bios 1.23 / Embedded Controller 1.03)
|-
| style="vertical-align:top;" | {{X20}} ||
*Neil Caunt <retardis at gmail dot com>
|-
| style="vertical-align:top;" | {{X21}} ||
*Patrick Leickner <ranma at web dot de>, (BIOS 2.21->2.25 / EC 1.31->1.36) via non-disk/cabextract/mkisofs/cdrecord
|-
| style="vertical-align:top;" | {{X22}} ||
*David Emery <dave at skiddlydee dot com>, (EC 1.30, BIOS 1.32 using non-disk/cabextract/CD method)
|-
| style="vertical-align:top;" | {{X23}} ||
*Nils Faerber <nils dot faerber at kernelconcepts dot de> (Embedded Controller 1.30, BIOS 1.32 with cabextract/CD method)
|-
| style="vertical-align:top;" | {{X30}} ||
*Hella Breitkopf, [http://www.unixwitch.de/ www] (Embedded Controller 1.04, BIOS 1.07 with cabextract/CD method)
|-
| style="vertical-align:top;" | {{X31}} ||
*Grzegorz KuÅ›nierz <koniu at sheket dot org> (Embedded Controller 1.08, BIOS 3.01 with cabextract/CD method)
|-
| style="vertical-align:top;" | {{X40}} ||
*Robbie Stone <robbie@serendipity.cx>
|-
| style="vertical-align:top;" | {{Z60m}} ||
*[[User:Morle|Morle]] 13:09, 20 May 2006 (CEST), (Embedded Controller 1.14 with cabextract/CD method)
|}

===Does not work:===
{|
| '''Model''' || '''Tested by'''
|}

Please note that testing this is '''at your own risk'''!!!

==Updating via Grub and a Floppy Image==

{{WARN|Many have warned '''not''' to use the [http://syslinux.zytor.com/ SYSLINUX] image-loader [http://syslinux.zytor.com/memdisk.php MEMDISK] to boot the images! Some flash tools may crash in that situation! Proceed at your own risk!}}

Floppy images may be booted from Grub via a utility called [http://syslinux.zytor.com/memdisk.php MEMDISK], which may be compiled from the [http://www.kernel.org/pub/linux/utils/boot/syslinux/ '''SYSLINUX source''']. Copy the compiled memdisk image and the floppy image to your boot directory and configure grub as follows:

<blockquote style="background: white; border: 1px solid black; padding: 1em;">
<pre><nowiki>
title Bios Flash
kernel /boot/memdisk
initrd /boot/FILENAME.img
</nowiki></pre></blockquote>

Again, proceed at your own risk. This was tested on an R51 type 2888.

This also worked for me on a T41p type 2373. -- [[User:MrStaticVoid|James Lee]] 20:55, 8 May 2006 (CEST)

And it worked for me on a X31 type 2673-CBU. -- [[User:JanTopinski|Jan Topinski]], 18 September 2006

And it worked for me on two X40 type 2371 -- [[User:Antialize|Jakob Truelsen]], 19 Jan 2007 -- BIOS: 2.07 1uuj21us.exe -- ECP: 1.62 1uhj10us.exe

Not working for me on T43 type 2668-F7G -- [[User:Maus3273|Maus3273]] 20:48, 30 January 2007 (CET) -- BIOS: 1.29 1YUJ18US.IMG -- I got into the bios program, but the machine never restarts after initiating the upgrade.

==Updating with Network Boot Image==

BIOS, Embedded Controller (EC), CD/DVD and Harddisk firmware disks can be booted
over the network with [http://syslinux.zytor.com/pxe.php PXELINUX] as part of the [http://syslinux.zytor.com/ SYSLINUX] package.

This requires that you have a DHCP and tftp server configured and setup properly on
your network, and is probably not for the faint of heart.

Make sure the firmware bootdisk is in linux 'dd' format, as the self-extracting .exe disks
from the IBM website cannot be booted directly as such.

This worked on the {{R31}}, {{X22}}, {{T21}}, {{T30}} and {{T41p}} with various firmware updates.

==Updating via "IBM Predesktop area", suitable for model X (not have CDROM and floppy)==
It's so difficult to update BIOS and ECP without cdrom, floppy disk.
Don't know the reason why I couldn't update BIOS and ECP(1QHJ08US and 1QUJ19US) for my IBM Thinkpad X31.Hmm, may be cause of the dividing partition on my hard disk, that is:
<blockquote style="background: white; border: 1px solid black; padding: 1em;">
<pre><nowiki>
Primary: ext3, ext3, ntfs
Extended: Ntsf, fat32
Bootloader: GRUB
</nowiki></pre></blockquote>

No problem, you can use this way to do it:
* First, config in BIOS
In Security part:
# Remove all password of Subpervisor and Power on password
# Set Access IBM Predesktop Area to Normal
# Choose Enable "Flash BIOS updating by End User" in BIOS update Option.

In Config part:
# Choose Enable for Network flash over Lan

* Second, download the newest version of BIOS update and ECP update
Running: The program extract all files to the folder. There is a .img file (1QUJ19US.IMG, 1QUJ08US.IMG) in each folder.
Copy the imformation content in that img file and paste it to one FAT partition(using winimage or TotalCmd to extract)

as seen All files in 1QUJ19US.IMG is extracted to D:\BIOS
<blockquote style="background: white; border: 1px solid black; padding: 1em;">
<pre><nowiki>
695,764 $018E000.FL1
163 0691.HSH
2,049 0691.PAT
163 0694.HSH
2,049 0694.PAT
163 0695.HSH
2,049 0695.PAT
2,049 06D0.PAT
163 06D1.HSH
2,049 06D1.PAT
163 06D2.HSH
2,049 06D2.PAT
163 06D6.HSH
2,049 06D6.PAT
2,049 06D8.PAT
697 CHKBMP.EXE
8,128 COMMAND.COM
26 CONFIG.SYS
24,860 FLASH2.EXE
26 LCREFLSH.BAT
170 LOGO.BAT
330 LOGO.SCR
111,925 PHLASH16.EXE
91,648 PREPARE.EXE
45 PROD.DAT
22,252 QKFLASH.EXE
9,923 README.TXT
4,260 TPCHKS.EXE
39,666 UPDTFLSH.EXE
6,958 UPDTMN.EXE
12,501 USERINT.EXE
15,254 UTILINFO.EXE
</nowiki></pre></blockquote>

And all files in 1QUJ08US.IMG are: D:\ECP
<blockquote style="background: white; border: 1px solid black; padding: 1em;">
<pre><nowiki>
315,404 $018E000.FL2
8,000 COMMAND.COM
36 CONFIG.SYS
16,910 ECFLASH2.EXE
45 PROD.DAT
17,812 QKFLASH.EXE
990 README.TXT
4,260 TPCHKS.EXE
89,738 UPDTEC.EXE
31,134 UPDTFLSH.EXE
12,501 USERINT.EXE
15,226 UTILINFO.EXE
</nowiki></pre></blockquote>

* Okie, now plug AC Adapter, charge full battery to your laptop and continue third step:

** '''Flash BIOS first,'''
1. Power On, press blue button on keyboard: '''Access IBM'''

2. On "Utilities", double click " Diagnostic disk"

3. Your laptop will start PC-DOS, wait when this message appear:
<blockquote style="background: white; border: 1px solid black; padding: 1em;">
<pre><nowiki>
Please insert the first floppy diskette and
Press any key to continue
</nowiki></pre></blockquote>

4. Press Ctrl + Break, you will see :
<blockquote style="background: white; border: 1px solid black; padding: 1em;"><pre><nowiki>Terminate batch job (Y/N) ?</nowiki></pre></blockquote>

5. Okie, press Y, you will get DOS prompt like D:\
{{NOTE|D:\ is my RAMDISK, C:\ is my disk format as FAT.!}}

6. Enter to c:\BIOS
<blockquote style="background: white; border: 1px solid black; padding: 1em;">
<pre><nowiki>
c:
cd c:\BIOS
</nowiki></pre></blockquote>

7. Run FLASH2.EXE /u $018E000.FL1

8. Wait flash progress compelete and reboot.
** '''Flash ECP'''
Follow above instruction from step 1 to 5

6. Enter to c:\ECP
<blockquote style="background: white; border: 1px solid black; padding: 1em;">
<pre><nowiki>
c:
cd c:\ECP
</nowiki></pre></blockquote>

7. run UPDTFLSH.EXE $018E000.FL2

8. Follow UPDTFLSH's instructions

9. Wait flash complete and auto turn off computer.

I done it on my IBM Thinkpad X31.

Enjoy,

Tested by nm.

==Check List==

The following is important to remember:
# You must update '''both''' the Control Program and the BIOS at the same time if your current Control Program is not compatible with the new BIOS (see below)
# You must find versions of the Control Program and BIOS that are compatible. Not all of them are, so follow the readmes on the IBM website carefully to determine which are.
# You must update the Control Program '''before''' you update the BIOS

When the Control Program '''and''' the BIOS need updating, have both update disks or CDs ready. Update the Control Program first and the system should switch itself off when finished. Insert the BIOS update disk and proceed to update the BIOS. When it's all finished, enter setup, reset the settings to their defaults and reboot. Enter setup again and tweak the settings as necessary.