This got me closer, but it got to "Encapsulating winpe.wim..." and
never went through the rest of the way. Ultimately PXELINUX apparently timed out
and the machine rebooted.
Here is relative portion of pxelinux:
LABEL SCCM OSD Boot
MENU LABEL ^2. SCCM OSD Boot
com32 linux.c32
append wimboot initrdfile=bootmgr.exe,BCD,boot.sdi,winpe.wim
TEXT HELP
Deployment of Operating System via SCCM.
Jason Jones
Sr. Associate, Network Services | End User Computing
3947 N Oak St Ext | Valdosta, GA 31605
O +15137844955
E jason.s.jones at convergys.com
-----Original Message-----
From: Michael Brown [mailto:mcb30 at ipxe.org]
Sent: Friday, August 29, 2014 8:02 AM
To: Jason Jones; syslinux at zytor.com
Subject: Re: [syslinux] PXE booting WinPE with UEFI architecture
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 by others.
>
> Really, any advice for UEFI booting into a winpe environment off of
pxelinux 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.
Michael
________________________________
NOTICE: The information contained in this electronic mail transmission is
intended by Convergys Corporation for the use of the named individual or entity
to which it is directed and may contain information that is privileged or
otherwise confidential. If you have received this electronic mail transmission
in error, please delete it from your system without copying or forwarding it,
and notify the sender of the error by reply email or by telephone (collect), so
that the sender's address records can be corrected.
On 04/09/14 13:31, Jason Jones wrote:> This got me closer, but it got to "Encapsulating winpe.wim..." and never went through the rest of the way. Ultimately PXELINUX apparently timed out and the machine rebooted. > > Here is relative portion of pxelinux: > > LABEL SCCM OSD Boot > MENU LABEL ^2. SCCM OSD Boot > com32 linux.c32 > append wimboot initrdfile=bootmgr.exe,BCD,boot.sdi,winpe.wimThe UEFI version of wimboot does not expect to find its files wrapped up into an initrd; it uses the EFI_SIMPLE_FILE_SYSTEM_PROTOCOL to retrieve them from the underlying media. It would be fairly simple to extend the UEFI version of wimboot to handle an initrd, but I have no immediate plans to do so. Michael
> -----Original Message----- > > 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 by others. > > Really, any advice > for UEFI booting into a winpe environment off of pxelinux 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. > > Michael > > ________________________________ > This got me closer, but it got to "Encapsulating winpe.wim..." and > never went through the rest of the way. Ultimately PXELINUX > apparently timed out and the machine rebooted. > > Here is relative portion of pxelinux: > > LABEL SCCM OSD Boot > MENU LABEL ^2. SCCM OSD Boot > com32 linux.c32 > append wimboot initrdfile=bootmgr.exe,BCD,boot.sdi,winpe.wim > TEXT HELP > Deployment of Operating System via SCCM. > > Jason Jones1_ Your LABEL directive is using space characters. For the LABEL directive, either limit the label to unique one-word type-able characters, or at least replace the space characters with underscores. 2_ Are you sure your "bootmgr.exe" is correct? Even for a UEFI system? 3_ Are all those files located in the same (working) directory as all your PXELINUX files? 4_ Are you using the *latest* Syslinux 6.03-pre* version? At the moment, the latest is 6.03-pre20 (and you should avoid using any prior 5.xx or 6.xx version, unless specifically requested for some test). 5_ Regarding files from Syslinux, are you using all files from the same exact version? Are you using pre-built binaries from kernel.org? 6_ When you mention UEFI architecture, I guess you are referring to clients only (not servers), right? 7_ Are the clients really configured for UEFI mode? Is there any chance they could be (mis)configured for CSM? 8_ Have you tried with lpxelinux.0 instead of pxelinux.0? 9_ Are you able to successfully boot anything else (so to discard a possible sever misconfiguration)? The above comments (they are not really questions) most probably won't resolve all the issues, but perhaps they might give you some basic points to consider. Regards, Ady. A: Because it messes up the order in which people normally read text, especially the archives of mailing lists. Q: Why is Top-posting such a bad thing?