Login loop likely due to NVIDIA drivers with CUDA installed
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
A few days ago I ran a sudo apt update
+ upgrade
on my Ubuntu 16.04. I had not done so for about 2 months. In the meantime, I had changed my graphics card from a GTX 1060 to a GTX 1070.
When today I tried to login, I discovered I had entered an annoying infinite login loop. This is the content of my xsessions-errors
log:
X Error of failed request: BadWindow (invalid Window parameter)
Major opcode of failed request: 155 (NV-GLX)
Minor opcode of failed request: 4 ()
Resource id in failed request: 0x3d0
Serial number of failed request: 46
Current serial number in output stream: 46
openConnection: connect: No such file or directory
cannot connect to brltty at :0
[...]
Looking at the promising answers to this question, I tried the following:
- Check the ownership of
.Xauthority
belongs to me, and notroot
(it does belong to me) - Reconfigure
lightdm
- Reinstall
lightdm
- Check if my
/home/
is full (it's at 44% usage)
all unsuccessfully. Then I started believing my issue lies in a NVIDIA drivers update, as I read multiple sources on various websites explaining that was a common issue. It's worth adding I did not make any recent modification to ./profile
or similar, and never run the command startx
in my life.
I found these potential solutions to my issue that revolve around NVIDIA drivers:
- installing
nvidia-current
drivers (older than latest supported by
NVIDIA) as proposed here; - reinstalling NVIDIA drivers by running
nvidia-installer.sh
as proposed here;
My problem is that on my computer I spent tens of hours configuring CUDA, in a delicate balance with NVIDIA drivers, and various packages. For installing CUDA, I also had to install a specific Ubuntu kernel version (4.4).
Is there a chance that my CUDA environment will break if I touch the drivers? Is there actually anything else I could try to fix the issue?
16.04 drivers nvidia login cuda
add a comment |
A few days ago I ran a sudo apt update
+ upgrade
on my Ubuntu 16.04. I had not done so for about 2 months. In the meantime, I had changed my graphics card from a GTX 1060 to a GTX 1070.
When today I tried to login, I discovered I had entered an annoying infinite login loop. This is the content of my xsessions-errors
log:
X Error of failed request: BadWindow (invalid Window parameter)
Major opcode of failed request: 155 (NV-GLX)
Minor opcode of failed request: 4 ()
Resource id in failed request: 0x3d0
Serial number of failed request: 46
Current serial number in output stream: 46
openConnection: connect: No such file or directory
cannot connect to brltty at :0
[...]
Looking at the promising answers to this question, I tried the following:
- Check the ownership of
.Xauthority
belongs to me, and notroot
(it does belong to me) - Reconfigure
lightdm
- Reinstall
lightdm
- Check if my
/home/
is full (it's at 44% usage)
all unsuccessfully. Then I started believing my issue lies in a NVIDIA drivers update, as I read multiple sources on various websites explaining that was a common issue. It's worth adding I did not make any recent modification to ./profile
or similar, and never run the command startx
in my life.
I found these potential solutions to my issue that revolve around NVIDIA drivers:
- installing
nvidia-current
drivers (older than latest supported by
NVIDIA) as proposed here; - reinstalling NVIDIA drivers by running
nvidia-installer.sh
as proposed here;
My problem is that on my computer I spent tens of hours configuring CUDA, in a delicate balance with NVIDIA drivers, and various packages. For installing CUDA, I also had to install a specific Ubuntu kernel version (4.4).
Is there a chance that my CUDA environment will break if I touch the drivers? Is there actually anything else I could try to fix the issue?
16.04 drivers nvidia login cuda
add a comment |
A few days ago I ran a sudo apt update
+ upgrade
on my Ubuntu 16.04. I had not done so for about 2 months. In the meantime, I had changed my graphics card from a GTX 1060 to a GTX 1070.
When today I tried to login, I discovered I had entered an annoying infinite login loop. This is the content of my xsessions-errors
log:
X Error of failed request: BadWindow (invalid Window parameter)
Major opcode of failed request: 155 (NV-GLX)
Minor opcode of failed request: 4 ()
Resource id in failed request: 0x3d0
Serial number of failed request: 46
Current serial number in output stream: 46
openConnection: connect: No such file or directory
cannot connect to brltty at :0
[...]
Looking at the promising answers to this question, I tried the following:
- Check the ownership of
.Xauthority
belongs to me, and notroot
(it does belong to me) - Reconfigure
lightdm
- Reinstall
lightdm
- Check if my
/home/
is full (it's at 44% usage)
all unsuccessfully. Then I started believing my issue lies in a NVIDIA drivers update, as I read multiple sources on various websites explaining that was a common issue. It's worth adding I did not make any recent modification to ./profile
or similar, and never run the command startx
in my life.
I found these potential solutions to my issue that revolve around NVIDIA drivers:
- installing
nvidia-current
drivers (older than latest supported by
NVIDIA) as proposed here; - reinstalling NVIDIA drivers by running
nvidia-installer.sh
as proposed here;
My problem is that on my computer I spent tens of hours configuring CUDA, in a delicate balance with NVIDIA drivers, and various packages. For installing CUDA, I also had to install a specific Ubuntu kernel version (4.4).
Is there a chance that my CUDA environment will break if I touch the drivers? Is there actually anything else I could try to fix the issue?
16.04 drivers nvidia login cuda
A few days ago I ran a sudo apt update
+ upgrade
on my Ubuntu 16.04. I had not done so for about 2 months. In the meantime, I had changed my graphics card from a GTX 1060 to a GTX 1070.
When today I tried to login, I discovered I had entered an annoying infinite login loop. This is the content of my xsessions-errors
log:
X Error of failed request: BadWindow (invalid Window parameter)
Major opcode of failed request: 155 (NV-GLX)
Minor opcode of failed request: 4 ()
Resource id in failed request: 0x3d0
Serial number of failed request: 46
Current serial number in output stream: 46
openConnection: connect: No such file or directory
cannot connect to brltty at :0
[...]
Looking at the promising answers to this question, I tried the following:
- Check the ownership of
.Xauthority
belongs to me, and notroot
(it does belong to me) - Reconfigure
lightdm
- Reinstall
lightdm
- Check if my
/home/
is full (it's at 44% usage)
all unsuccessfully. Then I started believing my issue lies in a NVIDIA drivers update, as I read multiple sources on various websites explaining that was a common issue. It's worth adding I did not make any recent modification to ./profile
or similar, and never run the command startx
in my life.
I found these potential solutions to my issue that revolve around NVIDIA drivers:
- installing
nvidia-current
drivers (older than latest supported by
NVIDIA) as proposed here; - reinstalling NVIDIA drivers by running
nvidia-installer.sh
as proposed here;
My problem is that on my computer I spent tens of hours configuring CUDA, in a delicate balance with NVIDIA drivers, and various packages. For installing CUDA, I also had to install a specific Ubuntu kernel version (4.4).
Is there a chance that my CUDA environment will break if I touch the drivers? Is there actually anything else I could try to fix the issue?
16.04 drivers nvidia login cuda
16.04 drivers nvidia login cuda
edited Aug 27 '18 at 9:13
raggot
asked Aug 26 '18 at 14:42
raggotraggot
15118
15118
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
The solution is try to reinstall the driver and reconfigure lightdm also. In the worst case you will need to install CUDA again but try reinstalling the driver first by downloading the installer from nvidia(the shell script).
Is there a chance that my CUDA environment will break if I touch the drivers? Is there actually anything else I could try to fix the issue?
Not necessarily. As long as your drivers are in place. nvcc
should function properly.
I eventually solved the problem yesterday night, and I indeed ended up reinstalling the drivers (actually went from version 387 to 390). Could you still elaborate on the 'shell script'? I followed these instructions but read somewhere on CUDA's forum that this is not an official NVIDIA repository and saw myself it's actually quite behind in version.
– raggot
Aug 28 '18 at 11:53
sorry i meant the run file
– Pradeep Kumar
Aug 28 '18 at 12:32
If you can list the instructions such aswget ...
andrun ...
I'll accept your answer. I am bound to console operations
– raggot
Aug 28 '18 at 14:43
wget this and try to install by settingquiet splash nomodeset
.
– Pradeep Kumar
Aug 28 '18 at 16:04
add a comment |
To other people facing my same issue, I suggest trying the following:
mv .Xauthority .Xauthority-backup
which renames .Xauthority
and forces the creation of a new one with the next login attempt. In case the problem laid there, then the login would work.
In my case, however, what actually worked was doing what I was afraid doing, which is reinstalling the NVIDIA drivers. For users of CUDA, the driver version that needs to be installed is defined by the documentation. In my case, as I had CUDA 9.1, it's at least driver version 390.46 (as per the moment I write this answer, of course).
I followed the instructions found on this website to (re)install the drivers I needed. I actually also found this post from the CUDA forum, written by a moderator, explaining how on his experience using this source for the drivers may not always work, as they are not officially released by NVIDIA. In my case, it still worked and I therefore share it.
First, remove the installed NVIDIA drivers:
sudo apt-get purge nvidia*
Add the repository for the graphics driver:
sudo add-apt-repository ppa:graphics-drivers/ppa
sudo apt update
Then install the correct version of the drivers (in my case, xxx = 390)
sudo apt install nvidia-xxx
And finally
reboot
The login problem should now be solved. In my case, the CUDA environment did not
get affected and all my project still ran normally.
390.48 is the current 390 driver from the standard repositories, no need for the graphics-drivers ppa. The package name is nvidia-driver-390 (no longer in the form nvidia-xxx).
– ubfan1
Aug 28 '18 at 15:25
@ubfan1 Ah, thanks. So what command should I use to install it the proper way?
– raggot
Aug 29 '18 at 9:57
Clean out any previous nvidia packages and from Software and Updates, check the sources (I think universe is the one needed), and then under the Additional Drivers tab, let it scan and select the one that says "tested", or the latest one if a tested one is not available.
– ubfan1
Aug 29 '18 at 16:41
@ubfan1 Thank you. If you are willing to write an answer with the commands one would need to type I'll be happy to accept it.
– raggot
Aug 30 '18 at 8:49
A search of this site already gives many correct answers to the Nvidia login loop problem, but you can accept your own answer since it worked for you.
– ubfan1
Aug 30 '18 at 15:12
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%2f1069116%2flogin-loop-likely-due-to-nvidia-drivers-with-cuda-installed%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
The solution is try to reinstall the driver and reconfigure lightdm also. In the worst case you will need to install CUDA again but try reinstalling the driver first by downloading the installer from nvidia(the shell script).
Is there a chance that my CUDA environment will break if I touch the drivers? Is there actually anything else I could try to fix the issue?
Not necessarily. As long as your drivers are in place. nvcc
should function properly.
I eventually solved the problem yesterday night, and I indeed ended up reinstalling the drivers (actually went from version 387 to 390). Could you still elaborate on the 'shell script'? I followed these instructions but read somewhere on CUDA's forum that this is not an official NVIDIA repository and saw myself it's actually quite behind in version.
– raggot
Aug 28 '18 at 11:53
sorry i meant the run file
– Pradeep Kumar
Aug 28 '18 at 12:32
If you can list the instructions such aswget ...
andrun ...
I'll accept your answer. I am bound to console operations
– raggot
Aug 28 '18 at 14:43
wget this and try to install by settingquiet splash nomodeset
.
– Pradeep Kumar
Aug 28 '18 at 16:04
add a comment |
The solution is try to reinstall the driver and reconfigure lightdm also. In the worst case you will need to install CUDA again but try reinstalling the driver first by downloading the installer from nvidia(the shell script).
Is there a chance that my CUDA environment will break if I touch the drivers? Is there actually anything else I could try to fix the issue?
Not necessarily. As long as your drivers are in place. nvcc
should function properly.
I eventually solved the problem yesterday night, and I indeed ended up reinstalling the drivers (actually went from version 387 to 390). Could you still elaborate on the 'shell script'? I followed these instructions but read somewhere on CUDA's forum that this is not an official NVIDIA repository and saw myself it's actually quite behind in version.
– raggot
Aug 28 '18 at 11:53
sorry i meant the run file
– Pradeep Kumar
Aug 28 '18 at 12:32
If you can list the instructions such aswget ...
andrun ...
I'll accept your answer. I am bound to console operations
– raggot
Aug 28 '18 at 14:43
wget this and try to install by settingquiet splash nomodeset
.
– Pradeep Kumar
Aug 28 '18 at 16:04
add a comment |
The solution is try to reinstall the driver and reconfigure lightdm also. In the worst case you will need to install CUDA again but try reinstalling the driver first by downloading the installer from nvidia(the shell script).
Is there a chance that my CUDA environment will break if I touch the drivers? Is there actually anything else I could try to fix the issue?
Not necessarily. As long as your drivers are in place. nvcc
should function properly.
The solution is try to reinstall the driver and reconfigure lightdm also. In the worst case you will need to install CUDA again but try reinstalling the driver first by downloading the installer from nvidia(the shell script).
Is there a chance that my CUDA environment will break if I touch the drivers? Is there actually anything else I could try to fix the issue?
Not necessarily. As long as your drivers are in place. nvcc
should function properly.
edited Aug 28 '18 at 10:47
abu_bua
4,31981632
4,31981632
answered Aug 28 '18 at 10:41
Pradeep KumarPradeep Kumar
1
1
I eventually solved the problem yesterday night, and I indeed ended up reinstalling the drivers (actually went from version 387 to 390). Could you still elaborate on the 'shell script'? I followed these instructions but read somewhere on CUDA's forum that this is not an official NVIDIA repository and saw myself it's actually quite behind in version.
– raggot
Aug 28 '18 at 11:53
sorry i meant the run file
– Pradeep Kumar
Aug 28 '18 at 12:32
If you can list the instructions such aswget ...
andrun ...
I'll accept your answer. I am bound to console operations
– raggot
Aug 28 '18 at 14:43
wget this and try to install by settingquiet splash nomodeset
.
– Pradeep Kumar
Aug 28 '18 at 16:04
add a comment |
I eventually solved the problem yesterday night, and I indeed ended up reinstalling the drivers (actually went from version 387 to 390). Could you still elaborate on the 'shell script'? I followed these instructions but read somewhere on CUDA's forum that this is not an official NVIDIA repository and saw myself it's actually quite behind in version.
– raggot
Aug 28 '18 at 11:53
sorry i meant the run file
– Pradeep Kumar
Aug 28 '18 at 12:32
If you can list the instructions such aswget ...
andrun ...
I'll accept your answer. I am bound to console operations
– raggot
Aug 28 '18 at 14:43
wget this and try to install by settingquiet splash nomodeset
.
– Pradeep Kumar
Aug 28 '18 at 16:04
I eventually solved the problem yesterday night, and I indeed ended up reinstalling the drivers (actually went from version 387 to 390). Could you still elaborate on the 'shell script'? I followed these instructions but read somewhere on CUDA's forum that this is not an official NVIDIA repository and saw myself it's actually quite behind in version.
– raggot
Aug 28 '18 at 11:53
I eventually solved the problem yesterday night, and I indeed ended up reinstalling the drivers (actually went from version 387 to 390). Could you still elaborate on the 'shell script'? I followed these instructions but read somewhere on CUDA's forum that this is not an official NVIDIA repository and saw myself it's actually quite behind in version.
– raggot
Aug 28 '18 at 11:53
sorry i meant the run file
– Pradeep Kumar
Aug 28 '18 at 12:32
sorry i meant the run file
– Pradeep Kumar
Aug 28 '18 at 12:32
If you can list the instructions such as
wget ...
and run ...
I'll accept your answer. I am bound to console operations– raggot
Aug 28 '18 at 14:43
If you can list the instructions such as
wget ...
and run ...
I'll accept your answer. I am bound to console operations– raggot
Aug 28 '18 at 14:43
wget this and try to install by setting
quiet splash nomodeset
.– Pradeep Kumar
Aug 28 '18 at 16:04
wget this and try to install by setting
quiet splash nomodeset
.– Pradeep Kumar
Aug 28 '18 at 16:04
add a comment |
To other people facing my same issue, I suggest trying the following:
mv .Xauthority .Xauthority-backup
which renames .Xauthority
and forces the creation of a new one with the next login attempt. In case the problem laid there, then the login would work.
In my case, however, what actually worked was doing what I was afraid doing, which is reinstalling the NVIDIA drivers. For users of CUDA, the driver version that needs to be installed is defined by the documentation. In my case, as I had CUDA 9.1, it's at least driver version 390.46 (as per the moment I write this answer, of course).
I followed the instructions found on this website to (re)install the drivers I needed. I actually also found this post from the CUDA forum, written by a moderator, explaining how on his experience using this source for the drivers may not always work, as they are not officially released by NVIDIA. In my case, it still worked and I therefore share it.
First, remove the installed NVIDIA drivers:
sudo apt-get purge nvidia*
Add the repository for the graphics driver:
sudo add-apt-repository ppa:graphics-drivers/ppa
sudo apt update
Then install the correct version of the drivers (in my case, xxx = 390)
sudo apt install nvidia-xxx
And finally
reboot
The login problem should now be solved. In my case, the CUDA environment did not
get affected and all my project still ran normally.
390.48 is the current 390 driver from the standard repositories, no need for the graphics-drivers ppa. The package name is nvidia-driver-390 (no longer in the form nvidia-xxx).
– ubfan1
Aug 28 '18 at 15:25
@ubfan1 Ah, thanks. So what command should I use to install it the proper way?
– raggot
Aug 29 '18 at 9:57
Clean out any previous nvidia packages and from Software and Updates, check the sources (I think universe is the one needed), and then under the Additional Drivers tab, let it scan and select the one that says "tested", or the latest one if a tested one is not available.
– ubfan1
Aug 29 '18 at 16:41
@ubfan1 Thank you. If you are willing to write an answer with the commands one would need to type I'll be happy to accept it.
– raggot
Aug 30 '18 at 8:49
A search of this site already gives many correct answers to the Nvidia login loop problem, but you can accept your own answer since it worked for you.
– ubfan1
Aug 30 '18 at 15:12
add a comment |
To other people facing my same issue, I suggest trying the following:
mv .Xauthority .Xauthority-backup
which renames .Xauthority
and forces the creation of a new one with the next login attempt. In case the problem laid there, then the login would work.
In my case, however, what actually worked was doing what I was afraid doing, which is reinstalling the NVIDIA drivers. For users of CUDA, the driver version that needs to be installed is defined by the documentation. In my case, as I had CUDA 9.1, it's at least driver version 390.46 (as per the moment I write this answer, of course).
I followed the instructions found on this website to (re)install the drivers I needed. I actually also found this post from the CUDA forum, written by a moderator, explaining how on his experience using this source for the drivers may not always work, as they are not officially released by NVIDIA. In my case, it still worked and I therefore share it.
First, remove the installed NVIDIA drivers:
sudo apt-get purge nvidia*
Add the repository for the graphics driver:
sudo add-apt-repository ppa:graphics-drivers/ppa
sudo apt update
Then install the correct version of the drivers (in my case, xxx = 390)
sudo apt install nvidia-xxx
And finally
reboot
The login problem should now be solved. In my case, the CUDA environment did not
get affected and all my project still ran normally.
390.48 is the current 390 driver from the standard repositories, no need for the graphics-drivers ppa. The package name is nvidia-driver-390 (no longer in the form nvidia-xxx).
– ubfan1
Aug 28 '18 at 15:25
@ubfan1 Ah, thanks. So what command should I use to install it the proper way?
– raggot
Aug 29 '18 at 9:57
Clean out any previous nvidia packages and from Software and Updates, check the sources (I think universe is the one needed), and then under the Additional Drivers tab, let it scan and select the one that says "tested", or the latest one if a tested one is not available.
– ubfan1
Aug 29 '18 at 16:41
@ubfan1 Thank you. If you are willing to write an answer with the commands one would need to type I'll be happy to accept it.
– raggot
Aug 30 '18 at 8:49
A search of this site already gives many correct answers to the Nvidia login loop problem, but you can accept your own answer since it worked for you.
– ubfan1
Aug 30 '18 at 15:12
add a comment |
To other people facing my same issue, I suggest trying the following:
mv .Xauthority .Xauthority-backup
which renames .Xauthority
and forces the creation of a new one with the next login attempt. In case the problem laid there, then the login would work.
In my case, however, what actually worked was doing what I was afraid doing, which is reinstalling the NVIDIA drivers. For users of CUDA, the driver version that needs to be installed is defined by the documentation. In my case, as I had CUDA 9.1, it's at least driver version 390.46 (as per the moment I write this answer, of course).
I followed the instructions found on this website to (re)install the drivers I needed. I actually also found this post from the CUDA forum, written by a moderator, explaining how on his experience using this source for the drivers may not always work, as they are not officially released by NVIDIA. In my case, it still worked and I therefore share it.
First, remove the installed NVIDIA drivers:
sudo apt-get purge nvidia*
Add the repository for the graphics driver:
sudo add-apt-repository ppa:graphics-drivers/ppa
sudo apt update
Then install the correct version of the drivers (in my case, xxx = 390)
sudo apt install nvidia-xxx
And finally
reboot
The login problem should now be solved. In my case, the CUDA environment did not
get affected and all my project still ran normally.
To other people facing my same issue, I suggest trying the following:
mv .Xauthority .Xauthority-backup
which renames .Xauthority
and forces the creation of a new one with the next login attempt. In case the problem laid there, then the login would work.
In my case, however, what actually worked was doing what I was afraid doing, which is reinstalling the NVIDIA drivers. For users of CUDA, the driver version that needs to be installed is defined by the documentation. In my case, as I had CUDA 9.1, it's at least driver version 390.46 (as per the moment I write this answer, of course).
I followed the instructions found on this website to (re)install the drivers I needed. I actually also found this post from the CUDA forum, written by a moderator, explaining how on his experience using this source for the drivers may not always work, as they are not officially released by NVIDIA. In my case, it still worked and I therefore share it.
First, remove the installed NVIDIA drivers:
sudo apt-get purge nvidia*
Add the repository for the graphics driver:
sudo add-apt-repository ppa:graphics-drivers/ppa
sudo apt update
Then install the correct version of the drivers (in my case, xxx = 390)
sudo apt install nvidia-xxx
And finally
reboot
The login problem should now be solved. In my case, the CUDA environment did not
get affected and all my project still ran normally.
edited Apr 5 at 12:38
answered Aug 28 '18 at 15:05
raggotraggot
15118
15118
390.48 is the current 390 driver from the standard repositories, no need for the graphics-drivers ppa. The package name is nvidia-driver-390 (no longer in the form nvidia-xxx).
– ubfan1
Aug 28 '18 at 15:25
@ubfan1 Ah, thanks. So what command should I use to install it the proper way?
– raggot
Aug 29 '18 at 9:57
Clean out any previous nvidia packages and from Software and Updates, check the sources (I think universe is the one needed), and then under the Additional Drivers tab, let it scan and select the one that says "tested", or the latest one if a tested one is not available.
– ubfan1
Aug 29 '18 at 16:41
@ubfan1 Thank you. If you are willing to write an answer with the commands one would need to type I'll be happy to accept it.
– raggot
Aug 30 '18 at 8:49
A search of this site already gives many correct answers to the Nvidia login loop problem, but you can accept your own answer since it worked for you.
– ubfan1
Aug 30 '18 at 15:12
add a comment |
390.48 is the current 390 driver from the standard repositories, no need for the graphics-drivers ppa. The package name is nvidia-driver-390 (no longer in the form nvidia-xxx).
– ubfan1
Aug 28 '18 at 15:25
@ubfan1 Ah, thanks. So what command should I use to install it the proper way?
– raggot
Aug 29 '18 at 9:57
Clean out any previous nvidia packages and from Software and Updates, check the sources (I think universe is the one needed), and then under the Additional Drivers tab, let it scan and select the one that says "tested", or the latest one if a tested one is not available.
– ubfan1
Aug 29 '18 at 16:41
@ubfan1 Thank you. If you are willing to write an answer with the commands one would need to type I'll be happy to accept it.
– raggot
Aug 30 '18 at 8:49
A search of this site already gives many correct answers to the Nvidia login loop problem, but you can accept your own answer since it worked for you.
– ubfan1
Aug 30 '18 at 15:12
390.48 is the current 390 driver from the standard repositories, no need for the graphics-drivers ppa. The package name is nvidia-driver-390 (no longer in the form nvidia-xxx).
– ubfan1
Aug 28 '18 at 15:25
390.48 is the current 390 driver from the standard repositories, no need for the graphics-drivers ppa. The package name is nvidia-driver-390 (no longer in the form nvidia-xxx).
– ubfan1
Aug 28 '18 at 15:25
@ubfan1 Ah, thanks. So what command should I use to install it the proper way?
– raggot
Aug 29 '18 at 9:57
@ubfan1 Ah, thanks. So what command should I use to install it the proper way?
– raggot
Aug 29 '18 at 9:57
Clean out any previous nvidia packages and from Software and Updates, check the sources (I think universe is the one needed), and then under the Additional Drivers tab, let it scan and select the one that says "tested", or the latest one if a tested one is not available.
– ubfan1
Aug 29 '18 at 16:41
Clean out any previous nvidia packages and from Software and Updates, check the sources (I think universe is the one needed), and then under the Additional Drivers tab, let it scan and select the one that says "tested", or the latest one if a tested one is not available.
– ubfan1
Aug 29 '18 at 16:41
@ubfan1 Thank you. If you are willing to write an answer with the commands one would need to type I'll be happy to accept it.
– raggot
Aug 30 '18 at 8:49
@ubfan1 Thank you. If you are willing to write an answer with the commands one would need to type I'll be happy to accept it.
– raggot
Aug 30 '18 at 8:49
A search of this site already gives many correct answers to the Nvidia login loop problem, but you can accept your own answer since it worked for you.
– ubfan1
Aug 30 '18 at 15:12
A search of this site already gives many correct answers to the Nvidia login loop problem, but you can accept your own answer since it worked for you.
– ubfan1
Aug 30 '18 at 15:12
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%2f1069116%2flogin-loop-likely-due-to-nvidia-drivers-with-cuda-installed%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