search for: syslx64

...cusing on the specific linux > kernel you eventually would like to boot nor on the whole Debian menu; > in these next steps (and in the next test), we are focusing on > vesamenu.c32 and our current directory tree. > > * You need to create a new file: > > _ "target/EFI/BOOT/SYSLX64.CFG" > > Please note: "SYSLX64.CFG" is supported since Syslinux 6.04-pre1. Older > versions do not support this configuration file name. > > Please note: There are several ways to achieve the main goal; this is > only one of them. I'm trying to make it as simple...

...; 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: > > "PATH EFI/BOOT/SYSLINUX/EFI64/" > > in > > "target/EFI/BOOT/SYSLX64.CFG". > > It is not perfect, but at least it should show the boot menu in UEFI > mode, and not hang immediately. > > Could you please confirm? It did show the boot menu, I can use the arrow keys to navigate the menu, I can select the installer and it runs If I select "Help...

...> ??? BOOT > > ??? BOOTX64.EFI > > ??? LDLINUX.E64 > > ??? SYSLINUX > > ? ??? EFI64 > > ? ??? libcom32.c32 > > ? ??? libutil.c32 > > ? ??? vesamenu.c32 > > ??? SYSLX64.CFG > > > > > > # EFI/BOOT/SYSLX64.CFG > > PATH /EFI/BOOT/SYSLINUX/EFI64/ > > default vesamenu.c32 > > label help > > menu label ^Help > > config prompt.cfg > > > > # /boot/syslinux/syslinux.cfg > > PATH /boot/syslinux/ >...

Hello, i would like create a bootdisk , that can be boot from Old BIOS, EFI32 and EFI64. But for EFI Boot there is only one directory /EFI/BOOT/ In this directory I can copy BOOTia32.EFI and BOOTx64.EFI. But the *.c32 files for EFI32 & EFI64 , I can install to this directory at the same time. Is there a way to load the *.c32 from different directory ? Or is there a other solution ?

...uot; 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: "PATH EFI/BOOT/SYSLINUX/EFI64/" in "target/EFI/BOOT/SYSLX64.CFG". It is not perfect, but at least it should show the boot menu in UEFI mode, and not hang immediately. Could you please confirm? Regarding the "prompt.cfg" you are now trying to investigate (which is not the one in boot.img), the following is (potentially) the first in a s...

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

...), 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: > > > > "PATH EFI/BOOT/SYSLINUX/EFI64/" > > > > in > > > > "target/EFI/BOOT/SYSLX64.CFG". > > > > It is not perfect, but at least it should show the boot menu in UEFI > > mode, and not hang immediately. > > > > Could you please confirm? > > It did show the boot menu, > I can use the arrow keys to navigate the menu, > I can select the...

...the result of pwd.c32 by executing it from CLI first (before going into the menu). For testing purposes, and starting from the cfg file I sent you in the floppy image, you could also add between 20 and 28 "blank" lines (at least when using the default screen resolution) to the end of SYSLX64.CFG. Now imagine you have the screen full of garbage. When using this cfg file, press [ESC] twice, then '[CTRL]+[L]' and then ("blindly") type in the command 'catl' (which is equivalent to 'cat.c32 SYSLX64.CFG' in the cfg I sent you). The content of the cfg file...

