Nvidia Persistance Daemon failed to start with drivers 390.xx
Clash Royale CLAN TAG#URR8PPP up vote
3
down vote
favorite
I am currently using 384.111 drivers, which work just fine. However, I tried upgrading to 390.12 initially, which caused this error, and 390.25 does too. I suspect 390.42 will have the same issue. I've installed both from the .run on Nvidia's website and the nvidia-384 package.
So, whenever I start up a 390.xx driver from the Ubuntu grub option, it loads with the regular splash screen and then into tty1, except it starts blinking; as in, the screen turns off and then on again. While the screen is off, none of my keystrokes are registered, meaning I have to spam a key a couple times for it to show up. This also makes it impossible to enter my password as I cannot see if a keystroke has been registered.
The thing is, when I select the Advanced options for Ubuntu grub option and then select recovery mode and then Resume, it boots normally into gdm3 and I can use the system as per usual.
I tried booting into Ubuntu and then pressing ESC to show tty1, and saw what's in the screenshot.
Specs
- Ubuntu 16.04
- 4.13.0-37-generic
- GTX 1060 6GB
boot drivers nvidia
edited Mar 22 at 18:40
David Foerster
26.3k1362106
asked Mar 22 at 12:10
Julian
988
add a comment |Â
up vote
3
down vote
favorite
I am currently using 384.111 drivers, which work just fine. However, I tried upgrading to 390.12 initially, which caused this error, and 390.25 does too. I suspect 390.42 will have the same issue. I've installed both from the .run on Nvidia's website and the nvidia-384 package.
So, whenever I start up a 390.xx driver from the Ubuntu grub option, it loads with the regular splash screen and then into tty1, except it starts blinking; as in, the screen turns off and then on again. While the screen is off, none of my keystrokes are registered, meaning I have to spam a key a couple times for it to show up. This also makes it impossible to enter my password as I cannot see if a keystroke has been registered.
The thing is, when I select the Advanced options for Ubuntu grub option and then select recovery mode and then Resume, it boots normally into gdm3 and I can use the system as per usual.
I tried booting into Ubuntu and then pressing ESC to show tty1, and saw what's in the screenshot.
Specs
- Ubuntu 16.04
- 4.13.0-37-generic
- GTX 1060 6GB
boot drivers nvidia
edited Mar 22 at 18:40
David Foerster
26.3k1362106
asked Mar 22 at 12:10
Julian
988
add a comment |Â
up vote
3
down vote
favorite
up vote
3
down vote
favorite
I am currently using 384.111 drivers, which work just fine. However, I tried upgrading to 390.12 initially, which caused this error, and 390.25 does too. I suspect 390.42 will have the same issue. I've installed both from the .run on Nvidia's website and the nvidia-384 package.
So, whenever I start up a 390.xx driver from the Ubuntu grub option, it loads with the regular splash screen and then into tty1, except it starts blinking; as in, the screen turns off and then on again. While the screen is off, none of my keystrokes are registered, meaning I have to spam a key a couple times for it to show up. This also makes it impossible to enter my password as I cannot see if a keystroke has been registered.
The thing is, when I select the Advanced options for Ubuntu grub option and then select recovery mode and then Resume, it boots normally into gdm3 and I can use the system as per usual.
I tried booting into Ubuntu and then pressing ESC to show tty1, and saw what's in the screenshot.
Specs
- Ubuntu 16.04
- 4.13.0-37-generic
- GTX 1060 6GB
boot drivers nvidia
edited Mar 22 at 18:40
David Foerster
26.3k1362106
asked Mar 22 at 12:10
Julian
988
I am currently using 384.111 drivers, which work just fine. However, I tried upgrading to 390.12 initially, which caused this error, and 390.25 does too. I suspect 390.42 will have the same issue. I've installed both from the .run on Nvidia's website and the nvidia-384 package.
So, whenever I start up a 390.xx driver from the Ubuntu grub option, it loads with the regular splash screen and then into tty1, except it starts blinking; as in, the screen turns off and then on again. While the screen is off, none of my keystrokes are registered, meaning I have to spam a key a couple times for it to show up. This also makes it impossible to enter my password as I cannot see if a keystroke has been registered.
The thing is, when I select the Advanced options for Ubuntu grub option and then select recovery mode and then Resume, it boots normally into gdm3 and I can use the system as per usual.
I tried booting into Ubuntu and then pressing ESC to show tty1, and saw what's in the screenshot.
Specs
- Ubuntu 16.04
- 4.13.0-37-generic
- GTX 1060 6GB
boot drivers nvidia
boot drivers nvidia
edited Mar 22 at 18:40
David Foerster
26.3k1362106
asked Mar 22 at 12:10
Julian
988
edited Mar 22 at 18:40
David Foerster
26.3k1362106
asked Mar 22 at 12:10
Julian
988
edited Mar 22 at 18:40
David Foerster
26.3k1362106
edited Mar 22 at 18:40
David Foerster
26.3k1362106
edited Mar 22 at 18:40
David Foerster
26.3k1362106
26.3k1362106
asked Mar 22 at 12:10
Julian
988
asked Mar 22 at 12:10
Julian
988
asked Mar 22 at 12:10
Julian
988
988
add a comment |Â
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
5
down vote
I would disable the nvidia-persistenced daemon. It's really meant for GPU server applications using CUDA, where there isn't an X server running. All it does is open the GPU device and hold it open. The GPU takes a couple seconds to initialize, so the persistence daemon is useful for running lots of short-duration CUDA jobs. On a desktop machine, the X server will hold open the GPU device, so nvidia-persistenced doesn't have any benefit.
That said, it sounds like you may still be having general GPU driver issues. I don't think it would hurt to try the 390.42 version -- there seem to be a number of bugs recently, but hopefully Nvidia is working on fixing them.
answered Mar 22 at 12:36
Mike Hicks
762
Thanks for the suggestion! I will try that and get back to you.
– Julian
Mar 22 at 13:23
add a comment |Â
up vote
0
down vote
I found a workaround for this issue that's been working for me for a couple of weeks now.
Simply set grub to text mode, add the following line to grub and update it:
GRUB_GFXPAYLOAD_LINUX=text
Hope it helps
PS: disabling nvidia-persistance did not work for me
edited Sep 13 at 8:07
NIMISHAN
6121819
answered Sep 13 at 2:02
Roberto
1
New contributor
Roberto 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 |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
5
down vote
I would disable the nvidia-persistenced daemon. It's really meant for GPU server applications using CUDA, where there isn't an X server running. All it does is open the GPU device and hold it open. The GPU takes a couple seconds to initialize, so the persistence daemon is useful for running lots of short-duration CUDA jobs. On a desktop machine, the X server will hold open the GPU device, so nvidia-persistenced doesn't have any benefit.
That said, it sounds like you may still be having general GPU driver issues. I don't think it would hurt to try the 390.42 version -- there seem to be a number of bugs recently, but hopefully Nvidia is working on fixing them.
answered Mar 22 at 12:36
Mike Hicks
762
Thanks for the suggestion! I will try that and get back to you.
– Julian
Mar 22 at 13:23
add a comment |Â
up vote
5
down vote
I would disable the nvidia-persistenced daemon. It's really meant for GPU server applications using CUDA, where there isn't an X server running. All it does is open the GPU device and hold it open. The GPU takes a couple seconds to initialize, so the persistence daemon is useful for running lots of short-duration CUDA jobs. On a desktop machine, the X server will hold open the GPU device, so nvidia-persistenced doesn't have any benefit.
That said, it sounds like you may still be having general GPU driver issues. I don't think it would hurt to try the 390.42 version -- there seem to be a number of bugs recently, but hopefully Nvidia is working on fixing them.
answered Mar 22 at 12:36
Mike Hicks
762
Thanks for the suggestion! I will try that and get back to you.
– Julian
Mar 22 at 13:23
add a comment |Â
up vote
5
down vote
up vote
5
down vote
I would disable the nvidia-persistenced daemon. It's really meant for GPU server applications using CUDA, where there isn't an X server running. All it does is open the GPU device and hold it open. The GPU takes a couple seconds to initialize, so the persistence daemon is useful for running lots of short-duration CUDA jobs. On a desktop machine, the X server will hold open the GPU device, so nvidia-persistenced doesn't have any benefit.
That said, it sounds like you may still be having general GPU driver issues. I don't think it would hurt to try the 390.42 version -- there seem to be a number of bugs recently, but hopefully Nvidia is working on fixing them.
answered Mar 22 at 12:36
Mike Hicks
762
I would disable the nvidia-persistenced daemon. It's really meant for GPU server applications using CUDA, where there isn't an X server running. All it does is open the GPU device and hold it open. The GPU takes a couple seconds to initialize, so the persistence daemon is useful for running lots of short-duration CUDA jobs. On a desktop machine, the X server will hold open the GPU device, so nvidia-persistenced doesn't have any benefit.
That said, it sounds like you may still be having general GPU driver issues. I don't think it would hurt to try the 390.42 version -- there seem to be a number of bugs recently, but hopefully Nvidia is working on fixing them.
answered Mar 22 at 12:36
Mike Hicks
762
answered Mar 22 at 12:36
Mike Hicks
762
answered Mar 22 at 12:36
Mike Hicks
762
answered Mar 22 at 12:36
Mike Hicks
762
762
Thanks for the suggestion! I will try that and get back to you.
– Julian
Mar 22 at 13:23
add a comment |Â
Thanks for the suggestion! I will try that and get back to you.
– Julian
Mar 22 at 13:23
Thanks for the suggestion! I will try that and get back to you.
– Julian
Mar 22 at 13:23
Thanks for the suggestion! I will try that and get back to you.
– Julian
Mar 22 at 13:23
add a comment |Â
up vote
0
down vote
I found a workaround for this issue that's been working for me for a couple of weeks now.
Simply set grub to text mode, add the following line to grub and update it:
GRUB_GFXPAYLOAD_LINUX=text
Hope it helps
PS: disabling nvidia-persistance did not work for me
edited Sep 13 at 8:07
NIMISHAN
6121819
answered Sep 13 at 2:02
Roberto
1
New contributor
Roberto 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 |Â
up vote
0
down vote
I found a workaround for this issue that's been working for me for a couple of weeks now.
Simply set grub to text mode, add the following line to grub and update it:
GRUB_GFXPAYLOAD_LINUX=text
Hope it helps
PS: disabling nvidia-persistance did not work for me
edited Sep 13 at 8:07
NIMISHAN
6121819
answered Sep 13 at 2:02
Roberto
1
New contributor
Roberto 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 |Â
up vote
0
down vote
up vote
0
down vote
I found a workaround for this issue that's been working for me for a couple of weeks now.
Simply set grub to text mode, add the following line to grub and update it:
GRUB_GFXPAYLOAD_LINUX=text
Hope it helps
PS: disabling nvidia-persistance did not work for me
edited Sep 13 at 8:07
NIMISHAN
6121819
answered Sep 13 at 2:02
Roberto
1
New contributor
Roberto is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I found a workaround for this issue that's been working for me for a couple of weeks now.
Simply set grub to text mode, add the following line to grub and update it:
GRUB_GFXPAYLOAD_LINUX=text
Hope it helps
PS: disabling nvidia-persistance did not work for me
edited Sep 13 at 8:07
NIMISHAN
6121819
answered Sep 13 at 2:02
Roberto
1
New contributor
Roberto is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Sep 13 at 8:07
NIMISHAN
6121819
edited Sep 13 at 8:07
NIMISHAN
6121819
edited Sep 13 at 8:07
NIMISHAN
6121819
6121819
answered Sep 13 at 2:02
Roberto
1
New contributor
Roberto is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Sep 13 at 2:02
Roberto
1
answered Sep 13 at 2:02
Roberto
1
1
New contributor
Roberto is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Roberto is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Roberto 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 |Â
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%2f1018232%2fnvidia-persistance-daemon-failed-to-start-with-drivers-390-xx%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