(you know we used to run entire operating systems in 512Kb ;) Bumping the
RAM up to 1GB produced no change.
Ok, I see gEfiMdePkgTokenSpaceGuid.PcdDebugPrintErrorLevel in the .dsc and
have added the VERBOSE, SNI Driver, and Boot Manager flags. (also no
change)
I looked at your qemu command line - you ran without any network at all. I
can do that as well with the *prebuilt* OVMF.fd (without the network
stack). I however need to use a uEFI image with the network stack
installed. I have never seen a precompiled OVMF.fd with network support in
the wild - is there a lisencing issue with NIC drivers?
And it seems I am unable to build an OVMF.fd with *or without* the uefi
network stack (using VS2008 or GCC44) that does not hang with a blank
screen. This is likely the crux of the matter here - I can't reproduce
building the OVMF.fd at all.
To summarize, I build with:
> build -p OvmfPkg\OvmfPkgX64.dsc
(which compiles correctly on both VS2008 and GCC44 since I have the
Intel3.5 e1000 drivers installed in my workspaces), and run with:
$ qemu-system-x86_64 -m 1024 -hda ovmf.disk -monitor stdio -debugcon
file:debug.log
(where bios.bin is symlinked to OVMF.fd) this hangs with a blank screen and
no debug messages.
I'm at edk2 revision 14204
Do you know where I can get an OVMF.fd with a network stack?
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-devel
