Message boards : News : Important news for Linux crunchers
Author | Message |
---|---|
Hi all, | |
ID: 36577 | Rating: 0 | rate: / Reply Quote | |
Did you send this path to boinc developers also? This is a very annoying thing in linux version. | |
ID: 36590 | Rating: 0 | rate: / Reply Quote | |
If Matt doesn't, I'd be happy to. | |
ID: 36591 | Rating: 0 | rate: / Reply Quote | |
Already sent upstream. Should be in the next release. | |
ID: 36593 | Rating: 0 | rate: / Reply Quote | |
I'm probably having a senior moment but what am I supposed to do with that file as I can't get it to do anything? | |
ID: 36594 | Rating: 0 | rate: / Reply Quote | |
Download it, do a "chmod +x boinc" to make it executable, then run it. | |
ID: 36597 | Rating: 0 | rate: / Reply Quote | |
I'm running linux mint 16 but I'm getting errors libssl.so.10, libcrypto.so.10 not found when I run your boinc app. | |
ID: 36600 | Rating: 0 | rate: / Reply Quote | |
Try this build: | |
ID: 36605 | Rating: 0 | rate: / Reply Quote | |
Try this build: ldd boinc_ubuntu libssl.so.1.0.0 => /lib/x86_64-linux-gnu/libssl.so.1.0.0 (0x00007fdaaf900000) libcrypto.so.1.0.0 => /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 (0x00007fdaaf523000) Thu 24 Apr 2014 04:49:30 AM EDT | | CUDA: NVIDIA GPU 0: GeForce GTX 780 Ti (driver version 337.12, CUDA version 6.0, compute capability 3.5, 3072MB, 2759MB available, 5345 GFLOPS peak) It works! thanks! | |
ID: 36606 | Rating: 0 | rate: / Reply Quote | |
Hi Gentoo-10 1 24/04/2014 13.09.11 Starting BOINC client version 7.2.33 for x86_64-pc-linux-gnu Gentoo-10 6 24/04/2014 13.09.11 CUDA: NVIDIA GPU 0: GeForce GTX 780 (driver version unknown, CUDA version 6.0, compute capability 3.5, 3071MB, 2989MB available, 4818 GFLOPS peak) 7 24/04/2014 13.09.11 CUDA: NVIDIA GPU 1: GeForce GTX 780 (driver version unknown, CUDA version 6.0, compute capability 3.5, 3072MB, 3002MB available, 4818 GFLOPS peak) 8 24/04/2014 13.09.11 OpenCL: NVIDIA GPU 0: GeForce GTX 780 (driver version 334.21, device version OpenCL 1.1 CUDA, 3071MB, 2989MB available, 4818 GFLOPS peak) 9 24/04/2014 13.09.11 OpenCL: NVIDIA GPU 1: GeForce GTX 780 (driver version 334.21, device version OpenCL 1.1 CUDA, 3072MB, 3002MB available, 4818 GFLOPS peak) 10 24/04/2014 13.09.11 OpenCL CPU: Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz (OpenCL driver vendor: Intel(R) Corporation, driver version 1.1, device version OpenCL 1.1 (Build 31360.31426)) ldd /usr/bin/boinc linux-vdso.so.1 (0x00007fff317ff000) libcurl.so.4 => /usr/lib64/libcurl.so.4 (0x00007f9bb5bec000) libssl.so.1.0.0 => /usr/lib64/libssl.so.1.0.0 (0x00007f9bb5981000) libcrypto.so.1.0.0 => /usr/lib64/libcrypto.so.1.0.0 (0x00007f9bb55aa000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f9bb53a6000) libz.so.1 => /lib64/libz.so.1 (0x00007f9bb5190000) libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007f9bb4e53000) libXss.so.1 => /usr/lib64/libXss.so.1 (0x00007f9bb4c4f000) libXext.so.6 => /usr/lib64/libXext.so.6 (0x00007f9bb4a3c000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f9bb481f000) libstdc++.so.6 => /usr/lib/gcc/x86_64-pc-linux-gnu/4.8.2/libstdc++.so.6 (0x00007f9bb4515000) libm.so.6 => /lib64/libm.so.6 (0x00007f9bb4220000) libgcc_s.so.1 => /usr/lib/gcc/x86_64-pc-linux-gnu/4.8.2/libgcc_s.so.1 (0x00007f9bb400a000) libc.so.6 => /lib64/libc.so.6 (0x00007f9bb3c5f000) libldap-2.4.so.2 => /usr/lib64/libldap-2.4.so.2 (0x00007f9bb3a15000) liblber-2.4.so.2 => /usr/lib64/liblber-2.4.so.2 (0x00007f9bb3805000) libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f9bb35ee000) /lib64/ld-linux-x86-64.so.2 (0x00007f9bb5e4f000) libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007f9bb33cd000) libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007f9bb31c9000) libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 (0x00007f9bb2fc3000) | |
ID: 36607 | Rating: 0 | rate: / Reply Quote | |
Hi huys :D $ ls -lh | grep lib -rw-r--r-- 1 saba users 360K 16 mar 14.20 libcudart.so.4.2.9 -rwxr-xr-x 1 saba users 322K 12 apr 19.12 libcudart.so.6.0 -rw-r--r-- 1 saba users 30M 16 mar 14.20 libcufft.so.4.2.9 -rwxr-xr-x 1 saba users 32M 12 apr 19.41 libcufft.so.6.0 but excutable doesn't find them $ ldd acemd.821-60.bin linux-vdso.so.1 (0x00007fffef10c000) libdl.so.2 => /lib64/libdl.so.2 (0x00007fd097934000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fd097717000) libnvidia-ml.so.1 => /usr/lib64/libnvidia-ml.so.1 (0x00007fd097478000) libcuda.so.1 => /usr/lib64/libcuda.so.1 (0x00007fd096513000) libcudart.so.6.0 => not found libcufft.so.6.0 => not found libstdc++.so.6 => /usr/lib/gcc/x86_64-pc-linux-gnu/4.8.2/libstdc++.so.6 (0x00007fd09620a000) libm.so.6 => /lib64/libm.so.6 (0x00007fd095f15000) libgcc_s.so.1 => /usr/lib/gcc/x86_64-pc-linux-gnu/4.8.2/libgcc_s.so.1 (0x00007fd095cff000) libc.so.6 => /lib64/libc.so.6 (0x00007fd095954000) /lib64/ld-linux-x86-64.so.2 (0x00007fd097b38000) libz.so.1 => /lib64/libz.so.1 (0x00007fd09573e000) librt.so.1 => /lib64/librt.so.1 (0x00007fd095536000) will try to reset the proiject now I'm installing cuda-6.0.37 and I will create a symlink to gpugrid work directory [edit] libraries missing for all excutables $ acemd.800-42.bin acemd.800-55.bin acemd.821-60.bin libcudart.so.4 => not found libcufft.so.4 => not found | |
ID: 36675 | Rating: 0 | rate: / Reply Quote | |
I'm still getting errors on the CUDA6 short tasks on my GTX 560. Yes, I tried the boinc version in this thread. Doesn't make a difference. Almost 98% of all CUDA6 tasks error out either immediately or they crunch for some time and then error out. Error codes don't give a clue about what has gone wrong | |
ID: 36740 | Rating: 0 | rate: / Reply Quote | |
I use the patched (v7.3.15) ubuntu client file above with nvidia-331.38 driver. GPUgrid doesn't get CUDA 6 jobs and run fine with lower version CUDA jobs. | |
ID: 36761 | Rating: 0 | rate: / Reply Quote | |
Hi huys :D As Matt said in the original post, you'll need nvidia driver 334.21 or later to run cuda 6.0 tasks. If you have installed the right drivers, try the following. I would uninstall cuda-6.0.37. The project provides the necessary cuda libraries in the GPUgrid project directory. Try adding the path to the GPUGrid folder to a new file in /etc/ld.so.conf.d directory. sudo nano /etc/ld.so.conf.d/gpugrid.conf on a single line, type in the complete path to your GPUgrid folder and then save the file. next: sudo ldconfig Then check to see if the app finds the libraries. | |
ID: 36762 | Rating: 0 | rate: / Reply Quote | |
You don't need to install CUDA yourself. We ship all the necessary runtime libraries along with the application. | |
ID: 36764 | Rating: 0 | rate: / Reply Quote | |
microchip, | |
ID: 36765 | Rating: 0 | rate: / Reply Quote | |
microchip, I doubt that. I've done stress tests on both its memory and the GPU itself. It passes every time. It crunched without issues in the past the CUDA5 apps. Every since CUDA6 tasks came, they started to fail on it ____________ Team Belgium | |
ID: 36767 | Rating: 0 | rate: / Reply Quote | |
I have a Gigabyte (GV-N66TOC-2GC) GTX660Ti which failed about 1/4 tasks under Linux. Tried different generations of Linux, system updates and a range of different drivers (from 304 to 337) and it kept failing work. It's a dual fan model and ran fairly cool and quiet, so temp probably wasn't an issue. | |
ID: 36774 | Rating: 0 | rate: / Reply Quote | |
tnx for the trick cuda is installed in /opt/ (outside boinc directory) now i'm crunching 1 WU with cuda4.2 so .. $ ldd acemd.800-42.bin linux-vdso.so.1 (0x00007fffeffff000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f050160e000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f05013f1000) libnvidia-ml.so.1 => /usr/lib64/libnvidia-ml.so.1 (0x00007f0501152000) libcuda.so.1 => /usr/lib64/libcuda.so.1 (0x00007f05001ed000) libcudart.so.4 => /home/saba/boinc/projects/www.gpugrid.net/libcudart.so.4 (0x00007f04fff93000) libcufft.so.4 => /home/saba/boinc/projects/www.gpugrid.net/libcufft.so.4 (0x00007f04fdf6b000) libstdc++.so.6 => /usr/lib/gcc/x86_64-pc-linux-gnu/4.8.2/libstdc++.so.6 (0x00007f04fdc62000) libm.so.6 => /lib64/libm.so.6 (0x00007f04fd96d000) libgcc_s.so.1 => /usr/lib/gcc/x86_64-pc-linux-gnu/4.8.2/libgcc_s.so.1 (0x00007f04fd757000) libc.so.6 => /lib64/libc.so.6 (0x00007f04fd3ac000) /lib64/ld-linux-x86-64.so.2 (0x00007f0501812000) libz.so.1 => /lib64/libz.so.1 (0x00007f04fd196000) librt.so.1 => /lib64/librt.so.1 (0x00007f04fcf8e000) waiting to finish | |
ID: 36778 | Rating: 0 | rate: / Reply Quote | |
Hi, I think that says something does not work. | |
ID: 36783 | Rating: 0 | rate: / Reply Quote | |
Carlesa, | |
ID: 36784 | Rating: 0 | rate: / Reply Quote | |
Carlesa, Hi, sure I've spelled wrong ... my English of Google. With the same driver 331.67 GPUGRID CUDA 6 tasks perfectly executed if you use the 7.2.42 BOINC client, but if I use the BOINC client 7.3.15 (which is recommended in GPUGRID) I just get CUDA 4.2 tasks. Just does not make sense since it is clear that 331.67 GPUGRID CUDA6 tasks running perfectly. NOTE: Right now I am running BOINC 7.2.42 and 331.67 Nvidia Cuda 6 one task GPUGRID June flawlessly. I think the mistake is that they have identified the wrong version of the Nvidia driver> 331.49 CUDA 6 support GPUGRID perfectly. | |
ID: 36785 | Rating: 0 | rate: / Reply Quote | |
Hello; Task perfectly completed: Ubuntu 14.04-64bits - Nvidia 331.67 - Boinc 7.2.42. http://www.gpugrid.net/result.php?resultid=9780070 | |
ID: 36790 | Rating: 0 | rate: / Reply Quote | |
Just does not make sense since it is clear that 331.67 GPUGRID CUDA6 tasks running perfectly. Each major version number acquired CUDA 6 support at different minor release points. For scheduling purposes we can use only one driver version number as the threshold above which we send CUDA 6 - the test is a simple numerical comparison. That version is 334.21, since earlier 334s don't support it. Blame Nvidia for this mess - the drivers report a "supported CUDA version", but there are many releases that lie about CUDA 6 capability. Matt | |
ID: 36791 | Rating: 0 | rate: / Reply Quote | |
Blame Nvidia for this mess - the drivers report a "supported CUDA version", but there are many releases that lie about CUDA 6 capability. Hello: I will not be that Nvidia defend their messes but in this case I think it is entirely fair. The 334.21 driver is a Beta released on 03/03/14 the same as is another Beta 337.12 on 08/04/14. Specifically, the 337.12 is quite unstable and not recommended for normal use. The 331.67 of 09/04/2014 is a certified version, ie not BETA, so you would have to make reference to this version and not the other, that is my opinion. | |
ID: 36792 | Rating: 0 | rate: / Reply Quote | |
I use Lubuntu 12.04.4 LTS with all the latest updates as provided by the developers. It uses Nvidia driver 304.116. My cruncher continues to error out on all GPUGrid Cuda 60 WUs. Unless there is some easy method to fix this, I'll just let it continue to make errors until the developers fix this in their distributions. It seems this is a problem to be worked out between GPUGrid/Boinc/Ubuntu and not the users providing crunching power. | |
ID: 36794 | Rating: 0 | rate: / Reply Quote | |
I use Lubuntu 12.04.4 LTS with all the latest updates as provided by the developers. It uses Nvidia driver 304.116. My cruncher continues to error out on all GPUGrid Cuda 60 WUs. Unless there is some easy method to fix this, I'll just let it continue to make errors until the developers fix this in their distributions. It seems this is a problem to be worked out between GPUGrid/Boinc/Ubuntu and not the users providing crunching power. Hello: First is right, it has become common for project managers, software OS, Nvidia etc ... download their problems, failures and / or limitations on the user and offer their time and money has to fight for this to work, if or if. "Lord forgive them for they know not what they do". That said in this thread has a solution for your Ubuntu no download homework Cuda 6 which are cultured to fail for the version you have installed Nvidia Cuda. The other thread has the option to upgrade to Ubuntu 14.04, install Nvidia> 331.67 etc. manually ... well challenging. | |
ID: 36795 | Rating: 0 | rate: / Reply Quote | |
Steve: your options are: | |
ID: 36796 | Rating: 0 | rate: / Reply Quote | |
Matt, | |
ID: 36797 | Rating: 0 | rate: / Reply Quote | |
Steve, | |
ID: 36798 | Rating: 0 | rate: / Reply Quote | |
Matt, | |
ID: 36801 | Rating: 0 | rate: / Reply Quote | |
Steve, I've been crunching on my Ubuntu 12.04 server for GPUGrid for over a year now without problems, frequently updating the BOINC client and NVidia drivers. It may be a little complicated, but once you've got the hang of it, it is straightforward. 1. Remove the existing driver * 2. Add the nouveau driver in the kernel module black list * 3. Install the new driver 4. Reboot
vagelis@vgserver:~$ dpkg-query -W 'nvidia*'
nvidia-180-modaliases
nvidia-185-modaliases
nvidia-current
nvidia-current-modaliases
nvidia-current-updates
nvidia-experimental-304
nvidia-experimental-310
nvidia-libvdpau
nvidia-libvdpau-ia32
nvidia-libvdpau1
nvidia-libvdpau1-ia32
nvidia-settings 304.88-0ubuntu0.0.2
nvidia-vdpau-driver
nvidia-vdpau-driver-ia32 As you see, the output is comprised of two columns, first the package and second the installed version. For packages that are not installed, there is no package version. So, you're looking for packages with a version. The exact packages you're looking for should be named nvidia-<version>, for example nvidia-304 or nvidia-304-updates. You should not remove the package nvidia-common. Then, remove the package with the command "sudo apt-get purge <package>". If the command displays a message about automatically installed packages that are no longer needed and can be removed, you should do it: "sudo apt-get autoremove". 2. Add the nouveau driver in the kernel module black list Edit file /etc/modprobe.d/blacklist.conf with the command "sudo vi /etc/modprobe.d/blacklist.conf", then go to the end of the file by pressing Shift-G, start editing with Shift-A, press enter and type "blacklist nouveau" (not the quotes!). Then exit editing by pressing ESC and save by typing ":wq" (again, not the quotes). 3. Install the new driver Provided you've downloaded a driver from the NVidia site, you just need to execute it with a command like "sudo sh <file>". The installation is wizard-like and you can safely use the default values / options. Personally, I choose to NOT create / update an Xorg configuration file and to DO install 32-bit libraries. In case you're thinking "how do I un-install the previous driver?" you'll be glad to know the new driver installation takes care of that, so you can say "that was easy"! Note 1: If the installer complains that it cannot compile the kernel module, you are probably missing some kernel-related and / or basic compiling packages. First make sure you have the basic compiling package: "sudo apt-get install build-essential". Then retry the driver installation. If it fails again, you probably also need to install the headers package for your kernel: "sudo apt-get install linux-headers-`uname -r`". Note that this command will only install the headers for your currently running kernel. If you update your system and receive a newer kernel, the headers will not be updated. You should probably instead install the linux-headers-generic or the linux-headers-server package, depending on which linux-image-* package you have installed (e.g. linux-image-generic or linux-image-server). The quick solution is to install the headers package matching your running kernel, just make sure you don't have automatic updates activated and keep a note to download the new headers package if / when you do update your kernel. Note 2: If / when you update your kernel, you will need to re-install the NVidia driver, because its kernel module has to be compiled again for the new kernel, so keep a note for this too. 4. Reboot Provided the new driver installation reports successful completion, you should then reboot, for example with the command "sudo reboot". Your cruncher should greet you with a new NVidia driver! Hope this helps! Also, any corrections / additions are welcome! ____________ | |
ID: 36803 | Rating: 0 | rate: / Reply Quote | |
Recently tried Nvidia 331.79 drivers with hopes on my Optimus system. However, Boinc said there is Nvidia libraries but no GPU's. I switched to 331.38 driver again. | |
ID: 37023 | Rating: 0 | rate: / Reply Quote | |
Recently tried Nvidia 331.79 drivers with hopes on my Optimus system. However, Boinc said there is Nvidia libraries but no GPU's. I switched to 331.38 driver again. Hello: This is a known issue new Nvidia drivers have a problem (Linux) Ubuntu and do not recognize the GPUs in BOINC. To work well 331.79 and 337.25 as the latest must settle manually as already mentioned in these pages. Greetings. | |
ID: 37034 | Rating: 0 | rate: / Reply Quote | |
I know the issue with drivers but I hadn't tested the 331.79 driver and had some hopes. All are broken now. :D | |
ID: 37035 | Rating: 0 | rate: / Reply Quote | |
I too have issues with the client. A stock BOINC Berkeley install slings files all over the file system on install and finding the correct location is a pain | |
ID: 37221 | Rating: 0 | rate: / Reply Quote | |
I am trying to install Linux on an 8 GB USB Stick and run GPU-Grid from there. | |
ID: 37691 | Rating: 0 | rate: / Reply Quote | |
After I have installed everything, I have controled with NVIDIA x Server Settings the NVIDIA Version: It is 340.32 and it sees 8 Cuda Cores from my GTS 8400 video card (It is a spare video card to try to set it up). And after I start the Boinc Manager, it reports Boinc Client 7.2.42, OS Linux 3.13.0-24-generic and NO USABLE GPUS FOUND. It may well be a problem with the boot sequence; I.e. the video card driver loads after the BOINC-client daemon starts. If I understand what you did, you installed the latest NVidia driver and restarted your computer. The BOINC-manager now shows "no usable GPUs". If my analysis is correct, you can resolve this problem by restarting the BOINC daemon. I run Ubuntu, but the procedure for restarting the daemon in Mint 17 should be similar. In Ubuntu, open a terminal and type: sudo /etc/init.d/boinc-client restart After authenticating with your password, the daemon will stop and restart and you should notice that the Boinc manager has found your GPU. If this works for you, be advised that you will need to do this each time you start up or restart your computer. There is, of course, permanent solutions to this problem, but these require changes to the boot sequence or delaying the start of the daemon. As you are new to Linux, I won't advise you try for a permanent solution for if you make an error, you could end up with an unbootable system. Anyway, its good practice and a lot of fun typing commands into the terminal and being amazed at what Linux can do. I hope this helps. ____________ | |
ID: 37695 | Rating: 0 | rate: / Reply Quote | |
A GTS 8400 is not capable of running GPUGrid tasks as it's a Compute Capable 1.1 card. | |
ID: 37696 | Rating: 0 | rate: / Reply Quote | |
I run Ubuntu, but the procedure for restarting the daemon in Mint 17 should be similar. In Ubuntu, open a terminal and type: The command did work in Mint as well! But without any success! In the terminal it reads: “*Stopping BOINC core client: boinc …waiting.. *Starting BOINC core client: boinc […]” But Boinc can still not find the GPU. Any ideas? A GTS 8400 is not capable of running GPUGrid tasks as it's a Compute Capable 1.1 card. I am well aware that the GPU is not useable for GPUGRID, but as it does not work at all, I would like to try it first with an old card I have, and change it to a capable card later. | |
ID: 37701 | Rating: 0 | rate: / Reply Quote | |
I am well aware that the GPU is not useable for GPUGRID, but as it does not work at all, I would like to try it first with an old card I have, and change it to a capable card later. skgiven may have supplied the vital clue to solving your problem. Maybe the BOINC manager is more sophisticated than we think - its' identification of usable GPUs may be project specific (who wooda taugh!). There is, of course, an easy way to find out - why not attach to a project that will accept any NVidia cc 1.1 card and see what happens. seti@home is a popular one. ____________ | |
ID: 37704 | Rating: 0 | rate: / Reply Quote | |
klepel, | |
ID: 37706 | Rating: 0 | rate: / Reply Quote | |
captainjack, | |
ID: 37708 | Rating: 0 | rate: / Reply Quote | |
klepel, | |
ID: 37709 | Rating: 0 | rate: / Reply Quote | |
A GTS 8400 is not capable of running GPUGrid tasks as it's a Compute Capable 1.1 card. Tasks will not be sent to you unless you have a CC1.3 card or better. This is determined by the project via compute capability. ____________ FAQ's HOW TO: - Opt out of Beta Tests - Ask for Help | |
ID: 37753 | Rating: 0 | rate: / Reply Quote | |
Dear all, | |
ID: 38447 | Rating: 0 | rate: / Reply Quote | |
Nikke, | |
ID: 38448 | Rating: 0 | rate: / Reply Quote | |
Hi Matt, | |
ID: 38450 | Rating: 0 | rate: / Reply Quote | |
Hi Matt, Hi Nikke all your WUs was failed reporting <core_client_version>6.10.58</core_client_version> <![CDATA[ <message> process exited with code 199 (0xc7, -57) </message> <stderr_txt> SWAN : FATAL : Cuda driver error 3 in file 'swanlibnv2.cpp' in line 446. # SWAN swan_assert -57 </stderr_txt> > | |
ID: 38453 | Rating: 0 | rate: / Reply Quote | |
Hi Matt, Yes, you've had 156 failed Work units all with v8.21 (cuda60) app Your last successfully completed WU was on Oct 6th and that was using the v8.03 (cuda42) app. Since Matt changed the server scheduling policy the GPUGrid server needs to know which Nvidia driver version you have installed to send you the proper WUs/app version. If you upgrade your boinc client to version 7.4.22, boinc will determine your nvidia driver version and report it to the server. You should then receive exclusively cuda 4.2 WUs. See this thread for new scheduling system: http://www.gpugrid.net/forum_thread.php?id=3874 If you'd like to receive cuda 6.0 or 6.5 Work then you'll need to upgrade your nvidia driver to 340.46 for cuda 6 or 343.23 for cuda 6.5 and also upgrade your boinc client to 7.4.22 EDIT: I made multiple changes to try be more clear. sorry. | |
ID: 38454 | Rating: 0 | rate: / Reply Quote | |
Thank you all guys, | |
ID: 38455 | Rating: 0 | rate: / Reply Quote | |
Thank you all guys, I Nikke, I solved a similar problem (on kUbuntu 14.04) installing manually the latest Nvidia driver. Do do so I followed step by step the tutorial that some posted on this thread: http://www.gpugrid.net/forum_thread.php?id=3713&nowrap=true#36671 to install the latest boinc server and client I use a custom PPA, that on my system works without any problem http://setiathome.berkeley.edu/forum_thread.php?id=70320 Hope it could help and works also on your OS G | |
ID: 38456 | Rating: 0 | rate: / Reply Quote | |
Thank you all guys, you can get new boinc client here if you can't get it via package-manager and repositories are too old and try to run it manually unpacking tarball and run client/manager http://boinc.berkeley.edu/wiki/Installing_BOINC#Linux but ... you have a very hold OS and most packages need to be upgrade (glibc first but this is a very important library for the system . Pay attention if you upgrade this.) you can check dinamic link library as following : run inside boinc folder $ ldd {boinccmd,boincmgr,boinc_client} | |
ID: 38457 | Rating: 0 | rate: / Reply Quote | |
Unfortunately upgrading the OS is out of scope.... | |
ID: 38458 | Rating: 0 | rate: / Reply Quote | |
Nikke, | |
ID: 38471 | Rating: 0 | rate: / Reply Quote | |
You're right Matt. | |
ID: 38486 | Rating: 0 | rate: / Reply Quote | |
Message boards : News : Important news for Linux crunchers