search for: efix64

...y the chapter on UEFI at the end of that page: https://wiki.syslinux.org/wiki/index.php?title=PXELINUX#UEFI ...contains a few examples of ISC DHCPd configuration. The stumbling block for me was the syntax of these "if" scopes: if option architecture-type = 9 { filename "path/to/EFIx64/syslinux.efi"; } That "if" clause just never matched in my case. I'm running ISC dhcpd v4.3.5-3+deb9u1 . I later found out that it's the "integer literal" that is spelled wrong. What works is the following syntax: if option architecture-type = 00:09 { filename &...

...f that page: > https://wiki.syslinux.org/wiki/index.php?title=PXELINUX#UEFI > ...contains a few examples of ISC DHCPd configuration. > > The stumbling block for me was the syntax of these "if" scopes: > > if option architecture-type = 9 { > filename "path/to/EFIx64/syslinux.efi"; > } > > That "if" clause just never matched in my case. > I'm running ISC dhcpd v4.3.5-3+deb9u1 . > I later found out that it's the "integer literal" that is spelled > wrong. What works is the following syntax: > > if option...

...ere, which will > > - prepend syslnx64.cfg to the config file search path for the 64bit variant > - prepend syslnx32.cfg to the config file search path for the 32bit variant For the BIOS cpu architectures, there is already ifcpu[64].c32. In my proposal, I am focusing on EFIIA32 and EFIX64 only. If I understand correctly, your patch seems to be based on "core/fs/lib/loadconfig.c": +#if defined(__amd64__) || defined(__x86_64__) || defined(_M_AMD64) which means (again, if I understand correctly) that it affects BIOS-based systems too. As potential reference, in &quot...

On 8 Nov 2019 at 0:42, Ady Ady via Syslinux wrote: > [in response to my = Frank Rysanek's rantings a few hours earlier:] > > if option architecture-type = 00:09 { > > filename "path/to/EFIx64/syslinux.efi"; > > } ... > > if substring (option vendor-class-identifier, 15, 5) = "00007" { > > filename "pxelinux/6.git/efi64/syslinux.efi"; > > } ... > > (plus the snippet on ignore-client-uids) ................... > The dhcpd.conf exa...

...py with the fact that APPEND options cannot be transferred to different labels this way (i.e. "auto lang=en" with the "auto" label being an ifcpu64.c32 "kernel" will kill everything that was typed at the command line). > In my proposal, I am focusing on EFIIA32 and EFIX64 only. I am aware of that. My solution patches the experimental "firmware" branch of syslinux, which I use exclusively for the EFI binaries. For BIOS mode, I stay with the official "stable" branch that is included in Debian. But, the patches don't actually change much of the...

On Wed, Dec 5, 2018 at 2:21 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > After some discussion/debugging behind the scenes, we are back on > track, with updated Debian packages. > > > 0_ Starting from an _original_ (so-called "hd-media") boot.img mounted > in "target" (or "$target", or some similar notation), and the version

Hello Ady & list, On Wed, Aug 27, 2014 at 08:17:51AM +0300, Ady wrote: > > Hello Ady, > > > > On Fri, Aug 01, 2014 at 08:35:27PM +0300, Ady wrote: > > > Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 > > > (with an optional Syslinux menu containing multiple entries). > > > > > > Problem (solved) #1: The default

> Hello Ady, > > On Fri, Aug 01, 2014 at 08:35:27PM +0300, Ady wrote: > > Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 > > (with an optional Syslinux menu containing multiple entries). > > > > Problem (solved) #1: The default directory location for both > > syslinux.efi is the same. > > > > Solution #1: Rename each