Werner

https://github.com/armbian/build/issues/3066

nanopim4v2 rc.local[3751]: /etc/rc.local: 16: echo: echo: I/O error  
That's the script error, probably line 16. Not sure why it failed. I don't see anything obviously wrong.
 
Depending, it's possible the kernel is still initializing the PWM device at the time it runs. You can add some print statements like "echo HERE" to you script to confirm where it dies. You can try to add a delay like a "sleep 30" at the start of the script, but that's just a guess. Not sure why you'd be getting an I/O error.
 
It's also possible that there's some kernel version differences between the FriendlyElec build and Armbian's kernel, so that scripting might need some changes.
 
For example, I had to do this to turn on the PWM fan on my M4V2 metal case. You may need to experiment a bit.
 
echo 0 > /sys/class/pwm/pwmchip1/export echo normal > /sys/class/pwm/pwmchip1/pwm0/polarity echo 50000 > /sys/class/pwm/pwmchip1/pwm0/period echo 40000 > /sys/class/pwm/pwmchip1/pwm0/duty_cycle echo 1 > /sys/class/pwm/pwmchip1/pwm0/enable  
 
Edit: As a note, my M4V2 had pwm0 set as inverted by default. Your settings of 90% power could be interpreted as 10% instead, and may not be enough for the fan to spin.

Mandatory for proper testing. Everyone who tinkers with SBCs should have such a thing. Also they are dirt cheap.

Man we really need to write the definitive sermon on this and add it to faq / documentation.     I think there might be an issue open for it somewhere 

Here is early work for proper XR819 mainline support. Tests reports are welcome, to see if it is actually any better than vendor driver. I got reasonable speed using it and only problem I can see is that suspend doesn't work. Of course, developer tests rarely last more than a few minutes, so long term stability isn't known.
 
Note, I extracted pretty recent FW binaries from H616 Android box, which should be better than old ones, in theory.

I found the culprit. Patch https://github.com/armbian/build/blob/master/patch/kernel/archive/sunxi-5.13/board-h6-orangepi-lite2-fix-missing-all.patch messes up HDMI node, which then doesn't properly enable DDC lines and then in turn, HDMI driver can't read EDID.
 
@Igor any reason for above patch to be so big? OPi Lite2 is pretty well supported in 5.13. Only nodes which are not present in mainline are spi0, usb3phy and dwc3. Patch can be much smaller...

Thank Jernej. Fixed, but I also can't test.
https://github.com/armbian/build/commit/f83100f9af5f5b8ef5a0b083e39c382763e2e86f

I trade my skills for help on tasks that doesn't require so much skills, but they still require time and attention.
https://forum.armbian.com/forum/54-help-wanted/
 
Currently working on sunxi bump to 5.13.y but since I am on vacations, my wife can interrupt this violently  If time permits, I'll try to fix this, but can't promise.

Once we get hands on some hardware (and somebody is willing to spend time on) it probably will sooner or later. Basic support for newer RK chip has already been pushed to mainline Linux.

You cannot run ARM binaries on Intel architecture and vice versa without some kind of emulation. Ideally you pick up a binary for the matching architecture.
Also since you did not tell which program you try to run there is no way to help any further.
 

Another bump of forum software to v4.6.4. What's new: https://invisioncommunity.com/release-notes/

Good for you, you deserve it.
 
No wonder your tone is more calm than usual. 

Your priorities are correct

Sorry could not participate, important private stuff. bride elect wanted to discuss wedding plans

This problem should be resolved. CDN needs several hours ... so perhaps not right now.

.config file matching the installed kernel is always in /boot.

It looks like that even with latest patches is 1.2 GHz mode unstable on more boards. Therefore there is a proposed patch which completely disables cpufreq driver on 1.2 GHz variant of all A3720 SoC including Espressobin:
https://lore.kernel.org/linux-pm/20210630135942.29730-1-kabel@kernel.org/t/#u
 
If you have any input on this or reaction from Marvell / GlobalScale, please reply.

https://github.com/armbian/build/pull/2907

Glad you have fun with it
 

Hi al.
I've finished my review of the PineBook Pro. I just love this thing. Runs great with Armbian.
Here my video.
Here all my gathered information:
 

This is forum - you are welcome to talk about, but demanding support is a bad idea. You can report bugs here but only if you pay commercial price for fixing it & if we agree / are free to accept a deal or if you will be the one fixing it.
 
 
By who? Why? Several years ago (i would estimate about 5 years) we have concluded its not possible without breaking others or without severe framework customisation / rework ... This is when incompetent people are making hardware and when you expect software can fix all those mistakes in this chaotic world. And you also believe we have to waste our private money for that. Attitude. Open source is not slavery.

That gave my videos a sudden boost. Thank you

Had similar report for a user of stable helios4 after their rootfs package updated. 
 
Ive modified jira issue to reflect broader scope

Needs to be checked. https://armbian.atlassian.net/browse/AR-822?atlOrigin=eyJpIjoiZWQzYjJiZjM3NDEwNDY5Y2IxMzI2ZWRiZTRlZDRmYjciLCJwIjoiaiJ9
 
To reduce wear on sdcard logs are written to a ramdisk and only synced periodically. To debug such things the best way is to put a serial console to it and log everything from there.

Feel free to try to add it to armbian-config.
https://github.com/armbian/config
The script is indeed dated. And no devs have time to work on it.
I've always manually set it up in /etc/rc.local.