Welcome to MilkyWay@home

ATI GPU R600 (R38xx) does not support OpenCL

Message boards : Number crunching : ATI GPU R600 (R38xx) does not support OpenCL
Message board moderation

To post messages, you must log in.

Previous · 1 · 2

AuthorMessage
Floyd

Send message
Joined: 2 Dec 10
Posts: 12
Credit: 107,787,192
RAC: 0
Message 62774 - Posted: 4 Dec 2014, 14:46:14 UTC - in response to Message 62739.  
Last modified: 4 Dec 2014, 14:49:12 UTC

I am yet another poor soul trying to contribute effort using an R9 290X in a Windoze 7 rig.

Tried your app_info (thanks), but I'm getting an error about:-

"File referenced in app_info.xml does not exist: milkyway_separation_1.20_windows_x86_64__opencl_amd_ati.exe"


Do I need to download this EXE manually? If so, where from?

Before I inserted the app_info file, I had the following installed:-

Boinc 7.4.27 (x64)
Catalyst 14.301
AMD APP SDK 2.9-1

I am also bizarrely gettting a message:-

"app version refers to missing GPU type NVIDIA"

I am hoping there is a simple answer (maybe the sysadmins can fix the project itself?).

Any ideas?
ID: 62774 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Floyd

Send message
Joined: 2 Dec 10
Posts: 12
Credit: 107,787,192
RAC: 0
Message 62775 - Posted: 4 Dec 2014, 15:32:26 UTC - in response to Message 62774.  

Update:-

I found the following EXE files on another machine running MW@H:-

milkyway_separation__modified_fit_1.32_windows_x86_64__opencl_amd_ati
milkyway_separation__modified_fit_1.36_windows_x86_64__opencl_ati_101
milkyway_separation_1.02_windows_x86_64__ati14
milkyway_separation_1.02_windows_x86_64__opencl_amd_ati

and the client is now running tasks.

However, the task names are preceded by "Local".

Am I storing up problems for when the applications are updated/replaced?
ID: 62775 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Ryan Munro

Send message
Joined: 22 Jun 09
Posts: 13
Credit: 74,878,564
RAC: 22,312
Message 62776 - Posted: 4 Dec 2014, 16:23:45 UTC

I am having this issue as well, is there a working solution?
ID: 62776 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile arkayn
Avatar

Send message
Joined: 14 Feb 09
Posts: 999
Credit: 74,932,619
RAC: 0
Message 62777 - Posted: 4 Dec 2014, 18:04:33 UTC - in response to Message 62774.  

I am yet another poor soul trying to contribute effort using an R9 290X in a Windoze 7 rig.

Tried your app_info (thanks), but I'm getting an error about:-

"File referenced in app_info.xml does not exist: milkyway_separation_1.20_windows_x86_64__opencl_amd_ati.exe"


Do I need to download this EXE manually? If so, where from?

Before I inserted the app_info file, I had the following installed:-

Boinc 7.4.27 (x64)
Catalyst 14.301
AMD APP SDK 2.9-1

I am also bizarrely gettting a message:-

"app version refers to missing GPU type NVIDIA"

I am hoping there is a simple answer (maybe the sysadmins can fix the project itself?).

Any ideas?


http://milkyway.cs.rpi.edu/milkyway/download/milkyway_separation_1.20_windows_x86_64__opencl_amd_ati.exe

Since there is no instance of NVIDIA in that app_info, it might be coming from another project.
ID: 62777 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Floyd

Send message
Joined: 2 Dec 10
Posts: 12
Credit: 107,787,192
RAC: 0
Message 62778 - Posted: 4 Dec 2014, 19:04:07 UTC - in response to Message 62777.  

Thanks for the download link, but I have already located a copy on a sister machine. My problems have moved on a little since then.

I have discovered that your app_info is coded for two of the four available applications. I have disabled the unconfigured applications in my profile until I can resolve the issue, either by the sysadmins fixing the generic problem or by using an app_info which covers all four applications.

Are you able/willing to supply a comprehensive app_info - I would have a go myself, but there are parameters in there that I have no idea what they are for.

