guidol

@balbes150 Thanks for the .deb packages from 5.76 to 5.77
 
for "normal" armbian-releases I did add me a package-information at the end of the file /etc/update-motd.d/10-armbian-header
ARMBIAN_bsp=$(more /etc/armbian-release|grep VERSION|cut -f 2 -d '=') ARMBIAN_kernel=$(dpkg -s linux-image-$BRANCH-$LINUXFAMILY|grep Version|cut -f 2 -d ' ') ARMBIAN_uboot=$(dpkg -s linux-u-boot-$BOARD-$BRANCH|grep Version|cut -f 2 -d ' ') ARMBIAN_dtb=$(dpkg -s linux-dtb-$BRANCH-$LINUXFAMILY|grep Version|cut -f 2 -d ' ') ARMBIAN_firmware=$(dpkg -s armbian-firmware|grep Version|cut -f 2 -d ' ') ARMBIAN_config=$(dpkg -s armbian-config|grep Version|cut -f 2 -d ' ') printf 'package bsp-kernel[\e[0;91m%s\x1B[0m] u-boot[\e[0;91m%s\x1B[0m] dtb[\e[0;91m%s\x1B[0m] firmware[\e[0;91m%s\x1B[0m] config[\e[0;91m%s\x1B[0m]\n' "$ARMBIAN_kernel" "$ARMBIAN_uboot" "$ARMBIAN_dtb" "$ARMBIAN_firmware" "$ARMBIAN_config" printf '\n' for your armbian-version I had to change the "source" because you didnt use as much environment-variables like the "real" one
 
ARMBIAN_bsp=$(more /etc/armbian-release|grep VERSION|cut -f 2 -d '=') ARMBIAN_kernel=$(dpkg -s linux-image-aml-s912|grep Version|cut -f 2 -d ' ') ARMBIAN_uboot=$(dpkg -s linux-u-boot-aml-s912-default|grep Version|cut -f 2 -d ' ') ARMBIAN_dtb=$(dpkg -s linux-dtb-aml-s912|grep Version|cut -f 2 -d ' ') ARMBIAN_firmware=$(dpkg -s firmware-armbian-full|grep Version|cut -f 2 -d ' ') ARMBIAN_config=$(dpkg -s armbian-config|grep Version|cut -f 2 -d ' ') printf 'package bsp-kernel[\e[0;91m%s\x1B[0m] u-boot[\e[0;91m%s\x1B[0m] dtb[\e[0;91m%s\x1B[0m] firmware[\e[0;91m%s\x1B[0m] config[\e[0;91m%s\x1B[0m]\n' "$ARMBIAN_kernel" "$ARMBIAN_uboot" "$ARMBIAN_dtb" "$ARMBIAN_firmware" "$ARMBIAN_config" printf '\n' but now its works too
 
armbian-aml-S912 shows 5.73 because of the package
 
linux-stretch-root-rockpro64    5.73   
Login with the new released puTTY 0.71  ==> https://www.chiark.greenend.org.uk/~sgtatham/putty/changes.html
 

WiFi is working on OPi3, but you need to manually tweak the firmware and reboot :
mv /lib/firmware/brcm/brcmfmac43455-sdio.bin /lib/firmware/brcm/brcmfmac43455-sdio.bin-ORIG mv /lib/firmware/brcm/brcmfmac43455-sdio.txt /lib/firmware/brcm/brcmfmac43455-sdio.txt-ORIG cp /lib/firmware/rkwifi/fw_bcm43456c5_ag.bin /lib/firmware/brcm/brcmfmac43455-sdio.bin cp /lib/firmware/rkwifi/nvram_ap6256.txt /lib/firmware/brcm/brcmfmac43455-sdio.txt  

Right ! Those are Ok !
That one of the reason there is no hurry to fix memory-leak issue, since I'm probably the only one who is using "dynamic" userspace method ...

OK - I will learn one possibility after another  For today I reached my goal

hiya @lanefu - thank you! more armbian boards are welcome (i had an orangepi on hand) if anyone would like to add support for their boards - we have libgpiod for easy-gpio control and use spidev/smbus for i2c/spi so adding other chips and boards is less than a day of effort
 
we can help and mentor if you're not sure how - please open an issue or create a PR here https://github.com/adafruit/Adafruit_Blinka
 
your devboard will get access to nearly 150 drivers and libraries - from OLEDs to sensors to LoRa radios - and more always on the way
https://github.com/adafruit/Adafruit_CircuitPython_Bundle/blob/master/circuitpython_library_list.md

