Updated SBC doc according to #168
This commit is contained in:
Peter Boy
parent
127ae69b2b
commit
2bffb92e46
3 changed files with 33 additions and 20 deletions
|
|
@ -2,8 +2,6 @@
|
|||
** xref:installation/interactive-local.adoc[Interactive local installation]
|
||||
** xref:installation/interactive-remote.adoc[Interactive remote installation]
|
||||
** xref:installation/sw-raid-upon-installation.adoc[Exkurs: Configuring a software RAID upon interactive installation]
|
||||
|
||||
** xref:installation/on-sbc.adoc[ARM Single Board Computer Installation]
|
||||
** xref:installation/postinstallation-tasks.adoc[Post Installation Tasks]
|
||||
|
||||
* xref:administration/index.adoc[Basic Administration]
|
||||
|
|
@ -35,7 +33,9 @@
|
|||
* Tutorials
|
||||
** xref:tutorials/imagefactory.adoc[ImageFactory - How to create a virtual machine disk image]
|
||||
** xref:tutorials/wordpress-installation.adoc[Installing Wordpress CMS]
|
||||
* xref:server-on-sbc/index.adoc[Special: Single Board Computers]
|
||||
|
||||
* xref:server-on-sbc/index.adoc[Special: Fedora Server on ARM Single Board Computers - the Raspberry Pi & Co]
|
||||
** xref:server-on-sbc/uboot-installation.adoc[ARM Single Board Computer Installation]
|
||||
|
||||
* xref:server-faq.adoc[FAQ]
|
||||
* xref:server-communicating.adoc[Getting in Touch]
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
= Fedora Server on Single Board Computers - Raspberry Pi & Co.
|
||||
= Fedora Server on ARM Single Board Computers - the Raspberry Pi & Co.
|
||||
Fredrik Arneving; Peter Boy; Jan Kuparinen
|
||||
:page-authors: {author}, {author_2}, {author_3}
|
||||
:revnumber: F36,F37
|
||||
|
|
@ -6,14 +6,13 @@ Fredrik Arneving; Peter Boy; Jan Kuparinen
|
|||
// :revremark: a new beginning
|
||||
|
||||
|
||||
[abstrqact]
|
||||
____
|
||||
Fedora has already supported the ARM architecture, and specifically ARM Single Board Computers (SBCs), for quite some time. Especially for these there is also a Fedora Server Edition installation media. But there are a number of pitfalls to be aware of.
|
||||
____
|
||||
[abstract]
|
||||
Fedora has already supported the ARM architecture, and specifically ARM Single Board Computers (SBCs), for quite some time. Especially for these there is also a Fedora Server Edition installation medium available. But there are a number of pitfalls to be aware of.
|
||||
|
||||
Fedora Server is also available for Single Board Computers (SBC) like the well-known Raspberry Pi. Once started as an experimentation and education tool, the technology evolved into an affordable but sufficiently powerful tool for many task of everyday life. Even though these devices are very miniature and limited in power, they offer enough strength, to install a dedicated modern, solid Linux system. This is especially true for the newer alternatives to the well known Raspberry Pi.
|
||||
|
||||
SBC Fedora Server Edition takes advantage of the power available on SBC today to install a dedicated modern, solid server system. In the end Fedora Server works on application level exactly as otherwise familiar. Depending on the application, however, this is not necessarily a limitation for practical usability.
|
||||
Once started as an experimentation and education tool, the technology evolved into an affordable but sufficiently powerful tool for many tasks of everyday life. Even though these devices are very miniature and limited in power, they offer enough strength, to install a dedicated modern, solid Linux system. This is especially true for the newer alternatives to the well known Raspberry Pi.
|
||||
|
||||
SBC Fedora Server Edition takes advantage of the power available on SBC today to install a dedicated modern, solid server system. In the end Fedora Server works on application level exactly as otherwise familiar.
|
||||
|
||||
But not all SBC models are equally or similarly capable for a Fedora Server deployment.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,14 +1,15 @@
|
|||
= ARM Single Board Computer (SBC) Installation
|
||||
= Installation based on __u-boot__
|
||||
Fredrik Arneving; Peter Boy; Emmanuel Seyman
|
||||
:page-authors: {author}, {author_2}, {author_3}
|
||||
:revnumber: F37,F38
|
||||
:revdate: 2023-05-19
|
||||
:revnumber: F37-F43
|
||||
:revdate: 2025-10-28
|
||||
|
||||
:page-aliases: pages/installation-on-sbc.adoc
|
||||
:page-aliases: pages/server-installation-sbc.adoc
|
||||
:page-aliases: pages/installation/on-sbc.adoc
|
||||
|
||||
[abstract]
|
||||
Fedora Server is also available for various Single Board Computers (SBC) like the well-known Raspberry Pi. Installation works quite different, though. But in the end __Fedora Server works on application level exactly as otherwise familiar__.
|
||||
ARM Single Board Computers originally had only __one data storage medium__, an SD card. And they use to have no BIOS or equivalent firmware to initialize the hardware at boot time and make it accessible. The operating system has to provide this function, too. The u-boot bootloader is one of several options for providing this function. Therefore, the installation method for SBC devices works quite differently from what is otherwise known from Fedora.
|
||||
|
||||
|
||||
// Please, comment in the Warning below when you start
|
||||
|
|
@ -25,13 +26,14 @@ Fedora Server is also available for various Single Board Computers (SBC) like th
|
|||
|
||||
== How it works
|
||||
|
||||
Single board computers originally had only __one data storage medium__, an SD card. The device expects a ready-to-use operating system, configured precisely for the respective hardware. This original principle is still maintained today and is the universal method provided by every SBC model.
|
||||
Even though many SBC devices now also feature eMMC modules or m.2 NVMe interfaces, the boot process remains very simple. The minimal firmware continues to boot from the SD card, and possibly supplementally from eMMC or an SPI flash module. The device expects a ready-to-use operating system, configured precisely for the respective hardware, including low-level hardware initialization.
|
||||
|
||||
Therefore, Fedora Server Edition is distributed as an __image file__, and installation is a matter of _transferring this image file_ to the designated storage medium, traditionally an SD card. The various SBCs differ significantly in hardware features and architecture. Instead of creating a separate distribution file for each model, Fedora distributes a _unified image file_. A special program, _arm-image-installer_, transfers the image and adapts it to the target model.
|
||||
A widely used software that provides this functionality is the bootloader __u-boot__. It is basically a collection of low-level, model-specific device drivers.
|
||||
|
||||
Many SBC models today offer additionally alternative storage media, especially eMMC memory, either pluggable or soldered. These SBCs can alternatively boot and operate directly from this remarkable faster memory. A pluggable memory can be connected to the desktop with an adapter instead of the SD card. In case of soldered memory, you must first go through the installation process with the SD card, and then use that system to copy an installation image to the internal eMMC memory in a second step.
|
||||
Instead of creating a separate distribution file for each model, Fedora Server Edition is distributed as an __unified basic image file__. The installation program _arm-image-installer_, transfers this image file to the designated storage medium and then adds model-specific u-boot bootloader files.
|
||||
|
||||
Even though the installation works quite differently, Fedora Server ultimately functions just like usual at the application level.
|
||||
|
||||
Some models can also support extended firmware, usually in the form of SPI modules that allow further selections during boot, e.g. NVMe boards, SATA drives, or USB sticks. This requires separate, model-dependent installation steps. It is best to perform the basic installation described here first.
|
||||
|
||||
== Prerequisites
|
||||
|
||||
|
|
@ -60,6 +62,18 @@ Fedora uses UEFI as the boot system, but on SBCs it still uses a DOS/MBR partiti
|
|||
|
||||
For practical reasons, the downloaded deliverable is limited to just under 8 GB in total. During or after installation, the size is adjusted to the existing hardware.
|
||||
|
||||
== Handling different boot media
|
||||
|
||||
Many SBC models today offer additionally alternative storage media, especially eMMC memory, either pluggable or soldered. Nevertheless, the installation procedure remains basically the same.
|
||||
|
||||
These SBCs can alternatively boot and operate directly from this remarkable faster memory. A pluggable memory can be connected to the desktop with an adapter. It is then the target for the image transfer, instead of the SD card. instead of the SD card. In case of soldered memory, you must first go through the installation process with the SD card, and then use that system to copy an installation image to the internal eMMC memory in a second step.
|
||||
|
||||
Some models provide a special flash module (SPI) to store a custom bootloader. For these cases, the u-boot bootloader offers a special format that is flashed onto the SPI module. This requires a board-specific tool independent from Fedora. The Fedora Server unified basic image file is transferred to the installation medium unchanged.
|
||||
|
||||
These bootloaders quite often support extended options to boot from, e.g. NVMe boards, SATA drives, or USB sticks.
|
||||
|
||||
Here we describe the basic steps for creating a customized boot medium (SD card or eMMC module).
|
||||
|
||||
|
||||
== Steps to install Fedora Server Edition on a Single Board Computer
|
||||
|
||||
|
|
@ -72,12 +86,12 @@ For practical reasons, the downloaded deliverable is limited to just under 8 GB
|
|||
[…]$ sudo dnf -y install arm-image-installer uboot-images-armv8.noarch
|
||||
----
|
||||
|
||||
2. Set the download directory as default, fetch a Fedora Server aarch64 system disk raw image, here F38, and check the integrity of the download.
|
||||
2. Set the download directory as default, fetch a Fedora Server aarch64 system disk raw image, here F43, and check the integrity of the download.
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
[…]$ cd ~/Downloads
|
||||
[…]$ wget https://download.fedoraproject.org/pub/fedora/linux/releases/38/Server/aarch64/images/Fedora-Server-38-1.6.aarch64.raw.xz -O Fedora-Server-38-1.6.aarch64.raw.xz
|
||||
[…]$ wget https://download.fedoraproject.org/pub/fedora/linux/releases/43/Server/aarch64/images/Fedora-Server-Host-Generic-43-1.6.aarch64.raw.xz -O Fedora-Server-38-1.6.aarch64.raw.xz
|
||||
[…]$ wget https://download.fedoraproject.org/pub/fedora/linux/releases/38/Server/aarch64/images/Fedora-Server-38-1.6-aarch64-CHECKSUM
|
||||
[…]$ sha256sum -c *-CHECKSUM --ignore-missing
|
||||
----
|
||||
Loading…
Add table
Add a link
Reference in a new issue