Intel Firmware Update

Via archnews and archwiki intel updates require some system changes.

  • install intel ucode

sh sudo pacman -S intel-ucode

  • Then, edit /etc/grub.d/10_linux to apply the updates during boot
  • Grubby Archers have two choices now (for other bootloaders see the archwiki)
    1. edit grub.cfg - overwritten on some updates
    2. or edit /etc/grub/10linux - some updates may no be applied
  • I like the latter, grub updates will create pacnew/pacsaves, so I'll have to go reconcile the difference. Editing grub.cfg along will be silently overwritten when it is generated again.
  • Note, lines with + need to be added, - removed.

sh if test -n "${initrd}" ; then + if test -f "${dirname}/intel-ucode.img"; then + ucode="${rel_dirname}/intel-ucode.img " + else + ucode= + fi # TRANSLATORS: ramdisk isn't identifier. Should be translated. message="$(gettext_printf "Loading initial ramdisk ...")" sed "s/^/$submenu_indentation/" << EOF echo '$(echo "$message" | grub_quote)' - initrd ${rel_dirname}/${initrd} + initrd ${ucode}${rel_dirname}/${initrd} EOF

  • Then regenerate grub.cfg:

sh grub-mkconfig -o /boot/grub/grub.cfg

  • Reboot, and check that everthing took.

dmesg | grep microcode

[ 0.000000] CPU0 microcode updated early to revision 0x29, date = 2013-06-12 [ 0.295049] CPU1 microcode updated early to revision 0x29, date = 2013-06-12 [ 0.308427] CPU2 microcode updated early to revision 0x29, date = 2013-06-12 [ 0.324988] CPU3 microcode updated early to revision 0x29, date = 2013-06-12 [ 0.741966] microcode: CPU0 sig=0x206a7, pf=0x2, revision=0x29 [ 0.741971] microcode: CPU1 sig=0x206a7, pf=0x2, revision=0x29 [ 0.741977] microcode: CPU2 sig=0x206a7, pf=0x2, revision=0x29 [ 0.741983] microcode: CPU3 sig=0x206a7, pf=0x2, revision=0x29 [ 0.742021] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba

I'm also thankful for this required intervention, because, while researching it I found out that btrfs is unstable on kernel 3.17.1

So I'll be staying with 3.16 on my laptop for a while. The problem seems to only be active when read-only snapshots are created, but I'll stay away for now to be safe.

Go Top
comments powered by Disqus