I'll check the apache logs later today. Regarding ipxe.lkrn I know it works since the example http://boot.ipxe.org/demo/boot.php loads fine. The issue I believe is somewhere where it hands off to wimboot. The motherboard has UEFI and Legacy modes. I'm using legacy PXE.
> If you read the pined topics in the forum it explains the state. Didn't notice that discussion was moved to GitHub. I was checking by last reply and saw forum was somewhat active. On Sat, Jul 2, 2022, 10:54 AM Christian Iwata Nilsson, <nik...@gmail.com> wrote: > > > On Sat, 2 Jul 2022, 04:39 Alex Leo, <sir.alexandre....@gmail.com> wrote: > >> Hey everyone, >> >> Tried asking on forums but registration is closed, hopefully you're guys >> ok with asking the question here. >> I'm attempting to boot Windows PE environment using wimboot and iPXE >> I'm currently loading iPXE through PXELinux using the following in >> default. >> The iPXE_Test loads up correctly and dumps me into Linux. >> iPXE_Windows_http however hangs after >> http://192.168.10.123/windows/win2019/boot.ipxe ... ok >> with a blinking cursor. >> >> I have the following in the boot.ipxe >> #!ipxe >> >> kernel wimboot >> initrd boot/bcd BCD >> initrd boot/boot.sdi boot.sdi >> initrd sources/boot.wim boot.wim >> boot >> >> #default PXELinux.cfg >> label iPXE_TEST >> menu label iPXE_TEST >> kernel iPXE/ipxe.lkrn >> APPEND dhcp && chain http://boot.ipxe.org/demo/boot.php >> >> label iPXE_Windows_http >> menu label iPXE_Windows_http >> kernel iPXE/ipxe.lkrn >> APPEND dhcp && chain >> http://192.168.10.123/windows/win2019/boot.ipxe >> >> >> Anyone have ideas why it won't boot? I have wimboot in same directory as >> boot.ipxe >> >> Alex >> > > If you read the pined topics in the forum it explains the state. > > >> > Since you have ipxe.lkrn we know you are using pcbios. > Have you tried to use only ipxe to rule out or confirm that this issue is > pxelinux related? (For example by using ipxe.usb on flash drive) > > You could also try to manually do imgfetch on boot.ipxe and then run > imgstat and verify that it is detected as script. It is important that > #!ipxe is the first bytes of the script, and that there is no BOM sequence > or similar. > > >> >> _______________________________________________ >> ipxe-devel mailing list >> ipxe-devel@lists.ipxe.org >> https://lists.ipxe.org/mailman/listinfo/ipxe-devel > >
_______________________________________________ ipxe-devel mailing list ipxe-devel@lists.ipxe.org https://lists.ipxe.org/mailman/listinfo/ipxe-devel
