OpenWrt 24.10.1 - Service Release

Hello,
Thank you for the link,
But i'm not sure it applies here.
the link mentions the update from 23.05 to 24.10
I am already on 24.10.0 and can't update to 24.10.01

Also I can't find how to check if this is needed and I remember having go trough this on the initial install (v23.05)

this ofcourse could be the reason.

But my feeling is the ASU for some reason(maybe cache) includes the wrong openWRT version for "mediatek/filogic" systems.
If I know how to open an itb file inwindows I might be able to check this.

1 Like

Dlink dir-3040 a1 upgrade via owut from 24.10 to 24.10.1 went smooth this time. Thanks

Xiaomi ax9000 and xiaomi ax3000T upgraded with firmware selector generated images. Plain vanilla only 802.11s meshes. Upgrade over mesh.

MT6000 / 24.10.0 -> 24.10.1 asu

all OK.

I still get

daemon.notice netifd: radio0 (3365): WARNING: Variable 'data' does not exist or is not an array/object
daemon.notice netifd: radio1 (3375): WARNING: Variable 'data' does not exist or is not an array/object

Does something need removing from /etc/config/wireless?

config wifi-device 'radio0'
	option type 'mac80211'
	option path 'platform/soc/18000000.wifi'
	option channel '6'
	option band '2g'
	option htmode 'HT20'
	option cell_density '0'

config wifi-device 'radio1'
	option type 'mac80211'
	option path 'platform/soc/18000000.wifi+1'
	option channel '36'
	option band '5g'
	option htmode 'HE80'
	option cell_density '0'

Also get the following during early boot, probably because some addresses aren't available yet, but everything works out fine when procd retries.

daemon.err uhttpd[2849]: bind(): Address not available
daemon.err uhttpd[2849]: bind(): Address not available
daemon.err uhttpd[2849]: Error: No sockets bound, unable to continue

were you able to recover?

You're welcome to update the wiki yourself (recent device) or ask @Linaro :

yes, i can recover the mx4200 v1 to the previous working 24.10.0 as this router has dual firmware flashing backup ...

okay cool! Yea I think my mx5300 has dual firmware but for the life of me could not figure it out

actually it doesn't lol

Hello
Raspberry Pi 3 Model B Rev 1.2
ARMv8 Processor rev 4
OpenWrt 24.10.1 (r28597-0425664679)

Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.137655] ------------[ cut here ]------------
Fri Apr 18 15:55:10 2025 kern.err kernel: [    0.138484] Device 'grafx' does not have a release() function, it is broken and must be fixed. See Documentation/core-api/kobject.rst.
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.140213] WARNING: CPU: 0 PID: 1 at drivers/base/core.c:2516 0xffffffc0804c31a4
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.141910] Modules linked in:
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.142736] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.6.86 #0
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.143574] Hardware name: Raspberry Pi 3 Model B Rev 1.2 (DT)
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.144402] pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.145249] pc : 0xffffffc0804c31a4
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.146069] lr : 0xffffffc0804c31a4
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.146843] sp : ffffffc080c1b6d0
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.147594] x29: ffffffc080c1b6d0 x28: 0000000000000000 x27: ffffff8001a42810
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.148374] x26: ffffff80019804b8 x25: ffffff80019804a0 x24: ffffffc0808d76e8
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.149138] x23: ffffffc08096e550 x22: 0000000000000000 x21: ffffffc08096ee58
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.149884] x20: 0000000000000000 x19: ffffff80019800b8 x18: 0000000000000075
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.150618] x17: 0000000000000000 x16: 0000000000000000 x15: ffffffc080a9e318
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.151323] x14: 000000000000015f x13: 0000000000000075 x12: 00000000ffffffea
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.152003] x11: 00000000ffffefff x10: ffffffc080af6318 x9 : ffffffc080a9e2c0
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.152673] x8 : 0000000000017fe8 x7 : c0000000ffffefff x6 : 0000000000057fa8
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.153360] x5 : 0000000000000fff x4 : 0000000000000000 x3 : ffffffc080c1b4d0
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.154047] x2 : ffffffc080a9e258 x1 : ffffffc080a9e258 x0 : 000000000000007a
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.154733] Call trace:
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.155377]  0xffffffc0804c31a4
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.155996]  0xffffffc08085d3f0
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.156576]  0xffffffc0804c338c
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.157147]  0xffffffc0804e89e4
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.157692]  0xffffffc0804e8ae8
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.158211]  0xffffffc080470f38
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.158697]  0xffffffc0804ceebc
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.159152]  0xffffffc0804cc268
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.159607]  0xffffffc0804cc448
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.160054]  0xffffffc0804cc538
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.160477]  0xffffffc0804cc68c
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.160879]  0xffffffc0804ca108
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.161260]  0xffffffc0804cca2c
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.161617]  0xffffffc0804cccf4
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.161953]  0xffffffc0804cb0ac
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.162274]  0xffffffc0804c8700
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.162573]  0xffffffc0804cea20
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.162846]  0xffffffc0804feb58
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.163100]  0xffffffc0804fef40
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.163323]  0xffffffc0804fe654
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.163514]  0xffffffc0804ceebc
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.163695]  0xffffffc0804cc268
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.163877]  0xffffffc0804cc448
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.164058]  0xffffffc0804cc538
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.164236]  0xffffffc0804cc75c
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.164414]  0xffffffc0804ca058
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.164591]  0xffffffc0804cbac4
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.164767]  0xffffffc0804cb2a0
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.164942]  0xffffffc0804cd6c4
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.165119]  0xffffffc0804ceb80
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.165296]  0xffffffc080a378a4
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.165475]  0xffffffc080012c28
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.165655]  0xffffffc080a1100c
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.165837]  0xffffffc08087c728
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.166020]  0xffffffc080013a50
Fri Apr 18 15:55:10 2025 kern.warn kernel: [    0.166204] ---[ end trace 0000000000000000 ]---

I upgraded from 24.10.0 to 24.10.1 via attended sysupgrade my BPI-R3 without issue. :smiley:

1 Like

It's just a new device, I don't know how. That's why I ask.

Any news about availability of Wi-Fi 7 routers? I'd be happy to be a beta tester, would buy any device within 150$ range and would try it.

Hello Guys,

Trying to build an image now , build system seems to be hanging , no progress for hours .

There's already reports, see the Firmware Selector thread starting here:

When I moved to 14.10.0, I had problems upgrading a remotely managed router because the device name assigned to the RNDIS cellular modem by kmod-usb-net-rndis changed from "usb0" to "eth0", which broke the network configuration that sysupgrade had retained across the reflash, and meant that the router was left running the successfully upgraded firmware, but completely offline. It required a days driving to resolve that.

So I note with... interest? frustration? excitement? panic? ...that under the announcement of 24.10.1 in the "Various fixes and improvements" section, there is an entry that says "kernel: usbnet: Restore usb%d naming for cdc-ethernet devices with local MAC".

Does that mean that 24.10.1 has reversed the change that bit me last time, and will reinstate my cellular modem as "usb0" again rather than the "eth0" that 24.10.0 used? If so I need to formulate a mechanism to safely manage a remote sysupgrade where the base network configuration needs to be amended as part of the upgrade. Or plan another road trip...

2 Likes

Thanks for the update.

Upgraded 2x Tp Link Archer c7v2 (used as AP's) with the sysupgrade from the firmware selector 23.05.5 to 24.10.1. The update itself went ok however did have to manualy correct the config for things to function after the upgrade.

After the upgrade (with keep settings) the clients on the guest network failed to get IP adresses on the AP.

It seems this was caused by an additional device with a "br_" prefix that somehow got configured for my guest lan and this device was not attached to anything. Switching it back to original one configured for the correct path and unconfiguring the new "br_" one fixed it for me. (note that both devices had the same issue)

Hi folks,
just upgraded from 24.10.0 to 24.10.1 via attended sysupgrade on my Xiaomi AX3600 without any issue.
Thanks to all developers and happy easter!
best
Andy

This is a harmless error. It says that the kernel module for RPi lacks the default function mentioned. It must be fixed upstream.

mx4xxx series has dual firmware setup. When doing a sysupgrade, both partitions are upgraded. In other words, you need to do a mtd flash to install OpenWRT on both partitions. If it is 1 OEM and 1 OpenWRT, the upgrade fails (blinking green, soft brick).

When it is soft bricked, you need to do 30/30/30 reset so the router returns to its most current OpenWRT installation.

oh i see...so is there an option to just upgrade the partition that is running OpenWRT and leave the other OEM partition as it is ??