FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > ArchLinux > ArchLinux General Discussion

 
 
LinkBack Thread Tools
 
Old 11-30-2011, 12:08 AM
scrat
 
Default wireless regulatory crda

I have installed arch to a laptop CLI only ( just base and base-devlel
with wireless) and updated to the latest packages.


I have setup the wireless manually.
I am in the US and have a wireless access point by tenda (china) and the
access point is open no security.

My desktop arch install does not have this problem it works without error.

When I bring up the wlan0 interface the kernel log shows CRDA calling
for country US followed by CRDA calling for county CN and changing the
regulatory domain to CN.


Later it calls for the US regulatory domain set to US and wlan0 is
deauthenticated.


iw dev wlan0 connect ESSID causes wlan0 to be authenticated and wireless
sevice returns.


How does one set this crda thing up so it does not slay the wireless
connection?


Google doesn't have any info on how to fix this

This is from the log

Nov 29 19:37:50 lapdog kernel: [ 8.027994] cfg80211: Calling CRDA for
country: CN
Nov 29 19:37:50 lapdog kernel: [ 8.032220] cfg80211: Regulatory
domain changed to country: CN
Nov 29 19:37:50 lapdog kernel: [ 8.032226] cfg80211: (start_freq
- end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Nov 29 19:37:50 lapdog kernel: [ 8.032231] cfg80211: (2402000 KHz
- 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Nov 29 19:37:50 lapdog kernel: [ 8.032235] cfg80211: (5735000 KHz
- 5835000 KHz @ 40000 KHz), (N/A, 3000 mBm)




Nov 29 19:38:11 lapdog kernel: [ 31.076726] b43-phy0: Loading firmware
version 410.2160 (2007-05-26 15:32:10)
Nov 29 19:38:11 lapdog kernel: [ 31.164873] cfg80211: Calling CRDA for
country: US
Nov 29 19:38:11 lapdog kernel: [ 31.170527] cfg80211: Regulatory
domain changed to country: US
Nov 29 19:38:11 lapdog kernel: [ 31.170533] cfg80211: (start_freq
- end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Nov 29 19:38:11 lapdog kernel: [ 31.170538] cfg80211: (2402000 KHz
- 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
Nov 29 19:38:11 lapdog kernel: [ 31.170542] cfg80211: (5170000 KHz
- 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
Nov 29 19:38:11 lapdog kernel: [ 31.170546] cfg80211: (5250000 KHz
- 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 29 19:38:11 lapdog kernel: [ 31.170550] cfg80211: (5490000 KHz
- 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 29 19:38:11 lapdog kernel: [ 31.170554] cfg80211: (5650000 KHz
- 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 29 19:38:11 lapdog kernel: [ 31.170558] cfg80211: (5735000 KHz
- 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
Nov 29 19:38:12 lapdog kernel: [ 32.336761] wlan0: authenticate with
c8:3a:35:40:47:88 (try 1)

Nov 29 19:38:12 lapdog kernel: [ 32.338348] wlan0: authenticated
Nov 29 19:38:12 lapdog kernel: [ 32.338379] wlan0: associate with
c8:3a:35:40:47:88 (try 1)
Nov 29 19:38:12 lapdog kernel: [ 32.340814] wlan0: RX AssocResp from
c8:3a:35:40:47:88 (capab=0x1 status=0 aid=3)

Nov 29 19:38:12 lapdog kernel: [ 32.340818] wlan0: associated
Nov 29 19:38:12 lapdog kernel: [ 32.341622] cfg80211: Calling CRDA for
country: CN
Nov 29 19:38:12 lapdog kernel: [ 32.345997] cfg80211: Regulatory
domain changed to country: CN
Nov 29 19:38:12 lapdog kernel: [ 32.346003] cfg80211: (start_freq
- end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Nov 29 19:38:12 lapdog kernel: [ 32.346006] cfg80211: (2402000 KHz
- 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Nov 29 19:38:12 lapdog kernel: [ 32.346010] cfg80211: (5735000 KHz
- 5835000 KHz @ 40000 KHz), (N/A, 3000 mBm)




Nov 29 19:43:12 lapdog kernel: [ 331.639351] wlan0: deauthenticated
from c8:3a:35:40:47:88 (Reason: 3)
Nov 29 19:43:12 lapdog kernel: [ 331.666833] cfg80211: Calling CRDA to
update world regulatory domain
Nov 29 19:43:12 lapdog kernel: [ 331.671216] cfg80211: World regulatory
domain updated:
Nov 29 19:43:12 lapdog kernel: [ 331.671222] cfg80211: (start_freq
- end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Nov 29 19:43:12 lapdog kernel: [ 331.671227] cfg80211: (2402000 KHz
- 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 29 19:43:12 lapdog kernel: [ 331.671231] cfg80211: (2457000 KHz
- 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Nov 29 19:43:12 lapdog kernel: [ 331.671235] cfg80211: (2474000 KHz
- 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Nov 29 19:43:12 lapdog kernel: [ 331.671239] cfg80211: (5170000 KHz
- 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 29 19:43:12 lapdog kernel: [ 331.671243] cfg80211: (5735000 KHz
- 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 29 19:43:12 lapdog kernel: [ 331.671451] cfg80211: Calling CRDA for
country: US
Nov 29 19:43:12 lapdog kernel: [ 331.677024] cfg80211: Regulatory
domain changed to country: US
Nov 29 19:43:12 lapdog kernel: [ 331.677029] cfg80211: (start_freq
- end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Nov 29 19:43:12 lapdog kernel: [ 331.677034] cfg80211: (2402000 KHz
- 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
Nov 29 19:43:12 lapdog kernel: [ 331.677038] cfg80211: (5170000 KHz
- 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
Nov 29 19:43:12 lapdog kernel: [ 331.677042] cfg80211: (5250000 KHz
- 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 29 19:43:12 lapdog kernel: [ 331.677045] cfg80211: (5490000 KHz
- 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 29 19:43:12 lapdog kernel: [ 331.677049] cfg80211: (5650000 KHz
- 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)


Anyone?
 
Old 11-30-2011, 12:21 AM
Karol Babioch
 
Default wireless regulatory crda

Hi,

Am 30.11.2011 02:08, schrieb scrat:
> How does one set this crda thing up so it does not slay the wireless
> connection?

Try something like "iw reg set CN"

Best regards,
Karol Babioch
 
Old 11-30-2011, 12:34 AM
scrat
 
Default wireless regulatory crda

On 11/29/2011 08:21 PM, Karol Babioch wrote:

Hi,

Am 30.11.2011 02:08, schrieb scrat:

How does one set this crda thing up so it does not slay the wireless
connection?

Try something like "iw reg set CN"

Best regards,
Karol Babioch


Yes I have already done that

I tries iw reg set Cn and iw reg set US still doesn't work
 
Old 11-30-2011, 05:43 AM
C Anthony Risinger
 
Default wireless regulatory crda

On Tue, Nov 29, 2011 at 7:34 PM, scrat <baho-utot@columbus.rr.com> wrote:
> On 11/29/2011 08:21 PM, Karol Babioch wrote:
>>
>> Hi,
>>
>> Am 30.11.2011 02:08, schrieb scrat:
>>>
>>> How does one set this crda thing up so it does not slay the wireless
>>> connection?
>>
>> Try something like "iw reg set CN"
>>
>> Best regards,
>> Karol Babioch
>>
> Yes I have already done that
>
> I tries iw reg set Cn and iw reg set US still doesn't work

what driver are you using? ath9k by chance?

i've been working with a friend on his cr-48 (the google netbook) and
his does something *very* similar to this, sometimes immediate,
sometimes hours later ... but his is quickly followed by (starts at
line 743):

http://paste.pocoo.org/show/514744/

.... iow ... BOOM!, meltdown, freeze.

also, how long has it been happening?

--

C Anthony
 
Old 11-30-2011, 10:13 AM
scrat
 
Default wireless regulatory crda

On 11/30/2011 01:43 AM, C Anthony Risinger wrote:

On Tue, Nov 29, 2011 at 7:34 PM, scrat<baho-utot@columbus.rr.com> wrote:

On 11/29/2011 08:21 PM, Karol Babioch wrote:

Hi,

Am 30.11.2011 02:08, schrieb scrat:

How does one set this crda thing up so it does not slay the wireless
connection?

Try something like "iw reg set CN"

Best regards,
Karol Babioch


Yes I have already done that

I tries iw reg set Cn and iw reg set US still doesn't work

what driver are you using? ath9k by chance?


Broadcomm and a netgear dongle that uses ath9k_htc



i've been working with a friend on his cr-48 (the google netbook) and
his does something *very* similar to this, sometimes immediate,
sometimes hours later ... but his is quickly followed by (starts at
line 743):

http://paste.pocoo.org/show/514744/

.... iow ... BOOM!, meltdown, freeze.

also, how long has it been happening?



Since installation. I am not getting thcall back trace as you are, just
the wireless going down, if I restart it is good util cfg80211 calls
crda for the reg domain and then its get deauthenticated.


The desktop doesn't have crda installed just the wireless-regdb db file
and it works, but it has netcfg.


On the lapdog I have found if I start wireless manually it works until
calling crda then it fails and doesn't restart.


If I start the wireless using netcfg the wireless will fails (as in the
log file ) but then it restarts. You don't see/notice the failure
because something restarts the wireless. Something in netcfg must be
restarting/authenticating the wireless.


I will need to look at netcfg scripts to see if I can determine what
going on.
 

Thread Tools




All times are GMT. The time now is 08:49 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org