search for: qemu5

...lly we'll > > get there at some point. If you can, please comment out the > > BIOS-related stuff in your script for now. > > removed all that. We'll come back to that later, when we combine UEFI with BIOS in the same boot.img. > > > http://imgr.sytes.net/a/qemu5.png > > > > > > Are we actually dealing with ipxe too in all these tests? > > > > Hmm? > > we are dealing with whatever QEMU uses for a boot manager. Your qemu5.png shows ipxe too (my guess is that the boot order is set to try ipxe first, and if it fails t...

...img > > mkfs.fat 4.1 (2017-01-24) > > + syslinux -i boot.img > > + qemu-system-x86_64 -m 512 -drive file=disk.cow,index=0 -drive > > file=boot.img,index=1,format=raw,if=none,id=thumb -device > > ide-hd,drive=thumb,bootindex=1 > > > > http://imgr.sytes.net/a/qemu5.png > > > Are 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/05480062710486be6b5f5501f560ce355...

...point. If you can, please comment out the > > > BIOS-related stuff in your script for now. > > > > removed all that. > > > We'll come back to that later, when we combine UEFI with BIOS in the > same boot.img. > > > > > > http://imgr.sytes.net/a/qemu5.png > > > > > > > > > Are we actually dealing with ipxe too in all these tests? > > > > > > > Hmm? > > > > we are dealing with whatever QEMU uses for a boot manager. > > > Your qemu5.png shows ipxe too (my guess is that the boot o...

...05 MB, 100 MiB) copied, 0.999141 s, 105 MB/s + /sbin/mkfs.msdos boot.img mkfs.fat 4.1 (2017-01-24) + syslinux -i boot.img + qemu-system-x86_64 -m 512 -drive file=disk.cow,index=0 -drive file=boot.img,index=1,format=raw,if=none,id=thumb -device ide-hd,drive=thumb,bootindex=1 http://imgr.sytes.net/a/qemu5.png > > BEWARE: > We are about to use the PATH directive. This PATH directive has > several issues, inconveniences, shortcomings, and bugs. Hence, the next > test _might_ "fail" to show the boot menu. According to (or depending > on) your next report, we might need to...

...MB/s > + /sbin/mkfs.msdos boot.img > mkfs.fat 4.1 (2017-01-24) > + syslinux -i boot.img > + qemu-system-x86_64 -m 512 -drive file=disk.cow,index=0 -drive > file=boot.img,index=1,format=raw,if=none,id=thumb -device > 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&quot...

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