Author: ken
Date: Wed Mar 14 17:52:36 2018
New Revision: 19951
Log:
Update intel microcode to 20180312.
Modified:
trunk/BOOK/introduction/welcome/changelog.xml
trunk/BOOK/postlfs/config/firmware.xml
Modified: trunk/BOOK/introduction/welcome/changelog.xml
==============================================================================
--- trunk/BOOK/introduction/welcome/changelog.xml Wed Mar 14 17:40:52
2018 (r19950)
+++ trunk/BOOK/introduction/welcome/changelog.xml Wed Mar 14 17:52:36
2018 (r19951)
@@ -45,6 +45,15 @@
<para>March 15th, 2018</para>
<itemizedlist>
<listitem>
+ <para>[ken] - Update intel microcode to 20180312 (spectre v2
+ mitigation for SandyBridge and later). Please note that for some
+ models, particularly Skylake, currently-available kernels may
+ disregard the mitigation because of issues with the previous (now
+ withdrawn) version. That will hopefully be fixed in a few days,
+ but wil then require a kernel upgrade. Fixes
+ <ulink url="&blfs-ticket-root;10300">#10300</ulink>.</para>
+ </listitem>
+ <listitem>
<para>[timtas] - Explain how to build network-manager-applet without
gobject-introspection and gtk-doc.</para>
</listitem>
</itemizedlist>
Modified: trunk/BOOK/postlfs/config/firmware.xml
==============================================================================
--- trunk/BOOK/postlfs/config/firmware.xml Wed Mar 14 17:40:52 2018
(r19950)
+++ trunk/BOOK/postlfs/config/firmware.xml Wed Mar 14 17:52:36 2018
(r19951)
@@ -130,14 +130,18 @@
<para>The first step is to get the most recent version of the Intel
microcode. This must be done by navigating to
- <ulink
url='https://downloadcenter.intel.com/download/27337/Linux-Processor-Microcode-Data-File'/>
+ <ulink
url='https://downloadcenter.intel.com/download/27591/Linux-Processor-Microcode-Data-File'/>
and following the instructions there. As of this writing the most recent
- version of the microcode is <filename>microcode-20171117.tgz</filename>.
+ version of the microcode is <filename>microcode-20180312.tgz</filename>.
Extract this file in the normal way to create an
<filename>intel-ucode</filename>
- directory, containing various blobs with names in the form
XX-YY-ZZ.</para>
+ directory, containing various blobs with names in the form XX-YY-ZZ.
+ This tarball does not contain a top-level directory, two files
+ (microcode.dat which is the old-style of updates, still used by some
+ linux distros, and releasenote) will be extracted into the current
+ directory.</para>
<note><para>The above URL may not be the latest page. If it is not,
- a line at the top of the list will direct you to the latest page.
+ a line at the top of the page will direct you to the latest page.
</para></note>
<para>Now you need to determine your processor's identity to see if there
@@ -180,8 +184,8 @@
<para>This example from the Haswell i7 which was released in Q2 2014 and
is
not affected by the TSX errata shows it has been updated from revision
0x19
- in the BIOS/UEFI (which this version of hte kernel now complains about)
to
- revision 0x22. Unlike in older kernels, the individual CPUs are not
separately
+ in the BIOS/UEFI (which this version of the kernel now complains about)
to
+ revision 0x24. Unlike in older kernels, the individual CPUs are not
separately
reported:</para>
<screen><literal>[ 0.000000] Linux version 4.15.3 (ken@plexi) (gcc version
7.3.0 (GCC))
@@ -191,7 +195,7 @@
please update microcode to version: 0x22 (or later)
[ 0.482712] microcode: sig=0x306c3, pf=0x2, revision=0x19
[ 0.482937] microcode: Microcode Update Driver: v2.2.
-[ 402.668612] microcode: updated to revision 0x22, date =
2017-01-27</literal></screen>
+[12624.259297] microcode: updated to revision 0x24, date =
2018-01-21</literal></screen>
<para>If the microcode was not updated, there is no new microcode for
this system's processor. If it did get updated, you can now proceed to
<xref
@@ -305,12 +309,12 @@
kernel, showing that the first notification comes before the kernel
version
is mentioned:</para>
-<screen><literal>[ 0.000000] microcode: microcode updated early to revision
0x22, date = 2017-01-27
+<screen><literal>[ 0.000000] microcode: microcode updated early to revision
0x24, date = 2018-01-21
[ 0.000000] Linux version 4.15.3 (ken@plexi) (gcc version 7.3.0 (GCC))
#3 SMP PREEMPT Fri Feb 23 05:06:50 GMT 2018
[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.15.3-sda6 root=/dev/sda6 ro
-[ 0.489478] microcode: sig=0x306c3, pf=0x2, revision=0x22
-[ 0.489747] microcode: Microcode Update Driver: v2.2.</literal></screen>
+[ 0.484409] microcode: sig=0x306c3, pf=0x2, revision=0x24
+[ 0.484575] microcode: Microcode Update Driver: v2.2.</literal></screen>
<para>An AMD example:</para>
--
http://lists.linuxfromscratch.org/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
