I have a fresh installation of OpenSuse 12.4 and the boot process hangs until I plug in a lan cable. I had my lan connected during the installation, so maybe this somehow related to the boot problem. I have to say live KDE cd boots up fine without any lan.
Here is my boot log fragment. I’ve plugged in the cable after the message in bold, and boot process resumed. Note time difference 23:14:22 - 23:14:55
Nov 18 23:14:22 localhost dbus[969]: [system] Activating service name='fi.w1.wpa_supplicant1' (using servicehelper)
Nov 18 23:14:22 localhost dbus-daemon[969]: dbus[969]: [system] Activating service name='fi.w1.wpa_supplicant1' (using servicehelper)
Nov 18 23:14:22 localhost dbus-daemon[969]: /etc/NetworkManager/dispatcher.d/netcontrol_services: line 37: scripts/ifhostname-services: No such file or directory
Nov 18 23:14:22 localhost kernel: 14.093292] sky2 0000:45:00.0: eth0: enabling interface
Nov 18 23:14:22 localhost kernel: 14.094245] ADDRCONF(NETDEV_UP): eth0: link is not ready
Nov 18 23:14:22 localhost dbus[969]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'
Nov 18 23:14:22 localhost dbus-daemon[969]: dbus[969]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'
**Nov 18 23:14:22 localhost kernel: 14.130142] NET: Registered protocol family 17**
Nov 18 23:14:55 localhost kernel: 46.555363] sky2 0000:45:00.0: eth0: Link is up at 100 Mbps, full duplex, flow control both
Nov 18 23:14:55 localhost kernel: 46.556574] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Nov 18 23:14:55 localhost dhclient: Internet Systems Consortium DHCP Client 4.2.2
Nov 18 23:14:55 localhost dhclient: Copyright 2004-2011 Internet Systems Consortium.
Nov 18 23:14:55 localhost dhclient: All rights reserved.
Nov 18 23:14:55 localhost dhclient: For info, please visit https://www.isc.org/software/dhcp/
Nov 18 23:14:55 localhost dhclient:
Nov 18 23:14:55 localhost dhclient: Listening on LPF/eth0/70:5a:b6:8f:a6:91
I guess I wonder if Network Manager was enabled? I suggest you visit YaST (Enter Root User Password) / Network Devices / Network Settings /Global Options Tab and set the Bullet (top Left) for “User Controlled with NetworkManager” and pick OK on the bottom right. This should provide a working network icon in the bottom right of the KDE desktop icon tray. If this does not allow you to boot without a network, you can disable networking in the network manager before you shut down.
go the exact same problem on laptop running 12.1 … quite annoying
And can you say you have followed my suggestion?
I suggest you visit YaST (Enter Root User Password) / Network Devices / Network Settings /Global Options Tab and set the Bullet (top Left) for “User Controlled with NetworkManager” and pick OK on the bottom right.
yes the laptop runs network manager although I haven’t tried disabling the network at shutdown. I don’t consider this a viable solution… booting should just work! it appears some service waits indefinitely on network to come up
So you need to tell us the hardware in which this is a problem. In Linux, most hardware is detected and activated by the Linux kernel modules. In some cases, there is firmware that may need to be installed. Most hardware is supported by individuals determining how to make the hardware work without help from the company that actually made it. When direct hardware company support is not provided to Linux (as it is with Windows), hardware operation can be very spotty at best. It is not the fault of the Linux kernel developers that this problem should exist. None the less, we all do the very best we can to help and we start off by needing to know the exact wireless lan hardware chipset that is not working.
I have had similar troubles recently just as the original poster described. I am using NetworkManager on my laptop (not the traditional ifup method)
I’ve resolved it but I don’t know much about it… Here are the steps (I’m not sure which one actually did the trick or maybe its a series of steps combined that did the trick):
yast2 lan - delete all configurations (yes, you’ll need to temporarily change from NetworkManager to Traditional method), switch back to NetworkManager and click OK to save the changes
On boot, at grub screen, hit F5 to change from default to SystemV
yast2 runlevel - go to expert mode, unchecked 3 and 5 from network and network-remotefs
Today, I tried to boot up with the default systemd and it worked! Therefore, Step (2) above may be optional.
Good luck and let me know if this works for you too.
Having the same problem I found that disabling network-remotefs from startup was enough to allow my laptop to boot and not wait until I plugged a network cable in.
Hi, in fact no automation is needed here. To disable network-remotefs, you can use either ‘yast2 runlevel’ or chkconfig network-remotefs off.
One interesting thing I’ve just found out: to solve this issue (opensuse wait for network cable plugged to continue boots up), I have disabled and RE-enabled these services:
network
network-remotefs
random
4.SuSEfirewall2_init
5.SuSEfirewall2_setup
To disable, use ‘yast2 runlevel’, Expert Mode, and uncheck all checked numbers in each service (write down the value for each service). Once finished, do a reboot with network cable UNPLUGGED. Opensuse should boots up fine.
Then again, use ‘yast2 runlevel’, Expert Mode, and check the corresponding runlevel checkboxes for all these services. Then do a reboot with network cable UNPLUGGED. OpenSUSE should still boots up FINE.
I have tried on 2 different laptops, and they are working properly. So I guess this is stable workaround.
On 2011-11-21 02:46, vanista wrote:
> is there a way to get more verbose logging from the network service
> starting up? dmesg obviously doesn’t tell what’s waiting on what…
Add “systemd.log_level=debug systemd.log_target=kmsg” when booting.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Here are the steps (I’m not sure which one actually did the trick or maybe its a series of steps combined that did the trick):