similar to: iPXE chain to lpxelinux.0 6.03 inconsistencies and failures

On 15 Nov 2014 05:06:52 +0200, Ady wrote: > > I would start by updating the BIOS. Prudent advice. As it turns out, I'm already at the latest version. On 15 Nov 2014 07:31:27 +0100, Geert Stappers wrote: > > And would reduce 'iPXE => pxe.0 => lpxelinux.0 => "vmlinux"' > into 'iPXE => "vmlinux"' That makes sense generally, but at

Op 2014-07-01 om 22:55 schreef Gene Cumm: > On Jul 1, 2014 10:37 PM, "Alexander Perlis" wrote: > > > > I believe I'm seeing a bug in lpxelinux.0 6.03-pre17 but I need some > > advice on how to isolate and troubleshoot this. (I can't try pre18 > > at the moment, but did try 4.07 and 5.10 and saw similar behavior, > > also with pxelinux.0, so

I believe I'm seeing a bug in lpxelinux.0 6.03-pre17 but I need some advice on how to isolate and troubleshoot this. (I can't try pre18 at the moment, but did try 4.07 and 5.10 and saw similar behavior, also with pxelinux.0, so although I'll give pre18 a try soon, some isolation/troubleshooting advice will be a good education no matter what.) To get to our PXE-launched tools from

On Jul 1, 2014 10:37 PM, "Alexander Perlis" <aperlis at math.lsu.edu> wrote: > > I believe I'm seeing a bug in lpxelinux.0 6.03-pre17 but I need some advice on how to isolate and troubleshoot this. (I can't try pre18 at the moment, but did try 4.07 and 5.10 and saw similar behavior, also with pxelinux.0, so although I'll give pre18 a try soon, some

On 07/01/2014 09:55 PM, Gene Cumm wrote: > On Jul 1, 2014 10:37 PM, "Alexander Perlis" <aperlis at math.lsu.edu > > I believe I'm seeing a bug in lpxelinux.0 6.03-pre17 ... > > Odd. 4.07 should be good but the 4.10/5.1*/6.0* revisions make sense. My bad. I tried again, and in 4.07 we do get further. We couldn't boot all the way because, it seems, using

On 07/03/2014 06:31 AM, Gene Cumm wrote: > On Jul 2, 2014 11:13 AM, Alexander Perlis wrote: > > > Or is there a different (non-ipxe?) way we can locally boot a machine > and get it to chain to our 6.0x pxelinux server? > > Unless this is a completely isolated network, talk with your IT department. > > If there's no DHCP, make a simple server. If there's DHCP and

> Now my question: where more specifically is the bug? What can I do to > help a developer isolate this? I would start by updating the BIOS.

On 07/03/2014 08:44 PM, Gene Cumm wrote: > On Thu, Jul 3, 2014 at 9:13 PM, Alexander Perlis wrote: > >> I suppose we could try making an ISOLINUX CD for the local boot, which then >> uses pxechn.c32 to connect to our PXE server? > > pxechn.c32 requires a functional PXELINUX. If I understand the issue correctly, is it that pxelinux.0 does not have a network stack and

On Jul 2, 2014 11:13 AM, "Alexander Perlis" <aperlis at math.lsu.edu> wrote: > Or is there a different (non-ipxe?) way we can locally boot a machine and get it to chain to our 6.0x pxelinux server? Unless this is a completely isolated network, talk with your IT department. If there's no DHCP, make a simple server. If there's DHCP and no boot info, add a PXE server

Hi All, I've been trying to understand how to use pxechn.c32 to chain a local pxelinux menu item to a remote server which has it's own pxelinux hierarchy served via TFTP and HTTP. We have no control over DHCP next-server and filename fields so I wanted to exploit the "prefix" -p option that pxechn.c32 accepts. I spent a long time hitting my head against a brick wall until I

On Thu, Jul 3, 2014 at 9:13 PM, Alexander Perlis <aperlis at math.lsu.edu> wrote: > I suppose we could try making an ISOLINUX CD for the local boot, which then > uses pxechn.c32 to connect to our PXE server? pxechn.c32 requires a functional PXELINUX. -- -Gene

I am experiencing an issue where I ran ipxe (as an option rom) and downloaded the lpxelinux.0 as the bootloader. Next it should download the ldlinux.c32 file using UNDI API. but before that it will close and open the underlying device (which is ipxe), and hooking the device interrupt so it can start getting some packets. What I'm experiencing is that if the underlying device doesn't

On 24/10/15 21:57, Doug Scoular via Syslinux wrote: > 1. gpxe - a mothballed Network Boot Program but with a possibly problematic > and slow HTTP implementation. > 2. ipxe - an active fork of gpxe but still with the possibly problematic > and slow HTTP implementation (?) iPXE's HTTP implementation is definitely not slow. On a Gigabit LAN, you should get the full 1000Mbps speed

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

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

Hello Geert Thanks for replying.. But i think i can?t use it, as i don?t reach the point where the debug module will be available.. it just pulls the lpxelinux.0 and tries to get the next download-- the ldlinux.c32 and it fails...and freezes. And the next step would be other modules i think.. if i?m wrong.. excuse me 8-).. yesterday i managed to get ipxelinux working from ipxe.org.. so the nic

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