Jeshu’s commands come down to the same installing repo packages as I already did before. Redid the whole tests anyway.
Disabled file indexing.
With repo packages, kernel linux-zen, it freezes at login with X11.
With nvidia-all packages, can log in, but it’s extremely slow. Opening htop, there is 2% CPU usage by Xorg but nothing else and no IO usage.
There is no driver installation error.
The error mentioned above is mentioned here; it’s benign and Garuda-related.
If I look into the NVIDIA Git repo, there are various reports of system freeze, such as this and this
They mention that v550 is stable.
v550 fails to install on 6.13 though.
( 6/17) Install DKMS modules
==> dkms install --no-depmod nvidia/550.135 -k 6.13.6-zen1-1.1-zen
Error! Bad return status for module build on kernel: 6.13.6-zen1-1.1-zen (x86_64)
Consult /var/lib/dkms/nvidia/550.135/build/make.log for more information.
==> WARNING: `dkms install --no-depmod nvidia/550.135 -k 6.13.6-zen1-1.1-zen' exited 10
==> dkms install --no-depmod nvidia/550.135 -k 6.12.18-1.1-lts
==> depmod 6.12.18-1.1-lts
Now i´m a little bit confused.
Not shure (at the moment) which version you have installed.
Pls poste your inxi again
Of course it fails if you have “active” nvidia driver Ver. 570.xxx and also newer kernels.
Then delete by hand all unnecessary stuff inside folder /var/lib/dkms/nvidia/ or
over konsole: sudo dkms remove --no-depmod xxx ( old version from nvidia + kernels)
Also, each time after un or install / building / reinstall make a reboot.
To know if you use a older driver then 560.35 you should
set the modeset=1 for the nvidia_drm` module in the kernel.
about
early boot insert nvidia_drm.modeset=1 in the default grub config file.
→ reboot pls
This froggy driver nvidia-all is … 
think on it if you don´t have related files about nvidia drm modeset fbdev inside /usr/lib/modprobe.d/ and /or inside /etc/modprobe.d/
inside your own self-generated initramfs →
you have always the issue with nvidia gpus.
open source
GeForce RTX: 50 Series, 40 Series, 30 Series, 20 Series
GeForce: 16 Series
NVIDIA Turing: T4, T4G
All other cards are not supported by the Open-Source default Nvidia driver module because they lack GSP Firmware compatibilty.
Acer is a nightmare with bios + nvidia for Linux. To often broken bios with nvidia.
Support = 0 (my mind).
Sorry for my long typing in this thread here.
What does this modeset do?
It’s currently pretty stable with linux-lts and nvidia-all v550
I might have to wait on this config until kernel 6.14 and new NVIDIA drivers, see if they fix it. I’m not the only one having issues according to nvidia issue tracker.
Perhaps, but it often saved my life.
Without this stuff the nvidia driver can´t funktion. If you type this, then sorry your knowledge is..hmm..expandable.
If you use nvidia distrodriver, (equal lts, dkms, open) the install script do this for you. But with this fruggydriver perhaps or not. Then you must set this by handmade. Also enable services for the nvidia gpu.
For this reason you should post your inxi again. You use know which driver with which kernel ? If you use distro driver perhaps i have a solution for your problem..with this fruggy driver, sorry…can´t help.
And if you post links about reported issues then you should read what the guys type and perhaps if you read to the end and follow there also links
(what i do then) you can find perhaps a solution self.
v550 is definitely the most stable so far; but it’s still unstable.
Alright I added modeset, deleted the content of /var/lib/dkms/nvidia/, uninstalled nvidia-all and re-installed repo packages.
Freezes after X11 login. Here is updated inxi
System:
Kernel: 6.13.6-zen1-1.1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/.snapshots/480/snapshot/boot/vmlinuz-linux-zen
root=UUID=51ef4a7a-fb89-43c3-a466-7318e0363e7e quiet loglevel=3 ibt=off
rootflags=defaults,noatime,compress=zstd,subvol=@/.snapshots/480/snapshot
Desktop: KDE Plasma v: 6.3.2 tk: Qt v: N/A info: frameworks v: 6.11.0
wm: kwin_x11 vt: 2 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Laptop System: Acer product: Predator PH315-53 v: V2.04
serial: <superuser required>
Mobo: CML model: QX50_CMS v: V2.04 serial: <superuser required>
part-nu: 0000000000000000 uuid: <superuser required> UEFI: Insyde v: 2.04
date: 08/20/2021
Battery:
ID-1: BAT1 charge: 41.7 Wh (100.0%) condition: 41.7/58.8 Wh (71.0%)
volts: 16.4 min: 15.4 model: SMP AP18E7M type: Li-ion serial: <filter>
status: full
CPU:
Info: model: Intel Core i7-10750H bits: 64 type: MT MCP arch: Comet Lake
gen: core 10 level: v3 note: check built: 2020 process: Intel 14nm family: 6
model-id: 0xA5 (165) stepping: 2 microcode: 0xFC
Topology: cpus: 1x dies: 1 clusters: 6 cores: 6 threads: 12 tpc: 2
smt: enabled cache: L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB
desc: 6x256 KiB L3: 12 MiB desc: 1x12 MiB
Speed (MHz): avg: 800 min/max: 800/5000 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 bogomips: 62399
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel CometLake-H GT2 [UHD Graphics] vendor: Acer Incorporated ALI
driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20
ports: active: eDP-1 empty: HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:9bc4
class-ID: 0300
Device-2: NVIDIA TU106M [GeForce RTX 2060 Mobile]
vendor: Acer Incorporated ALI driver: nvidia v: 570.124.04
alternate: nouveau,nvidia_drm non-free: 550/565.xx+ status: current (as
of 2025-01; EOL~2026-12-xx) arch: Turing code: TUxxx process: TSMC 12nm FF
built: 2018-2022 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3
speed: 8 GT/s ports: active: none off: HDMI-A-1 empty: DP-1
bus-ID: 01:00.0 chip-ID: 10de:1f15 class-ID: 0300
Device-3: Quanta HD User Facing driver: uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-5:3 chip-ID: 0408:a061
class-ID: 0e02
Display: x11 server: X.Org v: 21.1.16 with: Xwayland v: 24.1.6
compositor: kwin_x11 driver: X: loaded: modesetting,nvidia unloaded: nouveau
alternate: fbdev,intel,nv,vesa dri: iris gpu: i915,nvidia,nvidia-nvswitch
display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: eDP-1 res: mode: 1920x1080 hz: 144 scale: 100% (1) dpi: 142
size: 344x194mm (13.54x7.64") diag: 395mm (15.55") modes: N/A
API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0
drv: nvidia device: 1 drv: iris gbm: drv: iris surfaceless: drv: nvidia x11:
drv: iris inactive: wayland
API: OpenGL v: 4.6.0 compat-v: 4.6 vendor: intel mesa v: 24.3.4-arch1.1.1
glx-v: 1.4 direct-render: yes renderer: Mesa Intel UHD Graphics (CML GT2)
device-ID: 8086:9bc4 memory: 7.54 GiB unified: yes
API: Vulkan v: 1.4.304 layers: 10 device: 0 type: integrated-gpu
name: Intel UHD Graphics (CML GT2) driver: N/A device-ID: 8086:9bc4
surfaces: xcb,xlib device: 1 type: discrete-gpu
name: NVIDIA GeForce RTX 2060 driver: N/A device-ID: 10de:1f15
surfaces: xcb,xlib device: 2 type: cpu name: llvmpipe (LLVM 19.1.7 256
bits) driver: N/A device-ID: 10005:0000 surfaces: xcb,xlib
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel Comet Lake PCH cAVS vendor: Acer Incorporated ALI
driver: snd_hda_intel v: kernel alternate: snd_soc_avs,snd_sof_pci_intel_cnl
bus-ID: 00:1f.3 chip-ID: 8086:06c8 class-ID: 0403
Device-2: NVIDIA TU106 High Definition Audio vendor: Acer Incorporated ALI
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 01:00.1 chip-ID: 10de:10f9 class-ID: 0403
Device-3: Texas Instruments PCM2900B Audio CODEC
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 1-1.2:4 chip-ID: 08bb:29b0 class-ID: 0300
API: ALSA v: k6.13.6-zen1-1.1-zen status: kernel-api tools: N/A
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: PipeWire v: 1.4.0 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Comet Lake PCH CNVi WiFi vendor: Rivet Networks Dual Band
Wi-Fi 6 Killer AX1650i 160MHz 2x2 driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:06f0 class-ID: 0280
IF: wlp0s20f3 state: up mac: <filter>
Device-2: Realtek Killer E2600 GbE vendor: Acer Incorporated ALI
driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000
bus-ID: 08:00.0 chip-ID: 10ec:2600 class-ID: 0200
IF: enp8s0 state: down mac: <filter>
IF-ID-1: virbr0 state: down mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
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:5 chip-ID: 8087:0026
class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 1 state: down bt-service: enabled,running
rfk-block: hardware: no software: yes address: <filter> bt-v: 5.2 lmp-v: 11
status: discoverable: no pairing: no
Drives:
Local Storage: total: 3.19 TiB used: 2.2 TiB (68.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: PC SN730
SDBQNTY-512G-1014 size: 476.94 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 11101100 temp: 24.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:2 vendor: Western Digital
model: WD Blue SN570 2TB size: 1.82 TiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 234200WD temp: 38.9 C scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: HGST (Hitachi) model: HTS721010A9E630
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 7200 serial: <filter> fw-rev: A3J0 scheme: GPT
Partition:
ID-1: /boot/efi raw-size: 625 MiB size: 623.7 MiB (99.80%)
used: 608 KiB (0.1%) fs: vfat dev: /dev/nvme1n1p1 maj-min: 259:3
ID-2: /home raw-size: 1.73 TiB size: 1.73 TiB (100.00%)
used: 1.12 TiB (64.7%) fs: btrfs dev: /dev/nvme1n1p3 maj-min: 259:5
ID-3: /var/log raw-size: 1.73 TiB size: 1.73 TiB (100.00%)
used: 1.12 TiB (64.7%) fs: btrfs dev: /dev/nvme1n1p3 maj-min: 259:5
ID-4: /var/tmp raw-size: 1.73 TiB size: 1.73 TiB (100.00%)
used: 1.12 TiB (64.7%) fs: btrfs dev: /dev/nvme1n1p3 maj-min: 259:5
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 15.45 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 12
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 49.0 C pch: 56.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 16 GiB available: 15.45 GiB used: 3.38 GiB (21.9%)
Processes: 364 Power: uptime: 4m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 6.13 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1686 libs: 459 tools: octopi,paru Compilers:
clang: 19.1.7 gcc: 14.2.1 Shell: garuda-inxi default: fish v: 4.0.0
running-in: konsole inxi: 3.3.37
Garuda (2.7.2-1):
System install date: 2024-07-17
Last full system update: 2025-03-11
Is partially upgraded: Yes
Relevant software: snapper NetworkManager dracut
Windows dual boot: No/Undetected
Failed units: docker.service systemd-remount-fs.service docker.socket
I had booted in LTS; rebooted in ZEN and updated inxi here.
Just realized something. With this setup, it freezes at login. If I unplug HDMI, then it unfreezes and goes to the desktop. If I plug it back, it freezes again. If I unplug it, it closes/reopens X11 and unfreezes.
In which case; it’s really not SDDM, but NVIDIA+HDMI that causes the problem.
Right, the problem is then sddm login…
Edit…Sorry, no..you have the issue with sddm login (my mind)
Read this and insert pls the related stuff and perhaps you have the solution.
Test with wayland.. pls and ?
Wayland can log in; but after a while, it freezes. Unlike X11, I cannot recover from those freezes so that’s why I stick to X11.
Found this thread
Will try i915.dmc_firmware_path= boot parameter.
Some have fixed it by switching over to XFCE…
That’s annoying. .. 
Yes, also a good idea to switch.
Does not help.
Even re-installing; I’m seeing reports of the issue on Cinnamon and XFCE so I doubt that switching is a solution.
Is there an easy way to replace KDE with XFCE to try it out without re-installing the system in a way that can be rolled back; or would that require resetting the whole system?
Edit: ok after quick research it appears that I can simply install XFCE and both can co-exist
It depends on what you mean by easy, there is always a residual risk. You can create a new user and install xfce there. I strongly advise against installing several DE’s on one user.
It would make sense to test the whole thing in a VM beforehand, if there are conflicts between the DE’s, then probably also on bare metal.
Now that’s interesting. XFCE worked just fine.
Then I realized it was mirroring between laptop and HDMI displays.
When I switched to external-only, it froze. Unplugging HDMI, it unfreezes.
Perhaps KDE would work with mirror display? But by plugging HDMI, it automatically switches to external without giving me a chance to select. Any way to set the default to mirror before it freezes?
WOOHOO!!!
This thread explains the problem and here’s the solution
From 570 changelog
Fixed a bug that could cause external displays to become frozen until the next modeset when using PRIME Display Offloading with the NVIDIA dGPU acting as the display offload sink.
but the issue is not fixed at all.
The solution is to create file /etc/X11/xorg.conf.d/10-nvidia-drm-outputclass.conf with this content
Section "OutputClass"
Identifier "intel"
MatchDriver "i915"
Driver "modesetting"
EndSection
Section "OutputClass"
Identifier "nvidia"
MatchDriver "nvidia-drm"
Driver "nvidia"
Option "AllowEmptyInitialConfiguration"
Option "PrimaryGPU" "yes"
ModulePath "/usr/lib/nvidia/xorg"
ModulePath "/usr/lib/xorg/modules"
EndSection
Now all rendering is performed by NVidia’s dGPU and there is no freezes in glxgears/vkcube, cause reverse PRIME is not needed anymore. Ordinary PRIME (forward PRIME) is used in this setup. Yes, dGPU draws little more power, then Intel’s iGPU. But i’m ready to pay this price to get renderint without freezes. Especially while using AC power source.
Well… it works fine, until I turn off the TV and walk away. When I come back, the UI freezes.
Setting display to Mirror on both doesn’t help.
Not sure that’s better than the v550 setup.
Could it be that your system goes to sleep when you walk away? For when my computer goes to sleep, or when i hibernate my computer, then i have to excute a little script, i get running by hot key, which resets the win_x11 window manager, and if needed also the panel and resolution, this fixes the coming awake problem nvidia has had for some time now. You may have to install the app pixelcolor through bauh.
i’ll give you a copy of my script, so you can try and see if that works when your screen wont wake up after it has gone to sleep problem. (You may have to change the value of the screen resolutions, i have only one monitor and changr my resolution to 1920x1080 and then back to to 3840x2160, this usually fixes it, however you may not run the same resolutions as me, or have more than one monitor.
#!/usr/bin/bash
pixelcolour=`pixelcolor --x 140 --y 210 --hex`;
if [ "$pixelcolour" = "000000" ];then
pkill -9 kwin_x11;sleep .49;eval 'kwin_x11 &';pkill -15 plasmashell;
sleep .49;eval 'plasmashell &';sleep 1.4;
pixelcolour=`pixelcolor --x 140 --y 210 --hex`;
if [ $pixelcolour = "000000" ];then
pkill -9 kwin_x11;sleep .49;eval 'kwin_x11 &';sleep 3.5;
while :; do
pixelcolour2=`pixelcolor --x 210 --y 140 --hex`;
if ! [ $pixelcolour2 = "000000" ];then
break;
else
pkill -9 kwin_x11;sleep .49;eval 'kwin_x11 &';
xrandr --output `xrandr | grep " connected"|cut -f1 -d" "` --mode 1920x1080;
xrandr --output `xrandr | grep " connected"|cut -f1 -d" "` --mode 3840x2160 --rate '144';
sleep 3.5;
fi;
add=$((add+1));
if [ $add -gt 4 ];then
add=0;break;
fi;sleep 1.4;
done;
fi;
One issue is that while the UI is frozen, keyboard shortcuts don’t work.
If I set the display to “mirror”, with minimal internal screen brightness, then when I turn the TV back on, it freezes for about 10-15 seconds, then closes KDE and restarts it and I can keep working. That looks acceptable so far.