Network Manager cannot see wireless adapter, ifup works OK in KDE.

openSUSE 11.4
KDE 4.6.3 and now 4.6.4
Netbook ASUS eeePC 1000


The problem began after discharging of battery. Power Management made changes profiles, first to Powersave then to Aggressive powersave.
Now Network Manager cannot see wireless card (wlan0) but can see Ethernet card (eth0). In “Configure Desktop -> Network Setting -> Network Connections -> Wireless” the option “Scan” isn’t available.
Menu on right click on icon “Manage Connection” in tray shows that the option “Enable wireless” is grey and isn’t active.
When I turn on in YAST “Traditional method with ifup” wireless card works OK, but it isn’t suitable for me, because there are many secure wireless networks which are needed for me with quick toggle between.
How can I restore a work of Network Manager? What can I do?

On 06/26/2011 04:06 PM, jp73 wrote:
>
> openSUSE 11.4
> KDE 4.6.3 and now 4.6.4
> Netbook ASUS eeePC 1000
> _______________________
> The problem began after discharging of battery. Power Management made
> changes profiles, first to Powersave then to Aggressive powersave.
> Now Network Manager cannot see wireless card (wlan0) but can see
> Ethernet card (eth0). In “Configure Desktop -> Network Setting ->
> Network Connections -> Wireless” the option “Scan” isn’t available.
> Menu on right click on icon “Manage Connection” in tray shows that the
> option “Enable wireless” is grey and isn’t active.
> When I turn on in YAST “Traditional method with ifup” wireless card
> works OK, but it isn’t suitable for me, because there are many secure
> wireless networks which are needed for me with quick toggle between.
> How can I restore a work of Network Manager? What can I do?

Is the wireless device seen in the output of ‘/sbin/lspci -nnk’? If not, it is
not possible to use the device with either ifup or NetworkManager. Perhaps the
BIOS disabled it when the aggressive powersave mode was entered and you need to
enable it there.

Thank You. The wireless device is seen in the output of lspci -nnk:

...
01:00.0 Network controller [0280]: RaLink RT2860 [1814:0781]
        Subsystem: RaLink Device [1814:0781]
        kernel driver in use: rt2860
...

Wi-Fi works in ifup without problem, but doesn’t work with Network Manager.

On 06/27/2011 11:36 AM, jp73 wrote:
>
> Thank You. The wireless device is seen in the output of lspci -nnk:
>
> Code:
> --------------------
> …
> 01:00.0 Network controller [0280]: RaLink RT2860 [1814:0781]
> Subsystem: RaLink Device [1814:0781]
> kernel driver in use: rt2860
> …
>
> --------------------
>
> Wi-Fi works in ifup without problem, but doesn’t work with Network
> Manager.

Are you using KDE? If so, I find that knetworkmanager sometimes has a problem
with enabling wireless. If you change back to NM and run the following commands,
does it help?


killproc knetworkmanager
knetworkmanager > /dev/null 2>&1 &

For KDE, you might also try switching to the NetworkManager-Gnome applet, also
known as nm-applet, or the KDE plasmoid NM applet.

Yes, it helps.
After I have made these commands, Network Manager was run, the wireless connection was established.
What was the cause the problem occurred? Previously, Network Manager worked fine in KDE. I’d like it.
This method is suitable for my conditions.
Maybe the problem is in the configuration files?
What solution would you suggest in this case?


For KDE, you might also try switching to the NetworkManager-Gnome applet, also
known as nm-applet, or the KDE plasmoid NM applet.

OK, thanks. I’ll try to test these applets later.

It’s not that NetworkManager is not working :slight_smile: this is not dependent on the desktop You’re using. It’s that the graphical front ends for NetworkManager sometimes cause problems. I assume You’re using knetworkmanager as the front end, which is the default on openSUSE. I would recommend switching to the plasmoid as it works much better for me and many other people and it is also a native KDE application. Installation is as easy as typing one zypper command. Don’t remember the exact name of the package but search for something like plasmoid-networkmanagement.

This will also uninstall knetworkmanager in the process. NetworkManager will stay untouched :slight_smile:

Best regards,
Greg

It’s not that NetworkManager is not working this is not dependent on the desktop You’re using. It’s that the graphical front ends for NetworkManager sometimes cause problems.

Thanks a lot for the explanation. I’m very glad. I’ll try different plasmoids to select the most suitable.
Would you like yet to help me:

  1. When I run commands for restart of the Network Manager, his new front end is became different from a previous front end. It’s very interesting, why?
  2. Now the network connection doesn’t establish automatically after reboot or after a sleeping mode. First I need to mark “Enable networking”.
    How can I change this setting? NOTE: there is a mark “Connect automatically” in “Network Settings” of my wireless network.

Excuse me, I too molest you. >:(

So which one are You using at the moment ? the plasmoid or knetworkmanager ?

What is the command You use to restart NetworkManager ?
What is the output when using the command ?

Best regards,
Greg

The commands are (this advice from lwfinger - see posts above):

killproc knetworkmanager
knetworkmanager > /dev/null 2>&1 &

Output: the Network Manager runs successfully with another icon and with another interface.
New front end same as old one, but some another. It’s not important, it is good for me too but I interest to know why.
More importantly to do automatic connect to preferred network after turn on, reboot and after waking up from sleep mode.

“New front end same as old one, but some another” what does this mean ? :slight_smile:

Here’s the profile that starts automatically for me as configured in the plasmoid (sorry for polish) the checkbox that is checked says “connect automatically” :
SUSE Paste

Be sure that on all the other wireless profiles, You have got configured, connect automatically is unchecked.
To get a better idea of what’s actually happening look in the logs :

/var/log/NetworkManager

Please don’t ask my why knetworkmanager is working differently from the plasmoid or gnome networkmanager apple because I’ve got no idea :slight_smile:

Best regards,
Greg

OK, Greg.
There is only one profile of network connection in “Network Settings”. Check-box “Connect automatically” is marked. Unfortunately, it doesn’t work.
Check-box “System connection” is gray and it isn’t possible to mark it. What is its function?

As far as I know this function allows for the connection to be active even when You will log out from the desktop. Without this option checked once You log out from the desktop You lose the connection. It’s most likely grayed out for You because I have KDE 4.6.4 and the version of my plasmoid is higher :

~> rpm -qa plasmoid-networkmanagement
plasmoid-networkmanagement-0.9.1git20110503-4.1.i586

In order to get the one I’m using You would have to upgrade your whole KDE to the latest stable version which I don’t recommend unless You feel comfortable with repository management. Anyway, connecting automatically worked for me with the default openSUSE KDE which is version 4.6.0 so I don’t think this is the problem.

Best regards,
Greg

Greg, thanks for help and advices. I’ll test different plasmoids for NM now.