Got wifi upon boot working, but gets rfkilled logging into to plasma

General system Newbie
1

Hi, new EndeavourOS user here having switched over from Manjaro with a bunch of Asus PN51s.

Since there’s access some machines remotely I got finally wifi going at reboot seemingly fine
(using the default NetworkManager interfaces) so I should be able to leave the ethernet cable unplugged.

What I’m head scratching and head banging about is why when I login to a graphical session on the machine that wifi gets rfkilled.

Here is the log snippet after bootup:

...
août 12 22:21:34 pn51-3 NetworkManager[1202]: <info>  [1660335694.8938] device (wlan0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
août 12 22:21:34 pn51-3 NetworkManager[1202]: <info>  [1660335694.8948] device (wlan0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
août 12 22:21:34 pn51-3 NetworkManager[1202]: <info>  [1660335694.8949] device (wlan0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
août 12 22:21:34 pn51-3 NetworkManager[1202]: <info>  [1660335694.8951] manager: NetworkManager state is now CONNECTED_SITE
août 12 22:21:34 pn51-3 NetworkManager[1202]: <info>  [1660335694.8959] device (wlan0): Activation: successful, device activated.
août 12 22:21:35 pn51-3 NetworkManager[1202]: <info>  [1660335695.0203] manager: NetworkManager state is now CONNECTED_GLOBAL
août 12 22:21:36 pn51-3 NetworkManager[1202]: <info>  [1660335696.7801] manager: startup complete

then after logging in, the network icon is greyed out, and I see this:

août 12 22:23:15 pn51-3 NetworkManager[1202]: <info>  [1660335795.6922] manager: rfkill: Wi-Fi hardware radio set disabled
août 12 22:23:15 pn51-3 NetworkManager[1202]: <info>  [1660335795.6923] device (wlan0): state change: activated -> unavailable (reason 'none', sys-iface-state: 'managed')
août 12 22:23:15 pn51-3 NetworkManager[1202]: <info>  [1660335795.7281] dhcp4 (wlan0): canceled DHCP transaction
août 12 22:23:15 pn51-3 NetworkManager[1202]: <info>  [1660335795.7281] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
août 12 22:23:15 pn51-3 NetworkManager[1202]: <info>  [1660335795.7281] dhcp4 (wlan0): state changed no lease
août 12 22:23:15 pn51-3 NetworkManager[1202]: <info>  [1660335795.7325] device (wlan0): set-hw-addr: set MAC address to A2:D7:86:FE:F2:97 (scanning)
août 12 22:23:15 pn51-3 NetworkManager[1202]: <info>  [1660335795.7423] audit: op="radio-control" arg="wireless-enabled:off" pid=4836 uid=1001 result="success"
août 12 22:23:15 pn51-3 NetworkManager[1202]: <info>  [1660335795.7429] manager: rfkill: Wi-Fi now disabled by radio killswitch
août 12 22:23:15 pn51-3 NetworkManager[1202]: <info>  [1660335795.7446] manager: NetworkManager state is now CONNECTED_LOCAL
août 12 22:23:15 pn51-3 NetworkManager[1202]: <info>  [1660335795.7450] device (p2p-dev-wlan0): state change: disconnected -> unavailable (reason 'supplicant-failed', sys-iface-state: 'managed')

indeed, I need to click on the button to activate wifi to get it back up.

Can’t seem to figure out where rfkill is being called in the login process, can anybody steer me the right direction to fix it?

BTW I already have the following enabled and it seems to be okay:

$ systemctl status rfkill-unblock@wlan.service 
○ rfkill-unblock@wlan.service - RFKill-Unblock wlan
     Loaded: loaded (/usr/lib/systemd/system/rfkill-unblock@.service; enabled; preset: disabled)
     Active: inactive (dead) since Fri 2022-08-12 22:21:30 CEST; 26min ago
    Process: 1118 ExecStart=/usr/bin/rfkill unblock wlan (code=exited, status=0/SUCCESS)
   Main PID: 1118 (code=exited, status=0/SUCCESS)
        CPU: 913us

Thanks kindly, in advance.

2

Could be a KDE setting, could be something like TLP disabling the radio on boot (or on connection to Ethernet)?

3

Not familiar with TLP, I check and no tlp packages are installed.
Not sure where to look under KDE, still somewhat new to it coming from lxde/lxqt…

4

I guess good news from telepathic central, after recent updates, I don’t seem to experience the problem any longer!

5

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.