01-06-2018 08:57 AM - last edited on 03-06-2024 09:31 PM by ROGBot
01-06-2018 01:31 PM
01-06-2018 03:51 PM
ReaperOneSIx wrote:
what does this fix do?
01-11-2018 11:24 PM
01-15-2018 10:33 AM
01-15-2018 11:39 AM
kasper93 wrote:
Well, nice try, but this is not going to work.
To explain what is going on here. Nixon2992 used the driver https://labs.vmware.com/flings/vmware-cpu-microcode-update-driver which loads updated microcode. Nothing really complicated. But this DOES NOT work for Spectre/Meltdown because the new microcode is loaded by the driver too late, way after the kernel checked the CPU capabilities. So don't bother with this method.
One proven method is to wait for the updated BIOS or just mod it manually and replace the microcode. Procedure is really simple, for example using automated tool like https://www.win-raid.com/t154f16-Tool-Guide-News-quot-UEFI-BIOS-Updater-quot-UBU.html
Anyhow first you need to ask if microcode for your CPU is actually available. Because at this moment not every CPU have new microcode and many have issues. For example Haswells are unstable and Broadwell-E haven't got an update at all. Which is very sad, because it is two years old CPU.
01-17-2018 11:17 AM
kasper93 wrote:
Anyhow first you need to ask if microcode for your CPU is actually available. Because at this moment not every CPU have new microcode and many have issues. For example Haswells are unstable and Broadwell-E haven't got an update at all. Which is very sad, because it is two years old CPU.
Out of an abundance of caution, Intel requested Lenovo to stop distributing this firmware.