Displaying 3 results from an estimated 3 matches for "0c1dff8d".
2014 Nov 15
2
iPXE chain to lpxelinux.0 6.03 inconsistencies and failures
...lpxelinux.0, such as memory
management or stack management, which is simply being triggered by say
iPXE's Broadcom driver being say a different size than perhaps that of
most other drivers. Or who knows. (In case it helps: Back in July, Gene
posted that the problem may be related to commit 0c1dff8d.)
I'm happy to do testing, run a custom debug build and report output, or
whatever might help. Just need some pointers as to what to do. Any iPXE
or lpxelinux.0 developer is welcome to contact me.
Alex
2014 Jul 02
1
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
2014 Nov 15
2
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