Bug 1705676 - edk2 doesn't always enabled the graphical display on arm/aarch64
Summary: edk2 doesn't always enabled the graphical display on arm/aarch64
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: oz
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Chris Lalancette
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ARMTracker
TreeView+ depends on / blocked
 
Reported: 2019-05-02 18:10 UTC by Peter Robinson
Modified: 2020-10-23 22:03 UTC (History)
11 users (show)

Fixed In Version: oz-0.17.0-12.fc32 oz-0.17.0-12.fc33
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-13 20:34:29 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Fix oz to append console= so both serial and graphics work (1.50 KB, application/mbox)
2020-09-23 21:54 UTC, Jeremy Linton
no flags Details

Description Peter Robinson 2019-05-02 18:10:25 UTC
There doesn't seem to be any regulatly repeatable, sometimes it works and sometimes it doesn't, when run with the same cmd line but sometimes the graphical display isn't enabled by tianocore and you get the following error on the graphical console:

"Guest has not initialised the display (yet)"

It would be useful to have it consistently enabled and usable.

Comment 1 Peter Robinson 2019-05-02 18:11:10 UTC
edk2-aarch64-20190308stable-1.fc29.noarch
edk2-arm-20190308stable-1.fc29.noarch
edk2-ovmf-20190308stable-1.fc29.noarch

Comment 2 Jeremy Linton 2019-07-02 17:16:02 UTC
I must have forgotten to click save when I wrote this a couple weeks ago: Basically I was having problems too until I switched the graphics to pci-virtio graphics+spice+usb keyboard in virt-manager. Using the following qemu command line seems to work consistently with F30 for me:

/usr/bin/qemu-system-aarch64 -name guest=fedora30 -machine virt-3.1,accel=kvm,gic-version=3 -cpu host -m 2048  -smp 1,sockets=1,cores=1,threads=1 
-drive file=/usr/share/edk2/aarch64/QEMU_EFI-pflash.raw,if=pflash,format=raw 
-drive file=/var/lib/libvirt/qemu/nvram/fedora30_VARS.fd,if=pflash,format=raw  
-device qemu-xhci 
-device virtio-gpu-pci 
-drive file=/var/lib/libvirt/images/fedora30.qcow2
-device usb-kbd  
-display gtk


This is with:

[root@mammon-tx2 jlinton]# rpm -qa |grep edk2
edk2-aarch64-20190308stable-1.fc30.noarch
edk2-ovmf-20190308stable-1.fc30.noarch


Maybe the default fedora/aarch64 profile could use the addition of a graphics console?

Comment 3 Jeremy Linton 2019-07-02 17:26:03 UTC
Moved back to a f29 machine, a setup a gicv2 config via virt-manager. That generates a qemu command with `-machine virt-3.0,accel=kvm,usb=off,dump-guest-core=off,gic-version=2 -cpu host` and that seems fine too as does a similar TCG config emulating aarch64 on x86.

Comment 4 Jeremy Linton 2019-07-02 19:28:46 UTC
In the case of OZ this seems to be more a problem with the default ACPI config telling the kernel that the default console is ttyAMA0. Rather if 

<kernelparam>console=tty0</kernelparam>

is placed in the .tdl file, the console is switched back to the graphical head. My tweaks to explicitly ask for a virtio console via libvirt apparently aren't needed (the flashing tianocore logo, blurb about an empty DTB and then a blank screen happen either way).

Comment 5 Ben Cotton 2019-08-13 16:59:54 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.

Comment 6 Ben Cotton 2019-08-13 19:07:11 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.

Comment 7 Philippe Mathieu-Daudé 2019-08-14 09:33:15 UTC
This seems related/similar to bz 1661288.

Comment 8 Adam Williamson 2020-03-04 22:12:42 UTC
FWIW, to get this working reliably in openQA, we:

* Use `-device virtio-gpu-pci` for graphics
* Add `console=tty0` to the kernel boot args (this is to deal with #1661288)

Peter, are you still having issues with this if you do those?

Comment 9 Jeremy Linton 2020-09-23 21:54:14 UTC
Created attachment 1716151 [details]
Fix oz to append console= so both serial and graphics work

Before it gets lost, here is another oz patch to fix this problem for aarch64. At the moment the armv7 seems to be working/etc. 

So, that said, the default boot console remains serial, so if the machine dies between the efi stub exiting boot services, and the kernel switching the console back to framebuffer its possible that wont be visible in screen captures. That could be fixed by changing the default edk2 console, but AFAIK, there is some weirdness with some edk2 console patches (AFAIK Pete Batard has an open patch for some edk2 non-compliance issues in this area).

Comment 10 Peter Robinson 2020-10-03 16:08:33 UTC
Should be fixed with oz-0.17.0-10

Comment 11 Fedora Update System 2020-10-03 16:19:34 UTC
FEDORA-2020-59009c173d has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-59009c173d

Comment 12 Fedora Update System 2020-10-04 01:50:17 UTC
FEDORA-2020-59009c173d has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-59009c173d`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-59009c173d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 13 Fedora Update System 2020-10-04 02:16:05 UTC
FEDORA-2020-8334add35c has been pushed to the Fedora 33 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-8334add35c`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-8334add35c

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 14 Fedora Update System 2020-10-04 14:23:46 UTC
FEDORA-2020-8334add35c has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-8334add35c

Comment 15 Fedora Update System 2020-10-04 14:24:09 UTC
FEDORA-2020-59009c173d has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-59009c173d

Comment 16 Fedora Update System 2020-10-05 01:14:06 UTC
FEDORA-2020-8334add35c has been pushed to the Fedora 33 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-8334add35c`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-8334add35c

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 17 Fedora Update System 2020-10-05 01:50:52 UTC
FEDORA-2020-59009c173d has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-59009c173d`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-59009c173d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 18 Fedora Update System 2020-10-05 22:13:38 UTC
FEDORA-2020-59009c173d has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-59009c173d

Comment 19 Fedora Update System 2020-10-05 22:13:51 UTC
FEDORA-2020-8334add35c has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-8334add35c

Comment 20 Fedora Update System 2020-10-06 01:14:44 UTC
FEDORA-2020-8334add35c has been pushed to the Fedora 33 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-8334add35c`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-8334add35c

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 21 Fedora Update System 2020-10-06 01:25:11 UTC
FEDORA-2020-59009c173d has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-59009c173d`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-59009c173d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 22 Fedora Update System 2020-10-13 20:34:29 UTC
FEDORA-2020-59009c173d has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 23 Fedora Update System 2020-10-23 22:03:07 UTC
FEDORA-2020-8334add35c has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.