Jens Bauer

Sorry, my remark was totally unrelated to Armbian and I failed to differentiate between 'we' (Armbian team) and 'we' (my company and externals). The latter try to switch in customer installations to Ubuntu LTS where possible since... LTS (long term support). That's also mostly x86 where situation is different since kernel is also provided by distro core team (Debian or Canonical) unless you decide to switch from distro kernel to mainline. With Armbian and the +40 ARM boards we support it's different since there's only legacy kernel no one really cares of or mainline (sometimes something in between, see 4.4 LTS kernel for Marvell ARMADA 38x).
 
So while Ubuntu Xenial combined with ZFS is supposed to work flawlessly on x86 (since kernel + DKMS ZFS module comes both from Canonical) situation with the various ARM boards differs since we deal with 2-3 kernel variations per SoC family and there's no one taking care of tight integration between ZFS and kernel (longsleep with his A64 legacy kernel being one exception -- but the last time I tried ZFS on Pine64 it didn't work).
 
Anyway: I just wanted to point out that I built Netatalk on Xenial maybe 30 times within the last 6 months and it always worked flawlessly (though same with Jessie before )

Please note that Armbian is not a distribution but a build system instead. You installed Netatalk on Debian 8 which only differs from a Jessie installation on x86 if armhf architecture has different packages.
 
Since Jessie's packages are so horribly outdated and since I was overwhelmed by how easy ZFS support in Ubuntu 16.04 has become (at least on x86) we do all new installations with Ubuntu Xenial only and drop Jessie where possible.
 
I installed Netatalk on Xenial maybe 5 times the last 14 days (always x86) and it worked like a charme, Spotlight support included (but please read the notes, due to limitations of the event mechanism you run pretty fast in troubles if your volumes grow in size). In other words: can't comment on why it doesn't work on Jessie and recommend using Xenial instead.
 
Off-topic: Since I praised ZFS with Ubuntu 16.04 above. When testing a new storage cluster at a customer yesterday we ran into a nice bug with ZFS on Xenial (x86): file deletions didn't release the used space and since we did heavy testing with huge test files we ended up with a huge discrepancy between the really used space (du output) and what ZFS though (df / zfs list). Only restarts solved the problem so currently there seems to be a bug with ZFS on Xenial/x86. Doesn't apply to Armbian at all since on ARM I wouldn't recommend ZFS but btrfs instead when running mainline kernel.

Thanks Joe!
 
The idea is to establish a small team, which would help us test the boards upon request. Within 2-3 weeks before planned update. If we would made more changes, more testing will be required. We want to make sure that upgrade does not break the board's core functionality at first place, than we need to try to find hidden bugs and document them under "known problems" what was found in last moment.
 
Specific details about this process are still adjusting, but roughly this is it. 
 
When I cooked my first image, it was easy and I had a lot of fun trying to find and fix a problem. I like doing that   but I simply can not. Today, this task can be done only together.

I looked at the spoilers and see folks and boards listed, but don't quite understand. Are they covered? Need more coverage?
 
I have two ODROID C2's that I need to put an OS on (the last odroid updates rendered them useless). I am very time limited, but want to help.
 
I also have XU4's and Pine64's, but would rather take on the C2's (kill two birds - one stone - the C2's are in need).
 
Do you prefer me to use the prebuilt images, or the otherway? I could do either.
 
Is there someone that can coordinate these efforts? I'm thinking that this looks like a "free for all" and is in need of a little direction for a new guy coming in the door wanting to help.
 
Call me stupid, but I am thinking something like really clear "A-B-C" instructions:
 
a) Pick Board
 
-- Use this image
 
----c)  Do this   --------d)  Report results here   Just saying, if we could coordinate needs, we could coordinate the incoming offers to help, and you will get coordinated results.   It's gotta be fast and easy to figure out what you need, fast and easy to report, fast and easy to update needs, and fast and easy to find.   So what can be done to help an idiot like me provide useful help to really smart folks like you  guys?   Joe

A free tip from a Banana Pi BPI-R1 owner. Do not waste your money, just search the forum for Lamobo.
 
I don't know how well it will be supported software wise, but have you had a look at: Marvell ESPRESSOBin Board

Please stop feeding the troll. Why do we allow people who never understand the answers they get to flood constructive threads with stupid BS?! Is that really necessary?

You're welcome to submit a u-boot patch to support it faster.

I will get two MiQi boards and I will try to make preliminary Armbian support.

Let's speculate that bad support for A64 is because it was introduced by a board maker(s), which does not understand this business. They know how to generate sales, but they completely fail to establish rapport with community, which is essential for such projects. Support is terrible and they expect that everything is done by community without any input except a bunch of free boards. On the other hand Hardkernel try ... harder   My first impression with Pine64 was - yet another cash collecting scheme, while for Hardkernel I can have neutral feelings at worst.
inexperienced vs experienced? raising popularity of Amlogic? right place at right time? None of above?

No quick/easy ways unfortunately. You'll need to mount the image, extract everything and remove the kernel, u-boot and board specific tweaks. Debootatrapping a fresh Jessie/Xenial rootfs may be easier in some cases. 

Hi,
 
Is there any plan fro Armbian to support Rockchip processors like RK3288 or RK3399? Any guide on how to port Armbian on them?
 
These processors have official support on GPU (both openCL and openGL ES), HW video codec (like H264 encoding and decoding with gstream), and also open-sourced Kernel 4.4.x. And most important thing is they are willing to support opensource community and fix their bugs continuously.
 
I've got a RK3288 proto board which was able to run Linux 4.4 + Debian with HW accelerated desktop and video playing, and it worked perfect. The only thing that troubled me is the Debian system that maintained by Rockchip is suck...
 
So I'm looking on the great Armbian now. I'll star to port it when I have time. But I'm here to ask if it's considerable to have Rockchip supported officially.
 

 
 

I bough RK3299 at one point for hacking. Unfortunatelly, I can't find any SDK. Does anyone now where to find it?
 
On the other hand, I'm more and more interested in RK3288 based boards. Support for that chip should be pretty good in mainline kernel. If someone know cheap board (max. 50 USD), please tell me. I think I could find some time to add support for it.

I think there will be soon, but I'm not certain of anything I mention below; they're just hints and pointers that might/might not be helpful.
 
So far, I've not found any "one complete solution" to your request, and none of the below suggestions will run Armbian yet.
 
@tkaiser mentioned quite a few interesting boards to me; the one that stick to my memory the best is Solid-Run's awesome Community board.
While the $349 Community board does not have a built-in graphics card, it does have PCIe, which means you should be able to add a graphics card of your own choice.
I can count at least 3 S-ATA connectors on the community board, which means you could set up your harddisks in RAID configuration.
Here's a link to the Marvell Armada 8040 chipset used in the board and a direct link to the Community Board itself (also linked to by Marvell on the above page). Please note that the Armada 8040 is a Quad-core 64-bit Cortex-A72 (blazing fast).
I'd like to mention that Solid-Run makes high-quality hardware. This means it might be more expensive, but it will last a lot longer.
I think that using the Community board as a video recorder would be "extreme overkill" - in other words: I'd endorse it.
 
Solid-Run also makes the ClearFog, however, I think the Community Board would be a better choice; especially because o the PCIe, the extra S-ATA connector and the 4GB RAM.
 
MQMaker's MiTi Board was mentioned as well, but it does not use an ARM-based CPU; this CPU is only a Dual-Core MIPS running at 880MHz, so it's probably not interesting.
 
The $39 Marvell EXPRESSOBin has 3 GMAC ports and 512MB RAM or 1GB RAM; Mini PCIe interface and USB3.0. Only one S-ATA interface, though.
 
