On Fri, Jun 15, 2018 at 07:14:29PM +0200, jame88f...@gmx.de wrote:
> 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:(loop)/boot/bcd \
> newc:boot.sdi:(loop)/boot/boot.sdi \
> newc:boot.wim:(loop)/sources/boot.wim
> }
>
> Because I can not use linux16 in Grub2 EFI, I use only linux but this
> creates a blackscreen (with the chaining it does not work either).
>
> I also asked the developers of wimboot they said grub2 could not load EFI
> binarys directly.
> So I ask, is that the case?
>
> P.S.
> I found this maybe this helps:
> https://superuser.com/questions/1093986/boot-with-wimboot-a-windows-x64-imag
> e-on-uefi-32-bits
Wait, are you trying to run Windows UEFI x64 on UEFI x32 (to be precise
ia32) platform? It seems to me that such configs are not supported.
Additionally, paths above show that you are trying to use legacy
BIOS stuff. It will not run on UEFI platforms. I think that you
should use more or less something like that (+/- /amd64 part):
- /amd64/boot/boot.sdi,
- /amd64/efi/microsoft/boot/bcd,
- /amd64/efi/boot/bootx64.efi
- /amd64/winpe.wim.
So, more or less there is a chance that the issue is not related to GRUB2.
Daniel
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
