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

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

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

On this list in early July 2014 I reported that on certain hardware one cannot chain from ipxe to lpxelinux.0 . My report at the time was about 6.03-pre17. I've repeated the tests with the release version of 6.03 and here is an updated report with more details. I boot to a USB stick with iPXE, which then is told to "dhcp" and then "chain http://xxx.xxx.xxx.xxx/pxe.0".

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

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

Trying to PXE boot a Dell Optiplex 990 with BIOS A16, which has Intel Boot Agent 1.3.81 (2.1 build 089). It gets network and launches lpxelinux.0, I see the PXELINUX banner line, but there it hangs. I tried both 6.03-pre18 and 5.10, same hanging behavior. If I instead use pxelinux.0 or gpxelinux.0, either 6.03-pre18 or 5.10 or 4.07, there are no problems. The problem seems isolated to

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

On Thu, Jul 10, 2014 at 7:24 PM, H. Peter Anvin <hpa at zytor.com> wrote: > On 07/10/2014 04:07 PM, Alexander Perlis wrote: >> Trying to PXE boot a Dell Optiplex 990 with BIOS A16, which has Intel >> Boot Agent 1.3.81 (2.1 build 089). It gets network and launches >> lpxelinux.0, I see the PXELINUX banner line, but there it hangs. >> >> I tried both 6.03-pre18

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

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

> > From: Matt Fleming [matt at console-pimps.org] > > Sent: 25 June 2014 07:39 > > To: Andrew Rae > > Cc: Gene Cumm; syslinux at zytor.com > > Subject: Re: [syslinux] testing out 6.03 network booting... > > > > Andrew, could you try out syslinux-6.03-pre18? Peter pushed the release > > button yesterday and -pre18 contains my change. It would be

On Sun, 22 Jun, at 06:15:50PM, Andrew Rae wrote: > > Matt - I'd love to try it - but I'm not so good at fixing compiling > issues. right now I get stuck at being unable to 'make' the efi32 or > efi64 components due to an error: Andrew, could you try out syslinux-6.03-pre18? Peter pushed the release button yesterday and -pre18 contains my change. It would be good to

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

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

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 06/16/2014 05:14 PM, Gene Cumm wrote: > This sounds like you're using gpxelinux.0 4.07 which as I stated will > introduce issues. Instead of using gpxelinux.0 4.07, try pxelinux.0 > 4.07 then do your chainload to lpxelinux.0 6.02. If this doesn't > solve it, try 6.03-pre14. When I DHCP boot to lpxelinux.0 6.02, and then pxechn.c32 back to lpxelinux.0 6.02 with the http

Op 2014-07-23 om 17:57 schreef Gene Cumm: > On Wed, Jul 23, 2014 at 10:32 AM, Geert Stappers <stappers at stappers.nl> wrote: > > Hi, > > > > Since which version of pxelinux.0 is understood in pxelinux.cfg/default that > > > > kernel http://host.lan/netboot/vmlinuz > > > > means vmlinuz should be transported over HTTP? > > For non-EFI