SlackBuilds Repository

The microcode data file contains the latest microcode definitions for all Intelprocessors. Intel releases microcode updates to correct processor behavior asdocumented in the respective processor specification updates. While the regularapproach to getting this microcode update is via a BIOS upgrade, Intel realizesthat this can be an administrative hassle. The Linux operating system and VMwareESX products have a mechanism to update the microcode after booting.

This SlackBuild repackages the official Intel microcode archive.

The "microcode.dat" file is placed under /lib/firmware/microcode.dat and can belater uploaded using microcode_ctl utility (available from SlackBuilds.org).This approach (microcode.dat + microcode_ctl) is kept for compatibility reasonsand should be avoided whenever possible. * Use the solution described below. *

If the iucode_tool (available from SlackBuilds.org) is installed on the system,this SlackBuild will:

1) write the microcodes with the file names as expected by the Linux kernel firmware loader and place them under /lib/firmware/intel-ucode directory. The correct microcode is uploaded when the Intel microcode kernel's module is loaded.

2) write the microcodes to an early initramfs archive: /boot/intel-ucode.cpio This archive should be prepended to the regular initramfs to allow the kernel to update processor microcode very early during system boot.

To get started with early microcode loading, please have a look at:1) https://www.kernel.org/doc/Documentation/x86/early-microcode.txt2) iucode_tool man page, especially about --write-earlyfw option.

For example, on my system that uses syslinux, to load the microcode earlyduring the boot process, the configuration file reads something like that: