The official build framework for the Armbian Linux distribution. This repository contains the complete toolchain and scripts required to compile custom OS images from source, including kernel configuration, U-Boot handling, and board-specific tweaks for various ARM and ARM64 single-board computers.
aarch64armdebianfirmwareframeworkimageisokernelkernel-compilationkernel-hackinglightweightlinuxlinux-distributionoperating-systemu-bootubuntuuefiwsl2x86
633242e835
- change console welcome text - changed display manager to lightdm by default and remove nodm completly - desktop login manager enabled by default, toogle can be done with armbian-config - added URL to the build script and commit hash to /etc/armbian-release file - added debconf-utils,html2text,mmc-utils,sunxi-tools to the base and additional pkg list - added synaptic package manager and onboard keyboard to the desktop base - changed motd console welcome text to: Welcome to Debian Stretch with Armbian Linux 5.1.6-sunxi - added "logout" to the panel/menu - added normal users to additional groups: disk tty users games * Adjust tabs and alter displaying build options at the end - hide empty ones * Fix wrong MOTD message, adjust logic to autologin by default and request login for both notebooks * Making fs cache naming more intuitive, rename script * Move additional kernel drivers into separate file. Add AUFS for K5.1 this way, attach wireguard sources to last known working tag. master is broken atm * Add two more extra wireless drivers 88x2BU, (improved) 8811EU and introduce switch EXTRAWIFI which is enabled by default * Move 8812AU to the same version we have now. More recent has some performance issues in AP mode. Adjust configuration, add mvebut-dev 5.1.y kernel * Enable Wireguard also on 3.10.y since it was fixed upstream. Attach bach to master branch since its working now * Rockchip64 & RK3399 - upstream patches and remove deprecated patches, mvebu64 add DEV kernel attached to 5.1.y * Enable BT on Tinkerboard CLI images as well * cubox-i move to 5.1.y and enable missing HDMI * Bugfixes for adding wireless driver to Kconfig. Adjusted RK3399 kernel due to upstream changes at FriendlyARM - does not boot yet. Changes has to be extract from their commits. Removed patches with RTL8188EU since we add more recent driver with a new precedure. Small fixes mvebu-default, udoo-next, s56818-next, ... remove deprecated patches. * Boot-able RK3399-default config, add upstream patches for K4.4.y mvebu-default/udoo-next * Adjust overclocking patch to meet upstream changes * Odroid XU4 - remove deprecated kernel patches |
||
|---|---|---|
| .github | ||
| config | ||
| lib | ||
| packages | ||
| patch | ||
| .dockerignore | ||
| .gitignore | ||
| compile.sh | ||
| config-docker.conf | ||
| config-vagrant.conf | ||
| Dockerfile | ||
| LICENSE | ||
| main.sh | ||
| README.md | ||
| Vagrantfile | ||
Armbian
Debian based Linux for ARM based single-board computers
How to build an image or a kernel?
Supported build environment is Ubuntu Bionic 18.04 x64 (minimal iso image).
- guest inside a VirtualBox or other virtualization software,
- guest managed by Vagrant. This uses Virtualbox (as above) but does so in an easily repeatable way,
- inside a Docker, systemd-nspawn or other container environment (example),
- running natively on a dedicated PC or a server (not recommended),
- 25GB disk space or more and 2GB RAM or more available for the VM, container or native OS,
- superuser rights (configured
sudoor root access).
Execution
apt-get -y install git
git clone https://github.com/armbian/build
cd build
./compile.sh
Make sure that full path to the build script does not contain spaces.
You will be prompted with a selection menu for a build option, a board name, a kernel branch and an OS release. Please check the documentation for advanced options and additional customization.
Build process uses caching for the compilation and the debootstrap process, so consecutive runs with similar settings will be much faster.
How to report issues?
Please read this notice first before opening an issue.
How to contribute?
- Fork the project
- Make one or more well commented and clean commits to the repository.
- Perform a pull request in github's web interface.
If it is a new feature request, don't start the coding first. Remember to open an issue to discuss the new feature.
If you are struggling, check this detailed step by step guide on contributing.