提升的deepin的启动速度，大家请出招- Community

[ Content contribution] 提升的deepin的启动速度，大家请出招

Technology Exchange 691 views · 6 replies ·

森林的天空

deepin

2025-09-22 21:52

Author

我感觉deepin在我的macbook（i3双核，8G内存，SSD硬盘）上启动都一般，我先优化了grub的启动：

sudo vim /etc/default/grub.d/11_dde.cfg,修改内容如下：
GRUB_TIMEOUT=0 \\启动时间改为0
GRUB_TIMEOUT_STYLE=hidden \\把启动菜单给隐藏
GRUB_BACKGROUND="" \\这个是开机出现前加载的一个蓝色背景，加载完就是加载启动菜单，在加载deepin的几个大字动画，这个背景没有啥用，去掉感觉会优雅点
sudo update-grub \\更新grub.cfg配置文件
修改完后发现启动还是要38秒，但是目前还没有完整的学习systemd的相关知识，还不知道要关哪些service，等学完了再优化一下。
我很好奇，麒麟是如何做到10来秒就能开机进桌面的，不知道大家体验过麒麟v11没，有知道的，请多多指教。

Reply Like 0 Favorite View the author

All Replies

jjcui8595

deepin

Resources Team

2025-09-22 22:02

配置较低，很难快速启动

Reply Like 0 View the author

把一切操作变成GUI

deepin

Backbone of ecological co-construction group

2025-09-22 22:20

这就不得不拿出我当年的帖子了：https://bbs.deepin.org/zh/post/267009

Reply Like 0 View the author

森林的天空

deepin

2025-09-23 06:13

把一切操作变成GUI：

这就不得不拿出我当年的帖子了：https://bbs.deepin.org/zh/post/267009

好贴，多谢哈

Reply Like 0 View the author

森林的天空

deepin

2025-09-23 07:14

deepin启动时间35秒，算多么，同样的硬件装Ubuntu，不到25秒

1.236s udisks2.service
796ms deepin-authenticate.service
777ms dev-nvme0n1p3.device
765ms dev-nvme0n1p1.device
755ms dev-nvme0n1p5.device
727ms dev-nvme0n1p2.device
725ms lightdm.service
694ms accounts-daemon.service
436ms upower.service
429ms fprintd.service
417ms user@1000.service
346ms systemd-journal-flush.service
344ms modprobe@efi_pstore.service
341ms dde-backlight-helper.service
338ms systemd-logind.service
337ms systemd-hostnamed.service
314ms lvm2-monitor.service
314ms systemd-udev-trigger.service
310ms dde-dconfig-daemon.service
287ms polkit.service
276ms dde-greeter-setter.service
266ms bluetooth.service
254ms systemd-modules-load.service
252ms avahi-daemon.service
243ms event-log.service
229ms e2scrub_reap.service
207ms NetworkManager.service
204ms samba-ad-dc.service
198ms dbus.service
160ms systemd-udevd.service
156ms lastore-daemon.service
153ms wpa_supplicant.service
133ms grub-common.service
123ms systemd-timedated.service
119ms cups.service
118ms iio-sensor-proxy.service
118ms systemd-timesyncd.service
115ms systemd-journald.service
111ms deepin-devicecontrol.service
109ms dde-lock-service.service
108ms systemd-tmpfiles-setup-dev.service
106ms systemd-tmpfiles-setup-dev-early.service
104ms systemd-remount-fs.service
103ms systemd-binfmt.service
97ms modprobe@drm.service
83ms atd.service
80ms systemd-fsck@dev-disk-by\x2duuid-9031\x2d6EEC.service
68ms dev-hugepages.mount
68ms proc-sys-fs-binfmt_misc.mount
67ms dev-mqueue.mount
66ms sys-kernel-debug.mount
64ms systemd-fsck@dev-disk-by\x2duuid-401aa606\x2d3880\x2d4ab5\x2db752\x2da90885ca3f4e.service
64ms modprobe@fuse.service
63ms org.deepin.linglong.PackageManager.service
62ms modprobe@loop.service
60ms systemd-fsck@dev-disk-by\x2duuid-bda7dc2e\x2d3ee9\x2d4450\x2da16a\x2dc448def0d4ce.service
60ms sys-kernel-tracing.mount
60ms modprobe@dm_mod.service
57ms blk-availability.service
56ms systemd-random-seed.service
55ms systemd-tmpfiles-setup.service
53ms kmod-static-nodes.service
45ms uos-ste-resourced.service
44ms modprobe@configfs.service
41ms systemd-sysctl.service
41ms systemd-user-sessions.service
35ms user-runtime-dir@1000.service
35ms systemd-update-utmp.service
34ms tmp.mount
29ms ipwatchd.service
28ms sys-kernel-config.mount
26ms dev-disk-by\x2duuid-ae2a0a62\x2d2e17\x2d4380\x2d94a5\x2da5e2a48e9650.swap
21ms sys-fs-fuse-connections.mount
18ms systemd-backlight@backlight:acpi_video0.service
16ms systemd-update-utmp-runlevel.service
14ms systemd-backlight@leds:spi::kbd_backlight.service
10ms alsa-restore.service