#Wootility 4.4.12 does not recognize the 60HE in Arch Linux

1 messages · Page 1 of 1 (latest)

tidal frost
#

Keyboard: Wooting 60HE arm
Software: Wootility 4.4.12 appimage installed from AUR
OS: Arch Linux
Kernel: 5.19.10
Desktop Environement: KDE Plasma 5.25.5

Issue: The keyboard works fine but the wootiliy software does not recognize it, it is therefore impossible to configure.

Attempt at solving the issue:

  1. The steps to restore the keyboard to factory setting were followed but to no success after the software also failed to find the keyboard in restore mode.
  2. The keyboard was plugged to a windows 11 machine and there the wootility software had no issue finding the keyboard. A firmware update was done. After plugging it back in the Linux machine the issue persisted.
  3. Followed the tutorial for the rules found here: https://help.wooting.io/en/article/wootility-configuring-device-access-for-wootility-under-linux-udev-rules-r6lb2o/.
  4. Tried to run the app with sudo privileges, got the following result: [0929/175117.633751:FATAL:electron_main_delegate.cc(297)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.
    Trace/breakpoint trap.
  5. Ran sudo wootility-lekker --no-sandbox but the application only shows a white windows, when quitting with CTRL+C , the keyboard crashed.

Output of the terminal when running the software from the terminal can be found in the next post.

I also noticed that the permission is given for the device, has a productId: 4880 (hex: 1310) & vendorId: 12771 (hex: 31e3) while in the udev/wooting.rules the wooting 60HE has the vendorId 31e3 & the productID 1300.

#

Modifying the wooting.rules file by adding the following lines solved the issue:

SUBSYSTEM=="hidraw", ATTRS{idVendor}=="31e3", ATTRS{idProduct}=="1310", MODE:="0660", GROUP="input"
SUBSYSTEM=="usb", ATTRS{idVendor}=="31e3", ATTRS{idProduct}=="1310", MODE:="0660", GROUP="input"
# Wooting 60HE (ARM) Alt-gamepad mode
SUBSYSTEM=="hidraw", ATTRS{idVendor}=="31e3", ATTRS{idProduct}=="1311", MODE:="0660", GROUP="input"
SUBSYSTEM=="usb", ATTRS{idVendor}=="31e3", ATTRS{idProduct}=="1311", MODE:="0660", GROUP="input"
# Wooting 60HE (ARM) 2nd Alt-gamepad mode
SUBSYSTEM=="hidraw", ATTRS{idVendor}=="31e3", ATTRS{idProduct}=="1312", MODE:="0660", GROUP="input"
SUBSYSTEM=="usb", ATTRS{idVendor}=="31e3", ATTRS{idProduct}=="1312", MODE:="0660", GROUP="input"

# Wooting 60HE (ARM) update mode
SUBSYSTEM=="hidraw", ATTRS{idVendor}=="31e3", ATTRS{idProduct}=="131f", MODE:="0660", GROUP="input"```
#

Exiting the software make the keyboard unresponsive and need to be unplugged and replugged.

high ingot
#

Whoopsie, I forgot to add 60HE ARM to the udev rules. I'll get that updated, and RE: Exiting the software making the keyboard unresponsive, I'm already aware and working on a fix

hazy kraken
#

Awesome.

#

How dare you be anti linux

tidal frost
#

@high ingot Thanks.

broken yarrow
#

Wouldn't it be easier to just use the web version of the Wootility?

hazy kraken
#

Well yes but that's not a solution to a problem :p

broken yarrow
#

well, if the problem is not be able to use the local wootilty, you are right
if the problem is just config the keeb you are wrong

#

woa png pfps look gorgeous with the banner behind