You are not logged in.
I have bought a new keyboard, the White Shark Templar. This keyboard has 19-key anti-ghosting features as i confirmed on my Windows boot.
However under arch linux if i press 7 or more keys, the keyboard itself seems to become inactive while the keydown event gets repeated indefinitely for the last key pressed.
Therefore i am lead to believe it is a software difference of some kind.
I would greatly appreciate some help with this.
Last edited by Muzzy (2023-10-18 20:24:00)
Offline
Please start by posting relevant logs. There's nothing really to go on without that information to identify the problem. The problem could be hardware, kernel, X/Wayland, etc.
Offline
What is the typing test under console terminal without window manager, Xorg, wayland involved?
Offline
Did I miss an evolutionary update or do gam0rz now operate the keyboard all hands and feet?
wtf does anybody need a 19-key roll…whatever.
The autorepeat is probably a red herring and just happens b/c the OP is resting their hands toolong™
https://www.reddit.com/r/linux_gaming/c … _rollover/
Does the keyboard come w/ a special driver on windows?
Does it have a HW switch between 6 and n-key rollover?
Online
Here is the Xorg log and the output of journalctl -k.
Regarding the typing test, here is the output of
showkey --keycodes[muzzy@desktop ~]$ sudo !!
sudo showkey --keycodes
kb mode was ?UNKNOWN?
[ if you are trying this under X, it might not work
since the X server is also reading /dev/console ]
press any key (program terminates 10s after last keypress)...
keycode 28 release
jkhsfdkeycode 36 press
keycode 37 press
keycode 35 press
keycode 31 press
keycode 33 press
keycode 32 press
ddddddkeycode 32 press
keycode 32 press
keycode 32 press
keycode 32 press
keycode 32 press
keycode 32 press
keycode 32 press
keycode 32 press
keycode 32 press
keycode 32 press
keycode 32 press
keycode 32 press
keycode 32 press
keycode 32 press
keycode 32 press
keycode 32 press
keycode 32 press
keycode 32 press
dddddddddddddddddkeycode 32 press
keycode 32 press
keycode 32 press
keycode 32 press
keycode 32 press
keycode 32 press
keycode 32 press
keycode 32 press
keycode 32 press
keycode 32 press
keycode 32 press
keycode 32 press
keycode 32 press
keycode 32 press
keycode 32 press
keycode 32 press
keycode 32 press
keycode 32 press
ddddddddddddddddkeycode 32 pressIt just loops that last part until i replug it in. And yes it happens even under say tty2.
Regarding a special driver, all windows popped up with was a ready to use notification after a couple seconds, i had to manually install no extra stuff.
I have searched the keyboard and read the box it came in a couple times and to my knowledge there is no hardware switch for NKR.
Also I'm not sure about evolution of gamers or the utility of 19 key rollover I'm just a guy that needed a new keyboard and took one off a shelf, It's nice to have your peripherals work the right way regardless.
Offline
This could be a limitation from firmware side. Some firmware allow a keybinding to enable/disable NKRO or 6KRO. E.g: https://docs.qmk.fm/#/faq_misc?id=nkro-doesnt-work
Commercial keyboard doesn't support firmware flushing, but you could check on manufacture if they are willing to tell you possible keybinding.
Offline
You wanted to test that w/ evtest.
all windows popped up with was a ready to use notification after a couple seconds
Check the device properties, that very much sounds like windows fetched a driver over the network.
However that won't help you to activate NKRO on linux (or anywhere else) - esp. not if it's part-emulated by the driver.
You'll have to settle for pressing 6 keys at once or ask the vendor how the NKRO is activated.
Online
Gotcha, I guess there is no other more convenient way. I'll mark the thread as solved.
Offline