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
######### [root@dca632 /usbstick 53°]# rpi-throttlewatch.sh
NPROC:1 RUNSSLBENCH:off NPROC_SSL:2
Time Temp CPU Core Health Vcore
00:31:22 53.5'C 600MHz 200MHz 01010000000000000101 0.8375V
00:31:25 53.5'C 600MHz 200MHz 01010000000000000101 0.8375V
00:31:28 53.5'C 1500MHz 500MHz 01010000000000000000 0.8375V
00:31:31 53.5'C 600MHz 200MHz 01010000000000000101 0.8375V
00:31:34 53.0'C 600MHz 200MHz 01010000000000000101 0.8375V
00:31:37 53.0'C 600MHz 200MHz 01010000000000000101 0.8375V
^C
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)
1 Like
johnd2
2002
i suppose this is on 5.0.19?
on my 5.0.11 it looks like this:
root@vpn_pi /41# rpi-throttlewatch.sh
taskset-aarch64 -c 0,1,2,3 /bin/rpi-throttlewatch.sh -P -C 4
NPROC:1 RUNSSLBENCH:off NPROC_SSL:2
Time Temp CPU Core Health Vcore
15:40:12 39.9'C 1500MHz 500MHz 00000000000000000000 0.8438V
15:40:15 40.4'C 1100MHz 366MHz 00000000000000000000 0.8438V
15:40:18 40.9'C 1100MHz 366MHz 00000000000000000000 0.8438V
15:40:21 40.4'C 1100MHz 500MHz 00000000000000000000 0.8438V
15:40:24 39.9'C 1100MHz 366MHz 00000000000000000000 0.8438V
15:40:27 40.9'C 1500MHz 500MHz 00000000000000000000 0.8438V
15:40:30 40.4'C 1100MHz 500MHz 00000000000000000000 0.8438V
15:40:33 41.3'C 1500MHz 500MHz 00000000000000000000 0.8438V
15:40:36 40.9'C 1500MHz 500MHz 00000000000000000000 0.8438V
15:40:39 40.9'C 1100MHz 366MHz 00000000000000000000 0.8438V
not that much more voltage...
i would think it is not your power supply.
1 Like
yup... luckily had the normal PSU nearby... switched it over and;
note: the -P -C 2 to generate moderate load... ( -P -C 4 will give you high load )
[root@dca632 /usbstick 60°] rpi-throttlewatch.sh -P -C 2
NPROC:4 RUNSSLBENCH:1 NPROC_SSL:2
starting opensslbench with 2 cores
Time Temp CPU Core Health Vcore
02:07:45 61.3'C 1500MHz 500MHz 00000000000000000000 0.8375V
02:07:48 61.8'C 1500MHz 500MHz 00000000000000000000 0.8375V
02:07:51 62.3'C 1500MHz 500MHz 00000000000000000000 0.8375V
02:07:54 61.8'C 1500MHz 500MHz 00000000000000000000 0.8375V
02:07:57 63.3'C 1500MHz 500MHz 00000000000000000000 0.8375V
^C
without load (perfect);
[root@dca632 /usbstick 54°] rpi-throttlewatch.sh
NPROC:4 RUNSSLBENCH:off NPROC_SSL:2
Time Temp CPU Core Health Vcore
02:14:34 55.0'C 1500MHz 500MHz 00000000000000000000 0.8375V
02:14:37 54.0'C 1100MHz 366MHz 00000000000000000000 0.8375V
02:14:40 54.5'C 1100MHz 366MHz 00000000000000000000 0.8375V
johnd2
2004
felt lucky...
stable uptodate: 5.0.19-63
not that it needed extra confirmation, but...
taskset-aarch64 -c 0,1,2,3 /bin/rpi-throttlewatch.sh -P -C 4
NPROC:1 RUNSSLBENCH:1 NPROC_SSL:4
starting opensslbench with 4 cores
Time Temp CPU Core Health Vcore
13:12:35 38.4'C 1500MHz 500MHz 00000000000000000000 0.8500V
13:12:39 39.9'C 1500MHz 500MHz 00000000000000000000 0.8500V
13:12:42 40.4'C 1500MHz 500MHz 00000000000000000000 0.8500V
13:12:45 40.4'C 1500MHz 500MHz 00000000000000000000 0.8500V
13:12:49 40.9'C 1500MHz 500MHz 00000000000000000000 0.8500V
no issues to report.
thanks!
1 Like
early adopters get the pain and the spoils... ( mostly pain 
)
#######[ /usbstick 57°] rpi-support.sh | grep upghist
###################### upghist_count: 427
###################### upghist_list: 3.0.17-108 2.7.39-7 2.7.39-9 2.7.15-60 2.7.33-16 2.7.39-16 2.7.39-23 2.7.39-26 2.7.39-30 2.7.39-31 2.7.39-33 2.7.39-35 2.7.51-5 2.7.51-15 2.7.51-19 2.7.51-20 2.7.51-25 2.7.51-28 2.7.51-32 2.7.51-56 2.7.51-62 2.7.71-3 2.7.75-2 2.7.75-4 2.7.75-5 2.7.75-6 2.7.75-17 2.7.75-18 2.7.75-19 2.7.75-22 2.7.75-23 2.7.75-25 2.7.75-26 2.7.75-27 2.7.75-27 2.7.75-31 2.7.75-35 2.7.75-36 2.7.77-3 2.7.77-6 2.7.77-7 2.7.77-9 2.7.77-10 2.7.77-11 2.7.77-23 2.7.77-26 2.7.77-27 2.7.77-29 2.7.90-2 2.7.90-3 2.7.101-2 2.7.105-3 2.7.133-2 2.7.136-2 2.7.139-2 2.7.139-3 2.7.136-4 1.0.15-5 1.0.15-6 2.7.139-5 1.0.15-7 2.7.139-5 2.7.139-7 2.7.139-8 2.9.17-2 2.9.17-3 2.9.17-14 2.9.17-17 2.9.17-18 2.9.33-3 2.9.17-21 2.9.17-30 2.9.17-35 2.9.17-37 2.9.17-39 2.9.17-51 2.9.17-54 3.0.3-2 3.0.6-2 3.0.6-3 2.9.17-90 2.9.17-90 2.9.17-105 2.9.17-111 1.0.35-2 2.9.17-116 2.9.17-116 2.9.17-116 3.0.15-2 2.9.17-119 2.9.17-123 2.9.17-125 3.0.17-2 3.0.17-7 3.0.17-7 3.0.17-8 3.0.17-7 3.0.17-23 2.9.17-128 3.0.17-30 3.0.17-36 3.0.17-37 3.0.17-51 3.0.17-51 3.0.17-55 3.0.17-59 3.0.17-59 3.0.17-69 3.0.17-71 3.0.17-96 3.0.30-2 1.0.3-6 1.0.3-8 3.0.17-102 3.0.17-103 3.0.17-105 3.0.17-106 1.0.3-10 1.0.3-15 1.0.3-16 1.0.3-18 1.0.3-19 3.0.17-113 3.0.17-115 3.0.17-116 3.1.5-2 3.0.17-120 3.1.31-2 3.0.17-130 3.0.17-130 3.1.9-4 3.1.9-9 3.1.9-11 3.1.9-12 3.1.9-14 3.1.9-24 3.1.9-27 3.1.9-29 3.1.9-36 3.1.9-54 3.1.9-57 3.1.9-59 3.1.50-2 3.1.9-65 3.1.9-69 3.1.9-90 3.1.57-2 3.1.57-27 3.1.57-28 3.1.57-29 3.1.57-39 3.1.57-52 3.1.57-51 3.1.70-2 3.1.57-50 3.2.13-2 3.2.13-2 3.1.57-50 3.2.13-2 3.1.57-53 3.2.13-3 3.2.13-3 3.1.57-57 3.1.57-63 3.1.57-68 3.2.55-17 3.2.55-20 3.2.55-21 3.2.55-23 3.2.61-2 3.2.61-17 3.2.61-30 3.2.69-6 3.2.61-36 3.2.91-2 3.2.61-39 3.2.61-39 3.2.61-39 3.2.61-39 3.2.61-39 3.2.61-39 3.2.61-41 3.2.61-42 3.2.61-42 3.2.61-43 3.2.61-43 3.2.61-43 3.2.61-45 3.2.61-46 3.2.61-47 3.2.61-50 3.2.61-51 3.2.61-55 3.2.61-55 3.2.61-60 3.2.61-61 3.2.61-62 3.2.61-62 3.2.61-63 3.2.61-63 3.2.61-65 3.2.61-66 3.2.100-2 3.2.61-72 3.2.100-3 3.2.100-3 3.2.100-5 3.2.100-6 3.2.100-7 3.2.100-9 3.2.100-10 3.2.100-11 3.2.100-11 3.2.100-12 3.2.100-54 3.2.100-55 3.2.100-65 3.2.100-67 3.2.100-69 3.2.100-69 3.2.100-70 3.2.100-71 3.2.100-73 3.2.100-75 3.2.100-75 3.2.100-77 3.2.100-79 3.2.100-79 3.2.100-89 3.2.100-90 3.2.100-94 3.2.100-94 3.2.100-94 3.2.100-99 3.2.100-99 3.2.103-4 3.2.107-5 3.2.111-2 1.0.5-2 1.0.5-2 3.2.107-5 1.0.5-2 3.2.107-5 3.2.130-3 3.2.130-5 3.2.130-5 3.2.130-7 3.2.130-9 3.2.135-2 3.2.137-2 3.2.137-2 3.2.137-9 3.2.150-2 3.3.3-3 3.3.3-3 3.5.5-4 3.3.3-3 3.5.5-7 3.5.5-8 3.5.5-8 3.5.5-9 3.5.5-11 3.5.5-7 3.5.5-14 3.5.5-17 3.5.7-2 1.0.3-2 3.5.17-2 3.5.7-6 3.5.35-3 3.5.35-7 3.5.37-2 3.5.53-2 3.5.37-7 3.5.56-2 3.5.56-4 3.5.61-2 3.5.61-8 3.5.59-2 3.5.56-3 3.5.65-2 3.5.67-2 3.5.75-2 3.5.75-6 1.0.3-7 3.5.75-7 3.5.95-5 3.5.95-6 3.5.99-2 3.5.99-5 3.5.99-12 3.5.99-18 3.5.99-19 3.5.99-22 3.5.99-22 3.5.99-23 3.5.99-25 1.0.6-2 1.0.6-4 1.0.6-4 1.0.6-5 3.5.99-31 3.5.99-32 3.5.101-2 3.5.101-5 3.5.101-6 3.5.136-2 3.5.136-2 3.5.136-2 3.5.136-2 3.5.136-2 3.5.136-2 3.5.139-2 3.5.139-3 3.5.139-4 3.5.139-5 3.5.139-11 3.5.139-12 3.5.139-16 3.5.139-19 3.5.139-20 1.0.7-2 1.0.7-2 3.5.139-20 3.5.151-4 3.5.151-7 3.5.151-8 3.5.151-12 3.5.151-31 3.5.151-32 3.5.151-33 3.5.139-23 3.5.301-2 3.5.151-36 1.0.7-3 3.5.151-37 3.5.305-2 3.5.305-5 3.5.305-8 3.5.305-10 3.5.307-3 3.5.305-18 3.5.315-2 3.5.315-5 3.5.315-7 3.5.317-2 1.0.10-2 1.0.10-3 3.5.317-5 3.5.317-6 3.5.317-12 3.5.317-14 3.5.317-23 3.5.330-2 3.5.331-9 3.5.337-3 5.0.11-3 5.1.13-4 5.0.11-3 5.0.11-4 5.0.11-7 5.0.11-8 5.0.11-9 5.0.11-13 5.0.11-14 5.0.11-16 5.0.11-16 5.0.11-24 5.0.11-26 1.0.13-2 1.0.13-4 5.0.11-30 5.0.11-31 5.0.11-32 1.0.57-2 1.0.57-3 5.0.11-32 5.0.11-38 5.0.11-40 5.0.11-42 5.0.11-43 5.0.11-45 5.0.11-58 5.0.19-5 5.0.19-6 5.0.19-7 5.0.19-11 5.0.11-59 3.5.331-13 1.0.7-3 5.0.19-11 5.0.19-12 5.0.19-21 5.0.19-22 5.0.11-63 5.0.11-65 5.0.11-66 5.0.11-67 5.0.11-67 5.0.11-69 5.0.11-73 5.0.19-24 5.0.19-26 5.0.19-27 5.0.19-28 5.0.19-31 5.0.19-31 5.0.19-36 5.0.19-38 5.0.36-3 5.0.36-3 5.0.19-39 5.0.19-39 5.0.11-73 5.0.11-73 5.0.19-40 5.0.19-41 5.0.19-42 5.0.19-45 5.0.19-50 5.0.19-51 5.0.19-52 5.0.19-53 5.0.19-60 5.0.19-62 5.0.19-59 5.0.19-63
2 Likes
neil1
2006
I want to move back to release 
UPDATECHECKURL="https://raw.github.com/wulfy23/rpi4/master"
UPGRADEsFLAVOUR="release"
I changed to release but nothing happened. Doing something wrong?
1 Like
cd /tmp/
wget http://rpi4.wulfy23.info/builds/legacy/rpi-4_21.02.1_1.0.13-3_r16325_extra/rpi4.64-21.02.1-27230-1.0.13-3-r16325-ext4-sys.img.gz
sysupgrade -R /tmp/rpi4.64-21.02.1-27230-1.0.13-3-r16325-ext4-sys.img.gz
will get you the last 21.02 build that was made...
there is currently no 'release' 'auto-advertised'...;
- original is a little old and
- subsequent 'updated' builds are not really confirmed good and
- 21.02.2 is imminent
so not much point upgrading (everyone) till that is out...
1 Like
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"
1 Like
hey, sorry for late response,
- does usb-modewitch cause specific issues for you?
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).
1 Like
added... 
quite alot of people ask about usb-wifi dongles so grateful to see one working...
peexl
2013
Hello @anon50098793, First I want to say thank you for sharing this wonderful build and for the work you put on it.
My question is: what's the best way to execute a script on firstboot before packagesrestore?
I have a script that need to be executed once on every reboot in order to enable my Internet connection.
For now I have that script in /etc/custom/startup/5-internet and it's working fine but not after an upgrade.
Is putting this file in /etc/custom/firstboot/ and adding it to /etc/sysupgrade.conf the good way ?
1 Like
good question
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)
1 Like
neil1
2015
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.
1 Like
neil1
2017
[root@network /]# dmesg | grep https
[root@network /]#
1 Like
please put this in your /root/wrt.ini for the next upgrade...
HTTPS_DNS_DEBUG=1
and whenever it does not work... PM me the output of logread | grep https
1 Like
please also try enabling this setting in network > dhcp + dns > advanced > [no-negative-cache];
(you can turn it off in a few weeks if it has no effect)
neil1
2021
Done.
I am also testing IPTV stream and it stops working after few mins.
1 Like
