Re: [edk2] Sanity checking boot paths

2014-02-13 Thread Laszlo Ersek
On 02/12/14 22:49, Bill Paul wrote: > - If I use a version of my loader to create a correctly formatted Boot > variable -- in this case Boot0006 -- and add it to the head of the BootOrder, > it's properly preserved across QEMU instances. > > - If I run the buggy version of the loader and cr

Re: [edk2] Sanity checking boot paths

2014-02-12 Thread Bill Paul
Of all the gin joints in all the towns in all the world, Laszlo Ersek had to walk into mine at 08:31:22 on Wednesday 12 February 2014 and say: > On 02/12/14 01:51, Bill Paul wrote: > > the > > fact that the QEMU/OVMF combo doesn't actually emulate a persistent flash > > device. > > Use > - qemu-

Re: [edk2] Sanity checking boot paths

2014-02-12 Thread Laszlo Ersek
On 02/12/14 01:51, Bill Paul wrote: > the > fact that the QEMU/OVMF combo doesn't actually emulate a persistent flash > device. Use - qemu-1.6+, and - Linux host kernel 3.7+ (for KVM support) *or* TCG, and - a fresh OVMF, and - pass OVMF.fd with the -pflash option instead of the -bios option.

Re: [edk2] Sanity checking boot paths

2014-02-11 Thread Andrew Fish
Bill, The User Interface is not defined in EFI, so it is an implementation detail, so there is not a generic answer to this. In general there are hot keys to enter setup, and hot keys to clear “CMOS” which should also clear the EFI Variables on a modern system. You will need to find the mapp

[edk2] Sanity checking boot paths

2014-02-11 Thread Bill Paul
So, while working on my UEFI OS loader, I managed to brick a couple of machines. I recovered all but one of them so far (sadly that one is my personal tablet -- there may yet be a way to save it but I'm holding off on it until I'm better prepared for the attempt). I want people to be able to se