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.

gufus wrote:
ngbeslhang wrote:

On a side note, I found that there's two version of OpenWrt for WRT1900ac v1 (http://wiki.openwrt.org/toh/linksys/wrt1900ac), Caiman and Mamba. I chose Mamba because I didn't see Caiman on the rest of the page. Should have I installed Caiman, or Mamba is better?

Trunk
For initial flashing use
openwrt-mvebu-armada-xp-linksys-mamba-squashfs-factory.img

For sysupgrade-ing use
openwrt-mvebu-armada-xp-linksys-mamba-squashfs-sysupgrade.tar

WRT1900AC(v1) - Mamba
WRT1900AC(v2) - Cobra
WRT1200AC - Caiman

Although I already installed the correct version, thanks for telling me there's system upgrade package. smile

(Last edited by ngbeslhang on 8 Oct 2015, 05:16)

I recently purchased the WRT1900ACv2 and installed OpenWRT, but with both 15.05 final and RC3 I have to reboot the router several times a day! Is there a firmware known to be stable on this router, or how can I go about troubleshooting the issue?

JW0914 wrote:
suihkulokki wrote:
JW0914 wrote:

In regards to the S3 and Nexus 7, both have a wireless N controller, so setting the channel to N [legacy is b/g] should work.  What occurred when you set the channel to N and tried to connect to the router from the Nexus 7 and S3?

It 2.4Ghz new is set to N, They pick up the IP over dhcp, but trying to move a bigger chunk of data (like a typical web page), traffic stops moving completely.

What happens if you connect a non-cellular device to the 2.4gHz [set to N]? Do you get the same results?  If you don't, it would indicate an issue on the S3 and NX7, most likely caused by an app, or multiple apps, on the devices... however, in order to rule this out, a non-android device will need to be connected to see if the results are replicated. 
...
Do you have an issue connecting to other wireless N networks with the S3 or NX7?

Both the S3 and NX7 connected just fine the previous network which DIR-825 using 2.4ghz in Wireless-N. No other device (android or other) had problems connecing to WRT1900AC when it was in N instead of legacy mode. And the android devices are strictly play-store only.

Meanwhile, I've found about: https://github.com/kaloz/mwlwifi/issues/36 which is a much bigger issue now. Time to downgrade to RC3 it seems

Possibly related, but setting WRT1900AC as WDS client didn't work. No traffic from br-lan moved over to wifi interface, despite being in the same bridge.

bluethegrappler wrote:

I recently purchased the WRT1900ACv2 and installed OpenWRT, but with both 15.05 final and RC3 I have to reboot the router several times a day! Is there a firmware known to be stable on this router, or how can I go about troubleshooting the issue?

You might be one of the unlucky ones who hit the wireless driver's bug that causes issues like this. Please add more information about your setup to https://github.com/kaloz/mwlwifi/issues/21 . We are waiting on Marvell to publish a fixed version.

deniz2304 wrote:

Which OpenWrt Firmware can I use for Linksys WRT1900ACS-EU v1 or v2?

Support for the WRT1900ACS (Shelby) is available in CC and trunk now wink

BusyBox v1.23.2 (2015-06-18 06:39:10 CEST) built-in shell (ash)

  _______                     ________        __
|       |.-----.-----.-----.|  |  |  |.----.|  |_
|   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
|_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
-----------------------------------------------------
CHAOS CALMER (15.05-rc3, r46163)
-----------------------------------------------------
  * 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@OpenWrt:~# uptime
03:16:05 up 24 days, 41 min,  load average: 0.00, 0.01, 0.04


Not bad big_smile Running cool (not so quiet) thanks to gufus's fan script as well as the cpu load balancing.
Wanting to update to final but unsure if ill keep this "stability"

Kaloz wrote:
deniz2304 wrote:

Which OpenWrt Firmware can I use for Linksys WRT1900ACS-EU v1 or v2?

