Beta Asuswrt-Merlin 386.1 Beta (stage 2) is now available

[L&LD]

Small update to my post here: https://www.snbforums.com/threads/a...ta-stage-2-is-now-available.69116/post-649912

All RT-AC86U's (that failed to upgrade last time) have been successfully upgraded with 386.1 Beta 4b.

The customer did get back to me and his RT-AC66_B1 upgraded successfully too.

The two other RT-AC66U_B1's still won't allow an upgrade to Beta 4. On one, I tried at least 10 times but still got the same message as last time. All three of these 'B1 routers were on RMerlin 386.1 Beta 3 without issues. Maybe tomorrow I may have a chance to try again fresh.

To comply with regulatory amendments, we have modified our certification rule to ensure better firmware quality. This version is not compatible with all previously released ASUS firmware and uncertified third party firmware. Please check our official websites for the certified firmware.

 

[maxbraketorque]

I just updated my AC86U that is operating in AP mode. As others have shown EEE went from being enabled on 384.19 to being disabled under 386.1b4b. CPU temperature went from 62C to 66C, so a very mild increase. Room temperature is about 23C. I guess I'll try my main router shortly.

 

[Krism]

Upgraded my devices too, these are my findings:
AC5300 AIMesh node: no issues so far
AX86u: upgrade was smooth, first didn't see my aimesh node but after rebooting the node it appeared again.

Everything seems to work fine except the wifi guest network without intranet access. Now the log isn't flooded with errors anymore, now the iprange of the guest wifi is the same as the internal ip range and thus the guest wifi can access everything on the intranet. And yes, 'Access Intranet' is OFF.
Strange thing is that it is only the 2.4ghz band showing this behavior. When on the 5Ghz band an ipaddress completely different from the internal iprange is distributed, which is the expected behavior

 

[Kees17760]

I had a little more luck with it.
I experienced the same hang when the setting was first enabled, but that lasted about 10 seconds, and the terminal was then responsive again without needing to reconnect. My PC was directly connected to the router when I made that change.

My temps immediately dropped 4 degrees, and I haven't noticed any other ill-effects so far.
The setting was apparently enabled by default on 384.19 according to this:

Beta - Asuswrt-Merlin 386.1 Beta (stage 2) is now available

Confirmed here, too, on my AX88U. I'm glad a workaround could be found, since both of the two AX88U's I've updated are refusing to go back to b3 and I'm quite reluctant to reset them. Also resolved (Intel ethernet & Intel wireless) on my AX88U, with Beta4, after withdrawing from the Trend...

www.snbforums.com

It is enabled on 384.19.

 

[maxbraketorque]

Just finished upgrading my AC86U main router. My AC86U AP took the upgrade without a hitch, but my main router did not want to present the webui after the upgrade, soft reboots via ssh didn't fix the issue, but a manual power cycle took care of it. The modified main webui interface is only slightly changed but feels noticeably cleaner. Its only been running for about 30 minutes, but so far, everything appears to be working.

CPU temperature went from 75C with 384.19 to 80-81C with 386.1b4b. EEE went from enabled to disabled.

 

[Kees17760]

