Hello, Yes,I use 5Ghz and I'm aware of dynamic rate scaling (i monitored it with iwconfig before). It's just no matter how I load it i never shows speeds more than 520mbps (very rarely i get 600 but it doesn't last even 1 second). I load it with iperf and the max *real* speed I get is about 240mbps in TCP mode. Under Windows 7, I can see 866mbps when there is load. Is there a reason why it avoids speeds bigger than 520mbps? Also is it normal to get only half of the connection speed with iperf? Regards, Nick. On 28.05.2015 00:02, Dan Williams wrote: > On Wed, 2015-05-27 at 22:46 +0300, Nick Dimov wrote: >> Hello everyone. >> I updated the regulatory database from here >> https://www.kernel.org/pub/software/network/wireless-regdb/ (just copied >> the regulatory.bin and the public key) and the problem is gone! Thank to >> all of you and especially to Emmanuel Grumbach for suggesting this. >> >> Now another question - how to make it connect at 866mbps or at least >> something close to it? Any ideas? > iwlwifi does dynamic rate scaling, so you'll almost never see 866mbps. > When traffic is idle it drops back to 1mbit rates and then when traffic > starts, scales up from there. Also, I'm pretty sure you'll never get > 866mbps in the 2.4GHz band due to lack of bandwidth there, you'll have > to go 5GHz for that. > > Use "iw dev <ifname> link" to see the current rate. > > Dan > >> Thanks you, >> Nick. >> >> On 27.05.2015 21:34, Emmanuel Grumbach wrote: >>> On Wed, May 27, 2015 at 6:55 PM, Dan Williams <dcbw@xxxxxxxxxx> wrote: >>>> On Wed, 2015-05-27 at 02:44 +0300, Nick Dimov wrote: >>>>> Hello, >>>>> thank you for your response. I attach the full syslog since the last >>>>> boot which contains some disconnects. I enabled debug mode for >>>>> wpa_supplicant with -dd option (let me know if you need anything else). >>>>> >>>>> I also tried connecting directly, i.e. without NetworkManager but >>>>> manually with wpa_supplicant and I still get disconnects, howvever >>>>> wpa_supplicant gives different logs with different drivers. Please, see >>>>> the file wifi.log (you can see there the driver i used in >>>>> wpa_supplicant, that log doesn't have the debug activated but let me >>>>> know if you need that too) >>>> So if NM isn't involved in your later runs (and it's not, looking at the >>>> logs), then I'm not sure what the issue could be except something in the >>>> driver. >>>> >>>> mai 27 02:31:54 nick-G55VW wpa_supplicant[1565]: nl80211: Event message >>>> available >>>> mai 27 02:31:54 nick-G55VW wpa_supplicant[1565]: nl80211: Drv Event 20 >>>> (NL80211_CMD_DEL_STATION) received for wlan5 >>>> mai 27 02:31:54 nick-G55VW wpa_supplicant[1565]: nl80211: Delete station >>>> d8:50:e6:da:1d:b4 >>>> mai 27 02:31:54 nick-G55VW kernel: wlan5: deauthenticating from >>>> d8:50:e6:da:1d:b4 by local choice (Reason: 3=DEAUTH_LEAVING) >>>> >>>> I don't see anything interesting around those lines, so I guess its up >>>> to Emmanuel now... the tracing he requests would be good to get. >>>> >>> I suspect a regulatory problem. This is why I asked what was the >>> channel used on 2.4GHz. On 5.2GHz we have seen bugs happening because >>> of the regulatory database being ancient on Ubuntu. 2.4GHz should rule >>> these problems out, unless we are talking about channel 12 and up or >>> something like that. >> -- >> 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 > -- 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
