Bug ID 1219180
Summary Missing framebuffer during boot on aarch64
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware Other
URL https://openqa.opensuse.org/tests/3891664/modules/ansible/steps/31
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component Kernel
Assignee kernel-bugs@opensuse.org
Reporter fvogt@suse.com
QA Contact qa-bugs@suse.de
CC tzimmermann@suse.com
Target Milestone ---
Found By openQA
Blocker ---

Unless the initrd is built with the platform native DRM driver (e.g.
virtio_gpu), there is no graphical output during boot. This also means that
entering a passphrase for unlocking the root fs is not possible.

On x86 it uses the EFI framebuffer successfully, but on aarch64 dmesg has no
trace of efifb/simplefb/simpledrm.

## Observation

openQA test in scenario
microos-Tumbleweed-MicroOS-Image-sdboot-aarch64-microos-wizard@aarch64 fails in
[ansible](https://openqa.opensuse.org/tests/3891664/modules/ansible/steps/31)

## Test suite description
Like MicroOS, but use neither combustion nor ignition for the intial
configuration, so jeos-firstboot runs.


## Reproducible

Fails since (at least) Build
[20231129](https://openqa.opensuse.org/tests/3771195)


## Expected result

Last good: [20231127](https://openqa.opensuse.org/tests/3763820) (or more
recent)


## Further details

Always latest result in this scenario:
[latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=microos&flavor=MicroOS-Image-sdboot&machine=aarch64&test=microos-wizard&version=Tumbleweed)


You are receiving this mail because: