installed F33 from Fedora-WS-Live-33-1-2 on Dell Latitude E6410 with Intel Centrino Advanced-N 6200 Wifi adapter.
After installation Wifi worked fine.
rpm -qa | grep NetworkManager-wifi
After first upgrade Wifi stopped working. It seems to be scanning all the time for wifi networks but never connects.
systemctl status wpa_supplicant.service reports
CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
downgrading NetworkManager-wifi solved the problem
sudo dnf downgrade NetworkManager-wifi-1.26.8-1.fc33.x86_64
Tried to install F34, but in this case wifi never worked.
Could you please take a look at the currently open NetworkManager bugs to see if anything looks similar? If not, can you please file one. You can login to Bugzilla using the same Fedora login that you use here.
Additionally: did downgrading NetworkManager affect any other packages?
Downgrading NetworkManage included 8 Packages whose names began with “NetworkManager”.
I’m not too sure of how wpa_supplicant and NM interact nowdays but was the wpa_supplicant package also affected by the downgrade etc.?
wpa_supplicant package was affected by the system update wich raised the problem.
First I downgraded wpa_supplicant package. But this didn’t solve the problem.
Then I downgraded NetworkManager and this solved the problem.
Finally I upgraded wpa_supplicant again. ( wpa_supplicant-2.9-8.fc33.x86_64 )
Same with wifi firmware. ( iwl6000-firmware-184.108.40.206-119.fc33.noarch )
OK, so a few other packages are also involved. Did you reboot/restart the wpa_supplicant etc. services after downgrading/upgrading them? Otherwise the changed version would not neccesarily be active after the upgrade/downgrade.
(What I’m trying to do here is to pin point what package causes the issue, since your error message was from the wpa_supplicant service)
I rebooted after every downgrade/upgrade.
Finally only NetworkManager is downgraded.
I just reverted downgrade of NetworkManager (8 Packages, all named NetworkManager…) and problem is back.
That confirms it then. If you could add all this info in the bug too, that’ll help the maintainer narrow it down.
Since this is a regression, one could theoretically bisect the Network Manager source to see where this was introduced, but that requires building it from source etc.
systemctl status NetworkManager.service
● NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2021-05-05 04:01:57 EDT; 1 day 23h ago
Main PID: 813 (NetworkManager)
Tasks: 3 (limit: 6833)
CPU: 1min 44.054s
└─813 /usr/sbin/NetworkManager --no-daemon
Mai 07 03:42:30 fedora NetworkManager: <info> [1620373350.3754] Config: added 'auth_alg' value 'OPEN'
Mai 07 03:42:30 fedora NetworkManager: <info> [1620373350.3754] Config: added 'psk' value '<hidden>'
Mai 07 03:42:55 fedora NetworkManager: <warn> [1620373375.7243] device (wlp2s0): Activation: (wifi) association took too long, failing activation
Mai 07 03:42:55 fedora NetworkManager: <info> [1620373375.7244] device (wlp2s0): state change: config -> failed (reason 'ssid-not-found', sys-iface-state: 'managed>
Mai 07 03:42:55 fedora NetworkManager: <info> [1620373375.7450] device (wlp2s0): set-hw-addr: set MAC address to 02:E2:FE:7E:22:01 (scanning)
Mai 07 03:42:56 fedora NetworkManager: <warn> [1620373376.0584] device (wlp2s0): Activation: failed for connection 'erwin-public'
Mai 07 03:42:56 fedora NetworkManager: <info> [1620373376.0586] device (wlp2s0): supplicant interface state: inactive -> disconnected
Mai 07 03:42:56 fedora NetworkManager: <info> [1620373376.0587] device (wlp2s0): supplicant interface state: disconnected -> interface_disabled
Mai 07 03:42:56 fedora NetworkManager: <info> [1620373376.0592] device (wlp2s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Mai 07 03:42:56 fedora NetworkManager: <info> [1620373376.0714] device (wlp2s0): supplicant interface state: interface_disabled -> inactive
Maybe the reason of the problem are any modified timing conditions in NetworkManager.
I ran the system next to the access point for several hours and eventually a wifi connection was established. But after the next standby, the connection was gone again.