Apparently the reason my computer has been taking 2 minutes to boot was a faulty network mount

  • jsdz@lemmy.ml
    9·
    2 years ago

    I’m pretty sure the main system startup bottleneck is me typing the disk encryption passphrase.

    • astrsk@artemis.camp
      5·
      2 years ago

      Combine that with the 20-30 seconds my system takes to do bios memory training on the DDR5 ram and we’re practically back to the “go make some coffee while the system boots up” days 🤦

      • GodIsNull@feddit.de
        2·
        2 years ago

        Those where the good days. You always had fresh coffee when your computer was ready for work.

        • samn@lemmy.mlEnglish
          1·
          2 years ago

          As another DDR5 user, it’s not always this bad - there’s a bios setting that makes it remember the previous configuration and skips this step, but sometimes it still needs to do it, and then it can take a minute or two

    • magikmw@lemm.ee
      1·
      2 years ago

      I wish to replace it with a yubikey, but I don’t even know if it’s supported.

      • Ullebe1@lemmy.ml
        1·
        2 years ago

        It is supported by systemd to use FIDO2 + pin to decrypt luks partitions with many security keys, including Yubikeys. I use it every day on my laptop.

  • passepartout@feddit.de
    6·
    2 years ago

    You can use systemd-analyze blame if you want raw numbers:

    This command prints a list of all running units, ordered by the time they took to initialize. This information may be used to optimize boot-up times.

    Good way to see if your systemd also waits 2 minutes for a network connection which already exists but it can’t see it because systemd doesn’t do the networking (lxc containers on proxmox in my case) lol.

    Also see systemd-analyze.

    • FrostyPolicy@suppo.fi
      1·
      2 years ago

      systemd also waits 2 minutes for a network connection which already exists but it can’t see it because systemd doesn’t do the networking

      Any way to speed this up? On my system in every boot it waits for network for 30s.

      • intelati@programming.dev
        1·
        2 years ago

        If you go far enough, everything is.

        But SVGs are one of the few image types that can be human readable and editable

        • loutr@sh.itjust.works
          2·
          2 years ago

          If you go far enough, everything is.

          No, SVG are text files, it’s XML. You can write an SVG file representing a square using only a text editor relatively easily.

        • halva@discuss.tchncs.de
          2·
          2 years ago

          No, not really. Most image formats produce completely unreadable jumbo only meant to be parsed with clever maths.

  • gayhitler420@lemm.ee
    2·
    2 years ago

    I wrote a long-ish comment in another thread explaining why lots of people don’t like systemd.

    Stuff like this is why people do like systemd.

    The massive, un unixy and complex tools allow for very powerful and somewhat knowledge agnostic approaches to all sorts of problems.

    One of the nicest things about systemds toolset is that it allows a person who relies on finding the problem and googling it to resolve thing much faster than their alternative, learn what’s going on and figure it out.

    I don’t mean that as a pejorative, plenty of computer work is maintenance as opposed to engineering and there’s nothing wrong with that.

    • stifle867@programming.dev
      2·
      2 years ago

      The top/1st line is the first service and it cascaded down as each subsequent service starts. Left to right is time elapsed. Bright red line is time to start that service. Shorter is better.

      Does that help?

    • hare_ware@pawb.social
      2·
      2 years ago

      Honestly I laughed when it just spit an SVG in text at me. I was wholly expecting a GUI to appear.

  • Pantherina@feddit.de
    1·
    2 years ago

    My bottleneck at boot is my damn Bios… I am so hyped about flashing Heads on my Thinkpad T430.

    Even the old legacy Lenovo bioses where very fast at startup. The UEFI (with extremely nice secure-boot settings too) of an AMD Acer starts up in like 2 seconds. My old intel Thinkpad T430 needs like 4 seconds.

    And then my Lenovo T495 bullshit UEFI comes. No secure boot configuration at all, I have no idea how to boot from USB sticks, and this thing needs nearly 10 seconds to boot! Linux compared, a full Desktop OS, needs 3 seconds to show SDDM (after the LUKS dialog)

      • Pantherina@feddit.de
        0·
        2 years ago

        how does it run modern OSses?

        Its crazy how expensive T430 etc still are. People know how great they are

        • caseyweederman@lemmy.ca
          2·
          2 years ago

          I’m shocked how smoothly it runs Gnome on Debian 12. KDE on NixOS was okay but had some noticeable slowdown. Here I was thinking it would be relegated to being an Arch CLI terminal.

  • lntl@lemmy.ml
    0·
    2 years ago

    this is interesting! if i had a two minute boot time, I’d look for ways to figure out what’s going on.

    i remember init messages used to be printed to the console, but nowadays all i get is Manjaro branding. anyone know how to get my console messages back from systemd?