Some commentary on the Raptor Lake (Intel 13th and 14th gen) CPU's and the Supermicro X13SAE(-F) motherboards.
Supermicro had, for a few days, BIOS version 3.3, which included the 0x125 microcode update, which fixed eTVB (enhanced Thermal Velocity Boost) in the i9 parts. The website has now, temporarily reverted back to 3.1. My guess is that they are testing the just released 0x129 microcode update, which caps the Vcore supply to 1.55 V to prevent the processor ring-bus damage that was occurring because of Vcore voltages that were too high during single or dual thread operation of the CPU (i.e. where the clock speed of the P-Cores would be the highest and need the most voltage).
Until then, if you are worried about voltages above 1.55 V being provided to the CPU before (or even after the BIOS with 0x129 comes out), you can install the following two files in vcore_log_service.zip that provide a script based monitoring service:
The vcore_log.service goes into the /etc/systemd/system directory. The actual script, record_vcore.sh, goes into the /usr/local/bin directory.
You can enable the service after putting the files in place by systemctl daemon-reload then systemctl enable vcore_log.service and systemctl start vcore_log.service.
The script uses the bc console calculator, and the rdmsr tool from msr-tools. you may have to install packages for those commands if they are not available on your system.
The voltage maximum is set by editing record_vcore.sh and changing the vcore_log value. It is currently set to the Intel recommended maximum for Raptor Lake of 1.55 V. Note that after a BIOS upgrade is done with the 0x129 microcode version, you should see NO entries.
The script will log an entry to /var/log/vcore.log and also to the dmesg if this voltage is exceeded. It samples every second.
Note that I have been running this script for several days on my X13SAE with a 13900K and OpenSUSE Leap 15.6 and have NO entries. I have BIOS 3.3 with the 0x125 microcode installed.
