20200218 F32 Workstation worked (earliest I could see), 20200302 didn't boot. Happy to binary chop to help find breaking change.
On Tue, 3 Mar 2020 at 20:12, Paul Whalen <pwhalen@xxxxxxxxxx> wrote:
Hi Steve,
----- Original Message -----
> On 3/3/20 1:12 PM, Peter Robinson wrote:
> > On Tue, Mar 3, 2020 at 5:56 PM Steven A. Falco <stevenfalco@xxxxxxxxx>
> > wrote:
> >>
> >> On 3/3/20 9:38 AM, Paul Kennedy wrote:
> >>> I've just tried the latest F32 and Rawhide workstation images, but
> >>> neither successfully booted for me. Both hung after eth0 came up, then
> >>> sat for several minutes before logging about dracut timeouts and then a
> >>> recovery shell (mouse and keyboard never worked). I've seen that someone
> >>> had success with a
> >>> Fedora-Workstation-Rawhide-20200110.n.0.aarch64.raw.xz image - has
> >>> anyone successfully booted from anything newer?
> >>
> >> The new images do seem to be broken. I just tried the latest one, and as
> >> you have seen, the boot process hangs at the Ethernet initialization
> >> point.
> >
> > Kernel or firmware stage? The firmware stage is slow but it does go
> > through.
>
> I just tried Fedora-Minimal-Rawhide-20200302.n.1.aarch64.raw.xz and it worked
> properly. However, Fedora-Workstation-Rawhide-20200302.n.1.aarch64.raw.xz
> has a problem, as shown by the attached session.log file. I let it run for
> a long period of time, and after 5 or 10 minutes it wound up at a dracut
> emergency prompt. Please note that this was a fresh install - the only
> thing I changed was to enable the console uart in config.txt so I could log
> the output.
We're a few weeks out from Fedora 32 Beta, so Rawhide is getting very little
attention right now. Both of these are pre-release as well, so issues are
somewhat expected until GA.
The last nominated nightly was 20200225.n.0, I tested both Minimal and
Workstation images for AArch64 and they should boot as expected.
Paul
>
> >> I also tried Fedora-Minimal-Rawhide-20200214.n.1.aarch64.raw.xz, which is
> >> the latest one that I have saved, and it boots, but it won't let me log
> >> in on the console. I think that is because plymouth is fighting with
> >> agetty.
> >>
> >> I do have an RPi4 running 64-bit Fedora pretty well, including a KDE
> >> desktop. But I started with an earlier image, and it took a lot of
> >> fiddling around to get there.
> >>
> >> I have another RPi4 running Manjaro, and it provides a good 64-bit
> >> experience right out of the box. You might want to try that until
> >> "Fedora on RPi4" matures.
> >
> > Other distros are off topic for the list, please keep discussion to
> > topic, if you wish to discuss them there's other forums.
>
> Sorry - I'll use private email in future.
>
> Steve
>
>
>
> _______________________________________________
> arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
> 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://lists.fedoraproject.org/archives/list/arm@xxxxxxxxxxxxxxxxxxxxxxx
>
_______________________________________________
arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
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://lists.fedoraproject.org/archives/list/arm@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________ arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx 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://lists.fedoraproject.org/archives/list/arm@xxxxxxxxxxxxxxxxxxxxxxx
