Restart F32 WiFi on ThinkPad P72

[Robert G (Doc) Savage]

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 ATTxxxxxxxxError: Connection activation failed: No suitable
device found for this connection (device lo not available because
device is strictly unmanaged).
--Doc Savage
    Fairview Heights, IL

[Samuel Sieb]

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"?

[Samuel Sieb]

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.

[Patrick O'Callaghan]

On Wed, 2020-05-27 at 13:08 -0500, Robert G (Doc) Savage via users
wrote:

(Apparently an empty message)

In fact it's HTML only. If you post in HTML please always include a
plaintext/alternative section.

poc

[Robert G (Doc) Savage]

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. 
Sam,

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.

Is there a file I can edit to re-enable WiFi which "nmcli c" seems to
show is disabled in software somewhere?

--Doc Savage
  Fairview Heights, IL

[Todd Zullinger]

Patrick O'Callaghan wrote:
>  On Wed, 2020-05-27 at 13:08 -0500, Robert G (Doc) Savage via users
>  wrote:
>  
>  (Apparently an empty message)
>  
>  In fact it's HTML only. If you post in HTML please always include a
>  plaintext/alternative section. 
Though it's even better to follow the list guidelines and
not post HTML at all. :)

https://fedoraproject.org/wiki/Mailing_list_guidelines#No_HTML_Mail.2C_Pl...

Many mail clients that generate text parts in addition to
HTML are too dumb to ensure the text part is legible, that
quoted text is clearly marked (as opposed to only visually
differentiated by color, font size, or other means which are
useless in a text part.

-- 
Todd

[Samuel Sieb]

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.

[Ed Greshko]

On 2020-05-28 04:44, Patrick O'Callaghan wrote:
>  On Wed, 2020-05-27 at 13:08 -0500, Robert G (Doc) Savage via users
>  wrote:
>
>  (Apparently an empty message)
>
>  In fact it's HTML only. If you post in HTML please always include a
>  plaintext/alternative section.
>
>  
Best to check the source.  I got...

Content-Type: multipart/alternative

followed by

Content-Type: text/plain

and then

Content-Type: text/html

Sounds more like a UA issue on your end.  :-) 

-- 
The key to getting good answers is to ask good questions.

[Todd Zullinger]

Ed Greshko wrote:
>  On 2020-05-28 04:44, Patrick O'Callaghan wrote:
> > On Wed, 2020-05-27 at 13:08 -0500, Robert G (Doc) Savage via users
> > wrote:
> >
> > (Apparently an empty message)
> >
> > In fact it's HTML only. If you post in HTML please always include a
> > plaintext/alternative section.
> >
> >
>  
>  Best to check the source.  I got... 
Indeed.  But you have to check the details in this case. ;)

>  Sounds more like a UA issue on your end.  :-)  
Nope, not an issue on Patrick's end.  The text/plain part of
the message in questionwas empty (effectively, it contained
only a base64-encoded CR/LF).

-- 
Todd

[Patrick O'Callaghan]

On Wed, 2020-05-27 at 17:11 -0400, Todd Zullinger wrote:
>  Patrick O'Callaghan wrote:
>  > On Wed, 2020-05-27 at 13:08 -0500, Robert G (Doc) Savage via users
>  > wrote:
>  > 
>  > (Apparently an empty message)
>  > 
>  > In fact it's HTML only. If you post in HTML please always include a
>  > plaintext/alternative section.
>  
>  Though it's even better to follow the list guidelines and
>  not post HTML at all. :)
>  
>  https://fedoraproject.org/wiki/Mailing_list_guidelines#No_HTML_Mail.2C_Pl... 
Of course, though I suspect that ship has sailed. At least with
plaintext/alternative one doesn't have to read it.

poc

[Patrick O'Callaghan]

On Wed, 2020-05-27 at 18:00 -0400, Todd Zullinger wrote:
>  Ed Greshko wrote:
>  > On 2020-05-28 04:44, Patrick O'Callaghan wrote:
>  > > On Wed, 2020-05-27 at 13:08 -0500, Robert G (Doc) Savage via users
>  > > wrote:
>  > > 
>  > > (Apparently an empty message)
>  > > 
>  > > In fact it's HTML only. If you post in HTML please always include a
>  > > plaintext/alternative section.
>  > > 
>  > > 
>  > 
>  > Best to check the source.  I got...
>  
>  Indeed.  But you have to check the details in this case. ;)
>  
>  > Sounds more like a UA issue on your end.  :-) 
>  
>  Nope, not an issue on Patrick's end.  The text/plain part of
>  the message in questionwas empty (effectively, it contained
>  only a base64-encoded CR/LF). 
Indeed. What I saw was a single blank line. I had to use a menu option
in Evolution to read the HTML version.

poc

[Ed Greshko]

