erew

The 1st time I installed Openhab was a few years back and it was on a TV Box variant of Armbian. Either the option to install Openhab wasnt in the Armbian Config Util on that build/system, or I missed it being in the list and would/should have used that. I ended up for various reasons having to rebuild and customize my install multiple times, plus I couldnt see much mention of Armbian on the Openhab forums and suffered some problems with Openhabian's install routine (which I think may(?) be resolved now). So, at the time I wrote a guide there, partly so I could remember everything if I had to rebuild and also to share with others whom might hunt out the word Armbian. As for versions, yes I think there is a slightly later build.. 8.46.0.225 vs 8.40.0.178 Current Arm Build 64 - https://cdn.azul.com/zulu-embedded/bin/zulu8.46.0.225-ca-jdk8.0.252-linux_aarch64.tar.gz Current Arm Build 32 - https://cdn.azul.com/zulu-embedded/bin/zulu8.46.0.225-ca-jdk8.0.252-linux_aarch32hf.tar.gz Packages lists - https://www.azul.com/downloads/zulu-community/?version=java-8-lts&architecture=arm-64-bit&package=jdk Im happy to take a shot at updating it sometime, though Ive gotten myself caught up in 4 separate mini projects right now... so when I free up from one of those, if youve not made any updates yourself, Ill take a shot at it and let you know! Thanks

@balbes150Re: Beelink GT-King, unstable when copying files etc... (sorry it took a while to get back to you). This is off a fresh imaged disk for "Armbian_20.05.4_Arm-64_bionic_current_5.7.0-rc4_desktop_20200510" Printenv Help Commands Thanks for taking a look.

The commands I gave above... I found hidden away on Azul's website..... https://docs.azul.com/zulu/zuludocs/ZuluUserGuide/PrepareZuluPlatform/AttachAPTRepositoryUbuntuOrDebianSys.htm for these 3 lines: sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 0xB1998361219BD9C9 sudo apt-add-repository 'deb http://repos.azulsystems.com/ubuntu stable main' sudo apt-get update and https://docs.azul.com/zulu/zuludocs/ZuluReleaseNotes/Troubleshooting.htm for this line (Azul Repository Tips section): sudo apt-get install zulu-embedded-8 They've worked for me on every build/rebuild Ive done of my ARM systems (3 different systems and probably about 10 rebuilds over time). Though, I will say that with this build of Java, its best to add some XMM and XMS memory settings to the Openhab EXTRA_JAVA_OPTS within Openhab after its installed, as the Embedded version does seem to like keeping low memory utilization.... but that would be a case by case basis depending on the board its installed on. These settings are also very well discussed on the Openhab community forums.

Just noticed this... Re Java, you need to use Azul Zulu Embedded v8 at the moment... OpenJDK and things like that are sluggish/slow Full details here https://community.openhab.org/t/version-2-openhab-openhabian-on-an-android-tv-box-running-armbian-setting-it-up/76367 Actual commands here: sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 0xB1998361219BD9C9 sudo apt-add-repository 'deb http://repos.azulsystems.com/ubuntu stable main' sudo apt-get update sudo apt-get install zulu-embedded-8

I downloaded the images from here https://yadi.sk/d/_rQgn_FosYuW0g and the uart boot I show up in my post, is a freshly imaged Armbian on a USB SSD, using the meson-g12b-gtking.dtb that came with the image. (I tried multiple versions of Armbian and for a test, later, I tried the corelec DTB to see if it may work, which it didnt even boot Armbian).

Is anyone running a Beelink GT-King and does your box remain stable OR lock-up/freeze when transferring data to/from SD/USB? Mine freezes completely when I transfer data around. My full post on it is here My system is a version 2.2 board the SA9X model. I also see an "Internal error: Oops: 96000004 [#1] PREEMPT SMP" in the UART logs (See spoiler for full logs) If your system is running stable... be it any revision, please let me know.... and if there are any tweaks/changes anyone can suggest to try.....??? Many thanks

