Syslinux - Jan 2016 - Embedding com32 modules and ldlinux.sys into one file

Hi,

I installed syslinux 6.0.3 on a UEFI/GPT system with Arch Linux.

My /boot/EFI/syslinux/syslinux.cfg contains MENU SAVE but selected entries
aren't saved.
Just after I hit the Enter key in the syslinux menu, I see efi_adv_write:
Unable to open file \ldlinux.sys, this message isn't displayed
when the boot starts after the timeout (default entry).

My installation didn't have this file so I try to add it with extlinux
--install /boot/EFI/syslinux but the problem still there.

Any ideas?
Thank you,

St?phane

On Wed, Jan 6, 2016 at 3:24 PM, St?phane Raimbault <syslinux at zytor.com>
wrote:
> Hi,
>
> I installed syslinux 6.0.3 on a UEFI/GPT system with Arch Linux.
>
> My /boot/EFI/syslinux/syslinux.cfg contains MENU SAVE but selected entries
> aren't saved.
> Just after I hit the Enter key in the syslinux menu, I see efi_adv_write:
> Unable to open file \ldlinux.sys, this message isn't displayed
> when the boot starts after the timeout (default entry).
It shouldn't be attempting ldlinux.sys but rather syslinux.efi though
I'm not sure the ADV is fully functional in EFI
> My installation didn't have this file so I try to add it with extlinux
> --install /boot/EFI/syslinux but the problem still there.
Not necessary and essentially useless.
> Any ideas?
Official version from kernel.org without running make?  I don't know
if there have been changes that'll affect the ADV since 6.03 but you
could try my test binaries.

https://sites.google.com/site/genecsyslinux/sl604p0g22-x64.tgz?attredirects=0&d=1

-- 
-Gene

I copied your binaries to /boot/EFI/syslinux but the problem still there,
so I reinstalled Archlinux with legacy BIOS/MBR and now syslinux saves the
selected entry.

2016-01-06 21:52 GMT+01:00 Gene Cumm <gene.cumm at gmail.com>:
> On Wed, Jan 6, 2016 at 3:24 PM, St?phane Raimbault <syslinux at
zytor.com>
> wrote:
> > Hi,
> >
> > I installed syslinux 6.0.3 on a UEFI/GPT system with Arch Linux.
> >
> > My /boot/EFI/syslinux/syslinux.cfg contains MENU SAVE but selected
> entries
> > aren't saved.
> > Just after I hit the Enter key in the syslinux menu, I see
efi_adv_write:
> > Unable to open file \ldlinux.sys, this message isn't displayed
> > when the boot starts after the timeout (default entry).
>
> It shouldn't be attempting ldlinux.sys but rather syslinux.efi though
> I'm not sure the ADV is fully functional in EFI
>
> > My installation didn't have this file so I try to add it with
extlinux
> > --install /boot/EFI/syslinux but the problem still there.
>
> Not necessary and essentially useless.
>
> > Any ideas?
>
> Official version from kernel.org without running make?  I don't know
> if there have been changes that'll affect the ADV since 6.03 but you
> could try my test binaries.
>
>
>
https://sites.google.com/site/genecsyslinux/sl604p0g22-x64.tgz?attredirects=0&d=1
>
> --
> -Gene
>

On 01/06/16 12:52, Gene Cumm via Syslinux wrote:
> 
> It shouldn't be attempting ldlinux.sys but rather syslinux.efi though
> I'm not sure the ADV is fully functional in EFI
> 
The ADV probably should just be a file in EFI.

	-hpa

Hello There
I'm involved in a project which requires syslinux to be a single file.Is
there a simple way to merge com32 modules and ldlinux.sys into one file?Why does
the bootloader separated into few files (ldlinux.sys, ldlinux.c32, etc.)?
BTW: what is the easiest way to debug syslinux?Is it done by printing or there
are other methods?
Regards,Tal

Good day, Tal.

Perhaps if you describe a little bit more about the rationale behind 
this single-file requirement, someone might be able to make an 
alternative suggestion that you haven't thought of.

The BIOS- and disk-based Syslinux bootstrapping actually often has a 
filesystem-specific piece of code that lives in the filesystem's 
meta-data, as well as the primary file and COMBOOT32 modules that you 
are thinking of.  Because of that first piece, it's not really possible 
to have this kind of Syslinux as a single file.

But if you were to share a few more details, perhaps you're thinking of 
a PXE environment or a CD environment or a new filesystem or...?  Are 
you able to describe the sequence of boot-up events that occur before 
the point you are thinking of?

Yes, you can print debug-output from custom builds.

-- 

Shao Miller
Synthetel Corporation
T: +1.9053927729
W: https://www.synthetel.com