OpenWrt Forum Archive

Topic: davidc502 1900ac 3200acm builds

The content of this topic has been archived between 26 Feb 2018 and 7 May 2018. Unfortunately there are posts – most likely complete pages – missing.

Okay, r6520 has been completely replaced.  I modified the wifi make file, and recompiled. The new imaged was transferred over to the 3200acm and did a sysupgrade, and wifi is now working correctly.

If we can have a few other people do some testing, and if all goes well, then we will put those images on the downloads for everyone.

https://davidc502sis.dynamic-dns.net/sn … /cortexa9/

The sysupgrade of myWRT1200ACv1 from r4901 to r6520 with 'keep settings' worked without problems and I am back on the internet after about 4 minutes of work. I have yet to check the logs or tweak things like dnscrypt that probably is different after 6 months. The wifi, lan and wan is working and so now there is no hurry to work on any other problems if any.

Thanks davidc502.

Hello David you're doing a great job!, I was just wondering is there any update for OPENWRT on the Linksys WRT32X ?

Did an upgrade from stock Linksys fw to r6520 on my wrt3200acm without any trouble...all is working well (including wifi). P.S. I always keep Linksys fw on one partition for safety reasons.

I had all but given up on this router, as many others have. Constant wifi drops with stock linksys fw, dd-wrt, and earlier lede releases were extremely frustrating. However, beginning with experimental build r6365, that all changed. My wrt3200acm performed like a router should for the first time ever! Thank you David!

This latest build r6520 did not have 005-linksys_hardcode_nand_ecc_settings.patch

Will rebuild tonight and post tomorrow.

davidc502 wrote:

This latest build r6520 did not have 005-linksys_hardcode_nand_ecc_settings.patch

Will rebuild tonight and post tomorrow.

Oh well.... at least your getting close to wrapping up on a good final test release.

Donno, but I still plan on doing both 1900AC/V2 and 1900ACS firmware test runs, in the wee hours of the morn once your latest redo of your test built is uploaded.

Will they be in the same link 6520 or in a new revision  to reflect the latest builds of the modules released between your last build?

Notsofast wrote:
davidc502 wrote:

This latest build r6520 did not have 005-linksys_hardcode_nand_ecc_settings.patch

Will rebuild tonight and post tomorrow.

Oh well.... at least your getting close to wrapping up on a good final test release.

Donno, but I still plan on doing both 1900AC/V2 and 1900ACS firmware test runs, in the wee hours of the morn once your latest redo of your test built is uploaded.

Will they be in the same link 6520 or in a new revision  to reflect the latest builds of the modules released between your last build?

It's already done ... I've uploaded 6520 with the nand_ecc_settins patch. 

So far so good, but lets wait through the day and let other people try and see if there are issues or not.

https://davidc502sis.dynamic-dns.net/sn … /cortexa9/

When I upgraded my 1900ACv1 the wifi settings were a bit odd... So I rolled back.

I'm sure I can set everything up from scratch but I'm curious to hear how stable r6520 is on 1900ACv1 before I do all that.

//Brew

davidc502 wrote:
Notsofast wrote:
davidc502 wrote:

This latest build r6520 did not have 005-linksys_hardcode_nand_ecc_settings.patch

Will rebuild tonight and post tomorrow.

Oh well.... at least your getting close to wrapping up on a good final test release.

Donno, but I still plan on doing both 1900AC/V2 and 1900ACS firmware test runs, in the wee hours of the morn once your latest redo of your test built is uploaded.

Will they be in the same link 6520 or in a new revision  to reflect the latest builds of the modules released between your last build?

It's already done ... I've uploaded 6520 with the nand_ecc_settins patch. 

So far so good, but lets wait through the day and let other people try and see if there are issues or not.

https://davidc502sis.dynamic-dns.net/sn … /cortexa9/

Gosh, your fast! I thought I could nab on them after the race, but... Snow dashed my pans. Maybe the same for you... as nothing better to do when weather thwarts your day.

Downloaded... just so I can get the fresh installs tested, maybe save some settings for a possible finalised official run. Which I think will be soon, by how much headway has been done for both 1900AC/v1 and 3200 series. You have a bunch of 32x guys chomping at the bit, even if they end up down grading to 3200acm features with your builds. Maybe a patch can be done later to up do the basic test build to 32x mimo features can be done later and applied to both 3200 and 32x series. Just thinking out loud, for all them dealing with issues and no real support.

