[SOLVED] Microcode with Linux 3.17

Question

The Update to Linux 3.17 triggered this Announcement
Microcode on Intel CPUs is no longer loaded automatically, as it needs to be loaded very early in the boot process. This requires adjustments in the bootloader. If you have an Intel CPU, please follow the instructions in the wiki.
There, for Grub:
For the time being, you can manually add /intel-ucode.img in your grub.cfg as follows:
echo 'Loading initial ramdisk ...'
initrd /intel-ucode.img /initramfs-linux.img
I know this matches that post in arch-dev public, but IMHO it should be
echo 'Loading initial ramdisk ...'
initrd /boot/intel-ucode.img /boot/initramfs-linux.img
at least that worked for me:
# dmesg | grep microcode
[ 0.000000] CPU0 microcode updated early to revision 0x1c, date = 2014-07-03
[ 0.126060] CPU2 microcode updated early to revision 0x1c, date = 2014-07-03
[ 0.385231] microcode: CPU0 sig=0x40651, pf=0x40, revision=0x1c
[ 0.385238] microcode: CPU1 sig=0x40651, pf=0x40, revision=0x1c
[ 0.385248] microcode: CPU2 sig=0x40651, pf=0x40, revision=0x1c
[ 0.385257] microcode: CPU3 sig=0x40651, pf=0x40, revision=0x1c
[ 0.385305] microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
(And is really trivial, yes.)
But before I mess around in the wiki (on a recent update relevant topic!), I'd like to discuss this here first.
So what do you mean, should "/boot" be added to the wiki instructions for microcode in Grub?
Last edited by Carl Karl (2014-10-22 23:14:19)

Answer 1

There is a simple rule.
If you have a separate /boot partition then your 'set root=...' will point to that partition, and the .img files will be at the root of the boot partition hence the /intel-ucode.img.
If you don't have a separate /boot partition then your 'set root=...' will point to / and the .img files will be in /boot/...