XPS 9370 Upgrade from 17.10 to 18.04 not recognizing intel HD card
I did an upgrade via terminal yesterday, everything seemed to work fine but then I noticed very heavy CPU usage by gnome-shell. The problem is that the UHD card is not fully recognized, so it uses instead llvmpipe, so no native 3D acceleration :-( This was working great in 17.10
Some outputs which might be useful:
sudo lspci -nnk | grep -i vga -A3
00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07)
Subsystem: Dell UHD Graphics 620 [1028:07e6]
Kernel driver in use: i915
Kernel modules: i915
glxinfo | grep llv
Device: llvmpipe (LLVM 6.0, 256 bits) (0xffffffff)
OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits)
Pls let me know if providing more info would help. I am not sure if the driver is missing or if XORG is broken, please help. I am using XORG at the moment, Wayland freezes (it was working in 17.10).
Thanks!
upgrade intel-graphics 18.04
asked May 2 '18 at 9:19
user2003706
1
add a comment |
I did an upgrade via terminal yesterday, everything seemed to work fine but then I noticed very heavy CPU usage by gnome-shell. The problem is that the UHD card is not fully recognized, so it uses instead llvmpipe, so no native 3D acceleration :-( This was working great in 17.10
Some outputs which might be useful:
sudo lspci -nnk | grep -i vga -A3
00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07)
Subsystem: Dell UHD Graphics 620 [1028:07e6]
Kernel driver in use: i915
Kernel modules: i915
glxinfo | grep llv
Device: llvmpipe (LLVM 6.0, 256 bits) (0xffffffff)
OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits)
Pls let me know if providing more info would help. I am not sure if the driver is missing or if XORG is broken, please help. I am using XORG at the moment, Wayland freezes (it was working in 17.10).
Thanks!
upgrade intel-graphics 18.04
asked May 2 '18 at 9:19
user2003706
1
I found the solution at askubuntu.com/questions/908381/… Basically, type systemctl --user unset-environment LIBGL_ALWAYS_SOFTWARE and reboot, then glxinfo and system settings report the correct UHD renderer is being used ;-) The problem seems to be that at somepoint gui crashed and then the system set this variable to avoid using native 3D acceleration.
– user2003706
May 3 '18 at 8:42
add a comment |
I did an upgrade via terminal yesterday, everything seemed to work fine but then I noticed very heavy CPU usage by gnome-shell. The problem is that the UHD card is not fully recognized, so it uses instead llvmpipe, so no native 3D acceleration :-( This was working great in 17.10
Some outputs which might be useful:
sudo lspci -nnk | grep -i vga -A3
00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07)
Subsystem: Dell UHD Graphics 620 [1028:07e6]
Kernel driver in use: i915
Kernel modules: i915
glxinfo | grep llv
Device: llvmpipe (LLVM 6.0, 256 bits) (0xffffffff)
OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits)
Pls let me know if providing more info would help. I am not sure if the driver is missing or if XORG is broken, please help. I am using XORG at the moment, Wayland freezes (it was working in 17.10).
Thanks!
upgrade intel-graphics 18.04
asked May 2 '18 at 9:19
user2003706
1
I did an upgrade via terminal yesterday, everything seemed to work fine but then I noticed very heavy CPU usage by gnome-shell. The problem is that the UHD card is not fully recognized, so it uses instead llvmpipe, so no native 3D acceleration :-( This was working great in 17.10
Some outputs which might be useful:
sudo lspci -nnk | grep -i vga -A3
00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07)
Subsystem: Dell UHD Graphics 620 [1028:07e6]
Kernel driver in use: i915
Kernel modules: i915
glxinfo | grep llv
Device: llvmpipe (LLVM 6.0, 256 bits) (0xffffffff)
OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits)
Pls let me know if providing more info would help. I am not sure if the driver is missing or if XORG is broken, please help. I am using XORG at the moment, Wayland freezes (it was working in 17.10).
Thanks!
upgrade intel-graphics 18.04
upgrade intel-graphics 18.04
asked May 2 '18 at 9:19
user2003706
1
asked May 2 '18 at 9:19
user2003706
1
asked May 2 '18 at 9:19
user2003706
1
asked May 2 '18 at 9:19
user2003706
1
asked May 2 '18 at 9:19
user2003706
1
1
I found the solution at askubuntu.com/questions/908381/… Basically, type systemctl --user unset-environment LIBGL_ALWAYS_SOFTWARE and reboot, then glxinfo and system settings report the correct UHD renderer is being used ;-) The problem seems to be that at somepoint gui crashed and then the system set this variable to avoid using native 3D acceleration.
– user2003706
May 3 '18 at 8:42
add a comment |
I found the solution at askubuntu.com/questions/908381/… Basically, type systemctl --user unset-environment LIBGL_ALWAYS_SOFTWARE and reboot, then glxinfo and system settings report the correct UHD renderer is being used ;-) The problem seems to be that at somepoint gui crashed and then the system set this variable to avoid using native 3D acceleration.
– user2003706
May 3 '18 at 8:42
I found the solution at askubuntu.com/questions/908381/… Basically, type systemctl --user unset-environment LIBGL_ALWAYS_SOFTWARE and reboot, then glxinfo and system settings report the correct UHD renderer is being used ;-) The problem seems to be that at somepoint gui crashed and then the system set this variable to avoid using native 3D acceleration.
– user2003706
May 3 '18 at 8:42
I found the solution at askubuntu.com/questions/908381/… Basically, type systemctl --user unset-environment LIBGL_ALWAYS_SOFTWARE and reboot, then glxinfo and system settings report the correct UHD renderer is being used ;-) The problem seems to be that at somepoint gui crashed and then the system set this variable to avoid using native 3D acceleration.
– user2003706
May 3 '18 at 8:42
add a comment |
1 Answer
1
active
oldest
votes
For me helped setting i915.alpha_support=1. Try using instuction below:
- Run
sudo nano /etc/default/grub(you may use whatever editor instead ofnano) - Add
i915.alpha_support=1to the existing lineGRUB_CMDLINE_LINUX_DEFAULT=afterquiet splash. - Run
sudo update-grub
- Reboot
P.S. My backgound with this problem:
Initially I had a blackscreen after splash, so I had to add nomodeset (afterwards replaced to i915.modeset=0). Doing this I could boot the desktop, but it was rendered by LLVMpipe (software rendering using CPU capabilities).
answered Dec 16 '18 at 8:52
Shurov
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%2f1030993%2fxps-9370-upgrade-from-17-10-to-18-04-not-recognizing-intel-hd-card%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
For me helped setting i915.alpha_support=1. Try using instuction below:
- Run
sudo nano /etc/default/grub(you may use whatever editor instead ofnano) - Add
i915.alpha_support=1to the existing lineGRUB_CMDLINE_LINUX_DEFAULT=afterquiet splash. - Run
sudo update-grub
- Reboot
P.S. My backgound with this problem:
Initially I had a blackscreen after splash, so I had to add nomodeset (afterwards replaced to i915.modeset=0). Doing this I could boot the desktop, but it was rendered by LLVMpipe (software rendering using CPU capabilities).
answered Dec 16 '18 at 8:52
Shurov
12
add a comment |
For me helped setting i915.alpha_support=1. Try using instuction below:
- Run
sudo nano /etc/default/grub(you may use whatever editor instead ofnano) - Add
i915.alpha_support=1to the existing lineGRUB_CMDLINE_LINUX_DEFAULT=afterquiet splash. - Run
sudo update-grub
- Reboot
P.S. My backgound with this problem:
Initially I had a blackscreen after splash, so I had to add nomodeset (afterwards replaced to i915.modeset=0). Doing this I could boot the desktop, but it was rendered by LLVMpipe (software rendering using CPU capabilities).
answered Dec 16 '18 at 8:52
Shurov
12
add a comment |
For me helped setting i915.alpha_support=1. Try using instuction below:
- Run
sudo nano /etc/default/grub(you may use whatever editor instead ofnano) - Add
i915.alpha_support=1to the existing lineGRUB_CMDLINE_LINUX_DEFAULT=afterquiet splash. - Run
sudo update-grub
- Reboot
P.S. My backgound with this problem:
Initially I had a blackscreen after splash, so I had to add nomodeset (afterwards replaced to i915.modeset=0). Doing this I could boot the desktop, but it was rendered by LLVMpipe (software rendering using CPU capabilities).
answered Dec 16 '18 at 8:52
Shurov
12
For me helped setting i915.alpha_support=1. Try using instuction below:
- Run
sudo nano /etc/default/grub(you may use whatever editor instead ofnano) - Add
i915.alpha_support=1to the existing lineGRUB_CMDLINE_LINUX_DEFAULT=afterquiet splash. - Run
sudo update-grub
- Reboot
P.S. My backgound with this problem:
Initially I had a blackscreen after splash, so I had to add nomodeset (afterwards replaced to i915.modeset=0). Doing this I could boot the desktop, but it was rendered by LLVMpipe (software rendering using CPU capabilities).
answered Dec 16 '18 at 8:52
Shurov
12
answered Dec 16 '18 at 8:52
Shurov
12
answered Dec 16 '18 at 8:52
Shurov
12
answered Dec 16 '18 at 8:52
Shurov
12
12
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f1030993%2fxps-9370-upgrade-from-17-10-to-18-04-not-recognizing-intel-hd-card%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
I found the solution at askubuntu.com/questions/908381/… Basically, type systemctl --user unset-environment LIBGL_ALWAYS_SOFTWARE and reboot, then glxinfo and system settings report the correct UHD renderer is being used ;-) The problem seems to be that at somepoint gui crashed and then the system set this variable to avoid using native 3D acceleration.
– user2003706
May 3 '18 at 8:42