Displaying 2 results from an estimated 2 matches for "167a".
Did you mean:
167
2014 Nov 15
2
iPXE chain to lpxelinux.0 6.03 inconsistencies and failures
...a pxelinux-options) with an
appropriate next-server, path-prefix, and config-file.
This all works great on a lot of different machines.
But specifically on the Dell Optiplex GX620 and Optiplex 645, which have
built-in Broadcom ethernet (the GX620 has 14e4:1677 [1028:01ad], and the
645 has 14e4:167a [1028:01da]), there's a problem: first lpxelinux.0 is
correctly transferred, then control is indeed handed to lpxelinux.0
because the "PXELINUX 6.03 lwIP 2014-10-06" banner indeed appears, but
then the computer appears to be frozen, although it eventually says
"Failed to load...
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