Good morning, maeschba

Does `amd_iommu=off` in kernel parameters mitigate this issue? It should let the device sleep and come back from sleep, it might also help with the fan always on
We will look into the ACPI tables issue, as fixing it might make us not depend on `amd_iommu=off` as it disables IOMMU as a whole

If you do need IOMMU for your system (eg, PCIe passthrough for VMs), you'll have to not use the `amd_iommu` kernel parameter

Regards,

Good morning, Samanta

No, unfortunately it does not. First try, it went just back to the login screen. On second attempt, the system went black and I had to power down the laptop with the power key. There is a bigger problem than just the sleep behavior.

boot.conf:

title   Arch Linux (linux) 
linux   /vmlinuz-linux 
initrd  /amd-ucode.img 
initrd  /initramfs-linux.img 
options cryptdevice=UUID=fde6b5b8-2284-4003-87fb-73226a366524:cryptlvm root=/dev/ArchinstallVg/root zswap.enabled=0 rootflag
s=subvol=@ rw rootfstype=btrfs amdgpu.dcdebugmask=0x10 amd_iommu=off

The BIOS is causing kernel memory corruption:

Here my kernel errors:

Jan 11 22:03:39 archlinux kernel: ACPI BIOS Error (bug): Could not resolve symbol [^^PCI0.GP17.VGA.AFN4], AE_NOT_FOUND (20250807/psargs-332)
Jan 11 22:03:39 archlinux kernel: ACPI Error: Aborting method \_SB.ADP1._PSR due to previous error (AE_NOT_FOUND) (20250807/psparse-529)
Jan 11 22:03:39 archlinux systemd[1]: systemd-rfkill.socket: Socket service systemd-rfkill.service not loaded, refusing.
Jan 11 22:03:39 archlinux systemd[1]: Failed to listen on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Jan 11 22:03:39 archlinux kernel: platform acp_asoc_acp70.0: warning: No matching ASoC machine driver found
Jan 11 22:03:40 archlinux bootctl[1123]:  Mount point '/boot' which backs the random seed file is world accessible, which is a security hole! 
Jan 11 22:03:40 archlinux bootctl[1123]: Random seed file '/boot/loader/random-seed' is world accessible, which is a security hole!
Jan 11 22:03:42 archlinux systemd[1]: systemd-rfkill.socket: Socket service systemd-rfkill.service not loaded, refusing.
Jan 11 22:03:42 archlinux systemd[1]: Failed to listen on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Jan 11 22:03:42 archlinux kwin_wayland[1535]: Libinput: event6  - HTIX5288:00 36B6:C001 Touchpad: kernel bug: clickpad advertising right button. See https://wayland.freedesktop.org/libinput/doc/1.30.1/clickpad-with-right-button.html for details
Jan 11 22:19:19 archlinux kwin_wayland[1535]: Libinput: event6  - HTIX5288:00 36B6:C001 Touchpad: kernel bug: Touch jump detected and discarded.
                                              See https://wayland.freedesktop.org/libinput/doc/1.30.1/touchpad-jumping-cursors.html for details
Jan 11 22:47:08 archlinux kernel: BUG: Bad page map in process TaskCon~ller #0  pte:8000200210688867
Jan 11 22:47:08 archlinux kernel: pgd:22d8f3067 p4d:22d8f3067 pud:10ea6e067 pmd:196b64067
Jan 11 22:47:08 archlinux kernel: addr:000008f76221a000 vm_flags:08100073 anon_vma:ffff8f1b05940ea0 mapping:0000000000000000 index:8f76221a
Jan 11 22:47:08 archlinux kernel: file:(null) fault:0x0 mmap:0x0 mmap_prepare: 0x0 read_folio:0x0
Jan 11 22:47:08 archlinux kernel: BUG: Bad page map in process TaskCon~ller #0  pte:800020023e29a867
Jan 11 22:47:08 archlinux kernel: pgd:22d8f3067 p4d:22d8f3067 pud:10ea6e067 pmd:196b64067
Jan 11 22:47:08 archlinux kernel: addr:000008f76221f000 vm_flags:08100073 anon_vma:ffff8f1b05940ea0 mapping:0000000000000000 index:8f76221f
Jan 11 22:47:08 archlinux kernel: file:(null) fault:0x0 mmap:0x0 mmap_prepare: 0x0 read_folio:0x0
Jan 11 22:47:12 archlinux systemd-coredump[6343]: Process 6128 (Isolated Web Co) of user 1000 dumped core.
                                                  
                                                  Stack trace of thread 1898:
                                                  #0  0x00007f13f0b2dafb n/a (/app/lib/firefox/libxul.so + 0x452dafb)
                                                  ELF object binary architecture: AMD x86-64
Jan 11 22:47:12 archlinux kernel: BUG: Bad page map in process IPC I/O Child  pte:8000200210688867
Jan 11 22:47:12 archlinux kernel: pgd:22d8f3067 p4d:22d8f3067 pud:10ea6e067 pmd:196b64067
Jan 11 22:47:12 archlinux kernel: addr:000008f76221a000 vm_flags:08100073 anon_vma:ffff8f1b05940ea0 mapping:0000000000000000 index:8f76221a
Jan 11 22:47:12 archlinux kernel: file:(null) fault:0x0 mmap:0x0 mmap_prepare: 0x0 read_folio:0x0
Jan 11 22:47:12 archlinux kernel: BUG: Bad page map in process IPC I/O Child  pte:800020023e29a867
Jan 11 22:47:12 archlinux kernel: pgd:22d8f3067 p4d:22d8f3067 pud:10ea6e067 pmd:196b64067
Jan 11 22:47:12 archlinux kernel: addr:000008f76221f000 vm_flags:08100073 anon_vma:ffff8f1b05940ea0 mapping:0000000000000000 index:8f76221f
Jan 11 22:47:12 archlinux kernel: file:(null) fault:0x0 mmap:0x0 mmap_prepare: 0x0 read_folio:0x0
Jan 11 22:47:12 archlinux kernel: BUG: Bad rss-counter state mm:000000000242997c type:MM_ANONPAGES val:2 Comm:systemd Pid:6377
Jan 11 22:55:47 archlinux systemd[1]: systemd-rfkill.socket: Socket service systemd-rfkill.service not loaded, refusing.
Jan 11 22:55:47 archlinux systemd[1]: Failed to listen on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Jan 11 22:55:48 archlinux systemd[1]: systemd-rfkill.socket: Socket service systemd-rfkill.service not loaded, refusing.
Jan 11 22:55:48 archlinux systemd[1]: Failed to listen on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Jan 11 22:55:53 archlinux systemd[1]: systemd-rfkill.socket: Socket service systemd-rfkill.service not loaded, refusing.
Jan 11 22:55:53 archlinux systemd[1]: Failed to listen on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Jan 11 22:55:53 archlinux systemd[1]: systemd-rfkill.socket: Socket service systemd-rfkill.service not loaded, refusing.
Jan 11 22:55:53 archlinux systemd[1]: Failed to listen on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Jan 11 22:56:02 archlinux systemd[1]: systemd-rfkill.socket: Socket service systemd-rfkill.service not loaded, refusing.
Jan 11 22:56:02 archlinux systemd[1]: Failed to listen on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Jan 11 22:56:02 archlinux systemd[1]: systemd-rfkill.socket: Socket service systemd-rfkill.service not loaded, refusing.
Jan 11 22:56:02 archlinux systemd[1]: Failed to listen on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Jan 11 22:56:04 archlinux systemd[1]: systemd-rfkill.socket: Socket service systemd-rfkill.service not loaded, refusing.
Jan 11 22:56:04 archlinux systemd[1]: Failed to listen on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Jan 11 22:56:05 archlinux systemd[1]: systemd-rfkill.socket: Socket service systemd-rfkill.service not loaded, refusing.
Jan 11 22:56:05 archlinux systemd[1]: Failed to listen on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Jan 11 22:56:07 archlinux systemd[1]: systemd-rfkill.socket: Socket service systemd-rfkill.service not loaded, refusing.
Jan 11 22:56:07 archlinux systemd[1]: Failed to listen on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Jan 11 22:56:09 archlinux systemd[1]: Failed to listen on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Jan 11 22:56:14 archlinux systemd[1]: systemd-rfkill.socket: Socket service systemd-rfkill.service not loaded, refusing.
Jan 11 22:56:14 archlinux systemd[1]: Failed to listen on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Jan 11 22:56:22 archlinux systemd[1]: systemd-rfkill.socket: Socket service systemd-rfkill.service not loaded, refusing.
Jan 11 22:56:22 archlinux systemd[1]: Failed to listen on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Jan 11 22:56:23 archlinux systemd[1]: systemd-rfkill.socket: Socket service systemd-rfkill.service not loaded, refusing.
Jan 11 22:56:23 archlinux systemd[1]: Failed to listen on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Jan 11 22:56:28 archlinux systemd[1]: systemd-rfkill.socket: Socket service systemd-rfkill.service not loaded, refusing.
Jan 11 22:56:28 archlinux systemd[1]: Failed to listen on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Jan 11 22:56:28 archlinux systemd[1]: systemd-rfkill.socket: Socket service systemd-rfkill.service not loaded, refusing.
Jan 11 22:56:28 archlinux systemd[1]: Failed to listen on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Jan 11 22:56:29 archlinux systemd[1]: systemd-rfkill.socket: Socket service systemd-rfkill.service not loaded, refusing.
Jan 11 22:56:29 archlinux systemd[1]: Failed to listen on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Jan 11 22:56:30 archlinux systemd[1]: systemd-rfkill.socket: Socket service systemd-rfkill.service not loaded, refusing.
Jan 11 22:56:30 archlinux systemd[1]: Failed to listen on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Jan 11 22:56:32 archlinux systemd[1]: systemd-rfkill.socket: Socket service systemd-rfkill.service not loaded, refusing.
Jan 11 22:56:32 archlinux systemd[1]: Failed to listen on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Jan 11 22:56:42 archlinux kernel: BUG: unable to handle page fault for address: 0000010000000000
Jan 11 22:56:42 archlinux kernel: #PF: supervisor read access in kernel mode
Jan 11 22:56:42 archlinux kernel: #PF: error_code(0x0000) - not-present page
Jan 11 22:56:42 archlinux kernel: Fixing recursive fault but reboot is needed!
Jan 11 22:56:42 archlinux kernel: BUG: scheduling while atomic: TaskCon~ller #6/5360/0x00000000
Jan 11 22:56:42 archlinux kernel: BUG: Bad page map in process HTML5 Parser  pte:80018a1e5025
Jan 11 22:56:42 archlinux kernel: pgd:1cb486067 p4d:1cb486067 pud:1cb485067 pmd:196b75067
Jan 11 22:56:42 archlinux kernel: addr:00007f13f1488000 vm_flags:08000075 anon_vma:0000000000000000 mapping:ffff8f1acb88a300 index:4e87
Jan 11 22:56:42 archlinux kernel: file:libxul.so fault:filemap_fault mmap:0x0 mmap_prepare: btrfs_file_mmap_prepare read_folio:btrfs_read_folio
Jan 11 22:56:42 archlinux kernel: BUG: Bad page map in process HTML5 Parser  pte:4018a1ea825
Jan 11 22:56:42 archlinux kernel: pgd:1cb486067 p4d:1cb486067 pud:1cb485067 pmd:196b75067
Jan 11 22:56:42 archlinux kernel: addr:00007f13f148d000 vm_flags:08000075 anon_vma:0000000000000000 mapping:ffff8f1acb88a300 index:4e8c
Jan 11 22:56:42 archlinux kernel: file:libxul.so fault:filemap_fault mmap:0x0 mmap_prepare: btrfs_file_mmap_prepare read_folio:btrfs_read_folio
Jan 11 23:00:34 archlinux (udev-worker)[7702]: BAT0: Spawned process '/usr/bin/tlp auto' [7703] timed out after 2min 59s, killing.
Jan 11 23:00:34 archlinux (udev-worker)[7702]: BAT0: Process '/usr/bin/tlp auto' terminated by signal KILL.
Jan 11 23:00:34 archlinux (udev-worker)[7702]: BAT0: Failed to wait for spawned command '/usr/bin/tlp auto': Input/output error
Jan 11 23:00:42 archlinux dbus-broker-launch[1144]: Activation request for 'org.freedesktop.nm_dispatcher' failed.

