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.

alirz wrote:

I wonder though why some people are facing the freezes and others are not. In my case, i've never had mine freeze on me and im running alot of extra stuff on my router, python apps, other cron jobs, scripts,etc....I've have been compiling my images from trunk for the last 3 weeks or so...Currently running r45566 - 3.18.11.
I usually keep going for days(have gone over a week) until i reboot the router on purpose..

My router freeze yesterday. I was unable to access them. Even through cable. After reboot everything goes OK.

hnyman wrote:
alirz wrote:

Is there any performance (speed) differences between 3.18 vs 4.0 kernel?

There shouldn't be:
Linux 4.0 is just 3.19 renamed as 4.0 before the rc1 version release.
http://git.kernel.org/cgit/linux/kernel … 1deccff539
There is no quantum leap in functionality or performance. There are handy features like live kernel patching, but nothing special on networking performance front.

Thanks for the info/link smile

Using username "root".
Authenticating with public key "rsa-key-20120810"


BusyBox v1.23.2 (2015-04-26 03:30:09 UTC) built-in shell (ash)

Linksys WRT1900AC (Mamba)
Security is enabled, and your IP address has been logged.

root@AC1900:~# uname -a
Linux AC1900 3.18.11 #1 SMP Sun Apr 26 03:50:29 UTC 2015 armv7l GNU/Linux
root@AC1900:~# uptime
14:29:17 up 1 day, 21 min,  load average: 0.09, 0.13, 0.13
root@AC1900:~#

alirz wrote:

I wonder though why some people are facing the freezes and others are not. In my case, i've never had mine freeze on me and im running alot of extra stuff on my router, python apps, other cron jobs, scripts,etc....I've have been compiling my images from trunk for the last 3 weeks or so...Currently running r45566 - 3.18.11.
I usually keep going for days(have gone over a week) until i reboot the router on purpose..

Firstly, I'm not denying the freeze problem some people are seeming to have quite regularly - I did have it on 2 builds back at the end of March, although only immediately after flashing/rebooting.  I've not had it (at all) since.

Indeed, I ran for 14 days without any issues on r45337 before I upgraded (via stock) to 45566.

(I only upgrade when there are worthwhile new features/fixes/security patches.)


I think some people managed to catch a freeze with a usb-ttl connection?  Was there any useful info found??

(Last edited by DavidMcWRT on 27 Apr 2015, 23:44)

I was on LifeHacksback image(4.0) earlier this month, went at least 16 days without needing a restart.  That was a record on this router.  No issues whatsoever, and I was getting at least 80% of my ISP speed everywhere in my house.

I decided to try out the trunk image again to get the station stats/bitrate, and all has been well for the past 2 days.  If there are issues, I will go back to LifeBackHacks image and wait it out.

For me the daily need to update is gone, and I can now wait until there's another big change/fix.

You guys have done great with the development.  Thanks!

(Last edited by ShawnG1972 on 28 Apr 2015, 01:07)

ShawnG1972 wrote:

I was on LifeHacksback image(4.0) earlier this month, went at least 16 days without needing a restart.  That was a record on this router.  No issues whatsoever, and I was getting at least 80% of my ISP speed everywhere in my house.

I decided to try out the trunk image again to get the station stats/bitrate, and all has been well for the past 2 days.  If there are issues, I will go back to LifeBackHacks image and wait it out.

For me the daily need to update is gone, and I can now wait until there's another big change/fix.

You guys have done great with the development.  Thanks!

We're in so much of a better situation now at the release of the WRT1200AC than we were with the WRT1900AC.

Big congrats to Marvell who not only finally delivered an upstreamable driver but also have continued to add fixes/features.

Bigs thumbs up also to Kaloz throughout all of this, as well as lifehacksback and Chadster for helping us along the way.

I have had the freeze issue off trunk (I only run trunk ATM with 3.18 with 45337 right now). I captured a kernel log of the issue and posted it earlier in this forum:

https://forum.openwrt.org/viewtopic.php … 15#p272115

Longest uptime I have had is 6 days, but this is truly random as I have had it happen a few miniutes after a power cycle of the router...

DavidMcWRT wrote:

Firstly, I'm not denying the freeze problem some people are seeming to have quite regularly - I did have it on 2 builds back at the end of March, although only immediately after flashing/rebooting.  I've not had it (at all) since.

Indeed, I ran for 14 days without any issues on r45337 before I upgraded (via stock) to 45566.

(I only upgrade when there are worthwhile new features/fixes/security patches.)


I think some people managed to catch a freeze with a usb-ttl connection?  Was there any useful info found??

(Last edited by paul.culmsee on 28 Apr 2015, 01:47)

paul.culmsee wrote:

I have had the freeze issue off trunk (I only run trunk ATM with 3.18 with 45337 right now). I captured a kernel log of the issue and posted it earlier in this forum:

https://forum.openwrt.org/viewtopic.php … 15#p272115

Longest uptime I have had is 6 days, but this is truly random as I have had it happen a few miniutes after a power cycle of the router...

Ditto.

OpenWrt Chaos Calmer r45581 / LuCI (git-15.113.66125-f322842)
Kernel Version    3.18.11
Local Time    Mon Apr 27 19:24:43 2015
Uptime    5h 25m 23s

I've gone back to power cycling after a flash.
Waiting to see.

haven't seen any freezing issues...

root@ZOMGWTFBBQWIFI:~# uptime
19:55:16 up 15 days, 16:14,  load average: 0.00, 0.01, 0.04
root@ZOMGWTFBBQWIFI:~# uname -a
Linux ZOMGWTFBBQWIFI 3.18.11 #5 SMP Sat Apr 11 23:19:36 EDT 2015 armv7l GNU/Linux

Looks good!

|       |.-----.-----.-----.|  |  |  |.----.|  |_
|   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
|_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
-----------------------------------------------------
CHAOS CALMER (Bleeding Edge, r45269)
-----------------------------------------------------
  * 1 1/2 oz Gin            Shake with a glassful
  * 1/4 oz Triple Sec       of broken ice and pour
  * 3/4 oz Lime Juice       unstrained into a goblet.
  * 1 1/2 oz Orange Juice
  * 1 tsp. Grenadine Syrup
-----------------------------------------------------
root@BelNet:~# uptime
06:42:21 up 23 days, 21:58,  load average: 0.07, 0.03, 0.05

bmork wrote:
PsyD@f'Ke wrote:

The settings used in my example config seem to work fine (got both 2.4 and 5Ghz SSID, and can connect).
As stated in my earlier post, I'm missing the DFS channels for the 5Ghz band,

Hello, I was also a bit annoyed by this.  I  might be overlooking something, but it does look like the driver has DFS support. Enabling it seems to work for me, using a patch like this (for the mwlwifi driver):

diff --git a/mwl_main.c b/mwl_main.c
index 722d1c0..8ca8f48 100644
--- a/mwl_main.c
+++ b/mwl_main.c
@@ -166,6 +166,10 @@ static const struct ieee80211_iface_combination ap_if_comb = {
        .n_limits = ARRAY_SIZE(ap_if_limits),
        .max_interfaces = SYSADPT_NUM_OF_AP,
        .num_different_channels = 1,
+       .radar_detect_widths =  BIT(NL80211_CHAN_WIDTH_20_NOHT) |
+                               BIT(NL80211_CHAN_WIDTH_20) |
+                               BIT(NL80211_CHAN_WIDTH_40) |
+                               BIT(NL80211_CHAN_WIDTH_80),
 };
 
 
root@wrt1900ac-1:/# iw wlan1 info
Interface wlan1
        ifindex 16
        wdev 0x100000004
        addr 00:25:9c:13:0f:1d
        ssid Kjellerbod
        type AP
        wiphy 1
        channel 140 (5700 MHz), width: 80 MHz, center1: 5690 MHz
root@wrt1900ac-1:/# iw reg get
country NO: DFS-ETSI
        (2400 - 2483 @ 40), (N/A, 20), (N/A)
        (5150 - 5250 @ 80), (N/A, 23), (N/A)
        (5250 - 5350 @ 80), (N/A, 20), (0 ms), DFS
        (5470 - 5795 @ 160), (N/A, 27), (0 ms), DFS
        (5815 - 5850 @ 35), (N/A, 33), (0 ms), DFS
        (17100 - 17300 @ 200), (N/A, 20), (N/A)
        (57000 - 66000 @ 2160), (N/A, 40), (N/A)

