Unable to activate WiFi interfaces (Realtek chipset)

childerico · 2019-09-02 19:46:18

Hi all,
today the WiFi card on my laptop stopped working, after I had been regularly using it for hours. Trying to reconnect, I discovered that the card was blocked at hardware level. According to rfkill:

0: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: yes

That was also confirmed by the the WiFi LED on my laptop being off.The device, according to lspci, is:

05:00.0 Network controller: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe

I tried to unblock it without success. The issue persisted various reboots, using both the mainline and the LTS kernel. Only exception, after the very first reboot in which I switched from LTS to mainline kernel, the card worked for less than a minute before entering the "blocked" state again.

An excerpt from the log in that moment:

set 02 15:19:44 asus-n56j kernel: audit: type=1131 audit(1567433984.730:58): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=geoclue comm=">
set 02 15:19:44 asus-n56j audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=geoclue comm="systemd" exe="/usr/lib/syste>
set 02 15:19:44 asus-n56j systemd[1]: geoclue.service: Succeeded.
set 02 15:19:44 asus-n56j systemd[1]: geoclue.service: Main process exited, code=killed, status=15/TERM
set 02 15:19:44 asus-n56j geoclue[704]: Service not used for 60 seconds. Shutting down..
set 02 15:19:36 asus-n56j kernel: audit: type=1131 audit(1567433976.732:57): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager>
set 02 15:19:36 asus-n56j audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" e>
set 02 15:19:36 asus-n56j systemd[1]: NetworkManager-dispatcher.service: Succeeded.
set 02 15:19:36 asus-n56j org.gnome.Shell.desktop[907]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp >
set 02 15:19:36 asus-n56j kernel: audit: type=1131 audit(1567433976.296:56): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill>
set 02 15:19:36 asus-n56j audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/li>
set 02 15:19:36 asus-n56j systemd[1]: systemd-rfkill.service: Succeeded.
set 02 15:19:31 asus-n56j wpa_supplicant[611]: nl80211: deinit ifname=wlp5s0f0 disabled_11b_rates=0
set 02 15:19:31 asus-n56j gsd-sharing[1008]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit vino-server.servi>
set 02 15:19:31 asus-n56j gsd-sharing[1008]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-remote-desk>
set 02 15:19:31 asus-n56j gsd-sharing[1008]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not>
set 02 15:19:31 asus-n56j gsd-sharing[1008]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-user-share->
set 02 15:19:31 asus-n56j NetworkManager[581]: <info>  [1567433971.3538] manager: NetworkManager state is now DISCONNECTED
set 02 15:19:31 asus-n56j NetworkManager[581]: <info>  [1567433971.3475] device (wlp5s0f0): set-hw-addr: set MAC address to 3E:AC:XX:XX:EF:EF (s>
set 02 15:19:31 asus-n56j wpa_supplicant[611]: wlp5s0f0: PMKSA-CACHE-REMOVED 00:fc:ba:03:cf:e1 0
set 02 15:19:31 asus-n56j wpa_supplicant[611]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Inter>
set 02 15:19:31 asus-n56j wpa_supplicant[611]: wlp5s0f0: CTRL-EVENT-DISCONNECTED bssid=00:fc:ba:03:cf:e1 reason=3 locally_generated=1
set 02 15:19:31 asus-n56j kernel: audit: type=1130 audit(1567433971.294:55): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill>
set 02 15:19:31 asus-n56j gnome-shell[907]: An active wireless connection, in infrastructure mode, involves no access point?
set 02 15:19:31 asus-n56j audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/l>
set 02 15:19:31 asus-n56j systemd[1]: Started Load/Save RF Kill Switch Status.
set 02 15:19:31 asus-n56j NetworkManager[581]: <info>  [1567433971.2881] dhcp4 (wlp5s0f0): state changed bound -> done
set 02 15:19:31 asus-n56j NetworkManager[581]: <info>  [1567433971.2880] dhcp4 (wlp5s0f0): canceled DHCP transaction
set 02 15:19:31 asus-n56j NetworkManager[581]: <info>  [1567433971.2877] device (wlp5s0f0): state change: activated -> unavailable (reason 'none>
set 02 15:19:31 asus-n56j systemd[1]: Starting Load/Save RF Kill Switch Status...
set 02 15:19:31 asus-n56j kernel: wlp5s0f0: deauthenticating from 00:fc:ba:03:cf:e1 by local choice (Reason: 3=DEAUTH_LEAVING)
set 02 15:19:31 asus-n56j NetworkManager[581]: <info>  [1567433971.2873] manager: rfkill: Wi-Fi now disabled by radio killswitch
set 02 15:19:31 asus-n56j wpa_supplicant[611]: rfkill: WLAN hard blocked
set 02 15:19:26 asus-n56j kernel: audit: type=1130 audit(1567433966.761:54): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager>
set 02 15:19:26 asus-n56j audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" >
set 02 15:19:26 asus-n56j systemd[1]: Started Network Manager Script Dispatcher Service.
set 02 15:19:26 asus-n56j dbus-daemon[580]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
set 02 15:19:26 asus-n56j systemd[1]: Starting Network Manager Script Dispatcher Service...

Therefore, I decided to try with a USB WiFi adapter. The adapter is correctly displayed in the list of available wifi interfaces, and, when plugged, the WiFi LED on my laptop turns on.
However, I am not able to get the interface UP. If I try to activate it (either through the GUI or using ip link), I get no error messages and the interface simply stays DOWN.

Output of rfkill:

1: phy1: Wireless LAN
	Soft blocked: no
	Hard blocked: no

The device, which should be supported by current kernels, is:

Bus 002 Device 003: ID 148f:761a Ralink Technology, Corp. MT7610U ("Archer T2U" 2.4G+5G WLAN Adapter

At that point, I started thinking about a software issue. I had a Linux live CD at hand and I booted using it. The main WiFi card was still "hard blocked", while the USB adapter was not detected (I should try with another Live CD).

I have no idea of what is going on. Any advice is welcome.

EDIT: Please check also post #18 for additional information.

Last edited by childerico (2019-09-03 12:47:52)

loqs · 2019-09-02 20:09:54

You did not specify what the laptop is. Does it have an airplane or equivalent mode button?
I believe 148f:761a is a mediatek mt7610u the following may work https://aur.archlinux.org/packages/mt7610u_wifi_sta/ https://aur.archlinux.org/packages/mt76 … i_sta-alt/

childerico · 2019-09-02 21:09:34

Sorry, it is an ASUS N56JN. It has an airplane mode button (Fn+F2, as for many ASUS laptops), which only enables/disables "soft blocked" mode for the cards according to rfkill.

The two AUR packages you suggest both fail to build. I had already tried a similar package from AUR, which builds correctly but fails to install because that firmware is already provided by linux-firmware.

loqs · 2019-09-02 21:36:31

What was the AUR package which conflicted with linux-firmware?

childerico · 2019-09-02 21:52:07

The package is mt7601u-firmware, but I just realized it is for "7601u" and not "7610u" anyway.

loqs · 2019-09-02 23:46:18

https://aur.archlinux.org/packages/mt76 … i_sta-alt/ has not been updated for linux 5.0+ [1]
https://aur.archlinux.org/packages/mt7610u_wifi_sta/ looks to have not been touched in even longer.

[1] https://github.com/torvalds/linux/commi … 5655617693

seth · 2019-09-03 07:14:16

lsmod | grep asus

https://askubuntu.com/questions/459436/ … rd-blocked

ceterum censeo: you don't have a parallel windows installation, do you?

childerico · 2019-09-03 08:50:29

@seth: No, I have only Arch installed at the moment. I am actually considering replacing the SSD I am using now with my old HDD where I had a Windows installation, just to try.

Output of lsmod:

asus_nb_wmi            28672  0
asus_wmi               32768  1 asus_nb_wmi
sparse_keymap          16384  1 asus_wmi
rfkill                 28672  5 asus_wmi,cfg80211
wmi                    36864  2 asus_wmi,mxm_wmi
asus_wireless          20480  0
i8042                  32768  1 asus_nb_wmi

loqs · 2019-09-03 09:40:48

Did you try setting the asus_nb_wmi module's wapf parmareter to different values as suggested in the link seth provided?

module parameter using the command line

Edit:
updated mt7610u_wifi_sta-alt for linux 5.2
PKGBUILD

# Maintainer: Yannick Inizan <inizan[dot]yannick[at]gmail[dot]com>
# Based on the PKGBUILD created by Ivan Agarkov <ivan[dot]agarkov[at]gmail[dot]com>

pkgname=mt7610u_wifi_sta-alt
pkgver=3
pkgrel=4
# To get an overview of witch WiFi dongle has this chipset refer to https://wikidevi.com/wiki/MediaTek_MT7610U
pkgdesc="Kernel module for MediaTek MT7610U chipset featured in TP-Link Archer T2U and T2UH, TP-Link TL-WDN5200, ASUS USB-AC50, ASUS USB-AC51, Comcast Xfinity KXW02AAA, D-Link DWA-171 rev B1 and more"
arch=('x86_64')
license=('GPL2')
url="https://gitlab.com/BZHDeveloper/mt7610u_wifi_sta_v3002_dpo_20130916"
conflicts=('mt7610u_wifi_sta')
depends=('linux')
makedepends=('git' 'linux-headers')
source=("mt7610u_wifi_sta-alt"::"git+https://gitlab.com/BZHDeveloper/mt7610u_wifi_sta_v3002_dpo_20130916.git"
        "access_ok.patch")
md5sums=('SKIP'
         '1d69e72cc41fe6461a63bd748b43b6ba')
_extramodules=extramodules-ARCH

prepare() {
  cd $pkgname
  patch -p1 -i ../access_ok.patch
}

build() {
  cd "${srcdir}/${pkgname}"
  _kernver="$(cat /usr/lib/modules/$_extramodules/version)"
  make -C "${srcdir}/${pkgname}" LINUX_SRC=/usr/lib/modules/$_kernver/build
}

package() {
  cd "${srcdir}/${pkgname}"
  mkdir -p "${pkgdir}/etc/Wireless/RT2870STA"
  mkdir -p "${pkgdir}/usr/lib/modules/$_extramodules/kernel/drivers/net/wireless/os/linux"
  install -m 644 -t "${pkgdir}/etc/Wireless/RT2870STA" RT2870STA.dat
  install -m 644 -t "${pkgdir}/usr/lib/modules/$_extramodules/kernel/drivers/net/wireless/os/linux" os/linux/*.ko
}

access_ok.patch

diff --git a/os/linux/sta_ioctl.c b/os/linux/sta_ioctl.c
index e0c1232..8f4d919 100644
--- a/os/linux/sta_ioctl.c
+++ b/os/linux/sta_ioctl.c
@@ -32,6 +32,8 @@
 #include "rt_os_net.h"
 /*#include	"rt_config.h" */
 
+#include <linux/version.h>
+
 #ifdef DBG
 extern ULONG RTDebugLevel;
 extern ULONG RTDebugFunc;
@@ -2581,7 +2583,11 @@ INT rt28xx_sta_ioctl(
 		case SIOCGIWPRIV:
 			if (wrqin->u.data.pointer) 
 			{
+#if LINUX_VERSION_CODE < KERNEL_VERSION(5, 0, 0)
 				if ( access_ok(VERIFY_WRITE, wrqin->u.data.pointer, sizeof(privtab)) != TRUE)
+#else
+				if ( access_ok(wrqin->u.data.pointer, sizeof(privtab)) != TRUE)
+#endif
 					break;
 				if ((sizeof(privtab) / sizeof(privtab[0])) <= wrq->u.data.length)
 				{
@@ -2594,7 +2600,11 @@ INT rt28xx_sta_ioctl(
 			}
 			break;
 		case RTPRIV_IOCTL_SET:
-			if(access_ok(VERIFY_READ, wrqin->u.data.pointer, wrqin->u.data.length) != TRUE)   
+#if LINUX_VERSION_CODE < KERNEL_VERSION(5, 0, 0)
+			if(access_ok(VERIFY_READ, wrqin->u.data.pointer, wrqin->u.data.length) != TRUE)
+#else
+			if(access_ok(wrqin->u.data.pointer, wrqin->u.data.length) != TRUE)
+#endif
 					break;
 			return rt_ioctl_setparam(net_dev, NULL, NULL, wrqin->u.data.pointer);
 			break;

Last edited by loqs (2019-09-03 10:08:58)

childerico · 2019-09-03 10:08:31

Yes, I tried setting 0, 1, and 2 as values for the wapf parameter, but apparently nothing changed. Whenever I press the airplane mode button (Fn+F2) I only get a notification from GNOME saying that hardware-level airplane mode is active.

loqs · 2019-09-03 10:13:48

Did rfkill still show Hard blocked with those values for wapf? If so please try the value 4 for completeness. Also please see my edit to post #9 on the mt7610U.

childerico · 2019-09-03 10:23:19

@loqs: thank you for the help! I managed to build and install the firmware for the Mediatek card. Unfortunately, the issue is still there. The card is not blocked according to rfkill, but I am not able to use it because the interface is stuck in state DOWN. If I try to set it UP, both using the GUI and ip link, I don't get errors.

Output from journalctl -kr:

-- Logs begin at Tue 2019-08-27 09:12:29 BST, end at Tue 2019-09-03 11:20:23 BST. --
set 03 11:19:14 asus-n56j kernel: audit: type=1131 audit(1567505954.592:68): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
set 03 11:19:09 asus-n56j kernel: audit: type=1111 audit(1567505949.583:67): pid=596 uid=0 auid=4294967295 ses=4294967295 msg='op=radio-control arg="wwan-enabled" pid=997 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
set 03 11:19:09 asus-n56j kernel: audit: type=1130 audit(1567505949.580:66): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
set 03 11:19:07 asus-n56j kernel: audit: type=1131 audit(1567505947.850:65): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
set 03 11:19:02 asus-n56j kernel: audit: type=1111 audit(1567505942.842:64): pid=596 uid=0 auid=4294967295 ses=4294967295 msg='op=radio-control arg="wwan-enabled" pid=997 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
set 03 11:19:02 asus-n56j kernel: audit: type=1130 audit(1567505942.842:63): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
set 03 11:19:02 asus-n56j kernel: audit: type=1131 audit(1567505942.038:62): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
set 03 11:18:57 asus-n56j kernel: audit: type=1111 audit(1567505937.034:61): pid=596 uid=0 auid=4294967295 ses=4294967295 msg='op=radio-control arg="wwan-enabled" pid=997 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
set 03 11:18:55 asus-n56j kernel: audit: type=1111 audit(1567505935.078:60): pid=596 uid=0 auid=4294967295 ses=4294967295 msg='op=radio-control arg="wwan-enabled" pid=997 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
set 03 11:18:55 asus-n56j kernel: audit: type=1130 audit(1567505935.078:59): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
set 03 11:18:42 asus-n56j kernel: audit: type=1131 audit(1567505922.227:58): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=geoclue comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
set 03 11:18:24 asus-n56j kernel: audit: type=1131 audit(1567505904.042:57): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
set 03 11:18:23 asus-n56j kernel: audit: type=1131 audit(1567505903.475:56): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-localed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
set 03 11:18:21 asus-n56j kernel: audit: type=1111 audit(1567505901.722:55): pid=596 uid=0 auid=4294967295 ses=4294967295 msg='op=radio-control arg="wireless-enabled" pid=913 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
set 03 11:18:16 asus-n56j kernel: audit: type=1111 audit(1567505896.012:54): pid=596 uid=0 auid=4294967295 ses=4294967295 msg='op=radio-control arg="wireless-enabled" pid=913 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
set 03 11:18:13 asus-n56j kernel: audit: type=1131 audit(1567505893.772:53): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
set 03 11:18:12 asus-n56j kernel: audit: type=1131 audit(1567505892.435:52): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@120 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
set 03 11:18:12 asus-n56j kernel: audit: type=1131 audit(1567505892.425:51): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@120 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
set 03 11:18:08 asus-n56j kernel: audit: type=1130 audit(1567505888.769:50): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
set 03 11:18:08 asus-n56j kernel: usbcore: registered new interface driver rt2870
set 03 11:18:08 asus-n56j kernel: rtusb init rt2870 --->
set 03 11:18:08 asus-n56j kernel: usbcore: registered new interface driver mt76x0u
set 03 11:18:08 asus-n56j kernel: ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
set 03 11:18:08 asus-n56j kernel: usb 2-1: EEPROM ver:02 fae:01
set 03 11:18:06 asus-n56j kernel: usb 2-1: ASIC revision: 76100002 MAC revision: 76502000
set 03 11:18:06 asus-n56j kernel: usb 2-1: reset high-speed USB device number 5 using xhci_hcd
set 03 11:18:06 asus-n56j kernel: usb 2-1: SerialNumber: 1.0
set 03 11:18:06 asus-n56j kernel: usb 2-1: Manufacturer: MediaTek
set 03 11:18:06 asus-n56j kernel: usb 2-1: Product: WiFi
set 03 11:18:06 asus-n56j kernel: usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
set 03 11:18:06 asus-n56j kernel: usb 2-1: New USB device found, idVendor=148f, idProduct=761a, bcdDevice= 1.00
set 03 11:18:06 asus-n56j kernel: usb 2-1: new high-speed USB device number 5 using xhci_hcd
set 03 11:17:52 asus-n56j kernel: rfkill: input handler disabled
set 03 11:17:52 asus-n56j kernel: audit: type=1130 audit(1567505872.786:49): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=udisks2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

Last edited by childerico (2019-09-03 10:24:34)

loqs · 2019-09-03 10:27:01

What command did you use to try and bring the device up? What is the output of `ip l` after using that command?

childerico · 2019-09-03 10:33:32

1) I also tried setting wapf=4. The output of rfkill is always the same (soft blocked: no, hard blocked: yes)

2) I first tried activating the WiFi interface from GNOME network applet, then tried :

sudo ip link set wlan0 up

ip link before running that command:

4: wlp5s0f0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 1a:8c:fc:c0:84:05 brd ff:ff:ff:ff:ff:ff
5: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 12:17:a0:af:30:e8 brd ff:ff:ff:ff:ff:ff

After:

4: wlp5s0f0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 1a:8c:fc:c0:84:05 brd ff:ff:ff:ff:ff:ff
5: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
    link/ether 12:17:a0:af:30:e8 brd ff:ff:ff:ff:ff:ff

BTW, shouldn't the second interface be renamed to something different than "wlan0" as it happens at boot for the first one?

loqs · 2019-09-03 10:35:41

<NO-CARRIER,BROADCAST,MULTICAST,UP>

The interface is up.
Edit:
Wireless_network_configuration#Activate_the_interface.

Last edited by loqs (2019-09-03 10:41:16)

childerico · 2019-09-03 10:41:45

Ok, my interpretation of that output was not correct. In fact, I am not able to use the interface.
I use NetworkManager to manage connections. If I try, e.g., to run nmcli device:

DEVICE     TYPE      STATE        CONNECTION 
enp6s0     ethernet  unavailable  --         
wlan0      wifi      unavailable  --         
wlp5s0f0   wifi      unavailable  --         
lo         loopback  unmanaged    --

seth · 2019-09-03 12:09:01

The card is not blocked according to rfkill, but I am not able to use it because the interface is stuck in state DOWN.

The output of rfkill is always the same (soft blocked: no, hard blocked: yes)

This thread is a complete mess of contradicting informations now, probably because you're talking about two different interfaces at the same time?

Please get us some hard data first:

sudo journalctl -b
systemctl list-unit-files --state=enabled
rfkill
ip a
iw list

You can use https://wiki.archlinux.org/index.php/Pastebin

childerico · 2019-09-03 12:44:04

You are right, I am sorry for having provided some misleading information. Just to summarize:
1) the wifi card of my laptop suddenly stopped working (rfkill: "hard blocked: yes")
2) in the first post, I mentioned a second wifi card (i.e., a USB WiFi adapter), which I only plugged in aiming to check whether it could be simply a hardware issue with the first card. Unfortunately, it does not work either, and at the moment I am not able to tell whether it is due to a completely different problem or somehow the same.

You'll find below the output of the commands you requested. I will first report the output I get *without* using the second card. Just for completeness, then I will report the output I get after plugging in the second card. If you think it only creates ambiguity, please ignore the second card issues.

Only the main card used
journalctl -b
http://ix.io/1Ubu

systemctl list-unit-files --state=enabled
http://codepad.org/FlK3QKqb
rfkill

ID TYPE DEVICE      SOFT    HARD
 0 wlan phy0   unblocked blocked

ip a

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp6s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 78:24:af:db:e4:58 brd ff:ff:ff:ff:ff:ff
3: wlp5s0f0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 62:0f:ef:48:1f:8a brd ff:ff:ff:ff:ff:ff

iw list
http://codepad.org/Hr0MIuRm

After plugging the USB WiFi adapter
journalctl -b
http://ix.io/1Ubv

rfkill

ID TYPE DEVICE      SOFT      HARD
 0 wlan phy0   unblocked   blocked
 1 wlan phy1   unblocked unblocked

ip a

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp6s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 78:24:af:db:e4:58 brd ff:ff:ff:ff:ff:ff
3: wlp5s0f0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 62:0f:ef:48:1f:8a brd ff:ff:ff:ff:ff:ff
4: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether c6:37:eb:4c:21:a6 brd ff:ff:ff:ff:ff:ff

iw list
http://codepad.org/T0gqG5FM

EDIT: I updated the links to the journalctl output, which was truncated, as indicated by seth.

Last edited by childerico (2019-09-03 19:22:09)

seth · 2019-09-03 14:47:45

The journals are truncated early, please post the complete ones. Use the link I posted before.
We (therefore) also have no indication the wapf value was ever successfully set (I'd suggest either reloading the module or pass the parameter at the grub bootloader commandline in order to deal w/ pot. early loads from the initramfs)
Also try whether Fn+F2 toggles the hard block w/ those options.

The other adapter seems to work.
Basic test: stop networkmanager and run "wifi-menu wlan0" (ensure you've wpa_supplicant and dhcpcd installed)

childerico · 2019-09-03 19:29:02

1) Sorry, I have updated the links to the journals. Now they should be ok.
2) When I tried setting different values for wapf, I checked the value after rebooting looking at:

cat /sys/module/asus_nb_wmi/parameters/wapf

Whatever the value, I was not able to unblock the card at hardware level.

3) Thanks for suggesting trying netctl. The issue with the second adapter was indeed NetworkManager.
4) I verified also that, if I blacklist one of the modules required by the main wifi card, having the second card only NetworkManager works as expected. So, in presence of the issue with the main card, NetworkManager is not able to work at all.

I am now able to use the second adapter. Thanks a lot for the help. I will try to find out something more about the first card.

Arch Linux

#1 2019-09-02 19:46:18

Unable to activate WiFi interfaces (Realtek chipset)

#2 2019-09-02 20:09:54

Re: Unable to activate WiFi interfaces (Realtek chipset)

#3 2019-09-02 21:09:34

Re: Unable to activate WiFi interfaces (Realtek chipset)

#4 2019-09-02 21:36:31

Re: Unable to activate WiFi interfaces (Realtek chipset)

#5 2019-09-02 21:52:07

Re: Unable to activate WiFi interfaces (Realtek chipset)

#6 2019-09-02 23:46:18

Re: Unable to activate WiFi interfaces (Realtek chipset)

#7 2019-09-03 07:14:16

Re: Unable to activate WiFi interfaces (Realtek chipset)

#8 2019-09-03 08:50:29

Re: Unable to activate WiFi interfaces (Realtek chipset)

#9 2019-09-03 09:40:48

Re: Unable to activate WiFi interfaces (Realtek chipset)

#10 2019-09-03 10:08:31

Re: Unable to activate WiFi interfaces (Realtek chipset)

#11 2019-09-03 10:13:48

Re: Unable to activate WiFi interfaces (Realtek chipset)

#12 2019-09-03 10:23:19

Re: Unable to activate WiFi interfaces (Realtek chipset)

#13 2019-09-03 10:27:01

Re: Unable to activate WiFi interfaces (Realtek chipset)

#14 2019-09-03 10:33:32

Re: Unable to activate WiFi interfaces (Realtek chipset)

#15 2019-09-03 10:35:41

Re: Unable to activate WiFi interfaces (Realtek chipset)

#16 2019-09-03 10:41:45

Re: Unable to activate WiFi interfaces (Realtek chipset)

#17 2019-09-03 12:09:01

Re: Unable to activate WiFi interfaces (Realtek chipset)

#18 2019-09-03 12:44:04

Re: Unable to activate WiFi interfaces (Realtek chipset)

#19 2019-09-03 14:47:45

Re: Unable to activate WiFi interfaces (Realtek chipset)

#20 2019-09-03 19:29:02

Re: Unable to activate WiFi interfaces (Realtek chipset)

Board footer