dsdt.dat didn’t depend from kernel version.
I get trouble with keyboard when trying different distros. As i remember the problem was absent i8042 module in initramfs image.
On Manjaro, Ubuntu and Arch with kernel 6.17 work well, no any troubles with keyboard
1 Like
Guys, are you able to get fan speed from sensors ? I don’t hear them and I’m wondering if they are actually running…
I had the same fear. lm-sensors does not find any fan, but in /sys/class/thermal are some fans.
for dev in /sys/class/thermal/cooling_device*; do echo “$dev:”; cat “$dev/type”; cat “$dev/cur_state”; echo; done
But you can’t set them.
So I used “stress” to make the machine hot 
and the fans started spinning.
I don’t know if the firmware is doing that or something else.
I ran hw-probe again without any attached devices for reference
Ok I didn’t dare to do a stress test but thank you for your sacrifce 
So that’s good news, this means that the fan speed is controlled by the BIOS, even if we couldn’t change the curve or speed, they are a least doing their job !
I checked the HW probe results, so far so good, everything seems to be well detected….
Except the fingerprint reader, everything is working.
BTW, I noticed on my configuration that the backlight turn up and down itself, I don’t know if it comes from my configuration (yes, indeed, I use Arch btw) or from the latest changes we made. Anyone have the same issue ?
I added a feature request to support the missing Fn HotKeys:
https://github.com/aymanbagabas/Huawei-WMI/issues/107
Feel free to add information or corrections.
I’m still not sure if that driver get’s regulary merged into the kernel.
by the way, I tried to map a key with udev but that doesn’t work
/etc/udev/hwdb.d/90-huawei-hotkeys.hwdb
# Huawei WMI hotkeys – map snapshot key to Print Screen
evdev:input:b0019v0000p0000e0000\*
KEYBOARD_KEY_028e=print
This patch work. I recompile kernel with it and now there is no i8042.dumbkbt=1 needed.
Also I compile latest Huawei WMI and all keys works. In dmesg i see strange messages on some of its:
fmbp kernel: atkbd serio0: Unknown key released (translated set 2, code 0xf8 on isa0060/serio0).
fmbp kernel: atkbd serio0: Use 'setkeycodes e078 <keycode>' to make it known.
Same message on all buttons. This happens on both brightness buttons (F1,F2), touchpad toggle(F3), mic toggle(F7), camera toggle(F8), settings(F10), YOYO(F11) buttons.
Buttons camera toggle(F8), and screenshort(F12) do nothing. All other work as expected.
The patch @fouedz posted? And we don’t know where it came from? Interesting 
I see the same atkbd serio0 messages.
Currently I have a weird behavior. Once in a while the screen brightness is set to 5% and after 10 to 60 sec it goes up to 100%. When that happens the Fn keys for brightness no longer work.
GPT thinks it’s a graphics driver problem. Definitely it came with the latest Fedora 43 update.
Same for me, I think it is related to the keyboard mode using dumbkbd, the driver should receive spurious key press from Huawei-wmi…maybe the patch coming from nowhere fixed it !
Hi everyone, and thank you so much Foued, Rene and Denis, I was able to install fedora on my Magicbook thanks to you ! I also had the same brightness issue, it looks like it’s due to an unknown input device sending brightness control command.
When typing sudo evtest , I can see that I have this device : /dev/input/event5: GXT7863:00 27C6:01E0 UNKNOWN which is responsible for the brightness madness. I just disabled it by creating the file /etc/udev/rules.d/99-ignore-touchscreen.rules in which I put SUBSYSTEM=="input", ATTRS{name}=="GXT7863:00 27C6:01E0 UNKNOWN", RUN+="/bin/sh -c 'echo 1 > /sys$env{DEVPATH}/../inhibited'" (thank you AI).
After restart my brightness control works.
I hope it helps.
1 Like
Nice find!
The GXT7863 is the touchpad.
Why are there 3 devices for the touchpad?:
/dev/input/event3: GXT7863:00 27C6:01E0 Mouse
/dev/input/event4: GXT7863:00 27C6:01E0 Touchpad
/dev/input/event5: GXT7863:00 27C6:01E0 UNKNOWN
And why does that device generate key strokes?:
Event: time 1762261162.695052, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), value 2
Having a Mouse and a Touchpad device makes sense, but what is the third device for?
It could be a false device, but why are keystrokes generated and why do they change from time to time?
I was wondering if it would be a good idea to create a github repo to keep track of the todo’s and workarounds.
The README would be a summary and link list . The issues could be used to discuss single problems (brightness, keyboard, wmi, touchscreen, …). Maybe suboptimal, but it’s also not easy to keep track of this thread for new people.
What do you think?
1 Like
I think that would be great to keep a record of whatever needs to be done to make this laptop work with Linux ! Good idea 
I copy/pasted as much information as I could.
Some details are not clear to me so feel free to add information.
I tried to reference the sources but I also wanted to keep it simple. I hope it’s Ok.
1 Like
Hey @fumierardent (Oh un compatriote Breton !! Sudiste moi mais ça fait toujours plaisir de trouver des français), thank you for your fix, this was driving me crazy.
Did anyone know what is this device ? Huawei-wmi badly detected or some kind of ambient light sensor ?
1 Like
Thank you @rfritzzz for the repository, it will help the lost souls like us 
Thank you so much @rfritzzz !!! @fouedz It was also driving me crazy 
(hélas je ne suis plus en Bretagne, mais compatritore quand même 
)
1 Like
If someone is interested to test a driver for the FPC fingerprint reader, there’s one for an older device. See here for some links
1 Like