Hello all,
I am sorry to open another those “Slow boot after upgrade” topics. But sadly I am at my wits end.
I did perform an upgrade, and after upgrade + reboot my boot time increase to several minutes.
Now the funny, part I tried to restore a snapshot, but the issue prevails…
I did check posts on Garuda Forum as well ARch forum but nothing advised so far helped.
I did check fstab if possible UUID of SWAP didnt changed, as in past I have seen issues due to this. But UUIDs are correct.
lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
zram0 swap 1 zram0 ecdffac9-91a3-4bbd-a449-4eb021431125 [SWAP]
nvme2n1
└─nvme2n1p1 ext4 1.0 Turbo2G 36eac23f-40bb-4e21-b3f0-64c0ef401482 686,7G 57% /run/media/michal/Turbo2G
nvme0n1
├─nvme0n1p1 vfat FAT32 867C-3BE3 298,8M 0% /boot/efi
├─nvme0n1p2 btrfs 188e87a3-2337-4c6e-ade1-1b339f596605 368,5G 14% /var/tmp
│ /var/log
│ /var/cache
│ /home
│ /srv
│ /root
│ /
└─nvme0n1p3 swap 1 swap a90a8268-89a0-4867-a356-12b513ac9663 [SWAP]
nvme1n1
└─nvme1n1p1 ext4 1.0 Turbo1G a25d1702-6eef-4315-ba3a-67d7384e9ca4 869,2G 0% /run/media/michal/Turbo1G
cat /etc/fstab
File: /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=867C-3BE3 /boot/efi vfat defaults,umask=0077 0 2
UUID=188e87a3-2337-4c6e-ade1-1b339f596605 / btrfs subvol=/@,defaults,noatime,compress=zstd 0 0
UUID=188e87a3-2337-4c6e-ade1-1b339f596605 /home btrfs subvol=/@home,defaults,noatime,compress=zstd 0 0
UUID=188e87a3-2337-4c6e-ade1-1b339f596605 /root btrfs subvol=/@root,defaults,noatime,compress=zstd 0 0
UUID=188e87a3-2337-4c6e-ade1-1b339f596605 /srv btrfs subvol=/@srv,defaults,noatime,compress=zstd 0 0
UUID=188e87a3-2337-4c6e-ade1-1b339f596605 /var/cache btrfs subvol=/@cache,defaults,noatime,compress=zstd 0 0
UUID=188e87a3-2337-4c6e-ade1-1b339f596605 /var/log btrfs subvol=/@log,defaults,noatime,compress=zstd 0 0
UUID=188e87a3-2337-4c6e-ade1-1b339f596605 /var/tmp btrfs subvol=/@tmp,defaults,noatime,compress=zstd 0 0
UUID=a90a8268-89a0-4867-a356-12b513ac9663 swap swap defaults 0 0
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
I tried to as well rerun dracut to rebuilt, but that didnt yield any results. I tried as well with other kernels, but still same problem.
When checking system-analyze
λ systemd-analyze blame
2min 7.234s dev-tpmrm0.device
2min 7.234s sys-devices-LNXSYSTM:00-LNXSYBUS:00-MSFT0101:00-tpmrm-tpmrm0.device
2min 7.234s dev-ttyS0.device
2min 7.234s sys-devices-platform-serial8250-serial8250:0-serial8250:0.0-tty-ttyS0.device
2min 7.233s dev-ttyS3.device
2min 7.233s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
2min 7.233s dev-ttyS1.device
2min 7.233s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
2min 7.233s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
2min 7.233s dev-ttyS2.device
2min 7.222s sys-module-fuse.device
2min 7.221s sys-module-configfs.device
2min 7.197s dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_1TB_S5H9NS0R209831V\x2dpart1.device
2min 7.197s dev-disk-by\x2ddiskseq-3\x2dpart1.device
2min 7.197s dev-disk-by\x2did-nvme\x2deui.002538521140e698\x2dpart1.device
2min 7.197s dev-disk-by\x2dpartuuid-851ea200\x2d69aa\x2d45a3\x2da900\x2d7ebf6e6b0eba.device
2min 7.197s sys-devices-pci0000:00-0000:00:03.1-0000:71:00.0-nvme-nvme1-nvme1n1-nvme1n1p1.device
2min 7.197s dev-disk-by\x2dpath-pci\x2d0000:71:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-a25d1702\x2d6eef\x2d4315\x2dba3a\x2d67d7384e9ca4.device
2min 7.197s dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_1TB_S5H9NS0R209831V_1\x2dpart1.device
2min 7.197s dev-disk-by\x2dpath-pci\x2d0000:71:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-1.device
2min 7.197s dev-disk-by\x2duuid-a25d1702\x2d6eef\x2d4315\x2dba3a\x2d67d7384e9ca4.device
2min 7.197s dev-disk-by\x2dpath-pci\x2d0000:71:00.0\x2dnvme\x2d1\x2dpart-by\x2dlabel-Turbo1G.device
2min 7.197s dev-disk-by\x2dpath-pci\x2d0000:71:00.0\x2dnvme\x2d1\x2dpart1.device
2min 7.197s dev-disk-by\x2dpath-pci\x2d0000:71:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-851ea200\x2d69aa\x2d45a3\x2da900\x2d7ebf6e6b0eba.device
2min 7.197s dev-disk-by\x2dlabel-Turbo1G.device
2min 7.197s dev-nvme1n1p1.device
2min 7.195s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2dlabel-Turbo2G.device
2min 7.195s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-a3af50ae\x2d2520\x2d40ca\x2da194\x2d973df2374db3.device
2min 7.195s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-1.device
2min 7.195s dev-disk-by\x2ddiskseq-1\x2dpart1.device
2min 7.195s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_2TB_S7DNNU0X710768T_1\x2dpart1.device
2min 7.195s dev-disk-by\x2did-nvme\x2deui.0025384741a02a0e\x2dpart1.device
2min 7.195s dev-nvme2n1p1.device
2min 7.195s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_2TB_S7DNNU0X710768T\x2dpart1.device
2min 7.195s dev-disk-by\x2dpartuuid-a3af50ae\x2d2520\x2d40ca\x2da194\x2d973df2374db3.device
2min 7.195s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-36eac23f\x2d40bb\x2d4e21\x2db3f0\x2d64c0ef401482.device
2min 7.195s dev-disk-by\x2duuid-36eac23f\x2d40bb\x2d4e21\x2db3f0\x2d64c0ef401482.device
2min 7.195s dev-disk-by\x2dlabel-Turbo2G.device
2min 7.195s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart1.device
2min 7.195s sys-devices-pci0000:00-0000:00:01.2-0000:02:00.0-nvme-nvme2-nvme2n1-nvme2n1p1.device
2min 7.180s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_2TB_S7DNNU0X710768T_1.device
2min 7.180s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1.device
2min 7.180s dev-disk-by\x2did-nvme\x2deui.0025384741a02a0e.device
2min 7.180s dev-disk-by\x2ddiskseq-1.device
2min 7.180s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_2TB_S7DNNU0X710768T.device
2min 7.180s sys-devices-pci0000:00-0000:00:01.2-0000:02:00.0-nvme-nvme2-nvme2n1.device
2min 7.180s dev-nvme2n1.device
2min 7.179s dev-nvme1n1.device
2min 7.179s dev-disk-by\x2dpath-pci\x2d0000:71:00.0\x2dnvme\x2d1.device
2min 7.179s dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_1TB_S5H9NS0R209831V.device
2min 7.179s dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_1TB_S5H9NS0R209831V_1.device
2min 7.179s sys-devices-pci0000:00-0000:00:03.1-0000:71:00.0-nvme-nvme1-nvme1n1.device
2min 7.179s dev-disk-by\x2did-nvme\x2deui.002538521140e698.device
2min 7.179s dev-disk-by\x2ddiskseq-3.device
2min 3.672s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-8f34d6ef\x2dffdf\x2d4019\x2dbcbf\x2d410834344c64.device
2min 3.672s dev-disk-by\x2dpartlabel-root.device
2min 3.672s dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_500GB_S5H7NS1N501632Z\x2dpart2.device
2min 3.672s dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_500GB_S5H7NS1N501632Z_1\x2dpart2.device
2min 3.672s dev-disk-by\x2dpartuuid-8f34d6ef\x2dffdf\x2d4019\x2dbcbf\x2d410834344c64.device
2min 3.672s sys-devices-pci0000:00-0000:00:02.1-0000:03:00.0-0000:04:08.0-0000:0a:00.0-nvme-nvme0-nvme0n1-nvme0n1p2.device
2min 3.672s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-188e87a3\x2d2337\x2d4c6e\x2dade1\x2d1b339f596605.device
2min 3.672s dev-disk-by\x2did-nvme\x2deui.002538550142a19f\x2dpart2.device
2min 3.672s dev-nvme0n1p2.device
2min 3.672s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-2.device
2min 3.672s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartlabel-root.device
2min 3.672s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2dnvme\x2d1\x2dpart2.device
2min 3.672s dev-disk-by\x2ddiskseq-2\x2dpart2.device
2min 3.672s dev-disk-by\x2duuid-188e87a3\x2d2337\x2d4c6e\x2dade1\x2d1b339f596605.device
2min 3.668s dev-disk-by\x2did-nvme\x2deui.002538550142a19f\x2dpart1.device
2min 3.668s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2dnvme\x2d1\x2dpart1.device
2min 3.668s sys-devices-pci0000:00-0000:00:02.1-0000:03:00.0-0000:04:08.0-0000:0a:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
2min 3.668s dev-disk-by\x2dpartuuid-b39617fa\x2d23a6\x2d4809\x2dae2b\x2df220502f3bbf.device
2min 3.668s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-1.device
2min 3.668s dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_500GB_S5H7NS1N501632Z\x2dpart1.device
2min 3.668s dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_500GB_S5H7NS1N501632Z_1\x2dpart1.device
2min 3.668s dev-disk-by\x2ddiskseq-2\x2dpart1.device
2min 3.668s dev-nvme0n1p1.device
2min 3.668s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-b39617fa\x2d23a6\x2d4809\x2dae2b\x2df220502f3bbf.device
2min 3.668s dev-disk-by\x2duuid-867C\x2d3BE3.device
2min 3.668s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-867C\x2d3BE3.device
2min 3.659s dev-disk-by\x2dpartuuid-247a645f\x2d9cbd\x2d4a57\x2d926c\x2d1d903cf63b83.device
2min 3.659s dev-disk-by\x2dlabel-swap.device
2min 3.659s dev-disk-by\x2ddiskseq-2\x2dpart3.device
2min 3.659s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-247a645f\x2d9cbd\x2d4a57\x2d926c\x2d1d903cf63b83.device
2min 3.659s dev-disk-by\x2did-nvme\x2deui.002538550142a19f\x2dpart3.device
2min 3.659s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2dnvme\x2d1\x2dpart3.device
2min 3.659s dev-disk-by\x2duuid-a90a8268\x2d89a0\x2d4867\x2da356\x2d12b513ac9663.device
2min 3.659s sys-devices-pci0000:00-0000:00:02.1-0000:03:00.0-0000:04:08.0-0000:0a:00.0-nvme-nvme0-nvme0n1-nvme0n1p3.device
2min 3.659s dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_500GB_S5H7NS1N501632Z_1\x2dpart3.device
2min 3.659s dev-nvme0n1p3.device
2min 3.659s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2dnvme\x2d1\x2dpart-by\x2dlabel-swap.device
2min 3.659s dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_500GB_S5H7NS1N501632Z\x2dpart3.device
2min 3.659s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-a90a8268\x2d89a0\x2d4867\x2da356\x2d12b513ac9663.device
2min 3.659s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-3.device
2min 3.650s sys-devices-pci0000:00-0000:00:02.1-0000:03:00.0-0000:04:08.0-0000:0a:00.0-nvme-nvme0-nvme0n1.device
2min 3.650s dev-disk-by\x2did-nvme\x2deui.002538550142a19f.device
2min 3.650s dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_500GB_S5H7NS1N501632Z.device
2min 3.650s dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_500GB_S5H7NS1N501632Z_1.device
2min 3.650s dev-nvme0n1.device
2min 3.650s dev-disk-by\x2ddiskseq-2.device
2min 3.650s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2dnvme\x2d1.device
1.017s systemd-binfmt.service
641ms NetworkManager.service
457ms linux-modules-cleanup.service
371ms systemd-tmpfiles-setup.service
275ms initrd-switch-root.service
128ms systemd-journal-flush.service
101ms user@1000.service
96ms udisks2.service
91ms lvm2-monitor.service
89ms upower.service
88ms dev-zram0.swap
80ms systemd-oomd.service
69ms systemd-udev-trigger.service
68ms dracut-pre-udev.service
68ms systemd-tmpfiles-setup-dev-early.service
51ms systemd-remount-fs.service
42ms systemd-journald.service
42ms systemd-vconsole-setup.service
42ms systemd-userdbd.service
37ms systemd-zram-setup@zram0.service
36ms power-profiles-daemon.service
30ms virtlogd.service
28ms ModemManager.service
27ms polkit.service
27ms systemd-udevd.service
27ms systemd-update-utmp.service
25ms systemd-hostnamed.service
25ms systemd-random-seed.service
25ms systemd-rfkill.service
24ms initrd-udevadm-cleanup-db.service
23ms dev-hugepages.mount
23ms dev-mqueue.mount
23ms sys-kernel-debug.mount
23ms libvirtd.service
22ms sys-kernel-tracing.mount
22ms kmod-static-nodes.service
22ms bluetooth.service
22ms systemd-hibernate-resume.service
22ms user-runtime-dir@1000.service
22ms modprobe@dm_mod.service
21ms modprobe@loop.service
19ms systemd-logind.service
18ms proc-sys-fs-binfmt_misc.mount
17ms systemd-modules-load.service
17ms dbus-broker.service
17ms avahi-daemon.service
16ms rtkit-daemon.service
15ms systemd-udev-load-credentials.service
14ms systemd-user-sessions.service
13ms modprobe@configfs.service
13ms modprobe@fuse.service
13ms sys-fs-fuse-connections.mount
12ms systemd-fsck@dev-disk-by\x2duuid-867C\x2d3BE3.service
12ms dracut-cmdline.service
12ms systemd-timesyncd.service
11ms bolt.service
10ms dev-disk-by\x2duuid-a90a8268\x2d89a0\x2d4867\x2da356\x2d12b513ac9663.swap
8ms lm_sensors.service
7ms boot-efi.mount
7ms systemd-machined.service
6ms initrd-cleanup.service
6ms systemd-tmpfiles-setup-dev.service
6ms systemd-fsck-root.service
6ms dracut-pre-pivot.service
5ms initrd-parse-etc.service
4ms dracut-shutdown.service
4ms garuda-pacman-lock.service
4ms modprobe@drm.service
3ms systemd-sysctl.service
3ms home.mount
2ms root.mount
2ms srv.mount
2ms var-log.mount
2ms tmp.mount
2ms var-tmp.mount
2ms var-cache.mount
systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @2.898s
└─multi-user.target @2.898s
└─libvirtd.service @2.875s +23ms
└─network.target @2.874s
└─NetworkManager.service @2.232s +641ms
└─basic.target @2.231s
└─dbus-broker.service @2.212s +17ms
└─dbus.socket @2.211s
└─sysinit.target @2.210s
└─systemd-binfmt.service @1.193s +1.017s
└─proc-sys-fs-binfmt_misc.mount @2.177s +18ms
└─proc-sys-fs-binfmt_misc.automount @178ms
I see this and I thought maybe something with NVME disk.
2min 3.650s sys-devices-pci0000:00-0000:00:02.1-0000:03:00.0-0000:04:08.0-0000:0a:00.0-nvme-nvme0-nvme0n1.device
2min 3.650s dev-disk-by\x2did-nvme\x2deui.002538550142a19f.device
2min 3.650s dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_500GB_S5H7NS1N501632Z.device
2min 3.650s dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_500GB_S5H7NS1N501632Z_1.device
2min 3.650s dev-nvme0n1.device
2min 3.650s dev-disk-by\x2ddiskseq-2.device
2min 3.650s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2dnvme\x2d1.device
1.017s systemd-binfmt.service
But NVME is OK (I think), I did run a new smart test and no errors
sudo smartctl -a /dev/nvme0
[sudo] password for michal:
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.13.1-zen1-1-zen] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: Samsung SSD 970 EVO 500GB
Serial Number: S5H7NS1N501632Z
Firmware Version: 2B2QEXE7
PCI Vendor/Subsystem ID: 0x144d
IEEE OUI Identifier: 0x002538
Total NVM Capacity: 500 107 862 016 [500 GB]
Unallocated NVM Capacity: 0
Controller ID: 4
NVMe Version: 1.3
Number of Namespaces: 1
Namespace 1 Size/Capacity: 500 107 862 016 [500 GB]
Namespace 1 Utilization: 69 247 254 528 [69,2 GB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: 002538 550142a19f
Local Time is: Tue Feb 4 15:04:58 2025 CET
Firmware Updates (0x16): 3 Slots, no Reset required
Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test
Optional NVM Commands (0x005f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp
Log Page Attributes (0x03): S/H_per_NS Cmd_Eff_Lg
Maximum Data Transfer Size: 512 Pages
Warning Comp. Temp. Threshold: 85 Celsius
Critical Comp. Temp. Threshold: 85 Celsius
Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 6.20W - - 0 0 0 0 0 0
1 + 4.30W - - 1 1 1 1 0 0
2 + 2.10W - - 2 2 2 2 0 0
3 - 0.0400W - - 3 3 3 3 210 1200
4 - 0.0050W - - 4 4 4 4 2000 8000
Supported LBA Sizes (NSID 0x1)
Id Fmt Data Metadt Rel_Perf
0 + 512 0 0
=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
SMART/Health Information (NVMe Log 0x02)
Critical Warning: 0x00
Temperature: 33 Celsius
Available Spare: 100%
Available Spare Threshold: 10%
Percentage Used: 0%
Data Units Read: 15 320 489 [7,84 TB]
Data Units Written: 6 200 549 [3,17 TB]
Host Read Commands: 91 775 201
Host Write Commands: 73 785 834
Controller Busy Time: 158
Power Cycles: 2 151
Power On Hours: 1 154
Unsafe Shutdowns: 44
Media and Data Integrity Errors: 0
Error Information Log Entries: 8 594
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Temperature Sensor 1: 33 Celsius
Temperature Sensor 2: 40 Celsius
Error Information (NVMe Log 0x01, 16 of 64 entries)
Num ErrCount SQId CmdId Status PELoc LBA NSID VS Message
0 8594 0 0x000c 0x4004 - 0 0 - Invalid Field in Command
Self-test Log (NVMe Log 0x06)
Self-test status: No self-test in progress
Num Test_Description Status Power_on_Hours Failing_LBA NSID Seg SCT Code
0 Extended Completed without error 1153 - - - - -
1 Extended Completed without error 1126 - - - - -
2 Short Completed without error 105 - - - - -
System:
Kernel: 6.13.1-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=188e87a3-2337-4c6e-ade1-1b339f596605 rw rootflags=subvol=@
quiet resume=UUID=a90a8268-89a0-4867-a356-12b513ac9663 loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.2.5 tk: Qt v: N/A info: frameworks v: 6.10.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop Mobo: Micro-Star model: MAG X870 TOMAHAWK WIFI (MS-7E51)
v: 1.0 serial: <superuser required> uuid: <superuser required> UEFI: American
Megatrends LLC. v: 1.A1A date: 11/21/2024
CPU:
Info: model: AMD Ryzen 7 9800X3D bits: 64 type: MT MCP arch: N/A level: v4
note: check family: 0x1A (26) model-id: 0x44 (68) stepping: 0
microcode: 0xB404023
Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 threads: 16 tpc: 2
smt: enabled cache: L1: 640 KiB desc: d-8x48 KiB; i-8x32 KiB L2: 8 MiB
desc: 8x1024 KiB L3: 96 MiB desc: 1x96 MiB
Speed (MHz): avg: 2983 min/max: 600/5269 boost: enabled scaling:
driver: amd-pstate-epp governor: powersave cores: 1: 2983 2: 2983 3: 2983
4: 2983 5: 2983 6: 2983 7: 2983 8: 2983 9: 2983 10: 2983 11: 2983 12: 2983
13: 2983 14: 2983 15: 2983 16: 2983 bogomips: 150108
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA GA102 [GeForce RTX 3080] vendor: eVga.com. driver: nvidia
v: 570.86.16 alternate: nouveau,nvidia_drm non-free: 550/565.xx+
status: current (as of 2025-01; EOL~2026-12-xx) arch: Ampere code: GAxxx
process: TSMC n7 (7nm) built: 2020-2023 pcie: gen: 4 speed: 16 GT/s
lanes: 16 ports: active: none off: DP-3 empty: DP-1,DP-2,HDMI-A-1
bus-ID: 01:00.0 chip-ID: 10de:2206 class-ID: 0300
Device-2: Advanced Micro Devices [AMD/ATI] Granite Ridge [Radeon Graphics]
vendor: Micro-Star MSI driver: amdgpu v: kernel pcie: gen: 4 speed: 16 GT/s
lanes: 16 ports: active: none empty: DP-4, DP-5, DP-6, HDMI-A-2,
Writeback-1 bus-ID: 72:00.0 chip-ID: 1002:13c0 class-ID: 0300 temp: 35.0 C
Display: wayland server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.4
compositor: kwin_wayland driver: X: loaded: amdgpu,nvidia
unloaded: modesetting,nouveau alternate: fbdev,nv,vesa dri: radeonsi
gpu: nvidia,nvidia-nvswitch display-ID: 0
Monitor-1: DP-3 model: Dell AW3423DWF serial: <filter> built: 2023 res:
mode: 3440x1440 hz: 165 scale: 100% (1) dpi: 109 gamma: 1.2
size: 800x337mm (31.5x13.27") diag: 868mm (34.2") modes: max: 3440x1440
min: 640x480
API: EGL v: 1.5 hw: drv: nvidia drv: amd radeonsi platforms: device: 0
drv: nvidia device: 1 drv: radeonsi gbm: drv: radeonsi surfaceless:
drv: nvidia wayland: drv: nvidia x11: drv: nvidia
API: OpenGL v: 4.6.0 compat-v: 4.6 vendor: nvidia mesa v: 570.86.16
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 3080/PCIe/SSE2
memory: 9.77 GiB display-ID: :1.0
API: Vulkan v: 1.4.303 layers: 15 device: 0 type: discrete-gpu
name: NVIDIA GeForce RTX 3080 driver: N/A device-ID: 10de:2206
surfaces: xcb,xlib,wayland device: 1 type: integrated-gpu name: AMD
Radeon Graphics (RADV RAPHAEL_MENDOCINO) driver: N/A device-ID: 1002:13c0
surfaces: xcb,xlib,wayland device: 2 type: cpu name: llvmpipe (LLVM
19.1.7 256 bits) driver: N/A device-ID: 10005:0000
surfaces: xcb,xlib,wayland
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: corectrl, nvidia-settings,
nvidia-smi wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: NVIDIA GA102 High Definition Audio vendor: eVga.com.
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 01:00.1 chip-ID: 10de:1aef class-ID: 0403
Device-2: Advanced Micro Devices [AMD/ATI] Rembrandt Radeon High
Definition Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel
pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 72:00.1 chip-ID: 1002:1640
class-ID: 0403
Device-3: Advanced Micro Devices [AMD] Family 17h/19h/1ah HD Audio
vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie: gen: 4
speed: 16 GT/s lanes: 16 bus-ID: 72:00.6 chip-ID: 1022:15e3 class-ID: 0403
Device-4: VIA USB Audio Device driver: hid-generic,snd-usb-audio,usbhid
type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-3.3:6
chip-ID: 040d:340a class-ID: 0300
Device-5: Micro Star USB Audio driver: hid-generic,snd-usb-audio,usbhid
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-5:4
chip-ID: 0db0:cd0e class-ID: 0300
API: ALSA v: k6.13.1-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.2.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: Realtek vendor: Micro-Star MSI driver: r8126 v: 10.014.01-NAPI
modules: r8169 pcie: gen: 3 speed: 8 GT/s lanes: 1 port: e000
bus-ID: 08:00.0 chip-ID: 10ec:8126 class-ID: 0200
IF: enp8s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager,systemd-timesyncd
Bluetooth:
Device-1: Foxconn / Hon Hai driver: btusb v: 0.8 type: USB rev: 1.1
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-12:11 chip-ID: 0489:e10a
class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.3
lmp-v: 12 status: discoverable: no pairing: yes class-ID: 6c0104
Drives:
Local Storage: total: 3.18 TiB used: 1.09 TiB (34.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:2 vendor: Samsung model: SSD 970 EVO 500GB
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 2B2QEXE7 temp: 33.9 C
scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:6 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: 26.9 C
scheme: GPT
ID-3: /dev/nvme2n1 maj-min: 259:0 vendor: Samsung model: SSD 990 PRO 2TB
size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 4B2QJXD7 temp: 34.9 C
scheme: GPT
Partition:
ID-1: / raw-size: 432.01 GiB size: 432.01 GiB (100.00%)
used: 61.24 GiB (14.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:4
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 584 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:3
ID-3: /home raw-size: 432.01 GiB size: 432.01 GiB (100.00%)
used: 61.24 GiB (14.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:4
ID-4: /var/log raw-size: 432.01 GiB size: 432.01 GiB (100.00%)
used: 61.24 GiB (14.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:4
ID-5: /var/tmp raw-size: 432.01 GiB size: 432.01 GiB (100.00%)
used: 61.24 GiB (14.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:4
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 30.41 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 16
dev: /dev/zram0
ID-2: swap-2 type: partition size: 33.45 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/nvme0n1p3 maj-min: 259:5
Sensors:
System Temperatures: cpu: 38.6 C mobo: 30.5 C gpu: amdgpu temp: 35.0 C
Fan Speeds (rpm): N/A
Info:
Memory: total: 32 GiB note: est. available: 30.41 GiB used: 4.93 GiB (16.2%)
Processes: 436 Power: uptime: 7m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.1 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1851 libs: 543 tools: octopi,paru Compilers:
clang: 19.1.7 gcc: 14.2.1 Shell: garuda-inxi default: fish v: 3.7.1
running-in: konsole inxi: 3.3.37
Garuda (2.6.26-1.1):
System install date: 2024-12-06
Last full system update: 2025-02-04
Is partially upgraded: No
Relevant software: snapper NetworkManager dracut nvidia-dkms
Windows dual boot: No/Undetected
Failed units:
Does anybody have any ideas what coudl be wrong?
Many thanks in advance as always!
