Hi again. I bought an old laptop with 16 Gb RAM and used it to play with Zorin 17 Core for several months. I then upgraded to 18 Core. I get the impression that the computer now runs slower - is it my imagination or does anyone else have experience of this?
It could be that you're running into a similar issue with Wayland that I was when I first tried Zorin 18. Could you, if you haven't already, switch to X versus Wayland and see if you're running into the same thing?
The way my issues manifested themselves was that the framerate would drop from 60 to 30 during day to day use, making it FEEL like the system was performing much worse than it actually was.
1 Like
What Specs does the Laptop have?
1 Like
Using Warp terminal, it keeps suggesting going to X, though it used to be fine on Wayland. So far, I've not been able to get the screen where you choose X or Wayland - it just goes from Off to full loading.
Found it - forgot to use Log off. Makes no difference - even getting past "Zorin 18" takes ages (and before that)
Intel Celeron N2830 x2
16 Gb RAM
128 Gb SSD
Intel HD Graphics (BYT)
Wayland
Did You already tried it with switching from Wayland to Xorg?
EDIT: Ah, I see now this:
Do You have Auto Login enabled? Because then You don't have the Login Screen where You can switch between both.
1 Like
Managed to change it, but it's no better. Takes forever to load Zorin
Is the main problem the bootup time? We could look at what's causing it with
systemd-analyze blame
That could show what might be causing a really long boot time.
1 Like
@applecheeks37 . Mainly boot, but it seems to take longer to start apps.
Here's the printout - don't know why it does this skipping, but its done it twice, so i thought i'd better leave it in.
tom@tom-SATELLITE-PRO-NB10t-A-11G:~$ systemd-analyze blame
23.023s plymouth-quit-wait.service
5.957s NetworkManager-wait-online.service
5.319s snapd.seeded.service
5.030s accounts-daemon.service
4.871s gnome-remote-desktop.service
4.595s power-profiles-daemon.service
4.481s snapd.service
4.464s polkit.service
4.318s thermald.service
4.180s udisks2.service
3.696s NetworkManager.service
3.309s networkd-dispatcher.service
3.138s postfix@-.service
2.941s avahi-daemon.service
2.714s dev-sda3.device
2.671s gpu-manager.service
2.474s rsyslog.service
2.437s pulseaudio-enable-autospawn.service
2.432s systemd-logind.service
2.351s switcheroo-control.service
2.157s lm-sensors.service
2.125s apparmor.service
1.476s systemd-suspend.service
lines 1-23...skipping...
23.023s plymouth-quit-wait.service
5.957s NetworkManager-wait-online.service
5.319s snapd.seeded.service
5.030s accounts-daemon.service
4.871s gnome-remote-desktop.service
4.595s power-profiles-daemon.service
4.481s snapd.service
4.464s polkit.service
4.318s thermald.service
4.180s udisks2.service
3.696s NetworkManager.service
3.309s networkd-dispatcher.service
3.138s postfix@-.service
2.941s avahi-daemon.service
2.714s dev-sda3.device
2.671s gpu-manager.service
2.474s rsyslog.service
2.437s pulseaudio-enable-autospawn.service
2.432s systemd-logind.service
2.351s switcheroo-control.service
2.157s lm-sensors.service
2.125s apparmor.service
1.476s systemd-suspend.service
1.320s firewalld.service
1.145s e2scrub_reap.service
1.119s fwupd.service
1.082s systemd-udev-trigger.service
1.009s user@1000.service
916ms nmbd.service
862ms dbus.service
739ms systemd-resolved.service
675ms upower.service
644ms dev-loop3.device
638ms dev-loop2.device
634ms dev-loop1.device
633ms ModemManager.service
629ms dev-loop4.device
627ms keyboard-setup.service
604ms dev-loop5.device
604ms bluetooth.service
575ms dev-loop0.device
lines 1-41
23.023s plymouth-quit-wait.service
5.957s NetworkManager-wait-online.service
5.319s snapd.seeded.service
5.030s accounts-daemon.service
4.871s gnome-remote-desktop.service
4.595s power-profiles-daemon.service
4.481s snapd.service
4.464s polkit.service
4.318s thermald.service
4.180s udisks2.service
3.696s NetworkManager.service
3.309s networkd-dispatcher.service
3.138s postfix@-.service
2.941s avahi-daemon.service
2.714s dev-sda3.device
2.671s gpu-manager.service
2.474s rsyslog.service
2.437s pulseaudio-enable-autospawn.service
2.432s systemd-logind.service
2.351s switcheroo-control.service
2.157s lm-sensors.service
2.125s apparmor.service
1.476s systemd-suspend.service
1.320s firewalld.service
1.145s e2scrub_reap.service
1.119s fwupd.service
1.082s systemd-udev-trigger.service
1.009s user@1000.service
916ms nmbd.service
862ms dbus.service
739ms systemd-resolved.service
675ms upower.service
644ms dev-loop3.device
638ms dev-loop2.device
634ms dev-loop1.device
633ms ModemManager.service
lines 1-36
Nothing interesting here? Time to reinstall 17?
If you don't need any snap or flatpak applications then I would remove those as they bloat the system.
If only you could remove systemd without breaking the system it would be even lighter!
When Zorin 17 worked better on your laptop, I'd go back to Zorin 17. It will still be supported until 2027. Often that is the better choice for computers which are older than 10 years.
Take a look into your BIOS if secure boot and fast boot are turned off (or do you have you created a MOK to use secure boot with Linux?) and if you have a Dualboot with Windows if also fast startup is disabled there at energy settings. Sometimes updates change the BIOS settings to default settings.
Going back to your specifications, I see it is a Celeron Processor. These have a much more limited function than the mainstream Intel Processors. (AMD Sempron's are not much better). I hate to say it but you might fair better by changing to a lightweight distro. I installed Q4OS Plasma on a machine I built in 2006 which only has a Single Athlon 64 Processor, 2 Gb RAM maximum the board will take, and an 8x AGP with 512 Mb RAM and Q4OS runs on it but slowly - I am sure it would fly on your notebook/PC. It also offers different themed layouts at no cost, you just have to install 'Look Switcher' from the Welcome Screen's shortcut to 'Install Applications'. Or go back to Zorin 17. Q4OS 5.8 is good until Mid-2028.
1 Like