I have also now discovered that the client does not seem willing to update to the server automatically on a frequent-enough schedule to keep the cache flowing. The sister machine seems to run a scheduler every 60 seconds, clearing completed tasks and requesting new ones, but this new installation doesn't seem to run any automatic scheduler.

Is that configured (or missing) in the app_info?
ID: 62778 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile arkayn
Avatar

Send message
Joined: 14 Feb 09
Posts: 999
Credit: 74,932,619
RAC: 0
Message 62779 - Posted: 4 Dec 2014, 20:33:47 UTC - in response to Message 62778.  
Last modified: 4 Dec 2014, 20:34:51 UTC

Thanks for the download link, but I have already located a copy on a sister machine. My problems have moved on a little since then.

I have discovered that your app_info is coded for two of the four available applications. I have disabled the unconfigured applications in my profile until I can resolve the issue, either by the sysadmins fixing the generic problem or by using an app_info which covers all four applications.

Are you able/willing to supply a comprehensive app_info - I would have a go myself, but there are parameters in there that I have no idea what they are for.

I have also now discovered that the client does not seem willing to update to the server automatically on a frequent-enough schedule to keep the cache flowing. The sister machine seems to run a scheduler every 60 seconds, clearing completed tasks and requesting new ones, but this new installation doesn't seem to run any automatic scheduler.

Is that configured (or missing) in the app_info?


Contact rate is set by the cache settings that you use.

This should be the CPU app version of Milkyway.


<file_info>
<name>milkyway_separation_1.20_windows_x86_64.exe</name>
<executable />
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>120</version_num>
<file_ref>
<file_name>milkyway_separation_1.20_windows_x86_64.exe</file_name>
<main_program/>
</file_ref>
</app_version>

<file_info>
<name>milkyway_separation__modified_fit_1.36_windows_x86_64.exe</name>
<executable />
</file_info>
<app_version>
<app_name>milkyway_separation__modified_fit</app_name>
<version_num>136</version_num>
<file_ref>
<file_name>milkyway_separation__modified_fit_1.36_windows_x86_64.exe</file_name>
<main_program/>
</file_ref>
</app_version>

Paste them below the ATI versions that are already there.

<app_info>
<app>
<name>milkyway_separation__modified_fit</name>
</app>
<file_info>
<name>milkyway_separation__modified_fit_1.36_windows_x86_64__opencl_ati_101.exe</name>
<executable />
</file_info>
<app_version>
<app_name>milkyway_separation__modified_fit</app_name>
<version_num>136</version_num>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.567833</max_ncpus>
<plan_class>opencl_ati_101</plan_class>
<file_ref>
<file_name>milkyway_separation__modified_fit_1.36_windows_x86_64__opencl_ati_101.exe</file_name>
<main_program/>
</file_ref>
<coproc>
<type>ATI</type>
<count>1.0000</count>
</coproc>
</app_version>
<file_info>
<name>milkyway_separation__modified_fit_1.36_windows_x86_64.exe</name>
<executable />
</file_info>
<app_version>
<app_name>milkyway_separation__modified_fit</app_name>
<version_num>136</version_num>
<file_ref>
<file_name>milkyway_separation__modified_fit_1.36_windows_x86_64.exe</file_name>
<main_program/>
</file_ref>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>milkyway_separation_1.20_windows_x86_64__opencl_amd_ati.exe</name>
<executable />
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>120</version_num>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.567833</max_ncpus>
<plan_class>opencl_ati</plan_class>
<file_ref>
<file_name>milkyway_separation_1.20_windows_x86_64__opencl_amd_ati.exe</file_name>
<main_program/>
</file_ref>
<coproc>
<type>ATI</type>
<count>1.0000</count>
</coproc>
</app_version>
<file_info>
<name>milkyway_separation_1.20_windows_x86_64.exe</name>
<executable />
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>120</version_num>
<file_ref>
<file_name>milkyway_separation_1.20_windows_x86_64.exe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>

If you want NBODY, I cannot help you on that one.
ID: 62779 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Floyd

