Raspberry Pi 3B+ fails to boot aarch64 image

[Jan Kratochvil]

Hello,

sorry it may not be really Fedora specific but all images fail to boot for me
except for the plain 32-bit Raspbian.

Fedora 29 aarch64 Workstation fails on:
    https://www.jankratochvil.net/t/rpi3fail.jpg
    [FAILED] Failed to start Avahi mDNS/DNS-SD Stack.
    ...
    [FAILED] Failed to start Modem Manager
    etc.
    No graphical screen ever appears.
Fedora 29 arm also failed, I do not remember now how.
Various 64-bit Debian-derivatives also fail to boot.

Tried both MicroSD 16GB 23MB/s card and USB flashdisk 16GB 16MB/s.

Using official Raspberry power supply with their logo 5.1V 2.5A.

Any idea?

Thanks,
Jan

[Stuart D. Gathman]

On Tue, 12 Mar 2019, Jan Kratochvil wrote:
> sorry it may not be really Fedora specific but all images fail to boot for me
> except for the plain 32-bit Raspbian.
>
> Fedora 29 aarch64 Workstation fails on:
>    https://www.jankratochvil.net/t/rpi3fail.jpg
>    [FAILED] Failed to start Avahi mDNS/DNS-SD Stack.
>    ...
>    [FAILED] Failed to start Modem Manager
>    etc.
>    No graphical screen ever appears.
> Fedora 29 arm also failed, I do not remember now how.

I have rPi3B, and it required a few config tweaks. The
arm-image-installer package for Fedora has a script with the tweaks.

[Jan Kratochvil]

On Tue, 12 Mar 2019 20:58:43 +0100, Stuart D. Gathman wrote:
> I have rPi3B, and it required a few config tweaks. The
> arm-image-installer package for Fedora has a script with the tweaks.

Could you be more specific, please?

I have tried both 'xz -dc' and both fedora-arm-image-installer with no change
of the result:
# fedora-arm-image-installer --image=arch/iso-copy/Fedora-Workstation-29-1.2.aarch64.raw.xz --media=/dev/XXXsda --norootpass --resizefs --target=rpi3

I have found as a "tweak" only --blacklistvc4 from:
    Blank screen after boot on Raspberry Pi
    https://bugzilla.redhat.com/show_bug.cgi?id=1387733
Where they talk about black screen but I do not get black screen.
When I added --blacklistvc4 I got during installation:
    = Blacklisting the VC4 Driver for the Raspberry Pi 2/3
    sed: can't read /tmp/boot/extlinux/extlinux.conf: No such file or directory
But it did not change anything, it still fails during boot with:
    https://www.jankratochvil.net/t/rpi3fail.jpg
    [FAILED] Failed to start Avahi mDNS/DNS-SD Stack.
    ...
    [FAILED] Failed to start Modem Manager
    etc.
    It stays at the text failed systemd startup messages.

Also
    /usr/share/arm-image-installer/boards.d/rpi3
contains just:
    echo "= Raspberry Pi 3 Uboot is already in place, no changes needed."
    SYSCON="ttyS1,115200"
So I do not see "a script with the tweaks".

Thanks,
Jan

[Stuart D. Gathman]

On Tue, 12 Mar 2019, Jan Kratochvil wrote:
> On Tue, 12 Mar 2019 20:58:43 +0100, Stuart D. Gathman wrote:
> > I have rPi3B, and it required a few config tweaks. The
> > arm-image-installer package for Fedora has a script with the tweaks.
>
> Could you be more specific, please?
>
> I have tried both 'xz -dc' and both fedora-arm-image-installer with no change
> of the result:
> # fedora-arm-image-installer --image=arch/iso-copy/Fedora-Workstation-29-1.2.aarch64.raw.xz --media=/dev/XXXsda --norootpass --resizefs --target=rpi3
>
> I have found as a "tweak" only --blacklistvc4 from:

Yes, that is the critical one.
> When I added --blacklistvc4 I got during installation:
>    = Blacklisting the VC4 Driver for the Raspberry Pi 2/3
>    sed: can't read /tmp/boot/extlinux/extlinux.conf: No such file or directory

The script doesn't do it correctly.  I had to blacklist it myself.
Mount the filesystem on the image (loopback) and edit the modules.conf
I did the minimal image, and added a desktop later.

I am not near my rpi3B, and it is not powered on.

[Peter Robinson]

On Tue, Mar 12, 2019 at 3:55 PM Jan Kratochvil
 wrote:
> Hello,
>
> sorry it may not be really Fedora specific but all images fail to boot for me
> except for the plain 32-bit Raspbian.
>
> Fedora 29 aarch64 Workstation fails on:
>         https://www.jankratochvil.net/t/rpi3fail.jpg
>         [FAILED] Failed to start Avahi mDNS/DNS-SD Stack.
>         ...
>         [FAILED] Failed to start Modem Manager
>         etc.
>         No graphical screen ever appears.

Does the screen go blank, or does the startup scripts remain on the screen?

GNOME is pretty tight on resources, over the last year or so there has
been concerted efforts to shrink the footprint of gnome and F-29 is
better than F-28, and F-30 will be better again. Depending on your
usecase one of the other more lightweight DE might be a better fit.
> Fedora 29 arm also failed, I do not remember now how.
> Various 64-bit Debian-derivatives also fail to boot.
>
> Tried both MicroSD 16GB 23MB/s card and USB flashdisk 16GB 16MB/s.
>
> Using official Raspberry power supply with their logo 5.1V 2.5A.
>
> Any idea?
>
> Thanks,
> Jan
> _______________________________________________
> arm mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]

[Peter Robinson]

On Tue, Mar 12, 2019 at 9:00 PM Jan Kratochvil
 wrote:
> On Tue, 12 Mar 2019 20:58:43 +0100, Stuart D. Gathman wrote:
> > I have rPi3B, and it required a few config tweaks. The
> > arm-image-installer package for Fedora has a script with the tweaks.
>
> Could you be more specific, please?
>
> I have tried both 'xz -dc' and both fedora-arm-image-installer with no change
> of the result:
> # fedora-arm-image-installer --image=arch/iso-copy/Fedora-Workstation-29-1.2.aarch64.raw.xz --media=/dev/XXXsda --norootpass --resizefs --target=rpi3
>
> I have found as a "tweak" only --blacklistvc4 from:
>         Blank screen after boot on Raspberry Pi
>         https://bugzilla.redhat.com/show_bug.cgi?id=1387733
> Where they talk about black screen but I do not get black screen.
> When I added --blacklistvc4 I got during installation:
>         = Blacklisting the VC4 Driver for the Raspberry Pi 2/3
>         sed: can't read /tmp/boot/extlinux/extlinux.conf: No such file or directory
> But it did not change anything, it still fails during boot with:

On aarch64 we boot with grub2, not extlinux so that explains the issue
there, I don't believe the vc4 driver is the issue you're actually
experiencing here.
>     https://www.jankratochvil.net/t/rpi3fail.jpg
>     [FAILED] Failed to start Avahi mDNS/DNS-SD Stack.
>     ...
>     [FAILED] Failed to start Modem Manager
>     etc.
>     It stays at the text failed systemd startup messages.
>
> Also
>         /usr/share/arm-image-installer/boards.d/rpi3
> contains just:
>         echo "= Raspberry Pi 3 Uboot is already in place, no changes needed."
>         SYSCON="ttyS1,115200"
> So I do not see "a script with the tweaks".

The Raspberry Pi, because of the way it boots, is setup by default,
the vast majority of the boards need U-Boot dd:ed to somewhere special
in the first 2Mb of the disk.

[Jan Kratochvil]

On Wed, 13 Mar 2019 09:52:33 +0100, Peter Robinson wrote:
> Does the screen go blank, or does the startup scripts remain on the screen?

Not black, always the [  OK  ]+[FAILED] messages remain on the screen.
> GNOME is pretty tight on resources,

I am even trying to boot the Minimal image and it also does not boot.
    # fedora-arm-image-installer --image=Fedora-Minimal-29-1.2.aarch64.raw.xz --media=/dev/XXXsdb --norootpass --resizefs --target=rpi3 --blacklistvc4
    https://www.jankratochvil.net/t/rpi3fail2.jpg

Now it locks up on "Starting NTP client/server..." for 30+ minutes.

When I left it running whole night it booted into login prompt but after
entering any username it printed "timeout after 60 seconds" before asking for
a password.

Even 32-bit Fedora does not boot there.

Has anyone ever booted any Fedora on Raspberry Pi 3B+? I am not sure if my
RPi3B+ isn't defective but it does boot stock 32-bit Raspbian image.

Thanks,
Jan

[Peter Robinson]

On Wed, Mar 13, 2019 at 9:34 AM Jan Kratochvil
 wrote:
> On Wed, 13 Mar 2019 09:52:33 +0100, Peter Robinson wrote:
> > Does the screen go blank, or does the startup scripts remain on the screen?
>
> Not black, always the [  OK  ]+[FAILED] messages remain on the screen.

OK, so ignore the previously suggested vc4 blacklist, that is not your problem.
> > GNOME is pretty tight on resources,
>
> I am even trying to boot the Minimal image and it also does not boot.
>         # fedora-arm-image-installer --image=Fedora-Minimal-29-1.2.aarch64.raw.xz --media=/dev/XXXsdb --norootpass --resizefs --target=rpi3 --blacklistvc4
>         https://www.jankratochvil.net/t/rpi3fail2.jpg
>
> Now it locks up on "Starting NTP client/server..." for 30+ minutes.
>
> When I left it running whole night it booted into login prompt but after
> entering any username it printed "timeout after 60 seconds" before asking for
> a password.
>
> Even 32-bit Fedora does not boot there.
>
> Has anyone ever booted any Fedora on Raspberry Pi 3B+? I am not sure if my
> RPi3B+ isn't defective but it does boot stock 32-bit Raspbian image.

Yes, I've deployed it literally 100s of times and I've had lots of
other reports of success.

What is the rating of your PSU? It's a wide shot but it's also the
single biggest problem I see.

Peter

[Jan Kratochvil]

On Wed, 13 Mar 2019 10:43:41 +0100, Peter Robinson wrote:
> On Wed, Mar 13, 2019 at 9:34 AM Jan Kratochvil  wrote:
> > Has anyone ever booted any Fedora on Raspberry Pi 3B+? I am not sure if my
> > RPi3B+ isn't defective but it does boot stock 32-bit Raspbian image.
>
> Yes, I've deployed it literally 100s of times and I've had lots of
> other reports of success.

I see I will return it as defective.  But it is weird, it "almost" works.
> What is the rating of your PSU? It's a wide shot but it's also the
> single biggest problem I see.

I wrote in my OP:
    Using official Raspberry power supply with their logo 5.1V 2.5A.

I remember when I used first some my noname 5V PSU with just 2A it was
printing a lot of messages about low volate.  There are no such messages now.

Thanks,
Jan

[Peter Robinson]

On Wed, Mar 13, 2019 at 10:00 AM Jan Kratochvil
 wrote:
> On Wed, 13 Mar 2019 10:43:41 +0100, Peter Robinson wrote:
> > On Wed, Mar 13, 2019 at 9:34 AM Jan Kratochvil  wrote:
> > > Has anyone ever booted any Fedora on Raspberry Pi 3B+? I am not sure if my
> > > RPi3B+ isn't defective but it does boot stock 32-bit Raspbian image.
> >
> > Yes, I've deployed it literally 100s of times and I've had lots of
> > other reports of success.
>
> I see I will return it as defective.  But it is weird, it "almost" works.
> > What is the rating of your PSU? It's a wide shot but it's also the
> > single biggest problem I see.
>
> I wrote in my OP:
>         Using official Raspberry power supply with their logo 5.1V 2.5A.
>
> I remember when I used first some my noname 5V PSU with just 2A it was
> printing a lot of messages about low volate.  There are no such messages now.

OK, maybe try the latest F30 image to see if that is any better?

https://dl.fedoraproject.org/pub/fedora-secondary/development/30/Workstation...

[Jan Kratochvil]

On Wed, 13 Mar 2019 11:09:24 +0100, Peter Robinson wrote:
> https://dl.fedoraproject.org/pub/fedora-secondary/development/30/Workstation...

That looks much better although after "Starting Gnome display manager" it
flashed its screen to black, then back to systemd startup messages and I could
not do anything with it.  No X login screen, no text login screen on any text
console.

With "3" (disable X) it started into a text login but "root" was "!locked" and
after I unlocked it (in /etc/passwd+shadow) my USB flashdrive died so I cannot
do more tests until I receive a newly ordered one.

Thanks,
Jan

[Peter Robinson]

On Wed, Mar 13, 2019 at 12:00 PM Jan Kratochvil
 wrote:
> On Wed, 13 Mar 2019 11:09:24 +0100, Peter Robinson wrote:
> > https://dl.fedoraproject.org/pub/fedora-secondary/development/30/Workstation...
>
> That looks much better although after "Starting Gnome display manager" it
> flashed its screen to black, then back to systemd startup messages and I could
> not do anything with it.  No X login screen, no text login screen on any text
> console.
>
> With "3" (disable X) it started into a text login but "root" was "!locked" and
> after I unlocked it (in /etc/passwd+shadow) my USB flashdrive died so I cannot
> do more tests until I receive a newly ordered one.

Right, all of that is dealt with in the gnome initial setup. You could
add a ssh key with the --add-key (I think) option in
arm-image-installer or there might be a password option which would
allow you to circumvent that.

P