Unfortunately it does, and others will soon find out when attempting the upgrade to 22.03.4 from 22.03.3, unless notified that the outstanding issue is resolved. This should have been incorporated as a localized patch once the issue was reported about a month ago, but the team is waiting for the fix to make it downstream instead.
1 Like
I am well aware of all that, my question is if that commit fixes things?
If so, then its easy to backport
Hi.
No it's a separate problem. When upgrading, the other partition is flashed, but without any previous config. Hence it's not a real upgrade, and the systemp boots with default value. One must manually restore the config after.
Ouch, incoming bricked devices!
Let's hope the devs will post a global message about this in the 22.03.4 release note.
These 23.03.4 images should be pulled from the servers.
1 Like
I compiled master with the patch and my EA6350v3 is now working. It looks like T4keT4ke did the same with an MR8300.
2 Likes
It's not really bricked as the other partition can always be used on the MR8300 (but it's no fun). Also the doc has a warning (for those who read the doc..).
1 Like
Agreed, it was just a matter of fast speaking.
Fun fact : I rewrote the doc in january when the snapshots became available again, after updating kernel to 5.15. 
Does anyone have a working snapshot at the moment or know how to build it?
Or should i rather wait for the fix.
Hi.
I'm presently building from source code. It's rather long but it works. I have a custom build, and I'm awaiting for a build with default official config. I don't know yet how to include the patch, but I'm confidend I'll find soon enough.
Hi
Good news. A commit has been submited for solving both kernels 5.10 (22.03 snapshot) and 5.15 (master).
It may be active in the next daily release.
2 Likes
The fix does not correct the builds on 5.4.238 used in the earlier stable release, only the 5.10.x and 5.15.x cuts but leaves the 21.02.6 broken as well as 22.03.4. All stable releases should incorporate the fjx and then be re-issued in these stable branches. The feeling is if the build does not work, then so sad, if the build bricks it, too bad.
2 Likes
I agree that they shouldn't leave the broken releases on the servers, either correct them or remove them.
Personally, I hope for corrected builds, as we are missing the patches for the vulnerabilities exposed in 22.03.4, and a 22.03.5 release might take a while.
1 Like
Agreed.
I'm wondering if I haven't seen such patch amid all that I browsed. I must confess that I focus on 5.10 (current stable) and 5.15 (future).
I can confirm it works for MR8300
with the
Both my EA8300 and MR8300 now boot with OpenWrt 22.03-SNAPSHOT r20127-074db57936 / LuCI openwrt-22.03 branch git-23.093.57104-ce20b4a
THANK YOU!
2 Likes
Good to know the snapshot number that is working!
Awesome, would this mean the next nightly build is safe to install??
Also will there be a fixed version of 22.03.4 soon
Thanks
OpenWrt 22.03-SNAPSHOT r20127-074db57936 / LuCI openwrt-22.03 branch git-23.093.57104-ce20b4a
2 Likes
But these are eko builds, the official openwrt current snapshot works?