Supported Linux platforms and system requirements
The Wallboard Linux client runs on 64-bit PCs and ARM64 devices with a compatible Linux operating system and graphics stack. Compatibility depends on the operating system, CPU architecture, graphics drivers, and installed client release.
This page describes the tested operating systems and the requirements to check when selecting a player.
Tested operating systems
The following operating system versions have been used in Wallboard Linux testing:
| Operating system | Tested version |
|---|---|
| Debian | 12 |
| Debian | 13 |
| Ubuntu | 24.04 LTS, including 24.04.4 LTS |
The list records tested OS versions. It does not mean that every device, CPU architecture, desktop environment, or hardware feature has been tested on each version. Confirm the complete configuration for your deployment, including the intended content and client release.
The installer also includes dependency installation for the RHEL/Fedora, SUSE, and Arch families and recognizes compatible derivatives. These are additional installation paths, rather than an extension of the tested OS list above.
Required system components
| Component | Requirement |
|---|---|
| CPU architecture | AMD64 (x86_64) for 64-bit Intel/AMD systems, or ARM64 (aarch64). Use the matching 64-bit operating system and client package. |
| Runtime libraries | A glibc-based system with the glibc and C++ runtime versions required by the selected client release. |
| System services | systemd, including systemctl and systemd-run. |
| Installation tools | Bash, Python 3, OpenSSL, and administrator access. A non-root installer needs sudo; server-based installation also needs curl. |
| Graphics | A working X11 or Wayland graphics environment and the operating system's drivers for the installed GPU. |
| Automatic kiosk setup | An active local X11 or Wayland session for the selected user during initial setup. Installation can be run through SSH, but an SSH connection does not create that graphical session. |
| Dedicated Wayland kiosk | The host's Weston compositor and working graphics drivers. Availability of display control depends on the installed Weston version and display configuration. |
| Storage | Writable persistent storage with room for the application, downloaded content, logs, and installation/update work. See Hardware sizing. |
| Network | Connectivity to the Wallboard server and content sources for registration, updates, and content downloads. Installing missing system dependencies also needs access to the OS package repositories. |
32-bit operating systems and other CPU architectures are not supported by the native Linux packages.
The installer checks the host against the selected release's runtime libraries. A requirement such as glibc >= 2.34 or GLIBCXX >= 3.4.29 describes that particular build; it is not a permanent minimum for every Linux release. Use the matching installer and package, and check the requirements it reports.
Hardware sizing
Recommended starting configuration
Use the following as a starting point for a basic player. These are planning recommendations, rather than a guarantee for every content layout.
| Resource | Starting recommendation |
|---|---|
| Memory | 4 GB RAM or more for the operating system, graphical session, and player. Increase this for demanding web pages, simultaneous videos, or other applications running on the device. |
| Application and update space | Plan for 5 GB or more of free space, in addition to the space required by the OS and downloaded content. This provides headroom for the application, downloads, extraction, and retained versions used during updates. |
| Content storage | Additional capacity for the media and other content assigned to the device. Size this for the intended offline content collection. |
| Graphics and video | A GPU and driver combination that can play the intended codecs, resolutions, and simultaneous media streams reliably. |
| CPU | A processor supported by the chosen OS and client runtime, sized for the actual web content, animations, and video workload. |
A Raspberry Pi with 2 GB RAM has been used in testing. This provides a tested lower-memory configuration for the OS and content used on that device. A full desktop environment, several videos, or complex web pages can need more memory. For a 2 GB player, validate the intended OS image and complete content layout before deployment; the operating system's own memory requirements still apply.
Always allow for the operating system's own requirements. For example, the Ubuntu 24.04 Desktop installation guide specifies at least 25 GB of storage for the OS installation. That is separate from the additional free space and content capacity planned for Wallboard.
The Debian 12 and Debian 13 desktop requirements also describe the operating system, rather than a tested Wallboard workload.
Allow room for installation and updates
The application archive's download size is smaller than its extracted size. Capacity planning must include:
- The installed application and system dependencies.
- The downloaded archive and temporary extraction.
- Retained application files needed while an update is activated or rolled back.
- Downloaded media, content cache, and logs.
The 5 GB application/update allowance does not include the operating system or the content cache. A large media collection can require substantially more storage.
Hardware-dependent features
Installing successfully does not establish that every display or power-management feature is available.
| Feature | What to verify on the device |
|---|---|
| Screen ON/OFF and SCREEN working hours | A compatible display-power backend and monitor. Availability depends on the GPU, display connection, desktop/compositor, and monitor capabilities. |
| Device shutdown and scheduled wake | Verified hardware/firmware RTC wake capability. When device-power scheduling is unavailable, the client can use SCREEN scheduling instead. |
| Live display control in a dedicated Wayland kiosk | A supported Weston control module and display layout. The current live-control path requires one connected DRM display output; this is a control limitation, rather than a universal single-display playback requirement. |
| Video playback and hardware acceleration | The actual codecs, resolutions, frame rates, and simultaneous video count used in your content, with the installed GPU drivers. |
| Rotation and multiple displays | The exact output layout and orientation. These depend on the selected graphics backend and need separate testing. |
An ARM64 package does not by itself qualify every ARM board or Raspberry Pi model. The board's OS image, graphics driver, and display connection still need to meet these requirements.
A virtual machine can be useful for checking installation and registration. Its virtual graphics, display-power, and wake capabilities do not establish the same features on a physical player.
Installation
Follow Standard installation on Linux for server and ZIP installation, kiosk setup, command-line options, updates, and removal.