1 |
> The contents of cpuinfo is the same as the messages in dmesg. What does that |
2 |
> imply? |
3 |
|
4 |
Your BIOS or EFI might already install the same version or a later |
5 |
version than what the microcode package provides. Although the second |
6 |
case is highly unlikely. |
7 |
The update might also just not get applied properly. |
8 |
|
9 |
You should check whether the actual microcode version is the version |
10 |
which you expect. |
11 |
|
12 |
How are you trying to apply the microcode? |
13 |
The best way to update your processor's microcode is via early |
14 |
microcode loading. |
15 |
You can either use an initrd or build the microcode into your kernel |
16 |
image. I prefer the latter. |