Posts by PinkPenguin
log in
1) Message boards : Number crunching : MAC OS X 32-bit CUDA App (Message 10588)
Posted 2602 days ago by Profile PinkPenguin
Just got back and saw the reply. Many thanks Crunch3r. I will give it a go this evening and let you know...


Tried it.... Looks OK. Thanks again.
2) Message boards : Number crunching : MAC OS X 32-bit CUDA App (Message 10585)
Posted 2603 days ago by Profile PinkPenguin
Just got back and saw the reply. Many thanks Crunch3r. I will give it a go this evening and let you know...
3) Message boards : Number crunching : MAC OS X 32-bit CUDA App (Message 10563)
Posted 2606 days ago by Profile PinkPenguin
New news: PG OSX/CUDA app requires 3.2. And 3.2 does not work with Collatz. I would really like to run both, or use one project or the other as a back-up. Co can a 3.2 app please be created?


I would second this request. I have had to update update Cuda driver (to v3.2.17), toolkit and SDK for another non-boinc project and now Collatz doesn't run anymore.

Seeing as the same versions are out for Windows and Linux it might be a good idea to have Cuda v3.2 apps ready even if these drivers are listed by NVIDIA as development drivers (at the moment the optimized apps are listed for Cuda v3.1)...
4) Message boards : Macintosh : how to run CUDA on a mac book pro? (Message 10417)
Posted 2621 days ago by Profile PinkPenguin
Same here - I made the mistake of updating my cuda driver and toolkit to v3.2.17 and the WUs die as soon as they start.
5) Message boards : Number crunching : MAC OS X 32-bit CUDA App (Message 5473)
Posted 2934 days ago by Profile PinkPenguin
Since it sounds like you had to remove the lib from the app info, I changed the setup so that libcudart.dylib is no longer included with the application download. That should eliminate the need for the app_info file, but the symbolic links still have to be set.


Yes, I removed the references to libcuda and libcudart from app_info as the links make it unnecessary.

Also, it sounds like the 2.3 driver does not include the cuda runtime (libcudart.dylib) and that it needs to be installed with the CUDA Toolkit. Is that correct? It isn't an issue for CUDA 2.2 since the toolkit and driver are in the same install.


The 2.3.1a driver package doesn't contain libcudart.dylib (only libcuda.dylib) so the 2.3.0a toolkit has to be installed (preferably before the 2.3.1a driver package). In both cases I followed the standard package installation procedure for OS X and then created the links to /usr/lib.
6) Message boards : Number crunching : MAC OS X 32-bit CUDA App (Message 5471)
Posted 2934 days ago by Profile PinkPenguin
Same here, I installed the 2.3.0a toolkit first then the 2.3.1a driver without really worrying if they were both necessary (just following the recommendations). I had to create the links and edit the app_info.xml file to remove the references to the libraries. If app_info isn't necessary I'll remove for the next round.

Two units in at around 12.000 secs on a 9600M GT - both waiting for validation but they look OK.

... Only problem with Macbook Pros is that running both CUDA and CPU is really great for frying eggs 'n bacon on the keyboard.... ;)

I have cut out one of the CPUs which brings the temperature back down to normal dual-core processing temperatures with the fan running at 4.000 - 5.000 (which is not the usual silence one expects from Macbooks... Mind you I could try bunging it in the freezer overnight.

I presume the BOINC 6.10.28 version is only available through svn at the moment ?
7) Message boards : Number crunching : MAC OS X 32-bit CUDA App (Message 5464)
Posted 2935 days ago by Profile PinkPenguin
Just set it up on a Macbook Pro using a 9600M GT w. 512Mbyte - followed Paul's instructions and looks like it's running OK with Cuda Toolkit 2.3.0a and Driver 2.3.1a (OS X 10.6.2 / BOINC 6.10.27). First WU is 75% and another 40 minutes to go...

Will let you know this evening when I get back....




Main page · Your account · Message boards


Copyright © 2018 Jon Sonntag; All rights reserved.