You may be affected by the simpledrm issue.
See Arch wiki chapter 4.8
https://wiki.archlinux.org/title/Plymouth
And the linked bugreport
I just appended plymouth.use-simpledrm, but nothing changed. Even the plymouth debug log is the same as before.
just curious, perhaps we do a hardware check? See if it really is related to lower end systems?
just your CPU and GPU should be enough info i believe…
I just reset my cmos battery, because of frustration and it actually solved all my other problems except plymouth.
bird@localhost ~> sudo journalctl -b | grep plymouth (base)
Nov 23 22:29:18 localhost systemd[1]: /usr/lib/systemd/system/plymouth-start.service:15: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
Nov 23 22:29:19 localhost plymouthd[601]: 00:00:01.804 ../src/main.c:2036:check_logging : checking if console messages should be redirected and logged
Nov 23 22:29:19 localhost plymouthd[601]: 00:00:01.804 ../src/main.c:2048:check_logging : logging will be enabled!
Nov 23 22:29:19 localhost plymouthd[601]: 00:00:01.804 ../src/main.c:2122:initialize_environment : source built on Nov 15 2024
Nov 23 22:29:19 localhost systemd[1]: Dispatch Password Requests to Console Directory Watch was skipped because of an unmet condition check (ConditionPathExists=!/run/plymouth/pid).
Nov 23 22:29:51 localhost systemd-coredump[802]: Process 601 (plymouthd) of user 0 terminated abnormally with signal 11/SEGV, processing...
Nov 23 22:29:52 localhost systemd[1]: plymouth-start.service: Main process exited, code=dumped, status=11/SEGV
Nov 23 22:29:52 localhost systemd[1]: plymouth-start.service: Failed with result 'core-dump'.
Nov 23 21:29:52 localhost systemd[1]: plymouth-switch-root.service: Deactivated successfully.
Nov 23 21:29:52 localhost plymouthd[1102]: 00:00:35.138 ../src/main.c:2036:check_logging : checking if console messages should be redirected and logged
Nov 23 21:29:52 localhost plymouthd[1102]: 00:00:35.138 ../src/main.c:2048:check_logging : logging will be enabled!
Nov 23 21:29:52 localhost plymouthd[1102]: 00:00:35.138 ../src/main.c:2122:initialize_environment : source built on Nov 15 2024
bird@localhost ~> (base)
bird@localhost ~> sudo systemctl status plymouth-start.service (base)
● plymouth-start.service - Show Plymouth Boot Screen
Loaded: loaded (/usr/lib/systemd/system/plymouth-start.service; static)
Active: active (exited) since Sat 2024-11-23 21:29:54 CET; 2min 15s ago
Invocation: 90c1b2b373e14960b26706cb58515c26
Process: 1098 ExecStart=/usr/sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session (code=exited, status=0/SUCCESS)
Process: 1104 ExecStartPost=/usr/bin/plymouth show-splash (code=exited, status=0/SUCCESS)
Main PID: 1102 (code=exited, status=0/SUCCESS)
CPU: 155ms
Nov 23 21:29:52 localhost systemd[1]: Starting Show Plymouth Boot Screen...
Nov 23 21:29:52 localhost plymouthd[1102]: 00:00:35.138 ../src/main.c:2036:check_logging : checking if console messages should be redirected and log>
Nov 23 21:29:52 localhost plymouthd[1102]: 00:00:35.138 ../src/main.c:2048:check_logging : logging will be enabled!
Nov 23 21:29:52 localhost plymouthd[1102]: 00:00:35.138 ../src/main.c:2122:initialize_environment : source built on Nov 15 2024
Nov 23 21:29:54 localhost systemd[1]: Started Show Plymouth Boot Screen.
bird@localhost ~>
Also I changed the .service killmode, but it didn’t seem to resolve the killmode=none warning.
[Unit]
Description=Show Plymouth Boot Screen
DefaultDependencies=no
Wants=systemd-ask-password-plymouth.path systemd-vconsole-setup.service
After=systemd-vconsole-setup.service systemd-udev-trigger.service systemd-udevd.service
Before=systemd-ask-password-plymouth.service
ConditionKernelCommandLine=!plymouth.enable=0
ConditionVirtualization=!container
[Service]
ExecStart=/usr/sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session
ExecStartPost=-/usr/bin/plymouth show-splash
Type=forking
RemainAfterExit=yes
KillMode=mixed
SendSIGKILL=no
this is on a legacy boot mode system (i forgot to enable UEFI during installation)
usr_40476@localhost:~> cat /usr/lib/systemd/system/plymouth-switch-root.service
[Unit]
Description=Plymouth switch root service
DefaultDependencies=no
ConditionPathExists=/etc/initrd-release
Before=initrd-switch-root.service
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=-/usr/bin/plymouth update-root-fs --new-root-dir=/sysroot
StandardInput=null
StandardOutput=null
StandardError=null
usr_40476@localhost:~>
The killmode is only an informational message.
The issue on your system is that plymouth dumps core. The core dump creates a 32 seconds delay on your box.
Here the output from one of my machines where plymouth works without issues and does not delay the boot as there is no core dump.
ich@rennsemmel:~> sudo journalctl -b | grep plymouth
[sudo] Passwort für root:
Nov 23 21:46:40 rennsemmel systemd[1]: /usr/lib/systemd/system/plymouth-start.service:15: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
Nov 23 21:46:40 rennsemmel plymouthd[557]: 00:00:01.297 ../src/main.c:2036:check_logging : checking if console messages should be redirected and logged
Nov 23 21:46:40 rennsemmel plymouthd[557]: 00:00:01.297 ../src/main.c:2048:check_logging : logging will be enabled!
Nov 23 21:46:40 rennsemmel plymouthd[557]: 00:00:01.297 ../src/main.c:2122:initialize_environment : source built on Nov 15 2024
Nov 23 21:46:40 rennsemmel systemd[1]: Dispatch Password Requests to Console Directory Watch was skipped because of an unmet condition check (ConditionPathExists=!/run/plymouth/pid).
Nov 23 21:46:43 rennsemmel systemd[1]: /usr/lib/systemd/system/plymouth-start.service:15: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
Nov 23 21:46:43 rennsemmel systemd[1]: plymouth-start.service: Deactivated successfully.
Nov 23 21:46:43 rennsemmel systemd[1]: plymouth-start.service: Unit process 557 (plymouthd) remains running after unit stopped.
Nov 23 21:46:43 rennsemmel systemd[1]: Dispatch Password Requests to Console Directory Watch was skipped because of an unmet condition check (ConditionPathExists=!/run/plymouth/pid).
Nov 23 21:46:43 rennsemmel systemd[1]: plymouth-switch-root.service: Deactivated successfully.
Nov 23 21:46:43 rennsemmel systemd[1]: plymouth-start.service: Found left-over process 557 (plymouthd) in control group while starting unit. Ignoring.
Nov 23 21:46:43 rennsemmel systemd[1]: plymouth-start.service: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Nov 23 21:46:43 rennsemmel plymouthd[1189]: 00:00:04.736 ../src/main.c:2036:check_logging : checking if console messages should be redirected and logged
Nov 23 21:46:43 rennsemmel plymouthd[1189]: 00:00:04.736 ../src/main.c:2048:check_logging : logging will be enabled!
Nov 23 21:46:43 rennsemmel plymouthd[1189]: 00:00:04.736 ../src/main.c:2122:initialize_environment : source built on Nov 15 2024
Nov 23 21:46:43 rennsemmel systemd[1]: Dispatch Password Requests to Console Directory Watch was skipped because of an unmet condition check (ConditionPathExists=!/run/plymouth/pid).
ich@rennsemmel:~> 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 Sat 2024-11-23 21:46:43 CET; 6min ago
Invocation: b6cc2e92e32d429ba8e623dd9bac5e40
Process: 1183 ExecStart=/usr/sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session (code=exited, status=0/SUCCESS)
Process: 1191 ExecStartPost=/usr/bin/plymouth show-splash (code=exited, status=0/SUCCESS)
Main PID: 557 (code=exited, status=0/SUCCESS)
CPU: 27ms
Nov 23 21:46:43 rennsemmel plymouthd[1189]: 00:00:04.736 ../src/main.c:2036:check_logging : checking if console messages should be redirected and logged
Nov 23 21:46:43 rennsemmel plymouthd[1189]: 00:00:04.736 ../src/main.c:2048:check_logging : logging will be enabled!
Nov 23 21:46:43 rennsemmel plymouthd[1189]: 00:00:04.736 ../src/main.c:2122:initialize_environment : source built on Nov 15 2024
Nov 23 21:46:43 rennsemmel systemd[1]: Started Show Plymouth Boot Screen.
ich@rennsemmel:~>
Encountered the same bug on my system, removed splash=silent from grub boot menu. Now
26ms plymouth-switch-root.service.
3 Likes
I removed splash=silent works for me as well. With no plymouth boot splash showing.
Now
108ms plymouth-start.service
98ms wpa_supplicant.service
Hi,
The latest tumbleweed snapshot downgraded plymouth. The 30 seconds lag during boot appears to be gone when I test my machine with plymouth enabled.
3 Likes
Tumbleweed snapshot 20241127 fixes the 30~ delay for me as well.
plymouth (22.02.122+180.b1d5aa9 → 22.02.122+94.4bd41a3)
systemd-analyze blame | grep plymouth
154ms plymouth-quit-wait.service
39ms plymouth-read-write.service
23ms plymouth-start.service
19ms plymouth-switch-root.service
1 Like
I can confirm this for the two machines running Tumbleweed here that were affected by the 30-second delay.
1 Like
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.