search for: efi64

Hi, Matt Fleming wrote: > 'make efi64' will build just for x86-64. Likewise, 'make efi32' will > build just for i386. You can combine these, so to build BIOS and efi64 > you'd do, > > make bios efi64 'make efi64' failed with: ld -T /tmp/syslinux/efi/x86_64/syslinux.ld -Bsymbolic -pie -nostdlib -z...

...gt; > 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. Likewise, 'make efi32' will build just for i386. You can combine these, so to build BIOS and efi64 you'd do, make bios efi64 > Am I wrong? Did you install gnu-efi from source or from your distributions package manager? You need both the x86-64 l...

...en I referred to http://www.syslinux.org/archives/2015-June/023641.html And used the patch provided then it again hung but at different step Getting cached packet My IP 192.168.103.41 (hung here) >From /var/log/messages Oct 7 01:16:10 foreman in.tftpd[43905]: RRQ from 192.168.103.41 filename efi64/syslinux.efi Oct 7 01:16:10 foreman in.tftpd[43905]: tftp: client does not accept options Oct 7 01:16:10 foreman in.tftpd[43906]: RRQ from 192.168.103.41 filename efi64/syslinux.efi Oct 7 01:16:10 foreman in.tftpd[43907]: RRQ from 192.168.103.41 filename efi64/ldlinux.e64 Oct 7 01:16:10 foreman...

Hello, Apparently I can't put absolute path in the config file. Here is what happen. The DHCP server send the option filename = "/srv/tftp/efi64/syslinux.efi". The client download and boot on this file. It find its first configuration in /srv/tftp/efi64/pxelinux.cfg/default Then, I'd like to chain on the config file /srv/tftp/debian-installer/efi64/pxelinux.cfg/default. Thus the first file "default" contains this: label...

Hello, I tried to make my own binary with 'make efi64 install' but it fail with make[3]: *** No rule to make target `/root/syslinux-6.02-pre3/efi64/efi/../core//writestr.o', needed by `syslinux.so'. Stop. make[3]: Leaving directory `/root/syslinux-6.02-pre3/efi64/efi' make[2]: *** [install] Error 2 make[2]: Leaving directory `/root/...

On Wed, Oct 7, 2015 at 6:09 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> -----Original Message----- >> From: Gene Cumm [mailto:gene.cumm at gmail.com] >> Sent: Wednesday, October 07, 2015 4:43 PM >> To: For discussion of Syslinux and tftp-hpa; Geert Stappers >> Subject: Re: [syslinux] UEFI: Failed to load ldlinux.e64/ldlinux.e32 >> >> On Wed, Oct

...arget/EFI/BOOT/SYSLINUX.CFG > > > > I don't think that exists? (see list below) > > > In our "first test" (simple boot prompt), we created > "target/EFI/BOOT/SYSLINUX.CFG". In our "second test" we _added_ > "target/EFI/BOOT/SYSLINUX/EFI64/SYSLX64.CFG". Part of my intention was > to test whether it actually reaches one cfg or the other. Although > there are special circumstances in which the first one could still be > useful, I don't want to leave it there while troubleshooting. Ah, took out the first cfg. sounds...

On Thu, Apr 21, 2016 at 6:39 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > 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 (vmware specific) >> autoselect.lua >> >> These files are a...

...9; to > 'EFI/BOOT/SYSLINUX/' (all uppercase). > > * Once we don't have 'EFI/BOOT/syslinux/' anymore (because we renamed > it to all-uppercase), in your "target" device, we want (at least) one > additional directory: > _ "target/EFI/BOOT/SYSLINUX/EFI64/" > > (all uppercase) > > * From the 'efi64' subdirectory (tree) for syslinux files in your > OS/package/archive, you want to copy all "*.c32" files to: > > _ "target/EFI/BOOT/SYSLINUX/EFI64/*.c32" > > Let me re-emphasize this point: the...

...t seems with the binaries you had given, initrd image is not loading. It wait for some time to load initrd image and then reboots the machine. Here is the snapshot Untitled12.png attached. Here is the output from tftp server Oct 8 20:49:22 foreman in.tftpd[5383]: RRQ from 192.168.103.41 filename efi64/syslinux.efi Oct 8 20:49:22 foreman in.tftpd[5383]: tftp: client does not accept options Oct 8 20:49:22 foreman in.tftpd[5384]: RRQ from 192.168.103.41 filename efi64/syslinux.efi Oct 8 20:49:22 foreman in.tftpd[5387]: RRQ from 192.168.103.41 filename efi64/ldlinux.e64 Oct 8 20:49:22 foreman in...

Dear Syslinux developers, I'd like to continue the discussion about this: http://www.syslinux.org/archives/2014-February/021659.html i.e. different directories for *.c32 files of BIOS, EFI32, and EFI64. I am wondering why we can not have *.c32 for the COMBOOT files of BIOS, *.e32 for the COMBOOT files of EFI32 *.e64 for the COMBOOT files of EFI64 As now the ldlinux file of syslinux 6.0x has, i.e. ldlinux.c32: BIOS ldlinux.e32: EFI IA32 ldlinux.e64: EFI X64 Because from the doc: http://www.syslin...

...s /pxelinux.c32 & /ldlinux.e32 - also then tries to download /syslinux/ldlinux.e32, /boot/isolinux/ldlinux.e32, and /syslinux/ldlinux.e32 - then boot fails 6.03-pre15 EFI32: fails as per pre14 6.03-pre16 EFI32: fails as per pre14 6.03-pre17 EFI32: fails as per pre14 ----------------- 6.03-pre11 EFI64: fails - gets stuck in a loop downloading files - differs each boot 6.03-pre12 EFI64: fails - downloads /pxelinux.e64 & /ldlinux.e64 - then continually retries to download ldlinux.e64 6.03-pre13 EFI64: boots OK TFTP & HTTP 6.03-pre14 EFI64: fails - downloads /pxelinux.e64 & /ldlinux.e64...

...bian-cd at lists.debian.org> > > Swell. I have a few friends, I'll find someone :p > > > > I came to this conclusion by swapped out the files from the debian > > package with syslinux-6.04-pre1.tar.gz and get a nice menu. > > > > -cp /usr/lib/SYSLINUX.EFI/efi64/syslinux.efi $target/EFI/BOOT/BOOTX64.EFI > > -cp /usr/lib/syslinux/modules/efi64/ldlinux.e64 $target/EFI/BOOT/LDLINUX.E64 > > -cp /usr/lib/syslinux/modules/efi64/* $target/EFI/BOOT/SYSLINUX/EFI64 > > > > +# wget -N https://mirrors.edge.kernel.org/pub/linux/utils/boot/syslin...

...9;t taken > > the time to track down yet. > > Does any of this look like a problem? > > > > > (snip) > > Yes, of course you don't have a menu, because you are using c32 files > from the BIOS platform (those that came with the original boot.img), > not from EFI64. Right. we can ignore all that for now. > > For this "troubleshooting", please forget about the original d-i setup > (for now), as it is not relevant for what you want to achieve at this > initial step. ok, lets build from an almost blank image. it will still have the sysl...

On Thu, 11 Jul, at 01:55:12PM, Michael Szerencsits wrote: > Hello, > > I tried to make my own binary with 'make efi64 install' but it fail with > > make[3]: *** No rule to make target `/root/syslinux-6.02-pre3/efi64/efi/../core//writestr.o', needed by `syslinux.so'. Stop. > make[3]: Leaving directory `/root/syslinux-6.02-pre3/efi64/efi' > make[2]: *** [install] Error 2 > make[2]:...

