Network Manager doesn't list wifi connections

English Network/Internet
1

Hello I have a weird problem with wifi connection.
I’m using Network Manager to manage connection and if I click on the tray icon I can see only cable connection listed and not wifi.

The weird thing is that if I do the following procedure wifi works correctly:

  1. from yast select network settings;
  2. switch to Wicked Service
    and confirm; 1. open again network settings;
  3. switch again to Network Manager
    Service; 1. confirm;
  4. Network manager icon appear again and lists correctly cable and wifi connections
    giving me the possibility to use both without issues.

When I reboot the system anyway Network manager stops listing wifi connections.
If I open the connection properties I can see the settings of the wifi but cannot connect to it since connect button is grayed out.

# nmcli d

DEVICE  TIPO      STATO        CONNESSIONE        
eth0    ethernet  collegato    Wired connection 1 
lo      loopback  non gestito  --

Network manager does not list wifi connection.

# ifconfig -a
eth0      Link encap:Ethernet  HWaddr BC:5F:F4:E7:73:91  
          inet addr:192.168.1.69  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::be5f:f4ff:fee7:7391/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:13388 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12243 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:10471673 (9.9 Mb)  TX bytes:1781830 (1.6 Mb)
          Interrupt:16 

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:65536  Metric:1
          RX packets:1107 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1107 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1 
          RX bytes:185372 (181.0 Kb)  TX bytes:185372 (181.0 Kb)

wlan1     Link encap:Ethernet  HWaddr 00:0C:F6:89:60:AB  
          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)

wlan1 is not up.

# ifconfig wlan1 up

# iwlist wlan1 scan

wlan1     Scan completed :
          Cell 01 - Address: 9C:97:26:08:F7:94
                    ESSID:"MYWIFINETWORK"
                    Protocol:IEEE 802.11bgn
                    Mode:Master
                    Frequency:2.437 GHz (Channel 6)
                    Encryption key:on
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                              24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
                              12 Mb/s; 48 Mb/s
                    Extra:wpa_ie=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (1) : TKIP
                        Authentication Suites (1) : PSK
                    Extra:rsn_ie=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : PSK
                    IE: Unknown: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
                    Signal level=100/100

From iwlist command wifi seems to be working and scans correctly my network, but even if I try restarting Network Manager Service wifi doesn’t show in available connections.

Does anybody have suggestions on how to fix this problem?

2

Hi fecam
Have you solved?

3

You don’t mention which Desktop is being used – KDE Plasma 5 or GNOME?
[HR][/HR]Assuming KDE Plasma 5 (absolutely no idea about GNOME, I’m a KDE user . . . ):
The newest KDE Plasma 5 has a human eye visibility issue, which could affect other Desktops if they are also visually similar.

  • When you click on the Network Manage icon in the KDE Plasma 5 System Tray, check top left for an almost indiscernible box:
    [LIST]
  • If it’s not filled in with a colour, click it to fill it with colour and enable the WiFi.
  • If it’s filled in with a colour, a click will remove the coloured filling and switch the WiFi off . . .

[/LIST]

4

Hi,

Same here: The plasma-nm5 only show one check box to “air plane mode”, and the wlan interface do not appper in “*nmcli device *ouput”


argiros@opensuse:~> nmcli device 
DEVICE  TYPE      STATE      CONNECTION         
eth0    ethernet  connected  Wired connection 1 
lo      loopback  unmanaged  --                 
argiros@opensuse:~>

But the device is shown in “iwconfig”


lo        no wireless extensions.

wlan0     unassociated  Nickname:"<WIFI@REALTEK>"
          Mode:Auto  Frequency=2.412 GHz  Access Point: Not-Associated   
          Sensitivity:0/0  
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

eth0      no wireless extensions.

And i can scan various ssids via “iwlist wlan scan”

When a switch to Wicked service and switchback again to Network-Manager, all work fine!
The device checkbox to enable wi-fi is showed in the plasma-nm5, i can connect to wifi via NM and the wlan0 is showed in the “nmcli device output”:


argiros@opensuse:~> nmcli device 
DEVICE  TYPE      STATE      CONNECTION         
eth0    ethernet  connected  Wired connection 1 
wlan0   wifi      connected  Ageraniotis        
lo      loopback  unmanaged  --

But if i reboot or pulloff and plugin the USB wifi card again, the same behavior happen again.

Here is de dmesg when i plugin the wifi card


 2398.997155] usb 1-1.3: new high-speed USB device number 6 using ehci-pci
 2399.090584] usb 1-1.3: New USB device found, idVendor=0bda, idProduct=8179
 2399.090595] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
 2399.090599] usb 1-1.3: Product: 802.11n NIC
 2399.090601] usb 1-1.3: Manufacturer: Realtek
 2399.090604] usb 1-1.3: SerialNumber: 00E04C0001
 2399.091514] Chip Version Info: CHIP_8188E_Normal_Chip_TSMC_D_CUT_1T1R_RomVer(0)

With the leap 42.1 gnome all worked fine.

