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 Windows deployments. We can PXE boot from the ubuntu
TFTP server using both legacy (bios) and Uefi.
We have pxechn.c32 working with pxelinux.0 to switch between the two
system, but pxechn.c32 under Uefi come up with the folowing error
"pxechn.c32: ERROR: Unable to retrieve first packet". I have seen
that there was a message about this logged on the 28th August 2014
http://www.syslinux.org/archives/2014-August/022611.html,
and I would like to know if there have been any updated on this
problem.
If I can help by doing some testing that would not be a problem, but
I can not program. I probably could involve colleagues for in depth
debugging or programming.
Many thanks
Jonathan.
> 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 Windows deployments. We can PXE boot from the ubuntu > TFTP server using both legacy (bios) and Uefi. > > > > > > We have pxechn.c32 working with pxelinux.0 to switch between the two > system, but pxechn.c32 under Uefi come up with the folowing error > "pxechn.c32: ERROR: Unable to retrieve first packet". I have seen > that there was a message about this logged on the 28th August 2014 http://www.syslinux.org/archives/2014-August/022611.html, > and I would like to know if there have been any updated on this > problem. > > > > > > If I can help by doing some testing that would not be a problem, but > I can not program. I probably could involve colleagues for in depth > debugging or programming. > > > > > > Many thanks > > > > > > Jonathan.I doubt there has been any update to pxechn.c32 for UEFI support. Maybe Gene can confirm. If you are trying to chain to another efi binary / image, perhaps this [1] PoC might help? If not for the exact goal, perhaps as an initial base so to make some new c32 module for UEFI systems? [1]: http://www.syslinux.org/archives/2015-March/023320.html @Developers, please consider using 8.3 file names format for c32 files instead of such a long file name. If possible, also use short names for source files too. TIA. Regards, Ady.> _______________________________________________ > Syslinux mailing list > Submissions to Syslinux at zytor.com > Unsubscribe or set options at: > http://www.zytor.com/mailman/listinfo/syslinux >
On Fri, Sep 18, 2015 at 02:01:32PM +0300, Ady via Syslinux wrote:> > > > We have pxechn.c32 working with pxelinux.0 to switch between the two > > system, but pxechn.c32 under Uefi come up with the folowing error > > > @Developers, please consider using 8.3 file names format for c32 files > instead of such a long file name.Example of such a long file name? So we know which file name to surpress into 8.3. ( yes, CP/M file name convention legacy is still present )> If possible, also use short names for source files too. TIA.Euh, please visit http://www.dmst.aueb.gr/dds/pubs/conf/2015-MSR-Unix-History/html/Spi15c.html scroll down to '4 Data Uses', check the graphic, especial file name length. My point: _Why_ restrict the development system file name length? And now something completely different:> > _______________________________________________ > > Syslinux mailing list > > Submissions to Syslinux at zytor.com > > Unsubscribe or set options at: > > http://www.zytor.com/mailman/listinfo/syslinux > > > > > _______________________________________________ > Syslinux mailing list > Submissions to Syslinux at zytor.com > Unsubscribe or set options at: > http://www.zytor.com/mailman/listinfo/syslinuxWhat is the value quoting those lines? Groeten Geert Stappers -- Leven en laten leven ------------- volgend deel ------------ Een niet-tekst bijlage is gescrubt... Naam: signature.asc Type: application/pgp-signature Grootte: 836 bytes Omschrijving: Digital signature URL : <http://www.zytor.com/pipermail/syslinux/attachments/20150918/5186b137/attachment.sig>