I've Built a Couple OSX CUDA Apps...

Message boards : Number crunching : I've Built a Couple OSX CUDA Apps...
Message board moderation

To post messages, you must log in.

Previous · 1 . . . 23 · 24 · 25 · 26 · 27 · 28 · 29 . . . 58 · Next

AuthorMessage
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1787135 - Posted: 12 May 2016, 23:25:00 UTC - in response to Message 1787130.  
Last modified: 13 May 2016, 0:09:55 UTC

I'm afraid you're going to have to be a little more detailed. What should I do with the lines and where should I do it. I could post the App in the thread at C.A. if you'd like to try it yourself.

The Apps are here, OSX v8 apps - dev
The 7.5 App compiled in Mavericks was used over the last day on main.
ID: 1787135 · Report as offensive
Profile jason_gee
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 24 Nov 06
Posts: 7489
Credit: 91,093,184
RAC: 0
Australia
Message 1787144 - Posted: 13 May 2016, 0:11:46 UTC - in response to Message 1787135.  
Last modified: 13 May 2016, 0:12:59 UTC

In AnalyzeFuncs.cpp, Between the succeeding cudaAcc_free(); call, and Boinc_finish().

This looks like it'll require source level and build system debugging, also a bad idea to have broken builds in circulation.

Steps to replicate from scratch are this, using older OSX ?
- Build boinc libs from current boinc master under XCode
- paste code from Petri over the existingapp client folder files
- set osx min version flag and build via command line ? (using Berkeley's configure/Make?)

Did you see what happens with my flat Makefile (in mac_build) instead of their's ? (still have to run configure first, not completely uncoupled from sah_config.h yet)
"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.
ID: 1787144 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1787158 - Posted: 13 May 2016, 1:08:02 UTC - in response to Message 1787144.  

Did you see what happens with my flat Makefile (in mac_build) instead of their's ? (still have to run configure first, not completely uncoupled from sah_config.h yet)

I still don't know how to use that method of compiling. If you'd like to post the instructions in that restricted thread at C.A. I'll give it a try.

I searched the last used AnalyzeFuncs.cpp for Boinc_finish and received Zero hits.
ID: 1787158 · Report as offensive
Profile jason_gee
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 24 Nov 06
Posts: 7489
Credit: 91,093,184
RAC: 0
Australia
Message 1787169 - Posted: 13 May 2016, 1:50:07 UTC - in response to Message 1787158.  
Last modified: 13 May 2016, 1:52:26 UTC

Did you see what happens with my flat Makefile (in mac_build) instead of their's ? (still have to run configure first, not completely uncoupled from sah_config.h yet)

I still don't know how to use that method of compiling. If you'd like to post the instructions in that restricted thread at C.A. I'll give it a try.

I searched the last used AnalyzeFuncs.cpp for Boinc_finish and received Zero hits.


Try cudaAcc_free in that file, (which is where the succeeding things are done), after that it returns control to worker.cpp, where the final boinc_finish() is called.

Since it's failing (for whatever reasons) between those two points (perhaps on some pthreads termination of the worker), so far it's in line with either build system issues or boincapi. Trick is to isolate whether it's the client, timer thread, or worker threat initiating the insta-death weirdness. The pipe errors do suggest boinc_diagnostics and shared memory changes may be involved. As we're getting into advanced multithreading concepts, I will probably have to attempt to replicate the conditions.

Mavericks the appropriate variant ? ML ? Yosemite would do ?
"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.
ID: 1787169 · Report as offensive
Profile jason_gee
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 24 Nov 06
Posts: 7489
Credit: 91,093,184
RAC: 0
Australia
Message 1787172 - Posted: 13 May 2016, 1:54:35 UTC - in response to Message 1787169.  
Last modified: 13 May 2016, 1:56:03 UTC

I still don't know how to use that method of compiling.


Thought I put a readme in the mac_build folder, checking.

[Edit] mac_build_README in mac_build folder contains:
Prototype lean makefile (proof of concept only)

Adds mac_build directory on the client, with handmade Makefile
Currently known to work os OSX El Capitan, Clang, Cuda Toolkit 7.5

intended to see if a leaner, non-autotools based, single level, Makefile, can
reduce the maintenance overhead associated with updating the Cuda multibeam
builds. OSX as trial, though eventually should be made to work across all Cuda
enabled platforms (except Windows)

to use:
- Make sure Cuda toolkit is installed as per its documentation
, including XCode and command line tools as indicated, and samples
successfully build and run ( oceanFFT under simmulations is a
good, as it is close in needs to seti cuda multibeam)
- Ensure some [correctly] prebuilt static boinc libraries
( libboinc.a and libboinc_api.a ) are put somewhere on a predefined library path
(I just thre some in the cuda libraries folder for now, will better support
configurability later)
- For now, hardwired include directory search paths expect a 'boinc' directory
with sources, next to (at the same level) and the XBranch directory
- Adjust the Cuda toolkit path near the top of the make file
(will also be configurable later.
- run 'make' from the mac_build directory

known issues/todos: ( as at 18th December, 2015 )
- no explicit compiler optimisation flags added yet (device or host)
- x86_64 only for now, and compute capabilities <2.0 are not available
(will be addressed with adding older toolkit support later)
- Need to put static Boinc libs somewhere on an already present library path
- Only tested so far on El Capition, Cuda toolkit 7.5, Fully update XCode
- Lots and lots of compiler warnings to fix, due to c++11 deprecations
related to constant strings.

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.
ID: 1787172 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1787190 - Posted: 13 May 2016, 2:40:13 UTC - in response to Message 1787172.  
Last modified: 13 May 2016, 2:43:56 UTC

Mavericks the appropriate variant ? ML ? Yosemite would do ?

I really couldn't tell much difference between the 7.5 versions, the one compiled in Mavericks completed a few more tasks before giving the Crash after finish. The 6.5 version compiled in ML, using the Exact same code, doesn't Crash. The 7.0 version gives the same Crash as the other two 7 versions, I just added it 'cause it was there. Three different version 7 Apps all with the same Crash After Finish.

I saw the README, so, do I need to move the Makefile somewhere else? What do I do with the old Makefiles? Do I leave the BOINC libs in the boinc-master folder with the same SETI_BOINC_DIR=" /Users/Tom/boinc" line? After running the path lines;
export PATH=/Developer/NVIDIA/CUDA-7.5/bin:$PATH
export DYLD_LIBRARY_PATH=/Developer/NVIDIA/CUDA-7.5/lib:$DYLD_LIBRARY_PATH
export PATH=/Developer/NVIDIA/CUDA-7.5/bin/nvcc:$PATH
export PATH=/usr/include:$PATH
export DYLD_LIBRARY_PATH=/usr/include:$DYLD_LIBRARY_PATH
I cd to /Users/Tom/sah_v7_opt/Xbranch, run _autosetup, then run the custom configure line, then edit the makefiles in Xbranch and Xbranch/client and finally run make.
What do I do differently?
ID: 1787190 · Report as offensive
Profile jason_gee
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 24 Nov 06
Posts: 7489
Credit: 91,093,184
RAC: 0
Australia
Message 1787191 - Posted: 13 May 2016, 2:55:10 UTC - in response to Message 1787190.  

Mavericks the appropriate variant ? ML ? Yosemite would do ?

I really couldn't tell much difference between the 7.5 versions, the one compiled in Mavericks completed a few more tasks before giving the Crash after finish. The 6.5 version compiled in ML, using the Exact same code, doesn't Crash. The 7.0 version gives the same Crash as the other two 7 versions, I just added it 'cause it was there. Three different version 7 Apps all with the same Crash After Finish.

I saw the README, so, do I need to move the Makefile somewhere else? What do I do with the old Makefiles? Do I leave the BOINC libs in the boinc-master folder with the same SETI_BOINC_DIR=" /Users/Tom/boinc" line? After running the path lines;
export PATH=/Developer/NVIDIA/CUDA-7.5/bin:$PATH
export DYLD_LIBRARY_PATH=/Developer/NVIDIA/CUDA-7.5/lib:$DYLD_LIBRARY_PATH
export PATH=/Developer/NVIDIA/CUDA-7.5/bin/nvcc:$PATH
export PATH=/usr/include:$PATH
export DYLD_LIBRARY_PATH=/usr/include:$DYLD_LIBRARY_PATH
I cd to /Users/Tom/sah_v7_opt/Xbranch, run _autosetup, then run the custom configure line, then edit the makefiles in Xbranch and Xbranch/client and finally run make.
What do I do differently?

Same except replace
then edit the makefiles in Xbranch and Xbranch/client and finally run make.
with run make while in mac_build directory. Point was to bypass the unmaintained/broken Makefiles, and start clean.

If that chokes, then diagnosis and fixes are much easier (single file written by hand by myself, as opposed to 5 broken autogenerated files)
"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.
ID: 1787191 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1788523 - Posted: 18 May 2016, 20:06:33 UTC - in response to Message 1777639.  
Last modified: 18 May 2016, 20:33:27 UTC

Nice, FedEx delivers on Saturday!

So...We don't need no steeking Names right?
If Yosemite whats to call my new card a "NVIDIA Graphics Device" that's just fine I suppose, as long as it works.
But that means BOINC calls it the same; Coprocessors: [3] NVIDIA Graphics Device (2047MB) driver: 4600.58 OpenCL: 1.2
SETI too;
Sat Apr 9 16:10:47 2016 | | Starting BOINC client version 7.6.22 for x86_64-apple-darwin
Sat Apr 9 16:10:48 2016 | | CUDA: NVIDIA GPU 0: Graphics Device (driver version 7.5.26, CUDA version 7.5, compute capability 5.2, 2048MB, 1785MB available, 2022 GFLOPS peak)
Sat Apr 9 16:10:48 2016 | | CUDA: NVIDIA GPU 1: GeForce GTX 750 Ti (driver version 7.5.26, CUDA version 7.5, compute capability 5.0, 2048MB, 1879MB available, 1388 GFLOPS peak)
Sat Apr 9 16:10:48 2016 | | CUDA: NVIDIA GPU 2: GeForce GTX 750 Ti (driver version 7.5.26, CUDA version 7.5, compute capability 5.0, 2048MB, 1880MB available, 1421 GFLOPS peak)
Sat Apr 9 16:10:48 2016 | | OpenCL: NVIDIA GPU 0: Graphics Device (driver version 10.5.2 346.02.03f06, device version OpenCL 1.2, 2048MB, 1785MB available, 2022 GFLOPS peak)
Sat Apr 9 16:10:48 2016 | | OpenCL: NVIDIA GPU 1: GeForce GTX 750 Ti (driver version 10.5.2 346.02.03f06, device version OpenCL 1.2, 2048MB, 1879MB available, 1388 GFLOPS peak)
Sat Apr 9 16:10:48 2016 | | OpenCL: NVIDIA GPU 2: GeForce GTX 750 Ti (driver version 10.5.2 346.02.03f06, device version OpenCL 1.2, 2048MB, 1880MB available, 1421 GFLOPS peak)
Sat Apr 9 16:10:48 2016 | | OS: Mac OS X 10.10.5 (Darwin 14.5.0)

But it Does work...
Seems to be a little better than the 750Ti.
We'll see how it goes.

Seems the Second GTX 950 Broke BOINC. Now the thing thinks the 950s are pre-Fermi cards and have disabled OpenCL. It isn't happy about CUDA either but apparently CUDA Does Work, for now. It Removed the OpenCL: 1.2 from the description, and I don't have any APs to test.
Wed May 18 15:26:40 2016 | | Starting BOINC client version 7.6.32 for x86_64-apple-darwin
Wed May 18 15:26:40 2016 | | Data directory: /Volumes/Mov1/BOINC/Yosemite/BOINC Data
Wed May 18 15:26:41 2016 | | NVIDIA GPU 1: Graphics Device cannot be used for CUDA or OpenCL computation with CUDA driver 6.5 or later
Wed May 18 15:26:41 2016 | | NVIDIA GPU 2: Graphics Device cannot be used for CUDA or OpenCL computation with CUDA driver 6.5 or later
Wed May 18 15:26:41 2016 | | CUDA: NVIDIA GPU 0: Graphics Device (driver version 7.5.29, CUDA version 7.5, compute capability 5.2, 2048MB, 1848MB available, 2022 GFLOPS peak)
Wed May 18 15:26:41 2016 | | CUDA: NVIDIA GPU 1: GeForce GTX 750 Ti (driver version 7.5.29, CUDA version 7.5, compute capability 5.0, 2048MB, 1862MB available, 1421 GFLOPS peak)
Wed May 18 15:26:41 2016 | | CUDA: NVIDIA GPU 2: Graphics Device (driver version 7.5.29, CUDA version 7.5, compute capability 5.2, 2048MB, 1816MB available, 2022 GFLOPS peak)
Wed May 18 15:26:41 2016 | | OpenCL: NVIDIA GPU 1: GeForce GTX 750 Ti (driver version 10.5.2 346.02.03f06, device version OpenCL 1.2, 2048MB, 1862MB available, 1421 GFLOPS peak)
Wed May 18 15:26:41 2016 | | OpenCL: NVIDIA GPU 1: Graphics Device (driver version 10.5.2 346.02.03f06, device version OpenCL 1.2, 2048MB, 2048MB available, 758 GFLOPS peak)
Wed May 18 15:26:41 2016 | | OpenCL: NVIDIA GPU 2: Graphics Device (driver version 10.5.2 346.02.03f06, device version OpenCL 1.2, 2048MB, 2048MB available, 758 GFLOPS peak)
Wed May 18 15:26:41 2016 | | OpenCL CPU: Intel(R) Xeon(R) CPU E5472 @ 3.00GHz (OpenCL driver vendor: Apple, driver version 1.1, device version OpenCL 1.2)
Wed May 18 15:26:41 2016 | SETI@home | Found app_info.xml; using anonymous platform
Wed May 18 15:26:41 2016 | | App version needs OpenCL but GPU doesn't support it
Wed May 18 15:26:41 2016 | SETI@home Beta Test | Found app_info.xml; using anonymous platform
Wed May 18 15:26:41 2016 | | App version needs OpenCL but GPU doesn't support it
Wed May 18 15:26:42 2016 | | Processor: 8 GenuineIntel Intel(R) Xeon(R) CPU E5472 @ 3.00GHz [x86 Family 6 Model 23 Stepping 6]
Wed May 18 15:26:42 2016 | | OS: Mac OS X 10.10.5 (Darwin 14.5.0)

Stupid program...

Oh, and after Weeks of trying to work around the BOINC "Crash After Finish", the thing Still crashes AFTER the Results are written. BOINC says;
Wed May 18 16:20:39 2016 | SETI@home | [sched_op] Reason: Unrecoverable error for task blc2_2bit_guppi_57451_27739_HIP69824_0027.28248.0.17.26.246.vlar_2
Wed May 18 16:20:39 2016 | SETI@home | Computation for task blc2_2bit_guppi_57451_27739_HIP69824_0027.28248.0.17.26.246.vlar_2 finished
ID: 1788523 · Report as offensive
Chris Adamek
Volunteer tester

Send message
Joined: 15 May 99
Posts: 251
Credit: 434,772,072
RAC: 236
United States
Message 1788539 - Posted: 18 May 2016, 21:27:41 UTC - in response to Message 1788523.  

You could try the MB openCL app if you are in a hurry to try it. Doesn't look like there will be any AP's for a few days.

I'm just glad I found an app that doesn't barf constantly on my mac. lol No gaussian problems since I went back to 3347. The midrange AR's sometimes take an oddly long amount of time to finish (I think its when they are running at the same time as VLARs on a given GPU) but I imagine I can fiddle with the settings to get that better. VLARs though are pretty fast. Effective completion time with that app is usually under 10 minutes each running 3 at a time.

Chris
ID: 1788539 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1788675 - Posted: 19 May 2016, 12:17:46 UTC - in response to Message 1788539.  
Last modified: 19 May 2016, 12:20:17 UTC

Well, I don't think I need to bother with another App right now.

So, BOINC is Also Broke in El Capitan 10.11.4...and it Does see the cards as GTX 950s;

Thu May 19 08:06:37 2016 | | Starting BOINC client version 7.6.22 for x86_64-apple-darwin
Thu May 19 08:06:37 2016 | | log flags: file_xfer, sched_ops, task, sched_op_debug
Thu May 19 08:06:37 2016 | | Libraries: libcurl/7.39.0 OpenSSL/1.0.1j zlib/1.2.5 c-ares/1.10.0
Thu May 19 08:06:37 2016 | | Data directory: /Volumes/Mov1/BOINC/Yosemite/BOINC Data
Thu May 19 08:06:38 2016 | | NVIDIA GPU 1: GeForce GTX 950 cannot be used for CUDA or OpenCL computation with CUDA driver 6.5 or later
Thu May 19 08:06:38 2016 | | NVIDIA GPU 2: GeForce GTX 950 cannot be used for CUDA or OpenCL computation with CUDA driver 6.5 or later
Thu May 19 08:06:38 2016 | | CUDA: NVIDIA GPU 0: GeForce GTX 950 (driver version 7.5.29, CUDA version 7.5, compute capability 5.2, 2048MB, 1899MB available, 2022 GFLOPS peak)
Thu May 19 08:06:38 2016 | | CUDA: NVIDIA GPU 1: GeForce GTX 750 Ti (driver version 7.5.29, CUDA version 7.5, compute capability 5.0, 2048MB, 1906MB available, 1421 GFLOPS peak)
Thu May 19 08:06:38 2016 | | CUDA: NVIDIA GPU 2: GeForce GTX 950 (driver version 7.5.29, CUDA version 7.5, compute capability 5.2, 2048MB, 1810MB available, 2022 GFLOPS peak)
Thu May 19 08:06:38 2016 | | OpenCL: NVIDIA GPU 1: GeForce GTX 750 Ti (driver version 10.11.5 346.03.06f01, device version OpenCL 1.2, 2048MB, 1906MB available, 1421 GFLOPS peak)
Thu May 19 08:06:38 2016 | | OpenCL: NVIDIA GPU 1: GeForce GTX 950 (driver version 10.11.5 346.03.06f01, device version OpenCL 1.2, 2048MB, 2048MB available, 758 GFLOPS peak)
Thu May 19 08:06:38 2016 | | OpenCL: NVIDIA GPU 2: GeForce GTX 950 (driver version 10.11.5 346.03.06f01, device version OpenCL 1.2, 2048MB, 2048MB available, 758 GFLOPS peak)
Thu May 19 08:06:38 2016 | | OpenCL CPU: Intel(R) Xeon(R) CPU E5472 @ 3.00GHz (OpenCL driver vendor: Apple, driver version 1.1, device version OpenCL 1.2)
Thu May 19 08:06:38 2016 | SETI@home | Found app_info.xml; using anonymous platform
Thu May 19 08:06:38 2016 | | App version needs OpenCL but GPU doesn't support it
Thu May 19 08:06:38 2016 | SETI@home Beta Test | Found app_info.xml; using anonymous platform
Thu May 19 08:06:38 2016 | | App version needs OpenCL but GPU doesn't support it
Thu May 19 08:06:38 2016 | | Version change (7.6.32 -> 7.6.22)
Thu May 19 08:06:39 2016 | | Processor: 8 GenuineIntel Intel(R) Xeon(R) CPU E5472 @ 3.00GHz [x86 Family 6 Model 23 Stepping 6]
Thu May 19 08:06:39 2016 | | OS: Mac OS X 10.11.4 (Darwin 15.4.0)

Why is the OpenCL section listing TWO GPU 1s?
The card listings are Wrong as well. The 950s are in Slots 1 & 2, the 750Ti is in Slot 4.

What's up with that???
ID: 1788675 · Report as offensive
Chris Adamek
Volunteer tester

Send message
Joined: 15 May 99
Posts: 251
Credit: 434,772,072
RAC: 236
United States
Message 1788696 - Posted: 19 May 2016, 13:58:39 UTC - in response to Message 1788675.  

It is surely something to do with the web driver/cuda drivers. I've not had any trouble with boinc manager in El Capitan with my 3 card nvidia Mac Pro. Had you tried El Capitan before you put a second 950 in? In Windows I often have to reinstall the nvidia drivers when I swap cards around to get them to be seen correctly, did you try reinstalling the web drivers & cuda yet?

Chris
ID: 1788696 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1788704 - Posted: 19 May 2016, 14:20:51 UTC - in response to Message 1788696.  
Last modified: 19 May 2016, 14:25:25 UTC

Seems the Second GTX 950 Broke BOINC.

Both OSes worked the same with just One GTX 950.
It would Appear the Second GTX 950 has caused BOINC to think they are Both 9500 GTs even though they are listed as GTX 950s, hence the statement meant for pre-Fermi GPUs.
Why it doesn't consider the GTX 750Ti before disabling OpenCL is anyone's guess as is why it is listing Two GPU 1s.
Remember I told you it appears OpenCL is Broken in BOINC with Mavericks and above?
The GTX 9xx series Doesn't work with the Apple supplied drivers, You have to use the Webdrivers.
The cards work Fine with CUDA.
ID: 1788704 · Report as offensive
Urs Echternacht
Volunteer tester
Avatar

Send message
Joined: 15 May 99
Posts: 692
Credit: 135,197,781
RAC: 211
Germany
Message 1788810 - Posted: 19 May 2016, 22:00:35 UTC - in response to Message 1788704.  

Both OSes worked the same with just One GTX 950.
It would Appear the Second GTX 950 has caused BOINC to think they are Both 9500 GTs even though they are listed as GTX 950s, hence the statement meant for pre-Fermi GPUs.
Why it doesn't consider the GTX 750Ti before disabling OpenCL is anyone's guess as is why it is listing Two GPU 1s.
Remember I told you it appears OpenCL is Broken in BOINC with Mavericks and above?
The GTX 9xx series Doesn't work with the Apple supplied drivers, You have to use the Webdrivers.
The cards work Fine with CUDA.
Idea :
On win or linux it helped sometimes to switch GPU slots.
_\|/_
U r s
ID: 1788810 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1788825 - Posted: 19 May 2016, 22:31:07 UTC - in response to Message 1788810.  

On the Older Mac Pros Slots 1 & 2 are PCIe2 16x while slots 3 & 4 are PCIe1 4x. Also, you can't mount a double height card in Slot 4 without altering the faceplate. I'm not interested in altering another faceplate.

Seems to me CUDA sees the cards correctly. The problem is with OpenCL detection. Not only is BOINC incapable of determining there is only One GPU 1, it's also incapable of reading what it printed for Compute Capability. If it would realize that CC 5.2 is Not a pre-Fermi card it wouldn't print that driver 6.5 warning. It seems the warning is coming from the OpenCL detection since it's listing GPU 1 & 2.

Things improved a bit after rebooting back into Yosemite, now it appears it realizes the machine really does have OpenCL. At least the OpenCL: 1.2 is back and it's not complaining about the GPU not having OpenCL.

Thu May 19 17:58:49 2016 | | Starting BOINC client version 7.6.32 for x86_64-apple-darwin
Thu May 19 17:58:50 2016 | | NVIDIA GPU 1: Graphics Device cannot be used for CUDA or OpenCL computation with CUDA driver 6.5 or later
Thu May 19 17:58:50 2016 | | NVIDIA GPU 2: Graphics Device cannot be used for CUDA or OpenCL computation with CUDA driver 6.5 or later
Thu May 19 17:58:50 2016 | | CUDA: NVIDIA GPU 0: Graphics Device (driver version 7.5.29, CUDA version 7.5, compute capability 5.2, 2048MB, 1779MB available, 2022 GFLOPS peak)
Thu May 19 17:58:50 2016 | | CUDA: NVIDIA GPU 1: GeForce GTX 750 Ti (driver version 7.5.29, CUDA version 7.5, compute capability 5.0, 2048MB, 1882MB available, 1421 GFLOPS peak)
Thu May 19 17:58:50 2016 | | CUDA: NVIDIA GPU 2: Graphics Device (driver version 7.5.29, CUDA version 7.5, compute capability 5.2, 2048MB, 1855MB available, 2022 GFLOPS peak)
Thu May 19 17:58:50 2016 | | OpenCL: NVIDIA GPU 1: GeForce GTX 750 Ti (driver version 10.5.2 346.02.03f06, device version OpenCL 1.2, 2048MB, 1882MB available, 1421 GFLOPS peak)
Thu May 19 17:58:50 2016 | | OpenCL: NVIDIA GPU 1: Graphics Device (driver version 10.5.2 346.02.03f06, device version OpenCL 1.2, 2048MB, 2048MB available, 758 GFLOPS peak)
Thu May 19 17:58:50 2016 | | OpenCL: NVIDIA GPU 2: Graphics Device (driver version 10.5.2 346.02.03f06, device version OpenCL 1.2, 2048MB, 2048MB available, 758 GFLOPS peak)
Thu May 19 17:58:50 2016 | | OpenCL CPU: Intel(R) Xeon(R) CPU E5472 @ 3.00GHz (OpenCL driver vendor: Apple, driver version 1.1, device version OpenCL 1.2)
Thu May 19 17:58:50 2016 | SETI@home | Found app_info.xml; using anonymous platform
Thu May 19 17:58:50 2016 | SETI@home Beta Test | Found app_info.xml; using anonymous platform
Thu May 19 17:58:51 2016 | | Processor: 8 GenuineIntel Intel(R) Xeon(R) CPU E5472 @ 3.00GHz [x86 Family 6 Model 23 Stepping 6]
Thu May 19 17:58:51 2016 | | OS: Mac OS X 10.10.5 (Darwin 14.5.0)

Right now it's still working.
ID: 1788825 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14656
Credit: 200,643,578
RAC: 874
United Kingdom
Message 1788832 - Posted: 19 May 2016, 23:09:14 UTC - in response to Message 1788825.  

Is there a Mac/Darwin version of clinfo, which could perform the OpenCL card enumeration independently of BOINC?
ID: 1788832 · Report as offensive
Profile Raistmer
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 16 Jun 01
Posts: 6325
Credit: 106,370,077
RAC: 121
Russia
Message 1788840 - Posted: 19 May 2016, 23:26:57 UTC - in response to Message 1788832.  

Is there a Mac/Darwin version of clinfo, which could perform the OpenCL card enumeration independently of BOINC?

app itself does basic enumeration being started standalone.
ID: 1788840 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1788846 - Posted: 19 May 2016, 23:43:19 UTC - in response to Message 1788832.  
Last modified: 19 May 2016, 23:48:30 UTC

There are versions around you can compile yourself;
Last login: Thu May 19 11:18:11 on console
TomsMacPro:~ Tom$ cd /Users/Tom/MacCLinfo 
TomsMacPro:MacCLinfo Tom$ ./clinfo
Found 1 platform(s).
platform[0x7fff0000]: profile: FULL_PROFILE
platform[0x7fff0000]: version: OpenCL 1.2 (Nov 12 2015 15:39:11)
platform[0x7fff0000]: name: Apple
platform[0x7fff0000]: vendor: Apple
platform[0x7fff0000]: extensions: cl_APPLE_SetMemObjectDestructor cl_APPLE_ContextLoggingFunctions cl_APPLE_clut cl_APPLE_query_kernel_names cl_APPLE_gl_sharing cl_khr_gl_event
platform[0x7fff0000]: Found 4 device(s).
	device[0xffffffff]: NAME: Intel(R) Xeon(R) CPU           E5472  @ 3.00GHz
	device[0xffffffff]: VENDOR: Intel
	device[0xffffffff]: PROFILE: FULL_PROFILE
	device[0xffffffff]: VERSION: OpenCL 1.2 
	device[0xffffffff]: EXTENSIONS: cl_APPLE_SetMemObjectDestructor cl_APPLE_ContextLoggingFunctions cl_APPLE_clut cl_APPLE_query_kernel_names cl_APPLE_gl_sharing cl_khr_gl_event cl_khr_fp64 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_byte_addressable_store cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_3d_image_writes cl_khr_image2d_from_buffer cl_APPLE_fp64_basic_ops cl_APPLE_fixed_alpha_channel_orders cl_APPLE_biased_fixed_point_image_formats cl_APPLE_command_queue_priority
	device[0xffffffff]: DRIVER_VERSION: 1.1

	device[0xffffffff]: Type: CPU 
	device[0xffffffff]: EXECUTION_CAPABILITIES: Kernel Native 
	device[0xffffffff]: GLOBAL_MEM_CACHE_TYPE: Read-Write (2)
	device[0xffffffff]: CL_DEVICE_LOCAL_MEM_TYPE: Global (2)
	device[0xffffffff]: SINGLE_FP_CONFIG: 0xbf
	device[0xffffffff]: QUEUE_PROPERTIES: 0x2

	device[0xffffffff]: VENDOR_ID: 4294967295
	device[0xffffffff]: MAX_COMPUTE_UNITS: 8
	device[0xffffffff]: MAX_WORK_ITEM_DIMENSIONS: 3
	device[0xffffffff]: MAX_WORK_GROUP_SIZE: 1024
	device[0xffffffff]: PREFERRED_VECTOR_WIDTH_CHAR: 16
	device[0xffffffff]: PREFERRED_VECTOR_WIDTH_SHORT: 8
	device[0xffffffff]: PREFERRED_VECTOR_WIDTH_INT: 4
	device[0xffffffff]: PREFERRED_VECTOR_WIDTH_LONG: 2
	device[0xffffffff]: PREFERRED_VECTOR_WIDTH_FLOAT: 4
	device[0xffffffff]: PREFERRED_VECTOR_WIDTH_DOUBLE: 2
	device[0xffffffff]: MAX_CLOCK_FREQUENCY: 3000
	device[0xffffffff]: ADDRESS_BITS: 64
	device[0xffffffff]: MAX_MEM_ALLOC_SIZE: 1610612736
	device[0xffffffff]: IMAGE_SUPPORT: 1
	device[0xffffffff]: MAX_READ_IMAGE_ARGS: 128
	device[0xffffffff]: MAX_WRITE_IMAGE_ARGS: 8
	device[0xffffffff]: IMAGE2D_MAX_WIDTH: 8192
	device[0xffffffff]: IMAGE2D_MAX_HEIGHT: 8192
	device[0xffffffff]: IMAGE3D_MAX_WIDTH: 2048
	device[0xffffffff]: IMAGE3D_MAX_HEIGHT: 2048
	device[0xffffffff]: IMAGE3D_MAX_DEPTH: 2048
	device[0xffffffff]: MAX_SAMPLERS: 16
	device[0xffffffff]: MAX_PARAMETER_SIZE: 4096
	device[0xffffffff]: MEM_BASE_ADDR_ALIGN: 1024
	device[0xffffffff]: MIN_DATA_TYPE_ALIGN_SIZE: 128
	device[0xffffffff]: GLOBAL_MEM_CACHELINE_SIZE: 6291456
	device[0xffffffff]: GLOBAL_MEM_CACHE_SIZE: 64
	device[0xffffffff]: GLOBAL_MEM_SIZE: 6442450944
	device[0xffffffff]: MAX_CONSTANT_BUFFER_SIZE: 65536
	device[0xffffffff]: MAX_CONSTANT_ARGS: 8
	device[0xffffffff]: LOCAL_MEM_SIZE: 32768
	device[0xffffffff]: ERROR_CORRECTION_SUPPORT: 0
	device[0xffffffff]: PROFILING_TIMER_RESOLUTION: 1
	device[0xffffffff]: ENDIAN_LITTLE: 1
	device[0xffffffff]: AVAILABLE: 1
	device[0xffffffff]: COMPILER_AVAILABLE: 1


	device[0x1022700]: NAME: GeForce GTX 750 Ti
	device[0x1022700]: VENDOR: NVIDIA
	device[0x1022700]: PROFILE: FULL_PROFILE
	device[0x1022700]: VERSION: OpenCL 1.2 
	device[0x1022700]: EXTENSIONS: cl_APPLE_SetMemObjectDestructor cl_APPLE_ContextLoggingFunctions cl_APPLE_clut cl_APPLE_query_kernel_names cl_APPLE_gl_sharing cl_khr_gl_event cl_khr_byte_addressable_store 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_APPLE_fp64_basic_ops cl_khr_fp64 cl_khr_3d_image_writes cl_khr_depth_images cl_khr_gl_depth_images cl_khr_gl_msaa_sharing cl_khr_image2d_from_buffer cl_APPLE_ycbcr_422 cl_APPLE_rgb_422 
	device[0x1022700]: DRIVER_VERSION: 10.5.2 346.02.03f06

	device[0x1022700]: Type: GPU 
	device[0x1022700]: EXECUTION_CAPABILITIES: Kernel 
	device[0x1022700]: GLOBAL_MEM_CACHE_TYPE: None (0)
	device[0x1022700]: CL_DEVICE_LOCAL_MEM_TYPE: Local (1)
	device[0x1022700]: SINGLE_FP_CONFIG: 0x9f
	device[0x1022700]: QUEUE_PROPERTIES: 0x2

	device[0x1022700]: VENDOR_ID: 16918272
	device[0x1022700]: MAX_COMPUTE_UNITS: 5
	device[0x1022700]: MAX_WORK_ITEM_DIMENSIONS: 3
	device[0x1022700]: MAX_WORK_GROUP_SIZE: 1024
	device[0x1022700]: PREFERRED_VECTOR_WIDTH_CHAR: 1
	device[0x1022700]: PREFERRED_VECTOR_WIDTH_SHORT: 1
	device[0x1022700]: PREFERRED_VECTOR_WIDTH_INT: 1
	device[0x1022700]: PREFERRED_VECTOR_WIDTH_LONG: 1
	device[0x1022700]: PREFERRED_VECTOR_WIDTH_FLOAT: 1
	device[0x1022700]: PREFERRED_VECTOR_WIDTH_DOUBLE: 1
	device[0x1022700]: MAX_CLOCK_FREQUENCY: 1110
	device[0x1022700]: ADDRESS_BITS: 32
	device[0x1022700]: MAX_MEM_ALLOC_SIZE: 536870912
	device[0x1022700]: IMAGE_SUPPORT: 1
	device[0x1022700]: MAX_READ_IMAGE_ARGS: 256
	device[0x1022700]: MAX_WRITE_IMAGE_ARGS: 16
	device[0x1022700]: IMAGE2D_MAX_WIDTH: 16384
	device[0x1022700]: IMAGE2D_MAX_HEIGHT: 16384
	device[0x1022700]: IMAGE3D_MAX_WIDTH: 2048
	device[0x1022700]: IMAGE3D_MAX_HEIGHT: 2048
	device[0x1022700]: IMAGE3D_MAX_DEPTH: 2048
	device[0x1022700]: MAX_SAMPLERS: 32
	device[0x1022700]: MAX_PARAMETER_SIZE: 4352
	device[0x1022700]: MEM_BASE_ADDR_ALIGN: 1024
	device[0x1022700]: MIN_DATA_TYPE_ALIGN_SIZE: 128
	device[0x1022700]: GLOBAL_MEM_CACHELINE_SIZE: 0
	device[0x1022700]: GLOBAL_MEM_CACHE_SIZE: 0
	device[0x1022700]: GLOBAL_MEM_SIZE: 2147483648
	device[0x1022700]: MAX_CONSTANT_BUFFER_SIZE: 65536
	device[0x1022700]: MAX_CONSTANT_ARGS: 9
	device[0x1022700]: LOCAL_MEM_SIZE: 49152
	device[0x1022700]: ERROR_CORRECTION_SUPPORT: 0
	device[0x1022700]: PROFILING_TIMER_RESOLUTION: 1000
	device[0x1022700]: ENDIAN_LITTLE: 1
	device[0x1022700]: AVAILABLE: 1
	device[0x1022700]: COMPILER_AVAILABLE: 1


	device[0x2022700]: NAME: Graphics Device
	device[0x2022700]: VENDOR: NVIDIA
	device[0x2022700]: PROFILE: FULL_PROFILE
	device[0x2022700]: VERSION: OpenCL 1.2 
	device[0x2022700]: EXTENSIONS: cl_APPLE_SetMemObjectDestructor cl_APPLE_ContextLoggingFunctions cl_APPLE_clut cl_APPLE_query_kernel_names cl_APPLE_gl_sharing cl_khr_gl_event cl_khr_byte_addressable_store 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_APPLE_fp64_basic_ops cl_khr_fp64 cl_khr_3d_image_writes cl_khr_depth_images cl_khr_gl_depth_images cl_khr_gl_msaa_sharing cl_khr_image2d_from_buffer cl_APPLE_ycbcr_422 cl_APPLE_rgb_422 
	device[0x2022700]: DRIVER_VERSION: 10.5.2 346.02.03f06

	device[0x2022700]: Type: GPU 
	device[0x2022700]: EXECUTION_CAPABILITIES: Kernel 
	device[0x2022700]: GLOBAL_MEM_CACHE_TYPE: None (0)
	device[0x2022700]: CL_DEVICE_LOCAL_MEM_TYPE: Local (1)
	device[0x2022700]: SINGLE_FP_CONFIG: 0x9f
	device[0x2022700]: QUEUE_PROPERTIES: 0x2

	device[0x2022700]: VENDOR_ID: 33695488
	device[0x2022700]: MAX_COMPUTE_UNITS: 6
	device[0x2022700]: MAX_WORK_ITEM_DIMENSIONS: 3
	device[0x2022700]: MAX_WORK_GROUP_SIZE: 1024
	device[0x2022700]: PREFERRED_VECTOR_WIDTH_CHAR: 1
	device[0x2022700]: PREFERRED_VECTOR_WIDTH_SHORT: 1
	device[0x2022700]: PREFERRED_VECTOR_WIDTH_INT: 1
	device[0x2022700]: PREFERRED_VECTOR_WIDTH_LONG: 1
	device[0x2022700]: PREFERRED_VECTOR_WIDTH_FLOAT: 1
	device[0x2022700]: PREFERRED_VECTOR_WIDTH_DOUBLE: 1
	device[0x2022700]: MAX_CLOCK_FREQUENCY: 1316
	device[0x2022700]: ADDRESS_BITS: 32
	device[0x2022700]: MAX_MEM_ALLOC_SIZE: 536870912
	device[0x2022700]: IMAGE_SUPPORT: 1
	device[0x2022700]: MAX_READ_IMAGE_ARGS: 256
	device[0x2022700]: MAX_WRITE_IMAGE_ARGS: 16
	device[0x2022700]: IMAGE2D_MAX_WIDTH: 16384
	device[0x2022700]: IMAGE2D_MAX_HEIGHT: 16384
	device[0x2022700]: IMAGE3D_MAX_WIDTH: 2048
	device[0x2022700]: IMAGE3D_MAX_HEIGHT: 2048
	device[0x2022700]: IMAGE3D_MAX_DEPTH: 2048
	device[0x2022700]: MAX_SAMPLERS: 32
	device[0x2022700]: MAX_PARAMETER_SIZE: 4352
	device[0x2022700]: MEM_BASE_ADDR_ALIGN: 1024
	device[0x2022700]: MIN_DATA_TYPE_ALIGN_SIZE: 128
	device[0x2022700]: GLOBAL_MEM_CACHELINE_SIZE: 0
	device[0x2022700]: GLOBAL_MEM_CACHE_SIZE: 0
	device[0x2022700]: GLOBAL_MEM_SIZE: 2147483648
	device[0x2022700]: MAX_CONSTANT_BUFFER_SIZE: 65536
	device[0x2022700]: MAX_CONSTANT_ARGS: 9
	device[0x2022700]: LOCAL_MEM_SIZE: 49152
	device[0x2022700]: ERROR_CORRECTION_SUPPORT: 0
	device[0x2022700]: PROFILING_TIMER_RESOLUTION: 1000
	device[0x2022700]: ENDIAN_LITTLE: 1
	device[0x2022700]: AVAILABLE: 1
	device[0x2022700]: COMPILER_AVAILABLE: 1


	device[0x3022700]: NAME: Graphics Device
	device[0x3022700]: VENDOR: NVIDIA
	device[0x3022700]: PROFILE: FULL_PROFILE
	device[0x3022700]: VERSION: OpenCL 1.2 
	device[0x3022700]: EXTENSIONS: cl_APPLE_SetMemObjectDestructor cl_APPLE_ContextLoggingFunctions cl_APPLE_clut cl_APPLE_query_kernel_names cl_APPLE_gl_sharing cl_khr_gl_event cl_khr_byte_addressable_store 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_APPLE_fp64_basic_ops cl_khr_fp64 cl_khr_3d_image_writes cl_khr_depth_images cl_khr_gl_depth_images cl_khr_gl_msaa_sharing cl_khr_image2d_from_buffer cl_APPLE_ycbcr_422 cl_APPLE_rgb_422 
	device[0x3022700]: DRIVER_VERSION: 10.5.2 346.02.03f06

	device[0x3022700]: Type: GPU 
	device[0x3022700]: EXECUTION_CAPABILITIES: Kernel 
	device[0x3022700]: GLOBAL_MEM_CACHE_TYPE: None (0)
	device[0x3022700]: CL_DEVICE_LOCAL_MEM_TYPE: Local (1)
	device[0x3022700]: SINGLE_FP_CONFIG: 0x9f
	device[0x3022700]: QUEUE_PROPERTIES: 0x2

	device[0x3022700]: VENDOR_ID: 50472704
	device[0x3022700]: MAX_COMPUTE_UNITS: 6
	device[0x3022700]: MAX_WORK_ITEM_DIMENSIONS: 3
	device[0x3022700]: MAX_WORK_GROUP_SIZE: 1024
	device[0x3022700]: PREFERRED_VECTOR_WIDTH_CHAR: 1
	device[0x3022700]: PREFERRED_VECTOR_WIDTH_SHORT: 1
	device[0x3022700]: PREFERRED_VECTOR_WIDTH_INT: 1
	device[0x3022700]: PREFERRED_VECTOR_WIDTH_LONG: 1
	device[0x3022700]: PREFERRED_VECTOR_WIDTH_FLOAT: 1
	device[0x3022700]: PREFERRED_VECTOR_WIDTH_DOUBLE: 1
	device[0x3022700]: MAX_CLOCK_FREQUENCY: 1316
	device[0x3022700]: ADDRESS_BITS: 32
	device[0x3022700]: MAX_MEM_ALLOC_SIZE: 536870912
	device[0x3022700]: IMAGE_SUPPORT: 1
	device[0x3022700]: MAX_READ_IMAGE_ARGS: 256
	device[0x3022700]: MAX_WRITE_IMAGE_ARGS: 16
	device[0x3022700]: IMAGE2D_MAX_WIDTH: 16384
	device[0x3022700]: IMAGE2D_MAX_HEIGHT: 16384
	device[0x3022700]: IMAGE3D_MAX_WIDTH: 2048
	device[0x3022700]: IMAGE3D_MAX_HEIGHT: 2048
	device[0x3022700]: IMAGE3D_MAX_DEPTH: 2048
	device[0x3022700]: MAX_SAMPLERS: 32
	device[0x3022700]: MAX_PARAMETER_SIZE: 4352
	device[0x3022700]: MEM_BASE_ADDR_ALIGN: 1024
	device[0x3022700]: MIN_DATA_TYPE_ALIGN_SIZE: 128
	device[0x3022700]: GLOBAL_MEM_CACHELINE_SIZE: 0
	device[0x3022700]: GLOBAL_MEM_CACHE_SIZE: 0
	device[0x3022700]: GLOBAL_MEM_SIZE: 2147483648
	device[0x3022700]: MAX_CONSTANT_BUFFER_SIZE: 65536
	device[0x3022700]: MAX_CONSTANT_ARGS: 9
	device[0x3022700]: LOCAL_MEM_SIZE: 49152
	device[0x3022700]: ERROR_CORRECTION_SUPPORT: 0
	device[0x3022700]: PROFILING_TIMER_RESOLUTION: 1000
	device[0x3022700]: ENDIAN_LITTLE: 1
	device[0x3022700]: AVAILABLE: 1
	device[0x3022700]: COMPILER_AVAILABLE: 1
TomsMacPro:MacCLinfo Tom$
ID: 1788846 · Report as offensive
Profile jason_gee
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 24 Nov 06
Posts: 7489
Credit: 91,093,184
RAC: 0
Australia
Message 1788852 - Posted: 19 May 2016, 23:53:41 UTC - in response to Message 1788846.  

Missing names and compute capabilities imply a driver issue there. Probably the compute capability fields are zero and omitted, which would trigger the behaviour you see in the Boinc client.
"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.
ID: 1788852 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1788854 - Posted: 19 May 2016, 23:57:51 UTC - in response to Message 1788852.  
Last modified: 20 May 2016, 0:00:44 UTC

Except the Compute Capabilities are listed by BOINC and in El Capitan the cards are identified as GTX 950. It didn't seem to make a difference.
Thu May 19 08:06:37 2016 | | Starting BOINC client version 7.6.22 for x86_64-apple-darwin
Thu May 19 08:06:37 2016 | | log flags: file_xfer, sched_ops, task, sched_op_debug
Thu May 19 08:06:37 2016 | | Libraries: libcurl/7.39.0 OpenSSL/1.0.1j zlib/1.2.5 c-ares/1.10.0
Thu May 19 08:06:37 2016 | | Data directory: /Volumes/Mov1/BOINC/Yosemite/BOINC Data
Thu May 19 08:06:38 2016 | | NVIDIA GPU 1: GeForce GTX 950 cannot be used for CUDA or OpenCL computation with CUDA driver 6.5 or later
Thu May 19 08:06:38 2016 | | NVIDIA GPU 2: GeForce GTX 950 cannot be used for CUDA or OpenCL computation with CUDA driver 6.5 or later
Thu May 19 08:06:38 2016 | | CUDA: NVIDIA GPU 0: GeForce GTX 950 (driver version 7.5.29, CUDA version 7.5, compute capability 5.2, 2048MB, 1899MB available, 2022 GFLOPS peak)
Thu May 19 08:06:38 2016 | | CUDA: NVIDIA GPU 1: GeForce GTX 750 Ti (driver version 7.5.29, CUDA version 7.5, compute capability 5.0, 2048MB, 1906MB available, 1421 GFLOPS peak)
Thu May 19 08:06:38 2016 | | CUDA: NVIDIA GPU 2: GeForce GTX 950 (driver version 7.5.29, CUDA version 7.5, compute capability 5.2, 2048MB, 1810MB available, 2022 GFLOPS peak)
Thu May 19 08:06:38 2016 | | OpenCL: NVIDIA GPU 1: GeForce GTX 750 Ti (driver version 10.11.5 346.03.06f01, device version OpenCL 1.2, 2048MB, 1906MB available, 1421 GFLOPS peak)
Thu May 19 08:06:38 2016 | | OpenCL: NVIDIA GPU 1: GeForce GTX 950 (driver version 10.11.5 346.03.06f01, device version OpenCL 1.2, 2048MB, 2048MB available, 758 GFLOPS peak)
Thu May 19 08:06:38 2016 | | OpenCL: NVIDIA GPU 2: GeForce GTX 950 (driver version 10.11.5 346.03.06f01, device version OpenCL 1.2, 2048MB, 2048MB available, 758 GFLOPS peak)
Thu May 19 08:06:38 2016 | | OpenCL CPU: Intel(R) Xeon(R) CPU E5472 @ 3.00GHz (OpenCL driver vendor: Apple, driver version 1.1, device version OpenCL 1.2)
Thu May 19 08:06:38 2016 | SETI@home | Found app_info.xml; using anonymous platform
Thu May 19 08:06:38 2016 | | App version needs OpenCL but GPU doesn't support it
Thu May 19 08:06:38 2016 | SETI@home Beta Test | Found app_info.xml; using anonymous platform
Thu May 19 08:06:38 2016 | | App version needs OpenCL but GPU doesn't support it
Thu May 19 08:06:38 2016 | | Version change (7.6.32 -> 7.6.22)
Thu May 19 08:06:39 2016 | | Processor: 8 GenuineIntel Intel(R) Xeon(R) CPU E5472 @ 3.00GHz [x86 Family 6 Model 23 Stepping 6]
Thu May 19 08:06:39 2016 | | OS: Mac OS X 10.11.4 (Darwin 15.4.0)
ID: 1788854 · Report as offensive
Profile jason_gee
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 24 Nov 06
Posts: 7489
Credit: 91,093,184
RAC: 0
Australia
Message 1788860 - Posted: 20 May 2016, 0:24:58 UTC - in response to Message 1788854.  

Could be they're matching up Cuda-OpenCL Devices by name or similar parameter then (would have to look at the current detection code later). Only problem with that is the only guaranteed way to get the same device in the different enumerations, is by PCIe Bus+Slot# .

What happens if you do just the 2 x 950s ?
"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.
ID: 1788860 · Report as offensive
Previous · 1 . . . 23 · 24 · 25 · 26 · 27 · 28 · 29 . . . 58 · Next

Message boards : Number crunching : I've Built a Couple OSX CUDA Apps...


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.