// Module included in the following assemblies:
//
// <List assemblies here, each on a new line>

// Base the file name and the ID on the module title. For example:
// * file name: my-reference-a.adoc
// * ID: [id='my-reference-a']
// * Title: = My reference A

// The ID is used as an anchor for linking to the module. Avoid changing it after the module has been published to ensure existing links are not broken.
[id='reference-material_{context}']
// The `context` attribute enables module reuse. Every module's ID includes {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide.
[[sect-frequently-asked-questions]]
= Fedora on Raspberry Pi: Frequently Asked Questions
//In the title of a reference module, include nouns that are used in the body text. For example, "Keyboard shortcuts for ___" or "Command options for ___." This helps readers and search engines find the information quickly.

Frequently asked questions regarding what is supported.

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

Common causes of the rainbow display include:

* Insufficient power supply. See the xref:raspberry-pi-prerequisites[Prerequisites] section at the beginning of this document.

* There's no operating system installed. Check that an operating system was installed and the microSD card was properly inserted into the Raspberry Pi.
  For instructions about Fedora ARM on Raspberry Pi:
** For Fedora users, see: <<installing-fedora-on-a-raspberry-pi-using-the-fedora-arm-installer_{context}>>.
** For users of other Linux distributions, see: <<installing-fedora-on-a-raspberry-pi-for-linux-users_{context}>>.
** For Microsoft Windows users, see: <<installing-fedora-on-a-raspberry-pi-for-microsoft-windows-users_{context}>>.
** For macOS users, see: <<installing-fedora-on-a-raspberry-pi-for-macos-users_{context}>>.

* If you try to use Fedora on a Raspberry Pi 1, Raspberry Pi Zero, or a Raspberry Pi model A, you will receive the rainbow display. This occurs because your Raspberry Pi is not supported (ARMv6 SoCs architectures are not supported).

== What desktop environments are supported?

All desktops as shipped in Fedora should work and both 2D and 3D graphics work out of the box.
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 by the standard Fedora updates mechanism.
New, significant features will be announced by the link:https://fedoramagazine.org/[Fedora Magazine] or the link:http://fedoraplanet.org/[Fedora Planet].

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

These Raspberry Pi models are not supported.

Fedora is not supported on 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 link:https://pignus.computer[the Pignus site].

NOTE: Fedora DOES support the Compute Module 3 based on the same SoC as the Raspberry Pi 3, but *as the previous generation Compute Modules are based on ARMv6 architecture, they are [#.underline]#not supported#*.

== What USB devices are supported on the Raspberry Pi?

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 link:https://www.raspberrypi.org/documentation/hardware/raspberrypi/usb/README.md[documented here].

== Is the onboard Wi-Fi supported on the Raspberry Pi 3?

Wifi on the Raspberry Pi 3-series devices works out of the box with Fedora 29.

*Using Wi-Fi on CLI*

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

* To list available networks:
+
----
$ nmcli device wifi list
----

* To connect to a network:
+
[subs="quotes"]
----
nmcli device wifi connect __$SSID__ --ask
----
+
Where: `_$SSID_` is the network identifier (or name).

== Is the onboard Bluetooth supported on the Raspberry Pi 3?

Bluetooth works and is stable. The device sometimes has a generic bluetooth address but should work without any configuration.

== Does sound work?

HDMI audio output is included with Fedora, however, the analog port is not yet supported.
Audio output using a USB audio interface should work.

== Does the add-on camera work?

Not at this time.
There is still ongoing work to support this upstream and to add the appropriated media acceleration support.

== Does accelerated media decode work?

No.
The upstream kernel does not support the kernel subsystems required for accelerated media decoding.

== Does HDMI-CEC work?

Yes.
Yes. It's supported using the new 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` utility for use on the command line.

== Is the Raspberry Pi Touch Display supported?

Work on the official Raspberry Pi Touch Display is ongoing upstream and initial support is provided in the 4.10 kernel, see: link:https://github.com/anholt/linux/issues/8[GitHub: raspberrypi/linux issues - 7" LCD touchscreen not supported].
Fedora will review any missing pieces for support soon.
The touchscreen driver isn't yet released upstream.
Support for other displays is not currently planned.

== Is the composite TV out supported?

The composite TV out is not currently supported in a stable Fedora release but the core support is in the 4.10 kernel.
There is some missing enabling patches which will be added to the Fedora kernel soon.

== Are the expansion HATs supported?

The the expansion HATs are not currently supported.

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.

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.

== The use of config.txt

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

The configuration of HATs using `config.txt` is unsupported but is being actively developed.

== Are Device Tree Overlays supported?

There's basic support for overlays in u-boot and the Linux kernel but an overlay manager is not supported upstream.

== 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.

== Is I2C supported?

Yes, basic I2C is supported.

== Is there Raspberry Pi 3 aarch64 support?

Yes! You can download the aarch64 disk images for the Raspberry Pi 3 link:https://archive.fedoraproject.org/pub/fedora-secondary/releases/[here.]

== 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 link: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 link: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:

*Raspberry Pi 2:*

. Insert the microSD card 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 `extlinux/extlinux.conf` file adding `console=tty0 console=ttyAMA0,115200` to the end of the append line so it looks similar to:
+
----
$ append ro root=UUID="LARGE UUID STRING OF TEXT" console=tty0 console=ttyAMA0,115200
----
+
. Safely unmount the microSD card
. Insert microSD into Raspberry Pi, connect serial console, power on

*Raspberry Pi 3:*

. Insert the microSD card 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 `extlinux/extlinux.conf` file adding: `console=tty0 console=ttyS0,115200` to the end of the append line so it looks similar to:
+
----
$ append ro root=UUID="LARGE UUID STRING OF TEXT" console=tty0 console=ttyS0,115200
----
+
. Safely unmount the microSD card
. Insert microSD into Raspberry Pi, connect serial console, power on
