Merge branch 'master' into mkdocs-upgrade

2019-07-17 12:02:05 +08:00 · 2019-07-17 12:02:05 +08:00 · 61332bf069
parent 2e336ef13c 1979704a18
commit 61332bf069
77 changed files with 435188 additions and 2736 deletions
--- a/docs/arch.md
+++ b/docs/arch.md
@ -0,0 +1,100 @@
+This document is a guide for installing Arch Linux ARM on the Helios4.
+
+**Arch Linux ARM** is a port of Arch Linux for ARM processors. Its design philosophy is simplicity and full control to the end user, and like its parent operating system Arch Linux, aims to be very Unix-like. More info [here](https://archlinuxarm.org/).
+
+## Prerequisite
+
+Refer to the following [section](/install/#what-you-need-before-you-start) of the Helios4 install guide.
+
+## Arch Linux ARM image for Helios4
+
+Arch Linux ARM can be installed on Helios4 using an image file containing both the **Arch Linux ARM system** and the **U-Boot** boot loader.
+
+This image can be created using the `build-archlinux-img-for-helios4.sh` script provided by the [alarm-helios4-image-builder](https://github.com/gbcreation/alarm-helios4-image-builder) project, or you can use pre-built images provided by the same project. Each method is described below.
+
+Once you get an image file, follow the instructions from the [Installing Arch Linux ARM on Helios4](#installing-arch-linux-arm-on-helios4) section below.
+
+### Arch Linux ARM image builder
+
+The `build-archlinux-img-for-helios4.sh` script provides an easy way to automatically create a bootable Arch Linux ARM image file for Helios4.
+
+#### Requirements
+
+The `build-archlinux-img-for-helios4.sh` script expects to be run on a **x86 system running [Arch Linux](https://archlinux.org)**. It needs `qemu-arm-static` to work. You can install it using the [qemu-user-static](https://aur.archlinux.org/packages/qemu-user-static/) or [qemu-user-static-bin](https://aur.archlinux.org/packages/qemu-user-static-bin/) packages from the AUR.
+
+#### Usage
+
+!!! note
+    This script needs to execute commands as superuser. If not run as root, it will re-run itself using sudo.
+
+```shell
+$ git clone https://github.com/gbcreation/alarm-helios4-image-builder.git
+$ cd alarm-helios4-image-builder
+$ sh ./build-archlinux-img-for-helios4.sh
+```
+
+Once the Arch Linux ARM image is created, go to [Installing Arch Linux ARM on Helios4](#installing-arch-linux-arm-on-helios4) section.
+
+### Pre-built images
+
+You can download [here](https://github.com/gbcreation/alarm-helios4-image-builder/releases) pre-built Arch Linux ARM images for Helios4.
+
+```shell
+$ wget https://github.com/gbcreation/alarm-helios4-image-builder/releases/download/2019-02-27/ArchLinuxARM-helios4-2019-02-27.img.gz{,.md5}
+$ md5sum -c ArchLinuxARM-helios4-2019-02-27.img.gz.md5
+$ gunzip ArchLinuxARM-helios4-2019-02-27.img.gz
+```
+
+## Installing Arch Linux ARM on Helios4
+
+Once you get an Arch Linux ARM image, follows these instructions to use it on Helios4:
+
+### Writing image / power-up Helios4 / connecting to serial console
+
+Follows these steps from the Helios4 [install guide](/install):
+
+- [step 2](/install/#step-2-writing-an-image-to-a-microsd-card) to write the Arch Linux ARM image to a microSD card
+- [step 3](/install/#step-3-power-up-helios4) to power-up Helios4
+- [step 4](/install/#step-4-connect-to-helios4-serial-console) to connect to the Helios4 serial console.
+
+!!! note
+    Arch Linux ARM is configured by default to get its IP address from a DHCP server. As an alternative to **step 4**, you can connect to your router to find the IP address given to Helios4, then connect to this latter using SSH.
+
+### Log in
+
+Use the serial console or SSH to the IP address given to Helios4 by your router.
+
+You can login as:
+
+- the default user *alarm* with the password *alarm*
+- the user *root* with password *root*
+
+!!! important
+    For security reasons, it is highly recommended to change the default password of the **alarm** and **root** users.
+
+### Network settings
+
+Arch Linux ARM is configured by default to get its IP address from a DHCP server. To change the network settings, look at the [Network Configuration](https://wiki.archlinux.org/index.php/Network_configuration) page from the Arch Linux wiki.
+
+### Pacman
+
+The Pacman keyring is already initialized in the images created by the `build-archlinux-img-for-helios4.sh` script and the pre-built images. It is also already populated with the Arch Linux ARM package signing keys.
+
+## What to do next?
+
+You can now configure Arch Linux ARM according to your needs and use **pacman** to install 3rd party applications.
+
+Here are some useful links from the [Arch Linux wiki](https://wiki.archlinux.org) to get started:
+
+- [RAID](https://wiki.archlinux.org/index.php/RAID)
+- [dm-crypt/Device encryption](https://wiki.archlinux.org/index.php/Dm-crypt/Device_encryption).
+
+!!! note
+    Read the [Accelerate Disk Encryption](/cesa/#accelerate-disk-encryption) section of the Helios4 wiki before proceeding to learn how to offload disk encryption on the CESA unit.
+
+- [Nextcloud](https://wiki.archlinux.org/index.php/Nextcloud)
+- [NFS](https://wiki.archlinux.org/index.php/NFS)
+- [Samba](https://wiki.archlinux.org/index.php/Samba)
+
+
+*Page contributed by [gbcreation](https://github.com/gbcreation)*
--- a/docs/cesa.md
+++ b/docs/cesa.md
@ -52,12 +52,16 @@ You can refer to following forum [thread](https://forum.armbian.com/topic/8486-h

 ### Prerequisites

-You will need to add *debian source* repository to your APT list in order to download **libssl** source code. Edit */etc/apt/sources.list* and uncomment the following line.
+You will need to add *debian source* repository to your APT list in order to download **libssl** source code. Edit */etc/apt/sources.list* and uncomment the following lines.

 ```
 deb-src http://httpredir.debian.org/debian stretch main contrib non-free
 ```

+```
+deb-src http://security.debian.org/ stretch/updates main contrib non-free
+```
+
 Don't forget after to update your APT database.

 ```
@ -144,13 +148,13 @@ Apply the patch that you can find [here](/files/cesa/openssl-add-cryptodev-suppo
 ```
 wget https://wiki.kobol.io/files/cesa/openssl-add-cryptodev-support.patch

-patch < openssl-add-cryptodev-support.patch openssl1.0-1.0.2l/crypto/engine/eng_cryptodev.c
+patch < openssl-add-cryptodev-support.patch openssl1.0-1.0.2*/crypto/engine/eng_cryptodev.c
 ```

 Now let's compile libssl with **cryptodev** enabled.

 ```
-cd openssl1.0-1.0.2l/
+cd openssl1.0-1.0.2*/

 sed -i -e "s/CONFARGS  =/CONFARGS = -DHAVE_CRYPTODEV/" debian/rules

@ -167,11 +171,11 @@ If all goes well you should see couple of .deb files. Look for the libssl .deb f
 ```
 cd ..

-sudo dpkg -i libssl1.0.2_1.0.2l-2+deb9u3.1_armhf.deb
+sudo dpkg -i libssl1.0.2_1.0.2r-1~deb9u1.1_armhf.deb
 ```

 !!! info
-    A pre-build Debian libssl package (libssl1.0.2_1.0.2l-2+deb9u3.1_armhf.deb) with cryptodev enable is available [here](/files/cesa/libssl1.0.2_1.0.2l-2+deb9u3.1_armhf.deb), if you want to skip the recompile step.
+    A pre-build Debian libssl package (libssl1.0.2_1.0.2r-1~deb9u1.1_armhf.deb) with cryptodev enable is available [here](/files/cesa/libssl1.0.2_1.0.2r-1~deb9u1.1_armhf.deb), if you want to skip the recompile step.

 ### Apache2

@ -217,11 +221,11 @@ UsePrivilegeSeparation yes

 **Client Side: (optional)**

-To make your SSH client supports the cipher define in SSH server side, you might need to edit */etc/ssh/ssh_config* and add the following line.
+To make your SSH client supports the cipher define in SSH server side, you will need to edit */etc/ssh/ssh_config* and add the following line.

 ```
 #   Ciphers aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc
-Ciphers aes128-cbc
+Ciphers +aes128-cbc
 ```

 !!! Important
--- a/docs/docs.md
+++ b/docs/docs.md
@ -1,22 +1,42 @@
 # Helios4 Documents

+## Product Change Notification
+
+Doc-Type | Filename | Date | Download
+---------|----------|------|---------
+PCN|Helios4 PCN 201904220001|2019-04-22|[Download](/files/pcn/Helios4_PCN_201904220001.pdf)
+PCN|Helios4 PCN 201906060001|2019-06-06|[Download](/files/pcn/Helios4_PCN_201906060001.pdf)
+
+
+
 ## Carrier Board

 Doc-Type | Filename | Version | Date | Download | Description
 ---------|----------|---------|------|----------|------------
 Schematics|Helios4 Simplified Schematics|rev 1.1|2018-11-07|[Download](/files/carrier/Helios4_Schematics_R1-1.pdf)|Simplified Schematics - PDF
+Schematics|Helios4 Simplified Schematics|rev 1.2|2019-04-22|[Download](/files/carrier/Helios4_Schematics_R1-2.pdf)|Simplified Schematics - PDF
 Specifications|Helios4 Specifications|rev 02|2017-09-20|[Download](/files/carrier/Helios4_Specifications.pdf)|Product Specifications
 Mechanical|Helios4 Mechanical Assembly|rev 01|2017-08-05|[Download](/files/carrier/Helios4_Mechnical_Assembly.pdf)|Mechanical Design / Assembly
-BOM|Helios4 Bill-Of-Material|rev 1.1|2018-11-07|[Download](/files/carrier/Helios4_BOM_R1-1.xls)| Bill-Of-Material spreadsheet
-PCB Layout|Helios4 PCB Layout|rev 1.1|2018-11-07|[Download](/files/carrier/Helios4_PCB_R1-1.zip)| PCB Layout project files
+PCB Layout|Helios4 PCB Layout|rev 1.1|2018-11-07|[Download](/files/carrier/Helios4_PCB_R1-1.zip)|PCB Layout project files
+PCB Layout|Helios4 PCB Layout|rev 1.2|2019-06-06|[Download](/files/carrier/Helios4_PCB_R1-2.zip)|PCB Layout project files
+PCB Gerber|Helios4 PCB Gerber|rev 1.1|2018-11-07|[Download](/files/carrier/Helios4_Gerber_R1-1.zip)|PCB Gerber files
+PCB Gerber|Helios4 PCB Gerber|rev 1.2|2019-06-06|[Download](/files/carrier/Helios4_Gerber_R1-2.zip)|PCB Gerber files
+PCB Assembly|Helios4 PCB Assembly|rev 1.1|2018-11-07|[Download](/files/carrier/Helios4_Assembly_R1-1.zip)|PCB Assembly files
+PCB Assembly|Helios4 PCB Assembly|rev 1.2|2019-06-06|[Download](/files/carrier/Helios4_Assembly_R1-2.zip)|PCB Assembly files
+BOM|Helios4 Bill-Of-Material|rev 1.1|2018-11-07|[Download](/files/carrier/Helios4_BOM_R1-1.xls)|Bill-Of-Material spreadsheet
+BOM|Helios4 Bill-Of-Material|rev 1.2|2019-06-06|[Download](/files/carrier/Helios4_BOM_R1-2.xls)|Bill-Of-Material spreadsheet
 Software|PCB Layout Browser|rev xx|2018-11-07|[Link](https://www.mentor.com/pcb/downloads/browsers/)|Mentor PCB Layout Browser

+!!! note
+    The PCB layout was done with Mentor Graphic tools, therefore to open the Helios4 PCB files you will need to download the Mentor VX.2.4 Layout Browser free tool [here](https://www.mentor.com/pcb/downloads/browsers/) (available for Linux and Windows).
+
 ## A38x  MicroSoM

 Doc-Type | Filename | Version | Date | Download | Description
 ---------|----------|---------|------|----------|------------
 Brochures|a38x Brochure|rev 1.0|2017-09-05|[Download](/files/som/brochure_a38x_microsom_2017-09-05.pdf)|Official SR a38x Brochure
 Schematics|A38X Simplified Schematics|rev 2.0|2015-10-28|[Download](/files/som/a38x-microsom-schematics-simplified-rev2.00.pdf)|MicroSom A38X Simplified Schematics - PDF
+Schematics|A38X Simplified Schematics|rev 2.1|2019-07-09|[Download](/files/som/a38x-microsom-schematics-simplified-rev2.1.pdf)|MicroSom A38X Simplified Schematics - PDF
 Marvell Documents|Marvell ARMADA 38x Functional Specifications|rev xx|2015-10-25|[Link](https://marvellcorp.wufoo.com/forms/marvell-armada-38x-functional-specifications/)|Marvell ARMADA 38x Functional Specifications
 Marvell Documents|Marvell ARMADA 38x Hardware Specifications|rev xx|2017-03-09|[Link](https://marvellcorp.wufoo.com/forms/marvell-armada-38x-hardware-specifications/)|Marvell ARMADA 38x Hardware Specifications

@ -26,11 +46,20 @@ For more documents on the **A38x SoM** go to [SolidRun Wiki](https://wiki.solid-

 Doc-Type | Filename | Version | Date | Download | Description
 ---------|----------|---------|------|----------|-------------
-Mechanical|Helios4 Case B|rev 4G|2017-09-01|[Download](/files/casing/Helios4_CaseB_r4g.skp)|Case Mechanical Design - SketchUp
-Mechanical|Helios4 Case B|rev 4G|2017-09-01|[Download](/files/casing/Helios4_CaseB_r4g.pdf)|Case Mechanical Design - PDF
-Mechanical|Helios4 Case B|rev 4G|2017-09-01|[Download](/files/casing/Helios4_CaseB_r4g.dxf)|Case Mechanical Design - DXF
-Mechanical|Helios4 Case B|rev 4G|2017-09-01|[Download](/files/casing/Helios4_CaseB_r4g.eps)|Case Mechanical Design - EPS
-Mechanical|Helios4 Case B Assembled|rev 4G|2017-09-01|[Download](/files/casing/Helios4_CaseB_r4g-assembled.skp)|Case Mechanical Design Assembled - SketchUp
+Mechanical|Helios4 Case B|rev 4g|2017-09-01|[Download](/files/casing/Helios4_CaseB_r4g.skp)|Case Mechanical Design - SketchUp
+Mechanical|Helios4 Case B|rev 4g|2017-09-01|[Download](/files/casing/Helios4_CaseB_r4g.pdf)|Case Mechanical Design - PDF
+Mechanical|Helios4 Case B|rev 4g|2017-09-01|[Download](/files/casing/Helios4_CaseB_r4g.dxf)|Case Mechanical Design - DXF
+Mechanical|Helios4 Case B|rev 4g|2017-09-01|[Download](/files/casing/Helios4_CaseB_r4g.eps)|Case Mechanical Design - EPS
+Mechanical|Helios4 Case B Assembled|rev 4g|2017-09-01|[Download](/files/casing/Helios4_CaseB_r4g-assembled.skp)|Case Mechanical Design Assembled - SketchUp
+Mechanical|Helios4 Case B|rev 4j|2019-05-24|[Download](/files/casing/Helios4_CaseB_r4j.skp)|Case Mechanical Design - SketchUp
+Mechanical|Helios4 Case B|rev 4j|2019-05-24|[Download](/files/casing/Helios4_CaseB_r4j.pdf)|Case Mechanical Design - PDF
+Mechanical|Helios4 Case B|rev 4j|2019-05-24|[Download](/files/casing/Helios4_CaseB_r4j.dxf)|Case Mechanical Design - DXF
+Mechanical|Helios4 Case B|rev 4j|2019-05-24|[Download](/files/casing/Helios4_CaseB_r4j.eps)|Case Mechanical Design - EPS
+Mechanical|Helios4 Case B Assembled|rev 4g|2017-09-01|[Download](/files/casing/Helios4_CaseB_r4g-assembled.skp)|Case Mechanical Design Assembled - SketchUp
+Mechanical|Helios4 Mini-Case|rev 2|2019-05-07|[Download](/files/casing/Helios4_MiniCase_r2.skp)|Case Mechanical Design - SketchUp
+Mechanical|Helios4 Mini-Case|rev 2|2019-05-07|[Download](/files/casing/Helios4_MiniCase_r2.pdf)|Case Mechanical Design - PDF
+Mechanical|Helios4 Mini-Case|rev 2|2019-05-07|[Download](/files/casing/Helios4_MiniCase_r2.dxf)|Case Mechanical Design - DXF
+Mechanical|Helios4 Mini-Case|rev 2|2019-05-07|[Download](/files/casing/Helios4_MiniCase_r2.eps)|Case Mechanical Design - EPS

 ## Power Supply

--- a/docs/download.md
+++ b/docs/download.md
@ -2,22 +2,22 @@

 ### Debian 9 - Stretch (by [Armbian](https://www.armbian.com/helios4/))

-[![Debian Stretch](/img/os/debian.png)](https://dl.armbian.com/helios4/archive/Armbian_5.75_Helios4_Debian_stretch_next_4.14.98.7z)<br>
-*MD5SUM : 94939b8ebcbc25ee559bf184d8c607ef<br>
-Build date : 10/02/2019<br>
-Size : 258 MB<br>*
-[Direct Download](https://dl.armbian.com/helios4/archive/Armbian_5.75_Helios4_Debian_stretch_next_4.14.98.7z) - [Torrent Download](https://dl.armbian.com/torrent/Armbian_5.75_Helios4_Debian_stretch_next_4.14.98.7z.torrent)
+[![Debian Stretch](/img/os/debian.png)](https://cdn.kobol.io/files/Armbian_5.77_Helios4_Debian_stretch_next_4.14.106.7z)<br>
+*MD5SUM : 5f2e19d6ecf8a35de89c881fb06bd56e<br>
+Build date : 14/03/2019<br>
+Size : 238 MB<br>*
+[Direct Download](https://cdn.kobol.io/files/Armbian_5.77_Helios4_Debian_stretch_next_4.14.106.7z)

 !!! note
    OMV4 (OpenMediaVault 4) can be installed with the **armbian-config** tool as explained [here](/omv/#install-openmediavault).

 ### Ubuntu 18.04 - Bionic (by [Armbian](https://www.armbian.com/helios4/))

-[![Ubuntu Bionic](/img/os/ubuntu.png)](https://dl.armbian.com/helios4/archive/Armbian_5.75_Helios4_Ubuntu_bionic_next_4.14.98.7z)<br>
-*MD5SUM : d70b2d51b29e6729c33bbec90825f47a<br>
-Build date : 10/02/2019<br>
-Size : 193 MB<br>*
-[Direct Download](https://dl.armbian.com/helios4/archive/Armbian_5.75_Helios4_Ubuntu_bionic_next_4.14.98.7z) [Torrent Download](https://dl.armbian.com/torrent/Armbian_5.75_Helios4_Ubuntu_bionic_next_4.14.98.7z.torrent)
+[![Ubuntu Bionic](/img/os/ubuntu.png)](https://cdn.kobol.io/files/Armbian_5.77_Helios4_Ubuntu_bionic_next_4.14.106.7z)<br>
+*MD5SUM : 90805f23c5c6491bbf1b251f4d3d74a0<br>
+Build date : 14/03/2019<br>
+Size : 177 MB<br>*
+[Direct Download](https://cdn.kobol.io/files/Armbian_5.77_Helios4_Ubuntu_bionic_next_4.14.106.7z)


 ### Syncloud
@ -27,7 +27,7 @@ Size : 193 MB<br>*
 Check their [download page](https://github.com/syncloud/platform/wiki) for latest image.


-## Known Issues / Limitations
+## Known Limitations

 - SDcard High Speed timing have compatibility issue with some brands.

@ -41,7 +41,6 @@ Check their [download page](https://github.com/syncloud/platform/wiki) for lates

    *Can be manually enable, refer to the following [page](/spi).*

- Wake-on-LAN is not yet implemented.

 ## Image List

@ -50,33 +49,8 @@ Check their [download page](https://github.com/syncloud/platform/wiki) for lates

 Filename | Download | MD5
 ---------|----------|----
-**Armbian_5.75_Helios4_Debian_stretch_next_4.14.98.7z**<br>Armbian 5.75 Debian 9 Stretch (Kernel 4.14.98)<br>Build date : 10/02/2019<br>Size : 258 MB|[Download](https://dl.armbian.com/helios4/archive/Armbian_5.75_Helios4_Debian_stretch_next_4.14.98.7z)|94939b8ebcbc25ee559bf184d8c607ef
+**Armbian_5.77_Helios4_Debian_stretch_next_4.14.106.7z**<br>Armbian 5.77 Debian 9 Stretch (Kernel 4.14.106)<br>Build date : 14/03/2019<br>Size : 238 MB|[Download](https://cdn.kobol.io/files/Armbian_5.77_Helios4_Debian_stretch_next_4.14.106.7z)|5f2e19d6ecf8a35de89c881fb06bd56e
+**Armbian_5.77_Helios4_Ubuntu_bionic_next_4.14.106.7z**<br>Armbian 5.77 Ubuntu 18.04 Bionic (Kernel 4.14.106)<br>Build date : 14/03/2019<br>Size : 177 MB|[Download](https://cdn.kobol.io/files/Armbian_5.77_Helios4_Ubuntu_bionic_next_4.14.106.7z)|90805f23c5c6491bbf1b251f4d3d74a0
 **Armbian_5.75_Helios4_Ubuntu_bionic_next_4.14.98.7z**<br>Armbian 5.75 Ubuntu 18.04 Bionic (Kernel 4.14.98)<br>Build date : 10/02/2019<br>Size : 193 MB|[Download](https://dl.armbian.com/helios4/archive/Armbian_5.75_Helios4_Ubuntu_bionic_next_4.14.98.7z)|d70b2d51b29e6729c33bbec90825f47a
 **Armbian_5.72_Helios4_Debian_stretch_next_4.14.94.7z**<br>Armbian 5.72 Debian 9 Stretch (Kernel 4.14.94)<br>Build date : 20/01/2019<br>Size : 260 MB|[Download](https://dl.armbian.com/helios4/archive/Armbian_5.72_Helios4_Debian_stretch_next_4.14.94.7z)|c4b5973931acde6e070b88bdfb32957c
 **Armbian_5.72_Helios4_Ubuntu_bionic_next_4.14.94.7z**<br>Armbian 5.72 Ubuntu 18.04 Bionic (Kernel 4.14.94)<br>Build date : 20/01/2019<br>Size : 192 MB|[Download](https://dl.armbian.com/helios4/archive/Armbian_5.72_Helios4_Ubuntu_bionic_next_4.14.94.7z)|e372bd132de296228ad1a2289d163fa4
-**Armbian_5.68_Helios4_Debian_stretch_next_4.14.88.img.xz**<br>Armbian 5.68 Debian 9 Stretch (Kernel 4.14.88)<br>Build date : 14/12/2018<br>Size : 242 MB|[Download](https://cdn.kobol.io/files/Armbian_5.68_Helios4_Debian_stretch_next_4.14.88.img.xz)|a32a42f694c1aef3ebd8e217be5932e3
-**Armbian_5.68_Helios4_Ubuntu_bionic_next_4.14.88.img.xz**<br>Armbian 5.68 Ubuntu 18.04 Bionic (Kernel 4.14.88)<br>Build date : 14/12/2018<br>Size : 183 MB|[Download](https://cdn.kobol.io/files/Armbian_5.68_Helios4_Ubuntu_bionic_next_4.14.88.img.xz)|125735c9ebd88a91cf4fabd36ea903af
-**Armbian_5.67_Helios4_Debian_stretch_next_4.14.83.7z**<br>Armbian 5.67 Debian 9 Stretch (Kernel 4.14.83)<br>Build date : 26/11/2018<br>Size : 262 MB|[Download](https://dl.armbian.com/helios4/archive/Armbian_5.67_Helios4_Debian_stretch_next_4.14.83.7z)|56bf66e135ee218e715e72741c14737e
-**Armbian_5.67_Helios4_Ubuntu_bionic_next_4.14.83.7z**<br>Armbian 5.67 Ubuntu 18.04 Bionic (Kernel 4.14.83)<br>Build date : 26/11/2018<br>Size : 199 MB|[Download](https://dl.armbian.com/helios4/archive/Armbian_5.67_Helios4_Ubuntu_bionic_next_4.14.83.7z)|d31049b4965363d935e81b94a1af89f0
-
-## Image Archives (Old Images)
-
-!!! warning
-    Even though you can use those images, they are now obsoletes for the following reasons :
-
-    * Debian 8 Jessie is End-Of-Life,
-    * OpenMediaVault 3.X is End-Of-Life,
-    * No more Helios4 support effort on Kernel 4.4.
-
-Filename | Download | MD5
---------|----------|----
-**Armbian_Helios4_Debian_Jessie_4.14.20-OMV_3.0.97.img.xz**<br>Debian 8 Jessie (Kernel 4.14.20) with OMV 3.0.97<br>Build date : 17/02/2018<br>Size : 259 MB|[Download](https://cdn.kobol.io/files/Armbian_Helios4_Debian_Jessie_4.14.20-OMV_3.0.97.img.xz)|963af770df27c351a84622bcfc90617a
-**Armbian_Helios4_Debian_Jessie_4.4.112-OMV_3.0.96.img.xz**<br>Debian 8 Jessie (Kernel 4.4.112) with OMV 3.0.96<br>Build date : 05/02/2018<br>Size : 275 MB|[Download](https://cdn.kobol.io/files/Armbian_Helios4_Debian_Jessie_4.4.112-OMV_3.0.96.img.xz)|45425c2a16f8f3014275046b22010f82
-**Armbian_Helios4_Debian_Jessie_4.4.112.img.xz**<br>Debian 8 Jessie (Kernel 4.4.112)<br>Build date : 05/02/2018<br>Size : 202 MB|[Download](https://cdn.kobol.io/files/Armbian_Helios4_Debian_Jessie_4.4.112.img.xz)|dd6f5ea6e9ac80e4f379d619b71ef1e8
-
-**Default credential for OpenMediaVault image**
-
-```bash
-helios4 login: root
-Password: openmediavault
-```
--- a/docs/files/carrier/Helios4_Assembly_R1-1.zip
+++ b/docs/files/carrier/Helios4_Assembly_R1-1.zip
--- a/docs/files/carrier/Helios4_Assembly_R1-2.zip
+++ b/docs/files/carrier/Helios4_Assembly_R1-2.zip
--- a/docs/files/carrier/Helios4_BOM_R1-1.xls
+++ b/docs/files/carrier/Helios4_BOM_R1-1.xls
--- a/docs/files/carrier/Helios4_BOM_R1-2.xls
+++ b/docs/files/carrier/Helios4_BOM_R1-2.xls
--- a/docs/files/carrier/Helios4_Gerber_R1-1.zip
+++ b/docs/files/carrier/Helios4_Gerber_R1-1.zip
--- a/docs/files/carrier/Helios4_Gerber_R1-2.zip
+++ b/docs/files/carrier/Helios4_Gerber_R1-2.zip
--- a/docs/files/carrier/Helios4_PCB_R1-2.zip
+++ b/docs/files/carrier/Helios4_PCB_R1-2.zip
--- a/docs/files/carrier/Helios4_Schematics_R1-2.pdf
+++ b/docs/files/carrier/Helios4_Schematics_R1-2.pdf
--- a/docs/files/casing/Helios4_CaseB_r4j.dxf
+++ b/docs/files/casing/Helios4_CaseB_r4j.dxf
--- a/docs/files/casing/Helios4_CaseB_r4j.eps
+++ b/docs/files/casing/Helios4_CaseB_r4j.eps
--- a/docs/files/casing/Helios4_CaseB_r4j.pdf
+++ b/docs/files/casing/Helios4_CaseB_r4j.pdf
--- a/docs/files/casing/Helios4_CaseB_r4j.skp
+++ b/docs/files/casing/Helios4_CaseB_r4j.skp
--- a/docs/files/casing/Helios4_MiniCase_r2.dxf
+++ b/docs/files/casing/Helios4_MiniCase_r2.dxf
--- a/docs/files/casing/Helios4_MiniCase_r2.eps
+++ b/docs/files/casing/Helios4_MiniCase_r2.eps
--- a/docs/files/casing/Helios4_MiniCase_r2.pdf
+++ b/docs/files/casing/Helios4_MiniCase_r2.pdf
--- a/docs/files/casing/Helios4_MiniCase_r2.skp
+++ b/docs/files/casing/Helios4_MiniCase_r2.skp
--- a/docs/files/cesa/libssl1.0.2_1.0.2l-2+deb9u3.1_armhf.deb
+++ b/docs/files/cesa/libssl1.0.2_1.0.2l-2+deb9u3.1_armhf.deb
--- a/docs/files/cesa/libssl1.0.2_1.0.2r-1~deb9u1.1_armhf.deb
+++ b/docs/files/cesa/libssl1.0.2_1.0.2r-1~deb9u1.1_armhf.deb
--- a/docs/files/cesa/openssl-add-cryptodev-support.patch
+++ b/docs/files/cesa/openssl-add-cryptodev-support.patch
--- a/docs/files/pcn/Helios4_PCN_201904220001.pdf
+++ b/docs/files/pcn/Helios4_PCN_201904220001.pdf
--- a/docs/files/pcn/Helios4_PCN_201906060001.pdf
+++ b/docs/files/pcn/Helios4_PCN_201906060001.pdf
--- a/docs/files/som/a38x-microsom-schematics-simplified-rev2.1.pdf
+++ b/docs/files/som/a38x-microsom-schematics-simplified-rev2.1.pdf
--- a/docs/freebsd.md
+++ b/docs/freebsd.md
@ -72,3 +72,5 @@ This time, just sit back and watch as FreeBSD comes up.

 ### Default User
 The FreeBSD image by crochet comes with an unlocked root account. This means you do not need to enter a password to log in as root.
+
+*Page contributed by [Artox](https://github.com/Artox)*
--- a/docs/hardware.md
+++ b/docs/hardware.md
@ -6,7 +6,6 @@
 ### A388 System-On-Chip
 ![!Block Diagram](/img/hardware/soc_block_diagram.png)

-
 ## Connector / Interface List

 ![!Board Legend](/img/hardware/board_legend.jpg)
@ -77,6 +76,34 @@ Helios4 board exposes on header J9 the SoC I2C Bus 1. Below is the header pin-ou

 ![I2C Pinout](/img/hardware/i2c_pinout.png)

+## Power Consumption
+
+**Board only**
+
+* Idle  : 3.6 Watts
+* Active : 5.6 Watts
+
+**Full Kit (with 4x HDDs)**
+
+| State               | AC calculated<br>power consumption | DC measured<br>power consumption | Remarks             |
+|---------------------|----------------------|----------------------|---------------------|
+|  Idle               | 19.3 W               | 16.8 W               |                     |
+|  HDD Read Access    | 27.4 W               | 22.8 W               |                     |
+|  HDD Write Access   | 30.3 W               | 25.2 W               |                     |
+|  Standby            | 8.0 W                | 6.7 W                | HDD in Standby mode |
+|  Suspend-to-Ram     | 7.2 W                | 6.0 W                | HDD in Standby mode |
+
+!!! note
+    Measures were done using a Current Clamp Meter on the Helios4 12V DC input. AC Power consumption is calculated based on a AC/DC conversion efficiency of 85%.
+
+    * Meter tool : Extech 380942 - 30A True RMS AC/DC Mini Clamp
+    * AC/DC Adapter : yczx1268 (efficiency : 85%)
+    * AC Input Voltage: 220V
+    * HDD: 4x WD Red 2TB (WD20EFRX) configured as RAID10
+    * Network : Connected at 1000Mb/s
+    * OS: ARMBIAN 5.73 stable Debian GNU/Linux 9 (stretch) 4.14.98-mvebu   
+
+
 ## HDD Recommendation List

 We recommend HDD which are designed for NAS (Network Attached Storage). Those NAS HDD are specially conceived for reliable 24/7 operation and offers lower power consumption and dissipation, less vibration and noise, and finally better warranty. We recommend the following models :
--- a/docs/i2c.md
+++ b/docs/i2c.md
@ -15,7 +15,7 @@ The I2C interface on Helios4 board is located at header **J9** which exposes the

 You will need to use Female to Female Jumper Wire (a.k.a Dupont Cable) to connect your display to Helios4 board.

-Connect matching pin on each side (GND to GND, VDD to VDD, SDA to SDA, etc...). Ideally you use cables of different colors to easily check that your wiring is correct.
+Connect matching pin on each side (GND to GND, VCC to VCC, SDA to SDA, etc...). Ideally you use cables of different colors to easily check that your wiring is correct.

 ![oled i2c wiring](/img/i2c/wiring_01.jpeg)
 ![board i2c wiring](/img/i2c/wiring_02.jpeg)
@ -71,6 +71,9 @@ sudo ./install.sh

 Test which display model is the correct one by launching manually **sys-oled** and trying different display model as parameter until the System Status is showing correctly on the display.

+!!! info
+    If you get your OLED display as part of your Helios4 Kit, then you can skip to next [step](#2-configure-display-info) since **sys-oled** is already configure to use the correct model.
+
 Example :

 ```
@ -81,28 +84,35 @@ sudo sys-oled --display sh1106

 Supported values : ssd1306 (default), ssd1322, ssd1325, ssd1327, ssd1331, ssd1351, sh1106.

-Once you know which display model is the correct one, edit */usr/local/etc/sys-oled.conf* and update the **DISPLAY=** line.
+Once you know which display model is the correct one, edit */etc/sys-oled.conf* and update the **display_model=** line.


-#### 2. Configure storage info
+#### 2. Configure display info

-For now **sys-oled** is a very crude python app that will require you to edit it directly in order to customize what you want to display.
-
-Edit **sys-oled** script and look for the *status()* function.
+By default **sys-oled** will display usage info of your micro SDcard which is most probably your Root File System. You can display storage usage info of one more storage device by editing */etc/sys-oled.conf*

 ```
-sudo nano /usr/local/bin/sys-oled
+sudo nano /etc/sys-oled.conf
 ```

-You can edit the following lines to define for which storage devices you want to display info.
+You can edit the following lines to define for which storage devices you want to display usage info.

 ```
-d.text((0, 27), disk_usage('sd', '/'), font=font, fill="white")
-d.text((0, 39), disk_usage('md0', '/mnt/md0'), font=font, fill="white")
+# Storage Device 1
+# Device name
+storage1_name = sd
+
+# Device mount path
+storage1_path = /
+
+# Storage Device 2
+storage2_name= md0
+storage2_path= /mnt/md0
+
 ```

 In the above example, we are displaying **sd** (SDcard) usage which is the rootfs mounted on *'/'*. We are also displaying **md0** (RAID array) that is mounted on *'/mnt/mnd0'*.
-The values *(0, 27)* and *(0, 39)* correspond to the X, Y positions of displayed texts.
+

 #### 3. Start the service

--- a/docs/img/hardware/i2c_pinout.png
+++ b/docs/img/hardware/i2c_pinout.png
--- a/docs/img/install/armbian-config.png
+++ b/docs/img/install/armbian-config.png
--- a/docs/img/install/armbian-config_ip-static.png
+++ b/docs/img/install/armbian-config_ip-static.png
--- a/docs/img/install/armbian-config_ip.png
+++ b/docs/img/install/armbian-config_ip.png
--- a/docs/img/install/armbian-config_network.png
+++ b/docs/img/install/armbian-config_network.png
--- a/docs/img/install/first_login.png
+++ b/docs/img/install/first_login.png
--- a/docs/img/install/network_config.png
+++ b/docs/img/install/network_config.png
--- a/docs/img/install/softy.png
+++ b/docs/img/install/softy.png
--- a/docs/img/install/ssh_login.png
+++ b/docs/img/install/ssh_login.png
--- a/docs/img/kit/assembly_pic47.jpg
+++ b/docs/img/kit/assembly_pic47.jpg
--- a/docs/img/kit/assembly_pic48.jpg
+++ b/docs/img/kit/assembly_pic48.jpg
--- a/docs/img/kit/assembly_pic49.jpg
+++ b/docs/img/kit/assembly_pic49.jpg
--- a/docs/img/kit/assembly_pic50.jpg
+++ b/docs/img/kit/assembly_pic50.jpg
--- a/docs/img/kit/assembly_pic51.jpg
+++ b/docs/img/kit/assembly_pic51.jpg
--- a/docs/img/kit/assembly_pic52.jpg
+++ b/docs/img/kit/assembly_pic52.jpg
--- a/docs/img/kit/assembly_pic53.jpg
+++ b/docs/img/kit/assembly_pic53.jpg
--- a/docs/img/kit/assembly_pic54.jpg
+++ b/docs/img/kit/assembly_pic54.jpg
--- a/docs/img/kit/assembly_pic55.jpg
+++ b/docs/img/kit/assembly_pic55.jpg
--- a/docs/img/kit/assembly_pic56.jpg
+++ b/docs/img/kit/assembly_pic56.jpg
--- a/docs/img/kit/assembly_pic57.jpg
+++ b/docs/img/kit/assembly_pic57.jpg
--- a/docs/img/kit/i2c_board_pinout.jpg
+++ b/docs/img/kit/i2c_board_pinout.jpg
--- a/docs/img/kit/i2c_display_pinout.png
+++ b/docs/img/kit/i2c_display_pinout.png
--- a/docs/img/kit/oled_set.jpg
+++ b/docs/img/kit/oled_set.jpg
--- a/docs/img/omv/install-1.png
+++ b/docs/img/omv/install-1.png
--- a/docs/img/omv/install-2.png
+++ b/docs/img/omv/install-2.png
--- a/docs/img/omv/install-3.png
+++ b/docs/img/omv/install-3.png
--- a/docs/img/pwm/fan_control_schematic_rev1_1.png
+++ b/docs/img/pwm/fan_control_schematic_rev1_1.png
--- a/docs/img/pwm/fan_control_schematic_rev1_2.png
+++ b/docs/img/pwm/fan_control_schematic_rev1_2.png
--- a/docs/img/pwm/fan_speed_comparison.png
+++ b/docs/img/pwm/fan_speed_comparison.png
--- a/docs/img/pwm/fan_speed_graph_new_fan.png
+++ b/docs/img/pwm/fan_speed_graph_new_fan.png
--- a/docs/img/pwm/fan_speed_graph_new_fan_linux.png
+++ b/docs/img/pwm/fan_speed_graph_new_fan_linux.png
--- a/docs/img/pwm/fan_speed_graph_old_fan.png
+++ b/docs/img/pwm/fan_speed_graph_old_fan.png
--- a/docs/img/pwm/fan_speed_graph_old_fan_linux.png
+++ b/docs/img/pwm/fan_speed_graph_old_fan_linux.png
--- a/docs/img/pwm/fan_speed_graph_type_a_fan.png
+++ b/docs/img/pwm/fan_speed_graph_type_a_fan.png
--- a/docs/img/pwm/fan_speed_graph_type_a_fan_linux.png
+++ b/docs/img/pwm/fan_speed_graph_type_a_fan_linux.png
--- a/docs/img/pwm/fan_speed_graph_type_c_fan.png
+++ b/docs/img/pwm/fan_speed_graph_type_c_fan.png
--- a/docs/img/pwm/fan_speed_graph_type_c_fan_linux.png
+++ b/docs/img/pwm/fan_speed_graph_type_c_fan_linux.png
--- a/docs/img/pwm/fan_type_a_photo.jpg
+++ b/docs/img/pwm/fan_type_a_photo.jpg
--- a/docs/img/pwm/fan_type_c_photo.jpg
+++ b/docs/img/pwm/fan_type_c_photo.jpg
--- a/docs/index.md
+++ b/docs/index.md
@ -36,6 +36,7 @@ The Helios4 is an open source and open hardware project, therefore our objective
 |Boot Mode Selector|- SPI<br>- SD Card<br>- UART<br>- SATA|
 |SPI NOR Flash|32Mbit onboard|
 |PWM FAN|2|
+|RTC Battery|1|
 |DC input|12V / 8A|

 |**Mechanical Specifications**||
--- a/docs/install.md
+++ b/docs/install.md
@ -50,11 +50,13 @@ Etcher is a graphical SD card writing tool that works on Mac OS, Linux and Windo
 ### Under Linux (via Terminal)

 ```bash
-unxz Helios4_Debian_Jessie_4.4.96.img.xz
+7z e Armbian_5.90_Helios4_Debian_buster_next_4.19.59.7z

-sudo dd bs=4M if=Helios4_Debian_Jessie_4.4.96.img of=/dev/sdX conv=fsync
+sudo dd bs=4M if=Armbian_5.90_Helios4_Debian_buster_next_4.19.59.img of=/dev/sdX conv=fsync
 ```

+*Replace the filename by the image file name you downloaded.*
+
 !!! note
    /dev/sdX is where the microSD is mapped in your Linux machine, change the 'X' to your corresponding mapped device. If you set /dev/sdX to a wrong device then you might risk erasing a hard drive or different device than the designated microSD.

@ -135,22 +137,19 @@ You will be prompted to change the root password and then create a new user acco
 By default Helios4 will try to obtain an IP address via DHCP. To figure out what is the allocated IP address you will need to type the following command in the console.

 ```bash
-sudo ifconfig eth0
+ip addr show dev eth0
 ```

 ![Network Config](/img/install/network_config.png)

 Here the IP address of Helios4 is **10.10.10.1**.

-!!! note
-    Openmediavault comes with **mDNS** server (Avahi daemon). Therefore if your desktop/laptop runs a mDNS client you can reach the board via the following hostname address : **helios4.local**
-
 ### Set IP address

 If you wish to manually configure your IP address you can use the **armbian-config** tool.

 ```bash
-sudo armbian-config
+armbian-config
 ```

 ![Armbian-config](/img/install/armbian-config.png)
@ -183,6 +182,8 @@ You can now connect by SSH to your Helios4 to carry on with your configuration.

 If you want to install OpenMediaVault, the next-gen network attached storage (NAS) software, refer to the [OMV](/omv) page.

+If you have assembled an OLED Display as part of your Helios4 setup, it can be the right time to set it up. Refer to the following [section](/i2c/#sys-oled-application) that will explain you how to install the **sys-oled** application which control the OLED display.
+
 For other software you can use **armbian-config** which provides an easy way to install 3rd party applications. You can also refer to our *Software* section to find tutorials that will help you to setup manually your Helios4.

 ```bash
--- a/docs/kit.md
+++ b/docs/kit.md
@ -9,6 +9,19 @@

 ![Kit Assembly](/img/kit/assembly_pic1.jpg)

+Since Helios4 Batch 3 we added to the Kit an OLED Display kit containing
+
+* OLED 1.3" I2C display
+* 4-wire dupont cable (**Length : 30cm**)
+* 4x clear plastic screws + nuts
+
+![Kit Assembly](/img/kit/oled_set.jpg)
+
+!!! note
+    The instructions to install the OLED Display have been added to the end of this page.
+    Click [here](#oled-display-part-a) to jump to the section.
+
+
 ## What you need

 * Phillips #2 Screwdriver
@ -173,6 +186,9 @@

 ## **Step 6** - Casing assembly 1/2

+!!! important
+    If you kit comes with an OLED display then complete first the following [section](#oled-display-part-a) before going any further.
+
 > **Prepare and position the items as shown below.**

 ![Kit Assembly](/img/kit/assembly_pic36.jpg)
@ -210,21 +226,89 @@

 ![Kit Assembly](/img/kit/assembly_pic43.jpg)

-!!! note
-     You will have to push the HDD cables inside in order the slide in the front panel.
+!!! important
+    If you kit comes with an OLED display then skip to the following [section](#oled-display-part-b).

 > **Slide in front plate.**

+!!! note
+     You will have to push the HDD cables inside in order to slide in the front panel.
+
 ![Kit Assembly](/img/kit/assembly_pic44.jpg)

 > **Slide in top plate.**

 ![Kit Assembly](/img/kit/assembly_pic45.jpg)

+## Optional Assembly Step
+
+### OLED Display - Part A
+
+> **Prepare the following items.**
+
+* OLED display
+* 4-wire dupont cable (**Length : 30cm**)
+* 4x clear plastic screws + nuts
+* Front Panel
+
+![Kit Assembly](/img/kit/assembly_pic47.jpg)
+
+
+> **Connect the 4-wire cable to the J9 header**
+
+!!! note
+    It doesn't matter if the color of your cable won't match the one you see in the picture, just plug in any order.
+
+![Kit Assembly](/img/kit/assembly_pic48.jpg)
+
+![Kit Assembly](/img/kit/assembly_pic49.jpg)
+
+
+> **Assemble the OLED display to the front panel. Respect orientation.**
+
+!!! warning
+    Don't tighten too much the nuts, you don't want the OLED circuit board to bend or break.
+
+![Kit Assembly](/img/kit/assembly_pic50.jpg)
+
+![Kit Assembly](/img/kit/assembly_pic51.jpg)
+
+![Kit Assembly](/img/kit/assembly_pic52.jpg)
+
+**Now you can jump back to Casing Assembly [section](#step-6-casing-assembly-12).**
+
+### OLED Display - Part B
+
+> **Connect the 4-wire cable to the OLED screen.**
+
+!!! important
+    The PIN order is different between the J9 header and the OLED header. You will need to connect each cable to match the same PIN name between the OLED header and the J9 header (GND to GND, VCC to VCC, SDA to SDA, etc...). See below the J9 and Display header pinouts.
+
+![I2C Board Pinout](/img/kit/i2c_board_pinout.jpg)
+
+![I2C Display Pinout](/img/kit/i2c_display_pinout.png)
+
+**In our current example, the correct wiring would then look like this:**
+
+![Kit Assembly](/img/kit/assembly_pic53.jpg)
+
+![Kit Assembly](/img/kit/assembly_pic54.jpg)
+
+> **Slide in front plate.**
+
+!!! note
+     You will have to push the HDD cables inside in order to slide in the front panel.
+
+![Kit Assembly](/img/kit/assembly_pic55.jpg)
+
+> **Slide in top plate.**
+
+![Kit Assembly](/img/kit/assembly_pic56.jpg)
+
 ## What to do next ?

 AWESOME !!! You have completed Helios4 Kit Assembly.

 **Now you can jump to the [install section](/install).**

-![Kit Assembly](/img/kit/assembly_pic46.jpg)
+![Kit Assembly](/img/kit/assembly_pic57.jpg)
--- a/docs/mdadm.md
+++ b/docs/mdadm.md
@ -12,9 +12,9 @@ In this guide, we will show how to create different RAID configurations :

 ### Fix mdadm

-You might see the following error message in your boot messages *"mdadm: initramfs boot message: /scripts/local-bottom/mdadm: rm: not found"*
+Under Debian 9 (Stretch) you might see the following error message in your boot messages *"mdadm: initramfs boot message: /scripts/local-bottom/mdadm: rm: not found"*. This minor issue has been fixed in Debian 10 (Buster).

-To fix this minor issue simply edit the *mdadm* hook script of initramfs:
+To fix this minor issue in Debian 9, simply edit the *mdadm* hook script of initramfs:

    sudo nano /usr/share/initramfs-tools/hooks/mdadm

@ -377,7 +377,7 @@ if [ $EVENT == "RebuildStarted" ]; then
    echo 1 > $BRIGHTNESS
 fi

-# An md array that was rebuilding, isn't any more, either because it finished normally or was aborted. 
+# An md array that was rebuilding, isn't any more, either because it finished normally or was aborted.
 if [ $EVENT == "RebuildFinished" ]; then
    echo none > $TRIGGER
    echo 0 > $BRIGHTNESS
--- a/docs/nextcloud.md
+++ b/docs/nextcloud.md
@ -1,10 +1,10 @@
 Nextcloud is an open-source software suite that allows users to store their data such as files, contacts, calendars, news feed, TODO lists and much more, on their personal servers. It is using standard protocols such as webdavm, carddav and caldav. It also provides client applications so users can easily manage and synchronize their data among Linux, MacOS, Windows platforms and smart phones, which makes Nextcloud a great free alternative to proprietary cloud services such as Dropbox, Google Drive, iCloud, etc…

-In this tutorial we will install and configure Nextcloud 14 on a Debian 9 Stretch.
+In this tutorial we will install and configure Nextcloud 16 on a Debian 10 Buster.

 ## Step 0 - Requirements

-* You should have Debian 9 Stretch running on your Helios4. Refer to [Install](/install) page for instructions.
+* You should have Debian 10 Buster running on your Helios4. Refer to [Install](/install) page for instructions.

 * You should have setup your storage. This guide will assume you have setup a RAID array mounted to **/mnt/md0**. Refer to [Mdadm](/mdadm) page for guideline on how to setup a RAID array.

@ -18,7 +18,7 @@ A web server is required to run Nextcloud, in this tutorial we will use Apache2.

 You need to install PHP7 and the modules required by NextCloud.

-    sudo apt-get install php7.0 libapache2-mod-php7.0 php7.0-common php7.0-gd php7.0-json php7.0-mysql php7.0-curl php7.0-mbstring php7.0-intl php7.0-mcrypt php7.0-imagick php7.0-xml php7.0-zip
+    sudo apt-get install php7.3 libapache2-mod-php7.3 php7.3-common php7.3-gd php7.3-json php7.3-mysql php7.3-curl php7.3-mbstring php7.3-intl php-imagick php7.3-xml php7.3-zip php7.3-opcache

 ## Step 3 - Install and Configure MariaDB

@ -53,13 +53,13 @@ Don’t forget to replace *‘PASSWORD’* with an actual strong password. Combi

 ## Step 4 - Download and install Nextcloud

-Go to Nextcloud’s official website and download Nextcloud 14 to your Helios4. Currently latest stable version is Nextcould 14.
+Go to Nextcloud’s official website and download Nextcloud 16 to your Helios4. Currently latest stable version is Nextcould 16.

-    wget https://download.nextcloud.com/server/releases/nextcloud-14.0.0.zip
+    wget https://download.nextcloud.com/server/releases/nextcloud-16.0.3.zip

 Extract the downloaded ZIP archive in a directory Apache will have access to, and change the ownership of the nextcloud directory to the web server user.

-    sudo unzip nextcloud-14.0.0.zip -d /mnt/md0
+    sudo unzip nextcloud-16.0.3.zip -d /mnt/md0
    sudo chown -R www-data:www-data /mnt/md0/nextcloud/

 Once all Nextcloud prerequisites are fulfilled, we can complete the installation through the command line. Change the current working directory
@ -76,6 +76,35 @@ If the installation is successful you will get the following output

    Nextcloud was successfully installed

+### Update PHP settings
+
+Some of the default PHP settings for Apache2 need to be updated in order to meet Nextcloud requirements.
+
+
+    sudo nano /etc/php/7.3/apache2/php.ini
+
+
+Update the following values
+
+* memory_limit = 512M
+* upload_max_filesize = 1G
+
+### Install PHP APCu
+
+PHP APCu provides data caching that can be used to accelerate the performance of a PHP application such as NextCloud.
+
+    sudo apt-get install php-apcu
+
+Edit the Nextcloud config.php file
+
+```bash
+sudo nano config/config.php
+```
+
+Add the following line
+
+    'memcache.local' => '\OC\Memcache\APCu',
+
 ### Update Apache configuration

 In order to allow Apache to access the location where you installed Nextcloud you need to edit /etc/apache2/apach2.conf.
@ -93,7 +122,6 @@ Append the following at the bottom of the file:
            Require all granted
    </Directory>  

-
 ### Create Apache Virtual Host

 !!! important
@ -141,15 +169,17 @@ Save the file and enable the newly created virtual host

 To activate the new configuration, you need to reload Apache2

-    sudo systemctl reload apache2
+    sudo systemctl restart apache2


-Edit the config/config.php file and add mysubdomain.dynu.net as a trusted domain
+Edit the Nextcloud config.php file and add mysubdomain.dynu.net as a trusted domain

 ```bash
 sudo nano config/config.php
 ```

+Edit the following section
+
    'trusted_domains' =>
      array (
        0 => 'localhost',
@ -157,10 +187,12 @@ sudo nano config/config.php
      ),


-With this step the Nextcloud 14 installation is completed. You can now visit http://mysubdomain.dynu.net and login to your Nextcloud instance using the credentials used in the installation command above.
+With this step the Nextcloud 16 installation is completed. You can now visit http://mysubdomain.dynu.net and login to your Nextcloud instance using the credentials used in the installation command above.

 ![NextCloud Login Page](/img/nextcloud/login.png)

+Log in with user **admin** and the password you set up previously.
+
 ## Step 5 - Install and Configure Let's Encrypt (HTTPS)

 Finally it is a must to setup HTTPS for your nextcloud install. For that we will use **Let's Encrypt** certificate facility and the available tool **Certbot** to automatically install and configure your certificate.
--- a/docs/omv.md
+++ b/docs/omv.md
@ -11,10 +11,6 @@ OpenMediaVault (OMV) is a next-gen network attached storage (NAS) software based

 You can easily install OMV with the **armbian-config** tool.

-!!! note
-    If you have installed a pre-built OpenMediaVault image you can skip this step.<br>
-    **Important :** pre-built OMV images are now obsoletes.
-
 Connect to your Helios4 via SSH as explained [here](/install/#step-7-connect-to-helios4-via-ssh).

 Launch **armbian-config** and follow the steps.
--- a/docs/pwm.md
+++ b/docs/pwm.md
@ -11,27 +11,41 @@ The term *duty cycle* describes the proportion of 'on' time to the regular inter

 ## PWM Fan Implementation

-### Type A
+### Type-A

 ![Type A Curve](/img/pwm/fan_type_a_curve.jpg)

-### Type B
+### Type-B

 ![Type B Curve](/img/pwm/fan_type_b_curve.jpg)

-### Type C
+### Type-C

 ![Type C Curve](/img/pwm/fan_type_c_curve.jpg)

 ## Helios4 Fan Control Schematic

-![Helios4 Fan control](/img/pwm/fan_control_schematic.png)
+### Board Rev 1.1

+![Helios4 Fan control Rev1.1](/img/pwm/fan_control_schematic_rev1_1.png)

-| Description | Connector J10 | J17 | Remarks |
+**Remarks**
+
+| Description | Header J10 | Header J17 | Remarks |
 |-----------|---------|-----------|---------|
 | PWM pin | gpio41 | gpio55 | 3.3V pull up fan **ONLY**! Early generation of 4-wire pwm fan may use 5V pull-up |
-| SENSE pin | gpio43 | gpio48 | SENSE pin is not used yet |
+| SENSE pin | gpio43 | gpio48 | SENSE pin is not implemented yet |
+| PWM Frequency | 25 kHz | 25 kHz | defined in device tree |
+
+### Board Rev 1.2
+
+![Helios4 Fan control Rev 1.2](/img/pwm/fan_control_schematic_rev1_2.png)
+
+**Remarks**
+
+| Description | Header J10 | Header J17 | Remarks |
+|-----------|---------|-----------|---------|
+| SENSE pin | gpio43 | gpio48 | SENSE pin is not implemented yet |
 | PWM Frequency | 25 kHz | 25 kHz | defined in device tree |

 ## Bundled Fan
@ -48,9 +62,9 @@ Connector Pinout
 |  4  |  Control |   Blue     |


-### Old Fan (Batch 1)
+### Type-A Fan (Batch 1 & 3)

-![Old Fan](/img/pwm/fan_old_photo.jpg)
+![Type-A Fan](/img/pwm/fan_type_a_photo.jpg)

 Fan Specification

@ -61,14 +75,14 @@ Fan Specification
 | Shut off | No | | Not Supported |
 | Implementation Type | A |  |  |

-![Old Fan Speed Graph](/img/pwm/fan_speed_graph_old_fan.png)
+![Type-A Fan Speed Graph](/img/pwm/fan_speed_graph_type_a_fan.png)

 !!! info
    Duty cycle data is converted from Linux PWM

-### New Fan (Batch 2)
+### Type-C Fan (Batch 2)

-![New Fan](/img/pwm/fan_new_photo.jpg)
+![Type-C Fan](/img/pwm/fan_type_c_photo.jpg)

 Fan Specification

@ -79,7 +93,7 @@ Fan Specification
 | Shut off | Yes |  | duty cycle  <= 5.5% and restart @ duty cycle > 9% |
 | Implementation Type | C |  |  |

-![New Fan Speed Graph](/img/pwm/fan_speed_graph_new_fan.png)
+![Type-C Speed Graph](/img/pwm/fan_speed_graph_type_c_fan.png)

 !!! info
    Duty cycle data is converted from Linux PWM
@ -112,9 +126,9 @@ Linux use 8-bit integer to represent duty cycle. PWM value 0 represent 0% duty c

 Below graphs are bundled fan speed vs pwm value instead of duty cycle.

-![Old Fan Speed Graph](/img/pwm/fan_speed_graph_old_fan_linux.png)
+![Type-A Fan Speed Graph](/img/pwm/fan_speed_graph_type_a_fan_linux.png)

-![New Fan Speed Graph](/img/pwm/fan_speed_graph_new_fan_linux.png)
+![Type-C Fan Speed Graph](/img/pwm/fan_speed_graph_type_c_fan_linux.png)


 ### Patch requirement
@ -218,13 +232,13 @@ MINSTART

 Sets the minimum speed at which the fan begins spinning. You should use a safe value to be sure it works, even when the fan gets old.

-New bundled fan restart at 15, added 5 for safety (in case of aging fan) give us **20**. The value does not affect old bundle fan.
+Type-C fan restart at 15, added 5 for safety (in case of aging fan) give us **20**. The value does not affect Type-A fan.

 MINSTOP

 The minimum speed at which the fan still spins. Use a safe value here, too.

-New bundled fan stopped at 24, added 5 for safety (in case of aging fan) give us **29**. The value does not affect old bundle fan.
+Type-C fan stopped at 24, added 5 for safety (in case of aging fan) give us **29**. The value does not affect Type-A fan.

 -----

@ -246,7 +260,7 @@ MINPWM

 The PWM value to use when the temperature is below MINTEMP. Typically, this will be either 0 if it is OK for the fan to plain stop, or the same value as MINSTOP if you don't want the fan to ever stop. If this value isn't defined, it defaults to 0 (stopped fan).

-Set minimum PWM value to **0**. On new bundled fan, it would stopped the fan while on old bundled fan it would run in minimal speed.
+Set minimum PWM value to **0**. On Type-C fan, it would stopped the fan while on Type-A fan it would run in minimal speed.


 !!! note
--- a/docs/wol.md
+++ b/docs/wol.md
@ -7,7 +7,13 @@ The Armada 388 SoC provides several trigger options from different peripherals t

 Currently Helios4 uses the PHY interrupt and 'Wake on GPIO' event to implement Wake-on-LAN.

-## Device Tree Support
+
+## Add WoL Support
+
+!!! note
+		Starting Armbian version **5.77** the Wake-on-LAN support has been added by default. So you might want to upgrade your system via APT to skip this section.
+
+### Device Tree

 Linux provides gpio-keys driver to handle GPIO event and can be configured as wakeup source.

@ -27,7 +33,7 @@ Linux provides gpio-keys driver to handle GPIO event and can be configured as wa

 Device Tree Patch can be found [here](/files/wol/helios4-dts-add-wake-on-lan-support.patch).

-## Kernel Patch
+### Kernel

 Current gpio-mvebu driver does not implement [irq_set_wake()](https://www.kernel.org/doc/html/v4.14/core-api/genericirq.html?highlight=irq_set_wake#c.irq_chip)
 to support GPIO as wakeup source and properly route it to upper interrupt controller (Arm GIC).
@ -87,13 +93,16 @@ Patch for Linux Kernel 4.14.x can be found [here](/files/wol/lk4.14-mvebu-gpio-a

 ## Enabling WOL

+!!! note
+		Latest Armbian images, starting version **5.77**, already have the WoL enabled by default for eth0. So you may skip this step.
+
 Enable the PHY to raise an interrupt when magic packet received :

 ```
 sudo ethtool -s eth0 wol g
 ```

-To make it permanent, create the following file */etc/systemd/system/wol@.service* and copy the following:
+To make it permanent, create the following file */lib/systemd/system/wol@.service* and copy the following:

 ```
 [Unit]
@ -130,7 +139,7 @@ sudo systemctl suspend

 To wake up your suspended Helios4 you need to send it a magic packet from a machine on the same network.

-Before putting Helios4 in suspend mode, you need to know its MAC address. Use **ip link** command. In example below the MAC address is *02:fc:e7:3d:b8:c8*.
+Before putting Helios4 in suspend mode, you need to know its MAC address. Use **ip link** command. In the example below the MAC address is *02:fc:e7:3d:b8:c8*.

 ```
 ip link
@ -145,16 +154,22 @@ ip link

 From a Linux machine (running Debian/Ubuntu) on the same network :

-1. Install **wakeonlan** tool
+1. Install **etherwake** tool

 ```
-sudo apt-get install wakeonlan
+sudo apt-get install etherwake
 ```

 2. Send magic packet

 ```
-sudo wakeonlan 02:fc:e7:3d:b8:c8
+sudo etherwake 02:fc:e7:3d:b8:c8
+```
+
+If your system doesn't have an interface named *eth0*, you will need to specify the network interface you want to use to send out the magic packet. Example :
+
+```
+sudo etherwake -i enx00051bd1ca66 02:fc:e7:3d:b8:c8
 ```

 You can refer to this [guide](https://www.cyberciti.biz/tips/linux-send-wake-on-lan-wol-magic-packets.html) from *cyberciti.biz*.
@ -165,16 +180,14 @@ Measured using Sonoff POW R2 on AC side

 | Power state   | Power (Watt)  | Current (Ampere) | Remarks |
 |---------------|---------------|------------------|---------|
-|  Idle         | 16.18 - 19.87 | 0.14 - 0.17      | |
-|  Standby      |  8.24 -  8.63 | 0.09 - 0.10      | |
-|  Suspend      |  7.46 -  7.71 | 0.07 - 0.08      | |
-| Halt/Shutdown | 11.95         | 0.11             | HDDs still active, fans run on full speed |
+|  Idle         | 19.87 				| 0.17						 |				 |
+|  Standby      |  8.63				  | 0.10      			 | HDD in Standby mode |
+|  Suspend      |  7.71				  | 0.08      			 | HDD in Standby mode |

 !!! note
    * Nominal Input Voltage: 220V
    * HDD: 4x WD Red 2TB (WD20EFRX)
    * [I2C OLED screen](/i2c/) attached to the systems
-    * Variation of power consumption sometimes due to fluctuation of the input voltage

 ## Issues

@ -188,6 +201,6 @@ Therefore it is advised to always enable WOL (**sudo ethtool -s eth0 wol g**) be

 ### Thermal

-When system is put in suspend mode, the PWM feature controlling the fan speed is stopped. The fans will either spin at their lowest speed ([Batch 1 fan](/pwm/#old-fan-batch-1)) or stop spinning ([Batch 2 fan](/pwm/#new-fan-batch-2)). In the latest case, while this is not an issue for the SoC itself which is designed to run with passive cooling, it might have a negative impact on the HDD peripherals because the ambient temperature inside the case will rise.
+When system is put in suspend mode, the PWM feature controlling the fan speed is stopped. The fans will either spin at their lowest speed ([Batch 1 & 3 fan](/pwm/#type-a-fan-batch-1-3)) or stop spinning ([Batch 2 fan](/pwm/#type-c-fan-batch-2)). In the latest case, while it is not an issue for the SoC itself which is designed to run with passive cooling, it might have a negative impact on the HDD peripherals because the ambient temperature inside the case will rise.

-Therefore it is advised to ensure that when system is suspended the case ambient temperature will not exceed the operating temperature your HDDs are rated for.
+**Therefore it is advised to ensure that when system is suspended the case ambient temperature will not exceed the operating temperature your HDDs are rated for.**
--- a/mkdocs.yml
+++ b/mkdocs.yml
@ -41,7 +41,7 @@ extra:
    - type: 'rss-square'
      link: 'https://blog.kobol.io'
  sd_release:
-    latest: '10/02/2019'
+    latest: '14/03/2019'

 # Google Analytics
 google_analytics:
@ -70,14 +70,15 @@ pages:
 - Download: 'download.md'
 - Install: 'install.md'
 - O/S:
+  - Arch Linux : 'arch.md'
  - Armbian : 'armbian.md'
  - FreeBSD : 'freebsd.md'
+  - Syncloud : 'syncloud.md'
  - U-Boot (bootloader) : 'uboot.md'
 - Software:
  - Mdadm (RAID) : 'mdadm.md'
  - NextCloud : 'nextcloud.md'
  - OpenMediaVault : 'omv.md'
-  - Syncloud : 'syncloud.md'
 - Hardware:
  - Overview : 'hardware.md'
  - CESA (HW Crypto) : 'cesa.md'