Proxmox changing BIOS fan settings on ASUS NUC.

B

bartolus22

New Member
Apr 11, 2025
3
0
1
I have Proxmox running on an ASUS NUC 14 Pro.
Proxmox: latest version, kernel 6.11.11-2-pve, NUC: NUC14RVHU7.
Since an update on March 25th I face the following issue:

The NUC is running very hot, mostly on thermal throttle at about 100°C, at a CPU load of roughly 3%, so not too much.
This is happening only since this update, because Proxmox since that point of time is changing the BIOS setting for the fan to "standard". But I would like to have "performance".
If I change it back to performance, this setting obviously is set again to standard as soon as Proxmox loaded.
When booting into an Ubuntu the BIOS setting remains correctly.

What is happening here? Is there any idea what I could do to prevent Proxmox from changing this setting?

The update on March 25th was containing the following packages:

Start-Date: 2025-03-25 13:38:19
Commandline: apt-get dist-upgrade
Install: proxmox-kernel-6.8.12-9-pve-signed:amd64 (6.8.12-9, automatic)
Upgrade: proxmox-widget-toolkit:amd64 (4.3.6, 4.3.7), zfs-zed:amd64 (2.2.7-pve1, 2.2.7-pve2), zfs-initramfs:amd64 (2.2.7-pve1, 2.2.7-pve2), spl:amd64 (2.2.7-pve1, 2.2.7-pve2), libnvpair3linux:amd64 (2.2.7-pve1, 2.2.7-pve2), xsltproc:amd64 (1.1.35-1, 1.1.35-1+deb12u1), grub-pc-bin:amd64 (2.06-13+pmx5, 2.06-13+pmx6), libuutil3linux:amd64 (2.2.7-pve1, 2.2.7-pve2), libzpool5linux:amd64 (2.2.7-pve1, 2.2.7-pve2), proxmox-grub:amd64 (2.06-13+pmx5, 2.06-13+pmx6), proxmox-kernel-6.8:amd64 (6.8.12-8, 6.8.12-9), grub-efi-amd64:amd64 (2.06-13+pmx5, 2.06-13+pmx6), proxmox-backup-file-restore:amd64 (3.3.3-1, 3.3.4-1), proxmox-secure-boot-support:amd64 (1.0.11, 1.0.12), pve-i18n:amd64 (3.4.0, 3.4.1), grub-efi-amd64-signed:amd64 (1+2.06+13+pmx5, 1+2.06+13+pmx6), libxslt1.1:amd64 (1.1.35-1, 1.1.35-1+deb12u1), proxmox-backup-client:amd64 (3.3.3-1, 3.3.4-1), grub-efi-amd64-bin:amd64 (2.06-13+pmx5, 2.06-13+pmx6), grub2-common:amd64 (2.06-13+pmx5, 2.06-13+pmx6), grub-common:amd64 (2.06-13+pmx5, 2.06-13+pmx6), libzfs4linux:amd64 (2.2.7-pve1, 2.2.7-pve2), zfsutils-linux:amd64 (2.2.7-pve1, 2.2.7-pve2)
End-Date: 2025-03-25 13:39:00

Thanks in advance for any ideas or proposals!

Bernhard


​

 
Within the NUC14 you can try a custom FAN setting.
You can try if this remain.
 
But it still is a bit strange that proxmox is able to change this bios setting.
This is normally not possible
 
  • Like
Reactions: Ernst T.
I have a very similar problem with a nuc14 essential: If I change the fan profile to custom, after booting proxmox the fan profile switch back to standard.
I didn't tried with other OS so I don't now if it's a bios or OS problem.
Another problem that I have are suddendly spike in cpu temp to 105°C for 1s (clearly a glitch) that cause the fan to start at high speed.
I confirmed the spike with sensors, the problematic sensor is temp 2 from acpitz-acpi-0Adapter (it seems to track the cpu temperature).
 
I installed windows 11 pro on the same machine and I confirm that both problems are present also on windows.
This confirm that the problem is in the NUC 14 bios.
 
  • Like
Reactions: keeka
I asked my Asus contact, and he would like to have the
- SKU number
- Bios Version
- Proxmox version
- Windows Version
If all the affected users can send it via PM I can forward it.
 
Same issue with fan policy being reset. Upgraded to latest BIOS, but same issue. Throttling erratically:


Code: 
top - 03:53:45 up 6 days, 13:32,  2 users,  load average: 0.45, 0.39, 0.40
Tasks: 483 total,   1 running, 482 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.4 us,  0.4 sy,  0.0 ni, 99.2 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
MiB Mem :  31399.4 total,   9801.0 free,  17800.8 used,   4445.8 buff/cache     
MiB Swap:   8192.0 total,   8192.0 free,      0.0 used.  13598.6 avail Mem

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
2261732 root      20   0 9261392   4.4g  10824 S  40.0  14.4   7:10.66 kvm
   3689 root      20   0 5129544   3.0g  21720 S  10.0   9.7 208:15.93 kvm
2282465 root      20   0   11008   5564   3628 R  10.0   0.0   0:00.01 top
      1 root      20   0   25328  15572  10468 S   0.0   0.0   0:08.80 systemd
      2 root      20   0       0      0      0 S   0.0   0.0   0:00.34 kthreadd
      3 root      20   0       0      0      0 S   0.0   0.0   0:00.00 pool_wo+
      4 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+
      5 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+
      6 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+
      7 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+
      8 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+
     10 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+
     13 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+
 03:53:45 up 6 days, 13:32,  2 users,  load average: 0.45, 0.39, 0.40
[    3.307936] asus-nb-wmi asus-nb-wmi: Using throttle_thermal_policy for platform_profile support
[    0.117240] CPU0: Thermal monitoring enabled (TM1)
[    0.134367] thermal_sys: Registered thermal governor 'fair_share'
[    0.134367] thermal_sys: Registered thermal governor 'bang_bang'
[    0.134367] thermal_sys: Registered thermal governor 'step_wise'
[    0.134367] thermal_sys: Registered thermal governor 'user_space'
[    0.134367] thermal_sys: Registered thermal governor 'power_allocator'
[    0.866023] ACPI: thermal: [Firmware Bug]: Invalid critical threshold (-274000)
[    0.866083] thermal LNXTHERM:00: registered as thermal_zone0
[    0.866085] ACPI: thermal: Thermal Zone [TZ0] (40 C)
[    0.866379] thermal LNXTHERM:01: registered as thermal_zone1
[    0.866380] ACPI: thermal: Thermal Zone [TZ00] (54 C)
[    3.307936] asus-nb-wmi asus-nb-wmi: Using throttle_thermal_policy for platform_profile support
[    3.382507] proc_thermal_pci 0000:00:04.0: enabling device (0000 -> 0002)
 
You must log in or register to reply here.
Top Bottom