$ sudo systemctl status plymouth-start.service
● plymouth-start.service - Show Plymouth Boot Screen
Loaded: loaded (/usr/lib/systemd/system/plymouth-start.service; static)
Active: active (exited) since Wed 2021-09-01 21:44:22 CEST; 19h ago
Main PID: 483 (code=exited, status=0/SUCCESS)
Sep 01 21:44:22 fedora systemd: Starting Show Plymouth Boot Screen...
Sep 01 21:44:22 fedora systemd: Started Show Plymouth Boot Screen.
$ sudo systemctl enable plymouth-start.service
The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
instance name specified.
I have run the dracut thing, there is no output. Let’s see at next boot