No Networks after Upgrade to 13.2 (Realtek)

I have spent some time trying to figure this out, but have gotten nowhere. I am hoping someone here can help! Everything was working fine unitl I upgraded a few days ago. I used an old 13.1 DVD to perform a clean install, updated it, then performed an online distro upgrade. Now, I am unable to see any wireless connections.

First off, the hardware is detected and the kernel module is loaded.


$ sudo lspci -nnk
. . .
06:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723AE PCIe Wireless Network Adapter [10ec:8723]
        Subsystem: Realtek Semiconductor Co., Ltd. Device [10ec:0726]
        Kernel driver in use: rtl8723ae
        Kernel modules: rtl8723ae


$ sudo lsmod | grep rtl8723ae

rtl8723ae             160539  0
. . .

I performed the instructions from the release notes to switch to NetworkManager from wicked.


$ systemctl status wickedd NetworkManager

wickedd.service - wicked network management service daemon
   Loaded: loaded (/usr/lib/systemd/system/wickedd.service; disabled)
   Active: inactive (dead)


NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled)
   Active: active (running) since Sun 2014-11-16 02:38:44 EST; 15min ago
 Main PID: 3828 (NetworkManager)
   CGroup: /system.slice/NetworkManager.service
           ├─3828 /usr/sbin/NetworkManager --no-daemon
           └─3887 /sbin/dhclient -d -sf /usr/lib/nm-dhcp-helper -pf /var/run/dhclient-enp5s0f2.pid -lf /var/lib/NetworkManager/dhclient-c5326a67-5bc0-435f-b888-e85aafa4a5f3-enp5s0f2.lease -cf /var/lib/NetworkManager/dhclient-enp5s0f2.conf enp5s0f2

Nov 16 02:39:00 wander.site NetworkManager[3828]: XMT: Info-Request on enp5s0f2, interval 16510ms.
Nov 16 02:39:00 wander.site dhclient[3888]: XMT: Info-Request on enp5s0f2, interval 16510ms.
Nov 16 02:39:17 wander.site NetworkManager[3828]: XMT: Forming Info-Request, 31350 ms elapsed.
Nov 16 02:39:17 wander.site NetworkManager[3828]: XMT: Info-Request on enp5s0f2, interval 33510ms.
Nov 16 02:39:17 wander.site dhclient[3888]: XMT: Info-Request on enp5s0f2, interval 33510ms.
Nov 16 02:39:30 wander.site NetworkManager[3828]: <warn> (enp5s0f2): DHCPv6 request timed out.
Nov 16 02:39:31 wander.site NetworkManager[3828]: <info> (enp5s0f2): canceled DHCP transaction, DHCP client pid 3888
Nov 16 02:39:31 wander.site NetworkManager[3828]: <info> Activation (enp5s0f2) Stage 5 of 5 (IPv6 Commit) scheduled...
Nov 16 02:39:31 wander.site NetworkManager[3828]: <info> Activation (enp5s0f2) Stage 5 of 5 (IPv6 Commit) started...
Nov 16 02:39:31 wander.site NetworkManager[3828]: <info> Activation (enp5s0f2) Stage 5 of 5 (IPv6 Commit) complete.

Nothing appears wrong with the interface.


$ sudo iwconfig

wlp6s0    IEEE 802.11bgn  ESSID:off/any
          Mode:Managed  Access Point: Not-Associated   Tx-Power=20 dBm
          Retry short limit:7   RTS thr=2347 B   Fragment thr:off
          Encryption key:off
          Power Management:off

But nothing appears in the plasma network manager applet (KDE). And nothing appears when I try to scan from the command line either.


$ /usr/sbin/iwlist wlp6s0 scan

wlp6s0    No scan results

When I do this, nothing comes up in either journactl or dmesg, but here is what they print when I restart the entire network stack.


$ journalctl -f

