On 03/11/13 21:11, Duane Voth wrote:
> I can run OVMF without networking using qemu with no problem, and I have
> qemu with networking (using taps and a bridge) working properly, but
> when I use the network enabled OVMF.fd I get the blank vga console with
> no screen or network activity.  OVFM.fd builds with no errors using:
> 
>> build -D NETWORK_ENABLE -p OvmfPkg\OvmfPkgX64.dsc

Have you installed the Intel drivers for e1000 to the source tree? Do
you specify the e1000 emulated NIC in qemu?

Also, what does the debug console / serial output say? Consider setting
the DEBUG_VERBOSE & other bits in OvmfPkgX64.dsc:

  # DEBUG_INIT     0x00000001 Initialization
  # DEBUG_WARN     0x00000002 Warnings
  # DEBUG_LOAD     0x00000004 Load events
  # DEBUG_FS       0x00000008 EFI File system
  # DEBUG_POOL     0x00000010 Alloc & Free's
  # DEBUG_PAGE     0x00000020 Alloc & Free's
  # DEBUG_INFO     0x00000040 Informational debug messages
  # DEBUG_DISPATCH 0x00000080 PEI/DXE/SMM Dispatchers
  # DEBUG_VARIABLE 0x00000100 Variable
  # DEBUG_BM       0x00000400 Boot Manager
  # DEBUG_BLKIO    0x00001000 BlkIo Driver
  # DEBUG_NET      0x00004000 SNI Driver
  # DEBUG_UNDI     0x00010000 UNDI Driver
  # DEBUG_LOADFILE 0x00020000 UNDI Driver
  # DEBUG_EVENT    0x00080000 Event messages
  # DEBUG_GCD      0x00100000 Global Coherency Database changes
  # DEBUG_CACHE    0x00200000 Memory range cachability changes
  # DEBUG_VERBOSE  0x00400000 Detailed debug messages that may significantly
  #                           impact boot performance
  # DEBUG_ERROR    0x80000000 Error

  gEfiMdePkgTokenSpaceGuid.PcdDebugPrintErrorLevel|0x8040004F

Normally the debug output is set to the debug port; you can capture it
with the "-debugcon file:/tmp/debug.log -global
isa-debugcon.iobase=0x402" qemu command line options.

Alternatively specify -D DEBUG_ON_SERIAL_PORT when building, and capture
the serial port when running.

... I think the most recent thread on this topic was
<http://thread.gmane.org/gmane.comp.bios.tianocore.devel/2252>.

> I copy OVMF.fd to bios.bin, but no OvmfVideo.rom file is created or
> available as suggested by the online sourceforge docs
> (http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=How_to_run_OVMF)
> or the edk2\OvmfPkg\README.txt file, so I'm using the same
> CirrusLogic5446.rom that works with the non-networking OVMF.

I should really post a patch for the README; the video driver is
built-in (in case you don't use the -D CSM_ENABLE build, anyway).

Laszlo

------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester  
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the  
endpoint security space. For insight on selecting the right partner to 
tackle endpoint security challenges, access the full report. 
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-devel

Reply via email to