@ Matt - do you have a link for the download or will it download automatically as a stock app?

-Mike
____________

I just installed it on my GTX460 host and will see what it does on there.
http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=179088
____________

Just tried to run that version on my GTX260.
But I only get WUs that error out immediately like this one.
Do I need something else for it to run?
____________
Member of BOINC@Heidelberg and ATA!

My BOINCstats

I just downloaded and installed it. Fails immediate. Is there anything more to do?
win7-64, nVidia 460. Forceware 259.19, BM 6.10.58
Alexander

Hello,

Me it works, for cons I see only one unit in my stats that are validated and any error in or pending?!

when I returned well over a ....
____________
Team Alliance francophone, boinc: 7.0.18

GA-P55-UD5, i7 860, Win 7 64 bits, 8g DDR3, GTX 470

Thanks a lot, Matt :-) I'll try it later 2day on ubuntu x64.
____________

If I remember correctly, you will need at least a 26x.00 driver to use the openCL app.

Upgrade to the newest and see if it runs correctly.
____________

BTW, Matt, can I run OpenCL app on GTX275 and which driver's and CUDA versions I need? I've got 195.30 and cuda 2.3
____________

If I remember correctly, you will need at least a 26x.00 driver to use the openCL app.

Upgrade to the newest and see if it runs correctly.

BTW, Matt, can I run OpenCL app on GTX275 and which driver's and CUDA versions I need? I've got 195.30 and cuda 2.3

Thansk, guys :-)

The only thing - I tested that on GPUGRID and there cuda 2.3 is way faster then codu 3.0 and just faster then 3.1... But NP, I'll try latest drivers...
____________

ok, I understand - I have to move to CUDA 3.0 at least.

The latest driver (260.19.21) is on CUDA 3.2, so I think it's necessary to get cudatoolkit 3.2 from here
____________

Why in the stats on the project account, the stats of these test units do not stay posted?
____________
Team Alliance francophone, boinc: 7.0.18

GA-P55-UD5, i7 860, Win 7 64 bits, 8g DDR3, GTX 470

If I remember correctly, you will need at least a 26x.00 driver to use the openCL app.

The WUs are running fine now. :-)

Here is the stderr that came up on my 460.

615 secs??? wow... even if u run 2 WUs concurrent, it too much. my 4870 run it in 325 secs and 4890 in 312 secs. but taking in consideration dp cropped by nvidia in fermi cards...

But anyway I'll try it on GTX275
____________

Yes I know, my 5830 runs the same type of unit in 130 seconds.
____________

So, there is room for improvement :-)
____________

So, there is some room for inprovement :-)

The theoretical performance of doubles on ATI hardware is much higher than on Nvidia, so it's not expected to match that. It's expected to be about the same or marginally faster than the old CUDA application.

yep, agree. dp is 1/8 of sp instead of 1/2... so, there are no changes in my plans to get pair of 6970 :-)

when u plan to release OpenCL app for Ati? :-)
____________

