Displaying 20 results from an estimated 20000 matches similar to: "Syslinux 6.xx new directory structure and binary files"
2015 Aug 07
2
EFI: HP + syslinux = crash
>
> For a KISS troubleshooting, *all* the c32 files should be located
> together, in the root of the filesystem, where syslinux.efi and
> ldlinux.e64 (for EFI x86_64) should be located too.
>
I should clarify, just in case. In my previous email, when I mentioned
"all" the c32 files, I actually meant all the c32 files that pertain to
the adequate firmware's
2013 Jun 29
0
Syslinux 6.00 released
Hallo, Matt,
Du meintest am 29.06.13:
[...]
>> I didn't expect that. "make bios" will run without an error, but I
>> thought it should be possible to build syslinux 6.01-pre5 with just
>> make (when gnu-efi >=3.0u is available). Or how should I compile a
>> version for an EFI-capable system (x86_64)?
> 'make efi64' will build just for x86-64.
2013 Jun 25
3
Syslinux 6.00 released
On Tue, 25 Jun, at 03:14:32PM, Gene Cumm wrote:
> Is there a way to use a rule in mk/local.mk to block the automatic
> building of efi32 & efi64 in order to prevent the error for those that
> do not want efi32/efi64 built and don't have a build box capable of
> it?
'make bios' will only build the BIOS files.
We could probably fabricate a script of some sort to check
2016 Apr 21
0
Creating Syslinux UEFI usb boot
On Thu, Apr 21, 2016 at 3:29 AM, Atle Holm <atle at team-holm.net> wrote:
> Under EFI/BOOT are the following files:
> BOOTIA32.EFI (from efi32/efi/syslinux.efi)
> BOOTX64.EFI (from efi64/efi/syslinux.efi)
> ldlinux.sys (copied from root of partition)
> lua.c32
> mboot.c32
> menu.c32
> syslinux.cfg
> vesamenu.c32
> KS.CFG (vmware specific)
> BOOT.CFG
2015 Aug 07
1
Aside comments WAS:EFI: HP + syslinux = crash
> On 07-08-15 05:56, Ady via Syslinux wrote:
> > If we are talking about UEFI x86_64, then the c32 files are all those
> > located under the "efi64" directory tree of the Syslinux build. Plus,
> > the relevant "ldlinux.*" core module.
>
> I wonder why ldlinux.c32 got renamed to ldlinux.e64 whereas all other
> modules remained their c32 extension.
2014 Jul 09
0
isohybrid binary not in 6.03-pre18? (utils bt is in bios/utils?)
On Jul 9, 2014 6:11 AM, "Michael D. Setzer II" <mikes at kuentos.guam.net>
wrote:
>
> On 9 Jul 2014 at 6:01, Gene Cumm wrote:
>
> Date sent: Wed, 9 Jul 2014 06:01:22 -0400
> Subject: Re: [syslinux] isohybrid binary not in 6.03-pre18? (utils
bt is in bios/utils?)
> From: Gene Cumm <gene.cumm at gmail.com>
> To: "Michael D. Setzer,
2016 Apr 20
0
Creating Syslinux UEFI usb boot
On Wed, Apr 20, 2016 at 5:03 AM, Atle Holm <atle at team-holm.net> wrote:
> I recognize hardware with Lua and execute the ESXi installer with
> configuration files for that hardware.
> This works fine with normal Syslinux boot, but I want to get it working for
> UEFI boot as well.
>
> I found efi64/efi/syslinux.efi and efi32/efi/syslinux.efi in the installer
> source,
2014 Jul 09
4
isohybrid binary not in 6.03-pre18? (utils bt is in bios/utils?)
On 9 Jul 2014 at 6:01, Gene Cumm wrote:
Date sent: Wed, 9 Jul 2014 06:01:22 -0400
Subject: Re: [syslinux] isohybrid binary not in 6.03-pre18? (utils bt is in bios/utils?)
From: Gene Cumm <gene.cumm at gmail.com>
To: "Michael D. Setzer, II" <mikes at kuentos.guam.net>
Copies to: Syslinux at zytor.com
>
> On Jul 9, 2014 5:15 AM, "Michael D. Setzer II"
>
2014 Mar 07
0
Syslinux EFI + TFTPBOOT Support
>
>
> On 2014/3/7 05:23, Gene Cumm wrote:
> > 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,
2015 Aug 07
0
EFI: HP + syslinux = crash
On 07-08-15 05:56, Ady via Syslinux wrote:
> If we are talking about UEFI x86_64, then the c32 files are all those
> located under the "efi64" directory tree of the Syslinux build. Plus,
> the relevant "ldlinux.*" core module.
I wonder why ldlinux.c32 got renamed to ldlinux.e64 whereas all other
modules remained their c32 extension. This confused me as a beginner.
2013 Jun 25
0
Syslinux 6.00 released
On Mon, Jun 24, 2013 at 2:20 PM, Matt Fleming <matt at console-pimps.org> wrote:
> You need a newer version of gnu-efi, gnu-efi 3.0u, which is the release
> containing the EFI_SERVICE_BINDING definition.
Is there a way to use a rule in mk/local.mk to block the automatic
building of efi32 & efi64 in order to prevent the error for those that
do not want efi32/efi64 built and
2013 Jun 25
0
Syslinux 6.00 released
On 06/25/2013 01:03 PM, Matt Fleming wrote:
> On Tue, 25 Jun, at 03:14:32PM, Gene Cumm wrote:
>> Is there a way to use a rule in mk/local.mk to block the automatic
>> building of efi32 & efi64 in order to prevent the error for those that
>> do not want efi32/efi64 built and don't have a build box capable of
>> it?
>
> 'make bios' will only build
2013 May 07
2
Question about syslinux EFI alpha version
Dear list,
I would like to add and test EFI boot support for a live system. Since I
use isolinux and syslinux for everything, I would be glad to have
syslinux.efi as boot loader for EFI-only machines, so I can just keep
all syslinux.cfg files, help files and boot screen as they are.
I checked out version 6.00-pre git of syslinux (the "firmware" branch)
and was able to compile efi32 and
2014 Mar 07
0
Syslinux EFI + TFTPBOOT Support
>
> On 20140307 18:24, Ady wrote:
> > Hi Steven,
> >
> > Perhaps this could be of some basic sample/help, being based on
> > Debian:
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720589
> >
> > where:
> > _ if gpxelinux.0 is needed, it should probably be replaced by ipxe.
> > _ lpxelinux.0 (from official Syslinux archive) could
2014 Mar 07
0
Syslinux EFI + TFTPBOOT Support
On Fri, Mar 7, 2014 at 12:34 PM, Bryan Romine <bromine1027 at gmail.com> wrote:
> I'm convinced that my Syslinux install may be broken with all the hacking
> around and testing I have been doing. If I were to install fresh from the
> syslinux-6.03-pre7 archive, what would I need to do. I do not see any
> documentation on installation other than "make installer" in
2013 Sep 19
0
One DHCP/PXE config for BIOS, EFI32, and EFI64 clients?
> Dear all,
> I'd like to have a DHCP/PXE server for different arch of clients, i.e.
> BIOS, EFI32, and EFI64 clients.
> As described here:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720589
> What Daniel has proposed
> (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720589#10) should
> work, i.e. Using a file called pxelinux.cfg/bios containing the
>
2016 Apr 20
2
Creating Syslinux UEFI usb boot
I recognize hardware with Lua and execute the ESXi installer with configuration files for that hardware.
This works fine with normal Syslinux boot, but I want to get it working for UEFI boot as well.
I found?efi64/efi/syslinux.efi and efi32/efi/syslinux.efi in the installer source, copied them and named them respectively?BOOTX64.EFI and?BOOTIA32.EFI in USBDISK:\EFI\BOOT.
These were also the
2016 Apr 19
0
Creating Syslinux UEFI usb boot
On Mon, Apr 18, 2016 at 5:40 AM, Atle Holm via Syslinux
<syslinux at zytor.com> wrote:
> I am looking for guides on how to create syslinux uefi bootable usb.
> A syslinux bootable usb is created already with vesamenu and luascripting.
> Want to set up the same thing to be UEFI compatible.
What are you doing with Lua? Offering multiple boot selections
including ESXI's
2014 Mar 07
0
Syslinux EFI + TFTPBOOT Support
On Thu, Mar 6, 2014 at 6:45 PM, Bryan Romine <bromine1027 at gmail.com> wrote:
> Yes, I am using efi64/efi/syslinux.efi and
> efi64/com32/elflink/ldlinux/ldlinux.e64. I tried binaries from 6.03-pre7 and
> it gets farther along but brings up the error "Default boot device missing
> or boot failed". Maybe I am not installing all of the required dependencies?
> Are
2019 Feb 08
0
Mixed binary and source/building files in 6.04-pre3
> The end result was that I ended up refactoring much of the tree so that it now
It is known that, since version 6.00, the binary files are located
under:
_ ./bios/
_ ./efi32/
_ ./efi64/
Those directories should _only_ include binary files and documentation.
IOW, source code and/or (temporary) building files should not be in
there.
Within those subdirectories, the new 6.04-pre3 has a mix