search for: build_uefi

...t, we might need to perform some minor adjustments. > IOW, if your next test fails, don't worry and report the results as > accurately as possible. > report: using this code: https://salsa.debian.org/debconf-video-team/ansible/blob/05480062710486be6b5f5501f560ce3552e87c99/usbinst/uefi/build_uefi.sh Undef symbol FAIL: memset everything else is the same as before: http://imgr.sytes.net/a/qemu4.png target ??? EFI ? ??? BOOT ? ??? BOOTX64.EFI ? ??? LDLINUX.E64 ? ??? SYSLINUX ? ? ??? EFI64 ? ? ??? cat.c32 ? ? ??? chain.c32 ? ? ?...

...ice > ide-hd,drive=thumb,bootindex=1 > > http://imgr.sytes.net/a/qemu5.png Are we actually dealing with ipxe too in all these tests? > report: > using this code: > https://salsa.debian.org/debconf-video-team/ansible/blob/05480062710486be6b5f5501f560ce3552e87c99/usbinst/uefi/build_uefi.sh > > Undef symbol FAIL: memset Our "third test" was about adding the PATH directive. For some reason, the binary files you are using seem to have some building problem or some kind of corruption. I wonder whether your other device in your qemu line "-drive file=disk....

.../EFI/BOOT good news: linux boots. bad news: selecting the Help option locks it up - menu is still there and keys don't move highlight or anything. cpu here is the relevant bits of https://salsa.debian.org/debconf-video-team/ansible/blob/61b833ad1a010c4f046ea9d1d8c81679e97671e9/usbinst/uefi/build_uefi.sh + cp /usr/lib/SYSLINUX.EFI/efi64/syslinux.efi target/EFI/BOOT/BOOTX64.EFI + cp /usr/lib/syslinux/modules/efi64/ldlinux.e64 target/EFI/BOOT/LDLINUX.E64 + cp \ /usr/lib/syslinux/modules/efi64/vesamenu.c32 \ /usr/lib/syslinux/modules/efi64/libcom32.c32 \ /usr/lib/syslinux/modules/efi64/libutil.c32...

On Sat, Dec 1, 2018 at 2:46 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > it works. (boots into the d-i installer, I don't care if the installer > > is missing stuff, booting it is all we care about here. > > > OK, so let's add complexity (but not the whole thing, not yet). > > We already have: > > target > ??? EFI > ? ???

...re we actually dealing with ipxe too in all these tests? > Hmm? we are dealing with whatever QEMU uses for a boot manager. > > > report: > > using this code: > > https://salsa.debian.org/debconf-video-team/ansible/blob/05480062710486be6b5f5501f560ce3552e87c99/usbinst/uefi/build_uefi.sh > > > > Undef symbol FAIL: memset > > > Our "third test" was about adding the PATH directive. For some reason, > the binary files you are using seem to have some building problem or > some kind of corruption. > > I wonder whether your other device in yo...

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?) > > > >

...ote it is not "INITRD initrd.gz", # we use absolute paths here too. ### EFI/BOOT/SYSLINUX.CFG end ### the version of my code is here for anyone that wants to get a clean copy: https://salsa.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'...

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