Changeset 3d0e2ff for postlfs/config

Timestamp:

03/15/2018 12:52:36 AM (6 years ago)

Author:

Ken Moffat <ken@…>

Branches:

10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal

Children:

0dc1b7b

Parents:

5d7469f9

Message:

Update intel microcode to 20180312.

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@19951 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:

• postlfs/config/firmware.xml (modified) (4 diffs)

postlfs/config/firmware.xml

@@ -131 +131 @@
      <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>
 
@@ -181 +185 @@
       <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>
 
@@ -192 +196 @@
 [    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
@@ -306 +310 @@
       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>