Slow boot into Lubuntu 24.04

Hi, I am new to Lubuntu (have historically used Ubuntu and elementaryOS) on this machine and am experiencing slow boot times into fresh installation of Lubuntu 24.04. It works great once into the desktop - super snappy and great but getting there is taking some time. This is on a 2008 macbook 5,1 - specs below via neofetch.


Last boot (from hitting the powerbutton) I timed at just under 3 minutes. Symptom is that the screen is black for over half this time with a static (non flashing) white dash in the upper left corner of the black screen. Dash disappears, I then briefly get some screen garble and then the circulating blue Lubuntu hummingbird logo load screen pops up and then promptly into desktop.

Is this normal behavior for Lubuntu? It doesnt seem like it and I read about previous builds as of 18 having worse delays at boot (7-8-10minutes!) so was hoping that there was a solution that I did not see searching this forum. Thank you all in advance for any assistance in trimming down the boot time.

Coe

I did want to add a few things that I have noticed/tried and forgot to add to my original inquiry.

  1. My 240gb SSD is older, so I considered a hardware/drive issue. I have a 2nd identical spec macbook so ran the same USB installer on that macbook except with a 140gb spinner vs the ssd and got the same freeze/slow boot behavior. This leads me to think it is not hardware related, rather something software.
  2. When I boot and it is “frozen”, I cant get into grub or anything. The keyboard is completely unresponsive until just before the blue Lubuntu hummingbird boot screen appears.

Thanks again for any insight.

low hanging fruit, try:

systemd-analyze
systemd-analyze blame
systemd-analyze critical-chain

1 Like

Same issue here although I often have up to 4-5 minutes without anything happening. Using a Macbook Pro 2009.

Journalctl -b have given me reason to believe it has to do with systemd-network and that it times out before continuing. I’ve tried quite a lot of different things but not succeeded yet.

Some relevant logs:

https://www.thisoldcabin.net/journalctl_systemd-timesyncd.txt
https://www.thisoldcabin.net/critical_chain.txt

I get the same error no matter if I use wifi or plugged in to an ethernet cable.

I believe the screen garbage isn’t related though, I had the same during install etc. but got rid of it when disabling boot screen and have seen nothing of it ever since. But something with the Lubuntu distro isn’t playing a 100% nice with rhe older Macbook hardwares it seems. But I’m pretty confident that there will be a solution sometime. :smiley:

2 Likes

That’s pretty interesting—thanks for sharing! :smiley:

I wonder if the hardware they put on the Macbook’s is special or something. Might be one of those cases where it isn’t greatly supported on Linux due to the vendor.

1 Like

systemd-resolved[556]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 192.168.1.1

This means it’s not talking to the default dns. EDNS0 means the Mac was trying to use an extension mechanism for DNS (I haven’t had to deal with this myself - not an Apple fan, so, I’ll defer here), failed and switched back to non-extended DNS and then probably failed again. Simple question: is your DNS at 192.168.1.1? If not then it’s a configuration issue.

1 Like

systemd-analyze

Unfortunately, I can only add one pic at a time as I’m new to this forum.

1 Like

systemd-analyze blame

1 Like

systemd-analyze critical-chain

If a moderator can combine my posts into one, that would be fantastic. Thanks again to everyone for the discussion and insights.

1 Like

Well spotted! Indeed the DNS is not located there, the router is however. I get a bit curious to why it’s going there for DNS, /etc/resolv.conf doesn’t point there for example.

Another hint at the problem at least.

@Certofex - You have the same issue as me, the delay isn’t visible without checking the log. Try sudo journalctl -b and look for the section where you get a few minutes delay.

2 Likes

hm… curious there are no measurements for the firmware? 26s from power on to ready is pretty decent… Well, this + the journalctl output you provided would seem to point to a dns configuration issue.

I will indeed investigate the matter. The boot time - timeout excluded - is indeed as snappy as one would hope. I just hope to solve the boot case.

Have had a few hectic days with work + family, so I haven’t had time to look into this, but will return as soon as I have. Thank you for good and relevant feedback!

Woho! Problem solved.

I found this thread with discussions on DNS issues for Ubuntu: networking - DNS issues after upgrading to 20.04 - Ask Ubuntu

One user suggested that problems could be related to systemd-resolved.service and handled that by:

sudo systemctl enable systemd-resolved.service
sudo systemctl start systemd-resolved.service

I tried the same and voila - boot time down to roughly 20 seconds! Will keep an eye on the problem and see if it’s a temporary or permanent solution.

Once again thank you @eeyore for your help! Much appreciated!

2 Likes

…and sorry folks. It was a temporary success.

Next reboot and the problem is back. However there’s at least ONE successful boot now.

The quest continues.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.