similar to: gpxelinux 3.70pre7 - keeppxe problem

but it works well with pxelinux.0 in 3.75

Hi Can we get the result of an intigration without the absolute error? for example f1<-function(x1){(1/gamma(alpha))*x1^(alpha-1)*exp(-x1)*log(x1)} I1<-integrate(f1, 0, (max(cc)-tau1+(theta2/theta1)*tau1)/theta2) I1 0.08007414 with absolute error < 7.2e-05 I need the answer 0.08007414 withou the other part(with absolute error <7.2e-05) how can we do that? thank you and take care

Hi Peter et al, Just wanted to let you know my heartfelt appretiation of what you and the other devs have done in integrating gpxe and pxelinux... it works wonderfully well for me... I simply swapped my pxelinux.0 for my gpxelinux.0 and modified my pxelinux.cfg/default to use urls to refer to the kernel and initial ram disk images and it worked perfectly (dns resolution and all). This is a huge

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 356

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 linux utilities to look at the pxe

On Tue, Jun 14, 2016 at 12:33 PM, Ady via Syslinux <syslinux at zytor.com> wrote: > >> > kernel.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

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,

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.

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

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

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

On Wed, Jun 15, 2016 at 1:02 PM, Ady via Syslinux <syslinux at zytor.com> wrote: > >> On Tue, Jun 14, 2016 at 12:33 PM, Ady via Syslinux <syslinux at zytor.com> wrote: >> > >> >> > kernel.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 >>

All,? I am running a Fog Server and PXE booting 0.5.2 HDT image. The system boots and but I am not able to dump the system data to the tftp server.? I get a message "PXE stack was not detected. Dump feature is not available" This is the config i am using? kernel /fog/hdt/memdisk append initrd=fog/hdt/hdt.img.gz keeppxe Cheers Ian -------------- next part -------------- An HTML

> Pushed. Thank you for digging so deeply on this. > Gene, For the c32 modules to be able to use the keeppxe option, and considering that the issue in v.5.+ is that 'IS_PXELINUX' is/was dead code, is there any chance that the code in: com32/modules/whichsys.c would help? I mean, as a different way of detecting the Syslinux variant. In fact, the original idea of having the

Pushed. Thank you for digging so deeply on this. On Tue, Mar 7, 2017 at 6:01 AM, Adam Goldman <adamg at pobox.com> wrote: > 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

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

> On Wed, Jun 15, 2016 at 1:02 PM, Ady via Syslinux <syslinux at zytor.com> wrote: > > > >> On Tue, Jun 14, 2016 at 12:33 PM, Ady via Syslinux <syslinux at zytor.com> wrote: > >> > > >> >> > kernel.c:new_linux_kernel() to load_linux.c:bios_boot_linux() because > >> >> > there is no convenient way in new_linux_kernel() to

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 variant. Also, I moved the relevant code from

Hi, I want to use PXELINUX to load a DOS disk image which I currently use for Win2K/XP unattended installs. I want to move away from reliance on specific NDIS2 drivers and use the 3Com UNDIS3C driver instead. I have used this successfully to start the MSClient, but the problem is that the UNDI and PXE layer take about 90K of base memory, which means that WINNT.EXE has insufficent memory to run

It appears that the 3.74 completely broke the "keeppxe" directive -- not due to the command-line parser, but due to mishandling of the flag later. I consider this to be severe enough to do a short-cycle 3.75. As a result, I would like help with: a) are there any other bugs that snuck through? b) once I have a 3.75-pre1, I would really appreciate help testing it. The goal is to have