Message boards :
Number crunching :
Crashing GPUs when coming in with Remote Desktop
Message board moderation
Author | Message |
---|---|
woodenboatguy Send message Joined: 10 Nov 00 Posts: 368 Credit: 3,969,364 RAC: 0 |
I found a thread that describes this from a while back: http://setiathome.berkeley.edu/forum_thread.php?id=55939 It says that the upgrade at the time to 6.10.15 would prevent this. I've been encountering it myself recently however and I am on 6.10.43. It's happened a couple of times now - if fact the reason I caught it was I was remoting in from the laptop upstairs to check on things downstairs. The basement machine showed this message: 11/04/2010 11:15:48 PM GPUs have become unusable; disabling tasks only moments before I'd connected, hence my suspicion. Anyone else able confirm they can knock their GPUs off line by coming in on a 6.10.43 machine from remote? As background, the machine losing its GPUs is a Windows 7 64 bit and the machine I remoted in from is Vista 32 bit. Regards, |
BilBg Send message Joined: 27 May 07 Posts: 3720 Credit: 9,385,827 RAC: 0 |
You may also read: CUDA and Remote Desktop http://setiathome.berkeley.edu/forum_thread.php?id=55653 Any version of BOINC can't crunch on GPU as Microsoft's Remote Desktop replaces the video driver with non-CUDA generic video driver. Old versions of BOINC will in this case delete all of your CUDA tasks. New versions of BOINC are just suspending CUDA computation. I will recommend using TeamViewer http://www.teamviewer.com/ Â - ALF - "Find out what you don't do well ..... then don't do it!" :) Â |
woodenboatguy Send message Joined: 10 Nov 00 Posts: 368 Credit: 3,969,364 RAC: 0 |
Gads! I wonder now how many times I've crippled my machines by just being slightly lazy and not bothering to stumble down the stairs to check on things personally. Thanks for the tip on the software. I am going to look into that. Regards, |
Sidewinder Send message Joined: 15 Nov 09 Posts: 100 Credit: 79,432,465 RAC: 0 |
There are a few programs to get around this issue. I've tried UltraVNC (well pretty much all the flavors of VNC), but I find that LogMeIn works best. It's free for personal use; plus, you can access your computer(s) from anywhere in the world. You login using a web interface (addon for Firefox and I think it may use ActiveX for IE) and it uses RSA 2048 bit keys with AES256 for encryption. https://secure.logmein.com/US/solutions/personal/ |
BilBg Send message Joined: 27 May 07 Posts: 3720 Credit: 9,385,827 RAC: 0 |
There are a few programs to get around this issue. I've tried UltraVNC (well pretty much all the flavors of VNC), but I find that LogMeIn works best. It's free for personal use; plus, you can access your computer(s) from anywhere in the world. You login using a web interface (addon for Firefox and I think it may use ActiveX for IE) and it uses RSA 2048 bit keys with AES256 for encryption. TeamViewer security: http://www.teamviewer.com/products/security.aspx " Encryption TeamViewer includes full encryption, based on RSA private-/public key exchange and AES (256 Bit) session encoding. This technology is based on the same standards as https/SSL and is considered completely safe by today's standards. The key exchange also guarantees a full client-to-client data protection. This means that even our routing servers will not be able to read the data stream. " "from anywhere in the world": The same for TeamViewer (I connect from Bulgaria to my daughter's computer in London - the response time is ~ 1 sec) . Â - ALF - "Find out what you don't do well ..... then don't do it!" :) Â |
Gundolf Jahn Send message Joined: 19 Sep 00 Posts: 3184 Credit: 446,358 RAC: 0 |
It's happened a couple of times now - in fact the reason I caught it was I was remoting in from the laptop upstairs to check on things downstairs. If the "things" to check on are only BOINC-related, you could use the "Select computer..." feature of the manager's Advanced menu. (See Controlling BOINC remotely) Gruß, Gundolf Computer sind nicht alles im Leben. (Kleiner Scherz) SETI@home classic workunits 3,758 SETI@home classic CPU time 66,520 hours |
©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.