Igor

SPI is build in and it's working (to some degree, apparently). I forgot details, but as far as I remember, there were two patches around so I guess the easiest way would be to rebuild a kernel with that other patch, not with our default one. Both things (display, SPI) might also be achievable with some tweaking on Vanilla kernel ...

For download images it's trivial indeed and will be done asap. The rest we need to check manuals (wordpress, nginx, ispconfig, IPboard) and it's a task, with unknown time of execution at this point. BTW. My public pgp key is stored on a public keyserver. In any case, our primary objective is a build tool so if you are afraid on security -> build your own image from sources (with our tool or manually) Even this way, you need to trust that sources are good and fully checked ...

Why don't you recompile kernel only if you need this tiny change and install this new kernel? I see from this screen, that it was done successfully. Beware when upgrading since if you use our tools, recreated kernel will be overwritten at next update.

image.armbian.com

You have this board: https://linux-sunxi.org/Xunlong_Orange_Pi_Plus ?

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.

Probably something is missing, a script for loading Bluetooth firmware, firmware or Bluetooth stack. Try with clean image - it should work out of the box.

OK, will push out updated images later on.

Board settings are always a part of upgrade so you need to use your own custom name for settings to prevent overwriting. But everything else work and you forgot to mention - which board, which kernel, .... we need all the information to help. Run armbianmonitor util ...

https://github.com/igorpecovnik/lib/blob/master/scripts/h3disp#L194 m 33 should do the job. If you don't have this, can you paste the output of h3disp utility?

Yes, done.

If upgrade is not finished properly, it might not boot. I wrote a proper upgrade instructions in bold on www.armbian.com but I guess it was not noticed I don't have much other options to notify people who uses our system. Now the procedure is far more complex but nothing is lost unless you have already start with new image and install it over.

Not my area of expertise, can't answer.

We provide a vanilla kernel but not images since things are not working perfectly well yet. You can use a normal build and install those two packages: linux-image-dev-sun8i linux-dtb-dev-sun8i But you also need to adjust boot script to load a right DTB! Than you can reboot into new kernel. Try at your own risk.

Segmentation fault is strange ... first remove one of u-boot packages. It looks like linux-u-boot-orangepiplus2e-default is too much. Next try this: dpkg --get-selections | grep "linux\-$(lsb_release -cs)\-root" | awk '{print $1}' | xargs dpkg --remove apt-get install -f apt-get update apt-get upgrade BOARD=$(dpkg --get-selections | grep "linux-u-boot" | awk '{print $1}' | cut -f4 -d- ) BRANCH=$(dpkg --get-selections | grep "linux-u-boot" | awk '{print $1}' | cut -f5 -d- ) [[ $BRANCH == default ]] && apt-get install "linux-$(lsb_release -cs)-root-${BOARD}" [[ $BRANCH != default ]] && apt-get install "linux-$(lsb_release -cs)-root-${BRANCH}-${BOARD}" apt-get autoremove -y I am still testing but it looks to be o.k.

Most likely yes, if there is nothing else wrong with your X2. I assume you can run Android which is (usually) installed on the internal memory?

Board maker changed their RAM chips in recent version and settings hasn't been hacked yet. If you want to use Armbian or other systems based on mainline uboot you need to wait for a while since this was just discovered one week ago.

I just found out that repository is partially broken and I need to rebuilt it. Some files for v5.2 are missing.

So far we found 3 different revisions of Beelink X2, 2/3 boots and works fine while latest series have troubles to boot. Perhaps you are facing this problem here?

OK. Try blacklisting evdev or remove ir from device tree. I know it's annoying but I think it's safe to ignore ... until next update. Will pay attention to this.

I'll try to produce an fix for those troubles tomorrow. In the mean time: dpkg -r linux-xenial-root-orangepilite apt-get -f install apt-get upgrade apt-get install linux-xenial-root-orangepilite

I guess it must be some glitch in IR driver? To stop this flood try to blacklist the IR module.

Upgrade was not issued properly - you continued even an error (which you did no understand?) was popped out ... so you have to blame yourself. I give you a hint how to do recovery or if you haven't got any major data, rather start with a clean build. If you would ask this before reboot, we could give you a clean an proper solution. Our last update was an large one and even we made lot's of test, some bugs went trough. Please let me know when you find more polished distro. I am always happy to learn.

http://docs.armbian.com/User-Guide_Advanced-Features/#how-to-unbrick-the-system

We need to find a solution within mainline u-boot. It was confirmed that with prehistoric stock Allwinner u-boot works, but we can't and won't switch to it. Thanks for the pic.