Send message
Joined: 2 Dec 10
Posts: 12
Credit: 107,787,192
RAC: 0
Message 62781 - Posted: 4 Dec 2014, 21:10:19 UTC - in response to Message 62779.  

Thanks for the download link, but I have already located a copy on a sister machine. My problems have moved on a little since then.

I have discovered that your app_info is coded for two of the four available applications. I have disabled the unconfigured applications in my profile until I can resolve the issue, either by the sysadmins fixing the generic problem or by using an app_info which covers all four applications.

Are you able/willing to supply a comprehensive app_info - I would have a go myself, but there are parameters in there that I have no idea what they are for.

I have also now discovered that the client does not seem willing to update to the server automatically on a frequent-enough schedule to keep the cache flowing. The sister machine seems to run a scheduler every 60 seconds, clearing completed tasks and requesting new ones, but this new installation doesn't seem to run any automatic scheduler.

Is that configured (or missing) in the app_info?


Contact rate is set by the cache settings that you use.

This should be the CPU app version of Milkyway.


<file_info>
<name>milkyway_separation_1.20_windows_x86_64.exe</name>
<executable />
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>120</version_num>
<file_ref>
<file_name>milkyway_separation_1.20_windows_x86_64.exe</file_name>
<main_program/>
</file_ref>
</app_version>

<file_info>
<name>milkyway_separation__modified_fit_1.36_windows_x86_64.exe</name>
<executable />
</file_info>
<app_version>
<app_name>milkyway_separation__modified_fit</app_name>
<version_num>136</version_num>
<file_ref>
<file_name>milkyway_separation__modified_fit_1.36_windows_x86_64.exe</file_name>
<main_program/>
</file_ref>
</app_version>

Paste them below the ATI versions that are already there.

<app_info>
<app>
<name>milkyway_separation__modified_fit</name>
</app>
<file_info>
<name>milkyway_separation__modified_fit_1.36_windows_x86_64__opencl_ati_101.exe</name>
<executable />
</file_info>
<app_version>
<app_name>milkyway_separation__modified_fit</app_name>
<version_num>136</version_num>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.567833</max_ncpus>
<plan_class>opencl_ati_101</plan_class>
<file_ref>
<file_name>milkyway_separation__modified_fit_1.36_windows_x86_64__opencl_ati_101.exe</file_name>
<main_program/>
</file_ref>
<coproc>
<type>ATI</type>
<count>1.0000</count>
</coproc>
</app_version>
<file_info>
<name>milkyway_separation__modified_fit_1.36_windows_x86_64.exe</name>
<executable />
</file_info>
<app_version>
<app_name>milkyway_separation__modified_fit</app_name>
<version_num>136</version_num>
<file_ref>
<file_name>milkyway_separation__modified_fit_1.36_windows_x86_64.exe</file_name>
<main_program/>
</file_ref>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>milkyway_separation_1.20_windows_x86_64__opencl_amd_ati.exe</name>
<executable />
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>120</version_num>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.567833</max_ncpus>
<plan_class>opencl_ati</plan_class>
<file_ref>
<file_name>milkyway_separation_1.20_windows_x86_64__opencl_amd_ati.exe</file_name>
<main_program/>
</file_ref>
<coproc>
<type>ATI</type>
<count>1.0000</count>
</coproc>
</app_version>
<file_info>
<name>milkyway_separation_1.20_windows_x86_64.exe</name>
<executable />
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>120</version_num>
<file_ref>
<file_name>milkyway_separation_1.20_windows_x86_64.exe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>

If you want NBODY, I cannot help you on that one.



NBODY is one of the two unconfigured applications. The other is MilkyWay@Home (you have given me the two "Separation" applications).

I am dedicating the CPU processing to a different project (WCG) so do not need the CPU aspect of MW@H.

I have been fiddling with settings trying to sort out conflicting global settings with project-specific ones and think I have finally got the cache setting right to keep up the MW@H feed.

I guess I can live with my new status quo until the general problem is sorted centrally.

Thanks very much for your help.
ID: 62781 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile arkayn
Avatar

Send message
Joined: 14 Feb 09
Posts: 999
Credit: 74,932,619
RAC: 0
Message 62784 - Posted: 5 Dec 2014, 6:22:25 UTC - in response to Message 62781.  

