On 9/9/21 7:37 AM, Gerd Hoffmann wrote:
i
Hi,
4) The driver is not in final image.
5) The dependency is not satisfied.
The entry point currently has an endless loop in it, thus should stop edk2,
but it doesn't.
Cases (4) + (5) should be easy to figure by checking the log.
ovmf logs every driver loaded, and it also logs drivers loaded but not
initialized (which can be a dependency problem).
(the log is written to the qemu debug console, so try "qemu -chardev
stdio,id=fw.log -device isa-debugcon,iobase=0x402,chardev=fm.log").
Thanks. It was a missing entry in the .fdf file...
Stefan
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#80446): https://edk2.groups.io/g/devel/message/80446
Mute This Topic: https://groups.io/mt/85316773/21656
Group Owner: devel+ow...@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
