On 2026-09-13 11:34:45 +0200, Michel Verdier wrote: > On 2026-09-13, Steinar Bang wrote: > > > Also Fn has no events in xev at all. Its neighbours Ctrl, Windows and > > Alt has full event activity. > > > > Hm... could it be as simple as the Fn key being physically broken...? > > The key doesn't feel stuck in any way...? > > Fn key doesn't generate event but it changes the keycode of the associate > key. It is done somewhere before xev (bios I suppose ? perhaps firmware ?).
Before the keycode, there is the scan code, and it seems that it is evdev that maps scan codes to keycodes (the Fn key has its own scan code). See the following file: /lib/udev/hwdb.d/60-keyboard.hwdb There are several utilities for low-level tests: evtest, input-events, input-kbd, lsinput. There is some information about the Fn key there: https://askubuntu.com/q/818413/691424 How the Fn key is handled/configured exactly depends on the hardware. With the keyboard I'm using, there are driver options to be put in a file under the /etc/modprobe.d directory to change the way the Fn key behaves (and other things). -- Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)
