引言
树莓派是一块信用卡大小、基于 ARM 的单板计算机（SBC）。Fedora 从 25 Beta 及更新的版本中开始原生支持树莓派 2 代和 3 代 B 型，无需再用第三方内核或脚本修改官方镜像。本文将介绍如何上手，以及关于支持情况会有哪些常见问题（FAQ）等。
支持的硬件
目前只支持树莓派 2 代和 3 代 B 型。
前期准备
- 树莓派 2 代和 3 代 B 型
- 高质量的 SD 卡 （eLinux 有一份兼容性列表）
- HDMI 显示器或电视，一副 USB 键盘和鼠标
- 合适的供电装置。 树莓派 2 代建议至少 2A， 3 代建议至少 2.5A。 详情请访问 [1]
制备 SD 卡还需要：
- 一台运行 Windows 或 macOS 或 Linux 系统的电脑
- SD 读卡器
下载 Fedora ARM 镜像
Fedora 25 已经原生支持树莓派，关于目前的特性请阅读 FAQ 。
Fedora 25 镜像可以从这里下载：
制备 SD 卡
你可以很容易地在 Fedora 或其他 Linux 发行版，或者 macOS 、Windows 上将镜像写入 SD 卡中。默认设置会提供 HDMI 显示器上的用户可视界面和对键盘鼠标的支持。如果你想输出到串行控制台，请参考 Section in the FAQ.
Fedora 或其他 Linux 发行版
脚本化
- 使用 fedora-arm-installer
安装 arm-image-installer:
dnf install -y fedora-arm-installer
按照如下操作写入镜像：
$ 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.
手动
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)
macOS
树莓派基金会提供了一些友好的说明，会指导你如何使用 macOS 写入镜像。 你只需简单地替换步骤中的文件路径和文件名即可。
微软 Windows
树莓派基金会提供了一些友好的说明，会指导你如何使用 Windows 写入镜像。 你只需简单地替换步骤中的文件路径和文件名即可。
调整 root 分区大小
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.
Resize before first boot
The easiest way to do this 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 4th partition (this example uses mmcblk0) growpart /dev/mmcblk0 4 # grow the fileystem to fill the available space resize2fs /dev/mmcblk0p4 # for the server image (which uses xfs) xfs_growfs /dev/mmcblk0p4
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.
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.
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 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. The current best effort is Pignus based on Fedora 23. More information can be found at 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.
Will Fedora 24 be supported?
No. The small team is focused on the Fedora 25 release 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 released and is already very stable 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 documented here.
Is the onboard WiFi and Bluetooth supported on the Raspberry Pi 3?
Wifi:
Wifi on the Raspberry Pi 3 is supported in Fedora 26 Alpha (4.11 rc3 kernel).
There's currently a file we can't currently redistribute you'll need to retrieve. This can be done either post first boot using onboard ethernet or when setting up the SD card. The command needed when running from a Raspberry Pi 3 is as follows. Once retrieved you just need to reboot and WiFi should be avaialble.
sudo curl https://raw.githubusercontent.com/RPi-Distro/firmware-nonfree/master/brcm80211/brcm/brcmfmac43430-sdio.txt -o /lib/firmware/brcm/brcmfmac43430-sdio.txt
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.
For the brave you can test it with this command:
hciattach /dev/ttyAMA0 bcm43xx 3000000 noflow -
Does sound work?
Initial support for HDMI audio output is in Fedora 26 Alpha (4.11rc3) though the analog port is not yet supported. Audio output via a USB audio interface should also work fine.
Does the add-on camera work?
Not currently. There is still ongoing work to support this upstream and add the appropriated media acceleration support.
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.
Does HDMI-CEC work?
Yes. It current is supported using libcec packaged in Fedora.
Is the Raspberry Pi Touch Display supported?
Work on the official Raspberry Pi Touch Display is ongoing upstream and initial support has landed in the 4.10 kernel, being tracked upstream. Fedora will review any missing pieces for support soon. The touchscreen driver isn't yet releases 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 has landed upstream in the 4.10 kernel. There's some missing enabling patches currently which we will add to the Fedora kernel soon.
Are the expansion HATs supoorted?
The quick answer here is they 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.
Are Device Tree Overlays supported?
There's basic support for overlays in u-boot and the linux kernel but an overlay manager isn't yet upstream. There's
Is GPIO supported?
GPIO isn't supported well as they need to be mapped with Device Tree overlays. This will be improved in the F-25 cycle, and in Fedora 26.
Is SPI supported?
Yes, basic SPI is supported.
Is I2C supported?
Yes, basic I2C is supported.
Raspberry Pi 3 aarch64 support
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.
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 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 for the Raspberry Pi 2 or 3 as they both differ slightly:
Raspberry Pi 2:
- inset the micro SD 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 micro SD card
- Insert micro SD into Raspberry Pi, connect serial console, power on
Raspberry Pi 3:
- inset the micro SD 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 micro SD card
- Insert micro SD into Raspberry Pi, connect serial console, power on