So, after updating the firmware AND getting the new udev rules… is there anything I should be aware of to ensure Linux recognises my keyboard correctly? For some reason the keyboard shown in the “Configure” and the one shown in the “Key Tester” section of keyboard.frame.work are different…
If I recall, that’s normal. It seems that the key tester always just displays a generic keyboard. One reason to use a generic keyboard is that it’s only testing / displaying USB HID transmitted keys. If it showed your keymap then it might confuse some people as to why some keys, internal QMK function keys like Fn, backlight cycle, etc, do not register in the keytester.
1 Like
Okay, thank you and that makes sense! Now I realise I should have asked my question differently. How can I ensure on X11/Cinnamon (debian forky) that my keyboard layout is recognised correctly? Something broke since last week or so, and I can’t get
a) The keyboard module to start in Cinnamon-Settings (so I’m not even sure whether the current setup is correct…
b) The compose key (that I previously configured to Right-Alt) to work correctly…
This doesn’t sound related to the app/keyboard firmware - but rather to a change in Debian.
I would recommend creating a new topic - as this is OT from the guide I have created - the topic here should focus on the udev rules.
You might also bring up those issues on a Debian thread - as this sounds like an OS level issue:
a) The keyboard module to start in Cinnamon-Settings (so I’m not even sure whether the current setup is correct…
2 Likes
Good point! Thanks!
The linked file appears to have disappeared. Does anyone have the working file they can share?
well, thats unfortunate - i cant upload the file directly - but here is the link, from my gdrive - lemme know if you can access it:
Thank you! Got my laptop keyboard working again!
Here is another source, github.com/qmk/qmk_firmware/blob/0.32.11/util/udev/50-qmk.rules
1 Like