[solved] misssing microcode update messages in dmesg

toralf · Last edited by toralf on Sat Mar 17, 2018 8:34 pm; edited 1 time in total

I run the same kernel 4.15.10 at my server (i7) and at my ThinkPad (i5). The server tells me in dmesg, that the microcode is up to date :

bunder · Bodhisattva Joined: 10 Apr 2004 Posts: 5934

wasn't 2018-01-18 rescinded? i would try upgrading (or downgrading).

toralf · Posted: Sat Mar 17, 2018 10:22 am Post subject:

NeddySeagoon · Posted: Sat Mar 17, 2018 10:45 am Post subject:

toralf,

I have a feeling that modules no longer work for Intel microcode updates.

The update has to be done very early in the boot process, so built in is required.
This is not based on experience as my only Intel CPU is an Atom N270.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

toralf · Posted: Sat Mar 17, 2018 11:14 am Post subject:

krinn · Watchman Joined: 02 May 2003 Posts: 7470

You guys makes it unclear.
As for me you speak like module should be off.

Just to make it clearer : keep using module support, but for microcode update you cannot load it "later" to update the cpu microcode ; it must be done early, so module support is need to handle the module and the module need to be set in CONFIG_EXTRA_FIRMWARE for early update.

And i suppose your "I simply deactivated the modules" mean "i have switch my WLAN from module to build-in"?
Because obviously if you had only deactivate the module, your WLAN has no longer any drivers to work with and anyone could explains the mystery why it is no longer shown after boot

NeddySeagoon · Posted: Sat Mar 17, 2018 12:00 pm Post subject:

Module support can be used for other things.

For Intel firmware updates, the option must be selected as built into the kernel and the required firmware must be included in the kernel too.

There is no need to change anything wifi related.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

krinn · Watchman Joined: 02 May 2003 Posts: 7470

Yeah must be my understanding of English but also could be it's a few too subtle for common non native users.
Anyway, i was thinking it should be a few clearer what the "disable" really mean in that case for non native like me, where the "disable" is not really disabling anything.

toralf · Posted: Sat Mar 17, 2018 3:33 pm Post subject:

Well, I had

NeddySeagoon · Posted: Sat Mar 17, 2018 5:27 pm Post subject:

toralf,

There is no need to make a monolthic kernel.
You need to build in your wifi module and firmware if you want to do that.

Going forward, you need to make sure that new firmware is installed before you build your kernel.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

toralf · Posted: Sat Mar 17, 2018 5:54 pm Post subject:

Hu · Moderator Joined: 06 Mar 2007 Posts: 21633

It's possible that there is a kernel limitation here, but it looks to me more like a communication problem. According to the earlier posts, the microcode update must be built-in. If it is not, it initializes too late to be possible, so it is skipped and you do not get the full mitigations. You attempted to make the entire kernel monolithic, which works, but is overkill for that problem. More importantly, while wireless can be made to work in a monolithic kernel, it is more trouble, at least for some cards.

My advice is go back to a modular kernel, but make all microcode related drivers and firmware built-in.

toralf · Posted: Sat Mar 17, 2018 9:37 pm Post subject: