All my CUDA applications error out for this driver on a fresh installed Ubuntu 12.04.1 LTS 64 bit version with NVIDIA NVS310 card.
It seems to be a linking problem to dynamically library according to the error message I find:
sched_request_einstein.phys.uwm.edu.xml:../../projects/einstein.phys.uwm.edu/einsteinbinary_BRP4_1.28_i686-pc-linux-gnu__BRP4cuda32nv270: error while loading shared libraries: libcuda.so.1: wrong ELF class: ELFCLASS64
It appears that the program try to load the 64 bit version located in /usr/var/lib, while the correct 32 bit library is located in /usr/var/lib32.
Is this hardcoded in the program or does it exist a workaround to overcome this problem?
With very best regards
Bent Vangli, Oslo, Norway
Copyright © 2024 Einstein@Home. All rights reserved.
Linux 64 bit - NVIDIA GPU driver version 304.60 - Errror in cuda
)
Hi,
make sure you install 32bit drivers *and* 32bit compatibility libs.
The manual driver install script explicitely asks, if you want to install 32bit too.
KR
Michael
Team Linux Users Everywhere
Install the 32bit
)
Install the 32bit compatibility libraries like so: http://boinc.berkeley.edu/wiki/Installing_BOINC#Ubuntu
RE: I did find a workaround
)
I have upgraded to NVIDIA
)
I have upgraded to NVIDIA driver version 310.14 beta, and it also seems to work. However, the Einstein CUDA applications aren't able to run despite more than 450 MByte free memory on the card. It complains of too little memory
I have now tested with Milkyway CUDA, and they seems to run fine. But before I can be conclusive I have to see that the results validate.
Best regards Bent
A correction to my previous
)
A correction to my previous mail.
It was Milkyway OpenCL_NVIDIA that runs. The results done bu NVIDIA driver version 304.60 didn't validate, however the version 310.14 beta gives valid results.
The beta driver also run Primegrid CUDA applications, but it is too early to see if they validate.
Best regards Bent
Then it is checked. Both
)
Then it is checked. Both Milkyway OpenCL-NVIDIA and Primegrid Cuda applications work for NVS 310 mikro GPU, and the results validate. :-)
Einstein Cuda applications try to start, but after 2 seconds go into hibernation telling it is waiting for more CPU/GPU memory. I do have 16 GByte CPU memory and more than 450 MByte free GPU memory.
I wonder what the minimum requirements are for the Einstein Cuda applications?
Best regards Bent
PS! This is not important but more for fun. The NVS310 is more a standard video card and not intended for heavy GPU crunching :-).
According to BRP CUDA
)
According to BRP CUDA requirements ( READ ONLY thread ) it seems sufficient, but your BOINC version shows the "read memory bug" for host 5965511 (it shows 134214143MB), which might convert to negative memory available.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
RE: According to BRP CUDA
)
I find the reported GPU memory in My Computers list to be always wrong but the application runs OK and validates for example:
NVIDIA GeForce GTX 670 (6143MB)
Another is reported: NVIDIA GeForce GTX 560 (5119MB)
and my all time favorite: NVIDIA GeForce GTX 560 Ti (-2147483648MB)
Perhaps having a GPU with negative 2 Peta-bytes of memory is why I can't remember shit.
He-he, that must be the case
)
He-he, that must be the case LOLOL :-)))). And in an application report I even find that the GPU only had 8 DualPrecision FLOPs/sec. Yes 8 FLOPs, not GFLOPs. It was marked as bizarre low. :-)))))
Otherwise Einstein runs flawless on my other computers with ordinary good GPU's.
Have a wonderful crunching week, Bent
Today I got my fresh new
)
Today I got my fresh new computer up and run with the AMD FX8350 CPU, 16Gbyte RAM and GTX 680 GPU card with 4 GByte, Ubuntu 12.10 64 bit and BOINC 7.0.27.
Then I happily connected to the Einstein project, and what a disappointment. The standard CPU applications runs just fine, but the GPU versions are telling about too little memory, just as I have with my micro GPU (see the thread).
I know this may be a issue with the BOINC client, but all the Primegrid GPU applications runs just fine.
I really do wanna crunch Einstein GPU applications, but this silly bug do stop me. Is it possible, either by an extra option on the prefernece page or as a hardcoding to make an override of the memory test? Thus it will be possible to run the application despite this BOINC bug, just as the Primegrid applications do pretty well.
With very best regards
Bent Vangli, Oslo, Norway
PS! My older installations runs both CPU and GPU Einstein application.