Ubuntu 17.10 stuck in login loop after installing CUDA-9 and nvidia driver 390
Clash Royale CLAN TAG#URR8PPP up vote
1
down vote
favorite
I have Ubuntu-17.10. I was trying to install tensorflow-gpu and for that I needed CUDA-9. While installing CUDA-9 my graphics driver updated to nvidia-390.
Now when I restarted my PC. I'm stuck in a log in screen loop. I have tried editing the linux line nvidia.modeset = 0, nomodeset, nouveau.modeset = 0, all together. Nothing works.
Now one potential solution is to go back to the previous driver. For that, I enter TTY screen and enter my username, password. Now, this happens on TTY:
It goes back to the first login TTY screen in about 15 secs.
edit1:
Found a way to purge all the Nvidia drivers using ubuntu recovery mode. But still, the same problem continues.
drivers nvidia 17.10 cuda
asked Mar 11 at 8:25
Samar Yadav
86
add a comment |Â
up vote
1
down vote
favorite
I have Ubuntu-17.10. I was trying to install tensorflow-gpu and for that I needed CUDA-9. While installing CUDA-9 my graphics driver updated to nvidia-390.
Now when I restarted my PC. I'm stuck in a log in screen loop. I have tried editing the linux line nvidia.modeset = 0, nomodeset, nouveau.modeset = 0, all together. Nothing works.
Now one potential solution is to go back to the previous driver. For that, I enter TTY screen and enter my username, password. Now, this happens on TTY:
It goes back to the first login TTY screen in about 15 secs.
edit1:
Found a way to purge all the Nvidia drivers using ubuntu recovery mode. But still, the same problem continues.
drivers nvidia 17.10 cuda
asked Mar 11 at 8:25
Samar Yadav
86
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I have Ubuntu-17.10. I was trying to install tensorflow-gpu and for that I needed CUDA-9. While installing CUDA-9 my graphics driver updated to nvidia-390.
Now when I restarted my PC. I'm stuck in a log in screen loop. I have tried editing the linux line nvidia.modeset = 0, nomodeset, nouveau.modeset = 0, all together. Nothing works.
Now one potential solution is to go back to the previous driver. For that, I enter TTY screen and enter my username, password. Now, this happens on TTY:
It goes back to the first login TTY screen in about 15 secs.
edit1:
Found a way to purge all the Nvidia drivers using ubuntu recovery mode. But still, the same problem continues.
drivers nvidia 17.10 cuda
asked Mar 11 at 8:25
Samar Yadav
86
I have Ubuntu-17.10. I was trying to install tensorflow-gpu and for that I needed CUDA-9. While installing CUDA-9 my graphics driver updated to nvidia-390.
Now when I restarted my PC. I'm stuck in a log in screen loop. I have tried editing the linux line nvidia.modeset = 0, nomodeset, nouveau.modeset = 0, all together. Nothing works.
Now one potential solution is to go back to the previous driver. For that, I enter TTY screen and enter my username, password. Now, this happens on TTY:
It goes back to the first login TTY screen in about 15 secs.
edit1:
Found a way to purge all the Nvidia drivers using ubuntu recovery mode. But still, the same problem continues.
drivers nvidia 17.10 cuda
drivers nvidia 17.10 cuda
asked Mar 11 at 8:25
Samar Yadav
86
asked Mar 11 at 8:25
Samar Yadav
86
edited Mar 11 at 13:13
asked Mar 11 at 8:25
Samar Yadav
86
asked Mar 11 at 8:25
Samar Yadav
86
asked Mar 11 at 8:25
Samar Yadav
86
86
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
It looks like you added something to your .bashrc or .profile during installation of either cuda or cudnn and probably made a mistake while doing so. If you boot into recovery mode you should be able to login as root, navigate to your user's home directory and investigate those files to look for errors.
If you do not find the error immediately, just move the files out of the way by renaming them. This way you should at least be able to login again.
If that doesn't help, try the same with the global shell configuration files in /etc/bash.bashrc, /etc/profile and /etc/profile.d/*
answered Mar 11 at 21:52
Sebastian Stark
4,723938
It didn't work. Nothing changed actually. Moments like these make me hate Ubuntu.
– Samar Yadav
Mar 12 at 11:41
Please try checking again the files from my edited answer above.
– Sebastian Stark
Mar 12 at 13:25
That worked. You are a genius man. Thank you
– Samar Yadav
Mar 14 at 3:33
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
It looks like you added something to your .bashrc or .profile during installation of either cuda or cudnn and probably made a mistake while doing so. If you boot into recovery mode you should be able to login as root, navigate to your user's home directory and investigate those files to look for errors.
If you do not find the error immediately, just move the files out of the way by renaming them. This way you should at least be able to login again.
If that doesn't help, try the same with the global shell configuration files in /etc/bash.bashrc, /etc/profile and /etc/profile.d/*
answered Mar 11 at 21:52
Sebastian Stark
4,723938
It didn't work. Nothing changed actually. Moments like these make me hate Ubuntu.
– Samar Yadav
Mar 12 at 11:41
Please try checking again the files from my edited answer above.
– Sebastian Stark
Mar 12 at 13:25
That worked. You are a genius man. Thank you
– Samar Yadav
Mar 14 at 3:33
add a comment |Â
up vote
2
down vote
accepted
It looks like you added something to your .bashrc or .profile during installation of either cuda or cudnn and probably made a mistake while doing so. If you boot into recovery mode you should be able to login as root, navigate to your user's home directory and investigate those files to look for errors.
If you do not find the error immediately, just move the files out of the way by renaming them. This way you should at least be able to login again.
If that doesn't help, try the same with the global shell configuration files in /etc/bash.bashrc, /etc/profile and /etc/profile.d/*
answered Mar 11 at 21:52
Sebastian Stark
4,723938
It didn't work. Nothing changed actually. Moments like these make me hate Ubuntu.
– Samar Yadav
Mar 12 at 11:41
Please try checking again the files from my edited answer above.
– Sebastian Stark
Mar 12 at 13:25
That worked. You are a genius man. Thank you
– Samar Yadav
Mar 14 at 3:33
add a comment |Â
up vote
2
down vote
accepted
up vote
2
down vote
accepted
It looks like you added something to your .bashrc or .profile during installation of either cuda or cudnn and probably made a mistake while doing so. If you boot into recovery mode you should be able to login as root, navigate to your user's home directory and investigate those files to look for errors.
If you do not find the error immediately, just move the files out of the way by renaming them. This way you should at least be able to login again.
If that doesn't help, try the same with the global shell configuration files in /etc/bash.bashrc, /etc/profile and /etc/profile.d/*
answered Mar 11 at 21:52
Sebastian Stark
4,723938
It looks like you added something to your .bashrc or .profile during installation of either cuda or cudnn and probably made a mistake while doing so. If you boot into recovery mode you should be able to login as root, navigate to your user's home directory and investigate those files to look for errors.
If you do not find the error immediately, just move the files out of the way by renaming them. This way you should at least be able to login again.
If that doesn't help, try the same with the global shell configuration files in /etc/bash.bashrc, /etc/profile and /etc/profile.d/*
answered Mar 11 at 21:52
Sebastian Stark
4,723938
edited Mar 12 at 13:24
answered Mar 11 at 21:52
Sebastian Stark
4,723938
answered Mar 11 at 21:52
Sebastian Stark
4,723938
answered Mar 11 at 21:52
Sebastian Stark
4,723938
4,723938
It didn't work. Nothing changed actually. Moments like these make me hate Ubuntu.
– Samar Yadav
Mar 12 at 11:41
Please try checking again the files from my edited answer above.
– Sebastian Stark
Mar 12 at 13:25
That worked. You are a genius man. Thank you
– Samar Yadav
Mar 14 at 3:33
add a comment |Â
It didn't work. Nothing changed actually. Moments like these make me hate Ubuntu.
– Samar Yadav
Mar 12 at 11:41
Please try checking again the files from my edited answer above.
– Sebastian Stark
Mar 12 at 13:25
That worked. You are a genius man. Thank you
– Samar Yadav
Mar 14 at 3:33
It didn't work. Nothing changed actually. Moments like these make me hate Ubuntu.
– Samar Yadav
Mar 12 at 11:41
It didn't work. Nothing changed actually. Moments like these make me hate Ubuntu.
– Samar Yadav
Mar 12 at 11:41
Please try checking again the files from my edited answer above.
– Sebastian Stark
Mar 12 at 13:25
Please try checking again the files from my edited answer above.
– Sebastian Stark
Mar 12 at 13:25
That worked. You are a genius man. Thank you
– Samar Yadav
Mar 14 at 3:33
That worked. You are a genius man. Thank you
– Samar Yadav
Mar 14 at 3:33
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%2f1013824%2fubuntu-17-10-stuck-in-login-loop-after-installing-cuda-9-and-nvidia-driver-390%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