Advanced search

Message boards : News : Important news for Linux crunchers

Author Message
Profile MJH
Project administrator
Project developer
Project scientist
Send message
Joined: 12 Nov 07
Posts: 696
Credit: 27,266,655
RAC: 0
Level
Val
Scientific publications
watwat
Message 36577 - Posted: 23 Apr 2014 | 8:11:22 UTC
Last modified: 24 Apr 2014 | 8:33:41 UTC

Hi all,

We are having a problem with correctly scheduling work to Linux clients because the BOINC client for that platform does not report the Nvidia driver version to us.

If you find that you are receiving the cuda60 application version and it is not working for you, the fixes are:

*) Upgrade to driver 334.21 or later

*) Try the patched (v7.3.15) client I have made available at:

http://secure.acellera.com/insecure/boinc/boinc (RedHat etc)
http://secure.acellera.com/insecure/boinc/boinc_ubuntu (Ubuntu)

(the patch itself is at http://secure.acellera.com/insecure/boinc/gpu_nvidia.cpp_patch )

This client reports the driver version and allows a correct scheduling decision to be made.

Matt

HA-SOFT, s.r.o.
Send message
Joined: 3 Oct 11
Posts: 100
Credit: 4,855,582,826
RAC: 0
Level
Arg
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 36590 - Posted: 23 Apr 2014 | 15:40:49 UTC - in response to Message 36577.

Did you send this path to boinc developers also? This is a very annoying thing in linux version.

Thanks
Zdenek

Richard Haselgrove
Send message
Joined: 11 Jul 09
Posts: 791
Credit: 1,427,941,620
RAC: 1,315,908
Level
Met
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 36591 - Posted: 23 Apr 2014 | 15:57:55 UTC - in response to Message 36590.

If Matt doesn't, I'd be happy to.

I imagine he's waiting for some positive feedback to confirm that the patched version works as intended, without any unexpected side effects.

Profile MJH
Project administrator
Project developer
Project scientist
Send message
Joined: 12 Nov 07
Posts: 696
Credit: 27,266,655
RAC: 0
Level
Val
Scientific publications
watwat
Message 36593 - Posted: 23 Apr 2014 | 18:09:33 UTC - in response to Message 36591.

Already sent upstream. Should be in the next release.

Matt

Profile Stoneageman
Avatar
Send message
Joined: 25 May 09
Posts: 211
Credit: 12,279,345,996
RAC: 8,209,337
Level
Trp
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 36594 - Posted: 23 Apr 2014 | 19:29:39 UTC

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?

Profile MJH
Project administrator
Project developer
Project scientist
Send message
Joined: 12 Nov 07
Posts: 696
Credit: 27,266,655
RAC: 0
Level
Val
Scientific publications
watwat
Message 36597 - Posted: 23 Apr 2014 | 20:13:47 UTC - in response to Message 36594.

Download it, do a "chmod +x boinc" to make it executable, then run it.

If you normally use the boinc mangler or boinccmd, put it in the same directory as those, replacing the "boinc" executable that is already there (take a backup first).

If your OS isn't a redhat clone, you might need to make symlinks for libssl.so.10 and libcrypto.so.10, to whatever libssl/crypto you have in /usr/lib

Matt

biodoc
Send message
Joined: 26 Aug 08
Posts: 89
Credit: 656,130,328
RAC: 0
Level
Lys
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 36600 - Posted: 23 Apr 2014 | 23:06:46 UTC

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.

ldd boinc (Matt's version)
libssl.so.10 => not found
libcrypto.so.10 => not found


ldd boinc (7.2.42 version)

libssl.so.1.0.0 => /lib/x86_64-linux-gnu/libssl.so.1.0.0 (0x00007f892f87f000)
libcrypto.so.1.0.0 => /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 (0x00007f892f4a2000)


symlinks:

sudo ln -s /lib/x86_64-linux-gnu/libssl.so.1.0.0 /lib/x86_64-linux-gnu/libssl.so.10
sudo ln -s /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 /lib/x86_64-linux-gnu/libcrypto.so.10


ldd boinc (Matt's version)
libssl.so.10 => /lib/x86_64-linux-gnu/libssl.so.10 (0x00007f1823727000)
libcrypto.so.10 => /lib/x86_64-linux-gnu/libcrypto.so.10 (0x00007f182334a000)

Everything looks ok, but when I run Matt's boinc app, I get an error "libssl.so.10, libcrypto.so.10 not found"

Did I miss anything?



Profile MJH
Project administrator
Project developer
Project scientist
Send message
Joined: 12 Nov 07
Posts: 696
Credit: 27,266,655
RAC: 0
Level
Val
Scientific publications
watwat
Message 36605 - Posted: 24 Apr 2014 | 8:34:05 UTC - in response to Message 36600.

Try this build:

http://secure.acellera.com/insecure/boinc/boinc_ubuntu

biodoc
Send message
Joined: 26 Aug 08
Posts: 89
Credit: 656,130,328
RAC: 0
Level
Lys
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 36606 - Posted: 24 Apr 2014 | 8:51:23 UTC - in response to Message 36605.

Try this build:

http://secure.acellera.com/insecure/boinc/boinc_ubuntu



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!

Profile [VENETO] sabayonino
Send message
Joined: 4 Apr 10
Posts: 47
Credit: 546,306,012
RAC: 308,351
Level
Lys
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 36607 - Posted: 24 Apr 2014 | 11:13:10 UTC

Hi

Without any patch(es) , no problems found

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)


Profile [VENETO] sabayonino
Send message
Joined: 4 Apr 10
Posts: 47
Credit: 546,306,012
RAC: 308,351
Level
Lys
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 36675 - Posted: 26 Apr 2014 | 16:42:30 UTC
Last modified: 26 Apr 2014 | 17:09:42 UTC

Hi huys :D

I have many WUs fault with 780Ti and cuda6



in gpugrid work directory have a problems with libcudart and libcufft

libraries exist :

$ 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

Profile microchip
Send message
Joined: 4 Sep 11
Posts: 107
Credit: 187,573,639
RAC: 160,664
Level
Ile
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwat
Message 36740 - Posted: 30 Apr 2014 | 15:01:47 UTC
Last modified: 30 Apr 2014 | 15:03:14 UTC

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

GPUGRID is the buggiest project I've crunched for thus far
____________

Team Belgium
The Cyberpunk Movies Database

sis651
Send message
Joined: 25 Nov 13
Posts: 65
Credit: 63,981,254
RAC: 142,153
Level
Thr
Scientific publications
watwatwat
Message 36761 - Posted: 1 May 2014 | 3:12:32 UTC - in response to Message 36740.
Last modified: 1 May 2014 | 3:12:54 UTC

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.

biodoc
Send message
Joined: 26 Aug 08
Posts: 89
Credit: 656,130,328
RAC: 0
Level
Lys
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 36762 - Posted: 1 May 2014 | 8:08:09 UTC - in response to Message 36675.

Hi huys :D


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


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.

GPUGRID Role account
Send message
Joined: 15 Feb 07
Posts: 134
Credit: 1,349,535,983
RAC: 0
Level
Met
Scientific publications
watwatwatwatwatwatwatwatwat
Message 36764 - Posted: 1 May 2014 | 12:01:27 UTC - in response to Message 36762.

You don't need to install CUDA yourself. We ship all the necessary runtime libraries along with the application.

Matt

GPUGRID Role account
Send message
Joined: 15 Feb 07
Posts: 134
Credit: 1,349,535,983
RAC: 0
Level
Met
Scientific publications
watwatwatwatwatwatwatwatwat
Message 36765 - Posted: 1 May 2014 | 12:05:09 UTC - in response to Message 36740.

microchip,

Looking at the results from your GTX560 machine (#167410), I would say that your GPU is bad.

Matt

Profile microchip
Send message
Joined: 4 Sep 11
Posts: 107
Credit: 187,573,639
RAC: 160,664
Level
Ile
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwat
Message 36767 - Posted: 1 May 2014 | 19:57:15 UTC - in response to Message 36765.

microchip,

Looking at the results from your GTX560 machine (#167410), I would say that your GPU is bad.

Matt


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
The Cyberpunk Movies Database

Profile skgiven
Volunteer moderator
Project tester
Volunteer tester
Avatar
Send message
Joined: 23 Apr 09
Posts: 3968
Credit: 1,837,071,099
RAC: 365,113
Level
His
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 36774 - Posted: 2 May 2014 | 11:44:41 UTC - in response to Message 36767.

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.

Since I swapped it into a Win7 system 3days ago it hasn't failed a single WU...
The GTX670 that went from the W7 to the Ubuntu 14.04 system hasn't failed either!

I've had a similar experience with a GTX660 and a GTX260 in the past. Such problems could be down to some oddity between the driver, OS and card, or be an OS, motherboard chipset issue or even a card firmware revision/driver problem.
____________
FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

Profile [VENETO] sabayonino
Send message
Joined: 4 Apr 10
Posts: 47
Credit: 546,306,012
RAC: 308,351
Level
Lys
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 36778 - Posted: 2 May 2014 | 18:40:01 UTC - in response to Message 36762.
Last modified: 2 May 2014 | 18:43:30 UTC


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.


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

Profile Carlesa25
Avatar
Send message
Joined: 13 Nov 10
Posts: 324
Credit: 72,394,453
RAC: 0
Level
Thr
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 36783 - Posted: 3 May 2014 | 11:53:25 UTC
Last modified: 3 May 2014 | 12:00:47 UTC

Hi, I think that says something does not work.

Right now I have installed the Nvidia driver 331.67 and BOINC 7.3.15 (the GPUGRID recommended) reporting the cuda version installed, but I get only tasks for CUDA 4.2 but step BOINC 7.2.42 (recommended version) I have tasks CUDA 6 . Greetings.

GPUGRID Role account
Send message
Joined: 15 Feb 07
Posts: 134
Credit: 1,349,535,983
RAC: 0
Level
Met
Scientific publications
watwatwatwatwatwatwatwatwat
Message 36784 - Posted: 3 May 2014 | 13:31:38 UTC - in response to Message 36783.

Carlesa,

With our BOINC client you need to be using driver 334.21 or later to get CUDA6 tasks.
The unmodified BOINC client reports no driver version, which causes our server to erroneously send out CUDA 6 wus.

The drivers numerically between 331 and 334.21 don all support CUDA 6 well, so we have to exclude them.

Matt

Profile Carlesa25
Avatar
Send message
Joined: 13 Nov 10
Posts: 324
Credit: 72,394,453
RAC: 0
Level
Thr
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 36785 - Posted: 3 May 2014 | 13:51:39 UTC - in response to Message 36784.
Last modified: 3 May 2014 | 14:15:04 UTC

Carlesa,

With our BOINC client you need to be using driver 334.21 or later to get CUDA6 tasks.
The unmodified BOINC client reports no driver version, which causes our server to erroneously send out CUDA 6 wus.

The drivers numerically between 331 and 334.21 don all support CUDA 6 well, so we have to exclude them.

Matt



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.

Profile Carlesa25
Avatar
Send message
Joined: 13 Nov 10
Posts: 324
Credit: 72,394,453
RAC: 0
Level
Thr
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 36790 - Posted: 3 May 2014 | 16:26:45 UTC - in response to Message 36785.


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.



Hello; Task perfectly completed:

Ubuntu 14.04-64bits - Nvidia 331.67 - Boinc 7.2.42.

http://www.gpugrid.net/result.php?resultid=9780070

GPUGRID Role account
Send message
Joined: 15 Feb 07
Posts: 134
Credit: 1,349,535,983
RAC: 0
Level
Met
Scientific publications
watwatwatwatwatwatwatwatwat
Message 36791 - Posted: 3 May 2014 | 17:20:34 UTC - in response to Message 36785.
Last modified: 3 May 2014 | 17:21:24 UTC

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

Profile Carlesa25
Avatar
Send message
Joined: 13 Nov 10
Posts: 324
Credit: 72,394,453
RAC: 0
Level
Thr
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 36792 - Posted: 3 May 2014 | 21:23:17 UTC - in response to Message 36791.
Last modified: 3 May 2014 | 21:25:28 UTC

Blame Nvidia for this mess - the drivers report a "supported CUDA version", but there are many releases that lie about CUDA 6 capability.

Matt


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.

SJC_Steve
Send message
Joined: 31 Oct 12
Posts: 17
Credit: 167,541,702
RAC: 0
Level
Ile
Scientific publications
watwatwatwatwatwatwatwat
Message 36794 - Posted: 5 May 2014 | 17:52:42 UTC

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.
Thanks,
Steve

Profile Carlesa25
Avatar
Send message
Joined: 13 Nov 10
Posts: 324
Credit: 72,394,453
RAC: 0
Level
Thr
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 36795 - Posted: 5 May 2014 | 18:21:26 UTC - in response to Message 36794.

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.
Thanks,
Steve



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.

GPUGRID Role account
Send message
Joined: 15 Feb 07
Posts: 134
Credit: 1,349,535,983
RAC: 0
Level
Met
Scientific publications
watwatwatwatwatwatwatwatwat
Message 36796 - Posted: 5 May 2014 | 19:09:36 UTC - in response to Message 36794.

Steve: your options are:
1) Update to a more recent nvidia driver
2) Use our patched boinc client that correctly reports the driver version to the GPUGRID server (see elsewhere on the forums)

Matt

SJC_Steve
Send message
Joined: 31 Oct 12
Posts: 17
Credit: 167,541,702
RAC: 0
Level
Ile
Scientific publications
watwatwatwatwatwatwatwat
Message 36797 - Posted: 5 May 2014 | 20:49:17 UTC - in response to Message 36796.
Last modified: 5 May 2014 | 20:49:44 UTC

Matt,
Thanks for the reply. I've updated all files and drivers using this command;
'sudo apt-get dist-upgrade'. However, it still runs Nvidia driver 304.116 and fails Cuda 60 WUs.
Steve

GPUGRID Role account
Send message
Joined: 15 Feb 07
Posts: 134
Credit: 1,349,535,983
RAC: 0
Level
Met
Scientific publications
watwatwatwatwatwatwatwatwat
Message 36798 - Posted: 5 May 2014 | 21:55:32 UTC - in response to Message 36797.

Steve,

Try replacing your "boinc" executable with our version, available from:

http://secure.acellera.com/insecure/boinc/boinc_ubuntu

Matt

SJC_Steve
Send message
Joined: 31 Oct 12
Posts: 17
Credit: 167,541,702
RAC: 0
Level
Ile
Scientific publications
watwatwatwatwatwatwatwat
Message 36801 - Posted: 6 May 2014 | 14:53:06 UTC - in response to Message 36798.

Matt,
How do I do that? I'm not a programmer so you'll have to be more detailed in your explanation. I use SSH to control the cruncher as I'm not physically at the unit.
Thanks,
Steve

Vagelis Giannadakis
Send message
Joined: 5 May 13
Posts: 187
Credit: 349,254,454
RAC: 0
Level
Asp
Scientific publications
watwatwatwatwatwatwat
Message 36803 - Posted: 7 May 2014 | 11:05:48 UTC - in response to Message 36801.
Last modified: 7 May 2014 | 11:08:28 UTC

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.

Note 1: All commands should be typed without the double quotes
Note 2: Please make sure you understand what you need to do and do some research prior to performing the steps below. It's unlikely something bad will happen, but proceed cautiously!

First the easy part, using a "vanilla" (or custom) BOINC client build. There's nothing really to it, you just download the archive, run it with the command "sh <boinc archive name here>" at which point it creates a BOINC directory and extracts its contents in it. To run it you then "cd" to the directory and start the client "./boinc --daemon --dir <full path to BOINC directory here>". Contrary to the repository-installed BOINC client, you will need to run the client yourself, unless you want to start it at system boot, but I won't go into that. Also, the client will run with your own OS user, which you may not like. You can create a new OS user (it's pretty easy and Google will help you) and execute it with that.

Now the harder part, updating NVidia drivers. Summarizing, you will need to do the following:


    1. Remove the existing driver *
    2. Add the nouveau driver in the kernel module black list *
    3. Install the new driver
    4. Reboot


The starred steps need only be done when moving from a repository-installed driver to one you've downloaded yourself, and just once. I.e. next time you update your NVidia driver, you won't have to do them.

Let's go! :)

1. Remove the existing driver
You basically need to remove the driver's packages. First thing to do is to identify which packages to remove with the command "dpkg-query -W 'nvidia*'". On my cruncher this command shows the following:

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!
____________

sis651
Send message
Joined: 25 Nov 13
Posts: 65
Credit: 63,981,254
RAC: 142,153
Level
Thr
Scientific publications
watwatwat
Message 37023 - Posted: 7 Jun 2014 | 19:47:34 UTC

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.

Profile Carlesa25
Avatar
Send message
Joined: 13 Nov 10
Posts: 324
Credit: 72,394,453
RAC: 0
Level
Thr
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 37034 - Posted: 9 Jun 2014 | 11:59:42 UTC - in response to Message 37023.

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.

sis651
Send message
Joined: 25 Nov 13
Posts: 65
Credit: 63,981,254
RAC: 142,153
Level
Thr
Scientific publications
watwatwat
Message 37035 - Posted: 9 Jun 2014 | 18:24:56 UTC - in response to Message 37034.

I know the issue with drivers but I hadn't tested the 331.79 driver and had some hopes. All are broken now. :D
Also, while reinstalling drivers I broke the OpenCL support. Can't run OpenCL works now.

Robert Gammon
Send message
Joined: 28 May 12
Posts: 61
Credit: 625,170,496
RAC: 234,087
Level
Lys
Scientific publications
watwatwatwatwatwatwatwatwatwat
Message 37221 - Posted: 4 Jul 2014 | 15:11:20 UTC - in response to Message 36798.

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

A slightly better solution appears to be to download the BOINC package from Berkeley AFTER getting the stock manager installed from Ubuntu. Copy the downloaded file to the root level and run from there. Everything gets stuck in the BOINC directory tree so finding this file and replacing it is easier

klepel
Send message
Joined: 23 Dec 09
Posts: 138
Credit: 1,837,008,477
RAC: 1,405,486
Level
His
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 37691 - Posted: 20 Aug 2014 | 2:41:30 UTC

I am trying to install Linux on an 8 GB USB Stick and run GPU-Grid from there.

Therefore I have installed Linux Mint 17 “Qiuna” 64-bit. After lot of tries I managed to load down the latest NVIDIA driver fron “xorg-edgers” and after that I installed BOINC Client 7.2.42 from build in (Linux Mint) Software Manager BOINC 7.2.42+dfsg-1.

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.

As I am “newbie” on Linux I am stuck now. So I would highly appreciate if somebody with Linux Mint 17 and BOINC experience might help.

Robert Meckley
Send message
Joined: 3 Nov 13
Posts: 2
Credit: 554,130,122
RAC: 550,405
Level
Lys
Scientific publications
watwatwatwatwatwatwatwat
Message 37695 - Posted: 20 Aug 2014 | 13:35:06 UTC - in response to Message 37691.

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.
____________

Profile skgiven
Volunteer moderator
Project tester
Volunteer tester
Avatar
Send message
Joined: 23 Apr 09
Posts: 3968
Credit: 1,837,071,099
RAC: 365,113
Level
His
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 37696 - Posted: 20 Aug 2014 | 15:08:10 UTC - in response to Message 37695.

A GTS 8400 is not capable of running GPUGrid tasks as it's a Compute Capable 1.1 card.
CC1.3 or better is required to crunch here.
____________
FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

klepel
Send message
Joined: 23 Dec 09
Posts: 138
Credit: 1,837,008,477
RAC: 1,405,486
Level
His
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 37701 - Posted: 21 Aug 2014 | 2:09:55 UTC - in response to Message 37695.

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.

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.
CC1.3 or better is required to crunch here.

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.

Robert Meckley
Send message
Joined: 3 Nov 13
Posts: 2
Credit: 554,130,122
RAC: 550,405
Level
Lys
Scientific publications
watwatwatwatwatwatwatwat
Message 37704 - Posted: 21 Aug 2014 | 12:42:36 UTC - in response to Message 37701.

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.
____________

captainjack
Send message
Joined: 9 May 13
Posts: 114
Credit: 823,969,775
RAC: 980,854
Level
Glu
Scientific publications
watwatwatwatwatwatwatwatwat
Message 37706 - Posted: 21 Aug 2014 | 17:39:48 UTC

klepel,

You might try an NVIDIA driver from a different source. If I remember correctly, several months ago I tried the driver from xorg-edgers and it did not work for me for GPU computing. I had to do a manual install of the driver that I downloaded directly from NVIDIA. It is working fine for me on Ubuntu.

klepel
Send message
Joined: 23 Dec 09
Posts: 138
Credit: 1,837,008,477
RAC: 1,405,486
Level
His
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 37708 - Posted: 22 Aug 2014 | 0:23:02 UTC - in response to Message 37706.

captainjack,

I tried this before as well, but with the instruction for Ubuntu from Carlesa25 in Spanish I found in the forum, I managed to change the command lines that it does something in Mint, but I was not able to kill the nouveau driver, as I do not really know what I am doing:
“kl#!/bin/sh
service mdm stop
nvidia-uninstall
apt-get purge remove nvidia*
apt-get purge xserver-xorg-video-nouveau nvidia*
update-initramfs -u -k all bash /opt/NVIDIA.run
service mdm start”

So I am really looking for somebody who has experience with Linux Mint, best with newest version, which might be able to guide me. I really would like change one Computer with a GTX 570 from Windows XP to LINUX.

captainjack
Send message
Joined: 9 May 13
Posts: 114
Credit: 823,969,775
RAC: 980,854
Level
Glu
Scientific publications
watwatwatwatwatwatwatwatwat
Message 37709 - Posted: 22 Aug 2014 | 0:52:20 UTC

klepel,

Here are some instructions that show how to install the NVIDIA drivers in Ubuntu. It includes a section on how to stop the nouveau drivers.

http://www.gpugrid.net/forum_thread.php?id=3713&nowrap=true#36671

If you scroll down a few posts, there are some additional comments from skgiven that help clarify.

Hope that helps.

Profile skgiven
Volunteer moderator
Project tester
Volunteer tester
Avatar
Send message
Joined: 23 Apr 09
Posts: 3968
Credit: 1,837,071,099
RAC: 365,113
Level
His
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 37753 - Posted: 29 Aug 2014 | 20:03:13 UTC - in response to Message 37696.

A GTS 8400 is not capable of running GPUGrid tasks as it's a Compute Capable 1.1 card.
CC1.3 or better is required to crunch here.


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

Nikke
Send message
Joined: 25 Aug 10
Posts: 9
Credit: 2,143,920,937
RAC: 0
Level
Phe
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 38447 - Posted: 13 Oct 2014 | 7:09:52 UTC

Dear all,

I'm not receiving tasks since last week.
The message I get is:

"This computer has finished the daily quota of 1 tasks"

That' obviously not true.
My environment is pretty old in terms of software but, unfortunately, there is no easy and fast way to upgrade it.

Any other suggestion?

Thanks in advance

Profile MJH
Project administrator
Project developer
Project scientist
Send message
Joined: 12 Nov 07
Posts: 696
Credit: 27,266,655
RAC: 0
Level
Val
Scientific publications
watwat
Message 38448 - Posted: 13 Oct 2014 | 7:27:51 UTC - in response to Message 38447.

Nikke,

What nvidia driver version do you have?

Matt

Nikke
Send message
Joined: 25 Aug 10
Posts: 9
Credit: 2,143,920,937
RAC: 0
Level
Phe
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 38450 - Posted: 13 Oct 2014 | 9:01:21 UTC - in response to Message 38448.
Last modified: 13 Oct 2014 | 9:12:04 UTC

Hi Matt,

the system is based on:
- Centos 6.5, running kernel version 2.6.32-431.5.1.el6.x86_64
- Nvidia driver version 331.38
- Cuda version 5.5.22
- BOINC version 6.10.58

Profile [VENETO] sabayonino
Send message
Joined: 4 Apr 10
Posts: 47
Credit: 546,306,012
RAC: 308,351
Level
Lys
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 38453 - Posted: 13 Oct 2014 | 10:30:04 UTC - in response to Message 38450.

Hi Matt,

the system is based on:
- Centos 6.5, running kernel version 2.6.32-431.5.1.el6.x86_64
- Nvidia driver version 331.38
- Cuda version 5.5.22
- BOINC version 6.10.58



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>
>


biodoc
Send message
Joined: 26 Aug 08
Posts: 89
Credit: 656,130,328
RAC: 0
Level
Lys
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 38454 - Posted: 13 Oct 2014 | 11:08:08 UTC - in response to Message 38453.
Last modified: 13 Oct 2014 | 11:13:56 UTC

Hi Matt,

the system is based on:
- Centos 6.5, running kernel version 2.6.32-431.5.1.el6.x86_64
- Nvidia driver version 331.38
- Cuda version 5.5.22
- BOINC version 6.10.58



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>
>




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.

Nikke
Send message
Joined: 25 Aug 10
Posts: 9
Credit: 2,143,920,937
RAC: 0
Level
Phe
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 38455 - Posted: 13 Oct 2014 | 11:45:34 UTC - in response to Message 38454.
Last modified: 13 Oct 2014 | 11:59:49 UTC

Thank you all guys,

I was thinking something like that.
The only problem I see is upgrading the BOINC client, since the version 7 seems difficult to run under CentOS (at least it was last year...)
Once upgraded it, I can also try to upgrade drivers and CUDA easily.

Do you have any link suggestion for the BOINC client (possibly a fast and easy one ;-) ) ?

GGPA [E.R.]
Send message
Joined: 6 Jan 10
Posts: 3
Credit: 473,230,027
RAC: 0
Level
Gln
Scientific publications
watwatwatwatwatwat
Message 38456 - Posted: 13 Oct 2014 | 12:20:19 UTC - in response to Message 38455.

Thank you all guys,

I was thinking something like that.
The only problem I see is upgrading the BOINC client, since the version 7 seems difficult to run under CentOS (at least it was last year...)
Once upgraded it, I can also try to upgrade drivers and CUDA easily.

Do you have any link suggestion for the BOINC client (possibly a fast and easy one ;-) ) ?


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

Profile [VENETO] sabayonino
Send message
Joined: 4 Apr 10
Posts: 47
Credit: 546,306,012
RAC: 308,351
Level
Lys
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 38457 - Posted: 13 Oct 2014 | 12:25:34 UTC - in response to Message 38455.
Last modified: 13 Oct 2014 | 12:30:05 UTC

Thank you all guys,

I was thinking something like that.
The only problem I see is upgrading the BOINC client, since the version 7 seems difficult to run under CentOS (at least it was last year...)
Once upgraded it, I can also try to upgrade drivers and CUDA easily.

Do you have any link suggestion for the BOINC client (possibly a fast and easy one ;-) ) ?



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}

Nikke
Send message
Joined: 25 Aug 10
Posts: 9
Credit: 2,143,920,937
RAC: 0
Level
Phe
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 38458 - Posted: 13 Oct 2014 | 13:12:48 UTC - in response to Message 38457.

Unfortunately upgrading the OS is out of scope....

I've seen that the boinc client version 7.2.33 is available from the EPEL repository but I suppose it's not enough.

Last year I tried to manually compile the BOINC client from source.....as already noticed it was a nightmare of libraries dependencies.

Profile MJH
Project administrator
Project developer
Project scientist
Send message
Joined: 12 Nov 07
Posts: 696
Credit: 27,266,655
RAC: 0
Level
Val
Scientific publications
watwat
Message 38471 - Posted: 13 Oct 2014 | 20:25:18 UTC - in response to Message 38458.
Last modified: 13 Oct 2014 | 21:04:40 UTC

Nikke,

The problem is that your machine has one of the few bad driver versions that incorrectly report haing CUDA 6 capability.

Get our version of the client from

http://www.gpugrid.net/forum_thread.php?id=3736&nowrap=true#36577

This reports the exact driver version to the server and lets it give you an appropriate app version.

Matt

Nikke
Send message
Joined: 25 Aug 10
Posts: 9
Credit: 2,143,920,937
RAC: 0
Level
Phe
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 38486 - Posted: 14 Oct 2014 | 9:12:35 UTC - in response to Message 38471.

You're right Matt.
I've upgraded CUDA to 6.5, drivers to 343.22 and, using your compiled boinc client I'm now able to compute again.

I hope to be back soon with some GPU power ;-)

Many thanks

Post to thread

Message boards : News : Important news for Linux crunchers