I masked the systemd-rfkill.socket service in the meantime.

Regards, Michael

The above kernel errors were after the system froze while using Firefox. Now just after booting and trying to put the laptop into sleep:

Jan 12 09:19:32 archlinux kernel: ACPI BIOS Error (bug): Could not resolve symbol [^^PCI0.GP17.VGA.AFN4], AE_NOT_FOUND (202>
Jan 12 09:19:32 archlinux kernel: ACPI Error: Aborting method \_SB.ADP1._PSR due to previous error (AE_NOT_FOUND) (20250807>
Jan 12 09:19:32 archlinux kernel: platform acp_asoc_acp70.0: warning: No matching ASoC machine driver found
Jan 12 09:19:33 archlinux bootctl[1097]:  Mount point '/boot' which backs the random seed file is world accessible, which i>
Jan 12 09:19:33 archlinux bootctl[1097]: Random seed file '/boot/loader/random-seed' is world accessible, which is a securi>
Jan 12 09:19:35 archlinux kwin_wayland[1486]: Libinput: event6  - HTIX5288:00 36B6:C001 Touchpad: kernel bug: clickpad adve>
Jan 12 09:21:47 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: VPE queue reset failed
Jan 12 09:21:47 archlinux kernel: amdgpu 0000:03:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test failed on vpe (->
Jan 12 09:21:47 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: ib ring test failed (-110).

I should probably stay in the console (tty) and avoid touching the touchpad until the BIOS is fixed. In the first place, I was in console mode when I realized that the fan was spinning while the temperature of the CPU is under 30°C. Judging form the translation error in the BIOS (Performmance [sic] mode) and the small number of options, the BIOS seems to be the culprit.

• HTIX5288:00 36B6:C001 Touchpad: kernel bug

• System freezes often start with touchpad interaction

• Memory corruption follows touchpad errors

This laptop needs a serious BIOS/ACPI fix.

Framework ships the same CPU family with working Linux support. What's your timeline for fixing the ACPI tables?

Hello,
This is the first time that we have been notified that the touchpad causes freezes in this laptop.
As Arch is a bleeding edge distro, it might be a kernel issue, if you could try using an LTSC kernel or a Live CD with another kernel that isn't 6.18 to see if the touchpad errors still occur

For what is worth, this laptop needs 0x610 for amdgpu.dcdebugmask, as that disables all PSR technology which we know has caused issues with AMD laptops, so you can also try that for the freezes

Regardless anything, we are still investigating the ACPI errors mentioned here

Regards,

I tested suspend also on Slimbook OS r13 live USB (kernel 6.14.0-1019-oem with your default parameters). Suspend fails:

• Screen goes black

• Fans continue spinning

• Keyboard backlight stays and toggles

• System does not enter S3/suspend

• Cannot wake - requires hard power off.

Please provide a timeline for a BIOS fix. In its current state, the product is not fit for purpose.

Good morning,

Default kernel parameters of the live CD of Slimbook OS do not provide `amd_iommu=off`, only `amdgpu.dcdebugmask=0x610`
You would need to edit the entry and add the amd_iommu parameter

Regards,

The fact that amd_iommu=off is needed means your ACPI tables are broken. This is a firmware bug, not a configuration issue.

Questions:

When will you release a BIOS update that fixes the ACPI errors so these workarounds are not needed?

Other customers are reporting similar issues. What is your plan to address this systematically?

I've documented kernel memory corruption (BUG: Bad page map), failed suspend, broken power detection (_PSR), and missing GPU ACPI methods (VGA.AFN4). These are firmware defects. Kernel parameters are workarounds, not solutions.

By disabling the touchpad, not using any kind of suspend, and ignoring the fan running constantly, I can work more or less without system freezes. As far as I understand, the KDE Slimbook VII's current issues are:

• Power source detection broken (_PSR method fails)

• GPU ACPI methods missing (VGA.AFN4 unresolved)

• Fan control not exposed (EC-controlled only, no hwmon fan sensors, no ACPI binding)

• Touchpad errors (I2C relies on ACPI) - kernel bug: clickpad advertising right button

• Memory corruption (BUG: Bad page map, Fixing recursive fault) - historically observed, but less with workarounds* applied

• System freezes (cascade from above issues)

• S3 suspend broken (screen blacks out, fans spin, keyboard backlit, doesn't actually suspend)

* using Arch's linux-lts kernel most of the time, with kernel parameters amd_iommu=off and amdgpu.dcdebugmask=0x610, as well as kernel module i2c_hid_acpi blacklisted

Hello all 

I have the exact same model (Silver Excalibur with AMD 7840HS & 780M) with same symptoms and problems..

Samanta

"For what is worth, this laptop needs 0x610 for amdgpu.dcdebugmask, as that disables all PSR technology which we know has caused issues with AMD laptops, so you can also try that for the freezes"

when you disable PSR technology, battery drain goes sky high.I can't work more than 2 hours (at best) without plugging...

Please FIX it....

Regards

Theodore

Good afternoon @theodore,
Your model is not the same as KDE VII, your model uses an older CPU and GPU and is the KDE V model

I recommend contacting support, as this is not the same issue or at least not from the same model

Our support team will help you

https://slimbook.com/en/support

Regards,

Hello, 

I have exactly the same issue.  My laptop is a SLIMBOOK EVO with arch-linux. This is what happened: 

• [01/01/2026] System update. 

• [29/01/2026] My computer stopped suspending on lid close. No updates between 01/01 and 29/01 

• [30/01/2026] System update. My computer did not suspend on lid close either

• [30/01/2026] Inspection of the problem: 
     1. My computer does not suspend at all. Even if I force it: 
  

        $  systemctl suspend

     2. It does not hibernate either. 
     3. Under suspension, the service system-logind says: 
  

          Jan 31 09:29:15 cubo systemd-logind[613]: Lid closed.
          Jan 31 09:29:15 cubo systemd-logind[613]: Suspending...
          Jan 31 09:29:17 cubo systemd-logind[613]: Operation 'suspend' finished.

         It "finishes"  with no reason after 2 seconds. Every 30 seconds, the machine tries to suspend again with no success. 
  dmesg says: 
  

  [ 1077.593879] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.ACDC.RTAC], AE_NOT_FOUND (20250807/psargs-332)
  [ 1077.593888] ACPI Error: Aborting method \_SB.PEP._DSM due to previous error (AE_NOT_FOUND) (20250807/psparse-529)
  [ 1077.594336] ACPI: EC: interrupt unblocked

     4. I went to the BIOS, but it is 100% non-responsive, neither via keyboard not via mouse. I get to the screen (it takes a long time) but there is nothing I can do on it.  GRUB is reesponsive but it takes a second per keystroke at least. 
     5. These are the kernel messages: 
  

  Jan 31 09:11:22 cubo kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP6.WLAN._DSM], AE_ALREADY_EXISTS (20250807/dswload2-326)
  Jan 31 09:11:22 cubo kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20250807/psobject-220)
  Jan 31 09:11:22 cubo kernel: ACPI: Skipping parse of AML opcode: Method (0x0014)
  Jan 31 09:11:22 cubo kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP6._S0W], AE_ALREADY_EXISTS (20250807/dswload2-326)
  Jan 31 09:11:22 cubo kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20250807/psobject-220)
  Jan 31 09:11:22 cubo kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP6._PRW], AE_ALREADY_EXISTS (20250807/dswload2-326)
  Jan 31 09:11:22 cubo kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20250807/psobject-220)
  Jan 31 09:11:22 cubo kernel: ACPI: Skipping parse of AML opcode: Method (0x0014)
  Jan 31 09:11:22 cubo kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP6.WLAN._S0W], AE_ALREADY_EXISTS (20250807/dswload2-326)
  Jan 31 09:11:22 cubo kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20250807/psobject-220)

  
        

