Fedora CoreOS Raspberry Pi 4 image?

Project Discussion
21

This will be handy to have in a small RPI cluster/home lab.

22

Sometime ago I had CoreOS running on PI 4 - I posted the steps I followed at Headless (mostly) Fedora CoreOS on RPi4 - A Brief How To (updated 9 Oct) - Raspberry Pi Forums. I have not done anything since that post with Fedora CoreOS on RPi4 but intend to do so - soon.

23

Hi All. Iā€™d like to report that we now have documentation for how to run Fedora CoreOS on your Raspberry Pi 4. Please let us know if it works for you or if you find any issues!

3 Likes
25

Hey @theswampire - can you make a new post (so this one doesnā€™t get cluttered) with as much detail as possible?

26

Sure, sorry guys :sweat_smile:

27

I have been using the coreos pi4b image for a single node webserver running django. It works great thanks!

2 Likes
28

Although the topic is quite old I hope I find many FCOS on Pi users here :blush:.

Does any of you the GPIOs?

How do you set the overlays as document for Fedora?
https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi/HATs

29

We have some docs on this in Provisioning Fedora CoreOS on the Raspberry Pi 4 :: Fedora Docs which should help I think.

30

It only says how to activate GPIOs but not how for example deactivate Bluetooth to activate UART.

31

I donā€™t actually use the GPIO on my Pi4 so I could be wrongā€¦

As far as enabling specific things I think you should just be able to install using u-boot from Fedora and then you should just be the same as the docs page you linked to.

32

I was able to install and runs EDK2 but not sure if it is reliable, there some strange side effects.
see Enabling DeviceTree on Pi 4 4 GB causes boot to fail, it hangs at dracut.initqueue

U-boot is still in my agenda, as soon as I can spare time. Currently setting up my home automation on raspberry pi is + docker (and eventually I can close and open my blinds :smile:)

I checked once FCOS for the config.txt. As far as I remember, it doesnā€™t existed (can you confirm?), so I canā€™t do as said there

Activate UART0/1 with the following overlay configuration in /boot/efi/config.txt:

33

The latest stable release of FCOS does not boot with the latest v1.40 EDK2 release with the device tree enabled in the settings. At least on my RPi4, the latest bootable release of EDK2 with the device tree enabled is v1.38.

To access /boot/efi/config.txt on FCOS, you will need to mount the EFI-SYSTEM partition, e.g. sudo mount /dev/mmcblk0p2 /boot/efi.

1 Like
34

Is there a bug report we can follow?

35

I havenā€™t looked closely, but if you like, you can check out Raspberry Pi 4 UEFI Firmware Images Issues.

As has already been suggested several times here and in other threads by a couple of people, I would like to recommend again that you try booting via U-Boot. One of the main reasons for this advice is that U-Boot is used in other Fedora projects and is maintained by the developers and the community, as you can read in the wiki pages.

36

Interestingā€¦ I didnā€™t know that. I just used 1.40 this past weekend and it worked like a charm, but I definitely donā€™t use the GPIO for anything so I didnā€™t follow those steps in the documentation.

@hricky it wold be great if you could open a bug report upstream (or maybe one already exists?) that I could follow.

1 Like
37

As I mentioned in another post, I only use these pins to attach a fan, for which I donā€™t need to enable DeviceTree mode in the EDK2 menu. So the only way I can check if access to GPIO pins is enabled is to follow the docs. Unfortunately, without a HAT attached to the Pi, which I donā€™t have, I can only do this.

Anyhow, Iā€™ll check for a bug report and if there isnā€™t one, Iā€™ll file it. Iā€™ll also look for a HAT for testing.