[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fedora-arm
Subject:    =?utf-8?q?=5Bfedora-arm=5D?= Re: Status of armhfp grubs2-efi on top of Uboot
From:       "Mark Verlinde" <mark () havak ! nl>
Date:       2020-06-25 14:22:23
Message-ID: 20200625142223.18511.10565 () mailman01 ! iad2 ! fedoraproject ! org
[Download RAW message or body]

Thank you (@Gerd)

> Just going compile vanilla upstream grub and
> use that unfortunately doesn't work that easily any more due to
> non-upstream BLS support fedora grub2 has.  

There is still the grubby-deprecated package to fallback too..

> Also such a setup tends to break on updates, when a new grub2.rpm lands.

Yea, tent to epoch my "custom" builds, ATM it is epoch 2 for a custom grub2

> I don't feel like wading through the fedora grub2 patches, trying to
> find the broken one.  systemd-boot isn't available for armhfp either.
> So I gave up building on EFI (i.e. edk2 + grub2) for my VMs.

Still doing this, also for el7 where grub2 is totally absent for armhfp.

> I'm using a patched[1] qemu uboot image as firmware now & attach the
> fedora server image as sata disk.  Done.  Probably not the answer you
> where looking for ...
 
Well this actually is one the use-cases my looking for, get rid of those "external" \
kernels in armhfp VM's

Grtz Mark
_______________________________________________
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-leave@lists.fedoraproject.org
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@lists.fedoraproject.org



[prev in list] [next in list] [prev in thread] [next in thread]