What's new

Asuswrt-Merlin 376.49 is out

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

That's a 32 MB partition (30 MB, I suspect the missing 2 MB is allocated to nvram and boot).

So RMerlin, will folks with a /proc/mtd like this, who have installed your latest 49_6 "test/experimental" update, have problems with future updates of Asus (or Merlin) firmware...that will need a larger-than-32-megs CFE partition?

admin@unit3:/tmp/home/root# cat /proc/mtd

dev:__size_____erasesize_name
mtd0: 00080000 00020000 "boot"
mtd1: 00180000 00020000 "nvram"
mtd2: 03e00000 00020000 "linux"
mtd3: 03c676e8 00020000 "rootfs"
mtd4: 03ec0000 00020000 "brcmnand"
mtd5: 00140000 00020000 "asus"
 
Last edited:
So RMerlin, will folks with a /proc/mtd like this, who have installed your latest 49_6 "test/experimental" update, have problems with future updates of Asus (or Merlin) firmware...that will need a larger-than-32-megs CFE partition?

admin@unit3:/tmp/home/root# cat /proc/mtd

dev:__size_____erasesize_name
mtd0: 00080000 00020000 "boot"
mtd1: 00180000 00020000 "nvram"
mtd2: 03e00000 00020000 "linux"
mtd3: 03c676e8 00020000 "rootfs"
mtd4: 03ec0000 00020000 "brcmnand"
mtd5: 00140000 00020000 "asus"

What did you get if you run
strings /dev/mtd0 | grep bl_version
CFE should be updated aswell.
 
So RMerlin, will folks with a /proc/mtd like this, who have installed your latest 49_6 "test/experimental" update, have problems with future updates of Asus (or Merlin) firmware...that will need a larger-than-32-megs CFE partition?

No, that was the point of this release, to allow future updates from Asus to correctly apply.
 
Yepp, just tested to run 376.49_6_cfeupd and I can se larger linux but no CFE update.
After I returned to 376.49_5 and Linux is back to small size.
I did a nvram reset after but then still show old cfe1018EU.

I did not reconfigured by hand this time used my old config file, maby that was a mistake!

Octopus

I can't retest the whole process since my router was already updated a few weeks ago.

If the CFE update doesn't apply then this will have to wait for the next official release, as releasing back-versions such as this is quite time consuming.
 
I can't retest the whole process since my router was already updated a few weeks ago.

If the CFE update doesn't apply then this will have to wait for the next official release, as releasing back-versions such as this is quite time consuming.


Okey no problem that was just to inform about it. I have no hurry with that.
Taket it easy and I will wait for next relese.

I can test this and se if it's working.
The simpliest way is install original FW and the CFE will be merged with your current one but now with new rootfs size:
http://dlcdnet.asus.com/pub/ASUS/wireless/RT-AC68U/FW_RT_AC68U_30043763626.zip
After you can install your desired FW version again and all will be working like before but with new rootfs 64MB.

Regards
Octopus
 
Last edited:
Interesting. Asus RT-AC68P with cfe version 1.0.2.5:

Code:
admin@RT-AC68P-0980:/tmp/home/root# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00080000 00020000 "boot"
mtd1: 00180000 00020000 "nvram"
mtd2: 01e00000 00020000 "linux"
mtd3: 01c676ec 00020000 "rootfs"
mtd4: 05ec0000 00020000 "brcmnand"
mtd5: 00140000 00020000 "asus"
And from the web admin GUI, "General" -> "Tools" -> "Internal Storage":

Code:
NVRAM usage	40192 / 65536 bytes

Not sure how all this fits together?
 
Interesting. Asus RT-AC68P with cfe version 1.0.2.5:

Code:
admin@RT-AC68P-0980:/tmp/home/root# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00080000 00020000 "boot"
mtd1: 00180000 00020000 "nvram"
mtd2: 01e00000 00020000 "linux"
mtd3: 01c676ec 00020000 "rootfs"
mtd4: 05ec0000 00020000 "brcmnand"
mtd5: 00140000 00020000 "asus"
And from the web admin GUI, "General" -> "Tools" -> "Internal Storage":

Code:
NVRAM usage	40192 / 65536 bytes

Not sure how all this fits together?

You need both the updated bootloader and a firmware compiled with a rootfs size of 64 MB. That means FW 376_3626/ 376.49_6_cfeupd or newer.
 
does the 1.0.25 cfe work on ac68u? i have read conflicting things on this board. would there be any advantage to upgrading an ac68u to the 1.0.25 cfe if i've already upgraded to 1.0.20?
 
You need both the updated bootloader and a firmware compiled with a rootfs size of 64 MB. That means FW 376_3626/ 376.49_6_cfeupd or newer.

