Extremely slow boot after install on Tumbleweed

English Install/Boot/Login
1

I just installed Tumbleweed, I haven’t done much besides installing the nvidia proprietary drivers and it takes one and a half minute for the system to boot, I have an nvme.

I noticed something quite strange using systemd-analyze critical-chain but I have no idea how to fix it, here:

    graphical.target u/1.234s

    └─display-manager.service u/674ms +558ms

      └─systemd-user-sessions.service u/671ms +3ms

        └─network.target u/669ms
          └─NetworkManager.service u/654ms +14ms
            └─network-pre.target u/653ms
              └─firewalld.service u/514ms +139ms
                └─polkit.service u/499ms +14ms
                  └─basic.target u/495ms

                    └─sockets.target u/495ms

                      └─pcscd.socket u/495ms

                        └─sysinit.target u/494ms
                          └─systemd-update-utmp.service u/491ms +3ms
                            └─auditd.service u/475ms +14ms
                              └─systemd-tmpfiles-setup.service u/469ms +5ms

                                └─systemd-journal-flush.service u/433ms +35ms

                                  └─var.mount u/426ms +6ms
                                    └─dev-nvme0n1p3.device u/584542y 2w 2d 20h 1min 49.209s +759ms

Here’s the systemd-analyze blame results:

    759ms dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart3.device

    759ms dev-nvme0n1p3.device
    759ms sys-devices-pci0000:00-0000:00:06.0-0000:02:00.0-nvme-nvme0-nvme0n1-nvme0n1p3.device
    759ms dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_PRO_1TB_S5GXNF0R234952J\x2dpart3.device
    759ms dev-disk-by\x2duuid-72d1b2e5\x2d0c49\x2d4e96\x2db204\x2d10a45bec40ef.device
    759ms dev-disk-by\x2did-nvme\x2deui.002538b211b25c2e\x2dpart3.device
    759ms dev-disk-by\x2dpartuuid-6787021a\x2d5654\x2d46f5\x2d92ea\x2d4cf96459dfa7.device
    720ms sys-devices-pci0000:00-0000:00:06.0-0000:02:00.0-nvme-nvme0-nvme0n1-nvme0n1p2.device
    720ms dev-nvme0n1p2.device
    720ms dev-disk-by\x2did-nvme\x2deui.002538b211b25c2e\x2dpart2.device
    720ms dev-disk-by\x2duuid-5bf4374a\x2dfd58\x2d45c9\x2db59a\x2dadfa4b8c61aa.device
    720ms dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_PRO_1TB_S5GXNF0R234952J\x2dpart2.device
    720ms dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart2.device
    720ms dev-disk-by\x2dpartuuid-eef57d42\x2d7ab4\x2d4284\x2da33a\x2d08ee33a01982.device
    705ms sys-devices-platform-serial8250-tty-ttyS0.device
    705ms dev-ttyS0.device
    705ms sys-devices-platform-serial8250-tty-ttyS10.device
    705ms dev-ttyS10.device
    705ms sys-devices-platform-serial8250-tty-ttyS15.device
    705ms dev-ttyS15.device
    705ms sys-devices-platform-serial8250-tty-ttyS1.device
    705ms dev-ttyS1.device
    705ms dev-ttyS12.device
    705ms sys-devices-platform-serial8250-tty-ttyS12.device
    704ms sys-devices-platform-serial8250-tty-ttyS13.device
    704ms dev-ttyS13.device
    704ms sys-devices-platform-serial8250-tty-ttyS17.device
    704ms dev-ttyS17.device
    703ms sys-devices-platform-serial8250-tty-ttyS16.device
    703ms dev-ttyS16.device
    703ms sys-devices-platform-serial8250-tty-ttyS11.device
    703ms dev-ttyS11.device
    702ms dev-ttyS14.device
    702ms sys-devices-platform-serial8250-tty-ttyS14.device
    702ms sys-devices-platform-serial8250-tty-ttyS19.device
    702ms dev-ttyS19.device
    702ms dev-ttyS20.device
    702ms sys-devices-platform-serial8250-tty-ttyS20.device
    701ms dev-ttyS21.device
    701ms sys-devices-platform-serial8250-tty-ttyS21.device
    701ms dev-ttyS22.device
    701ms sys-devices-platform-serial8250-tty-ttyS22.device
    701ms dev-ttyS24.device
    701ms sys-devices-platform-serial8250-tty-ttyS24.device
    701ms dev-ttyS18.device
    701ms sys-devices-platform-serial8250-tty-ttyS18.device
    701ms dev-ttyS25.device
    701ms sys-devices-platform-serial8250-tty-ttyS25.device
    701ms sys-devices-platform-serial8250-tty-ttyS3.device
    701ms dev-ttyS3.device
    701ms dev-ttyS27.device
    701ms sys-devices-platform-serial8250-tty-ttyS27.device
    700ms sys-devices-platform-serial8250-tty-ttyS29.device
    700ms dev-ttyS29.device
    700ms dev-ttyS23.device
    700ms sys-devices-platform-serial8250-tty-ttyS23.device
    700ms sys-devices-platform-serial8250-tty-ttyS2.device
    700ms dev-ttyS2.device
    700ms dev-ttyS31.device
    700ms sys-devices-platform-serial8250-tty-ttyS31.device
    699ms sys-devices-platform-serial8250-tty-ttyS28.device
    699ms dev-ttyS28.device
    699ms dev-ttyS5.device
    699ms sys-devices-platform-serial8250-tty-ttyS5.device
    699ms sys-devices-platform-serial8250-tty-ttyS6.device
    699ms dev-ttyS6.device
    699ms dev-ttyS7.device
    699ms sys-devices-platform-serial8250-tty-ttyS7.device
    699ms dev-ttyS9.device
    699ms sys-devices-platform-serial8250-tty-ttyS9.device
    699ms dev-ttyS26.device
    699ms sys-devices-platform-serial8250-tty-ttyS26.device
    698ms dev-ttyS8.device
    698ms sys-devices-platform-serial8250-tty-ttyS8.device
    697ms dev-ttyS30.device
    697ms sys-devices-platform-serial8250-tty-ttyS30.device
    697ms sys-devices-platform-serial8250-tty-ttyS4.device
    697ms dev-ttyS4.device
    689ms dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_PRO_1TB_S5GXNF0R234952J\x2dpart1.device
    689ms sys-devices-pci0000:00-0000:00:06.0-0000:02:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
    689ms dev-nvme0n1p1.device
    689ms dev-disk-by\x2dpartuuid-9c048a26\x2d8686\x2d44ca\x2dac0b\x2d785577e1f05e.device
    689ms dev-disk-by\x2duuid-0CC3\x2d60ED.device
    689ms dev-disk-by\x2did-nvme\x2deui.002538b211b25c2e\x2dpart1.device
    689ms dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart1.device
    682ms dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_PRO_1TB_S5GXNF0R234952J.device
    682ms dev-disk-by\x2did-nvme\x2deui.002538b211b25c2e.device
    682ms dev-disk-by\x2ddiskseq-1.device
    682ms dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1.device
    682ms sys-devices-pci0000:00-0000:00:06.0-0000:02:00.0-nvme-nvme0-nvme0n1.device
    682ms dev-nvme0n1.device
    558ms display-manager.service
    511ms systemd-rfkill.service
    378ms postfix.service
    366ms dracut-pre-udev.service
    208ms initrd-switch-root.service
    188ms dracut-initqueue.service
    172ms dracut-cmdline.service
    139ms firewalld.service
    119ms initrd-parse-etc.service
    103ms user@1000.service
    67ms lvm2-monitor.service
    54ms systemd-udev-trigger.service
    46ms dev-hugepages.mount
    46ms boot-efi.mount
    45ms dev-mqueue.mount
    45ms sys-kernel-debug.mount
    45ms sys-kernel-tracing.mount
    44ms kmod-static-nodes.service
    43ms modprobe@configfs.service
    43ms modprobe@drm.service
    43ms modprobe@fuse.service
    42ms plymouth-quit-wait.service
    41ms systemd-fsck@dev-disk-by\x2duuid-0CC3\x2d60ED.service
    41ms chronyd.service
    41ms systemd-modules-load.service
    41ms systemd-journald.service
    40ms systemd-remount-fs.service
    38ms sound-extra.service
    35ms systemd-journal-flush.service
    33ms apparmor.service
    32ms augenrules.service
    31ms kbdsettings.service
    30ms smartd.service
    28ms cups.service
    28ms systemd-fsck-root.service
    28ms prime-select.service
    28ms ModemManager.service
    27ms systemd-random-seed.service
    26ms plymouth-switch-root.service
    25ms upower.service
    24ms mcelog.service
    22ms systemd-udevd.service
    21ms power-profiles-daemon.service
    21ms systemd-logind.service
    17ms systemd-vconsole-setup.service
    16ms rtkit-daemon.service
    15ms udisks2.service
    15ms avahi-daemon.service
    14ms auditd.service
    14ms NetworkManager.service
    14ms polkit.service
    13ms alsa-restore.service
    13ms dbus.service
    13ms \x2esnapshots.mount
    12ms boot-grub2-i386\x2dpc.mount
    12ms bluetooth.service
    11ms issue-generator.service
    11ms plymouth-start.service
    11ms boot-grub2-x86_64\x2defi.mount
    11ms plymouth-read-write.service
    10ms home.mount
    10ms dev-disk-by\x2duuid-5bf4374a\x2dfd58\x2d45c9\x2db59a\x2dadfa4b8c61aa.swap
    10ms opt.mount
    9ms systemd-tmpfiles-clean.service
    9ms root.mount
    8ms srv.mount
    7ms usr-local.mount
    7ms user-runtime-dir@1000.service
    6ms initrd-cleanup.service
    6ms var.mount
    5ms NetworkManager-wait-online.service
    5ms systemd-tmpfiles-setup.service
    5ms nscd.service
    4ms dracut-shutdown.service
    4ms systemd-tmpfiles-setup-dev.service
    3ms tmp.mount
    3ms systemd-user-sessions.service
    3ms systemd-update-utmp.service
    2ms initrd-udevadm-cleanup-db.service
    2ms systemd-sysctl.service
    2ms kernel-sysctl.service
    1ms sys-fs-fuse-connections.mount
    1ms sys-kernel-config.mount