@balbes150 Thanks for the reply. I appreciate that you dont have one of these with you to test/look at. Could I ask however.... would you think that this is an issue with the drivers within Ubuntu ... OR.... settings within the DTB file (frequencies/drivers used)? I have added the UART output of both Armbian's and Coreelec's DTB files, when booting Armbian with them... if there is anything you can see in those? (if you have the time to look) Armbian meson-g12b-gtking.dtb UART output https://pastebin.com/QmFt7WGC Perhaps this is the relevant bit?? (as my issue is to do with high disk activity) [ 6.647386] EXT4-fs (sda2): re-mounted. Opts: commit=600,errors=remount-ro [ 6.922303] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000f5 [ 6.927276] Mem abort info: [ 6.929986] ESR = 0x96000004 [ 6.932759] EC = 0x25: DABT (current EL), IL = 32 bits [ 6.939615] SET = 0, FnV = 0 [ 6.946536] EA = 0, S1PTW = 0 [ 6.947931] Data abort info: [ 6.949280] ISV = 0, ISS = 0x00000004 [ 6.949282] CM = 0, WnR = 0 [ 6.949287] user pgtable: 4k pages, 48-bit VAs, pgdp=00000000a220c000 [ 6.956371] [00000000000000f5] pgd=0000000000000000 [ 6.966305] Internal error: Oops: 96000004 [#1] PREEMPT SMP Also, I assume I can connect a serial cable to the TX/RX of the device during boot, look at the output, to try find why a DTB file might not start booting? Im happy to research. learn and give this a go, if you think that may be a good direction to try..... If you have any thoughts or suggestions on this, please let me know?

If its worth anything, this is my dmesg output, when I have booted with the Armbian GTKing DTB file and I am at the desktop/workspace screen (before it freezes)

@balbes150(sorry to @ you and hope youre keeping well!!) I have a Beelink GT King, which its motherboard lists as being version 2.2-S922X-4G-64G/A It has a terrible stability problem using meson-g12b-gtking.dtb (I have tried the pro file as well as others in case, but it wont boot with those). The problem I am experiencing is that when any high level of file transfers occur, the system freezes. The mouse etc locks up, the time/clock freezes at the time of the system hanging and the system drops off the network (stops responding to ping). Ive tried multiple revisions of Ubuntu that can be currently downloaded on Yandex, and been through Bionic, bullseye etc... and through 5.3 up to 5.7. All suffer the same issue. The system will stay stable as long as you dont do very much, however, examples of things that have caused the system to freeze are: 1) sudo apt update 2) ddbr 3) coping the test.mp4 file on the desktop multiple times 4) trying to install to emmc (never been able to get through an install to emmc) 5) running multiple tasks at the same time. 7) Trying to copy a 1GB file 8) etc In short, the issue is repeatable via various methods. Ive tried SD cards, USB flash drives and USB SSD'd... all have the same issue. Because the system freezes/locks up, I cant give any diagnostics.... though it runs 100% fine in Coreelec and Android. The only working DTB file I can find is the one thats coming with Armbian at the minute, and older revisions seem to be the same file. (50,214 bytes size on disk). The only thing I experienced in the past that locked a system up like this was the WIFI being used.... but Im on Ethernet. It does seem to be some buffer issue or similar with the disk access. Any suggestions? (as I cant find anything in the forums and see no issues with the boot process) My dmesg output is in a post below (if it helps) Many thanks If I use that DTB file with Armbian, it actually looks like my system is trying to boot... it does actually go to a black screen, though there is no scrolling text, though going to a black screen is further than other incorrect DTB files get to). Not sure if that helps in any way.

