search for: syslinux64

Hello, I wanted to recompile syslinux64.exe (windows 64bit binary) on ubuntu. The default ./find-mingw64.sh script failed to locate mingw64 on ubuntu, even after root at htpc:~# apt-get install gcc-mingw-w64 So I had to patch the script to let it find mingw64 on ubuntu as well. Patch is below, please apply to syslinux sources: ---...

...n the mailing list, there may have been a bunch of fixes that have been committed that have some bearing on uEFI, and even some on the mailing list that appear to be aimed at solving similar problems. However, I can't manage to build a new one based on the repository. Is there a newer-than-6.03 SYSLINUX64 EFI binary sitting around somewhere, or can someone point me to build directions? Thanks! See output below. >>Start PXE over IPv4. Station IP address is 10.0.81.200 Server IP address is 10.0.81.101 NBP filename is /warewulf/syslinux64.efi NBP filesize is 199952 Bytes Downloading N...

On Sat, Nov 21, 2015 at 1:04 AM, Andrey Plankin via Syslinux <syslinux at zytor.com> wrote: > Hello, > > I'm booting linux-3.16-686-pae kernel (32-bit) via syslinux.efi 64-bit version. > After boot linux sees only 2.5G of RAM while system has 32G installed. Why not use a 64-bit kernel with such a large machine? Do you have the config used to build that kernel? I'm

2015-11-21 7:04 UTC+01:00, Andrey Plankin via Syslinux <syslinux at zytor.com>: > Hello, > > I'm booting linux-3.16-686-pae kernel (32-bit) via syslinux.efi 64-bit > version. > After boot linux sees only 2.5G of RAM while system has 32G installed. > > If I boot the same kernel with GRUB64 efi instead of syslinux > then amount of RAM available to linux is 32G. >

> Hello, > > I'm booting linux-3.16-686-pae kernel (32-bit) via syslinux.efi 64-bit version. > After boot linux sees only 2.5G of RAM while system has 32G installed. > > If I boot the same kernel with GRUB64 efi instead of syslinux > then amount of RAM available to linux is 32G. > > Is this a bug or I'm missing something? > > syslinux.cfg: > >

2015-11-26 16:39 UTC+01:00, Ady via Syslinux <syslinux at zytor.com>: > >> On Sat, Nov 21, 2015 at 1:04 AM, Andrey Plankin via Syslinux >> <syslinux at zytor.com> wrote: >> > Hello, >> > >> > I'm booting linux-3.16-686-pae kernel (32-bit) via syslinux.efi 64-bit >> > version. >> > After boot linux sees only 2.5G of RAM

> On Mon, Nov 23, 2015 at 3:06 PM, Ady via Syslinux <syslinux at zytor.com> wrote: > > > It saddens (me) > > > C'mon; really? > > As you asked. > > -- > -Gene I appreciate the replies. Hopefully someone might be able to come up with some contribution / answer. The Syslinux code has already received at some point some patches regarding the EFI

It looks like it is more like the issue in bug #26. In the tcpdump I can see the client attempt to RRQ the kernel but the client itself reports "No file found." I am having similiar issues as reported in both bug reports with getting Syslinux 6.02 to work as in syslinux64.efi gets pulled but then the client gets stuck on ldlinux.e64. Can I use http/nfs instead after syslinux64.efi gets pulled? Seems to be a TFTP issue. Thanks for your help. Adam On Wed, Dec 4, 2013 at 7:09 PM, Celelibi <celelibi at gmail.com> wrote: > 2013/12/5, H. Peter Anvin <hpa...

On Mon, Nov 23, 2015 at 3:06 PM, Ady via Syslinux <syslinux at zytor.com> wrote: > It saddens (me) > C'mon; really? As you asked. -- -Gene

Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- 0) If I build syslinux on a system without mingw a (successful) build will end with: ls: cannot access win32/syslinux.exe: No such file or directory ls: cannot access win64/syslinux64.exe: No such file or directory [...] make: [all] Error 2 (ignored) Ie, it ends with an ignored error. That's confusing (and a bit annoying). 1) This simple patch makes this error go away. It is sent as an RFC because: - I don't have mingw installed: I'm not sure whether I brok...

