Release Asuswrt-Merlin 3004.388.5 is now available

[RMerlin]

. If you're running the beta, save your memory chip erase cycles.

If you stay on the beta, you will constantly get the notification that a newer version is available.

People shouldn't stay on beta versions when the final release is available.

 

[Lord_Vader]

Flash stock ASUS Firmware (newest), let it settle for 10 minutes, then flash RMerlin (let it settle 10 min.)

If that doesn't do it, use the ASUS Restoration Tool to flash RMerlin.

That's the way. Encountered the same issue myself a couple of times. Often flashing stock and go back to Merlin helps.

 

[B-dog66]

I have the same problem and the same router...
1. Nothing plugged into the usb ports.
2. unplugged the routner for 5 mins will boot into 3004.388.4
3. flash the router and I get the message to manually reboot the router
4. it comes back to 3004.388.4
5. I have cleared all the cache and rebooted my pc.


I have never had this problem before....

I had 3004.388.4, so far I have done the following:
1. Removed USB from GUI and unplugged after
2. Restart the router
3. When I tried to flash from my main PC, same issue
4. Took my wife MacBook, and it was smooth flashing from that point
5. Also, get the same message to manually reboot the router, after reboot it was flashed to 3004.388.5
6. It was a dirty flash, till now so far so good!
7. I need to check my main pc, what's wrong with it.

Thanks to everyone for the help, I'm new to ASUS and hopefully in the future I can help in future builds.

 

[jomcty]

After running 3004.388.4 for 102 days straight:

I performed a dirty upgrade to 3004.388.5. No apparent issues encountered thus far.

Thanks RMerlin! A donation is on its way!

 

[RMerlin]

I am still at 388.4, but when I try to retrieve the changelog for the new FW 388.5, the router returns a message "failed to find release notes". Is this the same problem that was found for FW 386.12?

There was a bug in 388.4 where it would try to retrieve the incorrect filename when fetching the changelog. The issue was fixed in 388.5, however that fix won't help getting the notification for people with the affected firmwares.

I've gone ahead and saved a second copy of the changelog using the incorrect filename, so in theory it should also appear for 388.4 users now. However I expect people to upgrade to 388.5, as I have no intention of doing the same duplicate changelog with future releases.
.

 

[Wisiwyg]

1.5 hr dirty upgrade... all's well.

 

[Thermaltake]

Can someone tell what this is in log I'm seeing this for the first time

Dec 3 12:30:12 kernel: CPU: 1 PID: 8838 Comm: dcd Tainted: P O 4.1.51 #2
Dec 3 12:30:12 kernel: Hardware name: Broadcom-v8A (DT)
Dec 3 12:30:12 kernel: task: ffffffc02962c180 ti: ffffffc0280ec000 task.ti: ffffffc0280ec000
Dec 3 12:30:12 kernel: PC is at 0x29d34
Dec 3 12:30:12 kernel: LR is at 0x29fb4
Dec 3 12:30:12 kernel: pc : [<0000000000029d34>] lr : [<0000000000029fb4>] pstate: 20070010
Dec 3 12:30:12 kernel: sp : 00000000ffacb840
Dec 3 12:30:12 kernel: x12: 00000000000a211c
Dec 3 12:30:12 kernel: x11: 0000000000081d64 x10: 0000000000000045
Dec 3 12:30:12 kernel: x9 : 0000000000000003 x8 : 0000000000000045
Dec 3 12:30:12 kernel: x7 : 00000000f5bfebf8 x6 : 0000000000000038
Dec 3 12:30:12 kernel: x5 : 00000000000003e8 x4 : 00000000f5bfec58
Dec 3 12:30:12 kernel: x3 : 0000000000000000 x2 : 0000000000000044
Dec 3 12:30:12 kernel: x1 : 000000000000000a x0 : 0000000000000000

 

[Zigster]

First attempt failed while upgrading from 3004.388.4_rog to 3004.388.5_rog on Asus GT-AXE1100 (actually it never happened to me before, that an upgrade failed) ... will try again later

 

[joegreat]

Dirty upgrade (from .4 version) on main router AX88U went OK - now testing...

Test results after first night:
- VPN - OK!
- No new/strange log entries
- All looks good to me!

 

[zakazak]

For me it could also not find the release notes when trying to upgrade from 3004.388.4.
The updated work fine now.

If I understand correctly, the bug should be fixed and when doing the next upgrade to 388.6 I should be able to find the changelog?
Besides... I am always checking your website for the changelog anyway

 

[Cleanev]

Can someone tell what this is in log I'm seeing this for the first time

Dec 3 12:30:12 kernel: CPU: 1 PID: 8838 Comm: dcd Tainted: P O 4.1.51 #2
Dec 3 12:30:12 kernel: Hardware name: Broadcom-v8A (DT)
Dec 3 12:30:12 kernel: task: ffffffc02962c180 ti: ffffffc0280ec000 task.ti: ffffffc0280ec000
Dec 3 12:30:12 kernel: PC is at 0x29d34
Dec 3 12:30:12 kernel: LR is at 0x29fb4
Dec 3 12:30:12 kernel: pc : [<0000000000029d34>] lr : [<0000000000029fb4>] pstate: 20070010
Dec 3 12:30:12 kernel: sp : 00000000ffacb840
Dec 3 12:30:12 kernel: x12: 00000000000a211c
Dec 3 12:30:12 kernel: x11: 0000000000081d64 x10: 0000000000000045
Dec 3 12:30:12 kernel: x9 : 0000000000000003 x8 : 0000000000000045
Dec 3 12:30:12 kernel: x7 : 00000000f5bfebf8 x6 : 0000000000000038
Dec 3 12:30:12 kernel: x5 : 00000000000003e8 x4 : 00000000f5bfec58
Dec 3 12:30:12 kernel: x3 : 0000000000000000 x2 : 0000000000000044
Dec 3 12:30:12 kernel: x1 : 000000000000000a x0 : 0000000000000000

Same here on AX86U

Dec 3 13:09:49 kernel: potentially unexpected fatal signal 11.
Dec 3 13:09:49 kernel: CPU: 0 PID: 2982 Comm: dnsmasq Tainted: P O 4.1.52 #2
Dec 3 13:09:49 (wan-event): 9188 Script not defined for wan-event: wan0-stopping
Dec 3 13:09:49 kernel: Hardware name: Broadcom-v8A (DT)
Dec 3 13:09:49 kernel: task: ffffffc02b9cea80 ti: ffffffc029494000 task.ti: ffffffc029494000
Dec 3 13:09:49 kernel: PC is at 0xf71bd654
Dec 3 13:09:49 kernel: LR is at 0x209ac
Dec 3 13:09:49 kernel: pc : [<00000000f71bd654>] lr : [<00000000000209ac>] pstate: 20010010
Dec 3 13:09:49 kernel: sp : 00000000ffb93ee8
Dec 3 13:09:49 kernel: x12: 0000000000000072
Dec 3 13:09:49 kernel: x11: 00000000000010f4 x10: 000000000009a70c
Dec 3 13:09:49 kernel: x9 : 00000000000010f8 x8 : 00000000ffffffff
Dec 3 13:09:49 kernel: x7 : 000000000009a70c x6 : 0000000000878f60
Dec 3 13:09:49 kernel: x5 : 00000000f726a5e8 x4 : 00000000ffb93d90
Dec 3 13:09:49 kernel: x3 : 0000000000000000 x2 : 0000000000000120

 

[jomcty]

First attempt failed while upgrading from 3004.388.4_rog to 3004.388.5_rog on Asus GT-AXE1100 (actually it never happened to me before, that an upgrade failed) ... will try again later

Try power cycling your router and use a different browser (FireFox).

I've had this happen to me using Chrome once in a blue moon, but doing the above allowed the flash to proceed (for me).

 

[octopus]

updated two routers without any problem, (well some).
Uptime: 0 days 3 hour(s) 46 minute(s) 0 seconds

1: My ssd disk as usuall and some build version back not mount after router com back after updateing.
Had to do a maually unmont/mount

2: update-notification doesen't trigg when alam clock flickering up in router corner.
Which I have reported several times, it can't be just me who has these phenomena.

3: My openvpn speed have decrased from 230-240 Mbps to 150-160 Mbps (-35%).
Haven't changed anything in my configs, just alot of program bug updates.

Thanks for new build's

 

[DJones]

This is more a Diversion issue, but since it happened after a Merlin upgrade from beta to stable I’m going to post it here. I’ve complained about this happening before and each time the fault is pushed to my storage medium which is a usb stick. Only it only ever happens with diversion and nothing else. Two scenarios it happens; either I manually update entware using the (u) command and it upgrades some component that diversion uses or Rmerlin upgrades some component diversion uses. Either way diversion seems to uninstall itself. No other amtm package is affected it seems.

As you can see in the picture diversion detects that pixelserv and other components are already installed. So maybe a mounting issue? Didn’t happen on the alpha or beta version and this one from beta to stable is I think just a title change. (Could be wrong)

Just an annoyance. I’ve mentioned this before in Asuswrt-Merlin add-ons; but I’m having doubts it’s my usb as I’ve used different one before. Just can’t be bothered to buy a cheap ssd, and enclosure for such minimal usage as it’s not used as a NAS.

Also what in the sweet broken UI is this?

Where did skynet’s gui go and why is it replaced with diversions gui?

And yes Diversions gui is on its proper page as well. >_>

I think it might be fair to do a full wipe or force reinstall of my addons at some point because doing a dirty upgrade seems to have caused issues.

Edit:
Force reinstalled addons and everything’s back to normal.

Looks like the upgrade corrupted the ext4 journal which likely explains why I have issues. Before the upgrade it was clean so not too sure why, but doubt it’s the stick itself most likely maybe a locked file got corrupted when the upgrade occurred and the router rebooted. Just my speculation.

 Sat Dec  2 05:02:54 EST 2023 Waited 5s for NTP to sync date
 Sat Dec  2 05:02:54 EST 2023 Probing 'ext4' on device /dev/sda1
 Running disk check v3.2, with command 'e2fsck -p' on /dev/sda1
 Entware: clean, 5454/1896832 files, 2841208/7575548 blocks
 Sat Dec  2 05:02:54 EST 2023 Disk check done on /dev/sda1
 
 Sat Dec  2 17:35:32 EST 2023 Waited 10s for NTP to sync date
 Sat Dec  2 17:35:32 EST 2023 Probing 'ext4' on device /dev/sda1
 Running disk check v3.2, with command 'e2fsck -p' on /dev/sda1
 Entware: recovering journal
 Entware: clean, 5466/1896832 files, 2841726/7575548 blocks
 Sat Dec  2 17:36:11 EST 2023 Disk check done on /dev/sda1
 
 Sat Dec  2 23:51:05 EST 2023 Waited 10s for NTP to sync date
 Sat Dec  2 23:51:05 EST 2023 Probing 'ext4' on device /dev/sda1
 Running disk check v3.2, with command 'e2fsck -p' on /dev/sda1
 Entware: clean, 5475/1896832 files, 2842147/7575548 blocks
 Sat Dec  2 23:51:11 EST 2023 Disk check done on /dev/sda1

 

[JIPG]

There was a bug in 388.4 where it would try to retrieve the incorrect filename when fetching the changelog. The issue was fixed in 388.5, however that fix won't help getting the notification for people with the affected firmwares.

I've gone ahead and saved a second copy of the changelog using the incorrect filename, so in theory it should also appear for 388.4 users now. However I expect people to upgrade to 388.5, as I have no intention of doing the same duplicate changelog with future releases.
.

Upgraded to 388.5 and working without a glitch. Thank you RMerlin for your efforts.

 

[CaptainSTX]

Smooth update everything working fine.

Thank you.

 

[PorscheT]

Upgraded from beta. Working great as always with my two AX110000 mesh. Thank you Merlin!

 

[Damit1]

I donated my yearly donation to thank you for this last SW, trully appreciated.

Hope for many more RMerlin Goodies to come
Thank you Eric!

 

[nzwayne]

Hi all,

I have a tricky issue with updating the firmware. I have a GT-AXE16000 and when I try to upload the new firmware, every time is't jumping back to router login screen.
I did try different browser or pc is the same.

Any ideas what it could be the issue?

I get this occasionally (also had it on earlier AXE1000). What resolves every time (for me) is Power Off Router, count to 10 (to avoid immediate off/on's), Power On Router, then some minutes after power up, then I action the firmware update via GUI panel. BTW: Not cleared a browser (Firefox or Edge) cache since re-installing Win11 six months ago on my Laptop.

 

[nzwayne]

Upgraded through the 3004.388-5 Alpha's, Beta and now on the GA level. I do the Mesh units first as acheck the code is operational to the model, before doing the Router unit.
Thanks RMerlin for the time, energy and skills to deploy these updates. Without your support for ASUS Routers, myself and my friends/work mates, wouldn't have purchased as many ASUS Router products. ASUS branding then bleeds into purchasing Motherboards and Graphic cards too

On item of interest, after each of the 388-5 Alpha/Beta/GA updates on the GT-AXE1600, this message would be posted on browser panel after GUI invoked update.

With the first Alpha I just ignored, to avoid further disruption to the 50+ clients/devices at home. Then within 24-48hrs most of my seven Roost Water/Heat/Humidity units started dropping offline. If you manually re-connected them again, most dropped out again over 24-48hrs. Powered off/on the Router after the second Alpha and still no better. What did resolve the Roosts dropping out, was powering off/on the AXE16000 I have as a AiMesh unit.

All the Add-Ons (as per my signature) all working ok too on these levels.

BTW: I had to drop two Add-Ons in last few months: spdmerlin as caused random boots, scribe (forget why off top of my head). Diversion "Full" created issues with 'pixelserv' but Diverson "Lite" works a charm, key to disable 'type 65 blocking'.