On 2020-05-28 06:00, Todd Zullinger wrote:
>  Nope, not an issue on Patrick's end.  The text/plain part of
>  the message in questionwas empty (effectively, it contained
>  only a base64-encoded CR/LF). 
Odd....

My source of the original message contains

--=-V2saX3G33UU4OPBTEaCs
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit

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.



-- 
The key to getting good answers is to ask good questions.

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"?_______________________________________________users mailing
>  list -- users(a)lists.fedoraproject.org
>  To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
>  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/[e-mail] 
Well, for what its worth,
My thinkpad E595 just did the same thing.  (Fedora 32)Was able to boot
to multi-user.target, logged in and the NIC was active and good.  Boot
to graphical.target failed.  No NIC, no bluetooth, no boot.The only way
to get it to boot normally was to go into the BIOS.  Didn't change
anything, even quit without saving.Rebooted and it came up clean.I'm at
a complete loss.  But it is back now.Looking at what happened, I see
that a lot of firmware packages were updated.Not sure why loading BIOS
helped.
2020-05-22T15:52:37Z SUBDEBUG Upgrade: linux-firmware-whence-20200519-
108.fc32.noarch2020-05-22T15:52:42Z SUBDEBUG Upgrade: iwl100-firmware-
39.31.5.1-108.fc32.noarch2020-05-22T15:52:42Z SUBDEBUG Upgrade:
iwl1000-firmware-1:39.31.5.1-108.fc32.noarch2020-05-22T15:52:42Z
SUBDEBUG Upgrade: iwl105-firmware-18.168.6.1-108.fc32.noarch2020-05-
22T15:52:42Z SUBDEBUG Upgrade: iwl135-firmware-18.168.6.1-
108.fc32.noarch2020-05-22T15:52:42Z SUBDEBUG Upgrade: iwl2000-firmware-
18.168.6.1-108.fc32.noarch2020-05-22T15:52:42Z SUBDEBUG Upgrade:
iwl2030-firmware-18.168.6.1-108.fc32.noarch2020-05-22T15:52:42Z
SUBDEBUG Upgrade: iwl3160-firmware-1:25.30.13.0-108.fc32.noarch2020-05-
22T15:52:42Z SUBDEBUG Upgrade: iwl3945-firmware-15.32.2.9-
108.fc32.noarch2020-05-22T15:52:42Z SUBDEBUG Upgrade: iwl4965-firmware-
228.61.2.24-108.fc32.noarch2020-05-22T15:52:42Z SUBDEBUG Upgrade:
iwl5000-firmware-8.83.5.1_1-108.fc32.noarch2020-05-22T15:52:42Z
SUBDEBUG Upgrade: iwl5150-firmware-8.24.2.2-108.fc32.noarch2020-05-
22T15:52:42Z SUBDEBUG Upgrade: iwl6000-firmware-9.221.4.1-
108.fc32.noarch2020-05-22T15:52:42Z SUBDEBUG Upgrade: iwl6000g2a-
firmware-18.168.6.1-108.fc32.noarch2020-05-22T15:52:42Z SUBDEBUG
Upgrade: iwl6000g2b-firmware-18.168.6.1-108.fc32.noarch2020-05-
22T15:52:42Z SUBDEBUG Upgrade: iwl6050-firmware-41.28.5.1-
108.fc32.noarch2020-05-22T15:52:42Z SUBDEBUG Upgrade: iwl7260-firmware-
1:25.30.13.0-108.fc32.noarch2020-05-22T15:52:43Z SUBDEBUG Upgrade:
libertas-usb8388-firmware-2:20200519-108.fc32.noarch2020-05-
22T15:52:43Z SUBDEBUG Upgrade: linux-firmware-20200519-
108.fc32.noarch2020-05-22T15:52:47Z SUBDEBUG Upgraded: linux-firmware-
20200421-107.fc32.noarch2020-05-22T15:52:47Z SUBDEBUG Upgraded:
libertas-usb8388-firmware-2:20200421-107.fc32.noarch2020-05-
22T15:52:47Z SUBDEBUG Upgraded: iwl7260-firmware-1:25.30.13.0-
107.fc32.noarch2020-05-22T15:52:47Z SUBDEBUG Upgraded: iwl6050-
firmware-41.28.5.1-107.fc32.noarch2020-05-22T15:52:47Z SUBDEBUG
Upgraded: iwl6000g2b-firmware-18.168.6.1-107.fc32.noarch2020-05-
22T15:52:47Z SUBDEBUG Upgraded: iwl6000g2a-firmware-18.168.6.1-
107.fc32.noarch2020-05-22T15:52:47Z SUBDEBUG Upgraded: iwl6000-
firmware-9.221.4.1-107.fc32.noarch2020-05-22T15:52:47Z SUBDEBUG
Upgraded: iwl5150-firmware-8.24.2.2-107.fc32.noarch2020-05-22T15:52:47Z 
SUBDEBUG Upgraded: iwl5000-firmware-8.83.5.1_1-107.fc32.noarch2020-05-
22T15:52:47Z SUBDEBUG Upgraded: iwl4965-firmware-228.61.2.24-
107.fc32.noarch2020-05-22T15:52:47Z SUBDEBUG Upgraded: iwl3945-
firmware-15.32.2.9-107.fc32.noarch2020-05-22T15:52:47Z SUBDEBUG
Upgraded: iwl3160-firmware-1:25.30.13.0-107.fc32.noarch2020-05-
22T15:52:47Z SUBDEBUG Upgraded: iwl2030-firmware-18.168.6.1-
107.fc32.noarch2020-05-22T15:52:47Z SUBDEBUG Upgraded: iwl2000-
firmware-18.168.6.1-107.fc32.noarch2020-05-22T15:52:47Z SUBDEBUG
Upgraded: iwl135-firmware-18.168.6.1-107.fc32.noarch2020-05-
22T15:52:47Z SUBDEBUG Upgraded: iwl105-firmware-18.168.6.1-
107.fc32.noarch2020-05-22T15:52:47Z SUBDEBUG Upgraded: iwl1000-
firmware-1:39.31.5.1-107.fc32.noarch2020-05-22T15:52:47Z SUBDEBUG
Upgraded: iwl100-firmware-39.31.5.1-107.fc32.noarch2020-05-22T15:52:47Z 
SUBDEBUG Upgraded: linux-firmware-whence-20200421-107.fc32.noarch
-- 
Brian Millett
"Mr. Garibaldi. Just now, would you really have killed *me*?"
'Yes. Yes, I would have, but I'm just as glad I didn't have to. The
    paperwork's a pain in the butt.'
   -- [ Londo and Garibaldi, "Midnight on the Firing Line"]

