5 ms·
Jesus, what a pain. Why the hell do you need to wait for your proprietary OS vendor or BIOS vendor to update anything? On Linux the kernel does that for you, ju
by scaladev 6y ago
Jesus, what a pain. Why the hell do you need to wait for your proprietary OS vendor or BIOS vendor to update anything? On Linux the kernel does that for you, just configure your bootloader to point the kernel to a microcode image and that's it. Why can't windows do the same?
- ac29 6y agoMicrosoft does release microcode updates for windows, here's an example: https://support.microsoft.com/en-us/topic/kb4494454-intel-microcode-updates-547a9fa2-7f24-3172-795b-51a956faed22 https://support.microsoft.com/en-us/topic/kb4494454-intel-mi...
- rincebrain 6y agoYou only really need the "early" microcode loading procedure (the one where you pass it in the bootloader) if you have a microcode problem that is so broken the system won't boot with it unfixed (...or you're toggling feature bits off and the kernel will break if you originally booted with those bits and then they go missing - e.g. the broken TSX implementations on Haswell/Broadwell). Otherwise, just loading the microcode update once you get into the running OS is fine. I've never actually had a system that needed to use the former, but I've certainly used the latter.