I like the armbian-system-packages  armbian header information. Will modify my rock64 to output the additional information.   Thanks for the tip!
 
 
 

Yes, HDMI works. Enabling it in DTS + the a64-de2 bus in config is enough.

only added the second last printf, and of course the variable initialisation

When I did start I also did think I need every bullet-point - you are not alone
In the future if you want to be a bit more risky, then you could use
./compile.sh EXPERT="yes"

I didn't have one. I always used prebuild images.
Now this seems a lot easier than what I thought. I had tried multiple times in the past to follow these instructions
https://docs.armbian.com/Developer-Guide_Build-Preparation/
What do I need? x86/x64 machine running any OS; 4G ram, SSD, quad core (recommended), VirtualBox or similar virtualization software (highly recommended with a minimum of 25GB hard disk space for the virtual disk image), Setting up VirtualBox and compile environment is easy following our Vagrant tutorial, Docker environment is also supported for building kernels and full OS images, The only supported compilation environment is Ubuntu Bionic 18.04 x64 (no other releases are supported! It has to be exactly 18.04 otherwise default compiler versions might not match so if you’re on an older Ubuntu release upgrade to 18.04 now, if you use a newer Ubuntu version start with 18.04 from scratch), installed basic system, OpenSSH and Samba (optional), no spaces in full path to the build script location allowed, superuser rights (configured sudo or root shell). I thought you needed every bullet point, and I never could run vagrant right. I didn't know what it did, and didn't know why I needed it.

Even this I had done, I was in the build directory  If only I had typed ./compile.sh
apt-get -y install git git clone https://github.com/armbian/build cd build Only the last step not. So stupid. Thank you so much, it's clearly a lot more simple than I made it look in my brain. I've now got mini.iso, and started the build process.
It's one of the most simple things, while my autistic brain made it take months just by not wanting to understand it's simple.
Well. Nothing is hard, when you know how to do it.

Didnt you already got a armbian-build-system?
 
If not - why use vagrant and not only the minimal-18.04 Ubuntu in a VirtualBox?
 
I do only use Virtualbox and there there the is installed the mini-iso of 18.04 64Bit.
 
I used this page as information: https://github.com/armbian/build
 
If you got 18.04 minmal 64Bit installed  (including configuring the network) - all you/I had to do is
 
apt-get -y install git git clone https://github.com/armbian/build cd build ./compile.sh @NicoD BTW: The "vagrant"-page seems to be old because of VirtualBox 5.1.12 (now we are up to 6.04) and 
Ubuntu Xenial (we are now using 18.04 Bionic)

Something else I tried. The Armbian Terracotta Army. I need to add textures to the ground.

I've tried to make a build system today. I've gotten so far to get the newest version of vagrant installed and up. But then I clearly forgot about it. I noticed hours later that virtualbox was running. I'm getting closer to building one

I've finished the Armbian Terracotta Army. Here is a HQ render of it.
It's maybe too busy, but it's something different.




 

Armbian has now the new OrangePi3 WIP !
WiFi and eMMC tested ...
 

Because of the dmesg-error-Message 
[    9.557455] cfg80211: loaded regulatory.db is malformed or signature is missing/invalid I rechecked the regulatory.db and did found 2 more files to install 

1.) new pem-certificate ( sforshee.key.pub.pem <-- for signature )
2.) new regulatory.bin
 
In the archive 
http://ftp.be.debian.org/pub/software/network/wireless-regdb/wireless-regdb-2019.03.01.tar.gz
or at
https://git.kernel.org/pub/scm/linux/kernel/git/sforshee/wireless-regdb.git/plain/
you could find the files:
regulatory.db
regulatory.db.p7s
regulatory.bin
sforshee.key.pub.pem
sforshee.x509.pem
 
copy 
from the archive directory wireless-regdb-2019.03.01 to:
regulatory.db        to /lib/firmware  regulatory.db.p7s    to /lib/firmware  regulatory.bin       to /lib/crda sforshee.key.pub.pem to /lib/crda/pubkeys/ (reboot)
[    9.519254] cfg80211: Loading compiled-in X.509 certificates for regulatory database  
wireless-regdb-2019.03.01.zip

No need to worry about this failure, if I remember, those clm blobs are used to determine countries and allowed channels...

I will try that, I don't think it's easy to do.
I now done a clear background with the color of the current background image. I like this one too.

