From: Dan Williams <dcbw@redhat.com>
To: Julien Cubizolles <j.cubizolles@free.fr>
Cc: linux-wireless@vger.kernel.org
Subject: Re: mwifiex problem: incompatible network settings
Date: Mon, 26 Oct 2015 11:10:14 -0500 [thread overview]
Message-ID: <1445875814.31216.18.camel@redhat.com> (raw)
In-Reply-To: <87wpu9632c.fsf@free.fr>
On Mon, 2015-10-26 at 16:51 +0100, Julien Cubizolles wrote:
> I can't connect anymore to my home wifi since upgrading my machine from
> Ubuntu 15.04 to Ubuntuy 15.10. I was previously running kernel 4.3.0-rc2
> from kernel.org without any problem. After the upgrade, and with the
> same kernel, I couldn't connect anymore. I built 4.3.0-rc7, and the
> problem remains. However, I can connect to the wifi access point from my
> Android phone.
>
> Here are the relevant lines from syslog. Let me know if you need more
> information.
The AP uses WPA, but the driver has been told that WPA is disabled. Are
you using wpa_supplicant (or NetworkManager, or something else?) to
control the WiFi, and if so what version is it?
Dan
> --8<---------------cut here---------------start------------->8---
> Oct 26 16:11:38 touco wpa_supplicant[734]: wlx6045bdf646b4: Trying to associate with f4:ca:e5:ef:be:18 (SSID='southcentral' freq=2462 MHz)
> Oct 26 16:11:38 touco wpa_supplicant[734]: wlx6045bdf646b4: CTRL-EVENT-ASSOC-REJECT status_code=1
> Oct 26 16:11:38 touco kernel: [ 66.745281] usb 1-3: info: trying to associate to 'southcentral' bssid f4:ca:e5:ef:be:18
> Oct 26 16:11:38 touco kernel: [ 66.745289] usb 1-3: info: mwifiex_is_network_compatible: failed: wpa_ie=0xdd wpa2_ie=0x0 WEP=d WPA=d WPA2=d EncMode=0xfac02 privacy=0x1
> Oct 26 16:11:38 touco kernel: [ 66.745291] usb 1-3: Incompatible network settings
> Oct 26 16:11:38 touco kernel: [ 66.745294] usb 1-3: info: association to bssid f4:ca:e5:ef:be:18 failed
> --8<---------------cut here---------------end--------------->8---
>
>
> The machine is a Microsoft Surface Pro. I've been having a lot of
> problems getting the wifi to work but never this particular one, and
> they were all fixed in 4.3.0-rc2.
>
> Julien.
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-10-26 16:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 15:51 mwifiex problem: incompatible network settings Julien Cubizolles
2015-10-26 16:10 ` Dan Williams [this message]
2015-10-26 21:50 ` Julien Cubizolles
2015-10-27 15:11 ` Dan Williams
2015-10-27 18:55 ` Amitkumar Karwar
2015-10-27 21:44 ` Julien Cubizolles
2015-10-28 14:50 ` Dan Williams
2015-10-28 21:38 ` Julien Cubizolles
2015-10-29 12:27 ` Amitkumar Karwar
2015-10-29 15:16 ` Dan Williams
2015-10-30 10:34 ` Amitkumar Karwar
2015-11-04 22:04 ` Julien Cubizolles
2015-11-05 8:59 ` Amitkumar Karwar
2015-11-07 7:38 ` Julien Cubizolles
2015-11-25 14:22 ` Amitkumar Karwar
2015-12-01 10:35 ` Julien Cubizolles
2015-12-01 10:36 ` Amitkumar Karwar
-- strict thread matches above, loose matches on Subject: below --
2015-10-29 14:29 Ujjal Roy
2015-10-30 10:27 ` Amitkumar Karwar
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=1445875814.31216.18.camel@redhat.com \
--to=dcbw@redhat.com \
--cc=j.cubizolles@free.fr \
--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).