> Date: Fri, 29 Aug 2014 13:02:10 +0100 > From: Michael Brown <mcb30 at ipxe.org> > To: Jason Jones <jason.s.jones at convergys.com>, "syslinux at zytor.com" > <syslinux at zytor.com> > Subject: Re: [syslinux] PXE booting WinPE with UEFI architecture > Message-ID: <54006BC2.3090703 at ipxe.org> > Content-Type: text/plain; charset=UTF-8; format=flowed > > On 28/08/14 19:38, Jason Jones wrote: > > Anyone have luck with pxechn32 and bootmgfw.efi? > > > > I'm getting the "Unable to retrieve first package" issue as reported byothers.> > > > Really, any advice for UEFI booting into a winpe environment off ofpxelinux 6.03 would be beneficial.> > As it happens, I released a new version of wimboot with support for UEFI > yesterday. The documentation isn't up yet, but you can get the code > from http://git.ipxe.org/release/wimboot and see the (not-yet-UEFIfied) > docs at http://ipxe.org/wimboot. > > MichaelWow, that totally confuses me! I am fat & happy UEFI-booting Fedora 20, RHEL7 et al on syslinux 6.03-pre19. I'm using syslinux/efi64/efi/syslinux.efi as the bootloader. Here's an example stanza in my pxelinux.cfg/default file: LABEL Fedora 20 interactive MENU LABEL ^fedora 20 MENU INDENT 3 KERNEL boot/fedora/vmlinuz APPEND initrd=/boot/fedora/initrd.img ramdisk_size=10000 But chain-loading into WinPE would be useful too. In order to use "wimboot", I have to use ./efi64/com32/modules/pxechn.c32 to chain-load into ipxe? As so: LABEL WinPE MENU LABEL WinPE MENU INDENT 3 COM32 pxechn.c32 APPEND http://192.168.1.100/undionly.kpxe And then in the same location, I put this boot.ipxe file and all support files: #!ipxe kernel wimboot initrd bootmgr bootmgr initrd boot/bcd BCD initrd boot/boot.sdi boot.sdi initrd http://<SCCM-server>/boot.wim boot.wim imgstat boot Is that all correct? Spike
On Fri, Aug 29, 2014 at 8:01 PM, Spike White <spikewhitetx at gmail.com> wrote:> But chain-loading into WinPE would be useful too.> In order to use "wimboot", I have to use ./efi64/com32/modules/pxechn.c32 > to chain-load into ipxe? As so:pxechn.c32 contains BIOS-only code and is not going to work in any EFI environment.> LABEL WinPE > MENU LABEL WinPE > MENU INDENT 3 > COM32 pxechn.c32 > APPEND http://192.168.1.100/undionly.kpxeundionly.kpxe will likely be BIOS-only also.> And then in the same location, I put this boot.ipxe file and all support > files: > > #!ipxe > kernel wimboot > initrd bootmgr bootmgr > initrd boot/bcd BCD > initrd boot/boot.sdi boot.sdi > initrd http://<SCCM-server>/boot.wim boot.wim > imgstat > bootLikely if you transform the above to Syslinux format. LABEL wimboot LINUX wimboot APPEND initrd=bootmgr,boot/bcd,boot/boot.sdi,http://<sccm-server>/boot.wim -- -Gene
On 30/08/14 02:00, Gene Cumm wrote:>> And then in the same location, I put this boot.ipxe file and all support >> files: >> >> #!ipxe >> kernel wimboot >> initrd bootmgr bootmgr >> initrd boot/bcd BCD >> initrd boot/boot.sdi boot.sdi >> initrd http://<SCCM-server>/boot.wim boot.wim >> imgstat >> boot > > Likely if you transform the above to Syslinux format. > > LABEL wimboot > LINUX wimboot > APPEND initrd=bootmgr,boot/bcd,boot/boot.sdi,http://<sccm-server>/boot.wimFor UEFI, wimboot acts as a UEFI binary and expects to be able to access the initrd files via EFI_SIMPLE_FILE_SYSTEM_PROTOCOL. This allows a boot of iPXE->wimboot->WinPE using an iPXE script such as: #!ipxe kernel wimboot initrd bootmgr bootmgr initrd EFI/Boot/bootx64.efi bootx64.efi initrd Boot/BCD BCD initrd Boot/boot.sdi boot.sdi initrd sources/boot.wim boot.wim boot Note that the same script (and the same wimboot binary) should work for both BIOS and UEFI systems. For syslinux, I would guess that you could place the bootx64.efi, BCD, boot.sdi, and boot.wim files in the same directory as the wimboot binary, and then just invoke wimboot as a UEFI binary (_not_ as a Linux kernel). I don't know the configuration file syntax for this, sorry. Michael