Comment 22 for bug 331092

Here's a fresh dmesg, more information like lspci output is in the initial bug report. I am in the Netherlands (ETSI region), both AP's I tested were sold here (I can select a country on the WNHDE111, this is set to NL, too), and set to automatically choose a free channel. Both AP's are discovered with pre-crda kernels (2.8.28-3 or so) and Windows. I'm not sure if it detects any 5GHz AP, I'll try to find overlapping channels between US and ETSI spectrums and see if that works.

Is there any way to see which regulatory domain was selected? It seems that iw only provides a reg set, no reg get command. iw reg set NL fixes it, but it's definitely a step back from working out-of-the-box like it did before crda.

The output after iw reg set:
[ 1274.636780] cfg80211: Calling CRDA for country: NL
[ 1274.675326] cfg80211: Regulatory domain changed to country: NL
[ 1274.675334] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 1274.675340] (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[ 1274.675345] (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[ 1274.675349] (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[ 1274.675353] (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm)
[ 1376.821314] wlan0: authenticate with AP 00:1e:2a:de:14:bd
[ 1377.020556] wlan0: authenticate with AP 00:1e:2a:de:14:bd
[ 1377.021019] wlan0: authenticated
[ 1377.021025] wlan0: associate with AP 00:1e:2a:de:14:bd
[ 1377.021845] wlan0: RX AssocResp from 00:1e:2a:de:14:bd (capab=0x111 status=0 aid=1)
[ 1377.021851] wlan0: associated