5 ms·
> ... I find the boot time compelling enough (~23sec until login, plus 2sec to open the browser) that I do not need this. I think something is slowing down you
by aiur3la 10y ago
> ... I find the boot time compelling enough (~23sec until login, plus 2sec to open the browser) that I do not need this.
I think something is slowing down your boot, I get faster boot on a 2008 thinkpad running the same OS.
OT: systemd was supposed to improve boot performance but it has actually become much worse. Upstart on a weak chromebook boots in under 2 sec, why shouldn't your current generation thinkpad with a fast SSD match that?
- karussell 10y agoWould be nice to have a faster one, yes :) ... some recommendations? Just fyi: I measure boot time from the time I press the power button. The BIOS logo appears a staggering 8sec or something although the BIOS fast boot is enabled. (Maybe the sync with NSA or something ;))
- aiur3la 10y agoI haven't tested any of these myself, but this page contains some great suggestions: https://askubuntu.com/questions/10290/how-do-i-improve-boot-speed https://askubuntu.com/questions/10290/how-do-i-improve-boot-... The initial boot delay is VERY annoying. I wish libreboot was supported on my laptop, then I could ditch lenovos ancient BIOS (and the NSA ping) once and for all: https://libreboot.org/docs/hcl/#supported_laptops_x86intel https://libreboot.org/docs/hcl/#supported_laptops_x86intel
- JoshTriplett 10y ago8 seconds for the BIOS sounds ridiculous; that should take less than a second. Check that you've booted and shut down successfully on the prior boot; with those, the boot should take much less time. (On an improper shutdown, the BIOS may do some extra work that takes longer.) Also check that you don't have some option enabled to make it wait around a while for a keyboard key. For the Linux portion of your boot, try running "systemd-analyze plot > /tmp/boot.svg" and looking at that. (Also note that "kernel" includes any time spent waiting in the initramfs for you to type your disk encryption passphrase.)
- dom0 10y agoUnsurprisingly UEFI didn't change much about vendor firmware shittiness. There's also still firmware around which just takes 5-10 seconds of black screen before doing shit.
- jmnicolas 10y agoCheck that PXE boot is disabled.
- karussell 10y agoWhen I disabled UEFI Network Stack ipv4 and ipv6 it is indeed much faster: just ~2seconds
- mateuszf 10y agoI don't think this is a problem with systemd. On Archilinux using it - it's quite simple to get < 5s boot times.
- dajonker 10y agoOh yeah, with Arch linux and some tweaking I got under 10 seconds on my X240. But I switched to Fedora, which is still under 20 seconds.
- cel1ne 10y agoI find it curious that you care about boot-times. I use macbooks and just close and reopen the lid. Waking from this sleep takes less than a second usually. My average uptime is about 22 days until I reboot for an update or something. I used Linux for years, and I understood that in 2008 sleep/resume on notebooks didn't properly work, but now we have 2017 - 9 years later!
- eltoozero 10y agoMac is my daily driver for this very reason, I'm a consultant and I need to frequently grab and go. I've had Linux on mobile for ages and have yet to have reliable sleep/wake behavior on a dozen machines over the years. Sleep on Linux works reliably if you run it inside a Mac VM though, FWIW! ;)
- karussell 10y agoImportant difference: sleep usually works and is fast. What often does not work is hibernation (recover from disc)
- pmontra 10y agoAccording to a comment in the post it fails when the swap partition is encrypted. However why enable swap with 16 GB of RAM? I've been running without swap for almost 3 years and never had any trouble. If I start approaching the limit I'll buy another 16 GB.