You've already forked documentation
mirror of
https://github.com/armbian/documentation.git
synced 2026-01-06 10:13:36 -08:00
Issue #24: fixed some Armbian forum links.
This commit is contained in:
Rafa Couto
@@ -71,7 +71,7 @@ This is a typical board configuration:
|
||||
BOARDRATING=""
|
||||
CHIP="http://docs.armbian.com/Hardware_Allwinner-A20/"
|
||||
HARDWARE="https://linux-sunxi.org/Banana_Pi"
|
||||
FORUMS="http://forum.armbian.com/index.php/forum/7-allwinner-a10a20/"
|
||||
FORUMS="https://forum.armbian.com/forum/7-allwinner-a10a20/"
|
||||
BUY="http://amzn.to/2fToHjR"
|
||||
|
||||
If you want that our automated system start making images for this particular board, you need to alter parameters CLI_BETA_TARGET and DESKTOP_BETA_TARGET.
|
||||
|
||||
@@ -8,7 +8,7 @@ As usual [SoC](http://linux-sunxi.org/H3) and [device information](http://linux-
|
||||
|
||||
When CPU or GPU cores are fully utilized H3 tends to overheat over time like any other popular ARM SoC released within the last 2-3 years. With Armbian we provide sane dvfs (dynamic voltage frequency scaling) settings that help a lot with throttling. In case you plan to operate your H3 device constantly under high load please check Armbian forums first since boards behave differently (related to voltage regulation and PCB size and design -- some use copper layers to spread the heat away from the SoC). Also consider applying a heatsink to the SoC (a fan should not be necessary unless you want to do number crunching on your board and then you obviously chose the wrong device).
|
||||
|
||||
You find some [differentiation criteria regarding supported H3 devices as well as an overview/history of H3 software support in our forums](http://forum.armbian.com/index.php/topic/1351-h3-board-buyers-guide/) or use Jean-Luc's [nice comparison table](http://www.cnx-software.com/2016/06/08/allwinner-h3-boards-comparison-tables-with-orange-pi-banana-pi-m2-nanopi-p1-and-h3-olinuxino-nano-boards/#comments) (both slightly outdated since more H3 devices have been released in the meantime).
|
||||
You find some [differentiation criteria regarding supported H3 devices as well as an overview/history of H3 software support in our forums](https://forum.armbian.com/topic/1351-h3-board-buyers-guide/) or use Jean-Luc's [nice comparison table](http://www.cnx-software.com/2016/06/08/allwinner-h3-boards-comparison-tables-with-orange-pi-banana-pi-m2-nanopi-p1-and-h3-olinuxino-nano-boards/#comments) (both slightly outdated since more H3 devices have been released in the meantime).
|
||||
|
||||
**Kernel support**
|
||||
|
||||
@@ -27,7 +27,7 @@ Please don't expect most of these features to be available when we provide mainl
|
||||
|
||||
- An insufficient power supply is the root cause of many weird symptoms/problems. Never trust in ratings written on the PSU since they might be wrong, the PSU might be old/dying and cable/contact resistance adds to problems. In other words: Before you blame Armbian for strange behaviour please try at least one second power supply (this applies to both PSU and cable between PSU and board if this is separate -- especially USB cables really suck due to high resistance leading to severe voltage drops).
|
||||
- In case you experience instabilities check your SD card using `armbianmonitor -c $HOME` and think about installing [RPi-Monitor for H3](http://www.cnx-software.com/2016/03/17/rpi-monitor-is-a-web-based-remote-monitor-for-arm-development-boards-such-as-raspberry-pi-and-orange-pi/) to get an idea whether you suffer from overheating (`sudo armbianmonitor -r` will install everything needed).
|
||||
- Especially for desktop images the speed of your SD card matters. If possible try to use our _nand-sata-install_ script to move the rootfs away from SD card. The script also works with USB disks flawlessly ([some background information](http://forum.armbian.com/index.php/topic/793-moving-to-harddisk/)).
|
||||
- Especially for desktop images the speed of your SD card matters. If possible try to use our _nand-sata-install_ script to move the rootfs away from SD card. The script also works with USB disks flawlessly ([some background information](https://forum.armbian.com/topic/793-moving-to-harddisk/)).
|
||||
|
||||
**Tips and tricks (H3 specific / lowering consumption)**
|
||||
|
||||
@@ -41,9 +41,9 @@ Recent research showed that H3 boards operated as wired IoT nodes need way less
|
||||
|
||||
As an example: We chose default Armbian settings for NanoPi NEO to ensure this board is not able to exceed 2W consumption when running with no peripherals connected. This resulted in CPU and DRAM clockspeed of just 480/408 MHz while _booting_ (the first ~20 seconds). In normal operation we limit maximum CPU clockspeed to 912 MHz to stay below the 2W consumption barrier even in worst case scenarios.
|
||||
|
||||
In case you want to have a few more percent maximum CPU performance you would need to set maximum cpufreq to 1200 MHz instead of 'just' 912 MHz maximum CPU clock using our new [h3consumption tool](http://forum.armbian.com/index.php/topic/1878-testers-wanted-h3consumption-to-be-included-into-future-armbian-releases/). Be warned: this will both heavily increase consumption and SoC temperature since exceeding 912 MHz CPU clockspeed means feeding the SoC with 1.3V instead of 1.1V core voltage (most smaller H3 devices use a voltage regulator only switching between 2 voltages to feed the SoC based on load).
|
||||
In case you want to have a few more percent maximum CPU performance you would need to set maximum cpufreq to 1200 MHz instead of 'just' 912 MHz maximum CPU clock using our new [h3consumption tool](https://forum.armbian.com/topic/1878-testers-wanted-h3consumption-to-be-included-into-future-armbian-releases/). Be warned: this will both heavily increase consumption and SoC temperature since exceeding 912 MHz CPU clockspeed means feeding the SoC with 1.3V instead of 1.1V core voltage (most smaller H3 devices use a voltage regulator only switching between 2 voltages to feed the SoC based on load).
|
||||
|
||||
Walking this route in the other direction is more interesting: In case you want to use an H3 device as IoT node you might want to limit both idle and maximum consumption. That should involve disabling stuff not needed (eg. HDMI/GPU since this saves 200mW) or limiting ressource consumption: Lowering maximum clockspeeds for both CPU and DRAM or even disabling CPU cores (which helps _not_ with idle consumption since ARM cores enter low-power modes if not needed but can help lowering maximum consumption requirements).
|
||||
|
||||
Since all of this stuff is based on recent research and being still WiP please consider reading through relevant threads in Armbian forums **and** join development/research/discussions: [Running H3 boards with minimal consumption](http://forum.armbian.com/index.php/topic/1614-running-h3-boards-with-minimal-consumption/), [SBC consumption/performance comparisons](http://forum.armbian.com/index.php/topic/1748-sbc-consumptionperformance-comparisons/) and [Default settings for NanoPi NEO/Air](http://forum.armbian.com/index.php/topic/1728-rfc-default-settings-for-nanopi-neoair/).
|
||||
Since all of this stuff is based on recent research and being still WiP please consider reading through relevant threads in Armbian forums **and** join development/research/discussions: [Running H3 boards with minimal consumption](https://forum.armbian.com/topic/1614-running-h3-boards-with-minimal-consumption/), [SBC consumption/performance comparisons](https://forum.armbian.com/topic/1748-sbc-consumptionperformance-comparisons/) and [Default settings for NanoPi NEO/Air](https://forum.armbian.com/topic/1728-rfc-default-settings-for-nanopi-neoair/).
|
||||
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
System images with legacy kernel
|
||||
|
||||
- Kernel [3.14.x](https://github.com/linux4kix/linux-linaro-stable-mx6) with large hardware support, headers and some firmware included
|
||||
- [Docker ready](http://forum.armbian.com/index.php/topic/490-docker-on-armbian/) – [what is Docker](https://www.docker.com/what-docker)?
|
||||
- [Docker ready](https://forum.armbian.com/topic/490-docker-on-armbian/) – [what is Docker](https://www.docker.com/what-docker)?
|
||||
- PCI-E operational (Hummingboard Pro, Gate & Edge)
|
||||
- mSATA / m2 operational (Hummingboard Pro & Edge)
|
||||
- Enabled audio devices: HDMI, spdif, analogue
|
||||
@@ -63,7 +63,7 @@ LVDS](https://github.com/notro/fbtft/wiki)
|
||||
# Udoo Quad #
|
||||
|
||||
- [Kernel 3.14.x](https://github.com/UDOOboard/linux_kernel) and [4.4.x](https://github.com/patrykk/linux-udoo) with some hardware support, headers and some firmware included
|
||||
- [Docker ready](http://forum.armbian.com/index.php/topic/490-docker-on-armbian/) – [what is Docker](https://www.docker.com/what-docker)?
|
||||
- [Docker ready](https://forum.armbian.com/topic/490-docker-on-armbian/) – [what is Docker](https://www.docker.com/what-docker)?
|
||||
- Wireless adapter with DHCP ready but disabled (/etc/network/interfaces, WPA2: normal connect, bonding / notebook or AP mode). It can handle between 40-70Mbit/s.
|
||||
- SATA operational
|
||||
- Enabled analogue (VT1613) and HDMI audio device
|
||||
|
||||
@@ -19,7 +19,7 @@ Not all support issues are tasks, but a support issue can generate a task.
|
||||
1. Create issue in [Armbian GitHub Repo](https://github.com/igorpecovnik/lib/issues) under appropriate milestone
|
||||
- 
|
||||
1. Copy the numeric ID of issue created
|
||||
1. Create new topic under the Tasks subforum on the [Armbian Forums](http://forum.armbian.com/index.php/forum/15-tasks/)
|
||||
1. Create new topic under the Tasks subforum on the [Armbian Forums](https://forum.armbian.com/forum/15-tasks/)
|
||||
- Use the the naming convention of `[ISSUE_ID] - Issue Name`
|
||||
- 
|
||||
1. Copy the URL of task subforum topic just created
|
||||
|
||||
@@ -404,7 +404,7 @@ Build script:
|
||||
|
||||
**v5.34 / 18.10.2017**
|
||||
|
||||
- bugfix Odroid XU4/HC1 image rebuild [due to broken USB install on kernel 4.9.x](https://forum.armbian.com/index.php?/topic/5413-odroid-hc1-sata-install)
|
||||
- bugfix Odroid XU4/HC1 image rebuild [due to broken USB install on kernel 4.9.x](https://forum.armbian.com/topic/5413-odroid-hc1-sata-install)
|
||||
- added Le Potato and Orange Pi Zero testing image (mainline kernel)
|
||||
- Tinkerboard, MiQi and Pinebook images rebuilt
|
||||
|
||||
@@ -418,11 +418,11 @@ Build script:
|
||||
|
||||
**v5.32 / 23.06.2017**
|
||||
|
||||
- bugfix release [due to broken crypto functions on kernel 4.11.x](https://forum.armbian.com/index.php?/topic/4556-partial-bugfix-update/)
|
||||
- bugfix release [due to broken crypto functions on kernel 4.11.x](https://forum.armbian.com/topic/4556-partial-bugfix-update/)
|
||||
|
||||
**v5.31 / 15.06.2017**
|
||||
|
||||
- bugfix release [due to network failure](https://forum.armbian.com/index.php?/topic/4498-no-boot-after-upgrade-to-530/) on some A10 / A20 boards
|
||||
- bugfix release [due to network failure](https://forum.armbian.com/topic/4498-no-boot-after-upgrade-to-530/) on some A10 / A20 boards
|
||||
|
||||
**End of support notice**
|
||||
|
||||
@@ -635,7 +635,7 @@ Known problems:
|
||||
|
||||
Images:
|
||||
|
||||
- all 3.10+ kernels [are Docker ready](http://forum.armbian.com/index.php/topic/490-docker-on-armbian/)
|
||||
- all 3.10+ kernels [are Docker ready](https://forum.armbian.com/topic/490-docker-on-armbian/)
|
||||
- all A10/A20/H3 comes with HW accelerated video playback in desktop build
|
||||
- [fixed root exploit on H3 boards](https://github.com/igorpecovnik/lib/issues/282)
|
||||
- [fixed kswapd 100% bug on H3 boards](https://github.com/igorpecovnik/lib/issues/219)
|
||||
@@ -654,7 +654,7 @@ Images:
|
||||
- kernel for H3/sun8i legacy come from new Allwinner updated source (friendlyarm)
|
||||
- [added support for Olimex Lime2 eMMC](https://github.com/igorpecovnik/lib/issues/258)
|
||||
- [increased MALI clockspeed on sun8i/legacy](https://github.com/igorpecovnik/lib/issues/265)
|
||||
- added [Armbianmonitor](http://forum.armbian.com/index.php/topic/881-prepare-v51-v201604/?p=7095)
|
||||
- added [Armbianmonitor](https://forum.armbian.com/topic/881-prepare-v51-v201604/?p=7095)
|
||||
- added Odroid C1, C2(arm64), Nanopi M1, Banana M2+, Pcduino 2 and Pcduino 3. CLI and desktop
|
||||
- added wifi radar to desktop
|
||||
- added preview mainline kernel images for H3 boards (4.6.RC1)
|
||||
@@ -709,8 +709,8 @@ Known bugs:
|
||||
- Mali acceleration works for all users not only root
|
||||
- verbose boot logging on 1st boot and after crashes (you can toggle verbose logging using `sudo armbianmonitor -b`)
|
||||
- more WiFi dongles supported due to backported firmware loader patch
|
||||
- all 3 USB ports on Orange Pi One (Lite) available ([2 of them need soldering](http://forum.armbian.com/index.php/topic/755-tutorial-orange-pi-one-adding-usb-analog-audio-out-tv-out-mic-and-ir-receiver/))
|
||||
- I2S possible on all Orange Pis (compare with the [mini tutorial](http://forum.armbian.com/index.php/topic/759-tutorial-i2s-on-orange-pi-h3/) since you need to tweak script.bin)
|
||||
- all 3 USB ports on Orange Pi One (Lite) available ([2 of them need soldering](https://forum.armbian.com/topic/755-tutorial-orange-pi-one-adding-usb-analog-audio-out-tv-out-mic-and-ir-receiver/))
|
||||
- I2S possible on all Orange Pis (compare with the [mini tutorial](https://forum.armbian.com/topic/759-tutorial-i2s-on-orange-pi-h3/) since you need to tweak script.bin)
|
||||
- default display resolution set to 720p60 to fix possible overscan issues on 1st boot
|
||||
- HW accelerated video decoding works for most formats
|
||||
- Booting from eMMC on OPi Plus now possible
|
||||
@@ -721,7 +721,7 @@ Known bugs:
|
||||
- HDMI/DVI works (bug in boot.cmd settings)
|
||||
- Reboot issues fixed (bug in fex settings)
|
||||
- 1-Wire useable (we chose to stay compatible to loboris' images so the data pin is 37 by default. You're able to change this in the [fex file](https://github.com/igorpecovnik/lib/blob/6d995e31583e5361c758b401ea44634d406ac3da/config/orangepiplus.fex#L1284-L1286))
|
||||
- changing display resolution and choosing between HDMI and DVI is now possible with the included _h3disp_ tool (should also work in the [stand-alone version](http://forum.armbian.com/index.php/topic/617-wip-orange-pi-one-support-for-the-upcoming-orange-pi-one/?p=5480) with Debian based OS images from loboris/Xunlong). Use `sudo h3disp` in a terminal to get the idea.
|
||||
- changing display resolution and choosing between HDMI and DVI is now possible with the included _h3disp_ tool (should also work in the [stand-alone version](https://forum.armbian.com/topic/617-wip-orange-pi-one-support-for-the-upcoming-orange-pi-one/?p=5480) with Debian based OS images from loboris/Xunlong). Use `sudo h3disp` in a terminal to get the idea.
|
||||
- Ethernet issues fixed (combination of kernel and fex fixes)
|
||||
- USB-to-SATA bridge on the Orange Pi Plus works
|
||||
- stability problems on Orange Pi One fixed (due to undervoltage based on wrong fex settings)
|
||||
@@ -746,7 +746,7 @@ Known bugs:
|
||||
|
||||
**v5.01 / 17.2.2016**
|
||||
|
||||
- Bugfix update for [Allwinner boards](http://forum.armbian.com/index.php/topic/691-banana-pro-testers-wanted-sata-drive-not-working-on-some-boards/)
|
||||
- Bugfix update for [Allwinner boards](https://forum.armbian.com/topic/691-banana-pro-testers-wanted-sata-drive-not-working-on-some-boards/)
|
||||
- Update [for H3 based boards](https://github.com/igorpecovnik/lib/commit/c93d7dfb3538c36739fb8841bd314d75e7d7cbe5)
|
||||
|
||||
**v5.00 / 12.2.2016**
|
||||
@@ -756,7 +756,7 @@ Known bugs:
|
||||
- added Marvel Armada kernel 3.10.96, 4.4.1 and patches for changing mPCI to SATA
|
||||
- added Cubox / Hummingboard kernel 4.4.1 (serial console only)
|
||||
- firstrun does autoreboot only if needed: wheezy and some legacy kernels.
|
||||
- [added motd](http://forum.armbian.com/index.php/topic/602-new-motd-for-ubuntudebian/#entry4223) to /etc/updated.motd ... redesign, added battery info for Allwinner boards, bugfix, coloring
|
||||
- [added motd](https://forum.armbian.com/topic/602-new-motd-for-ubuntudebian/#entry4223) to /etc/updated.motd ... redesign, added battery info for Allwinner boards, bugfix, coloring
|
||||
- fixed temperature reading on Cubox / Hummingboard legacy kernel
|
||||
- fixed FB turbo building on Allwinner
|
||||
- fixed NAND install on A10 boards (Legacy kernel only)
|
||||
|
||||
@@ -49,7 +49,7 @@ Than mount the SD card and download those files (This example is only for Banana
|
||||
http://apt.armbian.com/pool/main/l/linux-upstream/linux-dtb-next-sunxi_4.5_armhf.deb
|
||||
|
||||
|
||||
This is just an example for: **Ubuntu Trusty, Lamobo R1, mainline kernel** (next). Alter packages naming according to [this](http://forum.armbian.com/index.php/topic/211-kernel-update-procedure-has-been-changed/).
|
||||
This is just an example for: **Ubuntu Trusty, Lamobo R1, mainline kernel** (next). Alter packages naming according to [this](https://forum.armbian.com/topic/211-kernel-update-procedure-has-been-changed/).
|
||||
|
||||
Mount SD card and extract all those deb files to it's mount point.
|
||||
|
||||
@@ -143,7 +143,7 @@ Test if Docker works correctly:
|
||||
|
||||
... and point the browser of any device in the same network to `http://<IP OF YOUR DEVICE>/`
|
||||
|
||||
[More info in this forum topic](http://forum.armbian.com/index.php/topic/490-docker-on-armbian/)
|
||||
[More info in this forum topic](https://forum.armbian.com/topic/490-docker-on-armbian/)
|
||||
|
||||
# How to set wireless access point?
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@ Both kernels, where exists, are stable and production ready, but you should use
|
||||
- unstested,
|
||||
- for experienced users only.
|
||||
|
||||
Don’t use them for anything productive but to give constructive [feedback to developers](https://forum.armbian.com/index.php?/forum/4-development/).
|
||||
Don’t use them for anything productive but to give constructive [feedback to developers](https://forum.armbian.com/forum/4-development/).
|
||||
|
||||
# How to check download authenticity?
|
||||
|
||||
@@ -79,7 +79,7 @@ At the time of this writing A1 and A2 cards are only widely available from SanDi
|
||||
|
||||
  
|
||||
|
||||
In case you chose an SD card that was already in use before please consider resetting it back to 'factory default' performance with [SD Formatter](https://www.sdcard.org/downloads/formatter_4/) before burning Armbian to it ([explanation in the forum](https://forum.armbian.com/index.php?/topic/3776-the-partition-is-not-resized-to-full-sd-card-size/&do=findComment&comment=27413)). Detailed information regarding ['factory default' SD card performance](https://forum.armbian.com/topic/954-sd-card-performance/?page=3&tab=comments#comment-49811).
|
||||
In case you chose an SD card that was already in use before please consider resetting it back to 'factory default' performance with [SD Formatter](https://www.sdcard.org/downloads/formatter_4/) before burning Armbian to it ([explanation in the forum](https://forum.armbian.com/topic/3776-the-partition-is-not-resized-to-full-sd-card-size/&do=findComment&comment=27413)). Detailed information regarding ['factory default' SD card performance](https://forum.armbian.com/topic/954-sd-card-performance/?page=3&tab=comments#comment-49811).
|
||||
|
||||
# How to boot?
|
||||
|
||||
@@ -150,7 +150,7 @@ and you can choose the following file system options:
|
||||
* ext2,3,4
|
||||
* btrfs
|
||||
|
||||
On Allwinner devices after switching to boot from NAND or eMMC clearing the boot loader signature on the SD card is recommended: `dd if=/dev/zero of=/dev/mmcblkN bs=1024 seek=8 count=1` (replace `/dev/mmcblkN` with the correct device node -- in case you run this directly after `nand-sata-install` without a reboot in between then it's `/dev/mmcblk0`). When booting from eMMC to get SD cards auto-detected on Allwinner legacy images please consider changing `mmc0`'s `sdc_detmode` from 3 to 1 in the board's fex file (see [here](http://forum.armbian.com/index.php/topic/1702-orange-pi-plus-2e-where-is-16ghz-and-sd/?p=13163) for details).
|
||||
On Allwinner devices after switching to boot from NAND or eMMC clearing the boot loader signature on the SD card is recommended: `dd if=/dev/zero of=/dev/mmcblkN bs=1024 seek=8 count=1` (replace `/dev/mmcblkN` with the correct device node -- in case you run this directly after `nand-sata-install` without a reboot in between then it's `/dev/mmcblk0`). When booting from eMMC to get SD cards auto-detected on Allwinner legacy images please consider changing `mmc0`'s `sdc_detmode` from 3 to 1 in the board's fex file (see [here](https://forum.armbian.com/topic/1702-orange-pi-plus-2e-where-is-16ghz-and-sd/?p=13163) for details).
|
||||
|
||||
# How to connect to wireless?
|
||||
|
||||
|
||||
@@ -14,9 +14,9 @@ A lot of Bananian installations today run 24/7 for 3 years or even longer. While
|
||||
|
||||
### Hardware up to the task?
|
||||
|
||||
The vast majority of [boards Bananian runs on](https://www.bananian.org/hardware) is based on Allwinner's dual core A20 SoC which was a nice improvement over the first single-core Raspberry Pis few years ago but is pretty slow by today's standards. An awful lot of users (us Armbians **all** included) were excited by A20's 'native SATA' capabilities few years ago just to realize after purchase when using SATA attached storage that it's awfully slow and most probably the slowest 'native' SATA implementation existing (please wake up if in doubt and educate yourself [here](https://forum.armbian.com/index.php?/topic/1925-some-storage-benchmarks-on-sbcs/&do=findComment&comment=34192), [here](http://linux-sunxi.org/Sunxi_devices_as_NAS#Influence_of_the_chosen_OS_image_on_NAS_performance) or [here](https://forum.openmediavault.org/index.php/Thread/19871-Which-energy-efficient-ARM-platform-to-choose/?postID=154980#post154980). Important: combining Allwinner's crappy SATA implementation with port multipliers [is always wrong](https://github.com/armbian/build/issues/548#issuecomment-332918004)).
|
||||
The vast majority of [boards Bananian runs on](https://www.bananian.org/hardware) is based on Allwinner's dual core A20 SoC which was a nice improvement over the first single-core Raspberry Pis few years ago but is pretty slow by today's standards. An awful lot of users (us Armbians **all** included) were excited by A20's 'native SATA' capabilities few years ago just to realize after purchase when using SATA attached storage that it's awfully slow and most probably the slowest 'native' SATA implementation existing (please wake up if in doubt and educate yourself [here](https://forum.armbian.com/topic/1925-some-storage-benchmarks-on-sbcs/&do=findComment&comment=34192), [here](http://linux-sunxi.org/Sunxi_devices_as_NAS#Influence_of_the_chosen_OS_image_on_NAS_performance) or [here](https://forum.openmediavault.org/index.php/Thread/19871-Which-energy-efficient-ARM-platform-to-choose/?postID=154980#post154980). Important: combining Allwinner's crappy SATA implementation with port multipliers [is always wrong](https://github.com/armbian/build/issues/548#issuecomment-332918004)).
|
||||
|
||||
At the time of this writing (Oct 2017) Armbian supports +25 other ARM boards that show between 2 and 6 times better CPU performance than A20 devices. +20 boards we support show better network performance (A20 Gigabit Ethernet is not fully capable of 940 Mbits/sec in both directions). +15 boards support 2GB DRAM (a few even more just recently). And if you don't need Gigabit Ethernet you can get a new and fully supported board still better suited for light-weight server tasks than any Banana Pi for as less as $11 shipping included (check [this overview](https://forum.armbian.com/index.php?/topic/1351-h3-board-buyers-guide/&do=findComment&comment=28169) please).
|
||||
At the time of this writing (Oct 2017) Armbian supports +25 other ARM boards that show between 2 and 6 times better CPU performance than A20 devices. +20 boards we support show better network performance (A20 Gigabit Ethernet is not fully capable of 940 Mbits/sec in both directions). +15 boards support 2GB DRAM (a few even more just recently). And if you don't need Gigabit Ethernet you can get a new and fully supported board still better suited for light-weight server tasks than any Banana Pi for as less as $11 shipping included (check [this overview](https://forum.armbian.com/topic/1351-h3-board-buyers-guide/&do=findComment&comment=28169) please).
|
||||
|
||||
While this diversity of ARM species might be confusing the good news is: When Armbian is running on them they all behave the same.
|
||||
|
||||
@@ -24,7 +24,7 @@ While this diversity of ARM species might be confusing the good news is: When Ar
|
||||
|
||||
### Continue on same hardware but prevent SD card hassles
|
||||
|
||||
Especially if you run since years off the same SD card please be prepared that it might not survive an `apt-get dist-upgrade` and similar upgrade/crossgrade tasks. It's **strongly** recommended to clone/backup your card prior to every necessary upgrade step. Since this is time consuming and just a measure to prepare for what will happen in the future anyway (your SD card failing eventually -- if you're lucky immediately, if you're out of luck it will corrupt a lot of data dying slowly) a great idea is to buy a new one **now**. Please see [our community's collection of SD card performance tests](https://forum.armbian.com/index.php?/topic/954-sd-card-performance/) and especially the 3 links at the top dealing with reliability concerns.
|
||||
Especially if you run since years off the same SD card please be prepared that it might not survive an `apt-get dist-upgrade` and similar upgrade/crossgrade tasks. It's **strongly** recommended to clone/backup your card prior to every necessary upgrade step. Since this is time consuming and just a measure to prepare for what will happen in the future anyway (your SD card failing eventually -- if you're lucky immediately, if you're out of luck it will corrupt a lot of data dying slowly) a great idea is to buy a new one **now**. Please see [our community's collection of SD card performance tests](https://forum.armbian.com/topic/954-sd-card-performance/) and especially the 3 links at the top dealing with reliability concerns.
|
||||
|
||||
Once you bought a new, fast and hopefully reliable SD card, you should [test it according to our documentation](https://docs.armbian.com/User-Guide_Getting-Started/#how-to-prepare-a-sd-card), then burn a fresh Armbian image on it and manually transfer data and settings from your Bananian installation. This way you preserve your current settings/data on the old Bananian SD card saving you also a lot of time/efforts to clone/backup stuff.
|
||||
|
||||
@@ -32,9 +32,9 @@ Once you bought a new, fast and hopefully reliable SD card, you should [test it
|
||||
|
||||
### Replacing the hardware
|
||||
|
||||
If your Bananian installation runs since years better think about evaluating new hardware now. As explained above A20's SATA implementation is [awfully slow](https://forum.armbian.com/index.php?/topic/1925-some-storage-benchmarks-on-sbcs/&do=findComment&comment=34192) compared to good SATA implementations (Espressobin, Clearfog, Helios4) or even recent USB3 solutions, also Banana Pis can not saturate Gigabit Ethernet. It's almost 2018 now and we can choose from a variety of energy efficient boards more suited for the job.
|
||||
If your Bananian installation runs since years better think about evaluating new hardware now. As explained above A20's SATA implementation is [awfully slow](https://forum.armbian.com/topic/1925-some-storage-benchmarks-on-sbcs/&do=findComment&comment=34192) compared to good SATA implementations (Espressobin, Clearfog, Helios4) or even recent USB3 solutions, also Banana Pis can not saturate Gigabit Ethernet. It's almost 2018 now and we can choose from a variety of energy efficient boards more suited for the job.
|
||||
|
||||
[My](https://forum.armbian.com/index.php?/profile/7-tkaiser/) personal strategy was turning the various A20 servers into backup devices now receiving btrfs snapshots from better suited ARM servers in the meantime. New installation on new board, carefully migrating settings from Bananas, Cubietrucks or Lime boards to new server, testing, testing, testing, new installation on A20 device, setting up btrfs send|receive, testing, testing, testing, done.
|
||||
[My](https://forum.armbian.com/profile/7-tkaiser/) personal strategy was turning the various A20 servers into backup devices now receiving btrfs snapshots from better suited ARM servers in the meantime. New installation on new board, carefully migrating settings from Bananas, Cubietrucks or Lime boards to new server, testing, testing, testing, new installation on A20 device, setting up btrfs send|receive, testing, testing, testing, done.
|
||||
|
||||
## In-place migration tipps:
|
||||
|
||||
|
||||
@@ -13,4 +13,4 @@ To flash the image to eMMC:
|
||||
- Mount the eMMC partition and add a line `emmc_fix=on` to `/boot/armbianEnv.txt` file - this changes the DT during boot to switch from SD with card detect switch to a non-removable eMMC.
|
||||
- Unmount the eMMC partition and reboot
|
||||
|
||||
Please refer to [this](https://forum.armbian.com/index.php?/topic/3072-clearfog-pro-emmc-requires-sd-card-to-detect-device/) forum thread for the USB boot details and [this](http://forum.solid-run.com/linux-kernel-and-bootloaders-f34/unstable-mmc-operation-with-upstream-kernel-t2986.html) thread for a discussion of known eMMC issues.
|
||||
Please refer to [this](https://forum.armbian.com/topic/3072-clearfog-pro-emmc-requires-sd-card-to-detect-device/) forum thread for the USB boot details and [this](http://forum.solid-run.com/linux-kernel-and-bootloaders-f34/unstable-mmc-operation-with-upstream-kernel-t2986.html) thread for a discussion of known eMMC issues.
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
- a stripped down XU4 version dropping the internal USB hub, display and GPIO support but adding instead a great performing and UAS capable USB-to-SATA bridge (JMS578) directly to the PCB so no more cable/contact issues, no more underpowering and no more UAS hassles with some disk enclosures (that contain a broken SATA bridge or combine a working UAS capable chip with a branded/broken firmware)
|
||||
|
||||
from Review:
|
||||
> https://forum.armbian.com/index.php?/topic/4983-odroid-hc1/
|
||||
> https://forum.armbian.com/topic/4983-odroid-hc1/
|
||||
|
||||
1. Software support efforts needed for HC1 (or the other variants MC1 or HC2) are zero since Hardkernel kept everything 100% compatible to ODROID XU4
|
||||
1. HC1 is a very nice design addressing a few of XU3/XU4 former USB3 issues (mostly related to 'hardware' issues like cable/contact problems with USB3-A or underpowering)
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
- **Important**: A few Pine64+ devices suffer from a Gbit Ethernet issue related to the GbE PHY leading to a severe amount of packet losses which might render Ethernet unuseable. It's confirmed as [hardware issue](http://forum.pine64.org/showthread.php?tid=835&pid=19773#pid19773) and if you're affected or not can be simply checked by testing network throughput with *iperf3*. Against another GbE capable device you should exceed 900 Mbits/sec with Armbian (only 800 Mbits/sec in RX direction when not using Xenial due to [iperf3 being single-threaded in both directions then and bottlenecked by CPU](http://forum.armbian.com/index.php/topic/1917-armbian-running-on-pine64-and-other-a64h5-devices/?p=14673)). If you see low throughput and high retransmit counts then a work-around is to switch Pine64+ to Fast Ethernet only by adding `ethtool -s eth0 speed 100 duplex full` to `/etc/rc.local`. At the time of this writing a true fix is only replacing the defective board by Pine Microsystems Inc.
|
||||
- **Important**: A few Pine64+ devices suffer from a Gbit Ethernet issue related to the GbE PHY leading to a severe amount of packet losses which might render Ethernet unuseable. It's confirmed as [hardware issue](http://forum.pine64.org/showthread.php?tid=835&pid=19773#pid19773) and if you're affected or not can be simply checked by testing network throughput with *iperf3*. Against another GbE capable device you should exceed 900 Mbits/sec with Armbian (only 800 Mbits/sec in RX direction when not using Xenial due to [iperf3 being single-threaded in both directions then and bottlenecked by CPU](https://forum.armbian.com/topic/1917-armbian-running-on-pine64-and-other-a64h5-devices/?p=14673)). If you see low throughput and high retransmit counts then a work-around is to switch Pine64+ to Fast Ethernet only by adding `ethtool -s eth0 speed 100 duplex full` to `/etc/rc.local`. At the time of this writing a true fix is only replacing the defective board by Pine Microsystems Inc.
|
||||
- The only led on the board is a power led, it starts to light as soon as power is available and does not indicate anything else. So the only 'DOA or not?' indicator on this board is to burn an image, connect Ethernet, power on the board and wait 20 seconds whether the leds on the Ethernet jack show activity or not.
|
||||
- Comprehensive device information is available [in linux-sunxi wiki](http://linux-sunxi.org/Pine64).
|
||||
- Idle consumption with legacy image is ~1500 mW on Pine64 (or Pine64+ forced to use Fast Ethernet) and 1870 mW on Pine64+ (if you don't need GbE network transfer speeds switching to Fast Ethernet with `ethtool -s eth0 speed 100 duplex full` saves ~350 mW).
|
||||
@@ -8,7 +8,7 @@
|
||||
- If you use a DVI display don't forget to define `disp_dvi_compat=1` in `/boot/armbianEnv.txt` (supported starting with 5.21).
|
||||
- If you want to run heavy loads on Pine64 please keep in mind that you might need a heatsink to prevent throttling. Armbian uses community throttling settings that protect A64 SoC from overheating but without improved heat dissipation any heavy workload running longer than 60 seconds will result in CPU cores being clocked down to stay below 90°C SoC temperature.
|
||||
- Situation with mainline kernel can be considered experimental. At the moment only basic functionality is implemented and **no** thermal protection (throttling) is working (no cpufreq scaling also and no access to PMIC too). Therefore also pretty conservative settings are used which negatively impact performance.
|
||||
- In case you use mainline kernel already you can adjust cpufreq to 864 MHz for example by adding a line with `mw.l 0x1c20000 0x80001110` to `/boot/boot.cmd` (don't exceed 864 MHz now since [VDD_CPUX is currently limited to 1.1V](http://linux-sunxi.org/Pine64#CPU_clock_speed_limit)). By defining `mw.l 0x1c2005c 1` on a separate line you can speed up USB and Ethernet -- [Reference](http://forum.armbian.com/index.php/topic/1917-armbian-running-on-pine64-and-other-a64h5-devices/?p=15225)).
|
||||
- In case you use mainline kernel already you can adjust cpufreq to 864 MHz for example by adding a line with `mw.l 0x1c20000 0x80001110` to `/boot/boot.cmd` (don't exceed 864 MHz now since [VDD_CPUX is currently limited to 1.1V](http://linux-sunxi.org/Pine64#CPU_clock_speed_limit)). By defining `mw.l 0x1c2005c 1` on a separate line you can speed up USB and Ethernet -- [Reference](https://forum.armbian.com/topic/1917-armbian-running-on-pine64-and-other-a64h5-devices/?p=15225)).
|
||||
- It's possible to convert the upper USB port (normally an OTG port) into a full USB host port using an own PHY by setting some [magic bits](https://irclog.whitequark.org/linux-sunxi/2016-09-06#17478535;).
|
||||
- To use/configure Wi-Fi (currently only supported with legacy images) the most simple way is to use `NetworkManager`. Simply follow these steps (as root):
|
||||
- `echo "blacklist 8723bs_vq0" >/etc/modprobe.d/8723bs_vq0.conf` (optional, not really necessary)
|
||||
|
||||
@@ -1 +1 @@
|
||||
- Device has [different wireless chips](http://forum.armbian.com/index.php/topic/872-beelink-x2-with-armbian-possible) so wlan0 (WIFI connection) might not work out of the box.
|
||||
- Device has [different wireless chips](https://forum.armbian.com/topic/872-beelink-x2-with-armbian-possible) so wlan0 (WIFI connection) might not work out of the box.
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
- it's highly recommended to [power via header](https://forum.armbian.com/index.php?/topic/1095-miqi-is-a-35-single-board-computer-with-rockchip-rk3288/#comment-8338) with quality and powerful (3A) PSU - if you want stable operations and overclocking? In another words - don't even try to power via stock micro USB power connector since your board will suffer from regular crashing and might not even boot up.
|
||||
- it's highly recommended to [power via header](https://forum.armbian.com/topic/1095-miqi-is-a-35-single-board-computer-with-rockchip-rk3288/#comment-8338) with quality and powerful (3A) PSU - if you want stable operations and overclocking? In another words - don't even try to power via stock micro USB power connector since your board will suffer from regular crashing and might not even boot up.
|
||||
- to boot from SD card you need to press and hold a button on the back side of the board and power on. This erases bootloader on eMMC and now you can boot from SD. In case of troubles use [this tool to restore stock bootloader](https://github.com/mqmaker/miqi-prebuilt).
|
||||
- known issues: MALI and video acceleration libraries are not installed yet
|
||||
- overclocking to 2.2Ghz is possible with (patched) mainline kernel. Enable with:
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
- Severe powering troubles due to Micro USB power connector. It's recommended to [power through GPIO pins](https://forum.armbian.com/index.php?/topic/3327-asus-tinkerboard/&do=findComment&comment=32047) to prevent under-voltage issues (instabilities, boot/crash cycles).
|
||||
- Severe powering troubles due to Micro USB power connector. It's recommended to [power through GPIO pins](https://forum.armbian.com/topic/3327-asus-tinkerboard/&do=findComment&comment=32047) to prevent under-voltage issues (instabilities, boot/crash cycles).
|
||||
- Overclocking to 2.2GHz is possible with quality 3A PSU connected to GPIO pins and (patched) mainline kernel. Enable with:
|
||||
|
||||
echo 1 > /sys/devices/system/cpu/cpufreq/boost # enable turbo
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
|
||||
Based on a review from @tkaiser,
|
||||
|
||||
> https://forum.armbian.com/index.php?/topic/4983-odroid-hc1/
|
||||
> https://forum.armbian.com/topic/4983-odroid-hc1/
|
||||
|
||||
1. Use next kernel,
|
||||
1. don't think about USB3 issues any more (that's a XU4 problem),
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
**Legacy kernel images (all boards) ** (`default` branch)
|
||||
|
||||
- HDMI output (if exists) supports only limited number of predefined resolutions
|
||||
- TV Out is neither supported nor works as expected (only PAL/NTSC resolution, overscanning, no h3disp support, [notes for OPi Zero](https://forum.armbian.com/index.php?/topic/3837-psa-orange-pi-zero-expansion-board-tv-out-not-working-solution/))
|
||||
- 1-Wire protocol, reading out DHT11/DHT22 sensors or [S/PDIF](https://forum.armbian.com/index.php?/topic/1891-spdif-output-on-nanopi-m1/) requires setting the minimum CPU frequency to 480MHz or higher
|
||||
- TV Out is neither supported nor works as expected (only PAL/NTSC resolution, overscanning, no h3disp support, [notes for OPi Zero](https://forum.armbian.com/topic/3837-psa-orange-pi-zero-expansion-board-tv-out-not-working-solution/))
|
||||
- 1-Wire protocol, reading out DHT11/DHT22 sensors or [S/PDIF](https://forum.armbian.com/topic/1891-spdif-output-on-nanopi-m1/) requires setting the minimum CPU frequency to 480MHz or higher
|
||||
- Hardware accelerated video decoding supports only limited number of video formats
|
||||
- 'Out of memory' (OOM) issues are possible due to a kernel bug
|
||||
|
||||
@@ -15,4 +15,4 @@
|
||||
**Board: Orange Pi Zero and NanoPi Duo **
|
||||
|
||||
- Onboard wireless module (XR819) has poor software support so wireless connection issues are expected
|
||||
- Orange Pi Zero rev 1.4 reports [false high CPU temperatures](https://forum.armbian.com/index.php?/topic/4313-new-opi-zero-yet-another-high-temperature-issue).
|
||||
- Orange Pi Zero rev 1.4 reports [false high CPU temperatures](https://forum.armbian.com/topic/4313-new-opi-zero-yet-another-high-temperature-issue).
|
||||
|
||||
Reference in New Issue
Block a user