where can i find an updated image with everything in it (Kaloz' one dates from the end of january). tx

the latest trunk snapshot is always at:
https://downloads.openwrt.org/snapshots … actory.img

NOTE HOWEVER, that the web gui won't be present and wireless may need to be set up; both these are MANUAL steps and you need to be comfortable with the command line.

You can flash the above image from stock linksys, then you'll need to follow the below instructions:
http://wiki.openwrt.org/doc/howto/luci.essentials

The pertinent points:

opkg update
opkg install luci-ssl

/etc/init.d/uhttpd start
/etc/init.d/uhttpd enable

Additionally, the following packages are needed for basic wireless configuration: libiw, libiwinfo, libiwinfo-lua.

Alternatively, if you're already running a recent lifehacksback/Kaloz/trunk build you can use the sysupgrade method.

Get:
https://downloads.openwrt.org/snapshots … pgrade.tar

onto your router (e.g. in /tmp), then use

sysupgrade -c openwrt-mvebu-armada-xp-mamba-squashfs-sysupgrade.tar

You'll then also need to perform the above luci/wireless steps.

I used the sysupgrade option to go from Kaloz's last (end Jan) build.  All settings are kept but you'll need to reinstall any additional packages beyond the bare minimum base set.

Currently been running for 1 hour 40 minutes everything OK

(Last edited by DavidMcWRT on 10 Feb 2015, 20:46)

Firmware Version        OpenWrt Chaos Calmer r44371 / LuCI (git-15.040.55811-ec1a869)
Kernel Version             3.18.6
Local Time                   Tue Feb 10 20:59:23 2015
Uptime                           8h 30m 53s

Running fast and furious, no degradation,  and Gufus's adblock script  works perfect.

Hows the wifi performance. Especially AC wifi?

So far so good. Constant 867mb with my work laptop.

Nice. I might give this a try. I've been sticking to MCWRT as its been really stable for me.. Been running for weeks without any issues.
Is the image available for download or you compiled it?

Downloaded Kaloz' Jan 28 snapshot, used sysupgrade today. Really good so far.

Since several of us have installed the r44371 CC trunk snapshot successfully (using sysupgrade) and have found it OK (known wireless issues aside), I've archived it as a "known good" build below.  Note there have been three reports of bricking using the full install image, so I've removed that and recommended people upgrade to Kaloz's Jan 28th image in the first instance.  Sorry if you were bitten

OpenWrt Chaos Calmer r44371
Feb 10 2015 Trunk snapshot for the Linksys WRT1900AC
kernel 3.18.6

(I've since moved to r44486; download links at bottom of this post)

Full image
removed after three different reports of brickings.
Please use Kaloz's Jan 28th full image image instead (which also has the Luci GUI rolled into it):
https://www.dropbox.com/s/9vs4ix536dwhy … t.img?dl=0
(*** [LEFT-]CLICK the link then download from the dropbox page. ***DO NOT*** right-click and do Save [Target] As ***)
7864320 bytes. md5sum: d094a6457f4e325c30a919902e8c6606
You can then use sysupgrade -c with the sysupgrade file below, but you'll then need to [re-]install the GUI.

Sysupgrade (needs Luci GUI added after installing):
https://www.dropbox.com/s/ik6psk95yj3s0 … e.tar?dl=0
3952640 bytes. md5sum: 171c8b918e375e7db19e50e36c34f71c
(*** [LEFT-]CLICK the link then download from the dropbox page. ***DO NOT*** right-click and do Save [Target] As ***)

Notes:

Either do a firmware upgrade from the linksys stock GUI using the full .img file, or perform a sysupgrade -c sysupgrade_file.tar from a previous trunk build.

Then to install the web administration GUI (Luci):

opkg update
opkg install luci-ssl

/etc/init.d/uhttpd start
/etc/init.d/uhttpd enable

[The OpenWRT Trunk setup page noted "Additionally, the following packages are needed for basic wireless configuration: libiw, libiwinfo, libiwinfo-lua."  However, it appears this may no longer be the case and WiFi may be ready to go without doing this.]

Performing a sysupgrade will keep your previous settings, but you'll need to (re-)install any previous packages you may have added or that were present in lifehacksback/Kaloz builds (the trunk snapshots are extremely minimal).

If you go down the flash the full firmware route you'll need to put all your settings in again as well as also installing additional packages.  Note, with this method flash back to Linksys stock firmware first, and/or DO NOT "keep settings" or load old settings.

If you're coming from a previous lifehacksback/Kaloz image you may need to change the package URL paths to:

http://downloads.openwrt.org/snapshots/ … /packages/<whatever>

(to do this: either log in via the GUI and modify the entries in the textbox in System -> Software -> Configuration, or else using the command line ssh into the router and then edit /etc/opkg.conf )

(do this before performing a sysupgrade).

The sensors command available in previous Kaloz images is not present, although the fan control scripts are.  You can find out the temps manually by running:

cut -c1-2 /sys/class/hwmon/hwmon2/temp1_input
cut -c1-2 /sys/class/hwmon/hwmon1/temp1_input
cut -c1-2 /sys/class/hwmon/hwmon1/temp2_input

(cpu, ddr and wifi respectively)

There was one report of not being able to ssh in to the router, possibly due to a blank password being set; try telnet instead if you encounter this issue.

As with all CC/Trunk builds using the Dec 2014 Marvell wireless driver, you may encounter some issues with Apple clients on Wifi.  Setting:

uci set wireless.@wifi-iface[0].disassoc_low_ack=0
uci set wireless.@wifi-iface[1].disassoc_low_ack=0
uci commit
wifi

can help with one particular issue, but Apple wireless generally is still poor.

In the case of the router becoming 'bricked':

Try this at first:
https://github.com/Chadster766/McWRT/wi … s-firmware

Or if it's more severe, more extreme measures might be needed:
https://github.com/Chadster766/McWRT/wi … r-recovery

There has since been one report of a router bricking when using the full install .img and going from McWRT back to stock and then to this snapshot.

A second report of bricking has now come in when a full Kaloz Jan 28 image was updated to the full mvebu Feb 9 build (the previous day's snapshot) without keeping settings, although the same procedure had been performed on a second router from the Feb 8 snapshot without issue.

Third bricking report:
1. USB to TTL - updated both images to Linksys original
2. Booted original Linksys
3. Installed openwrt-mvebu-armada-xp-mamba-squashfs-factory.img 10-Feb-2015 08:21             5898240
4. After about 10 seconds of booting process - kernel panic
system upgrade from any previous version works perfect.

No reports of problems so far from those who have used the sysupgrade method; I've now removed the full install image and recommended people go to Kaloz's Jan 28th build first and then sysupgrade to the Feb 10th snapshot.

Finally, for those wondering about whether there might be some newer features/bugfixes available since this snapshot, if you periodically check:
https://dev.openwrt.org/timeline?changeset=on
you can see what changes have been committed recently (and thereby since r44371).

Furthermore,

opkg update
opkg list-upgradable|egrep -v "Using latest"

will tell you of any newer packages available.

UPDATE: I'm now running r44486 (Feb 18 trunk snapshot)

sysupgrade file:
https://www.dropbox.com/s/luaxju6q0cym7 … e.tar?dl=0
(*** [LEFT-]CLICK the link then download from the dropbox page. ***DO NOT*** right-click and do Save [Target] As ***)
3952640 bytes. md5sum: 6824e4f711b99bcae480b6c911d93475

full img file (***I HAVE NOT TRIED/TESTED THIS!***):
https://www.dropbox.com/s/qn02jr8ect2f5 … y.img?dl=0
(*** [LEFT-]CLICK the link then download from the dropbox page. ***DO NOT*** right-click and do Save [Target] As ***)
5898240 bytes. md5sum: 00e037174c40dcadf42c93fcdd1467f0

a reminder that you'll need to ssh in and do:

opkg update
opkg install luci-ssl

/etc/init.d/uhttpd start
/etc/init.d/uhttpd enable

to get the web management (gui) working.

(Last edited by DavidMcWRT on 19 Feb 2015, 00:48)

I think 867mb is the connection status, right? If you use iperf to test, what's your speed?

@DavidMcWRT Am I correct to understand though the trunk has changed we are still using the same underlying wireless driver, that was giving people the issues on the CC builds? I know I could run the CC builds on WiFi for more than 8 hours sometimes, but I could not keep WiFi up and running without having to power cycle the router, every 8-10 hours. I did revert back to the Linksys stock firmware, been up and running on it for 15 days have not a single drop on wifi, even with a range extender added to get the far reaches of the dead space in my house.

So I guess my question is, has the wireless driver been updated or has there been was around the issues we were seeing?

Thanks

@DavidMcWRT

I only had to install luci, everything else was good to go.

Unfortunately you are correct - this still contains the Dec 2014 Marvell wireless driver that has some issues, primarily with Apple clients.

Thanks for the confirmation - I've now de-emphasised the wireless set-up instructions even further, but I'm keeping them in for now as they were part of the OpenWRT Trunk installation set up instructions.

Ok, at least I have not missed something.... But I don't have any Apple clients in my house, all PC and Android devices. And still the WiFi was still unreliable. But now that I think about, that was before I installed the range extender to reach that dead zones in my house. Now my WiFi signal is much better in that area. I have this section in my home, not sure what is in the walls, but it kills the WiFi signal, anyway I digress. I wonder if I should give a CC version a whirl again, just have to decide which one to try..

Hmmmm something to think about... I just hope Marvell does update or shares a newer version of the driver... Or these wonderful developers find a way to assist to "fix", i.e. workaround what ever we want to call it.

Thanks again

I will quote myself. i dont know why i did but i did. This build has bricked my router.

i feel like cursing to my self so bad. Everything was going so good for me. Anyways, i was running MCWRT. Flashed to stock linyksys without keeping settings. Stock flash was fine.
I proceeded with flashing the full image from the link above and now the router wont boot up. The power light stays solid, i get lan leds up for devices that are connected but the router doesnt seem to proceed any further, no ips are given to devices and no wan.
I've tried to boot from the secondary flash but the reset button doesnt do anything anymore, holding it even for infinity doesnt reset the router. So i think because of that i cant seem to trigger a boot from the secondary flash by using the 3 power off cycle thing.

I've never had a bricked router before. I've also tred various images out there for this router but never had an issue like this.
Is this a sign of a bricked router?

Any ideas?

Sorry to hear that

Others have managed restore using a cable and this method:
https://github.com/Chadster766/McWRT/wi … r-recovery

Can someone confirm a bricked state? Some places say orange blinking light?
mine blinks for like 3 sec at power on and then stays solid.

I've noted your scenario (mcwrt -> stock -> snapshot img) in the post.

I wonder, since there are two firmware areas, and people have reported that when flashing betwen OpenWRT and stock and OpenWRT that somehow some settings have been preserved, as to whether in your situation what has happened is that it might still have picked up your old McWRT settings??

That said, many of us went from McWRT to stock to lifehacksback a month or so ago without problems.

EDIT:

For my own sanity I just triple-checked the md5sums of the files on my dropbox, and they match the files on my machine that I downloaded from openwrt.  I'd done this before posting the instructions but just wanted to test once again to make doubly sure.

It occured to me that you might have done a right-click "save [target] as" on the links, which would have instead download the dropbox html page for the download.  I have therefore added a caution note underneath the links.

For reference, md5sums are:

e828d7f0b6fe7ca1b5f1c7d66734163f  openwrt-mvebu-armada-xp-mamba-squashfs-factory.img (5898240 bytes)
171c8b918e375e7db19e50e36c34f71c  openwrt-mvebu-armada-xp-mamba-squashfs-sysupgrade.tar (3952640 bytes)

(Last edited by DavidMcWRT on 11 Feb 2015, 02:18)

I had first tried a right click save us but i had picked up on the .html download therefore i had correctly downloaded the .img
I checked the md5sum of the file that i downloaded and it matches yours

e828d7f0b6fe7ca1b5f1c7d66734163f

Also i had also gone from stock to lifehack to mcwrt and between those several times in the past with no issue.

One question though. I went from MCWRT to stock and now tried to flash the CC( which caused the brick), theoretically which image is supposed to be in my secondary flash anyways?

Finally ,So a solid white power light means bricked then?

Well it was a theory, and at least it's now there as a caution in case others make that mistake.

stock I would hope.

Don't know myself.  Others who have been through de-bricking scenarios could probably give more precise information.

(Last edited by DavidMcWRT on 11 Feb 2015, 02:38)

Try switching manually to the alternate image:
https://github.com/Chadster766/McWRT/wi … s-firmware

Purchasing an USB to TTL cable should allow you to recover the router.

(Last edited by Chadster766 on 11 Feb 2015, 02:50)

I also managed to brick my 1900AC last night.  The symptoms are the same, but how I got there is different....

I went from the full Kaloz Jan 28 image to the full mvebu Feb 9 build without keeping settings and it never came up.

The weird thing is that I did the exact same thing successfully the day before with my second 1900AC (Kaloz -> mvebu Feb 8 r44257).

Can it be something with the full Feb 9/10 builds?  I can try the sys upgrade on my working unit if anyone thinks it would help.

Will order the usb to ttl cable tomorrow but it won't arrive until next week....

Cheers

I had already tried that as mentioned in the thread above. But the fact the the reset button doesnt seem to be resetting the router, i think its not able to trigger a boot from the secondary flash. Cable was ordered from ebay several days ago, however will probably take another two weeks most likely...Op top of that i hope it will work.

(Last edited by alirz on 11 Feb 2015, 03:02)

Thanks for adding your own report/experience.

Could be, but unless someone with time, patience and a ttl cable for backup has a chance to go through all the different scenarios I guess we'll never know for sure given the few numbers of success/failures that have been reported.

(I've added your report as another bricking scenario to the original post - thanks.)

(Last edited by DavidMcWRT on 11 Feb 2015, 03:16)

Just did sysupgrade from Kaloz Jan 28 to Trunk Feb 10.  OpenWrt Chaos Calmer r44371

All appears to be well.