Zorin OS very slow to start

Hi, when I turn on my convertible laptop it is very slow to start Zorin (basically it takes a good couple of minutes to get to the Zorin logo screen). Having previously installed windows I remember it was very fast to start. How can I fix this?

The convertible laptop is an HP detachable x2 with Zorin OS 17 Lite installed. Thanks in advance to anyone who will answer me.

Windows includes "Fast Startup" which is actually not a boot initialization sequence. Instead, it hibernates the machine, waking it, bypassing the more lengthy boot sequence.

You can enable and set up Hibernation in Zorin OS if you would like to use it.

Can you please clarify a well measured time for Zorin OS to boot?
"Two minutes" as an accurate time frame sounds quite lengthy to me and suggests there may be a bit of troubleshooting.
But, "a couple minutes" as a human expression of more time than they wanted that is in actuality 45 seconds, would mean that patience is today's lesson of the day.

Excuse me, how do I enable hibernation?

I will post a link to a guide which will likely make a much clearer job of it than I would:

As you review the steps, please feel free to use this thread or the forum to examine details or ask any questions along the way.

The guide covers Ubuntu 22.04, which is the Base the Zorin OS 17 is built upon.

As they are using Lite, I wonder if they need xfce method? This is what Brave A.I. comes up with for xfce (=Lite):

Enable Hibernation in Xfce

To enable hibernation in XFCE, follow these steps:

  1. Ensure Swap Space: Make sure you have a swap partition or file that is at least as large as your system’s RAM. If you don’t have a swap file, you can create one using the command sudo fallocate -l 8G /swapfile (adjust the size as needed) and then set it up with sudo mkswap /swapfile and sudo swapon /swapfile.
  2. Find Swap UUID and Offset: If you have a swap file, find its UUID and offset. Use the command sudo filefrag -v /swapfile to get the offset and findmnt -no UUID -T /swapfile to get the UUID.
  3. Edit GRUB Configuration: Open /etc/default/grub in a text editor with root permissions, and add the UUID and offset to the GRUB_CMDLINE_LINUX_DEFAULT line. For example:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash resume=UUID=your_swap_uuid resume_offset=your_swap_offset"
 
  • Replace your_swap_uuid and your_swap_offset with the actual values you obtained.
  • Update GRUB: Run sudo update-grub to apply the changes.
  • Edit Initramfs Configuration: Create or edit the /etc/initramfs-tools/conf.d/resume file to include the resume line with the UUID and offset:
RESUME=UUID=your_swap_uuid resume_offset=your_swap_offset
 
  • Again, replace your_swap_uuid and your_swap_offset with the actual values.
  • Regenerate Initramfs: Run sudo update-initramfs -u to regenerate the initramfs.
  • Enable Hibernation in PolicyKit: Create or edit the /etc/polkit-1/localauthority/50-local.d/com.ubuntu.enable-hibernate.pkla file to allow hibernation:
[Re-enable hibernate by default in upower]
Identity=unix-user:*
Action=org.freedesktop.upower.hibernate
ResultActive=yes

[Re-enable hibernate by default in logind]
Identity=unix-user:*
Action=org.freedesktop.login1.hibernate;org.freedesktop.login1.handle-hibernate-key;org.freedesktop.login1;org.freedesktop.login1.hibernate-multiple-sessions;org.freedesktop.login1.hibernate-ignore-inhibit
ResultActive=yes
 
  1. Reboot: Reboot your system to apply all the changes.
  2. Test Hibernation: After rebooting, you can test hibernation by running sudo systemctl hibernate. If everything is configured correctly, your system should hibernate and resume as expected.
  3. Enable Hibernation in XFCE Power Manager: If you want to enable the hibernation option in the XFCE power manager, you can use the command xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-hibernate-key -n -t bool -s true to allow the hibernation key to be handled by systemd-logind.

Remember to test hibernation carefully to ensure that it works correctly on your system, as hibernation can sometimes cause issues on certain hardware configurations.

1 Like

Argh.

I missed spotting that in the O.P.

Thanks for your attention to detail.
@enry, take note of @swarfendor437's post rather than mine.

The Point from @Aravisian with Fast Start-Up in Windows is a good Start for looking to. Another things You could take a Look on are if Secure Boot and Fast Boot in the BIOS are turned off.

And could You post some Hardware Specs? I mean CPU, GPU, RAM etc.