On 5/27/20 2:02 PM, Robert G (Doc) Savage via users wrote:
On Wed, 2020-05-27 at 11:37 -0700, Samuel Sieb wrote:
> On 5/27/20 11:08 AM, Robert G (Doc) Savage via users wrote:
>> On Wed, 2020-05-27 at 10:07 -0700, Samuel Sieb wrote:
>>> On 5/27/20 9:06 AM, Robert G (Doc) Savage via users wrote:
>>>> After closing the lid on my P72 laptop last week and moving it
>>>> to the
>>>> livig room, I could not resume F32 when I raised the lid. I had
>>>> to hard
>>>> power cycle it, and after bootup I was unable to connect to my
>>>> WiFi
>>>> router. The router is fine, and WiFi works fine in the dual-
>>>> booted
>>>> Windows 10. But I can't figure out how to kick start my WiFi
>>>> connection.
>>>> I have restarted the P72 multiple times, with no success. The
>>>> copper
>>>> Ethernet connection works fine.
>>>>
>>>> Any suggestions how to kickstart it? When I try ifup I get
>>>> this:
>>>>
>>>> # ifup ATTxxxxxxxx
>>>>
>>>> Error: Connection activation failed: No suitable device found
>>>> for this
>>>> connection (device lo not available because device is strictly
>>>> unmanaged).
>>>
>>> What is the output of "nmcli c" and "rfkill list"?
>>
>> # rfkill list
>>
>> 2: phy0: Wireless LAN
>>
>> Soft blocked: yes
>>
>> Hard blocked: yes
>
> There's the problem. Somehow you've triggered the wifi kill switch.
> Check for a hardware switch around the outside or a keyboard
> function
> key related to wifi.
There's no physical WiFi switch on the P72. As I said, when I dual-boot
to Windows 10 the WiFi works perfectly. The problem is within F32.
The "Hard blocked: yes" means that something thinks the hardware is
disabled. Check the journal "journalctl -b" and search for "rfkill"
to
see what is triggering it.
Is there a file I can edit to re-enable WiFi which "nmcli
c" seems to
show is disabled in software somewhere?
"nmcli d" might give better info.