Seems it's not picking up my Nvidia 760GTX - using the latest 355.11 drivers..

Is this after starting up the computer?

If so, try restarting the BOINC client as Linux does not make the GPU available immediately.

---

you need the cuda toolkit 7.5 installed on the machine for boinc to see the gpu

you can get that on the nvidia site

---

I came down with a bad case of i don't give a crap

Installing the Toolkit would be the Shotgun effect, but, it should work providing the system hasn't already been damaged by prior attempts. You would need to remove the existing driver first using something similar to;
sudo apt-get remove --purge nvidia-*
Then download and install the Toolkit, https://developer.nvidia.com/cuda-downloads?sid=480386
You might want to make sure you have things backed-up, I had a bad experience installing the Toolkit on a damaged system...

actually that is not entirely correct

first remove all nvidia drivers as tbar said make sure you downloaded the latest linux drivers and the toolkit

then install the nvidia driver (newest versions do not ship with cuda in the driver

after nvidia driver install install the toolkit and voila you have a gpu found
make sure it is the 7.5 toolkit

---

I came down with a bad case of i don't give a crap

Actually it is correct. I just tried it with Ubuntu 15.04 and the system I used to test the 750Ti. After I uninstalled Driver 346 I ran Just the ToolKit. This is what it gave;

Tue 06 Oct 2015 08:06:03 AM EDT |  | Starting BOINC client version 7.2.33 for x86_64-pc-linux-gnu
Tue 06 Oct 2015 08:06:03 AM EDT |  | Data directory: /home/tbar/BOINC
Tue 06 Oct 2015 08:06:03 AM EDT |  | CUDA: NVIDIA GPU 0: GeForce GTX 750 Ti (driver version unknown, CUDA version 7.5, compute capability 5.0, 2043MB, 1845MB available, 2082 GFLOPS peak)
Tue 06 Oct 2015 08:06:03 AM EDT |  | OpenCL: NVIDIA GPU 0: GeForce GTX 750 Ti (driver version 352.39, device version OpenCL 1.2 CUDA, 2043MB, 1845MB available, 2082 GFLOPS peak)
Tue 06 Oct 2015 08:06:03 AM EDT |  | Host name: 750Ti
Tue 06 Oct 2015 08:06:03 AM EDT |  | Processor: 4 GenuineIntel Intel(R) Xeon(R) CPU           X3220  @ 2.40GHz [Family 6 Model 15 Stepping 11]
Tue 06 Oct 2015 08:06:03 AM EDT |  | OS: Linux: 3.19.0-28-generic

You do have to run the installer twice, to disable the Open Source driver first then second to install the nVidia drivers.
Most people don't Need the latest driver, in fact, my test with the Linux CUDA App worked great with driver 346 from 'Additional Drivers' with a couple of additions from the Package Manager. If you plan on running the Stock OpenCL App driver 352 should also work fine. It's a little overkill, but installing just the ToolKit is probably the easiest way to get BOINC to see the GPU.

Gary Roberts of Einstein has written of his experiences getting a GTX 750 Ti running under, I think, PCLinuxOS.

NVIDIA drivers present but no GPUs found

(the thread is subtitled Ubuntu 14.04, although the particular post by Gary refers more to PCLinuxOS)

It seems that his particular distro has started to package and distribute 'CUDA and OpenCL high performance computing libs' (what I'd call "runtime support files" separately from the base driver. They exist, but require a second package download.

Going the Toolkit route (usually Software Development Toolkit, or SDK for short) will probably get you a matched set of everything you could possibly want in one package, at the expense of a very much larger download. The downside is that SDKs are usually released in advance of the final driver and runtime releases for the new version, so that developers can start to test their programs with the new features. The toolkit drivers may not be as reliable or efficient as the final release version, and there may be compatibility issues with programs designed for the public release.

either way you need the toolkit

why install the toolkit without the driver o.0

---

I came down with a bad case of i don't give a crap

either way you need the toolkit

why install the toolkit without the driver o.0

No, you need the runtime support files, not the developer files.

Unless you're a developer?

either way you need the toolkit

why install the toolkit without the driver o.0

No, you need the runtime support files, not the developer files.

Unless you're a developer?

Unfortunately some people, such as the OP & Zombu, can install the latest driver from the nVidia site and Still get the GPU Not Found Error. For those people installing the ToolKit Works. The 7.5 ToolKit obviously installs Driver 352 because it shows up after just installing the ToolKit.

I mentioned the problem with the repository drivers last month and provided a link here, http://setiweb.ssl.berkeley.edu/beta/forum_thread.php?id=2164&postid=54931#54931. You can get the repository driver to work if you also go to the package manager and install the correct nvidia-xxx-uvm package and OpenCL loader. Unfortunately the latest repository driver is 346.xx and will probably give Errors with the Current Stock SETI MB Linux OpenCL App. The 7.5 Toolkit installs Driver 352 which Should work with the Current Stock MB OpenCL App. For me though, the Linux CUDA App is Faster and works fine with driver 346 from the repository.

Well, as I said, applying the whole developer sledgehammer is a viable alternative. But it shouldn't be *necessary*, and I thought Gary's post was a fairly good explanation of what was needed to get the end-user files from one particular repository. The rest, as always, it to get your particular package maintainer to finish the job: not for your benefit, but for the benefit of the next guy in line.

1.9 gigs are not gonna kill me and it's a quick way to get things going without much fuzz

there s probably many ways that lead to rome this one just works perfectly fine for me (might not for others )

---

I came down with a bad case of i don't give a crap

I just had another experience with the missing GPU. Actually it was just CUDA missing, OpenCL was seen. I was trying different system configurations, ran into a problem, and decided the easiest fix would be to just reinstall the system. This left me with a virgin 'No ToolKit' system. After installing everything else I installed the driver from nVidia and received the Missing co-processor Error. I was about to install the ToolKit then decided to just try a few links. The one that worked was to make links to \usr\lib\x86_64-linux-gnu libcuda.so, libcuda.so.1, and libcuda.so.346.59 then move them to \usr\lib and rename them. That seems to have satisfied BOINC without installing the ToolKit.

If you use the 'Additional Drivers' version above 340.xx you might have the same problem with missing CUDA. This problem can be fixed by opening the Synaptic Package Manager and entering nvidia in the Quick Filter box. Only drivers in the repository will show here. Look for nvidia-xxx-uvm and see if it is installed. If you are using a repository driver above 340.xx it will probably be uninstalled. Just install the nvidia-xxx-uvm version which matches your other package versions and that should solve it.

Have fun.

At the risk of saying something stupid yet again:

With a new machine (XUbuntu 14.04 ) Ubuntu nVidia drivers installed
ok (I used the Additonal Drivers panel)
but tbe GPU was not recognized by boinc till I also did
sudo apt-get install nvidia-modprobe

Apparently with new installs that -uvm stuff TBar
mentioned is no longer separate, no longer something
that requires attention (after a couple years
of problems with every new kernel).
Finally.

Read TBar's note more carefully.
Synaptic says (with nvidia as the filter) I have
the following installed and boinc sees the gpu:

nvidia-opencl-icd-346
nvidia-modprobe
libcuda1-346
nvidia-libopencl1-346
nvidia-346
nvidia-prime
bbswitch-dkms
ubuntu-drivers-common
libvdpau1
xserver-xorg-nvidia-lts-vivid
dmraid

Note the above list does not show the 346-uvm installed.
Synaptic shows that uvm, but without it the GPU seems
to be doing work. No AP work on hand it appears,
so it is Einstein using the GPU

I guess that`s my problem also.
Just that i have an AMD GPU.
Linux Mint 17.2 based on Ubuntu 14.04.

Would be nice if someone could direct me to it.

---

With each crime and every kindness we birth our future.

At the risk of saying something stupid yet again:

With a new machine (XUbuntu 14.04 ) Ubuntu nVidia drivers installed
ok (I used the Additonal Drivers panel)
but tbe GPU was not recognized by boinc till I also did
sudo apt-get install nvidia-modprobe

Apparently with new installs that -uvm stuff TBar
mentioned is no longer separate, no longer something
that requires attention (after a couple years
of problems with every new kernel).
Finally.

Nailed it. TY! :D

Just in time as my 970 GTX arrives on Monday :P

At the risk of saying something stupid yet again:

With a new machine (XUbuntu 14.04 ) Ubuntu nVidia drivers installed
ok (I used the Additonal Drivers panel)
but tbe GPU was not recognized by boinc till I also did
sudo apt-get install nvidia-modprobe

Apparently with new installs that -uvm stuff TBar
mentioned is no longer separate, no longer something
that requires attention (after a couple years
of problems with every new kernel).
Finally.

Nailed it. TY! :D

Just in time as my 970 GTX arrives on Monday :P

It appears BOINC still doesn't see OpenCL. You need OpenCL to receive the current stock SETI Apps. Obviously there is a difference between using the drivers from the Additional Drivers section and installing from nVidia, just as there is with different Systems and Drivers. Most people are having better luck with installing the drivers from nVidia although some still have problems with the drivers from the nVidia site. As for nvidia-modprobe, I've only had success with it helping with CUDA, but, I have the same success with just linking to the CUDA library without installing an additional package. The problem is with OpenCL, sometimes it just avoids all attempts without installing the CUDA ToolKit. After repeated attempts to awaken OpenCL, about the only alternative is to purge the drivers and trying the install again, maybe with a different driver. In the end there is always the ToolKit.

The nvidia-cuda-toolkit shows up in synaptic but
installing it would remove 346 and install 340.
I'm not changing anything here just yet.