DataDrake nice it's works 😁... but now i got another problem.
if i make a systemd-analyze
i got this:
Startup finished in 4.905s (firmware) + 2.591s (loader) + 1.191s (kernel) + 3.080s (initrd) + 24.581s (userspace) = 36.351s
graphical.target reached after 24.571s in userspace
it's so many time only for userspace i want to reduce that. And if i make a systemd-analyze blame
i get this:
11.487s systemd-journal-flush.service
5.278s ModemManager.service
5.047s lvm2-pvscan@8:2.service
4.885s udisks2.service
4.653s systemd-tmpfiles-setup.service
3.587s NetworkManager.service
2.957s systemd-udevd.service
2.287s bluetooth.service
2.283s avahi-daemon.service
2.283s clr-boot-manager-booted.service
2.273s systemd-logind.service
2.237s systemd-modules-load.service
2.151s systemd-tmpfiles-setup-dev.service
1.992s initrd-switch-root.service
1.819s org.cups.cupsd.service
1.242s systemd-rfkill.service
1.164s auditd.service
1.033s polkit.service
929ms upower.service
851ms dev-disk-by\x2duuid-a070020b\x2df326\x2d43a8\x2dbe2c\x2da26e46b4927f.swap
821ms accounts-daemon.service
679ms gdm.service
592ms dev-mqueue.mount
566ms user@21.service
544ms colord.service
493ms systemd-sysctl.service
478ms systemd-random-seed.service
476ms systemd-backlight@backlight:intel_backlight.service
454ms dev-hugepages.mount
453ms sys-kernel-debug.mount
453ms systemd-remount-fs.service
439ms systemd-udev-trigger.service
385ms systemd-journald.service
262ms systemd-resolved.service
244ms kmod-static-nodes.service
181ms wpa_supplicant.service
142ms initrd-parse-etc.service
131ms systemd-fsck-root.service
102ms systemd-hostnamed.service
60ms systemd-update-utmp.service
44ms user@1000.service
16ms snapd.socket
16ms systemd-user-sessions.service
13ms initrd-cleanup.service
7ms systemd-update-utmp-runlevel.service
5ms aa-lsm-hook.service
4ms initrd-udevadm-cleanup-db.service
3ms sys-fs-fuse-connections.mount
2ms tmp.mount
I dont know why the systemd-journal-flush.service take so many time, any idea?
PD: I would like to ask the following: which services can i deactivate to get a 5 seconds or less boot?