Does it run?¶
We have compiled a list of popular applications that are of interest to the Ten64 community and methods to run them.
Distributions¶
Due to the 'newness' of the Ten64 and DPAA2 hardware, many distributions have not enabled the required drivers, or there are incompatibilies with our bootloader (see roadmap)
See the Distributions page for information on known interoperability issues.
Most of the distributions that are currently not working natively can be made to work by installing a mainline kernel and/or minor bootloader configuration changes.
All of the distributions in this section that have "Yes" in their column can be installed via the bare metal appliance store (known as baremetal-deploy) or the μVirt appliance store, or another method if noted.
| Distribution | Native / Bare Metal | VM | Notes |
|---|---|---|---|
| Debian | Yes* | Yes | Debian 12 (bookworm), testing and unstable available from appliance store. See distribution installer application note if you want to use the Debian installer. |
| Fedora | Yes* | Yes | Version 38 available from appliance store. Minor adjustments required for native boot (implemented by baremetal-deploy). For specific details, see workaround steps. See distribution installer application note if you want to use the Fedora installer. |
| Ubuntu | Yes* | Yes | Ubuntu 20.04 and later cloud image works from NVMe but DPAA2 Ethernet driver (and USB3) is not installed by default. See steps for Ubuntu 20.10 |
| OpenSuSE | Yes | Yes | Leap 15.4 and Tumbleweed work OK |
| FreeBSD | Yes! (NEW) | Yes | See FreeBSD preview for Ten64. We anticipate full support from FreeBSD 14.0-STABLE onwards. |
| OpenBSD | No | No | Changes to run OpenBSD as VM under investigation |
| Alpine Linux | No | Needs work | There is an aarch64 ISO but no 'cloud' image |
| Gentoo and Funtoo | Yes | Planned | Use gentoo-setup to create a working system from a stage3 tarball |
| Arch | Yes | Some assembly required | Kernel Package linux-aarch64 5.11 and later. Use arch-setup to deploy natively.To assemble a VM image, see contributed instructions on the support forum |
| Yocto | Yes | Yes | See meta-traverse layer for Yocto Kirkstone |
| CentOS 8 | No Later kernel required |
Yes | CentOS/RHEL kernel does not have Layerscape drivers, need to use a later kernel (e.g install kernel RPMs from Fedora 33), sadly there is no EPEL/'kernel-ml' on aarch64. The other steps required are similar to Fedora. |
Router and Firewall¶
| Name | Native/Bare Metal | VM | Notes |
|---|---|---|---|
| OpenWrt | Yes | Yes | armsr branch (23.05 and later) for disk boot, layerscape for NAND. See OpenWrt page in this manual and OpenWrt upstreaming update |
| pfsense | No | Possible? | Might be able to generate an ARM64 installer image from source |
| IPFire | Yes | Yes | |
| VyOS | Yes* | Yes* | Experimental port - you will need to compile your own image from vyos-arm64-builder using a Debian ARM64 instance first |
Storage and NAS¶
| Name | Native/Bare Metal | VM | Notes |
|---|---|---|---|
| Rockstor | Yes | Yes | Supported from Rockstor 4 (openSuSE based). Binaries not published yet, see our Rockstor page |
| OpenMediaVault | Yes | Yes | Install Debian and then install OpenMediaVault from their apt repository |
Rockstor's Rock-On feature has a curated collection of addons which is a good way of deploying many applications - if you are not familiar with containers or Docker, consider starting there.
Applications¶
If your application does not publish ARM64 containers directly, sources such as LinuxServer.io may be an alternative.
IoT and Home Automation¶
See our ZigBee Home Automation application note for useful information on using ZigBee (and similar technolgies, such as Z-Wave) receivers.
| Name | Recommended Method |
|---|---|
| WebThings | Use packaged versions for your favourite distribution or the webthingsio/gateway container image |
| Home Assistant | Dedicated VM (if dealing with USB, as above), or container |
Media Servers (DLNA etc.)¶
| Name | Recommended Method |
|---|---|
| Emby Media Server | Download and Install arm64 package for your distribution |
Collaboration / Chat / Video¶
| Name | Recommended Method |
|---|---|
| Jitsi Meet | Container |
Personal/Private Cloud¶
| Name | Recommended Method |
|---|---|
| Nextcloud | Official container |
| Duplicati | LinuxServer.io container (not all versions from the offical Docker have arm64) |
Networking¶
| Name | Recommended Method |
|---|---|
| UniFi controller | LinuxServer.io container |
| Pi-Hole | Dedicated VM or container (with bridged network) |
Network Security¶
| Name | Recommended Method |
|---|---|
| Kismet | Bare metal or VM |
| Suricata | VM / DPAA2 chained (HOWTO pending) |
Cloud and Edge Computing¶
| Name | Recommended Method |
|---|---|
| K3s | VM - we are working on an "appliance" image |
| KubeEdge | Use Debian VMs as base and deploy with Ansible playbook |
If you are interested in running cloud-to-edge stacks such as:
- AWS Greengrass
- Azure IoT Edge
Please contact Traverse - we may be able to assist.
AI¶
| Name | Notes |
|---|---|
| TensorFlow Lite | Google's Coral AI miniPCIe and M.2 works with VFIO passthrough in muvirt |
Software Defined Radio¶
- GNURadio and LimeSDR - see the LimeSDR-FM Streaming Demo
Development¶
-
Works on ARM has facilitated ARM64 support for many development tools and languages
Not on the list?¶
If the software in question works on the Raspberry Pi 3 or 4, there is a good chance it will run on the Ten64 - you might just need to get the correct packages for your chosen distribution.
We appreciate any information on applications not listed here and welcome issues or merge requests in the documentation repository.