Yes, I noticed it, in fact it seems to be the reg. domain of the ath9k (there is also an ath9k card plugged on the same board). But it is in contrast with what I found in the syslog: Nov 21 07:53:23 MrProper kernel: [ 9.591563] ath: Regpair used: 0x3a Nov 21 07:53:23 MrProper kernel: [ 9.591573] cfg80211: Updating information on frequency 5180 MHz with regulatory rule: Nov 21 07:53:23 MrProper kernel: [ 9.591581] cfg80211: (5140000 KHz - 5360000 KHz @ 80000 KHz), (N/A, 3000 mBm) [...] - 5360000 KHz @ 80000 KHz), (N/A, 3000 mBm) Nov 21 07:53:23 MrProper kernel: [ 9.591654] cfg80211: Updating information on frequency 5300 MHz with regulatory rule: Nov 21 07:53:23 MrProper kernel: [ 9.591661] cfg80211: (5140000 KHz - 5360000 KHz @ 80000 KHz), (N/A, 3000 mBm) Nov 21 07:53:23 MrProper kernel: [ 9.591668] cfg80211: Updating information on frequency 5320 MHz with regulatory rule: Nov 21 07:53:23 MrProper kernel: [ 9.591675] cfg80211: (5140000 KHz - 5360000 KHz @ 80000 KHz), (N/A, 3000 mBm where there are @80MHz frequency slots. Is it possible that the system, showing all these different reg. domains from different cards, chose the most constrained one? 2016-11-21 11:53 GMT+01:00 Michal Kazior <michal.kazior@xxxxxxxxx>: > On 21 November 2016 at 10:46, Matteo Grandi <iu5bdp@xxxxxxxxx> wrote: >> Dear Bob, Michal, all, >> >> I've just tried your advices (actually I already tried it following >> the wireless.wiki.kernel web pages) and I had a look at the syslog >> while I was typing the commands >> At the beginning I have this > [...] >> Other (hopefully) useful info: >> root@MrProper:~# iw reg get >> global >> country US: DFS-UNSET >> (2402 - 2472 @ 40), (3, 27), (N/A) >> (5170 - 5250 @ 40), (3, 17), (N/A) >> (5250 - 5330 @ 40), (3, 20), (0 ms), DFS >> (5490 - 5600 @ 40), (3, 20), (0 ms), DFS >> (5650 - 5710 @ 40), (3, 20), (0 ms), DFS >> (5735 - 5835 @ 40), (3, 30), (N/A) >> (57240 - 63720 @ 2160), (N/A, 40), (N/A) >> >> phy#2 >> country US: DFS-UNSET >> (2402 - 2472 @ 40), (3, 27), (N/A) >> (5170 - 5250 @ 40), (3, 17), (N/A) >> (5250 - 5330 @ 40), (3, 20), (0 ms), DFS >> (5490 - 5600 @ 40), (3, 20), (0 ms), DFS >> (5650 - 5710 @ 40), (3, 20), (0 ms), DFS >> (5735 - 5835 @ 40), (3, 30), (N/A) >> (57240 - 63720 @ 2160), (N/A, 40), (N/A) >> >> phy#0 >> country US: DFS-UNSET >> (2402 - 2472 @ 40), (3, 27), (N/A) >> (5170 - 5250 @ 40), (3, 17), (N/A) >> (5250 - 5330 @ 40), (3, 20), (0 ms), DFS >> (5490 - 5600 @ 40), (3, 20), (0 ms), DFS >> (5650 - 5710 @ 40), (3, 20), (0 ms), DFS >> (5735 - 5835 @ 40), (3, 30), (N/A) >> (57240 - 63720 @ 2160), (N/A, 40), (N/A) >> >> phy#1 >> country US: DFS-UNSET >> (2402 - 2472 @ 40), (3, 27), (N/A) >> (5170 - 5250 @ 40), (3, 17), (N/A) >> (5250 - 5330 @ 40), (3, 20), (0 ms), DFS >> (5490 - 5600 @ 40), (3, 20), (0 ms), DFS >> (5650 - 5710 @ 40), (3, 20), (0 ms), DFS >> (5735 - 5835 @ 40), (3, 30), (N/A) >> (57240 - 63720 @ 2160), (N/A, 40), (N/A) >>[...] >> >> Checking on Internet I didn't find a working solution, and the data >> rate stucks to 120Mbps MCS7. >> For me it still a mistery, I hope in your help. > > Note the "@ 40" for all frequency ranges (except 60GHz band). Your > regulatory database seems to be limiting you to 40 MHz (it's probably > very old/ out of date). You'll need to update it to be able to use 80 > MHz. > > > Michal
