|
Size: 1862
Comment:
|
← Revision 27 as of 2024-11-18 12:21:30 ⇥
Size: 5032
Comment: Add info about Raspberry Pi 5.
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ## Please edit system and help pages ONLY in the master wiki! ## For more information, please see MoinMoin:MoinDev/Translation. ## page was renamed from Howto/RaspberryPI ##master-page:Unknown-Page ##master-date:Unknown-Date #acl DamianWrobel:read,write,revert AdminGroup:read,write,revert All:read #format wiki #language en |
|
| Line 3: | Line 11: |
| This documentation is about using Raspberry Pi Foundation "downstream kernel" and components on a Fedora (or CentOS) userspace. As with Fedora, this process is compatible with Raspberry Pi 2 and later model (No original Raspberry Pi or Pi Zero support is planned). Unless using a Raspberry Pi 4 with 8Gio of RAM. It's recommended to use the 32bit version over the 64bit. For graphics usage, it's really recommended to have a Raspberry Pi 4 which default to the vc4/v3d driver. |
This documentation is about using Raspberry Pi Foundation [[https://github.com/raspberrypi/linux|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+. |
| Line 8: | Line 14: |
| It's possible to use a Fedora official image as a base, then install additional repositories and adjust configuration. Or use the dedicated images. | == Kickstart files == Kickstart files are located at [[https://pagure.io/fork/dwrobel/fedora-kickstarts||fedora-kickstarts]] repository and are based on the original Fedora 41 files with the following modifications: || component || Repositories || comment || || kernel || [[https://github.com/dwrobel/kernel|spec]] / [[https://copr.fedorainfracloud.org/coprs/dwrobel/kernel-rpi/|copr]] || Downstream kernel || || bcm434xx-firmware || [[https://github.com/dwrobel/bcm434xx-firmware|spec]] / [[https://copr.fedorainfracloud.org/coprs/dwrobel/bcm434xx-firmware-rpi/|copr]] || || || bcm283x-firmware || [[https://github.com/dwrobel/bcm283x-firmware|spec]] / [[https://copr.fedorainfracloud.org/coprs/dwrobel/bcm283x-firmware-rpi/|copr]] || || || pykickstart || [[https://github.com/pykickstart/pykickstart/pull/275|PR]] / [[https://copr.fedorainfracloud.org/coprs/dwrobel/pykickstart/|copr]] || Adds --priority=<priority> || || livecd-tools || [[https://github.com/livecd-tools/livecd-tools/pull/134|PR]] / [[https://copr.fedorainfracloud.org/coprs/dwrobel/livecd-tools/|copr]] || Adds support for repository 'priority' configuration || |
| Line 10: | Line 24: |
| 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. | |
| Line 11: | Line 26: |
| == Using downstream kernel on Fedora == * For Fedora 32+ and CentOS 8: (available as aarch64 only) |
== Pre-built images (f41) == The location of pre-generated images for Fedora 41 can be found below: || Flavor || aarch64 || || Server || [[https://ufile.io/77aq192v|image]] / [[https://ufile.io/561odzlh|checksum]] || || Workstation || [[https://ufile.io/dffuf1vo|image]] / [[https://ufile.io/ub1cilsg|checksum]] || == Pre-built images (f40) == The location of pre-generated images for Fedora 40 can be found below: || Flavor || aarch64 || || Server || [[https://ufile.io/br3bfol9|image]] / [[https://ufile.io/5tvdtl30|checksum]] || || Workstation || [[https://ufile.io/dbt4yr3c|image]] / [[https://ufile.io/mr9cxxto|checksum]] || == Updating Raspberry Pi 4 bootloader EEPROM == Follow the gist available at: [[https://gist.github.com/dwrobel/266ad5d4e59b05ea26d8bb6725118578|https://gist.github.com/dwrobel/266ad5d4e59b05ea26d8bb6725118578]]. == Raspberry Pi 5 == Despite that Rasberry Pi 5 is not supported, images for F41 are [[https://discussion.fedoraproject.org/t/dwrobel-kernel-rpi/17877/25|reported to work]] with the following content appended to the '''/boot/config.txt''' file: |
| Line 14: | Line 46: |
| sudo dnf copr enable dwrobel/kernel-rpi sudo dnf install kernel #you might need to mention the extact kernel to use sudo dnf install kernel-rpi4 # for the raspberry-pi 4 |
[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 [[https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#BOOT_ORDER|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 / |
| Line 19: | Line 78: |
| == Using RPM Fusion RPI Repositories on Fedora == * For Fedora 32 and later: (available as armv7hl and aarch64). {{{ sudo dnf config-manager --add-repo=https://mirrors.rpmfusion.org/free/fedora/rpi/rpmfusion-rpi.repo sudo dnf install raspberrypi-vc-utils raspberrypi-vc-libs }}} == Using dedicated RPI Images == * https://bintray.com/dwrobel/fda-images * https://pagure.io/fork/dwrobel/fedora-kickstarts == Updating the eeprom on RPI4 == {{{ sudo ./rpi-eeprom-update }}} == Known issues == * There is a CMA memory allocation issue with graphics on the Pi3 using vc4, best is to disable vc4 (will be un-accelerated). |
|
| Line 42: | Line 79: |
| * You can report to our bugzilla, see [[ReportingBugs]], please mention using downstream kernel/components. |
Contents
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:
Pre-built images (f40)
The location of pre-generated images for Fedora 40 can be found below:
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
Downstream bugs on the kernel can be reported to https://github.com/raspberrypi/linux/