/
obs: I’ve blacklisted the module acer_wmi, cause none linux distro had worked in my laptop with this module loaded (the wi-fi always be in soft-bock state, regardless if i use rfkill to unblock then).

I’ll install the gnome DE to test if the problem be in the plasma5 or int the leap 42.2.

sorry my bad English

Best regards.

5

I found the supposed problem: The NM logs matches with this Bug.

Any can tell me how to do a downgrade to NetworkManager version 1.0.10 please?. The zypper do not know this version in the default repositories.

Thanks!

6

I have the same problem on Leap 42.2 KDE.
Until a patch is released I created a systemd service that switches to wicked and then back to NM.

[Unit]
Description=Fix for Network Manager
After=NetworkManager.service
After=suspend.target

[Service]
Type=oneshot
ExecStart=/usr/bin/systemctl stop NetworkManager.service ; /usr/bin/systemctl start wickedd.service wicked.service ; /usr/bin/systemctl stop wickedd.service wicked.service ; /usr/bin/systemctl start NetworkManager.service 

[Install]
WantedBy=multi-user.target
WantedBy=suspend.target

Save it as something.service, place it in /etc/systemd/system/ and enable it.
Not a real fix but it works for me.

7

Thank you for the tip.

Work greats for me too! I just change the default network system to wicked.service. So the systemd script just need stop the wicked e start the NM once.

8

cross reference: https://forums.opensuse.org/showthread.php/521744-Intel-Centrino-Advanced-N-6200-2x2-AGN-no-wlan-ap-s-found

tried to connect to an AP via nmcli in terminal

nmcli con up YOURAPNAME


Error: Connection activation failed: No suitable device found for this connection.
9

listed status with

systemctl status NetworkManager.service -l


NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled)
   Active: active (running) since Sat 2016-12-17 12:15:33 CET; 9min ago
 Main PID: 10648 (NetworkManager)
   CGroup: /system.slice/NetworkManager.service
           └─10648 /usr/sbin/NetworkManager --no-daemon

Dec 17 12:22:46 PCNAME NetworkManager[10648]: <warn>  Failed to acquire wpa_supplicant proxy: (Error calling StartServiceByName for fi.w1.wpa_supplicant1: GDBus.Error:org.freedesktop.systemd1.LoadFailed: Unit wpa_supplicant.service failed to load: No such file or directory.)

ll /var/run/ | grep wpa → nothing found

searched for wpa_supplicant

locate wpa_supp


/etc/wpa_supplicant
/etc/dbus-1/system.d/wpa_supplicant.conf
/etc/logrotate.d/wpa_supplicant
/etc/systemd/system/multi-user.target.wants/wpa_supplicant.service
/etc/wpa_supplicant/wpa_supplicant.conf
/usr/lib/systemd/system/dbus-fi.w1.wpa_supplicant1.service
/usr/lib/systemd/system/wpa_supplicant@.service
/usr/sbin/rcwpa_supplicant
/usr/sbin/wpa_supplicant
/usr/share/dbus-1/system-services/fi.w1.wpa_supplicant1.service

cat /usr/lib/systemd/system/dbus-fi.w1.wpa_supplicant1.service


[Unit]
Description=WPA Supplicant daemon (interface %i)
Before=network.target
After=dbus.service

[Service]
Type=dbus
BusName=fi.w1.wpa_supplicant1
ExecStart=/usr/sbin/wpa_supplicant -i%i -c /etc/wpa_supplicant/wpa_supplicant.conf -u -f /var/log/wpa_supplicant.log

[Install]
WantedBy=multi-user.target

cat /usr/lib/systemd/system/wpa_supplicant@.service


[Unit]
Description=WPA Supplicant daemon (interface %i)
Before=network.target
After=dbus.service

[Service]
Type=dbus
BusName=fi.w1.wpa_supplicant1
ExecStart=/usr/sbin/wpa_supplicant -i%i -c /etc/wpa_supplicant/wpa_supplicant.conf -u -f /var/log/wpa_supplicant.log

[Install]
WantedBy=multi-user.target

started wpa_supplicant in Konsole with (replaced -i%i by -i wlan1 → a blank between -i and wlan1)
/usr/sbin/wpa_supplicant -i wlan1 -c /etc/wpa_supplicant/wpa_supplicant.conf -u -f /var/log/wpa_supplicant.log

creates:

ll /var/run/ | grep wpa


drwxr-x---  2 root  wheel   60 17. Dez 12:54 wpa_supplicant

ll /var/run/wpa_supplicant/


total 0
srwxrwx--- 1 root wheel 0 Dec 17 12:54 wlan1

restarted NetworkManager-Service
systemctl restart NetworkManager.service

and now NM lists the available AP’s

Maybe the ExecStart-Parameter needs to look like (a blank between -i and %i forgotten?)
/usr/sbin/wpa_supplicant -i %i -c /etc/wpa_supplicant/wpa_supplicant.conf -u -f /var/log/wpa_supplicant.log
instead of
/usr/sbin/wpa_supplicant -i%i -c /etc/wpa_supplicant/wpa_supplicant.conf -u -f /var/log/wpa_supplicant.log

