Another CUDA problem?!
14 Jul 2013 18:09:27 UTC
Topic 197061
(moderation:
I'm in process of switching from 32-bit to 64-bit MEPIS 11 Linux; I've been running BOINC for a long time (originally in Windows XP, then in 32-bit MEPIS), and Einstein for two or three months. Recently I had a new nVidia driver update on my 32-bit, and started getting a report of "no usable GPU found"; installing the MEPIS packaged CUDA libraries fixed that problem. Now, in 64-bit, even with the CUDA packages and the CUDA ia-32 library as well (and yes, I've restarted my system since installing the ia-32 libraries) I'm still getting a report of "no usable GPU" -- I've got a GT520 and the most current nVidia non-free driver (319.32) installed.
What do I need to do?
Another CUDA problem?!
)
Ok that version has only 48 cores for the GPU tasks.
(same as my 610M in this laptop I am on right now)
Do you have the GPU-Z download so you can take a look and see what it says?
http://www.techpowerup.com/downloads/SysInfo/GPU-Z/
I know the GT520 did work on the BRP's before.
(here is the list of GPU versions used here)
http://www.dskag.at/images/Research/EinsteinGPUperformancelist.pdf
Edit: I just checked yours and I see you have some tasks running even though it doesn't show your GPU card.
http://einsteinathome.org/host/7292181/tasks&offset=0&show_names=1&state=1&appid=23
and completes http://einsteinathome.org/host/7292181/tasks
My nVidia GT520 GPU works
)
My nVidia GT520 GPU works fine in 32-bit MEPIS; the tasks that show running are in possession of the 32-bit OS install of BOINC/Einstein (I'm dual-booting while I test the 64-bit OS). It's only on the 64-bit side that I'm having trouble. I've been pretty happy with the performance of this GPU since starting to run Einstein on it; it's putting out almost three times as many credits as my dual-core CPU is getting on Milky Way (yea, I know, can't directly compare, but that's a big difference by any measure). I've been told both would pick up a significant amount of performance if I switch to 64-bit, which is why I'm testing -- but I'm finding other stuff doesn't work as well under 64-bit, and lots of stuff doesn't come in a 64-bit version, so I'm dependent on 32-bit libraries, which aren't always available (for instance, there's no way to play Quicktime streams from a 32-bit app on a 64-bit Linux, because there's no 32-bit Quicktime library for 64-bit Linux).
I think, given the other things I'm finding, that I'm going to abandon 64-bit MEPIS and stick with the 32-bit with Physical Address Extension to handle RAM above 3.2 GiB. Fortunately, I don't have anything like as much effort into getting 64-bit up and almost-working as I put into getting the 32-bit PAE extensions fixed, and I learned some useful stuff along the way anyway.