Am 21.10.2014 um 11:36 schrieb Mike Cloaked: > On Mon, Oct 20, 2014 at 5:44 PM, Thomas Bächler <thomas@xxxxxxxxxxxxx> > wrote: > >> >> These changes have been done precisely to avoid these problems, the >> first link and its responses summarize the situation pretty well. >> >> > The file at https://www.kernel.org/doc/Documentation/x86/early-microcode.txt > gives a method that should allow creating a combined initrd img file that > anyone booting with refind EFI may be able to test. There are suggested > methods to implement early microcode loading for the other main bootloaders > in the arch wiki, but until now for refind it seems not to have been > verified to work. It would be nice to see verification that early microcode > loading has been successful using all the main bootloaders/bootmanagers, as > well as direct efistub boot. A 2 minute Google search indicates that refind merely appends the initrd as a kernel command line option (initrd=) - refind, like gummiboot, is merely an EFI bootmanager and not a bootloader and thus relies on the kernel's EFIstub feature. Therefore, refind does not load the initrd itself, but delegates that task to the kernel.
Attachment:
signature.asc
Description: OpenPGP digital signature
