similar to: [ipxe-devel] pxelinux version 5.10 and beyound ....

On Jun 29, 2014 9:37 AM, "Wissam Shoukair" <wissams at mellanox.com> wrote: > > Hi Peter, > > I approached you before on this issue that I?m having with the SYSLINUX 6.03-pre18 when booting with iPXE option ROM. > > The issue was reproduced on different OEMs, and also on 2 different cards (Mellanox and Intel), with latest and 2 years old iPXE code. > > Just

On Thu, Oct 10, 2013 at 10:00 AM, Michael Brown <mbrown at fensystems.co.uk> wrote: > On 09/10/13 10:45, Robin Smidsr?d wrote: >> >> On 09.10.2013 02:56, H. Peter Anvin wrote: >>> >>> The gPXE in the Syslinux tree is ridiculously old. We could either >>> replace it with iPXE or just drop it, giving people a recipe for how to >>> integrate

From: Gene Cumm <gene.cumm at gmail.com> Date: Mon, Mar 17, 2014 at 7:39 PM Subject: Re: [ipxe-devel] iPXE boot from both ports (from diferent subnets) not working To: Wissam Shoukair <wissams at mellanox.com> Cc: "ipxe-devel at lists.ipxe.org" <ipxe-devel at lists.ipxe.org> On Mon, Mar 17, 2014 at 4:43 AM, Wissam Shoukair <wissams at mellanox.com> wrote: >

On 9/27/2015 10:11 PM, Geert Stappers wrote: > On Thu, Sep 24, 2015 at 07:57:47AM -0600, Alan Sparks via Syslinux wrote: >> On 9/24/2015 4:59 AM, Gene Cumm wrote: >>> OK. Found it. core/fs/pxe/pxe.h disabled all of the gPXE/iPXE >>> callbacks in the core, disabling HTTP and other functionality. It >>> appears someone disabled it intentionally in commit ID

On 25/10/15 01:04, Gene Cumm wrote: > On Sat, Oct 24, 2015 at 6:15 PM, Michael Brown via Syslinux > <syslinux at zytor.com> wrote: > >> Also, not a fork: http://git.ipxe.org/ipxe.git/commitdiff/8406115 > > A fork is a fork, regardless the reasons behind it (yes, I have some > understanding in this case). iPXE is based off of forking further > development as of a

On Tue, Sep 22, 2015 at 1:42 PM, Alan Sparks <asparks at doublesparks.net> wrote: > On 9/22/2015 4:33 AM, Gene Cumm wrote: >> >> https://sites.google.com/site/genecsyslinux/sl604p0g15-bios.tgz?attredirects=0&d=1 >> https://sites.google.com/site/genecsyslinux/sl604p0g15-x64.tgz?attredirects=0&d=1 >> > > Tried these new binaries this morning. No

On Fri, Mar 14, 2014 at 7:09 PM, Wissam Shoukair <wissams at mellanox.com> wrote: > Hi Gene , > > I will try to use 4.07 or 4.05 and update. Did you tried it on the VMWare > workstation on which you saw the issue? > > One more question, shouldn't iPXE reassign the correct parameters to the > "new" image its executing? I mean isn't it the responsibility

On 9/24/2015 4:33 AM, Gene Cumm wrote: > On Wed, Sep 23, 2015 at 5:43 PM, Alan Sparks via Syslinux > <syslinux at zytor.com> wrote: > Although it means another round of testing, you could also consider > lpxelinux.0 which can support HTTP URLs on its own and probably > interacts differently with iPXE. I am curious about a quantifiable > description of "an odd

On Mar 14, 2014 3:37 AM, "Wissam Shoukair" <wissams at mellanox.com> wrote: > > Hi, > > I'm having a similar problem to the one mentioned earlier by "Laborde Louis", but in this case I'm trying to boot in PXE mode and not iSCSI. > > The problem here is this: > > 1 - DHCP from net0 is successful > > 2 - pxelinux.0 is downloaded from

On Friday 25 Mar 2011 21:21:18 Marcus Grando wrote: > >> Script is something like that: > >> > >> #!ipxe > >> ifopen net0 > >> set net0/ip 192.168.0.10 > >> set net0/netmask 255.255.255.0 > >> set net0/gateway 192.168.0.1 > >> set net0/dns 8.8.8.8 > >> set 209:string pxelinux.cfg/default > >> set 210:string

On Thu, Sep 24, 2015 at 07:57:47AM -0600, Alan Sparks via Syslinux wrote: > On 9/24/2015 4:59 AM, Gene Cumm wrote: > > On Thu, Sep 24, 2015 at 6:33 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > > > >> Now I have something I can reproduce. Booting my same ipxe.iso to > >> perform an initial TFTP load shows what I saw already. Attempting to > >>

On 9/22/2015 4:33 AM, Gene Cumm wrote: > > https://sites.google.com/site/genecsyslinux/sl604p0g15-bios.tgz?attredirects=0&d=1 > https://sites.google.com/site/genecsyslinux/sl604p0g15-x64.tgz?attredirects=0&d=1 > Tried these new binaries this morning. No change, still will not attempt to load ldlinux.c32. As a context, what I'm really trying to do is get a newer

On Thu, Jun 5, 2014 at 8:50 AM, Wissam Shoukair <wissams at mellanox.com> wrote: > Hi Gene, > > More information about this? > > I have found in the syslinux git that this commit id is the last good > commit: > > commit 41c29c26d70fde563d7c255872bbadad87a39dfa (tag: > refs/tags/syslinux-5.02-pre3) > Author: Matt Fleming <matt.fleming at intel.com> >

On 9/21/2015 5:44 PM, Gene Cumm wrote: > On Mon, Sep 21, 2015 at 6:23 PM, Alan Sparks via Syslinux >> With pxelinux 3.8.6 (or, < 5.x), I was able to chain boot pxelinux.0 >> from ipxe, having set appropriate values for DHCP options 210 and 209 >> for the remote file path and the config file. This doesn't work with 6.0.3. > > I thought I recall a newer commit

On 9/23/2015 3:32 PM, Ady via Syslinux wrote: > >> On 9/23/2015 2:08 PM, Ady via Syslinux wrote: >> >>> Even if it still hangs with this test, does it hang exactly as before >>> (i.e. shows only one character and hangs immediately)? >> >> It happens with one entry, or two entries, or three. >> The configuration works otherwise perfectly on any

On Sat, Oct 24, 2015 at 6:15 PM, Michael Brown via Syslinux <syslinux at zytor.com> wrote: > Also, not a fork: http://git.ipxe.org/ipxe.git/commitdiff/8406115 A fork is a fork, regardless the reasons behind it (yes, I have some understanding in this case). iPXE is based off of forking further development as of a certain gPXE commit with some backporting of gPXE development to iPXE. --

> The gPXE in the Syslinux tree is ridiculously old. We could either > replace it with iPXE or just drop it, giving people a recipe for how to > integrate with iPXE themselves. > > What do people think? My vote is replace with iPXE. I've manually replaced gPXE with iPXE for years, works like charm. I suggest updating the Makefile to use undionly.kkkpxe because of the change

On Wed, Sep 23, 2015 at 5:43 PM, Alan Sparks via Syslinux <syslinux at zytor.com> wrote: > On 9/23/2015 3:32 PM, Ady via Syslinux wrote: >> >>> On 9/23/2015 2:08 PM, Ady via Syslinux wrote: >>> All this works OK on the menu.c32 in 6.x. I'm just stuck, since I can't >>> upgrade because ipxe chainloading won't work in 6.x. If I could resolve

On Mon, Sep 21, 2015 at 6:23 PM, Alan Sparks via Syslinux <syslinux at zytor.com> wrote: > If this is asked before, please point me at the answer, can't find it... I seem to recall seeing this before. > With pxelinux 3.8.6 (or, < 5.x), I was able to chain boot pxelinux.0 > from ipxe, having set appropriate values for DHCP options 210 and 209 > for the remote file path

> On 9/23/2015 12:14 AM, Ady via Syslinux wrote: > > > About your customers' setup... > > Are they using official binaries downloaded from kernel.org? > > Yes. Stock versions, no local modifications. > > > Which exact version of Syslinux are they using? > > I've tried versions 3.86, 4.07, 6.01, 6.03. > We can only generally use 4.07 or less