-
-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SteelSeries Rival 3 mapped-value (button6) not working #220
Comments
Hello, Thank you for your report. I you are not able to make it work, I think it is a bug.
It may worked on my Rival 3 in the past (or maybe I not tested enough? It was years ago ^^'). Maybe it depends on the firmware revision... Anyway, I have a bunch of Rival 3 at work, I will make some tests on them [when I will be able to come back to work...] to try to figure out what happens :) |
So I updated the firmware and button6=button6 mapping seems to work. This seems to me like not a bug of |
Problem description
SteelSeries Rival 3
button6
seems to be not working.Command Used:
rivalcfg --buttons "buttons(button6=button6)"
Alternative Command Used for diagnosis:
rivalcfg --buttons "buttons(button5=button6)"
Checked using screenkey
All other buttons M1 to M5 seem to be working as expected.
M6 from the Rival 110 mouse works fine (to be sure problem is not somewhere else)
Checked using libinput
libinput debug-events /dev/input/event#
Results:
The Rival 110 gives
BTN_FORWARD (277)
event (--btn6_mode=os
in that case), which the Rival 3 does not give.I also tried checking the Rival 3 keyboard events and there was nothing for
button6
.Further Diagnosis Required
Could it perhaps be a firmware issue?
Can someone confirm if they have a working
button6
action?Installation information
→ rivalcfg seems to be working fine since I have started using it. I have used it with Rival 110 for a few years.
→ SteelSeries Rival 3 was bought just recently.
System information
I also tried the same from source. same result.
The text was updated successfully, but these errors were encountered: