ACPI_BIOS_ERROR on Boot

[Andre]

Hello,

I switched from Windows to Garuda Linux because I’ve been getting BSOD boot loops that I couldn’t debug.

However, after using Garuda for some time (and Linux overall), I could see the logs from journalctl and this is what they say:

Nov 04 00:26:48 ASUS-A15 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GP19.NHI0._RST], AE_ALREADY_EXISTS (20240322/dswload2-326)
Nov 04 00:26:48 ASUS-A15 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240322/psobject-220)
Nov 04 00:26:48 ASUS-A15 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GP19.NHI1._RST], AE_ALREADY_EXISTS (20240322/dswload2-326)
Nov 04 00:26:48 ASUS-A15 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240322/psobject-220)
Nov 04 00:26:48 ASUS-A15 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP2.WWAN], AE_NOT_FOUND (20240322/dswload2-162)
Nov 04 00:26:48 ASUS-A15 kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20240322/psobject-220)
Nov 04 00:26:48 ASUS-A15 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP5.RTL8], AE_NOT_FOUND (20240322/dswload2-162)
Nov 04 00:26:48 ASUS-A15 kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20240322/psobject-220)
Nov 04 00:26:48 ASUS-A15 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP6.WLAN], AE_ALREADY_EXISTS (20240322/dswload2-326)
Nov 04 00:26:48 ASUS-A15 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240322/psobject-220)
Nov 04 00:26:48 ASUS-A15 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP7.DEV0], AE_NOT_FOUND (20240322/dswload2-162)
Nov 04 00:26:48 ASUS-A15 kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20240322/psobject-220)
Nov 04 00:26:48 ASUS-A15 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_TZ.THRM._SCP.CTYP], AE_NOT_FOUND (20240322/psargs-332)
Nov 04 00:26:48 ASUS-A15 kernel: ACPI Error: Aborting method \_TZ.THRM._SCP due to previous error (AE_NOT_FOUND) (20240322/psparse-529)

My laptop is ASUS TUF A15 2022, I have the latest BIOS update (315), and I was thinking I could probably fix this in some way by messing with ACPI on Linux, maybe you guys are gonna suggest something to put in the GRUB…

Someone similar had the same issue: ACPI BIOS Error : How can i resolve these errors? - Kernel, boot, graphics & hardware - EndeavourOS

BUT it did not crash their system.

For me, it enters the panic mode 3-5 times before finally booting (I have to manually hold and restart with the power button on my laptop). Any suggestions guys? I tried everything including drivers installation (and a lot of stuff was tried on Windows too previously).

[SGS]

Please, post

garuda-inxi
jctl

missing symbols doesn’t crash the system.
You can restore last working snapshot if possible, or chroot and update your system, maybe install other kernel + headers too.

[filo]

If you don’t find inportant issues in the logs, I’d leave everything as is, since these errors are usually due to non standard BIOS implementation of ACPI.
See also here:

Errors at boot (log from journalctl)

As regards the ACPI errors, you can search the internet, maybe update the BIOS, search in the jungle of kernel boot parameters, maybe using this guide (not limited to!), but I think that they are often due to non-standard BIOS implementations. I think this article summerizes the point quite well:

[LolFlasherNoobX]

I do not know if I can help but I usually see these errors and have been seeing them for almost every single day , on every single distro since I first stepped into Linux. They have been harmless me for me.

For linux, if you do not have major usability problems, then you may continue using Garuda unworried. For windows, meh, meh. You may try a LTSC iso(dont switch to Windows now that you got yourself into linux ) or a clean iso from M$ website.

Since you get panic errors and boot issues, maybe try a different kernel ? linux or linux-lts ? Some kernels tend to be quirky with different hardware sometimes. You may also try to fiddle in your BIOS to see if any weird feature is turned on, look out for RAID !

[tbg]

@LolFlasherNoobX

look out for RAID

I do notice RST errors in your logs. Raid or RST should be disabled in your BIOS. Your bios should be set to use only AHCI.

Also, If your bios has a setting such as “fast boot” or “quick startup” be sure those are disabled in your bios as well.