Ubuntu 18.04: nvidia PRIME issue - prime-select intel does not work
I have a strange problem while using nvidia-prime comand. When I change the command prime-select like this
prime-select intel
and reboot the system, my laptop will display something like this and will result with endless loop with displaying information on screenshot below:
How to solve this problem?
nvidia 18.04 intel nvidia-prime
edited May 29 '18 at 20:48
velix
3011213
asked May 29 '18 at 17:41
moerotormoerotor
111
bumped to the homepage by Community♦ 5 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
|
show 1 more comment
I have a strange problem while using nvidia-prime comand. When I change the command prime-select like this
prime-select intel
and reboot the system, my laptop will display something like this and will result with endless loop with displaying information on screenshot below:
How to solve this problem?
nvidia 18.04 intel nvidia-prime
edited May 29 '18 at 20:48
velix
3011213
asked May 29 '18 at 17:41
moerotormoerotor
111
bumped to the homepage by Community♦ 5 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
a quick workaround if You are in a hurry to use ubuntu for work...alt+f2 to get into tty, login there and type sudo prime-select nvidia, after reboot You may further search for solutions with intel, good luck
– PawełG
May 29 '18 at 18:10
Unfortunately, with that error, you can't access any tty. You should reboot in rescue mode from GRUB, enter in the shell as root and runprime-select nvidia. Then follow my answer. I'm quite sure is the same exact problem.
– velix
May 29 '18 at 18:34
Hi, I did that with running ubuntu via recovery mode and then dpkg. I'm wondering how to make nvidia-prime packet to work correctly.
– moerotor
May 29 '18 at 21:02
If you're running in Xorg, it should be working.
– velix
May 29 '18 at 21:15
I mean I changed that parameter to prime-select nvidia and it works, but the point is I want to use my integrated intel card.
– moerotor
May 30 '18 at 18:29
|
show 1 more comment
I have a strange problem while using nvidia-prime comand. When I change the command prime-select like this
prime-select intel
and reboot the system, my laptop will display something like this and will result with endless loop with displaying information on screenshot below:
How to solve this problem?
nvidia 18.04 intel nvidia-prime
edited May 29 '18 at 20:48
velix
3011213
asked May 29 '18 at 17:41
moerotormoerotor
111
I have a strange problem while using nvidia-prime comand. When I change the command prime-select like this
prime-select intel
and reboot the system, my laptop will display something like this and will result with endless loop with displaying information on screenshot below:
How to solve this problem?
nvidia 18.04 intel nvidia-prime
nvidia 18.04 intel nvidia-prime
edited May 29 '18 at 20:48
velix
3011213
asked May 29 '18 at 17:41
moerotormoerotor
111
edited May 29 '18 at 20:48
velix
3011213
asked May 29 '18 at 17:41
moerotormoerotor
111
edited May 29 '18 at 20:48
velix
3011213
edited May 29 '18 at 20:48
velix
3011213
edited May 29 '18 at 20:48
velix
3011213
3011213
asked May 29 '18 at 17:41
moerotormoerotor
111
asked May 29 '18 at 17:41
moerotormoerotor
111
asked May 29 '18 at 17:41
moerotormoerotor
111
111
bumped to the homepage by Community♦ 5 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 5 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
a quick workaround if You are in a hurry to use ubuntu for work...alt+f2 to get into tty, login there and type sudo prime-select nvidia, after reboot You may further search for solutions with intel, good luck
– PawełG
May 29 '18 at 18:10
Unfortunately, with that error, you can't access any tty. You should reboot in rescue mode from GRUB, enter in the shell as root and runprime-select nvidia. Then follow my answer. I'm quite sure is the same exact problem.
– velix
May 29 '18 at 18:34
Hi, I did that with running ubuntu via recovery mode and then dpkg. I'm wondering how to make nvidia-prime packet to work correctly.
– moerotor
May 29 '18 at 21:02
If you're running in Xorg, it should be working.
– velix
May 29 '18 at 21:15
I mean I changed that parameter to prime-select nvidia and it works, but the point is I want to use my integrated intel card.
– moerotor
May 30 '18 at 18:29
|
show 1 more comment
a quick workaround if You are in a hurry to use ubuntu for work...alt+f2 to get into tty, login there and type sudo prime-select nvidia, after reboot You may further search for solutions with intel, good luck
– PawełG
May 29 '18 at 18:10
Unfortunately, with that error, you can't access any tty. You should reboot in rescue mode from GRUB, enter in the shell as root and runprime-select nvidia. Then follow my answer. I'm quite sure is the same exact problem.
– velix
May 29 '18 at 18:34
Hi, I did that with running ubuntu via recovery mode and then dpkg. I'm wondering how to make nvidia-prime packet to work correctly.
– moerotor
May 29 '18 at 21:02
If you're running in Xorg, it should be working.
– velix
May 29 '18 at 21:15
I mean I changed that parameter to prime-select nvidia and it works, but the point is I want to use my integrated intel card.
– moerotor
May 30 '18 at 18:29
a quick workaround if You are in a hurry to use ubuntu for work...alt+f2 to get into tty, login there and type sudo prime-select nvidia, after reboot You may further search for solutions with intel, good luck
– PawełG
May 29 '18 at 18:10
a quick workaround if You are in a hurry to use ubuntu for work...alt+f2 to get into tty, login there and type sudo prime-select nvidia, after reboot You may further search for solutions with intel, good luck
– PawełG
May 29 '18 at 18:10
Unfortunately, with that error, you can't access any tty. You should reboot in rescue mode from GRUB, enter in the shell as root and run
prime-select nvidia. Then follow my answer. I'm quite sure is the same exact problem.– velix
May 29 '18 at 18:34
Unfortunately, with that error, you can't access any tty. You should reboot in rescue mode from GRUB, enter in the shell as root and run
prime-select nvidia. Then follow my answer. I'm quite sure is the same exact problem.– velix
May 29 '18 at 18:34
Hi, I did that with running ubuntu via recovery mode and then dpkg. I'm wondering how to make nvidia-prime packet to work correctly.
– moerotor
May 29 '18 at 21:02
Hi, I did that with running ubuntu via recovery mode and then dpkg. I'm wondering how to make nvidia-prime packet to work correctly.
– moerotor
May 29 '18 at 21:02
If you're running in Xorg, it should be working.
– velix
May 29 '18 at 21:15
If you're running in Xorg, it should be working.
– velix
May 29 '18 at 21:15
I mean I changed that parameter to prime-select nvidia and it works, but the point is I want to use my integrated intel card.
– moerotor
May 30 '18 at 18:29
I mean I changed that parameter to prime-select nvidia and it works, but the point is I want to use my integrated intel card.
– moerotor
May 30 '18 at 18:29
|
show 1 more comment
1 Answer
1
active
oldest
votes
Got my same problem. You should switch to Xorg. I think is a 18.04 Wayland bug.
My gdm3 session was running in wayland. To check it:
$ loginctl
SESSION UID USER SEAT TTY
2 1000 velix seat0 tty2
c2 1000 velix
c1 120 gdm seat0 tty1
The command loginctl show-session <session-n> -p Type show the session type:
$ loginctl show-session c1 -p Type
Type=Wayland
To change it, edit the file /etc/gdm3/custom.conf and uncomment the line WaylandEnable=false.
After rebooting:
$ loginctl show-session c1 -p Type
Type=x11
See My question and answer for a little more details.
answered May 29 '18 at 17:47
velixvelix
3011213
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%2f1041661%2fubuntu-18-04-nvidia-prime-issue-prime-select-intel-does-not-work%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Got my same problem. You should switch to Xorg. I think is a 18.04 Wayland bug.
My gdm3 session was running in wayland. To check it:
$ loginctl
SESSION UID USER SEAT TTY
2 1000 velix seat0 tty2
c2 1000 velix
c1 120 gdm seat0 tty1
The command loginctl show-session <session-n> -p Type show the session type:
$ loginctl show-session c1 -p Type
Type=Wayland
To change it, edit the file /etc/gdm3/custom.conf and uncomment the line WaylandEnable=false.
After rebooting:
$ loginctl show-session c1 -p Type
Type=x11
See My question and answer for a little more details.
answered May 29 '18 at 17:47
velixvelix
3011213
add a comment |
Got my same problem. You should switch to Xorg. I think is a 18.04 Wayland bug.
My gdm3 session was running in wayland. To check it:
$ loginctl
SESSION UID USER SEAT TTY
2 1000 velix seat0 tty2
c2 1000 velix
c1 120 gdm seat0 tty1
The command loginctl show-session <session-n> -p Type show the session type:
$ loginctl show-session c1 -p Type
Type=Wayland
To change it, edit the file /etc/gdm3/custom.conf and uncomment the line WaylandEnable=false.
After rebooting:
$ loginctl show-session c1 -p Type
Type=x11
See My question and answer for a little more details.
answered May 29 '18 at 17:47
velixvelix
3011213
add a comment |
Got my same problem. You should switch to Xorg. I think is a 18.04 Wayland bug.
My gdm3 session was running in wayland. To check it:
$ loginctl
SESSION UID USER SEAT TTY
2 1000 velix seat0 tty2
c2 1000 velix
c1 120 gdm seat0 tty1
The command loginctl show-session <session-n> -p Type show the session type:
$ loginctl show-session c1 -p Type
Type=Wayland
To change it, edit the file /etc/gdm3/custom.conf and uncomment the line WaylandEnable=false.
After rebooting:
$ loginctl show-session c1 -p Type
Type=x11
See My question and answer for a little more details.
answered May 29 '18 at 17:47
velixvelix
3011213
Got my same problem. You should switch to Xorg. I think is a 18.04 Wayland bug.
My gdm3 session was running in wayland. To check it:
$ loginctl
SESSION UID USER SEAT TTY
2 1000 velix seat0 tty2
c2 1000 velix
c1 120 gdm seat0 tty1
The command loginctl show-session <session-n> -p Type show the session type:
$ loginctl show-session c1 -p Type
Type=Wayland
To change it, edit the file /etc/gdm3/custom.conf and uncomment the line WaylandEnable=false.
After rebooting:
$ loginctl show-session c1 -p Type
Type=x11
See My question and answer for a little more details.
answered May 29 '18 at 17:47
velixvelix
3011213
edited May 29 '18 at 17:55
answered May 29 '18 at 17:47
velixvelix
3011213
answered May 29 '18 at 17:47
velixvelix
3011213
answered May 29 '18 at 17:47
velixvelix
3011213
3011213
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%2f1041661%2fubuntu-18-04-nvidia-prime-issue-prime-select-intel-does-not-work%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
a quick workaround if You are in a hurry to use ubuntu for work...alt+f2 to get into tty, login there and type sudo prime-select nvidia, after reboot You may further search for solutions with intel, good luck
– PawełG
May 29 '18 at 18:10
Unfortunately, with that error, you can't access any tty. You should reboot in rescue mode from GRUB, enter in the shell as root and run
prime-select nvidia. Then follow my answer. I'm quite sure is the same exact problem.– velix
May 29 '18 at 18:34
Hi, I did that with running ubuntu via recovery mode and then dpkg. I'm wondering how to make nvidia-prime packet to work correctly.
– moerotor
May 29 '18 at 21:02
If you're running in Xorg, it should be working.
– velix
May 29 '18 at 21:15
I mean I changed that parameter to prime-select nvidia and it works, but the point is I want to use my integrated intel card.
– moerotor
May 30 '18 at 18:29