Diamond

Restart loop could be incorrect dtb file. I'm not sure the correct one for your box.
 
 
For X96 Air: Is there way to have LED clock works? After installing ARMBIAN, the clock on box is off.

Hello
 
The driver for rtl88x2 seems to be not compatible with armbian:  https://forum.armbian.com/topic/15376-methods-to-fix-x96-max-pluss905x3-gigabit-ethernet-problem/?tab=comments#comment-109815
 
So, this is necessary to wait !
 

I don't see anything in the links you have provided that this would be a solution to your problem.  Are you sure that you have the that chip on your board?  (i.e. have you opened the case and inspected?).  In order to get things working, you need to have your dtb, driver and hardware all in sync.  The dtb is the mapping between the hardware and the kernel, I would expect that this is the real source of your problems that your dtb is referencing different hardware than what you have installed on your board.  The problem with armbian for android tv boxes is that while there are only a few different reference dtbs available, but there are hundreds of different boards with different components from all the manufacturers.  So most of the boards will not work in some way because of the mismatch between their hardware and the dtbs that are available (sometimes you get lucky and everything you need works, but rarely does everything work).  As I have said in other threads, no one should approach armbian for these tv boxes expecting that everything will work (especially wifi and bluetooth - none of my boxes have working wifi or bluetooth) because that is not a reasonable expectation, unless the board manufacturer is supporting their boards by getting code into the mainline kernel.
 
Having said all of that, it wouldn't hurt to try what you reference in the links above, and I suspect it is likely that the 5.6.1 based code would still work on a 5.7 kernel.
 
You should also consider the long term support issues even if you do finally get something working.  You will likely find yourself in the position that at some future point in time when a new kernel update with important security fixes gets pushed out that it is no longer compatible with your custom built driver and then you will need to choose between security of your system or breaking your wifi support.  If you need wifi, I would recommend getting a cheap usb wifi adapter that has mainline kernel support as over the long run that will be best.
 
However if your goal in all of this is to get your solution into future armbian builds (which really means getting it into mainline kernel) then keep hacking away.  But I would suspect that because you have already found a git repository that contains driver code that isn't in the mainline kernel (I am assuming this, but haven't verified), that that path has already been tried by others and rejected (lack of support of the code, poor code quality, or any number of other reasons).

I've spent hours today playing with dtb parameters and whatnot.
So far nothing.
Yes, Android dtb and dtb in this image are different. But I can not just copy-paste it. It is all related and pretty difficult to understand.
 
All I have is dmesg saying that SD card appeared, it is detected. Even partitions are detected and then it dissapears. But why it dissapears?
SDXC card seems to appear, then dissapear, then appear again...
[ 88.606168] mmc0: new high speed SDHC card at address aaaa [ 88.607742] mmcblk0: mmc0:aaaa SP32G 29.7 GiB [ 88.610100] mmcblk0: p1 p2 [ 89.637741] mmc0: card aaaa removed [ 89.731537] mmc0: error -84 whilst initialising SD card [ 90.824315] mmc0: error -84 whilst initialising SD card [ 91.912485] mmc0: error -84 whilst initialising SD card Keeps repeating the last message about once per second. /.../ Another card: [ 441.699628] mmc0: new high speed SDXC card at address aaaa [ 441.701190] mmcblk0: mmc0:aaaa SR64G 59.5 GiB [ 441.706375] mmcblk0: unable to read partition table [ 441.707109] mmc0: card aaaa removed [ 441.709786] udevd[2335]: inotify_add_watch(7, /dev/mmcblk0, 10) failed: No such file or directory [ 441.815132] mmc0: new high speed SDXC card at address aaaa [ 441.816655] mmcblk0: mmc0:aaaa SR64G 59.5 GiB [ 441.819250] mmcblk0: p1 p2 [ 441.890260] blk_update_request: I/O error, dev mmcblk0, sector 124735472 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [ 441.957930] blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [ 442.031386] blk_update_request: I/O error, dev mmcblk0, sector 8 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [ 442.034128] blk_update_request: I/O error, dev mmcblk0, sector 8 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0  
EDIT:
 
The same card/image/kernel that gives endless -84 errors boots just fine in another device.
I just changed dtb to match hardware and started it up in Nexbox A95X (s905x/2GB/8GB). No errors, starts just fine.
 
In A95X F3 Air (S905x3/4GB/32GB) still no luck.
I have no time to do more research at the moment. Maybe I'll try again next weekend.

@IgorDo what I do: ignore idiots, "ready, aim, fire" as opposed to "fire, aim, ready" once the target is properly identified as an idiot.
 
Your frustration and all the time / energy you waste is due the ignoring the reality of humanity: 5% criminals, 90% followers (idiots), 5% leaders.
 
Which is best: shutting down the forum because YOU are annoyed with reality, or, ignoring time wasters? Be aware the the corporations / individuals who are able / choose to pay 10K for support do so because of Armbian excellence which is a product of understanding / dealing with / solving issues from a large user (test) base.
 
FACT: you say I am close to solving my stated issue (and, I am, it appears to be an upstream issue, incomplete headers), implying that you see the solution and yet, waste all your time / energy complaining about people who ask questions, assuming ALL (except you) are non-contributors. Would have been better (less effort) to just answer the question so nobody (responsible enough to research) annoys you again.
 
My point is NOT that I am annoyed / insulted by your unfounded opinion regarding me and those who ask questions. My point is to convince you that your frustration is a product of how YOU choose to deal with matters. Sometimes, smart people miss the simplest things, as you have.

"and why"
 
because this is a "help" forum and, every answered question eliminates it being asked again and contributes to excellence. Just today, my WiFI patch helped two people who didn't have to annoy you by asking.
 
Please keep your "bad day" to yourself and don't call a professional evaluation and thank you for the excellence of Armbian and developers "BS".

Each kernel version needs its own dtb. So I'm afraid you will have to make one from scratch for 5.x kernels. I also have a mxq s805 board and no dtb was working for either 4.x or 5.x kernels. It just runs 3.x kernels and that's about it. We need someone with skills that can make an up to date dtb for s805 mxq boards or stick to kernel 3.x where everything including nand works.