[arch-general] wireless regulatory crda

scrat baho-utot at columbus.rr.com
Wed Nov 30 06:13:54 EST 2011

On 11/30/2011 01:43 AM, C Anthony Risinger wrote:
> On Tue, Nov 29, 2011 at 7:34 PM, scrat<baho-utot at 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.

More information about the arch-general mailing list