[Franework Laptop 12][SOLVED] How to trigger F1-F12 keys without holding Fn key?

Received my FW12 today.

How to use F1-F12 keys without holding Fn key? I never use these multimedia shortcuts because KDE provides a more portable, same shortcuts settings which can be applied on various models of laptop. I have ever used 5 laptops and they all can customize this behavior via BIOS or can be toggled via pressing Fn+Esc. However I am astonished when I cannot find any setting about this in BIOS and also didn’t find anyone is disscussing this problem…

Thanks.

1 Like

Did you press Fn+Esc together, or hold down the Fn key, and then press Esc?
Because the latter did work on my FW12.

2 Likes

I press and hold Fn, then press Esc. Doesn’t work.

You mention KDE, are you using Ferdora, or another Linux distro with KDE?

what distro and version are you running? I don’t have a FW12 yet to test with, but there are a ton of threads about function lock related to other FW models, one of which seems to be fixed with a kernel module update in kernel 6.11

I’m running Ubuntu 25.04 on a 12. I just now pressed Fn+Esc and it toggled the Fn keys functionality.

Can also confirm that it works on Fedora 42 (although did not test the Fedora KDE Plasma variant).

Weird…It works now… I swear I had already struggled and tried to toggle these function key mode via pressing Fn + Esc for at least 2 hours but it just didn’t work (I even burned a Fedora 42 Live USB to test it in Live environment and the problem remains), however when I’m writing this article and preparing the output of `evtest` for this article, it worked suddenly… Totally have no idea why…

Anyway, still provide the final output of `evtest` and thanks for everyone who reply me.

(Before pressing Fn + Esc)

Press F1

Event: time 1756561171.485957, -------------- SYN_REPORT ------------
Event: time 1756561172.518223, type 4 (EV_MSC), code 4 (MSC_SCAN), value a0
Event: time 1756561172.518223, type 1 (EV_KEY), code 113 (KEY_MUTE), value 1
Event: time 1756561172.518223, -------------- SYN_REPORT ------------
Event: time 1756561172.631771, type 4 (EV_MSC), code 4 (MSC_SCAN), value a0
Event: time 1756561172.631771, type 1 (EV_KEY), code 113 (KEY_MUTE), value 0
Event: time 1756561172.631771, -------------- SYN_REPORT ------------

Press Fn + F1

