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
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
