System:
Kernel: 6.12.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=98bd4f25-5b18-4300-8978-e64842768c50 rw rootflags=subvol=@
quiet loglevel=0 ibt=off
Desktop: KDE Plasma v: 6.2.4 tk: Qt v: N/A info: frameworks v: 6.8.0
wm: kwin_x11 tools: avail: lxlock vt: 2 dm: SDDM Distro: Garuda
base: Arch Linux
Machine:
Type: Desktop System: ASRock product: Z790 LiveMixer v: N/A
serial: <superuser required>
Mobo: ASRock model: Z790 LiveMixer serial: <superuser required>
uuid: <superuser required> UEFI: American Megatrends LLC. v: 13.02
date: 12/29/2023
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M275/M280
serial: <filter> charge: 5% (should be ignored) rechargeable: yes
status: discharging
CPU:
Info: model: 13th Gen Intel Core i9-13900KF bits: 64 type: MST AMCP
arch: Raptor Lake gen: core 13 level: v3 note: check built: 2022+
process: Intel 7 (10nm) family: 6 model-id: 0xB7 (183) stepping: 1
microcode: 0x12B
Topology: cpus: 1x dies: 1 clusters: 12 cores: 24 threads: 32 mt: 8 tpc: 2
st: 16 smt: enabled cache: L1: 2.1 MiB desc: d-16x32 KiB, 8x48 KiB; i-8x32
KiB, 16x64 KiB L2: 32 MiB desc: 8x2 MiB, 4x4 MiB L3: 36 MiB desc: 1x36 MiB
Speed (MHz): avg: 800 min/max: 800/5800:4600 scaling: driver: intel_pstate
governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800
8: 800 9: 800 10: 800 11: 800 12: 800 13: 800 14: 800 15: 800 16: 800
17: 800 18: 800 19: 800 20: 800 21: 800 22: 800 23: 800 24: 800 25: 800
26: 800 27: 800 28: 800 29: 800 30: 800 31: 800 32: 800 bogomips: 191692
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA AD103 [GeForce RTX 4080] vendor: Gigabyte driver: nvidia
v: 565.57.01 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: 8
link-max: lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:2704 class-ID: 0300
Display: x11 server: X.Org v: 21.1.14 with: Xwayland v: 24.1.4
compositor: kwin_x11 driver: X: loaded: N/A failed: nvidia gpu: nvidia
display-ID: :0 screens: 1
Screen-1: 0 s-res: 3840x2160 s-dpi: 139 s-size: 702x392mm (27.64x15.43")
s-diag: 804mm (31.65")
Monitor-1: Unknown-1 mapped: HDMI-0 res: 3840x2160 dpi: 139
size: 700x390mm (27.56x15.35") modes: 1024x768
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast gbm: drv: kms_swrast surfaceless: drv: nvidia x11: drv: nvidia
inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 565.57.01
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 4080/PCIe/SSE2
memory: 15.62 GiB
API: Vulkan v: 1.3.295 layers: 16 device: 0 type: discrete-gpu
name: NVIDIA GeForce RTX 4080 driver: nvidia v: 565.57.01
device-ID: 10de:2704 surfaces: xcb,xlib device: 1 type: cpu name: llvmpipe
(LLVM 18.1.8 256 bits) driver: mesa llvmpipe v: 24.2.7-arch1.1 (LLVM
18.1.8) device-ID: 10005:0000 surfaces: xcb,xlib
Audio:
Device-1: Intel Raptor Lake High Definition Audio vendor: ASRock
driver: snd_hda_intel v: kernel alternate: snd_soc_avs,snd_sof_pci_intel_tgl
bus-ID: 00:1f.3 chip-ID: 8086:7a50 class-ID: 0403
Device-2: NVIDIA vendor: Gigabyte driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 8 link-max: lanes: 16 bus-ID: 01:00.1
chip-ID: 10de:22bb class-ID: 0403
API: ALSA v: k6.12.1-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: 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 RTL8125 2.5GbE vendor: ASRock driver: r8169 v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: 3000 bus-ID: 04:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd
Drives:
Local Storage: total: 17.28 TiB used: 9.21 TiB (53.3%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:4 vendor: TeamGroup
model: T-FORCE TM8FF1001T size: 931.51 GiB block-size: physical: 512 B
logical: 512 B speed: 126 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: EQFM22.1 temp: 54.9 C scheme: MBR
ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Fanxiang model: S880 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: SN17171 temp: 44.9 C
scheme: GPT
ID-3: /dev/nvme2n1 maj-min: 259:2 vendor: TeamGroup
model: T-FORCE TM8FPZ004T size: 3.64 TiB block-size: physical: 512 B
logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: EIFM51.3 temp: 31.9 C scheme: GPT
ID-4: /dev/sda maj-min: 8:0 vendor: Seagate model: ST12000NM0127
size: 10.91 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 7200 serial: <filter> fw-rev: G006 scheme: GPT
Partition:
ID-1: / raw-size: 464.76 GiB size: 464.76 GiB (100.00%)
used: 275.09 GiB (59.2%) fs: btrfs dev: /dev/nvme0n1p1 maj-min: 259:5
ID-2: /boot/efi raw-size: 1.03 GiB size: 1.02 GiB (99.80%)
used: 10.4 MiB (1.0%) fs: vfat dev: /dev/nvme0n1p3 maj-min: 259:7
ID-3: /home raw-size: 464.76 GiB size: 464.76 GiB (100.00%)
used: 275.09 GiB (59.2%) fs: btrfs dev: /dev/nvme0n1p1 maj-min: 259:5
ID-4: /var/log raw-size: 464.76 GiB size: 464.76 GiB (100.00%)
used: 275.09 GiB (59.2%) fs: btrfs dev: /dev/nvme0n1p1 maj-min: 259:5
ID-5: /var/tmp raw-size: 464.76 GiB size: 464.76 GiB (100.00%)
used: 275.09 GiB (59.2%) fs: btrfs dev: /dev/nvme0n1p1 maj-min: 259:5
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 46.86 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 32
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 8.0 C mobo: 35.0 C gpu: nvidia temp: 46 C
Fan Speeds (rpm): fan-1: 0 fan-2: 1190 fan-3: 3191 fan-4: 0 fan-5: 890
fan-6: 0 fan-7: 0 gpu: nvidia fan: 0%
Info:
Memory: total: 48 GiB available: 46.86 GiB used: 5.49 GiB (11.7%)
Processes: 524 Power: uptime: 15h 8m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 1 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 18.72 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
tool: systemctl
Packages: 2570 pm: pacman pkgs: 2518 libs: 651
tools: gnome-software,octopi,paru pm: flatpak pkgs: 52 Compilers:
clang: 18.1.8 gcc: 14.2.1 Shell: garuda-inxi default: Bash v: 5.2.37
running-in: lxterminal inxi: 3.3.36
Garuda (2.6.26-1):
System install date: 2024-07-04
Last full system update: 2024-12-05
Is partially upgraded: No
Relevant software: snapper NetworkManager dracut(custom) mkinitcpio
Windows dual boot: No/Undetected
Failed units: avast-vpsupdate.service avast.service fancontrol.service
Hi friends, and in particular any Garuda developers happening to read this. i been having a lot of troubles with my nvidia drivers after updates over the last 18 months or so, unlike i have experienced before using a nvidia card. Yet being part of this forum always found a solution to keep me going. 
However one solution, Garuda developers advised against, has proven to be a life saver. Even now using it has restored all the trouble the latest nvidia drivers i received through the Garuda update caused me to have. Please do not get me wrong. i’m not blaming anyone here, but it has been a real frustration for me, and i’m sure for developers.
Anyhow i thought by myself maybe if i show you the steps i had to take to get my machine to run flawlessly with a later model nvidia graphic card, on the latest driver (565 series). For then maybe you understand how best to use that information with people not being able to boot their machines after an update, or suspend, or play (certain) games, or are forced to use either Wayland or X11, because their operating system, apps or games, do not behave as should, after a nvidia driver update.
Anyhow at the core of this, for me getting my card to run rightly, is the difference between using the default nvidia drivers Garuda provides, or use the nvidia-all drivers from git to install the drivers.
To try and makes sense i will begin right at the beginning doing a clean install, and outline the steps i took, (was forced to take, as well as did out of interest sake, to see what would happen if i did,) and what i found out works, and what doesn’t for my machine with a later model nvidia card. Hopefully this will be helpful sorting these kind of troubles out.
-
Step number one i MUST install the (28-04-2024 Garuda) installation image with the open source selection, if i want to be able to boot into the image. If i use the nvidia drivers option the installation will not boot up Garuda, but hang when it reaches the graphical interface.
-
When i run Garuda after installation, and have done the complete (first) update, can i install the nvidia drivers. After which i will also install the Lts kernel.
-
However if i reboot the computer now, my installation will not work, but hang at boot loading the Zen, or Lts image.
However what i have not tried doing straight after an install, with the current nvidia driver version 565 series, is use the Linux kernel, for none of the others seem to work. i only found this out undoing the step i had done to get my machine to work, and reinstalling the Garuda drivers using the following code to reinstall the Garuda drivers.
sudo pacman -Rdd lib32-nvidia-utils-tkg lib32-opencl-nvidia-tkg nvidia-dkms-tkg nvidia-egl-wayland-tkg nvidia-settings-tkg nvidia-utils-tkg opencl-nvidia-tkg
#and then
garuda-update remote fix
However when i did that neither my Zen, nor my Lts kernel worked anymore. The dkms modules threw up errors when complied. (error 10) So i installed different kernels, and found that the Linux kernel worked to some degree. (i use X11, not sure if Wayland would work) E.g games and apps all worked fine. However i could no longer suspend my machine, and a whole bunch of blue lined errors where thrown up at boot. (level 4) The suspend did not work any longer though i had successfully used the follow code to fix it
sudo micro /etc/modprobe.d/nvidia-preserve-video-memory.conf
#paste the line below
options nvidia NVreg_PreserveVideoMemoryAllocations=1
#press Ctrl s, and then Ctrl q, to save and close the file.
#activate suspend services.
sudo systemctl enable --now nvidia-suspend.service
sudo systemctl enable --now nvidia-hibernate.service
sudo systemctl enable --now nvidia-resume.service
So i reinstalled the fix i had before, and i wanted to tell you about, which fixed all three kernels, and the suspend problems, and i can play my games and use my apps without any hassle and no more blue lined errors at boot either.
i give you the lines i used;
straight after my clean install i used this code
git clone https://github.com/Frogging-Family/nvidia-all.git
cd nvidia-all
makepkg -si
sudo dracut-rebuild
sudo update-grub
However when i tried doing that after i reinstalled the Garuda drivers the code as it is above no longer worked the same.
This code was the same
git clone https://github.com/Frogging-Family/nvidia-all.git
cd nvidia-all
makepkg -si
However dracut-rebuild i was no longer able to do for some reason, not sure about grub update, i did not try that. Instead i run Grauda update remote fix and this fixed all issues after and i could finally safely reboot.
garuda-update remote fix
i hope this information was useful. i’m not a developer, and do not understand the inner workings of the Linux machines. However i’m a happy man being part of this forum, for with the knowledge past on to me by those angels sharing their knowledge, i got everything up and running 100 percent again. It did take a bit of sorting out though. And it would be great if somehow the information i learned could help you guys get to the bottom of all this down the line.
You are all doing a great job. Love you all! 
Garuda Is The Only Dragon i Love! 
