You are not logged in.

Pages: 1 2

#26 2012-12-15 23:11:02

mystara
Member
Registered: 2012-12-07
Posts: 21

Re: [gnome3.6, systemd]NetworkManager make polkit start extremely slow

I also confirm this. On x64 Arch running Unity:

 systemd-analyze blame
10083ms NetworkManager.service
  9586ms dkms.service
  6876ms laptop-mode.service
  3903ms polkit.service
   ...................

By some ungodly method, Windows boots up way faster than my Arch system because of this. Anyone have a solution yet?

Edit: What wireless cards are you all using? I'm using a Broadcom card with the proprietary drivers in the AUR.

Another edit: After disabling laptop-mode:

 systemd-analyze blame
  9303ms dkms.service
  7647ms NetworkManager.service
  4182ms upower.service
  2613ms systemd-logind.service
  2320ms polkit.service
   ..........................

Better, but still not really great.

Yet another edit: My systemd-analyze blame revealed my problem; I had to deactivate dhcpcd@eth0.service, which had been left on from when I installed the system and had to install wireless drivers using my ethernet connection before my card would work. This literally cut my boot time in half. networkmanager.service still takes a long time, but, hey, 19 second boot time, now!

 systemd-analyze
Startup finished in 2882ms (kernel) + 16157ms (userspace) = 19039ms

Last edited by mystara (2012-12-16 00:01:49)

mkdir ~/"Folder of all folders"
cd Folder\ of\ all\ Folders
# ln -s / root

Offline

#27 2012-12-16 00:12:01

beaverusiv
Member
From: Taupo, New Zealand
Registered: 2011-07-09
Posts: 41

Re: [gnome3.6, systemd]NetworkManager make polkit start extremely slow

I am on wired network, but do have some wireless connections saved. I too have broadcom-wl installed from AUR.

Offline

#28 2012-12-16 08:13:46

I-sty
Member
From: Romania
Registered: 2012-11-30
Posts: 60
Website

Re: [gnome3.6, systemd]NetworkManager make polkit start extremely slow

MyLordAngus wrote:

You can try the command 

journalctl _SYSTEMD_UNIT=NetworkManager.service

to see all logs related to NetworkManager. Perhaps you will find something interesting.

