Plasma user here. Been using Arch for years but always had someone else maintaining my system so still a newbie.
I have an Acer KU-0760 keyboard - not a new model by any means, but I’m not planning to swap it out any time soon - and the unique thing about it is that it has a volume control wheel in the upper right corner.
Thing is I’ve never been able to make it work - the system just doesn’t register when I do anything with it, and I realized that its probably due to the system settings.
Problem is these are the only Acer models available for selection, so I’m still stuck with just Generic 105.
So now I’m wondering - is there any way to add additional models to this menu, or some other way for the system to recognize my volume wheel?
sudo libinput debug-events
And
wev
Then test the volume wheel after each command, do you see volume events firing?
first command resulted in
sudo: libinput: command not found
and the second didn’t work either, and can’t work since this system uses X11
choose the 104 key generic because that’s what you have.
the media keys and volume another story and you are going to need to explore what (if any) signals are being sent when those are activated.
when i use:
xev | grep key on my keyboard (because i’m using X11), try wev if you are wayland
the volume dn/up are keycodes 122/123
the prev|play|next buttons are keycodes 173|172|171
from there you can likely intercept them so they can be used for what you want.
input-remapper is a powerful GUI tool for such things once you find out what the keys are doing.
short of that you might be able to create a custom keyboard layout that combines your english and russian characters along with whatever is needed to map those media controls into a single layout.
so to answer your question: Yes.
likely several ways.
Oh, I just assumed you’re under Wayland.
Now the same commands under X11 are:
- Same command, just install the package first:
sudo pacman -Sy libinput
then
sudo libinput debug-events
- The X11 equivalent of
wev is:
xev -event keyboard
doesn’t seem to be detecting it - other keys work just fine but the wheel remains radio silent
tbf the keyboard is pretty old so i wouldnt be surprised if its just broken by now lol
not even with the libinput-tools installed?
if there is no signal at all, then it’s likely busted or the firmware was changed via the windows software that came with it (assuming there is any) and the signal has been turned off.
if you have access to a windows machine, look up the driver/software for the keyboard and install it.
then, using the software, reset the keyboard back to factory defaults (specifically the volume controls) and then see if linux can read the volume control after that change to the firmware.
maybe later, but yeah.
thanks for the help anyway i appreciate it
if xev / wev can’t detect the wheel events, it could mean that there is simply no mapping from its hardware level code to something the higher levels understand.
You should try evtest instead - it works on a lower level. The volume wheel should generate events of types MSC and KEY, but I assume you`ll only get MSC. Is that right?
Note that some keyboards register as multiple devices (usually one extra for multimedia keys).
evtest offers up 5 devices for my huntsman V2, but the only one that registers events from the volume wheel, is the one called Razer Razer Huntsman V2 Keyboard
