Hello everyone,
I installed Fedora 42 Workstation using the ISO file on my Honor MagicBook 14 Pro. Currently experiencing these issues:
• Touchpad not working
• Bluetooth functional
• WiFi unavailable (no wireless option shown in settings)
• System hangs on boot screen during shutdown/restart
Note: Windows 11 is also installed on this machine, where all hardware works normally.
I’ve run the following commands in Fedora terminal - outputs may help diagnose the problem:
input: lspci -nnk | grep -iA3 network
output: 00:14.3 Network controller [0280]: Intel Corporation Device [8086:7740]
Subsystem: Intel Corporation Device [8086:0074]
Kernel modules: iwlwifi
00:15.0 Serial bus controller [0c80]: Intel Corporation Arrow Lake-H [Serial IOI2C Host Controller] [8086:7778]
input: lspci | grep -i touchpad
no output
input: lspci | grep -i audio
no output
I get many ACPI/BIOS errors. I assume that the touchpad and touchscreen is not detected because of broken ACPI tables.
No i2c devices are detected.
I read about how to decompile the DSDT table. I have little hope that I’m able to fix that. A fixed Bios would be better. Does anybody know how to reach out to Honor?
[edit] I added a acpi dump to the debug files below
Driver is loaded but it seems it has no functionality.
As I understand it provides access to keyboard backlight and power management?
Link to an active repo I found
Fingerprint reader
Device detected but ID is unknown. There are drivers from Levovo for FPC fingerprint reader, but for different devices.
[ 2.301501] usb 3-6: New USB device found, idVendor=10a5, idProduct=9924, bcdDevice= 1.51
[ 2.301504] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.301506] usb 3-6: Product: FPC L:2407 FW:3334151
[ 2.301507] usb 3-6: Manufacturer: FPC
Thanks for your attempts. But I’m really sorry, bro. I don’t know much about this. Judging from the attempts you’ve made, could the main reason that Fedora 42 can’t be installed on my laptop be the BIOS restrictions imposed by Honor? The BIOS just update today, but I’m not sure what effect it has. I haven’t tried the installation again yet, because there’s a possibility that I won’t be able to exit the installation properly and will have to force shut down my computer by cutting the power.
The laptop is so new that Fedora 42 will not work flawless anyway, I think. I had graphics artifacts and crashes. At least it will not work without updated kernel and graphics drivers.
But Fedora 43 would work if the Touchpad would be recognized. I used it a bit and had no crashes. Wifi was very slow though.
The problem with the BIOS are not restrictions but bad information (ACPI tables) provided by the BIOS.
(if my a conclusion is correct)
In principle one could fix the BIOS ACPI tables and the fixed tables can be used to boot Linux. But fixing the tables is beyond my knowledge. Someone more experienced might do that.
The best way would be that Honor fixes the BIOS.
It could still be possible that the touchpad will not work with a fixed BIOS because of a missing driver. But I assume it will work because it seems to be a i2c device which is very common as I understand.
I hope that someone with more knowledge than me can use the provided information.
march7thdev
(EvernightFedora(Evernight Vista Developer))
7
Hello. I also tried to install Arch, but it also failed. Are you also using Honor magicbook 14 pro? Perhaps I could call the Honor customer service to report the issue, but it’s not guaranteed to be effective.
No news yet. I didn’t worked on it the last weeks and hoped for a new Bios.
I just wrote to uk.support@honor.com. Maybe you could do the same?!
I don’t expect much, but who knows?
The keyboard is working (but no special keys) with the boot parameter described above:
i8042.dumbkbd=1
I didn’t try Arch, but a few other distros. All failed to install. Except Fedora 43. I think it’s because of the newer kernel. Even with Fedora 43 I had graphics glitches at first which were resolved later with an update.
I don’t understand. Why would that help?
F43 ist the only distribution I tested that installs and works (mostly) - because of the newest kernel, I think.
Yes, Arch on MagicBook 14 pro (intel i9 version), no internal keyboard no matter which options I set. I tried to finetune i8042 options with dumbkbd, nopnp, reset, nomux, etc… I all tried them, it doesn’t work on latest arch iso (kernel 6.15.x)
I tried fedora 42 with the options sent by Rene and it doesn’t work (I’m using ventoy to boot all my isos) and it doesn’t work either.
I tried to disable acpi and try to play with others options (acpi_osi) but nothing works, I’m in a dead end
From my understanding, the ACPI table is fucked up in this computer (for the god sake, why can’t we just have something basic and straightforward ?) and for an unknown reason, there is an overlap on IRQs between i8042 and huawei_wmi (or some other components).
I noticed if you blacklist or rmmod huawei_wmi, we lost the console shell, even the external keybord on usb is lost
My last chance is to rebuild an arch iso and build a kernel from linux-mainline, maybe something has been updated in early versions.
I also noticed there is no bug reports on kernel bugzilla, I will check again and open an issue to see if something could be done/.
Finally I contacted Honor France for another subject and they didn’t seem to be very responsive…
Sounds like you have a way better understanding on what’s going on than me
Would be great if you could open a kernel bug report! Please post the link here.
I just spend endless hours to try to understand what is going on and reading some past discussions related to this issue. The more I look, the more it tends to be this kind of issue.
Kernel 6.16.x works better sounds good for us, it seems that something has changed between 6.15.x et 6.16.x for our lovely machine
Next step for me : I rebuild an arch iso with 6.15.7, I will check if it works. If not, I will install my system with an external keyboard and try linux-mainline aka 6.16.x however it took several hours to build, probably could be faster using modprobe-db to autodetect modules currently used but if we have a detection issue on our machine it will probably ignore something useful.
These are updated iso images, a snapshot of the day. They boot a newer kernel (6.15.x) and use packages that were available in updates repository at the time the ISO images were created.
Quite often fixes are backported from mainline kernel to stable kernel.
I finally succeeded to install Archlinux on my Honor MagicBook 14 pro and as @rfritzzz reported, unless if you set “i8042.dumbkbd=1 snd-intel-dspcfg.dsp_driver=1” (I removed pci.nocrs as it didn’t change anything on my side) you won’t have your system booting…
So it’s seems to be related to a bad ACPI table causing a routing error within the IRQs and prevent booting or weird behavior.
I just spend endless hours to try to understand what is going on and reading some past discussions related to this issue. The more I look, the more it tends to be this kind of issue.