启动时间长

启动时间长

您好,我是 Linux 新手,今天安装了 Kubuntu,现在我的笔记本电脑启动需要 10 秒左右,而使用 Windows 11 时则需要 1.5 秒。我能以某种方式解决这个问题吗?

另外值得一提的是,我觉得我的电脑启动了 2 次?msi 徽标出现了 2-3 次,然后才显示 kubuntu 界面。

anti@anti-msi:~$ systemd-analyze
Startup finished in 2.379s (kernel) + 7.564s (userspace) = 9.943s 
graphical.target reached after 7.557s in userspace

anti@anti-msi:~$ 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 [email protected]
  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 [email protected]
  11ms [email protected]
  11ms snap-gnome\x2d3\x2d38\x2d2004-112.mount
  11ms [email protected]
  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 [email protected]
   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 [email protected]
 369us snapd.socket


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

答案1

10 秒的实际启动时间还不错。我看不出这是“问题”。如果您经常关闭和打开笔记本电脑,则可以使用暂停而不是关机。如果您不经常这样做,那么等待 10 秒并不算太长。

我的系统启动需要 12 秒,我不认为它“慢”。

Windows 启动速度实际上不会在 1.5 秒内完成。它使用的是快速启动,也就是休眠。如果你重新启动 Windows,你会发现它的启动速度比 Ubuntu 慢得多。

您还可以在 Ubuntu 中启用休眠或混合睡眠。但在某些硬件上,它可能无法正常工作。这就是为什么它默认被禁用的原因。

供应商徽标出现几次也是可以的。

相关内容