On 07/14/2016 12:49 PM, Leandro Gustavo Biss Becker wrote:
Analyzing the source code for both versions, I found an interesting change on
grub-core\loader\efi\chainloader.c:382 ( I do not know if this change is
broking what I need). In the newer version of grub, there is a call to
grub_device_c
Thank you all for the replies and sorry my late reply.
Gordon, I downgraded a little bit, from f24
(grub2-efi-2.02-0.34.fc24.x86_64.rpm) to f22
(grub2-efi-2.02-0.18.fc22.x86_64.rpm) and everything is working for my needs.
Chris, thank you for you tips, all the used modules are builtin.
Analyzi
On Tue, Jul 12, 2016 at 5:25 PM, Chris Murphy wrote:
> My understanding is that PXE is booting is going to talk to a DHCP
> server which should be configured to recognize UEFI specifically, so
> it can hand over the proper kind of bootloader, in this case an EFI
> version of GRUB2. What I don't kn
On Tue, Jul 12, 2016 at 11:52 AM, Leandro Gustavo Biss Becker
wrote:
> Using older versions of GRUB2 it is working, but with newer versions, ...
Just so that we're clear, if you boot this computer using an older
version of GRUB2 from tftp, your custom application works, but if you
then use the ne
On Tue, Jul 12, 2016 at 12:52 PM, Leandro Gustavo Biss Becker
wrote:
> Hello.
>
> I'm trying to use a newer version of GRUB2 (grub2-efi-2.02-0.34.fc24.x86_64)
> for UEFI PXE booting Linux (Clonezilla) and also a custom UEFI application
> (custom shell) that needs access to the TCP4 UEFI stack in
Hello.
I'm trying to use a newer version of GRUB2 (grub2-efi-2.02-0.34.fc24.x86_64)
for UEFI PXE booting Linux (Clonezilla) and also a custom UEFI application
(custom shell) that needs access to the TCP4 UEFI stack in firmware (depends of
the scenario). Using older versions of GRUB2 it is worki
