1 |
On Wednesday 01 Feb 2017 00:55:01 Marc Joliet wrote: |
2 |
> On Sunday 29 January 2017 13:51:39 Mick wrote: |
3 |
> > Hi All, |
4 |
> > |
5 |
> > I am trying out a systemd installation on a MackBook Pro and I am not sure |
6 |
> > the documentation on systemd + microcode is entirely correct. So, I read |
7 |
> > here: |
8 |
> > |
9 |
> > https://wiki.gentoo.org/wiki/Intel_microcode#systemd |
10 |
> > |
11 |
> > that the "microcode loader is set as a module in the kernel |
12 |
> > configuration". |
13 |
> > However, my kernel configuration is not offering this option. Both 'CPU |
14 |
> > microcode loading support' and 'Intel microcode loading support' can only |
15 |
> > be set as built in elements. I am not using an initramfs (yet) so I |
16 |
> > wonder how I should go about this. |
17 |
> |
18 |
> AIUI these days the microcode is supposed to be put in the initramfs and |
19 |
> loaded from there during early boot (I read this somewhere, but don't |
20 |
> remember where). Dracut takes care of this, e.g., the initramfs on my |
21 |
> laptop contains a microcode blob: |
22 |
> |
23 |
> # lsinitrd /boot/initramfs-4.9.6-gentoo.img|grep -i micro |
24 |
> drwxr-xr-x 1 root root 0 Jan 27 01:14 kernel/x86/microcode |
25 |
> -rw-r--r-- 1 root root 983040 Jan 27 01:14 |
26 |
> kernel/x86/microcode/GenuineIntel.bin |
27 |
> |
28 |
> The third journal entry on said laptop is then: |
29 |
> |
30 |
> Jan 30 20:42:17 localhost kernel: microcode: microcode updated early to |
31 |
> revision 0x4, date = 2013-06-28 |
32 |
> |
33 |
> So it looks to me like the kernel loads it autonomously, and the reason to |
34 |
> put the file in the initramfs is for the microcode to get updated as early |
35 |
> as possible (before the kernel has to read from disk). |
36 |
> |
37 |
> HTH |
38 |
|
39 |
Thanks Marc, I did read the same in the Wiki, where it also mentioned that |
40 |
with systemd all you need to do is mark the microcode as modules in the kernel |
41 |
and systemd will load them at boot time. I did try (twice) to generate a cpio |
42 |
with the blob, but the initrd wouldn't allow the efi stub to boot for some |
43 |
reason. I will revisit this in the next day or two and see if it can work |
44 |
better this time. |
45 |
-- |
46 |
Regards, |
47 |
Mick |