For implementation in Fedora Linux 37, UEFI support is planned to be transferred to the category of mandatory requirements for installing a distribution kit on the x86_64 platform. The ability to boot previously installed environments on legacy BIOS systems will remain for a while, but new non-UEFI installations will no longer be supported. In Fedora 39 or later, BIOS support is expected to be completely removed. The Fedora 37 Change Request has been posted by Ben Cotton, Fedora Program Manager at Red Hat. The change has not yet been reviewed by the FESCo (Fedora Engineering Steering Committee), which is responsible for the technical part of the development of the Fedora distribution.
Hardware based on Intel platforms has shipped with UEFI since 2005. In 2020, Intel discontinued BIOS support on client systems and data center platforms. However, the end of BIOS support may result in the inability to install Fedora on some laptops and PCs released before 2013. Past discussions also mentioned the inability to install on BIOS-only virtualization systems, but UEFI support has since been added to AWS environments. libvirt and Virtualbox also added support for UEFI, but it is not yet the default (it is planned for Virtualbox in the 7.0 branch).
The end of BIOS support in Fedora Linux will reduce the number of components used during boot and installation, remove VESA support, simplify installation, and reduce labor costs for maintaining the bootloader and installation builds, since UEFI provides unified standard interfaces, and BIOS requires separate testing of each option.
Additionally, we can note a note on the progress of the modernization of the Anaconda installer, which is being transferred from the GTK library to a new interface built on the basis of web technologies and allowing remote control via a web browser. Instead of a confusing process of managing the installation through the screen with a summary of the actions performed (Installation Summary), a step-by-step installation wizard is developed. The wizard was developed using PatternFly components and allows you not to spread your attention on several tasks at once, but to divide the installation and solution of complex work into sequentially performed small and simple steps.
Source: opennet.ru