There's also the LeMaker Cello board. This board has a Quad-Core Cortex-A57. It's not as quick as the Solid-Run board, but it does have some interesting specifications. If you need both a graphics card and an extra GMAC port, you could probably split the PCIe and add two cards there - or just connect the graphics card in the PCIe slot and add an external GMAC port on one of
the USB3 ports.
 
My opinion ... If you want a quality board and you can afford it, go for Solid-Run, but since you mention that it should be "affordable", then I guess you'd hesitate on that one.
If you have very little funds, the $39 board will probably be able to do the job. Again, there's no built-in HDMI and thus no hardware graphics accelerator.
 
Above, I've not mentioned the Western Digital My Cloud EX2100 and EX4100 NAS. These have Marvell chipsets and cost around $400 - as they have a complete enclosure and space for 2 or 4 harddisks (you can stuff up to 4 x 8 GB in the EX4100), they might be interesting to you.
 
Also, you may consider attaching a second Fast Ethernet via USB, so you have one Gbit and one 100Mbit Ethernet. Good GMACs are able to transfer up to 125MB/sec; bad 100Mbit are able to transfer only up to 10MB/sec. "Up to" means: This never really hapens. If you want fast connections just in order to be able to download quickly from the net, you need to remember that when you've upgraded your line to 10Gbit Fiber and you have extremely fast hardware, the servers you connect to and download from may be connected via a slow connections. Quick internal Ethernet connections on your LAN for accessing NAS or SAN is a good investment, but a fast internet connection may be waste of money. On a 100Mbit line I usually get 2MB/sec if I'm lucky. On rare occasions I've seen 4MB/sec.
 
Anyone who have better suggestions (perhaps a single board that satisfies all the requirements), please chip in!

Updated the deb packages (firmware and libmali) for manual installation in still images (5.24).
 
https://yadi.sk/d/LBA4bXk_32RGZ6
 
 
 
 
firmware/brcm/config.txt

i have test this device and i can say wifi can work fine without delays
 
i use kernel + firmware from armbian + enveroment from openwrt
 
load manually wifi modules  only!!!!
xradio_wlan
root@MusicBox:~# lsmod mac80211 358445 1 xradio_wlan xradio_wlan 210530 0 i have normal ping at any time !!!
64 bytes from oc2 (10.20.20.2): icmp_req=559 ttl=64 time=1.15 ms 64 bytes from oc2 (10.20.20.2): icmp_req=560 ttl=64 time=1.34 ms 64 bytes from oc2 (10.20.20.2): icmp_req=561 ttl=64 time=1.41 ms 64 bytes from oc2 (10.20.20.2): icmp_req=562 ttl=64 time=1.39 ms 64 bytes from oc2 (10.20.20.2): icmp_req=563 ttl=64 time=1.86 ms

I'm trying to find all errors on @balbes150 905x image, the issues are:
 
1) on boot
[FAILED] Failed to start Hostname Service. [FAILED] Failed to start Network Manager Wait Online. 2) nand-sata-install
 
Current root is returning a strange path: LABEL=ROOTFS
302         root_partition=$(cat /proc/cmdline | sed -e 's/^.*root=//' -e 's/ .*$//') root@amlogic-s905x:~# cat /proc/cmdline root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyS0,115200n8 console=tty0 no_console_suspend consoleblank=0 hdmimode=720p60hz m_bpp=24 fsck.repair=yes net.ifnames=0 mac=00:15:18:01:81:31 We also have a problem with emmc device
Error: The device /dev/mmcblk1 is so small that it cannot possibly store a file system or partition table.  Perhaps you selected the wrong device? Error: The device /dev/mmcblk1 is so small that it cannot possibly store a file system or partition table.  Perhaps you selected the wrong device? Error: The device /dev/mmcblk1 is so small that it cannot possibly store a file system or partition table.  Perhaps you selected the wrong device? Error: The device /dev/mmcblk1 is so small that it cannot possibly store a file system or partition table.  Perhaps you selected the wrong device? Error: The device /dev/mmcblk1 is so small that it cannot possibly store a file system or partition table.  Perhaps you selected the wrong device? 3) dmesg / kernel errors 
[    0.000000]               linux,ppmgr: 0x0000000078200000 - 0x000000007a200000  (32 MiB)[    0.000000]        linux,codec_mm_cma: 0x0000000066800000 - 0x0000000073800000  (208 MiB) [    0.000000]              linux,picdec: 0x0000000078200000 - 0x0000000078200000  (0 MiB) [    0.000000] Reserved memory: incorrect alignment of CMA region [    0.000000]   linux,codec_mm_reserved: 0x0000000074100000 - 0x0000000078200000  (65 MiB) [    0.000000] fdt Reserved memory total:  402 MiB [    0.000000] cma: Reserved 8 MiB at 66000000 [    0.000000] On node 0 totalpages: 519424 [    0.647863] clkmsr: Gxl msr_clk_reg0=ffffff800006075c,msr_clk_reg2=ffffff8000062764 [    0.650302] aml_iomap: amlogic iomap probe done [    0.650939] pinmux-gxl c1109880.pinmux: Init pinux probe! [    0.652185] pinmux-gxl c1109880.pinmux: Probed amlogic pinctrl driver [    0.652672] genirq: Setting trigger mode 8 for irq 241 failed (gic_set_type+0x0/0xbc) [    0.652709] genirq: Setting trigger mode 8 for irq 242 failed (gic_set_type+0x0/0xbc) [    0.652879] genirq: Setting trigger mode 8 for irq 241 failed (gic_set_type+0x0/0xbc) [    0.652908] genirq: Setting trigger mode 8 for irq 242 failed (gic_set_type+0x0/0xbc) [    0.655451] codec_mm has 2 memory regions [    0.655505] codec_mm codec_mm.19: assigned reserved memory node linux,codec_mm_cma ok [    0.655529] codec_mm codec_mm.19: assigned reserved memory node linux,codec_mm_reserved ok [    0.655641] codec_mm has 2 memory regions [    0.655664] codec_mm codec_mm.19: assigned reserved memory node linux,codec_mm_cma ok [    0.655685] codec_mm codec_mm.19: assigned reserved memory node linux,codec_mm_reserved ok [    0.657635] vpu: driver version: v02 [    0.657678] vpu: load vpu_clk: 666667000Hz(7) [    0.657779] vpu: vpu_probe OK [    0.659312] tv_vout: tvout_probe [    0.659340] tv_vout: major number 254 for disp [    0.659352] vout_notify: vout_register_server [    0.659363] tv_vout: register tv module server ok [    0.659463] tv_vout: tvout_probe OK [    0.660085] canvas_probe reg=00000000c8838000,size=400 [    0.660122] canvas maped reg_base =ffffff8000184000 [    0.664344] rdma_probe [    2.590447] meson-rng c8834000.rng: hwrng registered [    2.594299] loop: module loaded [    2.595295] mtdoops: mtd device (mtddev=name/number) must be supplied [    2.596090] tun: Universal TUN/TAP device driver, 1.6 [    2.596113] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com> [    2.648928] hdmitx: plugin [    2.741198] amlogic-new-usb2 d0078000.usb2phy: USB2 phy probe:phy_mem:0xd0078000, iomap phy_base:0xffffff80001ba000 [    2.741447] amlogic-new-usb3 d0078080.usb3phy: This phy has no usb port [    2.741481] amlogic-new-usb3 d0078080.usb3phy: USB3 phy probe:phy_mem:0xd0078080, iomap phy_base:0xffffff80001bc080 [    2.741999] mousedev: PS/2 mouse device common for all mice [    2.743182] USB Video Class driver (1.1.1) [    2.744089] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com [    2.744280] cpufreq-hotplug: cpufreq_gov_dbs_init: assumes CONFIG_NO_HZ [    2.744441] cpu cpu0: bL_cpufreq_init: CPU 0 initialized [    2.746648] cpu cpu4: bL_cpufreq_init: CPU 4 initialized [    4.543802] c11084c0.serial: ttyS1 at MMIO 0xc11084c0 (irq = 58, base_baud = 1500000) is a meson_uart [    4.553701] dwc_otg: usb0: type: 2 speed: 0, config: 0, dma: 0, id: 0, phy: d0078000, ctrl: 0 [    4.561709] dwc_otg_driver_probe host only, not probe usb_otg!!! [    4.568023] meson-gpu-clkgen c883c000.gpu_clk: can't request region for resource [mem 0xc883c000-0xc883cfff] [    4.577777] meson-gpu-clkgen: probe of c883c000.gpu_clk failed with error -16 [    4.585240] hdmitx: system: hdmitx_hdcp_init [    4.868852] emmc:pdata->caps = c0000d47 [    4.872790] emmc:pdata->caps2 = 18060 [    4.876590] storage 1, boot 1 [    4.879690] get_storage_dev return 1 [    4.910259] normal card in [    4.918796] [aml_sd_emmc_probe] aml_sd_emmc_probe() success! [    5.008814] [aml_sd_emmc_probe] aml_sd_emmc_probe() success! [    5.009399] ion_dev has 1 memory regions [    5.029124] fb: osd_init_module [    5.029348] fb: viu vsync irq: 35 [    5.030273] fb: failed to init reserved memory [    5.034853] tv_vout: tv_set_current_vmode[759]fps_target_mode=16 [    5.040993] tv_vout: mode is 16,sync_duration_den=1,sync_duration_num=60 [    6.060585] 6unifykey: device unifykeys created ok [    6.065362] 6aml_unifykeys_init done! [    6.069139] PPMGRDRV: warn: ppmgr module init func called [    6.074777] PPMGRDRV: err: ppmgr_driver_probe called [    6.079734] ppmgr has 1 memory regions [    6.083619] PPMGRDRV: info: ppmgr_dev major:232 [    6.088616] PPMGRDRV: info: ppmgr_probe done [    6.542486] audio_dsp: [dsp]register dsp to char divece(257) [    6.549117] amaudio: amaudio: driver amaudio succuess! [    6.553817] amlvid:err: amlvideo_init called [    6.557715] amlvid:err: amlvideo_create_instance called [    6.564008] amlvid:err: v4l2_dev.name=:amlvideo-000 [    6.568967] amlvideo-000: V4L2 device registered as video10 [    6.574874] [RX]-hdmirx: hdmirx_init. [    6.578201] ESM HLD: Initializing... [    6.849342] input input1: key 116 up [    6.853760] input: cec_input as /devices/virtual/input/input2 [    6.858808] cectx aocec: aml_cec_probe(): no hdmirx reg resource [    6.864611] cectx aocec: aml_cec_probe(): no hhi reg resource [    6.870589] cectx aocec: aml_cec_probe(): can't find hdmirx [    6.877313] cec: wake up flag:0 [    6.881408] aml_aes_dma c883e000.aml_aes: Aml AES_dma [    7.158993] aml_snd_card: headphone detection disable=1 [    7.162483] aml_snd_card: no spk event delay time set [    7.168047] aml_snd_m8_card aml_m8_snd.47: T9015-audio-hifi <-> I2S.40 mapping ok [    7.175606] aml_snd_m8_card aml_m8_snd.47: dit-hifi <-> SPDIF.41 mapping ok [    7.182298] aml_snd_m8_card aml_m8_snd.47: pcm2bt-pcm <-> PCM.42 mapping ok [    7.189168] aml_snd_m8_card aml_m8_snd.47: ASoC: no source widget found for LOUTL [    7.196709] aml_snd_m8_card aml_m8_snd.47: ASoC: Failed to add route LOUTL -> direct -> Ext Spk [    7.205526] aml_snd_m8_card aml_m8_snd.47: ASoC: no source widget found for LOUTR [    7.213110] aml_snd_m8_card aml_m8_snd.47: ASoC: Failed to add route LOUTR -> direct -> Ext Spk [    7.229669] aml_snd_card: audio use jtag pinmux as i2s output, read val =ffffffff [    8.562936] usb usb2: SerialNumber: xhci-hcd.0.auto [    8.568513] hub 2-0:1.0: USB hub found [    8.572608] hub 2-0:1.0: config failed, hub doesn't have any ports! (err -19) [    8.579306] aml_vrtc rtc.32: setting system clock to 2015-01-01 00:00:14 UTC (1420070414) [    8.588658] gxbb_pm: enter meson_pm_probe! [    8.594847] gxbb_pm: meson_pm_probe done [    8.601893] cpucore_cooling_register, max_cpu_core_num:4 [    8.608223] cpucore_cooling_register, max_cpu_core_num:4 [    8.628551] aml_istbt_dev_ready NULL [    8.632656] ALSA device list: [    8.636630]   #0: AML-M8AUDIO [   11.528107] systemd[1]: Starting Create list of required static device nodes for the current kernel... [   11.547452] systemd[1]: Mounted POSIX Message Queue File System. [   11.561244] systemd[1]: Mounted Debug File System. [   11.574443] systemd[1]: Mounted Huge Pages File System. [   11.587878] systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE [   11.598590] systemd[1]: Failed to start Load Kernel Modules. [   11.618008] systemd[1]: systemd-modules-load.service: Unit entered failed state. [   11.626685] systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. [   11.636116] systemd[1]: Started Set console keymap. [   11.651753] systemd[1]: Started Restore / save the current clock. [   11.670622] systemd[1]: Time has been changed [   11.713706] systemd[1]: Starting Apply Kernel Variables... 4) WiFi
 
I copied the WiFi files extracted from original Beelink GT1 Android image to /lib/firmware/brcm, but I'm getting these errors:
[   77.851826] F1 signature read @0x18000000=0x15264345 [   77.855166] F1 signature OK, socitype:0x1 chip:0x4345 rev:0x6 pkg:0x2 [   77.855833] DHD: dongle ram size is set to 819200(orig 819200) at 0x198000 [   77.856284] dhd_conf_read_config: kso_enable = 0 [   77.856372] dhd_conf_set_fw_name_by_chip: firmware_path=/lib/firmware/brcm/fw_bcm43455c0_ag.bin [   77.856381] dhdsdio_download_firmware: set use_rxchain 0 [   77.856386] dhdsdio_download_firmware: set txglomsize 40 [   77.856392] sdioh_set_mode: set txglom_mode to multi-desc [   77.856397] Final fw_path=/lib/firmware/brcm/fw_bcm43455c0_ag.bin [   77.856402] Final nv_path=/lib/firmware/brcm/ [   77.856407] Final conf_path=/lib/firmware/brcm/config.txt [   77.905834] dhdsdio_download_nvram: error reading nvram file: -21 [   77.905849] _dhdsdio_download_firmware: dongle nvram file download failed [   77.905889] dhd_net_bus_devreset: dhd_bus_devreset: -35 [   77.905898] dhd_prot_ioctl : bus is down. we have nothing to do [   77.905904] dhd_net_bus_devreset: dhd_bus_devreset: -35 [   77.905958] wifi_platform_set_power = 0 [   77.905964] ======== PULL WL_REG_ON LOW! ======== [   77.905969] wl_android_wifi_on: Failed [   77.905976] dhd_open : wl_android_wifi_on failed (-35) [   77.905984] dhd_stop: Enter ffffffc050c6d800 [   77.905989] wl_android_wifi_off in 1 [   77.905995] wl_android_wifi_off in 2: g_wifi_on=0 [   77.905999] wl_android_wifi_off out [   77.906004] dhd_stop: Exit [   77.906013] dhd_open: Exit ret=-1 4) Mali drivers
tar xvzf Mali_OpenCL_SDK_v1.1.0.tar.gz cd Mali_OpenCL_SDK_v1.1.0/samples/hello_world_opencl make export LD_LIBRARY_PATH=Mali_OpenCL_SDK_v1.1.0/lib Result:
root@amlogic-s905x:~/Mali_OpenCL_SDK_v1.1.0/samples/hello_world_opencl# ./hello_world_opencl OpenCL error: Unknown error Retrieving OpenCL platforms failed. common.cpp:233 Failed to create an OpenCL context. hello_world_opencl.cpp:39 Tried to modprobe mali, no success yet. There is an interesting Amlogic repository with gpu drivers: http://openlinux.amlogic.com:8000/download/ARM/gpu/