[Ed Greshko]

On 2020-05-28 06:07, Patrick O'Callaghan wrote:
>  On Wed, 2020-05-27 at 18:00 -0400, Todd Zullinger wrote:
> > Ed Greshko wrote:
> >> On 2020-05-28 04:44, Patrick O'Callaghan wrote:
> >>> On Wed, 2020-05-27 at 13:08 -0500, Robert G (Doc) Savage via users
> >>> wrote:
> >>>
> >>> (Apparently an empty message)
> >>>
> >>> In fact it's HTML only. If you post in HTML please always include a
> >>> plaintext/alternative section.
> >>>
> >>>
> >> Best to check the source.  I got...
> > Indeed.  But you have to check the details in this case. ;)
> >
> >> Sounds more like a UA issue on your end.  :-) 
> > Nope, not an issue on Patrick's end.  The text/plain part of
> > the message in questionwas empty (effectively, it contained
> > only a base64-encoded CR/LF).
>  Indeed. What I saw was a single blank line. I had to use a menu option
>  in Evolution to read the HTML version. 
As I mentioned in another post...  That is odd....

I have a correctly formatted multipart/alternative message with...

Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit

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:

ETC....



-- 
The key to getting good answers is to ask good questions.

[Patrick O'Callaghan]

On Thu, 2020-05-28 at 06:08 +0800, Ed Greshko wrote:
>  On 2020-05-28 06:00, Todd Zullinger wrote:
>  > Nope, not an issue on Patrick's end.  The text/plain part of
>  > the message in questionwas empty (effectively, it contained
>  > only a base64-encoded CR/LF).
>  
>  Odd....
>  
>  My source of the original message contains
>  
>  --=-V2saX3G33UU4OPBTEaCs
>  Content-Type: text/plain; charset="UTF-8"
>  Content-Transfer-Encoding: 7bit
>  
>  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. 
I took a look at the message. It actually has 3 sections:

1.
Content-Type: text/plain
Content-Transfer-Encoding: base64
(That's the empty line)

2.
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment; filename="attachment.html"
Content-Type: text/html; charset="utf-8"; name="attachment.html"
(the HTML)

3.
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
(the base64 version of the text)

My UA showed the first one and after selecting a menu option, the
second one. It didn't offer the third one. I would say that the
existence of two different text/plain sections with different content
points to a problem with the OP's UA, though it's debatable whether
mine should have offered both of them. It's certainly a situation I've
never come across before and I don't know what the standards say about
it.

The interesting thing is that the OP's UA *also* appears to be
Evolution. I'll mention this on the Evolution list.

poc

[Robert G (Doc) Savage]

On Wed, 2020-05-27 at 14:39 -0700, Samuel Sieb wrote:
>  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. 
Sam,

(In all plain text for those whose clients can't handle HTML...)

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'

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:

# rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
	Soft blocked: no
	Hard blocked: no
2: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: yes
3: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no

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".

Or is there something else?

--Doc Savage
  Fairview Heights, IL

[Todd Zullinger]

Ed Greshko wrote:
>  On 2020-05-28 06:00, Todd Zullinger wrote:
> > Nope, not an issue on Patrick's end.  The text/plain part of
> > the message in questionwas empty (effectively, it contained
> > only a base64-encoded CR/LF).
>  
>  Odd....
>  
>  My source of the original message contains 
That's the first message in the thread, but not the one to
which Patrick replied.  The message with Message-Id:

  <658fd946429a9ea3de63023dac386274d16ccec2.camel(a)peaknet.net&gt;

is the one which has only an empty text/plain part (aside
from the text/plain part containing the list footer that
Mailman adds).

It's _possible_ that the list software could have mangled
the message.  I'm not sure how likely that is, but it is
another piece of software in the pipeline between sender and
recipient, so it can't be ruled out. :)

Anyway, I'm mostly just demonstrating how easily distracted
I am by minutiae.

-- 
Todd

[Ed Greshko]

On 2020-05-28 07:03, Todd Zullinger wrote:
>  Ed Greshko wrote:
> > On 2020-05-28 06:00, Todd Zullinger wrote:
> >> Nope, not an issue on Patrick's end.  The text/plain part of
> >> the message in questionwas empty (effectively, it contained
> >> only a base64-encoded CR/LF).
> > Odd....
> >
> > My source of the original message contains
>  That's the first message in the thread, but not the one to
>  which Patrick replied.  The message with Message-Id: 
I see....

The tread-view I was showing didn't display that connection clearly due to a
"sub-optimal" theme.  :-(

>  Anyway, I'm mostly just demonstrating how easily distracted
>  I am by minutiae. 
Same here.  Now I have to be distracted looking for a better theme.  :-)


-- 
The key to getting good answers is to ask good questions.

[Ed Greshko]

On 2020-05-28 06:34, Patrick O'Callaghan wrote:

After being corrected by Todd, I see what you mean by the blank line.

But....

>  3.
>  Content-Type: text/plain; charset="utf-8"
>  MIME-Version: 1.0
>  Content-Transfer-Encoding: base64
>  Content-Disposition: inline
>  (the base64 version of the text) 
Did you decode the block?  When I decode it I see the standard footer applied to all
Fedora posts.



-- 
The key to getting good answers is to ask good questions.

[Todd Zullinger]

Ed Greshko wrote:
>  On 2020-05-28 06:34, Patrick O'Callaghan wrote:
>  
>  After being corrected by Todd, I see what you mean by the blank line.
>  
>  But....
>  
> > 3.
> > Content-Type: text/plain; charset="utf-8"
> > MIME-Version: 1.0
> > Content-Transfer-Encoding: base64
> > Content-Disposition: inline
> > (the base64 version of the text)
>  
>  Did you decode the block?  When I decode it I see the
>  standard footer applied to all Fedora posts. 
Indeed.  When Mailman adds the footer, it encapsulates the
entire multipart/alternative part and then adds a text/plain
part with the footer.

Here's what the MIME structure looks like (assuming anyone
other than the three of us are curious at this point ;) ):

    --===============2476488337104940302==
    Content-Type: multipart/alternative; boundary="=-sMDlrK7vtwC0ZKWLiA7c"


    --=-sMDlrK7vtwC0ZKWLiA7c
    Content-Type: text/plain
    Content-Transfer-Encoding: base64

    DQo=


    --=-sMDlrK7vtwC0ZKWLiA7c
    Content-Type: text/html; charset="utf-8"
    Content-Transfer-Encoding: quoted-printable

    [QP-encoded HTML part]


    --=-sMDlrK7vtwC0ZKWLiA7c--

    --===============2476488337104940302==
    Content-Type: text/plain; charset="utf-8"
    MIME-Version: 1.0
    Content-Transfer-Encoding: base64
    Content-Disposition: inline

    [B64-encoded list footer]

    --===============2476488337104940302==--

I don't know Evolution, but if it's presenting choices for
the multipart/alternative part, then that latter text/plain
part wouldn't be included as an option.

-- 
Todd

[Ed Greshko]

On 2020-05-28 07:55, Todd Zullinger wrote:
>  I don't know Evolution, but if it's presenting choices for
>  the multipart/alternative part, then that latter text/plain
>  part wouldn't be included as an option. 
I don't know Evolution either.  As expected, I see the same structure you presented.

Now, the question really is:  How did Evolution produce a message with non-matching
text/plain and text/html parts?

Maybe Patrick will find the answer with the Evolution folks.

-- 
The key to getting good answers is to ask good questions.

[Tim]

On Thu, 2020-05-28 at 07:14 +0800, Ed Greshko wrote:
>  Now I have to be distracted looking for a better theme.  :-) 
Isn't that what Microsoft does?

