Galium 0.4 on llvmpipe
I'm totally desperate. I'm trying to install open source video drivers for my R9 270x, but no matter what I do when I run
glxinfo | grep OpenGL
it shows
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.6, 128 bits)
OpenGL version string: 3.0 Mesa 11.0.2
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
I've been googling this problem for about 2 days already, read all posts related. Nothing works, nothing helps.
What I did:
added this ppa
ppa:oibaf/graphics-drivers
And this one
ppa:paulo-miguel-dias/mesa
Then
apt-get update
I looked into xorg.0.log file and found the following:
[ 45.977] (EE) Unable to initialize PCS database
[ 45.977] (EE) Missing PCS defaults file /etc/ati/amdpcsdb.default
[ 45.978] (II) [KMS] drm report modesetting isn't supported.
[ 45.978] (EE) open /dev/dri/card0: No such file or directory
[ 45.978] (WW) Falling back to old probe method for modesetting
[ 45.978] (EE) open /dev/dri/card0: No such file or directory
[ 45.978] (II) Loading sub module "fbdevhw"
[ 45.978] (II) LoadModule: "fbdevhw"
[ 45.978] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 45.989] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 45.989] compiled for 1.17.2, module version = 0.0.2
[ 45.989] ABI class: X.Org Video Driver, version 19.0
[ 45.989] (**) FBDEV(2): claimed PCI slot 1@0:0:0
[ 45.989] (II) FBDEV(2): using default device
[ 45.989] (WW) Falling back to old probe method for vesa
[ 45.989] (EE) Screen 0 deleted because of no matching config section.
[ 45.989] (II) UnloadModule: "radeon"
[ 45.989] (EE) Screen 0 deleted because of no matching config section.
45.994] (II) AIGLX: Screen 0 is not DRI2 capable
[ 45.994] (EE) AIGLX: reverting to software rendering
Still nothing. When I first installed Ubuntu 15.10 I managed to install this driver correctly and was using it till I decided to try Crimson AMD Driver yesterday (what a big mistake). I didn't like Crimson driver, so I completely uninstalled it. So now I have software rendering and not able to play games anymore, no solution from the web works.
drivers graphics ati opengl
bumped to the homepage by Community♦ 10 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I'm totally desperate. I'm trying to install open source video drivers for my R9 270x, but no matter what I do when I run
glxinfo | grep OpenGL
it shows
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.6, 128 bits)
OpenGL version string: 3.0 Mesa 11.0.2
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
I've been googling this problem for about 2 days already, read all posts related. Nothing works, nothing helps.
What I did:
added this ppa
ppa:oibaf/graphics-drivers
And this one
ppa:paulo-miguel-dias/mesa
Then
apt-get update
I looked into xorg.0.log file and found the following:
[ 45.977] (EE) Unable to initialize PCS database
[ 45.977] (EE) Missing PCS defaults file /etc/ati/amdpcsdb.default
[ 45.978] (II) [KMS] drm report modesetting isn't supported.
[ 45.978] (EE) open /dev/dri/card0: No such file or directory
[ 45.978] (WW) Falling back to old probe method for modesetting
[ 45.978] (EE) open /dev/dri/card0: No such file or directory
[ 45.978] (II) Loading sub module "fbdevhw"
[ 45.978] (II) LoadModule: "fbdevhw"
[ 45.978] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 45.989] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 45.989] compiled for 1.17.2, module version = 0.0.2
[ 45.989] ABI class: X.Org Video Driver, version 19.0
[ 45.989] (**) FBDEV(2): claimed PCI slot 1@0:0:0
[ 45.989] (II) FBDEV(2): using default device
[ 45.989] (WW) Falling back to old probe method for vesa
[ 45.989] (EE) Screen 0 deleted because of no matching config section.
[ 45.989] (II) UnloadModule: "radeon"
[ 45.989] (EE) Screen 0 deleted because of no matching config section.
45.994] (II) AIGLX: Screen 0 is not DRI2 capable
[ 45.994] (EE) AIGLX: reverting to software rendering
Still nothing. When I first installed Ubuntu 15.10 I managed to install this driver correctly and was using it till I decided to try Crimson AMD Driver yesterday (what a big mistake). I didn't like Crimson driver, so I completely uninstalled it. So now I have software rendering and not able to play games anymore, no solution from the web works.
drivers graphics ati opengl
bumped to the homepage by Community♦ 10 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Hi Sergey - I would remove the Oibaf drivers, I don't think they are helping you. You should useppa-purge
to do this, other methods will work poorly if at all. Then read this answer - I know it says "ATI" drivers, but the same methods remove the AMD drivers. Finally, I would try to re-install the drivers you had before...
– Charles Green
Dec 3 '15 at 22:33
Thank you for your answer! But, I already did everything you suggest and nothing helps
– Sergey Maslov
Dec 4 '15 at 11:58
add a comment |
I'm totally desperate. I'm trying to install open source video drivers for my R9 270x, but no matter what I do when I run
glxinfo | grep OpenGL
it shows
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.6, 128 bits)
OpenGL version string: 3.0 Mesa 11.0.2
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
I've been googling this problem for about 2 days already, read all posts related. Nothing works, nothing helps.
What I did:
added this ppa
ppa:oibaf/graphics-drivers
And this one
ppa:paulo-miguel-dias/mesa
Then
apt-get update
I looked into xorg.0.log file and found the following:
[ 45.977] (EE) Unable to initialize PCS database
[ 45.977] (EE) Missing PCS defaults file /etc/ati/amdpcsdb.default
[ 45.978] (II) [KMS] drm report modesetting isn't supported.
[ 45.978] (EE) open /dev/dri/card0: No such file or directory
[ 45.978] (WW) Falling back to old probe method for modesetting
[ 45.978] (EE) open /dev/dri/card0: No such file or directory
[ 45.978] (II) Loading sub module "fbdevhw"
[ 45.978] (II) LoadModule: "fbdevhw"
[ 45.978] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 45.989] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 45.989] compiled for 1.17.2, module version = 0.0.2
[ 45.989] ABI class: X.Org Video Driver, version 19.0
[ 45.989] (**) FBDEV(2): claimed PCI slot 1@0:0:0
[ 45.989] (II) FBDEV(2): using default device
[ 45.989] (WW) Falling back to old probe method for vesa
[ 45.989] (EE) Screen 0 deleted because of no matching config section.
[ 45.989] (II) UnloadModule: "radeon"
[ 45.989] (EE) Screen 0 deleted because of no matching config section.
45.994] (II) AIGLX: Screen 0 is not DRI2 capable
[ 45.994] (EE) AIGLX: reverting to software rendering
Still nothing. When I first installed Ubuntu 15.10 I managed to install this driver correctly and was using it till I decided to try Crimson AMD Driver yesterday (what a big mistake). I didn't like Crimson driver, so I completely uninstalled it. So now I have software rendering and not able to play games anymore, no solution from the web works.
drivers graphics ati opengl
I'm totally desperate. I'm trying to install open source video drivers for my R9 270x, but no matter what I do when I run
glxinfo | grep OpenGL
it shows
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.6, 128 bits)
OpenGL version string: 3.0 Mesa 11.0.2
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
I've been googling this problem for about 2 days already, read all posts related. Nothing works, nothing helps.
What I did:
added this ppa
ppa:oibaf/graphics-drivers
And this one
ppa:paulo-miguel-dias/mesa
Then
apt-get update
I looked into xorg.0.log file and found the following:
[ 45.977] (EE) Unable to initialize PCS database
[ 45.977] (EE) Missing PCS defaults file /etc/ati/amdpcsdb.default
[ 45.978] (II) [KMS] drm report modesetting isn't supported.
[ 45.978] (EE) open /dev/dri/card0: No such file or directory
[ 45.978] (WW) Falling back to old probe method for modesetting
[ 45.978] (EE) open /dev/dri/card0: No such file or directory
[ 45.978] (II) Loading sub module "fbdevhw"
[ 45.978] (II) LoadModule: "fbdevhw"
[ 45.978] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 45.989] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 45.989] compiled for 1.17.2, module version = 0.0.2
[ 45.989] ABI class: X.Org Video Driver, version 19.0
[ 45.989] (**) FBDEV(2): claimed PCI slot 1@0:0:0
[ 45.989] (II) FBDEV(2): using default device
[ 45.989] (WW) Falling back to old probe method for vesa
[ 45.989] (EE) Screen 0 deleted because of no matching config section.
[ 45.989] (II) UnloadModule: "radeon"
[ 45.989] (EE) Screen 0 deleted because of no matching config section.
45.994] (II) AIGLX: Screen 0 is not DRI2 capable
[ 45.994] (EE) AIGLX: reverting to software rendering
Still nothing. When I first installed Ubuntu 15.10 I managed to install this driver correctly and was using it till I decided to try Crimson AMD Driver yesterday (what a big mistake). I didn't like Crimson driver, so I completely uninstalled it. So now I have software rendering and not able to play games anymore, no solution from the web works.
drivers graphics ati opengl
drivers graphics ati opengl
edited Dec 3 '15 at 19:18
Sergey Maslov
asked Dec 3 '15 at 18:33
Sergey MaslovSergey Maslov
11314
11314
bumped to the homepage by Community♦ 10 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♦ 10 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Hi Sergey - I would remove the Oibaf drivers, I don't think they are helping you. You should useppa-purge
to do this, other methods will work poorly if at all. Then read this answer - I know it says "ATI" drivers, but the same methods remove the AMD drivers. Finally, I would try to re-install the drivers you had before...
– Charles Green
Dec 3 '15 at 22:33
Thank you for your answer! But, I already did everything you suggest and nothing helps
– Sergey Maslov
Dec 4 '15 at 11:58
add a comment |
Hi Sergey - I would remove the Oibaf drivers, I don't think they are helping you. You should useppa-purge
to do this, other methods will work poorly if at all. Then read this answer - I know it says "ATI" drivers, but the same methods remove the AMD drivers. Finally, I would try to re-install the drivers you had before...
– Charles Green
Dec 3 '15 at 22:33
Thank you for your answer! But, I already did everything you suggest and nothing helps
– Sergey Maslov
Dec 4 '15 at 11:58
Hi Sergey - I would remove the Oibaf drivers, I don't think they are helping you. You should use
ppa-purge
to do this, other methods will work poorly if at all. Then read this answer - I know it says "ATI" drivers, but the same methods remove the AMD drivers. Finally, I would try to re-install the drivers you had before...– Charles Green
Dec 3 '15 at 22:33
Hi Sergey - I would remove the Oibaf drivers, I don't think they are helping you. You should use
ppa-purge
to do this, other methods will work poorly if at all. Then read this answer - I know it says "ATI" drivers, but the same methods remove the AMD drivers. Finally, I would try to re-install the drivers you had before...– Charles Green
Dec 3 '15 at 22:33
Thank you for your answer! But, I already did everything you suggest and nothing helps
– Sergey Maslov
Dec 4 '15 at 11:58
Thank you for your answer! But, I already did everything you suggest and nothing helps
– Sergey Maslov
Dec 4 '15 at 11:58
add a comment |
1 Answer
1
active
oldest
votes
I have the same situation on Ubuntu Xenial.
For now, there is a bug for kernel 4.2+
You should do :
sudo ppa-purge oibaf/graphics-drivers
sudo ppa-purge paulo-miguel-dias/mesa
reboot
Then, you can either stay with the opensource AMDGPU driver or downgrade your kernel to 4.1.15 and try again.
sudo apt install fglrx
sudo amdconfig --initial
sudo dpkg-reconfigure xserver-xorg
reboot
To diagnose issue, look at your /var/log/kern or dmesg
grep fglrx /var/log/kern
dmesg | grep fglrx
If you can't reboot, go in recovery mode and work with those command
Good luck :)
thank you for your answer. what does this command do? sudo paulo-miguel-dias/mesa. Well, I managed to solve this by reinstalling system and looks like the root of the problem was in remains of official AMD driver, that I uninstalled unproperly. So for this situation the real question is: how to uninstall drivers correctly?
– Sergey Maslov
Jan 11 '16 at 6:35
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%2f705581%2fgalium-0-4-on-llvmpipe%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
I have the same situation on Ubuntu Xenial.
For now, there is a bug for kernel 4.2+
You should do :
sudo ppa-purge oibaf/graphics-drivers
sudo ppa-purge paulo-miguel-dias/mesa
reboot
Then, you can either stay with the opensource AMDGPU driver or downgrade your kernel to 4.1.15 and try again.
sudo apt install fglrx
sudo amdconfig --initial
sudo dpkg-reconfigure xserver-xorg
reboot
To diagnose issue, look at your /var/log/kern or dmesg
grep fglrx /var/log/kern
dmesg | grep fglrx
If you can't reboot, go in recovery mode and work with those command
Good luck :)
thank you for your answer. what does this command do? sudo paulo-miguel-dias/mesa. Well, I managed to solve this by reinstalling system and looks like the root of the problem was in remains of official AMD driver, that I uninstalled unproperly. So for this situation the real question is: how to uninstall drivers correctly?
– Sergey Maslov
Jan 11 '16 at 6:35
add a comment |
I have the same situation on Ubuntu Xenial.
For now, there is a bug for kernel 4.2+
You should do :
sudo ppa-purge oibaf/graphics-drivers
sudo ppa-purge paulo-miguel-dias/mesa
reboot
Then, you can either stay with the opensource AMDGPU driver or downgrade your kernel to 4.1.15 and try again.
sudo apt install fglrx
sudo amdconfig --initial
sudo dpkg-reconfigure xserver-xorg
reboot
To diagnose issue, look at your /var/log/kern or dmesg
grep fglrx /var/log/kern
dmesg | grep fglrx
If you can't reboot, go in recovery mode and work with those command
Good luck :)
thank you for your answer. what does this command do? sudo paulo-miguel-dias/mesa. Well, I managed to solve this by reinstalling system and looks like the root of the problem was in remains of official AMD driver, that I uninstalled unproperly. So for this situation the real question is: how to uninstall drivers correctly?
– Sergey Maslov
Jan 11 '16 at 6:35
add a comment |
I have the same situation on Ubuntu Xenial.
For now, there is a bug for kernel 4.2+
You should do :
sudo ppa-purge oibaf/graphics-drivers
sudo ppa-purge paulo-miguel-dias/mesa
reboot
Then, you can either stay with the opensource AMDGPU driver or downgrade your kernel to 4.1.15 and try again.
sudo apt install fglrx
sudo amdconfig --initial
sudo dpkg-reconfigure xserver-xorg
reboot
To diagnose issue, look at your /var/log/kern or dmesg
grep fglrx /var/log/kern
dmesg | grep fglrx
If you can't reboot, go in recovery mode and work with those command
Good luck :)
I have the same situation on Ubuntu Xenial.
For now, there is a bug for kernel 4.2+
You should do :
sudo ppa-purge oibaf/graphics-drivers
sudo ppa-purge paulo-miguel-dias/mesa
reboot
Then, you can either stay with the opensource AMDGPU driver or downgrade your kernel to 4.1.15 and try again.
sudo apt install fglrx
sudo amdconfig --initial
sudo dpkg-reconfigure xserver-xorg
reboot
To diagnose issue, look at your /var/log/kern or dmesg
grep fglrx /var/log/kern
dmesg | grep fglrx
If you can't reboot, go in recovery mode and work with those command
Good luck :)
edited Jan 11 '16 at 9:33
answered Jan 10 '16 at 22:20
Tr4sKTr4sK
33
33
thank you for your answer. what does this command do? sudo paulo-miguel-dias/mesa. Well, I managed to solve this by reinstalling system and looks like the root of the problem was in remains of official AMD driver, that I uninstalled unproperly. So for this situation the real question is: how to uninstall drivers correctly?
– Sergey Maslov
Jan 11 '16 at 6:35
add a comment |
thank you for your answer. what does this command do? sudo paulo-miguel-dias/mesa. Well, I managed to solve this by reinstalling system and looks like the root of the problem was in remains of official AMD driver, that I uninstalled unproperly. So for this situation the real question is: how to uninstall drivers correctly?
– Sergey Maslov
Jan 11 '16 at 6:35
thank you for your answer. what does this command do? sudo paulo-miguel-dias/mesa. Well, I managed to solve this by reinstalling system and looks like the root of the problem was in remains of official AMD driver, that I uninstalled unproperly. So for this situation the real question is: how to uninstall drivers correctly?
– Sergey Maslov
Jan 11 '16 at 6:35
thank you for your answer. what does this command do? sudo paulo-miguel-dias/mesa. Well, I managed to solve this by reinstalling system and looks like the root of the problem was in remains of official AMD driver, that I uninstalled unproperly. So for this situation the real question is: how to uninstall drivers correctly?
– Sergey Maslov
Jan 11 '16 at 6:35
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%2f705581%2fgalium-0-4-on-llvmpipe%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
Hi Sergey - I would remove the Oibaf drivers, I don't think they are helping you. You should use
ppa-purge
to do this, other methods will work poorly if at all. Then read this answer - I know it says "ATI" drivers, but the same methods remove the AMD drivers. Finally, I would try to re-install the drivers you had before...– Charles Green
Dec 3 '15 at 22:33
Thank you for your answer! But, I already did everything you suggest and nothing helps
– Sergey Maslov
Dec 4 '15 at 11:58