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 ?
The 2023.10 RC series are now landing in F-39 and rawhide. There's
been the beginnings of a few enhancements.
The first one that is noticeable is a bootmenu during the firmware
init process where it will allow you to select the device/partition
you wish to boot from, with the default selected and the usual time
out. It should make things a little easier for things like
reinstalling off a USB stick for devices that support that sort of
I've done some testing across a bunch of devices, various RPi, the
Pinebook pro and numerous SBCs so I think it should work just fine, at
least be no different than the usual process but I'd like to hear any
Sorry if you get asked this question a lot.
Are there any stable tablets out there running Fedora ARM yet? My wife's Android tablet is on its last legs and she if furious over the spying and lack of control. Xfce would be nice.
I have a Raspberry Pi 4B running Fedora 38 (server edition) that I use
as a little occasional server for random things. Since it doesn't
always have NTP available, I added an RTC module, and added
"dtoverlay=i2c-rtc,ds1307" to /boot/efi/config.txt (no other change);
all is good.
Now I have a short-term need to use it as a desktop, so I put the XFCE
spin on a different uSD card. I made the same edit to config.txt... and
it doesn't work. No RTC.
I've loaded all the Fedora updates, including the firmware with
"rpi-uboot-update", but it still doesn't work. If I swap back to the
"server" uSD card, it sees the RTC.
The only difference I can see is that the original card is 32G and the
new card is 64G (so "SDXC")... would that be an issue to the firmware
Chris Adams <linux(a)cmadams.net>
You know, Fedora Silverblue is available for aarch64, but it is not
provided as a raw image.
As far as I see around, in order to install Silverblue on a Raspberry
Pi, a lot of trickies are needed in order to boot the ISO from an USB
So. I tried to install Fedora IoT, then I added the Silverblue remotes
and rebased the system to it.
Well. It worked. Do you see any contraindications?
I don't remember if it has always been this way.
I was trying to upgrade from Fedora 38 to 39 on a Raspberry.
sudo dnf system-upgrade download --releasever=39
The point is that on the subsequent boot, following
dnf system-upgrade reboot
the operation fails because the signature verification fails, due to
the fact that the date/time of the RPi is incorrect. You know, each
time the RPi is rebooted, it lose the date/time.
So, has it always been this way and I don't remember that? Or in the
past, system-upgrade was performed after the clock was synchronized
with some source?
We are in the process to gather information about probably suitable SBC for Fedora Server
Khadas vim3 is supported, the vim4 uses the same processor family, it it by chance supported by vim3 drivers?
Timezone: CET (UTC+1) / CEST /UTC+2)
Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast
PhD services encompass a range of offerings designed to assist individuals pursuing a Doctor of Philosophy (PhD) degree. These services often include guidance in various stages of the research and academic journey. They may involve research assistance, editing, data analysis, manuscript preparation, and consultation to help PhD candidates navigate the complex process of completing their doctoral studies and research successfully.