xwiggen

just use sensors, cpu temp is measured

you could use sensors from lm-sensors

plug in additional wifi dongle; one for ap one for client

probably ipv6 misconfigured, so better play nice and use dns-over-https option.

Have you tried powering through GPIO pins?

The BOARD etc variables are imported in /etc/profile.d/armbian-check-first-login.sh, which in turn is only loaded in interactive login shells.

source /etc/armbian-release echo $BOARD

nfnetlink is the comms between userspace iptables/ipset and kernel

[ 7.102323] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator [ 7.102338] cpu cpu0: _opp_add: OPP not supported by regulators (1104000000) [ 7.102518] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator [ 7.102526] cpu cpu0: _opp_add: OPP not supported by regulators (1200000000) [ 7.102703] core: _opp_supported_by_regulators: OPP minuV: 1340000 maxuV: 1340000, not supported by regulator [ 7.102710] cpu cpu0: _opp_add: OPP not supported by regulators (1296000000) [ 7.102868] core: _opp_supported_by_regulators: OPP minuV: 1400000 maxuV: 1400000, not supported by regulator [ 7.102875] cpu cpu0: _opp_add: OPP not supported by regulators (1368000000) [ 7.103311] thermal thermal_zone0: binding zone cpu_thermal with cdev thermal-cpufreq-0 failed:-22

cpufreq working?

modprobe -v nfnetlink ?

add to armbianEnv.txt: extraargs=fsck.mode=force fsck.repair=yes

Can you compare the dts of this kernel with earlier kernel? (v20.02 -- arch/arm/boot/dts especially cpu entries) Seems like upstream did refactoring, I didn't want to touch anything since I've no way of testing changes.

have you tried swapping SD+PSU+cable to rule out any hardware issues?

Mounting / as read-only is for forensic purposes, journal etc won't be committed, i.e. nothing new is flushed to SD.

var/log should already be ram (zramctl) in sync. non-persistent logging defeats the purpose. what you can do is log to /tmp (tmpfs) en set logrotate entry to /tmp/... with the options you mentioned.

bashrc is supposed to be for interactive uses, I don't really know how getty interpretes this and it's difficult debugging from another end. Anyhow, the best/conventional method to do what you want is by writing a systemd service such as https://www.raspberrypi-spy.co.uk/2015/10/how-to-autorun-a-python-script-on-boot-using-systemd/, which basically describes your usecase though omits User= specification.

Try changing /var/log/smartbit/goccp.log to /var/log.hdd/smartbit/goccp.log /var/log is a ramlog mount that's synced underwater to /var/log.hdd to decrease SD writes.

Try updating 20-autologin; [Unit] ... Wants=graphical.target After=graphical.target ...

How do you autologin with user?

yes this is an issue with newest downloadable buster image, been meaning to fix that but no time yet at hand. workaround for classic specification (/etc/network/interfaces) auto eth0 iface eth0 inet dhcp hwaddress ether 12:34:56:78:9A:BC or set dhcp-client-identifier 12:34:56:78:9A:BC in dhclient.conf (https://linux.die.net/man/5/dhclient.conf)

ssh -X

Altera?

Did you try NFS? SMB3 traffic might be encrypted. It took my H3/GbE a lot of sweat transferring 2TB onto USB thru SMB3 earlier this week.

other alternative; raspberry pi imager. https://www.raspberrypi.org/downloads/