Belkin RT3200/Linksys E8450 WiFi AX discussion

I just tried an attended sysupgrade from 22.03.5 to 23.05.0, which resulted in 5GHz wifi not working. I guess its due to a driver not being installed. I'm still searching what I need to install.

[edit]

Fixed it. Installed opgk update ; opkg kmod-mt7915-firmware and replaced the "path" setting in /etc/config/wireless by phy wl0 and phy wl1.

I obviously have not much experience since I installed 23.05.0 just a couple of minutes ago, but at first glance the box is running at leasts as much as I need it for being able to fiddle around with it.

4 Likes

Upgraded RT3200 from 22.03.5 to 23.05.0 using Luci upgrade through browser and everything worked with existing config. My network setup includes 2 AX networks (AP mode, 80MHz, ch36, 20dBm - 100mW, disabled IPv6, SAE-mixed, 2 fixed MAC addresses, beamforming, and BSS coloring). Software and hardware offload as well as packet steering are on.

I maintain a minimal setup to ensure stability. After the upgrade, I re-flashed 23.05.0, and it worked as expected. Tested with Android devices, iPad, and another OpenWRT router.

Just had exactly same situation - after using auc to upgrade from 22.03.05 to 23.05.0 over web - I had no 5GHz WiFi. Had to install kmod-mt7915-firmware and reboot. After reboot, all seem as it was previously.

Thanks. I managed to upgrade from 22.03.5 to 23.05 0 using LuCi attended sysupgrade based on the posts here and this helpful post here:

I keep getting: "No upgrade available

The device runs the latest firmware version 22.03.5 - r20134-5f15225c1e"

When using LuCi Attended Sysupgrade with the https://sysupgrade.openwrt.org server.

Have you done something special for the upgrade to become available?

Edit: it appears I had to enable advanced mode!

1 Like

I would not advice using attended sysupgrade for a major version upgrades. As in your case, some packages were missing. You also don't know, what other important packages might be missing.
Better upgrade the normal way with sysupgrade, check keep data and then just install the packages you need to get your functionality back. All their configs are kept.

I have been running 23.05.0-rc4 for a while and just upgraded to 23.05.0. No WED, no 160 MHz channel, here

4 Likes

@patrakov after the upgrade, compared to the manifest, I now have:

kmod-mt7615-firmware
kmod-mt7915-firmware

Why are these not in:

https://downloads.openwrt.org/releases/23.05.0/targets/mediatek/mt7622/openwrt-23.05.0-mediatek-mt7622.manifest

which lists:

kmod-mt76-connac - 5.15.134+2023-08-14-b14c2351-1
kmod-mt76-core - 5.15.134+2023-08-14-b14c2351-1
kmod-mt7615-common - 5.15.134+2023-08-14-b14c2351-1
kmod-mt7615e - 5.15.134+2023-08-14-b14c2351-1
kmod-mt7622-firmware - 5.15.134+2023-08-14-b14c2351-1

I'm a bit confused by this. Is another package in the manifest providing the firmware otherwise provided by:

kmod-mt7615-firmware
kmod-mt7915-firmware

On my E8450, I only have these two firmwares:

kmod-mt7622-firmware - 5.15.134+2023-08-14-b14c2351-1
kmod-mt7915-firmware - 5.15.134+2023-08-14-b14c2351-1

Therefore, kmod-mt7615-firmware is redundant, while kmod-mt7915-firmware is not.

3 Likes

Understood. But why isn't kmod-mt7915-firmware in the manifest file?

Because kmod-mt7915-firmware is needed specifically for Linksys E8450, not for all devices covered by the mt7622 subtarget.

2 Likes

I did almost the same, but used firmware selector and added my additional packages there (ddns, speedtestpp, nano, and others), then I updated using sysupgrade.

Everything's working fine on 23.05.0.

I do have a question that's probably answered somewhere: is there a way to edit the model name to reflect Belkin RT3200 instead of E8450? I know it's cosmetic, but at least it should appear as Linksys E8450/Belkin RT3200 (UBI) in the overview page.

Cheers!

Hack the value in /tmp/sysinfo/model? It will be overwritten on reboot, but it should change what you see on the luci status page.

2 Likes

Could be made permanent via local startup commands.

3 Likes

Is there a different firmware selector? This one doesn't allow adding custom packages:
https://firmware-selector.openwrt.org/

Of course you can:

Cheers!

1 Like

This worked great!

I added:

echo "Belkin RT3200 (UBI)" > /tmp/sysinfo/model

in my Local Startup (/etc/rc.local) file!

By the way, On 22.03.x I didn't need to change the governor, but now, I had to set schedutil also on my /etc/rc.local file because on reboot, sometimes the router won't boot up. Any thoughts???

2 Likes

This would be a bug. I have read for at least about seven E8450/RT3200 working fine with OpenWrt 23.05. Mine included. Booting should also not depend on the CPU scaling governor.

What is your boot problem about?

Don't know, I just rebooted the router from the System menu and the router won't come up, I had to power it off and turn it on again using the switch on the back.

As soon as I changed the governor, it rebooted properly. The same happened to me on 22.03 when I got this router and followed the Wiki by manually putting ondemand as the governor. When changed to schedutil, it rebooted fine. Eventually I removed the governor line and still worked fine. But now on 23.05 the problem appeared again.

Depending on your location: did you wait for the DFS radar scanning time to complete? This needs about one minute until the 5 GHz SSIDs are activated.

If you have found a bug please provide debug information from logs what is failing. I don’t see a relation from the CPU scaling governor to boot problems for now.

+1

My RT3200 is running fine on 23.05.0

2 Likes