| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: GPU Support Forum
Thread: Next GPU Beta series |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 45
|
|
| Author |
|
|
CandymanWCG
Senior Cruncher Romania Joined: Dec 20, 2010 Post Count: 421 Status: Offline Project Badges: 
|
Hi SekeRob,
----------------------------------------I think we're kind of hijacking this thread, but here goes nothing: if you're asking me what would happen in that case, I'm 50-50 on the answer. If your questions are rhetorical, then please disregard my last remark. As for the roll-back, I'm curious: wouldn't that mean that you actually need to do it from the machine itself (so obviously not via RD client)? Cheers! Knowledge is limited. Imagination encircles the world! - Albert Einstein   |
||
|
|
mikey
Veteran Cruncher Joined: May 10, 2009 Post Count: 826 Status: Offline Project Badges: 
|
For the Know-How: Would RDPing be sensed by BOINC as using the system, meaning What if an RDPeed client is set to pause GPU computing when ever a remote session is started? I'm using TeamViewer7 [works on all platforms], and when using their driver it blew the remote GPU driver, but only when I told it to blank the remote screen... black it. Fortunately the W7-64 system has a roll-back in the display driver update screen, so was back in no time by simply choosing the previous driver from the pick list, no booting required. --//-- I use UltraVNC and it seems to not mess with the video card drivers or stop the gpu crunching when I do it. It is free too. I do not know about TeamViewer though, except it is not free.   |
||
|
|
mikey
Veteran Cruncher Joined: May 10, 2009 Post Count: 826 Status: Offline Project Badges:
|
Et al [Not At Al]. It seems critical as from reading many support threads, that display drivers are best uninstalled before upgrading, boot, back into the basic default and then install the new. This for best most reliable result. Shortcutting this process comes frequently with troubles. As it is while toiling around with the Radeon/Catalyst drivers and tools, I've done the various ways, and at times still had the system display as were I still on the old drivers. Booting is painful with 8 threads concurrent... there's always that checkpoint that has not been made for one or the other task for the last 30 minutes :(. If there is a manual that covers all steps to install the drivers, flow chart form accompanied ideally, I'd be happy to add this to the FAQs GPU section and sticky it [or sticky it in this forum, but that requires admin help]. --//- One step you left out is the step to run the small program from Guru3d.com http://downloads.guru3d.com/download.php?det=1655 that removes the AMD drivers from your pc. This is best to run all the time after you use the uninstall thru Windows options. As we all know Windows is really bad at leaving stuff, this will remove it, BUT you need to be careful, it will remove too much other stuff if you are not careful!! [Edit 1 times, last edit by mikey159b at Mar 20, 2012 11:50:53 AM] |
||
|
|
Jim1348
Veteran Cruncher USA Joined: Jul 13, 2009 Post Count: 1066 Status: Offline Project Badges: 
|
I use UltraVNC and it seems to not mess with the video card drivers or stop the gpu crunching when I do it. It is free too. UltraVNC works for me too. Back when I was using Microsoft's own Remote Desktop Connection (I think on WinXP, but maybe it was Vista?), it would crash BOINC when I logged in as Administrator, but not when using a User account, or vice-versa. The details are hazy now, but I know it could be made to work one way or the other. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
For the Know-How: Would RDPing be sensed by BOINC as using the system, meaning What if an RDPeed client is set to pause GPU computing when ever a remote session is started? I'm using TeamViewer7 [works on all platforms], and when using their driver it blew the remote GPU driver, but only when I told it to blank the remote screen... black it. Fortunately the W7-64 system has a roll-back in the display driver update screen, so was back in no time by simply choosing the previous driver from the pick list, no booting required. --//-- I use UltraVNC and it seems to not mess with the video card drivers or stop the gpu crunching when I do it. It is free too. I do not know about TeamViewer though, except it is not free. It is as free as a bird in the sky... long as you comply with "non- commercial use", then a closing a connection will say the session was sponsored by TeamViewer.. (not sure how they do when it never leaves the LAN :D) --//-- |
||
|
|
Hypernova
Master Cruncher Audaces Fortuna Juvat ! Vaud - Switzerland Joined: Dec 16, 2008 Post Count: 1908 Status: Offline Project Badges:
|
Soon - in about 30 minutes or so. Excellent, thanks knreed. I received four WU's.  Here is the first that has been processed by a Nvidia GTX580 with a 296 series driver. CPU usage was 0.85% of one core. As I have 6 cores and 12 threads that is ok. Here under, the first GPU WU processed in the whole history of WCG, by my solar system:  BETA_ X0900060941435200511301450_ 0-- Haumea Pending Validation 19.03.12 23:09:45 20.03.12 12:50:01 0.05 130.9 / 0.0 You cannot imagine how much this moment was expected and welcomed. It was processed swiftly and smoothly without any problem. It was amazing to see the task moving up the 12 CPU tasks that were in running mode. I display the tasks in order of their completion percentage, the GPU WU started on the bottom of the running task list and did climb incredibly fast. In fact it was on top of the task list at 99.4% completion after 2 minutes and 20 seconds, and then it finished at 3 minutes 30 seconds. I did not understand why it took nearly a minute to finish the remaining 0.6% and then start uploading. Here under the result log with kernel times etc.. Result Name: BETA_ X0900060941435200511301450_ 0-- <core_client_version>6.10.58</core_client_version> <![CDATA[ <stderr_txt> Commandline: projects/www.worldcommunitygrid.org/wcg_beta3_img_6.44_windows_intelx86__cuda_opencl X0900060941435200511301450.jp2 --device 0 Boinc requested NVIDIA gpu device number 0 Found compute platform NVIDIA Corporation Selecting this platform CL_DEVICE_NAME: GeForce GTX 580 CL_DEVICE_VENDOR: NVIDIA Corporation CL_DEVICE_VERSION: 296.10 CL_DEVICE_MAX_COMPUTE_UNITS: CL_DEVICE_MAX_WORK_ITEM_DIMENSIONS: 3 CL_DEVICE_MAX_WORK_ITEM_SIZES: 1024 / 1024 / 64 CL_DEVICE_MAX_WORK_GROUP_SIZE: 1024 CL_DEVICE_MAX_CLOCK_FREQUENCY: 1564 MHz CL_DEVICE_ADDRESS_BITS: 32 CL_DEVICE_MAX_MEM_ALLOC_SIZE: 384 MByte CL_DEVICE_GLOBAL_MEM_SIZE: 1536 MByte CL_DEVICE_ERROR_CORRECTION_SUPPORT: no CL_DEVICE_LOCAL_MEM_TYPE: local CL_DEVICE_LOCAL_MEM_SIZE: 48 KByte CL_DEVICE_MAX_CONSTANT_BUFFER_SIZE: 64 KByte CL_DEVICE_QUEUE_PROPERTIES: CL_QUEUE_OUT_OF_ORDER_EXEC_MODE_ENABLE CL_DEVICE_QUEUE_PROPERTIES: CL_QUEUE_PROFILING_ENABLE CL_DEVICE_EXTENSIONS: cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_d3d9_sharing cl_nv_d3d10_sharing cl_khr_d3d10_sharing cl_nv_d3d11_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 CL_DEVICE_COMPUTE_CAPABILITY_NV: 2.0 CL_DEVICE_REGISTERS_PER_BLOCK_NV: 32768 CL_DEVICE_WARP_SIZE_NV: 32 CL_DEVICE_GPU_OVERLAP_NV: CL_TRUE CL_DEVICE_KERNEL_EXEC_TIMEOUT_NV: CL_TRUE CL_DEVICE_INTEGRATED_MEMORY_NV: CL_FALSE Estimated kernel execution time = 0.31220 [sec] Starting analysis of ../../projects/www.worldcommunitygrid.org/BETA_X0900060941435200511301450_X0900060941435200511301450.jp2... Extracting GLCM features... Total kernel time: 81.329338 (1026 kernel executions) Total memory transfer time: 2.426409 Average kernel time: 0.079268 Min kernel time: 0.066550 (dx=25 dy=5 sample_dist=24 ) Max kernel time: 0.102766 dx=1 dy=1 sample_dist=0 Total time for ../../projects/www.worldcommunitygrid.org/BETA_X0900060941435200511301450_X0900060941435200511301450.jp2: 184 seconds Finished Image #0, pctComplete = 1.000000 CPU time used = 179.042348 13:49:35 (2588): called boinc_finish </stderr_txt>  [Edit 3 times, last edit by Hypernova at Mar 20, 2012 1:19:39 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Part of the standard HCC GPU program... for you 1 minute CPU, 1 minute GPU, 1 minute CPU. I'm guessing this is the same minute as the one we see with HCC CPU tasks when progress halts at 99.818 for that time, then skips to 100% and uploads.
--//-- |
||
|
|
BSD
Senior Cruncher Joined: Apr 27, 2011 Post Count: 224 Status: Offline |
3/19/2012 8:18:01 AM | | ATI GPU 0: AMD Radeon HD 6x00 series (Turks) (CAL version 1.4.1703, 1024MB, 768 GFLOPS peak) ---snip--- 3/19/2012 10:18:50 PM | | GPUs have become unusable; disabling tasks Is this because there's no more BETAs in the current batch or has my GPU been permanently blacked flaged due to using the wrong driver?  This will make 0 for 4 for my GPUs.  Ouch! Will you tell us when you schedule the funeral?  Seriously though, I have never seen that message or seen a post about it but I'm sure others may have or know to find the definition. Does not look good to me.  EDIT: This is what I could find. Good luck.  http://setiathome.berkeley.edu/forum_thread.php?id=65084 http://www.gpugrid.net/forum_thread.php?id=2494#21002 Thanks for the links. This is a work computer, the screen was locked when I left. Later in the evening is when I RDP'd into it and saw the "unusable" message. I disconnected the session which left the physical computer console locked. In the morning unlocking the console screen: 3/20/2012 8:08:04 AM | | GPUs have become usable; enabling tasks. Wow, all night RDP session disconnected and GPU was unusable until a console login? Just like Candyman suggested, reboot after a RDP session. As a test, I unset "Use GPU while in use", rebooted, RDP into it from another computer: 3/20/2012 8:29:17 AM | | GPUs have become unusable; disabling tasks Disconnected the RDP session and unlocked the console screen: 3/20/2012 8:53:07 AM | | GPUs have become usable; enabling tasks Moral of the story, don't use RDP unless you can login to the console or reboot the computer after a RDP session. I haven't tried any non-MS remote session clients to see if that makes a difference. |
||
|
|
Fulen
Cruncher Joined: Apr 30, 2010 Post Count: 2 Status: Offline Project Badges: 
|
My remote session disables it, and puts it back on after i leave. Win 7
(Win remote desktop out) X3-PC --- 20.03.2012 15:15:15 GPUs have become usable; enabling tasks (Win remote desktop in) X3-PC --- 20.03.2012 15:14:14 GPUs have become unusable; disabling tasks |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Doing a Lawrence:
 --//-- |
||
|
|
|