NixOS on ARM/Raspberry Pi - Revision history

Tennox: Add Raspberry Pi 5 to tables (it's already described below)

2025-01-10T21:40:30Z

Add Raspberry Pi 5 to tables (it's already described below)

← Older revision		Revision as of 21:40, 10 January 2025
Line 22:		Line 22:
	\|-		\|-
	!colspan="2" class="title"\|Raspberry Pi 4		!colspan="2" class="title"\|Raspberry Pi 4
			\|-
			!Architecture
			\|AArch64 + ARMv7
			\|-
			! colspan="2" \|Raspberry Pi 5
	\|-		\|-
	!Architecture		!Architecture
Line 90:		Line 95:
	\| AArch64<br /> ''+ armv7''		\| AArch64<br /> ''+ armv7''
	\| Yes (only with kernel >= 6.1)		\| Yes (only with kernel >= 6.1)
			\|-
			! colspan="3" \|Raspberry Pi 5
			\|-
			\|Raspberry Pi 5
			\|AArch64<br /> ''+ armv7''
			\|C*
	\|}		\|}

JadeTheDragon: /* Power issues */ Made the text less vague and removed a redundant word.

2024-08-01T21:55:18Z

Power issues: Made the text less vague and removed a redundant word.

← Older revision		Revision as of 21:55, 1 August 2024
Line 339:		Line 339:
	=== Power issues ===		=== Power issues ===

	Especially with the power-hungry Raspberry Pi 3, it is important to have a [https://www.raspberrypi.org/documentation/hardware/raspberrypi/power/README.md sufficient enough power supply] or ~~''weirdness''~~ may ~~happen. Weirdness~~ may include:		Especially with the power-hungry Raspberry Pi 3, it is important to have a [https://www.raspberrypi.org/documentation/hardware/raspberrypi/power/README.md sufficient enough power supply] or unexpected behaviour may occur; this may include:

	* Lightning bolt on HDMI output "breaking" the display.		* Lightning bolt on HDMI output "breaking" the display.
Line 346:		Line 346:
	* Random hangs		* Random hangs

	This ~~problem~~ is a hard problem. It is caused by the Raspberry Pi warning about power issues, but the current drivers (as of		This is a hard problem. It is caused by the Raspberry Pi warning about power issues, but the current drivers (as of
	Linux 4.14) have a hard time dealing with it properly. If the power supply is rated properly AND the cable is not incurring too much power losses, it may be required to disable the lightning bolt indicator so the display driver isn't messed up.<ref>https://logs.nix.samueldr.com/nixos/2017-12-20#1513784657-1513784714;</ref> The lightning bolt indicator can be disabled by adding the line <code>avoid_warnings=1</code> in config.txt<ref>https://www.raspberrypi.org/documentation/configuration/config-txt/README.md</ref>		Linux 4.14) have a hard time dealing with it properly. If the power supply is rated properly AND the cable is not incurring too much power losses, it may be required to disable the lightning bolt indicator so the display driver isn't messed up.<ref>https://logs.nix.samueldr.com/nixos/2017-12-20#1513784657-1513784714;</ref> The lightning bolt indicator can be disabled by adding the line <code>avoid_warnings=1</code> in config.txt<ref>https://www.raspberrypi.org/documentation/configuration/config-txt/README.md</ref>

Hasnep: Fix heading level

2024-05-06T07:11:43Z

Fix heading level

← Older revision		Revision as of 07:11, 6 May 2024
Line 160:		Line 160:
	''See'' [[NixOS on ARM/Raspberry Pi 5]]		''See'' [[NixOS on ARM/Raspberry Pi 5]]

	=== Audio ===		== Audio ==

	In addition to the usual config, it might be required to enable audio support explicitly in the firmwareConfig.		In addition to the usual config, it might be required to enable audio support explicitly in the firmwareConfig.

Nbdd0121: /* Raspberry Pi 5 */

2024-04-24T12:00:20Z

Raspberry Pi 5

← Older revision		Revision as of 12:00, 24 April 2024
Line 156:		Line 156:
	=== Raspberry Pi 4 ===		=== Raspberry Pi 4 ===
	''See'' [[NixOS on ARM/Raspberry Pi 4]]		''See'' [[NixOS on ARM/Raspberry Pi 4]]

			=== Raspberry Pi 5===
			''See'' [[NixOS on ARM/Raspberry Pi 5]]

	=== Audio ===		=== Audio ===

imported>Skylark: /* Raspberry Pi 4B */ Replace with link to NixOS on ARM/Raspberry Pi 4 which seems to be more up to date

2024-02-03T14:59:02Z

Raspberry Pi 4B: Replace with link to NixOS on ARM/Raspberry Pi 4 which seems to be more up to date

@@ Line 154: / Line 154: @@
 </syntaxHighlight>
-=== Raspberry Pi 4B ===
+=== Raspberry Pi 4 ===
-Support for the Pi 4 in nixpkgs is still experimental. These configurations will boot (from [https://github.com/NixOS/nixpkgs/pull/68265#issuecomment-532040372 this PR comment]):
+''See'' [[NixOS on ARM/Raspberry Pi 4]]
-==== Without GPU ====
+=== Audio ===
 In addition to the usual config, it might be required to enable audio support explicitly in the firmwareConfig.

imported>EyJhb: Changed `YES*` to `YES` as it once were (re-added for no reason), re-added Pi 400 as that was also removed for some reason

2024-01-06T16:02:27Z

Changed `YES*` to `YES` as it once were (re-added for no reason), re-added Pi 400 as that was also removed for some reason

← Older revision		Revision as of 16:02, 6 January 2024
Line 83:		Line 83:
	\| Raspberry Pi 4 Model B		\| Raspberry Pi 4 Model B
	\| AArch64<br /> ''+ armv7''		\| AArch64<br /> ''+ armv7''
	\| YES* ([https:/~~/github~~.~~com/NixOS/nixpkgs/issues/63720 GitHub issue]~~)		\| YES
			\|-
			!colspan="3" style="text-align: left;"\|Raspberry Pi 400
			\|-
			\| Raspberry Pi 400
			\| AArch64<br /> ''+ armv7''
			\| Yes (only with kernel >= 6.1)
	\|}		\|}

	''Support''		''Support''
	* YES: Supported architecture by Nixpkgs downstream and tested to be working.		* YES: Supported architecture by Nixpkgs downstream and tested to be working.
	* YES*: Available in Nixpkgs downstream but experimental.
	* C: Community supported, and tested to be working.		* C: Community supported, and tested to be working.
	* C*: Community supported, unverified but should be working.		* C*: Community supported, unverified but should be working.

imported>Hannesg: Left a comment about the bootmanager depreaction.

2023-08-04T12:42:24Z

Left a comment about the bootmanager depreaction.

← Older revision		Revision as of 12:42, 4 August 2023
Line 326:		Line 326:

	=== Boot option 2: <code>boot.loader.raspberryPi</code> ===		=== Boot option 2: <code>boot.loader.raspberryPi</code> ===

			{{warning\| This option has been deprecated in https://github.com/NixOS/nixpkgs/pull/241534}}

	This configuration assumes that the VFAT firmware partition is mounted to /boot. If it isn't, options like <code>boot.loader.raspberryPi.firmwareConfig</code> will write their configuration to the wrong partition and have no effect.		This configuration assumes that the VFAT firmware partition is mounted to /boot. If it isn't, options like <code>boot.loader.raspberryPi.firmwareConfig</code> will write their configuration to the wrong partition and have no effect.

imported>Bct at 00:52, 3 July 2023

2023-07-03T00:52:07Z

← Older revision		Revision as of 00:52, 3 July 2023
Line 360:		Line 360:

	// ... etc.		// ... etc.
	''		'';
	}		};
	];		];
	};		};

