search for: lslabel

...s is > only one of them. I'm trying to make it as simple as possible for > troubleshooting (IMHO). > > > The (initial, for now) content of "target/EFI/BOOT/SYSLX64.CFG": > > ### EFI/BOOT/SYSLX64.CFG start ### > > UI SYSLINUX/EFI64/vesamenu.c32 > DEFAULT lslabel > PROMPT 1 > TIMEOUT 100 > SAY *** Press enter to boot the default label *** > > LABEL lslabel > COM32 SYSLINUX/EFI64/ls.c32 > > LABEL pwdlabel > COM32 SYSLINUX/EFI64/pwd.c32 > > LABEL mylabel > LINUX /linux > INITRD /initrd.gz > > ### EFI/BOOT/SYSLX64....

...e menu and > > report the results for each. If, instead, the boot menu does not show > > up, we need to know the details / results too. > > > > A minor detail (that might be relevant for your report): we are > > defining a TIMEOUT of 10.0 seconds. When you select "lslabel", the > > result should show up on screen during those 10.0 seconds (unless you > > press 'enter', or some other key, before that time), and then the boot > > menu should show up again. The same goes for "pwdlabel". So, if you > > want to take note of...

On Fri, Nov 30, 2018 at 9:56 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > @Carl, > > I have a proposal for you here (in the Syslinux mailing list): let's > first find out _what_ exactly is required in order to boot in UEFI > mode, and then you can take the info downstream. Whether "downstream" > means your own personal customized boot.img, or

...e several ways to achieve the main goal; this is only one of them. I'm trying to make it as simple as possible for troubleshooting (IMHO). The (initial, for now) content of "target/EFI/BOOT/SYSLX64.CFG": ### EFI/BOOT/SYSLX64.CFG start ### UI SYSLINUX/EFI64/vesamenu.c32 DEFAULT lslabel PROMPT 1 TIMEOUT 100 SAY *** Press enter to boot the default label *** LABEL lslabel COM32 SYSLINUX/EFI64/ls.c32 LABEL pwdlabel COM32 SYSLINUX/EFI64/pwd.c32 LABEL mylabel LINUX /linux INITRD /initrd.gz ### EFI/BOOT/SYSLX64.CFG end ### * Save / close any relevant opened files and unmount the...

...report the results for each. If, instead, the boot menu does not show > > > up, we need to know the details / results too. > > > > > > A minor detail (that might be relevant for your report): we are > > > defining a TIMEOUT of 10.0 seconds. When you select "lslabel", the > > > result should show up on screen during those 10.0 seconds (unless you > > > press 'enter', or some other key, before that time), and then the boot > > > menu should show up again. The same goes for "pwdlabel". So, if you > > > w...

...we have an active ("uncommented") UI directive, # then the PROMPT directive makes no diff. # This command is here anyway, in purpose. PROMPT 1 # Let's try to clear the screen when we load the menu MENU CLEAR LABEL vesamenulabel COM32 vesamenu.c32 LABEL pwdlabel COM32 pwd.c32 LABEL lslabel COM32 ls.c32 LABEL catlabel COM32 cat.c32 APPEND /EFI/BOOT/SYSLX64.CFG # To be tested from the boot prompt, using a different label LABEL vesamenulabel2 COM32 vesamenu.c32 APPEND SYSLX64.CFG ### EFI/BOOT/SYSLX64.CFG end ### The result might not be a nice, readable screen, but it should not ha...

...T directive makes no diff. > # This command is here anyway, in purpose. > PROMPT 1 > > # Let's try to clear the screen when we load the menu > MENU CLEAR > > LABEL vesamenulabel > COM32 vesamenu.c32 > > LABEL pwdlabel > COM32 pwd.c32 /EFI/BOOT/ > > LABEL lslabel > COM32 ls.c32 > [dir] . LDLINUX.E64 libcom32.c32 menu.c32 boot: BOOTX64.EFI cat.c32 ls.c32l.c32 pwd.c32 > LABEL catlabel > COM32 cat.c32 > APPEND /EFI/BOOT/SYSLX64.CFG > (dumps this file to the screen) > # To be...

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:

...mplemented in the code (yet), but the most important part to answer to beginners is: because you don't want to have to re-write the current configuration files (and documentation, and explain how older forum posts, blogs and emails would not be relevant anymore, and...). For example: LABEL lslabel COM32 ls.c32 works for every firmware's architecture supported. It wouldn't work for "anyone and everyone" if we were to change the file name extensions according to each architecture, and each time you would want to change from BIOS to EFI* (or from EFI32 to EFI64) you would...

...derstand what's going > on here. > # The CWD is not the root of the booting fs (not "/"). # e.g. the CWD is "/boot/syslinux/". # PATH some/dir/other/than/the/CWD # Note that the PATH directive is intentionally # using a path expressed in relative notation. # LABEL lslabel # Note that the label is different than the name of the c32 file. # COM32 ls.c32 # The ls.c32 file should _not_ be present in the initial CWD. # The ls.c32 file should indeed be present as: # "/some/dir/other/than/the/CWD/ls.c32" # # Note that I am referring now to the absolute path, #...

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

...> > PROMPT 1 > > > > # Let's try to clear the screen when we load the menu > > MENU CLEAR > > > > LABEL vesamenulabel > > COM32 vesamenu.c32 > > > > LABEL pwdlabel > > COM32 pwd.c32 > > /EFI/BOOT/ > > > > > LABEL lslabel > > COM32 ls.c32 > > > > [dir] . LDLINUX.E64 libcom32.c32 menu.c32 > boot: BOOTX64.EFI cat.c32 ls.c32l.c32 pwd.c32 > > > > LABEL catlabel > > COM32 cat.c32 > > APPEND /EFI/BOOT/SYSLX64.CFG &...

On Fri, 02 Jan, at 02:23:48AM, Ady wrote: > > Hmm, I thought it was decided to consider the colon (":") character as > deprecated, and instead we should be using a space character as > separator for the PATH directive (or multiple lines). Well, at least as > for the current MASTER HEAD, Syslinux 6.03. Are you referring to commit 1945579 ("PATH: use a linked

...clear the screen when we load the menu > > > MENU CLEAR > > > > > > LABEL vesamenulabel > > > COM32 vesamenu.c32 > > > > > > LABEL pwdlabel > > > COM32 pwd.c32 > > > > /EFI/BOOT/ > > > > > > > > LABEL lslabel > > > COM32 ls.c32 > > > > > > > [dir] . LDLINUX.E64 libcom32.c32 menu.c32 > > boot: BOOTX64.EFI cat.c32 ls.c32l.c32 pwd.c32 > > > > > > > LABEL catlabel > > > COM32 cat.c3...

> On Sat, 20 Dec, at 12:48:18AM, Ady wrote: > > > > So, my first (still incomplete and still inaccurate) attempt to write > > some rules about the PATH directive, and ask about remaining doubts!... > > > > > > The search (for c32 files) is supposed to respect the following rules: > > > > 1_ The search for c32 files is performed according to