plymouth (and others) slowing down the boot process
by floppy_stuttgart from LinuxQuestions.org on (#5S26F)
Hello,
Debian11 is starting as multiboot on an HDD.
The PC is connected via LAN to home network and should print. It is used for SSH access and FTP access to other servers and central home router. So, not much.
The boot process times are indicated with a command in the terminal: see below.
For now, I will look at how to move plymouth away.
From the other services, I cannot see what is "nice to have" (perhaps taking WPA_SUPPLICANT away since I boot all the time with LAN cable).
Any recommendation is welcome.
systemd-analyze blame
Code:41.104s plymouth-quit-wait.service
17.363s systemd-journal-flush.service
12.543s ifupdown-pre.service
9.147s udisks2.service
7.947s cups.service
7.058s dev-sda2.device
7.045s fwupd.service
5.897s NetworkManager-wait-online.service
5.265s accounts-daemon.service
4.614s ModemManager.service
3.939s polkit.service
3.899s systemd-fsck@dev-disk-by\x2duuid-ce500d88\x2d3c58\x2d4dca\x2db334\x2dcf>
3.733s avahi-daemon.service
3.732s bluetooth.service
3.727s NetworkManager.service
3.723s switcheroo-control.service
3.718s wpa_supplicant.service
3.717s systemd-logind.service
3.163s teamviewerd.service
2.901s gdm.service
2.483s networking.service
2.043s apparmor.service
1.934s colord.service
1.762s systemd-fsck@dev-disk-by\x2duuid-DD72\x2d265D.service
1.673s systemd-udevd.service
1.623s ssh.service
1.522s mono-xsp4.service
1.270s rsyslog.service
1.197s systemd-tmpfiles-clean.service
1.160s lm-sensors.service
1.150s systemd-rfkill.service
1.135s plymouth-start.service
1.132s e2scrub_reap.service
929ms keyboard-setup.service
902ms packagekit.service
797ms dev-hugepages.mount
795ms dev-mqueue.mount
793ms sys-kernel-debug.mount
791ms sys-kernel-tracing.mount
655ms systemd-modules-load.service
602ms systemd-remount-fs.service
570ms user@1000.service
565ms sys-fs-fuse-connections.mount
564ms sys-kernel-config.mount
519ms binfmt-support.service
461ms systemd-tmpfiles-setup.service
434ms systemd-sysusers.service
426ms home.mount
415ms systemd-random-seed.service
412ms systemd-udev-trigger.service
398ms upower.service
392ms systemd-sysctl.service
378ms boot-efi.mount
362ms dev-disk-by\x2duuid-07b16d3c\x2df568\x2d4419\x2db44b\x2d814cce1ce057.sw>
345ms systemd-tmpfiles-setup-dev.service
209ms alsa-restore.service
200ms kmod-static-nodes.service
198ms modprobe@configfs.service
197ms modprobe@drm.service
195ms modprobe@fuse.service
184ms systemd-journald.service
147ms systemd-timesyncd.service
136ms rtkit-daemon.service
127ms geoclue.service
114ms console-setup.service
106ms systemd-update-utmp.service
91ms systemd-user-sessions.service
63ms hddtemp.service
38ms proc-sys-fs-binfmt_misc.mount
11ms plymouth-read-write.service
7ms user-runtime-dir@1000.service
4ms systemd-update-utmp-runlevel.service
Debian11 is starting as multiboot on an HDD.
The PC is connected via LAN to home network and should print. It is used for SSH access and FTP access to other servers and central home router. So, not much.
The boot process times are indicated with a command in the terminal: see below.
For now, I will look at how to move plymouth away.
From the other services, I cannot see what is "nice to have" (perhaps taking WPA_SUPPLICANT away since I boot all the time with LAN cable).
Any recommendation is welcome.
systemd-analyze blame
Code:41.104s plymouth-quit-wait.service
17.363s systemd-journal-flush.service
12.543s ifupdown-pre.service
9.147s udisks2.service
7.947s cups.service
7.058s dev-sda2.device
7.045s fwupd.service
5.897s NetworkManager-wait-online.service
5.265s accounts-daemon.service
4.614s ModemManager.service
3.939s polkit.service
3.899s systemd-fsck@dev-disk-by\x2duuid-ce500d88\x2d3c58\x2d4dca\x2db334\x2dcf>
3.733s avahi-daemon.service
3.732s bluetooth.service
3.727s NetworkManager.service
3.723s switcheroo-control.service
3.718s wpa_supplicant.service
3.717s systemd-logind.service
3.163s teamviewerd.service
2.901s gdm.service
2.483s networking.service
2.043s apparmor.service
1.934s colord.service
1.762s systemd-fsck@dev-disk-by\x2duuid-DD72\x2d265D.service
1.673s systemd-udevd.service
1.623s ssh.service
1.522s mono-xsp4.service
1.270s rsyslog.service
1.197s systemd-tmpfiles-clean.service
1.160s lm-sensors.service
1.150s systemd-rfkill.service
1.135s plymouth-start.service
1.132s e2scrub_reap.service
929ms keyboard-setup.service
902ms packagekit.service
797ms dev-hugepages.mount
795ms dev-mqueue.mount
793ms sys-kernel-debug.mount
791ms sys-kernel-tracing.mount
655ms systemd-modules-load.service
602ms systemd-remount-fs.service
570ms user@1000.service
565ms sys-fs-fuse-connections.mount
564ms sys-kernel-config.mount
519ms binfmt-support.service
461ms systemd-tmpfiles-setup.service
434ms systemd-sysusers.service
426ms home.mount
415ms systemd-random-seed.service
412ms systemd-udev-trigger.service
398ms upower.service
392ms systemd-sysctl.service
378ms boot-efi.mount
362ms dev-disk-by\x2duuid-07b16d3c\x2df568\x2d4419\x2db44b\x2d814cce1ce057.sw>
345ms systemd-tmpfiles-setup-dev.service
209ms alsa-restore.service
200ms kmod-static-nodes.service
198ms modprobe@configfs.service
197ms modprobe@drm.service
195ms modprobe@fuse.service
184ms systemd-journald.service
147ms systemd-timesyncd.service
136ms rtkit-daemon.service
127ms geoclue.service
114ms console-setup.service
106ms systemd-update-utmp.service
91ms systemd-user-sessions.service
63ms hddtemp.service
38ms proc-sys-fs-binfmt_misc.mount
11ms plymouth-read-write.service
7ms user-runtime-dir@1000.service
4ms systemd-update-utmp-runlevel.service