2 ms·
Yes, and this bug was fixed years ago. The person who stumbled upon it only did so because the correct microcode update was not being loaded. Although the fact
by Tuna-Fish 4y ago
Yes, and this bug was fixed years ago. The person who stumbled upon it only did so because the correct microcode update was not being loaded.
Although the fact that there apparently exist some APUs that have not had the update applied because of shitty OEMs is very concerning.
- jabl 4y agoAlso AMD being shitty and not publishing microcode updates to the linux-firmware repo so users would get access to them despite crappy OEM's or users neglecting to do BIOS updates.