Igor

RT patch is a part of our patch set, just enable it and recompile kernel.
 
Wrote on mobile phone

Another Orange device:
 

We can close this, Like an Idiot I've broke my system while trying to switch kernel so I've reinstalled Xenial which I found I like more than Jessie.
 
I've already set up the system as before and it seems to work fine so far. Likely the problem was related to some mess I did or an upgrade gone wrong.
 
Thanks for the support.

Builds can be reproducible but they might not be exactly since we are attached to external source projects and we are fixing things daily.
 
 
Sources are more or less trusted (mainline kernel and uboot, legacy sources maintained by vendors, some community, some mixed, ...). They are git cloned with https, so nothing gets in between.
 
 
Each developer has it's own environment and our common end result is public on Github. Code is review upon commits so I would say yes. Official build is (so far) always done by me on a dedicated hardware, accessible locally and output is securely transferred to download server which will get ssl when admin of the server gets up and finds time.
 
Armbian project is still a small one no matter of importance. Our core team resources and budget are tiny, on a hobby level, so even some things are possible, we might not be able to afford them. But we take security seriously and possible problems will be fixed ASAP ... just this ASAP will take longer
 
Sometimes is hard to see even most obvious things so I only thank you for bringing ideas up. I certainly don't want that our work becomes involved in something like this

I forgot that I got a back side too Added.

Armbian, not possible, only via SD card boot first method.
 
@mdel
 
I don't see any problems. Network works as expected ... desktop version uses Network Manager, where this could be possible.
 
Shutdown looks like it manifest to reboot? It works properly on some boards but I guess not on all ... need to be investigated.

service nodm disable

Another Orange device:
 

Builds can be reproducible but they might not be exactly since we are attached to external source projects and we are fixing things daily.
 
 
Sources are more or less trusted (mainline kernel and uboot, legacy sources maintained by vendors, some community, some mixed, ...). They are git cloned with https, so nothing gets in between.
 
 
Each developer has it's own environment and our common end result is public on Github. Code is review upon commits so I would say yes. Official build is (so far) always done by me on a dedicated hardware, accessible locally and output is securely transferred to download server which will get ssl when admin of the server gets up and finds time.
 
Armbian project is still a small one no matter of importance. Our core team resources and budget are tiny, on a hobby level, so even some things are possible, we might not be able to afford them. But we take security seriously and possible problems will be fixed ASAP ... just this ASAP will take longer
 
Sometimes is hard to see even most obvious things so I only thank you for bringing ideas up. I certainly don't want that our work becomes involved in something like this

Thanks Igor, that's sound advice.
 
I haven't installed Armbian on eMMC yet, will do that.
I've contacted the developer of Guitarix it there is still some tweaking within Guitarix possible so I'll try that also.
 
Hans

So far we find out that three different versions / revisions of Beelink X2 exists. All three are confirmed to work, the one I have, work. 
 
http://www.armbian.com/beelinkx2
 
Just give some moments, the screen does not come up strait since boot loader that we use, does not have video driver.

So far we find out that three different versions / revisions of Beelink X2 exists. All three are confirmed to work, the one I have, work. 
 
http://www.armbian.com/beelinkx2
 
Just give some moments, the screen does not come up strait since boot loader that we use, does not have video driver.

https://github.com/igorpecovnik/lib/commit/9de9de2de2a51afa9bacfaba23113f2319870db9
Check if something is missing.

Cheers, having a forgetful moment - All running fine on the V1.1.1 board I have, ethernet and WIFI also working great

I have network issues with horrible low upload speed (one day per GB) ... so need to wait until those issues are resolved. I'll put on blog when images are changed.

confirm. working ))), but have error, maybe script.bin is not correct configurated

after some restarts get only one error 

Edit: after some restarts get only one error and stopped fast blinking led red blue

mmc1: error -5 whilst initialising SDIO card

So for the sake of information had to disable these modules:
 
blacklist ir_lirc_codec blacklist lirc_dev blacklist evdev blacklist sunxi-cir   The reason i didit was because the board was hanging after a while (4 or 6 hours) after disabling those  im already at 17Hour uptime Thanks

Well i must say im a bit too used to x86`s the OP1 was my dabble into arm. I used linux pretty heavily before 2009 i think. When something on my normal PC went "kaput" before...it usually was not dealbreaker, and even if it was a tougher problem to deal with i usually had the time to fix it. I had a look see and i didnt really find the right "fit" distrowise so i think i will stay with armbian for the time being but hit the "Upgrade" button only if there is need. Maybe this weekend i will find time to do a reinstall.
 
Fortunately i have all my /home/ Data on separate drives (as a raid) which i think i can fit into a new system.

Yes, we could (formally) engage more people into developing process as testers. It could be helpful and we would be little relieved.
 
Perhaps we start to seek & assign few testers / maintainer for each board? We can provide access to daily upgrades to make things easy on technical level. I can provide extra repository (aptdev.armbian.com) with daily updated deb packages, while creating images takes way too much time for daily builds. I am already working on this for some time and it's not far away from running it daily.
 
Subforum "Development" is not that busy, so we can have those things here.

SOLVED  !!!   after dist-upgrade and before of reboot :   sudo apt-get install -f   be happy   thanks to   Igor and tkaiser

I made a quick test on Orange Pi One and I could boot into self build kernel 4.7.4 ... network works, but only one CPU is detected. I did not investigate why ...
 
Since we are talking about immature kernel, problems are expected. This kernel is from our point of view still in testing mode and not yet for usage so we don't support it. If it does not work, you are basically on your own. Of course we will try to help and we are happy to get feedback and if it's possible, we will fix it, but not right on the spot.

I made a quick test on Orange Pi One and I could boot into self build kernel 4.7.4 ... network works, but only one CPU is detected. I did not investigate why ...
 
Since we are talking about immature kernel, problems are expected. This kernel is from our point of view still in testing mode and not yet for usage so we don't support it. If it does not work, you are basically on your own. Of course we will try to help and we are happy to get feedback and if it's possible, we will fix it, but not right on the spot.

.raw was renamed to .img in latest update. There is no other diff.
 
If upgrading is failed, you don't reboot until you find out what's wrong ... I guess we need to write this somewhere since you are not the only one with this problem. Check for a solution:
 
http://forum.armbian.com/index.php/topic/2058-upgrade-problem-with-520-on-xenial/

Which kernel (I assume you had 3.4.112) and did you encounter any errors during update?
 
Edit: image from download section (Jessie Server) works fine, tested right now. Here is boot log. Check docs for resolving standard problems.

Yes, we could (formally) engage more people into developing process as testers. It could be helpful and we would be little relieved.
 
Perhaps we start to seek & assign few testers / maintainer for each board? We can provide access to daily upgrades to make things easy on technical level. I can provide extra repository (aptdev.armbian.com) with daily updated deb packages, while creating images takes way too much time for daily builds. I am already working on this for some time and it's not far away from running it daily.
 
Subforum "Development" is not that busy, so we can have those things here.