Description of problem: There are 2 releases of fedoraaarch64 for rpi. 1 - raw image burned with arm-installer 2 - iso 2 - iso is not usable on rpi3b since the board can only boot from sd card 1 - the instructions for using the raw image basically say: Generate an ssh key A) Burn to sdcard and use the --addkey option to include the ssh key on the sdcard B) Boot the sdcard C) the systrm will connect to zezerex (or whatever) and claim a key. This will allow login without a root password - since there is no way to assign one. What actually happens: 1) who knows if the ssh key is actually placed on the card. 2) at boot 2 things happen: a) a message is displayed instructing to go to a web site to claim a key. This is of course impossible. b) the screen is showere with endless identical messages avout some systemd problem. There is no way to capture anynof this. They mention hostname=? And ip=? C) a login prompt is displayed. Since no password has been set, login is impossible Version-Release number of selected component (if applicable): 36 How reproducible: Totally reproducible. Steps to Reproduce: 1. As described - simply follow the instructions in the fedora docs 2. 3. Actual results: As describe. Product is totally unusable on rpi3b Expected results: duh... It should work as described in the fedora-iot web pages. Additional info: I have spent over 8 hours on element fedora-iot and irc #fedora-arm. No one has a clue to why this fails. All offered suggestions only end up at login prompt but, of course, since password has not been set, can't proceed. This distro is either hopelessly broken or ill-conceived. It should be distributed with a root account enabled with either a blank password or one that is a documented default. And, whatever is generating the endless screen-filling steram of error kessages should be corrected.
Moving to the iot component.
additional info: I have tried this with aarch64 and armfhp (raw images) on rpi3b and Fedora-IoT-ostree-x86_64-36-20220618.0.iso in virtualbox on windows. All of the shower the screen with an endles scroll of: [ 18.862125] audit: type=1131 iludit(1663111069.105:222l: pid=l uid=B auid=1291967295 ses=1291967295 subj=system_u :system_r: init_t :s0 msg= 'unit=dbus-parsec comm="systemd" exe="/usr/l ib/systemd/systemd" hostnarne=? addr=? terminal=? res=succes When this is scrolling login is not possible on x86_64. Login is also not possible on rpi because a password has never been set.
What happened to the details that I supplied when I created this report?
IOS Safari does not display this page correctly. Edge does.
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. 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 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.
Thanks for that illuminating reply. It seem unlikely that the issue i describe are relate to the fedora version, rather, they suggest that who ever wrote the install procedure hadn't really ever tried to follow their own recipe. But maybe the point of these disros is not actually to use the?