For wrt1900ac v1 models only, they have a reboot issue with Kernel 4.9. Because of this @davidc502 has compiled a Kernel 4.4 build specifically for them: https://davidc502sis.dynamic-dns.net/snapshots/Kernel_4.4/r4323/targets/mvebu/generic/
Edit: However, the stable 17.01.2 also uses Kernel 4.4, so it shouldn't give you any reboot problems...even though you said it does...
I think there is an issue with the WRT1900AC V1 build because this reboot issue doesn't exist in other open source firmwares:
root@MCDEBIAN:~# uptime
00:31:05 up 4 days, 15:09, 1 user, load average: 0.00, 0.00, 0.00
root@MCDEBIAN:~# uname -a
Linux MCDEBIAN 4.9.31 #29 SMP Sun Jun 11 13:13:25 CDT 2017 armv7l GNU/Linux
difference from stock lede?
Yes, they are different. But I have discontinued these builds, so they are out of date.
what are the difference? i mean preinstalled package or patch to the code?
Hey Guys,
I am deploying multiple routers throughout my home and want to reduce the txpower but don't seem to be able to do so.
What I found:
I set txpower to 1 in /etc/config/wireless, iw wlan* info reports the setting in wireless config file but the actual power output is observed to stay the same regardless of the setting. (-40 dBm for 5ghz, and -36 dBm for 2.4ghz)
It's only when I switch 5ghz channel 149 to channel 36 then I observe a reduction of received signal for 5ghz from -40dBm to -49dBm. This seems to correspond to the regulatory limit
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
i.e. high channel (149 in my case) max power limited to 30, while low channel (36) limited to 23.
How do I properly reduce the txpower?
Hello. Can someone help me. I have linksys wrt1900acs v2 router I have gone from dd-wrt to LEDE reboot 17.01.2 r3435-65eeec8bd5f / LuCI lede-17.01 branch And I have a talktalk fibre router it is D-Link DSL-3782 on dd-wrt I have changed in factory settings local ip to 192.168.222.1 connected linksys router and it worked straight away. Now with Lede I'cant do the same, when changing the ipv4 to 192.168.111.1 or 192.168.222.1 or 192.168.111.2 or 192.168.222.2 after settings Got applied I cant access dashboard from any of Those ip's I also set the Lan protocol to static as is default
Please help me configure it, thanks in advance
Ok managed to fix the issue. Just in case anyone will need help with this. I managed to do below:
I changed the ipv4 ip from 192.168.1.1 to 192.168.60.1 and default gateway to 192.168.60.2 but after applying the router didn't go back to webui so I SSH Into the router to check partitions
first command :
fw_printenv boot_part
boot_part=1
so I tried different one in mycase partition 4 was spot on!
sofw_setenv boot_part 4 press enter
reboot press enter
Than I could finally connect via 192.168.60.1 and connected talktalk router from lan port 1 to the linksys WAN port and I have internet now 
This applies to all neon capable SoCs but if anyone wants to try (works on all versions expect 1900ACv1 which doesn't use Armada 385) here's a little speed-up for zlib. Works fine on my WRT3200ACM.
https://github.com/lede-project/source/pull/1329
You also need to change this line from vfpv3 to neon
Build for 3200ACM is up. I am playing around with this model only these days, so will post for this unit only here and there:
Testing now on my WRT3200ACM... the kernel is 4.4... So doesn't have this commit https://github.com/lede-project/source/commit/a8f63a0717f553e0a1b37ee9212fc4cb2a801426 right?
And the wifi driver are old 10.3.4.0-20170606
This is the stable branch, not the master branch. You are looking for items in the master branch, that's not what this is.
I could look at updating the driver, but the prior commit you called will not be added until the branch is updated.
EDIT: Latest driver on 17.01 stable branch:
@cybrnook Thank you for providing these great stable branch builds.
So far, this build is working absolutely fantastic with the addition of eduperez's stable branch drivers (https://github.com/eduperez/mwlwifi_LEDE) and the latest 9.3.0.8 firmware from yuhhaurlin (https://drive.google.com/open?id=0B3qLWtcWB9EdWU9vM09QRy1Bc00).
How are you adding this driver and firmware after the fact?
Good to hear it's running fantastic for you.
Driver and firmware can be distributed in a package, that you just need to install; see the thread Pre-compiled updated mwlwifi drivers for stable releases
For the driver package from eduperez, I simply copy the ipk over to the tmp directory and using WinSCP to run the opkg install ./kmod-mwlwifi.ipk command to upgrade the driver. Although I believe I had to uninstall the older driver first before issuing that command.
For the firmware .bin file, I simply used WinSCP to navigate to the /lib/firmware/mwlwifi directory, deleted the older 88W8964.bin file and copied over the newer 88W8964.bin firmware and rebooted the device.
Running very smooth at the moment. It's nice to see you and eduperez providing support for the community for Stable branch build users.
Interesting and cool idea.
However, in my case I am already compiling against the latest driver, so I think flashing this package is a redundant step on my build.
The firmware extracted from the 32X though is not included in my build, I am one version back matched to mwlwifi's latest. But seems it will be pushed to git soon.