similar to: syslinux EFI?

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, just before loading the >>

> Message: 3 > Date: Fri, 06 Jun 2014 08:13:36 -0700 > From: "H. Peter Anvin" <hpa at zytor.com> > To: Andrew Rae <A.M.Rae at leeds.ac.uk>, "'syslinux at zytor.com'" > <syslinux at zytor.com> > Subject: Re: [syslinux] EFI booting over network - can't then load > anything > Message-ID: <5391DAA0.2050207 at

Hi all - I'm not sure if it's appropriate to ask this here, but I don't see this question explicitly answered anywhere. Is there an EFI version of "pxelinux.0" that will function basically the same way and read the same pxelinux.cfg/default menu files? I've got a really dodgy grubx64.efi EFI PXE menu up at work, but it can't load the 1.2 gigabyte LiveCD that we use

Op 2014-08-01 om 20:35 schreef Ady: > Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 > (with an optional Syslinux menu containing multiple entries). What I would like to have is the same thing for network boot. So having one topdirectory on the TFTP server that can serve several "architectures". > Problem (solved) #1: The default directory location for

I am currently unable to get Syslinux v6.03 to load kernel + ramdisk when booting from a PXE server in EFI mode. Is this a feature that is currently supported? If not, is there a known time frame for which support will be added? Thanks. -Bryan

Hello, I am pxebooting a large linux kernel (with embedded initramfs) that is around 250 MB in size. When booting a board in legacy BIOS mode, the pxelinux.0 executable is transferred to the board and takes over, from where loading and booting this large kernel works as expected. Actually, better than expected, as no tftp file size limit is incurred. If I change the BIOS settings to UEFI mode,

Hi all, wasnt sure whether this was the best place to put this information; but something seems to have gone 'backwards' in the later pre-releases of 6.03 regarding network booting. below are results of me testing - i did each a few times to make sure they are valid results. hope it helps identify something that's gone awry ? so far, 6.03 pre11 and pre13 (excluding efi32) seem most

There are no pre-compiled binaries (official or otherwise) on kernel.org. I assume what is meant is https://www.kernel.org/pub/linux/utils/boot/syslinux/ At least, that is where the "downloads" page of syslinux.org directs you. Under there are the various source tarballs (tar.gz format, tar.bz2 format). Also a directory called RPMS/. But that kernel.org RPMS/ directory is devoid of

On 2014?03?07? 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 optionally be > added. > > _ from the

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:

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 syslinux.efi to bootx64.efi and to bootia32.efi. Problem (solved) #2: Each syslinux.efi needs at least its respective ldlinux module. Solution #2:

>> Are there any known problems with the performance of TFTP in (U)EFI >> environments in general or maybe just on VMWare? > I don't believe so. I use Workstation 10.0.2 on Ubuntu 12.04 for the > moment. <stupid question> and have EFI enabled? </stupid> > I hope this is a hex-core host with 6+GiB of RAM. Fedora runs on an AMD A8-6600K at 3Ghz and has 8G of

> There might be an alternative (and possibly others too): let the user > select the appropriate firmware from within pxelinux.cfg/default. > > So, keep using the same method you used in previous versions, instead > of selecting the Syslinux cfg / firmware from the DHCP snippet that > Daniel posted. > > If you actually get to pxelinux.cfg/default (as you probably used

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,

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

On 2014/4/23 ?? 09:55, Gene Cumm wrote: > The resulting config would require suffix-less module references, i.e. > "UI menu" or "COM32 ls". > > 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 >

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

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

Gene, Where did you find the precompiled binaries for syslinux 6.03-pre7? Actually, I'm interested in the pre-compiled binaries for syslinux 6.03-pre6. I went out to kernel.org, but the latest they have is 6.02. Which appears to have an endian problem in its TFTP client code (when syslinux.efi tries to connect to the TFTP server, attempts to connect to UDP port 17664 instead of 69).

Hi, background: I've managed to get EFI32, EFI64 and 'BIOS' modes all booting & working from the same TFTP/DHCP server using the setup described in message #10 here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720589#10 I'm running this inside VMWare 9 - switching between x86 and x86_64 to check both EFI32 and EFI64, and then another non efi VM for bios. issue #1: I can