OpenWrt 24.10.0-rc6 - Sixth Release Candidate

Try to clear browser cache. See whether that helps. Does seem weird though.

1 Like

Netgear WAX206: Built custom image replacing mbedtls with libwolfssl-cpucrypto. Everything works except "WPA3-SAE" security choice which results in wifi AP never coming up, and also get the same results when I have 160mhz selected as well.
I confirmed this by waiting around 5 minutes and checking with a wifi analyzer app.

Edit:
After deleting the wireless config and regenerating it with "wifi config" I was able to get SAE to work with no problems. 160mhz still doesn't seem to work.

No issues so far on Archer C7 v2 using a custom image built with the image builder. But on rc5 both Wi-Fi ifaces randomly went down at least once.

Flashing of the OpenWrt One using owut is working correctly now. Thank you.

1 Like

Nah, with save settings

Try owut between the two versions and see if it works

Should be fixed for all targets as of about 2025-01-24 0900 UTC. Please report if you see otherwise.

PR merged and also a change to ASU server has been merged (belt and suspenders), so all ASU clients should be showing the 24.10.0-rc6 available. Specifically, the LuCI Attended Sysupgrade app should show that version for anyone using 23.05 or 24.10 versions.

Note that the LuCI app won't migrate you from SNAPSHOT to a release branch, for that you need to use owut or Firmware Selector (and when doing so, be careful of config changes).

2 Likes

Means in-kernel rng found hardware events do not generate random enough data. Just that new kernel tests rng and rejects if not random. Use haveged if ronning https server etc.

1 Like

That was the first thing I tried. I always flash and first login a new build in incognito mode anyway so no cache.

Edit: I just tried from my iphone instead of PC and the menu item is there. Wtf? My browsers are Chrome 132 ingnonito, and iOS 18.2.1 Chrome which uses Apple webkit embedded I think (not Chromium on iPhone I believe). Anyway no matter what I do All CPU menu item is not available on my desktop browser just my phone.

1 Like

Working well on my raspberry pi's and Fritzbox 4040, also working great on my x86_64 fanless router board.

As an avid Alpine user I am stoked with apk, it is by far one of the best package managers.

(When running Alpine you can even downgrade the whole system and/or sync all packages to a certain release. Config files might break but the system will be fine. It is really robust.)

Fine on NanoPi R3S

1 Like

Upgraded my NanoPi R5C from rc5 via owut last night with no issues. Works great.

I have all the options for packet steering on there.

3 Likes

Updated my bananapi r4 from rc4 to rc6 via owut. No problems so far

Upgraded:

  • Netgear WAX206
  • Buffalo WZR-HP-AG300H
  • QEMU KVM x86_64 squashfs-combined-efi

from rc5, no new regressions. The regression (not present on 23.05.5) observed on the two physical devices where 802.11s interfaces falsely report encryption as None instead of WPA3-SAE is still present.

1 Like

Successfully upgraded gl-mt6000 rc5->rc6.
No apparent issues so far.

2 Likes

This message appeared on my Zyxel LTE5398-M904, after the upgrade:

Fri Jan 24 22:28:17 2025 kern.info kernel: [   75.691344] do_page_fault(): sending SIGSEGV to ujail for invalid read access from 00000036
Fri Jan 24 22:28:17 2025 kern.info kernel: [   75.708231] epc = 77df2757 in libubox.so.20240329[77dee000+1f000]
Fri Jan 24 22:28:17 2025 kern.info kernel: [   75.720732] ra  = 55554775 in ujail[55550000+14000]

Just sysupgraded my RPI4 and both of my Archer AX23 v1.20 units to rc6 from 23.05.5

Smooth sailing so far, but the RPi4 shows the following in the kernel log:

[    0.286699] ------------[ cut here ]------------
[    0.286716] Device 'grafx' does not have a release() function, it is broken and must be fixed. See Documentation/core-api/kobject.rst.
[    0.286788] WARNING: CPU: 0 PID: 1 at drivers/base/core.c:2515 0xffffffc0804d36f4
[    0.286815] Modules linked in:
[    0.286834] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.6.73 #0
[    0.286855] Hardware name: Raspberry Pi 4 Model B Rev 1.1 (DT)
[    0.286869] pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[    0.286890] pc : 0xffffffc0804d36f4
[    0.286904] lr : 0xffffffc0804d36f4
[    0.286916] sp : ffffffc080c5b6d0
[    0.286927] x29: ffffffc080c5b6d0 x28: 0000000000000000 x27: ffffff8040cee410
[    0.286958] x26: ffffff8040cc84b8 x25: ffffff8040cc84a0 x24: ffffffc0809088a0
[    0.286987] x23: ffffffc0809a3c18 x22: 0000000000000000 x21: ffffffc0809a4520
[    0.287015] x20: 0000000000000000 x19: ffffff8040cc80b8 x18: 00000000000000a2
[    0.287042] x17: 206e656b6f726220 x16: 7369207469202c6e x15: ffffffc080adefc8
[    0.287069] x14: 00000000000001e6 x13: 00000000000000a2 x12: 00000000ffffffea
[    0.287097] x11: 00000000ffffefff x10: ffffffc080b36fc8 x9 : ffffffc080adef70
[    0.287124] x8 : 0000000000017fe8 x7 : c0000000ffffefff x6 : 0000000000057fa8
[    0.287152] x5 : 0000000000000fff x4 : 0000000000000000 x3 : ffffffc080c5b4d0
[    0.287178] x2 : ffffffc080adef08 x1 : ffffffc080adef08 x0 : 000000000000007a
[    0.287205] Call trace:
[    0.287217]  0xffffffc0804d36f4
[    0.287230]  0xffffffc08088bff8
[    0.287242]  0xffffffc0804d38e4
[    0.287253]  0xffffffc0804f906c
[    0.287265]  0xffffffc0804f9170
[    0.287276]  0xffffffc0804812f0
[    0.287288]  0xffffffc0804df444
[    0.287299]  0xffffffc0804dc780
[    0.287311]  0xffffffc0804dc960
[    0.287322]  0xffffffc0804dca50
[    0.287334]  0xffffffc0804dcba4
[    0.287345]  0xffffffc0804da620
[    0.287356]  0xffffffc0804dcf44
[    0.287367]  0xffffffc0804dd20c
[    0.287379]  0xffffffc0804db5c4
[    0.287390]  0xffffffc0804d8c00
[    0.287402]  0xffffffc0804defa8
[    0.287413]  0xffffffc0805101d0
[    0.287424]  0xffffffc0805105b8
[    0.287436]  0xffffffc08050fccc
[    0.287447]  0xffffffc0804df444
[    0.287458]  0xffffffc0804dc780
[    0.287470]  0xffffffc0804dc960
[    0.287481]  0xffffffc0804dca50
[    0.287492]  0xffffffc0804dcc74
[    0.287504]  0xffffffc0804da570
[    0.287515]  0xffffffc0804dbfdc
[    0.287527]  0xffffffc0804db7b8
[    0.287538]  0xffffffc0804ddbdc
[    0.287549]  0xffffffc0804df108
[    0.287561]  0xffffffc080a7a26c
[    0.287572]  0xffffffc0800144c8
[    0.287584]  0xffffffc080a51014
[    0.287595]  0xffffffc0808ab3e4
[    0.287607]  0xffffffc0800152f0
[    0.287619] ---[ end trace 0000000000000000 ]---

First time seeing this. Operation doesn't seem to be affected. I'm running modern firmware.

I reckon error seems graphics related, so it makes sense it doesn't cause any issues in this context.

That's really early in the boot process. It's a solid warning.

Edit: it regards being able to remove the kernel module grafx (and the release function to do so is absent).

Dlink dir-3040 owut upgrade from rc5. Runs without any issues.

Thanks

Upgrading apm821xx/nand device Netgear WNDR4700 from 24.10.0-rc4 to 24.10.0-rc6 results in the following message:
"The device is supported, but this image is incompatible for sysupgrade based on the image version (3.0->2.0)." Is this an error in the version assigned to either the rc4 or rc6 image?

In any case upgrading using the -F parameter appears to be successful with no apparent issues. But then attempting to again update from 24.10.0-rc6 to 24.10.0-rc6 shows the same message!

1 Like