[1;39m-- Reboot --[0m
Dec 16 08:54:36 isty NetworkManager[316]: <info> NetworkManager (version 0.9.6.4) is starting...
Dec 16 08:54:36 isty NetworkManager[316]: <info> Read config file /etc/NetworkManager/NetworkManager.conf
Dec 16 08:54:36 isty NetworkManager[316]: <info> WEXT support is enabled
Dec 16 08:54:37 isty NetworkManager[316]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Dec 16 08:54:37 isty NetworkManager[316]: keyfile: parsing I-sty's Network ...
Dec 16 08:54:37 isty NetworkManager[316]: keyfile:     read connection 'I-sty's Network'
Dec 16 08:54:37 isty NetworkManager[316]: <info> trying to start the modem manager...
Dec 16 08:54:54 isty NetworkManager[316]: <info> monitoring kernel firmware directory '/lib/firmware'.
Dec 16 08:54:54 isty NetworkManager[316]: <warn> Failed to open plugin directory /usr/lib/NetworkManager: Error opening directory '/usr/lib/NetworkManager': No such file or directory
Dec 16 08:54:54 isty NetworkManager[316]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.1/0000:02:00.0/ieee80211/phy0/rfkill0) (driver iwlwifi)
Dec 16 08:54:54 isty NetworkManager[316]: <info> WiFi enabled by radio killswitch; enabled by state file
Dec 16 08:54:54 isty NetworkManager[316]: <info> WWAN enabled by radio killswitch; enabled by state file
Dec 16 08:54:54 isty NetworkManager[316]: <info> WiMAX enabled by radio killswitch; enabled by state file
Dec 16 08:54:54 isty NetworkManager[316]: <info> Networking is enabled by state file
Dec 16 08:54:54 isty NetworkManager[316]: <warn> failed to allocate link cache: (-10) Operation not supported
Dec 16 08:54:54 isty NetworkManager[316]: <info> (eth0): carrier is OFF
Dec 16 08:54:54 isty NetworkManager[316]: <info> (eth0): new Ethernet device (driver: 'r8169' ifindex: 2)
Dec 16 08:54:54 isty NetworkManager[316]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0
Dec 16 08:54:54 isty NetworkManager[316]: <info> (eth0): now managed
Dec 16 08:54:54 isty NetworkManager[316]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Dec 16 08:54:54 isty NetworkManager[316]: <info> (eth0): bringing up device.
Dec 16 08:54:54 isty NetworkManager[316]: <info> (eth0): preparing device.
Dec 16 08:54:54 isty NetworkManager[316]: <info> (eth0): deactivating device (reason 'managed') [2]
Dec 16 08:54:54 isty NetworkManager[316]: <info> (wlan0): using nl80211 for WiFi device control
Dec 16 08:54:54 isty NetworkManager[316]: <warn> (wlan0): driver supports Access Point (AP) mode
Dec 16 08:54:54 isty NetworkManager[316]: <info> (wlan0): new 802.11 WiFi device (driver: 'iwlwifi' ifindex: 3)
Dec 16 08:54:54 isty NetworkManager[316]: <info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/1
Dec 16 08:54:54 isty NetworkManager[316]: <info> (wlan0): now managed
Dec 16 08:54:54 isty NetworkManager[316]: <info> (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Dec 16 08:54:54 isty NetworkManager[316]: <info> (wlan0): bringing up device.
Dec 16 08:54:54 isty NetworkManager[316]: <info> (wlan0): preparing device.
Dec 16 08:54:54 isty NetworkManager[316]: <info> (wlan0): deactivating device (reason 'managed') [2]
Dec 16 08:54:54 isty NetworkManager[316]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
Dec 16 08:54:54 isty NetworkManager[316]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
Dec 16 08:54:54 isty NetworkManager[316]: <info> wpa_supplicant started
Dec 16 08:54:54 isty NetworkManager[316]: <info> (wlan0) supports 5 scan SSIDs
Dec 16 08:54:54 isty NetworkManager[316]: <info> (wlan0): supplicant interface state: starting -> ready
Dec 16 08:54:54 isty NetworkManager[316]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Dec 16 08:54:54 isty NetworkManager[316]: <warn> Trying to remove a non-existant call id.
Dec 16 08:54:54 isty NetworkManager[316]: <info> (wlan0): supplicant interface state: ready -> inactive
Dec 16 08:54:54 isty NetworkManager[316]: <info> (wlan0) supports 5 scan SSIDs
Dec 16 08:54:55 isty NetworkManager[316]: <info> Auto-activating connection 'I-sty's Network'.
Dec 16 08:54:55 isty NetworkManager[316]: <info> Activation (wlan0) starting connection 'I-sty's Network'
Dec 16 08:54:55 isty NetworkManager[316]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Dec 16 08:54:55 isty NetworkManager[316]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Dec 16 08:54:55 isty NetworkManager[316]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Dec 16 08:54:55 isty NetworkManager[316]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Dec 16 08:54:55 isty NetworkManager[316]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Dec 16 08:54:55 isty NetworkManager[316]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Dec 16 08:54:55 isty NetworkManager[316]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Dec 16 08:54:55 isty NetworkManager[316]: <info> Activation (wlan0/wireless): connection 'I-sty's Network' has security, and secrets exist.  No new secrets needed.
Dec 16 08:54:55 isty NetworkManager[316]: <info> Config: added 'ssid' value 'I-sty's Network'
Dec 16 08:54:55 isty NetworkManager[316]: <info> Config: added 'scan_ssid' value '1'
Dec 16 08:54:55 isty NetworkManager[316]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Dec 16 08:54:55 isty NetworkManager[316]: <info> Config: added 'psk' value '<omitted>'
Dec 16 08:54:55 isty NetworkManager[316]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Dec 16 08:54:55 isty NetworkManager[316]: <info> Config: set interface ap_scan to 1
Dec 16 08:54:55 isty NetworkManager[316]: <info> (wlan0): supplicant interface state: inactive -> scanning
Dec 16 08:54:56 isty NetworkManager[316]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Dec 16 08:54:56 isty NetworkManager[316]: <info> (wlan0): supplicant interface state: authenticating -> associating
Dec 16 08:54:56 isty NetworkManager[316]: <info> (wlan0): supplicant interface state: associating -> associated
Dec 16 08:54:56 isty NetworkManager[316]: <info> (wlan0): supplicant interface state: associated -> 4-way handshake
Dec 16 08:54:56 isty NetworkManager[316]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
Dec 16 08:54:56 isty NetworkManager[316]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'I-sty's Network'.
Dec 16 08:54:56 isty NetworkManager[316]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Dec 16 08:54:56 isty NetworkManager[316]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Dec 16 08:54:56 isty NetworkManager[316]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
Dec 16 08:54:56 isty NetworkManager[316]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Dec 16 08:54:57 isty NetworkManager[316]: <info> dhclient started with pid 496
Dec 16 08:54:57 isty NetworkManager[316]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Dec 16 08:54:58 isty dhclient[496]: Internet Systems Consortium DHCP Client 4.2.4-P2
Dec 16 08:54:58 isty dhclient[496]: Copyright 2004-2012 Internet Systems Consortium.
Dec 16 08:54:58 isty dhclient[496]: All rights reserved.
Dec 16 08:54:58 isty dhclient[496]: For info, please visit https://www.isc.org/software/dhcp/
Dec 16 08:54:58 isty dhclient[496]: 
Dec 16 08:54:58 isty NetworkManager[316]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
Dec 16 08:54:58 isty dhclient[496]: Listening on LPF/wlan0/68:5d:43:93:62:6e
Dec 16 08:54:58 isty dhclient[496]: Sending on   LPF/wlan0/68:5d:43:93:62:6e
Dec 16 08:54:58 isty dhclient[496]: Sending on   Socket/fallback
Dec 16 08:54:58 isty dhclient[496]: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Dec 16 08:54:58 isty dhclient[496]: DHCPACK from 192.168.2.1
Dec 16 08:54:58 isty dhclient[496]: bound to 192.168.2.5 -- renewal in 2147483648 seconds.
Dec 16 08:54:58 isty NetworkManager[316]: <info> (wlan0): DHCPv4 state changed preinit -> reboot
Dec 16 08:54:58 isty NetworkManager[316]: <info>   address 192.168.2.5
Dec 16 08:54:58 isty NetworkManager[316]: <info>   prefix 24 (255.255.255.0)
Dec 16 08:54:58 isty NetworkManager[316]: <info>   gateway 192.168.2.1
Dec 16 08:54:59 isty NetworkManager[316]: <info>   nameserver '192.168.2.1'
Dec 16 08:54:59 isty NetworkManager[316]: <info>   domain name 'Isti'
Dec 16 08:54:59 isty NetworkManager[316]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Dec 16 08:54:59 isty NetworkManager[316]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started...
Dec 16 08:55:00 isty NetworkManager[316]: <info> (wlan0): device state change: ip-config -> activated (reason 'none') [70 100 0]
Dec 16 08:55:01 isty NetworkManager[316]: <info> Policy set 'I-sty's Network' (wlan0) as default for IPv4 routing and DNS.
Dec 16 08:55:01 isty NetworkManager[316]: <info> Activation (wlan0) successful, device activated.
Dec 16 08:55:01 isty NetworkManager[316]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.

Same problem.

systemd-analyze blame
 17513ms NetworkManager.service
  1225ms run-media-isty-Vegyes2.mount
  1133ms run-media-isty-Vegyes1.mount
   879ms systemd-remount-fs.service

A little statistic:

Startup finished in 2330ms (kernel) + 17434ms (userspace) = 19765ms
Startup finished in 2265ms (kernel) + 19187ms (userspace) = 21453ms
Startup finished in 2246ms (kernel) + 20269ms (userspace) = 22516ms
Startup finished in 2324ms (kernel) + 18075ms (userspace) = 20400ms
Startup finished in 2248ms (kernel) + 18791ms (userspace) = 21040ms
Startup finished in 2407ms (kernel) + 27289ms (userspace) = 29696ms
Startup finished in 2451ms (kernel) + 25630ms (userspace) = 28082ms
Startup finished in 2374ms (kernel) + 22542ms (userspace) = 24916ms
Startup finished in 2252ms (kernel) + 8291ms  (userspace) = 10543ms
Startup finished in 2459ms (kernel) + 26011ms (userspace) = 28470ms
Startup finished in 2252ms (kernel) + 22347ms (userspace) = 24600ms
Startup finished in 2360ms (kernel) + 13106ms (userspace) = 15466ms
Startup finished in 15378ms (kernel) + 7838ms (userspace) = 23216ms
Dec 02:
Startup finished in 2534ms (kernel) + 8398ms  (userspace) = 10933ms
Startup finished in 29891ms (kernel) + 7982ms (userspace) = 37873ms
Dec 03:
Startup finished in 2766ms (kernel) + 8833ms (userspace) = 11600ms
Startup finished in 2634ms (kernel) + 8192ms (userspace) = 10826ms
Startup finished in 2547ms (kernel) + 29452ms (userspace) = 32000ms
Dec 05:
Startup finished in 2415ms (kernel) + 31610ms (userspace) = 34026ms
Startup finished in 2243ms (kernel) + 13423ms (userspace) = 15666ms
Startup finished in 2762ms (kernel) + 12051ms (userspace) = 14813ms
Startup finished in 2485ms (kernel) + 27647ms (userspace) = 30133ms
Startup finished in 2559ms (kernel) + 24983ms (userspace) = 27543ms
Dec 08:
Startup finished in 2332ms (kernel) + 12503ms (userspace) = 14836ms
Startup finished in 2334ms (kernel) + 11739ms (userspace) = 14073ms
Startup finished in 2544ms (kernel) + 25202ms (userspace) = 27746ms
Startup finished in 2621ms (kernel) + 13211ms (userspace) = 15833ms
Dec 10:
Startup finished in 2378ms (kernel) + 13741ms (userspace) = 16120ms
Dec 11:
Startup finished in 2485ms (kernel) + 7994ms (userspace) = 10480ms
Dec 13:
Startup finished in 2580ms (kernel) + 9029ms (userspace) = 11610ms
Startup finished in 2533ms (kernel) + 9160ms (userspace) = 11693ms
Startup finished in 2418ms (kernel) + 9561ms (userspace) = 11980ms
Dec 15:
Startup finished in 2517ms (kernel) + 27733ms (userspace) = 30250ms
Startup finished in 2461ms (kernel) + 12645ms (userspace) = 15107ms
Startup finished in 2203ms (kernel) + 8869ms (userspace) = 11073ms
Startup finished in 2250ms (kernel) + 12683ms (userspace) = 14933ms
Startup finished in 2357ms (kernel) + 25942ms (userspace) = 28300ms
Dec 16:
Startup finished in 2550ms (kernel) + 25909ms (userspace) = 28460ms

Last edited by I-sty (2012-12-16 08:17:22)

Offline

#29 2012-12-18 04:10:58

mystara
Member
Registered: 2012-12-07
Posts: 21

Re: [gnome3.6, systemd]NetworkManager make polkit start extremely slow

beaverusiv wrote:

I am on wired network, but do have some wireless connections saved. I too have broadcom-wl installed from AUR.

For me, the problem was actually that very same driver (I never did like Broadcom's drivers). Check out the wiki for running the b43 driver; my network manager now boots in... *checks systemd-analyze blame* 302ms. You have to automate the loading of the b43 driver at boot, so that takes an extra 2200ms, but that's nothing compared to what it once was.

mkdir ~/"Folder of all folders"
cd Folder\ of\ all\ Folders
# ln -s / root

Offline

#30 2012-12-18 08:48:54

beaverusiv
Member
From: Taupo, New Zealand
Registered: 2011-07-09
Posts: 41

Re: [gnome3.6, systemd]NetworkManager make polkit start extremely slow

So, theoretically, if I disable my wireless I should see an improvement? I'll try tomorrow.

Offline

#31 2012-12-18 18:48:20

mystara
Member
Registered: 2012-12-07
Posts: 21

Re: [gnome3.6, systemd]NetworkManager make polkit start extremely slow

beaverusiv wrote:

So, theoretically, if I disable my wireless I should see an improvement? I'll try tomorrow.

Give it a go, but if it's still loading the Broadcom driver, then theoretically little will have changed, if I understand what I did correctly.

mkdir ~/"Folder of all folders"
cd Folder\ of\ all\ Folders
# ln -s / root

Offline

#32 2012-12-28 13:41:10

siriusb
Member
From: Hungary
Registered: 2010-01-01
Posts: 422

Re: [gnome3.6, systemd]NetworkManager make polkit start extremely slow

Hi,

Having the same problem. Tried to boot with networkmanager disabled, with wicd, but it's the same slow boot.

journalctl -b | grep dbus
Dec 28 13:30:10 hparch dbus[1008]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Dec 28 13:30:51 hparch dbus[1008]: [system] Failed to activate service 'org.freedesktop.PolicyKit1': timed out
Dec 28 13:30:59 hparch dbus[1008]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Dec 28 13:30:59 hparch dbus[1008]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details.
Dec 28 13:31:01 hparch dbus[1008]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service'
Dec 28 13:31:03 hparch dbus[1008]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'
Dec 28 13:31:05 hparch dbus-daemon[1008]: dbus[1008]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Dec 28 13:31:05 hparch dbus-daemon[1008]: dbus[1008]: [system] Failed to activate service 'org.freedesktop.PolicyKit1': timed out
Dec 28 13:31:05 hparch dbus-daemon[1008]: dbus[1008]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Dec 28 13:31:05 hparch dbus-daemon[1008]: dbus[1008]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details.
Dec 28 13:31:05 hparch dbus-daemon[1008]: dbus[1008]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service'
Dec 28 13:31:05 hparch dbus-daemon[1008]: dbus[1008]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'
Dec 28 13:31:12 hparch dbus[1008]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Dec 28 13:31:12 hparch dbus-daemon[1008]: dbus[1008]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Dec 28 13:31:12 hparch dbus[1008]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Dec 28 13:31:13 hparch dbus-daemon[1008]: dbus[1008]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
$ journalctl -b | grep polkit
Dec 28 13:30:10 hparch dbus[1008]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Dec 28 13:30:51 hparch polkitd[1583]: Started polkitd version 0.107
Dec 28 13:30:53 hparch polkitd[1583]: Loading rules from directory /etc/polkit-1/rules.d
Dec 28 13:30:54 hparch polkitd[1583]: Loading rules from directory /usr/share/polkit-1/rules.d
Dec 28 13:30:55 hparch polkitd[1583]: Finished loading, compiling and executing 1 rules
Dec 28 13:30:55 hparch polkitd[1583]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
Dec 28 13:31:05 hparch dbus-daemon[1008]: dbus[1008]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Dec 28 13:31:07 hparch polkitd[1583]: Registered Authentication Agent for unix-session:1 (system bus name :1.9 [/usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1], object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
$ systemd-analyze 
Startup finished in 24443ms (kernel) + 79996ms (userspace) = 104440ms
$ systemd-analyze blame
 55215ms NetworkManager.service
 44622ms polkit.service
  7417ms ufw.service

Offline

#33 2013-03-05 13:35:58

dartfira
Member
Registered: 2010-08-23
Posts: 104

Re: [gnome3.6, systemd]NetworkManager make polkit start extremely slow

Same here. Don't you have any news about that problem? Thinks is something related to wireless connection.

Offline

#34 2013-05-08 15:39:49

silenc3r
Member
From: Poland
Registered: 2009-08-29
Posts: 149

Re: [gnome3.6, systemd]NetworkManager make polkit start extremely slow

I got similar problem, NetworkManager startup time went from ~7s to ~35s after installing Preload and Prelink.

Offline

#35 2013-06-19 17:36:05

jrussell
Member
From: Cape Town, South Africa
Registered: 2012-08-16
Posts: 510

Re: [gnome3.6, systemd]NetworkManager make polkit start extremely slow

This might be unrelated, but:

I have a problem whereby my wireless connects after about 20 seconds of me having logged into gnome from lightdm, never used to happen, I used to be connected to my network before the gnome session was even ready.
Cant remember when this changed unfortunately.

I assume everyones network only comes up after networkmanager has been started? I dont seem to have a slow boot, only slow connection to my wireless network, wired is fine.

jason-laptop% sudo systemd-analyze blame
[sudo] password for jason: 
         13.911s NetworkManager.service
          3.646s avahi-daemon.service
          3.644s systemd-logind.service
          1.535s alsa-restore.service
          1.368s systemd-modules-load.service
          1.067s sys-kernel-debug.mount
          1.062s systemd-udev-trigger.service
          1.046s systemd-remount-fs.service
          1.021s colord.service
           984ms dev-hugepages.mount
           977ms dev-mqueue.mount
           966ms systemd-tmpfiles-setup-dev.service
           908ms tmp.mount
           753ms ModemManager.service
           727ms polkit.service
           454ms systemd-vconsole-setup.service
           410ms systemd-sysctl.service
           310ms systemd-tmpfiles-clean.service
           283ms wpa_supplicant.service
           240ms systemd-update-utmp.service
           221ms udisks2.service
           188ms accounts-daemon.service
           188ms systemd-user-sessions.service
           137ms systemd-journal-flush.service
           130ms ntpd.service
           115ms systemd-udevd.service
            87ms systemd-random-seed-load.service
            62ms upower.service
            58ms lightdm.service
            50ms systemd-tmpfiles-setup.service
            40ms rtkit-daemon.service
             1ms sys-fs-fuse-connections.mount
             1ms sys-kernel-config.mount

*Edit
https://wiki.archlinux.org/index.php/Ne … ect_faster
Makes no difference to me

Last edited by jrussell (2013-06-19 17:38:01)

bitcoin: 1G62YGRFkMDwhGr5T5YGovfsxLx44eZo7U

Offline

#36 2013-06-22 14:57:12

lonaowna
Member
Registered: 2013-03-25
Posts: 28

Re: [gnome3.6, systemd]NetworkManager make polkit start extremely slow

I recently installed Arch on my laptop and only installed the gnome group. NetworkManager extends my boot time with about 6 seconds. Did anyone found a solution to this?

Offline

#37 2013-06-29 19:07:53

digitalis
Member
Registered: 2012-05-08
Posts: 3

Re: [gnome3.6, systemd]NetworkManager make polkit start extremely slow

In my case it helped to delete symlink in /etc/systemd/system/multi-user.target.wants/ since I do not need network for boot.

See also here:
https://bbs.archlinux.org/viewtopic.php?id=165688

The only issue it does start only after Xfce is loaded (but I do not need network there from start either). Note I do not use login manager but CLI.

Offline

#38 2013-06-30 06:32:32

jrussell
Member
From: Cape Town, South Africa
Registered: 2012-08-16
Posts: 510

Re: [gnome3.6, systemd]NetworkManager make polkit start extremely slow

digitalis wrote:

In my case it helped to delete symlink in /etc/systemd/system/multi-user.target.wants/ since I do not need network for boot.

See also here:
https://bbs.archlinux.org/viewtopic.php?id=165688

The only issue it does start only after Xfce is loaded (but I do not need network there from start either). Note I do not use login manager but CLI.

Deleting that symlink is essentially disabling the service I think

bitcoin: 1G62YGRFkMDwhGr5T5YGovfsxLx44eZo7U

Offline

#39 2013-07-27 17:28:44

dront78
Member
From: Moscow
Registered: 2010-11-24
Posts: 47

Re: [gnome3.6, systemd]NetworkManager make polkit start extremely slow

+100500 for this bug to be fixed. Because the ModemManager and NetworkManager multi-user.target.wants are blame in the system slow boot
Especially strange the /etc/systemd/system/dbus-org.freedesktop.NetworkManager.service and /etc/systemd/system/multi-user.target.wants/NetworkManager.service are point to the same .service file. And /etc/systemd/system/dbus-org.freedesktop.ModemManager1.service with /etc/systemd/system/multi-user.target.wants/ModemManager.service too

Last edited by dront78 (2013-07-27 17:32:18)

Offline

#40 2014-10-09 17:12:27

kalsan
Member
Registered: 2011-10-10
Posts: 119

Re: [gnome3.6, systemd]NetworkManager make polkit start extremely slow

It's been a while and things have changed. Have you guys tried http://ebalaskas.gr/blog/2014/01/27/spe … boot-time/ ?
Any experiences with that? Any problems?
cheers,
Kalsan

Offline

Pages: 1 2

Board footer

Powered by FluxBB