@All the wireless AC speed seems somehow limited to 80 MBit/s at most on my wrt1900acs (With the router in line of sight). I used different builds and all the same result. People who also have this kind of speed problem can you please add to this https://github.com/kaloz/mwlwifi/issues/85 so this can be resolved. Or maybe if no one has this problem it is my laptop. Thank you all in advance. (for the N band there is a separate issue)
Topic: Update on Linksys WRT1900AC support
The content of this topic has been archived between 16 Sep 2014 and 7 May 2018. Unfortunately there are posts – most likely complete pages – missing.
Page 479 of 598
@davidc502 -
I made the changes you suggested and it's working great. I think part of the problem was my n00b status with VI - I think when I was editing, I wasn't doing it properly, which was causing it to spaz. Working great so far though. I'll keep you posted!
Thanks for all the help - this is a really great community!
-Paul
jglooije wrote:
@All the wireless AC speed seems somehow limited to 80 MBit/s at most on my wrt1900acs (With the router in line of sight). I used different builds and all the same result. People who also have this kind of speed problem can you please add to this https://github.com/kaloz/mwlwifi/issues/85 so this can be resolved. Or maybe if no one has this problem it is my laptop. Thank you all in advance. (for the N band there is a separate issue)
My AC speed is fine?
nitroshift wrote:
@Nihilanth
https://onedrive.live.com/redir?resid=5 … =folder%2c
It contains latest mwlwifi commit (as of today), mac80211 dated 12.05.2016 and also netdata, which is why it's so hefty in size.
nitroshift
thanks buddy. will let you know how it works
davidc502 wrote:
cluprogram wrote:@david502c
Here ya go:
The option paths.. Change 01.0 to 02.0 for radio0 and change 02.0 to 03.0 for Radio1 and reboot
The should look like this
Radio0
option path 'platform/soc/soc:pcie-controller/pci0000:00/0000:00:02.0/00Radio1
option path 'platform/soc/soc:pcie-controller/pci0000:00/0000:00:03.0/00
David, this confuses the heck out of me. i have
config wifi-device 'radio0'
option type 'mac80211'
option hwmode '11a'
option path 'platform/soc/soc:pcie-controller/pci0000:00/0000:00:01.0/0000:01:00.0'
config wifi-device 'radio1'
option type 'mac80211'
option hwmode '11g'
option path 'platform/soc/soc:pcie-controller/pci0000:00/0000:00:02.0/0000:02:00.0'And it is working fine?
aren't you mixing up V1 vs V2/ACS hardware?
@mrfrezee, do you have source of your builds ? i would like to build my own images.
thnx
jglooije wrote:
@All the wireless AC speed seems somehow limited to 80 MBit/s at most on my wrt1900acs (With the router in line of sight). I used different builds and all the same result. People who also have this kind of speed problem can you please add to this https://github.com/kaloz/mwlwifi/issues/85 so this can be resolved. Or maybe if no one has this problem it is my laptop. Thank you all in advance. (for the N band there is a separate issue)
How are you testing speed?
iperf on my Mac Book Pro is showing:
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-10.00 sec 668 MBytes 560 Mbits/sec sender
[ 4] 0.00-10.00 sec 668 MBytes 560 Mbits/sec receiverJW0914 wrote:
To All Should SQM be used over QOS for qos? If so, does anyone recommend a good source to read up on how to properly configure SQM? I tried using it before, however always had issues with my Harmony Elite hanging on commands and switched back to QOS, as I could place the qos rules for the Elite at the top.
Opinions differ, but I would suggest that you try the sqm scripts first and only implement QOS if it doesn't work for you. QOS requires a lot of knowledge of what you have on your network and how they interact. It also doesn't address the problems of bufferbloat on the router between you and your ISP. You may find that the sqm scripts give you a usable system with little, if any tuning (and that being the one-time tuning to match your Internet connection, not tuning based on what traffic you have)
jglooije wrote:
@All the wireless AC speed seems somehow limited to 80 MBit/s at most on my wrt1900acs (With the router in line of sight). I used different builds and all the same result. People who also have this kind of speed problem can you please add to this https://github.com/kaloz/mwlwifi/issues/85 so this can be resolved. Or maybe if no one has this problem it is my laptop. Thank you all in advance. (for the N band there is a separate issue)
Speed seems to be down a touch, but can't quite put my finger on the situations.
JohnnySL wrote:
davidc502 wrote:cluprogram wrote:@david502c
Here ya go:
The option paths.. Change 01.0 to 02.0 for radio0 and change 02.0 to 03.0 for Radio1 and reboot
The should look like this
Radio0
option path 'platform/soc/soc:pcie-controller/pci0000:00/0000:00:02.0/00Radio1
option path 'platform/soc/soc:pcie-controller/pci0000:00/0000:00:03.0/00David, this confuses the heck out of me. i have
config wifi-device 'radio0' option type 'mac80211' option hwmode '11a' option path 'platform/soc/soc:pcie-controller/pci0000:00/0000:00:01.0/0000:01:00.0' config wifi-device 'radio1' option type 'mac80211' option hwmode '11g' option path 'platform/soc/soc:pcie-controller/pci0000:00/0000:00:02.0/0000:02:00.0'And it is working fine?
aren't you mixing up V1 vs V2/ACS hardware?
Just bought a ACS on ebay (NEW) for 150 including shipping... Will check to see this weekend if there is a difference in the configuration section.
There is one left on Ebay, if someone wants it. It took my offer of 150.00 automatically.
kirkgbr wrote:
jglooije wrote:@All the wireless AC speed seems somehow limited to 80 MBit/s at most on my wrt1900acs (With the router in line of sight). I used different builds and all the same result. People who also have this kind of speed problem can you please add to this https://github.com/kaloz/mwlwifi/issues/85 so this can be resolved. Or maybe if no one has this problem it is my laptop. Thank you all in advance. (for the N band there is a separate issue)
iperf on my Mac Book Pro is showing:
[ ID] Interval Transfer Bandwidth [ 4] 0.00-10.00 sec 668 MBytes 560 Mbits/sec sender [ 4] 0.00-10.00 sec 668 MBytes 560 Mbits/sec receiver
What are you using for the iperf3 client command line? We need a standard to compare.. I know you have a wrt1900acv1 like me. Are you using the MacBook as a client or server? We need a common denominator. for speed test. I use iperf3 -c 192.168.1.131 -P6 -t 120 and also run a -R and I do not see this speed. it is in the 400Mbs pushing 500Mbs but not as high as you are seeing.
(Last edited by northbound on 7 Jun 2016, 00:40)
@northbound
Macbook wireless:
iperf3 -c 192.168.1.220
192.168.1.220 - Linux wired:
iperf -s -V
EDIT: New test with your parameters
Macbook wireless:
iperf3 -c 192.168.1.220 -P6 -t 120
...
...
[SUM] 0.00-120.00 sec 7.58 GBytes 542 Mbits/sec sender
[SUM] 0.00-120.00 sec 7.57 GBytes 542 Mbits/sec receiver(Last edited by kirkgbr on 7 Jun 2016, 02:03)
kirkgbr wrote:
@northbound
Macbook wireless:
iperf3 -c 192.168.1.220192.168.1.220 - Linux wired:
iperf -s -VEDIT: New test with your parameters
Macbook wireless:
iperf3 -c 192.168.1.220 -P6 -t 120 ... ... [SUM] 0.00-120.00 sec 7.58 GBytes 542 Mbits/sec sender [SUM] 0.00-120.00 sec 7.57 GBytes 542 Mbits/sec receiver
Sweet! has the new mwlwifi did this or is this what you have been seeing?
I am still on 4.4.12+10.3.0.17-2016..1-1. May be time to grab new I was waiting till it stabilized.
Hi, how to see more lines from dmesg output, and logread? Where to configurr this? I use mrfrezee build.
Thnx
gsustek wrote:
Hi, how to see more lines from dmesg output, and logread? Where to configurr this?
/etc/config/system enables you to set the internal log buffer size for logread. Default 16 kB of RAM is ridiculously low for routers like WRT1900AC especially with additional packages installed, as the whole boot process doesn't likely fit into it. I have set it to 64 kB in my own builds.
/etc/config/system
config system
...
option log_size '64'The log size config item can also be found in Luci in the system menu: System/system/logging
(Last edited by hnyman on 7 Jun 2016, 07:35)
gsustek wrote:
Hi, how to see more lines from dmesg output, and logread? Where to configurr this? I use mrfrezee build.
Thnx
Offtopic: Did you saw my reply to you regarding your memory issue?
(Last edited by JohnnySL on 7 Jun 2016, 07:12)
JohnnySL wrote:
gsustek wrote:Hi, how to see more lines from dmesg output, and logread? Where to configurr this? I use mrfrezee build.
Thnx
Offtopic: Did you saw my reply to you regarding your memory issue?
oh, yes, i did, but first i have to rid of this NAND timeout(squashfs error) from my 1900ACS
Your command is helpful but the i need to know who is taking so much ram...
thnx.
(Last edited by gsustek on 7 Jun 2016, 07:55)
New driver and firmware available
[ 12.308227] <<Marvell 802.11ac Wireless Network Driver version 10.3.0.17-20160607>>
Edit: Firmware updated only for 88W8897, and wrt1X00ac(s) is having 88W8864.
(Last edited by Bogey on 7 Jun 2016, 08:12)
gsustek wrote:
@mrfrezee, do you have source of your builds ? i would like to build my own images.
thnx
I just fetch the repo from openwrt's git and apply all the contents with patch -p1 < patchfiles of the git-patch directory (Dropbox link is on my signature)
You can also find in this shared dropbox the default configuration and the script i'm using for building.
If you are searching for the imagebuilder, you can find it here:
https://openwrt.nc-network.io/?dir=builds/mvebu
northbound wrote:
Sweet! has the new mwlwifi did this or is this what you have been seeing?
I am still on 4.4.12+10.3.0.17-2016..1-1. May be time to grab new I was waiting till it stabilized.
kmod-mwlwifi - 4.4.12+10.3.0.17-20160603-1
Not sure what did this. Speeds have been this way thru several of the new versions lately.
Can someone explain me from where is that NAND timeout and how it being solved?
thnx
Hmm.. anyone know the meaning of this exchange.
anomeome wrote:
Hmm.. anyone know the meaning of this exchange.
Much can be left up to interpretation of this vague statement.
"Firmware of 8864 will be updated to comply with the new FCC rule later."
It has some rather nasty implications as of late. But in context, does not really stand to reason. But certainly raises many questions no matter what is meant. One obvious question, if I do not reside there, why do I have to comply.
(Last edited by anomeome on 7 Jun 2016, 15:53)
hnyman wrote:
gsustek wrote:Hi, how to see more lines from dmesg output, and logread? Where to configurr this?
/etc/config/system enables you to set the internal log buffer size for logread. Default 16 kB of RAM is ridiculously low for routers like WRT1900AC especially with additional packages installed, as the whole boot process doesn't likely fit into it. I have set it to 64 kB in my own builds.
/etc/config/system
config system ... option log_size '64'The log size config item can also be found in Luci in the system menu: System/system/logging
i change it to 1024, restart the router, but nothing changed, dmesg is "stuck" to 100 lines
Sorry, posts 11976 to 11975 are missing from our archive.
Page 479 of 598