@balbes150 and @chocho
 
I learnt how to extract the dtb and dts file from Beelink Android images. I will be documenting it here to help other users, but it is the exactly process @chocho already did.
 
1) update your GT1 device with GT1_104M0.img or GT1_104M0_AP6255.img
 
2) power-up, boot GT1;
 
3) copy boot.img from running Android image
adb pull /dev/block/boot boot.img 4) download split_bootimg.pl tool and run it over boot.img
wget -c http://www.enck.org/tools/split_bootimg_pl.txt -O split_bootimg.pl chmod a+x split_bootimg.pl split_bootimg.pl boot.img Result:
-rw-r--r--   1 lvmc  staff    32M Dec  4 19:28 boot.img -rw-r--r--   1 lvmc  staff   7.0M Dec  4 20:08 boot.img-kernel -rw-r--r--   1 lvmc  staff   898K Dec  4 20:08 boot.img-ramdisk.gz -rw-r--r--   1 lvmc  staff    82K Dec  4 20:08 boot.img-second.gz 5) find the hex addresses of "d0 0d fe ed"
hexdump -C -v boot.img-second.gz |less Results (hex and decimal addresses):
gxm_q201_1g: 00000800 (2048) gxm_q201_2g: 0000a800 (43008) 6) extract available dtb sections from boot.img-second.gz
gxm_q201_1g dd if=boot.img-second.gz of=gxm_q201_1g.dtb bs=2048 skip=1 gxm_q201_2g dd if=boot.img-second.gz of=gxm_q201_2g.dtb bs=43008 skip=1 7) convert dtb (binary format) to dts (readable)
dtc -I dtb -O dts -o gxm_q201_201_1g.dts gxm_q201_201_1g.dtb dtc -I dtb -O dts -o gxm_q201_201_2g.dts gxm_q201_201_2g.dtb *dtc command is available on GNU/Linux
 
