Im pretty sure that the problem atleast in my case is a driver thats not working properly…
Another workaround i think is nicer than using a different key is to use a udev rule.
Make a file 70-keyboard-fix.hwdb and place it in /lib/udev/hwdb.d/70-keyboard.hwdb
Content of file:
evdev:atkbd:dmi:*
KEYBOARD_KEY_ae=!volumedown
KEYBOARD_KEY_b0=!volumeup
The Keyboard keys should be the same in most cases. If not u need to check what the key code u get when u press the volume button. To do that simply use “evtest” which one might need to run with sudo.
If you are doing that you should get some output like this when pressing the volume key.
Event: time 1669304321.742435, type 4 (EV_MSC), code 4 (MSC_SCAN), value b0
Event: time 1669304321.742435, type 1 (EV_KEY), code 115 (KEY_VOLUMEUP), value 1
Event: time 1669304321.742435, -------------- SYN_REPORT ------------
Event: time 1669304321.742448, type 4 (EV_MSC), code 4 (MSC_SCAN), value b0
Event: time 1669304321.742448, type 1 (EV_KEY), code 115 (KEY_VOLUMEUP), value 0
the value for EV_MSC is the code after KEYBOARD_KEY.
Also evdev:atkbd:dmi:* is applying the fix for ALL keyboards. Since this might be bad in some cases (eg. if the keykode is not for vol changing) this might introduce some unwanted behavior.
Best wishes 