search for: setpkg

> > You are probably imitating / following some procedure used by > > Slackware to create EFI-compatible ISO images. The problem, as > > mentioned in a recent email this last week, is the particularities of > > the documents regarding, in this case, grub2 as EFI bootloader (as > > oppose to documents covering EFI bootloaders in general and clearly > >

.... But meanwhile, is there some other thing I can do, like moving the kernel elsewhere in the image? Currently the tree is: . |-- EFI | `-- BOOT | |-- bootx64.efi | |-- bzImage | |-- f2.txt | |-- initrd.img | |-- ldlinux.c32 | |-- ldlinux.e64 | |-- ldlinux.sys | |-- memtest | |-- message.txt | |-- setpkg | |-- syslinux.cfg | `-- ter-i16v.psf |-- README_SLINT.TXT `-- SLINT_DATE TIA and best regards, Didier

...ttp://www.linuxquestions.org/questions/slackware-14/%5Bann%5D-syslinux-6-03-has-been-released-4175521209/ Here is the tree: . |-- EFI | `-- BOOT | |-- bootx64.efi | |-- bzImage | |-- f2.txt | |-- initrd.img | |-- ldlinux.c32 | |-- ldlinux.e64 | |-- ldlinux.sys | |-- memtest | |-- message.txt | |-- setpkg | |-- syslinux.cfg | `-- ter-i16v.psf |-- README_SLINT.TXT `-- SLINT_DATE Best regards, Didier

On 10/11/2014 04:02, Ady wrote: > >> Hi there, >> >> I failed to boot an installer in a VMware player (Version6.0.3 >> build-1895310) >> using syslinux 6.03, be it off an hybrid ISO image and an USB stick. >> >> Booting succeeds if the VM is set to use a BIOS firmware with both media, >> but fails using an efi firmware. >>

...dlinux.e64 | |-- message.txt | |-- syslinux.cfg | `-- ter-i16v.psf |-- README_SLINT.TXT |-- SLINT_DATE |-- isolinux | |-- efiboot.img | |-- f2.txt | |-- initrd.img | |-- isolinux.bin | |-- isolinux.boot | |-- isolinux.cfg | |-- ldlinux.c32 | |-- message.txt | |-- setpkg | `-- ter-i16v.psf `-- kernels |-- VERSIONS.TXT |-- huge.s | |-- System.map.gz | |-- bzImage | `-- config |-- memtest | |-- README | `-- memtest `-- speakup.s `-- README.TXT 7 directories, 27 files Here is the beginning of /EFI/BOOT/syslinux...