jeanrhum

I'm currently accessing it through ssh and using a wireless connection. It works well, here is iwconfig result:
wlxa02c36cad0d2 IEEE 802.11 ESSID:"XXXXXXXX" Mode:Managed Frequency:2.412 GHz Access Point: XX:XX:XX:XX:XX:XX Bit Rate=72.2 Mb/s Tx-Power=18 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality=61/70 Signal level=-49 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 EDIT: I used armbian-config to set up the wifi.

Hi,
 
I received my box yesterday and was able to build and follow your instructions to get the following system:
 
_ _ _ | | __ _| | _____ / | | | / _` | |/ / _ \ | | | |__| (_| | < __/ | | |_____\__,_|_|\_\___| |_| Welcome to ARMBIAN 5.76 user-built Debian GNU/Linux 9 (stretch) 4.9.157-rtd1295 System load: 1.31 0.91 0.41 Up time: 5 min Memory usage: 3 % of 1636MB IP: CPU temp: 52°C Usage of /: 2% of 58G Great work!

Since I upgrade frequently, I think there is not too much difference. Armbian tools and firmware are updated as other packages. Of course there should be some specific modifications of Balbes after each update he made.
If 5.41 has mali, it is useless for me since I use my box as a server.

I'm currently running a Beelink GT1 ultimate (S912, 3Go DDR4, 32Go) with your armbian 5.37 based on 3.14.29 debian stretch without specifying any dtb file.  It is used as a server with openmediavault and homeassistant. I'm running armbian from sd card.
I just made upgrades and got armbian-config 5.64 with an uptime of 70 days.

I'm currently running a Beelink GT1 ultimate (S912, 3Go DDR4, 32Go) with your armbian 5.37 based on 3.14.29 debian stretch without specifying any dtb file.  It is used as a server with openmediavault and homeassistant. I'm running armbian from sd card.
I just made upgrades and got armbian-config 5.64 with an uptime of 70 days.

Hi,
 
I saw you tested your Up board based on atom z8300, so I tested my x5 based on z8350: http://ix.io/1lwg
However, I have only manjaro installed on it and cpufreq is not reported, nor the soc temperature, so maybe this numbers are not relevant for you.
 

You'll see here the state of 4.55 images of Balbes:
In my case I only test successfully debian stretch server image.
 
@Didi, don't forget to use aml_autoscript.zip to update your bootloader (see 1rst post of s905 topic) so that it tries first to boot to sd card. If your dtb file isn't good, you'll not be able to boot even in android if your sdcard is plugged in.

You can actually buy Ugoos UT3S 2GB/16GB on gearbest for less than 40$ (or 36.50€) with GBUT3S coupon: http://www.gearbest.com/tv-box/pp_141997.html?wid=21&lkid=10695139
There is already a dualboot between android and ubuntu, so it's maybe easier to port armbian to it.
 

You can actually buy Ugoos UT3S 2GB/16GB on gearbest for less than 40$ (or 36.50€) with GBUT3S coupon: http://www.gearbest.com/tv-box/pp_141997.html?wid=21&lkid=10695139
There is already a dualboot between android and ubuntu, so it's maybe easier to port armbian to it.
 

To summarize the discussion because it was difficult for me to follow all the answers. The initial objective was to identify a software to manage and process the documentation:
- current input format is markdown
- 2 output formats are expected: html and pdf

Identified solutions:
- mkdocs seems interesting (simple and configurable) to generate static html pages
- pandoc can generate pdf with toc from many document formats
- github wiki is based on markdown and offers a simple way to generate html doc as we can see with current redirection.

Personnally, I used Sphinx for a previous project to generate from the same input files an html documentation and a pdf report (in fact generate latex and then pdf). The input format is restructured text, but markdown can be easily translated to that close language (e.g. with pandoc) more especially if there are already files for each section of the doc. I'm not sure this is the best solution for current case.

One major issue is to define how people can contribute while keeping documentation structure with valid permalink:
- public wiki solutions don't fit this requirement even if it is easy to rollback when problem occurs.
- pull requests on a git repository for the documentation can be chosen, it requires that admins of this repo validate and integrate contributions, but it may offer more guarantee about structure preservation.

The content of the documentation and its structure should also be addressed, but perhaps in another topic.