similar to: move firmware-specific code into a directory

2015-09-20 14:21 UTC+02:00, Patrick Masotta via Syslinux <syslinux at zytor.com>: >>>> > > This is related to bug #37. > > http://bugzilla.syslinux.org/show_bug.cgi?id=37 > > > > Actually, I think this raises a more general issue about the source > > code organization. Most of the code of syslinux has been developped in > > a time where

On Sat, Sep 19, 2015 at 4:32 PM, BALATON Zoltan <balaton at eik.bme.hu> wrote: > On Fri, 18 Sep 2015, Gene Cumm via Syslinux wrote: >> >> On Sep 18, 2015 7:07 AM, "Ady via Syslinux" <syslinux at zytor.com> wrote: >> >>> I doubt there has been any update to pxechn.c32 for UEFI support. Maybe >>> Gene can confirm. >> >>

> To port a .c32 module to EFI requires a few steps: > > 1) The .c32 module must have access to the gnu-efi environment; I have posted a > patch some time ago that does exactly that (I really can't find it, surely Ady will help). > > 2) based on makefile variables it is very easy to define within the .c32 source code > "BIOS only sections" and "EFI only

>>> > This is related to bug #37. > http://bugzilla.syslinux.org/show_bug.cgi?id=37 > > Actually, I think this raises a more general issue about the source > code organization. Most of the code of syslinux has been developped in > a time where only BIOSes were supported. And now, there is no real > separation between generic code and BIOS-only code (while UEFI

On 12/04/2013 02:58 PM, Gene Cumm wrote: > On Wed, Dec 4, 2013 at 12:02 PM, Adam Sawyer <acsawyer at gmail.com> wrote: >> All, >> >> I have scoured the mailing list and the web and I can't seem to find any >> help on this issue. I am attempting to have EFI machines boot over PXE and >> then load various Linux Live distributions. I have a similar setup

Hi Folks , Can you please let me know if there is any fix for chain loading UEFI boot loader using chain.c32 in 6.04 release ? I am booting my system with syslinux.efi and want to chain load to windows or sex specific boot loader in the second stage . Thanks Robin

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 also all under the root of the partition (except BOOTIA32.EFI and BOOTX64.EFI) and work fine

On Sep 18, 2015 7:07 AM, "Ady via Syslinux" <syslinux at zytor.com> wrote: > I doubt there has been any update to pxechn.c32 for UEFI support. Maybe > Gene can confirm. No. pxechn.c32 is BIOS only for now. --Gene

On February 3, 2016 7:17:37 AM PST, Celelibi <celelibi at gmail.com> wrote: >2016-02-02 18:50 UTC+01:00, poma via Syslinux <syslinux at zytor.com>: >> On 30.01.2016 16:59, poma wrote: >>> ... >>> >>> https://sourceware.org/bugzilla/show_bug.cgi?id=19538 >>> >>> >> >> Mister Anvin, >> care to share what's the

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

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

works with legacy, hangs with efi. where works is: No DEFAULT or UI configuration directive found! but enter and ^v make things happen hangs is: nothing happens, no response from keyboard, have to reboot. note: config prompt.cfg prompt.cfg does not exist, but I would expect similar behaviour between efi and legacy. test is: starting with blank image, mkfs, mount it... + cp

On Thu, Dec 6, 2018 at 10:00 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > First, I'm confused. In the prior "whole" setup (the one you generated > after my 15 steps, plus one workaround), was/is the basic boot menu at > least "working" when you used the workaround for the buggy PATH > directive when booting in UEFI mode? I mean: > >

On Thu, Dec 6, 2018 at 5:14 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > works with legacy, hangs with efi. > > > > where works is: > > No DEFAULT or UI configuration directive found! > > but enter and ^v make things happen > > > > hangs is: nothing happens, no response from keyboard, have to reboot. > > > > note:

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. In this case I am booting an vmware esxi installer. /EFI/boot on the vmware ISO has the files?BOOTX64.EFI and?BOOTIA32.EFI that can be used on the usb. But these always go directly to boot.cfg,

On Thu, Nov 15, 2018 at 1:10 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > Here are some comments and questions for you. > Thanks. I've have my scripts to a better state, including installing/using qemu to uefi and legacy boot the usb stick for testing. It mostly works for me, but the "wget a tarball of binaries" step isn't going to sit well with

On Tue, Sep 24, 2013 at 11:57 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Sun, Sep 22, 2013 at 3:09 PM, Celelibi <celelibi at gmail.com> wrote: >> And (a bit out of scope) if I get my old kernel to boot in EFI mode, >> will the driver efivars have access to the EFI variables? Or does the >> kernel need to be recompiled specially for EFI? > > Doubtful.

Trying to set up UEFI Syslinux boot on an ArchLinux USB 4GB stick. - Host system: 64-bit Ubuntu 14.10 on 56 GB hard drive - Hardware: ASUS P8H77-I, Bios v1101, i7-3770 at 3.40 GHz, 16 GB DDR3 - ArchLinux Instructions followed: https://wiki.archlinux.org/index.php/Syslinux#UEFI_Systems > ? ? 2. UEFI Systems > 2.2 Installation - Arch syslinux v.6.03 196352 Oct 13 22:25 /usr/sbin/syslinux

We currently are running legacy pxe, in Centos 5.8 I am trying to develop a Dual mode (Legacy and uEFI) with Centos 6.7. I have be able to successfully PXE boot the legacy pxelinux and am having some Progress on the uEFI. Where I need help is the layout of the uEFI default file and proper use of the chain.c32. Been doing quite a bit of googling, but the uEFI pxe stuff is sparse. Any references

Hi, ________________________________________ From: Gene Cumm <gene.cumm at gmail.com> Sent: Wednesday, March 16, 2016 00:56 To: Jan Frode J?ger Cc: syslinux at zytor.com Subject: Re: [syslinux] Updated status on UEFI compliant version of the pxechn-module On Tue, Mar 15, 2016 at 9:32 AM, Jan Frode J?ger <jan.frode.jaeger at ntnu.no> wrote: Without trying to figure out where data is