Changeset 3d0e2ff for postlfs/config/firmware.xml
- Timestamp:
- 03/15/2018 12:52:36 AM (6 years ago)
- 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
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
postlfs/config/firmware.xml
r5d7469f9 r3d0e2ff 131 131 <para>The first step is to get the most recent version of the Intel 132 132 microcode. This must be done by navigating to 133 <ulink url='https://downloadcenter.intel.com/download/27 337/Linux-Processor-Microcode-Data-File'/>133 <ulink url='https://downloadcenter.intel.com/download/27591/Linux-Processor-Microcode-Data-File'/> 134 134 and following the instructions there. As of this writing the most recent 135 version of the microcode is <filename>microcode-201 71117.tgz</filename>.135 version of the microcode is <filename>microcode-20180312.tgz</filename>. 136 136 Extract this file in the normal way to create an <filename>intel-ucode</filename> 137 directory, containing various blobs with names in the form XX-YY-ZZ.</para> 137 directory, containing various blobs with names in the form XX-YY-ZZ. 138 This tarball does not contain a top-level directory, two files 139 (microcode.dat which is the old-style of updates, still used by some 140 linux distros, and releasenote) will be extracted into the current 141 directory.</para> 138 142 139 143 <note><para>The above URL may not be the latest page. If it is not, 140 a line at the top of the listwill direct you to the latest page.144 a line at the top of the page will direct you to the latest page. 141 145 </para></note> 142 146 … … 181 185 <para>This example from the Haswell i7 which was released in Q2 2014 and is 182 186 not affected by the TSX errata shows it has been updated from revision 0x19 183 in the BIOS/UEFI (which this version of hte kernel now complains about) to184 revision 0x2 2. Unlike in older kernels, the individual CPUs are not separately187 in the BIOS/UEFI (which this version of the kernel now complains about) to 188 revision 0x24. Unlike in older kernels, the individual CPUs are not separately 185 189 reported:</para> 186 190 … … 192 196 [ 0.482712] microcode: sig=0x306c3, pf=0x2, revision=0x19 193 197 [ 0.482937] microcode: Microcode Update Driver: v2.2. 194 [ 402.668612] microcode: updated to revision 0x22, date = 2017-01-27</literal></screen>198 [12624.259297] microcode: updated to revision 0x24, date = 2018-01-21</literal></screen> 195 199 196 200 <para>If the microcode was not updated, there is no new microcode for … … 306 310 is mentioned:</para> 307 311 308 <screen><literal>[ 0.000000] microcode: microcode updated early to revision 0x2 2, date = 2017-01-27312 <screen><literal>[ 0.000000] microcode: microcode updated early to revision 0x24, date = 2018-01-21 309 313 [ 0.000000] Linux version 4.15.3 (ken@plexi) (gcc version 7.3.0 (GCC)) 310 314 #3 SMP PREEMPT Fri Feb 23 05:06:50 GMT 2018 311 315 [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.15.3-sda6 root=/dev/sda6 ro 312 [ 0.48 9478] microcode: sig=0x306c3, pf=0x2, revision=0x22313 [ 0.48 9747] microcode: Microcode Update Driver: v2.2.</literal></screen>316 [ 0.484409] microcode: sig=0x306c3, pf=0x2, revision=0x24 317 [ 0.484575] microcode: Microcode Update Driver: v2.2.</literal></screen> 314 318 315 319 <para>An AMD example:</para>
Note:
See TracChangeset
for help on using the changeset viewer.