Ubuntu 18.04 EGPU not work
Clash Royale CLAN TAG#URR8PPP up vote
2
down vote
favorite
I have a HP Spectre (intel i7 6500 U). I have been using 16.04, and installed 18.04 recently. I don't travel much, so I use EGPU to gain more GPU power all the time. I have a razer core at home and an Omen Accelerator in my office; and I have a GTX 970 and a GTX 1080ti. With 16.04, everything is working smoothly: I connect the GPU dock to the laptop via the thunderbolt 3 connector and use the prime-select tool to select NVIDIA. Even CUDA is working fine.
However, with 18.04, things have been difficult. Firstly, when I used nouveau, the desktop simply froze after I logged in.
Secondly, I installed the NVIDIAï¼Â390 driver directly through the Bionic repo. The installation seemed fine, and did not report any error. However, when I connected the GPU dock to the laptop, the error PKCS#7 appeared continuously.
I could logged in via xorg, but the nouveau was loaded insteaf of NVIDIA. Moreovoer, nvidia-smi showed that the driver was not loaded. Finally, I installed NVIDIA-390 via the run file. This time nvidia-smi showed that the driver was loaded correctly, but I had the login loop for the xorg. S
trangely, most people don't see the wayland option when they have installed NVIDIA driver, but I can see both the wayland and xorg options in all circumstances. I have
So in summary, Nouveau makes my laptop with EGPU freeze; installation of nvidia-390 from the bionic repo does not load the driver properly; the installation of nvidia-390 through the run file seems alright but gives me the login loop.
Other than my laptop, I have a desktop with an NVIDIA 970, which works very smoothly under 18.04, including EGPU and cuda.
Any suggestion is deeply appreciated.
nvidia 18.04 nvidia-prime thunderbolt
edited May 15 at 0:57
stumblebee
2,3083922
asked May 14 at 20:37
Xdedm Meng
314
add a comment |Â
up vote
2
down vote
favorite
I have a HP Spectre (intel i7 6500 U). I have been using 16.04, and installed 18.04 recently. I don't travel much, so I use EGPU to gain more GPU power all the time. I have a razer core at home and an Omen Accelerator in my office; and I have a GTX 970 and a GTX 1080ti. With 16.04, everything is working smoothly: I connect the GPU dock to the laptop via the thunderbolt 3 connector and use the prime-select tool to select NVIDIA. Even CUDA is working fine.
However, with 18.04, things have been difficult. Firstly, when I used nouveau, the desktop simply froze after I logged in.
Secondly, I installed the NVIDIAï¼Â390 driver directly through the Bionic repo. The installation seemed fine, and did not report any error. However, when I connected the GPU dock to the laptop, the error PKCS#7 appeared continuously.
I could logged in via xorg, but the nouveau was loaded insteaf of NVIDIA. Moreovoer, nvidia-smi showed that the driver was not loaded. Finally, I installed NVIDIA-390 via the run file. This time nvidia-smi showed that the driver was loaded correctly, but I had the login loop for the xorg. S
trangely, most people don't see the wayland option when they have installed NVIDIA driver, but I can see both the wayland and xorg options in all circumstances. I have
So in summary, Nouveau makes my laptop with EGPU freeze; installation of nvidia-390 from the bionic repo does not load the driver properly; the installation of nvidia-390 through the run file seems alright but gives me the login loop.
Other than my laptop, I have a desktop with an NVIDIA 970, which works very smoothly under 18.04, including EGPU and cuda.
Any suggestion is deeply appreciated.
nvidia 18.04 nvidia-prime thunderbolt
edited May 15 at 0:57
stumblebee
2,3083922
asked May 14 at 20:37
Xdedm Meng
314
Did you check that secure boot is off?
– ubfan1
May 15 at 1:16
Thank you for you reply. But secure boot is off. Everything is fine with 16.04, and the installation for 18.04 is not complaining.
– Xdedm Meng
May 15 at 7:51
add a comment |Â
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I have a HP Spectre (intel i7 6500 U). I have been using 16.04, and installed 18.04 recently. I don't travel much, so I use EGPU to gain more GPU power all the time. I have a razer core at home and an Omen Accelerator in my office; and I have a GTX 970 and a GTX 1080ti. With 16.04, everything is working smoothly: I connect the GPU dock to the laptop via the thunderbolt 3 connector and use the prime-select tool to select NVIDIA. Even CUDA is working fine.
However, with 18.04, things have been difficult. Firstly, when I used nouveau, the desktop simply froze after I logged in.
Secondly, I installed the NVIDIAï¼Â390 driver directly through the Bionic repo. The installation seemed fine, and did not report any error. However, when I connected the GPU dock to the laptop, the error PKCS#7 appeared continuously.
I could logged in via xorg, but the nouveau was loaded insteaf of NVIDIA. Moreovoer, nvidia-smi showed that the driver was not loaded. Finally, I installed NVIDIA-390 via the run file. This time nvidia-smi showed that the driver was loaded correctly, but I had the login loop for the xorg. S
trangely, most people don't see the wayland option when they have installed NVIDIA driver, but I can see both the wayland and xorg options in all circumstances. I have
So in summary, Nouveau makes my laptop with EGPU freeze; installation of nvidia-390 from the bionic repo does not load the driver properly; the installation of nvidia-390 through the run file seems alright but gives me the login loop.
Other than my laptop, I have a desktop with an NVIDIA 970, which works very smoothly under 18.04, including EGPU and cuda.
Any suggestion is deeply appreciated.
nvidia 18.04 nvidia-prime thunderbolt
edited May 15 at 0:57
stumblebee
2,3083922
asked May 14 at 20:37
Xdedm Meng
314
I have a HP Spectre (intel i7 6500 U). I have been using 16.04, and installed 18.04 recently. I don't travel much, so I use EGPU to gain more GPU power all the time. I have a razer core at home and an Omen Accelerator in my office; and I have a GTX 970 and a GTX 1080ti. With 16.04, everything is working smoothly: I connect the GPU dock to the laptop via the thunderbolt 3 connector and use the prime-select tool to select NVIDIA. Even CUDA is working fine.
However, with 18.04, things have been difficult. Firstly, when I used nouveau, the desktop simply froze after I logged in.
Secondly, I installed the NVIDIAï¼Â390 driver directly through the Bionic repo. The installation seemed fine, and did not report any error. However, when I connected the GPU dock to the laptop, the error PKCS#7 appeared continuously.
I could logged in via xorg, but the nouveau was loaded insteaf of NVIDIA. Moreovoer, nvidia-smi showed that the driver was not loaded. Finally, I installed NVIDIA-390 via the run file. This time nvidia-smi showed that the driver was loaded correctly, but I had the login loop for the xorg. S
trangely, most people don't see the wayland option when they have installed NVIDIA driver, but I can see both the wayland and xorg options in all circumstances. I have
So in summary, Nouveau makes my laptop with EGPU freeze; installation of nvidia-390 from the bionic repo does not load the driver properly; the installation of nvidia-390 through the run file seems alright but gives me the login loop.
Other than my laptop, I have a desktop with an NVIDIA 970, which works very smoothly under 18.04, including EGPU and cuda.
Any suggestion is deeply appreciated.
nvidia 18.04 nvidia-prime thunderbolt
edited May 15 at 0:57
stumblebee
2,3083922
asked May 14 at 20:37
Xdedm Meng
314
edited May 15 at 0:57
stumblebee
2,3083922
edited May 15 at 0:57
stumblebee
2,3083922
edited May 15 at 0:57
stumblebee
2,3083922
2,3083922
asked May 14 at 20:37
Xdedm Meng
314
asked May 14 at 20:37
Xdedm Meng
314
asked May 14 at 20:37
Xdedm Meng
314
314
Did you check that secure boot is off?
– ubfan1
May 15 at 1:16
Thank you for you reply. But secure boot is off. Everything is fine with 16.04, and the installation for 18.04 is not complaining.
– Xdedm Meng
May 15 at 7:51
add a comment |Â
Did you check that secure boot is off?
– ubfan1
May 15 at 1:16
Thank you for you reply. But secure boot is off. Everything is fine with 16.04, and the installation for 18.04 is not complaining.
– Xdedm Meng
May 15 at 7:51
Did you check that secure boot is off?
– ubfan1
May 15 at 1:16
Did you check that secure boot is off?
– ubfan1
May 15 at 1:16
Thank you for you reply. But secure boot is off. Everything is fine with 16.04, and the installation for 18.04 is not complaining.
– Xdedm Meng
May 15 at 7:51
Thank you for you reply. But secure boot is off. Everything is fine with 16.04, and the installation for 18.04 is not complaining.
– Xdedm Meng
May 15 at 7:51
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
Problem solved. I hope it will be useful for people having an Intel+Nvidia Egpu system like mine. Firstly, installation of nvidia 390 from the bionic repo doesn't work for me. Possibly the DKMS is not written correctly. When I use run file, things work, and I can use nvidia-smi to see my nvidia card information. Secondly, Nvidia seems unable to create the correct xorg.conf file in this situation, which results in the login loop. I copied the xorg file from my 16.04 partition and pasted it into /etc/X11/, then everything works. Perhaps the system loads the wrong xorg file Nvidia created, so that the system simply refuses to log in.
It is a bit painful, as the xorg file has to be manually adapted if you connect the computer to a different EGPU dock or if the laptop is running without the EGPU dock. I simply use the wayland session when the EGPU dock is not used.
answered May 17 at 9:47
Xdedm Meng
314
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
Problem solved. I hope it will be useful for people having an Intel+Nvidia Egpu system like mine. Firstly, installation of nvidia 390 from the bionic repo doesn't work for me. Possibly the DKMS is not written correctly. When I use run file, things work, and I can use nvidia-smi to see my nvidia card information. Secondly, Nvidia seems unable to create the correct xorg.conf file in this situation, which results in the login loop. I copied the xorg file from my 16.04 partition and pasted it into /etc/X11/, then everything works. Perhaps the system loads the wrong xorg file Nvidia created, so that the system simply refuses to log in.
It is a bit painful, as the xorg file has to be manually adapted if you connect the computer to a different EGPU dock or if the laptop is running without the EGPU dock. I simply use the wayland session when the EGPU dock is not used.
answered May 17 at 9:47
Xdedm Meng
314
add a comment |Â
up vote
2
down vote
accepted
Problem solved. I hope it will be useful for people having an Intel+Nvidia Egpu system like mine. Firstly, installation of nvidia 390 from the bionic repo doesn't work for me. Possibly the DKMS is not written correctly. When I use run file, things work, and I can use nvidia-smi to see my nvidia card information. Secondly, Nvidia seems unable to create the correct xorg.conf file in this situation, which results in the login loop. I copied the xorg file from my 16.04 partition and pasted it into /etc/X11/, then everything works. Perhaps the system loads the wrong xorg file Nvidia created, so that the system simply refuses to log in.
It is a bit painful, as the xorg file has to be manually adapted if you connect the computer to a different EGPU dock or if the laptop is running without the EGPU dock. I simply use the wayland session when the EGPU dock is not used.
answered May 17 at 9:47
Xdedm Meng
314
add a comment |Â
up vote
2
down vote
accepted
up vote
2
down vote
accepted
Problem solved. I hope it will be useful for people having an Intel+Nvidia Egpu system like mine. Firstly, installation of nvidia 390 from the bionic repo doesn't work for me. Possibly the DKMS is not written correctly. When I use run file, things work, and I can use nvidia-smi to see my nvidia card information. Secondly, Nvidia seems unable to create the correct xorg.conf file in this situation, which results in the login loop. I copied the xorg file from my 16.04 partition and pasted it into /etc/X11/, then everything works. Perhaps the system loads the wrong xorg file Nvidia created, so that the system simply refuses to log in.
It is a bit painful, as the xorg file has to be manually adapted if you connect the computer to a different EGPU dock or if the laptop is running without the EGPU dock. I simply use the wayland session when the EGPU dock is not used.
answered May 17 at 9:47
Xdedm Meng
314
Problem solved. I hope it will be useful for people having an Intel+Nvidia Egpu system like mine. Firstly, installation of nvidia 390 from the bionic repo doesn't work for me. Possibly the DKMS is not written correctly. When I use run file, things work, and I can use nvidia-smi to see my nvidia card information. Secondly, Nvidia seems unable to create the correct xorg.conf file in this situation, which results in the login loop. I copied the xorg file from my 16.04 partition and pasted it into /etc/X11/, then everything works. Perhaps the system loads the wrong xorg file Nvidia created, so that the system simply refuses to log in.
It is a bit painful, as the xorg file has to be manually adapted if you connect the computer to a different EGPU dock or if the laptop is running without the EGPU dock. I simply use the wayland session when the EGPU dock is not used.
answered May 17 at 9:47
Xdedm Meng
314
edited May 17 at 10:07
answered May 17 at 9:47
Xdedm Meng
314
answered May 17 at 9:47
Xdedm Meng
314
answered May 17 at 9:47
Xdedm Meng
314
314
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%2f1036271%2fubuntu-18-04-egpu-not-work%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
Did you check that secure boot is off?
– ubfan1
May 15 at 1:16
Thank you for you reply. But secure boot is off. Everything is fine with 16.04, and the installation for 18.04 is not complaining.
– Xdedm Meng
May 15 at 7:51