Werner

It seems that base packages are different ... I didn't check anything at this stage. Perhaps a diff between stretch and buster packages should be nice to have. From CLI and desktop ... and adjust accordingly. Probably there are some other packages missing.

Ja, sag einfach Bescheid ob es geklappt hat in der Bretagne

- to build engine (EXPERT="yes")
- repository update with the purpose for adding it (armbian-config and armbian-firmware update everywhere)

This time was at least controlled offline  and according to my info, there were no troubles. There will be some further actions - adding redundant this and that - to prevent (unplanned) downtime in the future. 

Thanks!  Time = around 6pm CET.
 
We had two hardware failures before the actual planned upgrade  We are using a proverb for describing such mess "when the devil have children ... " 

The memory controller for the h6 is 32 bits, 4gb may be there but only 3 will ever be usable. Which is why they are being sold as 2gb/3gb options.

certainly just execute:
root@orangepioneplus:~# systemctl disable NetworkManager root@orangepioneplus:~#ip a |grep ether link/ether 00:2d:fd:1e:f1:e1 brd ff:ff:ff:ff:ff:ff # take note of MAC address root@orangepioneplus:~#vi /etc/network/interfaces ## add or update in to /etc/network/interfaces.d/ auto eth0 iface eth0 inet static address 192.168.10.200 netmask 255.255.255.0 gateway 192.168.10.1 dns-nameservers 192.168.10.2 192.168.10.1 hwaddress ether 00:2d:fd:1e:f1:e1 root@orangepioneplus:~# reboot # wait 5 secs and reconnect to IP address set root@orangepioneplus:~# cat /etc/network/interfaces # tada!  
you guys don't even realise how perfect this weekend started,
once again cheers for all your efforts, it is appreciated a lot!

Awesome news. And everyone can still be an old school guy using interfaces file 

I've compiled a new kernel with DWMAC-SUN8I as module, and it seems to be the trick, even no needs to do manual "rmmod", simply "reboot", using NetworkManager on my OPiOnePlus.
I will verify that it still true with "old school /etc/network/interface" , and then I will also confirm that it is working the same way on OPi3.
 
This would means something is wrong in the cleanup when built-in in the kernel ...

If you read my previous posts, it require to recompile the kernel with DWMAC-SUN8I as module.
Since I've done it and tested succesffuly, I've just committed the change in Armbian, so simply redo a new build ...

This issue has been discovered 2 days ago, and it is not an Armbian issue ...
Nigthlies are always images "no support ! use at you own risk !"
There is no Desktop in Nightly folder ...
Unfortunately no ! A 64bits SoC will always be 64bits kernel, even if you install 32bits libraries.
If you wish 32bits, simply purchase the OPiOne which use H3 instead of H6.

at this time there is only a pre-support with OS-images:
https://dl.armbian.com/orangepi3/
 
but support is getting beter from day to day

short answer:
 
https://dl.armbian.com/orangepi3/nightly/
 
long answer:
 
follow this thread

H6 has hardware virtualization, and now with mainline kernel it's possible to run KVM on it.
 
For Xen, it's possible to port, but I don't know who wants to port ;-)

You should do like me : I have more than a dozen of USB-TTL around, almost every boards have one, so I don't have to waste time unplugging/plugging them while testing. I've even placed a new order on eBay to get more ...
Tested on OPiOnePlus, now doing the OPiLite2 and OPi3 ... Patch is already committed to Armbian !
Thanks a lot for the help !
 
EDIT : OPiLite2 and OPi3 tested too ...

What would be this second patch for the U-Boot "reset" ?
 
EDIT : for the "reboot" patch, I'm confirming : it works ! Thanks a lot to both @froezus and @megi !!!
EDIT2 : tested on all my H6, OPiOne+/OPiLite2/OPi3 ... And patch committed in Armbian !

https://github.com/leeboby/OrangePiH6_Linux4.9

- firmware to support Orangepi 3 https://github.com/armbian/firmware/commit/fe584970a1f8e718540a3cec4838e7a4cad5f263
- spelling and grammar in armbian-config  https://github.com/armbian/config/commit/92ad8e77eec2e71429d677852654cfeb1a0ea3f0

Please refer to this topic rgd issue 1)
Also to create some more awareness I contacted "Allwinner Customer Service Team" recently and they made this a Xunlong issue,
their response: " After a short discussion internally, we suggest you contact Xunlong for clarification.
Let's hope for a satisfactory solution, little/ some hope this can be increased as Xunlog is partnering with armbian ... ...
 
let's keep fingers crossed...

Here you go ;)

This smells like someone savvy with higher ed dollars and grant money
 
So in all seriousness, what would armbian certified look like to you.  What are the skills that one would be trying to master.  As a brainstorming here's some possibilities:
 
Using build system to build custom images and kernels alternate kernel options the user-patches framework kernel patches alternate system configurations software preinstallaion Understanding the SBC ecosystem vendor culture kernel fragmentation u-boot fragmentation Mainlining Initiatives u-boot kernel Adding your own community support board to the ecosystem -- assuming you plan to continue to support it

That's super awesome.   Out of curiousity, what do you and you students do with armbian?  and what kind of hardware generally?
 

Thanks Martin! I just validated on my OpiOne+

Not on fresh boot, as well as original OPi U-Boot, but both work well if the BSP U-Boot handler is still in memory.
 
This is why I've said "Back to SquareOne" when I've investigated the reset_cpu() code from arch/arm/mach-sunxi/board.c
... and I still don't catch why PineH64 U-Boot works fine on PineH64 boards ...

https://github.com/armbian/documentation/pulls