B2200 Velica Upgrade 3.215 went sideways

roken70 · 2022-10-13T06:52:22.126Z

I have two new B2200 in a mesh network yesterday. Everything worked fine (also upgrade to 3.212).

Today, after the advertised upgrade from 3.212 to 3.215, this situation is completely different:

The main node is on 3.215, but the sub node remains on 3.212. The 2.4 GHz WLAN seems to have stopped working.

LuCI shows the firmware version OpenWrt Chaos Calmer 15.05.1 e7067e3+r49254 (which is kind of old; I think, I remember seeing 19 something yesterday on 3.212).

Tons of kernel errors, like:

Thu Oct 13 08:06:50 2022 daemon.info hostapd: ath1: STA 12:d5:a7:d2:cc:c7 IEEE 802.11: disassociated
Thu Oct 13 08:06:50 2022 kern.err kernel: [ 7685.956239] wlan: [1044:E:ANY] [soc1] FWLOG: [7730034] WAL_DBGID_PDEV_INFO_PRINT ( 0x197, 0x0, 0xab02)
Thu Oct 13 08:06:50 2022 kern.err kernel: [ 7685.956239] 
Thu Oct 13 08:06:50 2022 kern.err kernel: [ 7685.976001] wlan: [1044:I:ANY] debug_fatal_condition_handler: 1473: SmartLogEvent: STA KICKOUT SUBEVENT
Thu Oct 13 08:06:50 2022 kern.err kernel: [ 7685.976001] 
Thu Oct 13 08:06:50 2022 kern.err kernel: [ 7685.978313] wlan: [1044:E:ANY] [soc1] FWLOG: [7730058] WLAN_DEBUG_DBGID_PDEV ( 0x3, 0x0)
Thu Oct 13 08:06:50 2022 kern.err kernel: [ 7685.978313] 
Thu Oct 13 08:06:50 2022 kern.err kernel: [ 7685.989623] wlan: [1044:E:ANY] [soc1] FWLOG: [7730058] WAL_DBGID_PDEV_INFO_PRINT ( 0x83ba77f0, 0x82e7b121, 0xab00)
Thu Oct 13 08:06:50 2022 kern.err kernel: [ 7685.989623] 
Thu Oct 13 08:06:50 2022 kern.err kernel: [ 7685.999059] wlan: [1044:E:ANY] [soc1] FWLOG: [7730058] WAL_DBGID_PDEV_INFO_PRINT ( 0x40000395, 0x7ec8402e, 0x20048007, 0xab01)
Thu Oct 13 08:06:50 2022 kern.err kernel: [ 7685.999059] 
Thu Oct 13 08:06:50 2022 kern.err kernel: [ 7686.010667] wlan: [1044:E:ANY] [soc1] FWLOG: [7730058] WAL_DBGID_PDEV_INFO_PRINT ( 0x197, 0x0, 0xab02)
Thu Oct 13 08:06:50 2022 kern.err kernel: [ 7686.010667] 
Thu Oct 13 08:06:50 2022 kern.err kernel: [ 7686.024052] wlan: [1044:I:ANY] debug_fatal_condition_handler: 1473: SmartLogEvent: STA KICKOUT SUBEVENT
Thu Oct 13 08:06:50 2022 kern.err kernel: [ 7686.024052] 
Thu Oct 13 08:06:50 2022 kern.err kernel: [ 7686.570406] wlan: [1044:E:ANY] [soc1] FWLOG: [7730083] WAL_DBGID_STA_KICKOUT ( 0x4413cc, 0xccc7, 0x1c2, 0x10e, 0x1c2)
Thu Oct 13 08:06:50 2022 kern.err kernel: [ 7686.570406]

Wireless settings shown in LuCI are wrong (because of wrong OpenWRT version?)

Any suggestions how to fix this mess?

Thank you.

alzhao · 2022-10-13T09:50:00.335Z

The openwrt version are the same.

The sub node can still connec to the Internet? It is supposed to upgrade if version is older than the main node.

roken70 · 2022-10-13T13:01:11.932Z

What do you mean with the openwrt version are the same? Shoudn’t it be 19.x like the release notes say?

The subnode is connected to the main node by cable. So I think it should have.

Blobbie01 · 2022-10-13T13:34:39.858Z

V3.212
System:

1. Based on openwrt 19.07.8 (AR150,MIFI,AR300M,USB150,N300,AR750,AR750S,X750,E750,XE300,MT1300,MT300N-V2,MV1000)
1. Based on QSDK11 (B1300,S1300,AP1300,B2200)

The B2200 was, and still is, based on QSDK11. That’s OpenWRT 15.

You can manually update the second sub node through uboot: Debrick via Uboot - GL.iNet Docs

roken70 · 2022-10-13T14:07:12.363Z

Thanks for the info.

Are there compatibility issues with B2200 / GL.INet Admin Panel and newer OpenWRT versions? Or is it possible to move to a newer OpenWRT version?

alzhao · 2022-10-14T03:14:10.372Z

The mesh cannot bot ported to newer openwrt directly. Have to use totally different mesh technology.