From: Albert Herranz <albert_herranz@yahoo.es>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Holger Schurig <hs4233@mail.mn-solutions.de>,
linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: Problems with "cfg80211: fix SME connect" commit
Date: Mon, 28 Sep 2009 11:04:10 -0700 (PDT) [thread overview]
Message-ID: <29413.68229.qm@web28307.mail.ukl.yahoo.com> (raw)
In-Reply-To: <1253779538.3868.14.camel@johannes.local>
Johannes Berg wrote:
> On Mon, 2009-09-21 at 18:11 +0200, Albert Herranz wrote:
>
>> Adding back "cfg80211: fix SME connect" and applying "cfg80211: don't
>> overwrite privacy setting" fixes the connection issue, but with a
>> introduces a small difference vs the previous working version.
>> There is now an extra "deauthenticating by local choice (reason=3)"
>> message in the logs.
>
>> [ 13.969153] b43-phy0 debug: Adding Interface type 2
>> [ 16.679249] wlan1: direct probe to AP 00:12:17:15:e7:79 (try 1)
>
>> * master-20090916 + "cfg80211: don't overwrite privacy setting"
>
>> [ 13.218613] b43-phy0 debug: Adding Interface type 2
>> [ 15.832582] wlan1: deauthenticating by local choice (reason=3)
>> [ 16.131599] wlan1: direct probe to AP 00:12:17:15:e7:79 (try 1)
>
> Very odd. Can you edit the deauthenticating message to show the
> BSSID/MAC address?
>
> johannes
Hi,
Sorry if this comes too late (I was on vacation).
Here's the output showing the BSSID/MAC address for completeness.
[ 1.307985] b43-sdio mmc1:0001:1: Chip ID 14e4:4318
[ 1.344244] b43-phy0: Broadcom 4318 WLAN found (core revision 9)
[ 1.372627] b43-phy0 debug: Found PHY: Analog 3, Type 2, Revision 7
[ 1.377416] b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 8
[ 1.417302] phy0: Selected rate control algorithm 'minstrel'
[ 4.462416] udev: renamed network interface wlan0 to wlan1
[ 11.064949] b43 ssb0:0: firmware: requesting b43/ucode5.fw
[ 11.118177] b43 ssb0:0: firmware: requesting b43-open/ucode5.fw
[ 11.197385] b43 ssb0:0: firmware: requesting b43-open/pcm5.fw
[ 11.268949] b43 ssb0:0: firmware: requesting b43-open/b0g0initvals5.fw
[ 11.347623] b43 ssb0:0: firmware: requesting b43-open/b0g0bsinitvals5.fw
[ 12.353406] b43-phy0: Loading OpenSource firmware version 410.31754
[ 12.359142] b43-phy0: Hardware crypto acceleration not supported by firmware
[ 12.369827] b43-phy0: QoS not supported by firmware
[ 12.741767] b43-phy0 debug: Chip initialized
[ 12.757540] b43-phy0 debug: PIO initialized
[ 12.764455] b43-phy0 debug: QoS disabled
[ 12.945116] b43-phy0 debug: Wireless interface started
[ 13.053151] b43-phy0 debug: Adding Interface type 2
[ 15.624121] wlan1: starting authentication with 00:12:17:15:e7:79
[ 15.630717] wlan1: deauthenticating from 00:12:17:15:e7:79 by local choice (reason=3)
[ 15.645151] wlan1: starting authentication with 00:12:17:15:e7:79
[ 15.665811] wlan1: direct probe to AP 00:12:17:15:e7:79 (try 1)
[ 15.681132] wlan1: direct probe responded
[ 15.687261] wlan1: authenticate with AP 00:12:17:15:e7:79 (try 1)
[ 15.701105] wlan1: authenticated
[ 15.707860] wlan1: starting association with 00:12:17:15:e7:79
[ 15.713877] wlan1: associate with AP 00:12:17:15:e7:79 (try 1)
[ 15.726949] wlan1: RX AssocResp from 00:12:17:15:e7:79 (capab=0x431 status=0 aid=1)
[ 15.740953] wlan1: associated
I'm using wpa_supplicant _without_ NM.
Cheers,
Albert
next prev parent reply other threads:[~2009-09-28 18:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-20 18:03 Problems with "cfg80211: fix SME connect" commit Albert Herranz
2009-09-21 6:45 ` Holger Schurig
2009-09-21 16:11 ` Albert Herranz
2009-09-24 8:05 ` Johannes Berg
2009-09-24 19:13 ` Hin-Tak Leung
2009-09-25 6:22 ` Johannes Berg
2009-09-25 15:54 ` Hin-Tak Leung
2009-09-26 11:39 ` Johannes Berg
2009-09-26 23:57 ` Hin-Tak Leung
2009-09-28 14:41 ` Johannes Berg
2009-09-30 21:17 ` Hin-Tak Leung
2009-09-30 21:20 ` Johannes Berg
2009-09-28 18:04 ` Albert Herranz [this message]
2009-09-28 18:55 ` Johannes Berg
2009-09-28 19:22 ` Hin-Tak Leung
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=29413.68229.qm@web28307.mail.ukl.yahoo.com \
--to=albert_herranz@yahoo.es \
--cc=hs4233@mail.mn-solutions.de \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).