similar to: SYSLINUX 1.73-pre4 released

I have just released SYSLINUX 2.09-pre4 with a few changes: a) SYSLINUX should now correctly handle mode changes from within a COMBOOT program. b) Tweaks to the menu system to avoid the "grey text on black" problem. c) A new color scheme for the menu system (Murali, check it out and see if you think it works for you.) ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/

Hello all, I just installed syslinux 2.10 on my usb-stick. It still boots then, but doesn't load initrd.gz (same config file..). Reverting back to syslinux 2.09 works fine, eg: initrd.gz is loaded. Something changed in initrd handling code? greetz, Jaap Crezee NB I am willing to share you more information or hints how to solve the problem. I am using kernel 2.6.7-bk20

Hi! as i know that you like test reports, here are some... Testing environment: CompactFlash card, connected with an USB adapter to a Compaq Evo D310 frontal USB port. This machine boots via USB quite well with syslinux. 3.09 boots ok, no problem 3.10-pre2 does not boot 3.10-pre3 does not boot 3.10-pre4 does not boot 3.10-pre5 locks up pc 3.10-pre6 locks up pc 3.10-pre7 writes

I've been working with Matt Burgess here on this problem, and have found the following: syslinux 3.08-pre10 ? broken >>> config.inc:max_cmd_len=255 syslinux 3.08-pre11 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.08 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.09-pre1 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.09-pre2 ? broken

I've just been playing with PXELINUX 1.74, and I can't get NBP chaining to work. First problem is that the code doesn't appear to recognize .0 files. I could be completely mistaken (x86 assembler isn't my forte) but I think the problem in pxelinux.asm is here: ------------------------------------------------------------------------ .one_step: mov ecx,[di-4]

Hi all, I have just pushed out SYSLINUX 3.55-pre5 and 3.60-pre7. I have decided to give them both release candidate status, with the intent of having a simultaneous 3.55 (bug fixes only) and 3.60 (new functionality) release. Please test them out and let me know how they do. -hpa

HPA, I believe I've found a possible bug with /menu. This against the unmodified -pre5 snapshot. SRC: http://www.survivaldisk.com/menutest.c COMPILED: http://www.survivaldisk.com/menutest.com It's easiest explained if you just compile the .c and experience it for yourself, anyways. If you have two submenus nested within each other and then call a third menu it will bring up the

>>> Using VMware I built a test setup of a server with dhcp, tftp and a http-server and several pxe-clients with EFI mode turned on. This setup worked, albeit with the exponential-like decay of IO rate I described earlier. The work-around of using HTTP works beautifully though. <<< ""exponential-like decay of IO rate"" could you please post a link on

I found that the version of isolinux.bin (and the debug version too) doesn't work on my Via C3 system. I get the SAY text, but never the boot: prompt. C-A-Del doesn't reboot either. The debug version does not print anything after announcing it's opening the config file. Only the single SAY text follows. The cursor sits on the next blank line, useless (no responses to key presses).

I'm trying to pick a kernel for ext3. Looking at the web page (http://www.zip.com.au/~akpm/linux/ext3/), I see little that clues me in to the fact that "most" of ext3 is already in (some|most|all) of the 2.4 series kernels. Am I correct that most of the patches listed on the web page now are actually bug fixes to the existing ext3 code, as opposed to previous patches that actually

Hi all, I have pushed out Syslinux 3.81-pre4, which is now a release candidate for 3.81. This version includes halt on idle, and so I'm very keen on getting this tested. -hpa

Hi all, I have pushed out a SYSLINUX 3.32-pre4. This version attempts to work around the "missing floppy drive" issue. If you have systems on which MEMDISK doesn't work without a floppy drive, I would appreciate it if you would test this out. -hpa

In another mail I discussed my adventures on netbooting syslinux 6.03 and newer from iPXE, either from an emulated rom on qemu/kvm/ovmf or by chainloading via ipxe.efi onto a real HP Proliant DL360 gen9 piece of iron. You might have asked yourself, why chainload? Why not load it directly? Believe me, i tried. First I had to 'fix' my dhcpd.conf because HP probably read the docs on

> Gesendet: Donnerstag, 27. Juni 2013 um 17:44 Uhr > OK, now that's just weird. You don't see any response whatsoever from > tapping at the keys? > > If you set a TIMEOUT, can you run a DEFAULT even though you cannot type? > That's one way to figure out whether the machine is dead at that point > or not. A useful DEFAULT might be reboot.c32, that way even if the

Hello, I am using the pxelinux.0 and memdisk files from distribution syslinux-3.36. I am no longer able to access the real floppy disk drive B: instead I just get a mirrored copy of the emulated floppy disk A: The default config file is as follows label 1 kernel memdisk append initrd=kd202.img I was previously using the sysliunx-3.20 distribution which gave me access to the real floppy

>>> Is this possible? Are you saying the FW is stealing the DHCP response away before iPXE gets it?? I haven't thought of this possibility. Or am I misunderstanding you? <<< I'm saying that "probably" iPXE is trigerring a new PXE sequence with a different arch but the one that finally loads the new NBP is really the FW. >>> Since I'm

hi, realtek 8139 \ 8100sc NICs can not be used PXELINUX 5.0 -> 6.0-pre4 version boot, please verify.

On Fri, 28 Jun, at 01:44:56AM, Ady wrote: > 2_ If relevant, fixing the [MENU] INCLUDE directive in 6.xx (which > might be the same fix applied just before the release of 5.11-pre3; I > don't know). Yes, this fix is applicable to the 6.xx releases and will be merged before the final 6.01. -- Matt Fleming, Intel Open Source Technology Center

On Fri, 28 Jun, at 10:56:00AM, Helmut Hullen wrote: > Sorry - 5.11-pre3 works well, but 6.01-pre4 (compiled with "make bios") > still has the "include" error. The fix for INCLUDE is in 6.01-pre5. -- Matt Fleming, Intel Open Source Technology Center

It seems that at least SYSLINUX 1.73-pre4 and -pre5 had some very serious bugs in it, so here is a SYSLINUX 1.73-pre6 to test out; don't be surprised if there are more in short order... :) ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa