1929

This patch is fully functional and can be added to the official 23.XX branch and snapshot.
The firmware compiled with this patch has been working on a router with Winbond and OpenWrt U-Boot layout for the second day without any problems.

1 Like
1930

First time OpenWRT user here, I've set up one AX3000T as the dumb router and the other as the main one, everything is working fine with VLANs, Guest and IOT networks and fast roaming. There's two things that I need explanation:

  1. I've heard this device's hardware has some limits, so I can't just add every single software that might be useful. How do you know if you passed that threshold? Just keep looking at LUCI's and see if ram is totally used, or is there a proper test to stress the network and see if something pops out?

  2. My sister's phone only has 2.4ghz, and I found that for some weird reason it can't connect to networks that have the same SSID as a 5ghz one. Why is that? My old PC also only has 2.4ghz and it works fine, so what gives?

1931

Try changing the 2.4 GHz interface from AX to N.

2 Likes
1932

I had prpblem with my AX3000T (RD03 with ESMT NAND, that came with 1.0.47 FW) today. Out of nowhere (maybe after scheduled reboot that I set weekly), it stopped working and orange LED was blinking slowly (blinked every few seconds). Wifi was not active and when connected to LAN, I didn't get IP and Windows also slowed that cable got disconnected every few seconds.
Unplugging/replugging power nor pressing or holding reset button didn't help.
I had to use MiWifiRepairTool to flash 1.0.47 and switch to OpenWRT again, which fixed it.
I was on official 23.05.5 OpenWRT with stock bootloader.
Any ideas what could happen?

1933

ideas - there are.
Soft brick after 7 reboots.

  1. The openWrt team needs to apply a patch that fixes this problem.
  2. Read the topic and register a command in the auto boot that fixes this problem.
  3. Install a custom bootloader and the corresponding openWrt firmware for it.
1 Like
1934

As I see PR has been merged to the 23.05 branch

Please install ‘ubootmod-type’ firmware only with the bootloader from the snapshot or my build if your spi-nand by Winbond (Winbond chip support in the OpenWrt bootloader is available there).

This commit should be merged into the 23.05 branch to support the Winbond chip for ubootmod-type firmware (OpenWrt bootloader).

2 Likes
1935

how about AN8855 variant?

1 Like
1936

what does the merge do? does that mean we can use official release instead of snapshots for the ax3000t with winbond nands?

1937

Yes, I noticed some messages about resetting the counter before, but I had feeling that it is required just on newer routers with newer Xiaomi bootloader, so didn't pay much attention to it.
I added fw_setenv flag_try_sys1_failed 0 to /etc/rc.local as precaution, hopefully it will prevent this from happening again...

1938

Continue to look for alternative build, an8855 not supported in the official repository, until drivers for this switch will not be present in the Linux kernel.

Driver for the Winbond chip have been added to the 23.05 branch for firmware support, but no changes have been made to the OpenWrt booloader (OpenWrt layout - ubootmod) in the 23.05.

Upd
See last comments by the link

1 Like
1939

I'm testing AX3000T on a restaurant for future network upgrade, but a've noticed poor speeds on 5GHz ramdomly, solved with radio restart, but when it occours, the network goes down due to low speed/high latency.

The AP is running on 80MHz/AX mode.
Openwrt 23.05.5.

Screenshot_20241019-203131_Chrome~2
Screenshot_20241019-203131_Chrome~21080×2400 319 KB

Screenshot_20241020-195607_Speedtest
Screenshot_20241020-195607_Speedtest1080×2400 137 KB

1940

Try turning hardware flow offloading off (just leave software flow offloading on). Crappy 5 GHz performance seems to occur on some phones for me, when hardware flow offloading is enabled, but not on a laptop.

1941

Replace the wpad-basic-mbedtls package in the firmware with wpad-wolfssl.

1 Like
1942

tried to install ubootmod, but have issue with wireless settings and devices. creating '/etc/config/wireless' has no effect, and dmesg has such errors

[    7.052493] mt798x-wmac 18000000.wifi: HW/SW Version: 0x8a108a10, Build Time: 20221208201745a
[    7.052493] 
[    7.283501] mt798x-wmac 18000000.wifi: WM Firmware Version: ____000000, Build Time: 20221208201806
[    7.398783] mt798x-wmac 18000000.wifi: WA Firmware Version: DEV_000000, Build Time: 20221208202048
[    7.490847] mt798x-wmac 18000000.wifi: eeprom load fail, use default bin
[    7.497895] mt798x-wmac 18000000.wifi: Direct firmware load for mediatek/mt7981_eeprom_mt7976_dbdc.bin failed with error -2
[    7.509281] mt798x-wmac 18000000.wifi: Falling back to sysfs fallback for: mediatek/mt7981_eeprom_mt7976_dbdc.bin
[    7.570866] mt798x-wmac: probe of 18000000.wifi failed with error -12

maybe someone stumbled upon same issue and know how to solve it ?

1943

restore from backup to factory state and then flash again. You killed the section with WiFi module calibrations and most likely your MAC address does not match the sticker on the router.

1944

thx
btw after writing question i found KhetagAb solution

1945

so does that mean i can update using the official 23.05 firmware instead of snapshots?

or do i need to wait for next release?

1 Like
1946

Just a public service announcement: I bought one last month and I bought one last week from the same seller on Aliexpress. First one that came in was an RD03/Winbond (fw: 1.0.47), second one RD03/ESMT. (Will edit this later to add the fw version they came with, but the Winbond one came with the right fw for owrt upgrading).

Last month I wasn't aware of the 7 boot brick, so I guess I'll have to get them both up to date properly. Will dig through here for a while, thanks for all your efforts!

1 Like
1947

Offload don't make any change, bug occurred with and without offload enabled.

1948

I've changed the package and will test.
The CPU usage is higher, 50% CPU usage with NAT.