Announcement

Collapse
No announcement yet.

Fedora 36 Planning To Run Wayland By Default With NVIDIA's Proprietary Driver

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #11
    How about DMA-BUF support for screen casting using PipeWire? AFAIK it's not supported yet. Is there any chance NVIDIA will deliver that in time there's new Fedora release?

    GNOME patches required to run Wayland aren't in the Arch repo yet, but I tried separate installation of Fedora and I compiled mutter, gnome-shell, glib and few more from master. It worked almost ok on my RTX 3060Ti, but my issues (clicking on a drive in Nautilus caused the whole session crash, GNOME was successively filling all the RAM just by opening and closing apps) were probably related to the way I just built some of the desktop components and not the full thing. Anyway, I played with it for entire evening and the overall experience was great, including hardware accelerated Firefox and heavy AAA games. In fact in many cases it was far better than NVIDIA + Xorg in terms of smoothness. Looking forward to switching back to Wayland session!

    Comment


    • #12
      Who knows how many headaches Nvidia users will have, already with Xorg it is an ordeal, ... maybe not, we'll see, but they make me tenderness.

      Comment


      • #13
        You guys all realize that you can just choose the Gnome X11 session option at login right? Nothing is going to force you to use Wayland if there are still bugs to be worked out.

        Comment


        • #14
          They added GBM support in 2021, after like 5 years of keeping their unfunctional (at least on Fermi, though they said it's a minimum family for it to work, but it doesn't) and useless EGLStreams trash, and with their closed proprietary blobs with short time support – leaving older GPU families users behind.
          As always, they fucked up.



          Radeon doesn't greet.

          Comment


          • #15
            Never managed to get Nviida's .run package working on any distribution, so am stuck with Nouveau on my Optimus laptop.

            Problem with Nouveau is that setting DRI_PRIME is not 100% foolproof. In Debian 11, setting DRI_PRIME to the Nvidia GPU causes Plasma Wayland and Chome / Chromium to not work. And yet for some strange reason setting DRI_PRIME to the Nvidia GPU works for Gnome Wayland.

            Best compromise on hand for me is to use the following combinations:
            • Plasma Wayland (Intel) + Chrome / Chromium (Intel) + everything else (Nouveau)
              or
            • Gnome Wayland (Nouveau) + Chrome / Chromium (Intel) + everything else (Nouveau)

            Comment


            • #16
              Originally posted by Sonadow View Post
              Never managed to get Nviida's .run package working on any distribution, so am stuck with Nouveau on my Optimus laptop.[/LIST]
              Looks like you have super old GPU that is working with Nouveau. If missing Vulkan can be considered "fine" lol. We are unlucky with our 9xx+ GPUs here.

              In any case launching .run package is almost always a bad idea, better stuck with distro provided packages.

              Comment


              • #17
                Originally posted by Quackdoc View Post
                gnome still feels like the only stacking compositor that is ready for full time wayland, but we are getting there.

                ELI5 on this statement please.
                Can't GNOME fully go Wayland for Intel (or AMD) users like me?
                Isn't Wayland a part of GNOME?

                Comment


                • #18
                  Everyone is thinking "wow, Nvidia has come a long way with linux". It is however also true that Fedora has come a long way with Nvidia. It's hard to know what is more remarkable: Nvidia supporting gdm, or Fedora supporting Nvidia binaries.

                  Comment


                  • #19
                    Originally posted by Vorpal View Post

                    In that case, I hope they detect that configuration and don't enable wayland by default on such systems. While I'm knowledgable enough to fix this kind of issues fairly easily (and I don't run Fedora), it is important to provide a good out of the box user experience. (As an example of this: a crash issue when selecting btrfs in the installer of Manjaro made me just say "nope, going for another distro, don't want to deal with this". Could I have worked around this? Most likely. But just going with plain Arch instead was easier.)
                    I think that the problem with external monitors in Wayland when using the blob is only when you are running the hybrid setup. That is, let's say intel, iGPU is running the show and you plug your monitor into the Nvidia GPU, then that's when things go south, and that's probably why they still keep Xorg as default for hybrid setups. Last time I checked everything worked okay in Wayland for my hybrid setup **except** plugging in an external monitor. I don't think this is a problem if the Nvidia GPU is the primary display device, but I could be wrong, haven't tested that setup extensively.

                    Comment


                    • #20
                      Originally posted by arglebargle View Post
                      Hybrid graphics with nvidia work fine on X and Wayland now, I've been running Wayland exclusively since nvidia added support. I use Arch, btw.
                      I'm on KDE Wayland Intel plus nvidia.

                      You are right that it does works properly, but only when playing the games through xwayland. If you force Wayland directly on the game, Nvidia Optimus doesn't support that and the game won't run on the Nvidia card.

                      Comment

                      Working...
                      X