Kubuntu启动耗时过长且重复显示MSI Logo问题排查求助

大家好，我是Linux新手，今天刚装上Kubuntu，现在笔记本启动要花大概10秒，之前用Windows 11的时候只需要1.5秒，想问问有没有办法优化这个启动速度？

另外还有个奇怪的情况，我感觉电脑好像重复启动了好几次？MSI的logo会出现2-3次，之后才会显示Kubuntu的登录界面，这正常吗？

我已经运行了几个systemd相关的命令来排查，结果如下：

首先是systemd-analyze的输出：

anti@anti-msi:~$ systemd-analyze

Startup finished in 2.379s (kernel) + 7.564s (userspace) = 9.943s

graphical.target reached after 7.557s in userspace

然后是systemd-analyze blame的结果：

6.408s NetworkManager-wait-online.service
632ms gpu-manager.service
537ms systemd-logind.service
300ms snapd.service
290ms modprobe@chromeos_pstore.service
239ms dev-nvme0n1p2.device
222ms networkd-dispatcher.service
217ms accounts-daemon.service
201ms upower.service
198ms systemd-resolved.service
186ms bluetooth.service
183ms boot-efi.mount
170ms systemd-udev-trigger.service
156ms power-profiles-daemon.service
134ms dev-loop4.device
133ms e2scrub_reap.service
133ms dev-loop5.device
131ms dev-loop10.device
130ms dev-loop11.device
130ms snapd.apparmor.service
129ms dev-loop9.device
129ms dev-loop7.device
129ms systemd-timesyncd.service
128ms dev-loop0.device
128ms dev-loop8.device
128ms udisks2.service
124ms dev-loop12.device
124ms dev-loop3.device
122ms dev-loop2.device
119ms dev-loop6.device
108ms ModemManager.service
107ms apparmor.service
107ms dev-loop1.device
106ms systemd-journal-flush.service
95ms NetworkManager.service
95ms snapd.seeded.service
93ms avahi-daemon.service
87ms polkit.service
84ms packagekit.service
82ms proc-sys-fs-binfmt_misc.mount
78ms thermald.service
76ms wpa_supplicant.service
74ms systemd-udevd.service
54ms smartmontools.service
53ms user@1000.service
51ms secureboot-db.service
46ms apport.service
44ms rsyslog.service
43ms systemd-fsck@dev-disk-by\x2duuid-37A6\x2dDE91.service
42ms keyboard-setup.service
37ms cups.service
33ms systemd-sysctl.service
28ms systemd-journald.service
28ms plymouth-start.service
27ms systemd-modules-load.service
21ms plymouth-quit.service
19ms snap-bare-5.mount
18ms snap-core-14447.mount
17ms snap-core20-1587.mount
17ms snap-core20-1822.mount
16ms systemd-tmpfiles-setup-dev.service
15ms snap-core22-504.mount
15ms dev-hugepages.mount
15ms dev-mqueue.mount
15ms sys-kernel-debug.mount
14ms sys-kernel-tracing.mount
13ms snap-firefox-1635.mount
13ms systemd-tmpfiles-setup.service
12ms snap-gedit-664.mount
12ms plymouth-read-write.service
12ms kmod-static-nodes.service
12ms kerneloops.service
12ms systemd-sysusers.service
12ms modprobe@drm.service
11ms modprobe@configfs.service
11ms snap-gnome\x2d3\x2d38\x2d2004-112.mount
11ms modprobe@fuse.service
10ms snap-gnome\x2d3\x2d38\x2d2004-119.mount
10ms snap-gnome\x2d42\x2d2204-56.mount
9ms systemd-random-seed.service
9ms systemd-backlight@backlight:intel_backlight.service
8ms user-runtime-dir@1000.service
7ms snap-gtk\x2dcommon\x2dthemes-1535.mount
7ms grub-common.service
6ms snap-notepadqq-855.mount
6ms systemd-remount-fs.service
6ms grub-initrd-fallback.service
6ms snap-snapd-17950.mount
6ms alsa-restore.service
5ms systemd-update-utmp-runlevel.service
5ms systemd-user-sessions.service
4ms systemd-rfkill.service
4ms console-setup.service
4ms sddm.service
3ms swapfile.swap
3ms systemd-update-utmp.service
3ms ufw.service
3ms nvidia-persistenced.service
2ms rtkit-daemon.service
2ms sys-fs-fuse-connections.mount
1ms setvtrgb.service
1ms modprobe@efi_pstore.service
1ms sys-kernel-config.mount
1ms modprobe@pstore_blk.service
1ms modprobe@pstore_zone.service
1ms modprobe@ramoops.service
369us snapd.socket

最后是systemd-analyze critical-chain的输出：

anti@anti-msi:~$ systemd-analyze critical-chain

The time when unit became active or started is printed after the "@" character.

The time the unit took to start is printed after the "+" character.

graphical.target @7.557s
└─multi-user.target @7.557s
└─kerneloops.service @7.544s +12ms
└─network-online.target @7.528s
└─NetworkManager-wait-online.service @1.118s +6.408s
└─NetworkManager.service @1.022s +95ms
└─dbus.service @1.021s
└─basic.target @1.014s
└─sockets.target @1.014s
└─snapd.socket @1.014s +369us
└─sysinit.target @1.011s
└─snapd.apparmor.service @881ms +130ms
└─apparmor.service @771ms +107ms
└─local-fs.target @769ms
└─boot-efi.mount @586ms +183ms
└─systemd-fsck@dev-disk-by\x2duuid-37A6\x2dDE91.service @541ms +43ms
└─dev-disk-by\x2duuid-37A6\x2dDE91.device @515ms

希望有经验的大佬能帮忙看看，怎么优化启动速度，还有那个重复显示logo的问题是怎么回事？

备注：内容来源于stack exchange，提问作者Antiii