Running Arch Linux on a machine with Intel processor requires loading processor microcode (intel-ucode.img) very early in the boot process, ahead of initial ram disk. So the initrd line would need to look as follows:
initrd /boot/intel-ucode.img /boot/initramfs-linux.img
Below is my menu.lst:
title Arch Linux root (hd1,4) kernel /boot/vmlinuz-linux root=UUID=c0af9bh9-39c8-519g-cz4j-87684beg7958 ro # intel processors only initrd /boot/intel-ucode.img /boot/initramfs-linux.img
Everything boots and works ok with Grub4Dos v0.4.5c-2014-12-24. Here is the boot log from my Core 2 Duo test machine:
journalctl --boot=d667939e4baf4c7397a9d2ffca2f6742 --output=short-precise
-- Logs begin at Thu 2017-01-26 03:44:17 EST, end at Wed 2017-02-01 22:45:48 EST. -- Feb 01 22:45:07.527460 dc77 kernel: microcode: CPU0 microcode updated early to revision 0x5d, date = 2010-10-02 .... Feb 01 22:45:07.530905 dc77 kernel: microcode: CPU1 microcode updated early to revision 0x5d, date = 2010-10-02 .... Feb 01 22:45:07.553866 dc77 kernel: microcode: CPU0 sig=0x6f2, pf=0x1, revision=0x5d Feb 01 22:45:07.553888 dc77 kernel: microcode: CPU1 sig=0x6f2, pf=0x1, revision=0x5d Feb 01 22:45:07.553910 dc77 kernel: microcode: Microcode Update Driver: v2.01 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
However, I'm just not sure if two img files placed on a single initrd line are officially supported, or should two separate initrd lines be used instead. Another option mentioned in ArchWiki would be to merge both image files and then have standard initrd line with a single img file:
# concatenate both img files cat /boot/intel-ucode.img /boot/initramfs-linux.img > /boot/initramfs-merged.img # use standard initrd with a single img file initrd /boot/initramfs-merged.img
Below is the link to ArchWiki:
https://wiki.archlin...x.php/Microcode
Edited by Kirkx, 02 February 2017 - 08:50 AM.