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, which they need to resolve. Most people never
update their BIOS [1], because their system is working just fine. Only
power users do, and they know how to read changelogs and how to backup
their previous working BIOS. So, no, it's not Fedora's problem if a
users installs a BIOS update that bricks their system, or renders it
unbootable (for whatever reasons, doesn't matter whether they're related
to legacy boot or not). We have no obligation to prevent that. The right
approach to BIOS update is "don't do it, unless you have to". If it
ain't broke, don't fix it. I've been burned so many times, due to buggy
BIOS updates, most of them unrelated to legacy boot. We don't prevent
BIOS updates that break UEFI or secure boot, or which brick the system,
so why should we prevent BIOS updates that break legacy boot?
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?
If you want to deprecate legacy boot on new installs on UEFI-capable
BIOS-es, that's another story. E.g. if the installer detects that the
BIOS is modern (e.g. later than 2017-2018) and UEFI capable, but is
running in legacy boot mode, it could prints a warning and suggest to
the user to restart and turn off legacy boot from the BIOS setup. The
installer promises better hardware support, firmware updates and happier
times to the user if the operating system is installed in UEFI mode.
Finally user decides whether to do that, or choose to continue on their
own risk. That is totally reasonable, IMHO. But it is a completely
different thing than dropping legacy BIOS support completely.
1. It is indeed still universally called BIOS, even though it's UEFI:
https://www.asrock.com/support/BIOSIG.asp?cat=BIOS10
Best regards,
Nikolay
JBG
1.
https://forum-en.msi.com/index.php?threads/msi-pro-dp20z-5m-legacy-boot-how-to-enable-legacy-boot.374479/
_______________________________________________
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
