everytime I boot my Raspi I have to wait a few minutes till the kernel
start to boot.
Last line is:
genet@7d580000 Waiting for PHY auto negtiation to complete
there are more then 150 dots, then the kernel starts to boot.
Is there any option/config to modify that behavior? see screenshot
I have pushed out first batch of Fedora CoreOS images for
non-x86_64. You can run it on your own locally, both resulting images
and even rebuild them on your own. Please note those images are
unofficial, built outside of Fedora infrastructure.
Place to grab them is
https://fedorapeople.org/groups/fcos-images/builds/. Quick start
information are present in
https://fedorapeople.org/groups/fcos-images/README based on the official
Blog post format of them is pending release on Fedora community blog. I
would much appreciate any feedback and testing.
More onto the "boring" technical details, if you are user you can skip
rest of the email.
I have been working on building Fedora CoreOS for non-86_64
architectures for several past months. I'm currently in stage that most
of the basic building is working along with kola tests for QEMU target.
I'm also running nightly builds of the CoreOS Assembler container in
Jenkins and push it in to quay.io and docker hub(not yet manifested, due
to some tools issues).
Along with that I do build of FCOS. I still manually push images on to
the fedorapeople.org, I would like to change that eventually.
There is slight deviation on ppc64le as due to some bugs in virt stack,
I have to use more recent qemu&co for coreos-assembler image, that has
AFAIK no impact on the resulting images and slightly relaxed filtered
out packages on s390x(initscripts, config issue pending).
With this announcement I would like to start discussion on how to bring
all of this on the the official Fedora infrastructure and get official
multi-arch builds of FCOS out.
I think that coreos-assembler images is best place to start. Move build
of it from quay to the FCOS Jenkins and source HW for the FCOS Jenkins
instance so we can run the build on all arches and push out the results
manifest listed to the chosen container repositories.
I'm looking forward to your feedback. Thanks to all in Fedora CoreOS for
I recently got an ODROID-N2 but forgot to first check if it was possible
to run recent linux distros on it.
I am happy with Fedora on my raspberry pi 4, so that would be my first
choice. I now see that the N2 is not support and that booting it
requires a few binary blobs:
Is that a no go for fedora or are early boot blobs like that acceptable?
What package would I have to add the above build instructions to?