ok... so what happens/happened (on my system) is that htop + scaling indicate freq change... but the underlying freq does not change if you have active undervolt
i have a really thin power lead going to my board... and either the power supply is dying, or summer or something else changed in the code... but now i'm pretty much permanently undervolting...
so vcgencmd / soc Hz doesn't get bumped (expected)
yeah... forcing it on for a little bit to test feature... but if it stays it will be configurable UPDATECHECK_BANNERMSGS= ( disable, critical alert only, etc. etc. )
there are two other alerts that can pop up at the moment;
fsck repair on boot
nlbwmon database is corrupt
based on our findings above I guess a 'your rpi is consistently undervolting' alert might also be beneficial... (afaik a little similar to the lightning bolt in raspi(ian|OS)?)
pretty easy to add your own to test also;
/bin/bannermsg_do.sh msg "055-12345_reminder-12345" "dont forget to put the bins out and last backup script failed"
it's just a random guess, because after upgrade, i couldnt connect with my dongle to a network. (already associated with network/ap but no ip detected in the intefaces page)
did you remove fmac/firmware-usb for performance/simplicity only?
i dont remember removing those packages. i only remove my dongle firmware/driver, wpad/hostapd/wpa_supplicant or related to that to troubleshoot my problem. maybe because i commented one of option in wrt.ini related to wifi (wifi autoconfig?). iirc, back then, i'm removing handful of pacakages related with wifi because i saw in log there are error with wpad, (something like this, /usr/sbin/wpad does not match process path (/proc/exe)).
are both those firmware packages in use (or just the mt one?)
i have two dongle one with mediatek and the other one with realtek. buutt, my reltek based dongle is suck, low signals. i'm ended up using mediatek one.
same for iw-full how does it help? ( mt usb adapter does not work without it?)
iw-full just a random guess for me back then when i'm troubleshooting my wifi dongle problem.
for the above... i'm considering;
• changing iw > iw-full and (not sure why this is not done already actually)
• adding mt7601u-firmware to the build...
yeah. i would be grateful if you add that firmware (idk about iw-full tho, no harm i guess).
part of the firstboot sequence is a network restart... depending how this effects your connection the answer will vary...
on new builds /etc/custom/everyboot/ does what you think 'startup' would do... as an artifact of some old logic 'startup' right now essentially means 'not firstboot'...
technically yes, if you put the same script in both 'startup' and 'firstboot' then you achieve the same thing as 'everyboot'.... everyboot runs late though... so we probably need to modify some of the logic or your script to better support it...
so;
/etc/custom/everyboot/5-yourscript.sh
(and add to sysupgrade.conf) will work... but on firstboot it will be too late for the package restore logic...
so right now the question is... if you do a /etc/init.d/network restart does your script always need to be run after that?
there is also /etc/custom/<YOURMAC>.sh ...
but for your case, better we work out the timing / other issues as it will probably lead to improvements in the build and help others...
as a general rule 'link' related scripts always have some state logic (hotplug, netifd:/etc/config/network, daemon) and are not implemented in a one way fashion
one hacky workaround would be to call your script also at the top of /bin/checkinternet.sh and add that to sysupgrade.conf
(but we may as well fix the problem properly... above is just an FYI hack that would call it at the right time)
release [newer-major] 1.0.15-3(1.0.13-3) [flash] twicedaily[refresh]
I still face the issue of DNS not working when I get new IP from WAN side, I have to wait for 10-30mins for it to work again or restart dnsmasq and https-dns-proxy manually.