You are not logged in.
Messed up my system. After an update the system froze with HAL_REO_CMD_FLUSH_CACHE and No EDID read errors, and integrated ath12k network controller vanished after reboot. Downgraded linux-firmware packages to 202510 and 202509 versions, nothing. Booted LTS kernel, nothing. Switched to iwd backend and back, nothing. Read about mkinitcpio systemd hook changes, did that, the system throws /boot mount error but continues to boot after several Enter key presses (unrelated stuff, of course, but this one is reversible at least), nothing. Disabled audit, apparmor, firejail stuff, nothing. Uninstalled bluez, disabled bluetooth.service, and checked WiFi-only in UEFI settings, nothing. The system is technically partially upgraded due to ZFS kernel module delay stuff. I regularly maintain my system and check the logs in search of suspicious stuff, so this avalanche of random error bothers me.
Here's all the stuff I figured I should post for starts:
journalctl -b: https://paste.c-net.org/JolietConnor
lsmod: https://paste.c-net.org/OrientalSustain
lspci -v: https://paste.c-net.org/CoopersDebris
uname -a
Linux archie 6.12.57-2-lts #1 SMP PREEMPT_DYNAMIC Wed, 12 Nov 2025 15:16:57 +0000 x86_64 GNU/Linux
pacman -Q linux-lts
linux-lts 6.12.57-2The following is /etc/mkinitcpio.conf. If I switch back to the commented out Hooks section, and return the resume= part to kernel options, the system boots normally.
MODULES=()
BINARIES=()
FILES=()
# HOOKS=(base udev autodetect microcode modconf kms keyboard keymap consolefont block zfs filesystems resume fsck)
HOOKS=(base systemd autodetect microcode modconf kms keyboard sd-vconsole block zfs filesystems fsck)The /intel-ucode part was removed after the switch to systemd hook:
title Arch Linux LTS
linux /vmlinuz-linux-lts
initrd /initramfs-linux-lts.img
options root=UUID=d49abf4d-0fb2-4716-9f74-405832790fff rwI'm not sure what's going on here. Relevant threads show the system can be booted only via chroot, but here I'm able to just Enter-keypress it away:
ноя 14 23:44:44 archlinux systemd[1]: Mounting /boot...
ноя 14 23:44:44 archlinux systemd[1]: Starting Mountpoints Configured in the Real Root...
ноя 14 23:44:44 archlinux systemd[1]: Check battery level during early boot was skipped because of an unmet condition check (ConditionDirectoryNotEmpty=/sys/class/power_supply).
ноя 14 23:44:44 archlinux systemd[1]: TPM PCR Barrier (initrd) was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
ноя 14 23:44:44 archlinux mount[521]: mount: /boot: unknown filesystem type 'vfat'.
ноя 14 23:44:44 archlinux mount[521]: dmesg(1) may have more information after failed mount system call.
ноя 14 23:44:44 archlinux systemd[1]: boot.mount: Mount process exited, code=exited, status=32/n/a
ноя 14 23:44:44 archlinux systemd[1]: boot.mount: Failed with result 'exit-code'.
ноя 14 23:44:44 archlinux systemd[1]: Failed to mount /boot.
ноя 14 23:44:44 archlinux systemd[1]: Dependency failed for Local File Systems.
ноя 14 23:44:44 archlinux systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'.
ноя 14 23:44:44 archlinux systemd[1]: local-fs.target: Triggering OnFailure= dependencies.
ноя 14 23:44:44 archlinux systemd[1]: Started Emergency Shell.
ноя 14 23:44:44 archlinux systemd[1]: Reached target Emergency Mode.
ноя 14 23:44:44 archlinux systemd[1]: initrd-parse-etc.service: Deactivated successfully.
ноя 14 23:44:44 archlinux systemd[1]: Stopped Mountpoints Configured in the Real Root.
ноя 14 23:44:44 archlinux systemd[1]: initrd-parse-etc.service: Triggering OnSuccess= dependencies.
ноя 14 23:44:44 archlinux systemd[1]: Stopped target Emergency Mode.
ноя 14 23:44:44 archlinux systemd[1]: Starting Cleaning Up and Shutting Down Daemons...
ноя 14 23:44:44 archlinux (plymouth)[525]: emergency.service: Unable to locate executable 'plymouth': No such file or directory
ноя 14 23:44:44 archlinux systemd[1]: Stopped target Initrd Root Device.
ноя 14 23:44:44 archlinux systemd[1]: Stopped target Preparation for Local File Systems.
ноя 14 23:44:44 archlinux systemd[1]: Stopped target Path Units.
ноя 14 23:44:44 archlinux systemd[1]: Stopped target Slice Units.
ноя 14 23:44:44 archlinux systemd[1]: Stopped target Socket Units.
ноя 14 23:44:44 archlinux systemd[1]: Stopped target Swaps.
ноя 14 23:44:44 archlinux systemd[1]: Stopped target Timer Units.
ноя 14 23:44:44 archlinux systemd[1]: Stopping Emergency Shell...
ноя 14 23:44:44 archlinux systemd[1]: kmod-static-nodes.service: Deactivated successfully.
ноя 14 23:44:44 archlinux systemd[1]: Stopped Create List of Static Device Nodes.
ноя 14 23:44:44 archlinux systemd[1]: Stopping Display Boot-Time Emergency Messages In Full Screen...
ноя 14 23:44:44 archlinux systemd[1]: systemd-modules-load.service: Deactivated successfully.
ноя 14 23:44:44 archlinux systemd[1]: Stopped Load Kernel Modules.
ноя 14 23:44:44 archlinux systemd[1]: systemd-tmpfiles-setup.service: Deactivated successfully.
ноя 14 23:44:44 archlinux systemd[1]: Stopped Create System Files and Directories.
ноя 14 23:44:44 archlinux systemd[1]: systemd-udev-trigger.service: Deactivated successfully.
ноя 14 23:44:44 archlinux systemd[1]: Stopped Coldplug All udev Devices.
ноя 14 23:44:44 archlinux systemd[1]: Stopping Rule-based Manager for Device Events and Files...
ноя 14 23:44:44 archlinux systemd[1]: systemd-bsod.service: Deactivated successfully.
ноя 14 23:44:44 archlinux systemd[1]: Stopped Display Boot-Time Emergency Messages In Full Screen.
ноя 14 23:44:44 archlinux systemd[1]: emergency.service: Deactivated successfully.
ноя 14 23:44:44 archlinux systemd[1]: Stopped Emergency Shell.
ноя 14 23:44:44 archlinux systemd[1]: initrd-cleanup.service: Deactivated successfully.
ноя 14 23:44:44 archlinux systemd[1]: Finished Cleaning Up and Shutting Down Daemons.
ноя 14 23:44:44 archlinux systemd[1]: systemd-udevd.service: Deactivated successfully.
ноя 14 23:44:44 archlinux systemd[1]: Stopped Rule-based Manager for Device Events and Files.
ноя 14 23:44:44 archlinux systemd[1]: systemd-udevd.service: Consumed 4.866s CPU time, 47.6M memory peak.
ноя 14 23:44:44 archlinux systemd[1]: systemd-udevd-control.socket: Deactivated successfully.
ноя 14 23:44:44 archlinux systemd[1]: Closed udev Control Socket.
ноя 14 23:44:44 archlinux systemd[1]: Starting Cleanup udev Database...
ноя 14 23:44:44 archlinux systemd[1]: systemd-tmpfiles-setup-dev.service: Deactivated successfully.
ноя 14 23:44:44 archlinux systemd[1]: Stopped Create Static Device Nodes in /dev.
ноя 14 23:44:44 archlinux systemd[1]: initrd-udevadm-cleanup-db.service: Deactivated successfully.
ноя 14 23:44:44 archlinux systemd[1]: Finished Cleanup udev Database.
ноя 14 23:44:44 archlinux systemd[1]: Reached target Switch Root.
ноя 14 23:44:44 archlinux systemd[1]: Starting Switch Root...
ноя 14 23:44:44 archlinux systemd[1]: Switching root.Logs also show something messed up with swap partition, however swapon --show displays it correctly (although USED section is suspiciously low):
# /dev/nvme0n1p3
UUID=d49abf4d-0fb2-4716-9f74-405832790fff / ext4 defaults 0 1
# /dev/nvme0n1p4
UUID=d1e26a2a-c9bb-476d-8993-6c33f4f5990b /home ext4 defaults 0 2
# /dev/nvme0n1p1
UUID=2451-1182 /boot vfat defaults,nodev,nosuid,noexec,fmask=0177,dmask=0077 0 2
# /dev/nvme0n1p2
UUID=ee3492ce-e6aa-43ac-aec7-1a7330549c21 none swap defaults 0 0It's the first time in years I've run into system-breaking behavior and this time I can't figure it out myself, so help would be greatly appreciated.
Last edited by dr3amyxen0 (2025-11-15 01:39:59)
Offline
Does the fallback initrd which will not use the autodetect hook also have the same issues?
Offline
Does the fallback initrd which will not use the autodetect hook also have the same issues?
Messed with the initramfs and hooks some more after composing the initial post, the culprit there was zfs hook. I had switched from zfs-mount to zfs-mount-generator half a year ago and forgot to remove the hook, and apparently it became a problem only when I introduced systemd hook to the mix. As for the network aspect, this has never happened to me before, but basically the motherboard itself glitched, and I had to clear CMOS with a screwdriver. I believe there was a power outage when I was at work or whatever. Anyways, I couldn't suspect it could fail in a way when everything basically works, but one system part doesn't, as all the errors were pretty generic on their own. So, fresh login, no errors, everything works. I hope it stays this way, thanks for coming to the rescue.
Offline