boot problems::slow boot and plymouth theme
Hi everyone. I just installed fedora.25 Mate spin. Facing too much problems ever with fedora installation. buring boot plymouth theme is not appearing, i tried installing new plymouth theme and regenerated gurb.cfg but no help.
Also boot takes good 5 mins. I tried systemd-analyze to get following:
systemd-analyze blame
9.397s systemd-journal-flush.service
7.920s dev-mapper-fedora\x2droot.device
7.679s systemd-udev-settle.service
7.507s firewalld.service
5.734s lvm2-monitor.service
5.099s accounts-daemon.service
3.860s abrtd.service
3.107s ModemManager.service
2.025s upower.service
1.806s bluetooth.service
1.449s gssproxy.service
1.322s chronyd.service
1.228s polkit.service
1.202s proc-fs-nfsd.mount
1.156s abrt-ccpp.service
1.054s systemd-rfkill.service
1.032s rsyslog.service
979ms udisks2.service
910ms systemd-tmpfiles-setup-dev.service
879ms fedora-readonly.service
765ms avahi-daemon.service
725ms NetworkManager.service
665ms systemd-udevd.service
lines 1-23...skipping...
9.397s systemd-journal-flush.service
7.920s dev-mapper-fedora\x2droot.device
7.679s systemd-udev-settle.service
7.507s firewalld.service
5.734s lvm2-monitor.service
5.099s accounts-daemon.service
3.860s abrtd.service
3.107s ModemManager.service
2.025s upower.service
1.806s bluetooth.service
1.449s gssproxy.service
1.322s chronyd.service
1.228s polkit.service
1.202s proc-fs-nfsd.mount
1.156s abrt-ccpp.service
1.054s systemd-rfkill.service
1.032s rsyslog.service
979ms udisks2.service
910ms systemd-tmpfiles-setup-dev.service
879ms fedora-readonly.service
765ms avahi-daemon.service
725ms NetworkManager.service
665ms systemd-udevd.service
664ms cups.service
629ms lvm2-pvscan@8:6.service
587ms systemd-tmpfiles-setup.service
557ms auditd.service
551ms lightdm.service
498ms systemd-udev-trigger.service
458ms systemd-logind.service
450ms fedora-import-state.service
432ms systemd-journald.service
423ms dmraid-activation.service
386ms dev-hugepages.mount
340ms dev-mapper-fedora\x2dswap.swap
340ms systemd-sysctl.service
331ms dev-mqueue.mount
293ms nfs-config.service
274ms user@1000.service
207ms rtkit-daemon.service
205ms systemd-fsck-root.service
200ms systemd-vconsole-setup.service
187ms wpa_supplicant.service
183ms livesys.service
176ms plymouth-quit-wait.service
174ms plymouth-read-write.service
173ms systemd-backlight@backlight:radeon_bl0.service
171ms rpc-statd-notify.service
137ms blk-availability.service
137ms systemd-user-sessions.service
109ms kmod-static-nodes.service
104ms dracut-shutdown.service
103ms plymouth-quit.service
96ms systemd-random-seed.service
93ms systemd-remount-fs.service
89ms home.mount
62ms sys-kernel-debug.mount
40ms systemd-update-utmp.service
23ms plymouth-start.service
20ms livesys-late.service
17ms systemd-update-utmp-runlevel.service
12ms sys-fs-fuse-connections.mount
11ms var-lib-nfs-rpc_pipefs.mount
9ms tmp.mount
5ms sys-kernel-config.mount
lines 22-65/65 (END)
What should i do to improve boot time?
Please help.
Your situation is much worse than mine. I was just wandering why firewalld.service use 10 seconds to start. My boot time is 48 seconds. But I wish to reduce it.