How would a “normal” user know that the logon screen is called plymouth?
Anyways my problem is that on my 4k tv the logon dialog is way to small. The installation of Fedora 42 failed to set the proper variables. How to set the logon screen (plymouth) to a readable size?
In relation to the screen size it may seem small.
My 4k TV is a 65 inch so the entries are very readable for logging in.
On a 27 inch HD monitor those seem extremely large to me.
I can understand the extremely small button and passwd entry box for log on if it were a 35 or 42 inch screen. For me there is only the one button to select the user then the password entry box. The user name is automatically selected when first booting so it only requires the enter key to bring up the password entry then typing the password in the box.
I don’t know how to change sizes for the initial login, but you can use scaling for the sizes after getting the desktop displayed.
Plymouth is what shows you an animation during boot. The graphical login screen is called gdm on (Gnome) Workstation and sddm on KDE, respectively (at least by default, can be changed).
Again, not Plymouth. Assuming that you are using Gnome and gdm (on KDE you can just copy the current display settings to the login screen in the settings application), you can start a shell as the user ‘gdm’ and then use gsettings to modify some things:
machinectl shell gdm@ /bin/bash
gsettings set org.gnome.desktop.interface scaling-factor 2
Instead of scaling everything, I have also had good results by scaling just the text (which shows up as an enabled accessibility feature) when I was still using Gnome. This is particularly useful if you require a non-integer scaling factor but don’t want to activate fractional scaling of the framebuffer:
gsettings set org.gnome.desktop.interface text-scaling-factor 1.5
It is highly unlikely that a change to the GDM configuration (which was the topic of this thread) affects your BIOS time. I suggest you start a new thread.
This could be a result of the plymouth.force-scale=X kernel parameter change that @yuntaz suggested in post 3. But that is also just a guess.
Item #6 was your original issue, but you never said if changing the GDM configuration improved that. I am not sure if this is a new issue that you want people to look at or still the original one.
Your boot experience is not the one that I and probably most others here have. And since you describe this as a new behavior, I assume that this was caused by some change you made. I can only recommend you start a new thread and see if people can figure out what has caused this.
Or, to be kind of blunt, looking at all your other threads and the issues you are having, it might be a good idea to start fresh and get the system into a clean, unmodified state instead of trying to reconstruct everything that has happened to it since its first installation.