On Saturday, August 15, 2015 08:31:42 PM Jordan Uggla wrote:
> Specifically, while Mark entered something like "initrd
> /boot/initramfs-foo-bar", and everything he had typed was echoed back
> to him on screen as expected, the error message he received was (if I
> recall correctly) something about
On Fri, Aug 14, 2015 at 11:29 PM, Andrei Borzenkov wrote:
> On 14.08.2015 09:45, Mark Lee wrote:
>>
>> To all,
>>
>> I've encountered a bug when using GRUB2 + OVMF + QEMU on Arch Linux 64
>> bit.
>> The issue can be reproduced when running the latest git code from grub as
>> well.
>>
>> ISSUE: Ker
The following are two use cases from Rajat Jain :
1) We have a board that boots Linux and this board itself can be plugged into
one of different chassis types. We need to pass different parameters to the
kernel based on the "CHASSIS_TYPE" information that is passed by the bios in
the DMI / SMBI
If both SMBIOS v2 and v3 entry point structures are found, both are
registered instead of preferring one version since they can point
to different tables at different memory locations.
This also modifies the fakebios command so that the entire SMBIOS
(v2) EPS is copied instead of just the intermed
On Saturday, August 15, 2015 09:29:55 AM Andrei Borzenkov wrote:
> Once kernel is loaded, GRUB task is over. Why do you think it is GRUB issue?
This seems to only occur when using GRUB + OVMF + QEMU. Transferring test.img
to a disk and booting it in hardware UEFI is fine.
Regards,
Mark
signatu
