You are not logged in.
Pages: 1
Hey there. I did a new Arch install yesterday. The install was straightforward and things are up and running smoothly; it's not my first Arch install as I ran it as my daily driver during college. I have a post-install question that I'm hoping to get some assistance with. Bear in mind this is pretty nitpicky/niche so even if it goes unresolved it's not going to affect me at all, but it is something I'd like to get sorted out if possible.
For full(-ish) context, my setup is configured as follows:
1TB NVMe SSD partitioned into three partitions. Partition 1 is a 512MiB EFI partition, partition 3 is a 64GiB encrypted swap partition, and partition 2 is an encrypted BTRFS partition that fills the rest of the space.
Using mkinitcpio to generate kernel images.
Other hardware is AMD 5800X3D CPU, AMD 7900XTX GPU, 64GiB memory if that matters at all.
I'm running KDE Plasma/Wayland.
I attempted to use a signed UKI for Secure Boot essentially following this write-up, but am now just using a generic kernel (more info in the question below).
I use an Elgato Stream Deck Pedal for push-to-talk in Discord. I wrote a really simple program for binding the different buttons to different keys and generating those keypresses via a virtual input which then gets routed to Discord through KDE's Xwayland support. I noticed that when using the pedal on Arch Linux each button generates "UNK248" when not running my own program, which appear to be KEY_MICMUTE. When running my program, it is KEY_MICMUTE + whatever else I have bound. I cannot for the life of me figure out where that key mapping is actually coming from. Is there any way to determine if a separate program is generating those presses or if it's somehow coming from just the pedal itself? It's not the end of the world if it stays that way since I can work around that, but ideally I can get rid of those extra presses altogether.
Any help is appreciated!
Offline
Pages: 1