• Gnome 3.22 --> switch NVIDIA to Nouveau?


    Hi there,

    Currently, there are 114 updates waiting to be installed and this is because of the GNOME update. Apparently, Gnome 3.22 boots to Wayland by default but Wayland does not support the NVIDIA drivers.

    How can I savely switch to Nouveau before updating? What packages to install and uninstall? It would be nice if it was reversible in case something goes wrong.

    Do you have any idea as to when there will be NVIDIA support for Wayland? Maybe I can hold back the update a few days?

    Thanks in advance!

  • @DOS-6.1 said i

    Apparently, Gnome 3.22 boots to Wayland by default

    No worries about that. As with 3.20, there s an option of choosing between Wayland and X11 session. So, your selection now is “Gnome on X11” before login.
    I also have a problem with Wayland, which worked perfectly so far, but it stays with a dead-frozen gray screen and cursor with 3.22. I haven t dug for info so far just upgraded) since a) X11 works and b) my default DE is Plasma (on the same system).
    Cheers

    1.Antergos Linux KDE plasma / Gnome 2.Ubuntu 17.10 64bit Unity
    Intel Core2 Duo CPU P8400 2.26GHz‖ RAM 3908 MiB ‖ Dell Inc. 0F328M - Dell Inc. Latitude E6500
    Intel Mobile 4 Series Chipset Integrated Graphics [8086:2a42] {i915

  • @anarch
    I completely forgot about the login screen as I use gdm with auto login. That I can change before the update.
    Can I make the “Gnome on X11” the default option so that auto login would work with Gnome 3.22 or would I have to manually select it every time on login?

  • @DOS-6.1 said

    Can I make the “Gnome on X11” the default option or would I have to manually select it every time on login?

    Once an option is selected it becomes your default on login. Mine is set to…Plasma and it stays there as long as I don t change it to something other (Gnome, Gnome on X11, Plasma, Kodi, my own options).

    1.Antergos Linux KDE plasma / Gnome 2.Ubuntu 17.10 64bit Unity
    Intel Core2 Duo CPU P8400 2.26GHz‖ RAM 3908 MiB ‖ Dell Inc. 0F328M - Dell Inc. Latitude E6500
    Intel Mobile 4 Series Chipset Integrated Graphics [8086:2a42] {i915

  • @anarch
    that’s conveniant. I’ll do the update tomorrow and flag this thread as solved.

    Thanks for your help, mate!

  • @DOS-6.1 said in Gnome 3.22 --> switch NVIDIA to Nouveau?:

    …Apparently, Gnome 3.22 boots to Wayland by default but Wayland does not support the NVIDIA drivers…

    What makes you think so?

    I’m on Nvidia Optimus (GeForce GT 750M), with Bumblebee and proprietary Nvidia drivers, and with Gnome upgraded to 3.22 running on Wayland:

    0_1476299011691_gnome-3.22.1-on-wayland.png

    Bumblebee and Nvidia drivers continue to work flawlessly, without a problem No human intervention was needed before the upgrade.

    I have no idea how Gnome on Wayland behaves on simple, single-GPU NVIDIA cards though.

  • @just said in Gnome 3.22 --> switch NVIDIA to Nouveau?:

    @DOS-6.1 said in Gnome 3.22 --> switch NVIDIA to Nouveau?:

    …Apparently, Gnome 3.22 boots to Wayland by default but Wayland does not support the NVIDIA drivers…

    What makes you think so?

    It was mentioned on Reddit.

    I have no idea how Gnome on Wayland behaves on simple, single-GPU NVIDIA cards though.

    I guess I have to find out as this is my setup :)

  • @DOS-6.1 said in Gnome 3.22 --> switch NVIDIA to Nouveau?:

    I guess I have to find out as this is my setup :)

    Then your best bet is a full backup of the / partition with clonezilla or fsarchiver.

    After that you may do everything you want with the system - an eventual restore takes less than 5 minutes.

  • @just
    ok, I’m now on Gnome 3.22.1. Everything seems to be working so far.

    This might be a super noob question but how do I know whether I’m on Wayland or X? I clicked “Gnome” and not “Gnome under Xorg” on log in. My “Details” window just lists my graphics card under “graphics”.

    edit: echo $XDG_SESSION_TYPE returns "x11"
    It seems to be a bug/feature for some people that what should be the Wayland option loads an X session. Just saw it on Reddit. Anyway, as long as everything is working, I consider this question answered.
    Thanks againg, just. Til next time.

  • @just
    Are you sure that’s the nivida card running there and not the intel ?
    J.

  • @Jeannie____ said in Gnome 3.22 --> switch NVIDIA to Nouveau?:

    @just
    Are you sure that’s the nivida card running there and not the intel ?
    J.

    Yes, I’m pretty sure.

    I firmly believe that Gtk3 and Gnome3 are for aliens. Being an ordinary human, I’m unable to use them. Only occasionally I install or restore Gnome3, for technical tests or to help to solve problems related to it.

    I’m not a Gnome3 expert.

    Anyway. This is the situation with Gnome 3.22.1 running on Nvidia Optimus computer with GeForce GTK 750M hybrid video card. Optimus computers have two GPUs - Intel and NVIDIA. Any program can be run on either one. This installation uses GDM.

    GDM offers four sessions:

    • GNOME (the default; corresponds to former GNOME on Wayland) <-- tested
    • GNOME Classic
    • GNOME on Xorg <-- tested
    • Weston <-- tested

    GNOME session (GNOME on Wayland)

    1. Session type in CLI

      $ echo $XDG_SESSION_TYPE
      wayland
      $
      
    2. Session type in GUI

      $ gnome-control-center info
      

      opens
      gnome-on-wayland

    3. Bumblebee and proprietary NVIDIA test

      Glxspheres running on Intel on Wayland:

      $ glxspheres64
      Polygons in scene: 62464 (61 spheres * 1024 polys/spheres)
      Visual ID of window: 0x1b2
      Context is Direct
      OpenGL Renderer: Mesa DRI Intel(R) Haswell Mobile
      59.368815 frames/sec - 66.255597 Mpixels/sec
      59.964309 frames/sec - 66.920168 Mpixels/sec
      60.020259 frames/sec - 66.982609 Mpixels/sec
      59.970117 frames/sec - 66.926651 Mpixels/sec
      59.074222 frames/sec - 65.926832 Mpixels/sec
      59.998891 frames/sec - 66.958763 Mpixels/sec
      

      Glxspheres running on Nvidia on Wayland:

      $ optirun -c jpeg glxspheres64
      Polygons in scene: 62464 (61 spheres * 1024 polys/spheres)
      Visual ID of window: 0x24
      Context is Direct
      OpenGL Renderer: GeForce GT 750M/PCIe/SSE2
      96.609089 frames/sec - 127.815743 Mpixels/sec
      99.555864 frames/sec - 121.104345 Mpixels/sec
      100.815150 frames/sec - 122.509707 Mpixels/sec
      99.174667 frames/sec - 120.678929 Mpixels/sec
      99.105615 frames/sec - 120.601866 Mpixels/sec
      98.929099 frames/sec - 120.404874 Mpixels/sec
      100.762322 frames/sec - 122.450752 Mpixels/sec
      100.698622 frames/sec - 122.379662 Mpixels/sec
      100.595501 frames/sec - 122.264579 Mpixels/sec
      101.034562 frames/sec - 122.754571 Mpixels/sec
      

    GNOME on Xorg session

    1. Session type in CLI

      $ echo $XDG_SESSION_TYPE
      X11
      $
      
    2. Session type in GUI

      $ gnome-control-center info
      

      opens
      gnome-on-xorg
      On Xorg the tool reports the main GPU.

    3. Bumblebee and proprietary NVIDIA test

      Glxspheres running on Intel on Xorg:

      $ glxspheres64
      Polygons in scene: 62464 (61 spheres * 1024 polys/spheres)
      Visual ID of window: 0xb4
      Context is Direct
      OpenGL Renderer: Mesa DRI Intel(R) Haswell Mobile
      60.167724 frames/sec - 67.147180 Mpixels/sec
      60.184378 frames/sec - 67.165766 Mpixels/sec
      60.165834 frames/sec - 67.145071 Mpixels/sec
      60.251699 frames/sec - 67.240896 Mpixels/sec
      60.167831 frames/sec - 67.147300 Mpixels/sec
      

      Glxspheres running on Nvidia on Xorg:

      $ optirun -c jpeg glxspheres64
      Polygons in scene: 62464 (61 spheres * 1024 polys/spheres)
      Visual ID of window: 0x20
      Context is Direct
      OpenGL Renderer: GeForce GT 750M/PCIe/SSE2
      97.895588 frames/sec - 141.251476 Mpixels/sec
      98.903874 frames/sec - 142.376723 Mpixels/sec
      99.711063 frames/sec - 140.277547 Mpixels/sec
      99.353657 frames/sec - 145.878681 Mpixels/sec
      99.020174 frames/sec - 146.506514 Mpixels/sec
      100.528826 frames/sec - 144.190170 Mpixels/sec
      

    Weston session (same as GNOME on Wayland)

    1. Session type in CLI

      $ echo $XDG_SESSION_TYPE
      wayland  <-- as expected, correct
      $
      
    2. Session type in GUI

      $ gnome-control-center info
      

      as expected, reports Wayland graphics:
      gnome-on-wayland

    3. Bumblebee and proprietary NVIDIA test

      Trying to run glxspheres on Intel on Weston:

      $ glxspheres64
      Could not open display
      $
      

      Trying to run glxspheres on NVIDIA on Weston:

      $ optirun -c jpeg glxspheres64
      Could not open display
      

    I do not have computers with non-hybrid, simple, single-GPU, NVIDIA-only video cards. So can’t tell anything about Gnome 3.22 on them.

    Cheers

  • @just
    Thanks for that very detailed reply. Imho it doesn’t look as if wayland works with nvidia proprietary.
    What happens if you run the gnome-control-center info with optirun?
    J.

  • @Jeannie____ said in Gnome 3.22 --> switch NVIDIA to Nouveau?:

    @just

    What happens if you run the gnome-control-center info with optirun?

    Good question. Because I can’t get an aswer for it.

    When I run

    optirun gnome-control-center info
    

    with Alt+F2, nothing happens. No errors, Gnome Settings window doesn’t open.

    When I run the same command in terminal, again:

    $ optirun gnome-control-center info
    $
    

    Gnome Settings doesn’t open, no errors returned, nothing happens.

    I understand, you’d like to verify whether or not X clients run on xorg-server-xwayland, rather than on native wayland. Cannot exclude it, moreover, most probably this is the case. But honestly don’t know, how to check it.

    Other programs continue to run in Gnome on Wayland with optirun (on NVIDIA) normally, whether they use xorg-server-xwayland or wayland.

3.222 switch13 gnome250 nvidia112 Posts 13Views 2693
Log in to reply