AMD Catalyst installation woes on Slackware
Clash Royale CLAN TAG#URR8PPP
I'm trying to get my ATI graphics driver installed on my fresh Slackware OS (Zenwalk). I'm coming from Ubuntu 14.04-14.10, so I know there's a whole lot I don't understand just yet.
I download the .zip archive from here, then unzip
it to extract the .run file.
sh amd-driver-installer-catalyst-13.1-legacy-linux-x86.x86_64.run --buildpkg
generates the following output:
Created directory fglrx-install.hu4jBU
Verifying archive integrity... All good.
Uncompressing AMD Catalyst(TM) Proprietary Driver-8.97.100.7.........
=====================================================================
AMD Catalyst(TM) Proprietary Driver Installer/Packager
=====================================================================
Generating package: Slackware/Slackware
ATI SlackBuild
--------------------------------------------
by: Emanuele Tomasi <tomasi@cli.di.unipi.it>
AMD kernel module generator version 2.1
kernel includes at /usr/src/linux/include not found or incomplete
file: /usr/src/linux/include/linux/version.h
ERROR: I didn't make module
Removing temporary directory: fglrx-install.hu4jBU
Using the command ./amd-driver-installer-catalyst-13.1-legacy-linux-x86.x86_64.run
runs the GUI setup, but results in the same error. I'm not sure what to make of this error, or what steps I should be taking. Any assistance is appreciated.
If it matters, uname -r
= 3.14.5
slackware amd-graphics
add a comment |
I'm trying to get my ATI graphics driver installed on my fresh Slackware OS (Zenwalk). I'm coming from Ubuntu 14.04-14.10, so I know there's a whole lot I don't understand just yet.
I download the .zip archive from here, then unzip
it to extract the .run file.
sh amd-driver-installer-catalyst-13.1-legacy-linux-x86.x86_64.run --buildpkg
generates the following output:
Created directory fglrx-install.hu4jBU
Verifying archive integrity... All good.
Uncompressing AMD Catalyst(TM) Proprietary Driver-8.97.100.7.........
=====================================================================
AMD Catalyst(TM) Proprietary Driver Installer/Packager
=====================================================================
Generating package: Slackware/Slackware
ATI SlackBuild
--------------------------------------------
by: Emanuele Tomasi <tomasi@cli.di.unipi.it>
AMD kernel module generator version 2.1
kernel includes at /usr/src/linux/include not found or incomplete
file: /usr/src/linux/include/linux/version.h
ERROR: I didn't make module
Removing temporary directory: fglrx-install.hu4jBU
Using the command ./amd-driver-installer-catalyst-13.1-legacy-linux-x86.x86_64.run
runs the GUI setup, but results in the same error. I'm not sure what to make of this error, or what steps I should be taking. Any assistance is appreciated.
If it matters, uname -r
= 3.14.5
slackware amd-graphics
Not what you want to hear, but I had a disastrous time with that installer too. I had better luck with the system standard fglrx driver. But as to your error, it looks like you need to install the headers package for your kernel. I eventually went to nvidia graphics and haven't had a problem with them of any kind.
– Ray Andrews
Feb 2 '15 at 5:24
add a comment |
I'm trying to get my ATI graphics driver installed on my fresh Slackware OS (Zenwalk). I'm coming from Ubuntu 14.04-14.10, so I know there's a whole lot I don't understand just yet.
I download the .zip archive from here, then unzip
it to extract the .run file.
sh amd-driver-installer-catalyst-13.1-legacy-linux-x86.x86_64.run --buildpkg
generates the following output:
Created directory fglrx-install.hu4jBU
Verifying archive integrity... All good.
Uncompressing AMD Catalyst(TM) Proprietary Driver-8.97.100.7.........
=====================================================================
AMD Catalyst(TM) Proprietary Driver Installer/Packager
=====================================================================
Generating package: Slackware/Slackware
ATI SlackBuild
--------------------------------------------
by: Emanuele Tomasi <tomasi@cli.di.unipi.it>
AMD kernel module generator version 2.1
kernel includes at /usr/src/linux/include not found or incomplete
file: /usr/src/linux/include/linux/version.h
ERROR: I didn't make module
Removing temporary directory: fglrx-install.hu4jBU
Using the command ./amd-driver-installer-catalyst-13.1-legacy-linux-x86.x86_64.run
runs the GUI setup, but results in the same error. I'm not sure what to make of this error, or what steps I should be taking. Any assistance is appreciated.
If it matters, uname -r
= 3.14.5
slackware amd-graphics
I'm trying to get my ATI graphics driver installed on my fresh Slackware OS (Zenwalk). I'm coming from Ubuntu 14.04-14.10, so I know there's a whole lot I don't understand just yet.
I download the .zip archive from here, then unzip
it to extract the .run file.
sh amd-driver-installer-catalyst-13.1-legacy-linux-x86.x86_64.run --buildpkg
generates the following output:
Created directory fglrx-install.hu4jBU
Verifying archive integrity... All good.
Uncompressing AMD Catalyst(TM) Proprietary Driver-8.97.100.7.........
=====================================================================
AMD Catalyst(TM) Proprietary Driver Installer/Packager
=====================================================================
Generating package: Slackware/Slackware
ATI SlackBuild
--------------------------------------------
by: Emanuele Tomasi <tomasi@cli.di.unipi.it>
AMD kernel module generator version 2.1
kernel includes at /usr/src/linux/include not found or incomplete
file: /usr/src/linux/include/linux/version.h
ERROR: I didn't make module
Removing temporary directory: fglrx-install.hu4jBU
Using the command ./amd-driver-installer-catalyst-13.1-legacy-linux-x86.x86_64.run
runs the GUI setup, but results in the same error. I'm not sure what to make of this error, or what steps I should be taking. Any assistance is appreciated.
If it matters, uname -r
= 3.14.5
slackware amd-graphics
slackware amd-graphics
asked Feb 1 '15 at 21:02
SCKSCK
215
215
Not what you want to hear, but I had a disastrous time with that installer too. I had better luck with the system standard fglrx driver. But as to your error, it looks like you need to install the headers package for your kernel. I eventually went to nvidia graphics and haven't had a problem with them of any kind.
– Ray Andrews
Feb 2 '15 at 5:24
add a comment |
Not what you want to hear, but I had a disastrous time with that installer too. I had better luck with the system standard fglrx driver. But as to your error, it looks like you need to install the headers package for your kernel. I eventually went to nvidia graphics and haven't had a problem with them of any kind.
– Ray Andrews
Feb 2 '15 at 5:24
Not what you want to hear, but I had a disastrous time with that installer too. I had better luck with the system standard fglrx driver. But as to your error, it looks like you need to install the headers package for your kernel. I eventually went to nvidia graphics and haven't had a problem with them of any kind.
– Ray Andrews
Feb 2 '15 at 5:24
Not what you want to hear, but I had a disastrous time with that installer too. I had better luck with the system standard fglrx driver. But as to your error, it looks like you need to install the headers package for your kernel. I eventually went to nvidia graphics and haven't had a problem with them of any kind.
– Ray Andrews
Feb 2 '15 at 5:24
add a comment |
1 Answer
1
active
oldest
votes
I "solved" this by impatiently reformatting everything and freshly installing Ubuntu 14.04 again. Now everything works as it should.
With Ubuntu's driver, or with Catalyst? I don't think I'd ever touch the latter ever again, but if you got it to work ...
– Ray Andrews
Feb 2 '15 at 16:12
@rayandrews I'm just running with whatever shipped in Ubuntu. It worked fine before, it seems to be working fine now. I love my crusty old Sapphire ATI, I just want to know that I'm actually utilizing it to its full potential. And yeah, I seem to see less grief coming from the Nvidia side of things, but I built this dinosaur from the ground up with an AMD backbone. Next time around perhaps...
– SCK
Feb 2 '15 at 16:29
Ok. Be safe and stay away from that Catalyst disaster ;-)
– Ray Andrews
Feb 2 '15 at 21:51
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f182355%2famd-catalyst-installation-woes-on-slackware%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 "solved" this by impatiently reformatting everything and freshly installing Ubuntu 14.04 again. Now everything works as it should.
With Ubuntu's driver, or with Catalyst? I don't think I'd ever touch the latter ever again, but if you got it to work ...
– Ray Andrews
Feb 2 '15 at 16:12
@rayandrews I'm just running with whatever shipped in Ubuntu. It worked fine before, it seems to be working fine now. I love my crusty old Sapphire ATI, I just want to know that I'm actually utilizing it to its full potential. And yeah, I seem to see less grief coming from the Nvidia side of things, but I built this dinosaur from the ground up with an AMD backbone. Next time around perhaps...
– SCK
Feb 2 '15 at 16:29
Ok. Be safe and stay away from that Catalyst disaster ;-)
– Ray Andrews
Feb 2 '15 at 21:51
add a comment |
I "solved" this by impatiently reformatting everything and freshly installing Ubuntu 14.04 again. Now everything works as it should.
With Ubuntu's driver, or with Catalyst? I don't think I'd ever touch the latter ever again, but if you got it to work ...
– Ray Andrews
Feb 2 '15 at 16:12
@rayandrews I'm just running with whatever shipped in Ubuntu. It worked fine before, it seems to be working fine now. I love my crusty old Sapphire ATI, I just want to know that I'm actually utilizing it to its full potential. And yeah, I seem to see less grief coming from the Nvidia side of things, but I built this dinosaur from the ground up with an AMD backbone. Next time around perhaps...
– SCK
Feb 2 '15 at 16:29
Ok. Be safe and stay away from that Catalyst disaster ;-)
– Ray Andrews
Feb 2 '15 at 21:51
add a comment |
I "solved" this by impatiently reformatting everything and freshly installing Ubuntu 14.04 again. Now everything works as it should.
I "solved" this by impatiently reformatting everything and freshly installing Ubuntu 14.04 again. Now everything works as it should.
answered Feb 2 '15 at 9:21
SCKSCK
215
215
With Ubuntu's driver, or with Catalyst? I don't think I'd ever touch the latter ever again, but if you got it to work ...
– Ray Andrews
Feb 2 '15 at 16:12
@rayandrews I'm just running with whatever shipped in Ubuntu. It worked fine before, it seems to be working fine now. I love my crusty old Sapphire ATI, I just want to know that I'm actually utilizing it to its full potential. And yeah, I seem to see less grief coming from the Nvidia side of things, but I built this dinosaur from the ground up with an AMD backbone. Next time around perhaps...
– SCK
Feb 2 '15 at 16:29
Ok. Be safe and stay away from that Catalyst disaster ;-)
– Ray Andrews
Feb 2 '15 at 21:51
add a comment |
With Ubuntu's driver, or with Catalyst? I don't think I'd ever touch the latter ever again, but if you got it to work ...
– Ray Andrews
Feb 2 '15 at 16:12
@rayandrews I'm just running with whatever shipped in Ubuntu. It worked fine before, it seems to be working fine now. I love my crusty old Sapphire ATI, I just want to know that I'm actually utilizing it to its full potential. And yeah, I seem to see less grief coming from the Nvidia side of things, but I built this dinosaur from the ground up with an AMD backbone. Next time around perhaps...
– SCK
Feb 2 '15 at 16:29
Ok. Be safe and stay away from that Catalyst disaster ;-)
– Ray Andrews
Feb 2 '15 at 21:51
With Ubuntu's driver, or with Catalyst? I don't think I'd ever touch the latter ever again, but if you got it to work ...
– Ray Andrews
Feb 2 '15 at 16:12
With Ubuntu's driver, or with Catalyst? I don't think I'd ever touch the latter ever again, but if you got it to work ...
– Ray Andrews
Feb 2 '15 at 16:12
@rayandrews I'm just running with whatever shipped in Ubuntu. It worked fine before, it seems to be working fine now. I love my crusty old Sapphire ATI, I just want to know that I'm actually utilizing it to its full potential. And yeah, I seem to see less grief coming from the Nvidia side of things, but I built this dinosaur from the ground up with an AMD backbone. Next time around perhaps...
– SCK
Feb 2 '15 at 16:29
@rayandrews I'm just running with whatever shipped in Ubuntu. It worked fine before, it seems to be working fine now. I love my crusty old Sapphire ATI, I just want to know that I'm actually utilizing it to its full potential. And yeah, I seem to see less grief coming from the Nvidia side of things, but I built this dinosaur from the ground up with an AMD backbone. Next time around perhaps...
– SCK
Feb 2 '15 at 16:29
Ok. Be safe and stay away from that Catalyst disaster ;-)
– Ray Andrews
Feb 2 '15 at 21:51
Ok. Be safe and stay away from that Catalyst disaster ;-)
– Ray Andrews
Feb 2 '15 at 21:51
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f182355%2famd-catalyst-installation-woes-on-slackware%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
Not what you want to hear, but I had a disastrous time with that installer too. I had better luck with the system standard fglrx driver. But as to your error, it looks like you need to install the headers package for your kernel. I eventually went to nvidia graphics and haven't had a problem with them of any kind.
– Ray Andrews
Feb 2 '15 at 5:24