On Mon, Jan 8, 2018 at 3:55 PM, Max Zettlmeißl <max@zettlmeissl.de> wrote:

> > The contents of cpuinfo is the same as the messages in dmesg. What does
> that
> > imply?
>
> Your BIOS or EFI might already install the same version or a later
> version than what the microcode package provides. Although the second
> case is highly unlikely.
> The update might also just not get applied properly.
>
> You should check whether the actual microcode version is the version
> which you expect.
>
> How are you trying to apply the microcode?
> The best way to update your processor's microcode is via early
> microcode loading.
> You can either use an initrd or build the microcode into your kernel
> image. I prefer the latter.
>
>
Yes the microcode is in the the kernel. Equivalent config works fine on
another machine.

The problem could be;
The firmware from /lib/firmware is that same as that on the system, so its
not required
The firmware loaded successfully, but didnt write a success log
The firmware failed to load (and didnt write a failure log, but we dont
expect it to)

Since I dont know where look up firmware version numbers i'm in the dark.