It takes my PC (which should be fast enough; Ryzen 9, NVME) running OpenSUSE TW 42 seconds to boot, more than 30 seconds longer than before. Does anyone know what could cause the 38-second discrepancy between network.target and systemd-user-sessions.service? Is there a way to gather more information about what steps happen in between?

Posted image as text:

graphical.target @1min 42.681s
└─display-manager.service @1min 42.084s +597ms
  └─systemd-user-sessions.service @1min 42.059s +22ms
    └─network.target @4.014s
      └─NetworkManager.service @2.546s +1.466s
        └─network-pre.target @2.546s
          └─wpa_supplicant.service @4.012s +33ms
            └─dbus.service @2.054s +42ms
              └─basic.target @2.049s
                └─sockets.target @2.049s
                  └─cockpit.socket @2.036s +12ms
                    └─sysinit.target @2.003s
                      └─systemd-update-utmp.service @1.966s +36ms
                        └─auditd.service @1.939s +26ms
                          └─systemd-tmpfiles-setup.service @1.750s +162ms
                            └─systemd-journal-flush.service @1.008s +691ms
                              └─var.mount @999ms +6ms
                                └─local-fs-pre.target @992ms
                                  └─systemd-tmpfiles-setup-dev.service @829ms +79ms
                                    └─kmod-static-nodes.service @399ms +209ms
                                      └─systemd-journald.socket
                                        └─system.slice
                                          └─-.slice

EDIT: It was waiting for a network mount with a device that wasn’t online anymore.

  • Stepbro@lemmy.world
    link
    fedilink
    English
    arrow-up
    12
    ·
    1 year ago

    You can see exactly what it waits for by removing “rhgb quiet” from grub_cmdline_linux and grub2 mkconfig. But usually it’ll be like “Network Manager wait online” or something dumb.