Hi there!!! I recently bought the Linksys EA6200 smart wifi router.

I checked the Wiki / toh page and found this:

So, basicly is the ea6300 firmware compatible with this router? I've read that the ea6200 hw is pretty the same as the ea6300.

Anyone has running OpenWRT on this device?

I'd running OpenWrt on my tp-link 841 from 3 years with no problems, and I like to install it to my ea6200.

ty in advance

(Last edited by luiggybit on 28 Apr 2016, 00:06)

Any suggestions?

-1

I ended up installing DD-WRT

I have tried to compile and install the latest OpenWRT on EA6200,  But finally I got :
--------------
[    7.090777] UBI: auto-attach mtd5
[    7.093921] ubi0: attaching mtd5
[    7.205939] ubi0: scanning is finished
[    7.236784] ubi0: volume 1 ("rootfs_data") re-sized from 9 to 119 LEBs
[    7.244063] ubi0: attached mtd5 (name "ubi", size 25 MiB)
[    7.249445] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    7.256329] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    7.263096] ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
[    7.270022] ubi0: good PEBs: 199, bad PEBs: 1, corrupted PEBs: 0
[    7.276012] ubi0: user volume: 2, internal volumes: 1, max. volumes count: 128
[    7.283208] ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 432917767
[    7.292219] ubi0: available PEBs: 0, total reserved PEBs: 199, PEBs reserved for bad PEB handling: 19
[    7.301468] ubi0: background thread "ubi_bgt0d" started, PID 334
[    7.308893] block ubiblock0_0: created from ubi0:0(rootfs)
[    7.349335] squashfs: SQUASHFS error: unable to read id index table
[    7.355892] List of all partitions:
[    7.359395] 1f00             512 mtdblock0  (driver?)
[    7.364465] 1f01            1024 mtdblock1  (driver?)
[    7.369498] 1f02             512 mtdblock2  (driver?)
[    7.374556] 1f04            4095 mtdblock4  (driver?)
[    7.379591] 1f05           25600 mtdblock5  (driver?)
[    7.384637] 1f06           99328 mtdblock6  (driver?)
[    7.389673] 1f07            1869 mtdblock7  (driver?)
[    7.394719] 1f08           97458 mtdblock8  (driver?)
[    7.399756] 1f09           85760 mtdblock9  (driver?)
[    7.404802] fe00            7068 ubiblock0_0  (driver?)
[    7.410007] No filesystem could mount root, tried:  squashfs
[    7.415672] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,8)
[    7.423984] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,8)
--------
I think the rootfs has some problem(maybe it is the ubi format problem ??)
Did some one get this problem before ???

(Last edited by tekkamanninja on 15 May 2016, 11:12)

https://wiki.openwrt.org/toh/linksys/linksys_ea6200_1.0

Looks very much work in progress.

I had a look at the source in target/bcm53xx and there is not much there except for generic build code. So I guess some more work is needed building a profile for this unit. But there is probably enough information there to get a build profile working.

(Last edited by Xotic750 on 15 May 2016, 12:45)

I have made my EA6200 boot into OpenWRT, with a kernel patch below:

diff --git a/drivers/mtd/Kconfig b/drivers/mtd/Kconfig
index 63b6dbd..a9863b9 100644
--- a/drivers/mtd/Kconfig
+++ b/drivers/mtd/Kconfig
@@ -18,6 +18,12 @@ config MTD_ROOTFS_ROOT_DEV
        bool "Automatically set 'rootfs' partition to be root filesystem"
        default y
 
+config MTD_ROOTFS_ROOT_DEV_IGNORE_FORMER
+       bool "ignore the former 'rootfs' partition found"
+       depends on MTD_ROOTFS_ROOT_DEV
+       default n
+
+
 config MTD_SPLIT_FIRMWARE
        bool "Automatically split firmware partition for kernel+rootfs"
        default y
diff --git a/drivers/mtd/ubi/block.c b/drivers/mtd/ubi/block.c
index 965ff37..180c4c3 100644
--- a/drivers/mtd/ubi/block.c
+++ b/drivers/mtd/ubi/block.c
@@ -452,7 +452,8 @@ int ubiblock_create(struct ubi_volume_info *vi)
 
        if (!strcmp(vi->name, "rootfs") &&
            config_enabled(CONFIG_MTD_ROOTFS_ROOT_DEV) &&
-           ROOT_DEV == 0) {
+           (config_enabled(CONFIG_MTD_ROOTFS_ROOT_DEV_IGNORE_FORMER) ||
+            ROOT_DEV == 0)) {
                pr_notice("ubiblock: device ubiblock%d_%d (%s) set to be root filesystem\n",
                          dev->ubi_num, dev->vol_id, vi->name);
                ROOT_DEV = MKDEV(gd->major, gd->first_minor);

Sorry for this hacking style, I just want to point out where is the problem:
(1)kernel(linux-bcm53xx) will parse the partition table by reading MTD block, then it will get:
[    6.118072] Creating 9 MTD partitions on "brcmnand.0":
[    6.123205] 0x000000000000-0x000000080000 : "boot"
[    6.129153] 0x000000080000-0x000000180000 : "nvram"
[    6.135221] 0x000000180000-0x000000200000 : "nvram"
[    6.141265] 0x000000200000-0x00000020001c : "firmware"
[    6.148049] 0x00000020001c-0x000000600000 : "linux"
[    6.153999] 0x000000600000-0x000001f00000 : "ubi"
[    6.159838] 0x000001f00000-0x000008000000 : "firmware"
[    6.166873] 0x000001f0001c-0x0000020d3650 : "linux"
[    6.172874] 0x0000020d3650-0x000008000000 : "rootfs"

then kernel will set "0x0000020d3650-0x000008000000 : "rootfs" " as rootfs which is wrong.

(2)after (1) ubi driver will parse the ubi partition, then find a partition with roorfs lable. ubi driver can set this partition as rootfs, but it already got a "rootfs" in (1), so this time, the right rootfs will be ignore.

(3) then system boot fail because of getting the wrong rootfs partition.
---------------------

my patch just makes kernel to ignore   the former rootfs partiton and use the rootfs in ubi partiton.

But I found another problem, the image I made just can boot once.  In the next boot I got:

Boot version: v0.5.5

Device eth0:  hwaddr 98-FC-11-F0-AF-BD, ipaddr 192.168.1.1, mask 255.255.255.0
        gateway not set, nameserver not set
Invalid boot block on disk
Loader:raw, invalid tftp target filename (:)!
Could not load :: Invalid parameter
Invalid boot block on disk
nflash1.trx CRC check failed!
Changed to the other image 1
Loader:raw Filesys:raw Dev:nflash0.os2 File: Options:(null)
Loading: .... 4678976 bytes read

that means I system falls back to the default kernel.
Does some one know how to solve this problem ???

(Last edited by tekkamanninja on 16 May 2016, 16:57)

Hi,

I used https://downloads.openwrt.org/snapshots … uashfs.trx as stated in https://wiki.openwrt.org/toh/linksys/linksys_ea6200_1.0

Device stopped responding to ping and showed no wifi activity.

I power cycled and it became ping responsive, but no GUI, no wifi and no telnet.

Can I still revert to original? Can anyone give me a hint?

Be so kind to RTFW before posting.

Hello i have a ea6200 ac900 and i read that the ea6300 is a compatible firmware
and i neet to know if the 5gz and 2.4 is working fine with openwrt.

Regards