$ append ro root=UUID="LARGE UUID STRING OF TEXT" console=tty0 console=ttyAMA0,115200
$ append ro root=UUID="LARGE UUID STRING OF TEXT" console=tty0 console=ttyS0,115200
$ enable_uart=1
$ nmcli device wifi list
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.
Are Device Tree Overlays supported?
Are the expansion HATs supported?
Bluetooth works and is stable. The device sometimes has a generic bluetooth address but should work without any configuration.
Common causes of the rainbow display include:
Does accelerated media decode work?
Does HDMI-CEC work?
Does sound work?
Does the add-on camera work?
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.
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#*.
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].
Fedora on Raspberry Pi: Frequently Asked Questions
For Fedora users, see: <<installing-fedora-on-a-raspberry-pi-using-the-fedora-arm-installer_{context}>>.
For macOS users, see: <<installing-fedora-on-a-raspberry-pi-for-macos-users_{context}>>.
For Microsoft Windows users, see: <<installing-fedora-on-a-raspberry-pi-for-microsoft-windows-users_{context}>>.