rfkill Wifi toggles after i open lid

PranshuTG · 2022-11-20 13:33:36

02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 16)
03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8852AE 802.11ax PCIe Wireless Network Adapter

heres a live demonstration: https://youtu.be/j8pvsd7F9lM

Last edited by PranshuTG (2022-12-04 12:57:02)

PranshuTG · 2022-11-21 05:43:22

this is what happens after i open lid

▶ sudo systemctl status NetworkManager
● NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; preset: disabled)
     Active: active (running) since Mon 2022-11-21 08:32:26 +03; 9min ago
       Docs: man:NetworkManager(8)
   Main PID: 10862 (NetworkManager)
      Tasks: 3 (limit: 8725)
     Memory: 6.8M
        CPU: 3.238s
     CGroup: /system.slice/NetworkManager.service
             └─10862 /usr/bin/NetworkManager --no-daemon

Nov 21 08:40:18 pranshu-arch NetworkManager[10862]: <info>  [1669009218.2545] audit: op="statistics" interface="wlan0" ifindex=3 args="2000" pid=1199 uid=1000 result="success"
Nov 21 08:40:18 pranshu-arch NetworkManager[10862]: <info>  [1669009218.3447] manager: NetworkManager state is now CONNECTED_GLOBAL
Nov 21 08:40:19 pranshu-arch NetworkManager[10862]: <info>  [1669009219.2313] audit: op="statistics" interface="wlan0" ifindex=3 args="0" pid=1199 uid=1000 result="success"
Nov 21 08:42:05 pranshu-arch NetworkManager[10862]: <info>  [1669009325.6753] manager: rfkill: Wi-Fi now disabled by radio killswitch
Nov 21 08:42:05 pranshu-arch NetworkManager[10862]: <info>  [1669009325.6755] device (wlan0): state change: activated -> unavailable (reason 'none', sys-iface-state: 'managed')
Nov 21 08:42:05 pranshu-arch NetworkManager[10862]: <info>  [1669009325.6931] dhcp4 (wlan0): canceled DHCP transaction
Nov 21 08:42:05 pranshu-arch NetworkManager[10862]: <info>  [1669009325.6932] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Nov 21 08:42:05 pranshu-arch NetworkManager[10862]: <info>  [1669009325.6932] dhcp4 (wlan0): state changed no lease
Nov 21 08:42:05 pranshu-arch NetworkManager[10862]: <info>  [1669009325.7405] device (wlan0): set-hw-addr: set MAC address to AA:EA:60:22:54:C6 (scanning)
Nov 21 08:42:05 pranshu-arch NetworkManager[10862]: <info>  [1669009325.7409] manager: NetworkManager state is now DISCONNECTED

Last edited by PranshuTG (2022-11-21 05:43:41)

Ferdinand · 2022-11-21 08:27:00

From the first Nov 21 08:42:05 line, it looks like you trigger a turnoff of the wifi somehow.
Maybe the laptop actually turns off wifi when the lid closes, as it didn't seem from the video that it suspended?

At any rate, the problem seems to be that it doesn't turn it on again, when it should, which looks a bit like this situation:
https://wiki.archlinux.org/title/Networ … on_laptops

PranshuTG · 2022-11-21 14:34:02

i just found something weird. the wifi toggles when i open and close the lid, also i did a full system upgrade yesterday which is when the problem starting coming. also I had this problem before but it magically fixed itself. https://youtu.be/XGXTANPhmRU

PranshuTG · 2022-12-01 19:58:22

not fixed with new system upgrade

Last edited by PranshuTG (2022-12-04 12:56:51)

emunas1 · 2022-12-12 18:27:24

I am new to Arch, and I am also having this problem. Changing systemd login settings didn't help, and using stable mac address didn't help. When I close the lid, I can still access computer through local network. But OPENING the lid seems to shut down wifi adapter. Is this a systemic bug that there's no fix for ATM? Or is there something i'm doing wrong? Thanks!

Last edited by emunas1 (2022-12-12 18:28:47)