...l is well until I attempt to select a kernel >> (Ubuntu 13.10 vmlinuz.efi). Regardless of where the kernel is located, >> nested in a sub-directory of /tftpboot or not, the client always responds >> with "File not found." It is odd since all other support files >> (syslinux64.efi, pxelinux.cfg/default, vesamenu.c32, and so forth) have no >> issue. > > What exact kernel? This almost sounds familiar to some errors I've > seen in the last two months. What do you observe in the packet > capture? > I believe this is exactly the TFTP port number...

Hello, I'm booting linux-3.16-686-pae kernel (32-bit) via syslinux.efi 64-bit version. After boot linux sees only 2.5G of RAM while system has 32G installed. If I boot the same kernel with GRUB64 efi instead of syslinux then amount of RAM available to linux is 32G. Is this a bug or I'm missing something? syslinux.cfg: label live-686-pae menu label Linux (686-pae) menu

> On Sat, Nov 21, 2015 at 1:04 AM, Andrey Plankin via Syslinux > <syslinux at zytor.com> wrote: > > Hello, > > > > I'm booting linux-3.16-686-pae kernel (32-bit) via syslinux.efi 64-bit version. > > After boot linux sees only 2.5G of RAM while system has 32G installed. > > Why not use a 64-bit kernel with such a large machine? > > Do you have

...n the TFTP logs and over tcpdump. All is well until I attempt to select a kernel (Ubuntu 13.10 vmlinuz.efi). Regardless of where the kernel is located, nested in a sub-directory of /tftpboot or not, the client always responds with "File not found." It is odd since all other support files (syslinux64.efi, pxelinux.cfg/default, vesamenu.c32, and so forth) have no issue. Any guidance or assistance is greatly appreciated. Adam

...te: On Sat, Oct 6, 2018 at 7:48 AM Thomas Lurmeau via Syslinux wrote: > I have a little question about the last edition of Syslinux ! > Where is the syslinux.exe which should be into \syslinux-6.03\win64 ? under the bios/ binary folder. Handling 3 complete builds did this. see bios/win64/syslinux64.exe > Maybe should i compile it but i don't know how to do it on Windows operating system.. I can't say I've seen any attempt to get a build running on Windows. -- -Gene

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

...inux/Testing/6.04/syslinux-6.04-pre1.zip [pxe-server]$ unzip syslinux-6.04-pre1.zip [pxe-server]$ cd efi64/ [pxe-server]$ cp com32/elflink/ldlinux/ldlinux.e* com32/lib/libcom32.* com32/libutil/libutil.c32 com32/menu/vesamenu.c32 /var/lib/tftpboot/ [pxe-server]$ cp efi/syslinux.efi /var/lib/tftpboot/syslinux64.efi [pxe-server]$ mkdir /var/lib/tftpboot/pxelinux.cfg *Create a file named '/var/lib/tftpboot/pxelinux.cfg/default', copy contents from below - adjust IPs accordingly. ##Repo server setup *Install CentOS 7.4 *Set static IP (192.168.1.10) [repo-server]$ yum install httpd -y [repo-server]$...

Does anyone know how to install the gptmbr.bin onto a USB drive with Windows? I noticed that it would be really easy to modify the source of the installer to install gptmbr.bin instead of mbr.bin with the -m flag, but I'd like a solution that doesn't require me to maintain my own custom syslinux. I'm open to writing and submitting a patch to add a new flag (say -g) to install

...For our current purpose, this partition should be formatted as FAT32. You should be seeing the content of the Clonezilla zip archive expanded in your USB drive. Assuming that Windows Explorer sees this partition as "d:", that means, for example: d:\syslinux\syslinux.cfg d:\utils\win32\syslinux64.exe With the exception of the specific drive letter ("d:"), the above paths should be "exact". If you see something like: d:\clonezilla-live-2.2.1-22-amd64\syslinux\syslinux.cfg then that's not good for our purpose and you would need to correct it (and the rest of the Clo...

...anybody else who desires to conduct further tests. > @Ronald, I have to admit I am a little bit frustrated. Are you really abandoning the tests? Your last email mentions several different procedures you tried, but not the one I suggested after extracting Clonezilla: d: cd d:\utils\win32\ syslinux64.exe --mbr --active --directory /syslinux/ --install d: By the time I am writing this, the issue about the "LBA" flag has already been answered by others. Unfortunately, I wasn't available so to answer you before. It would had saved them some time. Just for generic information, the...