Syslinux - Feb 2018 - syslinux PXE boot version upgrade, network no longer working

My ?default? was just a sample to prevent further tl;dr :)

Right, by 2014 I meant 6.03. I didn?t notice in the docs this was a known issue.
If keeppxe is a bug with 6.03, that?s likely my issue. Do I drop back to 6.02 or
X? Which version?

Thanks,
David

Sent from my iPhone
> On Feb 1, 2018, at 6:53 PM, Ady Ady via Syslinux <syslinux at
zytor.com> wrote:
> 
> 
>> Hardware with issue is a Lenovo T410 (circa 2007?):
>> 
>> SysLinux PXE boot (pxelinux.0) version 2009 - PXE boot works, select
>> Ghost from PXE menu, PC-DOS loads, Ghost.exe runs and networking is
>> working for Ghostcast/peer to peer.
>> 
>> SysLinux PXE boot (pxelinux.0) version 2014 - PXE boot works, select
>> Ghost from PXE menu, PC-DOS loads, Ghost.exe runs and networking is
>> NOT working for Ghostcast/peer to peer.
>> 
>> The PC-DOS has a universal network driver (UNDI) 11.1 (boot disk made
>> from Ghost 11.5 Book Disk Wizard).
>> 
>> My "default" file configuration and .ima floppy disk image
are
>> identical in both environments:
>> 
>> DEFAULT menu.c32
>> PROMPT 0
>> TIMEOUT 300
>> MENU TITLE PXE Boot Menu
>> LABEL Ghost
>> MENU LABEL ^Ghost
>> MENU IMMEDIATE
>> KERNEL memdisk
>> APPEND keeppxe floppy rw initrd=bootimages/ghost.ima
>> 
>> My TFTP is identical in both environments:
>> TFTPD64 v4.60 Build Jan 28 2017 18:55:26 (Service Edition)
>> 
>> Only difference is the version of SysLinux (pxeconfig.0 and its
>> corresponding files from 2009 version: menu.c32, memdisk and in the
>> 2014 version add ldlinux.c32).  I have tried with and without
>> "keeppxe" in the APPEND line.
>> 
>> Interesting side note: Lenovo T420 works in both environments,
>> networking loads (as do many other models)
>> 
>> Ideas?
>> thanks,
>> David
> 
> 
> I am guessing that "keeppxe" is needed.
> 
> Although versions "2009" and "2014" are not really
"versions", "2014" is
> probably version 6.03, which is still/yet not supporting
"keeppxe". This is a
> known problem.
> 
> BTW, for menu.c32 "2014" you should also need its corresponding
libutil.c32
> (although, if your "default" file only has one entry, then
menu.c32 is useless;
> i.e. the menu won't show up anyway).
> 
> You could try the binaries from Debian's "experimental" repo
(replace _all_ of
> them, not just pxelinux.0). Feedback is appreciated.
> 
> 
>> _______________________________________________
>> Syslinux mailing list
>> Submissions to Syslinux at zytor.com
>> Unsubscribe or set options at:
>> http://www.zytor.com/mailman/listinfo/syslinux
> 
> 
> 
> _______________________________________________
> Syslinux mailing list
> Submissions to Syslinux at zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux

> Right, by 2014 I meant 6.03. I didn?t notice in the docs this was a known
issue. If keeppxe is a bug with 6.03, that?s likely my issue. Do I drop back to
6.02 or X? Which version?
 
 
I would suggest trying Debian's "experimental" binaries (which
include
potentially-relevant patches for keeppxe), including all its "bios"
lib*.c32
files (beware not to mix with the efi files with same file names) and its 
linux.c32 (so as to replace the KERNEL directive, as follows):

LABEL Ghost
COM32 linux.c32
APPEND memdisk keeppxe floppy rw initrd=bootimages/ghost.ima

Even if you are not using Debian, the [experimental] binaries can be downloaded 
and used anyway.

Please replace _all_ files with the corresponding version (including pxelinux.0 
+ ldlinux.c32 + menu.c32 + linux.c32 + lib*.c32, all from the "bios"
platform);
do not mix versions.

Prior to 6.03, the last version to correctly support keeppxe was version(s) 
4.xx.

Thanks Ady.  I have to stick with stable vs. experimental but I
appreciate the Debian suggestion.

I don't mean to troll anyone, but... how is 6.03 considered stable if
it does not correctly support keeppxe?  I have to go all the way back
to 4.xx for this to be supported?  Wow.  I still couldn't find it in
the docs online where it states keeppxe doesn't work.  I have some
"detail oriented" management who wants "proof" why I have to
run a
much older version of the PXE environment. *eye roll*

I'm in a catch 22 of sorts.  The older version I have from 2009 is so
old I don't see it under the OLD folder path under downloads.  That
version is starting to have trouble driving networking with some brand
new models of laptops, so I definitely have to upgrade.

Looks like 4.10 is where I need to go if I am sticking with SysLinux?

thank you,
David


On Thu, Feb 1, 2018 at 8:38 PM, Ady Ady via Syslinux <syslinux at
zytor.com> wrote:
>> Right, by 2014 I meant 6.03. I didn?t notice in the docs this was a
known issue. If keeppxe is a bug with 6.03, that?s likely my issue. Do I drop
back to 6.02 or X? Which version?
>
>
> I would suggest trying Debian's "experimental" binaries
(which include
> potentially-relevant patches for keeppxe), including all its
"bios" lib*.c32
> files (beware not to mix with the efi files with same file names) and its
> linux.c32 (so as to replace the KERNEL directive, as follows):
>
> LABEL Ghost
> COM32 linux.c32
> APPEND memdisk keeppxe floppy rw initrd=bootimages/ghost.ima
>
> Even if you are not using Debian, the [experimental] binaries can be
downloaded
> and used anyway.
>
> Please replace _all_ files with the corresponding version (including
pxelinux.0
> + ldlinux.c32 + menu.c32 + linux.c32 + lib*.c32, all from the
"bios" platform);
> do not mix versions.
>
> Prior to 6.03, the last version to correctly support keeppxe was version(s)
> 4.xx.
>
> _______________________________________________
> Syslinux mailing list
> Submissions to Syslinux at zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux