Comment # 1 on bug 1224404 from Antonio Feijoo

(In reply to Fabian Vogt from comment #0)
> +++ 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.

Thanks for finding this. It took me some time to reproduce it, because using
Leap as host the boot hangs forever (I don't know since when, I have an old vm
with snapshot 20231122 and it works), but I could reproduce it with Tumbleweed.

FTR:

> qemu-system-aarch64 -M virt -cpu cortex-a72 -m 2048 -serial stdio -device virtio-gpu-pci -device qemu-xhci -device usb-kbd -bios /usr/share/qemu/aavmf-aarch64-code.bin -drive if=none,file=$PWD/MicroOS.aarch64-16.0.0-kvm-and-xen-sdboot-Snapshot20240517.qcow2,id=hd0 -device virtio-blk-device,drive=hd0

(In reply to Fabian Vogt from comment #0)
> 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?

I would expand this requirement to when a dracut module needs
systemd-ask-password, not only to the crypt module.

But, there is a problem with the second part. Nowadays, current upstream admins
do not like to pull things based on which kernel modules are loaded on the
running systemd. See:
- https://github.com/dracutdevs/dracut/pull/2412#discussion_r1239313722
- https://github.com/dracut-ng/dracut-ng/issues/236