# Is there a way to get both F20 and AudioMicMute through to Linux?

**URL:** https://community.keyboard.io/t/is-there-a-way-to-get-both-f20-and-audiomicmute-through-to-linux/13675
**Category:** Help and Getting Started
**Tags:** question
**Created:** [January 12, 2026, 10:34am UTC](https://community.keyboard.io/t/is-there-a-way-to-get-both-f20-and-audiomicmute-through-to-linux/13675 "2026-01-12T10:34:24Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![bjn](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/bjn/32/5337_2.png) [@bjn](https://community.keyboard.io/u/bjn)
#### Post date: [January 12, 2026, 10:34am UTC](https://community.keyboard.io/t/is-there-a-way-to-get-both-f20-and-audiomicmute-through-to-linux/13675/1 "2026-01-12T10:34:24Z")

</div>

For years now I’ve been using F13 through F24 on a layer to trigger various things in my desktop environment.

I switched distro very recently and am setting things back up again. In going through getting them recognized as F13 through F24 I paid more attention this time to how they’re interpreted by default in Linux.

```auto
F13: key 191, XF86Tools
F14: key 192, XF86Launch5
F15: key 193, XF86Launch6
F16: key 194, XF86Launch7
F17: key 195, XF86Launch8
F18: key 196, XF86Launch9
F19: key 197, NoSymbol
F20: key 198, XF86AudioMicMute
F21: key 199, XF86TouchpadToggle
F22: key 200, XF86TouchpadOn
F23: key 201, XF86TouchpadOff
F24: key 202, NoSymbol

```

I’d like to set another key to trigger `XF86AudioMicMute`. But I don’t know how. The closest-sounding things I found in the [key defs](https://github.com/keyboardio/Kaleidoscope/tree/master/src/kaleidoscope/key_defs) I could find are `Consumer_MicrophoneCa` and `Consumer_StartOrStopMicrophoneCapture`. I tried both, and found that both come through as `key 248, NoSymbol`.

I’ve been searching around and I haven’t been able to figure out how to coax the system into seeing it as anything else.

I could remove my F20 remapping (by removing XKB option `fkeys:basic_13-24`, and then mapping the other higher F keys one by one, which I know how to do) and then send F20 and have the default behaviour of it being interpreted as `XF86AudioMicMute` but then I lose the real F20.

Any ideas? I’m finding it very hard to research, since I don’t know which of the many layers (Kaleidoscope, HID, udev, XKB, probably more?) to dig in to.

---

<div class="post-metadata">

### Author: ![bjn](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/bjn/32/5337_2.png) [@bjn](https://community.keyboard.io/u/bjn)
#### Post date: [January 13, 2026, 11:19pm UTC](https://community.keyboard.io/t/is-there-a-way-to-get-both-f20-and-audiomicmute-through-to-linux/13675/2 "2026-01-13T23:19:44Z")

</div>

Ah, I found that my window manager will allow me to bind raw keycodes, so I’ve got it mostly doing what I wanted.

I think Kaleidoscope isn’t doing anything wrong; if there’s an issue here I think it’s in one of the layers somewhere in between there and the WM.