nixos-raspberrypi

Unopinionated Nix flake for infrastructure, vendor packages, kernel, and some optimized third-party packages for NixOS running on Raspberry Pi devices.

It will let you deploy NixOS fully declaratively in one step with tools like nixos-anywhere.

What does it do

Provisions and manages Raspberry Pi firmware partition /boot/firmware. Partition is being provisioned on nixos generation switch (integrated with bootloader activation scripts, as opposed to oneshot systemd services, for example), enabling to use deployment tools like nixos-anywhere without any interactive intervention.

Supported boot methods: rpiboot, uboot. Also mostly-working uefi in a separate branch.

How to use

This flake can be consumed in a number of ways:

Add flake input

inputs = {
  nixos-raspberrypi = {
    url = "github:nvmd/nixos-raspberrypi";
    inputs = {
      # optionally follow your own `nixpkgs` inputs
      # this may make binary cache unavailable!
      nixpkgs.follows = "nixpkgs";
      nixpkgs-unstable.follows = "nixpkgs-unstable";
    };
  };
};

Optional: Use binary cache

Pre-built packages are provided for nixpkgs and nixpkgs-unstable locked with flake.lock

nixConfig = {
  extra-substituters = [
    "https://nixos-raspberrypi.cachix.org"
  ];
  extra-trusted-public-keys = [
    "nixos-raspberrypi.cachix.org-1:4iMO9LXa8BqhU+Rpg6LQKiGa2lsNh/j2oiYLNOQ5sPI="
  ];
};

Import modules corresponding to your hardware

imports = with nixos-raspberrypi.nixosModules; [
  # choose one of the following base board support modules
  raspberry-pi-4.base
  raspberry-pi-5.base

  # RPi4:
  # import this if you have the display, on rpi4 this is the only display configuration option
  raspberry-pi-4.display-vc4
  # Fan control for ArgonOne V2 case
  raspberry-pi-4.case-argonone

  # RPi5-specific, one of them for "PrimaryGPU" configuration:
  raspberry-pi-5.display-vc4  # "regular" display connected
  raspberry-pi-5.display-rp1  # for RP1-connected (DPI/composite/MIPI DSI) display
];

See flake.nix, nixosModules for a full of configuration modules for your hardware.

Import overlays you want

By default, modules use packages available in pkgs, i.e. they don't internally apply any of the overlays provided by this flake to avoid potential conflicts with what you may want to achieve.

If you don't have any special needs, you may import helper modules to apply overlays for you

imports = [
  # Required: Bootloaders, linux kernel, firmware, raspberry's utils
  # additionally, `nixpkgs.rpi` with _all_ overlays applied (see below)
  nixos-raspberrypi.lib.inject-overlays

  # Optional: Applies overlays with optimized packages to the global scope, 
  # including ffmpeg_{4,6,7}, kodi, libcamera, SDL2, vlc
  # Use with caution – this may cause lots of rebuilds (even though many 
  #  packages should be available in a binary cache above)
  nixos-raspberrypi.lib.inject-overlays-global
];

For more fine-grained control and full overlay list see overlays in flake.nix, and overlay helpers (mentined above) in lib.

Alternative ways to get individual packages

An alternative ways to consume individual packages without overlays are:

• to get it directly from the flake, it will based on stable nixpkgs without any of other optimisations transitively applied (i.e. only this particular package is optimised):

  environment.systemPackages = [
    nixos-raspberrypi.packages.aarch64-linux.vlc
  ];

• to get it from nixos-raspberrypi.legacyPackage.<system> or nixos-raspberrypi.legacyPackageUnstable.<system>. Here all overlays are applied.

Configure

Sane default configuration is provided by the base module for a corresponding Raspberry board, but further configuration is, of course, possible:

Configuration options for the bootloader are in boot.loader.raspberryPi (defined in modules/system/boot/loader/raspberrypi/default.nix).

Raspberry's config.txt can be configured with hardware.raspberry-pi.config options, see modules/configtxt.nix as an example (this is the default configuration as provided by RaspberryPi OS, but translated to nix format).

Deploy

for example, with nixos-anywhere to the system running installer image (will use disko to set the disks up):

$ nixos-anywhere --flake .#<system> root@<hostname>"

or, to an already running system:

$ nixos-rebuild switch --flake .#<system> --target-host root@<hostname>

Design goals

This is basically boot.loader.raspberryPi options, which are deprecated in nixpkgs, but updated and improved upon.

Design objectives:

• individually consumable modules and overlays for specific functions
• reuse of the existing nixos/nixpkgs infrastructure and idiomatic approaches to the maximum extent possible
• integration with the existing nixos system activation

Historical background

This project grew naturally out of the need to configure and extend rather great tstat's raspberry pi support repository, which we used for some time.

Unfortunately it was virtually possible to work with without reengineering the whole thing, so this Flake was born. Inability to use it non-interactively with nixos-anywhere was the biggest concern.

We found boot.loader.raspberryPi options to be much more idiomatic, easier to extend, and maintain.

This flake strives to keep and improve those properties by keeping it as unopinionated as possible and modular (see above)

We're still using some ot the modules provided by an adapted fork of tstat/raspberry-pi-nix, namely config.txt generation module.