1

<<TableOfContents: execution failed [list index out of range] (see also the log)>>

About this Howto

This documentation is about using Raspberry Pi Foundation downstream kernel and components from Fedora userspace. The Workstation flavor is recommended for the Raspberry Pi 4 B/400 with >=4GB RAM platform. The Server flavor is usable on starting from Raspberry Pi 3 B/B+.

Kickstart files

Kickstart files are located at https://pagure.io/fork/dwrobel/fedora-kickstarts repository and are based on the original Fedora 41 files with the following modifications:

The modifications in livecd-tools and pykickstart allows to generate image with selected downstream kernel (despite it has lower version) over the upstream one. On a system, all aforementioned repositories are installed with priority=50 option to instruct 'dnf' to choose packages from this repository, rather then Fedora default.

Pre-built images (f41)

The location of pre-generated images for Fedora 41 can be found below:

Flavor

aarch64

Server

image / checksum

Workstation

image / checksum

Pre-built images (f40)

The location of pre-generated images for Fedora 40 can be found below:

Flavor

aarch64

Server

image / checksum

Workstation

image / checksum

Updating Raspberry Pi 4 bootloader EEPROM

Follow the gist available at: https://gist.github.com/dwrobel/266ad5d4e59b05ea26d8bb6725118578.

Raspberry Pi 5

Despite that Rasberry Pi 5 is not supported, images for F41 are reported to work with the following content appended to the /boot/config.txt file: 

[pi5]
# Automatically load overlays for detected cameras
camera_auto_detect=1

# Automatically load overlays for detected DSI displays
display_auto_detect=1

# Enable DRM VC4 V3D driver
dtoverlay=vc4-kms-v3d

# Allows the default turbo-mode clock to be increased from 1.5GHz to 1.8GHz
# Based on https://www.raspberrypi.com/documentation/computers/config_txt.html#arm_boost-raspberry-pi-4-only
arm_boost=1

disable_overscan=1

Note: Basically it is the [pi4] section duplicated as [pi5].

Configurations

Booting from external USB drive

Write the image to the external drive, then mount the filesystem and change root=/dev/mmcblk0p2 to root=/dev/sda2 in the /boot/efi/cmdline.txt.

Note: On the Raspberry Pi 4, you may need to adjust BOOT_ORDER= parameter in order be able to boot from the external drive.

Resizing filesystem

After booting the system, please consider to resize the filesystem. The following example assumes system booted from internal SD card. 

sudo growpart -u on /dev/mmcblk0 2
sudo btrfs filesystem resize max /

Bug Report

CategoryHowto