On 4/15/22 01: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@xxxxxxxxxx> 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.
Really? I didn't know that. At least on my computers, Gnome has never
notified me about a BIOS update from my motherboard vendor. Besides,
it's proprietary software, so I wouldn't expect Fedora to be offering it
by default. Doesn't it need adding an extra software repository?
And besides, non-UEFI systems don't normally receive BIOS updates
that break legacy boot, because legacy boot is the only boot option
available, so what is your point, exactly?
Obviously this was for dual bios mode ( legacy and uefi ) ( otherwise
the option to disable it would not be there ) in which the vendor
himself seemingly decided to disable the legacy part of the bios via
firmware update which highlight the fact that we somehow need to deal
with that situation if we want to continue to support the legacy bios
option.
How I have no clue, which is why I pointed at an potential lvfs plugin
or the lvfs team.
I think we should check the BIOS date in the installer and deprecate (as
in, print warnings to the user in the installer) legacy boot on newer
systems (e.g. newer than 2017 or some other cutoff date, when we decide
that UEFI becomes more stable), an by deprecate, I mean, show warnings
to the user and suggest that they continue on their own risk. Of course,
we should also check for virtual machines, like e.g. QEMU/SeaBIOS, that
are known to be stable in legacy BIOS mode and not show the warning in
them, even if the BIOS date is new (although SeaBIOS seems to use an old
date - 06/23/99).
Nikolay
JBG
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
