Sorry I meant the first part and some other also just run schedutil.
Users have been reporting that schedutil avoids the problem. This is coincidental as it just happens not to end up in the lowest operating point at the point the reset is asserted
I did install luci-app-attendedsysupgrade but it can't find any update from 22.03.0-rc1.
Flashing snapshots through System -> Backup / Flash Firmware just hangs up my router and I have to enter recovery and re-flash rc1 to get it back working.
Tried again with todays build:
I am downloading the sysupgrade file. Maybe I am doing something wrong.
I used the method mentioned in the GitHub repo to successfully switch to UBI firmware. Then upgraded to the 22.03-rc1 snapshot. Everything was working fine. I then upgraded to the snapshot. Again fine. Today I upgraded all the packages. Then because I had no idea what I was doing I used scp to send the 22.03-rc1 sysupgrade to the router and did a 'sysupgrade 22.03-rc1-sysupgrade.itb' The router rebooted and now I can't enter recovery. It boots and shows yellow LED on the internet. I pressed reset while boot but it shows yellow on the Internet not power (not sure its the same thing). I can set my IP to 192.168.1.10 and subnet to 255.255.255.0 and gateway to 192.168.1.1. I can also ping 192.168.1.1 but I can't ssh or do anything beyond that. I have tftp setup but not sure how to go from here to recover. Any ideas ?
UPDATE: NVM. Just recovered. Needed a few power cycles. This is so easy to recover. Also used the snapshot initramfs recovery but sys upgraded the 22 rc1
It was my primarily my wive's phone... she hasn't complained about it so I assume it's fixed. I still see plenty of entries in my log like this though:
daemon.info hostapd: wlan1: STA XXX IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
I'm a bit of a chronic tinkerer (sounds like a medical issue but it isn't) and I checked out the smp_affinity of all the IRQs to see if any device is pegged to a specific CPU.
Using: cat /proc/irq/*/smp_affinity
IRQ 142 is usually set to 1
IRQ 143 is usually set to 2
The rest are 3
It looks like it is essentially a nop since the effective_affinity doesn't change.
142 and 143 are related to the ethernet driver.
I'm sure there is a good reason for it, but I'm just curious of the history or logic behind it? I know there was a patch that went in about a month ago that opened up the Ethernet to multiple CPUs for network processing.
Just trying to learn and hopefully this isn't straying off-topic but it is hardware related to this model.
Are there still problems with 802.11s mesh? I can't seem to get it to work. I tried on both the 2.4 en 5ghz bands with and without encryption... It seems to work for a minute or 2 and then stops working. I'm not able to connect to it. And when plugged into the lan port. The port on my switch flashes ones a second. I have to reboot the router to be able to access it again. I have the same setup on a pair of 1043wd v2's and that works perfectly.
OneMarcFifty posted a video about meshing with OpenWRT just a couple days ago. He's using BATMAN, so probably well different than what you're doing, but maybe worth a watch...
