I have 2 relatively new Linksys E8450s running OpenWrt 24.10.1 r28597-0425664679 / LuCI openwrt-24.10 branch 25.103.51521~2ac26e5, initialized by this procedure. With identical configs as well as reverted to the default config, one seems to have a broken 5GHz radio.
To be clear, OpenWrt thinks it's working. E.g.:
root@OpenWrt:~# dmesg | fgrep 7915
[ 1.775026] pci 0000:01:00.0: [14c3:7915] type 00 class 0x000280
[ 10.253115] mt7915e 0000:01:00.0: assign IRQ: got 130
[ 10.258232] mt7915e 0000:01:00.0: enabling device (0000 -> 0002)
[ 10.264408] mt7915e 0000:01:00.0: enabling bus mastering
[ 10.469946] mt7915e 0000:01:00.0: HW/SW Version: 0x8a108a10, Build Time: 20240429200716a
[ 10.665252] mt7915e 0000:01:00.0: WM Firmware Version: ____000000, Build Time: 20240429200752
[ 10.720920] mt7915e 0000:01:00.0: WA Firmware Version: DEV_000000, Build Time: 20240429200812
[ 10.837953] mt7915e 0000:01:00.0: registering led 'mt76-phy1'
and Luci reports it as on, but it's not visible. This started after the upgrade from 24.10.0 to 24.10.1, whereupon it would also freeze during reboot. I discovered the docs about OKoD on the E8450 page, and according to the given command:
root@OpenWrt:~# grep "(release)" /dev/mtd0ro
v2.10.0 (release):OpenWrt v2024.01.17~bacca82a-3 (mt7622-snand-ubi-1ddr)
v2.10.0 (release):OpenWrt v2024.01.17~bacca82a-3 (mt7622-snand-ubi-1ddr)
v2.10.0 (release):OpenWrt v2024.01.17~bacca82a-3 (mt7622-snand-ubi-1ddr)
v2.10.0 (release):OpenWrt v2024.01.17~bacca82a-3 (mt7622-snand-ubi-1ddr)
I should be okay. I also went as far as to compare fw_printenv and ubinfo -a output between the working and the broken router and they are the same except for expected differences like macaddr.
Any ideas how to proceed with debugging?
Btw note I didn't save a backup of the vendor bootchain because the instructions say If you plan to ever go back to the stock firmware, you will need a backup of the vendor bootchain and firmware, and after 10 years of running OpenWrt and only paying like $20 for the router on W00t, I figured what are the odds I'd want to go back? Though maybe there is a copy in a UBI partition?
root@OpenWrt:~# ubinfo -a
UBI version: 1
Count of UBI devices: 1
UBI control device major/minor: 10:127
Present UBI devices: ubi0
ubi0
Volumes count: 8
Logical eraseblock size: 126976 bytes, 124.0 KiB
Total amount of logical eraseblocks: 1020 (129515520 bytes, 123.5 MiB)
Amount of available logical eraseblocks: 0 (0 bytes)
Maximum count of volumes 128
Count of bad physical eraseblocks: 0
Count of reserved physical eraseblocks: 20
Current maximum erase counter value: 2
Minimum input/output unit size: 2048 bytes
Character device major/minor: 250:0
Present volumes: 0, 1, 2, 3, 4, 5, 6, 7
Volume ID: 0 (on ubi0)
Type: static
Alignment: 1
Size: 9 LEBs (1142784 bytes, 1.0 MiB)
Data bytes: 1021228 bytes (997.2 KiB)
State: OK
Name: fip
Character device major/minor: 250:1
-----------------------------------
Volume ID: 1 (on ubi0)
Type: static
Alignment: 1
Size: 5 LEBs (634880 bytes, 620.0 KiB)
Data bytes: 524288 bytes (512.0 KiB)
State: OK
Name: factory
Character device major/minor: 250:2
-----------------------------------
Volume ID: 2 (on ubi0)
Type: dynamic
Alignment: 1
Size: 1 LEBs (126976 bytes, 124.0 KiB)
State: OK
Name: ubootenv
Character device major/minor: 250:3
-----------------------------------
Volume ID: 3 (on ubi0)
Type: dynamic
Alignment: 1
Size: 1 LEBs (126976 bytes, 124.0 KiB)
State: OK
Name: ubootenv2
Character device major/minor: 250:4
-----------------------------------
Volume ID: 4 (on ubi0)
Type: dynamic
Alignment: 1
Size: 58 LEBs (7364608 bytes, 7.0 MiB)
State: OK
Name: recovery
Character device major/minor: 250:5
-----------------------------------
Volume ID: 5 (on ubi0)
Type: dynamic
Alignment: 1
Size: 123 LEBs (15618048 bytes, 14.8 MiB)
State: OK
Name: fit
Character device major/minor: 250:6
-----------------------------------
Volume ID: 6 (on ubi0)
Type: dynamic
Alignment: 1
Size: 67 LEBs (8507392 bytes, 8.1 MiB)
State: OK
Name: boot_backup
Character device major/minor: 250:7
-----------------------------------
Volume ID: 7 (on ubi0)
Type: dynamic
Alignment: 1
Size: 730 LEBs (92692480 bytes, 88.3 MiB)
State: OK
Name: rootfs_data
Character device major/minor: 250:8