ASUS RT-AX89U does not exist - the name is a U-Boot banner string (#841) #1201

Merged
jaylouisw merged 1 commit from feat/asus-rt-ax89u into main 2026-11-09 12:54:33 +00:00
Owner

Request #841 asks for the RT-AX89U, "the actual router model", on the grounds that the catalogue only has RT-AX89X. The catalogue is right and the request is chasing a bootloader.

The string is real, but it is not a SKU: in rescue mode this board prints RT-AX89U bootloader version. The forum thread that follows that string ends with the original poster correcting himself - "it is indeed the RT-AX89X ... muscle memory from typing other ASUS models made me write U by mistake". ASUS lists the 12-stream AX6000 router with the 10GBASE-T port and the SFP+ cage as RT-AX89X in every region it sells in; there is no RT-AX89U product page, datasheet or firmware because there is no RT-AX89U.

So nothing was added - a phantom SKU is worse than a missing one, because every later cross-check against it inherits the error. The existing entry already carries the spec sheet: 1x 1G WAN, 8x 1G LAN, one 10GBASE-T and one SFP+ 10G port, AX6000 with 8x8 on 5 GHz.

What changed is the note on devices/asus/rt-ax89x.json, so the next person to search that string lands on the answer instead of filing this again.

Request #841 asks for the RT-AX89U, "the actual router model", on the grounds that the catalogue only has RT-AX89X. **The catalogue is right and the request is chasing a bootloader.** The string is real, but it is not a SKU: in rescue mode this board prints `RT-AX89U bootloader version`. The forum thread that follows that string ends with the original poster correcting himself - *"it is indeed the RT-AX89X ... muscle memory from typing other ASUS models made me write U by mistake"*. ASUS lists the 12-stream AX6000 router with the 10GBASE-T port and the SFP+ cage as **RT-AX89X** in every region it sells in; there is no RT-AX89U product page, datasheet or firmware because there is no RT-AX89U. So nothing was added - a phantom SKU is worse than a missing one, because every later cross-check against it inherits the error. The existing entry already carries the spec sheet: 1x 1G WAN, 8x 1G LAN, one 10GBASE-T and one SFP+ 10G port, AX6000 with 8x8 on 5 GHz. What changed is the **note on `devices/asus/rt-ax89x.json`**, so the next person to search that string lands on the answer instead of filing this again.
ASUS RT-AX89U does not exist - the name is a U-Boot banner string
All checks were successful
CI / Classify the change (pull_request) Successful in 11s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 11s
CI / Test (Node 18) (pull_request) Successful in 1m44s
CI / Test (Node 20) (pull_request) Successful in 1m44s
CI / Server smoke test (pull_request) Has been skipped
CI / Docker build (pull_request) Has been skipped
CI / Test (Node 22) (pull_request) Successful in 1m28s
592c793ead
Request #841 asks for the RT-AX89U "the actual router model, catalogue only has RT-AX89X". The
catalogue is right and the request is chasing a bootloader.

The string is real but it is not a SKU: in rescue mode this board prints "RT-AX89U bootloader
version". The forum thread that follows that string ends with the original poster correcting
himself - "it is indeed the RT-AX89X ... muscle memory from typing other ASUS models made me write
U by mistake". ASUS's own site lists the 12-stream AX6000 router with the 10GBASE-T port and the
SFP+ cage as RT-AX89X in every region it sells in. There is no RT-AX89U product page, datasheet or
firmware download because there is no RT-AX89U.

So nothing is added: a phantom SKU in the catalogue is worse than a missing one, because every
later cross-check against it inherits the error. The existing entry already carries what the spec
sheet says - 1x 1G WAN, 8x 1G LAN, one 10GBASE-T and one SFP+ 10G port, AX6000 with 8x8 on 5 GHz.

What changed is the note, so the next person to search for that string lands on the answer instead
of filing the same request again.
jaylouisw scheduled this pull request to auto merge when all checks succeed 2026-11-09 12:54:31 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaylouisw/packetforge!1201
No description provided.