Description not filled in by author. Very likely personal repository for testing purpose, which you should not use.
This is a companion discussion topic for the original entry at https://copr.fedorainfracloud.org/coprs/dwrobel/kernel-rpi/
This is a companion discussion topic for the original entry at https://copr.fedorainfracloud.org/coprs/dwrobel/kernel-rpi/
How to install these packages on Fedora IoT edition
This is currently not convenient. You must manually download the kernel, kernel-core and kernel-modules packages, then install them with:
rpm-ostree override replace kernel-*.rpm
Later, you must manually apply updates in the same way.
I’m not quite sure that IoT flavour will work with downstream kernel without any changes as downstream kernel is configured by default to run without GRUB or UEFI loader. Alternatively you may look at Overview - fedora-kickstarts - Pagure.io and try to add support for IoT in order to generate the IoT image. So, far I was using those kickstart files only for generating Server and Workstation images.
is there a way to install the appropriate “kernel-devel” for the RPi kernel? I have several dkms modules that cannot be compiled.
– never mind, I worked it out (specify the whole version) 
(I had to link /usr/src/kernels/5.10.32-1.rpi.fc34.aarch64 to /usr/src/kernels/5.10.32-1.rpi4.fc34.aarch64)
The wifi in my Raspberry Pi 400 does not work yet. Maybe another firmware is needed? Thank you very much for this.
Works fine now with the recent firmware update. Thank you!
I tried this on Fedora IoT and unfortunately it does not work for me. rpm-ostree errors out with error: Unable to find kernel (vmlinuz) in /boot or /usr/lib/modules (bootdir=usr/lib/modules/5.10.74-1.rpi.fc34.aarch64). I had a look through the rpm packages in this copr but couldn’t find any kernel image in the kernel, kernel-core nor kernel-modules rpms.
I was under the impression that at least one of those should contain a linux kernel image under /boot/vmlinuz-kernel... . Am I wrong? What am I missing?
OK, my bad. I looked in the wrong place. There is a vmlinux file in the modules directory which will be installed in /boot as expected. It seems however that under rpm-ostree and Fedora IoT the file is expected to be a compressed vmlinuz file instead which is why the rpm-ostree override replace command fails.
I’ve repackaged the RPM and renamed the file(s) and hmac (which may be enough) such that rpm-ostree is pleased and generates the initramfs. Unfortunately I’m now stuck in a initramfs emergency shell. Something seems still to be off
I’ve digged down deeper and found in the emergency logs that apparently the eMMC is not detected at all. The whole block device is just missing. An sd card is detected successfully though. I’m guessing that this might be to some configuration issue in the kernel and it not being targeted at the CM3 / CM4 (aarch64) which are primarily operated with an on-board eMMC storage. I have yet to find out what config options could probably be missing and would appreciate any help finding out what is missing to get this kernel running on CM3 / CM4 (aarch64).
I’ve looked through the configs and compared them with Raspberry Pi OS and Fedora-ARK configs for aarch64 and saw that SDHCI and MMC drivers are present in all of them, so that does not explain this. I’ve also tried to configure the Fedora IoT uboot to use the Fedora IoT dtb directory instead of the kernel provided, but that seems to be the default behavior anyway so I don’t think that the problem arises from the dtb files. It has to be something in the kernel or initramfs
Using F35 workstation/rpmfuions version, Yesterday, I have upgraded to F36, I didn’t that after I disabled livecd-tools.repo and pykickstart.repo, everything seems working okay, but no wired connection in NetworkManager, so I am using WiFI instead, Any suggestions?
For the time being please consider installing kernel from f35 (or any other not compiled by currently broken gcc12).
With the new updated kernel-5.15.32-1.rpi.fc36.aarch64, wired connection is working.
Thank you.
Not sure if anyone else has the same issue, but the latest build (6.1.28-1) breaks wifi.
Trying to start it via nmcli results in a timeout.
I’m using an RPI 4 for reference,
but the latest build (6.1.28-1) breaks wifi.
These works for me (also on RPi 4B) at least in AP mode:
- kernel 6.1.36-1,
- bcm283x-firmware-20230703-1,
- bcm434xx-firmware-20230619-0.b5df30d.
Hello, I have some issue with this kernel package.
After installing this kernel, seems like the kernel isn’t installed properly, as /boot/loader/entries doesn’t update.
This issue is also tracking in another post: F39 - /boot/loader/entries not updating
After installing this kernel, seems like the kernel isn’t installed properly,
It’s not guaranteed that such a combination will work at all.
The downstream kernel is prepared to work with other changes described at [1] .
as
/boot/loader/entriesdoesn’t update.
When installing as per[1] then there is no such /boot/loader directory at all.
Hi, I just wanted to kindly request to enable the repo(s) for Fedora 41 so we can start testing. Thanks in advance 
1 Like
It should be available now.
2 Likes
Does the new release F41 support RPi5?
Please have a look at my answer on reddit [2], it’s still valid.
2 Likes