In Fedora 37 it is intended to leave only support for UEFI

Recently we share here on the blog the release note fedora 36 beta, in which we share a little about the changes that have been implemented in this new version.

The work on Fedora is not limited only to the new versions, but there are also plans for the future regarding the changes and improvements that will be implemented in later versions and it is in the case that for Fedora 37, UEFI support is planned to be transferred to the category of mandatory requirements to install the distribution on the x86_64 platform.

It is mentioned that the ability to start environments previously installed on systems BIOS legacy will keep for a while, but new non-UEFI installations will no longer be supported.

In Fedora 39 or later, it is expected that the support of BIOS is 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, End of BIOS support may result in the inability to install Fedora on some computers laptops and PCs released before 2013. Previous discussions also mentioned the inability to install on BIOS-only virtualization systems, but UEFI support has since been added to AWS environments. UEFI support has also been added to libvirt and Virtualbox, but is not yet the default (it is planned for Virtualbox in the 7.0 branch).

The end of BIOS support in Fedora will reduce the number of components used during boot and installation, will remove VESA support, it will simplify installation and reduce labor costs to maintain bootloader and installation builds, since UEFI provides standard unified interfaces and BIOS requires testing of each option.

In addition, we can notice a note about the Anaconda Installer Upgrade Progress, which is being ported 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 focus your attention on several tasks at once, but to break installation and troubleshooting of complex jobs into small, simple steps performed sequentially.

Another change we have for Fedora 37 is a recommendation that maintainers stop building packages for the i686 architecture if the need for such packages is questionable or would result in a significant waste of time or resources. The recommendation does not apply to packages used as dependencies on other packages or used in the "multilib" context to make 32-bit programs run in 64-bit environments.

Besides that the ARMv7 architecture, also known as ARM32 or armhfp, is scheduled to be implemented in Fedora 37. All development efforts for ARM systems are planned to focus on the ARM64 (Aarch64) architecture.

Reasons for ending support for ARMv7 are cited as a general move away from development for 32-bit systems, as some of Fedora's new security and performance enhancements are only available for 64-bit architectures.

Until now, ARMv7 has been the last fully supported 32-bit architecture in Fedora (repositories for the i686 architecture were discontinued in 2019, leaving only multi-library repositories for x86_64 environments).

Finally if you are interested in knowing more about it, you can check the details In the following link.


The content of the article adheres to our principles of editorial ethics. To report an error click here!.

A comment, leave yours

Leave a Comment

Your email address will not be published.

*

*

  1. Responsible for the data: Miguel Ángel Gatón
  2. Purpose of the data: Control SPAM, comment management.
  3. Legitimation: Your consent
  4. Communication of the data: The data will not be communicated to third parties except by legal obligation.
  5. Data storage: Database hosted by Occentus Networks (EU)
  6. Rights: At any time you can limit, recover and delete your information.

  1.   Luisa said

    Luckily this is Linux and fortunately we can use many different distros that work and will work with bios.