So, if I understand what you're saying here, I have the updated bootloader (cfe), but not firmware compiled with a rootfs size of 64MB? That sounds fine to me, and explains what I'm seeing (except the nvram usage of >32MB, which still has me wondering).

This does raise the question of whether, if I installed FW 376_3626/ 376.49_6_cfeupd, it would also install cfe version 1.0.2.1 on top of the version 1.0.2.5 cfe that I have now? I would hope that future firmware won't backdate the cfe?

Thanks.
 
Last edited:
Hi, I am currently on RT-AC68U_3.0.0.4_376.49_5, and if I want to update to RT-AC68U_3.0.0.4_376.49_6_cfeupd, is there anything special I need to do except standard firmware update through my router's GUI?

Sorry, I know it's moronic question, but I want to be sure I am not badly screwing up something.

Thanks in advance for your help, greatly appreciated.
 
Hi, I am currently on RT-AC68U_3.0.0.4_376.49_5, and if I want to update to RT-AC68U_3.0.0.4_376.49_6_cfeupd, is there anything special I need to do except standard firmware update through my router's GUI?

Sorry, I know it's moronic question, but I want to be sure I am not badly screwing up something.

Thanks in advance for your help, greatly appreciated.

From what i have read here it should be just like a standard firmware upgrade. I am sure a factory reset and nvram erase would also be a good idea.
 
RussellInCincinnati: [Am I good to go as long as I have been able to successfully install the 49_6 cfe update? Or might I still have problems?]
No, that was the point of this release, to allow future updates from Asus to correctly apply.

Thanks RMerlin for pounding us on the head enough times to finally get through to us. If we can install the 49_6 update that you were kind enough to post here at https://www.mediafire.com/folder/bkfq2a6aebq68/Asuswrt-Merlin#ftf9kjixr1a5f, then we are good to go for future, possibly larger bootloaders.

You have the patience of the Biblical Job.
 
From what i have read here it should be just like a standard firmware upgrade. I am sure a factory reset and nvram erase would also be a good idea.

Thanks for your help!

Two more questions:

1. If I perform factory reset, after the firmware update, can I load my configuration file I made with previous firmware to avoid setting everything from scratch, or is there something drastically different in this new firmware vs the old one?

2. How does one do nvram erase? I guess I'd have to use putty or some terminal, but I am not sure I am savvy enough for this task :(
 
Thanks for your help!

Two more questions:

1. If I perform factory reset, after the firmware update, can I load my configuration file I made with previous firmware to avoid setting everything from scratch, or is there something drastically different in this new firmware vs the old one?

2. How does one do nvram erase? I guess I'd have to use putty or some terminal, but I am not sure I am savvy enough for this task :(

Answered a million times on this forum. Sit back, relax and try the search function.
 
So, if I understand what you're saying here, I have the updated bootloader (cfe), but not firmware compiled with a rootfs size of 64MB? That sounds fine to me, and explains what I'm seeing (except the nvram usage of >32MB, which still has me wondering).

nvram is measured in bytes, not in kilobytes. So, you have 64 KB of nvram, like all recent Asus routers. The RT-N16 was the last one with only 32 KB of nvram.

This does raise the question of whether, if I installed FW 376_3626/ 376.49_6_cfeupd, it would also install cfe version 1.0.2.1 on top of the version 1.0.2.5 cfe that I have now? I would hope that future firmware won't backdate the cfe?

No, Broadcom's code is intelligent enough to only upgrade older bootloaders.
 
does the 1.0.25 cfe work on ac68u? i have read conflicting things on this board. would there be any advantage to upgrading an ac68u to the 1.0.25 cfe if i've already upgraded to 1.0.20?

Wrong thread, this has nothing to do with the 376.49 release.
 
Hi,

I have a RT-N66U. Since I updated to FW 376.49_5 I'm not able connect to my internal Teamspeak Server via my WAN-Domainname or WAN-IP. I forward port 9987 to internal 9987. For another aplication i forward external port 444 to internal 443 and everything is fine.
If I disable NAT Acceleration it works but my download speed drops to 100Mbit.
I have a 200Mbit cable connection and I want to use the full speed.
Do I have a possibility to use both, 200Mbit and the loopback?

Thanks Andy
 
Last edited:
nvram is measured in bytes, not in kilobytes. So, you have 64 KB of nvram, like all recent Asus routers. The RT-N16 was the last one with only 32 KB of nvram.

Oops, I was thinking KB, not MB...been typing MB too much lately. I meant that the admin GUI shows more than 32KB of nvram in use (40093 bytes), not more than 32MB.
 
Answered a million times on this forum. Sit back, relax and try the search function.

I can't find anything regarding my first question. Maybe because no one ever asked it in connection to this specific (newest) firmware and if loading settings from the old one would work.

Second one, I found couple of answers, but none of them was directly related to RT68U, so I am not sure if I am screwing up something by performing it. Therefore my question.
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top