Il 05/11/2017 18:28, Felix Miata ha scritto:
Marco Calistri composed on 2017-11-05 12:58 (UTC-0500):
I made a simple test: disabled graphical boot completely but boot duration is almost the same as when I enable it.
I could see that there is a sort of freezing when kernel arives at the step when outputs "Switch to root..." or something like that.
So for me also by disabling the splash stuff, the result of boot duration is the same, may be my system and HDD are too slow.
No need to guess why it takes the time it takes. Find out where the time is being spent:
systemd-analyze blame
Hi, I was not aware of this command! Here the result of it: marco@linux-turion64:~> systemd-analyze blame 8.467s ModemManager.service 8.033s dev-sda5.device 7.061s initrd-switch-root.service 5.233s SuSEfirewall2_init.service 4.846s display-manager.service 4.632s upower.service 4.170s rsyslog.service 4.051s postfix.service 2.880s jexec.service 2.874s NetworkManager.service 2.793s vboxdrv.service 2.792s nscd.service 2.730s mcelog.service 2.724s rc-local.service 2.673s avahi-daemon.service 2.127s systemd-vconsole-setup.service 1.985s polkit.service 1.946s SuSEfirewall2.service 1.775s systemd-tmpfiles-setup-dev.service 1.421s systemd-udevd.service 1.311s systemd-rfkill.service 1.106s systemd-backlight@backlight:acpi_video0.service 1.067s warsaw.service 1.057s dracut-pre-udev.service 813ms systemd-sysctl.service 691ms klog.service 652ms ntpd.service 646ms noip2.service 605ms dev-hugepages.mount 578ms user@485.service 551ms systemd-remount-fs.service 532ms sshd.service 507ms wpa_supplicant.service 491ms systemd-logind.service 480ms systemd-tmpfiles-setup.service 451ms sys-kernel-debug.mount 407ms systemd-fsck@dev-disk-by\x2did-ata\x2dSAMSUNG_HM501II_S2PMJ56B607218\x2dpart6.service 368ms accounts-daemon.service 366ms systemd-backlight@backlight:intel_backlight.service 352ms systemd-journal-flush.service 307ms systemd-journald.service 302ms dev-mqueue.mount 254ms systemd-fsck-root.service 245ms systemd-udev-trigger.service 244ms systemd-user-sessions.service 237ms systemd-random-seed.service 235ms udisks2.service 234ms plymouth-read-write.service 225ms systemd-update-utmp.service 203ms colord.service 198ms kmod-static-nodes.service 161ms systemd-modules-load.service 155ms initrd-parse-etc.service 142ms proc-sys-fs-binfmt_misc.mount 128ms dev-disk-by\x2did-ata\x2dSAMSUNG_HM501II_S2PMJ56B607218\x2dpart7.swap 128ms iscsi.service 94ms vboxautostart-service.service 77ms rtkit-daemon.service 74ms plymouth-start.service 69ms plymouth-switch-root.service 68ms home.mount 64ms user@1000.service 46ms dracut-cmdline.service 33ms dracut-shutdown.service 32ms vboxweb-service.service 26ms tmp.mount 20ms sysroot.mount 18ms dracut-pre-trigger.service 17ms issue-generator.service 14ms vboxballoonctrl-service.service 11ms initrd-cleanup.service 7ms initrd-udevadm-cleanup-db.service 6ms alsa-restore.service 5ms systemd-update-utmp-runlevel.service 5ms sys-fs-fuse-connections.mount lines 21-75/75 (END) I think at first glance I could disable at least ModemManager and Postfix since I don't use these services and seems are taking a lot of time to start. Also the services: dev-sda5.device, initrd-switch-root.service and jexec.service I would like to know what they are doing and then disable them too. Regards, -- Marco Calistri Linux version : openSUSE Tumbleweed 20171102 Kernel: 4.13.11-1.g0526da3-default - Cinnamon 3.6.0 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org