I have created an image using. fedora-arm-image-installer --image=Fedora-Minimal-armhfp-24-20160610.n.0-sda.raw.xz --target=Cubieboard --media=/dev/sdb --selinux=OFF --resizefs --addconsole --norootpass but images stucks in initial setup and I had to hit control + C to make it continues to boot. I only discovered that because I have the usb serial cable, rpm -e initial-setup-0.3.40-1.fc24.armv7hl solved it.
I got to the same initial setup problems. Except it being a nuisance, it was a real obstacle. I had 2 places available to connect my board: 1)planned location, where only ethernet cable was available, no monitor, 2)other room with monitor (TV), but no ethernet cable. Initial setup lets you configure everything, yet it does nothing until you complete all steps. BUT if it can't get ethernet online, it considers it incomplete configuration. That means that your only solution is to leave initial setup with nothing configured, despite you entered values for everything. Take sdcard out, put it in a laptop, mount partitions and configure everything manually. That's awful user experience.
(In reply to Michal Hlavinka from comment #1) > I got to the same initial setup problems. Except it being a nuisance, it was > a real obstacle. I had 2 places available to connect my board: 1)planned > location, where only ethernet cable was available, no monitor, 2)other room > with monitor (TV), but no ethernet cable. Initial setup lets you configure > everything, yet it does nothing until you complete all steps. BUT if it > can't get ethernet online, it considers it incomplete configuration. That > means that your only solution is to leave initial setup with nothing > configured, despite you entered values for everything. Take sdcard out, put > it in a laptop, mount partitions and configure everything manually. That's > awful user experience. That sounds like bug 1374864 - should be fixed since Fedora 25 Beta 1.1.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.