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

> Hello James, > > > ----- Forwarded message from Geert Stappers via Syslinux > <syslinux at zytor.com> ----- > > Date: Thu, 8 Oct 2015 01:24:26 +0200 > From: Geert Stappers via Syslinux <syslinux at zytor.com> > To: "Clements, James" <James.Clements at affiliate.oliverwyman.com> > Cc: "syslinux at zytor.com" <syslinux at

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

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 I have disabled secure boot on this VM for the installation of Linux. I am using the latest tftp-hpa package with

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 I have disabled secure boot on this VM for the installation of Linux. I am using the latest tftp-hpa package with the following config: # /etc/default/tftpd-hpa TFTP_USERNAME="tftp"

Hello, There's been a similarly-named thread several years ago, in October 2015: http://www.syslinux.org/archives/2015-October/024374.html I've recently encountered a similar problem, namely that when loading UEFI-based syslinux on Hyper-V Gen 2 machine the syslinux.efi will get loaded, will do the DHCP/BOOTP communication and request ldlinux.e64 from the correct server, however it

On Mon, Mar 10, 2014 at 8:50 PM, Spike White <spikewhitetx at gmail.com> wrote: > There are no pre-compiled binaries (official or otherwise) on kernel.org. The Syslinux archives at kernel.org are source and binary. Extract them and you'll see. > I assume what is meant is > https://www.kernel.org/pub/linux/utils/boot/syslinux/ > At least, that is where the

Gene Cumm wrote: > >> My test x86-64 binaries: > >> > >> https://sites.google.com/site/genecsyslinux/sl604p0g17-x64.tgz?attredirects=0&d=1 > > On Fri, Oct 2, 2015 at 4:46 PM, Derrick M <derrick.martinez at gmail.com> wrote: > > This works! Fixes my issue I have been having with the DL160s > > Further testing, preferably of the above binaries,

There are no pre-compiled binaries (official or otherwise) on kernel.org. I assume what is meant is https://www.kernel.org/pub/linux/utils/boot/syslinux/ At least, that is where the "downloads" page of syslinux.org directs you. Under there are the various source tarballs (tar.gz format, tar.bz2 format). Also a directory called RPMS/. But that kernel.org RPMS/ directory is devoid of

Spike, There are multiple binaries that come with syslinux. I would highly recommend that you start with the official syslinux pre-built's of pre-7 on kernel.org. You will find inside an syslinux.efi in a 64 bit folder and one in an 32 bit folder. These are the files that you need to point your clients to for efi booting. pxelinux.0 is for bios booting only. On Sunday, March 9, 2014 4:07