Ubuntu 18.04 boot issues

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








up vote
4
down vote

favorite
2












I upgraded my OS to Ubuntu 18.04 from Ubuntu 17.10 today after it was released.



The boot stops at a black screen saying nothing just one line, something about my SSD being loaded. The only way to start the OS is removing all the nvidia packages and replacing quiet splash by nomodeset in boot options on grub.



I need to know why this works and how do I fix the problem so that I don't have to do this all the time and start using my Nvidia drivers.



I have nvidia-390 driver installed







share|improve this question






















  • Related: askubuntu.com/questions/747314/is-nomodeset-still-required
    – Melebius
    Apr 26 at 10:20










  • To close voters: according to release schedule of bionic the release date is today, so closing as off topic because of developtment version not applies anymore! See wiki.ubuntu.com/BionicBeaver/ReleaseSchedule
    – Videonauth
    Apr 26 at 10:59










  • I am not talking about the development version here. I upgraded my ubuntu today after the final version was released on the update channel of ubuntu. Am I not getting something correct, in that case please clarify
    – akabhirav
    Apr 26 at 11:18










  • Yeah, same problem here, I can't get xorg to work with gdm, and nvidia-390 to work with wayland. I somehow ended up with wayland as default. Either nvidia drivers are broken af, or xorg is broken or both. Upgrade for me was a disaster.
    – Von Goofy
    Apr 27 at 9:22






  • 1




    thank you both, It actually worked and it did startup, but alas reinstalling can't be really the answer. I did reinstall but others might find it very laborious. I keep my files organized because I format a lot, just to keep experimenting with my system
    – akabhirav
    Apr 27 at 17:07














up vote
4
down vote

favorite
2












I upgraded my OS to Ubuntu 18.04 from Ubuntu 17.10 today after it was released.



The boot stops at a black screen saying nothing just one line, something about my SSD being loaded. The only way to start the OS is removing all the nvidia packages and replacing quiet splash by nomodeset in boot options on grub.



I need to know why this works and how do I fix the problem so that I don't have to do this all the time and start using my Nvidia drivers.



I have nvidia-390 driver installed







share|improve this question






















  • Related: askubuntu.com/questions/747314/is-nomodeset-still-required
    – Melebius
    Apr 26 at 10:20










  • To close voters: according to release schedule of bionic the release date is today, so closing as off topic because of developtment version not applies anymore! See wiki.ubuntu.com/BionicBeaver/ReleaseSchedule
    – Videonauth
    Apr 26 at 10:59










  • I am not talking about the development version here. I upgraded my ubuntu today after the final version was released on the update channel of ubuntu. Am I not getting something correct, in that case please clarify
    – akabhirav
    Apr 26 at 11:18










  • Yeah, same problem here, I can't get xorg to work with gdm, and nvidia-390 to work with wayland. I somehow ended up with wayland as default. Either nvidia drivers are broken af, or xorg is broken or both. Upgrade for me was a disaster.
    – Von Goofy
    Apr 27 at 9:22






  • 1




    thank you both, It actually worked and it did startup, but alas reinstalling can't be really the answer. I did reinstall but others might find it very laborious. I keep my files organized because I format a lot, just to keep experimenting with my system
    – akabhirav
    Apr 27 at 17:07












up vote
4
down vote

favorite
2









up vote
4
down vote

favorite
2






2





I upgraded my OS to Ubuntu 18.04 from Ubuntu 17.10 today after it was released.



The boot stops at a black screen saying nothing just one line, something about my SSD being loaded. The only way to start the OS is removing all the nvidia packages and replacing quiet splash by nomodeset in boot options on grub.



I need to know why this works and how do I fix the problem so that I don't have to do this all the time and start using my Nvidia drivers.



I have nvidia-390 driver installed







share|improve this question














I upgraded my OS to Ubuntu 18.04 from Ubuntu 17.10 today after it was released.



The boot stops at a black screen saying nothing just one line, something about my SSD being loaded. The only way to start the OS is removing all the nvidia packages and replacing quiet splash by nomodeset in boot options on grub.



I need to know why this works and how do I fix the problem so that I don't have to do this all the time and start using my Nvidia drivers.



I have nvidia-390 driver installed









share|improve this question













share|improve this question




share|improve this question








edited Apr 27 at 9:18

























asked Apr 26 at 10:18









akabhirav

1,00521029




