plymouth-quit-wait.service로 인해 Fedora 24의 시작 속도가 느려짐

저는 지금 약 2주 동안 Fedora 24를 사용해왔는데, 한 가지 불편한 점은진짜시작 시간이 더 깁니다. 나는 이 문제를 조사 systemd-analyze하려고 노력했는데 systemd-analyze blame시작하는 데 꽤 오랜 시간이 걸리는 일부 서비스가 있는 것 같습니다 plymouth-quit-wait.service. 대부분은 Linux를 처음 접했기 때문에 해당 서비스가 실제 원인인지 아니면 알 수 없습니다. 그것은 기다려야 할 또 다른 일입니다. 이것이 관련이 있는지는 모르겠지만 i5-2540M CPU가 장착된 Lenovo Thinkpad X220에서 워크스테이션 버전의 Fedora 24를 사용하고 있습니다. 이 질문에 systemd-analyze, systemd-analyze blame및 의 출력을 첨부 하겠습니다 .systemd-analyze critical chain

systemd-analyze
Startup finished in 2.546s (kernel) + 4.697s (initrd) + 1min 33.630s (userspace) = 1min 40.874s


systemd-analyze blame
     49.647s plymouth-quit-wait.service
     28.356s dnf-makecache.service
     13.163s systemd-journal-flush.service
     12.147s firewalld.service
     11.119s systemd-udev-settle.service
      9.478s dev-mapper-fedora\x2droot.device
      7.549s libvirtd.service
      5.923s udisks2.service
      5.694s abrtd.service
      5.658s accounts-daemon.service
      5.312s chronyd.service
      4.585s polkit.service
      3.809s lvm2-pvscan@8:2.service
      3.594s unbound-anchor.service
      2.736s ModemManager.service
      2.430s proc-fs-nfsd.mount
      2.367s lvm2-monitor.service
      2.287s cups.service
      2.283s dmraid-activation.service
      2.121s systemd-rfkill.service
      2.053s plymouth-start.service
      2.033s systemd-logind.service
      2.014s gssproxy.service
      1.873s systemd-tmpfiles-setup-dev.service
      1.830s packagekit.service
      1.803s rtkit-daemon.service
      1.794s NetworkManager.service
      1.792s avahi-daemon.service
      1.700s systemd-udevd.service
      1.678s bluetooth.service
      1.423s fedora-readonly.service
      1.367s systemd-backlight@backlight:intel_backlight.service
      1.161s abrt-ccpp.service
      1.095s wpa_supplicant.service
       972ms gdm.service
       798ms systemd-journald.service
       795ms dev-mqueue.mount
       790ms upower.service
       738ms systemd-random-seed.service
       734ms [email protected]
       695ms systemd-fsck@dev-disk-by\x2duuid-bc0eb656\x2d624f\x2d4c3d\x2d90a3\x2d321abc24867b.service
       694ms systemd-fsck@dev-mapper-fedora\x2dhome.service
       684ms auditd.service
       656ms tmp.mount
       621ms sys-kernel-debug.mount
       521ms systemd-sysctl.service
       479ms fedora-import-state.service
       438ms rpc-statd-notify.service
       395ms systemd-tmpfiles-setup.service
       364ms iio-sensor-proxy.service
       356ms dev-hugepages.mount
       319ms home.mount
       299ms systemd-fsck-root.service
       280ms dracut-shutdown.service
       254ms systemd-user-sessions.service
       232ms boot.mount
       230ms plymouth-read-write.service
       226ms systemd-remount-fs.service
       222ms colord.service
       163ms systemd-udev-trigger.service
       149ms kmod-static-nodes.service
       136ms systemd-tmpfiles-clean.service
       132ms nfs-config.service
        89ms [email protected]
        87ms blk-availability.service
        76ms dev-mapper-fedora\x2dswap.swap
        73ms systemd-vconsole-setup.service
        70ms systemd-update-utmp.service
        28ms livesys.service
        15ms livesys-late.service
         9ms var-lib-nfs-rpc_pipefs.mount
         6ms systemd-update-utmp-runlevel.service
         5ms sys-fs-fuse-connections.mount
         2ms sys-kernel-config.mount

systemd-analyze critical chain
graphical.target @1min 33.616s
└─multi-user.target @1min 33.616s
  └─libvirtd.service @37.051s +7.549s
    └─remote-fs.target @36.969s
      └─remote-fs-pre.target @36.969s
        └─iscsi-shutdown.service @36.965s
          └─network.target @36.933s
           └─wpa_supplicant.service @39.880s +1.095s
            └─dbus.service @21.045s
             └─basic.target @20.963s
              └─sockets.target @20.963s
                └─dbus.socket @20.963s
                  └─sysinit.target @20.911s
                    └─sys-fs-fuse-connections.mount @1min 32.526s +5ms
                      └─system.slice
                        └─-.slice