For the 86U, yes and no. In a terminal I've enabled EEE but the terminal would hang. After closing the terminal and reconnecting, I can see EEE enabled, but it had no effect on temps. I've put it into a script on boot and the boot was massively irregular. So, my conclusion is DO NOT DO THIS.
Also, on B4 (is there a B4b for the 86U--I'm on whatever is up now) the CPU wait fix doesn't work.
But I've put a fan on my 86U, which was 80C on .19 and 95C on B3, and it is at 60C on B4.

Are you sure you have the latest? I've read there's a beta 4b version out. It should be under test versions.

 

[Paul Smedley]

The two other RT-AC66U_B1's still won't allow an upgrade to Beta 4. On one, I tried at least 10 times but still got the same message as last time. All three of these 'B1 routers were on RMerlin 386.1 Beta 3 without issues. Maybe tomorrow I may have a chance to try again fresh.

Do you have AI Protection turned on? I disabled it and after that was able to flash beta 4 on my AC67U.

 

[cristobal07]

upgraded RT-AC88U to beta 4 - factory reset.

found out that IPv6 - tunnel 6in4 no longer accept
LAN IPv6 Prefix address from tunnel broker that ends with ::
randomly added one digit after ::, from xxx:xxx:xxxx:: to xxx:xxx:xxxx::0 did the trick.

Thanks Merlin.

 

[SubElement]

Okay, so running Beta 4 on the RT-AX86U. I actually did a firmware reset yesterday and set up my config again. Crashed and restarted this afternoon it seems. Here is a bit of the log before the restart at the end. Would love some insights as I have no idea...

Jan 11 15:48:37 RT-AX86U kernel: _blog_emit, blogp = 0x22a0
Jan 11 15:48:37 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:48:37 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:48:38 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:48:38 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:48:38 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:48:41 RT-AX86U kernel: CONSOLE: 059842.817 wl1: wlc_ampdu_recv_addba_resp: e0:2b:96:a6:4a:16: Failed. status 1 wsize 0 policy 0
Jan 11 15:48:51 RT-AX86U kernel: _blog_emit, blogp = 0x22e0
Jan 11 15:48:51 RT-AX86U kernel: _blog_emit, blogp = 0x22e0
Jan 11 15:49:41 RT-AX86U kernel: CONSOLE: 059902.544 wl1: wlc_ampdu_recv_addba_resp: e0:2b:96:a6:4a:16: Failed. status 1 wsize 0 policy 0
Jan 11 15:49:48 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:49:48 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:49:48 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:49:48 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:49:56 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:49:56 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:50:00 RT-AX86U kernel: _blog_emit, blogp = 0x22c0
Jan 11 15:50:00 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:50:14 RT-AX86U kernel: _blog_emit, blogp = 0x22a0
Jan 11 15:50:14 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:50:21 RT-AX86U kernel: _blog_emit, blogp = 0x22c0
Jan 11 15:50:21 RT-AX86U kernel: _blog_emit, blogp = 0x22c0
Jan 11 15:50:21 RT-AX86U kernel: _blog_emit, blogp = 0x22c0
Jan 11 15:50:41 RT-AX86U kernel: CONSOLE: 059962.267 wl1: wlc_ampdu_recv_addba_resp: e0:2b:96:a6:4a:16: Failed. status 1 wsize 0 policy 0
Jan 11 15:51:03 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:51:03 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:51:07 RT-AX86U kernel: _blog_emit, blogp = 0x22a0
Jan 11 15:51:07 RT-AX86U kernel: _blog_emit, blogp = 0x22a0
Jan 11 15:51:07 RT-AX86U kernel: _blog_emit, blogp = 0x22a0
Jan 11 15:51:10 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:51:10 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:51:41 RT-AX86U kernel: CONSOLE: 060022.010 wl1: wlc_ampdu_recv_addba_resp: e0:2b:96:a6:4a:16: Failed. status 1 wsize 0 policy 0
Jan 11 15:52:41 RT-AX86U kernel: CONSOLE: 060081.833 wl1: wlc_ampdu_recv_addba_resp: e0:2b:96:a6:4a:16: Failed. status 1 wsize 0 policy 0
Jan 11 15:53:09 RT-AX86U kernel: _blog_emit, blogp = 0x22c0
Jan 11 15:53:23 RT-AX86U kernel: _blog_emit, blogp = 0x22a0
Jan 11 15:53:41 RT-AX86U kernel: CONSOLE: 060141.564 wl1: wlc_ampdu_recv_addba_resp: e0:2b:96:a6:4a:16: Failed. status 1 wsize 0 policy 0
Jan 11 15:53:51 RT-AX86U kernel: _blog_emit, blogp = 0x22e0
Jan 11 15:53:51 RT-AX86U kernel: _blog_emit, blogp = 0x22e0
Jan 11 15:54:41 RT-AX86U kernel: CONSOLE: 060201.296 wl1: wlc_ampdu_recv_addba_resp: e0:2b:96:a6:4a:16: Failed. status 1 wsize 0 policy 0
Jan 11 15:54:52 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:54:56 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:55:14 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:55:14 RT-AX86U kernel: _blog_emit, blogp = 0x22c0
Jan 11 15:55:14 RT-AX86U kernel: _blog_emit, blogp = 0x22a0
Jan 11 15:55:14 RT-AX86U kernel: _blog_emit, blogp = 0x22a0
Jan 11 15:55:14 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:55:14 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:55:14 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:55:14 RT-AX86U kernel: _blog_emit, blogp = 0x22c0
Jan 11 15:55:14 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:55:19 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:55:19 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:55:19 RT-AX86U kernel: _blog_emit, blogp = 0x2260
May  5 13:05:07 syslogd started: BusyBox v1.25.1
May  5 13:05:07 kernel: klogd started: BusyBox v1.25.1 (2021-01-08 17:43:19 EST)

 

[isr25]

Okay, so running Beta 4 on the RT-AX86U. I actually did a firmware reset yesterday and set up my config again. Crashed and restarted this afternoon it seems. Here is a bit of the log before the restart at the end. Would love some insights as I have no idea...

Jan 11 15:48:37 RT-AX86U kernel: _blog_emit, blogp = 0x22a0
Jan 11 15:48:37 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:48:37 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:48:38 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:48:38 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:48:38 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:48:41 RT-AX86U kernel: CONSOLE: 059842.817 wl1: wlc_ampdu_recv_addba_resp: e0:2b:96:a6:4a:16: Failed. status 1 wsize 0 policy 0
Jan 11 15:48:51 RT-AX86U kernel: _blog_emit, blogp = 0x22e0
Jan 11 15:48:51 RT-AX86U kernel: _blog_emit, blogp = 0x22e0
Jan 11 15:49:41 RT-AX86U kernel: CONSOLE: 059902.544 wl1: wlc_ampdu_recv_addba_resp: e0:2b:96:a6:4a:16: Failed. status 1 wsize 0 policy 0
Jan 11 15:49:48 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:49:48 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:49:48 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:49:48 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:49:56 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:49:56 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:50:00 RT-AX86U kernel: _blog_emit, blogp = 0x22c0
Jan 11 15:50:00 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:50:14 RT-AX86U kernel: _blog_emit, blogp = 0x22a0
Jan 11 15:50:14 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:50:21 RT-AX86U kernel: _blog_emit, blogp = 0x22c0
Jan 11 15:50:21 RT-AX86U kernel: _blog_emit, blogp = 0x22c0
Jan 11 15:50:21 RT-AX86U kernel: _blog_emit, blogp = 0x22c0
Jan 11 15:50:41 RT-AX86U kernel: CONSOLE: 059962.267 wl1: wlc_ampdu_recv_addba_resp: e0:2b:96:a6:4a:16: Failed. status 1 wsize 0 policy 0
Jan 11 15:51:03 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:51:03 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:51:07 RT-AX86U kernel: _blog_emit, blogp = 0x22a0
Jan 11 15:51:07 RT-AX86U kernel: _blog_emit, blogp = 0x22a0
Jan 11 15:51:07 RT-AX86U kernel: _blog_emit, blogp = 0x22a0
Jan 11 15:51:10 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:51:10 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:51:41 RT-AX86U kernel: CONSOLE: 060022.010 wl1: wlc_ampdu_recv_addba_resp: e0:2b:96:a6:4a:16: Failed. status 1 wsize 0 policy 0
Jan 11 15:52:41 RT-AX86U kernel: CONSOLE: 060081.833 wl1: wlc_ampdu_recv_addba_resp: e0:2b:96:a6:4a:16: Failed. status 1 wsize 0 policy 0
Jan 11 15:53:09 RT-AX86U kernel: _blog_emit, blogp = 0x22c0
Jan 11 15:53:23 RT-AX86U kernel: _blog_emit, blogp = 0x22a0
Jan 11 15:53:41 RT-AX86U kernel: CONSOLE: 060141.564 wl1: wlc_ampdu_recv_addba_resp: e0:2b:96:a6:4a:16: Failed. status 1 wsize 0 policy 0
Jan 11 15:53:51 RT-AX86U kernel: _blog_emit, blogp = 0x22e0
Jan 11 15:53:51 RT-AX86U kernel: _blog_emit, blogp = 0x22e0
Jan 11 15:54:41 RT-AX86U kernel: CONSOLE: 060201.296 wl1: wlc_ampdu_recv_addba_resp: e0:2b:96:a6:4a:16: Failed. status 1 wsize 0 policy 0
Jan 11 15:54:52 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:54:56 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:55:14 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:55:14 RT-AX86U kernel: _blog_emit, blogp = 0x22c0
Jan 11 15:55:14 RT-AX86U kernel: _blog_emit, blogp = 0x22a0
Jan 11 15:55:14 RT-AX86U kernel: _blog_emit, blogp = 0x22a0
Jan 11 15:55:14 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:55:14 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:55:14 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:55:14 RT-AX86U kernel: _blog_emit, blogp = 0x22c0
Jan 11 15:55:14 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:55:19 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:55:19 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 11 15:55:19 RT-AX86U kernel: _blog_emit, blogp = 0x2260
May  5 13:05:07 syslogd started: BusyBox v1.25.1
May  5 13:05:07 kernel: klogd started: BusyBox v1.25.1 (2021-01-08 17:43:19 EST)

do you have scribe installed? I am only having this kernel alarm when scribe is installed and will disappear after it’s removed. It won’t reboot/crash my router though - or at least i didn’t leave it long enough to let it crash

 

[SubElement]

do you have scribe installed? I am only having this kernel alarm when scribe is installed and will disappear after it’s removed. It won’t reboot/crash my router though - or at least i didn’t leave it long enough to let it crash

I do, but I installed it to help diagnose this issue. It also happened yesterday prior to the firmware reset where scribe wasn't installed.

 

[fearz]

Hey,

How did you get the AC5300 386 branch from ?

 

[Dabombber]

It might be helpful to include this in the upgrade notes section of the first post.

  - NOTE: Some users upgrading might have to go through some
          database maintenance on first boot, which means the
          router might be slower or have a non-responsive webui
          for a while.
          This can take anywhere from 5 minutes up to an hour,
          depending on your model, just give it time to complete
          the process.

Other than that, no problems on 386.1_alpha4-gd4b7146753 that weren't self inflicted (annoyingly, it seems that "Mmm dd hh:mm:ss syslogd exiting" is a valid syslog message despite being inconsistent ).

 

[skeal]

I'm unable to get my AX88U DDNS by asuscomm.com to register. Even tried new names and still it fails to authorize. Anyone else or anyone have a trick to try?

 

[ExtremeFiretop]

I'm unable to get my AX88U DDNS by asuscomm.com to register. Even tried new names and still it fails to authorize. Anyone else or anyone have a trick to try?

Does it sign you out when you register or unregister? It does for me which indicates to me it worked successfully.
If it doesn't for you, I would recommend just a reboot after the register to double check.

Edit: The sign-out is only due to using HTTPS for the WebGUI, If you use unsecure HTTP then you likely won't have that symptom.

I seem to remember it didn't stick for me the first time after the upgrade (Until I rebooted after setting up DDNS)

 

[Smokey613]

It might be helpful to include this in the upgrade notes section of the first post.

  - NOTE: Some users upgrading might have to go through some
          database maintenance on first boot, which means the
          router might be slower or have a non-responsive webui
          for a while.
          This can take anywhere from 5 minutes up to an hour,
          depending on your model, just give it time to complete
          the process.

Other than that, no problems on 386.1_alpha4-gd4b7146753 that weren't self inflicted (annoyingly, it seems that "Mmm dd hh:mm:ss syslogd exiting" is a valid syslog message despite being inconsistent ).

I had the unable to login via web also after going to beta4b. Everything else seemed to be working. I just let it run and went to bed. I got up this morning and logged right in, no issues.

 

[boldie]

Not possible to upgrade from Beta3 to Beta4. using the correct file (RT-AC88U_386.1_beta4.trx). Redownload the file twice with same resultsView attachment 29255
Invailid firmware

Disabling AI Protection made it

 

[Slawek P]

So what are next steps for AX88U beta? Waiting for new Asus release?
I am on beta4 and reading posts it sounds I will might have an issue with the next upgrade, perhaps even requiring rescue tool.

 

[alex1236hk]

cpu wait in the new 386_41634 is still appear to be DISABLED.
Temp is still 10c higher then usual.
Since its closed source, any chance Asus did this on purpose or it's kind of mistake?

 

[ExtremeFiretop]

So what are next steps for AX88U beta? Waiting for new Asus release?
I am on beta4 and reading posts it sounds I will might have an issue with the next upgrade, perhaps even requiring rescue tool.

If your on the original Beta4 for AX88U, you might have issues yes; some people have had luck after a number of attempts to flash ontop of that version, but it always worked first shot with the rescue tool.
I would try and make my way to 4B if your on the original beta 4, just because throughput issue's are improved if you use AiProtection or QoS, and you'll be able to upgrade or downgrade freely again after flashing 4B.