similar to: {syslinux} Hyper-V Gen 2 waiting for ldlinux.e64

On Wed, Oct 07, 2015 at 05:58:51PM -0500, Clements, James wrote: > James Clement > > Geert Stappers > > > On Wed, Oct 07, 2015 at 05:06:41PM -0500, Clements, James wrote: > > > > The screen displays the following: > > > > > > > > PXE Network Boot using IPv4 > > > > .... > > > > Station IP address is 192.168.205.50

> On Wed, Oct 07, 2015 at 05:06:41PM -0500, Clements, James via Syslinux > wrote: > > > On Wed, Oct 07, 2015 at 06:01:30PM +0200, Geert Stappers via Syslinux > wrote: > > > is for BIOS, not for EFI. So that suggestion can be scraped. > > > > > > Which makes > > > * text which is on the screen of the netbooting (virtual) machine > > >

On Thu, Oct 08, 2015 at 01:24:26AM +0200, Geert Stappers via Syslinux wrote: > On Wed, Oct 07, 2015 at 05:58:51PM -0500, Clements, James wrote: > > > Correct me if I am wrong but if I understand correctly, syslinux.efi is > > what drives the request for ldlinux.e64. Is there a way we can enable > > some debug somehow to see why the request for ldlinux.e64 includes >

> > > On Wed, Oct 07, 2015 at 05:06:41PM -0500, Clements, James via Syslinux > > wrote: > > > > On Wed, Oct 07, 2015 at 06:01:30PM +0200, Geert Stappers via Syslinux > > wrote: > > > > is for BIOS, not for EFI. So that suggestion can be scraped. > > > > > > > > Which makes > > > > * text which is on the screen of

> On Wed, Oct 07, 2015 at 06:01:30PM +0200, Geert Stappers via Syslinux > wrote: > > On Wed, Oct 07, 2015 at 05:35:36PM +0200, Geert Stappers via Syslinux > wrote: > > > On Wed, Oct 07, 2015 at 08:55:53AM -0500, Clements, James wrote: > > > > On Wed, Oct 07, 2015 Geert Stappers wrote > > > > > 13:36:47.974245 IP 192.168.205.50.1939 >

> On Fri, Oct 09, 2015 at 10:55:11AM -0500, Clements, James wrote: > > > On Fri, Oct 09, 2015 at 09:45:23AM -0500, Clements, James wrote: > > > > From: Geert Stappers [mailto:stappers at stappers.nl] > > > > Sent: 09 October 2015 15:39 > > > > > On Fri, Oct 09, 2015 at 09:14:55AM -0500, Clements, James wrote: > > > > > > From:

On Wed, Oct 07, 2015 at 05:06:41PM -0500, Clements, James via Syslinux wrote: > > On Wed, Oct 07, 2015 at 06:01:30PM +0200, Geert Stappers via Syslinux wrote: > > is for BIOS, not for EFI. So that suggestion can be scraped. > > > > Which makes > > * text which is on the screen of the netbooting (virtual) machine > > * when/why was the network capture stopped

