@hnyman@anomeome-
i've doen more testing of old build versions i could recover.
builds (ad date downloaded) in which sysupgrade works correctly both from part 1->2 and 2->1:
r26300, 6/2/24
26657, 6/8/24
26608, 6/12/24
26912, 7/10/24
26928, 7/12/24
26955, 7/17/24
builds which fail 20>1:
26775, 6/24/24
26993, 7/25/24
27110, 8/11/24
this interval from 6/24- 7/25 corresponds to kernel version commits, but also to the shift from auc to owut, and come changes to ubus calls were made as part of this. specifically,
in which @daniel and @psherman are discussing plans for ucode changes for sysupgrade, and
in which owut made it into snapshot on 6/25/24.
there was subsequent discussion about sysupgrade failing in
curiously, luci-advanced-reboot stoped being able to decode the openwrt version in the other partition during this time interval also.
so i wonder if 'something' the complex sysupgrade-ucode logic is borked for the wrt32x/venom series?
this sysupgrade issue on wrt32x has been confiormed by at least one other user in the issues git:
thanks all
to the orinal poster - this thread has been hijacked, but you should pay attention because current snapshots will likely create sysupgrade problems for you until addressed.