I directed you to the thread below, where myself and others mentioned how to overcome the issues of the later NVIDIA drivers running on newer kernels/ubuntu distros: That issue is neither NVIDIA’s or BOINC’s… it’s an issue of who packaged the drivers and any relevant bugs should be filed against it. I never said there wasn’t a problem with the drivers that Ubuntu has in their repositories, in fact I know that the xorg-edgers repository’s 337 drivers include an older kernel 3.12 patch that fails to build nvidia-uvm, probably causing the issues you’re experiencing, possibly mingled with a missing /etc/OpenCL/vendors/nvidia.icd file pointing to the OpenCL library like I mentioned before. We return to the top, if not manually installed NVIDIA registering with DKMS everything works perfectly, including BOINC Note: You must install the ppa “xorg-edgers fresh X crack” to access all of Nvidia drivers. NVIDIA GPUs drivers present but not found Ubuntu to install it only gives an option if the Nvidia 331.38 BOINC works with, as I said before, but when you upgrade from “Software Updates + Additional Drivers”, a top driver system works perfectly but fails to locate BOINC GPUs installed. Made a complete clean install of Ubuntu 14.04-64bit to install the Nvidia 331.67 driver fails to locate BOINC GPUs. Setup… NVIDIA 337.12 drivers, BOINC 7.3.11, and able to run work units from PrimeGrid on CUDA and OpenCL on my GTX Titan Black and Quadro K6000 GPUs just fine… so it’s not a BOINC or NVIDIA issue, simply a misconfiguration on your system. Out of curiosity, I tried out BOINC on Ubuntu 14.04 and it works just fine for me… Update (7 february 2012): if you run this on a busy server, you might want to run. Update (9 December 2010): added requirement for curl. To avoid restarting your computer at the end of installation (the forced reboot seems totally useless), you can just delete the file named RebootPending.txt in BOINC’s folder. On a side note, I just installed BOINC into Windows 7 too. Now, of course, you might want to configure the thing to run at start up, or even as a service, but this is getting out of the scope of this post, and there are actually some guides available for that, here are some pointers: boinccmd -project_attach cee742fga12345b123ab27e51bb6d5c4Īnd that’s it… I don’t understand why noone at BOINC took the time to write down those instructions clearly.
Attach a project and your user key to the client using boinccmd, for instance:.Detach the screen (CTRL+A, CTRL+D) or open another terminal.(NB: depending on your Linux version, you may need to install curl, for instance on Ubuntu: apt-get install curl) Launch a screen ( screen), inside which you’ll run run_client (.
Navigate to the newly created subfolder BOINC ( cd BOINC).Get the BOINC client (for instance, wget ).Note your account key (you’ll need it later).For the example, I’ll be creating an account at Quantum Monte Carlo Home by University of Muenster (Germany). Create an account for the project you want.I recently tried to install it on a Linux server, and got lots of trouble figuring out how to configure it using only the command line: as a definitely mainstream program, they seem to revolve around their GUI and the documentation for the command line, although not inexistent, isn’t of much help when it comes to simply configuring the software… So here’s a complete step-by-step guide (even included the properly documented parts) to get it started: BOINC is a large distributed computing project, or more accurately, a piece of software used by a bunch of distributed computing projects.
0 kommentar(er)
