Ubuntu 17.10 boot stuck at message “Started NVIDIA Persistence Daemon” after installing nVidia 384.90How...
Do I need to watch Ant-Man and the Wasp and Captain Marvel before watching Avengers: Endgame?
Is there a better way to say "see someone's dreams"?
Why did C use the -> operator instead of reusing the . operator?
Extracting Dirichlet series coefficients
How to pronounce 'c++' in Spanish
Work requires me to come in early to start computer but wont let me clock in to get paid for it
Was Dennis Ritchie being too modest in this quote about C and Pascal?
Why do distances seem to matter in the Foundation world?
Co-worker works way more than he should
Why do real positive eigenvalues result in an unstable system? What about eigenvalues between 0 and 1? or 1?
Multiple options vs single option UI
What is the unit of time_lock_delta in LND?
How to not starve gigantic beasts
Multiple fireplaces in an apartment building?
What is this word supposed to be?
"My boss was furious with me and I have been fired" vs. "My boss was furious with me and I was fired"
Retract an already submitted recommendation letter (written for an undergrad student)
Contradiction proof for inequality of P and NP?
Is Diceware more secure than a long passphrase?
How important is it that $TERM is correct?
How can I wire a 9-position switch so that each position turns on one more LED than the one before?
As an international instructor, should I openly talk about my accent?
How long after the last departure shall the airport stay open for an emergency return?
How do I reattach a shelf to the wall when it ripped out of the wall?
Ubuntu 17.10 boot stuck at message “Started NVIDIA Persistence Daemon” after installing nVidia 384.90
How do I check if Ubuntu is using my NVIDIA graphics card?NVIDIA persistence daemon continuously starting and stopping in syslogUbuntu 18.04 boot stuck at message “Started NVIDIA Persistence Daemon” after installing nVidia 390.74NVIDIA Persistence Daemon Fails, symlinks are deltedUbuntu 16.04 Nvidia geforce gt 610 display and sound by hdmiNVIDIA drivers not working (no PRIME either)Use proprietary graphic drivers in Ubuntu 17.10Unable to log in into Ubuntu 17.10 after Nvidia driver rollbackInstalling latest nVidia Driver on Ubuntu 17.10Ubuntu 17.10 boot issues on Dell XPS 15 9560, dual monitor, suspend/resumeUbuntu 17.10 and 18.04 Beta 2 display driver issues (freezing/black screen after login)Nvidia driver installs but does not load on ubuntu 18.04Ubuntu 18.04 boot stuck at message “Started NVIDIA Persistence Daemon” after installing nVidia 390.74NVIDIA Persistence Daemon Fails, symlinks are delted
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I have made fresh install of Ubuntu 17.10 (fresh, except keeping my old /home
partition). Everything seams to work out of the box except after I installed (or actually enable in Additional drivers
) the nVidia 384.90 driver system failed to start. I was just getting following error
[ OK ] Started NVIDIA Persistence Daemon.
Stopping NVIDIA Persistence Daemon...
[ OK ] Stopped NVIDIA Persistence Daemon.
Starting NVIDIA Persistence Daemon...
And this goes all over again and again like hundred times and the just stops. The only way out is uninstalling nvidia-384 using recovery mode.
I have tried other versions of the driver as well but with very same result. On shared Intel graphics (Intel® Haswell Mobile) everything works fine.
My config:
Intel i7-4710MQ
nVidia GT 940M
drivers nvidia graphics 17.10
add a comment |
I have made fresh install of Ubuntu 17.10 (fresh, except keeping my old /home
partition). Everything seams to work out of the box except after I installed (or actually enable in Additional drivers
) the nVidia 384.90 driver system failed to start. I was just getting following error
[ OK ] Started NVIDIA Persistence Daemon.
Stopping NVIDIA Persistence Daemon...
[ OK ] Stopped NVIDIA Persistence Daemon.
Starting NVIDIA Persistence Daemon...
And this goes all over again and again like hundred times and the just stops. The only way out is uninstalling nvidia-384 using recovery mode.
I have tried other versions of the driver as well but with very same result. On shared Intel graphics (Intel® Haswell Mobile) everything works fine.
My config:
Intel i7-4710MQ
nVidia GT 940M
drivers nvidia graphics 17.10
add a comment |
I have made fresh install of Ubuntu 17.10 (fresh, except keeping my old /home
partition). Everything seams to work out of the box except after I installed (or actually enable in Additional drivers
) the nVidia 384.90 driver system failed to start. I was just getting following error
[ OK ] Started NVIDIA Persistence Daemon.
Stopping NVIDIA Persistence Daemon...
[ OK ] Stopped NVIDIA Persistence Daemon.
Starting NVIDIA Persistence Daemon...
And this goes all over again and again like hundred times and the just stops. The only way out is uninstalling nvidia-384 using recovery mode.
I have tried other versions of the driver as well but with very same result. On shared Intel graphics (Intel® Haswell Mobile) everything works fine.
My config:
Intel i7-4710MQ
nVidia GT 940M
drivers nvidia graphics 17.10
I have made fresh install of Ubuntu 17.10 (fresh, except keeping my old /home
partition). Everything seams to work out of the box except after I installed (or actually enable in Additional drivers
) the nVidia 384.90 driver system failed to start. I was just getting following error
[ OK ] Started NVIDIA Persistence Daemon.
Stopping NVIDIA Persistence Daemon...
[ OK ] Stopped NVIDIA Persistence Daemon.
Starting NVIDIA Persistence Daemon...
And this goes all over again and again like hundred times and the just stops. The only way out is uninstalling nvidia-384 using recovery mode.
I have tried other versions of the driver as well but with very same result. On shared Intel graphics (Intel® Haswell Mobile) everything works fine.
My config:
Intel i7-4710MQ
nVidia GT 940M
drivers nvidia graphics 17.10
drivers nvidia graphics 17.10
edited Nov 15 '17 at 6:55
Ciro Santilli 新疆改造中心996ICU六四事件
10.7k55054
10.7k55054
asked Nov 6 '17 at 18:03
Juraj.LorincJuraj.Lorinc
4683717
4683717
add a comment |
add a comment |
5 Answers
5
active
oldest
votes
Switch to Discrete Graphics on BIOS
Lenovo P51, UEFI BIOS Version N1UE40W, NVIDIA Quadro M1200 Mobile, Ubuntu 17.10, nvidia-384 installed from software-properties-gtk
:
- Hit Enter at boot time
- Press F1 for BIOS setup
- Config
- Graphics Device
- Select Discrete Graphics (Default was hybrid graphics)
- Security
- Secure Boot
- Secure Boot
- Select Disabled (Default enabled). If I don't do this, the NVIDIA driver simply gets ignored (and the boot problem does not happen either)
- Press F10 to save settings and exit boot menu
I think this makes the battery last less, but I'd rather have a desktop :-)
I also noticed that the problem is not reproducible every time. If I power cycle a few times, I also see the following behaviours:
- immediate computer restart during boot
- once everything actually worked
Then check that the GPU is actually being used: How do I check if Ubuntu is using my NVIDIA graphics card?
Possible launchpad bug for this: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1714881
1
For me on a Dell latitude this was in the graphics menu in BIOS and something to do with enabling Optimus, it says only supports windows but solved the problem in ubuntu 18.04 thanks for the point in the right direction
– shaunhusain
Jan 2 at 7:05
add a comment |
I do not know the cause for this behaviour but I have the same problem on my ASUS laptop with GM108M [GeForce 840M]. My improvised solution is to disable automatic login. If I do login manually I have the normal startup. I use the proprietary driver.
I had automatic login disabled and it didn't work. Did you have the very same problem as me with the Persistence Daemon?
– Juraj.Lorinc
Nov 13 '17 at 15:07
Yes, I did and still do. Each time I start with the automatic login enabled I get the message you posted and after a couple of seconds my computer stops. So I restart with an older kernel, the automatic login goes normally, then I change to manual login, restart again by default and the laptop boot without any problem. It seems it has to do with the new kernel.
– MartinH
Nov 14 '17 at 22:10
add a comment |
Consider changing your display manager to lightdm. gdm3 doesn't work very well with nvidia drivers in my experience. I can not get it work at all if I'm using the modeset driver (and I've been trying for months). There are no workarounds that I have found. Nvidia, gdm3 and modern gnome are broken on both of my Optimus Thinkpads, you have to change one of those three, and the easiest is to replace gdm3 (if you change from gnome to another desktop environment, you will probably end up with lightdm anyway).
You are not trying to use modeset so you don't experience the same problem, but I have become biased against the unholy trinity of nvidia graphics, gnome and gdm3.
I have no problems with lightdm
sudo apt install lightdm
if necessary
sudo dpkg-reconfigure lightdm
and set it to the default (the installation of lightdm will ask you, but not if you already had it installed).
If you can't log in, you may feel a bit stuck. Hopefully you still have that old kernel. Otherwise you will have to try the advanced option and boot into recovery mode. I find that I choose 'enable networking' I usually get to a root shell in read/write which lets me do apt get stuff. If that doesn't work, it gets a bit harder; you can either reinstall or boot from a livecd and learn how to use chroot to do a pretend-login to your main installation. (something very useful to know).
add a comment |
$sudo apt-get purge nvidia*
will work fine.
Once the system gets started install the compatible driver.
add a comment |
This answer actually did the job for me. None of the above solutions were applicable for me.
It all comes down to disabling the default startup of the nvidia persistence daemon and writing an own systemd service which starts on boot.
New contributor
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%2f973605%2fubuntu-17-10-boot-stuck-at-message-started-nvidia-persistence-daemon-after-ins%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
Switch to Discrete Graphics on BIOS
Lenovo P51, UEFI BIOS Version N1UE40W, NVIDIA Quadro M1200 Mobile, Ubuntu 17.10, nvidia-384 installed from software-properties-gtk
:
- Hit Enter at boot time
- Press F1 for BIOS setup
- Config
- Graphics Device
- Select Discrete Graphics (Default was hybrid graphics)
- Security
- Secure Boot
- Secure Boot
- Select Disabled (Default enabled). If I don't do this, the NVIDIA driver simply gets ignored (and the boot problem does not happen either)
- Press F10 to save settings and exit boot menu
I think this makes the battery last less, but I'd rather have a desktop :-)
I also noticed that the problem is not reproducible every time. If I power cycle a few times, I also see the following behaviours:
- immediate computer restart during boot
- once everything actually worked
Then check that the GPU is actually being used: How do I check if Ubuntu is using my NVIDIA graphics card?
Possible launchpad bug for this: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1714881
1
For me on a Dell latitude this was in the graphics menu in BIOS and something to do with enabling Optimus, it says only supports windows but solved the problem in ubuntu 18.04 thanks for the point in the right direction
– shaunhusain
Jan 2 at 7:05
add a comment |
Switch to Discrete Graphics on BIOS
Lenovo P51, UEFI BIOS Version N1UE40W, NVIDIA Quadro M1200 Mobile, Ubuntu 17.10, nvidia-384 installed from software-properties-gtk
:
- Hit Enter at boot time
- Press F1 for BIOS setup
- Config
- Graphics Device
- Select Discrete Graphics (Default was hybrid graphics)
- Security
- Secure Boot
- Secure Boot
- Select Disabled (Default enabled). If I don't do this, the NVIDIA driver simply gets ignored (and the boot problem does not happen either)
- Press F10 to save settings and exit boot menu
I think this makes the battery last less, but I'd rather have a desktop :-)
I also noticed that the problem is not reproducible every time. If I power cycle a few times, I also see the following behaviours:
- immediate computer restart during boot
- once everything actually worked
Then check that the GPU is actually being used: How do I check if Ubuntu is using my NVIDIA graphics card?
Possible launchpad bug for this: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1714881
1
For me on a Dell latitude this was in the graphics menu in BIOS and something to do with enabling Optimus, it says only supports windows but solved the problem in ubuntu 18.04 thanks for the point in the right direction
– shaunhusain
Jan 2 at 7:05
add a comment |
Switch to Discrete Graphics on BIOS
Lenovo P51, UEFI BIOS Version N1UE40W, NVIDIA Quadro M1200 Mobile, Ubuntu 17.10, nvidia-384 installed from software-properties-gtk
:
- Hit Enter at boot time
- Press F1 for BIOS setup
- Config
- Graphics Device
- Select Discrete Graphics (Default was hybrid graphics)
- Security
- Secure Boot
- Secure Boot
- Select Disabled (Default enabled). If I don't do this, the NVIDIA driver simply gets ignored (and the boot problem does not happen either)
- Press F10 to save settings and exit boot menu
I think this makes the battery last less, but I'd rather have a desktop :-)
I also noticed that the problem is not reproducible every time. If I power cycle a few times, I also see the following behaviours:
- immediate computer restart during boot
- once everything actually worked
Then check that the GPU is actually being used: How do I check if Ubuntu is using my NVIDIA graphics card?
Possible launchpad bug for this: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1714881
Switch to Discrete Graphics on BIOS
Lenovo P51, UEFI BIOS Version N1UE40W, NVIDIA Quadro M1200 Mobile, Ubuntu 17.10, nvidia-384 installed from software-properties-gtk
:
- Hit Enter at boot time
- Press F1 for BIOS setup
- Config
- Graphics Device
- Select Discrete Graphics (Default was hybrid graphics)
- Security
- Secure Boot
- Secure Boot
- Select Disabled (Default enabled). If I don't do this, the NVIDIA driver simply gets ignored (and the boot problem does not happen either)
- Press F10 to save settings and exit boot menu
I think this makes the battery last less, but I'd rather have a desktop :-)
I also noticed that the problem is not reproducible every time. If I power cycle a few times, I also see the following behaviours:
- immediate computer restart during boot
- once everything actually worked
Then check that the GPU is actually being used: How do I check if Ubuntu is using my NVIDIA graphics card?
Possible launchpad bug for this: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1714881
edited Jan 2 at 9:00
answered Nov 15 '17 at 6:48
Ciro Santilli 新疆改造中心996ICU六四事件Ciro Santilli 新疆改造中心996ICU六四事件
10.7k55054
10.7k55054
1
For me on a Dell latitude this was in the graphics menu in BIOS and something to do with enabling Optimus, it says only supports windows but solved the problem in ubuntu 18.04 thanks for the point in the right direction
– shaunhusain
Jan 2 at 7:05
add a comment |
1
For me on a Dell latitude this was in the graphics menu in BIOS and something to do with enabling Optimus, it says only supports windows but solved the problem in ubuntu 18.04 thanks for the point in the right direction
– shaunhusain
Jan 2 at 7:05
1
1
For me on a Dell latitude this was in the graphics menu in BIOS and something to do with enabling Optimus, it says only supports windows but solved the problem in ubuntu 18.04 thanks for the point in the right direction
– shaunhusain
Jan 2 at 7:05
For me on a Dell latitude this was in the graphics menu in BIOS and something to do with enabling Optimus, it says only supports windows but solved the problem in ubuntu 18.04 thanks for the point in the right direction
– shaunhusain
Jan 2 at 7:05
add a comment |
I do not know the cause for this behaviour but I have the same problem on my ASUS laptop with GM108M [GeForce 840M]. My improvised solution is to disable automatic login. If I do login manually I have the normal startup. I use the proprietary driver.
I had automatic login disabled and it didn't work. Did you have the very same problem as me with the Persistence Daemon?
– Juraj.Lorinc
Nov 13 '17 at 15:07
Yes, I did and still do. Each time I start with the automatic login enabled I get the message you posted and after a couple of seconds my computer stops. So I restart with an older kernel, the automatic login goes normally, then I change to manual login, restart again by default and the laptop boot without any problem. It seems it has to do with the new kernel.
– MartinH
Nov 14 '17 at 22:10
add a comment |
I do not know the cause for this behaviour but I have the same problem on my ASUS laptop with GM108M [GeForce 840M]. My improvised solution is to disable automatic login. If I do login manually I have the normal startup. I use the proprietary driver.
I had automatic login disabled and it didn't work. Did you have the very same problem as me with the Persistence Daemon?
– Juraj.Lorinc
Nov 13 '17 at 15:07
Yes, I did and still do. Each time I start with the automatic login enabled I get the message you posted and after a couple of seconds my computer stops. So I restart with an older kernel, the automatic login goes normally, then I change to manual login, restart again by default and the laptop boot without any problem. It seems it has to do with the new kernel.
– MartinH
Nov 14 '17 at 22:10
add a comment |
I do not know the cause for this behaviour but I have the same problem on my ASUS laptop with GM108M [GeForce 840M]. My improvised solution is to disable automatic login. If I do login manually I have the normal startup. I use the proprietary driver.
I do not know the cause for this behaviour but I have the same problem on my ASUS laptop with GM108M [GeForce 840M]. My improvised solution is to disable automatic login. If I do login manually I have the normal startup. I use the proprietary driver.
answered Nov 13 '17 at 3:16
MartinHMartinH
611
611
I had automatic login disabled and it didn't work. Did you have the very same problem as me with the Persistence Daemon?
– Juraj.Lorinc
Nov 13 '17 at 15:07
Yes, I did and still do. Each time I start with the automatic login enabled I get the message you posted and after a couple of seconds my computer stops. So I restart with an older kernel, the automatic login goes normally, then I change to manual login, restart again by default and the laptop boot without any problem. It seems it has to do with the new kernel.
– MartinH
Nov 14 '17 at 22:10
add a comment |
I had automatic login disabled and it didn't work. Did you have the very same problem as me with the Persistence Daemon?
– Juraj.Lorinc
Nov 13 '17 at 15:07
Yes, I did and still do. Each time I start with the automatic login enabled I get the message you posted and after a couple of seconds my computer stops. So I restart with an older kernel, the automatic login goes normally, then I change to manual login, restart again by default and the laptop boot without any problem. It seems it has to do with the new kernel.
– MartinH
Nov 14 '17 at 22:10
I had automatic login disabled and it didn't work. Did you have the very same problem as me with the Persistence Daemon?
– Juraj.Lorinc
Nov 13 '17 at 15:07
I had automatic login disabled and it didn't work. Did you have the very same problem as me with the Persistence Daemon?
– Juraj.Lorinc
Nov 13 '17 at 15:07
Yes, I did and still do. Each time I start with the automatic login enabled I get the message you posted and after a couple of seconds my computer stops. So I restart with an older kernel, the automatic login goes normally, then I change to manual login, restart again by default and the laptop boot without any problem. It seems it has to do with the new kernel.
– MartinH
Nov 14 '17 at 22:10
Yes, I did and still do. Each time I start with the automatic login enabled I get the message you posted and after a couple of seconds my computer stops. So I restart with an older kernel, the automatic login goes normally, then I change to manual login, restart again by default and the laptop boot without any problem. It seems it has to do with the new kernel.
– MartinH
Nov 14 '17 at 22:10
add a comment |
Consider changing your display manager to lightdm. gdm3 doesn't work very well with nvidia drivers in my experience. I can not get it work at all if I'm using the modeset driver (and I've been trying for months). There are no workarounds that I have found. Nvidia, gdm3 and modern gnome are broken on both of my Optimus Thinkpads, you have to change one of those three, and the easiest is to replace gdm3 (if you change from gnome to another desktop environment, you will probably end up with lightdm anyway).
You are not trying to use modeset so you don't experience the same problem, but I have become biased against the unholy trinity of nvidia graphics, gnome and gdm3.
I have no problems with lightdm
sudo apt install lightdm
if necessary
sudo dpkg-reconfigure lightdm
and set it to the default (the installation of lightdm will ask you, but not if you already had it installed).
If you can't log in, you may feel a bit stuck. Hopefully you still have that old kernel. Otherwise you will have to try the advanced option and boot into recovery mode. I find that I choose 'enable networking' I usually get to a root shell in read/write which lets me do apt get stuff. If that doesn't work, it gets a bit harder; you can either reinstall or boot from a livecd and learn how to use chroot to do a pretend-login to your main installation. (something very useful to know).
add a comment |
Consider changing your display manager to lightdm. gdm3 doesn't work very well with nvidia drivers in my experience. I can not get it work at all if I'm using the modeset driver (and I've been trying for months). There are no workarounds that I have found. Nvidia, gdm3 and modern gnome are broken on both of my Optimus Thinkpads, you have to change one of those three, and the easiest is to replace gdm3 (if you change from gnome to another desktop environment, you will probably end up with lightdm anyway).
You are not trying to use modeset so you don't experience the same problem, but I have become biased against the unholy trinity of nvidia graphics, gnome and gdm3.
I have no problems with lightdm
sudo apt install lightdm
if necessary
sudo dpkg-reconfigure lightdm
and set it to the default (the installation of lightdm will ask you, but not if you already had it installed).
If you can't log in, you may feel a bit stuck. Hopefully you still have that old kernel. Otherwise you will have to try the advanced option and boot into recovery mode. I find that I choose 'enable networking' I usually get to a root shell in read/write which lets me do apt get stuff. If that doesn't work, it gets a bit harder; you can either reinstall or boot from a livecd and learn how to use chroot to do a pretend-login to your main installation. (something very useful to know).
add a comment |
Consider changing your display manager to lightdm. gdm3 doesn't work very well with nvidia drivers in my experience. I can not get it work at all if I'm using the modeset driver (and I've been trying for months). There are no workarounds that I have found. Nvidia, gdm3 and modern gnome are broken on both of my Optimus Thinkpads, you have to change one of those three, and the easiest is to replace gdm3 (if you change from gnome to another desktop environment, you will probably end up with lightdm anyway).
You are not trying to use modeset so you don't experience the same problem, but I have become biased against the unholy trinity of nvidia graphics, gnome and gdm3.
I have no problems with lightdm
sudo apt install lightdm
if necessary
sudo dpkg-reconfigure lightdm
and set it to the default (the installation of lightdm will ask you, but not if you already had it installed).
If you can't log in, you may feel a bit stuck. Hopefully you still have that old kernel. Otherwise you will have to try the advanced option and boot into recovery mode. I find that I choose 'enable networking' I usually get to a root shell in read/write which lets me do apt get stuff. If that doesn't work, it gets a bit harder; you can either reinstall or boot from a livecd and learn how to use chroot to do a pretend-login to your main installation. (something very useful to know).
Consider changing your display manager to lightdm. gdm3 doesn't work very well with nvidia drivers in my experience. I can not get it work at all if I'm using the modeset driver (and I've been trying for months). There are no workarounds that I have found. Nvidia, gdm3 and modern gnome are broken on both of my Optimus Thinkpads, you have to change one of those three, and the easiest is to replace gdm3 (if you change from gnome to another desktop environment, you will probably end up with lightdm anyway).
You are not trying to use modeset so you don't experience the same problem, but I have become biased against the unholy trinity of nvidia graphics, gnome and gdm3.
I have no problems with lightdm
sudo apt install lightdm
if necessary
sudo dpkg-reconfigure lightdm
and set it to the default (the installation of lightdm will ask you, but not if you already had it installed).
If you can't log in, you may feel a bit stuck. Hopefully you still have that old kernel. Otherwise you will have to try the advanced option and boot into recovery mode. I find that I choose 'enable networking' I usually get to a root shell in read/write which lets me do apt get stuff. If that doesn't work, it gets a bit harder; you can either reinstall or boot from a livecd and learn how to use chroot to do a pretend-login to your main installation. (something very useful to know).
answered Nov 16 '17 at 1:16
Tim RichardsonTim Richardson
761415
761415
add a comment |
add a comment |
$sudo apt-get purge nvidia*
will work fine.
Once the system gets started install the compatible driver.
add a comment |
$sudo apt-get purge nvidia*
will work fine.
Once the system gets started install the compatible driver.
add a comment |
$sudo apt-get purge nvidia*
will work fine.
Once the system gets started install the compatible driver.
$sudo apt-get purge nvidia*
will work fine.
Once the system gets started install the compatible driver.
edited Sep 18 '18 at 1:00
abu_bua
4,31981632
4,31981632
answered Sep 17 '18 at 23:02
VishalVishal
312
312
add a comment |
add a comment |
This answer actually did the job for me. None of the above solutions were applicable for me.
It all comes down to disabling the default startup of the nvidia persistence daemon and writing an own systemd service which starts on boot.
New contributor
add a comment |
This answer actually did the job for me. None of the above solutions were applicable for me.
It all comes down to disabling the default startup of the nvidia persistence daemon and writing an own systemd service which starts on boot.
New contributor
add a comment |
This answer actually did the job for me. None of the above solutions were applicable for me.
It all comes down to disabling the default startup of the nvidia persistence daemon and writing an own systemd service which starts on boot.
New contributor
This answer actually did the job for me. None of the above solutions were applicable for me.
It all comes down to disabling the default startup of the nvidia persistence daemon and writing an own systemd service which starts on boot.
New contributor
New contributor
answered 15 hours ago
AndréAndré
1011
1011
New contributor
New contributor
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%2f973605%2fubuntu-17-10-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