From Fedora Project Wiki
mNo edit summary
 
(144 intermediate revisions by 24 users not shown)
Line 1: Line 1:
{{autolang|base=yes}}
{{autolang|base=yes}}


{{admon/tip | The Raspberry Pi support is now supported in Fedora 25 Beta and later. Fedora 25 final release support is still very new so please report issues to the ARM mailing list or IRC channel }}
{{admon/tip | The Raspberry Pi 3 and 4 are supported in in all stable Fedora releases. Please report issues to the ARM mailing list or IRC channel }}


= Introduction =
== Introduction ==


The [https://www.raspberrypi.org Raspberry Pi] is a credit card-sized ARM based single board computer (SBC). Fedora supports the the Raspberry Pi Model B versions 2 and 3 in Fedora 25 Beta and later without any requirement of third party kernels or scripts to adjust offical images. This documentation describes how to get started, and includes a Fequently Asked Questions (FAQ) about what is supported and what isn't.
The [https://www.raspberrypi.org Raspberry Pi] is a credit card-sized ARM based single board computer (SBC). Fedora supports the the Raspberry Pi 3-series of devices including the 3B, 3B+, 3A+, 3CM and 3CM+ and the Raspberry Pi 4 in Fedora 37 and later releases. This documentation describes how to get started, and includes a Frequently Asked Questions (FAQ) about what is supported and what isn't.


= Supported Hardware =
== Supported Hardware ==


We currently only support the Raspberry Pi Model B versions 2 and 3.
We currently support the Raspberry Pi 3-series of devices (3B, 3B+, 3A+, CM3, CM3+) and the Raspberry Pi 4-series (4B, 400, CM4, CM4s) and the Zero2W.


= Prerequisites =
Fedora IoT lists the Raspberry Pi 4 as one of its [https://docs.fedoraproject.org/en-US/iot/reference-platforms/ Reference Platforms].


* A Raspberry Pi 2 or 3
Official support for the Zero 5B is under review.
 
=== UEFI support ===
 
The [https://github.com/pftf Pi Firmware Task Force] is working to create a fully featured [https://developer.arm.com/architectures/system-architectures/arm-systemready SystemReady-ES] UEFI port for the RPi3 and RPi4. That project is rapidly evolving. As of version 1.5, Fedora 31+ will boot in ACPI mode on the Raspberry Pi 4 with gradually improving device support as one moves to newer kernels. Given a system running a Linux 5.7+ based kernel, the onboard NIC, PCI/XHCI, Graphics, etc, work. RPi3+DT support in the project is quite complete and mature. Firmware install guides for the [https://github.com/pftf/RPi4#readme RPi4] and [https://github.com/pftf/RPi3#readme RPi3] are found on that project's github. From there the fedora installer DVD [ISO https://getfedora.org/] for aarch64 should be used, or the fedora process for setting up PXE/HTTP boot.
 
== Prerequisites ==
 
* A Raspberry Pi 3-series device or 4.
* Good quality SD Card ([http://elinux.org/RPi_SD_cards eLinux] hosts a compatibility list)
* Good quality SD Card ([http://elinux.org/RPi_SD_cards eLinux] hosts a compatibility list)
* HDMI Monitor or TV, a USB keyboard and mouse
* HDMI Monitor or TV, a USB keyboard and mouse
* A decent power supply. You'll want at least 2A for the RPi2 and 2.5A for the RPi3 [https://www.raspberrypi.org/help/faqs/#power details here]
* A decent power supply. You'll want at least 2.5A. [https://www.raspberrypi.org/documentation/faqs/#pi-power details here].


For preparation of the SD card:
For preparation of the SD card:
Line 22: Line 30:
* SD card reader
* SD card reader


= Downloading the Fedora ARM image =
== Downloading the Fedora ARM image ==


As the support for the Raspberry Pi is now available with Fedora 25. Please read the FAQ for the current status of various features.
Official images for the supported Raspberry Pi devices can be found at the usual location [https://getfedora.org/ Get Fedora]. The various different options are linked from the various Edition, Spins, Labs and other artifact pages.


Fedora 25 images can be downloaded here:
== Preparing the SD card ==
* [https://download.fedoraproject.org/pub/fedora/linux/releases/25/Workstation/armhfp/images/Fedora-Workstation-armhfp-25-1.3-sda.raw.xz Fedora Workstation 25]
* [https://download.fedoraproject.org/pub/fedora/linux/releases/25/Server/armhfp/images/Fedora-Server-armhfp-25-1.3-sda.raw.xz Fedora Server 25]
* [https://download.fedoraproject.org/pub/fedora/linux/releases/25/Spins/armhfp/images/Fedora-Minimal-armhfp-25-1.3-sda.raw.xz Fedora 25 Minimal]
* [https://download.fedoraproject.org/pub/fedora/linux/releases/25/Spins/armhfp/images/ Fedora 25 Spins]


= Preparing the SD card =
You can quite easily prepare the image on the SD card on Fedora or any Linux distribution, MacOS or Windows. The default settings will provide the user interface on a HDMI monitor with keyboard and mouse support. If you wish to have output over a serial console please see [[#How_do_I_use_a_serial_console.3F | Section in the FAQ]].


You can quite easily prepare the image on the SD card on Fedora or any Linux distribution, MacOS or Windows. The default settings will provide the user interface on a HDMI monitor with keyboard and mouse support. If you wish to have output over a serial console please see [[User:Pbrobinson/RPi#How_do_I_use_a_serial_console.3Fthe | Section in the FAQ]].
=== Fedora or other Linux Distributions ===


== Fedora or other Linux Distributions ==
==== Scripted ====
===Scripted===
To install using arm-image-installer:
* Use the fedora-arm-installer
To install arm-image-installer:
<pre>
<pre>
dnf install -y fedora-arm-installer
dnf install -y arm-image-installer
</pre>
</pre>


Line 47: Line 49:
<pre>
<pre>
$ sudo arm-image-installer
$ sudo arm-image-installer
[sudo] password for USER:


Usage: arm-image-installer <options>
Usage: arm-image-installer <options>
Line 60: Line 61:
   --resizefs     - Resize root filesystem to fill media device
   --resizefs     - Resize root filesystem to fill media device
   --addconsole    - Add system console to extlinux.conf
   --addconsole    - Add system console to extlinux.conf
  --addkey=        - /path/to/ssh-public-key


Example: arm-image-installer --image=Fedora-Rawhide.xz --target=Bananapi --media=/dev/mmcblk0
Example: arm-image-installer --image=Fedora-Rawhide.xz --target=Bananapi --media=/dev/mmcblk0


$ sudo arm-image-installer --image=Fedora-IMAGE-NAME.raw.xz --target=none --media=/dev/XXX
For list of supported boards please check SUPPORTED-BOARDS file.
</pre>
</pre>


===Manual===
For the Raspberry Pi 3 or 3+ use <pre>--target=rpi3</pre>, and for the Raspberry Pi 4 use <pre>--target=rpi4</pre>.
<pre> xzcat Fedora-IMAGE-NAME.raw.xz | sudo dd status=progress bs=4M of=/dev/XXX # Location of your media (will be sdX or mmcblkX depending on hardwae)</pre>


== MacOS ==
==== Manual ====
<pre> xzcat Fedora-IMAGE-NAME.raw.xz | sudo dd status=progress bs=4M of=/dev/XXX # Location of your media (will be sdX or mmcblkX depending on hardware)</pre>
 
=== MacOS ===


The Raspberry Pi foundation provides some nice instructions for image copying using a Mac [https://www.raspberrypi.org/documentation/installation/installing-images/mac.md here].  Simply replace any image file references with the name and path of the image downloaded in the step above.
The Raspberry Pi foundation provides some nice instructions for image copying using a Mac [https://www.raspberrypi.org/documentation/installation/installing-images/mac.md here].  Simply replace any image file references with the name and path of the image downloaded in the step above.


== Microsoft Windows ==
=== Microsoft Windows ===


The Raspberry Pi foundation provides some nice instructions for image copying using a Windows [https://www.raspberrypi.org/documentation/installation/installing-images/windows.md here].  Simply replace any image file references with the name and path of the image downloaded in the step above.
The Raspberry Pi foundation provides some nice instructions for image copying using a Windows [https://www.raspberrypi.org/documentation/installation/installing-images/windows.md here].  Simply replace any image file references with the name and path of the image downloaded in the step above.


== Resizing the root partition ==
=== Resizing the root partition ===


The root partition is shrunk to the smallest size possible to ensure a small download. You currently need to resize it manually. The plan is to do it automatically before Fedora 25 is released.
The root partition is shrunk to the smallest size possible to ensure a small download. You currently need to resize it manually. Ideally we would like this to happen automatically (great community project idea!).
==== Resize before first boot ====


=== Resize before first boot ===
The easiest way to do this is using the arm-image-installer detailed above, otherwise before boot on a Linux system is with gparted:
 
The easiest way to do this before boot on a Linux system is with gparted:


<pre>gparted /dev/XXX</pre>
<pre>gparted /dev/XXX</pre>


=== Resize after initial-setup ===
==== Resize after initial-setup ====


The other mechanism for doing it is once you've booted the Raspberry Pi and completed the initial setup to create accounts.
The other mechanism for doing it is once you've booted the Raspberry Pi and completed the initial setup to create accounts.


<pre>
<pre>
# enlarge the 4th partition (this example uses mmcblk0)
# enlarge the 3rd partition (this example uses mmcblk0)
growpart /dev/mmcblk0 4
growpart /dev/mmcblk0 3
# grow the fileystem to fill the available space
# grow the volume to take up the rest of the disk
resize2fs /dev/mmcblk0p4
resize2fs /dev/mmcblk0p3
# for the server image (which uses xfs)
# resize root partition for the armhfp server image (which uses xfs)
xfs_growfs /dev/mmcblk0p4
xfs_growfs -d /
 
# Steps for the AArch64 Server image
 
# enlarge the 3rd partition (this example uses mmcblk0)
growpart /dev/mmcblk0 3
# resize the physical volume
pvresize /dev/mmcblk0p3
# extend the root filesystem to take up the space just added to the volume that it is in
lvextend -l +100%FREE /dev/fedora_fedora/root
# resize root partition for the server image (which uses xfs)
xfs_growfs -d /
</pre>
</pre>


= Booting Fedora on the Raspberry Pi for the first time =
== Booting Fedora on the Raspberry Pi for the first time ==


* Insert the SD card into the Raspberry Pi.
* Insert the SD card into the Raspberry Pi.
Line 109: Line 123:
* You should be presented with a login prompt or a getting started guide (depending on which Desktop/SPIN you're using).
* You should be presented with a login prompt or a getting started guide (depending on which Desktop/SPIN you're using).


= Applying updates and installing software =
== Applying updates and installing software ==


There are no special ways or procedures necessary to install or update the software so you just use standard Fedora installation and update mechanisms such as dnf, gnome-software or any of the other GUI update systems as supported in the various desktop environments.
There are no special ways or procedures necessary to install or update the software so you just use standard Fedora installation and update mechanisms such as dnf, gnome-software or any of the other GUI update systems as supported in the various desktop environments.


= Getting help and reporting issues =
== Getting help and reporting issues ==


So where can you get help if it’s not working? The usual Fedora support forums are:
So where can you get help if it’s not working? The usual Fedora support forums are:
Line 119: Line 133:
* [https://ask.fedoraproject.org/ Ask Fedora]
* [https://ask.fedoraproject.org/ Ask Fedora]
* [https://lists.fedoraproject.org/admin/lists/arm%40lists.fedoraproject.org/ Fedora ARM mailing list]
* [https://lists.fedoraproject.org/admin/lists/arm%40lists.fedoraproject.org/ Fedora ARM mailing list]
* [https://fedoraproject.org/wiki/IRC IRC via the #fedora-arm channel on Freenode]
* [https://matrix.to/#/#arm:fedoraproject.org Fedora Chat on Matix via the #arm:fedoraproject.org room]
== Frequently Asked Questions ==
 
=== Why do I get a rainbow display when I try and power on my Raspberry Pi? ===
 
There's a number of different reasons you might get rainbow output on the display when you're trying to boot as Raspberry Pi. The three common ones we see are:
* The power supply isn't strong enough. See [[Raspberry_Pi#Prerequisites | Prerequisites]] above.
* There's no OS installed. Check the SD card is properly in place and you've followed the instructions to write out the card.
* Wrong edition of the Raspberry Pi. If you try and use Fedora on a Raspberry Pi 1 or Zero you'll get this as we don't support ARMv6 SoCs.
* Unsupported version of Fedora, eg releases older than Fedora 37 on the RPi 4
 
=== Power Supplies ===


= Frequently Asked Questions =
The biggest single support issue is generally not a powerful enough PSU. The Raspberry Pi 3 Series needs a 2.5A PSU, this is especially important with Fedora where we support higher CPU frequencies which draws more power. PSUs that seemingly worked in the past have been seen to cause issues with Fedora due to this.


=== What desktop environments are supported? ===
=== What desktop environments are supported? ===


Both 3D/2D work out of the box and all desktops as shipped in Fedora should work just fine. There is an open source fully accelerated driver for the Video Core IV GPU.
Both 3D/2D work out of the box on Raspberry Pi 3/4 and most lightweight desktops as shipped in Fedora should work just fine. There is an open source fully accelerated driver for the Video Core IV GPU.


=== Will there be more enhancements to the hardware support ===
=== Will there be more enhancements to the hardware support? ===


Yes. New enhancements will be delivered when, and as soon as, they are ready via the standard Fedora updates mechanism. New significate features will be blogged about as they arrive either via [https://fedoramagazine.org/ Fedora Magazine] or the [http://fedoraplanet.org/ Fedora Planet].
Yes. New enhancements will be delivered when, and as soon as, they are ready via the standard Fedora updates mechanism. New significant features will be blogged about as they arrive either via [https://fedoramagazine.org/ Fedora Magazine] or the [http://fedoraplanet.org/ Fedora Planet].


=== Support for the Raspberry Pi Models A, A+, B (generation 1), Zero and Compute Module ===
=== What about support for the Raspberry Pi Models A/A+, B/B+ (generation 1), Zero/ZeroW and Compute Module? ===


Fedora doesn't support ARMv6 processors. There's been a number of attempts to support these over the years. The current best effort is Pignus based on Fedora 23. More information can be found at [https://pignus.computer the Pignus site]. We will support the new Compute Module 3 based on the same SoC as the Raspberry Pi 3 when it starts to ship.
THESE ARE NOT SUPPORTED!!!


=== When will support for Fedora 24 or 23 arrive? ===
Fedora doesn't, and NEVER will, support ARMv6 processors. There's been a number of attempts to support these over the years, none are currently active.


It likely won't. The small team is focused on the Fedora 25 development version and rawhide to best focus resources. While possible to do there is reasonably significant amount of work to back port all the fixes that have gone into Fedora 25/rawhide back to stable releases. Fedora 25 is [[Releases/25/Schedule | released]] and is already very stable on the Raspberry Pi.
=== What USB devices are supported on the Raspberry Pi? ===
 
=== What USB devices are supported on the Raspberry Pi ===


You should be able to use most USB-2 compatible devices that are supported in Fedora on other devices. There are some limitations to the USB bus of the Raspberry Pi hardware as [https://www.raspberrypi.org/documentation/hardware/raspberrypi/usb/README.md documented here].
You should be able to use most USB-2 compatible devices that are supported in Fedora on other devices. There are some limitations to the USB bus of the Raspberry Pi hardware as [https://www.raspberrypi.org/documentation/hardware/raspberrypi/usb/README.md documented here].
Line 145: Line 168:
=== Is the onboard WiFi and Bluetooth supported on the Raspberry Pi 3? ===
=== Is the onboard WiFi and Bluetooth supported on the Raspberry Pi 3? ===


==== Wifi: ====
==== WiFi ====
No currently, there's a number of reasons for this:
 
* Initially the firmware required for the device wasn't redistributable. This was resolved on [http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/commit/?id=c4c07a8d1128d50a5c2885ceea1abbebaa82f820 September 14th] when the firmware landed upstream in the linux-firmware repository!
WiFi on the Raspberry Pi 3-series devices works out of the box with Fedora. WiFi on the Raspberry Pi 4 model B works. WiFi on the Raspberry Pi Zero 2W and Raspberry Pi 400 is currently unsupported.
* The SDIO interface which the WiFi module uses to connect to isn't yet upstream.
 
* Some other support patches are missing.
===== Using Wi-Fi on CLI =====


It initially wasn't a focus due to the inability to redistribute the firmware. With the work now complete for initial support for the overall Pi now complete this will be easy to deliver as a standard Fedora update at some point in the future when the kernel pieces look sane.
To use Wi-Fi on minimal and server images you can configure the device using command line:
<pre>
# list of networks
nmcli device wifi list
# connect
nmcli device wifi connect $SSID --ask
</pre>


==== Bluetooth: ====
==== Bluetooth ====
It's currently untested but as it's attached to a serial port and is accessible it might work. It's only been briefly tested but in practice it tends to crash the entire device so is not currently recommended. Those interested can investigate further and potentially provide more informatin.
Bluetooth works quite well and seems to be quite stable. The device sometimes has a generic bluetooth address but should over all work just fine without any configuration.


For the brave you can test it with this command:
=== Do VLANs work on the onboard wired interface? ===


<pre>hciattach /dev/ttyAMA0 bcm43xx 3000000 noflow -</pre>
Yes, although you might need to tune the interface either with
ethtool -K eth0 rx-vlan-filter off
or something like
nmcli connection modify "Wired connection 1" ethtool.feature-rx-vlan-filter off


=== Why doesn't sound work? ===
=== Does sound work? ===


Support for the sound output via HDMI or though the analog port is not yet supported in the upstream kernel. This is one of the big items on the ToDo list. Audio output via a USB audio interface should work fine.
HDMI audio output is included Fedora however the analog port is not yet supported. Audio output via a USB audio interface should also work fine.


=== Does the add-on camera work? ===
=== Does the camera add-on work? ===


Not currently. There is still ongoing work to support this upstream and add the appropriated media acceleration support.
Yes. You need to ensure you're running bcm283x-firmware from 2019, ensure the latest config.txt is in place (no .rpmnew) and edit /boot/efi/config.txt and adjust the gpu_mem setting to be <b>gpu_mem=80</b>.


=== Does accelerated media decode work? ===
=== Does accelerated media decode work? ===


No. There's no upstream kernel support and it relies on code from a number of kernel subsystems to be supported.
No. There's no upstream kernel support and it relies on code from a number of kernel subsystems to be supported. This is unsupported on all Raspberry Pi platforms 3/4 and Zero 2W.


=== Does HDMI-CEC work? ===
=== Does HDMI-CEC work? ===


Yes. It current is supported using [http://libcec.pulse-eight.com/ libcec] packaged in Fedora.
Yes. It's supported using the upstream CEC support. There's a /dev/cec0 character device, it can be accessed using any application that supports the IR remote using the rc-cec keymap in the v4l-utils package, there's also a cec-ctl util for use via the command line.


=== Are display outputs other than HDMI supported? ===
=== Is the Raspberry Pi Touch Display supported? ===


Work on the official Raspberry Pi Touch Display is ongoing upstream and initial support might land as soon as the 4.9 kernel, being [https://github.com/anholt/linux/issues/8 tracked upstream]. Fedora will enable that support as soon as is reasonable and it is usable. Support for other displays is not currently planned.
Yes.


=== Are the expansion HATs supoorted? ===
=== Is the composite TV out supported? ===


The quick answer here is they are not currently supported.
The support should be present in current versions of the Fedora kernel, but this is untested. Note composite output on the Raspberry Pi 4 is disabled by default for performance reasons; it can be enabled with {{code|enable_tvout=1}} in {{filename|config.txt}}.


The long answer is a lot more complex. Most of the hardware interfaces that are exposed by the 40 pin HAT connector are supported with drivers shipped with Fedora. Drivers for the hardware contained on a lot of the common HATs are also enabled and supported in Fedora. The core means of supporting the HAT add-on boards require the use of device tree overlays. The kernel and the u-boot 2016.09 boot-loader supports the loading over overlays manually. Currently there is no upstream consensus on the means of autoloading these overlays by means of an "overlay manager" (also known as Cape Manager and by numerous other names) by reading the EEPROM ID and loading the appropriate overlay automatically. There's also no consensus on the extensions to the dtc (Device Tree Compiler) to build the binary blob overlays, and no consensus of the exact format of the overlay file. There is now a group of people working to resolve this issue which enable Fedora to better support HATs (Raspberry Pi), Capes (BeagleBone), DIPs (C.H.I.P) and Mezzanine (96boards) before long.
=== Are the expansion HATs supported? ===


The first focus HAT to support will be the official Raspberry Pi Sense HAT. This will be documented using the manual process to build and load the overlay to provide access to the onboard devices as a means of demonstrating how this process works for those wishing to use this manual method in the interim. The link to this documentation will be added here once that is complete.
Yes, most HATs are supported in Fedora- for instructions visit this [[Architectures/ARM/Raspberry_Pi/HATs|page]]. Once you've successfully got your HAT working, please update the wiki with the details and any additional notes.


=== Raspberry Pi 3 aarch64 support ===
=== The use of config.txt ===
The config.txt is only used for basic configuration at the moment. Because of the the use of the opensource vc4 GPU driver most of the video configuration is done within Linux.


The focus for Fedora 25 with the limited time and resources available, was to provide a polished experience with a single disk image for both the Raspberry Pi 2 and 3. At the time the work started it wasn't clear whether the aarch64 kernel support would land upstream in time. The intention is to officially support the Raspberry Pi 3 as an aarch64 device in Fedora 26. There has been significant enabling work in Fedora 25 but there is still quite a bit more work to do to finish the aarch64 support at time of writing.
The configuration of HATs using config.txt is currently unsupported but is being actively worked on.
 
=== Are Device Tree Overlays supported? ===
 
We support Raspberry Pi overlays via the config.txt option the same as the Raspberry Pi OS. Details can be found on the [[Architectures/ARM/Raspberry_Pi/HATs|HAT page]].
 
=== Is GPIO supported? ===
 
GPIO is supported with the use of libgpiod and associated bindings and utilities. RPI.GPIO is not currently supported.
 
=== Is SPI supported? ===
 
Yes, basic SPI is supported. It will need to be enabled using Device Tree.
 
=== Is I2C supported? ===
 
Yes, basic I2C is supported.


=== How do I use a serial console? ===
=== How do I use a serial console? ===


The serial console is disabled by default on the Raspberry Pi 2 and 3 because it requires the device to run at significantly slower speeds. To wire up the USB to TTL adapter follow [https://learn.adafruit.com/adafruits-raspberry-pi-lesson-5-using-a-console-cable/connect-the-lead this guide from Adafruit]. You'll need a 3.3 volt USB to TTL Serial Cable like [https://www.adafruit.com/product/954 this one from Adafruit]
The serial console is disabled by default on the Raspberry Pi because it requires the device to run at significantly slower speeds. To wire up the USB to TTL adapter follow [https://learn.adafruit.com/adafruits-raspberry-pi-lesson-5-using-a-console-cable/connect-the-lead this guide from Adafruit]. You'll need a 3.3 volt USB to TTL Serial Cable like [https://www.adafruit.com/product/954 this one from Adafruit]


To enable the serial console follow the specific steps for the Raspberry Pi 2 or 3 as they both differ slightly:
To enable the serial console follow the specific steps:


==== Raspberry Pi 2: ====
==== Raspberry Pi 3 ====
* inset the micro SD card into a PC
* connect the install media (micro SD card or HDD/SSD over USB) into a PC
* on the VFAT partition edit the config.txt file and uncomment the enable_uart line:
* on the VFAT partition edit the config.txt file and uncomment the enable_uart line:
<pre>enable_uart=1</pre>  
<pre>enable_uart=1</pre>  
* on the boot partition edit the extlinux/extlinux.conf file adding "console=tty0 console=ttyAMA0,115200" to the end of the append line so it looks similar to:
* on the boot partition edit the <i>loader/entries/*-<kernel-version>.aarch64.conf</i> file adding "console=tty0 console=ttyS0,115200" in the "options console" line:
<pre>append ro root=UUID="LARGE UUID STRING OF TEXT" console=tty0 console=ttyAMA0,115200</pre>
<pre>options console=ttyS0,115200 console=tty0 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/root rhgb quiet</pre>
* Safely unmount the micro SD card
* Safely unmount your install media (sdCard or HDD/SSD over USB)
* Insert micro SD into Raspberry Pi, connect serial console, power on
* Insert install media into Raspberry Pi, connect serial console, power on
* <b>Note:</b> in recent versions of <i>arm-image-installer</i> if you specify the option <i>--addconsole</i> the installer will automatically add the above console settings for you on the VFAT and boot partitions.


==== Raspberry Pi 3: ====
=== It waits too long before GRUB ===
* inset the micro SD card into a PC
<pre>lan78xx_eth Waiting for PHY auto negotiation to complete...</pre>
* on the VFAT partition edit the config.txt file and uncomment the enable_uart line:
That happens without ethernet cable plugged in. You can interrupt the waiting by CTRL+C.
<pre>enable_uart=1</pre>  
* on the boot partition edit the extlinux/extlinux.conf file adding "console=tty0 console=ttyS0,115200" to the end of the append line so it looks similar to:
<pre>append ro root=UUID="LARGE UUID STRING OF TEXT" console=tty0 console=ttyS0,115200</pre>
* Safely unmount the micro SD card
* Insert micro SD into Raspberry Pi, connect serial console, power on


[[Category:Raspberry Pi]]
[[Category:Raspberry Pi]]
[[Category:Fedora ARM]]
[[Category:AArch64]]

Latest revision as of 06:13, 6 March 2024

The Raspberry Pi 3 and 4 are supported in in all stable Fedora releases. Please report issues to the ARM mailing list or IRC channel

Introduction

The Raspberry Pi is a credit card-sized ARM based single board computer (SBC). Fedora supports the the Raspberry Pi 3-series of devices including the 3B, 3B+, 3A+, 3CM and 3CM+ and the Raspberry Pi 4 in Fedora 37 and later releases. This documentation describes how to get started, and includes a Frequently Asked Questions (FAQ) about what is supported and what isn't.

Supported Hardware

We currently support the Raspberry Pi 3-series of devices (3B, 3B+, 3A+, CM3, CM3+) and the Raspberry Pi 4-series (4B, 400, CM4, CM4s) and the Zero2W.

Fedora IoT lists the Raspberry Pi 4 as one of its Reference Platforms.

Official support for the Zero 5B is under review.

UEFI support

The Pi Firmware Task Force is working to create a fully featured SystemReady-ES UEFI port for the RPi3 and RPi4. That project is rapidly evolving. As of version 1.5, Fedora 31+ will boot in ACPI mode on the Raspberry Pi 4 with gradually improving device support as one moves to newer kernels. Given a system running a Linux 5.7+ based kernel, the onboard NIC, PCI/XHCI, Graphics, etc, work. RPi3+DT support in the project is quite complete and mature. Firmware install guides for the RPi4 and RPi3 are found on that project's github. From there the fedora installer DVD [ISO https://getfedora.org/] for aarch64 should be used, or the fedora process for setting up PXE/HTTP boot.

Prerequisites

  • A Raspberry Pi 3-series device or 4.
  • Good quality SD Card (eLinux hosts a compatibility list)
  • HDMI Monitor or TV, a USB keyboard and mouse
  • A decent power supply. You'll want at least 2.5A. details here.

For preparation of the SD card:

  • Computer running Windows/MacOS/Linux
  • SD card reader

Downloading the Fedora ARM image

Official images for the supported Raspberry Pi devices can be found at the usual location Get Fedora. The various different options are linked from the various Edition, Spins, Labs and other artifact pages.

Preparing the SD card

You can quite easily prepare the image on the SD card on Fedora or any Linux distribution, MacOS or Windows. The default settings will provide the user interface on a HDMI monitor with keyboard and mouse support. If you wish to have output over a serial console please see Section in the FAQ.

Fedora or other Linux Distributions

Scripted

To install using arm-image-installer:

dnf install -y arm-image-installer

To write the image out use the following:

$ sudo arm-image-installer

Usage: arm-image-installer <options>

   --image=IMAGE    - xz compressed image file name
   --target=TARGET  - target board
   --media=DEVICE   - media device file (/dev/[sdX|mmcblkX])
   --selinux=ON/OFF - Turn SELinux off/on as needed
   --norootpass     - Remove the root password
   -y		    - Assumes yes, will not wait for confirmation
   --version	    - Display version and exit
   --resizefs	    - Resize root filesystem to fill media device
   --addconsole     - Add system console to extlinux.conf
   --addkey=        - /path/to/ssh-public-key

Example: arm-image-installer --image=Fedora-Rawhide.xz --target=Bananapi --media=/dev/mmcblk0

For list of supported boards please check SUPPORTED-BOARDS file.

For the Raspberry Pi 3 or 3+ use

--target=rpi3

, and for the Raspberry Pi 4 use

--target=rpi4

.

Manual

 xzcat Fedora-IMAGE-NAME.raw.xz | sudo dd status=progress bs=4M of=/dev/XXX # Location of your media (will be sdX or mmcblkX depending on hardware)

MacOS

The Raspberry Pi foundation provides some nice instructions for image copying using a Mac here. Simply replace any image file references with the name and path of the image downloaded in the step above.

Microsoft Windows

The Raspberry Pi foundation provides some nice instructions for image copying using a Windows here. Simply replace any image file references with the name and path of the image downloaded in the step above.

Resizing the root partition

The root partition is shrunk to the smallest size possible to ensure a small download. You currently need to resize it manually. Ideally we would like this to happen automatically (great community project idea!).

Resize before first boot

The easiest way to do this is using the arm-image-installer detailed above, otherwise before boot on a Linux system is with gparted:

gparted /dev/XXX

Resize after initial-setup

The other mechanism for doing it is once you've booted the Raspberry Pi and completed the initial setup to create accounts.

# enlarge the 3rd partition (this example uses mmcblk0)
growpart /dev/mmcblk0 3
# grow the volume to take up the rest of the disk
resize2fs /dev/mmcblk0p3
# resize root partition for the armhfp server image (which uses xfs)
xfs_growfs -d /

# Steps for the AArch64 Server image

# enlarge the 3rd partition (this example uses mmcblk0)
growpart /dev/mmcblk0 3
# resize the physical volume
pvresize /dev/mmcblk0p3
# extend the root filesystem to take up the space just added to the volume that it is in
lvextend -l +100%FREE /dev/fedora_fedora/root
# resize root partition for the server image (which uses xfs)
xfs_growfs -d /

Booting Fedora on the Raspberry Pi for the first time

  • Insert the SD card into the Raspberry Pi.
  • Make sure you have a keyboard, mouse, network cable and monitor connected.
  • Power on the Raspberry Pi.
  • You will see Fedora booting and eventually the "Initial setup wizard" will appear.
  • Follow the wizard to set language, timezone and create users.
  • You should be presented with a login prompt or a getting started guide (depending on which Desktop/SPIN you're using).

Applying updates and installing software

There are no special ways or procedures necessary to install or update the software so you just use standard Fedora installation and update mechanisms such as dnf, gnome-software or any of the other GUI update systems as supported in the various desktop environments.

Getting help and reporting issues

So where can you get help if it’s not working? The usual Fedora support forums are:

Frequently Asked Questions

Why do I get a rainbow display when I try and power on my Raspberry Pi?

There's a number of different reasons you might get rainbow output on the display when you're trying to boot as Raspberry Pi. The three common ones we see are:

  • The power supply isn't strong enough. See Prerequisites above.
  • There's no OS installed. Check the SD card is properly in place and you've followed the instructions to write out the card.
  • Wrong edition of the Raspberry Pi. If you try and use Fedora on a Raspberry Pi 1 or Zero you'll get this as we don't support ARMv6 SoCs.
  • Unsupported version of Fedora, eg releases older than Fedora 37 on the RPi 4

Power Supplies

The biggest single support issue is generally not a powerful enough PSU. The Raspberry Pi 3 Series needs a 2.5A PSU, this is especially important with Fedora where we support higher CPU frequencies which draws more power. PSUs that seemingly worked in the past have been seen to cause issues with Fedora due to this.

What desktop environments are supported?

Both 3D/2D work out of the box on Raspberry Pi 3/4 and most lightweight desktops as shipped in Fedora should work just fine. There is an open source fully accelerated driver for the Video Core IV GPU.

Will there be more enhancements to the hardware support?

Yes. New enhancements will be delivered when, and as soon as, they are ready via the standard Fedora updates mechanism. New significant features will be blogged about as they arrive either via Fedora Magazine or the Fedora Planet.

What about support for the Raspberry Pi Models A/A+, B/B+ (generation 1), Zero/ZeroW and Compute Module?

THESE ARE NOT SUPPORTED!!!

Fedora doesn't, and NEVER will, support ARMv6 processors. There's been a number of attempts to support these over the years, none are currently active.

What USB devices are supported on the Raspberry Pi?

You should be able to use most USB-2 compatible devices that are supported in Fedora on other devices. There are some limitations to the USB bus of the Raspberry Pi hardware as documented here.

Is the onboard WiFi and Bluetooth supported on the Raspberry Pi 3?

WiFi

WiFi on the Raspberry Pi 3-series devices works out of the box with Fedora. WiFi on the Raspberry Pi 4 model B works. WiFi on the Raspberry Pi Zero 2W and Raspberry Pi 400 is currently unsupported.

Using Wi-Fi on CLI

To use Wi-Fi on minimal and server images you can configure the device using command line:

# list of networks
nmcli device wifi list
# connect
nmcli device wifi connect $SSID --ask

Bluetooth

Bluetooth works quite well and seems to be quite stable. The device sometimes has a generic bluetooth address but should over all work just fine without any configuration.

Do VLANs work on the onboard wired interface?

Yes, although you might need to tune the interface either with

ethtool -K eth0 rx-vlan-filter off

or something like

nmcli connection modify "Wired connection 1" ethtool.feature-rx-vlan-filter off

Does sound work?

HDMI audio output is included Fedora however the analog port is not yet supported. Audio output via a USB audio interface should also work fine.

Does the camera add-on work?

Yes. You need to ensure you're running bcm283x-firmware from 2019, ensure the latest config.txt is in place (no .rpmnew) and edit /boot/efi/config.txt and adjust the gpu_mem setting to be gpu_mem=80.

Does accelerated media decode work?

No. There's no upstream kernel support and it relies on code from a number of kernel subsystems to be supported. This is unsupported on all Raspberry Pi platforms 3/4 and Zero 2W.

Does HDMI-CEC work?

Yes. It's supported using the upstream CEC support. There's a /dev/cec0 character device, it can be accessed using any application that supports the IR remote using the rc-cec keymap in the v4l-utils package, there's also a cec-ctl util for use via the command line.

Is the Raspberry Pi Touch Display supported?

Yes.

Is the composite TV out supported?

The support should be present in current versions of the Fedora kernel, but this is untested. Note composite output on the Raspberry Pi 4 is disabled by default for performance reasons; it can be enabled with {{{1}}} in config.txt.

Are the expansion HATs supported?

Yes, most HATs are supported in Fedora- for instructions visit this page. Once you've successfully got your HAT working, please update the wiki with the details and any additional notes.

The use of config.txt

The config.txt is only used for basic configuration at the moment. Because of the the use of the opensource vc4 GPU driver most of the video configuration is done within Linux.

The configuration of HATs using config.txt is currently unsupported but is being actively worked on.

Are Device Tree Overlays supported?

We support Raspberry Pi overlays via the config.txt option the same as the Raspberry Pi OS. Details can be found on the HAT page.

Is GPIO supported?

GPIO is supported with the use of libgpiod and associated bindings and utilities. RPI.GPIO is not currently supported.

Is SPI supported?

Yes, basic SPI is supported. It will need to be enabled using Device Tree.

Is I2C supported?

Yes, basic I2C is supported.

How do I use a serial console?

The serial console is disabled by default on the Raspberry Pi because it requires the device to run at significantly slower speeds. To wire up the USB to TTL adapter follow this guide from Adafruit. You'll need a 3.3 volt USB to TTL Serial Cable like this one from Adafruit

To enable the serial console follow the specific steps:

Raspberry Pi 3

  • connect the install media (micro SD card or HDD/SSD over USB) into a PC
  • on the VFAT partition edit the config.txt file and uncomment the enable_uart line:
enable_uart=1
  • on the boot partition edit the loader/entries/*-<kernel-version>.aarch64.conf file adding "console=tty0 console=ttyS0,115200" in the "options console" line:
options console=ttyS0,115200 console=tty0 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/root rhgb quiet
  • Safely unmount your install media (sdCard or HDD/SSD over USB)
  • Insert install media into Raspberry Pi, connect serial console, power on
  • Note: in recent versions of arm-image-installer if you specify the option --addconsole the installer will automatically add the above console settings for you on the VFAT and boot partitions.

It waits too long before GRUB

lan78xx_eth Waiting for PHY auto negotiation to complete...

That happens without ethernet cable plugged in. You can interrupt the waiting by CTRL+C.