similar to: Updated status on UEFI compliant version of the pxechn-module

Hi, Ok, when can we then anticipate pxe-chaining to be possible with syslinux under the UEFI architecture? Are there any plans to implement both correct interfacing to UEFI as well as the issue of arbitrary UEFI images? Haven't tried to read the UEFI-specification as it is sub 3000-pages long, so I am a bit in the dark as to the changes in architecture from BIOS to UEFI. It has been

Hi, ________________________________________ From: Gene Cumm <gene.cumm at gmail.com> Sent: Wednesday, March 16, 2016 00:56 To: Jan Frode J?ger Cc: syslinux at zytor.com Subject: Re: [syslinux] Updated status on UEFI compliant version of the pxechn-module On Tue, Mar 15, 2016 at 9:32 AM, Jan Frode J?ger <jan.frode.jaeger at ntnu.no> wrote: Without trying to figure out where data is

On Tue, Mar 15, 2016 at 9:32 AM, Jan Frode J?ger <jan.frode.jaeger at ntnu.no> wrote: > Hi, > > Ok, when can we then anticipate pxe-chaining to be possible with syslinux under the UEFI architecture? Are there any plans to implement both correct interfacing to UEFI as well as the issue of arbitrary UEFI images? Haven't tried to read the UEFI-specification as it is sub 3000-pages

On Tue, Mar 15, 2016 at 3:51 AM, Jan Frode J?ger <syslinux at zytor.com> wrote: > Hi, > > > I have browsed through your syslinux archives and see that the issue of an UEFI compliant version of the pxechn-module has come up several times: > > > http://www.syslinux.org/archives/2014-August/022611.html > > http://www.syslinux.org/archives/2015-March/023320.html >

On Wed, Mar 16, 2016 at 2:58 AM, Jan Frode J?ger <jan.frode.jaeger at ntnu.no> wrote: > Hi, > ________________________________________ > From: Gene Cumm <gene.cumm at gmail.com> > Sent: Wednesday, March 16, 2016 00:56 > To: Jan Frode J?ger > Cc: syslinux at zytor.com > Subject: Re: [syslinux] Updated status on UEFI compliant version of the pxechn-module > >

Hello I'm currently working on a project to rolling out a new TFTP boot server, for a fairly large infrastructure (>200 servers, >1500 clients, with heterogeneous configurations/setups). We are using Syslinux version 6.03 for all the function within our TFTP server. We are using Ubuntu as our main TFTP server for most deployments and WDS for our

>>> BTW, some time ago I reworked the disk handling API to also support UEFI and then linking it against gnu-efi library. Patrick, I don't know what exactly you did, but follow what I did: http://git.zytor.com/users/pcacjr/syslinux.git/commit/?h=com32-disk-uefi&id=a29ec41c953cea84261b820cd469b090453125f4 Paulo <<< Patch "I" allows core to "run" the

On Sat, Sep 19, 2015 at 4:32 PM, BALATON Zoltan <balaton at eik.bme.hu> wrote: > On Fri, 18 Sep 2015, Gene Cumm via Syslinux wrote: >> >> On Sep 18, 2015 7:07 AM, "Ady via Syslinux" <syslinux at zytor.com> wrote: >> >>> I doubt there has been any update to pxechn.c32 for UEFI support. Maybe >>> Gene can confirm. >> >>

On Wed, Mar 16, 2016 at 7:21 PM, Patrick Masotta <masottaus at yahoo.com> wrote: >>>> > I'd like to get UEFI chaining working first. > > > <<< > > I have sent in the past two patches; one allows SL to chainload to efi > executives and the other one > allows to link the gnu-efi layer to a com32 module in order to access the > EFI firmware

On Sep 18, 2015 7:07 AM, "Ady via Syslinux" <syslinux at zytor.com> wrote: > I doubt there has been any update to pxechn.c32 for UEFI support. Maybe > Gene can confirm. No. pxechn.c32 is BIOS only for now. --Gene

> On Thu, Mar 17, 2016 at 01:48:52PM +0000, Patrick Masotta via Syslinux wrote: > > > Paulo wrote: > > > BTW, some time ago I reworked the disk handling API to also support > > > UEFI and then linking it against gnu-efi library. Patrick, I don't > > > know what exactly you did, but follow what I did: > > > > > >

> >>> > > > > I have sent in the past two patches; one allows SL to chainload to efi > > executives and the other one > > allows to link the gnu-efi layer to a com32 module in order to access the > > EFI firmware from the com32 code. > > Despite minor changes I might've made during all this time that code > > works... > > Do you

> Hello > > > > > > I'm currently working on a project to rolling out a new TFTP boot > server, for a fairly large infrastructure (>200 servers, >1500 > clients, with heterogeneous configurations/setups). We are using > Syslinux version 6.03 for all the function within our TFTP server. > > > > > > We

> 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;

On Jul 22, 2013 5:27 PM, "Gene Cumm" <gene.cumm at gmail.com> wrote: > > On Mon, Jul 22, 2013 at 11:36 AM, Matt Fleming <matt at console-pimps.org> wrote: > > On Sat, 20 Jul, at 09:48:38AM, Victor Sudakov wrote: > >> Negative. > >> > >> I have changed the stanza into > >> > >> label WDS > >> menu LABEL ^4.

With the BIOS architecture, I was used to boot WinPE from PXELINUX. I used 4 different ways: 1- Calling windows' native PXE loader directly from the config file with a 'kernel' line. 2- Calling windows' native PXE loader with pxechn.c32. 3- Loading an ISO with memdisk 4- iPXE project's wimboot, which relies on memdisk Methods 1 and 2 are slow because loading the bulk of the

On Thu, Mar 17, 2016 at 7:54 AM, Gene Cumm via Syslinux <syslinux at zytor.com> wrote: > On Wed, Mar 16, 2016 at 7:21 PM, Patrick Masotta <masottaus at yahoo.com> wrote: >>>>> >> I'd like to get UEFI chaining working first. >> >> >> <<< >> >> I have sent in the past two patches; one allows SL to chainload to efi

>>> I'd like to get UEFI chaining working first. <<< I have sent in the past two patches; one allows SL to chainload to efi executives and the other one allows to link the gnu-efi layer to a com32 module in order to access the EFI firmware from the com32 code. Despite minor changes I might've made during all this time that code works... Best,Patrick

On Thu, Mar 17, 2016 at 01:48:52PM +0000, Patrick Masotta via Syslinux wrote: > > Paulo wrote: > > BTW, some time ago I reworked the disk handling API to also support > > UEFI and then linking it against gnu-efi library. Patrick, I don't > > know what exactly you did, but follow what I did: > > > >

Patrick, Even more confusing. I downloaded the 6.03 syslinux tar and extracted all the files. It shows 3 pxechn versions, [root at localhost_PXENG ~]# cd /tmp/syslinux-6.03 [root at localhost_PXENG syslinux-6.03]# find . -name pxechn.c32 ./efi32/com32/modules/pxechn.c32 ./efi64/com32/modules/pxechn.c32 ./bios/com32/modules/pxechn.c32 Is it possible to pxechn to a BIOS pxelinux.0?