I just discovered that my network is one of the last services being started. This corrupts all previous services that see only loopback. If I add the boot flag to the network service I get two big NetworkManager SIGSEVs.
as root, open the file /usr/bin/startkde
Find line “LD_BIND_NOW=” and add at the end +knetworkmanager
or execute this
sed -e ‘/LD_BIND_NOW=/!b’ -e ‘/+knetworkmanager/!s/$/ +knetworkmanager/’ /usr/bin/startkde >/tmp/startkde-intermediate
cat /tmp/startkde-intermediate >/usr/bin/startkde
When you need you network starting “normaly” (that is at reaching runlevel 3 or 5) you should use “traditional with ifup” in YaST network configuration.
Network manager is for systems where the end-user decides what connection te make (mostly on laptop like ystems wich connect often to different networks). The end-user can only do so when (s)he is loged in. Thus the network is not even started at boot.
EDIT: After posting I see beli0135’s post above. I do not know want this parameter setting is supposed to do, but I doubt it will start your network before login.
Well this is a notebook, but I need the wired network to start normally and still manage the wireless using networkmanager (or something similar).
Hm, I do not know if this knot can be untangled. You could configure your cabled one with “ifup” and that would give you network from rather early in the boot sequence (before network deamons are started). But I do not know if you can configure to use networrk manager for your wired connection at the same time. In fact I doubt because the choice is in the Global option of YaST for network config.
May be it is still possible doing this outside YaST. Configure the cabled one in /etc/sysconfig/network/ifcfg-eth0 (if eth0 is the name) and nevertheless start the network manager deamon and configuring it in a way that it “ignores” eth0 (or at least let it run if allready running, but I do not know when you decide to switch, or do you want up at the same time?)
Hm, many questions here.
One option is to use ifup for both and you need to configure wireless using wpa_supplicant…
Interestingly this worked in OpenSuSe 11.2 just fine (services started in right order and everything worked).
You did not tell which services your notebook services, thus I can not comment on that.
Using ifup and WICD, the daemon can be set up to load at boot, on my Thinkpad this means that my wireless is up by the time the desktop loads, or within 5-10 seconds after.
Clearly there is an issue here in that 11.3 does not behave in the same way as previous versions. I am having problems with Network Manager or the supplicant on T42 laptop and am having to connect to wlan using “traditional ifup” method.
The Network Manager offered me the option to create a new wireless connection but didn’t give me the correct prompts for entering ssid and hex or passphrase for security and I couldn’t see the wireless link being found anywhere.
What used to happen is that boot would run normally and then the wireless connection would be set up. (Gear wheel turning and then signal strength bars). I didn’t have any problems with other services not finding the wlan but have a very simple setup so perhaps that is why I didn’t get the problem which initiated this thread.
Meanwhile if anybody can help me get things working as they should with Network Manager I would be most grateful.
On 07/21/2010 04:06 PM, Budgie2 wrote:
> Clearly there is an issue here in that 11.3 does not behave in the same
> way as previous versions. I am having problems with Network Manager or
> the supplicant on T42 laptop and am having to connect to wlan using
> “traditional ifup” method.
> The Network Manager offered me the option to create a new wireless
> connection but didn’t give me the correct prompts for entering ssid and
> hex or passphrase for security and I couldn’t see the wireless link
> being found anywhere.
KDE or Gnome?
If KDE, it is different than 11.1, but similar to 11.2. Rather than using the
“Connect to other Network” option, select “Manage Connections” from the applet
popup. Select wireless and create the connection. If you use the scan option to
select an AP, it has the correct encryption. Be sure to use a wallet. If you do
not wish to enter a password with every bootup, create the wallet with no password.
If Gnome, can anyone else help? It should be similar, but I have not done it.
In Gnome - just clicking on the wireless icon lists all the available wireless networks… Clicking on the network of choice brings up a window where you need to enter the password/paraphrase/other encryption settings and that is it…
Many thanks for the reply. I am using KDE. My problem was there was no applet showing but I have solved the problem now and Network Manager is accessible and working.