Support for the WRT1900ACS (Shelby) is available in CC and trunk now wink


Was the underlying Marvel chipset changed in the ACS release to make it not susceptible to the ongoing bugs as V1 and V2 have been having?

mercsniper wrote:
Kaloz wrote:
deniz2304 wrote:

Which OpenWrt Firmware can I use for Linksys WRT1900ACS-EU v1 or v2?

Support for the WRT1900ACS (Shelby) is available in CC and trunk now wink


Was the underlying Marvel chipset changed in the ACS release to make it not susceptible to the ongoing bugs as V1 and V2 have been having?

I have not the router, it get soon

mercsniper wrote:
Kaloz wrote:
deniz2304 wrote:

Which OpenWrt Firmware can I use for Linksys WRT1900ACS-EU v1 or v2?

Support for the WRT1900ACS (Shelby) is available in CC and trunk now wink


Was the underlying Marvel chipset changed in the ACS release to make it not susceptible to the ongoing bugs as V1 and V2 have been having?

No. And again, it's a driver bug in the wireless driver, so even if there would be a newer chipset, the driver would still have the same issue.

Guess I will stick with my V1 then. No point in upgrading then if it works (when the driver doesnt lock it up).

I have been running CC 15.05 on V1 for almost a week without any mods - no crashes or hangups, however I don't have hardware to push it to max. Android phones and tablets are the only ones using wifi at my place, and although they are capable of high link level speeds, they are tuned in a way which causes relatively miserable "real world" transfer speeds, i.e. using samba.

After reading this thread for a while, I want to share some ideas.

I suppose lots of people here are using fan scripts. In addition to that, they can try lowering transmission power to levels suitable to their environment. Just walk around your place with client device and check transfer rates, find the lowest power setting which still works ok - anything higher is just a heat.

It attracts attention how some of us are having pretty good experience with OpenWRT on this device, and how some of us get crashes multiple times a day. What is the difference? Configuration, client, devices, environment, network traffic? I think, unless we find a deterministic way to reproduce a crash, nothing will be fixed regarding that. So, "lucky" guys with multiple crashes a day, tell as much as you can about your devices, network and etc.

The 2nd interesting thing I noticed, it seems lots of you are using PPPoE, VLANS, and basically have to deal with MTU<>1500. Could it be the difference between users who have frequent crashes and users who do not?

I tried to install collectd but it did not work. This is the output:

Installing collectd (5.4.2-1) to root...
Downloading http://downloads.openwrt.org/chaos_calm … mvebu.ipk.
Installing libltdl (2.4-1) to root...
Downloading http://downloads.openwrt.org/chaos_calm … mvebu.ipk.
Configuring libltdl.
Configuring collectd.
plugin_load: opendir (/usr/lib/collectd) failed: No such file or directory
plugin_load: opendir (/usr/lib/collectd) failed: No such file or directory
plugin_load: opendir (/usr/lib/collectd) failed: No such file or directory
plugin_load: opendir (/usr/lib/collectd) failed: No such file or directory
plugin_load: opendir (/usr/lib/collectd) failed: No such file or directory
plugin_load: opendir (/usr/lib/collectd) failed: No such file or directory
plugin_load: opendir (/usr/lib/collectd) failed: No such file or directory
plugin_load: opendir (/usr/lib/collectd) failed: No such file or directory
Found a configuration for the `network' plugin, but the plugin isn't loaded or didn't register a configuration callback.

How stable is the latest stable version? I am fed up with stock firmware which crashes every 20ish days, or even lock up wifi.

zhengy4 wrote:

How stable is the latest stable version? I am fed up with stock firmware which crashes every 20ish days, or even lock up wifi.

The most stable version is Release Candidate 3 (RC3). However, it probably has around the same stability as stock; there are still going to be times where it locks up.

Id0n0tunderstand wrote:

I tried to install collectd but it did not work. This is the output:

Installing collectd (5.4.2-1) to root...
Downloading http://downloads.openwrt.org/chaos_calm … mvebu.ipk.
Installing libltdl (2.4-1) to root...
Downloading http://downloads.openwrt.org/chaos_calm … mvebu.ipk.
Configuring libltdl.
Configuring collectd.
plugin_load: opendir (/usr/lib/collectd) failed: No such file or directory
plugin_load: opendir (/usr/lib/collectd) failed: No such file or directory
plugin_load: opendir (/usr/lib/collectd) failed: No such file or directory
plugin_load: opendir (/usr/lib/collectd) failed: No such file or directory
plugin_load: opendir (/usr/lib/collectd) failed: No such file or directory
plugin_load: opendir (/usr/lib/collectd) failed: No such file or directory
plugin_load: opendir (/usr/lib/collectd) failed: No such file or directory
plugin_load: opendir (/usr/lib/collectd) failed: No such file or directory
Found a configuration for the `network' plugin, but the plugin isn't loaded or didn't register a configuration callback.

Did you install luci-app-statistics?

(Last edited by northbound on 9 Oct 2015, 01:57)

davidc502 wrote:
zhengy4 wrote:

How stable is the latest stable version? I am fed up with stock firmware which crashes every 20ish days, or even lock up wifi.

The most stable version is Release Candidate 3 (RC3). However, it probably has around the same stability as stock; there are still going to be times where it locks up.

I am fed up with this 1900ac crap, and have no patience waiting for another firmware, can anyone recommend me a stable router on the market?

davidc502 wrote:
gonzlobo wrote:

Man I wish this PunBB forum software had filtering settings like vBulletin et al.

I hear ya.

if I may ask, which of us is it that you would want to filter?

It doesn't matter now, but it wasn't you wink

It's been a little tiring listening to the constant complaining from one individual.

(Last edited by davidc502 on 9 Oct 2015, 04:40)

My WRT1900AC v1 has used the Stock Firmware without problems.  (I will upgrade to OPENWRT in due time)
AT&T Uverse 10mb Service
Motorola NVG-510 Gateway <=> WRT1900AC v1
Windows 10 Desktop (lots of Emule traffic), Roku (Netflix) & Lumia 1320 Windows Phablet / Wife's LG phone.

I THOUGHT the Linksys Router was behind Windows 10 intermittently indicating I had "Limited Internet Access." (Yellow Triangle) Still had normal access & the message would only resolve when I power cycled or rebooted the Router.  but the message always returned soon.
Last night, I updated the Desktop's Intel 82579V Gigabit Network Adapter driver to ver 12.12.140.22 (dated 2/15/2015) The prior one was from 2013 Works fine
But... No more limited internet connection messages!

I'm sure Linksys, Marvel and 3rd parties will forge ahead to produce a more powerful tool in time.
The thing that got me to jump onto the WRT1900AC was OPENWRT being able to run Privoxy on the router itself. 
(I've run Privoxy Desktop since 98' so I can wait a bit longer)
This is a learning experience for all parties involved.
(I got my WRT1900AC v1 for $129.00 returned by someone who could not wait for OPENWRT?)

dlang wrote:
davidc502 wrote:
gonzlobo wrote:

Man I wish this PunBB forum software had filtering settings like vBulletin et al.

I hear ya.

if I may ask, which of us is it that you would want to filter?

Not you. Not you.

deniz2304 wrote:

Which version of Here http://wiki.openwrt.org/toh/linksys/wrt1900acs I can use for Linksys WRT1900ACS?

or here https://downloads.openwrt.org/snapshots … u/generic/

Thanks

Wait a few days, I'm sure Builder mvebu will build it.
http://buildbot.openwrt.org:8010/builders/mvebu

Then you'll see the image here
http://downloads.openwrt.org/snapshots/ … u/generic/

BTY

Linksys WRT1900ACS (Shelby) is in trunk now
https://dev.openwrt.org/timeline?from=2 … ate=Update

(Last edited by gufus on 9 Oct 2015, 07:16)

Marvell swore they will release a new revision of the WiFi driver soon, whatever they mean by "soon"... As a positive note, but not related to the WiFi driver, we might see a new revision of the mvneta driver in a couple of weeks time that will integrate one of the dedicated offload engines, namely BM (buffer manager) with PnC (Parser and Classifier) in the works but without a release date yet.

nitroshift

JW0914 wrote:
plamka00 wrote:
plamka00 wrote:

Hi,

I've a small problem with TFTP Firmware flashing.
I've got two WRT1900AC v1 where at both the power lamp was blinking, so I tried to TFTP flash them as described at the wiki.
With the first everything was ok, but the second one will not flash.
The router connects to the tftpd32 server but the transferrate stands at 0 B/s and nothing happens. After a while I get an 'Undefined error code' (0). Afterwards the NAND is erased, which is "ok" and then the NAND is written again which also leads to an "ok".

Can someone give an adwise how to flash the router now?
Thanks!

Hi! The WAN is not blinking at all - its dark. When I start the device only the power LED is blinking. I've checked again the booting log and it is almost the same like that shown in the wiki. The biggest difference is at the "auto_recovery" section:

BootROM 1.20
Booting from NAND flash
Step 1: First phase of PEX-PIPE Configuration
Step 2: Configure the desire PIN_PHY_GEN
Step 3 QSGMII enable
Step 4: Configure SERDES MUXes
Step 5: Activate the RX High Impedance Mode
Step 6: [PEX-Only] PEX-Main configuration (X4 or X1)
Step 6.2: [PEX-Only] PCI Express Link Capabilities
Step 7: [PEX-X4 Only] To create PEX-Link
Steps 7,8,9,10 and 11
Steps 12: [PEX-Only] Last phase of PEX-PIPE ConfigurationSteps 13: Wait 

15ms before checking resultsSteps 14: [PEX-Only]  In order to 

configureSteps 15: [PEX-Only]  In order to configureSteps 16: [PEX-Only] 

Training Enablestep 17: max_if= 0x7
step 17:  PEX0  pexUnit= 0
PEX0 : Detected No Link. Status Reg(0x00041A64) = 0x00000002
step 17:  PEX1  pexUnit= 0
step 17:  PEX2  pexUnit= 0
** Link is Gen1, check the EP capability
 --> 0040
mvPexConfigRead: return addr=0x%x0040
 --> 5001
 --> 5001
 --> 7005
 --> 7005
 --> 0010
 --> DC12
Gen2 client!
step 17:  PEX3  pexUnit= 0
PEX3 : Detected No Link. Status Reg(0x0004DA64) = 0x00000001
step 17:  PEX4  pexUnit= 1
PEX4 : Detected No Link. Status Reg(0x00081A64) = 0x00000001
step 17:  PEX5  pexUnit= 1
PEX5 : Detected No Link. Status Reg(0x00085A64) = 0x00000001
step 17:  PEX6  pexUnit= 1
PEX6 : Detected No Link. Status Reg(0x00089A64) = 0x00000001
                                                            DDR3 

Training Sequence - Ver 4.5.DDR3 Training Sequence - Static MC Init
DDR3 Training Sequence - HW Training Procedure
DDR3 Training Sequence - Switching XBAR Window to FastPath Window
BootROM: Image checksum verification PASSED

 __   __                      _ _
|  \/  | __ _ _ ____   _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| |  | | (_| | |   \ V /  __/ | |
|_|  |_|\__,_|_|    \_/ \___|_|_|
         _   _     ____              _
        | | | |   | __ )  ___   ___ | |_
        | | | |___|  _ \ / _ \ / _ \| __|
        | |_| |___| |_) | (_) | (_) | |_
         \___/    |____/ \___/ \___/ \__|
 ** LOADER **


U-Boot 2011.12 (Feb 06 2014 - 17:14:13) Marvell version: v2011.12 

2013_Q1.2

Boot version:v1.3.25

Board: RD-AXP-GP rev 1.0
SoC:   MV78230 B0
       running 2 CPUs
       Custom configuration
CPU:   Marvell PJ4B (584) v7 (Rev 2) LE
       CPU 0
       CPU    @ 1200 [MHz]
       L2     @ 600 [MHz]
       TClock @ 250 [MHz]
       DDR    @ 600 [MHz]
       DDR 32Bit Width, FastPath Memory Access
       DDR ECC Disabled
DRAM:  256 MiB

Map:   Code:            0x0fea7000:0x0ff5e2d4
       BSS:             0x0ffefd80
       Stack:           0x0f9a6ef8
       Heap:            0x0f9a7000:0x0fea7000

NAND:  Spansion 1Gb(ID=F101) 128 MiB
MMC:   MRVL_MMC: 0
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01


#### auto_recovery ####
[u_env] get auto_recovery == no
[u_env] get auto_recovery == no
[u_env] get boot_part == 2
[u_env] get boot_part_ready == 3
auto_recovery enabled:0, boot_part:2, boot_part_ready:3

PEX 0.0(0): Detected No Link.
PEX 0.1(1): Root Complex Interface, Detected Link X1, GEN 1.1
PEX 0.2(2): Root Complex Interface, Detected Link X1, GEN 2.0
PEX 0.3(3): Detected No Link.
PEX 1.0(4): Detected No Link.
PEX 1.1(5): Detected No Link.
PEX 1.2(6): Detected No Link.

boot_end Offset: 0x100000
u_env_off Offset: 0x100000
s_env_off Offset: 0x140000
devinfo Offset: 0x900000

===================
total_badCount: 0
boot_badCount: 0
u_env_badCount: 0
s_env_badCount: 0
buff_badCount: 0
===================

FPU initialized to Run Fast Mode.
USB 0: Host Mode
USB 1: Host Mode
USB 2: Device Mode
Modules Detected:
mvEthE6171SwitchBasicInit finished
Net:   mvSysNetaInit enter
set port 0 to rgmii enter
set port 1 to rgmii enter
egiga0 [PRIME], egiga1
modify Phy Status
auto_recovery_check changes bootcmd: run altnandboot
Hit any key to stop autoboot:  0

NAND read: device 0 offset 0x3200000, size 0x400000
 4194304 bytes read: OK
Wrong Image Format for bootm command
ERROR: can't get kernel image!

Rename the firmware image to blk-mamba.128mb.img and TFTP flash it again. 

Some batches of the the WRT1900ac will not accept another name when flashing via TFTP (mine happens to be one of them), and is why the footnote of the the image name was added to the TFTP flash section of the Wiki.  I'd also set the server IP to .20 as I've been unable to get it to flash at .2

Successful TFTP Flash Output

Marvell>> setenv firmware_name blk-mamba.128mb.img
Marvell>> setenv ipaddr 192.168.1.1
Marvell>> setenv serverip 192.168.1.20
Marvell>> run flash_pri_image
mvNetaSpeedDuplexSet
Using egiga0 device
TFTP from server 192.168.1.20; our IP address is 192.168.1.1
Filename 'blk-mamba.128mb.img'.
Load address: 0x2000000
Loading: T #########################################################
####################################################################
#####         ##########################################################
done
Bytes transferred = 33292288 (1fc0000 hex)
NAND erase: device 0 offset 0xa00000, size 0x4000000
Erasing at 0x49e0000 -- 100% complete.
OK
NAND write: device 0 offset 0xa00000, size 0x1fc0000
33292288 bytes written: OK

Hi, I did it from the beginning like that and everything was ok except the datatransfer from tftpd32 to the router.
However, now the problem is solved. I tryed everything on an other computer and it worked. So I do not know where the problem was, but the router is now successfully flashed. Thanks!