Can't install AMD proprietary driver

English Hardware
#1

My CPU is AMD A4600 which integrates a AMD 7660G graphics along with the 7670M discrete graphic card
I want to compile AMD proprietary driver, so i downloaded the Official driver for my GPU from AMD website.

I’m using openSUSE 12.2 64bit with kernel :


mohit@linux-dv6e:/usr/share/ati> uname -r
3.4.6-2.10-desktop

Before compiling, i installed the build tools necessary using the following commands :


sudo zypper install kernel-source
sudo zypper install -t pattern devel_C_C++

no errors, everything went fine

then i extracted the downloaded file, made it executable and execute it using the following commands :


chmod + amd-catalyst-13.4-linux-x86.x86_64.run
sudo ./amd-catalyst-13.4-linux-x86.x86_64.run

I recieved an error that

“One or more tools required for installation cannot be found on the system. Install the required tools before installing the fglrx driver. Optionally, run the installer with --force option to install without the tools.
Forcing install will disable AMD hardware acceleration and may make your system unstable. Not recommended.”

I opened the log file in /usr/share/ati/fglrx-install.log

it had the following contents :


Supported adapter detected.
Supported adapter detected.
Check if system has the tools required for installation.
fglrx installation requires that the system have kernel headers.  /lib/modules/3.4.6-2.10-desktop/build/include/linux/version.h cannot be found on this system.
One or more tools required for installation cannot be found on the system. Install the required tools before installing the fglrx driver.
Optionally, run the installer with --force option to install without the tools.
Forcing install will disable AMD hardware acceleration and may make your system unstable. Not recommended.

i noticed that the file /lib/modules/3.4.6-2.10-desktop/build/include/linux/version.h did not exist but the file /lib/modules/3.4.33-2.24-desktop/build/include/linux/version.h.

It appears to me that the kernel header/source of 3.4.33-2.24 has been downloaded.

Can anybody please tell how to fix this problem or how to get right kernel source/header?

Any help will be deeply appreciated:)

#2

On 05/19/2013 11:36 AM, ThePerfectPunk wrote:
> Any help will be deeply appreciated

i suspect you have more than one repo enabled and updated with
kernels ready to be downloaded…and, when you issued the “sudo
zypper install kernel-source” zypper downloaded the source for the
latest version, from the highest priority repo it found…

one way to stop those kinds of things from happening would be to
start following the great advice in the paragraph beginning with
“IMPORTANT” in this post http://tinyurl.com/33qc9vu

another would be to use YaST Software Management for those kinds of
operations, so you can see what you are doing…

i guess if you open it and type kernel into the search block, and
scan down the list to kernel-source you will see (in the “Installed
(Available)” column that the source for more than one kernel is
available, and you are using (according to uname) one kernel but have
the source of another installed… you should be able left click
highlight the kernel-source line, the to go into the tab marked
“Versions” and (with the radio button) select to install the correct
source to match your working kernel…

hmmmm…i do not know, but i guess it is also possible with zypper to
specify the source of a particular kernel, rather than whatever is found.

by the way, read the caveat in my sig (i am not nearly as smart as my
photo makes me look:)

–
dd
http://tinyurl.com/DD-Caveat

#3

Have you installed the kernel-devel package? I had the same issue and solved by installing kernel devel package. Also there are some more requirements such as make. Cant remember from the top of my head but there is a document on the amd webpage, I think the link is on the same webpage where you find the link to download the drivers.

Hope that helps.

#4

Or rather kernel-desktop-devel.

But I would suggest to use the makerpm-amd-13.4.sh script by Sebastian Siebert to install the driver. That should correctly take care of everything.
See here: https://en.opensuse.org/SDB:AMD_fglrx#Building_yourself_the_rpm

#5

Well I stand corrected. Although, it doesnt make sence to install devel package that is not respective to the packages you have already installed.

Anyhow, this script didnt work very well for me. Over the years of using OpenSuSE I went through all the methods, in the end installing the latest available proprietary driver, compiled for your system, is provided only the way the op have attempted to install it.

If you are not too concerned about having the most recent driver installed, the link posted by wolfi323 will make things easier by far.

#6

Hm? The OP uses kernel-desktop, so kernel-desktop-devel is respective to the packages he has already installed, isn’t it? :wink:
And /lib/modules/3.4.6-2.10-desktop/build/include/linux/version.h is contained in the package kernel-desktop-devel.

Anyhow, this script didnt work very well for me. Over the years of using OpenSuSE I went through all the methods, in the end installing the latest available proprietary driver, compiled for your system, is provided only the way the op have attempted to install it.

Well, the script does the same, it just automates the process:

  • it installs all packages you need for compiling the driver
  • it downloads the latest version of the driver
  • it compiles the driver and creates an rpm package out of it
  • it installs that package

Of course the script may have bugs, but it has been improved incrementally over time…

#7

Well that was what i meant. By naming desktop-devel package I was reffering to any apropriate devel package in respect of what is installed.

Good thing you cleared it though cause by using minimal explanatory comments can confuse users that are unfamiliar with the differences in the details and my post could become misleading. I certainly remember being there and many vague or none descriptive posts were the reasons of many headaches :).

Once again victim of my own lacking in explanatory posts. You are correct it does all of the above. One thing that is different is the fact that there is some time from the release date of the latest driver in the AMD web site and the update of the said or any other script. That is a big difference for me and that is why it doesnt work for me. Plus I like being autonomous and waiting for a script to do something I ca do for myself isnt my first preference.

Otherwise the script runs fine cause I have used it and it is indeed improved as are all other different methods described in the link you provided.