search for: syslia32

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 ?

...y 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 ? 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 respectiv...

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

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

...uld also look for "syslx64.cfg" in the same location, and only if > "syslx64.cfg" is not found, then it should look for "syslinux.cfg" in > the same location. > > Similarly, syslinux.efi under IA32 looks for ldlinux.e32, so it > should look for "syslia32.cfg" as configuration file in the same > location, and only if "syslia32.cfg" is not found, then it should > look for "syslinux.cfg" in the same location. > > As usual, the searched name should be case-INsensitive. > > The same searched-name order is v...

...d using version 6.04-pre1 or newer of Syslinux. > - if yes - can it be done using syslinux UEFI as already setup? I don't see why not. Moreover, with v.6.04-pre1 the selection between 64/32 bits doesn't need to be manual anymore; syslinux.efi (IA32) should be able to find 'syslia32.cfg', and syslinux.efi (X64) should be able to find 'syslx64.cfg'. > - i looked for available information - what did i miss? There is something that many users seem to confuse: it is not the architecture of the microprocessor (x32 or x64) that defines which syslinux.efi is...

...for ldlinux.e64, it should also look for "syslx64.cfg" in the same location, and only if "syslx64.cfg" is not found, then it should look for "syslinux.cfg" in the same location. Similarly, syslinux.efi under IA32 looks for ldlinux.e32, so it should look for "syslia32.cfg" as configuration file in the same location, and only if "syslia32.cfg" is not found, then it should look for "syslinux.cfg" in the same location. As usual, the searched name should be case-INsensitive. The same searched-name order is valid, independently of the nam...

hi i was creating a boot stick for BIOS years ago, which still is working - of course. need just update kernels. i now need to set up new linux laptops. as i do not want to run into troubles i do intend to create a new stick for UEFI. do not mix BIOS/UEFI on one device. once again nothing fancy. prompt and say will do. was reading all available text about best solution. i so prepared a

...+22,11 @@ int generic_open_config(struct com32_filedata *filedata) > }; > static const char *filenames[] = { > "extlinux.conf", > +#if defined(__FIRMWARE_EFI64__) > + "syslx64.cfg", > +#elif defined(__FIRMWARE_EFI32__) > + "syslia32.cfg", > +#endif > "syslinux.cfg", > NULL > }; >From the thread "[syslinux] syslinux efi configuration file name proposal" at http://www.syslinux.org/archives/2014-October/022712.html -- -Gene

...OOT/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 debian PROMPT 0 LABEL debian CONFIG ../../debian.cfg ../../ Optionally, the content of 'target/EFI/BOOT...

On Mon, Dec 3, 2018 at 10:02 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > Now it is just dd, mkfs and copy in the files we need. > > One less thing to worry about keeping versions consistent. > > > > > > I just noticed those 2 files that were added by > > > > syslinux -i boot.img > > > > (right?) > > > >

...y 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/syslinux.cfg', patch: - PATH ./ + PATH BOOT/SYSLINUX/ 3_ There are additional potential improvements and c...

...om 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 debian > PROMPT 0 > LABEL debian > CONFIG ../../debian.cfg ../....

...39;t boot in such system (and it is not needed, nor intended > for such platform). > BTW, it is possible to use a mix of SYSLINUX (for BIOS) and > syslinux.efi in the same (USB) device, especially with 6.04-pre1 (or > newer), which automatically supports 'syslx64.cfg' and 'syslia32.cfg'. ......... Isn't this the recommended way to go? BTW. this TC isolinux USBstik booter CAN boot a different [Debian7] USBstik when I edit an appropriate *.cfg entry. But I don't think the Laptop's firmware showed the USB-to-IDE\SATA disks. It's all very complex, and disru...

On Wed, Aug 27, 2014 at 2:08 AM, Prof. Dipl.-Ing. Klaus Knopper <syslinux at knopper.net> wrote: > Apparently, the rename of ldlinux.e32 to ldlinux.e64 for the 64bit > variant is already in the mainline git, so the only change left for > automatically chosing a different config file is the tiny patch attached > here, which will > > - prepend syslnx64.cfg to the config file

...minimum. I would expect for your next reply to include something about: "I have now finally read the wiki pages, and I have succeeded building a mixed BIOS+EFI64 booting USB drive". The only thing that is not yet documented is how to use the optional "syslx64.cfg" and "syslia32.cfg" files, simply because there is no official release supporting them yet -- the closest thing at this time would be 6.04-pre1, or building your own binaries from current git head. If you have any doubts, please go to the Syslinux Mailing List Archives and read the entire email thread,...

...es/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/syslinux.cfg', patch: > > - PATH ./ > + PATH BOOT/SYSLINUX/ > > &gt...

Hi Ady, Ady Ady via Syslinux wrote: > > To me, it is not so clear what exactly is your goal. sorry for not being detailed enough. > Do you want to build an image for an internal HDD that could be capable > of booting in both, BIOS mode and UEFI mode? Yes. This would make us independent from the BIOS boot mode. > Or, is this for a portable (USB) device? Maybe - would be nice

> Hello Ady & list, > > On Wed, Aug 27, 2014 at 08:17:51AM +0300, Ady wrote: > > > Hello Ady, > > > > > > On Fri, Aug 01, 2014 at 08:35:27PM +0300, Ady wrote: > > > > Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 > > > > (with an optional Syslinux menu containing multiple entries). > > > > >

On Wed, Dec 12, 2018 at 4:00 PM Carl Karsten <carl at personnelware.com> wrote: > > On Tue, Dec 11, 2018 at 9:19 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > > > > > > > > > You should be able to see the effects of the DISPLAY directive when > > > > testing the floppy image I sent you, because it starts with the