desktop mainline kernel 4.17.y
mainline kernel 4.17.y
desktop legacy kernel 3.16.y
legacy kernel 3.16.y
- Comprehensive device information and various tips&tricks can be found in Hardkernel’s wiki. Please be aware that some of the information does not apply to Armbian (eg. we use a different partition table). Schematics can be found here.
- Idle consumption with a legacy image in headless mode (
setenv nographics "1"defined in
/boot/boot.ini) and only Gigabit Ethernet connection is between ~2300 mW (@500 MHz) and ~2400 mW (@1536 MHz). Hardkernel provides the possibility to exceed 1536 MHz max cpufreq but Armbian refrains from doing so. In case you want to change settings please keep in mind that you might have to adjust both
- The legacy kernel we use implements a few different cpufreq governors that show partially strange behavior (
interactivemost of the times acting like
performancefor example). Since idle consumption differences between different cpufreq governors are negligible choosing even
performanceseems to be ok. At least
conservativegovernor that switches between upper and lower clock speeds (for details see here) leads to some USB performance drops while not providing significant savings. In case you activate higher clock speeds please keep in mind that switching then to
performancegovernor is needed since otherwise, you might end up with a slower system since the added cpufreq operating points will slow down switching to highest clock speed when needed.
- If you don’t need GbE network transfer speeds switching to Fast Ethernet with
ethtool -s eth0 speed 100 duplex fullsaves ~230 mW. Completely disabling Ethernet saves an additional 100mW.
- GbE Ethernet speed should reach 935 Mbits/sec in TX direction. In RX direction with defaults you should get 800 Mbits/sec but with some tuning, it should be able to exceed 900 Mbits/sec:
- echo 32768 > /proc/sys/net/core/rps_sock_flow_entries
- echo 32768 > /sys/class/net/eth0/queues/rx-0/rps_flow_cnt
- You can save at least 170mW by cutting power to the internal USB hub (and also all USB devices connected to any of the type A receptacles) using
/sys/class/gpio/gpio126(see description here). The same way you have full control over power consumption of a connected host powered USB disk:
umount /mnt/usb && echo 0 >/sys/class/gpio/gpio126/valueand
echo 1 >/sys/class/gpio/gpio126/value && sleep 2 && mount /mnt/usb
- Reducing DRAM clock speed to reduce consumption doesn’t work (a difference between default 912 MHz and 408 MHz is just ~100mW less and also requires a reboot)
- the red led is a power led while the blue led is custom. Boot stage: as soon as u-boot is loaded the blue led lights solid and when the kernel starts this changes to
heartbeatblinking with default settings. Check
cat /sys/class/leds/*blue*/triggerfor other functionality.
* Specifications differ from hardware revision, model and software support level
We provide CLI (command line interface) images first. If the software is stable enough we add the option to upgrade to XFCE desktop. The Build-System relies on Debian and Ubuntu. The availability of different images may vary, most of the time because of driver restriction. Sometimes we provide only testing images.
All images can be built from sources at any time and in rare cases, where you can’t find an image which you need, you can build one.
Make sure you have a good & reliable SD card and a proper power supply. Archives can be uncompressed with 7-Zip on Windows, Keka on OS X and 7z on Linux (apt-get install p7zip-full). RAW images can be written with Etcher (all OS).
Insert the SD card into the slot, connect a cable to your network if possible or a display and power your board. (First) boot (with DHCP) takes up to 35 seconds with a class 10 SD Card.
Log in as: root Password: 1234. Then you are prompted to change this password (US-Keyboard setting). When done, you are asked to create a normal user-account for your everyday tasks.
SUPPORTED devices are tested and they work apart from known issues and missing features. Support is provided as far as possible (in general there is no support for 3rd party hardware like DVB tuners and software like Kodi). Please check the documentation and existing forum posts before posting a question.
SUITABLE FOR TESTING (WIP) are devices which we’re currently working on but they are not ready! These images are suitable for developers and experienced users. They are not very well tested but they might work without any problems. Your help to improve this situation is greatly appreciated.
SUPPORT ENDED (EOS) status are devices which used to be supported in the past. Reasons for moving to this section:
- no active software development (mainline u-boot and kernel)
- no support from the vendor (hardware samples, documentation, software packages)
- never was sold, only samples in small quantities were available
- hardware design flaws don’t allow using these devices without stability issues
- images are stable but we don’t test updating,
- images are provided with no support,
- most images have frozen kernel and u-boot packages to prevent their upgrades.
NO OFFICIAL SUPPORT (CSC) are devices which are supported by the 3rd party. We usually don’t have hardware samples nor conduct any tests but they might work. There is no support whatsoever.
Tested 3rd party hardware
USB2.0 / v4.0
USB3.0 / 1000Mbps
USB WiFi AC8811au
USB2.0 / 433Mbps
USB WiFi AC8812AU
USB3.0 / 876Mbps
USB WiFi AC8814AU
USB3.0 / 1300Mbps
USB WiFi AC8814AU
USB3.0 / 1300Mbps
USB2.0 / 150Mbps
USB2.0 / 150Mbps
USB WiFiRT3572 RT5572
USB2.0 / 300Mbps