1,00521029











  • Related: askubuntu.com/questions/747314/is-nomodeset-still-required
    – Melebius
    Apr 26 at 10:20










  • To close voters: according to release schedule of bionic the release date is today, so closing as off topic because of developtment version not applies anymore! See wiki.ubuntu.com/BionicBeaver/ReleaseSchedule
    – Videonauth
    Apr 26 at 10:59










  • I am not talking about the development version here. I upgraded my ubuntu today after the final version was released on the update channel of ubuntu. Am I not getting something correct, in that case please clarify
    – akabhirav
    Apr 26 at 11:18










  • Yeah, same problem here, I can't get xorg to work with gdm, and nvidia-390 to work with wayland. I somehow ended up with wayland as default. Either nvidia drivers are broken af, or xorg is broken or both. Upgrade for me was a disaster.
    – Von Goofy
    Apr 27 at 9:22






  • 1




    thank you both, It actually worked and it did startup, but alas reinstalling can't be really the answer. I did reinstall but others might find it very laborious. I keep my files organized because I format a lot, just to keep experimenting with my system
    – akabhirav
    Apr 27 at 17:07
















  • Related: askubuntu.com/questions/747314/is-nomodeset-still-required
    – Melebius
    Apr 26 at 10:20










  • To close voters: according to release schedule of bionic the release date is today, so closing as off topic because of developtment version not applies anymore! See wiki.ubuntu.com/BionicBeaver/ReleaseSchedule
    – Videonauth
    Apr 26 at 10:59










  • I am not talking about the development version here. I upgraded my ubuntu today after the final version was released on the update channel of ubuntu. Am I not getting something correct, in that case please clarify
    – akabhirav
    Apr 26 at 11:18










  • Yeah, same problem here, I can't get xorg to work with gdm, and nvidia-390 to work with wayland. I somehow ended up with wayland as default. Either nvidia drivers are broken af, or xorg is broken or both. Upgrade for me was a disaster.
    – Von Goofy
    Apr 27 at 9:22






  • 1




    thank you both, It actually worked and it did startup, but alas reinstalling can't be really the answer. I did reinstall but others might find it very laborious. I keep my files organized because I format a lot, just to keep experimenting with my system
    – akabhirav
    Apr 27 at 17:07















Related: askubuntu.com/questions/747314/is-nomodeset-still-required
– Melebius
Apr 26 at 10:20




Related: askubuntu.com/questions/747314/is-nomodeset-still-required
– Melebius
Apr 26 at 10:20












To close voters: according to release schedule of bionic the release date is today, so closing as off topic because of developtment version not applies anymore! See wiki.ubuntu.com/BionicBeaver/ReleaseSchedule
– Videonauth
Apr 26 at 10:59




To close voters: according to release schedule of bionic the release date is today, so closing as off topic because of developtment version not applies anymore! See wiki.ubuntu.com/BionicBeaver/ReleaseSchedule
– Videonauth
Apr 26 at 10:59












I am not talking about the development version here. I upgraded my ubuntu today after the final version was released on the update channel of ubuntu. Am I not getting something correct, in that case please clarify
– akabhirav
Apr 26 at 11:18




I am not talking about the development version here. I upgraded my ubuntu today after the final version was released on the update channel of ubuntu. Am I not getting something correct, in that case please clarify
– akabhirav
Apr 26 at 11:18












Yeah, same problem here, I can't get xorg to work with gdm, and nvidia-390 to work with wayland. I somehow ended up with wayland as default. Either nvidia drivers are broken af, or xorg is broken or both. Upgrade for me was a disaster.
– Von Goofy
Apr 27 at 9:22




Yeah, same problem here, I can't get xorg to work with gdm, and nvidia-390 to work with wayland. I somehow ended up with wayland as default. Either nvidia drivers are broken af, or xorg is broken or both. Upgrade for me was a disaster.
– Von Goofy
Apr 27 at 9:22




1




1




thank you both, It actually worked and it did startup, but alas reinstalling can't be really the answer. I did reinstall but others might find it very laborious. I keep my files organized because I format a lot, just to keep experimenting with my system
– akabhirav
Apr 27 at 17:07




thank you both, It actually worked and it did startup, but alas reinstalling can't be really the answer. I did reinstall but others might find it very laborious. I keep my files organized because I format a lot, just to keep experimenting with my system
– akabhirav
Apr 27 at 17:07










1 Answer
1






active

oldest

votes

















up vote
1
down vote













This helped me:




  • Open Terminal and run:



    sudo gedit /etc/default/grub



  • change GRUB_CMDLINE_LINUX=...... to:



    GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
    GRUB_CMDLINE_LINUX="nouveau.modeset=0"



  • Delete any extras like nomodeset,acpi=off,etc and after that update grub:



    sudo update-grub


  • Restart.


Of course its better to first test this from grub (while rebooting), editing the starting line (Ubuntu-line) with the e-key.






