Timeline for What does this output from xev mean?
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Oct 2, 2023 at 20:52 | history | suggested | Peter Mortensen | CC BY-SA 4.0 | Copy edited (e.g. ref. <https://www.wikihow.com/Use-You%27re-and-Your>). Broke down the wall of text. Applied some formatting. Expanded. |
| Oct 2, 2023 at 18:57 | review | Suggested edits | |||
| S Oct 2, 2023 at 20:52 | |||||
| Apr 1, 2014 at 7:12 | comment | added | orion | Thank you for this insight. It totally explains why some extra keys on my Toshiba just output the character x. To me, this makes no sense... why hard-wire a key combination that is very obviously single-purpose, single-application and unconfigurable? And that at the cost of rearranging the keys to make room for that silly Fn key, making me miss ctrl every time... | |
| Dec 28, 2013 at 12:01 | comment | added | Thorsten Staerk | you could go one level deeper and see what is really transmitted over the wire: Switch to CTRL_ALT_F1 console, log in and issue a command that will make your computer stop working as it will print all input onto the screen. No keypress will be accepted any longer, all will go to the screen, so save your work before! The command is cat /dev/tty0 | |
| Mar 6, 2012 at 4:51 | comment | added | Andrew | Really! Interesting! I will check my bios. Any insight into what the MappingNotify events might be? I didn't have much luck googling them. | |
| Mar 5, 2012 at 17:09 | comment | added | Gilles 'SO- stop being evil' | @Andrew The Fn key combinations are mapped by the BIOS. The OS doesn't see them. Depending on the computer model and on the key, you may or may not be able to reconfigure it through ACPI. | |
| Mar 4, 2012 at 3:12 | comment | added | penguin359 | @Andrew actually, I can't explain the MappingNotify itself without reviewing the X11 protocol again, but I do see three different keycodes listed above. | |
| Mar 4, 2012 at 3:10 | comment | added | penguin359 | Keycodes in X11 represent physical keys delivered by the kernel to the X server. The X server then uses various mechanisms to map them to Keysyms and then to strings, if needed. A normal keyboard sends one keycode per physical key using standard USB HID or PS/2 keycodes. However, some compressed, simplified, or simply non-standard keyboards can compose various keycodes differently depending on the state like when the numeric keypad is overlayed onto the letter keys. That's done in hardware. Also, sometimes keys like monitor select or sleep don't even generate normal codes, instead ACPI events | |
| Mar 4, 2012 at 0:54 | comment | added | Andrew | Interesting. You think the hardware is responsible for the MappingNotify event? I assumed that somewhere in linux, the key had been mapped to multiple keypresses, and I just had to figure out where so I could deactivate the multiple mapping. For comparison, when I hit Fn-F12, I get an xev response that contains keycode 78 (keysym 0xff14, Scroll_Lock), but no MappingNotify-type stuff. | |
| Mar 3, 2012 at 23:35 | history | answered | penguin359 | CC BY-SA 3.0 |