I've copied the Fedora arm list, please email the list or post on the
Fedora forumus in the future, it allows others to reply as well as
learn from replied.
On Mon, Nov 27, 2023 at 12:06 PM René Kummer <renku(a)gmx.de> wrote:
> Dear Peter Robinson,
> I read your post on the internet
> I am using fedora 38 on my Raspberry Pi4.
> I would say I like it running fedora on my Pi.
> It fits all my needs up to now except one thing.
> I wanted to use the GPIO ports but I can't figure out how to do so.
> So, the first step was trying to install pigpio library via dnf. But
> there seem to be no such package.
> Mhh I ended up confused and not knowing how to install pigpio.
> The next step was to compile pigpio library by my own, that was also not
TBH I had never heard of pigpio until you just mentioned it now.
> My question is, is it possible to use the GPIO Ports with fedora
> workstation 38.
The main way we support GPIO on any device in Fedora is via the gpiod
character interface: /dev/gpiochip*
The main userspace libaries for this is libgpiod and python3-libgpiod
but anything that supports the kernel gpiod character interfaces
The problem with a lot of the RPi specific interfaces for GPIO is that
the RPi has uses an old deprecated GPIO interface with their own
custom set of patches on top. We don't support those.
> The pigpio library would be a good choice in my humble opinion, but if
> it is not supported, could you tell me a system package or a way for
> using GPIO?
> So I tried my best to address the issue in English.
> I look forward to getting a response :)
> So have a nice day.
> Best regards
> beste Grüße René Kummer
did anyone succeed booting a FriendlyElec NanoPC-T6? Since there was some success report with Radxa Rock 5B recently, I was hoping that the NanoPC-T6 wouldn't be too different.
So, I tried CoreOS 40 with EDK2 (https://github.com/edk2-porting/edk2-rk3588) and the Linux 6.7-rc2 rk3588-nanopc-t6 device tree placed in the ESP. While ACPI didn't want to boot at all, the device tree boot at least spits out some more logs. However, the system just abruptly disappears in the end: https://pastebin.com/zqs7nQ8L
I also tried Fedora 40 (Minimal), but that runs into a CPU lockup: https://pastebin.com/aafvP6du
In both cases the OS image was copied to eMMC while EDK2 was on an SD card.
Any ideas why the NanoPC-T6 doesn't want to boot?
All of the Arm disk images use initial-setup to configure the image.
There would need to a concrete plan on how to manage the transition to
On Tue, Nov 21, 2023 at 6:35 AM Jiri Konecny <jkonecny(a)redhat.com> wrote:
> Hello everyone,
> We (anaconda team) are considering discontinuation of the Anaconda's
> Initial Setup tool, which is not related to Gnome Initial Setup. Here
> is a list of the reasons:
> * The relationship between the installer and the Initial Setup is very
> fragile. It is easy to break the Initial Setup by changes in the
> installer or break the installer while we are trying to fix the support
> for the Initial Setup. The shared code is complex as a result and it
> complicates development and maintenance of both projects.
> * As we had higher priority items to work on, the codebase is not in an
> ideal state and the upstream repository doesn't even have a proper
> automated CI. Fixing all these issues would take a lot of our resources
> that we would like to spent on improving the installer instead.
> * The Initial Setup tool is unnecessarily complicated. Since it shares
> code with the installer, it has to adapt to many limitations and
> requirements of the installation environment. It doesn't use the full
> potential of the installed system, because the installer can't. It
> postpones all actions until the end of the configuration, because the
> installer has to. It doesn't offer the best user experience for the
> first boot configuration, because it is designed to reuse parts of an
> installer. It drags Anaconda into the installed systems.
> * There are already alternatives: Gnome Initial Setup,
> systemd-firstboot, and preparation for KDE solution of initial setup. So
> the ecosystem changed from the time when Initial Setup was introduced.
> We think that these alternatives are able to give you a better solution.
> Before taking any action, we would like to understand your use-cases to
> find out how we can help you to make the transition smoother and also to
> find out how much time you would need for migration.
> Is Anaconda Initial Setup important for your project or workflow? What
> functionality is absolutely necessary for you? Do you use the text mode
> or the graphical mode? Are you aware of any alternatives? Is there
> anything that would prevent you from migrating to one of the proposed
> alternatives? Also please feel free to share this mail to any relevant
> : https://github.com/rhinstaller/initial-setup
> Best Regards,
> Anaconda team
> devel mailing list -- devel(a)lists.fedoraproject.org
> To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://email@example.com
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
I've recently - and somewhat surprisingly - already got my hands into a Raspberry Pi 5. I would like to contribute to make it supported , as the Pi4 is.
I have extensive Fedora experience, but not with ARM, and how the whole ecosystem works. What would be useful to get started with a test image for the Pi5? Or if that's not yet possible, what information or resources can be of use to get to that points?
I've tried to install Fedora on my Rock 5 without success.
on SD-Card and source from
Board boots up fine but later starting in loop with
350.456154] dracut-initqueue: Warning: ############# Anaconda
installer errors end ###############
[ 352.156835] dracut-initqueue: Warning: dracut-initqueue:
timeout, still waiting for following initqueue hooks:
[ 352.161387] dracut-initqueue: Warning:
/lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2froot.sh: "[ -e
[ 352.164564] dracut-initqueue: Warning:
/lib/dracut/hooks/initqueue/finished/wait_for_disks.sh: "[ "$main_loop"
-ge "10" ]"
[ 352.167716] dracut-initqueue: Warning:
/lib/dracut/hooks/initqueue/finished/wait_for_settle.sh: "[ -f
[ 352.171999] dracut-initqueue: Warning: dracut-initqueue:
starting timeout scripts
[ 352.172610] dracut-initqueue: Warning: ############# Anaconda
installer errors begin #############
[ 352.172852] dracut-initqueue: Warning: #
[ 352.173097] dracut-initqueue: Warning: It seems that the boot
has failed. Possible causes include
[ 352.173296] dracut-initqueue: Warning: missing inst.stage2 or
inst.repo boot parameters on the
[ 352.173537] dracut-initqueue: Warning: kernel cmdline. Please
verify that you have specified
[ 352.173731] dracut-initqueue: Warning: inst.stage2 or inst.repo.
[ 352.173918] dracut-initqueue: Warning: Please also note that
the 'inst.' prefix is now mandatory.
[ 352.174156] dracut-initqueue: Warning: #
[ 352.174354] dracut-initqueue: Warning: #### Installer
errors encountered during boot: ####
[ 352.174543] dracut-initqueue: Warning: #
[ 352.174775] dracut-initqueue: Warning: Reason unknown
[ 352.174970] dracut-initqueue: Warning: #
Full log file: see rock.txt
Has anybody more succcess ?