cancel
Showing results for 
Search instead for 
Did you mean: 

Archives Discussions

wadesyu
Adept I

Problems when installing SDK v3.0-0-Beta

Hi there,

   I am Wade and I encountered some problems while installing AMDAPPSDK v3.0-0-Beta. The error messages are as follows:

[08-19-2015T14:39:04][166]Failed to install files in the /opt/AMDAPPSDK-3.0-0-Beta directory.

[08-19-2015T14:39:04][1151]Failed to install AMD APP SDK v3.0-0-Beta to /opt/AMDAPPSDK-3.0-0-Beta. The installation cannot continue.

Although this problem has been addressed before(https://community.amd.com/thread/169866#1307248), I still couldn't solve it with the solution proposed in the attached link.

The above is my log file information. Any suggestions or comments would be highly appreciated!

[08-19-2015T14:38:58][1069]Starting installation of AMD APP SDK v3.0-0-Beta

[08-19-2015T14:38:58][1070]Retrieving Operating System details...

[08-19-2015T14:38:58][68]Detected OS Architecture: 64

[08-19-2015T14:38:58][75]Detected OS Distribution: Ubuntu

[08-19-2015T14:38:58][82]Detected OS Version: 14.04

[08-19-2015T14:38:58][100]Logged in user: root

[08-19-2015T14:38:58][121]---------------------------------------------------------------------------------

[08-19-2015T14:39:00][123]---------------------------------------------------------------------------------

[08-19-2015T14:39:02][1095]EULA accepted, proceeding with console mode installation

[08-19-2015T14:39:02][1108]AMD APP SDK v3.0-0-Beta will be installed for all users.

[08-19-2015T14:39:02][1129]USERMODE_INSTALL: 0. (0: root user; 1: non-root user

[08-19-2015T14:39:02][1134]Prompting user for selecting the Installation Directory. Default is /opt

[08-19-2015T14:39:04][210,]You have chosen to install AMD APP SDK v3.0-0-Beta in directory: /opt/AMDAPPSDK-3.0-0-Beta

[08-19-2015T14:39:04][155]Installing to /opt/AMDAPPSDK-3.0-0-Beta.

cp: ‘./APPSDK-EULA-linux.txt’ and ‘/opt/AMDAPPSDK-3.0-0-Beta/APPSDK-EULA-linux.txt’ are the same file

cp: ‘./bin’ and ‘/opt/AMDAPPSDK-3.0-0-Beta/bin’ are the same file

cp: ‘./docs’ and ‘/opt/AMDAPPSDK-3.0-0-Beta/docs’ are the same file

cp: ‘./include’ and ‘/opt/AMDAPPSDK-3.0-0-Beta/include’ are the same file

cp: ‘./install.sh’ and ‘/opt/AMDAPPSDK-3.0-0-Beta/install.sh’ are the same file

cp: ‘./lib’ and ‘/opt/AMDAPPSDK-3.0-0-Beta/lib’ are the same file

cp: ‘./samples’ and ‘/opt/AMDAPPSDK-3.0-0-Beta/samples’ are the same file

cp: ‘./shflags’ and ‘/opt/AMDAPPSDK-3.0-0-Beta/shflags’ are the same file

cp: ‘./uninstall.sh’ and ‘/opt/AMDAPPSDK-3.0-0-Beta/uninstall.sh’ are the same file

[08-19-2015T14:39:04][166]Failed to install files in the /opt/AMDAPPSDK-3.0-0-Beta directory.

[08-19-2015T14:39:04][1151]Failed to install AMD APP SDK v3.0-0-Beta to /opt/AMDAPPSDK-3.0-0-Beta. The installation cannot continue.

0 Likes
1 Solution
natasha
Elite

Dear Wade,

Excuse me please if my comment is stupid.

On my machine there is

...

‘./APPSDK-EULA-linux.txt’ -> ‘/opt/AMDAPPSDK-3.0-0-Beta/APPSDK-EULA-linux.txt’

‘./bin’ -> ‘/opt/AMDAPPSDK-3.0-0-Beta/bin’

...

instead of your

...

cp: ‘./APPSDK-EULA-linux.txt’ and ‘/opt/AMDAPPSDK-3.0-0-Beta/APPSDK-EULA-linux.txt’ are the same file

cp: ‘./bin’ and ‘/opt/AMDAPPSDK-3.0-0-Beta/bin’ are the same file

...

It seems that your source files for SDK are in /opt/AMDAPPSDK-3.0-0-Beta folder (the same source and destination directories), aren't they?

In my case, SDK was installed from separate directory in /home.

View solution in original post

9 Replies
jtrudeau
Staff

Welcome! I am going to move this to the OpenCL forum in DevGurus. I have white listed you as a developer, even if you are not and are downloading the SDK for some other reason. That's the location where you can probably get the most effective help.

As a whitelisted developer, you can post anywhere in DevGurus, so you can follow this thread and respond there.

Yes, please. Thank you very much for your kind help. BTW, I am trying to test the OpenCL 2.0 samples provided by your company.

0 Likes
natasha
Elite

Dear Wade,

Excuse me please if my comment is stupid.

On my machine there is

...

‘./APPSDK-EULA-linux.txt’ -> ‘/opt/AMDAPPSDK-3.0-0-Beta/APPSDK-EULA-linux.txt’

‘./bin’ -> ‘/opt/AMDAPPSDK-3.0-0-Beta/bin’

...

instead of your

...

cp: ‘./APPSDK-EULA-linux.txt’ and ‘/opt/AMDAPPSDK-3.0-0-Beta/APPSDK-EULA-linux.txt’ are the same file

cp: ‘./bin’ and ‘/opt/AMDAPPSDK-3.0-0-Beta/bin’ are the same file

...

It seems that your source files for SDK are in /opt/AMDAPPSDK-3.0-0-Beta folder (the same source and destination directories), aren't they?

In my case, SDK was installed from separate directory in /home.

wadesyu​, natasha​,

If you are installing the APP SDK as a non-root user, then the default installation directory would be $HOME, for root-mode the default directory would be /opt.

wadesyu​: Did you by any chance extract the contents of the self-extracting shell script. i.e., the APP SDK Linux Installer script? or do you already have the APP SDK 3.0 Beta installed in the /opt/ directory?

munsingh natasha,

Hi, thank you for the reply. I did install the APP SDK 3.0 Beta in the /opt/ directory. However, I tried to install the APP SDK 3.0 Beta under the non-root user and the APP SDK 3.0 was successfully installed.

0 Likes

Hi, thank you for the suggestion. The overlapping of these files may be the problem. I have installed the SDK 3.0 under the non-root user, and the directories are separated.

0 Likes
wadesyu
Adept I

Hi,

Though the APP SDK 3.0 Beta has been successfully installed, some of the samples(based on OpenCL 2.0) couldn't work well. I've try to execute the PipeProducerConsumerKernel but is showed the following error message(in the directory '/AMDAPPSDK-3.0-0-Beta/samples/opencl/bin/x86_64'). Any suggestions would be highly appreciated!

pastedImage_0.png

0 Likes

OpenCL 2.0 samples like PipeProducerConsumerKernel require OpenCL 2.0 supported device and driver. Did you install the required catalyst driver? After installing the driver, clinfo should report the corresponding GPU as OpenCL 2.0 supported device. Please check the clinfo output.

Hi, thank you for the suggestion and I am sorry for the late reply. It's indeed the catalyst driver that caused the problem. I am trying to update the driver and I will report the result later on. Thank you!

0 Likes