You are not logged in.
Hi all, I have just finished building a new mini ITX rig using the following components: ASRock X570 Phantom Gaming-ITX/TB3 with latest BIOS update (ver 3.10), 16GB memory (Corsair RGB pro 3600), Sabrent Rocket Q4 NVMEe 4.0 1TB, AMD Radeon 5500XT 8GB GPU, AMD Ryzen 7 3700x 3.6 Ghz. Using Arch 5.11.16-arch1-1, qt: 5,15,2, Kde Frameworks: 5.81.0, KF5-config:1.0, Plasma: 5.21.4. Checked hardware working with Win10 install, no issues. I've done a few arch installs in the past on other hardware all went ok, with this new build though I am having "headbanging" issues, see journalctl extract:
May 01 00:33:46 Phanteks kernel: ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
May 01 00:33:46 Phanteks kernel: ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
May 01 00:33:46 Phanteks kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPC0.EC0], AE_NOT_FOUND (20201113/dswload2-162)
May 01 00:33:46 Phanteks kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20201113/psobject-220)
May 01 00:33:46 Phanteks kernel: ACPI: Skipping parse of AML opcode: Scope (0x0010)
May 01 00:33:46 Phanteks kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP1], AE_NOT_FOUND (20201113/dswload2-162)
May 01 00:33:46 Phanteks kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20201113/psobject-220)
May 01 00:33:46 Phanteks kernel: ACPI: Skipping parse of AML opcode: Scope (0x0010)
May 01 00:33:46 Phanteks kernel: ACPI: 9 ACPI AML tables successfully acquired and loaded
May 01 00:33:46 Phanteks kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
May 01 00:33:46 Phanteks kernel: ACPI: Interpreter enabled
May 01 00:33:46 Phanteks kernel: ACPI: (supports S0 S3 S4 S5)
May 01 00:33:46 Phanteks kernel: ACPI: Using IOAPIC for interrupt routing
May 01 00:33:46 Phanteks kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
May 01 00:33:46 Phanteks kernel: ACPI: Enabled 3 GPEs in block 00 to 1F
May 01 00:33:46 Phanteks kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
May 01 00:33:46 Phanteks kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI EDR HPX-Type3]
May 01 00:33:46 Phanteks kernel: acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug SHPCHotplug PME AER PCIeCapability LTR DPC]
May 01 00:33:46 Phanteks kernel: acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-7f] only partially covers this bridge
May 01 00:33:46 Phanteks kernel: PCI host bridge to bus 0000:00
May 01 00:33:46 Phanteks kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database
May 01 00:33:46 Phanteks kernel: cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
May 01 00:33:46 Phanteks systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
May 01 00:33:46 Phanteks systemd[1]: Finished Create Volatile Files and Directories.
May 01 00:33:46 Phanteks audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup comm="systemd" exe="/usr/lib/sys>
May 01 00:33:46 Phanteks kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
May 01 00:33:46 Phanteks kernel: cfg80211: failed to load regulatory.db
May 01 00:33:46 Phanteks systemd[1]: Starting Rebuild Journal Catalog...
May 01 00:33:46 Phanteks systemd[1]: Starting Update UTMP about System Boot/Shutdown...
May 01 00:33:46 Phanteks audit[408]: SYSTEM_BOOT pid=408 uid=0 auid=4294967295 ses=4294967295 msg=' comm="systemd-update-utmp" exe="/usr/lib/systemd/systemd->
May 01 00:33:46 Phanteks systemd[1]: Finished Update UTMP about System Boot/Shutdown.
May 01 00:33:46 Phanteks audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-update-utmp comm="systemd" exe="/usr/lib/system>
May 01 00:33:46 Phanteks systemd[1]: Finished Rebuild Dynamic Linker Cache.
May 01 00:33:46 Phanteks audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=ldconfig comm="systemd" exe="/usr/lib/systemd/systemd" >
May 01 00:33:46 Phanteks kernel: pps pps0: new PPS source ptp0
May 01 00:33:46 Phanteks kernel: igb 0000:26:00.0: added PHC on eth0
May 01 00:33:46 Phanteks kernel: igb 0000:26:00.0: Intel(R) Gigabit Ethernet Network Connection
May 01 00:33:46 Phanteks kernel: igb 0000:26:00.0: eth0: (PCIe:2.5Gb/s:Width x1) a8:a1:59:42:12:10
May 01 00:33:46 Phanteks kernel: igb 0000:26:00.0: eth0: PBA No: FFFFFF-0FF
May 01 00:33:46 Phanteks kernel: igb 0000:26:00.0: Using MSI-X interrupts. 2 rx queue(s), 2 tx queue(s)
May 01 00:33:46 Phanteks systemd[1]: Finished Rebuild Journal Catalog.
May 01 00:33:46 Phanteks audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journal-catalog-update comm="systemd" exe="/usr>
May 01 00:33:46 Phanteks systemd[1]: Starting Update is Completed...
May 01 00:33:46 Phanteks systemd[1]: Finished Update is Completed.
May 01 00:33:46 Phanteks audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-update-done comm="systemd" exe="/usr/lib/system>
May 01 00:33:46 Phanteks systemd[1]: Reached target System Initialization.
May 01 00:33:46 Phanteks systemd[1]: Started Daily verification of password and group files.
May 01 00:33:46 Phanteks kernel: Intel(R) Wireless WiFi driver for Linux
May 01 00:33:46 Phanteks kernel: iwlwifi 0000:25:00.0: enabling device (0000 -> 0002)
May 01 00:33:46 Phanteks kernel: iwlwifi 0000:25:00.0: api flags index 2 larger than supported by driver
May 01 00:33:46 Phanteks kernel: iwlwifi 0000:25:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.22
May 01 00:33:46 Phanteks kernel: iwlwifi 0000:25:00.0: loaded firmware version 59.601f3a66.0 cc-a0-59.ucode op_mode iwlmvm
May 01 00:33:46 Phanteks systemd-udevd[344]: Using default interface naming scheme 'v247'.
May 01 00:33:46 Phanteks systemd-udevd[344]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
May 01 01:06:05 Phanteks kernel: EDAC amd64: Node 0: DRAM ECC disabled.
May 01 01:06:05 Phanteks kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database
May 01 01:06:05 Phanteks kernel: cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
May 01 01:06:05 Phanteks kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
May 01 01:06:05 Phanteks kernel: cfg80211: failed to load regulatory.db
May 01 01:06:05 Phanteks systemd-udevd[353]: Using default interface naming scheme 'v247'.
May 01 01:06:05 Phanteks systemd-udevd[353]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
May 01 01:06:05 Phanteks kernel: usb 3-3: New USB device found, idVendor=0b05, idProduct=879e, bcdDevice= 0.03
May 01 01:06:05 Phanteks kernel: usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 01 01:06:05 Phanteks kernel: usb 3-3: Product: ROG STRIX LC
May 01 01:06:05 Phanteks kernel: usb 3-3: Manufacturer: AsusTek Computer Inc.
May 01 01:06:05 Phanteks kernel: usb 5-2: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
May 01 01:06:05 Phanteks kernel: usb 5-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
It looks to me like there are BIOS and firmware bugs - see lines 3 and 10 from log extract. I have been searching other fora for similar issues, and it seems that back in 2020 (March/April) similar problems were reported on this forum, one was solved the other seemingly not. I have tried a lot of the suggestions found on eg. Gentoo etc. but I think the problem is related to faulty firmware/BIOS. I have emailed ASRock technical assistance with the output of journalctl, I'll report back what they say. As for the entry: " platform regulatory.0: Direct firmware load for regulatory.db failed with error -2", can anyone suggest cause?
I have installed mesa/mesa-git, linux-firmware/linux-firmware-git and tried various alternatives including non "git" packages but the issues remain. Does anyone have any suggestions?
Last edited by zaramaloo (2021-05-05 12:21:49)
Offline
SOLVED
Sorted the issue (or rather non issue) mb had severe firmware issues and I disconnected and reinstalled a Gigabyte X570 with similar architecture and everything works as it should (some minor issues as with all new installs), CLOSING this thread.
Offline