Proprietary drivers ATI Radeon HD in Ubuntu 13.04 don't work
I have an HP dv7 Pavillion with AMD/Intel hybrid graphics. The AMD is a Radeon HD 6370m, totally supported by AMD. I want to run with proprietary drivers to properly play games. I've already rigorously tried:
1) The method presented by Marian Lux here;
2) The method presented here, both usual and beta (13.6) versions;
3) The method presented here by Alexislavie, properly adapted to 13.04 version (that means, downloading the driver 13.4);
4) The first method presented here by Chris Carter, except for nomodeset configuration;
5) The second method presented there in the previous link by Nick Andrik;
6) The method presented here by Rodrigo Martins.
All of them were tested in fresh new installations of Ubuntu 13.04 (imagine how much time I've wasted reinstalling --clean-- versions of Ubuntu 13.04).
The results I get:
1) Every time when the installation is successful and I can apply the sudo aticonfig --initial
command (or its variants), the reboot returns me to the black screen (where it's said I'm running in "low graphics").
2) Each time when the installation seems not be successful (i.e., I can't apply the previous command or I simply don't do it - or even I restore the original xorg.conf back) I can log in but the Unity is broken, and the fglrxinfo
command also returns that there's a problem.
I would even try Ubuntu 12.04 if I were sure that those problems are related to my Ubuntu version, but I don't think so. That's why I'd appreciate your help to get those drivers properly working in Ubuntu 13.04.
[EDIT]
Just to register: I've made another --clear-- installation of Ubuntu 13.04 and tried rigorously exactly accurately... the method proposed by Rodrigo Martins. It didn't work. After rebooting, I get back to the black screen The system is running in low-graphics mode
.
drivers 13.04 radeon amd-graphics proprietary
add a comment |
I have an HP dv7 Pavillion with AMD/Intel hybrid graphics. The AMD is a Radeon HD 6370m, totally supported by AMD. I want to run with proprietary drivers to properly play games. I've already rigorously tried:
1) The method presented by Marian Lux here;
2) The method presented here, both usual and beta (13.6) versions;
3) The method presented here by Alexislavie, properly adapted to 13.04 version (that means, downloading the driver 13.4);
4) The first method presented here by Chris Carter, except for nomodeset configuration;
5) The second method presented there in the previous link by Nick Andrik;
6) The method presented here by Rodrigo Martins.
All of them were tested in fresh new installations of Ubuntu 13.04 (imagine how much time I've wasted reinstalling --clean-- versions of Ubuntu 13.04).
The results I get:
1) Every time when the installation is successful and I can apply the sudo aticonfig --initial
command (or its variants), the reboot returns me to the black screen (where it's said I'm running in "low graphics").
2) Each time when the installation seems not be successful (i.e., I can't apply the previous command or I simply don't do it - or even I restore the original xorg.conf back) I can log in but the Unity is broken, and the fglrxinfo
command also returns that there's a problem.
I would even try Ubuntu 12.04 if I were sure that those problems are related to my Ubuntu version, but I don't think so. That's why I'd appreciate your help to get those drivers properly working in Ubuntu 13.04.
[EDIT]
Just to register: I've made another --clear-- installation of Ubuntu 13.04 and tried rigorously exactly accurately... the method proposed by Rodrigo Martins. It didn't work. After rebooting, I get back to the black screen The system is running in low-graphics mode
.
drivers 13.04 radeon amd-graphics proprietary
Ok, I've already seen this link, but I see no difference between the method they explain there and the ones presented above (specially the 1st, the 2nd and the 3rd). Do you see any difference? Which one? Thanks.
– Tales Tomaz
Jul 19 '13 at 15:43
What is the output offglrxinfo
?
– Rodrigo Martins
Jul 26 '13 at 1:50
+1 because even if now this question is about an EOL release (have you had any success with 13.10?), this question should be pointed as example to newcomers...
– Rmano
Mar 18 '14 at 22:16
add a comment |
I have an HP dv7 Pavillion with AMD/Intel hybrid graphics. The AMD is a Radeon HD 6370m, totally supported by AMD. I want to run with proprietary drivers to properly play games. I've already rigorously tried:
1) The method presented by Marian Lux here;
2) The method presented here, both usual and beta (13.6) versions;
3) The method presented here by Alexislavie, properly adapted to 13.04 version (that means, downloading the driver 13.4);
4) The first method presented here by Chris Carter, except for nomodeset configuration;
5) The second method presented there in the previous link by Nick Andrik;
6) The method presented here by Rodrigo Martins.
All of them were tested in fresh new installations of Ubuntu 13.04 (imagine how much time I've wasted reinstalling --clean-- versions of Ubuntu 13.04).
The results I get:
1) Every time when the installation is successful and I can apply the sudo aticonfig --initial
command (or its variants), the reboot returns me to the black screen (where it's said I'm running in "low graphics").
2) Each time when the installation seems not be successful (i.e., I can't apply the previous command or I simply don't do it - or even I restore the original xorg.conf back) I can log in but the Unity is broken, and the fglrxinfo
command also returns that there's a problem.
I would even try Ubuntu 12.04 if I were sure that those problems are related to my Ubuntu version, but I don't think so. That's why I'd appreciate your help to get those drivers properly working in Ubuntu 13.04.
[EDIT]
Just to register: I've made another --clear-- installation of Ubuntu 13.04 and tried rigorously exactly accurately... the method proposed by Rodrigo Martins. It didn't work. After rebooting, I get back to the black screen The system is running in low-graphics mode
.
drivers 13.04 radeon amd-graphics proprietary
I have an HP dv7 Pavillion with AMD/Intel hybrid graphics. The AMD is a Radeon HD 6370m, totally supported by AMD. I want to run with proprietary drivers to properly play games. I've already rigorously tried:
1) The method presented by Marian Lux here;
2) The method presented here, both usual and beta (13.6) versions;
3) The method presented here by Alexislavie, properly adapted to 13.04 version (that means, downloading the driver 13.4);
4) The first method presented here by Chris Carter, except for nomodeset configuration;
5) The second method presented there in the previous link by Nick Andrik;
6) The method presented here by Rodrigo Martins.
All of them were tested in fresh new installations of Ubuntu 13.04 (imagine how much time I've wasted reinstalling --clean-- versions of Ubuntu 13.04).
The results I get:
1) Every time when the installation is successful and I can apply the sudo aticonfig --initial
command (or its variants), the reboot returns me to the black screen (where it's said I'm running in "low graphics").
2) Each time when the installation seems not be successful (i.e., I can't apply the previous command or I simply don't do it - or even I restore the original xorg.conf back) I can log in but the Unity is broken, and the fglrxinfo
command also returns that there's a problem.
I would even try Ubuntu 12.04 if I were sure that those problems are related to my Ubuntu version, but I don't think so. That's why I'd appreciate your help to get those drivers properly working in Ubuntu 13.04.
[EDIT]
Just to register: I've made another --clear-- installation of Ubuntu 13.04 and tried rigorously exactly accurately... the method proposed by Rodrigo Martins. It didn't work. After rebooting, I get back to the black screen The system is running in low-graphics mode
.
drivers 13.04 radeon amd-graphics proprietary
drivers 13.04 radeon amd-graphics proprietary
edited Oct 29 '18 at 23:14
Yufenyuy Veyeh Dider
1,5414924
1,5414924
asked Jul 19 '13 at 14:41
Tales TomazTales Tomaz
1213
1213
Ok, I've already seen this link, but I see no difference between the method they explain there and the ones presented above (specially the 1st, the 2nd and the 3rd). Do you see any difference? Which one? Thanks.
– Tales Tomaz
Jul 19 '13 at 15:43
What is the output offglrxinfo
?
– Rodrigo Martins
Jul 26 '13 at 1:50
+1 because even if now this question is about an EOL release (have you had any success with 13.10?), this question should be pointed as example to newcomers...
– Rmano
Mar 18 '14 at 22:16
add a comment |
Ok, I've already seen this link, but I see no difference between the method they explain there and the ones presented above (specially the 1st, the 2nd and the 3rd). Do you see any difference? Which one? Thanks.
– Tales Tomaz
Jul 19 '13 at 15:43
What is the output offglrxinfo
?
– Rodrigo Martins
Jul 26 '13 at 1:50
+1 because even if now this question is about an EOL release (have you had any success with 13.10?), this question should be pointed as example to newcomers...
– Rmano
Mar 18 '14 at 22:16
Ok, I've already seen this link, but I see no difference between the method they explain there and the ones presented above (specially the 1st, the 2nd and the 3rd). Do you see any difference? Which one? Thanks.
– Tales Tomaz
Jul 19 '13 at 15:43
Ok, I've already seen this link, but I see no difference between the method they explain there and the ones presented above (specially the 1st, the 2nd and the 3rd). Do you see any difference? Which one? Thanks.
– Tales Tomaz
Jul 19 '13 at 15:43
What is the output of
fglrxinfo
?– Rodrigo Martins
Jul 26 '13 at 1:50
What is the output of
fglrxinfo
?– Rodrigo Martins
Jul 26 '13 at 1:50
+1 because even if now this question is about an EOL release (have you had any success with 13.10?), this question should be pointed as example to newcomers...
– Rmano
Mar 18 '14 at 22:16
+1 because even if now this question is about an EOL release (have you had any success with 13.10?), this question should be pointed as example to newcomers...
– Rmano
Mar 18 '14 at 22:16
add a comment |
1 Answer
1
active
oldest
votes
Until now, the AMD proprietary drivers didn't work with Ubuntu 13.04 (graphic card Radeon 6850).
But today (07 sept 13), I simply check the proprietary driver (update) in System parameters of Ubuntu, it got installed and it works ! So, it seems to have been updated.
These are great news! What do you mean with "proprietary driver in System parameters"? Did you try to install it through "Additional drivers", is it that?
– Tales Tomaz
Sep 8 '13 at 11:39
Unfortunately it didn't work here again. When I reboot, the Unity is broken. The command fglrxinfo returns: X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 154 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 12 Current serial number in output stream: 12
– Tales Tomaz
Sep 29 '13 at 13:14
@TalesTomaz can you add that to your question? Each time you try something and fail add the new information to the question.
– Braiam
Oct 9 '13 at 13:08
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%2f321913%2fproprietary-drivers-ati-radeon-hd-in-ubuntu-13-04-dont-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
Until now, the AMD proprietary drivers didn't work with Ubuntu 13.04 (graphic card Radeon 6850).
But today (07 sept 13), I simply check the proprietary driver (update) in System parameters of Ubuntu, it got installed and it works ! So, it seems to have been updated.
These are great news! What do you mean with "proprietary driver in System parameters"? Did you try to install it through "Additional drivers", is it that?
– Tales Tomaz
Sep 8 '13 at 11:39
Unfortunately it didn't work here again. When I reboot, the Unity is broken. The command fglrxinfo returns: X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 154 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 12 Current serial number in output stream: 12
– Tales Tomaz
Sep 29 '13 at 13:14
@TalesTomaz can you add that to your question? Each time you try something and fail add the new information to the question.
– Braiam
Oct 9 '13 at 13:08
add a comment |
Until now, the AMD proprietary drivers didn't work with Ubuntu 13.04 (graphic card Radeon 6850).
But today (07 sept 13), I simply check the proprietary driver (update) in System parameters of Ubuntu, it got installed and it works ! So, it seems to have been updated.
These are great news! What do you mean with "proprietary driver in System parameters"? Did you try to install it through "Additional drivers", is it that?
– Tales Tomaz
Sep 8 '13 at 11:39
Unfortunately it didn't work here again. When I reboot, the Unity is broken. The command fglrxinfo returns: X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 154 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 12 Current serial number in output stream: 12
– Tales Tomaz
Sep 29 '13 at 13:14
@TalesTomaz can you add that to your question? Each time you try something and fail add the new information to the question.
– Braiam
Oct 9 '13 at 13:08
add a comment |
Until now, the AMD proprietary drivers didn't work with Ubuntu 13.04 (graphic card Radeon 6850).
But today (07 sept 13), I simply check the proprietary driver (update) in System parameters of Ubuntu, it got installed and it works ! So, it seems to have been updated.
Until now, the AMD proprietary drivers didn't work with Ubuntu 13.04 (graphic card Radeon 6850).
But today (07 sept 13), I simply check the proprietary driver (update) in System parameters of Ubuntu, it got installed and it works ! So, it seems to have been updated.
answered Sep 7 '13 at 9:56
arvernearverne
12
12
These are great news! What do you mean with "proprietary driver in System parameters"? Did you try to install it through "Additional drivers", is it that?
– Tales Tomaz
Sep 8 '13 at 11:39
Unfortunately it didn't work here again. When I reboot, the Unity is broken. The command fglrxinfo returns: X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 154 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 12 Current serial number in output stream: 12
– Tales Tomaz
Sep 29 '13 at 13:14
@TalesTomaz can you add that to your question? Each time you try something and fail add the new information to the question.
– Braiam
Oct 9 '13 at 13:08
add a comment |
These are great news! What do you mean with "proprietary driver in System parameters"? Did you try to install it through "Additional drivers", is it that?
– Tales Tomaz
Sep 8 '13 at 11:39
Unfortunately it didn't work here again. When I reboot, the Unity is broken. The command fglrxinfo returns: X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 154 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 12 Current serial number in output stream: 12
– Tales Tomaz
Sep 29 '13 at 13:14
@TalesTomaz can you add that to your question? Each time you try something and fail add the new information to the question.
– Braiam
Oct 9 '13 at 13:08
These are great news! What do you mean with "proprietary driver in System parameters"? Did you try to install it through "Additional drivers", is it that?
– Tales Tomaz
Sep 8 '13 at 11:39
These are great news! What do you mean with "proprietary driver in System parameters"? Did you try to install it through "Additional drivers", is it that?
– Tales Tomaz
Sep 8 '13 at 11:39
Unfortunately it didn't work here again. When I reboot, the Unity is broken. The command fglrxinfo returns: X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 154 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 12 Current serial number in output stream: 12
– Tales Tomaz
Sep 29 '13 at 13:14
Unfortunately it didn't work here again. When I reboot, the Unity is broken. The command fglrxinfo returns: X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 154 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 12 Current serial number in output stream: 12
– Tales Tomaz
Sep 29 '13 at 13:14
@TalesTomaz can you add that to your question? Each time you try something and fail add the new information to the question.
– Braiam
Oct 9 '13 at 13:08
@TalesTomaz can you add that to your question? Each time you try something and fail add the new information to the question.
– Braiam
Oct 9 '13 at 13:08
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%2f321913%2fproprietary-drivers-ati-radeon-hd-in-ubuntu-13-04-dont-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
Ok, I've already seen this link, but I see no difference between the method they explain there and the ones presented above (specially the 1st, the 2nd and the 3rd). Do you see any difference? Which one? Thanks.
– Tales Tomaz
Jul 19 '13 at 15:43
What is the output of
fglrxinfo
?– Rodrigo Martins
Jul 26 '13 at 1:50
+1 because even if now this question is about an EOL release (have you had any success with 13.10?), this question should be pointed as example to newcomers...
– Rmano
Mar 18 '14 at 22:16