Asus Numpad can't get the initial numlock state

[kamack38]

After running sudo asus-numpad, I get an error:

Error: Failed to get initial numlock state

I installed the program via cargo command in README.

[iamkroot]

What OS and DE are you running?

[kamack38]

I'm running Arch Linux with kernel 5.19.4-arch1-g14-1 and awesomewm-git

[iamkroot]

I've pushed some changes to not abort when the numlock detection fails. Could you try it out? Should be as easy as re-running the cargo install command from readme.

Also, which laptop model do you have? The error should only pop up when your laptop's keyboard driver does not support the Numlock key, which is bizarre.

[kamack38]

I have Asus ROG Strix Scar G533QS

[iamkroot]

I've updated master with some fixes to the keyboard detection. Could you please check if it works now? You'll need to install through the "manual" method as mentioned in the README.

[kamack38]

Sorry for not giving updates for so long, but it still doesn't work. I get this error

[2023-02-04T16:39:34Z ERROR asus_numpad] Failed to get initial numlock state. There might be something wrong with evdev keyboard detection. Using device: Asus Keyboard

[kamack38]

My kernel is 6.1.6-arch1-g14-1 and I tried it both on X11 (awesome-git) and Wayland (hyprland-nvidia-git). My laptop model is Asus ROG Strix G533QS

[iamkroot]

I can't really help much here. Did any of the other numpad scripts (such as https://github.com/asus-linux-drivers/asus-numberpad-driver/) work for you? Then maybe we can see what they do to make it work

[kamack38]

I know it's been a long time, but I hope that you'll be able to help. I was able to run the program successfully, but I'm not able to enable the numpad. Furthermore, I've tried all the layouts, but none of them works. Clicking numlock using an external keyboard lights up the numpad, but upon clicking anywhere on it, it is disabled instantaneously. Here's a log output:

[2024-03-29T18:12:09Z INFO  asus_numpad] Config: Config { layout: GX701, disable_numlock_on_start: false, calc_start_command: Keys([KEY_CALC]), calc_stop_command: None }
[2024-03-29T18:12:09Z DEBUG asus_numpad] setting on Full
[2024-03-29T18:12:11Z TRACE asus_numpad] TP EV_ABS(ABS_MT_TRACKING_ID) 233
[2024-03-29T18:12:11Z TRACE asus_numpad] TP EV_ABS(ABS_MT_POSITION_X) 624
[2024-03-29T18:12:11Z TRACE asus_numpad] TP EV_ABS(ABS_MT_POSITION_Y) 1439
[2024-03-29T18:12:11Z TRACE asus_numpad] TP EV_KEY(BTN_TOUCH) 1
[2024-03-29T18:12:11Z TRACE asus_numpad] TP EV_KEY(BTN_TOOL_FINGER) 1
[2024-03-29T18:12:11Z DEBUG asus_numpad] Start tap
[2024-03-29T18:12:11Z DEBUG asus_numpad] Grabbing
[2024-03-29T18:12:11Z DEBUG asus_numpad] Keydown KEY_KP1
[2024-03-29T18:12:11Z TRACE asus_numpad] TP EV_ABS(ABS_X) 624
[2024-03-29T18:12:11Z TRACE asus_numpad] TP EV_ABS(ABS_Y) 1439
[2024-03-29T18:12:11Z TRACE asus_numpad] TP EV_SYN(SYN_REPORT) 0
[2024-03-29T18:12:11Z DEBUG asus_numpad] setting off
^[[F[2024-03-29T18:12:11Z TRACE asus_numpad] KB LED_NUML, 0
[2024-03-29T18:12:11Z TRACE asus_numpad] KB SYN_REPORT, 0
[2024-03-29T18:12:11Z TRACE asus_numpad] TP EV_SYN(SYN_REPORT) 0
[2024-03-29T18:12:11Z TRACE asus_numpad] TP EV_SYN(SYN_REPORT) 0
[2024-03-29T18:12:11Z TRACE asus_numpad] TP EV_SYN(SYN_REPORT) 0
[2024-03-29T18:12:11Z TRACE asus_numpad] TP EV_ABS(ABS_MT_POSITION_X) 623
[2024-03-29T18:12:11Z TRACE asus_numpad] TP EV_ABS(ABS_X) 623
[2024-03-29T18:12:11Z TRACE asus_numpad] TP EV_SYN(SYN_REPORT) 0
[2024-03-29T18:12:11Z TRACE asus_numpad] TP EV_SYN(SYN_REPORT) 0
[2024-03-29T18:12:11Z TRACE asus_numpad] TP EV_ABS(ABS_MT_TRACKING_ID) -1
[2024-03-29T18:12:11Z TRACE asus_numpad] TP EV_KEY(BTN_TOUCH) 0
[2024-03-29T18:12:11Z TRACE asus_numpad] TP EV_KEY(BTN_TOOL_FINGER) 0
[2024-03-29T18:12:11Z DEBUG asus_numpad] End tap
[2024-03-29T18:12:11Z DEBUG asus_numpad] Keyup KEY_KP1
[2024-03-29T18:12:11Z TRACE asus_numpad] TP EV_SYN(SYN_REPORT) 0

I'm using the git version btw

[iamkroot]

Hi @kamack38 this is most likely a case of unsupported hardware - your laptop model probably needs some unique setup to get the touchpad working. I would again recommend trying out some of the other numpad softwares and see if they have already included a fix. We can incorporate it here if so.