Brewder wrote:

When I upgraded my 1900ACv1 the wifi settings were a bit odd... So I rolled back.

I'm sure I can set everything up from scratch but I'm curious to hear how stable r6520 is on 1900ACv1 before I do all that.

//Brew

Not knowing which build, i assume going from different kernels and such, settings are dependent on so much when there is constant change between your running build and what is released. That is why I choose to do clean installs with the best available for stability and upgradabilty.

One rule of thumb handed down from years of testing and support. It is best to  maintain a good base install and save settings once setup, then wait for a stable build to upgrade to. If by chance there are many builds in between,  you may have to upgrade from an intermediate build to make sure settings are passed on properly and adjust if needed, then save your new settings for the upgrade you planned on installing. It may take doing another intermediate build if needed. Eventually you will have a settings file compatible for the later builds until another big change happens, and your back to doing the process with intermediate build updates once again.

Not many keep a stash of all working builds available for general use, like linksys. Fortunately David has a good collection of builds to progressively update from.

I have not kept up on all this thread, but i  would assume David would state which new build, when it's is released past testing, will not work with older versions settings.

(Last edited by Notsofast on 25 Mar 2018, 16:34)

davidc502 wrote:
Notsofast wrote:
davidc502 wrote:

This latest build r6520 did not have 005-linksys_hardcode_nand_ecc_settings.patch

Will rebuild tonight and post tomorrow.

Oh well.... at least your getting close to wrapping up on a good final test release.

Donno, but I still plan on doing both 1900AC/V2 and 1900ACS firmware test runs, in the wee hours of the morn once your latest redo of your test built is uploaded.

Will they be in the same link 6520 or in a new revision  to reflect the latest builds of the modules released between your last build?

It's already done ... I've uploaded 6520 with the nand_ecc_settins patch. 

So far so good, but lets wait through the day and let other people try and see if there are issues or not.

https://davidc502sis.dynamic-dns.net/sn … /cortexa9/

Flashed and did some stress testing over wifi and ethernet.
Seemed to work fine on my 1900ACS V2.

I installed r6520 on both of my 1900AC V1 with David's quick fix for the Wireless driver directory and both have been up with solid wireless performance on 2.4GHz and 5GHz for 23 hours. This is the best performance i have seen out of these unit so far.  Looking forward for to updates and refinements. Thanks for a great build David!

Hi,

Can someone explain the changes between 6365 and 6520?

without both are vs betas, but I believe that this doubt always stays mara many users.

thankful

My 1900acs v2 is running fine so far on r6520 you just uploaded.

gu3d3s wrote:

Hi,

Can someone explain the changes between 6365 and 6520?

without both are vs betas, but I believe that this doubt always stays mara many users.

thankful

Here are some differences.

6520 has various package updates.
6520 has the latest wifi drivers and AMSDU hack to keep latency low.
6520 has the latest kernel bumps.
6520 has the latest v1 cpu idle patch which keeps the v1 from rebooting.
6365 packages will be deleted at some point to make room for newer builds.

makedir wrote:

https://davidc502sis.dynamic-dns.net/re … pgrade.bin is not on the server... 404 error

I've been updating the site to accommodate the new naming convention of the lede/openwrt images.

All of the links are working now.  However, you will need to refresh the browser to get the new hyperlinks. The link above will not work anymore.

I've now copied the latest build over to the downloads webpage, and r6520 is available for everyone.

Some of the improvements.

Kernel version  4.14.27
WiFi driver 10.3.4.0-20180305 << this is based on the latest Commits on Mar 18, 2018
cpu idle disabled for the v1. This allows the v1 to run with the latest kernel versions.
Customization - AMSDU is disables for the 1200 and 1900 series hardware. Keeps latency low for gamers.
ecc settings patch is included. Helps to accommodate some of the newer hardware showing up out there.

I'd like to take a moment to thank everyone who has helped to troubleshoot issues prior to this release as there has been several smile !

(Last edited by davidc502 on 25 Mar 2018, 21:45)

