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

  • passepartout@feddit.de
    link
    fedilink
    arrow-up
    1
    ·
    1 year 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
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      1 year 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.

      • passepartout@feddit.de
        link
        fedilink
        arrow-up
        0
        ·
        1 year ago

        In my case i masked the service because like i said, inside the lxc container there is no networking to do, it’s done on the host (proxmox). Note that disabling the service in my case was not enough since it could be invoked by other services, and then you would have to wait again.

        See this for further info and maybe arguments why you shouldn’t do it.

  • Pantherina@feddit.de
    link
    fedilink
    arrow-up
    0
    ·
    1 year 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)

    • Dkarma@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

      I adore my T530. I could kill a moose with it if it ever stops working. Literally dug it out of a dumpster and saw the i7 sticker and almost shit myself. Honestly I’ve had it for years and never even looked at the bios cuz with an SSD even with encryption enabled on the disk it booted in 30 sec.

      Until I built my latest rig I was doing ai image generation on it with 8gigs of ram.

      • Pantherina@feddit.de
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        1 year ago

        If you have a T530, there is coreboot for it! Dont know if 1vyra.in works, check it.

        Its not the question, if it works, but how it works! Its trustworthy and not extremely outdated proprietary garbage. Actually extremely important to update

      • Pantherina@feddit.de
        link
        fedilink
        arrow-up
        0
        ·
        1 year ago

        how does it run modern OSses?

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

  • jsdz@lemmy.ml
    link
    fedilink
    arrow-up
    0
    ·
    1 year ago

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

    • magikmw@lemm.ee
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

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

      • Contend6248@feddit.de
        link
        fedilink
        arrow-up
        0
        ·
        1 year ago

        You can’t even use a fucking fingerprint scanner while being in the system, that package is borked for months and nobody seem to care to solve it.

        I think using Yubikey at boot time is quite out of reach