What's new

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

  • 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!

Status
Not open for further replies.
Getting an Invalid Firmware Upload error with an AX88U after attempting to upgrade from 2 separate systems, with USB unmounted.

Tripled checked I was downloading the right file, same result every time. Anyone else run into this?
 
No issues with my AX88U flashing from 4b but note that I never tried the troubled original beta 4 when it was first released. Also I will say I have never had to unmount the USB drive when upgrading,
 
Had to wait for the wife's telenovela to finish, last episode and don't trust the DVR in the cloud enough to bet my life on it.

Now on Beta 5, AX88 (Beta 4b before) Main router and both AC5300 (Beta4 before) AIMESH nodes. Upgrade was a breeze, no issues. IPv6 looking much more stable. No more DDNS restarting every few minutes even though its disabled. All scripts running solid. Logs have a lot less going on, looking real good so far. Been runing for ~45m. Will beat on it more tomorrow.
 
Same here upgrade was a breeze on rt-ax88u from Beta 4b to beta 5, also never used beta 4 firmware, and i didnt have to unmount the USB drive
 
Getting an Invalid Firmware Upload error with an AX88U after attempting to upgrade from 2 separate systems, with USB unmounted.

Tripled checked I was downloading the right file, same result every time. Anyone else run into this?

Is your current firmware the beta 4? or beta 4b?
 
Is your current firmware the beta 4? or beta 4b?
Getting an Invalid Firmware Upload error with an AX88U after attempting to upgrade from 2 separate systems, with USB unmounted.

Tripled checked I was downloading the right file, same result every time. Anyone else run into this?

If your’re running aiprotection, withdraw consent and try again. I hade the same issue going from 4 to 4b. No issue going from 4b to 5 though. Ax88u
 
Beta 4 was just rock solid on my RT-AX58U, I'll admit I'm a little worried Beta 5 might introduce a new issue but everything seems good so far.

Something I noticed upgrading to Beta 4 and now 5 is that the scheduled disk health scan in the External USB drive tab gets reset to disabled after updating. Not sure if that's an ASUS issue but figured I'd mention it.
 
Upgrade to B5 on AX86 (Aimesh master) and ax5200 (aimesh slave) and both running fine.
Guest Wifi #1 seems to be fixes and less noise in the log also.

Looks very promising ...
 
Upgrade to B5 on AX86 (Aimesh master) and ax5200 (aimesh slave) and both running fine.
Guest Wifi #1 seems to be fixes and less noise in the log also.

Looks very promising ...
It look like enabling bandwith limit on guest #1 brings down the wan/dns/ ...

@RMerlin
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.641 wl1: wlc_ampdu_dotxstatus_aqm_complete: tx phy error (0x8500)
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.641 wl1.0: wlc_send_bar: for d2:26:9e:f4:61:60 seq 0x6 tid 0
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.641 wl1: wlc_ampdu_dotxstatus_aqm_complete: tx phy error (0x8500)
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.641 wl1.0: wlc_send_bar: for d2:26:9e:f4:61:60 seq 0x7 tid 0
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.949 wl1: wlc_ampdu_dotxstatus_aqm_complete: tx phy error (0x8500)
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.949 wl1.0: wlc_send_bar: for d2:26:9e:f4:61:60 seq 0x3 tid 6
Jan 26 07:56:10 rtaxbeast acsd: acsd_main_loop(1107): sync_id: 24413, status:1, misc.error/abort
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 wl1: PSM microcode watchdog fired at 882 (seconds). Resetting.
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 wl1: reason = psm watchdog at 882 seconds. corerev 129.1 ucode revision 1570.159 features 0x9106
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 psmdebug 0x01ff000d phydebug 0x48 macctl 0x4160403 maccmd 0x4
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: psm_brc 0x0080 psm_brc_1 0x424a M_UCODE_DBGST 0x2
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 PSMR1: psmdebug 0x0000009b macctl 0x4060402 maccmd 0x0 M_UCODE_DBGST 0x2
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 brwk_0 0x2401 brwk_1 0x0094 brwk_2 0x22a0 brwk_3 0x0ff2 brwk_4 0x0006
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 ifsstat 0xaf ifsstat1 0xff txectl 0x4000 txestat 0x425
Jan 26 07:56:10 rtaxbeast kernel: CFG80211-ERROR) wl_cfg80211_change_station : WLC_SCB_AUTHORIZE sta_flags_mask not set
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 rxestat1 0x4181 rxestat2 0x540 rcv_frmcnt 0x0 rxe_rxcnt 0x2e
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 wepctl 0x0
Jan 26 07:56:10 rtaxbeast hostapd: eth7: STA 2c:2b:f9:92:45:8c IEEE 802.11: associated
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 aqmf_ready0 0x0 aqmf_ready1 0x0 aqmf_ready2 0x0 aqmf_ready3 0x0
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 aqmf_ready4 0xa wepstat 0x0 wep_ivloc 0x10 wep_psdulen 0x187
Jan 26 07:56:10 rtaxbeast hostapd: eth7: STA 2c:2b:f9:92:45:8c RADIUS: starting accounting session F5B50369FABA66B9
Jan 26 07:56:10 rtaxbeast hostapd: eth7: STA 2c:2b:f9:92:45:8c WPA: pairwise key handshake completed (RSN)
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 rxe_errval 0x0 rxe_errmask 0x20f rxe_status3 0x100 txe_status2 0x425
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 dbg_bmc_status 0x0 psm_chk0_err 0x0 psm_chk1_err 0x0
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 PC :
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 R0: 0x17f7 0x17f7 0x17f7 0x17f7
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 R1: 0x9b 0x9b 0x9b 0x9b
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 R1: 0x9b 0x9b 0x9b 0x9b
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 R1: 0x9b 0x9b 0x9b 0x9b
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 R1: 0x9b 0x9b 0x9b 0x9b
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 R1: 0x9b 0x9b 0x9b 0x9b
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 R1: 0x9b 0x9b 0x9b 0x9b
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 R1: 0x9b 0x9b 0x9b 0x9b
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 R1: 0x9b 0x9b 0x9b 0x9b
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 R1: 0x9b 0x9b 0x9b 0x9b
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 R1: 0x9b 0x9b 0x9b 0x9b
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 R1: 0x9b 0x9b 0x9b 0x9b
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 R1: 0x9b 0x9b 0x9b 0x9b
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 R1: 0x9b 0x9b 0x9b 0x9b
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 R1: 0x9b 0x9b 0x9b 0x9b
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 R1: 0x9b 0x9b 0x9b 0x9b
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 R1: 0x9b 0x9b 0x9b 0x9b
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 phydebug :
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 0x48 0x48 0x48 0x48
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 0x48 0x48 0x48 0x48
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 0x48 0x48 0x48 0x48
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 0x48 0x48 0x48 0x48
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 0x48 0x48 0x48 0x48
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 0x48 0x48 0x48 0x48
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 0x48 0x48 0x48 0x48
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 0x48 0x48 0x48 0x48
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 pktproc 0x101 pktproc 0x101 pktproc 0x101 pktproc 0x101
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 TxFifoStatus0 0x1c3 TxFifoStatus1 0x1c3
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 gpiosel 0x0 gpiolo 0x0 gpiohi 0x0
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 gpiosel 0x1 gpiolo 0x0 gpiohi 0x0
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 psm stack_status : 0x8000
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 psm stack_entries:
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 0x17f7
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 0x1959
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 0x0629
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 0x1f24
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 0x09ff
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 0x3d1f
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 0x3438
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 0x3fdf
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 0) usr_count = 0, schedid = 0
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 1) usr_count = 0, schedid = 0
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 2) usr_count = 0, schedid = 0
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 3) usr_count = 0, schedid = 0
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 wl1: wlc_check_assert_type HAMMERING: reinit_reason 2
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 wl1: fatal error, reinitializing
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 wl1: fatal error, reinitializing, total count of reinit's[1]
Jan 26 07:56:10 rtaxbeast kernel: CONSOLE: 033178.989 wl1: 802.11 reinit reason[2], count[1]
 
Last edited:
beta 4b. no AI protection. Just a USB with Diversion and Skynet with AMTM. Haven't had any issue doing any updates ever before, so I'm curious what the change is.

Make sure you do have the correct model. beta 4b shouldn't have any problem upgrading to beta 5, the issue was only with beta 4.
 
The 'group' is too big to mention/name individually, but they know we love them all and couldn't do without each and every one of them!

Not to mention Asus too for their solid collaboration with RMerlin in many ways (GPL code, hardware, etc.).

The RT-AX86U AiMesh wired pair is behaving better than ever, even if it is only for a bit less than 7 hours. I smell a 386.1 final release in the air very soon.
 
Successful update from 386.1_beta4b-gb9175c6a96 to beta5 on AX88U. Will try to check if everything works properly.
Thank you guys :)
 
Upgraded to beta 5 from B4B, earlier today and all is good. No problem at all with the upgrade, used the WPS reset across ALL, and then completed a manual rebuild.

Temperature is back to normal.
CPU's are stable.
I am using the Ethernet backhaul mode, all is stable across all.
Syslog Clean
No VPN
No Trend Micro enabled

Thanks to ALL associated, in making this new beta possible.
 
Last edited:
Thanks to the "team" for Beta 5 !!! :D Installed it this morning on my AX86U and did a full factory reset/nuke afterwards. Seems to run great after a few hours, but still having two "old" issues...

1. Logs are still flooding with this stuff. It began right after setting up the router, so shouldn't be any custom settings I use. Anyone else with an AX86U getting this, so it's ASUS that still haven't disabled debug-logging?!

Code:
Jan 26 10:36:10 kernel: CONSOLE: 145417.629 wl1: wlc_ampdu_recv_addba_resp: xx:xx:xx:xx:xx:xx: Failed. status 37 wsize 64 policy 1
Jan 26 10:36:10 kernel: CONSOLE: 145417.629 wl1: wlc_ampdu_recv_addba_resp: xx:xx:xx:xx:xx:xx: Failed. status 37 wsize 64 policy 1
Jan 26 10:36:10 kernel: CONSOLE: 145417.629 wl1: wlc_ampdu_recv_addba_resp: xx:xx:xx:xx:xx:xx: Failed. status 37 wsize 64 policy 1
Jan 26 10:36:11 kernel: CONSOLE: 145418.605 wl1: wlc_ampdu_recv_addba_resp: xx:xx:xx:xx:xx:xx: Failed. status 37 wsize 64 policy 1
Jan 26 10:36:12 kernel: CONSOLE: 145420.559 wl1: wlc_ampdu_recv_addba_resp: xx:xx:xx:xx:xx:xx: Failed. status 37 wsize 64 policy 1

2. The Guest 1 bug is still there for me. Switched to Guest 2 and no errors.

Code:
Jan 26 11:12:06 kernel: protocol 0800 is buggy, dev eth7
Jan 26 11:12:06 kernel: protocol 0800 is buggy, dev eth7
Jan 26 11:12:06 kernel: protocol 0800 is buggy, dev eth7
Jan 26 11:12:06 kernel: protocol 0800 is buggy, dev eth7
Jan 26 11:12:06 kernel: protocol 0800 is buggy, dev eth7
 
I just downloaded 386.1 beta 5 for RT-AX88U but the update keep failing. Is there something wrong with this beta5?
1611657336116.png
 
My log is full of stuff like this

Jan 26 11:56:28 kernel: [BLOCKED - INBOUND] IN=eth0 OUT= MAC=04:d9:f5:fb:db:d8:00:01:5c:a5:00:5f:08:00 SRC=185.193.91.250 DST=my.ip LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=16802 PROTO=TCP SPT=52556 DPT=8489 SEQ=2481059237 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0 MARK=0x8000000

Am I under attack? :D

 
Status
Not open for further replies.

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