Event: time 1756561144.680707, -------------- SYN_REPORT ------------
Event: time 1756561146.637851, type 4 (EV_MSC), code 4 (MSC_SCAN), value 3b
Event: time 1756561146.637851, type 1 (EV_KEY), code 59 (KEY_F1), value 1
Event: time 1756561146.637851, -------------- SYN_REPORT ------------
^[OPEvent: time 1756561146.751424, type 4 (EV_MSC), code 4 (MSC_SCAN), value 3b
Event: time 1756561146.751424, type 1 (EV_KEY), code 59 (KEY_F1), value 0
Event: time 1756561146.751424, -------------- SYN_REPORT ------------

(After pressing `Fn + Esc`)

Press F1

Event: time 1756561427.522133, -------------- SYN_REPORT ------------
Event: time 1756561432.294108, type 4 (EV_MSC), code 4 (MSC_SCAN), value 3b
Event: time 1756561432.294108, type 1 (EV_KEY), code 59 (KEY_F1), value 1
Event: time 1756561432.294108, -------------- SYN_REPORT ------------
^[OPEvent: time 1756561432.361318, type 4 (EV_MSC), code 4 (MSC_SCAN), value 3b
Event: time 1756561432.361318, type 1 (EV_KEY), code 59 (KEY_F1), value 0
Event: time 1756561432.361318, -------------- SYN_REPORT ------------

Press Fn + F1

Event: time 1756561486.638207, -------------- SYN_REPORT ------------
Event: time 1756561487.264131, type 4 (EV_MSC), code 4 (MSC_SCAN), value a0
Event: time 1756561487.264131, type 1 (EV_KEY), code 113 (KEY_MUTE), value 1
Event: time 1756561487.264131, -------------- SYN_REPORT ------------
Event: time 1756561487.399687, type 4 (EV_MSC), code 4 (MSC_SCAN), value a0
Event: time 1756561487.399687, type 1 (EV_KEY), code 113 (KEY_MUTE), value 0
Event: time 1756561487.399687, -------------- SYN_REPORT ------------

The OS one has would not be a factor for anything involving the Fn key or FnLock (Fn+Esc). That’s handled within the keyboard controller, which just would not care what OS you’re running. If it is even made aware of that. Just for anyone else with an issue with FnLock.

2 Likes

Apologies to be digging up an old thread!

I’m having F-Key issues on FW12 running Fedora 43 KDE and cannot find another post as close to the problem I’m having as this one.

Fn lock is duplicating media control actions instead of swapping function with media control. I’ve ran evtest below:

[evtest with FN Lock OFF]
[Pressing F2]
Event: time 1763482151.424685, -------------- SYN_REPORT ------------
Event: time 1763482155.797338, type 4 (EV_MSC), code 4 (MSC_SCAN), value ae
Event: time 1763482155.797338, type 1 (EV_KEY), code 114 (KEY_VOLUMEDOWN), value 1
Event: time 1763482155.797338, -------------- SYN_REPORT ------------
Event: time 1763482155.978427, type 4 (EV_MSC), code 4 (MSC_SCAN), value ae
Event: time 1763482155.978427, type 1 (EV_KEY), code 114 (KEY_VOLUMEDOWN), value 0
[Pressing FN + F2]
Event: time 1763482155.978427, -------------- SYN_REPORT ------------
Event: time 1763482161.820925, type 4 (EV_MSC), code 4 (MSC_SCAN), value 3c
Event: time 1763482161.820925, type 1 (EV_KEY), code 60 (KEY_F2), value 1
Event: time 1763482161.820925, -------------- SYN_REPORT ------------
^[OQEvent: time 1763482161.910993, type 4 (EV_MSC), code 4 (MSC_SCAN), value 3c
Event: time 1763482161.910993, type 1 (EV_KEY), code 60 (KEY_F2), value 0

[evtest with FN Lock ON]
[Pressing F2]
Event: time 1763482024.745381, -------------- SYN_REPORT ------------
Event: time 1763482038.697351, type 4 (EV_MSC), code 4 (MSC_SCAN), value ae
Event: time 1763482038.697351, type 1 (EV_KEY), code 114 (KEY_VOLUMEDOWN), value 1
Event: time 1763482038.697351, -------------- SYN_REPORT ------------
Event: time 1763482038.878347, type 4 (EV_MSC), code 4 (MSC_SCAN), value ae
Event: time 1763482038.878347, type 1 (EV_KEY), code 114 (KEY_VOLUMEDOWN), value 0
[Pressing FN + F2]
Event: time 1763482038.878347, -------------- SYN_REPORT ------------
Event: time 1763482042.179411, type 4 (EV_MSC), code 4 (MSC_SCAN), value ae
Event: time 1763482042.179411, type 1 (EV_KEY), code 114 (KEY_VOLUMEDOWN), value 1
Event: time 1763482042.179411, -------------- SYN_REPORT ------------
Event: time 1763482042.314587, type 4 (EV_MSC), code 4 (MSC_SCAN), value ae
Event: time 1763482042.314587, type 1 (EV_KEY), code 114 (KEY_VOLUMEDOWN), value 0

Does anyone know why it might be repeating media control in FN Lock mode?

Boy that’s odd.
I don’t know, really. But I’d suggest trying a mainboard reset.

Some reset procedures:
guides.frame.work/Guide/Fully+Resetting+the+Mainboard+State.

framewiki.net/guides/mainboard-reset.

Unless I’m blind, I don’t see instructions for the FWL12, guides.frame.work/c/Framework_Laptop_12

For the FWL12, the keyboard controller, which handles Fn & FnLock is a chip on the touchpad pcb, (it’s connected to the mainboard via i2c, iirc). So I’m not sure if a mainboard reset will be effective, but not sure what else to suggest. If it doesn’t help, I don’t know, I think you’re left with contacting support. If you disassemble to try a reset, take pictures, I’d do an excessive number of pictures, support likes to ask for pictures, might save you from taking it apart again. Support: knowledgebase.frame.work/contact/contact-us-rJfw7Ryglx

1 Like

Absolutely bizarre but the issue has fixed itself last night! It was an issue for 3 weeks of owning the FW12 and just randomly corrected itself.

And I’m starting to learn how right you are, their suport do love pictures as I have a ticket open for small fan issue :grinning_face_with_smiling_eyes:

Thank you for the suggested help, hopefully helps someone else reading this in future.

Have a great day!

1 Like