Good morning all 

@Samanta I forgot to write that I was referring to the BIOS version NOT the laptop model. I know it's different laptop. 

@maeschba I don't know if it's possible for you but because of all these troubles with sudden reboots or sudden freezes I re-formated my laptop and installed CachyOS with Hyprland. Before that, I was always using KDE with either Arch or Fedora and some time openSuSE Tumbleweed.

After switching to Hyprland and using "amd_iommu=off dmgpu.dcdebugmask=0x610" in grub file, I HAVEN'T ANY CRASH and/or REBOOT.

I don't know if it's relevant or not, luck or not, but these factors permitted me to use laptop without the problems I mentioned. I also use extensively QEMU/KVM machines also WITHOUT problems.

Of course I know it might not be possible for others to do what I did, but I thought to write it down just in case :)

Theodore

Hi Theodore

With Hyprland, you're probably using mostly keyboard. I had similar success with Sway (no freezes). My crashes involved Firefox + touchpad interaction. After disabling the touchpad in KDE (mouse only), I had just one freeze. Now I've blacklisted i2c_hid_acpi entirely - even accidental touches should be safe. Thanks for confirming CachyOS/Hyprland works. Hoping for a BIOS fix soon - workarounds on a "Linux laptop" defeat the purpose. What browser do you use?

