Video output gets stuck on dev/sda1 clean The 2019 Stack Overflow Developer Survey Results Are InUbuntu 13.04 works fine from live USB but can't boot after install14.04 LTS only boots through recoveryStuck at fsck “/dev/sda1: clean xxx/xxx files […] ” after upgrade to Ubuntu 16 from 14After 16.04 installation: hang at blank purple screenUbuntu Gnome 16.04.3 gets stuck at boot on Dell XPS 15 (9560)Getting dev/sda1: clean … after update-rc.dBlack screen / LightDM not starting after nvidia driver updateUbuntu 17.10, regular boot stuckUbuntu 18.04 will only boot in recovery mode on HP Proliant dl380 G5Boot hangs after upgrade from 16.04 to 18.04.1
Origin of "cooter" meaning "vagina"
Can someone be penalized for an "unlawful" act if no penalty is specified?
What do hard-Brexiteers want with respect to the Irish border?
Can you compress metal and what would be the consequences?
Building a conditional check constraint
Is there any way to tell whether the shot is going to hit you or not?
What are the motivations for publishing new editions of an existing textbook, beyond new discoveries in a field?
I see my dog run
What do the Banks children have against barley water?
Apparent duplicates between Haynes service instructions and MOT
What did it mean to "align" a radio?
How to type this arrow in math mode?
How technical should a Scrum Master be to effectively remove impediments?
Deal with toxic manager when you can't quit
Is three citations per paragraph excessive for undergraduate research paper?
How to deal with fear of taking dependencies
What is the most effective way of iterating a std::vector and why?
Is this app Icon Browser Safe/Legit?
Is a "Democratic" Oligarchy-Style System Possible?
Time travel alters history but people keep saying nothing's changed
Did 3000BC Egyptians use meteoric iron weapons?
What tool would a Roman-age civilization have for the breaking of silver and other metals into dust?
Which Sci-Fi work first showed weapon of galactic-scale mass destruction?
How to obtain Confidence Intervals for a LASSO regression?
Video output gets stuck on dev/sda1 clean
The 2019 Stack Overflow Developer Survey Results Are InUbuntu 13.04 works fine from live USB but can't boot after install14.04 LTS only boots through recoveryStuck at fsck “/dev/sda1: clean xxx/xxx files […] ” after upgrade to Ubuntu 16 from 14After 16.04 installation: hang at blank purple screenUbuntu Gnome 16.04.3 gets stuck at boot on Dell XPS 15 (9560)Getting dev/sda1: clean … after update-rc.dBlack screen / LightDM not starting after nvidia driver updateUbuntu 17.10, regular boot stuckUbuntu 18.04 will only boot in recovery mode on HP Proliant dl380 G5Boot hangs after upgrade from 16.04 to 18.04.1
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
Running Ubuntu 18.04
The system seems to stuck at dev/sda1.
I can still SSH into the the system.
I can also go into the advanced menu select recovery, and without changing anything going with resume allows the system to start normally.
I have read posts about Nvidea drivers, but I don't have a Nvidea card.
I assume the recovery boot uses some sort of default drivers is there a way to force the use of those drivers always?
Place I get stuck at
boot drivers
edited yesterday
Jeff
840719
asked 2 days ago
VentingWhileorangeVentingWhileorange
61
New contributor
VentingWhileorange is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Running Ubuntu 18.04
The system seems to stuck at dev/sda1.
I can still SSH into the the system.
I can also go into the advanced menu select recovery, and without changing anything going with resume allows the system to start normally.
I have read posts about Nvidea drivers, but I don't have a Nvidea card.
I assume the recovery boot uses some sort of default drivers is there a way to force the use of those drivers always?
Place I get stuck at
boot drivers
edited yesterday
Jeff
840719
asked 2 days ago
VentingWhileorangeVentingWhileorange
61
New contributor
VentingWhileorange is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
Yes, the recovery mode uses the boot optionnomodeset. You can add that boot option manually also for the 'normal' menu entry (in the grub menu) according to this link and links from it. - But there is a problem behind, typical for nvidia chips/cards. Even if you have not got an nvidia card, maybe there is an nvidia chip on the motherboard or on a card with another name. Or maybe there is another graphics chip/card, that needsnomodeset.
– sudodus
2 days ago
add a comment |
Running Ubuntu 18.04
The system seems to stuck at dev/sda1.
I can still SSH into the the system.
I can also go into the advanced menu select recovery, and without changing anything going with resume allows the system to start normally.
I have read posts about Nvidea drivers, but I don't have a Nvidea card.
I assume the recovery boot uses some sort of default drivers is there a way to force the use of those drivers always?
Place I get stuck at
boot drivers
edited yesterday
Jeff
840719
asked 2 days ago
VentingWhileorangeVentingWhileorange
61
New contributor
VentingWhileorange is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Running Ubuntu 18.04
The system seems to stuck at dev/sda1.
I can still SSH into the the system.
I can also go into the advanced menu select recovery, and without changing anything going with resume allows the system to start normally.
I have read posts about Nvidea drivers, but I don't have a Nvidea card.
I assume the recovery boot uses some sort of default drivers is there a way to force the use of those drivers always?
Place I get stuck at
boot drivers
boot drivers
edited yesterday
Jeff
840719
asked 2 days ago
VentingWhileorangeVentingWhileorange
61
New contributor
VentingWhileorange is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited yesterday
Jeff
840719
asked 2 days ago
VentingWhileorangeVentingWhileorange
61
New contributor
VentingWhileorange is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited yesterday
Jeff
840719
edited yesterday
Jeff
840719
edited yesterday
Jeff
840719
840719
asked 2 days ago
VentingWhileorangeVentingWhileorange
61
New contributor
VentingWhileorange 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
VentingWhileorangeVentingWhileorange
61
asked 2 days ago
VentingWhileorangeVentingWhileorange
61
61
New contributor
VentingWhileorange is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
VentingWhileorange is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
VentingWhileorange is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
Yes, the recovery mode uses the boot optionnomodeset. You can add that boot option manually also for the 'normal' menu entry (in the grub menu) according to this link and links from it. - But there is a problem behind, typical for nvidia chips/cards. Even if you have not got an nvidia card, maybe there is an nvidia chip on the motherboard or on a card with another name. Or maybe there is another graphics chip/card, that needsnomodeset.
– sudodus
2 days ago
add a comment |
1
Yes, the recovery mode uses the boot optionnomodeset. You can add that boot option manually also for the 'normal' menu entry (in the grub menu) according to this link and links from it. - But there is a problem behind, typical for nvidia chips/cards. Even if you have not got an nvidia card, maybe there is an nvidia chip on the motherboard or on a card with another name. Or maybe there is another graphics chip/card, that needsnomodeset.
– sudodus
2 days ago
1
1
Yes, the recovery mode uses the boot option
nomodeset. You can add that boot option manually also for the 'normal' menu entry (in the grub menu) according to this link and links from it. - But there is a problem behind, typical for nvidia chips/cards. Even if you have not got an nvidia card, maybe there is an nvidia chip on the motherboard or on a card with another name. Or maybe there is another graphics chip/card, that needs nomodeset.– sudodus
2 days ago
Yes, the recovery mode uses the boot option
nomodeset. You can add that boot option manually also for the 'normal' menu entry (in the grub menu) according to this link and links from it. - But there is a problem behind, typical for nvidia chips/cards. Even if you have not got an nvidia card, maybe there is an nvidia chip on the motherboard or on a card with another name. Or maybe there is another graphics chip/card, that needs nomodeset.– sudodus
2 days ago
add a comment |
1 Answer
1
active
oldest
votes
Run on terminal. In SSH edit the file "/etc/default/grub". Example:
sudo vi /etc/default/grub
Change the line
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
to
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset"
sudo update-grub2
Reboot
You can do the same from recovery mode > root shell
answered 2 days ago
VijayVijay
2,1041822
add a comment |
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',
autoActivateHeartbeat: false,
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
);
);
VentingWhileorange is a new contributor. Be nice, and check out our Code of Conduct.
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%2faskubuntu.com%2fquestions%2f1132140%2fvideo-output-gets-stuck-on-dev-sda1-clean%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
Run on terminal. In SSH edit the file "/etc/default/grub". Example:
sudo vi /etc/default/grub
Change the line
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
to
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset"
sudo update-grub2
Reboot
You can do the same from recovery mode > root shell
answered 2 days ago
VijayVijay
2,1041822
add a comment |
Run on terminal. In SSH edit the file "/etc/default/grub". Example:
sudo vi /etc/default/grub
Change the line
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
to
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset"
sudo update-grub2
Reboot
You can do the same from recovery mode > root shell
answered 2 days ago
VijayVijay
2,1041822
add a comment |
Run on terminal. In SSH edit the file "/etc/default/grub". Example:
sudo vi /etc/default/grub
Change the line
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
to
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset"
sudo update-grub2
Reboot
You can do the same from recovery mode > root shell
answered 2 days ago
VijayVijay
2,1041822
Run on terminal. In SSH edit the file "/etc/default/grub". Example:
sudo vi /etc/default/grub
Change the line
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
to
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset"
sudo update-grub2
Reboot
You can do the same from recovery mode > root shell
answered 2 days ago
VijayVijay
2,1041822
edited 2 days ago
answered 2 days ago
VijayVijay
2,1041822
answered 2 days ago
VijayVijay
2,1041822
answered 2 days ago
VijayVijay
2,1041822
2,1041822
add a comment |
add a comment |
VentingWhileorange is a new contributor. Be nice, and check out our Code of Conduct.
VentingWhileorange is a new contributor. Be nice, and check out our Code of Conduct.
VentingWhileorange is a new contributor. Be nice, and check out our Code of Conduct.
VentingWhileorange is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f1132140%2fvideo-output-gets-stuck-on-dev-sda1-clean%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
Yes, the recovery mode uses the boot option
nomodeset. You can add that boot option manually also for the 'normal' menu entry (in the grub menu) according to this link and links from it. - But there is a problem behind, typical for nvidia chips/cards. Even if you have not got an nvidia card, maybe there is an nvidia chip on the motherboard or on a card with another name. Or maybe there is another graphics chip/card, that needsnomodeset.– sudodus
2 days ago