on every boot a n annoying start job for network manager

[vilde]

since some days every time I boot the there is a start job for network manager running, it's annoying taking between one and two minutes to complete

[devil]

Did you check the journal for errors/warnings? A new network manager came in these days.


greetz
devil

[vilde]

Code Auswählen Erweitern

root@vilde_dator:/home/vilde# journalctl  --since=today
-- Logs begin at fre 2016-03-11 11:39:29 CET, end at tis 2016-08-30 01:11:19 CEST. --
aug 30 00:02:43 vilde_dator NetworkManager[708]: <info>  [1472508163.8263] device (wlp3s0): set-hw-addr: set MAC address to CE:0D:C3:26:4C:5F (scanning)
aug 30 00:02:44 vilde_dator kernel: iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled
aug 30 00:02:44 vilde_dator kernel: iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled
aug 30 00:02:44 vilde_dator kernel: iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
aug 30 00:02:44 vilde_dator kernel: iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled
aug 30 00:02:44 vilde_dator kernel: iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled
aug 30 00:02:44 vilde_dator kernel: iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
aug 30 00:02:44 vilde_dator NetworkManager[708]: <info>  [1472508164.1845] device (wlp3s0): supplicant interface state: inactive -> disabled
aug 30 00:02:44 vilde_dator kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
aug 30 00:02:44 vilde_dator NetworkManager[708]: <info>  [1472508164.2098] device (wlp3s0): supplicant interface state: disabled -> disconnected
aug 30 00:02:44 vilde_dator NetworkManager[708]: <info>  [1472508164.2152] device (wlp3s0): supplicant interface state: disconnected -> inactive
aug 30 00:02:44 vilde_dator wpa_supplicant[7607]: wlp3s0: Reject scan trigger since one is already pending
aug 30 00:07:59 vilde_dator NetworkManager[708]: <info>  [1472508479.8268] device (wlp3s0): set-hw-addr: set MAC address to A2:FB:22:1D:D3:C6 (scanning)
aug 30 00:08:00 vilde_dator kernel: iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled
aug 30 00:08:00 vilde_dator kernel: iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled
aug 30 00:08:00 vilde_dator kernel: iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
aug 30 00:08:00 vilde_dator kernel: iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled
aug 30 00:08:00 vilde_dator kernel: iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled


[harley-peter]

Hello,

after an du 2 weeks ago I have a similar problem on my Thinkpad. Maybe it is the same problem.

Code Auswählen Erweitern

Aug 30 07:32:06 thinkpad kernel: iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-6000-6.ucode failed with error -2
Aug 30 07:32:07 thinkpad kernel: iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-6000-5.ucode failed with error -2


After this message I have to wait about 1 minute before the boot procedure continue. But all seems to works fine.

[devil]

Vilde,
I can't see anything in there to warrant such a wait.


greetz
devil

[vilde]

Some times it's much shorter, this boot the start job was over after a few seconds.

Anyway, I will go away for some days and will not be able to check this further until next weekend.

[vilde]

Still same problem, nearly every boot I have to wait 1 minit and 302 seconds for a start job for network manager.

I have tried to purge network manager and network manager gnome and then after reboot reinstall them but still same problem.

[vilde]

I'm booting my laptop several times each day and are completely bored of this "start job" so now I have purged Network Manager and are using ceni as in the good old times. 

[dieres]

I have the same problem since DU two days ago. Yes it is boaring to wait 90 sec every boot, not finding any error.

[vilde]

I have checked around and maybe it has to do with systemd and "NetworkManager-wait-online.service" but I don't understand enough toooo ehhhhh understand it. Maybe somebody who knows more can check that?

[towo]

I have seen this problem exact one time on an system @work. It was using sddm, after installing lightdm, the "waiting for networkmanager" was gone.

[melmarker]

one could disable the wait-online service -- if no dependend services require it. Solved
(services like nfs and so on)

[vilde]

I have tried this

Code Auswählen Erweitern

root@vilde_dator:/home/vilde# systemctl disable NetworkManager-wait-online.service
Removed /etc/systemd/system/network-online.target.wants/NetworkManager-wait-online.service.
root@vilde_dator:/home/vilde# but it doesn't help. How shall I disable it?

[melmarker]

ok - now we know that the Problem is not the wait-online service - so no clue, only the advice to dig a little bit deeper and find the reason why the nm-service fails.

[vilde]

ok, I have no idea if this can be to any help but first time the problem started systemd also did a start job for my second hardisk on every boot, four start jobs, one for each partition with ntfs file system and then finally the one for network manager. As this with hard disks have happen before when uuid has changed I checked fstab but uuid was the same and right so to get rid of that I put a # in front of this lines in fstab, (they are anyway not supposed to be mounted when booted in to siduction) then there was only the start job for network manager left.