Announcement

Collapse
No announcement yet.

Slow boot up on desktop but not laptop

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Slow boot up on desktop but not laptop

    Hello.

    I've used Linux for years but never really on an experience level. So please bear with me.

    Although I don't think it's the distro that is to blame, I will address that I have 6.2 on both the desktop and laptop. I have used previous version of KDE Neon, Linuxmint, etc, and the results are basically the same.
    When selecting "Neon Linux" at the bootloader, the laptop can take a matter of 5 seconds or so. The desktop last clocked in at 2 minutes, and 45 seconds.

    I'd appreciate any help on this. I have looked this issue up but so far, no real detail on how to fix it, at least coming from someone who doesn't know the complete Linux language.
    Thanks


    #2
    Moving to the KDE neon topic, since this is not Kubuntu related

    Comment


      #3
      The difference mainly will be in the hardware related, but one can look at what may be holding things up:

      See:
      https://www.kubuntuforums.net/forum/...ystemd-analyze
      and more detail
      https://opensource.com/article/20/9/...-configuration
      Last edited by claydoh; Oct 11, 2024, 07:39 PM.

      Comment


        #4
        I have done the systemd in the terminal. I just don't really know what I am looking. But this is what my desktop says:

        Code:
        [FONT=monospace][COLOR=#54ff54][B]jeremy@jeremy-741[/B][/COLOR][COLOR=#000000]:[/COLOR][COLOR=#5454ff][B]~[/B][/COLOR][COLOR=#000000]$ systemd-analyze blame [/COLOR]
        30.419s man-db.service
        12.294s gpu-manager.service
        9.425s systemd-journal-flush.service
        7.676s NetworkManager-wait-online.service
        5.113s networkd-dispatcher.service
        5.034s systemd-logind.service
        3.795s apparmor.service
        3.063s dev-sda5.device
        2.290s fwupd.service
        1.145s systemd-tmpfiles-clean.service
        1.010s user@1000.service
        930ms systemd-modules-load.service
        900ms systemd-binfmt.service
        808ms snapd.service
        682ms systemd-fsck@dev-disk-by\x2duuid-D690\x2d3B84.service
        571ms systemd-sysusers.service
        566ms neon-packagekit-online-update-policy.service
        556ms NetworkManager.service
        537ms systemd-random-seed.service
        520ms proc-sys-fs-binfmt_misc.mount
        469ms keyboard-setup.service
        463ms fwupd-refresh.service
        416ms boot-efi.mount
        397ms packagekit.service
        340ms systemd-sysctl.service
        284ms systemd-tmpfiles-setup-dev.service
        270ms ufw.service
        268ms systemd-udev-trigger.service
        246ms plymouth-read-write.service[/FONT]
        Not sure if you prefer this in code format or not. Been so long since I was last on a linux forum.

        Comment


          #5
          Code format is perfect but you can remove any text format like color and font, since these don't work in the block, but it is fine.
          It can help to see the output of just systemd-analyze to see if part of it is in the initial startup --BIOS

          And critical-chain shows how much time things add overall

          You can see the startup services that are taking long times. Some of these may be held up by other things, and do note that things are also loaded in parallel.

          All of the multi-second times are mostly too long, but man-db.service is the weird one.
          but it may be from systemd-journal-flush.service

          https://askubuntu.com/questions/http...taking-so-long


          Comment


            #6
            The part that makes sense is what is taking a long time. But I have no idea how to resolve it, and what should be removed, changed, etc...

            That link doesn't work.

            Comment


              #7
              https://askubuntu.com/questions/1348...taking-so-long
              HERE if the editor decides to mangle the url again

              You basically need to investigate the first two or three items, as these are not only slow, but probably are holding back the other items as well.

              Comment

              Working...
              X