----- Original Message -----
That is true unless your board need a FDT.
Then the following patch breaks that assumption that /boot is not
needed before grub2 starts:
The ways to reproduce for me is:
Writing the image mentioned above to a SD-Card and trying to boot it
in a Raspberry PI 3B.
The aarch64 server image was tested and boots on the rpi3(B/B+) and
pine64_plus using the provided uboot.
I can also reproduce the behavior by writing the image to a
and using a self built version of U-Boot (which is mainline upstream
incorporates the mentioned patch and "use Fedora specific EFI
path/name" as well as using the binary blob for memory init from
rockchip since the one you can build from mainline is not stable on my
Both setup fails with Fedora31 server images. Both boots fine with
Fedora30 server images.
Will see if I can produce logs, needs to re-write some SD-card for that
Thanks! Attached is a boot of the server image on the rpi3b+.
Den sön 1 dec. 2019 kl 19:02 skrev Peter Robinson <pbrobinson(a)gmail.com>:
> On Sun, 1 Dec 2019, 08:01 Peter Hjalmarsson, <kanelxake(a)gmail.com> wrote:
>> Just wanted to point out that due to U-Boot not supporting XFS, and Fedora
>> Server has moved to a XFS /boot, the current images as
>> does not boot on any system using U-Boot, like for example the raspberry
> On aarch64 we use uefi which loads grub2 off a vfat partition, which in
> turn has a XFS driver so this isn't an issue.
> You'll need to go into more explicit details of what you're doing and which
>> Best Regards,
>> Peter Hjalmarsson
>> arm mailing list -- arm(a)lists.fedoraproject.org
>> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
>> Fedora Code of Conduct:
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
arm mailing list -- arm(a)lists.fedoraproject.org
To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines