You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before I managed to get the asus-wmi-screenpad-dkms module installed, I got acpi_call-dkms installed from pamac. Turns out the ACPI calls that need to be made are super simple...
In Manjaro 22's Linux 5.15 echo '\_SB.ATKD.WMNB 0x0 0x53564544 b3200050069000000' | sudo tee /proc/acpi/call sets the brightness to 0x69.
So what's the benefit of using yay -S asus-wmi-screenpad-dkms-git instead?
Update: I had to update to 5.19 and it's been SOOOO much better. No crashes, vs 10 crashes a day and GPU/sleep bugs with 5.15. I installed linux519-acpi_call and started doing calls manually... still don't know the call for turning off the display.
The text was updated successfully, but these errors were encountered:
asus-wmi-screenpad also makes it possible to use the extra keys like MyASUS (//]), toggle screenpad on/off, or the key to swap windows between screens. I could probably make it work with acpi_call relatively easily, but some functionality will be missing.
And BTW, for turning off the display, I'm pretty sure you just have to set the brightness to 0, so echo '\_SB.ATKD.WMNB 0x0 0x53564544 b3200050000000000' | sudo tee /proc/acpi/call
Before I managed to get the asus-wmi-screenpad-dkms module installed, I got acpi_call-dkms installed from pamac. Turns out the ACPI calls that need to be made are super simple...
In Manjaro 22's Linux 5.15
echo '\_SB.ATKD.WMNB 0x0 0x53564544 b3200050069000000' | sudo tee /proc/acpi/call
sets the brightness to 0x69.So what's the benefit of using
yay -S asus-wmi-screenpad-dkms-git
instead?Apparently it will break in Linux 5.18... hooray Plippo/asus-wmi-screenpad#39
Update: I had to update to 5.19 and it's been SOOOO much better. No crashes, vs 10 crashes a day and GPU/sleep bugs with 5.15. I installed linux519-acpi_call and started doing calls manually... still don't know the call for turning off the display.
The text was updated successfully, but these errors were encountered: