-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Matebook X Pro 2020 #39
Comments
What desktop environment are you using? You gotta use a modern DE i.e. GNOME, KDE, etc for the mic mute to work, or you have to handle the keyboard event yourself in your DE of choice.
This has to be part of systems hwdb tables, see 99-Huawei.hwdb, notice
Please try https://github.com/aymanbagabas/Huawei-WMI/tree/feat/kbdlight and report back your findings. |
Also, please provide the output of |
As requested here the dmidecode from a Matebook x Pro 2020 with Ubuntu 20.10 installed. Disabled Nvidia completely because battery life still sucks hard... |
Sorry i don't have the notebook anymore so can't test or provide any further information. I couldn't handle the fan starting and stopping all the time (i think the fluctuating cpu temperature readings caused this) even on light tasks where i don't have problems with my 2018 model. |
Could you please upload an |
Sure. |
@Shadesh @bernimoses From what I understand, the only issue is the keyboard backlight. If so, please hop on to issue #38, and if you could please try https://github.com/aymanbagabas/Huawei-WMI/tree/feat/kbdlight. Feel free to close this ticket. |
I just got the Matebook X Pro 2020 (MACHC-WAX9) and tested the following with the 5.8.2 kernel:
/sys/devices/platform/huawei-wmi/leds/platform::micmute/brightness
(0, 1) but it doesn't change if i press the mute button (F7)/sys/class/power_supply/BAT0/charge_control_{start,end}_threshold
and read through/sys/devices/platform/huawei-wmi/charge_control_thresholds
after setting it in Linux or Windows (not 100% sure if it really works)/sys/devices/platform/huawei-wmi/fn_lock_state
(0, 1)Did i miss something or should i test something else?
One other thing i noticed: Pressing
Fn
outputsin dmesg. Is this related?
Boot dmesg snippet (not sure if some of the bold parts are related):
The text was updated successfully, but these errors were encountered: