gounthar

This board might meet your requirements, except of the price tag ... you may regard it as an upper bound.
 
https://www.solid-run.com/arm-servers-networking-platforms/honeycomb-workstation/

I do love the XU4, but it only sports 2GB of RAM.

The Utilite Pro has 2GB of RAM only, the Cubox-i has a variant (4x4) with 4 GB. Both share the same imx6 SoC, which is way slower than the Exynos 5422 from the XU4.
The Utilite Pro uses an internal msata ssd (which can be replaced), the Cubox-i has an esata connector (both with 3.0 Gbps).
 

https://en.t-firefly.com/product/industry/itx3588j
 

I was very happy to realize that the raspberry is now also supported. Many have waited a long time for this.
I immediately wrote an article about it on gnulinux.ch.
Hopefully this will not be a half-hearted project.
I also think it would be an advantage if Armbian would appear as a distribution on the Raspberry download page

Just noticed how small the M1 MacMini mainboard is... 
 
I'm surprised it even has a fan, they could have done a heat pipe to the housing, and that likely would have been "good enough"  - that's the nice thing about my MBAir-M1, no fans, it's dead silent.
 

Something to consider for your CI/CD pipeline...
 
https://www.servethehome.com/oracle-cloud-giving-away-ampere-arm-a1-instances-always-free/
 
There is always AWS, but that ain't free...

The kernel got correctly updated tonight.
 
Welcome to Armbian 22.02.1 Focal with bleeding edge Linux 5.16.10-bcm2711 Docker now works.
Thanks a lot for your work.

I'd consider this one ... https://www.hardkernel.com/shop/odroid-xu4-special-price/ 

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

Yes, hw decoding works out of the box for mainline linux kernel.

Thank you for your generosity! 
 
The Armbian community is doing a really great job. I am still grateful for all the help I found here when I had a problem with my Helios64. (Remember that? https://forum.armbian.com/topic/18855-upgrading-to-bullseye-troubleshooting-armbian-21081/?do=findComment&comment=129711 )
 
 
Today I'm not coming to ask for help (since my NAS is working perfectly fine!) but to say hi to everyone.
 
And reading your positive message, Amix73, you even made me want to make a small donation. 
 
Thanks again, everyone!
 

5.10 is ancient for video decoding purposes. Codecs started stabilizing after 5.11. With 5.14 you'll have stable and fully working MPEG2, VP8 and H264. If you need low effort solution, build latest gstreamer 1.20 RC with gst-plugins-bad with one of the latest kernels. With proper pipeline, it works. If you need out of the box solution, use LibreELEC distro.

Hi all. In this video I show how to install Open Media Vault on your SBC with Armbian Buster.
I've used the Odroid HC4, this is the same for any board you'd like to use. 
Here my video.
Greetings.
NicoD

It is possible that there are some options missing from armbianEnv.txt. On my Banana Pi M2 Zero, beyond setting the overlays, some additional settings had to be added to armbianEnv.txt. These options are:
param_spidev_spi_bus=1 param_spidev_spi_cs=0 If I understood the page about the OrangePi Zero (https://linux-sunxi.org/Xunlong_Orange_Pi_Zero), using BUS 1 and CS 0 should work (however, I don't have one to test).
 
You can find a more complete description about all possible parameters for armbianEnv.txt for the H3 on the page https://github.com/armbian/sunxi-DT-overlays/tree/master/sun8i-h3

Moved to Common issues / peer to peer technical support since unsupported image/build.

ver 20211219 kernel 5.15.10
fan work

Your GPS module may contain a well disciplined temperature compensated RTC and oscillator (most do), and there is a possibility that it may be able to provide accurate PPS output and NMEA time messages for a period even if there is no GPS signal, if programmed to do it.  (This is called holdover mode and some modules can do it, although the affordable ones may not offer this).

Many years ago I made PPS generator with a quartz xtal in an oven composed of a large TO220 transistor clamped to the xtal and surrounded by polystyrene.  The transistor was it's own temperature sensor, and the simple circuit maintained a steady temperature.  An 8048 programmed in assembler divided the oscillator down to 1Hz and added an extra unit to the division every now and then to compensate for the quantization error to get a final drift of about 4 parts per million.

The oven used the same principal as the link below, but the bigger transistor gave a better thermal coupling.  Something like this could provide stable temperature for any RTC.  https://www.romanblack.com/xoven.htm

Hi gounthar,
Sorry that I'm way to late to this party.  But if you are still interested.... 

I've built a GPS disciplined time server using ESP8266.  Jitter is way too high, the onboard oscillator is jittery and the WiFi module has variable latency.

I'll link you to a tutorial that I wrote for GPS discipline on OrangePi zero (should work for other boards to)
I get jitter of less than +- 20 microseconds with temperature control at 57 degrees C  about +-60 microseconds without temperature control.

EDIT: I read my tutorial again and note that you already responded to it. 
I'll leave this here in case it's useful to others finding your thread.
 

A few months back I came across something interesting on David Taylor's web site.
A shell script to control the temperature of a SBC using the heat generated by the CPU.
Of course if your clock oscillator is integrated into the CPU then this is a way to control it's temperature and theoretically get more accurate time.
I tried this and it worked really well with a few tweaks.  I liked it so scripted it as a service.
I'm getting a maximum offset of less than +-20 micro seconds

http://www.satsignal.eu/ntp/Raspberry-Pi-ntpheat.html
 
#!/usr/bin/env python # # Requires python3 # generate some heat! # # Run ntpheat in the background. # It will try to stabilize the CPU temperature at 54C by default. # Sometimes one copy of ntpheat can use 100% of one CPU and #!/usr/bin/env python # # generate some heat! # # Run ntpheat in the background. # It will try to stabilize the CPU temperature at 54C by default. # Sometimes one copy of ntpheat can use 100% of one CPU and # still not heat up your Pi as much as you want. The temptation # is to add more insulation to your Pi, but then it will overshoot # your target temperature if your load factor goes high. # # The solution is to run more than one copy of ntpheat. This is # easy to do with the -c option. # # To run 3 copies of ntpheat: ntpheat -c 3 import argparse import hashlib import os import sys import time # Work with argvars parser = argparse.ArgumentParser(description="make heat") parser.add_argument('-c', '--copies', default=[1], dest='copies', help="Number of copies to run. Default is 1", nargs=1, type=int) parser.add_argument('-t', '--temp', default=[57.0], dest='target_temp', help="Temperature to hold. Default is 57.0", nargs=1, type=float) parser.add_argument('-w', '--wait', default=[0.001], dest='wait', help="Set delay time in seconds, default is 0.1", nargs=1, type=float) args = parser.parse_args() args.copies[0] -= 1 while args.copies[0]: args.copies[0] -= 1 pid = os.fork() if pid: # I am the fork break zone0 = '/sys/class/thermal/thermal_zone0/temp' cnt = 0 m = hashlib.md5() temp = 0 max_cnt = args.wait[0] * 100000 # on a RasPi 3 the temp steps seem to be about 0.537 to 0.539C temp_gate = args.target_temp[0] while True: # on a RasPi 3, 200,000 of the m.update() can be one second delta = temp_gate - temp if 0 < delta: # heat it up my_str = "Time is an illusion. Lunchtime doubly so." my_enc = my_str.encode('utf-8') m.update(my_enc) else: cnt = max_cnt # cools off slower than it heats up. # undocumented Python 'feature', no sleep less than 1 milli Sec sleep = args.wait[0] * 10.0 * -delta if 0.001 > sleep: sleep = 0.001 time.sleep(sleep) cnt += 1 # read the temperature every max_cnt if max_cnt < cnt: cnt = 0 zone_data = open(zone0, 'r') for line in zone_data: temp = float(line) / 1000 zone_data.close() The service file: ntpheat.service - if you don't know how to set up a systemd service then go here https://wiki.debian.org/systemd/Services
[Unit] Description=ntpheat [Service] ExecStart=/usr/bin/ntpheat.sh Restart=on-failure [Install] WantedBy=multi-user.target  

 
I should add:  To make the CPU based temperature control work, there must be no CPU intensive processes at all.  This means disabling any cron jobs that load the CPU or forcing them to use less CPU over a longer period.
To do this you need cgroup-tools
 
#spread out heating caused by scheduled maintenance on NTP server #get package sudo apt-get install -y cgroup-tools #create a cpu group called cpulimit sudo cgcreate -g cpu:/cpulimit #set cpulimit group limit to 100000uS out of 1000000uS (= 10% of CPU cycles) sudo cgset -r cpu.cfs_period_us=1000000 cpulimit sudo cgset -r cpu.cfs_quota_us=100000 cpulimit #check settings sudo cgget -g cpu:cpulimit #to limit your process start it as follows - sudo cgexec -g cpu:cpulimit YOUR_COMMAND
You can use this to run CPU intensive jobs at 10%
To reconfigure some cron jobs:
 
/etc/cron.d/armbian-updates @daily root cgexec -g cpu:cpulimit /usr/lib/armbian/armbian-apt-updates
Some cron jobs run scripts:
#for some cron scripts: /etc/cron.daily/apt-show-versions cgexec -g cpu:cpulimit apt-show-versions -i /etc/cron.daily/sysstat cgexec -g cpu:cpulimit exec /usr/lib/sysstat/sa2 -A Apt xapian index is a hog...  limit it to 5%
#create a cpu group called cpulimit5 (for 5% CPU) sudo cgcreate -g cpu:/cpulimit5 #set cpulimit group limit to 25000uS out of 500000uS (= 5% of CPU cycles) for bad process. sudo cgset -r cpu.cfs_period_us=500000 cpulimit5 sudo cgset -r cpu.cfs_quota_us=25000 cpulimit5 /etc/cron.weekly/apt-xapian-index - comment out all except top line and replace with cgexec -g cpu:cpulimit5 /usr/sbin/update-apt-xapian-index
 

The documentation on the Orange Pi Zero Plus 2 is somewhat scarce. I couldn't find information on the GPIO map for the 26-pin header anywhere, but I manually mapped it. I did this with an LED on each successive pin and testing through the /sys/class/gpio driver until I found the one to control it. This caused a bunch of resets and eventually corrupted my sd card, but I got the info
 
Each of the numbers below is the GPIO number used for /sys/class/gpio. For example, 110 means gpio110. The list is by pin number from 1 to 26. A value of -1 means unavailable (as far as I could discover):
 
-1, -1, 12, -1  (pin 1,2,3,4)
11,-1,6,0 (pin 5,6,7,8)
-1,1,352,107 (pin 9,10,11,12)
353,-1,3,19 (pin 13,14,15,16)
-1,18,-1,-1 (pin 17,18,19,20)
-1,2,14,13 (pin 21,22,23,24)
-1,110 (pin 25, 26)
 
I've added this table to my SPI_LCD project to make it easier to use for generic GPIO access without having know the details of working with the sysfs kernel driver: https://github.com/bitbank2/SPI_LCD
 
P.S. The red LED on the board is mapped to GPIO17
 

OK, so no answers  Well as usual I pressed on. My first mistake was using JNA generation (but it was easy), so I researched JNI. Well JNI is very cumbersome to do by hand, so I looked for a JNI code generator and found one call HawtJNI. Of course it wouldn't work with Java 11 which is the Java LTS version, so I created a fork. Use the JDK11 branch if you want to play with it because I don't know if the PR will be accepted. I started wrapping c-periphery since it now supports the new /dev/gpiochip way of accessing the GPIO chips. I ran a performance test (I validated on a scope) and I'm getting ~235 KHz on a v1 Nano Pi Duo! That's over 500K writes per second compared to 2K using JNA and libgpiod. Even python-periphery yields ~37 KHz which is a pure Python version.
 
Any ways exciting news for bit bangers of the world or anyone needing high performance GPIO. Once I have the GPIO code working I'll post on my Github site and announce. Since Bulldog only supports three boards this is good news for Armbian folks with a wider array of supported boards. I still need to test ARMv8 64 bit.

@orangepie14
 

..about power outages..
 
I had this problem years argo also.
I run a server (Orange Pi PC) 24/7 in a area with a lot of "power outages".

I prevent this with a board like this: Double 18650 Lithium-Batterie Schild V8 Mobile Power bank
 
 
 
You have only to connect it between your power source and you Pi.
 
That's all..
 
Markus

Use:
 
 ./compile.sh CREATE_PATCHES="yes"
change sources when asked and a patch will be created / updated. Once done, copy that patch to the patck/kernel/sunxi64-edge/ folder and pay attention to the patch executing order. Hint - if you need that patch is executed last, add higher number or simply xx in front of the patch filename.
 
For adding an overlay, check this patch: https://github.com/armbian/build/blob/master/patch/kernel/archive/sunxi-5.15/general-sunxi-overlays.patch

I did next few moves:
Change sun8i-r40.dtsi  
Change sun8i-r40-bananapi-m2-ultra.dts  
Compile ffmpeg (options you can get from log message above) Compile codec driver sunxi-cedar Remove cma option from kernel command line (it cause conflict with SRAM described in DTS)