OpenWrt Forum Archive

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.

northbound wrote:

@DoITright
Just curious, how are you seeing this hit in performance?

:edit
Or should I say where?

Interesting....  I just power cycled both my routers and tested again with better results....

Very un-scientific of me but I always copy the same 4 G file from the same source to different targets.

In this case (I have not tried elsewhere) from the NAS to my workstation:

workstation -> wired to 1900AC (stock) -> 5GHz bridge -> 1900AC (with .13 driver) -> wired NAS

On .12/14 I would see 12 MB/s on average

On .13 I now see 13.5 MB/s on average with peak near 17 MB/s

Will try with a much larger file....

Cheers

doITright wrote:
northbound wrote:

@DoITright
Just curious, how are you seeing this hit in performance?

:edit
Or should I say where?

Interesting....  I just power cycled both my routers and tested again with better results....

Very un-scientific of me but I always copy the same 4 G file from the same source to different targets.

In this case (I have not tried elsewhere) from the NAS to my workstation:

workstation -> wired to 1900AC (stock) -> 5GHz bridge -> 1900AC (with .13 driver) -> wired NAS

On .12/14 I would see 12 MB/s on average

On .13 I now see 13.5 MB/s on average with peak near 17 MB/s

Will try with a much larger file....

Cheers

One of my  tests is a usb3 wd passport ntfs In the usb3 port. Using winscp ftp and openwrt vsftpd I get from 20 to 25 MB a sec.
Factory Linksys was 40 MB plus same drive and format. The main thing for speed I do to prep for the test is after any fresh install
echo 16384 > /proc/sys/vm/min_free_kbytes
On this one test there was no real difference. But I am pretty sure ext4 would be faster.

northbound wrote:

@muronghan
What does your   grep mwl /proc/interrupts ; sleep 1; grep mwl /proc/interrupts      look like?
And temp? sensors if you have lm-sensors installed.

Like:

61:    1377729          0       GIC  61  mwlwifi
65:    1440659          0       GIC  65  mwlwifi
61:    1379830          0       GIC  61  mwlwifi
65:    1442858          0       GIC  65  mwlwifi

muronghan wrote:
northbound wrote:

@muronghan
What does your   grep mwl /proc/interrupts ; sleep 1; grep mwl /proc/interrupts      look like?
And temp? sensors if you have lm-sensors installed.

Like:

61:    1377729          0       GIC  61  mwlwifi
65:    1440659          0       GIC  65  mwlwifi
61:    1379830          0       GIC  61  mwlwifi
65:    1442858          0       GIC  65  mwlwifi

Over 4k irq a sec by looking at this I assume idle?

Temps? 
opkg install lm-sensors
sensors

northbound wrote:
muronghan wrote:
northbound wrote:

@muronghan
What does your   grep mwl /proc/interrupts ; sleep 1; grep mwl /proc/interrupts      look like?
And temp? sensors if you have lm-sensors installed.

Like:

61:    1377729          0       GIC  61  mwlwifi
65:    1440659          0       GIC  65  mwlwifi
61:    1379830          0       GIC  61  mwlwifi
65:    1442858          0       GIC  65  mwlwifi

Over 4k irq a sec by looking at this I assume idle?

Temps? 
opkg install lm-sensors
sensors

root@WRT1200AC:~# sensors
tmp421-i2c-0-4c
Adapter: mv64xxx_i2c adapter
temp1:        +42.4 C
temp2:        +44.6 C

armada_thermal-virtual-0
Adapter: Virtual device
temp1:        +70.8 C

@muronghan
Thanks for the info and your time.

so... .12 is the same driver as .14 or are there some differences?

@northbound, pls find my recent post:

root@WRT1200AC:~# grep mwl /proc/interrupts ; sleep 1; grep mwl /proc/interrupts
61:   63121950          0       GIC  61  mwlwifi
65:   69125809          0       GIC  65  mwlwifi
61:   63124050          0       GIC  61  mwlwifi
65:   69128259          0       GIC  65  mwlwifi

Is that something serious and un-acceptable?

(Last edited by muronghan on 10 Nov 2015, 12:11)

muronghan wrote:

@northbound, pls find my recent post:

root@WRT1200AC:~# grep mwl /proc/interrupts ; sleep 1; grep mwl /proc/interrupts
61:   63121950          0       GIC  61  mwlwifi
65:   69125809          0       GIC  65  mwlwifi
61:   63124050          0       GIC  61  mwlwifi
65:   69128259          0       GIC  65  mwlwifi

Is that something serious and un-acceptable?

I don't like the heat build up that occurs at idle at the rate you are seeing.
No transfer should = no load .
You might want to test transfer speeds while paying attention to heat and load.
Then do the same and see what happens on 10.3.0.13. 
On a wrt1900av v1 .13 runs much cooler with no real performance hit (that I have seen). But you might see the results that the wrt1900ac v2 user sees and find low performance.
Please post results if you do this.
Thanks

