I did try multiple earlier versions - none helped. In the event log, there is no mention of the GT 120 at all.

Have you tried connecting a monitor to it, or a dummy plug?

Claggy

I did try multiple earlier versions - none helped. In the event log, there is no mention of the GT 120 at all.

Have you tried connecting a monitor to it, or a dummy plug?

Claggy

I had my monitor connected to the GT 120 (though I usually don't), but again no mention of it in the event log.

Thanks for responding!

You said that under the previous Operating System everything worked, both GPUs were found. You installed a new Operating System and now one of your GPUs is no longer found. If nothing but your OS (and possibly CUDA driver) changed, how can it be BOINC its fault?

BOINC looks for /usr/local/cuda/lib/libcuda.dylib under OS X to see if you have GPUs installed that are CUDA capable, and if so, which ones that are. When your GPU is not or no longer included in the list of CUDA capable GPUs in that library, it cannot be detected by BOINC. There's nothing that BOINC can do or change about that.

So, options:
- Mavericks installs CUDA drivers elsewhere, where BOINC isn't looking for them.
- There's a bug is the CUDA detection for some GPUs in Mavericks.
- The thing to be aware of may have bitten you in your foot: Some newer MacBooks have dual GPUs with automatic switching. BOINC won't detect the NVIDIA or ATI/AMD GPU unless it is currently selected.
- Cosmic Rays.

---

Apple must have messed up somewhere during the development of Mavericks... The problem only occurred since DP4 of Mavericks was released. Earlier developer previews have no issue.

Dual GPU on MacBooks isn't a problem since BOINC released version 7. It triggers discrete graphics upon launch. I've also tried using gfxCardStatus to trigger discrete graphics firsthand before launching BOINC, still having the same GPU missing problem, so GPU dualies is out of the question here.

I asked the BOINC developer for the Mac about this, and this is what he just answered me:

Hi Jord,

I haven't installed Maverick yet, but in the past when a new version of Mac OS X was released, CUDA needed a new set of divers from NVIDIA. And NVIDIA usually has not had new drivers ready by the time a new OS X was released, but soon afterward. At this time, Maverick is available only to registered Mac developers, so it hasn't even been officially released yet to the general public.

They should check whether NVIDIA has released a new set of CUDA drivers for Maverick, and install them when they become available. When you install CUDA on the Mac, it also installs a pane in the System Preferences. When you open this pane, it automatically checks if new drivers are available and allows you to download and install them if they are.

I just now checked (with an older version of OS X) and see that the CUDA 5.5.28 driver update is now available. I don't know whether or not this is a fix for Maverick.

Cheers,
--Charlie

---

No, just checked CUDA 5.5.28 on OSX 10.9 GM. BOINC 7.2.18 doesn't yet recognise the GPUs via CUDA again. Still OpenCL only.

Charlie is right, it usually takes ages until NVIDIA gets their drivers updated for new OSX versions, despite the OSX development versions being available months before the actual release. We'll see whether they manage it this time, say, until Oct 22nd.

Oliver

For some odd reasons BOINC version 7.0.65 had my GPU registered missing on all version of Mac OS X. This include 10.6.8, 10.8.5, and the current GM version of 10.9.

7.0.31 works fine on all versions of Mac OS X except 10.9 since Developer Preview 4.

So is this Apple's problem or BOINC's problem...?

NVIDIA GPUs require an updated CUDA driver to support CUDA on 10.9. OpenCL works out of the box as it's provided by Apple.

---

Einstein@Home Project

NVIDIA GPUs require an updated CUDA driver to support CUDA on 10.9. OpenCL works out of the box as it's provided by Apple.

To put 10.9 aside, that still doesn't explain why BOINC version 7.0.31 works on both 10.6.8 and 10.8.5 and yet version 7.0.65 does not.

Sure, it should therefore be considered as a regression in BOINC.

Oliver

---

Einstein@Home Project

I got impatient. I bought a Nvidia GT 640 (the one with the TDP of 49 watts and DDR5 memory), which works out of the box with my Mac Pro 2009 (though it doesn't show the boot screen) and 10.9. It was not expensive (less than $100), and it's twice as fast as the GT 120.

The GT 120 (and my GTX 285) may never be supported for CUDA in 10.9. (My GTX 285 has been in a box for a while, replaced by a GTX 570.)

Sadly replacing GPU is not an option for a MacBook Pro...

Sadly replacing GPU is not an option for a MacBook Pro...

Have you tried Boinc 7.2.33 yet, it has some changes relating to GPU detection, with Cuda use being re-enabled:

client: optionally detect GPUs via a child process, for dual_GPU laptops.

Some dual-GPU laptops (e.g., Macbook Pro) don't power down the more powerful GPU until all applications which used them exit. To save battery life, the client launches a second instance of the client as a child process to detect and get info about the GPUs. The child process writes the info to a temp file which our main client then reads. This option is enabled at compile time by defining USE_CHILD_PROCESS_TO_DETECT_GPUS as non-zero in gpu_detect.cpp

Claggy

The GT 120 (and my GTX 285) may never be supported for CUDA in 10.9.

FYI, this is a known issue of the CUDA 5.5 driver on Mavericks. It will be fixed by NVIDIA in a future update.

Best,
Oliver

---

Einstein@Home Project