Thanks for the download link, but I have already located a copy on a sister machine. My problems have moved on a little since then.

I have discovered that your app_info is coded for two of the four available applications. I have disabled the unconfigured applications in my profile until I can resolve the issue, either by the sysadmins fixing the generic problem or by using an app_info which covers all four applications.

Are you able/willing to supply a comprehensive app_info - I would have a go myself, but there are parameters in there that I have no idea what they are for.

I have also now discovered that the client does not seem willing to update to the server automatically on a frequent-enough schedule to keep the cache flowing. The sister machine seems to run a scheduler every 60 seconds, clearing completed tasks and requesting new ones, but this new installation doesn't seem to run any automatic scheduler.

Is that configured (or missing) in the app_info?


Contact rate is set by the cache settings that you use.

This should be the CPU app version of Milkyway.


<file_info>
<name>milkyway_separation_1.20_windows_x86_64.exe</name>
<executable />
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>120</version_num>
<file_ref>
<file_name>milkyway_separation_1.20_windows_x86_64.exe</file_name>
<main_program/>
</file_ref>
</app_version>

<file_info>
<name>milkyway_separation__modified_fit_1.36_windows_x86_64.exe</name>
<executable />
</file_info>
<app_version>
<app_name>milkyway_separation__modified_fit</app_name>
<version_num>136</version_num>
<file_ref>
<file_name>milkyway_separation__modified_fit_1.36_windows_x86_64.exe</file_name>
<main_program/>
</file_ref>
</app_version>

Paste them below the ATI versions that are already there.

<app_info>
<app>
<name>milkyway_separation__modified_fit</name>
</app>
<file_info>
<name>milkyway_separation__modified_fit_1.36_windows_x86_64__opencl_ati_101.exe</name>
<executable />
</file_info>
<app_version>
<app_name>milkyway_separation__modified_fit</app_name>
<version_num>136</version_num>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.567833</max_ncpus>
<plan_class>opencl_ati_101</plan_class>
<file_ref>
<file_name>milkyway_separation__modified_fit_1.36_windows_x86_64__opencl_ati_101.exe</file_name>
<main_program/>
</file_ref>
<coproc>
<type>ATI</type>
<count>1.0000</count>
</coproc>
</app_version>
<file_info>
<name>milkyway_separation__modified_fit_1.36_windows_x86_64.exe</name>
<executable />
</file_info>
<app_version>
<app_name>milkyway_separation__modified_fit</app_name>
<version_num>136</version_num>
<file_ref>
<file_name>milkyway_separation__modified_fit_1.36_windows_x86_64.exe</file_name>
<main_program/>
</file_ref>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>milkyway_separation_1.20_windows_x86_64__opencl_amd_ati.exe</name>
<executable />
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>120</version_num>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.567833</max_ncpus>
<plan_class>opencl_ati</plan_class>
<file_ref>
<file_name>milkyway_separation_1.20_windows_x86_64__opencl_amd_ati.exe</file_name>
<main_program/>
</file_ref>
<coproc>
<type>ATI</type>
<count>1.0000</count>
</coproc>
</app_version>
<file_info>
<name>milkyway_separation_1.20_windows_x86_64.exe</name>
<executable />
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>120</version_num>
<file_ref>
<file_name>milkyway_separation_1.20_windows_x86_64.exe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>

If you want NBODY, I cannot help you on that one.



NBODY is one of the two unconfigured applications. The other is MilkyWay@Home (you have given me the two "Separation" applications).

I am dedicating the CPU processing to a different project (WCG) so do not need the CPU aspect of MW@H.

I have been fiddling with settings trying to sort out conflicting global settings with project-specific ones and think I have finally got the cache setting right to keep up the MW@H feed.

I guess I can live with my new status quo until the general problem is sorted centrally.

Thanks very much for your help.


The 1.20 Seperation app is Milkyway@home now, they do not release work for the older versions.
ID: 62784 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Previous · 1 · 2

Message boards : Number crunching : ATI GPU R600 (R38xx) does not support OpenCL

©2024 Astroinformatics Group