1 Like
2

Looks to me like you’re booting in 1.234s, more than twice as fast as my nvme’s 2.901s:

# systemd-analyze
Startup finished in 15.938s (firmware) + 16.955s (loader) + 1.455s (kernel) + 1.651s (initrd) + 2.922s (userspace) = 38.922s
graphical.target reached after 2.901s in userspace.
# systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @2.901s
└─multi-user.target @2.900s
  └─smartd.service @818ms +34ms
    └─basic.target @810ms
      └─sockets.target @810ms
        └─telnet.socket @809ms
          └─sysinit.target @804ms
            └─systemd-update-utmp.service @784ms +3ms
              └─systemd-tmpfiles-setup.service @774ms +8ms
                └─local-fs.target @773ms
                  └─usr-local.mount @769ms +3ms
                    └─systemd-fsck@dev-disk-by\x2dlabel-tm8p04usrlcl.service @737ms +29ms
                      └─dev-disk-by\x2dlabel-tm8p04usrlcl.device @584542y 2w 2d 20h 1min 48.554s +1.730s
# df -h /
Filesystem      Size  Used Avail Use% Mounted on
/dev/nvme0n1p4  7.7G  3.9G  3.5G  53% /
# pinxi -SC
System:
  Host: ab560 Kernel: 5.18.15-1-default arch: x86_64 bits: 64
    Console: pty pts/0 Distro: openSUSE Tumbleweed 20220829
