View Full Version : BOINC + GPU + Remote Desktop = :(
KaptainBlaZzed
10-06-2009, 07:54 PM
I can not get BOINC or any other program to recognize the GPU on the remote computer while i am using Remote Desktop.
Everything works fine if i hook it to mouse\monitor\kb.
It this normal, or am i missing something?
Win 7 x64
9600 GSO
[XC] riptide
10-06-2009, 08:04 PM
Thats the same situation in F@H. :(
KaptainBlaZzed
10-06-2009, 09:07 PM
Grr.....Ok, i now have the second 9600 GSO in my main computer.
[XC] riptide
10-07-2009, 05:23 AM
Grr.....Ok, i now have the second 9600 GSO in my main computer.
Troy... from a Milkyway@home thread....
Speaking of, I just installed milkyway on another machine that was idling an HD4850 :wasntme:
Happy to report this works without any issues. Different catalyst on there, a little older (9.6 I think), machine is controlled via VNC, so no screen on it - and it works, almost as fast as on the 4870's.
Refreshing to see ATI + GPGPU actually WORK for a change :shocked:
Try VNC??
jcool
10-07-2009, 05:56 AM
I'm using UltraVNC on that machine, not RDP. Guess that makes the difference? ;)
The win7 built in remote desktop, disables the GPU when a remote computer logs in :mad::mad::mad: But once you exit logout of the remote session the GPU is enabled and crunching resumes. Just don't login to often or you can cause WU errors on larger projects such as GPUgrid.
skycrane
03-19-2010, 11:19 AM
im running net op with mine, but they are all xp64 and server 03. but i do have an dsub to vga adaptor conected to each card, so that might help out ???
Particle
03-20-2010, 03:21 PM
Agreed, with one correction:
RDP swaps your video device for an optimized software driver that helps RDP be more responsive. Your real driver doesn't get re-loaded, however, until you log back in in person on that computer. If you connect and disconnect, the pseudo driver is still loaded and will remain so until you log in at the keyboard.
Anything already accessing the GPU will continue to run until it terminates, however, though nothing new can load afterward. Example: If you have a FAH GPU2 client running and use RDP, it'll complete the WU but fail when it tries to start the next. Even when that WU is running, if you try to start anything else that uses the GPU it'll error.
When your application requires 3D, I suggest you use a VNC client. It just taps the real video driver instead of replacing it.
Molotox
03-20-2010, 04:50 PM
Use UltraVNC instead of RDP. It's free and won't mess up your Boinc GPU apps. I had the same problem with GPUGrid.