18.04 Boot to black unless I delete $vt_handoff grub parameter, related to Nvidia drivers?











up vote
0
down vote

favorite












I started having problems booting after I tried to use prime-select for the first time to switch between my laptop's Nvidia GTX 960M and Intel graphics, using the same nvidia-390 driver that had worked fine for months.



The computer would boot to black, then to tty if I put nomodeset in grub, then after reading a zillion Ask Ubuntu pages and reinstalling a lot of packages, I did sudo apt purge *nvidia* and switched to the new nvidia-driver-415. I also added nouveau.modeset=0 to /etc/default/grub.



Now it boots and runs fine, but only if I manually edit grub every time I boot and remove the $vt_handoff parameter that shows up after nouveau.modeset=0. If I don't, it boots to black, and I can't even get a tty. What gives?



Doing some digging, I found an old bug report that suggests that a missing /boot/grub/gfxblacklist.txt file could disable a graphical boot. I don't have that file. I considered installing grub-gfxpayload-lists as suggested by that post, but it looks like it might conflict with more recent grub-related packages and wreck shop. I'm relatively new to linux and hesitant to mess around with the guts of the OS in case I break something I don't understand.



Any ideas? I would greatly appreciate any help.



More details, let me know if I can include anything else:
Dell Inspiron 7559, dual boot with Windows 10 (Secure Boot off);
Ubuntu 18.04.1 LTS;
kernel 4.15.0-39-generic;
graphics Nvidia GeForce GTX 960M/PCIe/SSE2;
GNOME 3.28.2;
/etc/default/grub : link










share|improve this question









New contributor




zygomycete is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
























    up vote
    0
    down vote

    favorite












    I started having problems booting after I tried to use prime-select for the first time to switch between my laptop's Nvidia GTX 960M and Intel graphics, using the same nvidia-390 driver that had worked fine for months.



    The computer would boot to black, then to tty if I put nomodeset in grub, then after reading a zillion Ask Ubuntu pages and reinstalling a lot of packages, I did sudo apt purge *nvidia* and switched to the new nvidia-driver-415. I also added nouveau.modeset=0 to /etc/default/grub.



    Now it boots and runs fine, but only if I manually edit grub every time I boot and remove the $vt_handoff parameter that shows up after nouveau.modeset=0. If I don't, it boots to black, and I can't even get a tty. What gives?



    Doing some digging, I found an old bug report that suggests that a missing /boot/grub/gfxblacklist.txt file could disable a graphical boot. I don't have that file. I considered installing grub-gfxpayload-lists as suggested by that post, but it looks like it might conflict with more recent grub-related packages and wreck shop. I'm relatively new to linux and hesitant to mess around with the guts of the OS in case I break something I don't understand.



    Any ideas? I would greatly appreciate any help.



    More details, let me know if I can include anything else:
    Dell Inspiron 7559, dual boot with Windows 10 (Secure Boot off);
    Ubuntu 18.04.1 LTS;
    kernel 4.15.0-39-generic;
    graphics Nvidia GeForce GTX 960M/PCIe/SSE2;
    GNOME 3.28.2;
    /etc/default/grub : link










    share|improve this question









    New contributor




    zygomycete is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.






















      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I started having problems booting after I tried to use prime-select for the first time to switch between my laptop's Nvidia GTX 960M and Intel graphics, using the same nvidia-390 driver that had worked fine for months.



      The computer would boot to black, then to tty if I put nomodeset in grub, then after reading a zillion Ask Ubuntu pages and reinstalling a lot of packages, I did sudo apt purge *nvidia* and switched to the new nvidia-driver-415. I also added nouveau.modeset=0 to /etc/default/grub.



      Now it boots and runs fine, but only if I manually edit grub every time I boot and remove the $vt_handoff parameter that shows up after nouveau.modeset=0. If I don't, it boots to black, and I can't even get a tty. What gives?



      Doing some digging, I found an old bug report that suggests that a missing /boot/grub/gfxblacklist.txt file could disable a graphical boot. I don't have that file. I considered installing grub-gfxpayload-lists as suggested by that post, but it looks like it might conflict with more recent grub-related packages and wreck shop. I'm relatively new to linux and hesitant to mess around with the guts of the OS in case I break something I don't understand.



      Any ideas? I would greatly appreciate any help.



      More details, let me know if I can include anything else:
      Dell Inspiron 7559, dual boot with Windows 10 (Secure Boot off);
      Ubuntu 18.04.1 LTS;
      kernel 4.15.0-39-generic;
      graphics Nvidia GeForce GTX 960M/PCIe/SSE2;
      GNOME 3.28.2;
      /etc/default/grub : link










      share|improve this question









      New contributor




      zygomycete is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      I started having problems booting after I tried to use prime-select for the first time to switch between my laptop's Nvidia GTX 960M and Intel graphics, using the same nvidia-390 driver that had worked fine for months.



      The computer would boot to black, then to tty if I put nomodeset in grub, then after reading a zillion Ask Ubuntu pages and reinstalling a lot of packages, I did sudo apt purge *nvidia* and switched to the new nvidia-driver-415. I also added nouveau.modeset=0 to /etc/default/grub.



      Now it boots and runs fine, but only if I manually edit grub every time I boot and remove the $vt_handoff parameter that shows up after nouveau.modeset=0. If I don't, it boots to black, and I can't even get a tty. What gives?



      Doing some digging, I found an old bug report that suggests that a missing /boot/grub/gfxblacklist.txt file could disable a graphical boot. I don't have that file. I considered installing grub-gfxpayload-lists as suggested by that post, but it looks like it might conflict with more recent grub-related packages and wreck shop. I'm relatively new to linux and hesitant to mess around with the guts of the OS in case I break something I don't understand.



      Any ideas? I would greatly appreciate any help.



      More details, let me know if I can include anything else:
      Dell Inspiron 7559, dual boot with Windows 10 (Secure Boot off);
      Ubuntu 18.04.1 LTS;
      kernel 4.15.0-39-generic;
      graphics Nvidia GeForce GTX 960M/PCIe/SSE2;
      GNOME 3.28.2;
      /etc/default/grub : link







      boot dual-boot drivers grub2 nvidia






      share|improve this question









      New contributor




      zygomycete is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      share|improve this question









      New contributor




      zygomycete is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      share|improve this question




      share|improve this question








      edited 2 days ago





















      New contributor




      zygomycete is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked 2 days ago









      zygomycete

      11




      11




      New contributor




      zygomycete is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      zygomycete is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      zygomycete is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.



























          active

          oldest

          votes











          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: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });






          zygomycete is a new contributor. Be nice, and check out our Code of Conduct.










           

          draft saved


          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1093531%2f18-04-boot-to-black-unless-i-delete-vt-handoff-grub-parameter-related-to-nvidi%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown






























          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          zygomycete is a new contributor. Be nice, and check out our Code of Conduct.










           

          draft saved


          draft discarded


















          zygomycete is a new contributor. Be nice, and check out our Code of Conduct.













          zygomycete is a new contributor. Be nice, and check out our Code of Conduct.












          zygomycete is a new contributor. Be nice, and check out our Code of Conduct.















           


          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1093531%2f18-04-boot-to-black-unless-i-delete-vt-handoff-grub-parameter-related-to-nvidi%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

          Mangá

           ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