You are not logged in.
I want to compare the boot times of both systemd-boot and efistub but when I boot with efi stub
systemd-analyze
I get this error:
Bootup is not yet finished (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0).
Please try again later.
Hint: Use 'systemctl list-jobs' to see active jobs
Here's the output of
sudo systemctl list-jobs
JOB UNIT TYPE STATE
89 graphical.target start waiting
190 plymouth-quit-wait.service start running
90 multi-user.target start waiting
3 jobs listed.
I've never troubleshooted a problem like this before so I'm unsure what logs I should provide. While I could post the the entire output of journalctl, I have privacy concerns with doing so.
Last edited by JaydenDev (2024-01-28 16:58:19)
System Specs:
Intel Core i5-2400 Nvidia GTX 1050ti Logitech G402 Hyperion Fury (Mouse) BestBuy Essentials USB Keyboard
Software Specifications:
Desktop Environment: KDE Plasma Window Manager: KWin Operating System: Arch Linux (btw)
Offline
After stopping and masking
plymouth-quit-wait.service
the command now works. EFISTUB loads 200ms faster than systemd-boot in the singular comparison i ran my system booted 3-6 seconds faster
I never installed or set up plymouth on this installation so I'm unsure why this service was present in the first place
Last edited by JaydenDev (2024-01-28 16:58:50)
System Specs:
Intel Core i5-2400 Nvidia GTX 1050ti Logitech G402 Hyperion Fury (Mouse) BestBuy Essentials USB Keyboard
Software Specifications:
Desktop Environment: KDE Plasma Window Manager: KWin Operating System: Arch Linux (btw)
Offline