You are not logged in.
Pages: 1
So I recently bought an 8 - button mouse from ant esports and configured it in another windows device (which surprisingly worked).
However most of its buttons are being detected except the rapid fire one and the two middle ones (though i suppose those are for DPI and LED control)
I tried xev to find out that button 1, 2, 3, 8 and 9 are being detected while my rapid fire button is being detected as 1.
Found out about libinput in another thread but i am on wayland so it didn't change much.
So, mainly I wanna ask if there is any way to configure my mouse in arch without switching here and there, and also anyway to make these buttons work.
Offline
Which mouse is this? If it's logitech/some razer ones, there's libratbag and piper for handling some internal firmware of specific mice: https://archlinux.org/packages/extra/any/piper/
Generally that the DPI and led buttons are not detected as buttons by the OS itself is normal, they'll be handled in the firmware.
Last edited by V1del (2024-01-17 14:05:02)
Offline
I did mention its an ant esports mouse, specifically GM 320, and yeah i have already tried piper, it did not work. I just forgot to include it in the thread.
Offline
The lack of capitalization quite frankly makes it read generic + typo.
The post is generally rather incoherent:
However most of its buttons are being detected except the rapid fire one and the two middle ones
I tried xev to find out that button 1, 2, 3, 8 and 9 are being detected while my rapid fire button is being detected as 1
4,5,6,7 are the vertical and horizontal wheel and I suspect the rapid fire button simply autorepeats?
What actually doesn't work because
I wanna ask if there is any way to configure my mouse in arch without switching here and there
is incomprehensibly generic.
Offline
Sorry for my language I guess? I am not a native english speaker.
As for the *Rapid Fire Button*, it is remappable in windows so I dont think it just repeats left click.
My main problem is that every software capable of remapping mouse buttons does not recognise this rapid fire button as a seperate button, while windows does.
Offline
There are "some" references to Ant mice in libratbag though those that are there read like not fully fleshed out and with a high chance of breaking the device, so you probably want to stay clear of that...
https://github.com/libratbag/libratbag/issues/1512
https://github.com/libratbag/libratbag/issues/1553
"Windows" doesn't recognize it either. The driver software does and can remap it "internally" to rapid fire something else, im assuming.
Last edited by V1del (2024-01-17 15:04:04)
Offline
Does it produce different events for the left and RF button in evtest?
Offline
Does it produce different events for the left and RF button in evtest?
Yeah thats the issue, it doesnt produce different events.
Offline
I tried xev … on wayland
https://man.archlinux.org/man/extra/evtest/evtest.1.en
There's about a 20.000 mile difference between those things.
One is pointless because xev talks to xwayland and the other one pretty much prints what the kernel sees.
Offline
I tried xev … on wayland
https://man.archlinux.org/man/extra/evtest/evtest.1.en
There's about a 20.000 mile difference between those things.
One is pointless because xev talks to xwayland and the other one pretty much prints what the kernel sees.
Yeah its the same in evtest too.
(for left click)
Event: time 1705505340.035693, -------------- SYN_REPORT ------------
Event: time 1705505340.711987, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1705505340.711987, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
Event: time 1705505340.711987, -------------- SYN_REPORT ------------
Event: time 1705505340.827956, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1705505340.827956, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
Event: time 1705505340.827956, -------------- SYN_REPORT ------------(for RF button)
Event: time 1705505424.819658, -------------- SYN_REPORT ------------
Event: time 1705505424.837698, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1705505424.837698, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
Event: time 1705505424.837698, -------------- SYN_REPORT ------------
Event: time 1705505424.855705, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1705505424.855705, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0Though yeah for some reason Rapid fire button does repeat left click in evtest but doesn't do so anywhere else for some reason, basically being useless.
Last edited by 0xS (2024-01-17 15:41:29)
Offline
Please use [code][/code] tags. Edit your post in this regard.
Rapid fire button does repeat left click in evtest but doesn't do so anywhere else
Specify "anywhere else" and try an X11 session (can be openbox and running xev there)
Since the HW generates the same event, the only ways to discriminate that would be
1. detect the rapid repeat and alter the (subsequently) generated event on that base (you'd still get a one left-click before the change)
2. send some control command to the mouse to alter its behavior (which is very device specific and possibly proprietary, you'd have to intercept the USB communication on windows to get to this if the vendor doesn't specifcy that somewhere publically)
Offline
From anywhere else I meant the whole system except the evtest command window, imma try X11 session real quick.
Offline
No difference in xev outputs after changing to X11.
Last edited by 0xS (2024-01-17 15:45:50)
Offline
You might get screwed by https://wayland.freedesktop.org/libinpu … ncing.html
=> https://askubuntu.com/questions/1199820 … n-libinput
Offline
You might get screwed by https://wayland.freedesktop.org/libinpu … ncing.html
=> https://askubuntu.com/questions/1199820 … n-libinput
Thanks a lot man, by following the second link I was able to make my RP button do its function properly.
Offline
\o/
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Offline
Hi OP, as I have the same mouse and I am a little newbie in the world of arch linux and Rapid fire button is not working for me or I can say it is working like a lift click for me so can you please write a step by step solution in here, it will be a great help for me
Offline
Please don't DM me for attention or private help.
Thanks a lot man, by following the second link I was able to make my RP button do its function properly.
And the second link was https://askubuntu.com/questions/1199820 … n-libinput
Have you read that?
Offline
Yes tried to but its a lot as I am new in here it's not easy for me to figure out as these no exact resolution written, so can you please write the exact steps, it will be a great help
Offline
There's an *exact* instruction in the top answer of the ubuntu thread, referencing the same explanation in the libinput documetnation.
The part you need to adjust is your actual mouse model which neither you nor the OP have ever recorded.
sudo libinput list-devices | grep 'Device:'will tell you.
You'll have to use your own brain a bit if you intend to use archlinux, if your stance is to "please remote control me on every minor step" my remote control instruction is to buy a Tv and watch soap operas all day.
Offline
Thank you Sir, didn't needed to be that rude, I am trying to understand this all, It's my second day using Arch and after setting all this up I am little exhausted that's why I asked for it, I am sorry if I have irritated you
Offline
The plan wasn't to be rude but to be honest.
If you're exhausted, get some rest and approach the situation later on fresh, but your approach of "I refuse to think by myself at all, please spoon feed me detailed instructions on every minor step" will not work with archlinux.
If you want to keep using arch, get used to read the wiki and man pages and actually digest what you read, interpret it and interpolate solutions from there.
The point of archlinux isn't to say "I'm running arch, btw" on r/unixporn - you can just install Ubuntu and set an archlinux wallpaper and fake the os-release entry for that.
Offline
Pages: 1