search for: pwdlabel

...get/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 image (or the > fs of your testing device). mkdir -p $target/EFI/BOOT $target/EFI/BO...

...g 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 the results of each entry and you hadn't have > > enough time, then, while in the boot prompt, simply press the "left > > arrow" (or "cursor") key once and then the "right arrow" key once, or > > ch...

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

...hooting (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 image (or the fs of your testing device). When booting in UEFI x64 mode in your next test, you should see a boot menu. I'd...

...this case with vesamenu.c32 I would suggest a very simple cfg with 2 or 3 entries (not just one entry, as the behavior would be slightly different) as first step. For example: *** syslinux.cfg start *** # Note that labels are not using the same name as actual files, in purpose. DEFAULT pwdlabel LABEL pwdlabel COM32 pwd.c32 LABEL lslablel COM32 ls.c32 *** syslinux.cfg end *** 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. Note that all the Sysli...

...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 the results of each entry and you hadn't have > > > enough time, then, while in the boot prompt, simply press the "left > > > arrow" (or "cursor") key once and then the "right arrow" key once,...

...d DEFAULT vesamenulabel # If 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...

> If I may... If I were to say something like "Syslinux doesn't boot", I > would mean that I cannot even get to a simple Syslinux's "boot:" > prompt. In other words, I would mean that _Syslinux_ (in one of its > variants / family members) is failing to boot. Whether the problem is > in Syslinux itself or in some other area (HW, FW, user error, >

...ot;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 /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...

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:

...e 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 > > /EFI/BOOT/ > > > > > LABEL lslabel > > COM32 ls.c32 > > > > [dir] . LDLINUX.E64 libcom32.c32 menu.c32 > boot: BOOTX64.EFI cat.c32 ls.c32l.c32 pwd.c32 > > &gt...

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