Hello, I do not know exactly on which mail list I should address this
problem so I post this here.
I have here a combined bzImage and UEFI binary and wanted to start it with
the linux/linuxefi command, but unfortunately GRUB2 does not recognize the
integrated UEFI binary and tries to start the b
Hello,
can you add the possibility to check if a hybrid application should be
loaded in EFI or kernel mode or if a setting possibility can be set? I
wanted to use linuxefi and intridefi, but grub told me it was a "kernel too
old" although it should be started in EFI mode.
I use linuxefi and in
-Ursprüngliche Nachricht-
Von: Daniel Kiper
Gesendet: Samstag, 23. Juni 2018 20:17
An: jame88f...@gmx.de
Cc: 'Daniel Kiper' ; grub-devel@gnu.org
Betreff: Re: Grub2 EFI: compatibility with wimboot
On Thu, Jun 21, 2018 at 06:34:41PM +0200, jame88f...@gmx.de wrote:
> Hello,
> the problem
Hello,
the problem is that with this method you can only load a wim file.
I have several windows ISOs that should boot separately.
Of course it would be really nice if you could load wimboot EFI with
parameters directly via grub2 EFI.
So with menutrys
P.S.
The combination of shim, grub2 EFI and w
No it is windows UEFI 64bit on a UEFI 64bit platform
it doesn't matter anyway because even if I try to boot only Wimboot EFI from
Grub2 EFI without parameters I also get a blackscreen.
I mean:
menuentry "Windows 7" {
linux /boot/wimboot/wimboot
}
I can't get linux16 to work in EFI, can I?
Okay,
wimboot works in Grub2 Legacy for example:
# Successfully boots
menuentry "Windows 7" {
set ISOpath="/img/windows_7.iso"
loopback loop $ ISOpath
linux16 /boot/wimboot/wimboot
initrd16 \
newc:bootmgr:(loop)/bootmgr \
newc:bcd:(lo
Hello,
I wanted to ask if it would be possible to make the compatibility with
wimboot in Grub2 EFI? currently only legacy works.
http://ipxe.org/wimboot
that would be really nice.
___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org
