To be clear, I'm talking about my client not the router. In this case my client is a laptop running Archlinux, so in order to update my kernel to the latest available, I simply updated my packages using the package manager.
I have no idea what your setup is, and every client is different. For example, the iPhone is something completely different.
I finally found the right search term, apparently, some radios cannot broadcast and scan at the same time, so the one on my travel router probably has that capability where the Belkin does not. That answers that!
Alrighty, my belkins have been running fairly well but there is one oddity. The 5g radios apparently work fine, I have 5ghz and 2.4ghz on the same SSID and password, with 802.11r Fas transition on. I also have a set or Orbi RBR20's these Belkins might replace, if I get all the kinks worked out.
Current oddity is on the channel scanning page, the 2.4 ghz radios show all of the other channels / access stations in my neighborhood, but the Belkins do not. I have two of them, configured almost identically, with the 23.05 release installed. Neither of them will show a proper channel scan, they only show their own interface.
I have a GL.Inet Slate plus, running 23.03 I think, it can scan all the 5gh channels and sees the Belkin machines as well as some of my neighbors, but I would like my Belkins to work as well.
There is nothing in either the system log or kernel log that looks like a failure or error.
What would be a good next step to troubleshoot? My OpenWRT install is using the Dangowrt installer that was just update recently, if that helps. I had see some folks saying the radio packages changed or were not included but that does not seem to be the problem, as I can split out my SSID to 5g, connect to it separately, and run an iperf3 test and get good speeds. So the 5ghz radio definitely works.
root@OpenWrt-1:~# cat /etc/rc.local
# Put your custom commands here that should be executed once
# the system init finished. By default this file does nothing.
echo "ondemand" > /sys/devices/system/cpu/cpufreq/policy0/scaling_governor
is no longer necessary for those like me that had that?
With the default governor changed to ondemand in 23.05, is manually setting scaling_min_freq to 600000 still needed? I know one is not related to the other, however they're both manual steps performed in rc.local.
I think it was related to the default 437500 triggering a lower voltage on some RAM chips, and some devices would freeze upon boot in the lower voltage mode. There was a link to the code where this was identified, however I don't remember seeing if it was actually patched to use the higher voltage at the lower speed.
Is it still recommended to set scaling_min_freq to 600000?
Yes, 5GHz radio turns off, 2,4GHz wifi looks unusable, I can login to luci, but after clicking anywhere it says the session timed out and logs me out. The only thing I can do is ssh into the router via a cable connected computer and reboot the router.
I also disabled WED yesterday and waiting for the results.
I have two RT3200s that I use as access points. After upgrading to 23.05.0 one would shut down after a reboot and also lose the 5Ghz radio after a day or two. Setting the min frequency and changing the governor to schedutil seems to have fixed both those problems. The other RT3200 has had no issues at all.