...iner: Debian CD Group <debian-cd at lists.debian.org> > Swell. I have a few friends, I'll find someone :p > > I came to this conclusion by swapped out the files from the debian > package with syslinux-6.04-pre1.tar.gz and get a nice menu. > > -cp /usr/lib/SYSLINUX.EFI/efi64/syslinux.efi $target/EFI/BOOT/BOOTX64.EFI > -cp /usr/lib/syslinux/modules/efi64/ldlinux.e64 $target/EFI/BOOT/LDLINUX.E64 > -cp /usr/lib/syslinux/modules/efi64/* $target/EFI/BOOT/SYSLINUX/EFI64 > > +# wget -N https://mirrors.edge.kernel.org/pub/linux/utils/boot/syslinux/Testing/6.04/sys...

...) environments whereas > it might be a requirement in others; YMMV - reports are appreciated. > > For more details about several alternative official installers for > Syslinux, see: > > www.syslinux.org/wiki/index.php/Install > > > 9_ Create 'target/EFI/BOOT/SYSLINUX/EFI64/'. > > Optionally, create the directory 'target/EFI/BOOT/SYSLINUX/EFI32/' too. > > > 10_ From the 'efi64' subdirectory for Syslinux files in your OS, copy > 'syslinux.efi' to 'target/EFI/BOOT/BOOTX64.EFI'. > > Optionally, from the 'efi...

...;gene.cumm at gmail.com>> wrote: > > > 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 (vmware specific) > > &g...

...; > Additionally, I documented the basics of my test system here: > > http://www.syslinux.org/archives/2014-February/021740.html > > Bear in mind, by "URL-like file locations", I mean that if we have > "bios/pxelinux.0", "efi32/bootia32.efi" and "efi64/bootx64.efi" as > paths relative to the root and a common kernel "shared/vmlinuz", you'd > use "::shared/vmlinuz" or "tftp://<my-server>/shared/vmlinuz" in your > configs instead of "../shared/vmlinuz" (which is prone to issues). Becau...

> 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 > following 2 lines: > =...