Igor

Desktop, when installed via armbian-config, had this problem and it was fixed a week ago at source level. Hasn't landed to the repository yet.
https://github.com/armbian/config/commit/6c6947f2bea6f5af87fd542478584d6a5fd593a4

Unlikely. It's a problem with their kernel. We don't use Debian kernel - it's way too old, but I will pay attentions to upstream changes in this area. 

Unlikely. It's a problem with their kernel. We don't use Debian kernel - it's way too old, but I will pay attentions to upstream changes in this area. 

Desktop, when installed via armbian-config, had this problem and it was fixed a week ago at source level. Hasn't landed to the repository yet.
https://github.com/armbian/config/commit/6c6947f2bea6f5af87fd542478584d6a5fd593a4

Thank you for informing me that fact.
you know, the money we can spend on this project is limited as well so we chose this chip since it is not expensive but shows high performance.
Of course we understand it can fail during the flight.
But our machine is for observing something while flying so it is going to be like, "Welcome on board. You can enjoy playing some games running on RK3399 during our flight" haha 

I am just informing you that there are problems hidden deep inside. We have encounter some and some are ready to be found in a process when kernel gets matured. If I would sit in the plane where captain would say: "Welcome on board. This plane is running RK3399 ... I would immediately leave that plane"  In a few months from now, situation will be changed ... if there will be enough interest to have this kernel pitch perfect.

I am just informing you that there are problems hidden deep inside. We have encounter some and some are ready to be found in a process when kernel gets matured. If I would sit in the plane where captain would say: "Welcome on board. This plane is running RK3399 ... I would immediately leave that plane"  In a few months from now, situation will be changed ... if there will be enough interest to have this kernel pitch perfect.

I hope you are not going to fly soon?  RK3399 is not ready to fly yet 

It's simple to implement this on image for one machine, while implementing this on all armbian supported boards looks more complicated. For users perspective, things as such
bring more on the table. But I do agree we shell pay attention.

If you build Armbian from sources, this problem is solved. You need to apply this to the kernel sources: https://github.com/armbian/build/commit/40557aebb30fd98c4fa9af74e9d277d93d9be226

Igor, i commend you for all the work done here. With the growth of ARM architecture, Armbian will set both feet under the spotlight in the years to come, i foresee great adoption of this distro . I cannot thank you enough for what you and your team have done so far (And at least will donate. Regarding this issue, would be nice to make it more visible, the option to donate) .

I blame the hardware producers, not the ones doing pro bono work.
 
@martinayotte where are de latest images available? I would guess the download section would point us in the right direction.


Edit: Will just lay here the links with respect to information regarding custom builds (if someone stumbles upon this thread):
https://docs.armbian.com/Developer-Guide_Build-Preparation/
https://github.com/armbian/build

We'll dig into this. Thank you all.

It's not about censorship.. as you said you can look it up.. Normally you remember girls & guys being 'more often' here.. For me, text matters more than 'post count' or 'like count'.. (in fact the other two don't matter at all).  Remember this post here?
 
It was his first one cause I remember that I unlocked it... You can have a lot of experience (even on armbian) without posting here.. just by reading.. *random number of likes* just shows that someone is maybe longer here or longer recognized doesn't mean s/he's more experienced.. Just spends more time here..
 

This is irreversible. Any objections?

Proposed actions:
 
1. Renaming section "Technical support" to "Bug tracker" (leave restrictions as is)
2. Merging "Common issues" with "Peer to peer" and place under "Community forums" section
3. Creating new section "First aid" 
    - move "SD card and power supply"
    - create "Board doesn't boot"    
    
    or move "SD card and power supply" one level up and rename to "Board doesn't boot"    
 
Alternatively:
4. Make "armbianmonitor -u" field mandatory for "Bug tracker" section except "board doesn't boot"
5. Move NXP and Armada A388/A3700 under "Other supported boards"

Proposed actions:
 
1. Renaming section "Technical support" to "Bug tracker" (leave restrictions as is)
2. Merging "Common issues" with "Peer to peer" and place under "Community forums" section
3. Creating new section "First aid" 
    - move "SD card and power supply"
    - create "Board doesn't boot"    
    
    or move "SD card and power supply" one level up and rename to "Board doesn't boot"    
 
Alternatively:
4. Make "armbianmonitor -u" field mandatory for "Bug tracker" section except "board doesn't boot"
5. Move NXP and Armada A388/A3700 under "Other supported boards"

Check CREATE_PATCHES="yes" switch.

Well, it's seems to be ok, the wired is ok, all is working good, i think this new version works perfectly with my BananaPi M3

I actually have enough spares. Can clone and try it, why not? It's a nice idea
 
The customization I did should not be breaking. I've installed some packages, written some small tools, added some cron jobs, maybe changed some services' default parameters, etc. I actually use Debian for ~13 years now, and Linux in general for a bit longer. So I'm used to do small changes in my systems as I use them and find places which can be tuned better for my requirements. Since they're too small & short to document, they generally got lost in the process. This is why I'm hesitant to take the risk
 
Thanks again for the quick reply. I'll keep the progress updated in this thread.

Gentlemen, I'm sorry I did not thank you immediately for your suggestions. But I could not get more memory in Armbian.
On the box from the bottom:
Mele model A2000G .
After a few hours of fighting, I opened the box. I found memory chips on the PCB.
MT29F32G08CBACA FLASH 4GB MLC
2PCS X H5TQ2G63DFR-H9C   DDR3-1333H (supports down binning to DDR3-1066F), x16, density: 2G
That means I have 4 GB of flash and 512 MB of RAM even though I have an A2000G sticker on the box. Thanks for support . Igor, you're doing a great job.

i mist a " at the end, .... in the dts file
 
and thats whta i did so far igor i copied over the oneplus config and dts files, now the image builds, and i can start makeing chages to the device tree for orange pi3...

Most likely settings were changed upstream since I don't recall seeing anyone around Armbian fiddling around this.

Double checked, there is nothing wrong on our side. Get proper PSU and connect it properly, not on OTG port and it must work.
http://ix.io/1AuW (latest bionic image from the download page). Bananapi PRO is the same when it comes to SATA port.

There are no clear barriers between internal and external. If you or just somebody takes cover, than it will be supported. In any case it's hard to define "supported" for this board since nobody has all versions.

All files changed in last 10 minutes. That would be normally. If more than 10min, your SD card is dead.
 

 Do a proper shutdown. If you want to avoid fs corruption in any stage, you need to have full read only file system. This is ofc possible, but it has other limitations - you can't write to it  

You can change commit interval from 10m to 0m but it will affect performances. Go to /etc/fstab and remove commit=600 but this will solve only one problem. You still can run into fs corruption due to sudden power cut.

It works on mainline. Not sure for legacy.