Issues with Fury X driver install

[Rudy Toody]

I am trying to install AMD Catalyst on Debian "Stretch" 4.4.0-1. (This install require 3.6 or greater.) I get an error at the last step (DKMS) which I haven't been able to resolve.

Could someone tell me where I've gone wrong?

Here is what I have done (over several days) to get to this point:

Install Stretch (which installs 4.3.0-1)
Reboot
Install Stretch 4.4.0-1
Reboot
Completely remove 4.3.0-1
Reboot into root
Install Boinc modules and the two additional ones which have the dependencies.
Completely remove the NVIDIA modules so we don't get a tainted kernel.
Download Catalyst and unpack into fglrx-15.302 directory
Run amd-driver-installer-15.302-x86.x86_64.run

fglrx-install.log:

Supported adapter detected.
Check if system has the tools required for installation.
Uninstalling any previously installed drivers.

Creating symlink /var/lib/dkms/fglrx/15.302/source ->
                 /usr/src/fglrx-15.302

DKMS: add completed.

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area....
cd /var/lib/dkms/fglrx/15.302/build; sh make.sh --nohints --uname_r=4.4.0-1-amd64 --norootcheck....(bad exit status: 1)
[Error] Kernel Module : Failed to build fglrx-15.302 with DKMS
[Error] Kernel Module : Removing fglrx-15.302 from DKMS

------------------------------
Deleting module version: 15.302
completely from the DKMS tree.
------------------------------
Done.
[Reboot] Kernel Module : update-initramfs

 

[MrColin]

It could be that you don't have the compiler and or the kernel header libs or some other dependency installed. You need those in order to build the kernel module.

 

[Jodell88]

Isn't there a catalyst package for debian? I would use that rather than installing without a package manager.

 

[Rudy Toody]

It could be that you don't have the compiler and or the kernel header libs or some other dependency installed. You need those in order to build the kernel module.

At the Catalyst download point, I have all installed except possibly DKMS. That is what the complicated install/reboot steps accomplish.

Isn't there a catalyst package for debian? I would use that rather than installing without a package manager.

There is no package for debian. which is why I had to install the two BOINC modules which set the dependencies to make this work.

So I think I'm missing a DKMS module of some kind. Probably a source which is used by the final make command.

Any help to identify that module or to trace the install to identify it, is greatly appreciated.

 

[Elixer]

Have you tried these yet?
http://support.amd.com/en-us/kb-articles/Pages/AMDGPU-PRO-Beta-Driver-for-Vulkan-Release-Notes.aspx

 

[Rudy Toody]

Have you tried these yet?
http://support.amd.com/en-us/kb-articles/Pages/AMDGPU-PRO-Beta-Driver-for-Vulkan-Release-Notes.aspx

It states that there is no current support for OpenCL. I'm doing all this to crunch BOINC projects. Thanks for the heads-up.

 

[Rudy Toody]

It appears that fglrx-modules-dkms and fglrx-source are the missing packages. I have to get them from an earlier release and I have no idea if they will work.

 

[Rudy Toody]

I abandoned Debian and switched to openSUSE 42.1 and got the Furry X set up. Boinc doesn't work yet---two issues: hostname and remote security code for Boinc manager. Client is fine.

I over-rode the security requirement, but the hostname problem appears to be a permissions issue.

 

[Rudy Toody]

The BOINC package in openSUSE 42.1 is garbled. It sets up directory boinc instead of boinc-client which is where all the configuration info and the data reside. If I can't build a working BOINC install, I will do it manually.