It seems today update I lost wifi support, that i used yesterday without problems
today kernel: 4.16.10-300.fc28.x86_64
yesterday kernel: kernel-4.16.8-300.fc28.x86_64
other possible related packages: NetworkManager-openvpn.x86_64 1:1.8.4-1.fc28
NetworkManager-openvpn-gnome.x86_64 1:1.8.4-1.fc28
May 24 09:06:07 ope46 NetworkManager[735]: <info> [1527145567.4812] wifi-nl80211: (wlp3s0): using nl80211 for WiFi device control May 24 09:06:07 ope46 NetworkManager[735]: <info> [1527145567.4816] device (wlp3s0): driver supports Access Point (AP) mode May 24 09:06:07 ope46 NetworkManager[735]: <info> [1527145567.4832] manager: (wlp3s0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/3) May 24 09:06:07 ope46 NetworkManager[735]: <info> [1527145567.4856] device (wlp3s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
then many of this type:
May 24 09:43:22 ope46 NetworkManager[735]: <info> [1527147802.1365] device (wlp3s0): set-hw-addr: s et MAC address to AA:8F:A1:D9:3B:44 (scanning) May 24 09:43:22 ope46 kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready May 24 09:43:22 ope46 NetworkManager[735]: <info> [1527147802.1659] device (wlp3s0): supplicant interface state: inactive -> disabled May 24 09:43:22 ope46 NetworkManager[735]: <info> [1527147802.1662] device (wlp3s0): supplicant interface state: disabled -> inactive May 24 09:43:22 ope46 wpa_supplicant[663]: wlp3s0: Reject scan trigger since one is already pending
In Gnome control center settings, in WIFI section I see
No WI-FI Adapter Found Make sure you have a WI-FI adapter plugged and turned on
with nmcli [root@ope46 firmware]# nmcli con up AndroidAP-notepro Error: Connection activation failed: No suitable device found for this connection. [root@ope46 firmware]#
Any one else?
Thanks Gianluca
On 05/24/2018 07:31 AM, Gianluca Cecchi wrote:
It seems today update I lost wifi support, that i used yesterday without problems
What is the device including chipset and how is it connected?
today kernel: 4.16.10-300.fc28.x86_64
yesterday kernel: kernel-4.16.8-300.fc28.x86_64
Try booting with the previous kernel and see if that changes anything.
other possible related packages: NetworkManager-openvpn.x86_64 1:1.8.4-1.fc28 NetworkManager-openvpn-gnome.x86_64 1:1.8.4-1.fc28
Were there any other NetworkManager or Gnome packages updated?
May 24 09:06:07 ope46 NetworkManager[735]: <info> [1527145567.4812] wifi-nl80211: (wlp3s0): using nl80211 for WiFi device control May 24 09:06:07 ope46 NetworkManager[735]: <info> [1527145567.4816] device (wlp3s0): driver supports Access Point (AP) mode May 24 09:06:07 ope46 NetworkManager[735]: <info> [1527145567.4832] manager: (wlp3s0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/3) May 24 09:06:07 ope46 NetworkManager[735]: <info> [1527145567.4856] device (wlp3s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
The kernel driver is loaded and NetworkManager knows it exists, but for some reason it considers it to be unavailable.
May 24 09:43:22 ope46 NetworkManager[735]: <info> [1527147802.1365] device (wlp3s0): set-hw-addr: s et MAC address to AA:8F:A1:D9:3B:44 (scanning) May 24 09:43:22 ope46 kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready May 24 09:43:22 ope46 NetworkManager[735]: <info> [1527147802.1659] device (wlp3s0): supplicant interface state: inactive -> disabled May 24 09:43:22 ope46 NetworkManager[735]: <info> [1527147802.1662] device (wlp3s0): supplicant interface state: disabled -> inactive May 24 09:43:22 ope46 wpa_supplicant[663]: wlp3s0: Reject scan trigger since one is already pending
It's trying to scan, but something's wrong.
What is the output of "iw dev wlp3s0 scan"?
[root@ope46 firmware]#
I see that you're in a directory called "firmware". Is that relevant?
On Thu, May 24, 2018 at 6:07 PM, Samuel Sieb samuel@sieb.net wrote:
On 05/24/2018 07:31 AM, Gianluca Cecchi wrote:
It seems today update I lost wifi support, that i used yesterday without problems
What is the device including chipset and how is it connected?
03:00.0 Network controller: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
today kernel: 4.16.10-300.fc28.x86_64
yesterday kernel: kernel-4.16.8-300.fc28.x86_64
Try booting with the previous kernel and see if that changes anything.
Actually it seems I solved, or better, for some reason the wifi was disconnected, but from a sw point of view, not with the buttons combination, that are Fn+F2 in my case. See below
other possible related packages:
NetworkManager-openvpn.x86_64 1:1.8.4-1.fc28 NetworkManager-openvpn-gnome.x86_64 1:1.8.4-1.fc28
Were there any other NetworkManager or Gnome packages updated?
No it seems not
I was in a directory named "firmware" (/lib/firmware) because I was verifying my version of microcode, preparing to update with latest one released by Intel, not related.
What I found is that I didn't noticed in control manager of Gnome, in settings --> Wi-Fi I had in top right of the bar, here the image
https://drive.google.com/file/d/1l8CCL0tm_KGhDig7ypuxI_UGpyTHv7iS/view?usp=s...
switched to off... I don't know why. I switched to On and all went good
I have a suspect. I was already connected to cable lan and I wanted to connect also to wifi (something I'm often doing to open a VPN through the wifi connection). One possibility is that in new release if you are already connected through cable lan, wifi becomes disabled... I have to verify Or it was only a mis-typing at my side... Now after booting today, I'm using wifi without problems but I have not my lan cable connected
Gianluca
2018-05-24 11:31 GMT-03:00 Gianluca Cecchi gianluca.cecchi@gmail.com:
It seems today update I lost wifi support, that i used yesterday without problems
today kernel: 4.16.10-300.fc28.x86_64
yesterday kernel: kernel-4.16.8-300.fc28.x86_64
I'm facing the same problem but with an earlier version of Fedora and kernel:
# rpm -qa | grep ^kernel-4 kernel-4.16.7-100.fc26.x86_64 kernel-4.15.17-200.fc26.x86_64 kernel-4.15.16-200.fc26.x86_64 # uname -a Linux alderaan.marques 4.16.7-100.fc26.x86_64 #1 SMP Wed May 2 21:45:56 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
But I have a Broadcom controller:
08:00.0 Network controller: Broadcom Limited BCM43142 802.11b/g/n (rev 01)
I did find this in messages:
May 28 14:46:56 alderaan NetworkManager[1711]: <info> [1527529616.5374] audit: op="radio-control" arg="wireless-enabled:1" pid=2856 uid=1000 result="fail" reason="Not authorized to perform this operation"
I'm going to check if one of the earlier kernel works
On 05/28/2018 11:05 AM, Martín Marqués wrote:
2018-05-24 11:31 GMT-03:00 Gianluca Cecchi gianluca.cecchi@gmail.com:
It seems today update I lost wifi support, that i used yesterday without problems
today kernel: 4.16.10-300.fc28.x86_64
yesterday kernel: kernel-4.16.8-300.fc28.x86_64
I'm facing the same problem but with an earlier version of Fedora and kernel:
# rpm -qa | grep ^kernel-4 kernel-4.16.7-100.fc26.x86_64 kernel-4.15.17-200.fc26.x86_64 kernel-4.15.16-200.fc26.x86_64 # uname -a Linux alderaan.marques 4.16.7-100.fc26.x86_64 #1 SMP Wed May 2 21:45:56 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
But I have a Broadcom controller:
08:00.0 Network controller: Broadcom Limited BCM43142 802.11b/g/n (rev 01)
I did find this in messages:
May 28 14:46:56 alderaan NetworkManager[1711]: <info> [1527529616.5374] audit: op="radio-control" arg="wireless-enabled:1" pid=2856 uid=1000 result="fail" reason="Not authorized to perform this operation"
I'm going to check if one of the earlier kernel works
It's not a kernel issue, it's a privilege or selinux issue. What desktop (LXDE, Gnome, Xfce, etc.), display manager (lxdm, lightdm, etc.) are you using and is selinux enabled? Note that there is a problem if you're using the lightdm display manager and have pam-kwallet installed.
Also note that Fedora 26 is just about end of life. Think seriously about going to F27 or F28. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - IGNORE that man behind the keyboard! - - - The Wizard of OS - ----------------------------------------------------------------------
2018-05-28 15:18 GMT-03:00 Rick Stevens ricks@alldigital.com:
It's not a kernel issue, it's a privilege or selinux issue. What desktop (LXDE, Gnome, Xfce, etc.), display manager (lxdm, lightdm, etc.) are you using and is selinux enabled? Note that there is a problem if you're using the lightdm display manager and have pam-kwallet installed.
I'm using lightdm with plasma
I don't think it's a selinux issue:
# selinuxenabled # echo $? 0
# cat /etc/selinux/config
SELINUX=permissive # SELINUXTYPE= can take one of these three values: # targeted - Targeted processes are protected, # minimum - Modification of targeted policy. Only selected processes are protected. # mls - Multi Level Security protection. SELINUXTYPE=targeted
Also note that Fedora 26 is just about end of life. Think seriously about going to F27 or F28.
I'm well aware. Spare time to run the upgrade, while not interfering with work is a problem lately.
IAC, I plan to changing the spin-disk from my laptop and replace it with an SSD I bought, and I'm for sure going to do a clean installation.
Regards,
On 05/28/2018 11:31 AM, Martín Marqués wrote:
2018-05-28 15:18 GMT-03:00 Rick Stevens ricks@alldigital.com:
It's not a kernel issue, it's a privilege or selinux issue. What desktop (LXDE, Gnome, Xfce, etc.), display manager (lxdm, lightdm, etc.) are you using and is selinux enabled? Note that there is a problem if you're using the lightdm display manager and have pam-kwallet installed.
I'm using lightdm with plasma
I don't think it's a selinux issue:
# selinuxenabled # echo $? 0
# cat /etc/selinux/config
SELINUX=permissive # SELINUXTYPE= can take one of these three values: # targeted - Targeted processes are protected, # minimum - Modification of targeted policy. Only selected processes are protected. # mls - Multi Level Security protection. SELINUXTYPE=targeted
Also note that Fedora 26 is just about end of life. Think seriously about going to F27 or F28.
I'm well aware. Spare time to run the upgrade, while not interfering with work is a problem lately.
IAC, I plan to changing the spin-disk from my laptop and replace it with an SSD I bought, and I'm for sure going to do a clean installation.
See my statements about the interaction of lightdm and pam-kwallet. Edit your /etc/pam.d/lightdm file, comment out any lines referencing pam_kwallet.so and pam_kwallet5.so, save the edited file, log out and log back in. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - -"Jimmie crack corn and I don't care." What kind of a lousy attitude - - is THAT to have, huh? -- Dennis Miller - ----------------------------------------------------------------------
On Fri, May 25, 2018 at 9:07 AM, Gianluca Cecchi gianluca.cecchi@gmail.com wrote:
[snip]
Actually it seems I solved, or better, for some reason the wifi was disconnected, but from a sw point of view, not with the buttons combination, that are Fn+F2 in my case. See below
[snip]
What I found is that I didn't noticed in control manager of Gnome, in settings --> Wi-Fi I had in top right of the bar, here the image
https://drive.google.com/file/d/1l8CCL0tm_KGhDig7ypuxI_ UGpyTHv7iS/view?usp=sharing
switched to off... I don't know why. I switched to On and all went good
I have a suspect. I was already connected to cable lan and I wanted to connect also to wifi (something I'm often doing to open a VPN through the wifi connection). One possibility is that in new release if you are already connected through cable lan, wifi becomes disabled... I have to verify Or it was only a mis-typing at my side... Now after booting today, I'm using wifi without problems but I have not my lan cable connected
Gianluca
After doing some tests, I can confirm my suspects about different behavior depending on lan cable connected or not when opening the Gnome session. Some details
- boot into Gnome with lan cable connected: https://drive.google.com/file/d/1M9k6HalwQrDTHDtVagkMz1CQjxYk6af8/view?usp=s... You see what is the network line, but without a label... -> confusing
- if in this scenario I click on the right arrow: https://drive.google.com/file/d/19olKfBRwyjr-nezSxQUhrmgjBtY1qPl8/view?usp=s... You verify expanding that it is indeed relatd to wired lan settings
But there is no "direct" option to interact with wifi Even if you detach the lan cable, you get this: https://drive.google.com/file/d/1-VuZssh-XilIrA-hsn-915H7oOSezTFy/view?usp=s... So you loose the "no label" line related to wired network.
But even waiting for some time there is no wifi line appearing... You can go into Settings page (the bottom left icon in previous screenshots) and in Wi-Fi you see the available wireless networks (now I have no more the problem of wifi disabled, so I can connect).
Direct boot without lan cable connected: https://drive.google.com/file/d/1UBwzkiL_6UeNzNf2GP4N00ToRWeNvbcq/view?usp=s... You now see an explicit wireless line, with indication that it is not connected (in case none of the automatic-connect wifi networks is not available, otherwise you see the connection active)
Expanding the wifi line: https://drive.google.com/file/d/1d1B1ixchTWz8EI5TpiaIeOPYJbigEyzq/view?usp=s... So you see the choice for the wireless lan you want to connect to: https://drive.google.com/file/d/10-7z5ZsjYZpCL5_bAJUopDvzSnb_d-6M/view?usp=s...
Hope I have clarified.
In my opinion we have two things:
- wired network line without label and so a bit confusing - wireless options automatically hidden if you are connected through lan cable. This could be a feature or not depending on the final user. It would be nice if one can explicitly choose the behavior
Cheers, Gianluca
On 05/30/18 16:44, Gianluca Cecchi wrote:
After doing some tests, I can confirm my suspects about different behavior depending on lan cable connected or not when opening the Gnome session. Some details
Just as a test. Would it be possible to create a new user on the system and see if your tests produce the same results?
I could not get anything to look like what you've shown on my F28/Gnome VM.
On Wed, May 30, 2018 at 12:33 PM, Ed Greshko ed.greshko@greshko.com wrote:
On 05/30/18 16:44, Gianluca Cecchi wrote:
After doing some tests, I can confirm my suspects about different
behavior
depending on lan cable connected or not when opening the Gnome session. Some details
Just as a test. Would it be possible to create a new user on the system and see if your tests produce the same results?
I could not get anything to look like what you've shown on my F28/Gnome VM.
This morning I tried creating a new user pippo (the italian for Goofy ;-) but I have the same problem when I then logon into Gnome DE with that user. When I have the lan cable connected I see the empty line with the right-arrow on the right and I can click it and expand.
One note: I have many wired lan profiles, but only one (named p5p1) that is setup as dhcp and to connect automatically. Could it depend on this? Ed, how are your wired profiles configured, anything automatic?
Gianluca
On 06/07/18 20:26, Gianluca Cecchi wrote:
On Wed, May 30, 2018 at 12:33 PM, Ed Greshko <ed.greshko@greshko.com mailto:ed.greshko@greshko.com> wrote:
On 05/30/18 16:44, Gianluca Cecchi wrote: > After doing some tests, I can confirm my suspects about different behavior > depending on lan cable connected or not when opening the Gnome session. > Some details Just as a test. Would it be possible to create a new user on the system and see if your tests produce the same results? I could not get anything to look like what you've shown on my F28/Gnome VM.This morning I tried creating a new user pippo (the italian for Goofy ;-) but I have the same problem when I then logon into Gnome DE with that user. When I have the lan cable connected I see the empty line with the right-arrow on the right and I can click it and expand.
One note: I have many wired lan profiles, but only one (named p5p1) that is setup as dhcp and to connect automatically. Could it depend on this? Ed, how are your wired profiles configured, anything automatic?
I only have a single ethernet interface with the name enp0s3 and it is set to receive both IPv4 and IPv6 addresses automatically.
I've never configured additional LAN profiles since I have only one interface. Not sure what the value in that would be.
https://drive.google.com/open?id=1nOOmm_wA9T3TOUg-b-VoHAte3FYMRski
I noticed in your screenshots the "networking icon" seems to be missing. I have one to the right of the language chooser.
On Thu, Jun 7, 2018 at 4:02 PM, Ed Greshko ed.greshko@greshko.com wrote:
I've never configured additional LAN profiles since I have only one interface. Not sure what the value in that would be.
https://drive.google.com/open?id=1nOOmm_wA9T3TOUg-b-VoHAte3FYMRski
I noticed in your screenshots the "networking icon" seems to be missing. I have one to the right of the language chooser.
Exactly. I miss that icon and also the same icon and also the words "Wired Connected" on the line where you can drop down to see the options "Turn Off" and "Wired Settings". Not a big deal, but confusing. You could try to create a new profile where you assign another ip config and see if the behavior changes or not. Or other fedora users with more than one profile configured can confirm if it is only a problem of mine or a common one for which to open some sort of bugzilla.
Gianluca
On 06/08/18 14:31, Gianluca Cecchi wrote:
On Thu, Jun 7, 2018 at 4:02 PM, Ed Greshko <ed.greshko@greshko.com mailto:ed.greshko@greshko.com> wrote:
I've never configured additional LAN profiles since I have only one interface. Not sure what the value in that would be. https://drive.google.com/open?id=1nOOmm_wA9T3TOUg-b-VoHAte3FYMRski <https://drive.google.com/open?id=1nOOmm_wA9T3TOUg-b-VoHAte3FYMRski> I noticed in your screenshots the "networking icon" seems to be missing. I have one to the right of the language chooser.Exactly. I miss that icon and also the same icon and also the words "Wired Connected" on the line where you can drop down to see the options "Turn Off" and "Wired Settings". Not a big deal, but confusing. You could try to create a new profile where you assign another ip config and see if the behavior changes or not. Or other fedora users with more than one profile configured can confirm if it is only a problem of mine or a common one for which to open some sort of bugzilla.
OK, I have created another profile utilizing the same interface and configured it for a static IP address. I switched to the new profile and verified it worked.
I then rebooted.
After rebooting I had the same problem you are seeing. So, the issue is related to multiple profiles. And is easily reproduced.
I deleted the new profile and upon rebooting everything was back to normal.
I suppose you can now file a Bugzilla.
On Fri, Jun 8, 2018 at 8:53 AM, Ed Greshko ed.greshko@greshko.com wrote:
[snip]
After rebooting I had the same problem you are seeing. So, the issue is related to multiple profiles. And is easily reproduced.
I deleted the new profile and upon rebooting everything was back to normal.
I suppose you can now file a Bugzilla.
Thanks for confirming confusing behavior. Opened bug here: https://bugzilla.redhat.com/show_bug.cgi?id=1589128
we will see.
Gianluca
-
Ed Greshko -
Gianluca Cecchi -
Martín Marqués -
Rick Stevens -
Samuel Sieb