Sorry for my late reply on this.
Catching up the next pages, so maybe it's resolved in the mean time...
I didn't patch anything, and also get same output when 'iw reg get':

root@OpenWrt:~# iw reg get
country BE: DFS-ETSI
    (2402 - 2482 @ 40), (N/A, 20), (N/A)
    (5170 - 5250 @ 80), (N/A, 20), (N/A)
    (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS
    (5490 - 5710 @ 160), (N/A, 27), (0 ms), DFS
    (57000 - 66000 @ 2160), (N/A, 40), (N/A)

But no DFS channels selectable in LuCi.
Well, since I'm only playing with it (and not actually using it as router/AP), I can wait for a fix in the future.
Thought it was worth mentioning, for other people needing that functionality badly...

I've got almost 5 days uptime using channel 108, which is a DFS channel in Sweden with reg domain SE with a DFS patch.

I'm running my own custom build.

OpenWrt Chaos Calmer r45561 / LuCI Master (git-15.110.30908-6a13d73)

And no, Luci won't show DFS channels due to a bug/feature in Luci. They know about it and they will probably fix it at some point.

If you want to use DFS channels, do the following:

1) Set everything up in Luci the way you want it and set a channel (36 or whatever).
2) Set 80MHz width if you want to run that (why wouldn't you?).
3) Notice how it actually uses 5210MHz on channel 40 and not 5180MHz (which is channel 36)?
40MHz HT uses two sets of channels (20MHz each) with a primary channel and a secondary channel beneath (HT-) or above it (HT+). 5180MHz = Channel 36. 5200MHz = Channel 40. 5220MHz = Channel 44.
VHT at 80MHz however works differently, you define a center channel and then it goes the same amount in both directions.

So 5210MHz center channel becomes 80MHz between 5180 and 5260 (not including 5260), ie spanning all of channels 36, 40, 44 and 48.
4) "Save and Apply" all settings.
5) Figure out which DFS band you want to run on. Let's for the sake of discussion say you want to run on the H-Band which is channels 100-140. Lower frequencies as we all know have better wall penetration, etc so the lower the better, really. Now here's a gotcha that I ran into and couldn't figure out right away:
I set up 80MHz on channel 100 and wireless didn't go up. On the lower bands (36-48), it will auto-adjust the center channel so that all frequencies in the 80MHz spectrum are within the channel limits, ie lowest frequency is right at channel 36, etc.
Over on the H-band it doesn't do that, so if you put in channel 100 and 80MHz it would try to put the center channel right on channel 100 and since it can't run on frequencies below channel 100 it barfs. Move the center channel up to for instance channel 108 and you have the lowest frequency within the limits (and obviously the highest frequency as well since the H-band is more than 200MHz wide).
6) SSH to the router and modify /etc/config/wireless:

config wifi-device 'radio1'
        option type 'mac80211'
        option hwmode '11a'
        option path 'platform/soc/soc:pcie-controller/pci0000:00/0000:00:03.0/0000:03:00.0'
        option htmode 'VHT80'
        option country 'SE'
        option txpower '27'    <--
        option channel '108'   <--

That's from my Kernel 4.0 running 1900AC. What you need to modify is basically the channel right at the bottom to whatever you want. Check out regulations where you live and if they allow you to boost the transmit power (like ETSI does in Europe as long as you run DFS with TPC), set it to the value that's allowed, in my case regulations here allow me to run 1W but the driver won't let me set above 500mW which is 27dBm.

Good luck.

// Stefan

(Last edited by stesmi on 28 Apr 2015, 15:23)

Linksys posted the WRT1900AC Version 2 Firmware on their site today on the WRT1900AC Firmware Downloads page.

Product:        Linksys WRT1900AC
Classification:        Firmware Release Notes


---------------------------------------------------------------------------

IMPORTANT:
- DO NOT power cycle the Router during the firmware upgrade process.

===========================================================================


Firmware version:    2.0.6.166464
Release date:        April 10, 2015

- Wireless driver updated to ver. 7.2.8.6
- Fixed 2.4GHz connectivity issue on wireless bridge/repeater mode
- Resolved low throughput issues for some 802.11n clients
- Overall throughput has been improved when five or more clients are associated.

---------------------------------------------------------------------------


Firmware version:    2.0.6.166357
Release date:        March 16, 2015

