Search results

Looks like we're finally getting support for EDAC memory error reporting in Linux. Support for some in the 13th gen were added in 6.15 (EDAC/ie31200: Add Intel Raptor Lake-S SoCs support - kernel/git/next/linux-next.git - The linux-next integration testing tree) and it looks like more will be...

Support for some in the 13th gen were added in 6.15 (EDAC/ie31200: Add Intel Raptor Lake-S SoCs support - kernel/git/next/linux-next.git - The linux-next integration testing tree) and it looks like more will be added in 6.17 (EDAC/ie31200: Enable support for Core i5-14600 and i7-14700 -...

AFAIU, 0x12f also fixed some security issues, so its still useful to apply via the OS path (and they did eventually publish 0x129 via the OS path, just not initially). I assume the same is true, but someone could go ask.

For those curious, I just messaged Supermicro and their response was that "The coming BIOS version will have the Intel Microcode 0x12f for X13SAE/X13SAE-F. The estimated ETA will be by the end of this month."

Yes, one of the Intel folks who pushes the uCode updates that Linux distros pull from commented at uCode for Voltage issue · Issue #78 · intel/Intel-Linux-Processor-Microcode-Data-Files Right, so the update is important for anyone here (ie running a 24/7 machine, presumably with a "lightly...

Is this true? No published BIOSes include 0x12f yet, and while you can get 0x12f from your distro, applying earlier Vmin shift microcode updates post-boot as a part of early OS load was *not* sufficient to mitigate the issue, the microcode had to be applied by the BIOS.