OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
boot-kernel low very-common DISPUTE

'ACPI BIOS Error (bug): Could not resolve symbol ... AE_NOT_FOUND' at boot

archomarchyendeavouroscachyosmanjaroacpilaptopdesktop
AUDITED Audited against its sources and confirmed accurate. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

Forum thread 305498 contains the exact NPCF.ACBT and EC0._Q83 lines, the reply calling them likely manufacturer ACPI table bugs with possibly little impact, the advice to update firmware, disable CSM and pick Linux or Other OS options, and a second reporter's 3 to 4 second boot delay. The raw Silent_boot wiki supports quiet loglevel=3, that both are needed and quiet must come first, and that loglevel only changes console output while dmesg and the journal keep the messages. On this machine /etc/limine-entry-tool.d/omarchy-defaults.conf sets 'quiet splash loglevel=0', so the Omarchy statement holds. /usr/share/omarchy/bin/omarchy-update-firmware exists and calls sudo itself, so 'no sudo' is right. The danger about interrupted BIOS updates is reasonable. Nothing in the record is Omarchy 3 layout or unsupported. Not exercised: no firmware update or cmdline change was made.

RISK

A failed or interrupted BIOS update can brick the board. Use AC power and the vendor's procedure.

Symptom

Red lines on the console or in journalctl -k at every boot, often on a new laptop:


ACPI BIOS Error (bug): Could not resolve symbol [^^^^NPCF.ACBT], AE_NOT_FOUND (20240827/psargs-332)
ACPI Error: Aborting method \_SB.PCI0.SBRG.EC0._Q83 due to previous error (AE_NOT_FOUND) (20240827/psparse-529)

Users often assume these are why boot is slow or failing.

Cause

The firmware's ACPI tables (DSDT/SSDT) reference objects that do not exist, usually because the vendor tested only against Windows. The kernel's ACPI interpreter reports each failed lookup and aborts that one method. The rest of the system carries on. Arch forum replies treat these as firmware bugs with usually little impact. One reporter saw an extra 3 to 4 seconds of boot time, and no thread ties them to a failed boot. If boot actually fails, the cause is elsewhere.

Fix

Treat these lines as noise unless a specific feature tied to the named method is broken, such as battery status for _BST/_BIF or fan control for EC _Qxx methods. Then:

  1. Update the firmware. Omarchy: omarchy-update-firmware (no sudo). Elsewhere: fwupdmgr refresh && fwupdmgr update, or the vendor's BIOS tool.
  2. In firmware setup, disable CSM and pick any "Linux" or "Other OS" option.

To keep them off the console, Arch: use quiet loglevel=3, which hides kernel messages at error level and below from the console only, in that order on the kernel command line. Omarchy 4 already boots with quiet splash loglevel=0, so these lines appear only in the journal.

To look for the real cause of a boot problem, read the errors around it rather than the ACPI noise:


journalctl -b -p err
systemd-analyze critical-chain

Verify

With quiet loglevel=3 the ACPI lines no longer appear on the console, though journalctl -k -p err -b still lists them. Boot time and device function are unchanged.

Sources

acpi-bios-error-could-not-resolve-symbol-harmless