search for: uefix64

...vative distros customizing the set of cfg files (which they do, and that's the reason for having so many cfg files in Debian instead of just one), then you should not leave the filename "syslinux.cfg" in the root of the filesystem when introducing other Syslinux platforms (such as UEFIx64). You could, but you shouldn't. Since you are supposed to use "boot/syslinux/syslinux.cfg" instead, there should be no problem even when not using additional platforms. So, in fact there is no reason to leave the name "syslinux.cfg" in the root directory. > The hel...

...g problem, but they also include several improvements. Lukas might be able to help with the error message you are getting, although, I'm still not %100 convinced that the problem is in the build / source code (it might, but I have other "suspects" too). I might prepare some "UEFIx64 floppy image" for you to boot with qemu in UEFIx64 mode, "as-is" (i.e. as raw floppy image, no network booting first, no hard disk attached, just boot the floppy in UEFIx64 mode). Would you be able to perform such test if I prepare such floppy image? Regards, Ady.

On Sun, Dec 2, 2018 at 9:29 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > > _ target/EFI/BOOT/SYSLINUX.CFG > > > > I don't think that exists? (see list below) > > > In our "first test" (simple boot prompt), we created > "target/EFI/BOOT/SYSLINUX.CFG". In our "second test" we _added_ >

...gt; customizing the set of cfg files (which they do, and that's the reason > for having so many cfg files in Debian instead of just one), then you > should not leave the filename "syslinux.cfg" in the root of the > filesystem when introducing other Syslinux platforms (such as UEFIx64). > You could, but you shouldn't. > > Since you are supposed to use "boot/syslinux/syslinux.cfg" instead, > there should be no problem even when not using additional platforms. > So, in fact there is no reason to leave the name "syslinux.cfg" in the > root...

@Carl, I'll repeat what I said in my prior email: you don't have to keep looking, we already achieved what you want (considering that you are willing to "disregard" the 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

...> include several improvements. Lukas might be able to help with the > error message you are getting, although, I'm still not %100 convinced > that the problem is in the build / source code (it might, but I have > other "suspects" too). > > I might prepare some "UEFIx64 floppy image" for you to boot with qemu > in UEFIx64 mode, "as-is" (i.e. as raw floppy image, no network booting > first, no hard disk attached, just boot the floppy in UEFIx64 mode). > Would you be able to perform such test if I prepare such floppy image? sure - I have a f...

...ing, out of the USB device. In particular, please avoid having "/syslinux.cfg" in (the root of) your USB device at this time. I know, I know... We don't have a boot menu yet. Patience :). For a boot menu, and only when the above configuration actually boots your kernel+initrd in UEFIx64 mode, we will add some additional Syslinux files from the 'efi64' subdirectory and we'll edit "/media/sdc/EFI/BOOT/SYSLINUX.CFG" accordingly. Could you please confirm that the above setup actually works? If it fails in any way, we need to know that too. If this setup wor...

On Sat, Nov 17, 2018 at 1:54 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > On Thu, Nov 15, 2018 at 1:10 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > > > Here are some comments and questions for you. > > > > > > > Thanks. > > > > I've have my scripts to a better state, including

...lsa.debian.org/debconf-video-team/ansible/blob/e6e02369fad365cbed90f10b8df888fcda87783d/usbinst/uefi/build_uefi.sh > > I know, I know... We don't have a boot menu yet. Patience :). > > For a boot menu, and only when the above configuration actually boots > your kernel+initrd in UEFIx64 mode, we will add some additional > Syslinux files from the 'efi64' subdirectory and we'll edit > "/media/sdc/EFI/BOOT/SYSLINUX.CFG" accordingly. > > Could you please confirm that the above setup actually works? If it > fails in > any way, we need to know tha...