search for: keeppx

PXELINUX has stopped recognizing the keeppxe option on the kernel command line. Here is a patch to make it work again. With COM32, it is no longer possible to use preprocessor directives to determine the SYSLINUX variant. The code inside the #if will never be compiled. So, I changed it to use syslinux_filesystem() to determine the varia...

On Fri, Jun 10, 2016 at 2:06 AM, Adam Goldman via Syslinux <syslinux at zytor.com> wrote: > PXELINUX has stopped recognizing the keeppxe option on the kernel > command line. Here is a patch to make it work again. > > With COM32, it is no longer possible to use preprocessor directives to > determine the SYSLINUX variant. The code inside the #if will never be > compiled. So, I changed it to use syslinux_filesystem() to...

Summary ======= I have a recommendation for a minor documentation change regarding 'keeppxe'. I lost some time on this and think that a clarification could save other people time in the future. pxelinux.doc should be tweaked to explicitly say that the "keeppxe" option should be given on the kernel command line through the APPEND statemen Detail ====== pxelinux.doc line...

...have noticed that items at the bottom are dropping off. I seem to be limited to 12 items. Is there a limit to how many items can be on the simple menu? default pxelinux.cfg/menu.c32 prompt 0 MENU TITLE UWSP PXE Boot Menu # TIMEOUT 200 LABEL bartpe MENU LABEL Build 12 KERNEL /STARTROM.0 APPEND keeppxe LABEL 11dnet MENU LABEL Build 11DNET beta (works on 200MB ram) KERNEL 1/STARTROM.0 APPEND keepxe LABEL imgctr MENU LABEL Image Center (experimental) KERNEL memdisk APPEND keeppxe initrd=fimages/pqimgctr.vfd LABEL localboot MENU LABEL Localboot MENU DEFAULT LOCALBOOT 0 LABEL locksmi...

....c:new_linux_kernel() to load_linux.c:bios_boot_linux() because > > there is no convenient way in new_linux_kernel() to control the boot > > flags value. > > This is the part that has me questioning things and trying to recall > if any other KERNEL-like directives ever utilize keeppxe. > @Gene, Not being a developer myself, I don't understand this "other KERNEL-like directives" sentence. I do know what "kernel-like directives" means, but I do not know which one is the one you are referring to here, and why "_other_ KERNEL-like directives&qu...

...t; there is no convenient way in new_linux_kernel() to control the boot > >> >> > flags value. > >> >> > >> >> This is the part that has me questioning things and trying to recall > >> >> if any other KERNEL-like directives ever utilize keeppxe. > >> >> > >> > > >> > @Gene, > >> > > >> > Not being a developer myself, I don't understand this "other > >> > KERNEL-like directives" sentence. I do know what "kernel-like > >> > >> Th...

...oot_linux() because > >> > there is no convenient way in new_linux_kernel() to control the boot > >> > flags value. > >> > >> This is the part that has me questioning things and trying to recall > >> if any other KERNEL-like directives ever utilize keeppxe. > >> > > > > @Gene, > > > > Not being a developer myself, I don't understand this "other > > KERNEL-like directives" sentence. I do know what "kernel-like > > Those directives which acts like KERNEL, specifying a binary to > exec...

...() to load_linux.c:bios_boot_linux() because >> > there is no convenient way in new_linux_kernel() to control the boot >> > flags value. >> >> This is the part that has me questioning things and trying to recall >> if any other KERNEL-like directives ever utilize keeppxe. >> > > @Gene, > > Not being a developer myself, I don't understand this "other > KERNEL-like directives" sentence. I do know what "kernel-like Those directives which acts like KERNEL, specifying a binary to execute. BOOT BSS COM32 COMBOOT CONFIG FDIMAGE L...

but it works well with pxelinux.0 in 3.75

Hello, Has anyone thought about how one could use the "keeppxe" option with a vmlinuz/initrd? It would allow one to boot this combination, and if possible the linux kernel/initrd (assuming we have busybox in there) would not have to run udhcp and instead leverage what pxe stack information is loaded. The problem is I don't know of any PXE/UNDI linu...

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?): >>...

Good day, I have the problem to pass the ?loaded? undi driver to the next bootloader. In current pxelinux ?lernel memdisk keeppxe harddisk raw initrd::parh_to_img? always unloads undi before memdisk (or other kernel) takes control. After many tries I found that the keeppxe feature is broken starting from version 6.03 pre 9. I tried to find the reason by comparing sources 6.03 pre 8 / 6.03 pre 9 but can't see any keeppx...

Hi, I'm trying to get the above working, without success so far: UNDIS.DOS refuses to load with an invalid NDIS stack message (from memory). keeppxe has some effect: it reduces the available conventional memory by 140 kbytes or so... still, the packet driver doesn't seem to find the interface. Does anybody have a working setup I could look at? -- Thanks, Feri.

...boot using syslinux. Unfortunatly we can only pass DHCP ip's to hosts that exhibit a vendor code 'like windows/pxe/and other os's do". Unfortunatly DOS does not, so we cannot request a second IP after the pxe process to map samba shares. From what I've read you can use the 'keeppxe' line and call the orrignal ip information recieved durning the pxe boot process? Is that correct, and if so how would I do that. If that is not the case and I can keep around universal pxe stack to load dhcp again so that it exhibts a vendor code, how could I do that? Basicaly I need a wa...

...>> >> > there is no convenient way in new_linux_kernel() to control the boot >> >> > flags value. >> >> >> >> This is the part that has me questioning things and trying to recall >> >> if any other KERNEL-like directives ever utilize keeppxe. >> >> >> > >> > @Gene, >> > >> > Not being a developer myself, I don't understand this "other >> > KERNEL-like directives" sentence. I do know what "kernel-like >> >> Those directives which acts like KERNEL, s...

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

...my existing infrastructure. Except the g/pxelinux.0 and .c32 files everything else is the same as I use in production with syslinux 3.51. The HTTP fetching seems to work in my testing so far. I've got menus being dynamically generated from a PHP script. I did find that my dos boot disks using keeppxe and the 3com undi driver no longer work and give the errors 'Set Packet Filter failed' and 'Error: 255 Unable to Bind'. I'm not sure if keeppxe problem I'm observing is related to the chainloading other NBPs from gpxelinux.0 problem which isn't working yet according to...

On Fri, Jun 10, 2016 at 2:06 AM, Adam Goldman via Syslinux <syslinux at zytor.com> wrote: > PXELINUX has stopped recognizing the keeppxe option on the kernel > command line. Here is a patch to make it work again. > > With COM32, it is no longer possible to use preprocessor directives to Not COM32 but ldlinux.c32 as a result of splitting the core binary in two with variant-specific code to load another file of common code....

On Thu, Jun 16, 2016 at 06:20:31PM +0300, Ady via Syslinux wrote: > the main idea: if the LINUX directive would be capable of using / > parsing "keeppxe", then it might make sense to have the same capability > in linux.c32 (in addition to mboot.c32 and chain.c32). AFAICT, the following modules lead to the syslinux_boot_linux code path: ldlinux.c32 lua.c32 (for boot_linux and boot_it; and run_kernel_image for Linux kernels only) linux.c...

On Sun, Mar 05, 2017 at 05:39:42PM -0500, Gene Cumm wrote: > Adam, how about https://github.com/geneC/syslinux/compare/keeppxe ? I > changed to using strstr() and a uint16_t (to match the called > function) Hi Gene, Looks fine. Thanks. -- Adam