Help

¡Bienvenido al foro de la comunidad!

Si tienes problemas de software, este es tu sitio. Construyamos entre todos un lugar mejor, proporcionando experiencias, información de uso y tips. Si tienes alguna pregunta, procura dar información detallada sobre tu sistema.

Si tienes problemas de hardware, tramita la GARANTÍA AQUÍ, ya que nuestros técnicos no suelen revisar el foro por estar trabajando en reparaciones.

2

KDE Slimbook VII ACPI BIOS issue

Avatar
maeschba

BIOS (KPT-W042-FP8_OSLI-013 [Rev 5.0]) appears to have incomplete ACPI tables. The \_SB.ADP1._PSR method fails. The Kernel can't properly query power source state. This results in a fan always spinning and breaks sleep behavior. I updated the BIOS to the latest version on your website. Will this behavior be overridden by the packages in your repository or do I have to wait for an additional BIOS update? I'm running Arch Linux now, but the installed KDE neon showed also strange behavior.


Operating System: Arch Linux
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.21.0
Qt Version: 6.10.1
Kernel Version: 6.18.3-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 20 × AMD Ryzen AI 9 365 w/ Radeon 880M
Memory: 16 GiB of RAM (14.4 GiB usable)
Graphics Processor: AMD Radeon 890M Graphics
Manufacturer: SLIMBOOK
Product Name: EXCALIBUR-AMD-AI

[    0.309660] ACPI BIOS Error (bug): Could not resolve symbol [^^PCI0.GP17.VGA.AFN4], AE_NOT_FOUND (20250807/psargs-332)
[    0.309699] ACPI Error: Aborting method \_SB.ADP1._PSR due to previous error (AE_NOT_FOUND) (20250807/psparse-529)
[    0.309731] ACPI: \_SB_.ADP1: Error reading AC Adapter state: AE_NOT_FOUND
[    0.310476] ACPI: button: Power Button [PWRB]
[    0.310556] ACPI: button: Lid Switch [LID0]
[    0.313494] ACPI: thermal: Thermal Zone [TZ01] (28 C)
[    0.314604] ACPI: battery: Slot [BAT0] (battery present)
[    1.561421] ACPI: bus type drm_connector registered
[    1.763758] ACPI: video: Video Device [VGA] (multi-head: yes  rom: no  post: no)

+++ Battery Status: BAT0
/sys/class/power_supply/BAT0/manufacturer                   = W042-5951
/sys/class/power_supply/BAT0/model_name                     = 3862141
/sys/class/power_supply/BAT0/cycle_count                    =      0 (or not supported)
/sys/class/power_supply/BAT0/energy_full_design             =  83160 [mWh]
/sys/class/power_supply/BAT0/energy_full                    =  83160 [mWh]
/sys/class/power_supply/BAT0/energy_now                     =  70686 [mWh]
/sys/class/power_supply/BAT0/power_now                      =   6957 [mW]
/sys/class/power_supply/BAT0/status                         = Discharging

/sys/class/power_supply/BAT0/charge_control_start_threshold = (not available)
/sys/class/power_supply/BAT0/charge_control_end_threshold   = (not available)
/sys/class/power_supply/BAT0/charge_behaviour               = (not available)
/sys/class/power_supply/BAT0/charge_types                   = (not available)

KDE Slimbook VII (Excalibur)
Avatar
Discard
30 Answers
0
Avatar
maeschba
Best Answer

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,

Avatar
Discard
0
Avatar
maeschba
Best Answer

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:

ACPI BIOS Error: Could not resolve symbol [^^PCI0.GP17.VGA.AFN4]
BUG: Bad page map
Fixing recursive fault but reboot is needed!

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.


Avatar
Discard
0
Avatar
maeschba
Best Answer

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

Regards, Michael


Avatar
Discard
0
Avatar
maeschba
Best Answer

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.

Avatar
Discard
0
Avatar
maeschba
Best Answer
  • 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.

Avatar
Discard
0
Avatar
maeschba
Best Answer

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

Avatar
Discard
0
Avatar
maeschba
Best Answer

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,

Avatar
Discard
0
Avatar
maeschba
Best Answer

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.

Avatar
Discard
0
Avatar
maeschba
Best Answer

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,

Avatar
Discard
0
Avatar
maeschba
Best Answer

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.

Avatar
Discard
0
Avatar
maeschba
Best Answer

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

Avatar
Discard
0
Avatar
maeschba
Best Answer

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

Avatar
Discard
0
Avatar
maeschba
Best Answer

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,

Avatar
Discard
0
Avatar
maeschba
Best Answer

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)


          

Avatar
Discard
0
Avatar
maeschba
Best Answer

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

Avatar
Discard
0
Avatar
maeschba
Best Answer

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

Avatar
Discard
0
Avatar
maeschba
Best Answer

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

Avatar
Discard
0
Avatar
maeschba
Best Answer

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

Avatar
Discard
0
Avatar
maeschba
Best Answer

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)
Avatar
Discard
0
Avatar
maeschba
Best Answer

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

Avatar
Discard
0
Avatar
maeschba
Best Answer

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.

Avatar
Discard
0
Avatar
maeschba
Best Answer

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?

Avatar
Discard
0
Avatar
maeschba
Best Answer

There has a new BIOS version been posted 3 days ago (v0.16), but I didn't hear anything from Slimbook support or in the forum. My machine runs still dual-boot Windows 11 (workable, no possibility to turn off the fans, no proper sleep/wake-support) and Ubuntu (occasionally freezes, no proper sleep/wake-support).

It has been since the end of December, that the KDE Slimbook VII is in this deplorable state (the sticker powered by GNU/Linux seems to be a joke).

Does anybody else have the same hardware and did already try to update BIOS V0.13 to V0.16? Unfortunately, there is no changelog in the download, so I don't know what this update addresses.

Avatar
Discard
0
Avatar
maeschba
Best Answer

Hi maeschba.

Initially I too had had problems with the sleep functionality. However, the amd_iommu=off did the trick for me since I am using systemd-boot and the fix packages were for grub. Luckily , I did not experience the further issues you mentioned. I am also using Archlinux which I did installed my self. Did you tried the new BIOS version? I did try it and for me solved the sleep issue, I no longer need the amd_iommu=off kernel parameter. 

Best Regards

Avatar
Discard
0
Avatar
maeschba
Best Answer

Hi David. Thank you for your notice. I did not try yet. Is there any chance that the fans stop spinning with the new release or is there always this constant low spinning, even if the system is idle? Are the dmesg errors regarding \_SB.ADP1._PSR gone? 

Avatar
Discard
0
Avatar
maeschba
Best Answer

Suspend seems to work. dmesg only shows a problem with audio hardware and the cooling system is still a black box.

The most annoying part is that there is constant fan noise, even if the system is idle on TTY.

Avatar
Discard
1
Avatar
maeschba
Best Answer

Hi maeschba. So far I had not noticed a lot of fan spinning, only on occasion. But you are right! They are spinning constantly but the sound was sow low I did notice. Even when changing modes. I'll check the bios but I am pretty sure I did not activate the fans always-on option. Regarding the ACPI logs mine seem to be fine, at least for the current bios:

