| 1 |
On Monday, 12 April 2021 11:56:40 BST Adam Carter wrote: |
| 2 |
> Do these largely overlap? |
| 3 |
|
| 4 |
Yes. |
| 5 |
|
| 6 |
> So if your motherboard manufacturer is diligent with releasing updates and |
| 7 |
> you've applied them, you generally won't expect a 'microcode updated early |
| 8 |
> to new patch_level' message from dmesg? |
| 9 |
|
| 10 |
From what I've come across so far, it's been the case MoBo manufacturers |
| 11 |
release BIOS/UEFI code upgrades for a few years only. Dekstop MoBos up to 5 |
| 12 |
years after product launch, laptops up to 2 years if you're lucky. Thereafter |
| 13 |
CPU microcode patching becomes an exercise for the OS. However, the CPU |
| 14 |
manufacturer may not bother releasing updates for your CPU model, in which |
| 15 |
case the result is the same. :( |
| 16 |
|
| 17 |
The signature of the microcode will change after an OEM BIOS/UEFI code upgrade |
| 18 |
has been flashed into the MoBo, so you'll be able to tell if the upgrade had |
| 19 |
anything to do with the CPU. |
Archives