Appears kaloz closed the thread, but this has been a bug for wifi in the past. https://github.com/kaloz/mwlwifi/issues/55

If you want to go back, there's absolutely nothing you will loose by going to it. Maybe sometime in the future you can try to upgrade again.

Don't forget... you will need to sysupgrade with the -F option to go back.

1. Yes.

2.  If I'm understanding the question right, I believe no. The two partitions are separate and the file systems are completely separate.

Hope you enjoy the new router. Do you know which version you have?

I am determined to stick with it until we have a resolve now that I have been running with the drive unmounted for the last hour now and not an issue although I LOVE the nas abilities I dislike going backwards so I will wait another hour and re-mount to see if that is indeed the culprit. I will keep you posted and again thanks for the responses.

Noticed that occasionally my computer won't rejoin the wifi network after a while in the latest image. Still seeing what's up...

Ok ran for 2 hours problem free, mounted the drive and 10 minutes later all wifi dropped and was unable to connect to either again. I will disable mounts for now and hope they have a resolve soon.

[   49.131321] br-lan: port 2(wlan0) entered forwarding state
[ 7386.890951] EXT4-fs (sda): couldn't mount as ext3 due to feature incompatibilities
[ 7386.899880] EXT4-fs (sda): couldn't mount as ext2 due to feature incompatibilities
[ 7387.266317] EXT4-fs (sda): mounted filesystem with ordered data mode. Opts: (null)
[ 7978.760019] ieee80211 phy1: cmd 0x9125=BAStream timed out
[ 7978.765452] ieee80211 phy1: return code: 0x1125
[ 7978.770026] ieee80211 phy1: timeout: 0x1125
[ 7978.774228] ieee80211 phy1: destroy ba failed execution
[ 7982.799957] ieee80211 phy1: cmd 0x9125=BAStream timed out
[ 7982.805398] ieee80211 phy1: return code: 0x1125
[ 7982.809967] ieee80211 phy1: timeout: 0x1125
[ 7982.814169] ieee80211 phy1: destroy ba failed execution
[ 7986.839895] ieee80211 phy1: cmd 0x9125=BAStream timed out
[ 7986.845387] ieee80211 phy1: return code: 0x1125
[ 7986.850055] ieee80211 phy1: timeout: 0x1125
[ 7986.854477] ieee80211 phy1: destroy ba failed execution
[ 7990.889820] ieee80211 phy1: cmd 0x9125=BAStream timed out
[ 7990.895251] ieee80211 phy1: return code: 0x1125
[ 7990.899813] ieee80211 phy1: timeout: 0x1125
[ 7990.904018] ieee80211 phy1: destroy ba failed execution
[ 7994.939751] ieee80211 phy1: cmd 0x9125=BAStream timed out
[ 7994.945247] ieee80211 phy1: return code: 0x1125
[ 7994.949896] ieee80211 phy1: timeout: 0x1125
[ 7994.954098] ieee80211 phy1: check ba failed execution
[ 8002.821621] ieee80211 phy1: cmd 0x801d=MEMAddrAccess timed out
[ 8002.827483] ieee80211 phy1: return code: 0x001d
[ 8002.832047] ieee80211 phy1: timeout: 0x001d

(Last edited by markm12345 on 27 Nov 2016, 05:12)

Thanks David. I'm using WRT1900AC v2. Supplementary question: is it possible to specify the specific kernel to override when performing a sysupgrade? Or does sysupgrade simply override the other kernel partition that is not currently running?

It's done round robin, so the partition not being used is over written. It's a good system because you can always go back to where you were before the flash.

I had this problem with the 11/17/2016 build. Was a laptop with a Intel NIC. Was using the 5GHz wireless. Would not connect at times. If I just let it sit active it would eventually connect. No other devices had issues. 
Now running latest, 11/26/2016 and have not had the issue come up again.

--bill

I'm noticing it exclusively on the 5G channel as well and connecting from a macbook pro client. I had the issue before with another build (can't remember which), and it seemed to have gone away in subsequent builds and came back on this one.

Very odd, not sure what's going on

Late last night mine became unusable so I rolled back to Hydra r2221 and have ran all day problem free with drive mounted and samba running.

Thanks again for taking care of us David. Maybe one day I will get around to compiling myself, but you make it so easy not to :-)

Loaded up your 11/26 build this evening on my ACSv1 (was waiting for the switch change to be reverted), and so far so good. Some packages I use (and wanted to use) installed just fine. Adblock being one of them, with its pre-req packages as well.

On a side note, I know you mentioned it before about needing some MOAR!!! horsepowa for compiling on. I have a good amount of X99 hardware in the basement (Xeons and regular i7), and I would be willing to help you out if you are in the market for an upgrade. And what I mean is a very nice discount on some hardware for a build, not free :-) I am not that rich. If you are interested, let me know and we can talk further by some other more private means. (I am in SE Michigan)

