OpenWrt Forum Archive

Topic: Installation Method for Linksys EA4500

The content of this topic has been archived between 28 Mar 2018 and 18 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

I bought linksys ea4500 router days ago which advertised as a supported router in openwrt device list. I also read ea4500 is the best value router for openwrt. Anyway after bought I tried to install openwrt using image provided by candyhouse project. But that image have some problems and WiFi throughput is horrible

I saw since chaos calmer release this router officially supported by openwrt. But in the download page there is only files that suitable for serial flashing. To do this I have to open the case and solder the Serial cable. I little bit upset with this method (even though I have USB to TTL cable and necessary stuff)

Image provided by the candyhouse project can be flash directly through the OEM firmware and I re-flash OEM successfully without issues. Is official openwrt provide .bin file for direct flashing this router ? or I have to build image using openwrt build system ? I don't have any experience with building oprnwrt.

can someone please help me in this ? I really want to flash stable openwrt CC in my linksys ea4500. what is the most suitable way to do this ?

thanks !!

I'm kind of on the same boat as you, but my problem is that Candyhouse project sends me to Claudio's GitHub repository and there it tells me to build the image. You appear to have already the "image provided by candyhouse" project.

Can you tell me where did you get this ready to install image?.

Regarding your problem, on the OpenWRT page dedicated to Linksys EA4500 / E4200 v2 (http://wiki.openwrt.org/toh/linksys/ea4500) they explain to install the candyhouse image.... then......put the chaos files in a usb stick and run some procedure to install it...no serial needed. see it and let me know.

regards
Joni

I don't know, i'm trying to get there myself.

This image working fine but the wifi throughput is not good.  And also I tried to install openvpn but it failed because of the kernel version. LUCI is also little bit laggy first but after couple of reboots it fixed. I re-flashed stock again because I need strong wifi

I download your file using the link you sent but i still cannot find it on the candyhouse project. Can you post the link to the page where you saw that file (or saw the link to the file)?

thanks
Joni

PunBB bbcode test

Got it! thanks. Now I understand what they are talking about. As mentioned , EA4500 was added to the Chaos Calmer release but not squashfs (noted by Adrian on the same thread), that's why we have to go Claudio's first then perform the steps with USB stick to put Chaos in.
I will try this and report back.

(Last edited by joni on 31 Oct 2015, 21:01)

Okay I really cant understand what is the different between normal image and squashfs. :S The image I flashed only gave me 16MB of storage even the router has 128MB ( I thought this is the difference) anyway let me know if you are able to flash successfully and if it's possible please check the WiFi throughput as well.

Thanks !!

Hi,
a lot happened but let me sum up for you:

   The instructions on the wiki to install OpenWrt on EA4500 without using serial cable (1) do not work with the Fiona Claudio's based build (2).

   I managed to get it working after a lot of investigating, some courage and a lot of luck I guess.

   I'm going to put a copy of the instructions that do not work (1) here for future reference in case they are updated and invalidate my comments.

INSTRUCTIONS

-------
Prepare:

get the right Image for Your device from Candyhouse Projekt (3)
build an initramfs image from openwrts buildroot or download mine from Here (4)
download openwrt-kirkwood-ea4500-rootfs.ubi and openwrt-kirkwood-ea4500-uImage from Here (5)
format an usb pendrive with ext3 (no idea if fat is working? fatload available in uboot?) and mount it. (if it wont work, use ext2)
Put uImage, openwrt-kirkwood-ea4500-rootfs.ubi and openwrt-kirkwood-ea4500-uImage on that usb stick. Cleanly unmount it !!!

The flashing process:

Flash Your ea4500 wit the candyhouse image.
after reboot candyhouses openwrt will be up, login using telnet/ssh
plugin the prepared pen drive and run the following commands:

fw_setenv bootcmd 'run owrt_usb; run nandboot'
fw_setenv owrt_usb 'usb start; sleep 5;ext2load usb 0:1 ${loadaddr} /uImage; setenv bootargs $(console) $(mtdparts) root=/dev/ram rw; bootm ${loadaddr}'
mkdir /sda1 && mount /dev/sda1 /sda1           (no mistake it does not boot without it)
reboot

After a few, openwrt initramfs will be boot from this pen drive. Login using telnet/ssh and rum Commands:

mkdir /sda1 && mount /dev/sda1 /sda1 && cd /sda1
ubiformat /dev/mtd3 && ubiformat /dev/mtd3 -f openwrt-kirkwood-ea4500-rootfs.ubi

Only if ubiformat and mount didn't produce any errors continue with: (otherwise youre fucked!!)

mtd erase kernel
mtd write openwrt-kirkwood-ea4500-uImage kernel
fw_setenv bootcmd 'run owrt_usb; run owrt_boot'
fw_setenv owrt_usb 'usb start; sleep 5;ext2load usb 0:1 ${loadaddr} /uImage; setenv bootargs $(console) root=/dev/ram rw; bootm ${loadaddr}'
fw_setenv owrt_boot 'nand read.e ${loadaddr} 0x200000 0x200000; setenv bootargs $(console) ubi.mtd=3 root=ubi0:rootfs rootfstype=ubifs rw; bootm ${loadaddr}'
fw_setenv auto_recovery no
reboot

Now you are done. With the usb stick connected and uImage on it, the router will boot this image. otherwise it boots from nand.
Have fun!

------

COMMENTS

based on my experience:

   first issue was when mounting the usb pen, it gave me the error :
   
   NTFS signature is missing.
   Failed to mount '/dev/sda1': Invalid argument
   The device '/dev/sda1' doesn't seem to have a valid NTFS.

   Maybe the wrong device is used? Or the whole disk instead of a
   partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
   

   I search a lot about this but most issues were about trying to mount NTFS and not Ext. I tried Ext2, Ext3. even tried Fat and Fat32.
   At some point I found that I could mount it using -t ext2 parameter.
   I proceeded for the reboot (after the 2 fw_setenv commands and the mount)
   after the reboot the same banner and OpenWrt version appeared and I thought this can't be right but there was no way to tell, no intructions on how to verify, nothing..(afterwards I knew it was wrong).
   The next block of commands started with the mount (again had to put -t ext2) and then a format command which when i ran it produced the following:
   
   ubiformat: mtd3 (nand), size 27262976 bytes (26.0 MiB), 208 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
   libscan: scanning eraseblock 207 -- 100 % complete
   ubiformat: 43 eraseblocks are supposedly empty
   ubiformat: warning!: 165 of 208 eraseblocks contain non-UBI data
   ubiformat: continue? (y/N) N
   

   And as you can see i did not go ahead since i was not sure if this was expected or not.
   After investigating without finding any clear explanation I decided to go ahead because there was a statement somewhere that this might be expected (the warning).
   There were some more warnings and I proceeded with the next format (did not use the one liner &&, just ran it separetly).
   That went well, no warnings, so now it was the critical point before the erase kernel (mentioned on the instructions with a warm "your f'ed" if there's errors before...I had only warnings so..).
   
   I decided to go ahead with the kernel erase:
   
   root@OpenWrt:/sda1# mtd erase kernel
   Could not open mtd device: kernel
   Could not open mtd device: kernel

   

   after some investigation about mtd I ran a command to list the mtd "partitions"

   root@OpenWrt:/sda1# cat /proc/mtd
   dev:    size   erasesize  name
   mtd0: 00080000 00020000 "u-boot"
   mtd1: 00020000 00020000 "u_env"
   mtd2: 00020000 00020000 "s_env"
   mtd3: 01a00000 00020000 "kernel1"
   mtd4: 01760000 00020000 "rootfs1"
   mtd5: 01a00000 00020000 "kernel2"
   mtd6: 01760000 00020000 "ubi"
   mtd7: 04a00000 00020000 "syscfg"

   At this point I looked at the flash layout on the instructions page and on both of them (stock and openWRT recommended) and on both the kernel mtd match the same address as kernel1 on my mtd list.
   I decided to go ahead and use "kernel1" without noticing that I already had formated mtd3 on the previous commands (what an idiot!).
   Everything went well for the remaning commands.
   I unmounted the pen and removed it just before the reboot.
   This is where it went wrong because the router never came up again. Lights ok on the ethernet connection , the cisco bright with logo on top , dead as door nail...
   At this point I thought to my self well...I can still try to boot the pen as mentioned in the instructions.
   Turned power off, inserted pen, power on.....voila' it booted...but now I got what I should have got with the first pen boot...the Designated driver build from uImage file.
   I immeadiatly proceed to check mtd (because I noticed the double mtd3 burn I performed) and showed:
   
   dev:    size   erasesize  name
   mtd0: 00080000 00020000 "u-boot"
   mtd1: 00020000 00020000 "u-boot environment"
   mtd2: 00200000 00020000 "kernel"
   mtd3: 01c00000 00020000 "root"

   So now this made sense , since kernel is now alone (no 1 or 2) and mtd3 is root.
   This is the layout that is expected when you boot from the usb pen that should happened before and didn't.
   I reformatted mtd3 again (and wrote the ubi image), removed the pen and rebooted.
   It came back to designated driver again but now from NAND (since I removed the pen before reboot).
   There was no Luci (web console), I tried changing the password and reboot , but it came back again and the password change did not stick.
   I tried to set an IP address for my local network (I worked always with direct cable from my pc until now) and disabled DHCP using VI and config files (/etc/config/network and /etc/config/dhcp).
   After reboot nothing was sticking, no IP , no password , SSH keys being generated anew with SSH complaining..
   I noticed that running df only showed tmpfs file system listed twice for mount points /tmp and /dev
   After some reboots with same outcome I decided to do a power OFF.
   After power ON I could not login to SSH because it was not accepting any password. Telnet was not available.
   I decided to try via http and to my surprise Chaos Calmer  came in (designated driver version was gone)and Luci was available.
   Luci was stating that there was no password set, so i set it, rebooted and now i could login with SSH.
   From now on I changed the IP, moved to my local network and everything is sticking after Chaos Calmer appeared.
   Checked with df and had rootfs and ubi0:rootfs and also the 2 tmpfs.
   

(1) link that I sent you before about wiki instructions: http://wiki.openwrt.org/toh/linksys/ea4500 
(2) link that you sent me before with Fiona's build: https://mega.nz/#!bNAhDI6S!PZQTb8X4XxOf … tSSk6za9uc
       Fiona's Claudio's based build shows: CHAOS CALMER (Bleeding Edge, unknown)
(3) Project deprecated, old repo, no ready to flash imgs: http://www.wolfteck.com/projects/candyhouse/openwrt/
(4) uImage http://cloud.directupload.net/1AhK
       uImage booting from Usb shows : DESIGNATED DRIVER (Bleeding Edge, r47048)
(5) Chaos Calmer on OpenWrt builds : https://downloads.openwrt.org/chaos_cal … d/generic/
       Chaos calmer after sucessfully installed shows: CHAOS CALMER (15.05, r46767)

(Last edited by joni on 1 Nov 2015, 23:14)

Here's the action log. A lot of testing commands I used are not here but the essential is.

 === IMPORTANT ============================
  Use 'passwd' to set your login password
  this will disable telnet and enable SSH
 ------------------------------------------


BusyBox v1.23.2 (2015-09-09 11:08:31 BST) built-in shell (ash)

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 CHAOS CALMER (Bleeding Edge, unknown)
 -----------------------------------------------------
  * 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:/#
root@OpenWrt:/# fw_setenv bootcmd 'run owrt_usb; run nandboot'
root@OpenWrt:/# fw_setenv owrt_usb 'usb start; sleep 5;ext2load usb 0:1 ${loadad
dr} /uImage; setenv bootargs $(console) $(mtdparts) root=/dev/ram rw; bootm ${lo
adaddr}'
root@OpenWrt:/# mkdir /sda1 && mount /dev/sda1 /sda1
NTFS signature is missing.
Failed to mount '/dev/sda1': Invalid argument
The device '/dev/sda1' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?

BusyBox v1.23.2 (2015-09-09 11:08:31 BST) built-in shell (ash)

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 CHAOS CALMER (Bleeding Edge, unknown)
 -----------------------------------------------------
  * 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:/# ls
bin      etc      mnt      proc     root     sda1     tmp      var
dev      lib      overlay  rom      sbin     sys      usr      www
root@OpenWrt:/# mount -t ext2 /dev/sda1 /sda1
root@OpenWrt:/# cd sda1
root@OpenWrt:/sda1# ubiformat /dev/mtd3
ubiformat: mtd3 (nand), size 27262976 bytes (26.0 MiB), 208 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 207 -- 100 % complete
ubiformat: 43 eraseblocks are supposedly empty
ubiformat: warning!: 165 of 208 eraseblocks contain non-UBI data
ubiformat: continue? (y/N) N
root@OpenWrt:/sda1#


 === IMPORTANT ============================
  Use 'passwd' to set your login password
  this will disable telnet and enable SSH
 ------------------------------------------


BusyBox v1.23.2 (2015-09-09 11:08:31 BST) built-in shell (ash)

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 CHAOS CALMER (Bleeding Edge, unknown)
 -----------------------------------------------------
  * 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:/# mount -t ext2 /dev/sda1 /sda1
root@OpenWrt:/# cd /sda1
root@OpenWrt:/sda1# ls -l
drwx------    2 root     root         12288 Nov  1  2015 lost+found
-rw-r--r--    1 root     root       5505024 Sep 14  2015 openwrt-15.05-kirkwood-ea4500-rootfs.ubi
-rw-r--r--    1 root     root       1591838 Sep 14  2015 openwrt-15.05-kirkwood-ea4500-uImage
-rw-r--r--    1 root     root       3505278 Oct 31  2015 uImage
root@OpenWrt:/sda1# ubiformat /dev/mtd3
ubiformat: mtd3 (nand), size 27262976 bytes (26.0 MiB), 208 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 207 -- 100 % complete
ubiformat: 43 eraseblocks are supposedly empty
ubiformat: warning!: 165 of 208 eraseblocks contain non-UBI data
ubiformat: continue? (y/N) y
ubiformat: warning!: only 0 of 208 eraseblocks have valid erase counter
ubiformat: erase counter 0 will be used for all eraseblocks
ubiformat: note, arbitrary erase counter value may be specified using -e option
ubiformat: continue? (y/N) y
ubiformat: use erase counter 0 for all eraseblocks
ubiformat: formatting eraseblock 207 -- 100 % complete
ubiformat: mtd3 (nand), size 27262976 bytes (26.0 MiB), 208 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 207 -- 100 % complete
ubiformat: 208 eraseblocks have valid erase counter, mean value is 0
root@OpenWrt:/sda1# ubiformat /dev/mtd3 -f openwrt-15.05-kirkwood-ea4500-rootfs.ubi
ubiformat: mtd3 (nand), size 27262976 bytes (26.0 MiB), 208 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 207 -- 100 % complete
ubiformat: 208 eraseblocks have valid erase counter, mean value is 0
ubiformat: flashing eraseblock 41 -- 100 % complete
ubiformat: formatting eraseblock 207 -- 100 % complete
root@OpenWrt:/sda1#
root@OpenWrt:/sda1#
root@OpenWrt:/sda1# mtd erase kernel
Could not open mtd device: kernel
Could not open mtd device: kernel
root@OpenWrt:/sda1# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00080000 00020000 "u-boot"
mtd1: 00020000 00020000 "u_env"
mtd2: 00020000 00020000 "s_env"
mtd3: 01a00000 00020000 "kernel1"
mtd4: 01760000 00020000 "rootfs1"
mtd5: 01a00000 00020000 "kernel2"
mtd6: 01760000 00020000 "ubi"
mtd7: 04a00000 00020000 "syscfg"
root@OpenWrt:/sda1# mtd erase kernel1
Unlocking kernel1 ...
Erasing kernel1 ...
root@OpenWrt:/sda1# mtd write openwrt-15.05-kirkwood-ea4500-uImage kernel1
Unlocking kernel1 ...

Writing from openwrt-15.05-kirkwood-ea4500-uImage to kernel1 ...
root@OpenWrt:/sda1# fw_setenv owrt_usb 'usb start; sleep 5;ext2load usb 0:1 ${loadaddr} /uImage; setenv bootargs $(console)
root=/dev/ram rw; bootm ${loadaddr}'
root@OpenWrt:/sda1# fw_setenv owrt_boot 'nand read.e ${loadaddr} 0x200000 0x200000; setenv bootargs $(console) ubi.mtd=3 roo
t=ubi0:rootfs rootfstype=ubifs rw; bootm ${loadaddr}'
root@OpenWrt:/sda1# fw_setenv auto_recovery no
root@OpenWrt:/sda1# cd /
root@OpenWrt:/# umount /sda1
root@OpenWrt:/sda1# reboot


login as: root


BusyBox v1.23.2 (2015-09-25 23:29:19 CEST) built-in shell (ash)

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 DESIGNATED DRIVER (Bleeding Edge, r47048)
 -----------------------------------------------------
  * 2 oz. Orange Juice         Combine all juices in a
  * 2 oz. Pineapple Juice      tall glass filled with
  * 2 oz. Grapefruit Juice     ice, stir well.
  * 2 oz. Cranberry Juice
 -----------------------------------------------------
root@OpenWrt:~# mkdir /sda1 && mount /dev/sda1 /sda1
root@OpenWrt:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00080000 00020000 "u-boot"
mtd1: 00020000 00020000 "u-boot environment"
mtd2: 00200000 00020000 "kernel"
mtd3: 01c00000 00020000 "root"
root@OpenWrt:~# ubiformat /dev/mtd3
ubiformat: mtd3 (nand), size 29360128 bytes (28.0 MiB), 224 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 223 -- 100 % complete
ubiformat: 11 eraseblocks have valid erase counter, mean value is 1
ubiformat: 192 eraseblocks are supposedly empty
ubiformat: warning!: 21 of 224 eraseblocks contain non-UBI data
ubiformat: continue? (y/N) y
ubiformat: warning!: only 11 of 224 eraseblocks have valid erase counter
ubiformat: erase counter 0 will be used for all eraseblocks
ubiformat: note, arbitrary erase counter value may be specified using -e option
ubiformat: continue? (y/N) y
ubiformat: use erase counter 0 for all eraseblocks
ubiformat: formatting eraseblock 223 -- 100 % complete
root@OpenWrt:~# cd /sda1
root@OpenWrt:/sda1# ubiformat /dev/mtd3 -f openwrt-15.05-kirkwood-ea4500-rootfs.
ubi
ubiformat: mtd3 (nand), size 29360128 bytes (28.0 MiB), 224 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 223 -- 100 % complete
ubiformat: 224 eraseblocks have valid erase counter, mean value is 0
ubiformat: flashing eraseblock 41 -- 100 % complete
ubiformat: formatting eraseblock 223 -- 100 % complete
root@OpenWrt:/sda1# mtd erase kernel
Unlocking kernel ...
Erasing kernel ...
root@OpenWrt:/sda1# mtd write openwrt-15.05-kirkwood-ea4500-uImage kernel
Unlocking kernel ...

Writing from openwrt-15.05-kirkwood-ea4500-uImage to kernel ...
root@OpenWrt:/sda1# fw_setenv bootcmd 'run owrt_usb; run owrt_boot'
root@OpenWrt:/sda1# fw_setenv owrt_usb 'usb start; sleep 5;ext2load usb 0:1 ${loadaddr} /uImage; setenv bootargs $(console) root=/dev/ram rw; bootm ${loadaddr}'
root@OpenWrt:/sda1# fw_setenv owrt_boot 'nand read.e ${loadaddr} 0x200000 0x200000; setenv bootargs $(console) ubi.mtd=3 root=ubi0:rootfs rootfstype=ubifs rw; bootm ${loadaddr}'
root@OpenWrt:/sda1# fw_setenv auto_recovery no
root@OpenWrt:~# cd /
root@OpenWrt:/# umount /sda1
root@OpenWrt:/# reboot
root@OpenWrt:/#
TRIED LUCI ,connection refused.....then changed password and reboot

BusyBox v1.23.2 (2015-09-25 23:29:19 CEST) built-in shell (ash)

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 DESIGNATED DRIVER (Bleeding Edge, r47048)
 -----------------------------------------------------
  * 2 oz. Orange Juice         Combine all juices in a
  * 2 oz. Pineapple Juice      tall glass filled with
  * 2 oz. Grapefruit Juice     ice, stir well.
  * 2 oz. Cranberry Juice
 -----------------------------------------------------
root@OpenWrt:~#
root@OpenWrt:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00080000 00020000 "u-boot"
mtd1: 00020000 00020000 "u-boot environment"
mtd2: 00200000 00020000 "kernel"
mtd3: 01c00000 00020000 "root"
root@OpenWrt:~# passwd
Changing password for root
New password:
Bad password: too weak
Retype password:
Password for root changed by root
login as: root
root@192.168.1.1's password:


BusyBox v1.23.2 (2015-07-24 20:06:02 CEST) built-in shell (ash)

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 CHAOS CALMER (15.05, r46767)
 -----------------------------------------------------
  * 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:~#
root@OpenWrt:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00080000 00020000 "u-boot"
mtd1: 00020000 00020000 "u-boot environment"
mtd2: 00200000 00020000 "kernel"
mtd3: 01c00000 00020000 "root"
root@OpenWrt:~# df
Filesystem           1K-blocks      Used Available Use% Mounted on
rootfs                   21684      3416     18268  16% /
ubi0:rootfs              21684      3416     18268  16% /
tmpfs                    62720       524     62196   1% /tmp
tmpfs                      512         0       512   0% /dev
root@OpenWrt:~# df -h
Filesystem                Size      Used Available Use% Mounted on
rootfs                   21.2M      3.3M     17.8M  16% /
ubi0:rootfs              21.2M      3.3M     17.8M  16% /
tmpfs                    61.3M    524.0K     60.7M   1% /tmp
tmpfs                   512.0K         0    512.0K   0% /dev
root@OpenWrt:~# free
             total         used         free       shared      buffers
Mem:        125440        19896       105544          524            0
-/+ buffers:              19896       105544
Swap:            0            0            0


I got a new EA4500 (at a ridiculous cheap price) and I decided to keep stock firmware for now for some tests.
The previous had the same exact stock version which is 2.1.42.162351
I have both configured with Wifi 5Ghz and both are working fine.
The setup is:
CISCO 1 (OpenWrt) : ch 36 (5.180 GHz) Tx-Power 10dBm ch width 40MHz
CISCO 2 (Stock): ch  44 (5.220 GHz) Tx-Power ? ch width 40MHz

note:  I have nobody else in 5GHz.  2.4GHz is crowded.

let me know how you are testing Throughput so i can try to reproduce

Joni,

Am I right that your method above would let me get from my current Trunk image to a working STABLE image ?

I have posted my question here :- https://forum.openwrt.org/viewtopic.php?id=61667

Many Thanks for your efforts !

Drew

Hi Drew,

If you are already running openwrt, you should use the sysupgrade images.
Problem is that the stable image (Chaos Calmer) is an UBIFS instead of SQUASHFS ( UBIFS should be the best to use for this router who uses NAND flash) and i don't know the upgrade procedure for that (to go from Designated Driver trunk SquashFS to Chaos Calmer Stable UBIFS). Also don't forget that this is a downgrade since you are trying to go from an higher version (Designated driver) which now has full support for EA4500 to a lower (Chaos Calmer) that does not totally support this router (main issues are with unsupported wifi chipsets). I'm currently running the chaos calmer stable (UbiFS) and the only problem i have (considering I don't care about wireless) is that every time I reboot the router either from command line or from the GUI, it crashes and requires an power off/on to boot again.
the OpenWrt page for this router  (https://wiki.openwrt.org/toh/linksys/ea4500) mentions the steps to build the trunk and i would like to build an image but with UBIFS format, but the build system is something that I did not install yet and i also don't have enough linux skills to do it. For now i guess I will wait for the Designated Driver Stable version to come out since like yourself i would like to install Packages. I read somewhere that you can safely ignore the dependency errors somehow and have the packages installed, maybe you should investigate this.
If you can , please test the reboot on that Designated Driver trunk you are running (run reboot at the command line) and let me know if it works).

Joni,

Will test the reboot tonight, but from what I recall it does indeed work.

So my problem still seems to be how do I get packages to apply on my build - maybe running the versions I am would be better than the "downgraded" STABLE one.

Regards,

Drew.

joni wrote:

Problem is that the stable image (Chaos Calmer) is an UBIFS instead of SQUASHFS ( UBIFS should be the best to use for this router who uses NAND flash)

The squashfs image for NAND is squashfs on an UBI block volume, so it's appropriate for use on NAND. UBI takes care of bad blocks, wear leveling, etc.

The read/write overlay is UBIFS. This seems to be the preferred setup for OpenWrt on NAND these days.

Also don't forget that this is a downgrade since you are trying to go from an higher version (Designated driver) which now has full support for EA4500 to a lower (Chaos Calmer) that does not totally support this router (main issues are with unsupported wifi chipsets).

There are some differences between the mwl8k driver in the two versions, but they appear to be minor. The firmware provided with both is identical. Are you seeing distinct and reproducible differences in performance?

Also, it should be straightforward to backport the patches that added full support for DD to CC. That would give you easily flashable images for the old version.

leitec,

You sound like you know your stuff (unlike me) I am currently building a new image from source to attempt and upgrade !

is there any reason a flushable version for the EA4500 is not provided, or is it just a case no one built one as the more experienced people know what they are doing and theres no need for one ?