imported>Bct: Device tree overlays

2023-07-03T00:49:52Z

Device tree overlays

← Older revision		Revision as of 00:49, 3 July 2023
Line 340:		Line 340:

	Using the 3.3v serial port via the pin headers (exact location depends on hardware version) will get u-boot output and, when configured, a Linux kernel console.		Using the 3.3v serial port via the pin headers (exact location depends on hardware version) will get u-boot output and, when configured, a Linux kernel console.

			== Device trees ==

			Raspberry Pi add-on hardware often requires a device tree overlay. On other OSes this is usually set up using a <code>dtoverlay=</code> option in config.txt on the firmware partition. This approach can be made to work on NixOS with some combination of bootloader and kernel, but it may be easier and more explicit to use NixOS' <code>hardware.deviceTree</code> option to compile the overlay directly into the device tree.

			A device tree config looks something like this:

			<syntaxhighlight lang="nix">
			hardware.deviceTree = {
			enable = true;
			overlays = [
			{
			name = "hifiberry-dacplus";
			dtsText = ''
			/dts-v1/;
			/plugin/;
			/ {
			compatible = "brcm,bcm2835";

			// ... etc.
			''
			}
			];
			};
			</syntaxhighlight>

			This will apply the overlay to all <code>.dtb</code> files with a matching <code>compatible</code> line.

			After rebooting you can check if the overlay has been applied by looking for it in the output of <code>dtc --sort /proc/device-tree</code>.

			dtoverlay may fail with <code>FDT_ERR_NOTFOUND</code> on some Raspberry Pi device tree overlays. In this case dtmerge should be used instead. There is a Nix overlay to use dtmerge for applying device tree overlays: https://github.com/NixOS/nixos-hardware/blob/429f232fe1dc398c5afea19a51aad6931ee0fb89/raspberry-pi/4/apply-overlays-dtmerge.nix

	== Troubleshooting ==		== Troubleshooting ==

imported>Bct: Kernel selection

2023-07-02T23:31:28Z

Kernel selection

← Older revision		Revision as of 23:31, 2 July 2023
Line 297:		Line 297:
	\| AArch64		\| AArch64
	\|}		\|}

			== Kernel selection ==

			By default NixOS uses the official Linux kernel released by kernel.org (a "mainline" kernel, e.g. <code>pkgs.linuxPackages</code>). This works fine on a Raspberry Pi, and is the better-tested option.

			It is also possible to use a kernel released by the Raspberry Pi Foundation (a "vendor" kernel, e.g. <code>pkgs.linuxPackages_rpi3</code>). This may be preferable if you're using an add-on board that the mainline kernel does not have drivers for.

			You can select your kernel by setting <code>boot.kernelPackages</code>.

	== Notes about the boot process ==		== Notes about the boot process ==