Gives you pointless user-configuration toys for the look of your
desktop, to distract you from the terrible user-experience of actually
using the OS.
 
-- 
 
uname -rsvp
Linux 3.10.0-1127.8.2.el7.x86_64 #1 SMP Tue May 12 16:57:42 UTC 2020 x86_64
 
Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.

[Tim]

On Wed, 2020-05-27 at 19:55 -0400, Todd Zullinger wrote:
>  I don't know Evolution, but if it's presenting choices for
>  the multipart/alternative part, then that latter text/plain
>  part wouldn't be included as an option. 
When you have a mail with multiple parts, there should be some sane
logic applied to handling it.  If you have a multi-part alternative
section, then you should get to see one of those parts by default,
ignoring the alternatives.  When you have another section tacked on
that is NOT one of the alternatives, it should always be displayed.


    plain                 HTML
    text          or      text
    message               message

                   &

                PGP
                signatures

                   &

                 list
                footers

Each of those blocks is a section.  Only the first two are an OR
situation, everything else is an AND.  The ORed sections should be
treated the same whether you're reading a message, or replying to it.

Quite how his Evolution created a blank plain-text session I don't
know, as I can't see an option for whether, or not, to also create a
plain text section when you're creating a HTML message.

I have noticed Evolution screw up when deleting parts of messages,
before.  Such as trying to trim out quotes.  I'd noticed that if I
tried to remove a few words, it'd often remove the entire quoted
message.  I'd have to copy the text to somewhere else, edit it, then
paste it back in again.  So it's message editor is a bit wacky, as far
as I'm concerned.

