Am 12.10.2014 um 16:52 schrieb Christian Hesse:
Successfully tested with grub (1:2.02.beta2-4). You need something like this
in grub.cfg:
echo'Loading Intel ucode update and initial ramdisk ...'
initrd /intel-ucode.img /initramfs-linux.img
I edited grub.cfg manually,
On Sat, 18 Oct 2014 19:38:27 +0200
Thomas Bächler tho...@archlinux.org wrote:
Am 12.10.2014 um 16:52 schrieb Christian Hesse:
Successfully tested with grub (1:2.02.beta2-4). You need something
like this in grub.cfg:
echo'Loading Intel ucode update and initial ramdisk ...'
On 12/10/14 18:13, Evangelos Foutras wrote:
On 12/10/14 15:28, Thomas Bächler wrote:
For AMD, a similar mechanism is available, but since I don't own an AMD
CPU, I cannot implement this. This causes problems, since the microcode
update is no longer triggered automatically on boot (since
Intel released a new microcode update that disables an instruction on
Haswell CPUs. However, Linux doesn't handle this very well and in
combination with our glibc version, this essentially crashes your system.
The solution is to use the new early microcode update mechanism that
was introduced
On 12/10/14 15:28, Thomas Bächler wrote:
For AMD, a similar mechanism is available, but since I don't own an AMD
CPU, I cannot implement this. This causes problems, since the microcode
update is no longer triggered automatically on boot (since microcode is
no longer a module). If you want to
Am 12.10.2014 um 16:52 schrieb Christian Hesse:
Successfully tested with grub (1:2.02.beta2-4). You need something like this
in grub.cfg:
echo'Loading Intel ucode update and initial ramdisk ...'
initrd /intel-ucode.img /initramfs-linux.img
I edited grub.cfg manually,
6 matches
Mail list logo