Nov 16 03:00:48 wander.site NetworkManager[5620]: <info> caught signal 15, shutting down normally.
Nov 16 03:00:48 wander.site NetworkManager[5620]: <info> (enp5s0f2): device state change: unavailable -> unmanaged (reason 'removed') [20 10 36]
Nov 16 03:00:48 wander.site NetworkManager[5620]: <info> (wlp6s0): device state change: disconnected -> unmanaged (reason 'removed') [30 10 36]
Nov 16 03:00:48 wander.site kernel: IPv6: ADDRCONF(NETDEV_UP): enp5s0f2: link is not ready
Nov 16 03:00:48 wander.site NetworkManager[5620]: (NetworkManager:5620): GLib-CRITICAL **: Source ID 26 was not found when attempting to remove it
Nov 16 03:00:48 wander.site NetworkManager[5620]: <info> exiting (success)
Nov 16 03:00:48 wander.site NetworkManager[5915]: <info> NetworkManager (version 0.9.10.0) is starting...
Nov 16 03:00:48 wander.site NetworkManager[5915]: <info> Read config: /etc/NetworkManager/NetworkManager.conf
Nov 16 03:00:48 wander.site NetworkManager[5915]: <info> WEXT support is enabled
Nov 16 03:00:48 wander.site NetworkManager[5915]: <info> VPN: loaded org.freedesktop.NetworkManager.vpnc
Nov 16 03:00:48 wander.site NetworkManager[5915]: <info> VPN: loaded org.freedesktop.NetworkManager.openvpn
Nov 16 03:00:48 wander.site NetworkManager[5915]: <info> VPN: loaded org.freedesktop.NetworkManager.pptp
Nov 16 03:00:48 wander.site NetworkManager[5915]: <info> Loaded plugin ifcfg-suse: (C) 2008 Novell, Inc.  To report bugs please use the NetworkManager mailing list.
Nov 16 03:00:48 wander.site NetworkManager[5915]: <info> Loaded plugin keyfile: (c) 2007 - 2013 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Nov 16 03:00:48 wander.site NetworkManager[5915]: <info> monitoring kernel firmware directory '/lib/firmware'.
Nov 16 03:00:48 wander.site NetworkManager[5915]: <info> rfkill1: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.3/0000:06:00.0/ieee80211/phy0/rfkill1) (driver rtl8723ae)
Nov 16 03:00:48 wander.site NetworkManager[5915]: <info> WiFi hardware radio set enabled
Nov 16 03:00:48 wander.site NetworkManager[5915]: <info> WWAN hardware radio set enabled
Nov 16 03:00:48 wander.site NetworkManager[5915]: <info> Loaded device plugin: /usr/lib64/NetworkManager/libnm-device-plugin-wifi.so
Nov 16 03:00:48 wander.site NetworkManager[5915]: <info> Loaded device plugin: /usr/lib64/NetworkManager/libnm-device-plugin-wwan.so
Nov 16 03:00:48 wander.site NetworkManager[5915]: <info> Loaded device plugin: /usr/lib64/NetworkManager/libnm-device-plugin-bluetooth.so
Nov 16 03:00:48 wander.site NetworkManager[5915]: <info> Loaded device plugin: /usr/lib64/NetworkManager/libnm-device-plugin-adsl.so
Nov 16 03:00:48 wander.site NetworkManager[5915]: <info> WiFi enabled by radio killswitch; enabled by state file
Nov 16 03:00:48 wander.site NetworkManager[5915]: <info> WWAN enabled by radio killswitch; enabled by state file
Nov 16 03:00:48 wander.site NetworkManager[5915]: <info> WiMAX enabled by radio killswitch; enabled by state file
Nov 16 03:00:48 wander.site NetworkManager[5915]: <info> Networking is enabled by state file
Nov 16 03:00:48 wander.site sudo[5911]: pam_unix(sudo:session): session closed for user root
Nov 16 03:00:48 wander.site NetworkManager[5915]: <info> (lo): link connected
Nov 16 03:00:48 wander.site NetworkManager[5915]: <info> (lo): carrier is ON
Nov 16 03:00:48 wander.site NetworkManager[5915]: <info> (lo): new Generic device (driver: 'unknown' ifindex: 1)
Nov 16 03:00:48 wander.site NetworkManager[5915]: <info> (lo): exported as /org/freedesktop/NetworkManager/Devices/0
Nov 16 03:00:48 wander.site NetworkManager[5915]: <info> (enp5s0f2): carrier is OFF
Nov 16 03:00:48 wander.site NetworkManager[5915]: <info> (enp5s0f2): new Ethernet device (driver: 'r8169' ifindex: 2)
Nov 16 03:00:48 wander.site NetworkManager[5915]: <info> (enp5s0f2): exported as /org/freedesktop/NetworkManager/Devices/1
Nov 16 03:00:48 wander.site NetworkManager[5915]: <info> (enp5s0f2): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Nov 16 03:00:48 wander.site kernel: r8169 0000:05:00.2 enp5s0f2: link down
Nov 16 03:00:48 wander.site kernel: IPv6: ADDRCONF(NETDEV_UP): enp5s0f2: link is not ready
Nov 16 03:00:48 wander.site NetworkManager[5915]: <info> (enp5s0f2): preparing device
Nov 16 03:00:48 wander.site NetworkManager[5915]: <info> (enp5s0f2): created default wired connection 'Wired connection 1'
Nov 16 03:00:48 wander.site NetworkManager[5915]: <info> (wlp6s0): using nl80211 for WiFi device control
Nov 16 03:00:48 wander.site NetworkManager[5915]: <info> (wlp6s0): driver supports Access Point (AP) mode
Nov 16 03:00:48 wander.site NetworkManager[5915]: <info> (wlp6s0): new 802.11 WiFi device (driver: 'rtl8723ae' ifindex: 3)
Nov 16 03:00:48 wander.site NetworkManager[5915]: <info> (wlp6s0): exported as /org/freedesktop/NetworkManager/Devices/2
Nov 16 03:00:48 wander.site NetworkManager[5915]: <info> (wlp6s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Nov 16 03:00:49 wander.site kernel: IPv6: ADDRCONF(NETDEV_UP): wlp6s0: link is not ready
Nov 16 03:00:49 wander.site NetworkManager[5915]: <info> (wlp6s0): preparing device
Nov 16 03:00:49 wander.site NetworkManager[5915]: <info> use BlueZ version 5
Nov 16 03:00:49 wander.site NetworkManager[5915]: <info> ModemManager available in the bus
Nov 16 03:00:49 wander.site NetworkManager[5915]: <info> (wlp6s0) supports 4 scan SSIDs
Nov 16 03:00:49 wander.site NetworkManager[5915]: <info> (wlp6s0): supplicant interface state: starting -> ready
Nov 16 03:00:49 wander.site NetworkManager[5915]: <info> (wlp6s0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Nov 16 03:00:49 wander.site NetworkManager[5915]: <info> (wlp6s0): supplicant interface state: ready -> disconnected
Nov 16 03:00:49 wander.site NetworkManager[5915]: <info> (wlp6s0) supports 4 scan SSIDs
Nov 16 03:00:50 wander.site NetworkManager[5915]: <info> (wlp6s0): supplicant interface state: disconnected -> inactive
Nov 16 03:00:53 wander.site NetworkManager[5915]: <info> startup complete


$ dmesg

 1570.337924] IPv6: ADDRCONF(NETDEV_UP): enp5s0f2: link is not ready
 1570.719145] IPv6: ADDRCONF(NETDEV_UP): wlp6s0: link is not ready

