On 2026-09-15 19:39:38 +0200, Steinar Bang wrote: > >>>>> Vincent Lefevre <[email protected]>: > > > 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 > > Hm... "cat /lib/udev/hwdb.d/60-keyboard.hwdb" output a lot of stuff. > What am I looking at/for here wrt. to my own keyboard?
This is just an example of what can be done. But if you do not get a scan code, then I don't think you can do anything on the kernel side. > > There are several utilities for low-level tests: > > evtest, input-events, input-kbd, lsinput. > > I have tried evtest and input-events without any success (i.e. no events > on Fn or from the Fx keys that doesn't give anything useful in xev). I suppose that in your case, the Fn key is handled internally by the keyboard controller as said at <https://superuser.com/a/786076/403265> and that the event is not sent on the wire. > Will try input-kbd and lsinput, thanks! If you do not see any event, I doubt that this will change anything. > > There is some information about the Fn key there: > > https://askubuntu.com/q/818413/691424 > > Will read! Thanks again! > > > 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). > > Hm... ok. Could a kernel module change be the cause of what affects my > keyboard? (ie. my recurrent question: is it possible to fix Fn without > entering the BIOS?) If the Fn key is handled internally by the keyboard controller, I would say no. -- 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)
