Ubuntu's main bootup only returns blank screen, systemd bootup works fine
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I use Grub to boot between Ubuntu and Windows. The options are somewhat like
Ubuntu
Ubuntu (Recovery Mode)
Windows
If I choose 1, it shows the Ubuntu logo, the little balls under it flowing. Then just a blank screen. I can't even get into a text terminal by pressing Ctrl-Alt-F1.
But if I choose 2, and then choose Ubuntu (systemd), everything works just fine. I log in, everything runs. I'm no Linux expert but I believe the only two differences is that Option 1 uses Upstart instead of Systemd and vice versa.
Personally, I don't care which my system uses. I'm just trying to get my default choice to work again. Any thoughts?
ubuntu boot systemd upstart
edited Sep 6 '16 at 23:05
GnP
1,5611011
asked Sep 6 '16 at 19:49
JoshEmoryJoshEmory
1063
add a comment |
I use Grub to boot between Ubuntu and Windows. The options are somewhat like
Ubuntu
Ubuntu (Recovery Mode)
Windows
If I choose 1, it shows the Ubuntu logo, the little balls under it flowing. Then just a blank screen. I can't even get into a text terminal by pressing Ctrl-Alt-F1.
But if I choose 2, and then choose Ubuntu (systemd), everything works just fine. I log in, everything runs. I'm no Linux expert but I believe the only two differences is that Option 1 uses Upstart instead of Systemd and vice versa.
Personally, I don't care which my system uses. I'm just trying to get my default choice to work again. Any thoughts?
ubuntu boot systemd upstart
edited Sep 6 '16 at 23:05
GnP
1,5611011
asked Sep 6 '16 at 19:49
JoshEmoryJoshEmory
1063
1
I don't use Ubuntu so I won't post this as an answer but it might help you until someone more knowledgeable comes along. If you can boot up Ubuntu in recovery mode, you should be able to access your files in one way or the other. Specifically, you should be able to access your log files (look in /var/log on your rootfs). While you might not be able to solve the issue with the information you find there, you are likely to get better replies here if you provide a copy of the error log.
– vic
Sep 6 '16 at 20:06
@vic I'm not sure which log file in particular I should be looking at.
– JoshEmory
Sep 6 '16 at 21:39
add a comment |
I use Grub to boot between Ubuntu and Windows. The options are somewhat like
Ubuntu
Ubuntu (Recovery Mode)
Windows
If I choose 1, it shows the Ubuntu logo, the little balls under it flowing. Then just a blank screen. I can't even get into a text terminal by pressing Ctrl-Alt-F1.
But if I choose 2, and then choose Ubuntu (systemd), everything works just fine. I log in, everything runs. I'm no Linux expert but I believe the only two differences is that Option 1 uses Upstart instead of Systemd and vice versa.
Personally, I don't care which my system uses. I'm just trying to get my default choice to work again. Any thoughts?
ubuntu boot systemd upstart
edited Sep 6 '16 at 23:05
GnP
1,5611011
asked Sep 6 '16 at 19:49
JoshEmoryJoshEmory
1063
I use Grub to boot between Ubuntu and Windows. The options are somewhat like
Ubuntu
Ubuntu (Recovery Mode)
Windows
If I choose 1, it shows the Ubuntu logo, the little balls under it flowing. Then just a blank screen. I can't even get into a text terminal by pressing Ctrl-Alt-F1.
But if I choose 2, and then choose Ubuntu (systemd), everything works just fine. I log in, everything runs. I'm no Linux expert but I believe the only two differences is that Option 1 uses Upstart instead of Systemd and vice versa.
Personally, I don't care which my system uses. I'm just trying to get my default choice to work again. Any thoughts?
ubuntu boot systemd upstart
ubuntu boot systemd upstart
edited Sep 6 '16 at 23:05
GnP
1,5611011
asked Sep 6 '16 at 19:49
JoshEmoryJoshEmory
1063
edited Sep 6 '16 at 23:05
GnP
1,5611011
asked Sep 6 '16 at 19:49
JoshEmoryJoshEmory
1063
edited Sep 6 '16 at 23:05
GnP
1,5611011
edited Sep 6 '16 at 23:05
GnP
1,5611011
edited Sep 6 '16 at 23:05
GnP
1,5611011
1,5611011
asked Sep 6 '16 at 19:49
JoshEmoryJoshEmory
1063
asked Sep 6 '16 at 19:49
JoshEmoryJoshEmory
1063
asked Sep 6 '16 at 19:49
JoshEmoryJoshEmory
1063
1063
1
I don't use Ubuntu so I won't post this as an answer but it might help you until someone more knowledgeable comes along. If you can boot up Ubuntu in recovery mode, you should be able to access your files in one way or the other. Specifically, you should be able to access your log files (look in /var/log on your rootfs). While you might not be able to solve the issue with the information you find there, you are likely to get better replies here if you provide a copy of the error log.
– vic
Sep 6 '16 at 20:06
@vic I'm not sure which log file in particular I should be looking at.
– JoshEmory
Sep 6 '16 at 21:39
add a comment |
1
I don't use Ubuntu so I won't post this as an answer but it might help you until someone more knowledgeable comes along. If you can boot up Ubuntu in recovery mode, you should be able to access your files in one way or the other. Specifically, you should be able to access your log files (look in /var/log on your rootfs). While you might not be able to solve the issue with the information you find there, you are likely to get better replies here if you provide a copy of the error log.
– vic
Sep 6 '16 at 20:06
@vic I'm not sure which log file in particular I should be looking at.
– JoshEmory
Sep 6 '16 at 21:39
1
1
I don't use Ubuntu so I won't post this as an answer but it might help you until someone more knowledgeable comes along. If you can boot up Ubuntu in recovery mode, you should be able to access your files in one way or the other. Specifically, you should be able to access your log files (look in /var/log on your rootfs). While you might not be able to solve the issue with the information you find there, you are likely to get better replies here if you provide a copy of the error log.
– vic
Sep 6 '16 at 20:06
I don't use Ubuntu so I won't post this as an answer but it might help you until someone more knowledgeable comes along. If you can boot up Ubuntu in recovery mode, you should be able to access your files in one way or the other. Specifically, you should be able to access your log files (look in /var/log on your rootfs). While you might not be able to solve the issue with the information you find there, you are likely to get better replies here if you provide a copy of the error log.
– vic
Sep 6 '16 at 20:06
@vic I'm not sure which log file in particular I should be looking at.
– JoshEmory
Sep 6 '16 at 21:39
@vic I'm not sure which log file in particular I should be looking at.
– JoshEmory
Sep 6 '16 at 21:39
add a comment |
1 Answer
1
active
oldest
votes
The logs vic is referring to are probably /var/log/boot.log and /var/log/dmesg.
If you don't see something in them that jumps out at you, then have you tried disabling the splash screen? In the past I've had trouble with the splash screen on some computers.
sudo nano /etc/default/grub
Remove quiet splash and leave the quotes there so that it looks something like
GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=false
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT=""
GRUB_CMDLINE_LINUX=""
Then issue the command to reconstruct the boot configuration (sudo update-grub) and reboot (reboot).
If that does not solve the problem, we're going to need way more information to help, so edit the configuration again so that you can boot into text mode:
GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=false
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="text"
GRUB_CMDLINE_LINUX=""
Then issue the command to reconstruct the boot configuration (sudo update-grub) and reboot (reboot).
This should get you to a text login (if it doesn't, you're going to have to use the recovery to extract the info we need to debug).
sudo bash
lshw > /var/log/usermade_hardware.log
exit
To help further, I would need that log (display/video card or another integral part to the standard boot might be UNCLAIMED) as well as the logs located at /var/log/boot.log and /var/log/dmesg.
If there's nothing in those logs, there might be a problem with upstart (have you updated it?).
PS. In the future, the best place for OS-specific help on ubuntu is probably ubuntuforums or askubuntu.
PPS. I don't have enough reputation to comment, so it's in an answer.
answered Sep 6 '16 at 22:09
SchivesSchives
569311
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
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',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f308268%2fubuntus-main-bootup-only-returns-blank-screen-systemd-bootup-works-fine%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The logs vic is referring to are probably /var/log/boot.log and /var/log/dmesg.
If you don't see something in them that jumps out at you, then have you tried disabling the splash screen? In the past I've had trouble with the splash screen on some computers.
sudo nano /etc/default/grub
Remove quiet splash and leave the quotes there so that it looks something like
GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=false
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT=""
GRUB_CMDLINE_LINUX=""
Then issue the command to reconstruct the boot configuration (sudo update-grub) and reboot (reboot).
If that does not solve the problem, we're going to need way more information to help, so edit the configuration again so that you can boot into text mode:
GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=false
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="text"
GRUB_CMDLINE_LINUX=""
Then issue the command to reconstruct the boot configuration (sudo update-grub) and reboot (reboot).
This should get you to a text login (if it doesn't, you're going to have to use the recovery to extract the info we need to debug).
sudo bash
lshw > /var/log/usermade_hardware.log
exit
To help further, I would need that log (display/video card or another integral part to the standard boot might be UNCLAIMED) as well as the logs located at /var/log/boot.log and /var/log/dmesg.
If there's nothing in those logs, there might be a problem with upstart (have you updated it?).
PS. In the future, the best place for OS-specific help on ubuntu is probably ubuntuforums or askubuntu.
PPS. I don't have enough reputation to comment, so it's in an answer.
answered Sep 6 '16 at 22:09
SchivesSchives
569311
add a comment |
The logs vic is referring to are probably /var/log/boot.log and /var/log/dmesg.
If you don't see something in them that jumps out at you, then have you tried disabling the splash screen? In the past I've had trouble with the splash screen on some computers.
sudo nano /etc/default/grub
Remove quiet splash and leave the quotes there so that it looks something like
GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=false
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT=""
GRUB_CMDLINE_LINUX=""
Then issue the command to reconstruct the boot configuration (sudo update-grub) and reboot (reboot).
If that does not solve the problem, we're going to need way more information to help, so edit the configuration again so that you can boot into text mode:
GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=false
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="text"
GRUB_CMDLINE_LINUX=""
Then issue the command to reconstruct the boot configuration (sudo update-grub) and reboot (reboot).
This should get you to a text login (if it doesn't, you're going to have to use the recovery to extract the info we need to debug).
sudo bash
lshw > /var/log/usermade_hardware.log
exit
To help further, I would need that log (display/video card or another integral part to the standard boot might be UNCLAIMED) as well as the logs located at /var/log/boot.log and /var/log/dmesg.
If there's nothing in those logs, there might be a problem with upstart (have you updated it?).
PS. In the future, the best place for OS-specific help on ubuntu is probably ubuntuforums or askubuntu.
PPS. I don't have enough reputation to comment, so it's in an answer.
answered Sep 6 '16 at 22:09
SchivesSchives
569311
add a comment |
The logs vic is referring to are probably /var/log/boot.log and /var/log/dmesg.
If you don't see something in them that jumps out at you, then have you tried disabling the splash screen? In the past I've had trouble with the splash screen on some computers.
sudo nano /etc/default/grub
Remove quiet splash and leave the quotes there so that it looks something like
GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=false
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT=""
GRUB_CMDLINE_LINUX=""
Then issue the command to reconstruct the boot configuration (sudo update-grub) and reboot (reboot).
If that does not solve the problem, we're going to need way more information to help, so edit the configuration again so that you can boot into text mode:
GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=false
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="text"
GRUB_CMDLINE_LINUX=""
Then issue the command to reconstruct the boot configuration (sudo update-grub) and reboot (reboot).
This should get you to a text login (if it doesn't, you're going to have to use the recovery to extract the info we need to debug).
sudo bash
lshw > /var/log/usermade_hardware.log
exit
To help further, I would need that log (display/video card or another integral part to the standard boot might be UNCLAIMED) as well as the logs located at /var/log/boot.log and /var/log/dmesg.
If there's nothing in those logs, there might be a problem with upstart (have you updated it?).
PS. In the future, the best place for OS-specific help on ubuntu is probably ubuntuforums or askubuntu.
PPS. I don't have enough reputation to comment, so it's in an answer.
answered Sep 6 '16 at 22:09
SchivesSchives
569311
The logs vic is referring to are probably /var/log/boot.log and /var/log/dmesg.
If you don't see something in them that jumps out at you, then have you tried disabling the splash screen? In the past I've had trouble with the splash screen on some computers.
sudo nano /etc/default/grub
Remove quiet splash and leave the quotes there so that it looks something like
GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=false
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT=""
GRUB_CMDLINE_LINUX=""
Then issue the command to reconstruct the boot configuration (sudo update-grub) and reboot (reboot).
If that does not solve the problem, we're going to need way more information to help, so edit the configuration again so that you can boot into text mode:
GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=false
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="text"
GRUB_CMDLINE_LINUX=""
Then issue the command to reconstruct the boot configuration (sudo update-grub) and reboot (reboot).
This should get you to a text login (if it doesn't, you're going to have to use the recovery to extract the info we need to debug).
sudo bash
lshw > /var/log/usermade_hardware.log
exit
To help further, I would need that log (display/video card or another integral part to the standard boot might be UNCLAIMED) as well as the logs located at /var/log/boot.log and /var/log/dmesg.
If there's nothing in those logs, there might be a problem with upstart (have you updated it?).
PS. In the future, the best place for OS-specific help on ubuntu is probably ubuntuforums or askubuntu.
PPS. I don't have enough reputation to comment, so it's in an answer.
answered Sep 6 '16 at 22:09
SchivesSchives
569311
edited Sep 6 '16 at 22:16
answered Sep 6 '16 at 22:09
SchivesSchives
569311
answered Sep 6 '16 at 22:09
SchivesSchives
569311
answered Sep 6 '16 at 22:09
SchivesSchives
569311
569311
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f308268%2fubuntus-main-bootup-only-returns-blank-screen-systemd-bootup-works-fine%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
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
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
1
I don't use Ubuntu so I won't post this as an answer but it might help you until someone more knowledgeable comes along. If you can boot up Ubuntu in recovery mode, you should be able to access your files in one way or the other. Specifically, you should be able to access your log files (look in /var/log on your rootfs). While you might not be able to solve the issue with the information you find there, you are likely to get better replies here if you provide a copy of the error log.
– vic
Sep 6 '16 at 20:06
@vic I'm not sure which log file in particular I should be looking at.
– JoshEmory
Sep 6 '16 at 21:39