I do not see anything particularly glaring there either. I cannot find any other way to diagnose the problem, so any help would be greatly appreicated! I am at least still able to connect with a cable, but I am feeling rather tethered at the moment :slight_smile:

Thanks!

Searching forums for something similar to my experience. I have discovered

  • Wi-Fi is working fine with Network Manager on a fresh 13.2 install
  • Wi-Fi is working fine with ifup/ifdown (disable installation of wicked, to retain ) when upgrading from 13.1 to 13.2.
  • I can’t get W-Fi to work at all with wicked on 13.2

I have tried 2 adapters. A built in Broadcom 4312 (requires broadcom_wl from Packman Repository) and a Realtek USB device (badged as Belkin)

lspci →

03:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)

lsusb →

Bus 005 Device 005: ID 050d:815f Belkin Components F5D8053 N Wireless USB Adapter v6000 [Realtek RTL8192SU]

If I attempt to configure the BCM4312 manually using iwconfig, I get complaints about invalid Mac addresses.

[The main issue I have with network manager is that someone has to log in to activate the network. Somewhat awkward for remote maintenance]

Configure it as “System connection” (“Allow all users to connect” or similar). It will then be established during boot already, without anybody logging in.

Err thanks … except it doesn’t appear to be as simple as that (looking at other threads to find out why … basically I can’t connect until I have used nm-applet; even nmcli doesn’t appear to want to play).

