On 02/07/2021 00:40, Jon LaBadie wrote:
On Thu, Jul 01, 2021 at 07:35:12AM -0300, George N. White III wrote:
On Thu, 1 Jul 2021 at 02:02, Jon LaBadie <jonfu@xxxxxxxxxx> wrote:
Laptop running F34 with an "Intel Cannon Point-LP CNVi [Wireless-AC]"
controller.
Every 10 seconds I get this error message (/var/log/messages):
wpa_supplicant[78893]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-22
A websearch shows this is not an uncommon problem though most
see it every 1 second, not 10 seconds. I've tried numerous
suggested solutions that were all ineffective (reboot after
changes). These included:
- downgrading wpa_supplicant (none available)
- downgrading NM (restored current)
- eliminating all NM interfaces except the active one
- eliminated the ethernet (wired) NM interface
- several .conf changes for NM and wpa_supplicant
Still the messages keep coming (200K+).
Any suggestions?
Have you seen <https://bugzilla.redhat.com/show_bug.cgi?id=1703745>?
This indicates the messages are due to wpa_supplicant not properly handling
your wifi hardware, so you may want to check upstream. This could
be an issue with the firmware version provided by Fedora.
My Fedora 33 system has wpa_supplicant messages in "the systemd(1)
journal as written by systemd-journald.service(8)." so either Fedora 34 has
changed logging for wpa_supplicant or you have a local wpa_supplicant
version/configuration.
This sort of problem often appears across multiple linux distros, so it is
worth
checking for similar issues on other distros, in particular Ubuntu and
Arch.
My bugzilla-foo is weak, I overlooked that one. Couple of things.
I'm not having connection problems at all.
Yes, most of the websearch results are Arch & Ubuntu
In that bugzilla report the messages the messages end with "retries=1",
as do most of the found reports. Mine do not.
Logging to /var/log/message is just my old school habit. systemD
journal gets them too.
wpa_supplicant is totally stock. Never even tried to look at config
before.
Does wifi work if wpa_supplicant service is disabled?
Well, what I would do in this case is to first do "lspci -v" and compare my hardware specs and
driver in use with that reported in the BZ to see how they match up. It is not inconceivable that
an error message may be the same while the underlying issue different than reported in a BZ.
--
Remind me to ignore comments which aren't germane to the thread.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
