You've already forked documentation
mirror of
https://github.com/armbian/documentation.git
synced 2026-01-06 10:13:36 -08:00
Change (almost) all http: to https: throughout docs
There were a few small hobbyist/user sites (sharing pastes), also http://cubieboard.org that I tested and would not work with httpS, so I left those alone. Also any apt repositories or archives. I did not necessarily test every single link (would have taken all day), however if it appeared to be to a "reasonably large" website (i.e., WikiPedia, Armbian, Odroid, linux-sunxi, etc.) then I assumed they should be able to manage httpS.
This commit is contained in:
TRS-80
@@ -36,7 +36,7 @@ Run the script
|
||||
|
||||
Make sure that full path to the build script **does not contain spaces**.
|
||||
|
||||
|
||||
|
||||
|
||||
## Providing build configuration
|
||||
|
||||
@@ -89,10 +89,10 @@ This is a typical board configuration:
|
||||
DESKTOP_BETA_TARGET=""
|
||||
#
|
||||
BOARDRATING=""
|
||||
CHIP="http://docs.armbian.com/Hardware_Allwinner-A20/"
|
||||
CHIP="https://docs.armbian.com/Hardware_Allwinner-A20/"
|
||||
HARDWARE="https://linux-sunxi.org/Banana_Pi"
|
||||
FORUMS="https://forum.armbian.com/forum/7-allwinner-a10a20/"
|
||||
BUY="http://amzn.to/2fToHjR"
|
||||
BUY="https://amzn.to/2fToHjR"
|
||||
```
|
||||
|
||||
You can find more information about those variables [here](https://github.com/armbian/build/blob/master/config/boards/README.md).
|
||||
|
||||
@@ -11,23 +11,23 @@ Both *legacy* and *current* kernels are stable and production ready and mostly s
|
||||
- Enabled audio devices: analog, 8 channel HDMI, spdif and I2S (if wired and enabled in HW configuration)
|
||||
- Bluetooth ready (working with supported external keys)
|
||||
- [Enabled overlayfs](User-Guide_Advanced-Features/#how-to-freeze-your-filesystem)
|
||||
- [I2C](http://en.wikipedia.org/wiki/I%C2%B2C) ready and tested with small 16×2 LCD. Basic i2c tools included.
|
||||
- [I2C](https://en.wikipedia.org/wiki/I%C2%B2C) ready and tested with small 16×2 LCD. Basic i2c tools included.
|
||||
- SPI ready and tested with ILI9341 based 2.4″ TFT LCD display.
|
||||
- [Drivers for small TFT LCD](https://github.com/notro/fbtft) display modules.
|
||||
- [Clustering / stacking](http://en.wikipedia.org/wiki/Cluster_(computing))
|
||||
- [Clustering / stacking](https://en.wikipedia.org/wiki/Cluster_(computing))
|
||||
- Onboard LED attached to SD card activity (script.bin)
|
||||
- [Docker ready](User-Guide_Advanced-Features/#how-to-run-docker)
|
||||
- Enabled audio devices: analog, SPDIF (if available) & USB
|
||||
- [USB / UAS](http://linux-sunxi.org/USB/UAS) – more efficient disk access over USB (A20 and H3)
|
||||
- [USB / UAS](https://linux-sunxi.org/USB/UAS) – more efficient disk access over USB (A20 and H3)
|
||||
- [CAN bus](https://en.wikipedia.org/wiki/CAN_bus) – Controller Area Network
|
||||
- [USB OTG connector](http://linux-sunxi.org/USB_Gadget) – OTG or host mode
|
||||
- [USB OTG connector](https://linux-sunxi.org/USB_Gadget) – OTG or host mode
|
||||
- Bluetooth ready (working with supported external keys)
|
||||
- [I2C](http://en.wikipedia.org/wiki/I%C2%B2C) ready and tested with small 16×2 LCD. Basic i2c tools included.
|
||||
- [I2C](https://en.wikipedia.org/wiki/I%C2%B2C) ready and tested with small 16×2 LCD. Basic i2c tools included.
|
||||
- Onboard LED attached to SD card activity (not enabled on all boards yet)
|
||||
|
||||
### Bugs or limitation
|
||||
|
||||
- NAND install sometime fails. Workaround: install [Lubuntu to NAND](http://dl.cubieboard.org/software/a20-cubietruck/lubuntu/) with [Phoenix tools](http://docs.cubieboard.org/downloads) and run install again.
|
||||
- NAND install sometime fails. Workaround: install [Lubuntu to NAND](https://dl.cubieboard.org/software/a20-cubietruck/lubuntu/) with [Phoenix tools](http://docs.cubieboard.org/downloads) and run install again.
|
||||
- Shutdown results into reboot under certain conditions.
|
||||
- SATA port multiplier support is disabled by default, can be enabled by adding kernel parameter `ahci_sunxi.enable_pmp=1`
|
||||
- Screen output from kernel is set to HDMI by default. Boot loader can detect and switch, kernel not.
|
||||
@@ -35,7 +35,7 @@ Both *legacy* and *current* kernels are stable and production ready and mostly s
|
||||
|
||||
## Desktop
|
||||
|
||||
[](http://www.youtube.com/watch?v=hsthqj90vTU "Armbian Desktop")
|
||||
[](https://www.youtube.com/watch?v=hsthqj90vTU "Armbian Desktop")
|
||||
|
||||
- HW accelerated video playback (if available)
|
||||
- MALI Open GLES (if available)
|
||||
@@ -57,4 +57,4 @@ Since environment is reset after flashing u-boot, you need to do this after ever
|
||||
|
||||
## Resources
|
||||
|
||||
[Armbian packages repository](http://www.armbian.com/kernel/)
|
||||
[Armbian packages repository](https://www.armbian.com/kernel/)
|
||||
|
||||
@@ -2,13 +2,13 @@
|
||||
|
||||
## Overview
|
||||
|
||||
The H3 SoC from Allwinner is meant for OTT boxes and therefore its reference design is _not_ accompanied by a separate PMIC (power management IC) unlike _A series_ Allwinner SoCs (like A10, A20, A64, ...). No PMIC means also that there is no battery charging/monitoring implemented so H3 is not that much suited for mobile devices. On the other hand some pretty cheap H3 boards were released that can be driven with rather low consumption and therefore combining H3 devices with a battery became a real use case with boards like [Orange Pi One/Lite](http://linux-sunxi.org/Orange_Pi_Lite), NanoPi [NEO and Neo AIR](http://linux-sunxi.org/FriendlyARM_NanoPi_NEO).
|
||||
The H3 SoC from Allwinner is meant for OTT boxes and therefore its reference design is _not_ accompanied by a separate PMIC (power management IC) unlike _A series_ Allwinner SoCs (like A10, A20, A64, ...). No PMIC means also that there is no battery charging/monitoring implemented so H3 is not that much suited for mobile devices. On the other hand some pretty cheap H3 boards were released that can be driven with rather low consumption and therefore combining H3 devices with a battery became a real use case with boards like [Orange Pi One/Lite](https://linux-sunxi.org/Orange_Pi_Lite), NanoPi [NEO and Neo AIR](https://linux-sunxi.org/FriendlyARM_NanoPi_NEO).
|
||||
|
||||
As usual [SoC](http://linux-sunxi.org/H3) and [device information](http://linux-sunxi.org/Category:H3_Devices) can be found in Linux-sunxi wiki. Same applies to status of [mainlining kernel efforts](http://linux-sunxi.org/Linux_mainlining_effort). Adding to the usual SoC feature set (I2C, SPI, PWM, UART, SDIO, GPIO and so on) H3 has one USB OTG port, 3 real USB host ports (not exposed on all devices), Fast- and Gigabit Ethernet capablities (board specific), a Mali400MP2 GPU and Allwinner's video encoding/decoding engine.
|
||||
As usual [SoC](https://linux-sunxi.org/H3) and [device information](https://linux-sunxi.org/Category:H3_Devices) can be found in Linux-sunxi wiki. Same applies to status of [mainlining kernel efforts](https://linux-sunxi.org/Linux_mainlining_effort). Adding to the usual SoC feature set (I2C, SPI, PWM, UART, SDIO, GPIO and so on) H3 has one USB OTG port, 3 real USB host ports (not exposed on all devices), Fast- and Gigabit Ethernet capablities (board specific), a Mali400MP2 GPU and Allwinner's video encoding/decoding engine.
|
||||
|
||||
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](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).
|
||||
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](https://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
|
||||
|
||||
@@ -22,7 +22,7 @@ Almost all features of the H3 SoC are supported on Armbian's _current_ branch. P
|
||||
## Tips and tricks (general)
|
||||
|
||||
- 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).
|
||||
- In case you experience instabilities check your SD card using `armbianmonitor -c $HOME` and think about installing [RPi-Monitor for H3](https://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](https://forum.armbian.com/topic/793-moving-to-harddisk/)).
|
||||
|
||||
## Tips and tricks (H3 specific / lowering consumption) (outdated)
|
||||
|
||||
@@ -73,16 +73,16 @@ I tried three different display connection types: I2C, (4bit) parallel and SPI.
|
||||
|
||||
I2C
|
||||
|
||||
|
||||
|
||||
|
||||
I am using [this code](https://github.com/vvromanov/cb_i2c_lcd) for mainline kernel and with [changed line](https://github.com/vvromanov/cb_i2c_lcd/blob/master/i2c_lcd.c#L28): /dev/i2c-%u = /dev/i2c-2 for Legacy kernel.
|
||||
|
||||
SPI
|
||||
|
||||
|
||||
|
||||
|
||||
- I am using [2.4″ 240×320 SPI TFT LCD Serial Port Module+5/3.3V Pbc Adapter Micro SD ILI9341](http://www.google.com/search?q=2.4%E2%80%B3+240%C3%97320+SPI+TFT+LCD+Serial+Port+Module%2B5%2F3.3V+Pbc+Adapter+Micro+SD+ILI9341&oq=2.4%E2%80%B3+240%C3%97320+SPI+TFT+LCD+Serial+Port+Module%2B5%2F3.3V+Pbc+Adapter+Micro+SD+ILI9341)
|
||||
- Wire according to [this map](http://blog.riyas.org/2014/07/quickly-test-il9341-22-inch-22-spi-tft-raspbmc-fbtft.html).
|
||||
- I am using [2.4″ 240×320 SPI TFT LCD Serial Port Module+5/3.3V Pbc Adapter Micro SD ILI9341](https://www.google.com/search?q=2.4%E2%80%B3+240%C3%97320+SPI+TFT+LCD+Serial+Port+Module%2B5%2F3.3V+Pbc+Adapter+Micro+SD+ILI9341&oq=2.4%E2%80%B3+240%C3%97320+SPI+TFT+LCD+Serial+Port+Module%2B5%2F3.3V+Pbc+Adapter+Micro+SD+ILI9341)
|
||||
- Wire according to [this map](https://blog.riyas.org/2014/07/quickly-test-il9341-22-inch-22-spi-tft-raspbmc-fbtft.html).
|
||||
- You have to use Armbian 1.5 or newer. Currently working only under Legacy kernel.
|
||||
- Add this to your /etc/modules:
|
||||
`fbtft_device name=adafruit22a rotate=90 speed=48000000 fps=50 gpios=reset:25,led:19,dc:24`
|
||||
@@ -92,7 +92,7 @@ SPI
|
||||
- [Troubleshooting and settings for other displays
|
||||
LVDS](https://github.com/notro/fbtft/wiki)
|
||||
|
||||
|
||||
|
||||
|
||||
Currently working only under Legacy kernel.
|
||||
|
||||
|
||||
@@ -9,10 +9,10 @@ System images with legacy kernel
|
||||
- mSATA / m2 operational (Hummingboard Pro & Edge)
|
||||
- Enabled audio devices: HDMI, spdif, analogue
|
||||
- [Bluetooth ready](https://wiki.debian.org/BluetoothUser) (working with Cubox-i/HB PRO on-board device or external key)
|
||||
- [I2C](http://en.wikipedia.org/wiki/I%C2%B2C) ready and tested with small 16×2 LCD. Basic i2c tools included.
|
||||
- [I2C](https://en.wikipedia.org/wiki/I%C2%B2C) ready and tested with small 16×2 LCD. Basic i2c tools included.
|
||||
- SPI ready and tested with ILI9341 based 2.4″ TFT LCD display.
|
||||
- [Drivers for small TFT LCD](https://github.com/notro/fbtft) display modules.
|
||||
- [USB redirector](http://www.incentivespro.com/usb-server-usage.html) – for sharing USB over TCP/IP (disabled by default /etc/init.d/rc.usbsrvd)
|
||||
- [USB redirector](https://www.incentivespro.com/usb-server-usage.html) – for sharing USB over TCP/IP (disabled by default /etc/init.d/rc.usbsrvd)
|
||||
|
||||
### Bugs or limitation
|
||||
|
||||
@@ -21,7 +21,7 @@ System images with legacy kernel
|
||||
## Mainline
|
||||
System images with mainline kernel
|
||||
|
||||
- [Mainline](http://www.kernel.org/) with large hardware support, headers and some firmware included
|
||||
- [Mainline](https://www.kernel.org/) with large hardware support, headers and some firmware included
|
||||
- [Docker ready](User-Guide_Advanced-Features/#how-to-run-docker) – [what is Docker](https://www.docker.com/what-docker)?
|
||||
- PCI-E operational (Hummingboard Pro, Gate & Edge)
|
||||
- mSATA / m2 operational (Hummingboard Pro & Edge)
|
||||
@@ -42,10 +42,10 @@ System images with mainline kernel
|
||||
|
||||
I tried two different display connection types: I2C and SPI. Both are working perfectly with my image 2.6 or higher.
|
||||
|
||||
|
||||
|
||||
|
||||
- I am using [2.4″ 240×320 SPI TFT LCD Serial Port Module+5/3.3V Pbc Adapter Micro SD ILI9341](http://www.google.com/search?q=2.4%E2%80%B3+240%C3%97320+SPI+TFT+LCD+Serial+Port+Module%2B5%2F3.3V+Pbc+Adapter+Micro+SD+ILI9341&oq=2.4%E2%80%B3+240%C3%97320+SPI+TFT+LCD+Serial+Port+Module%2B5%2F3.3V+Pbc+Adapter+Micro+SD+ILI9341)
|
||||
- Wire according to [this map](http://blog.riyas.org/2014/07/quickly-test-il9341-22-inch-22-spi-tft-raspbmc-fbtft.html).
|
||||
- I am using [2.4″ 240×320 SPI TFT LCD Serial Port Module+5/3.3V Pbc Adapter Micro SD ILI9341](https://www.google.com/search?q=2.4%E2%80%B3+240%C3%97320+SPI+TFT+LCD+Serial+Port+Module%2B5%2F3.3V+Pbc+Adapter+Micro+SD+ILI9341&oq=2.4%E2%80%B3+240%C3%97320+SPI+TFT+LCD+Serial+Port+Module%2B5%2F3.3V+Pbc+Adapter+Micro+SD+ILI9341)
|
||||
- Wire according to [this map](https://blog.riyas.org/2014/07/quickly-test-il9341-22-inch-22-spi-tft-raspbmc-fbtft.html).
|
||||
- You have to use Armbian 1.5 or newer. Currently working only under Legacy kernel.
|
||||
- Add this to your /etc/modules:
|
||||
`fbtft_device name=adafruit22a rotate=90 speed=48000000 fps=50 gpios=reset:67,led:72,dc:195 busnum=1`
|
||||
@@ -57,7 +57,7 @@ LVDS](https://github.com/notro/fbtft/wiki)
|
||||
|
||||
## GPIO
|
||||
|
||||
[How to control HummingBoard GPIO from kernel space?](http://www.solid-run.com/community/topic2345.html)
|
||||
[How to control HummingBoard GPIO from kernel space?](https://www.solid-run.com/community/topic2345.html)
|
||||
|
||||
## Udoo Quad
|
||||
|
||||
|
||||
@@ -42,13 +42,13 @@ Both builds provide close to 100% hardware support, some slight differences are
|
||||
|
||||
#### Legacy/Current
|
||||
|
||||
- [Mainline kernel](http://www.kernel.org/) with large hardware support, headers and some firmware included
|
||||
- [Mainline kernel](https://www.kernel.org/) with large hardware support, headers and some firmware included
|
||||
- [Docker ready](User-Guide_Advanced-Features/#how-to-run-docker)
|
||||
- Both mPCIe are operational and [convertible to mSATA](#converting-mpcie-to-msata), M2 operational
|
||||
- Added patch to unlock Atheros regulatory restrictions which unlock 5Ghz AP mode in cheap Atheros cards (ath9 driver)
|
||||
- Bluetooth ready (working with supported external keys)
|
||||
- [I2C](http://en.wikipedia.org/wiki/I%C2%B2C) ready. Basic i2c tools included.
|
||||
- [SPI](http://en.wikipedia.org/wiki/Serial_Peripheral_Interface_Bus) ready but untested.
|
||||
- [I2C](https://en.wikipedia.org/wiki/I%C2%B2C) ready. Basic i2c tools included.
|
||||
- [SPI](https://en.wikipedia.org/wiki/Serial_Peripheral_Interface_Bus) ready but untested.
|
||||
- SFP is working at up to 1GB/s even with faster fiber modules
|
||||
- SFP DDMI is operational (`sudo ethtool -m eth2`)
|
||||
|
||||
|
||||
@@ -28,6 +28,6 @@ Armbian-config tool:
|
||||
|
||||
If you find our project useful, then we’d really appreciate it if you’d consider contributing to the project however you can. Donating is the easiest way to help us – you can use PayPal and Bitcoin or you can buy us something from our Amazon.de wish list.
|
||||
|
||||
[http://www.armbian.com/donate/](http://www.armbian.com/donate/)
|
||||
[https://www.armbian.com/donate/](https://www.armbian.com/donate/)
|
||||
|
||||
Thanks!
|
||||
|
||||
@@ -41,7 +41,7 @@ Tags are used in ad-hoc manner.
|
||||
| 21.02 | Urubu | January | planned
|
||||
| 21.05 | Jerboa | May | planned
|
||||
|
||||
by http://www.codenamegenerator.com/ from unusual animals
|
||||
by https://www.codenamegenerator.com/ from unusual animals
|
||||
|
||||
## Release Planning
|
||||
|
||||
@@ -121,7 +121,7 @@ A release starts as a RC Branch cut from master at freeze time. Once a RC Branc
|
||||
|
||||
### 1. Forum Communication
|
||||
|
||||
- Create a new thread in the [Armbian Build Framework Subforum](http://forum.armbian.com/forum/12-armbian-build-framework/)
|
||||
- Create a new thread in the [Armbian Build Framework Subforum](https://forum.armbian.com/forum/12-armbian-build-framework/)
|
||||
- Ex topic name: `Ambian 20.02 (Chiru) Release Thread`
|
||||
- Tag the post with relase, release version, and codename
|
||||
- Use the following template to begin the body of the release thread:
|
||||
@@ -136,8 +136,8 @@ Testing Tracking Sheet: https://example.com/link (google sheets)
|
||||
|
||||
The goal of this thread is to discuss testing, bugfixes, and the overall quality of the release. Once the release is complete, this thread should be locked and unpinned.
|
||||
```
|
||||
- Before Code Freeze -- Make note in the thread the incomplete jira issues tagged for the release [example](http://forum.armbian.com/topic/12763-armbian-2002-chiru-release-thread/?do=findComment&comment=93245)
|
||||
- After test images are procuded, engage in community for assistants wih testing.. forums, twitter, etc. [share this tool](http:///github.com/armbian/autotests)
|
||||
- Before Code Freeze -- Make note in the thread the incomplete jira issues tagged for the release [example](https://forum.armbian.com/topic/12763-armbian-2002-chiru-release-thread/?do=findComment&comment=93245)
|
||||
- After test images are procuded, engage in community for assistants wih testing.. forums, twitter, etc. [share this tool](https:///github.com/armbian/autotests)
|
||||
|
||||
### 2. Release Candidate Branch Management
|
||||
|
||||
|
||||
@@ -1200,7 +1200,7 @@ Known problems:
|
||||
|
||||
- fixed eMMC install on Odroid C2
|
||||
- firmware package was splitted into minimal (default) and full versions
|
||||
- patched [Dirty COW exploit](http://thehackernews.com/2016/10/linux-kernel-exploit.html) on all kernels
|
||||
- patched [Dirty COW exploit](https://thehackernews.com/2016/10/linux-kernel-exploit.html) on all kernels
|
||||
- added Odroid XU4 mainline kernel image
|
||||
- added Olimex A33 mainline kernel image
|
||||
- added Overlay FS for Cubox, Udoo and Udoo Neo
|
||||
@@ -1446,7 +1446,7 @@ Known bugs:
|
||||
**v5.00 / 12.2.2016**
|
||||
|
||||
- mainline kernel for Allwinner based boards upgraded to 4.4.1
|
||||
- Allwinner audio driver playback and capture on kernel 4.4.1, [UAS](http://linux-sunxi.org/USB/UAS), USB OTG, battery readings,
|
||||
- Allwinner audio driver playback and capture on kernel 4.4.1, [UAS](https://linux-sunxi.org/USB/UAS), USB OTG, battery readings,
|
||||
- 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.
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
|
||||
## How to switch kernels?
|
||||
|
||||
Check [_this_](http://www.armbian.com/kernel/) for more info.
|
||||
Check [_this_](https://www.armbian.com/kernel/) for more info.
|
||||
|
||||
## How to troubleshoot?
|
||||
## How to unbrick the system?
|
||||
@@ -133,7 +133,7 @@ Required conditions:
|
||||
- IR hardware
|
||||
- loaded driver
|
||||
|
||||
Get your [remote configuration](http://lirc.sourceforge.net/remotes/) (lircd.conf) or [learn](http://kodi.wiki/view/HOW-TO:Setup_Lirc#Learning_Commands). You are going to need the list of all possible commands which you can map to your IR remote keys:
|
||||
Get your [remote configuration](https://lirc.sourceforge.net/remotes/) (lircd.conf) or [learn](https://kodi.wiki/view/HOW-TO:Setup_Lirc#Learning_Commands). You are going to need the list of all possible commands which you can map to your IR remote keys:
|
||||
|
||||
irrecord --list-namespace
|
||||
|
||||
|
||||
@@ -64,12 +64,12 @@ Software installation menu provides automated install of the following packages.
|
||||
- [Transmission](https://transmissionbt.com/) *(torrent server)*
|
||||
- [ISPConfig](https://www.ispconfig.org/) *(WEB & MAIL server)*
|
||||
- [NCP](https://nextcloudpi.com) *(Nextcloud personal cloud)*
|
||||
- [Openmediavault NAS](http://www.openmediavault.org/) *(NAS server)*
|
||||
- [Openmediavault NAS](https://www.openmediavault.org/) *(NAS server)*
|
||||
- [PI hole](https://pi-hole.net) *(ad blocker)*
|
||||
- [UrBackup](https://www.urbackup.org/) *(client/server backup system)*
|
||||
- [Docker](https://www.docker.com) *(Docker CE engine)*
|
||||
- [Mayan EDMS](https://www.mayan-edms.com/) *(Document management system within Docker)*
|
||||
- [MiniDLNA](http://minidlna.sourceforge.net/) *(media sharing)*
|
||||
- [MiniDLNA](https://minidlna.sourceforge.net/) *(media sharing)*
|
||||
- **M**onitor = simple CLI monitoring
|
||||
- **D**iagnostics = create a summary of logs and upload them to paste.bin
|
||||
- **T**oggle kernel headers, RDP service, Thunderbird and Libreoffice (desktop builds)
|
||||
|
||||
@@ -88,11 +88,11 @@ This is useful when you need to fall back to previous kernel version.
|
||||
|
||||
apt install linux-image-sun8i=5.13
|
||||
|
||||
This example is for H3 legacy kernel. Check [this page](http://www.armbian.com/kernel/) for others.
|
||||
This example is for H3 legacy kernel. Check [this page](https://www.armbian.com/kernel/) for others.
|
||||
|
||||
## How to toggle boot output?
|
||||
|
||||
Edit and change [boot parameters](http://redsymbol.net/linux-kernel-boot-parameters/) in `/boot/boot.cmd` (not recommended) or variables in `/boot/armbianEnv.txt`:
|
||||
Edit and change [boot parameters](https://redsymbol.net/linux-kernel-boot-parameters/) in `/boot/boot.cmd` (not recommended) or variables in `/boot/armbianEnv.txt`:
|
||||
|
||||
- console=both
|
||||
+ console=serial
|
||||
@@ -119,7 +119,7 @@ Copy and past URL of your log to the forum, mail, ...
|
||||
|
||||
## How to change network configuration?
|
||||
|
||||
To get Wi-Fi working simply use `nmtui`, a simple console based UI for network-manager (an example how to set up an AP with network-manager can be found [here](http://forum.odroid.com/viewtopic.php?f=52&t=25472&)). To deal with different Ethernet/Wi-Fi combinations there are six predefined configurations available, you can find them in those files:
|
||||
To get Wi-Fi working simply use `nmtui`, a simple console based UI for network-manager (an example how to set up an AP with network-manager can be found [here](https://forum.odroid.com/viewtopic.php?f=52&t=25472&)). To deal with different Ethernet/Wi-Fi combinations there are six predefined configurations available, you can find them in those files:
|
||||
|
||||
/etc/network/interfaces.bonding
|
||||
/etc/network/interfaces.default
|
||||
|
||||
@@ -84,7 +84,7 @@ while on Linux/macOS, in the directory in which you have downloaded the files ,y
|
||||
|
||||
## How to prepare a SD card?
|
||||
|
||||
**Important note:** Make sure you use a **good, reliable and fast** SD card. If you encounter boot or stability troubles in over 95 percent of the time it is either insufficient power supply or related to SD card (bad card, bad card reader, something went wrong when burning the image, card too slow to boot -- 'Class 10' highly recommended!). Armbian can simply not run on unreliable hardware so checking your SD card with either [F3](http://oss.digirati.com.br/f3/) or [H2testw](http://www.heise.de/download/h2testw.html) is mandatory if you run in problems. Since [counterfeit SD cards](http://www.happybison.com/reviews/how-to-check-and-spot-fake-micro-sd-card-8/) are still an issue checking with F3/H2testw directly after purchase is **highly recommended**.
|
||||
**Important note:** Make sure you use a **good, reliable and fast** SD card. If you encounter boot or stability troubles in over 95 percent of the time it is either insufficient power supply or related to SD card (bad card, bad card reader, something went wrong when burning the image, card too slow to boot -- 'Class 10' highly recommended!). Armbian can simply not run on unreliable hardware so checking your SD card with either [F3](https://oss.digirati.com.br/f3/) or [H2testw](https://www.heise.de/download/h2testw.html) is mandatory if you run in problems. Since [counterfeit SD cards](https://www.happybison.com/reviews/how-to-check-and-spot-fake-micro-sd-card-8/) are still an issue checking with F3/H2testw directly after purchase is **highly recommended**.
|
||||
|
||||
Write the xz compressed image with [USBImager](https://gitlab.com/bztsrc/usbimager) or [Etcher](https://balena.io/etcher) on all platforms since unlike other tools, either can validate burning results **saving you from corrupted SD card contents**.
|
||||
|
||||
@@ -107,7 +107,7 @@ Insert SD card into a slot and power the board. (First) boot (with DHCP) takes u
|
||||
|
||||
## How to login?
|
||||
|
||||
Login as **root** on console (HDMI / serial) or via SSH and use password **1234**. You will be prompted to change this password at first login. You will then be asked to create a normal user account that is sudo enabled (beware of default QWERTY keyboard settings at this stage). Please use [this tool](http://angryip.org/), to find your board IP address.
|
||||
Login as **root** on console (HDMI / serial) or via SSH and use password **1234**. You will be prompted to change this password at first login. You will then be asked to create a normal user account that is sudo enabled (beware of default QWERTY keyboard settings at this stage). Please use [this tool](https://angryip.org/), to find your board IP address.
|
||||
|
||||
Desktop images start into desktop without asking for password. To change this add some display manager:
|
||||
|
||||
|
||||
@@ -16,7 +16,7 @@ A lot of Bananian installations today have been running 24/7 for 3 years or even
|
||||
|
||||
### 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/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](https://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/topic/1351-h3-board-buyers-guide/&do=findComment&comment=28169) please).
|
||||
|
||||
|
||||
@@ -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/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](https://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.
|
||||
|
||||
@@ -11,6 +11,6 @@
|
||||
setenv load_script 'if test -e mmc 0:1 boot/boot.scr; then echo \"... booting from SD\";setenv boot_interface mmc;else echo \"... booting from USB/SATA\";usb start;setenv boot_interface usb;fi;if test -e \$boot_interface 0:1 boot/boot.scr;then ext4load \$boot_interface 0:1 0x00800000 boot/boot.scr; source; fi'
|
||||
setenv bootcmd 'run get_images; run set_bootargs; run load_script;booti \$kernel_addr \$ramfs_addr \$fdt_addr'
|
||||
saveenv
|
||||
- If you manage to crash your SPI, proceed with [SATA boot recovery](http://wiki.espressobin.net/tiki-index.php?page=Boot+ESPRESSObin+from+SATA+drive).
|
||||
- If you manage to crash your SPI, proceed with [SATA boot recovery](https://wiki.espressobin.net/tiki-index.php?page=Boot+ESPRESSObin+from+SATA+drive).
|
||||
- booting directly from SATA is currently broken.
|
||||
- rebooting works with 4.14.y and SD media while it is broken with SATA and USB (always stops)
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
- Please note: From a software point of view ODROID C1, C1+ and C0 are (nearly) identical. For Hardware differences between C1 and C1+ and to see how to use USB OTG on the latter please see [here](http://odroid.com/dokuwiki/doku.php?id=en:c1_hardware#c1_has_below_improvements_from_the_original_c1). C0 is a stripped down and more power efficient C1+ that can be battery powered (see here [how to read out battery voltage](http://odroid.com/dokuwiki/doku.php?id=en:c0_read_battery_voltage))
|
||||
- Comprehensive device information and various tips&tricks can be found in [Hardkernel's wiki](http://odroid.com/dokuwiki/doku.php?id=en:odroid-c1). 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](http://dn.odroid.com/S805/Schematics/).
|
||||
- Please note: From a software point of view ODROID C1, C1+ and C0 are (nearly) identical. For Hardware differences between C1 and C1+ and to see how to use USB OTG on the latter please see [here](https://odroid.com/dokuwiki/doku.php?id=en:c1_hardware#c1_has_below_improvements_from_the_original_c1). C0 is a stripped down and more power efficient C1+ that can be battery powered (see here [how to read out battery voltage](https://odroid.com/dokuwiki/doku.php?id=en:c0_read_battery_voltage))
|
||||
- Comprehensive device information and various tips&tricks can be found in [Hardkernel's wiki](https://odroid.com/dokuwiki/doku.php?id=en:odroid-c1). 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](https://dn.odroid.com/S805/Schematics/).
|
||||
- Idle consumption of an ODROID-C1+ with Armbian defaults varies between 1800 mW (@504 MHz) and 1900 mW (@1728 MHz -- temperature also differs just by 2°C -- for reasons please refer to the ['race to idle' concept](https://en.wikipedia.org/wiki/Dynamic_frequency_scaling#Performance_impact).
|
||||
- By defining `setenv hdmioutput "0"` and `setenv vpu "0"` in `/boot/boot.ini` followed by a reboot you get true headless mode (no consumption savings but `MemTotal` increases from 804 MB to 941 MB -- check `/proc/meminfo` if in doubt)
|
||||
- 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/gpio4` (see description [here](http://forum.odroid.com/viewtopic.php?f=112&t=23763#p160852)). 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/gpio4/value` and `echo 1 >/sys/class/gpio/gpio4/value && sleep 2 && mount /mnt/usb`
|
||||
- Interestingly at least on C1+ consumption remains the same if you switch from Gbit to Fast Ethernet or disable Ethernet at all. It seems the GbE PHY is powered all the time (maybe related to [performance/stabiity problems on ODROID-C1 in early 2015](http://forum.odroid.com/viewtopic.php?f=115&t=8121))
|
||||
- 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/gpio4` (see description [here](https://forum.odroid.com/viewtopic.php?f=112&t=23763#p160852)). 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/gpio4/value` and `echo 1 >/sys/class/gpio/gpio4/value && sleep 2 && mount /mnt/usb`
|
||||
- Interestingly at least on C1+ consumption remains the same if you switch from Gbit to Fast Ethernet or disable Ethernet at all. It seems the GbE PHY is powered all the time (maybe related to [performance/stabiity problems on ODROID-C1 in early 2015](https://forum.odroid.com/viewtopic.php?f=115&t=8121))
|
||||
- Ethernet performance is ~940 Mbits/sec in TX direction and 400-500 Mbits/sec in RX direction. You might be able to tweak the latter a little, just have a look in the link one paragraph above.
|
||||
- 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 kernel starts this changes to `heartbeat` blinking with default settings. Check `cat /sys/class/leds/*blue*/trigger` for other functionality.
|
||||
- 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 kernel starts this changes to `heartbeat` blinking with default settings. Check `cat /sys/class/leds/*blue*/trigger` for other functionality.
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
- Comprehensive device information and various tips&tricks can be found in [Hardkernel's wiki](http://odroid.com/dokuwiki/doku.php?id=en:odroid-c2). 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](http://dn.odroid.com/S905/Schematic/).
|
||||
- Idle consumption with legacy image in headless mode (`setenv nographics "1"` defined in `/boot/boot.ini`) and only Gigabit Ethernet connected is between ~2300 mW (@500 MHz) and ~2400 mW (@1536 MHz). Hardkernel provides the possibility to [exceed 1536 MHz max cpufreq](http://odroid.com/dokuwiki/doku.php?id=en:c2_set_cpu_freq) but Armbian refrains from doing so. In case you want to change settings please keep in mind that you might have to adjust both `/boot/boot.ini` and `/etc/defaults/cpufrequtils`.
|
||||
- Comprehensive device information and various tips&tricks can be found in [Hardkernel's wiki](https://odroid.com/dokuwiki/doku.php?id=en:odroid-c2). 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](https://dn.odroid.com/S905/Schematic/).
|
||||
- Idle consumption with legacy image in headless mode (`setenv nographics "1"` defined in `/boot/boot.ini`) and only Gigabit Ethernet connected is between ~2300 mW (@500 MHz) and ~2400 mW (@1536 MHz). Hardkernel provides the possibility to [exceed 1536 MHz max cpufreq](https://odroid.com/dokuwiki/doku.php?id=en:c2_set_cpu_freq) but Armbian refrains from doing so. In case you want to change settings please keep in mind that you might have to adjust both `/boot/boot.ini` and `/etc/defaults/cpufrequtils`.
|
||||
- The legacy kernel we use implements a few different cpufreq governors that show partially strange behaviour (`interactive` most of the times acting like `performance` for example). Since idle consumption differences between different cpufreq governors are negligible choosing even `performance` seems to be ok. At least `conservative` governor that switches between upper and lower clockspeeds (for details see [here](https://github.com/igorpecovnik/lib/issues/499#issuecomment-253481174)) leads to some USB performance drops while not providing significant savings. In case you activate higher clockspeeds please keep in mind that switching then to `performance` governor is needed since otherwise you might end up with a slower system since the added cpufreq operating points will slow down switching to highest clockspeed when needed.
|
||||
- If you don't need GbE network transfer speeds switching to Fast Ethernet with `ethtool -s eth0 speed 100 duplex full` saves ~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](http://forum.odroid.com/viewtopic.php?t=22637&p=151969#p151982)). 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/value` and `echo 1 >/sys/class/gpio/gpio126/value && sleep 2 && mount /mnt/usb`
|
||||
- Reducing DRAM clockspeed to reduce consumption doesn't work (difference between default 912 MHz and 408 MHz is just ~100mW less and also [requires a reboot](http://odroid.com/dokuwiki/doku.php?id=en:c2_adjust_ddrclk))
|
||||
- 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 kernel starts this changes to `heartbeat` blinking with default settings. Check `cat /sys/class/leds/*blue*/trigger` for other functionality.
|
||||
- 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](https://forum.odroid.com/viewtopic.php?t=22637&p=151969#p151982)). 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/value` and `echo 1 >/sys/class/gpio/gpio126/value && sleep 2 && mount /mnt/usb`
|
||||
- Reducing DRAM clockspeed to reduce consumption doesn't work (difference between default 912 MHz and 408 MHz is just ~100mW less and also [requires a reboot](https://odroid.com/dokuwiki/doku.php?id=en:c2_adjust_ddrclk))
|
||||
- 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 kernel starts this changes to `heartbeat` blinking with default settings. Check `cat /sys/class/leds/*blue*/trigger` for other functionality.
|
||||
|
||||
@@ -1,14 +1,14 @@
|
||||
- **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.
|
||||
- **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](https://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).
|
||||
- Comprehensive device information is available [in linux-sunxi wiki](https://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).
|
||||
- Since the default DC-IN connector unfortunately is made with a Micro USB jack it's important to keep in mind that most USB cables have a resistance way too high which leads to undervoltage situations. In case you run into stability problems please power your Pine64(+) through the Euler pins (see [linux-sunxi wiki](http://linux-sunxi.org/File:Pine64_Powered_through_Euler_Connector.jpg) for details).
|
||||
- Since the default DC-IN connector unfortunately is made with a Micro USB jack it's important to keep in mind that most USB cables have a resistance way too high which leads to undervoltage situations. In case you run into stability problems please power your Pine64(+) through the Euler pins (see [linux-sunxi wiki](https://linux-sunxi.org/File:Pine64_Powered_through_Euler_Connector.jpg) for details).
|
||||
- If you clone one Armbian installation for more than one Pine64 please keep in mind that currently the Ethernet MAC address will be chosen randomly on first boot and then saved in `/boot/uEnv.txt`. To avoid MAC address collisions you must adjust the address there or delete the whole `ethaddr` line (next boot will [assign a new MAC address automagically](https://github.com/igorpecovnik/lib/blob/54070358c28d5e88f14305f2e8d179875e5b2e5e/scripts/firstrun#L411-L414)). OS images from Aug 2016 or before suffer from [this bug](https://github.com/longsleep/linux-pine64/commit/58636d53c21e1ee31e98bb971ebf95ebf44d6f2a) so `/boot/uEnv.txt` has to be adjusted manually in any case if more than one Pine64 joins the same Ethernet network.
|
||||
- Even if HDMI situation is still somewhat limited Armbian starting with release 5.21 supports setting the default resolution in `/boot/armbianEnv.txt` (defaults to `720p60` and could be changed to 4K@30Hz for example with an entry `disp_mode=2160p30` -- for the list of supported resolutions please have a look into `/boot/boot.cmd`)
|
||||
- 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](https://forum.armbian.com/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](https://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)
|
||||
@@ -16,7 +16,7 @@
|
||||
- `nmtui` (choose then *Activate a connection*)
|
||||
- You could also use the other Wi-Fi interface for an access point at the same time. In this case you want to use `wlan1` and follow [these instructions](https://help.ubuntu.com/community/WifiDocs/WirelessAccessPoint). Please note that Armbian already ships with an example default config `/etc/network/interfaces.hostapd` using `wlan0` and that we also ship with an own `hostapd` version (check with `dpkg -l | grep hostapd`).
|
||||
- Starting with [Armbian 5.21](https://github.com/igorpecovnik/lib/commit/04e6a4d76ad71a9f2117ae8b07c41617bfcb1eae) fixed camera drivers for both SK54EC and OV5640 are included.
|
||||
- Currently BT is not supported out of the box by Armbian. Please read through [this thread in pine64 forum](http://forum.pine64.org/showthread.php?tid=2248&pid=21412#pid21412) to enable it.
|
||||
- Currently BT is not supported out of the box by Armbian. Please read through [this thread in pine64 forum](https://forum.pine64.org/showthread.php?tid=2248&pid=21412#pid21412) to enable it.
|
||||
- Starting with Armbian 5.24 in `/boot/armbianEnv.txt` camera support can be activated: `camera_type=none|s5k4ec|ov5640` (defaults to `none`, reboot needed for changes to take effect)
|
||||
- Also starting with 5.24 Pine64's own LCD with touchscreen support can simply be activated in `/boot/armbianEnv.txt` by setting `pine64_lcd=on` and adding `gt9xxf_ts` to `/etc/modules` followed by a reboot. Please note that current `gt9xxf_ts` driver seems to be buggy and crashes on shutdown.
|
||||
- Starting with 5.25 in `/boot/armbianEnv.txt` two more parameters can be set: `gmac-tx-delay` (defaults to `3`) and `gmac-rx-delay` (defaults to `0`). Adjusting this parameters should not be necessary but in case you are curious or experience bad Gigabit Ethernet performance please read through [the appropriate github issue](https://github.com/igorpecovnik/lib/issues/546).
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
- total memory is 1000Mb (disabled all memory reservations for GPU on CLI images)
|
||||
- drivers for [LVDS LCD display modules](http://www.lenovator.com/7-inch-LCD) are added. TS module: ft5x_ts, added configuration for 7″ – [other sizes](https://github.com/LeMaker/fex_configuration/tree/master/fex).
|
||||
- drivers for [LVDS LCD display modules](https://www.lenovator.com/7-inch-LCD) are added. TS module: ft5x_ts, added configuration for 7″ – [other sizes](https://github.com/LeMaker/fex_configuration/tree/master/fex).
|
||||
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user