[SOLVED] F-keys - arch linux on framework

Framework Laptop 13 Linux
1

Hello!

Just got arch running on my freshly arrived DIY Framework.

It’s all looking good except for the fact that I can’t seem to use the F-keys to control brightness, speakers etc.

Any ideas?

Many thanks
Anna

2 Likes
2

Just to clarify, hitting fn+f-keys doesn’t work? Have you tried an EC reboot (hold down the power button for ~30s until the lights flash green)?

2 Likes
3

Yup, that’s right! Been trying different key combinations, including fn+f keys.

Definitely rebooted a few times… not sure what the EC reboot is though? Holding the power button down for an extended period of time (> 30s) doesn’t make it flash green for me…

Thanks

1 Like
4

12th Gen? This sounds like [RESPONDED] 12th gen not sending XF86MonBrightnessUp / Down. There’s a solution for it downthread.

2 Likes
5

Hi @Atomyka
The solution is on Arch Wiki here.
Make that file with the content and reboot. This should fix the problem until the issue is fixed in linux kernel at some point and we won’t need this workaround.

2 Likes
6

Hi @DHowett and @Cipher

Many thanks for your quick responses and sorry for the delay on my side.

I did try out the blacklisting option. I tried two versions of writing the file content, either

blacklist hid_sensor_hub
or
blacklist hid-sensor-hub

(found both versions in the links you referenced) and then restarted my laptop. However, the issues seems to persist.

So firstly, I wanted to check that I am indeed supposed to create framework-als-deactivate.conf as a new file? I.e. I’m not supposed to add the blacklist line to an exiting file?

Many thanks

1 Like
7

Yes @Atomyka make a new file at /etc/modprobe.d location named framework-als-deactivate.conf with blacklist hid_sensor_hub.
Do not add the above to any existing file.

if you’re comfortable with using terminal, all you need to do is
open a terminal run:
sudo nano /etc/modprobe.d/framework-als-deactivate.conf
copy & paste blacklist hid_sensor_hub
Save and that should be all.

2 Likes
8

Hmm… that’s exactly what I did (except for using vim :p) @Cipher

In case it helps, previously using fn + F7 led to a pop-up about enabling carnet browsing popping up. So maybe I have a setting somewhere that is defining shortcuts that override the basic F-key usage?

2 Likes
9

I tried it, got the same thing. Not certain but might be a feature in firefox?
Screenshot_20230328_061746

1 Like
10

hello @Atomyka ,

just in case you need it, In firefox’s about:config there’s an entry there

accessibility.browsewithcaret_shortcut.enabled you can set it to false

11

Hi @Loell_Framework
Thanks for the info! I never actually knew about:config existed… great to know!

Unfortunately, even after turning the shortcut off, I still don’t seem to able to use the fn keys as intended…

I hope this thread can remain open, perhaps someone might come up with another idea? :slight_smile: (Or have an idea why @Cipher’s and @DHowett’s good sugestion isnt’working on my end…)

Thanks

12

Hi @Atomyka , yes this thread will continue to be open, I see many threads here gets revived with new solutions.

2 Likes
13

@Atomyka have you tried running mkinitcpio -P after making the framework-als-deactivate.conf ?
Maybe the kernel images need to be rebuilt?
one more thing to try and test.

14

Quick question. Have you tried to turn press FN+ESC once?

15

Good news everyone! I went back to just checking my sway config file (which I was convinced I had done, but apparently I did not…)
Simply changing the key binding I still had from my old laptop (Librem 14 → XF86MonBrightnessUp/Down) to F7/8 did the trick!

Thanks to everyone for your suggestions in the meantime and happy it has sorted itself out now. Time to fully enjoy <Framework|arch> ! :smiley:

2 Likes
16

Thanks for getting back on this thread @Atomyka , glad to hear that it only boiled down to adjusting sway config. :slight_smile:

17

Delighted to hear this worked out, marking as solved.