martinayotte

That is what I do all the time, the nand-sata-install is working fine.
Then, if I wish to boot from SDCard, even if U-Boot is start booting from eMMC as priority, I'm stopping it with <spacebar>, then do "mmc list" to see SDCard number, and do "setenv devnum 1" followed with "run mmc_boot", it will then continue booting from SDCard ...

No problem, as I said the resulting "dmas = <0xa8 0xf 0xa8 0xf>;" is good !
No worries ! But that would be a good opportunity and challenge ...

Right ! Every SoC users should have a USB-TTL Serial dongle nearby !
(I've more than 10 of them, leaving them connected on all boards where I do frequent updates)
My OrangePi3 is currently working with 5.1.0-rc4 from eMMC ...

I'm running my OrangePi3 headless, but just to verify HDMI, I've tested with both my Dell 23in monitor as well as a small 10in HDMI LCD, and I'm able to see the login prompt in plain text (without any x11).
Did the nand-sata-install succeed ?
Personally, I didn't get issue and I'm running Armbian from the eMMC...

Instead of applying power, if I recall correctly, I used the RESET button SW2103, it is much easier to press, and less risks to shake your other hand doing the TP50265 short...

I know by been one of the first having done that, TP50265 is so small, you need steady not shaking hand to make the short correctly ...

Yes !

Yes ! Because I'm pretty sure you still have the old U-Boot ...

It is not that easy, you will need to disable few patches, tweaks some others, and create new ones ...
But here is at least where you should begin with :
diff --git a/config/sources/sun50iw6.conf b/config/sources/sun50iw6.conf index e42581a..0245e64 100644 --- a/config/sources/sun50iw6.conf +++ b/config/sources/sun50iw6.conf @@ -46,11 +46,11 @@ case $BRANCH in KERNELPATCHDIR='sunxi-dev-h6' BOOTSOURCE=$MAINLINE_UBOOT_SOURCE BOOTDIR=$MAINLINE_UBOOT_DIR - BOOTBRANCH='tag:v2019.01' + BOOTBRANCH='tag:v2019.04' #KERNELSOURCE=$MAINLINE_KERNEL_SOURCE KERNELSOURCE="https://github.com/megous/linux" - KERNELBRANCH="branch:orange-pi-5.0" + KERNELBRANCH="branch:orange-pi-5.1" KERNELPATCHDIR='sunxi-dev' KERNELDIR=$MAINLINE_KERNEL_DIR diff --git a/config/sources/sunxi64_common.inc b/config/sources/sunxi64_common.inc index fea1322..aa84a2e 100644 --- a/config/sources/sunxi64_common.inc +++ b/config/sources/sunxi64_common.inc @@ -54,7 +54,7 @@ case $BRANCH in #KERNELSOURCE=$MAINLINE_KERNEL_SOURCE KERNELSOURCE="https://github.com/megous/linux" #KERNELBRANCH='branch:linux-4.19.y' - KERNELBRANCH="branch:orange-pi-5.0" + KERNELBRANCH="branch:orange-pi-5.1" KERNELDIR=$MAINLINE_KERNEL_DIR KERNELPATCHDIR='sunxi-dev' KERNEL_USE_GCC='> 7.0' diff --git a/config/sources/sunxi_common.inc b/config/sources/sunxi_common.inc index 26f8602..c767d33 100644 --- a/config/sources/sunxi_common.inc +++ b/config/sources/sunxi_common.inc @@ -40,7 +40,7 @@ case $BRANCH in #KERNELSOURCE=$MAINLINE_KERNEL_SOURCE KERNELSOURCE="https://github.com/megous/linux" - KERNELBRANCH="branch:orange-pi-5.0" + KERNELBRANCH="branch:orange-pi-5.1" KERNELDIR=$MAINLINE_KERNEL_DIR KERNELPATCHDIR='sunxi-dev' KERNEL_USE_GCC='> 7.0'  

Maybe he didn't included the fix in those builds ...
Why are you not using latest nightly from here ?
https://dl.armbian.com/orangepi3/nightly/
 

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 ...

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 ...

I've finally "unmasked" the ghost !!!
 
Since I'm an old fashion guy, I'm usually defining my network settings in /etc/network/interfaces, for both WiFi and Wired...
As soon as I've commented out the "allow-hotplug eth0" and "iface eth0 inet dhcp" and leave NetworkManager managing it, after cold boot, of course, the wired network was working fine on every reboot !
 
It still amazed me to figure out that, because it is really like we opened a pandara box, why old /etc/init.d/networking could leave something dirty in memory that make the following errors after a warm reboot :
[ 4.388263] platform 5020000.ethernet eth0: Could not attach to PHY [ 4.394739] platform 5020000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) Maybe @froezus has an idea ?
 
In the mean time, don't be a old fashion guy like me, leave NetworkManager do things properly ...
 
EDIT : BTW, when I've said earlier the PineH64 doesn't behave like OPis for this wired networking issue, it is still true, because if I've the settings in /etc/network/interfaces, it still have proper networking after warm reboot ... So, still pandora box !

Of course ! Starkbier can be dangerous if drank too fast ...
I've maybe one hidden somewhere here :

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.

The normal way to install is to do "dpkg -i device-tree-compiler_1.4.7-3_arm64.deb" ...
It should be done within the DT using "clock-frequency = <400000>;" in the i2c node, nearby the "status"

The fix has been committed yesterday, so you need to try with 5.78.190408 or later ...

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 !

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 !

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 !

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 !

Now one more for EOL? A gravestone with one of the background images as picture, a big RIp and some text to explain it's eol.
I can do that tomorrow. Let me know what text would fit to not enrage the user because it's eol.
 

Wow !!! That really fine !