Can't disable nouveau drivers in Ubuntu 18.04

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
3
down vote

favorite
3












I tried disabling nouveau drivers in Ubuntu 18.04 by putting these lines in /etc/modprobe.d/blacklist.conf:




#Blacklist nouveau drivers
blacklist nouveau
blacklist lbm-nouveau
alias nouveau off
alias lbm-nouveau off




and updating initramfs.



On reboot the gdm won't start, blocked in the last line: gdm error
Trying to enter any tty, I get the same error (I had to undo changes from rescue mode).



The same procedure was working on 17.10 (with xorg).



My pc is an Asus ux430uq with clean install of ubuntu 18.04 (4.15.0-20 kernel).



I am afraid of uninstalling xserver-xorg-video-nouveau drivers since I don't know how to reinstall them if something go wrong (I can't get internet working in rescue mode).




EDIT:



Uninstalling the above package lead to the same error. Trying to boot ubuntu with the kernel flag nouveau.modeset=0 gives the same error too.







share|improve this question


























    up vote
    3
    down vote

    favorite
    3












    I tried disabling nouveau drivers in Ubuntu 18.04 by putting these lines in /etc/modprobe.d/blacklist.conf:




    #Blacklist nouveau drivers
    blacklist nouveau
    blacklist lbm-nouveau
    alias nouveau off
    alias lbm-nouveau off




    and updating initramfs.



    On reboot the gdm won't start, blocked in the last line: gdm error
    Trying to enter any tty, I get the same error (I had to undo changes from rescue mode).



    The same procedure was working on 17.10 (with xorg).



    My pc is an Asus ux430uq with clean install of ubuntu 18.04 (4.15.0-20 kernel).



    I am afraid of uninstalling xserver-xorg-video-nouveau drivers since I don't know how to reinstall them if something go wrong (I can't get internet working in rescue mode).




    EDIT:



    Uninstalling the above package lead to the same error. Trying to boot ubuntu with the kernel flag nouveau.modeset=0 gives the same error too.







    share|improve this question
























      up vote
      3
      down vote

      favorite
      3









      up vote
      3
      down vote

      favorite
      3






      3





      I tried disabling nouveau drivers in Ubuntu 18.04 by putting these lines in /etc/modprobe.d/blacklist.conf:




      #Blacklist nouveau drivers
      blacklist nouveau
      blacklist lbm-nouveau
      alias nouveau off
      alias lbm-nouveau off




      and updating initramfs.



      On reboot the gdm won't start, blocked in the last line: gdm error
      Trying to enter any tty, I get the same error (I had to undo changes from rescue mode).



      The same procedure was working on 17.10 (with xorg).



      My pc is an Asus ux430uq with clean install of ubuntu 18.04 (4.15.0-20 kernel).



      I am afraid of uninstalling xserver-xorg-video-nouveau drivers since I don't know how to reinstall them if something go wrong (I can't get internet working in rescue mode).




      EDIT:



      Uninstalling the above package lead to the same error. Trying to boot ubuntu with the kernel flag nouveau.modeset=0 gives the same error too.







      share|improve this question














      I tried disabling nouveau drivers in Ubuntu 18.04 by putting these lines in /etc/modprobe.d/blacklist.conf:




      #Blacklist nouveau drivers
      blacklist nouveau
      blacklist lbm-nouveau
      alias nouveau off
      alias lbm-nouveau off




      and updating initramfs.



      On reboot the gdm won't start, blocked in the last line: gdm error
      Trying to enter any tty, I get the same error (I had to undo changes from rescue mode).



      The same procedure was working on 17.10 (with xorg).



      My pc is an Asus ux430uq with clean install of ubuntu 18.04 (4.15.0-20 kernel).



      I am afraid of uninstalling xserver-xorg-video-nouveau drivers since I don't know how to reinstall them if something go wrong (I can't get internet working in rescue mode).




      EDIT:



      Uninstalling the above package lead to the same error. Trying to boot ubuntu with the kernel flag nouveau.modeset=0 gives the same error too.









      share|improve this question













      share|improve this question




      share|improve this question








      edited May 4 at 9:59

























      asked May 3 at 11:22









      velix

      236213




      236213




















          4 Answers
          4






          active

          oldest

          votes

















          up vote
          3
          down vote



          accepted










          I found the solution. I'll write it here for who may have the same problem.



          My gdm3 session was running in wayland. To check it:



           $ loginctl
          SESSION UID USER SEAT TTY
          2 1000 velix seat0 tty2
          c2 1000 velix
          c1 120 gdm seat0 tty1


          The command loginctl show-session <session-n> -p Type show the session type:



          $ loginctl show-session c1 -p Type
          Type=Wayland


          To change it, edit the file /etc/gdm3/custom.conf and uncomment the line WaylandEnable=false.



          After rebooting:



          $ loginctl show-session c1 -p Type
          Type=x11


          Now blacklisting nouveau drivers in /etc/modprobe.d/blacklist.conf (as in the question) works and doesn't give the above error.



          The key point is to run xorg instead of wayland



          (That's why it was working in my 17.10 ubuntu, forced to run xorg)






          share|improve this answer






















          • +1 Thanks for sharing. Don't forget to accept your answer by clicking check mark next to it in a day or so when it lets you.
            – WinEunuuchs2Unix
            May 4 at 23:13







          • 1




            Gives black screen on a MacBook, answer no longer works?
            – Gabor
            May 9 at 2:10










          • My answer is 5 days old. This method is still working on my notebook.
            – velix
            May 9 at 16:24










          • On a MacBook, where I have the error same as in your screenshot, I only get a black screen. Loginctl also errors out with Failed to create bus connection
            – Gabor
            May 9 at 20:24










          • I think it's a different problem. Open a new question and put more info in that.
            – velix
            May 10 at 9:58

















          up vote
          1
          down vote













          Got exactly same problem, my configuration is x11 (returned by loginctl command).
          The only way working for me at the moment is to rename the nouveau file module.



          # pwd
          /lib/modules/4.15.0-20-generic/kernel/drivers/gpu/drm/nouveau
          # mv nouveau.ko nouveau.ko-old
          # reboot


          dirty solution but working, hope it will help. Of course, all was fine in 17.10.






          share|improve this answer



























            up vote
            1
            down vote













            https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1784598



            try:



            sudo systemctl disable nvidia-fallback.service





            share|improve this answer



























              up vote
              0
              down vote













              Don't forget to disable Secure Boot in BIOS especially when you want nvidia (and not nouveau) driver working. Otherwise it will quite always fall back back to nouveau no matter what you do.



              Also note that "Secure Boot" option can be hidden in BIOS under various options on various places and often that option is not saying anything about "Secure Boot" but sometimes it's called "Other OS" similar. Every BIOS can be quite unique here. It took me several days of trying various approaches until I went back to BIOS as last resort. It cannot be emphasized enough especially when you are upgrading 18.04 from older version.






              share|improve this answer




















                Your Answer







                StackExchange.ready(function()
                var channelOptions =
                tags: "".split(" "),
                id: "89"
                ;
                initTagRenderer("".split(" "), "".split(" "), channelOptions);

                StackExchange.using("externalEditor", function()
                // Have to fire editor after snippets, if snippets enabled
                if (StackExchange.settings.snippets.snippetsEnabled)
                StackExchange.using("snippets", function()
                createEditor();
                );

                else
                createEditor();

                );

                function createEditor()
                StackExchange.prepareEditor(
                heartbeatType: 'answer',
                convertImagesToLinks: true,
                noModals: false,
                showLowRepImageUploadWarning: true,
                reputationToPostImages: 10,
                bindNavPrevention: true,
                postfix: "",
                onDemand: true,
                discardSelector: ".discard-answer"
                ,immediatelyShowMarkdownHelp:true
                );



                );








                 

                draft saved


                draft discarded


















                StackExchange.ready(
                function ()
                StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1031511%2fcant-disable-nouveau-drivers-in-ubuntu-18-04%23new-answer', 'question_page');

                );

                Post as a guest






























                4 Answers
                4






                active

                oldest

                votes








                4 Answers
                4






                active

                oldest

                votes









                active

                oldest

                votes






                active

                oldest

                votes








                up vote
                3
                down vote



                accepted










                I found the solution. I'll write it here for who may have the same problem.



                My gdm3 session was running in wayland. To check it:



                 $ loginctl
                SESSION UID USER SEAT TTY
                2 1000 velix seat0 tty2
                c2 1000 velix
                c1 120 gdm seat0 tty1


                The command loginctl show-session <session-n> -p Type show the session type:



                $ loginctl show-session c1 -p Type
                Type=Wayland


                To change it, edit the file /etc/gdm3/custom.conf and uncomment the line WaylandEnable=false.



                After rebooting:



                $ loginctl show-session c1 -p Type
                Type=x11


                Now blacklisting nouveau drivers in /etc/modprobe.d/blacklist.conf (as in the question) works and doesn't give the above error.



                The key point is to run xorg instead of wayland



                (That's why it was working in my 17.10 ubuntu, forced to run xorg)






                share|improve this answer






















                • +1 Thanks for sharing. Don't forget to accept your answer by clicking check mark next to it in a day or so when it lets you.
                  – WinEunuuchs2Unix
                  May 4 at 23:13







                • 1




                  Gives black screen on a MacBook, answer no longer works?
                  – Gabor
                  May 9 at 2:10










                • My answer is 5 days old. This method is still working on my notebook.
                  – velix
                  May 9 at 16:24










                • On a MacBook, where I have the error same as in your screenshot, I only get a black screen. Loginctl also errors out with Failed to create bus connection
                  – Gabor
                  May 9 at 20:24










                • I think it's a different problem. Open a new question and put more info in that.
                  – velix
                  May 10 at 9:58














                up vote
                3
                down vote



                accepted










                I found the solution. I'll write it here for who may have the same problem.



                My gdm3 session was running in wayland. To check it:



                 $ loginctl
                SESSION UID USER SEAT TTY
                2 1000 velix seat0 tty2
                c2 1000 velix
                c1 120 gdm seat0 tty1


                The command loginctl show-session <session-n> -p Type show the session type:



                $ loginctl show-session c1 -p Type
                Type=Wayland


                To change it, edit the file /etc/gdm3/custom.conf and uncomment the line WaylandEnable=false.



                After rebooting:



                $ loginctl show-session c1 -p Type
                Type=x11


                Now blacklisting nouveau drivers in /etc/modprobe.d/blacklist.conf (as in the question) works and doesn't give the above error.



                The key point is to run xorg instead of wayland



                (That's why it was working in my 17.10 ubuntu, forced to run xorg)






                share|improve this answer






















                • +1 Thanks for sharing. Don't forget to accept your answer by clicking check mark next to it in a day or so when it lets you.
                  – WinEunuuchs2Unix
                  May 4 at 23:13







                • 1




                  Gives black screen on a MacBook, answer no longer works?
                  – Gabor
                  May 9 at 2:10










                • My answer is 5 days old. This method is still working on my notebook.
                  – velix
                  May 9 at 16:24










                • On a MacBook, where I have the error same as in your screenshot, I only get a black screen. Loginctl also errors out with Failed to create bus connection
                  – Gabor
                  May 9 at 20:24










                • I think it's a different problem. Open a new question and put more info in that.
                  – velix
                  May 10 at 9:58












                up vote
                3
                down vote



                accepted







                up vote
                3
                down vote



                accepted






                I found the solution. I'll write it here for who may have the same problem.



                My gdm3 session was running in wayland. To check it:



                 $ loginctl
                SESSION UID USER SEAT TTY
                2 1000 velix seat0 tty2
                c2 1000 velix
                c1 120 gdm seat0 tty1


                The command loginctl show-session <session-n> -p Type show the session type:



                $ loginctl show-session c1 -p Type
                Type=Wayland


                To change it, edit the file /etc/gdm3/custom.conf and uncomment the line WaylandEnable=false.



                After rebooting:



                $ loginctl show-session c1 -p Type
                Type=x11


                Now blacklisting nouveau drivers in /etc/modprobe.d/blacklist.conf (as in the question) works and doesn't give the above error.



                The key point is to run xorg instead of wayland



                (That's why it was working in my 17.10 ubuntu, forced to run xorg)






                share|improve this answer














                I found the solution. I'll write it here for who may have the same problem.



                My gdm3 session was running in wayland. To check it:



                 $ loginctl
                SESSION UID USER SEAT TTY
                2 1000 velix seat0 tty2
                c2 1000 velix
                c1 120 gdm seat0 tty1


                The command loginctl show-session <session-n> -p Type show the session type:



                $ loginctl show-session c1 -p Type
                Type=Wayland


                To change it, edit the file /etc/gdm3/custom.conf and uncomment the line WaylandEnable=false.



                After rebooting:



                $ loginctl show-session c1 -p Type
                Type=x11


                Now blacklisting nouveau drivers in /etc/modprobe.d/blacklist.conf (as in the question) works and doesn't give the above error.



                The key point is to run xorg instead of wayland



                (That's why it was working in my 17.10 ubuntu, forced to run xorg)







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited May 29 at 17:57

























                answered May 4 at 13:34









                velix

                236213




                236213











                • +1 Thanks for sharing. Don't forget to accept your answer by clicking check mark next to it in a day or so when it lets you.
                  – WinEunuuchs2Unix
                  May 4 at 23:13







                • 1




                  Gives black screen on a MacBook, answer no longer works?
                  – Gabor
                  May 9 at 2:10










                • My answer is 5 days old. This method is still working on my notebook.
                  – velix
                  May 9 at 16:24










                • On a MacBook, where I have the error same as in your screenshot, I only get a black screen. Loginctl also errors out with Failed to create bus connection
                  – Gabor
                  May 9 at 20:24










                • I think it's a different problem. Open a new question and put more info in that.
                  – velix
                  May 10 at 9:58
















                • +1 Thanks for sharing. Don't forget to accept your answer by clicking check mark next to it in a day or so when it lets you.
                  – WinEunuuchs2Unix
                  May 4 at 23:13







                • 1




                  Gives black screen on a MacBook, answer no longer works?
                  – Gabor
                  May 9 at 2:10










                • My answer is 5 days old. This method is still working on my notebook.
                  – velix
                  May 9 at 16:24










                • On a MacBook, where I have the error same as in your screenshot, I only get a black screen. Loginctl also errors out with Failed to create bus connection
                  – Gabor
                  May 9 at 20:24










                • I think it's a different problem. Open a new question and put more info in that.
                  – velix
                  May 10 at 9:58















                +1 Thanks for sharing. Don't forget to accept your answer by clicking check mark next to it in a day or so when it lets you.
                – WinEunuuchs2Unix
                May 4 at 23:13





                +1 Thanks for sharing. Don't forget to accept your answer by clicking check mark next to it in a day or so when it lets you.
                – WinEunuuchs2Unix
                May 4 at 23:13





                1




                1




                Gives black screen on a MacBook, answer no longer works?
                – Gabor
                May 9 at 2:10




                Gives black screen on a MacBook, answer no longer works?
                – Gabor
                May 9 at 2:10












                My answer is 5 days old. This method is still working on my notebook.
                – velix
                May 9 at 16:24




                My answer is 5 days old. This method is still working on my notebook.
                – velix
                May 9 at 16:24












                On a MacBook, where I have the error same as in your screenshot, I only get a black screen. Loginctl also errors out with Failed to create bus connection
                – Gabor
                May 9 at 20:24




                On a MacBook, where I have the error same as in your screenshot, I only get a black screen. Loginctl also errors out with Failed to create bus connection
                – Gabor
                May 9 at 20:24












                I think it's a different problem. Open a new question and put more info in that.
                – velix
                May 10 at 9:58




                I think it's a different problem. Open a new question and put more info in that.
                – velix
                May 10 at 9:58












                up vote
                1
                down vote













                Got exactly same problem, my configuration is x11 (returned by loginctl command).
                The only way working for me at the moment is to rename the nouveau file module.



                # pwd
                /lib/modules/4.15.0-20-generic/kernel/drivers/gpu/drm/nouveau
                # mv nouveau.ko nouveau.ko-old
                # reboot


                dirty solution but working, hope it will help. Of course, all was fine in 17.10.






                share|improve this answer
























                  up vote
                  1
                  down vote













                  Got exactly same problem, my configuration is x11 (returned by loginctl command).
                  The only way working for me at the moment is to rename the nouveau file module.



                  # pwd
                  /lib/modules/4.15.0-20-generic/kernel/drivers/gpu/drm/nouveau
                  # mv nouveau.ko nouveau.ko-old
                  # reboot


                  dirty solution but working, hope it will help. Of course, all was fine in 17.10.






                  share|improve this answer






















                    up vote
                    1
                    down vote










                    up vote
                    1
                    down vote









                    Got exactly same problem, my configuration is x11 (returned by loginctl command).
                    The only way working for me at the moment is to rename the nouveau file module.



                    # pwd
                    /lib/modules/4.15.0-20-generic/kernel/drivers/gpu/drm/nouveau
                    # mv nouveau.ko nouveau.ko-old
                    # reboot


                    dirty solution but working, hope it will help. Of course, all was fine in 17.10.






                    share|improve this answer












                    Got exactly same problem, my configuration is x11 (returned by loginctl command).
                    The only way working for me at the moment is to rename the nouveau file module.



                    # pwd
                    /lib/modules/4.15.0-20-generic/kernel/drivers/gpu/drm/nouveau
                    # mv nouveau.ko nouveau.ko-old
                    # reboot


                    dirty solution but working, hope it will help. Of course, all was fine in 17.10.







                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered May 23 at 16:30









                    lightman

                    112




                    112




















                        up vote
                        1
                        down vote













                        https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1784598



                        try:



                        sudo systemctl disable nvidia-fallback.service





                        share|improve this answer
























                          up vote
                          1
                          down vote













                          https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1784598



                          try:



                          sudo systemctl disable nvidia-fallback.service





                          share|improve this answer






















                            up vote
                            1
                            down vote










                            up vote
                            1
                            down vote









                            https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1784598



                            try:



                            sudo systemctl disable nvidia-fallback.service





                            share|improve this answer












                            https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1784598



                            try:



                            sudo systemctl disable nvidia-fallback.service






                            share|improve this answer












                            share|improve this answer



                            share|improve this answer










                            answered Jul 31 at 10:10









                            heeen

                            1112




                            1112




















                                up vote
                                0
                                down vote













                                Don't forget to disable Secure Boot in BIOS especially when you want nvidia (and not nouveau) driver working. Otherwise it will quite always fall back back to nouveau no matter what you do.



                                Also note that "Secure Boot" option can be hidden in BIOS under various options on various places and often that option is not saying anything about "Secure Boot" but sometimes it's called "Other OS" similar. Every BIOS can be quite unique here. It took me several days of trying various approaches until I went back to BIOS as last resort. It cannot be emphasized enough especially when you are upgrading 18.04 from older version.






                                share|improve this answer
























                                  up vote
                                  0
                                  down vote













                                  Don't forget to disable Secure Boot in BIOS especially when you want nvidia (and not nouveau) driver working. Otherwise it will quite always fall back back to nouveau no matter what you do.



                                  Also note that "Secure Boot" option can be hidden in BIOS under various options on various places and often that option is not saying anything about "Secure Boot" but sometimes it's called "Other OS" similar. Every BIOS can be quite unique here. It took me several days of trying various approaches until I went back to BIOS as last resort. It cannot be emphasized enough especially when you are upgrading 18.04 from older version.






                                  share|improve this answer






















                                    up vote
                                    0
                                    down vote










                                    up vote
                                    0
                                    down vote









                                    Don't forget to disable Secure Boot in BIOS especially when you want nvidia (and not nouveau) driver working. Otherwise it will quite always fall back back to nouveau no matter what you do.



                                    Also note that "Secure Boot" option can be hidden in BIOS under various options on various places and often that option is not saying anything about "Secure Boot" but sometimes it's called "Other OS" similar. Every BIOS can be quite unique here. It took me several days of trying various approaches until I went back to BIOS as last resort. It cannot be emphasized enough especially when you are upgrading 18.04 from older version.






                                    share|improve this answer












                                    Don't forget to disable Secure Boot in BIOS especially when you want nvidia (and not nouveau) driver working. Otherwise it will quite always fall back back to nouveau no matter what you do.



                                    Also note that "Secure Boot" option can be hidden in BIOS under various options on various places and often that option is not saying anything about "Secure Boot" but sometimes it's called "Other OS" similar. Every BIOS can be quite unique here. It took me several days of trying various approaches until I went back to BIOS as last resort. It cannot be emphasized enough especially when you are upgrading 18.04 from older version.







                                    share|improve this answer












                                    share|improve this answer



                                    share|improve this answer










                                    answered Jul 19 at 19:13









                                    crdev

                                    1




                                    1






















                                         

                                        draft saved


                                        draft discarded


























                                         


                                        draft saved


                                        draft discarded














                                        StackExchange.ready(
                                        function ()
                                        StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1031511%2fcant-disable-nouveau-drivers-in-ubuntu-18-04%23new-answer', 'question_page');

                                        );

                                        Post as a guest













































































                                        Popular posts from this blog

                                        pylint3 and pip3 broken

                                        Missing snmpget and snmpwalk

                                        How to enroll fingerprints to Ubuntu 17.10 with VFS491