[    0.000000] BIOS-e820: [mem 0x0000000009f00000-0x0000000009f3bfff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x000000007977f000-0x0000000079f7efff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x0000000079f7f000-0x0000000079ffefff] ACPI data
[    0.000000] efi: ACPI=0x79ffe000 ACPI 2.0=0x79ffe014 SMBIOS=0x77e73000 SMBIOS 3.0=0x77e70000 MEMATTR=0x72f4a018 ESRT=0x72f57e98 RNG=0x79f99f18 INITRD=0x72b7cf18 
[    0.008135] ACPI: Early table checksum verification disabled
[    0.008139] ACPI: RSDP 0x0000000079FFE014 000024 (v02 INSYDE)
[    0.008144] ACPI: XSDT 0x0000000079F9A228 00016C (v01 INSYDE EDK2     00000001      01000013)
[    0.008152] ACPI: FACP 0x0000000079FEE000 000114 (v06 INSYDE EDK2     00000001 ACPI 00040000)
[    0.008159] ACPI: DSDT 0x0000000079FC6000 007112 (v02 INSYDE EDK2     00040000 ACPI 00040000)
[    0.008162] ACPI: FACS 0x0000000079E94000 000040
[    0.008164] ACPI: UEFI 0x0000000079F66000 0001CF (v01 INSYDE EDK2     00000001 ACPI 00040000)
[    0.008166] ACPI: SSDT 0x0000000079FFB000 001335 (v01 INSYDE EDK2     00000001 ACPI 00040000)
[    0.008169] ACPI: ASF! 0x0000000079FFA000 000085 (v32 INSYDE EDK2     00000002 ACPI 00040000)
[    0.008171] ACPI: SSDT 0x0000000079FF2000 007F18 (v02 INSYDE EDK2     00000002 ACPI 00040000)
[    0.008174] ACPI: ASF! 0x0000000079FF0000 0000A5 (v32 INSYDE EDK2     00000001 ACPI 00040000)
[    0.008176] ACPI: BOOT 0x0000000079FEF000 000028 (v01 INSYDE EDK2     00000001 ACPI 00040000)
[    0.008178] ACPI: HPET 0x0000000079FED000 000038 (v01 INSYDE EDK2     00000001 ACPI 00040000)
[    0.008181] ACPI: MCFG 0x0000000079FEC000 00003C (v01 INSYDE EDK2     00000001 ACPI 00040000)
[    0.008183] ACPI: SLIC 0x0000000079FEB000 000176 (v01 INSYDE EDK2     00000001 ACPI 00040000)
[    0.008185] ACPI: APIC 0x0000000079FE1000 00010A (v06 INSYDE EDK2     00000002 ACPI 00040000)
[    0.008187] ACPI: SSDT 0x0000000079FE0000 00058F (v01 INSYDE EDK2     00003000 ACPI 00040000)
[    0.008190] ACPI: SSDT 0x0000000079FDF000 00021A (v02 AMD    Hetero   00000001 INTL 20200326)
[    0.008193] ACPI: PCCT 0x0000000079FDE000 0000D4 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.008195] ACPI: SSDT 0x0000000079FD7000 006992 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.008197] ACPI: VFCT 0x0000000079FD1000 005484 (v01 INSYDE EDK2     00000001 ACPI 00040000)
[    0.008199] ACPI: ABLT 0x0000000079FD0000 0002C2 (v00 INSYDE EDK2     00000000 ACPI 00040000)
[    0.008202] ACPI: SSDT 0x0000000079FCF000 0000F8 (v02 INSYDE EDK2     00001000 ACPI 00040000)
[    0.008204] ACPI: SSDT 0x0000000079FFD000 000664 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.008206] ACPI: SSDT 0x0000000079FE8000 0008E6 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.008209] ACPI: SSDT 0x0000000079FE6000 001DB7 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.008211] ACPI: SSDT 0x0000000079FE4000 00169E (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.008213] ACPI: SSDT 0x0000000079FC3000 002AA6 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.008215] ACPI: SSDT 0x0000000079FB9000 009A47 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.008217] ACPI: FPDT 0x0000000079FE3000 000044 (v01 INSYDE EDK2     00000002 ACPI 00040000)
[    0.008220] ACPI: WSMT 0x0000000079FB8000 000028 (v01 INSYDE EDK2     00000001 ACPI 00040000)
[    0.008222] ACPI: SSDT 0x0000000079FB5000 0023E0 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.008224] ACPI: IVRS 0x0000000079FEA000 0001BE (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.008226] ACPI: SSDT 0x0000000079FE9000 000C17 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.008229] ACPI: SSDT 0x0000000079FB3000 0013E2 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.008231] ACPI: SSDT 0x0000000079FB1000 0016CD (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.008233] ACPI: SSDT 0x0000000079FB0000 000500 (v02 INSYDE EDK2     00000002 ACPI 00040000)
[    0.008235] ACPI: SSDT 0x0000000079FAF000 00080C (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.008238] ACPI: SSDT 0x0000000079FAD000 00101C (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.008240] ACPI: SSDT 0x0000000079FA3000 0097D1 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.008242] ACPI: SSDT 0x0000000079F9E000 004608 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.008244] ACPI: SSDT 0x0000000079F9D000 000DC3 (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.008246] ACPI: SSDT 0x0000000079F9C000 00096A (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.008249] ACPI: SSDT 0x0000000079F9B000 00008D (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.008251] ACPI: SSDT 0x0000000079FCE000 000F5C (v02 INSYDE EDK2     00000001 ACPI 00040000)
[    0.008253] ACPI: BGRT 0x0000000079FE2000 000038 (v01 INSYDE EDK2     00000002 ACPI 00040000)
[    0.008255] ACPI: Reserving FACP table memory at [mem 0x79fee000-0x79fee113]
[    0.008257] ACPI: Reserving DSDT table memory at [mem 0x79fc6000-0x79fcd111]
[    0.008257] ACPI: Reserving FACS table memory at [mem 0x79e94000-0x79e9403f]
[    0.008258] ACPI: Reserving UEFI table memory at [mem 0x79f66000-0x79f661ce]
[    0.008259] ACPI: Reserving SSDT table memory at [mem 0x79ffb000-0x79ffc334]
[    0.008259] ACPI: Reserving ASF! table memory at [mem 0x79ffa000-0x79ffa084]
[    0.008260] ACPI: Reserving SSDT table memory at [mem 0x79ff2000-0x79ff9f17]
[    0.008260] ACPI: Reserving ASF! table memory at [mem 0x79ff0000-0x79ff00a4]
[    0.008261] ACPI: Reserving BOOT table memory at [mem 0x79fef000-0x79fef027]
[    0.008262] ACPI: Reserving HPET table memory at [mem 0x79fed000-0x79fed037]
[    0.008262] ACPI: Reserving MCFG table memory at [mem 0x79fec000-0x79fec03b]
[    0.008263] ACPI: Reserving SLIC table memory at [mem 0x79feb000-0x79feb175]
[    0.008263] ACPI: Reserving APIC table memory at [mem 0x79fe1000-0x79fe1109]
[    0.008264] ACPI: Reserving SSDT table memory at [mem 0x79fe0000-0x79fe058e]
[    0.008265] ACPI: Reserving SSDT table memory at [mem 0x79fdf000-0x79fdf219]
[    0.008265] ACPI: Reserving PCCT table memory at [mem 0x79fde000-0x79fde0d3]
[    0.008266] ACPI: Reserving SSDT table memory at [mem 0x79fd7000-0x79fdd991]
[    0.008266] ACPI: Reserving VFCT table memory at [mem 0x79fd1000-0x79fd6483]
[    0.008267] ACPI: Reserving ABLT table memory at [mem 0x79fd0000-0x79fd02c1]
[    0.008268] ACPI: Reserving SSDT table memory at [mem 0x79fcf000-0x79fcf0f7]
[    0.008268] ACPI: Reserving SSDT table memory at [mem 0x79ffd000-0x79ffd663]
[    0.008269] ACPI: Reserving SSDT table memory at [mem 0x79fe8000-0x79fe88e5]
[    0.008270] ACPI: Reserving SSDT table memory at [mem 0x79fe6000-0x79fe7db6]
[    0.008270] ACPI: Reserving SSDT table memory at [mem 0x79fe4000-0x79fe569d]
[    0.008271] ACPI: Reserving SSDT table memory at [mem 0x79fc3000-0x79fc5aa5]
[    0.008271] ACPI: Reserving SSDT table memory at [mem 0x79fb9000-0x79fc2a46]
[    0.008272] ACPI: Reserving FPDT table memory at [mem 0x79fe3000-0x79fe3043]
[    0.008273] ACPI: Reserving WSMT table memory at [mem 0x79fb8000-0x79fb8027]
[    0.008273] ACPI: Reserving SSDT table memory at [mem 0x79fb5000-0x79fb73df]
[    0.008274] ACPI: Reserving IVRS table memory at [mem 0x79fea000-0x79fea1bd]
[    0.008275] ACPI: Reserving SSDT table memory at [mem 0x79fe9000-0x79fe9c16]
[    0.008275] ACPI: Reserving SSDT table memory at [mem 0x79fb3000-0x79fb43e1]
[    0.008276] ACPI: Reserving SSDT table memory at [mem 0x79fb1000-0x79fb26cc]
[    0.008276] ACPI: Reserving SSDT table memory at [mem 0x79fb0000-0x79fb04ff]
[    0.008277] ACPI: Reserving SSDT table memory at [mem 0x79faf000-0x79faf80b]
[    0.008278] ACPI: Reserving SSDT table memory at [mem 0x79fad000-0x79fae01b]
[    0.008278] ACPI: Reserving SSDT table memory at [mem 0x79fa3000-0x79fac7d0]
[    0.008279] ACPI: Reserving SSDT table memory at [mem 0x79f9e000-0x79fa2607]
[    0.008280] ACPI: Reserving SSDT table memory at [mem 0x79f9d000-0x79f9ddc2]
[    0.008280] ACPI: Reserving SSDT table memory at [mem 0x79f9c000-0x79f9c969]
[    0.008281] ACPI: Reserving SSDT table memory at [mem 0x79f9b000-0x79f9b08c]
[    0.008281] ACPI: Reserving SSDT table memory at [mem 0x79fce000-0x79fcef5b]
[    0.008282] ACPI: Reserving BGRT table memory at [mem 0x79fe2000-0x79fe2037]
[    0.037930] ACPI: PM-Timer IO Port: 0x408
[    0.037943] ACPI: X2APIC_NMI (uid[0xffffffff] high level lint[0x1])
[    0.037946] ACPI: LAPIC_NMI (acpi_id[0xff] high level lint[0x1])
[    0.037968] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.037970] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
[    0.037975] ACPI: Using ACPI (MADT) for SMP configuration information
[    0.037977] ACPI: HPET id: 0x10228201 base: 0xfed00000
[    0.114036] ACPI: Core revision 20250807
[    0.280165] ACPI: PM: Registering ACPI NVS region [mem 0x09f00000-0x09f3bfff] (245760 bytes)
[    0.280165] ACPI: PM: Registering ACPI NVS region [mem 0x7977f000-0x79f7efff] (8388608 bytes)
[    0.284730] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[    0.286878] ACPI: Added _OSI(Module Device)
[    0.286880] ACPI: Added _OSI(Processor Device)
[    0.286881] ACPI: Added _OSI(Processor Aggregator Device)
[    0.309026] ACPI: 26 ACPI AML tables successfully acquired and loaded
[    0.321089] ACPI: EC: EC started
[    0.321090] ACPI: EC: interrupt blocked
[    0.341777] ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
[    0.341781] ACPI: \_SB_.PCI0.LPC0.H_EC: Boot DSDT EC used to handle transactions
[    0.341783] ACPI: Interpreter enabled
[    0.341800] ACPI: PM: (supports S0 S4 S5)
[    0.341802] ACPI: Using IOAPIC for interrupt routing
[    0.342574] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    0.342964] ACPI: Enabled 3 GPEs in block 00 to 1F
[    0.344673] ACPI: \_SB_.PCI0.GPP0.PWRS: New power resource
[    0.345203] ACPI: \_SB_.PCI0.GPP0.SWUS.PWRS: New power resource
[    0.345695] ACPI: \_SB_.PCI0.GPP1.PWRS: New power resource
[    0.346199] ACPI: \_SB_.PCI0.GPP1.SWUS.PWRS: New power resource
[    0.346490] ACPI: \_SB_.PCI0.GPP3.P0NV: New power resource
[    0.347893] ACPI: \_SB_.PCI0.GPPA.PWRS: New power resource
[    0.348114] ACPI: \_SB_.PCI0.GPPA.VGA_.PWRS: New power resource
[    0.348392] ACPI: \_SB_.PCI0.GPPA.ACP_.PWRS: New power resource
[    0.348826] ACPI: \_SB_.PCI0.GPPA.AZAL.PWRS: New power resource
[    0.349170] ACPI: \_SB_.PCI0.GPPA.HDAU.PWRS: New power resource
[    0.349538] ACPI: \_SB_.PCI0.GPPA.XHC1.PWRS: New power resource
[    0.351118] ACPI: \_SB_.PCI0.GPPC.XHC0.PWRS: New power resource
[    0.353303] ACPI: \_SB_.PCI0.GPPC.XHC3.PWRS: New power resource
[    0.354417] ACPI: \_SB_.PCI0.GPPC.XHC4.PWRS: New power resource
[    0.355537] ACPI: \_SB_.PCI0.GPPC.NHI0.PWRS: New power resource
[    0.356917] ACPI: \_SB_.PCI0.GPPC.NHI1.PWRS: New power resource
[    0.364358] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[    0.364370] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI EDR HPX-Type3]
[    0.364469] acpi PNP0A08:00: _OSC: platform does not support [SHPCHotplug AER]
[    0.364621] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME PCIeCapability LTR DPC]
[    0.384392] ACPI: EC: interrupt unblocked
[    0.384394] ACPI: EC: event unblocked
[    0.384415] ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
[    0.384415] ACPI: EC: GPE=0xa
[    0.384415] ACPI: \_SB_.PCI0.LPC0.H_EC: Boot DSDT EC initialization complete
[    0.384415] ACPI: \_SB_.PCI0.LPC0.H_EC: EC: Used to handle transactions and events
[    0.384645] ACPI: bus type USB registered
[    0.400792] PCI: Using ACPI for IRQ routing
[    0.412771] pnp: PnP ACPI init
[    0.415617] pnp: PnP ACPI: found 5 devices
[    0.421748] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
[    0.511239] ACPI: AC: AC Adapter [ADP1] (off-line)
[    0.511325] ACPI: button: Power Button [PWRB]
[    0.511393] ACPI: button: Lid Switch [LID0]
[    0.515310] ACPI: thermal: Thermal Zone [TZ01] (22 C)
[    0.516473] ACPI: battery: Slot [BAT0] (battery present)
[    0.518227] ACPI: bus type drm_connector registered
[    0.733989] ACPI: video: Video Device [VGA] (multi-head: yes  rom: no  post: no)