-- 
 
uname -rsvp
Linux 3.10.0-1127.8.2.el7.x86_64 #1 SMP Tue May 12 16:57:42 UTC 2020 x86_64
 
Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.

[Robert G (Doc) Savage]

On Thu, 2020-05-28 at 10:29 +0930, Tim via users wrote:
>  On Thu, 2020-05-28 at 07:14 +0800, Ed Greshko wrote:
>  > Now I have to be distracted looking for a better theme.  :-)
>  
>  Isn't that what Microsoft does?
>  
>  Gives you pointless user-configuration toys for the look of your
>  desktop, to distract you from the terrible user-experience of
>  actually
>  using the OS.
>   
>  -- 
>   
>  uname -rsvp
>  Linux 3.10.0-1127.8.2.el7.x86_64 #1 SMP Tue May 12 16:57:42 UTC 2020
>  x86_64
>   
>  Boilerplate:  All unexpected mail to my mailbox is automatically
>  deleted.
>  I will only get to see the messages that are posted to the mailing
>  list. 
Tim,
Ed,
Todd,
Patrick,

Would you fellows please take your HTML discussion somewhere else and
leave this thread to the original subject, which has yet to be
resolved.

Thanks.

--Doc Savage
  Fairview Heights, IL

[Samuel Sieb]

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.

