Hi, guys:
Recently I got a atheros mini-PCIE wifi module AR5B22, so I download
the latest version of compat-driver(compat-drivers-2013-03-28.tar.gz),
and build it for armel on my arm board, it works great but with one
little problem:
If I connect to an inscure AP then change to a WEP/WPA AP, I can't
connect the inscure one again, I have to run "modprobe -r ath9k;
modprobe ath9k" to connect the inscure AP.
I think this may be a bug in the ath9k driver, I also search this
bug on web but without an answer, so I send this letter for help.
Any advice would be grateful, thanks.
Wally
Hi, Adrian:
Here is it's wiki:http://wikidevi.com/wiki/Atheros_AR5B22
As I modprobe ath9k. dmesg give these messages:
----------------------------------------------------------------------
[49603.281250] compat-drivers backport release:
compat-drivers-2013-03-28
[49603.281250] Backport based on linux-next.git next-20130328
[49603.281250] compat.git: linux-next.git
[49603.367187] cfg80211: Calling CRDA to update world regulatory domain
[49603.609375] ath: EEPROM regdomain: 0x60
[49603.609375] ath: EEPROM indicates we should expect a direct regpair
map
[49603.609375] ath: Country alpha2 being used: 00
[49603.609375] ath: Regpair used: 0x60
[49603.609375] ieee80211 phy0: Selected rate control algorithm
'ath9k_rate_control'
[49603.609375] Registered led device: ath9k-phy0
[49603.609375] ieee80211 phy0: Atheros AR9462 Rev:2 mem=0xe1300000,
irq=48
-----------------------------------------------------------------------
so it seems ath9k probe this chip as Atheros AR9462. do you have
some idea?
Wally
於 三，2013-05-08 於 15:46 -0700，Adrian Chadd 提到：
> .. AR5B22? Which chip does that probe as?
>
>
>
> Adrian
>
>
> On 8 May 2013 05:25, Wally <[email protected]> wrote:
> > Hi, guys:
> > Recently I got a atheros mini-PCIE wifi module AR5B22, so I download
> > the latest version of compat-driver(compat-drivers-2013-03-28.tar.gz),
> > and build it for armel on my arm board, it works great but with one
> > little problem:
> >
> > If I connect to an inscure AP then change to a WEP/WPA AP, I can't
> > connect the inscure one again, I have to run "modprobe -r ath9k;
> > modprobe ath9k" to connect the inscure AP.
> >
> > I think this may be a bug in the ath9k driver, I also search this
> > bug on web but without an answer, so I send this letter for help.
> >
> > Any advice would be grateful, thanks.
> >
> > Wally
> >
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> > the body of a message to [email protected]
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
.. AR5B22? Which chip does that probe as?
Adrian
On 8 May 2013 05:25, Wally <[email protected]> wrote:
> Hi, guys:
> Recently I got a atheros mini-PCIE wifi module AR5B22, so I download
> the latest version of compat-driver(compat-drivers-2013-03-28.tar.gz),
> and build it for armel on my arm board, it works great but with one
> little problem:
>
> If I connect to an inscure AP then change to a WEP/WPA AP, I can't
> connect the inscure one again, I have to run "modprobe -r ath9k;
> modprobe ath9k" to connect the inscure AP.
>
> I think this may be a bug in the ath9k driver, I also search this
> bug on web but without an answer, so I send this letter for help.
>
> Any advice would be grateful, thanks.
>
> Wally
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
於 四，2013-05-09 於 09:54 +0530，Sujith Manoharan 提到：
> Wally wrote:
> > Recently I got a atheros mini-PCIE wifi module AR5B22, so I download
> > the latest version of compat-driver(compat-drivers-2013-03-28.tar.gz),
> > and build it for armel on my arm board, it works great but with one
> > little problem:
> >
> > If I connect to an inscure AP then change to a WEP/WPA AP, I can't
> > connect the inscure one again, I have to run "modprobe -r ath9k;
> > modprobe ath9k" to connect the inscure AP.
> >
> > I think this may be a bug in the ath9k driver, I also search this
> > bug on web but without an answer, so I send this letter for help.
>
> What commands do you use to connect to the APs ? Also, can you post the
> kernel log / wpa_supplicant log when the issue happens ?
>
> Sujith
Hi, Sujjth:
I do following steps to reproduce this problem:
/**********************************************************************/
first step, I connect to an inscure AP
1. sudo iwconfig wlan0 mode managed key off essid "dlink FRANCE"
2. sudo dhclient wlan0
dmesg give these messages:
[ 224.937500] wlan0: authenticate with 00:1c:f0:eb:9a:ed
[ 224.945312] wlan0: send auth to 00:1c:f0:eb:9a:ed (try 1/3)
[ 224.953125] wlan0: authenticated
[ 224.953125] ath9k 0000:01:00.0: wlan0: disabling HT as WMM/QoS is not
supported by the AP
[ 224.953125] ath9k 0000:01:00.0: wlan0: disabling VHT as WMM/QoS is
not supported by the AP
[ 224.960937] wlan0: associate with 00:1c:f0:eb:9a:ed (try 1/3)
[ 224.960937] wlan0: RX AssocResp from 00:1c:f0:eb:9a:ed (capab=0x421
status=0 aid=2)
[ 224.960937] wlan0: associated
second step, I connect to another WEP AP:
1. sudo dhclient -r
2. sudo iwconfig wlan0 mode managed essid "sw-wifi"
3. sudo wpa_supplicant -B -D wext -i wlan0 -c ./auth_file
4. sudo dhclient wlan0
dmesg give these messages:
[ 1425.843750] wlan0: deauthenticating from 00:1c:f0:eb:9a:ed by local
choice (reason=3)
[ 1436.296875] wlan0: authenticate with 00:26:5a:ff:c9:6d
[ 1436.312500] wlan0: send auth to 00:26:5a:ff:c9:6d (try 1/3)
[ 1436.312500] wlan0: deauthenticating from 00:26:5a:ff:c9:6d by local
choice (reason=3)
[ 1436.312500] wlan0: authenticate with 00:26:5a:ff:c9:6d
[ 1436.328125] wlan0: send auth to 00:26:5a:ff:c9:6d (try 1/3)
[ 1436.328125] wlan0: send auth to 00:26:5a:ff:c9:6d (try 2/3)
[ 1436.328125] wlan0: authenticated
[ 1436.328125] ath9k 0000:01:00.0: wlan0: disabling HT/VHT due to
WEP/TKIP use
[ 1436.328125] ath9k 0000:01:00.0: wlan0: disabling HT as WMM/QoS is not
supported by the AP
[ 1436.328125] ath9k 0000:01:00.0: wlan0: disabling VHT as WMM/QoS is
not supported by the AP
[ 1436.335937] wlan0: associate with 00:26:5a:ff:c9:6d (try 1/3)
[ 1436.335937] wlan0: RX AssocResp from 00:26:5a:ff:c9:6d (capab=0x431
status=0 aid=16)
[ 1436.335937] wlan0: associated
third step, I reconnect the inscure AP agian and failed:
1. sudo dhclient -r
2. sudo killall wpa_supplicant
2. sudo iwconfig wlan0 mode managed key off essid "dlink FRANCE"
3. sudo dhclient wlan0 <-- system can't get an IP forever...
dmesg give these messages:
[ 2049.585937] wlan0: deauthenticating from 00:26:5a:ff:c9:6d by local
choice (reason=3)
[ 2049.609375] cfg80211: Calling CRDA to update world regulatory domain
/**********************************************************************/
very weird, at third step, dmesg only print two messages, and not
start to do authenticate anymore. if I retry second step, it still can
connect WEP/WPA APs.
Hope this messages helps. the attach file is my auth_file using in
second step.
Wally
Wally wrote:
> Recently I got a atheros mini-PCIE wifi module AR5B22, so I download
> the latest version of compat-driver(compat-drivers-2013-03-28.tar.gz),
> and build it for armel on my arm board, it works great but with one
> little problem:
>
> If I connect to an inscure AP then change to a WEP/WPA AP, I can't
> connect the inscure one again, I have to run "modprobe -r ath9k;
> modprobe ath9k" to connect the inscure AP.
>
> I think this may be a bug in the ath9k driver, I also search this
> bug on web but without an answer, so I send this letter for help.
What commands do you use to connect to the APs ? Also, can you post the
kernel log / wpa_supplicant log when the issue happens ?
Sujith
Ah, right. An AR9462.
Odd. It should be fine. I wonder if the same behaviour exists for
other NICs in that general family (AR9380, AR9485.)
Some code has shown up recently in the reference driver that does
funny things with the keycache as a work-around for some bug. I don't
know what the bug is yet though.
I'll go check it out and get back to the list.
Adrian
On 8 May 2013 18:28, Wally <[email protected]> wrote:
> Hi, Adrian:
> Here is it's wiki:http://wikidevi.com/wiki/Atheros_AR5B22
>
> As I modprobe ath9k. dmesg give these messages:
> ----------------------------------------------------------------------
> [49603.281250] compat-drivers backport release:
> compat-drivers-2013-03-28
> [49603.281250] Backport based on linux-next.git next-20130328
> [49603.281250] compat.git: linux-next.git
> [49603.367187] cfg80211: Calling CRDA to update world regulatory domain
> [49603.609375] ath: EEPROM regdomain: 0x60
> [49603.609375] ath: EEPROM indicates we should expect a direct regpair
> map
> [49603.609375] ath: Country alpha2 being used: 00
> [49603.609375] ath: Regpair used: 0x60
> [49603.609375] ieee80211 phy0: Selected rate control algorithm
> 'ath9k_rate_control'
> [49603.609375] Registered led device: ath9k-phy0
> [49603.609375] ieee80211 phy0: Atheros AR9462 Rev:2 mem=0xe1300000,
> irq=48
> -----------------------------------------------------------------------
> so it seems ath9k probe this chip as Atheros AR9462. do you have
> some idea?
>
> Wally
>
>
>
> ?? ?T?A2013-05-08 ?? 15:46 -0700?AAdrian Chadd ?????G
>> .. AR5B22? Which chip does that probe as?
>>
>>
>>
>> Adrian
>>
>>
>> On 8 May 2013 05:25, Wally <[email protected]> wrote:
>> > Hi, guys:
>> > Recently I got a atheros mini-PCIE wifi module AR5B22, so I download
>> > the latest version of compat-driver(compat-drivers-2013-03-28.tar.gz),
>> > and build it for armel on my arm board, it works great but with one
>> > little problem:
>> >
>> > If I connect to an inscure AP then change to a WEP/WPA AP, I can't
>> > connect the inscure one again, I have to run "modprobe -r ath9k;
>> > modprobe ath9k" to connect the inscure AP.
>> >
>> > I think this may be a bug in the ath9k driver, I also search this
>> > bug on web but without an answer, so I send this letter for help.
>> >
>> > Any advice would be grateful, thanks.
>> >
>> > Wally
>> >
>> >
>> > --
>> > To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
>> > the body of a message to [email protected]
>> > More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>