Add support for ASUS RT-AX89X AX6000

No, I didn't need to modify the source, I was planning to write a service script which would disable the automatic control and manage the fan based on temperature readings.

Then I would have installed enabled that service after each update.

Hmm... so the modes are writable?
I have been trying to write to a bunch of things, nothing seems to stick.

Modes are writable, yes. But yeah, my script detects correct location in hwmon, since that can change after each boot.

You can find it using something like this:

fan_hwmon_pattern='*/gpio-fan/*'
hwmon_glob='/sys/class/hwmon/hwmon*'

configure() {
  local hwmon=''
  for hwmon in $hwmon_glob; do
    hwmon_path=$(readlink -f $hwmon)

    if [[ "$hwmon_path" == "$fan_hwmon_pattern" ]]; then
      fan_hwmon_path=$hwmon_path
    fi
  done
}

which gives you fan_hwmon_path

1 Like

That would be useful for the fan control script. I'll add it and also add the mode change every time it starts up.
So 'disabled' will turn the zone off?

Fan Control script is running, just for testing now:

I might get to finishing my script and will post it on Gitlab somewhere. That would be easier probably.

1 Like

Do you mind if I use your code snippets to make a merged script?

Sure, you can use the above or wait until I post a full version. Those could be placed in /etc/init.d/... to be used as services.

I'm done with the script, its running.
Needed to make some minor modifications to your code, but other than that it seems to work fine.
Will post it on github tomorrow.

Edit: Or ill do it now.
https://github.com/NotANewNick/ASUS-RT-AX89X-OpenWRT-Fan-Control

2 Likes

This router is in a fairly warm room, so its a bit hotter than normal.
Script is still running and it seems to be keeping it cool enough.

1 Like

Ok, so there is some stuff.

When adding a Wifi AP, at least for the 5Ghz, it does not automatically add a device in the device list. So you cant really make a connection to the br-lan.
You will need to manually add the device in the list
Here you can see the interface name:

Here is where you input it for br-lan, Green arrow is how it will look after you added it, red arrow is where you input the interface name from the above image:

This seems to work automatically for 2.4Ghz, but I am verifying it still.

This is a bit interesting, didn't see this on the other router.


Stuck again, how fun :smiley:
Never mind..... dumb ... wifi is turned off.

Edit:
Both my B2 routers are now flashed.
There are some issues with the initial setup of the 5GHz network, one is sad.
Initially it shows that the signal power is 1W(!), but if you try to use it then you quickly see that bad things start to happen.
The only way I was actually able to get 5GHz to work reliably was to reset the interface config and change the security prototcol to something new.

My ASUS RT-AX89X was bootlooping. It was working fine for few months (both physical and WiFi connections). The '.trx' debricking method didn't work for me. But this '.itb' method worked.

Now, when I reconfigure the device and enable/add the WiFi, it bootlooping again. Any idea?

UART console logs:

Saw this, not sure if its an issue. Perhaps its worth checking?

Cannot parse config file '/etc/fw_env.config': No such file or directory

Crash seems to start here:

[   20.759427] qcom-q6v5-wcss-pil cd00000.q6v5_wcss: fatal error received: 
[   20.759427] QC Image Version: QC_IMAGE_VERSION_STRING=WLAN.HK.2.9.0.1-02146-QCAHKSWPL_SILICONZ-1
[   20.759427] Image Variant : IMAGE_VARIANT_STRING=8074.wlanfw.eval_v2Q

Have you tried to flash the OEM image?

I've tried OEM image using both TFTP and ASUS Firmware Restoration method. But the device still bootlooping.

TFTP UART serial console logs:

ASUS Firmware Restoration UART serial console logs:

ASUS Firmware Restoration screenshots:


Any idea what's wrong and how to fix this?

You must try load asus_rt-ax89x-initramfs-factory.trx from https://downloads.openwrt.org/releases/24.10.0-rc7/targets/qualcommax/ipq807x/

1 Like

asus_rt-ax89x-initramfs-factory.trx worked. But when Luci web UI is ready, I uploaded sysupgrade.bin image file and it bootloop again.

Thoughts?

I re-downloaded sysupgrade image from https://downloads.openwrt.org/releases/24.10.0-rc7/targets/qualcommax/ipq807x/ and retry - it worked this time.

Renamed the WiFi SSIDs and reboot the device - everything looks normal so far.

I will report back if I face similar issues. Thanks for your help.

1 Like

I think I know what's causing the boot loop issue. When I add third SSID under Qualcomm Atheros IPQ8074 802.11ax/b/g/n radio, my ASUS RT-AX89X B2 crashed and entered boot loop phase.

The only way for me to use the device again is by going through the ".trx → sysupgrade flash process" all over again and limit the number of SSIDs under 802.11ax/b/g/n radio to just two maximum.

Interestingly, Qualcomm Atheros IPQ8074 802.11ac/ax/n radio works fine with >= 3 SSIDs. So, something isn't right here with 802.11ax/b/g/n radio.

Having multiple SSIDs per radio support is critical for me because I have multiple VLANs/interfaces/firewalls. My setup is quite similar to this.

While doing some research, I found this issue. But my /etc/config/wireless file does not contain any “option macaddr” lines.

Is this a bug in the code?

Other build/target references (GitHub issue & PRs):

Perhaps you can sort this with the same SSID and sort things by IP with MWAN?
Or just give different Subnets to different MACs via DHCP and sort it in the firewall that way?

Thanks. But that’s not an option for now.

Can someone confirm this? Is it just me? Is it a bug in the code?