plasmoid-networkmanagement

Hello
I have installed opensuse 11.4, 32bit, KDE 4.6 on an Asus eee1005HA. I connect to the internet - both wired and wireless at boot, an a small pop-up note tells me that the connection is controlled by the networkmanagement.

BUT the installed plasmoid-networkmanagement is not available in system tray and if I add the plasmoid at the desktop it reads: no network interfaces. The control tells the same.

I would like to use plasmoid for networkmanagement when travelling, and was looking forward for a working replacement to wicd, so please help me to solve this issue. Thx

Just to get a handle on this, what do these commands report about your network interfaces?

/sbin/ifconfig
/sbin/lspci -nnk

/sbin/ifconfig

eth0 Link encap:Ethernet HWaddr 90:E6:BA:83:6E:3E
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:42

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:465 errors:0 dropped:0 overruns:0 frame:0
TX packets:465 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:37246 (36.3 Kb) TX bytes:37246 (36.3 Kb)

wlan0 Link encap:Ethernet HWaddr 00:25:D3:8C:89:A7
inet addr:10.0.0.4 Bcast:10.0.0.255 Mask:255.255.255.0
inet6 addr: fe80::225:d3ff:fe8c:89a7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:34320 errors:0 dropped:0 overruns:0 frame:0
TX packets:24817 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:41219883 (39.3 Mb) TX bytes:3618634 (3.4 Mb)

and /sbin/lspci -nnk:

blah blah blah…


01:00.0 Ethernet controller [0200]: Atheros Communications AR8132 Fast Ethernet [1969:1062] (rev c0)
Subsystem: ASUSTeK Computer Inc. Device [1043:838a]
Kernel driver in use: atl1c
02:00.0 Network controller [0280]: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) [168c:002b] (rev 01)
Subsystem: AzureWave Device [1a3b:1089]
Kernel driver in use: ath9k

thanks for the interest!

I initially had the same problem. I nuked the old $HOME/.kde4, and reconfigured from scratch. I now have the network manager icon. It seems that something in the old settings was confusing KDE.

Or this could be as simple as right clicking on the system tray->system tray settings-> check the Network Management box. You have to unblock the elements of the interface first to not have it grayed out :slight_smile:

Best regards,
Greg

I tried both the solutions provided by glistwan and nrickert but the problem persists. I have now been fumbling around this issue for a couple of days with wireless on and off but never after a boot and are looking at other treads, since it seems to be a misconfiguration problem.

traditional (ifup) and networkmanager problems using KDE 11.4

I hope the efforts in this thread will solve the problem…

So what happenes when You have your network controlled by NetworkManager and use this command ?

sudo /etc/init.d/network restart

Best regards,
Greg

When I use the

code:
sudo /etc/init.d/network restart

The plasmoid-networkmanager starts up fine and shows both attached network-interfaces and I am able to connect to both. So it is apparently a start-up problem for the plasmoid-networkmanager service. How do I enable it to start at boot time? It is naturally enabled i Yast.
Best regards Tarp

I can add the following information when using the command “sudo /etc/init.d/network restart”

soren@eee1005:~> sudo /etc/init.d/network restart
root’s password:
Shutting down network interfaces:
eth0 device: Atheros Communications AR8132 Fast Ethernet (rev c0)
eth0 done
wlan0 device: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
wlan0 done
Shutting down service network . . . . . . . . . done
Starting the NetworkManager done
Connecting… 1s
waiting
soren@eee1005:~> sudo /etc/init.d/network restart
root’s password:
Shutting down the NetworkManager done
Shutting down network interfaces:
eth0 device: Atheros Communications AR8132 Fast Ethernet (rev c0)
eth0 done
wlan0 device: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
wlan0 done
Shutting down service network . . . . . . . . . done
Starting the NetworkManager done
Connecting. 29s done
soren@eee1005:~>

as you see I have to issue the command twice before I can connect - and every time I have booted :frowning: Is this a bug?

I haven’t had the NetworkManagement plasmoid in the system tray since installing 11.4 last week. I clicked on system tray > System Tray Settings > unlock widgets, but there is no NetworkManager to enable, and I don’t see it in Add Widgets. I cannot see my network settings anywhere.

Please don’t ask an elementary question, like what’s the output of ifconfig. I’m not a novice. I just want to know what happened to the plasmoid.

If there is no Network Management widget available, check that you have the plasmoid-networkmanagement package installed (I hope that you don’t find this answer too elementary :))

Thanks for your reply. I hope my question wasn’t too elementary for you. There’s a conflict when I try to install the plasmoid. Let me say that the installation of 11.4 was a fresh install from DVD, to a newly reformatted partition rather than an upgrade from my 11.3 version, with no modifications except to not format my /home partition. Is it possible the installer incorrectly thinks the plasmoid should not be installed? So I guess, in my case, the plasmoid in not installed, and cannot be installed. I see no other network manager plasmoid package, in the Yast list, that could be substituted. How can we solve this?

Here’s the conflict.txt.

NetworkManager-kde4-0.9.svn1192577-7.2.x86_64 conflicts with plasmoid-networkmanagement provided by plasmoid-networkmanagement-0.9.svn1192577-7.2.x86_64

     ] do not install plasmoid-networkmanagement-0.9.svn1192577-7.2.x86_64

     ] deinstallation of NetworkManager-kde4-0.9.svn1192577-7.2.x86_64

Well you have a choice to make: If you prefer the plasmoid (as I do), then NetworkManager-kde4 needs to be de-installed (as the package solver says is necessary).

I think it is a bug. Just to be sure create a new test user, log in as the test user and see if the behavior there is different.

Best regards,
Greg

If you have not already done so, try switching your DHCP to use “dhclient”. It is the value assigned to DHCLIENT_BIN and you can set from Yast in the sysconfig settings.

The default is “dhcpcd”. My experience is that “dhcpcd” doesn’t work if you are using WiFi and reconfiguring your network (changing which SSID you connect to). Specifically, dhcpcd seems to cache too much information. So, if I edit or switch the “ifcfg-*” file for my WiFi card, and restart the network, it shows as connected but with the IP address and routing from my previous network connection. If I use “dhclient”, I don’t run into that problem.

Many thanks to nrickert for caring solving other peoples probs…

I have done two things - upgraded to KDE 4.6 (no effect) and then changing sysconfig as nrickert suggested:

Set DHCP to use “dhclient”. It is the value assigned to DHCLIENT_BIN and you can set from Yast in the sysconfig settings.

Success!

Now the plasmoid-networkmanagement does not fail to connect or acts strange/irresponsive after boot.
The only minor issue left is that the plasmoid-networkmanagement does not connect automatically to the preferred wlan, even if its is preconfigured in the settings.
But I can live with that :wink: until the Canterbury distribution comes along lol!

I am sorry to say but the situation is back to normal - which means that plasmoid-networkmanager do not connect without console commands in my previous posts - being issued twice.:frowning:

Btw - I have tried the “test user” suggestion as well - no difference. It is like the wlan interface is not being initialized correctly at boot time or at kde-logon…?

In that case You might want to try renaming the file /etc/sysconfig/network/ifcfg-wlan0 to something else (for example ifcfg-wlan0.bak) and see what happenes when You reboot.

Best regards,
Greg

I have tried renaming the /etc/sysconfig/network/ifcfg-wlan0 file but without any change.
It seems to me that both network devices are not configured correctly at boot, and that the wlan interface is unstable during use which causes a lot of interrupts in my home network (nfs).:frowning: