Locking nVidia-Settings fan speed

Anyone know how to lock one’s custom fan speed in nVidia-Settings? They revert back to 0 after a logoff or reboot. I edited the one config file I could find and changed thermal in it from 0 to 80, but on a reboot it was back to the 0 and I could no longer set the fan speed in the GUI.

~  garuda-inxi                                                                                             ✔  11:28:11 AM
System:
Kernel: 6.14.7-zen2-1-zen arch: x86_64 bits: 64 compiler: gcc v: 15.1.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=5d6e39dd-31e5-4e2c-8ea6-251eb13348a1 rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.3.5 tk: Qt v: N/A info: frameworks v: 6.14.0
wm: kwin_wayland with: krunner vt: 1 dm: SDDM Distro: Arch Linux
Machine:
Type: Desktop Mobo: Gigabyte model: X670 AORUS ELITE AX v: x.x
serial: <superuser required> uuid: <superuser required> UEFI: American
Megatrends LLC. v: FB1 date: 05/22/2024
CPU:
Info: model: AMD Ryzen 7 7700X bits: 64 type: MT MCP arch: Zen 4 gen: 4
level: v4 note: check built: 2022+ process: TSMC n5 (5nm) family: 0x19 (25)
model-id: 0x61 (97) stepping: 2 microcode: 0xA601209
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: 8 MiB
desc: 8x1024 KiB L3: 32 MiB desc: 1x32 MiB
Speed (MHz): avg: 2989 min/max: 545/5575 boost: enabled scaling:
driver: amd-pstate-epp governor: performance cores: 1: 2989 2: 2989 3: 2989
4: 2989 5: 2989 6: 2989 7: 2989 8: 2989 9: 2989 10: 2989 11: 2989 12: 2989
13: 2989 14: 2989 15: 2989 16: 2989 bogomips: 143729
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA GA106 [GeForce RTX 3060 Lite Hash Rate] vendor: ASUSTeK
driver: nvidia v: 570.153.02 alternate: nouveau,nvidia_drm
non-free: 550-570.xx+ status: current (as of 2025-04; 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: HDMI-A-1
empty: DP-1,DP-2,DP-3 bus-ID: 01:00.0 chip-ID: 10de:2504 class-ID: 0300
Device-2: Advanced Micro Devices [AMD/ATI] Raphael vendor: Gigabyte
driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm)
built: 2020-22 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: 17:00.0
chip-ID: 1002:164e class-ID: 0300 temp: 44.0 C
Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6
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: HDMI-A-1 model: 32SA2QK serial: <filter> built: 2024 res:
mode: 3840x2160 hz: 60 scale: 150% (1.5) to: 2560x1440 dpi: 140 gamma: 1.2
size: 697x393mm (27.44x15.47") diag: 800mm (31.5") ratio: 16:9 modes:
max: 3840x2160 min: 640x480
API: EGL v: 1.5 hw: drv: nvidia drv: amd radeonsi platforms: device: 0
drv: nvidia device: 1 drv: radeonsi device: 3 drv: swrast gbm: drv: radeonsi
surfaceless: drv: nvidia wayland: drv: nvidia x11: drv: nvidia
inactive: device-2
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 570.153.02
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 3060/PCIe/SSE2
memory: 11.72 GiB display-ID: :1.0
API: Vulkan v: 1.4.313 layers: 10 device: 0 type: discrete-gpu
name: NVIDIA GeForce RTX 3060 driver: nvidia v: 570.153.02
device-ID: 10de:2504 surfaces: N/A device: 1 type: integrated-gpu name: AMD
Radeon Graphics (RADV RAPHAEL_MENDOCINO) driver: mesa radv
v: 25.1.1-arch1.2 device-ID: 1002:164e surfaces: N/A device: 2 type: cpu
name: llvmpipe (LLVM 19.1.7 256 bits) driver: mesa llvmpipe
v: 25.1.1-arch1.2 (LLVM 19.1.7) device-ID: 10005:0000 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: corectrl, lact, nvidia-settings,
nvidia-smi wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: NVIDIA GA106 High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 01:00.1 chip-ID: 10de:228e class-ID: 0403
Device-2: Creative Labs CA0108/CA10300 [Sound Blaster Audigy Series]
driver: snd_emu10k1 v: kernel bus-ID: 0d:00.0 chip-ID: 1102:0008
class-ID: 0401
Device-3: Advanced Micro Devices [AMD/ATI] Rembrandt Radeon High
Definition Audio driver: snd_hda_intel v: kernel pcie: gen: 4
speed: 16 GT/s lanes: 16 bus-ID: 17:00.1 chip-ID: 1002:1640 class-ID: 0403
Device-4: Advanced Micro Devices [AMD] Family 17h/19h/1ah HD Audio
vendor: Gigabyte driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
lanes: 16 bus-ID: 17:00.6 chip-ID: 1022:15e3 class-ID: 0403
API: ALSA v: k6.14.7-zen2-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.4.2 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 RTL8852CE PCIe 802.11ax Wireless Network vendor: AzureWave
driver: rtw89_8852ce v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1
port: c000 bus-ID: 0e:00.0 chip-ID: 10ec:c852 class-ID: 0280
IF: wlp14s0 state: up mac: <filter>
Device-2: Realtek RTL8125 2.5GbE vendor: Gigabyte driver: r8169 v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: b000 bus-ID: 0f:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: enp15s0 state: down mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: IMC Networks Bluetooth Radio driver: btusb v: 0.8 type: USB
rev: 1.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-7:6 chip-ID: 13d3:3586
class-ID: e001 serial: <filter>
Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
rfk-block: hardware: no software: no address: <filter> bt-v: 5.3 lmp-v: 12
status: discoverable: no pairing: no
Drives:
Local Storage: total: 36.38 TiB used: 21.05 TiB (57.9%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:1 vendor: Samsung model: SSD 990 EVO 2TB
size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 126 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 0B2QKXJ7 temp: 40.9 C
scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:7 vendor: Crucial model: CT1000P3SSD8
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: P9CR313 temp: 30.9 C
scheme: GPT
ID-3: /dev/nvme2n1 maj-min: 259:0 vendor: Crucial model: CT1000T500SSD8
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: P8CR002 temp: 31.9 C
scheme: GPT
ID-4: /dev/sda maj-min: 8:0 vendor: Seagate model: Expansion HDD
size: 7.28 TiB block-size: physical: 4096 B logical: 512 B type: USB
rev: 2.1 spd: 480 Mb/s lanes: 1 mode: 2.0 tech: N/A serial: <filter>
fw-rev: 1801 scheme: GPT
ID-5: /dev/sdb maj-min: 8:16 vendor: Seagate model: Expansion HDD
size: 10.91 TiB block-size: physical: 4096 B logical: 512 B type: USB
rev: 2.1 spd: 480 Mb/s lanes: 1 mode: 2.0 tech: N/A serial: <filter>
fw-rev: 0003 scheme: GPT
ID-6: /dev/sdc maj-min: 8:32 vendor: Seagate model: Expansion HDD
size: 14.55 TiB block-size: physical: 4096 B logical: 512 B type: USB
rev: 2.1 spd: 480 Mb/s lanes: 1 mode: 2.0 tech: N/A serial: <filter>
fw-rev: 1801 scheme: GPT
Partition:
ID-1: / raw-size: 349.26 GiB size: 349.26 GiB (100.00%)
used: 38.04 GiB (10.9%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:4
ID-2: /boot/efi raw-size: 1.95 GiB size: 1.95 GiB (99.80%)
used: 363.5 MiB (18.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:2
ID-3: /home raw-size: 349.26 GiB size: 349.26 GiB (100.00%)
used: 38.04 GiB (10.9%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:4
ID-4: /var/log raw-size: 349.26 GiB size: 349.26 GiB (100.00%)
used: 38.04 GiB (10.9%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:4
ID-5: /var/tmp raw-size: 349.26 GiB size: 349.26 GiB (100.00%)
used: 38.04 GiB (10.9%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:4
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 61.76 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: 54.8 C mobo: 34.5 C gpu: amdgpu temp: 43.0 C
Fan Speeds (rpm): N/A
Info:
Memory: total: 64 GiB note: est. available: 61.76 GiB
used: 12.14 GiB (19.7%)
Processes: 542 Power: uptime: 1h 50m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 24.63 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Packages: 2175 pm: pacman pkgs: 2157 libs: 592 tools: pacseek,pikaur,yay
pm: appimage pkgs: 0 pm: flatpak pkgs: 9 pm: snap pkgs: 9 Compilers:
clang: 19.1.7 gcc: 15.1.1 Shell: garuda-inxi default: Zsh v: 5.8
running-in: konsole inxi: 3.3.38
Garuda (2.7.2-1):
System install date:     2025-05-26
Last full system update: 2025-05-30 ↻
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       No/Undetected
Failed units:

You know wayland and nvidia-settings are not good friends.
Perhaps with X11 or with sudo rights..but .. install lact. (my mind)

open konsole:

  • sudo pacman -S lact
  • sudo systemctl enable --now lactd
  • lact
1 Like

:smiley:

2 Likes

Thanks, much appreciated. Had asked about a GWE alternative but guess I should of asked here.

Installed and service started, but getting the below.

~  lact                                                                                                    ✔  02:05:26 PM

(lact:1146687): Gtk-WARNING **: 14:05:31.769: Unknown key gtk-modules in /home/cccp/.config/gtk-4.0/settings.ini
2025-05-30T21:05:31.994517Z  INFO lact_client::connection::unix: connecting to service at "/run/lactd.sock"
2025-05-30T21:05:55.550498Z  WARN update_with_view{input=ApplyChanges component="lact_gui::app::AppModel" id="0x7ffe1e5ddf40"}: lact_gui::app: Could not apply settings

Caused by:
0: Got error from daemon, end of client boundary
1: Could not apply settings
2: Failed to set static fan control
3: Could not set fan control method
4: io error: Permission denied (os error 13)
~  sudo lact                                                                                         ✔  58s  02:06:29 PM

(lact:1152305): Gtk-WARNING **: 14:06:36.634: Unknown key gtk-modules in /root/.config/gtk-4.0/settings.ini

(lact:1152305): Gtk-WARNING **: 14:06:36.650: Unable to acquire session bus: Error spawning command line “dbus-launch --autolaunch=9be6fbd51d674a7793fd4af8058f5bce --binary-syntax --close-stderr”: Child process exited with code 1
2025-05-30T21:06:36.706658Z  INFO lact_client::connection::unix: connecting to service at "/run/lactd.sock"

(lact:1152305): Gtk-WARNING **: 14:06:36.730: Trying to measure GtkHeaderBar 0x55d97bfffdb0 for width of 208, but it needs at least 583
2025-05-30T21:06:46.534605Z  WARN update_with_view{input=ApplyChanges component="lact_gui::app::AppModel" id="0x7ffd14e41040"}: lact_gui::app: Could not apply settings

Caused by:
0: Got error from daemon, end of client boundary
1: Could not apply settings
2: Failed to set static fan control
3: Could not set fan control method
4: io error: Permission denied (os error 13)

you have to enable the demon there’s a button to do it. should be in the software tab. its a gui tool so no need for sudo

Already did sudo systemctl enable --now lactd

https://i.imgur.com/DdMu04u.png

https://i.imgur.com/KDJseuu.png

Your pictures: lact show your igpu (amd) and not your dgpu (nvidia)
and the fan is not physical connected, of course that’s the cpu fan.
With

  • lact cli list-gpus
    or
  • lact cli info
    you see gpu information.
    If you don´t see about this your dgpu than fan monitoring or control might not be available on some laptops (own message from the lact devs)

But perhaps reboot can also resolve this. (not shure)

And you can switch if you click there

No function about lact try with coolercontrol (sensors must running then) or corectl.
Self, no knowledge about both.

1 Like

Nice catch, thanks. I always forget that this CPU as that. Looks to be working perfectly now.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.