Beta Asuswrt-Merlin 388.1 Beta is available for select models

[DJBeat]

Try wired connec
The AXE16000 found the XT12 via LAN cable and set it up

The AXE16000 found the XT12 via LAN cable and set it up

in the firmware AXE16000 under backhaul connection priority set to "5GHz-2 WIfi first", LAN cable removed, now the blue LED on the XT12 is flashing - it has a mesh connection via 5GHz-2 , but it does not reinforce WiFi

Update:
I deactivated Smart Connect, now mesh seems to work, I will test it tomorrow with the 2nd XT 12

 

[bobstc]

Hello. If someone could point me in the right direction I would appreciate it.

I flashed (web gui) my GT-AXE16000 with 388 beta 2 from the stock 386 and things where great. I wanted to compare something, so stupidly I flashed (web gui) back to stock 386. Now I want to go back to 388 beta 2 and the update does not stick. The gui does its thing with no error but after reboot the previous firmware persists.

What I have done with no success:

1. Performed a rescue to stock 386 then gui to update to Merlin 388 beta 2 and beta 1. In this case stock 386 rescue works fine but giu update to 388 does not stick.
2. Performed a rescue to merlin 388 beta 1 and 2. With this method the router is successfully flashed but then sits in a boot loop.

In all my attempts I have also performed a nvram clear or reset using the wps button power combo prior to and after each update. My feeling is this is a corrupt bootloader or partition or something. I would not know where to start if that's the case.

Thanks. Pardon the long post and if I am posting in the wrong place.

I am running Merlin 386 latest right now.

Bob

 

[skeal]

Hello. If someone could point me in the right direction I would appreciate it.

I flashed (web gui) my GT-AXE16000 with 388 beta 2 from the stock 386 and things where great. I wanted to compare something, so stupidly I flashed (web gui) back to stock 386. Now I want to go back to 388 beta 2 and the update does not stick. The gui does its thing with no error but after reboot the previous firmware persists.

What I have done with no success:

1. Performed a rescue to stock 386 then gui to update to Merlin 388 beta 2 and beta 1. In this case stock 386 rescue works fine but giu update to 388 does not stick.
2. Performed a rescue to merlin 388 beta 1 and 2. With this method the router is successfully flashed but then sits in a boot loop.

In all my attempts I have also performed a nvram clear or reset using the wps button power combo prior to and after each update. My feeling is this is a corrupt bootloader or partition or something. I would not know where to start if that's the case.

Thanks. Pardon the long post and if I am posting in the wrong place.

I am running Merlin 386 latest right now.

Bob

I think maybe you should talk to @L&LD he's the best at this kind of thing. I tagged him so maybe if he has time he'll give you a hand.

 

[bobstc]

I think maybe you should talk to @L&LD he's the best at this kind of thing. I tagged him so maybe if he has time he'll give you a hand.

Great thank you for that!

 

[Slapdaddy]

Hello. If someone could point me in the right direction I would appreciate it.

I flashed (web gui) my GT-AXE16000 with 388 beta 2 from the stock 386 and things where great. I wanted to compare something, so stupidly I flashed (web gui) back to stock 386. Now I want to go back to 388 beta 2 and the update does not stick. The gui does its thing with no error but after reboot the previous firmware persists.

What I have done with no success:

1. Performed a rescue to stock 386 then gui to update to Merlin 388 beta 2 and beta 1. In this case stock 386 rescue works fine but giu update to 388 does not stick.
2. Performed a rescue to merlin 388 beta 1 and 2. With this method the router is successfully flashed but then sits in a boot loop.

In all my attempts I have also performed a nvram clear or reset using the wps button power combo prior to and after each update. My feeling is this is a corrupt bootloader or partition or something. I would not know where to start if that's the case.

Thanks. Pardon the long post and if I am posting in the wrong place.

I am running Merlin 386 latest right now.

Bob

You're the second person I've seen on here with this exact same problem, caused by a flash from 388 back to 386, which leaves me hesitant to flash any updates at all until it is resolved. Not sure if the flash is exposing bad memory blocks on the router or what. Have you verified the checksum of the firmware after downloading?

 

[bobstc]

Yes the checksums checkout. I'm doing great on Merlin 386 but I am worried about the future updates now.

 

[L&LD]

@bobstc, if you've verified you have flashed the correct 386.xx version and you have downloaded the correct version of 388.xx for your router (and the router still doesn't upgrade to the new firmware), then this is what I would do next.