I assume you are okay with bandwidth and all for hosting?

cybrnook

(Last edited by cybrnook2002 on 28 Nov 2016, 03:39)

Dear David,

thank you for providing your excellent builds!

I bought a WRT1900AC v1 when they first came out and after being so frustrated and disappointed with Linksys original toy firmware I swapped to OpenWrt but had too many performance problems so my router ended up in its box for 1 year. I brought it out again and have been running OpenWrt with OK results the last year and just recently I thought I'd give your LEDE build (Lede Torero r1967 / LuCI Master (git-16.298.34250-95358ab)) a try.

WOW!  Very smooth running! Very stable and performance is acceptable even if I still seem to have some speed issues on MacBook Pro and Air running 2.4GHz. But in overall, great build and very, very stable!

Thank you again, and please keep up the good work!

Also thinking of rolling back to r2221 or r2317. Seems David still has the build available, along with the package repo.

Will roll back this evening and report, as I am also facing drop outs on the latest.

(Last edited by cybrnook2002 on 29 Nov 2016, 15:54)

Me too... Yes, the repo will be there automatically. From what I remember 2317 does not have the latest wifi drivers that seem to be causing issues.

I'm getting random drops with the latest wifi. Will probably put in a bug report to kaloz tonight.

Thanks David!

I will follow your lead, and align with you on r2317.

Interesting about folks having issues. I have 2321 installed on my wrt1900acs v1 and not experiencing any issues. Has been up for 2.5 days. Streaming all last night without issue on the 5Ghz wireless. Guess I am lucky. Don't do anything fancy, routing to Internet and wireless support .

--bill

Strange, as you know I am also on the WRT1900ACSv1. I also believe David recently switched to an ACSv1 as well...... I wonder if it comes down to what client devices we have on the network?

I would guess it probably is client device specific. I have a laptop with Intel wireless NIC, PC with Asus USB AC56 NIC, Amazon Fire TV, Roku 3, iPhone 6s. All of these get used. Have 2 other i Phones that connect, but only use the wireless for calling.  Only true Android device I have is 2.4 only. Of course the Fire and Roku are Android. No Apple laptops or desktops. Apple devices seem to be the problem children from what I remember reading different reports on various firmware versions both Openwrt/LEDE and DD-WRT.

I to like david's builds. I do load up DD-WRT when a new version comes out just to see how it looks. Always find that my simple iperf test of the 5GHz wireless always says Openwrt/LEDE wins the race. In all fairness, DD-WRT is closing the gap. Also like the Luci interface better then DD-WRT. Have also loaded up Gargoyle, based on Openwrt, a couple of times. Interesting firmware, but they do not seem to stay current with builds, especially wireless drivers. Of course they have more to test and modify before they put out a new build and I think it is only a couple of guys supporting multiple vendor routers.

--bill

New issue has been opened for the wifi drops on the latest committed driver.

https://github.com/kaloz/mwlwifi/issues/126

Thanks David for following up on that, let's see what comes of it.

In the meantime, I first dropped back to 2317, but IPV6 would not lock for me. So I then dropped back to "Ol faithful" r2221, and am back up and running.

I want to say, thanks again for continuing to host the packages for the older builds. This is much appreciated for these scenarios where the latest may not be the greatest at the time and we want to fall back to N-1 (or 2).

(Last edited by cybrnook2002 on 30 Nov 2016, 02:46)

@cybrnook2002

Thanks for the input.

I was going to roll back to 2221, but this build will probably be needed for wifi troubleshooting.

David, looks like you have a nibble from Marvel about the wireless issue on the issue you created. 
--bill

Can one go back to a previous/earlier build using the sysupgrade.bin images? Not liking the 5Ghz network crashing and not restarting with the current build.

(Last edited by moore.dwayne on 30 Nov 2016, 16:50)

Yes you can.

Hello david,

I use your firmware since november and had a great experience with the version you released end of november, it was stable for over a month with no problems.

Until I updated, right now I'm at the latest version you released on 2016-11-26 with two WRT1900ACS.
I did a factory reset on both after and while upgrading and configured them from the beginning.

Since then the wifi is really unstable. I can't use all the channels, with most the wifi won't work anymore. I only can pick channel 36 and 48 for AC for example, because everything else isn't working or is slow.

Could you please look up the issue? I'll roll back to the older version for now.

Thanks a lot for your great firmware and your great support.

Also found a bug:
If I update your firmware and keep settings enables checked, all of my installed software is getting uninstalled. DNScrypt for example. I had to reinstall it completely after upgrading.

(Last edited by johndoe on 30 Nov 2016, 23:33)