I have now a couple of wu's finished.
11min 34sec is a typical time for de_separation_16_3s_fix_1_1137162_...
GTX460 @ 715MHz, win7-64, E8400, BM 6.10.58, Forceware 260.99
GPU-Usage ~98%, Mem usage 255MB (Afterburner)
No invalid or errors logged (but they don't stay long..)

I have tested the new OpenCL app with a Geforce GT 420m notebook GPU.

When I used Crunch3er's optimized app in the past, my work units took either 49 or 73 minutes to complete. With the new OpenCL app, work units need either 51 or 75 minutes to complete. I do not know why the new app is actually a bit slower, maybe it is because I was surfing on the web and displaying some images while running the work units? (though simple tasks like this never seemed to affect the work units of the old app by Crunch3er)

Furthermore, there is a significant difference in system responsiveness and a slight difference in GPU temperature between the two apps.

While Crunch3er's app did not cause any negative effects regarding system responsiveness, the new OpenCL app causes the system to react very sluggishly, so that comfortably writing something or surfing the web is not possible anymore.

Lastly, GPU temperature with the OpenCL app is about 3 degrees celsius higher than with Crunch3er's app. That is why I have now switched back to the old app for the time being.

I hope my information gathered about the performance of the new app is helpful.

Matt,

I followed the link above to extract the tar file into the MW sub-dir under boinc-client on /var however I am still getting the exact same error message about the app not finding a double-precision card even though it accurately identifies the Fermi. I'm on 64-bit Ubuntu.

In addition, all of the WU's are id'd as cuda 23 units, there is no mention in the error message or in the WU log of Open CL.

I notice that in the app_info.xml it refers to:

<file_info>
<name>milkyway_separation_0.48_x86_64-pc-linux-gnu__cuda_opencl</name>
<executable/>
</file_info>

However, there is no such file. The only executable that it unpacked was:
milkyway_0.24_x86_64-pc-linux-gnu__cuda23

Also, does:
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>

refer to the number of processors or to its ID number? Mine always comes up as GPU0 which is why I ask.

Thanks,
Steve

Hi,
I´m new to milkyway@home, so I don´t know exactly how long the WUs took with the CUDA App, but here are the numbers for the new opencl app.

Boinc 6.10.58, E6750@3.2GHz, GTX 260-216, driver 260.99, vista 64

1,689.29 sec 320.63 credits
914.38 sec 213.76 credits
960.59 sec 213.76 credits

GPU usage @ ~90%

Matt,

Thanks for the feedback. I see where I wasn't the owner for some of the files.

I think that I've caught all of them.

It sounds like I should purge the WU's in progress and re-extract the tar?

Thanks,
Steve

Sorry to go a bit off topic, but will the ATi OpenCL version come out soon?

I'm taking part in some cpu-based projects (like climateprediction.net and yoyo@home) and was looking for another project to run on my gpu (besides SETI). In the past milkyway told me that my gpu was lacking memory so i thought that maybe the OpenCL version would run. After installing the package and updating my NVIDIA driver to 260.99 I was happy to get some WUs - but they all ended up with "calculating error". - Okay, let's do it step by step... So at first I've updated Boinc to 6.10.58. Now milkyway says at start-up "Message from server: Your app_info.xml file doesn't have a version of MilkyWay@Home N-Body Simulation."

Hmmh, what does that tell me? Did I make any mistake? Or do I need the formerly mentioned 3.2 cudatoolkit from that guy "Crunch3er"? Any help is appreciated!

By the way: GeForce 8800 GTS (driver 26099, CUDA version 3020, compute capability 1.0).

Greetings from Germany,
Axel

P.S.: Bad English? Maybe that's because I've left school 25 years ago...

app_info essayez avec ce fichier:

<app_info>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>milkyway_0.45_windows_x86_64.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>45</version_num>
<file_ref>
<file_name>milkyway_0.45_windows_x86_64.exe</file_name>
<main_program/>
</file_ref>
</app_version>

<app>
<name>milkyway_nbody</name>
<user_friendly_name>MilkyWay@Home nbody Simulation</user_friendly_name>
</app>
<file_info>
<name>milkyway_nbody_0.21_windows_x86_64__sse2.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway_nbody</app_name>
<version_num>21</version_num>
<file_ref>
<file_name>milkyway_nbody_0.21_windows_x86_64__sse2.exe</file_name>
<main_program/>
</file_ref>
</app_version>

<app>
<name>milkyway</name>
<user_friendly_name>Milkyway@home Separation</user_friendly_name>
</app>
<file_info>
<name>milkyway_separation_0.48_windows_intelx86__cuda_opencl.exe</name>
<executable/>
</file_info>

<app_version>
<app_name>milkyway</app_name>
<version_num>47</version_num>
<plan_class>cuda_opencl</plan_class>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>0.05</max_ncpus>
<flops>1.0e11</flops>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>milkyway_separation_0.48_windows_intelx86__cuda_opencl.exe</file_name>
<main_program/>
</file_ref>
</app_version>

<app>
<name>milkyway</name>
</app>
<file_info>
<name>milkyway_windows_intelx86__cuda23.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart.dll</name>
<executable/>
</file_info>
<file_info>
<name>cutil32.dll</name>
<executable/>
</file_info>

<app_version>
<app_name>milkyway</app_name>
<version_num>24</version_num>
<plan_class>cuda23</plan_class>
<flops>1.0e11</flops>
<avg_ncpus>0.1</avg_ncpus>
<max_ncpus>0.1</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1.0</count>
</coproc>
<cmdline></cmdline>
<file_ref>
<file_name>milkyway_windows_intelx86__cuda23.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cutil32.dll</file_name>
</file_ref>
</app_version>

</app_info>
____________
Team Alliance francophone, boinc: 7.0.18

GA-P55-UD5, i7 860, Win 7 64 bits, 8g DDR3, GTX 470

By the way: GeForce 8800 GTS (driver 26099, CUDA version 3020, compute capability 1.0).

That GPU doesn't have doubles and won't work. It needs at least compute capability 1.3.

Is anyone running it in a system with both ATI and Nvidia drivers installed? I just realized a hypothetical problem that might happen.

By the way: GeForce 8800 GTS (driver 26099, CUDA version 3020, compute capability 1.0).

That GPU doesn't have doubles and won't work. It needs at least compute capability 1.3.

Thanks for the information! But why did milkyway sent me any WUs then?

If you tried manually installing this, it will try sending the workunits to it. You shouldn't get sent the Nvidia applications since you don't have doubles.

OK Matt, if you're still interested, your new app takes a little over 17 minutes to complete 1 opencl wu. This is with Seti@Home working on both cpus (e6600@2.4GHz) with Folding@home working also. Windows XP32, Nvidia driver 206.63.

Palit GeForce GTS 450 (Fermi) Sonic Platinum 1GB

What updates? an updated application?
____________
Team Alliance francophone, boinc: 7.0.18

GA-P55-UD5, i7 860, Win 7 64 bits, 8g DDR3, GTX 470

ok, thank you but I did not understand what the minor updates of the application?
____________
Team Alliance francophone, boinc: 7.0.18

GA-P55-UD5, i7 860, Win 7 64 bits, 8g DDR3, GTX 470

With 48.0 I found that the runtimes are over 2m longer than with the CUDA app on my GTX260. 15:40 - 16:00 for OpenCL and 13:22 - 13:31 for CUDA.

The memory bandwith used on the card is up to about 50% as well which is a HUGE jump from CUDA (0%). As well as having a larger system memory footprint. Just found that interesting, it doesn't particularly concern me.

And it also uses more CPU time than the CUDA app, though I didn't notice the cpu being used while I was watching the task manager. Does it use most / all of the cycles at the start or end of the WU or something?
____________

Matt,

I downloaded the WU's all today and within about an hour of each other. I did 4 OpenCL then 3 CUDA before posting and another few CUDA after posting (With the same type of run time seen).

The memory bandwith usage struck me as odd as well which is why I posted it. I was running GPU-z to watch what was going on a bit to make sure it wasn't say using 50% of the GPU core or something and noticed that the "Memory Controller Load" was reading at 50% or over. I've only ever seen that with SETI before.

I'll give a try with 48.1 and see if anything different happens. If there is some kind of test WU I can run through the command line or the like to help you out any, I'd be more than willing to do it.
____________

After I posted the last one I figured you would need more details since the deleter is deleting things right away. (Looks like I was right) So I went about getting them for you.

One other thing I noticed on my system is that the OpenCL tasks sit at 100% with the clock still going for about 30s.

I'll PM you with all the info so I don't make a huge post full of data useless to anyone but you and Travis.
____________

Matt,

I wanted to give you an update on my use of the OpenCL app.

To re-cap, I'm running 64-bit Ubuntu 10.10 on an AMD quad-core with 8GB of DDR2 RAM and a GTX460 Fermi card with the latest Nvidia driver from their website.

1. Simply extracting the tar to the top-level MW folder did not work since the executable that it put there was for cuda23, not Open CL. The WU's continued to be retrieved as cuda23 WU's and the completed one's continued to fail validation.

2. Having noticed the app.xml and correct executable had been extracted into a sub-folder in the MW main folder, I first moved them to another non-MW folder and then copied the contents into the main MW folder with the rest of the extracted files.

3. I then deleted the cuda23 executable.

4. Based on discussion at Collatz, I copied libcudart32_23.so into the MW folder.

5. I suspended the WU's and exited Boinc Manager.

6. I then opened a terminal window as root and typed "service boinc-client restart" [Enter] and closed the terminal window.

7. I re-started Boinc Manager and the apps and quickly saw work units id's as "open_cl" work units along with the notation that they were using 0.5CPU and 1.0 GPU. The WU's so far have taken about 15-20 min. to process vs. a few hours before.

6. However, at first,the WU's were coming back the message "completed, validation inconclusive". Since then, it has changed to "Successful" so I guess I'm ok.

Here is the stderr_text for one of them.
Task 263496737

Name de_separation_17_3s_fix_1_1719797_1291478684_1
Workunit 198514068
Created 4 Dec 2010 16:09:29 UTC
Sent 4 Dec 2010 16:10:24 UTC
Received 4 Dec 2010 19:06:06 UTC
Server state Over
Outcome Success
Client state Done
Exit status 0 (0x0)
Computer ID 228451
Report deadline 12 Dec 2010 16:10:24 UTC
Run time 1519.988412
CPU time 8.83
stderr out

<core_client_version>6.10.58</core_client_version>
<![CDATA[
<stderr_txt>
<search_application> milkywayathome separation 0.48 Linux x86_64 double OpenCL </search_application>
Found 1 platforms
Platform 0 information:
Platform name: NVIDIA CUDA
Platform version: OpenCL 1.0 CUDA 3.2.1
Platform vendor:
Platform profile:
Platform extensions: cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll
Using device 0 on platform 0
Found 1 CL devices
Device GeForce GTX 460 (NVIDIA Corporation:0x10de)
Type: CL_DEVICE_TYPE_GPU
Driver version: 260.19.21
Version: OpenCL 1.0 CUDA
Compute capability: 2.1
Little endian: CL_TRUE
Error correction: CL_FALSE
Image support: CL_TRUE
Address bits: 32
Max compute units: 7
Clock frequency: 1502 Mhz
Global mem size: 804454400
Max mem alloc: 201113600
Global mem cache: 114688
Cacheline size: 128
Local mem type: CL_LOCAL
Local mem size: 49152
Max const args: 9
Max const buf size: 65536
Max parameter size: 4352
Max work group size: 1024
Max work item dim: 3
Max work item sizes: { 1024, 1024, 64 }
Mem base addr align: 4096
Min type align size: 128
Timer resolution: 1000 ns
Double extension: MW_CL_KHR_FP64
Extensions: cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64

Compiler flags:
-cl-mad-enable -cl-no-signed-zeros -cl-strict-aliasing -cl-finite-math-only -DUSE_CL_MATH_TYPES=0 -DUSE_MAD=0 -DUSE_FMA=0 -cl-nv-verbose -DDOUBLEPREC=1 -DMILKYWAY_MATH_COMPILATION -DNSTREAM=3 -DFAST_H_PROB=1 -DAUX_BG_PROFILE=0 -DUSE_IMAGES=1 -DI_DONT_KNOW_WHY_THIS_DOESNT_WORK_HERE=1

Build status: CL_BUILD_SUCCESS
Build log:

: Considering profile 'compute_20' for gpu='sm_21' in 'cuModuleLoadDataEx_4'
Kernel work group info:
Work group size = 512
Kernel local mem size = 0
Compile work group size = { 0, 0, 0 }
Lower n solution: n = 40, x = 0
Higher n solution: n = 40, x = 0
Using solution: n = 40, x = 0
Range: { nu_steps = 640, mu_steps = 1600, r_steps = 1400 }
Iteration area: 2240000
Chunk estimate: 40
Num chunks: 40
Added area: 0
Effective area: 2240000
Integration time: 795.240523 s. Average time per iteration = 1242.563318 ms
Kernel work group info:
Work group size = 512
Kernel local mem size = 0
Compile work group size = { 0, 0, 0 }
Lower n solution: n = 38, x = 1792
Higher n solution: n = 50, x = 0
Using solution: n = 38, x = 1792
Range: { nu_steps = 640, mu_steps = 400, r_steps = 1400 }
Iteration area: 560000
Chunk estimate: 40
Num chunks: 38
Added area: 1792
Effective area: 561792
Integration time: 343.485032 s. Average time per iteration = 536.695363 ms
Kernel work group info:
Work group size = 512
Kernel local mem size = 0
Compile work group size = { 0, 0, 0 }
Lower n solution: n = 38, x = 1792
Higher n solution: n = 50, x = 0
Using solution: n = 38, x = 1792
Range: { nu_steps = 640, mu_steps = 400, r_steps = 1400 }
Iteration area: 560000
Chunk estimate: 40
Num chunks: 38
Added area: 1792
Effective area: 561792
Integration time: 369.818321 s. Average time per iteration = 577.841126 ms
<background_integral> 0.00049448328945061429 </background_integral>
<stream_integrals> 98.00489805211894633885 736.88664944943548107403 0.00661912358812184829 </stream_integrals>
<background_only_likelihood> -3.28428541304979715321 </background_only_likelihood>
<stream_only_likelihood> -35.67127293699287093887 -4.01220139598113423318 -231.34968260617702640047 </stream_only_likelihood>
<search_likelihood> -3.04403874542270713732 </search_likelihood>
12:51:02 (3471): called boinc_finish

</stderr_txt>
]]>

Validate state Checked, but no consensus yet
Claimed credit 0.0784035175711632
Granted credit 0
application version Anonymous platform

I assume since it's not failing, that it is using the Fermi at the double-precision level.

Sorry for the delay in posting this, the computer quit and it me a couple of days to fix it. Thanks for getting me back in the game.

Regards,
Steve

Big trouble!!

I'm trying now the 0.48.2 and I am having slowdowns my PC that I was not with 0.48.1 ... In addition, the unit does not and this calculation is boosting the temperature of my card ...

GPU load is yet to 99% ... but 0% CPU

I do not think so in this case recalculate these units 0.48.2 ...

I still do not think that just my version of boinc: 6.12.8?
____________
Team Alliance francophone, boinc: 7.0.18

GA-P55-UD5, i7 860, Win 7 64 bits, 8g DDR3, GTX 470

Matt,

The OpenCL setup continues to work like a charm on the first machine.

I've assembled a second machine that is virtually identical. Aside from being an AMD 6 core vs. AMD quad-core and having DDR3 RAM vs. DDR2, they are the same. I even made a point of getting the same model graphics card (MSI Twin-Frozr GTX-460). Both are 64-bit Ubuntu 10.10 and also have the backward compatibility 32-bit libraries. I updated the Nvidia driver, I've matched the permissions with those on the working machine BUTno matter what I do, I cannot get milkyway_separation_0.48_x86_64-pc-linux-gnu__cuda_opencl to run on this machine. The cuda 23 variant keeps re-appearing in the folder and executing. I've tried multiple bulk deletes of the MW folder contents and re-extractions of the OpenCL tar but I always end up with the cuda23 executable reappearing in the folder and taking over.

When I start up Boinc it sees the Fermi card.

As I said earlier, things continue to run like a charm on the first machine and this one is virtually identical. I don't figure out the problem.

Any suggestions? Thanks for any help that you can provide.

Regards,
Steve

You are copying the app_info.xml file as well I hope, that is what tells BOINC what app to use with the project.
____________

Matt,

Yes, indeed.

Here it is.

<app_info>
&#8722;
<app>
<name>milkyway</name>
<user_friendly_name>Milkyway@home Separation</user_friendly_name>
</app>
&#8722;
<file_info>
&#8722;
<name>
milkyway_separation_0.48_x86_64-pc-linux-gnu__cuda_opencl
</name>
<executable/>
</file_info>
&#8722;
<app_version>
<app_name>milkyway</app_name>
<version_num>48</version_num>
<plan_class>cuda_opencl</plan_class>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>0.05</max_ncpus>
<flops>1.0e11</flops>
&#8722;
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
&#8722;
<file_ref>
&#8722;
<file_name>
milkyway_separation_0.48_x86_64-pc-linux-gnu__cuda_opencl
</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>


It appears identical to the one on the first machine.


Here's the body of one of the stderr.txt's from machine #2. Seems like old times!! :)

<core_client_version>6.10.58</core_client_version>
<![CDATA[
<message>
process exited with code 1 (0x1, -255)
</message>
<stderr_txt>
Device index specified on the command line was 0
Looking for a Double Precision capable NVIDIA GPU
The device GeForce GTX 460 from the command line cannot be used because a device supporting compute capability 1.3 (Double Precision) is required
Found 1 CUDA cards
Found a GeForce GTX 460
Device cannot be used, it does not have compute capability 1.3 support
No compute capability 1.3 cards have been found, exiting...

//////
I installed the latest Nvidia driver from their website but am I missing some sort of cuda library file? The last time, it was the installation of the OpenCL app that solved things. I can't figure out why and where the cuda23 executable keeps coming from or gets called for.

But, I think that's symptomatic of it still trying to run cuda23 WU's rather than OpenCL ones. Is there any way to keep the cuda23 executable from returning to the MW folder?

I noticed that the WU's have changed to MilkyWay@Home N-Body Simulation v0.21 (sse2). Maybe the MW server has given up sending me cuda23 WUs?

Regards,
Steve

What are you using to open the .xml files, it almost looks like a browser.

Make sure you are opening them in Gedit instead.

Also try the 48.2 version that is also in the first post of the thread.

The app_info should looks something like this.

It does.

It occurred to me that there are two things that I did last time that I haven't tried yet. I haven't tried re-installing Boinc from a BOINC app site. This installation is from the Ubuntu repository. I did both last time.

The other thing was that I attached to Collatz which I understand has some good cuda libraries included. I remember copying over one of their cuda files the last time.

I'll have to try both later today.

Regards,
Steve

Matt,

After doing a couple of Boinc re-installs and detach/attach's to MW, I think I've spotted the problem on the second machine but I don't know what's causing it or how to fix it.

On the good machine (both are virtually identical including the exact same model GPU card) at the start of the messages on the BOINC Manager it says:

Fri 10 Dec 2010 12:21:13 PM EST NVIDIA GPU 0: GeForce GTX 460 (driver version unknown, CUDA version 3020, compute capability 2.1, 767MB, 673 GFLOPS peak)

Found app_info.xml; using anonymous platform

Fri 10 Dec 2010 12:21:13 PM EST Milkyway@home URL http://milkyway.cs.rpi.edu/milkyway/; Computer ID 243370; resource share 100


But, on the problem machine it is missing the reference line to "app_info.xml; using anonymous platform" at that spot.

Fri 10 Dec 2010 12:21:13 PM EST NVIDIA GPU 0: GeForce GTX 460 (driver version unknown, CUDA version 3020, compute capability 2.1, 767MB, 673 GFLOPS peak)

Fri 10 Dec 2010 12:21:13 PM EST Milkyway@home URL http://milkyway.cs.rpi.edu/milkyway/; Computer ID 243370; resource share 100

I've tried using both the original 48.0 version and the 48.2 but no luck. I just saw your posting about the new version being pushed out by the server and the removal of the cuda version. I'm hoping that will fix things on this second machine.

Regards,
Steve

Matt,

It's there. That's the nice thing about having the working machine right next to it. I've checked everything multiple times.

So, right now, I'm hanging on for the server refresh with the OpenCl version and the removal of the cuda23. I'm hoping that will "force" whatever correction is needed.

Thanks for the suggestions.

Regards,
Steve

Matt,

An update. Everything is now working!

I did an uninstall/re-boot/re-install of the installation from the Ubuntu repository. I did not un-install the manual install from the BOINC site.

I then extracted the last OpenCL tar and deleted the cuda23 executable. Re-started the BOINC-Client and was greeted by the previously openCL config line in the messages. A WU popped up and has the notation that it is using 0.5CPU and 1.0 GPU and is chugging along.

A bonus, is that this has fixed all of the problems on this machine. Previously, all of the other projects on this machine with the exception of Seti were returning bad WU's.

It's been 2 hrs. and I'm now seeing credits for all of the projects for this machine.

I guess there's something that I needed from both installations.

Hooray!

Regards,
Steve