Won't boot after latest updates

garuda-inxi
System:
Kernel: 6.4.4-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.1.1
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=4f4a6bc5-a19a-4528-a662-e2bb88015b4d rw rootflags=subvol=@
rd.driver.pre=vfio-pci intel_iommu=on quiet rd.udev.log_priority=3
vt.global_cursor_default=0 loglevel=3 options vfio_pci.ids=10de:1c82
pcie_acs_override=downstream,multifunction video=efifb:off iommu=pt
Desktop: KDE Plasma v: 5.27.6 tk: Qt v: 5.15.10 wm: kwin_x11 vt: 2
dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: TUF GAMING Z590-PLUS WIFI v: Rev 1.xx
serial: <superuser required> UEFI: American Megatrends v: 1801
date: 12/26/2022
Battery:
Device-1: hid-0003:256F:C62E.0002-battery model: 3Dconnexion SpaceMouse
Wireless serial: N/A charge: N/A status: discharging
CPU:
Info: model: 11th Gen Intel Core i9-11900KF bits: 64 type: MT MCP
arch: Rocket Lake gen: core 11 level: v4 note: check built: 2021+
process: Intel 14nm family: 6 model-id: 0xA7 (167) stepping: 1
microcode: 0x58
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
L1: 640 KiB desc: d-8x48 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
L3: 16 MiB desc: 1x16 MiB
Speed (MHz): avg: 1812 high: 3500 min/max: 800/5100:5300 scaling:
driver: intel_pstate governor: powersave cores: 1: 801 2: 3500 3: 801
4: 3500 5: 800 6: 800 7: 800 8: 800 9: 3500 10: 800 11: 800 12: 801
13: 3500 14: 3500 15: 3500 16: 799 bogomips: 112128
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA TU104 [GeForce RTX 2080 Rev. A] vendor: ZOTAC
driver: nvidia v: 535.86.05 alternate: nouveau,nvidia_drm non-free: 535.xx+
status: current (as of 2023-07) arch: Turing code: TUxxx
process: TSMC 12nm FF built: 2018-22 bus-ID: 0000:01:00.0
chip-ID: 10de:1e87 class-ID: 0300
Device-2: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: Micro-Star MSI
driver: vfio-pci v: N/A alternate: nouveau,nvidia_drm,nvidia
non-free: 535.xx+ status: current (as of 2023-07) arch: Pascal code: GP10x
process: TSMC 16nm built: 2016-21 bus-ID: 0000:04:00.0 chip-ID: 10de:1c82
class-ID: 0300
Device-3: Adomax Nuroum C40
driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-1.1:4 chip-ID: 0627:a6bf
class-ID: 0102 serial: <filter>
Device-4: Logitech HD Pro Webcam C920 driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 5-3.4.2:7
chip-ID: 046d:082d class-ID: 0102 serial: <filter>
Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.2
compositor: kwin_x11 driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nvidia,vfio-pci display-ID: :0
screens: 1
Screen-1: 0 s-res: 8320x1440 s-dpi: 92 s-size: 2297x393mm (90.43x15.47")
s-diag: 2330mm (91.75")
Monitor-1: DP-1 pos: 2-4 res: 1920x1080 hz: 60 dpi: 82
size: 598x336mm (23.54x13.23") diag: 686mm (27.01") modes: N/A
Monitor-2: DP-3 pos: 2-2 res: 1920x1080 hz: 60 dpi: 82
size: 598x336mm (23.54x13.23") diag: 686mm (27.01") modes: N/A
Monitor-3: DP-4 pos: primary,1-3 res: 2560x1440 dpi: 93
size: 698x392mm (27.48x15.43") diag: 801mm (31.52") modes: N/A
Monitor-4: USB-C-0 pos: 2-1 res: 1920x1080 dpi: 163
size: 300x260mm (11.81x10.24") diag: 397mm (15.63") modes: N/A
API: OpenGL v: 4.6.0 NVIDIA 535.86.05 renderer: NVIDIA GeForce RTX
2080/PCIe/SSE2 direct-render: Yes
Audio:
Device-1: Intel Tiger Lake-H HD Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel alternate: snd_sof_pci_intel_tgl bus-ID: 0000:00:1f.3
chip-ID: 8086:43c8 class-ID: 0403
Device-2: NVIDIA TU104 HD Audio vendor: ZOTAC driver: snd_hda_intel
v: kernel bus-ID: 0000:01:00.1 chip-ID: 10de:10f8 class-ID: 0403
Device-3: NVIDIA GP107GL High Definition Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel bus-ID: 0000:04:00.1 chip-ID: 10de:0fb9
class-ID: 0403
Device-4: Adomax Nuroum C40
driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-1.1:4 chip-ID: 0627:a6bf
class-ID: 0102 serial: <filter>
Device-5: Giga-Byte ESS SABRE HiFi USB Audio Device
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 480 Mb/s
lanes: 1 mode: 2.0 bus-ID: 1-12.2:15 chip-ID: 0414:a00c class-ID: 0300
Device-6: Giga-Byte USB Audio driver: snd-usb-audio type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-12.3:17 chip-ID: 0414:a008
class-ID: 0102 serial: <filter>
Device-7: Logitech HD Pro Webcam C920 driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 5-3.4.2:7
chip-ID: 046d:082d class-ID: 0102 serial: <filter>
Device-8: GN Netcom Jabra Engage 75 driver: jabra,snd-usb-audio,usbhid
type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 5-3.4.3:8
chip-ID: 0b0e:1112 class-ID: 0300 serial: <filter>
API: ALSA v: k6.4.4-zen1-1-zen status: kernel-api tools: N/A
Server-1: PipeWire v: 0.3.74 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 Tiger Lake PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 0000:00:14.3 chip-ID: 8086:43f0 class-ID: 0280
IF: wlo1 state: down mac: <filter>
Device-2: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel
port: N/A bus-ID: 0000:07:00.0 chip-ID: 8086:15f3 class-ID: 0200
IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: virbr0 state: down mac: <filter>
Bluetooth:
Device-1: Intel AX201 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-14:16 chip-ID: 8087:0026
class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
RAID:
Hardware-1: Intel Device driver: intel_nvme_remap v: N/A port: 5020
bus-ID: 0000:00:17.0 chip-ID: 8086:43d6 rev: N/A class-ID: 0104
Drives:
Local Storage: total: 22.53 TiB used: 2.22 TiB (9.9%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital
model: WDS100T2B0C-00PXH0 size: 931.51 GiB block-size: physical: 512 B
logical: 512 B tech: SSD serial: <filter> fw-rev: 233010WD temp: 28.9 C
scheme: MBR
ID-2: /dev/nvme1n1 maj-min: 259:3 vendor: Samsung model: SSD 970 EVO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 2B2QEXE7 temp: 34.9 C
scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: SanDisk model: SSD PLUS 1000GB
size: 931.52 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 00RL scheme: MBR
ID-4: /dev/sdb maj-min: 8:16 vendor: SanDisk model: SSD PLUS 1000GB
size: 931.52 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 00RL scheme: GPT
ID-5: /dev/sdc maj-min: 8:32 vendor: SanDisk model: SDSSDH3 512G
size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 1000 scheme: MBR
ID-6: /dev/sdd maj-min: 8:48 vendor: Silicon Power model: SPCC M.2 SSD
size: 119.24 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 1B0 scheme: GPT
ID-7: /dev/sde maj-min: 8:64 vendor: ASMedia model: T ASM236X NVME
size: 119.24 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 2.1 spd: 480 Mb/s lanes: 1 mode: 2.0 tech: SSD serial: <filter>
scheme: GPT
ID-8: /dev/sdf maj-min: 8:80 vendor: Samsung model: SSD 860 EVO 500GB
size: 465.76 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 3.0 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: SSD serial: <filter>
fw-rev: 0101 scheme: GPT
ID-9: /dev/sdg maj-min: 8:96 vendor: Samsung model: SSD 850 EVO 500GB
size: 465.76 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 3.0 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: SSD serial: <filter>
fw-rev: 0101 scheme: GPT
ID-10: /dev/sdh maj-min: 8:112 vendor: Seagate model: Expansion SW
size: 7.28 TiB block-size: physical: 4096 B logical: 512 B type: USB
rev: 3.2 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter>
fw-rev: 1801 scheme: GPT
ID-11: /dev/sdi maj-min: 8:128 vendor: Samsung model: SSD 860 EVO 500GB
size: 465.76 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 3.2 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: SSD serial: <filter>
fw-rev: 0057 scheme: GPT
ID-12: /dev/sdj maj-min: 8:144 vendor: Seagate model: Backup+ Hub BK
size: 3.64 TiB block-size: physical: 4096 B logical: 512 B type: USB
rev: 3.1 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter>
fw-rev: D781 scheme: GPT
ID-13: /dev/sdk maj-min: 8:160 vendor: Samsung model: SSD 860 EVO
size: 465.76 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 2.1 spd: 480 Mb/s lanes: 1 mode: 2.0 tech: SSD serial: <filter>
fw-rev: RVT0 scheme: GPT
ID-14: /dev/sdl maj-min: 8:176 model: USB 3.0 Device SCSI size: 465.76 GiB
block-size: physical: 4096 B logical: 512 B type: USB rev: 3.0 spd: 5 Gb/s
lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter> fw-rev: 0501
scheme: GPT
ID-15: /dev/sdm maj-min: 8:192 vendor: Samsung model: SSD 860 EVO 500GB
size: 465.76 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 3.0 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: SSD serial: <filter>
fw-rev: TB08 scheme: GPT
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
ID-16: /dev/sdn maj-min: 8:208 vendor: Samsung model: SSD 860 EVO 500GB
size: 465.76 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 2.1 spd: 480 Mb/s lanes: 1 mode: 2.0 tech: SSD serial: <filter>
fw-rev: TB08 scheme: GPT
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
ID-17: /dev/sdo maj-min: 8:224 vendor: Samsung model: SSD 860 EVO 500GB
size: 465.76 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 3.0 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: SSD serial: <filter>
fw-rev: TB08 scheme: GPT
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
ID-18: /dev/sdr maj-min: 65:16 vendor: Western Digital
model: WD40EFRX-68N32N0 size: 3.64 TiB block-size: physical: 4096 B
logical: 512 B type: USB rev: 3.0 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1
tech: HDD rpm: 5400 serial: <filter> fw-rev: 3004 scheme: GPT
Partition:
ID-1: / raw-size: 117.19 GiB size: 117.19 GiB (100.00%)
used: 79.26 GiB (67.6%) fs: btrfs dev: /dev/nvme1n1p5 maj-min: 259:8
ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
used: 25.6 MiB (26.7%) fs: vfat dev: /dev/nvme1n1p1 maj-min: 259:4
ID-3: /home raw-size: 117.19 GiB size: 117.19 GiB (100.00%)
used: 79.26 GiB (67.6%) fs: btrfs dev: /dev/nvme1n1p5 maj-min: 259:8
ID-4: /var/log raw-size: 117.19 GiB size: 117.19 GiB (100.00%)
used: 79.26 GiB (67.6%) fs: btrfs dev: /dev/nvme1n1p5 maj-min: 259:8
ID-5: /var/tmp raw-size: 117.19 GiB size: 117.19 GiB (100.00%)
used: 79.26 GiB (67.6%) fs: btrfs dev: /dev/nvme1n1p5 maj-min: 259:8
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 31.18 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 34.0 C mobo: N/A gpu: nvidia temp: 36 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 33%
Info:
Processes: 405 Uptime: 3h 3m wakeups: 36 Memory: total: 32 GiB
available: 31.18 GiB used: 3.99 GiB (12.8%) Init: systemd v: 253
default: graphical tool: systemctl Compilers: gcc: 13.1.1 clang: 15.0.7
Packages: 1841 pm: pacman pkgs: 1831 libs: 511
tools: gnome-software,octopi,pamac,paru,yay pm: flatpak pkgs: 10 Shell: fish
v: 3.6.1 default: Bash v: 5.1.16 running-in: konsole inxi: 3.3.28
Garuda (2.6.16-1):
System install date:     2023-04-06
Last full system update: 2023-07-19
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       Probably (Run as root to verify)
Failed units:

When I apply the latest list of updates (listed below), my system will reboot and never get past the black screen. I can pick recovery and then restore a snapshot to just prior and I am good to go. I am new to Garuda / Arch linux so not quite sure what to check. I have also included my Boot/Grub line, I have a 2nd video card installed so its set to not use it and leave it for QEMU/Libvirt. Updates for last few months have been just perfect, just something with the recent updats that get applied it never boots to the window manager.

Grub line: rd.driver.pre=vfio-pci intel_iommu=on quiet rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3 options vfio_pci.ids=10de:1c82 pcie_acs_override=downstream,multifunction video=efifb:off iommu=pt # Modified by garuda-migrations: splash

Updates being applied:

abseil-cpp 20230125.3-1 -> 20230125.3-2
alsa-card-profiles 1:0.3.74-1 -> 1:0.3.76-2
ananicy-cpp 1.1.0-1 -> 1.1.0-2
audacity 1:3.3.2-1 -> 1:3.3.3-1
beautyline 1:20230603-1 -> 1:20230729-1
bind 9.18.16-1 -> 9.18.17-1
binutils 2.40-6 -> 2.41-1
bluedevil 1:5.27.6-1 -> 1:5.27.7-1
breeze 5.27.6-1 -> 5.27.7-1
btrfs-progs 6.3.2-1 -> 6.3.3-1
ca-certificates-mozilla 3.91-1 -> 3.92-1
candy-icons-git r1023.f372cc4-1 -> r1033.f78e4e7-1
cmake 3.26.4-1 -> 3.27.1-1
curl 8.1.2-1 -> 8.2.1-1
deepin-calculator 5.8.23-4 -> 5.8.24-1
dracut 059-2 -> 059-3
embree 4.1.0-1 -> 4.2.0-1
exa 0.10.1-7 -> 0.10.1-8
fmt 9.1.0-4 -> 10.0.0-1
fuse-common 3.14.1-1 -> 3.15.1-1
fuse3 3.14.1-1 -> 3.15.1-1
garuda-dr460nized 3.0.4-1 -> 3.0.6-1
gcc 13.1.1-2 -> 13.2.1-2
gcc-libs 13.1.1-2 -> 13.2.1-2
geoip-database 20230519-1 -> 20230719-1
git 2.41.0-1 -> 2.41.0-2
glibc 2.37-3 -> 2.37-4
glslang 12.2.0-1 -> 12.3.1-2
google-chrome 114.0.5735.198-1 -> 115.0.5790.170-1
graphviz 8.0.5-2 -> 8.1.0-1
gspell 1.12.1-2 -> 1.12.2-1
gst-libav 1.22.4-2 -> 1.22.5-1
gst-plugin-pipewire 1:0.3.74-1 -> 1:0.3.76-2
gst-plugins-bad 1.22.4-2 -> 1.22.5-1
gst-plugins-bad-libs 1.22.4-2 -> 1.22.5-1
gst-plugins-base 1.22.4-2 -> 1.22.5-1
gst-plugins-base-libs 1.22.4-2 -> 1.22.5-1
gst-plugins-good 1.22.4-2 -> 1.22.5-1
gst-plugins-ugly 1.22.4-2 -> 1.22.5-1
gstreamer 1.22.4-2 -> 1.22.5-1
gstreamer-vaapi 1.22.4-2 -> 1.22.5-1
gupnp 1:1.6.4-1 -> 1:1.6.5-1
helvum 0.3.4-1 -> 0.4.0-1
highway 1.0.4-1 -> 1.0.5-1
hwinfo 23.1-1 -> 23.2-1
imagemagick 7.1.1.13-1 -> 7.1.1.15-1
inkscape 1.2.2-10 -> 1.3-2
jre-openjdk 20.0.1.u9-3 -> 20.0.2.u9-3
jre-openjdk-headless 20.0.1.u9-3 -> 20.0.2.u9-3
kactivitymanagerd 5.27.6-1 -> 5.27.7-1
kde-cli-tools 5.27.6-1 -> 5.27.7-1
kde-gtk-config 5.27.6-1 -> 5.27.7-1
kdecoration 5.27.6-1 -> 5.27.7-1
kdeplasma-addons 5.27.6-2 -> 5.27.7-1
khotkeys 5.27.6-1 -> 5.27.7-1
kinfocenter 5.27.6-1 -> 5.27.7-1
kirigami-addons 0.9.0-1 -> 0.10.0-1
kmenuedit 5.27.6-1 -> 5.27.7-1
kpipewire 5.27.6-1 -> 5.27.7-1
kscreen 5.27.6-1 -> 5.27.7-1
kscreenlocker 5.27.6-1 -> 5.27.7-1
ksshaskpass 5.27.6-1 -> 5.27.7-1
ksystemstats 5.27.6-1 -> 5.27.7-1
ktextaddons 1.3.2-1 -> 1.4.0-1
kwallet 5.108.0-1 -> 5.108.0-2
kwallet-pam 5.27.6-1 -> 5.27.7-1
kwayland-integration 5.27.6-1 -> 5.27.7-1
kwin 5.27.6-1 -> 5.27.7-1
layer-shell-qt 5.27.6-1 -> 5.27.7-1
lensfun 1:0.3.4-2 -> 1:0.3.4-3
lib32-curl 8.1.2-1 -> 8.2.1-1
lib32-gcc-libs 13.1.1-2 -> 13.2.1-2
lib32-glibc 2.37-3 -> 2.37-4
lib32-libcurl-compat 8.1.2-1 -> 8.2.1-1
lib32-libcurl-gnutls 8.1.2-1 -> 8.2.1-1
lib32-libpipewire 1:0.3.74-1 -> 1:0.3.76-1
lib32-libva 2.18.0-1 -> 2.19.0-1
lib32-mesa 23.1.3-1 -> 23.1.4-2
lib32-nss 3.91-1 -> 3.92-1
lib32-openssl 1:3.1.1-1 -> 1:3.1.2-1
lib32-openssl-1.1 1.1.1.u-1 -> 1.1.1.v-1
lib32-pipewire 1:0.3.74-1 -> 1:0.3.76-1
lib32-pipewire-jack 1:0.3.74-1 -> 1:0.3.76-1
lib32-systemd 253.6-1 -> 254-1
libarchive 3.6.2-2 -> 3.7.1-1
libbpf 1.2.0-1 -> 1.2.2-1
libcamera 0.0.5-1 -> 0.1.0-1
libcamera-ipa 0.0.5-1 -> 0.1.0-1
libcurl-compat 8.1.2-1 -> 8.2.1-1
libcurl-gnutls 8.1.2-1 -> 8.2.1-1
libelf 0.189-1 -> 0.189-2
libgit2 1:1.6.4-1 -> 1:1.7.0-3
libimagequant 4.1.1-1 -> 4.2.0-1
libkscreen 5.27.6-1 -> 5.27.7-1
libksysguard 5.27.6-1 -> 5.27.7-1
libpipewire 1:0.3.74-1 -> 1:0.3.76-2
libplacebo 5.264.1-1 -> 5.264.1-2
libreoffice-fresh 7.5.4-4 -> 7.5.5-1
librsvg 2:2.56.2-1 -> 2:2.56.3-1
libsysprof-capture 3.48.0-2 -> 3.48.0-3
libtool 2.4.7+4+g1ec8fa28-4 -> 2.4.7+4+g1ec8fa28-6
libva-utils 2.18.2-1 -> 2.19.0-1
libvirt 1:9.5.0-1 -> 1:9.6.0-1
libvirt-python 1:9.5.0-1 -> 1:9.6.0-1
libwbclient 4.18.4-1 -> 4.18.5-2
licenses 20220125-2 -> 20230729-1
linux 6.4.4.arch1-1 -> 6.4.7.arch1-2
linux-api-headers 6.3-1 -> 6.4-1
linux-firmware 20230625.ee91452d-4 -> 20230625.ee91452d-5
linux-firmware-whence 20230625.ee91452d-4 -> 20230625.ee91452d-5
linux-headers 6.4.4.arch1-1 -> 6.4.7.arch1-2
linux-zen 6.4.4.zen1-1 -> 6.4.7.zen1-2
linux-zen-headers 6.4.4.zen1-1 -> 6.4.7.zen1-2
lsb-release 2.0.r48.3cf5103-1 -> 2.0.r53.a86f885-1
luajit 2.1.0.beta3.r481.g51fb2f2c-1 -> 2.1.0.beta3.r493.g8635cbab-1
mame 0.256-1 -> 0.257-1
mesa 23.1.3-2 -> 23.1.4-2
meson 1.2.0-2 -> 1.2.0-3
milou 5.27.6-1 -> 5.27.7-1
mpfr 4.2.0.p9-1 -> 4.2.0.p12-2
mpv 1:0.35.1-8 -> 1:0.36.0-1
noto-fonts 1:23.7.1-1 -> 1:23.8.1-1
noto-fonts-cjk 20220126-1 -> 20220126-2
nss 3.91-1 -> 3.92-1
openssh 9.3p1-2 -> 9.3p2-1
openssl 3.1.1-1 -> 3.1.2-1
oxygen-sounds 5.27.6-1 -> 5.27.7-1
perl-file-listing 6.15-2 -> 6.16-1
pipewire 1:0.3.74-1 -> 1:0.3.76-2
pipewire-alsa 1:0.3.74-1 -> 1:0.3.76-2
pipewire-audio 1:0.3.74-1 -> 1:0.3.76-2
pipewire-jack 1:0.3.74-1 -> 1:0.3.76-2
pipewire-pulse 1:0.3.74-1 -> 1:0.3.76-2
pipewire-v4l2 1:0.3.74-1 -> 1:0.3.76-2
pipewire-x11-bell 1:0.3.74-1 -> 1:0.3.76-2
pipewire-zeroconf 1:0.3.74-1 -> 1:0.3.76-2
plasma-browser-integration 5.27.6-1 -> 5.27.7-1
plasma-desktop 5.27.6-1 -> 5.27.7-1
plasma-firewall 5.27.6-1 -> 5.27.7-1
plasma-integration 5.27.6-1 -> 5.27.7-1
plasma-nm 5.27.6-1 -> 5.27.7-1
plasma-pa 5.27.6-1 -> 5.27.7-1
plasma-systemmonitor 5.27.6-1 -> 5.27.7-1
plasma-thunderbolt 5.27.6-1 -> 5.27.7-1
plasma-workspace 5.27.6-2 -> 5.27.7-1
polkit-kde-agent 5.27.6-1 -> 5.27.7-1
postgresql-libs 15.3-2 -> 15.3-4
powerdevil 5.27.6-3 -> 5.27.7-1
proton-ge-custom 2:GE.Proton8.6-8 -> 2:GE.Proton8.8-1
protontricks-git 1.10.3.r2.g0b88463-1 -> 1.10.3.r6.g7a2e3eb-1
python-cairo 1.23.0-6 -> 1.24.0-1
python-chardet 5.1.0-3 -> 5.2.0-1
python-click 8.1.5-1 -> 8.1.6-1
python-fastjsonschema 2.17.1-1 -> 2.18.0-1
python-fonttools 4.41.0-1 -> 4.41.1-1
python-inflect 6.1.0-1 -> 7.0.0-1
python-markdown 3.4.3-2 -> 3.4.4-1
python-pip 23.1.2-1 -> 23.2.1-1
python-pyqt5-sip 12.12.1-2 -> 12.12.2-1
qca-qt5 2.3.6-2 -> 2.3.7-1
qemu-audio-alsa 8.0.2-1 -> 8.0.3-1
qemu-audio-dbus 8.0.2-1 -> 8.0.3-1
qemu-audio-jack 8.0.2-1 -> 8.0.3-1
qemu-audio-oss 8.0.2-1 -> 8.0.3-1
qemu-audio-pa 8.0.2-1 -> 8.0.3-1
qemu-audio-sdl 8.0.2-1 -> 8.0.3-1
qemu-audio-spice 8.0.2-1 -> 8.0.3-1
qemu-block-curl 8.0.2-1 -> 8.0.3-1
qemu-block-dmg 8.0.2-1 -> 8.0.3-1
qemu-block-nfs 8.0.2-1 -> 8.0.3-1
qemu-block-ssh 8.0.2-1 -> 8.0.3-1
qemu-chardev-spice 8.0.2-1 -> 8.0.3-1

qemu-common 8.0.2-1 -> 8.0.3-1
qemu-desktop 8.0.2-1 -> 8.0.3-1
qemu-hw-display-qxl 8.0.2-1 -> 8.0.3-1
qemu-hw-display-virtio-gpu 8.0.2-1 -> 8.0.3-1
qemu-hw-display-virtio-gpu-gl 8.0.2-1 -> 8.0.3-1
qemu-hw-display-virtio-gpu-pci 8.0.2-1 -> 8.0.3-1
qemu-hw-display-virtio-gpu-pci-gl 8.0.2-1 -> 8.0.3-1
qemu-hw-display-virtio-vga 8.0.2-1 -> 8.0.3-1
qemu-hw-display-virtio-vga-gl 8.0.2-1 -> 8.0.3-1
qemu-hw-s390x-virtio-gpu-ccw 8.0.2-1 -> 8.0.3-1
qemu-hw-usb-host 8.0.2-1 -> 8.0.3-1
qemu-hw-usb-redirect 8.0.2-1 -> 8.0.3-1
qemu-hw-usb-smartcard 8.0.2-1 -> 8.0.3-1
qemu-img 8.0.2-1 -> 8.0.3-1
qemu-pr-helper 8.0.2-1 -> 8.0.3-1
qemu-system-x86 8.0.2-1 -> 8.0.3-1
qemu-system-x86-firmware 8.0.2-1 -> 8.0.3-1
qemu-tools 8.0.2-1 -> 8.0.3-1
qemu-ui-curses 8.0.2-1 -> 8.0.3-1
qemu-ui-dbus 8.0.2-1 -> 8.0.3-1
qemu-ui-egl-headless 8.0.2-1 -> 8.0.3-1
qemu-ui-gtk 8.0.2-1 -> 8.0.3-1
qemu-ui-opengl 8.0.2-1 -> 8.0.3-1
qemu-ui-sdl 8.0.2-1 -> 8.0.3-1
qemu-ui-spice-app 8.0.2-1 -> 8.0.3-1
qemu-ui-spice-core 8.0.2-1 -> 8.0.3-1
qemu-vhost-user-gpu 8.0.2-1 -> 8.0.3-1
qt5-base 5.15.10+kde+r135-1 -> 5.15.10+kde+r139-1
qt6-base 6.5.1-5 -> 6.5.2-1
qt6-svg 6.5.1-1 -> 6.5.2-1
qt6-translations 6.5.1-1 -> 6.5.2-1
rate-mirrors 0.16.2-1 -> 0.16.4-1
rubberband 3.2.1-1 -> 3.3.0-1
samba 4.18.4-1 -> 4.18.5-2
sddm-kcm 5.27.6-1 -> 5.27.7-1
shaderc 2023.3-1 -> 2023.4-1
skypeforlinux-stable-bin 8.99.0.403-1 -> 8.100.0.203-2
smbclient 4.18.4-1 -> 4.18.5-2
spdlog 1.11.0-2 -> 1.11.0-3
squashfuse 0.2.0-1 -> 0.4.0-1
starship 1.15.0-1 -> 1.16.0-1
strongswan 5.9.10-1 -> 5.9.11-1
sudo 1.9.14.p2-1 -> 1.9.14.p3-1
systemd 253.6-2 -> 254-1
systemd-libs 253.6-2 -> 254-1
systemd-sysvcompat 253.6-2 -> 254-1
systemsettings 5.27.6-1 -> 5.27.7-1
talloc 2.4.0-3 -> 2.4.1-1
tar 1.34-2 -> 1.35-1
tdb 1.4.8-2 -> 1.4.9-1
tevent 1:0.14.1-2 -> 1:0.15.0-1
thin-provisioning-tools 1.0.4-1 -> 1.0.5-1
thunderbird 115.0-4 -> 115.0.1-1
unrar 1:6.2.8-1 -> 1:6.2.10-1
wayland-protocols 1.31-1 -> 1.32-1
webkit2gtk 2.40.3-1 -> 2.40.5-1
webkit2gtk-4.1 2.40.3-1 -> 2.40.5-1
whois 5.5.17-1 -> 5.5.18-1
wine 8.12-1 -> 8.13-1
xapian-core 1:1.4.22-1 -> 1:1.4.23-1
xdg-desktop-portal-kde 5.27.6-1 -> 5.27.7-1
xfsprogs 6.3.0-2 -> 6.4.0-1
xxhash 0.8.1-4 -> 0.8.2-1
yay 12.1.0-1 -> 12.1.2-1
zoom 5.15.3-1 -> 5.15.5-1
3 Likes

I did remove one of the quiets, no go and tried the same with splash. But included my grub line just in case its something in there I have done.

Yep. With the latest core system won't boot for me either.

Test if there has been a breaking change in the kernel by installing the LTS kernel, which uses a different kernel version.

sudo pacman -S linux-lts linux-lts-headers

When you are booting up, you can select an alternate kernel from the advanced options in the Grub menu.

5 Likes

When booting try using a snapshot

Ill Try this, I was able to get back in picking a differnt kernel and then restoring a snapshot. I just do not dare update at this point. I will give your suggestion a try in a few days once I get caught up on some work here. Thank you!

1 Like

The LTS Kernel appears to work and is almost instant on. It's a little weird once the window manager opens it hangs for about 10 seconds. All is well though even after applying updates. I need to figure out how to get this to be my first option now instead. I dual boot between Garuda and Windows. Id like to make the LTS my top option. I messed with Garauda Boot and didnt see the ability to move items like I could in grub editor.

Use garuda-boot-options

1 Like

Is this the right syntax now in grub line for the VFIO: vfio_pci.ids=10de:1c82,10de:1ad9

Prior to LTS pass thru seemed to work, now I get the following trying to start my VM:

Error starting domain: internal error: QEMU unexpectedly closed the monitor (vm='FMB-LookingGlass-Working'): 2023-08-06T23:34:26.929806Z qemu-system-x86_64: -device {"driver":"vfio-pci","host":"0000:04:00.0","id":"hostdev3","bus":"pci.6","addr":"0x0"}: vfio 0000:04:00.0: group 16 is not viable
Please ensure all devices within the iommu_group are bound to their vfio bus driver.

Yeah thanks, I am in there I only see the option to change "Boot to" but not the order of the list per say. Ill keep pooking around. My Boot To is Windows, which I want to leave as my kids use my PC. But I do want to move Garuda LTS to the top of the list so I dont have to enter a submenu to get to it.

Applied the latest updates after a reinstall and it stops @loading Linux-zen.... Loading Initial Ramdisk...
Let it sit for an hour, go back and restore the snapshot just before the new install wants to do the updates and it works. What tool could I use to install updates but the kernel updates? As of now I am reinstalling one more time, then I am going to stop it from running Updates till I figure out why it all works fine and has for the last 4 months till now.

Check in your BIOS settings to confirm the SATA controller is set to AHCI mode. This has always been our recommendation (see here), however it seems some folks have been able to successfully use the firmware RAID mode up until recently. The latest kernel versions appear to be unable to detect certain types of hard drives when AHCI mode is not enabled.

3 Likes

Thank you, yes I checked that in case the last bios update a few months back flipped it back. It still set to AHCI, been working like a champ love Garuda, just to this latest update. Thank you for the follow-up.

Can we see the journal from this boot? It may be helpful to see what it is getting stuck on.

Sure if I can figure out how to get back in once it updates. Fallback etc doesnt work after updates and it tries to boot. What file do you want? The boot txt in /var/logs?

After the boot fails, grab your USB and boot up the live environment. Use the chroot tool, or use garuda-chroot as described here to get into the non-booting system and from there you can pull up the journal from the failed boot.

An easy way to get the journal uploaded to the forum would be to pipe it to termbin:

journalctl -b -1 | tb

or

journalctl -b -1 | nc termbin.com 9999

Make sure the system is internet connected of course. :wink: Then, just plop the URL right here in the thread so we can take a peek.

3 Likes

Using LTS Kernel boots with no problem.
Seems like we had issues a few months ago wit Zen Kernel after an Update

Journal
https://termbin.com/49vs

This topic was automatically closed after 14 days. New replies are no longer allowed.