>>>>> [ 1058.936551] cfg80211: Calling CRDA to update world regulatory domain >>>>> [ 1058.945510] cfg80211: World regulatory domain updated: >>>>> [ 1058.945519] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) >>>>> [ 1058.945529] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) >>>>> [ 1058.945538] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) >>>>> [ 1058.945547] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) >>>>> [ 1058.945555] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) >>>>> [ 1058.945563] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) >>>>> [ 1058.945604] cfg80211: Calling CRDA for country: 97 >>>>> [ 1061.373997] ieee80211 phy1: channel change: 2417 -> 2422 failed (2). >>>>> [ 1061.682115] ieee80211 phy1: channel change: -1 -> 2422 failed (2). >>>>> [ 1061.682132] usb 10-1.2: restart device (7) >>>>> [ 1062.096523] cfg80211: Calling CRDA to update world regulatory domain >>>>> [ 1062.105469] cfg80211: World regulatory domain updated: >>>> >>>> Any idea what is going on here? Do I need a crda tool? Or is something >>>> else failing? >>> Yes, you need crda, if you haven't installed it already. >> >> Sorry, I forgot "update" there. So I asked if I would need to update >> crda. I just did that, but I just don't want to disconnect right now to >> see if it connects any faster. Those messages still appear every 16 >> seconds and spam my logs :( > Luis, do you know what causes these CRDA spamming? > (Also, the country code should be "DE" in his case, or?) After installing a new crda version *and* rebooting those messages only appear once now. New 3.1-rc1 kernel incompatible with old tools? Btw, isn't errno=28 a bit weird on setting the country code with crda? bernd@bathl ~>COUNTRY=DE crda Failed to set regulatory domain: -28 (28 = ENOSPC) Thanks, Bernd -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