For the audio I also seem to get no issues:
[    5.376776] snd_acp_pci 0000:03:00.5: enabling device (0000 -> 0002)
[    5.385311] snd_hda_intel 0000:03:00.1: enabling device (0000 -> 0002)
[    5.385334] snd_hda_intel 0000:03:00.1: Handle vga_switcheroo audio client
[    5.385397] snd_hda_intel 0000:03:00.6: enabling device (0000 -> 0002)
[    5.397860] snd_hda_intel 0000:03:00.1: bound 0000:03:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
[    5.398449] input: HD-Audio Generic HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:08.1/0000:03:00.1/sound/card0/input9
[    5.424510] snd_hda_codec_alc269 hdaudioC1D0: autoconfig for ALC269VC: line_outs=1 (0x1a/0x0/0x0/0x0/0x0) type:speaker
[    5.424513] snd_hda_codec_alc269 hdaudioC1D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[    5.424514] snd_hda_codec_alc269 hdaudioC1D0:    hp_outs=1 (0x15/0x0/0x0/0x0/0x0)
[    5.424515] snd_hda_codec_alc269 hdaudioC1D0:    mono: mono_out=0x0
[    5.424515] snd_hda_codec_alc269 hdaudioC1D0:    inputs:
[    5.424516] snd_hda_codec_alc269 hdaudioC1D0:      Internal Mic=0x12
[    5.424517] snd_hda_codec_alc269 hdaudioC1D0:      Mic=0x18
[    5.433337] input: HD-Audio Generic Mic as /devices/pci0000:00/0000:00:08.1/0000:03:00.6/sound/card1/input10
[    5.433357] input: HD-Audio Generic Headphone as /devices/pci0000:00/0000:00:08.1/0000:03:00.6/sound/card1/input11

