|(4 intermediate revisions by 2 users not shown)|
Better differentiation needed == |+|
| || |
|−|Since i'm a newbie here, I prefer not to do it on my own. IMHO, the organisation should be revamped... I would rather use a "Console" "X.org" split cause xev is of no use in Console, and showkey seems to also be useless in X. I'd add that in many case acpid can be useful for functions key cause independant of X/Console. The fact that the Fn key is sometimes handled in the hardware and invisible to the kernel could be noted too (I searched like 3 hours to get it, searching for where is the error and unable to find it (cause I'm not used to linux and and still don't master logging in linux, so I never thought that it may just be non- existent...) to learn in a random comment on a post that the Fn key sometime just throw a different keycode when pushed... But I don't know if it really belong here, and personally i'd also merge this file with both [[Extra Keyboard Keys in Xorg]] and [[Extra Keyboard Keys in Console]], don't know if it's a good idea? I think it's better to not juggle between 32 page cause as a newbie, it's kind of confusing :) Oh, and... should I split my comment in multiple topic instead of one huge? [[User:Blakthorn|Blakthorn]] ( [[User talk:Blakthorn|talk]]) 14:53, 29 January 2013 (UTC) |+|
is useful for .
and it -
the of ()
| || |
|−|:Yes, I agree. |+|
| || |
|−|:showkey and xev report totally different keycodes for media buttons. Getting codes for use in X from showkey is pointless. The article is very misleading. [[User: Dibblethewrecker| dtw]] ([[User talk: Dibblethewrecker|talk]]) 17: 42, 7 August 2013 (UTC) |+|
[[User:|]] ([[User talk:|talk]]) :, 2013 (UTC)
| || |
:Implemented: [ https://wiki. archlinux. org/index. php?title=Extra_Keyboard_Keys &diff=277391&oldid=277389] -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 21: 37, 2 October 2013 (UTC) |+|
-- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz
|talk]]) 21:, 2013 (UTC)
Revision as of 21:10, 14 December 2013
getscancodes is very useful tool for grabbing scancodes.
Quick howto for newbie
- install getscancodes from aur #yaourt -Sya getscancodes
- connect your device and recognize it #dmesg|tail -30
- find the event id of the device (use grep) #cat /proc/bus/input/devices
- run getscancodes #sudo getscancodes /dev/input/event18
I find that it easy just to use setkeycodes for a quick test # setkeycodes scancode keycode
I recommend on mapping the scancodes to a keycode with udev, just link to the wiki or merge the pages.
Dhead (talk) 05:54, 21 October 2013 (UTC)
- There's already a link to official instructions in Extra_Keyboard_Keys#See_also, so I'd say it's not necessary to add these to our wiki.
- setkeycodes and mapping with udev are described in Map_scancodes_to_keycodes, which is just fine - I don't know what you mean...
- Map_scancodes_to_keycodes and Extra_Keyboard_Keys are properly interlinked, and I'm against the merging at the moment because that would imply other pages should be merged too and the resulting page would be too long and hard to read.
- -- Lahwaacz (talk) 13:00, 21 October 2013 (UTC)
Regarding the discussion about the out of date section (2.6 kernels): I use a 3.2 kernel (although not archlinux) and have a non functioning key for which "showkey -s" reports nothing, but the kernel log is full of with logs that that key is unkown, and reports it's scancode. And with the scancode reported in the log I can make it known (although this breaks another behaviour of the keyboard, so for me it is useless). So I think that section is not out of date. Kovacssanya (talk) 21:10, 14 December 2013 (UTC)