similar to: bug (I think) in gpxelinux.0 ?

Hi, I have a working PXE environment that chainloads gPXE and loads pxelinux.0 afterwards. As I'm also interested in doing san boot (in my case aoe) I tried loading the new gpxelinux.0 file instead of my gPXE --> pxelinux.0 setup (works) and booting from my aoe target by adding this to the default config file: LABEL doaoe MENU LABEL Continue AoE kernel sanboot.c32 append

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.

I am using the following simple menu and 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

but it works well with pxelinux.0 in 3.75

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

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

First let me say I'm really excited about the possibility of dynamic menu creation over http using php. When this is stable it will make maintinging some of our pxelinux infrastructure much easier. Id like to thank all involved; I'm really looking forward to the gpxe intigration. After hpa's announment for 3.70pre7 I begain testing. I dropped the new gpxelinux.0 and new c32 modules

Hi, I've been trying a couple of day now, but I can't seem to figure it out. On www.etherboot.org, I found the example of configuring gPXE so that it mounts an iSCSI lun and then boot from CDROM so you are able to install on the LUN. But if I use gpxelinux.0 (latest release 3.73), with sanboot.c32 like this: label sanboot2008srv menu label ^[iscsi] Windows server 2008 kernel

gpxelinux.0 (3.73 and 3.74) can't work with microsoft RIS (startrom.n12),but pxelinux.0 (3.73 and 3.74) can work with microsoft RIS well. keeppxe can't work in 3.74.

I am using memdisk to remotely flash the BIOS and other firmware. It works well for most flash programs. After the flash I need to initialize the NIC to send a signal to my management server that the flash is complete. I am curious as to how others have solved this problem. Thanks.

Hi Peter. I have some question: on my nt4 dhcp server i have added the option (067 Bootfile Name - ......\boot.ovl) the boot.ovl is needed for automatic installation and configuration with on command ccm (www.ontechnology.de) the clients boot with pxe this boot.ovl. now my question: I want to to boot in a menue with two options. first and default boot, is to boot the boot.ovl and second is

I have a lab in which I keep all my computers set to try network boot first that way it is easy to put a file in pxelinux.cfg of the mac address of a faulty machine and have it build itself or run diagnostics. Up till recently I used pxelinux.0. I have been trying out gpxelinux so that I can use its http fuctionality to download initrd images faster to boot. I just discovered that its local boot

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

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

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

> 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

First off I love syslinux and it has worked flawless for us on the unix side of the realm. We're trying to use our ghost images within a dos netboot 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

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

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

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