Wow, I thought, give it a try, maybe ‘Team BPi’ learned in the meantime how to do it better. Just to realize that it’s as bad as always.
After flashing the image you can’t do literally anything since there are ZERO BYTES free:
Filesystem Size Used Avail Use% Mounted on
/dev/root 3.9G 3.7G 0 100% /
devtmpfs 373M 0 373M 0% /dev
tmpfs 501M 68K 501M 1% /dev/shm
tmpfs 501M 6.9M 494M 2% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 501M 0 501M 0% /sys/fs/cgroup
/dev/mmcblk0p1 256M 45M 211M 18% /boot
tmpfs 101M 4.0K 101M 1% /run/user/1000
/dev/mmcblk1p1 7.2G 145M 6.7G 3% /media/pi/3684f9bd-1ea5-4cd0-a75b-b47af6147d77
tmpfs 101M 0 101M 0% /run/user/0
Why don’t you implement auto fs expansion?
Then you managed to f*ck up throttling settings and with this combination of kernel + sysconfig.fex maximal cpufreq is limited to 1008 MHz. Then your THS settings are really crappy since they lead to killed CPU cores. I’m currently running your insane Raspbian image with a typical Phoronix benchmark and already two CPU cores are killed:
root@bananapi:/# grep -c processor /proc/cpuinfo
root@bananapi:/# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
root@bananapi:/# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
Using Rasbian is already crap (slow ARMv6 code!) but with your THS settings on top this ensures to get the slowest H3 device in the world. Running Armbian instead of your crappy Raspbian image the M2+ might perform over twice as fast (since with Armbian you have a quad core SBC running at 1.2GHz and with this horrible Raspbian thing only a dual core SBC running at 1GHz).
C’mon: Why don’t you test the stuff you’re working on? It’s unvelievable that you spend time on producing such a mess.