I have recently upgraded my laptop from SuSE 11.x to 12.1. Since the upgrade, I have an issue with the boot, with network manager.
My laptop has an ethernet connection and a build-in wifi chip. The ethernet connection is normally not connected to the network, for logistics reasons.
When I boot, I get at one moment in time the following messages:
Started Network Manager
Starting Network Manager Wait Online
It then reports that the ethernet and the wlan are both down and starts waiting for either of them to go up. It keeps waiting forever (that is: I have waited myself up to 5 minutes before loosing my patience).
When I go find a network cable, move the laptop close enough to a network socket and then plug the laptop into the physical network, the ‘wait online’ function discovers that the ethernet has gone up and the boot continues. I can then unplug the network cable and login to the wlan once I’m logged-in to KDE, as per usual process.
Where can I configure that the boot process must skip waiting for the network to go online? I have checked various settings but I have not been able to find such an option.
Please let me know if I should post certain configuration files or configuration parameters.
If when I power down and the network is enabled, on the next boot there is no
delay.
If when I power down and the network is disabled, on the next boot the process
waits for the time-out on the wired connection and then the time-out on the
wireless connection. By default the time-out is set to 30 sec. A long wait.
Two possible improvements,
change the time-out delay
or
always power down with a network connection enabled.
For settings have a look in Kickoff Launcher Applications
–Network and Connectivity --Network Settings --Connection Preferences
(Possibly you need to do this with root privileges)
I have changed parameter NM_ONLINE_TIMEOUT in file /etc/sysconfig/network/config from 0 to 1 and that has worked around the problem. Now network manager waits only 1 second instead of forever.
I have not found which settings to change in “Kickoff Launcher Applications
–Network and Connectivity --Network Settings --Connection Preferences” in order to completely remove the network manager wait during boot.
I have meanwhile booted the laptop with the network cable plugged-in. Now the wired network is visible in the network manager widget.
It has allowed me to perform many different experiments, with various settings. I have tried to disable auto-connection at IP4/IP6 level using network manager widget, but it does not make a difference. Network manager waits during the boot. I have completely disabled the wired network with the widget, but still same results.
I have studied the network manager documentation and based on that, I have added following parameters to config file /etc/sysconfig/network/ifcfg-eth0 :
NM_CONTROLLED=‘no’
HWADDR=‘xx:xx:xx:xx:xx:xx’
(with xx:xx… being the MAC address), which should tell network manager to completely ignore that specific interface.
Seems to work half; the interface no longer appears in the network manager widget so some part of network manager understands that setting. However, ‘network manager wait online’ service still knows about the eth0 interface and still wants to wait for it to come online during boot, so it seems to ignore the setting.
I’m lost. Can anybody advise me how I can completely disable the ‘network manager wait online’ service? I’m not yet enough up to speed on the new systemctl stuff to figure out myself how to disable that service, without breaking dependencies that other services might have on it.
On 2011-12-17 19:26, awulms wrote:
> I’m lost. Can anybody advise me how I can completely disable the
> ‘network manager wait online’ service? I’m not yet enough up to speed on
> the new systemctl stuff to figure out myself how to disable that
> service, without breaking dependencies that other services might have on
> it.
You might try booting with systemV. F5 at boot.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
I run into exactly the same problem as described above: After upgrade, my notebook which is not connected to wired LAN waits 30 sec for NetWorker-wait-online.service until it coninues with booting. As WLAN gets configured only after a login I switched off this service with
oldcpu wrote:
> I note also there is a bug report on this issue :
> https://bugzilla.novell.com/show_bug.cgi?id=738727 where the solution
> recommended there is slightly different:
>
>> Please check /etc/sysconfig/network/config and ensure it contains :
>> NM_ONLINE_TIMEOUT=“0”
I started to see a similar problem now (hanging in the boot sequence) and
networ manager failing (although I am not using NM). The machine eventually
completes the booting and the net is reachable (because is set via the ifup
method).
It makes no difference if I boot using systemd-sysvinit or sysvinit-init.
I tried the timeout “0” above and it makes no difference. I think this
problem started since I upgraded 12.1 to KDE 4.8.1.
I am not using NetworkManager but the ifup method… should I nevertheless
enable NetworkManager:
NETWORKMANAGER=“yes” in /etc/sysconfig/network/config and then set:
NM_ONLINE_TIMEOUT=“0”
Or alternatively, can I uninstall NetworkManager safely?
And if so, would this stop the boot process that tries to launch it?
I got this one too on a wired connection, but when a changed from
traditional method with ifup to user controlled with networkmanager
it speed-up the boot time. My machine boot time is 12 seconds now.