There is only one difference between gxm_q201_201_1g.dts and gxm_q201_201_2g.dts
memory@00000000 { device_type = "memory"; linux,usable-memory = <0x0 0x1000000 0x0 0x3f000000>; }; memory@00000000 { device_type = "memory"; linux,usable-memory = <0x0 0x1000000 0x0 0x7f000000>; }; boot.img, dtb and dts files from previous steps are available at:
https://dl.dropboxusercontent.com/u/11164079/GT1/beelink_gt1.tar.gz
 
beelink_gt1/boot
-rw-r--r--  1 lvmc  staff    32M Dec  4 19:28 boot.img -rw-r--r--  1 lvmc  staff   7.0M Dec  4 20:08 boot.img-kernel -rw-r--r--  1 lvmc  staff   898K Dec  4 20:08 boot.img-ramdisk.gz -rw-r--r--  1 lvmc  staff    82K Dec  4 20:08 boot.img-second.gz beelink_gt1/dtb_dts
-rw-r--r--  1 lvmc  staff    80K Dec  4 20:24 gxm_q201_1g_00000800.dtb -rw-r--r--  1 lvmc  staff    48K Dec  4 20:25 gxm_q201_1g_00000800.dts -rw-r--r--  1 lvmc  staff    40K Dec  4 20:18 gxm_q201_2g_0000a800.dtb -rw-r--r--  1 lvmc  staff    48K Dec  4 20:21 gxm_q201_2g_0000a800.dts

