similar to: SYSLINUX 3.08-pre7 released

Hi all, I have just released Syslinux 3.83. Special thanks to my employer, Intel, for letting me spend time on this. It is somewhat of a meager release despite four months, as most of the work has gone into the future-work branches. -hpa Changes in 3.83: * PXELINUX: clear memory before handing over to a chainloaded NBP. This may help avoid a bug in Windows RIS. *

I have produced a first cut of integrating gPXE with PXELINUX. This builds, in addition to the usual pxelinux.0, an image called gpxelinux.0 which includes the gPXE network stack. The result is that one can now download images via (almost) any network protocol supported by gPXE, including http. This lets one do fun things like using a CGI or PHP script for the configuration file. SAN

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

Hi all, I have merged Tim's patches to the mboot loader, and have pushed it out as 3.20-pre7. I guess I'm going to actually have to make a 3.20 here soon... -hpa

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

Syslinux 3.85 is a bug fix and minor new feature release. The biggest change is undoubtedly that gPXELINUX is now considered feature complete, and should be able to be a drop-in for PXELINUX for all uses. Special thanks to Intel Corporation, my current employer, for their support for my Syslinux work. Changes in 3.85: * gPXELINUX: updated to gPXE 1.0.0. gPXELINUX can now do NBP

(Sorry, Outlook webmail prohibits me from proper replying/quoting) >it has the nice effect that you can load the El Torito >CD-ROM driver. Which seems logical if you boot a kernel (like Linux, or Memdisk with an imagefile), but not when doing a local boot (diskette/harddisk) In other words: boot from cdrom, and if you then load a disk-image, eltorito.sys should load. If not loading a

On Thu, Mar 6, 2014 at 10:55 AM, Bryan Romine <bromine1027 at gmail.com> wrote: > Sorry for the confusion, I am actually using 6.02. It turns out that I was > trying to use the 32-bit efi binary to load 64-bit kernels. I switched to > using "syslinux64.efi" but it hangs during boot, just before loading the > menu. I have not been able to get it to load the menu

On 2019-12-13 08:36, Gregory Lee Bartholomew via Syslinux wrote: > On Fri, 2019-12-13 at 08:47 +0100, jps--- via Syslinux wrote: >> Hi, >> >> We are currently testing PXE booting with syslinux.efi in UEFI mode. >> This is working fine. >> However the loading of syslinux.efi and the config files is still using >> TFTP protocol, the rest kernel and initrd is

On 31-07-15 18:45, Patrick Masotta wrote: >>>> > 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

Hi all, I have pushed out Syslinux 4.00-pre20, which includes support for running out of a new working directory: if a directory is given on the append line to a "config" statement, that will now be considered the new working directory. The "pathbased" branch is now the active development branch for Syslinux 4. With this checkin, I now expect that the major restructuring

On 06/16/2014 07:12 PM, H. Peter Anvin wrote: > On 06/16/2014 02:57 PM, Alexander Perlis wrote: >> Here's what I mean by 'chainloading to install an automatic http prefix': > > The other option is to use a very small default configuration file > containing only: > > default reload > label reload > config http://...path to real config file .../

Hello dear list, 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. So it was time for the next step. Migrate this setup to our automated testing environment that runs

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

Inspired from a similar patch posted on grub-devel for Grub2 I immersed myself into the code of Grub Legacy and came up with this absurdedly simple patch to allow syslinux or other bootloaders residing in logical partition to be chainloaded from GRUB Legacy (0.9x). Hoping it to be of help, regards Fulvio Scapin -------------- next part -------------- A non-text attachment was scrubbed... Name:

> On 06/16/2014 07:12 PM, H. Peter Anvin wrote: > > On 06/16/2014 02:57 PM, Alexander Perlis wrote: > >> Here's what I mean by 'chainloading to install an automatic http prefix': > > > > The other option is to use a very small default configuration file > > containing only: > > > > default reload > > label reload > >

> Some magic in dhcpd.conf: > > if option architecture-type = 00:09 { > filename "efi64/syslinux-87020-or.efi"; > option pxelinux.pathprefix "http://bla/efi64/"; > } elsif option > architecture-type = 00:07 { > filename "efi64/ipxe-git87981.efi"; > } else { > filename

Hello, Starting version PXELINUX 3.83 2009-10-05, i am not able to boot anymore using "localboot 0" entry. It show "" Booting from local disk... """ Then loop on the network boot of the interface then after a few try show the message: """ It appears your computer has less than 268K of low ("DOS") ... Boot failed: press a key to

I just uploaded SYSLINUX 3.72-pre7. I'm hoping this will be the final 3.72 prerelease. Please test it and holler if something is (still) broken. -hpa

Still interested in pre-compiled binaries for 6.03-pre6. But my comment about 6.02 TFTP brokenness may speak more to my lack of understanding of the TFTP protocol than to any pxelinux 6.02 code problems. It seems that when TFTP sends an OACK back to syslinux.efi, it sends it from another port than 69. So, it seems to be opening a data connection back to the TFTP client off an ephemeral port.