System Details:
This report was compiled on August 15, 2025.
System:
Kernel: 6.15.9-zen1-1.1-zen arch: x86\_64 bits: 64 compiler: gcc v: 15.1.1
clocksource: tsc avail: acpi\_pm
parameters: BOOT\_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=fd6c5ed8-44c7-4bd6-93e0-ecaa4cf684cf rw rootflags=subvol=@ quiet
loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.4.4 tk: Qt v: N/A info: frameworks v: 6.17.0
wm: kwin\_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Laptop System: ASUSTeK product: ROG Strix G512LW\_G512LW v: 1.0
serial: \<superuser required\>
Mobo: ASUSTeK model: G512LW v: 1.0 serial: \<superuser required\>
uuid: \<superuser required\> UEFI: American Megatrends v: G512LW.314
date: 04/27/2021
CPU:
Info: model: Intel Core i7-10750H bits: 64 type: MT MCP arch: Comet Lake
gen: core 10 level: v3 note: check built: 2020 process: Intel 14nm family: 6
model-id: 0xA5 (165) stepping: 2 microcode: 0x100
Graphics:
Device-1: Intel CometLake-H GT2 [UHD Graphics] vendor: ASUSTeK driver: i915
v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports:
active: eDP-1 empty: none bus-ID: 0000:00:02.0 chip-ID: 8086:9bc4
class-ID: 0300
Device-2: NVIDIA TU106M [GeForce RTX 2070 Mobile / Max-Q Refresh]
vendor: ASUSTeK driver: nouveau v: kernel non-free: 550-570.xx+
status: current (as of 2025-04; EOL\~2026-12-xx) arch: Turing code: TUxxx
process: TSMC 12nm FF built: 2018-2022 ports: active: none
empty: DP-1,HDMI-A-1 bus-ID: 0000:01:00.0 chip-ID: 10de:1f14 class-ID: 0300
Display: wayland server: X.org v: 1.21.1.18 with: Xwayland v: 24.1.8
compositor: kwin\_wayland driver: X: loaded: modesetting
alternate: fbdev,intel,nouveau,nv,vesa dri: iris gpu: i915 display-ID: 0
Monitor-1: eDP-1 model: ChiMei InnoLux 0x1521 built: 2020 res:
mode: 1920x1000 hz: 144 scale: 100% (1) dpi: 142 gamma: 1.2
size: 344x193mm (13.54x7.6") diag: 394mm (15.5") ratio: 16:9
modes: 1920x1080
API: EGL v: 1.5 hw: drv: intel iris platforms: device: 1 drv: iris
device: 2 drv: swrast gbm: drv: kms\_swrast surfaceless: drv: iris wayland:
drv: iris x11: drv: iris inactive: device-0
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.1.7-arch1.1
glx-v: 1.4 direct-render: yes renderer: Mesa Intel UHD Graphics (CML GT2)
device-ID: 8086:9bc4 memory: 15.04 GiB unified: yes display-ID: :1.0
API: Vulkan v: 1.4.321 layers: 9 device: 0 type: integrated-gpu name: Intel
UHD Graphics (CML GT2) driver: mesa intel v: 25.1.7-arch1.1
device-ID: 8086:9bc4 surfaces: N/A device: 1 type: cpu name: llvmpipe
(LLVM 20.1.8 256 bits) driver: mesa llvmpipe v: 25.1.7-arch1.1 (LLVM
20.1.8) device-ID: 10005:0000 surfaces: N/A
Audio:
Device-1: Intel Comet Lake PCH cAVS vendor: ASUSTeK driver: snd\_hda\_intel
v: kernel alternate: snd\_soc\_avs,snd\_sof\_pci\_intel\_cnl bus-ID: 0000:00:1f.3
chip-ID: 8086:06c8 class-ID: 0403
Device-2: NVIDIA TU106 High Definition Audio vendor: ASUSTeK
driver: snd\_hda\_intel v: kernel bus-ID: 0000:01:00.1 chip-ID: 10de:1f09
class-ID: 0403
API: ALSA v: k6.15.9-zen1-1.1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.4.7 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Comet Lake PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 0000:00:14.3 chip-ID: 8086:06f0 class-ID: 0280
IF: wlo1 state: up mac: \<filter\>
Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK driver: r8169 v: kernel port: 3000 bus-ID: 0000:02:00.0
chip-ID: 10ec:8168 class-ID: 0200
IF: eno2 state: up speed: 1000 Mbps duplex: full mac: \<filter\>
RAID:
Hardware-1: Intel Comet Lake PCH-H RAID driver: intel\_nvme\_remap v: kernel
port: 5060 bus-ID: 0000:00:17.0 chip-ID: 8086:06d7 rev: class-ID: 0104
Drives:
Local Storage: total: 953.87 GiB used: 23.57 GiB (2.5%)
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Intel model: SSDPEKNW010T8
size: 953.87 GiB block-size: physical: 512 B logical: 512 B tech: SSD
serial: \<filter\> fw-rev: 002C temp: 28.9 C scheme: GPT
Partition:
ID-1: / raw-size: 953.57 GiB size: 953.57 GiB (100.00%)
used: 23.57 GiB (2.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 616 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
Summary of Issues:
I am reporting two distinct but critical issues on a fresh installation of Garuda Linux (KDE Dragonized).
- On a fresh installation, there is no audio from the internal speakers.
- Running the official
garuda-update
causes the system to freeze, and the subsequent repair process leads to a new boot failure.
Issue #1: No Speaker Audio (SOF Driver Failure)
The laptop’s ALC294 codec requires the snd_sof_pci_intel_cnl
driver. However, the system incorrectly defaults to snd_hda_intel
, which fails to initialize the speakers (dmesg
confirms speaker_outs=0
).
The core problem is that the system actively resists all attempts to load the correct SOF driver. We have confirmed the following methods fail:
modprobe
options: Settingoptions snd-hda-intel model=asus-zenbook
oralc294-asus
does not enable the speakers.- Kernel Parameter: Adding
snd_intel_dspcfg.dsp_driver=1
to the GRUB command line is completely ignored. - Dracut Early Loading: Forcing the SOF modules into the initramfs via a
dracut.conf.d
file is also ignored. - Blacklisting: Blacklisting
snd_hda_intel
results in the audio device havingdriver: N/A
. The correctsnd_sof
driver still fails to attach to the hardware.
Conclusion for Issue #1: The kernel appears unable to correctly probe and assign the SOF driver for this specific hardware, ignoring all standard configuration overrides.
Issue #2: System Freeze and Subsequent Boot Failure on Update (Critical Regression)
This issue describes a critical failure in the update process. The sequence of events is as follows:
- Start from a stable, working system (e.g., a fresh install or a restored snapshot).
- Run the official
garuda-update
command. - The update process proceeds normally until the post-transaction hooks, where it freezes the entire system at this exact point:
( 5/17) Reloading device manager configuration...
- A hard reboot is required. After rebooting, the system boots successfully back into the default
linux-zen
kernel, but the update is left in an incomplete state. - To properly complete the update and install an alternative kernel for testing (
linux-lts
), achroot
from a Live USB is necessary. Inside thechroot
, reinstalling the kernels (pacman -S linux-zen linux-lts
) and rebuilding the boot images (dracut-rebuild
) completes the transaction. - This is the critical failure: After the update is successfully completed via
chroot
, the newly generated boot image for thelinux-lts
kernel is not bootable. Attempting to boot thelinux-lts
kernel from the GRUB “Advanced options” menu fails, dropping to adracut
emergency shell with the error:Warning: /dev/disk/by-uuid/[your-uuid] does not exist
.
Conclusion for Issue #2: A package in the current repositories causes a severe instability. First, it freezes the system during the official update process at a udev
hook. Second, after forcing the update to complete, the dracut
process creates a broken initramfs
for at least the linux-lts
kernel, which lacks the modules to detect the NVMe storage. Note: The inxi
output shows the system is using the intel_nvme_remap
driver (Intel RST/RAID mode). The boot failure is very likely related to a regression in this specific driver or its interaction with dracut
.
Workaround:
The only way to maintain a stable system is to restore and stay on a BTRFS snapshot taken before the update is attempted.