That's odd. I updated to 24.10.1 with no problems.
But if you did it from TFTP recovery, you could have added the recovery image at that point. It's not that hard.
Just go into TFTP recovery again and follow from step 4:
[OpenWrt Wiki] Xiaomi Redmi AX6000
If you read carefully what I wrote, then it does not work.
ubidetach -p /dev/mtd5; ubiformat /dev/mtd5 -y; ubiattach -p /dev/mtd5
detach - does not happen. Suggests to do detach first))).
I understand that theoretically it should work, but in practice it does not work.
The reason you couldn't upgrade to 24.10.1 was because your install was missing fitblk:
I wonder if your issues with TFTP are also due to missing fitblk. Are you using the default files from https://downloads.openwrt.org/? Because they should have fitblk.
All problems are solved.
Indeed, the problem was in this file, since according to the owner of this router, he used it starting from version 23.X and updated it to version 24.10.0 using attendedsysupgrade. Since this file was not included in the assemblies of versions 23.X, and in version 24.X it is advisory in nature and does not have strict dependencies during assembly, it turns out to be due to a bug in OpenWrt itself.
But as I wrote above, it could be solved using TFTP and a recovery image. But formatting and flashing the recovery image directly into the flash could not be solved. Exclusive access was not given for formatting with subsequent flashing of the mtd5 partition. I had to "kill" it by forced flashing of the image openwrt-24.10.1-mediatek-filogic-xiaomi_redmi-router-ax6000-ubootmod-initramfs-factory.ubi, after which the router rebooted itself into recovery mode and waited for the recovery file to be loaded via TFTP.
In this case, it allowed me to reformat the mtd5 and repartition the space for the recovery partition and the main OpenWrt firmware.
That is, the Fitblk file was already in the flash version 24.10.1 at that time and I think in the recovery image as well.
Although I can't imagine how it could affect kmod-mtd-rw.
Most likely, in no way. There must be a less radical way other than deliberately "killing" the router with subsequent recovery))).
I didn't find it, but I did everything that was needed))).
Could someone help me? I have the U-Boot FW layout installed. I installed it when RC1 or RC2 of 23.05 first appeared. The recovery image is still one of those RCs.
I'm currently running version 24.10, which I installed the week it was released via attendedsysupgrade, and it didn't come with the fitblk package.
Even after installing it later via LUCI, there's simply no way to update to 24.10.1 using xiaomi_redmi-router-ax6000-ubootmod-squashfs-sysupgrade.itb
It simply boots into version 24.10, as if nothing had happened.
Honestly, I don't remember how to enter TFTP mode when it is installed in the U-Boot layout, if it is the same procedure as the Redmi stock FW or if there is something specific to OpenWRT that needs to be done.
Even worse, I have no idea what to do if there is something specific related to TFTP if it was customized by the OpenWRT U-Boot layout, because of the minor problems I at least know how the Redmi/Xiaomi TFTP recovery works.
At that time, there was no working Uboot, it is not restored with the help of TFTP. First, update Uboot to the current one and then update what you need from under it.
You can also install the fitblk package right now and then you can update the firmware, but this will not update Uboot. It must be updated manually. Otherwise, if there is a failure, you will get a brick that needs to be restored via UART.
Hi everyone,
I have not touched my Redmi AX6000 firmware since a long time ago. I have my own snapshot derived from OpenWrt 22 (if I am correct) in the stock layout. It has been rock solid and everything works well (including i.e. 160MHz bands).
I have been thinking of finally moving on and installing the Uboot layout with the newest version of OpenWrt. Is there anything I should be aware of? Any issues with the new versions? Any issues with Uboot? I have seen some complaints about the 160MHz bands. Would you suggest upgading, or would you just stay with what I have?
Thanks.
EDIT: Interesting, after changing to Uboot and OpenWrt 24.10.1, it is about 50 mbps slower. On OpenWrt 22 (experimental support snapshot), packet steering and flow offloading, I had about 922 mbps. With OpenWrt 24.10.1 and the same settings, I get about 877 mbps (not limited by CPU).
I managed to update to 24.10.1 from the previously installed version 24.10 U-Boot layout with a problem related to fitblk.
I basically followed the wiki from step 4 and some alterations in the others:
"Installing OpenWrt (U-Boot layout)"
"4. Reboot. It'll boot into initramfs, check mtd partion info. "
detail, I didn't enter the "initramfs-factory" mode, I did it directly in the "normal" version that was running version 24.10 U-Boot layout checking the command "cat /proc/mtd"
I continued with steps 5 -> 6 -> skipped 7 (I already had the volume previously formatted) -> part 8 (only the "ubiupdatevol" command to update the recovery to the latest version -> 9 -> 10
Haven't touched the AX6000 in a long time, struggling to get it updated to the latest stable. I vaguely remember doing a custom partition layout way back when support was added, is there a way to convert it to either stock or ubootmod so I can get it updated?
Current mtd layoud:
root@OpenWrt:/tmp# cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00020000 "BL2"
mtd1: 00040000 00020000 "Nvram"
mtd2: 00040000 00020000 "Bdata"
mtd3: 00200000 00020000 "Factory"
mtd4: 00200000 00020000 "FIP"
mtd5: 00040000 00020000 "crash"
mtd6: 00040000 00020000 "crash_log"
mtd7: 06e00000 00020000 "ubi"
It says the device name is xiaomi,redmi-router-ax6000 if that helps at all, running
OpenWrt SNAPSHOT r21380-5429411f73
fitblk install, or if working Uboot mod install from under it, but it was not working for a long time at that time. Need to update to the current version.
Hello,
I’m running this router with the latest OpenWrt snapshot:
When enabling multiple SSIDs (e.g. 3 per radio / on phy0) each bridged separately (such as br-lan, br-guest, br-automation), I consistently receive the following error in system logs:
hostapd: VLAN: vlan_event_receive: recvfrom failed: No buffer space available
Steps to reproduce:
ssid1, ssid2, ssid3) on the same radio (phy0), each assigned to a different bridge.I confirmed that net.core.rmem_max and wmem_max are already set to 8 MiB, and netdev_max_backlog is at 1000—so buffer limits are not the issue. It appears to be a hostapd / netifd / mt798x driver integration problem where netlink events overflow or mismanage interfaces.
Could you please confirm if you have the same problem?
Please let me know if further logs or dumps would be useful.
Thank you!
Is anyone else having issues with the 5ghz radio not coming up after soft reboots? 2.4ghz works fine and a hard reboot fixes the 5ghz issue so not a huge deal but a little annoying. I’m on the 24.10 branch.
I had an old recovery volume installed, dont remember which version, I have update to latest 24.10.4 itb, running the command:
ubiupdatevol /dev/ubi0_2 /tmp/openwrt-24.10.4-mediatek-filogic-xiaomi_redmi-router-ax6000-ubootmod-initramfs-recovery.itb
I would like to test if the recovery volume is working correctly, how do I trigger the device to boot from that volume?
Another question, I built a custom image using firmware selector and apart from the sysupgrade itb image, it also creates custom preloader.bin and bl31-uboot.fip images. I understand that its not necessary (or even recommended at all) to update those partitions even if they were installed from a pre 24.10 version?
Hey everyone!
I’m currently on 23.05 (U-boot), willing to upgrade to the latest stable. Are there any caveats/problems in the upgrading process that I should know?