Regards, Michael

Hello Michael

To be honest, I "hate" using touchpad. I prefer and try to use mouse :)

Yes, Hyprland is MOSTLY keyboard but mouse actually helps. I was using Vivaldi, but lately tried Floorp first but settled with Zen browser. Both are Firefox derivatives. 

Theodore

Hi everybody, 

if I let the battery drain completely until the computer shuts down, then, 

1. BIOS works as expected, 

2. Suspend works. 
   

However, the kernel error persists, and today it was working properly for some hours until it broke again. 

Paula

Hello Paula,

Is this for the KDE Slimbook VII (Ryzen AI 300)? Draining the battery resets the EC (Embedded Controller). What specifically "broke again" and what do you mean be BIOS works as expected? 

If you run dmesg on your system, does it also show an error message like this?

Jan 11 22:03:39 archlinux kernel: ACPI BIOS Error (bug): Could not resolve symbol [^^PCI0.GP17.VGA.AFN4], AE_NOT_FOUND (20250807/psargs-332)
Jan 11 22:03:39 archlinux kernel: ACPI Error: Aborting method \_SB.ADP1._PSR due to previous error (AE_NOT_FOUND) (20250807/psparse-529)

Good morning @Paula,
Since I see that your Arch Linux installation was installed by yourself, I ask you if you installed our meta-packages for kernel parameters (specifically, the acpi no wakeup one! to make it able to suspend)
The EC from your EVO might send sporadic wakeup signals that might prevent the laptop sleep. As the wakeup signals are random,  that is why you probably got to suspend your laptop correctly last time you mentioned it

