Forum > GPU crunching

BOINC 6.6.20 x64 does not run on 2 GPUs on Win 7

(1/5) > >>

FalconFly:
Following the Team Mod discussion and updates, I went with the new recommendations.

However, the old result remained :
BOINC 6.6.20 x64 does not recognize the 2nd GPU of my GTX295 unter Win7 64bit.

Consequently the V11 VLARkill_refined is launched only once instead of twice.
Other than that, everthing is apparently working fine.

I'll have to revert to my old Installation with V10a Team Mod in order to get the 2nd GPU back into business unless someone can find an error I made.

- Point blank installation of BOINC x64 6.6.20
- attached to Project (no workunits downloaded yet)
- quite BOINC
- inserted cudart.dll into program files Directory (overwriting the default one, assuming the new one is required here also)
- inserted V11 + SSE3 Files, cudart.dll, cufft.dll, libfftw3f-3-1-1a_upx.dll and app_info.xml files into program data/projects/setiathome Sub-Directory
- launched BOINC

-- edit --

This app_info.xml works like a charm for my 2 GTX295, now running under WinXP SP3 32bit and BOINC 6.6.20 Win32
(Win32, CPU SSE3 for AP und MB, for GPU V11 VLARkill)


--- Code: ---<app_info>
 <app>
 <name>astropulse</name>
 </app>
<file_info>
<name>ap_5.00r103_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse</app_name>
<version_num>500</version_num>
<file_ref>
<file_name>ap_5.00r103_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
 <app>
 <name>astropulse_v5</name>
 </app>
<file_info>
        <name>ap_5.03r112_SSE3.exe</name>
        <executable/>
</file_info>
<app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
        <file_ref>
        <file_name>ap_5.03r112_SSE3.exe</file_name>
        <main_program/>
        </file_ref>
</app_version>

 <app>
 <name>setiathome_enhanced</name>
 </app>
<file_info>
<name>AK_v8_win_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>528</version_num>
<file_ref>
<file_name>AK_v8_win_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<file_ref>
<file_name>AK_v8_win_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>

 <app>
 <name>setiathome_enhanced</name>
 </app>
<file_info>
<name>MB_6.08_mod_CUDA_V11_VLARKill_refined.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft.dll</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>

<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<flops>21400000000</flops>
<plan_class>cuda</plan_class>
<avg_ncpus>0.150000</avg_ncpus>
<max_ncpus>0.150000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB_6.08_mod_CUDA_V11_VLARKill_refined.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
</app_version>

</app_info>
--- End code ---

Jason G:
Hi FalconFly,
   Was curious about this issue you're having, in case it has ramifications for some of the development going on in the background, regarding installer prototype:

Number of GPUs is managed by Boinc &  Drivers:

i notice that your Windows 7 machine, comes up with coprocessor as:

--- Quote ---NVIDIA GeForce GTX 295 (896MB) driver: 18585
--- End quote ---

Whereas Bob Mahoney's 3 card (6 GPU) setup comes up as:

--- Quote --- [6] NVIDIA GeForce GTX 295 (895MB) driver: 18585
--- End quote ---

Just to eliminate the obvious things that can cause this: Do you have SLI disabled properly (so it'll be seen by the system as 2 GPUs instead of one big one), and does the seond GPU possibly need something plugged into it to wake it up.  The v10 team build may be 'Fudging' the setup to make it look like it's working, when it might not be.

Jason

FalconFly:
Yes, that's correct.

I've never managed to get 6.6.20 to show [2] GPUs like I saw on other Systems I looked at for comparison.
I have SLI disabled in the Driver for the GTX295 and even Enabled it for a quick test. No change.

Unless I made another mistake this as good as I could get, following the latest recommendations.

Lacking detailled documentation (I hate that), there still are possible mistakes I did :

Is the cudart.dll indeed supposed not only to go into the Projects directory, but also in the program files?
The one I found there by default was a ~447k File and came with the original BOINC 6.6.20 installation.
I noticed the one found in the V10a was only 228k and thus obviously another version.

I haven't checked so far, but maybe the cudart.dll coming with BOINC 6.6.20 Installation by default might/should be used instead of the one I took from the V10a Team Mod package.

Might also be an Idea to let BOINC download its .dlls from the stock CUDA application download alltogether and try to use these instead with the V11 VLARkill_refined (and leave all .dlls from the old V10a Team Mod package alone ?

With a bit of luck, one of these steps I took turns out to be a mistake.

My other Single GPU GTX285 installation with BOINC 6.6.20 does run fine this way, but I also noted there ist no [1] in front of the GPU indication on the Computer Overview page. With these details, we may be onto something.
Additionally, it runs the Default intel_x86 CUDA client which still leaves me with the VLAR problems.

Devaster:
it seems that is a driver bug - i have three cards and see only onr too under win7...
i  am trying another driver - if functional then i refer and send a link ...

cuda-z is showing only one cuda device too ....

FalconFly:
-- edit --

http://setiathome.berkeley.edu/show_host_detail.php?hostid=4900487

Same Driver, so it does seem to work under Windows 7 x64 at all, but these are 2 individual GTX285...
Might be a problem with the dual GPU cards then.

Navigation

[0] Message Index

[#] Next page

Go to full version