-
-
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
v 3.1 not working on MateBook 13 #14
Comments
Hmm.. that's strange. Does it register the input driver? What's the output of |
Could you try using DKMS from here.
Edit: use |
Ermmm... Maybe. Not sure. How do I check? ;-)
:-D Well, let's try again...
That's better...
And here's where the weird part starts. There is no
However, matebook-applet successfully reads and writes... Oh! Oh! Disregard my previous comment on how batpro levels and fnlock work, they don't! The applet falls back to using scripts, that's what's happening.
Hangs forever on |
Ahhh you got a kernel panic! Can I see you full |
Yep, I looked into it more closely, and it's all shambles with 3.1: sometimes it wouldn't even boot, attempting to kill init, other times it wouldn't reboot correctly, requiring the SysRq REISUB dance (thank heavens for FnLock ;))) No such behaviour with 3.0.
Why not, here you go. |
Signed-off-by: Ayman Bagabas <[email protected]>
Fixed in v3.2 |
Yep, works. Thank you! Keep up the awesome work! |
@aymanbagabas I tried to install 'huawei-wmi/3.2' in three ways (rpm, tar.gz and build from source), but "/sys/devices/platform/huawei-wmi" doesn’t appear :(
Huawei Matebook 13 |
Please open up a new issue and provide more details and provide |
After update to driver v 3.1 additional keys (WiFi switch, micmute, PCmanager) and micmute LED stopped working on MateBook 13. Batpro and fnlock functionality still available.
The text was updated successfully, but these errors were encountered: