https://bugzilla.redhat.com/show_bug.cgi?id=1405539
--- Comment #53 from Hans de Goede <hdegoede(a)redhat.com> ---
(In reply to Michael Catanzaro from comment #52)
Hans, any update here?
Not really I'm afraid. This is on my radar / todo list: From my local TODO
file:
-What do I want to do in the F33 cycle?:
-1. Get rid of things bringing in udev-setttle
-2. Get rid of downstream patches for show boot menu stuff
-3. Prioritized bugs:
-3.1 plymouth diskunlock dialog kbd layout thing
Note that this is the 3th item, so depending on how the other 2 items go I
might not get around to it, or at least not in time for F33. There also is all
the usual hw-enablement work / hw related regression fixes which I spend a lot
of time on, the above list is done next to that...
I've had some discussions about this on the upstream systemd-devel list. One of
the problems here is fixing this in a way which works for both silverblue and
traditional Fedora.
ATM the plan roughly is like this:
1. Put a copy of vconsole.conf in /boot (and keep that in sync)
2. Make grub dynamically generate an extra initramfs containing the
vconsole.conf copy from /boot and use that
as an overlay to the standard initramfs
This will fix the issue discussed here; while allowing silverblue to keep using
a pre generated initramfs for the main initramfs. An other option would be
playing tricks with the kernel commandline but that is not really a nice way to
deal with this.
--
You are receiving this mail because:
You are on the CC list for the bug.