[syslinux] gpxelinux.0 Unable to locate configuration file while pxelinux.0 works

[Gene Cumm]

On Fri, Apr 19, 2013 at 10:16 PM, peter Sjoberg <lpaseen at gmail.com> wrote:
> On Fri, 2013-04-19 at 10:08 -0700, H. Peter Anvin wrote:
>> You could try lpxelinux.0 from 5.10-pre*.
> Maybe but after seeing it working on a different server (BL460C G6) I
> did bite the bullet and did a firmware upgrade, UNDU PXE 2.0
> 3.102.517.701 became 4.2.401.6, and after that gpxelinux.0 works fine
> also (well, still need to figure out what menu.c32 to use, see the
> versions and so on but that's another story).

Not unusual.  I recall other systems behaving similarly (broken UNDI
fixed by a BIOS/firmware upgrade)

> While it impacts lots of servers we have an environment where it's
> reasonable simple to change how a server network boots so I left one
> option booting pxelinux.0 for when firmware upgrade is needed.

Another choice I forgot to mention:

Boot pxelinux.0 first then chainboot to gpxelinux.0 with pxechn.c32,
setting option 210 (prefix).  If I were to implement this scenario and
I used (vesa)menu.c32, I'd put the gpxelinux.0 item first but default
to the second item (safe default but quick access to gpxelinux.0).

--
-Gene