silvah wrote:

so... .12 is the same driver as .14 or are there some differences?

I have not had the time to do a git diff they are supposed to be the same.

JohnnySL wrote:

Why is easy, .13 kills the performance on a V2 and the newer ACS models.
It would be nicer if it would get properly fixed though, such that it runs ok on all hardware models.

The timer based solution obviously didn't work out too well.  Maybe we could arm the "queue empty" interrupt only when we give the firmware a packet (or more) instead?  I don't see the value in arming it when you already know the firmware tx queue is empty.  And you do know that for sure if you are handling a "queue empty" interrupt and don't have any packets to transmit.

northbound wrote:
silvah wrote:

so... .12 is the same driver as .14 or are there some differences?

I have not had the time to do a git diff they are supposed to be the same.

They're not. .13 added another change as well, which is still there in .14.

bjorn@nemi:/usr/local/src/git/mwlwifi$ git log --oneline origin|head
0e3478e3405c Commit mwlwifi driver 10.3.0.14.
716010d6cfbe Commit mwlwifi driver 10.3.0.13.
30e6b06de659 Commit mwlwifi driver 10.3.0.12.
7a6aff718d2d Commit mwlwifi driver 10.3.0.10.
59e0d3d167a5 Commit mwlwifi driver 10.3.0.8
aaf953e1baf9 Remove unnecessary debug messages.
36e430f93174 Update F/W to version 7.2.8.6.
2b93ae5bf32e Commit mwlwifi driver 10.3.0.3
f6f2b26593a3 Change Chip to modules.
010dd6fba522 Modify code to pass checkpatch.pl.
bjorn@nemi:/usr/local/src/git/mwlwifi$ git diff --stat 30e6b06de659..0e3478e3405c
 debugfs.c  |  8 --------
 dev.h      |  3 ++-
 fwcmd.c    | 19 ++++++++++---------
 hostcmd.h  |  2 +-
 mac80211.c | 98 ++++++++++++++++++++++++++++++++++++++++----------------------------------------------------------
 main.c     |  2 +-
 rx.c       | 82 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 sysadpt.h  |  2 +-
 tx.c       | 25 ++++++++++++++++++++-----
 9 files changed, 157 insertions(+), 84 deletions(-)

This is a problem with how they use git. It would have been much, much, much better if they commited each change separately instead of collecting a number of them and then commiting a whole new release as a major mess of changes.  This makes it very hard to pinpoint regression sources, and makes powerful tools like "git bisect" mostly useless. The recent flow of small releases improves the situation, but there are still problems like the one shown above: The 10.3.0.13 commit was really two separate changes merged together.

But I beleive the driver should be ready for mainline soon, and then this problem is going away.  There is no way that kind of commits are going to be accepted after the driver is in mainline.

bmork wrote:

This is a problem with how they use git. It would have been much, much, much better if they commited each change separately instead of collecting a number of them and then commiting a whole new release as a major mess of changes.  This makes it very hard to pinpoint regression sources, and makes powerful tools like "git bisect" mostly useless. The recent flow of small releases improves the situation, but there are still problems like the one shown above: The 10.3.0.13 commit was really two separate changes merged together.

But I beleive the driver should be ready for mainline soon, and then this problem is going away.  There is no way that kind of commits are going to be accepted after the driver is in mainline.

They did a pretty lousy job reverting the schedular. some .13 files still contain references to the old schedular variables and others just contain a version number update to .13 (while already upgraded to .14)

so i think that it could have been cleaned-up a bit better as well.
i'm interested in the "arming the interrupt" solution you talked about above. it that an easy patch we could try ourselves?

(Last edited by JohnnySL on 10 Nov 2015, 13:28)

@northbound, I will probably test .13 after a few more days tracking on .14 on my WRT1200ac. A few hours ago my wife reported a crash when i was away, the router wan LED is gone and devices were offline so she turned off and on it. That can be the overheating problem?

For installing .13, just opkg install the .13 ipk file instead of a fresh rolling back, will it be ok?

I have a WRT1900AC v2, I just flashed to .14 and have to say bravo and thank you.  It is working lovely and even doesn't struggle streaming over 2.4GHz under load (was the previous deal breaker)

I just installed .14 yesterday and I haven't had any issues like this before with any build or drive.  Now my router reboots every 6-8 hours.   according to collectd it does not appear that heat is an issue .  Any place I should start watching for to determine why this has been happening?

The driver itself seems much faster (again non scientifically) and finally able to pull an IPv6 and ping magically started collecting again as well.

NemoAlex wrote:

Here is the 10.3.0.13 driver:
https://www.dropbox.com/s/s3cwni75te3cn … u.ipk?dl=0