As for the "non-responsive" BIOS settings, to rule out any misunderstandings, Bluetooth and 2.4 Ghz dongles will not work on BIOS,  so you must use either USB or the built-in devices (not saying you used Bluetooth or 2.4Ghz, but do not want to assume things)

As for the ACPI errors of your EVO, we understand it is a BIOS error, and until we fix it, the kernel parameter mitigates it. 

The EVO BIOS and EC and the EXCALIBUR/KDE VII uses both different BIOS and EC, so their problems are different and they must be treated in isolation, a fix that could work for EXCALIBUR/KDE VII does not have to work for the EVO series

Regards

After extensive debugging of ACPI firmware crashes (touchpad freezes, system hangs, memory corruption), I'm switching this Slimbook VII to Windows 11 Pro with Arch in WSL2. The ODM chassis firmware appears optimized for Windows and remains unstable under Linux despite vendor support engagement. A recent failed boot after an update was the final confirmation that this hardware isn't production-ready for native Linux.

One week later, with Arch in WSL2 and very little use of the system due to constantly running fans (audibly spinning even at idle), I examined the BIOS and Windows 11 with 3rd-party tools. The Device Manager shows a Microsoft ACPI-Compliant Embedded Controller working properly, but the EC firmware itself is incomplete/defective. Windows just hides the problem better by not exposing errors, but the functionality is equally missing. Even under Windows 11 with ODM-targeted firmware, the EC does not expose any hardware monitoring data - the fans cannot be monitored or controlled.

BIOS: InsydeH20 0.13 (KPT-W042-FP8-0SLI)
OS: Windows 11 Professional Build 26200.7840

HWiNFO64 v8.40-5900 Report Analysis:
- EC device present in Device Manager (working properly)
- Zero EC sensor data exposed
- No fan speed monitoring available
- No motherboard thermal sensors accessible

Conclusion: EC firmware fundamentally broken for hardware monitoring,
independent of operating system. LibreHardwareMonitor and HWiNFO64
both fail to access sensor data. This is ODM firmware failure.

I'm hoping this cross-platform validation helps isolate the firmware issue for your ODM escalation. What's the timeline for a BIOS update addressing the EC sensor interface?