On 09/07/2018 08:19 AM, Robert Moskowitz wrote:
What is meant by:
Improvements for upgrade path for UEFI on ARMv7
I just spent a little time researching UEFI. I have a few concerns, and
it probably explains a challenge I have had on my x86_64 notebook.
That is, I have the 'habit' of developing a build on a test system,
moving the drive to the production unit in my rack and booting up.
It seems I can do that with Legacy BIOS as it searches for a boot drive
with an MBR and goes from there. My take on UEFI is that the GUID for a
drive and other information is stored on the system board and that is
used to find the bootup drive. You swap out drives, it won't boot up.
Either you need a tool to change the GUID information in the system, or
change the GUID in the drive you are using.
I suppose one way is to set the GUID in my drive to what the production
system is expecting so that the move goes smoothly.
Do I have this right? Is there something else I should be aware of and
plan for?
thanks
thanks
On 09/07/2018 05:32 AM, Peter Robinson wrote:
Hi All,
There's a new update headed to testing for Fedora 29. It makes some
adjustments to how we handle a few things, in particular the Raspberry
Pi firmware:
https://bodhi.fedoraproject.org/updates/FEDORA-2018-56bc88dfb2
I don't expect anyone to see anything issues in particular especially
for the vast majority of people that just use a SD card or HDD with
their ARM device but there might be some corner cases for people with
slightly more esoteric setups when they upgrade. If anyone sees any
issues please open a bug [1] or reply to this or reach out on
#fedora-arm. The change has been in rawhide for a little while and
I've not seen any fall out there.
Also the new U-Boot will have some slight improvements for those
running AllWinner 64 bit devices as we've moved to the upstream ARM
trusted firmware. It's just a snapshot at the moment but the previous
fork was quite old and had it's issues on certain devices so I expect
this to be an overall win for people there, but again I can't test
everything so if anyone sees issues please reach out.
All please add karma to the above update when you do test it. People
can update U-Boot on a running system with the update-uboot command
with similar syntax to arm-image-installer.
Peter
[1]
https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=29&component=bcm283x-firmware
_______________________________________________
arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
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/arm@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
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/arm@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
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/arm@xxxxxxxxxxxxxxxxxxxxxxx
