Skip to content
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

Doesn't seem to work on Arch #9

Open
lunaneff opened this issue Jun 28, 2020 · 5 comments
Open

Doesn't seem to work on Arch #9

lunaneff opened this issue Jun 28, 2020 · 5 comments

Comments

@lunaneff
Copy link

lunaneff commented Jun 28, 2020

I'm on Linux 5.7.6-arch1-1. I've done almost nothing after installing (just installed GNOME and asus-wmi-screenpad). My laptop's model number is UX481FLY (reported by MyASUS on Windows, the package says UX481FL-HJ086R. If you need more info, just ask

@CampGareth
Copy link

CampGareth commented Jul 29, 2020

Same boat here on Manjaro (Arch based) so I installed acpi_call for my kernel version and then used the raw ACPI calls from this comment which asus-wmi-screenpad is based on: s-light/ASUS-ZenBook-Pro-Duo-UX581GV#1 (comment)

Now there's a couple of bash scripts on my machine like this:

#!/bin/bash

echo '\_SB.ATKD.WMNB 0x0 0x53564544 b32000500FF000000' | sudo tee /proc/acpi/call

Not quite as convenient but it'll do for now.

@Plippo
Copy link
Owner

Plippo commented Jul 29, 2020

@laurinneff I'm really sorry I didn't answer earlier, I didn't log into Github for some weeks and somehow missed the email notification about the creation of this bug... Did you (or @CampGareth) get any error messages while trying to install the module or did it just silently fail?

@CampGareth
Copy link

CampGareth commented Jul 29, 2020

No obvious errors on build, I'll include my logs here:
debugging-asus-wmi-screenpad.txt
Running lsmod | grep "asus" pre and post install and reboot gives exactly the same results:

$ lsmod | grep "asus"
asus_nb_wmi            28672  0
asus_wmi               40960  1 asus_nb_wmi
sparse_keymap          16384  1 asus_wmi
rfkill                 28672  10 asus_wmi,bluetooth,cfg80211
battery                20480  1 asus_wmi
wmi                    36864  3 asus_wmi,wmi_bmof,mxm_wmi
i8042                  32768  1 asus_nb_wmi

I'm guessing it's a naming clash? Two asus_wmi modules?

modinfo on asus_wmi and asus_nb_wmi suggests they're official modules made by Corentin Chary and Yong Wang.

@Plippo
Copy link
Owner

Plippo commented Aug 12, 2020

I don't see anything suspicious in the logs either. Maybe the original asus_* modules are already compiled into your kernel and thus can't be replaced by the modified versions? It's normal that both asus_wmi and asus_nb_wmi are active, those control different parts of the device.
Are you able to map the keys above the touchpad, to the left of the on/off key? Those are also provided by the modified modules.

@TRPB
Copy link

TRPB commented Jul 2, 2021

I can report the same thing, it appears in /sys/class/leds but the brightness is reported as 0 even though the screen is on (50% I'd guess from looking at it) and changing the brightness has no effect.

Thank you for your work anyway, it led me here and the acpi_call method above which works fine. I wish I'd discovered it before I spent an hour looking through xrandr, ddcutil and perusing /sys/class/backlight.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants