there is no difference, it keeps what sysupgrade -l shows. Add your script files paths to /ets/sysupgrade.conf if not yet included. Also same config is used for config backup tarball.
firmware-selector and imagebuilder locally are different tjat they do not apply package deprecations like firewall is not substituted by fitewall4
1 Like
Upgraded GL.iNET GL-MT6000 successfully. The batman-adv mesh network is still incompatible with VLAN-aware bridging.
Netgear WAX202 also works as a mesh point after the upgrade.
Upgraded my NanoPi R5C last night via owut and everything seems to be working fine as of this morning.
Upgrade my phicomm k2g from openwrt 24.10.1 to 24.10.2 successful.
In addition to the home routers, I just also updated my 2 travel routers (Cudy TR3000, GL-MT1300) without issues. Very smooth release so far!
Update by 3 ssh commands:
opkg update
opkg install owut
owut upgrade
The update worked perfect on the WAX202 and the GL.Inet GL-MT6000. Kept my settings and all installed packages.
8 Likes
i have installed 24.10.2 on my tplink tlwa1201 and 5g wifi donĀ“t work...anyone knows why? this will be fixed in the near future? thanks
Have you tried to plug it off completely? I had similar situation in the past after upgrading AX3200 - 5GHz didn't initialize.
unplug from power you say? from the first 24.10 rc to the atual 24.10.2 it didĀ“t recognize 5g chip. but i will try that! thanks
In this case it will not help I'm sure. I'm not familiar with your hardware. I'm just telling about mine with similar symptoms. Probably some HW initialization issue just like with HW offloading chip being not initialized properly and items survining simple reboot in builtin memory.
Man, that owut developer must be a really cool dude. He's a genius! 
Back on topic. Besides my two RT3200s, I also did owut upgrade to my GF's Redmi AC2100 and Mi 4A 100M International; also updated a crappy Comfast CF-WR758AC V2 I have laying around. All devices updated just fine.
Thanks again to all the community.
4 Likes
My MikroTik Hex S is not happy upgrading from 24.10.1. It tells me Config cannot be migrated from swconfig to DSA. I get the same error with owut upgrade and when I call sysupgrade with a downloaded image file
# owut download
ASU-Server https://sysupgrade.openwrt.org
Upstream https://downloads.openwrt.org
Target ramips/mt7621
Profile mikrotik_routerboard-760igs
Package-arch mipsel_24kc
Version-from 24.10.1 r28597-0425664679 (kernel 6.6.86)
Version-to 24.10.2 r28739-d9340319c6 (kernel 6.6.93)
101 packages are out-of-date
Request hash:
cd58c6cf63494d2f23476dcf8c03f58806f01b0c54fbfb32cbad4a6f003e75bf
--
Status: done
Progress: 0s total = 0s in queue + 0s in build
Build succeeded in 0s total = 0s in queue + 0s to build:
Image saved : /tmp/firmware.bin
ERROR: sysupgrade validation failed:
stderr =
Wed Jun 25 09:41:03 EDT 2025 upgrade: The device is supported, but this image is incompatible for sysupgrade based on the image version (2.0->1.1).
Wed Jun 25 09:41:03 EDT 2025 upgrade: Config cannot be migrated from swconfig to DSA
Image check failed.
# ubus call system board
{
"kernel": "6.6.86",
"hostname": "OpenWrt",
"system": "MediaTek MT7621 ver:1 eco:3",
"model": "MikroTik RouterBOARD 760iGS (hEX S)",
"board_name": "mikrotik,routerboard-760igs",
"rootfs_type": "squashfs",
"release": {
"distribution": "OpenWrt",
"version": "24.10.1",
"revision": "r28597-0425664679",
"target": "ramips/mt7621",
"description": "OpenWrt 24.10.1 r28597-0425664679",
"builddate": "1744562312"
}
}
mt7621 has been migrated to DSA a long time ago (21.02). This message is indeed weird.
I like living on the edge. All units updated on a weekly basis to latest SNAPSHOT - everything is working just fine 
Yeah, especially since I upgraded successfully from 24.10.0 to 24.10.1 successfully.
1 Like
Upgraded my Dynalink DL-WRX36 to v24.10.2 using the Attended Upgrade (luci interface) and running smoothly. Why did I not know about this feature earlier! So simple and literally took <2 minutes of downtime. Fantastic work by all!
1 Like
Upgraded from 24.10.1 to 24.10.2 with owut upgrade on
TP-Link Archer C2600,
ASUS Lyra MAP-AC2200 and
Zyxel T-56 (Model shown in luci: Zyxel EX5601-T0 ubootmod)
No problems so far.
It looks like something messed with your system compatibility level, or maybe it leaked through from a previous upgrade???
If you're sure that you've already done the jump to DSA (apparently so, if it's working ok with 24.10.1), just edit the compat_version in /etc/config/system, setting it to 2.0. Or probably easier, just uci set it.
uci set system.@system[0].compat_version=2.0
uci commit
1 Like
Please, tell my wife that, she often indicates otherwise. 
16 Likes
I already have this in my /etc/config/system:
# head /etc/config/system
config system
option hostname 'OpenWrt'
option ttylogin '0'
option log_size '64'
option urandom_seed '0'
option compat_version '2.0'