And I forget:<br><br>This is how keyboard is defined in xorg.conf (I tried it without definition too)<br><br>Section "InputDevice"<br> Identifier "Generic Keyboard"<br> Driver "evdev"<br>
Option "XkbRules" "evdev"<br> Option "XkbModel" "evdev"<br> Option "XkbLayout" "us"<br>EndSection<br>
<br>And this is output from Xorg.0.log<br><br><br>(II) config/hal: Adding input device Internal keyboard<br>(II) LoadModule: "evdev"<br>(II) Loading /usr/lib/xorg/modules/input//evdev_drv.so<br>(II) Module evdev: vendor="X.Org Foundation"<br>
compiled for 1.5.99.901, module version = 2.1.1<br> Module class: X.Org XInput Driver<br> ABI class: X.Org XInput driver, version 4.0<br>(**) Internal keyboard: always reports core events<br>(**) Internal keyboard: Device: "/dev/input/event0"<br>
(II) Internal keyboard: Found keys<br>(II) Internal keyboard: Configuring as keyboard<br>(II) XINPUT: Adding extended input device "Internal keyboard" (type: KEYBOARD)<br>(**) Option "xkb_rules" "evdev"<br>
(**) Internal keyboard: xkb_rules: "evdev"<br>(**) Option "xkb_model" "pc105"<br>(**) Internal keyboard: xkb_model: "pc105"<br>(**) Option "xkb_layout" "us"<br>(**) Internal keyboard: xkb_layout: "us"<br>
<span style="color: rgb(255, 0, 0);">(WW) Internal keyboard: unable to handle keycode 464</span><br><br><br><div class="gmail_quote">On Tue, Jan 27, 2009 at 1:06 AM, Lokean Darken <span dir="ltr"><<a href="mailto:lokean.darken@gmail.com">lokean.darken@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hello, thank you for reply<br><br><div class="gmail_quote"><div class="Ih2E3d">On Tue, Jan 27, 2009 at 12:52 AM, Sébastien Mazy <span dir="ltr"><<a href="mailto:melyadon@gmail.com" target="_blank">melyadon@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Michal,<br>
<div><br>
On Tue, Jan 27, 2009 at 12:39:20AM +0100, Lokean Darken wrote:<br>
> This is my fdi which I use to remap key 464 to key 216<br>
><br>
</div><snip><br>
<div>><br>
> Anyway, xev still don't catch any signal while I press this key...<br>
><br>
> Is this configuration right? If yes, how should I found where is the<br>
> problem?<br>
<br>
</div>1) make sure your fdi file is under /etc/hal/fdi/policy, so that it is<br>
processed after the ones from your distribution</blockquote></div><div><br>Yes, fullpath is /etc/hal/fdi/policy/30-n810.fdi<br></div><div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
2) is 0x1d0 really the scancode from the key? How did you find it?</blockquote></div><div><br>To be honest, I can't swear. I used hexadecimal form of 464 and in /usr/include/linux/input.h is such key defined as: <br>
<br>#define KEY_FN 0x1d0<br>
<br>Then I guessed it's ok. Unfortunelly, I have no access to real console for this device, only over X or by ssh, so I don't know howto make better guess.<br></div><div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
3) what returns lshal -m when you press the key?<br>
</blockquote></div><div><br>Nothing, no matter what key I press, there is no output. <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
--<br>
<font color="#888888">Sébastien Mazy<br>
</font></blockquote></div><br>
</blockquote></div><br>