I'm not getting 5 Ghz connectivity after upgrading from 23.05.4 on my Netgear R6700 v2 and Linksys E8450. I'm not sure if it's a configuration issue. I'll have to look at my logs when I get time.
1 Like
Did you customize your build with extra packages? The base package list for all models in the firmware selector is missing packages that have always been there before, such as firmware for wireless radios for said devices.
The plain stock builds are working fine.
You're not the only one with issues on the MT76* and MT79* hardware. I suspect that there is a new dependency that the custom builder component of the firmware selector doesn't yet know about and so it isn't listed by default. Did you use the default builds or did you customize?
It seems to be every device and hardware (firmware missing from custom package firmware builds)? Anybody in the know that can update if this is going to be fixed?
I can't confirm whether it's every device or not. The only devices I've had issues upgrading are the MT76* devices which (in my network) all require additional packages. This includes the Ubiquiti U6 Lite, the BPI R3, the Linksys e8450 and others.
I've noticed it on both my mediatek and non-mediatek devices
3 Likes
Xiaomi Redmi AX6S / AX3200, upgraded via Luci Attended Sysupgrade, no problems.
Thanks developers 
2 Likes
It looks like the package list for the builder has been reverted to an earlier point. Some firmware files are present, but those recently added or changed are missing.
3 Likes
Yes, it was the custom build. Stock firmware worked fine.
The E8450 list still has kmod-mt7622-firmware, but not kmod-mt7915-firmware (Hence one of the radios not working). Other packages like kmod-usb3 not there either. Weird.
1 Like
Checking the pre-built image package contents against those generated from the firmware selector shows that the '/lib/firmware' folder and kernel modules are missing for all devices. The nasty side effect would be to effectively render the box as a 'soft-brick' after installation or following an upgrade without all the required components. Manually adding the missing package components to the build list for each target and versions from SNAPSHOT down does generate the correct image identical to the existing pre-built images.
5 Likes
Just used the "Flash new firmware image" page in luci to update Linksys WRT3200ACM from 23.05.04 to 23.05.05 using an image with customized packages list (add a few to the base).
Install went fine, and I'm getting ~600Mbps on wifi vs ~100Mbps before.
5 Likes
kmod-mt7915-firmware was added as a dependency for the e8450 when the firmware was split into its own package, and that change was somewhat recent.
This is definitely going to cause some really ugly issues for people who are now missing critical packages.
2 Likes
Thanks to developers, upgrades from .4 and previous 23.05-snapshot builds went smoothly here with no apparent regressions.
Buffalo WZR-HP-AG300H and Netgear WAX206 with some non-default VLAN config and services.
Re: the MT7622/MT8915E Netgear and firmware files: I built my images locally with imagebuilder which still includes the necessary firmware as default dependencies:
make image PROFILE=netgear_wax206 PACKAGES="wpad-mbedtls mtr luci-ssl tcpdump htop -wpad-basic-mbedtls luci-app-openvpn luci-app-sqm luci-app-tinyproxy openvpn tinyproxy sqm-scripts"
Looking at the JSON responses, it looks like the firmware selector isn't parsing the specific device packages correctly and adding that to the package list, so it affects multiple devices, irregardless of target. This explains why for example ath10k-firmware-qca9984-ct and kmod-ramoops is missing for R7800 when you compare with https://downloads.openwrt.org/releases/23.05.5/targets/ipq806x/generic/profiles.json.
I know that there's at least a few devices which configure their switch with device packages, so I guess this in worst case could lead to a brick if serial isn't available/the user don't know how to use it (just guessing tho).
8 Likes
You probably already checked this, but do you happen to have Hardware Offload enabled on the Xiaomi AX3200 after the upgrade? That usually causes the discrepancy in the accounted packets on WAN
3 Likes
Linksys EA8500 continues to work well with OpenWrt version 23.05.5.
2 Likes
Do we have bugtracker link so I can read more about it?
1 Like
If that is indeed the cause, it's not really a bug, as hardware offload usually works by offloading a lot of the NAT away from the CPU.
This also means that the offloaded traffic can't really be tracked or accounted as properly as before.
I don't know if there is an official bug tracker for it, but you can check the shortlog for the updates added since the previous version: https://git.openwrt.org/?p=openwrt/openwrt.git;a=shortlog;h=refs/tags/v23.05.5
1 Like
AP-only WAX202 upgrading via luci to 23.05.5 seems to fail to boot with my existing config. No WiFi networks, no response to the configured IPs on Ethernet. Using the reset button doesn't consistently work, 9 times out of 10 pressing the reset has main LED turn off instead of flashing orange to indicate a reset.
After a lot of power cycling I got a reset, and it boots to 23.05.5, but restoring my config backup takes it right back to the boot issue. A rollback to 23.05.4 with the same restored backup is working fine.
Not sure how to debug this, it seem like the thread thinks some packages are missing in the default 23.05.5 image for WAX202?