YES  I like it in red!

I have watched this thread and decided to check the status of the mainline kernel 5.0 for the H6 with the @Icenowy 's work on top of it.
I can say it works really nice (tested on Orange Pi 3 H6):
* HDMI
* DVFS
* Gbps / ethernet
 
I have prepared a blindly DT that should work on Opi 3 H6: https://github.com/avafinger/orangepi-h6-ubuntu-base-minimal/tree/master/dts
 @Igor , Basically fetch the mainline kernel 5, apply your patch set on top and add/modify my DT.
 
I have tried to add i2c and spi but it did not work as i expected.
I had something like this:
For the i2c
        i2c0: i2c@5002000 {             compatible = "allwinner,sun6i-a31-i2c";             reg = <0x05002000 0x400>;             interrupts = <GIC_SPI 4 IRQ_TYPE_LEVEL_HIGH>;             clocks = <&ccu CLK_BUS_I2C0>;             resets = <&ccu RST_BUS_I2C0>;             status = "disabled";             #address-cells = <1>;             #size-cells = <0>;         };         i2c1: i2c@5002400 {             compatible = "allwinner,sun6i-a31-i2c";             reg = <0x05002400 0x400>;             interrupts = <GIC_SPI 5 IRQ_TYPE_LEVEL_HIGH>;             clocks = <&ccu CLK_BUS_I2C1>;             resets = <&ccu RST_BUS_I2C1>;             status = "disabled";             #address-cells = <1>;             #size-cells = <0>;         };             i2c0_pins: i2c0_pins {                 pins = "PH5", "PH6";                 function = "i2c0";             };             i2c1_pins: i2c1_pins {                 pins = "PD25", "PD26";                 function = "i2c1";             }; Default i2c in use (PMIC and possibly HDMI):
ls /dev/i2c-* /dev/i2c-0  /dev/i2c-1 i2cdetect -y 0      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f 00:          -- -- -- -- -- -- -- -- -- -- -- -- --  10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  30: -- -- -- -- -- -- UU -- -- -- -- -- -- -- -- --  40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  70: -- -- -- -- -- -- -- --                          i2cdetect -y 1      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f 00:          -- -- -- -- -- -- -- -- -- -- -- -- --  10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  30: 30 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  50: 50 51 52 53 54 55 56 57 -- -- -- -- -- -- -- --  60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  70: -- -- -- -- -- -- -- --            
For the SPI0:
 
        spi0: spi@5010000 {             compatible = "allwinner,sun8i-h3-spi";             reg = <0x05010000 0x1000>;             interrupts = <GIC_SPI 10 IRQ_TYPE_LEVEL_HIGH>;             clocks = <&ccu CLK_BUS_SPI0>, <&ccu CLK_SPI0>;             clock-names = "ahb", "mod";             dmas = <&dma 23>, <&dma 23>;             dma-names = "rx", "tx";             pinctrl-names = "default";             pinctrl-0 = <&spi0_pins>;             resets = <&ccu RST_BUS_SPI0>;             status = "disabled";             num-cs = <1>;             #address-cells = <1>;             #size-cells = <0>;         };             spi0_pins: spi0 {                 pins = "PC0", "PC2", "PC3", "PC5";                 function = "spi0";             }; One thing i noticed was some instability on SD card but resorting to 4.19-rc6 clk values fixed it.
 
Regarding the reboot command, i applied the latest ATF power fix (as suggested by @jernej but reboot works exactly as shutdown -h now

for me the eyes and sky are much better

for voltage-drops and resistance inside connectors and how to measure I could recommend the following Youtube-Video
 

I would set the blue sky a little bit darker-blue. The far away cloud are grey - when then near more white clouds. I like the pedestal in this way
I will stay for the straight shapes.
I dont know if I like the "raytraceing" in the eyes *hmm* looks like he is crying

Success, Used the dts from here rk3399-roc-pc.dts and merged some of the kernel config from here firefly_linux_defconfig and presto! I have a booting Armbian image for the Renegade Elite 
 
 

take a look here:
https://yadi.sk/d/pHxaRAs-tZiei/5.37
kernel 3.14.29

It would be weird if you wouldn't get this error. This actually tells you that U-Boot checked if environment variables are stored somewhere. It looked at configured place, noticed that CRC doesn't match and concluded that it will use default environment instead.
 
In short, this error is normal and it would go away only if you would execute "saveenv" command in U-Boot.