Recent 'master' snapshots losing 5G on EA6350v3

[mvh]

I have been building 'master' snapshots and running them on an EA6350 v3. Last few days the 5GHz radio becomes non-responsive when my daughter opens her laptop and connects to the wireless (it's a macbook air). New clients are not able to connect, old clients lose data transfer. If I restart the radio it's fine for a while. I don't see anything in the logs when this happens. I've switched to using a 19.07 snapshot for the sake of my sanity (as my daughter uses the network for her homework) but wanted to put something out there so that if other people see the same thing they'll know it's not them. Is there a place to file non-specific bugs?

[bill888]

I wonder whether the issue is related to this commit from 17 August 2019 but this is almost 2 months old ?

https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=8f757d427cce1e675df12fcde24ce78d5cd4651e

Furthermore the BDFs for the:
OpenMesh A42 specific BDFs
OpenMesh A62 specific BDFs
Linksys EA6350v3
have been updated.

Regarding your question about where to post non-specific bugs:

https://forum.openwrt.org/t/add-support-for-linksys-ea6350-v3/18907/375

https://bugs.openwrt.org/

[NoTengoBattery]

Hi, Bill
As you might not know, I uploaded both the files deleted in that commit and the files “upstream”, as they say.

Add support for Linksys EA6350 v3

I don't want to be noisy but... I put a new release in GitHub. All of the releases I did before were using the FCC/EU (which are 99% the same, bitwise speaking). I was investigating the original firmware and I found that they name the files like the board. So FCC/EU are using some Yxxxx board which is not this one. The folder hw_1 (not a surprise that if you ls -Ral /lib/firmware you will find the hw.1 folder) does contain a 2 files with the name of the board. Those files were sent here but n…

So, as I can confirm they are bitwise identical, this may not be the problem but it might be related.

With the work of @anders, we managed to get a combination that works the best. However, some devices have different wireless hardware (the EEPROM to be more specific), that’s why the OEM includes different calibration for different regions.
If I might suggest something, I would like you, @mvh, to give a try to my binary prebuilt. It contains the same script we used with @anders and all the calibration files from the OEM firmware ready to test.
The script is easy to use, and the prebuilt is easy to install (as it have a bunch of preinstalled software).

Optimized build for IPQ40xx devices

About this ROM This is a custom ROM for the EA6350 (the EA6350v3, to be more specific), EA8300, MR8300, and GL-S1300 [GL-B1300 needs feedback]. It fixes many problems present in the official OpenWrt build, allows users to revert to the original firmware [EA6350v3 only], and improves their wireless performance [EA6350v3 only]. Features: Fully preemptive, tickless kernel for improved latency. GNU bash as the default shell and nano with syntax highlights. Minimum clock frequency to 200 MHz with…

[mvh]

I went back to 'master' and it seems to be working fine now. I'll continue to use 'master' but will upgrade much less frequently!