[Thread-1] [ 386.1_Alpha Build(s) ] Testing available build(s)

[Unisoft]

You really should do a Hard Factory Reset when going from Asus to Merlin firmware. See: https://www.asus.com/support/FAQ/1039074/ The AX86U will use Method 2. And double check that the /jffs is mounted after a Hard Reset.

OK.

I'd already hard reset the RT-AC86U and had the issues.

So, TWO brand spanking new AX86U (different model being pointed out here) and a hard reset was done after flashing to Merlin using the Asus Method2.

The issue with NTP not syncing after reboot still exists. Once booted, I have to go into the Administration > System page and press APPLY button then NTP syncs the correct date/time.
On the AX86U's though - I don't have the issue with having to change the login user id just to be able to change any setting on that page.

 

[bbunge]

OK.

I'd already hard reset the RT-AC86U and had the issues.

So, TWO brand spanking new AX86U (different model being pointed out here) and a hard reset was done after flashing to Merlin using the Asus Method2.

The issue with NTP not syncing after reboot still exists. Once booted, I have to go into the Administration > System page and press APPLY button then NTP syncs the correct date/time.
On the AX86U's though - I don't have the issue with having to change the login user id just to be able to change any setting on that page.

There was some earlier discussion on the MTU causing problems. You should make sure you set MTU to 1500. WAN DNS issues can cause the time not to sync. Turn off DoT if you use it. Set the WAN DNS to reliable upstream DNS servers in your area. Worse case set the time servers to an IP address in lieu of a URL. Also, this is beta firmware and the first Merlin for the AX86U. You might do well to use one of the AC86U's for a main router until the bugs have been worked out of the firmware for the AX86U.

 

[brianward317]

Looks like Alpha 4 is out

 

[Sicario]

new alpha4-gd4b7146753 is now available

 

[brianward317]

Appears the alpha 4 still doesn't work with the rt-3100 router. Router becomes unpingable and it drops off as a node. Performed hard reset Alpha 4 works on AX88 and AC68 no issues. Early alpha 3 works on the 3100 model.
Will have to roll back to Alpha 2 and try again once it's stable for this model.

 

[ecantona9]

Appears the alpha 4 still doesn't work with the rt-3100 router. Router becomes unpingable and it drops off as a node. Performed hard reset Alpha 4 works on AX88 and AC68 no issues. Alpha 3 didn't seem to work for it either. Will have to roll back to Alpha 2 and try again once it's stable for this model.

Ugh. Been waiting on this one. I guess I will stay with the early Alpha3 version. Its been working great for the ac86u as the main and the ac3100 as the node. Only problem I'm having is the Traffic Analyzer is only picking up my activity in MBs. I know we're using GBs in this house.

 

[brianward317]

Ugh. Been waiting on this one. I guess I will stay with the early Alpha3 version. Its been working great for the ac86u as the main and the ac3100 as the node. Only problem I'm having is the Traffic Analyzer is only picking up my activity in Mbs. I know we're using GBs in this house.

Agreed! Not Alpha 2, early version of Alpha 3 works just fine. I'll revert back to that and wait.

 

[JWoo]

Tried Alpha 4 on my RT-AX58U. Did a clean install.

2.4Ghz wireless works fine. 5.0Ghz wireless does not function: cannot set Control Channel (stuck on Auto and defaulted to 0) and cannot change channel bandwidth beyond 40MHz (no 80MHz or 160MHz).

SSH also does not appear to work.

Nov 29 20:58:53 syslogd started: BusyBox v1.25.1
Nov 29 20:58:53 kernel: klogd started: BusyBox v1.25.1 (2020-11-29 17:52:27 EST)
Nov 29 20:59:12 dropbear[5740]: Failed loading /etc/dropbear/dropbear_rsa_host_key
Nov 29 20:59:12 dropbear[5740]: Failed loading /etc/dropbear/dropbear_dss_host_key
Nov 29 20:59:12 dropbear[5740]: Failed loading /etc/dropbear/dropbear_ecdsa_host_key
Nov 29 20:59:12 dropbear[5740]: Failed loading /etc/dropbear/dropbear_ed25519_host_key
Nov 29 20:59:12 dropbear[5740]: Early exit: No hostkeys available. 'dropbear -R' may be useful or run dropbearkey.
Nov 29 20:59:12 hour_monitor: daemon is starting
Nov 29 20:59:12 hour_monitor: daemon terminates

These are Alpha builds on a new Asus code base so it will take a little time to get the bugs worked out.

 

[crkpot]

I can confirm RT-AX58U clean install and 5GHz not working. Just get the same options as 2.4.

 

[RMerlin]

I can confirm RT-AX58U clean install and 5GHz not working. Just get the same options as 2.4.

Looks like the 5 GHz SoC firmware image is missing, maybe the previous GPL merge moved that image to a different location. I'll have to check.

 

[Sicario]

Looks like the 5 GHz SoC firmware image is missing, maybe the previous GPL merge moved that image to a different location. I'll have to check.

Specifically for AX58U or all the builds? I was trying to update my AC68U mesh node (wireless backhaul), it didn't show any progress of install, and didn't appear upgraded after that, still shown as alpha3.

 

[crkpot]

Specifically for AX58U or all the builds? I was trying to update my AC68U mesh node (wireless backhaul), it didn't show any progress of install, and didn't appear upgraded after that, still shown as alpha3.

Try a factory reset before flashing. I've had to do that, for the reason you describe, with each alpha upgrade since AX58U was added.

 

[RMerlin]

Specifically for AX58U or all the builds?

Just the RT-AX58U (the other model on that same SDK, the RT-AX56U, does not use dhd at all, both its radios use the built-in wifi from the 6750 CPU).

The RT-AC68U firmware is fine, it's my primary development platform here, so it's actually tested.

 

[RMerlin]

I fixed a typo in 386_41035's Makefile causing the RT-AX58U 5 GHz radio firmware to be missing from the router's firmware image. Rebuilt firmware has been uploaded.

 

[Sicario]

It turns out I had to update my mesh router (AC86U) first, therefore I can update my node.

 

[iJorgen]

Installed Alpha 4 on my AX86U, but still notice the systemlog flooding with these messages from different MAC-addresses, same as in alpha 3. Is it a setting or known issue?

Nov 30 06:49:21 kernel: CONSOLE: 020931.321 wl1: wlc_ampdu_recv_addba_resp: XX:XX:XX:XX:XX:XX: Failed. status 37 wsize 64 policy 1
Nov 30 06:49:22 kernel: CONSOLE: 020932.191 wl1: wlc_ampdu_recv_addba_resp: XX:XX:XX:XX:XX:XX: Failed. status 37 wsize 64 policy 1
Nov 30 06:49:22 kernel: CONSOLE: 020932.191 wl1: wlc_ampdu_recv_addba_resp: XX:XX:XX:XX:XX:XX: Failed. status 37 wsize 64 policy 1
Nov 30 06:49:23 kernel: CONSOLE: 020933.188 wl1: wlc_ampdu_recv_addba_resp: XX:XX:XX:XX:XX:XX: Failed. status 37 wsize 64 policy 1
Nov 30 06:49:23 kernel: CONSOLE: 020933.226 wl1: wlc_ampdu_recv_addba_resp: XX:XX:XX:XX:XX:XX: Failed. status 37 wsize 64 policy 1
Nov 30 06:49:31 kernel: CONSOLE: 020941.156 wl1: wlc_ampdu_recv_addba_resp: XX:XX:XX:XX:XX:XX: Failed. status 37 wsize 64 policy 1

 

[RMerlin]

Installed Alpha 4 on my AX86U, but still notice the systemlog flooding with these messages from different MAC-addresses, same as in alpha 3. Is it a setting or known issue?

Nov 30 06:49:21 kernel: CONSOLE: 020931.321 wl1: wlc_ampdu_recv_addba_resp: XX:XX:XX:XX:XX:XX: Failed. status 37 wsize 64 policy 1
Nov 30 06:49:22 kernel: CONSOLE: 020932.191 wl1: wlc_ampdu_recv_addba_resp: XX:XX:XX:XX:XX:XX: Failed. status 37 wsize 64 policy 1
Nov 30 06:49:22 kernel: CONSOLE: 020932.191 wl1: wlc_ampdu_recv_addba_resp: XX:XX:XX:XX:XX:XX: Failed. status 37 wsize 64 policy 1
Nov 30 06:49:23 kernel: CONSOLE: 020933.188 wl1: wlc_ampdu_recv_addba_resp: XX:XX:XX:XX:XX:XX: Failed. status 37 wsize 64 policy 1
Nov 30 06:49:23 kernel: CONSOLE: 020933.226 wl1: wlc_ampdu_recv_addba_resp: XX:XX:XX:XX:XX:XX: Failed. status 37 wsize 64 policy 1
Nov 30 06:49:31 kernel: CONSOLE: 020941.156 wl1: wlc_ampdu_recv_addba_resp: XX:XX:XX:XX:XX:XX: Failed. status 37 wsize 64 policy 1

This is simply debugging output. Asus has debugging enabled on wifi because these are part of public beta releases.

 

[JWoo]

I fixed a typo in 386_41035's Makefile causing the RT-AX58U 5 GHz radio firmware to be missing from the router's firmware image. Rebuilt firmware has been uploaded.

Running on it now. Thanks for recompiling the firmware. I can confirm the RT-AX58U has both radios working now.

 

[Krism]

installed (not clean) alpha4 on my ax86u and everything is working fine for the moment

 

[chchia]

Try a factory reset before flashing. I've had to do that, for the reason you describe, with each alpha upgrade since AX58U was added.

same here, AX58U, need to factory reset otherwise update will not work. since Alpha 3. (AX58U added)

when i upload the firmware, without any error message it reboot the AX58U, and the same old firmware intact.