In Fedora 36 Wayland will work by default with NVIDIA drivers and could be the last version with support for 32-bit ARM

Recently Fedora developers, gave to be known through the mailing lists part of the plans and changes that are already prepared to be implemented in the next version of Fedora Linux 36.

In the information released, the transition to using the GNOME session default based on protocol Wayland with proprietary NVIDIA driver systems.

This change, broadly benefits the ability to select a GNOME session that runs on a Wayland server using the Nvidia drivers, which highlights that it is already at the level of a session on a traditional X server and which will also continue provided as before.

The change has not yet been reviewed by the Fedora Engineering Steering Committee, which is responsible for the technical development of the Fedora Linux distribution, but as some may already know, these announced changes are usually implemented in the test images.

With that the recent updates to the NVIDIA proprietary driver allow Xwayland to benefit
hardware acceleration and X11 applications can have their
accelerated rendering hardware.

It should be noted that in the recent NVIDIA proprietary driver release, changes have been made to provide full support for OpenGL and Vulkan hardware acceleration in X11 applications running using XWayland's DDX (Device-Dependent X) component.

With the new branch of NVIDIA drivers, the performance of OpenGL and Vulkan in X applications launched with XWayland is now almost the same as when launched with a normal X server.

As a reminder, the distribution started offering a default GNOME session based on the Wayland protocol as of Fedora 25. This session was only used when using open source drivers, and when installing proprietary NVIDIA drivers, only a session based on on X server.

This changed with the release of Fedora Linux 35 and added the option to use Wayland with proprietary NVIDIA drivers. Fedora Linux 36 plans to set this option to default.

Another change that has been released for the next Fedora versions, is for the implementation on Fedora Linux 37, version in which it is contemplated that is transferred on a scheduled basis to the legacy ARMv7 download architecture, also known as ARM32 or armhfp.

All development efforts for ARM systems plan to focus on the ARM64 (Aarch64) architecture. The change has not yet been reviewed by the Fedora Engineering Steering Committee, which is responsible for the technical development of the Fedora distribution.

In this case, if such a change is approved, the version of Fedora 36 will be the last 32-bit ARM version of the distribution with updates until June 2023, that is, it will practically have one more year of support.

The general rollback of the distribution for 32-bit systems is cited as reasons for the end of support for ARMv7, as some of the new security and performance improvements in Fedora are only available for 64-bit architectures.

In general, arm32 is on the decline with generally few new ARMv7 devices being added to Fedora in recent versions.

To add to that a number of new Fedora features designed to improve the speed and security of Fedora.

The release is causing 32-bit architectures in general mainly due to
the process memory limit when linking large applications.
ARMv7 / armhfp is the latest fully supported 32-bit architecture, yet
they currently compile i686 packages, but they are not shipped as artifacts.

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

Finally if you are interested in knowing more about it About the news, you can check the details in the following links.

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

Be the first to comment

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.