Ubuntu 18.04 boot stuck at message “Started NVIDIA Persistence Daemon” after installing nVidia...
Extracting Dirichlet series coefficients
Why didn't the Space Shuttle bounce back into space as many times as possible so as to lose a lot of kinetic energy up there?
How do I reattach a shelf to the wall when it ripped out of the wall?
Should the Product Owner dictate what info the UI needs to display?
How do I deal with a coworker that keeps asking to make small superficial changes to a report, and it is seriously triggering my anxiety?
What is purpose of DB Browser(dbbrowser.aspx) under admin tool?
Is there a word for the censored part of a video?
How much cash can I safely carry into the USA and avoid civil forfeiture?
A Paper Record is What I Hamper
Nails holding drywall
"Whatever a Russian does, they end up making the Kalashnikov gun"? Are there any similar proverbs in English?
Will I lose my paid in full property
What was Apollo 13's "Little Jolt" after MECO?
Injection into a proper class and choice without regularity
What is this word supposed to be?
Do I need to watch Ant-Man and the Wasp and Captain Marvel before watching Avengers: Endgame?
How exactly does Hawking radiation decrease the mass of black holes?
How to be good at coming up with counter example in Topology
Creating a chemical industry from a medieval tech level without petroleum
Is it acceptable to use working hours to read general interest books?
What is the most expensive material in the world that could be used to create Pun-Pun's lute?
Drawing a german abacus as in the books of Adam Ries
Multiple options vs single option UI
Negative Resistance
Ubuntu 18.04 boot stuck at message “Started NVIDIA Persistence Daemon” after installing nVidia 390.74
Ubuntu gets stuck in a login loopHow do I boot into a root shell?Ubuntu 17.10 boot stuck at message “Started NVIDIA Persistence Daemon” after installing nVidia 384.90NVIDIA persistence daemon continuously starting and stopping in syslogNVIDIA Persistence Daemon Fails, symlinks are deltedHow to remove faulty GPU driversUbuntu 16.04LTS doesn't boot or gets stuck in login loop after installNvidia Driver 375 Install Gets Stuck on Ubuntu 16.04.1Stuck in Login-loop after installing drivers for GTX 1060Ubuntu 16.04 Stuck in Login Loop After Installing Cuda or Nvidia DriverUbuntu 17.10 boot stuck at message “Started NVIDIA Persistence Daemon” after installing nVidia 384.90Ubuntu 17.10 stuck in login loop after installing CUDA-9 and nvidia driver 390Ubuntu Nvidia Drivers and Login LoopAtombios stuck in loop - after 18.04 upgradeBlack screen after installing proprietary Nvidia driver on Ubuntu 18.04Nvidia Persistence Daemon/Login Loop 18.04
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I seem to have a similar problem to this guy.
Ubuntu 17.10 boot stuck at message "Started NVIDIA Persistence Daemon" after installing nVidia 384.90
Is the only option to remove the nvidia drivers?
If so is the correct procedure to boot into recovery mode, select root and then delete the drivers in the terminal with the following commands?
sudo apt-get purge --auto-remove libcud*
sudo apt-get purge --auto-remove cuda*
sudo apt-get purge --auto-remove nvidia*
Update!
I can't even apply the above fix because I also have the problem in the link below where my Ubuntu is stuck in a login loop when trying to enter my desktop. When I login, the screen gets black and soon after that the login screen comes back.
Ubuntu gets stuck in a login loop
Unfortunately the solutions in the link rely on your knowing your login but I don't (only the password).
In theory it seems that you can recover your login by going into recovery mode, but my keyboard and mouse won't work with recovery GUI!
It does seem to be catch 22!
Am I right in thinking at this stage the only option is to delete and reinstall ubuntu?
Thanks
Update 2:
The keyboard and mouse are usb and they work in the regular linux login screen (it's just that that login process has the looping bug).
Not only is the recovery mode GUI completely unresponsive after a few minutes it start's displaying a bunch of random commands all over the screen see image below)!
drivers nvidia graphics 18.04
asked Jul 30 '18 at 19:49
BazmanBazman
2052714
add a comment |
I seem to have a similar problem to this guy.
Ubuntu 17.10 boot stuck at message "Started NVIDIA Persistence Daemon" after installing nVidia 384.90
Is the only option to remove the nvidia drivers?
If so is the correct procedure to boot into recovery mode, select root and then delete the drivers in the terminal with the following commands?
sudo apt-get purge --auto-remove libcud*
sudo apt-get purge --auto-remove cuda*
sudo apt-get purge --auto-remove nvidia*
Update!
I can't even apply the above fix because I also have the problem in the link below where my Ubuntu is stuck in a login loop when trying to enter my desktop. When I login, the screen gets black and soon after that the login screen comes back.
Ubuntu gets stuck in a login loop
Unfortunately the solutions in the link rely on your knowing your login but I don't (only the password).
In theory it seems that you can recover your login by going into recovery mode, but my keyboard and mouse won't work with recovery GUI!
It does seem to be catch 22!
Am I right in thinking at this stage the only option is to delete and reinstall ubuntu?
Thanks
Update 2:
The keyboard and mouse are usb and they work in the regular linux login screen (it's just that that login process has the looping bug).
Not only is the recovery mode GUI completely unresponsive after a few minutes it start's displaying a bunch of random commands all over the screen see image below)!
drivers nvidia graphics 18.04
asked Jul 30 '18 at 19:49
BazmanBazman
2052714
1
You should definitely be able to purge the drivers from the mode. What exactly is the problem with your keyboard and mouse - do they not respond at all? Are they ordinary usb keyboard and mouse? If possible try following this answer to enter the root shell and purge the drivers from there askubuntu.com/a/92558/783019
– adikus
Jul 31 '18 at 8:50
See edit to original question above the recovery mode GUI will not respond to keyboard/mouse commands and then after a few minutes I get the crazy output shown above.
– Bazman
Jul 31 '18 at 11:36
Alright, that seems very weird. Judging by the errors there might be something else wrong here as well (the errors mention filesystem and disk issues). Only other think I can think is you can try booting to the recovery shell from a Live USB (or live CD), assuming that's not what we're seeing here.
– adikus
Aug 1 '18 at 9:14
Did you recover? Looking for some way of disabling all the new drivers
– mathtick
Nov 24 '18 at 13:22
add a comment |
I seem to have a similar problem to this guy.
Ubuntu 17.10 boot stuck at message "Started NVIDIA Persistence Daemon" after installing nVidia 384.90
Is the only option to remove the nvidia drivers?
If so is the correct procedure to boot into recovery mode, select root and then delete the drivers in the terminal with the following commands?
sudo apt-get purge --auto-remove libcud*
sudo apt-get purge --auto-remove cuda*
sudo apt-get purge --auto-remove nvidia*
Update!
I can't even apply the above fix because I also have the problem in the link below where my Ubuntu is stuck in a login loop when trying to enter my desktop. When I login, the screen gets black and soon after that the login screen comes back.
Ubuntu gets stuck in a login loop
Unfortunately the solutions in the link rely on your knowing your login but I don't (only the password).
In theory it seems that you can recover your login by going into recovery mode, but my keyboard and mouse won't work with recovery GUI!
It does seem to be catch 22!
Am I right in thinking at this stage the only option is to delete and reinstall ubuntu?
Thanks
Update 2:
The keyboard and mouse are usb and they work in the regular linux login screen (it's just that that login process has the looping bug).
Not only is the recovery mode GUI completely unresponsive after a few minutes it start's displaying a bunch of random commands all over the screen see image below)!
drivers nvidia graphics 18.04
asked Jul 30 '18 at 19:49
BazmanBazman
2052714
I seem to have a similar problem to this guy.
Ubuntu 17.10 boot stuck at message "Started NVIDIA Persistence Daemon" after installing nVidia 384.90
Is the only option to remove the nvidia drivers?
If so is the correct procedure to boot into recovery mode, select root and then delete the drivers in the terminal with the following commands?
sudo apt-get purge --auto-remove libcud*
sudo apt-get purge --auto-remove cuda*
sudo apt-get purge --auto-remove nvidia*
Update!
I can't even apply the above fix because I also have the problem in the link below where my Ubuntu is stuck in a login loop when trying to enter my desktop. When I login, the screen gets black and soon after that the login screen comes back.
Ubuntu gets stuck in a login loop
Unfortunately the solutions in the link rely on your knowing your login but I don't (only the password).
In theory it seems that you can recover your login by going into recovery mode, but my keyboard and mouse won't work with recovery GUI!
It does seem to be catch 22!
Am I right in thinking at this stage the only option is to delete and reinstall ubuntu?
Thanks
Update 2:
The keyboard and mouse are usb and they work in the regular linux login screen (it's just that that login process has the looping bug).
Not only is the recovery mode GUI completely unresponsive after a few minutes it start's displaying a bunch of random commands all over the screen see image below)!
drivers nvidia graphics 18.04
drivers nvidia graphics 18.04
asked Jul 30 '18 at 19:49
BazmanBazman
2052714
asked Jul 30 '18 at 19:49
BazmanBazman
2052714
edited Jul 31 '18 at 11:35
Bazman
asked Jul 30 '18 at 19:49
BazmanBazman
2052714
asked Jul 30 '18 at 19:49
BazmanBazman
2052714
asked Jul 30 '18 at 19:49
BazmanBazman
2052714
2052714
1
You should definitely be able to purge the drivers from the mode. What exactly is the problem with your keyboard and mouse - do they not respond at all? Are they ordinary usb keyboard and mouse? If possible try following this answer to enter the root shell and purge the drivers from there askubuntu.com/a/92558/783019
– adikus
Jul 31 '18 at 8:50
See edit to original question above the recovery mode GUI will not respond to keyboard/mouse commands and then after a few minutes I get the crazy output shown above.
– Bazman
Jul 31 '18 at 11:36
Alright, that seems very weird. Judging by the errors there might be something else wrong here as well (the errors mention filesystem and disk issues). Only other think I can think is you can try booting to the recovery shell from a Live USB (or live CD), assuming that's not what we're seeing here.
– adikus
Aug 1 '18 at 9:14
Did you recover? Looking for some way of disabling all the new drivers
– mathtick
Nov 24 '18 at 13:22
add a comment |
1
You should definitely be able to purge the drivers from the mode. What exactly is the problem with your keyboard and mouse - do they not respond at all? Are they ordinary usb keyboard and mouse? If possible try following this answer to enter the root shell and purge the drivers from there askubuntu.com/a/92558/783019
– adikus
Jul 31 '18 at 8:50
See edit to original question above the recovery mode GUI will not respond to keyboard/mouse commands and then after a few minutes I get the crazy output shown above.
– Bazman
Jul 31 '18 at 11:36
Alright, that seems very weird. Judging by the errors there might be something else wrong here as well (the errors mention filesystem and disk issues). Only other think I can think is you can try booting to the recovery shell from a Live USB (or live CD), assuming that's not what we're seeing here.
– adikus
Aug 1 '18 at 9:14
Did you recover? Looking for some way of disabling all the new drivers
– mathtick
Nov 24 '18 at 13:22
1
1
You should definitely be able to purge the drivers from the mode. What exactly is the problem with your keyboard and mouse - do they not respond at all? Are they ordinary usb keyboard and mouse? If possible try following this answer to enter the root shell and purge the drivers from there askubuntu.com/a/92558/783019
– adikus
Jul 31 '18 at 8:50
You should definitely be able to purge the drivers from the mode. What exactly is the problem with your keyboard and mouse - do they not respond at all? Are they ordinary usb keyboard and mouse? If possible try following this answer to enter the root shell and purge the drivers from there askubuntu.com/a/92558/783019
– adikus
Jul 31 '18 at 8:50
See edit to original question above the recovery mode GUI will not respond to keyboard/mouse commands and then after a few minutes I get the crazy output shown above.
– Bazman
Jul 31 '18 at 11:36
See edit to original question above the recovery mode GUI will not respond to keyboard/mouse commands and then after a few minutes I get the crazy output shown above.
– Bazman
Jul 31 '18 at 11:36
Alright, that seems very weird. Judging by the errors there might be something else wrong here as well (the errors mention filesystem and disk issues). Only other think I can think is you can try booting to the recovery shell from a Live USB (or live CD), assuming that's not what we're seeing here.
– adikus
Aug 1 '18 at 9:14
Alright, that seems very weird. Judging by the errors there might be something else wrong here as well (the errors mention filesystem and disk issues). Only other think I can think is you can try booting to the recovery shell from a Live USB (or live CD), assuming that's not what we're seeing here.
– adikus
Aug 1 '18 at 9:14
Did you recover? Looking for some way of disabling all the new drivers
– mathtick
Nov 24 '18 at 13:22
Did you recover? Looking for some way of disabling all the new drivers
– mathtick
Nov 24 '18 at 13:22
add a comment |
1 Answer
1
active
oldest
votes
If the problem only occurs due to the persistence daemon, you can disable the startup by modifying /lib/udev/rules.d/71-nvidia.rules, similar to the first part of this answer.
If necessary, also execute
sudo systemctl disable nvidia-persistenced.service
If, in the end, you need the nvidia persistence daemon, you can try to apply the second part of the answer to see if it works for you.
answered 15 hours ago
AndréAndré
1011
New contributor
André 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 |
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
});
}
});
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%2f1060893%2fubuntu-18-04-boot-stuck-at-message-started-nvidia-persistence-daemon-after-ins%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
If the problem only occurs due to the persistence daemon, you can disable the startup by modifying /lib/udev/rules.d/71-nvidia.rules, similar to the first part of this answer.
If necessary, also execute
sudo systemctl disable nvidia-persistenced.service
If, in the end, you need the nvidia persistence daemon, you can try to apply the second part of the answer to see if it works for you.
answered 15 hours ago
AndréAndré
1011
New contributor
André 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 |
If the problem only occurs due to the persistence daemon, you can disable the startup by modifying /lib/udev/rules.d/71-nvidia.rules, similar to the first part of this answer.
If necessary, also execute
sudo systemctl disable nvidia-persistenced.service
If, in the end, you need the nvidia persistence daemon, you can try to apply the second part of the answer to see if it works for you.
answered 15 hours ago
AndréAndré
1011
New contributor
André 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 |
If the problem only occurs due to the persistence daemon, you can disable the startup by modifying /lib/udev/rules.d/71-nvidia.rules, similar to the first part of this answer.
If necessary, also execute
sudo systemctl disable nvidia-persistenced.service
If, in the end, you need the nvidia persistence daemon, you can try to apply the second part of the answer to see if it works for you.
answered 15 hours ago
AndréAndré
1011
New contributor
André is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
If the problem only occurs due to the persistence daemon, you can disable the startup by modifying /lib/udev/rules.d/71-nvidia.rules, similar to the first part of this answer.
If necessary, also execute
sudo systemctl disable nvidia-persistenced.service
If, in the end, you need the nvidia persistence daemon, you can try to apply the second part of the answer to see if it works for you.
answered 15 hours ago
AndréAndré
1011
New contributor
André is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 15 hours ago
AndréAndré
1011
New contributor
André is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 15 hours ago
AndréAndré
1011
answered 15 hours ago
AndréAndré
1011
1011
New contributor
André is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
André is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
André 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 |
add a comment |
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%2f1060893%2fubuntu-18-04-boot-stuck-at-message-started-nvidia-persistence-daemon-after-ins%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
You should definitely be able to purge the drivers from the mode. What exactly is the problem with your keyboard and mouse - do they not respond at all? Are they ordinary usb keyboard and mouse? If possible try following this answer to enter the root shell and purge the drivers from there askubuntu.com/a/92558/783019
– adikus
Jul 31 '18 at 8:50
See edit to original question above the recovery mode GUI will not respond to keyboard/mouse commands and then after a few minutes I get the crazy output shown above.
– Bazman
Jul 31 '18 at 11:36
Alright, that seems very weird. Judging by the errors there might be something else wrong here as well (the errors mention filesystem and disk issues). Only other think I can think is you can try booting to the recovery shell from a Live USB (or live CD), assuming that's not what we're seeing here.
– adikus
Aug 1 '18 at 9:14
Did you recover? Looking for some way of disabling all the new drivers
– mathtick
Nov 24 '18 at 13:22