notice: 15.05 final ONLY

@trustno1foxm
I didn't test it out, so be careful.

Thank you very much!! I am very busy at the moment and hope to be able to test it! If I could I would test it immediately, because I am very interrested in!

muronghan wrote:
northbound wrote:
muronghan wrote:

Like:

61:    1377729          0       GIC  61  mwlwifi
65:    1440659          0       GIC  65  mwlwifi
61:    1379830          0       GIC  61  mwlwifi
65:    1442858          0       GIC  65  mwlwifi

Over 4k irq a sec by looking at this I assume idle?

Temps? 
opkg install lm-sensors
sensors

root@WRT1200AC:~# sensors
tmp421-i2c-0-4c
Adapter: mv64xxx_i2c adapter
temp1:        +42.4 C
temp2:        +44.6 C

armada_thermal-virtual-0
Adapter: Virtual device
temp1:        +70.8 C

Tems are quite ok! I have the same with .3! Could you test .13 already? I don't think your crash has something to do with your temps!

so long

JohnnySL wrote:

i'm interested in the "arming the interrupt" solution you talked about above. it that an easy patch we could try ourselves?

I don't know.  I'm just throwing wild ideas around smile

I assume it's going to take a few hours of trial and error, if anyone is willing/able to put that into it.  I'm afraid I can't offer much at the moment.  So I should probably be a little more careful with my big mouth smile

Hi everyone.  I'm new to this forum and to WRT as well. I'm currently running dd-wrt on my Linksys WRT1200AC, but I want to give openwrt a try.  I need a recommendation on which firmware to start with; I'd like to try Kaloz's build, but I'm not sure which file to dowload.  Would someone be kind enough to point me in the right direction?  Thanks in advance.

Mike

UPDATE:  I found out which file to grab... a little more reading was required on my end..  Since I'm already running dd-wrt, do I need to flash back to the stock linksys firmware before flashing openwrt?

Thanks,

Mike

mmcneil wrote:

Hi everyone.  I'm new to this forum and to WRT as well. I'm currently running dd-wrt on my Linksys WRT1200AC, but I want to give openwrt a try.  I need a recommendation on which firmware to start with; I'd like to try Kaloz's build, but I'm not sure which file to dowload.  Would someone be kind enough to point me in the right direction?  Thanks in advance.

Mike

mmcneil wrote:

Hi everyone.  I'm new to this forum and to WRT as well. I'm currently running dd-wrt on my Linksys WRT1200AC, but I want to give openwrt a try.  I need a recommendation on which firmware to start with; I'd like to try Kaloz's build, but I'm not sure which file to dowload.  Would someone be kind enough to point me in the right direction?  Thanks in advance.

Mike

Hmmcnel.. and hi forum members..   I also am new to this forum I have the R7000...  Im looking for security Im being constantly hacked...  I believe this individual is somehow using a MS 2012 server to incorp my windows OS 10pro...  my question like you mmcneil...   is this software working properly for my needs...: Ive been reading this thread for about 2hrs..  and I dont seem to have an idea if any issue is a NON-starter for a protected VPN option..  Ive read that the wifi dont work.. and or the 5g dont work... 

I read that the DD-WRT is a option however, I now not even sure I should even try a opensource for fear that my lack of knowledge could leave me even more vulnerable...  be that as it may..  please assist if possible..  thanks again

(Last edited by metcalf338 on 10 Nov 2015, 23:53)

mmcneil wrote:

UPDATE:  I found out which file to grab... a little more reading was required on my end..  Since I'm already running dd-wrt, do I need to flash back to the stock linksys firmware before flashing openwrt?

Yes.

HI Kaloz THX for your Image
I need 3 more Gpios for 1900ACS so I can buy more units for our company (filling stations)
http://www.lteforum.at/attachments/upload_2015-11-8_19-34-38-png.3326/
echo 31 > /sys/class/gpio/export; echo out > /sys/class/gpio/gpio31/direction (+3,2 Volt on/off)
echo 1 > /sys/class/gpio/gpio31/value (+3,2 Volt on)
echo 0 > /sys/class/gpio/gpio31/value (+3,2 Volt off)
http://i.ebayimg.com/t/4-Kanal-5V-Relay-Relais-Module-Modul-fuer-Arduino-TTL-Logik-/00/s/MzY3WDUwMA==/z/Ps8AAOxyNepRmclY/$(KGrHqF,!qMFGBW3-(LMBRmclYECfQ~~60_35.JPG

(Last edited by Huawei on 11 Nov 2015, 09:20)

Thanks to Felix Fietkau we can now run kernel 4.3 on our wrt's, though I can recommend this only to whoever wishes to do testing.

nitroshift

Sorry, posts 8626 to 8625 are missing from our archive.