NixOS on ARM/UEFI - Revision history

Ardenet: Marked this version for translation

2025-10-07T22:41:37Z

Marked this version for translation

← Older revision		Revision as of 22:41, 7 October 2025
Line 54:		Line 54:
	As an opinionated example, you can get started with [https://github.com/Tow-Boot/Tow-Boot Tow-Boot, a ''U-Boot'' distribution], which is intended to make the initial setup a bit easier by abstracting the platform differences so that they do not matter.		As an opinionated example, you can get started with [https://github.com/Tow-Boot/Tow-Boot Tow-Boot, a ''U-Boot'' distribution], which is intended to make the initial setup a bit easier by abstracting the platform differences so that they do not matter.

			<!--T:51-->
	Where supported, Nix can be used to build U-boot from its main-line repositories. See [[U-Boot#Building a packaged U-Boot]] for further information. The resulting firmware image can then be flashed to SPI with tools such as <code>flashcp</code> or <code>flashrom</code>, or installed to EMMC/SD card by writing to specific offsets. This is platform specific, refer to [https://github.com/u-boot/u-boot/tree/master/doc/board upstream U-boot documentation for your platform or board].		Where supported, Nix can be used to build U-boot from its main-line repositories. See [[U-Boot#Building a packaged U-Boot]] for further information. The resulting firmware image can then be flashed to SPI with tools such as <code>flashcp</code> or <code>flashrom</code>, or installed to EMMC/SD card by writing to specific offsets. This is platform specific, refer to [https://github.com/u-boot/u-boot/tree/master/doc/board upstream U-boot documentation for your platform or board].

Ryjelsum: /* Getting a Platform Firmware */ more specificity

2025-07-19T14:56:47Z

Getting a Platform Firmware: more specificity

← Older revision		Revision as of 14:56, 19 July 2025
Line 54:		Line 54:
	As an opinionated example, you can get started with [https://github.com/Tow-Boot/Tow-Boot Tow-Boot, a ''U-Boot'' distribution], which is intended to make the initial setup a bit easier by abstracting the platform differences so that they do not matter.		As an opinionated example, you can get started with [https://github.com/Tow-Boot/Tow-Boot Tow-Boot, a ''U-Boot'' distribution], which is intended to make the initial setup a bit easier by abstracting the platform differences so that they do not matter.

	Where supported, Nix can be used to build U-boot from its main-line repositories. See [[U-Boot#Building a packaged U-Boot]] for further information. The resulting image can then be flashed to SPI with tools such as <code>flashcp</code> or <code>flashrom</code>, or installed to EMMC/SD card by writing to specific offsets. This is platform specific, refer to [https://github.com/u-boot/u-boot/tree/master/doc/board upstream U-boot documentation for your platform or board].		Where supported, Nix can be used to build U-boot from its main-line repositories. See [[U-Boot#Building a packaged U-Boot]] for further information. The resulting firmware image can then be flashed to SPI with tools such as <code>flashcp</code> or <code>flashrom</code>, or installed to EMMC/SD card by writing to specific offsets. This is platform specific, refer to [https://github.com/u-boot/u-boot/tree/master/doc/board upstream U-boot documentation for your platform or board].

	<!--T:21-->		<!--T:21-->

Ryjelsum: Added brief directions and reference links for building and flashing U-boot from Nixpkgs

2025-07-19T03:31:05Z

Added brief directions and reference links for building and flashing U-boot from Nixpkgs

← Older revision		Revision as of 03:31, 19 July 2025
Line 53:		Line 53:
	<!--T:20-->		<!--T:20-->
	As an opinionated example, you can get started with [https://github.com/Tow-Boot/Tow-Boot Tow-Boot, a ''U-Boot'' distribution], which is intended to make the initial setup a bit easier by abstracting the platform differences so that they do not matter.		As an opinionated example, you can get started with [https://github.com/Tow-Boot/Tow-Boot Tow-Boot, a ''U-Boot'' distribution], which is intended to make the initial setup a bit easier by abstracting the platform differences so that they do not matter.

			Where supported, Nix can be used to build U-boot from its main-line repositories. See [[U-Boot#Building a packaged U-Boot]] for further information. The resulting image can then be flashed to SPI with tools such as <code>flashcp</code> or <code>flashrom</code>, or installed to EMMC/SD card by writing to specific offsets. This is platform specific, refer to [https://github.com/u-boot/u-boot/tree/master/doc/board upstream U-boot documentation for your platform or board].

	<!--T:21-->		<!--T:21-->

Nicolas-goudry at 20:40, 12 July 2024

2024-07-12T20:40:17Z

← Older revision		Revision as of 20:40, 12 July 2024
Line 46:		Line 46:
	Believe me or not, it's more likely that you can, if your SBC is well supported by mainline ''[[U-Boot]]''. ''U-Boot'' provides enough UEFI to comply with EBBR, which in turn is enough to allow us to boot the <tt>AArch64</tt> UEFI NixOS iso, and with almost no differences compared to the <tt>x86_64</tt> guide, simply follow the installation instruction to boot into an installed system.		Believe me or not, it's more likely that you can, if your SBC is well supported by mainline ''[[U-Boot]]''. ''U-Boot'' provides enough UEFI to comply with EBBR, which in turn is enough to allow us to boot the <tt>AArch64</tt> UEFI NixOS iso, and with almost no differences compared to the <tt>x86_64</tt> guide, simply follow the installation instruction to boot into an installed system.

	=== Getting a ''Platform Firmware'' === <!--T:18-->		== Getting a ''Platform Firmware'' == <!--T:18-->

	<!--T:19-->		<!--T:19-->

Nicolas-goudry at 17:01, 12 July 2024

2024-07-12T17:01:20Z

← Older revision		Revision as of 17:01, 12 July 2024
Line 1:		Line 1:
	<~~language~~/>		<languages/>
	<translate>		<translate>
	<!--T:1-->		<!--T:1-->

Nicolas-goudry at 17:00, 12 July 2024

2024-07-12T17:00:52Z

← Older revision		Revision as of 17:00, 12 July 2024
Line 1:		Line 1:
			<language/>
	<translate>		<translate>
	<!--T:1-->		<!--T:1-->

Nicolas-goudry: Marked this version for translation

2024-07-12T15:31:59Z

Marked this version for translation

Show changes

Nicolas-goudry at 15:31, 12 July 2024

2024-07-12T15:31:53Z

← Older revision		Revision as of 15:31, 12 July 2024
Line 1:		Line 1:
			<translate>
	{{ARM/breadcrumb}}		{{ARM/breadcrumb}}

Line 117:		Line 118:

	It is unknown how much of an actual issue this is in practice.		It is unknown how much of an actual issue this is in practice.
			</translate>

Samueldr: /* Platform Firmware */ Add links to U-Boot

2024-04-07T04:53:27Z

Platform Firmware: Add links to U-Boot

← Older revision		Revision as of 04:53, 7 April 2024
Line 17:		Line 17:
	Let's define what a '''Platform Firmware''' is. It is a generic term I'm using to describe the first thing the CPU starts at boot time. On your typical <tt>x86_64</tt> system, it would be what was previously called the ''BIOS''. Now often diminutively called by the name ''EFI''. This is what initializes enough of the hardware so that the operating system can start. Additionally, it often provides facilities for the user to do basic configuration, and manage boot options.		Let's define what a '''Platform Firmware''' is. It is a generic term I'm using to describe the first thing the CPU starts at boot time. On your typical <tt>x86_64</tt> system, it would be what was previously called the ''BIOS''. Now often diminutively called by the name ''EFI''. This is what initializes enough of the hardware so that the operating system can start. Additionally, it often provides facilities for the user to do basic configuration, and manage boot options.

	In the ARM with SBCs landscape, '''U-Boot''' is the de facto solution for the ''Platform Firmware''. Though ''U-Boot'' is confusingly, but rightly, often referred to as a ''Boot Loader''. ''U-Boot'' plays double duties often. It is tasked with ''initializing the hardware'', and often also used to handle ''loading and booting'' the operating system.		In the ARM with SBCs landscape, '''''[[U-Boot]]''''' is the de facto solution for the ''Platform Firmware''. Though ''U-Boot'' is confusingly, but rightly, often referred to as a ''Boot Loader''. ''U-Boot'' plays double duties often. It is tasked with ''initializing the hardware'', and often also used to handle ''loading and booting'' the operating system.

	=== UEFI ===		=== UEFI ===
Line 31:		Line 31:
	== UEFI, on my SBC??? ==		== UEFI, on my SBC??? ==

	Believe me or not, it's more likely that you can, if your SBC is well supported by mainline ''U-Boot''. ''U-Boot'' provides enough UEFI to comply with EBBR, which in turn is enough to allow us to boot the <tt>AArch64</tt> UEFI NixOS iso, and with almost no differences compared to the <tt>x86_64</tt> guide, simply follow the installation instruction to boot into an installed system.		Believe me or not, it's more likely that you can, if your SBC is well supported by mainline ''[[U-Boot]]''. ''U-Boot'' provides enough UEFI to comply with EBBR, which in turn is enough to allow us to boot the <tt>AArch64</tt> UEFI NixOS iso, and with almost no differences compared to the <tt>x86_64</tt> guide, simply follow the installation instruction to boot into an installed system.

	=== Getting a ''Platform Firmware'' ===		=== Getting a ''Platform Firmware'' ===

imported>Samueldr: edit link to new kernel iso

2024-01-20T00:08:41Z

edit link to new kernel iso

← Older revision		Revision as of 00:08, 20 January 2024
Line 45:		Line 45:
	Choose one of the images (in rough order of preference):		Choose one of the images (in rough order of preference):

	* [https://hydra.nixos.org/job/nixos/trunk-combined/nixos.~~iso_minimal_new_kernel~~.aarch64-linux NixOS unstable, new kernel] – rolling release, latest mainline kernel, ~~may be somewhat~~ behind ~~on Nixpkgs updates due to out of tree module compatibility issues~~		* [https://hydra.nixos.org/job/nixos/trunk-combined/nixos.iso_minimal_new_kernel_no_zfs.aarch64-linux NixOS unstable, new kernel] – rolling release, latest mainline kernel, does not build with ZFS as it would often lag behind.
	* [https://hydra.nixos.org/job/nixos/trunk-combined/nixos.iso_minimal.aarch64-linux NixOS unstable, LTS kernel] – may be less compatible with specific hardware, but tracks a more recent Nixpkgs		* [https://hydra.nixos.org/job/nixos/trunk-combined/nixos.iso_minimal.aarch64-linux NixOS unstable, LTS kernel] – may be less compatible with specific hardware, but tracks a more recent Nixpkgs
	* [https://nixos.org/download.html#download-nixos NixOS stable] – release branch, LTS kernel, generally not recommended unless you are confident your hardware is well-supported upstream		* [https://nixos.org/download.html#download-nixos NixOS stable] – release branch, LTS kernel, generally not recommended unless you are confident your hardware is well-supported upstream