On Wed, Oct 07, 2015 at 01:58:51PM +0200, James Clements via Syslinux wrote: > On Wed, Oct 07, 2015 at 07:21:28AM -0400, Gene Cumm via Syslinux wrote: > > On Wed, Oct 7, 2015 at 6:40 AM, Clements, James via Syslinux wrote: > > > Hi, > > > > > > I am using a Windows Server 2012 R2 Hyper-V Generation 2 VM as a > > > PXE client (no physical machines

> On Wed, Oct 07, 2015 at 01:58:51PM +0200, James Clements via Syslinux > wrote: > > On Wed, Oct 07, 2015 at 07:21:28AM -0400, Gene Cumm via Syslinux wrote: > > > On Wed, Oct 7, 2015 at 6:40 AM, Clements, James via Syslinux wrote: > > > > Hi, > > > > > > > > I am using a Windows Server 2012 R2 Hyper-V Generation 2 VM as a > > > >

On Wed, Oct 07, 2015 at 05:35:36PM +0200, Geert Stappers via Syslinux wrote: > On Wed, Oct 07, 2015 at 08:55:53AM -0500, Clements, James wrote: > > On Wed, Oct 07, 2015 Geert Stappers wrote > > > 13:36:47.964636 IP 192.168.205.1.47973 > 192.168.205.50.1938: UDP, length 30 > > > 13:36:47.964685 IP 192.168.205.50.1938 > 192.168.205.1.47973: UDP, length 4 > >

On Wed, Oct 07, 2015 at 08:55:53AM -0500, Clements, James wrote: > On Wed, Oct 07, 2015 Geert Stappers wrote > > On Wed, Oct 07, 2015 at 01:58:51PM +0200, James Clements via Syslinux > > > On Wed, Oct 07, 2015 at 07:21:28AM -0400, Gene Cumm via Syslinux wrote: > > > > > > > > http://www.syslinux.org/archives/2015-October/024375.html

On 05/10/2013 06:27 AM, syslinux-bot for Matt Fleming wrote: > > diff --git a/efi/main.c b/efi/main.c > index 31f0bff..27e7f8f 100644 > --- a/efi/main.c > +++ b/efi/main.c > @@ -1177,13 +1177,10 @@ static void efi_setcwd(CHAR16 *dp) > > EFI_STATUS efi_main(EFI_HANDLE image, EFI_SYSTEM_TABLE *table) > { > + EFI_PXE_BASE_CODE *pxe; > EFI_LOADED_IMAGE *info;

On Wed, Oct 07, 2015 at 06:01:30PM +0200, Geert Stappers via Syslinux wrote: > On Wed, Oct 07, 2015 at 05:35:36PM +0200, Geert Stappers via Syslinux wrote: > > On Wed, Oct 07, 2015 at 08:55:53AM -0500, Clements, James wrote: > > > On Wed, Oct 07, 2015 Geert Stappers wrote > > > > 13:36:47.974245 IP 192.168.205.50.1939 > 192.168.205.1.tftp: 47 RRQ

On 13.07.2015 12:08, Gene Cumm wrote: > systemd Mailing List <systemd-devel at lists.freedesktop.org> would be > the wrong address. > > On Mon, Jul 13, 2015 at 5:33 AM, poma <pomidorabelisima at gmail.com> wrote: >> On 03.07.2015 21:35, Gene Cumm wrote: >>> On Jul 3, 2015 1:34 PM, "poma" <pomidorabelisima at gmail.com> wrote: >>>

On Wed, Oct 07, 2015 at 07:21:28AM -0400, Gene Cumm via Syslinux wrote: > On Wed, Oct 7, 2015 at 6:40 AM, Clements, James via Syslinux > <syslinux at zytor.com> wrote: > > Hi, > > > > I am using a Windows Server 2012 R2 Hyper-V Generation 2 VM as a > > PXE client (no physical machines available). This is a UEFI VM, and > > as per instructions I've read

This patch adds to Com32 modules the capabilities of accessing the EFI environment The idea is simple, the EFI parameters "image" and "table" received by syslinux.efi's efi_main() are stored in the "firmware" structure, next they are retrieved from the Com32 module which is linked against the gnu-efi static library. The Com32 module can use the EFI

On Mon, Jul 6, 2015 at 6:04 AM, Patrick Masotta <masottaus at yahoo.com> wrote: > > What I've found: > (from older to newer hardware) > > 1) There's not "any" SB protocol present (Elitebook 8460p/2560p) The only solution for these is to use our own stack (likely full TCP/IP like lwIP) and connect to the Net GUID (EFI_SIMPLE_NETWORK_PROTOCOL). Does the

EFI booting may hang indefinitely when no keyboard is present on a machine (or when UEFI has chosen to not init USB due to fast boot). Reproducible at least with "EFI v2.31 by American Megatrends" on an Asrock H81M-ITX board. Reason is the input draining loop near the end in efi/main.c; it calls ReadKeyStroke() as long as EFI_NOT_READY is not returned. On machines without keyboard,

>>> I'm just debating what's the best algorithm here.? It would seem if the LoadeImage's DeviceHandle provides UDPv4Sb, use it as it's guaranteed to be the same interface.? Otherwise, we need a MNPSb (EFI_MANAGED_NETWORK_SERVICE_BINDING) that provides UDPv4Sb across the same interface.? Presumably it should also provide TCPv4Sb (rather than being on a separate

From: Sylvain Gault <sylvain.gault at gmail.com> The behavior when running a "CONFIG" command line is to reload ldlinux.c32 with the new file as argument. This call never return. In order to avoid stacking up the calls to start_ldlinux, this patch introduce a setjmp/longjmp to return to the first call to start_ldlinux, thus freeing all the stack space. Signed-off-by: Sylvain