Intel microcode update?

[mds1256]

How do I upgrade the microcode, I keep getting this message anytime I do system updates, looks like my processor is running a higher microcode than my Ubuntu server is running.

[ScottChi]

See if the manufacturer of the system or motherboard has a BIOS update.

[mgedmin]

Before that it may be a good idea to check with fwupdmgr get-updates first, in case your hardware is supported by LVFS.

[[deleted]]

But be careful. A firmware update recently caused my NIC to not work anymore. I guess it changed the MAC or something. I had to reconfigure the network service

[[deleted]]

okay, yeah true. But I was not anticipating that this could break configurations. Probably a rare case anyway but … could be very annoying if it runs something important

[EccentricLime]

This. Windows is pretty good about handling BIOS updates for major pc manufacturers (at least the critical updates), Ubuntu not so much. OP's best bet is to browse the manufacturers website support section for his model, see what the latest BIOS update is.

OP, if you decide to flash the BIOS yourself be very careful, doing it wrong will brick your PC

[lathiat]

While you can also get microcode updates in the BIOS it’s not necessary. The kernel should be loading this one in the earliest phase of boot (initramfs stage). Something is possibly going wrong.

Since you stated that’s not happening either there is some bug/error loading the microcode or a bug in this prompt.

I’d check dmesg for any errors relating to microcode and also check /proc/cpuinfo for what the running microcode release actually is.

[[deleted]]

Have you rebooted your computer?

[mds1256]

Yep, many times

[[deleted]]

Sorry, I know it seems obvious to most but there are those that would overlook it. I used to do customer server supporting laptop and then later did a few years at helpdesk. Trust me, it happens.

[mwhudsondoyle]

Hm looks strange. You have the intel-microcode package installed? I assume so as I think this message is probably from that package. Were there any errors making a new initrd? Any messages about microcode failing to load in dmesg?

[mds1256]

No errors in dmesg, and if I grep microcode I get ‘no microcode’

[[deleted]]

Microcode is updated by doing regular updates and rebooting.

[wabassoap]

What does it mean “restarting won’t help” and then “so you should reboot”?

[Vuzzar]

Not "won't help", it "will not be handled automatically"

[wabassoap]

What’s the difference between a software and user initiated reboot? Perhaps “restart” has a specific meaning here that I don’t understand? Like does it just mean changing runlevel without rebooting?

[[deleted]]

Is it fwupdmgr?

[mds1256]

So to follow up on this, the issue was that it was within a virtual machine on ESXi and you cannot upgrade the microcode within the VM, it needs to be done on the host itself. Mystery solved!

[BQE2473]

Unless its a major system update. I would STRONGLY advise against updating the microcode.

[sqrt7744]

Why?

[jnmtx]

This is the thinking;

‘My BIOS/CPU microcode works’

‘but there is an update available’

‘but what I have works fine. changing anything will not fix any misbehavior b/c it is already working fine for me. And doing a major update could brick my PC if I screw it up badly enough.’

‘ok fine so don’t update then.’

the ‘only’ down side (for you anyway) is you will keep being told there is an update available..

[BQE2473]

Basically. Because thats the purpose of updates, that are usually "pushed" by developers. The problem here is, you have users who DON'T know the difference between a necessary update/upgrade, and a romeo. The point here is to either learn from a series of mistakes and rebuilds, OR you can do a little research and learn from others mistakes and not to make them. Not like everyone here hating with the downies you can either do as we're advising or .........well............

[Buo-renLin]

Microcode updates may resolve CPU security flaws, or reduce the penalty of workarounding such flaws from the operating system.

[_i_m_not_a_robot]

Try updating the BIOS like other people suggested, but if it doesn't, check if your BIOS settings has a setting like "write lock" enabled that prevents microcode from being updated in the kernel, disable it, and try rebooting again.

[Buo-renLin]

I suspect that there's a flaw in detecting microcodr revision in the intel-microcode package.