On Fri, Dec 7, 2018 at 11:16 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > If this is the best we can do, I'm ok with that. > > It's _not_ the best we can do. The question is... what exactly is this > "we"? We have both made some contributions to my little goal. you certainly share in the credit. > > After some testing (which I

...with this setup, _without_ focusing on the specific linux kernel you eventually would like to boot nor on the whole Debian menu; in these next steps (and in the next test), we are focusing on vesamenu.c32 and our current directory tree. * You need to create a new file: _ "target/EFI/BOOT/SYSLX64.CFG" Please note: "SYSLX64.CFG" is supported since Syslinux 6.04-pre1. Older versions do not support this configuration file name. Please note: There are several ways to achieve the main goal; this is only one of them. I'm trying to make it as simple as possible for troubles...

...;target/EFI/BOOT/SYSLINUX/EFI64/*.c32'. > > Optionally, from the 'efi32' subdirectory for Syslinux files, copy: > _ vesamenu.c32 > _ libcom32.c32 > _ libutil.c32 > > to 'target/EFI/BOOT/SYSLINUX/EFI32/*.c32'. > > > 13_ Create 'target/EFI/BOOT/SYSLX64.CFG'. > > Optionally, create 'target/EFI/BOOT/SYSLIA32.CFG'. > > > 14_ Content of 'target/EFI/BOOT/SYSLX64.CFG': > > # D-I config version 2.0 > # search path for the c32 support libraries (libcom32, libutil etc.) > PATH SYSLINUX/EFI64/ > DEFAULT deb...

...; easier. > > I had the impression from the first or second message you send that > you already had a recipe. > > http://www.syslinux.org/wiki/index.php?title=Install#UEFI is a start. > > An additional config will be warranted. In the root of the file > system, a file named syslx64.cfg with > > #BEGIN syslx64.cfg > PATH boot/syslinux/x64 > INCLUDE common.cfg > #END syslx64.cfg > > > For COM32 modules, you'll need at least (vesa)menu.c32, lua.c32, > mboot.c32, and all of the libraries they depend on (though everything > is easier) from within...

...t; > least "working" when you used the workaround for the buggy PATH > > > directive when booting in UEFI mode? I mean: > > > > > > "PATH EFI/BOOT/SYSLINUX/EFI64/" > > > > > > in > > > > > > "target/EFI/BOOT/SYSLX64.CFG". > > > > > > It is not perfect, but at least it should show the boot menu in UEFI > > > mode, and not hang immediately. > > > > > > Could you please confirm? > > > > It did show the boot menu, > > I can use the arrow keys to n...

...screen problems and similar issues, at least for now, according to your own emails). In short: 1_ Re-read my email from 2018Dec05: www.syslinux.org/archives/2018-December/026247.html where I posted step-by-step instructions. 2_ Amendment to those instructions: 2.1_ In 'target/EFI/BOOT/SYSLX64.CFG', patch: - PATH SYSLINUX/EFI64/ + PATH EFI/BOOT/SYSLINUX/EFI64/ 2.2_ In 'target/EFI/BOOT/SYSLIA32.CFG' (which is part of the "optional"steps in the aforementioned email), patch: - PATH SYSLINUX/EFI32/ + PATH EFI/BOOT/SYSLINUX/EFI32/ 2.3_ In 'target/boot/syslinux/s...

...executing it from CLI first > (before going into the menu). > > For testing purposes, and starting from the cfg file I sent you in the > floppy image, you could also add between 20 and 28 "blank" lines (at > least when using the default screen resolution) to the end of > SYSLX64.CFG. Now imagine you have the screen full of garbage. When > using this cfg file, press [ESC] twice, then '[CTRL]+[L]' and then > ("blindly") type in the command 'catl' (which is equivalent to 'cat.c32 > SYSLX64.CFG' in the cfg I sent you). The content of...

...wouldn't keep cluttering the screen > when I was trying to take notes. > > at the boot: prompt, hit tab, enter the 3 ... > > boot: > lslabel pwdlabel mylabel > boot: lslabel > [dir] [dir] SYSLINUX LDLINUX.E64 > [dir] . BOOTX64.EFI SYSLX64.CFG > boot: pwdlabel > /EFI/BOOT/ > boot: mylabel > (linux boots) These are _not_ bad news. The two c32 modules that don't need additional module libraries are working correctly (i.e. they execute with no errors, and the result is what we expected). Since vesamenu.c32 requir...

...w, according to your own emails). > > In short: > > 1_ Re-read my email from 2018Dec05: > > www.syslinux.org/archives/2018-December/026247.html > > where I posted step-by-step instructions. > > 2_ Amendment to those instructions: > > 2.1_ In 'target/EFI/BOOT/SYSLX64.CFG', patch: > > - PATH SYSLINUX/EFI64/ > + PATH EFI/BOOT/SYSLINUX/EFI64/ > > 2.2_ In 'target/EFI/BOOT/SYSLIA32.CFG' (which is part of the > "optional"steps in the aforementioned email), patch: > > - PATH SYSLINUX/EFI32/ > + PATH EFI/BOOT/SYSLINUX/EF...

...c32 ? ??? libutil.c32 ? ??? syslinux.cfg ? ??? vesamenu.c32 ??? EFI ??? BOOT ??? BOOTX64.EFI ??? LDLINUX.E64 ??? SYSLINUX ? ??? EFI64 ? ??? libcom32.c32 ? ??? libutil.c32 ? ??? vesamenu.c32 ??? SYSLX64.CFG # EFI/BOOT/SYSLX64.CFG PATH /EFI/BOOT/SYSLINUX/EFI64/ default vesamenu.c32 label help menu label ^Help config prompt.cfg # /boot/syslinux/syslinux.cfg PATH /boot/syslinux/ default vesamenu.c32 label help menu label ^Help config prompt.cfg https://salsa.debian.org/carlfk-gue...

...t; > when I was trying to take notes. > > > > at the boot: prompt, hit tab, enter the 3 ... > > > > boot: > > lslabel pwdlabel mylabel > > boot: lslabel > > [dir] [dir] SYSLINUX LDLINUX.E64 > > [dir] . BOOTX64.EFI SYSLX64.CFG > > boot: pwdlabel > > /EFI/BOOT/ > > boot: mylabel > > (linux boots) > > > These are _not_ bad news. > > The two c32 modules that don't need additional module libraries are > working correctly (i.e. they execute with no errors, and the result is &g...

...ia32.EFI and BOOTx64.EFI. > > But the *.c32 files for EFI32 & EFI64 , I can install to this directory at the > same time. > > Is there a way to load the *.c32 from different directory ? Using Syslinux 6.04-pre1, you can use the PATH directive, together with SYSLIA32.CFG and SYSLX64.CFG. In the following example, the file "SYSLUEFI.CFG" is "in-common" to both UEFI platforms, and each of the other 2 cfg files is parsed by its respective "syslinux.efi" (renamed) only (i.e. depending on the platform you are booting). The respective c32 modules ar...