Beta Asuswrt-Merlin 386.1 Beta is now available

[bradbort]

I've been running beta 3 since we resolved the MCU being blanked problem when installing over asus stock.

Everything has been going well with my AC88U, running non-mesh, with about 30 clients with two exceptions:

1. I lost the 5g band once. I turned off 160, and that problem has not reoccurred. I gather from other postings that this may have to do with the auto channel it selects for that high bandwidth.

2. IPV6 seemed to be non-functions in beta 3. I noticed this because of log errors. When I reverted back to ASUS 386 stock, IPV6 came back.

Any ideas how to trouble shoot the issue in beta 3? set it to native, and auto, which populated the proper settings, which works in stock but not the beta.

Typo. That is AX88u

 

[clweb]

Not going above 50c here on the AX58U. Been checking every hour. Just checked now its 47c

Yes, 47°C is the normal temp. for 2.4GHz. So I'm searching for an explanation.
When I do an ifconfig via ssh, i have eth0 to eth5 with the 2.4GHz address, and only eth6 for 5GHz.
Also i have a CFE with version 0.1.0.7, I read most poeple here have a 0.5.0.5.

 

[Treadler]

I've been running beta 3 since we resolved the MCU being blanked problem when installing over asus stock.

Everything has been going well with my AC88U, running non-mesh, with about 30 clients with two exceptions:

1. I lost the 5g band once. I turned off 160, and that problem has not reoccurred. I gather from other postings that this may have to do with the auto channel it selects for that high bandwidth.

2. IPV6 seemed to be non-functions in beta 3. I noticed this because of log errors. When I reverted back to ASUS 386 stock, IPV6 came back.

Any ideas how to trouble shoot the issue in beta 3? set it to native, and auto, which populated the proper settings, which works in stock but not the beta.

IPv6 working fine here on beta 3.

 

[bradbort]

IPv6 working fine here on beta 3.

I wonder is this is another case of folks who move over from stock ASUS 386 to the beta run into some sort of data glitch problem. That was the problem with my internet connection issues earlier.

 

[David Williams]

Have a RT-AX86U with Beta 3 running and one Mesh node (RT-AC-3100) running Beta 3 also:

Lost access for about 45 seconds a few minutes ago and see the following in logs:

Jan 1 17:27:58 kernel: Virtual device br0 asks to queue packet!
Jan 1 17:27:58 kernel: Virtual device br0 asks to queue packet!
Jan 1 17:27:58 kernel: Virtual device br0 asks to queue packet!
Jan 1 17:27:58 kernel: Virtual device br0 asks to queue packet!
Jan 1 17:27:58 kernel: Virtual device br0 asks to queue packet!
Jan 1 17:27:58 kernel: Virtual device br0 asks to queue packet!
Jan 1 17:27:58 kernel: Virtual device br0 asks to queue packet!
Jan 1 17:27:58 kernel: Virtual device br0 asks to queue packet!
Jan 1 17:27:58 kernel: Virtual device br0 asks to queue packet!
Jan 1 17:27:58 kernel: Virtual device br0 asks to queue packet!
Jan 1 17:28:04 kernel: Virtual device br0 asks to queue packet!
Jan 1 17:28:04 kernel: Virtual device br0 asks to queue packet!
Jan 1 17:28:05 kernel: Virtual device br0 asks to queue packet!
Jan 1 17:28:06 kernel: Virtual device br0 asks to queue packet!
Jan 1 17:28:06 kernel: Virtual device br0 asks to queue packet!
Jan 1 17:28:07 kernel: Virtual device br0 asks to queue packet!
Jan 1 17:28:07 kernel: Virtual device br0 asks to queue packet!
Jan 1 17:28:07 Mastiff: Got SIGTERM
Jan 1 17:28:25 Mastiff: init


This went on about 45 seconds and then everything came back. What is device br0? Is there something I should be looking at that would cause this?

I see now that my 5G is showing disabled. After reboot it came back.

 

[Treadler]

I wonder is this is another case of folks who move over from stock ASUS 386 to the beta run into some sort of data glitch problem. That was the problem with my internet connection issues earlier.

IMHO, a full reset called for in that scenario.

 

[bradbort]

IMHO, a full reset called for in that scenario.

I had done a full reset when I moved to the stock asus 386 firmware. Since it is still working when I move back to it after noting the IPV6 issue, I'm not inclined to do another full reset to move to the beta, unless something else is going on.

 

[Blacklistedcard]

Typo. That is AX88u

IPV6 is running fine on my AX88U. Any client using IPV6 is running ok.

 

[Treadler]

Back on 386 beta 3. Did a services-start script file to run "pwr config --wait on" and the CPU temp is holding at 83-84 C. Cooling fan on order...

Beta 3, did “pwr config (2 hyphens) cpuwait on”.
AX88U.
Ambient 25°.
Cpu temp went from 76° to 66° in 30 seconds or so.
No operational issues seen so far.
Just wish I knew how to make it survive a reboot........
(Any guidance appreciated).

[Edit, 63° now!]

 

[Blacklistedcard]

Beta 3, did “pwr config (2 hyphens) cpuwait on”.
AX88U.
Ambient 25°.
Cpu temp went from 76° to 66° in 30 seconds or so.
No operational issues seen so far.
Just wish I knew how to make it survive a reboot........
(Any guidance appreciated).

I thought that the AX88Us were supposed to have the cpu wait set to off?

 

[Sanna1967]

Beta 3, did “pwr config (2 hyphens) cpuwait on”.
AX88U.
Ambient 25°.
Cpu temp went from 76° to 66° in 30 seconds or so.
No operational issues seen so far.
Just wish I knew how to make it survive a reboot........
(Any guidance appreciated).

I am not sure it is revelant to your model . Merlin fixed it already for the next release

rc: re-enable cpuwait support on RT-AC86U/GT-AC2900 · RMerl/asuswrt-merlin.ng@ec97c10

Third party firmware for Asus routers (newer codebase) - rc: re-enable cpuwait support on RT-AC86U/GT-AC2900 · RMerl/asuswrt-merlin.ng@ec97c10

github.com

 

[Treadler]

I thought that the AX88Us were supposed to have the cpu wait set to off?

Yes.
Obviously too much time on my hands, experimenting......

 

[Blacklistedcard]

I am not sure it is revelant to your model . Merlin fixed it already for the next release

rc: re-enable cpuwait support on RT-AC86U/GT-AC2900 · RMerl/asuswrt-merlin.ng@ec97c10

Third party firmware for Asus routers (newer codebase) - rc: re-enable cpuwait support on RT-AC86U/GT-AC2900 · RMerl/asuswrt-merlin.ng@ec97c10

github.com

I just did a pull and clean build. I noticed that my AC86U as a AiMesh node is still set to cpuwait as disabled.

ASUSWRT-Merlin RT-AC86U 386.1_beta4-g434857ddb5 Sat Jan 2 04:13:19 UTC 2021
admin@RT-AC86U-F210:/tmp/home/root# pwr show

Power Management Configuration
Functional Block Status
CPU Wait DISABLED
Ethernet Auto Power Down ENABLED
Energy Efficient Ethernet DISABLED
Switch Deep Green Mode ENABLED (statuseactivated)

Here is my AX88U running latest commit

ASUSWRT-Merlin RT-AX88U 386.1_beta4-g434857ddb5 Sat Jan 2 04:13:36 UTC 2021
admin@RT-AX88U-5918:/tmp/home/root# pwr show

Power Management Configuration
WIFI Off Disabled
DISK Off Disabled
PCI ASPM Disabled
UBUS DCM N/A
CPU Off N/A
CPU Wait Disabled
CPU Speed Disabled
XRDP Gate N/A
NET Down Disabled
PHY Down Disabled
PHY EEE Enabled
PHY APD Enabled
SF2 DGM Enabled
DRAM SR N/A
AVS Enabled

 

[cybrnook]

I thought that the AX88Us were supposed to have the cpu wait set to off?

Looking at the code snippet from Merlin's recent comment, that seems the intention from asus was for hw v1.0 only.

Beta - Asuswrt-Merlin 386.1 Beta is now available

As I suspected, this was a deliberate change by Asus in a recent GPL merge. @@ -3613,6 +3701,9 @@ void init_others(void) #ifdef GTAC2900 update_cfe_ac2900(); #endif +#if defined(RTAC86U) || defined(GTAC2900) + system("pwr config --wait off"); +#endif #if defined(RTAX88U) ||...

www.snbforums.com

if defined(RTAX88U) || defined(RTAX92U) if(nvram_match("HwVer", "1.0")) { system("pwr config --cpuwait off

 

[SomeWhereOverTheRainBow]

Is this a new feature on the RTAX88U in beta 3?

if so, what values should be put here?

 

[athua]

Currently using Beta3 on two RT-AC68U (One as an AP and the other as an AIMESH node). Been using Beta1 and did a clean install (factory reset) after installing Beta1. Then a dirty update to Beta2 and then now to Beta3.
When I ssh into the AP, and issue the following command 'wl -i eth2 country', it returns 'US (US/0) UNITED STATES' even when I change my region in the UI to Australia.

This then limits the available 5Ghz channels as shown using the 'wl -i eth2 chanspec_txpwr_max' command:

36 (0xd024) 18.00(dbm)
40 (0xd028) 18.00(dbm)
44 (0xd02c) 18.00(dbm)
48 (0xd030) 18.00(dbm)
149 (0xd095) 25.50(dbm)
153 (0xd099) 25.50(dbm)
157 (0xd09d) 25.50(dbm)
161 (0xd0a1) 25.50(dbm)
165 (0xd0a5) 25.50(dbm)
40u (0xd926) 13.50(dbm)
48u (0xd92e) 13.50(dbm)
153u (0xd997) 23.50(dbm)
161u (0xd99f) 23.50(dbm)
36l (0xd826) 13.50(dbm)
44l (0xd82e) 13.50(dbm)
149l (0xd897) 23.50(dbm)
157l (0xd89f) 23.50(dbm)
36/80 (0xe02a) 13.50(dbm)
149/80 (0xe09b) 25.50(dbm)
40/80 (0xe12a) 18.00(dbm)
153/80 (0xe19b) 25.50(dbm)
44/80 (0xe22a) 18.00(dbm)
157/80 (0xe29b) 25.50(dbm)
48/80 (0xe32a) 18.00(dbm)
161/80 (0xe39b) 25.50(dbm)

If I change the country code to AU using: 'wl -i eth2 country AU', it changes to Australia and I get the following available to me:

36 (0xd024) 21.00(dbm)
40 (0xd028) 21.00(dbm)
44 (0xd02c) 21.00(dbm)
48 (0xd030) 21.00(dbm)
52 (0xd034) 21.00(dbm)
56 (0xd038) 21.00(dbm)
60 (0xd03c) 21.00(dbm)
64 (0xd040) 21.00(dbm)
100 (0xd064) 21.00(dbm)
104 (0xd068) 21.00(dbm)
108 (0xd06c) 21.00(dbm)
112 (0xd070) 21.00(dbm)
116 (0xd074) 21.00(dbm)
132 (0xd084) 21.00(dbm)
136 (0xd088) 21.00(dbm)
140 (0xd08c) 21.00(dbm)
144 (0xd090) 21.00(dbm)
149 (0xd095) 21.00(dbm)
153 (0xd099) 21.00(dbm)
157 (0xd09d) 21.00(dbm)
161 (0xd0a1) 21.00(dbm)
165 (0xd0a5) 21.00(dbm)
40u (0xd926) 22.00(dbm)
48u (0xd92e) 22.00(dbm)
56u (0xd936) 22.00(dbm)
64u (0xd93e) 22.00(dbm)
104u (0xd966) 22.00(dbm)
112u (0xd96e) 22.00(dbm)
136u (0xd986) 22.00(dbm)
144u (0xd98e) 22.00(dbm)
153u (0xd997) 22.00(dbm)
161u (0xd99f) 22.00(dbm)
36l (0xd826) 22.00(dbm)
44l (0xd82e) 22.00(dbm)
52l (0xd836) 22.00(dbm)
60l (0xd83e) 22.00(dbm)
100l (0xd866) 22.00(dbm)
108l (0xd86e) 22.00(dbm)
132l (0xd886) 22.00(dbm)
140l (0xd88e) 22.00(dbm)
149l (0xd897) 22.00(dbm)
157l (0xd89f) 22.00(dbm)
36/80 (0xe02a) 22.00(dbm)
52/80 (0xe03a) 22.00(dbm)
100/80 (0xe06a) 22.00(dbm)
132/80 (0xe08a) 22.00(dbm)
149/80 (0xe09b) 22.00(dbm)
40/80 (0xe12a) 22.00(dbm)
56/80 (0xe13a) 22.00(dbm)
104/80 (0xe16a) 22.00(dbm)
136/80 (0xe18a) 22.00(dbm)
153/80 (0xe19b) 22.00(dbm)
44/80 (0xe22a) 22.00(dbm)
60/80 (0xe23a) 22.00(dbm)
108/80 (0xe26a) 22.00(dbm)
140/80 (0xe28a) 22.00(dbm)
157/80 (0xe29b) 22.00(dbm)
48/80 (0xe32a) 22.00(dbm)
64/80 (0xe33a) 22.00(dbm)
112/80 (0xe36a) 22.00(dbm)
144/80 (0xe38a) 22.00(dbm)
161/80 (0xe39b) 22.00(dbm)

Anyone know why the Country code set in the UI does not seem to be updating the actual country code being used?

 

[Kees17760]

I taped a little 5v maker fan to the middle of the right side vents, over the processor, wired it to the usb port and my temps dropped from 84C to 71C. I had been at 80 on Beta2. Probably a good idea anyway.

Did so too a few months back. Decreased the CPU temp by ~10-15 degrees Celsius

 

[gasparraposo]

Will there be merlin update coming for the AX92U? I really hope its in development. I also hope they fix the dedicated back haul feature for Ai mesh. it sucks.

 

[Blacklistedcard]

Looking at the code snippet from Merlin's recent comment, that seems the intention from asus was for hw v1.0 only.

Beta - Asuswrt-Merlin 386.1 Beta is now available

As I suspected, this was a deliberate change by Asus in a recent GPL merge. @@ -3613,6 +3701,9 @@ void init_others(void) #ifdef GTAC2900 update_cfe_ac2900(); #endif +#if defined(RTAC86U) || defined(GTAC2900) + system("pwr config --wait off"); +#endif #if defined(RTAX88U) ||...

www.snbforums.com

if defined(RTAX88U) || defined(RTAX92U) if(nvram_match("HwVer", "1.0")) { system("pwr config --cpuwait off

I wonder how many hardware version there are for the AX88U?

 

[Vimes]

I wonder how many hardware version there are for the AX88U?

Mine is version 1.1 and produced in 2020, bought mid October of last year. From what little I have noted, within these forums, I only see mine or the first revision being mentioned.