Drew.

There's definitely a flashable snapshot for DD:

https://downloads.openwrt.org/snapshots … d/generic/

"linksys-viper" is the EA4500/E4200v2. The code to build that image wasn't there yet for CC.

(Last edited by leitec on 21 Dec 2015, 18:48)

leitec,

If I apply the latest sysupdate file do you think I might then be able to install the openvpn package ?

The error I am trying to overcome is :- http://imgur.com/L6aDOPo

My current build is :- OpenWrt Designated Driver r47197 / LuCI squashfs Branch (git-15.310.28416-524c918)

Drew.

Yes, it should install. The packages and images in the snapshot directory are built daily. There are enough changes on a regular basis to break package installs after some time. You can install everything right when you upgrade, or build an image from source that already includes the packages you need.

Edit: that image you're running now might be old enough that you should flash the factory firmware first, then flash with https://downloads.openwrt.org/snapshots … actory.bin . The board name changed from ea4500 to linksys-viper, which will prevent sysupgrade from accepting the .tar image.

(Last edited by leitec on 21 Dec 2015, 19:20)

Ah i didnt think you could actually flash a factory file on to an already installed openwrt ?

Drew

If you're running something from my old Github repo or DD snapshot it will work. I've tested it several times with the original FW_<whatever>.SSA images. I don't think the Candyhouse OpenWrt supported sysupgrade at all, though.