seth · 2022-12-12 21:47:40

Do you also use networkmanager?
If you stop if, make sure that the wifi is NOT rfkill blocked afterwards and then cycle the lid - what is the rfkill state afterwards?

emunas1 · 2022-12-12 21:50:49

seth wrote:

Do you also use networkmanager?
If you stop if, make sure that the wifi is NOT rfkill blocked afterwards and then cycle the lid - what is the rfkill state afterwards?

Yes, I use NetworkManager. And, you're right.Before I close the lid, everything is unblocked. After I close the lie and open it again, rfkill says wlan is softblocked. Closing and opening it again toggles it again and wifi comes back and it shows as unblocked.

emunas1 · 2022-12-12 21:56:30

seth wrote:

Do you also use networkmanager?
If you stop if, make sure that the wifi is NOT rfkill blocked afterwards and then cycle the lid - what is the rfkill state afterwards?

Is there an alternative to NetworkManager that will solve this? I'm reading about systemd-networkd. I'm still kind of a newbie when it comes to these things, so please excuse the ignorance.

seth · 2022-12-12 21:57:29

seth and a typo-daemon wrote:

Do you also use networkmanager?
If you stop it

The plan was to test whether that's also the case when NM is not running.

Edit:
We first need to figure whether NM is actually the cause.
However, https://wiki.archlinux.org/title/Networ … k_managers

Last edited by seth (2022-12-12 21:58:45)

emunas1 · 2022-12-12 22:25:05

seth wrote:

seth and a typo-daemon wrote:
Do you also use networkmanager?
If you stop it
The plan was to test whether that's also the case when NM is not running.
Edit:
We first need to figure whether NM is actually the cause.
However, https://wiki.archlinux.org/title/Networ … k_managers

If I stop NM, then the wifi turns off completely, as expected. If it's off, then closing and reopening the lid will not turn the wifi on. So I don't know that there's any way to test.

seth · 2022-12-12 22:32:26

The wireless connection is irrelevant, the rfkill state is what matters.
If stopping NM rfkill softblocks the NIC, you can just first unblock it.

emunas1 · 2022-12-12 23:14:11

seth wrote:

The wireless connection is irrelevant, the rfkill state is what matters.
If stopping NM rfkill softblocks the NIC, you can just first unblock it.

OK I see what you were getting at.
No, simply stopping the NetworkManager services does not create a softblock. It still says unblocked.
It is opening the lid that toggles it into a blocked state. (and closing it and opening it a second time will toggle it back into being unblocked).

emunas1 · 2022-12-13 01:55:32

I may have found something, not sure. dmesg shows the following info from closing and then reopening my lid (i changed the mac info in case there's privacy info on it):
232.208385] atkbd serio0: Unknown key pressed (translated set 2, code 0xd8 on isa0060/serio0).
[ 232.208392] atkbd serio0: Use 'setkeycodes e058 <keycode>' to make it known.
[ 232.216200] atkbd serio0: Unknown key released (translated set 2, code 0xd8 on isa0060/serio0).
[ 232.216205] atkbd serio0: Use 'setkeycodes e058 <keycode>' to make it known.
[ 233.488971] wlan0: deauthenticating from 12:ba:aa:1f:24:fg by local choice (Reason: 3=DEAUTH_LEAVING)

this unknown key can only be closing the lid but i'm unsure if it's related.
The deauthenticating by local choice (wlan0 is my wifi adapter) is what's interesting me. What does this mean and how can I stop it?

Last edited by emunas1 (2022-12-13 01:58:31)

cfr · 2022-12-13 03:47:00

Just to be clear, if you stop NetworkManager, unblock wifi if required, what is the output of

rfkill

before you close the lid and after you open it? Are you getting unblocked before and blocked after?

demaio · 2022-12-13 07:34:35

emunas1 wrote:

[ 232.208392] atkbd serio0: Use 'setkeycodes e058 <keycode>' to make it known.
[ 232.216200] atkbd serio0: Unknown key released (translated set 2, code 0xd8 on isa0060/serio0).
[ 232.216205] atkbd serio0: Use 'setkeycodes e058 <keycode>' to make it known.
[ 233.488971] wlan0: deauthenticating from 12:ba:aa:1f:24:fg by local choice (Reason: 3=DEAUTH_LEAVING)

(Is this an HP system?) On my HP 250 G7 machine I have to use the following command so the lid close does not (soft) block the RF / wifi:

setkeycodes e057 240 e058 240

This has to be executed as root. I do use a systemd service file to execute this command on every boot.

EDIT: and by the way, in Gnome, the following was also needed to stop rf blocking on lid close (as the logged in user):

gsettings set org.gnome.settings-daemon.plugins.media-keys rfkill-static "['XF86UWB', 'XF86RFKill']"

Last edited by demaio (2022-12-13 07:39:29)

emunas1 · 2022-12-13 12:35:15

demaio wrote:

emunas1 wrote:
[ 232.208392] atkbd serio0: Use 'setkeycodes e058 <keycode>' to make it known.
[ 232.216200] atkbd serio0: Unknown key released (translated set 2, code 0xd8 on isa0060/serio0).
[ 232.216205] atkbd serio0: Use 'setkeycodes e058 <keycode>' to make it known.
[ 233.488971] wlan0: deauthenticating from 12:ba:aa:1f:24:fg by local choice (Reason: 3=DEAUTH_LEAVING)
(Is this an HP system?) On my HP 250 G7 machine I have to use the following command so the lid close does not (soft) block the RF / wifi:
setkeycodes e057 240 e058 240
This has to be executed as root. I do use a systemd service file to execute this command on every boot.
EDIT: and by the way, in Gnome, the following was also needed to stop rf blocking on lid close (as the logged in user):
gsettings set org.gnome.settings-daemon.plugins.media-keys rfkill-static "['XF86UWB', 'XF86RFKill']"

Brilliant. Based on my research I was doing e058 242 or something similar and it didn't help. But yours helped. Thanks so much! Can you tell me instructions on how to set this up at boot? Thanks so much!

demaio · 2022-12-13 12:55:20

emunas1 wrote:

Can you tell me instructions on how to set this up at boot?

As written in my earlier post, you can use a systemd service file as described in the Arch wiki. If you need help with this (after reading the relevant sections in the linked wiki page), I suggest you open a new thread.

Arch Linux

#1 2022-11-20 13:33:36

rfkill Wifi toggles after i open lid

#2 2022-11-21 05:43:22

Re: rfkill Wifi toggles after i open lid

#3 2022-11-21 08:27:00

Re: rfkill Wifi toggles after i open lid

#4 2022-11-21 14:34:02

Re: rfkill Wifi toggles after i open lid

#5 2022-12-01 19:58:22

Re: rfkill Wifi toggles after i open lid

#6 2022-12-12 18:27:24

Re: rfkill Wifi toggles after i open lid

#7 2022-12-12 21:47:40

Re: rfkill Wifi toggles after i open lid

#8 2022-12-12 21:50:49

Re: rfkill Wifi toggles after i open lid

#9 2022-12-12 21:56:30

Re: rfkill Wifi toggles after i open lid

#10 2022-12-12 21:57:29

Re: rfkill Wifi toggles after i open lid

#11 2022-12-12 22:25:05

Re: rfkill Wifi toggles after i open lid

#12 2022-12-12 22:32:26

Re: rfkill Wifi toggles after i open lid

#13 2022-12-12 23:14:11

Re: rfkill Wifi toggles after i open lid

#14 2022-12-13 01:55:32

Re: rfkill Wifi toggles after i open lid

#15 2022-12-13 03:47:00

Re: rfkill Wifi toggles after i open lid

#16 2022-12-13 07:34:35

Re: rfkill Wifi toggles after i open lid

#17 2022-12-13 12:35:15

Re: rfkill Wifi toggles after i open lid

#18 2022-12-13 12:55:20

Re: rfkill Wifi toggles after i open lid

Board footer