Ubuntu boots to purple screen with Nvidia MSI 1080 and nomodeset
Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
I tried to solve this issue for about a week now, but can't seem to get around it. During installation had this same problem and nomodeset wasn't the solution, but had to install it switching to the Intel graphics. After the installation I kept using the Intel graphics, was able to boot and install the drivers, switch back to the Nvidia GPU, but still have to use nomodeset during every boot.
Now that would be simple enough (and this post explains it how to do so: How do I set 'nomodeset' after I've already installed Ubuntu?), but still every single time I have to press enter at least to get it to boot or edit the grub entry and - without modifying anything - I can boot from there. This is super agonizing because I'm not always there and we tend to use the machine remotely and after every reboot someone has to go there and boot as explain above.
HW specs: Intel 7700 i7, MSI 1080, 16GB ram, 250GB SSD, UEFI only. (would love to post more details, but the box is down again and the office is closed for the weekend...)
I don't think that this is a duplicate as I couldn't find an exact problem and a solution around here, but if it is I apologize in advance.
EDIT: /etc/default/grub/
GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="nomodeset"
GRUB_CMDLINE_LINUX=""
boot grub2 nvidia
asked Apr 14 at 6:20
Adathor
56118
 |Â
show 2 more comments
up vote
0
down vote
favorite
I tried to solve this issue for about a week now, but can't seem to get around it. During installation had this same problem and nomodeset wasn't the solution, but had to install it switching to the Intel graphics. After the installation I kept using the Intel graphics, was able to boot and install the drivers, switch back to the Nvidia GPU, but still have to use nomodeset during every boot.
Now that would be simple enough (and this post explains it how to do so: How do I set 'nomodeset' after I've already installed Ubuntu?), but still every single time I have to press enter at least to get it to boot or edit the grub entry and - without modifying anything - I can boot from there. This is super agonizing because I'm not always there and we tend to use the machine remotely and after every reboot someone has to go there and boot as explain above.
HW specs: Intel 7700 i7, MSI 1080, 16GB ram, 250GB SSD, UEFI only. (would love to post more details, but the box is down again and the office is closed for the weekend...)
I don't think that this is a duplicate as I couldn't find an exact problem and a solution around here, but if it is I apologize in advance.
EDIT: /etc/default/grub/
GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="nomodeset"
GRUB_CMDLINE_LINUX=""
boot grub2 nvidia
asked Apr 14 at 6:20
Adathor
56118
1
Yes, there is more that you need to supply. Please supply your/etc/default/grub. Also please indicate if you ransudo apt upgate-grubafter making the change.
– L. D. James
Apr 14 at 6:38
Yes I know, but I just can't access the box right now. The <code> /etc/default/grub </code> is: GRUB_DEFAULT=0 GRUB_HIDDEN_TIMEOUT=0 GRUB_HIDDEN_TIMEOUT_QUIET=true GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR=lsb_release -i -s 2> /dev/null || echo DebianGRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset" GRUB_CMDLINE_LINUX="" Updated the grub of course and the <code>nomodeset</code> is present in the kernel line after rebooting and checking the entry.
– Adathor
Apr 14 at 6:51
I can't make out weather your output is formatted correctly. If you would paste the same thing here: Edit Your Question it would be easier to analyze. Also, it'll make your issue clearer to others looking at the question. How did you check the entry? I understand you can't do it now, but when you get to the office run this:cat /proc/cmdlinewithout manually adding it at boot. You can useCtrl+Alt+F2to get to a console, if the GUI doesn't work.
– L. D. James
Apr 14 at 6:54
Yea sorry, updated accordingly.
– Adathor
Apr 14 at 6:57
Your response was quick. I had mistakenly pressed ENTER when I was still editing my comment. Can you elaborate on this: How did you check the entry? to verify the presence during boot? I understand you can't do it now, but when you get to the office run this: cat /proc/cmdline without manually adding it at boot. You can use Ctrl+Alt+F2 to get to a console, if the GUI doesn't work
– L. D. James
Apr 14 at 7:01
 |Â
show 2 more comments
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I tried to solve this issue for about a week now, but can't seem to get around it. During installation had this same problem and nomodeset wasn't the solution, but had to install it switching to the Intel graphics. After the installation I kept using the Intel graphics, was able to boot and install the drivers, switch back to the Nvidia GPU, but still have to use nomodeset during every boot.
Now that would be simple enough (and this post explains it how to do so: How do I set 'nomodeset' after I've already installed Ubuntu?), but still every single time I have to press enter at least to get it to boot or edit the grub entry and - without modifying anything - I can boot from there. This is super agonizing because I'm not always there and we tend to use the machine remotely and after every reboot someone has to go there and boot as explain above.
HW specs: Intel 7700 i7, MSI 1080, 16GB ram, 250GB SSD, UEFI only. (would love to post more details, but the box is down again and the office is closed for the weekend...)
I don't think that this is a duplicate as I couldn't find an exact problem and a solution around here, but if it is I apologize in advance.
EDIT: /etc/default/grub/
GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="nomodeset"
GRUB_CMDLINE_LINUX=""
boot grub2 nvidia
asked Apr 14 at 6:20
Adathor
56118
I tried to solve this issue for about a week now, but can't seem to get around it. During installation had this same problem and nomodeset wasn't the solution, but had to install it switching to the Intel graphics. After the installation I kept using the Intel graphics, was able to boot and install the drivers, switch back to the Nvidia GPU, but still have to use nomodeset during every boot.
Now that would be simple enough (and this post explains it how to do so: How do I set 'nomodeset' after I've already installed Ubuntu?), but still every single time I have to press enter at least to get it to boot or edit the grub entry and - without modifying anything - I can boot from there. This is super agonizing because I'm not always there and we tend to use the machine remotely and after every reboot someone has to go there and boot as explain above.
HW specs: Intel 7700 i7, MSI 1080, 16GB ram, 250GB SSD, UEFI only. (would love to post more details, but the box is down again and the office is closed for the weekend...)
I don't think that this is a duplicate as I couldn't find an exact problem and a solution around here, but if it is I apologize in advance.
EDIT: /etc/default/grub/
GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="nomodeset"
GRUB_CMDLINE_LINUX=""
boot grub2 nvidia
boot grub2 nvidia
asked Apr 14 at 6:20
Adathor
56118
asked Apr 14 at 6:20
Adathor
56118
edited Apr 14 at 6:56
asked Apr 14 at 6:20
Adathor
56118
asked Apr 14 at 6:20
Adathor
56118
asked Apr 14 at 6:20
Adathor
56118
56118
1
Yes, there is more that you need to supply. Please supply your/etc/default/grub. Also please indicate if you ransudo apt upgate-grubafter making the change.
– L. D. James
Apr 14 at 6:38
Yes I know, but I just can't access the box right now. The <code> /etc/default/grub </code> is: GRUB_DEFAULT=0 GRUB_HIDDEN_TIMEOUT=0 GRUB_HIDDEN_TIMEOUT_QUIET=true GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR=lsb_release -i -s 2> /dev/null || echo DebianGRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset" GRUB_CMDLINE_LINUX="" Updated the grub of course and the <code>nomodeset</code> is present in the kernel line after rebooting and checking the entry.
– Adathor
Apr 14 at 6:51
I can't make out weather your output is formatted correctly. If you would paste the same thing here: Edit Your Question it would be easier to analyze. Also, it'll make your issue clearer to others looking at the question. How did you check the entry? I understand you can't do it now, but when you get to the office run this:cat /proc/cmdlinewithout manually adding it at boot. You can useCtrl+Alt+F2to get to a console, if the GUI doesn't work.
– L. D. James
Apr 14 at 6:54
Yea sorry, updated accordingly.
– Adathor
Apr 14 at 6:57
Your response was quick. I had mistakenly pressed ENTER when I was still editing my comment. Can you elaborate on this: How did you check the entry? to verify the presence during boot? I understand you can't do it now, but when you get to the office run this: cat /proc/cmdline without manually adding it at boot. You can use Ctrl+Alt+F2 to get to a console, if the GUI doesn't work
– L. D. James
Apr 14 at 7:01
 |Â
show 2 more comments
1
Yes, there is more that you need to supply. Please supply your/etc/default/grub. Also please indicate if you ransudo apt upgate-grubafter making the change.
– L. D. James
Apr 14 at 6:38
Yes I know, but I just can't access the box right now. The <code> /etc/default/grub </code> is: GRUB_DEFAULT=0 GRUB_HIDDEN_TIMEOUT=0 GRUB_HIDDEN_TIMEOUT_QUIET=true GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR=lsb_release -i -s 2> /dev/null || echo DebianGRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset" GRUB_CMDLINE_LINUX="" Updated the grub of course and the <code>nomodeset</code> is present in the kernel line after rebooting and checking the entry.
– Adathor
Apr 14 at 6:51
I can't make out weather your output is formatted correctly. If you would paste the same thing here: Edit Your Question it would be easier to analyze. Also, it'll make your issue clearer to others looking at the question. How did you check the entry? I understand you can't do it now, but when you get to the office run this:cat /proc/cmdlinewithout manually adding it at boot. You can useCtrl+Alt+F2to get to a console, if the GUI doesn't work.
– L. D. James
Apr 14 at 6:54
Yea sorry, updated accordingly.
– Adathor
Apr 14 at 6:57
Your response was quick. I had mistakenly pressed ENTER when I was still editing my comment. Can you elaborate on this: How did you check the entry? to verify the presence during boot? I understand you can't do it now, but when you get to the office run this: cat /proc/cmdline without manually adding it at boot. You can use Ctrl+Alt+F2 to get to a console, if the GUI doesn't work
– L. D. James
Apr 14 at 7:01
1
1
Yes, there is more that you need to supply. Please supply your
/etc/default/grub. Also please indicate if you ran sudo apt upgate-grub after making the change.– L. D. James
Apr 14 at 6:38
Yes, there is more that you need to supply. Please supply your
/etc/default/grub. Also please indicate if you ran sudo apt upgate-grub after making the change.– L. D. James
Apr 14 at 6:38
Yes I know, but I just can't access the box right now. The <code> /etc/default/grub </code> is: GRUB_DEFAULT=0 GRUB_HIDDEN_TIMEOUT=0 GRUB_HIDDEN_TIMEOUT_QUIET=true GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR=
lsb_release -i -s 2> /dev/null || echo Debian GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset" GRUB_CMDLINE_LINUX="" Updated the grub of course and the <code>nomodeset</code> is present in the kernel line after rebooting and checking the entry.– Adathor
Apr 14 at 6:51
Yes I know, but I just can't access the box right now. The <code> /etc/default/grub </code> is: GRUB_DEFAULT=0 GRUB_HIDDEN_TIMEOUT=0 GRUB_HIDDEN_TIMEOUT_QUIET=true GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR=
lsb_release -i -s 2> /dev/null || echo Debian GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset" GRUB_CMDLINE_LINUX="" Updated the grub of course and the <code>nomodeset</code> is present in the kernel line after rebooting and checking the entry.– Adathor
Apr 14 at 6:51
I can't make out weather your output is formatted correctly. If you would paste the same thing here: Edit Your Question it would be easier to analyze. Also, it'll make your issue clearer to others looking at the question. How did you check the entry? I understand you can't do it now, but when you get to the office run this:
cat /proc/cmdline without manually adding it at boot. You can use Ctrl+Alt+F2 to get to a console, if the GUI doesn't work.– L. D. James
Apr 14 at 6:54
I can't make out weather your output is formatted correctly. If you would paste the same thing here: Edit Your Question it would be easier to analyze. Also, it'll make your issue clearer to others looking at the question. How did you check the entry? I understand you can't do it now, but when you get to the office run this:
cat /proc/cmdline without manually adding it at boot. You can use Ctrl+Alt+F2 to get to a console, if the GUI doesn't work.– L. D. James
Apr 14 at 6:54
Yea sorry, updated accordingly.
– Adathor
Apr 14 at 6:57
Yea sorry, updated accordingly.
– Adathor
Apr 14 at 6:57
Your response was quick. I had mistakenly pressed ENTER when I was still editing my comment. Can you elaborate on this: How did you check the entry? to verify the presence during boot? I understand you can't do it now, but when you get to the office run this: cat /proc/cmdline without manually adding it at boot. You can use Ctrl+Alt+F2 to get to a console, if the GUI doesn't work
– L. D. James
Apr 14 at 7:01
Your response was quick. I had mistakenly pressed ENTER when I was still editing my comment. Can you elaborate on this: How did you check the entry? to verify the presence during boot? I understand you can't do it now, but when you get to the office run this: cat /proc/cmdline without manually adding it at boot. You can use Ctrl+Alt+F2 to get to a console, if the GUI doesn't work
– L. D. James
Apr 14 at 7:01
 |Â
show 2 more comments
1 Answer
1
active
oldest
votes
up vote
0
down vote
Ok, gave up on this one as it was greatly effecting our work-flow and installed Fedora 27. Everything works as expected.
answered Apr 16 at 8:40
Adathor
56118
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Ok, gave up on this one as it was greatly effecting our work-flow and installed Fedora 27. Everything works as expected.
answered Apr 16 at 8:40
Adathor
56118
add a comment |Â
up vote
0
down vote
Ok, gave up on this one as it was greatly effecting our work-flow and installed Fedora 27. Everything works as expected.
answered Apr 16 at 8:40
Adathor
56118
add a comment |Â
up vote
0
down vote
up vote
0
down vote
Ok, gave up on this one as it was greatly effecting our work-flow and installed Fedora 27. Everything works as expected.
answered Apr 16 at 8:40
Adathor
56118
Ok, gave up on this one as it was greatly effecting our work-flow and installed Fedora 27. Everything works as expected.
answered Apr 16 at 8:40
Adathor
56118
answered Apr 16 at 8:40
Adathor
56118
answered Apr 16 at 8:40
Adathor
56118
answered Apr 16 at 8:40
Adathor
56118
56118
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1024874%2fubuntu-boots-to-purple-screen-with-nvidia-msi-1080-and-nomodeset%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
1
Yes, there is more that you need to supply. Please supply your
/etc/default/grub. Also please indicate if you ransudo apt upgate-grubafter making the change.– L. D. James
Apr 14 at 6:38
Yes I know, but I just can't access the box right now. The <code> /etc/default/grub </code> is: GRUB_DEFAULT=0 GRUB_HIDDEN_TIMEOUT=0 GRUB_HIDDEN_TIMEOUT_QUIET=true GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR=
lsb_release -i -s 2> /dev/null || echo DebianGRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset" GRUB_CMDLINE_LINUX="" Updated the grub of course and the <code>nomodeset</code> is present in the kernel line after rebooting and checking the entry.– Adathor
Apr 14 at 6:51
I can't make out weather your output is formatted correctly. If you would paste the same thing here: Edit Your Question it would be easier to analyze. Also, it'll make your issue clearer to others looking at the question. How did you check the entry? I understand you can't do it now, but when you get to the office run this:
cat /proc/cmdlinewithout manually adding it at boot. You can useCtrl+Alt+F2to get to a console, if the GUI doesn't work.– L. D. James
Apr 14 at 6:54
Yea sorry, updated accordingly.
– Adathor
Apr 14 at 6:57
Your response was quick. I had mistakenly pressed ENTER when I was still editing my comment. Can you elaborate on this: How did you check the entry? to verify the presence during boot? I understand you can't do it now, but when you get to the office run this: cat /proc/cmdline without manually adding it at boot. You can use Ctrl+Alt+F2 to get to a console, if the GUI doesn't work
– L. D. James
Apr 14 at 7:01