I cant specifically speak for the debian build as Im mostly familiar with the Ubuntu build..... So ill talk about that and you can figure if Debian is similar. UBUNTU UPDATES On the Ubuntu version, you can either go into the Armbian configuration utility and the System menu and Firmware option OR you can at a terminal use: sudo apt-get update sudo apt-get upgrade Perhaps even sudo apt-get dist-upgrade (never tried it, but this probably WILL remove some packages). This should obviously update all your software AND the upgrade will pull later revision kernels. What this means is you should be able to upgrade point revisions by updating the kernel etc, but not major revisions. So in effect you could upgrade Ubuntu 18.6 to 18.7 through minor updates BUT NOT 18.6 to 19.x The major revisions would be a re-install as far as I know. Additionally, I have seen something about the fact that a recent issue with kernel updates (so please check that). This post also roughly explains that the TV box version updates arent stored in the Armbian repository, so that complicates making a major revision update process possible... well.. at least, thats my interpretation of it. OTHER PROCESS TO COPY BACK OTHER FILES etc. Actually... its something Ive thought about testing some time, but Ive never gotten around to it. In theory, Im reasonably sure this is possible, but I cant say how involved the process is and of course, that may vary depending on your customization. If someone has any suggestions on doing this, point me in the direction of anything you know and Im happy to test and write a guide.

Hi, not sure.... Ive just opened a fresh install of Armbian on a USB stick and the Extlinux.conf there shows the # in the place I originally indicated (copy/paste below) LABEL Armbian LINUX /zImage INITRD /uInitrd FDTDIR /dtb # FDT /dtb/meson-gxl-s905x-khadas-vim.dtb APPEND root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 The # may get changed/removed if/when you install to EMMC/NAND as the Extlinux.conf file is used for booting from EMMC/NAND storage and not off a USB card/SD/TF card.... so that file is only used in that instance of booting from internal storage. The # is typically used to say "dont use this line in the code" ..... so its possible something has been changed on the boot process too. Its not something Ive seen yet, but ill take a look sometime.

Noticed this post with the question above... emmc to SD.... I wrote instructions on doing this+videos showing how to do it. Thought you might find them helpful if you wanted to do this for backups etc. Making a Backup of your emmc via the GUI https://www.ondroid.net/armbian-os-backing-up-emmc-nand-via-gui/ - What you will need - All the commands/screens to perform this - Includes 1 x video showing the whole process Making a Backup of your emmc via Command line https://www.ondroid.net/armbian-os-backing-up-emmc-nand-via-cli/ - What you will need - All the commands/screens to perform this - Includes 1 x video showing the whole process Thanks erew

@Janaboy My rough (dont quote me) understanding of this is that its a mix of your DTB (Device Tree Blob) file and also actual driver files, hence trying different DTB files, with different results. The DTB file is basically telling the system which drivers to load at startup. I believe the Beelink Mini MXIII box has an Aigale AW-CM273SM and Qualcomm Atheros QCA9377 for WiFi/Bluetooth.... And I have no idea if anyone has ever written a driver or if one of the DTB files activates the driver, though I can seem some references around the internet to people trying. So, if you can find a driver or if one exists, you can write your own DTB file, which might work OR obviously test other DTB files.... (this is why Im thinking to create a database so that we can find the best combinations for which DTB to use with which box). The other alternative is to use an external usb dongle. Im not 100% confident which one would or wouldnt work, but have seen the CSR bluetooth dongles referenced before in ubuntu/armbian forums.... and they are cheap as $2 kind of thing.... Maybe someone else on here has experience with them. (If I had one to hand Id give it a go for you, but sadly dont) Search google for csr bluetooth dongle if you want to try this route. Im not yet at a stage to start writing about loading other drivers/editing DTB files etc.... as Ive still got my own research/experiments to do on that.

@Janaboy Thanks, and glad it helped!! Im working on a slightly updated guide... and potentially going to collate a list/database of DTB files/boxes and what works/doesnt work (HDMI, WiFi etc) so its a bit easier to figure which DTB file to use... So Ill post something on that in the future!

@imikei Youve not mentioned which box you have.... However I think you may end up needing to reset it back to factory (if its not even booting to the internal Android OS anymore), so Booting Problems section of this post. Once thats done, if youre sure your using the correct DTB for your box, Id suggest trying an earlier build of Armbian or one with a different kernel version to see if that gets you working. Im guessing you mean username/password at the initial text screen where you log in as root and change the passwords etc.