Message boards :
Number crunching :
MAC OS X El Capitan and NVIDIA Web Driver.
Message board moderation
Previous · 1 · 2 · 3 · Next
Author | Message |
---|---|
Zalster Send message Joined: 27 May 99 Posts: 5517 Credit: 528,817,460 RAC: 242 |
TL, You can try this product. I use it when I need one for those files http://7zx.en.softonic.com/mac Of course if TBar knows of a better program go with his recommendation |
jason_gee Send message Joined: 24 Nov 06 Posts: 7489 Credit: 91,093,184 RAC: 0 |
Probably that's the one I use as well, which I can verify later. "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. |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
I did try updating BOINC but downgraded it again because there was issue I was having with the last version. I can't remember what it was but it annoyed me enough that it forced me to revert to a older BOINC manager. I'm seeing another Laptop with the same strangeness. This task was normal, like most I've seem from that host; http://setiathome.berkeley.edu/result.php?resultid=4775667241 This task a while later isn't normal; http://setiathome.berkeley.edu/result.php?resultid=4775963217 That's the first time I've seen a task like that from that host, and he has been running the App for a while. Still looks better than most of the other LapTops though. Hmmm, could be the Apple driver isn't working CUDA correctly on the LapTops. I haven't seen that on the desktops. I would suggest trying the nVidia driver and see it it continues. The current driver from nVidia for 10.11.3 is here; http://www.nvidia.com/download/driverResults.aspx/99119/en-us If it won't work on the target machine, it won't install. Things to remember about the nVidia Webdriver; Each OS Update will require a New Driver, therefore, wait a few days and make sure a New driver is available BEFORE you run the Apple Update. After the first install, you can check the nVidia preference pane for updates and install the driver update from the Preference pane. All I can say is it's strange no one has posted about the stderr.txt before. I suppose as long as the App works, and the App Does work once BOINC assigns the card, most people are oblivious to the stderr.txt. I'm glad it doesn't happen on the desktops though, it would drive me nuts. Hmmmm, I wonder if that may be why the OpenCL App works so poorly on the nVidia Laptops... |
TimeLord04 Send message Joined: 9 Mar 06 Posts: 21140 Credit: 33,933,039 RAC: 23 |
e-Mailed file to friend with MAC and Linux... He used Linux to Unzip the .7z file; recompressed in .tar.gz and e-Mailed that back to me. Downloaded to my Desktop in El Capitan, and Opened it with the MAC Archiver Utility... SUCCESS!!! I have the files!!!!! :-) TL TimeLord04 Have TARDIS, will travel... Come along K-9! Join Calm Chaos |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
I'm still using http://www.macupdate.com/app/mac/20526/7zx on my machine. macupdate.com is a respected Mac site and I would trust them over other non-Apple sites. They probably have more Apps for .7z on the site. Just remember, the Tasks already assigned will be Lost if the app_info and client_state.xml don't match. If you add an app_info you need to edit the client_state.xml to match the app_info for Every Task you already have. In the client_state.xml, you would change the <version_num> and <plan_class> on every task in the results section. Also, there are Plan Classes reserved and if you use one of the reserved plan classes the server will apply the rules for that reserved plan class. So, you don't want to use an OpenCL plan class name for a CUDA App, and vice versa. That's why when switching from an OpenCL App to a CUDA App you need to change the plan class to a CUDA name such as what's in the example. <result> <name>15oc10ab.14769.141267.10.37.215_0</name> <final_cpu_time>0.000000</final_cpu_time> <final_elapsed_time>0.000000</final_elapsed_time> <exit_status>0</exit_status> <state>2</state> <platform>x86_64-apple-darwin</platform> <version_num>802</version_num> <plan_class>cuda65</plan_class> <wu_name>15oc10ab.14769.141267.10.37.215</wu_name> <report_deadline>1459411482.000000</report_deadline> <received_time>1457643301.679192</received_time> <file_ref> <file_name>15oc10ab.14769.141267.10.37.215_0_0</file_name> <open_name>result.sah</open_name> </file_ref> </result> Otherwise the existing tasks will become Ghosts if the app_info and client_state don't match. |
TimeLord04 Send message Joined: 9 Mar 06 Posts: 21140 Credit: 33,933,039 RAC: 23 |
I'm still using http://www.macupdate.com/app/mac/20526/7zx on my machine. macupdate.com is a respected Mac site and I would trust them over other non-Apple sites. They probably have more Apps for .7z on the site. I just want to confirm; this App is for CPU or GPU, or is it for both??? I ONLY crunch GPU... If this is only for CPU, it's useless to me. TL TimeLord04 Have TARDIS, will travel... Come along K-9! Join Calm Chaos |
TimeLord04 Send message Joined: 9 Mar 06 Posts: 21140 Credit: 33,933,039 RAC: 23 |
TBar, CUDA 65 Toolkit does NOT specify compatibility with OS X 10.11, El Capitan. There IS a 7.5 Toolkit which IS compatible. NOTE: I've already installed the CUDA 7.5.25 Driver for El Capitan. What does the Toolkit do??? Is the 7.5 Toolkit backwards compatible to your 6.5 App??? With all this extra stuff, I'm getting that uncomfortable feeling... The same feeling I had installing Snow Leopard and El Capitan with all the Hackintosh stuff... I REALLY like automatic installers for Apps - like Lunatics. An installer gets things to the right locations with the right modifications. Me, I could end up screwing something up majorly!!! Will this EVENTUALLY end up in Lunatics??? If so, I think I'll wait for the Lunatics Installer. I don't trust myself modifying an app_info.xml file... I'm lucky I can modify my app_config.xml that Joe Segur created for me. TL TimeLord04 Have TARDIS, will travel... Come along K-9! Join Calm Chaos |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
I just want to confirm; this App is for CPU or GPU, or is it for both??? I ONLY crunch GPU... If this is only for CPU, it's useless to me. setiathome_x41zi_x86_64-apple-darwin_cuda65 Is for FERMI CUDA GPUs and up. MBv8_8.05r3344_sse41_x86_64-apple-darwin Is for CPUs with at least SSE41. If you don't want to run the CPU just un-select it in the SETI Web preferences. On your CPU, it would probably be about twice as fast as the stock CPU App. As the down load states, you will need to download and extract the CUDA Libraries libcudart.6.5.dylib and libcufft.6.5.dylib from the CUDA 6.5 Toolkit and add those to the setiathome.berkeley.edu folder. If you just install the Toolkit instead of extracting the libraries, you should reinstall the current CUDA driver before using BOINC. You don't need a working toolkit, all you need is the 2 Library files from the Toolkit. You Must use the 6.5 libraries with the 6.5 App. There has Never Been a Lunatics Installer for OSX, I wouldn't hold my breath for one. To check and make sure CUDA is working, you can use this App; http://cuda-z.sourceforge.net/ If CUDA-Z doesn't see CUDA, don't launch BOINC...it won't work. |
jason_gee Send message Joined: 24 Nov 06 Posts: 7489 Credit: 91,093,184 RAC: 0 |
@Timelord, the Lunatics installers started by myself for Windows, then handed over to Richard Haselgrove for maintenance/updates, represent a pretty significant investment in tooling/infrastructure and time. Alpha, beta and test builds will be unlikely to receive installer status, because incomplete or broken builds are subject to change, and being a manually intensive process to produce the cost outweighs the benefits. So In general, manual/advanced user installation will remain first point of call before a more general release is called for. Any build package (any platform) that doesn't meet pretty stringent checklist for completion, i.e the 'docs' folder - Some limited form of user documentation (Advanced user or otherwise, updated2) - Complete set of the GPL docs ( including updated Author(s) and GPL files ) - link in the readme to sources Should really be considered a pre-release test build at best. Now for Mac 'Installers' the infrastructure isn't in place yet (and is limited to advanced users for Linux, and a trial stock deployment). Most likely Cuda multibeam will be the first to have installers/scripts in some form across all three main platforms, followed sometime afterwards by opt-in auto-update, and registered tester access. When that exists in automated form, all our lives will be a little easier. "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. |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14654 Credit: 200,643,578 RAC: 874 |
@Timelord, the Lunatics installers started by myself for Windows, then handed over to Richard Haselgrove for maintenance/updates, represent a pretty significant investment in tooling/infrastructure and time. Yes, we did a lot of learning in the early days, but it's pretty routine now. Perhaps the most important thing that we learned was how the 'Anonymous Platform' (app_info.xml) mechanism works, and how to use it to best advantage. TBar wrote: Just remember, the Tasks already assigned will be Lost if the app_info and client_state.xml don't match. If you add an app_info you need to edit the client_state.xml to match the app_info for Every Task you already have. In the client_state.xml, you would change the <version_num> and <plan_class> on every task in the results section. And that is not how to do it. A major part of updating the installer each time is making sure that the app_info templates match the entries likely to be found in user client_state files - so that users who have only ever run stock apps, or previous installer versions, don't lose work in progress. That's greatly helped by the way Eric handles application deployment on this project: he likes to allow plenty of time for applications to mature in Beta, and then, once deployed to Main, apps stay deployed for a long time - because they've been done right and don't need correcting after testing. Otherwise, every time an app is updated, we need to re-deploy the installer to match the new version numbers. That's another reason why there isn't an installer designed to install Beta apps on the Beta project: we expect Beta apps to change rapidly during development, and apps to pass through a multitude of version numbers before being released to Main as a stable product with an X.00 version number. And that's why I keep asking - usually without success - that developers exercise some thought and planning when releasing test packages containing sample app_info files. Please make it clear throughout the process whether your app_info has been designed to match the current Beta or Main versions: if you feel that your product has reached the stage where it merits more exhaustive testing on the Main project, re-release it with an app_info that fits into the Main version-numbering schema. And keep the Main and Beta packages separate, clearly labelled, on your download resources. That way, volunteer testers can concentrate on testing your application, rather than wasting time learning how to deploy it properly. |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
@Timelord, the Lunatics installers started by myself for Windows, then handed over to Richard Haselgrove for maintenance/updates, represent a pretty significant investment in tooling/infrastructure and time. Yes, we did a lot of learning in the early days, but it's pretty routine now. Perhaps the most important thing that we learned was how the 'Anonymous Platform' (app_info.xml) mechanism works, and how to use it to best advantage. This is a Mac thread. There aren't any installers...remember? Hey, just Forget I told MAC users how to keep from creating Ghosts. Instead just follow my first suggestion; Unless you want to edit the state file to set the new plan_class I suggest you finish the tasks you have first, or you will create Ghosts. That will work for most anyone, except the impatient ones that want it to work Now and not wait. For those there is the option I suggested, or they can just forget about it, and create the Ghosts. In other current events, Zalster has apparently fixed his Mac, http://setiathome.berkeley.edu/result.php?resultid=4784537842 At least it looks to be working well now. Zalster, what did you do to fix it? Oh, to unpack the ToolKit use this tool, http://www.macupdate.com/app/mac/16357/unpkg Then look in the CUDAToolkit/lib folder for the two 6.5 libraries. It doesn't get much easier... |
William Send message Joined: 14 Feb 13 Posts: 2037 Credit: 17,689,662 RAC: 0 |
To reiterate, you do not edit client_state.xml. You make an app_info.xml where the plan_classes match what is already there. And that applies to ANY platform. A person who won't read has no advantage over one who can't read. (Mark Twain) |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
To reiterate, you do not edit client_state.xml. You make an app_info.xml where the plan_classes match what is already there. Have you tried using a reserved OpenCL Plan Class on a CUDA App lately? The last time I tried it BOINC told me the App Needed OpenCL which it didn't have and trashed All My tasks. Maybe it's changed, I dunno, I only tried it that once. |
William Send message Joined: 14 Feb 13 Posts: 2037 Credit: 17,689,662 RAC: 0 |
To reiterate, you do not edit client_state.xml. You make an app_info.xml where the plan_classes match what is already there. that's rebranding openCL to cuda. without looking at a stock Mac opencl_nvidia_mac client_state.xml entry set, I can't say how you would have to adjust app_info.xml to get those switched, and whether it's possible. should be, tasks are tasks, but the checkpointing format between the apps is not necessarily the same. I would run down the openCL tasks and start with a clean sheet, anyway. And yes, you can just rebrand in client_state.xml and have a matching app_info.xml but tinkering with client_state.xml can have catastrophic results, if not done 100% right. Also, you need entries in app_info.xml for CPU tasks, if you are crunching on CPU - using either the stock app or, if available and desired, an optimised one. Switching a stock rig over to anonymous platform with tasks on board requires a lot of thought and care with app_info.xml. Which is why people are so happy using the installer under Windows :) A person who won't read has no advantage over one who can't read. (Mark Twain) |
Zalster Send message Joined: 27 May 99 Posts: 5517 Credit: 528,817,460 RAC: 242 |
Updated the nvidia driver, but there was 1 unexpected crash overnight,which I can only assume was do to the new driver. I reinstalled newer BOINC as well but I don't think that what resolved the issue. |
TimeLord04 Send message Joined: 9 Mar 06 Posts: 21140 Credit: 33,933,039 RAC: 23 |
Call me a coward; but, I'm NOT comfortable making these changes to a newly running system. I had A REALLY hard time of it creating this Hackintosh. It's running pretty smoothly now; I don't want that to change. I HIGHLY respect what TBar has done with these Apps. I'm just NOT the person to get them installed manually. I don't trust myself enough. I will keep the stock MAC Apps for a good while longer before reconsidering. Right now I'm on the Prometheus - Win 7 side of the system, running down the BOINC cache. Due to multiple changes to the Win 7 side since getting MAC up and running, I also need to re-clone the Win 7 drive before upgrading that to Win 10 Pro. I've almost got this entire system right where I want it to be; I don't want to screw anything up. There's too many changes between Yosemite and El Capitan that keep giving me that uncomfortable feeling making ANY changes to the MAC OS side. SIP Security being the most worrisome. Xcode stuff being another. I just don't know enough about this stuff to want to "play" around more with it. It works, now, I'm just going to leave it this way. TL TimeLord04 Have TARDIS, will travel... Come along K-9! Join Calm Chaos |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
That's one of the reasons I'm still using Yosemite. I had a couple driver crashes with the early versions of El Capitan. I don't remember one of those in Yosemite. They have been claiming the LapTop drivers are Beta since early on in Yosemite, I'm not sure how much longer they are going to keep calling them beta for Laptops, http://www.nvidia.com/download/driverResults.aspx/97606/en-us One has to wonder how the OpenCL App works with the nVidia driver, OpenCL on the Laptops doesn't work very well at all with the Apple driver. Have you noticed any change in screen response since changing drivers? The only time I notice any slowdown with CUDA is when running one of those Un-Labeled VLARs, otherwise I don't notice any lag. Much better than my Mac with the older ATI cards running OpenCL MB. Even the mid-range tasks would make the machine annoying. The near VLARs made it unusable. I don't have that problem anymore. The only time I didn't have screen Lag with the ATI cards running OpenCL was when running shorties or APs, both are becoming difficult to find lately. |
woohoo Send message Joined: 30 Oct 13 Posts: 972 Credit: 165,671,404 RAC: 5 |
|
Zalster Send message Joined: 27 May 99 Posts: 5517 Credit: 528,817,460 RAC: 242 |
Really haven't seen any lag with the new driver. I always see some lag when I run BOINC, why I restrict to 4 core of 8 Ever since you had me do the cuda update to 6.5 I haven't seen any OpenCl on this computer. Only the Nivida now is crunching. Before the upgrade, both the Nivida and Intel would crunch so I'm assuming something in the cuda update didn't go well with the Intel portion. |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14654 Credit: 200,643,578 RAC: 874 |
Ever since you had me do the cuda update to 6.5 I haven't seen any OpenCl on this computer. Only the Nivida now is crunching. Before the upgrade, both the Nivida and Intel would crunch so I'm assuming something in the cuda update didn't go well with the Intel portion. You probably didn't add the intel_gpu application to your new app_info.xml file. Edit - yes, your uncompleted intel gpu tasks like task 4693789507 were supplied as stock apps back in January. Unless you added an anonymous platform 'wrapper' in app_info.xml to re-declare that application for the new mode, nothing happens. You'll probably have messages displayed in BOINC Manager and the Event Log to tell you that - "no application for task...", or words to that effect. |
©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.