From: "Antanas Uršulis" <antanas@cantab.net>
To: linux-wireless@vger.kernel.org
Subject: Re: [linuxwifi] Intel Centrino Ultimate N 6300 regression
Date: Thu, 22 Aug 2019 23:42:16 +0100 [thread overview]
Message-ID: <90e4da8a-10a6-2e2d-c3de-27f21e644f3e@cantab.net> (raw)
In-Reply-To: <CAG6aBkW09YFz4asHZkhWBUenBiT3dgb7iGXBCq8KkCM09QXjLg@mail.gmail.com>
I was investigating what appears to be the same issue on my T420
Thinkpad and at least found a workaround (and perhaps a clue for where
the bug could lie).
On 22/08/2019 01:12, Nigel Sollars wrote:
> Interesting to be sure, so here are the versions of kernel and wpa_supplicant,
>
> 5.2.9-200.fc30.x86_64
> wpa_supplicant-2.8-2.fc30.x86_64
Are you using NetworkManager by chance? I stumbled across a Red Hat bug
report[0] involving 'CTRL-EVENT-SCAN-FAILED ret=-22' and the proprietary
broadcom driver. A comment there[1] describes a workaround for their
issue, by making NetworkManager not randomise the MAC address during
access point scans.
Adopting that workaround also works for my Centrino Ultimate-N 6300 (rev
3e). Create a config file /etc/NetworkManager/conf.d/iwl.conf with contents:
[device]
match-device=driver:iwlwifi
wifi.scan-rand-mac-address=no
Then restart NetworkManager. Alternatively, downgrading wpa_supplicant
(to 2.7-r3 on Gentoo ~amd64) also works for me.
- Antanas
[0] https://bugzilla.redhat.com/show_bug.cgi?id=1703745
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1703745#c56
prev parent reply other threads:[~2019-08-22 22:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAG6aBkWDyGDtWX7X0t-FjynkYxpdhpZsAv4Ysw3dKf+iEu+mig@mail.gmail.com>
[not found] ` <5d4c34ea.1c69fb81.a7a36.5f7f.GMR@mx.google.com>
2019-08-08 19:58 ` Fwd: Delivery Status Notification (Failure) Nigel Sollars
[not found] ` <941b807b02962fadaf738942baf1621738872723.camel@intel.com>
2019-08-21 14:30 ` [linuxwifi] Intel Centrino Ultimate N 6300 regression Nigel Sollars
2019-08-21 21:45 ` Alexander Wetzel
2019-08-22 0:12 ` Nigel Sollars
2019-08-22 22:42 ` Antanas Uršulis [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=90e4da8a-10a6-2e2d-c3de-27f21e644f3e@cantab.net \
--to=antanas@cantab.net \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).