On 5/27/20 3:46 PM, Robert G (Doc) Savage via users wrote:
Here's what "journalctl -b" tells me:
May 27 16:48:50 tiger.protogeek.org rfkill[14554]: unblock set for all
May 27 16:48:50 tiger.protogeek.org audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd"
hostname=? addr=? terminal=? res=success'
May 27 16:48:56 tiger.protogeek.org systemd[1]: systemd-rfkill.service:
Succeeded.
May 27 16:48:56 tiger.protogeek.org audit[1]: SERVICE_STOP pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd"
hostname=? addr=? terminal=? res=success'
Is that the only references to rfkill? Did the log start at boot up?
Try searching also for "KILL", it's likely in the wifi device
initialization.
What is the "lspci" line for your wifi device?
It looks like every time the service tries to start wifi with rfkill,
SOMETHING is turning it around and stopping it. As the rfkill list
command shows, this denial will apparently be done on all wifi
connections that are stored in /etc/sysconfig/network-scripts:
systemd-rfkill is a static service, it runs when called and then stops.
# rfkill list
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
Since there is no hardware switch to enable/disable WiFi on the
ThinkPad P72, there must be some configuration command I can give that
turns "Hard blocked: yes" to "Hard blocked: no".
No, that's the difference between a "hard" block and a "soft" block.
You need to find out why rfkill thinks the hardware is blocked.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