CPU:
  Info: 6-core model: 11th Gen Intel Core i5-11400 bits: 64 type: MT MCP

However, I don’t know whether your /u compared to my @ makes any difference.

3

I just did a fresh install and it is related to nvidia, before I install the nvidia drivers everything boots fine but once I install them booting takes one and a half minute, sometimes even 2 whole minutes, I’m new to linux but I used the systemd-analyze commands and I can see that it shows nothing so I don’t understand what’s wrong, previously I thought the 500000y device thing was something bad but I guess not.
Here are the result but I guess they won’t help since it says I booted in 17s which is not true.

#  systemd-analyze
Startup finished in 11.600s (firmware) + 1.918s (loader) + 1.165s (kernel) + 1.335s (initrd) + 1.339s (userspace) = 17.360s  
graphical.target reached after 1.339s in userspace.
# systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character. 
The time the unit took to start is printed after the "+" character. 

graphical.target @1.339s 
└─**display-manager.service @778ms +560ms**
  └─time-sync.target @776ms 
    └─**chronyd.service @748ms +28ms**
      └─network.target @747ms 
        └─**NetworkManager.service @729ms +17ms**
          └─network-pre.target @728ms 
            └─**firewalld.service @582ms +146ms**
              └─**polkit.service @565ms +15ms**
                └─basic.target @561ms 
                  └─sockets.target @561ms 
                    └─pcscd.socket @561ms 
                      └─sysinit.target @560ms 
                        └─**systemd-update-utmp.service @557ms +3ms**
                          └─**auditd.service @536ms +21ms**
                            └─**systemd-tmpfiles-setup.service @522ms +12ms**
                              └─**systemd-journal-flush.service @478ms +43ms**
                                └─**var.mount @469ms +7ms**
                                  └─**dev-nvme0n1p2.device @584542y 2w 2d 20h 1min 49.142s +870ms**[FONT=monospace]
# df -h /
Filesystem       Size   Used  Avail Use% Mounted on
/dev/nvme0n1p2   900G   7,5G  891G   1% /
[/FONT]# inxi -SC
**System:**
  **Host:** localhost.localdomain **Kernel:** 5.19.2-1-default **arch:** x86_64 **bits:** 64 
    **Desktop:** KDE Plasma **v:** 5.25.4 **Distro:** openSUSE Tumbleweed 20220829 
**CPU:**
  **Info:** 12-core (8-mt/4-st) **model:** 12th Gen Intel Core i7-12700K **bits:** 64 
    **type:** MST AMCP
4

Did you have a look at journalctl/dmesg messages if anything appears there?

5

I don’t know how to use those commands, would you mind help guide me on what to do exactly?