share|improve this answer






















  • @aman-mittal Could you please review my edits and also review the editing help to improve the readability of your own edits in the future... ;-)
    – Fabby
    May 25 at 18:27







  • 1




    @Fabby Thank you for the suggestion. It's always fun to know more about this site. I'll keep in mind those points. :)
    – Kulfy
    May 25 at 18:32










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%2f1028359%2fubuntu-18-04-boot-issues%23new-answer', 'question_page');

);

Post as a guest






























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
1
down vote













This helped me:




  • Open Terminal and run:



    sudo gedit /etc/default/grub



  • change GRUB_CMDLINE_LINUX=...... to:



    GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
    GRUB_CMDLINE_LINUX="nouveau.modeset=0"



  • Delete any extras like nomodeset,acpi=off,etc and after that update grub:



    sudo update-grub


  • Restart.


Of course its better to first test this from grub (while rebooting), editing the starting line (Ubuntu-line) with the e-key.






share|improve this answer






















  • @aman-mittal Could you please review my edits and also review the editing help to improve the readability of your own edits in the future... ;-)
    – Fabby
    May 25 at 18:27







  • 1




    @Fabby Thank you for the suggestion. It's always fun to know more about this site. I'll keep in mind those points. :)
    – Kulfy
    May 25 at 18:32














up vote
1
down vote













This helped me:




  • Open Terminal and run:



    sudo gedit /etc/default/grub



  • change GRUB_CMDLINE_LINUX=...... to:



    GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
    GRUB_CMDLINE_LINUX="nouveau.modeset=0"



  • Delete any extras like nomodeset,acpi=off,etc and after that update grub:



    sudo update-grub


  • Restart.


Of course its better to first test this from grub (while rebooting), editing the starting line (Ubuntu-line) with the e-key.






share|improve this answer






















  • @aman-mittal Could you please review my edits and also review the editing help to improve the readability of your own edits in the future... ;-)
    – Fabby
    May 25 at 18:27







  • 1




    @Fabby Thank you for the suggestion. It's always fun to know more about this site. I'll keep in mind those points. :)
    – Kulfy
    May 25 at 18:32












up vote
1
down vote










up vote
1
down vote









This helped me:




  • Open Terminal and run:



    sudo gedit /etc/default/grub



  • change GRUB_CMDLINE_LINUX=...... to:



    GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
    GRUB_CMDLINE_LINUX="nouveau.modeset=0"



  • Delete any extras like nomodeset,acpi=off,etc and after that update grub:



    sudo update-grub


  • Restart.


Of course its better to first test this from grub (while rebooting), editing the starting line (Ubuntu-line) with the e-key.






share|improve this answer














This helped me:




  • Open Terminal and run:



    sudo gedit /etc/default/grub



  • change GRUB_CMDLINE_LINUX=...... to:



    GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
    GRUB_CMDLINE_LINUX="nouveau.modeset=0"



  • Delete any extras like nomodeset,acpi=off,etc and after that update grub:



    sudo update-grub


  • Restart.


Of course its better to first test this from grub (while rebooting), editing the starting line (Ubuntu-line) with the e-key.







share|improve this answer














share|improve this answer



share|improve this answer








edited May 25 at 18:26









Fabby

24.2k1352153




24.2k1352153










answered May 25 at 18:18









ChristArmy

111




111











  • @aman-mittal Could you please review my edits and also review the editing help to improve the readability of your own edits in the future... ;-)
    – Fabby
    May 25 at 18:27







  • 1




    @Fabby Thank you for the suggestion. It's always fun to know more about this site. I'll keep in mind those points. :)
    – Kulfy
    May 25 at 18:32
















  • @aman-mittal Could you please review my edits and also review the editing help to improve the readability of your own edits in the future... ;-)
    – Fabby
    May 25 at 18:27







  • 1




    @Fabby Thank you for the suggestion. It's always fun to know more about this site. I'll keep in mind those points. :)
    – Kulfy
    May 25 at 18:32















@aman-mittal Could you please review my edits and also review the editing help to improve the readability of your own edits in the future... ;-)
– Fabby
May 25 at 18:27





@aman-mittal Could you please review my edits and also review the editing help to improve the readability of your own edits in the future... ;-)
– Fabby
May 25 at 18:27





1




1




@Fabby Thank you for the suggestion. It's always fun to know more about this site. I'll keep in mind those points. :)
– Kulfy
May 25 at 18:32




@Fabby Thank you for the suggestion. It's always fun to know more about this site. I'll keep in mind those points. :)
– Kulfy
May 25 at 18:32

















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1028359%2fubuntu-18-04-boot-issues%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