Questions and Answers :
Windows :
RDP'ing to Machine with GPU Processing
Message board moderation
Author | Message |
---|---|
Rick Chabot Send message Joined: 10 Apr 02 Posts: 6 Credit: 8,791,333 RAC: 0 |
Hi, Does anyone know if you have a machine running GPU tasks and you have to RDP (Remote Desktop) to the machine (as I must do from time to time) will BOINC give that GPU disabled message and no longer process those WU until I log back into the the machine's console and restart BOINC? I had something like this happen the other day and was just curious if it is the norm. Thanks |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
Yes, that is normal. It's caused by Windows RDP itself, as that uses a videocard driver of its own (for stability reasons), one that doesn't know about CUDA, CAL or OpenCL. This RDP driver cannot be updated to one that knows about these new technologies either. So, when you RDP into a machine, it'll use the RDP video driver, and then BOINC will just halt processing any work on the GPU, since the GPU will be 'lost'. Until you RDP out, and wait, or restart the remote machine. A way around is not to use RDP, but something like VNC or LogMeIn, which use the driver supplied by the user, not their own. |
John McLeod VII Send message Joined: 15 Jul 99 Posts: 24806 Credit: 790,712 RAC: 0 |
Hi, It depends on what you use to access the remote desktop. If you use Windows Remote Desktop, then, yes, BOINC will stop running GPU tasks until you log in using the console. If you use VNC, it won't. The difference lies in how the two do the work. Windows RDP creates a new session and uses its own drivers to show the screen remotely. This bypasses the hardware on the side being accessed. VNC does not create a new session, but uses the current one. BOINC WIKI |
Rick Chabot Send message Joined: 10 Apr 02 Posts: 6 Credit: 8,791,333 RAC: 0 |
Thanks for the response. I was guessing this was the reason. Just thought I would ask. I do use Windows Remote Desktop, and I know it does not use the native hardware drivers. Have to look into an alternative approach :) Thanks for the suggestions. |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.