Is Wicked meant to handle wi-fi?

Not to be a jerk, but could you kindly not completely derail my thread here? It seems like your issue is completely unrelated to the one I am seeing, and I really could use some help here, but now it is completely off topic.

Much appreciated.

On Sun 16 Nov 2014 03:46:01 PM CST, aehall wrote:

wolfi323;2676488 Wrote:
> Configure it as “System connection” (“Allow all users to connect” or
> similar). It will then be established during boot already, without
> anybody logging in.

Err thanks … except it doesn’t appear to be as simple as that (looking
at other threads to find out why … basically I can’t connect until I
have used nm-applet; even nmcli doesn’t appear to want to play).

Is Wicked meant to handle wi-fi?

Hi
Yes, via YaST Network Settings, you need to set to use wicked, then
configure the interface and add your wireless key etc.


Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.28-4-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

Of course it is that simple. I’m using it that way since years. If “automatically connect” is enabled you do not need nmcli or any applet, the connection is established at boot time automatically.

But I agree with protean, you shouldn’t have hijacked his thread with your (different) problem in the first place.
Unfortunately I don’t really have an idea regarding that problem.
Do you have “kernel-firmware” installed?

As you say yourself, the driver seems to be loaded correctly.

Maybe you should file a bug report?
But first check that wireless is enabled in the network applet, and “airplane mode” is disabled.
And maybe try to setup a connection in the connection editor, try switching to a “system connection” as well, this seems to help sometimes with strange problems.

Thanks for the response!

I wouldn’t even know where to file a bug report - I’m not sure at what layer in the stack the problem is or how to even go about figuring that out. I might try bringing it up on the Factory mailing list. Do you have any suggestion on where else I should post this?. I messed around with rfkill, disabled IPv6, and tried updating to Tumbleweed, all to no avail. I tried the various suggestions from the Arch wireless wiki article ( https://wiki.archlinux.org/index.php/Wireless_network_configuration#Realtek ), but that didn’t help.

I think I will follow your suggestion and try disabling NetworkManager completely. Wicked wouldn’t even bring up the interfaces, so that seems hopeless. I will see if I can get things working completely unmanaged. I am also going to grab some DVDs this week and try a fresh install. I would hate for this to be the death knell that sends me off to another distribution, but not having access to wireless on my laptop is kind of a deal breaker, so I would like to get this figured out ASAP.

http://bugzilla.opensuse.org (same username/password as here)

  • I’m not sure at what layer in the stack the problem is or how to even go about figuring that out.

The developers will tell you.

I think I will follow your suggestion and try disabling NetworkManager completely. Wicked wouldn’t even bring up the interfaces, so that seems hopeless. I will see if I can get things working completely unmanaged.

I’m not sure whether “unmanaged” would even work in 13.2.

But Wicked should bring up the interfaces at least. You might have to configure them in YaST->Network Devices->Network Settings though, just like with ifup in previous versions. And remove stray configuration files (ifcfg-xxx) that might lie around in /etc/sysconfig/network/.

I was able to get wicked running, but it unfortunately did not resolve any of the problems. I guess I will need to escalate this issue if no one else has any ideas. Thanks again for the help!

Apologies. The post initially looked very similar to my issue (Upgrade 13.1->13.2 & wi-fi no longer works). I do have it working now (after a fashion).