While defaulting to Wayland since version 25 of Fedora Workstation (GNOME), and Fedora version 34 for the KDE Plasma Desktop spin, this Linux distribution intends to completely ditch X.Org session as fallback for GNOME on release 41.
Quoting Jens Petersen from the change number 414 of fedora-workstation Pague:
Fedora Workstation WG discussed this today and we agreed we should do this for Fedora 41, since it is really too late already for F40 and it should really be handled as a System Wide Change anyway.
Based on that message we can conclude that while it is too late to have that change merged into Fedora 40, it is likely that this will be the default for Fedora 41, making GNOME completely bound to Wayland with no X.Org fallback.
While one user on that same discussion stated that screen reader users will still rely on the X11 session because of some GNOME bugs, it is likely that any software still using X11 by default will not be distributed with the installation ISO as pointed out by Neal Gompa.
Other than that, no matter if you are an NVIDIA, Intel or AMD user, this might be a really good move starting with Fedora because GNOME developers can focus on fixing existing Wayland bugs instead of wasting time with three layers (X.Org, Wayland and in some cases XWayland).
The ChangeSet page for that Fedora 41 was not updated with this change as per the date of this article.
That would explain why now, after all this time, Nvidia has suddenly shown interest in supporting open source drivers.The open source kernel modules were more a result of discussions with Red Hat: https://blogs.gnome.org/uraeus/2022/05/11/why-is-the-open-source-driver-release-from-nvidia-so-important-for-linux/
And as the only linux vendor with a significant engineering footprint in GPUs we have been working closely with NVIDIA. People like Kevin Martin, the manager for our GPU technologies team, Ben Skeggs the maintainer of Nouveau and Dave Airlie, the upstream kernel maintainer for the graphics subsystem, Nouveau contributor Karol Herbst and our accelerator lead Tom Rix have all taken part in meetings, code reviews and discussions with NVIDIA.
That makes me wonder how much attention they'll ever give to gaming if their main focus is engineering and other technical uses. Has there been any disccussion around actual gaming use? Part of the problem with the proprietary drivers has always been their apathy toward Linux gaming. Any plans for that to change with the open source driver?
I'm tempted to say NVIDIA is thinking: "I wish they would get to tens of millions of [gaming] users, at which point it would actually make sense to support it." I don't know.That would explain why now, after all this time, Nvidia has suddenly shown interest in supporting open source drivers.The open source kernel modules were more a result of discussions with Red Hat: https://blogs.gnome.org/uraeus/2022/05/11/why-is-the-open-source-driver-release-from-nvidia-so-important-for-linux/
And as the only linux vendor with a significant engineering footprint in GPUs we have been working closely with NVIDIA. People like Kevin Martin, the manager for our GPU technologies team, Ben Skeggs the maintainer of Nouveau and Dave Airlie, the upstream kernel maintainer for the graphics subsystem, Nouveau contributor Karol Herbst and our accelerator lead Tom Rix have all taken part in meetings, code reviews and discussions with NVIDIA.
That makes me wonder how much attention they'll ever give to gaming if their main focus is engineering and other technical uses. Has there been any disccussion around actual gaming use? Part of the problem with the proprietary drivers has always been their apathy toward Linux gaming. Any plans for that to change with the open source driver?
But in some ways, it doesn't matter. It's open source, now, and the community is already doing great work with NVK, Zink, and the Noveau kernel driver (maybe one day replaced by Nova?). Fancy stuff like DLSS might not be there (?, I don't really use any of those features), but I don't think it will be long until Noveau + Zink + NVK is the driver stack we'll be running on NVIDIA almost everywhere because it's just a better experience in general.
I sure hope so...
NVK is turing+, isn't it?I'm tempted to say NVIDIA is thinking: "I wish they would get to tens of millions of [gaming] users, at which point it would actually make sense to support it." I don't know.That would explain why now, after all this time, Nvidia has suddenly shown interest in supporting open source drivers.The open source kernel modules were more a result of discussions with Red Hat: https://blogs.gnome.org/uraeus/2022/05/11/why-is-the-open-source-driver-release-from-nvidia-so-important-for-linux/
And as the only linux vendor with a significant engineering footprint in GPUs we have been working closely with NVIDIA. People like Kevin Martin, the manager for our GPU technologies team, Ben Skeggs the maintainer of Nouveau and Dave Airlie, the upstream kernel maintainer for the graphics subsystem, Nouveau contributor Karol Herbst and our accelerator lead Tom Rix have all taken part in meetings, code reviews and discussions with NVIDIA.
That makes me wonder how much attention they'll ever give to gaming if their main focus is engineering and other technical uses. Has there been any disccussion around actual gaming use? Part of the problem with the proprietary drivers has always been their apathy toward Linux gaming. Any plans for that to change with the open source driver?
But in some ways, it doesn't matter. It's open source, now, and the community is already doing great work with NVK, Zink, and the Noveau kernel driver (maybe one day replaced by Nova?). Fancy stuff like DLSS might not be there (?, I don't really use any of those features), but I don't think it will be long until Noveau + Zink + NVK is the driver stack we'll be running on NVIDIA almost everywhere because it's just a better experience in general.
I sure hope so...
Currently yes, but this is from the [December 2023 update](https://www.collabora.com/news-and-blog/news-and-events/nvk-holiday-update.html):NVK is turing+, isn't it?I'm tempted to say NVIDIA is thinking: "I wish they would get to tens of millions of [gaming] users, at which point it would actually make sense to support it." I don't know.That would explain why now, after all this time, Nvidia has suddenly shown interest in supporting open source drivers.The open source kernel modules were more a result of discussions with Red Hat: https://blogs.gnome.org/uraeus/2022/05/11/why-is-the-open-source-driver-release-from-nvidia-so-important-for-linux/
And as the only linux vendor with a significant engineering footprint in GPUs we have been working closely with NVIDIA. People like Kevin Martin, the manager for our GPU technologies team, Ben Skeggs the maintainer of Nouveau and Dave Airlie, the upstream kernel maintainer for the graphics subsystem, Nouveau contributor Karol Herbst and our accelerator lead Tom Rix have all taken part in meetings, code reviews and discussions with NVIDIA.
That makes me wonder how much attention they'll ever give to gaming if their main focus is engineering and other technical uses. Has there been any disccussion around actual gaming use? Part of the problem with the proprietary drivers has always been their apathy toward Linux gaming. Any plans for that to change with the open source driver?
But in some ways, it doesn't matter. It's open source, now, and the community is already doing great work with NVK, Zink, and the Noveau kernel driver (maybe one day replaced by Nova?). Fancy stuff like DLSS might not be there (?, I don't really use any of those features), but I don't think it will be long until Noveau + Zink + NVK is the driver stack we'll be running on NVIDIA almost everywhere because it's just a better experience in general.
I sure hope so...
We are also continuing to work on Maxwell support. We don't have an ETA yet but the work is ongoing. Most of the work right now is in bringing up the new compiler on Maxwell. While the overall shape of the instruction set is largely the same as in Turing, it has an entirely different encoding. There are also some Maxwell-specific bugs as well as a few features that have to be implemented differently there. If you're looking to contribute to NVK, helping out with Maxwell support is an excellent area for new contributors.
See more from me