Asus TUF Gaming AX6000 support

For Developers
740

Its happened again. The wan interface down (no internet ip address) and impossible to restart

Here is the log :

Mon Apr 29 16:30:59 2024 kern.warn kernel: [149128.074860] ------------[ cut here ]------------
Mon Apr 29 16:30:59 2024 kern.info kernel: [149128.079571] NETDEV WATCHDOG: eth1 (mtk_soc_eth): transmit queue 1 timed out
Mon Apr 29 16:30:59 2024 kern.warn kernel: [149128.086627] WARNING: CPU: 0 PID: 0 at 0xffffffc0086c46d4
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.092012] Modules linked in: pppoe ppp_async nft_fib_inet nf_flow_table_ipv6 nf_flow_table_ipv4 nf_flow_table_inet ebtable_nat ebtable_filter ebtable_broute pppox ppp_generic nft_reject_ipv6 nft_reject_ipv4 nft_reject_inet nft_reject nft_redir nft_quota nft_objref nft_numgen nft_nat nft_masq nft_log nft_limit nft_hash nft_flow_offload nft_fib_ipv6 nft_fib_ipv4 nft_fib nft_ct nft_counter nft_chain_nat nf_tables nf_nat nf_flow_table nf_conntrack mt7915e mt76_connac_lib mt76 mac80211 iptable_mangle iptable_filter ipt_REJECT ipt_ECN ip_tables ebtables ebt_vlan ebt_stp ebt_redirect ebt_pkttype ebt_mark_m ebt_mark ebt_limit ebt_among ebt_802_3 cfg80211 xt_time xt_tcpudp xt_tcpmss xt_statistic xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_ecn xt_dscp xt_comment xt_TCPMSS xt_LOG xt_HL xt_DSCP xt_CLASSIFY x_tables slhc sch_cake nfnetlink nf_reject_ipv6 nf_reject_ipv4 nf_log_syslog nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c compat crypto_safexcel sch_tbf sch_ingress sch_htb sch_hfsc
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.092159]  em_u32 cls_u32 cls_route cls_matchall cls_fw cls_flow cls_basic act_skbedit act_mirred act_gact ifb sha1_generic seqiv md5 des_generic libdes authencesn authenc leds_gpio xhci_plat_hcd xhci_pci xhci_mtk_hcd xhci_hcd gpio_button_hotplug usbcore usb_common aquantia crc_ccitt
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.204349] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.15.150 #0
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.210511] Hardware name: ASUS TUF-AX6000 (DT)
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.215109] pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.222136] pc : 0xffffffc0086c46d4
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.225695] lr : 0xffffffc0086c46d4
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.229253] sp : ffffffc008003db0
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.232637] x29: ffffffc008003db0 x28: 0000000000000140 x27: 00000000ffffffff
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.239840] x26: 0000000000000000 x25: 0000000000000000 x24: ffffff8000d704c0
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.247042] x23: 0000000000000000 x22: 0000000000000001 x21: ffffffc008a36000
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.254244] x20: ffffff8000d70000 x19: 0000000000000001 x18: ffffffc008a4a2a8
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.261446] x17: ffffffc01746f000 x16: ffffffc008000000 x15: 0000000000000def
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.268647] x14: 00000000000024a5 x13: ffffffc008003ae8 x12: ffffffc008aa22a8
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.275849] x11: 0000000000032db8 x10: 0000000000032d78 x9 : 0000000000006f78
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.283051] x8 : ffffffc008a4a258 x7 : ffffffc008a4a2a8 x6 : 0000000000000001
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.290252] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.297455] x2 : 0000000000000040 x1 : 0000000000000004 x0 : 000000000000003f
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.304657] Call trace:
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.307176]  0xffffffc0086c46d4
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.310388]  0xffffffc0080a5c50
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.313601]  0xffffffc0080a64c8
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.316812]  0xffffffc0080a6e18
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.320024]  0xffffffc0080102bc
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.323235]  0xffffffc00803b280
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.326446]  0xffffffc00803b3a0
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.329657]  0xffffffc008089564
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.332869]  0xffffffc0080100e0
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.336081]  0xffffffc00801584c
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.339293]  0xffffffc00801614c
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.342505]  0xffffffc008834770
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.345717]  0xffffffc008834f24
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.348928]  0xffffffc008011374
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.352140]  0xffffffc008835504
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.355352]  0xffffffc008069390
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.358564]  0xffffffc0080695a4
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.361776]  0xffffffc0088358a4
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.364989]  0xffffffc0089c0954
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.368200]  0xffffffc0089c0f20
Mon Apr 29 16:30:59 2024 kern.debug kernel: [149128.371411]  0xffffffc0089c034c
Mon Apr 29 16:30:59 2024 kern.warn kernel: [149128.374624] ---[ end trace 8bcc21244dd34b06 ]---
Mon Apr 29 16:30:59 2024 kern.err kernel: [149128.379328] mtk_soc_eth 15100000.ethernet eth1: transmit timed out
Mon Apr 29 16:31:00 2024 kern.info kernel: [149128.517721] mtk_soc_eth 15100000.ethernet eth0: Link is Down
Mon Apr 29 16:31:00 2024 kern.info kernel: [149128.523488] mtk_soc_eth 15100000.ethernet eth1: Link is Down
Mon Apr 29 16:31:00 2024 kern.err kernel: [149129.054755] mtk_soc_eth 15100000.ethernet: warm reset failed
Mon Apr 29 16:31:00 2024 kern.info kernel: [149129.073780] mtk_soc_eth 15100000.ethernet eth0: configuring for fixed/2500base-x link mode
Mon Apr 29 16:31:00 2024 kern.info kernel: [149129.082275] mtk_soc_eth 15100000.ethernet eth0: Link is Up - 2.5Gbps/Full - flow control rx/tx
Mon Apr 29 16:31:00 2024 kern.info kernel: [149129.082727] mtk_soc_eth 15100000.ethernet eth1: PHY [mdio-bus:06] driver [Maxlinear Ethernet GPY211C] (irq=POLL)
Mon Apr 29 16:31:00 2024 kern.info kernel: [149129.101207] mtk_soc_eth 15100000.ethernet eth1: configuring for phy/sgmii link mode
Mon Apr 29 16:31:00 2024 daemon.notice netifd: Network device 'eth1' link is down
Mon Apr 29 16:31:00 2024 daemon.notice netifd: Interface 'wan' has link connectivity loss
Mon Apr 29 16:31:00 2024 daemon.notice netifd: wan (11861): udhcpc: received SIGTERM
Mon Apr 29 16:31:00 2024 daemon.notice netifd: wan (11861): udhcpc: unicasting a release of xx.xx.xx.xx to xx.xx.xx.xx
Mon Apr 29 16:31:00 2024 daemon.notice netifd: wan (11861): udhcpc: sending release
Mon Apr 29 16:31:00 2024 daemon.notice netifd: wan (11861): udhcpc: entering released state
Mon Apr 29 16:31:00 2024 daemon.notice netifd: wan (11861): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "wan" } (Permission denied)
Mon Apr 29 16:31:00 2024 daemon.notice netifd: Interface 'wan' is now down
Mon Apr 29 16:31:01 2024 daemon.warn dnsmasq[1]: no servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
Mon Apr 29 16:31:01 2024 user.warn igmpproxy[4982]: select() failure; Errno(4): Interrupted system call
Mon Apr 29 16:31:03 2024 kern.info kernel: [149132.231727] mtk_soc_eth 15100000.ethernet eth1: Link is Up - 1Gbps/Full - flow control rx/tx
Mon Apr 29 16:31:03 2024 daemon.notice netifd: Network device 'eth1' link is up
Mon Apr 29 16:31:03 2024 daemon.notice netifd: Interface 'wan' has link connectivity
Mon Apr 29 16:31:03 2024 daemon.notice netifd: Interface 'wan' is setting up now
Mon Apr 29 16:31:03 2024 daemon.notice netifd: wan (15432): udhcpc: started, v1.36.1
Mon Apr 29 16:31:03 2024 daemon.notice netifd: wan (15432): udhcpc: broadcasting discover
Mon Apr 29 16:31:06 2024 daemon.notice netifd: wan (15432): udhcpc: broadcasting discover
Mon Apr 29 16:31:10 2024 daemon.notice netifd: wan (15432): udhcpc: broadcasting discover

Every time i restart the wan interface :

Mon Apr 29 17:13:55 2024 daemon.notice netifd: wan (19899): udhcpc: received SIGTERM
Mon Apr 29 17:13:55 2024 daemon.notice netifd: wan (19899): udhcpc: entering released state
Mon Apr 29 17:13:55 2024 daemon.notice netifd: wan (19899): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "wan" } (Permission denied)
Mon Apr 29 17:13:55 2024 daemon.notice netifd: Interface 'wan' is now down
Mon Apr 29 17:13:55 2024 daemon.notice netifd: Interface 'wan' is setting up now
Mon Apr 29 17:13:55 2024 daemon.notice netifd: wan (21298): udhcpc: started, v1.36.1
Mon Apr 29 17:13:55 2024 daemon.notice netifd: wan (21298): udhcpc: broadcasting discover
Mon Apr 29 17:13:59 2024 daemon.notice netifd: wan (21298): udhcpc: broadcasting discover
Mon Apr 29 17:14:02 2024 daemon.notice netifd: wan (21298): udhcpc: broadcasting discover```

Only reboot solve this problem.
741

Seems a known problem :

According to one comment its already happened on : Asus TUF AX4200

I found a temporarily solution in #13262
using the ethtool -K eth0 tso off command, the timeout did not appear. Now my uptime is: 5d 8h 52m 55s

I'll see if its happened again with : ethtool -K eth1 tso off

1 Like
742

Hi @feneri25 ,

How did you fix this? I've the same problem.
With Asus restoration tool i flashed Asus rom, bring back the router to life. Flashed openwrt trx and openwrt sysupgrade.bin

But both radio0 and radio1 staying 5ghz.

743

I had this exact same problem: Asus TUF Gaming AX6000 support - #638 by f0ff886f

I never found a proper workaround :frowning: I ended up migrating the routing for my home network to a VM running on Proxmox, and I only use the AX6000 as a WAP for the wired network. It works fine there, no issues, but I'm not using eth1 at all.

744

It seems to solve the problem. That's the antidote.
Since I ran the command yesterday, I haven't had a crash on the wan interface, before that I had crashes every day since I bought this router with openwrt.
Its an very old problem (2017)
i put 2 links about it above.

1 Like
745

hi @Supergroover, I didn't have time to look into this, but @Andry772 had the same problem and restoring MTD1 from someone else's dump resolved his case.

Could somone please upload their AX6000 MTD1 dump using the command below?

dd if=/dev/mtd1 of=/tmp/mtd1 bs=10M

In case any other modification would be needed to retain e.g. MAC please let us now, hope simply writing it back will be enough.

Thanks in advance!

2 Likes
746

I dumped the file and here is the raw format:

mtd1

root@OpenWrt:/dev# ubus call system board
{
	"kernel": "5.15.150",
	"hostname": "OpenWrt",
	"system": "ARMv8 Processor rev 4",
	"model": "ASUS TUF-AX6000",
	"board_name": "asus,tuf-ax6000",
	"rootfs_type": "squashfs",
	"release": {
		"distribution": "OpenWrt",
		"version": "23.05.3",
		"revision": "r23809-234f1a2efa",
		"target": "mediatek/filogic",
		"description": "OpenWrt 23.05.3 r23809-234f1a2efa"
	}
2 Likes
747

Thanks Anton, you're a star!
I'm away for 2 weeks, but I downloaded the file and will use after my return. I'm looking forward to sell the Xiaomi AX3600 it was supposed to replace.
Hope it will help @Supergroover too.

748

Do I still need to rename the file to mtd1.bin?
Should I just follow the steps below?

SCP mtd1 file to /tmp

mtd -r write /tmp/mtd1 mtd1
749

above my knowledge unfortunately, @feneri25 might have more knowledge?

750

Oke, Thanks for your help :+1:t4:

1 Like
751

Do you see any difference between the stock firmware and OpenWRT WiFi range?

752

@remittor or @patrykk seem to be the most experienced, they adviced Andry772 too on how to restore such broken eeprom. We have broken wifi data as in previous case. Wifi works with stock/trx image, but is gone after sysupgrade. Kernel log shows failing eeprom load.

Not sure if beside writing back mtd1 from someone else's router will be enough to restore eeprom or also copies of factory1/factory2 volumes would be needed or any other modification would be needed. Thanks!

753

Thanks Patrykk, I managed to get around 150MB/s up and down with Samba 4, with the synchronous I/O and extra tuning options and a 2.5Gbe connection.
I'm getting much better results with Samba 4 compared to ksmbd.

I couldn't test nfsd on my ssd as it's formatted in exfat but I seem to get slightly better results with Samba 4 on my hdd formatted in ext4 compared to nfs and ksmbd,

2 Likes
754

I restored two factory and MTD1 partitions. Mac remained like a donors.

1 Like
755

Try to manually add dns to LAN and See if it helps

756

Already tried. I even tried reflashing to stable version (gotten from image builder site) and while that worked initially, I stopped working again after a little bit.

757

Can I somehow help to dump the factory volumes? In that case, where do I find these?

758

I found out how to download the files:

factory

factory2

root@OpenWrt:/dev# ubus call system board
{
	"kernel": "5.15.150",
	"hostname": "OpenWrt",
	"system": "ARMv8 Processor rev 4",
	"model": "ASUS TUF-AX6000",
	"board_name": "asus,tuf-ax6000",
	"rootfs_type": "squashfs",
	"release": {
		"distribution": "OpenWrt",
		"version": "23.05.3",
		"revision": "r23809-234f1a2efa",
		"target": "mediatek/filogic",
		"description": "OpenWrt 23.05.3 r23809-234f1a2efa"
	}

Ping @Supergroover @feneri25

2 Likes
759

I open a bug https://github.com/openwrt/openwrt/issues/15304 regarding the lan ports don't work as expected. And I also created a pull request with a solution https://github.com/openwrt/openwrt/pull/15353