Hi,
I have an Intel Core i7 laptop with an NVidia Quadro 1000M graphics card.
Dual Windows 7 and Ubuntu (recently updated to 14.04).
I am contributing to many projects and on Windows everything goes right, and I think that before the upgrade on Ubuntu too.
Now Ubuntu "Additional drivers" gives me 2 options for NVIDIA:

- version 331.38 from nvidia-331 and
- version 304.117 from nvidia-304.

with the corresponding "updates" choices.
When I choose the first one, I get the following error message for Milkyway and Einstein:

"App version needs OpenCL but GPU doesn't support it"

I read in the forums that removing some lines in cc_config.xml will fix it.
Done, cc_config.xml deleted completely and nothing.
Also that coming back to the previous drivers would do it, because the current ones are CUDA 6.5, only 64 bits bla bla bla, nothing:
When I come back to 304.117 I get a different error message for Einstein:

"App version needs CUDA but GPU doesn't support it"

Funny, because two lines above the log says that BOINC detects cuda:

"OpenCL: NVIDIA GPU 0: Quadro 1000M (driver version 304.117, device version OpenCL 1.1 CUDA, 2047MB, 2047MB available, 45 GFLOPS peak)"

So... what the hell is going on??
I don't want to start messing with the graphic drivers in Ubuntu because the NVIDIA angel can come and slice me with a sword of fire, so better I ask first.

BTW: also I updated to BOINC 7.4.22 trying to fight this nightmare.

Somebody has any ideas?

Thanks!

Also that coming back to the previous drivers would do it, because the current ones are CUDA 6.5, only 64 bits bla bla bla, nothing:
When I come back to 304.117 I get a different error message for Einstein:

"App version needs CUDA but GPU doesn't support it"

Funny, because two lines above the log says that BOINC detects cuda:

"OpenCL: NVIDIA GPU 0: Quadro 1000M (driver version 304.117, device version OpenCL 1.1 CUDA, 2047MB, 2047MB available, 45 GFLOPS peak)"

So... what the hell is going on??

No, It doesn't say Boinc detects Cuda, it says it detects OpenCL, Cuda support will be detected on a different line.

Claggy

Hi Claggy, thanks for the reply.
I think I figure it out by my own. I post it here just in case somebody has the same problems:

It seems that for my configuration the GPU Einstein application (Binary Radio Pulsar Search (Arecibo, GPU) v1.39 (BRP4G-cuda32-nv270)) works only for the latest NVIDIA driver (nvidia-331), while it doesn't for the previous one (nvidia-304).
On the other side Milkyway does the contrary.
So I have just had to decide in which project I am more interested and install the driver accordingly (because I don't see differences in the behavior of the rest of the programs or the computer).

What I don't understand is why Milkyway continuously send me tasks to abort them without start and then saying: "App version needs OpenCL but GPU doesn't support it".
It is the first time I see this behavior in Milkyway and that is the reason because I began digging into this.
If it is not supported, just don't send the tasks.

On a side note, in case somebody cares about the opinion of a simple user: I have seen over these 2 years contributing to BOINC that projects have become more and more complex requiring more user intervening: some of them require to install specific libraries, others external programs, now to have installed an specific driver and not only they required it, they will send you tasks and then abort them, what for a novice would be really confusing and discouraging.

Honestly, I think it goes against one of the central aims of BOINC: keep expanding the network.
Making things more and more difficult won't help.
Just an opinion.

Thanks,
Yacob