• NetworkManager


    Why the *** the NM takes 30+ seconds?

    Startup finished in 584542y 2w 2d 20h 1min 44.851s (loader) + 3.648s (kernel) + 36.660s (userspace) = 40.309s
    
      
    31.597s NetworkManager.service  
    6.516s lightdm.service  
    5.926s systemd-logind.service  
    2.182s systemd-vconsole-setup.service  
    1.601s teamviewerd.service  
    1.273s systemd-modules-load.service  
    1.140s polkit.service  
    1.108s dev-mqueue.mount  
    1.030s sys-kernel-debug.mount  
    987ms dev-hugepages.mount  
    973ms tmp.mount  
    931ms run-media-i\\x2dsty-Filmek.mount  
    844ms udisks2.service  
    820ms kmod-static-nodes.service  
    737ms upower.service  
    523ms user@1000.service  
    488ms systemd-tmpfiles-setup.service  
    406ms systemd-journal-flush.service  
    397ms systemd-random-seed.service  
    353ms sys-kernel-config.mount  
    334ms alsa-restore.service  
    333ms run-media-i\\x2dsty-Egyeb.mount  
    286ms systemd-udev-trigger.service  
    275ms systemd-user-sessions.service  
    250ms systemd-tmpfiles-setup-dev.service  
    236ms systemd-remount-fs.service  
    166ms bluetooth.service  
    146ms rtkit-daemon.service  
    138ms systemd-update-utmp.service  
    119ms systemd-sysctl.service  
    62ms systemd-udevd.service  
    27ms sys-fs-fuse-connections.mount  
    
    
      
    The time after the unit is active or started is printed after the "@" character.  
    The time the unit takes to start is printed after the "+" character.  
      
    graphical.target @36.660s  
    └─teamviewerd.service @35.058s +1.601s  
    └─network.target @35.056s  
    └─NetworkManager.service @3.459s +31.597s  
    └─basic.target @3.361s  
    └─timers.target @3.333s  
    └─systemd-tmpfiles-clean.timer @3.333s  
    └─sysinit.target @3.272s  
    └─systemd-vconsole-setup.service @1.073s +2.182s  
    └─systemd-journald.socket @1.063s  
    └─-.mount @1.057s  
    └─system.slice @1.062s  
    └─-.slice @1.061s  
    
    

    Don't forget to mark as [SOLVED], if your problem was solved!

  • Why the *** the NM takes 30+ seconds?

    Startup finished in 584542y 2w 2d 20h 1min 44.851s (loader) + 3.648s (kernel) + 36.660s (userspace) = 40.309s
    
      
    31.597s NetworkManager.service  
    6.516s lightdm.service  
    5.926s systemd-logind.service  
    2.182s systemd-vconsole-setup.service  
    1.601s teamviewerd.service  
    1.273s systemd-modules-load.service  
    1.140s polkit.service  
    1.108s dev-mqueue.mount  
    1.030s sys-kernel-debug.mount  
    987ms dev-hugepages.mount  
    973ms tmp.mount  
    931ms run-media-i\\x2dsty-Filmek.mount  
    844ms udisks2.service  
    820ms kmod-static-nodes.service  
    737ms upower.service  
    523ms user@1000.service  
    488ms systemd-tmpfiles-setup.service  
    406ms systemd-journal-flush.service  
    397ms systemd-random-seed.service  
    353ms sys-kernel-config.mount  
    334ms alsa-restore.service  
    333ms run-media-i\\x2dsty-Egyeb.mount  
    286ms systemd-udev-trigger.service  
    275ms systemd-user-sessions.service  
    250ms systemd-tmpfiles-setup-dev.service  
    236ms systemd-remount-fs.service  
    166ms bluetooth.service  
    146ms rtkit-daemon.service  
    138ms systemd-update-utmp.service  
    119ms systemd-sysctl.service  
    62ms systemd-udevd.service  
    27ms sys-fs-fuse-connections.mount  
    
    
      
    The time after the unit is active or started is printed after the "@" character.  
    The time the unit takes to start is printed after the "+" character.  
      
    graphical.target @36.660s  
    └─teamviewerd.service @35.058s +1.601s  
    └─network.target @35.056s  
    └─NetworkManager.service @3.459s +31.597s  
    └─basic.target @3.361s  
    └─timers.target @3.333s  
    └─systemd-tmpfiles-clean.timer @3.333s  
    └─sysinit.target @3.272s  
    └─systemd-vconsole-setup.service @1.073s +2.182s  
    └─systemd-journald.socket @1.063s  
    └─-.mount @1.057s  
    └─system.slice @1.062s  
    └─-.slice @1.061s  
    
    

    Don't forget to mark as [SOLVED], if your problem was solved!

  • @“I-sty”:14zj7if2 said:

    Why the *** the NM takes 30+ seconds?[/quote:14zj7if2]NM cannot connect until your network interfaces have been initialized, renamed, and then released by systemd. I dont mean to discourage you, but based on your system specs I honestly don’t think you can get your boot tome much lower than it is now. Try not to get too caught up in this

Posts 3Views 524
Log in to reply