Only the fans contant spinning seems to be the problem. That and DC offset pulse that causes that pop sound when they activate (only happens sometimes).

Best regards

Avatar
Discard
0
Avatar
maeschba
Best Answer

[Update] It seems that there is no fan control option in the BIOS. I must have have confused with another device BIOS.

Avatar
Discard
0
Avatar
maeschba
Best Answer

I do have similar output regarding audio:

[    2.393425] platform acp_asoc_acp70.0: warning: No matching ASoC machine driver found

...
[    2.409475] snd_hda_intel 0000:03:00.1: enabling device (0000 -> 0002)
[    2.409503] snd_hda_intel 0000:03:00.1: Handle vga_switcheroo audio client
[    2.409577] snd_hda_intel 0000:03:00.6: enabling device (0000 -> 0002)
[    2.412146] [drm] Initialized amdxdna_accel_driver 0.0.0 for 0000:04:00.1 on minor 0
[    2.413304] mt7921e 0000:02:00.0: ASIC revision: 79220010
[    2.417556] input: HD-Audio Generic HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:08.1/0000:03:00.1/sound/card0/input8
[    2.429203] snd_hda_codec_alc269 hdaudioC1D0: autoconfig for ALC269VC: line_outs=1 (0x1a/0x0/0x0/0x0/0x0) type:speaker
[    2.429208] snd_hda_codec_alc269 hdaudioC1D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[    2.429209] snd_hda_codec_alc269 hdaudioC1D0:    hp_outs=1 (0x15/0x0/0x0/0x0/0x0)
[    2.429210] snd_hda_codec_alc269 hdaudioC1D0:    mono: mono_out=0x0
[    2.429210] snd_hda_codec_alc269 hdaudioC1D0:    inputs:
[    2.429211] snd_hda_codec_alc269 hdaudioC1D0:      Internal Mic=0x12
[    2.429212] snd_hda_codec_alc269 hdaudioC1D0:      Mic=0x18
[    2.441947] input: HD-Audio Generic Mic as /devices/pci0000:00/0000:00:08.1/0000:03:00.6/sound/card1/input9
[    2.441976] input: HD-Audio Generic Headphone as /devices/pci0000:00/0000:00:08.1/0000:03:00.6/sound/card1/input10

The kernel detects AMD's ACP 7.0 audio hardware but a generic driver is covering for a missing machine driver. This doesn't really look like a Laptop genuinely built for Linux.

I can also confirm the pop sound that sometimes happens at startup.

This morning, my KDE Slimbook VII hard-crashed in Windows 11(!). This is the first or second time since I switched to dual-boot in February. Perhaps it's a coincidence, but Firefox is always in use just before a crash. I deactivated Firefox' hardware acceleration now in Linux and in Windows. 

 

Avatar
Discard
0
Avatar
maeschba
Best Answer

Hello, @maeschba
Until the machine driver is not added here the kernel will still warn that it can't find a machine driver, it is a kernel issue and not hardware related, in any case the audio should work properly generally
As for the audio pops/crackling, you can follow the arch wiki troubleshooting section: https://wiki.archlinux.org/title/Advanced_Linux_Sound_Architecture/Troubleshooting
If there were any logs for the Windows crash, you could send them to see what truly crashed the device

Regards,

Avatar
Discard