Hello,
Recently after upgrading my kernel (via /repositories/Base:/Kernel/standard) I have had issues with the network not starting properly on bootup. The kernel is 100% SUSE-patched and behaves perfectly outside of that one issue. To get the network to “start” (DHCP issued, eth0 brought up) I have to ‘rcnetwork start’ in a shell. I’ve checked to make sure my config is right in both ifcfg-eth0 and ‘config’ for /etc/sysconfig/network, but nothing affects the outcome.
How do I get the boot scripts to bring up eth0 and issue a DHCP on startup?
Here’s the output of ‘rcnetwork start -o debug fake’:
Which network do you want to start - eth0 or wlan0?
By default, eth0 should start automatically if the cable is connected.
wlan0 is probably controlled by the network manager.
If you go to yast>network devices, you ccan first change to using the traditional if up method and saving and then go back and adjust the settings for each card in the network manager settings.
By default, eth0 should start automatically if the cable is connected.
In theory, yes.
wlan0 is probably controlled by the network manager.
I am not using NetworkManager.
If you go to yast>network devices, you ccan first change to using the traditional if up method and saving and then go back and adjust the settings for each card in the network manager settings.
I have tried to set eth0 to ‘ifplugd’ and ‘auto’ (auto is for on-boot apparently) - neither renew the IP on startup.
It is. wlan0’s hardware was just added to the machine last night - this problem has existed for weeks. eth0 has been set to ‘at boot time’ as well (that’s what ‘auto’ is in the config file). The trouble is the new kernel. The startup works fine under the stock kernel, but once it’s updated to a non-stock kernel it stops working.
There are several reasons for me to upgrade to 2.6.29+ - one primarily being support (and/or better support) for my Pinnicle HDTV TV Tuner card, as well as a few other less major reasons. I would just stay with the stock kernel, but it’s not much of a practical solution.
I’ve used Linux nearly exclusively for the past 8 years and despite my vast experience this bug has me stumped. I’ve tried everything I can, but for whatever reason it continues to not start on boot.
Here’s the exact output on boot:
Setting up (localfs) network interfaces:
lo
lo IP address: 127.0.0.1/8
IP address: 127.0.0.2/8 done
Waiting for mandatory devices: eth0 __NSC__
11 10 9 7 6 5 4 2 1 0
eth0 device: Attansic Technology Corp. L1 Gigabit Ethernet Adapter (rev b0)
eth0 DHCP4 client NOT running
eth0 is down failed
eth0 interface could not be set up until now failed
eth0 is not so much as ‘brought up’ (e.g. not listed in ifconfig) on start, let alone an IP obtained.