Description of problem:
F33 was installed 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.
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
I just reverted downgrade of NM and System is back in failure state.
I could do some diagnostics if someone advises me.
The only changes related to Wi-Fi between 1.26.2 and 1.26.8 are:
$ git log --oneline --grep=wifi 1.26.2...1.26.8
8df18958ed05 libnm: fix tracking object state in NMClient cache
3cff6f294f84 wifi: fix caching ap-flags for supplicant-interface
5454681ab76e wifi: auto-activate devices as soon as the first scan finishes
2bec392e563b wifi: fix evaluating the scanning state for wpa-supplicant
def7533c64d6 core: recognize "wifi.scan-generate-mac-address-mask" as valid "NetworkManager.conf" option
9b8a60a9a315 shared: fix NM_CAST_STRV_CC() for "char **const" pointers
09c4fa5a6cae iwd: Fix a use after free
42d28ae2e8dd device/wifi: don't reset the SSID of a NMWifiAP to unknown
b5310115d1b9 wifi: re-add code for tracking a peers groups
bd5da809caee device/wifi: fix leak of NMSupplicantPeerInfo.peer_path in NMSupplicantInterface
ed9f63724a16 supplicant: fix crash in _scan_notify_allowed() when supplicant disconnects
If you know how to rebuild packages, it would be worth to try
reverting 5454681ab76e and 2bec392e563b (or even better, a git
Otherwise, please provide debug logs of NM and wpa_supplicant:
- set "level=TRACE" in the [logging] section of /etc/NetworkManager.conf
- set "RateLimitIntervalSec=0" in /etc/systemd/journald.conf to disable journal rate limiting
- add "-ddd" to OTHERARGS in /etc/sysconfig/wpa_supplicant
- reproduce the issue
- attach the output of "journalctl -u wpa_supplicant -u NetworkManager -b"
Note that the journal might contain sensitive information like MAC
addresses, IP addresses, SSIDs. Redact them before attaching the
file. If you prefer to not attach it here, you can send the file to me
at bgalvani. Thanks.
This bug also affects Fedora 34:
NetworkManager: <warn> [xxx.xxx] device (wlpXsX): Activation: (wifi) association took too long, failing activation
This bug makes WiFi connections on Intel Centrino Advanced-N 6200 devices unusable.
This adapter type is quite widespread and widely used, for example, in the Thinkpad T and P series.
Please set an appropriate priority and severity.
Device: "Intel Centrino Advanced-N 6200"
$ NetworkManager --version
As a temporary workaround until there is a fix, you can add a file /etc/NetworkManager/conf.d/99-wifi.conf containing:
This disables the randomization of the Wi-Fi MAC address during scans. This should help with the issue.
Dear Beniamino, the solution you suggested instantly fixes the issue.
How did you know - is the MAC randomization a regular cause for connection issues?
(In reply to q8311692 from comment #5)
> Dear Beniamino, the solution you suggested instantly fixes the issue.
> How did you know - is the MAC randomization a regular cause for connection
I sent logfiles to Beniamino before and then we tested the temporary workaround.
Regarding the bug he explained
>> that's because NM doesn't need to bring the interface down to
>> change the MAC. Bringing the interface down means that wpa_supplicant
>> flushes the list of APs and must rescan, which triggers the bug.
For me, another way to solve the problem is to use the wpa_supplicant from the dcaratti/wpa_supplicant COPR
sudo dnf copr enable dcaratti/wpa_supplicant
sudo dnf update
I'm facing the same issue on a thinkpad x230.
Additional to this bug, my boot process takes 2+mins to finish because its waiting for the NetworkManager-wait-online.service to finish (which almost always fails).
I forgot to mention that none of the workarounds listed in this page worked.
Intel Centrino Ultimate-N 6300
Network manager version: 1.26.8-1.fc33
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 33 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.