+++ This bug was initially created as a clone of Bug #1219180 +++

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.

The original bug report has some more details, but the summary is that efifb or
other builtin drivers don't work with virtio-gpu-pci. To get any display output
at all, the virtio-gpu module is needed. From a dracut PoV, the crypt module
should probably pull in drm if virtio-gpu is detected?

## 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)