I surely will try this out, but what about device 4/0/0 showing the
same issue. Both tests where performed separately showing the exact
same result, of course I'd be happy if either one of them worked.
I think what is happening here is that Windows is enabling legacy
interrupts on the device
I can confirm the new firmware does fix the issue for us. Thanks for
the quick resolution. It at least allowed me to script a proper
workaround for our automated tests.It turns out my previous
vm-bhyve workaround was a bad idea, and broke installs. I would
assume vm-bhyve copies the iso to n
On Sat, Mar 24, 2018 at 12:59 AM, Peter Grehan wrote:
> Hi Kyle,
>
>> FYI- I've created PR #2 [1] against the freebsd/uefi-edk2 repository
>> and have confirmed that this fixes the broken-looking firmware along
>> with the booting problem experienced in this thread.
>>
>> [1] https://github.com/fr