[Patrick O'Callaghan]

On Thu, 2020-05-28 at 07:21 +0800, Ed Greshko wrote:
>  On 2020-05-28 06:34, Patrick O'Callaghan wrote:
>  
>  After being corrected by Todd, I see what you mean by the blank line.
>  
>  But....
>  
>  > 3.
>  > Content-Type: text/plain; charset="utf-8"
>  > MIME-Version: 1.0
>  > Content-Transfer-Encoding: base64
>  > Content-Disposition: inline
>  > (the base64 version of the text)
>  
>  Did you decode the block?  When I decode it I see the standard footer applied to all
> Fedora posts. 
No, I erroneously assumed it was the same text. So not in fact a third
alternative as I thought.

poc

Multipart issues (WAS: Re: Restart F32 WiFi on ThinkPad P72)

[Patrick O'Callaghan]

On Thu, 2020-05-28 at 13:20 +0930, Tim via users wrote:
>  On Wed, 2020-05-27 at 19:55 -0400, Todd Zullinger wrote:
>  > I don't know Evolution, but if it's presenting choices for
>  > the multipart/alternative part, then that latter text/plain
>  > part wouldn't be included as an option.
>  
>  When you have a mail with multiple parts, there should be some sane
>  logic applied to handling it.  If you have a multi-part alternative
>  section, then you should get to see one of those parts by default,
>  ignoring the alternatives.  When you have another section tacked on
>  that is NOT one of the alternatives, it should always be displayed.
>  
>  
>      plain                 HTML
>      text          or      text
>      message               message
>  
>                     &
>  
>                  PGP
>                  signatures
>  
>                     &
>  
>                   list
>                  footers
>  
>  Each of those blocks is a section.  Only the first two are an OR
>  situation, everything else is an AND.  The ORed sections should be
>  treated the same whether you're reading a message, or replying to it.
>  
>  Quite how his Evolution created a blank plain-text session I don't
>  know, as I can't see an option for whether, or not, to also create a
>  plain text section when you're creating a HTML message.
>  
>  I have noticed Evolution screw up when deleting parts of messages,
>  before.  Such as trying to trim out quotes.  I'd noticed that if I
>  tried to remove a few words, it'd often remove the entire quoted
>  message.  I'd have to copy the text to somewhere else, edit it, then
>  paste it back in again.  So it's message editor is a bit wacky, as far
>  as I'm concerned. 
I'll try to take this up on the Evolution list, which (luckily) I
haven't done yet.

poc

Multipart issues (WAS: Re: Restart F32 WiFi on ThinkPad P72)

[Patrick O'Callaghan]

On Thu, 2020-05-28 at 12:12 +0100, Patrick O'Callaghan wrote:
>  On Thu, 2020-05-28 at 13:20 +0930, Tim via users wrote:
>  > On Wed, 2020-05-27 at 19:55 -0400, Todd Zullinger wrote:
>  > > I don't know Evolution, but if it's presenting choices for
>  > > the multipart/alternative part, then that latter text/plain
>  > > part wouldn't be included as an option.
>  > 
>  > When you have a mail with multiple parts, there should be some sane
>  > logic applied to handling it.  If you have a multi-part alternative
>  > section, then you should get to see one of those parts by default,
>  > ignoring the alternatives.  When you have another section tacked on
>  > that is NOT one of the alternatives, it should always be displayed.
>  > 
>  > 
>  >     plain                 HTML
>  >     text          or      text
>  >     message               message
>  > 
>  >                    &
>  > 
>  >                 PGP
>  >                 signatures
>  > 
>  >                    &
>  > 
>  >                  list
>  >                 footers
>  > 
>  > Each of those blocks is a section.  Only the first two are an OR
>  > situation, everything else is an AND.  The ORed sections should be
>  > treated the same whether you're reading a message, or replying to it.
>  > 
>  > Quite how his Evolution created a blank plain-text session I don't
>  > know, as I can't see an option for whether, or not, to also create a
>  > plain text section when you're creating a HTML message.
>  > 
>  > I have noticed Evolution screw up when deleting parts of messages,
>  > before.  Such as trying to trim out quotes.  I'd noticed that if I
>  > tried to remove a few words, it'd often remove the entire quoted
>  > message.  I'd have to copy the text to somewhere else, edit it, then
>  > paste it back in again.  So it's message editor is a bit wacky, as far
>  > as I'm concerned.
>  
>  I'll try to take this up on the Evolution list, which (luckily) I
>  haven't done yet.
>  
>  poc 

This is what I got from one of the Evolution developers:

   Right, this is more likely. Having evolution run from a terminal, there
   could be seen some runtime warnings related to WebKit, coming either
   from Evolution itself or from a WebKitWebProcess (maybe it's still in
   the system journal). That would just show there happened something, but
   not necessarily what or why.

   The composer (the UI part) asks the editor (on the WebKitWebProcess
   side) for the content, once in HTML once in plain text (can be in
   opposite order). Failing to get it should result in a stop of the send
   operation, if I recall correctly. But it seems it was able to read the
   HTML part and failed only with the plain text part.

   Checking the message itself, the text/plain part is not completely
   empty, it contains CRLF encoded in base64.

   The HTML part doesn't look like anything complicated, just the
   opposite, pretty simple code, without special characters (unless I
   overlooked any).

   Obviously only Robert can check if there's anything in his journal to
   indicate an Evolution problem.

   poc

[Robert G (Doc) Savage]

On Thu, 2020-05-28 at 00:37 -0700, Samuel Sieb wrote:
>  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. 
No. It was the final instance of four lines that repeat every time I
disconnect my copper Ethernet cable and the system tries to light up
the WiFi connection. In my next reply I'll send the entire output
following a restart.

>  What is the "lspci" line for your wifi device? 
# lspci
...
00:14.3 Network controller: Intel Corporation Wireless-AC 9560
[Jefferson Peak] (rev 10)
...

>  > 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. 
Because of a recent event where the opposite situation occurred -- wifi
but no copper connectivity -- I decided to perform this 3-step
experiment:

1. State immediately following a restart with copper Ethernet
connected:

$ rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
	Soft blocked: no
	Hard blocked: no
1: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no
2: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: yes

2. Disconnect copper Ethernet and allow NetworkManager to try setting
up wifi:

$ rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
	Soft blocked: no
	Hard blocked: no
1: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no
2: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no

3. Reconnect copper Ethernet and allow NetworkManager to finish:

$ rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
	Soft blocked: no
	Hard blocked: no
1: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no
2: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: yes

This test appears to show that NetworkManager is actually controlling
the Wireless LAN hard blocking. 

My working theory is to the problem is in NetworkManager.

--Doc Savage
  Fairview Heights, IL

[Robert G (Doc) Savage]

On Thu, 2020-05-28 at 00:37 -0700, Samuel Sieb wrote:
>  On 5/27/20 3:46 PM, Robert G (Doc) Savage via users wrote:
>  
>  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. 
No, it was just a group of four repeating lines. Here's the entire
output since rebooting yesterday:

Immediately after reboot, from  00:05:17 - 00:05:38

# journalctl -b | grep rfkill
May 29 00:05:17 tiger.protogeek.org kernel: thinkpad_acpi: rfkill
switch tpacpi_bluetooth_sw: radio is unblocked
May 29 00:05:19 tiger.protogeek.org systemd[1]: Listening on Load/Save
RF Kill Switch Status /dev/rfkill Watch.
May 29 00:05:19 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 29 00:05:24 tiger.protogeek.org systemd[1]: systemd-rfkill.service: 
Succeeded.
May 29 00:05:24 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'
May 29 00:05:24 tiger.protogeek.org kernel: audit: type=1131
audit(1590728724.799:94): 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 29 00:05:30 tiger.protogeek.org NetworkManager[1132]:
<info>  [1590728730.2538] rfkill2: found Wi-Fi radio killswitch (at
/sys/devices/pci0000:00/0000:00:14.3/ieee80211/phy0/rfkill2) (driver
iwlwifi)
May 29 00:05:30 tiger.protogeek.org NetworkManager[1132]:
<info>  [1590728730.2540] manager[0x560023bbe080]: rfkill: Wi-Fi
hardware radio set enabled
May 29 00:05:30 tiger.protogeek.org NetworkManager[1132]:
<info>  [1590728730.2540] manager[0x560023bbe080]: rfkill: WWAN
hardware radio set disabled
May 29 00:05:30 tiger.protogeek.org NetworkManager[1132]:
<info>  [1590728730.2638] manager: rfkill: Wi-Fi disabled by radio
killswitch; enabled by state file
May 29 00:05:30 tiger.protogeek.org NetworkManager[1132]:
<info>  [1590728730.2639] manager: rfkill: WWAN enabled by radio
killswitch; disabled by state file
May 29 00:05:30 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 29 00:05:30 tiger.protogeek.org NetworkManager[1132]:
<info>  [1590728730.4670] manager: rfkill: Wi-Fi now enabled by radio
killswitch
May 29 00:05:33 tiger.protogeek.org NetworkManager[1132]:
<info>  [1590728733.9596] manager: rfkill: Wi-Fi now disabled by radio
killswitch
May 29 00:05:38 tiger.protogeek.org systemd[1]: systemd-rfkill.service: 
Succeeded.
May 29 00:05:38 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'

Here I disconnected the copper Ethernet cable, from  00:07:33 -
00:18:14

May 29 00:07:33 tiger.protogeek.org kernel: rfkill: input handler
disabled
May 29 00:07:33 tiger.protogeek.org gsd-media-keys[8459]: Failed to
grab accelerator for keybinding settings:rfkill
May 29 00:07:57 tiger.protogeek.org kernel: rfkill: input handler
enabled
May 29 00:18:09 tiger.protogeek.org NetworkManager[1132]:
<info>  [1590729489.0225] manager: rfkill: Wi-Fi now enabled by radio
killswitch
May 29 00:18:09 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 29 00:18:14 tiger.protogeek.org systemd[1]: systemd-rfkill.service: 
Succeeded.
May 29 00:18:14 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'

Reconnected the copper Ethernet cable, from  00:31:43 - 00:31:48

May 29 00:31:43 tiger.protogeek.org NetworkManager[1132]:
<info>  [1590730303.2728] manager: rfkill: Wi-Fi now disabled by radio
killswitch
May 29 00:31:43 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 29 00:31:48 tiger.protogeek.org systemd[1]: systemd-rfkill.service: 
Succeeded.
May 29 00:31:48 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'

Several hours later, I disconnected the copper Ethernet cable again,
from  15:44:59 - 15:45:04

May 29 15:44:59 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 29 15:44:59 tiger.protogeek.org NetworkManager[1132]:
<info>  [1590785099.5945] manager: rfkill: Wi-Fi now enabled by radio
killswitch
May 29 15:45:04 tiger.protogeek.org systemd[1]: systemd-rfkill.service: 
Succeeded.
May 29 15:45:04 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'

Then reconnected it again, from  15:45:19 - 15:45:24

May 29 15:45:19 tiger.protogeek.org NetworkManager[1132]:
<info>  [1590785119.9723] manager: rfkill: Wi-Fi now disabled by radio
killswitch
May 29 15:45:19 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 29 15:45:24 tiger.protogeek.org systemd[1]: systemd-rfkill.service: 
Succeeded.
May 29 15:45:24 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'

I wish I could decode this output line by line in detail, but that's
behond my skill set. I long for the simple old days of ifup and ifdown.
 As I said in my last message about rfkill, I strongly suspect
NetworkManager is controlling these sequences.

--Doc Savage
  Fairview Heights, IL

[Samuel Sieb]

On 5/29/20 2:12 PM, Robert G (Doc) Savage via users wrote:
>  On Thu, 2020-05-28 at 00:37 -0700, Samuel Sieb wrote:
> > On 5/27/20 3:46 PM, Robert G (Doc) Savage via users wrote:
> >
> > 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.
>  
>  No, it was just a group of four repeating lines. Here's the entire
>  output since rebooting yesterday:
>  
>  Immediately after reboot, from  00:05:17 - 00:05:38
>  
>  # journalctl -b | grep rfkill 
I think you missed my comment about searching for "KILL".  Don't use 
grep, just run "journalctl -b".  That gets you a "less"-type
interaction 
with it.  You can search with "/" and then go up and down to see what's 
around it.  Start from the top and try to find where the wifi device 
gets initialized.

>  I wish I could decode this output line by line in detail, but
> that's
>  behond my skill set. I long for the simple old days of ifup and ifdown.
>    As I said in my last message about rfkill, I strongly suspect
>  NetworkManager is controlling these sequences. 
The "hard" block should only come from hardware.  If it was 
NetworkManager, it would be the "soft" block that gets set.
That is a very curious chain of events in the log.  Can you have both 
ethernet and wifi connected at the same time in windows?  When you 
unplug the ethernet, does wifi work then?

[Lester M Petrie]

On 5/30/20 5:25 PM, Samuel Sieb wrote:
>  On 5/29/20 2:12 PM, Robert G (Doc) Savage via users wrote:
> > On Thu, 2020-05-28 at 00:37 -0700, Samuel Sieb wrote:
> >> On 5/27/20 3:46 PM, Robert G (Doc) Savage via users wrote:
> >>
>  
>  The "hard" block should only come from hardware.  If it was
>  NetworkManager, it would be the "soft" block that gets set.
>  That is a very curious chain of events in the log.  Can you have both
>  ethernet and wifi connected at the same time in windows?  When you
>  unplug the ethernet, does wifi work then?
>  _______________________________________________ 
I don't know anything about the rest of this problem, but Windows will
allow you to have both a wifi connection and a wired connection. It even
will randomly use one or the other if they are both present.

-- 
Lester M Petrie

[Samuel Sieb]

On 5/30/20 2:44 PM, Lester M Petrie wrote:
>  On 5/30/20 5:25 PM, Samuel Sieb wrote:
> > On 5/29/20 2:12 PM, Robert G (Doc) Savage via users wrote:
> >> On Thu, 2020-05-28 at 00:37 -0700, Samuel Sieb wrote:
> >>> On 5/27/20 3:46 PM, Robert G (Doc) Savage via users wrote:
> >>>
> >
> > The "hard" block should only come from hardware.  If it was
> > NetworkManager, it would be the "soft" block that gets set.
> > That is a very curious chain of events in the log.  Can you have both
> > ethernet and wifi connected at the same time in windows?  When you
> > unplug the ethernet, does wifi work then?
> > _______________________________________________
>  
>  I don't know anything about the rest of this problem, but Windows will
>  allow you to have both a wifi connection and a wired connection. It even 
It was not a general question about windows, it was a specific question 
about his laptop.

>  will randomly use one or the other if they are both present. 
And that is a terrible situation if it's true.

[Ed Greshko]

On 2020-05-31 05:25, Samuel Sieb wrote:
>  The "hard" block should only come from hardware.  If it was
> NetworkManager, it would be the "soft" block that gets set.
>  
FWIW, that doesn't appear to be as clear cut as I expected.  I was able to resurrect a
lap top running F32/KDE.
It only has one WiFi adapter so I can't explain 0 an 3 below.  But here is what things
show.


With everything Normal

[egreshko@acer ~]$ rfkill list
0: acer-wireless: Wireless LAN
        Soft blocked: no
        Hard blocked: no
1: acer-bluetooth: Bluetooth
        Soft blocked: no
        Hard blocked: no
2: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no
3: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no

Used NetworkManger to place system in "Airplane" mode.  Wireless and Bluetooth
stopped working. 
I have a Bluetooth mouse.

[egreshko@acer ~]$ rfkill list
0: acer-wireless: Wireless LAN
        Soft blocked: yes
        Hard blocked: no
1: acer-bluetooth: Bluetooth
        Soft blocked: no
        Hard blocked: no
2: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no
3: phy0: Wireless LAN
        Soft blocked: yes
        Hard blocked: yes

Used NetworkManger to exit "Airplane" mode and then disabled Wifi.  Wireless and
Bluetooth stopped working.

[egreshko@acer ~]$ rfkill list
0: acer-wireless: Wireless LAN
        Soft blocked: yes
        Hard blocked: no
1: acer-bluetooth: Bluetooth
        Soft blocked: no
        Hard blocked: no
2: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no
3: phy0: Wireless LAN
        Soft blocked: yes
        Hard blocked: yes

Enabled Wifi via NetworkManager, Not in Airplane mode.  Used the physical button on laptop
to
disable Wifi.

[egreshko@acer ~]$ rfkill list
0: acer-wireless: Wireless LAN
        Soft blocked: yes
        Hard blocked: no
1: acer-bluetooth: Bluetooth
        Soft blocked: no
        Hard blocked: no
2: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no
3: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: yes

-- 
The key to getting good answers is to ask good questions.