in these two files:
/usr/lib/systemd/system/wpa_supplicant@.service
/usr/lib/systemd/system/dbus-fi.w1.wpa_supplicant1.service

?

10

changed this two files, but

systemctl restart wpa_supplicant


Failed to restart wpa_supplicant.service: Unit wpa_supplicant.service failed to load: No such file or directory.

wpa_supplicant complains about missing file.

locate wpa_supplicant.service


/etc/systemd/system/multi-user.target.wants/wpa_supplicant.service

cat /etc/systemd/system/multi-user.target.wants/wpa_supplicant.service


cat: /etc/systemd/system/multi-user.target.wants/wpa_supplicant.service: No such file or directory

is there a link needed ?

/usr/lib/systemd/system/dbus-fi.w1.wpa_supplicant1.service -> /usr/lib/systemd/system/dbus-fi.w1.wpa_supplicant1.service
or
/usr/lib/systemd/system/dbus-fi.w1.wpa_supplicant1.service -> /usr/lib/systemd/system/wpa_supplicant@.service

11

Whenever you modify a service configuration file, you have to reload the systemd service.

I wrote a Wiki page that summarizes…

https://en.opensuse.org/User:Tsu2/systemd_commands

TSU

12

I had a similar issue with the TP-Link Archer AC600 and openSUSE Leap 42.2.

The weird thing is that it actually worked fine with kernel 4.4.62-18.6. And I can still make it work by booting this kernel.

Now as soon as I boot a kernel >= 4.4.73-18.17, NetworkManager-1.0.12-4.3.1.x86_64 doesn’t recognize the wifi interface any more.
Interface appears in “ifconfig -a” but is down.
“nmcli d” doesn’t show it.

The proposed workaround with wicked did NOT work for me.

However my solution is similar:

  1. “systemctl stop network”
  2. Run wpa_supplicant with a properly formatted config
  3. While wpa_supplicant is still running and connected, run “systemctl start network”. At this point NetworkManager starts listing the access points.
  4. Kill wpa_supplicant
  5. Continue using network manager

It almost looks like the driver / kernel / device is in a non-initialized state and needs a nudge from wpa_supplicant (or wicked) to activate itself.

And strange that this nudge isn’t needed for older kernels.

I read above that this bug might be fixed in more recent NetworkManager versions but looking at packages from LEAP 42.3 seems to show the same version.
So either the fix needs to be backported or a higher version of NetworkManager should be provided by the distro.

Thoughts ? Should this be reported in the bug tracker in the hope to get a backport ?

13

So I went ahead and made a bug report: https://bugzilla.suse.com/show_bug.cgi?id=1050959

14

I’ve tried with the patch in a locally patched OBS folder based on https://build.opensuse.org/package/show/openSUSE:Leap:42.2/NetworkManager.

Unfortunately it doesn’t seem to work for me, the symptoms are the same as before.

15

hi,

just for info :

Thanks to those involved

The internal network card, BC43124, is now detected and connects

This was after install of the following packages,
Its the first time of operation since updates from Kernel-4.4.71 with wl.ko driver
(note this driver no longer compiles)

broadcom-wl-6.30.223.271-7.4.x86_64 Build Time: So 16 Jul 2017 13:15:29 CEST
broadcom-wl-kmp-default-6.30.223.271_k4.4.76_1-7.4.x86_64 Build Time: So 16 Jul 2017 13:15:29 CEST

Thanks again!

System: Kernel-4.4.73-1-default x86_64 (64 bit) KDE Plasma 5.8.7 openSUSE Leap 42.3

16

(note this driver no longer compiles)

In Leap 42.3 the driver compiles only with a Patch, because the Kernel from Leap 42.3 has some Features of higher Kernel-Versions…

17

I had a similar problem too, on Leap 42.3, kernel 4.4, card[FONT=monospace] Intel Dual Band Wireless AC 3165[/FONT]

This worked for me:

Do # rfkill list and see I you find “acer-wireless”, which was the problem for me.

I had that log:
[FONT=monospace]# rfkill list
0: acer-wireless: Wireless LAN
Soft blocked: yes
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
21: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
[/FONT]
If you don’t have any log install rfkill by doing that command: # zypper in rfkill

Then do as explained here:
http://karim-ouda.blogspot.ca/2011/11/wifi-now-disabled-by-radio-killswitch.html

Here’s a copy of the procedure:

If you found “acer-wireless” then this may be the conflicting module, do the following to remove this module

sudo rmmod acer-wmi
Now the wireless should work

I didn’t need to do that one] You may also need to execute this command **rfkill unblock all
**
To make this change permanent ( disable acer-wmi module forever ) do the following
1- sudo gedit /etc/modprobe.d/blacklist.conf
2- add the following line at the end of the file blacklist acer-wmi
Or do as I did because that command didn’t work for me: open the root’s directory, clic on racine, then etc, then modprobe.d, then open blacklist.conf and add the line “blacklist acer-wmi” at the end of the file.

Thanks to Alionet’s forum
https://www.alionet.org/showthread.php?33401-Probl�me-de-wifi-avec-Intel-Dual-Band-Wireless-AC-3165