Before I erase macOS and go full Solus...

MMB

Hi to all Solus guys!
My main problem with macOS on my iMac is that takes more than needed time to boot. About 90 seconds at best. And I am talking about just booting. Then I do logging and the hard disk is cr**ing for about four to five minutes where I barely can have a responsible system, yes it may work but at ridiculous pace. After that minutes it just goes fine. I just can't stand the excuses for this, mostly when, lets say, Mac OS Snow Leopard booted and logged-in in twelve seconds, on a hard disk!!! I know what you are thinking... Go SSD? I have done. An SSD running the latest macOS available for this iMac.. it is still slower to boot than old MacOS from hard disk 😅 crappy modern OS!

MMB

This is what I need, speed up Solus boot time

systemd-analyze
Startup finished in 24.417s (firmware) + 8.894s (loader) + 1.411s (kernel) + 7.971s (initrd) + 16.175s (userspace) = 58.870s
graphical.target reached after 16.114s in userspace

MMB

systemd-analyze blame
6.475s ModemManager.service
5.007s NetworkManager.service
4.197s systemd-fsck-root.service
4.133s ufw.service
3.893s avahi-daemon.service
3.708s clr-boot-manager-booted.service
3.705s systemd-logind.service
3.704s org.cups.cupsd.service
3.571s vboxdrv.service
2.311s systemd-udevd.service
2.127s initrd-switch-root.service
2.075s auditd.service
1.783s systemd-tmpfiles-setup-dev.service
1.718s colord.service
1.408s systemd-tmpfiles-setup.service
1.344s systemd-journal-flush.service
1.043s polkit.service
928ms accounts-daemon.service
819ms udisks2.service
770ms aa-lsm-hook.service
696ms systemd-sysctl.service
693ms wpa_supplicant.service
631ms lightdm.service
427ms upower.service
417ms systemd-tmpfiles-clean.service
376ms systemd-journald.service
375ms systemd-remount-fs.service
347ms systemd-udev-trigger.service
248ms kmod-static-nodes.service
244ms sys-kernel-debug.mount
185ms systemd-random-seed.service
160ms dev-mqueue.mount
158ms snapd.socket
149ms bluetooth.service
119ms initrd-parse-etc.service
94ms systemd-resolved.service
69ms systemd-rfkill.service
60ms systemd-backlight@backlight:radeon_bl0.service
59ms systemd-update-utmp.service
59ms user@1000.service
49ms tmp.mount
30ms systemd-user-sessions.service
11ms initrd-cleanup.service
5ms systemd-update-utmp-runlevel.service
5ms alsa-restore.service
3ms dev-hugepages.mount
3ms sys-fs-fuse-connections.mount
3ms initrd-udevadm-cleanup-db.service

RaMa

MMB 6.475s ModemManager.service

You could save 6.475 seconds by disabling this service? It seems that this service does mobile broadband (2G/3G/4G), (unless you use this network connection of course...)

https://www.linux.com/tutorials/cleaning-your-linux-startup-process/

MMB

How can I speed up those 24.417sec on firmware? Anything else I can do to make it faster?
Thanks.

uaos

speed things up?
But from a person who build and refurbished some PC's, not a mac, SSD performance is always better and faster. So the question is why is the boot time not as good from before? Right? Some SSD's are not fully Mac or Linux compatible. For my Linux system I look for from Amazon being Linux compatible, I know that SSD from OWC are Mac compatible. Sorry, this seems to be the only idea I have.

MMB

Hi! Is not an SSD problem as the SSD is no longer on the iMac. I installed on a MacBook Pro that needs it more than the iMac.

I just wish Solus booted a bit faster if is possible. Maybe is not and it boots as fan as it can boot on a hard disk? Is that on any way related to the slow time (24 seconds) on firmware? I remember, wait for it, that Solus on 1.x version few years ago booted on 3 seconds on the MacBook Pro running his mega-slow 5200rpm hard disk. I understand that that speeds may be no longer possible. But just a bit faster than it does now?

MMB

When I ask and complain on other websites they just tell me that ‘modern OS are not optimized for hard disks’ 😅

Well these modern OSes don’t give much that my I can’t do on my G5

Justin

Firmware is firmware, it depends on your hardware and how they start the system up.

systemd-analyze 
Startup finished in 15.157s (firmware) + 50ms (loader) + 1.149s (kernel) + 1.247s (initrd) + 743ms (userspace) = 18.348s
graphical.target reached after 737ms in userspace

I ignore firmware when determining boot time, so mine is 3.191s.

MMB

RaMa Thanks! I’ll do that and share the results. That link comes handy! I was looking for a way to do that. Thanks a lot RaMa!

Mitchell-McCann

RaMa

6.475s ModemManager.service

You could save 6.475 seconds by disabling this service?

The 6.475 seconds is cumulative of all the steps below that. So the ModemManager.service only takes about 1.468 seconds.

RaMa

Mitchell-McCann The 6.475 seconds is cumulative of all the steps below that. So the ModemManager.service only takes about 1.468 seconds.

OK, thank you! :-)