- Initial release

(Last edited by W4LNY on 28 Apr 2015, 18:49)

W4LNY wrote:

Linksys posted the WRT1900AC Version 2 Firmware on their site today on the WRT1900AC Firmware Downloads page.

Product:        Linksys WRT1900AC
Classification:        Firmware Release Notes


---------------------------------------------------------------------------

IMPORTANT:
- DO NOT power cycle the Router during the firmware upgrade process.

===========================================================================


Firmware version:    2.0.6.166464
Release date:        April 10, 2015

- Wireless driver updated to ver. 7.2.8.6
- Fixed 2.4GHz connectivity issue on wireless bridge/repeater mode
- Resolved low throughput issues for some 802.11n clients
- Overall throughput has been improved when five or more clients are associated.

---------------------------------------------------------------------------


Firmware version:    2.0.6.166357
Release date:        March 16, 2015

- Initial release

No information about what this "version 2" is.
Stock for "version 1" has not been updated.

crap crap crap ... first brick and no usb ...grr

grimley wrote:
W4LNY wrote:

Linksys posted the WRT1900AC Version 2 Firmware on their site today on the WRT1900AC Firmware Downloads page.

Product:        Linksys WRT1900AC
Classification:        Firmware Release Notes


---------------------------------------------------------------------------

IMPORTANT:
- DO NOT power cycle the Router during the firmware upgrade process.

===========================================================================


Firmware version:    2.0.6.166464
Release date:        April 10, 2015

- Wireless driver updated to ver. 7.2.8.6
- Fixed 2.4GHz connectivity issue on wireless bridge/repeater mode
- Resolved low throughput issues for some 802.11n clients
- Overall throughput has been improved when five or more clients are associated.

---------------------------------------------------------------------------


Firmware version:    2.0.6.166357
Release date:        March 16, 2015

- Initial release

No information about what this "version 2" is.
Stock for "version 1" has not been updated.

http://www.linksys.com/us/support-artic … Num=156194

V2 has no fan, lower power usage and higher CPU clock.

Product comparison between the Linksys WRT1900AC and WRT1900AC v2.

Oh yeah already tried and tried the three reboot method ... I got lazy and skipped the stop firmware ... my own damn fault just CRAP

craig.reiners wrote:

Oh yeah already tried and tried the three reboot method ... I got lazy and skipped the stop firmware ... my own damn fault just CRAP

Wow you sure a long run without need for a USB to TTL cable wink

Chadster766 wrote:
craig.reiners wrote:

Oh yeah already tried and tried the three reboot method ... I got lazy and skipped the stop firmware ... my own damn fault just CRAP

Wow you sure a long run without need for a USB to TTL cable wink


I know right?  guess I got cocky big_smile or lucky not sure which

ilukeberry wrote:
grimley wrote:
W4LNY wrote:

Linksys posted the WRT1900AC Version 2 Firmware on their site today on the WRT1900AC Firmware Downloads page.

Product:        Linksys WRT1900AC
Classification:        Firmware Release Notes


---------------------------------------------------------------------------

IMPORTANT:
- DO NOT power cycle the Router during the firmware upgrade process.

===========================================================================


Firmware version:    2.0.6.166464
Release date:        April 10, 2015

- Wireless driver updated to ver. 7.2.8.6
- Fixed 2.4GHz connectivity issue on wireless bridge/repeater mode
- Resolved low throughput issues for some 802.11n clients
- Overall throughput has been improved when five or more clients are associated.

---------------------------------------------------------------------------


Firmware version:    2.0.6.166357
Release date:        March 16, 2015

- Initial release

No information about what this "version 2" is.
Stock for "version 1" has not been updated.

http://www.linksys.com/us/support-artic … Num=156194

V2 has no fan, lower power usage and higher CPU clock.

Product comparison between the Linksys WRT1900AC and WRT1900AC v2.


I like my V1 fan smile

(Last edited by alirz on 28 Apr 2015, 20:44)

Please report mwlwifi issues on github, so Marvell will see it smile

ilukeberry wrote:

http://www.linksys.com/us/support-artic … Num=156194

V2 has no fan, lower power usage and higher CPU clock.

Product comparison between the Linksys WRT1900AC and WRT1900AC v2.

The CPU is clocked higher, but it's from a different family (Armada 385).