why is wget missing, there is just a wget-nossl_1.19.2-2_arm_cortex-a9_vfpv3.ipk no ssl wget?

Currently running r6520 - and so far so good - WAN performance is hitting 700mbps (about 200 less than stock) but this is a huge improvement over 4.4 kernels.. Both 2.4 and 5Ghz up and running without issues.  Connection via PPPoE working without issues.  UPnP setup easily for Plex.  Only been up for 45 minutes but thats longer than any 4.9 build I tested.

Wireless speeds are faster than stock!

Sticking with this over stock for a while smile  Nice Work Davidc502 and other testers!

makedir wrote:

why is wget missing, there is just a wget-nossl_1.19.2-2_arm_cortex-a9_vfpv3.ipk no ssl wget?

wget is already baked in with busybox.

root@lede:~# wget
BusyBox v1.27.2 () multi-call binary.

Usage: wget [-c|--continue] [--spider] [-q|--quiet] [-O|--output-document FILE]
        [--header 'header: value'] [-Y|--proxy on/off] [-P DIR]
        [-S|--server-response] [-U|--user-agent AGENT] [-T SEC] URL...

Retrieve files via HTTP or FTP

        --spider        Only check URL existence: $? is 0 if exists
        -c              Continue retrieval of aborted transfer
        -q              Quiet
        -P DIR          Save to DIR (default .)
        -S              Show server response
        -T SEC          Network read timeout is SEC seconds
        -O FILE         Save to FILE ('-' for stdout)
        -U STR          Use STR for User-Agent header
        -Y on/off       Use proxy
root@lede:~# cd /tmp
root@lede:/tmp# wget https://davidc502sis.dynamic-dns.net/releases/lede-mvebu-cortexa9-linksys-wrt1900ac-squashfs-factory.img
Connecting to davidc502sis.dynamic-dns.net (45.79.194.151:443)
lede-mvebu-cortexa9- 100% |**********************************************************************************| 12288k  0:00:00 ETA

*EDIT*

I remember... there was an issue with wget, and the package was removed. I've re-added it as a module for the next build. If it continues to fail, I'll have to remove it again.

If you need the module right now, I think it can still be pulled off of the daily builds. -- https://downloads.openwrt.org/snapshots … _vfpv3.ipk

(Last edited by davidc502 on 25 Mar 2018, 22:06)

Really thanks David for r6520, i don't know why but on my wrt3200acm i get like 10MB/s more on ethernet than r6365 and previous versions, from 70MB/s to 80MB/s. Maybe a placebo effect?
The remote update on lede interface is not working with sysupgrade files, i must use the command line to upgrade.

(Last edited by Keltere on 25 Mar 2018, 23:33)

Keltere wrote:

Really thanks David for r6520, i don't know why but on my wrt3200acm i get like 10MB/s more on ethernet than r6365 and previous versions, from 70MB/s to 80MB/s. Maybe a placebo effect?
The remote update on lede interface is not working with sysupgrade files, i must use the command line to upgrade.

Good, I'm glad you are getting more speed. Really, between the two there shouldn't be a difference via ethernet, but you may have picked up a little more speed through Wifi.

With sysupgrade are you trying through LuCi and it isn't working?

davidc502 wrote:
Keltere wrote:

Really thanks David for r6520, i don't know why but on my wrt3200acm i get like 10MB/s more on ethernet than r6365 and previous versions, from 70MB/s to 80MB/s. Maybe a placebo effect?
The remote update on lede interface is not working with sysupgrade files, i must use the command line to upgrade.

Good, I'm glad you are getting more speed. Really, between the two there shouldn't be a difference via ethernet, but you may have picked up a little more speed through Wifi.

With sysupgrade are you trying through LuCi and it isn't working?

Yup i've tried with a remote update but when the upload ends the connection but it won't upgrade, i will try next time to do a local sysupgrade with LuCI.
I don't think is just a placebo effect. I use speedtest-cli and now with multiple test and after 24h it show a reduction of 50% of the ping, from 20-25 to 13-9 ms and the throughput is really stable. it always show 500mbps and 200mbps as it should. Before this update the fluctuation was from 50mbps to 200mbps to 400mbps, almost never reaching 500mbps

Thank you, davidc502!
You've made a great work- I've found answers to all my questions here in one place.