@balbes150 and @choco
 
1. I just wrote your image to sdcard and booted, I haven't copied any dtb file.
How can I extract dtb files from available Beelink Android images (GT1_104M0.img or GT1_104M0_AP6255.img)?
 
2. What are the differences from @balbes150 and @choco initiative?
 
3. What do you mean by "script in internal the internal memory"? What are the steps to test and help you?
 
4. I extracted newest Bluetooth and WiFi drivers for AP6255 from Beelink's GT1 Android image, it can be downloaded from:
https://dl.dropboxusercontent.com/u/11164079/GT1/bluetooth.tar.gz
https://dl.dropboxusercontent.com/u/11164079/GT1/wifi.tar.gz

1. I understand that the system automatically used the correct dtb data (you not copied dtb) ?
2. It is the universal images, which are collected from my git if you select AmlogicS905X
3. The setup script in the internal memory is NOT working. It needs to be changed (I don't have time, something would have to change it and test). The main problem is that the script should NOT replace u-boot and should be able to embed the system into existing mtd-partitions without affecting functionality of an internal component (recovery env, etc).
4. For WiFi settings you need to perform several manual operations (I hope next versions will be added gradually need the infrastructure to support WiFi).
 
https://forum.armbian.com/index.php/topic/2419-armbian-for-amlogic-s905-and-s905x/?p=20730

Yes. I downloaded respective img from balbes150 link, wrote to sdcard.
 
To boot you have to insert sdcard, unplug power, hold the key near the capacitor / power plug, plug power and release key after some seconds.
 
On screen image will take a little bit to turn on.
 
@balbes150, nand-sata-install is writing upto 100%, but after reboot android is booting again, not the probably written armbian image.
 
Do you know what else we need to do?

Judging by the log, the system is running. Log in as the root user with the password 1234, change the root password, create new user and give the shutdown command "poweroff". After turning it off try to start the system the power button on the remote control. If You are using a version of the image Desktop, after system startup and login, you can give the command "startx" to start graphical desktop.

Ordered 2 x Beelink GT1 today, however not on Amazon. Can sent them to you if you leave me your address via PM

Yes, of course.
1. Download and burn image Armbian to the media.
2. Using prepared media to activate universal multiboot.
3. Try to start the system from external media without modifications.
If the system cannot start, try to copy the from the directory "dtb" in the root of the FAT partition dtb file with the name "dtb.img". And try to start the system with this file. For tests, recommended you have connected the console UART. This will significantly ease the debugging process, because will be immediately obvious where the error occurs run, will allow you to make adjustments to the testing process (to load the elements of the system separately , without the need of a long process of rebuilding). You can try to use files that have collected garyang (link above in this thread), just remember to rename the kernel Image to zImage.

@balbes150, could you provide us a step-by-step to test your armbian on GT1 / S912? I want to help you to support this hardware.

Hello!
Sorry for too high-level description, I'm not an experienced embedded engineer, just an enthusiast.
 
I'm going to try to run a project to build an affordable home video recorder/player and I need a brief insight on the current ones available. I'm currently using A20 and I'm looking for a possible more powerful solutions.
 
Requirements:
 - At least twice powerful computing power comparing to A20
 - Video chip with hardware acceleration support in Linux (not planning to use Android)
 - SATA with at least 40 Megabytes per second throughput (NOT crappy usb<->sata built-in adapters)
 - Network stack with at least 300Mbps bandwidth that does NOT affect CPU performance (like in Banana Pi). Ideally, 2 separated NICs
 
Ideally to be able to use several displays.
 
Maybe it sounds naive, but Is there anything on the market that can do it?
 
Thank you in advance!