You are not logged in.

#1 2026-08-25 03:06:45

LichenGrub
Member
Registered: 2026-08-25
Posts: 2

[SOLVED] KDE Plasma Blind to AJAZZ AK820 Keyboard Volume Knob

Hello:

I have a wired AJAZZ AK820 with a volume knob and I am running a fresh Arch install with KDE Plasma installed. The volume knob doesn't seem to affect the system volume at all. I can manually manipulate the volume with Plasma's slider.

Trying to adjust Plasma's keybinds doesn't do anything, as the input detection doesn't seem to recognize the knob's input.

Yet, Arch itself seems to recognize the input with the correct keycode according to "sudo libinput debug-events", an excerpt of which is pasted below:

$ sudo libinput debug-events

...
-event3   DEVICE_ADDED                 SEMICO   USB Gaming Keyboard  Consumer Control seat0 default group3  cap:kp scroll-nat
-event5   DEVICE_ADDED                 SEMICO   USB Gaming Keyboard  System Control seat0 default group3  cap:k
-event6   DEVICE_ADDED                 SEMICO   USB Gaming Keyboard  Keyboard seat0 default group3  cap:k
-event3   KEYBOARD_KEY                 +0.000s	KEY_VOLUMEUP (115) pressed
 event3   KEYBOARD_KEY                 +0.008s	KEY_VOLUMEUP (115) released
 event3   KEYBOARD_KEY                 +0.313s	KEY_VOLUMEDOWN (114) pressed
 event3   KEYBOARD_KEY                 +0.320s	KEY_VOLUMEDOWN (114) released
 event3   KEYBOARD_KEY                 +0.728s	KEY_VOLUMEUP (115) pressed
 event3   KEYBOARD_KEY                 +0.737s	KEY_VOLUMEUP (115) released
 event3   KEYBOARD_KEY                 +1.041s	KEY_VOLUMEDOWN (114) pressed
 event3   KEYBOARD_KEY                 +1.049s	KEY_VOLUMEDOWN (114) released
...

I also went and looked at dmesg to see if I could parse anything, but I am not knowledgeable enough to know what any of it means. Regardless, below is a section related to my keyboard:

$ sudo dmesg

...
[ 8451.260479] usb 1-5: new low-speed USB device number 21 using xhci_hcd
[ 8451.511035] usb 1-5: New USB device found, idVendor=1a2c, idProduct=9605, bcdDevice= 1.16
[ 8451.511043] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 8451.511046] usb 1-5: Product: USB Gaming Keyboard 
[ 8451.511048] usb 1-5: Manufacturer: SEMICO  
[ 8451.538111] input: SEMICO   USB Gaming Keyboard  as /devices/pci0000:00/0000:00:02.1/0000:02:00.0/usb1/1-5/1-5:1.0/0003:1A2C:9605.000D/input/input44
[ 8451.661289] hid-generic 0003:1A2C:9605.000D: input,hidraw3: USB HID v1.10 Keyboard [SEMICO   USB Gaming Keyboard ] on usb-0000:02:00.0-5/input0
[ 8451.691193] input: SEMICO   USB Gaming Keyboard  Consumer Control as /devices/pci0000:00/0000:00:02.1/0000:02:00.0/usb1/1-5/1-5:1.1/0003:1A2C:9605.000E/input/input45
[ 8451.743959] input: SEMICO   USB Gaming Keyboard  System Control as /devices/pci0000:00/0000:00:02.1/0000:02:00.0/usb1/1-5/1-5:1.1/0003:1A2C:9605.000E/input/input46
[ 8451.744066] input: SEMICO   USB Gaming Keyboard  Keyboard as /devices/pci0000:00/0000:00:02.1/0000:02:00.0/usb1/1-5/1-5:1.1/0003:1A2C:9605.000E/input/input48
[ 8451.744212] hid-generic 0003:1A2C:9605.000E: input,hiddev98,hidraw4: USB HID v1.10 Keyboard [SEMICO   USB Gaming Keyboard ] on usb-0000:02:00.0-5/input1

I'd like to get my volume knob working. This is my first major problem on Arch and I would appreciate some help. Let me know if more info is needed; I am happy to oblige.

Not sure if it's relevant, but the knob did work on a Fedora installation without issue prior to installing Arch. I cannot compare anything between the two because Fedora was overwritten by Arch.

Thank you.

Last edited by LichenGrub (2026-08-25 07:54:20)

Offline

#2 2026-08-25 07:53:55

LichenGrub
Member
Registered: 2026-08-25
Posts: 2

Re: [SOLVED] KDE Plasma Blind to AJAZZ AK820 Keyboard Volume Knob

I ended up solving the issue using keyd. Below is my .conf for keyd that ended up working for me:

[ids] 
1a2c:9605:e4dfba95            

volumeup = leftalt-f11
volumedown = leftalt-f12
mute = leftalt-f10

I bound volume up to Alt + f11, volume down to Alt + f12, and so on in KDE Plasma's shortcut menu. I chose Alt-f10~12 because they are unused across all the programs I checked.

For anyone experiencing problems involving inputs from unusual peripherals, keyd seems to be a great tool.

Offline

Board footer

Powered by FluxBB