You are not logged in.

Pages: 1

#1 2019-02-26 22:33:43

bosco
Member
Registered: 2019-02-26
Posts: 16

[SOLVED] NetworkManager and hardware toggle wifi soft block problems

I'm using the KDE Plasma Desktop Environment and NetworkManager to manage my connections since there's a built in KDE front-end (the one in the panel bar as a graphical element) for that, it used to be working fine.
Then I pressed once the F8 key on a thinkpad, that is, the one that disables the wifi card. I went to rfkill to see its status, it was soft blocked. Both pressing the key again and using the unblock command work to unblock it, but when I do, I don't see the KDE network front-end scanning for wifi networks. I thought that the logical step to follow would be to restart the NetworkManager service, but as I did, the card was soft blocked again, I've been running around in circles re-doing the process and rebooting several times. To confirm my suspicions, I performed the watch command for rfkill, and it did, in fact, soft block my network card the moment I start NetworkManager.service

Last edited by bosco (2019-03-03 16:18:09)

Offline

#2 2019-02-26 22:47:15

Head_on_a_Stick
Member
From: The Wirral
Registered: 2014-02-20
Posts: 9,003
Website

Re: [SOLVED] NetworkManager and hardware toggle wifi soft block problems

You should probably post the actual output of `rfkill` rather than a vague description.

Hardware switches usually produce a hard block rather than a soft block.

What is recorded in the systemd journal when you experience this problem?

Can you connect if you use something other than NetworkManager?

Jin, Jîyan, Azadî

Offline

#3 2019-02-27 11:23:19

bosco
Member
Registered: 2019-02-26
Posts: 16

Re: [SOLVED] NetworkManager and hardware toggle wifi soft block problems

Head_on_a_Stick wrote:

You should probably post the actual output of `rfkill` rather than a vague description.

Either when I boot with NetworkManager.service enabled, or I start it, this is the outcome

ID TYPE      DEVICE                      SOFT         HARD
 0 bluetooth tpacpi_bluetooth_sw desbloqueado desbloqueado
 1 wlan      phy0                   bloqueado desbloqueado
 2 bluetooth hci0                desbloqueado desbloqueado

When I press the key (F8 on thinkpad laptop), or boot without NM service enabled, I get this

ID TYPE      DEVICE                      SOFT         HARD
 0 bluetooth tpacpi_bluetooth_sw desbloqueado desbloqueado
 1 wlan      phy0                desbloqueado desbloqueado
 2 bluetooth hci0                desbloqueado desbloqueado

I tested by using watch to see it go from one state to the other in real time, I drew the conclusion that NM service does, in fact, soft block it

Head_on_a_Stick wrote:

Hardware switches usually produce a hard block rather than a soft block.

Maybe, but this isn't a flicking type switch, it's a key in the keyboard

Head_on_a_Stick wrote:

What is recorded in the systemd journal when you experience this problem?

feb 27 11:46:57 boscohost systemd[1]: Starting Network Manager...
feb 27 11:46:57 boscohost NetworkManager[984]: <info>  [1551264417.8055] NetworkManager (version 1.14.5dev+17+gba83251bb-2) is starting... (for the first time)
feb 27 11:46:57 boscohost NetworkManager[984]: <info>  [1551264417.8057] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf)
feb 27 11:46:57 boscohost NetworkManager[984]: <info>  [1551264417.8078] wifi-nl80211: (wlan0): using nl80211 for WiFi device control
feb 27 11:46:57 boscohost NetworkManager[984]: <info>  [1551264417.8128] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
feb 27 11:46:57 boscohost systemd[1]: Started Network Manager.
feb 27 11:46:57 boscohost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
feb 27 11:46:57 boscohost kernel: audit: type=1130 audit(1551264417.810:43): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
feb 27 11:46:57 boscohost kdeinit5[697]: propsReply "No existe la interfaz «org.freedesktop.DBus.Properties» en el objeto en la ruta /org/freedesktop/NetworkManager"
feb 27 11:46:57 boscohost NetworkManager[984]: <info>  [1551264417.8142] manager[0x5634106cf060]: monitoring kernel firmware directory '/lib/firmware'.
feb 27 11:46:57 boscohost systemd[1]: Reached target Network.
feb 27 11:46:57 boscohost kdeinit5[697]: nmReply "No existe la interfaz «org.freedesktop.NetworkManager» en el objeto en la ruta /org/freedesktop/NetworkManager"
feb 27 11:46:57 boscohost dbus-daemon[493]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.109' (uid=0 pid=984 comm="/usr/bin/NetworkManager --no-daemon ")
feb 27 11:46:57 boscohost kdeinit5[697]: "Object path cannot be empty"
feb 27 11:46:57 boscohost systemd[1]: Starting Hostname Service...
feb 27 11:46:58 boscohost dbus-daemon[493]: [system] Successfully activated service 'org.freedesktop.hostname1'
feb 27 11:46:58 boscohost systemd[1]: Started Hostname Service.
feb 27 11:46:58 boscohost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
feb 27 11:46:58 boscohost kernel: audit: type=1130 audit(1551264418.046:44): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
feb 27 11:46:58 boscohost NetworkManager[984]: <info>  [1551264418.0511] hostname: hostname: using hostnamed
feb 27 11:46:58 boscohost NetworkManager[984]: <info>  [1551264418.0511] hostname: hostname changed from (none) to "boscohost"
feb 27 11:46:58 boscohost NetworkManager[984]: <info>  [1551264418.0513] dns-mgr[0x5634106dc910]: init: dns=default, rc-manager=symlink
feb 27 11:46:58 boscohost NetworkManager[984]: <info>  [1551264418.0520] rfkill1: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.6/0000:03:00.0/ieee80211/phy0/rfkill1) (driver iwlwifi)
feb 27 11:46:58 boscohost NetworkManager[984]: <info>  [1551264418.0522] manager[0x5634106cf060]: rfkill: WiFi hardware radio set disabled
feb 27 11:46:58 boscohost NetworkManager[984]: <info>  [1551264418.0522] manager[0x5634106cf060]: rfkill: WWAN hardware radio set disabled
Head_on_a_Stick wrote:

Can you connect if you use something other than NetworkManager?

Yes, wpa_supplicant

Offline

#4 2019-02-27 21:13:10

Head_on_a_Stick
Member
From: The Wirral
Registered: 2014-02-20
Posts: 9,003
Website

Re: [SOLVED] NetworkManager and hardware toggle wifi soft block problems

See https://wiki.archlinux.org/index.php/Ne … on_laptops, or perhaps https://wiki.archlinux.org/index.php/Ne … ion,_etc.).

Prepend commands with LC_ALL=C to get them to speak English.

Jin, Jîyan, Azadî

Offline

#5 2019-03-03 16:17:34

bosco
Member
Registered: 2019-02-26
Posts: 16

Re: [SOLVED] NetworkManager and hardware toggle wifi soft block problems

Turned out to be the GUI client messing things up, I've uninstalled and reinstalled the packages and now it works out fine

Offline

Pages: 1

Board footer

Powered by FluxBB