I love the song Save Myself by ZOEgirl & some other non Christian songs but want more Christian artists. I like Faith Evans, Mary J. Blige, Ashanti, Aaliyah, Mya, Cassie, Destiny's Child, TLC. Those are just some examples. Give me some Christian equivalents!

When I initially tried these fixes, it just used the default keys. And input remapper wasn't working. So this is a guide for those who were annoyed like me! Here's the fix. Your keyboard's exact scan codes will differ from mine, so the configs below are just small examples. All this tested on CachyOS, KDE Plasma.

1. Install keyd

sudo pacman -S keyd
sudo systemctl enable --now keyd

2. Find your keys' codes

sudo keyd monitor

Press each macro key. Note the device ID (e.g. 1038:1200:...) and the raw scan code each key sends. This is your source of truth — everyone's codes are different.

3. Rename the scan codes

Create /etc/udev/hwdb.d/99-steelseries.hwdb. One space before each line e.g.:

evdev:input:b0003v1038p1200*
 KEYBOARD_KEY_700f4=f13
 KEYBOARD_KEY_700f5=f14

(there should be multiple in your list — add one line per key, map each individual extra macro key) Apply and replug the keyboard:

sudo systemd-hwdb update
sudo udevadm trigger --action=change

Re-run keyd monitor to confirm the keys now report f13, f14, etc.

4. Map them to actions

Create /etc/keyd/steelseries.confe.g.:

[ids]
1038:1200

[main]
f13 = playpause
f14 = C-c

(The playpause is for a media key, C-c for Ctrl+C, etc. Map your renamed keys to whatever you want.)

sudo systemctl restart keyd

Modifier syntax: C=Ctrl S=Shift A=Alt M=Meta.

Things to be aware of:

• Some keys can't be remapped. Profile/G-shift keys are firmware-handled and send nothing to the OS. If a key prints nothing in keyd monitor, no config seems to catch it.
• Watch for code collisions. If a macro key sends a real key's code (e.g. tab), mapping it affects the real key too. Rename it in the hwdb first.

Works on any desktop (KDE, GNOME, Hyprland) since it's all below the desktop layer. Hope it saves someone the trial-and-error.

When I initially tried these fixes, it just used the default keys. And input remapper wasn't working. So this is a guide for those who were annoyed like me! Here's the fix. Your keyboard's exact scan codes will differ from mine, so the configs below are just small examples. All this tested on CachyOS, KDE Plasma.

1. Install keyd

sudo pacman -S keyd
sudo systemctl enable --now keyd

2. Find your keys' codes

sudo keyd monitor

Press each macro key. Note the device ID (e.g. 1038:1200:...) and the raw scan code each key sends. This is your source of truth — everyone's codes are different.

3. Rename the scan codes

Create /etc/udev/hwdb.d/99-steelseries.hwdb. One space before each line e.g.:

evdev:input:b0003v1038p1200*
 KEYBOARD_KEY_700f4=f13
 KEYBOARD_KEY_700f5=f14

(there should be multiple in your list — add one line per key, map each individual extra macro key) Apply and replug the keyboard:

sudo systemd-hwdb update
sudo udevadm trigger --action=change

Re-run keyd monitor to confirm the keys now report f13, f14, etc.

4. Map them to actions

Create /etc/keyd/steelseries.confe.g.:

[ids]
1038:1200

[main]
f13 = playpause
f14 = C-c

(The playpause is for a media key, C-c for Ctrl+C, etc. Map your renamed keys to whatever you want.)

sudo systemctl restart keyd

Modifier syntax: C=Ctrl S=Shift A=Alt M=Meta.

Things to be aware of:

• Some keys can't be remapped. Profile/G-shift keys are firmware-handled and send nothing to the OS. If a key prints nothing in keyd monitor, no config seems to catch it.
• Watch for code collisions. If a macro key sends a real key's code (e.g. tab), mapping it affects the real key too. Rename it in the hwdb first.

Works on any desktop (KDE, GNOME, Hyprland) since it's all below the desktop layer. Hope it saves someone the trial-and-error.

When I initially tried these fixes, it just used the default keys. And input remapper wasn't working. So this is a guide for those who were annoyed like me! Here's the fix. Your keyboard's exact scan codes will differ from mine, so the configs below are just small examples. All this tested on CachyOS, KDE Plasma.

1. Install keyd

sudo pacman -S keyd
sudo systemctl enable --now keyd

2. Find your keys' codes

sudo keyd monitor

Press each macro key. Note the device ID (e.g. 1038:1200:...) and the raw scan code each key sends. This is your source of truth — everyone's codes are different.

3. Rename the scan codes

Create /etc/udev/hwdb.d/99-steelseries.hwdb. One space before each line e.g.:

evdev:input:b0003v1038p1200*
 KEYBOARD_KEY_700f4=f13
 KEYBOARD_KEY_700f5=f14

(there should be multiple in your list — add one line per key, map each individual extra macro key) Apply and replug the keyboard:

sudo systemd-hwdb update
sudo udevadm trigger --action=change

Re-run keyd monitor to confirm the keys now report f13, f14, etc.

4. Map them to actions

Create /etc/keyd/steelseries.confe.g.:

[ids]
1038:1200

[main]
f13 = playpause
f14 = C-c

(The playpause is for a media key, C-c for Ctrl+C, etc. Map your renamed keys to whatever you want.)

sudo systemctl restart keyd

Modifier syntax: C=Ctrl S=Shift A=Alt M=Meta.

Things to be aware of:

• Some keys can't be remapped. Profile/G-shift keys are firmware-handled and send nothing to the OS. If a key prints nothing in keyd monitor, no config seems to catch it.
• Watch for code collisions. If a macro key sends a real key's code (e.g. tab), mapping it affects the real key too. Rename it in the hwdb first.

Works on any desktop (KDE, GNOME, Hyprland) since it's all below the desktop layer. Hope it saves someone the trial-and-error.