...here we go again... file or directory not exixsts after update & grub duplicate entries

[Pasqui]

System:
Kernel: 6.12.7-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=142516ae-d002-447e-a9a5-0939a0cf79fa rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.2.4 tk: Qt v: N/A info: frameworks v: 6.9.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: TUF GAMING X570-PLUS (WI-FI) v: Rev X.0x
serial: <superuser required> part-nu: SKU uuid: <superuser required>
UEFI: American Megatrends v: 5013 date: 03/22/2024
CPU:
Info: model: AMD Ryzen 7 5800X bits: 64 type: MT MCP arch: Zen 3+ gen: 3
level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
model-id: 0x21 (33) stepping: 0 microcode: 0xA20102D
Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 threads: 16 tpc: 2
smt: enabled cache: L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB
desc: 8x512 KiB L3: 32 MiB desc: 1x32 MiB
Speed (MHz): avg: 1752 min/max: 550/4851 boost: enabled scaling:
driver: amd-pstate-epp governor: performance cores: 1: 1752 2: 1752 3: 1752
4: 1752 5: 1752 6: 1752 7: 1752 8: 1752 9: 1752 10: 1752 11: 1752 12: 1752
13: 1752 14: 1752 15: 1752 16: 1752 bogomips: 121605
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA AD104 [GeForce RTX 4070 Ti] vendor: ZOTAC driver: nvidia
v: 565.77 alternate: nouveau,nvidia_drm non-free: 550.xx+
status: current (as of 2024-09) arch: Lovelace code: AD1xx
process: TSMC n4 (5nm) built: 2022+ pcie: gen: 2 speed: 5 GT/s lanes: 16
link-max: gen: 4 speed: 16 GT/s ports: active: none off: DP-1,HDMI-A-1
empty: DP-2,DP-3 bus-ID: 0a:00.0 chip-ID: 10de:2782 class-ID: 0300
Device-2: Microdia Dual Mode Camera (8006 VGA) driver: hid-generic,usbhid
type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-2:3
chip-ID: 0c45:8006 class-ID: 0301
Device-3: Sunplus Innovation Aukey-PC-LM1E Camera
driver: snd-usb-audio,uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1
mode: 2.0 bus-ID: 5-1:2 chip-ID: 1bcf:0215 class-ID: 0102
Display: wayland server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.4
compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nvidia d-rect: 4480x2520
display-ID: 0
Monitor-1: DP-1 pos: top-right res: 2560x1440 size: N/A modes: N/A
Monitor-2: HDMI-A-1 pos: bottom-l res: 1920x1080 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia gbm:
drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia x11: drv: nvidia
API: OpenGL v: 4.6.0 vendor: nvidia v: 565.77 glx-v: 1.4
direct-render: yes renderer: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
memory: 11.71 GiB display-ID: :1.0
API: Vulkan v: 1.4.303 layers: 5 device: 0 type: discrete-gpu name: NVIDIA
GeForce RTX 4070 Ti driver: N/A device-ID: 10de:2782
surfaces: xcb,xlib,wayland
Audio:
Device-1: NVIDIA AD104 High Definition Audio vendor: ZOTAC
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 0a:00.1 chip-ID: 10de:22bc class-ID: 0403
Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
lanes: 16 bus-ID: 0c:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-3: Sunplus Innovation Aukey-PC-LM1E Camera
driver: snd-usb-audio,uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1
mode: 2.0 bus-ID: 5-1:2 chip-ID: 1bcf:0215 class-ID: 0102
API: ALSA v: k6.12.7-zen1-1-zen status: kernel-api 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: Intel Wi-Fi 5 Wireless-AC 9x6x [Thunder Peak] driver: iwlwifi
v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 05:00.0
chip-ID: 8086:2526 class-ID: 0280
IF: wlp5s0 state: down mac: <filter>
Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: f000 bus-ID: 06:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Intel Wireless-AC 9260 Bluetooth Adapter driver: btusb v: 0.8
type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-5:2
chip-ID: 8087:0025 class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
rfk-block: hardware: no software: no address: <filter> bt-v: 5.1 lmp-v: 10
status: discoverable: no pairing: no
Drives:
Local Storage: total: 10.01 TiB used: 153.19 GiB (1.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:3 vendor: Smart Modular Tech.
model: SHPP41-1000GM size: 931.51 GiB block-size: physical: 512 B
logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 51060A20 temp: 42.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Sabrent model: Rocket Q
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: RKT30Q.2 temp: 28.9 C
scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: Seagate model: ST4000DM004-2CV104
size: 3.64 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 5425 serial: <filter> fw-rev: 0001 scheme: GPT
ID-4: /dev/sdb maj-min: 8:16 vendor: SanDisk model: SSD PLUS 1000GB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 04RL scheme: GPT
ID-5: /dev/sdc maj-min: 8:32 vendor: Western Digital
model: WD40EFRX-68WT0N0 size: 3.64 TiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 5400 serial: <filter>
fw-rev: 0A82 scheme: GPT
Partition:
ID-1: / raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 153.19 GiB (16.5%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 588 KiB (0.2%) fs: vfat dev: /dev/nvme1n1p1 maj-min: 259:1
ID-3: /home raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 153.19 GiB (16.5%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 153.19 GiB (16.5%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 153.19 GiB (16.5%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 31.25 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 16
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 49.9 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 32 GiB available: 31.25 GiB used: 3 GiB (9.6%)
Processes: 341 Power: uptime: 13m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.45 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1535 libs: 419 tools: paru Compilers:
gcc: 14.2.1 Shell: garuda-inxi default: fish v: 3.7.1 running-in: konsole
inxi: 3.3.36
Garuda (2.6.26-1):
System install date:     2024-12-03
Last full system update: 2024-12-29
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       Probably (Run as root to verify)
Failed units:

after recent update, dkms status give me:

find: ‘/usr/lib/modules/6.12.1-zen1-1-zen/’: File o directory non esistente
find: ‘/usr/lib/modules/6.12.1-zen1-1-zen/’: File o directory non esistente
find: ‘/usr/lib/modules/6.12.1-zen1-1-zen/’: File o directory non esistente
find: ‘/usr/lib/modules/6.12.4-zen1-1-zen/’: File o directory non esistente
find: ‘/usr/lib/modules/6.12.4-zen1-1-zen/’: File o directory non esistente
find: ‘/usr/lib/modules/6.12.4-zen1-1-zen/’: File o directory non esistente
nvidia/565.77, 6.12.7-zen1-1-zen, x86_64: installed
vboxhost/7.1.4_OSE, 6.12.4-zen1-1-zen, x86_64: builtfind: ‘/usr/lib/modules/6.12.4-zen1-1-zen/’: File o directory non esis
tente
find: ‘/usr/lib/modules/6.12.4-zen1-1-zen/’: File o directory non esistente
find: ‘/usr/lib/modules/6.12.4-zen1-1-zen/’: File o directory non esistente
(Built modules are missing in the kernel modules folder)
vboxhost/7.1.4_OSE, 6.12.7-zen1-1-zen, x86_64: installed

…why?

[Yada]

Just a hunch, can you reinstall linux-zen and linux-zen-headers. The problem I suspect may be due to the use of virtualbox. This is just a hunch, if you hae switched kernel and the same problem doesn’t arise then I might be somehow right.

[Pasqui]

Pacchetto (2)            Vecchia versione  Nuova versione  Variazione netta

extra/linux-zen          6.12.7.zen1-1     6.12.7.zen1-1           0,00 MiB
extra/linux-zen-headers  6.12.7.zen1-1     6.12.7.zen1-1           0,00 MiB

Dimensione totale dei pacchetti da installare:  280,47 MiB
Dimensione netta dell'aggiornamento:              0,00 MiB

:: Vuoi procedere con l'installazione? [S/n]
(2/2) verifica delle chiavi presenti nel portachiavi                      [-----------------------------------------] 100%
(2/2) verifica dell'integrità dei pacchetti                               [-----------------------------------------] 100%
(2/2) caricamento dei file dei pacchetti                                  [-----------------------------------------] 100%
(2/2) controllo dei conflitti in corso                                    [-----------------------------------------] 100%
(2/2) controllo dello spazio disponibile sul disco                        [-----------------------------------------] 100%
:: Esecuzione degli hook di pre-transazione...
(1/4) Rejecting pacman transaction if running in snapshot...
(2/4) Performing snapper pre snapshots for the following configurations...
==> root: 183
(3/4) Saving Linux kernel modules...
(4/4) Remove upgraded DKMS modules
==> dkms remove --no-depmod nvidia/565.77 -k 6.12.7-zen1-1-zen
==> dkms remove --no-depmod vboxhost/7.1.4_OSE -k 6.12.7-zen1-1-zen
:: Elaborazione delle modifiche al pacchetto...
(1/2) reinstallazione linux-zen                                           [-----------------------------------------] 100%
(2/2) reinstallazione linux-zen-headers                                   [-----------------------------------------] 100%
:: Esecuzione degli hook di post-transazione...
( 1/11) Restoring Linux kernel modules...
++ uname -r
+ KVER=6.12.7-zen1-1-zen
+ test -e /usr/lib/modules/backup/6.12.7-zen1-1-zen
+ rsync -AHXal --ignore-existing /usr/lib/modules/backup/6.12.7-zen1-1-zen /usr/lib/modules/
+ rm -rf /usr/lib/modules/backup
( 2/11) Arming ConditionNeedsUpdate...
( 3/11) Updating module dependencies...
( 4/11) Install DKMS modules
**==> dkms install --no-depmod vboxhost/7.1.4_OSE -k 6.12.7-zen1-1-zen**
**Module /usr/lib/modules/6.12.7-zen1-1-zen/updates/dkms/vboxdrv.ko.zst already installed at version 7.1.4, override by specifying --force**
**Module /usr/lib/modules/6.12.7-zen1-1-zen/updates/dkms/vboxnetflt.ko.zst already installed at version 7.1.4, override by specifying --force**
**Module /usr/lib/modules/6.12.7-zen1-1-zen/updates/dkms/vboxnetadp.ko.zst already installed at version 7.1.4, override by specifying --force**

**Error! Installation aborted.**
**==> WARNING: `dkms install --no-depmod vboxhost/7.1.4_OSE -k 6.12.7-zen1-1-zen' exited 6**
**==> dkms install --no-depmod nvidia/565.77 -k 6.12.7-zen1-1-zen**
**Module /usr/lib/modules/6.12.7-zen1-1-zen/updates/dkms/nvidia.ko.zst already installed at version 565.77, override by specifying --force**
**Module /usr/lib/modules/6.12.7-zen1-1-zen/updates/dkms/nvidia-uvm.ko.zst already installed at version 565.77, override by specifying --force**
**Module /usr/lib/modules/6.12.7-zen1-1-zen/updates/dkms/nvidia-modeset.ko.zst already installed at version 565.77, overrideby specifying --force**
**Module /usr/lib/modules/6.12.7-zen1-1-zen/updates/dkms/nvidia-drm.ko.zst already installed at version 565.77, override by specifying --force**
**Module /usr/lib/modules/6.12.7-zen1-1-zen/updates/dkms/nvidia-peermem.ko.zst already installed at version 565.77, overrideby specifying --force**

**Error! Installation aborted.**
**==> WARNING: `dkms install --no-depmod nvidia/565.77 -k 6.12.7-zen1-1-zen' exited 6**
( 5/11) Updating initramfs...
:: Building initramfs for linux-zen (6.12.7-zen1-1-zen)
:: Building fallback initramfs for linux-zen (6.12.7-zen1-1-zen)
( 6/11) Updating linux initcpios...
( 7/11) Foreign/AUR package notification
jdownloader2 latest-21
konsave 2.2.0-4
nextdns 1.43.5-1
winegui 2.6.4-1
xerox-workcentre-6515-6510 5.662.0.0-3
( 8/11) Orphaned package notification...
=> No orphans found.
( 9/11) Checking for .pacnew and .pacsave files...
.pac* files found:
/etc/issue.pacnew
/etc/locale.gen.pacnew
/etc/pacman.conf.pacnew
/etc/makepkg.conf.d/rust.conf.pacnew
/etc/pacman.d/mirrorlist.pacnew
/etc/updatedb.conf.pacsave
Please check and merge
(10/11) Performing snapper post snapshots for the following configurations...
==> root: 184
(11/11) Syncing all file systems...

[Yada]

Do you have a backup kernel like linux-lts?
You could purge linux-zen whle using the lts kernel then reinstall zen from there.

or maybe wait for a more professional opinion from amazing people on here.

[Pasqui]

no, I already checked and I don’t have a kernel backup

[gampel]

you don´t need a backup…
It was no reboot after kernel / dkms update. (my mind)
Delete all folders from the defunct kernel/virtualbox/dkms stuff.
/var/lib/dkms
/usr/lib/modules/ + /usr/lib/modules/.old/
your active kernel is 6.12.7 not 6.12.4 or 6.12.1
pls always reboot directly after kernel/dkms stuff and never install something after these kind of update/install without reboot. First…reboot…all fine ? yes…then install what you need.

[Pasqui]

so, after a restore to a few days ago, I did a “garuda-update remote fix” and the update went smoothly.
The only things (also happened yesterday) are that now the grub menu has duplicate entries and dkms status still sends me:

find: ‘/usr/lib/modules/6.12.1-zen1-1-zen/’: File o directory non esistente
find: ‘/usr/lib/modules/6.12.1-zen1-1-zen/’: File o directory non esistente
find: ‘/usr/lib/modules/6.12.1-zen1-1-zen/’: File o directory non esistente
find: ‘/usr/lib/modules/6.12.4-zen1-1-zen/’: File o directory non esistente
find: ‘/usr/lib/modules/6.12.4-zen1-1-zen/’: File o directory non esistente
find: ‘/usr/lib/modules/6.12.4-zen1-1-zen/’: File o directory non esistente
nvidia/565.77, 6.12.7-zen1-1-zen, x86_64: installed
vboxhost/7.1.4_OSE, 6.12.4-zen1-1-zen, x86_64: builtfind: ‘/usr/lib/modules/6.12.4-zen1-1-zen/’: File o directory non esis
tente
find: ‘/usr/lib/modules/6.12.4-zen1-1-zen/’: File o directory non esistente
find: ‘/usr/lib/modules/6.12.4-zen1-1-zen/’: File o directory non esistente
(Built modules are missing in the kernel modules folder)
vboxhost/7.1.4_OSE, 6.12.7-zen1-1-zen, x86_64: installed

edit: delete the offending old kernel folders… now only the problem with grub remains

[SGS]

Try

sudo update-grub

At last you can try to clean /boot/efi/ with efibootmgr

[Pasqui]

Cleaning the efi would be a temporary thing that would happen again with the next update
In the case of update-grub it doesn’t solve it, not even reinstalling grub.
I was checking the updates this morning and I don’t understand what could have interfered…

[2024-12-30T08:23:32+0100] [ALPM] upgraded ckbcomp (1.232-1 -> 1.233-1)
[2024-12-30T08:23:32+0100] [ALPM] upgraded eza (0.20.13-1 -> 0.20.14-1)
[2024-12-30T08:23:32+0100] [ALPM] upgraded fastfetch (2.32.1-1 -> 2.33.0-1)
[2024-12-30T08:23:32+0100] [ALPM] upgraded icu (75.1-1 -> 75.1-2)
[2024-12-30T08:23:32+0100] [ALPM] upgraded libjpeg-turbo (3.0.4-1 -> 3.1.0-1)
[2024-12-30T08:23:32+0100] [ALPM] upgraded lib32-libjpeg-turbo (3.0.4-2 -> 3.1.0-1)
[2024-12-30T08:23:32+0100] [ALPM] upgraded libtorrent (0.14.0-1 -> 0.15.0-1)
[2024-12-30T08:23:33+0100] [ALPM] upgraded linux-zen (6.12.6.zen1-1 -> 6.12.7.zen1-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded linux-zen-headers (6.12.6.zen1-1 -> 6.12.7.zen1-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded memtest86+ (7.20-1 -> 7.20-2)
[2024-12-30T08:23:35+0100] [ALPM] upgraded pcsclite (2.3.0-1 -> 2.3.1-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded openconnect (1:9.12-2 -> 1:9.12-3)
[2024-12-30T08:23:35+0100] [ALPM] upgraded python-inflect (7.4.0-2 -> 7.5.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded python-peewee (3.17.8-2 -> 3.17.8-3)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-common (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-audio-alsa (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-audio-dbus (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-audio-jack (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-audio-oss (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-audio-pa (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-audio-pipewire (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-audio-sdl (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-ui-opengl (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-ui-spice-core (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-audio-spice (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-img (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-system-x86-firmware (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-system-x86 (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-base (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-block-curl (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-block-dmg (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-block-gluster (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-block-iscsi (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-block-nfs (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-block-ssh (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-chardev-baum (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-chardev-spice (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-hw-display-qxl (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-hw-display-virtio-gpu (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-hw-display-virtio-gpu-gl (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-hw-display-virtio-gpu-pci (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-hw-display-virtio-gpu-pci-gl (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-hw-display-virtio-vga (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-hw-display-virtio-vga-gl (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-hw-usb-host (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-hw-usb-redirect (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-hw-usb-smartcard (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-ui-curses (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-ui-dbus (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-ui-egl-headless (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-ui-gtk (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-ui-sdl (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-ui-spice-app (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-vhost-user-gpu (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-desktop (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-docs (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-system-aarch64 (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-system-alpha-firmware (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-system-alpha (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-system-arm-firmware (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-system-arm (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-system-avr (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-system-hppa-firmware (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-system-hppa (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-system-loongarch64 (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-system-m68k (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-system-microblaze-firmware (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-system-microblaze (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-system-mips (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:35+0100] [ALPM] upgraded qemu-system-or1k (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:36+0100] [ALPM] upgraded qemu-system-ppc-firmware (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:36+0100] [ALPM] upgraded qemu-system-ppc (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:36+0100] [ALPM] upgraded qemu-system-riscv-firmware (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:36+0100] [ALPM] upgraded qemu-system-riscv (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:36+0100] [ALPM] upgraded qemu-system-rx (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:36+0100] [ALPM] upgraded qemu-system-s390x-firmware (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:36+0100] [ALPM] upgraded qemu-system-s390x (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:36+0100] [ALPM] upgraded qemu-system-sh4 (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:36+0100] [ALPM] upgraded qemu-system-sparc-firmware (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:36+0100] [ALPM] upgraded qemu-system-sparc (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:36+0100] [ALPM] upgraded qemu-system-tricore (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:36+0100] [ALPM] upgraded qemu-system-xtensa (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:36+0100] [ALPM] upgraded qemu-user (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:36+0100] [ALPM] upgraded qemu-emulators-full (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:36+0100] [ALPM] upgraded qemu-hw-s390x-virtio-gpu-ccw (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:36+0100] [ALPM] upgraded qemu-pr-helper (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:36+0100] [ALPM] upgraded qemu-tests (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:36+0100] [ALPM] upgraded qemu-tools (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:36+0100] [ALPM] upgraded qemu-vmsr-helper (9.1.2-1 -> 9.2.0-1)
[2024-12-30T08:23:36+0100] [ALPM] upgraded qemu-full (9.1.2-1 -> 9.2.0-1)

[gampel]

what do garuda-update remote fix ?
pls read

Garuda Update

You have restore your system. It´s “normal” then all these updates
and of course your “old” dkms stuff is also there. (my mind)
Delete again the “old” stuff inside dkms folder + /usr/lib/modules,
then run update again → reboot → all fine ?
yes
no …pls post inxi + log file/s
i know, spend time to doing this it´s sometimes. .but if the result is …that make sense and learning by doing is always a good thing.

https://iso.builds.garudalinux.org/iso/garuda/
You use kvm/qemu…download a test iso or what you prefer → install → test what ever you like —> result ok → do it on your real os.
Of course only if it is important to you and you want to invest this time.

[SGS]

@Pasqui

Cleaning the efi would be a temporary thing that would happen again with the next update

I don’t think so, only an OS install write in to /boot/efi, but not a normal system update. Or efibootmgr
Grub use the date from there, IIRC.

Please, post the log from

efibootmgr
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0016,0001,0003,0002,0000,0012,0013,0018,0014,0015,0017
Boot0000* Windows Boot Manager	HD(1,GPT,c9cd2\EFI\Microsoft\Boot\bootmgfw.efi57
Boot0001* Garuda	HD(1,GPT,c9cd2d1b-0589-468f-a38e-8d71c33a7d6a,0x800,0x82000)/\EFI\Garuda\grubx64.efi
Boot0002* kde	HD(1,GPT,c9cd2d1b-0589-468f-a38e-8d71c33a7d6a,0x800,0x82000)/\EFI\kde\grubx64.efi
Boot0003* i3	HD(1,GPT,c9cd2d1b-0589-468f-a38e-8d71c33a7d6a,0x800,0x82000)/\EFI\i3\grubx64.efi
# shortened

[Pasqui]

BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0000,0002,0003,0001,0004,0005
Boot0000* garuda        HD(1,GPT,abf7c7ff-b0ed-4614-8c1c-bd9a1804f51f,0x1000,0x96000)/\EFI\garuda\grubx64.efi
Boot0001* UEFI:CD/DVD Drive     BBS(129,,0x0)
Boot0002* Windows Boot Manager  HD(1,GPT,8b7b9374-8d31-49d2-814a-03dac7d63665,0x800,0xfffc1)/\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI0000424f
Boot0003* UEFI OS       HD(1,GPT,abf7c7ff-b0ed-4614-8c1c-bd9a1804f51f,0x1000,0x96000)/\EFI\BOOT\BOOTX64.EFI0000424f
Boot0004* UEFI:Removable Device BBS(130,,0x0)
Boot0005* UEFI:Network Device   BBS(131,,0x0)

[SGS]

What is the Boot0003 UEFI OS?
The problem with double entry must exist in forum, did you search about?

[gampel]

this is the file /boot/efi/boot/bootx64.efi …from grub for garuda linux
but …efi000xx i never see before, only bootx64.efi.

[Pasqui]

@SGS

What is the Boot0003 UEFI OS?

I think it’s UEFI Firmware Settings
“efibootmgr -D” did nothing by not finding duplicates

I wonder why all sorts of things happen after a simple update (yes, ok, I could blame it on Windows but at the moment I can’t get rid of it for a few reasons) also because I recently reinstalled clean.
These are currently the boot entries:

[gampel]

Disable inside bios the uefi entry UEFI OS → boot in os → run update-grub
reboot
or delete the folder /boot/efi/boot → update-grub → go bios and the uefi entry is history ( choose garuda as first boot entry)
…is also possible

[Pasqui]

The problem is not the UEFI OS entry, it’s the fact that the Garuda and advanced options entries have been duplicated… and all for a simple update in which nothing seems to have been touched

[gampel]

Did you have a previous linux install ? (grub issue)
What´s now with your “problems” dkms/virtualbox ?
M$ + Linux pls turn off fastboot inside bios and M$

• no warm reboot from M$ to Linux (my mind)
  pls post inxi again + if needed the log files

[filo]

@Pasqui

Garuda and advanced options entries have been duplicated

Try this one to exclude your current system partition from the os-prober:

Multiple Garuda boot entries in Grub after update

Meanwhile I found this: Gentoo Forums :: View topic - os-prober creating duplicate entry for main linux system TL;DR a partition can be blacklisted from os-prober so it doesn't show up twice perhaps on EFI there's no need for a GRUB entry, but I don't have EFI and don't know jack about it. edit: posting this just in case someone is still on BIOS booting, my previous comments were due to my misunderstanding that this case is about an EFI boot.

[Pasqui]

Fastboot has always been disabled. dkms doesn’t give me any problems.
@filo
seeing efibootmgr (Boot0000* garuda HD(1,GPT,abf7c7ff-b0ed-4614-8c1c-bd9a1804f51f,0x1000,0x96000)/\EFI\garuda\grubx64.efi) I tried to add “GRUB_OS_PROBER_SKIP_LIST=abf7c7ff-b0ed-4614-8c1c-bd9a1804f51f@/dev/nvme1n1p2” to /etc/default/grub → sudo update-grub → nothing has changed.

System:
Kernel: 6.12.7-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=142516ae-d002-447e-a9a5-0939a0cf79fa rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.2.4 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
Distro: Garuda base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: TUF GAMING X570-PLUS (WI-FI) v: Rev X.0x
serial: <filter> part-nu: SKU uuid: 1fc97934-1057-be38-3a23-c87f54569f7d
UEFI: American Megatrends v: 5013 date: 03/22/2024
CPU:
Info: model: AMD Ryzen 7 5800X socket: AM4 bits: 64 type: MT MCP
arch: Zen 3+ gen: 3 level: v3 note: check built: 2022 process: TSMC n6 (7nm)
family: 0x19 (25) model-id: 0x21 (33) stepping: 0 microcode: 0xA20102D
Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 threads: 16 tpc: 2
smt: enabled cache: L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB
desc: 8x512 KiB L3: 32 MiB desc: 1x32 MiB
Speed (MHz): avg: 3674 min/max: 550/4851 boost: enabled
base/boost: 3800/4850 scaling: driver: amd-pstate-epp governor: performance
volts: 1.1 V ext-clock: 100 MHz cores: 1: 3674 2: 3674 3: 3674 4: 3674
5: 3674 6: 3674 7: 3674 8: 3674 9: 3674 10: 3674 11: 3674 12: 3674
13: 3674 14: 3674 15: 3674 16: 3674 bogomips: 121587
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA AD104 [GeForce RTX 4070 Ti] vendor: ZOTAC driver: nvidia
v: 565.77 alternate: nouveau,nvidia_drm non-free: 550.xx+
status: current (as of 2024-09) arch: Lovelace code: AD1xx
process: TSMC n4 (5nm) built: 2022+ pcie: gen: 4 speed: 16 GT/s lanes: 16
ports: active: none off: DP-1,HDMI-A-1 empty: DP-2,DP-3 bus-ID: 0a:00.0
chip-ID: 10de:2782 class-ID: 0300
Device-2: Microdia Dual Mode Camera (8006 VGA) driver: hid-generic,usbhid
type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-2:3
chip-ID: 0c45:8006 class-ID: 0301
Device-3: Sunplus Innovation Aukey-PC-LM1E Camera
driver: snd-usb-audio,uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1
mode: 2.0 bus-ID: 5-1:2 chip-ID: 1bcf:0215 class-ID: 0102
Display: unspecified server: X.Org v: 24.1.4 with: Xwayland v: 24.1.4
compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nvidia,nvidia-nvswitch
display-ID: :1 screens: 1
Screen-1: 0 s-res: 4480x1440 s-dpi: 96 s-size: 1185x381mm (46.65x15.00")
s-diag: 1245mm (49.01")
Monitor-1: DP-1 note: disabled pos: primary,top-right model: MSI G273Q
serial: <filter> built: 2020 res: 2560x1440 hz: 165 dpi: 109 gamma: 1.2
size: 597x336mm (23.5x13.23") diag: 685mm (27") ratio: 16:9 modes:
max: 2560x1440 min: 640x480
Monitor-2: HDMI-A-1 note: disabled pos: bottom-l model: MSI MAG272C
serial: <filter> built: 2020 res: 1920x1080 hz: 120 dpi: 82 gamma: 1.2
size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes:
max: 1920x1080 min: 640x480
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia gbm:
drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia inactive: wayland
API: OpenGL v: 4.6.0 vendor: nvidia v: 565.77 glx-v: 1.4
direct-render: yes renderer: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
memory: 11.71 GiB
API: Vulkan v: 1.4.303 layers: 1 device: 0 type: discrete-gpu name: NVIDIA
GeForce RTX 4070 Ti driver: N/A device-ID: 10de:2782 surfaces: xcb,xlib
Audio:
Device-1: NVIDIA AD104 High Definition Audio vendor: ZOTAC
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 0a:00.1 chip-ID: 10de:22bc class-ID: 0403
Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
lanes: 16 bus-ID: 0c:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-3: Sunplus Innovation Aukey-PC-LM1E Camera
driver: snd-usb-audio,uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1
mode: 2.0 bus-ID: 5-1:2 chip-ID: 1bcf:0215 class-ID: 0102
API: ALSA v: k6.12.7-zen1-1-zen status: kernel-api tools: N/A
Server-1: PipeWire v: 1.2.7 status: n/a (root, process) 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 Wi-Fi 5 Wireless-AC 9x6x [Thunder Peak] driver: iwlwifi
v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 05:00.0
chip-ID: 8086:2526 class-ID: 0280
IF: wlp5s0 state: down mac: <filter>
Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: f000 bus-ID: 06:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Intel Wireless-AC 9260 Bluetooth Adapter driver: btusb v: 0.8
type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-5:2
chip-ID: 8087:0025 class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
rfk-block: hardware: no software: no address: <filter> bt-v: 5.1 lmp-v: 10
status: discoverable: no pairing: no
Drives:
Local Storage: total: 10.01 TiB used: 156.41 GiB (1.5%)
ID-1: /dev/nvme0n1 maj-min: 259:3 vendor: Smart Modular Tech.
model: SHPP41-1000GM size: 931.51 GiB block-size: physical: 512 B
logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 51060A20 temp: 40.9 C scheme: GPT
SMART: yes health: PASSED on: 60d 19h cycles: 1,267
read-units: 57,923,518 [29.6 TB] written-units: 34,254,308 [17.5 TB]
ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Sabrent model: Rocket Q
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: RKT30Q.2 temp: 27.9 C
scheme: GPT
SMART: yes health: PASSED on: 67d 23h cycles: 2,463
read-units: 37,135,558 [19.0 TB] written-units: 27,650,139 [14.1 TB]
ID-3: /dev/sda maj-min: 8:0 vendor: Seagate model: ST4000DM004-2CV104
family: BarraCuda 3.5 (SMR) size: 3.64 TiB block-size: physical: 4096 B
logical: 512 B sata: 3.1 speed: 6.0 Gb/s tech: HDD rpm: 5425
serial: <filter> fw-rev: 0001 temp: 29 C scheme: GPT
SMART: yes state: enabled health: PASSED on: 2822h+32m+49.418s
cycles: 2587 read: 10.18 TiB written: 10.87 TiB Pre-Fail:
attribute: Spin_Retry_Count value: 100 worst: 100 threshold: 97
ID-4: /dev/sdb maj-min: 8:16 vendor: SanDisk model: SSD PLUS 1000GB
family: Marvell based SSDs size: 931.51 GiB block-size: physical: 512 B
logical: 512 B sata: 3.2 speed: 6.0 Gb/s tech: SSD serial: <filter>
fw-rev: 04RL temp: 25 C scheme: GPT
SMART: yes state: enabled health: PASSED on: 55d 1h cycles: 2223
ID-5: /dev/sdc maj-min: 8:32 vendor: Western Digital
model: WD40EFRX-68WT0N0 family: Red size: 3.64 TiB block-size:
physical: 4096 B logical: 512 B sata: 3.0 speed: 6.0 Gb/s tech: HDD
rpm: 5400 serial: <filter> fw-rev: 0A82 temp: 28 C scheme: GPT
SMART: yes state: enabled health: PASSED on: 78d 12h cycles: 1517
Partition:
ID-1: / raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 156.41 GiB (16.8%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p2
maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 588 KiB (0.2%) fs: vfat block-size: 512 B dev: /dev/nvme1n1p1
maj-min: 259:1
ID-3: /home raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 156.41 GiB (16.8%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p2
maj-min: 259:2
ID-4: /var/log raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 156.41 GiB (16.8%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p2
maj-min: 259:2
ID-5: /var/tmp raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 156.41 GiB (16.8%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p2
maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 31.25 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 16
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 47.6 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 32 GiB available: 31.25 GiB used: 3.55 GiB (11.4%)
Processes: 416 Power: uptime: 5m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.45 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1538 libs: 421 tools: paru Compilers:
gcc: 14.2.1 Shell: garuda-inxi (sudo) default: Bash v: 5.2.37
running-in: konsole inxi: 3.3.36
Garuda (2.6.26-1):
System install date:     2024-12-03
Last full system update: 2024-12-30
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       Yes
Failed units: