On 4/14/22 15:53, Jóhann B. Guðmundsson wrote:
On 14.4.2022 22:24, Nikolay Nikolov wrote:
>
> On 4/14/22 23:49, Jóhann B. Guðmundsson wrote:
>> On 14.4.2022 18:20, Chris Adams wrote:
>>> Once upon a time, Robbie Harwood <rharwood(a)redhat.com> said:
>>>> Given there is consensus that legacy BIOS is on its way out
>>> I don't think this statement is true, unless Fedora doesn't want to
be
>>> considered for a bunch of popular VM hosts (e.g. Linode and such) that
>>> have no stated plans to support UEFI.
>>>
>>> Maybe "legacy BIOS on physical hardware" is on its way out
>>
>>
>> It's not an maybe, it is on it's way out either physically or simply
>> via firmware update [1]
>>
>> "In the bios, upgraded to 810 the option to enable legacy boot is
>> greyed out"
>>
>> So how do people propose the situation to be handled when firmware
>> from vendors, disables the legacy boot option via firmware update.
>>
>> Is Fedora supposed to block/blacklist those firmware updates via some
>> plugin in lvfs based on user feedback when their legacy boot mode
>> suddenly stops working or is it expected that upstream lvfs team
>> looks into this or what?
>
> Fedora doesn't install these updates. Users install these updates,
> when they have a problem
In the past they did, today users ( including the novice ones ) update
it as Gnome notifies them about available update just like they do when
they receive anyother software update notification.
That only applies to a UEFI system, so it doesn't matter if legacy mode
gets disabled by the update since it's already using UEFI to boot.