• Test with another browser, or a browser in 'safe', 'incognito', or 'InPrivate' mode.
• Remove all cables and USB devices from the router.
• Reboot the router via the GUI (yes, via the WiFi, with no WAN or LAN cables connected). Does the upgrade work now?
• If not, pull the power from the router and the wall ac outlet. Leave the router 'on' but unplugged for at least a minute or two. After you have plugged in the power supply to the wall and the router, and the router has fully booted up, does the upgrade process work now?
• If not, perform a full reset via the GUI and make sure you check the 'Initialize all settings...' check box before you hit reset.
• After the router has rebooted, do a temporary setup (just so the router doesn't show the setup screen after a reboot again and you won't know if you did a reset or not, using this different method). Then, use the Reset Button to reset it again. If after the reset the setup screen doesn't come up, you did not do a reset properly using the Reset Button.
• Finally, do one more temporary setup, then use the WPS Button method (see link below), and be sure the router was really reset (by verifying it comes up with the setup screen when you try to log in after it has booted up).

[Wireless] ASUS router Hard Factory Reset | Official Support | ASUS Global


If you followed this sequence precisely, and the router still isn't accepting a properly downloaded, verified, and matched firmware for your model router, I would consider this a hardware issue of the affected router.

Even doing all the above, before I would attempt to return it (if the return window is on your side), I would wait for Beta 3 from RMerlin before giving up on the hardware.

Hope this helps a little.

 

[JT Strickland]

It appears the RT-AX3000 or AX58U V2 isn't supported, but isn't shown that way in the list.
I'm hoping it's because it will be added in the very near future?
If not, it may be helpful to edit the naughty list and show it so.
I know I would not have bought a non-supported router if I had known.

 

[bobstc]

@bobstc, if you've verified you have flashed the correct 386.xx version and you have downloaded the correct version of 388.xx for your router (and the router still doesn't upgrade to the new firmware), then this is what I would do next.

• Test with another browser, or a browser in 'safe', 'incognito', or 'InPrivate' mode.
• Remove all cables and USB devices from the router.
• Reboot the router via the GUI (yes, via the WiFi, with no WAN or LAN cables connected). Does the upgrade work now?
• If not, pull the power from the router and the wall ac outlet. Leave the router 'on' but unplugged for at least a minute or two. After you have plugged in the power supply to the wall and the router, and the router has fully booted up, does the upgrade process work now?
• If not, perform a full reset via the GUI and make sure you check the 'Initialize all settings...' check box before you hit reset.
• After the router has rebooted, do a temporary setup (just so the router doesn't show the setup screen after a reboot again and you won't know if you did a reset or not, using this different method). Then, use the Reset Button to reset it again. If after the reset the setup screen doesn't come up, you did not do a reset properly using the Reset Button.
• Finally, do one more temporary setup, then use the WPS Button method (see link below), and be sure the router was really reset (by verifying it comes up with the setup screen when you try to log in after it has booted up).

[Wireless] ASUS router Hard Factory Reset | Official Support | ASUS Global


If you followed this sequence precisely, and the router still isn't accepting a properly downloaded, verified, and matched firmware for your model router, I would consider this a hardware issue of the affected router.

Even doing all the above, before I would attempt to return it (if the return window is on your side), I would wait for Beta 3 from RMerlin before giving up on the hardware.

Hope this helps a little.

Thanks very much for your reply and help. I did a few of these steps already but some steps I did not know about. I will give it try. I will wait for b3 before sending the hardware away. Kind regards.

 

[shabbs]

I will wait for b3

Join us in the waiting room...

 

[ASSAD]

Thanks very much for your reply and help. I did a few of these steps already but some steps I did not know about. I will give it try. I will wait for b3 before sending the hardware away. Kind regards.

These problems it will takes a matter of time and they will be fixed sooner or later.

 

[tarzan2000]

dcd crashes are long-standing issue that Trend Micro seems to not care enough to fully address (there are many different causes for these dcd crashes). The issues have been there for years, and by now they are fully aware of their existence.

Yes, it seemed to me that there was no such error before upgrading from the extreme stable version.
Maybe I 'm wrong ?

In general, the router works as usual. Should I worry about something and turn off the Micro Trend?

Spoiler

Nov 20 09:46:55 kernel: potentially unexpected fatal signal 11.
Nov 20 09:46:55 kernel: CPU: 1 PID: 7172 Comm: dcd Tainted: P O 4.1.52 #2
Nov 20 09:46:55 kernel: Hardware name: Broadcom-v8A (DT)
Nov 20 09:46:55 kernel: task: ffffffc032636080 ti: ffffffc028c44000 task.ti: ffffffc028c44000
Nov 20 09:46:55 kernel: PC is at 0xf706739c
Nov 20 09:46:55 kernel: LR is at 0x1dce0
Nov 20 09:46:55 kernel: pc : [<00000000f706739c>] lr : [<000000000001dce0>] pstate: 40000010
Nov 20 09:46:55 kernel: sp : 00000000ff943308
Nov 20 09:46:55 kernel: x12: 00000000000a2050
Nov 20 09:46:55 kernel: x11: 00000000f62ff024 x10: 00000000000a2876
Nov 20 09:46:55 kernel: x9 : 0000000000000020 x8 : 00000000000a287c
Nov 20 09:46:55 kernel: x7 : 000000000000001d x6 : 00000000f62ffe64
Nov 20 09:46:55 kernel: x5 : 0000000000000000 x4 : 00000000f62ffe00
Nov 20 09:46:55 kernel: x3 : 0000000034362f34 x2 : 0000000000000000
Nov 20 09:46:55 kernel: x1 : 000000000007d72e x0 : 0000000000000000
Nov 20 09:51:52 kernel: potentially unexpected fatal signal 11.
Nov 20 09:51:52 kernel: CPU: 1 PID: 10555 Comm: dcd Tainted: P O 4.1.52 #2
Nov 20 09:51:52 kernel: Hardware name: Broadcom-v8A (DT)
Nov 20 09:51:52 kernel: task: ffffffc023987580 ti: ffffffc024ffc000 task.ti: ffffffc024ffc000
Nov 20 09:51:52 kernel: PC is at 0xf6ede39c
Nov 20 09:51:52 kernel: LR is at 0x1dce0
Nov 20 09:51:52 kernel: pc : [<00000000f6ede39c>] lr : [<000000000001dce0>] pstate: 40000010
Nov 20 09:51:52 kernel: sp : 00000000ffd04768
Nov 20 09:51:52 kernel: x12: 00000000000a2050
Nov 20 09:51:52 kernel: x11: 00000000f61ff024 x10: 00000000000a2876
Nov 20 09:51:52 kernel: x9 : 0000000000000020 x8 : 00000000000a287c
Nov 20 09:51:52 kernel: x7 : 000000000000001d x6 : 00000000f61ffe64
Nov 20 09:51:52 kernel: x5 : 0000000000000000 x4 : 00000000f61ffe00
Nov 20 09:51:52 kernel: x3 : 0000000034362f34 x2 : 0000000000000000
Nov 20 09:51:52 kernel: x1 : 000000000007d72e x0 : 0000000000000000

 

[RMerlin]

Should I worry about something and turn off the Micro Trend?

Just ignore them.

 

[Treadler]

An observation.

Using native dual stack, IPv4 & 6;

When Firewall > Basic Config > Enable IPv4 inbound firewall rules = Enabled (this is the default)
Then, an IPv6 port scan shows most ports as connection ‘refused’.

If Enable IPv4 inbound firewall rules = Disabled, then all ports are ‘Stealth’.

 

[Damit1]

Well, Im simple person.
No VPNs or whatever.
I think the most stable release for me was 386 5.2, and ever since it went buggier more and more.

7 days my router works in a raw.
For long time, the uptime was not that high (for months now, needed to reboot every 3-4 days)

I hope the small bugs would resolve on their own in B3 (although, they are not explained purely now).

Thank you, again @RMerlin

 

[violetenergy]

Hello , Little test of latest beta from 386.7_2.

I have 2xAX86U, with 388.1 Beta 2 , I have little issue with mesh , connection is ok but on WebGUI I have "great" connection but with red alert.

I can't manage my mesh node with this issue (test with led on/off for example). I rollback to previous and all is ok now.

I will retry when RC or final. Thank you for your amazing work.

 

[clweb]

hello,

Very stable build this 388.1 Beta 2. Over 8 days without problem on my AX58U.
I noticed also that the CPU load is lower than with 386.7_2. Now it is around 0.5 vs 1.4

Thank you RMerlin

 

[bartj12]

Hello , Little test of latest beta from 386.7_2.

I have 2xAX86U, with 388.1 Beta 2 , I have little issue with mesh , connection is ok but on WebGUI I have "great" connection but with red alert.

I can't manage my mesh node with this issue (test with led on/off for example). I rollback to previous and all is ok now.

I will retry when RC or final. Thank you for your amazing work.

I have almost the same setup, only a Ax86s as node. In my experience running the latest Merlin beta on the router and latest stock on the node (both 388) gives the best stability. You can give it a try if you want.

 

[ASSAD]

I have GT-AX11000 working on AP mode ONLY using the normal radio wireless that all bands are turned ON in Wireless - Professional tab and wps, smart connect are OFF, I am not using even AiMesh. I don't have problems that when i use the wireless and i will not complain, but i see error and other thing i want to report it for you RMerlin. Maybe it will interest you.

When i connect a device straight after that i see this in system log appear right away

The rest of the system log 1

When i turn OFF the wireless device i see this even right away

The rest of the system log 2

 

[ASSAD]

The continuing....

After that this will appear

The rest of system log 3

That's it.

The first system log 1 spamming for every (11min to 30min) random.

The second system log 2 random.

The third system log 3 spamming for every (52min to 44min to 48min) random.

This happens for every device i connect to the router, it means every device having that same errors what i mentioned above. I don't know if i am the only one having that errors here, but it's good to report it and the firmware on 388.1 b2.

Sorry for the confusing.

Thanks.