Hi, Also, sprach Timo Hoenig am Montag, den 27. November 2006 um 13:01: > On Mon, 2006-11-27 at 12:36 +0100, Sebastian Fontius wrote: > > I agree. I have no real idea of the inner workings of fnfx, its > > client, or the kernel in regard to this, but the symptoms reminded > > me of #328085. So I concluded (or merely hoped) that it would be > > a matter of simply making the patch dependant on what version of > > Linux actually runs or something as easy as this. > > Agreed, #328085 sounds very similar. > > > But then I found http://developer.berlios.de/projects/ial [...] > > How good is IAL working and is there a possibility that it will > > enter Debian? > > IAL is basically not under development any longer. Please do not spend > any time on getting it into Debian.
Okay. > I am planning to cleanup the hotkey mess in 2007 by adding some bits > to HAL. Again, not only for Toshiba laptops but an abstract > approach which should help any system, vendor independent. If I am not mistaken there already are at least some things Toshiba specific in HAL: $ dlocate hal: | grep tosh hal: /usr/share/hal/fdi/policy/10osvendor/10-toshiba-buttons.fdi hal: /usr/lib/hal/hald-addon-acpi-buttons-toshiba $ lsof | grep tosh hald-addo 4724 root mem REG 3,1 9212 149972 /usr/lib/hal/hald-addon-acpi-buttons-toshiba The lsof output gives the hint that HAL loads this addon (and indeed, smbios.system.manufacturer is TOSHIBA, as specified in /usr/share/hal/fdi/policy/10osvendor/10-toshiba-buttons.fdi), but it does not appear to do anything. At least lshal -m does not utter a single byte regarding to the keys, whereas it reacts to everything else I tried: removing input devices, charging the battery, etc.pp. I also stopped fnfx from starting for this so as not to disturb HAL in any way. I read some things about a virtual input device or something (again: no knowledge, and if, then some rather dangerous half-knowledge ;)) but did not find anything in the output of lshal or the source code of the current version of HAL in testing. > If FnFX is missing key events, IAL will miss them, too as it is > basically the same backend code. Good reasoning :). > > BTW: I updated to linux 2.6.18.3 and the problem has not gone away. > If you want to succeed I'd suggest breaking it down to the kernel > version where it broke. If you can tell "it worked with 2.6.16.3 but > stopped working with 2.6.1.16.4" you will have a realistic chance to > find the culprit. Bah! (Read: "I know of course that you are right, but had hoped to find a solution without resorting to bug hunting this way. I strongly assume that with Linux 2.6.17 it worked and will try that now (albeit not my homegrown version but the Debian one linux-image-2.6.17-2-686... If that does not help I will have to think of something because I do not backup my old kernel .configs). I will report my findings shortly"... I am always surprised to find what a simpe "Bah!" is able to convey ;)) Greetings, -- : Sebastian Fontius : www.fsfe.org : www.fsfe.org/en/fellows/smc `--------+----------+--------------+-----------------------------------. [] | "They that can give up essential liberty to obtain a little | [][][] | temporary safety deserve neither liberty nor safety." | || : Benjamin Franklin, 1759 :
signature.asc
Description: Digital signature